text:
[Bug]: There are more than 2000 databases that cannot be switched in the sql window

ODC version
ODC 424-bp2
OB version
NO related
What happened?
There are more than 2000 databases that cannot be switched in the sql window.
What did you expect to happen?
More than 2000 databases can also switch databases in the sql window.
How can we reproduce it (as minimally and precisely as possible)?
When there are 2000 databases, switch databases in the sql window.
Anything else we need to know?
No response

pass

repo: oceanbase/odc


text:
[Bug]: When you view a task that is to be executed, an error is reported on the interface

ODC version
4.3.2
OB version
no related
What happened?

In the schema change ticket, if you select View Task Details in the Pending Execution status, an error is reported
What did you expect to happen?
In the schema change ticket, select View Task Details in the Pending Status to view the details normally
How can we reproduce it (as minimally and precisely as possible)?
In the schema change ticket, select View Tasks in the Pending Status to view the execution details and observe the program response
Anything else we need to know?
No response

Fixed In Commit 9ec5ef705eea3bacdc1619f6bb9cd43dfe261219
------
畅晚
Wed Sep 25 16:02:09 2024 +0800

pass

source: gharchive/issue

authors: HSunboy qymsummer

license_type: permissive

license_source: github-api


text:
fix(sql-execute): anonymous block execution module adapted to oracle11g

What type of PR is this?
type-bug
module-sql-execution
module-db-browser
What this PR does / why we need it:

Anonymous block execution module adapted to oracle11g

rename OBOracleDBMSOutputInitializer to OracleDBMSOutputInitializer

Fixed the problem of error reporting when viewing packages without package body

Which issue(s) this PR fixes:

Fixes #1729
Fixes #1754
Special notes for your reviewer:

Additional documentation e.g., usage docs, etc.:

lgtm

source: gharchive/pull-request

authors: PeachThinking krihy


text:
Adding more logs

We should have many more logs in every different component, to give more insight in case anything goes wrong.

closed on https://github.com/oceanprotocol/ocean-node/pull/152

repo: oceanprotocol/ocean-node


text:
Towards #1159: Expand CI to more OSes & Py versions

Towards #1159
Changes proposed in this PR:

add weekly dependabot
add build tests on different os: windows/macos/linux
add build tests on different python versions: 3.8 , 3.10, 3.11

What's the status of this? It's 6 days old. It would be very useful to have this.

Not all new CI tests passed: it failed on macos-latest x python 3.10 with a "coincurve" error.

Yes, @calina-c is working on fixing that failing test 😄 We got this

authors: AnaLoznianu alexcos20 trentmc


text:
Bump version: 0.8.4 → 0.8.5

Changes:

refactor serach function for FRE;
unify asset & ddo classes, common folder refactoring;
added OPERATOR_SERVICE_URL in developers.md;
fixed network names to match the networks from address.json file ones;
in C2D readme, link Raven logistic regression work;
updated BLOCK_NUMBER_POLL_INTERVAL dict;
make transaction_timeout configurable;
removed multi network aqua duplicates from example_config;
refactor services;
added support for mumbai network;
feature/re add get provider address;
feature/bump contracts 0.6.9.

@mariacarmina Can you please post the proposed release notes in the PR description?

@mariacarmina Can you please post the proposed release notes in the PR description?

Yep, done.

authors: DMats mariacarmina


text:
SBT launch fails with error: "Unsupported Major.minor version 52.0"

Full error text:
java.lang.UnsupportedClassVersionError: com/typesafe/config/ConfigException : Unsupported major.minor version 52.0
Forgive me if this is an obvious fix, I'm a newcomer to scala.js. Various searches indicate that I need to specify a target version of the JVM in build.sbt, but none of the solutions found elsewhere have worked in this case.
I am working from an unmodified clone of this project.

You probably need to use Java8.

authors: gtkovas ochrons

repo: ochrons/scalajs-spa-tutorial

license_source: bigquery


text:
LineEdit password delay should be platform specific

Hello,
    // LineEdit
    case SH_LineEdit_PasswordCharacter:
      return QChar(0x2022).unicode(); // Bullet.
    case SH_LineEdit_PasswordMaskDelay:
      return 200;

This hard codes 200 ms delay for the password echo delay, but this is not really the wanted behavior on desktop (or non-touch screen devices) where passcodes don't have to echo typed characters.
It would be better to have a delay only when required.
thanks !

Yes you're right. You can make a PR and I'll have a look

NB: Qlementine is an opinionated QStyle. I'm OK to set 0. I set 200 because at first I thought it looked good, but actually it's not handy on Desktop to have that feature. Let's set 0.

authors: oclero pierrenicolasr

repo: oclero/qlementine

license: MIT


text:
./bin/dev loads from  /src/commands ONLY if /dist does not exist

Describe the bug
If /dist contains an older version of the build,  running ./bin/dev will ignore the /src/ and load the older files from /dist
After deleting the /dist folder, everything works fine
To Reproduce
Steps to reproduce the behavior:

Run a build npm run build
Make a change in a command
Run the command in dev mode ./bin/dev
The change is not reflected, the command returns the output before the change
Remove the /dist folder
Rerun the command via  ./bin/dev
Now the changes are reflected immediately

Expected behavior
When running commands via  ./bin/dev, they should ignore the /dist files
Environment (please complete the following information):

OS & version: MacOS Ventura
Fish shell
Node 16

@chetzof I don't observe that behavior at all when I try it.
Can you check your ./bin/dev to see if it matches https://github.com/oclif/hello-world/tree/main/bin

The other thing that may be happening is that there's an compilation error in your changes, and when the TS fails to require, oclif will use the lib if it exists.  After making your change, can you confirm that build would have run without error?

Closing this since there hasn't been any updates. Please re-open if needed

authors: mdonnalley mshanemc vladcosorg

repo: oclif/core


text:
Excessive warnings during startup against existing 1.2.0 OCSF

One of the PR guidelines for ocsf-schema is for this server to run without warnings.  However, it is rather noisy when running against the current OCSF repo.  These are the warnings from the v1.2.0 branch:
23:40:48.984 [warning] resource_details uses 'cloud' profile, but it does not define 'cloud' attribute
23:40:48.989 [warning] The invoked_by attribute in actor has been deprecated. Use  app_name, app_uid  attributes instead.
23:40:48.989 [warning] The finding object has been deprecated. Use the new finding_info object.
23:40:48.989 [warning] The type attribute in related_event has been deprecated. Use type_name attribute instead.
23:40:48.990 [warning] The related_analytics attribute in analytic has been deprecated. Related Analytics has been decoupled from this object, instead use finding_info.related_analytics.
23:40:48.990 [warning] The security_finding class has been deprecated. Use the new specific classes according to the use-case: Vulnerability Finding, Compliance Finding, Detection Finding, Incident Finding.
23:40:48.991 [warning] The web_resource_access_activity class has been deprecated. Use the Web Resources Activity class with the Security Control and/or Network Proxy profile instead.
23:40:48.992 [warning] The network_file_activity class has been deprecated. Use the new class: 'File Hosting Activity' in the 'Application'  category.
23:40:48.993 [warning] The following attributes do not have a "requirement" field, a value of "optional" will be used: authentication.logon_process (class), authorization.decision (object), authorization.policy (object), device.uid_alt (object), device_config_state_change.prev_security_level (class), device_config_state_change.prev_security_level_id (class), device_config_state_change.prev_security_states (class), device_config_state_change.security_level (class), device_config_state_change.security_level_id (class), device_config_state_change.security_states (class), dhcp_activity.tls (class), dns_activity.tls (class), dns_answer.flag_ids (object), dns_answer.flags (object), email.subject (object), ftp_activity.tls (class), http_activity.http_status (class), http_activity.tls (class), http_request.http_method (object), logger.logged_time (object), memory_activity.size (class), metadata.loggers (object), network_activity.tls (class), network_connection_info.boundary (object), network_connection_info.boundary_id (object), network_connection_info.protocol_name (object), network_connection_info.protocol_ver (object), network_connection_info.protocol_ver_id (object), network_connection_info.tcp_flags (object), network_connection_info.uid (object), network_file_activity.tls (class), ntp_activity.tls (class), policy.is_applied (object), product.feature (object), product.path (object), product.url_string (object), rdp_activity.tls (class), security_state.state (object), security_state.state_id (object), smb_activity.tls (class), ssh_activity.tls (class), tunnel_activity.tls (class), url.categories (object), url.resource_type (object), win/win_resource.details (object), win/win_resource.svc_name (object)

Agree, the solution to this is two fold,

An ocsf-server PR to change remove warnings for deprecated entities (I don't see a value of such warnings while building a server, this should be more of a schema-presentation warning, which we already do using simple UI elements)
An ocsf-schema PR to fix missing requirement attributes to the schema definition files.

authors: dkolbly floydtree

repo: ocsf/ocsf-server


text:
How to install on raspbian?

Readme is missing the steps needed to install, this is what I've done:
git clone https://github.com/octo/librouteros.git
cd librouteros/
automake

result in errors:

configure.ac: error: no proper invocation of AM_INIT_AUTOMAKE was found.
configure.ac: You should verify that configure.ac invokes AM_INIT_AUTOMAKE,
configure.ac: that aclocal.m4 is present in the top-level directory,
configure.ac: and that aclocal.m4 was recently regenerated (using aclocal)
configure.ac:30: error: required file './install-sh' not found
configure.ac:30:   'automake --add-missing' can install 'install-sh'
Makefile.am: error: required file './INSTALL' not found
Makefile.am:   'automake --add-missing' can install 'INSTALL'
src/Makefile.am:3: error: COMPILER_IS_GCC does not appear in AM_CONDITIONAL
src/Makefile.am:5: error: BUILD_WITH_DEBUG does not appear in AM_CONDITIONAL
src/Makefile.am:15: error: BUILD_WITH_LIBSOCKET does not appear in AM_CONDITIONAL
configure.ac:3: error: required file 'src/config.h.in' not found
src/Makefile.am:11: error: Libtool library used but 'LIBTOOL' is undefined
src/Makefile.am:11:   The usual way to define 'LIBTOOL' is to add 'LT_INIT'
src/Makefile.am:11:   to 'configure.ac' and run 'aclocal' and 'autoconf' again.
src/Makefile.am:11:   If 'LT_INIT' is in 'configure.ac', make sure
src/Makefile.am:11:   its definition is in aclocal's search path.
src/Makefile.am:18: warning: source file 'md5/md5.c' is in a subdirectory,
src/Makefile.am:18: but option 'subdir-objects' is disabled
automake: warning: possible forward-incompatibility.
automake: At least a source file is in a subdirectory, but the 'subdir-objects'
automake: automake option hasn't been enabled.  For now, the corresponding output
automake: object file(s) will be placed in the top-level directory.  However,
automake: this behaviour will change in future Automake versions: they will
automake: unconditionally cause object files to be placed in the same subdirectory
automake: of the corresponding sources.
automake: You are advised to start using 'subdir-objects' option throughout your
automake: project, to avoid future incompatibilities.

Instead this way for install success, but there are missing "*.h" at runtime:
1 ) ---- download librouteros-1.1.2.tar.bz2 from https://github.com/octo/librouteros/releases/download/librouteros-1.1.2/librouteros-1.1.2.tar.bz2
to a file /home/pi/librouteros-1.1.2.tar.bz2
( home page: https://octo.github.io/librouteros/
examples: https://wiki.mikrotik.com/wiki/Librouteros )
2 ) ---- extract from /home/pi/librouteros-1.1.2.tar.bz2 to /home/pi/librouteros-1.1.2
3 ) ---- cd /home/pi/librouteros-1.1.2
4 ) ---- apt install libgcrypt-dev
5 ) ---- modify the file: /home/pi/librouteros-1.1.2/src/ros.c ( example file )
--- comment out line 296: const char *host;
--- comment out line 320: host = argv[optind];
5 ) ---- ./configure
6 ) ---- make
7 ) ---- make install
8 ) ---- create a symlink /usr/share/man/man1/ros.1 to /opt/librouteros/share/man/man1/ros.1
9 ) ---- create a symlink /usr/share/man/man3/librouteros.3 to /opt/librouteros/share/man/man3/librouteros.3
10 ) ---- create a symlink /usr/lib/librouteros.so.0 to /opt/librouteros/lib/librouteros.so.0
To build and run the test program:
1 ) ---- cd /home/pi/
2 ) ---- make wifirssitest
3 ) ---- ./wifirssitest
The test program would output:
Temporary breakpoint 1, main (argc=1, argv=0x7effdf14) at wifirssitest.c:77
77 c = ros_connect ("192.168.1.1", ROUTEROS_API_PORT, "WHO", "AMI");
(gdb) n
78 if (c == NULL)
(gdb)
80 fprintf (stderr, "ros_connect failed: %s\n", strerror (errno));
(gdb)
ros_connect failed: Permission denied
81 exit (EXIT_FAILURE);
(gdb) n
[Inferior 1 (process 627) exited with code 01]

Getting down in step by step:
__GI_getaddrinfo (name=0x10d88 "192.168.1.1", service=0x10d80 "8728", hints=hints@entry=0x7effdd68, pai=0x7effdd64, pai@entry=0x7effdd5c)
at ../sysdeps/posix/getaddrinfo.c:2175
2175 ../sysdeps/posix/getaddrinfo.c: No such file or directory.

Even with admin user I still get:
 ros_connect failed: Permission denied

@Summer88
You are compiling it wrong. Take a look how I am doing it under debian:
git clone https://github.com/octo/librouteros.git
cd librouteros
autoreconf -ivf
./configure
make -j4

The permission denied error you have indicating a problem on the mikrotik or its configuration I suppose...

Thank for your reply I've tried to reinstall with:
git clone https://github.com/octo/librouteros.git
cd librouteros
root@gigi:/home/pi/librouteros# autoreconf -ivf
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/bin/autoconf --force
configure.ac:36: error: possibly undefined macro: AC_LIBTOOL_DLOPEN
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.ac:37: error: possibly undefined macro: AC_PROG_LIBTOOL
autoreconf: /usr/bin/autoconf failed with exit status: 1

However with this python library I can connect so the router is configured correctly.
https://github.com/socialwifi/RouterOS-api
There's only a difference from python script to C, theres a plain_login option?

What version of libtool you have installed?
I don't know the difference - never used a python script. If you compile librouteros there is a test tool which you can use for connecting to mikrotiks. You sure you are passing proper credentials and you have enabled the api in the routeros? Also make sure that you are not using SSL which is currently not enabled in the library....

Actually libtool wasn't installed at all.
libtool/stable,now 2.4.6-9 all [installed]
  Generic library support script

Now autoreconf -ivf and install succeded.
Recompiled the script but output is the same.
I've checked on the router API port 8728 is open.
Thank you

Hmmm ... no idea what is wrong in your case. I was testing it and it is working for me without any problem (I am constantly using the library for collecting statistics into collectd).
Maybe they changed something in the newer RouterOS versions? No idea :(

@cirolandolfi found the issue
Please take a look at you should update your code to work with latest RouterOS.
https://wiki.mikrotik.com/wiki/Manual:API

@Summer88
This was done two years ago! :)
https://github.com/octo/librouteros/commit/348e107aa5023c520604a0f67c68ce53794eb606

Well looking at Release page "Latest release" appear to be 1.1.2 and that was the starting point of the issue.

repo: octo/librouteros

license: isc


text:
Update instructions for better eslint support

Without this steps linting not working

Thanks for the PR! However it seems to me more people are using https://github.com/vuejs/eslint-plugin-vue, and it's under the official vuejs organization.
So I'd say either leave the setup up to users, or recommend vuejs/eslint-plugin-vue.

ok, you're right

authors: iatsiuk octref

repo: octref/vetur


text:
🛑 KeyCloak (auth.octubre.org.ar) is down

In af02e36, KeyCloak (auth.octubre.org.ar) (https://auth.octubre.org.ar/auth/) was down:

HTTP code: 404
Response time: 831 ms

Resolved: KeyCloak (auth.octubre.org.ar) is back up in 489a2ea.

repo: octubre-softlab/octubre-upptime


text:
Update build.yml

Adjust build.yml

Pull Request Test Coverage Report for Build 258505532

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 31.765%

Totals

Change from base Build 258502902:
0.0%

Covered Lines:
27

Relevant Lines:
85

💛  - Coveralls

authors: coveralls odair-pedro

repo: odair-pedro/sonarci


text:
Error building

error[E0432]: unresolved import ffmpeg::format::register_all
--> /home/frag/.cargo/registry/src/github.com-1ecc6299db9ec823/video-rs-0.1.8/src/init.rs:6:5
|
6 |     register_all,
|     ^^^^^^^^^^^^
|     |
|     no register_all in format
|     help: a similar name exists in the module: register_t
error[E0599]: no method named codec found for reference &StreamMut<'_> in the current scope
--> /home/frag/.cargo/registry/src/github.com-1ecc6299db9ec823/video-rs-0.1.8/src/encode.rs:363:8
|
363 |       .codec()
|        ^^^^^ method not found in &StreamMut<'_>
error[E0599]: no method named codec found for struct Stream in the current scope
--> /home/frag/.cargo/registry/src/github.com-1ecc6299db9ec823/video-rs-0.1.8/src/mux.rs:316:19
|
316 |         if stream.codec().id() == AvCodecId::H264 {
|                   ^^^^^ method not found in Stream<'_>
Some errors have detailed explanations: E0432, E0599.
For more information about an error, try rustc --explain E0432.
error: could not compile video-rs due to 3 previous errors

Yeah this is related to an issue with video-rs that I'm currently working on. Will be fixed soon. Using ffmpeg 4 should work for now.

repo: oddity-ai/oddity-rtsp


text:
feat(extractors/services): add dnsmasq

Converts the dns, domain to address mappings into details
        services.dnsmasq = {
          enable = true;
          settings.address = [
            "/home.lan/192.168.25.125"
            "/example.com/192.168.25.25"
          ];
        };

Ah, very nice idea!
Just some thoughts (and not meant to be feedback for this PR but food for thought in the future)
I could see some configurations becoming quite large in mappings they might have configured, so just noting we might want to return to the parsing of settings.addresses as possibly split from normal vs detailed view (pending where/if https://github.com/oddlama/nix-topology/issues/15 changes that concept into the future)
All in all, I love it - going to add a similar split to blocky if there is appetite to merge this :heart_eyes:

I agree, in #19. Caddy can serve many services and load balance, which can add quite a few options. So possibly adding a threshold, where after let's say 10 lines, all others are added with ....
Then the detailed view would have all of the details, ignoring the threshold.

@oddlama The issues have been fixed

Awesome! Thanks a lot!

authors: IogaMaster JayRovacsek oddlama

repo: oddlama/nix-topology


text:
Update stackbit.config.ts

// stackbit.config.js
import { ContentfulContentSource } from "@stackbit/cms-contentful";
export default {
contentSources: [
new ContentfulContentSource({
spaceId: process.env.CONTENTFUL_SPACE_ID,
environment: process.env.CONTENTFUL_ENVIRONMENT,
previewToken: process.env.CONTENTFUL_PREVIEW_TOKEN,
accessToken: process.env.CONTENTFUL_MANAGEMENT_TOKEN
})
]
// ...
};

👷 Deploy Preview for oherlife processing.

Name
Link

🔨 Latest commit
af99ebe2965fa1dbdbdf6510810f1eb49a57c57d

🔍 Latest deploy log
https://app.netlify.com/sites/oherlife/deploys/6694247752d95c0009cc599e

repo: odieskoalikish/astrowinds


text:
Improve ODK-X AndroidLibrary Test Coverage: Write/Update Test(s) for DateUtils Class

I would like to write tests for the validifyDateValue method in the DateUtils class to verify various date formats and ensure the correct handling of different input types.

@Redeem-Grimm-Satoshi can this be assigned to me to do?

repo: odk-x/tool-suite-X


text:
Support pagination in the approvals API

Summary
Need for support of pagination in the approvals api - /v1beta1/me/approvals.
Even with the filters which the api currently supports, there are users who have too many approvals as part of this api response.

I would add that we need pagination on the resources API too, because our team has a lot of resources to manage

We should ideally have pagination support for all the list kind of API's that we have.

authors: bsushmith swallowstalker

repo: odpf/guardian


text:
Cannot inject large libraries into helm chart (for connector demos)

In our 'egeria-base' helm chart there is information on adding additional libraries (such as connectors) for deployment at https://github.com/odpi/egeria/tree/master/open-metadata-resources/open-metadata-deployment/charts/egeria-base
This has been tested previously and allows additional libraries to effectively be added to LOADER_PATH in the deployment
However when testing https://github.com/odpi/egeria-database-connectors/pull/73 this fails
For example

Download postgres jdbc driver at https://jdbc.postgresql.org/download/postgresql-42.2.21.jar
Build https://github.com/odpi/egeria-database-connectors
cd ~/src/egeria/charts
cp ~/src/egeria-database-connectors/egeria-connector-postgres/build/libs/egeria-connector-postgres-2.10-SNAPSHOT.jar egeria-base/libs
cp  ~/Downloads/postgresql-42.2.21.jar egeria-base/libs

However this then fails with:
$ helm install base egeria-base                                                                                [12:57:55]
Error: create: failed to create: Request entity too large: limit is 3145728

$ ls -la egeria-base/libs                                                                                [12:58:13]
total 2056
drwxr-xr-x   4 jonesn  staff      128 15 Jun 12:57 .
drwxr-xr-x  10 jonesn  staff      320  9 Jun 11:08 ..
-rw-r--r--   1 jonesn  staff    43350 15 Jun 12:56 egeria-connector-postgres-2.10-SNAPSHOT.jar
-rw-r--r--@  1 jonesn  staff  1005332 15 Jun 12:57 postgresql-42.2.21.jar
jonesn:charts/ (master)

These libraries are being encoded in base64, and as such will take more space than the binaries, quite likely exceeding the number given, which is the max size of a kubernetes API request...
This approach therefore needs rethinking. One viable alternative is to build a customized docker image with the required connector (+egeria) - indeed we already do this for the current SAS Viya connector at https://github.com/odpi/egeria-sas-viya-connector
Need to consider other options, but in either case it seems the current documented approach will not work well for k8s as this 3MB limit is very small (but was enough to pass my testing ....!)

As an aside it's noted that etcd (used for storing yaml in k8s) also has a limit around the 1.5MB size. Although this can be increased when using etcd directly, this is unlikely to be feasible in a k8s deployment. This may also mean files such as egeria configuration files cannot be managed as k8s resources.

The approach taken by the postgres connector (building a separate image) works ok on top of a stable release. However during development it will rapidly go out of date, since the build is only triggered by changes to the connector, not the egeria code itself....
.. more thinking required as to best way to handle this.

repo: odpi/egeria


text:
Cannot show code on Google TV

Hello! I need your help.
After I tested your Demo project, after selecting Connect, it displayed "Remote state: Connected" but my GoogleTV did not respond. I don't know what's missing to make your Demo project work.

This is strange behavior. You should to add the logs for dump the data variable in the receive or handleData methods of the RemoteManager class. Also, make sure that your device has a certificate; you can do this with the console command: openssl s_client -connect SERVER_IP:6467 -prexit -state -debug

@TuongLinhTL  I added logs in version 2.4.5 so you can update to this version and send me the log data for figure out your issue.

Can modify the connect function in RemoteTVManager as follows:
queue.async {
            self.remoteManager.stateChanged = { [weak self] remoteState in
                self?.remoteStateChanged?(remoteState.toString())
            }

            self.pairingManager.stateChanged = { [weak self] pairingState in
                self?.pairingStateChanged?(pairingState.toString())

                if case .successPaired = pairingState {
                    self?.remoteManager.connect(host)
                }
            }

            self.pairingManager.connect(host, "client", "iPhone")
        }

And try again.

authors: TuongLinhTL odyshewroman

repo: odyshewroman/AndroidTVRemoteControl


text:
The road to 2.0

Updated docs
Updated changelog
Added upgrade doc
Updated readme

This PR is to get ready for a 2.0 release. I have attempted to add documentation to everything that has been changes + anything that was missing documentation. Check it out and let me know what you guys think because once this is given the go ahead im gonna update the demo and create the 2.0.0 release.

@stefanpenner @blimmer

@jasonmit let me know when you are also done on your end :smile_cat:

LGTM

All done on my end, both libs ready :)

Sweet thanks again everyone for all the help in getting this release together! :smiley_cat:

authors: jasonmit offirgolan stefanpenner

repo: offirgolan/ember-cp-validations


text:
Added UpdatePassword.js and modified settings.js based on UpdatePassw…

UpdatePassword has three options compared to previous option created by Peter: old password, new password, confirm new password. The setting.js file is changed on line 6, 9-17, 37, 44 to show the buttons to update password.

Looks great. But lets fix the gap on the right side, add a gap below current password to match other sites. Also add password checking for security purposes. Change buttons to match the same color theme and scheme as the rest of the app.

repo: oggunderscore/PocketChef


text:
Authentication using Localstorage and API from Backend (FRONT END) REACT

Consumption of Endpoint from #1 Authentication using devise (Backend)#1 from Backend Rails API

This task is assigned to Victor


text:
Avoid capturing PR merged by as pr_merged event

Currently pr_merge events capture both merged PRs authors and merged by. pr_merged event is intended to capture only PRs merged by the authors and not who merged the PR

@rithviknishad Can you please assign this issue to me?

repo: ohcnetwork/leaderboard


text:
Unify nonce logic between Rest and Websocket requests to prevent "nonce too small"

Related to issue #18.
Add warning about this in the documentation + unify nonce logic between Rest and Websocket requests to prevent the "nonce too small" error.

I was confused by "nonce too small" for several days. I use an api key for wss_example.py, not used on other py
Is it possible to find "nonce" and "small" keywords  by message. then reconnect WSS. I tried to modify wss_example.py
 def cb_auth(self, message):

        LOGGER.info(f"cb_auth received {message}")

        if isinstance(message, list):
            msg_type = message[1]
            if msg_type in self.wssactions:
                self.wssactions[msg_type]()

        # my add
        my_small = "small"
        my_nonce = "nonce"

        if my_small in message and my_nonce in message:
            self.save_message_nonce_small = message
            sleep(2)
            self.stopit()
            sleep(18)

But it can't work properly, BTW, sometimes I find a 'code': 10100 error in message log.
My message log
2018-09-24 17:26:41---{'event': 'auth', 'status': 'FAILED', 'chanId': 0, 'code': 10114, 'msg': 'nonce: small'}
2018-09-24 17:28:22---{'event': 'info', 'version': 2, 'serverId': '3db72066-7ebe-4a3a-a22f-0030404af1a3', 'platform': {'status': 1}}
2018-09-24 17:28:23---{'event': 'auth', 'status': 'FAILED', 'chanId': 0, 'code': 10114, 'msg': 'nonce: small'}
2018-09-24 17:30:04---{'event': 'info', 'version': 2, 'serverId': 'cc13cb73-fc86-4e66-96a3-95a9a2d69bb8', 'platform': {'status': 1}}
2018-09-24 17:30:04---{'event': 'auth', 'status': 'FAILED', 'chanId': 0, 'code': 10114, 'msg': 'nonce: small'}
2018-09-24 17:31:09---{'event': 'error', 'msg': 'auth: invalid', 'code': 10100}
2018-09-24 17:32:50---{'event': 'info', 'version': 2, 'serverId': 'acbd834f-0de5-4c14-ac68-cfe507cc2be2', 'platform': {'status': 1}}
2018-09-24 17:32:50---{'event': 'auth', 'status': 'FAILED', 'chanId': 0, 'code': 10114, 'msg': 'nonce: small'}
2018-09-24 17:34:31---{'event': 'info', 'version': 2, 'serverId': 'b4a03312-fd53-47cb-a752-911b35e75a09', 'platform': {'status': 1}}
2018-09-24 17:34:32---{'event': 'auth', 'status': 'FAILED', 'chanId': 0, 'code': 10114, 'msg': 'nonce: small'}
2018-09-24 17:36:13---{'event': 'info', 'version': 2, 'serverId': '11971802-74d3-4165-9130-355e5f414fdc', 'platform': {'status': 1}}
2018-09-24 17:36:13---{'event': 'auth', 'status': 'FAILED', 'chanId': 0, 'code': 10114, 'msg': 'nonce: small'}
2018-09-24 17:37:54---{'event': 'info', 'version': 2, 'serverId': 'bdc71981-2acf-4f96-8bc9-9e5c682a2590', 'platform': {'status': 1}}
2018-09-24 17:37:54---{'event': 'auth', 'status': 'FAILED', 'chanId': 0, 'code': 10114, 'msg': 'nonce: small'}

I personally feel that the 'nonce: small' problem is caused by multiple threads and local time. I install the NTP client or Simple Network Time Protocol (SNTP) client software on the service, and this problem will occur in large numbers. I find that the time of the Windows vps server always gets slower. I hope my thoughts will help, thank you very much for your program.

2018-09-27 11:47:33---{'event': 'info', 'version': 2, 'serverId': 'b8b9f009-3050-4212-a661-516913218753', 'platform': {'status': 1}}
2018-09-27 11:47:33---{'event': 'auth', 'status': 'FAILED', 'chanId': 0, 'code': 10114, 'msg': 'nonce: small'}
2018-09-27 11:47:54---{'event': 'info', 'version': 2, 'serverId': 'fd124a67-2c87-4633-8cc5-d52333870f44', 'platform': {'status': 1}}
2018-09-27 11:47:55---{'event': 'auth', 'status': 'OK', 'chanId': 0, 'userId': 2266936, 'auth_id': 'ae65a339-39a9-499c-b353-e39dc99164de', 'caps': {'orders': {'read': 1, 'write': 1}, 'account': {'read': 1, 'write': 0}, 'funding': {'read': 1, 'write': 1}, 'history': {'read': 1, 'write': 0}, 'wallets': {'read': 1, 'write': 1}, 'withdraw': {'read': 0, 'write': 0}, 'positions': {'read': 1, 'write': 1}}}
2018-09-27 11:47:55---[0, 'ps', []]
2018-09-27 11:47:55---[0, 'ws', [['exchange', 'USD', 229.08958891, 0, None], ['funding', 'USD', 0, 0, None], ['margin', 'USD', 193.58849932, 0, None], ['funding', 'EOS', 0.02105733, 0, None]]]
2018-09-27 11:47:55---[0, 'os', []]
2018-09-27 11:47:55---[0, 'fos', []]
2018-09-27 11:47:55---[0, 'fcs', []]
2018-09-27 11:47:55---[0, 'fls', []]
2018-09-27 11:56:23---{'event': 'info', 'version': 2, 'serverId': '8f1a92f8-2ddc-431a-af05-953a524a5669', 'platform': {'status': 1}}
2018-09-27 11:56:23---{'event': 'auth', 'status': 'FAILED', 'chanId': 0, 'code': 10114, 'msg': 'nonce: small'}
2018-09-27 11:56:45---{'event': 'info', 'version': 2, 'serverId': 'f4470216-4432-46bf-9b05-da935b7ea69f', 'platform': {'status': 1}}
2018-09-27 11:56:46---{'event': 'auth', 'status': 'OK', 'chanId': 0, 'userId': 2266936, 'auth_id': '7376ecac-1b83-42d0-afb1-e693d7ad157d', 'caps': {'orders': {'read': 1, 'write': 1}, 'account': {'read': 1, 'write': 0}, 'funding': {'read': 1, 'write': 1}, 'history': {'read': 1, 'write': 0}, 'wallets': {'read': 1, 'write': 1}, 'withdraw': {'read': 0, 'write': 0}, 'positions': {'read': 1, 'write': 1}}}
2018-09-27 11:56:46---[0, 'ps', []]
2018-09-27 11:56:46---[0, 'ws', [['exchange', 'USD', 229.08958891, 0, None], ['funding', 'USD', 0, 0, None], ['margin', 'USD', 193.58849932, 0, None], ['funding', 'EOS', 0.02105733, 0, None]]]
2018-09-27 11:56:46---[0, 'os', []]
2018-09-27 11:56:46---[0, 'fos', []]
2018-09-27 11:56:46---[0, 'fcs', []]
2018-09-27 11:56:46---[0, 'fls', []]
2018-09-27 11:57:13---{'event': 'info', 'version': 2, 'serverId': 'e5690e92-7ec9-44b2-85fe-33986d65f4c7', 'platform': {'status': 1}}
2018-09-27 11:57:13---{'event': 'auth', 'status': 'FAILED', 'chanId': 0, 'code': 10114, 'msg': 'nonce: small'}
2018-09-27 11:57:34---{'event': 'info', 'version': 2, 'serverId': 'a63a3127-faac-4fd8-9d6b-578bef331394', 'platform': {'status': 1}}
2018-09-27 11:57:35---{'event': 'auth', 'status': 'OK', 'chanId': 0, 'userId': 2266936, 'auth_id': '143656f3-b142-4fbd-bf46-e7d62eeebae1', 'caps': {'orders': {'read': 1, 'write': 1}, 'account': {'read': 1, 'write': 0}, 'funding': {'read': 1, 'write': 1}, 'history': {'read': 1, 'write': 0}, 'wallets': {'read': 1, 'write': 1}, 'withdraw': {'read': 0, 'write': 0}, 'positions': {'read': 1, 'write': 1}}}
2018-09-27 11:57:35---[0, 'ps', []]
2018-09-27 11:57:35---[0, 'ws', [['exchange', 'USD', 229.08958891, 0, None], ['funding', 'USD', 0, 0, None], ['margin', 'USD', 193.58849932, 0, None], ['funding', 'EOS', 0.02105733, 0, None]]]
2018-09-27 11:57:35---[0, 'os', []]
2018-09-27 11:57:35---[0, 'fos', []]
2018-09-27 11:57:35---[0, 'fcs', []]
2018-09-27 11:57:35---[0, 'fls', []]
2018-09-27 11:58:06---{'event': 'info', 'version': 2, 'serverId': '716760b0-ac2f-4899-b52e-3c60c906fa45', 'platform': {'status': 1}}
2018-09-27 11:58:06---{'event': 'auth', 'status': 'FAILED', 'chanId': 0, 'code': 10114, 'msg': 'nonce: small'}
2018-09-27 11:58:27---{'event': 'info', 'version': 2, 'serverId': '91e978e6-9332-4268-b251-01f3f1b48067', 'platform': {'status': 1}}
2018-09-27 11:58:27---{'event': 'auth', 'status': 'OK', 'chanId': 0, 'userId': 2266936, 'auth_id': '565ea33f-f2ec-4912-a598-41d81eabd3a3', 'caps': {'orders': {'read': 1, 'write': 1}, 'account': {'read': 1, 'write': 0}, 'funding': {'read': 1, 'write': 1}, 'history': {'read': 1, 'write': 0}, 'wallets': {'read': 1, 'write': 1}, 'withdraw': {'read': 0, 'write': 0}, 'positions': {'read': 1, 'write': 1}}}
2018-09-27 11:58:27---[0, 'ps', []]
2018-09-27 11:58:27---[0, 'ws', [['exchange', 'USD', 229.08958891, 0, None], ['funding', 'USD', 0, 0, None], ['margin', 'USD', 193.58849932, 0, None], ['funding', 'EOS', 0.02105733, 0, None]]]
2018-09-27 11:58:27---[0, 'os', []]
2018-09-27 11:58:27---[0, 'fos', []]
2018-09-27 11:58:27---[0, 'fcs', []]
2018-09-27 11:58:27---[0, 'fls', []]
2018-09-27 12:17:05---{'event': 'info', 'version': 2, 'serverId': '2e7e80ca-5429-42c5-91e5-da373048ee34', 'platform': {'status': 1}}
2018-09-27 12:17:05---{'event': 'auth', 'status': 'FAILED', 'chanId': 0, 'code': 10114, 'msg': 'nonce: small'}
2018-09-27 12:17:26---{'event': 'info', 'version': 2, 'serverId': '1eca6b8c-8ce4-4972-b9a4-5d271732483e', 'platform': {'status': 1}}
2018-09-27 12:17:26---{'event': 'auth', 'status': 'OK', 'chanId': 0, 'userId': 2266936, 'auth_id': 'b46f54b3-92ff-4a6b-9e8d-e12635768a66', 'caps': {'orders': {'read': 1, 'write': 1}, 'account': {'read': 1, 'write': 0}, 'funding': {'read': 1, 'write': 1}, 'history': {'read': 1, 'write': 0}, 'wallets': {'read': 1, 'write': 1}, 'withdraw': {'read': 0, 'write': 0}, 'positions': {'read': 1, 'write': 1}}}
2018-09-27 12:17:26---[0, 'ps', []]
2018-09-27 12:17:26---[0, 'ws', [['exchange', 'USD', 229.08958891, 0, None], ['funding', 'USD', 0, 0, None], ['margin', 'USD', 193.58849932, 0, None], ['funding', 'EOS', 0.02105733, 0, None]]]
2018-09-27 12:17:26---[0, 'os', []]
2018-09-27 12:17:26---[0, 'fos', []]
2018-09-27 12:17:26---[0, 'fcs', []]
2018-09-27 12:17:26---[0, 'fls', []]
2018-09-27 12:26:43---{'event': 'info', 'version': 2, 'serverId': '6c1fb10d-932e-40e3-8584-468b0c2832d8', 'platform': {'status': 1}}
2018-09-27 12:26:43---{'event': 'auth', 'status': 'FAILED', 'chanId': 0, 'code': 10114, 'msg': 'nonce: small'}
2018-09-27 12:27:04---{'event': 'info', 'version': 2, 'serverId': 'bbf92310-08fa-4bf5-98a2-776a0d4b0217', 'platform': {'status': 1}}
2018-09-27 12:27:05---{'event': 'auth', 'status': 'OK', 'chanId': 0, 'userId': 2266936, 'auth_id': '324f6b2c-e0fc-46d7-a097-d119ccd468a9', 'caps': {'orders': {'read': 1, 'write': 1}, 'account': {'read': 1, 'write': 0}, 'funding': {'read': 1, 'write': 1}, 'history': {'read': 1, 'write': 0}, 'wallets': {'read': 1, 'write': 1}, 'withdraw': {'read': 0, 'write': 0}, 'positions': {'read': 1, 'write': 1}}}
2018-09-27 12:27:05---[0, 'ps', []]
2018-09-27 12:27:05---[0, 'ws', [['exchange', 'USD', 229.08958891, 0, None], ['funding', 'USD', 0, 0, None], ['margin', 'USD', 193.58849932, 0, None], ['funding', 'EOS', 0.02105733, 0, None]]]
2018-09-27 12:27:05---[0, 'os', []]
2018-09-27 12:27:05---[0, 'fos', []]
2018-09-27 12:27:05---[0, 'fcs', []]
2018-09-27 12:27:05---[0, 'fls', []]
2018-09-27 12:42:01---{'event': 'info', 'version': 2, 'serverId': '2c1e79e0-d3ba-49ed-9170-27c5ad075565', 'platform': {'status': 1}}
2018-09-27 12:42:02---{'event': 'auth', 'status': 'FAILED', 'chanId': 0, 'code': 10114, 'msg': 'nonce: small'}
2018-09-27 12:42:23---{'event': 'info', 'version': 2, 'serverId': '6202a6a1-e15d-49ee-a4d4-ac1e44ce1ab8', 'platform': {'status': 1}}
2018-09-27 12:42:23---{'event': 'auth', 'status': 'OK', 'chanId': 0, 'userId': 2266936, 'auth_id': '596ea46a-746f-449c-9f51-d37a42d2554b', 'caps': {'orders': {'read': 1, 'write': 1}, 'account': {'read': 1, 'write': 0}, 'funding': {'read': 1, 'write': 1}, 'history': {'read': 1, 'write': 0}, 'wallets': {'read': 1, 'write': 1}, 'withdraw': {'read': 0, 'write': 0}, 'positions': {'read': 1, 'write': 1}}}
2018-09-27 12:42:23---[0, 'ps', []]
2018-09-27 12:42:23---[0, 'ws', [['exchange', 'USD', 229.08958891, 0, None], ['funding', 'USD', 0, 0, None], ['margin', 'USD', 193.58849932, 0, None], ['funding', 'EOS', 0.02105733, 0, None]]]
2018-09-27 12:42:23---[0, 'os', []]
2018-09-27 12:42:23---[0, 'fos', []]
2018-09-27 12:42:23---[0, 'fcs', []]
2018-09-27 12:42:23---[0, 'fls', []]
2018-09-27 12:47:07---{'event': 'info', 'version': 2, 'serverId': '85ca86ae-5477-482c-9c5f-5b14e9870dab', 'platform': {'status': 1}}
2018-09-27 12:47:08---{'event': 'auth', 'status': 'FAILED', 'chanId': 0, 'code': 10114, 'msg': 'nonce: small'}
2018-09-27 12:47:29---{'event': 'info', 'version': 2, 'serverId': '69441c55-e18c-4075-97ec-1494c3912605', 'platform': {'status': 1}}
2018-09-27 12:47:29---{'event': 'auth', 'status': 'OK', 'chanId': 0, 'userId': 2266936, 'auth_id': '0dcc955f-8b3d-4c2f-bcf7-0d832e9f1ac3', 'caps': {'orders': {'read': 1, 'write': 1}, 'account': {'read': 1, 'write': 0}, 'funding': {'read': 1, 'write': 1}, 'history': {'read': 1, 'write': 0}, 'wallets': {'read': 1, 'write': 1}, 'withdraw': {'read': 0, 'write': 0}, 'positions': {'read': 1, 'write': 1}}}
2018-09-27 12:47:29---[0, 'ps', []]
2018-09-27 12:47:29---[0, 'ws', [['exchange', 'USD', 229.08958891, 0, None], ['funding', 'USD', 0, 0, None], ['margin', 'USD', 193.58849932, 0, None], ['funding', 'EOS', 0.02105733, 0, None]]]
2018-09-27 12:47:29---[0, 'os', []]
2018-09-27 12:47:29---[0, 'fos', []]
2018-09-27 12:47:29---[0, 'fcs', []]
2018-09-27 12:47:29---[0, 'fls', []]

I found one thing, I don't know if it is correct.

bitfinex/bitfinex/websockets/client.py

  def authenticate(self, callback, filters=None):
        nonce = int(wss_utils.UtcNow() * 1000000)

*But the Time is already 10000000
bitfinex/bitfinex/websockets/wss_utils.py
def UtcNow():
    now = datetime.datetime.utcnow()
    return int(float(now.strftime("%s.%f"))*10000000)

  def ping(self, channel="auth"):
        """Ping bitfinex."""
        client_cid = wss_utils.UtcNow()
        data = {
            'event': 'ping',
            'cid': client_cid
        }

        client_order_id = wss_utils.UtcNow()
        order_op = {
            'cid': client_order_id,
            'type': order_type,
            'symbol': wss_utils.order_pair(pair),
            'amount': amount,
            'price': price,
            'hidden': hidden,
            "flags": sum(flags),
        }

Hmm that's true... I seem to remember messing a bit with this. So i guess i forgot to remove the multiplier in th authenticate message.
However the problem in this issue is related to the client_id (or client_cid :roll_eyes: as i managed to write this as) is not relevant here i think as it does not affect the nonce.
I think the problem is that the rest api is using a different way to calculate the nounce:
https://github.com/ohenrik/bitfinex/blob/master/bitfinex/rest/restv2.py#L40-L56
This needs to be the same, using the same multiplier. Also the websocket version should allow users to change this.
As to your earlier comment. All the nonce to small messages are related to the client trying to connection with authentication. If you are using machines that have the clock set differently (and not just the time zones set differently) this might be the problem.

might be worth to add that a complete new API key needs to be created once its been used with a websocket connection. For using the v2 rest api that is.

@judasbenhur thats a good point, we have now updated the nonce logic so that it is the same on all api versions. However people probably need to use a new key for websockets in version 1.0.0 of the library, so ill add a note about that.

authors: gaorufeng judasbenhur ohenrik

repo: ohenrik/bitfinex


text:
[Meso] research Pacific region

Research Pacific region sites from this photo from the Museo Anthropologia de Mexico

Some more including trade with US region tribes

More sites

Some verbiage on conquest in Pacific region

Some more regional info

repo: ohmec/ohmec


text:
webdash: optimize task list

closes #547

Also, closes #384 ...maybe
I added code to cache tasks in the browser, use the minimal view where possible, and stop the refresh loop when the page/tab is in the background.
It's still not ideal, but it's a substantial improvement. Previously, our task list was requesting about 500-800MB every two seconds, even when you weren't looking. Now, it's about 500 bytes when nothing has changed and nothing is running.
The page load is still slow on the first load (although faster than before). This might be improved in a number of ways: partial list rendering, server-side rendering, etc.
Our task views are kinda clunky. The basic view can still be pretty heavy, and the list doesn't need most of that weight (~500-700KB). We could improve this substantially by having server-side support for requesting specific fields, and/or being able to subscribe to an event stream.

This looks like a great improvement.  Could you apply the stoping of the background refresh loop while the page is in the background behavior to the task, node list and node pages as well?

Could you apply the stoping of the background refresh loop while the page is in the background behavior to the task, node list and node pages as well?

Done

authors: adamstruck buchanae

repo: ohsu-comp-bio/funnel

license: mit


text:
Code Completion hint stays open until I click

When a code completion hint shows up it will stay up until I either click or get another hint which then stays on screen.

moving cursor or pressing ESC will not close it?

Sometimes, you would want to tip to just go away when you continue typing because it blocks the view.
Better yet, just raise the Y value of the tooltip by several pixels so it becomes non-blocking for the line in question.

I agree it should be dismissed automatically (somehow) as you continue to type, especially after moving to the next line.

i seriously don't see the problem, could you be more specific :)

Try this to reproduce:

Start a new script
In _init start a for loop
When the tool tip pops up showing the range() usage, it stays up even after completing the for line
Type a few more lines (without clicking the mouse)

The tool tip stays one line above the cursor covering up the previous line:

I can't reproduce this issue in the current master branch, the tooltip is discarded as soon as the closing parenthesis is added in range(100). Assuming it has thus been fixed.

authors: Ace-Dragon akien-mga kbdavidson reduz thecodethinker

repo: okamstudio/godot


text:
🛑 Ekşi Sözlük is down

In 1d96b90, Ekşi Sözlük (https://eksisozluk.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Ekşi Sözlük is back up in 33232f5.

repo: okankocyigit/upptime


text:
ConsoleNotificationSyncDegraded during upgrade from latest 4.11 to 12

Hi.
Upgrade from latest 4.11 to 4.12 stuck with openshift-console operator degraded.
ConsoleNotificationSyncDegraded: rpc error: code = Unavailable desc = keepalive ping failed to receive ACK within timeout
Is this relatet to the banner which is automatically added on the top of web console?

must-gather.tar.gz

Upstream issue: https://issues.redhat.com//browse/OCPBUGS-6488
console-operator mistakenly keeps Degraded status although all is now well

Something new here?

Hello! I have same problem.
4h57m       Normal    OperatorStatusChanged    deployment/console-operator              Status for clusteroperator/console changed: Degraded message changed from "ConfigMapSyncDegraded: the server is currently unable to handle the request (get oauthclients.oauth.openshift.io console)\nConsoleNotificationSyncDegraded: etcdserver: request timed out" to "ConfigMapSyncDegraded: the server is currently unable to handle the request (get oauthclients.oauth.openshift.io console)\nConsoleNotificationSyncDegraded: etcdserver: request timed out\nSyncLoopRefreshDegraded: routes.route.openshift.io \"console\" is forbidden: User \"system:anonymous\" cannot get resource \"routes\" in API group \"route.openshift.io\" in the namespace \"openshift-console\""
4h38m       Warning   FastControllerResync     deployment/console-operator              Controller "HealthCheckController" resync interval is set to 30s which might lead to client request throttling
4h38m       Warning   FastControllerResync     deployment/console-operator              Controller "UnsupportedConfigOverridesController" resync interval is set to 0s which might lead to client request throttling
4h38m       Warning   FastControllerResync     deployment/console-operator              Controller "LoggingSyncer" resync interval is set to 0s which might lead to client request throttling
4h38m       Normal    OperatorStatusChanged    deployment/console-operator              Status for clusteroperator/console changed: Degraded message changed from "ConfigMapSyncDegraded: the server is currently unable to handle the request (get oauthclients.oauth.openshift.io console)\nConsoleNotificationSyncDegraded: etcdserver: request timed out\nSyncLoopRefreshDegraded: routes.route.openshift.io \"console\" is forbidden: User \"system:anonymous\" cannot get resource \"routes\" in API group \"route.openshift.io\" in the namespace \"openshift-console\"" to "ConfigMapSyncDegraded: the server is currently unable to handle the request (get oauthclients.oauth.openshift.io console)\nConsoleNotificationSyncDegraded: etcdserver: request timed out\nCustomRouteSyncDegraded: rpc error: code = Unknown desc = malformed header: missing HTTP content-type\nSyncLoopRefreshDegraded: routes.route.openshift.io \"console\" is forbidden: User \"system:anonymous\" cannot get resource \"routes\" in API group \"route.openshift.io\" in the namespace \"openshift-console\""
4h38m       Normal    OperatorStatusChanged    deployment/console-operator              Status for clusteroperator/console changed: Degraded message changed from "ConfigMapSyncDegraded: the server is currently unable to handle the request (get oauthclients.oauth.openshift.io console)\nConsoleNotificationSyncDegraded: etcdserver: request timed out\nCustomRouteSyncDegraded: rpc error: code = Unknown desc = malformed header: missing HTTP content-type\nSyncLoopRefreshDegraded: routes.route.openshift.io \"console\" is forbidden: User \"system:anonymous\" cannot get resource \"routes\" in API group \"route.openshift.io\" in the namespace \"openshift-console\"" to "ConfigMapSyncDegraded: the server is currently unable to handle the request (get oauthclients.oauth.openshift.io console)\nConsoleNotificationSyncDegraded: etcdserver: request timed out\nSyncLoopRefreshDegraded: routes.route.openshift.io \"console\" is forbidden: User \"system:anonymous\" cannot get resource \"routes\" in API group \"route.openshift.io\" in the namespace \"openshift-console\""
4h38m       Normal    OperatorStatusChanged    deployment/console-operator              Status for clusteroperator/console changed: Degraded message changed from "ConfigMapSyncDegraded: the server is currently unable to handle the request (get oauthclients.oauth.openshift.io console)\nConsoleNotificationSyncDegraded: etcdserver: request timed out\nSyncLoopRefreshDegraded: routes.route.openshift.io \"console\" is forbidden: User \"system:anonymous\" cannot get resource \"routes\" in API group \"route.openshift.io\" in the namespace \"openshift-console\"" to "ConsoleNotificationSyncDegraded: etcdserver: request timed out"
3h3m        Normal    OperatorStatusChanged    deployment/console-operator              Status for clusteroperator/console changed: Degraded message changed from "ConsoleNotificationSyncDegraded: etcdserver: request timed out" to "ConsoleNotificationSyncDegraded: etcdserver: request timed out\nRouteHealthDegraded: failed to GET route (https://console-openshift-console.apps.dev.local.lan): Get \"https://console-openshift-console.apps.dev.local.lan\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)",Available changed from True to False ("RouteHealthAvailable: failed to GET route (https://console-openshift-console.apps.dev.local.lan): Get \"https://console-openshift-console.apps.dev.local.lan\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)")
3h3m        Normal    OperatorStatusChanged    deployment/console-operator              Status for clusteroperator/console changed: Degraded message changed from "ConsoleNotificationSyncDegraded: etcdserver: request timed out\nRouteHealthDegraded: failed to GET route (https://console-openshift-console.apps.dev.local.lan): Get \"https://console-openshift-console.apps.dev.local.lan\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)" to "ConsoleNotificationSyncDegraded: etcdserver: request timed out",Available changed from False to True ("All is well")

I suppose the error is in response from download application:
~ curl -k https://downloads-openshift-console.apps.libvirt.alma.lan
<!doctype html>

**

**

license
oc (amd64 linux) (tar zip)
oc (amd64 mac) (tar zip)
oc (amd64 windows) (tar zip)
oc (arm64 linux) (tar zip)
oc (arm64 mac) (tar zip)
oc (ppc64le linux) (tar zip)
oc (s390x linux) (tar zip)

Upstream issue: https://issues.redhat.com//browse/OCPBUGS-6488
console-operator mistakenly keeps Degraded status although all is now well

This issue is missed and cannot be opened!

Hi, Same problem here updating from 4.12.0-0.okd-2023-01-21-055900 to 4.12.0-0.okd-2023-02-04-212953.
Operator console Stuck in "Degraded State", even if reporting "All is well."

Fix for this landed in recent nightlies - https://github.com/openshift/console-operator/pull/728

Fix for this landed in recent nightlies - openshift/console-operator#728

Great news, but now i'm figuring out how to "manually" report (as should be done by operator here ), to unstuck upgrade...  any ideas?

Check if deleting console-operator pod fixes it?

deleting console pod, download pod and console-operator pod doesn't solves...

Same here. It does not fixe it.

@dkoci Standing to https://github.com/openshift/console-operator/pull/728, it looks just a labeling issue. I managed to solve in the WORST you can imagine: editing etcd. I think it should be avoided in any case, but now update is going on.
Backup Etcd -> Ensure is a good Backup
oc project openshift-etcd
oc get pods
oc rsh etcd-<cluster-name>-<pod-istance>-master-0
etcdctl put /kubernetes.io/operator.openshift.io/consoles/cluster '{"apiVersion":"operator.openshift.io/v1","kind":"Console","metadata":{"annotations":{"include.release.openshift.io/ibm-cloud-managed":"true","include.release.openshift.io/self-managed-high-availability":"true","include.release.openshift.io/single-node-developer":"true","release.openshift.io/create-only":"true"},"creationTimestamp":"2022-10-14T13:29:40Z","generation":3,"managedFields":[{"apiVersion":"operator.openshift.io/v1","fieldsType":"FieldsV1","fieldsV1":{"f:metadata":{"f:annotations":{".":{},"f:include.release.openshift.io/ibm-cloud-managed":{},"f:include.release.openshift.io/self-managed-high-availability":{},"f:include.release.openshift.io/single-node-developer":{},"f:release.openshift.io/create-only":{}},"f:ownerReferences":{".":{},"k:{\"uid\":\"aea61e81-3f75-459b-a6a2-06978bc702b9\"}":{}}},"f:spec":{".":{},"f:logLevel":{},"f:managementState":{},"f:operatorLogLevel":{}}},"manager":"cluster-version-operator","operation":"Update","time":"2022-10-14T13:29:40Z"},{"apiVersion":"operator.openshift.io/v1","fieldsType":"FieldsV1","fieldsV1":{"f:status":{}},"manager":"Go-http-client","operation":"Update","subresource":"status","time":"2023-02-08T18:03:40Z"},{"apiVersion":"operator.openshift.io/v1","fieldsType":"FieldsV1","fieldsV1":{"f:status":{"f:conditions":{},"f:generations":{},"f:observedGeneration":{},"f:readyReplicas":{}}},"manager":"console","operation":"Update","subresource":"status","time":"2023-02-08T19:19:44Z"}],"name":"cluster","ownerReferences":[{"apiVersion":"config.openshift.io/v1","kind":"ClusterVersion","name":"version","uid":"aea61e81-3f75-459b-a6a2-06978bc702b9"}],"uid":"51a1c4ef-fc4a-4835-909a-d937fbd816fc"},"spec":{"logLevel":"Normal","managementState":"Managed","operatorLogLevel":"Normal"},"status":{"conditions":[{"lastTransitionTime":"2023-02-06T10:04:13Z","status":"False","type":"PDBSyncDegraded"},{"lastTransitionTime":"2022-10-14T13:30:08Z","status":"False","type":"PDBSyncProgressing"},{"lastTransitionTime":"2022-10-14T13:30:08Z","reason":"NoUnsupportedConfigOverrides","status":"True","type":"UnsupportedConfigOverridesUpgradeable"},{"lastTransitionTime":"2022-10-14T13:30:09Z","status":"False","type":"ManagementStateDegraded"},{"lastTransitionTime":"2022-10-14T13:30:12Z","status":"False","type":"ResourceSyncControllerDegraded"},{"lastTransitionTime":"2023-02-06T10:04:14Z","status":"False","type":"DownloadsDeploymentSyncDegraded"},{"lastTransitionTime":"2022-10-14T13:30:14Z","status":"False","type":"DownloadsDeploymentSyncProgressing"},{"lastTransitionTime":"2023-01-31T13:43:52Z","status":"False","type":"CustomRouteSyncDegraded"},{"lastTransitionTime":"2022-10-14T13:30:15Z","status":"False","type":"CustomRouteSyncProgressing"},{"lastTransitionTime":"2023-01-31T13:43:53Z","status":"False","type":"DefaultRouteSyncDegraded"},{"lastTransitionTime":"2022-10-14T13:30:15Z","status":"False","type":"DefaultRouteSyncProgressing"},{"lastTransitionTime":"2023-02-08T14:46:31Z","status":"False","type":"RouteHealthDegraded"},{"lastTransitionTime":"2022-10-14T13:30:17Z","status":"False","type":"RouteHealthProgressing"},{"lastTransitionTime":"2023-02-08T14:46:31Z","status":"True","type":"RouteHealthAvailable"},{"lastTransitionTime":"2022-10-14T13:30:19Z","status":"False","type":"ServiceSyncDegraded"},{"lastTransitionTime":"2022-10-14T13:30:19Z","status":"False","type":"ServiceSyncProgressing"},{"lastTransitionTime":"2023-02-02T13:38:10Z","status":"False","type":"SyncLoopRefreshDegraded"},{"lastTransitionTime":"2023-02-08T19:19:16Z","status":"False","type":"SyncLoopRefreshProgressing"},{"lastTransitionTime":"2023-01-17T17:39:12Z","status":"False","type":"RedirectServiceSyncDegraded"},{"lastTransitionTime":"2022-10-14T13:30:36Z","status":"False","type":"RedirectServiceSyncProgressing"},{"lastTransitionTime":"2022-10-14T13:41:09Z","status":"False","type":"OCDownloadsSyncDegraded"},{"lastTransitionTime":"2023-01-16T11:36:17Z","status":"False","type":"ODODownloadsSyncDegraded"},{"lastTransitionTime":"2023-01-17T12:30:39Z","status":"False","type":"ManagedClusterConfigSyncDegraded"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"ManagedClusterConfigSyncProgressing"},{"lastTransitionTime":"2023-02-06T10:04:35Z","status":"False","type":"ConfigMapSyncDegraded"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"ConfigMapSyncProgressing"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"ServiceCASyncDegraded"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"ServiceCASyncProgressing"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"TrustedCASyncDegraded"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"TrustedCASyncProgressing"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"CustomLogoSyncDegraded"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"CustomLogoSyncProgressing"},{"lastTransitionTime":"2023-01-16T17:40:13Z","status":"False","type":"OAuthServingCertValidationDegraded"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"OAuthServingCertValidationProgressing"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"OAuthClientSecretSyncDegraded"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"OAuthClientSecretSyncProgressing"},{"lastTransitionTime":"2023-02-06T10:04:35Z","status":"False","type":"OAuthClientSyncDegraded"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"OAuthClientSyncProgressing"},{"lastTransitionTime":"2022-11-28T17:50:48Z","status":"False","type":"DeploymentSyncDegraded"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"DeploymentSyncProgressing"},{"lastTransitionTime":"2023-01-16T16:56:50Z","status":"True","type":"DeploymentAvailable"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"ConsoleConfigDegraded"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"ConsolePublicConfigMapDegraded"},{"lastTransitionTime":"2023-02-06T10:04:10Z","status":"False","type":"ConsoleNotificationSyncDegraded"},{"lastTransitionTime":"2023-02-06T10:04:10Z","status":"False","type":"ConsoleNotificationSyncProgressing"}],"generations":[{"group":"apps","hash":"","lastGeneration":7,"name":"downloads","namespace":"openshift-console","resource":"deployments"},{"group":"apps","hash":"","lastGeneration":16,"name":"console","namespace":"openshift-console","resource":"deployments"}],"observedGeneration":3,"readyReplicas":2}}'

It looks it worked for me but I think this is a REALLY bad thing to do. Obviously i did it in my test cluster.

@kalik1 thanks for sharing. This will be the last option because I dont want to mess with etcd. @vrutkovs is there any other option to unstuck it?

@kalik1 thanks for sharing. This will be the last option because I dont want to mess with etcd. @vrutkovs is there any other option to unstuck it?

I totally agree...

After pod operator pod deletion, error is: ConsoleNotificationSyncDegraded: etcdserver: request timed out

Kubernetes (OKD OpenShift) writs in ETCD through API and the json format of the keys and values look like this:
The new value should be in base64 format. I didn't try to edit the ETCD DB. If someone try it, please give us a feedback :-)
[root@libvirt-cp-1 /]# etcdctl get /kubernetes.io/operator.openshift.io/consoles/cluster -w=json
{"header":{"cluster_id":5634154139435658575,"member_id":6048843481634052877,"revision":168621632,"raft_term":46266},"kvs":[{"key":"L2t1YmVybmV0ZXMuaW8vb3BlcmF0b3Iub3BlbnNoaWZ0LmlvL2NvbnNvbGVzL2NsdXN0ZXI=","create_revision":25166,"mod_revision":168557637,"version":43630,"value":"[encoded data, 9092 characters]"}],"count":1}

Kubernetes (OKD OpenShift) writs in ETCD through API and the json format of the keys and values look like this: The new value should be in base64 format. I didn't try to edit the ETCD DB. If someone try it, please give us a feedback :-)
[root@libvirt-cp-1 /]# etcdctl get /kubernetes.io/operator.openshift.io/consoles/cluster -w=json
{"header":{"cluster_id":5634154139435658575,"member_id":6048843481634052877,"revision":168621632,"raft_term":46266},"kvs":[{"key":"L2t1YmVybmV0ZXMuaW8vb3BlcmF0b3Iub3BlbnNoaWZ0LmlvL2NvbnNvbGVzL2NsdXN0ZXI=","create_revision":25166,"mod_revision":168557637,"version":43630,"value":"[encoded data, 9092 characters]"}],"count":1}

@madpearl if you just use etcdctl put /kubernetes.io/operator.openshift.io/consoles/cluster  '<json-data>'  you can update the value of the key (note the  ') ...

@kalik1 can you give us the output of etcdctl get /kubernetes.io/operator.openshift.io/consoles/cluster -w=json and
etcdctl get /kubernetes.io/operator.openshift.io/consoles/cluster -w=simple
Thanks!

... I'm not getting the point, but those are the results:
sh-4.4# etcdctl get /kubernetes.io/operator.openshift.io/consoles/cluster -w=json
{"header":{"cluster_id":5715281520808535666,"member_id":7350831208949681494,"revision":179173692,"raft_term":542},"kvs":[{"key":"L2t1YmVybmV0ZXMuaW8vb3BlcmF0b3Iub3BlbnNoaWZ0LmlvL2NvbnNvbGVzL2NsdXN0ZXI=","create_revision":19325,"mod_revision":178209300,"version":1971,"value":"[encoded data, 8728 characters]"}],"count":1}

sh-4.4# etcdctl get /kubernetes.io/operator.openshift.io/consoles/cluster -w=simple
/kubernetes.io/operator.openshift.io/consoles/cluster
{"apiVersion":"operator.openshift.io/v1","kind":"Console","metadata":{"annotations":{"include.release.openshift.io/ibm-cloud-managed":"true","include.release.openshift.io/self-managed-high-availability":"true","include.release.openshift.io/single-node-developer":"true","release.openshift.io/create-only":"true"},"creationTimestamp":"2022-10-14T13:29:40Z","generation":3,"managedFields":[{"apiVersion":"operator.openshift.io/v1","fieldsType":"FieldsV1","fieldsV1":{"f:metadata":{"f:annotations":{".":{},"f:include.release.openshift.io/ibm-cloud-managed":{},"f:include.release.openshift.io/self-managed-high-availability":{},"f:include.release.openshift.io/single-node-developer":{},"f:release.openshift.io/create-only":{}},"f:ownerReferences":{".":{},"k:{\"uid\":\"aea61e81-3f75-459b-a6a2-06978bc702b9\"}":{}}},"f:spec":{".":{},"f:logLevel":{},"f:managementState":{},"f:operatorLogLevel":{}}},"manager":"cluster-version-operator","operation":"Update","time":"2022-10-14T13:29:40Z"},{"apiVersion":"operator.openshift.io/v1","fieldsType":"FieldsV1","fieldsV1":{"f:status":{}},"manager":"Go-http-client","operation":"Update","subresource":"status","time":"2023-02-08T18:03:40Z"},{"apiVersion":"operator.openshift.io/v1","fieldsType":"FieldsV1","fieldsV1":{"f:status":{"f:conditions":{},"f:generations":{},"f:observedGeneration":{},"f:readyReplicas":{}}},"manager":"console","operation":"Update","subresource":"status","time":"2023-02-09T11:05:37Z"}],"name":"cluster","ownerReferences":[{"apiVersion":"config.openshift.io/v1","kind":"ClusterVersion","name":"version","uid":"aea61e81-3f75-459b-a6a2-06978bc702b9"}],"uid":"51a1c4ef-fc4a-4835-909a-d937fbd816fc"},"spec":{"logLevel":"Normal","managementState":"Managed","operatorLogLevel":"Normal"},"status":{"conditions":[{"lastTransitionTime":"2023-02-06T10:04:13Z","status":"False","type":"PDBSyncDegraded"},{"lastTransitionTime":"2022-10-14T13:30:08Z","status":"False","type":"PDBSyncProgressing"},{"lastTransitionTime":"2022-10-14T13:30:08Z","reason":"NoUnsupportedConfigOverrides","status":"True","type":"UnsupportedConfigOverridesUpgradeable"},{"lastTransitionTime":"2022-10-14T13:30:09Z","status":"False","type":"ManagementStateDegraded"},{"lastTransitionTime":"2022-10-14T13:30:12Z","status":"False","type":"ResourceSyncControllerDegraded"},{"lastTransitionTime":"2023-02-06T10:04:14Z","status":"False","type":"DownloadsDeploymentSyncDegraded"},{"lastTransitionTime":"2022-10-14T13:30:14Z","status":"False","type":"DownloadsDeploymentSyncProgressing"},{"lastTransitionTime":"2023-01-31T13:43:52Z","status":"False","type":"CustomRouteSyncDegraded"},{"lastTransitionTime":"2022-10-14T13:30:15Z","status":"False","type":"CustomRouteSyncProgressing"},{"lastTransitionTime":"2023-01-31T13:43:53Z","status":"False","type":"DefaultRouteSyncDegraded"},{"lastTransitionTime":"2022-10-14T13:30:15Z","status":"False","type":"DefaultRouteSyncProgressing"},{"lastTransitionTime":"2023-02-09T11:05:37Z","status":"False","type":"RouteHealthDegraded"},{"lastTransitionTime":"2022-10-14T13:30:17Z","status":"False","type":"RouteHealthProgressing"},{"lastTransitionTime":"2023-02-09T11:05:37Z","status":"True","type":"RouteHealthAvailable"},{"lastTransitionTime":"2022-10-14T13:30:19Z","status":"False","type":"ServiceSyncDegraded"},{"lastTransitionTime":"2022-10-14T13:30:19Z","status":"False","type":"ServiceSyncProgressing"},{"lastTransitionTime":"2023-02-02T13:38:10Z","status":"False","type":"SyncLoopRefreshDegraded"},{"lastTransitionTime":"2023-02-08T19:19:16Z","status":"False","type":"SyncLoopRefreshProgressing"},{"lastTransitionTime":"2023-01-17T17:39:12Z","status":"False","type":"RedirectServiceSyncDegraded"},{"lastTransitionTime":"2022-10-14T13:30:36Z","status":"False","type":"RedirectServiceSyncProgressing"},{"lastTransitionTime":"2022-10-14T13:41:09Z","status":"False","type":"OCDownloadsSyncDegraded"},{"lastTransitionTime":"2023-01-16T11:36:17Z","status":"False","type":"ODODownloadsSyncDegraded"},{"lastTransitionTime":"2023-01-17T12:30:39Z","status":"False","type":"ManagedClusterConfigSyncDegraded"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"ManagedClusterConfigSyncProgressing"},{"lastTransitionTime":"2023-02-08T21:45:26Z","status":"False","type":"ConfigMapSyncDegraded"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"ConfigMapSyncProgressing"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"ServiceCASyncDegraded"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"ServiceCASyncProgressing"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"TrustedCASyncDegraded"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"TrustedCASyncProgressing"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"CustomLogoSyncDegraded"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"CustomLogoSyncProgressing"},{"lastTransitionTime":"2023-01-16T17:40:13Z","status":"False","type":"OAuthServingCertValidationDegraded"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"OAuthServingCertValidationProgressing"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"OAuthClientSecretSyncDegraded"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"OAuthClientSecretSyncProgressing"},{"lastTransitionTime":"2023-02-06T10:04:35Z","status":"False","type":"OAuthClientSyncDegraded"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"OAuthClientSyncProgressing"},{"lastTransitionTime":"2022-11-28T17:50:48Z","status":"False","type":"DeploymentSyncDegraded"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"DeploymentSyncProgressing"},{"lastTransitionTime":"2023-01-16T16:56:50Z","status":"True","type":"DeploymentAvailable"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"ConsoleConfigDegraded"},{"lastTransitionTime":"2022-10-14T13:41:12Z","status":"False","type":"ConsolePublicConfigMapDegraded"},{"lastTransitionTime":"2023-02-08T21:43:17Z","status":"False","type":"ConsoleNotificationSyncDegraded"},{"lastTransitionTime":"2023-02-06T10:04:10Z","status":"False","type":"ConsoleNotificationSyncProgressing"}],"generations":[{"group":"apps","hash":"","lastGeneration":7,"name":"downloads","namespace":"openshift-console","resource":"deployments"},{"group":"apps","hash":"","lastGeneration":16,"name":"console","namespace":"openshift-console","resource":"deployments"}],"observedGeneration":3,"readyReplicas":2}}

@kalik1 Thank you for your response! The point was to check if the new value is encrypted with json output format. In your post before, was an etcdserver with request timeout  after the changing the value  and I thought it will a further upgrade problem for the cluster.
Ich danke dir, noch einmal! ( Thank you one more time!)

I've applied the "etcd editing" solution from @kalik1 and it works without etcdserver timeout message

Now I have some machine config pools issue:
 "failed to update OS to quay.io/openshift/okd-content@sha256:01d90a996a2e78a0486616a0adba0733db428f5a1074976054cedff62f17b2ac : error running rpm-ostree rebase --experimental ostree-unverified-registry:quay.io/openshift/okd-content@sha256:01d90a996a2e78a0486616a0adba0733db428f5a1074976054cedff62f17b2ac: \x1b[0m\x1b[31merror: \x1b[0mNo enabled repositories\n: exit status 1"

/run/bin/machine-config-daemon pivot "quay.io/openshift/okd-content@sha256:01d90a996a2e78a0486616a0adba0733db428f5a1074976054cedff62f17b2ac"

@madpearl thank you! Must be run on all machines (all masters and all workers)?

Please stay on topic. Comments like "fix when", "I have this too" and "there's another issue" are not helping others to fix the problem

Sorry, I will create separate topic for my issue.

The fix landed in https://github.com/okd-project/okd/releases/tag/4.12.0-0.okd-2023-02-18-033438

The fix landed in https://github.com/okd-project/okd/releases/tag/4.12.0-0.okd-2023-02-18-033438

how to get the update to install though, as it's complaining about the console operator being degraded, so the update is failing?
Thanks
$ oc adm upgrade
Error while reconciling 4.12.0-0.okd-2023-02-04-212953: the cluster operator console is degraded

Upstream: https://amd64.origin.releases.ci.openshift.org/graph
Channel: stable-4

Recommended updates:

  VERSION                        IMAGE
  4.12.0-0.okd-2023-02-18-033438 registry.ci.openshift.org/origin/release@sha256:fd08a1dae13a434729451cdb6edd969714a4329904e8d27eb45d94e96021dff4

Try kubectl edit --subresource=status (you need recent oc for that) or check out previous comments for etcdctl way (and make sure you make etcd backups)

https://docs.openshift.com/container-platform/4.12/cli_reference/openshift_cli/developer-cli-commands.html
 # Edit the deployment/mydeployment's status subresource

  oc edit deployment mydeployment --subresource='status'

ok thanks.
I could remove the error doing an oc edit consoles.operator.openshift.io cluster --subresource=status to remove the message and reason fields under ConsoleNotificationSyncDegraded, and could update the cluster after that

authors: MSI77 dkoci grozan kalik1 madpearl vrutkovs

repo: okd-project/okd


text:
Dropping from an open file picker crashes chrome

Do you want to request a feature or report a bug?

I found a bug

What is the current behavior?
In Chrome If you click the dropzone to open a file picker, then drop from the open file picker to the dropzone, then hit cancel on the file picker, then (sometimes) chrome will become non responsive and crash
If the current behavior is a bug, please provide the steps to reproduce.

click the dropzone to open a file picker
Drag and drop a file from the file picker to the dropzone
Close the file picker by clicking cancel ( not by clicking open )

Sometimes (but not always) chrome becomes non responsive and force closes.
What is the expected behavior?
Either of:

Dropping shouldn't be allowed while the file dialog is open.
It should work the same as any other drop and not crash the browser.

If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Operating System and react-dropzone version.
Chrome Version 57.0.2987.133 (64-bit)
Windows 7 professional Service pack 1
react dropzone version 3.13.1. (Have also managed to reproduce this on the demo site https://react-dropzone.netlify.com/)

As noted in https://github.com/enyo/dropzone/issues/669 this seems to be a Chrome/Chromium (and Opera?!) issue.

Issue in Chromium Bug Tracker (Listed as WontFix...)
Thread on Google Products thinger about Chrome

repo: okonet/react-dropzone


text:
Change std::tm to time_point and add "date.h"

Hi,
Here is my proposal of changing std::tm to std::chrono::time_point And include "date.h" dock here and presentation at cppcon
Plus:

more c++11
more portable
is smaller (8 bytes) std::tm (52 bytes)
compiler catch errors

Minus:

slower (avg: ~1.731 us (date.h) to ~0.820 us (std::tm) for RFC1123 parsing)

This is better (in my opinion) solution for #131.

I have mixed feelings on merging this PR.  It introduces an additional namespace with a really generic name ("date") that might cause conflicts with other projects that link against pistache.io.  I do not know how others feel about the performance impact either.  However, I like the idea of use more c++11 and less "".
Opinions, anyone?

You can find sources here. The author of this is the same that author of <chrono>. I made this PR because pistache can't compile to musl target. This PR solve this.
If u don't like that "data" namespace you can use https://github.com/oktal/pistache/pull/131. I don't know that work or not. I don't use pistache anymore. But check also that.

I do not know how others feel about the performance impact either.
Remember. Correctness first.

xoac, your arguments are persuasive.
I've tested your PR on Gentoo Linux w/ gcc 7.3.9-r3 and Ubunut 16.04.3 (LTS) w/ gcc 5.4.0.  Both compile cleanly, pass the test, and my own app runs fine.
I will merge this PR and humbly ask that you cancel #131, if appropriate.

I have used this PRs to make server pistache stable for me (inside docker app). But my apps wasn't heavy loaded and device was single core.
source=("${pkgname%}::git://github.com/oktal/pistache.git"
        # '00001-support-musl.patch::https://github.com/oktal/pistache/pull/131.patch'
        '00002-support-musl.patch::https://github.com/oktal/pistache/pull/132.patch'
        # '00001-Check-inflightRequests.patch::https://github.com/oktal/pistache/pull/118.patch'
        '00002-inflightRequests.patch::https://github.com/oktal/pistache/pull/154.patch'
        '00001-prevent-race.patch::https://github.com/oktal/pistache/pull/119.patch'
        '00001-increase_max_buff.patch::https://github.com/xoac/pistache/pull/1.patch'
        '00001-memory-leak-fix.patch::https://github.com/oktal/pistache/pull/130.patch'
        '00001-fd-leak-fix.patch::https://github.com/oktal/pistache/pull/39.patch'
        "00001-application_octet_stream.patch::https://github.com/oktal/pistache/pull/153.patch"
        "00001-add_str_method_to_query.patch::https://github.com/oktal/pistache/pull/172.patch"
    )
md5sums=('SKIP'
         '3d8eeea14268d23c7de727d792483021'
         '2a7f958b243af49424b913877b92c331'
         'd924b911437476a5e3e495502605afc8'
         'f093da038a6cc650098667b0e71510ee'
         'bb6e2d9b3b81dd1385a19252b218fe7c'
         '4c62fe4a722d4ad866c8385848d24e2a'
         'b01d1953664504a2a29d95de45589dca'
         'da313d26d48215a07811a8e355e759aa')

xoac,
Thank you for your curated list of issues.  For each patch that is in "octal/pistache", I either merged it or left feedback.  Hopefully we'll get #205 merged and then you can drop xoac/pistache#1.

repo: oktal/pistache


text:
allow to parse error responses from fetch API

This PR introduces errorResponse parser so that we don't need to parse e.g. JSON errors in the user space.

Found a bug in this PR. Closing for now before I find a fix.

repo: okwolf/hyperapp-fx


text:
Cleaning up the proto API of the proxy, and the library API as well.

This changes the remote library API -- now runRemote command accepts a proto instead of JCommander options, which makes it much easier to use. This also gets rid of a couple of ugly hacks.
Commands change:

proxy_stats command now accepts an optional command_id to narrow down by.
proxy_print_command only pretty-prints the command (using proxy_stats underneath), to get the RunRecord proto use proxy_stats instead.
Will update documentation separately.

Will that require changes to rbecc?

It includes changes to rbecc.
On Tue, Apr 30, 2019 at 7:49 AM ramymedhat notifications@github.com wrote:

Will that require changes to rbecc?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ola-rozenfeld/tools_remote/pull/18#issuecomment-487921729,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGFAVOF654BYETL5G25T22DPTAW4XANCNFSM4HI7ACXQ
.

Addressing Kaveh's offline comments: split the proxy service into two services and proto files.

Oops, sorry missed this, was too early in the day!

It includes changes to rbecc.
…
On Tue, Apr 30, 2019 at 7:49 AM ramymedhat @.***> wrote: Will that require changes to rbecc? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#18 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AGFAVOF654BYETL5G25T22DPTAW4XANCNFSM4HI7ACXQ .

this is kind of how I would organized the proto
not that my way of reorganizing it is better, I think it is partly personal style really :), I don't see a problem with how you have organized it, just in case there is some ideas you might like and find interesting.
btw, I am not sure the streaming is really required for proxy protocol, is the caller likely to take any action in the middle of the execution? if not I would probably drop it and simplify the usage, and if later it is needed would add a GetCommandStatus or something like that.
also you might want to think about how to extend it to support multiple runs (i.e. passing local execution root) and also being able to use different instances/pools without restarting the proxy. In the long run, people would not like to need to restart the proxy, they would like to start it once and then do the rest as without thinking about it I think.
service Commands {
  rpc RunCommand (RunCommandRequest) returns (stream RunCommandResponse) {}
}

message RunCommandRequest {
  Command command = 1;
}

// The command to be executed remotely.
message Command {
  string id = 1;

  Inputs inputs = 2;

  Outputs outputs = 3;

  string exec = 4;

  Args args = 5;

  ExecutionOptions execution_options = 6;

  ProxyOptions proxy_options = 7;

  map<string,string> labels = 8;
  // invocation and build id can be specified here if needed, otherwise a uuid is generated for them.
}

message Args {
  repeated string arg = 1;
}

message Inputs {
  repeated File file = 1;
  repeated Dir dir = 2;
  repeated RegExp exclusions = 3;
}

message Output {
  repeated File file = 1;
  repeated Dir dir = 2;
  repeated RegExp exclusions = 3;
}

message File {
  string local_path = 1;
  string remote_path = 2;
}

message Dir {
  string local_path = 1;
  string remote_path = 2;
}

message ExecutionOptions {
  string working_directory = 1;

  string side_tool_name = 2;

  bool accept_cached = 3;

  bool do_not_cache = 4;

  map<string,string> environment = 5;

  map<string,string> platform = 6;

  int32 timeout = 7;

  bool record_execution_data = 8;
}

message ProxyOptions {
    string log_path = 1;

    bool local_fallback = 2;
}

message RunCommandResponse {
  Result result = 1;
}

message Result {
  enum Status {
    UNKNOWN = 0;
    SUCCESS = 1;
    CACHE_HIT = 2;
    NON_ZERO_EXIT = 3;
    TIMEOUT = 4;
    INTERRUPTED = 5;
    REMOTE_ERROR = 6;
    LOCAL_ERROR = 7;
  }
  Status status = 1;

  int32 exit_code = 2;

  string stdout = 3;

  string stderr = 4;

  // Extra information useful for troubleshooting (debug/trace/stats).
  // E.g. build.bazel.remote.execution.v2.ExecutedActionMetadata.
  repeated google.protobuf.Any metadata = 5;
}

one more thing came to mind:
local_fallback: I think it is possible that in future we might have more than one way of falling back to local (e.g. inside docker, etc.) so it might be better to use an enum instead of a bool for it (iirc, that is one of dos/don'ts for proto/api to not use bool for something that we are not really certain will remain as bool)

Thank you for your comments!
A general note: we are not designing an API right now! If I were to do that, I'd send out a design doc, not a CL. This is not an API -- this proto is not supposed to be stable, nor account for every possible feature. I strongly prefer to iterate on it as we discover new use cases, rather than proactively.

btw, I am not sure the streaming is really required for proxy protocol, is the caller likely to take any action in the middle of the execution?

That is not the reason streaming is required -- I don't actually pass on any state, such as execution stage. The reason for streaming is that stdout and stderr may not fit into a single message. RE API doesn't have this problem, because it digests these, but I wanted a simpler one here.

Naming the message Command

yes, will do! It is a bit annoying in Java because there is no import+rename feature to resolve name clashes.

Inputs:

message Inputs {
  repeated File file = 1;
  repeated Dir dir = 2;
  repeated RegExp exclusions = 3;
}

Dir: the problem is that the caller often does not know whether something is an input file or directory. This is even more true for outputs, where we have a feature request to merge these in RE API (because the caller doesn't even have a way to find out whether an action will generate a file or a directory). So we want the caller to just specify the paths. I'd do it for outputs, too, but current RE API doesn't allow me to.
RegExp: these are strings, right?
File: yes, if we decide to do the local/remote paths feature request, that's what it should be. Also if I ever need to implement virtual files (when byte content + remote path is passed directly), a message will be useful. I'll introduce it when it is needed (although will have to think of a different name to avoid clashes with Stats.File).
local_fallback: yes, good point! will do.
tool_name: why side_tool_name? What's side?
exec/args: why do you want to separate argv[0] from the rest of them? And in a separate message, too? This is one I'm happily borrowing from RE API -- we never had to reconsider that choice there, so I don't see why would we do it here. Splitting the first argument would make every bit of code I know more complicated, and none simpler. I also can't think why would we want to add fields to the Args message.
Making stdout/stderr part of a Result: unlike the RE API I split these out, because I want to stream the content, rather than return the digests.
RunResult: I actually prefer the longer name.
metadata: no, I don't want to return any metadata anywhere, because this is not the RE API, this is an inter-process communication protocol. Its only user is the client tools we write. If anyone wants to debug executions beyond what's provided by the grpc logging and Stats functionalities, they should modify the proxy code.
map<string,string> labels: I will probably add something like that (I was thinking repeated string tag, but you're right a map is better) for Ramy's tagging feature request. But all the ids (command_id, invocation_id, build_request_id) should not be part of it, I think, but should be specified explicitly. The reason is that they're not arbitrary tags, the field maps to the corresponding field in the RE API and is passed on to RE (just like tool_name). How about this:
message Labels {
  string command_id = 1;
  string invocation_id = 2;
  string build_request_id = 3;
  string tool_name = 4;
  map<string,string> labels = 5;
}

Splitting some Command fields into *Options messages: I guess the advantage is to have smaller messages? Sure, I can do that. I prefer a simpler split, though, just one kind of Options message, so that I don't have to think which fields apply to remote exec options, which to local exec options, and which to both.

Sorry, I didn't push the changes yet, I'll let you know when this is ready for another pass.

Okay, this is ready for another pass. Note that splitting the Command message into 3 message, even though it makes logical sense, made all the code a lot more annoying. I'm not sure it was the right call. PTAL, thank you!

Command proto looks reasonable to me
some concern about streaming, but discussed offline.
I feel tool_name is kind of what bazel calls it, but not sure it is clear for others, if you can think of a more descriptive name I think that would be easier to understand.
RunResult: this is not a big deal, RunResult is ok. The reason for my comment: Run is the verb, the resource is Command, and Result seems like either a separate resource or something below Command. If I wanted to refer to them, I would refer to a Run, I would refer to a Command and ask for its Result or I would refer to the Result directly.

RunResult: oh, okay, I see. You're right, renamed it to CommandResult instead, so that it's still unambiguous what result it is.

tool_name: this is what it's called in RE API, you meant? Bazel is kind irrelevant here, it just uses this option to pass its own name and version.

I will merge this, as it works, and will make it easier to address other comments separately.

authors: ghasemloo ola-rozenfeld ramymedhat


text:
Show github connection status

Small feature, will hopefully make setting up easier for less tech savvy people.
Just adds an emoji which indicates connection status.
Also allows for validating token permissions in future (github is advocating for less powerful and more specific tokens (which is good)). Also indicates if token has expired!
This should probably be debounced though, but these are mostly pasted so it's not that bad.

Looks good, thank you 🙌 Should make it easier to spot config errors for new users.

authors: julesvirallinen oleeskild

repo: oleeskild/obsidian-digital-garden


text:
🛑 QR Ruby is down

In 41ca765, QR Ruby (https://qrruby.onrender.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: QR Ruby is back up in fedd20c after 9 minutes.


text:
Plans for span query?

Hello! It is awesome library, thanks for it! Do you have any milestone plans for span query? And are there some challenges with it? I'm asking it because I need this functionality, and I would like to try to implement this. Are there some plans or problems for span query?

No plans, but IIRC there's a tracking issue for years now. You're the first to ask though. Seems Span Queries are not that popular.
If you need it today, you can revert back to RawStringQuery (examples).

authors: olivere rbUUbr

repo: olivere/elastic


text:
Sorting

Hi!
I'm still learning so be gentle...
Is there a way to re-order or sort the results after a search?
I have a working implementation with some numeric data and I want to bring the largest values for a specific term to the top.
Any help would be really appreciated.
Thanks

Closing this now, feel free to re-open if you have any other questions.

I don't want to reopen here, but how could I sort the results by a given factor in an index entry. For example popularity or so.

Well, the results are an array of score and document ref. So you can re-sort it however you want, including looking up the existing document by its ref from wherever you have it in memory. As a reminder, lunr does not keep a copy of the indexed documents itself.

@olivernn Okay, thanks! Just out of curiosity, can I set two or more refs in one lunr index? If not, wouldn't that be a cool feature? I mean, I just imagined setting two different refs, for example one with the filename in it for alphabetic sorting and one with a popularity number. I know, I just could load up the documents or make a store of these values by my own to access this data, but this would be an additional step and seems performance-heavy, especially in my case, when trying to handle 3 million different and changing documents.
By the way, thank you for this library! I really like it! 👍

The problem is that Lunr is not intended to be the store of all your documents. How this data is stored would be very application specific, and trying to provide a reasonable interface would add quite a bit of complexity. The simplest thing for Lunr is to provide you with a key that you can use to lookup documents in whatever store you keep them in, be that locally in memory, or remotely via xhr.
I'm glad that Lunr is working well for you, especially with 3 million documents!

authors: jbavington713 nnmrts olivernn


text:
(Prune unwanted dangling models) Prune data from models which where partially downloaded

Sometime it happens that a user starts to download the wrong model or runs out of space (https://github.com/ollama/ollama/issues/2497).
The partially downloaded model is not visible through 'ollama list' after canceling the download and therefore cannot be removed using 'ollama rm '.
At the moment users have to find the corresponding sha and blob in the ollama directory and remove it manually or fully download the model just to be able to delete it.
Path for windows users: "C:\Users\your_user\ .ollama\models\blobs"
A command like 'ollama prune' or 'ollama autoremove' would be great.

Hi @arthurGrigo in this case you can restart Ollama which will prune. Pruning also happens on ollama create and I think ollama pull. Let me know if this helps!

authors: arthurGrigo jmorganca

repo: ollama/ollama


text:
failed to run llama3 on macos

What is the issue?
ollama run llama3 pulling manifest pulling 00e1317cbf74... 100% ▕██████████████████████████████████████████████████████████▏ 4.7 GB pulling 4fa551d4f938... 100% ▕██████████████████████████████████████████████████████████▏  12 KB pulling 8ab4849b038c... 100% ▕██████████████████████████████████████████████████████████▏  254 B pulling 577073ffcc6c... 100% ▕██████████████████████████████████████████████████████████▏  110 B pulling ad1518640c43... 100% ▕██████████████████████████████████████████████████████████▏  483 B verifying sha256 digest writing manifest removing any unused layers success Error: error starting the external llama server: fork/exec /var/folders/c3/vcxjn8bn59jd7th67f2fr9840000gn/T/ollama1329764937/runners/metal/ollama_llama_server: no such file or directory
OS
macOS
GPU
Apple
CPU
Apple
Ollama version
0.1.32

Hi @Mercccccc try upgrading to 0.1.35+ it should fix this (sorry about that!). Note if you restart Ollama that will fix it too, but this is an issue fixed in recent versions :)

Thank you very much! I will try it right now

authors: Mercccccc jmorganca


text:
llama3 8b BF16 error

What is the issue?
I downloaded the model from huggingface llama3 8b bf16 and when I run:
ollama create llama3bf16 -f Modfile
I get this output:
transferring model data
Error: invalid file magic
This is on a Win 11 PC running ollama 0.1.38 with an AMD W6800 GPU.  Is the bf16 model not supported?
OS
Windows
GPU
AMD
CPU
AMD
Ollama version
0.1.38

@ccbadd did you download a bf16 gguf file? What does the Modelfile look like?
Unfortunately the runner will not work w/ bf16 natively, as it has to be converted to fp16. If you downloaded the bf16 safetensors, you can however convert that directly in Ollama (just put the directory w/ the safetensors in the FROM line of your modelfile). You'll still have to get the template and the stop parameters correct which is somewhat tricky.
Alternatively you can just ollama pull llama3:8b-instruct-fp16 to download the already converted model.

What is the limitation that stops bf16 from working?
Models like llama3.1 are trained natively in bf16, not fp16, and the difference matters. Casting from bf16 to fp16 will degrade performance.  It matters less than going from fp16 to Q4, but it does clip some large and small weights in a way that can affect inference. So if serving bf16 was possible, I think that'd be preferable for those of us who run 16bits, especially for larger models.
What would need to be done to make this possible?

@Jbollenbacher the GGML library didn't support bfloat16s as a datatype until recently. There is support for that now, but it still takes time to make it work everywhere.

Great thanks. Is there an open issue tracking this?

authors: Jbollenbacher ccbadd pdevine


text:
feat: Added two new rebuses

Associated Issue: N/A
Summary of Changes

Added 'gift card' rebus.
Added 'bow tie' rebus.

Pull Request Test Coverage Report for Build 462

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 86.617%

Totals

Change from base Build 455:
0.0%

Covered Lines:
154

Relevant Lines:
175

💛  - Coveralls

Awesome, thank you 🙂

authors: TimOomis coveralls ollelauribostrom

repo: ollelauribostrom/rebus


text:
🛑 MediaNet is down

In 00c7179, MediaNet (https://medianet-pa.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MediaNet is back up in 3a05e18.

repo: olmloa/upptime


text:
No parallellism

The exhaustive search could be made faster by utilizing actually all the cores. Most computers these days have at least 4 cores, so there's opportunity for a 4x speedup right there.

I'm reopening this since we lost parallelism after the rewrite

repo: omarandlorraine/strop


text:
Import fails

Hi,
While I follow the steps necessary to install the module, and load the application, I get the following error message:
Error importing module: 'Module "api.cache.middleware" does not define a "ProfilerMiddleware" attribute/class'.
Django 1.10 / Python 3.6.

I suspect this would be fixed by #29

authors: Beenhakker roysmith

repo: omarish/django-cprofile-middleware


text:
🛑 UoD SLS OMERO (public) is down

In 319bdf2, UoD SLS OMERO (public) (https://omero.lifesci.dundee.ac.uk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: UoD SLS OMERO (public) is back up in 01660d7.

repo: ome/upptime


text:
🛑 UoD SLS OMERO (10.17867/10000109) is down

In c3f3512, UoD SLS OMERO (10.17867/10000109) (http://dx.doi.org/10.17867/10000109) was down:

HTTP code: 504
Response time: 10170 ms

Resolved: UoD SLS OMERO (10.17867/10000109) is back up in 7ba1a8e.


text:
🛑 OME training server 1 is down

In bec5463, OME training server 1 (https://outreach.openmicroscopy.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: OME training server 1 is back up in 5924e5f after 640 days, 13 hours, 47 minutes.


text:
Fix IE 11 support

This line is required to make IE11 work smoothly.

👍

👎

👍

This is fine.
But it has to be applied to all the pages using webots.min.js, i.e. at least to robotbenchmark and the HTML page created for the animation (resources/web/templates/x3d_playback.html).
I will update robotbenchmark in the existing PR https://github.com/omichel/robotbenchmark/pull/324

Well spotted, thank you, I test this for the X3D playback page.

x3d_playback.html was suffering indeed the same issue:

👍

authors: fabienrohrer stefaniapedrazzi

repo: omichel/webots


text:
AdditionalProperties are not honored in v0.9.0

I am trying to generate a model from the following schema file.
It works fine with v0.8.0 but fails on v0.9.0
test.json
{
  "$schema": "http://json-schema.org/draft-04/schema#",
  "$ref": "#/definitions/TestObject",
  "definitions":
  {
    "TestObject":
    {
      "required":
      [
        "owner",
        "name"
      ],
      "properties":
      {
        "owner":
        {
          "type": "string"
        },
        "name":
        {
          "type": "string"
        },
        "config":
        {
          "patternProperties":
          {
            ".*":
            {
              "additionalProperties": true
            }
          },
          "type": "object"
        }
      },
      "additionalProperties": false,
      "type": "object"
    }
  }
}

Error:
gojsonschema -v -p model ../test.json -o test.go
gojsonschema: Loading ../test.json
gojsonschema: Failed: error parsing from file ../test.json: json: cannot unmarshal bool into Go struct field Type.definitions.properties.patternProperties.additionalProperties of type schemas.Type

Is this fixed by https://github.com/atombender/go-jsonschema/pull/29?
Waiting for a release! :-)

@jdimeo you can use it right by doing this:
go install github.com/atombender/go-jsonschema/cmd/gojsonschema@master

Added the test to the suite of regressions test here #76, closing.

authors: anandsunderraman atreya2011 jdimeo omissis

repo: omissis/go-jsonschema


text:
Check against omnia/label/rc

fixes #488

Restarted the osx build.

authors: jchodera mpharrigan

repo: omnia-md/conda-recipes


text:
feat: summer cleaning :broom:

[main] Remove Thanos, authelia, glauth and dragonfly
[main] Prometheus to one replica using ceph fs
[storage] Deploy grafana and prometheus operator crds
[main/storage] grafana no persistence
[main] remove fstrim and altermanager-silencer "operators"
[main/storage] drop replicas down to 1 for most workloads

Since you have removed glauth and authelia how are you doing authn and authz for access to your services when accessed from outside your local network?

license: WTFPL