Update to Microsoft.Data.SqlClient 2.0.0 breaks a self-contained .NET Core 3.1 ServiceFabric service

We have a ServiceFabric service, which is running the latest .NET Core 3.1. We publish & deploy it as self-contained. It references Microsoft.Data.SqlClient. Using version 1.1.3 everything works perfectly. After updating to 2.0.0, we can not event deploy it to the fabric anymore. Unfortunataly, ServiceFabric gives very little information why. This is what we see:
Service package for manifest 'XXXX' and service package activation ID 'XXXX' is in Error.
		'System.Hosting' reported Error for property 'ServiceTypeRegistration:XXX'.
		The ServiceType was disabled on the node.

It tries that several times and then gives up.
By digging into SF events i was able to find this as well:
There was an error during CodePackage activation.The process/container terminated with exit code:2147516556.

By comparing service package i can see that it used to include sni.dll when using 1.1.3 and then its gone after we updated to 2.0.0. My suspicion is that is the reason why the service fails to start.
And i think is my theory is correct because the service works just fine locally, since sni.dll is availaible on my PC. But it does not exist on the ServiceFabric's VMs.

@dmytro-gokun
Please look at 2.0.0 release notes for breaking changes in SNI naming (introduced in #570). For .NET Core, with 2.0.0 we've introduced our own replacement for runtime.native.System.Data.SqlClient.sni NuGet as well that renames sni.dll to Microsoft.Data.SqlClient.SNI.dll.
If you can provide us a repro, we can investigate more in what your observations are.

@cheenamalhotra Yes, I've read that. And the deployment package contains Microsoft.Data.SqlClient.SNI.dll, so no problem here. The problem is that it somehow still needs sni.dll to load.
About a repro. As I said, it does not reproduce with a Service Fabric Local Cluster on a typical development machine. I can make a repro that you will have to deploy to a real cluster and then you will see it works just fine with 1.1.3 and does not even start with 2.0.0. Will this work for you?

The problem is that it somehow still needs sni.dll to load.

The SqlClient driver does not need the old sni.dll anymore. Can you confirm which component needs the old 'sni.dll' by capturing more logs from your cluster? The above errors don't provide any context.

I can make a repro that you will have to deploy to a real cluster and then you will see it works just fine with 1.1.3 and does not even start with 2.0.0. Will this work for you?

I don't have that environment to deploy but if you can gather logs we can investigate the errors.

The SqlClient driver does not need the old sni.dll anymore.

Do you perhaps know, in which situations it was loaded before? That will help me build a repro.

Can you confirm which component needs the old 'sni.dll' by capturing more logs from your cluster? The above errors don't provide any context.

Well, that's the problem with ServiceFabric. It does not give you any more info than that. I've spent several hours googling and trying different tricks, but that's all I've got :( Any chance, you know anyone who can help with getting more info from SF?

Do you perhaps know, in which situations it was loaded before? That will help me build a repro.

It's a NuGet package reference, and was loaded from runtime.native.System.Data.SqlClient.sni same way as currently Microsoft.Data.SqlClient.SNI.runtime NuGet is loaded. It's a package reference that contains native runtime DLLs. The old package referenced another package implicitly based on arch, but now we added arch specific runtime folders in the same NuGet. But again. the driver doesn't need old sni.dll anymore, so I don't think it will stop you from working if it's absent from your environment.
Have you tried to remove sni.dll from your local dev environment and confirm if you see same error?
If it's related, it should fail locally too, but if not - this error is probably not related to driver and it's dependencies. I also see similar issues on service fabric (same error code): https://github.com/microsoft/service-fabric/issues/868
You can find guide to debug issues here: Debug service errors using the log files, or else contact Service Fabric teams.

So, after further investigation, I was able to find the root cause. It has nothing to do with sni.dll.
The root cause is this exception:
Error:
  An assembly specified in the application dependencies manifest (XXXX.deps.json) was not found:
    package: 'Microsoft.Data.SqlClient.SNI.runtime', version: '2.0.0'
    path: 'runtimes/win-x64/native/Microsoft.Data.SqlClient.SNI.pdb'

This exception happens during the deployment and before our code even has a chance to run.
Now:

Why a .pdb is even required for the app to load? Are not pdbs only needed for debugging/stack trace formatting etc? To me this looks really weird, maybe I do not understand something about pdbs here;

The .pdb is not here because that's how Azure DevOps deploys services by default: without pdbs. This is described in detail here: https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-tutorial-deploy-app-with-cicd-vsts#configure-continuous-delivery-with-azure-pipelines. Particularly, on this screenshot: https://docs.microsoft.com/en-us/azure/service-fabric/media/service-fabric-tutorial-deploy-app-with-cicd-vsts/saveandqueue.png you can (partially) see the step which copies *.pdb to a separate folder (which is later zipped to an artifact) and then the next step which deletes original *.pdb from the final deployment package. This explains why pdbs are not copied to Service Fabric and why we get the exception we get.

After we removed steps which remove pdbs from the deployment package, it deploys and works just fine.

To me it looks like the correct fix to this issue should be not to require the pdb presence after all. If, for some reason, it is absolutely required, this should be thoroughfuly documented somewhere. Noone should kill so much time on this again.

@dmytro-gokun This looks very Service Fabric specific - wonder why the Service Fabric team does not want to deploy .pdb files? Maybe the Azure DevOps template should be updated?

@ErikEJ well, I do not know why. I can only guess that they want to preserve disk space. If you are using microservices architecture and run hundreds of services, all those pdbs (which are identical for each service) may eat all your limited disk space very fast.
Nevertheless, deploying a .pdb alongside your app or not deploying it should be the developer's choice and not a requirement for the app to run at all.

Agree, wonder if the pdb was included in the previous package? @cheenamalhotra  ??

@ErikEJ It obviously was not, as the same app/DevOps pipeline worked just fine with 1.1.3

Hi @dmytro-gokun
The pdbs were included starting with v2.0.0 since the DLLs are closed source, as tools like Binskim fail to work with driver otherwise as reported in #598
I would expect these errors to be handled by applications or application frameworks and there should be a solution to this.
But products cannot NOT ship PDBs due to such issues, it looks like a generic issue to me that should be reported to Service Fabrics.

This issue is called by this step in the Azure DevOps build pipeline:
steps:
- task: DeleteFiles@1
  displayName: 'Delete files from $(build.artifactstagingdirectory)\applicationpackage'
  inputs:
    SourceFolder: '$(build.artifactstagingdirectory)\applicationpackage'
    Contents: '**\*.pdb'

@cheenamalhotra In my humble opinion, Azure DevOps does the right thing: they treat debug info as debug info. By requiring a pdb to be present for an app to start, you are essentially changing the semantic of what pdb is. IMO.

By requiring a pdb to be present for an app to start, you are essentially changing the semantic of what pdb is. IMO.

@dmytro-gokun I'm nor sure I follow.. We don't require PDBs to be present, there's no dependency! They're copied with DLL when you build/deploy. You should be able to work without them.
What seems to be going on is these PDB references are copied to your deps.json file but when you remove these PDBs the deps.json fails to find them when it reads the file. So you need to probably remove them before deps.json is created or fix your deps.json essentially if you absolutely need to remove them.

@cheenamalhotra deps.json is not created manually or by Service Fabric. It is created by dotnet build and i presume it uses dependency information from nuget packages. Here is the problematic peace:
      "Microsoft.Data.SqlClient.SNI.runtime/2.0.0": {
        "native": {
          "runtimes/win-x64/native/Microsoft.Data.SqlClient.SNI.dll": {
            "fileVersion": "<IP_ADDRESS>"
          },
          "runtimes/win-x64/native/Microsoft.Data.SqlClient.SNI.pdb": {
            "fileVersion": "<IP_ADDRESS>"
          }
        }
      },

And that's why Service Fabric looks for this pdb while deploying the service. To be honest, i'm not that familiar with nuget to tell if it's possible to mark *.pdb dependency as optional. But that's what would look like a correct solution to me.

I would then recommend this gets reported to dotnet/sdk team that they should exclude copying PDBs for "deploy" targets :)
We don't control anything in .NET Core. We only ship PDBs along with DLLs and rest is taken care by NuGet restore and dotnet sdk.
For .NET Framework we control COPY targets and also exclude PDBs for deploy tasks, but we always shipped PDBs there and there have been no such concerns reported.

@cheenamalhotra
Okay, but:

This does not happen to any other nuget package we reference in any other project we have (quite a lot of packages, quite a lot of projects);
This did not happen in version 1.1.3

The only conclusion I can draw from this is that there is some problem with this particular nuget package. Do not you agree?

Maybe have a look at any differences between the two SNI packages

Can you give me name of any other native runtime NuGet packages that contain PDBs that you reference?
I can compare and see.

For 1.1.3 it didn't happen because we refenced "runtime.native.System.Data.SqlClient.SNI" NuGet that did not contain PDBs. Reason why there were complaints regarding missing PDBs.

LOL - now there are complaints that they are there 😄

@cheenamalhotra Unfortunately, I cannot give you such an example. But it also obvious to me that the way it is done today is causing problems. I've spent tons of time getting to the root of this issue. I'm 100% sure hundreds of people are doing the same these days and will do in the future if it's not fixed somehow. This is not the way it should be.
If you ask me, I would say it makes sense for you to speak to the core team (or nuget team?) and ask them how to do this properly, so that .pdb is not included to .deps.json. If no such way exists at the moment, a feature request has to be made to the proper team.
Also, if you think about it ... why should the pdb go to the package itself? That's what MS symbol server is for, is not it?

I think since we also shipped the PDBs to Microsoft.Data.SqlClient.SNI Nuget (SNI for .NET Framework), we packaged it here too for consistency, but I agree the experience hasn't been great with .NET Core. I'll take it offline and see if we can take them away and only upload them on symbol server.

Hi @dmytro-gokun
Just a heads up, we're setup and planning to fix this issue with next preview release of Microsoft.Data.SqlClient v2.1.0-preview2, will keep you posted.

@cheenamalhotra Thanks a lot. Looking forward for it.

Run into the same problem here. Our single exe .net core app crashed after upgrading Sqlclient from 1.1.0 to 2.0.1. Took me whole night to realize it's the pdb missing, then I found this discussion.
Looking forward for for the next release/fix!

I had a similar problem. I was using EFCore.BulkExtensions v3.2.4 (which is using SqlClient v2). Downgrade to EFCore.BulkExtensions v3.1.4 (with SqlClient v1) solved the issue.

Hi @dmytro-gokun
Closing this issue as pdbs have been removed from Microsoft.Data.SqlClient.SNI.runtime v2.1.1 to be picked by Microsoft.Data.SqlClient v2.1.0-preview2 onwards.

This issue happened when I switched from .NET 5 rc2 to RTM today. Has there been a regression?

Rolling the entity framework nuget packages back to 3.1.8 fixed the problem on the .NET 5 rtm release for me.

I had this issue too with a .NET Core app using Entity Framework Core 5.0.0 packaged as a single exe. I solved it by explicitly taking a dependency on Microsoft.Data.SqlClient version 2.1.0 (which depends on Microsoft.Data.SqlClient.SNI.runtime >= 2.1.1):
<PackageReference Include="Microsoft.Data.SqlClient" Version="2.1.0" />
<PackageReference Include="Microsoft.EntityFrameworkCore.SqlServer" Version="5.0.0" />

I did the same thing and it worked as well.


Enforce unicode in exception kwargs

This converts any binary exception kwargs into unicode strings.
This is needed because it is possible to have uncode bytes in a
python 2 string. When formatting, there is an attempt to convert
those bytes to ascii, which fails. Explicitly converting them to
unicode resolves the issue.
Fixes #2395
cc @kyleknap @jamesls @stealthycoin @dstufft

Codecov Report

:exclamation: No coverage uploaded for pull request head (unicode-exception-kwargs@c8a6a39).

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 c41778b...c8a6a39. Read the comment docs.

What's the rationale for not just fixing it at the source, given we know where this error originates from?  Otherwise, we have to be sure there's no breakage here given you're possibly affecting every botocore exception.

@JordonPhillips I hope your pull request will be approved… or tweaked. Kudos! :+1:
@jamesls @kyleknap whatever it takes, Boto development team should address this blocking issue as soon as possible. I lost a few hours trying to make AWS Command Line Interface work on my Windows set-up until I realized the problem originated from my (poorly) chosen username and some stupid UTF-8 handling issue within Boto.

@galopin Yes, completely agree we should fix this.  We just need to be careful to not fix this while unintentionally breaking other people as a result of this change.
@JordonPhillips To elaborate on my point more, while file system encoding in general is flaky, I don't think we can always assume it's utf-8.  Additionally, failure to decode to unicode when we can't load a config shouldn't itself be a failure, even using replacement chars seems to be better than failing on a decode in this specific scenario.
So my suggestion:

Move the decoding into the configloader module when we raise an exception.
Use similar logic to what the S3 code in the CLI uses (sys.getfilesystemencoding() I think).
Use 'replace' when decoding so it's not a hard failure (I don't think we want to mask the original error message if we can't decode the file).

@jamesls From the perspective of the config loader, there's nothing wrong with the strings we're using. It finds the right paths and loads the files just fine when they're available. The bug occurs in the exception itself. While we can fix the specific issue by making a change to the config loader, we can't guarantee that it will be fixed elsewhere. I think the point about file system encoding is a good one though. In this specific case, the ambiguity of the file system's encoding probably make it make more sense to fix at the config loader level.

Updated

@jamesls @kyleknap what's up, doc? Is there any hope to have this conundrum solved anytime soon?


"Include of non-modular header inside framework module 'SQLite.SQLite_Bridging'", plea

Issues are used to track bugs and feature requests.
Need  help or have a general question? Ask on Stack Overflow (tag sqlite.swift).

Build Information

Include the SQLite.swift version, commit or branch experiencing the issue.
Mention Xcode and OS X versions affected.
How do you integrate SQLite.swift in your project?

CocoaPods

ve and install the pod, changing to different versions to install, it still shows the error msg in the SQLite_Bridging.h: "Include of non-modular header inside framework module 'SQLite.SQLite_Bridging'"

same here with Xcode Version 10.1.
import from CocoaPods
pod 'SQLite.swift/SQLCipher'
error: include of non-modular header inside framework module 'SQLite.SQLite_Bridging': '/Pods/SQLCipher/sqlite3.h'
#import "sqlite3.h"

Same here with XCode 10.1
Import via CocoPods
pod 'SQLite.swift/SQLCipher'
Issue solved by removing #import "sqlite3.h" and add "@import SQLCipher;"
Check this: https://github.com/stephencelis/SQLite.swift/commit/a72a1c43361b480f7c3ca8b57c5ed3d788345880

hello every one! what happen with this issue?

this should be fixed now, please reopen if not


Detect when $PORT is missing

Add a warning to hotel add or error page.

Not relevant actually when using commands like npm start


IndexError: index 3 is out of bounds for dimension 0 with size 3

Hi,

I run this project successfully.
However, in the Training the GraspGF process, it shows the error: IndexError: index 3 is out of bounds for dimension 0 with size 3

I ran the experiment two times, but the same error occurred in each time when the time-step reached 999/50000

The command in shell "gf_train.sh" is:
python ./Runners/TrainSDE_update.py
--log_dir gf_pt2
--sde_mode vp
--batch_size 32
--lr 2e-4
--t0 0.5
--train_model
--demo_nums 15387
--num_envs=3
--demo_name=train_gf_rc
--eval_demo_name=train_eval
--device_id=0
--mode train
--dataset_type train
--relative
--space riemann
--pt_version pt2 \

The similar error occurred when the command in shell "gf_train.sh" is:
python ./Runners/TrainSDE_update.py
--log_dir gf_pt2
--sde_mode vp
--batch_size 5077
--lr 2e-4
--t0 0.5
--train_model
--demo_nums 15387
--num_envs=200
--demo_name=train_gf_rc
--eval_demo_name=train_eval
--device_id=0
--mode train
--dataset_type train
--relative
--space riemann
--pt_version pt2 \
The error shows IndexError: index 200 is out of bounds for dimension 0 with size 200:

I think this is related to num_envs, your error index is exactly the num_envs you set, I think this is because the training data requires to open all envs, if your computer not support that, you can disable evaluation, or change the data that being used for validation.

@tianhaowuhz I will try it today. Thanks for your reply.

Yes. It works. Thanks a lot.


Please add Texttospeech example

From @NinoSkopac on May 7, 2018 9:15
Hi, I'm trying to figure out how to use the new Wavenet voices, but I can't find any examples.
Please help
Copied from original issue: google/google-api-php-client#1426

Would love to get some examples out for this, I believe we have a few options for how to move forward - which would be preferred?

Generate a GAPIC with samples in this repository (I would prefer this)
Write and submit samples utilizing apiary and publish to googlecloudplatform/php-docs-samples

Is this what we're after? https://texttospeech.googleapis.com/$discovery/rest?version=v1beta1
Discovered through a GET request to https://www.googleapis.com/discovery/v1/apis

oooooops.  Looks like it is in fact here: https://github.com/google/google-api-php-client-services/tree/master/src/Google/Service/Texttospeech

I am going to close this and open the original issue.  Sorry for the noise.


Get answers for an embedded form without server side APIs / access tokens

We're personalising post-Typeform redirect pages to include "First name" data that was submitted in the form.
To do that, we added a variable in the redirect URL (like the help article suggests).
Unfortunately this creates data privacy problems, since URLs containing personal data are then sent to various tracking providers like Meta and Google. We have had warnings from these vendors about it.
One solution would be to retrieve answer data via the Embed SDK so we can store it in local storage instead, but the the Embed SDK doesn't appear to support this. The alternative, the Responses API, necessitates setting up a complex server-side application.
Will Typeform bring this capability to the Embed SDK, or is it not something that will be considered?
I notice a few similar services do appear to offer this functionality, FYI.

Hello @binarymonkey84
we do not plan to support a feature like this for the embed SDK at the moment. Since responses are processed asynchronously, the only way to retrieve data is via Responses API (as you mentioned).
Out of curiosity, could you please link to some docs of the similar services you mentioned? Thanks.

@mathio Sure, here's an example from Paperform:
https://paperform.co/help/articles/embedded-form-submissions/
Typeform does have a similar onSubmit callback, but stops short of providing the data that was in the form. Why don't you you just provide the answer data in this callback?

Since responses are processed asynchronously, the only way to retrieve data is via Responses API (as you mentioned).

I'm not sure what influence server side processing has on this use case, since we're just talking about extracting the data that's already local on the client side.

Let me discuss this with the team. I will get back to you soon  🤞

Hello @binarymonkey84
I am sorry, but we have decided we will not be providing this feature at the moment.
There is some security risk tied to this. If we pass this payload in onSubmit callback, any website that embeds a typeform would be able to read responses. At the moment host website does not have access to embedded typeform or any responses since it is inside an iframe. Malicious websites might display fake forms even right now and collect data, however by building this feature we would make it easier for potential attackers and allow them to use actual typeforms to execute the attack.

Sounds like that concern could be pretty easily addressed by having an authorised hosts / domains list in the Typeform account?
In your iframe, you can just query what host is embedding the frame (via window.parent.location) and if it's on the authorised list, you can be safe in passing back responses.
Maybe that would work well?

We considered a whitelisting feature, but decided not to go forward with the idea. Other than that, there are also some challenges in reliably determining host page URL.

A script from the iframe does have access to window.parent.location, but it can not read any of its values:
Uncaught DOMException: Failed to read a named property 'href' from 'Location': Blocked a frame with origin "https://***" from accessing a cross-origin frame.

We can not reliably use document.referrer either, as it depends on the browser and might not be present.
In some browsers we might be able to use ancestorOrigins, however it is not supported by all browsers.

Perhaps event.origin on a cross-origin window message could be used to verify the host instead? MDN even suggests this here, and browser support looks good.
The Embed SDK code could call postMessage to send a message to the Typeform iframe, like "verifyhost" or something. If you're already using postMessage to set up callbacks with the Embed SDK, just use the existing calls.
Then on the Typeform side, listen for the message and if event.origin matches a domain that's been whitelisted on the Typeform account, then include the response data in the onSubmit callback.
Surely that's a winner? 🤞

Yes that solution sounds solid.
However, as I mentioned in my previous comment, we decided not to implement this feature at the moment.

Oh, I thought that decision was only based on the fact Typeform didn't want response data available to non whitelisted hosts. If my suggested approach solves that, why not reconsider?
I have noticed quite a few developers struggle with the same problem when I was researching how to do this on Stack Overflow, etc.
Typeform is difficult to recommend to our agency clients who want embedded forms on their sites which can then redirect to a personalised landing page, so this relatively simple improvement would make a world of difference.

Thank you for the comment. Although we are not working on this feature, we might plan it in the future.


text input, is there a way?

Is there a straightforward way to prompt a user for text value?
I'm not looking for something like a text editor (I'm aware of micro).  Rather looking for a way to prompt for a filename, or a password, or things like that.  In a perfect world, a filename prompt could autocomplete, and a password prompt would mask what is typed.
Does tcell support anything like that already?  I hope I'm not missing something obvious.

not at present but i did start some of this with the views subpackage.  you should check that out.
Sent from my iPhone

On Apr 23, 2017, at 2:56 PM, dncohen<EMAIL_ADDRESS>wrote:
Is there a straightforward way to prompt a user for text value?
I'm not looking for something like a text editor (I'm aware of micro). Rather looking for a way to prompt for a filename, or a password, or things like that. In a perfect world, a filename prompt could autocomplete, and a password prompt would mask what is typed.
Does tcell support anything like that already? I hope I'm not missing something obvious.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@dncohen If what you described is all you need, maybe https://godoc.org/golang.org/x/crypto/ssh/terminal#NewTerminal instead of tcell.

I don't think that includes autocompletion.  It strikes me that there is an opportunity for someone to build something like this -- perhaps a Go version of readline.
At any rate, this is not something tcell is intended for -- it has a "views" sub package, and you might want to look at the TextArea object for ideas, but you'll still have to write code.
This isn't really a bug, so I'm closing this for now.

Thanks for the suggestion and explanation.  If I have any breakthrough that works well, I'll be sure to let you know.

And speaking of "Go version of readline," https://github.com/chzyer/readline.

Did anyone make any progress here? Some way to embed/extend in readline support would be great.

I havent looked at it.
On Sun, Sep 24, 2017 at 1:44 PM cornfeedhobo<EMAIL_ADDRESS>wrote:

Did anyone make any progress here? Some way to embed/extend in readline
support would be great.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/gdamore/tcell/issues/146#issuecomment-331738997, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABPDffO3q7MpiFpuT9sy9VHa7k8UlqaSks5slr8zgaJpZM4NFjRG
.


Help Menu Links

Wonderful work, thank you!
Would like use this in school classroom but cannot have links which open default browser and access the internet. The "Help" menu has such links...
Looking at API and see no way to change this? Is it possible to remove links leading to external sites?
Thanks again.

@oleteacher glad you find it useful 🙂!
The help menu has such links, and links can also be opened in the default browser with a simple Ctrl+click (or Shift+click, not sure), and some links considered extenal will open in the default browser. I don't think Nativefier has the enforcement mechanisms you need for your specific use case, sorry.

Ok, thanks for trying to support school kids wishing to learn!


samples: bmg169: don't enable CONFIG_LOG

It's not necessary for this sample to output to the user
(it uses printf) and saves over 5K of ROM size, eliminating
some build failures on Quark D2000.
Fixes: #14476
Signed-off-by: Andrew Boie<EMAIL_ADDRESS>

Codecov Report

Merging #14583 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #14583   +/-   ##
=======================================
  Coverage   51.96%   51.96%
=======================================
  Files         309      309
  Lines       45576    45576
  Branches    10554    10554
=======================================
  Hits        23683    23683
  Misses      17083    17083
  Partials     4810     4810

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 350f6f7...40775c6. Read the comment docs.


Default dynamic profile view on data model/class/element level

As a user, I want to be able to see s certain set of data model/class/element attributes by default (defined in one dynamic profile), so that information I need is readily available and I do not need to perform an additional search or click through different screens to see the information I need.

@gammonpeter @jamesrwelch Could I get some feedback on whether this would be a good solution for Users to have a Custom Profile set as a default on Catalog Item Edit/View screens?
Proposed solution for setting a custom profile as the default selection in the Profile drop list

The UI will look for the default.profile property key on the current catalog item

The default.profile property key and namespace are determined by the Admin Configuration property entries of:
ui.property.namespace
ui.property.default.profile.key
These properties will be loaded to the database through a new Grails bootstrap entry for dev/production environments
a. If the default.profile property key is not found on the catalog item, the UI will search for this
property on the parent catalog item, and continue up the hierarchy until a property is found, or the top of
the hierarchy of catalog items has been reached. (eg. Data Element > Data Class > Data Model)

The UI will set the Profile drop list value to:
a. Default if no default.profile property key is found in the hierarchy, or
b. Default if a default.profile property key is found but does not match an existing Custom Profile for the catalog item, or
c. The Value found for the default.profile property key that matches an existing Custom Profile

@GBishop-PHSA This seems like a really nice feature - I especially like that by setting the property in some of our custom imports we can control the way the model / class / element is presented.  I'm playing with the branch now and I can't seem to get it working - we've made some changes to the back end which may have inadvertently broken it?  Or maybe I've not followed the instructions above correctly.  Would you be able to take a look?

@jamesrwelch I made a design change when we were testing the solution. Since the logic in 2c is "The Value found for the default.profile property value that matches an existing Custom Profile", it didn't seem necessary to have a configuraton to set the property key, just the namespace.
So part 1, is now:

The UI will look for the default.profile property on the hierarchy of catalog items
The default.profile property namespace is determined by the Admin Configuration property entry of:

ui.default.profile.namespace

eg. A Data Model that has a custom profile assigned called "Custom Profile A"
The Data Model would then have a property set:
namespace               key              Value
default.propfile        any_key        Custom Profile A


About calculating the momentum for entanglement spectrum

Thank you for the wonderful package
I am using your package to do some dmrg calculation in 2D and I need to calculate the momentum for entanglement spectrum. However, I find the entanglement spectrum I get from the function (in the class ..networks.mps.MPS) compute_K() is different from any entanglement spectrum I get directly from the function entanglement_spectrum(), which calculates the entanglement spectrum for every site(bond). Also, the momentum I get, which I read from the angle of the entanglement spectrum, is not at all what I suppose (n*2Pi/Ly). I want to understand what entanglement_spectrum compute_K calculates and how to get the correct momentum I want.
(The lattice I am using is Kagome lattice.)

see the discusssion in the forum.


refactor: adapting transfer metadata bytes field to memo string

Description

Changing metadata bytes field to memo string

closes: #XXXX

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

Nice work! Would it be easier to redo these changes for each backport branch? Maybe we try to use mergify and see how bad the conflicts are?

I'm happy to use mergify and see how that goes. I'll add the labels now


Webapp config

Add config mojo to webapp maven plugin, it will generate new configuration when no configuration was found and it allow user to modify configurations.
Config includes three parts

Webapp(appname, resourcegroup, pricingTier, region )
Runtime(os, container and docker configuration)
Slot(slot name and configurationSource)

When create new configuration, it will ask user for runtime attributes and create new configuration, when configuration was found, it will ask user which part to config and config correspond attributes.

Pr too large, split it into small one


Cannot forward ports; iptables does not recognize --to-destination option

Describe the bug
Trying to use this type of config creates the expected firewall config, but that config fails
networking.nat = {
      enable = true;
      externalInterface = "enp1s0";
      #externalInterface = "enp2s0";
      internalInterfaces  = [ "br0" "tailscale0" ];
      forwardPorts = [{ sourcePort = 13443; destination = "<IP_ADDRESS>:13443"; proto = "tcp"; }];
    };

The errors
Apr 20 20:35:01 cmp-nix1 systemd[1]: Reloading Firewall.
Apr 20 20:35:01 cmp-nix1 firewall-reload[12061]: iptables: Bad rule (does a matching rule exist in that chain?).
Apr 20 20:35:01 cmp-nix1 firewall-reload[12062]: iptables: Bad rule (does a matching rule exist in that chain?).
Apr 20 20:35:04 cmp-nix1 firewall-reload[12205]: iptables v1.8.5 (legacy): unknown option "--to-destination"
Apr 20 20:35:04 cmp-nix1 firewall-reload[12205]: Try `iptables -h' or 'iptables --help' for more information.
Apr 20 20:35:04 cmp-nix1 firewall-reload[12048]: Failed to reload firewall... Stopping
Apr 20 20:35:04 cmp-nix1 systemd[1]: firewall.service: Control process exited, code=exited, status=1/FAILURE
Apr 20 20:35:04 cmp-nix1 systemd[1]: Reload failed for Firewall.
Apr 20 20:35:21 cmp-nix1 systemd[1]: Reloading Firewall.

I am currently using the Hardened Kernel with the following extra kernel modules
boot.kernelModules = [
    "sch_cake"
    "ipt_mark"
    "iptable_nat"
    "iptable_filter"
  ];

These are all the modules with "ip" loaded
[root@cmp-nix1:~/nix-config]# lsmod | grep ip
ip6table_nat           16384  1
ip6t_rpfilter          16384  1
ipt_rpfilter           16384  1
ip6table_raw           16384  1
iptable_raw            16384  1
nf_log_ipv6            16384  1
nf_log_ipv4            16384  1
nf_log_common          16384  2 nf_log_ipv4,nf_log_ipv6
ip6table_filter        16384  1
ip6_tables             36864  5 ip6table_filter,ip6table_raw,ip6table_nat
iptable_filter         16384  1
iptable_nat            16384  1
nf_nat                 49152  4 ip6table_nat,nf_nat_ftp,iptable_nat,xt_MASQUERADE
nf_defrag_ipv6         24576  1 nf_conntrack
nf_defrag_ipv4         16384  1 nf_conntrack
ip_tables              36864  4 iptable_filter,iptable_raw,iptable_nat
x_tables               45056  15 ip6table_filter,xt_conntrack,ip6table_raw,iptable_filter,ip6t_rpfilter,xt_LOG,xt_tcpudp,xt_comment,ip6_tables,ipt_rpfilter,xt_pkttype,iptable_raw,ip_tables,xt_MASQUERADE,xt_mark

To Reproduce
Steps to reproduce the behavior:

Using hardened kernel parameters (except scudo)
Add port forwarding to the NAT block
Add firewall allowed ports

Expected behavior
Firewall reload succeeds and port forwarding enabled
Notify maintainers
Unclear who are maintainer to me for NAT cause to me it seems the issue is a middle module. Just tagging last two committers for now.
@valeriangalliat @thatsmydoing
Metadata
[root@cmp-nix1:~/nix-config]# nix-shell -p nix-info --run "nix-info -m"
these paths will be fetched (0.05 MiB download, 0.28 MiB unpacked):
  /nix/store/a9g7p6fwanw66j5djzila7ql1hky759z-bash-interactive-4.4-p23-dev
copying path '/nix/store/a9g7p6fwanw66j5djzila7ql1hky759z-bash-interactive-4.4-p23-dev' from 'https://cache.nixos.org'...
 - system: `"x86_64-linux"`
 - host os: `Linux 5.4.100-hardened1, NixOS, 20.09.3376.1ac507ba981 (Nightingale)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.10`
 - channels(cmp): `""`
 - channels(root): `"nixos-20.09.3376.1ac507ba981"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

I'm not really a maintainer and just contributed a bug fix here so I know as much as you do.
Have you tried it on a non-hardened kernel config? Did this work before and broke recently?
Could you put the contents of the file returned by this command?
nix-instantiate --eval '<nixpkgs/nixos>' -A config.systemd.services.firewall.serviceConfig.ExecStart

Yea I realize that. I do still appreciate the help. From what I could see the file looks like it's using the argument correctly. I had similar issues trying to setup cake which required a specific kernel module.
I will try not using the hardened version. I think that has been a source of a ton of problems. If possible it'd be nice to figure things out while still using that.
Here is what was in that file for me
#! /nix/store/9ywr69qi622lrmx5nn88gk8jpmihy0dz-bash-4.4-p23/bin/bash -e
# Helper command to manipulate both the IPv4 and IPv6 tables.
ip46tables() {
  iptables -w "$@"
  ip6tables -w "$@"

}

# Flush the old firewall rules.  !!! Ideally, updating the
# firewall would be atomic.  Apparently that's possible
# with iptables-restore.
ip46tables -D INPUT -j nixos-fw 2> /dev/null || true
for chain in nixos-fw nixos-fw-accept nixos-fw-log-refuse nixos-fw-refuse; do
  ip46tables -F "$chain" 2> /dev/null || true
  ip46tables -X "$chain" 2> /dev/null || true
done

# The "nixos-fw-accept" chain just accepts packets.
ip46tables -N nixos-fw-accept
ip46tables -A nixos-fw-accept -j ACCEPT

# The "nixos-fw-refuse" chain rejects or drops packets.
ip46tables -N nixos-fw-refuse

ip46tables -A nixos-fw-refuse -j DROP

# The "nixos-fw-log-refuse" chain performs logging, then
# jumps to the "nixos-fw-refuse" chain.
ip46tables -N nixos-fw-log-refuse

ip46tables -A nixos-fw-log-refuse -p tcp --syn -j LOG --log-level info --log-prefix "refused connection: "

ip46tables -A nixos-fw-log-refuse -m pkttype ! --pkt-type unicast -j nixos-fw-refuse

ip46tables -A nixos-fw-log-refuse -j nixos-fw-refuse

# The "nixos-fw" chain does the actual work.
ip46tables -N nixos-fw

# Clean up rpfilter rules
ip46tables -t raw -D PREROUTING -j nixos-fw-rpfilter 2> /dev/null || true
ip46tables -t raw -F nixos-fw-rpfilter 2> /dev/null || true
ip46tables -t raw -X nixos-fw-rpfilter 2> /dev/null || true

# Perform a reverse-path test to refuse spoofers
# For now, we just drop, as the raw table doesn't have a log-refuse yet
ip46tables -t raw -N nixos-fw-rpfilter 2> /dev/null || true
ip46tables -t raw -A nixos-fw-rpfilter -m rpfilter --validmark  -j RETURN

# Allows this host to act as a DHCP4 client without first having to use APIPA
iptables -t raw -A nixos-fw-rpfilter -p udp --sport 67 --dport 68 -j RETURN

# Allows this host to act as a DHCPv4 server
iptables -t raw -A nixos-fw-rpfilter -s <IP_ADDRESS> -d <IP_ADDRESS> -p udp --sport 68 --dport 67 -j RETURN

ip46tables -t raw -A nixos-fw-rpfilter -j DROP

ip46tables -t raw -A PREROUTING -j nixos-fw-rpfilter

# Accept all traffic on the trusted interfaces.
ip46tables -A nixos-fw -i lo -j nixos-fw-accept

# Accept packets from established or related connections.
ip46tables -A nixos-fw -m conntrack --ctstate ESTABLISHED,RELATED -j nixos-fw-accept

# Accept connections to the allowed TCP ports.
ip46tables -A nixos-fw -p tcp --dport 53 -j nixos-fw-accept -i br0
ip46tables -A nixos-fw -p tcp --dport 80 -j nixos-fw-accept -i br0
ip46tables -A nixos-fw -p tcp --dport 443 -j nixos-fw-accept -i br0
ip46tables -A nixos-fw -p tcp --dport 6789 -j nixos-fw-accept -i br0
ip46tables -A nixos-fw -p tcp --dport 8080 -j nixos-fw-accept -i br0
ip46tables -A nixos-fw -p tcp --dport 8443 -j nixos-fw-accept -i br0
ip46tables -A nixos-fw -p tcp --dport 8843 -j nixos-fw-accept -i br0
ip46tables -A nixos-fw -p tcp --dport 8880 -j nixos-fw-accept -i br0
ip46tables -A nixos-fw -p tcp --dport 13443 -j nixos-fw-accept -i br0
ip46tables -A nixos-fw -p tcp --dport 22 -j nixos-fw-accept
ip46tables -A nixos-fw -p tcp --dport 13443 -j nixos-fw-accept
ip46tables -A nixos-fw -p tcp --dport 13443 -j nixos-fw-accept -i enp1s0

# Accept connections to the allowed TCP port ranges.

# Accept packets on the allowed UDP ports.
ip46tables -A nixos-fw -p udp --dport 53 -j nixos-fw-accept -i br0
ip46tables -A nixos-fw -p udp --dport 3478 -j nixos-fw-accept -i br0
ip46tables -A nixos-fw -p udp --dport 10001 -j nixos-fw-accept -i br0
ip46tables -A nixos-fw -p udp --dport 41641 -j nixos-fw-accept

# Accept packets on the allowed UDP port ranges.
ip46tables -A nixos-fw -p udp --dport 67:68 -j nixos-fw-accept -i br0

# Accept IPv4 multicast.  Not a big security risk since
# probably nobody is listening anyway.
#iptables -A nixos-fw -d <IP_ADDRESS>/4 -j nixos-fw-accept

# Optionally respond to ICMPv4 pings.
iptables -w -A nixos-fw -p icmp --icmp-type echo-request -j nixos-fw-accept

# Accept all ICMPv6 messages except redirects and node
# information queries (type 139).  See RFC 4890, section
# 4.4.
ip6tables -A nixos-fw -p icmpv6 --icmpv6-type redirect -j DROP
ip6tables -A nixos-fw -p icmpv6 --icmpv6-type 139 -j DROP
ip6tables -A nixos-fw -p icmpv6 -j nixos-fw-accept

# Allow this host to act as a DHCPv6 client
ip6tables -A nixos-fw -d fe80::/64 -p udp --dport 546 -j nixos-fw-accept

# Helper command to manipulate both the IPv4 and IPv6 tables.
ip46tables() {
  iptables -w "$@"
  ip6tables -w "$@"

}

ip46tables -w -t nat -D PREROUTING -j nixos-nat-pre 2>/dev/null|| true
ip46tables -w -t nat -F nixos-nat-pre 2>/dev/null || true
ip46tables -w -t nat -X nixos-nat-pre 2>/dev/null || true
ip46tables -w -t nat -D POSTROUTING -j nixos-nat-post 2>/dev/null || true
ip46tables -w -t nat -F nixos-nat-post 2>/dev/null || true
ip46tables -w -t nat -X nixos-nat-post 2>/dev/null || true
ip46tables -w -t nat -D OUTPUT -j nixos-nat-out 2>/dev/null || true
ip46tables -w -t nat -F nixos-nat-out 2>/dev/null || true
ip46tables -w -t nat -X nixos-nat-out 2>/dev/null || true

iptables -A FORWARD -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
iptables -A FORWARD -i br0 -o enp1s0 -j ACCEPT
tc qdisc replace dev enp1s0 root cake besteffort autorate-ingress bandwidth 1000mbit lan ingress dual-dsthost ethernet
# tc qdisc replace dev br0 root cake besteffort autorate-ingress bandwidth 1000mbit lan dual-dsthost ethernet
# tc qdisc add dev enp1s0 handle 1: root cake besteffort autorate-ingress bandwidth $BANDWIDTH internet ingress dual-dsthost ethernet

# Helper command to manipulate both the IPv4 and IPv6 tables.
ip46tables() {
  iptables -w "$@"
  ip6tables -w "$@"

}

# Create subchain where we store rules
ip46tables -w -t nat -N nixos-nat-pre
ip46tables -w -t nat -N nixos-nat-post
ip46tables -w -t nat -N nixos-nat-out

# We can't match on incoming interface in POSTROUTING, so
# mark packets coming from the internal interfaces.
iptables -w -t nat -A nixos-nat-pre \
  -i 'br0' -j MARK --set-mark 1
iptables -w -t nat -A nixos-nat-pre \
  -i 'tailscale0' -j MARK --set-mark 1

# NAT the marked packets.
iptables -w -t nat -A nixos-nat-post -m mark --mark 1 \
  -o enp1s0 -j MASQUERADE

# NAT packets coming from the internal IPs.

# NAT from external ports to internal ports.
iptables -w -t nat -A nixos-nat-pre \
  -i enp1s0 -p tcp \
  --dport 13443 \
  -j DNAT --to-destination <IP_ADDRESS>:13443

# Append our chains to the nat tables
ip46tables -w -t nat -A PREROUTING -j nixos-nat-pre
ip46tables -w -t nat -A POSTROUTING -j nixos-nat-post
ip46tables -w -t nat -A OUTPUT -j nixos-nat-out

# Reject/drop everything else.
ip46tables -A nixos-fw -j nixos-fw-log-refuse

# Enable the firewall.
ip46tables -A INPUT -j nixos-fw

I switched to not using the hardened kernel package and seems to not have made a difference. I did reboot to and reapply the config to forward ports, but I get the same error.
Apr 25 13:40:37 cmp-nix1 systemd[1]: Reloading Firewall.
Apr 25 13:40:41 cmp-nix1 firewall-reload[16462]: iptables v1.8.5 (legacy): unknown option "--to-destination"
Apr 25 13:40:41 cmp-nix1 firewall-reload[16462]: Try `iptables -h' or 'iptables --help' for more information.
Apr 25 13:40:41 cmp-nix1 firewall-reload[16303]: Failed to reload firewall... Stopping
Apr 25 13:40:42 cmp-nix1 systemd[1]: firewall.service: Control process exited, code=exited, status=1/FAILURE
Apr 25 13:40:42 cmp-nix1 systemd[1]: Reload failed for Firewall.
Apr 25 13:41:14 cmp-nix1 systemd[1]: Reloading Firewall.
Apr 25 13:41:15 cmp-nix1 firewall-reload[16740]: iptables: Bad rule (does a matching rule exist in that chain?).
Apr 25 13:41:15 cmp-nix1 firewall-reload[16741]: iptables: Bad rule (does a matching rule exist in that chain?).
Apr 25 13:41:18 cmp-nix1 systemd[1]: Reloaded Firewall.
-- Reboot --
Apr 25 13:41:55 cmp-nix1 systemd[1]: Starting Firewall...
Apr 25 13:41:57 cmp-nix1 systemd[1]: Finished Firewall.
Apr 25 13:45:00 cmp-nix1 systemd[1]: Reloading Firewall.
Apr 25 13:45:03 cmp-nix1 firewall-reload[2416]: iptables v1.8.5 (legacy): unknown option "--to-destination"
Apr 25 13:45:03 cmp-nix1 firewall-reload[2416]: Try `iptables -h' or 'iptables --help' for more information.
Apr 25 13:45:03 cmp-nix1 firewall-reload[2256]: Failed to reload firewall... Stopping
Apr 25 13:45:03 cmp-nix1 systemd[1]: firewall.service: Control process exited, code=exited, status=1/FAILURE
Apr 25 13:45:03 cmp-nix1 systemd[1]: Reload failed for Firewall.

Following is my full configuration.nix.  I'm posting it cause last time it was the kernel module I needed and what I had posted would never have shown that. Maybe someone can see something obviously wrong with my config.
# your system.  Help is available in the configuration.nix(5) man page
# and in the NixOS manual (accessible by running ‘nixos-help’).

{ config, pkgs, ... }:

{
  imports =
    [ # Include the results of the hardware scan.
      ./hardware-configuration.nix
    ];

  # Use the systemd-boot EFI boot loader.
  boot.loader.systemd-boot.enable = true;
  boot.loader.efi.canTouchEfiVariables = true;

  nixpkgs.config.allowUnfree = true;

  boot.kernel.sysctl."net.ipv4.ip_forward" = 1;
  boot.kernel.sysctl."net.core.default_qdisc" = "cake";
  boot.kernel.sysctl."net.ipv4.tcp_ecn" = 1;
  boot.kernel.sysctl."net.ipv4.tcp_sack" = 1;
  boot.kernel.sysctl."net.ipv4.tcp_dsack" = 1;
  #boot.kernel.sysctl."net.ipv6.conf.all.forwarding" = 1;

  networking = {
    hostName = "cmp-nix1"; # Define your hostname.
    wireless.enable = false;  # Enables wireless support via wpa_supplicant.
    useDHCP = false; # Disabled because it's on each interface

    bridges = {
      br0.interfaces = ["enp2s0" "enp3s0" "enp4s0"];
    };

    interfaces = {
      # WAN Port
      enp1s0.useDHCP = true;

      # LAN Port
      br0 = {
        useDHCP = false;
        ipv4 = {
          addresses = [
            { address = "<IP_ADDRESS>"; prefixLength = 24;}
          ];
        };
      };
    };

    nat = {
      enable = true;
      externalInterface = "enp1s0";
      #externalInterface = "enp2s0";
      internalInterfaces  = [ "br0" "tailscale0" ];
      forwardPorts = [{ sourcePort = 13443; destination = "<IP_ADDRESS>:13443"; proto = "tcp"; }];
    };

    firewall = {
      allowPing = true;
      allowedTCPPorts = [ 22 13443 ];
      allowedUDPPorts = [ 41641 ];
      interfaces = {
        enp1s0 = {
          allowedTCPPorts = [ 13443 ];
          allowedUDPPorts = [ ];
        };
        br0 = {
          allowedTCPPorts = [ 53 80 443 13443 8443 8080 8880 8843 6789 ];
          allowedUDPPorts = [ 53 3478 10001 ];
          allowedUDPPortRanges = [ { from = 67; to = 68; }];
        };
      };
        extraPackages = [ pkgs.iproute ];
        extraCommands = ''
    iptables -A FORWARD -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
    iptables -A FORWARD -i br0 -o enp1s0 -j ACCEPT
    tc qdisc replace dev enp1s0 root cake besteffort autorate-ingress bandwidth 1000mbit lan ingress dual-dsthost ethernet
    # tc qdisc replace dev br0 root cake besteffort autorate-ingress bandwidth 1000mbit lan dual-dsthost ethernet
    # tc qdisc add dev enp1s0 handle 1: root cake besteffort autorate-ingress bandwidth $BANDWIDTH internet ingress dual-dsthost ethernet
    '';
        extraStopCommands = ''
    iptables -D FORWARD -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT || true
    iptables -D FORWARD -i br0 -o enp1s0 -j ACCEPT || true
    '';
    };
  };

  services.tailscale.enable = true;

  services.dhcpd4 = {
    enable = true;
    #authoritative = true;
    interfaces = [ "br0" ];
    machines = [
    <snip>
    ];
    extraConfig = ''
subnet <IP_ADDRESS> netmask <IP_ADDRESS> {
	range <IP_ADDRESS> <IP_ADDRESS>;
	option routers <IP_ADDRESS>;
	option domain-name-servers <IP_ADDRESS>;
	option broadcast-address <IP_ADDRESS>;
}
'';
  };
  services.bind = {
    enable = true;
    cacheNetworks = [
      "<IP_ADDRESS>/24"
      "<IP_ADDRESS>/24"
      "<IP_ADDRESS>/32"
      "<IP_ADDRESS>/32"
    ];
    #listenOn = ["enp2s0"];
    #listenOnIpv6 = ["enp2s0"];
    forwarders = [
      "<IP_ADDRESS>"
      "<IP_ADDRESS>"
    ];
#    extraOptions = ''
#recursion yes;
#allow-recursion { cachenetworks; };
#'';
  };
  services.unifi = {
    enable = true;
    openPorts = false;
  };

  # Select internationalisation properties.
  i18n.defaultLocale = "en_US.UTF-8";
  console = {
    font = "Lat2-Terminus16";
    keyMap = "us";
  };

  # Set your time zone.
  time.timeZone = "America/New_York";

  services.chrony.enable = true;

  # List packages installed in system profile. To search, run:
  # $ nix search wget
  environment.systemPackages = with pkgs; [
    wget vim inetutils traceroute
  ];

  # Some programs need SUID wrappers, can be configured further or are
  # started in user sessions.
  # programs.mtr.enable = true;
  # programs.gnupg.agent = {
  #   enable = true;
  #   enableSSHSupport = true;
  #   pinentryFlavor = "gnome3";
  # };

  # List services that you want to enable:

  # Enable the OpenSSH daemon.
  services.openssh.enable = true;
  services.openssh.passwordAuthentication = false;
  services.openssh.challengeResponseAuthentication = false;
  services.openssh.permitRootLogin = "no";

  # Open ports in the firewall.

  # Enable CUPS to print documents.
  services.printing.enable = false;

  # Enable sound.
  # sound.enable = true;
  # hardware.pulseaudio.enable = true;

  # Enable the X11 windowing system.
  services.xserver.enable = false;
  # services.xserver.layout = "us";
  # services.xserver.xkbOptions = "eurosign:e";

  # Enable touchpad support.
  services.xserver.libinput.enable = false;

  # Enable the KDE Desktop Environment.
  services.xserver.displayManager.sddm.enable = false;
  services.xserver.desktopManager.plasma5.enable = false;

  # Define a user account. Don't forget to set a password with ‘passwd’.
  users.users.cmp = {
    isNormalUser = true;
    extraGroups = [ "wheel" ]; # Enable ‘sudo’ for the user.
    openssh.authorizedKeys.keys = [
    <snip>
    ];
  };

  # Security Settings from secure profile in nixos repo
  #boot.kernelPackages = pkgs.linuxPackages_hardened;

  # environment.memoryAllocator.provider = "scudo";
  # environment.variables.SCUDO_OPTIONS = "ZeroContents=1";

  security.hideProcessInformation = true;
  security.lockKernelModules = true;
  security.protectKernelImage = true;
  security.allowSimultaneousMultithreading = false;
  security.forcePageTableIsolation = true;
  security.virtualisation.flushL1DataCache = "always";
  security.apparmor.enable = true;
  boot.kernelParams = [
    # Slab/slub sanity checks, redzoning, and poisoning
    "slub_debug=FZP"

    # Overwrite free'd memory
    "page_poison=1"

    # Enable page allocator randomization
    "page_alloc.shuffle=1"
  ];
  boot.kernelModules = [
    "sch_cake"
    "ipt_mark"
    "iptable_nat"
    "iptable_filter"
  ];
  boot.blacklistedKernelModules = [
    # Obscure network protocols
    "ax25"
    "netrom"
    "rose"

    # Old or rare or insufficiently audited filesystems
    "adfs"
    "affs"
    "bfs"
    "befs"
    "cramfs"
    "efs"
    "erofs"
    "exofs"
    "freevxfs"
    "f2fs"
    "hfs"
    "hpfs"
    "jfs"
    "minix"
    "nilfs2"
    "qnx4"
    "qnx6"
    "sysv"
    "ufs"
  ];
  # Restrict ptrace() usage to processes with a pre-defined relationship
  # (e.g., parent/child)
  boot.kernel.sysctl."kernel.yama.ptrace_scope" = "1";

  # Hide kptrs even for processes with CAP_SYSLOG
  boot.kernel.sysctl."kernel.kptr_restrict" = "2";

  # Disable bpf() JIT (to eliminate spray attacks)
  boot.kernel.sysctl."net.core.bpf_jit_enable" = false;

  # Disable ftrace debugging
  boot.kernel.sysctl."kernel.ftrace_enabled" = false;

  # Enable strict reverse path filtering (that is, do not attempt to route
  # packets that "obviously" do not belong to the iface's network; dropped
  # packets are logged as martians).
  boot.kernel.sysctl."net.ipv4.conf.all.log_martians" = true;
  boot.kernel.sysctl."net.ipv4.conf.all.rp_filter" = "1";
  boot.kernel.sysctl."net.ipv4.conf.default.log_martians" = true;
  boot.kernel.sysctl."net.ipv4.conf.default.rp_filter" = "1";

  # Ignore broadcast ICMP (mitigate SMURF)
  boot.kernel.sysctl."net.ipv4.icmp_echo_ignore_broadcasts" = true;

  # This value determines the NixOS release from which the default
  # settings for stateful data, like file locations and database versions
  # on your system were taken. It‘s perfectly fine and recommended to leave
  # this value at the release version of the first install of this system.
  # Before changing this value read the documentation for this option
  # (e.g. man configuration.nix or on https://nixos.org/nixos/options.html).
  system.stateVersion = "20.03"; # Did you read the comment?

}

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/fix-iptables-not-recognizing-flags-to-forward-ports-to-destination-unknown/12683/1

I'd recommend you unlock kernel modules and if it succeeds, check the difference in iptables modules.
Just a wild guess, but have you tried adding ipt_DNAT / xt_nat?

Your logs say
Apr 25 13:41:55 cmp-nix1 systemd[1]: Starting Firewall...
Apr 25 13:41:57 cmp-nix1 systemd[1]: Finished Firewall.

so it does look like it works? Did you only add your forward config after you've rebooted? After doing a nixos-rebuild boot with the forward config and rebooting does it not work?
Looking at how lockKernelModules works, it only locks it after the firewall has loaded so you shouldn't even have to explicitly load anything IIUC. https://github.com/NixOS/nixpkgs/blob/d600f006643e074c2ef1d72e462e218b647a096c/nixos/modules/security/lock-kernel-modules.nix

Yea I basically remove the forwardPorts option and the firewall works fine. I rollback to get internet again when I'm still connected to that network.
I have unlocked the kernel modules and added the other two modules. I thought those were being loaded somehow cause I saw them in the list of modules, but maybe I needed to be more explicit.

ok! I think that was the fix. Pretty sure combo of not locking the modules and also explicitly adding them made it work. Now I can access the NAS I was trying to access fine.

Hey everyone, I had a similar issue. The following solved the problem and helped me keep the locked modules settings enabled:
  config.boot.kernelModules = [
          "iptable_nat"
          "iptable_filter"
          "xt_nat"
  ];


Error on use

I am getting an error
 - node-red-contrib-xiaomi-ble:Xiaomi BLE : Error: Cannot find module 'bluetooth-hci-socket'

What version of node.js are you using?

~# node -v
v11.0.0
~# npm -v
6.4.1
I have just rebuilt from scratch (DietPi) and get the same error.

There are a number of issues with this dependency installing https://github.com/noble/node-bluetooth-hci-socket/issues
I tried this as a solution https://github.com/DigitalSecurity/btlejuice/issues/15#issuecomment-397269423
I think the problem lies with bluetooth-hci-socket itself.

Thanks for your investigation!


Release process

Codecov Report

Merging #80 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master     #80   +/-   ##
======================================
  Coverage    88.2%   88.2%
======================================
  Files           5       5
  Lines         780     780
======================================
  Hits          688     688
  Misses         56      56
  Partials       36      36

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 62b2910...d9226a0. Read the comment docs.

nice PR :+1:

@unleashed made some changes based on your comments


[BUG]: searchable select component default empty list

Issue description
When we click on the bl-select component to search, an orange line appears.
Media & Screenshots

Baklava Version
No response
Operating system
No response
Priority this issue should have
High (immediate attention needed)
Please review the checkboxes that are applicable.

[ ] This issue is directly related to React

Have you attempted to provide a SelectOption? It will be displayed in that manner if there are no options available for the select.

SelectOption will be created once the search process concludes. Initially, there are no SelectOptions during the first render because the data is empty.

You should wait for the data fetching to complete before attempting to render, ensuring successful option rendering or you will attempt to re-render the select option

To start the data fetching process, I need to click selected and perform the action. The error happens right at this moment.

We are not currently supporting API fetching with search functionality, so you should handle the data manually. At the moment, providing a slot element to bl-select when fetching data can be worked around using the following approach:
<bl-select
     multiple
     search-bar
     search-bar-placeholder="Arama yapabilirsiniz"
>
    // your custom element
</bl-select>

I am currently using this method. I just wanted to let you know because component trying to create an option with empty data.

This appears to be a UI scenario, so we can seek assistance from @buseselvi in this matter. What should be shown to the user if no selection option has been added?

We shouldn't show the select popover / a line like in the image above if the popover is empty, we should show only the select input. Let's fix it 🚀


Mean Function throws Null Pointer Exception on Arm64

Steps to reproduce:
List the minimal actions needed to reproduce the behavior.

Launch InfluxDB 2 Beta 12 in a docker container on Arm64 (e.g. AWS Graviton 2)
Run Flux Query
Null Pointer Exception

The flux query works fine on x86
Flux Query:
import "strings"

from(bucket: "os/record")
	|> range(start: -2m, stop: -1m)
	|> filter(fn: (r) =>
		(r["_measurement"] == "mount"))
	|> filter(fn: (r) =>
		(r["_field"] == "util"))
	|> filter(fn: (r) =>
		(strings.index(v: r["instance"], substr: "i-") == 0))
	|> mean(column:"_value")

The null pointer is thrown by the mean function.
please note: max() and quantile calculation work with no issue
Expected behavior:
No Null Pointer Exception
Actual behavior:
Null Pointer Exception
Environment info:
Linux 4.14.177-139.254.amzn2.aarch64 aarch64
Influx 2.0.0-beta.12 (git: ff620782eb) build_date: 2020-06-12T22:41:00Z
containerd: 1.3.2
CPU: AWS Graviton2 c6g.xlarge
Logs:
ts=2020-06-12T22:28:48.904353Z lvl=info msg="Dispatcher panic" log_id=0NMdJ8C0000 service=storage-reads component=dispatcher error="panic: runtime error: invalid memory address or nil pointer dereference" stacktrace="goroutine 11075 [running]:\nruntime/debug.Stack(0x4001489e00, 0x30ec700, 0x1ff0c96)\n\t/usr/local/go/src/runtime/debug/stack.go:24 +0x88\ngithub.com/influxdata/flux/execute.(*poolDispatcher).Start.func1.1(0x4001489e60)\n\t/go/pkg/mod/github.com/influxdata/flux@v0.69.2/execute/dispatcher.go:81 +0x13c\npanic(0x1cba4c0, 0x425c4b0)\n\t/usr/local/go/src/runtime/panic.go:679 +0x194\ngithub.com/apache/arrow/go/arrow/math.Float64Funcs.Sum(...)\n\t/go/pkg/mod/github.com/apache/arrow/go/arrow@v0.0.0-20191024131854-af6fa24be0db/math/float64.go:38\ngithub.com/influxdata/flux/stdlib/universe.(*MeanAgg).DoFloat(0x4002013a20, 0x40024e95c0)\n\t/go/pkg/mod/github.com/influxdata/flux@v0.69.2/stdlib/universe/mean.go:144 +0x14c\ngithub.com/influxdata/flux/execute.(*aggregateTransformation).Process.func1(0x315b8c0, 0x40024e9600, 0x0, 0xffff84165708)\n\t/go/pkg/mod/github.com/influxdata/flux@v0.69.2/execute/aggregate.go:142 +0x3b0\ngithub.com/influxdata/flux/execute.(*tableBuffer).Do(0x4000b6f950, 0x4001030af0, 0x0, 0x0)\n\t/go/pkg/mod/github.com/influxdata/flux@v0.69.2/execute/table.go:64 +0xcc\ngithub.com/influxdata/flux/execute.(*aggregateTransformation).Process(0x400101bb30, 0xcd5cfc81f3919fda, 0x72c1bd1cf28cf5ad, 0xffff8411f648, 0x4000b6f950, 0x1, 0x0)\n\t/go/pkg/mod/github.com/influxdata/flux@v0.69.2/execute/aggregate.go:127 +0x3f0\ngithub.com/influxdata/flux/execute.processMessage(0x3133840, 0x4000cc4d50, 0x313bc80, 0x400101bb30, 0x310e680, 0x40022d9a60, 0x4000f6ed00, 0x40022bbe8e, 0x0)\n\t/go/pkg/mod/github.com/influxdata/flux@v0.69.2/execute/transport.go:206 +0x248\ngithub.com/influxdata/flux/execute.(*consecutiveTransport).processMessages(0x4001489f20, 0x3133840, 0x4000cc4d50, 0xa)\n\t/go/pkg/mod/github.com/influxdata/flux@v0.69.2/execute/transport.go:159 +0xb0\ngithub.com/influxdata/flux/execute.(*poolDispatcher).run(0x4001489e60, 0x3133840, 0x4000cc4d50)\n\t/go/pkg/mod/github.com/influxdata/flux@v0.69.2/execute/dispatcher.go:132 +0x48\ngithub.com/influxdata/flux/execute.(*poolDispatcher).Start.func1(0x4001489e60, 0x3133840, 0x4000cc4d50)\n\t/go/pkg/mod/github.com/influxdata/flux@v0.69.2/execute/dispatcher.go:86 +0xa0\ncreated by github.com/influxdata/flux/execute.(*poolDispatcher).Start\n\t/go/pkg/mod/github.com/influxdata/flux@v0.69.2/execute/dispatcher.go:63 +0x74\n"

to add the issue is in beta.9, beta.10 and beta.12 (tested all 3 versions)

I have also had this problem. I tried the same setup on amd64, and it worked fine.

I did some more troubleshooting, and this problem seems to be happening when you use the Apache Arrow math library to sum an array of ints/floats. Flux already supports sum/mean without the shortcut (by iterating over the array) and I commented out the code and it no longer throws exceptions.
I am curious to know if the beta/nightly builds are running the tests, as there are a bunch of failures with flux.
diff.txt

I also see this problem on aarch64, but not in a container.  The processor is not an AWS G2.

@FrankStienhans2 @benlamonica @majulier our 2.0.3 release includes an updated ARM64 build which we hope will address issues like this. You can download the binaries here: https://dl.influxdata.com/influxdb/releases/influxdb2-2.0.3_linux_arm64.tar.gz
Please let me know how it goes if you try it out!

Closing this as I've seen enough successful reports about the new ARM builds to be confident things work in general, but please do open new issues if you hit any problems!


nixos/thunar: init

Description of changes
A module for the thunar file manager, which depends on the xfconf dbus service, and also has a dbus service and a systemd unit.
Fixes https://github.com/NixOS/nixpkgs/issues/65771
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Is it appropriate to have both services.xserver.desktopManager.xfce.thunarPlugins and programs.thunar.plugins?

Is it appropriate to have both services.xserver.desktopManager.xfce.thunarPlugins and programs.thunar.plugins?

After I posted that review I also realized that, and suggested him to use mkRenamedOption in this case.

Is it appropriate to have both services.xserver.desktopManager.xfce.thunarPlugins and programs.thunar.plugins?

After I posted that review I also realized that, and suggested him to use mkRenamedOption in this case.

Done.

I have tested with the Xfce DE and also with the awesome WM.


Cluster map issue

Select district, Block, Cluster
Issue:Cluster map is taking time to load  in all programs

Issue is fixed


FETCH RFC822 response lacks RFC822 information in icloud IMAP server

Server replies successfully, but the untagged FETCH line lacks RFC822 part. A workaround is to fetch BODY[] instead.
Found in the wild: snapshot at archive.org |  original
existing MUA workarounds

meli fixed in v0.8.7 https://github.com/meli/meli/commit/197132cca0901aac4c3204fd2f7691baf02b6edf https://git.meli-email.org/meli/meli/commit/197132cca0901aac4c3204fd2f7691baf02b6edf

I tried to find something quotable but gave up. NO -  fetch error: can't fetch that data indicates it's an error. But I feel we could miss something... Still, best bet is that it's an error.

What do you mean by "something quotable"?

I'm scared by IMAP and not sure if responding with less data items than requested could still be valid.
Maybe the "NO" response is reserved for the case when no data items at all could be constructed but the server knows they exist.
I hoped to find a sentence in the RFC like "a server MUST respond with all data items that were requested" but there is no clear answer so far.

There was no "NO" response actually according the user, but a successful one. It must be a bug


Add edit functionality to Vm Details overview

Pull Request Test Coverage Report for Build 564

63 of 122 (51.64%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-3.3%) to 82.683%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/components/Form/FormFactory.js
2
3
66.67%

src/components/InlineEdit/InlineEdit.js
6
8
75.0%

src/components/Flavor/Flavor.js
36
40
90.0%

src/components/Details/VmDetails/VmDetails.js
11
37
29.73%

src/utils/utils.js
2
28
7.14%

Totals

Change from base Build 431:
-3.3%

Covered Lines:
1363

Relevant Lines:
1566

💛  - Coveralls

Pull Request Test Coverage Report for Build 434

63 of 122 (51.64%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-3.3%) to 82.683%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/components/Form/FormFactory.js
2
3
66.67%

src/components/InlineEdit/InlineEdit.js
6
8
75.0%

src/components/Flavor/Flavor.js
36
40
90.0%

src/components/Details/VmDetails/VmDetails.js
11
37
29.73%

src/utils/utils.js
2
28
7.14%

Totals

Change from base Build 431:
-3.3%

Covered Lines:
1363

Relevant Lines:
1566

💛  - Coveralls


Create initial Visual Studio solution

Created a new solution in Visual Studio 2022 (version 17.4.x).
Options selected:

Template: Blazor WebAssembly app.
Individual accounts selected.
ASP.Net Core hosted selected.
Everything else set to default options.


Added config 'track_total_hits' for patching in embedded-CS for Erchef

:nut_and_bolt: Description: What code changed, and why?
We have added track_total_hits field in CS indexing, Now users can patch this config in embedded CS also.
This pr contains changes for that.
JIRA TICKET: https://progresssoftware.atlassian.net/browse/CHEF-5783

:chains: Related Resources
:+1: Definition of Done
:athletic_shoe: How to Build and Test the Change
user can use this
[erchef.v1.sys.index]
 track_total_hits=true

can be patched like this
chef-automate config patch test.toml

changes will reflect here.
sudo nano /hab/svc/automate-cs-oc-erchef/config/sys.config

:white_check_mark: Checklist
All PRs must tick these:

[ ] I have read the CONTRIBUTING document.
[ ] All commits signed-off for the Developer Certification of Origin.

With occasional exceptions, all PRs from Progress employees must tick these:

[ ] Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
[ ] Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
[ ] Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
[ ] Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
[ ] Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

All PRs from Progress employees should tick these if appropriate:

[ ] Tests added/updated? (all new code needs new tests)
[ ] Docs added/updated? (all customer-facing changes)

Please add a note next to any checkbox above if you are NOT ticking it.
:camera: Screenshots, if applicable

Demo Video for this: https://progresssoftware.sharepoint.com/:v:/s/ChefCoreC/ER7ArTDUvsVNmUHhZ7siOGQB2XCFTRwfRgV5Ft-M22SFFA?e=BdOf35


[KBFS-2830] KBFS Finder Banner in Folder Browser

@keybase/react-hackers @songgao

@chrisnojima Ready for another look.


Standard as an option in gulp kickstart

Currently, when running gulp kickstart, we show a confusing Standard option that currently doesn't stand for anything.

It would be nice to have the "Classic" theme option like in previous versions...

Hey @caneta, the existence of Classic in the previous version was an oversight.
We've never encouraged it nor supported extending classic as a recommended path. In fact, we didn't even publish updates of the classic theme throughout the 7.0.x lifecycle, and we're not planning to do it either for 7.1.x.
Being classic our specific implementation of a theme, providing it as an API makes it almost impossible to update without complicating updates even more.
I'd be fine to explore other options or ideas... for example, what it is that classic has nowadays that styled lacks that you'd want to have when starting your theme?

Trivial example: I would like to have a copy of the classic theme, but with background-color of the #wrapper element turned into red. How would you make that?

That should be doable using the Site or Page custom CSS options, for example, isn't it? Why would you want to deploy a whole theme for that?

Because turning the background into red is not the only thing I would like to change...suppose I have 100 CSS classes to add/modify, a copy of the theme could be useful...so again: how to reach this goal?

Right now, I think what most people do is copy/pasting it and then working on top of it.

Sure, I'm aware of it.

I'm not asking to bother you. We've always considered styled as the API we maintain and the one we try not to mess up because customers use it. We try not to push changes that would inadvertently end up in a clients theme.

I was just trying to start a theme extending the classic one with the gulp kickstart option, avoiding the copy/paste thing.
I'm not saying that classic theme is better, to me it would be an just an option like styled or unstyled.

We're more than happy to try to figure out what makes classic a better starting point than styled. Is it just because it's prettier? Is it because the amount of customization is low or very focused on custom development rather than out-of-the-box features?

Prettiness  and low customization are two vaid points, yes...

If we gave you classic as a starting point, but then we applied super-classic as a default... would you then want super-classic as the starting point?

Yes...why not?

Hey @caneta, I've created https://github.com/liferay/liferay-themes-sdk/issues/90 to gather some feedback about this. Please, would you mind collecting your thoughts over there?
This will be auto-closed when we release rc.1 as the ticket was just to remove the option for now.
Thanks!


token invalid

its saying my token is invalid?

Create a filename .evn and put this info
ME_TOKEN = Bot Token
ME_MONGO = MongoDB Url

[x] Thx

I’ve already done that, am I not supposed to replace the “Bot Token” and “MongoDB url” with my bot token and mongo url?


CNI plugin fails to respect IP address type of subject alternative name in apiserver's TLS certificate

I found this complaint in my CNI plugin's log:
2016-07-10 00:02:47,157 9293 [kube-system/kube-dns-v9-eei3v] DEBUG Querying Kubernetes API for Pod: https://<IP_ADDRESS>:443/api/v1/namespaces/kube-system/pods/kube-dns-v9-eei3v
2016-07-10 00:02:47,157 9293 [kube-system/kube-dns-v9-eei3v] DEBUG Using client certificate for Query API. cert: /etc/kubernetes/ssl/worker.pem, key: /etc/kubernetes/ssl/worker-key.pem
2016-07-10 00:02:47,180 9293 [kube-system/kube-dns-v9-eei3v] ERROR Exception hitting Kubernetes API
Traceback (most recent call last):
  File "calico_cni/policy_drivers.py", line 293, in _get_api_pod
  File "site-packages/requests/sessions.py", line 480, in get
  File "site-packages/requests/sessions.py", line 468, in request
  File "site-packages/requests/sessions.py", line 576, in send
  File "site-packages/requests/adapters.py", line 447, in send
SSLError: hostname '<IP_ADDRESS>' doesn't match either of 'kubernetes', 'kubernetes.default'

But here is the certificate that the apiserver is offering:
$ openssl x509 -noout -text -in apiserver.pem
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:<PHONE_NUMBER>9840230133 (0x9af3e63373b00ef5)
    Signature Algorithm: sha256WithRSAEncryption
        Issuer: CN=kube-ca
        Validity
            Not Before: Jun  6 17:16:10 2016 GMT
            Not After : Jun  6 17:16:10 2017 GMT
        Subject: CN=kube-apiserver
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                Public-Key: (2048 bit)
                Modulus:
                    <snip/>
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            X509v3 Basic Constraints:
                CA:FALSE
            X509v3 Key Usage:
                Digital Signature, Non Repudiation, Key Encipherment
            X509v3 Subject Alternative Name:
                DNS:kubernetes, DNS:kubernetes.default, IP Address:<IP_ADDRESS>, IP Address:<IP_ADDRESS>
    Signature Algorithm: sha256WithRSAEncryption
         <snip/>

And, just to prove I am not crazy:
/etc/kubernetes/ssl$ sudo openssl s_client -connect <IP_ADDRESS>:443 -cert worker.pem -key worker-key.pem -CAfile ca.pem
CONNECTED(00000003)
depth=1 CN = kube-ca
verify return:1
depth=0 CN = kube-apiserver
verify return:1
---
Certificate chain
 0 s:/CN=kube-apiserver
   i:/CN=kube-ca
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIC/zCCAeegAwIBAgIJAJrz5jNzsA71MA0GCSqGSIb3DQEBCwUAMBIxEDAOBgNV
BAMMB2t1YmUtY2EwHhcNMTYwNjA2MTcxNjEwWhcNMTcwNjA2MTcxNjEwWjAZMRcw
FQYDVQQDEw5rdWJlLWFwaXNlcnZlcjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBAK1cZX/6jNyzl+/PYt+HRb3+BsX72+u70fHVGb8jE9tu1n4uZronkSMl
0fNye8XIuNa6N/Vf19HcdKEmIAYcQZwc1HysgcMIj59hJovxmqNRDkil2Ff/Orfx
jM9nV9SHfptyweRurO5Lfv8VSjLQ+qxY/2jNRzs0Z8p22iXEGBsKAuXI6QuMqbm2
v6NzV/V0VwQRYB4AUzhm3DRn4u7J52v4m5Ef7lSdaZtcg784aZm3rLFrWE/GJSBP
WKza7ZVQ7k7Pwpw54O0WT7SS/qydH6I770TAjxlp6MKNELlEF88STN8EIhhZV38F
OZgAlcsdKPo2ggxCUfMze6tSq3uxl90CAwEAAaNRME8wCQYDVR0TBAIwADALBgNV
HQ8EBAMCBeAwNQYDVR0RBC4wLIIKa3ViZXJuZXRlc4ISa3ViZXJuZXRlcy5kZWZh
dWx0hwQKZAABhwRkfwACMA0GCSqGSIb3DQEBCwUAA4IBAQBAl5jBNQxftek2Ndum
HphZh7alnTUn7O7WJCqRa4VxgxDkPdIYIb2FYp4yPlVA6kZpWpov6OeAypq3hi2d
gJfs04nbEOjJo5NfWoITgRu5P+ttIDJJpjw2/CIgA1dmEKXMWuBBPPrlbIV1OSbE
K36+GuyUP7ZA4QvisqT2suxikzPUWWUq//1BLusjopcTtYL9dgrmB6XNg0JP0qkI
743QxUYwETrSDhokxurKaKJvCPYq52EFtcyvcN23iRGtBzv+HPc/idIWSXclWyYV
LMdgW+gtzFyGu1L//vIpC4lg6wHrXjhbFZeUlJ4sjvTulYPErWQpDTKwhGTo5uRS
oZce
-----END CERTIFICATE-----
subject=/CN=kube-apiserver
issuer=/CN=kube-ca
---
Acceptable client certificate CA names
/CN=kube-ca
Client Certificate Types: RSA sign, ECDSA sign
Requested Signature Algorithms: RSA+SHA256:ECDSA+SHA256:RSA+SHA384:ECDSA+SHA384:RSA+SHA1:ECDSA+SHA1
Shared Requested Signature Algorithms: RSA+SHA256:ECDSA+SHA256:RSA+SHA384:ECDSA+SHA384:RSA+SHA1:ECDSA+SHA1
Peer signing digest: SHA384
Server Temp Key: ECDH, P-256, 256 bits
---
SSL handshake has read 2927 bytes and written 2210 bytes
---
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES128-GCM-SHA256
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
...

Or, a little more succinctly:
/etc/kubernetes/ssl$ sudo curl --cacert ca.pem --cert worker.pem --key worker-key.pem https://<IP_ADDRESS>/version
{
  "major": "1",
  "minor": "3",
  "gitVersion": "v1.3.0",
  "gitCommit": "283137936a498aed572ee22af6774b6fb6e9fd94",
  "gitTreeState": "clean",
  "buildDate": "2016-07-01T19:19:19Z",
  "goVersion": "go1.6.2",
  "compiler": "gc",
  "platform": "linux/amd64"
}

BTW: I am not familiar with the packaging technology used to build the CNI plugin, but it looks like it is not picking up the latest version of the requests package.

I believe this is a urllib3 limitation where IP SANs are not respected.  See https://github.com/shazow/urllib3/pull/922
For now I think you'll need to use a DNS name.

Shouild be fixed in Go version - just needs to be tested


Error Handling - surround API calls with error handling

All of the API calls need some sort of error handling so that we don't have unhandled promise rejection errors

Can we use nodejs middleware to solve this problem?
Does #25 take care of this? Also, api-error-handler middleware is already installed. Have you seen anything make it out of this middleware?

Looks like PR 25 is still open... not sure whether it resolves this issue


fix(aws_lambda.py): fix cases where steps dict not found

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


Binary Search in a Sorted Array

DSA Challenges in Python
This directory contains a collection of Data Structures and Algorithms (DSA) challenges in Python. Each challenge focuses on key DSA concepts to help improve problem-solving skills.
Folder Structure
Please follow this structure when adding solutions:
/DSA_in_Python
    ├── /algorithms            # Algorithm challenges (e.g., sorting, searching)
    ├── /data_structures       # Data structure challenges (e.g., linked lists, trees)
    ├── /tests                 # Unit tests for algorithms and data structures
    ├── /utils                 # Helper functions or utilities
    └── README.md              # Project documentation

Contribution Guidelines

Organize Solutions: Place each solution in the relevant folder.
Naming: Use clear, descriptive names (e.g., binary_search.py, linked_list.py).
Testing: Write unit tests for each solution in the /tests folder.
Code Quality: Follow PEP 8 and write clean, modular code with comments.

Assign me please @Mugunth-dev .

Feel free to contribute @sharma-mohit-codes

@Mugunth-dev Thanks ! Will be submitting Binary Search in Sorted Array very soon !


Get-DPMSampleScript - Redirection doesnt work/pointed to wrong resource

[Hello,
I just find out the PS samples redirection is not working. It is nothing important:
PS C:\Program Files\Microsoft Azure Backup Server\DPM\DPM\bin> Get-DPMSampleScript
Once you hit Enter you are redirected to http://blogs.technet.com/ which is not exist anymore.
]

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

ID: 22c9bafa-6606-789e-24c8-f0f901c5da57
Version Independent ID: 0be47fb3-b9ee-0607-5a6d-ee9deb164d69
Content: PowerShell Samples - Azure Backup
Content Source: articles/backup/powershell-backup-samples.md
Service: backup
GitHub Login: @v-amallick
Microsoft Alias: v-amallick

@MilanKrocek Thank you for the feedback. We will review the content and update the documentation as appropriate.
@v-amallick FYI

@MilanKrocek The issue you reported doesn't seem to be related to this doc : PowerShell Samples - Azure Backup It would be great if you can share the documentation link you are referring, so that we can assist you accordingly.


MNT support oder requests versions

I've tested locally for all possibilities of installed packages (simplejson, json, old and new requests).
I don't think we need to add CI to test for old requests though.
Fixes #816

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Example Acceleration code for the RAK2270

Example Acceleration code for the RAK2270
@carlrakwireless
Where would I find example Acceleration code for the RAK2270?
It looks like it is fairly simple I2C communication

Hi @hpssjellis ,
The 3-axis accelerometer is based on RAK1904.
You can follow this guide for its basic functionality.
https://docs.rakwireless.com/Product-Categories/WisBlock/RAK1904/Quickstart/#software-configuration-and-example


Add online browser (Webassembly/emscripten) as supported platform to list.

I think it's important to show that some of consoles can work online in browser too and they have their own online showroom.
Now I know only two of them who support webassembly: TIC-80 and PICO-8. But maybe there are alot of more who may work in browser too.

By reviewing through the list, I added some supported exporting platforms.
Feel free to supply for any omission.

By reviewing through the list, I added some supported exporting platforms.
Feel free to supply for any omission.


Access crawled pages

Discussed in https://github.com/mercedes-benz/sechub/discussions/570

Originally posted by Jeeppler March  2, 2021
While doing a webscan it is helpful to look at all the pages the crawler found and analyzed for vulnerabilities. It might be beneficial to provide the ability to download and view all pages which have been visited from SecHub. However, this would be a "special report" and the question is, whether we want to have the functionality in SecHub and maybe even in the SecHub client?

Jeremias Eppler<EMAIL_ADDRESS>Daimler TSS GmbH, imprint

We solve this over user messages inisde the report.
Because of this we close this issue


Get FINOS listed in LF landscapes and landscapes.dev

yes, please do! it should be on landscapes.dev, we didn't include it for
awhile since your repo was closed :)
On Mon, Jun 29, 2020 at 3:17 PM Gabriele Columbro<EMAIL_ADDRESS>wrote:

OK let's put this one on hold then.
But then at least we should add the FINOS landscape to the main LF
landscapes. Shall I raise an issue here
https://github.com/cncf/landscapeapp/issues @caniszczyk
https://github.com/caniszczyk ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/finos/finos-landscape/issues/31#issuecomment-651337045,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAPSILPF6PXF2SDIXNLKNTRZDZFDANCNFSM4OLO75WQ
.

--
Cheers,
Chris Aniszczyk
http://aniszczyk.org
+1<PHONE_NUMBER>
Originally posted by @caniszczyk in https://github.com/finos/finos-landscape/issues/31#issuecomment-651342025

Done!


split kind cluster in template/real cluster

this PR splits the kind cluster in a template package and a cluster package which consumes the templates.
this PR fixes also a topologyFlag which was not set to true.

@henderiw I know that gives more flexibility in terms of customization but also requires more steps in terms of consumption, can you provide some use cases and advantages of this PR? Maybe this derserves more discussion.

/approve

Merged and tagged.


controller api: support for os-volume_attachments

Hi, would it be possible to support endpoint compatible with POST /v2.1/{tenant}/servers/{serverid}/os-volume_attachments ?
This is the endpoint web-ui is currently using to attach volumes.

We have implemented the Cinder API, and have not the Nova API.    They may be being deprecated so tools preferentially use the cinder and glance APIs directly, not the duplicated functionality.  Typical Openstack tools do use the Nova calls for volume attachment today.
Tools could be changed, the API implemented, or the API mapped inside Ciao to the existing cinder api endpoint implementation.


Hello, how do i change my node from localhost to <IP_ADDRESS>

Bug report
Thanks in advance
Relevant log output
No response
IPFS hash
No response
Subgraph name or link to explorer
No response
Some information to help us out

[ ] Tick this box if this bug is caused by a regression found in the latest release.
[ ] Tick this box if this bug is specific to the hosted service.
[X] I have searched the issue tracker to make sure this issue is not a duplicate.

OS information
Linux

What do you mean?

Closing, @userbox020 please re-open with more reproduction info

@azf20, @YaroShkvorets lol bros if you dont know how to start the graph-node server and not even know the difference between localhost and <IP_ADDRESS>
I would better look at code by myself fork it and solve it, I bet with a simple flag can be on the start up command will do


examples: CFO program

CFO program for the serum DEX and a bunch of misc features that make it easier to write.
New features include:

#[account(address = <expr>)] constraint for checking an address is as specified.
#[account(init, token, associated = ...)] constraint for creating token accounts inside an accounts context. This makes it a lot easier to check accounts are correct in susbequent instructions, since one can continue to use #[account(associated = ...)] to check the given account is correct.
Anchor.toml [scripts] section added for running bash commands via anchor run <script-name>.
Anchor.toml [clusters.<network>] table entries can now also use { address = <base58-str>, idl = <filepath-str> } to specify workspace programs.

Going to checkpooint this work, though the CFO program itself isn't complete.

[ ] #[account(address = <expr>)] / #[account(init, token = <mint-target>, authority = <auth-target>, ...)] need updated docs in anchor-derive-accounts :disappointed:
[ ] Is [scripts] section really required? Scripts can be placed in package.json and run with npm run or Makefile...


Please add another domain for SRH Berlin University of Applied Sciences

Students of SRH Berlin University of Applied Sciences got a new domain, stud.srh-university.de for their email addresses. To enable them to apply for educational licenses, I kindly ask you to also accept this domain name in the future.
Best regards,
Prof. Dr.-Ing. David Linner

@davidlinner Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


Updated ship Workflow concurrency group

Current dependencies on/for this PR:

main

PR #266   👈

This comment was auto-generated by Graphite.


Add binary for cartographer_grpc_server.

RFC=0002

@wally-the-cartographer merge

Merge requested by authorized user cschuet. Merge queue now has a length of 1.


The Github action build is failing due to no space left on disk

I created a simple HelloWorld application in Azure Functions without using any packages. Initially, I successfully deployed the app using the Azure Functions extension in Visual Studio Code. However, when I tried using the Azure Deployment Center workflow, it only worked once and then started failing. I am puzzled as to why it is not working for me and wonder if others have encountered this issue. I am using a consumption-based plan.  @ejizba  This is my first time using Node.js and previously I was using C#. Is there something special I need to configure, as the zip file is 210 MB with no packages installed (as I observed in the action logs or output in Visual Studio Code)?
This make me wonder how it's work for other. Is there anything I am missing here.  These are the logs I see
##[debug]ZIP Deploy response: {"statusCode":500,"statusMessage":"Internal Server Error","headers":{"content-length":"8754","connection":"close","content-type":"application/json; charset=utf-8","date":"Sun, 12 Feb 2023 02:22:24 GMT","server":"Microsoft-IIS/10.0","cache-control":"no-cache","expires":"-1","pragma":"no-cache","x-ms-request-id":"9373ad85-b9b1-410e-8924-b25bb8ff41c9","x-aspnet-version":"4.0.30319","x-powered-by":"ASP.NET"},"body":{"Message":"An error has occurred.","ExceptionMessage":"There is not enough space on the disk.\r\n","ExceptionType":"System.IO.IOException","StackTrace":"   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)\r\n   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)\r\n   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access)\r\n   at System.CodeDom.Compiler.TempFileCollection.EnsureTempNameCreated()\r\n   at System.CodeDom.Compiler.TempFileCollection.AddExtension(String fileExtension, Boolean keepFile)\r\n   at System.Web.HttpRawUploadedContent.TempFile..ctor()\r\n   at System.Web.HttpRawUploadedContent.AddBytes(Byte[] data, Int32 offset, Int32 length)\r\n   at System.Web.HttpBufferlessInputStream.EndRead(IAsyncResult asyncResult)\r\n   at System.IO.Stream.<>c.b__43_1(Stream stream, IAsyncResult asyncResult)\r\n   at System.Threading.Tasks.TaskFactory1.FromAsyncTrimPromise1.Complete(TInstance thisRef, Func3 endMethod, IAsyncResult asyncResult, Boolean requiresSynchronization)\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.WebHost.SeekableBufferedRequestStream.<ReadAsync>d__0.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Kudu.Services.ByteRanges.HttpRequestMessageExtensions.<CopyToAsync>d__1.MoveNext() in C:\\Kudu Files\\Private\\src\\master\\Kudu.Services\\ByteRanges\\HttpRequestMessageExtensions.cs:line 55\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Kudu.Services.Deployment.PushDeploymentController.<WriteSitePackageZip>d__25.MoveNext() in C:\\Kudu Files\\Private\\src\\master\\Kudu.Services\\Deployment\\PushDeploymentController.cs:line [86](https://github.com/anirugu/Proxy/actions/runs/4154207978/jobs/7186468408#step:5:87)1\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Kudu.Services.Deployment.PushDeploymentController.<>c__DisplayClass16_0.<<PushDeployAsync>b__0>d.MoveNext() in C:\\Kudu Files\\Private\\src\\master\\Kudu.Services\\Deployment\\PushDeploymentController.cs:line 444\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Kudu.Contracts.Infrastructure.LockExtensions.<LockOperationAsync>d__6.MoveNext() in C:\\Kudu Files\\Private\\src\\master\\Kudu.Contracts\\Infrastructure\\LockExtensions.cs:line 115\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Kudu.Services.Infrastructure.LockExtensions.<LockHttpOperationAsync>d__1.MoveNext() in C:\\Kudu Files\\Private\\src\\master\\Kudu.Services\\Infrastructure\\LockExtensions.cs:line 30\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)\r\n   at Kudu.Services.Deployment.PushDeploymentController.<PushDeployAsync>d__16.MoveNext() in C:\\Kudu Files\\Private\\src\\master\\Kudu.Services\\Deployment\\PushDeploymentController.cs:line 433\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at Kudu.Services.Deployment.PushDeploymentController.<ZipPushDeploy>d__12.MoveNext() in C:\\Kudu Files\\Private\\src\\master\\Kudu.Services\\Deployment\\PushDeploymentController.cs:line 105\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Threading.Tasks.TaskHelpersExtensions.<CastToObject>d__31.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Controllers.ApiControllerActionInvoker.d__0.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Filters.ActionFilterAttribute.d__5.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Web.Http.Filters.ActionFilterAttribute.d__5.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Filters.ActionFilterAttribute.d__0.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Filters.ActionFilterAttribute.d__5.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Web.Http.Filters.ActionFilterAttribute.d__5.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Filters.ActionFilterAttribute.d__0.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Controllers.ActionFilterResult.d__2.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Controllers.ExceptionFilterResult.d__0.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Web.Http.Controllers.ExceptionFilterResult.d__0.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n   at System.Web.Http.Dispatcher.HttpControllerDispatcher.d__1.MoveNext()"}}
Error: Failed to deploy web package to App Service.
Error: Execution Exception (state: PublishContent) (step: Invocation)
Error:   When request Azure resource at PublishContent, zipDeploy : Failed to use D:\a_temp\temp_web_package_5533907285453192.zip as ZipDeploy content
Error:     Failed to deploy web package to App Service.
Internal Server Error (CODE: 500)
Error:       Error: Failed to deploy web package to App Service.

Sorry for the delayed response. I'm not that familiar with "Azure Deployment Center workflow" or the logs listed. Hopefully you've either figured out your issue already or moved on to something else, but if not we would need more concrete repro steps


New documentation structure

Please, also update changes file: add your ticket's numbers and comments what was changed there