make a list of all Picard metrics tools used in the production pipeline (WGS, WES)

We have the list - can't put it here yet though. Closing the ticket.


how to exclude files from being styled by anchor tags?

I have setup # as an anchor tag but this is messing up with my .md and .env files.
"commentAnchors.tags.list": [
   {
     "tag": "#",
     "scope": "file",
     "iconColor": "default",
     "highlightColor": "#A8C023",
     "styleComment": true,
     "isBold": true,
     "isItalic": false,
     "isRegion": true
   },
}

How not to stylize .md and .env files when I add # in these files? but it's fine in .ts,.js files.

This is currently not possible, however I'll look into adding support for this in the near future


Can this player play .m3u8 file ?. It doesn't work in your example .

I'm using your VG vertical example and iOS 11.2

Player is not playing .m3u8 live stream url, any update on this?

can not play m3u8


add type definition for getContentByIds

This resolves issue #286

I don't know much about how type definitions works. As said in mentioned issue comments, I figured it from other type definition.
I am happy to make any changes required.

No changes needed! LGTM! :+1:


Does not work with allure-pytest

When I attempt to use pytest-parallel it prevents the allure report from being generated. for instance if I run:
pytest --tests-per-worker 4 --alluredir=reports/allure
no report is generated. If i take the tests per worker argument out the report works. Any idea why this would prevent the report from being saved?

looks like this is the same issue as the --junit one

Hmm, I'd understand for --workers, but I'm not sure why it's not working for --tests-per-worker

Let me rephrase that just to be clear. It is being generated, but its showing 0 tests executed.

@kevlened Can you tell me your idea about a time for fix this issue (Bug) ?

Please, look my changes, it is help me to work with allure-pytest in paralel.
I'm test with --workers 2 and with 3,6,8,auto.
But it is have a trouble with --tests-per-worker when it is greather than 1. It is add N identical steps, where N = tests-per-worker
index 63d4175..8e71da4 100644
--- a/pytest_parallel/__init__.py
+++ b/pytest_parallel/__init__.py
@@ -8,6 +8,7 @@ import threading
 import queue as Queue
 from py._xmlgen import raw
 from multiprocessing import Manager, Process
+from allure_pytest.plugin import pytest_configure as original_pytest_configure

 __version__ = '0.0.9'

@@ -54,6 +55,7 @@ def run_test(session, item, nextitem):

 def process_with_threads(queue, session, tests_per_worker):
+    original_pytest_configure(allur_conf)
     threads = []
     for _ in range(tests_per_worker):
         thread = ThreadWorker(queue, session)
@@ -62,6 +64,9 @@ def process_with_threads(queue, session, tests_per_worker):
     [t.join() for t in threads]

+allur_conf = None
+
+
 class ThreadWorker(threading.Thread):
     def __init__(self, queue, session):
         threading.Thread.__init__(self)
@@ -69,6 +74,7 @@ class ThreadWorker(threading.Thread):
         self.session = session

     def run(self):
+        original_pytest_configure(allur_conf)
         while True:
             try:
                 index = self.queue.get_nowait()
@@ -87,6 +93,8 @@ class ThreadWorker(threading.Thread):

 @pytest.mark.trylast
 def pytest_configure(config):
+    global allur_conf
+    allur_conf = config
     workers = parse_config(config, 'workers')
     tests_per_worker = parse_config(config, 'tests_per_worker')
     if not config.option.collectonly and (workers or tests_per_worker):

@SizovIgor did you get any further with getting tests-per-worker to work?

The latest (0.1.0) is quite a bit change that should resolve most reporting issues. It may solve this issue as well.

is this issue resolved? i am still facing this issue with 0.1.0

Hi @kevlened
Thank you for your response.
I have same issue:
allure-pytest==2.8.6
pytest==6.0.1
pytest-parallel==0.1.0
Do you know when it can be resolve BTW, same with report portal.
Thanks!

I'm facing the same issue
Any solution/workaround for this problem?

Facing same issue.
@kevlened - If i were to try and change the current situation, do you have a recommendation for a starting point? where in the repo should i investigate?

Thanks for the interest. Here's what I'd do:

Repro
Do the brief steps in CONTRIBUTING.md and make sure the existing tests were working.
Write a failing test case similar to the one for pytest-html. pytest-allure needs to be added to tox.ini. I might skip this if I was unfamiliar with testing pytest plugins.
I'd start by trying @SizovIgor's suggestion. The suggestion was prior to a pretty substantial change, but could be adapted.
If that didn't work, I'd investigate the pytest-allure repo to determine how the reports are generated. There's probably some data that pytest-allure depends on that pytest-parallel isn't sharing across threads. All of pytest-parallel is a few hundred lines in this file.
If I still couldn't figure it out, I'd open a PR with the test case (if I wrote one), so others could give it a shot.

If you try it, let me know if you run into any issues.

Facing same issue.

Facing same issue.

Any solution for this issue？

Same issue still. Any progress on this?


Update

Banano.Exchange redirects to Nanswap.com
BananoCharts stopped working
Added My Banano Ninja (temporary down)
Added HotBit
Added ViteX
Added BANANO resources section

Banano Wiki
wBAN GitBook

Verified and implemented. Appreciate the assistance!


io_uring improvements (error sets, completion cancellation, queued write retries)

There are a couple of things here, I'm happy to split them up into multiple PRs:

Adds some common error codes for send/recv operations (e.g. Connection refused, timed out, connection reset)
Adds a generic completion cancellation function that can be used to cancel any completion (tested with TCP recv operations)
Improves handling of partial queued writes. Public Queued API should guarantee the ordering of writes. These changes ensure that partially completed writes are re-tried rather than discarded.

@recursiveGecko I think it's fine to have these in one pull request, but obviously it's really @mitchellh's preference that matters here.

This looks really good. I'm going to make some cosmetic changes but the core work here is excellent. Thank you. All the changes in one PR is fine.

I know this was still marked as draft but the queueWrite fixes were too good and the remainder looked ready to go to me. If you have some issues let me know! Thank you again, so much!


Webnovel source incomplete

Source information
Webnovel.com
Steps to reproduce
Opened the app
Open webnovel source
Downloaded a locked chapter
Locked Chapter incomplete
Expected behavior
Locked Chapters are supposed to be have 3 pages worth of contemt
Actual behavior
but only 1 page worth shows which makes the locked chapters incomplete
LNReader version
2.0.0
Android version
Android 10
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 1.1.19.
[X] I have updated all installed extensions.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Do you expect the app to display content from locked chapters that you haven’t paid for?


[New Maintainers] Becoming NuGet.org Admins

In order to be able to maintain Rx, @idg10 and @HowardvanRooijen need admin access to the rxteam profile on nuget.org.
Can @clairernovotny or @bartdesmet make this assignment, otherwise can @richlander or @jglozano from the .NET Foundation help?

Given that those folks are available, it would be greatly preferable if they did it. I am hoping that we can make that happen. Please remind us if you cannot get traction within one week.

Hi @richlander - no traction as yet.

Hi @richlander - still nothing. How can we get unblocked?

Sorry. Just saw this. I will push on it.

Thank you. Issue https://github.com/dotnet/reactive/issues/1870 is also related!

Invitation accepted! Thanks @clairernovotny (& @richlander) 🎉


support manual compaction with _compact

Is your feature request related to a problem? Please describe.
Support the /{db}/_compact endpoint or provide a way to reuse the authentication and send arbitrary requests to the server.
Describe the solution you'd like
Have a method to get the value of _compact, similar to postRevsDiff
Describe alternatives you've considered
reuse the authentication and send arbitrary requests to the server.

Hi @thigg, this endpoint is automatically handled and not available in Cloudant.
e.g.
curl https://<cloudant_account>.../db/_compact
{"error":"forbidden","reason":"compaction is automatic on Cloudant"}

For more details about the server compatibility with this SDK, please see https://github.com/IBM/cloudant-java-sdk#features

what about the alternative? creating a way to reuse the authentication and run custom requests?

There's an option to create an OkHttp request and pass it to the SDK client object.  You can add existing authentication to the custom request using client.getAuthenticator().authenticate():
        Cloudant client = Cloudant.newInstance("SERVER");
        String dbName = "your-db";
        HttpUrl requestUrl =  HttpUrl.parse(client.getServiceUrl()).newBuilder().addPathSegment(dbName).addPathSegment("_compact").build();
        Request.Builder rb = new Request.Builder().url(requestUrl).get();
        client.getAuthenticator().authenticate(rb);
        Response response = client.getClient().newCall(rb.build()).execute();
        System.out.println(response.body().string());

If you're using session cookie auth, you'll need to disable gzip compression with client.enableGzipCompression(false);.  This is mentioned in https://github.com/IBM/cloudant-java-sdk/blob/master/KNOWN_ISSUES.md#session-authentication


Add visualization instance to ros-image-demo

Description of changes:
This adds a sample deployment of an EC2 based visualization instance to the ros-image-demo manifest. It also increases the default ubuntu user password length.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@a13zen I think the only outstanding item is the ordering on the manifest...?


Does it restore with a forward match if specified for key? (not restore-keys)

Hello! I have been using cache, very useful.
Is the key string forward matching?
For example, if key=foo, does it match key=foobar or not?
I think restore-keys is a forward matching specification.
But since key also forward matched, I thought it might be a bug and came here to report it.
Here is the log.

key: ubuntu-20.04-voicevox-core-voicevox_core-linux-x64-cpu-0.14.0
Cache restored from key: ubuntu-20.04-voicevox-core-voicevox_core-linux-x64-cpu-0.14.0-preview.4

Run actions/cache@v3
  with:
    key: ubuntu-20.04-voicevox-core-voicevox_core-linux-x64-cpu-0.14.0
    path: download/core
    enableCrossOsArchive: false
    fail-on-cache-miss: false
  env:
    PYTHON_VERSION: 3.8.10
    VOICEVOX_RESOURCE_VERSION: 0.14.0
    VOICEVOX_CORE_VERSION: 0.14.0
    pythonLocation: /opt/hostedtoolcache/Python/3.8.10/x64
    PKG_CONFIG_PATH: /opt/hostedtoolcache/Python/3.8.10/x64/lib/pkgconfig
    Python_ROOT_DIR: /opt/hostedtoolcache/Python/3.8.10/x64
    Python2_ROOT_DIR: /opt/hostedtoolcache/Python/3.8.10/x64
    Python3_ROOT_DIR: /opt/hostedtoolcache/Python/3.8.10/x64
    LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.8.10/x64/lib
    MSYS: winsymlinks:nativestrict
Received 0 of 702401041 (0.0%), 0.0 MBs/sec
Received 79691776 of 702401041 (11.3%), 38.0 MBs/sec
Received 188743680 of 702401041 (26.9%), 60.0 MBs/sec
Received 306184192 of 702401041 (43.6%), 72.9 MBs/sec
Received 419430400 of 702401041 (59.7%), 79.9 MBs/sec
Received 528482304 of 702401041 (75.2%), 83.9 MBs/sec
Received 629145600 of 702401041 (89.6%), 85.6 MBs/sec
Received 702401041 of 702401041 (100.0%), 80.6 MBs/sec
Cache Size: ~670 MB (702401041 B)
/usr/bin/tar -xf /home/runner/work/_temp/575f5ea6-2037-472b-9f8f-c3b5bfa684e0/cache.tzst -P -C /home/runner/work/voicevox_engine/voicevox_engine --use-compress-program unzstd
Cache restored successfully
Cache restored from key: ubuntu-20.04-voicevox-core-voicevox_core-linux-x64-cpu-0.14.0-preview.4

Github Runs: https://github.com/VOICEVOX/voicevox_engine/actions/runs/4047017525/jobs/6960530619

@Hiroshiba I can confirm this finding. Same is the case with my testing.

@Hiroshiba cache-hit is set as false in this case so nothing should break if you follow our recommendations of creating primary and restore keys

@Phantsure
I see!!
I thought it would be easier to understand if the documentation said that key is also restored with forward matching!
(In my case, since the documentation says restore keys is forward matching, so I mistakenly thought that primary key is exact matching.)

Hi @Hiroshiba, I agree that the documentation should have been more clear. We will take this up and fix it in the documentation. Thanks :)

Could the behavior not be changed?
Right now it's impossible to only restore cache with a specific key, you have to restore, check the cache-hit output, and then delete the cache again if it's not a hit.


([]["isPrototypeOf"] + "")[11]

I don't know if anyone has said that, but this gives the result P.
([]["isPrototypeOf"] + "")[11]

@Andromeda606 do you realize that “isPrototypeOf” requires “P” to get that word?

the same is heard here.

No, it is completely different: “undefined” is an “atomic” construct that does not require any letters — [][[]]+[].

aynısı burada da duyuluyor.

Hayır, tamamen farklıdır: “undefined”herhangi bir harf gerektirmeyen “atomik” bir yapıdır — [][[]]+[].
I understand.


[Backend] Modify UserProject model

We need to add some properties to UserProject Model to be possible work with invitation in the projects.
    public User User { get; private set; } = new User(); // Already exists, change to optional
    public string Email { get; set; } // when user not exists
    public Project Project { get; private set; } = new Project();  // Already exists
    public Role Role { get; private set; }  // Already exists
    public Guid Token { get; set; }
    public bool Accepted { get; set; }
    public DateTime SentAt { get; set; }
    public DateTime? AcceptedAt { get; set; }
    public bool Expired { get; set; }
    public DateTime ExpiryDate { get; set; }

[ ] create a index on token property

Hey @AmirAbdollahi ,
Are you still working on it?
I'm just asking because if you are not I'll release it to another one.
Thank you in advance.

Hi @FelipePSoares .
No I'm not. You can release it.
Thank your very much.

Hi @AmirAbdollahi ,
No problem, Thank you very much for everything.

Hey @saksham-malhotra-27!
This one is a "simple" backend task if you want. You will need generate a migration after change the domain, you can find the instructions for that in contribution.md file.
If you accept the challenge, let me know any doubt that you could have.

Yup @FelipePSoares ! alright I'll try

or have you already completed the task ?

@saksham-malhotra-27 I know that you can handle with it. Let me know anything that you need.


TOMEE-2982 Translate to Portuguese: examples/simple-jms-context

Translate to portuguese the example JMS context .
Link to JIra: https://issues.apache.org/jira/browse/TOMEE-2982

In this phrase "This example demostrate how to set up a CustomJmsService in order to produce and consume a JMS Message.", have a problem, it is in english.

thanks @jrxxjr , you can review again ?

Now, the translation it is ok.

thanks @jrxxjr  for review :)


System doesn't show hydrogens if carbons connected by aromatic bond

Steps to Reproduce

Open from file: System doesn't show hydrogens if carbons connected by aromatic bond.zip (unzip first)

Actual behavior

Expected behavior

Ketcher version [e.g. v2.4.2].

Indigo Toolkit Version 1.18.0-dev.4.0-g085ab345f-x86_64-linux-gnu-11.2.1
Ketcher Version 2.17.0-rc.2 Build at 2024-01-03; 17:17:22
Chrome Version 120.0.6099.225 (Official Build) (64-bit)
Win10
Issue found while testing https://github.com/epam/Indigo/issues/1436

Moved to Refined Backlog since no fix over 4 versions


Hardlinking <....>.file to VGAuthService: File exists

Describe the bug
I have a cluster at 4.6.0-0.okd-2020-12-12-135354, it was previously upgrade already 7 times from earlier OKD releases and this was always successful. Now I am trying to upgrade to the new 4.6.0-0.okd-2021-01-17-185703 but it fails.
All but the MCO are done but the MCO does not progress. I saw that it set a worker (and a master) to SchedulingDisabled but then nothing happened over a long period of time. I decided to reboot the nodes in question but soon thereafter the same worker is in SchedulingDisabled state again and nothing happens.
Also, since the upgrade any AD/LDAP login fails with internal server error 500 but this may be unrelated and I'll open a separate issue for this
Version
4.6.0-0.okd-2020-12-12-135354 to 4.6.0-0.okd-2021-01-17-185703
How reproducible
See above.
Log bundle
Unfortunately, must-gather fails:
$ oc adm must-gather
[must-gather      ] OUT Using must-gather plugin-in image: quay.io/openshift/okd-content@sha256:c46390d74c9ac6152264da87b5667eacc42871cf4eb9ab444cd953ae56b81b07
[must-gather      ] OUT namespace/openshift-must-gather-lb75x created
[must-gather      ] OUT clusterrolebinding.rbac.authorization.k8s.io/must-gather-zz8lq created
[must-gather      ] OUT pod for plug-in image quay.io/openshift/okd-content@sha256:c46390d74c9ac6152264da87b5667eacc42871cf4eb9ab444cd953ae56b81b07 created
[must-gather-vfwbk] OUT gather did not start: Get https://api.devqs.ars.de:6443/api/v1/namespaces/openshift-must-gather-lb75x/pods/must-gather-vfwbk: unexpected EOF [must-gather      ] OUT clusterrolebinding.rbac.authorization.k8s.io/must-gather-zz8lq deleted
[must-gather      ] OUT namespace/openshift-must-gather-lb75x deleted
error: gather did not start for pod must-gather-vfwbk: Get https://api.devqs.ars.de:6443/api/v1/namespaces/openshift-must-gather-lb75x/pods/must-gather-vfwbk: unexpected EOF

I checked with journalctl to see what the SchedulingDisabled worker does all the time and found that it is looping with failing rpm-ostree attempts:
Jan 19 12:42:59 worker-01.devqs.ars.de rpm-ostree[96916]: client(id:machine-config-operator dbus:1.432 unit:crio-f1cec2ed1f6a38ad5afe618d6f044ee7d999d001128648296cb0c1795636b8ac.scope uid:0) added; new total=1
Jan 19 12:42:59 worker-01.devqs.ars.de rpm-ostree[96916]: client(id:machine-config-operator dbus:1.432 unit:crio-f1cec2ed1f6a38ad5afe618d6f044ee7d999d001128648296cb0c1795636b8ac.scope uid:0) vanished; remaining=0
Jan 19 12:42:59 worker-01.devqs.ars.de rpm-ostree[96916]: In idle state; will auto-exit in 63 seconds
Jan 19 12:43:01 worker-01.devqs.ars.de rpm-ostree[96916]: client(id:machine-config-operator dbus:1.434 unit:crio-f1cec2ed1f6a38ad5afe618d6f044ee7d999d001128648296cb0c1795636b8ac.scope uid:0) added; new total=1
Jan 19 12:43:01 worker-01.devqs.ars.de rpm-ostree[96916]: Locked sysroot
Jan 19 12:43:01 worker-01.devqs.ars.de rpm-ostree[96916]: Initiated txn UpdateDeployment for client(id:machine-config-operator dbus:1.434 unit:crio-f1cec2ed1f6a38ad5afe618d6f044ee7d999d001128648296cb0c1795636b8ac.scope uid:0): /org/projectatomic/rpmostree1/fedora_coreos
Jan 19 12:43:03 worker-01.devqs.ars.de rpm-ostree[96916]: warning: Found bdb Packages database while attempting sqlite backend: using bdb backend.
Jan 19 12:43:03 worker-01.devqs.ars.de rpm-ostree[96916]: Librepo version: 1.12.1 with CURL_GLOBAL_ACK_EINTR support (libcurl/7.71.1 OpenSSL/1.1.1h-fips zlib/1.2.11 brotli/1.0.9 libidn2/2.3.0 libpsl/0.21.1 (+libidn2/2.3.0) libssh/0.9.5/openssl/zlib nghttp2/1.41.0)
Jan 19 12:43:03 worker-01.devqs.ars.de rpm-ostree[96916]: warning: Found bdb Packages database while attempting sqlite backend: using bdb backend.
Jan 19 12:43:05 worker-01.devqs.ars.de rpm-ostree[96916]: warning: Found bdb Packages database while attempting sqlite backend: using bdb backend.
Jan 19 12:43:07 worker-01.devqs.ars.de rpm-ostree[96916]: Preparing pkg txn; enabled repos: ['fedora-cisco-openh264', 'updates', 'fedora', 'coreos-extensions', 'updates-archive'] solvables: 93213
Jan 19 12:43:08 worker-01.devqs.ars.de rpm-ostree[96916]: warning: Found bdb Packages database while attempting sqlite backend: using bdb backend.
Jan 19 12:43:08 worker-01.devqs.ars.de rpm-ostree[96916]: Txn UpdateDeployment on /org/projectatomic/rpmostree1/fedora_coreos failed: Checkout open-vm-tools-11.2.5-1.fc33.x86_64: Hardlinking 57/2d1e0a8b85be28856aa9655c6ef42462a8aabdc30868f3a7a910bfa0f8dd3d.file to VGAuthService: File exists
Jan 19 12:43:08 worker-01.devqs.ars.de rpm-ostree[96916]: Unlocked sysroot
Jan 19 12:43:08 worker-01.devqs.ars.de rpm-ostree[96916]: client(id:machine-config-operator dbus:1.434 unit:crio-f1cec2ed1f6a38ad5afe618d6f044ee7d999d001128648296cb0c1795636b8ac.scope uid:0) vanished; remaining=0
Jan 19 12:43:08 worker-01.devqs.ars.de rpm-ostree[96916]: In idle state; will auto-exit in 60 seconds

I checked with journalctl to see what the SchedulingDisabled worker does all the time and found that it is looping with failing rpm-ostree attempts:
Jan 19 12:42:59 worker-01.devqs.ars.de rpm-ostree[96916]: client(id:machine-config-operator dbus:1.432 unit:crio-f1cec2ed1f6a38ad5afe618d6f044ee7d999d001128648296cb0c1795636b8ac.scope uid:0) added; new total=1
Jan 19 12:42:59 worker-01.devqs.ars.de rpm-ostree[96916]: client(id:machine-config-operator dbus:1.432 unit:crio-f1cec2ed1f6a38ad5afe618d6f044ee7d999d001128648296cb0c1795636b8ac.scope uid:0) vanished; remaining=0
Jan 19 12:42:59 worker-01.devqs.ars.de rpm-ostree[96916]: In idle state; will auto-exit in 63 seconds
Jan 19 12:43:01 worker-01.devqs.ars.de rpm-ostree[96916]: client(id:machine-config-operator dbus:1.434 unit:crio-f1cec2ed1f6a38ad5afe618d6f044ee7d999d001128648296cb0c1795636b8ac.scope uid:0) added; new total=1
Jan 19 12:43:01 worker-01.devqs.ars.de rpm-ostree[96916]: Locked sysroot
Jan 19 12:43:01 worker-01.devqs.ars.de rpm-ostree[96916]: Initiated txn UpdateDeployment for client(id:machine-config-operator dbus:1.434 unit:crio-f1cec2ed1f6a38ad5afe618d6f044ee7d999d001128648296cb0c1795636b8ac.scope uid:0): /org/projectatomic/rpmostree1/fedora_coreos
Jan 19 12:43:03 worker-01.devqs.ars.de rpm-ostree[96916]: warning: Found bdb Packages database while attempting sqlite backend: using bdb backend.
Jan 19 12:43:03 worker-01.devqs.ars.de rpm-ostree[96916]: Librepo version: 1.12.1 with CURL_GLOBAL_ACK_EINTR support (libcurl/7.71.1 OpenSSL/1.1.1h-fips zlib/1.2.11 brotli/1.0.9 libidn2/2.3.0 libpsl/0.21.1 (+libidn2/2.3.0) libssh/0.9.5/openssl/zlib nghttp2/1.41.0)
Jan 19 12:43:03 worker-01.devqs.ars.de rpm-ostree[96916]: warning: Found bdb Packages database while attempting sqlite backend: using bdb backend.
Jan 19 12:43:05 worker-01.devqs.ars.de rpm-ostree[96916]: warning: Found bdb Packages database while attempting sqlite backend: using bdb backend.
Jan 19 12:43:07 worker-01.devqs.ars.de rpm-ostree[96916]: Preparing pkg txn; enabled repos: ['fedora-cisco-openh264', 'updates', 'fedora', 'coreos-extensions', 'updates-archive'] solvables: 93213
Jan 19 12:43:08 worker-01.devqs.ars.de rpm-ostree[96916]: warning: Found bdb Packages database while attempting sqlite backend: using bdb backend.
Jan 19 12:43:08 worker-01.devqs.ars.de rpm-ostree[96916]: Txn UpdateDeployment on /org/projectatomic/rpmostree1/fedora_coreos failed: Checkout open-vm-tools-11.2.5-1.fc33.x86_64: Hardlinking 57/2d1e0a8b85be28856aa9655c6ef42462a8aabdc30868f3a7a910bfa0f8dd3d.file to VGAuthService: File exists
Jan 19 12:43:08 worker-01.devqs.ars.de rpm-ostree[96916]: Unlocked sysroot
Jan 19 12:43:08 worker-01.devqs.ars.de rpm-ostree[96916]: client(id:machine-config-operator dbus:1.434 unit:crio-f1cec2ed1f6a38ad5afe618d6f044ee7d999d001128648296cb0c1795636b8ac.scope uid:0) vanished; remaining=0
Jan 19 12:43:08 worker-01.devqs.ars.de rpm-ostree[96916]: In idle state; will auto-exit in 60 seconds

A co-worker checked/researched/experimented with the cluster and removed the open-vm-tools from the cluster nodes. Then the MCO made progress and updated successfully all worker nodes. The vSphere persistent volumes still work and vSphere integration also works after enabling/starting the vmtoolsd service.
However, the master nodes still are not updated, and we can not see any progress there.

A co-worker checked/researched/experimented with the cluster and removed the open-vm-tools from the cluster nodes. Then the MCO made progress and updated successfully all worker nodes. The vSphere persistent volumes still work and vSphere integration also works after enabling/starting the vmtoolsd service.
However, the master nodes still are not updated, and we can not see any progress there.

I ran into the same situation (same versions, but I didn't experience the mentioned LDAP issues).
The line Checkout open-vm-tools-11.2.5-1.fc33.x86_64: Hardlinking 57/2d1e0a8b85be28856aa9655c6ef42462a8aabdc30868f3a7a910bfa0f8dd3d.file to VGAuthService: File exists seems to be crucial here, I had exactly the same entry in the logs.
Manually removing the open-vm-tools on all nodes seems to solve the problem - in my case the master nodes continued automatically after the removal, the MCO upgrade completed without further actions.

I ran into the same situation (same versions, but I didn't experience the mentioned LDAP issues).
The line Checkout open-vm-tools-11.2.5-1.fc33.x86_64: Hardlinking 57/2d1e0a8b85be28856aa9655c6ef42462a8aabdc30868f3a7a910bfa0f8dd3d.file to VGAuthService: File exists seems to be crucial here, I had exactly the same entry in the logs.
Manually removing the open-vm-tools on all nodes seems to solve the problem - in my case the master nodes continued automatically after the removal, the MCO upgrade completed without further actions.

Yes, it only took the MCO a while of thinking before it also upgraded the masters of our cluster.
So the upgrade is done now.
(But the AD/LDAP problem persists but that is another issue.)

Yes, it only took the MCO a while of thinking before it also upgraded the masters of our cluster.
So the upgrade is done now.
(But the AD/LDAP problem persists but that is another issue.)

See https://github.com/openshift/okd-machine-os/pull/63

See https://github.com/openshift/okd-machine-os/pull/63

remove open-vm-tools invalid,  a new error
[root@master02 ~]# rpm-ostree uninstall open-vm-tools
Checking out tree d2e23f9... done
Resolving dependencies... done
Relabeling... done
Checking out packages... done
Running pre scripts... done
Running post scripts... done
Running posttrans scripts... done
Writing rpmdb... done
Writing OSTree commit... done
Staging deployment... done
Freed: 1.4 GB (pkgcache branches: 7)
Upgraded:
  gdbm-libs 1:1.18.1-5.fc33 -> 1:1.19-1.fc33
  python-unversioned-command 3.9.0-1.fc33 -> 3.9.1-1.fc33
  python3 3.9.0-1.fc33 -> 3.9.1-1.fc33
  python3-libs 3.9.0-1.fc33 -> 3.9.1-1.fc33
  qemu-guest-agent 2:5.1.0-8.fc33 -> 2:5.1.0-9.fc33
Removed:
  libdrm-2.4.102-2.fc33.x86_64
  libmspack-0.10.1-0.4.alpha.fc33.x86_64
  libpciaccess-0.16-3.fc33.x86_64
  libtool-ltdl-2.4.6-36.fc33.x86_64
  libxslt-1.1.34-4.fc33.x86_64
  open-vm-tools-11.2.0-1.fc33.x86_64
  xmlsec1-1.2.29-2.fc33.x86_64
  xmlsec1-openssl-1.2.29-2.fc33.x86_64
Run "systemctl reboot" to start a reboot
[root@master02 ~]#
[root@master02 ~]#
[root@master02 ~]# rpm -qa | grep open-vm-tools
warn：Found bdb Packages database while attempting sqlite backend: using bdb backend.
open-vm-tools-11.2.0-1.fc33.x86_64
[root@master02 ~]#
[root@master02 ~]#
[root@master02 ~]# systemctl reboot

# oc -n openshift-machine-config-operator logs machine-config-daemon-666bs machine-config-daemon -f
I0120 14:09:24.584661    6816 start.go:108] Version: machine-config-daemon-4.6.0-202006240615.p0-374-ga72f402c-dirty (a72f402cce4a683d4f9ba3956b5dcd297b458a54)
I0120 14:09:24.588389    6816 start.go:121] Calling chroot("/rootfs")
I0120 14:09:24.588516    6816 rpm-ostree.go:261] Running captured: rpm-ostree status --json
I0120 14:09:24.678275    6816 daemon.go:226] Booted osImageURL: quay.io/openshift/okd-content@sha256:95034a94e28949af41a53b9efb2fbb0651454a7c37bab002b0646e73c4721829 ()
I0120 14:09:24.689869    6816 daemon.go:233] Installed Ignition binary version: 2.8.1
I0120 14:09:24.718133    6816 start.go:97] Copied self to /run/bin/machine-config-daemon on host
I0120 14:09:24.720604    6816 metrics.go:106] Registering Prometheus metrics
I0120 14:09:24.720710    6816 metrics.go:111] Starting metrics listener on <IP_ADDRESS>:8797
I0120 14:09:24.728387    6816 update.go:1661] Starting to manage node: master02.manage-dev.oc4.forchange.cn
I0120 14:09:24.735549    6816 rpm-ostree.go:261] Running captured: rpm-ostree status
I0120 14:09:24.795731    6816 daemon.go:862] State: idle
Deployments:
* pivot://quay.io/openshift/okd-content@sha256:95034a94e28949af41a53b9efb2fbb0651454a7c37bab002b0646e73c4721829
              CustomOrigin: Managed by machine-config-operator
                 Timestamp: 2020-12-12T05:05:37Z
           LayeredPackages: NetworkManager-ovs glusterfs glusterfs-fuse qemu-guest-agent

  pivot://quay.io/openshift/okd-content@sha256:95034a94e28949af41a53b9efb2fbb0651454a7c37bab002b0646e73c4721829
              CustomOrigin: Managed by machine-config-operator
                 Timestamp: 2020-12-12T05:05:37Z
           LayeredPackages: NetworkManager-ovs glusterfs glusterfs-fuse open-vm-tools
                            qemu-guest-agent
I0120 14:09:24.795851    6816 rpm-ostree.go:261] Running captured: journalctl --list-boots
I0120 14:09:24.819288    6816 daemon.go:869] journalctl --list-boots:
-2 e195922e5b754a109b75474436df49f4 Mon 2021-01-18 20:48:14 UTC—Wed 2021-01-20 13:51:50 UTC
-1 01309413d4ab4dedbafd6e2640c94cf2 Wed 2021-01-20 13:54:53 UTC—Wed 2021-01-20 14:06:21 UTC
 0 e887d707d6084137b2ed56822f74b013 Wed 2021-01-20 14:07:06 UTC—Wed 2021-01-20 14:09:24 UTC
I0120 14:09:24.819316    6816 rpm-ostree.go:261] Running captured: systemctl list-units --state=failed --no-legend
I0120 14:09:24.830462    6816 daemon.go:884] systemd service state: OK
I0120 14:09:24.830576    6816 daemon.go:616] Starting MachineConfigDaemon
I0120 14:09:24.830827    6816 daemon.go:623] Enabling Kubelet Healthz Monitor
I0120 14:09:25.750968    6816 daemon.go:397] Node master02.manage-dev.oc4.forchange.cn is part of the control plane
I0120 14:09:25.794465    6816 daemon.go:815] Current config: rendered-master-18f16c1426810c6c3235ea1a1a08b07d
I0120 14:09:25.794512    6816 daemon.go:816] Desired config: rendered-master-27b5838883d09dd7eb035dc624c8ca11
I0120 14:09:25.808052    6816 update.go:1661] Disk currentConfig rendered-master-27b5838883d09dd7eb035dc624c8ca11 overrides node's currentConfig annotation rendered-master-18f16c1426810c6c3235ea1a1a08b07d
I0120 14:09:25.811130    6816 daemon.go:1085] Validating against current config rendered-master-27b5838883d09dd7eb035dc624c8ca11
E0120 14:09:25.811199    6816 writer.go:135] Marking Degraded due to: unexpected on-disk state validating against rendered-master-27b5838883d09dd7eb035dc624c8ca11: expected target osImageURL "quay.io/openshift/okd-content@sha256:2fe2fd4d99c953d5bcf0d53b420a2012aae7fd12986dac8e757ad68f7b97030c", have "quay.io/openshift/okd-content@sha256:95034a94e28949af41a53b9efb2fbb0651454a7c37bab002b0646e73c4721829"
I0120 14:09:27.841136    6816 daemon.go:815] Current config: rendered-master-18f16c1426810c6c3235ea1a1a08b07d
I0120 14:09:27.841190    6816 daemon.go:816] Desired config: rendered-master-27b5838883d09dd7eb035dc624c8ca11
I0120 14:09:27.853565    6816 update.go:1661] Disk currentConfig rendered-master-27b5838883d09dd7eb035dc624c8ca11 overrides node's currentConfig annotation rendered-master-18f16c1426810c6c3235ea1a1a08b07d
I0120 14:09:27.856244    6816 daemon.go:1085] Validating against current config rendered-master-27b5838883d09dd7eb035dc624c8ca11
E0120 14:09:27.856385    6816 writer.go:135] Marking Degraded due to: unexpected on-disk state validating against rendered-master-27b5838883d09dd7eb035dc624c8ca11: expected target osImageURL "quay.io/openshift/okd-content@sha256:2fe2fd4d99c953d5bcf0d53b420a2012aae7fd12986dac8e757ad68f7b97030c", have "quay.io/openshift/okd-content@sha256:95034a94e28949af41a53b9efb2fbb0651454a7c37bab002b0646e73c4721829"
I0120 14:09:31.878608    6816 daemon.go:815] Current config: rendered-master-18f16c1426810c6c3235ea1a1a08b07d
I0120 14:09:31.878683    6816 daemon.go:816] Desired config: rendered-master-27b5838883d09dd7eb035dc624c8ca11
I0120 14:09:31.890954    6816 update.go:1661] Disk currentConfig rendered-master-27b5838883d09dd7eb035dc624c8ca11 overrides node's currentConfig annotation rendered-master-18f16c1426810c6c3235ea1a1a08b07d
I0120 14:09:31.895787    6816 daemon.go:1085] Validating against current config rendered-master-27b5838883d09dd7eb035dc624c8ca11
E0120 14:09:31.895889    6816 writer.go:135] Marking Degraded due to: unexpected on-disk state validating against rendered-master-27b5838883d09dd7eb035dc624c8ca11: expected target osImageURL "quay.io/openshift/okd-content@sha256:2fe2fd4d99c953d5bcf0d53b420a2012aae7fd12986dac8e757ad68f7b97030c", have "quay.io/openshift/okd-content@sha256:95034a94e28949af41a53b9efb2fbb0651454a7c37bab002b0646e73c4721829"

remove open-vm-tools invalid,  a new error
[root@master02 ~]# rpm-ostree uninstall open-vm-tools
Checking out tree d2e23f9... done
Resolving dependencies... done
Relabeling... done
Checking out packages... done
Running pre scripts... done
Running post scripts... done
Running posttrans scripts... done
Writing rpmdb... done
Writing OSTree commit... done
Staging deployment... done
Freed: 1.4 GB (pkgcache branches: 7)
Upgraded:
  gdbm-libs 1:1.18.1-5.fc33 -> 1:1.19-1.fc33
  python-unversioned-command 3.9.0-1.fc33 -> 3.9.1-1.fc33
  python3 3.9.0-1.fc33 -> 3.9.1-1.fc33
  python3-libs 3.9.0-1.fc33 -> 3.9.1-1.fc33
  qemu-guest-agent 2:5.1.0-8.fc33 -> 2:5.1.0-9.fc33
Removed:
  libdrm-2.4.102-2.fc33.x86_64
  libmspack-0.10.1-0.4.alpha.fc33.x86_64
  libpciaccess-0.16-3.fc33.x86_64
  libtool-ltdl-2.4.6-36.fc33.x86_64
  libxslt-1.1.34-4.fc33.x86_64
  open-vm-tools-11.2.0-1.fc33.x86_64
  xmlsec1-1.2.29-2.fc33.x86_64
  xmlsec1-openssl-1.2.29-2.fc33.x86_64
Run "systemctl reboot" to start a reboot
[root@master02 ~]#
[root@master02 ~]#
[root@master02 ~]# rpm -qa | grep open-vm-tools
warn：Found bdb Packages database while attempting sqlite backend: using bdb backend.
open-vm-tools-11.2.0-1.fc33.x86_64
[root@master02 ~]#
[root@master02 ~]#
[root@master02 ~]# systemctl reboot

# oc -n openshift-machine-config-operator logs machine-config-daemon-666bs machine-config-daemon -f
I0120 14:09:24.584661    6816 start.go:108] Version: machine-config-daemon-4.6.0-202006240615.p0-374-ga72f402c-dirty (a72f402cce4a683d4f9ba3956b5dcd297b458a54)
I0120 14:09:24.588389    6816 start.go:121] Calling chroot("/rootfs")
I0120 14:09:24.588516    6816 rpm-ostree.go:261] Running captured: rpm-ostree status --json
I0120 14:09:24.678275    6816 daemon.go:226] Booted osImageURL: quay.io/openshift/okd-content@sha256:95034a94e28949af41a53b9efb2fbb0651454a7c37bab002b0646e73c4721829 ()
I0120 14:09:24.689869    6816 daemon.go:233] Installed Ignition binary version: 2.8.1
I0120 14:09:24.718133    6816 start.go:97] Copied self to /run/bin/machine-config-daemon on host
I0120 14:09:24.720604    6816 metrics.go:106] Registering Prometheus metrics
I0120 14:09:24.720710    6816 metrics.go:111] Starting metrics listener on <IP_ADDRESS>:8797
I0120 14:09:24.728387    6816 update.go:1661] Starting to manage node: master02.manage-dev.oc4.forchange.cn
I0120 14:09:24.735549    6816 rpm-ostree.go:261] Running captured: rpm-ostree status
I0120 14:09:24.795731    6816 daemon.go:862] State: idle
Deployments:
* pivot://quay.io/openshift/okd-content@sha256:95034a94e28949af41a53b9efb2fbb0651454a7c37bab002b0646e73c4721829
              CustomOrigin: Managed by machine-config-operator
                 Timestamp: 2020-12-12T05:05:37Z
           LayeredPackages: NetworkManager-ovs glusterfs glusterfs-fuse qemu-guest-agent

  pivot://quay.io/openshift/okd-content@sha256:95034a94e28949af41a53b9efb2fbb0651454a7c37bab002b0646e73c4721829
              CustomOrigin: Managed by machine-config-operator
                 Timestamp: 2020-12-12T05:05:37Z
           LayeredPackages: NetworkManager-ovs glusterfs glusterfs-fuse open-vm-tools
                            qemu-guest-agent
I0120 14:09:24.795851    6816 rpm-ostree.go:261] Running captured: journalctl --list-boots
I0120 14:09:24.819288    6816 daemon.go:869] journalctl --list-boots:
-2 e195922e5b754a109b75474436df49f4 Mon 2021-01-18 20:48:14 UTC—Wed 2021-01-20 13:51:50 UTC
-1 01309413d4ab4dedbafd6e2640c94cf2 Wed 2021-01-20 13:54:53 UTC—Wed 2021-01-20 14:06:21 UTC
 0 e887d707d6084137b2ed56822f74b013 Wed 2021-01-20 14:07:06 UTC—Wed 2021-01-20 14:09:24 UTC
I0120 14:09:24.819316    6816 rpm-ostree.go:261] Running captured: systemctl list-units --state=failed --no-legend
I0120 14:09:24.830462    6816 daemon.go:884] systemd service state: OK
I0120 14:09:24.830576    6816 daemon.go:616] Starting MachineConfigDaemon
I0120 14:09:24.830827    6816 daemon.go:623] Enabling Kubelet Healthz Monitor
I0120 14:09:25.750968    6816 daemon.go:397] Node master02.manage-dev.oc4.forchange.cn is part of the control plane
I0120 14:09:25.794465    6816 daemon.go:815] Current config: rendered-master-18f16c1426810c6c3235ea1a1a08b07d
I0120 14:09:25.794512    6816 daemon.go:816] Desired config: rendered-master-27b5838883d09dd7eb035dc624c8ca11
I0120 14:09:25.808052    6816 update.go:1661] Disk currentConfig rendered-master-27b5838883d09dd7eb035dc624c8ca11 overrides node's currentConfig annotation rendered-master-18f16c1426810c6c3235ea1a1a08b07d
I0120 14:09:25.811130    6816 daemon.go:1085] Validating against current config rendered-master-27b5838883d09dd7eb035dc624c8ca11
E0120 14:09:25.811199    6816 writer.go:135] Marking Degraded due to: unexpected on-disk state validating against rendered-master-27b5838883d09dd7eb035dc624c8ca11: expected target osImageURL "quay.io/openshift/okd-content@sha256:2fe2fd4d99c953d5bcf0d53b420a2012aae7fd12986dac8e757ad68f7b97030c", have "quay.io/openshift/okd-content@sha256:95034a94e28949af41a53b9efb2fbb0651454a7c37bab002b0646e73c4721829"
I0120 14:09:27.841136    6816 daemon.go:815] Current config: rendered-master-18f16c1426810c6c3235ea1a1a08b07d
I0120 14:09:27.841190    6816 daemon.go:816] Desired config: rendered-master-27b5838883d09dd7eb035dc624c8ca11
I0120 14:09:27.853565    6816 update.go:1661] Disk currentConfig rendered-master-27b5838883d09dd7eb035dc624c8ca11 overrides node's currentConfig annotation rendered-master-18f16c1426810c6c3235ea1a1a08b07d
I0120 14:09:27.856244    6816 daemon.go:1085] Validating against current config rendered-master-27b5838883d09dd7eb035dc624c8ca11
E0120 14:09:27.856385    6816 writer.go:135] Marking Degraded due to: unexpected on-disk state validating against rendered-master-27b5838883d09dd7eb035dc624c8ca11: expected target osImageURL "quay.io/openshift/okd-content@sha256:2fe2fd4d99c953d5bcf0d53b420a2012aae7fd12986dac8e757ad68f7b97030c", have "quay.io/openshift/okd-content@sha256:95034a94e28949af41a53b9efb2fbb0651454a7c37bab002b0646e73c4721829"
I0120 14:09:31.878608    6816 daemon.go:815] Current config: rendered-master-18f16c1426810c6c3235ea1a1a08b07d
I0120 14:09:31.878683    6816 daemon.go:816] Desired config: rendered-master-27b5838883d09dd7eb035dc624c8ca11
I0120 14:09:31.890954    6816 update.go:1661] Disk currentConfig rendered-master-27b5838883d09dd7eb035dc624c8ca11 overrides node's currentConfig annotation rendered-master-18f16c1426810c6c3235ea1a1a08b07d
I0120 14:09:31.895787    6816 daemon.go:1085] Validating against current config rendered-master-27b5838883d09dd7eb035dc624c8ca11
E0120 14:09:31.895889    6816 writer.go:135] Marking Degraded due to: unexpected on-disk state validating against rendered-master-27b5838883d09dd7eb035dc624c8ca11: expected target osImageURL "quay.io/openshift/okd-content@sha256:2fe2fd4d99c953d5bcf0d53b420a2012aae7fd12986dac8e757ad68f7b97030c", have "quay.io/openshift/okd-content@sha256:95034a94e28949af41a53b9efb2fbb0651454a7c37bab002b0646e73c4721829"

I now have a similar situation as @klzsysy.
Does anyone have any idea where the osImageURL quay.io/openshift/okd-content@sha256:2fe2fd4d99c953d5bcf0d53b420a2012aae7fd12986dac8e757ad68f7b97030c came from?

I now have a similar situation as @klzsysy.
Does anyone have any idea where the osImageURL quay.io/openshift/okd-content@sha256:2fe2fd4d99c953d5bcf0d53b420a2012aae7fd12986dac8e757ad68f7b97030c came from?

If the master node is in a degraded state and complains with "Marking Degraded due to: unexpected on-disk state", try the following on the master node:
/run/bin/machine-config-daemon pivot "quay.io/openshift/okd-content@sha256:2fe2fd4d99c953d5bcf0d53b420a2012aae7fd12986dac8e757ad68f7b97030c"

If the master node is in a degraded state and complains with "Marking Degraded due to: unexpected on-disk state", try the following on the master node:
/run/bin/machine-config-daemon pivot "quay.io/openshift/okd-content@sha256:2fe2fd4d99c953d5bcf0d53b420a2012aae7fd12986dac8e757ad68f7b97030c"

Thank you the command helped me. After changing some other files to the desired state, the upgrade of my cluster was successful.

Thank you the command helped me. After changing some other files to the desired state, the upgrade of my cluster was successful.

What other files did you need to change to "desired state"?

What other files did you need to change to "desired state"?

In my case:

/var/lib/kubelet/config.json, twice because I run into #264, but https://github.com/openshift/okd/issues/264#issuecomment-704087624 was very helpful
/usr/local/bin/configure-ovs.sh
/usr/local/bin/vsphere-hostname.sh

In my case:

/var/lib/kubelet/config.json, twice because I run into #264, but https://github.com/openshift/okd/issues/264#issuecomment-704087624 was very helpful
/usr/local/bin/configure-ovs.sh
/usr/local/bin/vsphere-hostname.sh

I only wanted to note, that I only had to rpm-ostree uninstall open-vm-tools at one point on the nodes.  A reboot was not necessary.

I only wanted to note, that I only had to rpm-ostree uninstall open-vm-tools at one point on the nodes.  A reboot was not necessary.

In my case:
* `/var/lib/kubelet/config.json`, twice because I run into #264, but [#264 (comment)](https://github.com/openshift/okd/issues/264#issuecomment-704087624) was very helpful

* `/usr/local/bin/configure-ovs.sh`

* `/usr/local/bin/vsphere-hostname.sh`

The machine-config-daemon pod should give you the information which files did not match.

Where is the 'desired state' referenced? I don't see from that issue you linked where the desired state is set.

In my case:
* `/var/lib/kubelet/config.json`, twice because I run into #264, but [#264 (comment)](https://github.com/openshift/okd/issues/264#issuecomment-704087624) was very helpful

* `/usr/local/bin/configure-ovs.sh`

* `/usr/local/bin/vsphere-hostname.sh`

The machine-config-daemon pod should give you the information which files did not match.

Where is the 'desired state' referenced? I don't see from that issue you linked where the desired state is set.

Found this solution stating that there needs to be an octal 0 before the mode numbers in the machine configs. at least with the error that I'm seeing in relation to the 'configure-ovs.sh' file. could this be a possible fix?
https://access.redhat.com/solutions/4773161

Found this solution stating that there needs to be an octal 0 before the mode numbers in the machine configs. at least with the error that I'm seeing in relation to the 'configure-ovs.sh' file. could this be a possible fix?
https://access.redhat.com/solutions/4773161

Here is what I'm seeing in the nodes:
Failed Units: 1
ovs-configuration.service
[core@okd4-compute-0 ~]$
[core@okd4-compute-0 ~]$
[core@okd4-compute-0 ~]$ systemctl status ovs-configuration
● ovs-configuration.service - Configures OVS with proper host networking configuration
Loaded: loaded (/etc/systemd/system/ovs-configuration.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2021-01-22 13:02:21 UTC; 1h 42min ago
Process: 810 ExecStart=/usr/local/bin/configure-ovs.sh OpenShiftSDN (code=exited, status=1/FAILURE)
Main PID: 810 (code=exited, status=1/FAILURE)
CPU: 421ms
Jan 22 13:02:19 okd4-compute-0.okd4-2.apptecinc.com systemd[1]: Starting Configures OVS with proper host networking configuration...
Jan 22 13:02:19 okd4-compute-0.okd4-2.apptecinc.com configure-ovs.sh[811]: + rpm -qa
Jan 22 13:02:19 okd4-compute-0.okd4-2.apptecinc.com configure-ovs.sh[812]: + grep -q openvswitch
Jan 22 13:02:21 okd4-compute-0.okd4-2.apptecinc.com configure-ovs.sh[810]: + echo 'Warning: Openvswitch package is not installed!'
Jan 22 13:02:21 okd4-compute-0.okd4-2.apptecinc.com configure-ovs.sh[810]: Warning: Openvswitch package is not installed!
Jan 22 13:02:21 okd4-compute-0.okd4-2.apptecinc.com configure-ovs.sh[810]: + exit 1
Jan 22 13:02:21 okd4-compute-0.okd4-2.apptecinc.com systemd[1]: ovs-configuration.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 13:02:21 okd4-compute-0.okd4-2.apptecinc.com systemd[1]: ovs-configuration.service: Failed with result 'exit-code'.
Jan 22 13:02:21 okd4-compute-0.okd4-2.apptecinc.com systemd[1]: Failed to start Configures OVS with proper host networking configuration.

Here is what I'm seeing in the nodes:
Failed Units: 1
ovs-configuration.service
[core@okd4-compute-0 ~]$
[core@okd4-compute-0 ~]$
[core@okd4-compute-0 ~]$ systemctl status ovs-configuration
● ovs-configuration.service - Configures OVS with proper host networking configuration
Loaded: loaded (/etc/systemd/system/ovs-configuration.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2021-01-22 13:02:21 UTC; 1h 42min ago
Process: 810 ExecStart=/usr/local/bin/configure-ovs.sh OpenShiftSDN (code=exited, status=1/FAILURE)
Main PID: 810 (code=exited, status=1/FAILURE)
CPU: 421ms
Jan 22 13:02:19 okd4-compute-0.okd4-2.apptecinc.com systemd[1]: Starting Configures OVS with proper host networking configuration...
Jan 22 13:02:19 okd4-compute-0.okd4-2.apptecinc.com configure-ovs.sh[811]: + rpm -qa
Jan 22 13:02:19 okd4-compute-0.okd4-2.apptecinc.com configure-ovs.sh[812]: + grep -q openvswitch
Jan 22 13:02:21 okd4-compute-0.okd4-2.apptecinc.com configure-ovs.sh[810]: + echo 'Warning: Openvswitch package is not installed!'
Jan 22 13:02:21 okd4-compute-0.okd4-2.apptecinc.com configure-ovs.sh[810]: Warning: Openvswitch package is not installed!
Jan 22 13:02:21 okd4-compute-0.okd4-2.apptecinc.com configure-ovs.sh[810]: + exit 1
Jan 22 13:02:21 okd4-compute-0.okd4-2.apptecinc.com systemd[1]: ovs-configuration.service: Main process exited, code=exited, status=1/FAILURE
Jan 22 13:02:21 okd4-compute-0.okd4-2.apptecinc.com systemd[1]: ovs-configuration.service: Failed with result 'exit-code'.
Jan 22 13:02:21 okd4-compute-0.okd4-2.apptecinc.com systemd[1]: Failed to start Configures OVS with proper host networking configuration.

This is resolved in https://amd64.origin.releases.ci.openshift.org/releasestream/4-stable/release/4.6.0-0.okd-2021-01-23-132511 - MCD will no longer attempt to install duplicated open-vm-tools.
If you're upgrading from previous (4.6.0-0.okd-2021-01-17-185703) install run upgrade-master and upgrade-worker scripts to bring those to the necessary os content

This is resolved in https://amd64.origin.releases.ci.openshift.org/releasestream/4-stable/release/4.6.0-0.okd-2021-01-23-132511 - MCD will no longer attempt to install duplicated open-vm-tools.
If you're upgrading from previous (4.6.0-0.okd-2021-01-17-185703) install run upgrade-master and upgrade-worker scripts to bring those to the necessary os content

@vrutkovs, how are those scripts supposed to work?
Really need to run them locally on the nodes?
There is normally no kubeconfig for core or root users on the node ...
Also, is it correct that the upgrade-worker script is assigning the rendered-master (!) config to the workers??

@vrutkovs, how are those scripts supposed to work?
Really need to run them locally on the nodes?
There is normally no kubeconfig for core or root users on the node ...
Also, is it correct that the upgrade-worker script is assigning the rendered-master (!) config to the workers??

/open

/open

Really need to run them locally on the nodes?

Yes

There is normally no kubeconfig for core or root users on the node ...

Masters have /etc/kubernetes/static-pod-resources/kube-apiserver-certs/secrets/node-kubeconfigs/localhost.kubeconfig, workers could use kubeadmin or any other privildged user token. In any case, worker MC can be fetched externally

Also, is it correct that the upgrade-worker script is assigning the rendered-master (!) config to the workers??

Good catch, fixed it

Really need to run them locally on the nodes?

Yes

There is normally no kubeconfig for core or root users on the node ...

Masters have /etc/kubernetes/static-pod-resources/kube-apiserver-certs/secrets/node-kubeconfigs/localhost.kubeconfig, workers could use kubeadmin or any other privildged user token. In any case, worker MC can be fetched externally

Also, is it correct that the upgrade-worker script is assigning the rendered-master (!) config to the workers??

Good catch, fixed it

Really need to run them locally on the nodes?

Yes

There is normally no kubeconfig for core or root users on the node ...

Masters have /etc/kubernetes/static-pod-resources/kube-apiserver-certs/secrets/node-kubeconfigs/localhost.kubeconfig, workers could use kubeadmin or any other privildged user token. In any case, worker MC can be fetched externally

Also, is it correct that the upgrade-worker script is assigning the rendered-master (!) config to the workers??

Good catch, fixed it

@vrutkovs, another question: when am I supposed to run this exactly? Before I start the cluster upgrade at all? Or when the upgrade of the cluster services is done and only the MCO is left to do its work?

Really need to run them locally on the nodes?

Yes

There is normally no kubeconfig for core or root users on the node ...

Masters have /etc/kubernetes/static-pod-resources/kube-apiserver-certs/secrets/node-kubeconfigs/localhost.kubeconfig, workers could use kubeadmin or any other privildged user token. In any case, worker MC can be fetched externally

Also, is it correct that the upgrade-worker script is assigning the rendered-master (!) config to the workers??

Good catch, fixed it

@vrutkovs, another question: when am I supposed to run this exactly? Before I start the cluster upgrade at all? Or when the upgrade of the cluster services is done and only the MCO is left to do its work?

Before I start the cluster upgrade at all? Or when the upgrade of the cluster services is done and only the MCO is left to do its work?

During cluster upgrade, when MCO has generated new rendered-... Just to be safe you can set spec.paused:true in MCP so that MCO would not attempt to update nodes itself (don't forget to unset it when MCP shows the pool is updated)

Before I start the cluster upgrade at all? Or when the upgrade of the cluster services is done and only the MCO is left to do its work?

During cluster upgrade, when MCO has generated new rendered-... Just to be safe you can set spec.paused:true in MCP so that MCO would not attempt to update nodes itself (don't forget to unset it when MCP shows the pool is updated)

hello. I post a link to the must gathering file since it is more than 10 MB. please help my cluster went into degradation after the update.
https://yadi.sk/d/sM6rXTPHKXek1A

@ofedotov51 your last complete install was 4.5.0-0.okd-2020-07-29-070316 then I see a lot of partial upgrades to 4.5.0-0.okd-2020-08-12-020541 and all the way up to 4.6.0-0.okd-2021-01-17-185703.
Why are these were not complete? Check if you can upgrade to 4.6.0-0.okd-2021-01-23-132511 (with mentioned workarounds)

I now have a similar situation as @klzsysy.
Does anyone have any idea where the osImageURL quay.io/openshift/okd-content@sha256:2fe2fd4d99c953d5bcf0d53b420a2012aae7fd12986dac8e757ad68f7b97030c came from?

ssh login host
exec /run/bin/machine-config-daemon pivot quay.io/openshift/okd-content@sha256:2fe2fd4d99c953d5bcf0d53b420a2012aae7fd12986dac8e757ad68f7b97030c

@vrutkovs came across similar issue while updating 4.7.0-0.okd-2021-04-24-103438 to 4.7.0-0.okd-2021-05-22-050008 on a bare metal cluster, the reasons were slightly different (temporary DNS resolving failure), but eventually I got the following picture:
$ oc get clusteroperators
NAME                                       VERSION                         AVAILABLE   PROGRESSING   DEGRADED   SINCE
authentication                             4.7.0-0.okd-2021-05-22-050008   True        False         False      97m
baremetal                                  4.7.0-0.okd-2021-05-22-050008   True        False         False      3d20h
cloud-credential                           4.7.0-0.okd-2021-05-22-050008   True        False         False      3d20h
cluster-autoscaler                         4.7.0-0.okd-2021-05-22-050008   True        False         False      3d20h
config-operator                            4.7.0-0.okd-2021-05-22-050008   True        False         False      3d20h
console                                    4.7.0-0.okd-2021-05-22-050008   True        False         False      178m
csi-snapshot-controller                    4.7.0-0.okd-2021-05-22-050008   True        False         False      3d20h
dns                                        4.7.0-0.okd-2021-05-22-050008   True        False         False      3d20h
etcd                                       4.7.0-0.okd-2021-05-22-050008   True        False         False      3d20h
image-registry                             4.7.0-0.okd-2021-05-22-050008   True        False         False      3d20h
ingress                                    4.7.0-0.okd-2021-05-22-050008   True        False         False      178m
insights                                   4.7.0-0.okd-2021-05-22-050008   True        False         False      3d20h
kube-apiserver                             4.7.0-0.okd-2021-05-22-050008   True        False         False      3d20h
kube-controller-manager                    4.7.0-0.okd-2021-05-22-050008   True        False         False      3d20h
kube-scheduler                             4.7.0-0.okd-2021-05-22-050008   True        False         False      3d20h
kube-storage-version-migrator              4.7.0-0.okd-2021-05-22-050008   True        False         False      3d17h
machine-api                                4.7.0-0.okd-2021-05-22-050008   True        False         False      3d20h
machine-approver                           4.7.0-0.okd-2021-05-22-050008   True        False         False      3d20h
machine-config                             4.7.0-0.okd-2021-04-24-103438   False       True          True       43h
marketplace                                4.7.0-0.okd-2021-05-22-050008   True        False         False      177m
monitoring                                 4.7.0-0.okd-2021-05-22-050008   True        False         False      177m
network                                    4.7.0-0.okd-2021-05-22-050008   True        False         False      3d20h
node-tuning                                4.7.0-0.okd-2021-05-22-050008   True        False         False      43h
openshift-apiserver                        4.7.0-0.okd-2021-05-22-050008   True        False         False      97m
openshift-controller-manager               4.7.0-0.okd-2021-05-22-050008   True        False         False      3d20h
openshift-samples                          4.7.0-0.okd-2021-05-22-050008   True        False         False      43h
operator-lifecycle-manager                 4.7.0-0.okd-2021-05-22-050008   True        False         False      3d20h
operator-lifecycle-manager-catalog         4.7.0-0.okd-2021-05-22-050008   True        False         False      3d20h
operator-lifecycle-manager-packageserver   4.7.0-0.okd-2021-05-22-050008   True        False         False      41h
service-ca                                 4.7.0-0.okd-2021-05-22-050008   True        False         False      3d20h
storage                                    4.7.0-0.okd-2021-05-22-050008   True        False         False      3d20h

$ oc get mcp
NAME     CONFIG                                             UPDATED   UPDATING   DEGRADED   MACHINECOUNT   READYMACHINECOUNT   UPDATEDMACHINECOUNT   DEGRADEDMACHINECOUNT   AGE
master   rendered-master-55810d47d9787947900fac077ce6e367   False     True       True       3              0                   0                     1                      3d20h
worker   rendered-worker-03845709535ef46b8efede70e2c2536a   False     True       True       2              0                   0                     2                      3d20h

$ oc describe mcp | fgrep 'is reporting'
    Message:               Node okd4-control-plane-1 is reporting: "unexpected on-disk state validating against rendered-master-05130572cd434228a8d757873f90e9ac: expected target osImageURL \"quay.io/openshift/okd-content@sha256:d6dfe3828655dac553f9eb7346fd8c2bbb60c4d5635326fd0c6b2db3b3da0c31\", have \"quay.io/openshift/okd-content@sha256:770cae9f7277f7aa8418331318203177affe53eb0285d14a69f0e1939bfbbf76\""
    Message:               Node okd4-compute-1 is reporting: "unexpected on-disk state validating against rendered-worker-9b47568cad472cadca17f524f9ab858f: expected target osImageURL \"quay.io/openshift/okd-content@sha256:d6dfe3828655dac553f9eb7346fd8c2bbb60c4d5635326fd0c6b2db3b3da0c31\", have \"quay.io/openshift/okd-content@sha256:770cae9f7277f7aa8418331318203177affe53eb0285d14a69f0e1939bfbbf76\"", Node okd4-compute-2 is reporting: "unexpected on-disk state validating against rendered-worker-03845709535ef46b8efede70e2c2536a: expected target osImageURL \"quay.io/openshift/okd-content@sha256:d6dfe3828655dac553f9eb7346fd8c2bbb60c4d5635326fd0c6b2db3b3da0c31\", have \"quay.io/openshift/okd-content@sha256:770cae9f7277f7aa8418331318203177affe53eb0285d14a69f0e1939bfbbf76\""

When I'm trying to upgrade manually by running machine-config-daemon, I'm getting the following errors:
[root@okd4-compute-1 core]# /run/bin/machine-config-daemon pivot quay.io/openshift/okd-content@sha256:d6dfe3828655dac553f9eb7346fd8c2bbb60c4d5635326fd0c6b2db3b3da0c31
I0528 11:31:11.506991   42753 run.go:18] Running: nice -- ionice -c 3 oc image extract --path /:/run/mco-machine-os-content/os-content-012661350 --registry-config /var/lib/kubelet/config.json quay.io/openshift/okd-content@sha256:d6dfe3828655dac553f9eb7346fd8c2bbb60c4d5635326fd0c6b2db3b3da0c31
I0528 11:32:40.305051   42753 rpm-ostree.go:261] Running captured: rpm-ostree status --json
I0528 11:32:40.872261   42753 rpm-ostree.go:179] Previous pivot: quay.io/openshift/okd-content@sha256:770cae9f7277f7aa8418331318203177affe53eb0285d14a69f0e1939bfbbf76
I0528 11:32:43.222972   42753 rpm-ostree.go:216] No com.coreos.ostree-commit label found in metadata! Inspecting...

This is #398


JSMpeg not playing audio when websocket stream is used

I am streaming RTSP stream to web browser using ffmpeg with help of a websocket relay in node js as per  the example given here https://github.com/phoboslab/jsmpeg
FFMPEG command used:
ffmpeg -rtsp_transport tcp -i rtsp://wowzaec2demo.streamlock.net/vod/mp4:BigBuckBunny_115k.mp4 -f mpegts -c:a mp2  -c:v mpeg1video http://<IP_ADDRESS>:5100/stream_from_ffmpeg
The video is playing good, but no audio, if i open the same RTSP URL above in vlc, the video plays along with the audio

I have the same problem.
When I used the project node-rtsp-stream, JSMpeg don't play audio.
But When I used the project: rtsp2web, JSMpeg played audio.
They all used the command: ffmpeg -i rtsp://**** -f mpegts -c:v mpeg1video -ca: mp2
So I think maybe this problem isn't caused by JSMPeg.
And  I want to know if you solved this problem. If can, please tell me. Thank you.

I found the situation which caused this problem. Here are my ffmpeg options:

had problem: ffmpeg -i rtsp://**** -f mpegts -c:v mpeg1video -ca: mp2 -ar 16000
solved problem: ffmpeg -i rtsp://**** -f mpegts -c:v mpeg1video -ca: mp2 -ar 32000

I test the sampling rate: 16000、22050、32000、44100、48000。
My raw stream sampling rate is 16khz、and when I set the option -ar to 32000 and higher, I heard the audio sound.
I hope this can help you.

That's interesting. JSMpeg just uses the WebAudio createBuffer() function for audio, which should work with allmost all sample rates:

All browsers must support sample rates in at least the range 8,000 Hz to 96,000 Hz.

My assumption is that this issue is caused by a locked audio context. The test if WebAudio needs to be unlocked (testing only if we're running on iOS devices) is no longer true. All browsers start out with a locked context now. Proper unlocking is only handled by the VideoElement.
So, I'm not sure why the change in sample rate would fix that for you.


[REQUEST] add few computational/scientific languages

Thank you for this great plugin!

would you please add brushes for Fortran, Matlab, and Julia
is there any way to reduce the size of plugin?

* would you please add brushes for Fortran, Matlab, and Julia

I will provide a tool to pick any languages you like soon.

* is there any way to reduce the size of plugin?

I think the only way to reduce the size is to drop languages that you don't need. Currently this plugin only includes minified and necessary code from PrismJS so it should be as small as possible.

Thank you very much!

FYI the DIY tool is available here.


Workflow can't be stopped/terminated when wait container was terminated while main container is still running.

Pre-requisites

[X] I have double-checked my configuration
[X] I can confirm the issues exists when I tested with :latest
[ ] I'd like to contribute the fix myself (see contributing guide)

What happened/what you expected to happen?
Workflow can't be stopped/terminated when wait container was terminated while main container is still running.
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  name: gpu-evaluate-multi-step-49f294a6-b6b
  ...
  ...
spec:
  ...
  imagePullSecrets:
  - name: cloud-dragon-pull-secret
  nodeSelector:
    group: group-evaluate
  onExit: exit-handler
  podGC:
    strategy: OnPodCompletion
  podMetadata:
    annotations:
      multicluster.admiralty.io/elect: ""
      multicluster.admiralty.io/no-reservation: ""
  podPriorityClassName: free-check-priviledge
  shutdown: Terminate
  ...
----------
apiVersion: v1
kind: Pod
metadata:
  name: gpu-evaluate-multi-step-49f294a6-b6b-849349960
...
spec:
  containers:
    wait:
      ...
      Command:
        argoexec
        wait
        --loglevel
        info
      State:          Terminated
        Reason:       Completed
        Message:      Step terminated
        Exit Code:    0
        Started:      Fri, 16 Jun 2023 19:29:05 +0800
        Finished:     Sun, 18 Jun 2023 10:27:16 +0800
      Ready:          False
     ...
    main:
      ...
      State:          Running
        Started:      Fri, 16 Jun 2023 19:29:06 +0800
      Ready:          True
      ...

Version
v3.4.1
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  name: gpu-evaluate-multi-step-49f294a6-b6b
  ...
  ...
spec:
  ...
  imagePullSecrets:
  - name: cloud-dragon-pull-secret
  nodeSelector:
    group: group-evaluate
  onExit: exit-handler
  podGC:
    strategy: OnPodCompletion
  podMetadata:
    annotations:
      multicluster.admiralty.io/elect: ""
      multicluster.admiralty.io/no-reservation: ""
  podPriorityClassName: free-check-privilege
  shutdown: Terminate
  ...

Logs from the workflow controller
kubectl logs -n argo workflow-controller-5b65ff6b84-l99z6 |grep gpu-evaluate-multi-step-49f294a6-b6b

time="2023-06-21T06:22:58.572Z" level=info msg="TaskSet Reconciliation" namespace=evaluate workflow=gpu-evaluate-multi-step-49f294a6-b6b
time="2023-06-21T06:22:58.572Z" level=info msg=reconcileAgentPod namespace=evaluate workflow=gpu-evaluate-multi-step-49f294a6-b6b
time="2023-06-21T06:39:38.552Z" level=info msg="cleaning up pod" action=shutdownPod key=evaluate/gpu-evaluate-multi-step-49f294a6-b6b-849349960/shutdownPod
time="2023-06-21T06:39:38.553Z" level=info msg="https://<IP_ADDRESS>:443/api/v1/namespaces/evaluate/pods/gpu-evaluate-multi-step-49f294a6-b6b-849349960/exec?command=%2Fbin%2Fsh&command=-c&command=kill+-15+%24%28pidof+argoexec%29&container=wait&stderr=true&stdout=true&tty=false"
time="2023-06-21T06:39:38.579Z" level=info msg="signaled container" container=wait error="unable to upgrade connection: container not found (\"wait\")" namespace=evaluate pod=gpu-evaluate-multi-step-49f294a6-b6b-849349960 stderr="<nil>" stdout="<nil>"
time="2023-06-21T06:39:38.579Z" level=warning msg="failed to clean-up pod" action=shutdownPod error="unable to upgrade connection: container not found (\"wait\")" key=evaluate/gpu-evaluate-multi-step-49f294a6-b6b-849349960/shutdownPod
time="2023-06-21T06:42:58.545Z" level=info msg="Processing workflow" namespace=evaluate workflow=gpu-evaluate-multi-step-49f294a6-b6b
time="2023-06-21T06:42:58.557Z" level=info msg="Shutting down pod gpu-evaluate-multi-step-49f294a6-b6b-849349960" namespace=evaluate workflow=gpu-evaluate-multi-step-49f294a6-b6b
time="2023-06-21T06:42:58.578Z" level=info msg="Workflow step group node gpu-evaluate-multi-step-49f294a6-b6b-3503623152 not yet completed" namespace=evaluate workflow=gpu-evaluate-multi-step-49f294a6-b6b
time="2023-06-21T06:42:58.578Z" level=info msg="Workflow step group node gpu-evaluate-multi-step-49f294a6-b6b-3005692030 not yet completed" namespace=evaluate workflow=gpu-evaluate-multi-step-49f294a6-b6b
time="2023-06-21T06:42:58.578Z" level=info msg="TaskSet Reconciliation" namespace=evaluate workflow=gpu-evaluate-multi-step-49f294a6-b6b
time="2023-06-21T06:42:58.578Z" level=info msg=reconcileAgentPod namespace=evaluate workflow=gpu-evaluate-multi-step-49f294a6-b6b
time="2023-06-21T06:59:38.557Z" level=info msg="cleaning up pod" action=shutdownPod key=evaluate/gpu-evaluate-multi-step-49f294a6-b6b-849349960/shutdownPod
time="2023-06-21T06:59:38.558Z" level=info msg="https://<IP_ADDRESS>:443/api/v1/namespaces/evaluate/pods/gpu-evaluate-multi-step-49f294a6-b6b-849349960/exec?command=%2Fbin%2Fsh&command=-c&command=kill+-15+%24%28pidof+argoexec%29&container=wait&stderr=true&stdout=true&tty=false"
time="2023-06-21T06:59:38.584Z" level=info msg="signaled container" container=wait error="unable to upgrade connection: container not found (\"wait\")" namespace=evaluate pod=gpu-evaluate-multi-step-49f294a6-b6b-849349960 stderr="<nil>" stdout="<nil>"
time="2023-06-21T06:59:38.584Z" level=warning msg="failed to clean-up pod" action=shutdownPod error="unable to upgrade connection: container not found (\"wait\")" key=evaluate/gpu-evaluate-multi-step-49f294a6-b6b-849349960/shutdownPod
time="2023-06-21T07:02:58.549Z" level=info msg="Processing workflow" namespace=evaluate workflow=gpu-evaluate-multi-step-49f294a6-b6b
time="2023-06-21T07:02:58.559Z" level=info msg="Shutting down pod gpu-evaluate-multi-step-49f294a6-b6b-849349960" namespace=evaluate workflow=gpu-evaluate-multi-step-49f294a6-b6b
time="2023-06-21T07:02:58.581Z" level=info msg="Workflow step group node gpu-evaluate-multi-step-49f294a6-b6b-3503623152 not yet completed" namespace=evaluate workflow=gpu-evaluate-multi-step-49f294a6-b6b
time="2023-06-21T07:02:58.582Z" level=info msg="Workflow step group node gpu-evaluate-multi-step-49f294a6-b6b-3005692030 not yet completed" namespace=evaluate workflow=gpu-evaluate-multi-step-49f294a6-b6b
time="2023-06-21T07:02:58.582Z" level=info msg="TaskSet Reconciliation" namespace=evaluate workflow=gpu-evaluate-multi-step-49f294a6-b6b
time="2023-06-21T07:02:58.582Z" level=info msg=reconcileAgentPod namespace=evaluate workflow=gpu-evaluate-multi-step-49f294a6-b6b
time="2023-06-21T07:19:38.560Z" level=info msg="cleaning up pod" action=shutdownPod key=evaluate/gpu-evaluate-multi-step-49f294a6-b6b-849349960/shutdownPod
time="2023-06-21T07:19:38.560Z" level=info msg="https://<IP_ADDRESS>:443/api/v1/namespaces/evaluate/pods/gpu-evaluate-multi-step-49f294a6-b6b-849349960/exec?command=%2Fbin%2Fsh&command=-c&command=kill+-15+%24%28pidof+argoexec%29&container=wait&stderr=true&stdout=true&tty=false"
time="2023-06-21T07:19:38.586Z" level=info msg="signaled container" container=wait error="unable to upgrade connection: container not found (\"wait\")" namespace=evaluate pod=gpu-evaluate-multi-step-49f294a6-b6b-849349960 stderr="<nil>" stdout="<nil>"
time="2023-06-21T07:19:38.586Z" level=warning msg="failed to clean-up pod" action=shutdownPod error="unable to upgrade connection: container not found (\"wait\")" key=evaluate/gpu-evaluate-multi-step-49f294a6-b6b-849349960/shutdownPod
time="2023-06-21T07:22:58.556Z" level=info msg="Processing workflow" namespace=evaluate workflow=gpu-evaluate-multi-step-49f294a6-b6b
time="2023-06-21T07:22:58.570Z" level=info msg="Shutting down pod gpu-evaluate-multi-step-49f294a6-b6b-849349960" namespace=evaluate workflow=gpu-evaluate-multi-step-49f294a6-b6b
time="2023-06-21T07:22:58.593Z" level=info msg="Workflow step group node gpu-evaluate-multi-step-49f294a6-b6b-3503623152 not yet completed" namespace=evaluate workflow=gpu-evaluate-multi-step-49f294a6-b6b
time="2023-06-21T07:22:58.593Z" level=info msg="Workflow step group node gpu-evaluate-multi-step-49f294a6-b6b-3005692030 not yet completed" namespace=evaluate workflow=gpu-evaluate-multi-step-49f294a6-b6b
time="2023-06-21T07:22:58.593Z" level=info msg="TaskSet Reconciliation" namespace=evaluate workflow=gpu-evaluate-multi-step-49f294a6-b6b
time="2023-06-21T07:22:58.593Z" level=info msg=reconcileAgentPod namespace=evaluate workflow=gpu-evaluate-multi-step-49f294a6-b6b

Logs from in your workflow's wait container
kubectl logs -n argo -c wait -l workflows.argoproj.io/workflow=${workflow},workflow.argoproj.io/phase!=Succeeded

time="2023-06-18T02:23:05.394Z" level=info msg="Patch pods 200"
time="2023-06-18T02:24:05.374Z" level=info msg="patching pod progress annotation" progress=
time="2023-06-18T02:24:05.374Z" level=info msg="Alloc=5995 TotalAlloc=3349328 Sys=32466 NumGC=1171 Goroutines=8"
time="2023-06-18T02:24:05.393Z" level=info msg="Patch pods 200"
time="2023-06-18T02:25:05.375Z" level=info msg="patching pod progress annotation" progress=
time="2023-06-18T02:25:05.392Z" level=info msg="Patch pods 200"
time="2023-06-18T02:26:05.375Z" level=info msg="patching pod progress annotation" progress=
time="2023-06-18T02:26:05.392Z" level=info msg="Patch pods 200"
time="2023-06-18T02:27:05.375Z" level=info msg="patching pod progress annotation" progress=
time="2023-06-18T02:27:05.392Z" level=info msg="Patch pods 200"
time="2023-06-18T02:27:15.456Z" level=info msg="Step terminated"
time="2023-06-18T02:27:15.456Z" level=info msg="Killing containers"
time="2023-06-18T02:27:15.460Z" level=info msg="Get pods 200"
time="2023-06-18T02:27:16.287Z" level=info msg="Main container completed"
time="2023-06-18T02:27:16.287Z" level=info msg="No Script output reference in workflow. Capturing script output ignored"
time="2023-06-18T02:27:16.287Z" level=info msg="Saving logs"
time="2023-06-18T02:27:16.289Z" level=info msg="S3 Save path: /tmp/argo/outputs/logs/main.log, key: data/artifact-training-39-prod/evaluate/2023/06/16/c2372b66-8efa-4049-8640-d9af7bccaa7f/gpu-evaluate-multi-step-49f294a6-b6b-849349960/main.log"
time="2023-06-18T02:27:16.289Z" level=info msg="Creating minio client using static credentials" endpoint="<IP_ADDRESS>:8080"
time="2023-06-18T02:27:16.290Z" level=info msg="Saving file to s3" bucket=data-artifact endpoint="<IP_ADDRESS>:8080" key=data/artifact-training-39-prod/evaluate/2023/06/16/c2372b66-8efa-4049-8640-d9af7bccaa7f/gpu-evaluate-multi-step-49f294a6-b6b-849349960/main.log path=/tmp/argo/outputs/logs/main.log
time="2023-06-18T02:27:16.487Z" level=info msg="not deleting local artifact" localArtPath=/tmp/argo/outputs/logs/main.log
time="2023-06-18T02:27:16.487Z" level=info msg="Successfully saved file: /tmp/argo/outputs/logs/main.log"
time="2023-06-18T02:27:16.487Z" level=info msg="No output parameters"
time="2023-06-18T02:27:16.487Z" level=info msg="Saving output artifacts"
time="2023-06-18T02:27:16.487Z" level=info msg="Staging artifact: evaluate_log"
time="2023-06-18T02:27:16.487Z" level=info msg="Staging /data/log/run.log from mirrored volume mount /mainctrfs/data/log/run.log"
time="2023-06-18T02:27:16.488Z" level=info msg="Taring /mainctrfs/data/log/run.log"
time="2023-06-18T02:27:16.543Z" level=info msg="Successfully staged /data/log/run.log from mirrored volume mount /mainctrfs/data/log/run.log"
time="2023-06-18T02:27:16.543Z" level=info msg="S3 Save path: /tmp/argo/outputs/artifacts/evaluate_log.tgz, key: data/artifact-training-39-prod/evaluate/2023/06/16/c2372b66-8efa-4049-8640-d9af7bccaa7f/gpu-evaluate-multi-step-49f294a6-b6b-849349960/evaluate_log.tgz"
time="2023-06-18T02:27:16.543Z" level=info msg="Creating minio client using static credentials" endpoint="<IP_ADDRESS>:8080"
time="2023-06-18T02:27:16.544Z" level=info msg="Saving file to s3" bucket=data-artifact endpoint="<IP_ADDRESS>:8080" key=data/artifact-training-39-prod/evaluate/2023/06/16/c2372b66-8efa-4049-8640-d9af7bccaa7f/gpu-evaluate-multi-step-49f294a6-b6b-849349960/evaluate_log.tgz path=/tmp/argo/outputs/artifacts/evaluate_log.tgz
time="2023-06-18T02:27:16.680Z" level=info msg="not deleting local artifact" localArtPath=/tmp/argo/outputs/artifacts/evaluate_log.tgz
time="2023-06-18T02:27:16.680Z" level=info msg="Successfully saved file: /tmp/argo/outputs/artifacts/evaluate_log.tgz"
time="2023-06-18T02:27:16.680Z" level=info msg="Annotating pod with output"
time="2023-06-18T02:27:16.698Z" level=info msg="Patch pods 200"
time="2023-06-18T02:27:16.701Z" level=info msg="Killing sidecars []"
time="2023-06-18T02:27:16.701Z" level=info msg="Alloc=8687 TotalAlloc=3359557 Sys=32722 NumGC=1173 Goroutines=11"

Can you try the latest release?

right, probably fixed by this


Raspberry PI memory

My memory is almost out, does anyone know how to upgrade the memory on a raspberry PI?

You can't; but the used memory is probably just Linux doing a good job at using free ram to caching things.

Thanks, as if by magic... https://www.raspberrypi.org/products/raspberry-pi-4-model-b/

Yeah, just got a newsletter from my local electronics webshop, announcing the 4B.  It needs a 3.0A power supply (as opposed to 2.5A for the 3B and 3B+).  I wonder how well it manages its heat.  Any experiences yet?

What is the price at your local electronics webshop?

I've ordered a Pi 4 to test with.

€ 40 for the 1GB model to € 60 for the 4GB.  But you need a new power adapter, hdmi cable, and, optionally, case.
https://www.kiwi-electronics.nl/raspberry-pi-4?utm_source=Kiwi+Electronics+Mailing&utm_campaign=2144e8568a-RASPBERRY_PI_4&utm_medium=email&utm_term=0_779f4f564e-2144e8568a-154817201&mc_cid=2144e8568a&mc_eid=7e9867bcad

The website does say you can get away with a good quality 2.5A power supply if your USB devices use less than 500mA.

A good quality 2.5A power supply can be used if downstream USB peripherals consume less than 500mA in total.

You will need a USB-C cable if you don't have one already though.

I don’t think that it need new power adapter. Mineis usb and need to change only usb cable or adapter from micro usb to usb C.


chore: pre-commit autoupdate

:tada: This PR is included in version 4.8.0 :tada:
The release is available on:

v4.8.0
GitHub release

Your semantic-release bot :package::rocket:


call rest api one by one

I wanna call a "get" api and then call a "post" api one by one. I want that "post" dose not start until "get" finish. Right now, it starts "post" api when "get" does not finish. How to solve that?

Instead of creating a support issue in Github, please open a question on Stack Overflow and tag Alamofire. The Alamofire community is very helpful and supportive. Stack Overflow is the best place to get your question answered quickly and correctly.

From our Contribution Guidelines
Asking Questions
We don't use GitHub as a support forum. For any usage questions that are not specific to the project itself, please ask on Stack Overflow instead. By doing so, you'll be more likely to quickly solve your problem, and you'll allow anyone else with the same question to find the answer. This also allows maintainers to focus on improving the project for others.


ScrollView ref.scrollTo is not working in Android real device

Description
When i am using ScrollView ref for trigger the UI to scroll to certain content, it works well on iOS real device. but unfortunately it is not working on Android real device, iOS Simulator, and Android Simulator. I've already try in Android 10 and Android 11.
React Native version:
System:
OS: macOS 11.2.3
CPU: (8) x64 Intel(R) Core(TM) i5-8257U CPU @ 1.40GHz
Memory: 24.74 MB / 8.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 12.15.0 - ~/.nvm/versions/node/v12.15.0/bin/node
Yarn: 1.22.4 - /usr/local/bin/yarn
npm: 6.14.11 - ~/.nvm/versions/node/v12.15.0/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.5, DriverKit 20.4, macOS 11.3, tvOS 14.5, watchOS 7.4
Android SDK: Not Found
IDEs:
Android Studio: 4.2 AI-202.76<IP_ADDRESS>51085
Xcode: 12.5/12E262 - /usr/bin/xcodebuild
Languages:
Java: 13.0.2 - /Users/qubisagml/.sdkman/candidates/java/current/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.1 => 17.0.1
react-native: 0.64.1 => 0.64.1
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps To Reproduce

I make a state for certain content's y number.
I get the certain content position with onLayout and set the y number into a state.
I get the ScrollView ref with useRef
When the state is updated, i call the ScrollView scrollTo method and passing the state into it.

Expected Results
The screen automatically scroll down to the wanted certain content's position.
Snack, code example, screenshot, or link to a repository:
import React, { useState, useEffect } from 'react';
import { ScrollView } from 'react-native';

export default function App() {
  const [yIndex, setYIndex] = useState(0);
  const scrollViewRef = useRef();

  useEffect(() => {
    if (scrollViewRef.current) {
      scrollViewRef.current.scrollTo({ y: yIndex });
    }
  }, [yIndex, scrollViewRef]);

  return (
    <ScrollView
      ref={scrollViewRef}>
      <View />
      <View />
      <View />
      <View
        onLayout={(event) => {
          setYIndex(event.nativeEvent.layout.y);
        }}
      />
      <View />
    </ScrollView>
  )
};

I created the following Snack to reproduce it:
https://snack.expo.io/wai1EMhQE
Looks like it does work on both the Android and iOS simulators.
Can you try the above Snack on your device and see if it fails as you described above?

This bug persists, https://snack.expo.dev/nPYnQCzUl0


kube-aws requires you to delete ./clusters each time you run

Seems the code currently assumes the ./clusters path doesn't exist so it fails if you attempt to recreate a cluster.

Closing, as the functionality of kube-aws has significantly changed. Let us know if this needs to be re-opened.


Dev

Co-authored-by: dream2216<EMAIL_ADDRESS>

Co-authored-by: dream2216<EMAIL_ADDRESS>


Disturbed position of password show/hide icon when sign up error occurs

Describe the bug
While trying to sign up whenever any error occurs the position of password show/hide icon gets disturbed.
To Reproduce
Steps to reproduce the behavior:

Go to 'circuitverse.org'
Click on 'login'
Scroll down to 'sign up'
Click on 'sign up'
Leave everything blank and click on 'sign up'
See error

Current behavior

Screenrecording
https://user-images.githubusercontent.com/87171452/141999476-7a78d3f5-aec9-4855-af7b-98298b54d324.mp4
Are you working on this issue? (Yes/No)
Yes i have solved this issue  ,  will make a pull request soon  .

@Prerna-0202 ,is this issue still open ,should i work on this if this is still open


update thor to v0.20

I would like to use a gem in my project but it requires thor (~> 0.20), which results in the following error:
Bundler could not find compatible versions for gem "thor":
  In snapshot (Gemfile.lock):
    thor (= 0.19.4)

  In Gemfile:
    foreman was resolved to 0.85.0, which depends on
      thor (~> 0.19.1)

    release-notes (~> 4.0) was resolved to 4.0.0, which depends on
      thor (~> 0.20)

Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.

I took a look and did not see any reason why foreman could not be bumped to v0.20 so this PR does exactly that.

Is there an upcoming release that would include this update? I have exactly the same problem as the OP 🙏

@Morred it appears this project is abandoned for now. I forked the gem and merged this pr into master if you’d like to use that: https://github.com/andrewmcodes/foreman

I highly suggest that you do not include foreman in your Gemfile. I've written up my reasoning here:
https://github.com/ddollar/foreman/wiki/Don't-Bundle-Foreman

Hi @ddollar, I wonder if we could please everyone by inlining the one and only dependency (Thor) into Foreman? I believe this would address the concerns you list in the wiki above, and allow people who want to bundle Foreman to do so, which would stop the flow of issues and PRs like this one.
There's prior art for this exact same inlining situation in the Bundler source code: https://github.com/bundler/bundler/tree/master/lib/bundler/vendor
What do you think? I'm happy to do the legwork here, if it sounds good to you.

Seems reasonable to me

Great! I'll prepare a PR.

By vendoring this dependency will foreman lose the Github vulnerability notifications?

You're imagining a scenario in which a new vulnerability is discovered within the version of Thor that Foreman is depending on? As it stands, you would get a notification, and you're concerned that vendoring Thor would prevent that notification from coming through?

Yes, I am wondering if Github's vulnerability detection includes vendored dependencies. Perhaps leaving it in the Gemfile of the project but removing it from the .gemspec will be enough.
If you're going this route please include some sort of Rake task / script for unpacking/vendoring a new version of thor should said vulnerability notice come through.

If this is the scenario you mean, I think we can work around it, since it looks at Gemfile.lock as well as the gemspec: https://help.github.com/en/articles/listing-the-packages-that-a-repository-depends-on#supported-languages

@ddollar Good idea

For reference to anyone else who lands here, inlining thor was done in https://github.com/ddollar/foreman/pull/742 and released in foreman 0.86.0: https://github.com/ddollar/foreman/blob/7ce55676394f701615923181cfe31f8bf7f43cc0/Changelog.md#0860-2019-10-09


join label and content

Allows the placement of a label in code mode without intermediately switching over to markup mode.
Before:
#{
 metadata("some...");
[<label>]
}

After:
#{
 metadata("some...");
 <label>
}

I don't think this mechanism will work well, see my response here: https://github.com/typst/typst/pull/1812#issuecomment-1666934705

When you write something like the thing below, joining would attach the label to the sequence of "Hello" and the heading instead of just the heading.#{
  [Hello]
  heading[Introduction]
  <intro>
}

It would be preferable to be able to write just this, in one line:#{
  [Hello]
  heading[Introduction] <intro>
}

I answer here.
1.) But we cannot simply attach the label to the last child of a sequence (recursively), or would that work?
2.) This seems to be an exeption to regular syntax, right?

It could work, but I think dedicated syntax is better.
It would be new dedicated syntax. I would need to think a bit whether there are any ambiguities. But the upside is that it also works without a code block. E.g. to attach a label to something in an argument list.

Take your time. Syntax changes should be well prepared.

I am going to close this then, in favor of implementing designated syntax down the road.

Thank you


[build] Wrong CMake version mentioned in tag 5.0

Issue description
This is quite minor, but Raylib 5.0 still has wrong version mentioned in CMake. Literally spent half an hour thinking of wrong Cmake configuration, but config is simple enough to have errors in it.
Environment
Raylib desktop, Windows 10, MSVC 19.38.33133.0, CMake 3.28.0
Code Example
For Cmake code:
include(CMakePrintHelpers)
include(FetchContent)

# Include sub-projects.
FetchContent_Declare(
  raylib
  GIT_REPOSITORY https://github.com/raysan5/raylib.git
  GIT_TAG ae50bfa2cc569c0f8d5bc4315d39db64005b1b08 # <<<<<<<<<<<<<<<<<<<<<<<<< version 5.0
)

set(raylib_BUILD_EXAMPLES OFF CACHE BOOL "Build Raylib examples" FORCE)
set(raylib_BUILD_GAMES    OFF CACHE BOOL "Build Raylib games" FORCE)

FetchContent_MakeAvailable(raylib)

cmake_print_properties(TARGETS raylib
  PROPERTIES
    NAME
    TYPE
    VERSION
    SOVERSION
    C_STANDARD
    SOURCE_DIR
    BINARY_DIR
    INCLUDE_DIRECTORIES
    INTERFACE_INCLUDE_DIRECTORIES
    PUBLIC_HEADER
    COMPILE_DEFINITIONS
    INTERFACE_COMPILE_DEFINITIONS
    LINK_LIBRARIES
    INTERFACE_LINK_LIBRARIES
    MSVC_DEBUG_INFORMATION_FORMAT
)

It returns such output which is confusing:
[cmake] CMake version: 3.28.0
[cmake] -- The C compiler identification is MSVC 19.38.33133.0
[cmake] -- The CXX compiler identification is MSVC 19.38.33133.0
...
[cmake]  Properties for TARGET raylib:
[cmake]    raylib.NAME = "raylib"
[cmake]    raylib.TYPE = "STATIC_LIBRARY"
[cmake]    raylib.VERSION = "4.5.0" <<<<<<<<<<<<<<<<<<<<<<<<< confusion here
[cmake]    raylib.SOVERSION = "450"
[cmake]    raylib.C_STANDARD = "99"
...

Also please note that:
[cmake] CMake Deprecation Warning at out/build/x64-debug/_deps/raylib-src/CMakeLists.txt:1 (cmake_minimum_required):
[cmake]   Compatibility with CMake < 3.5 will be removed from a future version of
[cmake]   CMake.
[cmake]
[cmake]   Update the VERSION argument <min> value or use a ...<max> suffix to tell
[cmake]   CMake that the project does not need compatibility with older versions.

@borodin-devel It has already been reviewed on raylib repo master branch. I'm not re-tagging it.
Also, please note that I'm not the CMake maintainer, it was added by contributors and it's a build system I don't use neither maintain.
I'll keep this issue open for some days in case any CMake expert wants to review it.

@borodin-devel simply "we" forgot to bump the number in the CMakeLists.txt before the release was tagged.
Unfortunate, but it is what it is. Next release should be correct
Is this all you're addressing with the issue? If so, I don't see an acceptable way to change this that Ray would agree with, so it can be closed.

@Peter0x44 What about the CMake version deprecation? Can it be reviewed?
[cmake] CMake Deprecation Warning at out/build/x64-debug/_deps/raylib-src/CMakeLists.txt:1 (cmake_minimum_required):
[cmake]   Compatibility with CMake < 3.5 will be removed from a future version of
[cmake]   CMake.
[cmake]
[cmake]   Update the VERSION argument <min> value or use a ...<max> suffix to tell
[cmake]   CMake that the project does not need compatibility with older versions.

@raysan5 changing the first line of CMakeLists.txt to require cmake 3.5 removes that warning for me.
cmake 3.5 is from 2016 so I think bumping this shouldn't be an issue. I doubt anyone is testing older versions anyway, it's unlikely they even work.
I can submit a PR for that if it's desired.

I can submit a PR for that if it's desired.

@Peter0x44 no worries, I can just PR it myself, I'm working on it right now.

@borodin-devel it would still be building 5.0, just cmake won't report it as such
which, could be confusing
Actually, some distro packages built with cmake have incorrectly named sos... including arch
https://archlinux.org/packages/extra/x86_64/raylib/
usr/lib/libraylib.so.4.5.0
usr/lib/libraylib.so.450

Fixing this would require re-tagging a release, but it won't matter to people who aren't using cmake.
But, you can still use dlsym on raylibVersion if you really want to make sure which so version you have.
In static linking (majority of cases) it is mostly irrelevant.
Opening your raylib.h will also confirm the version you're using.


CUDA error 700 : an illegal memory access was encountered

RTX 3090
Windows 11
CUDA 12.3
Same result with WSL2 or Native.

ggml_init_cublas: GGML_CUDA_FORCE_MMQ:   no
ggml_init_cublas: CUDA_USE_TENSOR_CORES: yes
ggml_init_cublas: found 1 CUDA devices:
Device 0: NVIDIA GeForce RTX 3090, compute capability 8.6
// snip all the tensor stuff
llm_load_print_meta: format           = GGUF V3 (latest)
llm_load_print_meta: arch             = llama
llm_load_print_meta: vocab type       = SPM
llm_load_print_meta: n_vocab          = 32000
llm_load_print_meta: n_merges         = 0
llm_load_print_meta: n_ctx_train      = 32768
llm_load_print_meta: n_embd           = 4096
llm_load_print_meta: n_head           = 32
llm_load_print_meta: n_head_kv        = 8
llm_load_print_meta: n_layer          = 32
llm_load_print_meta: n_rot            = 128
llm_load_print_meta: n_gqa            = 4
llm_load_print_meta: f_norm_eps       = 0.0e+00
llm_load_print_meta: f_norm_rms_eps   = 1.0e-05
llm_load_print_meta: f_clamp_kqv      = 0.0e+00
llm_load_print_meta: f_max_alibi_bias = 0.0e+00
llm_load_print_meta: n_ff             = 14336
llm_load_print_meta: rope scaling     = linear
llm_load_print_meta: freq_base_train  = 100000.0
llm_load_print_meta: freq_scale_train = 1
llm_load_print_meta: n_yarn_orig_ctx  = 32768
llm_load_print_meta: rope_finetuned   = unknown
llm_load_print_meta: model type       = 7B
llm_load_print_meta: model ftype      = mostly Q8_0
llm_load_print_meta: model params     = 7.24 B
llm_load_print_meta: model size       = 7.17 GiB (8.50 BPW)
llm_load_print_meta: general.name   = models
llm_load_print_meta: BOS token = 1 ''
llm_load_print_meta: EOS token = 2 ''
llm_load_print_meta: UNK token = 0 ''
llm_load_print_meta: LF token  = 13 '<0x0A>'
llm_load_tensors: ggml ctx size =    0.11 MiB
llm_load_tensors: using CUDA for GPU acceleration
llm_load_tensors: mem required  =  132.92 MiB
llm_load_tensors: offloading 32 repeating layers to GPU
llm_load_tensors: offloading non-repeating layers to GPU
llm_load_tensors: offloaded 35/35 layers to GPU
llm_load_tensors: VRAM used: 7205.83 MiB
...................................................................................................
llama_new_context_with_model: n_ctx      = 4096
llama_new_context_with_model: freq_base  = 100000.0
llama_new_context_with_model: freq_scale = 1
llama_kv_cache_init: offloading v cache to GPU
llama_kv_cache_init: offloading k cache to GPU
llama_kv_cache_init: VRAM kv self = 512.00 MiB
llama_new_context_with_model: kv self size  =  512.00 MiB
llama_build_graph: non-view tensors processed: 740/740
llama_new_context_with_model: compute buffer total size = 291.07 MiB
llama_new_context_with_model: VRAM scratch buffer: 288.00 MiB
llama_new_context_with_model: total VRAM used: 8005.83 MiB (model: 7205.83 MiB, context: 800.00 MiB)
Entering chat...
Bot: Jade decided it was time to unwind after
CUDA error 700 at D:\a\LLamaSharp\LLamaSharp\ggml-cuda.cu:7576: an illegal memory access was encountered
current device: 0

I have compiled llama.cpp with CUDA support and it works.  I've tried it with a few different 7b models that work with llama.cpp but give this error with LlamaSharp. I've tried sending the same prompts to llama.cpp and that also works. And to make matters more confusing, it started working for a bit, then it started failing again.

Could you get a stack trace from the exception? That'll tell us what C# code was running when it crashed.

I'm getting this too, and it hard crashes the host app even if you have try/catch all over the place.
In my case It's using Apple Silicon.
llama_new_context_with_model: n_ctx      = 32768
llama_new_context_with_model: freq_base  = 10000.0
llama_new_context_with_model: freq_scale = 1
llama_new_context_with_model: kv self size  = 4096.00 MiB
llama_build_graph: non-view tensors processed: 740/740
ggml_metal_init: allocating
ggml_metal_init: found device: Apple M1
ggml_metal_init: picking default device: Apple M1
ggml_metal_init: default.metallib not found, loading from source
ggml_metal_init: loading '/Users/jameshancock/Repos/TheDailyFactum/Server/Tools/Chat/bin/Debug/net8.0/runtimes/osx-arm64/native/ggml-metal.metal'
ggml_metal_init: GPU name:   Apple M1
ggml_metal_init: GPU family: MTLGPUFamilyApple7 (1007)
ggml_metal_init: hasUnifiedMemory              = true
ggml_metal_init: recommendedMaxWorkingSetSize  = 10922.67 MiB
ggml_metal_init: maxTransferRate               = built-in GPU
llama_new_context_with_model: compute buffer total size = 2139.07 MiB
llama_new_context_with_model: max tensor size =   102.54 MiB
ggml_metal_add_buffer: allocated 'data            ' buffer, size =  4893.70 MiB, ( 4895.08 / 10922.67)
ggml_metal_add_buffer: allocated 'kv              ' buffer, size =  4096.02 MiB, ( 8991.09 / 10922.67)
ggml_metal_add_buffer: allocated 'alloc           ' buffer, size =  2136.02 MiB, (11127.11 / 10922.67)ggml_metal_add_buffer: warning: current allocated size is greater than the recommended max working set size
ggml_metal_graph_compute: command buffer 0 failed with status 5
GGML_ASSERT: /Users/runner/work/LLamaSharp/LLamaSharp/ggml-metal.m:1611: false
The program '[26619] Chat.dll' has exited with code 0 (0x0).

It should have fallen back automatically to CPU and swapped like crazy.

Right. But the actual issue here is that llama.cpp errors are crashing any LlamaSharp based .net application to the desktop.  We can't handle these errors.
And in addition to the fact that these errors can't be handled, LLamaSharp can't fall back properly in many cases to CPU from GPU because of memory errors like other systems like LM Desktop do just fine.

According to MS's docs, the best way to work around abort() is to run in a separate process spun up in C# before calling into the C++ library.

Yep that would be the only way to handle it (an abort() just destroys the process, with no way to recover).
That's not something LLamaSharp does internally at the moment (and personally I would say we're unlikely to, remaining just a wrapper around llama.cpp).
Instead imo the two ways to handle this would be at a higher level (load LLamaSharp in a separate process and interact with it) and at a lower level (contact the llama.cpp team ask them to use a recoverable kind of error detection where possible).

I can ask if you'd prefer not to, but LLamaSharp doesn't have any special pull in the llama.cpp project. To be honest at the moment I suspect any such request will be largely ignored (unless it's accompanied by PRs to implement better error handling).

Could you do so? This really is killing us because it doesn't allow us to fall back to not using the GPU when this occurs.

I'm opened up https://github.com/ggerganov/llama.cpp/issues/4385

Although I will say I wouldn't expect this to change quickly if at all! It woud be a large change in both LLamaSharp and llama.cpp! If it's an issue you currently have you'll want to split off your usage of LLamaSharp into a separate process.

Some interesting discussion related to error handling in llama.cpp here: https://github.com/ggerganov/ggml/pull/701


Chrome Debugger when Running on Device

Is there any way to use the Chrome Debugger when running on device (I am in dev mode and am "Accessing development server from device")?
From this line it looks like the host is hard coded as localhost.

Debugging on device is not supported out of the box.

Hard coded localhosts aren't just a debugging on device issue. I develop our iOS app on a Windows machine so the packager runs there and I have to patch AppDelegate.m and RCTWebSocketExecutor.m to make things work.
Being able to specify packager host in react-native-cli commands would be a nice addition:
react-native run-ios --packager-host <IP_ADDRESS>:8081

@cancan101 Thanks for bringing this up!
This still isn't supported, but there's a Product Pains entry you can upvote to get more attention around the issue of configurable hosts and ports for React Native development tools.
Closing out this issue in favor of the PP discussion, or a PR!


Typings for ...props on components

Raised to address #1644
Checklist:

[ ] Documentation N/A
[ ] Tests N/A
[x] Ready to be merged

@penx it looks like you're the person who would need to merge this? Is there anything else I need to do here before that can happen?


Fork!

Following an internal policy change at Microsoft, this project has no maintainers able to make releases.
I'm going to continue work in my own personal fork of the repository at https://github.com/benjamin-bader/thrifty.  Will need to repackage it to facilitate publication on Maven Central

Unfortunate :( we use still use thrift in our project and wanted to explore KMP (ios, android, web) using this lib. I see that there are more recent commits on this repo compared to the fork, is the fork just for releases? If I want to contribute, which repo should I work on?

Good question.  The fork is in limbo at the moment - it's possible that publishing rights will be restored.  I'm not clear on the details yet.  Please pick this one if you'd like to contribute, and if the situation doesn't resolve then I can port your work over.


Does to_wkt use PROJ version to determine WKT version to use?

I'm in the process of converting the pyresample project to use WKT internally by calling CRS.to_wkt(). We've had issues in the past with other projects where we would pass pyproj.CRS.to_wkt() to rasterio's CRS object. Rasterio seemed to depend on the version of GDAL installed (GDAL 3 -> WKT2 supported, otherwise WKT1). So I'm wondering, does pyproj's support of WKT2 depend on the version of PROJ? Is there ever a chance for a user to install current pyproj with an old-ish PROJ and get errors when to_wkt tries to convert to WKT2?

This should help: https://pyproj4.github.io/pyproj/latest/crs_compatibility.html

Perfect! Thank you. That helps a lot. However, I couldn't find the answer I specifically wanted but I may just be missing an explicit answer on that page or have a misunderstanding of pyproj. If I do:
pyproj.CRS.from_user_input(some_input).to_wkt()

Is there ever a case where I could have a version of pyproj with those methods where to_wkt defaults to WKT2 where it would then fail (exception) because WKT2 isn't supported by the installed version of PROJ. Put another way, what library does the WKT conversion in pyproj? Is it coded in pyproj or does it come from PROJ? Does the minimum version of PROJ required by pyproj support WKT2 so this could never happen?

If you have pyproj >= 2 it should always support WKT2.

Is it coded in pyproj or does it come from PROJ?

It comes from PROJ

Does the minimum version of PROJ required by pyproj support WKT2 so this could never
happen?

Correct

Great.pyproj >= 2.3 is probably what pyresample will require so this looks good. Thanks again.