Statistics isn't shown

Code of Conduct

[X] I agree to follow this project's Code of Conduct.

Submission validity

[X] This is not a personal support request, that should be posted on discussions community.
[X] I checked current issues and this request isn't a duplicate of an existing issue, opened or closed.

Self troubleshooting

[X] I've read the documentation and made sure to follow it.
[X] I've read the troubleshooting first steps and frequent issues guides.

Version
1.9.2
Description
After clicking Statistics the error message appears, that there is no such page found on the server

Expectation
statistics is shown below the link
Reproduction steps

go to admin panel
click on Statistics right to the URL, I wanted to see statistics
I'm redirected to the error message page, that this page wasn't found

Context
No response

This is almost certainly a server configuration issue, or possibly a plugin conflict.
At the risk of sounding like "that project maintainer", statistics work just fine for me on 1.9.2.

Thanks!
And sorry, will try to reinstall completely - I tried to install themes, may be they caused the problem.
BTW, no theme is working.. :(
Is there some actual theme, supporting 1.9.2?

We don't maintain third-party themes ourselves, obviously. (That's what makes them third-party.)
Knowing what you tried to do could help make YOURLS more robust, if you figure out a definite cause. :)

We don't maintain third-party themes ourselves, obviously. (That's what makes them third-party.)
Knowing what you tried to do could help make YOURLS more robust, if you figure out a definite cause. :)

Just tried to unstall sleeky theme and statistics stopped working

Ah, not the first I've heard of problems caused by Sleeky. Seems to be not-really-maintained these days, which is too bad. I used it on an older YOURLS instance that no longer exists; it was neat.

We don't maintain third-party themes ourselves, obviously. (That's what makes them third-party.)

of course, I understand. that was a question - may be there are some new and actual themes for YOURLS - it's very cool and useful, but not for mobile use.  :(

There's a small list of themes (including Sleeky, hmm) on the Awesome list, but YOURLS 1.x isn't really designed to support theming. The WIP 2.0 branch is a lot better at it, but I couldn't tell you when that's coming.

Actually, I tried all three themes and all of them are not working properly... Air 66 doesn't show the menu at all, Sleeky breaks statistics, Infinity squared is only frontend actually, but the it's Bookmarklet doesn't work at all. And for the last, I don't need to have the public shortener, just the private one. So it's useless for me at all.

There's a small list of themes (including Sleeky, hmm) on the Awesome list, but YOURLS 1.x isn't really designed to support theming and it looks like none of the entries are particularly maintained any more (based on commit activity). The WIP 2.0 branch is a lot better at it, but I couldn't tell you when that's coming.

I see, thanks. So I better will use the pure YOURLS and waiting for the new release. thanks again!

Ah, Is that planned to make the folders for the URLs inside the admin panel?

I encourage you to make use of issue search for further feature questions. (And remember to include closed issues.) https://github.com/YOURLS/YOURLS/issues/3459#issuecomment-1312603515


Option to specify features to use for splitting and for leaf models

Added two additional parameters:

split_features: Indices of features that can be used for splitting. Default all.
linear_features: Indices of features that are used by the linear models in the leaves. Default all except for categorical features

This implements a feature requested in https://github.com/cerlymarco/linear-tree/issues/2
Potential performance improvement: Currently the code still computes bins for all features and not only for those used for splitting.

Hi Jonas,
Thanks for your patience to look into my messy code, I really appreciate your valuable contribution.
At a first glance, it seems ok but I want to test it in detail. In the next months, I plan to make some extensions to the library with other functionalities. So I think, I'll merge your contribution in the next version.
Stay tuned

I agree that this needs additional testing. In fact, it would be great to
add some unit tests to the library that cover the most important use cases.
Looking forward to the next version.
Am Do., 22. Juli 2021 um 10:31 Uhr schrieb Marco Cerliani <
@.***>:

Hi Jonas,
Thanks for your patience to look into my messy code, I really appreciate
your valuable contribution.
At a first glance, it seems ok but I want to test it in detail. In the
next months, I plan to make some extensions to the library with other
functionalities. So I think, I'll merge your contribution in the next
version.
Stay tuned
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cerlymarco/linear-tree/pull/3#issuecomment-884742372,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALXI5FORZCGYNFU4BSNN23TY7JMRANCNFSM5AYUGSBQ
.

I've merged it... Soon I'll release the new version
Thanks


Determine date and time of forking deadline for Mainnet rollout of gemini release v2.x

This issue tracks the determination of the forking deadline and schedule for the Mainnet rollout of Gemini release (currently tagged as https://github.com/fioprotocol/fio/releases/tag/v2.0.0-rc1).
Proposed rollout schedule:

Week of August 10 - Reach out to Exchanges and Wallets to ask about upgrade timing.
Milestone 1 (Friday Aug-14) - Announce release and schedule to FIO community.
Milestone 2 (M1 + 3 weeks = Sep-4) - All Mainnet nodes must be upgraded to gemini
Milestone 3 (M2 + 1 week = Sep-11) - FIP-12 system contract msig approved on mainnet. This enables the calling of addaction/remaction.
Milestone 4 (M3 + 5 days = Sep-16) Mainnet forking transaction: addaction msigs approved for 50-60 fio actions
Milestone 5 (M3 + 1 week = Wed Sep 23 16:00:00 UTC 2020 ) The new actions table needs to be populated with all of the allowed actions in the fio protocol. If Milestone 4 is not fully executed by this date the blockchain will reject all actions that are not in the new whitelist table.

This is a 5 week schedule from announcement to Mainnet activation.
The important steps are Milestones 4 and 5. The real fork is happening with Milestone 4. Though there is a "forking date" in the chain code that is mentioned in Milestone 5, the reality is that if a node has not upgraded by the time the addaction msig is executed in Milestone 4 they will be already forked by the time we get to Step 5.

we should identify the key players list for main net. (do this before we begin)
we should decide what tools or social networking avenues, or blog will be used to communicate amongst the key players (do this before we begin)
we should record the following audit trail for the key players (received notification to upgrade, upgrade performed, notified of impending forking event and time window of forking event (the MSIG for the addiction), notified that forking event has passed (addiction is completed). Then we wait for the final switchover date/time.

I think we should consider to add just a bit more "slop" into the dates, IE add a couple of days to the deadline, 3 days to get the addiction msig seems adequate, but if/when something unexpected happens we will be thankful for a bit more time on this. I would think its safe to add a couple of days to the final switchover (which is hardcoded in the code)...this puts the final switchover mid week during the week ending Sept 11. This looks like a great plan...

unknowns/risks --
necessary time to coordinate the exchanges and wallets.
       -- start this process now.
what happens if/when one or more of the key players decides they cannot continue In the transition?   (unboink/rollback main net, or accept them being forked out)

unknowns/risks --
necessary time to coordinate the exchanges and wallets.
       -- start this process now.
what happens if/when one or more of the key players decides they cannot continue In the transition?   (unboink/rollback main net, or accept them being forked out)

this was discussed offline, DPOS doesn't care who you might be in the scheme of things, we need to socialize the change in the community, then go forward with the plan. anyone that doesn't do this upgrade will fork and that is what it is.

one more idea. do we need marketing involvement in this rollout? not sure if this is necessary, but it might be useful. I am unsure..

Added dates to the schedule above.

Proposed fork date: Wed Sep 23 16:00:00 UTC 2020

Gemini release v2.0 is complete. Closing.


Unclosed file handlers lead to OSError when used in wsgi

I am getting
OSError: [Errno 24] Too many open files

After leaving my pywps server running for a few days. I am running pywps under wsgi and calling it ~1500 times per day.
After investigating, it seems that everytime that pywps calls tempfile.mkstemp an open file handler is left lying around unclosed[1].
According to python's documentation, mkstemp returns a tuple with an already opened file and the path to the file. In pywps we are never using the file handlers (only the file paths) and we never close these open files!
In a wsgi application this becomes a serious problem, because wsgi does some caching of running processes.
When using apache's mod_wsgi, the process is eventually restarted, causing all file descriptors to be closed. However, if your usage happens to be intensive (as seems to be my use case) there is a chance that you'll run out of file handlers to use.
I'll provide a Pull Request for solving this in the coming days.
[1] - To reproduce the problem, and assuming you get pywps running under wsgi, try the following:
# reload apache in order to start fresh
sudo service reload apache2

# extract the pid of the wsgi process
ps aux | grep [w]sgi

# check that there are no tmp* files opened by the wsgi process
sudo lsof -p <wsgi_process_pid> | grep tmp

# now run one of your WPS processes

# recheck if there are any tmp* files opened by the wsgi process
sudo lsof -p <wsgi_process_pid> | grep tmp

# there should now be one more tmp* file still open
# everytime you re-run a WPS process another tmp* file will be opened
# until sometime when apache's mod_wsgi decides to clean its cache

Thanks @ricardogsilva!  FYI your PR is merged in master and backported to branch pywps-3.2.

@gkm4d @ricardogsilva fix applied in 7e053dd78bde964557881cb7ea5db74525044af5


ValueError: No gradients provided for any variable, check your graph for ops that do not support gradients,

I am green in a tensorflow
I do not know where it is wrong
here is a warning
ValueError: No gradients provided for any variable, check your graph for ops that do not support gradients, between variables ["", "
here is my code
import tensorflow as tf
import numpy as np
import pandas as pd
import math
from sklearn import tree
from sklearn.cross_validation import train_test_split
COLUMNS = ["CLD_A","DDI","DFS_A","DFS_B","deg1","deg2","y"]
filename="D:/outputs/train.csv"
file = pd.read_csv(filename, skipinitialspace=True,
skiprows=0, names=COLUMNS)
n_samples = file[['CLD_A','DDI','DFS_A','DFS_B','deg1','deg2']]
n_samples=n_samples.as_matrix()
n_features= file[['y']]
n_features=n_features.as_matrix()
train_X, test_X, train_y, test_y = train_test_split(n_samples, n_features,
test_size = 0.8,random_state=0)
x=tf.placeholder(tf.int32,shape=[None, 6])
y=tf.placeholder(tf.int32,shape=[None, 1])
l1 = tf.layers.dense(x, 10, tf.nn.relu)          # hidden layer
output = tf.layers.dense(l1, 1)
loss = tf.losses.mean_squared_error(y, output)
optimizer = tf.train.GradientDescentOptimizer(learning_rate = 0.01)
train_op = optimizer.minimize(loss)
with tf.Session() as sess:
init=tf.global_variables_initializer()
sess = tf.Session()
sess.run(init)
for i in range(1000):
total_loss = 0
for i in range(len(train_X)):
feed={x:train_X,y:train_y}
sess.run(train_op,feed_dict={x:train_X,y:train_y})
if i%100==0:
print(sess.run(loss, feed ={x:train_X,y:train_y}))

Try asking here instead: https://stackoverflow.com/questions/tagged/tensorflow

This question is better asked on  StackOverflow since it is not a  bug or feature request. There is also a larger community that reads questions there. Thanks!


functions with "Section: " declarations in docstring appear in "Uncategorized forms"

functions with "Section: " declarations in docstring appear in "Uncategorized forms"
here: https://sstanfield.github.io/slsh/

The excess "Uncategorized forms" were being caused by a few issues that crept into sl-sh itself.  I fixed all of them tonight and the docs are fine again.  We might want to have CI fail if docs find any of these in the future- one main problem was a regression in ns-import (was no longer leaving the docstrings intact) so having CI fail early might be good.  Otherwise you can close this unless you had something you think needs doing.


Not getting location updates when gps is turned off

In a foreground service, i'm using FusedLocationProviderClient to request for location updates. I'm using foreground service because, i want location updates even when the app is closed. so far so good. it is working. But the problem is, if the gps is turned off then i'm not getting the onLocationResult() call back. How to handle this problem ?? Before starting the service, location was on and i got a couple of callbacks in onLocationResult() method. After sometime, user turned off the gps, after that i'm not getting the onLocationResult() call back. Any idea how to deal with this problem ??

There 2 possible approach I may recommend:

Check or change your Location request priority settings to use
PRIORITY_BALANCED_POWER_ACCURACY(uses any available service) instead of PRIORITY_HIGH_ACCURACY that replies mostly on GPS according to Google.
E.g.
LocationRequest locReq = LocationRequest.create();  locReq.setPriority(LocationRequest.PRIORITY_BALANCED_POWER_ACCURACY)

Implement a Broadcast Receiver for changes to gps state and make a new location request using another Location Service Provider e.g. Network or Wifi if the GPS is off

There 2 possible approach I may recommend:

Check or change your Location request priority settings to use
PRIORITY_BALANCED_POWER_ACCURACY(uses any available service) instead of PRIORITY_HIGH_ACCURACY that replies mostly on GPS according to Google.
E.g.
LocationRequest locReq = LocationRequest.create();  locReq.setPriority(LocationRequest.PRIORITY_BALANCED_POWER_ACCURACY)
Implement a Broadcast Receiver for changes to gps state and make a new location request using another Location Service Provider e.g. Network or Wifi if the GPS is off

I already implemented both of these approaches. In the second approach, instead of starting new location request, i'm just raising a audio notification to the user to  switch on the GPS.  If i make a new location request using another location service provider, will it automatically turn on the GPS or will it prompt a message to user to TURN ON GPS ??

Other location providers shouldn't prompt user to turn on the GPS and it won't turn the GPS on automatically, runtime permission is required.
It depends on your requirements;

If it is like a tracker then notifying user to turn on the gps is best options
If you don't need precise use location i.e. you only need city-wide location then WiFi or Network providers should do, caveat is less accurate.
Other option is to call 3rd party location api if the gps is off and you still need location updates.

Other location providers shouldn't prompt user to turn on the GPS and it won't turn the GPS on automatically, runtime permission is required.
It depends on your requirements;

If it is like a tracker then notifying user to turn on the gps is best options
If you don't need precise use location i.e. you only need city-wide location then WiFi or Network providers should do, caveat is less accurate.
Other option is to call 3rd party location api if the gps is off and you still need location updates.

Yes, it is a tracker. So I'm notifying the user to turn on the GPS.  Can you give more details about the last option, calling 3rd party location APIs. What 3rd party location APIs are available and what have you used ?

There are lots of options but I have had a quick search for you to kick start your research 😉.
See below for the links.
I tried openweathermap.org api before and was alright.
Most of the 3rd-party location api uses user device's ip address to do the magic so it might not be accurate as well.
https://ipfind.com/
https://www.google.com/amp/s/rapidapi.com/blog/ip-geolocation-api/amp/
Advice:

When the GPS is off, save the last user location locally, preferably use Shared Preference with a relative key e.g. Gps_LastLocation
Compare the newly pulled location from any other providers aside GPS, with last saved location.
If same happy days if not notify user to confirm the new location. It is a lot of work but that's what I will do as a fall back.


Payload URLs are missing the configured cdnURL

Environment

Reproduction

Describe the bug
You're not attaching the cdnURL to the paths you generate for "payloads": https://github.com/nuxt/nuxt/blob/4b6f3e1ba11ee247906a34ea76292bf3a171ed3b/packages/nuxt/src/core/runtime/nitro/renderer.ts#L243
Additional context
Not sure why this setting should only apply to some URLs and not others. If this is by design, feel free to close.
Logs
No response

Just to give some context:
My task in this context was actually to deploy a Nuxt rendered output, as static pages, to S3-based simple website hosting. These pages were error pages, that should be presented at the requested URL if the request resulted in an error. When I served the pages at the given URL, they would always fall into a "404 state", because the current URL wasn't in the routing of the application.
The first I learned, was that another developer used a ClientOnly node in the pages, because they thought it would be the right solution for another problem they faced. It was not the right solution, as we were aiming for fully static pages.
Once I fixed that, I noticed that the entire JS usage dropped to pretty much zero, and that these payloads also didn't seem to contain any really meaningful data.
So I went with the following configuration bits:
  experimental: {
    noScripts: true,
    payloadExtraction: false,
  },

The resulting pages were fully static HTML pages that I could serve from any origin or host. All other links in the document respected the cdnURL already through one mechanism or the other.
Sorry if any of the terminology is off. I'm in unknown territory here 😅

Thoughts @pi0?

I think we can implement once https://github.com/nuxt/nuxt/pull/21641 is merged.

@danielroe any news about implementation? I can help if you want :)


✅ Adds web-app remote file test

Adds a 'url' input field to the web app
Adds a simple node:http test server that can serve exactly one file (with range header support)
Works on small (~100 MB) files but fails on large (GB+) files

Hah it is failing on encrypt, not decrypt, so it isn't the chunker bug. I suspect it is just not throttling the download but IDK it could be a leak somewhere? It is strange that File streams don't trigger it but web streams do. I've had no luck so far, see https://github.com/opentdf/client-web/pull/159


K8SPXC-1237: verify backups and secrets before starting restore

https://jira.percona.com/browse/K8SPXC-1237
DESCRIPTION
Problem:
The operator starts the restore process even if the backup destination doesn't exist or credentials are invalid. It leads to stopping cluster without any progress in restore
Solution:
Before starting the restore, the operator should check if the secrets required by the restore job exist and try to connect to the storage to verify the existence of a backup.
This PR also fixes https://jira.percona.com/browse/K8SPXC-1302.
CHECKLIST
Jira

[x] Is the Jira ticket created and referenced properly?
[x] Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
[x] Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

[ ] Is an E2E test/test case added for the new feature/change?
[x] Are unit tests added where appropriate?
[x] Are OpenShift compare files changed for E2E tests (compare/*-oc.yml)?

Config/Logging/Testability

[ ] Are all needed new/changed options added to default YAML files?
[ ] Are the manifests (crd/bundle) regenerated if needed?
[ ] Did we add proper logging messages for operator actions?
[ ] Did we ensure compatibility with the previous version or cluster upgrade process?
[ ] Does the change support oldest and newest supported PXC version?
[ ] Does the change support oldest and newest supported Kubernetes version?

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
failure

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
failure

haproxy-5-7
failure

haproxy-8-0
passed

ignore-labels-annotations-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failure

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
failure

scheduled-backup-8-0
failure

security-context-8-0
failure

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
failure

upgrade-proxysql-8-0
failure

users-5-7
failure

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1403/commits/90e514bc37935042b772480d340bf627e49ef503
image: perconalab/percona-xtradb-cluster-operator:PR-1403-90e514bc

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
failure

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
failure

haproxy-5-7
passed

haproxy-8-0
passed

ignore-labels-annotations-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failure

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
failure

scheduled-backup-8-0
failure

security-context-8-0
failure

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
failure

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
failure

upgrade-proxysql-8-0
failure

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1403/commits/3d1567abc8cf8a72c106d36d9d76bfee42bcc884
image: perconalab/percona-xtradb-cluster-operator:PR-1403-3d1567ab

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
failure

demand-backup-encrypted-with-tls-8-0
failure

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
failure

ignore-labels-annotations-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failure

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
failure

scheduled-backup-8-0
failure

security-context-8-0
failure

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
failure

upgrade-proxysql-8-0
failure

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1403/commits/0facb75406bab7bd7d9b79664ed3975301f19295
image: perconalab/percona-xtradb-cluster-operator:PR-1403-0facb754

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
failure

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
failure

haproxy-5-7
passed

haproxy-8-0
failure

ignore-labels-annotations-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
failure

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failure

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
failure

scheduled-backup-8-0
failure

security-context-8-0
failure

smart-update1-8-0
failure

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
failure

upgrade-proxysql-8-0
passed

users-5-7
failure

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1403/commits/cf4586f8fd25f8c599e1c28d50e503e3265aab0c
image: perconalab/percona-xtradb-cluster-operator:PR-1403-cf4586f8

Test name
Status

affinity-8-0
skipped

auto-tuning-8-0
skipped

cross-site-8-0
skipped

demand-backup-cloud-8-0
skipped

demand-backup-encrypted-with-tls-8-0
skipped

demand-backup-8-0
skipped

haproxy-5-7
skipped

haproxy-8-0
skipped

ignore-labels-annotations-8-0
skipped

init-deploy-5-7
skipped

init-deploy-8-0
skipped

limits-8-0
skipped

monitoring-2-0-8-0
skipped

one-pod-5-7
skipped

one-pod-8-0
skipped

pitr-8-0
skipped

proxy-protocol-8-0
skipped

proxysql-sidecar-res-limits-8-0
skipped

recreate-8-0
skipped

restore-to-encrypted-cluster-8-0
skipped

scaling-proxysql-8-0
skipped

scaling-8-0
skipped

scheduled-backup-5-7
skipped

scheduled-backup-8-0
skipped

security-context-8-0
skipped

smart-update1-8-0
skipped

smart-update2-8-0
skipped

storage-8-0
skipped

tls-issue-cert-manager-ref-8-0
skipped

tls-issue-cert-manager-8-0
skipped

tls-issue-self-8-0
skipped

upgrade-consistency-8-0
skipped

upgrade-haproxy-8-0
skipped

upgrade-proxysql-8-0
skipped

users-5-7
skipped

users-8-0
skipped

validation-hook-8-0
skipped

We run 0 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1403/commits/1bcb2929152a2a5bed8ab73cabefde8bda3e7dcc
image: perconalab/percona-xtradb-cluster-operator:PR-1403-1bcb2929

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
failure

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
failure

haproxy-5-7
failure

haproxy-8-0
failure

ignore-labels-annotations-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failure

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
failure

scheduled-backup-8-0
failure

security-context-8-0
failure

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
failure

upgrade-haproxy-8-0
failure

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1403/commits/8dde504f2cdcf8d141968895f94bf2010f254963
image: perconalab/percona-xtradb-cluster-operator:PR-1403-8dde504f

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
failure

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
failure

haproxy-8-0
failure

ignore-labels-annotations-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failure

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
failure

scheduled-backup-8-0
failure

security-context-8-0
failure

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
failure

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
failure

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
failure

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1403/commits/795a1398e8c3f08afd49dd42cd8dd8d0b5d6b7dd
image: perconalab/percona-xtradb-cluster-operator:PR-1403-795a1398

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

ignore-labels-annotations-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failure

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
failure

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
failure

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1403/commits/03fc31fe4699de1bf68dca3bd60b3050d2bb6772
image: perconalab/percona-xtradb-cluster-operator:PR-1403-03fc31fe

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
failure

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
failure

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failure

pitr-gap-errors-8-0
failure

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
failure

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
failure

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
failure

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1403/commits/ee56abe65a2b0fa71b5a6b3a4f20020687fa01e0
image: perconalab/percona-xtradb-cluster-operator:PR-1403-ee56abe6

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
failure

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
failure

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failure

pitr-gap-errors-8-0
failure

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
failure

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
failure

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1403/commits/13313c585cd8824fae4cdd5e5557fce4549ddd32
image: perconalab/percona-xtradb-cluster-operator:PR-1403-13313c58

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
failure

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
failure

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failure

pitr-gap-errors-8-0
failure

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
failure

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
failure

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1403/commits/65f523a671096181397566821f5dde7ec234b94b
image: perconalab/percona-xtradb-cluster-operator:PR-1403-65f523a6

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
failure

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
failure

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failure

pitr-gap-errors-8-0
failure

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
failure

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
failure

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1403/commits/705794f6794d39f9e72ef4d424a9cc225281af3f
image: perconalab/percona-xtradb-cluster-operator:PR-1403-705794f6

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
failure

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
failure

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failure

pitr-gap-errors-8-0
failure

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
failure

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
failure

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1403/commits/e601df027aa1f8789d30b5f51a9b3724bf7bd5b3
image: perconalab/percona-xtradb-cluster-operator:PR-1403-e601df02

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
failure

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
failure

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failure

pitr-gap-errors-8-0
failure

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
failure

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
failure

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1403/commits/b3ac1e4247dd221a4933e8c62db7d93d42a9c8c6
image: perconalab/percona-xtradb-cluster-operator:PR-1403-b3ac1e42

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
failure

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failure

pitr-gap-errors-8-0
failure

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
failure

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
failure

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1403/commits/cb6189f644396a883c3fb713c2d7dc06d350f101
image: perconalab/percona-xtradb-cluster-operator:PR-1403-cb6189f6

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
failure

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failure

pitr-gap-errors-8-0
failure

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
failure

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
failure

upgrade-proxysql-8-0
failure

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1403/commits/8a7783605d2c561c816edd9b756175cd66feaf2f
image: perconalab/percona-xtradb-cluster-operator:PR-1403-8a778360

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failure

pitr-gap-errors-8-0
failure

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
failure

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
failure

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1403/commits/1c076cd0ebfce3a78caac2fdd28e14de71a12389
image: perconalab/percona-xtradb-cluster-operator:PR-1403-1c076cd0

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failure

pitr-gap-errors-8-0
failure

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
failure

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
failure

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1403/commits/1c076cd0ebfce3a78caac2fdd28e14de71a12389
image: perconalab/percona-xtradb-cluster-operator:PR-1403-1c076cd0

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

pitr-gap-errors-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
failure

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
failure

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
failure

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1403/commits/e8caad152fb32bd321a2b4674b25981b2d1df0c5
image: perconalab/percona-xtradb-cluster-operator:PR-1403-e8caad15

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
failure

pitr-gap-errors-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1403/commits/8ea66bafceb362d8a85e5612e0c66330d0ceb7a9
image: perconalab/percona-xtradb-cluster-operator:PR-1403-8ea66baf

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

pitr-gap-errors-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1403/commits/8ea66bafceb362d8a85e5612e0c66330d0ceb7a9
image: perconalab/percona-xtradb-cluster-operator:PR-1403-8ea66baf

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

pitr-gap-errors-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1403/commits/604035a53faf155236e6e8fcf4b5918b92ed6d2c
image: perconalab/percona-xtradb-cluster-operator:PR-1403-604035a5

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

pitr-gap-errors-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
failure

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1403/commits/247e149574d2644c4069b1667649a6830dca6180
image: perconalab/percona-xtradb-cluster-operator:PR-1403-247e1495

Test name
Status

affinity-8-0
passed

auto-tuning-8-0
passed

cross-site-8-0
passed

demand-backup-cloud-8-0
passed

demand-backup-encrypted-with-tls-8-0
passed

demand-backup-8-0
passed

haproxy-5-7
passed

haproxy-8-0
passed

init-deploy-5-7
passed

init-deploy-8-0
passed

limits-8-0
passed

monitoring-2-0-8-0
passed

one-pod-5-7
passed

one-pod-8-0
passed

pitr-8-0
passed

pitr-gap-errors-8-0
passed

proxy-protocol-8-0
passed

proxysql-sidecar-res-limits-8-0
passed

recreate-8-0
passed

restore-to-encrypted-cluster-8-0
passed

scaling-proxysql-8-0
passed

scaling-8-0
passed

scheduled-backup-5-7
passed

scheduled-backup-8-0
passed

security-context-8-0
passed

smart-update1-8-0
passed

smart-update2-8-0
passed

storage-8-0
passed

tls-issue-cert-manager-ref-8-0
passed

tls-issue-cert-manager-8-0
passed

tls-issue-self-8-0
passed

upgrade-consistency-8-0
passed

upgrade-haproxy-8-0
passed

upgrade-proxysql-8-0
passed

users-5-7
passed

users-8-0
passed

validation-hook-8-0
passed

We run 37 out of 37

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1403/commits/247e149574d2644c4069b1667649a6830dca6180
image: perconalab/percona-xtradb-cluster-operator:PR-1403-247e1495


Add star to the required fields. #61

I have added the * symbol in every required field of InputFieldsPage

According to this comment: https://github.com/enisn/UraniumUI/issues/226#issuecomment-1458373921
We expect to do it inside the InputField class, so it'll be shipped to all the projects which use UraniumUI.
But this PR adds star only to the demo application. It should be something like this: https://github.com/enisn/UraniumUI/pull/261


Use UPLC in the ledger

This is a wide-ranging PR. Some highlights:

We didn't have Program for UPLC, so I added it.
The prettyprinting for UPLC didn't include the (new) types for constants.
We didn't have a CBOR instance for UPLC.
 I tidied it up a little bit
Using UPLC for golden tests means that we need De Bruijn conversion
for UPLC so we can have stable test output. Fortuantely it's an easy
port. I reorganize the TPLC one so it was easier to share most of it.
We can no longer typecheck validators. We used to do this during tx
validation, and also in the typed tx interface. Now you're on your own
if you submit ill-typed code, but that's the deal we made.

The prettyprinting for UPLC didn't include the (new) types for constants.

Sorry and thanks for fixing!


Running unit tests destroys all menus and menu items

It seems, that the unit tests are removing all menus and menu items during the test run

Yes, unit tests for native menus do that, I'm not 100% sure why yet, but I think that the menu entries in Electron are shared between windows, but in brackets-shell they're per window

Yes, I think that's the case. :-/

Nothing that's not fixable ;)


[CLI] Cannot delete artifact with only one version

Description
When an artifact of a wandb run has only one version, it cannot be deleted successfully (tested with the Python API).
Wandb features
I am using wandb.apis.public.Api to delete artifacts.
How to reproduce

Create a run with an artifact that has only one version. The same holds if a run has multiple artifacts with only one version each.
Run the following code:

import wandb
api = wandb.Api()
runpath = 'YOUR_RUN_PATH'
run = api.run(runpath)
for artifacts in run.logged_artifacts():
	artifacts.delete()

This will raise a wandb.errors.CommError
Environment

OS: Ubuntu Server 18.04 (kernel version 4.15.0-154-generic)
Environment: conda
Python Version: 3.8.11

Hi @magehrig looking into this for you. Could you let me know which version of wandb you're using?

0.12.1


@conda-forge-admin, please add bot automerge

@conda-forge-admin, please add bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/types-toml-feedstock#4.


Add EMR support

CloudFormation does not seem to currently support EMR.

now possible per https://aws.amazon.com/about-aws/whats-new/2016/02/aws-cloudformation-adds-support-for-amazon-vpc-nat-gateway-amazon-ec2-container-registry-and-more/

Addressed in https://github.com/MonsantoCo/cloudformation-template-generator/pull/121

Closed by #121.


[BUG]: Correcting the Repeated Files

Two cart folders are repeated and making the website slow
so I want to fix it

Cart folder is repeated 2 times making the website slow

Hey @codervivek5
please assign this issue to me


What happened:
Images are not displayed. A question mark is displayed instead.
Expected result:
Images are displayed.

What’s the URL of the feed?

http://www.irunfar.com

Appears to have been fixed.


Canvas resizes in an animated manner by default

Hello :)
I noticed that by default, a react-native-skia canvas resizes in an animated way.
This is demonstrated in the video below, using an example I made.
When I do set the canvas size to fixed values, the animated scaling does not happen.
This is shown in the second video.
I think that it would be more logical if a canvas resize is drawn instantly, instead of animated resizing.
It is a nice option to have, though. Maybe this could be a configuration option on the canvas?
Specifically I noticed this 'issue' in our production app.
For this app we use an image header. The Skia canvas in this image header has its width set to the width of the screen, coming from the react-native Dimensions API. It seems to me that sometimes a Skia canvas is already rendered before the definitive screen width is coming through, because sometimes (rarely though) I do see this animated resize happen (scaling out from the left upper corner) in our production app.
Curious what you think about this.
Have a nice day!
https://user-images.githubusercontent.com/48212886/181081398-f7b16bcd-b0cb-4875-973e-b3ed785df829.mov
https://user-images.githubusercontent.com/48212886/181082323-566377c0-b68b-4b46-8af2-49a5c6d86316.mov

#1027 Native Skia Dom

Hi @chrfalch,
Great to hear that a solution to this has been found!
Do you know if this is already included in the latest release (0.1.165)?
When I test that version, I still experience these animated resizing/drawing, but from the left side now, instead of the left upper corner.
Thanks a lot for all of your work on this.
Laurens

Hi @laurens-lamberts - yeah, we thought we'd fixed them, but my test was obviously testing the wrong thing. I see the same as you.

Hey! I believe I'm experiencing the same thing when drawing SVGs within a canvas. Just wondering what the status is with this issue? :)
https://user-images.githubusercontent.com/5165963/213175925-9c0ad43b-e631-4164-80c2-65ab8550c533.mp4

Thanks for reporting this - We will look into this. It is only on iOS, right? I think I know where / what this is...

Yep - this seems to just happen for iOS.
For my particular use case, I've deferred mounting the Canvas until the surrounding onLayout measurements have happened; after which the image fades in. Reduces some of the janky feel.

@laurens-lamberts and @Braden1996 - Please look at the PR I've made and see if it fixes the issues you're having. It is a super simple fix that can be tested directly in the node_modules/@shopify/react-native-skia folder.

Hi @chrfalch, thanks a lot for the fix! Just tested it on my example app, and that works perfectly fine.
CC @Braden1996


Trouble with fonts

I have been having trouble getting fonts to work with xelatex. I realize this isn't quite appropriate for a github issue but I didn't know where else to turn for help!
I've tried installing fonts by putting  collection-fontsrecommended in the texlive.profile and then using something like \usepackage{palatino}, which doesn't work. Basically the \renewcommand\familydefault{\sfdefault} doesn't seem to do anything because I'm still getting serif fonts. I also tried using fontspec, and \setmainfont{} but then I imagine specific font packages must be installed and I wasn't able to do it via tlmgr and placing more entries on the texlive.profile. Any ideas?

Hi @sschloesser do the font's work for you if you compile the PDF on your local machine?

Yes, both on my machine with the full texlive installation or on overleaf, the fonts work as expected, which is why I imagine some files might just be missing from the bare bones installation on heroku.

@sschloesser is this a TTF or LaTeX Font?

for latex font installing the corresponding package should be good enough. Perhaps you'll have to search inside your local (full) tex installation which package installs the font you need
if it's xelatex and a normal TTF font, they can't be installed via tex packages. You have to have them installed on your local system. In our case we have a .fonts directory in our application repo, the fonts there get picked up by heroku/xelatex

Ok so including the TTF font in .fonts and using it via
\usepackage{fontspec} \setmainfont{Arial}
worked! The only thing that is still not working is bold via \textbf{bold text here}. Could that be a deficiency of the TTF file I used?

Problem solved! I wasn't aware that different .ttf files were necessary for each font type. Thanks for the help!


[InputAdornment] Automatically inherit the variant

[x] I have followed (at least) the PR section of the contributing guide.

Closes #12996

I'm not sure why the tests broke, it doesn't seem like it's anything to do with the code 😕


Can't read the text in ContentControl

Hello everybody, I need your help.
I tried to read a docx document by using Python-docx, but all of the text I wanted were in the ContentControl. When I try to print the text of the paragraphe including a ContentControl, error occurs.
For exemple, I try to print the 14th paragraphe, using
print(p[13].text)
then I get an error like:
UnicodeEncodeError: 'gbk' codec can't encode character '\xa0' in position 8: illegal multibyte sequence
So what should I do to get the text in ContentControl?
Thanks a lot for your help!

Hi Goliard, please use StackOverflow (with tag 'python-docx') for user support questions. This issues list is reserved for feature requests and suspected bugs.

No problem. Sorry, I didn't know that rule. Thanks!


Issue debugging node with "serverless-offline" "webpack-serverless" and TypeScript - Unverified breakpoint, Breakpoints set but not yet bound

VSCode Version: 1.21.1
OS Version: macOD 10.12.6

The problem is in the combination of "serverless-framework" working offline and the interactive debugging facilities of VSCode.
I am running "serverless-framework" with the "webpack-serverless" and "serverless-offline" plugins. Node is the runtime environment naturally.
I use TypeScript.
The code is very simple, and works well when run from command line, i.e. I can launch the "serverless-framework" to work offline with the command "serverless offline start" and my Lambda functions are correclty executed.
The Node debugger of VSCode works fine with TypeScript, i.e. if I have a TypeScript function or class, I can set a breakpoint and the Debugger gently stops there showing me all the variables, their values and so on.
When I try though to set breakpoints in serverless functions, than some weird behaviors occur.
Here are the steps I follow

I launch "serverless-framework" offline using the following "launch" configuration
 {
     "type": "node",
     "request": "launch",
     "name": "Debug - 1",
     "program": "/usr/local/bin/serverless",
     "args": [
       "offline",
       "start",
       "--lazy"
     ],
     "env": {
       "NODE_ENV": "development"
     },
     "outFiles": [
         "${workspaceRoot}/.webpack/service/*"
     ],
     "sourceMaps": true,
     "cwd": "${workspaceRoot}",
     "localRoot": "${workspaceRoot}",
     "smartStep": true,
     "protocol": "inspector",
 }

Consider that I have installed "serveless-framework" globally, and therefore the "program" path is like it is.

As soon as I try to set a breakpoint, I see it greyed-out, as you can see from here

The structure of the project is simple - worth noticing that the "handler.ts" is in the root, while the rest of the code in in the "src" folder

If I launch a request to execute one of the functions I have coded, e.g. issuing a get request from browser bar, than the code execution actually stops where the breakpoint was set, even if the breakpoint was originally greyed-out, as you can see from here

and after the execution is continued, the breakpoint remains red as you can see here

Unfortunately though, the context of the execution seems to be lot, i.e. I can not see the variables and their values, as you can see from here

Other relevant configuration files
package.json
{
  "name": "backend-serverless",
  "version": "1.0.0",
  "description": "serverless backend for Picci site",
  "main": "handler.js",
  "scripts": {
    "test": "mocha -r ts-node/register transform/src/**/*.spec.ts src/**/**/*.spec.ts",
    "tsc": "tsc",
    "serverless": "serverless offline start",
    "debug": "export SLS_DEBUG=* && node --inspect-brk=5858 /usr/local/bin/serverless offline start --skipCacheInvalidation"
  },
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "@types/aws-lambda": "0.0.34",
    "@types/chai": "^4.1.2",
    "@types/mocha": "^5.0.0",
    "@types/node": "^9.6.0",
    "chai": "^4.1.2",
    "mocha": "^5.0.5",
    "serverless-offline": "^3.18.0",
    "serverless-webpack": "^5.1.1",
    "ts-loader": "^4.1.0",
    "ts-node": "^5.0.1",
    "typescript": "^2.7.2",
    "webpack": "^4.3.0"
  }
}

tsconfig.json
   {
        "compilerOptions": {
         "target": "es6",
          "module": "commonjs",
          "outDir": "dist",
          "sourceMap": true,
          "allowJs": true,
          "noUnusedLocals": true,
          "noUnusedParameters": true
    },
    "include": [
        "src/**/*.ts", "*.ts", "src/*.ts"
    ],
    "exclude": [
         "node_modules"
    ],
    "typeRoots": [
         "node_modules/@types"
    ],
     "lib": [
         "es2016",
          "dom"
       ]
    }

webpack.config.js
  const path = require('path');
  const slsw = require('serverless-webpack');

  module.exports = {
    devtool: 'source-map',
    entry: slsw.lib.entries,
    resolve: {
      extensions: [
        '.js',
        '.json',
        '.ts',
        '.tsx'
      ]
    },
    output: {
      devtoolModuleFilenameTemplate: '[absolute-resource-path]',
      // devtoolFallbackModuleFilenameTemplate: '[absolute-resource-path]?[hash]',
      libraryTarget: 'commonjs',
      path: path.join(__dirname, '.webpack'),
      filename: '[name].js'
    },
    target: 'node',
    module: {
      rules: [
        {
          test: /\.ts(x?)$/,
          use: [
            {
              loader: 'ts-loader'
            }
          ],
        }
      ]
    }
  };

launch configuration which allows me to debug nicely TypeScript code (i.e. when I use this launch configuration I can set breakpoints on TypeScript code, and they behave as expected, stopping execution when hit and showing all variables)
   {
        "name": "Current TS File",
        "type": "node",
        "request": "launch",
        "args": ["${relativeFile}"],
        "runtimeArgs": ["--nolazy", "-r", "ts-node/register"],
        "sourceMaps": true,
        "cwd": "${workspaceRoot}",
        "protocol": "inspector"
    }

Does this issue occur when all extensions are disabled?: Yes

@auchenberg did you try "serverless" before? I do not really know whether we are supporting this. I suggest that we investigate in order to create a recipe or to better understand what the problems are (and try to fix them).

The issue with the breakpoint starting out gray, then turning red once it's hit, it expected if the code is not actually loaded initially. The breakpoint only turns red once it's bound to a real location in loaded code.
The issue with not seeing the real local variables is strange... Did it stop in the correct location? If you step over the console.log line, does the log show up in the console at the correct step?

@roblourens
Here my answers to your questions

It does not stop necessarily in the right location
First I place the breakpoint on the console.log line

I then execute the function and the debugger stops at the last line

I am not able to step over the console.log function - if I put the breakpoint on the console.log line, the breakpoint is moved to the last line of the method - if I put the breakpoint before the console.log line, then the breakpoint is moved a the beginning of the method and then the "spepover" seems to go randomly around snippets of code which seems to belong to node or webpack.

I have also noted that the callstack reproduced is not correct

I am executing the method hallo1 but in the stacktrace it seems that I am executing the method hallo

Ok, it sounds like there might be some problem with the sourcemaps...

Anything new with this? @EnricoPicci did you find a solution? Thanks!

no
On Wed, Apr 25, 2018 at 4:00 PM, Marvin Li<EMAIL_ADDRESS>wrote:

Anything new with this? @EnricoPicci https://github.com/EnricoPicci did
you find a solution? Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/46913#issuecomment-384297191,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APSjUgRgvOl58Nt2wwiT8dfmX7TbJfTYks5tsIGPgaJpZM4S_8BY
.

@weinand We have an open issue tracking writing a recipe for Serverless in https://github.com/Microsoft/vscode-recipes/issues/24, but I agree. We should do an investigation on what it would take.

Experiencing same issue in code 1.28.2 and Babel.
According to this question this behaviour is a regression introduced in 1.21.1. That seems to be the version reported initially in this issue

Same here. Also, if I unset a breakpoint, it still breaks at that point at random. Looks like some kind of lag.
PS: No TypeScript here, just regular JS.
Version: 1.29.1
Commit: bc24f98b5f70467bc689abf41cc5550ca637088e
Date: 2018-11-15T19:07:43.495Z
Electron: 2.0.12
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64

Did anyone figured it out easily?

One workaround is putting debugger; at the start of the function, then it will stop there and all breakpoint after that will be woken up, and work properly (vscode 1.35)

Sorry that this issue was left behind. If someone has a simple project that reproduces this issue that I can try, I can help investigate. From https://github.com/microsoft/vscode/issues/46913#issuecomment-377467701, it just sounds like the sourcemaps are not correct/do not actually match the source.

Please don't close it. The project from @Enrico is pretty simple


Add partial validation (first pass)

This is a first pass at adding some schema/validation/docs

Thanks! @nfcampos


Failed to parse line protocol

Hey.
I'm trying to configure unpoller with influx cloud. I have downloaded the newest docker image for controller (7.3) and the newest for unpoller. In the bucket, in grafana cloud, I can only see usw_port measurements, no others.
Previously I was running my setup on influx db in AWS, no issues.
Now in the logs I can see:
influxdb2client E! Write error: invalid: failed to parse line protocol: error writing line 2: Unable to insert iox::column_type::tag type into column wan_ip with type iox::column_type::field::string
What can I do to solve it?

Here is configuration taken from influx cloud "to be used with telegraf to connect":
[[outputs.influxdb_v2]]
urls = ["https://eu-central-1-1.aws.cloud2.influxdata.com"]
token = "$INFLUX_TOKEN"
organization = "superorg"
bucket = "telegraf"
The data are being stored in the influx db so I assume configuration is right:

I'm gonna look for more detailed logs.

looks like this is solved?

looks like this is solved?

Actually no. I couldn't get it working and I didn't find anything in the logs so I moved to influx on premise.

yeah I'm not sure this is something I can sustainably support, we use their open source client and if it's incompatible with their cloud offering this might be an issue to file with influx


Add Registry UI

Add Components for viewing Namespace
Add forms for creating and updating Namespaces
Update login page for CIlogin Users

@haoming29 This test failure isn't likely to be my error

@haoming29 This test failure isn't likely to be my error

Nope. That's a flaky test, will re-run it

LGTM after the revision! One last thing to add and we should be good to go.

Can we add some text under "Pending Registration" and "Namespace Registry" clarifying who the namespace listed below belong to? When I login as a regular user it's a bit confusing to see "Pending Registration" and "Origin" and "Cache" as I don't know if this is others' namespace or mine.

The help text can be based on the user role:

Under "Namespace Registry"

Admin users: Namespace registry shows all registered namespaces in the federation. As an admin user, you can check pending namespace registration and review them. Approved registration are listed under "Origin" or "Cache" table. Denied registrations are hidden.
Regular users: Namespace registry shows all registered namespaces in the federation. You can edit your registrations prior to approval. If you want to edit your registration that has been approved, please contact your registry administrator.

Under "Pending Registration"

Admin users: Pending Registration are namespaces waiting for your review and approve or deny. If a cache is in pending status, the director will not use that cache
Regular users: Pending Registration are namespaces waiting for admin to review. Caches with pending status will not be used in the federation until they are approved

@haoming29 I made some tweaks in my changes to reduce the amount of text. It is hard to get people to read text so I tried to add some ui elements to answer your questions and your text suggestions where UI couldn't answer them all.
Sorry about missing the issue you had to fix, I thought I saw a second suggested change for the input form but I looked through a couple times and couldn't find it.

Looks like the only test failure is the client side test that's supposed by fixed by @joereuss12 soon? Will merge ours first.


RigidBodies should collide only the bodies that were updated on after a previous collision

introduced in #682

I think after fixing #704 this doesn't really make any sense anymore.


Assist creating PVC for workspaces

When starting a pipeline or adding a trigger, user should have in advance created a PVC for some of the workspaces the pipelines needs. The extension should assist the user in creating the PVC.

Allow user to create a PVC on the "start pipeline" and "add trigger" wizards by providing storage class, name and size.


[11.0.x] [WFCORE-4878] Upgrade WildFly OpenSSL to 1.0.10.Final

https://issues.redhat.com/browse/WFCORE-4878
master PR: https://github.com/wildfly/wildfly-core/pull/4098

@fjuma thanks


Front-end design for group chat encryption

By reviewing code, I discover several lines are duplicated for a feature, such us Key Generation, even only several lines.
However, it means we need a discussion for UI cooperation so that make every one works perfectly.  I prefer we just talk here.
It is better @irisgyq upload your UI mockup design now.  Just graphs file is OK.

@tonghuix @fallacy321 These are my UI mockup for group chat OTR encryption.

I don't think timer is necessary.
For reference, here is the cryptocat's UI, it shows the status at the room title bar, encrypted or not.

And a chatter info, it shows room's fingerprint and chatter's.


Allow Splunk Sink to reuse HttpClient

The sink currently allows reuse of the HttpMessageHandler
(https://github.com/serilog/serilog-sinks-splunk/blob/dev/src/Serilog.Sinks.Splunk/Sinks/Splunk/EventCollectorSink.cs#L92)
Would it be possible to also allow reuse of the full HttpClient? The EventCollectorClient is a thin implementation of HttpClient and either the sink or the user would be on the hook to handle the authentication header.
The request stems from the usage of the Sink within the execution context of an Azure Function, where best practice includes reuse of the HttpClient.
Currently, I'm seeing occasional SocketExceptions when using the Splunk Sink within an Azure Function that I believe are stemming from the construction of a new HttpClient by the Sink during every Function invocation.

Hi @Christoba,
Thanks for the note. Just wondering what is the lifetime of your overall Serilog logger? The sink (and the underlying HTTP Client) should be related to that life cycle.  I am guessing the logger is initialized every Azure Function lifecycle?
In terms of the handler there is an overload already for HttpMessageHandler here.
HTH, however not sure this is what you are after.

You're getting at the next workaround I was planning to try, and that is reusing the entire logger. The logger is currently constructed on every function invocation, which will end up creating new HttpClient instances. I'll note that its less desirable to persist the logger, as the Splunk-specific configuration is appsettings-driven, so reusing the logger makes it more difficult to make changes to the settings (one would then need to cycle the app service).
I am already using the HttpMessageHandler overload, but reusing the handler has not prevented occurrences of the socket exceptions.

A couple of things that are downsides with reusing the whole Serilog ILogger to work around this issue

We're also using the Function's (MS's) ILogger, so reusing the Serilog Logger wouldn't allow us to log to both Splunk and the MS's log (portal, app insights)
We're unable to configure the logger with invocation specific information (e.g. the function's invocation id) if we're having the persist the entire logger (instead of just the HttpClient).

var logger = new LoggerConfiguration()
                .MinimumLevel.Information()
                .WriteTo.ILogger(log)
                .WriteTo.EventCollector(
                    splunkHost: splunkHost,
                    eventCollectorToken: splunkToken,
                    **host: context.InvocationId.ToString()**,
                    source: source,
                    sourceType: SourceType,
                    index: splunkIndex,
                    messageHandler: client)
                .CreateLogger();

@Christoba when you mention..

We're also using the Function's (MS's) ILogger

Are you using MEL? e.g.

https://github.com/serilog/serilog-extensions-logging
https://www.nuget.org/packages/Microsoft.Extensions.Logging

MEL: yes
With this sink: https://www.nuget.org/packages/Serilog.Sinks.ILogger/

Thanks @Christoba I have not used that sink before, I will have to dig in and research it.

This would be a feature enhancement for high load scenarios. For release 2.x of ASP.NET Core they introduced HttpClientFactory (docs) to mitigate problems concerned with opening of, and tearing down, socket connections as well as draining the number of connections.
The EventCollectorClient could be removed and its functionality for setting authentication header moved to the inner/outer HttpMessageHandler in the chain.

@joacar, that's a good link and I'll keep it in mind when working with httpClient. It seems like you're advocating a similar approach in not explicitly managing the httpClient lifecycle within the sink.
@merbla, I've found stability by persisting (singleton) and reusing the EventCollector ILogger as well as enriching and pushing properties for each function invocation.

Closing as a part of larger Serilog contrib reorg
Checkout https://github.com/serilog/serilog/issues/1627


Automatically tableize the Template URLs, to properly be counterpart …

…to the new Routing's File Serving
The basic idea is that a Template path like:
nova\app\Templates\NiceTheme/

Will become:
/templates/nice_theme/

The actual Routing known how to interpret this URI path and to look in the right path, transforming that path back into CamelCase.

nice!


Create Filter Block

It consists block which will be useful for changing the main view on changing the selection.

Looks like this is done, right?

Yes . It supports for string, numerical, categorical and matrix for now.

OK, then please close the ticket and create more specific ones for missing sub-features or extensions.

See here
https://github.com/Caleydo/mothertable/commit/7c486b8c74e8d4fb37b10aebe1b2d95420ca14c2


Where are the slides from Class 04?

Procurei os slides da aula 04 e não encontrei, alguém poderia atualizar para mim?
I looked for the slides from class 04 and didn't find it, could someone update for me?

Good question! He must have forgotten this part of the project.


Fixes #2

For some reason that I don't understand, this only seems to be a problem if launching
the notebook using a binder from mybinder.org. It seems to work just fine if we use the
Pangeo hub (https://binder.pangeo.io/).

Thanks for fixing this, @biavillasboas!


gym.error.UnregisteredEnv: No registered env with id: flashgames.DuskDrive-v0

[2016-12-05 10:11:34,087] Making new env: flashgames.DuskDrive-v0
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/gym/envs/registration.py", line 106, in spec
return self.env_specs[id]
KeyError: 'flashgames.DuskDrive-v0'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "main.py", line 2, in
import universe # register the universe environments
File "/home/r2d2/tmp/main.py", line 4, in
env = gym.make('flashgames.DuskDrive-v0')
File "/usr/local/lib/python3.5/dist-packages/gym/envs/registration.py", line 130, in make
return registry.make(id)
File "/usr/local/lib/python3.5/dist-packages/gym/envs/registration.py", line 94, in make
spec = self.spec(id)
File "/usr/local/lib/python3.5/dist-packages/gym/envs/registration.py", line 116, in spec
raise error.UnregisteredEnv('No registered env with id: {}'.format(id))
gym.error.UnregisteredEnv: No registered env with id: flashgames.DuskDrive-v0

Have you run "import universe"? You'll need to do that before the make call.
On Monday, December 5, 2016, Ilya Kostrikov<EMAIL_ADDRESS>wrote:

[2016-12-05 10:11:34,087] Making new env: flashgames.DuskDrive-v0
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/gym/envs/registration.py",
line 106, in spec
return self.env_specs[id]
KeyError: 'flashgames.DuskDrive-v0'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "main.py", line 2, in
import universe # register the universe environments
File "/home/r2d2/tmp/main.py", line 4, in
env = gym.make('flashgames.DuskDrive-v0')
File "/usr/local/lib/python3.5/dist-packages/gym/envs/registration.py",
line 130, in make
return registry.make(id)
File "/usr/local/lib/python3.5/dist-packages/gym/envs/registration.py",
line 94, in make
spec = self.spec(id)
File "/usr/local/lib/python3.5/dist-packages/gym/envs/registration.py",
line 116, in spec
raise error.UnregisteredEnv('No registered env with id: {}'.format(id))
gym.error.UnregisteredEnv: No registered env with id:
flashgames.DuskDrive-v0
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/openai/universe/issues/9, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAM7kfYRTD0OjrnMZ9W6UbVyuWZ-QAXPks5rFCnjgaJpZM4LEVpv
.

--
Sent from mobile

Yes, I'm trying to run the example:
import gym
import universe # register the universe environments
env = gym.make('flashgames.DuskDrive-v0')
env.configure(remotes=1) # automatically creates a local docker container
observation_n = env.reset()
while True:
action_n = [[('KeyEvent', 'ArrowUp', True)] for ob in observation_n] # your agent here
observation_n, reward_n, done_n, info = env.step(action_n)
env.render()

Can you run that one line at a time and paste the whole session?
On Monday, December 5, 2016, Ilya Kostrikov<EMAIL_ADDRESS>wrote:

Yes, I'm trying to run the example:
import gym
import universe # register the universe environments
env = gym.make('flashgames.DuskDrive-v0')
env.configure(remotes=1) # automatically creates a local docker container
observation_n = env.reset()
while True:
action_n = [[('KeyEvent', 'ArrowUp', True)] for ob in observation_n] #
your agent here
observation_n, reward_n, done_n, info = env.step(action_n)
env.render()
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/openai/universe/issues/9#issuecomment-264880074, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAM7kRjpIoDf4xkMOTXYruHNecCxzTwhks5rFCqqgaJpZM4LEVpv
.

--
Sent from mobile

import gym
import universe # register the universe environments
[2016-12-05 10:18:02,035] Making new env: flashgames.DuskDrive-v0
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/gym/envs/registration.py", line 106, in spec
return self.env_specs[id]
KeyError: 'flashgames.DuskDrive-v0'

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "/home/r2d2/tmp/universe.py", line 4, in
env = gym.make('flashgames.DuskDrive-v0')
File "/usr/local/lib/python3.5/dist-packages/gym/envs/registration.py", line 130, in make
return registry.make(id)
File "/usr/local/lib/python3.5/dist-packages/gym/envs/registration.py", line 94, in make
spec = self.spec(id)
File "/usr/local/lib/python3.5/dist-packages/gym/envs/registration.py", line 116, in spec
raise error.UnregisteredEnv('No registered env with id: {}'.format(id))
gym.error.UnregisteredEnv: No registered env with id: flashgames.DuskDrive-v0

I don't see the make call in that paste so I feel like it's not showing
everything.
My suspicion is that "import universe" is exceptioning (such as by not
being installed). Can you actually access "universe.envs"?
Assuming that works, can you paste "pip list" and the result from running
"find" in the path correspond to "universe.file"?
On Monday, December 5, 2016, Ilya Kostrikov<EMAIL_ADDRESS>wrote:

import gym
import universe # register the universe environments
[2016-12-05 10:18:02,035] Making new env: flashgames.DuskDrive-v0
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/gym/envs/registration.py",
line 106, in spec
return self.env_specs[id]
KeyError: 'flashgames.DuskDrive-v0'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "/home/r2d2/tmp/universe.py", line 4, in
env = gym.make('flashgames.DuskDrive-v0')
File "/usr/local/lib/python3.5/dist-packages/gym/envs/registration.py",
line 130, in make
return registry.make(id)
File "/usr/local/lib/python3.5/dist-packages/gym/envs/registration.py",
line 94, in make
spec = self.spec(id)
File "/usr/local/lib/python3.5/dist-packages/gym/envs/registration.py",
line 116, in spec
raise error.UnregisteredEnv('No registered env with id: {}'.format(id))
gym.error.UnregisteredEnv: No registered env with id:
flashgames.DuskDrive-v0
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/openai/universe/issues/9#issuecomment-264880707, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAM7kU9xe8rtDnMudDn-KsVBQpDl1dXiks5rFCs4gaJpZM4LEVpv
.

--
Sent from mobile

There was a problem with importing the file. Closing the issue.


Added ZK cleanup thread to Manager for Scan Server nodes

Closes #4559

I started to comment on the loop where the lock data was read in the loop from getChildren with the following:
''' Would it be worth it to wrap this call with another try...catch(Keeper.NO_NODE ex) to allow it to handle the case where the ephemeral lock was removed while in the main getChildren loop?  With no lock node, it could either delete the host:port then - or at least continue processing the other nodes.  As is, it will retry, but handling NO_NODE could  make it more responsive by processing the remaining nodes in the list.

Taking no action and allowing that node to be processed on the next try would be safer.

But, could there be a race condition between the server lock code and this cleaner.  If the server lock creates the host:port node and then writes the lock there will a period where the lock does not exist, but host:port is expected to be there.  What would happen if the cleaner deletes the host:port and then the server lock write is attempted?

It may be possible to use the creation time of the host:port node (ZK stat ctime) and check that it is older than the loop retry period.  This would delay the removal for at least one cleaner cycle.  Or, the service lock code could try to recreate the host:port node.

I did test the code using a small, single node instance with multiple scan servers - the scan server entries were removed on a cluster restart and when killing individual scan server processes as expected.

Another mitigation may be to delay the first run of the cleaners so that initialization and scan server assignments have a better chance to complete before the cleaner runs - that way seeing a lock as it is being built should not occur.

Another mitigation may be to delay the first run of the cleaners so that initialization and scan server assignments have a better chance to complete before the cleaner runs - that way seeing a lock as it is being built should not occur.

The Manager and CompactionCoordinator don't have an initial delay when calling LiveTServerSet.startListeningForTabletServerChanges or CompactionCoordinator.startCompactionCleaner. I could make this change, but if we do, then we should do it for all of them for the same reason.

I started to comment on the loop where the lock data was read in the loop from getChildren with the following:

Would it be worth it to wrap this call with another try...catch(Keeper.NO_NODE ex) to allow it to handle the case where the ephemeral lock was removed while in the main getChildren loop?  With no lock node, it could either delete the host:port then - or at least continue processing the other nodes.  As is, it will retry, but handling NO_NODE could  make it more responsive by processing the remaining nodes in the list.

Taking no action and allowing that node to be processed on the next try would be safer.
But, could there be a race condition between the server lock code and this cleaner. If the server lock creates the host:port node and then writes the lock there will a period where the lock does not exist, but host:port is expected to be there. What would happen if the cleaner deletes the host:port and then the server lock write is attempted?
It may be possible to use the creation time of the host:port node (ZK stat ctime) and check that it is older than the loop retry period. This would delay the removal for at least one cleaner cycle. Or, the service lock code could try to recreate the host:port node.

Are you suggesting wrapping the following line with a try/catch to catch Keeper.NO_NODE?
            byte[] lockData = ServiceLock.getLockData(getContext().getZooCache(), zLockPath, stat);

I don't think that method throws that Exception.

You are correct - it does not throw NO_NODE - I incorrectly assumed that getLockData would echo the ZK exceptions - but it does not,


Test infra bug: you ignore unit test errors!

REFER: https://github.com/nnstreamer/api/pull/26
The following line makes test case errors ignored:
https://github.com/nnstreamer/nntrainer/blob/0037716297a5abc88ed72d9cca458a08566521b4/packaging/run_unittests.sh#L21

:octocat: cibot: Thank you for posting issue #1052. The person in charge will reply soon.


Skip imprinting

This PR skips the imprint step and instead merges the coincident surfaces using the fact that parastell will import the volumes in inside to outside order. (and some cubit geometry queries)
Likely we will want this to be some sort of setting, right now it just completely replaces the imprint/merge commands, maybe another item in the export dictionary would be the best place to put the option to toggle this, open to suggestions.
For reference imprinting a build with 10 layers took about 50 minutes to imprint for me yesterday, this takes about 5 seconds to merge all coincident surfaces in the example script (7 surfaces to merge)

I'm happy to approve this, but wonder if someone who can actively test it should be responsible for merging. (@connoramoreno @FusionSandwich ?)

Made some changes to comments, variable names, line lengths and newlines based on what I read in PEP8, please let me know if I missed anything

Made some changes to comments, variable names, line lengths and newlines based on what I read in PEP8, please let me know if I missed anything

You should look into a PEP8 formatter for your editor that will do this automatically...


.NET Standard support

Thanks for you library!
I like how this can be used in other mapping library. I was thinking to add it as a TileSource in BruTile. If it support .NET Standard it could be used on all the platforms BruTile supports. Looking at the code I would say there is not that much standing in the way. There is a WritableBitmap that could be replaced by other methods to render to bitmap. What is the reason it does not support PCL or .NET Standard right now? Any specific limitations you ran into or did you just not attempt to?

The library uses file io, which is desktop dependent.

I don't think there's any specific core code that is desktop dependent. The file i/o methods are mostly just helper functions (except for loading mbtiles from file, using sqlite). I took the desktop approach because at the time of development, I didn't have the .net standard/core framework 😆

I looked into this but need to do some cleanup first to know what is actually needed. I created a PR to remove the binaries. I also see alot of unused references.

Hi guys.
I've made a Mapbox GL JS port for .Net. Check out my newest project:
https://github.com/AliFlux/MapboxNet/

I wanted to create a pure C# vector map, but it was too complicated and I was juggling a few projects already. So I ended up porting Mapbox GL JS using CefSharp and it works awesome!

Interesting. I've been working on something similar for Azure Maps. The one issue I have with cefsharp is that the winform version works great but you can't display xml elements above it which many will want to do in WPF for things like pop-ups. The WPF version of cefsharp isn't as performant and doesn(t support touch well, but xaml can be overlaid above it. What I'm considering doing is exposing an option where the user chooses if they want to allow xaml to be overlaid and then switch between the different cefsharp versions. Not sure how well the two versions run side by side but will find out soon.

I faced the same issue while developing this library. I initially used Microsoft Toolkit, which is basically a WebView that is based on Edge engine. Halfway through I realized that they have a ton of security restrictions and won't allow their webview to communicate with localhost :/ It was pretty performant though.
We can allow the user to chose whether they want to use an overlaid version (WinForms in WinFormsHost) or pure WPF, but that would require a System.Windows.Forms reference, and it's kinda deal breaker for some people.
MapboxNet WPF version is a bit faster than just running mapbox in CefSharp in WPF. The parameters have been tuned.

I looked at the Microsoft toolkit as well but thought the xaml islands would limit the library to windows 10. Looked at the tuning you did for cefsharp and I've been doing the same. Haven't had any customers mention any issues with system.windows in the past, but could create two seperate libraries with shared code fairly easily so that the choice is made at the package level.
Get Outlook for Androidhttps://aka.ms/ghei36

From: Ali Ashraf<EMAIL_ADDRESS>Sent: Friday, April 26, 2019 7:46:27 PM
To: AliFlux/VectorTileRenderer
Cc: Ricky Brundritt; Comment
Subject: Re: [AliFlux/VectorTileRenderer] .NET Standard support (#2)
I faced the same issue while developing this library. I initially used Microsoft Toolkit, which is basically a WebView that is based on Edge engine. Halfway through I realized that they have a ton of security restrictions and won't allow their webview to communicate with localhost :/ It was pretty performant though.
We can allow the user to chose whether they want to use an overlaid version (WinForms in WinFormsHost) or pure WPF, but that would require a System.Windows.Forms reference, and it's kinda deal breaker for some people.
MapboxNet WPF version is a bit faster than just running mapbox in CefSharp in WPF. The parameters have been tuned.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAliFlux%2FVectorTileRenderer%2Fissues%2F2%23issuecomment-487248410&data=02|01||719d62594ebe48dabf8a08d6caba8bfe|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636919299888791117&sdata=3L5rE3vizxutHx40ckfBaHCY4X%2BuFHiIM1OgYO62N3I%3D&reserved=0, or mute the threadhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABRJCRHDOYNUBOEFANJWMFTPSO5AHANCNFSM4E3DYWJA&data=02|01||719d62594ebe48dabf8a08d6caba8bfe|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636919299888801128&sdata=5WpkzYDzg9iwt%2BXupVBeQBvG7gJY1vylSRH5gzkMZQA%3D&reserved=0.

Some devs don't like references to System.Windows.Forms when they're working with WPF. For that reason I've made two different projects, one for WPF, other for WinForms.
I'm thinking about making a third project as well. A WPF version that uses WinFormsHost for CefSharp control. That way we'll have more control over the binding, since the MapboxNet WinForms version doesn't have dependency properties. There will be an issue of overlay but I guess it can be solved using <Popup/>.

The use of WPF (System.Windows.Media.BitmapSource) does make it Windows-dependant, and therefore non-NetStandard.
There are only a few changes required to make it netstandard, I've done it, see:
https://github.com/ststeiger/VectorTileRenderer

@ststeiger you have done some nice upgrades. Can you send a merge request so that i can test and upgrade this repo

I have a version that is completely not dependent on any Windows specific frameworks. Basically, it uses pure SkiaSharp. I don't know how ready it is for merging, but I made it mainly for my own usage.
The main things I had to do:

remove all the colour stuff - this was tied to WPF. It now uses SKColor for all the colours, with a nod to System.Drawing.Color in a couple of places.
remove all the Bitmap related functions. It now uses byte[] and SkiaSharp's rendering directly to handle PNG loading and generation.
removed any dependency on Point, Rect, Size and Vector - so at the moment we are using my own classes for this, but I'll look at using the Skia ones (though they all use float, soo I guess will lose precision.) I will probably just carry on using my own, but will probably break them out in to a new assembly.
pulled in the HSL routine from ColourSpace, though I think SkiaSharp can handle HSL natively, so I will probably factor that out. I went through a lot of pain getting the colours to render correctly because of the magic numbers needed to create to correct HSL values.
embedded the Clipper in to the code because there was no viable .NetStandard version. I also needed to mess about with it to make it work as the latest version available is not compatible with the released nuget that was originally used (there was no AddPolygon(..) method for example.)
embedded the latest MapBox libs, as there was no version in Nuget that was recent and .NetStandard.
upgraded the codebase to use .Net4.8 for the WPF demo and .NetStandard2.0 for the lib. This also involved me updating all the deps to newer versions, so we are now targeting Mapsui 3.02 and BruTile 4.0.
Broke up large files and removed inlined enums/classes as they are more ugly to work with,

I also made all the nonstandard method naming to be in line with standards (so no Camel case, all is now Pascal case.)  The main library now only depends on SkiaSharp for all drawing.
Next plan:

embed the resources (styles and fonts) so that they do not need to be deployed with the assembly. Hopefully use them directly from the resource, otherwise I guess they will be written to a local directory when the app starts(?) This will make use on Mobile a lot easier as the assembly won't need to put files in to odd places so that the Android/iOS app can locate them, and will not need a user to know about any of that.
make the styles fixed, so that I can create an enum to represent them, but allow for a custom one to be specified. I don't think it needs to be more complicated than that. Most use cases I have needs a regular, dark and light option.
add in a better scheme for caching tiles. I think it will probably be by number - it will cache the last N tiles, and the cache will be like a circular buffer. Not ideal, but unless a user zooms in and out a lot and moves around on the map a massive amount, it should be fine. I think we'd allow the cache size to be set externally anyway.
possibly create an option to generate a cache in an mbtiles database. This would then be used on the desktop to generate raster MBTiles databases for offline use. Our current solution involves setting up an entire database for a PBF from OSM or one of the other providers that slice the data like GeoFabrik, and I think this way will be a lot more pleasant for users to interface to.

Feel free to take a look. I intend to keep my fork up to date with your changes as far as I can. I will also offer you back any changes I make.
https://github.com/memsom/VectorTileRenderer


cloud-init: need update to 22.3.4

Checklist

[x] Checked the nixpkgs master branch

[x] Checked the nixpkgs pull requests

Project name
nix search name: cloud-init

current version: 21.4
desired version: 22.3.4
Notify maintainers

maintainers: @madjar @phile314
Note for maintainers
Please tag this issue in your PR.

would be fixed by https://github.com/NixOS/nixpkgs/pull/193715