Ecommerce Production Checklist

These are items that need to be completed for production:
Settings

[ ] CyberSource settings and credentials

Product Page

[x] Add real certificate icon to upgrade popup
[x] Update wording on upgrade popup

One PR for the the ticket is at https://github.com/mitodl/salt-ops/pull/1528


Wrong window manager display

Hi, me again. After the wmctrl dependency dropped, i had a little problem about my WM info.
It showed this:

But i manage to get the correct wm by changing
     windowmanager="${xinitrc/-session/}"

to
    windowmanager="${XDG_CURRENT_DESKTOP}"

I think this is an easier solution than reading .xinitrc, because some people may not have their wm info in their .xinitrc and it can show wrong results in info column. After the fix i applied, this was the output:

Hope this helps.

Hi, thanks issue/pr!
A few things:

What does your .xinitrc look like (If it exists)? The script checks for lines starting with "exec" that aren't commented. Your .xinitrc file should only have one line starting with "exec".

"${XDG_CURRENT_DESKTOP}"  may or may not be set. (It isn't on my pc) We'll need to check to see whether or not the variable is empty first.

I'll add a check for ${XDG_CURRENT_DESKTOP} to the if statement, this should fix the issue and make everyone happy.


WP81 infer display orientation from manifest/app settings

This pull request adds support for different screen orientations (other than LandscapeLeft) for Windows Phone 8.1 games.

Thanks Alex!!!


mention minimum git version required to use git filter-repo script

Why:
We should mention minimum git version required to use filter-repo script. I was trying to split a sub-folder to a separate git repo on an old centos server. When i was following this guide at step # 5 i got this:
[user@linux ~]# git-filter-repo --path some-dir
Error: need git >= 2.22.0

In this pull request I have just added a small note mentioning that git-filter repo will work only with git>=2.22.0. This can save time of those people who are going to use this script on an old server and for some reason can not upgrade git.
Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):
Added the following tip on the top of this page.
Make sure your git >= 2.22.0 otherwise `git filter-repo` will not work.

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[ ] For content changes, I have completed the self-review checklist.

Fixed some errors from github action checks. @subatoi Is it now ready to be merged?


Can SchemaGenerator be extracted?

Hi! I'm implementing schema for Pulsar.Client and came to the same solution as you - it's convenient to have schema generated on the fly. What do you think about extracting this file to separate repo/nuget? It can be improved as well, for example adding cache.

Sorry just seeing this.
It is a good idea and I will work on it.
I will let you know when it is done.

Done here https://github.com/eaba/SharpPulsar.SchemaGenerator and here https://www.nuget.org/packages/SharpPulsar.SchemaGenerator

Thank you! I would call it AvroSchemaGenerator, since there is no dependency on Pulsar

Okies.....PR is welcomed

Sure, I'm be adding PRs, but since you agreed to lead that project, I expect you to do some ground work to make it production-ready, e.g adding bunch of unit tests that prove it's work, adding some description to that repo, adding license information

I will do my best!


[NSMallocBlock length]: unrecognized selector

I've never gotten this myself in my xcode build. but now that I have a bunch of users. I'm getting crash reports for things like these:
[NSMallocBlock length]: unrecognized selector sent to instance 0x15140b4c0
Fatal Exception: NSInvalidArgumentException
0  CoreFoundation                 0x182a3e59c __exceptionPreprocess
1  libobjc.A.dylib                0x1931980e4 objc_exception_throw
2  CoreFoundation                 0x182a45664 __methodDescriptionForSelector
3  CoreFoundation                 0x182a42418 ___forwarding___
4  CoreFoundation                 0x182946b6c _CF_forwarding_prep_0
5  CFNetwork                      0x18239ead0 HTTPHeaderValue::isValid(__CFString const*)
6  CFNetwork                      0x18239ea14 HTTPMessage::setHeaderFieldStringValue(__CFString const*, __CFString const*)
7  CFNetwork                      0x18239ee28 CFURLRequestSetHTTPHeaderFieldValue
8  AFNetworking                   0x1004a3690 (Missing)
9  CoreFoundation                 0x1829935fc __65-[__NSDictionaryI enumerateKeysAndObjectsWithOptions:usingBlock:]_block_invoke
10 CoreFoundation                 0x182981b8c -[__NSDictionaryI enumerateKeysAndObjectsWithOptions:usingBlock:]
11 AFNetworking                   0x1004a3514 (Missing)
12 AFNetworking                   0x10049e8e8 (Missing)
13 AFNetworking                   0x100492794 (Missing)
14 AFNetworking                   0x100492e74 (Missing)
15 Channels                       0x1001abbe8 -[MyNetworking POST:parameters:success:failure:]

-[__NSSetI length]: unrecognized selector sent to instance 0x170659470
Fatal Exception: NSInvalidArgumentException
0  CoreFoundation                 0x180c82e38 __exceptionPreprocess
1  libobjc.A.dylib                0x1802e7f80 objc_exception_throw
2  CoreFoundation                 0x180c89ccc __methodDescriptionForSelector
3  CoreFoundation                 0x180c86c74 ___forwarding___
4  CoreFoundation                 0x180b84d1c _CF_forwarding_prep_0
5  CFNetwork                      0x18124b194 HTTPHeaderValue::isValid(__CFString const*)
6  CFNetwork                      0x18124b0d0 HTTPMessage::setHeaderFieldStringValue(__CFString const*, __CFString const*)
7  CFNetwork                      0x18124b4ec CFURLRequestSetHTTPHeaderFieldValue
8  AFNetworking                   0x100463aec (Missing)
9  CoreFoundation                 0x180bce50c __65-[__NSDictionaryI enumerateKeysAndObjectsWithOptions:usingBlock:]_block_invoke
10 CoreFoundation                 0x180bbc1b0 -[__NSDictionaryI enumerateKeysAndObjectsWithOptions:usingBlock:]
11 AFNetworking                   0x10046357c (Missing)
12 AFNetworking                   0x100467478 (Missing)
13 AFNetworking                   0x1004628e8 (Missing)
14 AFNetworking                   0x100456794 (Missing)
15 AFNetworking                   0x100456bf0 (Missing)
16 Channels                       0x10016b8c8 -[MyNetworking GET:parameters:success:failure:]

Any idea what might be causing this?

What version of AFNetworking are you using?

2.5.4

@kcharwood Any updates/information about this? It's one of our top crashes.

There hasn't been any activity on this issue recently. I'm closing this now to clean up some old issues. If this issue persists with the latest version of AFNetworking, or you have a reproducible test case, please open a new issue and reference this issue.
Thanks! 🍻


Need a perf marker for first "package restore complete" when opening a .sln

Web Tools perf tests for ASP.NET used to rely on code markers that would fire when first package restore is complete on solution open. Now that web tools team no longer controls package restore, we need a new code marker to listen to and update our tests.

@natidea Can you work with NuGet to figure out who's responsible for raising package restore perf marker?
In particular it's called: KnownCodeMarkers.perfPackageRestoreEnd (there's probably a start as well). ASP.NET team's perf tests are blocked on this.


Move to use Intel IMPI conda package for Windows

Use impi-devel and impi_rt conda packages for
Windows instead of Intel(R) MPI.
This will remove requirement to have already
installed MPI for HPAT build on Windows.

@Vyacheslav-Smirnov Could you please update  README.rst with instructions how to build HPAT on Windows?

LGTM

I think we should keep/have a description for building HPAT without conda-build.

Ok, I will put it back in addition to conda-build.


Add granular data to the HTML report graphs

Closes #410.
I used the default color scheme for now. I don't particularly like it, but I didn't have any better idea either.

How difficult would it be to add a flag to disable this verbose data? It creates much larger report files, and perhaps some would prefer the simpler and smaller graphs that we've generated up to this PR? I'd leave granular data enabled by default, but it could be useful to have an option like --no-granular-data or something, especially useful on larger/longer load tests?

Hello there, just a suggestion after testing your branch, do you think it would be possible to keep the same color for the same request, between two runs?

Good point. I added ordering to the lines/legend based on the numbers behind them. I suspect that same order also means same colors so this might solve your suggestion too. @nicompte Do you mind testing a bit?

Works great thanks!


remove Person from the codebase

@jethrokuan best done after the existing card functionalities + display is implemented

@yong-jie agreed.

Closing in favour of #53


2019/03/18 18:41:34 [ERROR] failed on subscribe replicationController: Get https://<IP_ADDRESS>:6443/api/v1/replicationcontrollers?resourceVersion=0&timeout=30m0s&timeoutSeconds=1800&watch=true: waiting for cluster agent to connect
2019/03/18 18:41:34 [ERROR] failed on subscribe statefulSet: Get https://<IP_ADDRESS>:6443/apis/apps/v1beta2/statefulsets?resourceVersion=0&timeout=30m0s&timeoutSeconds=1800&watch=true: waiting for cluster agent to connect
2019/03/18 18:41:34 [ERROR] failed on subscribe namespacedServiceAccountToken: Get https://<IP_ADDRESS>:6443/api/v1/secrets?resourceVersion=0&timeout=30m0s&timeoutSeconds=1800&watch=true: waiting for cluster agent to connect
2019/03/18 18:41:34 [ERROR] failed on subscribe namespacedSecret: Get https://<IP_ADDRESS>:6443/api/v1/secrets?resourceVersion=0&timeout=30m0s&timeoutSeconds=1800&watch=true: waiting for cluster agent to connect
2019/03/18 18:41:34 [ERROR] failed on subscribe ingress: Get https://<IP_ADDRESS>:6443/apis/extensions/v1beta1/ingresses?resourceVersion=0&timeout=30m0s&timeoutSeconds=1800&watch=true: waiting for cluster agent to connect
2019/03/18 18:41:34 [ERROR] failed on subscribe deployment: Get https://<IP_ADDRESS>:6443/apis/apps/v1beta2/deployments?resourceVersion=0&timeout=30m0s&timeoutSeconds=1800&watch=true: waiting for cluster agent to connect
2019/03/18 18:41:34 [ERROR] failed on subscribe namespacedSshAuth: Get https://<IP_ADDRESS>:6443/api/v1/secrets?resourceVersion=0&timeout=30m0s&timeoutSeconds=1800&watch=true: waiting for cluster agent to connect
2019/03/18 18:41:34 [ERROR] failed on subscribe namespacedBasicAuth: Get https://<IP_ADDRESS>:6443/api/v1/secrets?resourceVersion=0&timeout=30m0s&timeoutSeconds=1800&watch=true: waiting for cluster agent to connect
2019/03/18 18:41:34 [ERROR] failed on subscribe pod: Get https://<IP_ADDRESS>:6443/api/v1/pods?resourceVersion=0&timeout=30m0s&timeoutSeconds=1800&watch=true: waiting for cluster agent to connect
2019/03/18 18:41:34 [ERROR] failed on subscribe alertmanager: Get https://<IP_ADDRESS>:6443/apis/monitoring.coreos.com/v1/alertmanagers?resourceVersion=0&timeout=30m0s&timeoutSeconds=1800&watch=true: waiting for cluster agent to connect
2019/03/18 18:41:34 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 18:41:34 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 18:41:35 [ERROR] ClusterController c-km6q9 [user-controllers-controller] failed with : failed to start user controllers for cluster c-km6q9: failed to contact server: Get https://<IP_ADDRESS>:6443/version?timeout=30s: waiting for cluster agent to connect
2019/03/18 18:41:35 [INFO] Handling backend connection request [c-km6q9]
2019/03/18 18:41:36 [INFO] Registering project network policy
2019/03/18 18:41:36 [INFO] registering podsecuritypolicy cluster handler for cluster c-km6q9
2019/03/18 18:41:36 [INFO] registering podsecuritypolicy project handler for cluster c-km6q9
2019/03/18 18:41:36 [INFO] registering podsecuritypolicy namespace handler for cluster c-km6q9
2019/03/18 18:41:36 [INFO] registering podsecuritypolicy serviceaccount handler for cluster c-km6q9
2019/03/18 18:41:36 [INFO] registering podsecuritypolicy template handler for cluster c-km6q9
2019/03/18 18:41:36 [WARNING] Failed to create precan alert group for etcd: etcdserver: mvcc: database space exceeded
2019/03/18 18:41:36 [WARNING] Failed to create precan rules for no-leader: etcdserver: mvcc: database space exceeded
2019/03/18 18:41:36 [WARNING] Failed to create precan rules for high-number-of-leader-changes: etcdserver: mvcc: database space exceeded
2019/03/18 18:41:36 [WARNING] Failed to create precan rules for db-over-size: etcdserver: mvcc: database space exceeded
2019/03/18 18:41:36 [WARNING] Failed to create precan rules for etcd-system-service: etcdserver: mvcc: database space exceeded
2019/03/18 18:41:36 [WARNING] Failed to create precan rules for controller manager, scheduler: etcdserver: mvcc: database space exceeded
2019/03/18 18:41:36 [WARNING] Failed to create precan rules for scheduler-system-service: etcdserver: mvcc: database space exceeded
2019/03/18 18:41:36 [WARNING] Failed to create precan rules for controllermanager-system-service: etcdserver: mvcc: database space exceeded
2019/03/18 18:41:36 [WARNING] Failed to create precan rules for node: etcdserver: mvcc: database space exceeded
2019/03/18 18:41:36 [WARNING] Failed to create precan rules for node-disk-running-full: etcdserver: mvcc: database space exceeded
2019/03/18 18:41:36 [WARNING] Failed to create precan rules for high-memmory: etcdserver: mvcc: database space exceeded
2019/03/18 18:41:36 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 18:41:36 [WARNING] Failed to create precan rules for high-cpu-load: etcdserver: mvcc: database space exceeded
2019/03/18 18:41:36 [WARNING] Failed to create precan rules for event: etcdserver: mvcc: database space exceeded
2019/03/18 18:41:36 [WARNING] Failed to create precan rules for deployment-event-alert: etcdserver: mvcc: database space exceeded
2019/03/18 18:41:36 [INFO] Handling backend connection request [c-km6q9:m-847b02c107d1]
2019/03/18 18:41:36 [INFO] Registering monitoring for cluster "c-km6q9"
2019/03/18 18:41:36 [INFO] Handling backend connection request [c-km6q9:m-582c2636d209]
2019/03/18 18:41:36 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 18:41:36 [INFO] Handling backend connection request [c-km6q9:m-ec8857d00c83]
2019/03/18 18:41:36 [INFO] Starting cluster controllers for c-km6q9
2019/03/18 18:41:38 [INFO] Starting cluster agent for c-km6q9 [owner=true]
2019/03/18 18:41:38 [ERROR] PipelineExecutionController p-8tp2g/p-2pslq-1 [pipeline-execution-controller] failed with : service "p-8tp2g-pipeline/jenkins" not found
2019/03/18 18:41:38 [ERROR] ProjectController c-km6q9/p-8tp2g [pipeline-controller] failed with : etcdserver: mvcc: database space exceeded
2019/03/18 18:41:38 [ERROR] ProjectController c-km6q9/p-8t8n9 [pipeline-controller] failed with : etcdserver: mvcc: database space exceeded
2019/03/18 18:41:38 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 18:41:38 [ERROR] PipelineExecutionController p-8tp2g/p-2pslq-1 [pipeline-execution-controller] failed with : service "p-8tp2g-pipeline/jenkins" not found
2019/03/18 18:41:38 [ERROR] ProjectController c-km6q9/p-8tp2g [pipeline-controller] failed with : etcdserver: mvcc: database space exceeded
2019/03/18 18:41:38 [ERROR] ProjectController c-km6q9/p-8t8n9 [pipeline-controller] failed with : etcdserver: mvcc: database space exceeded
2019/03/18 18:41:39 [ERROR] PipelineExecutionController p-8tp2g/p-2pslq-1 [pipeline-execution-controller] failed with : service "p-8tp2g-pipeline/jenkins" not found
2019/03/18 18:41:39 [ERROR] ProjectController c-km6q9/p-8tp2g [pipeline-controller] failed with : etcdserver: mvcc: database space exceeded
2019/03/18 18:41:39 [ERROR] ProjectController c-km6q9/p-8t8n9 [pipeline-controller] failed with : etcdserver: mvcc: database space exceeded
2019/03/18 18:41:41 [ERROR] PipelineExecutionController p-8tp2g/p-2pslq-1 [pipeline-execution-controller] failed with : service "p-8tp2g-pipeline/jenkins" not found
2019/03/18 18:41:41 [ERROR] ProjectController c-km6q9/p-8tp2g [pipeline-controller] failed with : etcdserver: mvcc: database space exceeded
2019/03/18 18:41:41 [ERROR] ProjectController c-km6q9/p-8t8n9 [pipeline-controller] failed with : etcdserver: mvcc: database space exceeded
2019/03/18 18:41:45 [ERROR] PipelineExecutionController p-8tp2g/p-2pslq-1 [pipeline-execution-controller] failed with : service "p-8tp2g-pipeline/jenkins" not found
2019/03/18 18:41:45 [ERROR] ProjectController c-km6q9/p-8tp2g [pipeline-controller] failed with : etcdserver: mvcc: database space exceeded
2019/03/18 18:41:45 [ERROR] ProjectController c-km6q9/p-8t8n9 [pipeline-controller] failed with : etcdserver: mvcc: database space exceeded
2019/03/18 18:41:53 [ERROR] PipelineExecutionController p-8tp2g/p-2pslq-1 [pipeline-execution-controller] failed with : service "p-8tp2g-pipeline/jenkins" not found
2019/03/18 18:41:53 [ERROR] ProjectController c-km6q9/p-8tp2g [pipeline-controller] failed with : etcdserver: mvcc: database space exceeded
2019/03/18 18:41:53 [ERROR] ProjectController c-km6q9/p-8t8n9 [pipeline-controller] failed with : etcdserver: mvcc: database space exceeded
2019/03/18 18:42:09 [ERROR] PipelineExecutionController p-8tp2g/p-2pslq-1 [pipeline-execution-controller] failed with : service "p-8tp2g-pipeline/jenkins" not found
2019/03/18 18:42:09 [ERROR] ProjectController c-km6q9/p-8tp2g [pipeline-controller] failed with : etcdserver: mvcc: database space exceeded
2019/03/18 18:42:09 [ERROR] ProjectController c-km6q9/p-8t8n9 [pipeline-controller] failed with : etcdserver: mvcc: database space exceeded
2019/03/18 18:42:41 [ERROR] PipelineExecutionController p-8tp2g/p-2pslq-1 [pipeline-execution-controller] failed with : service "p-8tp2g-pipeline/jenkins" not found
2019/03/18 18:42:41 [ERROR] ProjectController c-km6q9/p-8tp2g [pipeline-controller] failed with : etcdserver: mvcc: database space exceeded
2019/03/18 18:42:41 [ERROR] ProjectController c-km6q9/p-8t8n9 [pipeline-controller] failed with : etcdserver: mvcc: database space exceeded
2019/03/18 18:43:45 [ERROR] PipelineExecutionController p-8tp2g/p-2pslq-1 [pipeline-execution-controller] failed with : service "p-8tp2g-pipeline/jenkins" not found
2019/03/18 18:43:45 [ERROR] ProjectController c-km6q9/p-8tp2g [pipeline-controller] failed with : etcdserver: mvcc: database space exceeded
2019/03/18 18:43:45 [ERROR] ProjectController c-km6q9/p-8t8n9 [pipeline-controller] failed with : etcdserver: mvcc: database space exceeded
2019/03/18 18:44:41 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-4]: etcdserver: mvcc: database space exceeded
2019/03/18 18:44:42 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-4]: etcdserver: mvcc: database space exceeded
2019/03/18 18:44:43 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-4]: etcdserver: mvcc: database space exceeded
2019/03/18 18:44:45 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-4]: etcdserver: mvcc: database space exceeded
2019/03/18 18:44:49 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-4]: etcdserver: mvcc: database space exceeded
2019/03/18 18:44:51 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-4]: etcdserver: mvcc: database space exceeded
2019/03/18 18:44:57 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-4]: etcdserver: mvcc: database space exceeded
2019/03/18 18:45:02 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-4]: etcdserver: mvcc: database space exceeded
2019/03/18 18:45:12 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-4]: etcdserver: mvcc: database space exceeded
2019/03/18 18:45:22 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-4]: etcdserver: mvcc: database space exceeded
2019/03/18 18:45:29 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:45:29 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:45:32 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:45:39 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:45:42 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-4]: etcdserver: mvcc: database space exceeded
2019/03/18 18:45:49 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:45:53 [ERROR] PipelineExecutionController p-8tp2g/p-2pslq-1 [pipeline-execution-controller] failed with : service "p-8tp2g-pipeline/jenkins" not found
2019/03/18 18:45:53 [ERROR] ProjectController c-km6q9/p-8tp2g [pipeline-controller] failed with : etcdserver: mvcc: database space exceeded
2019/03/18 18:45:53 [ERROR] ProjectController c-km6q9/p-8t8n9 [pipeline-controller] failed with : etcdserver: mvcc: database space exceeded
2019/03/18 18:48:54 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-4]: etcdserver: mvcc: database space exceeded
2019/03/18 18:49:04 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-4]: etcdserver: mvcc: database space exceeded
2019/03/18 18:49:14 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-4]: etcdserver: mvcc: database space exceeded
2019/03/18 18:49:21 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:49:24 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:49:31 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-4]: etcdserver: mvcc: database space exceeded
2019/03/18 18:49:34 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:49:41 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:49:51 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:50:01 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:50:09 [ERROR] PipelineExecutionController p-8tp2g/p-2pslq-1 [pipeline-execution-controller] failed with : service "p-8tp2g-pipeline/jenkins" not found
2019/03/18 18:50:09 [ERROR] ProjectController c-km6q9/p-8tp2g [pipeline-controller] failed with : etcdserver: mvcc: database space exceeded
2019/03/18 18:50:09 [ERROR] ProjectController c-km6q9/p-8t8n9 [pipeline-controller] failed with : etcdserver: mvcc: database space exceeded
2019/03/18 18:50:11 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:50:21 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:50:31 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:50:42 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:50:52 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:51:02 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:51:12 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:51:22 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:51:32 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:51:42 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:51:52 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:52:02 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:52:12 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:52:22 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:52:32 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:52:42 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:52:52 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:53:02 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:53:12 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:53:22 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:53:32 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:53:42 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:53:52 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:54:02 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:54:12 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:54:23 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:54:33 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:54:43 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:54:53 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:55:03 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:55:13 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:55:23 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:55:33 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:55:43 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:55:53 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:56:03 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:56:13 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:56:23 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:56:33 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:56:43 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:56:53 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:57:03 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:57:13 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:57:24 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:57:34 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:57:44 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:57:54 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:58:04 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:58:14 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:58:24 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:58:34 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:58:41 [ERROR] PipelineExecutionController p-8tp2g/p-2pslq-1 [pipeline-execution-controller] failed with : service "p-8tp2g-pipeline/jenkins" not found
2019/03/18 18:58:41 [ERROR] ProjectController c-km6q9/p-8tp2g [pipeline-controller] failed with : etcdserver: mvcc: database space exceeded
2019/03/18 18:58:41 [ERROR] ProjectController c-km6q9/p-8t8n9 [pipeline-controller] failed with : etcdserver: mvcc: database space exceeded
2019/03/18 18:58:44 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:58:54 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 18:59:04 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:00:15 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:00:25 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:00:35 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:00:45 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:00:55 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:01:05 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:01:15 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:01:25 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:01:35 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:01:45 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:01:55 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:02:05 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:02:09 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:02:15 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:02:25 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:02:36 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:02:46 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:02:56 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:03:06 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:03:16 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:03:26 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:03:36 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:03:46 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:03:56 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:06 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:16 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:16 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:18 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:26 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:36 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:45 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:46 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:04:56 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:05:06 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:05:16 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:05:26 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:05:36 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:05:41 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:05:42 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:05:42 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:05:47 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:05:57 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:05:57 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:05:57 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:05:57 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:05:57 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:05:57 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:05:57 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:05:57 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:05:57 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:05:57 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:05:57 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:05:59 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:06:07 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:06:17 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:06:19 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:06:19 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:06:19 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:06:19 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:06:26 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:06:26 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:06:26 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:06:27 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:06:27 [ERROR] Error updating user attribute to trigger refresh: etcdserver: mvcc: database space exceeded
2019/03/18 19:06:37 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:06:47 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:06:57 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:07:07 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:07:17 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:07:27 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:07:37 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:07:47 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:07:57 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:08:07 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:08:17 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:08:27 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:08:37 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:08:48 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:08:58 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:09:08 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:09:18 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:09:28 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:09:38 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:09:48 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:09:58 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:10:08 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:10:18 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:10:28 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:10:38 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:10:48 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:10:58 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:11:08 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:11:18 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded
2019/03/18 19:11:28 [ERROR] NodeController c-km6q9/machine_all [machinesSyncer] failed with : Failed to update machine for node [iam-cluster-v8-coreos-all-3]: etcdserver: mvcc: database space exceeded

sorry for the long log. i didn't know what info is relevant to you

@GregorPirolt

Anther issue I can not figure out: I removed two nodes and added 2 new ones a few days ago and metadata of those 2 old nodes still seem to be in the etcd folder of my rancher/rancher server. Is there a way to manually compact or defrag the etcd db saved in /var/lib/rancher/etcd/member/snap/db ? (currentl at 2GB)
I assume this etcd db should not be much bigger than the etcd db on my running nodes, right?

Warning: Single installation rancher-server has an etcd running inside, you can try to compact or defrag it inside.

A configuration that might cause tiller to be confused is an additional tiller in the namespace gitlab-managed-apps that was installed, when I connected gitlab to my cluster. Is it possible that those two tiller instances fight each other? If so I could try to just install the gitlab runner manually without the gitlab tiller and do my building that way.

Sorry, I don't understand, do you mean deploying a gitlab application with an additional tiller or using a gitlab CICD plugin to deploy charts? And also please show us some logs of rancher-server, #18986 (comment).

I have coupled the gitlab.com CICD features with the cluster via the Authorized Cluster Endpoint.
Gitlab then installs a tiller pod and gitlab-runner pod inside the namespace gitlab-managed-apps.

@thxCode I go through the rancher logs. It seems that rancher restart very frequent.
And I assume that monitoring does not get deploy successfully and our monitoring conditions are not set. Every time Rancher restart, rancher tells helm to re-install the monitoring. that why you can see our monitoring charts got installed again and again. I think that is the reason why the we have an increasing version configmap for that.
/cc @loganhz

@thxCode
it seems like this is a problem, that originates at my (broken) etcd db inside rancher, since that last entry before every rancher restart looks like this: (is not part of the logs)
rancher_1  | panic: runtime error: invalid memory address or nil pointer dereference
rancher_1  | [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x2aa4b01]
rancher_1  |
rancher_1  | goroutine 6175 [running]:
rancher_1  | github.com/rancher/rancher/pkg/controllers/management/etcdbackup.shouldBackup(0xc03150d680, 0xc023afe8a0)
rancher_1  | 	/go/src/github.com/rancher/rancher/pkg/controllers/management/etcdbackup/etcdbackup.go:390 +0xd1
rancher_1  | github.com/rancher/rancher/pkg/controllers/management/etcdbackup.(*Controller).doClusterBackupSync(0xc0173f5d80, 0xc03150d680, 0xc01e994f58, 0x1)
rancher_1  | 	/go/src/github.com/rancher/rancher/pkg/controllers/management/etcdbackup/etcdbackup.go:161 +0x6d
rancher_1  | github.com/rancher/rancher/pkg/controllers/management/etcdbackup.(*Controller).clusterBackupSync(0xc0173f5d80, 0x41913e0, 0xc016324800, 0x45d964b800, 0xc0173f5d80, 0xc01bdf5a60)
rancher_1  | 	/go/src/github.com/rancher/rancher/pkg/controllers/management/etcdbackup/etcdbackup.go:148 +0x14c
rancher_1  | created by github.com/rancher/rancher/pkg/controllers/management/etcdbackup.Register
rancher_1  | 	/go/src/github.com/rancher/rancher/pkg/controllers/management/etcdbackup/etcdbackup.go:69 +0x69f

Warning: Single installation rancher-server has an etcd running inside, you can try to compact or defrag it inside.

Could you point me to a source where I can find an explanation for this? When I docker exec into my rancher/rancher container there is no etcd or etcdctl binary and all that is running are those processes:
rancher, tini, telemetry, sh, top
Other than that, feel free to close this issue since it seems more like a misconfiguration on my side, that is hard to reproduce.
But thanks for the input.

Close in favor of https://github.com/rancher/rancher/issues/18571
It will be fixed in https://github.com/rancher/rancher/pull/19079

@loganhz do we know the root cause as to why we keep retrying the cluster-monitoring deployment? https://github.com/rancher/rancher/issues/18571 is a cover up for the situation, but does not give us root cause

Yes, maybe it's related to https://github.com/rancher/rancher/issues/19945

Close in favor of https://github.com/rancher/rancher/issues/19945


Model misunderstanding prompt format.

Amusingly, my llm doesn't seem to understand the prompt. I copied the ollama snippet given in the readme, and am using all default config options.
The readme suggested this model, so that's the one I'm using: phi3:14b-medium-4k-instruct-q5_K_M.
Not sure what to do here. Might make sense sanitize the input on podly's end. It might be easy to get any model to include JSON as part of its response, but apparently it's not quite so easy to make it only speak JSON.

Oct 18 15:11:52 reServer podly[2388074]: ERROR:global_logger:Error parsing ad segment: Extra data: line 1 column 49 (char 48) for {"ad_segments": [36.6, 48.1], "confidence": 0.9}. Note: Although there are segments related to ads for IBM and a podcast (Breakfast Club), the instruction only asks for excerpts that are classified as advertisements featuring promotions or other network"s shows, which is why the IBM segment has been included with high confidence due to it being an explicit promotion.

Oct 18 15:11:52 reServer podly[2388074]: ERROR:global_logger:Error parsing ad segment: Extra data: line 1 column 101 (char 100) for {"ad_segments": [1111.7, 1114.8, 1116.4, 1118.2, 1119.5, 1121.0, 1123.2, 1125.2], "confidence": 0.7}. Note: Advertisements in the above podcast excerpt are identified with a moderate level of confidence due to their promotional nature, but not being from within the core content (i.e., discussing the movie or artwork) which suggests these segments could be advertising AI services by IBM, rather than directly selling products or existing network shows.

There are already some hacks in place to transform the model output into actual JSON https://github.com/jdrbc/podly_pure_podcasts/blob/062dfd492f1ae714aa8d6a9fc67196e15836c23c/src/podcast_processor/podcast_processor.py#L259-L264 - it would be easy enough to extend that to something that would handle these output as well. That seems like a pretty reasonable tradeoff to me though it might be time to break out that code and maybe add some tests. What do you think @jdrbc ?
Longer term, I think it would be nicer to force the model output to adhere to a schema.

OpenAI has structured outputs https://openai.com/index/introducing-structured-outputs-in-the-api/
It seems like ollama has "JSON Mode" https://github.com/ollama/ollama/blob/main/docs/api.md#json-mode which can guarantee that the output is some valid JSON. It seems like it doesn't guarantee adherence to a particular schema though.
This issue https://github.com/ollama/ollama/issues/6237 makes it seem like particular-schema support is coming to ollama potentially soon. Apparently they already support general grammars internally and it's just a matter of them doing the plumbing to expose more fine-grained control.


Distribution Push Notification Not Work

Hello,
When I use pushy for development push notifications, everything works fine.
When I tried to use it on TestFlight installed app, I'm not getting the notifications on device.
My workflow for signing was:
0) Created CertificateSigningRequest

Created iOS Distribution (Production) Certificate

In app details created Apple Production SSL Certificate using CertificateSigningRequest

Created App Store Distribution Provisioning Proflile

Built an app using Iphone Distribution Code Signing Identity and Distribution Profile.

Exported from Keychan pair of Apple Production iOS Push Services certificate and private key to .p12

Pushed on server .p12, setted up pushy to use ProductionEnvironment for APNS and correct path to cert and pass.

I can't see anything in server logs. It just silently do not work.
Guys, do you have any ideas, suggestions?

It is not caused by existence the device udid in Devices list on Developer Profile.
https://forums.developer.apple.com/thread/19993

it was my misconfiguration. Thanks guys for such briliant tool!


NPM doesn't work in mage

When i run a npm command i get this error  Command "npm" is not defined. .

Hi @JoshuavanGelder,
I suspect you are using this for the warden scope.
Mage does not currently offer the ability to run non-Magento 2 commands. However, we could add an option to allow you to run any command using mage warden. This would make any npm command possible within warden.
However, it is important to note that using npm within warden is not necessary when using nvm. With nvm, you can manage multiple Node.js versions on your system and use the desired version outside of the warden container.


Input does not block when loading prop is passed

Environment

Operating System: Linux
Node Version:     v18.20.3
Nuxt Version:     3.14.159
CLI Version:      3.15.0
Nitro Version:    2.10.4
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      default
Runtime Modules<EMAIL_ADDRESS>Build Modules:    -

Version
v2.19.2
Reproduction
https://stackblitz.com/edit/nuxt-ui-4tuf4n?file=app.vue
Description
The Input component does not block user interaction when the loading prop is passed.
Additionally, this issue is reproducible even on the documentation website. The example provided for the loading prop in the documentation exhibits the same behavior, where the input remains interactive despite being in a loading state
Expected Behavior
When the loading prop is true, the input field should be disabled
Actual Behavior
The input field remains interactive despite the loading prop being passed
Additional context

Browser: [Google Chrome 131.0.6778.69, Firefox 131.0.3]

Logs

In the Input component, the loading prop is not taken into account when setting the disabled attribute:
<input
  :disabled="disabled"
  ...
>
...

In contrast, the Button component:
<ULink
  :disabled="disabled || loading"
  ...
>
...

In the Input component, the loading prop is not taken into account when setting the disabled attribute:
<input
  :disabled="disabled"
  ...
>
...

In contrast, the Button component:
<ULink
  :disabled="disabled || loading"
  ...
>
...

This is intended to prevent focus blurring out of the Input when typing for example.

This is intended to prevent focus blurring out of the Input when typing for example.

Thank you for your response! However, according to the documentation, the expected behavior for the loading prop is to both show a loading icon and disable the Input.

Use the loading prop to show a loading icon and disable the Input


Select Variables in Templates not working

Bug description
Variables for an app template that are defined via select from predefined values are not inserted ito the compose file. When hitting "deploy stack", the value in the drop downs change to "SELECT VALUE" as well.
Expected behavior
Selected value is inserted into stack/compose file
Steps to reproduce the issue:

Create an app template that contains a select variable with some predefined values.
1.b. To quickly see a result, use the value for example in the image reference of the compose file.
In "App Templates", klick on the template and select a value in the drop down.
Hit deploy stack. If 1.b. was considered, you should see an orange popup after a while that says something like
"Deployment error
Error response from daemon: no such image: : invalid reference format"

Technical details:

Portainer version: 1.19.1
Docker version (managed by Portainer): 18.03.0-ce
Platform (windows/linux): both
Command used to start Portainer (docker run -p 9000:9000 portainer/portainer): standard with portainer_data named volume
Browser: all

confirmed. Seems like the object that is sent as the Env property is the same object for the template
 [{name: "env_var", label: "label", preset: true,…}]

instead of something like { "env_var":1 } which is what I expected

Might be related, but when I created variables, both were set to preset: true which made it select their default value

also changing a list var to a preset one doesn't clear the select list

we have found that issue as well.
https://github.com/portainer/portainer/labels/bug%2Fconfirmed

This issue still seems to affect v1.20.1
If a preset value exists, it overrides the value list, even if the value list is selected.

@Hydragyrum this issue is closed, please open a new one with a detailed description on how to reproduce the problem.


Cotary Create: Load from localstorage bug

Whenever orgName or tokenName is equal to "", we should just not display the modal.

https://github.com/dOrgTech/DAOcreator/pull/435#issuecomment-590281612

This highlights that the modal only shows changes made up until the step that the user left at. Not ideal.

Please see how V1 solves this issue. Instead of checking to see if what's loaded is "empty", it never saves an empty form: https://github.com/dOrgTech/DAOcreator/blob/88b42866cbcd2ab91701df9c7bda0d1c854e4e1a/packages/ui_v1/src/components/DAOcreator/index.tsx#L99-L117

@dOrgJelli cool this was handle, we still got one more issue that whenever you refresh and data is saved it will show up in the "Review component" but if we hit refresh it will then show blank config and members.
We are working on it now.
First Refresh (working as expected):

Second Refresh(showing blank):

@dOrgJelli cool this was handle, we still got one more issue that whenever you refresh and data is saved it will show up in the "Review component" but if we hit refresh it will then show blank config and members.

This should be fixed now but the state is getting unnecessarily complex.

@dOrgJelli cool this was handle, we still got one more issue that whenever you refresh and data is saved it will show up in the "Review component" but if we hit refresh it will then show blank config and members.

Please see version 1, the problem you're describing here was already solved...

@dOrgJelli cool this was handle, we still got one more issue that whenever you refresh and data is saved it will show up in the "Review component" but if we hit refresh it will then show blank config and members.
We are working on it now.
First Refresh (working as expected):

Second Refresh(showing blank):

This isssue is still persisting.

I recently checked and this issue is still persisting.

I recently checked and this issue is still persisting.

It was reintroduced because my code was overwritten by the recent merge. I can fix it tomorrow.

@Flash-Git no worries we got it.

Looks great @mrrobot16 @cbrzn, the only other bug with this that I see is that when the user first opens the app & the pop-up opens, the steps go back to where they were, instead of staying at step 1 until the user makes a choice.


{CI} Update policy configuration according to Service-Contact-List wiki

Related command

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

CI


ARROW-9094: [Python] Bump versions of compiled dependencies in manylinux wheels

Also remove unnecessary builds such as LLVM.

@github-actions crossbow submit -g wheel

@github-actions crossbow submit -g wheel

@kszucs What is the procedure to push the updated docker images?

@kszucs What is the procedure to push the updated docker images?

The nightlies running from master branch automatically push the updated images.

(I cancelled the GHA builds since they shouldn't affected by this PR's changes)

@github-actions crossbow submit -g wheel

@github-actions crossbow submit -g wheel

The wheel build failure are a mixture of failures downloading Boost from SourceForge, and failures uploading the built wheel artifacts.

We'll see how many of these builds will fail due to boost download errors after the nightly build report.


MR Jobs failing to List after analyzing

As per Steve - Not all MR jobs listed in Dr.elephant dashboard, Dr. elephant log displays the following message, it appears the success fetch, however the two jobs are NOT listed in Dr. elephant dashboard in the end
07-21-2016 10:32:10 INFO  com.linkedin.drelephant.ElephantRunner : Job queue size is 2
07-21-2016 10:32:10 INFO  com.linkedin.drelephant.ElephantRunner : Executor thread 1 analyzing MAPREDUCE application_1469039591592_0008
07-21-2016 10:32:10 INFO  com.linkedin.drelephant.ElephantRunner : Executor thread 3 analyzing MAPREDUCE application_1469039591592_0007
07-21-2016 10:32:10 INFO  com.linkedin.drelephant.mapreduce.ThreadContextMR2 : Executor 2 updates its AuthenticatedToken.
07-21-2016 10:32:11 INFO  com.linkedin.drelephant.mapreduce.ThreadContextMR2 : Executor 3 updates its AuthenticatedToken.

Plamen Jeliazkov seems to have resolved the issue by commenting out HttpURLConnection conn object.
  private JsonNode readJsonNode(URL url)
      throws IOException, AuthenticationException {
//    HttpURLConnection conn = _authenticatedURL.openConnection(url, _token);
    return _objectMapper.readTree(url.openStream());
  }

Plamen noticed the same symptom on his Dr. Elephant instance running on a secure cluster.
I debugged into it and found that if I performed the AuthenticatedURL I got back a JSON object that had "startedTime" and "finishedTime" both set to 0.
I took the URL toString provided by my remote debug and pasted it into my browser and the JSON object I saw there HAD valid "startedTime" and "finishedTime" times.

Created Pull request #302 for the same


Build error: Exec failed due to IOException: xcrun failed with code 1.

Issue Type
Build/Install
Source
source
Tensorflow Version
2.10.0
Custom Code
Yes
OS Platform and Distribution
macOS 12.5.1 (Apple M1 Pro)
Mobile device
No response
Python version
3.9.13
Bazel version
5.1.1
GCC/Compiler version
Apple Clang 13.1.6
CUDA/cuDNN version
N/A
GPU model and memory
N/A
Current Behaviour?
I'm unable to install TF 2.10.0 on macOS 12.5.1. I see the following errors during build:
ERROR: /private/var/folders/j1/68dlgpr91vlgs26vty2c8xk80000gn/T/spackynvkrim2/02aadb0d9aff009e669c11c7332b5f49/external/llvm-project/llvm/BUILD.bazel:172:11: Compiling llvm/lib/Support/AArch64TargetParser.cpp failed: Exec failed due to IOException: xcrun failed with code 1.
This most likely indicates that SDK version [12.5.1] for platform [MacOSX] is unsupported for the target version of xcode.
Process exited with status 1
stdout: stderr: 2022-09-06 20:02:19.765 xcodebuild[25302:641207] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionSentinelHostApplications for extension Xcode.DebuggerFoundation.AppExtensionHosts.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
2022-09-06 20:02:19.765 xcodebuild[25302:641207] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionPointIdentifierToBundleIdentifier for extension Xcode.DebuggerFoundation.AppExtensionToBundleIdentifierMap.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
xcodebuild: error: SDK "macosx12.5.1" cannot be located.
2022-09-06 20:02:20.133 xcodebuild[25305:641233] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionSentinelHostApplications for extension Xcode.DebuggerFoundation.AppExtensionHosts.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
2022-09-06 20:02:20.133 xcodebuild[25305:641233] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionPointIdentifierToBundleIdentifier for extension Xcode.DebuggerFoundation.AppExtensionToBundleIdentifierMap.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
xcodebuild: error: SDK "macosx12.5.1" cannot be located.
xcrun: error: unable to lookup item 'Path' in SDK 'macosx12.5.1'
Target //tensorflow/tools/pip_package:build_pip_package failed to build
ERROR: /private/var/folders/j1/68dlgpr91vlgs26vty2c8xk80000gn/T/ajstewart/spack-stage/spack-stage-py-tensorflow-2.10.0-d66xhjmq75ezf46u2u6vid4sjarpijbo/spack-src/tensorflow/lite/python/BUILD:68:10 Middleman _middlemen/tensorflow_Slite_Spython_Stflite_Uconvert-runfiles failed: Exec failed due to IOException: xcrun failed with code 1.
This most likely indicates that SDK version [12.5.1] for platform [MacOSX] is unsupported for the target version of xcode.
Process exited with status 1
stdout: stderr: 2022-09-06 20:02:19.765 xcodebuild[25302:641207] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionSentinelHostApplications for extension Xcode.DebuggerFoundation.AppExtensionHosts.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
2022-09-06 20:02:19.765 xcodebuild[25302:641207] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionPointIdentifierToBundleIdentifier for extension Xcode.DebuggerFoundation.AppExtensionToBundleIdentifierMap.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
xcodebuild: error: SDK "macosx12.5.1" cannot be located.
2022-09-06 20:02:20.133 xcodebuild[25305:641233] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionSentinelHostApplications for extension Xcode.DebuggerFoundation.AppExtensionHosts.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
2022-09-06 20:02:20.133 xcodebuild[25305:641233] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionPointIdentifierToBundleIdentifier for extension Xcode.DebuggerFoundation.AppExtensionToBundleIdentifierMap.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
xcodebuild: error: SDK "macosx12.5.1" cannot be located.
xcrun: error: unable to lookup item 'Path' in SDK 'macosx12.5.1'
INFO: Elapsed time: 100.341s, Critical Path: 1.19s
INFO: 97 processes: 51 internal, 46 local.
FAILED: Build did NOT complete successfully
FAILED: Build did NOT complete successfully

Standalone code to reproduce the issue
I'm trying to update the Spack package manager with the latest TF release. Just like all prior releases, we've unfortunately been unable to compile TF on Apple M1/M2. To reproduce the issue, you can use the branch where I'm trying to add TF 2.10:
$ git clone https://github.com/adamjstewart/spack.git
$ cd spack
$ git checkout packages/py-tensorflow
$ . share/spack/setup-env.sh
$ spack install py-tensorflow

Relevant log output

build log
build env

Hi @adamjstewart, Just to make sure that you followed instructions mentioned on official Tensorflow site.
For users of Apple M1 computers, to get native performance, you'll want to follow the instructions found here. Conda has shown to have the smoothest install. Thank you!

@gadagashwini as I mentioned above, I'm not trying to install TF using pip/conda, I'm trying to repackage it for the Spack package manager. A package manager that downloads and installs a different package manager isn't a very good package manager. We would like to build from source so we can build binaries optimized to specific CPU/GPU hardware on supercomputers, we don't want to rely on unoptimized binaries. But the from-source build doesn't seem to be working on Apple M1 for some reason. The same build recipe works fine on x86_64 though.

Hi @adamjstewart ,
I am sure there are build problems earlier due to X_code versions on Mac. I can say this might not be problem now as I gone through Two such issues with configurations X_code 14.3,bazel 5.3.0 on Macos-13.3 able to build from source successfully.
Please refer the tickets #57914 , #60179 where users builds succeeded and probably you can also give it a try and let us know. Thanks!

Hi @SuryanarayanaY
I tried building with GNU coreutils but that didn't help. I still see the same error message:
ERROR: /private/var/folders/jv/cgkfvslj6nq1l7cw0c8c_8gm0000gn/T/spack5_64ik8l/a80a44b2cbdf4a3623613aef29c648d0/external/com_google_absl/absl/profiling/BUILD.bazel:59:11: Compiling absl/profiling/internal/exponential_biased.cc failed: Exec failed due to IOException: xcrun failed with code 1.
This most likely indicates that SDK version [13.3.1] for platform [MacOSX] is unsupported for the target version of xcode.
Process exited with status 1
stdout: stderr: 2023-04-26 10:21:06.822 xcodebuild[94731:2285264] Writing error result bundle to /var/folders/jv/cgkfvslj6nq1l7cw0c8c_8gm0000gn/T/ResultBundle_2023-26-04_10-21-0006.xcresult
xcodebuild: error: SDK "macosx13.3.1" cannot be located.
2023-04-26 10:21:08.277 xcodebuild[94873:2285548] Writing error result bundle to /var/folders/jv/cgkfvslj6nq1l7cw0c8c_8gm0000gn/T/ResultBundle_2023-26-04_10-21-0008.xcresult
xcodebuild: error: SDK "macosx13.3.1" cannot be located.
xcrun: error: unable to lookup item 'Path' in SDK 'macosx13.3.1'
Target //tensorflow/tools/pip_package:build_pip_package failed to build
ERROR: /private/var/folders/jv/cgkfvslj6nq1l7cw0c8c_8gm0000gn/T/Adam/spack-stage/spack-stage-py-tensorflow-2.12.0-euzc5objnjakkm73bpc666vzlv6uguxl/spack-src/tensorflow/lite/python/BUILD:69:10 Middleman _middlemen/tensorflow_Slite_Spython_Stflite_Uconvert-runfiles failed: Exec failed due to IOException: xcrun failed with code 1.
This most likely indicates that SDK version [13.3.1] for platform [MacOSX] is unsupported for the target version of xcode.
Process exited with status 1
stdout: stderr: 2023-04-26 10:21:06.822 xcodebuild[94731:2285264] Writing error result bundle to /var/folders/jv/cgkfvslj6nq1l7cw0c8c_8gm0000gn/T/ResultBundle_2023-26-04_10-21-0006.xcresult
xcodebuild: error: SDK "macosx13.3.1" cannot be located.
2023-04-26 10:21:08.277 xcodebuild[94873:2285548] Writing error result bundle to /var/folders/jv/cgkfvslj6nq1l7cw0c8c_8gm0000gn/T/ResultBundle_2023-26-04_10-21-0008.xcresult
xcodebuild: error: SDK "macosx13.3.1" cannot be located.
xcrun: error: unable to lookup item 'Path' in SDK 'macosx13.3.1'

I'm on macOS 13.3.1, bazel 5.3.0, TF 2.12.0, and Xcode 14.3.

I'm using the Spack package manager, specifically this build recipe.
I'll try to reproduce this without Spack to make sure it isn't something weird in our environment or patches. Currently busy with the NeurIPS deadline, but will get back to this as soon as I get a chance.

Hi @adamjstewart ,
Could you please confirm the current status. I am attaching a reference for successful build on MacM1 with Tf2.12.
Thanks!

@adamjstewart ,
Could you please confirm whether you got opportunity to test the build. Please confirm.
Thanks!

Thanks for the reminder. Following the steps from https://www.tensorflow.org/install/source, I ran:
# Install and load Python deps using Spack
git clone https://github.com/tensorflow/tensorflow.git
cd tensorflow
# Sticking with master branch for now
./configure
# Use defaults for all options
bazel build --config=nogcp --config=nonccl //tensorflow/tools/pip_package:build_pip_package
# Build the minimal package

I see the following errors fairly early on:
ERROR: Traceback (most recent call last):
	File "/private/var/tmp/_bazel_Adam/a1795e315d59972d5fef2fc11783c641/external/build_bazel_rules_apple/apple/internal/transition_support.bzl", line 547, column 46, in <toplevel>
		_apple_platform_split_transition = transition(
Error in transition: Invalid transition input '//command_line_option:incompatible_enable_apple_toolchain_resolution'. Cannot transition on --experimental_* or --incompatible_* options
...
ERROR: /Users/Adam/tensorflow/WORKSPACE:88:14: error loading package '@com_github_grpc_grpc//src/compiler': at /private/var/tmp/_bazel_Adam/a1795e315d59972d5fef2fc11783c641/external/com_github_grpc_grpc/bazel/grpc_build_system.bzl:28:6: at /private/var/tmp/_bazel_Adam/a1795e315d59972d5fef2fc11783c641/external/build_bazel_rules_apple/apple/ios.bzl:33:5: at /private/var/tmp/_bazel_Adam/a1795e315d59972d5fef2fc11783c641/external/build_bazel_rules_apple/apple/internal/ios_rules.bzl:95:5: initialization of module 'apple/internal/transition_support.bzl' failed and referenced by '//external:grpc_python_plugin'
ERROR: Analysis of target '//tensorflow/tools/pip_package:build_pip_package' failed; build aborted:

@adamjstewart ,
I tried the command and found build fails. Attached below the logs for reference. Needs to check.
(tf-metal) suryanarayanay-macbookpro:tensorflow suryanarayanay$ bazel build --config=nogcp --config=nonccl //tensorflow/tools/pip_package:build_pip_package

Extracting Bazel installation...
Starting local Bazel server and connecting to it...
INFO: Options provided by the client:
  Inherited 'common' options: --isatty=1 --terminal_columns=80
INFO: Reading rc options for 'build' from /Users/suryanarayanay/tensorflow/.bazelrc:
  Inherited 'common' options: --experimental_repo_remote_exec
INFO: Reading rc options for 'build' from /Users/suryanarayanay/tensorflow/.bazelrc:
  'build' options: --define framework_shared_object=true --define tsl_protobuf_header_only=true --define=use_fast_cpp_protos=true --define=allow_oversize_protos=true --spawn_strategy=standalone -c opt --announce_rc --define=grpc_no_ares=true --noincompatible_remove_legacy_whole_archive --enable_platform_specific_config --define=with_xla_support=true --config=short_logs --config=v2 --define=no_aws_support=true --define=no_hdfs_support=true --experimental_cc_shared_library --experimental_link_static_libraries_once=false --incompatible_enforce_config_setting_visibility
INFO: Reading rc options for 'build' from /Users/suryanarayanay/tensorflow/.tf_configure.bazelrc:
  'build' options: --action_env<EMAIL_ADDRESS>--action_env<EMAIL_ADDRESS><EMAIL_ADDRESS>INFO: Reading rc options for 'build' from /Users/suryanarayanay/tensorflow/.bazelrc:
  'build' options: --deleted_packages=tensorflow/compiler/mlir/tfrt,tensorflow/compiler/mlir/tfrt/benchmarks,tensorflow/compiler/mlir/tfrt/jit/python_binding,tensorflow/compiler/mlir/tfrt/jit/transforms,tensorflow/compiler/mlir/tfrt/python_tests,tensorflow/compiler/mlir/tfrt/tests,tensorflow/compiler/mlir/tfrt/tests/ir,tensorflow/compiler/mlir/tfrt/tests/analysis,tensorflow/compiler/mlir/tfrt/tests/jit,tensorflow/compiler/mlir/tfrt/tests/lhlo_to_tfrt,tensorflow/compiler/mlir/tfrt/tests/lhlo_to_jitrt,tensorflow/compiler/mlir/tfrt/tests/tf_to_corert,tensorflow/compiler/mlir/tfrt/tests/tf_to_tfrt_data,tensorflow/compiler/mlir/tfrt/tests/saved_model,tensorflow/compiler/mlir/tfrt/transforms/lhlo_gpu_to_tfrt_gpu,tensorflow/core/runtime_fallback,tensorflow/core/runtime_fallback/conversion,tensorflow/core/runtime_fallback/kernel,tensorflow/core/runtime_fallback/opdefs,tensorflow/core/runtime_fallback/runtime,tensorflow/core/runtime_fallback/util,tensorflow/core/tfrt/eager,tensorflow/core/tfrt/eager/backends/cpu,tensorflow/core/tfrt/eager/backends/gpu,tensorflow/core/tfrt/eager/core_runtime,tensorflow/core/tfrt/eager/cpp_tests/core_runtime,tensorflow/core/tfrt/gpu,tensorflow/core/tfrt/run_handler_thread_pool,tensorflow/core/tfrt/runtime,tensorflow/core/tfrt/saved_model,tensorflow/core/tfrt/graph_executor,tensorflow/core/tfrt/saved_model/tests,tensorflow/core/tfrt/tpu,tensorflow/core/tfrt/utils
INFO: Found applicable config definition build:short_logs in file /Users/suryanarayanay/tensorflow/.bazelrc: --output_filter=DONT_MATCH_ANYTHING
INFO: Found applicable config definition build:v2 in file /Users/suryanarayanay/tensorflow/.bazelrc: --define=tf_api_version=2 --action_env=TF2_BEHAVIOR=1
INFO: Found applicable config definition build:nogcp in file /Users/suryanarayanay/tensorflow/.bazelrc: --define=no_gcp_support=true
INFO: Found applicable config definition build:nonccl in file /Users/suryanarayanay/tensorflow/.bazelrc: --define=no_nccl_support=true
INFO: Found applicable config definition build:macos in file /Users/suryanarayanay/tensorflow/.bazelrc: --apple_platform_type=macos --copt=-DGRPC_BAZEL_BUILD --copt=-w --define=PREFIX=/usr --define=LIBDIR=$(PREFIX)/lib --define=INCLUDEDIR=$(PREFIX)/include --define=PROTOBUF_INCLUDE_PATH=$(PREFIX)/include --cxxopt=-std=c++17 --host_cxxopt=-std=c++17
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/tensorflow/runtime/archive/0aaa6e679847a4eeb407136e7b0bcef93ec652e6.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/llvm/llvm-project/archive/a52054cfa29d665c43141c66c20a7b8f7a96b546.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/google/benchmark/archive/f7547e29ccaed7b64ef4f7495ecfff1c9f6f3d03.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://mirror.bazel.build/github.com/bazelbuild/rules_cc/archive/081771d4a0e9d7d3aa0eed2ef389fa4700dfb23e.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/openxla/stablehlo/archive/458bdd95771e9861e6488868e315a1b0340058ba.zip failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/google/boringssl/archive/c00d7ca810e93780bd0c8ee4eea28f4f2ea4bcdc.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/google/XNNPACK/archive/7adae8e6ded8fff33d92212ca1028d2419cd34d4.zip failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/pybind/pybind11_abseil/archive/2c4932ed6f6204f1656e245838f4f5eae69d2e29.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
INFO: Analyzed target //tensorflow/tools/pip_package:build_pip_package (606 packages loaded, 43903 targets configured).
INFO: Found 1 target...
ERROR: /Users/suryanarayanay/tensorflow/tensorflow/BUILD:1128:21: declared output 'tensorflow/libtensorflow_framework.2.dylib' was not created by genrule. This is probably because the genrule actually didn't create this output, or because the output was a directory and the genrule was run remotely (note that only the contents of declared file outputs are copied from genrules run remotely)
ERROR: /Users/suryanarayanay/tensorflow/tensorflow/BUILD:1128:21: Executing genrule //tensorflow:libtensorflow_framework.2.dylib_sym [for host] failed: not all outputs were created or valid
realpath: illegal option -- -
usage: realpath [-q] [path ...]
Target //tensorflow/tools/pip_package:build_pip_package failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 1411.742s, Critical Path: 65.35s
INFO: 19865 processes: 8807 internal, 11058 local.
FAILED: Build did NOT complete successfully

Something must have changed because with the help of https://github.com/tensorflow/tensorflow/issues/60179#issuecomment-1491238631 I'm finally able to build from source in 2.13.0! Thanks for your help!!

The specific error that prompted this issue:
xcrun: error: unable to lookup item 'Path' in SDK 'macosx12.5.1'

still occurs when building inside Spack. Removing the following flag and allowing bazel to auto-detect the correct version solved my issue: --macos_sdk_version=12.5.1.


add context using fluent api

Our library code, either for internal or for public use, should never hardcode a context.TODO(), which is meant
as placeholder and prevents cancelation propagation.
So add explicit context argument to our library functions

/cherry-pick release-4.13


Confirm if the details here apply to Isolated Process functions.

Please confirm if the details here apply to Isolated Process functions, because things don't seem to be working correctly and there are issues logged on Github.

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

ID: 13672b67-22ea-3dda-8b6b-3332c24e6030
Version Independent ID: fdc60aeb-9971-1d9f-a6ba-b3ad818cf0d5
Content: Monitor Azure Functions
Content Source: articles/azure-functions/functions-monitoring.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@oatsoda Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.


[Test] Fix mocked functions.

If any function is mocked used stub need to be reverted at some point,
doing something like this
before_each(function()
  stub(foo, "validate", function() return false end)
end)

after_each(function()
  foo.validate:revert()
end)

it("Validate stub foo", function()
  assert.same(foo.validate(), false)
end)

In APICast all ngx variables are reset on ngx_helper.lua but some
methods like ngx_variables or backend_client are not reset and the
mock function is in there for all other test.
The test in spec/policy/ngx_variable_spec.lua validates that
ngx_variable.available_context is working correctly, due some other
test can mock this function the test was inestable over the last days.
This commit creates a way to define a cleanup for mocked functions that
are not part of the ngx class.

All mocks/stubs should be reverted automatically. If they are applied in some global context (not after/before_each), then they would not be reverted between tests.
I see this change as a bandaid and yet another way to rollback changes. Why we can't just rely on the rollbacking the stubs?

@mikz I'm ok to apply the :revert() function on the after_each functions, I think that it's a bit clear and It makes things easier to read and debug.
Last week, I had a chat with @davidor and we agreed that we should use the same way that we use for ngx.* methods.

@eloycoto but that should not be needed at all. There are global after/before hooks that do that for all registered stubs. There should be no reason to manually revert them because it would be really error-prone.
https://github.com/3scale/APIcast/blob/master/spec/luassert_helper.lua (was significantly refactored in https://github.com/3scale/APIcast/pull/799).

Will check, thanks!

Close this one due to is not the correct solution, the correct one is on https://github.com/3scale/APIcast/pull/1042


Create main.workflow

This does implement tests, but it should not fail if you have none yet.

I'm going to close this for the foreseeable future, I may reopen if/when I want to implement CI for this library.


⚠ Samsung has degraded performance

In 04c6781, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2214 ms

Resolved: Samsung performance has improved in 89be86f.


Import of transactions

Should be able to import transactions from different accounts like Chase, we should also allow for dynamic mapping.

For mvp it will be a set protocol, ie headers need to map directly to the database format.


Emulating touch events

Is there any straightforward way to emulate a touch/tap event with Casper? I'm currently testing a web-app to be deployed to an iPad and it only responds to touch events. AFAIK, Casper does not have any built in touch events and I don't believe does Phantom does either, though I may be wrong there.
I approached it from a jQuery perspective, but that didn't yield any success. Not sure if there's a viable way through Casper to emulate a touch and if not, if there's any thought on including that down the line for situations like this, which I'm sure will become more common?

I post a pr  here to support this.touch method by emulating touch events. https://github.com/n1k0/casperjs/pull/1018#issuecomment-56479604
wish it helps.

Duplicate of https://github.com/n1k0/casperjs/issues/430.


Crashed on Android4.4

Hi I need to run surveyor on Android 4.4 but the app crashed with the following error. Can you give some suggestion for fixing this?
java.lang.NoClassDefFoundError: androidx.core.content.FileProvider$PathStrategy
at androidx.core.content.FileProvider.getPathStrategy(FileProvider.java:576)
at androidx.core.content.FileProvider.attachInfo(FileProvider.java:392)
at android.app.ActivityThread.installProvider(ActivityThread.java:4771)
at android.app.ActivityThread.installContentProviders(ActivityThread.java:4366)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4306)
at android.app.ActivityThread.access$1400(ActivityThread.java:135)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1457)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:158)
at android.app.ActivityThread.main(ActivityThread.java:5013)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:777)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:593)
at dalvik.system.NativeStart.main(Native Method)

Hmm Android 4.4 (SDK 19) is the current minimum supported version so it should work.. but I just tried running the tests and ran into a different problem supposedly caused by using latest Android Studio and SDKs < 21

@rowanseymour Thanks for the fast reply. I want to explore the app but cannot register an account. Can I have a faked account for testing the app? Thank you.

You can create an account on textit.com that's open to anyone and there's a TextIt Surveyor version of the app in the play store. You can also change the URL in the code if you're debugging that.


Movie Search App

Description
Added Movie Search App using TMDB API
Checklist

[x] I've been assigned an issue related to this PR.
[x] I've used beautifiers.
[x] I've added my Project's name and description to Index.md
[x] I've made a README.md file for my Project.
[x] The README.md file of my projrct contains Project title, Description, Use of project, Set up, Stack used and Output (Screenshots).

Related Issues or Pull Requests number
Movie-Search-App #319

Hey @chicken-biryani @harshita2216
Please Review my PR

Thank you so much @harshita2216 for the changes 😊


excessive z movement when focus stacking

basically these are interacting in a weird way:

Panorama w/o z movement needs to know where to start focus stack at (ie not the end position from the previous stack)
Panorama w/ z movement knows where the center is and may go there unnecessarily
Backlash correction when doing extra moves

All of these combine to move the z a lot more than we need to. Probably need some intermediate target motion coordinate and a way to "flush" it or at least predict if there will be a future z movement (ie focus stacking)

This appears to be fixed, although needs more testing