support URIs instead of just Paths

@uschi2000

@uschi2000 dropwizard supports URI parsing. added unit test: https://github.com/palantir/http-remoting/pull/52/files#diff-0a17123000e058a85ac57bf2cbb5ef62

Can you also test serialization of this?

When would we ever be serializing it?

There was an issue where someone was serializing it to ship config to worker nodes...see #30

Seems like someone should have written a unit test for THAT issue ;)
Anyway, sure, I'll add it to this commit as well

Well it was verified at the time it was serializable, but since we're going from Path to URI we should be testing :)

will squash after +1

@markelliot ready for review again

lgtm except for losing the emptiness check on the uri

Empty string in config actually becomes "file:///" in the URL parser. As a
consumer of this we can't actually check for empty string
On Wed, Feb 17, 2016 at 9:31 PM, Mark Elliot<EMAIL_ADDRESS>wrote:

lgtm except for losing the emptiness check on the uri
—
Reply to this email directly or view it on GitHub
https://github.com/palantir/http-remoting/pull/52#issuecomment-185549615
.

hm, is there a way to check that if it's a file it actually exists? It'd be nice to maintain some error reporting at the config level.

It's a URI, you can't check for existence

file:/// is invalid, so what if we error if it's equal to URI("")?

any more comments?

one comment, otherwise LGTM


az storage account network-rule add clobbers ipRules with concurrent operations

Describe the bug
It seems that running two or more commands of az storage account network-rule add -n mystorage --ip-address x.x.x.x concurrently will overwrite each other's changes - i.e. it's not actually safely adding to whatever is there. It should probably be using ETags, or at least providing the possibility to use them by providing some sort of --if-match argument.
My Storage Account access logs show that there were two changes 2 seconds apart, the first one added an IP address and the second one immediately overwrote the lastly added IP address with another one.
My use case is running Azure DevOps pipelines, where multiple runs are triggered at the same time and they each run on different agents, needing access to the same Storage Account.
Related command
az storage account network-rule add -n mystorage --ip-address x.x.x.x

Errors

Issue script & Debug output

Expected behavior
Adding IP addresses to Storage Account IP Rules should always add, never replace existing ones.
Environment Summary
azure-cli                         2.63.0
core                              2.63.0
telemetry                          1.1.0
Dependencies:
msal                              1.30.0
azure-mgmt-resource               23.1.1
Python location '/opt/az/bin/python3'
Extensions directory '/home//.azure/cliextensions'
Python (Linux) 3.11.8 (main, Jul 31 2024, 03:39:39) [GCC 11.4.0]
Legal docs and information: aka.ms/AzureCliLegal
Additional context

We are also running into exactly the same issue, running on Github Actions.
11/21/2024, 8:32:37 AM GMT+1
properties.networkAcls.ipRules["<IP_ADDRESS>"]
properties.networkAcls.ipRules["<IP_ADDRESS>"]
11/21/2024, 8:32:35 AM GMT+1
properties.networkAcls.ipRules["<IP_ADDRESS>"]

ip <IP_ADDRESS> is added correctly at 8:32:35, but when the ip <IP_ADDRESS> is being added at 8:32:37, it is resulting in a change, not appending to the existing ruleset:
             {
               "action": "Allow",
-              "value": "<IP_ADDRESS>"
+              "value": "<IP_ADDRESS>"
             }

according to the `Microsoft_Azure_ChangeAnalysis` on the storage account.

We have other workflows that succeeds in appending to the network ruleset.
According to our github action logs, the action ran at the same timestamp for these two actions:

one gh action log
2024-11-21T07:32:30.1490274Z Opening firewall for <IP_ADDRESS>

one gh action log
2024-11-21T07:32:30.2839596Z Opening firewall for <IP_ADDRESS>

### environment
github action execution via docker image mcr.microsoft.com/azure-cli:2.66.0


Notmuch module remove *notmuch-hello* buffer customizations + add some documentation

@hlissner I would like to progress development of this module if no one else has interest. It seems to have been in a WIP state for a while.
What I did here is remove some aesthetic customizations that the doom module currently does on the notmuch-hello buffer. I think these customizations are easy to achieve with user config and I provided documentation to do so. As a user of notmuch with vanilla emacs I've grown very used to landing on the normal notmuch-hello buffer and I think that should be the default when using notmuch in doom as well.
I think I've struck a decent balance here of having unsurprising defaults, but also easy customization for those that want it. Please consider this PR for merge.

@hlissner What can I do to help this and #3933 be merged?

@nackjicholson Sorry for the delay. What's holding this PR back is a) I'm swamped at the moment and b) a number of errors exist between this, #3933, and #4024 that needs correction and I haven't found the time to write a full review or correct them myself. I'll get to it as soon as I can.

@hlissner No problem. Thanks for taking a moment to reply. I'll take a look at #4024 and correct those conflicts when I'm able.

@hlissner I rebased onto an updated develop and the conflicts seemed to be gone now. Good?

Sorry for the tremendously late response! I've made some minor corrections, but was otherwise perfect. Thanks for your help and patience!


real utilzation descheduler

LowNodeRealUtilization
use k8s metrics cient,cache metrics point
chec metrics point group nodes into high and low
only can use cpu/memory

x-ref https://github.com/kubernetes-sigs/descheduler/issues/225
/ok-to-test

/retest

/retest

/retest

/retest

/retest

@niuyueyang1996 Can you continue this job？

@niuyueyang1996 Any update on real node utlization ?

The strategy based on instantaneous resource usage for descheduling is very unwise. Nodes may have instantaneous peaks or may be undervalued. Including the pull request(https://github.com/kubernetes-sigs/descheduler/pull/1087) mentioned by another classmate, I think they are not quite perfect. I have implemented a descheduling strategy based on real loads internally in the company. I am willing to further refine it and contribute it.


fix description of arguments

the help text description of the two arguments --all-features and --no-default-features seem to have been mixed up.

bors r+


BUG: latest Tagify and latest Bootstrap (ie. any version > 5.0.2) has conflict in modals

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
When using Tagify https://yaireo.github.io/tagify/ in a Bootstrap Modal for BS. v5.1.3 and v5.2.3, selection of a tagify item (an event that causes $().on('add')) using a mouseclick, will cause the modal to auto scroll to top of modal.
I've tested using different versions of Bootstrap, and this bug doesn't occur in version 5.0.2, only in versions above this.
This modal scroll-to-top bug doesn't occur with select2 or other input selection, and doesn't occur when 'enter' is used for a typed selection.. it only occurs on a click selection.
Reduced test cases
In this codepen I've set up a long modal (lots of br)
Steps to re-create:

Scroll to the bottom and make a selection for tagify with mouseclick. The modal will scroll to top.
Then change (un 'X') the src/href for v5.0.1 and 'X' out v5.2.3 in the  of the HTML section, and re-do the same test. The modal will NOT scroll to top.

https://codepen.io/gidzr/pen/OJwjMNN
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Chrome
What version of Bootstrap are you using?
v5.0 vs 5.1 and 5.2.. the issues are on 5.1 and 5.2

Closing as not an issue with Bootstrap as far as I can tell. If this can be reduced to Bootstrap itself, we can maybe look into it more. /cc @GeoSot for more ideas though just in case.

Hey Mdo, I've got a response from the creator of Tagify, and confirmed it IS a Bootstrap issue.
https://github.com/yairEO/tagify/issues/1170
"I've analyzed the bug and it's Bootstrap's fault. Tagify's dropdown list is injected to the  element and I think Bootstrap is treating it in a weird way, since a click-outside should close the modal, but it doesn't get closed in this situation (which is easily done since you can know if a mouse click was made on top of a modal, even if the element is not within it in the DOM) and then scrolls to the top."
It does seem to be a legit Bootstrap unintended consequence bug..
Can you please re-open this issue?

@GeoSot Thoughts on this?

It got some time till I was guided to https://github.com/twbs/bootstrap/blob/cbc4e3a4098506315c32346b194e9e1a4d7db091/js/src/util/focustrap.js#L102
Seems that a focus event is triggered out of Modal, so FocusTrap, catches this and re-focus to Modal element
Unfortunately, it is a feature and not a bug :rofl: :laughing:
and this suggestion seems to be the only and the right way to solve the issue https://github.com/yairEO/tagify/issues/1170#issuecomment-1399429774

Hi @GeoSot,
great progress with pinpointing to the source of the "problem"!
Theoretically bootstrap could allow an "off-the-books* way to tell it when should the focus trap work and when should it be ignored, by exposing a global mechanism, for example:
// now I want bootstrap to stop trapping focus:
window.bootstrap.features = {} // initialize this object property globally somewhere inside bootstrap
window.bootstrap.features.focustrap = false;

// ...developer doing some UI stuff

// ...UI stuff are done, so revert things back as they were
window.bootstrap.features.focustrap = true;

I know this is very easy to make but at the same time, a huge thing to implement as this opens the door to an endless discussion about what should be allows in features property and how best to expose things and who knows what else :)

Hey @GeoSot + @mdo .. cool re explanation and approach.. and really appreciate the time to check out this issue.. though not a bug, certainly an unintended downstream effect. The jitter with Tagify/Boot-Modals makes the combo unusable from an experience perspective - but I don't want to forgo either technology. ;P  .. they're both awesome.. :)
For now I'll apply @yairEO's suggestion appendTarget: document.querySelector('.modal-content') and see how that works, as I'm very keen to get back to the latest Bootstrap version (after having wound back to 5.0).
Hopefully getting this on your radar might come in handy later - might affect other libraries in-modal.

Anybody still dealing with this ? When one of the tags is selected in the modal the pages scrolls to the top.
Even with all you guys suggestions, still does not work.
Bootstrap 5.3.2


makedip.py - add sip package argument

add an argument to makedip.py so that it can be used on a sip package, taking the present oe-number as the file name for the proxy instead of the absent aaa accession number.
argument could be called -sip_name
Raelene

Hi Raelene - this is added now, soz for the delay - didn't see this notification at all. I didn't add an argument as it was possible to just make this the default behaviour - use aaa or oe number depending on source.

great, - thanks for that.
R


album selector for ios ?

hello the other version of multi image picker has album selection option but I cant find in this version, is there any option to activate this ?

@kormemis were you able to run the picker on the iOS? I do not see the camera button to start the camera on the iOS but the feature is working fine on Android.

Did you find a solution for this? I can also not select the album on iOS

@priyankpatel22 were you able to solve this issue? Right now I am having the same. I cannot take a photo from iOS, while on android this feature works fine.

@morvagergely did you find a solution? Same problem here. No live camera & album selection on iOS

@morvagergely did you find a solution? Same problem here. No live camera & album selection on iOS

Hi, I ended up using the image_picker package. I didn't find a solution for the desired function, but you can make a simple widget where the user can choose the source (camera or gallery).


[FLINK-31238] [WIP] Use IngestDB to speed up Rocksdb rescaling recovery (rebased)

Rebased and slightly refactored version of #23169.

@rkhachatryan Can you take one more look? I have fixed all problems that I encountered in the original PR and also addressed your comments. Using TestStreamEnvironment.randomizeConfiguration seems a bit problematic because the RocksDB config keys are not visible in that module. We also still need to change to frocksDB version and the notice file once we have the release.

One more thing, we should probably update the UI and show the new flag under Checkpoints / Configuration. But that can be a separate PR.


Cheque mailers

Alexia indicated concerns with the cheque mailer text. This is reasonably urgent, so if you're okay with it please land it today. I couldn't figure out anything by way of testing that would meaningfully capture these changes, tbh.

@offbyone, this has a failing test that isn't That Test.  If that gets fixed, this is approved.

I'm tied up til 5, if you see an easy fix. Otherwise I will.
On Mon, Aug 3, 2020 at 12:14 PM Victoria Garcia<EMAIL_ADDRESS>wrote:

@offbyone https://github.com/offbyone, this has a failing test that
isn't That Test. If that gets fixed, this is approved.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ChicagoWorldcon/wellington/pull/40#issuecomment-668195011,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABMLPNQQRNZXVESNKKOHNDR64EAPANCNFSM4PTNCK6Q
.

--
Chris R.
Not to be taken literally, internally, or seriously.
Twitter: http://twitter.com/offby1


Implement top-level await

Consider implementing top-level await, stage 3: https://github.com/tc39/proposal-top-level-await
I had misgivings about this, but it seems to have picked up traction recently and is already stage 3 so I doubt it's going anywhere, regardless of what I think of it. 😛

I’ve been thinking about doing this for a while; but it would be a little messy and would likely involve internally treating any module containing Top Level Await as an asynchronous generator function.
Considering that my Async Geberator function implementation is still not enabled by default that could be problematic.

Note that top-level await blocks execution of dependent module(s), unlike an async IIFE.  Seems like that might make things tricky, too.

I'll be happy to do this once #6312 has landed will be fairly simple.

@rhuanjl That will be awesome! I'll try to get #6312 merged over the next week.

Further to my comment above I have now written an implementation of this, but it still needs some testing before it's ready to merge and it is based on top of #6312 so I cannot open a PR with it until that is merged.

The fact that WScript.LoadScriptFile() doesn't return a promise complicates this IMO.  I would expect the dynamic import() to still reject its promise (as this is well-defined by spec), but what should happen for the LoadScriptFile call is less clear and strikes me as a host-specific question.

Implementation I've done is here https://github.com/rhuanjl/ChakraCore/tree/TopLevelAwait for anyone interested. I can't open a PR yet due to waiting on 6312 as mentioned above AND needing to set up some tests for it as well.


https://github.com/jhipster/generator-jhipster/issues/6061 Impelment BOM project

Here's the bom without the parent pom.
Regards,

@Tcharl This looks good! I have a few little ideas about this, would you mind if I try to make a PR onto your onlydependencies branch? I think it will be quicker to do it with code than try to explain in an issue :-)

@Tcharl Side question, you wanted to eventually add some maven-release-plugin configuration to jhipster, right? Would that mean that all the artifacts have to be moved into a single repository? Or have you found some way around the limitations of the plugin in that regard?

It seems to me that as long as you configure the scm and site informations on the children poms (the server modules), you don't have to squash them all on a single repo. But I can be wrong on that

I got into a lot of trouble once with this -- but the difference is possibly in that case, we wanted to run maven-release-plugin once to release a whole bunch of modules at the same time.
The problem there was that the plugin wants to do some commits, e.g. to bump the <version> elements, and that doesn't work across git repository boundaries. So we ended up making a single repository with all the modules as (regular) subdirectories.
I think this isn't an issue if the plan is to keep releasing these artifacts more or less independently.

IMO, keeping module in separate repository is synonym to have a separate module lifecycle. Otherwise we would prefer keep them in the same place (as it's easier to manage).


jager missing data

HKube micro-service
pipeline driver
Describe the bug
when executong pipeline the jager chart is missing algorithim data

it should containg algorithms start

tested on:
systemVersion: "v2.1.40",
fullSystemVersion: "v2.1.40-1624865396771",
versions: [
{
project: "api-server",
tag: "v2.1.17",
image: "hkube/api-server"
},

@yehiyam @tamir321
I wonder how this bug resolved by itself, I didn't do anything


CP-SAT solver fails to prove infeasibility

What version of OR-Tools and what language are you using?
Versions: pypi ortools-9.0.9048 and ortools-9.3.10497
Language: Python
Which solver are you using (e.g. CP-SAT, Routing Solver, GLOP, BOP, Gurobi)
CP-SAT
What operating system (Linux, Windows, ...) and version?
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.6 LTS
Release:	18.04
Codename:	bionic
What did you do?
We have upgraded from ortools-9.0.9048 to ortools-9.3.10497 and discovered that the new version fails to prove infeasibility of some of our models.
What did you expect to see
On 9.0, solver behaves as expected: proves infeasibility within a few seconds:
Statistics
  - status          : INFEASIBLE
  - conflicts       : 2
  - branches        : 6751
  - wall time       : 4.776481 s

What did you see instead?
On 9.3, solver fails to prove infeasibility and ultimately returns UNKNOWN status (after reaching time limit):
Statistics
  - status          : UNKNOWN
  - conflicts       : 15319
  - branches        : 143430
  - wall time       : 2512.561640 s

Make sure you include information that can help us debug (full error message, model Proto).
See below for an example model that should allow you reproduce the issue across the 2 versions:

bin: https://www.dropbox.com/s/all9lagqj3c1j6q/model_proto.bin?dl=1
txt: https://www.dropbox.com/s/y1bbwcqzwumjkec/model_proto.txt?dl=1

Extra note
We have also empirically detected a notable degradation in solving performance between 9.0 and 9.3.

can you attach the proto from the 9.3 release (the format has changed in between) ?


message "Started to play with bot!" sending to the bot each hour

can we avoid that?

yes

yes

how

I fixed update new version


Parallax scrolling effect for a website

Using front-end like mainly html,css & javascript I've come up to design a scrolling effect web page.
Here the background content (i.e. an image) is moved at a different speed than the foreground content while scrolling. It looks visually appealing.

@aishwaryas15 under which program you can contribute

@aishwaryas15 under which program you can contribute
I don't get you I guess. It's for a website with some CSS animations & Javascript.

Under which open source program you can contribute

Under which open source program you can contribute

Under DevIncept

Can I work on this issue @Ayush7614 ?

Hi @Ayush7614 I want to contribute in this issue. Can i contribute under hacktoberfest 2021?

Go Ahead @Abhicoder03

Hi @Ayush7614 sir i want to work on this issue can you assign it to me ?


Integration of International Phonetic Alphabet (IPA) in Accent Quick of PowerToys

Description of the new feature / enhancement
I propose the addition of a dedicated section for the International Phonetic Alphabet (IPA) within the Accent Quick feature of PowerToys.
The feature should provide an easily accessible interface for users to quickly select and insert IPA symbols. It should include dynamic tooltips for each symbol to offer contextual information about its meaning and usage.
Scenario when this would be used?
This feature would be beneficial for linguists, phoneticians, and users working with foreign languages. It allows for the swift insertion of phonetic symbols without the need for external references, enhancing productivity and language support.
As a power user dealing with linguistics and foreign languages, having a seamless way to input IPA symbols directly within PowerToys would significantly improve efficiency. It eliminates the need to switch between applications or consult external resources, streamlining the workflow and contributing to a more integrated user experience.
Supporting information
An intuitive user interface for quick selection of IPA symbols.
Tooltip functionality for contextual information on each IPA symbol.
Potential impact on productivity and language-related tasks.
I believe the integration of the International Phonetic Alphabet in Accent Quick would be a valuable addition to PowerToys, catering to the needs of users working with linguistic elements and enhancing the overall versatility of the software.

/dup #25860


x/debug/internal/gocore: allocation headers break viewcore tests

#!watchflakes
post <- pkg == "golang.org/x/debug" && `TestVersions/goroot`

The new allocation headers change modifies how the heap metadata is laid out, which unsurprisingly breaks the x/debug viewcore tests that care about that kind of thing.
Example failure: https://build.golang.org/log/921d95ba40810cde564beec65d12b3714c642e57

Broken as of https://go.dev/cl/538217.

@mknyszek There's a release-blocker label here, but it's in Unreleased milestone meaning it's not blocking any release. Did you mean for this to be a blocker for Go 1.22 (RC 1), or something else?

Deduplicating this with #63359.


Configure Liveness, Readiness and Startup Probes

The failureThreshold in section Configure Probes is missing the threshold value, i.e. 3, which is the default as checked from pod yaml output when not defined in pod definition file.
failureThreshold: After a probe fails failureThreshold times in a row --> failureThreshold: After a probe fails failureThreshold 3 times in a row

Example of pod yaml output

/language en

Default value : 3 can be mentioned in the bracket.

This has to be fixed in the upstream source code. We can, however, mention the default value when articulating the concepts.

/remove-lifecycle rotten

@pinakig22, As above already mentioned there can be any value of failureThreshold in PodSpec, so it would be better to keep mention failureThreshold as it is.

Default value : 3 can be mentioned in the bracket.
It can be mentioned here.

/remove-lifecycle stale


(maint) Convert cert-whitelist test to clojure

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1829/

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1834/

:+1:  will merge once the release is done

@ajroetker updated

@senior Am I ok to merge this in?

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1844/


April 2 accession update

Also changes the notebook so that it can be run in Galaxy as well as locally.

Ah, looks like netlify tries to install things from requirements.txt (which is needed to render the notebooks on https://mybinder.org/v2/gh/mvdbeek/SARS-CoV-2/april2_update?filepath=genomics%2F4-Variation%2Fextended variation analysis.ipynb) and fails.

@mvdbeek Yeah.  It's related to https://github.com/netlify/build-image/issues/141.
I haven't worked with mybinder before, but is there a way to configure the requirements location on that end?  If not, we probably need to just drop it here.

AFAICT there isn't. I'll move it back to the genomics folder, I don't think mybinder is crucial.


product_image_filestore: when updating module it throws error.

Hello,
Great module, my DB dump size changed from 1.2 GB to 340MB.
After module install if we do a database update with
odoo.py -u all  ...
following error happens
File "/opt/odoo/custom/addons/product_image_filestore/product_image_filestore_models.py", line 20, in _auto_init
cr.execute("ALTER TABLE product_template RENAME COLUMN image TO image_old")
File "/opt/odoo/odoo-server/openerp/sql_db.py", line 158, in wrapper
return f(self, *args, **kwargs)
File "/opt/odoo/odoo-server/openerp/sql_db.py", line 234, in execute
res = self._obj.execute(query, params)
ProgrammingError: column "image_old" of relation "product_template" already exists

I guess, image column is restored after updating product module, which leads to error.
@jrial, as a author of that updates could assist on fixing this, please?
Probably, we need to use alternative check before renaming the column.
Current check is:
    cr.execute("select COUNT(*) from information_schema.columns where table_name='product_template' AND column_name='image';")
    res = cr.dictfetchone()
    if res.get('count'):
        _logger.info('Starting conversion for product_template: saving data for further processing.')
        # Rename image column so we don't lose images upon module install
        cr.execute("ALTER TABLE product_template RENAME COLUMN image TO image_old")
        cr.commit()
    else:
        _logger.info('No image field found in product_template; no data to save.')

I no longer work with Odoo, but I'll give it a shot.
First some explanation on how the product_image_filestore auto-upgrade works:

The image column, if present, gets renamed to image_old. This happens in _auto_init, before the new fields are added.
The module installs normally and updates its columns/fields.
The image_old column, if present, is rewritten to the filestore. The field then gets overwritten with null in the DB to free up the space. This happens in _auto_end.
Afterwards, still in _auto_end, the column image_old gets renamed to image_bkp so that subsequent upgrades of this module don't bother with trying to rewrite its contents to the filestore.

From this, I can already guess what went wrong: every time you upgrade everything, you reinstate the "image" column when the "product" module where it's defined gets updated. The timeline is as follows:

The first installation of product_image_filestore removes image, and replaces it with image_bkp.
The -u all reinstates image, which gets renamed to image_old. But when image_old should get renamed to image_bkp, it fails because that column already exists. At that point, image has disappeared, image_old was added, and image_bkp is still there from the previous upgrade.
All upgrades after this will encounter an image_old column, and fail to rename image. This is the error you pasted, but it's not the first error you encountered.

@yelizariev : The code fix: there is no reason to rename image_old to image_bkp if all went well during image conversion. After the for-loop, check if image_old contains data. If it does, rename to _bkp so the data doesn't get lost. But if it doesn't, simply drop image_old instead of renaming it. Needs to be done for both models.
@aaltinisik : The fix for your database: check if there's anything in the image_bkp and image_old columns. If not, simply drop them. And word of advice: "-u all" is a recipe for disaster, although that doesn't excuse my code for breaking, of course. ;)
I could create a pull request if you prefer me to do it, but it'll take a while as I'm currently rather busy.

@jrial : "-u all" is for update and module should cope with that.
I think code that moves pictures from DB to filestore should be seperate and run with a wizard or from cron job and should convert just a limited number of images (to cope with timeout)

I know; I'm just informing you it's a recipe for disaster. Worked with Odoo for 4 years, of which 3.5 at the company itself, and I can no longer count the number of development databases that went broken beyond repair due to weird interactions between modules when updating all.
I'll fix my code because I don't want to contribute to the problem. But I'm advising you it's a better idea to update only the modules that have changed whenever possible.

@jrial thank you for explanation.
Currently, I am focused on 9.0 version, so your help are very welcome

Here you go. Tested on a fresh DB by repeatedly restarting with -u all. Verified that it preserves the state of the images that were altered/dropped before installing the module.
When the upgrade fails, the old columns are preserved with the _bkp suffix in order to preserve the unconverted data. When the upgrade succeeds, these old image columns are simply discarded and won't get in the way during subsequent updates of the product module.

@aaltinisik I hope the issue is resolved for you

will test and report

@aaltinisik : if you still have lingering _old and _bkp fields in your DB, make sure they're empty and toss them out before testing. The fix will prevent similar issues from cropping up in the future, but it won't fix your current DB.
In fact, I should probably add another check in the __auto_begin method to see if there's a _bkp column, and abort the upgrade in such a case. @yelizariev : I'll probably do another PR soon adding this check as well.


[ko] Update outdated files in dev-1.27-ko.1 (M127-M137)

Signed-off-by: jongwooo<EMAIL_ADDRESS>Description
Related Issue: #41631
Updated outdated files in content/en/docs/tasks/administer-cluster/.
11 files to be modified
M127, M128은 이미 변경 사항이 적용되어 있습니다. https://github.com/kubernetes/website/issues/41631#issuecomment-1678902282
그리고 M134는 단순 영문 오탈자 수정입니다.

[x] M127. content/en/docs/tasks/administer-cluster/access-cluster-api.md | 1(+XS) 0(-)
[x] M128. content/en/docs/tasks/administer-cluster/certificates.md | 2(+XS) 2(-)
[x] M129. content/en/docs/tasks/administer-cluster/change-default-storage-class.md | 1(+XS) 0(-)
[x] M130. content/en/docs/tasks/administer-cluster/change-pv-reclaim-policy.md | 1(+XS) 0(-)
[x] M131. content/en/docs/tasks/administer-cluster/cluster-upgrade.md | 2(+XS) 1(-)
[x] M132. content/en/docs/tasks/administer-cluster/coredns.md | 1(+XS) 0(-)
[x] M133. content/en/docs/tasks/administer-cluster/declare-network-policy.md | 1(+XS) 0(-)
[x] M134. content/en/docs/tasks/administer-cluster/dns-custom-nameservers.md | 2(+XS) 1(-)
[x] M135. content/en/docs/tasks/administer-cluster/dns-horizontal-autoscaling.md | 1(+XS) 0(-)
[x] M136. content/en/docs/tasks/administer-cluster/enable-disable-api.md | 2(+XS) 1(-)
[x] M137. content/en/docs/tasks/administer-cluster/extended-resource-node.md | 14(+S) 28(-)

Thanks @yoonian for the review!
/lgtm

/approve


64-bit .NET Core on Antares

As part of our effort to add support for 64-bit runtimes on Antares, we'll need to verify that this works on a private stamp.
The current plan on record deploy only the 64-bit runtime (and not the 64-bit SDK) via rapid update mechanism.

cc @muratg @leecow @davidebbo

cc @BrennanConroy

In 2.1.0-preview1 we now install the runtime/sdk via a Site Extension instead of already having the runtime/sdk already installed on the machine. Is this not how we want to do 64 bit also?

Nothing changes for the previews.
However, this is how we plan to ship rc/rtm (for both 32/64 bit). I only put it in the preview2 milestone so we can validate this scenario during that time frame.

@BrennanConroy, @muratg and I spoke offline.
The current plan is to deploy only a 64-bit runtime (in addition to the 32-bit SDK and runtime that we already deploy). We will not be deploying a 64-bit SDK.
Additionally, 64-bit support for out-of-proc apps is a non-goal.
The scenarios we want to verify are

[ ] Publishing via kudu. (Build with 32-bit SDK and run against a 64-bit runtime)

[ ] Test with an app that has a native dependency

[ ] Ensure in-process 32-bit apps will still work

@jkotalik @davidebbo Any other scenarios you want tested?

Did you mean Ensure out-of-process 32-bit apps will still work? Since that's all we have today.

Also we should ensure that inproc works with both 32 and 64 bit (that it at least starts).

@BrennanConroy @shirhatti This is done?

InProc worked well on x64 and x86, and out-of-process 32 bit apps still work

@shirhatti Anything else you'd like verified? Or good to close?

Good to close 😄


Calibration logic and uncertainties

Changes to do with the GlaMBIE algorithm to combine timeseries as well ass added in uncertainties which were previously ignored.

Added logic to average and calibrate a whole data catalogue of timeseries.
Implemented uncertainties for each step in the GlaMBIE algorithm. Note that there are still some placeholders for steps where the Assessment Algorithm doesn't define the uncertainties yet which will need to be defined with the GlaMBIE consortium.

Thanks very much for the review!!
Requested changes were fairly simple & straight forward.
Hope you're happy with it :)


Feature request: Schematics

Discussed in https://github.com/help-me-mom/ng-mocks/discussions/6399

Originally posted by JsantosDK July 29, 2023
By default angular test are created with schematics that rely on TestBed, like below:
import { ComponentFixture, TestBed } from '@angular/core/testing';

import { FooComponent } from './foo.component';

describe('FooComponent', () => {
  let component: FooComponent;
  let fixture: ComponentFixture<FooComponent>;

  beforeEach(() => {
    TestBed.configureTestingModule({
      imports: [FooComponent]
    });
    fixture = TestBed.createComponent(FooComponent);
    component = fixture.componentInstance;
    fixture.detectChanges();
  });

  it('should create', () => {
    expect(component).toBeTruthy();
  });
});

Howetver, it would be very useful if schematics could be provided by default, such that when a component would be created, the default test setup would be:
import { MockedComponentFixture, MockBuilder, MockRender } from 'ng-mocks';

import { FooComponent } from './foo.component';

describe('FooComponent', () => {
  let component: FooComponent;
  let fixture: MockedComponentFixture<FooComponent>;

  beforeEach(() => {
    return MockBuilder(FooComponent)
  });

  it('should create', () => {
    fixture = MockRender(FooComponent);
    component = fixture.point.componentInstance;
    expect(component).toBeTruthy();
  });
});

This would avoid the need to re-write the test setup on every test and would also reduce the change for minor errors.

Please follow https://github.com/help-me-mom/ng-mocks/issues/6293


Concerns about reiability of GA

We've been observing large fluctuation in benchmark results on essentially empty commits. It's apparently because GitHub Actions runs benches on different machines (come to think of it, it's sensible) with different load score.
It doesn't look like GA should be used for benchmarking to me.

GitHub Actions runs benches on different machines

Yep. In my project I solved this by keying the benchmark with the OS and the CPU:
https://github.com/openfga/openfga/blob/main/.github/workflows/main.yaml#L47-L53


build: add additional library search paths

Alter the search path for libdispatch components when linking
foundation.  This is needed to ensure that BlocksRuntime is found on
Windows.

@swift-ci please test

https://dev.azure.com/compnerd/windows-swift/_build/results?buildId=8373&view=results is a PR test run for Windows with this change.  Hopefully it will repair the X64 build.


chore(deps): update links, dependencies

Synchronize links and docs with the main repo.

ping @skshetry :)


Update metadata for shared representations

As a follow-up to https://github.com/indralab/mira/pull/174 and https://github.com/DARPA-ASKEM/Model-Representations/pull/42, this makes updates to the MIRA export for ASKEM petri nets to put the metadata for annotations into an "annotations" key in the "metadata" dictionary.
This PR also adds the metadata export to the ASKEM regnets. It externalizes the code that does this since it's duplicated in both (and potentially others)

Codecov Report

Merging #178 (a965f11) into main (20033d7) will increase coverage by 0.00%.
The diff coverage is 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##             main     #178   +/-   ##
=======================================
  Coverage   76.25%   76.26%
=======================================
  Files          63       64    +1
  Lines        4928     4930    +2
=======================================
+ Hits         3758     3760    +2
  Misses       1170     1170

Impacted Files
Coverage Δ

mira/modeling/askenet/petrinet.py
96.64% <100.00%> (-0.05%)
:arrow_down:

mira/modeling/askenet/utils.py
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[oc8.1] Web interface does not respond after activating  storagecharts2 app

Description:
After activating the storagecharts2 in ownCloud 8.1 the login over web-interface does not work anymore.
I could login over sync-client, android app, and one_not app.
I wanted to disable the app over occ, but the occ does not respond at all for any command:
root@snoopy:/var/www/html/owncloud# sudo -u www-data php occ
root@snoopy:/var/www/html/owncloud#
Steps to reproduce

activate the storagechart app
login from another client: The page isn't redirecting properly
try to disable app. over occ -> Doesn't work anymore

Workaround: Remove the storagecharts2 directory and then works!
Expected behaviour
Can login after I activate the app over the web-server
Actual behaviour
Tell us what happens instead
Server configuration
Operating system:
Ubuntu 14.04.2 LTS \n \l
Web server:
Server version: Apache/2.4.7 (Ubuntu)
Server built:   Mar 10 2015 13:05:59
Database:
mysql  Ver 15.1 Distrib 5.5.44-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2
Connection id:          98563
Current database:
Current user:           root@localhost
SSL:                    Not in use
Current pager:          stdout
Using outfile:          ''
Using delimiter:        ;
Server:                 MariaDB
Server version:         5.5.44-MariaDB-1ubuntu<IP_ADDRESS> (Ubuntu)
Protocol version:       10
Connection:             Localhost via UNIX socket
Server characterset:    latin1
Db     characterset:    latin1
Client characterset:    utf8
Conn.  characterset:    utf8
UNIX socket:            /var/run/mysqld/mysqld.sock
Uptime:                 --------------
PHP version:
PHP 5.5.9-1ubuntu4.11 (cli) (built: Jul  2 2015 15:23:08)
Copyright (c) 1997-2014 The PHP Group
Zend Engine v2.5.0, Copyright (c) 1998-2014 Zend Technologies
with Zend OPcache v7.0.3, Copyright (c) 1999-2014, by Zend Technologies
ownCloud version: (see ownCloud admin page)
8.1 Community Edition
Updated from an older ownCloud or fresh install:
Fresh install
List of activated apps:
Enabled:
 - activity: 2.0.1
 - calendar: 0.7.2
 - files: 1.1.9
 - files_external: 0.2.3
 - files_locking:
 - files_mv: 0.8.1a
 - files_sharing: 0.6.2
 - files_texteditor: 0.4
 - files_trashbin: 0.6.3
 - files_versions: 1.0.6
 - firstrunwizard: 1.1
 - provisioning_api: 0.2
 - registration: 0.0.3
 - templateeditor: 0.1
 - updater: 0.6
 - bookmarks
 - contacts
 - delete_confirmation
 - direct_menu
 - external
 - files_antivirus
 - files_pdfviewer
 - ownnote
 - sharelinks
 - tasks

The content of config/config.php:
$CONFIG = array (
  'instanceid' => 'xxxxx',
  'passwordsalt' => 'xxxxx',
  'secret' => 'xxxxxx',
  'trusted_domains' =>
  array (
    0 => 'xxxxx',
    1 => 'xxxxx',
  ),
  'datadirectory' => '/mnt/owncloud/data',
  'dbtype' => 'mysql',
  'version' => '<IP_ADDRESS>',
  'dbname' => 'ocxxxxxx',
  'dbhost' => '<IP_ADDRESS>',
  'dbtableprefix' => 'oc_',
  'dbuser' => 'xxxxx',
  'dbpassword' => 'xxxxxx',
  'logtimezone' => 'UTC',
  'installed' => true,
  'mail_smtpmode' => 'smtp',
  'mail_from_address' => 'xxxxxx',
  'mail_domain' => 'xxxxxx',
  'mail_smtpsecure' => 'tls',
  'mail_smtpauth' => 1,
  'mail_smtpauthtype' => 'LOGIN',
  'mail_smtphost' => 'xxxxxx',
  'mail_smtpport' => '25',
  'mail_smtpname' => 'xxxxxxx',
  'mail_smtppassword' => 'xxxxxx',
);

Are you using external storage, if yes which one: local/smb/sftp/...
NFS = '/mnt/owncloud/data'
Are you using encryption: yes/no
No
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
No
Logs
Web server error log
No visible errors in access.log or error.log
ownCloud log (data/owncloud.log)
This logs is when I was logged in and activated the app, After I try to login and there is no info about the app.
{"reqId":"Q7JiRsG+ssfjMx0gI6qw","remoteAddr":"IP.NUMMER","app":"PHP","message":"Undefined index: s at \/var\/www\/html\/owncloud\/apps\/storagecharts2\/ajax\/data.php#30","level":3,"time":"2015-07-30T09:50:02+00:00"}
{"reqId":"MJXmxZm4zZxjB+5XiZmk","remoteAddr":"IP.NUMMER","app":"PHP","message":"Undefined index: s at \/var\/www\/html\/owncloud\/apps\/storagecharts2\/ajax\/data.php#30","level":3,"time":"2015-07-30T09:51:09+00:00"}
{"reqId":"ASmUh1UYxYZCbUMujf+u","remoteAddr":"IP.NUMMER","app":"PHP","message":"Undefined index: s at \/var\/www\/html\/owncloud\/apps\/storagecharts2\/ajax\/data.php#30","level":3,"time":"2015-07-30T11:22:19+00:00"}
{"reqId":"\/MMgtkCcEnkqbr4hF0jk","remoteAddr":"IP.NUMMER","app":"PHP","message":"Undefined index: s at \/var\/www\/html\/owncloud\/apps\/storagecharts2\/ajax\/data.php#30","level":3,"time":"2015-07-30T16:14:04+00:00"}

thanks for the info provided.. will be very helpfull, there's a index problem in the storagehcarts2 that affect the ox 8.0.X release...

@mckaygerhard this release is the 8.1.0, should I test it from the master?

yeah, please try and report feedback! BUT REMEMBER, u'r log said that seem the problem are the index .. but only if the problem are that i expected will be solved.. but if u'r log contains something more that u not paste here.. i think will be still in trouble!

@mckaygerhard I test again and I come back with new logs if the  problem happens again :smile: Thanks a lot.

due u response, i assume resolved and close this issue. Please reopens if something related happened again.

Hello, I still have the same problem on oc 8.1, even after using the last storagecharts2 github files:

occ command does not display anything
the login page loops while trying to fetch index.php

The error appears on a fresh install or after migrating from oc 8.0 to 8.1 (it worked on 8.0).

hello @Worst45 i ask to you to confirm: the oc give to u a redirection loop? please confirm quickly. seems related to the 351 redirection loop bug

Yes, I confirm it loops if we try to access login page
tail -f /var/log/apache2/access.log
<IP_ADDRESS> - - [25/Aug/2015:15:37:27 +0200] "GET /drive/index.php HTTP/1.1" 302 -/- (-%)
<IP_ADDRESS> - - [25/Aug/2015:15:37:27 +0200] "GET /drive/index.php HTTP/1.1" 302 -/- (-%)
...
<IP_ADDRESS> - - [25/Aug/2015:15:37:27 +0200] "GET /drive/index.php HTTP/1.1" 302 -/- (-%)
<IP_ADDRESS> - - [25/Aug/2015:15:37:27 +0200] "GET /drive/index.php HTTP/1.1" 302 -/- (-%)
(More than 20 times)

please, u are talking about another issue, please refers to issue 351 (i dont put the "#" before the number to dont link here)

can you please retry the latest nightly build?
https://martinreinhardt-online.de/jenkins/job/OwnCloud_nightly/

I'm affraid it is not better... I took the storagecharts2_v2.6.2_build436.zip, and have still the same errors: occ empty, and http 302 loop on fetching index page.
Just before this 302 loop, I had the update page indicating that storagecharts2 was being updated. Just after the process, it redirect to index page, and then hangs.

@hypery2k the function in thisproblem are private in OC api, so i think must change between oc 8.0.X and 8.1.X, see #351 please

@hypery2k  I found when the server crash..
1.- Enable the app
2.- Select: "Enable only for specific groups" and just add the admins.
3.- Logout and and try to log from another session

hi @cdamken do u have the solution? the oc-apps are not mantained any more, so until oc 7.X works, oc 8.X does not supported officially too many changes in oc api to track to a simple man...
if u have dissagree with this, rec laim to oc entrerprices that changes everyting in each version or better collaborate with working code solution to the problems


https://eru.sh/docs/ is 404

@halk947 hi...yep....no docs under this url, you can try https://book.eru.sh/ instead.

@halk947 hi...yep....no docs under this url, you can try https://book.eru.sh/ instead.

It's url on  this page

@halk947 hi...yep....no docs under this url, you can try https://book.eru.sh/ instead.

It's url on this page

Oh yes, already modify it now lol, thanks.


Support for listening on the same port on two different sockets with different IP addresses

I think we currently don't support that case, because we Identify the random local port by the requested port, we can only remember one local port per requested port.
So if an app starts two threads, each of them listening on the same port on a different IP address, I think we don't support it. I think neither the agent nor the layer would differentiate between connections on different addresses, and we would just send everything just to one of those sockets (before https://github.com/metalbear-co/mirrord/commit/4d0490ac74833e8d0bb7b9ffce0c52a087705a54 to the first, after that to the second socket to listen).
I don't know if it's an actual use-case for anybody, but I think it's technically valid.

I actually thought we solved it with #1123


Add unit and integration tests

Ideally we have unit tests and integration tests to validate functionality works. For integration tests, we could likely provide a Snowflake environment via GitHub Actions to be used for testing end to end

Have our first test! https://github.com/Snowflake-Labs/snowcli/tree/main/tests
Leaving this open for now to track adding a few more


var authenticationContext = AuthFlow.InitAuthentication(appCredentials) error

When my code hits
            var appCredentials = new TwitterCredentials(ConsumerKey, ConsumerSecret);             var authenticationContext = AuthFlow.InitAuthentication(appCredentials);
I'm getting an exception:

System.FormatException occurred
HResult=0x80131537
Message=String was not recognized as a valid Boolean.
Source=
StackTrace:
at System.Boolean.Parse(String value)
at Tweetinvi.Credentials.WebTokenFactory.InitAuthenticationProcess(IConsumerCredentials appCredentials, String callbackURL, String credsIdentifier)
at Tweetinvi.AuthFlow.InitAuthentication(IConsumerCredentials appCredentials, String callbackURL)
at MSDevListManager.MainPage.d__6.MoveNext() in C:\Users\jayde\Source\Repos\MSDevListManager\MSDevListManager\MainPage.xaml.cs:line 82

I'd really just love a tip. I'm not even sure where precisely to start.

Hi @jaydeflix,
This appears to be because of a bool.Parse(...) call as opposed to a bool.TryParse(...) inside of Tweetinvi. It seems to indicate the authentication failed.
@linvi if you're taking contributions, happy to pick this up.

@ChrizC Yay and Boo and Yay. Or some combination. Hurm. That would suggest my ConsumerKey/Secret isn't working right, yeah? I'm just trying to follow https://github.com/linvi/tweetinvi/wiki/Authentication.

fires up Fiddler to figure out what's being sent
starts app
no error.
..... Rargh.

Thanks for reporting the bug, I will take a look as soon as possible.
Cheers,
Linvi

Hello there,
The fix will be available in 2.1. I have not been able to reproduce it myself but the fix is there anyway ;)
Thank you for the feedback!
Linvi


Potentially find a way to control question order

Maybe add questions that appear in every letter (ie clients name, clients address, attorneys name, attorneys address, etc) to an order block to control the order of those questions and everything else will come in a random order
Use signature final method to make sure signature comes last (ask Quinten for formatting)

Using separate .YML's for each "form" might be a good option? I'm unsure how these interactions work and if the "master interview" would be able to pull all the gathered info from the questions asked so far.
But I think if we If we can break them into separate files, and keep all the info gathered available to auto-populate from, I think it would allow complete control of questions order and not risk asking for the same piece of info twice.

Using separate .YML's for each "form" might be a good option? I'm unsure how these interactions work and if the "master interview" would be able to pull all the gathered info from the questions asked so far.
But I think if we If we can break them into separate files, and keep all the info gathered available to auto-populate from, I think it would allow complete control of questions order and not risk asking for the same piece of info twice.

Absolutely! We use the method of a main.yml for the main order that refers to sub interview orders in the individual yml files for each form for several other projects. We also add a shared.yml for any custom questions (not AL) shared by all forms.
See:

https://github.com/LemmaLegalConsulting/docassemble-MOHUDEvictionProject
https://github.com/LemmaLegalConsulting/docassemble-DangerLaw
https://github.com/LemmaLegalConsulting/docassemble-ElderLaw


Speech recognition reproducibility

Hi,
I am having trouble reproducing the speech recognition results. With the default settings, the model stagnates at 25% train accuracy. By employing a different optimizer, increasing the batch size and tuning the lr, I was able to reach 8% WER, but that is far from the claimed 5% without tuning.
Could you please provide additional info about your configuration (the model and number of GPUs, the total batch size), or even better: logs and/or model checkpoints?
Thank you.

@okhonko

Hi,
I'm having similar results on 1 GPU for a different dataset. Could you share with us the parameters you used to improve the results?
Thank you

hi, i was having similar issues but was able to do better with the default settings on one gpu by simulating the larger batch size with --update-freq 16

@alexbie98 I actually used this parameter when training on 1 GPU, and it didn't help. Can you elaborate on "do better"? Did you replicate the paper's WER?
@carlosep93 My parameters were: --optimizer adam --lr 5e-4 --fp16 --memory-efficient-fp16 --warmup-updates 2500 --update-freq 4
I also changed the batching logic to pack as much data on each GPU as possible, resulting in the average batch size 670 for all 8 GPUs. Only after that it started properly training.

right now it's at 96% train acc/91.7% valid acc after training for 5 days (epoch 31). Have not yet matched the reported WER, getting 9.9 on the current checkpoint. The loss/acc plateaus for a bit before dropping quite low.
https://i.imgur.com/XBL1TZo.png

Wow, that looks nice! What batch size do you have? Also, could you share the accuracy plot?

https://i.imgur.com/dKadcXq.png
The effective batch size is 80k. My training command is the same as the one in the repo with --update-freq 16

Thanks for providing the plot! Are you sure about 80k? I think, the whole librispeech train set has around 200k utterances, which means 3 batches per epoch in your case.

sorry 80k tokens*, using the default command's --max-tokens 5000 with --update-freq 16, the average number of sentences is around 60

https://i.imgur.com/dKadcXq.png
The effective batch size is 80k. My training command is the same as the one in the repo with --update-freq 16
sorry for oot reply,

Could you share how do you plot the training accuracy?

If I recall correctly, specifying a directory to --tensorboard-logdir will generate these plots viewable from tensorboard. I haven't used this a while though.

https://i.imgur.com/dKadcXq.png
The effective batch size is 80k. My training command is the same as the one in the repo with --update-freq 16
sorry for oot reply,

Could you share how do you plot the training accuracy?

If I recall correctly, specifying a directory to --tensorboard-logdir will generate these plots viewable from tensorboard. I haven't used this a while though.


Split audio option when converting audios in batches

When converting audios in batches, if I select the split audio option, it doesn't unite the chunked audio file.
I only can find the folders that contain chunk audios, is it suppose to do this way?

Exact same issue here on Linux

Does your output folder exist prior to conversion? Could be related to the bug that the output folder HAS to exist, otherwise the files wont be saved. It is not automatically created.

Closing this issue due to lack of response. Feel free to reopen if needed.


Use enumerate() instead of index variable

Coverage decreased (-0.0002%) to 99.518% when pulling 3267627a09d20e1ffb99aa2e0d27f097aa776708 on enumerate into fc6b1599fe6fd16f012838d57e5f39178930a976 on master.


Received Message "Oops! Error Occured..." After Signing Up

Describe the bug
I received the message "Oops! Error Occured..." After Signing up. The message appeared after the "Financial Incentive? Own Your Data" screen. This was done on Android phone - Google Pixel.
Also, the error message contains a spelling error (at least here in the United States). It should say "Occurred".
To Reproduce
Steps to reproduce the behavior:

Register on SocialX
Click next all the way until you get to the last one. I believe it says "Financial Incentive? Own Your Data" or a similar message.
Click next
Error occurs

Screenshots

@Willwalker1   please check if the problem still occurs or if that is fixed now.
Thanks for your help!


WIP Adds uTP network test (currently failing)

r? @canndrew
(maidsafe_highfive has picked a reviewer for you, use r? to override)

As being replaced by the PR https://github.com/maidsafe/crust/pull/442


[APM-SERVER] It is not possible to configure HTTPS on the pod

Chart version:
7.6.1
Kubernetes version:
1.17
Kubernetes provider: E.g. GKE (Google Kubernetes Engine)
GKE, Kind
Helm Version:
3.0.2
helm get release output
USER-SUPPLIED VALUES:
apmConfig:
  apm-server.yml: |
    logging.level: debug
    apm-server:
      host: "<IP_ADDRESS>:8200"
      rum.enabled: true
      ilm.enabled: true
      secret_token: ${APM_TOKEN}
# HERE is the issue if it is true the livenessProbe and readinessProbe fails
      ssl.enabled: true
      ssl.key: /usr/share/apm-server/config/certs/tls.key
      ssl.certificate: /usr/share/apm-server/config/certs/tls.crt
    queue: {}
    monitoring.elasticsearch.ssl.verification_mode: none
    setup.kibana:
      host: ${KIBANA_PROTO}://${KIBANA_HOST}:${KIBANA_PORT}
      protocol: ${KIBANA_PROTO}
      username: ${KIBANA_USERNAME}
      password: ${KIBANA_PASSWORD}
    output.elasticsearch:
      enabled: true
      hosts: ["${ELASTICSEARCH_PROTO}://${ELASTICSEARCH_HOST}:${ELASTICSEARCH_PORT}"]
      username: ${ELASTICSEARCH_USERNAME}
      password: ${ELASTICSEARCH_PASSWORD}
      ssl.verification_mode: none
extraEnvs:
- name: ELASTICSEARCH_USERNAME
  valueFrom:
    secretKeyRef:
      key: user
      name: es-creds
- name: ELASTICSEARCH_PASSWORD
  valueFrom:
    secretKeyRef:
      key: password
      name: es-creds
- name: ELASTICSEARCH_PROTO
  valueFrom:
    secretKeyRef:
      key: protocol
      name: es-creds
- name: ELASTICSEARCH_HOST
  valueFrom:
    secretKeyRef:
      key: host
      name: es-creds
- name: ELASTICSEARCH_PORT
  valueFrom:
    secretKeyRef:
      key: port
      name: es-creds
- name: NODE_NAME
  valueFrom:
    fieldRef:
      fieldPath: spec.nodeName
- name: KIBANA_HOST
  valueFrom:
    secretKeyRef:
      key: host
      name: kibana-creds
- name: KIBANA_PROTO
  valueFrom:
    secretKeyRef:
      key: protocol
      name: kibana-creds
- name: KIBANA_PORT
  valueFrom:
    secretKeyRef:
      key: port
      name: kibana-creds
- name: KIBANA_USERNAME
  valueFrom:
    secretKeyRef:
      key: user
      name: kibana-creds
- name: KIBANA_PASSWORD
  valueFrom:
    secretKeyRef:
      key: password
      name: kibana-creds
- name: APM_TOKEN
  valueFrom:
    secretKeyRef:
      key: token
      name: apm-creds
extraVolumeMounts:
- mountPath: /usr/share/apm-server/config/certs
  name: default-tls
extraVolumes:
- name: default-tls
  secret:
    defaultMode: 420
    secretName: default-tls
image: elastic/apm-server
imagePullPolicy: Always
imageTag: 7.6.1
ingress:
  annotations:
    cert-manager.io/cluster-issuer: letsencrypt-staging
    ingress.kubernetes.io/ssl-redirect: "true"
    kubernetes.io/ingress.class: nginx
    kubernetes.io/tls-acme: "true"
    nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
  enabled: true
  hosts:
  - apm.IP.ip.es.io
  path: /
  tls:
  - hosts:
    - apm.IP.ip.es.io
    secretName: apm-ingress-tls
replicas: 2
service:
  annotations: {}
  port: "8200"
  targetPort: "8200"
  type: ClusterIP

Describe the bug:
If you configure the APM Server to use TLS the pod is killed by the livenessProbe check.
livenessProbe and readinessProbe only check HTTP so they fail if you configure HTTPS
Steps to reproduce:

Install the Helm chart with the provided configuration
wait a couple of mins
check the pod logs to confirm the pod is killed

Expected behavior:
The APM server goes up and running, a way to configure the livenessProbe and readinessProbe to use HTTPS would resolve the issue.
Provide logs and/or server output (if relevant):
2020-03-19T12:21:42.773Z	DEBUG	[monitoring]	memqueue/ackloop.go:128	ackloop: return ack to broker loop:1
2020-03-19T12:21:42.774Z	DEBUG	[monitoring]	memqueue/ackloop.go:131	ackloop:  done send ack
2020-03-19T12:21:52.720Z	DEBUG	[service]	service/service.go:53	Received sigterm/sigint, stopping
2020-03-19T12:21:52.720Z	INFO	[beater]	beater/beater.go:230	stopping apm-server... waiting maximum of 5 seconds for queues to drain
2020-03-19T12:21:52.720Z	INFO	[beater]	beater/http.go:103	Stop listening on: [::]:8200
2020-03-19T12:21:52.721Z	INFO	[beater]	beater/server.go:88	Server stopped
2020-03-19T12:21:52.721Z	DEBUG	[publisher]	pipeline/client.go:162	client: closing acker

still  valid

still valid

still valid

still valid

still valid
Note that the above is not a matter of HTTP/HTTPS, as the "http" port reference on the readiness/liveness probes is to the named port 8200 (not 80/443).
Encountering the same issue. I've tried this configuration set as well, and even with ssl.client_authentication: optional or none, the probes still fail on the apm-server pod. Only ssl.enabled: false works for the probes, as currently configured.
It does work to change the probes to use tcpSocket instead of httpGet, as a workaround.

Can I offer a possible means to resolving this issue? I think it stems from trying in this chart to fit the generic implementation of apm-server into a Kubernetes context while not using Kubernetes practices. I would contend that, instead of using apm-server.yaml as the configuration location for adding SSL communication with agents, SSL should be separate from the apm-server container. By using apm-server.yaml, there's not a straightforward way to use something like a cert-manager Certificate resource to create and connect with any agents referencing that cert.
Instead, this chart could be modified to place an ssl proxy in front of the apm-server Pod. In this way, SSL communication with agents is assured while also continuing to use httpGet probes as expected and successfully. Enabling SSL communication with agents in this chart is then decoupled from the apm-server.yaml configuration.

Another solution is to just override the liveness and readiness probes to use an HTTPS check:
livenessProbe:
  httpGet:
    path: /
    port: http
    scheme: HTTPS
  initialDelaySeconds: 30
  failureThreshold: 3
  periodSeconds: 10
  timeoutSeconds: 5
readinessProbe:
  httpGet:
    path: /
    port: http
    scheme: HTTPS
  initialDelaySeconds: 30
  failureThreshold: 3
  periodSeconds: 10
  timeoutSeconds: 5

Thanks @mfinelli !!! That worked for me. Did not know about the scheme field on httpGet probes.

scheme: HTTPS

Thanks @mfinelli this helped me resolve issues with APM after enabling SSL on it using helm installation.

Chart version:
7.6.1
Kubernetes version:
1.17
Kubernetes provider: E.g. GKE (Google Kubernetes Engine)
GKE, Kind
Helm Version:
3.0.2
helm get release output
USER-SUPPLIED VALUES:
apmConfig:
  apm-server.yml: |
    logging.level: debug
    apm-server:
      host: "<IP_ADDRESS>:8200"
      rum.enabled: true
      ilm.enabled: true
      secret_token: ${APM_TOKEN}
# HERE is the issue if it is true the livenessProbe and readinessProbe fails
      ssl.enabled: true
      ssl.key: /usr/share/apm-server/config/certs/tls.key
      ssl.certificate: /usr/share/apm-server/config/certs/tls.crt
    queue: {}
    monitoring.elasticsearch.ssl.verification_mode: none
    setup.kibana:
      host: ${KIBANA_PROTO}://${KIBANA_HOST}:${KIBANA_PORT}
      protocol: ${KIBANA_PROTO}
      username: ${KIBANA_USERNAME}
      password: ${KIBANA_PASSWORD}
    output.elasticsearch:
      enabled: true
      hosts: ["${ELASTICSEARCH_PROTO}://${ELASTICSEARCH_HOST}:${ELASTICSEARCH_PORT}"]
      username: ${ELASTICSEARCH_USERNAME}
      password: ${ELASTICSEARCH_PASSWORD}
      ssl.verification_mode: none
extraEnvs:
- name: ELASTICSEARCH_USERNAME
  valueFrom:
    secretKeyRef:
      key: user
      name: es-creds
- name: ELASTICSEARCH_PASSWORD
  valueFrom:
    secretKeyRef:
      key: password
      name: es-creds
- name: ELASTICSEARCH_PROTO
  valueFrom:
    secretKeyRef:
      key: protocol
      name: es-creds
- name: ELASTICSEARCH_HOST
  valueFrom:
    secretKeyRef:
      key: host
      name: es-creds
- name: ELASTICSEARCH_PORT
  valueFrom:
    secretKeyRef:
      key: port
      name: es-creds
- name: NODE_NAME
  valueFrom:
    fieldRef:
      fieldPath: spec.nodeName
- name: KIBANA_HOST
  valueFrom:
    secretKeyRef:
      key: host
      name: kibana-creds
- name: KIBANA_PROTO
  valueFrom:
    secretKeyRef:
      key: protocol
      name: kibana-creds
- name: KIBANA_PORT
  valueFrom:
    secretKeyRef:
      key: port
      name: kibana-creds
- name: KIBANA_USERNAME
  valueFrom:
    secretKeyRef:
      key: user
      name: kibana-creds
- name: KIBANA_PASSWORD
  valueFrom:
    secretKeyRef:
      key: password
      name: kibana-creds
- name: APM_TOKEN
  valueFrom:
    secretKeyRef:
      key: token
      name: apm-creds
extraVolumeMounts:
- mountPath: /usr/share/apm-server/config/certs
  name: default-tls
extraVolumes:
- name: default-tls
  secret:
    defaultMode: 420
    secretName: default-tls
image: elastic/apm-server
imagePullPolicy: Always
imageTag: 7.6.1
ingress:
  annotations:
    cert-manager.io/cluster-issuer: letsencrypt-staging
    ingress.kubernetes.io/ssl-redirect: "true"
    kubernetes.io/ingress.class: nginx
    kubernetes.io/tls-acme: "true"
    nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
  enabled: true
  hosts:
  - apm.IP.ip.es.io
  path: /
  tls:
  - hosts:
    - apm.IP.ip.es.io
    secretName: apm-ingress-tls
replicas: 2
service:
  annotations: {}
  port: "8200"
  targetPort: "8200"
  type: ClusterIP

Describe the bug:
If you configure the APM Server to use TLS the pod is killed by the livenessProbe check.
livenessProbe and readinessProbe only check HTTP so they fail if you configure HTTPS
Steps to reproduce:

Install the Helm chart with the provided configuration
wait a couple of mins
check the pod logs to confirm the pod is killed

Expected behavior:
The APM server goes up and running, a way to configure the livenessProbe and readinessProbe to use HTTPS would resolve the issue.
Provide logs and/or server output (if relevant):
2020-03-19T12:21:42.773Z	DEBUG	[monitoring]	memqueue/ackloop.go:128	ackloop: return ack to broker loop:1
2020-03-19T12:21:42.774Z	DEBUG	[monitoring]	memqueue/ackloop.go:131	ackloop:  done send ack
2020-03-19T12:21:52.720Z	DEBUG	[service]	service/service.go:53	Received sigterm/sigint, stopping
2020-03-19T12:21:52.720Z	INFO	[beater]	beater/beater.go:230	stopping apm-server... waiting maximum of 5 seconds for queues to drain
2020-03-19T12:21:52.720Z	INFO	[beater]	beater/http.go:103	Stop listening on: [::]:8200
2020-03-19T12:21:52.721Z	INFO	[beater]	beater/server.go:88	Server stopped
2020-03-19T12:21:52.721Z	DEBUG	[publisher]	pipeline/client.go:162	client: closing acker

Hi @kuisathaverat could you please share what is the benefit of all the kibana TLS info in the APM server config? I believe it directly communicates with the ES server only. Please suggest?

overwriting the probes and using the schema HTTPS resolves the issue, see https://github.com/elastic/helm-charts/issues/527#issuecomment-856830956


Dashboard gives a generic error message when duplicate bucket is created in mult-cloud

Issue/Feature Description:
Dashboard gives a generic error message while creating bucket with the exisiting bucket name.
Why this issue to fixed / feature is needed(give scenarios or use cases):
Error seems to be generic and confuses the user to believe something is wrong with the configuration.
How to reproduce, in case of a bug:
Create a mult-cloud bucket with the same name which exisit already in cloud.

A follow up PR can be raised in multi-cloud if it need changes in the backend

@asifdxtreme I checked this and see that the dashboard receives a generic error from the API, which is shown to the user.

The logs from the S3 container show that the cloud returns an error 409 as the bucket name was already present on the cloud.
[2021-04-09T08:55:10+05:30] [ERROR] [/root/gopath/src/github.com/sodafoundation/multi-cloud/s3/pkg/datastore/aws/aws.go] [aws.(*AwsAdapter).BucketCreate():77] [PID:8] the create bucket failed in aws-s3 service with err:%sBucketAlreadyOwnedByYou: Your previous request to create the named bucket succeeded and you already own it.
	status code: 409, request id: 56R6N8R9QXAJB7SJ, host id: gmN8PFktES89VnRnM2jnFSw0DuSvP5yDtY2CbjZUN6Qd6HF2yL+wL0rQLhwrDZBvF/6dWAluA4Q=

If this error can be send through in the API response then we can display the same.


operators opentelemetry-operator (0.46.0)

Signed-off-by: Yuri Sa<EMAIL_ADDRESS>Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[x] Are you familiar with our contribution guidelines?
[x] Have you packaged and deployed your Operator for Operator Framework?

[x] Is your submission signed?
[x] Is operator icon set?

Updates to existing Operators

[x] Did you create a ci.yaml file according to the update instructions?
[x] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

/merge possible

@jpkrohling , please approve

@jpkrohling , @VineethReddy02 , @pavolloffay . Could you please have a look?

@yuriolisa I would recommend publishing only the latest if we are publishing the two versions at the same time to this repo. Publishing 0.46.0 when 0.47.0 is available doesn't make sense. In fact, we skipped a few versions that are not published to this repo and ended up publishing the latest.

+1 this PR can be closed per ^ comment.


Typo in example

Thanks but addressed in https://github.com/charliekassel/vuejs-datepicker/pull/514


Selecting a tab in Meta-Example may not be applied immediately.

Today I tried meta_xeample.rb with glimmer-dsl-libui.
I found a very small unexpected behavior.
After launching meta_example.rb, open the Advanced tab ①,  and you will see "Area Gallery (4 versions)" selected.
Now, Click on the Launch button ②. The "Basic Area" will be launched. This was an unexpected behavior for me.
For practical use, there is no problem at all, but I would like to report it.
Have a good day.

Ubuntu 21.10 impish
ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux]
glimmer-dsl-libui (0.4.18)

Yes, I noticed this behavior on Linux only. On the Mac and Windows, the selected example under Basic remains selected when I switch to the Advanced tab, so it is not confusing to the user.

Thank you for reporting. Unfortunately, it is not a Glimmer DSL for LibUI issue, yet a C libui issue. Perhaps, you could report there instead and link back here just for reference.

Thanks.
I understand your intended behavior on macOS and Windows.
The expected behavior is that the radio buttons are not selected when a tab So it is a problem with c libui that the radio buttons are selected from the beginning. Also, as you said, I have confirmed that there is no function to detect that the tab has been switched.
I thought about checking the tab number when the start button is pressed, but that would be useless if the code displayed in the text area is not updated when the tab is switched. I see, it is not an easy fix.
By the way, you might be wondering why I'm running meta_example today. Actually, I wrote a small post on Qiita to introduce glimmer-dsl-libui to Rubyists in Japan. This is a website equivalent to dev.to in Japanese. I hope it will help more people in Japan to discover glimmer-dsl-libui.
Take care again.


Use RtmpOnlyAudio. When I step back to the background after the App successfully pushes the audio stream, the other device cannot receive the audio stream pushed by me after the voice call lasts for one minute

I use RtmpOnlyAudio to push audio streams to the Nginx server. When the App pushes the audio streams successfully, I step back to the background. After the voice call lasts for one minute, the other device cannot receive the audio streams I push, but RtmpOnlyAudio The callback method has always been onNewBitrateRtmp, so I would like to ask what specifically caused the voice call to be silent after my App retreated to the background for one minute
This is the log from AndroidStadio

App back in the background for one minute, push audio no sound, this is the Nginx log

My colleague's ios app doesn't have this problem, and it works fine for more than half an hour after it's retreated into the background

Finally, I solved this problem because the microphone permissions will be cancelled when the android is back in the background, so I need to open a foreground service and keep the microphone permissions running all the time, so that I can keep the voice.

Now I have another situation
The voice call function is implemented. After 26 minutes of the call, there is no voice in the voice call, but the call is always displayed, and there is no callback for error or disconnection. Therefore, I would like to ask whether the audio push fails due to network fluctuation and disconnection.

Hello, I encountered a problem when I was using RtmpOnlyAudio to develop voice calls. When I started to push the stream to apply for voice rights, the user allowed the voice rights. At this time, I entered the phone setting interface, selected my App, and manually added the geographical location or call rights. Then I entered my App again and started to push the stream (See the worklog), the push will work, but the onConnectionSuccessRtmp callback will not happen again
Work log
2023-01-06 09:58:09.732  E/CME Player: RtmpOnlyAudio,onConnectionSuccessRtmp=====onConnectionSuccessRtmp
2023-01-06 09:58:09.932  E/CME Player: RtmpOnlyAudio:Success==直接语音==rtsp://root:root@<IP_ADDRESS>:7788/session0.mpg
2023-01-06 09:58:09.941  E/TAG: RtmpOnlyAudio,onNewBitrateRtmp=====onNewBitrateRtmp410
2023-01-06 09:58:10.143  E/TAG: RtmpOnlyAudio,RtmpOnlyAudio=====BadName received, endpoint in use.
2023-01-06 09:58:10.143  E/TAG: RtmpOnlyAudio,onConnectionFailedRtmp=====onConnectionFailedRtmp
2023-01-06 09:58:10.223  E/TAG: RtmpOnlyAudio,RtmpOnlyAudio=====BadName received, endpoint in use.
2023-01-06 09:58:10.224  E/TAG: RtmpOnlyAudio,onConnectionFailedRtmp=====onConnectionFailedRtmp
2023-01-06 09:58:10.355  E/TAG: RtmpOnlyAudio,RtmpOnlyAudio=====Error configure stream, publish permitted failed
2023-01-06 09:58:10.355  E/TAG: RtmpOnlyAudio,onConnectionFailedRtmp=====onConnectionFailedRtmp
2023-01-06 09:58:10.356  E/TAG: RtmpOnlyAudio,onDisconnectRtmp=====onDisconnectRtmp
2023-01-06 09:58:10.356  E/TAG: RtmpOnlyAudio,RtmpOnlyAudio=====BadName received, endpoint in use.
2023-01-06 09:58:10.356  E/TAG: RtmpOnlyAudio,onConnectionFailedRtmp=====onConnectionFailedRtmp
2023-01-06 09:58:10.557  E/TAG: RtmpOnlyAudio,RtmpOnlyAudio=====Error configure stream, publish permitted failed
2023-01-06 09:58:10.557  E/TAG: RtmpOnlyAudio,onConnectionFailedRtmp=====onConnectionFailedRtmp
2023-01-06 09:58:10.559  E/TAG: RtmpOnlyAudio,onDisconnectRtmp=====onDisconnectRtmp
2023-01-06 09:58:10.635  E/TAG: RtmpOnlyAudio,RtmpOnlyAudio=====BadName received, endpoint in use.
2023-01-06 09:58:10.635  E/TAG: RtmpOnlyAudio,onConnectionFailedRtmp=====onConnectionFailedRtmp
2023-01-06 09:58:10.777  E/TAG: RtmpOnlyAudio,onDisconnectRtmp=====onDisconnectRtmp
2023-01-06 09:58:10.947  E/TAG: RtmpOnlyAudio,RtmpOnlyAudio=====Error configure stream, publish permitted failed
2023-01-06 09:58:10.947  E/TAG: RtmpOnlyAudio,onConnectionFailedRtmp=====onConnectionFailedRtmp
2023-01-06 09:58:10.948  E/TAG: RtmpOnlyAudio,onDisconnectRtmp=====onDisconnectRtmp
2023-01-06 09:58:11.057  E/TAG: RtmpOnlyAudio,onNewBitrateRtmp=====onNewBitrateRtmp64372
2023-01-06 09:58:11.125  E/TAG: RtmpOnlyAudio,onDisconnectRtmp=====onDisconnectRtmp
2023-01-06 09:58:11.288  E/TAG: RtmpOnlyAudio,RtmpOnlyAudio=====Error configure stream, publish permitted failed
2023-01-06 09:58:11.288  E/TAG: RtmpOnlyAudio,onConnectionFailedRtmp=====onConnectionFailedRtmp
2023-01-06 09:58:11.290  E/TAG: RtmpOnlyAudio,onDisconnectRtmp=====onDisconnectRtmp
2023-01-06 09:58:11.435  E/TAG: RtmpOnlyAudio,onDisconnectRtmp=====onDisconnectRtmp
2023-01-06 09:58:11.604  E/TAG: RtmpOnlyAudio,onDisconnectRtmp=====onDisconnectRtmp
2023-01-06 09:58:12.177  E/TAG: RtmpOnlyAudio,onNewBitrateRtmp=====onNewBitrateRtmp67678

Hello,
About the first one (audio fail after 12min). I recommend you check that your audio is working fine before send it. You can use startRecord method to check it because the buffer is the same for stream and record.
About the second one. It is really weird, try to recreate the class after return to your activity to reset all

Closing as inactive.


Add CLI options to download plugins, both all plugins and a specific …

Tested with racetrack running in docker.
To setup tests:
cd racetrack_client && pip install -e . && sleep 3 && racetrack plugin install github.com/TheRacetrack/plugin-docker-infrastructure && racetrack plugin install github.com/TheRacetrack/plugin-python-job-type==2.13.0 && mkdir temp_folder
To download a plugin - both name and version required:
racetrack plugin download python3-job-type 2.13.0

To test if we are actually downloading the right thing
racetrack plugin download python3-job-type 2.13.0 --out-dir=temp_folder && cd temp_folder
wget https://github.com/TheRacetrack/plugin-python-job-type/releases/download/2.13.0/python3-job-type-2.13.0.zip -O from_github.zip
sha256sum python3-job-type-2.13.0.zip
sha256sum from_github.zip

To test the download button, upload a plugin, then click the download button on /dashboard/ui/administration

@anders314159 Please include a short note in docs/CHANGELOG.md about what you've made


DBZ-2525 Generify exclusion of columns from snapshotting in all relational connectors

https://issues.redhat.com/browse/DBZ-2525

@Naros Added the suggested changes. Will be further adding PRs for Db2 and Vitess after this gets done.

@gunnarmorling your review is pending here, in case you got some free time today please have a look :-)

@Naros Could you please review this? I have added Gunnar's suggestions for unifying column logic.

Hey @ani-sha, I've pushed one more commit to this PR which shows how I suggest the interaction to look like. This only does the required changes to RelationalSnapshotChangeEventSource and the MySQL implementation, but perhaps you can pick it up from there, if you agree it makes sense that way? Specifically, the filter application happens only once in the base class. Also custom statements are left alone (i.e. we don't apply the column filtering there; only Oracle needs to keep the addition of the AS OF SCN part). Does that make sense?

@ani-sha, so what should we do with this one? Can you rebase it to the current master, so to address the conflict and also trigger another CI run? Thx!

Sample of the NPE:
io.debezium.DebeziumException: io.debezium.DebeziumException: java.lang.NullPointerException
	at io.debezium.pipeline.source.AbstractSnapshotChangeEventSource.execute(AbstractSnapshotChangeEventSource.java:79)
	at io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:118)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: io.debezium.DebeziumException: java.lang.NullPointerException
	at io.debezium.relational.RelationalSnapshotChangeEventSource.lambda$createSchemaChangeEventsForTables$2(RelationalSnapshotChangeEventSource.java:281)
	at io.debezium.pipeline.EventDispatcher.dispatchSchemaChangeEvent(EventDispatcher.java:307)
	at io.debezium.relational.RelationalSnapshotChangeEventSource.createSchemaChangeEventsForTables(RelationalSnapshotChangeEventSource.java:276)
	at io.debezium.relational.RelationalSnapshotChangeEventSource.doExecute(RelationalSnapshotChangeEventSource.java:124)
	at io.debezium.pipeline.source.AbstractSnapshotChangeEventSource.execute(AbstractSnapshotChangeEventSource.java:70)
	... 6 more
Caused by: java.lang.NullPointerException
	at io.debezium.pipeline.EventDispatcher$SchemaChangeEventReceiver.schemaChangeEvent(EventDispatcher.java:541)
	at io.debezium.relational.RelationalSnapshotChangeEventSource.lambda$createSchemaChangeEventsForTables$2(RelationalSnapshotChangeEventSource.java:278)
	... 10 more

@gunnarmorling So the EventDispatcher class is causing the NPE. https://github.com/debezium/debezium/blob/b0c0d879e5c3c8bbe164e496933e6a66be17304b/debezium-core/src/main/java/io/debezium/pipeline/EventDispatcher.java#L118


Version Up to 1.8.2

Description
Please include a summary of the change and which is fixed.

Version up

How has this been tested?
Please describe the tests that you ran to verify your changes.

[ ] UnitTest
[ ] Benchmark

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

Project coverage is 90.19%. Comparing base (31dcd1d) to head (3f8c45d).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #579      +/-   ##
==========================================
+ Coverage   90.15%   90.19%   +0.03%
==========================================
  Files         129      131       +2
  Lines        4642     4680      +38
  Branches      752      755       +3
==========================================
+ Hits         4185     4221      +36
- Misses        304      305       +1
- Partials      153      154       +1

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


Cluster creation with custom cluster driver always stopped after 30 seconds

What kind of request is this: bug
Steps to reproduce:
I have implemented a custom cluster driver, following the kontainer-engine-cluster-driver-example, and installed in my Rancher instance. When using it to create a cluster, I always run into the following problem:
The creation sequence starts out with invoking the cluster driver 6 times, each time only calling the GetCapabilities and GetK8SCapabilities methods (from the Rancher log, some white space added for readability):
time="2019-05-23T12:29:27Z" level=info msg="     NewDriver | "
2019/05/23 12:29:27 [INFO] [mgmt-project-rbac-create] Updating project p-gml95
time="2019-05-23T12:29:27Z" level=info msg="RPC GrpcServer listening on address <IP_ADDRESS>:10107"
time="2019-05-23T12:29:27Z" level=info msg="Kubika driver up and running at <IP_ADDRESS>:10107"
2019/05/23 12:29:27 [INFO] [mgmt-auth-prtb-controller] Creating role project-owner in namespace c-6x6gt
2019/05/23 12:29:27 [INFO] [mgmt-auth-crtb-controller] Creating roleBinding for subject user-vrdw5 with role cluster-owner in namespace
2019/05/23 12:29:27 [INFO] [mgmt-auth-prtb-controller] Creating roleBinding for subject user-vrdw5 with role project-owner in namespace
2019/05/23 12:29:27 [INFO] [mgmt-auth-prtb-controller] Creating roleBinding for subject user-vrdw5 with role project-owner in namespace
2019/05/23 12:29:27 [INFO] [mgmt-auth-prtb-controller] Creating role project-owner in namespace p-gml95
2019/05/23 12:29:27 [INFO] [mgmt-auth-prtb-controller] Creating role project-owner in namespace p-rqxbx
2019/05/23 12:29:27 [INFO] [mgmt-auth-prtb-controller] Creating role admin in namespace p-gml95
2019/05/23 12:29:27 [INFO] [mgmt-auth-prtb-controller] Creating role admin in namespace p-rqxbx
2019/05/23 12:29:27 [INFO] [mgmt-auth-prtb-controller] Creating roleBinding for subject user-vrdw5 with role project-owner in namespace
2019/05/23 12:29:27 [INFO] [mgmt-auth-prtb-controller] Creating roleBinding for subject user-vrdw5 with role project-owner in namespace
2019/05/23 12:29:27 [INFO] [mgmt-auth-prtb-controller] Creating roleBinding for subject user-vrdw5 with role admin in namespace
2019/05/23 12:29:27 [INFO] [mgmt-auth-prtb-controller] Creating roleBinding for subject user-vrdw5 with role admin in namespace
2019/05/23 12:29:27 [INFO] [mgmt-auth-prtb-controller] Updating clusterRoleBinding clusterrolebinding-7lkq9 for cluster membership in cluster c-6x6gt for subject user-vrdw5
2019/05/23 12:29:32 [INFO] kontainerdriver kd-tb6dt listening on address <IP_ADDRESS>:10107
time="2019-05-23T12:29:32Z" level=info msg="GetCapabilities | "
2019/05/23 12:29:32 [INFO] kontainerdriver kd-tb6dt stopped
time="2019-05-23T12:29:32Z" level=info msg="GetK8SCapabilities | "
2019/05/23 12:29:32 [INFO] [mgmt-cluster-rbac-delete] Updating cluster c-6x6gt

time="2019-05-23T12:29:32Z" level=info msg="     NewDriver | "
time="2019-05-23T12:29:32Z" level=info msg="RPC GrpcServer listening on address <IP_ADDRESS>:10404"
time="2019-05-23T12:29:32Z" level=info msg="Kubika driver up and running at <IP_ADDRESS>:10404"
2019/05/23 12:29:37 [INFO] kontainerdriver kd-tb6dt listening on address <IP_ADDRESS>:10404
time="2019-05-23T12:29:37Z" level=info msg="GetCapabilities | "
time="2019-05-23T12:29:37Z" level=info msg="GetK8SCapabilities | "
2019/05/23 12:29:37 [INFO] kontainerdriver kd-tb6dt stopped

time="2019-05-23T12:29:37Z" level=info msg="     NewDriver | "
time="2019-05-23T12:29:37Z" level=info msg="RPC GrpcServer listening on address <IP_ADDRESS>:10539"
time="2019-05-23T12:29:37Z" level=info msg="Kubika driver up and running at <IP_ADDRESS>:10539"
2019/05/23 12:29:42 [INFO] kontainerdriver kd-tb6dt listening on address <IP_ADDRESS>:10539
time="2019-05-23T12:29:42Z" level=info msg="GetCapabilities | "
time="2019-05-23T12:29:42Z" level=info msg="GetK8SCapabilities | "
2019/05/23 12:29:42 [INFO] kontainerdriver kd-tb6dt stopped

time="2019-05-23T12:29:42Z" level=info msg="     NewDriver | "
time="2019-05-23T12:29:42Z" level=info msg="RPC GrpcServer listening on address <IP_ADDRESS>:10035"
time="2019-05-23T12:29:42Z" level=info msg="Kubika driver up and running at <IP_ADDRESS>:10035"
2019/05/23 12:29:47 [INFO] kontainerdriver kd-tb6dt listening on address <IP_ADDRESS>:10035
time="2019-05-23T12:29:47Z" level=info msg="GetCapabilities | "
time="2019-05-23T12:29:47Z" level=info msg="GetK8SCapabilities | "
2019/05/23 12:29:47 [INFO] kontainerdriver kd-tb6dt stopped

time="2019-05-23T12:29:47Z" level=info msg="     NewDriver | "
time="2019-05-23T12:29:47Z" level=info msg="RPC GrpcServer listening on address <IP_ADDRESS>:10581"
time="2019-05-23T12:29:47Z" level=info msg="Kubika driver up and running at <IP_ADDRESS>:10581"
2019/05/23 12:29:52 [INFO] kontainerdriver kd-tb6dt listening on address <IP_ADDRESS>:10581
2019/05/23 12:29:52 [INFO] kontainerdriver kd-tb6dt stopped
time="2019-05-23T12:29:52Z" level=info msg="GetCapabilities | "
time="2019-05-23T12:29:52Z" level=info msg="GetK8SCapabilities | "

time="2019-05-23T12:29:52Z" level=info msg="     NewDriver | "
time="2019-05-23T12:29:52Z" level=info msg="RPC GrpcServer listening on address <IP_ADDRESS>:10417"
time="2019-05-23T12:29:52Z" level=info msg="Kubika driver up and running at <IP_ADDRESS>:10417"
2019/05/23 12:29:57 [INFO] kontainerdriver kd-tb6dt listening on address <IP_ADDRESS>:10417
time="2019-05-23T12:29:57Z" level=info msg="GetCapabilities | "
2019/05/23 12:29:57 [INFO] kontainerdriver kd-tb6dt stopped
time="2019-05-23T12:29:57Z" level=info msg="GetK8SCapabilities | "

On the seventh invocation, cluster provisioning actually begins. The cluster driver successfully requests the cluster provisioning (which is then handled by our provisioning system), and goes into a cluster wait loop. However, 30 seconds later (counted from entry into Create), Rancher stops the custom driver with [cluster-provisioner-controller] failed with : timed out waiting for the condition:
2019/05/23 12:29:57 [INFO] Provisioning cluster [c-6x6gt]
2019/05/23 12:29:57 [INFO] Creating cluster [c-6x6gt]
time="2019-05-23T12:29:57Z" level=info msg="     NewDriver | "
time="2019-05-23T12:29:57Z" level=info msg="RPC GrpcServer listening on address <IP_ADDRESS>:10611"
time="2019-05-23T12:29:57Z" level=info msg="Kubika driver up and running at <IP_ADDRESS>:10611"
2019/05/23 12:30:02 [INFO] kontainerdriver kd-tb6dt listening on address <IP_ADDRESS>:10611
time="2019-05-23T12:30:02Z" level=info msg="GetCapabilities | "
time="2019-05-23T12:30:02Z" level=info msg="        Create | "
time="2019-05-23T12:30:02Z" level=info msg="      newState | "
ERROR: logging before flag.Parse: I0523 12:30:02.968643      81 http.go:110] HTTP2 has been explicitly disabled
time="2019-05-23T12:30:02Z" level=info msg="createClusterCR | creating the cluster CR"
time="2019-05-23T12:30:02Z" level=info msg="        Create | cluster CR for cluster 'beta' created"
time="2019-05-23T12:30:02Z" level=info msg="waitForCluster | waiting for cluster 'beta' to reach phase 'available'"
time="2019-05-23T12:30:03Z" level=info msg="         func1 | cluster 'beta' entered phase 'requested'"
time="2019-05-23T12:30:07Z" level=info msg="         func1 | cluster 'beta' entered phase 'preparing'"
time="2019-05-23T12:30:13Z" level=info msg="         func1 | cluster 'beta' entered phase 'prepared'"
time="2019-05-23T12:30:23Z" level=info msg="         func1 | cluster 'beta' entered phase 'provisioning'"
2019/05/23 12:30:32 [INFO] kontainerdriver kd-tb6dt stopped
2019/05/23 12:30:33 [ERROR] ClusterController c-6x6gt [cluster-provisioner-controller] failed with : timed out waiting for the condition

Result:
Rancher assumes provisioning has failed and subsequently tries it again (same sequence: 6 driver invocations, the seventh one actually doing a cluster provisioning). However, since the creation of the cluster is actually already in progress, the cluster driver now rejects this:
time="2019-05-23T12:31:13Z" level=info msg="     NewDriver | "
time="2019-05-23T12:31:13Z" level=info msg="RPC GrpcServer listening on address <IP_ADDRESS>:10533"
time="2019-05-23T12:31:13Z" level=info msg="Kubika driver up and running at <IP_ADDRESS>:10533"
2019/05/23 12:31:18 [INFO] kontainerdriver kd-tb6dt listening on address <IP_ADDRESS>:10533
time="2019-05-23T12:31:18Z" level=info msg="GetCapabilities | "
2019/05/23 12:31:18 [ERROR] Cluster c-6x6gt previously failed to create
time="2019-05-23T12:31:18Z" level=info msg="        Create | "
time="2019-05-23T12:31:18Z" level=info msg="      newState | "
ERROR: logging before flag.Parse: I0523 12:31:18.069023     118 http.go:110] HTTP2 has been explicitly disabled
time="2019-05-23T12:31:18Z" level=info msg="createClusterCR | creating the cluster CR"
2019/05/23 12:31:18 [INFO] kontainerdriver kd-tb6dt stopped
2019/05/23 12:31:18 [ERROR] ClusterController c-6x6gt [cluster-provisioner-controller] failed with : clusters.kubika.audi.de "beta" already exists

The cluster is shown in the Rancher UI as in error state (first timed out waiting for the condition, later clusters.kubika.audi.de "beta" already exists).
Environment information

Rancher version: 2.2.3
Installation option: running as a deployment on K8s, scaled to 1 replica

I finally found the root cause. It's within my own cluster wait logic. I was using a polling mechanism that came with a default 30 seconds timeout. So definitely not a Rancher bug. Mea culpa!!


unfocus event should be bound to document, not document.body.

Here's a fiddle (forked from one of yours) that uses {hide: "unfocus"}.   As you will see, clicking inside the box dismisses the qTip, but clicking outside (above or below) the box does not dismiss the qTip.
The apparent fix is to change this line from
targets.body.bind('mousedown'+namespace, function(event) {

to
targets.document.bind('mousedown'+namespace, function(event) {

This actually affects my current project at work, where a short page has a qTip near the bottom; clicking under the qTip didn't dismiss it, as the fiddle demonstrated.
Is there any reason it wasn't targets.document in the first place?

Can you verify this change works in IE too please? IT was originally document.body as I recall it didn't work for me when using document in IE... but I could be wrong!

Right now, I'm not able to use that same fiddle to dismiss the popup in any of Chrome/FF/IE8.  I saw that the resource is pointing towards a nightly build, so maybe one of the changes since yesterday broke unfocus?

This works fine in both IE8 and IE9, as well as Chrome and FF.

I think the problem is the fiddle, as the body element doesn't extend the full height of the window it seems, it misses the top part of it, so unfocus won't work there.
pivotal, do you mean the current implementation does, or that  the change to using "document" instead of "document.body" works fine?

Added in the latest revision :)


PPC64 Link problems on Linux

Link issue on GCC112. Too much output to paste on GitHub and Pastebin.
failed-link.zip

Output from make -jN is not exactly helpful as it interleaves errors and it's impossible to attribute them to specific command. So I'd suggest to submit logs from make without -j. But in this case it's possible to tell what's the problem, because all errors point in same direction, assembly modules. One can also see that commands generating them are not suitable to gcc112. Specifically perlasm_scheme, it should be linux64le for gcc112. Output suggests that you've executed ./Configure linux-ppc64 manually. When you do so, you become accountable for choosing correct target, and correct target for gcc112 is linux-ppc64le. I'd suggest to stick with ./config.

Output suggests that you've executed ./Configure linux-ppc64 manually.

Yes. That's because configure detected again. It detected 32-bit platform, not a 64-bit one.

It detected 32-bit platform, not a 64-bit one.

There is no 32-bit option on ppc64le platform, and gcc112 is detected as linux-ppc64le by ./config. As for the rest, get less emotional, collect your thoughts, and make suggestion :-)

There is no 32-bit option on ppc64le platform

.... but @noloader isn't talking about ppc64le
Now, @noloader, have you possibly set the environment variable KERNEL_BITS?  If you have and the value is 32, then you have effectly told ./config that you do want 32-bit platform.

Now, @noloader, have you possibly set the environment variable KERNEL_BITS?

Never mind that question...  I misread the code.  It's true that ./config defaults to 32-bit, i.e. linux-ppc...  Setting KERNEL_BITS=64 makes it choose linux-ppc64 instead.

(and mind you, I agree that it seems weird to default to a 32-bit build on a 64-bit platform.  It's not intuitive)

.... but @noloader isn't talking about ppc64le

Yes, he does. gcc112 is ppc64le system and assertion that it was detected as 32-bit is unsubstantiated. What is more likely to happen is that he got angry with big-endian system [where 32-bit would indeed be offered as default] and copy-n-pasted config command between two systems...

(and mind you, I agree that it seems weird to default to a 32-bit build on a 64-bit platform. It's not intuitive)

One can blame OpenSSL for being overly conservative, nothing wrong with that, blaming that is. I only suggest to put emotions aside.


{var} macro does not allow missing $ sign.

{var test = 0} is a valid code in latte. $ sign is not necessary here.

Ah, I found it.
https://forum.nette.org/cs/33029-latte-verze-2-7-typy-naseptavani-a-sandbox-rezim#p208282


[filer] sync/backup/replicate exclude directories to sync on filer

What problem are we solving?
There are buckets of many temporary files that do not need to be synchronized or backup
How are we solving the problem?
Add option with exclude directories to sync on filer
Checks

[ok] I have added unit tests if possible.
[ok] I will add related wiki document changes and link to this PR after merging.

PR rolled out to a test cluster