postfix: 3.6.4 -> 3.7.0

Motivation for this change
http://www.postfix.org/announcements/postfix-3.7.0.html
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Postfix 3.7.0 support build with OpenSSL 3.0.0 and PCRE2:
diff --git a/pkgs/top-level/all-packages.nix b/pkgs/top-level/all-packages.nix
index 3978163a631..51e9a352bac 100644
--- a/pkgs/top-level/all-packages.nix
+++ b/pkgs/top-level/all-packages.nix
@@ -21312,7 +21312,12 @@ with pkgs;

   popa3d = callPackage ../servers/mail/popa3d { };

-  postfix = callPackage ../servers/mail/postfix { };
+  postfix = callPackage ../servers/mail/postfix {
+    openssl = openssl_3_0;
+    pcre = pcre2;
+    cyrus_sasl = cyrus_sasl.override { openssl = openssl_3_0; };
+    openldap = openldap.override { openssl = openssl_3_0; };
+  };

   postfixadmin = callPackage ../servers/postfixadmin { };

ldd ./result/bin/postfix | grep ssl
        libcrypto.so.3 => /nix/store/jrvavv8r817np5pbs408cczigpyx5hya-openssl-3.0.1/lib/libcrypto.so.3 (0x000060dc003fd000)
        libssl.so.3 => /nix/store/jrvavv8r817np5pbs408cczigpyx5hya-openssl-3.0.1/lib/libssl.so.3 (0x000060dc0034d000)

ldd ./result/bin/postfix | grep pcre
        libpcre2-8.so.0 => /nix/store/gfwgghgmj3qxg919p0fcsc910vxwp0dv-pcre2-10.37/lib/libpcre2-8.so.0 (0x0000633e72715000)

As per this notice from the CERT-FR (in French), this fixes a security vulnerability present in previous versions.

It just links to the release announcement which lists mitigations but no vulnerabilities.

We should then also consider to update NixOS 21.11. Do we want to update it to 3.7.0, which is a new minor version? Otherwise, for 21.11, Postfix 3.6.5 also solves the vulnerability.

We can update to 3.6.5. Do you mind filing a PR?

Probably need to add more

Then I would say we shouldn't use OpenSSL 3 etc. We should just wait until it becomes the default.

arch is on 3.7.0 https://archlinux.org/packages/extra/x86_64/postfix/

As https://github.com/NixOS/nixpkgs/pull/197491 is brings us Postfix 3.7.3 this PR is not needed anymore.


build: cleanup pipelines

Description
The github actions are more or less following the boilerplate from very good workflows
this should be cleaned up, and make pass :)

all paa, all good ;)


Feature/useSimpleLayout

This should have all the outstanding changes that we discussed in the other PR.
I'll close the other one off now in favour of this one (which is on top of the current master).

@gary-menzel do you have any code sample/snippet on how to use it?


[Feature]: programmatically update table column order

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
Hi, I would like the ability to set the a table widgets column order, as well as updating the column datatype, from a JSObject.
Why should this be worked on?
I'm building a control panel to allow a user to see and update configuration from around 20 different tables.  Instead of have 20 different table widgets on one page, I'd like to have one table that is dynamically populated.  I can currently use a Select widget with a JSObject to dynamically populate the table, but it re-orders the columns each time the source data changes.  All of my tables have 2 common columns that I would like to always appear at the far right (date created, date modified).
I think a new function, perhaps called 'setColumnOrder' for the table object, that can accept an array with the column names in the desired order.
It'd be great if we could update all of the table.json properties programmatically, but I can see why you'd want to control each one with a specific 'set...' function.  The other properties I would really like to be able to update from a JSObject are 'columnType', 'label', 'isEditable' and 'isVisible'.
Thanks for the consideration,

@mmcallister-selkirk thanks for raising this issue. We'll give it some consideration but it's unlikely that we'll be able to pick this up any time soon. If it's only about the UX, may I suggest having 20 tables inside separate tabs and changing the default tab based on the table you want to show?

Thanks @Nikhil-Nandagopal for the consideration.  I'll be able to use tabs, or the setVisibility() function to hide unselected tables.


Add: Lanzhou Culture & Tourism Channel

Channel Name
Lanzhou Culture & Tourism Channel
Alternative Names (optional)
文旅频道
Network (optional)
No response
Owners (optional)
No response
Country
CN
Subdivision (optional)
No response
City (optional)
Lanzhou
Broadcast Area
c/CN
Languages
zho
Categories (optional)
culture
NSFW
FALSE
Launched (optional)
No response
Closed (optional)
No response
Replaced By (optional)
No response
Website (optional)
https://www.lztv.tv/folder25/folder26/folder30/
Logo
https://p3-pc.douyinpic.com/img/aweme-avatar/tos-cn-i-0813c001_676b39bc8bfd41f58814f7381000dce6~c5_300x300.jpeg?from=2956013662
Notes
No response

Please update your request:

the logo link is geoblocked

https://github.com/iptv-org/database/blob/master/CONTRIBUTING.md#channels

Corrected


Dep Ensure on Master

Adds dep vendor changes applied by #40

This change is

Can you help clean up the commit history ?

Looks good to me other than all the commits :)


Service suggestion: hasura.io

Could you add https://hasura.io/ , an instant GraphQL service?

Why the service? It is enough to run DockerFile, here is an example.
FROM hasura/graphql-engine:v2.6.0-beta.1

ENV HASURA_GRAPHQL_DATABASE_URL postgresql://user:password@host:5432/db_name
ENV HASURA_GRAPHQL_ENABLE_CONSOLE true
ENV HASURA_GRAPHQL_DEV_MODE true

ENV HASURA_GRAPHQL_ENABLED_LOG_TYPES startup,http-log,webhook-log,websocket-log,query-log
ENV HASURA_GRAPHQL_ADMIN_SECRET ***
ENV HASURA_GRAPHQL_ENABLE_TELEMETRY false
ENV HASURA_GRAPHQL_JWT_SECRET '{"type":"HS256","key":"*********"}'
ENV HASURA_GRAPHQL_UNAUTHORIZED_ROLE anonymous
ENV HASURA_GRAPHQL_LOG_LEVEL debug
ENV HASURA_GRAPHQL_CORS_DOMAIN *
ENV HASURA_GRAPHQL_EXPERIMENTAL_FEATURES inherited_roles

ENV HASURA_GRAPHQL_CONNECTION_COMPRESSION true
ENV HASURA_GRAPHQL_WEBSOCKET_KEEPALIVE 5
ENV HASURA_GRAPHQL_PG_CONN_LIFETIME 0
ENV HASURA_GRAPHQL_PG_CONNECTIONS 100

It is happening in the next version!


[SPARK-36669][SQL] Add Lz4 wrappers for Hadoop Lz4 codec

What changes were proposed in this pull request?

This patch proposes to add a few LZ4 wrapper classes for Parquet Lz4 compression output that uses Hadoop Lz4 codec.
Why are the changes needed?

Currently we use Hadop 3.3.1's shaded client libraries. Lz4 is a provided dependency in Hadoop Common 3.3.1 for Lz4Codec. But it isn't excluded from relocation in these libraries. So to use lz4 as Parquet codec, we will hit the exception even we include lz4 as dependency.
[info]   Cause: java.lang.NoClassDefFoundError: org/apache/hadoop/shaded/net/jpountz/lz4/LZ4Factory
[info]   at org.apache.hadoop.io.compress.lz4.Lz4Compressor.<init>(Lz4Compressor.java:66)
[info]   at org.apache.hadoop.io.compress.Lz4Codec.createCompressor(Lz4Codec.java:119)
[info]   at org.apache.hadoop.io.compress.CodecPool.getCompressor(CodecPool.java:152)
[info]   at org.apache.hadoop.io.compress.CodecPool.getCompressor(CodecPool.java:168)

Before the issue is fixed at Hadoop new release, we can add a few wrapper classes for Lz4 codec.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Modified test.

After discussing with some PMC members, more preferred direction now is to document snappy issue as known issue for 3.2. Here to deal with lz4 issue, so to add lz4 wrappers back.
cc @dbtsai @dongjoon-hyun @sunchao @cloud-fan

Test build #143100 has started for PR 33940 at commit f649d6c.

Test build #143100 has finished for PR 33940 at commit f649d6c.

This patch fails Java style tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/143100/

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47603/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47603/

Test build #143102 has started for PR 33940 at commit b665d1c.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47606/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47606/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47606/

Test build #143102 has finished for PR 33940 at commit b665d1c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/143102/

Test build #143113 has started for PR 33940 at commit df00bab.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47618/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47618/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47618/

Test build #143113 has finished for PR 33940 at commit df00bab.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/143113/

Thanks! Merging to master/3.2.

+1, late LGTM like the first PR. Thank you, @viirya and @cloud-fan .

Late +1, thanks for the fix!


为什么最小api是16

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:processDebugManifest'.

Manifest merger failed : uses-sdk:minSdkVersion 15 cannot be smaller than version 16 declared in library [com.sankuai.waimai.router:router:1.0.41] /Users/mac/.gradle/caches/transforms-1/files-1.1/router-1.0.41.aar/e0026560c6ebc6f667ef1f72f7599244/AndroidManifest.xml as the library might be using APIs not available in 15
Suggestion: use a compatible library with a minSdk of at most 15,
or increase this project's minSdk version to at least 16,
or use tools:overrideLibrary="com.sankuai.waimai.router" to force usage (may lead to runtime failures)

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

在Application工程的Manifest配置一下，覆盖SDK中的版本即可


(properties) Keys with . in them are highlighted differently

Describe the issue
When the key part doesn't contain a dot it's rendered as other properties
Which language seems to have the issue?
Properties
Are you using highlight or highlightAuto?
I don't know, I am using @asciidoc/reveal
Sample Code to Reproduce
listeners=CLIENT://<IP_ADDRESS>:9092,CLUSTER://<IP_ADDRESS>:9093
advertised.listeners=CLIENT://public:9092,CLUSTER://private:9093
listener.security.protocol.map=CLIENT:PLAINTEXT,CLUSTER:PLAINTEXT
inter.broker.listener.name=CLUSTER

is rendered as

Expected behavior
listeners= should be rendered as advertised.listeners=
Additional context
Highlight.js 10.7.1 in Chrome with Github theme

@egor-rogov This one is for you... you committed our Properties support. You seem to make a very purposeful distinction between alphanumeric keys and "other" keys yet none of our tests or sample data have anything other than alphanumeric keys... what were you going for with "other" keys, and is this behavior what you intended?

@egor-rogov Ping. Any thoughts?

Hmm... Returning back to this, I couldn't find any solid reason for separating non-alphanumeric keys, other then relevance balancing game. Anyway using meta class looks plain wrong.
I'm going to try to get rid of non-alphanumeric case and see if it's okay from autodetection point of view. If not, I'll leave it be and will just replace className.

And is . supposed to be treated differently for some reason or should that be included in alphanumeric keys?  What other keys are there?  Could we get some examples in the tests?  Right now I have no idea what an example of a non-alphanumeric key even is or what's allowed.

Looks like there are no any restrictions, you can use whatever characters you like for keys. No special cases, dot is just like any other character.
I think my thoughts were like this: "in all examples of .properties files I've ever seen the keys were alphanumeric; so if we encounter something strange (@#$ = foo) we'd better use zero relevance". And then I made this special case and somehow managed to use different class name for it. It's a 100% bug.
I've just checked: it's OK to flatten he grammar to just keys (making no distinction for character classes).

so if we encounter something strange (@#$ = foo) we'd better use zero relevance"

Ah, that's worth some thought.  The wider the rule gets the more careful we need to be with relevance.  Thanks for the fix though.  I'll review it later and see if I think we need any relevance tweaks.  If we do I think we can do it a simpler way than having two entirely different modes like that.

@gquintana Thanks!  In version 11 these keys should render exactly the same as the first.

Thank you @joshgoebel  and @egor-rogov


Add installation instructions and tutorial

@mikhailsirenko Thanks a lot for this. Docs are always really appreciated, saves a lot of reinventing the wheel!
@averbraeck could you review and merge this, before it's outdated, needs to be rebased, etc.


[1.3.6-prepare][FIX-#4617][LoggerServer] task log can not refresh in …

…time #4618
issue #4617
pr #4618

@597365581 please take a look.Thx

.ok

okokok


Always getting 'bad request' response

[Try to implement the speech enrollment API but always getting a bad request response. Here's my code: using System;
using System.Net.Http.Headers;
using System.Text;
using System.Net.Http;
using System.Web;
namespace SpeechRecEnroll
{
class Program
{
static void Main(string[] args)
{
MakeRequest();
Console.WriteLine("Hit ENTER to exit...");
Console.ReadLine();
}
    static async void MakeRequest()
    {
        var client = new HttpClient();
        var queryString = HttpUtility.ParseQueryString(string.Empty);

        // Request headers
        client.DefaultRequestHeaders.Add("Ocp-Apim-Subscription-Key", "****************************");

        // Request parameters
        //queryString["shortAudio"] = "true";
        var uri = "https://westus.api.cognitive.microsoft.com/spid/v1.0/identificationProfiles/d556fc02-c007-4e05-9205-265ba65569dc/enroll?" + queryString;

        HttpResponseMessage response;

        // Request body
        byte[] byteData = Encoding.UTF8.GetBytes("c:\\ogilo\\source\\repos\\SpeechRecEnroll\\SpeechRecEnroll\\bin\\Debug\\netcoreapp2.2\\test.wav");

        using (var content = new ByteArrayContent(byteData))
        {
            content.Headers.ContentType = new MediaTypeHeaderValue("application/octet-stream");
            response = await client.PostAsync(uri, content);
        }
    }
}

}]

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

ID: 3604fe7e-46a3-6f5b-41e0-d3e69e01c8ae
Version Independent ID: 9415c8a5-177e-fe11-7198-3d97ed438dc8
Content: What is the Speaker Recognition API? - Azure Cognitive Services
Content Source: articles/cognitive-services/Speaker-recognition/Home.md
Service: cognitive-services
GitHub Login: @dwlin
Microsoft Alias: dwlin

@codescream, Thanks for the question! We are investigating and will update you shortly.

Hi, any feedback please?

@codescream Hi Mark, since this issue is not a document issue, I help you move it to our MSDN forum. Please refer to: https://social.msdn.microsoft.com/Forums/en-US/c1f42f1f-43fe-48e4-bf7e-05bf24cc9fb8/always-getting-bad-request-response?forum=AzureCognitiveService  Please keep eyes on it.
We will now proceed to close this thread. If there are further questions regarding this matter, please respond here and @YutongTie-MSFT and we will gladly continue the discussion.

Can we please never - ever - suggest MSDN forums to people here?

@Jarrich Hi Jarrich, sorry for your experience. For now we have new tech forum - Microsoft Q&A, please feel free to try ^^ https://docs.microsoft.com/en-us/answers/index.html

@Jarrich Hi Jarrich, sorry for your experience. For now we have new tech forum - Microsoft Q&A, please feel free to try ^^ https://docs.microsoft.com/en-us/answers/index.html

Ok, thank you!


Commits show the right time on repo pages, explore page doesn't

Commits show the right time (e.g. "3 minutes ago") in the repo page, but in the explore page, the "Updated x time ago" doesn't follow, it shows instead, the time of the commit before the last time I updated gogs, which was yesterday.
I updated to develop, then deleted it and installed back again from master branch.
My current gogs version is <IP_ADDRESS>4, installed from source.
I'm using "MySQL DB Ver 14.14 Distrib 5.5.46, for debian-linux-gnu (i686)"
Gogs is installed in a Debian Wheezy i386 machine,
Running git <IP_ADDRESS>
What could be causing this and how can I diagnose it?
Thanks.

Thanks your feedback!

Commits show the right time (e.g. "3 minutes ago") in the repo page, but in the explore page, the "Updated x time ago" doesn't follow, it shows instead, the time of the commit before the last time I updated gogs, which was yesterday.

How did you push the code?

With GitHub Desktop for windows, with the origin set to the gogs repo, which is the same way I pushed previous commits that showed the right time on "Explore"

Hmm.. are you pushing by HTTP or SSH?

HTTP

Thanks.

Commits show the right time (e.g. "3 minutes ago") in the repo page, but in the explore page, the "Updated x time ago" doesn't follow, it shows instead, the time of the commit before the last time I updated gogs, which was yesterday.

Can you given some screenshots?

Repo pages with correct date, time:

Explore page with old time:

Thanks, I got it.

Hi there, can you checkout develop branch see if the fix works?

Checked, it doesn't yet, made one more last commit a minute ago, which consisted only in deleting some files, did not add new lines of code, I don't know if that could have any effect on showing or not the correct Updated time.

What is the version you just tested?

<IP_ADDRESS>4 Beta

The version of develop is <IP_ADDRESS>4.

True, when I run "go get -u ./..." just before "go build", it downloads "<IP_ADDRESS>4 Beta" again, overwriting the already present "<IP_ADDRESS>4" in the gogs directory

Ok, I was following this http://gogs.io/docs/installation/install_from_source#build-from-develop-branch when it downloaded the previous version.
But I ran "git checkout develop" after "cd gogs" and did "go get ./..." instead of "go get -u ./...", then built successfully, made an additional commit to one of the repos and checked that now it works perfectly:

Thanks man! :smile:

Thanks your confirmation!


Comment shortcut not using correct comment syntax

Initial checklist

[X] I read the support docs
[X] I read the contributing guide
[X] I agree to follow the code of conduct
[X] I searched issues and couldn’t find anything (or linked relevant results below)

Affected packages and versions
mdxv2
Link to runnable example
No response
Steps to reproduce
Inside VSCode open a .mdx file and hightlight a line e.g.
# Some cool heading

Press CMD + / on macOS or Ctrl + /. Observe the line changes to:
<!-- # Some cool heading -->

Expected behavior
MDX requires using JS comment syntax not HTML e.g.
{/* # Some cool heading */}

Actual behavior
Wrong syntax is used.
Runtime
Node v16
Package manager
npm v6
OS
macOS
Build and bundle tools
webpack, Next.js

The latest version on the marketplace is v0.3.2 but on here its v1.0.0 so it looks like the latest changes aren't live yet.

The marketplace has been bumped to v1.0.1 and I am experiencing the same issue.

I have been experimenting for a while now and discovered that if you remove contributes.grammars from package.json, the commenting works as expected. This surprised me, since I thought grammars were the textmate rule for syntax highlighting and nothing more. But, anyway, it shows where the problem lies.

Found it. The setting contributes.grammars.embeddedLanguages includes the directive
         "text.html.markdown": "markdown",
This shouldn't be there, I think. MDX files won't have embedded markdown -- that part of the grammar definition, I think, is for CSS within HTML and stuff like that. If markdown (non-MDX markdown) is indicated as an embedded language, then it will take over and overrule MDX commenting and so on.
Anyway, if you remove that line from grammars.embeddedLanguages then MDX2 commenting works as expected and normal markdown syntax highlighting does, as well.
I'm going to read the contribution guide and submit a PR. I don't do this very often, please be gentle!

MDX files won't have embedded markdown

@grahampcharles Sorry for the delay first, but I'm not quite sure to understand this. Why markdown can not be included in MDX?

Well, because MDX is itself a version of markdown. If you indicate that markdown can be included as an embed within markdown, then your markdown language configuration will take over.
The embedded grammar is there for including other grammars within your parent language configuration. For example, if you have <style> tags within HTML, you want CSS language features to take over.
The proof is in the pudding, though. If you remove the embed line, then MDX commenting works correctly. If you leave it in, then it does not -- the markdown language configuration takes over.

@grahampcharles Thanks.
I just forgot mdx@v2 doesn't use HTML style comments anymore.

I can confirm that the latest version v1.0.3 uses the correct syntax now when using the comment shortcut for embedded markdown:
{/* ## Headings */}

but it doesn't work on ESM import/exports or embedded JavaScript:
// export const foo = "bar";

export const foo = "bar"; is recognized as ES module syntax, so its comments are // by default. It needs some kind of investigation.
cc @remcohaszing
Do you have any experience about this?

close in favor of #221


Petting zoo version

the compatible petting-zoo version for SMACv2 should be 1.8.1 @benellis3

Thanks, it works for me.


Node memory fix

This fixes it so that the executor updates the HADOOP_HEAPSIZE.
There are also changes to have configurations are read.

@elingg @gabrielhartmann looking for a review.  This has been tested working.

One major concern related to setting HADOOP_HEAPSIZE twice in two locations. Another style comment. Let's address these comments and get any feedback from @gabrielhartmann. Other than that, looks great @kensipe!

@elingg updates in place... tested on dcos... starting test on standard mesos.   @gabrielhartmann ready for additional review.

Tested on Mesos and DCOS... boom!

Looks great! One nit above @Kensipe. If no objections from @gabrielhartmann by this afternoon, I will merge

LGTM.