[WIP] Xenial Fixes

Repos for Xenial are not currently available, so install packages
directly by URL.
Upstream Bug: https://github.com/eLvErDe/hwraid/issues/50
Connects: rcbops/u-suk-dev#825

:eyes: Preview

Your content preview is now ready. :bow:

HULK PREVIEW

:mag_right: Preview

HULK PREVIEW

Your content preview is now ready. :bow:

recheck_all

The standard gate will test on 14.04, heres a test build on 16.04: http://jenkins.propter.net/job/JJB-RPC-AIO_master-cidev-xenial/100/

rebuild after rebase: http://jenkins.propter.net/job/JJB-RPC-AIO_master-cidev-xenial/102/

recheck_all

Ready for Review. This has now passed the standard gate (14.04) and a check on 16.04 (job 102 linked above).

Xenial build including the removal of xtrabackup from the rpc support role and excluding the patch to enable the percona repo: http://jenkins.propter.net/job/JJB-RPC-AIO_master-cidev-xenial/107/

Successful Xenial test run without percona repo: http://jenkins.propter.net/job/JJB-RPC-AIO_master-cidev-xenial/109/console

16.04 build after hwraid cleanup: http://jenkins.propter.net/job/JJB-RPC-AIO_master-cidev-xenial/120/

16.04 build succeeded http://jenkins.propter.net/job/JJB-RPC-AIO_master-cidev-xenial/120/

+1 This looks good to me, however there is one thing that concerns me. Please see https://github.com/rcbops/jenkins-rpc/pull/693#issuecomment-271310558

16.04 build with DEPLOY_MAAS=yes - good idea to test with maas @alextricity25  http://jenkins.propter.net/job/JJB-RPC-AIO_master-cidev-xenial/125/

MaaS job failed for a few reasons:
Rackspace-monitoring-agent package not available:
01:54:04.554 TASK [rpc_maas : Ensure container packages are installed] **********************
...
01:54:07.833 failed: [jramcx-125-11317] (item=[u'rackspace-monitoring-agent', u'mariadb-client']) => {"failed": true, "item": ["rackspace-monitoring-agent", "mariadb-client"], "msg": "No package matching 'rackspace-monitoring-agent' is available"}

Curl binary not available:
01:56:00.978 TASK [rpc_maas : Get list of vhosts] *******************************************
01:56:01.988 fatal: [jramcx-125-11317_rabbit_mq_container-efa08146]: FAILED! => {"changed": true, "cmd": "curl -u maas_user:c5f6be54fe7c45e7828542a3ada8ac2911b08bf6e9d1292962962d6275c localhost:15672/api/vhosts", "delta": "0:00:00.002979", "end": "2017-01-10 09:11:56.173268", "failed": true, "rc": 127, "start": "2017-01-10 09:11:56.170289", "stderr": "/bin/sh: 1: curl: not found", "stdout": "", "stdout_lines": [], "warnings": ["Consider using get_url or uri module rather than running curl"]}

/etc/rackspace-monitoring-agent.conf.d does not exist - Probably because the package was not installed available.
01:57:33.476 TASK [rpc_maas : Install process checks] ***************************************
...
01:57:40.529 failed: [jramcx-125-11317_horizon_container-a1bc7d24 -> <IP_ADDRESS>] (item={u'group': u'all', u'name': u'filebeat_process_check'}) => {"changed": true, "failed": true, "item": {"group": "all", "name": "filebeat_process_check"}, "msg": "Destination directory /etc/rackspace-monitoring-agent.conf.d does not exist"}

Package not installed because repo add task has hard coded list of versions that doesn't include 16.04 https://github.com/rcbops/rpc-openstack/blob/master/rpcd/playbooks/roles/rpc_maas/tasks/repo_setup.yml#L28
 when: "ansible_distribution_version in ['12.04', '13.04', '13.10', '14.04'] and maas_apt_repos is defined"

Next test job with MaaS: http://jenkins.propter.net/job/JJB-RPC-AIO_master-cidev-xenial/128/

seems like this is still in-progress, not needs-review

@prometheanfire It was a review commented that prompted a check with MaaS enabled. Cards can't go backwards so the fixes for MaaS on 16.04 need to be done with the card where it is :/

Cards not being able to go backwards seems like sticking our heads in the sand.  Sometimes you need to go back and work on things.  reassign me when this is actually in needs review, not pretend needs review.

cc @hughsaunders I've rebuilt the xenial job with maas enabled: http://jenkins.propter.net/job/JJB-RPC-AIO_master-cidev-xenial/

Previous build failed because I didn't add the url scheme when calling the URI module, next build: http://jenkins.propter.net/job/JJB-RPC-AIO_master-cidev-xenial/131/

Previous build failed on memached version:
02:10:26.555 TASK [Local MaaS Checks] *******************************************************
02:10:46.479 FAILED - RETRYING: TASK: Local MaaS Checks (5 retries left).
02:11:24.397 FAILED - RETRYING: TASK: Local MaaS Checks (4 retries left).
02:12:02.573 FAILED - RETRYING: TASK: Local MaaS Checks (3 retries left).
02:12:40.264 FAILED - RETRYING: TASK: Local MaaS Checks (2 retries left).
02:13:17.985 FAILED - RETRYING: TASK: Local MaaS Checks (1 retries left).
02:13:55.495 fatal: [jramcx-131-22575]: FAILED! => {"changed": false, "cmd": " . /openstack/venvs/maas-r13.1.0rc1/bin/activate\n  /opt/rpc-openstack/scripts/rpc-maas-tool.py verify-local  --excludeverifycheck holland_local_check\n ", "delta": "0:00:17.380652", "end": "2017-01-11 02:51:09.023990", "failed": true, "failed_when_result": true, "rc": 1, "start": "2017-01-11 02:50:51.643338", "stderr": "", "stdout": "The following metrics are required by alarms but not produced by any checks: set(['memcache_curr_connections'])\nThe following checks failed to execute or didn't return 'okay' as their status: [('memcached_status--jramcx-131-22575-memcached-container-899a7d5c', \"status error This plugin has only been tested with version ['1.4.14 (Ubuntu)', '1.4.15'] of memcached, and you are using version 1.4.25 Ubuntu\\n\")]", "stdout_lines": ["The following metrics are required by alarms but not produced by any checks: set(['memcache_curr_connections'])", "The following checks failed to execute or didn't return 'okay' as their status: [('memcached_status--jramcx-131-22575-memcached-container-899a7d5c', \"status error This plugin has only been tested with version ['1.4.14 (Ubuntu)', '1.4.15'] of memcached, and you are using version 1.4.25 Ubuntu\\n\")]"], "warnings": []}

Next build: http://jenkins.propter.net/job/JJB-RPC-AIO_master-cidev-xenial/134/

16.04 + MaaS build succeeded http://jenkins.propter.net/job/JJB-RPC-AIO_master-cidev-xenial/134/ 🎉

does that mean we can move back to needs-review :P

@prometheanfire yes please

16.04 test build after latest changes requested by @odyssey4me http://jenkins.propter.net/job/JJB-RPC-AIO_master-cidev-xenial/136/

@hughsaunders Thank you for doing those changes. However, I just realised that those debs are versioned, and that he repo only carries one version, which means if they update the repo then a new deployment for that tag won't work any more. It may be best to instead add the repo as it used to, but just add the wily repo for xenial? That way it will work today, and next year for any release.

These changes look very good to me, but I'm going to hold off my approval until the commit title is fixed and all of the jenkins jobs have run successfully.

which commit title? there have been a ton of commits

you know, the only way to fix this is to do an amended commit :P

Switched back to using repos for hwraid packages trusty-->trusty xenial-->wily. Test build: http://jenkins.propter.net/job/JJB-RPC-AIO_master-cidev-xenial/141/

recheck_all Previous jobs failed because Jenkins ran out of disk.

Xenial build: http://jenkins.propter.net/job/JJB-RPC-AIO_master-cidev-xenial/143/

Xenial build failed on MaaS verify / missing metric: neutron-metering-agent_status
02:12:54.189 TASK [Local MaaS Checks] *******************************************************
02:13:16.684 FAILED - RETRYING: TASK: Local MaaS Checks (5 retries left).
02:13:57.587 FAILED - RETRYING: TASK: Local MaaS Checks (4 retries left).
02:14:37.760 FAILED - RETRYING: TASK: Local MaaS Checks (3 retries left).
02:15:17.739 FAILED - RETRYING: TASK: Local MaaS Checks (2 retries left).
02:15:58.675 FAILED - RETRYING: TASK: Local MaaS Checks (1 retries left).
02:16:39.342 fatal: [jramcx-143-23658]: FAILED! => {"changed": false, "cmd": " . /openstack/venvs/maas-r13.1.0rc1/bin/activate\n  /opt/rpc-openstack/scripts/rpc-maas-tool.py verify-local", "delta": "0:00:20.535667", "end": "2017-01-13 01:44:17.044005", "failed": true, "failed_when_result": true, "rc": 1, "start": "2017-01-13 01:43:56.508338", "stderr": "", "stdout": "The following metrics are required by alarms but not produced by any checks: set(['neutron-metering-agent_status'])", "stdout_lines": ["The following metrics are required by alarms but not produced by any checks: set(['neutron-metering-agent_status'])"], "warnings": []}

This turns out to be an OSA and upstream Neutron issue, which I'll work on in rcbops/u-suk-dev#976

Set interface_driver in neutron_metering_agent_ini_overrides (config template) so that this PR can continue while the upstream neutron and OSA fixes are trickling through.
Next Xenial Build: http://jenkins.propter.net/job/JJB-RPC-AIO_master-cidev-xenial/146/

Previous build failed on getting the glance image a few seconds in :( next build: http://jenkins.propter.net/job/JJB-RPC-AIO_master-cidev-xenial/148/

Build 148 failed on the holland test because it used jenkins-rpc branch bug/825 which hadn't' been reabsed on master so didn't' include https://github.com/rcbops/jenkins-rpc/commit/230a7753f48d5792ef2f47501fe3281f902b3ded which is required now that https://github.com/rcbops/rpc-openstack/commit/a25b0252cf4d5d400401f0dcb7fab12bedbe1236 has merged. I propose that we merge this PR anyway, as it got past the previous problem and the problem it hit has already been fixed.


Appointment Booking Bot

Hi Ranjan,
You have made wonder full bot, I have used your VFS-APPOINTMENT-BOT, but I want to further add appointment booking bot.
Please help on this.

Hi Ramakant,
I'm happy to know it was helpful!
We also thought about it and decided not to include appointment booking functionality at this time because appointment booking is a little more complex, requiring collecting and managing a significant amount of user data. Additionally, integrating payment processing introduces security considerations.
The idea was to keep the bot simple and easy to use.
We're currently focusing on expanding it to support new countries! However, appointment booking could be an useful feature in the future. If you're interested, feel free to contribute.


Unexpceted exception when resolving more than once

Here is a repro, the exception says 'InvalidOperationException - Value of ContainerControlledLifetimeManager can only be set once',  is it bug or expected? And what is the correct usage
[TestMethod]
        public void ResolveFactory_ShowNotThrowOnResolve()
        {
            IUnityContainer container = new UnityContainer();
            container.RegisterType<object>("key", new ContainerControlledLifetimeManager(), new InjectionFactory(c => null));
            container.Resolve<object>("key");
            container.Resolve<object>("key");
        }

This works in at least 5.5.5

Your injection factory returns null ... new InjectionFactory(c => null).
Value null is not a valid object. Next time you try to resolve it, container calls your factory again and attempts to set it on the lifetime container second time via SetValue. But since it is already initialized with null in first resolve it throws.
To fix your test do this instead:
[TestMethod]
public void ResolveFactory_ShowNotThrowOnResolve()
{
    IUnityContainer container = new UnityContainer();
    container.RegisterType<object>("key", new ContainerControlledLifetimeManager(), new InjectionFactory(c => new object()));
    container.Resolve<object>("key");
    container.Resolve<object>("key");
}

@ENikS  I would argue this is a regression,  it is a valid scenario that a factory will conditionally return null,  and the case worked for previous versions.   If you insist this is by design, I would say Unity does not have consistent and valid design and will have to move away from it

Typically situation when lifetime manager is set twice indicative of abnormal condition and requires attention, hence the exception.
If you insist on null being valid object just copy lifetime manager from here, rename it and use away...


Column order reversed

The code below returns a table with "Value" and then "Date", but I'd expect the column order to be "Date" and then "Column" just as the data is represented on the site: https://www.quandl.com/data/MULTPL/SHILLER_PE_RATIO_MONTH-Shiller-PE-Ratio-by-Month
session = TableSawQuandlSession.create();
cape = session.getDataSet(DataSetRequest.Builder.of("MULTPL/SHILLER_PE_RATIO_MONTH").build());

Nevermind. This bug is in beakerx


[timeseries] add all frequencies support.

Description
Now user can use all frequencies for time series inference including "10min", "12D", "24M", "7W" etc.
And taking into account the precision problem, turn float multiple into double multiple in the get lags process

Codecov Report

Merging #1973 (262c292) into master (bb5073f) will decrease coverage by 1.98%.
The diff coverage is 67.91%.

@@             Coverage Diff              @@
##             master    #1973      +/-   ##
============================================
- Coverage     72.08%   70.10%   -1.99%
- Complexity     5126     5848     +722
============================================
  Files           473      575     +102
  Lines         21970    25917    +3947
  Branches       2351     2795     +444
============================================
+ Hits          15838    18168    +2330
- Misses         4925     6381    +1456
- Partials       1207     1368     +161

Impacted Files
Coverage Δ

api/src/main/java/ai/djl/modality/cv/Image.java
69.23% <ø> (-4.11%)
:arrow_down:

...rc/main/java/ai/djl/modality/cv/MultiBoxPrior.java
76.00% <ø> (ø)

...rc/main/java/ai/djl/modality/cv/output/Joints.java
71.42% <ø> (ø)

.../main/java/ai/djl/modality/cv/output/Landmark.java
100.00% <ø> (ø)

...main/java/ai/djl/modality/cv/output/Rectangle.java
72.41% <0.00%> (ø)

...i/djl/modality/cv/translator/BigGANTranslator.java
21.42% <0.00%> (-5.24%)
:arrow_down:

...odality/cv/translator/BigGANTranslatorFactory.java
33.33% <0.00%> (+8.33%)
:arrow_up:

...nslator/InstanceSegmentationTranslatorFactory.java
14.28% <0.00%> (-3.90%)
:arrow_down:

.../cv/translator/SemanticSegmentationTranslator.java
0.00% <0.00%> (ø)

.../cv/translator/StyleTransferTranslatorFactory.java
40.00% <ø> (ø)

... and 477 more

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


NoMemoryError when exporting huge events

Hi, I'm having a problem when I try to export a very large number of events
client.request('export', from_date: from_date, to_date: to_date).each do |event|
  file.puts(event.to_json)
end

We get:
2015-04-09T16:46:00.705Z 1 TID-otovfis9w WARN: failed to allocate memory
2015-04-09T16:46:00.705Z 1 TID-otovfis9w WARN: /usr/src/app/vendor/bundle/ruby/2.2.0/gems/mixpanel_client-4.1.1/lib/mixpanel/client.rb:69:in `make_normal_request'

I think it's because the HTTP body of the response is to big to be stored in memory at once.
There should be a way to stream or chunk the output.
What do you think ?

That seems reasonable. Would you like to take a stab at it?


Bar size changes with "underline" Workspace highlight and changing monitor focus

Describe the bug
The underline workspace highlight adds a bit of padding to the bar height, which is fine, however, when the monitor that's highlight loses focus, the highlight dissapears and the whole bar shrinks back. It's a bit hard to see in screenshots, but is very noticeable when the hyprland windows readjust to the new bar size.

This could be fixed by changing the bar to not flex its size when its not being highlighted, however, I would like to rework the way workspaces are highlighted to allow for highlights to appear on all active monitors.

Couldn't replicate it and added a fix for the underline pushing the number up a little bit in the related MR. Feel free to reopen this if you're still seeing the issue.


OmniSharp throws MSBuildNotFoundException

Hi, i'm trying to run omnisharp (1.39.0) with doom emacs under fedora. Starting the server throws the following error:
The following clients were selected based on priority: (server-id omnisharp, priority -1)
OmniSharp.Services.DotNetCliService: Checking the 'DOTNET_ROOT' environment variable to find a .NET SDK |
OmniSharp.Services.DotNetCliService: Checking the 'DOTNET_ROOT' environment variable to find a .NET SDK |
OmniSharp.Services.DotNetCliService: DotNetPath set to /usr/lib64/dotnet/dotnet |
OmniSharp.Services.DotNetCliService: DotNetPath set to /usr/lib64/dotnet/dotnet |
OmniSharp.MSBuild.Discovery.MSBuildLocator: Located 0 MSBuild instance(s) |
OmniSharp.MSBuild.Discovery.MSBuildLocator: Located 0 MSBuild instance(s) |
OmniSharp.Extensions.JsonRpc.InputHandler: Failed to handle request initialize 1 - OmniSharp.MSBuild.Discovery.MSBuildNotFoundException: Could not locate MSBuild instance to register with OmniSharp.
  at OmniSharp.MSBuild.Discovery.Extensions.RegisterDefaultInstance (OmniSharp.MSBuild.Discovery.IMSBuildLocator msbuildLocator, Microsoft.Extensions.Logging.ILogger logger, OmniSharp.Services.DotNetInfo dotNetInfo) [0x000b1] in <4afa8cba4e6b43e3a16fcca35fdc1d41>:0
  at OmniSharp.CompositionHostBuilder.Build (System.String workingDirectory) [0x000ad] in <4afa8cba4e6b43e3a16fcca35fdc1d41>:0
  at OmniSharp.LanguageServerProtocol.LanguageServerHost.CreateCompositionHost (OmniSharp.Extensions.LanguageServer.Protocol.Server.ILanguageServer server, OmniSharp.Extensions.LanguageServer.Protocol.Models.InitializeParams initializeParams, OmniSharp.CommandLineApplication application, Microsoft.Extensions.DependencyInjection.IServiceCollection services, System.Action`1[T] configureLogging) [0x0017d] in <9843221f127b4c1a9250fba4580c89f8>:0
  at OmniSharp.LanguageServerProtocol.LanguageServerHost.Initialize (OmniSharp.Extensions.LanguageServer.Protocol.Server.ILanguageServer server, OmniSharp.Extensions.LanguageServer.Protocol.Models.InitializeParams initializeParams, System.Threading.CancellationToken cancellationToken) [0x00000] in <9843221f127b4c1a9250fba4580c89f8>:0
  at OmniSharp.Extensions.LanguageServer.Server.LanguageServer+<>c__DisplayClass77_0.<MediatR.IRequestHandler<OmniSharp.Extensions.LanguageServer.Protocol.Models.InternalInitializeParams,OmniSharp.Extensions.LanguageServer.Protocol.Models.InitializeResult>.Handle>b__0 (OmniSharp.Extensions.LanguageServer.Protocol.Server.OnLanguageServerInitializeDelegate handler, System.Threading.CancellationToken ct) [0x00012] in <a65ee41ef84f44d8810b866724a97eec>:0
  at OmniSharp.Extensions.LanguageServer.Protocol.LanguageProtocolEventingHelper+<>c__DisplayClass0_1`2[TDelegate,THandler].<Run>b__2 (System.Threading.CancellationToken ct) [0x00000] in <16970f5ac0364766b872ef4b5abe0a02>:0
  at System.Reactive.Linq.QueryLanguage.StartAsyncImpl (System.Func`2[T,TResult] actionAsync, System.Reactive.Concurrency.IScheduler scheduler) [0x0000d] in <3a11ea46836344a282870ba916885e3d>:0
--- End of stack trace from previous location where exception was thrown ---

  at OmniSharp.Extensions.LanguageServer.Server.LanguageServer.MediatR.IRequestHandler<OmniSharp.Extensions.LanguageServer.Protocol.Models.InternalInitializeParams,OmniSharp.Extensions.LanguageServer.Protocol.Models.InitializeResult>.Handle (OmniSharp.Extensions.LanguageServer.Protocol.Models.InternalInitializeParams request, System.Threading.CancellationToken token) [0x00133] in <a65ee41ef84f44d8810b866724a97eec>:0
  at OmniSharp.Extensions.LanguageServer.Server.Pipelines.SemanticTokensDeltaPipeline`2[TRequest,TResponse].Handle (TRequest request, System.Threading.CancellationToken cancellationToken, MediatR.RequestHandlerDelegate`1[TResponse] next) [0x0031e] in <a65ee41ef84f44d8810b866724a97eec>:0
  at OmniSharp.Extensions.LanguageServer.Server.Pipelines.ResolveCommandPipeline`2[TRequest,TResponse].Handle (TRequest request, System.Threading.CancellationToken cancellationToken, MediatR.RequestHandlerDelegate`1[TResponse] next) [0x00077] in <a65ee41ef84f44d8810b866724a97eec>:0
  at MediatR.Pipeline.RequestPreProcessorBehavior`2[TRequest,TResponse].Handle (TRequest request, System.Threading.CancellationToken cancellationToken, MediatR.RequestHandlerDelegate`1[TResponse] next) [0x0013e] in <856ae299ee314304bc3affd17d8d5868>:0
  at MediatR.Pipeline.RequestPostProcessorBehavior`2[TRequest,TResponse].Handle (TRequest request, System.Threading.CancellationToken cancellationToken, MediatR.RequestHandlerDelegate`1[TResponse] next) [0x0007e] in <856ae299ee314304bc3affd17d8d5868>:0
  at MediatR.Pipeline.RequestExceptionProcessorBehavior`2[TRequest,TResponse].Handle (TRequest request, System.Threading.CancellationToken cancellationToken, MediatR.RequestHandlerDelegate`1[TResponse] next) [0x00084] in <856ae299ee314304bc3affd17d8d5868>:0
  at MediatR.Pipeline.RequestExceptionProcessorBehavior`2[TRequest,TResponse].Handle (TRequest request, System.Threading.CancellationToken cancellationToken, MediatR.RequestHandlerDelegate`1[TResponse] next) [0x00276] in <856ae299ee314304bc3affd17d8d5868>:0
  at MediatR.Pipeline.RequestExceptionActionProcessorBehavior`2[TRequest,TResponse].Handle (TRequest request, System.Threading.CancellationToken cancellationToken, MediatR.RequestHandlerDelegate`1[TResponse] next) [0x00084] in <856ae299ee314304bc3affd17d8d5868>:0
  at MediatR.Pipeline.RequestExceptionActionProcessorBehavior`2[TRequest,TResponse].Handle (TRequest request, System.Threading.CancellationToken cancellationToken, MediatR.RequestHandlerDelegate`1[TResponse] next) [0x001e7] in <856ae299ee314304bc3affd17d8d5868>:0
  at OmniSharp.Extensions.JsonRpc.RequestRouterBase`1[TDescriptor].<RouteRequest>g__InnerRoute|5_0 (Microsoft.Extensions.DependencyInjection.IServiceScopeFactory serviceScopeFactory, OmniSharp.Extensions.JsonRpc.Server.Request request, TDescriptor descriptor, System.Object params, System.Threading.CancellationToken token, Microsoft.Extensions.Logging.ILogger logger) [0x000fc] in <f52078c2a67749cdb3fc490a4675d4eb>:0
  at OmniSharp.Extensions.JsonRpc.RequestRouterBase`1[TDescriptor].RouteRequest (OmniSharp.Extensions.JsonRpc.IRequestDescriptor`1[TDescriptor] descriptors, OmniSharp.Extensions.JsonRpc.Server.Request request, System.Threading.CancellationToken token) [0x00622] in <f52078c2a67749cdb3fc490a4675d4eb>:0
  at OmniSharp.Extensions.JsonRpc.InputHandler+<>c__DisplayClass38_0.<RouteRequest>b__5 (System.Threading.CancellationToken ct) [0x000f2] in <f52078c2a67749cdb3fc490a4675d4eb>:0  | Method='initialize' RequestId='1'

both mono and the dotnet 6 sdk are installed:
dotnet --info
.NET SDK (reflecting any global.json):
 Version:   6.0.105
 Commit:    1c35735293

Runtime Environment:
 OS Name:     fedora
 OS Version:  36
 OS Platform: Linux
 RID:         fedora.36-x64
 Base Path:   /usr/lib64/dotnet/sdk/6.0.105/

Host (useful for support):
  Version: 6.0.5
  Commit:  70ae3df4a6

.NET SDKs installed:
  6.0.105 [/usr/lib64/dotnet/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 6.0.5 [/usr/lib64/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 6.0.5 [/usr/lib64/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET runtimes or SDKs:
  https://aka.ms/dotnet-download

mono --version
Mono JIT compiler version <IP_ADDRESS> (tarball Thu Jan 20 20:34:53 UTC 2022)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
	TLS:           __thread
	SIGSEGV:       altstack
	Notifications: epoll
	Architecture:  amd64
	Disabled:      none
	Misc:          softdebug
	Interpreter:   yes
	LLVM:          supported, not enabled.
	Suspend:       hybrid
	GC:            sgen (concurrent by default)

running omnisharp from the command line results in the same behaviour.

this seems to be a problem with emacs lsp-mode default installation for omnisharp
using the latest net6.0 build works fine via cli.
just to clarify: the correct way to run the net6.0 build is via dotnet runtime (dotnet OmniSharp.dll), right?

Further investigations:
setting the lsp-emacs download url (which defaults to the normal release instead of the net6 one) to the net6 release sadly did not resolve the issue.
It seems that lsp-emacs tries to start the run binary, which throws Cannot open assembly './OmniSharp.exe': No such file or directory., which can be confirmed on the cli.
Both the OmniSharp binary and dotnet OmniSharp.dll work though.
Lsp-emacs also allows setting a binary path. Setting this to the OmniSharp binary works and resolves my original issue.


SHA-1 Weak Authentication Algorithm vulnerability in dependency "request"

Our customer reported a vulnerability in bluemix-autoscaling-agent caused by "request" package.
The vulnerability reports that
"The request package is vulnerable to Weak Authentication Algorithm. The function function in oauth.js uses SHA-1 for authentication which is no longer considered cryptographically secure."
Here is the hierarchy of the "request" module tracking back to appmetrics
"request" --> "ibmapm-restclient" --> "ibmapm-embed" --> "appmetrics" --> bluemix-autoscaling-agent
According to request/request#2640 it looks like all versions of request are vulnerable and the request package is deprecated.
Can you please take a look? Any plan to replace it?  thanks,

Hi,  Can anyone help to check this issue? thanks,

Hi,  Can anyone help to check this issue? thanks,

@aqan213 Hi, the request package has been deprecated, so we can't resolve the issue by upgrade the request package simply.
I checked the recommend package in issue https://github.com/request/request/issues/3143, I think we have to do lots of development and testing effort if we plan to replace the request package with one of alternative libraries. And now DC team has some more high priority work to complete asap.
I will address this issue and try to resolve it when the high priority work done.

@aqan213 Hi, the request package has been deprecated, so we can't resolve the issue by upgrade the request package simply.
I checked the recommend package in issue https://github.com/request/request/issues/3143, I think we have to do lots of development and testing effort if we plan to replace the request package with one of alternative libraries. And now DC team has some more high priority work to complete asap.
I will address this issue and try to resolve it when the high priority work done.

thanks for the update. The customer is supposed to fix it in Feb. Is it possible to address this issue asap or can you please give  us a date when you plan to do it? thanks,

thanks for the update. The customer is supposed to fix it in Feb. Is it possible to address this issue asap or can you please give  us a date when you plan to do it? thanks,

I think we have to postpone this issue fix to 2Q.

I think we have to postpone this issue fix to 2Q.


Move local_assets to std/assets/local

Changes

Package module std/local_assets has been moved to std/assets/local.

Migration steps

Replace @fartlabs/jsonx/std/local_assets imports with @fartlabs/jsonx/std/assets/local.

Future work: std/assets/remote.


Add Splashtop to the remote-admin definitions.

Which category is the feature part of?

[x] Definition File

Use Cases
Add Splashtop to the remote-admin definitions.
Proposal
       "process_name": ["srmanager.exe",
                        "strwinclt.exe"]
   }```.

**Additional context**
Add any other context or screenshots about the feature request here.

Splashtop entry added via PR #63


⚠ ClamAV has degraded performance

In 11bbf97, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 466 ms

Resolved: ClamAV performance has improved in 4403240.


Add CONTRIBUTING.md

In a project this big having no commit message format could lead to diverse styles for messages which makes it harder to read and search the commit history. Also, since this is a monorepo, dividing it into components (scopes) and signifying what part of the repo the commit relates to in a unified way could be really helpful.
I propose the following git message conventions: https://karma-runner.github.io/6.4/dev/git-commit-msg.html
The only icky part is the build type, it's recent and in previous versions it was chore. Many automated up-keep solutions for code still use the chore type (ex: Renovate). But that is a minor inconvenience, these conventions are used by many developers and git bots.

There are many variations on the basic semantic commit message conventions, such as versions supporting emoji: https://gist.github.com/alpteo/e93d754e5e09907c6362c4230fb66f87
Or versions that use only the emoji for types: https://gitmoji.dev/ (giant list btw)
GitMoji integration etc: https://dev.to/javidjms/git-write-better-commits-with-gitmoji-3193

Great question, so on draft PRs like #2 you can see that i have committed a bunch of commits with random names. Before I merge this PR I will squash all the commits into a single commit and then do a merge on master (not a squash merge)
So while we are developing a PR the commit names dont need to be anything special. Once we are ready to merge and we squash the commits into a single commit. We should in the commit title briefly mention what the commit does and then in the commit body we should reference the tickets from https://github.com/orgs/ScuffleTV/projects/1
For example when the first PR gets merged
it will look like
Added documentation and flow charts
#1

Currently I am trying out using github projects. I dont know how good it is or if its actually useful if it isnt ill just switch to JIRA or some other project management tool.

This all sounds like it needs to be documented in CONTRIBUTION.md, perhaps a  task for later.
Just want to mention, the all scope seems redundant, IMO it's much better to omit the parenthesis all together if the scope is too big or undecidable.

There is a script when making change logs which looks for tag(scope) syntax not sure if it works without the scope part. Which is why I put it there. And yeah that sounds good ill make a ticket for it and repurpose this issue.

Closed in favour of the ticked issue.

I suggest looking into commitizen


[solution] can we accept wild cards in for-type

I need to define build types for my project that do not depend only on the compiler:
  build-types:
    - type: AC6_UART
      compiler: AC6
      misc:
        - C*:
          - -std=c99
    - type: GCC_UART
      compiler: GCC
      misc:
        - C*:
          - -std=c99
    - type: IAR_UART
      compiler: IAR
      misc:
        - C*:
          - -std=c99
    - type: AC6_ITM
      compiler: AC6
      misc:
        - C*:
          - -std=c99
    - type: GCC_ITM
      compiler: GCC
      misc:
        - C*:
          - -std=c99
    - type: IAR_ITM
      compiler: IAR
      misc:
        - C*:
          - -std=c99

So basically, it is compiler_function where function is either UART or ITM.
I tried this:
    - group: Simple Trace
      files:
        - file: ../Src/stm32_simple_trace_UART.c
          for-type: *_UART
        - file: ../Src/stm32_simple_trace_ITM.c
          for-type: *_ITM

But got this error:
> csolution.exe list dependencies -s test.csolution.yml
C:/Cube/simple_trace/internal/test.cproject.yml:29:21 - error csolution: yaml-cpp: error at line 29, column 21: the referenced anchor is not defined: _UART

https://github.com/Open-CMSIS-Pack/devtools/blob/main/tools/projmgr/docs/Manual/YML-Format.md#add-paths
Have you tried:  .*_UART
The . is indicating that this is a build type vs. + indicating that this is a target type.
Otherwise you need to specify a comma separated list (see documentation).

Wildcards are not accepted in for-types and not-for-types:
https://github.com/Open-CMSIS-Pack/devtools/blob/main/tools/projmgr/docs/Manual/YML-Format.md#buildtarget-type-control

is it something that may be added ?

I suggest to focus the energy on essential functionality as otherwise we can get easily distracted. That said, if you are volunteering to contribute the implementation and the extended tests I cannot see why this would not be accepted.

The semantics around for-type and not-for-type are already very complex (consider how the inclusion of files in groups are managed for an example). I would definitely not be in favour of making this any more complicated.

I would investigate this a little later (realistic Q3'22).  However in general it seems a good idea.

I suggest we keep the current behavior as the tool has already some complexity.  Willing to investigate at a later point in time (after we a IDE integration completed).


Bug: log full stack trace on error

Summary
We are currently not logging the stack track when an exception is caught.  This should be fixed to make troubleshooting easier.

This is now fixed in prod.


add strict module layout rule

This gives us a consistent layout for the top of a module, we are using the default order provided by credo.
      defmodule MyMod do
        @moduledoc "moduledoc"
        use Foo
        import Bar
        alias Baz
        require Qux
      end

Codecov Report

Merging #387 (322cbcb) into master (dc09328) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #387   +/-   ##
=======================================
  Coverage   77.06%   77.06%
=======================================
  Files          33       33
  Lines         484      484
=======================================
  Hits          373      373
  Misses        111      111

Impacted Files
Coverage Δ

lib/shopify_api/app.ex
88.88% <ø> (ø)

lib/shopify_api/bulk/cancel.ex
0.00% <ø> (ø)

lib/shopify_api/conn_helpers.ex
87.50% <ø> (ø)

lib/shopify_api/graphql.ex
78.12% <ø> (ø)

lib/shopify_api/graphql/telemetry.ex
100.00% <ø> (ø)

lib/shopify_api/plugs/admin_authenticator.ex
81.81% <ø> (ø)

lib/shopify_api/plugs/webhook.ex
80.00% <ø> (ø)

lib/shopify_api/rate_limiting/graphql_tracker.ex
80.00% <ø> (ø)

lib/shopify_api/rate_limiting/rest_tracker.ex
91.66% <ø> (ø)

lib/shopify_api/rest/checkout.ex
0.00% <ø> (ø)

... and 3 more

Continue to review full report at Codecov.

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


It keeps reporting using uninitialized variables before training started

I launch the training using the command
python3 tools/train_lanenet.py --net vgg --dataset_dir data_path/tusimple/from_zips/training/ -m 0

Then I got the following error:
It says I have variables uninitialized. But I didn't make any change to the training code. I double check the code and there is sess.run(init) which shall initialize all variables.
What's wrong with it?

2020-04-20 12:18:36.205370: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1392] Found device 0 with properties:
name: Tesla V100-PCIE-16GB major: 7 minor: 0 memoryClockRate(GHz): 1.38
pciBusID: 0000:35:00.0
totalMemory: 15.77GiB freeMemory: 15.36GiB
2020-04-20 12:18:36.981516: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1392] Found device 1 with properties:
name: Tesla V100-PCIE-16GB major: 7 minor: 0 memoryClockRate(GHz): 1.38
pciBusID: 0000:39:00.0
totalMemory: 15.77GiB freeMemory: 15.36GiB
2020-04-20 12:18:36.983067: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1471] Adding visible gpu devices: 0, 1
2020-04-20 12:18:37.690751: I tensorflow/core/common_runtime/gpu/gpu_device.cc:952] Device interconnect StreamExecutor with strength 1 edge matrix:
2020-04-20 12:18:37.690795: I tensorflow/core/common_runtime/gpu/gpu_device.cc:958]      0 1
2020-04-20 12:18:37.690805: I tensorflow/core/common_runtime/gpu/gpu_device.cc:971] 0:   N Y
2020-04-20 12:18:37.690812: I tensorflow/core/common_runtime/gpu/gpu_device.cc:971] 1:   Y N
2020-04-20 12:18:37.691712: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1084] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 15344 MB memory) -> physical GPU (device: 0, name: Tesla V100-PCIE-16GB, pci bus id: 0000:35:00.0, compute capability: 7.0)
2020-04-20 12:18:37.693032: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1084] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:1 with 15344 MB memory) -> physical GPU (device: 1, name: Tesla V100-PCIE-16GB, pci bus id: 0000:39:00.0, compute capability: 7.0)
I0420 12:18:49.695656 102048 train_lanenet.py:668] Training from scratch
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/client/session.py", line 1322, in _do_call
    return fn(*args)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/client/session.py", line 1307, in _run_fn
    options, feed_dict, fetch_list, target_list, run_metadata)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/client/session.py", line 1409, in _call_tf_sessionrun
    run_metadata)
tensorflow.python.framework.errors_impl.FailedPreconditionError: Attempting to use uninitialized value lanenet_model/vgg_frontend/vgg16_encode_module/conv5_2_instance/conv/W
         [[Node: lanenet_model/vgg_frontend/vgg16_encode_module/conv5_2_instance/conv/W/read = Identity[T=DT_FLOAT<EMAIL_ADDRESS>_device="/job:localhost/replica:0/task:0/device:GPU:0"](lanenet_model/vgg_frontend/vgg16_encode_module/conv5_2_instance/conv/W)]]

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "tools/train_lanenet.py", line 750, in <module>
    train_lanenet_multi_gpu(args.dataset_dir, args.weights_path, net_flag=args.net_flag)
  File "tools/train_lanenet.py", line 670, in train_lanenet_multi_gpu
    sess.run(init)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/client/session.py", line 900, in run
    run_metadata_ptr)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/client/session.py", line 1135, in _run
    feed_dict_tensor, options, run_metadata)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/client/session.py", line 1316, in _do_run
    run_metadata)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/client/session.py", line 1335, in _do_call
    raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.FailedPreconditionError: Attempting to use uninitialized value lanenet_model/vgg_frontend/vgg16_encode_module/conv5_2_instance/conv/W
         [[Node: lanenet_model/vgg_frontend/vgg16_encode_module/conv5_2_instance/conv/W/read = Identity[T=DT_FLOAT<EMAIL_ADDRESS>_device="/job:localhost/replica:0/task:0/device:GPU:0"](lanenet_model/vgg_frontend/vgg16_encode_module/conv5_2_instance/conv/W)]]

Caused by op 'lanenet_model/vgg_frontend/vgg16_encode_module/conv5_2_instance/conv/W/read', defined at:
  File "tools/train_lanenet.py", line 750, in <module>
    train_lanenet_multi_gpu(args.dataset_dir, args.weights_path, net_flag=args.net_flag)
  File "tools/train_lanenet.py", line 585, in train_lanenet_multi_gpu
    train_images, train_binary_labels, train_instance_labels, train_net, optimizer
  File "tools/train_lanenet.py", line 233, in compute_net_gradients
    instance_label=gt_instance_labels, name='lanenet_model'
  File "mypath/lanenet-lane-detection-master/lanenet_model/lanenet.py", line 82, in compute_loss
    reuse=self._reuse
  File "mypath/lanenet-lane-detection-master/lanenet_model/lanenet_front_end.py", line 43, in build_model
    reuse=reuse
  File "mypath/lanenet-lane-detection-master/semantic_segmentation_zoo/vgg16_based_fcn.py", line 357, in build_model
    self._vgg16_fcn_encode(input_tensor=input_tensor, name='vgg16_encode_module')
  File "mypath/lanenet-lane-detection-master/semantic_segmentation_zoo/vgg16_based_fcn.py", line 253, in _vgg16_fcn_encode
    need_layer_norm=True
  File "mypath/lanenet-lane-detection-master/semantic_segmentation_zoo/vgg16_based_fcn.py", line 63, in _vgg16_conv_stage
    use_bias=False, padding=pad, name='conv'
  File "mypath/lanenet-lane-detection-master/semantic_segmentation_zoo/cnn_basenet.py", line 70, in conv2d
    w = tf.get_variable('W', filter_shape, initializer=w_init)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/ops/variable_scope.py", line 1328, in get_variable
    constraint=constraint)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/ops/variable_scope.py", line 1090, in get_variable
    constraint=constraint)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/ops/variable_scope.py", line 435, in get_variable
    constraint=constraint)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/ops/variable_scope.py", line 404, in _true_getter
    use_resource=use_resource, constraint=constraint)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/ops/variable_scope.py", line 796, in _get_single_variable
    use_resource=use_resource)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/ops/variable_scope.py", line 2234, in variable
    use_resource=use_resource)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/ops/variable_scope.py", line 2224, in <lambda>
    previous_getter = lambda **kwargs: default_variable_creator(None, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/ops/variable_scope.py", line 2207, in default_variable_creator
    constraint=constraint)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/ops/variables.py", line 259, in __init__
    constraint=constraint)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/ops/variables.py", line 422, in _init_from_args
    self._snapshot = array_ops.identity(self._variable, name="read")
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/ops/array_ops.py", line 79, in identity
    return gen_array_ops.identity(input, name=name)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/ops/gen_array_ops.py", line 3263, in identity
    "Identity", input=input, name=name)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/framework/op_def_library.py", line 787, in _apply_op_helper
    op_def=op_def)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/framework/ops.py", line 3414, in create_op
    op_def=op_def)
  File "/usr/local/lib/python3.5/dist-packages/tensorflow/python/framework/ops.py", line 1740, in __init__
    self._traceback = self._graph._extract_stack()  # pylint: disable=protected-access

FailedPreconditionError (see above for traceback): Attempting to use uninitialized value lanenet_model/vgg_frontend/vgg16_encode_module/conv5_2_instance/conv/W
         [[Node: lanenet_model/vgg_frontend/vgg16_encode_module/conv5_2_instance/conv/W/read = Identity[T=DT_FLOAT<EMAIL_ADDRESS>_device="/job:localhost/replica:0/task:0/device:GPU:0"](lanenet_model/vgg_frontend/vgg16_encode_module/conv5_2_instance/conv/W)]]

@FCInter It's werid seeing this. Maybe something different with my local TensorFlow environment. I think that problem should not exist if tensorflow 1.12 was used by you:)

@FCInter Besides there is a little bug which I have got enough spare time to fix in multi gpu trainner. The single gpu trainner was prefered:）

@MaybeShewill-CV Thx. Yes the reason is that I'm using a very old tf .19, limited by the server I'm using... Do you have any idea to fix this? I think this shall be simply replacing some codes with those supported by older versions of TF. I kept searching for a whole day but got nothing...

@FCInter I think the problem should not exist even in tf 1.9. You may debug to see if the sess.run(tf.global_variables_initializer()) was exactly excuted. Make sure the single gpu trainner was used here:)


Fix logical error in TimePickerDialog - the RenderObject forgets to update fields

Close #112038. Please see description there.
If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

would be good to have a test for this.

Ahh my bad, I should have asked for a test for this one

@Hixie I have tried but failed, that is why this one has no tests though others have :/ It is so deep that it is hard to construct a test, without relaxing the code visibility of the widget/renderobjects.

@Hixie So shall I relax the code visibility of the widgets and render objects (i.e. change from private to public) in order to have a test?

Tests can actually get to the private classes, they just can't use the private class name. You can cast the render object to dynamic and can call things on it blindly.

@Hixie Thanks, but the problem is I cannot construct a _CupertinoDialogRenderWidget object. All its current usages does not cause this bug (but future usages may do), while this is a logical bug indeed (since by definition updateRenderObject should update the fields).

Ah, I see. Yeah, that's unfortunate. Probably fine to skip the test for now then.
test-exempt: not technically changing actual behaviour.


Is there a way to persist token cache?

This is great, however as long as I understand there is no way to persist token cache externally, it's kept in memory and on application restart we need to authenticate again. For UI based applications it won't be acceptable. Can you recommend a way or point me in the direction of how to persist the token cache?

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

ID: ad0ed2dc-fd93-c2e2-ecc7-0a1f7ce10c62
Version Independent ID: 44070167-c751-c3da-b787-0240850690f4
Content: Authenticate with the Azure libraries for .NET - Azure for .NET Developers
Content Source: docs-ref-conceptual/dotnet-sdk-azure-authenticate.md
Service: multiple
GitHub Login: @CamSoper
Microsoft Alias: casoper

@aloneguid The token credentials method? Or file?

I'm particulary interested in Device Flow method where user logs in interactively. I can't ask the user to do it on every application restart.

Gotcha.
This doc has been on my list of docs to expand for a while and that scenario is on the list. Unfortunately, I don't know much about it off the top of my head.
Which service(s) are you providing access to? I'll try to do some research and let you know what I've found.


(BKR-1004) beaker exec implementation

These changes introduce new subcommand functionality for beaker; the
exec subcommand takes a file, directory, or beaker suite name and
launches beaker to test that resource specifically. If no resource is
specified, it reads in default configuration that should already be set
up by previous subcommands.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/3636/

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/3638/

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/3678/

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/3679/

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/3684/


Updated python packages to fix some CEV issues.

Updated python packages to fix some CEV issues.
Removed some old un-used code for old BDS scans
Updated licenses and documentation

/azp run

/azp run


Fix query scoping in dev workspace

@hughess why is this change needed?

@ItsMeBrianD there are 2 orders tables available in the schema - 1 in needful_things and 1 in ecommerce. It seems to pick up needful things initially, but will switch to ecommerce and error out unpredictably. In another PR, the deployment preview was showing a broken page as a result

@ItsMeBrianD this seems to happen on the dropdown page in the dev workspace project as well


Compiling from source

I am trying to compile tensorflow from source as the pip version is compiled on older version of cuDNN
System information

**OS Platform and Distribution ** : Linux Ubuntu 16.04
TensorFlow installed from source:
TensorFlow version (use command below):
Python version: 2.7
Bazel version (if compiling from source):  Build label: 0.5.3
CUDA/cuDNN version: CUDA 8, cuDNN 7.0.1
GPU model and memory: GTX 1080 Ti and VRAM 11GB, RAM 32 GB
Exact command to reproduce:
Trying to compile with   :  https://www.tensorflow.org/install/install_sources

Describe the problem
Unable to compile from source. I tried the binary but it uses an old version of cuDNN I am using 7.0.1
Source code / logs
ERROR: /home/ntweat/tensorflow/tensorflow/stream_executor/BUILD:39:1: C++ compilation of rule '//tensorflow/stream_executor:cuda_platform' failed (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command
(exec env -
CUDA_TOOLKIT_PATH=/usr/local/cuda
CUDNN_INSTALL_PATH=/usr/local/cuda-8.0
GCC_HOST_COMPILER_PATH=/usr/bin/gcc
PWD=/proc/self/cwd
PYTHON_BIN_PATH=/usr/bin/python2.7
PYTHON_LIB_PATH=/usr/local/lib/python2.7/dist-packages
TF_CUDA_CLANG=0
TF_CUDA_COMPUTE_CAPABILITIES=6.1
TF_CUDA_VERSION=8.0
TF_CUDNN_VERSION=7.0.1
TF_NEED_CUDA=1
TF_NEED_OPENCL=0 \

@Ntweat Please include the full error log

Hi
It was issue with cuDNN, I think Tensorflow does not work with cuDNN 7.
I downgraded cuDNN to v6 and it compiled without any issues.

Ah yes, please see #12052 for the cuDNN 7 status

Thank you 👍  I will look out for updates on cuDNN 7


Allow to login with a (known) API key instead of going through github oauth

Primarily to facilitate automated testing/interaction with webui, originally came up in https://github.com/dandi/dandi-api-webshots/issues/1 for which we had to move webshots to be done on a dedicated in-house box (drogon) with persistent device id.
The question came back while discussing automating figures/webshots for documentation.

transferred to dandiarchuve.
one way of doing this is to allow it as a parameter for the Vue app: httpurl/?api_key=<apikey>
vue can store this value directly and use it internally for all operations. this will bypass the need for changing the login process and allows a quick injection of the api key into the client.

I'd like to offer a solution to the problem of automated testing login that will not require engineering a new feature solely to support that corner case. Here's a procedure to illustrate it (initially designed and tested by @dchiquito):

Open an incognito browser window.
Navigate to https://api-staging.dandiarchive.org/admin/.
Log in with username<EMAIL_ADDRESS>and the right password (talk to Roni to get it).
Navigate to https://gui-staging.dandiarchive.org/.
Click on the "login with github" button.
Wait to be redirected back to the front page.

You are now logged into the web app without having to use an API key or Github credentials. (A note: the interstitial "authorize dandi?" page that sometimes appeared between steps 5 and 6 has now been disabled, which specifically makes this procedure more reliable than before.)
Note that all steps above are possible to automate. Any solution involving API keys would require a similar amount of automation, but a lot of extra engineering to support a relatively heavy feature that would only be useful for this specific use case.
Please let me know if this approach to automated logins will be sufficient--specifically, I'd like to know the ways in which it is inadequate to current needs.

@waxlamp - we need this for generating webshots of actual dandisets. so this is not testing per se, but snapshots of the archive itself in production.

@waxlamp - we need this for generating webshots of actual dandisets. so this is not testing per se, but snapshots of the archive itself in production.

The procedure Daniel cooked up should enable this use case though, right?

The procedure Daniel cooked up should enable this use case though, right?

as long as it can work on the main api server. sorry, if i misread this as only working with staging.

Yes, it should work on production as well. The procedure was aimed at staging since that's where it's safe to play without a hazmat suit on, etc.


Error message for <IP_ADDRESS>.e should say FAIL:

From j1939-84 created by ericthomasswenson: Equipment-and-Tool-Institute/j1939-84#1162
Error message for <IP_ADDRESS>.e should say FAIL:
D       1  SPN 7353 - Engine Exhaust 1 Corrected Nox
D   T   1  SPN 7393 - AFT 1 Particulate Sensor Current
D       2  SPN 12750 - AFT 1 SCR 1 Engine Exhaust NOx Mass Flow
D       2  SPN 12751 - AFT 1 SCR 1 Tailpipe NOx Mass Flow
]
FAIL: <IP_ADDRESS>.d - SP 12675 is not included in DM24 response from Engine #1 (0)
/* NOx Tracking Engine Activity Lifetime Fuel Consumption Bins (64258)
WARN: <IP_ADDRESS>.e - SP 12730 is not included in DM24 response from Engine #1 (0)
/* GHG Tracking Lifetime Engine Run Time (64252)
WARN: <IP_ADDRESS>.f - SP 12691 is not included in DM24 response from Engine #1 (0)
/* GHG Tracking Lifetime Active Technology Index (64257)

Previously fixed:


Add Check zone peers to Subscription.json

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

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[x] update existing version to fix swagger quality issue in s360

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.

Feature is already publicly available

When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[x] No refresh required for updates in this PR

Contribution checklist:

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

ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.

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

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

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

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

/azp run

@tjegbejimba , please fix CI check failures.

@tjegbejimba  there are redundant definition for  ErrorResponse - https://github.com/Azure/azure-rest-api-specs/blob/7501f28247d0bf65ff6f7dfdbcbf5aa37fe683ef/specification/resources/resource-manager/Microsoft.Resources/stable/2021-01-01/subscriptions.json#L270, suggest to use the one in common types

@tjegbejimba there are redundant definition for ErrorResponse -
https://github.com/Azure/azure-rest-api-specs/blob/7501f28247d0bf65ff6f7dfdbcbf5aa37fe683ef/specification/resources/resource-manager/Microsoft.Resources/stable/2021-01-01/subscriptions.json#L270
, suggest to use the one in common types

As my code change does not include those error responses, could we make that fix next time?

/azp run

@msyyc , can you have a look at the python track2 failures?


[Support] connection timeout after setup

In raising this issue, I confirm the following:
{please fill the checkboxes, e.g: [X]}

[X] I have read and understood the contributors guide.
[X] The issue I am reporting can be replicated.
[] The issue I am reporting can be is directly related to the pivpn installer script.
[] The issue I am reporting isn't a duplicate (see FAQs, closed issues, and open issues).

Issue
after setup (listening to domain which is configured via dyndns to the router) android OpenVPN connect app gets to timeout.
Have you searched for similar issues and solutions?
(yes/no / which issues?)

pivpn -d got an error like https://bbs.archlinux.org/viewtopic.php?id=163377, reboot helped, but didn't solve timeout
Console output of      curl -L install.pivpn.dev | bash
 I won't install pivpn dev - I've installed the normal one.

Console output of      pivpn add or pivpn add nopass
pivpn add
Enter a Name for the Client:

Console output of      pivpn debug
pi@$hostname:~ $ pivpn debug
::: Generating Debug Output
::::            PiVPN debug              ::::
=============================================
::::            Latest commit            ::::
commit 443ef51e293a1aaca57cf1f8505a5328ac148fda
Author: Orazio<EMAIL_ADDRESS>Date:   Wed Nov 4 11:45:36 2020 +0100

    Update LatestUpdate.md
=============================================
::::        Installation settings        ::::
PLAT=Raspbian
OSCN=buster
USING_UFW=0
IPv4dev=eth0
dhcpReserv=1
IPv4addr=<IP_ADDRESS>/24
IPv4gw=<IP_ADDRESS>
install_user=pi
install_home=/home/pi
VPN=openvpn
pivpnPROTO=udp
pivpnPORT=1194
pivpnDNS1=<IP_ADDRESS>
pivpnDNS2=<IP_ADDRESS>
pivpnSEARCHDOMAIN=
pivpnHOST=REDACTED
TWO_POINT_FOUR=0
pivpnENCRYPT=2048
USE_PREDEFINED_DH_PARAM=1
INPUT_CHAIN_EDITED=1
FORWARD_CHAIN_EDITED=1
pivpnDEV=tun0
pivpnNET=<IP_ADDRESS>
subnetClass=24
UNATTUPG=1
INSTALLED_PACKAGES=(dnsutils iptables-persistent openvpn grepcidr expect unattended-upgrades)
HELP_SHOWN=1
=============================================
::::  Server configuration shown below   ::::
dev tun
proto udp
port 1194
ca /etc/openvpn/easy-rsa/pki/ca.crt
cert /etc/openvpn/easy-rsa/pki/issued/raspberrypi_b301a2ba-01b8-4ca3-b0b4-97d6f69a07e2.crt
key /etc/openvpn/easy-rsa/pki/private/raspberrypi_b301a2ba-01b8-4ca3-b0b4-97d6f69a07e2.key
dh /etc/openvpn/easy-rsa/pki/dh2048.pem
topology subnet
server <IP_ADDRESS> <IP_ADDRESS>
# Set your primary domain name server address for clients
push "dhcp-option DNS <IP_ADDRESS>"
push "dhcp-option DNS <IP_ADDRESS>"
# Prevent DNS leaks on Windows
push "block-outside-dns"
# Override the Client default gateway by using <IP_ADDRESS>/1 and
# <IP_ADDRESS>/1 rather than <IP_ADDRESS>/0. This has the benefit of
# overriding but not wiping out the original default gateway.
push "redirect-gateway def1"
client-to-client
client-config-dir /etc/openvpn/ccd
keepalive 15 120
remote-cert-tls client
tls-version-min 1.2
tls-auth /etc/openvpn/easy-rsa/pki/ta.key 0
cipher AES-256-CBC
auth SHA256
user openvpn
group openvpn
persist-key
persist-tun
crl-verify /etc/openvpn/crl.pem
status /var/log/openvpn-status.log 20
status-version 3
syslog
verb 3
#DuplicateCNs allow access control on a less-granular, per user basis.
#Remove # if you will manage access by user instead of device.
#duplicate-cn
# Generated for use by PiVPN.io
=============================================
::::  Client template file shown below   ::::
client
dev tun
proto udp
remote REDACTED 1194
resolv-retry infinite
nobind
key-direction 1
remote-cert-tls server
tls-version-min 1.2
verify-x509-name raspberrypi_b301a2ba-01b8-4ca3-b0b4-97d6f69a07e2 name
cipher AES-256-CBC
auth SHA256
auth-nocache
verb 3
=============================================
::::    Recursive list of files in       ::::
::: /etc/openvpn/easy-rsa/pki shows below :::
/etc/openvpn/easy-rsa/pki/:
ca.crt
crl.pem
Default.txt
dh2048.pem
index.txt
index.txt.attr
index.txt.attr.old
index.txt.old
issued
Konstantin.ovpn
openssl-easyrsa.cnf
private
renewed
revoked
safessl-easyrsa.cnf
serial
serial.old
ta.key

/etc/openvpn/easy-rsa/pki/issued:
Konstantin.crt
raspberrypi_b301a2ba-01b8-4ca3-b0b4-97d6f69a07e2.crt

/etc/openvpn/easy-rsa/pki/private:
ca.key
Konstantin.key
raspberrypi_b301a2ba-01b8-4ca3-b0b4-97d6f69a07e2.key

/etc/openvpn/easy-rsa/pki/renewed:
private_by_serial
reqs_by_serial

/etc/openvpn/easy-rsa/pki/renewed/private_by_serial:

/etc/openvpn/easy-rsa/pki/renewed/reqs_by_serial:

/etc/openvpn/easy-rsa/pki/revoked:
private_by_serial
reqs_by_serial

/etc/openvpn/easy-rsa/pki/revoked/private_by_serial:

/etc/openvpn/easy-rsa/pki/revoked/reqs_by_serial:
=============================================
::::            Self check               ::::
:: [OK] IP forwarding is enabled
:: [OK] Iptables MASQUERADE rule set
:: [OK] Iptables INPUT rule set
:: [OK] Iptables FORWARD rule set
:: [OK] OpenVPN is running
:: [OK] OpenVPN is enabled (it will automatically start on reboot)
:: [OK] OpenVPN is listening on port 1194/udp
=============================================
:::: Having trouble connecting? Take a look at the FAQ:
:::: https://github.com/pivpn/pivpn/wiki/FAQ
=============================================
::::      Snippet of the server log      ::::
Nov 29 14:59:36 $hostname ovpn-server[456]: IFCONFIG POOL: base=<IP_ADDRESS> size=252, ipv6=0
Nov 29 14:59:36 $hostname ovpn-server[456]: Initialization Sequence Completed
Nov 29 15:16:56 $hostname ovpn-server[504]: OpenVPN 2.4.7 arm-unknown-linux-gnueabihf [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 20 2019
Nov 29 15:16:56 $hostname ovpn-server[504]: library versions: OpenSSL 1.1.1d  10 Sep 2019, LZO 2.10
Nov 29 15:16:56 $hostname ovpn-server[504]: Diffie-Hellman initialized with 2048 bit key
Nov 29 15:16:56 $hostname ovpn-server[504]: Outgoing Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
Nov 29 15:16:56 $hostname ovpn-server[504]: Incoming Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
Nov 29 15:16:56 $hostname ovpn-server[504]: TUN/TAP device tun0 opened
Nov 29 15:16:56 $hostname ovpn-server[504]: TUN/TAP TX queue length set to 100
Nov 29 15:16:56 $hostname ovpn-server[504]: /sbin/ip link set dev tun0 up mtu 1500
Nov 29 15:16:56 $hostname ovpn-server[504]: /sbin/ip addr add dev tun0 <IP_ADDRESS>/24 broadcast <IP_ADDRESS>
Nov 29 15:16:56 $hostname ovpn-server[504]: Could not determine IPv4/IPv6 protocol. Using AF_INET
Nov 29 15:16:56 $hostname ovpn-server[504]: Socket Buffers: R=[180224->180224] S=[180224->180224]
Nov 29 15:16:56 $hostname ovpn-server[504]: UDPv4 link local (bound): [AF_INET][undef]:1194
Nov 29 15:16:56 $hostname ovpn-server[504]: UDPv4 link remote: [AF_UNSPEC]
Nov 29 15:16:56 $hostname ovpn-server[504]: GID set to openvpn
Nov 29 15:16:56 $hostname ovpn-server[504]: UID set to openvpn
Nov 29 15:16:56 $hostname ovpn-server[504]: MULTI: multi_init called, r=256 v=256
Nov 29 15:16:56 $hostname ovpn-server[504]: IFCONFIG POOL: base=<IP_ADDRESS> size=252, ipv6=0
Nov 29 15:16:56 $hostname ovpn-server[504]: Initialization Sequence Completed
=============================================
::::            Debug complete           ::::
:::
::: Debug output completed above.
::: Copy saved to /tmp/debug.log
:::
pi@$hostname:~ $

Have you taken any steps towards solving your issue?
  which?
1. first pivpn -d got some iptables questions, said -y to all of them
2. second pivpn -d got "OpenVPN 2.3.1 - ERROR: Cannot open TUN/TAP dev /dev/net/tun" - solved by rebooting according to https://bbs.archlinux.org/viewtopic.php?id=163377
3. port forwarding is shown as active on the AVM Fritzbox
4. router reboot

- if an external DynDNS is adding a domain to a dynamic external IP, does Pivpn need to listen to it's localhost or its internal IP or to the domain configured by DynDNS?
The router forwards the port to the internal IP, so I'm unsure because this port is resolved in the WWW with an rDNS.

sorry for the quick reply. Github formats output much nicer. checking Port forwarding now. Remembered having forwarded TCP...

resolution: Port forwarding set wrong in router config


Workshop topics

Hello! @smoya and I have opened this issue so that to know opinions about the workshops. We want to create these seminars to introduce AsyncAPI to potential users and improve the knowledge of people who already know the specification and want to improve it.
For this, we need the opinion of the community especially on these points:

To which communities we can offer the workshops.
Companys or groups that might be interested in this.
Themes that would be interesting for these workshops.
And anything else you can think of regarding the workshops.

Here is the summary document of the information we have collected so far on the workshops: https://docs.google.com/document/d/1qfDGhRI07vO6ZydYYRFRk6B9PyYr2oUU/edit#heading=h.gjdgxs
Feel free to post your interests :)

Done :)

@all-contributors please add @Barbanio for eventOrganizing, ideas

@all-contributors please add @SIHAM TAHI for review

@all-contributors please add @Sihamtahi for review


Multi-language

I hope more languages will be released

This is something I'd like to add. However, it will require crowd sourcing efforts to help me translate as I only speak English..

You can actually use the help of deepl.com, I'm from China and I feel it's very accurate.
After the first edition is published, we can give feedback about the problems in the translation, which saves a lot of time.
(Translated by deepl)


dockerfileNative task should mention graal annotation processor

Not sure if this should be on the task help output, a warning, or in the docs, but if you're using the micronaut openapi generation and a standalone docker file for your builds (our CI environment requires this), you have to update the resource-config.json for the resource files.
This is done automatically by the dockerBuildNative task by dynamically adding the micronaut-graal annotation processor, but was pretty challenging to figure out as a person new to graalvm.
The prerequisite to make things work as espected in standalone native-image dockerfile builds is to add the following annotation to your build.gradle:
annotationProcessor("io.micronaut:micronaut-graal:$micronautVersion")

Can you check if you still have the same problem with the latest release, and if so, share a minimal reproducer?


Why use a DaemonSet in Kubernetes?

Hi There,
Just curious why use a DaemonSet in Kubernetes. DaemonSet restarts the pumba pods once they complete. If you have a requirement to run a single/once off chaos test e.g. add 300ms delay for 5mins to container x, this means that after 5mins the pod will complete and will then be restarted by the DaemonSet, making it impossible to run a single/once off test.
So I guess there are 2 questions here:

Why use a DaemonSet?
Is there a way to avoid the scenario above? i.e. run the pod once and only once

Thanks in advance

@mzeljkovic there is a point in what you say. I'm thinking to make it a more K8s-friendly.
Currently, DaemonSet deployment does not suit your use case. Probably, you could use K8s Job with nodeSelector running it on specified nodes.

Thanks a million for the quick response @alexei-led


Enable setupOnly mode like the GitHub action.

I'd like to use the run-cmake task without the need for actually building anything in vcpkg. I still need to build vcpkg since run-cmake relies on vcpkg env so for now I'm building a package I don't need.

@cbezault last release contains support for run-vcpkg's setupOnly:true


UPNP port mapping not refreshed after router reboot

Home Assistant release with the issue:

0.100
Last working Home Assistant release (if known):
None or unknown
Operating environment (Hass.io/Docker/Windows/etc.):

hassio 2.12 on Raspberry Pie 3.0B+
Integration:

UPNP
Description of problem:
Using UPNP to set port forwarding on router works as expected initially.  However, if router is rebooted, HA does not refresh the port mapping.  As far as I can tell, the only way to fix is to restart HA.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

upnp:
  port_mapping: true
  ports:
    hass: 8123

Traceback (if applicable):

Additional information:
Note that other applications do not have this issue, such as Plex media server.

Dunno if this might be the same issue but my upnp platform (added by integrations) will fail after a while
Tue Nov 05 2019 19:04:56 GMT+0100 (Mitteleuropäische Normalzeit)
Update for sensor.rt_ac68u_bytes_sent fails
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 936, in _wrap_create_connection
    return await self._loop.create_connection(*args, **kwargs)  # type: ignore  # noqa
  File "/usr/local/lib/python3.7/asyncio/base_events.py", line 954, in create_connection
    raise exceptions[0]
  File "/usr/local/lib/python3.7/asyncio/base_events.py", line 941, in create_connection
    await self.sock_connect(sock, address)
  File "/usr/local/lib/python3.7/asyncio/selector_events.py", line 464, in sock_connect
    return await fut
  File "/usr/local/lib/python3.7/asyncio/selector_events.py", line 494, in _sock_connect_cb
    raise OSError(err, f'Connect call failed {address}')
ConnectionRefusedError: [Errno 111] Connect call failed ('<IP_ADDRESS>', 47779)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 270, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 448, in async_device_update
    await self.async_update()
  File "/usr/src/homeassistant/homeassistant/components/upnp/sensor.py", line 143, in async_update
    self._state = await self._device.async_get_total_bytes_sent()
  File "/usr/src/homeassistant/homeassistant/components/upnp/device.py", line 151, in async_get_total_bytes_sent
    return await self._igd_device.async_get_total_bytes_sent()
  File "/usr/local/lib/python3.7/site-packages/async_upnp_client/profiles/igd.py", line 99, in async_get_total_bytes_sent
    result = await action.async_call()
  File "/usr/local/lib/python3.7/site-packages/async_upnp_client/client.py", line 509, in async_call
    await self.service.requester.async_http_request('POST', url, headers, body)
  File "/usr/local/lib/python3.7/site-packages/async_upnp_client/client.py", line 70, in async_http_request
    body_type=body_type)
  File "/usr/local/lib/python3.7/site-packages/async_upnp_client/aiohttp.py", line 103, in async_do_http_request
    async with self._session.request(method, url, headers=headers, data=body) as response:
  File "/usr/local/lib/python3.7/site-packages/aiohttp/client.py", line 1012, in __aenter__
    self._resp = await self._coro
  File "/usr/local/lib/python3.7/site-packages/aiohttp/client.py", line 483, in _request
    timeout=real_timeout
  File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 523, in connect
    proto = await self._create_connection(req, traces, timeout)
  File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 859, in _create_connection
    req, traces, timeout)
  File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 1004, in _create_direct_connection
    raise last_exc
  File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 986, in _create_direct_connection
    req=req, client_error=client_error)
  File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 943, in _wrap_create_connection
    raise client_error(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host <IP_ADDRESS>:47779 ssl:None [Connect call failed ('<IP_ADDRESS>', 47779)]

Is there something I can do from the side of my router?

Dunno if this might be the same issue but my upnp platform (added by integrations) will fail after a while
Tue Nov 05 2019 19:04:56 GMT+0100 (Mitteleuropäische Normalzeit)
Update for sensor.rt_ac68u_bytes_sent fails
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 936, in _wrap_create_connection
    return await self._loop.create_connection(*args, **kwargs)  # type: ignore  # noqa
  File "/usr/local/lib/python3.7/asyncio/base_events.py", line 954, in create_connection
    raise exceptions[0]
  File "/usr/local/lib/python3.7/asyncio/base_events.py", line 941, in create_connection
    await self.sock_connect(sock, address)
  File "/usr/local/lib/python3.7/asyncio/selector_events.py", line 464, in sock_connect
    return await fut
  File "/usr/local/lib/python3.7/asyncio/selector_events.py", line 494, in _sock_connect_cb
    raise OSError(err, f'Connect call failed {address}')
ConnectionRefusedError: [Errno 111] Connect call failed ('<IP_ADDRESS>', 47779)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 270, in async_update_ha_state
    await self.async_device_update()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 448, in async_device_update
    await self.async_update()
  File "/usr/src/homeassistant/homeassistant/components/upnp/sensor.py", line 143, in async_update
    self._state = await self._device.async_get_total_bytes_sent()
  File "/usr/src/homeassistant/homeassistant/components/upnp/device.py", line 151, in async_get_total_bytes_sent
    return await self._igd_device.async_get_total_bytes_sent()
  File "/usr/local/lib/python3.7/site-packages/async_upnp_client/profiles/igd.py", line 99, in async_get_total_bytes_sent
    result = await action.async_call()
  File "/usr/local/lib/python3.7/site-packages/async_upnp_client/client.py", line 509, in async_call
    await self.service.requester.async_http_request('POST', url, headers, body)
  File "/usr/local/lib/python3.7/site-packages/async_upnp_client/client.py", line 70, in async_http_request
    body_type=body_type)
  File "/usr/local/lib/python3.7/site-packages/async_upnp_client/aiohttp.py", line 103, in async_do_http_request
    async with self._session.request(method, url, headers=headers, data=body) as response:
  File "/usr/local/lib/python3.7/site-packages/aiohttp/client.py", line 1012, in __aenter__
    self._resp = await self._coro
  File "/usr/local/lib/python3.7/site-packages/aiohttp/client.py", line 483, in _request
    timeout=real_timeout
  File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 523, in connect
    proto = await self._create_connection(req, traces, timeout)
  File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 859, in _create_connection
    req, traces, timeout)
  File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 1004, in _create_direct_connection
    raise last_exc
  File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 986, in _create_direct_connection
    req=req, client_error=client_error)
  File "/usr/local/lib/python3.7/site-packages/aiohttp/connector.py", line 943, in _wrap_create_connection
    raise client_error(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host <IP_ADDRESS>:47779 ssl:None [Connect call failed ('<IP_ADDRESS>', 47779)]

Is there something I can do from the side of my router?

This is still an issue with the latest version and can easily be checked simply by rebooting your router and seeing that the port forward does not return.

This is still an issue with the latest version and can easily be checked simply by rebooting your router and seeing that the port forward does not return.

Same issue     0.107.0.dev20200224

Same Issue
Error setting up entry UPnP/IGD for upnp
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/async_upnp_client/aiohttp.py", line 103, in async_do_http_request
    async with self._session.request(method, url, headers=headers, data=body) as response:
  File "/usr/local/lib/python3.7/site-packages/aiohttp/client.py", line 1012, in __aenter__
    self._resp = await self._coro
  File "/usr/local/lib/python3.7/site-packages/aiohttp/client.py", line 504, in _request
    await resp.start(conn)
  File "/usr/local/lib/python3.7/site-packages/aiohttp/client_reqrep.py", line 847, in start
    message, payload = await self._protocol.read()  # type: ignore  # noqa
  File "/usr/local/lib/python3.7/site-packages/aiohttp/streams.py", line 591, in read
    await self._waiter
concurrent.futures._base.CancelledError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 192, in async_setup
    hass, self
  File "/usr/src/homeassistant/homeassistant/components/upnp/__init__.py", line 147, in async_setup_entry
    device = await async_discover_and_construct(hass, config_entry.data.get("udn"))
  File "/usr/src/homeassistant/homeassistant/components/upnp/__init__.py", line 116, in async_discover_and_construct
    return await Device.async_create_device(hass, ssdp_description)
  File "/usr/src/homeassistant/homeassistant/components/upnp/device.py", line 60, in async_create_device
    upnp_device = await factory.async_create_device(ssdp_description)
  File "/usr/local/lib/python3.7/site-packages/async_upnp_client/client_factory.py", line 52, in async_create_device
    root = await self._async_get_url_xml(description_url)
  File "/usr/local/lib/python3.7/site-packages/async_upnp_client/client_factory.py", line 290, in _async_get_url_xml
    await self.requester.async_http_request('GET', url)
  File "/usr/local/lib/python3.7/site-packages/async_upnp_client/client.py", line 70, in async_http_request
    body_type=body_type)
  File "/usr/local/lib/python3.7/site-packages/async_upnp_client/aiohttp.py", line 113, in async_do_http_request
    resp_body = None
  File "/usr/local/lib/python3.7/site-packages/async_timeout/__init__.py", line 55, in __aexit__
    self._do_exit(exc_type)
  File "/usr/local/lib/python3.7/site-packages/async_timeout/__init__.py", line 92, in _do_exit
    raise asyncio.TimeoutError
concurrent.futures._base.TimeoutError

I'm jumping in on this issue as well.
Sometimes my router freaks on me and I have to unplug/plug it back in (no accessible reboot) and the home-assistant code is left repeatedly trying to access it via the old port.
It seems like it would be an easy fix that once this kind of error is encountered, the software would query for the updated port and continue on from there.
In the meantime, all I'm doing is restarting hass.

Port mappings are no longer supported. I think this issue can be closed.

"no longer supported"? when the source is showing the latest activity to have been only 12 days ago, and the integration is still available, and no mention of any deprecation/obsolescence? That kind of "no longer supported"?

Although I don't understand why the port mapping feature was removed at all, I'd have to agree that this is a moot issue now unless that functionality is restored.

I'm just questioning whether it really is "no longer supported" when there's been recent activity and no sign that it isn't supported as far as I can tell other than the comment from a bot-assigned contributor after a previously bot-assigned person removed theirself.

@vindicatorr This might convince you: https://github.com/home-assistant/core/pull/35191
The main reason it was removed is that it was considered dangerous. It was too easy to accidentally expose your home assistant installation to the world wide web.
Also, it required more maintaining from my side. Shrinking the upnp component made it simpler thus resulting in less issues. This is a component which applies to almost every (home-)installation and there are lots of broken devices which partially/brokenly implemented UPnP.

@StevenLooman Ugh, I didn't pay attention to the specific "port mappings" in your reply. I just assumed it was about the whole UPNP/IGD part of hass being gone now.
For me it was never about mapping, and all about just getting the statistics my modem would transmit and like it was mentioned, when the device reboots, the port that hass established is no longer valid and it keeps puking in the log.
So the underlying issue wasn't about the ports (I think), but the loss of connection when the device reboots.
I can go ahead and force a power cycle for my modem to see if the issue still stands (assuming it will) and just open a new issue specific to the part about the loss of connection with the device if that would be best.
I had disabled hass for these past few months because of this and the neglected MaryTTS issue.

@vindicatorr While your router is rebooting it might not be able to reply to the regular requests home assistant sends (once per 30 seconds, by default.) If a connection cannot be established for the request, you might see an error yes.
If you think this is important, then feel free to open a new issue for this. The error can be 'caught' and replaced by a friendly message.


Pulling changes into HA

Wasn't sure where to ask this, but here we go: at what point will the changes in this repository be merged into the HA repository? Are there rules for that?
I've been running the code in this repository for a while now and it seems to work fine.
Means I won't have to run custom_components anymore 😄

What i hear is that there's a new API coming, i think we should merge this again when that's tested and implemented. There are no real rules for that though, we could merge this at any time.

Not much more stability I am afraid since the api that feeds the data is
very unstable. I will soon look at the new api and see how that goes.
On Wed, Dec 6, 2017 at 4:36 PM, Michiel Lowijs<EMAIL_ADDRESS>wrote:

Okay! Good to know, and that sounds like a good idea. Surely many people
will appreciated the improved stability of this code base over the older
version. 😃
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/krocat/ToonHA/issues/21#issuecomment-349676488, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AEbFawqS7pRfcDwQOAm8stXf4UTAqF80ks5s9rSXgaJpZM4Q4EBz
.

Just a quick update here, toonapilib is around 95% done. Currently missing the active part of actually setting values and switching things on and off and enabling the caching. Should be done the next time I sit with it. We can retain full compatibility with the old toonlib so the only thing that we will need once the library is done is to update the component for the new extra arguments of oath_secret and oauth_key and the documentation on how people should register on the new api and get those keys to setup their components. Hoping to be done with the library by the end of the year. Cheers!

Great work @costastf! 😀


Improve Scale.symlog ticks

Follow-up to #2031:

Related: https://github.com/d3/d3-scale/issues/162

Repro: https://www.squiggle-language.com/playground#code=eNqrVkpJTUsszSlxzk9JVbJSCsjJL9FLySwu0YjJU1CoBhEKCiC%2BlYKhQbZCST6Q8tWBCFcEJyfmpFopgCm94srcnPx0DU2wZG1MnqaSjlJxRn55cGlubmJRpZJVSVFpai0A3ekkLw%3D%3D

Does this look good? @berekuk @OAGr ?

That looks great, kudos!


CentOS - SELinux dependency handling

Followup to this PR:
https://github.com/hack13/ansible-opennic-setup/pull/1
This should handle SELinux dependency properly depending on CentOS version -- assumes the use of Python3

Happy to help :)
Thanks for the merge, we should now be more modern!
I've tested on EL7, EL8, and Fedora 32 - all look good.  The many Fedora versions between should be fine, there was a fairly hard cut off for the dependency change at 31


Need to project before using hexagonal sampling in cv_fik-inla

[1] "Begin LOO cross-valdiation of CIV2017PHIA"
[ failed     ]  2022-02-20 11:00:05
[ elapsed    ]  Failed report in 0.2224343 secs
Error in st_poly_sample(x, size = size, ..., type = type, by_polygon = by_polygon) :
  hexagonal sampling on geographic coordinates not supported; consider projecting first
In addition: Warning message:
 Error in st_poly_sample(x, size = size, ..., type = type, by_polygon = by_polygon) :
  hexagonal sampling on geographic coordinates not supported; consider projecting first

https://geocompr.robinlovelace.net/reproj-geo-data.html

Want to use st_transform but don't know the right arguments to set.

Tried using st_transform(3857) which is "Projected CRS: WGS 84 / Pseudo-Mercator". Then I run into the same problem as with the inla_ck!
 Error in Ops.units(m, 1e-08) :
  both operands of the expression should be "units" objects

Jeff suggests EPSG:4326.


User should not be able to save episode without uploading an audio file

Currently this is possible

Resolved in #34


Implement preview login via the Preview API

The default Wagtail preview logic depends too much on the templating rendering layer whilst we're using an API approach.
The first attempt, tried to change the default logic by POSTing to a Frontend url passing through the preview content as a POST param.
This is far from ideal and not very secure.
Hence, this PR restructures the preview logic by disabling the Wagtail 'preview by POST' and requires content designers to always save the content (and therefore create a revision in background) before previewing it.
This way, we can preview content using the page id and the specific revision id via the API.
The Frontend app will pull the preview content using the passed in ids instead of receiving it via a POST param and is therefore more secure.

Coverage increased (+0.3%) to 98.091% when pulling 68880fbc3316098a2d8a48118ee379bda1dbbc6a on preview-button into 1f6bc8a39ae6038d00966854e426f537d6346156 on master.

Coverage increased (+0.3%) to 98.091% when pulling c9ab7f57bd7aa45f647db5c134c4b9f1c02df5cb on preview-button into 1f6bc8a39ae6038d00966854e426f537d6346156 on master.

Coverage increased (+0.3%) to 98.091% when pulling 8ff6b24b31e043ff5ebbe4da4ffe1a11d2e48457 on preview-button into 1f6bc8a39ae6038d00966854e426f537d6346156 on master.

Coverage increased (+0.3%) to 98.091% when pulling b30c7078d5c6ff218bf2ab2561b69d9875135535 on preview-button into 1f6bc8a39ae6038d00966854e426f537d6346156 on master.

Coverage increased (+0.3%) to 98.091% when pulling f3df58ee4b361baf25b45527ed3ed4780e3eabcf on preview-button into 1f6bc8a39ae6038d00966854e426f537d6346156 on master.

@teneightfive have a look as well

Coverage increased (+0.3%) to 98.091% when pulling 7e0df3d35fd9c4f87b3e1ac679c8fe45089d18d7 on preview-button into 007d2f88886c627f1a11f5dc3dcb354f82a5dff6 on master.


Unexpected River Reveal in API

Normally Slumbot only returns cards revealed while playing via API, although I'm curious to see unexposed cards but understand why you would limit this.
Anyway, I found that if:

Player is the dealer
On the turn, SB checks
Player raises
SB re-raises
Player folds
Returned data from API call will include river card, which was never exposed during play

Not a big deal but thought you would want to know.

Thanks for the bug report.  I'm having trouble finding an example of this in the logs.  If you see it again, feel free to share the details with me.  Just knowing what the board cards were would probably be enough for me to find the hand in the logs.

OK, I saw it twice but didn’t collect that info. If I see it again I will let you know.
Jay

On Jan 10, 2022, at 7:35 PM, ericgjackson @.***> wrote:
Thanks for the bug report. I'm having trouble finding an example of this in the logs. If you see it again, feel free to share the details with me. Just knowing what the board cards were would probably be enough for me to find the hand in the logs.
—
Reply to this email directly, view it on GitHub https://github.com/ericgjackson/slumbot2017/issues/13#issuecomment-1009486003, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQSPWNXO4OMOCDJLYIJDQ2TUVN3NVANCNFSM5LUTHJRA.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.

I never saw this again so it was likely me reading the data incorrectly from the feed.
On a side note, let me tell you how much I appreciate you putting this out there as an open resource. It has really helped me focus and refine my engine. Should you find yourself in Philadelphia for any reason, I would love the opportunity to buy you a beer, coffee, or pizza. --Poacher2023

Thanks for letting me know that you found the API useful.  I'll take you up on that beer some time.


Returning rowcount of expanded rows

Promised PR. Fixed scrolling height - row count now returns the count of visible rows instead of all rows.
You can consider merging your branch with upstream master, so possible owner sees that PR is at least auto-merging and in buildable state.

Thanks!


AVCapturePhotoSettings

When taking a sequence of photos with the camera example, I get the following error:
-[AVCapturePhotoOutput capturePhotoWithSettings:delegate:] Settings may not be re-used'
Any idea how to create a unique value for the settings?

let me check that in detail. Thanks for reporting this issue.

I've run into a similar problem when taking more than one photo in my app. I traced the issue back to the reuse of the self.capturePhotoSettings object that has the same uniqueId.
Here is the Apple Doc reference:
https://developer.apple.com/reference/avfoundation/avcapturephotosettings

Important
It is illegal to reuse a AVCapturePhotoSettings instance for multiple captures. Calling the capturePhoto(with:delegate:) method throws an exception (invalidArgumentException) if the settings object’s uniqueID value matches that of any previously used settings object.
To reuse a specific combination of settings, use the init(from:) initializer to create a new, unique AVCapturePhotoSettings instance from an existing photo settings object.

My workaround was to modify the source code as follows.
CameraEngine.swift - line 461
public func capturePhoto(_ blockCompletion: @escaping blockCompletionCapturePhoto) {
        let uniqueSettings = AVCapturePhotoSettings.init(from: self.capturePhotoSettings)
        self.cameraOutput.capturePhoto(settings: uniqueSettings, blockCompletion)
    }

This seems to be working for me now. I hope this is helpful to you guys.


Providing a more helpful message

Tried to validate a sbom  using cyclonedx-cli command:
cyclonedx validate --input-format json --input-file /tmp/scan-trivy.cdx --fail-on-errors --input-version v1_4

What I expected: Invalid sboms should result in a clear and specific error message. (for example something like what sbom-utility prints)
[ERROR] invalid SBOM: schema errors found (/tmp/scan-trivy.cdx):
(2) Schema errors detected (use `--debug` for more details):
	1. Type: [unique], Field: [dependencies.37.dependsOn], Description: [array items[0,1] must be unique]
	Failing object: [[
	  "pkg:deb/debian/libc6@2.31-13+deb11u6?arch=amd64&distro=debian-11.7",
	  "pkg:deb/debi ... (truncated)
	2. Type: [unique], Field: [dependencies.79.dependsOn], Description: [array items[0,1] must be unique]
	Failing object: [[
	  "pkg:deb/debian/debconf@1.5.77?arch=all&distro=debian-11.7",
	  "pkg:deb/debian/debcon ... (truncated)
[INFO] document `/tmp/scan-trivy.cdx`: valid=[false]
exit status 2

What happened: cyclonedx-cli output was not specific enough to identify the problem
Validating JSON BOM...
Validation failed:
#/properties/dependencies/items
BOM is not valid.

https://github.com/CycloneDX/cyclonedx-cli/pull/317 should help in this respect (even if it might not completely resolve it).


Header become unsticky after updateDataSet

When init the adapter and set the data first time , the sticky header works. but after updateDataSet, it become disabled.

@NiaNingXue, please check if the new items have the header set and equals method is correctly implemented.

Sticky Header still works after updateDataSet. Check last commit to test better.


fix(2D): Added saturation, brightness, and contrast to 2D mode

resolves Issue #157

A few things I noticed in testing:

Brightness, contrast, and saturation are only applied if the default color is changed or Colorize is checked. This is due to the color filter being removed from the source unless at least one of those is true.
The end result is different in 2D and 3D because cesium.js is still adjusting values on the Cesium layer, in addition to the transform done in the original tile layer. 2D and 3D tiles should look the same.
Changing the values in 3D mode causes excessive flickering due to reloading the tile textures to the GPU. It would be preferred for Cesium to continue adjusting these values directly on the Cesium layer instead of transforming tiles, for performance reasons. 2D mode should do the transform, and the result should fairly closely match what we see in Cesium.
Translating each pixel from RGB to HSL and back is responsible for 40%+ of the CPU trace when adjusting these tile controls. Can we use a transform matrix against the RGB values to avoid that step? We do that for the color transform, so maybe we can do something similar for brightness/contrast/saturation. I'm not an expert on color transforms, so I poked around a little and most searches point toward this guide: https://docs.rainmeter.net/tips/colormatrix-guide/

@schmidtk's comment needs to be addressed:

Brightness, contrast, and saturation are only applied if the default color is changed or Colorize is checked. This is due to the color filter being removed from the source unless at least one of those is true.

That's occurring on os.layer.Tile:440. You'll need to add some expressions to that check to test for non-default brightness, contrast, and saturation as well.

@lilysikes check out yarn test on your branch. The tests you added have a couple of failures and also one other test is failing due to this ticket.
The failures related to the state XSD should be addressed by ngageoint/opensphere-state-schema#8.
As soon as those are addressed then I think this is good to merge.


cant cancel an order, error -1104

I have tried to cancel an order with:
result = self.binance_client.cancel_order(symbol=self.pair_code, origClientOrderId=trade_id, orderID=exchange_order_id)

and am getting
API Error Code: -1104  API Error message: Not all sent parameters were read; read '4' parameter(s) but was sent '5'.

and if i send with out including my order number I get the same result but read '3' and sent '4'

@Chingis-Khan check your parameters names, it should be orderId, not orderId

lol, Thanks , sorry