Error : Can't find the valid AspnetMergePath - precompilation on Azure

Hello,
I'm trying to attempt to configure precompilation on Azure via git deployment. I'm testing using the default Web Forms project (VS 2015), before attempting with my own project.
I've set it up similar to this [post on stackoverflow] (http://stackoverflow.com/questions/27554510/cant-deploy-precompiled-merged-webapp-to-azure/29614694) as I couldn't find much documentation about how to do it.
I've enabled precompilation, and have experimented with the other settings (all same result) e.g.
Updatable (on / off)
Merge all pages (on / off)
I've created a .deployments file with:
[config]
project=UpstreamTest/UpstreamTest.csproj
SCM_BUILD_ARGS=/p:Configuration=Release;PublishProfile=azure-prod /v:n

This deploys correctly without precompilation, and works with precompilation locally, and using the publish to azure option in VS.
Instead, when deployments are triggered by bitbucket on azure I get the following output (snipped for relevancy):
Command: "D:\home\site\deployments\tools\deploy.cmd"

Handling .NET Web Application deployment.

All packages listed in packages.config are already installed.

Build started 8/11/2015 11:36:18 AM.

The target "MvcBuildViews" listed in a BeforeTargets attribute at "D:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing.targets (840,131)" does not exist in the project, and will be ignored.

Project "D:\home\site\repository\UpstreamTest\UpstreamTest.csproj" on node 1 (Build;pipelinePreDeployCopyAllFilesToOneFolder target(s)).

<SNIP>

  Copying D:\home\site\repository\packages\Microsoft.Net.Compilers.1.0.0\tools\VBCSCompiler.exe.config to obj\Release\AspnetCompileMerge\Source\bin\roslyn\VBCSCompiler.exe.config.

  Copying obj\Release\TransformWebConfig\transformed\Web.config to obj\Release\AspnetCompileMerge\Source\Web.config.

D:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Transform\Microsoft.Web.Publishing.AspNetCompileMerge.targets(132,5): error : Can't find the valid AspnetMergePath [D:\home\site\repository\UpstreamTest\UpstreamTest.csproj]

Done Building Project "D:\home\site\repository\UpstreamTest\UpstreamTest.csproj" (Build;pipelinePreDeployCopyAllFilesToOneFolder target(s)) -- FAILED.

Build FAILED.

"D:\home\site\repository\UpstreamTest\UpstreamTest.csproj" (Build;pipelinePreDeployCopyAllFilesToOneFolder target) (1) ->

(GetAspNetMergePath target) ->

  D:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Transform\Microsoft.Web.Publishing.AspNetCompileMerge.targets(132,5): error : Can't find the valid AspnetMergePath [D:\home\site\repository\UpstreamTest\UpstreamTest.csproj]

    0 Warning(s)

    1 Error(s)

Time Elapsed 00:00:10.37

Failed exitCode=1, command="D:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe" "D:\home\site\repository\UpstreamTest\UpstreamTest.csproj" /nologo /verbosity:m /t:Build /t:pipelinePreDeployCopyAllFilesToOneFolder /p:_PackageTempDir="D:\local\Temp\d34abb98-e420-4bf0-9f7f-a9194a4220b3";AutoParameterizationWebConfigConnectionStrings=false;Configuration=Release /p:SolutionDir="D:\home\site\repository\.\\" /p:Configuration=Release;PublishProfile=azure-prod /v:n

An error has occurred during web site deployment.

I can't find any reference to AspnetMergePath/AspNetCompileMerge in the csproj file or in any project file for that matter.
Is anyone able to shed some light on this, whether i'm doing something wrong or missing a step.
Thanks
Ben

Can you please share a test repo that has this issue? Thanks.

Here is the repo
https://github.com/benosman/upstreamtest
I tested this on Azure, and it has the same error as when using bitbucket.

seems like this error "error : Can't find the valid AspnetMergePath" is not new. from below two thread, to solve the issue we will need to use the right version of build tool.
http://stackoverflow.com/questions/12713714/cant-find-the-valid-aspnetmergepath-on-visual-web-developer-publish
http://blog.maskalik.com/msbuild/2014/03/04/changes-in-msbuild-with-visual-studio-2013/
however, my first attempt failed.

Since project is created from VS2015, I set below app setting
MSBUILD_PATH = D:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe

or update .deployment to below (application is targeting .net framework 4.5)

[config]
project=UpstreamTest/UpstreamTest.csproj
SCM_BUILD_ARGS=/p:Configuration=Release;PublishProfile=azure-prod /v:n /p:VisualStudioVersion=14.0 /p:AspnetMergePath="D:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\"

but still getting the same error.
digging ..

@benosman
there is a two steps work-around as below. I tried with your sample repo and it works. Let me know if you find any other issues.

Go to portal, add one app setting to your site:

Key: MSBUILD_PATH
Value: D:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe

Update your deployment script to below

[config]
project=UpstreamTest/UpstreamTest.csproj
SCM_BUILD_ARGS=/p:Configuration=Release;PublishProfile=azure-prod /v:n /p:AspnetMergePath="D:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools"

Explanation:
From what i learnt, project that created by a different version of Visual Studio, it require a corresponding version of Build Tool. Also asp.net project that target different version of .net framework will have corresponding version of aspnet_merge.exe

@shrimpy
Thanks for looking at this for me, the two changes you suggested worked for me and it now deploys successfully.
Many thanks
Ben


feat: Support seek subscription in AdminClient

Seek subscription performs an out-of-band seek for a subscription to a specified target, which may be a backlog location, publish timestamp or event timestamp.

Note: this feature is pre-release. The "do not merge" label will be removed once publicly available.


[new FAQ] add network proxy related FAQ

What do these changes do?
add a new FAQ related to network proxy setting
Related issue number
#2203
Fixes

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Merged. Thank you @YifanYuan3 !


Update FAQ with sign in block/no detection info

@cloudhandler : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @cloudhandler -- This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. Would you make this content update in the private repo instead? Thank you! We'll close this PR.

Agh no!!! I was sure I had done it in the right one this time. I’m so sorry
From: Kristine Toliver<EMAIL_ADDRESS>Sent: Thursday, October 29, 2020 10:53 AM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Sarah Handler<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Update FAQ with sign in block/no detection info (#65242)
Hi @cloudhandlerhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcloudhandler&data=04|01|sarah.handler%40microsoft.com|b71c1f1dc6654a1593c208d87c3368e1|72f988bf86f141af91ab2d7cd011db47|1|0|637395907530989639|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Dr607RdK2CZD7TR59OJxDfVEPU9jeX2b0JNo%2BX1tpaA%3D&reserved=0 -- This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. Would you make this content update in the private repo instead? Thank you! We'll close this PR.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fpull%2F65242%23issuecomment-718920055&data=04|01|sarah.handler%40microsoft.com|b71c1f1dc6654a1593c208d87c3368e1|72f988bf86f141af91ab2d7cd011db47|1|0|637395907530999636|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=b8rEGffXKRxlAImVLS0zxvv9rBQNnlHdGcz3MJACpGo%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAH3QFY6XQKD3ZZ236SKWGNTSNGTV7ANCNFSM4TEBF7HQ&data=04|01|sarah.handler%40microsoft.com|b71c1f1dc6654a1593c208d87c3368e1|72f988bf86f141af91ab2d7cd011db47|1|0|637395907531009633|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=9nP245pZxdN82FfXA%2BYaml%2FiiuB6xM85UxJXxCi7SOw%3D&reserved=0.


'Download a url list' function does not work (Crash)

When I use 'Download a url list' function instead of downloading actual files, TumblThree freezes (or crashes) after retrieving first 25 urls. I am only trying to get image and video file links but it seems to have some problem on my computer.

Thanks for reporting. It's really time for unit tests now ...
The date setting of the downloaded files truly doesn't work if there is no file downloaded at all but the url stored in a text file instead.


Prepare for new release of Confluence

Workflow links: https://github.com/atlassian-labs/atlassian-slack-integration-server/actions/runs/4012278414, https://github.com/atlassian-labs/atlassian-slack-integration-server/actions/runs/4012280210.

JDK 17 run: https://github.com/atlassian-labs/atlassian-slack-integration-server/actions/runs/4106990997

Java 8 is not supported anymore for confluence 8.0.3.
Integration tests pass for JDK 11 and 17, so current version of Confluence Server for Slack is marked compatible with 8.0.3


[sample request ] paypal sample

Have a request for a new sample?
Is it possible to add a paypal sample into functions?
Example:

A user buys a service or product via paypal.
Paypal triggers it's webhook to Functions.
Functions updates the firebase database and send a push notification to the user.

Its possible. Basically add paypal-rest-sdk to the functions directory.
In the index.js execute paypal.configure with the client id + secret you’ve created to the app in your paypal developer console.
Next, depends on your needs (payment/subscription etc), create the objects you need (based on the paypal rest docs) and execute the functions. For example, for one-time payment use the following functions:
paypal.payment.create
paypal.payment.execute
remember that ‘create’ takes a PAYMENT OBJECT as first param, and there you can set ‘return_url’ that will point to the second function ‘execute’, and so you call the ‘create’ which - when finished with user approval on paypal - will call the ‘execute’.
Hope this gives you few starting points. It is very confusing in the beginning, mainly due to the psychedelic docs and examples at paypal, with some wrong instructions and some black holes, and several bugs in the developer console and few sandbox horrors, but once you get used to it its not that difficult. Make sure you log all return values and post results, it will vlarify what is really going on.
Good luck!

We now have a Paypal sample: https://github.com/firebase/functions-samples/tree/master/paypal

Hi, I have implemented PayPal payouts through my Android app but unable to get implemented in my IOS app.  Basically, when the GET PAYOUTS button is selected, a POST request is sent to the firebase-function and then the data is sent to PayPal.  When I see the firebase-logs, I see the data is captured through a console.log() but isn't retained through PayPal and cannot figure out why.  Please see my index.js file attached and my iOS swift payoutRequest() method
index_js.txt
payoutRequest.txt
Any help would be greatly appreciated as I have been working on this for a month with no resolution in sight.
. No one on stack overflow has been able to answer my posts on this.


[stable/nginx-ingress] Nginx ingress no empty quotes clusterIp

What this PR does / why we need it:
Please see https://github.com/helm/charts/pull/19146
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #19041

Special notes for your reviewer:
#19146 was missing this, because if we keep quote we still get empty quotes as values for clusterIp.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

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

cc @ChiefAlexander @taharah

As it stands we will still wind up with clusterIP: "" if no value is provided ... just {{ . }} is better since it will not add clusterIP to rendered files if no value is provided, but the user needs to quote any provided values themselves

Please add to the readme what is expected for this to work for users who may need to include that. I think this should also be a minor change as we are changing how someone would set their values files.

@ChiefAlexander README updated, I also added a deprecation notice to the commendable omitClusterIP workaround as this would make it redundant.

/retest

@ChiefAlexander had a few hiccups sorry. Chart is ready now! Thanks.

Thanks for working on this
/lgtm

My pleasure and thanks for the quick lgtm @ChiefAlexander

Any idea why no artifact was produced??

It's there now, charts sync every half hour.

Hi! I'm on chart version 1.25.0 and tried to upgrade to 1.26.1. I removed the previously supplied clusterIP fields as auggested and sill get the same error.
$ helm history nginx-ingress
33              Fri Nov 15 13:48:28 2019        deployed        nginx-ingress-1.25.0    0.26.1          Upgrade complete
34              Thu Nov 28 12:09:04 2019        failed          nginx-ingress-1.26.1    0.26.1          Upgrade "nginx-ingress" failed: cannot patch "nginx-ingress-controller" with kind Service: Service "nginx-ingress-controller" is invalid: spec.clusterIP: Invalid value: "": field is immutable && cannot patch "nginx-ingress-default-backend" with kind Service: Service "nginx-ingress-default-backend" is invalid: spec.clusterIP: Invalid value: "": field is immutable

Is there a special upgrade procedure? I was doing this previously and was hoping to remove the kubectl calls:
__clusterIP=$(kubectl get services nginx-ingress-controller -o jsonpath="{.spec.clusterIP}")
__clusterIPdefault=$(kubectl get services nginx-ingress-default-backend -o jsonpath="{.spec.clusterIP}")
helm upgrade nginx-ingress stable/nginx-ingress \
    --wait \
    --reuse-values \
    --set controller.service.clusterIP=${__clusterIP} \
    --set defaultBackend.service.clusterIP=${__clusterIPdefault}

Hi @josefschabasser , I'm afraid my efforts were in vain. I have the same issue and I've given in and am hard quoting the clusterIPs in the values file until I can afford a downtime to re deploy without those values... Sorry :(

@naseemkullah thanks for your efforts to fix this annoying issue.
Is there a remaining chance to fix this properly, or is there no way around hard-coding IP addresses when this issue occurs?
Just for me to understand: Why doesn't your fix work? Is this a limitation of how k8s handles Service resources, or is it a limitation of the Helm template language?
If I understood correctly, this issue at least should't appear for fresh deployments of 1.26.1 or later, right?

@naseemkullah thanks for your efforts to fix this annoying issue.
Is there a remaining chance to fix this properly, or is there no way around hard-coding IP addresses when this issue occurs?

I've tried just about everything after upgrading to helm3. I think if you are still on helm2 there is more of a chance, try commenting out all the clusterIP values in your values file and see if that works.

Just for me to understand: Why doesn't your fix work? Is this a limitation of how k8s handles Service resources, or is it a limitation of the Helm template language?

I'm pretty confused and not sure anymore sorry.

If I understood correctly, this issue at least should't appear for fresh deployments of 1.26.1 or later, right?
That's my understanding and hope

Thanks, will try that when back at work.
I'll also try to assign null to the .clusterIP values, maybe it has a different effect.

Thanks, will try that when back at work.
I'll also try to assign null to the .clusterIP values, maybe it has a different effect.

Please share how it goes!

 There is no difference in the resulting rendered template.

I mixed up the PRs, and commented to the other one sorry....
https://github.com/helm/charts/pull/13646#issuecomment-561560417


Better error rendering (human readable captions)

Refer to my issues for Joi...
Markdown test

Not going to invest time to this for now.


Optimizing over unknown domain for context variable

I'm working with a problem that has a continuous context variable whose min and max I don't know - how might I approach this?
In thinking that the bo.domain only matters for suggesting samples via bo.suggested_sample = bo._compute_next_evaluations(), I set the unknown continuous domains to (0,1) arbitrarily and set the bo.context={'fixed_dim':3.14}. Expecting to see the bo.suggested_sample contain the context dimensions fixed at what I provided via bo.context i.e. 3.14, I am surprised to see 1.
Setting the unknown domain to (0,np.inf) appears to satisfy my use-case, but in general, what is the GPyOptic way to achieve this functionality? Is (-np.inf, np.inf) appropriate? And what might be done in the case that we have unknown cardinality of the categorical variables' sets? The latter seems more daunting vis a vis the one-hot-encoded bo.X columns...

You can set the boundary of context variable to be [-inf, inf]. I do not think we actually do the boundary check for setting the context variable. The API that you should use should be either BO.run_optimization(context=...) or BO.suggest_next_locations(context=...).

Hmm I will consider BO.suggest_next_locations.
There doesn't appear to be boundary checking, but there does appear to be some value overriding. When I set context that is outside of bounds (before using (-inf, inf)) the context is overridden.
The question still stands re: unknown cardinality of categorical variable valid sets - maybe a more interesting problem - any thoughts?


Error while trying to install nms-extension

Hello!
I am trying to install the custom extensions from MDT_ProstateX: custom_extensions/nms, custom_extensions/roi_align/2D, and custom_extensions/roi_align/3D. RoIAlign-extension-2D and RoIAlign-extension-3D have been successfully built, but nms-extension keeps failing. I have attached below the console output I get everytime I am trying to run setup.py.
I am using PyCharm Community Edition 2021.2.3 on Windows 10, with NVIDIA GPU Computing Toolkit/CUDA/v11.6 and Visual Studio Build Tools 2019. The virtual environment uses Python 3.7, as suggested in the README.md document.
  building 'nms_extension' extension
  C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.29.30133\bin\HostX86\x64\cl.exe /c /nologo /Ox /W3 /GL /DNDEBUG /MD -IC:\Users\anama\anaconda3\envs\prostate_lesion\lib\site-packages\torch\include -IC:\Users\anama\anaconda3\envs\prostate_lesion\lib\site-packages\torch\include\torch\csrc\api\include -IC:\Users\anama\anaconda3\envs\prostate_lesion\lib\site-packages\torch\include\TH -IC:\Users\anama\anaconda3\envs\prostate_lesion\lib\site-packages\torch\include\THC "-IC:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.6\include" -IC:\Users\anama\anaconda3\envs\prostate_lesion\include -IC:\Users\anama\anaconda3\envs\prostate_lesion\include "-IC:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.29.30133\include" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\ucrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\shared" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\um" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\winrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\cppwinrt" /EHsc /TpD:\git\prostate_lesion_detection\MDT_ProstateX\custom_extensions\nms\src\nms_interface.cpp /Fobuild\temp.win-amd64-3.7\Release\git\prostate_lesion_detection\MDT_ProstateX\custom_extensions\nms\src\nms_interface.obj /MD /wd4819 /EHsc -DTORCH_API_INCLUDE_EXTENSION_H -DTORCH_EXTENSION_NAME=nms_extension -D_GLIBCXX_USE_CXX11_ABI=0
  nms_interface.cpp
  C:\Users\anama\anaconda3\envs\prostate_lesion\lib\site-packages\torch\include\c10/util/Exception.h(28): warning C4275: non dll-interface class 'std::exception' used as base for dll-interface class 'c10::Error'
  C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.29.30133\include\vcruntime_exception.h(48): note: see declaration of 'std::exception'
  C:\Users\anama\anaconda3\envs\prostate_lesion\lib\site-packages\torch\include\c10/util/Exception.h(28): note: see declaration of 'c10::Error'
  C:\Users\anama\anaconda3\envs\prostate_lesion\lib\site-packages\torch\include\c10/util/Exception.h(29): warning C4251: 'c10::Error::msg_stack_': class 'std::vector<std::string,std::allocator<std::string>>' needs to have dll-interface to be used by clients of class 'c10::Error'
  C:\Users\anama\anaconda3\envs\prostate_lesion\lib\site-packages\torch\include\c10/util/Exception.h(29): note: see declaration of 'std::vector<std::string,std::allocator<std::string>>'
  C:\Users\anama\anaconda3\envs\prostate_lesion\lib\site-packages\torch\include\c10/util/Exception.h(30): warning C4251: 'c10::Error::backtrace_': class 'std::basic_string<char,std::char_traits<char>,std::allocator<char>>' needs to have dll-interface to be used by clients of class 'c10::Error'

  [Many warnings listed from C:\Users\anama\anaconda3\envs\prostate_lesion\lib\site-packages\torch\include: warning C4251, C4273, C4275, C4267, C4244 etc.]

  C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.6\bin\nvcc.exe -c D:\git\prostate_lesion_detection\MDT_ProstateX\custom_extensions\nms\src\nms.cu -o build\temp.win-amd64-3.7\Release\git\prostate_lesion_detection\MDT_ProstateX\custom_extensions\nms\src\nms.obj -IC:\Users\anama\anaconda3\envs\prostate_lesion\lib\site-packages\torch\include -IC:\Users\anama\anaconda3\envs\prostate_lesion\lib\site-packages\torch\include\torch\csrc\api\include -IC:\Users\anama\anaconda3\envs\prostate_lesion\lib\site-packages\torch\include\TH -IC:\Users\anama\anaconda3\envs\prostate_lesion\lib\site-packages\torch\include\THC "-IC:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.6\include" -IC:\Users\anama\anaconda3\envs\prostate_lesion\include -IC:\Users\anama\anaconda3\envs\prostate_lesion\include "-IC:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.29.30133\include" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\ucrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\shared" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\um" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\winrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\cppwinrt" -Xcompiler /EHsc -Xcompiler /wd4819 -Xcompiler /MD -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr -DTORCH_API_INCLUDE_EXTENSION_H -DTORCH_EXTENSION_NAME=nms_extension -D_GLIBCXX_USE_CXX11_ABI=0 -gencode=arch=compute_61,code=sm_61 -gencode=arch=compute_75,code=sm_75

  [Many warnings listed from C:\Users\anama\anaconda3\envs\prostate_lesion\lib\site-packages\torch\include: warning #1394-D, #68-D, #1388-D etc.]

  C:/Users/anama/anaconda3/envs/prostate_lesion/lib/site-packages/torch/include\torch/csrc/jit/script/jit_exception.h(10): warning #1388-D: base class dllexport/dllimport specification differs from that of the derived class
  C:/Users/anama/anaconda3/envs/prostate_lesion/lib/site-packages/torch/include\c10/cuda/CUDAStream.h(171): warning #1394-D: field of class type without a DLL interface used in a class with a DLL interface
  C:/Users/anama/anaconda3/envs/prostate_lesion/lib/site-packages/torch/include\TH/THAllocator.h(60): warning #1394-D: field of class type without a DLL interface used in a class with a DLL interface
  C:/Users/anama/anaconda3/envs/prostate_lesion/lib/site-packages/torch/include\TH/THAllocator.h(66): warning #1394-D: field of class type without a DLL interface used in a class with a DLL interface
  C:/Users/anama/anaconda3/envs/prostate_lesion/lib/site-packages/torch/include\THC/THCAllocator.h(14): warning #1394-D: field of class type without a DLL interface used in a class with a DLL interface

  2 errors detected in the compilation of "D:/git/prostate_lesion_detection/MDT_ProstateX/custom_extensions/nms/src/nms.cu".
  nms.cu
  error: command 'C:\\Program Files\\NVIDIA GPU Computing Toolkit\\CUDA\\v11.6\\bin\\nvcc.exe' failed with exit status 1

I would really appreciate your help, since I am not sure what I am missing.
Thank you!

Hi,
Unfortunately, I am not sure that I can help you. medicaldetectiontoolkit was developed for linux, and there is no support for Windows. You could try to reach the developers, but even the new framework that they have developed, nnDetection does not support Windows either.
Regards,
Oscar.

Hi!
Thank you for the quick response.
I managed to run the setup.py file successfully through WSL2 Ubuntu 20.04.4 LTS.

That's great to hear!

Hello, thanks for your contribution!
I have used torch1.9.0+cudnn11.4 to run

python exec.py --mode test --exp_source experiments/exp0 --exp_dir experiments/exp0

. But it brings a problem in nms.py  in the line 37

return nms_extension.nms(boxes, scores, iou_threshold)

.The details are as follows.
RuntimeError: CUDA error: no kernel image is available for execution on the device
CUDA kernel errors might be asynchronously reported at some other API call,so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.

Could you please give me some guidance? I will be very grateful if you can help me.
Best wishes!

As I mentioned, WSL is not officially supported, so I can't really help you
much.
By searching for your error a bit online I found that you might have an
older GPU, and maybe want to try with CUDA 10 instead of CUDA 11
https://stackoverflow.com/questions/67825986/nvidia-cuda-error-no-kernel-image-is-available-for-execution-on-the-device
Regards,
Oscar.
El mié, 6 jul 2022 a las 11:05, changzhang777 @.***>)
escribió:

Hello, thanks for your contribution!
I have used torch1.9.0+cudnn11.4 to run
python exec.py --mode test --exp_source experiments/exp0 --exp_dir
experiments/exp0
. But it brings a problem in nms.py in the line 37
return nms_extension.nms(boxes, scores, iou_threshold)
.The details are as follows.
RuntimeError: CUDA error: no kernel image is available for execution on the device
CUDA kernel errors might be asynchronously reported at some other API call,so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.
Could you please give me some guidance? I will be very grateful if you can
help me.
Best wishes!
—
Reply to this email directly, view it on GitHub
https://github.com/OscarPellicer/prostate_lesion_detection/issues/3#issuecomment-1175973373,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AELKNITXFZQ3MZ5TDDQH4HTVSVD4FANCNFSM5SRSVIIQ
.
You are receiving this because you commented.Message ID:
@.***>

Hello!
First of all thanks for your great work. I have some confusions and I would appreciate if you could help.
I noticed that the requirement.txt file in the MDT_ProstateX folder requests torch==1.4.0, torchvision==0.5.0, and you also said that you are using pytorch 1.7, can I change torch==1.4.0 , torchvision==0.5.0 replaced with torch==1.7.0, torchvision==0.8.0?
Kind regards.

Thank you for your answer ！the cause of the previous problem is indeed related to the version of the torch, I have switched to the torch 1.7 to solve the problem.
But I have a new problem, when using ProstateX preprocessing.ipynb preprocessing pid=0105 samples, a warning and an error were thrown.
/home/zbx/anaconda3/envs/prostate_lesion/lib/python3.7/site-packages/numpy/core/fromnumeric.py:3441: RuntimeWarning: Mean of empty slice.
  out=out, **kwargs)
/home/zbx/anaconda3/envs/prostate_lesion/lib/python3.7/site-packages/numpy/core/_methods.py:189: RuntimeWarning: invalid value encountered in double_scalars
  ret = ret.dtype.type(ret / rcount)
 - Error: Lesion mask array is empty: no segmentations were performed

It points out that the lesion_masks_arr_list of this sample is an all-0 vector, corresponding to line 882 in the code preprocessing_lib.py:
lesion_mask= np.mean([m for m in lesion_masks_arr_list if np.sum(m) > 64], axis=0) > 2.5/8 #At least 3
Is this normal and will it affect the following test and analysis?
Regards.

I'm pretty sure that it is normal and it should not affect later stages, but it has been a while...
If you have problems later on, let me know and I will look deeper into it.


Get nft owner history does not include initial send block

Example block: A61110DC676B0405D507342CD4679C1842867BABE5CEA1A4FEAD5D81EC4A4D75
(Template Qmf3kndfvzLW6RDcnAne6xcdgKXg2NCXfZHjLUnAmaad6q)
Response from get_nft_asset_owner has an empty history array (should include the initial send that minted the block):

now shows
Asset:A61110DC676B0405D507342CD4679C1842867BABE5CEA1A4FEAD5D81EC4A4D75
Asset Owner:ban_3dbwwneas58hr8ihhrtt4616gh4wzasuj5p85xohfbmr6nmyd7z1ret8bac4
Asset Account:ban_3bij45g8gtr61qcigf3etjmsr844isxtqsggn8khxdcxi9p6nmdoyppi9x5i
A61110DC676B0405D507342CD4679C1842867BABE5CEA1A4FEAD5D81EC4A4D75=>=ban_3dbwwneas58hr8ihhrtt4616gh4wzasuj5p85xohfbmr6nmyd7z1ret8bac4

reopened issue as i did it wrong. only checked first send and not last send.


fix: prior and posterior profile plotting

Prior and Prior+posterior profile plotting.
Named columns with prior explicitly: prior_bias and prior_sq
Prior and prior+posterior plotting of rmse, bias, total spread
Note the prior plotting does not need the dataframe reshaping to long, but leaving it in to be consistent with plot_profile_prior_post for now.
I'm not sure whether plotly is the way forwards, it is pretty and nice to have the interactive plots (click by type), but matplotlib might be a better option going forwards to reproduce the DART Matlab plots. Or not. Sticking with plotty for now.
example of clickable type plot: (note y axis needs reversing)

reverse axis for pressure a62ce63

Codecov Report
Attention: Patch coverage is 9.09091% with 60 lines in your changes missing coverage. Please review.

Please upload report for BASE (main@bd0041c). Learn more about missing BASE report.

Files with missing lines
Patch %
Lines

src/pydartdiags/plots/plots.py
6.25%
60 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #29   +/-   ##
=======================================
  Coverage        ?   68.81%
=======================================
  Files           ?        2
  Lines           ?      574
  Branches        ?        0
=======================================
  Hits            ?      395
  Misses          ?      179
  Partials        ?        0

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Dump RSpec JUnit Formatter failures to a local .xml_dump_failures file #trivial

So that the test suite won't emit a lot of scary stuff. If anyone want to checkout those failures, can see  this file .xml_dump_failures after tests ran.

works for me

I notice sometimes CircleCI only run 420 examples instead of 490 examples...\_(ツ)_/


Gentoo Bot doesn't work

I've got a gentoo-server with python 2.7.10 installed.
sqlite useflag fpr python is set.
When cloning and pip install -r requirements.txt the follwing errors appear:
remote: Counting objects: 1523, done.
remote: Compressing objects: 100% (33/33), done.
remote: Total 1523 (delta 14), reused 0 (delta 0), pack-reused 1490
Empfange Objekte: 100% (1523/1523), 814.60 KiB | 335.00 KiB/s, Fertig.
Löse Unterschiede auf: 100% (789/789), Fertig.
Prüfe Konnektivität ... Fertig.
/usr/lib64/python2.7/site-packages/requests/packages/urllib3/contrib/socks.py:31: DependencyWarning: SOCKS support in urllib3 requires the installation of optional dependencies: specifically, PySocks.  For more information, see https://urllib3.readthedocs.org/en/latest/contrib.html#socks-proxies
  DependencyWarning
Obtaining pgoapi from git+git://github.com/tejado/pgoapi.git@1f25e907f3e5f1b603330e71041e1ad7bee7580f#egg=pgoapi (from -r requirements.txt (line 1))
  Cloning git://github.com/tejado/pgoapi.git (to 1f25e907f3e5f1b603330e71041e1ad7bee7580f) to ./src/pgoapi
  Could not find a tag or branch '1f25e907f3e5f1b603330e71041e1ad7bee7580f', assuming commit.
Requirement already satisfied (use --upgrade to upgrade): geopy==1.11.0 in /usr/lib64/python2.7/site-packages (from -r requirements.txt (line 2))
Collecting protobuf==3.0.0b4 (from -r requirements.txt (line 3))
  Using cached protobuf-3.0.0b4.tar.gz
Requirement already satisfied (use --upgrade to upgrade): requests==2.10.0 in /usr/lib64/python2.7/site-packages (from -r requirements.txt (line 4))
Requirement already satisfied (use --upgrade to upgrade): s2sphere==0.2.4 in /usr/lib64/python2.7/site-packages (from -r requirements.txt (line 5))
Requirement already satisfied (use --upgrade to upgrade): gpsoauth==0.3.0 in /usr/lib64/python2.7/site-packages (from -r requirements.txt (line 6))
Requirement already satisfied (use --upgrade to upgrade): protobuf-to-dict==0.1.0 in /usr/lib64/python2.7/site-packages (from -r requirements.txt (line 7))
Requirement already satisfied (use --upgrade to upgrade): googlemaps==2.4.4 in /usr/lib64/python2.7/site-packages (from -r requirements.txt (line 8))
Collecting colorama==0.3.7 (from -r requirements.txt (line 9))
  Using cached colorama-0.3.7-py2.py3-none-any.whl
Requirement already satisfied (use --upgrade to upgrade): six>=1.9 in /usr/lib64/python2.7/site-packages (from protobuf==3.0.0b4->-r requirements.txt (line 3))
Requirement already satisfied (use --upgrade to upgrade): setuptools in /usr/lib64/python2.7/site-packages (from protobuf==3.0.0b4->-r requirements.txt (line 3))
Requirement already satisfied (use --upgrade to upgrade): future in /usr/lib64/python2.7/site-packages (from s2sphere==0.2.4->-r requirements.txt (line 5))
Requirement already satisfied (use --upgrade to upgrade): pycryptodomex>=3.0 in /usr/lib64/python2.7/site-packages (from gpsoauth==0.3.0->-r requirements.txt (line 6))
Installing collected packages: protobuf, pgoapi, colorama
  Found existing installation: protobuf 2.6.1
    Uninstalling protobuf-2.6.1:
      Successfully uninstalled protobuf-2.6.1
  Running setup.py install for protobuf
    Complete output from command /usr/bin/python2.7 -c "import setuptools, tokenize;__file__='/tmp/pip-build-i1onX2/protobuf/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-JSj5gH-record/install-record.txt --single-version-externally-managed --compile:
    running install
    running build
    running build_py
    protoc is not installed nor found in ../src.  Please compile it or install the binary package.
    Generating google/protobuf/pyext/python_pb2.py...

    ----------------------------------------
  Rolling back uninstall of protobuf
Command "/usr/bin/python2.7 -c "import setuptools, tokenize;__file__='/tmp/pip-build-i1onX2/protobuf/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /tmp/pip-JSj5gH-record/install-record.txt --single-version-externally-managed --compile" failed with error code 255 in /tmp/pip-build-i1onX2/protobuf

@alexanderrock consider using virtualenv

@alexanderrock did you install protobuf?
portage install protobuf

Just emerging the following two:
dev-libs/protobuf
dev-python/protobuf-python
Also it says that pysqlite or sqlite are not installed.
Also recompiled python with sqlite useflag.
File "/usr/lib64/python2.7/site-packages/peewee.py", line 3402, in connect
    **self.connect_kwargs)
  File "/usr/lib64/python2.7/site-packages/peewee.py", line 3657, in _connect
    raise ImproperlyConfigured('pysqlite or sqlite3 must be installed.')
peewee.ImproperlyConfigured: pysqlite or sqlite3 must be installed.

now its working after the emerge

@alexanderrock if its working please close the issue

@alexanderrock I assume its working, closing the issue.
Please feel free the open a new issue when necessary!


update crypto from 2.1.12 to 2.1.4-SNAPSHOT & integrate gitlab artifa…

…ct repo

does this compile? you haven't added the Ubirch Maven Repository as a repository for dependencies only for distributions. Would have thought, you need both. But if not, the better!
Also I wonder, if we should update the ubirch-crypto library version to a non-snapshot version, as it now even has been deployed to PROD and didn't cause any errors yet.. just an idea.

does this compile? you haven't added the Ubirch Maven Repository as a repository for dependencies only for distributions. Would have thought, you need both. But if not, the better! Also I wonder, if we should update the ubirch-crypto library version to a non-snapshot version, as it now even has been deployed to PROD and didn't cause any errors yet.. just an idea.

yes, it compiles. it can be the case that my local setup resolves the dependency. But, I want to see how it goes on GOCD.

if we should update the ubirch-crypto library version to a non-snapshot version, as it now even has been deployed to PROD and didn't cause any errors yet.. just an idea
Yes, we can.


Alert - Get incident

Describe the Bug with repro steps
Task 6: Invoke an incident and review the associated actions.
Links to an external site.
In the Azure portal, navigate to the Microsoft Defender for Cloud | Overview blade.
Note: Check your secure score. By now it should have updated.
On the Microsoft Defender for Cloud | Overview blade, click Workload protections under Cloud Security in the left navigation.
On the Microsoft Defender for Cloud | Workload protections blade, scroll down and click Just-in-time VM access tile under Advanced protection.
On the Just-in-time VM access blade, on the right hand side of the row referencing the myVM virtual machine, click the ellipsis (...) button, click Remove and then click Yes.
Note: If the VM is not listed in the Just-in-time VMs, navigate to Virutal Machine blade and click the Configuration, Click the Enable the Just-in-time VMs option under the Just-in-time Vm's access. Repeat the above step to navigate back to the Microsoft Defender for Cloud and refresh the page, the VM will appear.
In the Azure portal, in the Search resources, services, and docs text box at the top of the Azure portal page, type Activity log and press the Enter key.
Navigate to the Activity log blade, note an Delete JIT Network Access Policies entry.
Note: This may take a few minutes to appear. Refresh the page if it does not appear.
In the Azure portal, navigate back to the Microsoft Sentinel | Overview blade.
On the Microsoft Sentinel | Overview blade, review the dashboard and verify that it displays an incident corresponding to the deletion of the Just-in-time VM access policy.
Note: It can take up to 5 minutes for alerts to appear on the Microsoft Sentinel | Overview blade. If you are not seeing an alert at that point, run the query rule referenced in the previous task to verify that the Just-in-time access policy deletion activity has been propagated to the Log Analytics workspace associated with your Microsoft Sentinel instance. If that is not the case, re-create the Just-in-time VM access policy and delete it again.
On the Microsoft Sentinel | Overview blade, in the Threat Management section, click Incidents.
Verify that the blade displays an incident with either medium or high severity level.
Note: It can take up to 5 minutes for the incident to appear on the Microsoft Sentinel | Incidents blade.
Note: Review the Microsoft Sentinel | Playbooks blade. You will find there the count of succesfull and failed runs.
Note: You have the option of assigning a different severity level and status to an incident.
Results: You have created an Microsoft Sentinel workspace, connected it to Azure Activity logs, created a playbook and custom alerts that are triggered in response to the removal of Just-in-time VM access policies, and verified that the configuration is valid.
What type of Logic App Is this happening in?
Consumption (Portal)
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
No response
Screenshots or Videos

Browser
Chrome
Additional context
No response

Describe the Bug with repro steps
Task 6: Invoke an incident and review the associated actions. Links to an external site. In the Azure portal, navigate to the Microsoft Defender for Cloud | Overview blade.
Note: Check your secure score. By now it should have updated.
On the Microsoft Defender for Cloud | Overview blade, click Workload protections under Cloud Security in the left navigation.
On the Microsoft Defender for Cloud | Workload protections blade, scroll down and click Just-in-time VM access tile under Advanced protection.
On the Just-in-time VM access blade, on the right hand side of the row referencing the myVM virtual machine, click the ellipsis (...) button, click Remove and then click Yes.
Note: If the VM is not listed in the Just-in-time VMs, navigate to Virutal Machine blade and click the Configuration, Click the Enable the Just-in-time VMs option under the Just-in-time Vm's access. Repeat the above step to navigate back to the Microsoft Defender for Cloud and refresh the page, the VM will appear.
In the Azure portal, in the Search resources, services, and docs text box at the top of the Azure portal page, type Activity log and press the Enter key.
Navigate to the Activity log blade, note an Delete JIT Network Access Policies entry.
Note: This may take a few minutes to appear. Refresh the page if it does not appear.
In the Azure portal, navigate back to the Microsoft Sentinel | Overview blade.
On the Microsoft Sentinel | Overview blade, review the dashboard and verify that it displays an incident corresponding to the deletion of the Just-in-time VM access policy.
Note: It can take up to 5 minutes for alerts to appear on the Microsoft Sentinel | Overview blade. If you are not seeing an alert at that point, run the query rule referenced in the previous task to verify that the Just-in-time access policy deletion activity has been propagated to the Log Analytics workspace associated with your Microsoft Sentinel instance. If that is not the case, re-create the Just-in-time VM access policy and delete it again.
On the Microsoft Sentinel | Overview blade, in the Threat Management section, click Incidents.
Verify that the blade displays an incident with either medium or high severity level.
Note: It can take up to 5 minutes for the incident to appear on the Microsoft Sentinel | Incidents blade.
Note: Review the Microsoft Sentinel | Playbooks blade. You will find there the count of succesfull and failed runs.
Note: You have the option of assigning a different severity level and status to an incident.
Results: You have created an Microsoft Sentinel workspace, connected it to Azure Activity logs, created a playbook and custom alerts that are triggered in response to the removal of Just-in-time VM access policies, and verified that the configuration is valid.
What type of Logic App Is this happening in?
Consumption (Portal)
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
No response
Screenshots or Videos

Browser
Chrome
Additional context
No response

changeincidentseverity.json


Total counts for PUM, PUI, and tests are null

The original data source removed this data. They are currently set as null.

Moved to #34


Bash Shell Integration: Please co-exist with other trap DEBUG handlers (ie: leverage bash-preexec)

The vscode shell integration currently needs to be turned off or disabled for anyone with complex prompt commands, or any trap DEBUG.
Please consider supporting some kind of chaining model so we can work with the shell integration as needed.
Even better - use the defacto package that has already been written.
VSCode is the 3rd script that wants to mess with prompts and traps - but it's the first to completely ignore https://github.com/rcaloras/bash-preexec
Please consider shipping this along side shellintegration-bash.sh and sourcing/using it.  If that is unacceptable, consider at least
detecting this module has been loaded as documented in the repo - and using it:
if [[ -n "${bash_preexec_imported:-}" ]]; then
    precmd_functions+=(__vsc_chained_precmd)
    preexec_functions+=(__vsc_chained_preexec)
else
    # the existing prompt/trap stuff near the end of the file.
fi

fwiw: iterm2 has very very similar functionality to the vscode shell integration, but I've been able to work with it. Although they embedded the script directly, they kept the compatible function names and mechanisms and interop fine.

I believe we have already fixed this:
https://github.com/microsoft/vscode/blob/5357dcfc04ddfce12661dca80ae9a104640a2c7e/src/vs/workbench/contrib/terminal/browser/media/shellIntegration-bash.sh#L91-L105
Adding @meganrogge to make sure

Well, line 100 PS1=... breaks my prompt.
Adding the line echo "$BASH_COMMAND" as the 1st line of __vsc_preexec shows why.
I think perhaps there needs to be 1 more state 'not in prompt' that causes preexec to bail until all prompt_command processing is done.
Alternatively, if this is all to send __vsc_command_output_start - it seems like using PS0 on bash >= 4.4 would be a lot cleaner?

We've made some big changes in the past few days around debug trap and PS1 handling in bash, I believe the issues here are fixed. We may at some point hook into bash-preexec similar to what starship does but for now that will just increase the number of cases we would need to test for (contributions very welcome).

Actually I'll keep this open with help wanted to track.

OK. Pulling the bash integration script on June-03 - Things look better, but not quite right.
The problems I see:

Still seems to be not preserving $? for prompt_command
Seems to execute the trap twice.  repro with setup instructions below: Do 'cd' into some directory.  The command '..' should then pop one directory up, but it will try to process twice and pop twice.
Instead of 'success dots' in the gutter, all commands seem to think there are fail exit status.

If you like, here are my dotfiles: https://github.com/joerohde/dotfiles and a branch to help debug:
https://github.com/joerohde/dotfiles/tree/jrohde/its-a-trap
If you wish to pursue the repro, here's a quick summary.

Repros in OSX and WSL Ubuntu 22.04 for me.

It uses dotbot.  In a scratch user directory you can run ./install to link everything into ~/.

Pass --update to ./install to avoid installing extra tooling it finds missing (pygments/tmux/coreutils)

There is a script that get's sourced  local/bin/cd.sh.  This is the root of all evil.  It's on the hacky side. The function cd_debug_trap is small and is (I believe) the only relevant part.  I should stop using it, but it's sooooo ingrained into my muscle memory.

To verify: Removing [[ -r "$HOME/.local/bin/cd.sh" ]] && . "$HOME/.local/bin/cd.sh" from .bashrc makes everything work great with none of the above mentioned problems.

One hack, that seems irrelevant is that cd.sh uses debug trap directly, but also detects and uses the pre-exec infrastructure if it has been loaded (to not break iTerm2's shell integration).

The debug branch just build an array of what  commands were that triggered the trap and print them at the start and end of building the prompt.

I appreciate the time and effort going into this feature.  It's becoming a shockingly advanced embedded shell environment.

@joerohde thanks again, planning on tackling this in June

I use just merged in a fix for this. It would be great if someone could help verify in tomorrow's insiders build as I'm not normally a user of bash-preexec.

Still some problems around $?.  Very simple repro:
clean environment. Mine are:
BASH_VERSION='5.1.16(1)-release'
TERM_PROGRAM_VERSION=1.69.0-insider

use this .bashrc:
#!/bin/bash
shopt -s extdebug

For me (In WSL, repros in plain OSX):

Without extdebug

If extdebug works, then this would be the next simplest test (I think).  Same clean environment.  The following .bashrc
#!/bin/bash

shopt -s extdebug

function my_debug_trap()
{
    false
    return 0
}
trap my_debug_trap DEBUG

Are there verif steps for this?

This bug has been fixed in the latest release of VS Code Insiders!
@joerohde, you can help us out by commenting /verified if things are now working as expected.
If things still don't seem right, please ensure you're on version 9cf2fabdd600c7d8e3230803acb246405321e8dd of Insiders (today's or later - you can use Help: About in the command palette to check), and leave a comment letting us know what isn't working as expected.
Happy Coding!

With the more complicated trap my_debug_trap DEBUG scenario, the decorations don't seem to show blue and red anymore.

I realize that in the screenshot I forgot to add (), but that didn't make a difference.

@rzhao271 what is your exact debug trap when that happens?


Native ads support

Hello.
Is there any way to support different viewTypes that doesn't extends Model like AdExpressViewHolder ?
The problem is that in your implementation onCreateViewHolder must return something that extend Model class
ViewHolder<? extends ExampleModel> onCreateViewHolder
Is it possible in my situation ?
@Override
    public RecyclerView.ViewHolder onCreateViewHolder(ViewGroup parent, int viewType) {
        final View v = inflater.inflate(viewType, parent, false);
        if (viewType == VIEW_TYPE_COLLAPSED) {
            return new CollapsedVH(v, this);
        } else if (viewType == VIEW_TYPE_EXPANDED) {
            return new ExpandedVH(v, this);
        } else if (viewType == VIEW_TYPE_AD_EXPRESS) {
            return new AdExpressViewHolder(v);
        } else return null;
    }

Hi! At the moment this is not possible. The Adapter has to enforce that type constraint to allow for the simplified binding functionality. However there are ways to still have the simplified binding feature and allow for any type of ViewHolder to be used. I am going to look into this at some point in the near future. In the meantime this issue is going to stay open until I either implemented this change or decided not to implement it at all.


fixed auto_annotation for multijob tasks

Fixed error like
django.db.utils.IntegrityError: duplicate key value violates unique constraint "engine_labeledshape_pkey"
DETAIL:  Key (id)=(13663) already exists.

for multijob tasks

@azhavoro , please create an issue which exhaustive description of the problem and put here Resolve #.... Also need to add a corresponding note to CHANGELOG.md file.

@azhavoro , the patch is good. Just need to be sure that we put necessary information into CHANGELOG.md.


made requiring adaptor classes dynamic

Fixes #
BigDecimalConverter which should store this data type as String in the database.
This pull introduces/changes:

additionally made adapter class loading more dynamic
added a way to specify adaptor classes directly without assigning a type to them

Codecov Report

Merging #1505 into master will decrease coverage by 0.01%.
The diff coverage is 84%.

@@            Coverage Diff             @@
##           master    #1505      +/-   ##
==========================================
- Coverage   96.81%   96.79%   -0.02%
==========================================
  Files         205      205
  Lines       12669    12676       +7
==========================================
+ Hits        12265    12270       +5
- Misses        404      406       +2

Impacted Files
Coverage Δ

lib/neo4j.rb
97.93% <ø> (-0.05%)
:arrow_down:

...ntegration/type_converters/type_converters_spec.rb
100% <100%> (ø)
:arrow_up:

lib/neo4j/shared/type_converters.rb
95.34% <50%> (-0.45%)
:arrow_down:

lib/neo4j/session_manager.rb
79.06% <81.81%> (-0.94%)
:arrow_down:

Continue to review full report at Codecov.

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

@cheerfulstoic what's your take on too long spec blocks?

I've used this in other projects:
Metrics/ModuleLength:
  Exclude:
    - 'spec/**/*'

I think it would be just fine here.

There is a negative coverage delta for 2 files due to the removal of covered lines. No touched lines are missing a test coverage. And of course a huge delta due to the removal of specs from the statistics which were distorting the result anyway.

I have added a deprecation warning for embedded_db so I am not sure if this makes it more than a bug fix now.

@cheerfulstoic could we move ahead on that? It is not ideal to point our production to forks and keep synching the fork with upstream.


Merge annsk.alignment

I tried to merge this extension to Transformer but i can't. Can you do it pls?

Why would you want to merge another extension when you can just install it separately?

Well, I just want to keep the amount of extension i have to install to a minimum and less settings i have to find. Additionally, the "Align to Cursor" kinda broken.

You can create your own extension pack to better help manage your own installs.  I did that for myself as an example - https://marketplace.visualstudio.com/items?itemName=dakara.dakara-editor-core-pack
The Align To Cursor aligns only text to the right side of the cursor to the position of the cursor where there is a gap of empty space.  It doesn't parse the text and try to figure out the syntactic character separators.


Vtol new tailsitter

rotate attitude in fw attitude control module if vtol type is tailsitter
added config and mixer file for a tailsitter in quad x configuration

@LorenzMeier Please review shortly and then merge.


1.19.0

Any plans to port on 1.19.0?

Sure! rewrite the mod so you'll have it

You are awesome! Thank you a lot!


On MacOS getting error : channel 0 closed: 'executing job failed: No such file or directory'

Hi I'm getting the error on mac

channel 0 closed: 'executing job failed: No such file or directory'

I ran
dotnet new sln
dotnet sln add myproject.csproj
My vimrc look like the following
let g:OmniSharp_server_use_mono = 1
let g:OmniSharp_server_stdio = 1
let g:OmniSharp_proc_debug = 1
let g:OmniSharp_loglevel = 'debug'

When I look at messages I get

DEBUG: 'Using vim job_start to start the following command:'
DEBUG: ['mono', '/Users/Me/.omnisharp/omnisharp-roslyn/OmniSharp.exe', '-s', '/Users/Me/dev/test/carconfig.api/carconfig.api.sln']
channel 0 closed: 'executing job failed: No such file or directory'

It seems like it's downloading and trying to execute the windows version of omnisharp-roslyn?

Ok I think mono is used to execute the exe file.. Tried to run this manually it seems to work

Seems this is the error from above
yToken=1488e028ca7ab535' or one of its dependencies.```

Seems there is a thread an issue here regarding it
https://github.com/OmniSharp/omnisharp-roslyn/issues/1536

Can you try removing the g:OmniSharp_server_use_mono line from your .vimrc, restarting vim, then run :OmniSharpInstall again? This will download the osx version mentioned in the linked issue - see if that helps?
I don't have a Mac to test on, it has been necessary for Mac users in the past to use the mono version, but perhaps not with stdio?
If that doesn't work, you could try adding the g:OmniSharp_server_use_mono line back in again after downloading the osx version, and see if that combination works. If so, I'll update the install command to prevent Macs from downloading the mono version.

Thanks Nickspoons, I tried that yesterday...That did the trick. I was asking it to work with the separately installed version of mono rather than the bundled version. Also, I don't think I had the latest version of Omnisharp-vim installed.. I tried it a month or two back so I needed to run Plug-update.. When installing it was missing the SQL dependencies.. When I updated Omnisharp and removed the setting you suggested it worked like a charm..
Thanks for your help 🥇
Must say it's awesome! Loving it!!

Glad to hear you got it working! There's always some magic combination of OS/OmniSharp-roslyn/mono/msbuild that works ... but it's unfortunately not always easy to find it! I think we're getting better at setting/suggesting the correct defaults but we're obviously not quite there yet. But it's good to know that the stdio version works well without g:OmniSharp_server_use_mono on mac, that's one less installation step.


Add lexer code

Add in the current lexer code.

[x] The commit message follows our guidelines.
For bug fixes and features:

[x] You tested the changes.
[ ] You updated the docs or changelog.

Related issue (if applicable): #10
What kind of change does this PR introduce?
Just adding in the lexer code for the parser.

Great work. The only change I'd request for the language would be the use of and, or, and not over C-style conditionals, for consistency with the rest of the language: it's intended for writers, not programmers, and everything else looks like English.
There are some things I'd rename for educational purposes, but I'll take care of that directly once you made the above change. And then it'll be good to merge, so you can move to the parser as soon as you changed these keywords.

I've made the change to the conditionals' syntax. I'll start work on the parser now.


Typo in ToOptions func in expose cmd

There is a typo in ToOptions func in expose cmd.
dryRunStratergy should be dryRunStrategy.

Thanks for the PR. Going to close this to keep our tracker clear.
/close


research Performance Analyzer & RCA

research the following items:
architecture of PA plugin; collectors and metrics in PA/RCA; how to collect data from other nodes in PA/RCA;
still need to research:
how is the analysis process implemented

finished：
read the design doc and high-level code of RCA; finish the RA/RCA presentation doc with hailong


[Tab] Style prop is not functional

Problem Description
The style prop on the "Tab" component does not do anything. The "style" prop is still defined in Tab.propTypes, and in Tab.render it is extracted from the component props (Tab.jsx:115), but the prop is never used or passed down to child components.
Versions

Material-UI: 0.15.0-alpha.1
React: 0.14.7
Browser: Firefox 44.0

I can make a PR, if you don't mind.


Added az predictor article

Docs Build status updates of commit 4acf95d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azps-7.3.2/az-predictor.md
:white_check_mark:Succeeded
View (azps-7.3.2)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit fee200e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azps-7.3.2/az-predictor.md
:white_check_mark:Succeeded
View (azps-7.3.2)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit f466188:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azps-7.3.2/az-predictor.md
:white_check_mark:Succeeded
View (azps-7.3.2)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 734c88a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azps-7.3.2/az-predictor.md
:white_check_mark:Succeeded
View (azps-7.3.2)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 5e6c1b3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azps-7.3.2/az-predictor.md
:white_check_mark:Succeeded
View (azps-7.3.2)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Black screen since SteamVR update

As of yesterdays steamvr update to 2.2.2 when launching ALVR all seems to work as expected except the screen on the quest stays black once connected. All audio works and controller/environments work(as seen in steams vr view), nothing out the ordinary in logs.
This was not the case before today/yesterdays steamvr update.
Tested on
Manjaro Linux(Arch)
ALVR latest stable 20.5.0
and
ALVR nightly 12-17
.appimage

Downgrading to 2.1.10 makes the issue go away. Here's to hoping Steam doesn't shove yet another broken beta update to their "stable" branch....

Maybe related with #1928?

How to downgrade or access the nightly AppImage? I'm having the same problem, none of the beta branches fix it for me

This is the one that worked for me, on steamvr stable(2.2.1)
https://github.com/alvr-org/ALVR-nightly/releases/tag/v21.0.0-dev00%2Bnightly.2023.12.17


formToModifier not being called on a update form

I have a form which I repurpose for both insert and update of appointment items. I have seperate "time" and "date" items in the schema for appointments, the latter of which is hidden from the form and set with the time, which is a string. (The day is set outside of the form).
This logic was contained in docToForm, so 2.1 broke my form updating. No problem, move the logic into a function and call that from both docToForm and docToModifier, right? I tried that, and now my update field calls neither docToForm or docToModifier.
Schema:
	date: {
		type: Date,
		label: "Date",
		index: true,
		custom: function() {
			return checkDate(this, true);
		}
	},
	time: {
		type: String,
		label: "Time",
 		regEx: /^[0-2]?\d:\d\d [APap]m|M$/
	},

Form:
<template name="insertAppointmentForm">
	{{#autoForm collection=appointmentList doc=currentDoc id="insertAppointmentFormInner" type=currentType}}
...
		{{> afQuickField name='time' value=timePreset type='timePicker'}}
...
		{{> afFieldInput name='date' value=sessionDate type="hidden"}}
	{{/autoForm}}
</template>

I have verified that the form is correctly marked as update via AutoForm.getCurrentDataForForm("insertAppointmentFormInner"). Validation is default submitThenKeyup.
Form JS:
AutoForm.hooks({
	insertAppointmentFormInner: {
...
		formToDoc: function(doc) {
			prepareDocForDB(doc)
		},
		formToModifier: function(doc) {
			console.log(doc);
			prepareDocForDB(doc)
		},
...
   }
});

prepareDocForDB = function(doc) {

	if (typeof doc.time === "string") {
		var datestring = moment(Session.get("date")).format("YYYY-MM-DD ") + doc.time;
		doc.date = moment(datestring, "YYYY-MM-DD hh:mm A").utc().toDate();
	}
	return doc;
}

I have set breakpoints on both of the prepareDocForDB calls on both Firefox and Chrome, never got called during an update operation.
Thanks so much for your time and hard work! :)

I am facing the same issue using the method-update form type.

+1

+1

+1
Hooks = {
  form: {},
  global: {
    before: {},
    after: {},
    formToDoc: [],
    docToForm: [],
    onSubmit: [],
    onSuccess: [],
    onError: [],
    beginSubmit: [],
    endSubmit: []
  }
};

I think this is the problem. there is no "formToModifier" hook.
This feature should have been tested.

+1

+1

+1

+1

The case for me as well, formToModifier is not called for "method-update" form type. The workaround is to amend modifier in before hook, e.g.:
...
   editLocationForm: {
     before: {
       "method-update": function(modifier) {
         var latlng = modifier.$set.location.split(',');
         doc.$set.location = { type: "Point", coordinates: [ parseFloat(latlng[1]), parseFloat(latlng[0]) ] };
         return modifier;
       }
     },

Same bug here with a quickForm update. Thanks @kabalin for the workaround.

@laurentpayot this was fixed with #1058

I haven't released yet but hopefully soon. Need to get some things working in devel branch.

+1
Same bug for basic type="update" form, formToDoc hook not called, skipped altogether

@aldeed - reproduction repo here: https://github.com/pcuci/autoform-practice
There another issue!
formToDoc gets called on type="update" forms instead of formToModifier - but only for the text field (tags field in the repo)
The range input doesn't trigger formToDoc nor formToModifier on update.

+1

+1 @ 5.3.2

@aldeed is 5.3.2 coming soon? meteor add  won't let me install anything un-semver-like, and there don't seem to be any published forks including this fix (not that I think using a fork is a very good idea).
For now... @kabalin's workaround worked well. I thought it wouldn't because before is supposedly run after the form is deemed valid. I guess the form being valid and the values being valid against the schema are two different things, and it clearly runs before validation of the underlying schema happens. My spin on it was:
before: {
  update: function (modifier) {
    return CommonHooks.formToModifier(modifier);
  }
}

+1
having the same bug as @pcuci
formToDoc not fired on update.

Pretty sure this was fixed a few releases ago.

@aldeed, I have the same bug as @pcuci
My form:
+quickForm(id="editSchool" collection="School" type="update" doc=editingDoc fields="name, address, phone, workBegin, workEnd, description" buttonContent=false)

My hooks:
AutoForm.hooks
  editSchool:
    formToDoc: (doc) ->
      console.log doc
      if doc.workBegin
        time = doc.workBegin.split ':'
        date = new Date()
        date.setHours time[0], time[1]
        doc.workBegin = date
      if doc.workEnd
        time = doc.workEnd.split ':'
        date = new Date()
        date.setHours time[0], time[1]
        doc.workEnd = date
      return doc

If I remove type="update" from quickform, formToDoc hook will trigger as expected.


mobile: Envoy Mobile shouldn't terminate on malloc failure

The application should decide how new/malloc failures are handled.

/assign @alyssawilk


Multi-arch image build

This PR contains the following changes:

In the builder image we use the native platform (linux/amd64) to cross compile for the target platform (linux/arm64). And then copy the cross compilation result to the final base image for the target platform (linux/arm64). This approach is way more faster than doing everything with the target platform. The reason is that when we compile something in an arm64 image on amd64 platform, we are using an emulator which has huge performance penalty. Ref reading: https://www.docker.com/blog/faster-multi-platform-builds-dockerfile-cross-compilation-guide/
Overhaul the image build process for kubeval

One dependency (https://github.com/instrumenta/openapi2jsonschema) is lack of maintenance and can't be installed on arm64 platform. So we generate the json schema beforehand and bake them in the image.
Kubeval CLI is lack of maintenance, it doesn't provide a build for arm64. We compile it by ourselves.

There are a few functions that download other binaries e.g. render-helm-chart. They download the correct binary now.

The motivation to speed up the image building process is that it seems the GCP auth token used in our release pipeline won't last multiple hours and it will cause some image push to failing when it expired.

The e2e test has been fixed on HEAD.
PR is rebased on top of HEAD.


Kong Linux command client did not run and return data

Summary
I installed kong on my Ubuntu 18.04 bionic as intructions:
https://docs.konghq.com/install/ubuntu/?_ga=2.27228475.749820824.1568107389-1191384212.1567663353
However, when I run Kong command on the command line it did not return anything
I also try to run Kong commnand on Kong Docker container by official image and the output was the same.
Steps To Reproduce

Install Kong: https://docs.konghq.com/install/ubuntu/?_ga=2.27228475.749820824.1568107389-1191384212.1567663353
Open cmd and run, nothing returned in the cmd

kong

Install Docker
Run Kong docker container on https://hub.docker.com/_/kong
Run kong and nothing returned

Additional Details & Logs

Kong version (1.3.0)
Linux version (bionic 18.04)
I did not know what is the cause

try kong -vv for verbose output

try kong -vv for verbose output

I tried but the result was still the same. I re-install Ubuntu but the error is still there

try kong -vv for verbose output

I tried and also re-install Ubuntu the the result is still the same

output of:
whereis kong
kong version
sudo kong

I have a high degree of confidence that Kong 1.3.0 works on Ubuntu 18.04 as we specifically test that our releases can be installed / ran and not seeing a ton of similar reports

I have changed CPU to Intel Core and it worked. I have also tested on other PCs and kong command worked as usual on those computers. But the PC with AMD CPU as above did not

I tried this on a m5a on AWS and wasn't able to reproduce
ubuntu@ip-172-31-69-229:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.2 LTS
Release:        18.04
Codename:       bionic

ubuntu@ip-172-31-69-229:~$ uname -a
Linux ip-172-31-69-229 4.15.0-1044-aws #46-Ubuntu SMP Thu Jul 4 13:38:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

ubuntu@ip-172-31-69-229:~$ curl -fsSLo kong.deb https://bintray.com/kong/kong-deb/download_file?file_path=kong-1.3.0.bionic.amd64.deb

ubuntu@ip-172-31-69-229:~$ sudo dpkg -i kong.deb
Selecting previously unselected package kong.
(Reading database ... 56638 files and directories currently installed.)
Preparing to unpack kong.deb ...
Unpacking kong (1.3.0) ...
Setting up kong (1.3.0) ...

ubuntu@ip-172-31-69-229:~$ kong version
1.3.0

As we can't reproduce this issue, and

I have changed computer with to Intel Core CPU and it worked

I'm concluding that this was due to a local machine's configuration and closing this. Please reopen if needed.


Add accessibility testing with Quail

@bblake suggests we check out Quail (https://github.com/quailjs/quail) to add accessibility testing.

grunt-quail may prove a useful starting place, but it appears to be limited to scanning static HTML.

Closing old issues that I do not expect to be tackled in the context of this project.


Unable to set a ConnectionTimeout on Invoke-DbaQuery

Before submitting a bug report:

[√] Ensure you are able to reproduce it on the latest released version (we release often)
[√] Verified this bug is not already reported in an issue
[√] Verified errors are not related to permissions
[√] Can reproduce in a clean PowerShell session (clean = powershell -NoProfile)

Steps to Reproduce
PS > Invoke-DbaQuery -ConnectionTimeout 15 ...

Expected Behavior

Actual Behavior
Invoke-DbaQuery : A parameter cannot be found that matches parameter name 'ConnectionTimeout'.
Environmental data

PowerShell: 5.1

Other thoughts
Looks like Connect-SqlInstance is what gets called by Invoke-DbaQuery and already has a StatementTimeout param that may work.
As noted: for advanced connection options, you can use Set-DbatoolsConfig  or create the reusable connection with Connect-DbaInstance
I would expect ConnectionTimeout to be common enough that it exposed on Invoke-DbaQuery

thank you for the report! 🙇  This will be better handled by
Get-DbatoolsConfig *connect*
Set-DbatoolsConfig -FullName sql.connection.timeout -Value 30

doing it this way is similar to the way it's done in SSMS

👍


Add Widget feature

Adds widget feature, as per #1161

Working on the UI for the feed selection flow, and the styling for the widget. Will be ready to merge soon.

Looking forward to this!

@samuelclay the feature is working, but I am having some issues with a synchronization race condition. Likely a few line fix, but finding where that needs to go has been challenging.
Where would you like my dev resources to be spent over coming days?

I think finishing up this feature would be a good use of time. Did you have any other issues in mind to work on before finishing this one?

Sounds good. Was just seeing the activity on the missing image task, and wanted to make sure

Let's get to that one next, since it's a long standing issue.

@samuelclay I believe this is ready

Nice! So how do I test this out? I did a cursory search but couldn't find where to add it.

@samuelclay it will have to be added via your homescreen, should be a long press -> widgets I think

Let me know your feedback

Firs thought, this should absolutely prioritize folders over feeds. name them (so they are in alphabetical order and folders are on top):
Folder: [Title]
Site: [Title]

Also, tapping stories does nothing but show the tap fade action.

Is it possible to add an icon before the folder/site title?

Tiny image previews would be nice as well. This is great stuff!

Great feedback--tapping should work but I'll investigate that. As well as the icon, and folder feeds in the selections!

First thought, this should absolutely prioritize folders over feeds. name them (so they are in alphabetical order and folders are on top):
Folder: [Title]
Site: [Title]

Is this what you have in mind?

Yep, just remove the "Feed: " part.


Use FileVersion as suggested version number?

Description of the new feature/enhancement
I just found something out and even if it can't make 2.0, I think it's worth noting for the future if anyone feels like implementing it (maybe I will)..
The FileVersion attribute is often the same as the ARP version number, and it's super easy to get in PowerShell.
S C:\Users\easton> iwr https://github.com/git-for-windows/git/releases/download/v2.33.1.windows.1/Git-2.33.1-64-bit.exe -OutFile .\git.exe
PS C:\Users\easton> (Get-Item .\git.exe).VersionInfo

ProductVersion   FileVersion      FileName
--------------   -----------      --------
2.33.1       ... <IP_ADDRESS>     ... C:\Users\easton\git.exe

PS C:\Users\easton>

YamlCreate should be able to do this for the user, so that they can hand it a URL (or URLs) for an update and it can handle the rest. wingetcreate already does something like this too.
Proposed technical implementation details (optional)
Just do Get-Item on the file, and look to see if ProductVersion/FileVersion are set. If they are, either suggest that they use that number, or if it's a quick update, then use that number by default.

Good idea...👍

It would require a bit of rework to incorporate this, but I love the idea. I'll add it to the roadmap


Remove duplicated notebook

https://github.com/courtois-neuromod/anat-processing-book/blob/c3dd7c66ba345ef0fd9abf40cff7effda636228f/source/_config.yml#L45

Issue resolved with: 209578d9e0087ea77898e10752d9d75ce3dd747f


Found a newer place for this user: skipping update

I have the adapter running for some months (years?) without problems. It is still working fine.
But now I am receiving the following warnings. It is right that a newer place has been found because it is moving. What does it mean and how can I get rid of it? The google maps function is turned off.
`

places.0
2020-12-03 08:30:40.774
warn
(20098) Found a newer place for this user: skipping update

places.0
2020-12-03 08:30:33.413
warn
(20098) Found a newer place for this user: skipping update

places.0
2020-12-03 08:30:26.278
warn
(20098) Found a newer place for this user: skipping update

`
Edit: the tesla adapter sends every 5sec the location. Too often perhaps?

My guess was right. The other Adapter was sending with too much frequency, every 5 sec.
With a script I now send the data only every 15sec. Now working without that warning.
Perhaps it should be added a suggestion in the places adapter description saying that the frequency should not be less 10sec for example.


Update to readme and contributor guidelines

GitHub issue: #266
Added a short version of the guidelines to the readme. Guidelines updated to use simplified branching model, and added info on release cycle.
Please review for correctness. I'm not 100% sure about the organization of this either: if you have suggestions for changes to make it all easier to digest by all means go ahead.

Looks fairly good, just a few comments inline.

I merged this using GitHub's "squash and commit" option, instead of the regular merge commit. The advantage of this is that it makes cherrypicking easier, and we get a simpler history view. The downside is that we lose the original commit history (and my local git client gets confused about local branches and whether or not they are merged or not).

Losing the commit history is cleaner to browse, but hopefully it won't result in more local merge conflicts.
I also notice that the Signed-Off tag isn't on the squashed/merged commit. Is it possible to have it there (hopefully without having users type it out, which is prone to spelling mistakes)? It may be a little confusing having users always use -s but then not have the signed-off by (which Eclipse seems to require) in the final squashed commit.
I also use -S (gpg signing) which is also wiped by squashing, but that isn't as big an issue in the long term given the other inbuilt safeguards that Git has.
Both -s and -S could be preserved if we change the instructions to include "git rebase -i master" and "git commit --amend -as" or "git commit --amend -asS" for them to use locally after the pull request was approved but before merging. However, it is difficult to explain the rebase process, and would be much simpler to use the Github squash if it can preserve "-s" that Eclipse requires.

NB I am using squashing for merges, not rebasing. They're different things!

Losing the commit history is cleaner to browse, but hopefully it won't result in more local merge conflicts.

I don't think it will - unless people do local changes on their own master branch directly (but in that case you'd get merge conflicts no matter what merging technique we use).

I also notice that the Signed-Off tag isn't on the squashed/merged commit. Is it possible to have it there (hopefully without having users type it out, which is prone to spelling mistakes)? It may be a little confusing having users always use -s but then not have the signed-off by (which Eclipse seems to require) in the final squashed commit.

Well we don't get the signoff in the 'normal' merge commit either. I don't think I can easily configure this. However, I should point out that the way I'm aiming for this to work is that the commit message includes not just the issue number, but also the Pull Request number. This actually happens automagically if I use the GitHub squash-and-merge - and this gives you an automatic link back to the original PR, which still includes the full commit history.

I know they are technically separate, but "rebase -i" is how you would practically do squashing locally, and rebasing onto the current tip/head is the simplest way to rebase locally.

Is the full original commit history still visible if someone deletes the branch or their repository? I haven't kept up with the way that the github pull request branches work to know the specifics of that.
Even though the merge doesn't have signed-off it is still present on the original commits if we don't use squash and merge.

Is the full original commit history still visible if someone deletes the branch or their repository? I haven't kept up with the way that the github pull request branches work to know the specifics of that

Ah good point - I was looking at this particular PR, but wasn't considering PRs from forked repos. Hm, probably not.
Perhaps I should be a little less keen to use squashing everywhere. My main motivation was to have easier cherrypicking. But to be fair using Sourcetree, at least, I've found that selecting multiple commits for cherrypicking is still quite straightforward.

Shall we continue this discussion in issue #266 ?


Ember form attribute binding (1.13.3)

This adds form attr binding back.
This version of Emberx-select can only run on ember 1.13.3 +!

Any ETA for the new release?

Probably around tomorrow. I want to get a blog post out about it since there will be compatibility issues for older ember users.

has this been released?

@lholmquist I ended up writing a component. It's not that much code to get a <select>.


Failed to import iconoir-react in production mode

Describe the bug
When I build an application which uses iconoir-react package for production and try to run remix-kit preview, I get this error:

What I tried:

Added 'type': 'module' in package.json
Added 'iconoir-react': 'iconoir-react/dist/esm' in resolve.alias
Changed from server.production.js to server.production.mjs
Added serverDependenciesToBundle: ['iconoir-react'] in remix.config.js

The development server works like a charm, but production preview throws. Also the same remix project using the default build system works too.
Reproduction
No response
Steps to reproduce

Create a remix-kit project
Add iconoir-react
Build for production
Try to run remix-kit preview

System Info
System:
    OS: macOS 13.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 108.45 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.12.1 - ~/.asdf/installs/nodejs/lts-hydrogen/bin/node
    Yarn: 1.22.19 - ~/.asdf/shims/yarn
    npm: 8.19.2 - ~/.asdf/plugins/nodejs/shims/npm
  Browsers:
    Firefox: 107.0.1
    Safari: 16.2
  npmPackages:
    @remix-kit/cli: ^0.1.2 => 0.1.2
    @remix-kit/react: ^0.1.2 => 0.1.2
    @remix-kit/vite: ^0.1.2 => 0.1.2
    @remix-run/dev: ^1.9.0 => 1.9.0
    @remix-run/express: ^1.9.0 => 1.9.0
    @remix-run/node: ^1.9.0 => 1.9.0
    @remix-run/react: ^1.9.0 => 1.9.0
    @remix-run/serve: ^1.9.0 => 1.9.0
    @remix-run/server-runtime: ^1.9.0 => 1.9.0

Used Package Manager
pnpm
Validations

[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a RemixKit issue and not a Remix specific issue. For example, if it's a Remix related bug, it should likely be reported to remix instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion.

Really appreciate the bug report @ceopaludetto! We'll get to improving this as part of the preview feature re-think in the short-term roadmap here.


Badge does not match score

Hi,
My score is 100% but the badge is stuck on B:
https://goreportcard.com/report/github.com/michelpmcdonald/go-peat
I did create and completely destroy the repo a few times in git hub using the exact same repo name, not sure if that matters...
thanks

@michelpmcdonald thanks for bringing this to our attention - there was a bug in some caching code we're testing on the server. It should be fixed now, could you take another look?

Looks good on goreportcard.com, still shows as B score on github, but guessing that's nothing to do with goreportcard.
thank you


File opens back after closing

Have a TS and TSLint error.
Open Problems view and Select TS Error
Close the file now

🐛 It opens back

Verified in sources


When to share the code

hello, @hehefan   thanks for your paper, i'm interested in the implementation  ``EMD``` loss , so when do you share your code?  thanks.

sorry for repeated submissions, because the  Network response is too slow.


[INFO] Upcoming game updates with archnemesis UI changes

GGG has announced archnemesis UI changes for the near future, including permanent recipe indicators (colored frames). This should not affect this tool in any way. If more aspects of the UI get changed, the tool may not work immediately after the update is published. If that is the case, there may be some hours of downtime for this tool since game updates usually come out at while I'm sleeping.
I'm asking you to keep this in mind and keep issues submissions to a minimum -- check if there already is a submission and confirm the issue in the comments. If you want to be even more helpful, you can try to summarize what changed in the UI so that I can adapt the tool even faster in the following morning.
In the unlikely event that GGG increases inventory capacity or changes the fundamentals of the inventory, adaption will of course take longer. I would also take this opportunity to update the scanning method, which would entail re-training on your end.

Hey i should propably create new thread but i dont think its worth it for problem that small https://i.imgur.com/d8Dn6DF.jpg is this possible for this red cursor to be like it should ? in the middle ? im using 1080 an was waiting for an update but i never came so maybe you could tell me how i can fix it/

I can change that for the next release. It was just a placeholder from when I started, and then I never touched it again -- that's why it looks so ugly.

I can change that for the next release. It was just a placeholder from when I started, and then I never touched it again -- that's why it looks so ugly.

i mean even the images in recognition folder looks weird ? im 100% sure that image like that https://i.imgur.com/o0ZVUSN.jpg (echoist) will not work in pixel search or maybe im wrong ?

I don't know how this could have happened. Which resolution are you running?

https://i.imgur.com/iy3Ghck.jpg

(I was testing previously in windowed fullscreen but couldn't get the overlay to show but after i deleted and unpacked again it worked just now 😂)
Okay now it actually works like it should and its even skipping the already "recognized" images i guess mb for running in windowed thanks for your help, you did an amazing job with that tool ❤


Fix default function "greater than or equal".

The default function for "greater than or equal" did not use >= for comparison.
Instead == was used. This led to wrong results.

Well that's pretty embarrassing.
Thanks!

You're welcome.
Thanks for the fast merge :)


Fixing dataset duplication

Fixes https://github.com/CartoDB/cartodb/issues/8643.
Fixes https://github.com/CartoDB/cartodb/issues/8640.
Thanks @iriberri and @rafatower.

:flushed: I would've fixed it myself if I knew where
:+1:
Thanks a lot! :smile:


destroy infra aws: delete network LBs and reduce dependency error noise

What this PR does / why we need it:
VPCs are building up because destroy infra aws currently only removes classic ELBs via ELBv1 API.  The ELBv2 interface lists NLB.  The PR adds a removal path for NLBs.
There is also a drastic cleanup in dependency error logging.
New example output
./bin/hypershift destroy infra aws --aws-creds=$HOME/hypershift/aws-creds --infra-id=sjenning-dev --region=us-west-1 --base-domain=hypershift.sjennings.me
2022-04-12T23:01:09-05:00       INFO    Detached internet gateway from VPC      {"gateway id": "igw-016b2a17ae4c68fbb", "vpc": "vpc-0e0a46a3513d23cd3"}
2022-04-12T23:01:09-05:00       INFO    Deleted internet gateway        {"id": "igw-016b2a17ae4c68fbb"}
2022-04-12T23:01:11-05:00       INFO    Deleted VPC endpoints   {"IDs": "vpce-074e6195d7bd8821e"}
2022-04-12T23:01:12-05:00       INFO    Deleted private hosted zone     {"id": "Z08189712MUEPHMU9K7PD", "name": "example.hypershift.local."}
2022-04-12T23:01:13-05:00       INFO    Deleted private hosted zone     {"id": "Z0667350F4T3T89XW4SX", "name": "example.hypershift.sjennings.me."}
2022-04-12T23:01:13-05:00       INFO    Deleted route from route table  {"table": "rtb-06f125dd4dbbb8781", "destination": "<IP_ADDRESS>/0"}
2022-04-12T23:01:13-05:00       INFO    Removed route table association {"table": "rtb-06f125dd4dbbb8781", "association": "rtb-06f125dd4dbbb8781"}
2022-04-12T23:01:14-05:00       INFO    Deleted route table     {"table": "rtb-06f125dd4dbbb8781"}
2022-04-12T23:01:14-05:00       INFO    Deleted route from route table  {"table": "rtb-0dcdc311509e75645", "destination": "<IP_ADDRESS>/0"}
2022-04-12T23:01:14-05:00       INFO    Removed route table association {"table": "rtb-0dcdc311509e75645", "association": "rtb-0dcdc311509e75645"}
2022-04-12T23:01:14-05:00       INFO    Deleted route table     {"table": "rtb-0a60b3593f0829881"}
2022-04-12T23:01:14-05:00       INFO    WARNING: error during destroy, will retry       {"error": "deleting NAT gateway nat-058a5d8cb8dafdd5b"}
2022-04-12T23:01:22-05:00       INFO    WARNING: error during destroy, will retry       {"error": "NAT gateway nat-058a5d8cb8dafdd5b still deleting"}
2022-04-12T23:01:26-05:00       INFO    WARNING: error during destroy, will retry       {"error": "NAT gateway nat-058a5d8cb8dafdd5b still deleting"}
2022-04-12T23:01:31-05:00       INFO    WARNING: error during destroy, will retry       {"error": "NAT gateway nat-058a5d8cb8dafdd5b still deleting"}
2022-04-12T23:01:37-05:00       INFO    WARNING: error during destroy, will retry       {"error": "NAT gateway nat-058a5d8cb8dafdd5b still deleting"}
2022-04-12T23:01:41-05:00       INFO    WARNING: error during destroy, will retry       {"error": "NAT gateway nat-058a5d8cb8dafdd5b still deleting"}
2022-04-12T23:01:46-05:00       INFO    WARNING: error during destroy, will retry       {"error": "NAT gateway nat-058a5d8cb8dafdd5b still deleting"}
2022-04-12T23:01:51-05:00       INFO    WARNING: error during destroy, will retry       {"error": "NAT gateway nat-058a5d8cb8dafdd5b still deleting"}
2022-04-12T23:01:56-05:00       INFO    WARNING: error during destroy, will retry       {"error": "NAT gateway nat-058a5d8cb8dafdd5b still deleting"}
2022-04-12T23:02:02-05:00       INFO    WARNING: error during destroy, will retry       {"error": "NAT gateway nat-058a5d8cb8dafdd5b still deleting"}
2022-04-12T23:02:06-05:00       INFO    Revoked security group ingress permissions      {"group": "sg-01eaaede00f5b4a52"}
2022-04-12T23:02:07-05:00       INFO    Revoked security group egress permissions       {"group": "sg-01eaaede00f5b4a52"}
2022-04-12T23:02:07-05:00       INFO    Deleted security group  {"group": "sg-01eaaede00f5b4a52"}
2022-04-12T23:02:07-05:00       INFO    Revoked security group ingress permissions      {"group": "sg-0d46ec5a904cf1f8f"}
2022-04-12T23:02:07-05:00       INFO    Revoked security group egress permissions       {"group": "sg-0d46ec5a904cf1f8f"}
2022-04-12T23:02:08-05:00       INFO    Deleted subnet  {"id": "subnet-07d5efadd67da63e8"}
2022-04-12T23:02:08-05:00       INFO    Deleted subnet  {"id": "subnet-00239b325455ffaf7"}
2022-04-12T23:02:09-05:00       INFO    Deleted VPC     {"id": "vpc-0e0a46a3513d23cd3"}
2022-04-12T23:02:09-05:00       INFO    Successfully destroyed infrastructure

Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #
Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/lgtm


Implement CompactChip

Implement CompactChip.
Redlines

Expected output:

Implementation in compose-material module, matching the redlines;
Implementation should use CompactChip from wear compose material library;
Previews in the debug folder for each variant;
Snapshot tests for:

each variant;
text overflow;
large font scale (TestHarness(fontScale = 1.18f)));
rtl (TestHarness(layoutDirection = LayoutDirection.Rtl)));
a11y

Can I help in implementing this one?


Rawscore Prediction in R package

I tried predict.lgb.Booster method in R package for prediction with and without setting rawscore=TRUE.
But the prediction results can't verify each other.
Could someone explain this a little bit? Maybe I understand it wrong.
# Package and Function
library(lightgbm)
Sigmoid <- function(x) 1 / (1 + exp(-x))
Logit <- function(x) log(x / (1 - x))
# Dataset
data(agaricus.train, package='lightgbm')
train <- agaricus.train
dtrain <- lgb.Dataset(train$data, label=train$label)
data(agaricus.test, package='lightgbm')
test <- agaricus.test
# Training
params = list(objective = "binary",
              learning_rate = 0.01, num_leaves = 63, max_depth = -1,
              min_data_in_leaf = 1, min_sum_hessian_in_leaf = 1)
model <- lgb.train(params, dtrain, 100)
# Prediction
prob <- predict(model, test$data)[1]
logodds <- predict(model, test$data, rawscore = TRUE)[1]
Logit(prob) == logodds

@yanyachen
fix this at latest version.
However, Logit(prob) == logodds this may is still not True, due to precision problem.


public-vm: define a "public input"-like mechanism in backend

Is this for powdr? If yes then it's done


[sokol_imgui] add  the optional backend interface for font management

As a happy sokol_imgui user, I am humbling proposing this PR. It splits the font texture creation in a API function and add a function for the font texture destruction. Those functions are  considered optional function of the imgui backends.
For instance they are implemented for opengl3 on the main imgui repo:
https://github.com/ocornut/imgui/blob/659fb41d0a23efbb9ea6cf74f51ecae0a51575b5/backends/imgui_impl_opengl3.h#L39C1-L42C3
I find those functions are useful in two cases:

when testing different fonts raterization config,  it is convenient to recreate the texture dynamically. The imgui's author provides an example of such application: https://gist.github.com/ocornut/b3a9ecf13502fd818799a452969649ad
when creating non default font, this allows to remove the boilerplate of uploading the font on GPU for the user of sokol_imgui.

Does this proposal make sense?

Good idea! But I wonder if we should make create-fonts function a bit more flexible by passing some data in.
For instance, it would be nice if I could replace this code block in the imgui-highdpi-sapp.c sample which sets up a TTF font texture with the new function:
https://github.com/floooh/sokol-samples/blob/6a03725117ce0175a45fa2d0c51ad3272c955cb5/sapp/imgui-highdpi-sapp.cc#L45-L67
...but as you can see here I'm also using a different sampler with LINEAR filtering:
https://github.com/floooh/sokol-samples/blob/6a03725117ce0175a45fa2d0c51ad3272c955cb5/sapp/imgui-highdpi-sapp.cc#L58-L63
Maybe simgui_create_fonts_texture() should allow to pass in optional parameters (like either a sampler object, or maybe better just a minimal set of sampler params, like min+mag filter?
Or do you solve this same problem currently in some other way? (since you are writing: "...when testing different fonts raterization config...").

This is good suggestion!
I have not played either the sampler in my testing so far, the tool I linked allow to switch from free type to stb_truetype with different parameter but the texture sampler was not one.

I gave it a shot and submitted the sister PR:
https://github.com/floooh/sokol-samples/pull/135

Ok, looking into this PR now.

And merged, many thanks! (also updated the changelog)