Readiness Probe Fails on Backup Broker in HA Pair due to nonHA Message Spool.

I have successfully setup a 3 node HA group on the k8 using this guide:
https://docs.solace.com/Configuring-and-Managing/Configuring-HA-Groups.htm
Everything works as expected including the "Validate Failover" step.
Under this configuration, kubectl get pods reports the backup broker as not ready:

This is unexpected because it seems to properly take over when the primary broker releases activity to it. The only reported issues are warnings referring to the nonHA message spool. Failing the readiness check due to nonHA related warnings is not expected.
Describing the seemingly functional backup broker yields:
`]# kubectl describe pod solace2-solace-0
Name:         solace2-solace-0
Namespace:    default
Priority:     0
Node:         /
Start Time:   Mon, 02 Dec 2019 13:58:45 -0500
Labels:       active=false
app=solace
controller-revision-hash=solace2-solace-7855574578
release=solace2
statefulset.kubernetes.io/pod-name=solace2-solace-0
Annotations:
Status:       Running
IP:           <IP_ADDRESS>
IPs:
IP:           <IP_ADDRESS>
Controlled By:  StatefulSet/solace2-solace
Containers:
solace:
Container ID:  docker://ec51c6517fee9d76d50f738e9537c82e7415727b5a93e422e99c6be24d9a6aee
Image:         solace/solace-pubsub-standard:latest
Image ID:      docker-pullable://solace/solace-pubsub-standard@sha256:57c2b6c4d5ce3c0166f13efa3857ebdc3353d462a5be4974db9b7c44662c73a9
Ports:         2222/TCP, 8080/TCP, 55555/TCP, 55003/TCP, 55443/TCP, 60943/TCP, 60080/TCP, 60443/TCP
Host Ports:    0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP
Command:
bash
-ec
source /mnt/disks/solace/init.sh
# not using postinstall hooks because of order dependencies
# launch config check then Solace so VCMR can provide return code
nohup /mnt/disks/solace/config-sync-check.sh &
/usr/sbin/boot.sh
State:          Running
  Started:      Tue, 03 Dec 2019 10:50:06 -0500
Last State:     Terminated
  Reason:       Completed
  Exit Code:    0
  Started:      Mon, 02 Dec 2019 13:59:31 -0500
  Finished:     Tue, 03 Dec 2019 10:50:05 -0500
Ready:          False
Restart Count:  1
Limits:
  cpu:     2
  memory:  7680Mi
Requests:
  cpu:      1200m
  memory:   4Gi
Liveness:   tcp-socket :8080 delay=300s timeout=5s period=10s #success=1 #failure=3
Readiness:  exec [/mnt/disks/solace/readiness_check.sh] delay=30s timeout=1s period=5s #success=1 #failure=3
Environment:
  STATEFULSET_NAME:       solace2-solace
  STATEFULSET_NAMESPACE:  default (v1:metadata.namespace)
Mounts:
  /dev/shm from dshm (rw)
  /mnt/disks/secrets from secrets (ro)
  /mnt/disks/solace from config-map (rw)
  /usr/sw/adb from data (rw,path="adb")
  /usr/sw/internalSpool from data (rw,path="internalSpool")
  /usr/sw/internalSpool/softAdb from data (rw,path="softAdb")
  /usr/sw/jail from data (rw,path="jail")
  /usr/sw/var from data (rw,path="var")
  /var/lib/solace/diags from data (rw,path="diags")
  /var/run/secrets/kubernetes.io/serviceaccount from default-token-22scj (ro)

Conditions:
Type              Status
Initialized       True
Ready             False
ContainersReady   False
PodScheduled      True
Volumes:
data:
Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName:  data-solace2-solace-0
ReadOnly:   false
config-map:
Type:      ConfigMap (a volume populated by a ConfigMap)
Name:      solace2-solace
Optional:  false
secrets:
Type:        Secret (a volume populated by a Secret)
SecretName:  solace2-solace-secrets
Optional:    false
dshm:
Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
Medium:     Memory
SizeLimit:
default-token-22scj:
Type:        Secret (a volume populated by a Secret)
SecretName:  default-token-22scj
Optional:    false
QoS Class:       Burstable
Node-Selectors:
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type     Reason     Age                      From                            Message

Warning  Unhealthy  34m                      kubelet,   Readiness probe failed: Tue Dec  3 16:07:01 UTC 2019 INFO: readiness_check.sh-nonHA Message Router message spool is down
Warning  Unhealthy  34m                      kubelet,   Readiness probe failed: Tue Dec  3 16:07:06 UTC 2019 INFO: readiness_check.sh-nonHA Message Router message spool is down
Warning  Unhealthy  2m29s (x15258 over 21h)  kubelet,   (combined from similar events): Readiness probe failed: Tue Dec  3 16:39:21 UTC 2019 INFO: readiness_check.sh-nonHA Message Router message spool is down
`

Hi John, there may be multiple reasons as setting up a redundant configuration requires quite a few steps.
The suggested way is to not go through all the manual steps of setting up three PubSub+ deployments and configure them to create a working HA deployment.
You can set solace.redundancy to true in the solace/values.yaml file and then run the helm install command. This will use automation to set up redundancy and config-sync. This also makes use of kubernetes-local DNS resolvable hostnames to refer to the Solace nodes instead of IP addresses that would change when a pod goes down or gets evicted.

Ah yes. Using solace.redundancy to establish the HA cluster is a lot easier.
Are there additional commands to force the members of the cluster to use 3 different tainted nodes?
Thank you for the guidance,
-John

We currently allow kubernetes full control on placing pods on nodes.  We do not use taints, node affinity or anti-affinity.   It will likely be difficult to advise a scheme that would satisfy all requirements in all environments.
I think an anti-affinity to drive toward spread placement might be the simplest if you are going to allow Solace to be deployed on all nodes.
We are ok with multiple Solace pods on a node, just not multiple Solace containers in a pod.

My envisioned schema would potentially deploy the HA group across multiple data-centers to establish geographic diversity. I will look into an anti-affinity approach as you suggest.
Thank you,

We have drifted from product issue to solution architecture and git issues is not the correct form for this discussion.  I would suggest solace community. https://solace.community/ if you do not have a support account.
But generally speaking the disaster recovery feature is a better fit then trying to build a stretch cluster on Solace.   The main problem is where to place the monitor node.  Keep in mind two nodes must be able to communicate at all times for cluster to stay up.

Ok, thank you for your guidance. I will close this issue and move any further discussion to the solace.community.


GPC-NONE: Remove deprecated deploy parameter

I think so, but I wanted to do it in a couple of stages, because I couldn't work out quite what was going to happen :)


Fixing minor grammatical errors.

Saw a minor grammatical error in the Design considerations section. Approve if it feels suitable.

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

#label:"aq-pr-triaged"


Specify node version(s) for CircleCI tests

Need to make sure it's tests in 0.10+.

Now test in 0.10 and 4.


Auto skip last

We are currently using the category scale to show dates in a combo bar/line chart and would rather not have a large tick gap with inconsistent spacing between ticks.
Default functionality:
https://codepen.io/anon/pen/GEEqpr

AutoSkipLast disabled:
https://codepen.io/anon/pen/pwwbex

I agree that this definitely fixes the issue you are seeing. Not sure if we want to stick with a new boolean option or have some other kind of more generic option. @simonbrunel thoughts?

If that option only applies to the auto skipper and there is no use cases where we want to preserve other tick (e.g. autoSkipBeforeLast), then I'm fine with that option. I can't find a more generic name, @etimberg do you have any suggestion?
Actually, the only thing I'm thinking is if we are going to have more and more options to control the auto skipper, then maybe we should start to gather them under the autoSkip option:
autoSkip: false;   // disabled
autoSkip: true;    // enabled with default options
autoSkip: {        // enabled with custom options
    keepLast: true,
    padding: ...   // deprecates autoSkipPadding
}

An idea that could make this feature more generic: instead of autoSkipLast, we could use a callback: autoSkipInclude/autoSkip.include (or a better name) that will force the auto skipper to keep specific ticks:
include: function(tick, index, count) {
    return index === count-1;
}

I don't know if that would be useful, neither if that's the best function signature.
Any thoughts?

@simonbrunel I like the idea of nesting these options underneath the autoSkip setting.
I like the idea of a function that can override the default decision. Maybe we'd also want to provide a function that can do the measuring as well (right now we just use helpers.longestText). I'm not 100% on that function signature as well, but that's an implementation detail that could be worked out.
I wonder if we could refactor the autoSkip logic out into an internal plugin. #4117 refactored grid line drawing to a plugin so it should be possible.

I'm going to rewrite the helpers.longestText to be more generic and also handle more text formats. I'm not sure we should expose an option to override the text length, but I'm not familiar enough with scales and the auto skipper, so maybe I missed some use cases.
Could be a good improvement to export the auto skip logic in a separate plugin, I don't know if that's easily and cleanly possible.

I like the idea of moving autoskip into an internal plugin. I'll give it a shot.

Agreed about the use case of changing the lengths. It was just a thought I had.

How about something like this:
'use strict';

module.exports = function(Chart) {
	var helpers = Chart.helpers;

	return {
		id: 'tickAutoSkip',

		beforeDraw: function(chart, options) {
			helpers.each(chart.scales, function(scale) {
				var scaleOptions = scale.options;

				if (scaleOptions.display && scale.isHorizontal()) {
					scale.tickSkip = [1, 3, 5, 7];
				}
			});
		},
	};
};

Then in core.scale.js:
helpers.each(me.ticks, function(tick, index) {
	// Don't draw skipped ticks
	if (me.tickSkip && me.tickSkip.indexOf(index) !== -1) {
		return;
	}

Not sure about
if (me.tickSkip && me.tickSkip.indexOf(index) !== -1) {
  return;
}

if tickSkip contains a lot of indexes, this becomes O(n^2). I'd prefer a map or set.

Agree but also I'm not sure about a plugin accessing (private) members of scales. I think scales should provide all options that allows the user to fully customize ticks (e.g. a filter callback, etc.). Then the auto skip plugin would simply override these options.
Could require some substantial changes, so maybe we should first implement the feature of this PR directly in scale and work on the plugin refactor in another PR?

Doesn't seem like this is needed anymore with the changes to master.


Swedish characters not displaying

When I use JAMF School and sent a message through a bash script, all the swedish characters ÅÄÖ comes up with a ?-mark on the client side. Is this something to do with dialog or is it something else? It works fine when I run it on a client directly.

what version and how are you launching the dialog?
If swiftDialog is launched as root instead of the user, user preferences such as language and highlight colour are not captured. swiftDialog 2.3 or newer should handle this for you if you use /usr/local/bin/dialog

JAMF school runs them as root. It works fine if I run them directly on a client. I’ll see if I can work around it with your tips. Thanks !

closing as wontfix - the issue only appears when running the script from jamf school, not directly so the issue is somewhere in the command chain, not with swiftDialog itself


Change the log level in maven plugin

Characteristics

Issue Type: bug
Reproducibility: always

Description
We have a configuration file for Botsing and Evosuite logging level here. The botsing jar file follows this configuration. However, the Botsing maven plugin does not.

Maven, by default uses the SLF4J API for logging combined with the SLF4J Simple implementation and the default log level is set to info for all but in that way there is a lot of log at info level by classes under org.evosuite package.
A simple solution is to set the logging level for org.evosuite to off in the simplelogger.properties file of Maven (for me it is /usr/share/maven/conf/logging/simplelogger.properties) adding this line:
org.slf4j.simpleLogger.log.org.evosuite=off

I don't like to put something specific of EvoSuite in a general Maven configuration file, so the alternative is to add this parameter when the plugin is invoked.
The parameters to add are:

-Dorg.slf4j.simpleLogger.log.org.evosuite=off
-Dorg.slf4j.simpleLogger.showLogName=true
The first one is to exclude org.evosuite packages, the second one is to show the class name and can be optional.

The resulting command will be something like that:
mvn eu.stamp-project:botsing-maven:botsing -Dcrash_log=LANG-9b.log -Dtarget_frame=2 -Dorg.slf4j.simpleLogger.log.org.evosuite=off -Dorg.slf4j.simpleLogger.showLogName=true


Make tilde a choice please

📝 Provide a description of the new feature
Keyboard in my language (italian) doesn't have such a key and it's impossible to pick it. The usual way to type tilde is Alt+126(NumPad)
What is the expected behavior of the proposed feature?  What is the scenario this would be used?
I'd like to have tilde right in the key list, to pick from
If you'd like to see this feature implemented, add a 👍 reaction to this post.

Identical to #8238. See #8230.

Identical to #8238. See #8230.


[Release Test] Verify that VMs stay up when disks are evicted

Related issues

#1334 Volumes fail with Scheduling Failure after evicting disc on multi-disc node
#5307 Replicas should be evicted and rescheduled to other disks before removing extrak disk

Verification Steps

Created 3 nodes Harvester.
Added formatted disk (called disk A) to node0 VM in the harvester node page.
Added disk tag test on following disk in the longhorn page.

disk A of node0
root disk of node1
root disk of node2

Created storage class with disk tag test.
Created volume (called B) with previous storage class. You should check scheduling status in the longhorn page.
Created VM with volume B as extra volume (not boot volume).
The node scheduling status should look like this.

Deleted disk A in the harvester node page, error message should be displayed.
Added disk tag test to root disk of node0.
Requested eviction and disabled scheduling on disk A in the longhorn dashboard.

Before:

After:

Removed disk A in the harvester node page, and it should be removed.

Expected Results

Disk A is removed on the harvester node page.
VM is running in whole step

Test ok on v1.3.1-rc1, close as done.
Environment

harvester-v1.3.1-rc1

Profile: 3 nodes QEMU/KVM (8C/16G/500G)
ui-source: Auto

Steps

 Added formatted disk (called disk A) to node-0 VM in the harvester node page.

Added disk tag test on following disk in the longhorn page.

 disk A of node0

Reflect on Harvester

 root disk of node1

Reflect on Harvester

 root disk of node2

Reflect on Harvester

 Created storage class sc-tag-test with Disk Selector tag test.

 Created volume extra-volume with previous storage class. You should check scheduling status in the longhorn page.

Longhorn status

 Created VM with extra-volume as extra volume.

 Check Longhorn node scheduling status.

Delete disk A from harvester node page

 After save, error message should be displayed.

 Check eviction and disabled scheduling are requested on longhorn.

 Added disk tag test to root disk of node-0.

As replica condition is satiffied, now disk A should be removed.

 Disk A is removed on the harvester node page.

 Disk A is removed on the Longhorn node page

 VM is running in whole step


[core-amqp] Remove esbuild for vite

Packages impacted by this PR

@azure/core-amqp

Issues associated with this PR

#29683

Describe the problem that is addressed by this PR
Removes esbuild and its polyfills for Node in favor of vite and vite node plugins.
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.

/check-enforcer override


[nrf noup] boards: nordic: thingy53: Remove old SECURE_BOOT selection

Removes selecting SECURE_BOOT as this is now an automatic selection

just note that this makes it incompatible with child_image. I assume that's the intention.

just note that this makes it incompatible with child_image. I assume that's the intention.

?? No it does not, this is a sysbuild file, it does nothing to parent/child images


Refactor first set of extensions into structs

Please note that while we are transitioning from travis-ci to AWS CodeBuild, some tests are run on each platform. Non-AWS contributors will temporarily be unable to see CodeBuild results. We apologize for the inconvenience.
Issue # (if available): https://github.com/awslabs/s2n/issues/1817
Description of changes:
Move the first 5 extensions into the new structures. This batch is mostly currently tested through the shared s2n_client_extensions_test, so I also added individual unit tests.
For each extension, I:

create the struct
move current send and receive logic into static methods linked to the struct
write static should_send method based on the existing logic in s2n_client_extensions
replace current send and receive methods with calls to s2n_extension_send/recv
remove type + size from what the send method sends

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

Codecov Report

Merging #1886 into master will decrease coverage by 1.49%.
The diff coverage is 86.44%.

@@            Coverage Diff             @@
##           master    #1886      +/-   ##
==========================================
- Coverage   81.51%   80.01%   -1.50%
==========================================
  Files         229      229
  Lines       17014    18262    +1248
==========================================
+ Hits        13869    14613     +744
- Misses       3145     3649     +504


Create federated private rooms in Element

Summary

The test group has asked for this feature.
Users should be able to create a private room in Element and make it federated to Mattermost

Summary

The private room will be a federated room when the Mattermost Bridge user is invited to the room by the creator.
Mattermost puppet user must be invited room before we create a private channel mapped to the room.

Development estimation
8 hours (1 day)


Incompatible with AutoHUD

Description
AutoHUD hides different elements on your HUD, from the hotbar to the crosshair. When disabling its interaction with the crosshair (setting Crosshair > Active = False), it causes an interesting effect when Shoulder Surfing's crosshair is set to dynamic or adaptive and you hold a shooting weapon, like a bow or snowball. It causes the entire HUD to move with it, and the crosshair doesn't display, throwing up errors in the log. Reenabling AutoHUD's interaction with the crosshair (setting Crosshair > Active = True) removes this glitch.
Tested in a minimal instance in the log below.

Minecraft version
1.20.1-FORGE-47.3.6
Incompatible mod name
AutoHUD
Incompatible mod version
8.0
Game Logs
https://mclo.gs/9GNiRFt

Thanks for reporting. I pushed a fix for the "offset hud" bug. The error messages in the logs are caused by AutoHUD, which also appear when you just install AutoHUD on its own. It looks like they are targeting newer or older code than 1.20.1. Because of that, the crosshair still behaves a bit buggy. I suggest reporting this to the authors to AutoHUDin order to fully fix the issue.


When I try to use this mod with mod Optifine 1.12.2, the game crashes.

When I try to use this mod with mod Optifine 1.12.2, the game does not start.
Additional information:

crashlog file or gist:
fml-latest.log file: highly recommended to provide
2019-12-20-4.log

First, you use the <IP_ADDRESS> version which crashes by itself, you need to use <IP_ADDRESS>
Second, interesting enough, in the log you sent it crashes because of Optifine itself somehow, does that work for you without my mod?
And third, yes, this mod was known to never work with Optifine since the beginning, and Optifine is already the first in the list of mods to be checked for mod compat issues.
Thanks for your input, but also closing this as duplicate of #16, since nothing changed about optifine support (the lack of it) since then


Swift instructions in README

Can you add some instructions to the README on how to use CoreBitcoin in Swift? I'm able to use the Cocoapod in a single page Objective C iOs project. But if I try import BTCMnemonic or import CoreBitcoin in a Swift project - iOs or OS X - I get no such module CoreBitcoin.

Just try to add path to CoreBitcoin in Build Settings -> Header Search Path and then create bridge file to objective-c and make #import "CoreBitcoin/CoreBitcoin.h" in the bridge file. For me it worked.


Igo fr legalcode

@aldenstpage to walk @TimidRobot through publishing IGO FR

@aldenstpage @sarahpearson @TimidRobot
Let's do this! I'll send a meeting invite wherein I hope we can screen share and pull these forward to publication. Also, I'd like to address the issue of how to reflect the additional languages on the legal code, which is currently missing.

Just a note that the link to the deeds still pull up an "error establishing a database connection" so I'm not sure these are ready to go live.


Replace pre-calculation of resourcesWithAttributedChildren

resourcesWithAttributedChildren have been introduced in AttributionData back at the time when we were showing down-arrows for signals and attributions (and were not virtualizing the tree). This data it is not optimized for the folder colors, and expensive to compute. Therefore:

remove it
if tree navigation becomes slower add new pre-computed data, that is:
2.1 optimized to get the folder color,
2.2 can be updated with cheap (aka fast) calculation if an attribution is created/deleted or a signal is hidden.

As this ticket is unclear and also @vasily-pozdnyakov does not remember this scope/rationale, we close this issue.


Update README.md

Corrected link to the tutorial:
http://blog.aluxian.com/how-to-create-cross-platform-desktop-apps-with-nw-js/
Fix #2

Wonderful! Thanks a lot! :)


Fix issue template to mention doctest instead of Catch

Should this go to master or dev branch?
This only changes the issue template, not the repo. Also Github complains about the issue template:

You are using an old version of issue templates. Please update to the new issue template workflow. Learn more

Thanks for this! I'll keep it open for when I have some time to look at the new issue template - then I'll merge it!


Replace sodium-prebuilt with sodium-native

When I wanted to install scuttlebot, there was numerous problems to install sodium-prebuilt package on Darwin without automake and libtool.
Recommended solution from @mafintosh https://github.com/mafintosh/node-sodium-prebuilt/issues/10#issuecomment-293849292 is to replace package for sodium-native
Thoughts?

yes, so we basically just need either to update secret-handshake, private-box, ssb-keys and pull-box-stream to the sodium-native api. or write an adapter that gives the other api. pull-box-stream is the only place that would actually benefit from the memory reusing perf thing

Just tried installing scuttlebot and the installation is super fast! :heart:
This issue can be closed. I believe 2.2.7 fixes this but the code isn't pushed to github yet.

yup, this is all good now, and there is even a prebuild for arm (RPi and your phone)


p2p shutdown delay

Motivation

Closes #1885

Changes
use context to cancel p2p routines
Test Plan
change UT accordingly
TODO

[x] Explain motivation or link existing issue(s)
[x] Test changes and document test plan
[x] Update documentation as needed

bors merge

bors merge


testbench: Increase DMA memory transactions to omit DMA deadlock

Transaction issued by the DMA larger than 4K might deadlock. Increasing the transaction buffer fixes this in my case.
@zarubaf @accuminium do you think we can leave it like that for now?

Yes absolutely! I’ll open an issue about the fundamental problem later and will take care of it :-) Thanks 🙏


Undefined preferred language when using determinePreferredLanguage()

I have the following setup in my module config:
$translateProvider.fallbackLanguage('en');
$translateProvider.useLocalStorage();
$translateProvider.useSanitizeValueStrategy('escaped');
$translatePartialLoaderProvider.addPart('relinc_ui');
$translateProvider.useLoader('$translatePartialLoader', {
  urlTemplate: '/cxf/relinc-service/language/translations/{part}?lang={lang}'
});
$translateProvider.registerAvailableLanguageKeys(['en', 'ar']);
$translateProvider.determinePreferredLanguage();

Everything works fine when the browser sends an en_* or ar_* locale, however when the browser sends a locale which is not registered in the available language keys I just see untranslated keys in my UI and I see "undefined" as language key in my local storage. It seems to me that this is due to the implementation of the negotiateLocale function which doesn't return anything if the preferred locale is not found in the available languages.
What is even worse than that is that if at some later point in my application I do $translate.refresh() I get the error "No language key specified for loading.". From what I understand from going through the code with a debugger every time the $translate function is called the preferredLanguage (which in this case is undefined) is pushed in the $fallbackLanguage array which is what later causes the error in $translate.refresh().
Is there something wrong in my configuration or is this an angular-translate issue?

One question about this topic, I would like to use determinePreferredLanguage to determine preferred language (yes, not a surprise!) for the user, but only his locale is included within $availableLanguageKeys. But this is not working as the method negotiateLocale() just returned the given locale by default if not found in availableLanguage array. I would say that it should return the $fallbackLanguage instead, shouldn't it ? otherwise user can have a non supported locale as preferred. What do you think ?
thanks for your feedback


Fix error in prepareServer

Description
This PR fixes a bug in Server.prepareServer.

@emilevauge  Oups, tests failed !


Questions about evaluation

Hi，Mathias
I noticed that there are no ground truth flow in the evaluation or test sequences of DSEC dataset, and some training sequences neither. Did you just split the sequences with ground truth into training and test sequence to get the EPE score?

We only compute optical flow groundtruth for parts of the dataset without moving objects. Therefore we had to exclude some sequences because they contain moving objects.
In this work, we train on the full training set and then finally evaluate on the test set.
To evaluate on the test set, you have to submit to the evaluation server: https://dsec.ifi.uzh.ch/uzh/dsec-flow-optical-flow-benchmark/

Is it possible for you to release the ground truth of test set?
Since I don't have the ground truth of test set, I have to split the train set into train and test set to get the AEE score.
I can't train E-RAFT on my split train set because of no training code. If I train it using my strategy, it will be unfair for you because of my bad coding skill.
It's really hard to compare your work with mine. And when writing paper, there should be the optical flow images of your results , my results and ground truth.


wrong weather template that does not report any forecast

hello.
I think that there is an error in the template example. OpenWeather does report some weather (listed in the debug mode) but the template is testing << tuesday['weather_status'] >> It should be  tuesday['07:00']['weather_status']

This is correct. Feel free to send a PR to update the doc.

Actually, I can't get a response using this template, even with the "if" statement change. It pulls the data, but the message is empty. It looks like the times have changed in the data, for example, there is no '07:00' anymore, it's '08:00'. Even with those updates, if there's no data, it should report "I'm sorry, there is no forecast for..." but it just returns an empty message.

Yep. We haven't changed the doc. But I'm still wondering if the api change when summer/winter time.

maybe we can change the template to "read the available hour" and update the request..


Missing fonts somewhere

get_icon_names output

So, correct me if I'm wrong, but it looks like it's actually rendering your prompt just fine, but you then see UTF garbage when you execute your command, maybe? Can you show a bigger screenshot where you are seeing the bad codepoints?

So does the text appear after you execute a command? While you're typing? Can you describe what's happening?

Sorry, it appears after command execution.

So you execute a command, which works fine, and then it echos the name of the program you ran surrounded by UTF garbage?
Can you share your ~/.zshrc?

Sure. https://gist.github.com/Coding-Doctors/267fdbce6649ec5008eeec407c57aecf

Hm, two things to try: Can you try commenting out your  setopt CORRECT and let me know if that does anything? Can you also try removing your custom wifi segment from your prompt and let me know if that does anything?

Seems neither do anything besides remove my wifi signal segment. I've updated my config with the changes you suggested https://git.io/vFCnG

Small update, part of the issue seems to be in relation to me using xfce-terminal, (forgot how broken it is) After switching back to gnome-terminal the UTF garbage doesn't stay all the time, and usually disappears in a couple of seconds.

@Coding-Doctors - I'm really quite flummoxed, to be honest. I don't think I've seen anything like this before. What version of ZSH are you using? What version of gnome-terminal? Out of pure curiosity, what Linux distro?

ZSH version is zsh 5.4.2
gnome-terminal version is GNOME Terminal 3.26.2 Using VTE version 0.50.2 +GNUTLS
I'm using the Void Linux distro

@Coding-Doctors - I'm honestly not sure what's going on :(
The fact that the behavior changes between terminals makes me think that it's not necessarily a P9k issue, but I'm really not sure. If anyone else has thoughts, here, that would be super helpful! @dritter @shibumi

So I've narrowed it down to this variable export TERM="screen-256color" when this is active the utf garbage is thrown after every command, with it disabled/commented out the garbage disappears and is no longer a problem.

@Coding-Doctors - That's really strange, because that's exactly what I have my $TERM env variable set to when I use tmux (which I do everyday). I'm not sure why it would work for me and not for you.
Really confused about this one.
Are you using the master or next branch of P9k?

I see garbage in both gnome-terminal and xfce-terminal with it set, when unset neither of those have garbage in them. This occurs on both master and next (my git install for both powerlevel and ohmyzsh were broken for some reason, though after reinstalling those nothing but the git repo changed) it does not seem to be effected by which branch I'm using nor terminal.
I will not I'm not using tmux at the moment (need to remake a new config for it, managed to delete it) if that means anything to you.

@Coding-Doctors - Well, I apologize, but I really don't have any idea what's going on here or how to fix it. It sounds like you have a $TERM setting that works outside of screen/tmux, so hopefully it's not a problem for you to just use that? Sorry - I'm just not sure what else to do on this one. I'm going to close this for now, but feel free to re-open if you find more clues.


dockerTools.buildImage: support impure dates

Because dates are an impurity, by default buildImage will use a static
date of one second past the UNIX Epoch. This can be a bit frustrating
when listing docker images in the CLI:
$ docker image list
REPOSITORY   TAG      IMAGE ID       CREATED        SIZE
hello        latest   08c791c7846e   48 years ago   25.2MB

If you want to trade the purity for a better user experience, you can
set created to now.
pkgs.dockerTools.buildImage {
  name = "hello";
  tag = "latest";
  created = "now";
  contents = pkgs.hello;

  config.Cmd = [ "/bin/hello" ];
}

and now the Docker CLI will display a reasonable date and sort the
images as expected:
$ docker image list
REPOSITORY   TAG      IMAGE ID       CREATED              SIZE
hello        latest   de2bf4786de6   About a minute ago   25.2MB

Motivation for this change

the date issue is a real issue. I often am asking the question of "is this the image I just built? what's the timestamp on it?"

-- https://twitter.com/StewOConnor/status/1042671588447936512
cc @stew
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

amazing nerdsnipe! Thank you so much, @graham-at-target !!

I like it!

It doesn't just provide the ability, but advertises it in the manual as "providing better user experience" (so nudges the user in that direction). BTW, apart from the minor cosmetic aspect of improving the "CREATED" column, how does this improve user experience?

Well it does provide a better user experience if you're looking at the output of docker image list. The lines are ordered by when they're created, and having your newly loaded image appear by the oldest make them hard to find.  I could replace the vague "improved user experience" nudge with "ordered docker image list output"

what if the docs said:

You can break binary reproducibility and have a sorted, meaningful CREATED column by setting created to now.

This isn't enabled by default right? I don't see a big problem with providing an option that has a small (cosmetic) impurity.

My impression is the biggest concern is in the too-positive nudge for users to turn it on without understanding the cost.

@grahamc Yeah something like that sounds good.

Great! Improved in
https://github.com/NixOS/nixpkgs/commit/7736337916538aab67a00739c53b8434da773a3b
On Thu, Sep 20, 2018 at 5:05 PM Eelco Dolstra<EMAIL_ADDRESS>wrote:

@grahamc https://github.com/grahamc Yeah something like that sounds
good.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/47005#issuecomment-423332910, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAErrBnIeOmRVzx6Khk5F5gREY1Pl9nLks5udAMBgaJpZM4WybeQ
.

Sounds good! As long as we keep binary reproducibility by default and set up big warning signs, I don’t see why that shouldn’t be an option.


Feat: The UI of the About section

Describe the feature
Hey @SUGAM-ARORA the UI in the about section seems boring with the minimal animation and the absence of navbar which make user difficult to go from about page to another page directly.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[ ] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@Shrivastava-04 Issue not needed


Update ISSUE_TEMPLATE.md

description description description description description description description description description description description description description description description description description

description  description  description  description  description
description  description  description  description  description
description  description  description
On Thu, Dec 9, 2021 at 3:16 PM Chimpin @.***> wrote:

No description provided.
Wen description ser
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Aberzelius/raptoreum/pull/6#issuecomment-990212707,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASTSMPOVPH4W2TWJED7IXG3UQEFDFANCNFSM5JXK7BKQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Create organization-workflows.md

Checklist

[x] If you're adding a listing for your app, be sure your app is in the /_apps/ folder before opening this Pull Request.
[x] All comments in frontmatter need to be removed.
[x] Performs a useful action through the GitHub API that solves an existing problem for developers: Centralized GitHub Action workflows
[x] Is original: for example, it does something not already done by an existing Probot app
[x] Has unit tests and e2e tests
[x] Has documentation
[x] Is open source
[x] Has a license
[x] Has a code of conduct
[x] Has someone willing to at least minimally maintain them for the near future: @svanboxel

View rendered _apps/organization-workflows.md

From what I can see the Travis CI errors don't relate to the file I added:

From what I can see the Travis CI errors don't relate to the file I added:

From what I can see the Travis CI errors don't relate to the file I added:

yeah, sorry for that. The website repo could really use some love and get rid of these errors, and get rid of Travis while at it

From what I can see the Travis CI errors don't relate to the file I added:

yeah, sorry for that. The website repo could really use some love and get rid of these errors, and get rid of Travis while at it


ilm:1.2.1

I am submitting

[ ] a new package
[x] an update for a package

Changelog

Avoid line break between link text and indicator (circle) (https://github.com/talal/ilm/commit/dc8614011d3c2bf08ec4b041c59e9723443fc479)

[x] ensured that my package is licensed such that users can use and distribute the contents of its template directory without restriction, after modifying them through normal use.

Thanks :)


Fix https://github.com/nrc/rustfmt/issues/377

Excellent!
The only thing that to consider is when things don't work out. What if there's not enough space, or if a rewrite fails?
We generally propagate such errors to the caller, in the hope that it can create more space for us. Practically, this can be done by returning None when a rewrite fails (using try_opt!, for example) and checking the width constraints by wrapping the overall result in a utils::wrap_str call.
Thanks for the PR!

Changed it to return None in error cases. I mistakenly thought we need to handle the error at the rewrite func.

Maybe consider using write_list instead of just blindly concatenating the members of the tuple?  (The current version isn't wrong, exactly, just less than ideal.)

write_list doesn't work with separators any more. This is good for now.
Thanks for the PR, @sinhpham!


Training Feature Preprocessing Issues

As described in Data-strategies for image-based cell profiling, preprocessing features usually involves plate-layout-effect correct. However, for the training data, we do not have the context of an entire plate. For this reason, batch and plate-layout effect correction become difficult. This is a good time to begin considering the download, preprocessing, segmenting, feature extraction data stream pipeline so we can demonstrate these corrections are not needed or begin applying them to training data.

In 3.normalize_data we use UMAP to suggest that batch effects are not the dominant signal in mitosis movies. Rather, the gene knockdown perturbations are the dominant signal in feature data.
Because batch effects are likely not the dominant signal in the mitosis movies, we perform normalization across the entire screen. In other words, we create one normalization scaler from all negative control features and apply this normalization scaler to all mitosis movie feature data.


some update

Is the entire PR just a change to a comment?

Is the entire PR just a change to a comment?

Due to inactivity I'm going to close this.
... Next time, please make meaningful contributions. Do remember that other people spend time and effort into reviewing your changes.

Due to inactivity I'm going to close this.
... Next time, please make meaningful contributions. Do remember that other people spend time and effort into reviewing your changes.


[Feature] Improvements to source properties handling

Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature
We have a use case for dynamic assignment of database names for models which select a database name based on the currently authenticated user to allow for usage of developer-specific data sets during development. While we have been able to implement a custom generate_database_name macro for this functionality on models, we cannot apply this same logic on sources as dbt does not support using the generate_X_name macros for dynamic assignment of either database or schema properties for sources.
For context, we currently use logic similar to below to assign database names within sources properties files.
sources:
  - name: source_x
    database: "\
      reporting_
      {%- if target.name == 'dev' -%}
        {{ env_var('DBT_USER') }}
      {%- else -%}
        {{ target.name }}
      {%- endif -%}
      "

While this functionally works, we have to copy and paste this code for every single source property file in our project to reuse this logic for each source. This exact same logic is contained within our generate_database_name macro so it would be useful to be able to reuse that and not violate DRY for every new source.
I therefore suggest one of the following approaches to bring source configuration more in-line with model configuration to allow for this functionality with reference to the above example on how this would improve it.

Have sources properties use the generate_X_name macros automatically. e.g.

sources:
  - name: source_x
    database: "reporting"  # This would then use the `generate_database_name` macro to use the same logic as above

Allow usage of generate_X_name macros within source properties files to allow us to unify handling of these properties for both sources and models.

sources:
  - name: source_x
    database: "{{ generate_database_name('reporting') }}"

If this is not possible due to design choices, bring parity of source properties with other resource types to allow for definitions at the project file level to pass down to all sources within a resource path as is possible with models. This will at least allow us to define the logic for sources once at the project file level.

sources:
  project_name:
    resource_name:
      +enabled: true
      +database: "\
          reporting_
          {%- if target.name == 'dev' -%}
            {{ env_var('DBT_USER') }}
          {%- else -%}
            {{ target.name }}
          {%- endif -%}
          "

Describe alternatives you've considered
Manually copying and pasting database jinja templates across all source properties which violates DRY.
Who will this benefit?
Anyone who uses dynamic database or schema assignment for sources in a similar way to models. Specifically this will benefit users who need developer specific data environment handling for sources.
Are you interested in contributing this feature?
Yes
Anything else?
I am aware there are stale discussions for all of the suggestions above as described here and here.
These discussions are stale and closed so I am consolidating these here in an effort to unify discussion on this issue.

Snapshots also have this issue. In each snapshot sql config block you HAVE to specify database to reference the generate_custom_database() AND specify schema even if schema name isn't dynamic. Took me days of troubleshooting to figure this out.

I was redirected to Issue 4753 from Issue 6056 and landed here based on a comment left on Issue 4753. (And I see the OP on this thread also notes Issue 3662). I have effectively the same problem as the OP in this request but related to generate_schema_name. We need everything to flow into the same schema for both Sources and Models during development and testing.
In my specific use case, we only have one database in play, but each of our clients' data is stored in a dedicated schema and must be kept separate for security and integrity purposes. We have an uncommon setup in that we do substantial amounts of dev testing directly on our production database because we don't want to create any additional copies of our live client data for security purposes. The generate_schema_name macro supports this pattern quite nicely for Models, but we hit the same roadblock described in the original request for Sources.
From a DevOps perspective, this is frustrating and confusing because it means configs, and therefore the ETL construction process, work fundamentally differently for different dbt resources - the natural support of parallel construction and DRY-friendly structure is normally one of the strongest benefits of using dbt. I have gotten around this for now by adjusting the schema names directly in each Source file: "{{ '[client]_landing' if target.schema in [my_values] else target.schema ~ '_[client]_landing' }}". This is not outrageously problematic while I'm the only data engineer at a small startup and our number of Sources isn't huge, but as my team grows, it would be great to have one of the improvements described in the original request above.


High Vuln with lodash in cli-service

Version
4.5.6
Reproduction link
https://github.com/vuejs/vue-cli
Environment info
Environment Info:

  System:
    OS: macOS 10.15.6
    CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
  Binaries:
    Node: 10.15.1 - /usr/local/bin/node
    Yarn: 1.19.2 - /usr/local/bin/yarn
    npm: 6.14.2 - /usr/local/bin/npm
  Browsers:
    Chrome: 85.0.4183.121
    Firefox: 80.0.1
    Safari: 14.0
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce
Need to bump versions of lodash methods defaultsdeep, mapvalues & transform to ^4.17.11
https://snyk.io/vuln/SNYK-JS-LODASH-73638
What is expected?
No High Vulns in dependencies.
What is actually happening?
High Vulns in dependencies.

I don't there are any vulnerabilities in these dependencies. You are referring to a vulnerability in the lodash package, while Vue CLI uses the latest version of these standalone packages, which is not affected by the issue.


fix slot duration parsing

Observed a problem when using mainnet-genesis.json from cardano-sl: the slot duration was reported to be 0.020 seconds. In that file, and in the yaml genesis specs, slot duration is milliseconds. Before this patch, the FromJSON NominalDiffTime instance was used for parsing. Now, the FromJSON Integer instance is used, and the Integer milliseconds are explicitly converted to NominalDiffTime.

Looks like one of the golden tests is failing.

The golden test for ProtocolParameters CBOR fails because the example uses 999e-6 :: NominalDiffTime for the slot duration value, which rounds to 0 in milliseconds. Previously this was encoded as 0x1903e7, or 999 in major type 0, so it makes sense then that decoding 20000 would give 0.020 = 20000e-6 seconds. With this patch, it encodes to 0x00, or 0 in major type 0, because of the floor rounding (it is 0 milliseconds).
What to do about this? I pushed another commit to simply change the example so that a sufficiently-big NominalDiffTime is used, to get that 0x1903e7 pattern that other fields show.
But maybe it would be better to not use NominalDiffTime here, to avoid this rounding trap all together. Thoughts?

Now  ✗ ts_prop_mainnetEpochsValid failed after 1 test. fails, but it does so too on master.

If you're sure that this doesn't break compatibility with mainnet encodings, then you can simply update the golden test file. You can get the updated lines from the test output diff. Do make really sure this works with mainnet though!

@avieth Ru comments

It looks compatible with mainnet, so you can just update the golden tests I suppose

If you're sure that this doesn't break compatibility with mainnet encodings, then you can simply update the golden test file. You can get the updated lines from the test output diff. Do make really sure this works with mainnet though!

If I change it to be Integer rather than NominalDiffTime, it'll still work. I'll make the change and verify.

If you're sure that this doesn't break compatibility with mainnet encodings, then you can simply update the golden test file. You can get the updated lines from the test output diff. Do make really sure this works with mainnet though!

Golden test file unchanged, but the test subject was changed from (999e-6 :: NominalDiffTime) to (999 :: Natural). This is better overall. 999 microseconds is not a valid slot duration.

bors r+


Adding support for Redis lookup tables

The lag in second metrics is really what make that exporter different from the others.
After using it for a while, I noticed the lag was really accurate when the points were inside the lookup table, but the extrapolation was really not that precise and was often leading to really high numbers.
One of the reason is when the extrapolation happens, it is done based on the entire lookup table, which works well if you have a consumer speed that don't change too much, but doesn't work well when you have a consumer that spikes.
Because of that, I tried to increase the size of the in-memory lookup table, to be able to fit between one day and one week of data but when the exporter was restarting, it took a very long time to build the lookup table.
This lead to change change, which is basically adding an option to move the lookup table in Redis, so the lookup table could be bigger and will not be affected by restart anymore.
The option is under a redis category:

Key
Default
Required
Description

enabled
"false"
No
Switch to enable or disable the Redis table (if enabled, the memory tables will not be created).

database
0
No
Redis database number.

host
"localhost"
No
Redis server to use.

port
6379
No
Redis port to use.

timeout
60
No
Redis connection timeout.

prefix
"kafka-lag-exporter"
No
Prefix used by all the keys.

separator
":"
No
Separator used to build the keys.

resolution
"1 minute"
No
Resolution of the lookup table. Last point will get updated if the collection interval is less than the resolution.

retention
"1 day"
No
Retention of the lookup table. Points will get removed from the table after that.

expiration
"1 day"
No
Expiration (TTL) of all the keys

Other changes: Updating the docker base image from centos:8 to openjdk:8 as the centos repositories were archived
Test images are available here: https://hub.docker.com/r/guillaumeroland/kafka-lag-exporter/tags

[info] ConsumerGroupCollectorSpec:
[info] ConsumerGroupCollector should send
[info] - report 9 metrics
[info] - earliest offset metric
[info] - latest offset metric
[info] - last group offset metric
[info] - offset lag metric
[info] - time lag metric
[info] - max group offset lag metric
[info] - max group time lag metric
[info] - sum group offset lag metric
[info] - sum topic offset lag metric
[info] ConsumerGroupCollector should calculate max group metrics and send
[info] - max group offset lag metric
[info] - max group time lag metric
[info] ConsumerGroupCollector should sum the group offset lag metrics and send
[info] - sum of offset lag metric
[info] - sum of offset lag by topic metric
[info] ConsumerGroupCollector should report group offset, lag, and time lag as NaN when no group offsets found
[info] - last group offset metric
[info] - offset lag metric
[info] - time lag metric
[info] - max group offset lag metric
[info] - max group time lag metric
[info] - earliest offset metric
[info] - latest offset metric
[info] - topic offset lag metric
[info] ConsumerGroupCollector should evict data when group metadata changes
[info] - remove metric for consumer ids no longer being reported
[info] - remove metrics for topic group partitions no longer being reported
[info]   remove metrics for topic partitions no longer being reported
[info]   - topic partition metric removed
[info]   - all group-related metrics removed
[info]   - topic partition in topic partition table removed
[info] InfluxDBPusherSinkSpec:
[info] InfluxDBPusherSinkImpl should
[info] - create database
[info] - report metrics which match the regex
[info] - should get the correct global label names and values as tags
[info] IntegrationSpec:
[info] kafka lag exporter
[info] - should reports offset-based lag metrics
[info] - should reports time lag increasing over time
[info] - should report poll time metric greater than 0 ms
[info] AppConfigSpec:
[info] AppConfig
[info] - should parse static clusters
[info] - should set blank string for the clusters if label value is absent
[info] - should handle the empty config case
[info] MetricsEvictionOnFailureSpec:
[info] kafka lag exporter
[info] - should not report metrics for group members or partitions after a failure
[info] LookupTableSpec:
[info] LookupTable
[info] - toLong
[info]   RedisTable
[info]   - invalids and edge conditions
[info]   - square lookups, x == y
[info]   - lookups with flat sections
[info]   - lookups when table only contains a flat section with offsets same as lookup
[info]   - lookup is zero when when table has a single element the same as the last group offset
[info]   - infinite lookups, dy == 0, flat curve/no growth
[info]   - table retention and resolution
[info]   - normal case, steady timestamps, different val rates
[info]   - mostRecentPoint
[info]   - redis return invalid results
[info]   MemoryTable
[info]   - invalids and edge conditions
[info]   - square lookups, x == y
[info]   - lookups with flat sections
[info]   - lookups when table only contains a flat section with offsets same as lookup
[info]   - lookup is zero when when table has a single element the same as the last group offset
[info]   - infinite lookups, dy == 0, flat curve/no growth
[info]   - normal case, table truncates, steady timestamps, different val rates
[info]   - mostRecentPoint
[info] PrometheusEndpointSinkSpec:
[info] PrometheusEndpointSinkImpl should
[info] - register only metrics which match the regex
[info] - append global labels to metric labels
[info] - should not append global labels to metric labels when global label is not specified for any cluster
[info] - report only metrics which match the regex
[info] - remove only metrics which match the regex
[info] - should get the correct global label names and values for the given cluster
[info] - should add blank value for the cluster label for the cluster label is not specified for the cluster
[info] MetricsEvictionSpec:
[info] kafka lag exporter
[info] - should not report metrics for group members or partitions that no longer exist
[info] KafkaClientSpec:
[info] KafkaClient
[info]   getGroupOffsets
[info]   - returns None offsets for missing partitions and doesn't overwrite results for shared topic partitions
[info]   - returns distinct offsets when multiple groups subscribe to same partitions
[info]   - returns no offsets when a null offset is returned
[info] - getOffsetOrZero returns offsets of None (Option[Point]) for missing partitions
[info]   groupTopicPartition
[info]   - will default to fetching all topics
[info]   - will only fetch whitelisted topic when whitelist contains a single topic
[info]   - will only fetch non blacklisted topics
[info]   - will only fetch whitelisted topics when whitelist is a regex against multiple topics
[info]   - will exclude topics that match with blacklist regex
[info]   - will not return any topics if the whitelist is empty
[info]   getGroupIds
[info]   - will default to fetching all group IDs
[info]   - will only return one group when whitelist contains a single group
[info]   - will only return groups for whitelist that contains a regex that matches multiple groups
[info]   - will not return any groups when whitelist is empty
[info]   - will only fetch non blacklisted groups
[info]   - will exclude groups that match with blacklist regex
[info]   - will not return any groups when blacklist matches all
[info]   - will only fetch whitelisted and non blacklisted groups
[info]   - will include groups that match with whitelist regex and exclude groups that match with blacklist regex
[info] GraphiteEndpointSinkTest:
[info] GraphiteEndpointSinkImpl should
[info] - report only metrics which match the regex
[info] Run completed in 4 minutes, 25 seconds.
[info] Total number of tests run: 84
[info] Suites: completed 10, aborted 0
[info] Tests: succeeded 84, failed 0, canceled 0, ignored 0, pending 0
[info] All tests passed.
[success] Total time: 341 s (05:41), completed Mar 15, 2022 12:50:46 AM

Excellent idea. Thanks for your work on this PR. I merged another PR #297 that updated the base image so there's a small conflict.

I'll review this soon.

I resolved the conflict, should be good to review.
FYI, moving to openjdk:17 resolved the few remaining vulnerabilities on the docker image that were present in openjdk:8

Please merge master to run CI.

@guillaume-roland-cd I'm going to cut a release soon. We can release this whenever it's ready, but I just wanted to let you know!

@guillaume-roland-cd Do you think you'll have time to follow up on this PR? I could probably wrap it up if you like.

That's still in my todo list, but I struggle a little with the changes as I actually have very little knowledges on how to dev in Scala.
If you have time to start making some changes to make it better, or show me some examples, I would be able to continue.
Thanks!

@guillaume-roland-cd No problem! I'll push some changes to this branch soon.

@seglo I rebased from master, I've deployed the snapshot image on one of my cluster, there is no issues so far.
I made some changes on how we're building the docker image, so the image do not contain vulnerabilities anymore and is smaller.
What else need to be done here before we're able to merge the PR?

Thanks for updating the branch. It would be great to merge this soon. IIRC I was hoping to add more testing and DRY up a few more places, but that could be done as follow up work. I'm ok with the image building cleanup too but I want to learn more about the implications of using Corretto.

I've squashed all the commit, cleaned up the carriage return / spaces to made the diff shorter, I think we're good now.


Seeking Help running TAU instance

I know this doesn't really qualify for an issue, but if someone would be willing and has the time to help me merge TAU with the discord bot I am working on, that would be great.
https://github.com/Heptagram-Bot/Heptagram/issues/24

Taking a look at Heptagram (and correct me if I am wrong on any of this), "merging" the TAU code with it would be difficult, as first and foremost, Heptagram is a node/javascript based project, and TAU uses python.  One of the tricky bits of python and django in particular are the python modules and outside dependencies.  In this case, we have several modules (e.g.- django, django_rest_framework, django-channels, etc..) and rely on both postgresql and redis.  This is why I wrapped everything in docker containers.
My recommendation for integrating TAU with Heptagram, would be to automate grabbing TAU, setting up the containers, and running it.  That way, you dont have to implement all of the python requirements inside of the Heptagram project.  Perhaps this could be a simple first-start script that would be run the first time a user sets up Heptagram?  Would love to hear anyone else's thoughts on setting up this kind of integration.

I think your recommendation makes sense.

I would also love to hear anyone else's thoughts on setting up this kind of integration.


Update office-365-user-view-access-to-project-and-roadmap.md

GCC has shipped

@serdarsemen @SerdarSoysal

@SerdarSoysal PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


Fixed a tensorflow pooling test failure

This fixes a typo in the original PR causing incorrect values to be passed for any asymmetric parameter combinations in one of backward solvers.

@junliume
All configs from https://github.com/ROCmSoftwarePlatform/MIOpen/issues/1642#issuecomment-1197409178 are now passed. As this is urgent, then it can be merged as is, however, we shall add regression tests soon as well (I'll take care about those).
urgency_blocker, bug

@junliume Would you please try running tensorflow test on this branch?

@junliume Would you please try running tensorflow test on this branch?

@DrizztDoUrden it looks great!
Target //tensorflow/python/kernel_tests:pool_test_gpu up-to-date:
  bazel-bin/tensorflow/python/kernel_tests/pool_test_gpu
INFO: Elapsed time: 656.864s, Critical Path: 256.62s
INFO: 13595 processes: 1322 internal, 12273 local.
INFO: Build completed successfully, 13595 total actions
//tensorflow/python/kernel_tests:pool_test_gpu                           PASSED in 34.1s

INFO: Build completed successfully, 13595 total actions


Bug: React-Native SDK crash - 'Error when sending event: breezSdkEvent with body: { type = synced; }

Bug: React-Native SDK crash 'Error when sending event: breezSdkEvent with body: { type = synced; }
Current behavior
Experiencing periodic crashes on iOS while using hot reloads in a dev environment. This doesn't seemed to be triggered by anything the user is doing within application, as I've experienced the crash while the app is idling in the background.
The crash occurs seemingly at random - every 20 minutes or so. Requires restarting the bundler to fix.
error output:
[CoreFoundation] *** Terminating app due to uncaught
exception 'NSInternalInconsistencyException', reason: 'Error when sending event:
breezSdkEvent with body: { type = synced; }. RCTCallableJSModules is not set. This is
probably because you've explicitly synthesized the RCTCallableJSModules in RNBreezSDK,
even though it's inherited from RCTEventEmitter.'
*** First throw call stack:
(
0   CoreFoundation                      0x0000000180437330
__exceptionPreprocess + 172
1   libobjc.A.dylib                     0x0000000180051274
objc_exception_throw + 56
2   Foundation                          0x0000000180ae2ae8 -[NSMutableDictionary(NSMutableDictionary) classForCoder] + 0
3   [REDACTED]                          0x0000000104c87604 -[RCTEventEmitter sendEventWithName:body:] + 372
4   [REDACTED]                          0x000000010516d6cc $s9breez_sdk16BreezSDKListenerC7onEvent1ey0C3SDK0cF0O_tF + 220
5   [REDACTED]                          0x000000010516dc18 $s9breez_sdk16BreezSDKListenerC0C3SDK13EventListenerA<…>

Environment

breeztech/react-native-breez-sdk: 0.2.10
react-native: 0.72.7
expo: 49.0.18
ios deployment target: 13.0
simulator: iPhone 14 Pro - ios 16.4

Happy to provide more details if needed.

Experienced different crash with similar but more descriptive error message:
[CoreFoundation] *** Terminating app due to uncaught exception
'NSInternalInconsistencyException', reason: 'Error when sending event:
breezSdkEvent with body: { details = { error = "SQL: table sync.payments_external_info
has 7 columns but 6 values were supplied"; }; type = backupFailed; }.
RCTCallableJSModules is not set. This is probably because you've
explicitly synthesized the RCTCallableJSModules in RNBreezSDK, even though
it's inherited from RCTEventEmitter.'
*** First throw call stack:
(
0   CoreFoundation                      0x0000000180437330 __exceptionPreprocess + 172
1   libobjc.A.dylib                     0x0000000180051274 objc_exception_throw + 56
2   Foundation                          0x0000000180ae2ae8 -[NSMutableDictionary(NSMutableDictionary) classForCoder] + 0
3   [REDACTED]                          0x0000000100de7cd0 - [RCTEventEmitter sendEventWithName:body:] + 372
4   [REDACTED]                          0x00000001012cdd8c $s9breez_sdk16BreezSDKListenerC7onEvent1ey0C<…>

Which SDK version are you using ? have you switched back / forth between versions?

~Which SDK version are you using?~ have you switched back / forth between versions?

@dangeross
We've recently upgraded to 0.2.12 from 0.2.10.

Smooth sailing so far. Seems to be fixed. Will share if anything changes.
Thanks for the fix, @dangeross!


Optional replacement value for replaceAboveValue

I'm converting some raw sensor data into a percentage, and want to truncate values above 100 to 100%. This PR lets me do this using a new optional argument to replaceAboveValue:

sensor.soil_capacitance | offset(-244) | scale(0.3813) | removeAboveValue(100, 100)

If this looks reasonable, I could be convinced to add it to the other replace{Below,Above}{Value,Percentile} functions too.

add it to the other replace{Below,Above}{Value,Percentile} functions too

Maybe instead it makes more sense to add two new functions? PromQL has clamp_max and clamp_min, so maybe we can borrow that terminology.

I'm fine with both variants. Maybe separate functions is better, although modifying replace functions also make sense.


Fix incorrect macOS font encoding

macOS doesn't render extra characters correctly when set to UTF8, instead requiring UTF16. See more about the issue here: https://community.openfl.org/t/font-problem-on-mac-os-x/12919/7
Original fix found by Beckwahn

@jgranick This fix has been tested on multiple versions of macOS.


Chocolatey install Windows 11, Python 3.10.2

Preliminaries

[x ] I have followed the latest version of the
installation instructions.
[x ] I have checked the troubleshooting page and my problem is either not mentioned there,
or the solution given there does not help.

Description of error
Manim does not show up in the pip package list after installing via chocolatey (choco install manimce).
(Maybe?) Relevant Information:

Windows 11
Python version 3.10.2
Manimce version v.0.14.0

Installation logs

Terminal output
C:\WINDOWS\system32>

C:\WINDOWS\system32> pip install manim
WARNING: Ignoring invalid distribution -ip (c:\python310\lib\site-packages)
WARNING: Ignoring invalid distribution -ip (c:\python310\lib\site-packages)
Collecting manim
  Using cached manim-0.14.0-py3-none-any.whl (509 kB)
Collecting moderngl-window<3.0.0,>=2.3.0
  Using cached moderngl_window-2.4.1-py3-none-any.whl (365 kB)
Requirement already satisfied: pygments in c:\python310\lib\site-packages (from manim) (2.11.2)
Collecting tqdm
  Using cached tqdm-4.62.3-py2.py3-none-any.whl (76 kB)
Collecting networkx<3.0,>=2.5
  Using cached networkx-2.6.3-py3-none-any.whl (1.9 MB)
Requirement already satisfied: colour in c:\python310\lib\site-packages (from manim) (0.1.5)
Requirement already satisfied: watchdog in c:\python310\lib\site-packages (from manim) (2.1.6)
Requirement already satisfied: pydub in c:\python310\lib\site-packages (from manim) (0.25.1)
Collecting manimpango<0.5.0,>=0.4.0.post0
  Using cached ManimPango-0.4.0.post2-cp310-cp310-win_amd64.whl (4.0 MB)
Requirement already satisfied: decorator<6.0.0,>=5.0.7 in c:\python310\lib\site-packages (from manim) (5.1.1)
Requirement already satisfied: setuptools in c:\python310\lib\site-packages (from manim) (58.1.0)
Requirement already satisfied: requests in c:\python310\lib\site-packages (from manim) (2.27.1)
Collecting isosurfaces==0.1.0
  Using cached isosurfaces-0.1.0-py3-none-any.whl (10 kB)
Collecting moderngl<6.0.0,>=5.6.3
  Using cached moderngl-5.6.4-cp310-cp310-win_amd64.whl (139 kB)
Collecting Pillow
  Using cached Pillow-9.0.1-cp310-cp310-win_amd64.whl (3.2 MB)
Requirement already satisfied: screeninfo<0.7.0,>=0.6.7 in c:\python310\lib\site-packages (from manim) (0.6.7)
Collecting numpy<2.0,>=1.9
  Using cached numpy-1.22.2-cp310-cp310-win_amd64.whl (14.7 MB)
Collecting cloup<0.8.0,>=0.7.0
  Using cached cloup-0.7.1-py2.py3-none-any.whl (23 kB)
Collecting srt<4.0.0,>=3.5.0
  Using cached srt-3.5.1-py3-none-any.whl
Requirement already satisfied: click>=7.1 in c:\python310\lib\site-packages (from manim) (8.0.3)
Collecting rich>=6.0
  Using cached rich-11.2.0-py3-none-any.whl (217 kB)
Collecting mapbox-earcut<0.13.0,>=0.12.10
  Using cached mapbox_earcut-0.12.11-cp310-cp310-win_amd64.whl (68 kB)
Collecting click-default-group
  Using cached click_default_group-1.2.2-py3-none-any.whl
Collecting skia-pathops<0.8.0,>=0.7.0
  Using cached skia_pathops-0.7.2-cp310-cp310-win_amd64.whl (2.8 MB)
Collecting scipy
  Using cached scipy-1.8.0-cp310-cp310-win_amd64.whl (37.0 MB)
Collecting pycairo<2.0,>=1.19
  Using cached pycairo-1.20.1-cp310-cp310-win_amd64.whl (1.2 MB)
Requirement already satisfied: colorama in c:\python310\lib\site-packages (from click>=7.1->manim) (0.4.4)
Requirement already satisfied: glcontext<3,>=2 in c:\python310\lib\site-packages (from moderngl<6.0.0,>=5.6.3->manim) (2.3.4)
Requirement already satisfied: pyglet<2,>=1.5.8 in c:\python310\lib\site-packages (from moderngl-window<3.0.0,>=2.3.0->manim) (1.5.21)
Collecting pyrr<1,>=0.10.3
  Using cached pyrr-0.10.3-py3-none-any.whl (46 kB)
Requirement already satisfied: commonmark<0.10.0,>=0.9.0 in c:\python310\lib\site-packages (from rich>=6.0->manim) (0.9.1)
Requirement already satisfied: charset-normalizer~=2.0.0 in c:\python310\lib\site-packages (from requests->manim) (2.0.12)
Requirement already satisfied: urllib3<1.27,>=1.21.1 in c:\python310\lib\site-packages (from requests->manim) (1.26.8)
Requirement already satisfied: idna<4,>=2.5 in c:\python310\lib\site-packages (from requests->manim) (3.3)
Requirement already satisfied: certifi>=2017.4.17 in c:\python310\lib\site-packages (from requests->manim) (2021.10.8)
Collecting multipledispatch
  Using cached multipledispatch-0.6.0-py3-none-any.whl (11 kB)
Requirement already satisfied: six in c:\python310\lib\site-packages (from multipledispatch->pyrr<1,>=0.10.3->moderngl-window<3.0.0,>=2.3.0->manim) (1.16.0)
WARNING: Ignoring invalid distribution -ip (c:\python310\lib\site-packages)
Installing collected packages: tqdm, srt, skia-pathops, rich, pycairo, Pillow, numpy, networkx, multipledispatch, moderngl, manimpango, scipy, pyrr, mapbox-earcut, isosurfaces, cloup, click-default-group, moderngl-window, manim
  WARNING: Failed to write executable - trying to use .deleteme logic
ERROR: Could not install packages due to an OSError: [WinError 2] The system cannot find the file specified: 'C:\\Python310\\Scripts\\tqdm.exe' -> 'C:\\Python310\\Scripts\\tqdm.exe.deleteme'

WARNING: Ignoring invalid distribution -ip (c:\python310\lib\site-packages)

System specifications
System Details

OS (with version, e.g., Windows 10 v2004 or macOS 10.15 (Catalina)): Windows 11 Home 21H2
RAM: 8.00GB
Python version (python/py/python3 --version): 3.10.2
Installed modules (provide output from pip list):

WARNING: Ignoring invalid distribution -ip (c:\python310\lib\site-packages)
Package              Version
-------------------- ---------
anyio                3.5.0
argon2-cffi          21.3.0
argon2-cffi-bindings 21.2.0
asttokens            2.0.5
attrs                21.4.0
Babel                2.9.1
backcall             0.2.0
black                22.1.0
bleach               4.1.0
certifi              2021.10.8
cffi                 1.15.0
charset-normalizer   2.0.12
click                8.0.3
colorama             0.4.4
colour               0.1.5
commonmark           0.9.1
debugpy              1.5.1
decorator            5.1.1
defusedxml           0.7.1
entrypoints          0.4
executing            0.8.2
glcontext            2.3.4
idna                 3.3
ipykernel            6.9.1
ipython              8.0.1
ipython-genutils     0.2.0
jedi                 0.18.1
Jinja2               3.0.3
json5                0.9.6
jsonschema           4.4.0
jupyter-client       7.1.2
jupyter-core         4.9.2
jupyter-server       1.13.5
jupyterlab           3.2.9
jupyterlab-pygments  0.1.2
jupyterlab-server    2.10.3
MarkupSafe           2.0.1
matplotlib-inline    0.1.3
mistune              0.8.4
mypy-extensions      0.4.3
nbclassic            0.3.5
nbclient             0.5.11
nbconvert            6.4.2
nbformat             5.1.3
nest-asyncio         1.5.4
notebook             6.4.8
packaging            21.3
pandocfilters        1.5.0
parso                0.8.3
pathspec             0.9.0
pickleshare          0.7.5
pip                  22.0.3
platformdirs         2.5.0
prometheus-client    0.13.1
prompt-toolkit       3.0.28
pure-eval            0.2.2
pycparser            2.21
pydub                0.25.1
pyglet               1.5.21
Pygments             2.11.2
pyparsing            3.0.7
pyrsistent           0.18.1
python-dateutil      2.8.2
pytz                 2021.3
pywin32              303
pywinpty             1.1.6
pyzmq                22.3.0
requests             2.27.1
screeninfo           0.6.7
Send2Trash           1.8.0
setuptools           58.1.0
six                  1.16.0
sniffio              1.2.0
srt                  3.5.1
stack-data           0.2.0
terminado            0.13.1
testpath             0.5.0
tomli                2.0.1
tornado              6.1
tqdm                 4.62.3
traitlets            5.1.1
urllib3              1.26.8
watchdog             2.1.6
wcwidth              0.2.5
webencodings         0.5.1
websocket-client     1.2.3
wheel                0.37.1
WARNING: Ignoring invalid distribution -ip (c:\python310\lib\site-packages)

LaTeX details

LaTeX distribution (e.g. TeX Live 2020): MikTeX
Installed LaTeX packages:
N/A

FFMPEG
Output of ffmpeg -version:
ffmpeg version 5.0-essentials_build-www.gyan.dev Copyright (c) 2000-2022 the FFmpeg developers
built with gcc 11.2.0 (Rev5, Built by MSYS2 project)
configuration: --enable-gpl --enable-version3 --enable-static --disable-w32threads --disable-autodetect --enable-fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp --enable-lzma --enable-zlib --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth --enable-sdl2 --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxvid --enable-libaom --enable-libopenjpeg --enable-libvpx --enable-libass --enable-libfreetype --enable-libfribidi --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf --enable-cuda-llvm --enable-cuvid --enable-ffnvcodec --enable-nvdec --enable-nvenc --enable-d3d11va --enable-dxva2 --enable-libmfx --enable-libgme --enable-libopenmpt --enable-libopencore-amrwb --enable-libmp3lame --enable-libtheora --enable-libvo-amrwbenc --enable-libgsm --enable-libopencore-amrnb --enable-libopus --enable-libspeex --enable-libvorbis --enable-librubberband
libavutil      57. 17.100 / 57. 17.100
libavcodec     59. 18.100 / 59. 18.100
libavformat    59. 16.100 / 59. 16.100
libavdevice    59.  4.100 / 59.  4.100
libavfilter     8. 24.100 /  8. 24.100
libswscale      6.  4.100 /  6.  4.100
libswresample   4.  3.100 /  4.  3.100
libpostproc    56.  3.100 / 56.  3.100

Additional comments

I eventually got it working by specifying Python 3.9 after installing via choco.
py -3.9 pip install manim

Can you post the chocolatey log/terminal output when you run choco?

Chocolatey v0.12.1
Installing the following packages:
manimce
By installing, you accept licenses for the packages.
manimce v0.14.0 already installed.
 Use --force to reinstall, specify a version to install, or try upgrade.

Chocolatey installed 0/1 packages.
 See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Warnings:
 - manimce - manimce v0.14.0 already installed.
 Use --force to reinstall, specify a version to install, or try upgrade.

Closing due to inactivity.

Uploading chocolatey.log…
Here are the logs from the ProgramData Folder.

You didn't successfully upload the logs. Can you try again?

@bibbca Sorry, for the late reply. I have looked in to the logs you posted and found that Python 3.6 is used, which isn't support by manim for a long time now.
2022-02-16 12:29:36,980 3808 [INFO ] - Found Python 3.6 from Registry
2022-02-16 12:29:36,985 3808 [INFO ] - Found Install Path - C:\Program Files\Python36\python.exe
2022-02-16 12:29:36,985 3808 [INFO ] - Found python at 'C:\Program Files\Python36\python.exe' using it.
2022-02-16 12:29:37,018 3808 [INFO ] - Using python version Python 3.6.4 (v3.6.4:d48eceb, Dec 19 2017, 06:54:40) [MSC v.1900 64 bit (AMD64)]

I have updated the installation script to ignore python 3.6 now https://github.com/naveen521kk/au-packages/commit/3a0ae931474b4b3d0842df3f4bf4d149a28e4685 and pushed a new version with those changes https://community.chocolatey.org/packages/manimce/<IP_ADDRESS>20312.
Now, you can run choco install manimce --force to update.

Closing due to inactivity.


Submission forms for Academic Programs, Course Materials, and Research Centers/Institutes

On the Academic Programs, Research Centers & Institutes, and Course Materials content type submission forms, Academic discipline should be required. On all other forms, Academic Disciplines should be optional.

There should be pre-selected content on these forms as well that cannot be changed (okay if only shows up in the admin, but then the forms should be set not show these options, and include up to 2 instead of 3):

Academic Programs - Curriculum should be preselected as a choice under Sustainability Topic(s)
Course Materials - Curriculum should be preselected as a choice under Sustainability Topic(s)
Research Centers/Institutes - Research should be preselected as a choice under Sustainability Topic(s)

Number 1 above (Academic Disciplines being optional in most content types) is a high priority, since it is messing up how we can submit content.

1/8/16 update - no change.

What do you mean?

Basically, we need to classify Academic Programs and Course Materials under the "Curriculum" topic no matter what, even if the user doesn't check "Curriculum" on the form. Same goes for Research Centers and Institutes always falling under the "Research" content type.

So the way I implemented this was to automatically populate the topic input with the required topic and then disable deletion of that topic, but allow deletion of others. Give it a try...


Some Electron apps cannot access the network

Describe the bug
Some Electron apps that I attempt to run are unable to access the network. This includes Discord, Google Play Music Desktop Player.
If started in the terminal, Discord repeatedly shows the following error:
[WebContents] did-fail-load -2 ERR_FAILED retry in 1000 ms
[WebContents] retrying load https://ptb.discordapp.com/app?_=1595990016446

GPMDP shows no errors, but refuses to load.
Element Desktop still works.
To Reproduce
Steps to reproduce the behavior:

Install Discord
Attempt to start Discord
Observe the infinite spinner as it attempts to make HTTP requests

Expected behavior
The app is able to access the internet and launches properly.
Screenshots

Additional context
This happened soon after a routine rebuild.
Notify maintainers

Metadata

system: "x86_64-linux"
host os: Linux 5.7.10, NixOS, 20.09pre236138.970b2b853d4 (Nightingale)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.7
channels(root): "nixos-20.09pre236138.970b2b853d4, home-manager"
channels(anna): ""
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

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

It's not just electron. No Steam browser pages load either.

Duplicate of #93955


persist game state in localstorage

mostly just hook swap, useState => useLocalStorage
seems to work. needs testing.

ah, i left playAgain commits in. i will rebase after that pr is merged or closed

a nice plus of persisting is that refreshing re-opens the EndGame popup with streak info

ok, rebased. i tested it some more yday, should be good


polish-notation

Student, group: Nikita Zadorotskas, 3530901/90203
URL: https://github.com/zadorotskas/polish-notation
Git approach: git-flow

`+