HDDS-4145. Bump version to 1.1.0-SNAPSHOT on master

What changes were proposed in this pull request?
s/0.6.0-SNAPSHOT/1.1.0-SNAPSHOT/g
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4145
How was this patch tested?
CI build: https://github.com/elek/hadoop-ozone/actions/runs/223327025

[ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 10.29 s <<< FAILURE! - in org.apache.hadoop.ozone.recon.api.TestEndpoints
[ERROR] testGetDatanodes(org.apache.hadoop.ozone.recon.api.TestEndpoints)  Time elapsed: 0.858 s  <<< FAILURE!
java.lang.AssertionError: expected:<1> but was:<0>

Also failed in here:
https://github.com/elek/ozone-build-results/blob/master/2020/08/25/2533/unit/hadoop-ozone/recon/org.apache.hadoop.ozone.recon.api.TestEndpoints.txt
and here:
https://github.com/elek/ozone-build-results/blob/master/2020/08/22/2499/unit/hadoop-ozone/recon/org.apache.hadoop.ozone.recon.api.TestEndpoints.txt

LGTM, +1. Thanks @elek for the patch.

Thank You @elek for the contribution and @xiaoyuyao for the review.


Auth getToken is not refreshing expired token on iOS

Calling getToken should refresh expired tokens on iOS but it keeps returning the same expired token.  I have not tried it yet on Android so I don't know if this is iOS only.

Thanks for the report. Is this with the npm module or master branch?

This is v2.3.3 from npm.

This appears to be working correctly on Android.

Note that I deleted the comment about it working in Android because my test was invalid. I retested and confirmed that it is broken on Android as well.

Interesting... can you share how you're testing it so we're working off the same baseline?

I'm testing using code baked into a much larger app that will take some time to split out.  Are you not seeing the same results?

No, I haven't seen this myself. If you have screenhero, I'm glad to hop on and help debug, if you can't share it.

I haven't had a chance to debug this yet.  Hopefully I can tackle that this evening.  I'll let you know if I'm having any issues.
If you have an idea of what might be the issue to point me in the right direction before I get started, let me know.

Well this turned out to be user error.  getToken is refreshing the token.
It is worth noting that the behavior of iOS and Android are different.  iOS will only refresh the token if it is expired and Android will force refresh every time.  Both platforms ignore the force refresh boolean from the JS documentation.


Group energy sensors stopped working

System Health details
System Information

version
core-2023.12.3

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.11.6

os_name
Linux

os_version
6.1.63-haos

arch
x86_64

timezone
Europe/Berlin

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

GitHub API Calls Remaining
5000

Installed Version
1.33.0

Stage
running

Available Repositories
1355

Downloaded Repositories
31

Home Assistant Cloud

logged_in
false

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Home Assistant OS 11.2

update_channel
stable

supervisor_version
supervisor-2023.11.6

agent_version
1.6.0

docker_version
24.0.7

disk_total
228.5 GB

disk_used
50.2 GB

healthy
true

supported
true

board
generic-x86-64

supervisor_api
ok

version_api
ok

installed_addons
Z-Wave JS (0.4.3), Studio Code Server (5.14.2), Terminal & SSH (9.8.1), ESPHome (2023.11.6), Samba Backup (5.2.0), phpMyAdmin (0.9.0), MariaDB (2.6.1)

Dashboards

dashboards
7

resources
24

views
34

mode
storage

Recorder

oldest_recorder_run
10. März 2023 um 09:35

current_recorder_run
19. Dezember 2023 um 08:38

estimated_db_size
9526.28 MiB

database_engine
mysql

database_version
10.6.12

Checklist

[X] I have read the FAQ to see if there is a known solution to my problem.
[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..

Describe the issue
Energy sensors that powercalc creates automatically stopped updating correctly.

I have a all yaml configuration
The problem started very likely after 1.9.6, downgrading helped for a few days but not for good
currently I am on V1.9.10 with several re-installs (without deleted the integration before though)
For the groups in question power sensors and energy sensors have been correctly created by powercalc

Excerpt from the error logs seem to point towards this: energy calc is done and increasing ('new value..') but then the sensor goes back to an initial value of always the same value ('recalculate ...').
here are some of the relevant lines:
It happens to nested groups but also sensors for just a single group with several sensors underneath.
It does not happen though for all groups consistently. In my case I have 4 top level groups and one of them seems to work. There is no pattern that I can see why it applies to only 3 out of the 4.
The energy sensor always goes back to an initial value but rounds to integer of that starting value.
Reproduction steps

it happens consistently
also after multiple powercalc re-installs
also after complete re-sarts of the system
...

Debug logs
2023-12-19 09:10:03.876 DEBUG (MainThread) [custom_components.powercalc.sensors.group] sensor.technik_energy: New value: 2836.1160

2023-12-19 09:11:03.898 DEBUG (MainThread) [custom_components.powercalc.sensors.group] sensor.technik_energy: Recalculate, current value: 2836

2023-12-19 09:11:03.902 DEBUG (MainThread) [custom_components.powercalc.sensors.group] sensor.technik_energy: New value: 2836.1192

2023-12-19 09:12:00.860 DEBUG (MainThread) [custom_components.powercalc.sensors.group] sensor.technik_energy: Recalculate, current value: 2836

It keeps going like this.

Diagnostics dump or YAML config
no GUI used

I am closing this issue and will further investigate myself first.
It could ne that I excluded some energy sensors from recorder.
Just to sure which sensors need to be recorded:

Do you need power sensors to be recorded or can they be excluded in the recorder.yaml?
Do you. need energy sensors to be recorded - particularly in the light that those are being tracked in LTS anyhow (or is it required to record regular energy sensors to get them transferred into LTS)?

Given that a sizable piece of my database is being used by powercalc sensors I was trying to reduce some of the load and might have overdone that.

I am closing this issue and will further investigate myself first.
It could ne that I excluded some energy sensors from recorder.
Just to sure which sensors need to be recorded:
Do you need power sensors to be recorded or can they be excluded in the recorder.yaml?
Do you. need energy sensors to be recorded - particularly in the light that those are being tracked in LTS anyhow (or is it required to record regular energy sensors to get them transferred into LTS)?
Given that a sizable piece of my database is being used by powercalc sensors I was trying to reduce some of the load and might have overdone that.

I am not 100% sure, but I don't think they need to be in recorder per se.
LTS is not directly used for the group power or energy states. Just all the current states of the child entities, they are summed together whenever one of the child entities changes state.
You can set following option to decrease state size a lot:
powercalc:
  disable_extended_attributes: true

Also see https://homeassistant-powercalc.readthedocs.io/en/latest/configuration/global-configuration.html
And also decrease force_update_frequency to cause less state writes to the DB.

Many thanks. I will keep digging.
I was afraid of using  disable_extended_attributes because I never understood what downside I get when limiting it.
On LTS: I use 2 graphs created with custom:sankey-chart, one for actual power distribution and one for energy splits in combination with energy-period-selector to filter by certain time periods.
In the meantime I have deleted the regular energy recordings for beyond the past 30 days.
Nonetheless I get the graphs for periods before that time period. I assume that this is because the energy graph then displays data from LTS which seems to be recorded in the database anyhow.
Questions:

If you record this historical data separately  in .storage/powercalc_group file, I assume that this is in addition to the LTS recordings? Or does it have any relationship and they need each other?
Could I then delete your file from time to time without causing any other problems?
Is there a particular reason for doing the double recording (just out of interest)?

Man thanks again for your cool powercalc project!!!!


Inter region connectivity ?

Is it possible to place VWAN hubs in different regions and achieve spoke to spoke connectivity between regions ?

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

ID: 6a32c05e-04ab-f76f-8dd1-cbffed44da06
Version Independent ID: 906d444a-332d-2254-7093-8dc817bb1026
Content: Architecture: Global transit network architecture - Azure Virtual WAN
Content Source: articles/virtual-wan/virtual-wan-global-transit-network-architecture.md
Service: virtual-wan
GitHub Login: @cherylmc
Microsoft Alias: cherylmc

Thanks for the feedback and bringing this to our notice . At this time we are reviewing the feedback and will update the document as appropriate .

@Andriy-dev You can only have 1 hub per Azure region, but hubs in different regions can connect to each other. This feature is currently in preview. You can find more information Here.

@Andriy-dev We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


TRG 1.01 - appropriate README.md file

Version Mismach within ReadMe

software version doubeled

Basic description of repository and its content (Why you need Daps-Server and for what is it?) Why the needed

where to get this infrastructure?

Notice: Tractus-x relies on an IDS-compatible architecture. In that context, a DAPS is needed as an identity server. In this project, we use Fraunhofer's DAPS implementation (https://github.com/Fraunhofer-AISEC/omejdn-server#readme).

why the things with frauenhofer DAPS?

Installation instructions to get component working

how to use daps-sever

if there dependencies how to enable?

Removed the version section as it is generated inside charts/daps-server
You just need to add image from fraunhofer in values.yaml & get it deployed.
There are no dependencies

I don't like the Readme very much either but i do have to assume that the reference to frauenhofer is good enough. Please revisit the README @adkumar1 for the next release and challange it with someone who doesn't know daps but needs to use it.
Closing as version is removed, no dependencies to enable


more specific examples

https://github.com/ubsuny/MLFringe-Contrast-CP2P2024/blob/2492e3a61cf4dfc9ad530770b6bdd274d1bb9cd1/documentation.md?plain=1#L3
Can you give some more specific examples?

@laserlab , I will be using np.complex64, and maybe np.complex128 or even np.complex256. And also, float64 and so on. As I have huge data so I need to use them. Also I have complex exponentials and I need complex data types.


Update README.md for sample_spl2_pii_masking app

Updated to change how to access the app. Users don't need to install the app.

@PKing70 - Fixed the title

Ready to merge


Prometheus in service task can't talk to host metrics via "localhost"

File: engine/admin/prometheus.md, CC @mstanleyjones
This docker engine metrics shows a prometheus.yml file that points to localhost for engine metrics on linux. However, from the prom container, it can't access host's localhost, only the containers localhost, and gets a connection refused.
Not sure the best way to get a swarm service to see the localhost IP of the engine.

Run with --net=host probably. That will bind the port on the Docker host directly. Can you give it a try and let me know?

passing --network=host
container cannot be disconnected from host network or connected to host ne

it works just not as service. Boh too many parameters but i dont see the more important
node cpu,disk,memory,bandwidth usage

Closing this ticket due to its age, and the impending refactor. If you think this is in error, feel free to reopen. Thanks!

Sorry for reopening this, but documentation is wrong and should be corrected.
As previous people have said, you can only connect to the docker metrics through container's localhost if you use the hosts network, which doesn't look very doable in a production environment, IMO.
Could you provide the standard way to do this by fixing the documentation?
Thanks a lot!

On Mac/Windows you can use host.docker.internal to connect to localhost because --net=host only works on Linux. However, I completely agree with @johnyserpa. There has to be a standard way to implement this functionality in a production environment

please update the docs. its not working!

Always not working!

What is the correct way of doing this in Docker Swarm mode?


Question on cft with autoscale for auth code

As per document "before launching the templates"
obtain the auth code for a bundle that supports the number of firewalls that might be required for your deployment.
Does this means this works only for BYOL or am I misunderstanding, want to test for usage based.

@niteenkole this should work fine with PAYG the PAYG licensing or BYOL AMIs.

In Aws I am not able to fire panorama 10+ with EULA it’s just gives me option of BYOL
Any help much appreciated

Ah, sorry. I thought you meant the VM-Series. Yes, Panorama is only BYOL license. If you need Evaluation licenses for your testing you can get these from a Palo Alto Networks Partner, or your Palo Alto Networks Account team.
If you want to email me<EMAIL_ADDRESS>your Name, Contact Details, and Organizations Name I can make contact with your account team for them to contact you.

Ok thanks.
No where it’s documented in aws or even at PA that it’s BYOL.

I'll speak to the team and see if we can get this mentioned in the text description too. It is flagged on the AWS Marketplace, but I'll see if we can get this improved in the supporting documentation too.

Hi
Thanks mailed you from my company ID
See all this template demo or on your YouTube demo no where it says panorama in AWS is only BYOL so its kind of struggle who wants to test.

No problem, thanks. I'll track down the account team for you, and get them to make contacts with you.
I've also asked our Technical Marketing engineers to take a look at our documentation etc, to make the BYOL requirement more obvious, thanks for the input on this.


Language-agnostic test suite

It would be great to have a language-agnostic test suite for verifying the correctness of encoding/decoding algorithms. It would be especially valuable for people who want to implement blurhash for some new language.
Each test case could have e.g.

source image
expected blurhashes with different X,Y (e.g. a json/csv file)
expected decoded image from one of the blurhashes

Duplicate of #38


create_endpoint_config doesn't support Serverless deployment

It is currently not possible to use moto to mock create_endpoint_config if the endpoint config involves using serverless deployment.
To reproduce:
from moto import mock_sagemaker
import boto3

with mock_sagemaker():
    client = boto3.client("sagemaker")
    endpoint_conf_name = 'test'

    client.create_endpoint_config(
        EndpointConfigName=endpoint_conf_name,
        ProductionVariants=[
            {'VariantName': 'dummy',
                'ModelName': 'dummy',
                'ServerlessConfig': {
                'MemorySizeInMB': 1024,
                'MaxConcurrency': 20
            }}
        ],
    )

Stacktrace:
self = <moto.sagemaker.models.FakeEndpointConfig object at 0x7f90f8934850>, production_variants = [{'ModelName': 'test', 'ServerlessConfig': {'MaxConcurrency': 20, 'MemorySizeInMB': 6144}, 'VariantName': 'default-variant-test'}]

    def validate_production_variants(self, production_variants):
        for production_variant in production_variants:
>           self.validate_instance_type(production_variant["InstanceType"])
E           KeyError: 'InstanceType'

ml_framework/venv/lib/python3.7/site-packages/moto/sagemaker/models.py:401: KeyError

The error is triggered when moto creates a new FakeEndpointConfig: https://github.com/spulec/moto/blob/930c58bd1366b073e8630a82fa7f34624babd867/moto/sagemaker/models.py#L399-L401
When deploying using ServerlessConfig, there is no InstanceType present in the ProductionVariant (see documentation: https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/sagemaker.html#SageMaker.Client.create_endpoint_config)
Ideally, we should condition based on whether we have InstanceType or ServerlessConfig in the ProductionVariant, and add some checks on the Serverless Config parameters.
Happy to get a PR out to fix this :)

Hi @arnaudstiegler, thanks for raising this. PR's are always welcome - let me know if you need any help or pointers.

Sounds good, will work on this

@bblommers Is there a guide for contribution? Can I simply open a PR against the repo or should I fork it instead?


(maint) This was prevent bolt/pal from being required in module testing.

CLA signed by all contributors.


Please add license

Thank you for TiBUdecrypter, works fine here.
Can you add a free software license of your choice, so everyone knows what he can do with your software and what not?
Thank you,
Thomas

A License would be great :-)
Amazing program, thank you.

I'll likely be adding the MIT license shortly. Sorry for how long it took me to remember to do this :)


Adding old gods bottom

This contains all of the Old Gods branch changes, not just the object stuff, so we definitely don't want to merge it it into dev yet. I'll close this and we can start it again tomorrow.


filetype: jupyterlab config and sublime config are not recognized

Problem: jupyterlab config and sublime config are not recognized
Solution: Add patterns for jupyterlab config and sublime config

thanks


2 ➡ 3

➡ Forward port
Port ign-cmake2 to main
Branch comparison: https://github.com/ignitionrobotics/ign-cmake/compare/main...ign-cmake2
Note to maintainers: Remember to Merge with commit (not squash-merge or rebase)

There were a few PRs that have been merged to ign-cmake2 since this forward port was opened, can you update this PR so that we can forward port these new PRs as well? I believe we are only missing #150, #158, and #159.

can you update this PR so that we can forward port these new PRs as well?

Done :+1:


Memory leak

The following program will leak memory, but can be switched to not leak memory as noted in the comments:
use "time"

actor Main
  new create(env: Env) =>
    Timers()(Timer(Notify(ReceiverConcrete), 20_000_000, 20_000_000))

class Notify is TimerNotify
  let _receiver: Receiver
  new iso create(receiver: Receiver) => _receiver = receiver
  fun ref apply(timer: Timer, count: U64): Bool =>
    _receiver.receive(recover iso Array[U8].init(0, 400_000) end)
    true

trait tag Receiver
  be receive(string: Array[U8] iso) // change this to val for stable memory

actor ReceiverConcrete is Receiver
  be receive(string: Array[U8] val) => None // OR change this to iso for stable memory

It should be noted that the "doesnt leak memory version" takes a while to reach "memory equilibrium" so it memory growth slowly occurs. The test program will rapidly leak memory with the "bad" version and you should see over a gig in memory used within a minute of running whereas the "good" version will have significantly less usage (it will stabilize at less than 100 megs within a few minutes).
The issue stems from the call going through a trait that is iso and traced as such and the receiving end being a val and then we don't do the correct tracing and objects end up not being freed.
In Zulip @jemc stated:

I can confirm that from a LLVM IR perspective, we will call pony_traceknown with PONY_TRACE_MUTABLE when the trait parameter type is iso, even when the concrete type's parameter type is val (and thus, PONY_TRACE_IMMUTABLE would be the correct trace kind to use)
I think probably the best way to solve this would be to change the selector painting / virtual tables around in such a way that we end up with a different selector color / virtual table index / message id for the val case vs the iso case
Even though they are compatible in the type system, they are not compatible at runtime and need to be treated separately.

Full zulip thread is at: https://ponylang.zulipchat.com/#narrow/stream/189985-beginner-help/topic/Debugging.20excessive.20memory.20usage

@jemc did you ever do a write up? i don't remember our agreed upon solution.

A full "non hack" fix for #1118 might not fix this leak.

Yes, I suspect that as we iteratively bring back the optimization removed in #4247 this memory leak will likely come back as well - I think it likely still needs a separate fix.

In fact, the minimal example in the ticket description should come back in the very first iteration of bringing back the optimization, as Array[U8] very obviously cannot contain an actor.


Support for mainnet/testnet address on any derivation

The device is able to process requests for setting the network version to use when calculating the address from the device's pk.
I added a new method to the BlockstackApp object:
setNetworkVersion(path: string, version: number)
Although path is not used, It may be required later.
version is a number that must be either:

Mainnet: 22

or

Testnet: 26
the default value is Mainnet.

I noticed that the package stacks.js is not part of the dependencies for the js lib, I am not sure if it is intentional. We may include that package in order to use this enum instead of plain number( the internal implementation checks that the version value is correct if not it returns an invalid data error).

Tests fail because of snapshoots, although values are equal.

I noticed that the package stacks.js is not part of the dependencies for the js lib, I am not sure if it is intentional. We may include that package in order to use this enum instead of plain number( the internal implementation checks that the version value is correct if not it returns an invalid data error).

To this point, if you're only using the types exposed, I believe you can use TypeScript's import type { AddressVersion } from '@stacks/transactions';. So you get the types but not the bundled js.

It is ready. now the getAddress/showAddress takes in a new AddressVersion parameter.


make EventSource optional

When using kvlt on the Microsoft Edge browser, the compiled javascript fails because EventSource is not supported and the code tries to 'require' the eventsource module (presumably for node.js). When removing the SSE support in a fork (we don't actually use it in our code), the problem no longer appears. A clean way to turn off the SSE support would allow us avoid maintaining a fork.
I've noticed that you have created a (possibly?) similar ticket for WebSocket (#20). If you have ideas on how you see options for turning on/off various features, we'd be happy to try to create a PR for this.

@loomis So I included both of those features (SSE and websockets), in retrospect, maybe a little exuberantly, despite not using them myself.  There is a snapshot (0.2.0-SNAPSHOT) and corresponding branch (wip/smaller) which just removes that functionality and updates the deps.  I'm tempted to release the snapshot at some point - would that break anything for you?
If so, (delay)'ing the requires and derefing them on first use may be the simplest approach.

@moea Just creating a release without those features would currently work for us.  However, we're actually planning to start using websockets in the next few weeks, so that would be a very short term fix for us.  I'll look to see if the delays would be easy to add.

@moea Unfortunately, it doesn't look like any solution with delay will work for clojurescript.  The first issue is that require can only appear at the top-level in clojurescript.  Therefore, it can't appear in a delay and necessitates that the user explicitly require the kvlt.platform.* namespaces. Even with that, clojurescript doesn't have any of the resolve-like functions, so the correct request! function can't be looked up dynamically (at least not without a lot of direct hacking with javascript).
The only moderately clean solution that I can find is to separate the websocket! and event-source! functions into their own namespaces. Users would then be able to choose which features they need, but with the inconvenience of requiring more than just the current kvlt.core namespace.
Would you be open to a split-namespace solution? Or perhaps you can think of something I've missed with delayed loading in clojurescript.

@loomis Ah, sorry, I wasn't being clear - I meant delaying the calls to js/require in the cljs modules, e.g:
(def websocket (delay (js/require "websocket"))

And then explicitly deref'ing the websocket var within that module, at the point of use - everything would appear fine on platforms where the import will be unsuccessful, up until the point where the functionality is exercised.

(the only caveat would be if there are module-level uses of the required Node modules, though if there are, wrapping them in functions or just delaying them, also, shouldn't be too much trouble)

@moea I've generated a PR (#26) with changes to delay the loading of EventSource and WebSocket.
I've added some logging to the delay to give the user some more specific feedback when either library is unavailable; the default "Uncaught ReferenceError: require is not defined" is not very helpful in understanding the problem. Currently the code re-throws the exception, but could be changed to eat the exception or generate one with a different method.
Getting the constructor to work from the delayed value was a bit difficult.  In the end I had to bind a local symbol to get the constructor syntax to work.  There's some magic going on there, that I don't understand and didn't have time to dig into.  If you know a better incantation that doesn't require the local binding, please let me know.
The modified library works for us, even with the Edge browser. I've seen that the CI tests pass as well.  I haven't done much other testing, so you might want to take it for a real-world spin before merging it.


Fix validator tests

Coverage increased (+0.2%) to 77.137% when pulling 889912f8ef4038d76ea7173c38218f9e0f28e93a on jmedved:contiv-crd into 57cb50059e0f4abcba0da7886e904cb1bae26e86 on contiv:contiv-crd.


fixes and more todos

Current coverage is 98.74% (diff: 94.11%)

Merging #11 into master will increase coverage by 0.04%

@@             master        #11   diff @@
==========================================
  Files             1          1
  Lines           306        318    +12
  Methods           4          4
  Messages          0          0
  Branches         49         51     +2
==========================================
+ Hits            302        314    +12
  Misses            1          1
  Partials          3          3

Diff Coverage
File Path

•••••••••  94%
src/SplitSharp/StringSplitter.cs

Powered by Codecov. Last update 0ee66ba...fdebcbe


node module updates, screenshot update.

FYI: There is a new commit added to this PR that includes a whole new tutorial. I didn't consider this when pushing to QA.

I will close this PR. Please create PR just for the updates to existing tutorial (if you need to reset fork there is a button in the plugin for this). For the new tutorial, please send me email with link to tutorial in QA and I will review.


:memo: Adding/Fixing Links for Badge

Codecov Report
Base: 97.87% // Head: 97.87% // No change to project coverage :thumbsup:

Coverage data is based on head (98f2896) compared to base (d61795a).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main       #6   +/-   ##
=======================================
  Coverage   97.87%   97.87%
=======================================
  Files           3        3
  Lines         235      235
=======================================
  Hits          230      230
  Misses          4        4
  Partials        1        1

Flag
Coverage Δ

unit-tests
97.87% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


⚠ LPDM Handbook (hosted on Divio) has degraded performance

In 0c54693, LPDM Handbook (hosted on Divio) (https://repohubdev.tk) experienced degraded performance:

HTTP code: 500
Response time: 5400 ms

Resolved: LPDM Handbook (hosted on Divio) performance has improved in aba3d96.


Blockstore stops advancing

This seems to be related to #2595 but only Blockstore stops advancing; Headers, Consensus and Wallet synchronise to the network height as the network advances.
Logs: https://stratisplatform-my.sharepoint.com/:u:/p/maciej_zaleski/Ebzl-9y8OIxBupgxU_RyQeYBiM_eUPVXvuaWJ8ko2KAbpw?e=x03fq9

This problem has not reoccurred and can be closed due to it not not being reproducible.


Chose an appropriate DATA_SHAPE

Previous behaviour leads to various memory errors. It happened time to time 'cause of unreasonably large choice of the DATA_SHAPE. The average maximum height of lungs for a grown man, according to this research (Table 2), is 282mm with std equals to 22mm and median 274mm (Table 2). Assuming normal distribution, 3 sigmas aside the mean will lead to the probability of case h belong to the interval P{|282 - h| <= 66} ~= 0.9974. Taking into an account the fact that all algorithms which were described (not only implemented ones) works with spacing on z-axis >= 0.9, therefore, having an upper bound value of (282 + 66) / 0.9 = 386 (voxels) for z-axis should be enough for all cases.
I've made DATA_SHAPE to be (512, 512, 512) which should fit in memory while having reserved space for the z-axis.
CLA

[x] I have signed the CLA; if other committers are in the commit history, they have signed the CLA as well

How does this compare to #307? :)

Failing.

Based on this comment it seems like best option is to add to here, just the bits of code from #308  that will fix the current error... agree?

@reubano, done, but I've added all code from #308, 'cause in other cases, it'll lead to wrong tests for a new calculate_volumes which now works with real-world units.

============================= test session starts ==============================
platform linux -- Python 3.6.3, pytest-3.1.3, py-1.5.2, pluggy-0.4.0
rootdir: /app, inifile:
collected 63 items
src/tests/test_classification.py ...
src/tests/test_classification_3dlrcnn.py ...
src/tests/test_cropping.py ...
src/tests/test_endpoints.py ..x.....
src/tests/test_generators.py .........
src/tests/test_grt123_preprocess.py ...
src/tests/test_identification.py xxx
src/tests/test_improved_segmentation.py ..
src/tests/test_loading.py .......
src/tests/test_preprocess_dicom.py ....
src/tests/test_segment_evaluate.py ........
src/tests/test_segmentation.py ....xxx
src/tests/test_volume_calculation.py ...
=========================== short test summary info ============================
XFAIL src/tests/test_endpoints.py::test_identify
  Test was stopped after timeout
XFAIL src/tests/test_identification.py::test_identify_nodules_001
  Test was stopped after timeout
XFAIL src/tests/test_identification.py::test_identify_nodules_003
  Test was stopped after timeout
XFAIL src/tests/test_identification.py::test_identify_luna
  Test was stopped after timeout
XFAIL src/tests/test_segmentation.py::test_nodule_segmentation
  Test was stopped after timeout
XFAIL src/tests/test_segmentation.py::test_lung_segmentation
  Test was stopped after timeout
XFAIL src/tests/test_segmentation.py::test_stop_timeout
  Test was stopped after timeout
=============================== warnings summary ===============================
src/tests/test_endpoints.py::test_identify
  /app/src/tests/../../src/preprocess/extract_lungs.py:34: RuntimeWarning: invalid value encountered in less
    truncate=2.0) < intensity_th
src/tests/test_identification.py::test_identify_nodules_001
  /app/src/tests/../../src/preprocess/extract_lungs.py:34: RuntimeWarning: invalid value encountered in less
    truncate=2.0) < intensity_th
src/tests/test_identification.py::test_identify_nodules_003
  /app/src/tests/../../src/preprocess/extract_lungs.py:34: RuntimeWarning: invalid value encountered in less
    truncate=2.0) < intensity_th
-- Docs: http://doc.pytest.org/en/latest/warnings.html
============== 56 passed, 7 xfailed, 3 warnings in 991.87 seconds ==============

Tests look good now. Just the styling that is making travis unhappy
$ flake8 prediction
prediction/src/algorithms/evaluation/evaluate_detection.py:233:80: W291 trailing whitespace
prediction/src/algorithms/evaluation/evaluate_detection.py:246:20: E999 SyntaxError: invalid syntax
The command "flake8 prediction" exited with 1.

$ pycodestyle prediction
prediction/src/algorithms/evaluation/evaluate_detection.py:233:80: W291 trailing whitespace

Yes, but this was fixed in PR #306

@reubano, I'm a bit confused with all those permutations, but it seems to be done :)

Yes, sorry for all the back and forth. The main idea was to just include the relevant (and minimum set of) code changes needed to get the travis test passing.

Glad to help :)

Great work!!


added log to runLocally, added test for tarring folder/

console.log packages/ssh-pool/src/Connection.js:414
    Running "cd shipit/packages/ssh-pool/tests/__fixtures__ && tar -czf foo.tar.gz anotherfolder1604264657030" on locally.

console.log packages/ssh-pool/src/Connection.js:414
    Running "mkdir -p ./" on host "ssh.example.com".

console.log packages/ssh-pool/src/Connection.js:414
    Running "ssh -i /home/user/.ssh/id_rsa<EMAIL_ADDRESS>"mkdir -p ./"" on locally.

console.log packages/ssh-pool/src/Connection.js:414
    Running "cd shipit/packages/ssh-pool/tests/__fixtures__ && scp -i /home/user/.ssh/id_rsa foo.tar.gz user@ssh.example.com:./" on locally.

console.log packages/ssh-pool/src/Connection.js:414
    Running "cd shipit/packages/ssh-pool/tests/__fixtures__ && rm foo.tar.gz" on locally.

console.log packages/ssh-pool/src/Connection.js:414
    Running "cd ./ && tar -xzf foo.tar.gz" on host "ssh.example.com".

console.log packages/ssh-pool/src/Connection.js:414
    Running "ssh -i /home/user/.ssh/id_rsa<EMAIL_ADDRESS>"cd ./ && tar -xzf foo.tar.gz"" on locally.

console.log packages/ssh-pool/src/Connection.js:414
    Running "cd ./ && rm foo.tar.gz" on host "ssh.example.com".

console.log packages/ssh-pool/src/Connection.js:414
    Running "ssh -i /home/user/.ssh/id_rsa<EMAIL_ADDRESS>"cd ./ && rm foo.tar.gz"" on locally.

console.log packages/ssh-pool/src/Connection.js:414
    Running "ls -la | grep anotherfolder1604264657030" on host "ssh.example.com".

console.log packages/ssh-pool/src/Connection.js:414
    Running "ssh -i /home/user/.ssh/id_rsa<EMAIL_ADDRESS>"ls -la | grep anotherfolder1604264657030"" on locally.

console.log packages/ssh-pool/src/Connection.js:414
    Running "cat ./anotherfolder1604264657030/test.txt" on host "ssh.example.com".

console.log packages/ssh-pool/src/Connection.js:414
    Running "ssh -i /home/user/.ssh/id_rsa<EMAIL_ADDRESS>"cat ./anotherfolder1604264657030/test.txt"" on locally.

Any idea when this will be merged in? would be great to have this is soon as its breaking the proper usage of this library at the moment


Prevent Recursive Validation

We need requestSubmit (8df3c92f319a3ecbb6cf2770f5d5ddfc01c5ea86) for Turbo support, but it triggers revalidation.

Nicely done!


Create "Tags" for Assessments

Related to #271. Let's start with tags for assessments. This would be a user-defined text field, but we would eventually want the ability to sort and filter on tags. Any added features that can contribute to more consistent tagging (e.g. so we don't end up with "rivers" and river" as two separate tags) would be appreciated, but we can start with something basic for now.
Use: Tags help Analysts build Analyses from Assessments. Help sort by similar subjects.

Use: Tags help Analysts build Analyses from Assessments. Help sort by similar subjects.

This is really helpful context, thank you!

Any added features that can contribute to more consistent tagging (e.g. so we don't end up with "rivers" and river" as two separate tags) would be appreciated, but we can start with something basic for now.

:100:


Update turn-on-or-off-preloading-content-for-meetings-using-outlook.md

Added Notes
Replaced SkypeOnlineConnector with MicrosoftTeams

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

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


Bug:  StaticPublisher::republish() doesn't strip slashes from $legalPages

If pagesAffectedByChanges() end allPagesToCache() both return urls with a trailing slash, then StaticPublisher::republish() wil strip that slash from its $urls, but not from its $legalPages. So intersecting $urls and $legalPages will allways return an empty array.
This afflicts master and v1.1.0
Solution: strip the slashes from $legalPages as well.
Temporary workaround: make sure your pagesAffectedByChanges() end allPagesToCache() return $urls without trailing slash :)

Yeah, I referenced apull request by mistake, and changed that, but it still hangs around here. Cache issue??? If it's still here when you visit - please ignore! :)

@Martimiz would you mind submitting a PR?


Create klara-oppenheimer-schule

We are a professional school in Würzburg (Germany) teaching programmers.

@steinam #745 fixed the Travis build. If you close and re-open this thread, it will trigger a new Travis build.

Thanks for merging my pull request


Fix a bug where upstream git commit was incorrectly pinned for stream…

… assembly
Commit 0917797db7fce1b6e4ea55aefdce0e55b819cc46 introduced a new
behavior to prevent from rebuilding images/rpms off their latest commits
for non-stream assemblies.
However, assembly related fields in class Runtime are initialized too late,
which results in stream assembly builds are also pinned to their latest
upstream commits.
This PR moves up the code for initializing assembly related fields and
explicitly checks assembly_basis_event to decide whether pinning a commit is needed or not.

Codecov Report

Merging #495 (cb12b0d) into master (84c70eb) will increase coverage by 32.52%.
The diff coverage is 0.00%.

:exclamation: Current head cb12b0d differs from pull request most recent head 3d35639. Consider uploading reports for the commit 3d35639 to get more accurate results

@@             Coverage Diff             @@
##           master     #495       +/-   ##
===========================================
+ Coverage        0   32.52%   +32.52%
===========================================
  Files           0       42       +42
  Lines           0    10377    +10377
  Branches        0     2166     +2166
===========================================
+ Hits            0     3375     +3375
- Misses          0     6794     +6794
- Partials        0      208      +208

Impacted Files
Coverage Δ

doozerlib/runtime.py
26.43% <0.00%> (ø)

doozerlib/image.py
33.12% <0.00%> (ø)

doozerlib/dblib.py
37.09% <0.00%> (ø)

doozerlib/__init__.py
54.54% <0.00%> (ø)

doozerlib/cli/__main__.py
0.00% <0.00%> (ø)

doozerlib/olm/bundle.py
25.22% <0.00%> (ø)

doozerlib/dotconfig.py
21.42% <0.00%> (ø)

doozerlib/cli/detect_embargo.py
73.61% <0.00%> (ø)

doozerlib/exectools.py
52.57% <0.00%> (ø)

doozerlib/config.py
0.00% <0.00%> (ø)

... and 33 more

Continue to review full report at Codecov.

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


network_plugin_mode expects "Overlay" but azurerm provider expect "overlay" resulting in constant cluster destroy

Is there an existing issue for this?

[X] I have searched the existing issues

Greenfield/Brownfield provisioning
greenfield
Terraform Version
1.5.4
Module Version
7.2.0
AzureRM Provider Version
3.64.0
Affected Resource(s)/Data Source(s)
azurerm_kubernetes_cluster
Terraform Configuration Files
network_plugin                    = "azure"
  network_plugin_mode               = "Overlay"
  ebpf_data_plane                   = "cilium"

tfvars variables values
N/A

Debug Output/Panic Output
network_profile {
          + network_mode        = (known after apply)
          ~ network_plugin_mode = "overlay" -> "Overlay" # forces replacement
          ~ network_policy      = "cilium" -> (known after apply)
          ~ pod_cidr            = "<IP_ADDRESS>/16" -> (known after apply)
          ~ pod_cidrs           = [
              - "<IP_ADDRESS>/16",
            ] -> (known after apply)

Expected Behaviour
Not have the capitalization of the network_plugin_mode force a replacement.
Actual Behaviour
Setting the network_plugin_mode to "Overlay" forces a replacement, and setting it to "overlay" results in an error.
Steps to Reproduce
No response
Important Factoids
No response
References
No response

hello @daximillian ,
this is a provider issue, and should be opened on the repo https://github.com/hashicorp/terraform-provider-azurerm
I checked, and the issue has already been fixed with provider version v3.66.0
https://github.com/hashicorp/terraform-provider-azurerm/issues/22621
I see you are using provider version 3.64.0, please upgrade

Should we upgrade the requirement to v3.66.0 if using Overlay ?
https://github.com/Azure/terraform-azurerm-aks/blob/0833586b9a22b683fcd1a774372956ae8f9da5ba/versions.tf#L9-L12

Should we upgrade the requirement to v3.66.0 if using Overlay ?
https://github.com/Azure/terraform-azurerm-aks/blob/0833586b9a22b683fcd1a774372956ae8f9da5ba/versions.tf#L9-L12

Good idea!

Hi

Should we upgrade the requirement to v3.66.0 if using Overlay ?
https://github.com/Azure/terraform-azurerm-aks/blob/0833586b9a22b683fcd1a774372956ae8f9da5ba/versions.tf#L9-L12

After reading the issue comment

The latest release v3.66.0 shipped a documentation fix to the casing of the value in https://github.com/hashicorp/terraform-provider-azurerm/pull/22554.

v3.66.0 only fixed the document, so now the user must use overlay instead of Overlay @daximillian .

I have upgraded to provider 3.79.0 and to module version 7.4.0.
The bug remains, it just isn't forcing a cluster replacement, it's just doing a cluster update every single time.
When the module receives "overlay" it outputs the following error:
╷
│ Error: Resource precondition failed
│
│   on .terraform/modules/test2_aks/main.tf line 523, in resource "azurerm_kubernetes_cluster" "main":
│  523:       condition     = var.ebpf_data_plane != "cilium" || var.network_plugin_mode == "Overlay" || var.pod_subnet_id != null
│     ├────────────────
│     │ var.ebpf_data_plane is "cilium"
│     │ var.network_plugin_mode is "overlay"
│     │ var.pod_subnet_id is null
│
│ When ebpf_data_plane is set to cilium, one of either network_plugin_mode = `Overlay` or pod_subnet_id must be specified.
╵

When the module receives "Overlay" it forces an update:
Terraform will perform the following actions:

  # module.test2_aks.azurerm_kubernetes_cluster.main will be updated in-place
  ~ resource "azurerm_kubernetes_cluster" "main" {
        id                                  = "********"
        name                                = "test2-aks"
        tags                                = {
            "env"        = "test2"
            "managed_by" = "terraform"
            "name"       = "test2-aks"
        }
        # (32 unchanged attributes hidden)

      ~ network_profile {
          ~ network_plugin_mode = "overlay" -> "Overlay"
            # (11 unchanged attributes hidden)

            # (1 unchanged block hidden)
        }

        # (11 unchanged blocks hidden)
    }

Please change the condition of the module to specify "overlay" and not "Overlay" so that we can specify the correct value and not have our cluster updated with no need.

I think this issue has been fix by #472 so I'm closing it now, please feel free to reopen it if you still meet the error after you've upgraded to v7.5.0 @daximillian .


Fix Docker repo URLs in installer CLI

The env file of the CLI module of the installer links to some internal repos and need to be changed to a public Docker registry.
Imported from Jira STREAMPIPES-29. Original Jira may contain additional context.
Reported by: riemer.

Closing the issue as it is inadvertently in open status due to migration from JIRA.


Year and Month dropdowns with dropdownMode="scroll" are not responding to mouse scrolls

After just dropping this component into my react application, the scrollable versions of the month and year dropdowns are not actually responding to mouse scrolls. Clicking the previous, upcoming arrows in the year dropdown function properly. Is there a parameter that needs to be toggled to enable the mouse wheel scrolling?

I have created a simpler codepen based off someone else's code pen to illustrate the scrolling not working using the current version (0.43.0)
https://codepen.io/dhassouni/pen/dvdZOr

Well, I feel silly now, but the scrollableYearDropdown input is what enables this. It actually was not intuitive to me from the documentation I have found and thought dropdownMode = 'scroll', would accomplish what I wanted, but I'll still chalk this up to user error.

Try     yearDropdownItemNumber={50}

scrollableYearDropdown={true} is working for me

How to unable future dates too in year dropdown?

Putting maxDate={new Date()} means the maximum possible date is today's date


The command “fw_update” was not found.

Good day,
My DMWG03LM is currently on firmware version 1.0.3_0028. I’ve tried to upgrade it to mgl03_1.5.6_0001_mod20231031 via telnet, but it says the “fw_update” command was not found. Where should I find a “fw_update” program for it?
Or should I not upgrade the firmware at all? But there is always a chance I might accidentally hit the upgrade button every time I’m in the app.

This is different gateway models.
I'm not writing custom firmwares for gateway.


Latest update appears to have broken nodePath specification

ESLint is no longer loading modules from the configured nodePath, and therefore fails to load the configured plugins.
VS Code 1.6.x (both 1.6.0 and 1.6.1 had this problem)
ESLint 1.3.1

I'm having the same problem. Breaker. It there way how to install previous version?

Great question, @dacz. I didn't find a way around this issue yet. I've been trying since it's broken ESLint for me. If I work it out, I'll be sure to post it here. In the meantime, it would be nice to get some acknowledgement that this issue is a legit problem.

@somewhatabstract @dacz
That still works for me in a test setup that looks like this:

eslint npm module installed under C:\tmp\es-298\node_modules\eslint
VS Code workspace under P:\mseng\vscode\playgrounds\bugs\es-298
workspace settings file like this:

{
	"eslint.nodePath": "C:\\tmp\\es-298\\node_modules",
	"eslint.trace.server": "messages"
}

open VS Code on P:\mseng\vscode\playgrounds\bugs\es-298
.eslintrc.json file

{
    "env": {
        "browser": true,
        "commonjs": true,
        "es6": true,
        "node": true
    },
    "parserOptions": {
        "ecmaFeatures": {
            "jsx": true
        },
        "sourceType": "module"
    },
    "rules": {
        "no-const-assign": "warn",
        "no-this-before-super": "warn",
        "no-undef": "warn",
        "no-unreachable": "warn",
        "no-unused-vars": "warn",
        "constructor-super": "warn",
        "valid-typeof": "warn"
    }
}

test.js

function foo() {
	var x;
}

results in:

Do you have any steps to reproduce what you are seeing.

I installed eslint 4.7.1 and tested above under Windows.

And can you enable tracing to verbose ("eslint.trace.server": "verbose") and attach what is printed to the output channel. May be this already gives me a hint what is failing.

I downgraded plugin to 1.2.11 and downgraded eslint (locally installed) to 4.6.1. It worked. Because I need to work I have no courage to try upgrading the plugin.
I suspect that the problem is not the plugin but the eslint 4.7.0.

For me, we have several ESLint plugins in a sub-folder, so we point node_modules to that. But it is picking up eslint and node_modules from the very first node_modules folder it finds, rather than the path provided.

@somewhatabstract is there anything in the trace when "eslint.trace.server": "verbose" is set that looks suspicious?

@dbaeumer A few things look strange, but this specifically:
[Trace - 19:46:02] NODE_PATH value is: ./<PATH_I_SPECIFIED_FOR_NODEPATH>/node_modules
[Trace - 19:46:02] NODE_PATH value is: /usr/local/lib/node_modules
[Trace - 19:46:02] NODE_PATH value is: ./<PATH_I_SPECIFIED_FOR_NODEPATH>/node_modules
[Trace - 19:46:02] NODE_PATH value is: /usr/local/lib/node_modules

And:

[Info  - 19:46:03] ESLint library loaded from: /Users/jeffyates/<GIT_REPO>/<BUILD_LOCATION_NOT_REFERENCED_IN_ESLINTRC>/node_modules/eslint/lib/api.js

Interestingly, BUILD_LOCATION_NOT_REFERENCED_IN_ESLINTRC is the first folder that contains a node_modules folder. Though, I suspect that's a red herring.

@somewhatabstract  I think I know what it is. Can you do the following to verify it:

make the nodePath variable in the settings file absolute. This should fix the problem.

The underlying cause of the problem is the support for multiple workspace folders which got added to ESLint 1.3.1. To implement this the ESLint language server is not running on working directory of the workspace anymore (since for n folders there is no common working directory). I need to handle the case that the nodePath setting is relative and make it absolute relative to the file being linted.
@egamma you would need to do the same for tslint.

@dbaeumer thanks, issue on this came in today https://github.com/Microsoft/vscode-tslint/issues/264 ;-)

Published 1.3.2 which has support for relative nodePath.

Hmm, I tried an absolute path and it didn't seem to work. Let me try again.

Ha, I see that 1.3.2 fixes it anyway. Great! Thank you!


Error on notify: context deadline exceeded

If I group my alerts in such a way that 4 alerts fall in a group I get following error:
ERRO[0300] Error on notify: context deadline exceeded    source=notify.go:152
ERRO[0300] Notify for 1 alerts failed: context deadline exceeded  source=dispatch.go:238
& if I modify grouping so that 1 group has one alert each, then thing move smoothly.
Please help to correct where I am wrong.
alertmanager.conf:
 group_by: ['severity', 'alertname', 'instance']
  group_wait: 1m
  group_interval: 5m
  repeat_interval: 30m
  receiver: alerta
  routes:
  - match_re:
      service: container
    receiver: mail
  - match:
      service: jira_chk
    receiver: JIRA

That seems highly unlikely to be related to the grouping. context deadline exceeded simply means the request timed out.
The error message shows that only one of the four alerts failed. So against your expectation the 4 alerts are not in the same group.
The most likely thing here is that notification requests to one of your receivers are timing out. Your configuration changes then cause no requests being sent to that receiver in the first place.
For further debugging we need the full configuration (before AND after) and the label sets of the four alerts.

Difference in old & new configuration is "group_by" & "repeat_interval" value
Old alertmanager.conf:
global:
  # The smarthost and SMTP sender used for mail notifications.
  smtp_smarthost: 'mailhostX:25'
  smtp_from: 'XYZ@ABC'

route:
  group_by: ['severity', 'alertname']
  group_wait: 1m
  group_interval: 5m
  repeat_interval: 333h
  receiver: alerta
  routes:
  - match_re:
      service: container
    receiver: mail
  - match:
      service: jira_chk
    receiver: JIRA

inhibit_rules:
- source_match:
    severity: 'low'
  target_match:
    severity: 'warning'
  # Apply inhibition if the alertname is the same.
  equal: ['alertname', 'cluster', 'service']

receivers:
- name: 'alerta'
  webhook_configs:
  - url: 'http://<IP>:8995/api/webhooks/prometheus'
    send_resolved: true

- name: 'mail'
  email_configs:
  - to: 'kk@ABC'
    send_resolved: true

- name: 'JIRA'
  webhook_configs:
  - url: 'http://<IP>:8955/issues/projects/LP'
    send_resolved: true

New alertmanager.conf:
global:
  # The smarthost and SMTP sender used for mail notifications.
  smtp_smarthost: 'mailhostX:25'
  smtp_from: 'XYZ@ABC'

route:
  group_by: ['severity', 'alertname', 'instance']
  group_wait: 1m
  group_interval: 5m
  repeat_interval: 30m
  receiver: alerta
  routes:
  - match_re:
      service: container
    receiver: mail
  - match:
      service: jira_chk
    receiver: JIRA

inhibit_rules:
- source_match:
    severity: 'low'
  target_match:
    severity: 'warning'
  # Apply inhibition if the alertname is the same.
  equal: ['alertname', 'cluster', 'service']

receivers:
- name: 'alerta'
  webhook_configs:
  - url: 'http://<IP>:8995/api/webhooks/prometheus'
    send_resolved: true

- name: 'mail'
  email_configs:
  - to: 'kk@ABC'
    send_resolved: true

- name: 'JIRA'
  webhook_configs:
  - url: 'http://<IP>:8955/issues/projects/LP'
    send_resolved: true

Complete Error:
ERRO[239100] Error on notify: context deadline exceeded    source=notify.go:152
ERRO[239100] Notify for 4 alerts failed: context deadline exceeded  source=dispatch.go:238
WARN[239100] Notify attempt 1 failed: Post http://:8955/issues/projects/LP: dial tcp :8955: getsockopt: connection refused  source=notify.go:193
ERRO[239101] Error on notify: context deadline exceeded    source=notify.go:152
ERRO[239101] Notify for 1 alerts failed: context deadline exceeded  source=dispatch.go:238
With old configuration: I have 5 alerts for jira_chk receiver; 4 in a group & 1 in other if

I am also facing the same issue. Does alertmanager retries fail notifications?

Here are my logs (using latest stable version - v0.3.0):
{"level":"warning","msg":"Notify attempt 2 failed: context deadline exceeded","source":"notify.go:193","time":"2016-08-04T03:02:01Z"}
{"level":"warning","msg":"Notify attempt 3 failed: context deadline exceeded","source":"notify.go:193","time":"2016-08-04T03:02:01Z"}
{"level":"error","msg":"Error on notify: context deadline exceeded","source":"notify.go:152","time":"2016-08-04T03:02:01Z"}
{"level":"error","msg":"Notify for 1 alerts failed: context deadline exceeded","source":"dispatch.go:238","time":"2016-08-04T03:02:01Z"}
{"level":"warning","msg":"Notify attempt 1 failed: Post https://events.pagerduty.com/generic/2010-04-15/create_event.json: dial tcp: lookup events.pagerduty.com on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:44485-\u003e<IP_ADDRESS>:53: i/o timeout","source":"notify.go:193","time":"2016-08-04T03:02:02Z"}
{"level":"warning","msg":"Notify attempt 2 failed: context deadline exceeded","source":"notify.go:193","time":"2016-08-04T03:02:11Z"}
{"level":"warning","msg":"Notify attempt 3 failed: context deadline exceeded","source":"notify.go:193","time":"2016-08-04T03:02:11Z"}
{"level":"error","msg":"Error on notify: context deadline exceeded","source":"notify.go:152","time":"2016-08-04T03:02:11Z"}
{"level":"error","msg":"Notify for 1 alerts failed: context deadline exceeded","source":"dispatch.go:238","time":"2016-08-04T03:02:11Z"}
{"level":"warning","msg":"Notify attempt 1 failed: Post https://events.pagerduty.com/generic/2010-04-15/create_event.json: dial tcp: lookup events.pagerduty.com on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:53401-\u003e<IP_ADDRESS>:53: i/o timeout","source":"notify.go:193","time":"2016-08-04T03:02:12Z"}
{"level":"warning","msg":"Notify attempt 2 failed: context deadline exceeded","source":"notify.go:193","time":"2016-08-04T03:02:21Z"}
{"level":"warning","msg":"Notify attempt 3 failed: context deadline exceeded","source":"notify.go:193","time":"2016-08-04T03:02:21Z"}
{"level":"error","msg":"Error on notify: context deadline exceeded","source":"notify.go:152","time":"2016-08-04T03:02:21Z"}
{"level":"error","msg":"Notify for 1 alerts failed: context deadline exceeded","source":"dispatch.go:238","time":"2016-08-04T03:02:21Z"}
{"level":"warning","msg":"Notify attempt 1 failed: Post https://events.pagerduty.com/generic/2010-04-15/create_event.json: dial tcp: lookup events.pagerduty.com on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:47474-\u003e<IP_ADDRESS>:53: i/o timeout","source":"notify.go:193","time":"2016-08-04T03:02:22Z"}

@rohit01 yes, Alertmanager retries failed notifications. However, only up until the timeout. Timeout of sends themselves is not a retry condition as it would defeat its purpose.

@rohit01 could you share your configuration as well? Did it also happened after you changed something or was it there from the beginning?

It started happening automatically one day without any config change. All of a sudden, we stopped getting any alerts. Did random things like restart container, minor config changes and it started working again with intermittent failures.
We were on version 01.0, we tried 0.1.1 and finally moved to v0.3.0 (yesterday).
Here's the configuration:
global:
  # The smarthost and SMTP sender used for mail notifications.
  smtp_smarthost: '****'
  smtp_from: '****'

# The root route on which each incoming alert enters.
route:
  # The labels by which incoming alerts are grouped together. For example,
  # multiple alerts coming in for cluster=A and alertname=LatencyHigh would
  # be batched into a single group.
  group_by: ['severity', 'alertname', 'instance', 'job']

  # When a new group of alerts is created by an incoming alert, wait at
  # least 'group_wait' to send the initial notification.
  # This way ensures that you get multiple alerts for the same group that start
  # firing shortly after another are batched together on the first
  # notification.
  group_wait: 3s

  # When the first notification was sent, wait 'group_interval' to send a batch
  # of new alerts that started firing for that group.
  group_interval: 3s

  # If an alert has successfully been sent, wait 'repeat_interval' to
  # resend them.
  repeat_interval: 3h

  # A default receiver
  receiver: 'notifications'

  # All the above attributes are inherited by all child routes and can
  # overwritten on each.

  # The child route trees.
  routes:
  # This routes performs a regular expression match on alert labels to
  # catch alerts that are related to a list of services.
    - match_re:
        severity: ^(critical|warning)$
      receiver: 'notifications'
      # Child Routes (having greater precedence)
      routes:
      - match:
          severity: critical
        receiver: 'notifications-and-pagerduty'

# Inhibition rules allow to mute a set of alerts given that another alert is
# firing.
# We use this to mute any warning-level notifications if the same alert is
# already critical.
inhibit_rules:
  - source_match:
      severity: 'critical'
    target_match:
      severity: 'warning'
    # Apply inhibition if the following matches.
    equal: ['CITY', 'SERVICE', 'instance']

  - source_match:
      severity: 'critical'
    target_match:
      severity: 'warning'
    # Apply inhibition if the following matches.
    equal: ['alertname', 'instance', 'job']

receivers:
  - name: 'notifications'
    # Send email
    email_configs:
      - to: '<email 1>'
        require_tls: false
      - to: '<email 2>'
        require_tls: false

  - name: 'notifications-and-pagerduty'
    # Trigger pagerduty
    pagerduty_configs:
      - service_key: <hidden>
    # Send email
    email_configs:
      - to: '<email 1>'
        require_tls: false
      - to: '<email 2>'
        require_tls: false

This is worrying as it's two cases. But OTOH in both cases the error messages indicate a timeout when sending the notification (not anywhere in our code before or after). So I'm wondering if it's just an unlucky coincidence.
Have you verified whether you can curl the respective notification endpoint (PagerDuty in your case @rohit01) within the timeout?

@fabxc What is the timeout value?
Unable to find in code.

@rohit01 I was not quite precise earlier.
The general timeout is the grouping interval, which you can think of the "update frequency" for a group of alerts. You have set yours very low, it should generally be at the order of 1 minute or more as it is meant to avoid getting spammed. PagerDuty for that matter will not even page you again and has issues updating the data (last time I checked). So there's no value in having it that low here.
It also means your effective request timeout to PagerDuty is only 3 seconds.
The timeout is assigned here: https://github.com/prometheus/alertmanager/blob/7b20b776eaca8ceeac09eff0187222fe317b2ec2/dispatch.go#L314-L316
Now for your error logs on the failed retry attempts. This seems to be an issue here:
https://github.com/prometheus/alertmanager/blob/master/notify/notify.go#L191-L199
We retry notification with backoff based on a ticker. We attempt to receive a signal from that ticker, but want to abort that if the context timed out. In the code we just do a plain select over both signals, the choice is random.
If we retry with a timed out context, the notification immediately fails. The code should check the context first before then waiting on whatever signal appears first.
Does that make sense? So your problem would most likely disappear if you set group_interval to a value of 3-5 minutes.
Sorry about addressing your issue super late, @kavyakul. Your error logs also simply indicates a failure to reach the notification endpoint:  dial tcp :8955: getsockopt: connection refused. Have you checked whether you can manually curl it from the Alertmanager host?

@fabxc Thanks for the explanation. We were running with group_interval as 1s as well. Now, I think we know the reason for our pain :)

Yes, I suppose we could think about making changes to have a timeout larger than group_interval to allow for "immediate updates". But I believe this at best enables self harm for users and cannot see any practical value.
@brian-brazil what's your opinion?

I'd not consider any group interval under a minute to be sane. I think our current behaviour is fine.
If you want some form of automated action faster than that, then you want a dedicated realtime control system because humans can't respond that fast.

Hi
I have similar issue.
Getting context deadline exceeded and also I can able to curl the endpoint from alert manager host
here is my alert rules config:
alert.rules
groups:

name: sample
rules:

alert: prometheus_remote_storage_succeeded_samples_total_alert
expr: sum(prometheus_remote_storage_succeeded_samples_total{instance="prometheus:9090"}) == 0
for: 30s
labels:
severity: warning
annotations:
summary: Instance {{ $labels.instance }} cannot store sample to remote storage

name: sample1
rules:

alert: sample_alert
expr: testmetric == 0
labels:
severity: warning
instance: i1
annotations:
summary: this is sample summary for {{ $labels.instance }}

alertmanager.yaml
global:
resolve_timeout: 5m
route:
group_by: ['instance']
group_wait: 1m
group_interval: 1m
repeat_interval: 1h
receiver: 'web.hook'
receivers:

name: 'web.hook'
webhook_configs:

url : http://json-server.2304650011.svc:3030/EspServiceRequest/

Alert:
See Attachment
Can connect to endpoint:
sh-4.2# curl -v http://json-server.2304650011.svc:3030/EspServiceRequest/

About to connect() to json-server.2304650011.svc port 3030 (#0)
Trying <IP_ADDRESS>...
Connected to json-server.2304650011.svc (<IP_ADDRESS>) port 3030 (#0)

GET /EspServiceRequest/ HTTP/1.1
User-Agent: curl/7.29.0
Host: json-server.2304650011.svc:3030
Accept: /

Error:
level=error ts=2018-09-19T23:31:48.278890325Z caller=notify.go:332 component=dispatcher msg="Error on notify" err="context deadline exceeded"
level=error ts=2018-09-19T23:31:48.278990617Z caller=dispatch.go:280 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="context deadline exceeded"
level=error ts=2018-09-19T23:31:58.279279537Z caller=notify.go:332 component=dispatcher msg="Error on notify" err="context deadline exceeded"
level=error ts=2018-09-19T23:31:58.279346534Z caller=dispatch.go:280 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="context deadline exceeded"
Could you please let me know for any solution for this.
Regards,
Keshav Sharma

also having the same solution here
My alertmanager and prometheus are both in a kubernetes cluster. And using helm with the stable/prometheus chart.
here is my configuration for alertmanager.
`alertmanagerFiles:
alertmanager.yml:
global:
resolve_timeout: 1h
slack_api_url: 'https://hooks.slack.com/services/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'
route:
  group_by: ['instance','alertname']
  group_wait: 1s
  group_interval: 3m
  receiver: ea_sspc
  repeat_interval: 30m

receivers:
  - name: 'ea_sspc'
    slack_configs:
      - channel: 'viper-lab-sspc'
        send_resolved: false
        text: 'Test device Selenium/Appium is down, please SSH and restart'`

and here are the logs
level=info ts=2018-10-25T23:10:17.313219036Z caller=cluster.go:587 component=cluster msg="gossip settled; proceeding" elapsed=10.000852659s level=error ts=2018-10-25T23:17:19.970316317Z caller=notify.go:332 component=dispatcher msg="Error on notify" err="context deadline exceeded" level=error ts=2018-10-25T23:17:19.970394998Z caller=dispatch.go:280 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="context deadline exceeded" level=error ts=2018-10-25T23:17:19.987694626Z caller=notify.go:332 component=dispatcher msg="Error on notify" err="context deadline exceeded" level=error ts=2018-10-25T23:17:19.987740048Z caller=dispatch.go:280 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="context deadline exceeded"

also having the same solution here
My alertmanager and prometheus are both in a kubernetes cluster. And using helm with the stable/prometheus chart.
here is my configuration for alertmanager.
alertmanagerFiles:
  alertmanager.yml:
    global:
      resolve_timeout: 1h
      slack_api_url: <secret>

    route:
      group_by: ['instance','alertname']
      group_wait: 1s
      group_interval: 3m
      receiver: ea_sspc
      repeat_interval: 30m

    receivers:
      - name: 'ea_sspc'
        slack_configs:
          - channel: 'viper-lab-sspc'
            send_resolved: false
            text: 'Test device Selenium/Appium is down, please SSH and restart'

and here are the logs
level=info ts=2018-10-25T23:10:17.313219036Z caller=cluster.go:587 component=cluster msg="gossip settled; proceeding" elapsed=10.000852659s level=error ts=2018-10-25T23:17:19.970316317Z caller=notify.go:332 component=dispatcher msg="Error on notify" err="context deadline exceeded" level=error ts=2018-10-25T23:17:19.970394998Z caller=dispatch.go:280 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="context deadline exceeded" level=error ts=2018-10-25T23:17:19.987694626Z caller=notify.go:332 component=dispatcher msg="Error on notify" err="context deadline exceeded" level=error ts=2018-10-25T23:17:19.987740048Z caller=dispatch.go:280 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="context deadline exceeded"

also having the same solution here
My alertmanager and prometheus are both in a kubernetes cluster. And using helm with the stable/prometheus chart.
here is my configuration for alertmanager.
alertmanagerFiles:
  alertmanager.yml:
    global:
      resolve_timeout: 1h
      slack_api_url: <secret>

    route:
      group_by: ['instance','alertname']
      group_wait: 1s
      group_interval: 3m
      receiver: ea_sspc
      repeat_interval: 30m

    receivers:
      - name: 'ea_sspc'
        slack_configs:
          - channel: '@me'
            send_resolved: false
            text: 'Test device Selenium/Appium is down, please SSH and restart'

and here are the logs
level=info ts=2018-10-25T23:10:17.313219036Z caller=cluster.go:587 component=cluster msg="gossip settled; proceeding" elapsed=10.000852659s level=error ts=2018-10-25T23:17:19.970316317Z caller=notify.go:332 component=dispatcher msg="Error on notify" err="context deadline exceeded" level=error ts=2018-10-25T23:17:19.970394998Z caller=dispatch.go:280 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="context deadline exceeded" level=error ts=2018-10-25T23:17:19.987694626Z caller=notify.go:332 component=dispatcher msg="Error on notify" err="context deadline exceeded" level=error ts=2018-10-25T23:17:19.987740048Z caller=dispatch.go:280 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="context deadline exceeded"

also having the same solution here
My alertmanager and prometheus are both in a kubernetes cluster. And using helm with the stable/prometheus chart.
here is my configuration for alertmanager.
alertmanagerFiles:
  alertmanager.yml:
    global:
      resolve_timeout: 1h
      slack_api_url: <secret>

    route:
      group_by: ['instance','alertname']
      group_wait: 1s
      group_interval: 3m
      receiver: default
      repeat_interval: 30m

    receivers:
      - name: 'default'
        slack_configs:
          - channel: '@me'
            send_resolved: false
            text: 'Test device Selenium/Appium is down, please SSH and restart'

and here are the logs
level=info ts=2018-10-25T23:10:17.313219036Z caller=cluster.go:587 component=cluster msg="gossip settled; proceeding" elapsed=10.000852659s level=error ts=2018-10-25T23:17:19.970316317Z caller=notify.go:332 component=dispatcher msg="Error on notify" err="context deadline exceeded" level=error ts=2018-10-25T23:17:19.970394998Z caller=dispatch.go:280 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="context deadline exceeded" level=error ts=2018-10-25T23:17:19.987694626Z caller=notify.go:332 component=dispatcher msg="Error on notify" err="context deadline exceeded" level=error ts=2018-10-25T23:17:19.987740048Z caller=dispatch.go:280 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="context deadline exceeded"

also having the same solution here
My alertmanager and prometheus are both in a kubernetes cluster. And using helm with the stable/prometheus chart.
here is my configuration for alertmanager.
alertmanagerFiles:
  alertmanager.yml:
    global:
      resolve_timeout: 1h
      slack_api_url: <secret>

    route:
      group_by: ['instance','alertname']
      group_wait: 1s
      group_interval: 3m
      receiver: default
      repeat_interval: 30m

    receivers:
      - name: 'default'
        slack_configs:
          - channel: '@me'
            send_resolved: false
            text: 'text'

and here are the logs
level=info ts=2018-10-25T23:10:17.313219036Z caller=cluster.go:587 component=cluster msg="gossip settled; proceeding" elapsed=10.000852659s level=error ts=2018-10-25T23:17:19.970316317Z caller=notify.go:332 component=dispatcher msg="Error on notify" err="context deadline exceeded" level=error ts=2018-10-25T23:17:19.970394998Z caller=dispatch.go:280 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="context deadline exceeded" level=error ts=2018-10-25T23:17:19.987694626Z caller=notify.go:332 component=dispatcher msg="Error on notify" err="context deadline exceeded" level=error ts=2018-10-25T23:17:19.987740048Z caller=dispatch.go:280 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="context deadline exceeded"


Update init_parallel_stencil.jl

Updated text formatting.
Before the parallel in @init_parallel_stencil showed up in italics.

There was intentionally not everything put between `` symbols and therefore highlighted in color in the REPL - in order to make the most important things for each function come out more. I therefore reverted the commit. At some point, we should revise the usage of `` in order to improve the formatting, but this should be done in the consistently in the whole source code at once.


Update telling-git-about-your-signing-key.md

Corrected instructions for setting the GPG_TTY environment variables on GNU/Linux
Why:
The current instructions for setting GPG_TTY is unsuited for GNU/Linux. Unlike on macOS where interactive shells are also login shells, shells lauched by terminal emulators on GNU/Linux are non-login shells by default. As a result, neither .bash_profile nor .profile will be executed when they are started normally. See Bash Reference Manual for a fuller explanation.
What's being changed:
The relevant instructions have been updated to align with the standard practice of putting initialization commands in .bashrc on GNU/Linux. Please note that the GnuPG Manual also recommends that:

You should always add the following lines to your .bashrc or whatever initialization file is used for all shell invocations:
GPG_TTY=$(tty)
export GPG_TTY

Check off the following:

[x] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

@xty
Thanks so much for opening a PR! I'll get this triaged for review :zap:


Prepare for beta2 release

Description
Cherry picked the last 2 commits on main, added changelog entries and bumped the SDK dependency
NOTE: this is going into the release branch from which a beta2 release will be immediately cut after merging
closes: #XXXX

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

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

will open prs into main for the dependency change and missing changelog entries, then I'll cherry pick everything


🐛 FIX: Update priority for LaTeX output for html and latex builders

This PR increases the priority for text/latex representations for html and latex builders.
For html -- mathjax renders the text/latex representation more cleanly than typical images provided by some underlying packages (i.e. png images)
For latex -- native latex syntax should be used in preference.

[ ] check if this PR fixes https://github.com/QuantEcon/lecture-python.myst/issues/95

I don't think latex should be above svg

I don't think latex should be above svg

hey @chrisjsewell can you explain why? mathjax seems to do a nicer job of displaying the math.

Because svg is natively supported by HTML, latex is not

Because svg is natively supported by HTML, latex is not

roger that.

@chrisjsewell I see epub is listed as a builder in the builder option list.
Do you know if epub has a mechanism to support text/latex like mathjax?


Add unit test for search history end points

See #59 for context. Implement unit test for the routing end points needed. You will need to incorporate authentication into test case since this will be secured data (see #38 and #76 for related information). You can reference savedPins file in tests for an example and routes/users.js and routes/saved-pins regarding routes and their controller functions.

hey @jkwening.  I am thinking of tackling this issue.  However when I run npm test I get an error
Cannot find module '../src/components/SigninForm'
It is coming from components.test.js in the client folder.  I don't see any folder by that name in the components directory.  Maybe your team is already aware of this?  I am just gonna comment out that test for now and work on this issue.

@Euklidian-Space yeah that's fine; the front end code base has change a lot since this issue was created. The related component is now in ../src/components/AccountForm - can you add a comment noting that while you're at it. Thanks for contributing!
@motosharpley can you add him to the group? Thanks.

hey @jkwening, I have some questions.

For postSavedPins in saved-pins-controller.js there is a part in the function definition where it is checking if a pin exists in the database.  It does that by looking at appReq.body.lat and appReq.body.lng .  I cannot seem to find where in the middleware pipeline those properties get set.  I know for this particular route verifyToken is called before postSavedPins but verify token does not mutate the body property on the appReq object.

I only ask this because the first test for POST /search/savedpins route in saved-pins-test.js is failing when i run npm test.  These were test that were written before me taking on this task.

Hi @Euklidian-Space appReq.body.lat/lng are from the request body data that are sent along with the api request from the frontend. For a given pin/marker, it has a lat/lng data that specifies it geolocation. The frontend passes along that information in its request to the backend server to save to the database. So in writing the test, you're going to have to mimic a request response by passing the necessary correct key, value pairs in the body of the request.
Did that help?

@jkwening I understand that.  What I am saying though is I do not see where that is happening in the unit test in saved-pins-test.js .  There is no explicit assignment in the test as far as I can tell. Is that hidden in the test setup for the project somewhere?  Take a look at saved-pins-test.js and tell me if you can see where the request is mutated.  Note that the first test fails on the first .expect(200) because somewhere along the line the one of the Pin generated by seed.js is getting assigned to appReq.body and I have no idea where that is happening.  It is obfuscated from the flow of the code as far as I can tell

@jkwening I figured it out.  I didn't notice the call to .send() in the promise chain in the test.  Whoever wrote this test must have unintentionally placed it in the test because that call to send is antithetical to the description of the test and causing it to fail.  I am going to remove it and have it among my commits for this task

Hey @jkwening, How are do you feel about SinonJS as a dev dependency in order to Mock responses from the google API?

@jkwening PR submitted.

@jkwening PR was merged.  This issue can be closed out.


get Info and PhoneInfo data

Hi,
How to get  Info and PhoneInfo data ?
I saw that these informations are in function newInfoFromReq (inside session.go), but there are some example how to get these data?
Thanks.

Hi,
How to get Info and PhoneInfo data ?
I saw that these informations are in function newInfoFromReq (inside session.go), but there are some example how to get these data?
Thanks.

Solved using HandleJsonMessage.


Accept environment variable as Webhook URL

Hello,
Currently if I enter the webhook as a parameter or as an environment variable (secret text), the notification doesn't get sent out as it doesn't accept the URL.
ERROR: Build step failed with exception
java.net.MalformedURLException: no protocol: ${PST_DISCORD_JENKINS_CHANNEL}
	at java.net.URL.<init>(URL.java:593)
	at java.net.URL.<init>(URL.java:490)
	at java.net.URL.<init>(URL.java:439)
	at com.mashape.unirest.http.HttpClientHelper.prepareRequest(HttpClientHelper.java:171)
Caused: java.lang.RuntimeException
	at com.mashape.unirest.http.HttpClientHelper.prepareRequest(HttpClientHelper.java:183)
	at com.mashape.unirest.http.HttpClientHelper.request(HttpClientHelper.java:131)
	at com.mashape.unirest.request.BaseRequest.asJson(BaseRequest.java:68)
	at nz.co.jammehcow.jenkinsdiscord.DiscordWebhook.send(DiscordWebhook.java:112)
	at nz.co.jammehcow.jenkinsdiscord.WebhookPublisher.perform(WebhookPublisher.java:104)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690)
	at hudson.model.Build$BuildExecution.cleanUp(Build.java:196)
	at hudson.model.Run.execute(Run.java:1771)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:97)
	at hudson.model.Executor.run(Executor.java:421)
Build step 'Discord Notifier' marked build as failure

It would be cool if that can get enabled as it will make it so much easier to integrate it to many jobs (and if the webhook URL changes, I'll only have to change it once from the credentials page).

I'll note it down and this should be added within the next few days.

Hello,
would it be possible to consider using the Credentials plugin directly as consumer?
It would secure the storage of the webhook URL and be an elegant solution to the request.

I forgot to finish this off, but I'll go with @marcolinux's suggestion here. Bypasses unneeded steps.

great thanks. If you prepare a pre-release hpi I can test it with pleasure.

Well, for the sake of discussion, discord URL isn't necessarily a "secret". Which is why I suggested the ability to add it as an environment variable approach. This way, the developers have more freedom to where they want to send the payload to.

So lets say they want to send the payload to different discord channels on different Jenkins builds, they could put the webhook urls as a "choice parameter" and the plugin will pick up on that.

I would like to apologize for my absence and lack of care taken on this project. If one of you wants to submit a PR for this that would be great, otherwise I'm setting it up for release 1.3 when I get around to it. I'll definitely have a look at how I'd approach this within the next few days and re-evaluate the options.
Any changes and I'll let you all know.

I'm going to close this, see #25 for more details.


PyStruct is BSD-licensed but is inoperable without GPL-licensed CVXOPT

I was hoping to use PyStruct for a BSD-licensed project, but when I try to run
from pystruct.learners import SubgradientSSVM

which apparently does not rely on cvxopt, I get
ImportError: No module named 'cvxopt'

This is a show stopper for me. Is there any possibility that this dependency might be made optional at some point in the near future?
Thank you!

Also, AD3 is a required dependency. Is there any chance of that changing any time soon?
Thanks again.

Neigher of them are required dependencies.
You can do
from pystruct.learners.subgradient import SubgradientSSVM
and you won't wee the cvxopt error.
AD3 should not be required anywhere.

Thanks very much @amueller.
When I run
from pystruct.learners.subgradient import SubgradientSSVM

I get
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
<ipython-input-2-2805ab9ce42b> in <module>()
----> 1 from pystruct.learners.subgradient import SubgradientSSVM

/Users/ben/miniconda2/envs/qiime2/lib/python3.5/site-packages/pystruct/learners/__init__.py in <module>()
----> 1 from .n_slack_ssvm import NSlackSSVM
      2 from .subgradient_ssvm import SubgradientSSVM
      3 from .downhill_simplex_ssvm import PrimalDSStructuredSVM
      4 from .structured_perceptron import StructuredPerceptron
      5 from .one_slack_ssvm import OneSlackSSVM

/Users/ben/miniconda2/envs/qiime2/lib/python3.5/site-packages/pystruct/learners/n_slack_ssvm.py in <module>()
     10
     11 import numpy as np
---> 12 import cvxopt
     13 import cvxopt.solvers
     14

ImportError: No module named 'cvxopt'

Also, ad3 is an install_requires in setup.py, so whether you need it or not it it gets installed.

Yeah I wanted to remove that from the setup.py. You can do that locally or tell pip not to install the dependencies, right?
It's weird that the __init__.py get's called if you do the direct import. It's pretty easy to make the import lazy in the NSlackSSVM and OneSlackSSVM, though.

I don't have a lot of time to work on pystruct right now put PR welcome.

Thanks again. If structured learning turns out to give significant improvements over what's available in scikit-learn for my problem you will be hearing from me.

cool. Can I ask what you're working on?

Sure! It's here. It's a core plugin for QIIME 2. QIIME 2 is the successor to QIIME, a microbiome analysis framework.


Mb pgp separate files and gvcf

Updates to PGP Harvard data import.

Create separate files, not using a compressed tar archive.
Import survey data as JSON if available.
Import Complete Genomics var file, if available.
If there's a var file, create gVCF from var file.
Import Complete Genomics masterVarBeta file, if available.

Task update sends both old version of update data ('s3_keys') and planned new field containing s3 key, description, and tags information ('data_files'), as planned for https://github.com/PersonalGenomesOrg/open-humans/issues/320

@madprime looks good to me! :+1:


conditional @font-face hack for slick-theme.less

font files should only be loaded if they are needed, like sass file already does.

Good call. Merging.


feat: allow saving deployments to config file

What I did
Allows you to save your deployments to your config file.
How I did it
Add another base key deployments to config manager user config logic
How to verify it
Have this in your config:
deployments:
  rinkeby:
  - "0x1122C33728208F55e11AC24536b6AB207A4a9E03"

Have some python using it like this:
from ape import config

contract_address = config.deployments.get("rinkeby")[0]

Checklist

[ ] Passes all linting checks (pre-commit and CI jobs)
[ ] New test cases have been added and are passing
[ ] Documentation has been updated
[ ] PR title follows Conventional Commit standard (will be automatically included in the changelog)

Still think deployments need to be expanded a bit:
deployments:
  ethereum:  # ecosystem
    rinkeby:  # network
      MyContract:  # ContractType[deployments]
      - 0x1122C33728208F55e11AC24536b6AB207A4a9E03  # No string necessary?

Still think deployments need to be expanded a bit:
deployments:
  ethereum:  # ecosystem
    rinkeby:  # network
      MyContract:  # ContractType[deployments]
      - 0x1122C33728208F55e11AC24536b6AB207A4a9E03  # No string necessary?

Good point! Especially about including the ecosystem and using real contract types. Let me add in these revisions; I want the schema to be solid enough to not have to change too much to lessen breaking changes

Oh I just now saw your comment on #374  regarding the syntax for .at(-1).


wild type sequence for stability dataset

Hi,
I am interested in using you tape data for my deep learning, but we would like to generate pdb file from the wild type sequence first. we sort of figured out the wild type sequence for fluroscent data is the one with num_mutation=0, but couldn't figure out the wild type sequence for stability score, as we looked into it, there were a few of them with stability_score =1.
would you mind share with me the wild type sequence for the stabililty_score?
Thank you.

I've been looking into the original data files from the Rocklin 2017 stability paper, and the wild type sequences in the saturation mutagenesis (ssm2) experiment are clearly indicated there. Their entries in the name column of the Rocklin file are
EEHEE_rd3_0037.pdb
EEHEE_rd3_1498.pdb
EEHEE_rd3_1702.pdb
EEHEE_rd3_1716.pdb
EHEE_0882.pdb
EHEE_rd2_0005.pdb
EHEE_rd3_0015.pdb
HEEH_rd2_0779.pdb
HEEH_rd3_0223.pdb
HEEH_rd3_0726.pdb
HEEH_rd3_0872.pdb
HHH_0142.pdb
HHH_rd2_0134.pdb
HHH_rd3_0138.pdb
Pin1
hYAP65
villin

If you want to find them in stability_test.json in the TAPE data, match those to the id entries or look for id entries that don't have an additional underscore specifying the mutation. For instance, EEHEE_rd3_0037.pdb is a wild type instance but EEHEE_rd3_0037.pdb_A19D is a mutation.


Include warning to say excluding parts of the profile should be done with care

People have been using redirections.xml circulated from the internet blindly  this has been causing issues. Add warning something like the following
'Exclusions from the profile may have serious impact on functionality.  Exclusions should be by exception and tested to ensure no loss of functionality is incurred'

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

ID: 960d3cdb-4c5a-7c10-a78e-127b1216a547
Version Independent ID: a1bf2ff6-41a6-e840-676e-0eb4b9feed72
Content: Profile Container content - FSLogix
Content Source: fslogix-docs/manage-profile-content-cncpt.md
Product: fslogix
GitHub Login: @DougCoombs
Microsoft Alias: docoombs

Thanks Jim, I will add this!
Doug
From: Jim Moyle<EMAIL_ADDRESS>Sent: Thursday, April 9, 2020 3:19 AM
To: MicrosoftDocs/fslogix-docs<EMAIL_ADDRESS>Cc: Doug Coombs<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: [MicrosoftDocs/fslogix-docs] Include warning to say excluding parts of the profile should be done with care (#38)
People have been using redirections.xml circulated from the internet blindly this has been causing issues. Add warning something like the following
'Exclusions from the profile may have serious impact on functionality. Exclusions should be by exception and tested to ensure no loss of functionality is incurred'

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

ID: 960d3cdb-4c5a-7c10-a78e-127b1216a547
Version Independent ID: a1bf2ff6-41a6-e840-676e-0eb4b9feed72
Content: Profile Container content - FSLogixhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-au%2Ffslogix%2Fmanage-profile-content-cncpt&data=02|01|Doug.Coombs%40microsoft.com|af1aeaa500ed42bb1c9e08d7dc670f4d|72f988bf86f141af91ab2d7cd011db47|1|0|637220207504333784&sdata=vmkLwKJR%2FIZ6G9qaFZ3z8%2B9PKZIkodcJb74ELXHtVuI%3D&reserved=0
Content Source: fslogix-docs/manage-profile-content-cncpt.mdhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Ffslogix-docs-pr%2Fblob%2Flive%2Ffslogix-docs%2Fmanage-profile-content-cncpt.md&data=02|01|Doug.Coombs%40microsoft.com|af1aeaa500ed42bb1c9e08d7dc670f4d|72f988bf86f141af91ab2d7cd011db47|1|0|637220207504333784&sdata=xWyGvDOolZIASVVGFZWalScO0zTcHHPWhH0CDHSqttU%3D&reserved=0
Product: fslogix
GitHub Login: @DougCoombshttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FDougCoombs&data=02|01|Doug.Coombs%40microsoft.com|af1aeaa500ed42bb1c9e08d7dc670f4d|72f988bf86f141af91ab2d7cd011db47|1|0|637220207504343776&sdata=AJgfQaAnEiNMcJSh%2FwvfMTveIkyx1Wa9iMV%2F7nsQMAQ%3D&reserved=0
Microsoft Alias: docoombs

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Ffslogix-docs%2Fissues%2F38&data=02|01|Doug.Coombs%40microsoft.com|af1aeaa500ed42bb1c9e08d7dc670f4d|72f988bf86f141af91ab2d7cd011db47|1|0|637220207504343776&sdata=zwMeA%2FN5yqM7O97mtwjoyh%2FGnGZebZ8t3DbmdTJ9OeM%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALSRDL4MHJ7QCB2YIY46FPDRLWHI3ANCNFSM4MESPSDQ&data=02|01|Doug.Coombs%40microsoft.com|af1aeaa500ed42bb1c9e08d7dc670f4d|72f988bf86f141af91ab2d7cd011db47|1|0|637220207504353771&sdata=fUaif00QtlewTy1BqrWuFKCaCYMvBkPKg4CR%2FYnjR48%3D&reserved=0.

This pull request is complete, and will be included in the docs update for 2009 docs release.  Thanks!


Feature/event bridge

Pull Request Test Coverage Report for Build 805

0 of 0   changed or added relevant lines in 0 files are covered.
73 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.8%) to 69.89%

Files with Coverage Reduction
New Missed Lines
%

dist/plugins/Trace.js
2
80.0%

dist/plugins/support/InvocationTraceSupport.js
18
64.84%

dist/plugins/integrations/AWSIntegration.js
53
67.05%

Totals

Change from base Build 799:
-0.8%

Covered Lines:
2612

Relevant Lines:
3484

💛  - Coveralls


How to implement such a widget with categories

Good afternoon. Please tell me how to implement such a widget with categories. There must also be an opportunity clear current refined values.

Hi, to implement the list you can use the RefinementList widget. To clear all the active refinements, you can use the ClearAll widget.

Thanks for the answer. Can I implement a multi-level menu of this kind using the RefinementList widget?

The widget HierarchicalMenu is designed to built such experience.


Updating MS Learn learning paths to Innovate

Added a link to a complementary MS Learn learning path which supports the Innovate section of CAF. Part of an exercise with Brian Blanchard to provide more specific guidance to our customers by recommending complementary learning paths from MS Learn.

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

Note: Must remove en-us after reviewed.

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

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

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

Resolved the merge conflicts.


Migrating from React.PropTypes

using prop-types package for newer React version 15.5.0

I went ahead and added both react updates to same branch as they were small

:+1:

@JedWatson without these changes, using the component with React >=15.5 emits red console errors that look like hard errors (thanks Facebook 😞); would be great to get this in soon

ping

@JedWatson Can you please merge this? Since the React 16 Update is coming soon, this is seriously necessary!

@chadams Maybe you can implement the suggested changes, then we could use this PR.

@derpoho can you merge this and continue fix the suggested changes, since we need to fix the react warning.

@derpoho or i can open a another PR after you merge this

@paranoidjk I can't merge it, i have no rights in this Repo, you must ask @chadams ;)

I don't think this is still maintained, maybe we should maintain a forked version? @paranoidjk

@afc163
Ok, i will fork this repo to react-component group and continue to mantain it.
still, thanks for @JedWatson great job.

Just FYI - I've been away for personal reasons but am picking this up at the moment and getting it ready for react 16, plus merging some other fixes.
@afc163 @paranoidjk I don't mind if you want to continue to maintain a fork, but you're welcome to help maintain this one if you like, just let me know.

Any progress on this guys?

@JedWatson 💯
Since our project https://ant.design/ is heavily rely on hammerjs, so  I'd like to help with mantain this one.
If you agree with this, please add me owner permission,  both my github and npm id is paranoidjk, email is<EMAIL_ADDRESS>thanks.

our fork is https://github.com/react-component/react-hammerjs

@JedWatson, I do not mean to hurry but any idea when this PR will be merged and a new NPM version will be available?

Sorry missed these comments. However, I'm not understanding what needs to be done.

Hey guys, this should do the work. https://github.com/JedWatson/react-hammerjs/pull/74

I removed the statics, is thats what is holding this up?

I can't use this wonderful tool in prod if it takes months to get fixes like these in. Perhaps another owner/maintainer should be added to this project. It is a pity because this tool is so easy.

@chadams Did you ever find out?

If I understand correctly, what's holding this up is that prop-types needs to be moved in package.json from devDependencies to dependencies. Can anyone confirm this?

@chadams @jrsinclair The move from devDependencies to dependencies is the only comment on the PR where changes were requested.  I would guess that's all that's holding this up.

Looks like a version with the amends has already been posted here: #74

This just became slightly more pressing, now that React 16 has been released.

Was this PR made redundant by #78?

There were a bunch of issues with this in the end, I've cleaned it up significantly and replaced the build system so it should be good now. Try using 1.0.1


Use Kubernetes common labels for Carrier objects

We are using custom labels to identify Carrier objects (e.g. here: https://github.com/SUSE/carrier/blob/main/paas/client.go#L485-L487)
There is some good reasoning on why standard labels are better in this page: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/
Doing this will help us identify and group objects that belong or where deployed by Carrier. This can also happen in some Web UI in the far future.

A new issue is created for the remaining work to be done. #218.


Wastore master to Azure master

@zezha-msft,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Add support for 10.0.17083.1000

termsrv_x64.zip

x86 (32-bit) DLL with build number 10.0.17083.1000 is also required to resolve this issue.

x86 (32-bit) DLL with build number 10.0.17083.1000 is also required to resolve this issue.