Custom LLVM_PROFILE_FILE Modes

In wgpu's tests, with 1000 or so tests with a large binary, we are running out of space holding all the intermediate profraw files. Each one is about 20MB, and there are a thousand of them, and it easily eats through the 14GB provided by github actions without paying more.
Looking at https://doc.rust-lang.org/rustc/instrument-coverage.html#running-the-instrumented-binary-to-generate-raw-coverage-profiling-data it seems like there are modes which consolidate the data into a few files. Notably %Nm looks very useful for this use case.
It would be nice to have a flag, or some other mechanism to get access to this. There is a limit on parallelism (9, per the docs) so it isn't good for all situations, but if you're on a constrained system like CI, this restriction is fine.

Looking at https://doc.rust-lang.org/rustc/instrument-coverage.html#running-the-instrumented-binary-to-generate-raw-coverage-profiling-data it seems like there are modes which consolidate the data into a few files. Notably %Nm looks very useful for this use case.

I'm not sure that will fix the problem. If you are using nextest you are already using it.
https://github.com/taiki-e/cargo-llvm-cov/blob/e3dd19fe090eb27ec37f8c41ed129c0aa838054e/src/main.rs#L214-L230

From experience, my impression is that when there is a disk usage problem, it is easier to just free up disk space than to look for workarounds to reduce disk usage.

From experience, my impression is that when there is a disk usage problem, it is easier to just free up disk space than to look for workarounds to reduce disk usage

Unfortunately at the rate our test disk space are growing, that is only buying us a little time until we need to start using the larger github runners with more space.

I'm not sure that will fix the problem. If you are using nextest you are already using it.

Interesting - the idea I was thinking of was using {}-%{}m instead of {}-%p-%{} so that as much re-use as possible happens. I wonder if the PID behavior on windows causes more usage than on linux/mac where we didn't hit this problem.

the idea I was thinking of was using {}-%{}m instead of {}-%p-%{}m so that as much re-use as possible happens.

Ah, interesting.
I've implemented this in llvm-profile-file-name branch. Could you try to see if it works as expected?
cargo install cargo-llvm-cov --git https://github.com/taiki-e/cargo-llvm-cov --branch llvm-profile-file-name

LLVM_PROFILE_FILE_NAME='<name>.profraw' cargo llvm-cov ...

Nice!
Using the default profile name, running wgpu's 1000 test, test suite on my windows machine results in: 14.3 GB of profraw files.
Using "wgpu-%8n.profraw" as the profile name, I get 26 (264MB) profraw files.
Using "wgpu-%n.profraw" as the profile name, I get 13 (125MB) profraw files.
I built the reports from the various runs and they were completely identical. Additionally, changing the number of allowed profiles didn't seem to affect runtime at all, though we generally have longer running tests (4s each).
This is a massive win for us, and completely eliminates the problem. I might actually suggest that the nextest default be {}-%Nm, as this feels like a much better default.

Just tested with a subset of our tests which are very fast (<0.1s each) and the profile file name setting makes no difference in suite runtime.

Published in v0.6.2. Thanks for testing this!

I might actually suggest that the nextest default be {}-%Nm, as this feels like a much better default.

Yeah, it would be preferable to do so if it would not affect the accuracy.


Change K9-Mail signing to new setup

This changes the signing configuration to allow easier addition of different signing configs for our different app variants. Keystores are now located in the .signing directory, accompanied by signing.properties files that provide the necessary keys. This avoids having to declare global properties for all the different variants.
This is the first iteration to change signing for K-9 Mail. Thunderbird for Android will follow shortly.

It strips the signing config from the build script:

^[\t ]*signingConfig\s*[= ]\s*[^ ]*$ matches signingConfig = signingConfigs.getByType(SigningType.K9_RELEASE)


Configuring the Xcode plugin to generate the source code for checkin

Question
I'm using the Xcode plugin successfully but the code completion is working slowly, the generated names are very cumbersome and navigating the generated code is awkward. I can't find where the generated code is actually located when I "cmd click" to navigate to it.

My thought is to continue using the Xcode plugin to produce the code in a file (as the cli tool does), and then I will add the generated code to my project and check it in. This will also allow me to customize some of the awkwardness.
Here are some examples of the cumbersome code I am encountering

client.post_sol_api_sol_v3_sol_order_sol_oco(<#T##input: Operations.post_sol_api_sol_v3_sol_order_sol_oco.Input##Operations.post_sol_api_sol_v3_sol_order_sol_oco.Input#>)

Hi @avnerbarr,
the long names are due to your OpenAPI doc not specifying a human-friendly operationId for each operation. You could ask the vendor of the OpenAPI doc to add those, and then you'll get exactly those names as long as they stick to the recommended character set for operationId, which is [a-zA-Z0-9_].
Regarding issues using Xcode with build plugins, please direct those to https://feedbackassistant.apple.com, those are not tracked as part of this project.
But yes, manually invoking the CLI is another supported way to use the tool: https://swiftpackageindex.com/apple/swift-openapi-generator/1.2.0/documentation/swift-openapi-generator/manually-invoking-the-generator-cli
If you have any specific questions or issues related to this project, please file new GitHub issues, thanks!


Const.dart file issue

You need to update it to remove 'cursorColor', worked for me after removing both of those lines
lib/util/const.dart:39:5: Error: No named parameter with the name 'cursorColor'.
cursorColor: lightPrimary,
^^^^^^^^^^^

is this issue still open?


Missing LICENCE file

http://choosealicense.com/
MIT?

Yeah, it's MIT. It was added in e96a71792f23f9d602a882eb504c36f5566faef9 but it looks like it's not in the default branch.

Closed in #98 & #100


Question: Is it possible to avoid long relative paths ?

Could you point me on an example of how to configure flow.js so that I could just use the name of a file for imports instead of long relative paths ?. This implies that the name of my files in my entire working directory are unique.
example:
Directories
pages/components/foo.js
common/types/abc.js

Current import statements
import foo from "../../pages/components/foo"
import abc from "../common/types/abc"

Desired import statements
import foo from "foo"
import abc from "abc"

I guess this refers to https://github.com/facebook/flow


Review subdomain_from_request usages

During the CR of #11361 I wondered which subdomain_from_request are actually correct. A quick search brought up this usage pattern:
  def eligible_for_redirect?(user)
    return false if CartoDB.subdomainless_urls?
    user.has_organization? && !request.params[:redirected].present? &&
      CartoDB.subdomain_from_request(request) != user.organization.name
  end

As you see, it checks if subdomainless is enabled and then returns.
The needed fix at #11361 is likely needed in other cases. As extract_subdomain covers more scenarios, it should be probably used. If it's not, maybe a refactor that wraps those methods in others with intention revealing names (username_from_url or something similar) might be interesting.
Of course, minor, and changes like this involves thorough testing.
cc @CartoDB/builder-backend

Closing automatically because of inactivity. If anybody considers that this still important, please reopen and it'll be prioritized.


.setScreenName() for iOS

It seems this method is only implemented for Android devices (should be in readme). Can we also please have it for iOS?

I'll take a PR

I implemented this method only in Android because I'm not too experienced programming for iOS. I didn't indicate it in the readme because I assume it'll be implemented before doing the next release (in case it isn't it should be documented yes). You can see the status of the feature in this issue: https://github.com/arnesson/cordova-plugin-firebase/issues/98


invokeWithInvocationModeAndOptions method doesn't exist in iOS module

This part guides to use the invokeWithInvocationModeAndOptions method in BugReporting module. BugReporting.invokeWithInvocationModeAndOptions calls same method in the iOS module that doesn't have invokeWithInvocationModeAndOptions method.
I think BugReporting.invokeWithInvocationModeAndOptions method should process differently depending on OS or add a new method invokeWithInvocationModeAndOptions in the iOS module.
Below is my temporary workaround.
// In modules/BugReporting.js file
invokeWithInvocationModeAndOptions: function (invocationMode, invocationOptions) {
  if (Platform.OS === 'ios') {
    Instabug.invokeWithInvocationMode(invocationMode, invocationOptions);
  } else {
    Instabug.invokeWithInvocationModeAndOptions(invocationMode, invocationOptions);
  }
},

Thanks for pointing that out! We're working on a fix and will release it very soon.

We just released a fix for this and #180. Please update to 8.0.2.

Thanks for the quick fix! 👍


Fuel consumption increasing over time

I like this mod, and I think the jetpacks are well-balanced for some use cases. Unfortunately, in some situations they are extremely overpowered, and causes other problems as well.
A big problem in my opinion is that jetpacks can be used as a way of travelling long distances. They are completely overpowered for that purpose, and makes all other ways useless. It requires 0 setup (unlike for example minecart networks), can be used to travel to any given location, and mainly, it is a lot faster than all other methods. It also causes the server to lag, because chunks are loaded in too quickly.
The problem would be solved if fuel consumption was to increase over time. Then, jetpacks would not be overpowered for travelling, but still useful for all other purposes. When used, jetpacks should "heat up", more heat increasing fuel consumption. When not used, "heat" will go down over time. It should be added as a config option, since everyone wouldn't like this addition.

"A big problem in my opinion is that jetpacks can be used as a way of travelling long distances." (sic)
Hey, guess, what! This is EXACTLY what jetpacks are for!

You don't need a setup because you need RF to go. RF aren't naturally generated.

A fix for the lag is to reduce the speed a jetpack can move while flying. however you'll have to do that to every tier to make it balanced.

Stargates, Teleporters, /home set, plugins for warp stations. all of these can be included in a Server to minimize players flying everywhere with jetpacks. but if someone just wanted to lag up a server and cause lag, yes they can do that with jetpacks. you'll need to tweak chucks loading / unloading and get more ram to cover the loaded chuncks until they can get unloaded safely without causing massive lag.

This request makes no sense fuel usage is a constant rate the only thing that would actually affect the rate of fuel consumption would be the players weight which to the best of my knowledge is not calculated

This request is pointless. Don't install jetpacks on your server if your server can't handle them.

Jetpacks being overpowered for you seems to be the real issue here. Their speed and other properties can be changed/nerfed in the config, or disabled completely through MineTweaker.


add standalone launch gateway

Describe your changes
Adds a standalone launch page when opening the app on the base url.  When opening localhost:3000 the app will show a form that allows the user to input the iss/client/scopes before launching.  Inputs default to the value in the env file so if you just want to connect to the regular ehr, you can launch immediately.
You can test by changing the values in the inputs and seeing that it connects to the chosen ehr.
There is some room here to connect with the client id registration task and have the dropdown menus include a list of iss/clients, and automatically loading the associated iss/client when you choose the counterpart.
Issue ticket number and Jira link
REMS-573
Checklist before requesting a review

[x] I have performed a self-review of my code
[x] Ensure the target / base branch for any feature PR is set to dev not main (the only exception to this is releases from dev and hotfix branches)

Checklist for conducting a review

[ ] Review the code changes and make sure they all make sense and are necessary.
[ ] Pull the PR branch locally and test by running through workflow and making sure everything works as it is supposed to.

This works great to connect to the test-ehr running locally, but I am having trouble connecting to meld.
My settings are the following:
FHIR Server Endpoint: https://gw.interop.community/REMS/data
Client ID: ed8b940e-4aaa-4209-b17d-69dfe67543b9
Scope: launch offline_access openid profile user/.
It complains about the scopes. I get the same error when I try the default scopes. The scopes I have listed here are what worked for me when I set them in the .env file and was able to connect.

recent commit should fix it, note that the scopes must match what meld has registered for the specific client.  Also the test-ehr does not validate scopes so this error did not occur there.


Feature: Add Client Library API Documentation

Add documentation for each method within this client library that maps to an M2X API call.
Guidelines & Tips:

Use appropriate syntax for this programming language
Documentation for each method should include the exact title and url for the associated AT&T M2X API endpoint. Example: "Method for List Devices endpoint."
All input parameters should be documented, including datatype
All return values should be documented, including datatype
Please use the Python Client Library documentation as a reference: http://m2x-python.readthedocs.io/en/latest/

Will do!

@kristinpeterson Will do!

@azarc3 thank you!


[SPARK-4905][STREAMING] FlumeStreamSuite fix.

Using String constructor instead of CharsetDecoder to see if it fixes the issue of empty strings in Flume test output.

Test build #26773 has started for   PR 4371 at commit af3ba14.

This patch merges cleanly.

Lets run this a bunch of times on the pull request builder and see if it is still flaky

Could explain what going wrong here? How was this flaky? Something like this should fail every time, isnt it?

Test build #26773 has finished for   PR 4371 at commit af3ba14.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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

Test build #583 has started for   PR 4371 at commit af3ba14.

This patch merges cleanly.

Sorry, I was not clear enough. I am running this here to see how we can reproduce this. As of now the only place where I have seen this fail is on Jenkins. I am going to update this PR with incremental changes until I know what the issue is.
I will ping you once this is ready for review/merge.

Aah, that wasnt clear. Gotcha.

Test build #583 has finished for   PR 4371 at commit af3ba14.

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

Jenkins, test this.

Test build #584 has started for   PR 4371 at commit af3ba14.

This patch merges cleanly.

Test build #584 has finished for   PR 4371 at commit af3ba14.

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

Test build #585 has started for   PR 4371 at commit af3ba14.

This patch merges cleanly.

Test build #585 has finished for   PR 4371 at commit af3ba14.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #587 has started for   PR 4371 at commit af3ba14.

This patch does not merge cleanly.

Test build #587 has finished for   PR 4371 at commit af3ba14.

This patch fails Spark unit tests.
This patch does not merge cleanly.
This patch adds no public classes.

Test build #588 has started for   PR 4371 at commit af3ba14.

This patch merges cleanly.

Test build #588 has finished for   PR 4371 at commit af3ba14.

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

Jenkins, test this please.

Test build #26937 has started for   PR 4371 at commit af3ba14.

This patch merges cleanly.

Test build #26937 has finished for   PR 4371 at commit af3ba14.

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

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

Jenkins, test this please

Test build #26956 has started for   PR 4371 at commit af3ba14.

This patch merges cleanly.

Test build #26956 has finished for   PR 4371 at commit af3ba14.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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

Failure was unrelated to this commit.

Jenkins, test this please

Test build #26974 has started for   PR 4371 at commit af3ba14.

This patch merges cleanly.

Test build #26974 has finished for   PR 4371 at commit af3ba14.

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

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

According to the Javadocs, CharsetDecoder is not thread-safe: Instances of this class are not safe for use by multiple concurrent threads..  This might explain the flakiness, so this LGTM.

Jenkins, retest this please.

Test build #27027 has started for   PR 4371 at commit af3ba14.

This patch merges cleanly.

Test build #27027 has finished for   PR 4371 at commit af3ba14.

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

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

Actually, is this a thread-safety issue?  I guess that outputEvents is a driver-local collection, not an RDD, so the decoder should only be used from one thread.

Jenkins, retest this please.

Test build #27076 has started for   PR 4371 at commit af3ba14.

This patch merges cleanly.

@JoshRosen i dont think its a thread safety issue. But i think it is some issue with decoder, as the error turns out to be that the decoded strings are empty. So it may be better with this change where decoder object is not used across multiple objects.
@harishreedharan Could you please follow @JoshRosen suggestion on using Charset objects in all the places, rather than string "UTF=8" that is prone to errors?

@JoshRosen, @tdas - Thanks for the review!
Updated the PR to use Charsets.UTF_8.

Test build #27076 has finished for   PR 4371 at commit af3ba14.

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

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

Test build #27081 has started for   PR 4371 at commit 550d363.

This patch merges cleanly.

Test build #27081 has finished for   PR 4371 at commit 550d363.

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

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

Jenkins, test this please

Test build #27114 has started for   PR 4371 at commit 550d363.

This patch merges cleanly.

Test build #27114 has finished for   PR 4371 at commit 550d363.

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

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

Ping @JoshRosen @tdas

Jenkins, test this please

Test build #27123 has started for   PR 4371 at commit 550d363.

This patch merges cleanly.

Test build #27123 has finished for   PR 4371 at commit 550d363.

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

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

LGTM, so I'm going to merge this into master (1.4.0) and branch-1.3 (1.3.0).  I'm going to close the JIRA ticket for now, but let's re-open it if we see any more flakiness from this test.

I've also merged this into branch-1.2 (1.2.2).


[Enhancement] Support json_array_get function for trino parser

Fixes #issue
#14825
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.1
[x] 3.0
[ ] 2.5
[ ] 2.4

[FE PR Coverage Check]
:heart_eyes: pass : 12 / 13 (92.31%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/connector/parser/trino/ComplexFunctionCallTransformer.java
7
8
87.50%
[48]

:large_blue_circle:
com/starrocks/connector/parser/trino/AstBuilder.java
5
5
100.00%
[]

@Mergifyio backport branch-3.1

@Mergifyio backport branch-3.0


Core MVC template database file name starts with a backslash on Linux/Mac

From @DesktopMan on April 14, 2017 22:36
From the template's appsettings.json:
"DefaultConnection": "DataSource=.\\test.db"

This has two presumably unintentional consequences: The file becomes hidden and the name starts with a backslash. My students had trouble finding the file to inspect it until I pointed this out.
Copied from original issue: aspnet/Templates#840

It appears that othing needs to be done for this issue. From the history & references of the related issues, it appears this was fixed back in June in this PR: https://github.com/dotnet/templating/pull/904
Looking through this repo, all the appsettings.json files in StarterWeb templates have their default connections setup as "DefaultConnection": "DataSource=app.db"
@Eilon - if there is anything else that needs to be done, please let me know.

@seancpeters ah yes that appears to be the case, so closing this.


Postgresql as broker

Any plans to add PostgreSQL to list of brokers?

I can support it if there is a demand. It would be helpful if you could share your use cases.

So I need to add a queue system to https://gitlab.com/gadelkareem/skeleton . And since I am deploying the demo to Heroku free tier, PostgreSQL is the easiest way to manage the queue. Moreover using database for queueing is very common in many frameworks ex https://laravel.com/docs/7.x/queues
There are a lot of advantages for using PostgreSQL, ex https://gist.github.com/chanks/7585810 , and there is a port for ruby gem to Golang here https://github.com/bgentry/que-go

It looks like it is not officially supported by the Celery project. https://github.com/celery/celery/issues/5149
I don't think free tier availability is a good reason to support entire new broker/backend.

I can support it if there is a demand. It would be helpful if you could share your use cases.

Hi. We have another use case. We have multi-zone database (CockrochDB) that is wire compatible with Postgresql. It would be nice to use postgres as broker for deploying multi zone/datacenter celery worker that are synced by backend broker. With this we can achieve symmetric deployments on multi datacenter.
Is there any other solution for synchronizing workers? like using cockroachdb as lock management system and try to obtain a lock before every task?  i don't know how can i prevent to run tasks in not leader cluster. Is there any workaround for running a function before every task (like prerun hook) and don't run main task if this function fails?

@bbkgh just use routing https://docs.celeryproject.org/en/stable/userguide/routing.html#manual-routing
So you can route your task to leader cluster
Also you can always raise an exception it task and handle it to make celery task failed in controllable way

We have multi-zone database (CockrochDB) that is wire compatible with Postgresql.

Worth pointing out on here that CockroachDB don't support NOTIFY/(UN)LISTEN https://github.com/cockroachdb/cockroach/issues/41522 but they are considering it from user requests.


Fix streaming upload

Uploading blob that was read from source like pipe was not working correctly due to couple of bugs.

Codecov Report

Merging #670 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #670   +/-   ##
=======================================
  Coverage   86.98%   86.99%
=======================================
  Files          52       52
  Lines        5288     5289    +1
  Branches      566      567    +1
=======================================
+ Hits         4600     4601    +1
  Misses        515      515
  Partials      173      173

Impacted Files
Coverage Δ

...torage-blob/azure/storage/blob/_upload_chunking.py
71.96% <100.00%> (+0.10%)
:arrow_up:

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 9cbce66...8ee7dd5. Read the comment docs.


Imandana fix

My First PR.
Bug Fix on
https://trello.com/c/Ovaie0Fj/159-bug-prevent-changemaximum-to-have-value-0

Sorry for commenting this PR in bad situation, I think you fixed and joined the wrong card, https://trello.com/c/iDPexdUt/164-bug-everything-isnt-allowed-to-be-inputted-under-zero, it is the bug that you should have fixed before. For your information, the ChangeMaximum button bug has been fixed, but this revision will be accepted due to better feature. Please continue fixing the following bug (https://trello.com/c/iDPexdUt/164-bug-everything-isnt-allowed-to-be-inputted-under-zero)

Sorry for commenting this PR in bad situation, I think you fixed and joined the wrong card, https://trello.com/c/iDPexdUt/164-bug-everything-isnt-allowed-to-be-inputted-under-zero, it is the bug that you should have fixed before. For your information, the ChangeMaximum button bug has been fixed, but this revision will be accepted due to better feature. Please continue fixing the following bug (https://trello.com/c/iDPexdUt/164-bug-everything-isnt-allowed-to-be-inputted-under-zero)


Move back to Angular 1.4.4 from Angular 1.4.8 to resolve bower confli…

…ct resolution. Our options are 1.4.4 or 1.5.0. So 1.4.4 was chosen.
bower angular                        resolution Unsuitable resolution declared for angular: 1.4.8
Unable to find a suitable version for angular, please choose one:
1) angular#1.3.20 which resolved to 1.3.20 and is required by angular-route#1.3.20, angular-sanitize#1.3.20
2) angular#~1.3.5 which resolved to 1.3.20 and is required by hawtio-core#2.0.30
3) angular#1.4.4 which resolved to 1.4.4 and is required by angular-animate#1.4.4
4) angular#* which resolved to 1.5.0 and is required by angular-clipboard#1.3.0, angular-md5#0.1.10, angular-momentjs#0.2.2, angular-wizard#0.6.1
5) angular#>=1.3.0 which resolved to 1.5.0 and is required by angular-bootstrap#0.13.4, angular-toastr#1.6.0
6) angular#^1.2.16 which resolved to 1.5.0 and is required by angular-scroll#0.6.5
7) angular#^1.3.0 which resolved to 1.5.0 and is required by hawkular-charts#9bfefa9
8) angular#1.5.0 which resolved to 1.5.0 and is required by angular-resource#1.5.0
9) angular#>= 1.2.0 which resolved to 1.5.0 and is required by ng-idle#1.0.4
10) angular#>=1.2.0 which resolved to 1.5.0 and is required by ngInfiniteScroll#1.2.1
11) angular#>=1.2.18 which resolved to 1.5.0 and is required by angular-ui-select#0.11.2
12) angular#^1.3.5 which resolved to 1.5.0 and is required by hawkular-ui-services#0.8.23

Original blocking  bower conflict is solved:
[ERROR] bower angular                       resolution Unsuitable resolution declared for angular: 1.4.8
[ERROR] bower                                ECONFLICT Unable to find suitable version for angular
There is still some license check issues with some repos that need to get fixed.
But everything builds with -Dlicense.skip so there are no compile blockers.

Merged #835


Save to the same-directory as the tack is not working non-ANSI path

the "Save to the same-directory as the tack" option is not working on non-ANSI characters path, like path with Japanese or Korean characters

What do you mean by "not working"? What does it do and what do you expect it to do instead?
When this happens, does the console (Menu Bar -> View -> Console) show any warnings or errors for OpenLyrics?

Closing this because I just tried it with a directory that contained Japanese and Korean characters, it seemed to work fine. Open a new ticket if you're still experiencing this on the latest release and please include some more info.


feat(Media): add new AudioSession class for configuring audio on iOS

Add AudioSession and AudioConfiguration
Configure audio session in WebRTCMediaConnection
Add audio route picker view in demo

Looks like AVRoutePickerView stops camera, which is a bit unfortunate.

Looks like AVRoutePickerView stops camera, which is a bit unfortunate.

No biggie.


[ENH] New Transformer: Outlier detection based on Interquartile range

Is your feature request related to a problem? Please describe.
I would like to use an Interquartile range filter to detect outliers in time series.
Describe the solution you'd like
A Transformer similar to the already existing HampelFilter , creating np.nan values and allowing them to be imputed afterwards.
Additional context
If that is something you think is useful, I could create a PR for this.

hm, @shagn, is that not already possible by combining something from pyOD with the TabularToSeriesAdaptor?

ok, it doesn´t work, because pyod has predict and not transform in its interface.
How about a transformer RemoveOutliers that is based on TabularToSeriesAdaptor, and internally uses predict instead of transform, and has a parameter that controls what happens to the outliers, e.g., na is filled (default?) or they are simply removed.
Then you can pipeline with Imputer or a similar transformer if you want to do something more fancy.

Hey @fkiraly,
sorry for the long delay.
Regarding the PyodOutlierRemover or similiar: why would you base it on the TabularToSeriesAdaptor?
Would it not be quite similar to the PyODAnnotator? Meaning the new transformer would accept an PyOD estimator and in the _transform the predict function of the fitted estimator would be called.


In comes a real README.md

Messed up the workflow, but followed git's suggestions to open the branch.

Hope I merged that correctly and didn't clobber anything.


add version template to keep in sync with tito

TEST
[jesusr@speed3 ansible-service-broker{version}]$ ./broker --version
0.1.0
[jesusr@speed3 ansible-service-broker{version}]$ tito tag
Tagging new version of ansible-service-broker: untagged -> 0.1.2-1
Created tag: ansible-service-broker-0.1.2-1
   View: git show HEAD
   Undo: tito tag -u
   Push: git push origin && git push origin ansible-service-broker-0.1.2-1
[jesusr@speed3 ansible-service-broker{version}]$ make build
go build -i -ldflags="-s -w" ./cmd/broker
[jesusr@speed3 ansible-service-broker{version}]$ ./broker --version
0.1.2


bots: Fix a Chessbot dependency error.

This PR specifies a version for Chessbot so that it will continue to function properly if the library is updated. This also updates test-bots to remove a temporary fix for Chessbot.

Merged, thanks @skunkmb!


added loadingMessage() option for ajax calls

I have been using sweet alert on a project with a few ajax calls that may take a little while to finish.
On top of the swal.disableButtons() spin effect, I wanted a way to show a "loading" message, to replace the original alert message used before initiating the ajax call.
For example, a "Are you sure?" message could hang for a few seconds until the ajax call was finished.

thanks for contributing @crabbly but I can't merge this PR. loadingMessage() is the method that related to your project, not to this plugin. In other words it's too custom, I want to keep this plugin as simple as possible.


EXC_BAD_ACCESS on release executions

I tried to run this project using the release version and they all crash at:
   mpscnn = MPSCNNFullyConnected(device: device,                                   convolutionDescriptor: desc,                                   kernelWeights: weights.pointer,                                   biasTerms: biasTerms,                                   flags: .none)
In createCompute of layers.swift
Only MNIST project, which does not use Forge, seems to work.
This means that an app using this library cannot be compiled to be sent to the app store, ad hoc or enterprise distribution.

What version of iOS are you trying this on? I think I know why this happens but didn't see it on my devices yet.

Hi @hollance
I am using an iPhone 6 64gb running iOS 11.1 (15B93)

This is actually an issue I ran into before and thought I had fixed but apparently not. With optimizations enabled, Swift deallocates the object containing the bias terms for the layer before the layer gets constructed. This seems like a compiler error since there are still (optional) objects with a reference to this object and so it gets deallocated too soon. It also doesn't happen with optimizations disabled. I'll see if I can find a workaround.

This should be fixed in https://github.com/hollance/Forge/commit/14a6d7229c8e8c14c0d18f429c91fd628d694067


fix: top level required does not apply to allOf sub schemas

🚨 IMPORTANT: Please do not create a Pull Request without creating an issue first.
Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of
the pull request.
Description
Top level required does not apply to allOf sub schemas.
When a schema with allOf sub schemas has a required on a property that exists in all of schemas, but one or all sub schema's don't have a required on this field, the required isn't inherited and the field in the generated Graphql type not marked as required and is invalid.
  OpenAPI loader: Required allOf
    ✕ type should be required in all types (6 ms)

  ● OpenAPI loader: Required allOf › type should be required in all types

    expect(received).toMatchInlineSnapshot(snapshot)

    Snapshot name: `OpenAPI loader: Required allOf type should be required in all types 1`

    - Snapshot  - 1
    + Received  + 1

    @@ -13,11 +13,11 @@

      type Admin implements User {
        "The Name."
        name: query_getAdmin_allOf_0_name
        "The type"
    -   type: String!
    +   type: String
        "The admin"
        admin: Boolean
      }

      interface User @discriminator(field: "type") {

Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as
expected)
[ ] This change requires a documentation update

Screenshots/Sandbox (if appropriate/relevant):
Adding links to sandbox or providing screenshots can help us understand more about this PR and take
action on it as appropriate
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can
reproduce. Please also list any relevant details for your test configuration

[x] required-allof.test.ts

Test Environment:

OS:
@graphql-mesh/...:
NodeJS:

Checklist:

[ ] I have followed the
CONTRIBUTING doc and the
style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests and linter rules pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose
the solution you did and what alternatives you considered, etc...

Came up with a more elegant fix. non nullable fields now never get overwritten.


Improving docs and more

required to
fix https://github.com/Lundalogik/crm-feature/issues/3820

required to
fix https://github.com/Lundalogik/crm-feature/issues/3820

How exactly is this required for that issue? 🧐

required to
fix Lundalogik/crm-feature#3820

How exactly is this required for that issue? 🧐

If we don't have this, in the linked PR of Lime Elements, all components will inherit their font-family from Kompendium ('Lato', sans-serif;), which is not what we want. Instead, we want the feature introduced here in this PR: e3be024 (#130) to be able to specify what font family is the one that examples should run.
If not clear, call me so I can explain.

The reason this PR became too big was because I wanted to add documentations for this new feature, but there was no good place for adding the docs. 😅 so I had to do some changes to prepare the foundation for it.

The reason this PR became too big was because I wanted to add documentations for this new feature, but there was no good place for adding the docs. 😅 so I had to do some changes to prepare the foundation for it.

Yeah, I'm sure these changes are all great, I just felt a bit stressed out having to review them all just to get the new feature in. So it felt better to separate them. I think we should definitely keep this PR though, and get these changes in at some point 👍


Circles speed during the test

Actually, we can configure the speed of circle switch time, during the test, with a dropdown implemented into the UI.
But when the program run, the speed is not constant, and some circles can stay more than switch time set.
Need to check if it was a problem of computer or not, and if its not, need to check code to resolve the issue.

This seem to be fixed now.


btc: get bitcoin network ID from WIF

I refactored this to use it in alice

This change is

Reviewed 3 of 3 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

blockchain/btc/btc.go, line 38 at r1 (raw file):

var (
	// ErrUnknwonBitcoinNetwork is returned when the network ID associated to the WIF is unknown.
	ErrUnknwonBitcoinNetwork = errors.New("WIF encoded private key uses unknown Bitcoin network")

nit: typo (Unknown)

blockchain/btc/btc.go, line 48 at r1 (raw file):

	WIF, err := btcutil.DecodeWIF(key)
	if err != nil {
		return "", errors.Wrapf(err, ErrBadWIF.Error())

nit: why Wrapf instead of Wrap?

blockchain/btc/btc_test.go, line 63 at r1 (raw file):

			net, err := btc.GetNetworkFromWIF(tt.wif)
			if tt.err == "" {
				assert.Equal(t, net, tt.expectedNetwork)

nit: you could also assert.NoError in this if branch

Comments from Reviewable

Reviewed 3 of 3 files at r1.
Review status: all files reviewed at latest revision, 3 unresolved discussions.

Comments from Reviewable

Review status: all files reviewed at latest revision, 3 unresolved discussions.

blockchain/btc/btc.go, line 38 at r1 (raw file):
Previously, t-bast (Bastien Teinturier) wrote…
nit: typo (Unknown)

Done.

blockchain/btc/btc.go, line 48 at r1 (raw file):
Previously, t-bast (Bastien Teinturier) wrote…
nit: why Wrapf instead of Wrap?

Done.

blockchain/btc/btc_test.go, line 63 at r1 (raw file):
Previously, t-bast (Bastien Teinturier) wrote…
nit: you could also assert.NoError in this if branch

Done.

Comments from Reviewable

Reviewed 2 of 2 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 3 of 3 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks pending.

blockchain/btc/btc_test.go, line 49 at r1 (raw file):

			wif:             "fakeWIF",
			err:             errors.Wrap(btcutil.ErrMalformedPrivateKey, btc.ErrBadWIF.Error()).Error(),
			expectedNetwork: btc.NetworkTest3,

not really thou

blockchain/btc/btc_test.go, line 55 at r1 (raw file):

			wif:             "5KrPNVvAhnRBNMYRJUq58YMfyUMyVMQrQhhfFtcbT9rK67poC3F",
			err:             btc.ErrUnknwonBitcoinNetwork.Error(),
			expectedNetwork: btc.NetworkTest3,

not really neither

Comments from Reviewable

Reviewed 1 of 1 files at r3.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

Comments from Reviewable

Review status: all files reviewed at latest revision, 2 unresolved discussions.

blockchain/btc/btc_test.go, line 49 at r1 (raw file):
Previously, such (Adrien Montfort) wrote…
not really thou

:tired_face:

blockchain/btc/btc_test.go, line 55 at r1 (raw file):
Previously, such (Adrien Montfort) wrote…
not really neither

Done.

Comments from Reviewable

blockchain/btc/btc_test.go, line 55 at r1 (raw file):
Previously, simonvadee (Simon Vadée) wrote…
Done.

thanks

Comments from Reviewable

Reviewed 1 of 2 files at r2, 1 of 1 files at r3.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

Comments from Reviewable


Implements a comment directive to skip the next translation group.

This is the beginning of support for handling special comments for translation, https://github.com/google/mdbook-i18n-helpers/issues/63
This adds support for adding a comment of the form: <!-- mdbook-xgettext: skip -->.  This will cause the system to skip the next message group that would otherwise be translated.
It adds a dependency to the regex crate to match for the comment skip pattern.

Thoughts on using <!-- NO-TRANSLATE --> instead? I think the use of all-caps signifies that this comment is for machine interpretation, and the words are specific enough that they would not conflict with anything not translation-related, so there is no need to scope them with mdbook-xgettext.

Yeah, it's rather long indeed...
I suggested the long form in #63 and it's slightly inspired by how xgettext supports special xgettext:c-format and xgettext:no-c-format comments. However, the manual also talks about a TRANSLATORS: prefix, which is more your style (I believe you trigger this with xgettext --add-comments=TRANSLATORS).
I'm not entirely sure where we should land, but we should try to think of how skipping can work with more directives in the future: translator comments and a message context.

@mgeisler 's questions on what happens with the current implementation and inline sections made me reconsider.  I didn't know offhand what exactly would happen, and that to me is a warning sign.
I'd rather it be obviously clear.  So maybe it might make a safer and robust feature to have the skips define regions, rather than implicitly skip the next block.  Explicitly marking off the start and end of a skip section feels both simpler and clearer to me.
It would look something like this
<!-- mdbook-xgettext: skip-start -->
This content is ignored.
<!-- mdbook-xgettext: skip-end -->

This would make it easier to see what sections are being ignored, removing ambiguity on the boundaries of the skipped region.
Would you be amendable to this proposed change to the feature?

It would look something like this
<!-- mdbook-xgettext: skip-start -->
This content is ignored.
<!-- mdbook-xgettext: skip-end -->

This would make it easier to see what sections are being ignored, removing ambiguity on the boundaries of the skipped region.
Would you be amendable to this proposed change to the feature?

I'm more thinking that we could have both. The immediate use case for skipping is to remove some very large code listings from the PO files for Comprehensive Rust. There your current implementation will already work great and I think we should merge it already.
A next step could be to support skipping regions like you suggest — I think this is a great idea! Infact, I just found a tool today which supports similar comments: mdpo.
Seeing the comments they support gives me an idea: we could use i18n as a shorthand for mdbook-i18n-helpers and implement these comments:

i18n-skip: this PR, skips next event,
i18n-disable: starts skipping events,
i18n-enable: stops skipping,
i18n-comment: translator comment,
i18n-context and i18n-ctx: sets message context for next (or following?) event.

Sounds good!  I have added more tests but have left the rest of the implementation as is; we can follow up with changing the keyword in a subsequent PR.

I note that there is appears to be a bug in the Markdown parser that I've reported upstream as https://github.com/raphlinus/pulldown-cmark/issues/712.  The bug causes content on the same line as an inline HTML comment to be "glued" to the comment.  In the case of our comment-skipping directive, this means that some of the behavior in this PR is due to  accident rather than intention.  :)
I do have a workaround for the inline HTML comment bug, prepared in https://github.com/google/mdbook-i18n-helpers/compare/main...dyoo:mdbook-i18n-helpers:isolate_first_html_comment.  If it turns out that fixing the bug upstream is taking too much time, I can clean up that branch and prepare it for a PR.  I wanted to give you a heads up so that we're aware of the issue.

Hey @dyoo, thanks for the update! I ran dprint fmt (the formatter we use in this repository) and pushed the result back to your branch. I also squashed the commits: that way every commit will pass all CI tests.
In general, I prefer to edit existing commits instead of having a string of commits in the history — especially if the string of commits represent fixes to comments that came up through code review. I wrote down some thoughts on this more than 10 years ago, in case you're curious :smile:


[5.8] Use the getDirty method on insert instead of getAttributes

Same as #25559, except this time targeting new version as you said you wouldn't change something like this on a point release.
Below is a comment from previous PR:
In #25349 performInsert() was changed to use getAttributes() instead of accessing $attributes property directly, thus having more similar behavior to performUpdate().
I think it is better to use getDirty() in performInsert() as well.
Currently if we override getAttributes() method and return additional property the insert is going to fail, while update can pass if we override originalIsEquivalent() and return true for that additional property.

@taylorotwell it has been 17 days like this not for years. $attributes property was accessed directly and overriding getAttributes() method didn't cause a problem with performInsert(). Now if we override getAttbibutes() and return some transient attributes there as well we will have a problem with insert. Before 17 days we didn't have this problem.


Treebank Pull Requests

Do you take pull requests for corrections to the treebanks?

Closed in favor of https://github.com/perseids-publications/treebank-template/issues/67 (see https://github.com/perseids-publications/harrington-trees/issues/5)

Closed in favor of https://github.com/perseids-publications/treebank-template/issues/67 (see https://github.com/perseids-publications/harrington-trees/issues/5)


Install through cocoapods will not have minDistance/maxDistance/step options

Install through cocoapod will not have minDistance/maxDistance options. But the cocapods indicated the installed version is 1.0.2. It seems that the files from cocoapods are not same as the github. Please advise it. Thanks

Hey,
The latest released version was 1.0.2, which didn't have these additions yet. I've just released version 1.0.3 though so you should be able to do a pod update and get them now :-)
Thanks,
Tom

Thank you so much.

No problem - thanks for using TTRangeSlider :-)


Pro crashes when clicking "Add" button on Coordinate Conversion pane after searching for location

Copy/paste this coordinate into the Coordinate Conversion input box:
39.0392N, 125.7625E
Hit Enter.
I'm zoomed to this location, I see it flash on screen.
Hit Add button.
Pro crashes.

ArcGIS Pro 2.0
Military Tools Add-In 2.0 version
(ArcGIS Pro 2.0, add-in downloaded from Solutions page, version for Pro 2.0 - add-in installer 6/28/2017)

Test this on 9/7/ unable to reproduce this bug.  Closing Issue.


Event color issue

Hello,
I am facing problem in event color change issue on selection of date.
Can you please help me how to change color of event text on date selection?

You can use a customized BaseCellView and override the onDraw method. Check the CalendarActivity2 it uses ExampleCellView2, it should solve your problem.


Provide Adobe Flash Player script template which checks for running browsers before updating

Just out of interest wouldn't that just be a case of adding the blocking programs?

Exactly. I'm just keeping this open until I actually post a script that shows that happening.

Turns out this doesn't work, because we're using pgrep:
RECIPE_NAME=(
    "AdobeFlashPlayer"
)
BLOCKING_APPS=(
    ""
)

However, you can do this by specifying a blocking app that doesn't (and never will) exist:
RECIPE_NAME=(
    "AdobeFlashPlayer"
)
BLOCKING_APPS=(
    "NoBlockingAppNecessaryForAdobeFlashPlayer"
)

I think that's sufficient for now.


[FLINK-4998][yarn] fail if too many task slots are configured

This fails the deployment of the Yarn application if the number of task
slots are configured to be larger than the maximum virtual cores of the
Yarn cluster.

Added a test case to verify the error reporting.


cups-kyocera: init at 1.1203

Things done:

[x] Tested using sandboxing (nix-build --option build-use-chroot true or nix.useChroot on NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

cc @abbradar

I got 403 trying to download src -- I guess there is a problem with the link.

@vanzef I too am getting a 403 trying to download the source.


Remove unwanted files

Description
As mentioned by @gauravdas014 in #178 . I've removed the node_modules, yarn.lock and .DS_Store from the repo.

@priyanshisharma why there are 24 commits associated with this PR?

@priyanshisharma why there are 24 commits associated with this PR?

There are mostly older commits and merge commits from upstream, I think you can squash and merge them as one commit..? 😅

There are mostly older commits and merge commits from upstream, I think you can squash and merge them as one commit..? 😅

There are mostly older commits and merge commits from upstream, I think you can squash and merge them as one commit..?

yeah no issue!

There are mostly older commits and merge commits from upstream, I think you can squash and merge them as one commit..?

yeah no issue!


Add support for Delete Location History

Ready for Review

@lucholaf Please let us know if this can be merged and closed.

@Mohasina can you sync with master so GH let me merge this? thanks

@lucholaf Created new PR with latest master.So closing this PR.
https://github.com/attm2x/m2x-ios/pull/25


Weird data formatting being returned

Hi,
Thanks again for this piece of software.
When executing the following query:
SELECT 1 as foo, 2 as foo

Data returned is:
[
    [ '1\t2' ],
    [ { name: 'foo', type: 'tinyint', comment: '' }, { name: 'foo', type: 'tinyint', comment: '' } ]
]

I'm not sure i quite understand why 1\t2, i was expecting ['1', '2'].
Is this a bug ?
Regards

Probably a bug. Can you fix it? You can easily understand the problem by inserting a console.log here to see what is wrong with the result.


6 Job repository

#7
GIVEN a job entity
WHEN doing a CRUD operation on the JobContext
THEN operation is executed in database

Use Entity Framework here


Fix rendering dashboard when no user is set

When you open up SUI with no username set it derps and throws an exception because it tries to call undefined.split. This fixes that. It's been broken since October (0eb428).
Also just because I had to change this, @ssalinas and @wsorenson please use is for CoffeeScript comparisons, not ==. is translates to the more strict === operator in JS.
@tpetr @benrlodge @gchomatas

CoffeeScript also compiles == into ===. That said, is is used more frequently in the code base so I agree for consistency's sake we stick with is

@benrlodge My bad, you're right :rabbit:


Display Changelog on app start

Is your feature request related to a problem? Please describe.
Many users don't know what's new in recent updates. Although there's already Releases tab on GitHub, and a changelog on Discord, many users aren't aware of that and don't bother checking.
Describe the solution you'd like
Create a changelog tab in the settings menu with the most recent changes (and previous updates).
Additional context
Maybe we could get the GitHub changelog data via some api?

@d2dyno1 There is a link to the latest changelog in the settings page, is there an added benefit of building the release notes into the app?

It's an accessibility feature, quality of life change. Users won't have to go to the Github page. Everything could be done on the Files' level.

...or if making separate tab does not convince you, maybe we could settle somewhere between, and add a popup dialog when starting Files after updating?

When a new version is started for the first time a small ! could be added to the status bar. Upon clicking on it, it would either link to the release page here on GitHub or show most important changes in the app.

After reviewing this proposal, we have decided against implementing this change. Users who are looking for the changelog can find it in the dedicated section in the Microsoft Store and on the GitHub release page.

After reviewing this proposal, we have decided against implementing this change. Users who are looking for the changelog can find it in the dedicated section in the Microsoft Store and on the GitHub release page.

:/

:/

just a link ... super decision thanks .. so i can't be alert that a new version is installed ... with new features .. fix ,..
It is some communication  ; have you ever heard about it ? You know geek don't like it but users  love it !


HmIP-BSM - Changes in Power triggers keypress event

I agree to the following

[X] I have read the documentation
[X] I am aware of the latest release notes
[X] The Backend (CCU/Homegear/...) is working as expected and connected devices are controllable by its own UI.
[X] I am running the latest version of the custom_component (and Home Assistant)

The problem
I have a Zigbee Lamp connected to one of the switch outputs of a BSM. Pressing the button works fine and triggers the keypress event but sadly switching the light on or off and even changing brightness also triggers both keypress events.
Same issue on both BSM Switches i own.
The Problem is not new with 1.40.
What version of HomematicIP (local) has the issue?
1.40
What was the last working version of HomematicIP (local)?
No response
What type of installation are you running?
Home Assistant OS
What type of installation are you running for your homematic backend?
RaspberryMatic Standalone
Which version of your homematic backend are you running?
No response
What hardware are you running for your system?
Proxmox
Which config details do you use

[X] Username and password
[ ] TLS
[ ] callback data (see)

Which interfaces do you use?

[X] Homematic IP
[ ] Homematic (Bidcos-RF)
[ ] Groups (Heating-Group)
[ ] BidCos-Wired (HM-Wired)

Diagnostics information
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response

Please add your automation code.

alias: Neue Automatisierung description: "" use_blueprint:   path: danielperna84/homematicip_local-actions-for-2-button.yaml   input:     remote: 3432ca89db6ad74e49d81c2248a33452     action_top_short:       - type: toggle         device_id: 2dd0877cc1efab1674a258cc8316d53e         entity_id: c1c84530f613df643e0260bccd129c85         domain: light
But it also happens without any automations

This is not reproducable with my HmIP-BSMs or other devices.
keypress is only send when key is pressed.
Do you have any programs running on CCU related to you BSMs?

No nothing, interestingly it also happens when I disable the sending of power values

How do you disable sending power values?
You must have a minimum of one dummy program like described in the docs, otherwise one events will be send by CCU.

I tried both ways with ja dummy programm and the raspberrymatic activation of sending keypress events

Sorry, but I don’t see an issue with this integration.
Try to test it without the blue print (ensure you use the latest) and use device triggers or the events directly, just to double check.
Additionally enable logging for the device channels in the CCU, and check the emitted events.
It‘s also worth asking the RM team for support.

I did try it with other automations and also without any, same thing.
But I just recently changed the behaviour setting to output 1 only and now it doesnt happen anymore.
Obviously it cant be switched anymore like this but keypress is now only send when a key is pressed.
In that case the issue is on the raspberrymatic side right?

In that case the issue is on the raspberrymatic side right?

Looks like.
Please add the yaml code of your automation.

Can this be closed?


Try and fix .NET 7 deployment issues

After downgrading to .NET 7, there are some odd issues with the template where it will return a Cannot find the fallback endpoint specified by route values: { page: /_Host, area: } exception.
This PR is an attempt to fix this issue.

https://github.com/dotnet/aspnetcore/issues/36535


is this project still active?

hi, i m interested in this plugin, is it still active?

It is finished. It works great. Fork it on github and do whatever you wish. Or just install it and use it.


Integrating templates for more complex bots

Wictor, today the bot portion of the generator template is pretty basic.
We've been working on a templatized version of a more complex bot we built. The GitHub project for the template is here: https://github.com/OfficeDev/microsoft-teams-template-bot and an example of it is here: https://teams.microsoft.com/l/chat/0/0?users=28:d75efef8-8a73-4b32-b7ad-9a05a7cff408.
Please take a look at the templates though - while I want there to be a more robust bot implementation, having these blank templates in place may be overkill. On the other hand, they don't take up a lot of space. The Yeoman generator itself wouldn't touch them, they would be, in essence, static files.

Also, check out https://github.com/OfficeDev/microsoft-teams-generator-compose-extension. I would like to fold it into generator-teams but we also need to discuss scope (that example is pretty bare bones).

This task is up for grabs!

We've been working on an enterprise ready version of the node bot template we call bot boiler - composable, testable, injectable etc - the real deal enterprise style boiler plate built on top of the regular bot builder. It might be of interest to have an enterprise option for the generator?

This task is up for grabs!

@wictorwilen @billbliss:
is there still a need for adding a complex bot application option into teams generator? I would be interested in extending of the teams generator.

The current scaffolded bot shows some details and more complexity


KAFKA-7367: Ensure stateless topologies don't require disk access

Streams should not eagerly create the state store directory, since in general topologies may not need state stores.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

I've currently just implemented the test (which fails). Fix pending...
The culprit is this, in the KafkaStreams constructor:
        try {
            stateDirectory = new StateDirectory(config, time);
        } catch (final ProcessorStateException fatal) {
            throw new StreamsException(fatal);
        }

/cc @guozhangwang

No need to keep this PR open, it was only ever to demonstrate an issue.


Rootless podman via systemd with User directive does not work

/kind bug
In anticipation of https://github.com/containers/libpod/pull/6415 getting merged I pulled down @vrothberg branch to start playing around with the new --infra-conmon-pidfile flag and I found that trying to create systemd units with the User directive doesn't work. I want to have a systemd unit that creates and starts a pod and then more systemd units that create services in that pod that run as a rootless user.
I then built https://koji.fedoraproject.org/koji/buildinfo?buildID=1522974 for Fedora 32 and installed that to get the most recent build.
$ podman version
Version:      2.0.0-dev
API Version:  1
Go Version:   go1.14.3
Git Commit:   2c532a92cd9993d93f010c736dd61102d269eece
Built:        Wed Jun 10 19:00:00 2020
OS/Arch:      linux/amd64

Here is my systemd unit file for the pod:
[Unit]
Description=12345 pod service
Wants=network.target
After=network-online.target

[Service]
User=jdoss
Group=jdoss
Environment=PODMAN_SYSTEMD_UNIT=%n
Restart=on-failure
ExecStartPre=-/usr/bin/podman pod create --infra-conmon-pidfile /tmp/12345-pod-conmon.pid --name 12345-pod -p 443:443 -p 80:80
ExecStart=/usr/bin/podman pod start 12345-pod
ExecStop=/usr/bin/podman pod stop -t 10 12345-pod
PIDFile=/tmp/12345-pod-conmon.pid
KillMode=none
Type=forking
SyslogIdentifier=12345-pod

[Install]
WantedBy=multi-user.target default.target

This fails to start the pod correctly:
$ systemctl status 12345-pod.service
● 12345-pod.service - 12345 pod service
     Loaded: loaded (/etc/systemd/system/12345-pod.service; disabled; vendor preset: disabled)
     Active: failed (Result: protocol) since Thu 2020-06-11 10:11:36 CDT; 2min 57s ago
    Process: 272513 ExecStartPre=/usr/bin/podman pod create --infra-conmon-pidfile /tmp/12345-pod-conmon.pid --name 12345-pod -p 443:443 -p 80:80 (code=exited, status=0/SUCCESS)
    Process: 272540 ExecStart=/usr/bin/podman pod start 12345-pod (code=exited, status=0/SUCCESS)
        CPU: 299ms

Jun 11 10:11:35 sts7 systemd[1]: Starting 12345 pod service...
Jun 11 10:11:36 sts7 systemd[1]: 12345-pod.service: New main PID 272597 does not belong to service, and PID file is not owned by root. Refusing.
Jun 11 10:11:36 sts7 systemd[1]: 12345-pod.service: New main PID 272597 does not belong to service, and PID file is not owned by root. Refusing.
Jun 11 10:11:36 sts7 systemd[1]: 12345-pod.service: Failed with result 'protocol'.
Jun 11 10:11:36 sts7 systemd[1]: Failed to start 12345 pod service.

Jun 11 10:11:35 sts7 systemd[1]: Starting 12345 pod service...
Jun 11 10:11:35 sts7 systemd[6314]: Started podman-272525.scope.
Jun 11 10:11:35 sts7 systemd[6314]: Created slice cgroup user-libpod_pod_40db3b8c043fc1cd8d423e83d234c98d2c25d2b37f23211c68dcb54209436b1e.slice.
Jun 11 10:11:35 sts7 12345-pod[272525]: 40db3b8c043fc1cd8d423e83d234c98d2c25d2b37f23211c68dcb54209436b1e
Jun 11 10:11:35 sts7 systemd[6314]: podman-272525.scope: Succeeded.
Jun 11 10:11:35 sts7 systemd[6314]: Started podman-272552.scope.
Jun 11 10:11:35 sts7 systemd[6314]: Started libcrun container.
Jun 11 10:11:36 sts7 12345-pod[272552]: 40db3b8c043fc1cd8d423e83d234c98d2c25d2b37f23211c68dcb54209436b1e
Jun 11 10:11:36 sts7 systemd[1]: 12345-pod.service: New main PID 272597 does not belong to service, and PID file is not owned by root. Refusing.
Jun 11 10:11:36 sts7 systemd[1]: 12345-pod.service: New main PID 272597 does not belong to service, and PID file is not owned by root. Refusing.
Jun 11 10:11:36 sts7 systemd[1]: 12345-pod.service: Failed with result 'protocol'.
Jun 11 10:11:36 sts7 systemd[1]: Failed to start 12345 pod service.

The PID in question is conmon:
$ ps aux |grep 272597
jdoss     272597  0.0  0.0  80492  1996 ?        Ssl  10:11   0:00 /usr/bin/conmon --api-version 1 -c cc06c7b2d28fc5219a8e31609f78b76e19275f48a8334fb1bf669de18afe5240 -u cc06c7b2d28fc5219a8e31609f78b76e19275f48a8334fb1bf669de18afe5240 -r /usr/bin/crun -b /home/jdoss/.local/share/containers/storage/overlay-containers/cc06c7b2d28fc5219a8e31609f78b76e19275f48a8334fb1bf669de18afe5240/userdata -p /run/user/1000/containers/overlay-containers/cc06c7b2d28fc5219a8e31609f78b76e19275f48a8334fb1bf669de18afe5240/userdata/pidfile -n 40db3b8c043f-infra --exit-dir /run/user/1000/libpod/tmp/exits --socket-dir-path /run/user/1000/libpod/tmp/socket -s -l k8s-file:/home/jdoss/.local/share/containers/storage/overlay-containers/cc06c7b2d28fc5219a8e31609f78b76e19275f48a8334fb1bf669de18afe5240/userdata/ctr.log --log-level error --runtime-arg --log-format=json --runtime-arg --log --runtime-arg=/run/user/1000/containers/overlay-containers/cc06c7b2d28fc5219a8e31609f78b76e19275f48a8334fb1bf669de18afe5240/userdata/oci-log --conmon-pidfile /tmp/12345-pod-conmon.pid

After some digging it turns out this is by design for systemd https://access.redhat.com/solutions/4420581
Running this as a user system service does not have this issue:
[Unit]
Description=12345 pod service
Wants=network.target
After=network-online.target

[Service]
Environment=PODMAN_SYSTEMD_UNIT=%n
Restart=on-failure
ExecStartPre=-/usr/bin/podman pod create --infra-conmon-pidfile /tmp/12345-pod-conmon.pid --name 12345-pod -p 443:443 -p 80:80
ExecStart=/usr/bin/podman pod start 12345-pod
ExecStop=/usr/bin/podman pod stop -t 10 12345-pod
PIDFile=/tmp/12345-pod-conmon.pid
KillMode=none
Type=forking
SyslogIdentifier=12345-pod

[Install]
WantedBy=multi-user.target default.target

$ podman ps -a
CONTAINER ID  IMAGE                 COMMAND  CREATED         STATUS             PORTS               NAMES
7fa0a255ade1  k8s.gcr.io/pause:3.2           31 minutes ago  Up 31 minutes ago  <IP_ADDRESS>:80->80/tcp  ee25849f051e-infra
$ podman pod list
POD ID        NAME       STATUS   CREATED         # OF CONTAINERS  INFRA ID
ee25849f051e  12345-pod  Running  31 minutes ago  1                7fa0a255ade1

If I try to create a postgresql container in the same way without a pod, but with a PIDFile it just times out and says it doesn't start the unit. Here is the unit for this test case:
[Unit]
Description=12345 Postgresql Service
Wants=network.target
After=network-online.target

[Service]
User=jdoss
Group=jdoss
Environment=PODMAN_SYSTEMD_UNIT=%n
#Restart=on-failure
ExecStartPre=-/usr/bin/podman kill 12345-postgresql
ExecStartPre=-/usr/bin/podman rm 12345-postgresql
ExecStartPre=-/usr/bin/podman pull postgres:9.6.17
ExecStartPre=-/usr/bin/podman volume create 12345-postgresql
ExecStart=/usr/bin/podman run --rm --name 12345-postgresql -e POSTGRES_PASSWORD=supersecurepassword -e POSTGRES_USER=mycool_user -e POSTGRES_DB=mycooldb --volume 12345-postgresql:/var/lib/postgresql/data:Z --conmon-pidfile=/tmp/postgresql-conmon.pid postgres:9.6.17
ExecStop=/usr/bin/podman stop -t 10 12345-postgresql
PIDFile=/tmp/postgresql-conmon.pid
KillMode=none
Type=forking
SyslogIdentifier=12345-postgresql

[Install]
WantedBy=multi-user.target default.target

Which is weird because when the above unit starts it does write out the PIDFile:
$ ll /tmp/postgresql-conmon.pid
-rw-r--r--. 1 jdoss jdoss 6 Jun 11 14:03 /tmp/postgresql-conmon.pid

and it shows the container as started:
$ podman ps -a
CONTAINER ID  IMAGE                              COMMAND   CREATED         STATUS             PORTS   NAMES
75f45e50668f  docker.io/library/postgres:9.6.17  postgres  44 seconds ago  Up 44 seconds ago          12345-postgresql

but it fails eventually with a time out from systemd.
Jun 11 13:43:57 sts7 systemd[1]: Failed to start 12345 Postgresql Service.
Jun 11 14:03:56 sts7 systemd[1]: Starting 12345 Postgresql Service...
Jun 11 14:05:29 sts7 systemd[1]: 12345-postgresql.service: start operation timed out. Terminating.
Jun 11 14:05:29 sts7 systemd[1]: 12345-postgresql.service: Failed with result 'timeout'.
Jun 11 14:05:29 sts7 systemd[1]: Failed to start 12345 Postgresql Service.

If you downgrade back down to podman 1.9.3 the 12345-postgresql.service still fails to start in the eyes of systemd but it is running when you do a podman ps.
With that all said, is there a way to run a root systemd unit with the User directive set that runs as a non root user that has a PIDFile?
My end use case is that I want to use Podman and Systemd with Fedora CoreOS to deploy services in a pod via Ignition that run via rootless Podman.

Add the -d (detach) option do your ExecStart line and try again.

@goochjj Doh you are right. I set that on my 12345-postgresql.service and it results in the same error as the 12345-pod.service
● 12345-postgresql.service - 12345 Postgresql Service
     Loaded: loaded (/etc/systemd/system/12345-postgresql.service; disabled; vendor preset: disabled)
     Active: failed (Result: protocol) since Thu 2020-06-11 16:17:07 CDT; 12s ago
    Process: 343048 ExecStartPre=/usr/bin/podman kill 12345-postgresql (code=exited, status=0/SUCCESS)
    Process: 343077 ExecStartPre=/usr/bin/podman rm 12345-postgresql (code=exited, status=1/FAILURE)
    Process: 343118 ExecStartPre=/usr/bin/podman pull postgres:9.6.17 (code=exited, status=0/SUCCESS)
    Process: 343151 ExecStartPre=/usr/bin/podman volume create 12345-postgresql (code=exited, status=125)
    Process: 343178 ExecStart=/usr/bin/podman run -d --rm --name 12345-postgresql -e POSTGRES_PASSWORD=supersecurepassword -e POSTGRES_USER=mycool_user -e POSTGRES_DB=mycooldb --volume 12345-postgresql:/var/lib/postgresql/data:Z --conmon-pidfile=/tmp/postgresql-conmon.pid postgres:9.6.17 (code=exited, status=0/SUCCESS)
        CPU: 800ms

Jun 11 16:17:03 sts7 systemd[1]: Starting 12345 Postgresql Service...
Jun 11 16:17:07 sts7 systemd[1]: 12345-postgresql.service: New main PID 343211 does not belong to service, and PID file is not owned by root. Refusing.
Jun 11 16:17:07 sts7 systemd[1]: 12345-postgresql.service: New main PID 343211 does not belong to service, and PID file is not owned by root. Refusing.
Jun 11 16:17:07 sts7 systemd[1]: 12345-postgresql.service: Failed with result 'protocol'.
Jun 11 16:17:07 sts7 systemd[1]: Failed to start 12345 Postgresql Service.

That's...interesting... because I ran your service file (plus the -d) on my photon machine and it worked...
--cgroups no-conmon?

I am on Fedora 32 with cgroups v2 if that makes a difference.
$ rpm -qa |grep conmon
conmon-2.0.17-1.fc32.x86_64
$ cat /etc/redhat-release
Fedora release 32 (Thirty Two)

Funny, it was not having the -d flag on my setup within Fedora CoreOS that was the source of my main problem. Thanks for this @goochjj  It is now working as expected on FCOS now.
I started debugging on my main workstation as I was trying to better understand what was going on but It looks like I found a different issue with cgroups v2 as FCOS has cgroups v1 enabled still.

Thanks for creating the issue! We currently do not support the User and Group fields in a systemd unit. However, the systemd team is investigating to improve on that.
Given we're discussing the issue in https://github.com/containers/libpod/issues/5572 already, I am closing this issue and ask to comment over there.


rte: use role, not clusterrole

There is no strong reason to use a clusterrole{,binding} for RTE,
while using role{,binding} would make the resources used by RTE
almost entirely confined in a NS, thus easier to track and to remove.
No intended change in behaviour.
Signed-off-by: Francesco Romani<EMAIL_ADDRESS>

we actually still need Clusterole{,Binding} fro the scheduling side, so merging this change as-is.


chore: bump go-apiops to v0.1.35

Ref: https://github.com/Kong/go-apiops/pull/186

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 22.43%. Comparing base (aca781a) to head (78bcffb).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1355   +/-   ##
=======================================
  Coverage   22.43%   22.43%
=======================================
  Files          54       54
  Lines        4520     4520
=======================================
  Hits         1014     1014
  Misses       3407     3407
  Partials       99       99

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


bundle not found

I installed bundle-loader from npm and it says it's not found. I've verified the package is in my node_modules dir. I'm installing version 0.5.1.
var PreDashboard = React.createClass({
  mixins: [AsyncReactComponent],
  bundle: require('bundle?lazy!./Dashboard.react.js'),
  preRender: function() {
    return
Loading dashboard...

  }
});

@roycehaynes Please provide more info about your current setup (webpack.config.js etc), did you solve the issue ?

@michael-ciniawsky - This is no longer an issue.


BU_BO_REL causes 'index out of range' error

Unfortunately I'm not very proficient with regards to the dbc format, but I noticed the following issue when trying to generate_c_source form our CAN DB.
The following line causes an 'index out of range' error if the kind of a BA_REL attribute is BU_BO_REL, since the sequence only has 6 elements:
https://github.com/cantools/cantools/blob/92f4c020df296402040eb84139bf7678a2d36f7b/cantools/database/can/formats/dbc.py#L1191
As can be seen from:
https://github.com/cantools/cantools/blob/92f4c020df296402040eb84139bf7678a2d36f7b/cantools/database/can/formats/dbc.py#L309-L311
Can easily be reproduced by adding a sample line, with the above format, to:
https://github.com/cantools/cantools/blob/92f4c020df296402040eb84139bf7678a2d36f7b/tests/files/dbc/attributes_relation.dbc#L61
Issue was introduced with #430.

@malneni Could you please have a look at this? I do not see a discrimination between rel attributes associated with messages vs. with signals in _load_attributes_rel. If this is because it is not implemented, it still should not break in this case. If you do not plan to implement, this still should be fixed and a test case added that ensures this break is gone.
Thanks.
@CodenameReese I think @malneni might have implemented just what he needed in his use case. This break was probably not anticipated. If you want to take a shot at it, be our guest :). Does it break for you without even requiring the rel attribute or do you use rel attributes?

@juleq, I could not create any rel attributes for Messages with tools that I have. I do not know dbc format for that.
I will try to fix the break

I could also create a PR, but I think @malneni is already on it 😉
I threw together a quick sample dbc, I hope this helps with testing:
VERSION ""

NS_ :
	NS_DESC_
	CM_
	BA_DEF_
	BA_
	VAL_
	CAT_DEF_
	CAT_
	FILTER
	BA_DEF_DEF_
	EV_DATA_
	ENVVAR_DATA_
	SGTYPE_
	SGTYPE_VAL_
	BA_DEF_SGTYPE_
	BA_SGTYPE_
	SIG_TYPE_REF_
	VAL_TABLE_
	SIG_GROUP_
	SIG_VALTYPE_
	SIGTYPE_VALTYPE_
	BO_TX_BU_
	BA_DEF_REL_
	BA_REL_
	BA_DEF_DEF_REL_
	BU_SG_REL_
	BU_EV_REL_
	BU_BO_REL_
	SG_MUL_VAL_

BS_:

BU_: ECU1 ECU2

BO_ 1 message_1: 7 ECU1
 SG_ signal_1 : 0|8@1+ (1,0) [0|100] "" ECU2

BA_DEF_REL_ BU_BO_REL_  "MsgProject" ENUM  "A","B","C";
BA_DEF_DEF_REL_ "MsgProject" "A";
BA_REL_ "MsgProject" BU_BO_REL_ ECU1 1 2;
VAL_ 1 signal_1 255 "Invalid" ;

@CodenameReese, Updated code is now merged to fix this issue

@malneni Thank you very much for the quick fix!


Eureka dead instance eviction problem

Hi,
I am trying to find a good configuration for creating a cluster of Eureka nodes.
During the experiment I found a weird problem. An Eureka instance which I closed manually is not removed from the Eureka information that other nodes have.
peer1 (serviceURL points to itself):
spring:
profiles: peer1 # not standalone
eureka:
instance:
hostname: localhost
client:
registerWithEureka: true
fetchRegistry: true
serviceUrl:
defaultZone: http://user:${eureka.password}@localhost:8761/eureka/
peer2 (serviceURL points to peer1):
spring:
profiles: peer2 # not standalone
server:
port: 8762
eureka:
instance:
hostname: localhost
metadataMap:
instanceId: ${vcap.application.instance_id:${spring.application.name}:${spring.application.instance_id:${random.value}}}
client:
registerWithEureka: true
fetchRegistry: true
serviceUrl:
defaultZone: http://user:${eureka.password}@localhost:8761/eureka/
peer3 (serviceURL points to peer1):
spring:
profiles: peer3 # not standalone
server:
port: 8763
eureka:
instance:
hostname: localhost
metadataMap:
instanceId: ${vcap.application.instance_id:${spring.application.name}:${spring.application.instance_id:${random.value}}}
client:
registerWithEureka: true
fetchRegistry: true
serviceUrl:
defaultZone: http://user:${eureka.password}@localhost:8761/eureka/
I closed peer3  manually and after 15 minutes I can still see the instance in info stored by peer1.
Even more, I have a service which at every 5 seconds displays the info it has about Eureka nodes and the node which has isCoordinatingDiscoveryServer==true. Actually peer 3 appears here and it is the coordinatingDiscoveryServer: Discovery server host: localhost:8763.
Note: peer2 and peer3 point to peer1 (serviceUrl) and peer1 points to itself, so no cross reference.

Do you see message about Eureka being in Self Preservation mode ? It stops expiring instances is number of heartbeats drop more than 15% within a minute. Normally would not happen if you have multiple services running/registering with Eureka instances
You can either disable self preservation mode or adjust using eureka.server.renewalPercentThreshold

selfPreservation is disabled

Closed for lack of feedback. Please, reopen if there is something new to add.

I experience a little different issue: one Eureka instance, several clients. Clients who wasn't shut down gracefully are not evicted from registry. Running all stuff in AWS cloud.

Probably caused by the "self preservation" feature of the Eureka server.

hi,
we have same issue on AWS, occasionally we see that there are stale entries in registry even though service is not running for more than hour. @brenuart eureka is configured to not preserve entries. the only thing we could find is this
2016-11-04 07:32:34.470  WARN 7 --- [qtp641905134-91] c.n.eureka.PeerAwareInstanceRegistry     : The self preservation mode is disabled!. Hence allowing the instances to expire.
2016-11-04 07:32:37.471  INFO 7 --- [qtp641905134-99] c.n.eureka.resources.InstanceResource    : Found (Cancel): SERVICE_NAME - SERVICE_ID

and here is what eureka is sending back
<application>
    <name>SERVICE_NAME</name>
    <instance>
        <hostName>...</hostName>
        <app>SERVICE_NAME</app>
        <ipAddr>...</ipAddr>
        <status>UP</status>
        <overriddenstatus>UNKNOWN</overriddenstatus>
        <port enabled="true">...</port>
        <securePort enabled="false">443</securePort>
        <countryId>1</countryId>
        <dataCenterInfo class="com.netflix.appinfo.AmazonInfo">
            <name>Amazon</name>
            <metadata>
                <public-ipv4>...</public-ipv4>
                <accountId>...</accountId>
                <public-hostname>...</public-hostname>
                <instance-id>...</instance-id>
                <local-ipv4>...</local-ipv4>
                <instance-type>...</instance-type>
                <vpc-id>...</vpc-id>
                <ami-id>...</ami-id>
                <mac>...</mac>
                <availability-zone>us-east-1e</availability-zone>
            </metadata>
        </dataCenterInfo>
        <leaseInfo>
            <renewalIntervalInSecs>30</renewalIntervalInSecs>
            <durationInSecs>90</durationInSecs>
            <registrationTimestamp>1477414955327</registrationTimestamp>
            <lastRenewalTimestamp>1478221919325</lastRenewalTimestamp>
            <evictionTimestamp>0</evictionTimestamp>
            <serviceUpTimestamp>1477414955327</serviceUpTimestamp>
        </leaseInfo>
        <metadata class="java.util.Collections$EmptyMap"/>
        <homePageUrl>host_url:40123/</homePageUrl>
        <statusPageUrl>host_url:8080/healthcheck</statusPageUrl>
        <healthCheckUrl>host_url:8080/healthcheck</healthCheckUrl>
        <vipAddress>SERVICE_NAME</vipAddress>
        <isCoordinatingDiscoveryServer>false</isCoordinatingDiscoveryServer>
        <lastUpdatedTimestamp>1477414955327</lastUpdatedTimestamp>
        <lastDirtyTimestamp>1476696409522</lastDirtyTimestamp>
        <actionType>ADDED</actionType>
    </instance>
</application>

it is strange that lastUpdatedTimestamp/lastDirtyTimestamp and lastRenewalTimestamp are really old.
is there something obvious we are missing?

@pawel-kaminski-krk @aivans did you get any solution we are also facing same issue

@vikrantch-hk would this answer your question? https://github.com/Netflix/eureka/wiki/Server-Self-Preservation-Mode . Thanks


DEV: update pydevtool version to propagate exit codes

The pin is not really needed anymore, we just want the latest version.
This change also flushes the GitHub Actions cache, which is keyed on environment.yml.
Closes gh-16476

Let's see if any CI jobs fail before merging, it's possible hidden failures will now show up.

All green now and this fixes broken CI, so in it goes.


FIX use type for JSON output

A quick patch to support the --type switch on JSON output.

Thnx for yet another contribution :+1:

Indeed I'm wondering if would be even better to add the plugin version on the output as well.
{
  "plugins": [
    {
       "plugin": "whatever",
       "version": "x.y.z",
       "count": N,
       "details": [
         {
           "fixed_in": "i.j.k"
...

Something you get already from the command line indeed.


Improvement for k8s.io/docs/concepts/workloads/controllers/cron-jobs/

Does not describe the fields failedJobsHistoryLimit and successfulJobsHistoryLimit, please add a list of all fields the spec can have, preferable with examples of use and format.

/triage accepted
/kind feature

/retitle Mention failedJobsHistoryLimit and successfulJobsHistoryLimit in CronJob concept page
https://k8s.io/docs/concepts/workloads/controllers/cron-jobs/ does link to https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/cron-job-v1/ which includes an explanation of these fields.
/priority backlog
/sig apps

/language en

Hmm, does not make sense to have these fields described by having to follow global doc link at the footer of the document. The exhaustive list of fields should be shown in the main page and for more information clearly linked to a detail page if needed. For starting users this is not clear and I can imagine for somebody not in the known you can only find this through the StackOverflow route. It also now fails to explain the possibilities of the definition as a person not aware of these fields is not informed of them as they would not know to look for them.  Not a great Documentation Experience this way.

This issue is ready for a volunteer to work on it. Would anyone like to help out?

Does not describe the fields failedJobsHistoryLimit and successfulJobsHistoryLimit

Let's add that

Please add a list of all fields the spec can have, preferable with examples of use and format.

This issue is now not about listing all the fields; for that, we already have https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/cron-job-v1/ (and that's why I changed the title of the issue)

There is a brief description of those fields in the document: https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/#jobs-history-limits
@sftim, are you asking for additional details? There isn't a lot more to say about them other than maybe rephrase it so it is more clear?

Rephrasing the page to be more clear would be a welcome improvement.

The exhaustive list of fields should be shown in the main page and for more information clearly linked to a detail page if needed.

Since this was filed, we've changed the page to link to the API reference from the right hand nav. We also have a long standing issue for fact sheets, so work on this issue does not need to add a fact sheet.
A brief tidy-up of the job history limit explanation would be fine to close this issue. @mrgiles if you're happy with the wording as-is, you are welcome to close the issue already.

/assign

Thanks @sftim, see if you like the wording in the PR