Failed to launch new .net core application to app engine flex.

Microsoft Visual Studio Community 2017
Version 15.4.4
VisualStudio.15.Release/15.4.4+27004.2009
Microsoft .NET Framework
Version 4.7.02053

Installed Version: Community

Visual Basic 2017   00369-60000-00001-AA909
Microsoft Visual Basic 2017

Visual C# 2017   00369-60000-00001-AA909
Microsoft Visual C# 2017

Application Insights Tools for Visual Studio Package   8.9.00809.2
Application Insights Tools for Visual Studio

ASP.NET and Web Tools 2017   15.0.30925.0
ASP.NET and Web Tools 2017

ASP.NET Core Razor Language Services   1.0
Provides languages services for ASP.NET Core Razor.

ASP.NET Web Frameworks and Tools 2017   5.2.50921.0
For additional information, visit https://www.asp.net/

Azure App Service Tools v3.0.0   15.0.30915.0
Azure App Service Tools v3.0.0

Common Azure Tools   1.10
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.

DeployToGae Extension   1.0
DeployToGae Visual Studio Extension Detailed Info

JavaScript Language Service   2.0
JavaScript Language Service

Microsoft Azure Tools   2.9
Microsoft Azure Tools for Microsoft Visual Studio 2017 - v2.9.50719.1

Microsoft Continuous Delivery Tools for Visual Studio   0.3
Simplifying the configuration of continuous build integration and continuous build delivery from within the Visual Studio IDE.

Microsoft JVM Debugger   1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines

Microsoft MI-Based Debugger   1.0
Provides support for connecting Visual Studio to MI compatible debuggers

NuGet Package Manager   4.4.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.

SQL Server Data Tools   15.1.61707.200
Microsoft SQL Server Data Tools

TypeScript   <IP_ADDRESS>
TypeScript tools for Visual Studio

Visual Studio Code Debug Adapter Host Package   1.0
Interop layer for hosting Visual Studio Code debug adapters in Visual Studio

PS > gcloud --version
Google Cloud SDK 180.0.0
beta 2017.09.15
bq 2.0.27
core 2017.11.10
gcloud
gsutil 4.28

Here's the build log:
Publishing WebApplication2 to Compute Engine.
dotnet publish -o "C:\Users\DPE Admin\AppData\Local\Temp\0jyto2oj.5pm" -c Release
Microsoft (R) Build Engine version <IP_ADDRESS>001 for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

  WebApplication2 -> C:\Users\DPE Admin\source\repos\WebApplication2\WebApplication2\bin\Release\netcoreapp2.0\WebApplication2.dll
  WebApplication2 -> C:\Users\DPE Admin\AppData\Local\Temp\0jyto2oj.5pm\
Services to deploy:

descriptor:      [C:\Users\DPE Admin\AppData\Local\Temp\0jyto2oj.5pm\app.yaml]
source:          [C:\Users\DPE Admin\AppData\Local\Temp\0jyto2oj.5pm]
target project:  [surferjeff-test2]
target service:  [default]
target version:  [20171117t153449]
target url:      [https://surferjeff-test2.appspot.com]

Beginning deployment of service [default]...
Building and pushing image for service [default]
Started cloud build [be39d55f-599a-45d9-8212-cc7665662fc3].

ERROR: (gcloud.app.deploy) Error Response: [9]
Application startup error:
Error:
  An assembly specified in the application dependencies manifest (WebApplication2.deps.json) was not found:
    package: 'Microsoft.AspNetCore.Antiforgery', version: '2.0.1'
    path: 'lib/netstandard2.0/Microsoft.AspNetCore.Antiforgery.dll'
  This assembly was expected to be in the local runtime store as the application was published using the following target manifest files:
    aspnetcore-store-2.0.3.xml

Failed to deploy project WebApplication2 to App Engine Flex.

Seems related to an old issue here:
https://github.com/dotnet/cli/issues/6516
On Fri, Nov 17, 2017 at 4:47 PM, Jeffrey Rennie<EMAIL_ADDRESS>wrote:

Here's the build log:
Publishing WebApplication2 to Compute Engine.
dotnet publish -o "C:\Users\DPE Admin\AppData\Local\Temp\0jyto2oj.5pm" -c Release
Microsoft (R) Build Engine version <IP_ADDRESS>001 for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.
WebApplication2 -> C:\Users\DPE Admin\source\repos\WebApplication2\WebApplication2\bin\Release\netcoreapp2.0\WebApplication2.dll
WebApplication2 -> C:\Users\DPE Admin\AppData\Local\Temp\0jyto2oj.5pm
Services to deploy:
descriptor:      [C:\Users\DPE Admin\AppData\Local\Temp\0jyto2oj.5pm\app.yaml]
source:          [C:\Users\DPE Admin\AppData\Local\Temp\0jyto2oj.5pm]
target project:  [surferjeff-test2]
target service:  [default]
target version:  [20171117t153449]
target url:      [https://surferjeff-test2.appspot.com]
Beginning deployment of service [default]...
Building and pushing image for service [default]
Started cloud build [be39d55f-599a-45d9-8212-cc7665662fc3].

ERROR: (gcloud.app.deploy) Error Response: [9]
Application startup error:
Error:
An assembly specified in the application dependencies manifest (WebApplication2.deps.json) was not found:
package: 'Microsoft.AspNetCore.Antiforgery', version: '2.0.1'
path: 'lib/netstandard2.0/Microsoft.AspNetCore.Antiforgery.dll'
This assembly was expected to be in the local runtime store as the application was published using the following target manifest files:
aspnetcore-store-2.0.3.xml
Failed to deploy project WebApplication2 to App Engine Flex.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-visualstudio/issues/847#issuecomment-345403622,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH7cpc8g3I2xvwTnpg10l2fbPIlB9ra6ks5s3ikqgaJpZM4QizMz
.

It definitely looks related to that issue, but I don't understand how to work around it.

Oh I see... Actually, we have not yet published the 2.0.3 version of the .NET Core runtime. See PR in aspnetcore

Hmmm... Just tried to repo this with VS 2017 and I had no issue. What template are you using? Is the app available somewhere I can try?

The animated gif shows which template and which options I'm choosing.

I tried updating visual studio 2017 to latest version and I still see the same error.
Microsoft Visual Studio Community 2017
Version 15.4.4
VisualStudio.15.Release/15.4.4+27004.2009
Microsoft .NET Framework
Version 4.7.02046

Installed Version: Community

Visual Basic 2017   00369-60000-00001-AA591
Microsoft Visual Basic 2017

Visual C# 2017   00369-60000-00001-AA591
Microsoft Visual C# 2017

Visual C++ 2017   00369-60000-00001-AA591
Microsoft Visual C++ 2017

Visual F# 4.1   00369-60000-00001-AA591
Microsoft Visual F# 4.1

Application Insights Tools for Visual Studio Package   8.9.00809.2
Application Insights Tools for Visual Studio

ASP.NET and Web Tools 2017   15.0.30925.0
ASP.NET and Web Tools 2017

ASP.NET Core Razor Language Services   1.0
Provides languages services for ASP.NET Core Razor.

ASP.NET Web Frameworks and Tools 2017   5.2.50921.0
For additional information, visit https://www.asp.net/

Azure App Service Tools v3.0.0   15.0.30915.0
Azure App Service Tools v3.0.0

Common Azure Tools   1.10
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.

DeployToGae Extension   1.0
DeployToGae Visual Studio Extension Detailed Info

JavaScript Language Service   2.0
JavaScript Language Service

Microsoft Azure Tools   2.9
Microsoft Azure Tools for Microsoft Visual Studio 2017 - v2.9.50719.1

Microsoft Continuous Delivery Tools for Visual Studio   0.3
Simplifying the configuration of continuous build integration and continuous build delivery from within the Visual Studio IDE.

Microsoft JVM Debugger   1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines

Microsoft MI-Based Debugger   1.0
Provides support for connecting Visual Studio to MI compatible debuggers

Microsoft Visual C++ Wizards   1.0
Microsoft Visual C++ Wizards

Microsoft Visual Studio VC Package   1.0
Microsoft Visual Studio VC Package

NuGet Package Manager   4.4.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.

SQL Server Data Tools   15.1.61707.200
Microsoft SQL Server Data Tools

TypeScript   <IP_ADDRESS>
TypeScript tools for Visual Studio

Visual Studio Code Debug Adapter Host Package   1.0
Interop layer for hosting Visual Studio Code debug adapters in Visual Studio

Visual Studio tools for CMake   1.0
Visual Studio tools for CMake

I still have no work-arounds.  An application created with "dotnet new MVC" suffers the same problem.

And deploying from a new Google Cloud Platform Web Application template fails with this error:
Publishing GcpProject2 to Compute Engine.
dotnet publish -o "C:\Users\Jeffrey Rennie\AppData\Local\Temp\jpolqxei.lnu" -c Release
Microsoft (R) Build Engine version <IP_ADDRESS>001 for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

  GcpProject2 -> C:\Users\Jeffrey Rennie\source\repos\GcpProject2\GcpProject2\bin\Release\netcoreapp2.0\GcpProject2.dll
  It was not possible to find any compatible framework version

  The specified framework 'Microsoft.NETCore.App', version '1.0.0' was not found.

    - Check application dependencies and target a framework version installed at:

        \

    - Alternatively, install the framework version '1.0.0'.

C:\Users\Jeffrey Rennie\source\repos\GcpProject2\GcpProject2\GcpProject2.csproj(24,5): error MSB3073: The command "dotnet bundle" exited with code -2147450749.
Failed to deploy project GcpProject2 to App Engine Flex.

The fact that the "dotnet publish" command failed can indicate a corrupted installation. It is interesting that is looking for the reference assemblies at the \ path, instead of the right location.
Would you be able to try this out in a different machine?

Just realized that the last entry refers to the 1.0.0 runtime, which means you probably don't have an SDK that supports netcoreapp1.0 installed on the machine. The fact that we allow you to instantiate that template is indeed a bug.

Can you list the SDKs that you have installed? Typically they will be under c:\Program Files\dotnet\sdk.

I got some juicy details here:
On a machine with the following dotnet core SDKs installed:
1.0.1
1.0.4
1.1.0
2.0.0
2.0.2
The app engine flex deploy succeeded.  Then, I uninstalled 2.0.0 and 2.0.2 and installed 2.0.3, and the app engine deploy failed with the exact error above.

I reinstalled 2.0.2, and it failed as before.

I reinstalled 2.0.0, and it failed as before.

I uninstalled 2.0.3 and it still failed as before!

Created a new project, and it succeeded.
So to reproduce the bug, it looks like you must run 'dotnet new mvc' with version 2.0.3 of the SDK.

Ok, the 2.0.3 image is not yet released in App Engine, which is why you are seeing this. It would be good for the extension to have an error message about this (not sure how it will be done) but this is not a P0, this is what happens when you used an unsupported SDK.
I have confirmed many times that if you use the 2.0.0 SDK the resulting apps will deploy successfully.
The core of the problem is this:
<Project Sdk="Microsoft.NET.Sdk.Web">

  <PropertyGroup>
    <TargetFramework>netcoreapp2.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.All" Version="2.0.3" />
  </ItemGroup>

  <ItemGroup>
    <DotNetCliToolReference Include="Microsoft.VisualStudio.Web.CodeGeneration.Tools" Version="2.0.1" />
  </ItemGroup>

  <!-- Copy the app.yaml on publish -->
  <ItemGroup>
    <None Include="app.yaml" CopyToOutputDirectory="Always" />
  </ItemGroup>

</Project>

The Microsoft.AspNetCore.All metapackage is version 2.0.3 which requires the 2.0.3 runtime to run. I have confirmed that a 2.0.0 app will deploy successfully.

I'm glad you found the origin of the issue.
I'm re-opening this bug because it is still a frustrating dead end for the user.  When users first try the extension, they have no concept of a "supported SDK."  All they know is that:

Deploying a new .NET core app fails.
Deploying a GCP .NET core app fails.
Therefore, Google App Engine is broken.  They really don't know what they're doing when it comes to .NET.

Point 3 is not true, but it's a natural conclusion to draw.  First impressions are critical.
When the VS extension begins a deploy, the extension should verify that the app being deployed is compatible with App Engine Flex, and give the user an error message that will help them understand and work around the situation.

I had the same issue today with the same error Message. It took me a while to figure out how to work around it. I am running dotnet cli on Ubuntu.
Workaround: Edit the .csproj file and reduce the asp.net core version used.
My previous dependency which showed the same error message:
<PackageReference Include="Microsoft.AspNetCore.All" Version="2.0.6" />
And it worked today with this dependency:
<PackageReference Include="Microsoft.AspNetCore.All" Version="2.0.3" />
After changing the AspNetCore.All version using dotnet publish -c release and then gcloud app deploy ... worked.
Thanks to the above hints I could find my way around this issue.

I've also hit this issue, until it's fixed I have no idea how to use .NET Core on GCP, or even whether it's possible at all.
Thank you @iantalarico for looking into this.

I am also facing the same issue when published the asp.net core blazor server app in to GCP.

I had the same issue today with the same error Message. It took me a while to figure out how to work around it. I am running dotnet cli on Ubuntu.
Workaround: Edit the .csproj file and reduce the asp.net core version used.
My previous dependency which showed the same error message:
<PackageReference Include="Microsoft.AspNetCore.All" Version="2.0.6" />
And it worked today with this dependency:
<PackageReference Include="Microsoft.AspNetCore.All" Version="2.0.3" />
After changing the AspNetCore.All version using dotnet publish -c release and then gcloud app deploy ... worked.
Thanks to the above hints I could find my way around this issue.

this will not work in core 3.0 + since its removed

I had the same problem trying to work through the tutorial at: https://codelabs.developers.google.com/codelabs/cloud-app-engine-aspnetcore/#6
with the key error-out: Step #0: No valid .NET Core runtime version found for the app or it is not a supported app.
I tried unsuccessfully to change the aspnetcore version to 2.2 and 2.1 which result in build errors.


obs-plugin-droidcam: Add version 1.6.0

Closes  #7107

[x] I have read the Contributing Guide.

/verify

/verify

Alle Änderungen sehen gut aus.
Warten Sie auf die Überprüfung durch menschliche Mitarbeiter.
droidcam-obs-plugin

[x] Beschreibung
[x] Lizenz
[x]  Hashes
[x] Schachbrett
[x] Automatische Aktualisierung

Closes #7107

[x]  I have read the Contributing Guide.

for plugins of other apps: <app>-plugin-<plugin_name>.json
❯ scoop search obs
Results from local buckets...

Name             Version      Source   Binaries
----             -------      ------   --------
obs-studio-small 21.1.2       extras
obs-studio       28.1.2       extras
streamlabs-obs   1.12.1       extras
obs-studio-pre   29.0.0-beta1 versions
obs-studio27     27.2.4       versions

consider the variant versions of OBS, obs-plugin-droidcam is acceptable.
here is an example:
❯ scoop search keepass
Results from local buckets...

Name                               Version Source   Binaries
----                               ------- ------   --------
keepass-plugin-keeagent            0.13.3  extras
keepass-plugin-keeanywhere         2.0.3   extras
keepass-plugin-keepasshttp         <IP_ADDRESS> extras
keepass-plugin-keepassnatmsg       2.0.14  extras
keepass-plugin-keepassrpc          1.14.0  extras
keepass-plugin-keetraytotp         0.108.0 extras
keepass-plugin-kpenhentryview      2.4.3   extras
keepass-plugin-readable-passphrase 1.3.0   extras
keepass-plugin-sequencer           0.1.1   extras
keepass-plugin-webautotype         6.8.2   extras
keepass-plugin-yafd                <IP_ADDRESS> extras
keepass                            2.52    extras
keepassxc                          2.7.4   extras
keepassxc2.6.6                     2.6.6   versions

/verify

/verify

@HUMORCE It's important to keep the else function, or it will not work properly.

@HUMORCE don't merge, I am still running some tests of the manifest on my machine. I will let you know when this PR is ready.

The current manifest is not functioning properly. Why does Scoop only execute the first command in the if statement and skips the other commands?
Checking hash of DroidCamOBS.Setup.1.6.0.exe ... ok.
Extracting dl.7z ... done.
Running pre_install script...
INFO  Install for obs-studio Copy-Item
ERROR obs-plugin-droidcam requires any obs-studio variant to be installed!
Please install either,
extras/obs-studio
extras/obs-studio-small
versions/obs-studio27
versions/obs-studio-pre

this plugin is not a development tool or one of development toolchain, we should not use method such as depends to restrict installation.
expected behaviour: decompress file and nothing happens, if OBS not found.

this plugin is not a development tool or one of development toolchain, we should not use method such as depends to restrict installation.
expected behaviour: decompress file and nothing happens, if OBS not found.

I'm not using the depends property in my manifest.

/verify


add month dropdowns

The styles are horribly broken, but apart from that, it works.
Oh, and it has no tests...

Current coverage is 88.11% (diff: 51.72%)

Merging #657 into master will decrease coverage by 2.19%

@@             master       #657   diff @@
==========================================
  Files            12         13     +1
  Lines           547        572    +25
  Methods          16         17     +1
  Messages          0          0
  Branches        100        103     +3
==========================================
+ Hits            494        504    +10
- Misses           15         28    +13
- Partials         38         40     +2

Powered by Codecov. Last update 3f1e195...7a8c4d3

It probably makes sense to review #646 first and revisit this afterwards.

@martijnrusschen this should be ready for review

Would you mind adding an example to the docs on how this works? Similar to the year dropdown.

Done. But I noticed that the year is not dsplayed in the header if showMonthDropdown  is set. This is probably a bug. Might be related to #533.

Awesome, thanks for the help!


My Profile Page - Remove Image

Web Path
Home Page -> John Doe -> My Profile

Requirement

Remove "Under Constriction" image
Remove Upload button

Screen Shot

This issue was moved to Code4SocialGood/c4sg-web#57

Hi Jenny,
I am having flu from last week. Not able to work on anything. I would like
to take some time from you. Please let me know if that is ok.
Thanks,
Sabrina
On Thu, Mar 16, 2017 at 8:32 PM, Code for Social Good <
<EMAIL_ADDRESS>wrote:

This issue was moved to Code4SocialGood/c4sg-web#57
https://github.com/Code4SocialGood/c4sg-web/issues/57
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/Code4SocialGood/C4SG-Obsolete/issues/460#issuecomment-287242143,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATkfjL3rTJ964M3ESH4NZssmL99IRtNiks5rmeK5gaJpZM4MWGxo
.


Add auto-links for external citations

For eregs/notice-and-comment#393

Failures here are expected -- it adds new entries to the external citations layer.


TSQL/MS SQL Server statements/syntax not supported.

From https://github.com/dbeaver/dbeaver/issues/16756.
Two large TSQL files:
https://github.com/jOOQ/sakila/blob/main/sql-server-sakila-db/sql-server-sakila-schema.sql
https://github.com/jOOQ/sakila/blob/main/sql-server-sakila-db/sql-server-sakila-insert-data.sql

Did you investigate this issue further?


Error: No mudule named '_tkinter'

Graphics and UI through Python is unsupported yet. It's a TODO on my list and will be possible in a future release of 3DS.py.


Android Java: 17.3 Android Chronometer

Description

Chronometer class
its application

Domain
Android Dev (Java)
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign


Send an email notification when added as a member of a collective/org

Fixes https://github.com/opencollective/opencollective/issues/566
Fixes https://github.com/opencollective/opencollective/issues/565

Coverage increased (+0.02%) to 77.754% when pulling 3c74ae40e63a8daf61e4aadcc585f6875a6c0727 on fix566 into 998507e1279d08769a5025e8cb9179758e40665a on master.

Let me know if you have any comment on the default email template for this: https://github.com/opencollective/opencollective-api/blob/3c74ae40e63a8daf61e4aadcc585f6875a6c0727/templates/emails/collective.newmember.hbs
@piamancini @asood123

Looks fine


helm chart using stable tag

Hey there,
first off, thanks for such an awesome an helpful tool!
when deploying the provided helm chart into kubernetes using the stable image from hub.docker.com the deployment (readiness and liveness probe) fails because the exposed ports where changed from 10080/10025/10110 to 9000/2500/1100.
Are you planing to provide a helm chart and docker image(tag) for v2.0.0?
If I can be of any assistance in that manner please let me know. I rather deploy the chart right from the source than maintain a custom chart in our repo.

Thanks for the kind words.
  I'd love to get the helm charts updated for the stable release, but I expect there is quite some learning curve to it, plus I don't do much development during the N. hemisphere summer months.
@cpanato contributed the helm charts and may be able to provide some guidance for anyone interested in helping. See issue #97 for details.
Also worth noting I received an automated email with some suggested improvements: http://helmqa-zhaw-hendu.appuioapp.ch/charts/inbucket

Hey!!
the update the helm charts to the latest version is in my backlog, I just need to get used with the new release to understand what are the changes.
Lets to that, next week i will save some time to make this happen. sounds good?

ENVs actually translate quite well to helm. Either using them directly in the deployment description or injecting them by ConfigMap.
@cpanato I would suggest adding this option either way and giving the commented out examples in the values.yaml or adding a configmap.yaml template with default values. I already noticed env being read from Values.env in the deployment but no env variable was specified in the values.yaml file. So this might be the faster solution
@jhillyerd I also noticed that there is no tag for version 2.0.0 in the hub.docker.com repository. I think that would be helpful for a default tag in the helm config for the new version. Otherwise using the stable tag might lead to problems in case of breaking changes in newer version tagged as stable as well.

I started using the recommended vN.N.N tagging format on GitHub, looks like that broke the regex that was configured on the hub.  I've updated it, but I don't see a way to manually tag the existing release.  Is that something I have to do from the docker command line?

yes. tag the image manually on command line and than push it to docker hub.

PR opened: https://github.com/helm/charts/pull/7126
it will be good to have a docker image with 2.0.0 (release-2.0) or something

Assigning to myself as a reminder to add a release tag to docker hub.

helm chart merged, we can close this issue

Thanks for working on this!


feat: replace sane with chokidar

Summary
sane pulls in old version of micromatch. We're also already vendoring their watchman watcher (#5387) and the fsevents watcher they removed (#8258). Replacing with chokidar allows us to drop that last vendoring as chokidar abstracts over it.
We might need to create a chokidar abstraction here, I just did the minimal to make it work.
This is very untested

Test plan
Dunno. It works for the simple cases I played with locally, but it needs real usage.

Hmm, #5387 imports some stuff from sane

We should vendor it, I guess

Hey @SimenB, thanks for your amazing work, its actually should also improve DX for Windows users of Metro. What is currently blocking you from landing this PR? Do you need some help with it?

@arhelmus no real blocker, just time and energy to work on this. It'll require extensive testing, so I haven't really found the time to do it.
This is the part of the code base I've touched the least (along with watch mode, which also mostly is haste-map), so I'm a but hesitant to merge it

@SimenB I would love to help you to test it on Mac and Windows, but I missing lots of context. Can you provide some test plan which I can follow. The best is: create new file/rename it/upper lower case it/delete and see how watchers will react.

Yeah, that's essentially it - make sure you're disabling watchman (by either not having it installed or by passing --no-watchman).
Note that the linting errors now (https://github.com/facebook/jest/pull/10048#issuecomment-629265479) need to be solved first. We don't really have many tests for watch mode on CI which is why it's passing even though those imports does not resolve presumably).

Given https://github.com/amasad/sane/issues/159 (upstream dependency execa has critical vuln) and that sane is basically unmaintained, this PR would be really helpful!

Feel free to open PRs against my branch (or opening a new PR based on this branch) fixing the type error. This will need to be tested thoroughly, but once we have a green PR I can make alpha releases

Testing this, it's horribly slow during first run - about 50x regression over what's currently in master. I think this is due to it reading (or at least stating) all files it finds during initial crawl instead of just registering a watcher.
In addition, on change it emits change events for node_modules - I was unable to figure out how or where. In monorepos any local files are usually symlinked in node_modules, meaning they all triggered a change event (even worse, it happened staggered. So changing one file which ended up regenerating a bunch of .d.ts changes made the tests re-run 10-12 times on my machine).

So instead of spending time trying to figure out how to make chokidar do what I want, I think it's better to just vendor the last watcher from sane (the node watcher - we already vendor both the watchman watcher and the fsevents one).
#10919


TypeScript 5.1 support

TypeScript 5.1 has new type JSX.ElementType to determine the type of JSX element.
https://devblogs.microsoft.com/typescript/announcing-typescript-5-1-beta/#decoupled-type-checking-between-jsx-elements-and-jsx-tag-types

jsx-slack should be working on TS 5.1 with no changes. Close.


[JENKINS-65398] Terminology Changes

[x] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your master branch!
[x] Ensure that the pull request title represents the desired changelog entry
[x] Please describe what you did
[x] Link to relevant issues in GitHub or Jira
[x] Link to relevant pull requests, esp. upstream and downstream changes
[x] Ensure you have provided tests - that demonstrates feature works or fixes the issue

@batmat any update on getting  this merged?


viewClass is not a constructor

Hi?
I am using nativescript-image-swipe in Angular for Android platform. When I load the page it throws this error:
ERROR Error: Uncaught (in promise): TypeError: viewClass is not a constructor
JS: TypeError: viewClass is not a constructor.
And does not show anythng.
What does it mean?

Hey @YoungLinkar , please refer to the demo-ng example in this repo and compare it to your integration to see what might be problem. Other than that I cannot help you with this little of info provided.

Thanks for answering. Let me try

Hey @YoungLinkar , please refer to the demo-ng example in this repo and compare it to your integration to see what might be problem. Other than that I cannot help you with this little of info provided.

Hi?
I was using local storage so it didnt work and it threw a malFormedUrl. Then I tried some Urls in my firebase storage and it worked:

I have few questions:
1-The plugin does not support files from local storage?
2-Could it work inside TabViews?
Another thing is the allowZoom property when set to true didnt work for me. Anyway at least i have something to work with.

Hey @YoungLinkar ,
For 1 - you need to generate URL from your local files, then it should be working. So your URLs should look something like file://.....
For 2 - never used it inside a tab view, so you have to try it out yourself 😉
Not sure what do you mean with the allowZoom property. By default it is true, and you are also setting it to true???

Hey @YoungLinkar ,
For 1 - you need to generate URL from your local files, then it should be working. So your URLs should look something like file://.....
For 2 - never used it inside a tab view, so you have to try it out yourself 😉
Not sure what do you mean with the allowZoom property. By default it is true, and you are also setting it to true???

Thanks.
Yes, I'm setting to true because it's not working

Make sure your images are large enough. In my projects I have never set the property and it works just fine 😄

Alright. I tested now inside tabview, it works!
I have an image with: (1920: 1280) isn't it large enough
Em qua, 17 de out de 2018 às 09:34, Peter Staev<EMAIL_ADDRESS>escreveu:

Make sure your images are large enough. In my projects I have never set
the property and it works just fine 😄
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/PeterStaev/nativescript-image-swipe/issues/29#issuecomment-430539409,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AhDxpHZe-8Lb2tny9Rou3p9sG5ZewWWXks5uluuOgaJpZM4XeWfq
.

--
ATENTAMENTE;
Eng. Adelino Safeca
Software & Web Developer
|


added css for card

I completed the task for css (hard). please assign this issue to me.

Hi! As it says on the issue descriptions, we don't assign these tasks to anyone in this project.


Suggestion: Make Laser Amplifier Forge Micro Part Compatible

It would be neat to have a laser door but not have the amplifiers visible and shoot through hollow covers (which it already does but doesn't look good)

This would require a model change of the Laser Amplifier, something which I am not currently willing to do.


Download an entire channel does not work anymore

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2<IP_ADDRESS>. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2<IP_ADDRESS>

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the -v flag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
$ youtube-dl https://www.youtube.com/user/caseyneistat/videos -v
[debug] System config: []
[debug] User config: ['-o', '%(title)s.%(ext)s']
[debug] Custom config: []
[debug] Command-line args: ['https://www.youtube.com/user/caseyneistat/videos', '-v']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2<IP_ADDRESS>
[debug] Python version 3.5.4 - Linux-4.12.0-1-amd64-x86_64-with-debian-buster-sid
[debug] exe versions: ffmpeg 3.3.3, ffprobe 3.3.3, rtmpdump 2.4
[debug] Proxy map: {}
[youtube:user] caseyneistat: Downloading channel page
[youtube:user] caseyneistat: Downloading page #1
[download] Downloading playlist: caseyneistat
[youtube:user] playlist caseyneistat: Downloading 0 videos
[download] Finished downloading playlist: caseyneistat

...
<end of log>

Description of your issue, suggested solution and other information
I use to watch channel in shuffle mode with mpv and the command mpv --ytdl --shuffle https://www.youtube.com/user/caseyneistat/videos. It doesn't work anymore. I first opened a bug report in mpv github and it seemes the bug is related to youtube-dl. Indeed, downloading the entire channel doesn't work.

I have also had this issue. I'd appreciate a fix from anyone, thanks.

Me too... AFAIK, this issue started around 3 days ago.

This has been reported before. See #14083. A solution has been posted there as well.


Intermittence “PKIX path building failed” issue during Tessera startup

This issue is similar to the reported under Quorum Ticket 914362.
Tested versions:

Quorum: 22.1.1
Tessera: 22.1.3

Reproducible steps:

Git clone from https://github.com/anthonyyeong18/quorum-examples
a. This is a fork from Consensys, with some config changes to enable SSL and updated images on Tessera
Run:
a. docker-compose up -d
Wait for all tessera services to be up and running (using docker ps)
Run “docker log ” on all 7 running tessera containers

Expected results:

All 7 containers should be showing following logs:
2022-06-27 20:36:49.974 [pool-4-thread-1] INFO c.q.t.p.p.PartyInfoBroadcaster - Started PartyInfo polling round
2022-06-27 20:36:49.975 [pool-4-thread-1] INFO c.q.t.p.p.PartyInfoBroadcaster - Finished PartyInfo polling round
2022-06-27 20:36:54.975 [pool-4-thread-1] INFO c.q.t.p.p.PartyInfoBroadcaster - Started PartyInfo polling round
2022-06-27 20:36:54.976 [pool-4-thread-1] INFO c.q.t.p.p.PartyInfoBroadcaster - Finished PartyInfo polling round
2022-06-27 20:36:59.976 [pool-4-thread-1] INFO c.q.t.p.p.PartyInfoBroadcaster - Started PartyInfo polling round
2022-06-27 20:36:59.977 [pool-4-thread-1] INFO c.q.t.p.p.PartyInfoBroadcaster - Finished PartyInfo polling round
2022-06-27 20:37:04.980 [pool-4-thread-1] INFO c.q.t.p.p.PartyInfoBroadcaster - Started PartyInfo polling round
2022-06-27 20:37:04.981 [pool-4-thread-1] INFO c.q.t.p.p.PartyInfoBroadcaster - Finished PartyInfo polling round
2022-06-27 20:37:09.983 [pool-4-thread-1] INFO c.q.t.p.p.PartyInfoBroadcaster - Started PartyInfo polling round

Results observed:

Out of 7 running tessera containers, few of it will have SSL PKIX issue:
2022-06-27 08:22:01.361 [pool-4-thread-1] INFO c.q.t.p.p.PartyInfoBroadcaster - Started PartyInfo polling round
2022-06-27 08:22:01.362 [pool-4-thread-1] INFO c.q.t.p.p.PartyInfoBroadcaster - Finished PartyInfo polling round
2022-06-27 08:22:01.396 [pool-3-thread-7] WARN c.q.t.p.p.PartyInfoBroadcaster - Failed to connect to node https://txmanager7:9000/, due to javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
2022-06-27 08:22:01.407 [pool-3-thread-2] WARN c.q.t.p.p.PartyInfoBroadcaster - Failed to connect to node https://txmanager2:9000/, due to javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
2022-06-27 08:22:01.416 [pool-3-thread-10] WARN c.q.t.p.p.PartyInfoBroadcaster - Failed to connect to node https://txmanager6:9000/, due to javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
2022-06-27 08:22:01.422 [pool-3-thread-6] WARN c.q.t.p.p.PartyInfoBroadcaster - Failed to connect to node https://txmanager3:9000/, due to javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
2022-06-27 08:22:01.434 [pool-3-thread-8] WARN c.q.t.p.p.PartyInfoBroadcaster - Failed to connect to node https://txmanager4:9000/, due to javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
2022-06-27 08:22:01.436 [pool-3-thread-4] WARN c.q.t.p.p.PartyInfoBroadcaster - Failed to connect to node https://txmanager5:9000/, due to javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
2022-06-27 08:22:01.436 [pool-3-thread-1] WARN c.q.t.p.p.PartyInfoBroadcaster - Failed to connect to node https://<IP_ADDRESS>:9000/, due to javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
2022-06-27 08:22:01.440 [pool-3-thread-5] WARN c.q.t.p.p.PartyInfoBroadcaster - Failed to connect to node https://<IP_ADDRESS>:9000/, due to javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
2022-06-27 08:22:01.443 [pool-3-thread-3] WARN c.q.t.p.p.PartyInfoBroadcaster - Failed to connect to node https://txmanager1:9000/, due to javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
2022-06-27 08:22:01.444 [pool-3-thread-9] WARN c.q.t.p.p.PartyInfoBroadcaster - Failed to connect to node https://<IP_ADDRESS>:9000/, due to javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
2022-06-27 08:22:06.363 [pool-4-thread-1] INFO c.q.t.p.p.PartyInfoBroadcaster - Started PartyInfo polling round
2022-06-27 08:22:06.364 [pool-4-thread-1] INFO c.q.t.p.p.PartyInfoBroadcaster - Finished PartyInfo polling round
2022-06-27 08:22:06.492 [pool-3-thread-8] WARN c.q.t.p.p.PartyInfoBroadcaster - Failed to connect to node https://txmanager4:9000/, due to javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
2022-06-27 08:22:06.522 [pool-3-thread-7] WARN c.q.t.p.p.PartyInfoBroadcaster - Failed to connect to node https://txmanager7:9000/, due to javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Notes:

Above steps have been tested several times on:
a. Local laptop with Windows 11 Pro – WSL2 Ubuntu 20.04 (12 logical cores,32GB RAM)
b. GCP VM – Ubuntu 20.04 (4 vCPU,16GB RAM,30GB HD)
Issue was “intermittence” as not all containers having PKIX issue. Hence need to docker log all the tessera containers.
In the event if no PKIX issue was observed, try the steps again after cleaning up the “dockerData” folder.
This is not related to SSL SNI validation, as issue is reproducible even with the validation disabled.

https://hub.docker.com/layers/quorumengineering/tessera/develop/images/sha256-21f5c9f4670f028e3303796b86eb2474ef3ec9c361db34d03d5a92a9fdf5d3de?context=explore

@antonydenyer, have tested the latest tessera:develop image on similar docker compose setup.
No longer see the issue after many run. Thanks for the fix.


[FCWP-6] onFileCommentMismatch is getting ignored for 'replace'

onFileCommentMismatch is getting ignored due to a check on different param.

Fixed in https://github.com/saurabhiam/file-comments-webpack-plugin/pull/11


Convert tags in ALL CAPS to small caps

This might require converting tags from a string to an object with text and grammatical fields.

Waiting for actual instances of this to be in the tags.

As of 7/29/24 there are still no tags in all caps.
Here's the code you used to check for instances:
import Database from './data/Database.js'

const db = new Database

await db.initialize()

const capsRegExp = /^([A-Z]|\s)+$/v

const caps = db.components
.filter(Boolean)
.filter(component => component.tags?.some(tag => capsRegExp.test(tag)))

console.log(caps)

Handled as part of #174.


NotADirectory error thrown by treetime.py

art@Wernstrom covizu % python3 covizu/treetime.py ~/Desktop/by_lineage.json --ref covizu/data/NC_045512.fa
Traceback (most recent call last):
  File "covizu/treetime.py", line 250, in <module>
    args = parse_args()
  File "covizu/treetime.py", line 228, in parse_args
    default=open(os.path.join(covizu.__path__[0], "data/NC_045512.fa")),
NotADirectoryError: [Errno 20] Not a directory: '/Library/Python/3.8/site-packages/covizu-0.3-py3.8.egg/covizu/data/NC_045512.fa'

This might be a macOS-specific problem.

Added an if..else in dev branch to catch case when package __path__ points to egg (macOS), which is what raises the directory error.

Added an if..else in dev branch to catch case when package __path__ points to egg (macOS), which is what raises the directory error.


use amplify-prompts in place of inquirer

Description of changes

migration to use amplify-prompts package.
Changes are reviewed in https://github.com/aws-amplify/amplify-cli/pull/8182
Issue #, if available

Description of how you validated changes
unit and e2e tests updated
Checklist

[x] PR description included
[x] yarn test passes
[x] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #8183 (90a2b70) into tagged-release-without-e2e-tests/geo (ec13554) will increase coverage by 1.20%.
The diff coverage is 70.37%.

@@                           Coverage Diff                            @@
##           tagged-release-without-e2e-tests/geo    #8183      +/-   ##
========================================================================
+ Coverage                                 53.28%   54.48%   +1.20%
========================================================================
  Files                                       555      664     +109
  Lines                                     28016    37895    +9879
  Branches                                   5429     7788    +2359
========================================================================
+ Hits                                      14927    20648    +5721
- Misses                                    12105    16407    +4302
+ Partials                                    984      840     -144

Impacted Files
Coverage Δ

...c/provider-utils/awscloudformation/import/index.ts
4.39% <0.00%> (-0.62%)
:arrow_down:

...udformation/service-walkthroughs/auth-questions.js
2.83% <0.00%> (-0.21%)
:arrow_down:

...dformation/utils/generate-auth-trigger-template.ts
24.48% <0.00%> (-2.79%)
:arrow_down:

...ovider-utils/awscloudformation/utils/cronHelper.ts
19.51% <0.00%> (ø)

...cloudformation/utils/environmentVariablesHelper.ts
48.69% <0.00%> (ø)

...ider-utils/awscloudformation/utils/layerHelpers.ts
21.92% <0.00%> (ø)

...vider-utils/awscloudformation/utils/zipResource.ts
16.66% <ø> (ø)

packages/amplify-cli/src/amplify-service-helper.ts
26.92% <ø> (ø)

packages/amplify-cli/src/commands/status.ts
94.73% <ø> (ø)

packages/amplify-cli/src/context-manager.ts
76.66% <ø> (ø)

... and 507 more

Continue to review full report at Codecov.

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


Update sbt-coveralls to 1.3.2

Updates org.scoverage:sbt-coveralls from 1.3.1 to 1.3.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scoverage", artifactId = "sbt-coveralls" } ]

labels: sbt-plugin-update, early-semver-patch, semver-spec-patch, commit-count:1

Coverage decreased (-2.8%) to 91.975% when pulling 6bfa4194f83ded9207383156dda1983939290087 on scala-steward:update/sbt-coveralls-1.3.2 into 376b2b0cadf9a39aca67ca4c73368f461153b79a on iheartradio:master.

Superseded by #242.


Minor changes

I added some minor changes based on the experience we collected in course of troubleshooting customer issues.

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

@kenwith - Hi, would you review the proposed update to your article?
Publishing in this repository is suspended until Tuesday, September 22; merging will resume at 7 AM Pacific Tuesday. If you sign off in the PR, we'll merge the PR at that time.
Thanks.

#sign-off

This PR is ready to merge on 9/22.

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


Add optional Custom Url Target

Description
Use case: Being able to set a custom target has helped us address a request raised by a client, who wanted to know if it was possible to return to the same tab every time they selected a particular action; however still have both the admin panel & tab in question open.
We noticed that WordPress uses a target="wp-post-1234" format to achieve this. This gives flexibility for other use cases too.
I have added a section in the Actions docs to help document this addition.
Huge thanks to @chrispage1 for the support & help on this!
Visual changes
No visual changes.
Functional changes

[x] Code style has been fixed by running the composer cs command.
[x] Changes have been tested to not break existing functionality.
[x] Documentation is up-to-date.

Thanks, but it feels weird having this next to the boolean _blank option in v3, feels cluttered. Please reopen this to the v4 branch, and refactor to fit better with the existing _blank option. The existing setter can be an alias for urlTarget('_blank'). The generate_href_html() helper can have the argument changed.


Allvideouser doesnt work

Hi , great script , but allvideouser.js just doesnt work. there no output

js selector updated now it works


'Bad certificate' after stopping and starting vmwarefusion machine

VMWare Fusion machines seem not to be functional after stopping and re-starting them.
As of commit 7d6fd1f (midday January 28, 2015) with Docker 1.4.1 and a fresh boot2docker.iso, if I do the following:
docker-machine create -d vmwarefusion foo
docker $(docker-machine config foo) ps     # SUCCESS
docker-machine stop
docker-machine start
docker $(docker-machine config foo) ps     # FAILURE
the second attempt to do 'docker ps' fails with FATA[0000] An error occurred trying to connect: Get https://<IP_ADDRESS>:2376/v1.16/containers/json: remote error: bad certificate. Same is true if I replace the stop/start with restart. 'docker-machine ssh' also fails in that I end up being prompted to authenticate via password.
This does not happen for VirtualBox machines. I haven't had trouble stopping/starting them.
If I 'docker-machine rm foo' and start over, I get the same behavior (works fine until I stop the machine).
This isn't too terrible, but it is a hassle in that any of the cached Docker image files must be re-fetched.

This is a known issue.  Support for detecting the virtual disk in order to store the b2d configs needs to be added.

I'm putting together a workaround for this short term as the long term solution will take some time to develop.

@frapposelli awesome!! thanks!

I have the same/similar problem with virtualbox.  Start/stop an engine ends up with this error when I try to connect to it again:
FATA[0000] An error occurred trying to connect: Get https://<IP_ADDRESS>:2376/v1.16/containers/json: x509: certificate is valid for <IP_ADDRESS>, not <IP_ADDRESS>

Yes we are working on this.  There should be a workaround soon.
On Wed, Feb 4, 2015 at 3:30 PM, ryanwalls<EMAIL_ADDRESS>wrote:

I have the same/similar problem with virtualbox. Start/stop an engine ends
up with this error when I try to connect to it again:
FATA[0000] An error occurred trying to connect: Get https://<IP_ADDRESS>:2376/v1.16/containers/json: x509: certificate is valid for <IP_ADDRESS>, not <IP_ADDRESS>
—
Reply to this email directly or view it on GitHub
https://github.com/docker/machine/issues/430#issuecomment-72932662.

@ehazlett Thanks!

yw -- i will post here once it's available.
On Wed, Feb 4, 2015 at 4:34 PM, ryanwalls<EMAIL_ADDRESS>wrote:

@ehazlett https://github.com/ehazlett Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/docker/machine/issues/430#issuecomment-72944217.

@ehazlett What's weird is if I start a new terminal and run docker $(docker-machine config dev) ps I can connect.
If I run $(docker-machine env dev), then docker ps it fails with the cert error.

As a reference, this issue depends on boot2docker/boot2docker#747

@frapposelli Were you able to come up with a short term solution or does the short term solution also depend on boot2docker/boot2docker#747?

This PR adds shared folders support for Fusion and should fix this issue https://github.com/docker/machine/pull/1034


Update ICMP Spec with additions from RFC 1122/950

RFC 950

adds a new Message Type: Address Mask Request/Reply with Code 17,18 (p. 10)
Wikipedia

RFC 1122
Defines additional codes for:

ICMP Destination Unreachable (p. 39)

The following additional codes [for Destination Unreachable] are hereby defined:
   6 = destination network unknown
   7 = destination host unknown
   8 = source host isolated
   9 = communication with destination network administratively prohibited
   10 = communication with destination host administratively prohibited
   11 = network unreachable for type of service
   12 = host unreachable for type of service

ICMP Parameter Problem (p. 42)

A new variant on the Parameter Problem message is hereby defined:
   Code 1 = required option is missing.

This is a new feature which should not delay 0.4.1 further.

Moved to Componolit/RecordFlux-specifications#1.


Hierarchies list question/bug - edition mode - left filter

Describe the bug
I am working on a new hierarchy and see odd things in the display.
As this hierarchy is generated by a script, I am trying here to understand if:

my generated hierarchy has problems (RDF)
I do not fully understand how Visualize is using the hierarchy
There is a display bug in Visualize

Cube: "fab Foreign Trade test 2"
Environment TEST
In visualize, here
Here is an example: the node "WK '1' ROUND WOOD (WOOD IN THE ROUGH)" has a child "List of Zolltarifs", which has 43 children.
But the filter on the left "Tariff or Basket ID" displays only 4 children:

The filter on the right, when choosing a color, does display all children:

Those 43 children are visible when displaying the hierarchy in the Cube Creator. I suppose that the RDF is thus correct.
I see "missing" nodes in different parts of the hierarchy, I could give more examples if needed.

@ptbrowne salut Patrick, aurais-tu quelques infos à ce sujet ? Est-ce une incompréhension de ma part, une erreur dans les données, un bug de Visualize ? Merci d'avance

Hi @FabianCretton , I'll have a look tomorrow, it seems we are effectively not returning all the nodes but I do not know exactly why and right now I get 503 from test.lindas.admin.ch.

Technical details
query DimensionHierarchy($sourceType: String!, $sourceUrl: String!, $locale: String!, $cubeIri: String!, $dimensionIri: String!) {
dataCubeByIri(
  iri: $cubeIri
  sourceType: $sourceType
  sourceUrl: $sourceUrl
  locale: $locale
) {
  dimensionByIri(
    iri: $dimensionIri
    sourceType: $sourceType
    sourceUrl: $sourceUrl
  ) {
    ...hierarchyMetadata
    __typename
  }
  __typename
}
}

fragment hierarchyMetadata on Dimension {
hierarchy(sourceType: $sourceType, sourceUrl: $sourceUrl) {
  ...hierarchyValueFields
  children {
    ...hierarchyValueFields
    children {
      ...hierarchyValueFields
      children {
        ...hierarchyValueFields
        __typename
      }
      __typename
    }
    __typename
  }
  __typename
}
}

fragment hierarchyValueFields on HierarchyValue {
value
dimensionIri
depth
label
hasValue
}

Variables
{
  "cubeIri": "https://environment.ld.admin.ch/foen/fab_foreign_trade_test_2/4",
  "dimensionIri": "https://environment.ld.admin.ch/foen/fab_foreign_trade_test_2/tnorwarenkoerbeid",
  "sourceType": "sparql",
  "sourceUrl": "https://test.lindas.admin.ch/query",
  "locale": "en"
}

This hierarchy seems a bit strange in the sense that there are children that are reached through multiple chains of parents. It would mean that in the left panel select, an option could appear multiple times. Is this wanted @FabianCretton , can you explain a bit more what is this data ?
Attached is a rendition of the hierarchy, where we see that some children on the right have multiple incoming arrows = multiple parents. This is a usecase that was not foreseen, it could be changed on visualize quite easily, but I just want to make sure that this is normal.

Thank you for the information Patrick.
And yes, it is currently on purpose that a resource could have different parents.
Those leaf "resources" are tarifs.
The first case is that we have different baskets, and one tarif can be found in more than one basket.
The other case is that the baskets are in a hierarchy, and if a tarif is in a basket of 'level 2', then we also want to show that it is in the parent basket of level 1.
This was my way to do it, but we can discuss about it of course, if it doesn't make sense.

It seems to me that the 1st case is OK, while the second case is more problematic as the total of the children would be over 100% right ?
Example:
A
  B
  C
     D
  D

B + C + D > 100% and I think it could be problematic. I think here, it should be handled through another mean that the parent relationship, since this is wanted only for "viewing".
@l00mi What's your thoughts on this ?

Yes, I think you are right, currently it is more for viewing what is inside a basket at a specific level.
But the total value, calculated to create the input CSV, is correct at each level (I think that Visualize still do not calculate agregate and they must be provided in the dataset, right @ptbrowne ?)
A special case here is that we talk about tarifs (the real values), which are grouped in baskets.
The baskets do have a hierarchy.
But then, a basket can contain other baskets, but also directly a tarif that is not in a sub-basket.
For instance:

basket 1 is the parent of basket 1.1 and basket 1.2
basket 1.1 contains tarif A
basket 1.2 contains tarif B
basket 1 contains tarif A (from 1.1), tarif B (from 1.2) and tarif C (directly here)
Is that ok ?
We might want to involve Achim Schafer in this discussion.


Can't connect through POP3

I can't seem to connect through pop3, both with or without SSL.
Context

I can connect through SMTP with SSL, but I can't connect through POP3 at all. With or without SSL, on port 110 or 995. I have opened up both ports in my docker-compose file and also added ENABLE_POP3=1 to it. I
I get my SSL certificates through Let's Encrypt. It's also setup for mail.mydomain.com.
When I'm trying to connect the logs show the following error:
Mar 11 19:16:08 mail dovecot: pop3-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, TLS: Disconnected, session=<AkHN2yd45sgKfVIL>

Edit: Gmail (web) returns the following error when trying to connect: SSL error: unknown CA (alert 48).
I ran:
docker exec mail openssl s_client -connect <IP_ADDRESS>:25 -starttls imap -CApath /etc/ssl/certs/

It returns Verify return code: 0 (ok), but it fails on port 143, and all other ports from what I can see.
Possible Fix

I noticed dovecot is looking for its certificates at /etc/dovecot/ssl/dovecot.pem. Is that based on my Let's Encrypt certificates? Is there any way to check if they are legit?
I've read people with this error didn't had their SSL certificates in order.
Your Environment

Amount of RAM available: N/A
Mailserver version used: latest stable
Docker version used: 17.09.0-ce
Environment settings relevant to the config:
ENABLE_POP3=1
SSL_TYPE=letsencrypt
Any relevant stack traces ("Full trace" preferred): N/A

How did you setup SSL in your docker_compose?

I'm using the letsencrypt container from linuxserver. The letsencrypt folder is mounted to /etc/letsencrypt. Below is the docker-compose file. It is seperated from the mailserver docker-compose file since I followed the readme instructions, but I'm intending to merge them when the mailserver works.
  letsencrypt:
    image: linuxserver/letsencrypt
    container_name: letsencrypt
    cap_add:
      - NET_ADMIN
    ports:
      - "80:80"
      - "443:443"
    environment:
      - PUID=1000
      - PGID=1000
      -<EMAIL_ADDRESS>      - URL=something.com
      - SUBDOMAINS=plex,sonarr,radarr,mail
      - VALIDATION=http
      - TZ=Europe/Paris
    volumes:
      - /home/ubuntu/web:/config

I noticed you wrote that dovecot is looking for the certificate at etc/dovecot/ssl/dovecot.pem and that means either you did not set ssl type to letsencrypt or the certification files are not available.
Could you run the following and post the output:
docker exec mail ls /etc/letsencrypt/live/$HOSTNAME/

docker exec mail cat /etc/dovecot/conf.d/10-ssl.conf

With $HOSTNAME replaced with your actual hostname

I initially forgot to mount the letsencrypt folder, but fixed it soon after. Perhaps that has something to do with it?
The files seem to be there now:
ubuntu@host:~/apps/mail$ sudo docker exec mail ls /etc/letsencrypt/live/hostname/
README
cert.pem
chain.pem
fullchain.pem
privkey.pem
privkey.pfx

ubuntu@host:~/apps/mail$ sudo docker exec mail cat /etc/dovecot/conf.d/10-ssl.conf
##
## SSL settings
##

# SSL/TLS support: yes, no, required. <doc/wiki/SSL.txt>
ssl = required

# PEM encoded X.509 SSL/TLS certificate and private key. They're opened before
# dropping root privileges, so keep the key file unreadable by anyone but
# root. Included doc/mkcert.sh can be used to easily generate self-signed
# certificate, just make sure to update the domains in dovecot-openssl.cnf
ssl_cert = </etc/dovecot/ssl/dovecot.pem
ssl_key = </etc/dovecot/ssl/dovecot.key

# If key file is password protected, give the password here. Alternatively
# give it when starting dovecot with -p parameter. Since this file is often
# world-readable, you may want to place this setting instead to a different
# root owned 0600 file by using ssl_key_password = <path.
#ssl_key_password =

# PEM encoded trusted certificate authority. Set this only if you intend to use
# ssl_verify_client_cert=yes. The file should contain the CA certificate(s)
# followed by the matching CRL(s). (e.g. ssl_ca = </etc/ssl/certs/ca.pem)
#ssl_ca =

# Require that CRL check succeeds for client certificates.
#ssl_require_crl = yes

# Directory and/or file for trusted SSL CA certificates. These are used only
# when Dovecot needs to act as an SSL client (e.g. imapc backend). The
# directory is usually /etc/ssl/certs in Debian-based systems and the file is
# /etc/pki/tls/cert.pem in RedHat-based systems.
#ssl_client_ca_dir =
#ssl_client_ca_file =

# Request client to send a certificate. If you also want to require it, set
# auth_ssl_require_client_cert=yes in auth section.
#ssl_verify_client_cert = no

# Which field from certificate to use for username. commonName and
# x500UniqueIdentifier are the usual choices. You'll also need to set
# auth_ssl_username_from_cert=yes.
#ssl_cert_username_field = commonName

# DH parameters length to use.
ssl_dh_parameters_length = 2048

# SSL protocols to use
ssl_protocols = !SSLv3,!TLSv1,!TLSv1.1

# SSL ciphers to use
ssl_cipher_list = ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256

# Prefer the server's order of ciphers over client's.
ssl_prefer_server_ciphers = yes

# SSL crypto device to use, for valid values run "openssl engine"
#ssl_crypto_device =

Please rebuild the container with
docker-compose down && docker-compose up -d --build

So that the startup script change the path to letsencrypt certificates.
Then you should be able to connect to your server :)

Did that, still a no go. :(
10-ssl.conf still contains:
ssl_cert = </etc/dovecot/ssl/dovecot.pem
ssl_key = </etc/dovecot/ssl/dovecot.key

That's strange.
Could you provide your startup log?

Sure, here it is. I masked my domain for privacy purposes.
mail    | 2018-03-12 20:05:37,425 CRIT Supervisor running as root (no user in config file)
mail    | 2018-03-12 20:05:37,425 INFO Included extra file "/etc/supervisor/conf.d/saslauth.conf" during parsing
mail    | 2018-03-12 20:05:37,425 INFO Included extra file "/etc/supervisor/conf.d/supervisor-app.conf" during parsing
mail    | 2018-03-12 20:05:37,471 INFO RPC interface 'supervisor' initialized
mail    | 2018-03-12 20:05:37,471 CRIT Server 'unix_http_server' running without any HTTP authentication checking
mail    | 2018-03-12 20:05:37,472 INFO supervisord started with pid 7
mail    | 2018-03-12 20:05:38,475 INFO spawned: 'postsrsd' with pid 10
mail    | 2018-03-12 20:05:38,476 INFO spawned: 'mailserver' with pid 11
mail    |
mail    | 2018-03-12 20:05:38,527 INFO success: postsrsd entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | 2018-03-12 20:05:38,527 INFO success: mailserver entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | #
mail    | #
mail    | # docker-mailserver
mail    | #
mail    | #
mail    |
mail    | Initializing setup
mail    | Checking configuration
mail    | Configuring mail server
mail    | 2018-03-12 20:05:38,835 INFO exited: postsrsd (exit status 0; expected)
mail    |   * Spamassassin is disabled. You can enable it with 'ENABLE_SPAMASSASSIN=1'
mail    |   * Clamav is disabled. You can enable it with 'ENABLE_CLAMAV=1'
mail    | Starting Misc
mail    | Starting mail server
mail    | 2018-03-12 20:05:42,083 INFO spawned: 'cron' with pid 106
mail    | 2018-03-12 20:05:42,083 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | cron: started
mail    | 2018-03-12 20:05:42,299 INFO spawned: 'rsyslog' with pid 108
mail    | 2018-03-12 20:05:42,299 INFO success: rsyslog entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | rsyslog: started
mail    | 2018-03-12 20:05:42,494 INFO spawned: 'dovecot' with pid 113
mail    | 2018-03-12 20:05:42,495 INFO success: dovecot entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | dovecot: started
mail    | 2018-03-12 20:05:42,703 INFO spawned: 'opendkim' with pid 120
mail    | 2018-03-12 20:05:42,704 INFO success: opendkim entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | opendkim: started
mail    | 2018-03-12 20:05:42,877 INFO spawned: 'opendmarc' with pid 124
mail    | 2018-03-12 20:05:42,877 INFO success: opendmarc entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | opendmarc: started
mail    | 2018-03-12 20:05:43,044 INFO spawned: 'postfix' with pid 137
mail    | 2018-03-12 20:05:43,044 INFO success: postfix entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | postfix: started
mail    | 2018-03-12 20:05:43,218 INFO spawned: 'fail2ban' with pid 166
mail    | 2018-03-12 20:05:43,220 INFO success: fail2ban entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | fail2ban: started
mail    | 2018-03-12 20:05:43,399 INFO spawned: 'changedetector' with pid 170
mail    | 2018-03-12 20:05:43,399 INFO success: changedetector entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | changedetector: started
mail    | 2018-03-12 20:05:43,594 INFO spawned: 'amavis' with pid 232
mail    | 2018-03-12 20:05:43,595 INFO success: amavis entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | amavis: started
mail    |
mail    | #
mail    | # mail.domain.com is up and running
mail    | #
mail    |
mail    | Mar 12 20:05:45 mail postfix/master[972]: daemon started -- version 3.1.8, configuration /etc/postfix
mail    | Mar 12 20:05:45 mail amavis[232]: starting. /usr/sbin/amavisd-new at mail.domain.com amavisd-new-2.10.1 (20141025), Unicode aware
mail    | Mar 12 20:05:45 mail amavis[232]: Net::Server: Group Not Defined.  Defaulting to EGID '111 111'
mail    | Mar 12 20:05:45 mail amavis[232]: Net::Server: User Not Defined.  Defaulting to EUID '109'
mail    | Mar 12 20:05:45 mail amavis[232]: Module Amavis::Conf        2.404
mail    | Mar 12 20:05:45 mail amavis[232]: Module Archive::Zip        1.59
mail    | Mar 12 20:05:45 mail amavis[232]: Module BerkeleyDB          0.55
mail    | Mar 12 20:05:45 mail amavis[232]: Module Compress::Raw::Zlib 2.069
mail    | Mar 12 20:05:45 mail amavis[232]: Module Compress::Zlib      2.069001
mail    | Mar 12 20:05:45 mail amavis[232]: Module Digest::MD5         2.54
mail    | Mar 12 20:05:45 mail amavis[232]: Module Encode              2.80_01
mail    | Mar 12 20:05:45 mail amavis[232]: Module File::Temp          0.2304
mail    | Mar 12 20:05:45 mail amavis[232]: Module IO::Socket::IP      0.37
mail    | Mar 12 20:05:45 mail amavis[232]: Module MIME::Entity        5.508
mail    | Mar 12 20:05:45 mail amavis[232]: Module MIME::Parser        5.508
mail    | Mar 12 20:05:45 mail amavis[232]: Module MIME::Tools         5.508
mail    | Mar 12 20:05:45 mail amavis[232]: Module Mail::Header        2.18
mail    | Mar 12 20:05:45 mail amavis[232]: Module Mail::Internet      2.18
mail    | Mar 12 20:05:45 mail amavis[232]: Module Net::LibIDN         0.12
mail    | Mar 12 20:05:45 mail amavis[232]: Module Net::Server         2.008
mail    | Mar 12 20:05:45 mail amavis[232]: Module Scalar::Util        1.4202
mail    | Mar 12 20:05:45 mail amavis[232]: Module Socket              2.020_03
mail    | Mar 12 20:05:45 mail amavis[232]: Module Time::HiRes         1.9733
mail    | Mar 12 20:05:45 mail amavis[232]: Module Unix::Syslog        1.1
mail    | Mar 12 20:05:45 mail amavis[232]: Amavis::ZMQ code     NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: Amavis::DB code      loaded
mail    | Mar 12 20:05:45 mail amavis[232]: SQL base code        NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: SQL::Log code        NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: SQL::Quarantine      NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: Lookup::SQL code     NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: Lookup::LDAP code    NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: AM.PDP-in proto code loaded
mail    | Mar 12 20:05:45 mail amavis[232]: SMTP-in proto code   loaded
mail    | Mar 12 20:05:45 mail amavis[232]: Courier proto code   NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: SMTP-out proto code  loaded
mail    | Mar 12 20:05:45 mail amavis[232]: Pipe-out proto code  NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: BSMTP-out proto code NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: Local-out proto code loaded
mail    | Mar 12 20:05:45 mail amavis[232]: OS_Fingerprint code  NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: ANTI-VIRUS code      NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: ANTI-SPAM code       NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: ANTI-SPAM-EXT code   NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: ANTI-SPAM-C code     NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: ANTI-SPAM-SA code    NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: Unpackers code       loaded
mail    | Mar 12 20:05:45 mail amavis[232]: DKIM code            NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: Tools code           NOT loaded
mail    | Mar 12 20:05:45 mail amavis[232]: Found $file            at /usr/bin/file
mail    | Mar 12 20:05:45 mail amavis[232]: No $altermime,         not using it
mail    | Mar 12 20:05:45 mail amavis[232]: Internal decoder for .mail
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .Z    at /bin/uncompress
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .gz   at /bin/gzip -d
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .bz2  at /bin/bzip2 -d
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .xz   at /usr/bin/xz -dc
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .lzma at /usr/bin/xz -dc --format=lzma
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .lrz  at /usr/bin/lrzip -q -k -d -o -
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .lzo  at /usr/bin/lzop -d
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .lz4  at /usr/bin/lz4c -d
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .rpm  at /usr/bin/rpm2cpio
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .cpio at /bin/pax
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .tar  at /bin/pax
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .deb  at /usr/bin/ar
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .rar  at /usr/bin/unrar-free
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .arj  at /usr/bin/arj
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .arc  at /usr/bin/nomarch
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .zoo  at /usr/bin/zoo
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .doc  at /usr/bin/ripole
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .cab  at /usr/bin/cabextract
mail    | Mar 12 20:05:45 mail amavis[232]: Internal decoder for .tnef
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .zip  at /usr/bin/7za
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .kmz  at /usr/bin/7za
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .7z   at /usr/bin/7zr
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .jar  at /usr/bin/7z
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .swf  at /usr/bin/7z
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .lha  at /usr/bin/7z
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .iso  at /usr/bin/7z
mail    | Mar 12 20:05:45 mail amavis[232]: Found decoder for    .exe  at /usr/bin/unrar-free; /usr/bin/arj
mail    | Mar 12 20:05:45 mail amavis[232]: No decoder for       .F
mail    | Mar 12 20:05:45 mail amavis[232]: Deleting db files  in /var/lib/amavis/db
mail    | Mar 12 20:05:45 mail amavis[232]: Creating db in /var/lib/amavis/db/; BerkeleyDB 0.55, libdb 5.3
mail    | Mar 12 20:06:01 mail dovecot: ssl-params: SSL parameters regeneration completed

Ah, forgot to mention: Could you enable DMS_DEBUG with adding DMS_DEBUG=1 to your docker-compose and then rebuild the container?

Ah right. Here it is:
ubuntu@host:~/apps/mail$ sudo docker-compose down && sudo docker-compose up -d --build
Stopping mail ... done
Removing mail ... done
Removing network mail_default
Creating network "mail_default" with the default driver
Creating mail ...
Creating mail ... done
ubuntu@host:~/apps/mail$ sudo docker-compose logs -f mail
Attaching to mail
mail    | 2018-03-12 23:19:14,575 CRIT Supervisor running as root (no user in config file)
mail    | 2018-03-12 23:19:14,575 INFO Included extra file "/etc/supervisor/conf.d/saslauth.conf" during parsing
mail    | 2018-03-12 23:19:14,575 INFO Included extra file "/etc/supervisor/conf.d/supervisor-app.conf" during parsing
mail    | 2018-03-12 23:19:14,592 INFO RPC interface 'supervisor' initialized
mail    | 2018-03-12 23:19:14,592 CRIT Server 'unix_http_server' running without any HTTP authentication checking
mail    | 2018-03-12 23:19:14,592 INFO supervisord started with pid 7
mail    | 2018-03-12 23:19:15,595 INFO spawned: 'postsrsd' with pid 10
mail    | 2018-03-12 23:19:15,597 INFO spawned: 'mailserver' with pid 11
mail    |
mail    | #
mail    | 2018-03-12 23:19:15,645 INFO success: postsrsd entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | 2018-03-12 23:19:15,645 INFO success: mailserver entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | #
mail    | # ENV
mail    | #
mail    | #
mail    |
mail    | SASLAUTHD_LDAP_FILTER=
mail    | FETCHMAIL_POLL=300
mail    | POSTGREY_DELAY=300
mail    | SASLAUTHD_LDAP_SEARCH_BASE=
mail    | SASLAUTHD_MECHANISMS=
mail    | SA_SPAM_SUBJECT=***SPAM*****
mail    | SPOOF_PROTECTION=0
mail    | LDAP_BIND_PW=
mail    | HOSTNAME=mail.domain.com
mail    | ENABLE_LDAP=0
mail    | OVERRIDE_HOSTNAME=
mail    | SASLAUTHD_LDAP_PASSWORD=
mail    | LDAP_SERVER_HOST=
mail    |<EMAIL_ADDRESS>mail    | LDAP_SEARCH_BASE=
mail    | LDAP_BIND_DN=
mail    | PUID=1000
mail    | ENABLE_POSTFIX_VIRTUAL_TRANSPORT=
mail    | TLS_LEVEL=modern
mail    | SA_TAG=2.0
mail    | ENABLE_MANAGESIEVE=0
mail    | SMTP_ONLY=0
mail    | PERMIT_DOCKER=network
mail    | SA_TAG2=6.31
mail    | PGID=1000
mail    | PWD=/
mail    | POSTFIX_DAGENT=
mail    | LDAP_QUERY_FILTER_USER=
mail    | DOVECOT_TLS=
mail    | HOME=/root
mail    | SA_KILL=6.31
mail    | DEBIAN_FRONTEND=noninteractive
mail    | DMS_DEBUG=1
mail    | ENABLE_FAIL2BAN=1
mail    | SSL_TYPE=letsencrypt
mail    | SUPERVISOR_PROCESS_NAME=mailserver
mail    | POSTSCREEN_ACTION=enforce
mail    | SUPERVISOR_ENABLED=1
mail    | LDAP_QUERY_FILTER_ALIAS=
mail    | SASLAUTHD_LDAP_SERVER=
mail    | SASL_PASSWD=
mail    | SASLAUTHD_LDAP_BIND_DN=
mail    | ENABLE_SPAMASSASSIN=0
mail    | ENABLE_POSTGREY=0
mail    | ENABLE_FETCHMAIL=0
mail    | VIRUSMAILS_DELETE_DELAY=
mail    | SASLAUTHD_MECH_OPTIONS=
mail    | SHLVL=1
mail    | ENABLE_SASLAUTHD=0
mail    | SUPERVISOR_GROUP_NAME=mailserver
mail    | DOVECOT_USER_FILTER=
mail    | ENABLE_CLAMAV=0
mail    | SASLAUTHD_LDAP_SSL=
mail    | PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
mail    | DOVECOT_PASS_FILTER=
mail    | POSTGREY_TEXT=Delayed by postgrey
mail    | ONE_DIR=0
mail    | SUPERVISOR_SERVER_URL=unix:///dev/shm/supervisor.sock
mail    | POSTGREY_MAX_AGE=35
mail    | ENABLE_POP3=1
mail    | LDAP_QUERY_FILTER_GROUP=
mail    | LDAP_START_TLS=
mail    | _=/usr/bin/printenv
mail    |
mail    | #
mail    | #
mail    | # docker-mailserver
mail    | #
mail    | #
mail    |
mail    | Initializing setup
mail    |   Registering check,setup,fix,misc and start-daemons functions
mail    |   * _check_environment_variables() registered
mail    |   * _check_hostname() registered
mail    |   * _setup_default_vars() registered
mail    |   * _setup_dovecot() registered
mail    |   * _setup_dovecot_local_user() registered
mail    |   * _setup_dkim() registered
mail    |   * _setup_ssl() registered
mail    |   * _setup_docker_permit() registered
mail    |   * _setup_mailname() registered
mail    |   * _setup_amavis() registered
mail    |   * _setup_dmarc_hostname() registered
mail    |   * _setup_postfix_hostname() registered
mail    |   * _setup_dovecot_hostname() registered
mail    |   * _setup_postfix_sasl() registered
mail    |   * _setup_postfix_override_configuration() registered
mail    |   * _setup_postfix_sasl_password() registered
mail    |   * _setup_security_stack() registered
mail    |   * _setup_postfix_aliases() registered
mail    |   * _setup_postfix_vhost() registered
mail    |   * _setup_postfix_dhparam() registered
mail    |   * _setup_postfix_postscreen() registered
mail    |   * _setup_postfix_access_control() registered
mail    |   * _setup_environment() registered
mail    |   * _fix_var_mail_permissions() registered
mail    |   * _fix_var_amavis_permissions() registered
mail    |   * _fix_cleanup_clamav() registered
mail    |   * _misc_save_states() registered
mail    |   * _start_daemons_cron() registered
mail    |   * _start_daemons_rsyslog() registered
mail    |   * _start_daemons_dovecot() registered
mail    |   * _start_daemons_opendkim() registered
mail    |   * _start_daemons_opendmarc() registered
mail    |   * _start_daemons_postfix() registered
mail    |   * _start_daemons_fail2ban() registered
mail    |   * _start_changedetector() registered
mail    |   * _start_daemons_amavis() registered
mail    | Checking configuration
mail    |   Check that there are no conflicts with env variables [_check_environment_variables]
mail    |   Check that hostname/domainname is provided or overidden (no default docker hostname/kubernetes) [_check_hostname]
mail    |   * Domain has been set to domain.com
mail    |   * Hostname has been set to mail.domain.com
mail    | Configuring mail server
mail    |   Setting up default variables [_setup_default_vars]
mail    |   * Set ENABLE_LDAP=0
mail    |   * Set OVERRIDE_HOSTNAME=
mail    |   * Set DMS_DEBUG=1
mail    |   * Set ENABLE_CLAMAV=0
mail    |   * Set ENABLE_FAIL2BAN=1
mail    |   * Set FETCHMAIL_POLL=300
mail    |   * Set TLS_LEVEL=modern
mail    |   * Set ENABLE_SPAMASSASSIN=0
mail    |   * Set POSTGREY_DELAY=300
mail    |   * Set POSTGREY_TEXT=Delayed by postgrey
mail    |   * Set ENABLE_POSTGREY=0
mail    |   * Set POSTGREY_MAX_AGE=35
mail    |   * Set<EMAIL_ADDRESS>mail    |   * Set ENABLE_FETCHMAIL=0
mail    |   * Set ENABLE_MANAGESIEVE=0
mail    |   * Set POSTSCREEN_ACTION=enforce
mail    |   * Set ENABLE_POP3=1
mail    |   * Set ENABLE_SASLAUTHD=0
mail    |   * Set SMTP_ONLY=0
mail    |   * Set SPOOF_PROTECTION=0
mail    |   Setting up Dovecot
mail    | 2018-03-12 23:19:15,757 INFO exited: postsrsd (exit status 0; expected)
mail    |   Setting up Dovecot Local User
mail    |   * Checking file line endings
mail    |   * Regenerating postfix user list
mail    |   * user 'requests' for domain 'domain.com' with password '********'
mail    |   Setting up DKIM
mail    |   * DKIM keys added for: domain.com
mail    |   * Changing permissions on /etc/opendkim
mail    |   Setting up SSL
mail    |   * TLS configured with 'modern' ciphers
mail    |   Setting up PERMIT_DOCKER Option
mail    |   * Adding docker network in my networks
mail    |   Setting up Mailname
mail    |   * Creating /etc/mailname
mail    |   Setting up Amavis
mail    |   * Applying hostname to /etc/amavis/conf.d/05-node_id
mail    |   Setting up dmarc
mail    |   * Applying hostname to /etc/opendmarc.conf
mail    |   Applying hostname and domainname to Postfix
mail    |   * Applying hostname to /etc/postfix/main.cf
mail    |   Applying hostname to Dovecot
mail    |   * Applying hostname to /etc/dovecot/conf.d/15-lda.conf
mail    |   Setting up Postfix Override configuration
mail    |   * No extra postfix settings loaded because optional '/tmp/docker-mailserver/postfix-main.cf' not provided.
mail    |   * No extra postfix settings loaded because optional '/tmp/docker-mailserver/postfix-master.cf' not provided.
mail    |   * set the compatibility level to 2
mail    |   Setting up Postfix SASL Password
mail    |   * Warning: 'SASL_PASSWD' is not provided. /etc/postfix/sasl_passwd not created.
mail    |   Setting up Security Stack
mail    |   * Spamassassin is disabled. You can enable it with 'ENABLE_SPAMASSASSIN=1'
mail    |   * Clamav is disabled. You can enable it with 'ENABLE_CLAMAV=1'
mail    |   * Fail2ban enabled
mail    |   Setting up Postfix Aliases
mail    |   * Warning 'config/postfix-virtual.cf' is not provided. No mail alias/forward created.
mail    |   Setting up Postfix vhost
mail    |   Setting up Postfix dhparam
mail    |   * No state dir, we use the dhparams generated on image creation
mail    |   * Configuring postscreen
mail    |   * Configuring user access
mail    |   Setting up /etc/environment
mail    |   Checking /var/mail permissions
mail    |   * Fixing /var/mail permissions
mail    |   Checking $amavis_state_dir permissions
mail    |   * Permissions in /var/lib/amavis look OK
mail    |   Cleaning up disabled Clamav
mail    | Starting Misc
mail    | Starting mail server
mail    |   Starting cron2018-03-12 23:19:19,168 INFO spawned: 'cron' with pid 107
mail    | 2018-03-12 23:19:19,168 INFO success: cron entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | cron: started
mail    |   Starting rsyslog 2018-03-12 23:19:19,383 INFO spawned: 'rsyslog' with pid 109
mail    | 2018-03-12 23:19:19,383 INFO success: rsyslog entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | rsyslog: started
mail    |   Starting dovecot services  Starting pop3 services2018-03-12 23:19:19,592 INFO spawned: 'dovecot' with pid 114
mail    | 2018-03-12 23:19:19,592 INFO success: dovecot entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | dovecot: started
mail    |   Starting opendkim 2018-03-12 23:19:19,818 INFO spawned: 'opendkim' with pid 123
mail    | 2018-03-12 23:19:19,818 INFO success: opendkim entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | opendkim: started
mail    |   Starting opendmarc 2018-03-12 23:19:19,985 INFO spawned: 'opendmarc' with pid 125
mail    | 2018-03-12 23:19:19,985 INFO success: opendmarc entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | opendmarc: started
mail    |   Starting postfix2018-03-12 23:19:20,153 INFO spawned: 'postfix' with pid 138
mail    | 2018-03-12 23:19:20,154 INFO success: postfix entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | postfix: started
mail    |   Starting fail2ban 2018-03-12 23:19:20,324 INFO spawned: 'fail2ban' with pid 167
mail    | 2018-03-12 23:19:20,324 INFO success: fail2ban entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | fail2ban: started
mail    |   Starting changedetector2018-03-12 23:19:20,493 INFO spawned: 'changedetector' with pid 170
mail    | 2018-03-12 23:19:20,493 INFO success: changedetector entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | changedetector: started
mail    |   Starting amavis2018-03-12 23:19:20,673 INFO spawned: 'amavis' with pid 199
mail    | 2018-03-12 23:19:20,673 INFO success: amavis entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
mail    | amavis: started
mail    |
mail    | #
mail    | # mail.domain.com is up and running
mail    | #
mail    |
mail    | Mar 12 23:19:21 mail amavis[199]: starting. /usr/sbin/amavisd-new at mail.domain.com amavisd-new-2.10.1 (20141025), Unicode aware
mail    | Mar 12 23:19:21 mail postfix/master[973]: daemon started -- version 3.1.8, configuration /etc/postfix
mail    | Mar 12 23:19:21 mail amavis[199]: Net::Server: Group Not Defined.  Defaulting to EGID '111 111'
mail    | Mar 12 23:19:21 mail amavis[199]: Net::Server: User Not Defined.  Defaulting to EUID '109'
mail    | Mar 12 23:19:21 mail amavis[199]: Module Amavis::Conf        2.404
mail    | Mar 12 23:19:21 mail amavis[199]: Module Archive::Zip        1.59
mail    | Mar 12 23:19:21 mail amavis[199]: Module BerkeleyDB          0.55
mail    | Mar 12 23:19:21 mail amavis[199]: Module Compress::Raw::Zlib 2.069
mail    | Mar 12 23:19:21 mail amavis[199]: Module Compress::Zlib      2.069001
mail    | Mar 12 23:19:21 mail amavis[199]: Module Digest::MD5         2.54
mail    | Mar 12 23:19:21 mail amavis[199]: Module Encode              2.80_01
mail    | Mar 12 23:19:21 mail amavis[199]: Module File::Temp          0.2304
mail    | Mar 12 23:19:21 mail amavis[199]: Module IO::Socket::IP      0.37
mail    | Mar 12 23:19:21 mail amavis[199]: Module MIME::Entity        5.508
mail    | Mar 12 23:19:21 mail amavis[199]: Module MIME::Parser        5.508
mail    | Mar 12 23:19:21 mail amavis[199]: Module MIME::Tools         5.508
mail    | Mar 12 23:19:21 mail amavis[199]: Module Mail::Header        2.18
mail    | Mar 12 23:19:21 mail amavis[199]: Module Mail::Internet      2.18
mail    | Mar 12 23:19:21 mail amavis[199]: Module Net::LibIDN         0.12
mail    | Mar 12 23:19:21 mail amavis[199]: Module Net::Server         2.008
mail    | Mar 12 23:19:21 mail amavis[199]: Module Scalar::Util        1.4202
mail    | Mar 12 23:19:21 mail amavis[199]: Module Socket              2.020_03
mail    | Mar 12 23:19:21 mail amavis[199]: Module Time::HiRes         1.9733
mail    | Mar 12 23:19:21 mail amavis[199]: Module Unix::Syslog        1.1
mail    | Mar 12 23:19:21 mail amavis[199]: Amavis::ZMQ code     NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: Amavis::DB code      loaded
mail    | Mar 12 23:19:21 mail amavis[199]: SQL base code        NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: SQL::Log code        NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: SQL::Quarantine      NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: Lookup::SQL code     NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: Lookup::LDAP code    NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: AM.PDP-in proto code loaded
mail    | Mar 12 23:19:21 mail amavis[199]: SMTP-in proto code   loaded
mail    | Mar 12 23:19:21 mail amavis[199]: Courier proto code   NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: SMTP-out proto code  loaded
mail    | Mar 12 23:19:21 mail amavis[199]: Pipe-out proto code  NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: BSMTP-out proto code NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: Local-out proto code loaded
mail    | Mar 12 23:19:21 mail amavis[199]: OS_Fingerprint code  NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: ANTI-VIRUS code      NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: ANTI-SPAM code       NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: ANTI-SPAM-EXT code   NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: ANTI-SPAM-C code     NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: ANTI-SPAM-SA code    NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: Unpackers code       loaded
mail    | Mar 12 23:19:21 mail amavis[199]: DKIM code            NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: Tools code           NOT loaded
mail    | Mar 12 23:19:21 mail amavis[199]: Found $file            at /usr/bin/file
mail    | Mar 12 23:19:21 mail amavis[199]: No $altermime,         not using it
mail    | Mar 12 23:19:21 mail amavis[199]: Internal decoder for .mail
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .Z    at /bin/uncompress
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .gz   at /bin/gzip -d
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .bz2  at /bin/bzip2 -d
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .xz   at /usr/bin/xz -dc
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .lzma at /usr/bin/xz -dc --format=lzma
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .lrz  at /usr/bin/lrzip -q -k -d -o -
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .lzo  at /usr/bin/lzop -d
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .lz4  at /usr/bin/lz4c -d
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .rpm  at /usr/bin/rpm2cpio
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .cpio at /bin/pax
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .tar  at /bin/pax
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .deb  at /usr/bin/ar
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .rar  at /usr/bin/unrar-free
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .arj  at /usr/bin/arj
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .arc  at /usr/bin/nomarch
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .zoo  at /usr/bin/zoo
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .doc  at /usr/bin/ripole
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .cab  at /usr/bin/cabextract
mail    | Mar 12 23:19:21 mail amavis[199]: Internal decoder for .tnef
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .zip  at /usr/bin/7za
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .kmz  at /usr/bin/7za
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .7z   at /usr/bin/7zr
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .jar  at /usr/bin/7z
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .swf  at /usr/bin/7z
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .lha  at /usr/bin/7z
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .iso  at /usr/bin/7z
mail    | Mar 12 23:19:21 mail amavis[199]: Found decoder for    .exe  at /usr/bin/unrar-free; /usr/bin/arj
mail    | Mar 12 23:19:21 mail amavis[199]: No decoder for       .F
mail    | Mar 12 23:19:21 mail amavis[199]: Deleting db files  in /var/lib/amavis/db
mail    | Mar 12 23:19:21 mail amavis[199]: Creating db in /var/lib/amavis/db/; BerkeleyDB 0.55, libdb 5.3
mail    | Mar 12 23:21:32 mail dovecot: ssl-params: SSL parameters regeneration completed

Okay. Your environment variable for the ssl type is correctly set. That means the start-mailserver script is not able to access the letsencrypt files.
So either if [ -e "/etc/letsencrypt/live/$HOSTNAME/fullchain.pem" ]; then or if [ -e "/etc/letsencrypt/live/$HOSTNAME/privkey.pem" ]; then fails.
You could test what is not working with adding a notify line (see the other lines around).
I will provide an pull request maybe tomorrow what prints what fails in some of these cases.
When you cannot find a way to fix it by your own: Have a look at the wiki page for custom ssl certs. You could easily add your letsencrypt files manually :)

Ah that's good to hear. I can see what happens around those lines in start-mailserver.sh. I would be able to add the notify, but I don't know how to apply it to my docker-composer. I'll take a look at the custom SSL certs. Cheers!

Perhaps this helps. I tried the manual files. The log returns (in green):
mail    |   * Configuring certificates using cert /tmp/ssl/live/domain.com/cert.pem and key /tmp/ssl/live/domain.com/privkey.pem
mail    |   * SSL configured with 'Manual' certificates

However I see amazon servers is doing something like a ping every few seconds (very annoying by the way) because it keeps giving me:
mail    | Mar 13 23:33:07 mail postfix/submission/smtpd[992]: SSL_accept error from ec2-13-126-248-148.ap-south-1.compute.amazonaws.com[<IP_ADDRESS>]: -1
mail    | Mar 13 23:33:07 mail postfix/submission/smtpd[992]: warning: TLS library problem: error:1417D102:SSL routines:tls_process_client_hello:unsupported protocol:../ssl/statem/statem_srvr.c:974:
mail    | Mar 13 23:33:07 mail postfix/submission/smtpd[992]: lost connection after STARTTLS from ec2-13-126-248-148.ap-south-1.compute.amazonaws.com[<IP_ADDRESS>]
mail    | Mar 13 23:33:07 mail postfix/submission/smtpd[992]: disconnect from ec2-13-126-248-148.ap-south-1.compute.amazonaws.com[<IP_ADDRESS>] ehlo=1 starttls=0/1 commands=1/2

However Gmail still returns SSL error: unknown CA (alert 48), and the log for that requests still returns:
mail    | Mar 13 23:33:25 mail dovecot: pop3-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=<IP_ADDRESS>, lip=<IP_ADDRESS>, TLS: Disconnected, session=<zudZr1Nnw47RVYCJ>

I'm starting to doubt the way I did my Let's Encrypt validation. As I mentioned before I validated through http, but it's for the subdomain mail.domain.com. Not sure if that's enough to get the required certificates?

The unsupported protocol error could be added by setting TLS_LEVEL to intermediate. This also enables  TLSv1, TLSv1.1 and some older ciphers that are disabled by default.
I'm not sure why Gmail is not accepting the CA. Did you test your SSL configuration with checktls.com?

That website helped me out. I used cert.pem instead of fullchain.pem. Now it's working, with TLS_LEVEL set to intermediate. Thank you so much!


change variant name to effect, update documentation for clarity and readability

"Signals" is the perfect name, this PR clarifies the mental model

Thanks for the PR!
I wonder if there's something else meaningful that signal could do as a variant if we free it up with effect, even to complement the existing signal utility behavior and make that more powerful.
Because this is built upon style queries, it can do plenty more than the group variant can naturally do. I think we're just scratching the surface here, and I would love to iterate on this change while it's early.
Any ideas?

I agree, I'm not quite sure about use cases for signal as a variant, but I do think there's an opportunity to change the way values and modifiers are used.
Could do signal-[<signal name>]/<signal value>, then write effect-[<signal name>]/<signal value> to say "when the signal is set to this specific value, apply a new style"
Demo here: https://play.tailwindcss.com/UcV9YsUvLH
I can't think of any great real-world use cases off the top of my head, but even just refactoring to signal-[<signal name>] feels a little more intuitive to me than using the modifier as the signal name.

@AlexVipond The modifier order used to bug me. It's sort of the standard now for all Tailwind CSS utilities that accept a name, so I want to be in line with that— as close to native as possible. 🙂


chore: Update to gwt 2.10.0

I don't know why there's no dtd for 2.10.0, so I chose the dtd from 2.9.0

Seems the 2.10.0 dtd may be deployed soon? https://github.com/gwtproject/gwt/issues/9770

It looks like there's no entry in the changelog. I think I'll merge this first, because it has two approvals, and encourage GWT users to test the latest SNAPSHOT release. If there are any critical issues, then fixing them may affect the changelog; if there aren't any issues, it should be easy to add it in (potentially including quick tips for updating, if we discover some are needed).

Current Gdx Setup fails when executing superDev with several errors like this:
[ERROR] Line 6669: No source code is available for type jsinterop.annotations.JsMethod; did you forget to inherit a required module?
Maybe something missing in the Gdx Setup template app GWT config?

Ahhh, probably because
"com.google.jsinterop:jsinterop-annotations:${versions.jsinteropAnnotations}:sources"

is missing

transitively

Not sure about that, I think we don't do it with any other sources. I'd just add the dep alongside the other sources deps.


Doesn't compile

carmen@serenity:~/code/empires/vtf2tga$ g++ -std=c++11 vtf2tga.cpp -lVTFLib13 Magick++-config --cppflags --cxxflags --ldflags --libs -o vtf2tga.exe
vtf2tga.cpp: In function ‘int main(int, char**)’:
vtf2tga.cpp:35:17: warning: variable ‘dstformat’ set but not used [-Wunused-but-set-variable]
VTFImageFormat dstformat;
^
/usr/lib/gcc/x86_64-linux-gnu/4.9/../../../x86_64-linux-gnu/libVTFLib13.so: undefined reference to `tx_compress_dxtn(int, int, int, unsigned char const*, unsigned int, unsigned char*, int)'
collect2: error: ld returned 1 exit status

Sounds like VTFLib13.so is missing a dependency. Not sure what that might be.
Unfortunately I'm no longer supporting this software. I'd recommend looking at the Source 2 Decompiler as that includes some updated code for changes to the vtex_c format.

Sounds like VTFLib13.so is missing a dependency. I am not sure what that is.
Unfortunately I'm not supporting this software anymore, sorry!

It's a bug in VTFLib. I fixed it in this PR: https://github.com/panzi/VTFLib/pull/7

Thanks Yepoleb. It hasn't solved the issue for me, just changed the error to an ImageMagick problem - the underlying issue in this project is of not specifying the dependencies:
vtf2tga.cpp: In function ‘int main(int, char**)’:
vtf2tga.cpp:35:17: warning: variable ‘dstformat’ set but not used [-Wunused-but-set-variable]
  VTFImageFormat dstformat;
                 ^~~~~~~~~
/tmp/ccHZ35zq.o: In function `main':
/home/carmen/code/empires/vtf2tga/vtf2tga.cpp:71: undefined reference to `Magick::Image::read(unsigned int, unsigned int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, MagickLib::StorageType, void const*)'
/home/carmen/code/empires/vtf2tga/vtf2tga.cpp:75: undefined reference to `Magick::Image::magick(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
/home/carmen/code/empires/vtf2tga/vtf2tga.cpp:76: undefined reference to `Magick::Image::write(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)'
collect2: error: ld returned 1 exit status

Can you show me the command line you used and the output of Magick++-config --version?

Magick++-config --version gives 1.3.20
Unfortunately, vtfconv gives similar undefined references.
identify --version shows I am running ImageMagick 6.8.9-9

What's your distribution, so I can test on it?
Maybe Magick++-config --libscan give us a clue about what's wrong. My output is -lGraphicsMagick++ -lGraphicsMagick -ljbig -lwebp -llcms2 -ltiff -lfreetype -ljpeg -lpng16 -lwmflite -lXext -lSM -lICE -lX11 -llzma -lbz2 -lxml2 -lz -lm -lgomp -lpthread.
Running ldconfig as root often magically solves linker problems for me, you could try that too.

$ Magick++-config --libs
-lGraphicsMagick++ -lGraphicsMagick -ljbig -llcms2 -ltiff -lfreetype -ljasper -ljpeg -lpng12 -lwmflite -lXext -lSM -lICE -lX11 -llzma -lbz2 -lxml2 -lz -lm -lgomp -lpthread
$ uname --all
Linux serenity 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02) x86_64 GNU/Linux
(Debian 9)
sudo ldconfig output nothing, and vtfconv make still runs into undefined references (despite praying)

I just compiled vtf2tga and vtfconv on a fresh install of Debian jessie and stretch. It worked flawlessly, aside from the testing installer being constantly broken. That means the problem is most likely with your environment, but I'm fine with helping you with that. If you want you can add me on Steam, so we can talk about it there.