ETCD joining does not work, Issue with k8s.io/docs/setup/independent/high-availability/

This is a...

[ ] Feature Request
[X] Bug Report

Problem:
I have followed the stacked control plane documentation, after joining the second etcd with
KUBECONFIG=/etc/kubernetes/admin.conf kubectl exec -n kube-system etcd-${CP0_HOSTNAME} -- etcdctl --ca-file /etc/kubernetes/pki/etcd/ca.crt --cert-file /etc/kubernetes/pki/etcd/peer.crt --key-file /etc/kubernetes/pki/etcd/peer.key --endpoints=https://${CP0_IP}:2379 member add ${CP1_HOSTNAME} https://${CP1_IP}:2380
kubeadm alpha phase etcd local --config kubeadm-config.yaml
the etcd on the first master started to restart and the second one did also restart all the time.
It looks like if following the documentation the second master starts a new cluster instead of joining  the existing one
Output from the second etcd
2018-07-15 17:10:36.572643 I | etcdserver/membership: added member 20c0dd3b6954fe4e [https://X.X.X.X:2380] to cluster 22c27da476f1057b
2018-07-15 17:10:36.572747 I | embed: ClientTLS: cert = /etc/kubernetes/pki/etcd/server.crt, key = /etc/kubernetes/pki/etcd/server.key, ca = , trusted-ca = /etc/kubernetes/pki/etcd/ca.crt, client-cert-auth = true
2018-07-15 17:10:36.572821 I | etcdserver/membership: added member c7a6c6075e685c85 [https://Y.Y.Y.Y:2380] to cluster 22c27da476f1057b
2018-07-15 17:10:36.605605 E | rafthttp: request sent was ignored (cluster ID mismatch: peer[20c0dd3b6954fe4e]=8d2dcd2eb7f48c4, local=22c27da476f1057b)
The last line was repeated for ever.
The first etcd (don't have the log right now), complained about not being able to elect a master and/or find its peer and entered a restart loop (although no crashloop backoff)
Proposed Solution:
To get the cluster to form correctly I had to add following extra args to the first etcd node:
initial-cluster-token: "some token"
and for the second and third node
initial-cluster-token: "some token"
initial-cluster-state: "existing"
Page to Update:
https://kubernetes.io/docs/setup/independent/high-availability/

Kubernetes Version:
kubeadm version:
kubeadm version: &version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.0", GitCommit:"91e7b4fd31fcd3d5f436da26c980becec37ceefe", GitTreeState:"clean", BuildDate:"2018-06-27T20:14:41Z", GoVersion:"go1.10.2", Compiler:"gc", Platform:"linux/amd64"}
rpm -qa:
kubelet-1.11.0-0.x86_64
kubectl-1.11.0-0.x86_64
kubernetes-cni-0.6.0-0.x86_64
kubeadm-1.11.0-0.x86_64
docker images:
k8s.gcr.io/kube-controller-manager-amd64   v1.11.0             55b70b420785        2 weeks ago         155 MB
k8s.gcr.io/kube-scheduler-amd64            v1.11.0             0e4a34a3b0e6        2 weeks ago         56.8 MB
k8s.gcr.io/kube-apiserver-amd64            v1.11.0             214c48e87f58        2 weeks ago         187 MB
k8s.gcr.io/kube-proxy-amd64                v1.11.0             1d3d7afd77d1        2 weeks ago         97.8 MB
k8s.gcr.io/coredns                         1.1.3               b3b94275d97c        7 weeks ago         45.6 MB
k8s.gcr.io/etcd-amd64                      3.2.18              b8df3b177be2        3 months ago        219 MB

/assign @detiber @chuckha


{Core} Ping azure-mgmt-core version setup.py

Description

The pipeline of extension install pre version of packages https://github.com/Azure/azure-cli-extensions/blob/a0b24e846c3a9d74a5deddac5289753d5187869b/scripts/ci/test_source.sh#L6.
Recently this PR triggered a issue that the azure-mgmt-core 1.3.0b1 (preview version) conflict with azure-core 1.14.0 (stable version).

This PR will ping the version of azure-mgmt-core <= 1.3.0 in setup.py to workaround above issue.
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Core

Is there an issue to track the actual fix for this incompatibility?

Is there an issue to track the actual fix for this incompatibility?

cannot import name `ChallengeAuthenticationPolicy`

- ping
+ pin

pip won't install beta versions without --pre, how does azure-mgmt-core 1.3.0b1 get installed?


"info • This method overrides a method annotated as @mustCall super in 'State', but does invoke the overriden method" has typos

specifically, the annotation is @mustCallSuper not @mustCall super and the word overridden is spelled with two ds.
cc @pq

d'oh!  It looks like @mohamedhayibor has a patch in. 👍


Add support for order-sensitive aggregation for multipartitions

Which issue does this PR close?

Closes #.
Rationale for this change
Order-sensitive aggregators (FIRST_VALUE, LAST_VALUE, ARRAY_AGG) previously was working only in single partition (AggregateMode::Single mode).  This behavior is limited. Current PR extends this support to multi partitions.
With the changes in this PR query below
SELECT FIRST_VALUE(amount ORDER BY ts ASC) AS fv1,
  LAST_VALUE(amount ORDER BY ts DESC) AS fv2
  FROM sales_global

can work both in single partition (set datafusion.execution.target_partitions = 1) and multipartition (set datafusion.execution.target_partitions = 8).

What changes are included in this PR?
To be able to support this feature,

Order sensitive aggregators (in the AggregateMode::Partial mode) now includes ordering expressions in their output table so that subsequent Aggregate stages in the plan (AggregateMode::Final or AggregateMode::FinalPartitioned) can enforce their required ordering.
A new variant of the ARRAY_AGG (OrderSensitiveArrayAgg) is introduced, since its implementation is quite different than the ArrayAgg.

Are these changes tested?
Yes, new tests added to the groupby.slt file (approximately 300 lines of change) to test new functionality.

Are there any user-facing changes?

I plan to review this PR carefully tomorrow

This is good to go from my perspective. If any issue that we might havem missed comes up, we will address in a follow on PR. Thanks for the review @alamb!


changing pointer for dbt-core in 1.0.latest

resolves # https://github.com/dbt-labs/dbt-spark/pull/307
Description
Changing ref pointer for dbt-core install so branches test against correct "main" branch to have correct testing cases throughout history.
Checklist

[x] I have signed the CLA
[ ] I have run this code in development and it appears to resolve the stated issue
[ ] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have updated the CHANGELOG.md and added information about my change to the "dbt-spark next" section.

@leahwicz redid the set due to the issues in previous pr after main pull in https://github.com/dbt-labs/dbt-spark/pull/307


add props types

Simple PR for removing the dirty any of the provider's props.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@d92e939). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master    #321   +/-   ##
========================================
  Coverage          ?   84.8%
========================================
  Files             ?      21
  Lines             ?     454
  Branches          ?      94
========================================
  Hits              ?     385
  Misses            ?      67
  Partials          ?       2

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 d92e939...d3d5fae. Read the comment docs.


Register variable's proto function with key 'LOCAL_VARIABLES'

When export/input meta graph, user expect all collections
been rebuilded on target graph, but it turns out local variables
on target collection is not Variable but Tensor because local variable
do not have it's proto fn registered

Can one of the admins verify this patch?

Sadly we can't accept this as-is because it breaks the capability of loading any meta graphs which were saved before this change.
Instead for now it's safer to put the registration in your model core.

Well then, Let's change it into a issue, cause it look like one.


DPT error

DPT is sending an error message:

Traceback (most recent call last):
File "C:\GH_CPython\PythonFileWritten_2.py", line 58, in
import cv2
ModuleNotFoundError: No module named 'cv2'

Thanks!

Hello! Thanks for you feedback.
Seems that your machine is missing the "opencv-python" library... Simply try installing it through the CMD.exe on Windows OS and restart Rhino. Please, let me know

Hello! Thanks for you feedback. Seems that your machine is missing the "opencv-python" library... Simply try installing it through the CMD.exe on Windows OS and restart Rhino. Please, let me know

Thanks Luciano! issue was solve
Regards
Luis

Hurray! 😊 Thanks for your feedback!


Roman Numeral Converter: Tests results incorrect

Challenge Name

Roman Numeral Converter
Issue Description

The FCC IDE showed that my code didn't pass some of the tests while the tests are passed no problem on my Chrome 53.0.2762.0 canary (64-bit), and on NodeJS (v4.2.3). What's more interesting is that when I used the same code on the Chinese branch of FCC (freecodecamp.cn), it worked perfectly.
Browser Information

Browser Name, Version: Chrome 53.0.2762.0 canary (64-bit)
Operating System: OS X 10.11.4
Mobile, Desktop, or Tablet: Desktop

Your Code
// If relevant, paste all of your challenge code in here
"use strict";
"use esversion: 6";

class RomanDict {
	constructor() {
		this.M = 1000;
		this.D = 500;
		this.C = 100;
		this.L = 50;
		this.X = 10;
		this.V = 5;
		this.I = 1;
	}

}

function stringMultiplier(str, n) {
	var result_str = "";

	for (var i = 0; i < n; i++) {
		result_str = result_str + str;
	}

	return result_str;
}

function numOfSymbol(num, symbol) {
	var roman_dict = new RomanDict();

	// console.log([parseInt(num / roman_dict[symbol]), num % roman_dict[symbol]]);
	return [parseInt(num / roman_dict[symbol]), num % roman_dict[symbol]];
}

function convertToRoman(num) {
	var roman_dict = new RomanDict();
	var result_str = "";
	var temp_num = num;

	for (var property in roman_dict) {
    	if (roman_dict.hasOwnProperty(property)) {
    		result_str = result_str + stringMultiplier(property, numOfSymbol(temp_num, property)[0]);
			temp_num = numOfSymbol(temp_num, property)[1];
    	}
	}

	// ETL for XI and VI etc...
	result_str = result_str.replace("DCCCC", "CM");
	result_str = result_str.replace("CCCC", "CD");
	result_str = result_str.replace("LXXXX", "XC");
	result_str = result_str.replace("XXXX", "XL");
	result_str = result_str.replace("VIIII", "IX");
	result_str = result_str.replace("IIII", "IV");

	// console.log(result_str);
	return result_str;
}

// convertToRoman(36);

console.log(convertToRoman(2) === "II")
console.log(convertToRoman(3) === "III")
console.log(convertToRoman(4) === "IV")
console.log(convertToRoman(5) === "V")
console.log(convertToRoman(9) === "IX")
console.log(convertToRoman(12) === "XII")
console.log(convertToRoman(16) === "XVI")
console.log(convertToRoman(29) === "XXIX")
console.log(convertToRoman(44) === "XLIV")
console.log(convertToRoman(45) === "XLV")
console.log(convertToRoman(68) === "LXVIII")
console.log(convertToRoman(83) === "LXXXIII")
console.log(convertToRoman(97) === "XCVII")
console.log(convertToRoman(99) === "XCIX")
console.log(convertToRoman(500) === "D")
console.log(convertToRoman(501) === "DI")
console.log(convertToRoman(649) === "DCXLIX")
console.log(convertToRoman(798) === "DCCXCVIII")
console.log(convertToRoman(891) === "DCCCXCI")
console.log(convertToRoman(1000) === "M")
console.log(convertToRoman(1004) === "MIV")
console.log(convertToRoman(1006) === "MVI")
console.log(convertToRoman(1023) === "MXXIII")
console.log(convertToRoman(2014) === "MMXIV")
console.log(convertToRoman(3999) === "MMMCMXCIX")

Screenshot

your code works fine for me in FCC 'ide'
also tested running through node. 4 results in IV and type is string

@savourylie you code passes just fine for me on the FCC website. But I'm a bit unclear on what you mean between the FCC "IDE" and just Chrome and Node.

@erictleung Not sure about Chrome, I assume running local file and viewing in dev console?
Node however, if you install node js you can execute js at the command line.

@robjloranger Thanks for clarifying for me. Yes that's what I meant by running in Chrome (dev tools console). I usually test my JS in node.js which allows me to test my code "headlessly". I find that very convenient. :)
Oh and strangely, when I opened up FCC just now, everything was running green! So I pressed Test/Run button again and it showed all passed and jumped to the next challenge.
I don't know what happened as I didn't change my code nor anything. But I guess this mean the problem is fixed now. Thanks guys. Deeply appreciated!

Glad it's sorted, sometimes a browser refresh or restart helps. It can be
cashed code.
How do we close this now?
Rob Loranger
250-589-4806
Saanich, B.C.
www.robloranger.ca
On Jun 11, 2016 10:15 PM, "Calvin Ku"<EMAIL_ADDRESS>wrote:

@robjloranger https://github.com/robjloranger Thanks for clarifying for
me. Yes that's what I meant by running in Chrome (dev tools console). I
usually test my JS in node.js which allows me to test my code "headlessly".
I find that very convenient. :)
Oh and strangely, when I opened up FCC just now, everything was running
green! So I pressed Test/Run button again and it showed all passed and
jumped to the next challenge.
I don't know what happened as I didn't change my code nor anything. But I
guess this mean the problem is fixed now. Thanks guys. Deeply appreciated!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/9090#issuecomment-225410633,
or mute the thread
https://github.com/notifications/unsubscribe/AMqbrmsp-xvlkVLpvxuBPXE9_iXyaLbIks5qK5XkgaJpZM4IzlFA
.

@savourylie glad things are working now! I'll go ahead and close this issue as it seems resolve. Happy coding!


Add docker or similar setup

Should there be a separate build container from the node server container that just outputs optimized minified etc.'d files for nginx container to use?


Ensure TC breakage pings #allennlp-alerts

Minimally http://build.allennlp.org/viewType.html?buildTypeId=AllenNLPHub_Master, maybe also http://build.allennlp.org/viewType.html?buildTypeId=AllenNLPHub_Release.
We have this set up for the main repo, but I can't find where the configuration lives in TC or Slack.

@schmmd, could you comment on this when you get a chance?


Error: timeout while waiting for plugin to start

I've noticed about a dozen jobs failing with this error that happens right during provisioning of the gitlab runner.
Example: https://gitlab.com/osbuild/ci/osbuild-composer/-/jobs/1408715258
Opening this for tracking purposes to see if it's just temporary issue or something worth looking into.

It was probably just a transient error, I have never seen it since, closing.


Change active window/zone with keyboard

Description of the new feature / enhancement
With FancyZones if there would be a way to use a keyboard shortcut to move the active zone to another zone without needing to use the mouse, Alt+Tab or Win+Tab and without having to switch the active window to a different zone, change to the other window in the zone and then move it back to the original zone.
Something like Win+Alt+{<,>,∧,∨} to change focus to the window / zone in whichever direction selected.
Scenario when this would be used?
This would  be useful to navigate between windows / zones that are visibly side by side (or above/below) without having to use the mouse, or use Alt+Tab (or Win+Tab) to select the window.
I would use this when I have a chat open in one window, a browser in another, and an editor in another all on the same screen in different zones (or any other windows like file explorer etc.)
I feel like this could speed up and improve workflow for almost anyone.

It's nice being able to move the windows to other zones conveniently with Win+{<,>} or Win+{<,>,∧,∨} and then switching between windows in the same zone with Win+{pgup,pgdown}, but it would be ideal to be able to switch between windows in different zones without having them move around or without having to use mouse / Alt+Tab / Win+Tab

If I might add, a small colored outline to the currently focused zone would be a nice visual cue as well, especially when changing focus with only keyboard hotkeys.

Hi CaioLC, I will be closing this as a /dup of #492


Document how to restore or rebuild the Foreseti VM

In the case that we lose the VM, or the customer has a requirement to run an up-to-date instance every N weeks.

Issue Review: Documentation issue.

This will also need to include how to handle and manage the gsuite_reader service account key, which is currently not saved somewhere shared: i.e. currently only saved on the vm, and the original installer's cloud shell.
It would be nice, if we have a tool that can handle this automatically.

The key is only stored on the VM. It gets deleted from the cloud shell.

Linking issue #856

Per andrew: an instance template with an instance manager may help with a new VM built every N days automatically.

Per Carise: Could break this out into different installer modules.


arm64: changing the startup of arm64 SMP from serial to parallel

Summary
arm64: changing the startup of arm64 SMP from serial to parallel
Impact
arm64
Testing
ostest

[Experimental Bot, please feedback here]
No, this PR does not meet the NuttX requirements.
Here's why and what needs improvement:

Insufficient Summary:

Missing "Why":  You haven't explained why changing the SMP startup from serial to parallel is necessary.  What problem does it solve? What are the benefits (e.g., performance improvement)?
Lack of Detail: "changing the startup" is very vague. Be specific about what code is modified and how the parallel startup mechanism works.
Missing References: Are there related issues in the NuttX or NuttX Apps repositories?

Incomplete Impact Assessment:

Limited Scope: Simply stating "arm64" doesn't provide enough information. Specify the impact on:

Architectures: Does this only affect arm64?
Boards: Are any specific boards affected more than others?
Drivers:  Are there driver implications?

Missing Details:  You need to address all other impact points (user impact, build process, documentation, security, compatibility).  Even if the answer is "NO," state it explicitly.

Inadequate Testing:

Vague Host/Target: "ostest" is not descriptive enough. Provide details about:

Build Host: Your operating system, CPU architecture, compiler version.
Target: The specific ARM64 architecture, board, and configuration you tested on.

Missing Logs: You need to include actual testing logs from before and after your changes. This demonstrates how the change works and helps reviewers verify its correctness.

To improve your PR:

Expand your Summary: Provide a clear and concise explanation of the change's purpose, functionality, and any relevant issue references.
Complete the Impact Assessment: Address all impact points with specific details, even if the impact is minimal or non-existent.
Provide Detailed Testing Information:  Include your build host and target details along with actual testing logs.


Linux distro with UTF-8 characters in lsb_release breaks homebrew-bundle lockfile generation

brew config output
HOMEBREW_VERSION: 3.3.9
ORIGIN: https://github.com/Homebrew/brew
HEAD: 96137bc19e68398ebbb7033379df288cd8b9a3f9
Last commit: 3 weeks ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 8bdba997f6c32cdd556b2ef21a619adf662f561a
Core tap last commit: 63 minutes ago
Core tap branch: master
HOMEBREW_PREFIX: /home/linuxbrew/.linuxbrew
HOMEBREW_CASK_OPTS: ["--appdir=/dev/null", "--fontdir=/home/colin/.fonts"]
HOMEBREW_CORE_GIT_REMOTE: https://github.com/Homebrew/homebrew-core
HOMEBREW_DISPLAY: :0
HOMEBREW_EDITOR: vim
HOMEBREW_MAKE_JOBS: 12
Homebrew Ruby: 2.6.8 => /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.8/bin/ruby
CPU: dodeca-core 64-bit zen
Clang: N/A
Git: 2.25.1 => /bin/git
Curl: 7.68.0 => /bin/curl
Kernel: Linux 5.11.0-44-generic x86_64 GNU/Linux
OS: elementary OS 6.1 Jólnir (jolnir)
Host glibc: 2.31
/usr/bin/gcc: 9.3.0
/usr/bin/ruby: 2.7.0
glibc: N/A
gcc@5: N/A
xorg: N/A

brew doctor output
Your system is ready to brew.

Verification

[X] I ran brew update and am still able to reproduce my issue.
[X] I have resolved all warnings from brew doctor and that did not fix my problem.

What were you trying to do (and why)?
I was trying to install a very simple Brewfile:
brew "docker-compose"
brew "rsstail"

What happened (include all command output)?
hit an error.
Skipping rsstail (no bottle for Linux)
Skipping rsstail (no bottle for Linux)
Error: "\xC3" from ASCII-8BIT to UTF-8
Please report this bug:
  https://github.com/Homebrew/homebrew-bundle/issues
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.8/lib/ruby/2.6.0/json/common.rb:286:in `encode'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.8/lib/ruby/2.6.0/json/common.rb:286:in `generate'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.8/lib/ruby/2.6.0/json/common.rb:286:in `pretty_generate'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/homebrew/homebrew-bundle/lib/bundle/locker.rb:76:in `lock'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/homebrew/homebrew-bundle/lib/bundle/installer.rb:64:in `install'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/homebrew/homebrew-bundle/lib/bundle/commands/install.rb:10:in `run'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/homebrew/homebrew-bundle/cmd/bundle.rb:94:in `bundle'
/home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/brew.rb:110:in `<main>'

What did you expect to happen?
Run to completion, installing my dependencies.
Step-by-step reproduction instructions (by running brew commands)
I summarized it and my debugging here: https://github.com/Homebrew/homebrew-bundle/issues/1043

The trick is running this on elementaryOS 6.1, which has an LSB description that includes an acute `o`.

I've traced it down to how Ruby handles reading the output of lsb_release when it gets the release version information:
https://github.com/Homebrew/brew/blob/7fc2159fcddd1deed70d2a7225d34750f080160b/Library/Homebrew/os/linux.rb#L14-L20
which calls
https://github.com/Homebrew/brew/blob/7fc2159fcddd1deed70d2a7225d34750f080160b/Library/Homebrew/utils/popen.rb#L8-L13
In Ruby 2.7 installed from distro repos:
a = IO.popen("lsb_release -a", "r")
l = a.readlines
p l
p l.map(&:encoding)

outputs:
["Distributor ID:\tElementary\n", "Description:\telementary OS 6.1 Jólnir\n", "Release:\t6.1\n", "Codename:\tjolnir\n"]
[#<Encoding:UTF-8>, #<Encoding:UTF-8>, #<Encoding:UTF-8>, #<Encoding:UTF-8>]

but
a = IO.popen("lsb_release -a", "rb")
l = a.readlines
p l
p l.map(&:encoding)

Outputs:
["Distributor ID:\tElementary\n", "Description:\telementary OS 6.1 J\xC3\xB3lnir\n", "Release:\t6.1\n", "Codename:\tjolnir\n"]
[#<Encoding:ASCII-8BIT>, #<Encoding:ASCII-8BIT>, #<Encoding:ASCII-8BIT>, #<Encoding:ASCII-8BIT>]

Ruby's JSON encoder tries to convert the ASCII-8BIT string to UTF-8 and fails because that's dangerous.
As I said in the linked issue on the homebrew-bundle repo, a solution may be to force the encoding or not read this particular call in binary mode (popen(cmd, 'r') instead of 'rb') when we're expecting UTF-8 data.


Can't get Let's Encrypt certificates to work

Describe Your Goal
I want to convert my valid let's encrypt certificate to the correct DER format to use it on the HTTPS Async example
What Does Your Project Look Like
The example HTTPS Async sketch with only the cert.h and private_key.h replaced. I got the following files from Let's Encrypt:

cert.pem
chain.pem
fullchain.pem
privkey.pem

I have tried the following commands with varying level of success to generate the example.crt.DER which then gets converted to cert.h with xxd:

openssl x509 -in fullchain.pem -outform DER -out example.crt.DER
openssl x509 -in cert.pem -outform DER -out example.crt.DER
opening a properly configured Apache webserver with the certificate and then download the certificate with chrome and saving it as DER file. (I have tried it at the root level as well as only on the domain level)

I test using curl -v which always fails at :

ALPN, offering h2
ALPN, offering http/1.1
successfully set certificate verify locations:
CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
TLSv1.3 (OUT), TLS handshake, Client hello (1):
TLSv1.3 (IN), TLS handshake, Server hello (2):
TLSv1.2 (IN), TLS handshake, Certificate (11):
TLSv1.2 (OUT), TLS alert, unknown CA (560):
SSL certificate problem: unable to get local issuer certificate
Closing connection 0
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.haxx.se/docs/sslcerts.html

And using the chrome exported certificate from the root level it fails at:

ALPN, offering h2
ALPN, offering http/1.1
successfully set certificate verify locations:
CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
TLSv1.3 (OUT), TLS handshake, Client hello (1):
TLSv1.3 (IN), TLS handshake, Server hello (2):
TLSv1.2 (IN), TLS handshake, Certificate (11):
TLSv1.2 (IN), TLS handshake, Server key exchange (12):
TLSv1.2 (OUT), TLS alert, decrypt error (563):
error:0407008A:rsa routines:RSA_padding_check_PKCS1_type_1:invalid padding
Closing connection 0
curl: (35) error:0407008A:rsa routines:RSA_padding_check_PKCS1_type_1:invalid padding

So how do I convert let's encrypt certificated properly? The example.key.DER was produced using the following command:
openssl rsa -in privkey.pem -outform DER -out example.key.DER
ESP32 Module
ESP32 Dev Module breakout board, no RAM addon or anything fancy
Software (please complete the following information if applicable)

IDE and Version:  Arduino 1.8.12
OS: Ubuntu 20.4
Client used to access the server: curl 7.68.0

Sorry for the late reply. If I remember correctly, using the full chain will not work, only the last certificate that is the one you want to use with the server, and for which you have the matching private key.
So this should be the correct syntax if you have a cert.pem file:
# check the certificate, only a single certificate should be shown (not a chain):
openssl x509 -inform pem -in cert.pem -text
# Convert the certificate
openssl x509 -in cert.pem -outform DER -out cert.der
# Check the converted certificate (output should be the same as for the first command)
openssl x509 -inform der -in cert.der -text

For the private key (in .pem format) to the following. Make sure you actually have an RSA key. EC won't work with the server.
openssl rsa -in cert.key -outform der -out cert.key.der

As a last step, you can verify that your private key and certificate in the DER files do match:
# Get modulus of the key
openssl rsa -modulus -noout -in cert.key.der -inform der | openssl sha256
# Get modulus of the cert
openssl x509 -modulus -noout -in cert.der -inform der | openssl sha256

If both commands show the same output, the files should be okay and that should not be the problem.
What might be an issue though is if the intermediate CA used by Let's Encrypt isn't known to your browser (or curl, respectively). In that case, you would have a working certificate presented by the ESP32, but the client isn't able to verify it. These lines from your test with curl look like that could indeed be the problem:
TLSv1.2 (OUT), TLS alert, unknown CA (560):
SSL certificate problem: unable to get local issuer certificate

Does curl --insecure [...] solve the problem? In that case, curl would ignore being not able to validate the certificate, but at least we would see that the certificate as such was deployed correctly. In that case, I'd convert this issue into a feature request to support certificate chains delivered by the server.

Thank you for the answer, I will test it on the weekend :-)

Ok I finally got around to test it today with the commands you gave me. Sadly curl still shows the same error message. When using curl with --insecure it works.
* TCP_NODELAY set
* Connected to [Censored my DNS Name] port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server did not agree to a protocol
* Server certificate:
*  subject: CN=[Censored my DNS Name]
*  start date: Jun 20 16:17:11 2020 GMT
*  expire date: Sep 18 16:17:11 2020 GMT
*  issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
*  SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
> GET / HTTP/1.1

So thank you very much for your effort :) Sad that this is probably nothing we / you could fix. So I am closing this issue now, have a nice weekend and thank you for the awesome project!

Thanks for checking that! If curl --insecure works but says SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway., that indeed sounds like a problem with the certificate chain, not the certificate itself. I created #93 to track work on that.


flush  buffer

Summary
I did not see ask_question on MinGW, so I added $stdout.flush.

Thanks for the PR! This looks good so far. I don't see a need for a test, but could you add a CHANGELOG entry as suggested above?

Thank you for your reply ❗
I added changelog so please watch it.

Thanks! 🙌


updating package json

I tried to update package.json by running the npm-check-updates tool (aka ncu -a) and now the task runner fails when trying to install or run the development task.
I have tried rolling the package.json file back and deleting node_modules and so far still failure. The template is neat, but seems delicate.
My question is, what is the best way to update the package.json file with latest packages for all. Or are some packages, such as the one made by the team, have dependencies that cannot be updated?

You can update the package version numbers in the package.json and then run npm install --save using the  node command line in that directory.  You will probably need to make sure that you run the command line as Administrator.

My question is, what is the best way to update the package.json file with latest packages for all?

I think this is the key point.    Sure you can update the packages in package.json but it will likely break the app.  Try updating to React 16 and it won't even compile.  You can't even update some of the @types a single version.  What if you want to use the latest webpack?
We need a strategy for this and a tool would be even better.
 Until the template and its dependencies can be updated separately, this project is really only a neat example of what is possible. Otherwise not too practical or cutting edge. For now I have seperated my AspNetCore Web API from the front-end using a starter package. I think I am using this one: https://github.com/angularclass/angular-starter .It did allow me to update all packages using npm check updates.

You can update your third-party dependencies at any time, but if newer versions introduce breaking changes, you would have to find solutions or not update those packages. I know it would be better if third-party packages never introduced breaking changes, but that's not something any of us can control I'm afraid! Sorry it's not easier.


Release 1.7.8

Codecov Report
Attention: Patch coverage is 32.69231% with 35 lines in your changes are missing coverage. Please review.

Project coverage is 79.32%. Comparing base (bef9555) to head (b3f73b9).
Report is 3 commits behind head on main.

Files
Patch %
Lines

eogrow/utils/testing.py
41.46%
24 Missing :warning:

eogrow/pipelines/download_batch.py
0.00%
11 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #339      +/-   ##
==========================================
- Coverage   79.72%   79.32%   -0.40%
==========================================
  Files          49       49
  Lines        3738     3773      +35
==========================================
+ Hits         2980     2993      +13
- Misses        758      780      +22

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


Refactor official docs

This is exactly #1219, just taking a longer route through #1222.

First of all, this is a vast improvement on our existing documentation @MasterSkepticista. Very well done!
I had to disable warnings on build, but here's a live version on ReadTheDocs:
https://openfl.readthedocs.io/en/karansh1-docs/index.html
A couple issues (I realize that not all of these were caused by this PR):

The Contributing link is broken from the Overview page
Guide link is broken on Quickstart:
image.png link is broken on MNIST Example: Workflow API
On https://openfl.readthedocs.io/en/karansh1-docs/about/features_index/workflowinterface.html

Features link is broken

https://openfl.readthedocs.io/en/karansh1-docs/about/features_index/privacy_meter.html
On the Privacy Meter page

Here link is broken

Hijacking this PR to also note that the Director-Envoy Communication mermaid diagram isn't very clear in dark mode.

Thanks for the feedback @theakshaypant. Addressed relevant items.
Remainder, will be part of future PRs. Some of it is simple deletion of deprecated API docs, and remainder needs rewrite + restructuring, as the scope here was to get the ball rolling.

First of all, this is a vast improvement on our existing documentation @MasterSkepticista. Very well done!
I had to disable warnings on build, but here's a live version on ReadTheDocs:
https://openfl.readthedocs.io/en/karansh1-docs/index.html
A couple issues (I realize that not all of these were caused by this PR):

The Contributing link is broken from the Overview page

Guide link is broken on Quickstart:

image.png link is broken on MNIST Example: Workflow API

On https://openfl.readthedocs.io/en/karansh1-docs/about/features_index/workflowinterface.html

Features link is broken

https://openfl.readthedocs.io/en/karansh1-docs/about/features_index/privacy_meter.html

On the Privacy Meter page

Here link is broken

Addressed most. The only ones I cannot test right now, are notebook URLs. They cannot be relative to the docs, only complete URLs, AFAIU. I have updated the links to be what they "will be" post-merge. We will do hotfixes if necessary.

These are great improvements, thank you @MasterSkepticista ! My only suggestion is to consider removing the duplication of the link to the Quickstart in the index (left menu). By the way, the Quickstart page takes quite a while to load (could it be because it's present twice in the index)?

@theakshaypant had a similar https://github.com/securefederatedai/openfl/pull/1223#discussion_r1891039557. Since this concern has appeared twice, I have made relevant changes in https://github.com/securefederatedai/openfl/pull/1223/commits/b73d487afa8d207daa4bf4077da72cbdfeb29358
@teoparvanov on your second question: I don't see any lag on loading the quickstart. This may be due to this being a dev build, or network issues.


2022-03-21: Fix GitHub Pull Request URLs

I'm not allowed to git push:
ERROR: Permission to Rust-GCC/Reporting.git denied to tschwinge.

..., so please manually git am the attached file, "2022-03-21: Fix GitHub Pull Request URLs".
0001-2022-03-21-Fix-GitHub-Pull-Request-URLs.patch.txt

@philberty independently fixed the GitHub Pull Request URLs in commit 68bcec2d44e372af3c1aa6edd4830fda6d6e6d41 "Fix url for links to PRs".


newly created resources don't show up in search

on stage and on dev, create a new description that has a title.
the new resource does not show up in search results.
examples of resources that should be found in search:
https://trellis.stage.sinopia.io/repository/stanford/c2ea4e49-8399-4459-9088-bd9f1688d9af
https://trellis.development.sinopia.io/repository/stanford/382b2f5e-fb2a-4f2d-a639-c709505021bb

Dupe of https://github.com/LD4P/sinopia_indexing_pipeline/issues/41


Fix 'Animated images' demo name in Gallery's test.

In https://github.com/flutter/flutter/pull/13141 I updated the demo name
from 'Animated Images' to 'Animated images' before submitted, but did
not update the name in the smoketest and transitions_perf test.


Properly implement caches (Party, Lobby, PartyInvite), handle ClientHello more gracefully

This pull request fixes issues #32 #39 #54 #61 #63 #65 ... aka most of the issues on this repo.

I also didn't mention... I changed the generate_protos script to pull http://github.com/paralin/dota2 which is always up to date with the latest protos and is a far smaller repository.

Great work :D  Thanks


Setup pipeline for binary releases (Windows, macOS, Linux)

Building binary releases is a great way to improve adoption. Before this, versioning (#7) needs to be specified.

Done! :) Works ok, I feel I'm very unfamiliar with GitHub Actions, but there's (naturally) a lot of overlap coming from DevOps pipelines.


Switch to cargo nextest as test runner

Summary of changes
Changes introduced in this pull request:

Changes to Makefile to use cargo nextest as test runner

Reference issue to close (if applicable)

Closes #2040
Other information and links

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.creativcoder seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Updated README.md


Remove sidebar

No longer needed as pages can be accessed from search/location and profile pages.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.07%) to 46.746%

Totals

Change from base Build<PHONE_NUMBER>:
-0.07%

Covered Lines:
325

Relevant Lines:
574

💛  - Coveralls


Mark redis policy tests as flaky

These tests fail almost all of the time and hide real failures as a result (mixer tests always fail, so I don't even both looking at them).
Opened an issue to track these at https://github.com/istio/istio/issues/15686

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: howardjohn
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

tests/integration/mixer/OWNERS [howardjohn]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@howardjohn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

istio-lint-master
9c7d212b4de7ee16524df355f9bd1969ba7edd50
link
/test istio-lint-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

istio-lint-master
9c7d212b4de7ee16524df355f9bd1969ba7edd50
link
/test istio-lint-master

integ-mixer-local-presubmit-tests-master
363a93b9e4fc1e2d56c14953b597aae3b78c317d
link
/test integ-mixer-local-presubmit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-local-presubmit-tests-master
363a93b9e4fc1e2d56c14953b597aae3b78c317d
link
/test integ-mixer-local-presubmit-tests-master

istio-lint-master
363a93b9e4fc1e2d56c14953b597aae3b78c317d
link
/test istio-lint-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-local-presubmit-tests-master
363a93b9e4fc1e2d56c14953b597aae3b78c317d
link
/test integ-mixer-local-presubmit-tests-master

istio-lint-master
363a93b9e4fc1e2d56c14953b597aae3b78c317d
link
/test istio-lint-master

istio-codecov-master
363a93b9e4fc1e2d56c14953b597aae3b78c317d
link
/test istio-codecov-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

istio-racetest-master
8c8b14ecdcdd1317c4a52a693b0a6831ee9fde74
link
/test istio-racetest-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/lgtm

@howardjohn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

istio-racetest-master
8c8b14ecdcdd1317c4a52a693b0a6831ee9fde74
link
/test istio-racetest-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Custom functions

Applications that embed sqlite can define custom functions.
sqlite3 supports custom functions through createFunction and createAggregateFunction.
This would be very much a non-trivial very useful feature yet probably not horrible to implement (particularly as it can be cribbed from sqlite3).

The thing is that drift supports other implementations too (outside of package:sqlite3). For instance, we have an implementation that uses sqflite internally and there's experimental support for postgres too. So we can't have generalized support for custom functions since the different implementations have varying support for them.
The NativeDatabase constructors have a setup parameter which you can use to prepare the database before drift starts using it. This is a good place to register custom functions:
NativeDatabase(
  File('/foo/bar'),
  setup: (rawDb) {
    rawDb.createAggregateFunction(
      functionName: 'sumint',
      function: _SumInt(),
      argumentCount: const AllowedArgumentCount(1),
   );
  }
)


Event Request: "Reservation Management": GetSourceRecordValue

In Codeunit 99000845 "Reservation Management" there is a function GetSourceRecordValue. This function is calling the event OnGetSourceRecordValue to which various "[TableName]-Reserve" Codeunits subscribe to in order to provide the source quantity. This event has a few issues:

it does not implement the handled pattern. As such, I can not know if anyone already handled a given table.
I cannot add custom handlers for a specific scenario, because I cannot know if my handler comes before or after the ones from the base app.

I therefore suggest:

Add the Handled-Pattern to this event.
Provide a new event in the function GetSourceRecordValue that is called right after OnGetSourceRecordValue. Something like
OnAfterGetSourceRecordValue(var ReservEntry, var SetAsCurrent, ReturnOption, var SourceQty, vat SourceRecRef);

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


terraform plan crash report

I did not touch my terragrunt config, but somehow, it seems got crashed by itself when I run it today.
Below is the crash log
[terragrunt] 2018/11/09 20:04:30 Error with plan: [terragrunt] [<project>/aws/eks] 2018/11/09 20:04:19 Initializing remote state for the s3 backend
[terragrunt] [<project>/aws/eks] 2018/11/09 20:04:19 Running command: terraform init -backend-config=bucket=<project>.tf-states -backend-config=key=aws/eks/terraform.tfstate -backend-config=region=us-east-1 -backend-config=encrypt=true -backend-config=dynamodb_table=<project>.tf-lock-table
Initializing modules...
- module.vpc
  Found version 1.14.0 of terraform-aws-modules/vpc/aws on registry.terraform.io
  Getting source "terraform-aws-modules/vpc/aws"
- module.eks
  Found version 1.7.0 of terraform-aws-modules/eks/aws on registry.terraform.io
  Getting source "terraform-aws-modules/eks/aws"
Initializing the backend...
Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.
Initializing provider plugins...
- Checking for available provider plugins on https://releases.hashicorp.com...
- Downloading plugin for provider "aws" (1.43.1)...
- Downloading plugin for provider "template" (1.0.0)...
- Downloading plugin for provider "local" (1.1.0)...
- Downloading plugin for provider "null" (1.0.0)...
The following providers do not have any version constraints in configuration,
so the latest version was installed.
To prevent automatic upgrades to new major versions that may contain breaking
changes, it is recommended to add version = "..." constraints to the
corresponding provider blocks in configuration, with the constraint strings
suggested below.
* provider.local: version = "~> 1.1"
* provider.null: version = "~> 1.0"
* provider.template: version = "~> 1.0"
Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
Error: Error refreshing state: 8 error(s) occurred:
* module.eks.aws_iam_role_policy_attachment.workers_autoscaling: 1 error(s) occurred:
* module.eks.aws_iam_role_policy_attachment.workers_autoscaling: aws_iam_role_policy_attachment.workers_autoscaling: unexpected EOF
* module.eks.aws_launch_configuration.workers: 1 error(s) occurred:
* module.eks.aws_launch_configuration.workers: aws_launch_configuration.workers: unexpected EOF
* module.eks.aws_iam_role_policy_attachment.workers_AmazonEC2ContainerRegistryReadOnly: 1 error(s) occurred:
* module.eks.aws_iam_role_policy_attachment.workers_AmazonEC2ContainerRegistryReadOnly: aws_iam_role_policy_attachment.workers_AmazonEC2ContainerRegistryReadOnly: unexpected EOF
* aws_iam_role_policy_attachment.worker_node_external_dns_policy: 1 error(s) occurred:
* aws_iam_role_policy_attachment.worker_node_external_dns_policy: aws_iam_role_policy_attachment.worker_node_external_dns_policy: unexpected EOF
* module.eks.aws_iam_role_policy_attachment.workers_AmazonEKSWorkerNodePolicy: 1 error(s) occurred:
* module.eks.aws_iam_role_policy_attachment.workers_AmazonEKSWorkerNodePolicy: aws_iam_role_policy_attachment.workers_AmazonEKSWorkerNodePolicy: unexpected EOF
* module.eks.aws_security_group_rule.cluster_https_worker_ingress: 1 error(s) occurred:
* module.eks.aws_security_group_rule.cluster_https_worker_ingress: aws_security_group_rule.cluster_https_worker_ingress: unexpected EOF
* module.eks.aws_security_group_rule.workers_ingress_self: 1 error(s) occurred:
* module.eks.aws_security_group_rule.workers_ingress_self: aws_security_group_rule.workers_ingress_self: unexpected EOF
* module.eks.aws_security_group_rule.workers_egress_internet: 1 error(s) occurred:
* module.eks.aws_security_group_rule.workers_egress_internet: aws_security_group_rule.workers_egress_internet: unexpected EOF
panic: runtime error: invalid memory address or nil pointer dereference
2018-11-09T20:04:30.459Z [DEBUG] plugin.terraform-provider-aws_v1.43.1_x4: [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x235739c]
2018-11-09T20:04:30.459Z [DEBUG] plugin.terraform-provider-aws_v1.43.1_x4:
2018-11-09T20:04:30.459Z [DEBUG] plugin.terraform-provider-aws_v1.43.1_x4: goroutine 580 [running]:
2018-11-09T20:04:30.459Z [DEBUG] plugin.terraform-provider-aws_v1.43.1_x4: github.com/terraform-providers/terraform-provider-aws/aws.findRuleMatch(0xc00054ef80, 0xc0009b34e0, 0x3, 0x3, 0x1, 0x0)
2018-11-09T20:04:30.459Z [DEBUG] plugin.terraform-provider-aws_v1.43.1_x4: 	/opt/teamcity-agent/work/5d79fe75d4460a2f/src/github.com/terraform-providers/terraform-provider-aws/aws/resource_aws_security_group_rule.go:433 +0x6c
2018-11-09T20:04:30.459Z [DEBUG] plugin.terraform-provider-aws_v1.43.1_x4: github.com/terraform-providers/terraform-provider-aws/aws.resourceAwsSecurityGroupRuleRead(0xc0005b6310, 0x2c5ea40, 0xc00022e300, 0xc0005b6310, 0x0)
2018-11-09T20:04:30.459Z [DEBUG] plugin.terraform-provider-aws_v1.43.1_x4: 	/opt/teamcity-agent/work/5d79fe75d4460a2f/src/github.com/terraform-providers/terraform-provider-aws/aws/resource_aws_security_group_rule.go:286 +0x5fd
2018-11-09T20:04:30.459Z [DEBUG] plugin.terraform-provider-aws_v1.43.1_x4: github.com/terraform-providers/terraform-provider-aws/vendor/github.com/hashicorp/terraform/helper/schema.(*Resource).Refresh(0xc0003c9ea0, 0xc000094f50, 0x2c5ea40, 0xc00022e300, 0xc00000fdd0, 0x4bfe01, 0x273d220)
2018-11-09T20:04:30.459Z [DEBUG] plugin.terraform-provider-aws_v1.43.1_x4: 	/opt/teamcity-agent/work/5d79fe75d4460a2f/src/github.com/terraform-providers/terraform-provider-aws/vendor/github.com/hashicorp/terraform/helper/schema/resource.go:352 +0x160
2018-11-09T20:04:30.459Z [DEBUG] plugin.terraform-provider-aws_v1.43.1_x4: github.com/terraform-providers/terraform-provider-aws/vendor/github.com/hashicorp/terraform/helper/schema.(*Provider).Refresh(0xc000508ee0, 0xc000094eb0, 0xc000094f50, 0xc000062700, 0xc000bb4c20, 0x7f0a45c196c0)
2018-11-09T20:04:30.459Z [DEBUG] plugin.terraform-provider-aws_v1.43.1_x4: 	/opt/teamcity-agent/work/5d79fe75d4460a2f/src/github.com/terraform-providers/terraform-provider-aws/vendor/github.com/hashicorp/terraform/helper/schema/provider.go:308 +0x92
2018-11-09T20:04:30.459Z [DEBUG] plugin.terraform-provider-aws_v1.43.1_x4: github.com/terraform-providers/terraform-provider-aws/vendor/github.com/hashicorp/terraform/plugin.(*ResourceProviderServer).Refresh(0xc00058b1a0, 0xc0006bd4d0, 0xc0006bd5c0, 0x0, 0x0)
2018-11-09T20:04:30.459Z [DEBUG] plugin.terraform-provider-aws_v1.43.1_x4: 	/opt/teamcity-agent/work/5d79fe75d4460a2f/src/github.com/terraform-providers/terraform-provider-aws/vendor/github.com/hashicorp/terraform/plugin/resource_provider.go:549 +0x4e
2018-11-09T20:04:30.459Z [DEBUG] plugin.terraform-provider-aws_v1.43.1_x4: reflect.Value.call(0xc00007f260, 0xc000140848, 0x13, 0x31d66b8, 0x4, 0xc0000a3f18, 0x3, 0x3, 0xc000ae38c0, 0xc000152500, ...)
2018-11-09T20:04:30.459Z [DEBUG] plugin.terraform-provider-aws_v1.43.1_x4: 	/opt/goenv/versions/1.11.1/src/reflect/value.go:447 +0x449
2018-11-09T20:04:30.459Z [DEBUG] plugin.terraform-provider-aws_v1.43.1_x4: reflect.Value.Call(0xc00007f260, 0xc000140848, 0x13, 0xc00005c718, 0x3, 0x3, 0x5d464b, 0xc00005c728, 0x1000000000001)
2018-11-09T20:04:30.459Z [DEBUG] plugin.terraform-provider-aws_v1.43.1_x4: 	/opt/goenv/versions/1.11.1/src/reflect/value.go:308 +0xa4
2018-11-09T20:04:30.459Z [DEBUG] plugin.terraform-provider-aws_v1.43.1_x4: net/rpc.(*service).call(0xc00046cac0, 0xc000094f00, 0xc00096b4b0, 0xc00096b4c0, 0xc000155180, 0xc00031c4e0, 0x273d1e0, 0xc0006bd4d0, 0x16, 0x273d220, ...)
2018-11-09T20:04:30.459Z [DEBUG] plugin.terraform-provider-aws_v1.43.1_x4: 	/opt/goenv/versions/1.11.1/src/net/rpc/server.go:384 +0x14e
2018-11-09T20:04:30.459Z [DEBUG] plugin.terraform-provider-aws_v1.43.1_x4: created by net/rpc.(*Server).ServeCodec
2018-11-09T20:04:30.459Z [DEBUG] plugin.terraform-provider-aws_v1.43.1_x4: 	/opt/goenv/versions/1.11.1/src/net/rpc/server.go:481 +0x47e
2018/11/09 20:04:30 [ERROR] root.eks: eval: *terraform.EvalRefresh, err: aws_iam_role_policy_attachment.workers_autoscaling: unexpected EOF
2018/11/09 20:04:30 [ERROR] root.eks: eval: *terraform.EvalSequence, err: aws_iam_role_policy_attachment.workers_autoscaling: unexpected EOF
2018/11/09 20:04:30 [TRACE] [walkRefresh] Exiting eval tree: module.eks.aws_iam_role_policy_attachment.workers_autoscaling
2018/11/09 20:04:30 [ERROR] root.eks: eval: *terraform.EvalRefresh, err: aws_iam_role_policy_attachment.workers_AmazonEKSWorkerNodePolicy: unexpected EOF
2018/11/09 20:04:30 [ERROR] root.eks: eval: *terraform.EvalSequence, err: aws_iam_role_policy_attachment.workers_AmazonEKSWorkerNodePolicy: unexpected EOF
2018/11/09 20:04:30 [TRACE] [walkRefresh] Exiting eval tree: module.eks.aws_iam_role_policy_attachment.workers_AmazonEKSWorkerNodePolicy
2018/11/09 20:04:30 [ERROR] root.eks: eval: *terraform.EvalRefresh, err: aws_launch_configuration.workers: unexpected EOF
2018/11/09 20:04:30 [ERROR] root.eks: eval: *terraform.EvalSequence, err: aws_launch_configuration.workers: unexpected EOF
2018/11/09 20:04:30 [TRACE] [walkRefresh] Exiting eval tree: module.eks.aws_launch_configuration.workers
2018/11/09 20:04:30 [TRACE] dag/walk: upstream errored, not walking "module.eks.aws_autoscaling_group.workers"
2018/11/09 20:04:30 [TRACE] dag/walk: upstream errored, not walking "module.eks.output.workers_asg_names"
2018/11/09 20:04:30 [ERROR] root.eks: eval: *terraform.EvalRefresh, err: aws_security_group_rule.cluster_https_worker_ingress: unexpected EOF
2018/11/09 20:04:30 [ERROR] root.eks: eval: *terraform.EvalSequence, err: aws_security_group_rule.cluster_https_worker_ingress: unexpected EOF
2018/11/09 20:04:30 [TRACE] [walkRefresh] Exiting eval tree: module.eks.aws_security_group_rule.cluster_https_worker_ingress
2018/11/09 20:04:30 [ERROR] root.eks: eval: *terraform.EvalRefresh, err: aws_iam_role_policy_attachment.workers_AmazonEC2ContainerRegistryReadOnly: unexpected EOF
2018/11/09 20:04:30 [ERROR] root.eks: eval: *terraform.EvalSequence, err: aws_iam_role_policy_attachment.workers_AmazonEC2ContainerRegistryReadOnly: unexpected EOF
2018/11/09 20:04:30 [TRACE] [walkRefresh] Exiting eval tree: module.eks.aws_iam_role_policy_attachment.workers_AmazonEC2ContainerRegistryReadOnly
2018/11/09 20:04:30 [ERROR] root: eval: *terraform.EvalRefresh, err: aws_iam_role_policy_attachment.worker_node_external_dns_policy: unexpected EOF
2018/11/09 20:04:30 [ERROR] root: eval: *terraform.EvalSequence, err: aws_iam_role_policy_attachment.worker_node_external_dns_policy: unexpected EOF
2018/11/09 20:04:30 [TRACE] [walkRefresh] Exiting eval tree: aws_iam_role_policy_attachment.worker_node_external_dns_policy
2018/11/09 20:04:30 [ERROR] root.eks: eval: *terraform.EvalRefresh, err: aws_security_group_rule.workers_ingress_self: unexpected EOF
2018/11/09 20:04:30 [ERROR] root.eks: eval: *terraform.EvalSequence, err: aws_security_group_rule.workers_ingress_self: unexpected EOF
2018/11/09 20:04:30 [TRACE] [walkRefresh] Exiting eval tree: module.eks.aws_security_group_rule.workers_ingress_self
2018/11/09 20:04:30 [ERROR] root.eks: eval: *terraform.EvalRefresh, err: aws_security_group_rule.workers_egress_internet: unexpected EOF
2018/11/09 20:04:30 [ERROR] root.eks: eval: *terraform.EvalSequence, err: aws_security_group_rule.workers_egress_internet: unexpected EOF
2018/11/09 20:04:30 [TRACE] [walkRefresh] Exiting eval tree: module.eks.aws_security_group_rule.workers_egress_internet
2018-11-09T20:04:30.464Z [DEBUG] plugin: plugin process exited: path=<project>/aws/eks/.terraform/plugins/linux_amd64/terraform-provider-aws_v1.43.1_x4
2018/11/09 20:04:30 [TRACE] dag/walk: upstream errored, not walking "module.eks.output.workers_asg_arns"
2018/11/09 20:04:30 [TRACE] dag/walk: upstream errored, not walking "provider.aws (close)"
2018/11/09 20:04:30 [TRACE] dag/walk: upstream errored, not walking "root"
2018/11/09 20:04:30 [DEBUG] plugin: waiting for all plugin processes to complete...
2018-11-09T20:04:30.523Z [WARN ] plugin: error closing client during Kill: err="connection is shut down"
2018-11-09T20:04:30.525Z [DEBUG] plugin: plugin process exited: path=<project>/aws/eks/.terraform/plugins/linux_amd64/terraform-provider-null_v1.0.0_x4
2018-11-09T20:04:30.525Z [DEBUG] plugin: plugin process exited: path=<project>/aws/eks/.terraform/plugins/linux_amd64/terraform-provider-local_v1.1.0_x4
2018-11-09T20:04:30.525Z [DEBUG] plugin.terraform: local-exec-provisioner (internal) 2018/11/09 20:04:30 [ERR] plugin: plugin server: accept unix /tmp/plugin247165509: use of closed network connection
2018-11-09T20:04:30.525Z [DEBUG] plugin.terraform: local-exec-provisioner (internal) 2018/11/09 20:04:30 [DEBUG] plugin: waiting for all plugin processes to complete...
2018-11-09T20:04:30.525Z [DEBUG] plugin: plugin process exited: path=<project>/aws/eks/.terraform/plugins/linux_amd64/terraform-provider-template_v1.0.0_x4
2018-11-09T20:04:30.526Z [DEBUG] plugin: plugin process exited: path=<project>/bin/terraform

Hi @chenrui333 thanks for the bug report! I just ran into the same issue, and it appears that hashicorp pushed a new version of the AWS terraform provider (https://github.com/terraform-providers/terraform-provider-aws/releases), v1.43.1 and there appears to be a bug in it. I just filed an issue there and you can track it there: https://github.com/terraform-providers/terraform-provider-aws/issues/6416
Thanks!

That is good to know. Thanks for confirming it.

Closing issue since the actual bug is in https://github.com/terraform-providers/terraform-provider-aws/issues/6416.


The LeetCode problem number is not the same as LeetHub-2.0

The LeetCode problem number is not the same as LeetHub-2.0
Describe the bug
It seems that LeetCode problem number generated by LeetHub-3.0 is not the same as LeetHub-2.0. For example, when I use LeetHub-2.0 with old UI of LeetCode, I got the correct problem number for the following problems: 1004-max-consecutive-ones-iii and 1234-replace-the-substring-for-balanced-string. But when I use LeetHub-3.0 with new UI of LeetCode, I got the incorrect problem number: 1046-max-consecutive-ones-iii and 1351-replace-the-substring-for-balanced-string.
For problems with small numbers, it seems that LeetHub-3.0 works fine.
Screenshots

No, I think you think LeetCode 2.0 worked, in fact there was the same error there https://github.com/arunbhardwaj/LeetHub-2.0/issues/41 .The id is taken from the id api, not the one that is there. But this is my assumption, I don't have time to look at it yet.

@aystream You are right. Thanks for your feedback. It is not an issue that was introduced with LeetHub-3.0. After checking my private leetcode-solution repo, I can confirm that this issue also occurred with Leetcode-2.0 using the new Leetcode UI.
The issue is due to Leetcode returns a wrong problem id. I found that the returned problem id from problem 1-741 is correct. From problem 743 onwards there are inconsistencies.
Btw we can access the problem id in various ways. One possibility is to read the graphql query. Another way is to read the local Chrome cache value. Please take a look at the screenshot below. We can see that the id for problem 743 is stored incorrectly (stored as 744).
So this is a general leetcode problem over which we have no influence on client side. I think an idea to bypass this issue would be to parse the title and extract the id from there...But this is not a critical issue.

@raphaelheinz
Hi. This issue still occurs in the latest version (v0.0.13). Could you please check?
I'm using the new Leetcode UI.
Github repo

Leethub version

Leetcode UI


Sbc imu

These changes implement the Adafruit BNO055 IMU directly connected to the sbc (Rpi in my case) using I2C.  The IMU data and motor encoder based odom is fused in robot_localization to create a much more robust odom.
Some of the changes in this PR are tangential and were just me trying various settings to clear problems with transform timings and "extrapolation into the future" errors.  Those can be ignore or tweaked as appropriate.  The key changes are in diffbot_control/config, ros-imu-bno055/launch, robot_localization/params, diffbot_description/urdf, and the diffbot_bringup/launch files that now also start the IMU and robot_localization, specifically:  bringup_with_laser_imu.launch and bringup_all.launch.
Hope you find this useful.  Thanks again for diffbot.

Thanks a lot @joeuser846, this looks very promising! I am planning to test it soon and provide detailed feedback to get this merged.


Don't highlight cell outside message bubble (when long press)

Hi everyone!
How can I disable bubble selection when I press outside message bubble? So, basically, now when you long press outside message bubble - it highlights (without menucontroller showing), and i want to remove that behavior.
Thanks for any help!

Thanks @seidju ! 😄
Currently there's no workaround for this behavior. We can investigate this UI bug though.


duplicate modules in presence of proxyquireify

I am having a mocha test suite with two mocha files. They go about doing different things. One of them uses proxyquireify to mock out the http module (and thus get rid of the external calls from the tests). whenever i change
var routeModule  = require("../scripts/ui/mapRoute.js");
to
var routeModule  = proxyquire("../scripts/ui/mapRoute.js", stubs);
ALL of my source modules get loaded/evaluated twice - which is of course undesired.
Is it plausible wrt design? Is it a surprise? Shall i supply evidence? (evidence is hard to supply in my case, so i don't want to waste time if this is a known issue).

This is expected behavior. Proxyquireify manipulates the cache. Depending on how and where you require your files you can get things that are re-evaluated.


Remove 'unkown props' from DOM elements; fixes #16

This is an interesting problem to 'solve', this was the cleanest and most transparent method I could think of. It touches a bunch of files, though.
Another option was just to const {invalidProps, ...everythingElse} = this.props and then <span ...everythingElse> in a one liner. But it would produce a lot of unused consts and would just get pretty messy.
Let me know your thoughts!

Hi, thank you for your interest!
Actually, I was going to replace mixin/StyleComponent.js with simple inheritance first and think about this issue after.
As far as I know there are two opportunities to solve it: use the white list and provide only necessary props to the React.createElement or use the black list and omit unnecessary props.
Mostly that issue appear from using custom props styles and styleName and other props that come from the components level (theme, size and etc). And in the simple cases we can manually set the unwanted properties to undefined: https://babeljs.io/repl/#?evaluate=true&lineWrap=false&presets=es2015%2Creact%2Cstage-2&code=function Link(props) {
  return (
    <a {...props} className%3D{styleName(props)} styleName%3D{undefined} styles%3D{undefined}%2F>
  )%3B%0A%7D (that avoids necessity for another iteration and object creation).
But I'm not sure what's better to use for the other cases.
I'll try to review yours pr at the weekend and may be I'll come with a more thoughtful answer. Thanks


Provide ways to configure alm options

Hi,
I can think of two configuration files at the moment:

A password file for the postgres database connection
A configuration file with options for

HTTP

Port to listen on
Hostname or IP to bind to

In the future:

SSL options:

Certificate
Private Key

Postgres

Host
Port
Username
Password
Password file
Number of connection retries
Time between connection retries

These values are all hardcoded at the moment and we might want to provide mechanisms for providing these options through:

A configuration file
Environment variables
Command line switches

In Go there's a library called viper which we might want to use.

https://github.com/almighty/almighty-core/issues/25

Are we considering external K/V store for configuration? Here are two choices:
https://coreos.com/etcd/docs/latest/
https://www.consul.io/

The main focus here is extracting them to Env variables for now.

@baijum Viper supports that; https://github.com/spf13/viper#remote-keyvalue-store-support possible something to consider for the future, but not atm.

The env. vars should be qualified with some prefix like ALMIGHTY. e.g., ALMIGHTY_POSTGRES_HOST ALMIGHTY_POSTGRES_USERNAME, ALMIGHTY_REDIS_HOST etc.

@baijum I have that covered already through viper.SetEnvPrefix("ALM"). But thanks

@kwk What's the state of this? Need some env variables for user_auth related config as well.

@kwk What's the state of this? Need some env variables for user_auth related config as well.

I have a branch and started working a while ago but lately I was working on coverage. Just let me know what you need.

@kwk I need the 'framework' for reading env vars if you had one going. :)

@aslakknutsen @baijum Since you participated in this issue I'd like to ask you to review PR #274 . Thank you


Add AIX back to CI after full stdlib support

Currently Rust on AIX is still under development and is missing some upstream stdlib implementations causing failed CI tests. Once powerpc64-ibm-aix becomes a tier 2 target, CI can be enabled.

This is specifically about uncommentating this line: https://github.com/tokio-rs/mio/pull/1833/files#diff-b803fcb7f17ed9235f1e5cb1fcd2f5d3b2838429d4368ae4c57ce4436577f03fR155.


Page Panel - Design - Updated UI

Important
THESE COMPS ARE SLIGHTLY OUT OF DATE. Please keep the buttons at the bottom using the same approach as https://github.com/concrete5/concrete5/issues/8479
Before you work on this, make sure you read the following two articles about working UI pull requests for concrete5 version 9:
concrete5 Bedrock: A Foundation for concrete5 and concrete5 Themes
https://documentation.concrete5.org/developers/appendix/concrete5-bedrock-a-foundation-for-concrete5-and-concrete5-themes
Submitting User Interface Pull Requests for concrete5 Version 9
https://documentation.concrete5.org/tutorials/submitting-user-interface-pull-requests-for-concrete5-version-9

@aembler added the updated design above. Let me know if I should also post the spec to this thread, thx!

This was completed with
https://github.com/concrete5/concrete5/pull/8523
and
https://github.com/concrete5/concrete5/pull/8546


Handle manual edits to emulated_hue_ids.json

Description:
I've added and removed a few entities from my setup since starting to use the emulated_hue component. I wanted to remove all references to some of the old stuff, so I manually edited the emulated_hue_ids.json file. This resulted in new entities not being properly added.
With this change, new emulated hue numbers are based off the highest currently numbered entity, not purely off the number of entities in the file. This appears to be the way Hue itself does things.

THanks!


Add Force ipv6 option similar to curl

The request module seems to be only making requests using ipv4. In curl I can add a -6 flag to use ipv6.

Also curious if ipv6 is supported? Is there an option ipv6: true?

Encountered this while testing an app. The server was running on [::1]:666 and when requesting localhost:666, request would not connect to [::1] but always to <IP_ADDRESS>. Might be an error with hosts configuration on my machine, but IPv6 option would be nice nonetheless.

is there any way to use request as curl -6 flag ?


Will "PredictiveAnalysis" web app be released?

@dfoll Will the web app SolutionsWeb\Apps\NationalIntel\PredictiveAnalysis be released? The associated portal item is owned by you. If it's not going to be released that please remove this app folder from the SolutionsWeb\Apps\NationalIntel so it's not shipped with the release. Alternatively, I can remove to another location on the server so it's not included, but you'll have a backup of this files. Thank you.

@dfoll Haven't heard back and it's after the content cutoff so I'm going to move this app outside SolutionsWeb\Apps\NationalIntel. Moved to the following folder on the server:
C:\EricL\TEM2016Release\SolutionsWeb_files_removed_from_release\Apps\NationalIntel
Closing this issue.

@elinz i know it's after the fact, but for what it's worth, that was the correct move...the one owned by me was not intended to be released, as i mentioned on the other issue, that was just a lack of thinking on my part, and didn't think about removing it from solutionsweb


Points are not showing at cluster level

I can see feature counts and the extent polygons are able to be selected/highlighted.
When I zoom to lower zoom levels, the icons appear. I haven't changed any defaults.
I've added two seperate geojson objects into the markerclustergroup variable/object  using the addlayer method and then I add the markerclustergroup to the map object using "map.addLayer(markers);"
Thanks

Hi,
I think you would need to share some of your code for people to be able to help you on that.
A better situation would be to reproduce your issue online, and ideally in a code edition service (like JSBin, Plunker, JSFiddle…).
Furthermore, you should consider asking for help on Stack Overflow: as this library is quite popular, you would receive faster support over there.


Removing heartbeat pipe from ProcessManager

ProcessManager sends heartbeat messages to child processes so that it can kill a child process when the process doesn't respond due to too high GC overhead, deadlock, etc. It was relatively easy to keep the code maintained but because ServerEngine started supporting Windows since #50, having heartbeat doesn't seem worth to make the code a lot more complicated.
Idea here is to remove heartbeat support from ProcessManager. ProcessManager doesn't create a set of pipes to child processes. Thus it doesn't need Windows-specific code (ServerEngine.windows? and Fcntl) any more.
A downside is that the parent process can't notice finish (or crash) of child processes using IO.select. Instead, the parent process needs to use waitpid2 for each process. This means that the parent process takes slightly longer time to notice and restart a child process, or needs another synchronization mechanism (e.g. Thread per child process).

I guess this is relevant vice versa – when the parent process dies, worker processes should be notified about it. For example, in Unicorn and Puma there is EOF sign appears in the pipe between parent and child processes, that OS triggers during the parent process killing. I don't know much about Windows inter-process communication support, but as far as the need for communication exists in one direction (child –> parent ) it's reasonable to think about another direction (parent –> child) too.
I'm concerned about the orphaned children in case of the parent death. It's critical for non-supervised (supervisor: false) server, like in sneakers. Monitoring tool is able to spy only on the parent process due to one pidfile and launches new server process with a new set of worker processes without caring about orphaned.
Cross Reference: "Pidfiles per Sneakers Process"


Patch version bump for fix merged in from PR#215?

Any chance that there could be a new patch release for the fix that was merged in #215 this past December?

Just released<EMAIL_ADDRESS>

Thank you @ayrton!


refactor(AsyncBeanOperationExecutor): let AsyncBeanOperationExecutor inherit DisorderedBeanOperationExecutor to avoid repeated access to the same data source in asynchronous populations (Giee #I82EBG)

…

Codecov Report
Patch coverage: 55.00% and project coverage change: -0.24% :warning:

Comparison is base (0a6cee5) 91.65% compared to head (540f5d1) 91.42%.

Additional details and impacted files
@@             Coverage Diff              @@
##                dev     #158      +/-   ##
============================================
- Coverage     91.65%   91.42%   -0.24%
- Complexity     1368     1379      +11
============================================
  Files           135      135
  Lines          3248     3276      +28
  Branches        309      314       +5
============================================
+ Hits           2977     2995      +18
- Misses          144      153       +9
- Partials        127      128       +1

Files Changed
Coverage Δ

...ne4j/core/executor/AsyncBeanOperationExecutor.java
56.00% <0.00%> (-31.50%)
:arrow_down:

...core/executor/DisorderedBeanOperationExecutor.java
89.47% <100.00%> (+3.75%)
:arrow_up:

... and 2 files with indirect coverage changes

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


Document the 11AM mystery

Newly minted RHEL8 boxes will not get their /etc/subuid updated until 11AM after a rebuild.
podman will not run containers and will get:
ERRO[0000] cannot find UID/GID for user hgv27681: No subuid ranges found for user "hgv27681" in /etc/subuid - check rootless mode in man pages.
WARN[0000] Using rootless single mapping into the namespace. This might break some images. Check /etc/subuid and /etc/subgid for adding sub*ids if not using a network user

fixed in 2.0.4


Media links processing

A chunk of my content feed via my content publisher system goes along with media (mostly images).
Sometimes the media attachments contain a significant amount of context that may be lost with text only compilation.
So, it's better to include media. However,the feed is already cluttered with text and it could be tricky to place media in current context.
This needs to be worked on.

One improvement could be anchor text describing the content of media (alt text) with link to media off-site.

Now the context isn't completely lost to the keen eye 😉


Please add live MS Teams alert so that assignee will know that they are tagged in the live components. Alert in email is not too helpful!

[Enter feedback here]

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

ID: 62fa48ba-86fc-85d1-4f32-c22f862536ff
Version Independent ID: 778b3266-914d-db5f-d7df-66bda022d65c
Content: Manage live components in Teams - Microsoft Teams
Content Source: Teams/live-components-in-teams.md
Service: msteams
GitHub Login: @HowlinWolf-92
Microsoft Alias: v-mahoffman

Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


Timestamp Error

The integration stopped working for me a few days ago.
In the logs

I have tried

Resetting my developer key in open api as this has worked before
Reloading the integration
Removing and reinstalling the integration (now I can't add it again)

All successful api calls in postman so I don't think its an issue with the alpha api.

Is there a chance that your HAOS machine is out of sync of time? only reason you would be receiving that error is when (according to the docs) "the timespan between request timestamp and server timestamp exceeds 300 seconds"

I've also tried changing the HA Time Zone to GMT (no daylight saving) in case that caused the incorrect time and then back again to GMT London.
Each time also a fresh install of the integration and rebooting.
Using developer tools the time seems to be 10 minutes out but I can't see any way to set the time manually.

10 mins seems an odd offset I would have expected it to be whole hours if its timezone related.

The timestamp is UTC based - it counts the number of seconds since 1st January, 1970 UTC so time zone is not important.
That your HA is 10 minutes out suggests that its time sync isn't working - are you running HAOS or a VM or something else?  If it's HAOS I am not sure, you may try a complete reboot.  If it's a VM I'd suspect that the underlying OS isn't time synced, you should be able to manually change the time there.

HASS OS on raspberry pi 4.
Rebooting the host didn't work and looks to be an ntp issue but can't see any way to change the time manually in HA or OS.
obviously not an issue with the integration so I'll close this and keep looking for solutions with the OS.
Thanks for your help


addition to Further Topics: Aux Factories and their Creation

📚 Documentation

There's no documentation currently on how to use the iris.aux_factory module at the moment, either on creation of new factories or how to work with them in cubes. Seems a fitting topic for a Further Topics section?
See related discussion https://github.com/SciTools/iris/discussions/4780_

Thanks @acchamber. We consider Aux Factories to be among the most complex pieces of Iris' public API, with only a few niche uses, hence why we so far haven't gone beyond writing API docstrings.
Do you have some examples of when people want to use Aux Factories? It may be that the documentation should simply advise NOT using them (!), but we'd need to know more to be sure.

So, the reason I had to figure out how to create them was that I had some grib data that is in model-level format, and I needed to feed it into a suite ethat required input data to have a hybrid-pressure coordinate. The grib cube came with the level pressure and sigma data as coordinates and I have another cube with the surface pressure data, so had to figure out the exact syntax to add the the hybrid pressure factory to my input data.

@trexfeathers That sounds great. I don't know when I'll be able to get around to it, but my hope is this summer to do so (along with the other topics I've raised)


type-store: add field checks while reading types from JSON v2

Differences from v1:
- added checks for ports
Wrong JSON entries were causing segmentation fault in generator.
Pointed out by coverity.
Signed-off-by: Ricardo de Almeida Gonzaga<EMAIL_ADDRESS>

merged, thanks


Make Godzippa work with latest Cocoapods

Trying to use Godzippa with the latest Cocoapods which builds a framework fails.
This is because of the zlib import in the header files:
include of non-modular header inside framework module

Moving the import inside the implementation files seems to fix the issue and the framework and module map is generated automatically for the old podspec.

Thanks for the PR, @alexanderjarvis, but I'm not sure if this is an ideal solution, since the int parameters of some of the methods expect constants defined by zlib... Is there a way to resolve the non-modular header issues while not requiring the end-user to re-import the zlib headers?

This is fixed in the latest cocoapods.

#12 has a fix for this too 👍


[Bugfix] Files in SubmodelElementLists and NullPointerException when serializing/deserializing empty files

When a File had an empty value, a NullpointerException would occur in both AASXDeserializer and AASXSerializer. This is now filtered out with file.getValue != null
Additionally, Files in SubmodelElementLists were not included in the fileList. This was fixed by using the Visitor to get all files.

If I understand it correctly, the empty files issue is in the AASXSerializer. Would it be possible to move this test case to the TestAASXSerializer? Additionally, the test does not test the issue correctly. After reverting the code in AASX(De)Serializer, emptyFiles still passes.


Support for Explicit Source/Header Files

Currently, Tart uses the argument src and include to define header and source file with Cmake file globbing.
Desired features

[ ] Explicit file listing
[ ] Placeholder/Regex filepath

not really possible as headers are always found in a search path


[Blog]Change date on CV and Private posts

Issue has been resolved. Closing the ticket.

Accepted Closed.


Reduce startup latency and Sustain 60 fps for ephemeral UI apps

This issue captures all the issues being worked on for reducing startup latency and to sustain 60 fps for ephemeral UI apps

[ ] Improve Quality of unoptimized code https://github.com/dart-lang/sdk/issues/36409
[ ] Bridge all differences being seen in optimized JIT between the AST based version and the bytecode based version https://github.com/dart-lang/sdk/issues/36429
[ ] Investigate more optimal method dispatch mechanism https://github.com/dart-lang/sdk/issues/36426
[ ]  Further improvements to the kernel reader to speed up initial load times
[ ] Move debugging functionality out from unoptimized code to the interpreter https://github.com/dart-lang/sdk/issues/36427
[x] Separate the unoptimized and optimized background compilation queues
[x] Investigate and implement protobuf tree shaking of apps https://github.com/dart-lang/sdk/issues/36406
[ ] Explore possibility of AOTing framework code in a modular fashion https://github.com/dart-lang/sdk/issues/36408
[ ] Consider having a zygote process https://github.com/dart-lang/sdk/issues/36407
[ ] Optimize interpreter execution https://github.com/dart-lang/sdk/issues/36410
[ ] Switch default execution mode to be bytecode based https://github.com/dart-lang/sdk/issues/36425

ephemeral UI apps is not being worked on.


Maximum Subarray Sum Algorithm

The naive method is to run two loops. The outer loop picks the beginning element, the inner loop finds the maximum possible sum with first element picked by outer loop and compares this maximum with the overall maximum. Finally return the overall maximum. The time complexity of the Naive method is O(n^2).
Using Divide and Conquer approach, we can find the maximum subarray sum in O(nLogn) time. Following is the Divide and Conquer algorithm.
IMPORTANT: Please do not create a Pull Request without an issue.
All Submissions:

[ ] I have read the CONTRIBUTING document.
[ ] My code is written in Python3 and is ending with .py
[ ] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[ ] I have checked that my submission does pass the test on LeetCode.com
[ ] Does your filename follow the naming Conventions?
[ ] Have you linked your PR to an Issue?

Closing issues
Put closes #XXXX in your comment to auto-close the issue that your PR fixes (if such).

PR does not follow Contribution Guidelines - closed as spam


Fill out the cuisines select dropdown with cuisines user can search for

Need to check what cuisines the API is expecting

Have taken a selection of 15 or so of the most common, as displayed in the API. Omitted any with spaces ("Middle Eastern", "Family Friendy" ets) as I think spaces need escaping


why doesn't marked('#content') render well

Details about this question. Some wired question confusing me for hours
http://stackoverflow.com/questions/43921241/why-doesnt-markedcontent-render-well

Because it is not valid markdown.
use marked('#content')


Fix OMS addon + add tests and documentation for addons

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #3254
Special notes for your reviewer:
If applicable:

[x] documentation
[ ] unit tests
[ ] tested backward compatibility (ie. deploy with previous version, upgrade with this branch)

Release note:

@rashmichandrashekar FYI

/lgtm


Refactor Wikimedia Commons to use ProviderDataIngester

Fixes

Fixes #598 by @stacimc
Description

Refactors Wikimedia Commons to use the ProviderDataIngester base class
Notes
For Wikimedia Commons, the batch_limit applies to the number of image_pages to process, which is not necessarily a 1:1 relationship with records ingested. The result is that using a global ingestion_limit still works to limit the processing time but you may see slightly more records ingested.
Testing Instructions

Run the Wikimedia Commons DAG. Also try setting an ingestion_limit
Checklist

[ ] My pull request has a descriptive title (not a vague title like Update index.md).
[ ] My pull request targets the default branch of the repository (main) or a parent feature branch.
[ ] My commit messages follow best practices.
[ ] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[ ] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@stacimc Is this PR still in progress? Is there anything you need to be able to continue the work on this?

This is in draft pending the completion of the v1.3.0 milestone - once that's complete this can be rebased and undrafted!

Changing this to high priority as it blocks our ability to turn on reingestion workflows.

@krysal Good catch! I just confirmed that the issue appears on main, so it's not a regression. I opened a new issue for this in #715.


Possibility to preserve unknown aspect ratio

Hi!
I have a case where I use images with different aspect ratios (I have an upload function where the user can upload whichever image they want). In the documentation, I can see that you are supposed to provide a width and a height for the image. Is there any way to specify only e.g the width, and have the height adjust while preserving the original aspect ratio? Similar to how it works in html.
I am aware of the type: contain property in the sizing property, but as far as I understand, that only preserves the aspect ratio specified in the image's position/size-props. Is that correct?
I guess I can make some function to figure out the fetched image's width and height, calculate its aspect ratio and set the w+h in position/size-props accordingly, but of course it would be smoother if there was any way this package could handle that.
Thanks in advance,

I'm looking for the same thing. The images I'm trying to add to my PPT document need to be scaled, can either be in landscape or portrait mode, and I don't know their size or aspect ratio. I would like to define an area by w and h and have the image fill it. For portrait images, it would fill by height and by width for landscape images.

@AndreasNasman yeah, it seems like a pretty basic thing to ask for...
Anyway, I didn't find any way to achieve this natively in the package. I did it this way instead:

...
const image = await getImageMetadata(href) // See implementation in 1.
return {
    path: href,
    ...getBaseImageStyling(image.naturalWidth, image.naturalHeight) // See implementation in 3.
}

Get metadata (height, width) from img with url href

export const getImageMetadata = async (url: string) => {
  const img = new Image()
  img.src = url
  await img.decode()
  return img
}

Aspect ratio preserver

export const getBaseImageStyling = (
  width: number,
  height: number
): PptxGenJS.ImageProps => {
  const aspectRatio = width / height
  const adjustedWidth = IMAGE_WIDTH
  const adjustedHeight = IMAGE_WIDTH / aspectRatio

  return {
    w: adjustedWidth,
    h: adjustedHeight,
  }
}

... and then setting the sizing-attribute's w and h to whatever values I want the image to be contained in (with preserved aspect ratio)


Better naming of anonymous types and fields

Implement an algorithm that can automatically determine the best applicable name for anonymous types and fields. During my mapping work, I have yet to run into an edge case with these. Some suggested rules:

[ ] Anonymous fields should be named Anonymous as long as they are the only anonymous field in a type; otherwise, a number should be appended: Anonymous1, Anonymous2, etc.
[ ] Anonymous types should automatically take the name of the field they are associated with if the field is named. For example, _Range_e__Union if the anonymous type is on a field named Range. The algorithm may also be able to handle multiple named fields (with different names) referencing the same anonymous type in certain circumstances.
[ ] Unnamed anonymous types take the form _Anonymous_e__Union. Sometimes they conflict if multiple are defined within the same parent type. In these cases, a number should be appended: _Anonymous_e__Union1, _Anonymous_e__Union2, etc.

All of these should be getting handled now and should have test cases where applicable.


Aduprat jenkins 29850

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests


fuse: Better check for whether snapshots changed

What does this PR change? What problem does it solve?
We previously checked whether the set of snapshots might have changed based only on their number, which fails when as many snapshots are forgotten as are added. Check for the SHA-256 of their id's instead.
Was the change previously discussed in an issue or on the forum?
No.
Checklist

[x] I have read the contribution guidelines.
[x] I have enabled maintainer edits.
[ ] I have added tests for all code changes.
[ ] I have added documentation for relevant changes (in the manual).
[ ] There's a new file in changelog/unreleased/ that describes the changes for our users (see template).
[x] I have run gofmt on the code in all commits.
[x] All commit messages are formatted in the same style as the other commits in the repo.
[x] I'm done! This pull request is ready for review.

Test failure is something relating to locking.