text:
Typeahead to support multiple selections

Hello I was just checking out the typeahead (autocomplete) widget in the wip 2.0 branch and thought I'd request a variant that supported multiple selections. So after i pick one I can pick another and they both appear in the field with a little X next to them or something.
Like http://loopj.com/jquery-tokeninput/ which i'm using atm but it's a bit of a turd to style...

For now i think we're going to keep it simple - maybe in the future we'll consider extending it that way

Hi. Plz reopen this issue, so you might be able to take a note of it some time in the future. Thank you

#2007 is where we'll be tracking it

authors: Merg1255 fat worldspawn


text:
Call to client.connect() fails: java.lang.NullPointerException

Hi there,
I'm trying to use the client without much success. I had a look at the examples and wrote my own classes but I can't avoid this annoying issue: every time I call the connect method from the BasicClient class I'm getting this exception (it does not matter whether I use directly the BasicClient or I try to wrap it into the Twitter4jStatusClient class):

Exception in thread "hosebird-client-io-thread-0" java.lang.NullPointerException
	at com.twitter.hbc.httpclient.RestartableHttpClient.getConnectionManager(RestartableHttpClient.java:89)
	at com.twitter.hbc.httpclient.ClientBase.run(ClientBase.java:165)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:722)

Actually, by simply copying some code example from the hbc-example module (e.g.: SampleStreamExample) the error is still there. Running the same code from the hbc-module gives no error and works properly; I am definetely missing something...
I ran the debugger and the error is caused by the underlying property from the ClientBase class, which when executing line 165 from this class, is null.
The complete stack is:

Daemon Thread [hosebird-client-io-thread-0] (Suspended (exception NullPointerException))
	RestartableHttpClient.getConnectionManager() line: 89
	ClientBase.run() line: 165
	ThreadPoolExecutor.runWorker(ThreadPoolExecutor$Worker) line: 1145
	ThreadPoolExecutor$Worker.run() line: 615
	Thread.run() line: 722

Any help will be much appreciated, thanks.

I had this issue with hadoop dependencies also pulling in (different) versions of httpclient.

source: gharchive/issue

authors: jarandaf richmidwinter

repo: twitter/hbc

license_type: permissive

license_source: bigquery


text:
Testing, please ignore. (tskoez)

Bug bounty test - please ignore.... Please DO NOT APPROVE THIS! (tskoez)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.nunezalmorado seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

source: gharchive/pull-request

authors: CLAassistant nunezalmorado

repo: twitter/twitter-text


text:
Typeahead cuts my JSON result

Hi folks!
I'm currently migrating a project from Bootstrap 2 to Bootstrap 3.
Since I used the old Bootstrap Typeahead I followed the suggestion and went over to Twitter Typeahead.
I'm just experiencing a strange problem:
I fetch data from a remote URL (the backend) where the typed string is evaluated and the server returns a JSON array containing JSON objects, which have the same properties.
There are 3 important properties: id, name and path.
I use the path inside the template like {{{path}}} and the name is the valueKey. The id is set as a data-attribute on typeahead:selected.
Now it is possible, that the name can be identical, but the path and id differ. But typeahead only shows me the first item inside the suggestion list.
Example:
Server response:
[{
    id: 1,
    name: 'Foo',
    path: 'Problems > Foo'
},{
    id: 23,
    name: 'Foo',
    path: 'Food > Foo'
}]

Suggestion list:
Problems > Foo

Do you have a workaround for me?

do you have any fix for typeahead.js 0.9.3.
or can you suggest me any other solution.

authors: Regaddi ShrinivasMese

license: mit


text:
[UPDATE] Readme - Adding table of contents on readme

Problem
There wasn't a table of contents to jump right into chapters
Solution
Add table of contents chapter
Result
We will have the possibility to get into a chapter quickly

Thank you @Zakichanu

authors: Zakichanu zacmos

repo: twitterdev/twitter-api-java-sdk

license_source: github-api


text:
Motd Modification

Can you add a new option in motd like : Map motd = on/off Custom Motd= On/OFF
i have the overcast network motd exactly but i cant put because the map motd replace D:

I think developers are not going to add that to prevent the abuse of the plugin by turning the motd off and added whatever they want there.

There is a plugin called motd manager for that use

@AngelCasillas01 Pero no funciona aun asi, el Cardinal tiene como un Overrride MOTD algo asi

authors: AngelCasillas01 Jonmuxu RubeGamerV felipufeliu

repo: twizmwazin/CardinalPGM


text:
No match page upload when you run /cycle -f 0

I tried this the other day,  are you sure it didn't send the message after cycling?

@dentmaged The module is unloaded and has no access to the other stats modules when the map is immediately ended and cycled from.

@iEli2tyree011 For me, maybe the message had been sent, but it was in the packet queue?

Closing as this feature is being removed due to incompleteness


text:
Reason code for failed jobs

I see there was work to propagate the reason code for failed jobs. However, it looks like it's not showing up for some reasons. My jobs have failed due to memory limitation. However, when querying the status of the job, I do not see any reason field.
Sep 15 15:03:14 foo kernel: Killed process 27918 (python) total-vm:1357356kB, anon-rss:1023804kB, file-rss:0kB
Sep 15 15:03:14 foo systemd: Stopped docker container 797b6bffc3760a5cf766965de3248d2eff58479c0ccd8d5315b39dbe4ea5c13f.
Sep 15 15:03:14 foo systemd: Stopping docker container 797b6bffc3760a5cf766965de3248d2eff58479c0ccd8d5315b39dbe4ea5c13f.
Sep 15 15:03:14 foo journal: time="2016-09-15T15:03:14.752321974Z" level=info msg="{Action=wait, ID=797b6bffc3760a5cf766965de3248d2eff58479c0ccd8d5315b39dbe4ea5c13f, LoginUID=4
294967295, PID=27881}"
Sep 15 15:03:14 foo kernel: XFS (dm-1): Unmounting Filesystem
Sep 15 15:03:14 foo mesos-slave[14656]: I0915 15:03:14.868490 14692 slave.cpp:3211] Handling status update TASK_FAILED (UUID: edc3f4d2-fdb0-4163-adcf-ac58730d11ff) for task 92af32c4-d78e-4960-a78b-2a03070bc047 of framework 2566d37b-3913-4069-baa0-a4a398bddf1c-0000 from executor(1)@10.0.0.1:43590
Sep 15 15:03:14 foo mesos-slave[14656]: I0915 15:03:14.920524 14689 status_update_manager.cpp:320] Received status update TASK_FAILED (UUID: edc3f4d2-fdb0-4163-adcf-ac58730d11ff) for task 92af32c4-d78e-4960-a78b-2a03070bc047 of framework 2566d37b-3913-4069-baa0-a4a398bddf1c-0000
..

Query the status:
[root@hkgcpu10 mesos]# curl -u user: -X GET http://cook:12321/rawscheduler?job=62469824-7b55-11e6-a363-000c295e64ae
[{"labels":{},"mem":1000.0,"max_retries":1,"max_runtime":86400000,"name":"cookjob","command":"python \/test.py","env":{},"framework_id":null,"ports":0,"instances":[{"start_time":1473951736936,"executor_id":"92af32c4-d78e-4960-a78b-2a03070bc047","hostname":"foo","slave_id":"5cbb4cd9-cefd-4daa-a421-376d89328ab6-S6","preempted":false,"end_time":1473951794921,"backfilled":false,"ports":null,"status":"failed","task_id":"92af32c4-d78e-4960-a78b-2a03070bc047"}],"priority":50,"status":"completed","uuid":"62469824-7b55-11e6-a363-000c295e64ae","uris":null,"cpus":1.5}]

You can see that the task id is the same: 92af32c4-d78e-4960-a78b-2a03070bc047

Are these logs from the mesos slave log or the executor log?
You can check the cook log to see if it got the memory limit exceeded reason from mesos and didn't propogate it correctly or if mesos didn't recognize it as memory limit exceeded.

Hi @wyegelwel,
unfortunately, I set the cook log level to WARNING.. so I guess I won't be able to see those messages if they are reported using loglevel INFO. I checked the cook.log and didn't see anything.
Thanks,
Matteo

By the way, those logs are from the slave. The executor logs don't contain much info.

Hmm, unfortunately we only print the status from mesos with log level info.
What log level do you have for the mesos masters? You might be able to find the status message there.
Alternatively, you could try setting cook log level to info for a little while and re-run the job. I'm wondering if your python process got killed by Dockers oom killer and so mesos doesn't treat it as a memory limit exceeded error.
For what it is worth we have previous observed memory limit exceeded reasons when querying cook.

Also sorry if that was a bit unclear I'm typing on my phone.

I had a look at the mesos master, and don't see much there beside the "Status update TASK_FAILED" message for the task.
I'm running the default log level there, which is INFO.
I think you are right about the Docker OOM killer. I guess Mesos doesn't catch.. only option would be to use mesos containers.

Verified this using Mesos native containers (instead of Docker) and reason is propagated indeed when container gets killed due to OOM.

repo: twosigma/Cook


text:
Ambiance: active buttons in stdout/err should have blue bkg

Issue #3624. Please, check.

:+1:

kick jenkins

authors: alice-kroch kpaharelau scottdraves

repo: twosigma/beaker-notebook


text:
EasyForm text field width

width parameter to addTextField seems to be ignored.

if the width is omitted then the field should stretch to fill the form horizontally
if provided, then it should be measured in characters not pixels.

here is classic beaker doing it correctly:

repo: twosigma/beakerx


text:
stop webtau feature tests from overriding html reports

Closes #323

do you want to have 1 file per test file? or a timestamped combined file per test run?

I don't think we need the timestamp.  Rebuilding will nuke the code in target anyway.  The problem is more about multiple tests in the same run overriding the report.

I think reports are being generated next to the test file right now and marked as ignore in git

authors: MykolaGolubyev tsiq-clemens tsiq-karold

repo: twosigma/webtau


text:
When multiple namespaces are forwarded, only the first provided namespace appends namespace to the hostname.

I tried to make sense of https://github.com/txn2/kubefwd/issues/4 that lead to ability to provide multiple namespaces to forward, but I'm still a bit uncertain about this behavior.
	 // ShortName field only use short name for the first namespace and context
... 		if opts.ShortName != true { 				serviceHostName = serviceHostName + "." + pod.Namespace 			}
This has lead to some inconsistencies within my team, depending on which order the namespaces are flagged for forwarding, one user will commit a development configuration referencing redis.db and microservice-1 where another user will expect redis and microservice-1.appname.
I propose that this is configurable behavior, as it seems to be by design according to the original issue referenced above.
It seems like a straightforward change, but I would like opinions on the best way to implement. A single flag at the CLI, such as --hostnames --fq for a more terse "fully-qualified"?

@zcmack every entry gets SERVICE.NAMESPACE and SERVICE.NAMESPACE.svc.cluster.local, however, the first forwarded namespace also gets a non-namespaced entry. The logged output does not show all the rules added to the /etc/hosts.
While running kubefwd check out /etc/hosts and you should see the entries.
Example for kubefwd svc -n first -n second assuming the namespaces first and second have services a, b and c.
127.1.28.1       a a.first.svc.cluster.local a.first
127.1.28.2       b b.first.svc.cluster.local b.first
127.1.28.3       c c.first.svc.cluster.local c.first
127.1.28.4       a.second.svc.cluster.local a.second
127.1.28.5       b.second.svc.cluster.local b.second
127.1.28.6       c.second.svc.cluster.local c.second

@zcmack keep in mind the non-namespaced service (the first one forwarded) is only a convenience for developing as though you are in that namespace, however, all services may be accessed by service.namespace or service.namespace.svc.cluster.local.

authors: cjimti zcmack


text:
Fix OpenCV dependency in Python 3

Some tests currently fail because OpenCV was difficult to install on Python 3 until recently. There now appears to be a conda installer, so we should fix the travis config to properly install OpenCV on both Python 2 and 3 (and make sure the tests pass).

This is the same issue as #3, and the same issue with ffmpeg applies, I think, so closing this one.

repo: tyarkoni/featureX


text:
allows passing State instances instead of names; closes #153

Addresses issue in #153--allows State instances to be passed in as arguments to add_transition instead of requiring strings.

Coverage decreased (-0.2%) to 99.501% when pulling 2c3195e1fcf2c5ceacb9f0b96ccab408aa2ba978 on state-refs into bbd1a79b33a5b843004f9b135492e6561681bb7e on master.

Coverage increased (+0.002%) to 99.701% when pulling f54b8cdabf5d64324547c7c32e2276ad2daec554 on state-refs into bbd1a79b33a5b843004f9b135492e6561681bb7e on master.

Coverage increased (+0.002%) to 99.701% when pulling f54b8cdabf5d64324547c7c32e2276ad2daec554 on state-refs into bbd1a79b33a5b843004f9b135492e6561681bb7e on master.

authors: coveralls tyarkoni

repo: tyarkoni/transitions

license: MIT


text:
Is it possible to support Scala Native?

Is it possible to support Scala Native?
Fastparse supports scala native(2.12, 2.13) but does not support scala 3. On the other hand, catsparse supports scala 3, but does not support scala native😖

Thanks! I will try it!

Exciting! Thanks!

FYI, if you are looking for the combination of Native+Scala3 you'll be blocked by https://github.com/typelevel/cats/issues/4117 which is blocked by https://github.com/typelevel/scalacheck/pull/868 which is presumably blocked by https://github.com/lampepfl/dotty/pull/14156 which comes in Scala 3.1.2.

It's actually a really nice option to write compilers using Scala Native.

Closed by #376 and #426

authors: Erdemus armanbilge i10416 johnynek

repo: typelevel/cats-parse


text:
Versioning scheme convention

Right now I'm trying to match versions with the latest Typst version (currently 0.10.0 -- current npm package is typst@0.10.0-5)
https://github.com/typst/typst/releases
https://www.npmjs.com/package/typst?activeTab=versions
note that there's a X.Y.Z-N where N goes up. idk if that's the "right" way to do it or not? are there other projects that do it better/differently? is there a convention to this? basically I want a four-part semver specific not a three part specifier lol.
Sidenote: should the first 0.11.0 release be typst@0.11.0 or typst@0.11.0-1 or typst@0.11.0-0 ?

i think ill do it sorta like debian does https://serverfault.com/questions/604541/debian-packages-version-convention where it's 1.2.3-1 and then 1.2.3-2? that's what im already doing lol.

Actually what if I did more of a "bindings" approach instead of a "redist" approach?
https://github.com/semver/semver/issues/352
What about something like this:

typst-cli: 0.10.0-1 -- holds JUST the binary cli blob, uses 1.2.3-1 versioning like debian. this is a redist
typst: 1.0.0+0.10.0 -- holds all the magic fancy bindings and types and such. uses 1.2.3+4.5.6 versioning where 4.5.6 is the "underlying lib" of the bindings wrapper 1.2.3?


text:
fix typo in ansi-render README

referenced PR

In accordance with the updated submission guidelines minor documentation fixes that cannot break existing users of the package are now allowed.

repo: typst/packages


text:
natrix:0.1.0

I am submitting

[x] a new package
[ ] an update for a package

Description: This package solve https://github.com/typst/typst/issues/1617 and can generate LaTeX looking matrices

I have read and followed the submission guidelines and, in particular, I

[x] selected a name that isn't the most obvious or canonical name for what the package does
[x] added a typst.toml file with all required keys
[x] added a README.md with documentation for my package
[x] have chosen a license and added a LICENSE file or linked one in my README.md
[x] tested my package locally on my system and it worked
[x] excluded PDFs or README images, if any, but not the LICENSE

Thank you.

authors: Enter-tainer elegaanz


text:
Long tables in figures that should overflow onto the next page don't overflow

Description
If you have a table longer than the height of your page, it will overflow the remaining rows onto the next page. However, if you place that table in a figure, then it will not overflow, and it'll just place all the remaining cells overlapping at the bottom of the table.
Reproduction
= Here is a long table

#figure(
  table(
    columns: 2,
    ..([#lorem(5)], [#lorem(8)]) * 200
  )
)

Reproduction URL
https://typst.app/project/ptxQmUUyMdH27t78RMrCOJ
Operating system
Web app
Typst version

[X] I am using the latest version of Typst

Ah, that works. Thanks.

repo: typst/typst


text:
Bibliography chapter attribute breaks bibliography entry rendering

Description
Field chapter of bibliography record breaks bibliography. It seems that kind of bibliography item (inbook or article) does not matter.

Issues stays for latest (v0.10.0) on Web and standalone compiler on Linux platform.
Issue #1161 seems to be related.
Reproduction URL
https://typst.app/project/ruTfM_JQH5u0j5EqPh7eHE
Operating system
WebApp/Linux.
Typst version

[X] I am using the latest version of Typst

Which bibliography style, and what does it look like in another CSL-based apps?

The issue exists for APA and IEEE for sure (see reproduction URL). I have no other CSL-based app so can't provide any info here.

authors: Enivex daskol


text:
bibliography missing translator and editor

Description
some properties of a citation are missing from the long form of a bibliography entry while showing in the short form. I found the problem in the translator and editor properties, but it is likely to happen in multiple properties.
this is the bibtex file:
@book{test,
  title = {{title}},
  author = {author},
  translator = {translator},
  editor = {editor},
  year = {2024},
  series = {{series}},
  publisher = {publisher},
  address = {city}
}

the test file I used:
#set cite(style: "chicago-fullnotes")
@test
#bibliography("library_test.bib")

expected result:
Author. Title. Edited by Editor. Translated by Translator. Series. city: publisher, 2024.
actual result:

Reproduction URL
No response
Operating system
Linux
Typst version

[X] I am using the latest version of Typst

When you write #set cite(style: "chicago-fullnotes") you're setting only the style for citations, not the bibliography (which here has defaulted to "IEEE"). If you want to set both, use #set bibliography(style: ) instead

authors: Enivex YonatanRubin


text:
Use --locked for install command

Installation should use the Cargo.lock from the repo for reproducibility and theoretically to reduce the possibility of a supply-chain attack.

Makes sense.

authors: laurmaedje mattfbacon


text:
Add Devanagari numbering

This small PR adds support for Devaganari numbering, aiming to resolve https://github.com/typst/typst/issues/4843 .
I'm not sure what the best name for the new NumberingKind is. I tentatively went for DevanagariNumber, with the idea that another numbering could be added later with Devanagari letters.

Thanks!

authors: FlorentCLMichel laurmaedje


text:
Install on turnkey linux

Here's what got my setup working on Turnkey Linux LAMP virtual server. I'm putting this up in the hopes that it will be useful and allow the installer script to evolve into something that is more generic.
instructions for turnkey linux LAMP app
As root:
apt-get install sudo
useradd -d /home/portia -s /bin/bash -m portia
passwd portia
echo "portia ALL=(ALL:ALL) ALL">> /etc/sudoers.d/portia
chmod 0440 /etc/sudoers.d/portia
apt-get install gcc
apt-get install apt-utils
apt-get install aptitude
aptitude update
as portia:
git clone https://github.com/tytek2012/Portia_Installer_Script.git
-- the above step is optional because the script as written at present doesn't work
sudo aptitude install curl git git-core python-pip python-dev toilet libxml2-dev libxslt1-dev libffi-dev libssl-dev
sudo aptitude upgrade
sudo aptitude dist-upgrade
sudo pip install virtualenv
sudo git clone https://github.com/scrapinghub/portia.git
sudo virtualenv portia --no-site-packages
source ~/portia/bin/activate
cd ~/portia/slyd/
sudo ln -s ~/portia/src ~/portia/slyd/
sudo chown -R portia:portia ~/portia
cd ~/portia/slyd/
~/portia/bin/pip install service_identity
cd ~/portia/
~/portia/bin/pip install -r requirements.txt
pip install -e ./slybot

you should post that to your github and I will link to it
On Sat, Feb 7, 2015 at 3:35 PM, TMLutas notifications@github.com wrote:

Here's what got my setup working on Turnkey Linux LAMP virtual server. I'm
putting this up in the hopes that it will be useful and allow the installer
script to evolve into something that is more generic.
instructions for turnkey linux LAMP app
As root:
apt-get install sudo
useradd -d /home/portia -s /bin/bash -m portia
passwd portia
echo "portia ALL=(ALL:ALL) ALL">> /etc/sudoers.d/portia
chmod 0440 /etc/sudoers.d/portia
apt-get install gcc
apt-get install apt-utils
apt-get install aptitude
aptitude update
as portia:
git clone https://github.com/tytek2012/Portia_Installer_Script.git
-- the above step is optional because the script as written at present
doesn't work
sudo aptitude install curl git git-core python-pip python-dev toilet
libxml2-dev libxslt1-dev libffi-dev libssl-dev
sudo aptitude upgrade
sudo aptitude dist-upgrade
sudo pip install virtualenv
sudo git clone https://github.com/scrapinghub/portia.git
sudo virtualenv portia --no-site-packages
source ~/portia/bin/activate
cd ~/portia/slyd/
sudo ln -s ~/portia/src ~/portia/slyd/
sudo chown -R portia:portia ~/portia
cd ~/portia/slyd/
~/portia/bin/pip install service_identity
cd ~/portia/
~/portia/bin/pip install -r requirements.txt
pip install -e ./slybot
—
Reply to this email directly or view it on GitHub
https://github.com/tytek2012/Portia_Installer_Script/issues/6.


text:
uSockWrite does not support "connected" UDP sockets

Hi again, we've run into another issue with ubxlib unfortunately.
We have some code that uses a UDP connection but relies on "connecting" UDP sockets, i.e. setting the default target address by calling connect() on a UDP socket once and just using plain send() and receive() calls.
This is supported by the modem (though discouraged) and also by the cellular layer of ubxlib.
But the general sock layer does not support this and filters by socket type on uCellSockWrite() and uCellSockRead() calls.
Is there a reason for this limitation?
If so, do you see a way to ease that constraint?

Hi Johannes: it might be something to do with the way the short range stuff works, let me check...

There's a comment in the sockBasicUdp() test that we used to test connection of a UDP socket but stopped doing so because SARA-R422 had a bug which prevented it.  However, even then, we didn't actually call uSockWrite() on that UDP socket in that test, so it wasn't a very good test.  The sockets code for Wifi only supports socket writes for TCP but, on the other hand, it will just return an error so if the change is as simple as removing this line in u_sock.c I can't see a problem with that.
Would making that change meet your needs?

Thanks for your quick response! Your suggested change is exactly what we did locally to get it to work 👍 It also seems to work on our R422, so not sure what bug occured with that in the past.

Your requested change has been made internally, just waiting for tests to run and review from the short-range people,  hopefully push it to public tomorrow.

Great! Thanks for your swift response as always 👍

Hopefully address by 57f7ca5c17ccc15f737f1e9b0cb1ae8dcd2363aa - let me know if not.

authors: RobMeades johannesmay

repo: u-blox/ubxlib


text:
Word2Vec に対応したい

事前学習済み Word2Vec を Embedding モデルとして実装し、他のモデルと比較できるようにしたい。
MeCab、gensim ライブラリの利用を想定。

Embedding モデルを Serialize する際に Tagger が問題になる可能性がある。Tagger だけは後から初期化でも良しとしたい。

とりあえず実装した。
以下の課題がある。
テキストを分割するのに10分かかる。学習時間は2分程度。

Word 分割時と Embedding 時に異なる形態素解析ライブラリを利用している。統一したい。

Janome、fugashi

test コードが弱い（基本的な部分しか test できていない）
パイプライン側に組み込んでいない（Embedding クラスだけしか作っていない）

repo: u-masao/sbert-news-recommender


text:
🛑 Analytics is down

In 7c80e65, Analytics (https://analytics.uvvu.pw) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Analytics is back up in b905fe8.

repo: u-v-v-u/status


text:
Add method to get all headers on the request

I would like to be able to get all the headers for a given request, with the intention of being able to add this into the uWebSockets.js repo. Commit for uWebSocket.js on fork.
I want to apologize in advance if I am doing something wrong or a bad way, I don't actually know c++.

This is not how we solve problems here. Algorithmically this is very poor. You want a simple loop.

Unless you're doing a proxy, one should never loop over all headers. You're solving a problem that isn't there

authors: alexhultman kyle-mccarthy

repo: uNetworking/uWebSockets


text:
chore: update to use Hibernate 5 and Spring JPA; fix topic w/ announc…

…ements export issue
This PR does the following:

updates Hibernate version from 3.6 to 5.6 (in prep for Spring 5 upgrade)
adds use of Spring Data JPA
fixes data export failure issue for topics that have announcements (Exporter.java)

Per PR review meeting, I have done the following:

removed unused property from pom.xml
added comment noting why some code in AnnouncementsService is commented out (for use later)
tested and verified that hibernate property overrides still works

repo: uPortal-Project/AnnouncementsPortlet


text:
fix: Obscure notifications bell when on full view

MUMMNG-2880: "As a user dismissing/un-dismissing notifications on the notification page, I would like the bell icon to update to reflect my new unread count, so that consistency is maintained."
In this PR:

Hide notification bell (and mobile menu count) when user is viewing the full notifications page

Why?
Because the notifications-bell (in its many forms) and view__notifications templates both use NotificationsController to establish and manipulate scope, you would think the scope would be shared among all the things that use that controller. However, this is not the case. The scope of the full view is isolated from the scope(s) of the various instances of the directive. This means that communication between them has to happen on the $rootScope level (barring yet another involved refactor of the notifications/announcements architecture). A truly syncopated experience without a prohibitive amount of work would depend upon $rootScope.$broadcast or manipulation of a $rootScope variable every time a notification is dismissed or restored, which means messily updating scope in up to 5 places every time. Additionally, the functionality of the full notifications view and the bell directive are nearly identical (a.k.a. redundant).
For the above reasons, it's simpler and arguably better practice to just hide the bell when users are already on the notifications page.
Screenshots

Contributor License Agreement adherence:

[x] This Contribution is under the terms of Individual Contributor License Agreements (and also Corporate Contributor License Agreements to the extent applicable) appearing in the Apereo CLA roster.

I suspect displaying and mutating the bell when the user takes an action affecting active notification count elsewhere would help the user to relate the bell to the action, would help the user understand these are different views on the same thing. So arguably that might be a better experience. But this solution seems nonetheless totally acceptable and reduces some aspects of the complexity to be maintained, so, +1.

Closing this pull request because it's a duplicate (and slightly behind its twin). See #572

authors: apetro thevoiceofzeke

repo: uPortal-Project/uportal-app-framework


text:
Show app directory search results the user can BROWSE but not SUBSCRIBE

Restores the search result count badge on the app directory results tab. That badge had been temporarily removed in #843 because it was including items the user could BROWSE-but-not-SUBSCRIBE in the count even though those search results were not displayed to the user.
This makes that badge count correct by following through on including the BROWSE-but-not-SUBSCRIBE items in the search results display. These you're-allowed-to-learn-about-this-item-but-you-cannot-actually-launch-it items are displayed at the end of the search results, after the items the user can actually launch.

(The use case here is there may be situations in which it is helpful for a user to know about, reference, show another user about an item in MyUW, even though that item isn't intended for their own use. For instance, academic advisors helping students to understand content available to students, even though the advisors themselves cannot launch all of that content.)

Contributor License Agreement adherence:

[x] This Contribution is under the terms of Individual Contributor License Agreements (and also Corporate Contributor License Agreements to the extent applicable) appearing in the Apereo CLA roster.

What are we waiting for on this PR?

We are probably waiting on teeing up local data changes so that the BROWSE permissions result in users finding content that they might value finding. I should have some local merge requests soon proposing applying the BROWSE permission grants explicitly on the individual portlet-definition entity files rather than inheriting these via categories.

authors: apetro davidmsibley

repo: uPortal-Project/uportal-home


text:
Set up a CI job testing with Caffeine

Caffeine is a current user of JSpecify mode, and also has a lot of interesting code patterns that may not be covered by our unit tests.  It would be great if we could add a CI job that runs on PRs that would check that the latest Caffeine git SHA builds successfully.  At first we could just make sure there are no crashes, though eventually it would be good to also somehow check to see that any new warnings are sensible.
@ben-manes any thoughts on this?  Right now I do this testing locally by building a NullAway snapshot, changing the NullAway version to the snapshot version in Caffeine's libs.versions.toml, and patching errorprone.caffeine.gradle.kts to pick up the snapshot with:
repositories {
  mavenCentral()
  mavenLocal()
}

We could just do this patching in our CI job to start.  But maybe there's a better way.

Cool!  Will give it a shot, thanks!

repo: uber/NullAway


text:
Add ShardID to valid attributes

What changed?
Adding ShardID as valid attribute

Why?
Related to https://github.com/uber/cadence/pull/5099
Indexing fails if you will try to use "config/dynamicconfig/development_es.yaml"

How did you test it?

Potential risks

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 0186e4af-bce5-45e7-a64d-a74a3973f0c2

0 of 0   changed or added relevant lines in 0 files are covered.
109 unchanged lines in 18 files lost coverage.
Overall coverage decreased (-0.03%) to 57.049%

Files with Coverage Reduction
New Missed Lines
%

client/history/client.go
2
38.1%

client/history/metricClient.go
2
45.3%

common/task/parallelTaskProcessor.go
2
92.75%

common/task/weightedRoundRobinTaskScheduler.go
2
88.6%

service/history/handler.go
2
47.15%

service/history/task/transfer_active_task_executor.go
2
72.15%

service/history/task/transfer_standby_task_executor.go
2
86.82%

common/persistence/nosql/nosqlplugin/cassandra/workflow.go
3
59.1%

service/matching/taskListManager.go
3
81.15%

common/persistence/serialization/parser.go
4
63.91%

Totals

Change from base Build 0186e47c-902b-4c78-9a2f-38a5b8fc9749:
-0.03%

Covered Lines:
85233

Relevant Lines:
149404

💛  - Coveralls

authors: coveralls mantas-sidlauskas

repo: uber/cadence


text:
[Coding] [Doc update]Tooltip code not found

In the page 'http://uber.github.io/deck.gl/#/documentation/deckgl-api-reference/layers/hexagon-layer', the 'setTooltip' function is not found in the code, it is undefined. Could the code definition be displayed, I searched the whole project code but not found!

I managed to create a scatterplot example with the setTooltip function. I'm not sure if it's the code definition, but it works the same the example.

I am also having this issue with the Polygon Layer. In the documentation http://deck.gl/#/documentation/deckgl-api-reference/layers/polygon-layer 'setTooltip' is not defined. I have searched far and wide for the definition of this function and have found nothing that works. Please give us a clearer definition of this function.

We do not include specific code for tooltips because it can be wildly different depending on if you are using React or not. You can find sample code in the examples folder, e.g.
React:
https://github.com/uber/deck.gl/blob/master/examples/website/geojson/app.js#L89
Pure JS:
https://github.com/uber/deck.gl/blob/master/examples/gallery/src/geojson-layer.html#L107

Strangely enough, the html version works!

If you land here hours into searching for the settooltip, make sure you try with a different class name in React/other npm package, in case tooltip is already used by another css definition. That cost me hours of frustration.

authors: MicalKarl Pessimistress ianshan0915 layik matthewjwhitney


text:
cellToBoundary sometimes returns structures with numVerts set to 7 instead of 6 ??? depending on resolution.

Sometimes cellToBoundary returns a structure with numVerts set to something higher than 6, it seems to be 7.
This is especially noticeable on higher resolutions, like 1 and 2.
These "special" cells seem to form a star across the globe and such.
Why is this ? Is this a bug ? This is causing some visualization issues for me...
I show two screenshot examples at bottom of post. Second screenshot shows what happens if my code tries to visualize the cells with 7 vertices instead of 6. (Current visualization code computes mid point on edge and draws lines from center to midpoint, the white lines, the gray lines are the cell borders, the black lines are incorrect...)
(* * @struct CellBoundary
  @brief cell boundary in latitude/longitude
*)
CellBoundary = record
	/// number of vertices
	numVerts: Integer;
	/// vertices in ccw order
	verts: array [0 .. 9] of LatLng;
end;

	cellToBoundary
	(
		H3Index(vH3Index),
		@vCellBoundary
	);

Resolution 3 example, ignoring cell boundaries with 7 vertices:

Resolution 1 example: trying to draw cells with 7 vertices with standard code, leads to troubles:

The issues seems to be much more severe, according to this thread:
https://stackoverflow.com/questions/60727617/how-many-possible-h3-geoboundary-vertex-configurations-are-there
Original Question:
"
When getting the vertices of an H3 cell using H3toGeoBoundary, how many possible vertex configurations can the GeoBoundary struct produce? I count four:
6 vertices: regular hexagon
5 vertices: regular pentagon
7 vertices: irregular hexagon (https://observablehq.com/@nrabinowitz/h3-index-inspector#85080013fffffff)
10 vertices: irregular pentagon (https://observablehq.com/@nrabinowitz/h3-index-inspector#85080003fffffff%0A%0A)

Is this list exhaustive or can other configurations exist? Would it also ever produce 0?
"
Reply to Question:
"
Your list is missing the 8 vertices case. Rather than using the generic term "irregular", it's more accurate to consider extra distortion vertices: At odd resolutions, cell edges that cross an edge of the icosahedron will have additional distortion vertices added to account for the change in projection plane (at even resolutions, the cells are aligned with the icosahedron edges and do not require this). With that explanation, the list looks like this:
5 vertices: even-resolution pentagon cell ([8408001ffffffff](https://observablehq.com/@nrabinowitz/h3-index-inspector#8408001ffffffff))
6 vertices: standard hexagon cell ([85283473fffffff](https://observablehq.com/@nrabinowitz/h3-index-inspector#85283473fffffff))
7 vertices: hexagon cell with an icosahedron edge crossing one vertex and one edge ([85080013fffffff](https://observablehq.com/@nrabinowitz/h3-index-inspector#85080013fffffff))
8 vertices: hexagon cell with an icosahedron edge crossing two edges ([850802a3fffffff](https://observablehq.com/@nrabinowitz/h3-index-inspector#850802a3fffffff))
10 vertices: odd-resolution pentagon cell ([85080003fffffff](https://observablehq.com/@nrabinowitz/h3-index-inspector#85080003fffffff))

Note that we still use "pentagon" and "hexagon" to describe these cells, because that's still topologically correct (a pentagon always has 5 neighbors, a hexagon always has 6).
"
This should have been explained in the documentation of Uber H3, so I would have know about it, before using Uber H3...
So far for me it hasn't caused major issues, but now it has... I can imagine this might drive other users crazy and believing they might have some bugs in their own code.
Anyway...
How are these special cells supposed to be visualized ?! and how are they suppose to look like ?!?
Apperently they look like normal hexagons and normal pentagons, but just have some secret extra little verteces among their edges ?!
Because that is what my black lines seem to indicate ?!
Is this really necessary, these extra verteces ?! It seems to be a very minor minor minor issue so far ?! and might be causing more trouble then it's worth it ????????????????????????????????

After implementing this color function it's starting to shine some more light on the situation, see screenshot below, showing the strange/secret/hidden verteces (sort of, the mid points are computed between them):
function MakeColorBasedOnNumberOfVerteces( ParaNumberOfVerteces : integer ) : TColorVec;
begin
case ParaNumberOfVerteces of
0 : result := MakeCellColor(   10,   10,   10 );
1 : result := MakeCellColor(   20,   20,   20 );
2 : result := MakeCellColor(   30,   30,   30 );
3 : result := MakeCellColor(   40,   40,   40 );
4 : result := MakeCellColor(   50,   50,   50 );
5 : result := MakeCellColor(   60,   60,   60 );
6 : result := MakeCellColor(   255,   255,   255 );
7 : result := MakeCellColor(   0,   0,   255 );
8 : result := MakeCellColor(   0,   0,   128 );
9 : result := MakeCellColor(   0,   255,   0 );
10 : result := MakeCellColor(   0,   128,   0 );
else
result := MakeCellColor(   255,   0,   0 );
end;
end;

Resolution 2 behaves weird:
Some cells have 8 center to center lines huh ? but they still show up white huh ?!? I am confused...

I am trying to make sense of the above picture. My program was performing a second loop, and re-draw all cells twice, but that doesn't matter much... with loop disabled and edge colors being visualized and making the edges smaller/bigger/whatever to see them individually, the result is as follows.
I don't quite understand why there appear multiple center lines, it's weird...
Again resolution 2, same zoom in...

I agree that we need more prominent documentation for this. You can see the explanation here: https://github.com/uber/h3/discussions/755#discussioncomment-5126482

authors: SkybuckFlying nrabinowitz


text:
How to use the CLI tools?

I am currently trying to develop my own live streaming XVIZ server. It would be nice to have a few examples of the CLI tool.
I think the CLI tools would be very helpful for debugging and supporting development, but I have no idea how to run them. Some documentation on how to do this and what each tool is good for would be very nice.

Thanks for filing an issue about this.  I have some notes on plan and the existing usage of the tool and I can get that as a start of the documentation for the tool itself.   I am hoping to get to it by the end of the week but here are some quick notes:
You should be able to run the tool with JS tool chain, ie. node and npm/yarn so install like so (I have just run these commands and they don't work, I am looking into it and making it work see: ):
yarn add @xviz/cli
npx xviz

xviz <command> [<args>]

The xviz tool support the following commands for exploring
and saving XVIZ data.

   dump       Output XVIZ content to stdout
  validate   Ensure data and server conform to the specification

Dump the data from the server (all of it) in condensed form:
xviz dump -c ws://localhost:8085 630e522f-d2b1-403c-a9a3-468b398cbf60

Dump EVERYTHING:
xviz dump ws://localhost:8085 630e522f-d2b1-403c-a9a3-468b398cbf60

Validate what you are producing with a summary of errors at the end:
xviz validate -c ws://localhost:8085 630e522f-d2b1-403c-a9a3-468b398cbf60

See all the validation errors (note, these are a little verbose but they point you in the direction):
xviz validate ws://localhost:8085 630e522f-d2b1-403c-a9a3-468b398cbf60

I have landed an initial set of documented in #376, you can see it in master here: https://github.com/uber/xviz/tree/master/docs/xviz-tool

authors: gerardsimons jlisee

repo: uber/xviz


text:
GUVNOR-2548: Guided Decision Table Editor: BasicFileMenuBuilderImpl: Support overriding default lock-sync behaviour

See https://issues.jboss.org/browse/GUVNOR-2548
This PR delegates the decision as to whether to enable or disable (or veto any change in state) to a helper class. The default implementation retains the current behaviour (I also have a new implementation in kie-wb-common - see linked PR - that only applies changes to MenuItem enabled state if change in lock is associated with the "active document".

Part of an ensemble:-
https://github.com/uberfire/uberfire/pull/390
https://github.com/droolsjbpm/kie-wb-common/pull/385
https://github.com/droolsjbpm/drools-wb/pull/198

+1

Just a suggestion for the test method names. It's no longer required to prefix methods names with test (as we have an annotation and run the test with junit4+). So, instead of testLockSyncMenuStateHelper_Default_LockedByCurrentUser() I'd use menuItemsEnabledWhenLockedByCurrentUser()

thanks @manstis

authors: csadilek ederign manstis

repo: uberfire/uberfire


text:
Installation of aurora-dx-nvidia-40 fails

Describe the bug
After clicking Begin Installation it runs for a while and then I get the following error message:

The following error occurred while installing the payload. This is a fatal  error and installation will be aborted.

The command 'ostree admin instutil set-kargs resume=UUID-0e17c1f0-b5c0-4ad3-93cc-65a92d62e259 rhgb quiet root=UUID=2b41ffd4-c9b4-481e-93ff-fd99787a75cd rw' exited with the code 1.

What did you expect to happen?
Expected to complete the installation.
Output of rpm-ostree status
No response
Output of groups
No response
Extra information or context
I'm trying to replace a Windows 10 installation (so not dual booting) with secure boot. I turned it off, or rather set it to Other OS as that was the only option. I couldn't even get in to the installation app without doing that.
I'm using two disks for this. Two SSDs both Samsungs but different sizes. One as "primary" with /, /boot/efi/ and swap and the other disk on /home/.
Tried to do the installation twice:
First time the primary disk with btrfs and the home disk with ext4.
Second time the primary disk with ext4 and the home disk with ext4.
Same result both times.
I built this desktop back in 2010-2012, don't remember exactly when. I'm mentioning this because I've earlier installed Bazzite on a laptop from 2018/19 without issues. So my mind went to if my desktop is too old, if that is even possible? My other concern is if there is more configuration I have to change in the BIOS? But I wouldn't even know where to start there.
Would greatly appriciate some help.

Please try again using the Bluefin Installation Runbook

I found this through @Malix-Labs link:
https://docs.fedoraproject.org/en-US/fedora-silverblue/installation/#manual-partition
And following that I was able to install it. It was probably the swap partition.

Why did you add a swap partition?
I don't actually know what I'm doing. Even though I've used Linux off and on through the years I still am a noob when it comes to these things.

Anyway, Aurora froze after a while and now I can't boot into the OS anymore, and I can't boot into the install app either. I'm getting the same error as when I tried to start the install app the first time and I had forgotten to change Secure Boot to Other OS (don't seem to be able to turn it off? Can't find an explicit option to do that, just changing it between Windows UEFI and Other OS.) Almost feels like it's bricked.
But I don't want to take up anymore of your time, I'll figure something out, so you can close this.

authors: Malix-Labs solkrans

repo: ublue-os/bluefin


text:
F41 ublue-sulogin-generator selinux

@antheas discovered an issue for F41 with our ublue-sulogin-generator
See: https://github.com/ublue-os/main/issues/634#issuecomment-2439595931

Did some research...
noticed that the SElinux contexts for several systemd-generators differ between F40 and F41.
F41 Silverblue/ublue:
bsherman@fedora:~$ ls -Z /usr/lib/systemd/system-generators/
                         system_u:object_r:nfsd_exec_t:s0 nfs-server-generator
    system_u:object_r:systemd_generic_generator_exec_t:s0 ostree-system-generator
                               system_u:object_r:lib_t:s0 podman-system-generator
    system_u:object_r:systemd_generic_generator_exec_t:s0 rpc-pipefs-generator
system_u:object_r:selinux_autorelabel_generator_exec_t:s0 selinux-autorelabel-generator.sh
 system_u:object_r:systemd_bless_boot_generator_exec_t:s0 systemd-bless-boot-generator
 system_u:object_r:systemd_cryptsetup_generator_exec_t:s0 systemd-cryptsetup-generator
      system_u:object_r:systemd_debug_generator_exec_t:s0 systemd-debug-generator
      system_u:object_r:systemd_fstab_generator_exec_t:s0 systemd-fstab-generator
      system_u:object_r:systemd_getty_generator_exec_t:s0 systemd-getty-generator
        system_u:object_r:systemd_gpt_generator_exec_t:s0 systemd-gpt-auto-generator
    system_u:object_r:systemd_generic_generator_exec_t:s0 systemd-hibernate-resume-generator
    system_u:object_r:systemd_generic_generator_exec_t:s0 systemd-integritysetup-generator
   system_u:object_r:systemd_rc_local_generator_exec_t:s0 systemd-rc-local-generator
    system_u:object_r:systemd_generic_generator_exec_t:s0 systemd-run-generator
        system_u:object_r:systemd_ssh_generator_exec_t:s0 systemd-ssh-generator
    system_u:object_r:systemd_generic_generator_exec_t:s0 systemd-system-update-generator
       system_u:object_r:systemd_sysv_generator_exec_t:s0 systemd-sysv-generator
       system_u:object_r:systemd_tpm2_generator_exec_t:s0 systemd-tpm2-generator
    system_u:object_r:systemd_generic_generator_exec_t:s0 systemd-veritysetup-generator
    **system_u:object_r:systemd_generic_generator_exec_t:s0 ublue-sulogin-generator**
       system_u:object_r:systemd_zram_generator_exec_t:s0 zram-generator

F40 Silverblue/ublue:
bsherman@fedora:~$ ls -Z /usr/lib/systemd/system-generators/
                         system_u:object_r:init_exec_t:s0 bootc-systemd-generator
                         system_u:object_r:nfsd_exec_t:s0 nfs-server-generator
                         system_u:object_r:init_exec_t:s0 ostree-system-generator
                               system_u:object_r:lib_t:s0 podman-system-generator
                         system_u:object_r:init_exec_t:s0 rpc-pipefs-generator
system_u:object_r:selinux_autorelabel_generator_exec_t:s0 selinux-autorelabel-generator.sh
 system_u:object_r:systemd_bless_boot_generator_exec_t:s0 systemd-bless-boot-generator
 system_u:object_r:systemd_cryptsetup_generator_exec_t:s0 systemd-cryptsetup-generator
      system_u:object_r:systemd_debug_generator_exec_t:s0 systemd-debug-generator
      system_u:object_r:systemd_fstab_generator_exec_t:s0 systemd-fstab-generator
      system_u:object_r:systemd_getty_generator_exec_t:s0 systemd-getty-generator
        system_u:object_r:systemd_gpt_generator_exec_t:s0 systemd-gpt-auto-generator
                         system_u:object_r:init_exec_t:s0 systemd-hibernate-resume-generator
                         system_u:object_r:init_exec_t:s0 systemd-integritysetup-generator
   system_u:object_r:systemd_rc_local_generator_exec_t:s0 systemd-rc-local-generator
                         system_u:object_r:init_exec_t:s0 systemd-run-generator
                         system_u:object_r:init_exec_t:s0 systemd-system-update-generator
       system_u:object_r:systemd_sysv_generator_exec_t:s0 systemd-sysv-generator
                         system_u:object_r:init_exec_t:s0 systemd-veritysetup-generator
                         system_u:object_r:init_exec_t:s0 ublue-sulogin-generator
       system_u:object_r:systemd_zram_generator_exec_t:s0 zram-generator

I found that this commit from May adds the new systemd_generic_generator_exec_t context, which is more restrictive than the previous default of init_exec_t: https://github.com/fedora-selinux/selinux-policy/commit/feb2379d4674d065dbcabe8b342c731954930536
And this commit from July adds some CoreOS specific policies: https://github.com/fedora-selinux/selinux-policy/commit/7aad2a628a1b68937f128b9ac30b78362ef08278
This is important because ublue-sulogin-generator started life in ublue, but I also submitted it to coreos as coreos-sulogin-generator...
So we can probably solve this issue by renaming our ublue-sulogin-generator to coreos-sulogin-generator and calling it good.

By the way, do not worry about the gnome issue. Unrelated upstream crash.

authors: antheas bsherman

repo: ublue-os/main


text:
Simplified distro.String

It makes no sense to print so much information in the String method. For reference, we used to print all of this:
name: Ubuntu
guid: '{bae22193-b9f2-4ca1-9194-f99dc5d81730}}'
configuration:
  - Version: 2
  - DefaultUID: 0
  - InteropEnabled: true
  - PathAppended: true
  - DriveMountingEnabled: true
  - undocumentedWSLVersion: 2
  - DefaultEnvironmentVariables:
    - HOSTTYPE: x86_64
    - LANG: en_US.UTF-8
    - PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
    - TERM: xterm-256color

If this was needed, yaml.Unmarshal would be the way to go.
If something goes wrong, the error was printed as well:
name: wsltesting_TestDistroString_432343647698211282_\x00_invalid_name
guid: distro is not registered
configuration: |
  could not access configuration for wsltesting_TestDistroString_432343647698211282_\x00_invalid_name: WslGetDistributionConfiguration: could not convert distro name to UTF16

This makes the mocks more complicated to implement because the error message must be the same for tests to pass.

Huh, tests failed because a distro was stuck in this state even after rebooting the machine
wsltesting_TestTerminate_8683048680539705577    Uninstalling    2

I had to manually remote into the machine and wsl --unregister ... it. Should be solved now.

repo: ubuntu/GoWSL


text:
Pods stuck in FailedCreatePodSandBox (but sometimes manage to get past this)

The problem
In the beginning things seemed to work fine, but all of a sudden pods have trouble starting properly (although it seems to work sometimes after a few minutes of trying).
What I typically see in the event log of a pod that is trying to start:
Warning  FailedCreatePodSandBox  2m23s              kubelet, tobias-dev  Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "24b9563389806c6f4ca7f261721ddbf1cf09e7376664bf861297ed8a3f34652a": netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
Warning  FailedCreatePodSandBox  2m10s              kubelet, tobias-dev  Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "50634c020f8f783989b4addc02f83378218c07967321c6f41181cb11131038ff": netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
Warning  FailedCreatePodSandBox  119s               kubelet, tobias-dev  Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "74f8fd6f55e08394c6bcae90a967fd8d826135b41788bd4f7167cea4ef907bbd": netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
Warning  FailedCreatePodSandBox  104s               kubelet, tobias-dev  Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "11ed326e72f75b9bc66308e7bdddf6a2c0eeb97bc04731bf520582e86fbcf6c7": netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
Warning  FailedCreatePodSandBox  88s                kubelet, tobias-dev  Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "faa107323fe9ad706aee5f706f1a63adb1537f95819fcb4461dcecc11599dcfb": netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
Warning  FailedCreatePodSandBox  73s                kubelet, tobias-dev  Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "7affe1b7be9ca8b2e42f52b9a6ee04dd1da7374da4f906ce06a7073373d86d2d": fork/exec /snap/microk8s/1319/opt/cni/bin/host-local: resource temporarily unavailable
Warning  FailedCreatePodSandBox  58s                kubelet, tobias-dev  Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "d07e94af48dcff9a27a4297bfd6a6ff577b18429faf159ecf988f0044a38709a": netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
Warning  FailedCreatePodSandBox  43s                kubelet, tobias-dev  Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "ecf36b73a9071ef3f5e3a4473529e59aca092708473018ad8754dfb15269fa13": netplugin failed but error parsing its diagnostic message "": unexpected end of JSON input
Warning  FailedCreatePodSandBox  10s (x2 over 28s)  kubelet, tobias-dev  (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to start sandbox container: failed to create containerd task: OCI runtime create failed: container_linux.go:345: starting container process caused "process_linux.go:269: starting init process command caused \"fork/exec /proc/self/exe: resource temporarily unavailable\"": unknown

Usually it will be stuck here, but in some cases (that I'm not able to predict), it manages to start. The chance of it eventually working seems to go down the more pods are running.
When the problem first appeared
I added postgres-operator, to the cluster. Everything worked fine so far. Then, when I used their UI to provision a new postgres cluster, the "FailedCreatePodSandbox" error first appeared.
Since then, I deleted all the postgres-operator resources - but this error now appears every time I try to start any pod. Usually the pods will be stuck at this error and retry for hours. Sometimes, all the pods stuck in FailedCreatePodSandBox will manage to start (and then this happens at the same time for these pods).
After a successful start, when I try adding a new pod of any type, it will again be stuck with the errors above.
What I've tried

Restarting microk8s: microk8s stop && microk8s start
Restarting the node itself: sudo reboot now
Delete all resource definitions and readd them

The environment
I have a single node running on Scaleway (8GB RAM, 4vCPU), with Ubuntu 20.04 as the base OS, and installed microk8s with snap install microk8s --classic --channel=1.18/stable.
From kubectl describe node | grep -A5 "Allocated":
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource           Requests         Limits
  --------           --------         ------
  cpu                1190m (29%)      7200m (180%)
  memory             1474960Ki (18%)  4352400Ki (54%)

Output from microk8s inspect: inspection-report-20200427_154029.tar.gz

I disabled linkerd, and now pods start without any problem:
microk8s disable linkerd

I'm not sure why linkerd broke my "cluster" like this - so I'd be happy to hear some opinions.
Looking at the report from microk8s inspect is what made me suspicious of linkerd in the first place:
#inspection-report/snap.microk8s.daemon-controller-manager/journal.log, line 3295

Apr 27 15:11:14 tobias-dev microk8s.daemon-controller-manager[578]: W0427 15:11:14.599282     578 garbagecollector.go:644] failed to discover some groups: map[tap.linkerd.io/v1alpha1:the server is currently unable to handle the request]

@bergkvist do you have some namespaces meshed with linkerd?

All I did was microk8s enable linkerd, and after that I didn't touch/do anything with linkerd directly.

I will need to reproduce this. Thanks for letting us know.

i could not reproduce this one.  Enabled postgres-operator like you did.  Also created a minimal Postgres cluster.
kubectl get postgresqls.acid.zalan.do  -o wide
NAME                   TEAM   VERSION   PODS   VOLUME   CPU-REQUEST   MEMORY-REQUEST   AGE   STATUS
acid-minimal-cluster   acid   12        2      1Gi                                     11m   Running

This is how my pods looks like.
kubectl get pods -A
NAMESPACE     NAME                                      READY   STATUS    RESTARTS   AGE
default       acid-minimal-cluster-0                    1/1     Running   0          11m
default       acid-minimal-cluster-1                    1/1     Running   0          10m
default       postgres-operator-54f8c768f5-bzkgc        1/1     Running   0          24m
default       postgres-operator-ui-6957759889-m2scl     1/1     Running   0          21m
ingress       nginx-ingress-microk8s-controller-45qvk   1/1     Running   0          87m
ingress       nginx-ingress-microk8s-controller-hm8sb   1/1     Running   0          87m
ingress       nginx-ingress-microk8s-controller-zbsd9   1/1     Running   0          87m
kube-system   coredns-588fd544bf-s7tbw                  1/1     Running   0          88m
kube-system   hostpath-provisioner-75fdc8fccd-2gg2w     1/1     Running   0          12m
linkerd       linkerd-controller-5fd7b68965-zr2t5       2/2     Running   0          87m
linkerd       linkerd-destination-d665bddd-545ww        2/2     Running   0          87m
linkerd       linkerd-grafana-677999f8c4-68hmk          2/2     Running   0          87m
linkerd       linkerd-identity-6c65f6567f-sb6tz         2/2     Running   0          87m
linkerd       linkerd-prometheus-6965db4598-bmf5c       2/2     Running   0          87m
linkerd       linkerd-proxy-injector-84bc4d7fd8-tfgw5   2/2     Running   0          87m
linkerd       linkerd-sp-validator-5d598d54c-4ht66      2/2     Running   0          87m
linkerd       linkerd-tap-664ff9798-cvwjw               2/2     Running   0          87m
linkerd       linkerd-web-f6db68cd-4vjrm                2/2     Running   0          87m

Did you wait for a long time before the pods started failing?
Thanks,

Yeah, my gut tells me this didn't have anything to do with postgres operator in particular.
At first it only happened to the postgres pods (because these were the ones I was restarting)
When I added postgres-operator initially, my request limits went slightly above 100%. This could have killed something that linkerd relied on - and then it somehow failed to recover automatically from that.
The interesting part is that it did work sometimes though. I imagine this could be hard to reproduce, but my logs might be able to say something about the order of things that led up to this.

Seems like this might have happened because the VPS I was running on ran out of disk space (80GB). This never struck me as a possibility at the time - since I imagined 80GB would never run out that quickly.
  77G  56G  56G      55G     37G  37G  36G        31G                                    31G
/ var/ snap/microk8s/common/ var/ lib/ containerd/io.containerd.snapshotter.v1.overlayfs/snapshots/
.   .                     .                      . 5.2G                             5.2G  5.2G
.   .                     .                      / io.containerd.content.v1.content/blobs/sha256/
.   .                     . 18G  18G        18G                            18G
.   .                     / run/ containerd/io.containerd.runtime.v1.linux/k8s.io/
.   . 21G  16G
.   / log/ syslog
.        . 4.1G
.        / journal/
. 3.2G
/ snap/
.
. 1.5G
/ root/
.
. 1.1G
/ usr/

The reason the syslog file is so huge is because it is full of k8s-errors which are likely caused by a lack of storage space. (almost making this a "bootstrap paradox")
Regarding the folders /var/snap/microk8s/common/var and /var/snap/microk8s/common/run, I'd love to better understand why they are so big. I'm guessing image storage might play a significant role in this.

Containerd images are in /var/snap/microk8s/common/var/lib/containers
If you are using the storage addon, then it will be in /var/snap/microk8s/common/default-storage
The registry addon uses the storage addon.

Actually, it seems like running out of storage space was only part of the problem. After restarting microk8s and waiting a few hours - the syslog starts being spammed with errors every 10 seconds again - and all the pods restart.
Typical logs that are printed every 10 seconds or so to syslog:
Aug  6 22:45:33 tobias-dev microk8s.daemon-containerd[4014]: time="2020-08-06T22:45:33.248110718Z" level=info msg="StopContainer for "1a3e7a9b49e78b810eda74059067bd750107f9668b186d43032f01a1c3a127b7" with timeout 30 (s)"
Aug  6 22:45:33 tobias-dev microk8s.daemon-containerd[4014]: time="2020-08-06T22:45:33.251627932Z" level=error msg="StopContainer for "1a3e7a9b49e78b810eda74059067bd750107f9668b186d43032f01a1c3a127b7" failed" error="failed to get task for container "1a3e7a9b49e78b810eda74059067bd750107f9668b186d43032f01a1c3a127b7": OCI runtime state failed: fork/exec /snap/microk8s/1550/bin/runc: resource temporarily unavailable: : unknown"
Aug  6 22:45:33 tobias-dev microk8s.daemon-kubelet[4026]: E0806 22:45:33.252810    4026 remote_runtime.go:243] StopContainer "1a3e7a9b49e78b810eda74059067bd750107f9668b186d43032f01a1c3a127b7" from runtime service failed: rpc error: code = Unknown desc = failed to get task for container "1a3e7a9b49e78b810eda74059067bd750107f9668b186d43032f01a1c3a127b7": OCI runtime state failed: fork/exec /snap/microk8s/1550/bin/runc: resource temporarily unavailable: : unknown
Aug  6 22:45:33 tobias-dev microk8s.daemon-kubelet[4026]: E0806 22:45:33.252920    4026 kuberuntime_container.go:652] Container "containerd://1a3e7a9b49e78b810eda74059067bd750107f9668b186d43032f01a1c3a127b7" termination failed with gracePeriod 30: rpc error: code = Unknown desc = failed to get task for container "1a3e7a9b49e78b810eda74059067bd750107f9668b186d43032f01a1c3a127b7": OCI runtime state failed: fork/exec /snap/microk8s/1550/bin/runc: resource temporarily unavailable: : unknown
Aug  6 22:45:33 tobias-dev microk8s.daemon-kubelet[4026]: E0806 22:45:33.252991    4026 kuberuntime_manager.go:689] killContainer "dashboard-metrics-scraper"(id={"containerd" "1a3e7a9b49e78b810eda74059067bd750107f9668b186d43032f01a1c3a127b7"}) for pod "dashboard-metrics-scraper-db65b9c6f-sv9gb_kube-system(df019a05-891f-41cc-a2c8-5e57035210c5)" failed: rpc error: code = Unknown desc = failed to get task for container "1a3e7a9b49e78b810eda74059067bd750107f9668b186d43032f01a1c3a127b7": OCI runtime state failed: fork/exec /snap/microk8s/1550/bin/runc: resource temporarily unavailable: : unknown
Aug  6 22:45:33 tobias-dev microk8s.daemon-kubelet[4026]: E0806 22:45:33.253054    4026 pod_workers.go:191] Error syncing pod df019a05-891f-41cc-a2c8-5e57035210c5 ("dashboard-metrics-scraper-db65b9c6f-sv9gb_kube-system(df019a05-891f-41cc-a2c8-5e57035210c5)"), skipping: failed to "KillContainer" for "dashboard-metrics-scraper" with KillContainerError: "rpc error: code = Unknown desc = failed to get task for container \"1a3e7a9b49e78b810eda74059067bd750107f9668b186d43032f01a1c3a127b7\": OCI runtime state failed: fork/exec /snap/microk8s/1550/bin/runc: resource temporarily unavailable: : unknown"
Aug  6 22:45:34 tobias-dev microk8s.daemon-containerd[4014]: time="2020-08-06T22:45:34.254781365Z" level=info msg="StopContainer for "65dc0c16e983532b1b1f47731eedfbae38e3d934f29dc3a2f4941f776ad6e9be" with timeout 30 (s)"
Aug  6 22:45:34 tobias-dev microk8s.daemon-containerd[4014]: time="2020-08-06T22:45:34.257093323Z" level=error msg="StopContainer for "65dc0c16e983532b1b1f47731eedfbae38e3d934f29dc3a2f4941f776ad6e9be" failed" error="failed to get task for container "65dc0c16e983532b1b1f47731eedfbae38e3d934f29dc3a2f4941f776ad6e9be": OCI runtime state failed: fork/exec /snap/microk8s/1550/bin/runc: resource temporarily unavailable: : unknown"
Aug  6 22:45:34 tobias-dev microk8s.daemon-kubelet[4026]: E0806 22:45:34.259592    4026 remote_runtime.go:243] StopContainer "65dc0c16e983532b1b1f47731eedfbae38e3d934f29dc3a2f4941f776ad6e9be" from runtime service failed: rpc error: code = Unknown desc = failed to get task for container "65dc0c16e983532b1b1f47731eedfbae38e3d934f29dc3a2f4941f776ad6e9be": OCI runtime state failed: fork/exec /snap/microk8s/1550/bin/runc: resource temporarily unavailable: : unknown
Aug  6 22:45:34 tobias-dev microk8s.daemon-kubelet[4026]: E0806 22:45:34.259878    4026 kuberuntime_container.go:652] Container "containerd://65dc0c16e983532b1b1f47731eedfbae38e3d934f29dc3a2f4941f776ad6e9be" termination failed with gracePeriod 30: rpc error: code = Unknown desc = failed to get task for container "65dc0c16e983532b1b1f47731eedfbae38e3d934f29dc3a2f4941f776ad6e9be": OCI runtime state failed: fork/exec /snap/microk8s/1550/bin/runc: resource temporarily unavailable: : unknown
Aug  6 22:45:34 tobias-dev microk8s.daemon-kubelet[4026]: E0806 22:45:34.259967    4026 kuberuntime_manager.go:689] killContainer "coredns"(id={"containerd" "65dc0c16e983532b1b1f47731eedfbae38e3d934f29dc3a2f4941f776ad6e9be"}) for pod "coredns-588fd544bf-fpvsj_kube-system(2d84145a-4538-4629-881c-d6acd42c22b1)" failed: rpc error: code = Unknown desc = failed to get task for container "65dc0c16e983532b1b1f47731eedfbae38e3d934f29dc3a2f4941f776ad6e9be": OCI runtime state failed: fork/exec /snap/microk8s/1550/bin/runc: resource temporarily unavailable: : unknown
Aug  6 22:45:34 tobias-dev microk8s.daemon-kubelet[4026]: E0806 22:45:34.260062    4026 pod_workers.go:191] Error syncing pod 2d84145a-4538-4629-881c-d6acd42c22b1 ("coredns-588fd544bf-fpvsj_kube-system(2d84145a-4538-4629-881c-d6acd42c22b1)"), skipping: failed to "KillContainer" for "coredns" with KillContainerError: "rpc error: code = Unknown desc = failed to get task for container \"65dc0c16e983532b1b1f47731eedfbae38e3d934f29dc3a2f4941f776ad6e9be\": OCI runtime state failed: fork/exec /snap/microk8s/1550/bin/runc: resource temporarily unavailable: : unknown"

Thanks for looking into this one.  Will it still be possible to grab the inspect tarball again?
Also prior to that, what do you have running in there?

Tarball:
inspection-report-20200806_230915.tar.gz
All the pods that are running:
(Notice that coredns says 0/1 Running)
kubectl get pods -A
NAMESPACE      NAME                                              READY   STATUS    RESTARTS   AGE
cert-manager   cert-manager-74d6c4d49b-kg486                     1/1     Running   10         43d
cert-manager   cert-manager-cainjector-77bc84779-cdmqm           1/1     Running   12         43d
cert-manager   cert-manager-webhook-5b5485577f-r7jvp             1/1     Running   10         43d
default        acid-pg11-0                                       1/1     Running   1          20h
default        acid-tobias-0                                     1/1     Running   1          20h
default        blog-0                                            1/1     Running   2          20h
default        jupyter-0                                         1/1     Running   1          20h
default        nginx-7c85b9b6c8-j69jf                            1/1     Running   1          20h
default        ntust2019-6949c6648f-2phq9                        1/1     Running   1          20h
default        postgres-operator-64cdb54f94-j6zzq                1/1     Running   1          20h
default        postgres-operator-ui-58bdbf7748-jdzlf             1/1     Running   1          20h
default        wellapi-0                                         1/1     Running   1          20h
default        wellclient-6d8d9b6df4-v84zf                       1/1     Running   1          20h
ingress        nginx-ingress-microk8s-controller-4gvnz           1/1     Running   299        103d
kube-system    coredns-588fd544bf-fpvsj                          0/1     Running   36         103d
kube-system    dashboard-metrics-scraper-db65b9c6f-sv9gb         1/1     Running   40         101d
kube-system    elasticsearch-logging-0                           1/1     Running   58         103d
kube-system    fluentd-es-v2.2.0-zm4vj                           1/1     Running   218        103d
kube-system    heapster-v1.5.2-58fdbb6f4d-rdf8k                  4/4     Running   164        101d
kube-system    hostpath-provisioner-75fdc8fccd-v2bwb             1/1     Running   221        101d
kube-system    kibana-logging-84f486f46b-9p97b                   1/1     Running   38         103d
kube-system    kubernetes-dashboard-67765b55f5-s6krb             1/1     Running   208        101d
kube-system    metrics-server-f7cdcc99-gdl4c                     1/1     Running   1          20h
kube-system    monitoring-influxdb-grafana-v4-6dc675bf8c-khmcz   2/2     Running   71         101d
kube-system    tiller-deploy-d47d5858d-zhwtk                     1/1     Running   13         90d

kubectl describe pod coredns-588fd544bf-fpvsj -nkube-system
Name:                 coredns-588fd544bf-fpvsj
Namespace:            kube-system
Priority:             2000000000
Priority Class Name:  system-cluster-critical
Node:                 tobias-dev/10.18.86.149
Start Time:           Sat, 25 Apr 2020 17:34:53 +0000
Labels:               k8s-app=kube-dns
                      pod-template-hash=588fd544bf
Annotations:          scheduler.alpha.kubernetes.io/critical-pod:
Status:               Running
IP:                   10.1.6.26
IPs:
  IP:           10.1.6.26
Controlled By:  ReplicaSet/coredns-588fd544bf
Containers:
  coredns:
    Container ID:  containerd://65dc0c16e983532b1b1f47731eedfbae38e3d934f29dc3a2f4941f776ad6e9be
    Image:         coredns/coredns:1.6.6
    Image ID:      docker.io/coredns/coredns@sha256:41bee6992c2ed0f4628fcef75751048927bcd6b1cee89c79f6acb63ca5474d5a
    Ports:         53/UDP, 53/TCP, 9153/TCP
    Host Ports:    0/UDP, 0/TCP, 0/TCP
    Args:
      -conf
      /etc/coredns/Corefile
    State:          Running
      Started:      Thu, 06 Aug 2020 06:05:15 +0000
    Last State:     Terminated
      Reason:       Unknown
      Exit Code:    255
      Started:      Thu, 06 Aug 2020 02:26:57 +0000
      Finished:     Thu, 06 Aug 2020 06:04:29 +0000
    Ready:          False
    Restart Count:  36
    Limits:
      memory:  170Mi
    Requests:
      cpu:        100m
      memory:     70Mi
    Liveness:     http-get http://:8080/health delay=60s timeout=5s period=10s #success=1 #failure=5
    Readiness:    http-get http://:8181/ready delay=0s timeout=1s period=10s #success=1 #failure=3
    Environment:  <none>
    Mounts:
      /etc/coredns from config-volume (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from coredns-token-n8z6r (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  config-volume:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      coredns
    Optional:  false
  coredns-token-n8z6r:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  coredns-token-n8z6r
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  <none>
Tolerations:     CriticalAddonsOnly
                 node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason     Age                    From                 Message
  ----     ------     ----                   ----                 -------
  Warning  Unhealthy  4m31s (x3481 over 9h)  kubelet, tobias-dev  Readiness probe failed: Get http://10.1.6.26:8181/ready: dial tcp 10.1.6.26:8181: connect: connection refused

I can see that coredns isnt healthy.  I will start first by disabling elasticsearch, fluentd.  As elasticsearch seems to be pretty resource intensive.  Well just to see if the system gets to stable state.

Okay - I tried disabling elasticsearch/fluentd now using microk8s disable fluentd. I guess I will see in the next few days if it remains stable.
How much memory does the fluentd/elasticsearch addon usually consume?

The elasticsearch resource usage depends on how much logs we are putting into it.  If your pod logs are verbose then it can be resource heavy.
We recently updated metrics server.
The update removed some components which are not required or made obsolete by the metrics server.

@bergkvist do you also mind disabling the metrics-server? Thanks.

After running microk8s disable fluentd, none of my pods have restarted during the last 11 hours. I think you were right about elasticsearch causing the problems here/being resource heavy.

I didn't realize metrics-server was part of microk8s addons, so I had originally added it with the command below (which didn't seem to work anyways):
kubectl apply -f https://github.com/kubernetes-sigs/metrics-server/releases/download/v0.3.7/components.yaml

I disabled it using
kubectl delete -f https://github.com/kubernetes-sigs/metrics-server/releases/download/v0.3.7/components.yaml

@bergkvist good to hear that it seems to make the cluster stable.  I believe that the more logs fluentd forwards to ES, the more resources it needs to index them.
And as you said, some pods can be affected.  You can try grafana loki if your need is simply to search for logs and dont do any analytics on it. It cuts storage needs by a lot.

Seems like the cluster has gone unstable again:
kubectl get pods -A
NAMESPACE      NAME                                              READY   STATUS                 RESTARTS   AGE
cert-manager   cert-manager-74d6c4d49b-zrw7j                     1/1     Running                1          17d
cert-manager   cert-manager-cainjector-77bc84779-w268r           1/1     Running                1          17d
cert-manager   cert-manager-webhook-5b5485577f-rt8dm             0/1     Error                  1          17d
default        acid-pg11-0                                       1/1     Running                1          17d
default        acid-tobias-0                                     0/1     CreateContainerError   1          17d
default        blog-0                                            1/1     Running                1          17d
default        jupyter-0                                         0/1     CreateContainerError   1          17d
default        nginx-7c85b9b6c8-vhx95                            1/1     Running                1          17d
default        ntust2019-6949c6648f-9zjgj                        0/1     Error                  1          17d
default        postgres-operator-64cdb54f94-dhgc4                1/1     Running                1          17d
default        postgres-operator-ui-58bdbf7748-jwmfc             1/1     Running                1          17d
default        wellapi-0                                         0/1     CreateContainerError   1          17d
default        wellclient-6d8d9b6df4-grh42                       1/1     Running                1          17d
ingress        nginx-ingress-microk8s-controller-fwpfg           1/1     Running                1          17d
kube-system    coredns-588fd544bf-7q4fm                          0/1     Error                  1          17d
kube-system    dashboard-metrics-scraper-db65b9c6f-m4s86         1/1     Running                1          17d
kube-system    heapster-v1.5.2-58fdbb6f4d-v6zgc                  3/4     CreateContainerError   4          17d
kube-system    hostpath-provisioner-75fdc8fccd-48v7c             1/1     Running                1          17d
kube-system    kubernetes-dashboard-67765b55f5-vtfvg             1/1     Running                1          17d
kube-system    monitoring-influxdb-grafana-v4-6dc675bf8c-khzqb   1/2     CreateContainerError   2          17d
kube-system    tiller-deploy-d47d5858d-rk6g4                     0/1     Error                  1          17d

kubectl describe pod coredns-588fd544bf-7q4fm -nkube-system
...
Events:
  Type    Reason          Age                    From                 Message
  ----    ------          ----                   ----                 -------
  Normal  SandboxChanged  91s (x77970 over 16d)  kubelet, tobias-dev  Pod sandbox changed, it will be killed and re-created.

@bergkvist would it be posible to upload the microk8s inspect tarball?

@ktsakalozos Here you go:
inspection-report-20200824_231322.tar.gz

@bergkvist the tarball you attached was one you got yesterday, right? I see there that k8s (containerd) had problems creating containers (forking). Often this is due to some resource shortage. I see the amount of free memory your system had was rather low, that could be a reason. there was a lot of memory used in buffers but I could not pinpoint which process was causing this. How does your free -m look like now?

The tarball is from yesterday, yes. Running free -m right now gives me:
free -m
              total        used        free      shared  buff/cache   available
Mem:           7968        1902         231          37        5833        6018
Swap:             0           0           0

My understanding is that the "available" column is the relevant one - and that the linux operating system will always try to keep the "free" memory as low as possible. See https://askubuntu.com/questions/867068/what-is-available-memory-while-using-free-command

authors: balchua bergkvist ktsakalozos


text:
Signing the CLA and the new cla-check

I have already contributed and also signed the CLA using the same email.
I noticed after a recent update to a PR #2052 that the new cla-check github action, is failing for my build.
After some checking i installed the  cla-check snap and i could verify that Canonical believe that this email has signed the CLA.

So am i missing a step regarding how i create my pr so that the action can verify the contributing email against the CLA?
Or does the documentation need updating?

Hmm, that does look like something is going wrong with the action and we should check into it

authors: evilnick tbertenshaw


text:
Implement only reading the first frame for Python library

Implement "first frame" reading for the Python version.

Implemented in v1.3.0

repo: ucalgary-aurora/themis-imager-readfile


text:
Nvidia driver,cuda, cudnn,tensorflow-gpu DockerFile  Image for Model Container

I am trying  to install nvidia driver cuda cudnn and related dependcy for running models in gpu mode.
First of all , I built a custom image with the following code
`FROM clipper/python36-closure-container:0.3
RUN mkdir -p /python-deps
RUN apt-get update
RUN apt-get install -y libgtk2.0-dev
RUN pip install pillow
RUN pip install opencv-python
RUN pip install --default-timeout=100000 tensorflow-gpu
RUN pip install cython
RUN pip install --default-timeout=100000 scipy
RUN pip install --default-timeout=100000 sklearn
ENV PYTHONPATH=$PYTHONPATH:/python-deps/`
and I built a model container with the image and link it to the clipper-admin by the following code
clipper_conn.register_application(name="opencv2", input_type="bytes", default_output="-1.0", slo_micros=300000000) python_deployer.deploy_python_closure(clipper_conn, name="detectface", version=2,num_replicas=2, input_type="bytes", func=detectface,base_image='face_image:latest') clipper_conn.link_model_to_app(app_name="opencv2", model_name="detectface")
After doing these stuff ,I am trying to import tensorflow from terminal  in docker
import tensorflow as tf
but it says the error
ImportError: libcublas.so.9.0: cannot open shared object file: No such file or directory
To resolve this i am tring to install Nvidia driver,cuda, cudnn,tensorflow-gpu from the following
https://gist.github.com/ashokpant/5c4e9481615f54af4025ab2085f85869
https://gist.github.com/niderhoff/52c514f20337516500084dd7b17af7e2
But i can't install nvidia-driver, cuda , nvidia-container-runtime properly.
I am searching for Dockerfile that includes all dependency to build a docker container that supports gpu computing and i don't want to install any dependency after  logging to the docker manually.
Is there is any docker image available that supports GPU?

@robi56 :
How about refer to this site?

Hi @robi56! Clipper will soon include native CUDA 10 support for PyTorch and TF! Here is a PR adding pytorch support with docker! This can also serve as a handy guide if you want to write your own Dockerfile.

This PR addresses this issue #669

authors: RehanSD robi56 withsmilo

repo: ucbrise/clipper


text:
[CLIPPER-212] Add CLOCK cache eviction policy

Fixes #212

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/607/
Test FAILed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/608/
Test PASSed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/609/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/610/
Test FAILed.

@dcrankshaw This is now ready for review.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/611/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/612/
Test PASSed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/613/
Test FAILed.

jenkins test this please

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/614/
Test FAILed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/615/
Test PASSed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/620/
Test FAILed.

@dcrankshaw Addressed your review comments. Regarding applications with low cache hit rates, the user can avoid eviction overhead by setting the cache size to zero, effectively disabling caching.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/621/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/622/
Test FAILed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/623/
Test PASSed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/646/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/647/
Test FAILed.

jenkins test this please

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/648/
Test PASSed.

authors: AmplabJenkins Corey-Zumar


text:
Another example for preventing errors heuristic?

@timbellnz we just found a rather nice example of the "prevent errors" heuristic being violated. Want to include an image of this in the guide?

The error was because I had typed digits that were not 1's and 0's -- something I should not have been allowed to do. It's cool because it has a good computer sciency theme to it. It happened because a few days ago I was using the calculator program to do something in binary, and then today when I opened it, it was still in that mode but I didn't notice. Not only is it an example of "prevent errors", it is also an example of a useless error messages :-)

I've added the calculator, and also got carried away and added an ATM example.
commit number 1d8c17fa637c2956497bd3f5d2b937b2671270be

authors: Heidirose timbellnz

repo: uccser/cs-field-guide


text:
(game management) research if there is existing functionality for making search bars (admin page has resources help???) (ryan, patrick)

For this task, we will research existing functionality for making search bars in Django in order to determine how we will go about implementing the search bar.

The website GeeksForGeeks has a good example  of a search bar that autocompletes using jQuery UI (a jQuery library, see documentation here) This could be useful for implementing autocompletion in the search bar

From many examples such as this tutorial, the basic idea of search bar can be broken down into the following components:

Create a separate search results view, template, and url
Add a form with a text input field to the template that sends a GET request to the view
In views.py, get the query from the GET request and override the default get_queryset() method provided by ListView

In summary, a basic search bar can be implemented using the HTML form tag (including the action and method attributes) and created a new view for the search results based on the query.

In summary, a basic search bar can be implemented using the HTML form tag (including the action and method attributes) and created a new view for the search results based on the query. There are many tutorials such as this one about creating a basic search bar and search results page. We can add autocomplete functionality after we complete a basic search bar using the jQuery UI autocomplete widget (see documentation). Preliminary research into functionality for making a search bar is done, so this issue is complete.
Distribution of work:
Ryan: research
Patrick: research and documentation

Issue Score: Excellent
Comments:
Great job providing frequent smaller updates as y'all went through the task!
For future reference, please update the title of any issue you work on to not be the title assigned in team meeting.
This is because the task titles are informal and meant to capture enough such that you can look at them and remember what we talked about.
They are usually not formatted nicely (including extra parentheticals or questions).
Overall, y'all are doing good work, keep going!

authors: fkbad ptlin25 rakrusch

repo: uchicago-cs/chigame


text:
Nuxeo content_harvest issues for #27124 - various error messages

Registry ID: 27124
Mapper: Nuxeo
Run ID: manual__2024-10-08T05:57:09+00:00
Link to Airflow: https://7a8067cb-3b99-477e-a883-7e311175a9b4.c3.us-west-2.airflow.amazonaws.com/dags/harvest_collection/grid?dag_run_id=manual__2024-10-08T05%3A57%3A09%2B00%3A00&num_runs=365
convert: cache resources exhausted

[ ] mapped task 2:

ERROR: make_jp2 command failed: ['/usr/bin/convert', '-quiet', '-format', '-jp2', '-define', 'jp2:rate=10', '/tmp/sim_137_001_0001.jpg[0]', '/tmp/sim_137_001_0001.jp2']
returncode was: 1
output was:
convert: cache resources exhausted `/tmp/sim_137_001_0001.jpg' @ error/cache.c/OpenPixelCache/4095.
convert: no images defined `/tmp/sim_137_001_0001.jp2' @ error/convert.c/ConvertImageCommand/3229.

Nuxeo: https://nuxeo.cdlib.org/nuxeo/nxdoc/default/8b0931c4-d523-4960-9980-2c5b2845feca/view_documents

Calisphere-stage: https://calisphere-stage.cdlib.org/item/ark:/86086/n25m679x/

[ ] mapped task 3:

ERROR: make_jp2 command failed: ['/usr/bin/convert', '-quiet', '-format', '-jp2', '-define', 'jp2:rate=10', '/tmp/sim_145_000_116_0776.jpg[0]', '/tmp/sim_145_000_116_0776.jp2']
returncode was: 1
output was:
convert: cache resources exhausted `/tmp/sim_145_000_116_0776.jpg' @ error/cache.c/OpenPixelCache/4095.
convert: no images defined `/tmp/sim_145_000_116_0776.jp2' @ error/convert.c/ConvertImageCommand/3229.

Nuxeo: https://nuxeo.cdlib.org/nuxeo/nxdoc/default/8206df43-c038-49c6-a892-fe65c7ae0c41/view_documents
Calisphere-stage: https://calisphere-stage.cdlib.org/item/ark:/86086/n29025fd/

convert: width or height exceeds limit

[ ] mapped task 4:

ERROR: make_jp2 command failed: ['/usr/bin/convert', '-quiet', '-format', '-jp2', '-define', 'jp2:rate=10', '/tmp/sim_156_000_114_1247.jpg[0]', '/tmp/sim_156_000_114_1247.jp2']
returncode was: 1
output was:
convert: width or height exceeds limit `/tmp/sim_156_000_114_1247.jpg' @ error/cache.c/OpenPixelCache/3909.
convert: no images defined `/tmp/sim_156_000_114_1247.jp2' @ error/convert.c/ConvertImageCommand/3229.

Nuxeo: https://nuxeo.cdlib.org/nuxeo/nxdoc/default/6a55236e-9a18-48db-a590-ce3a0c9d0992/view_documents
Calisphere-stage: https://calisphere-stage.cdlib.org/item/ark:/86086/n2xp76qs/

make_jp2 command failed

[ ] mapped task 21: - failed on retry, same file

--------------------------------
ERROR: make_jp2 command failed: ['/usr/bin/convert', '-quiet', '-format', '-jp2', '-define', 'jp2:rate=10', '/tmp/sim_057_000_001_0037.tif[0]', '/tmp/sim_057_000_001_0037.jp2']
returncode was: -6
output was:
--------------------------------; 13632)

Nuxeo: https://nuxeo.cdlib.org/nuxeo/nxdoc/default/98110137-29b5-4c7e-ba81-c71c3124c444/view_documents

Calisphere-stage: https://calisphere-stage.cdlib.org/item/ark:/86086/n2fj2j1b/?order=36
(child record)

[ ] mapped task 28:

--------------------------------
ERROR: make_jp2 command failed: ['/usr/bin/convert', '-quiet', '-format', '-jp2', '-define', 'jp2:rate=10', '/tmp/sim_063_009_001_0027.tif[0]', '/tmp/sim_063_009_001_0027.jp2']
returncode was: -6
output was:
--------------------------------; 210)

https://nuxeo.cdlib.org/nuxeo/nxdoc/default/fa825f58-34cc-4f80-be5e-c897afb33923/view_documents
Calisphere-stage: https://calisphere-stage.cdlib.org/item/ark:/86086/n2wh2r8n/?order=26
(child record)
convert: Failed to seek in the stream.

[ ] mapped task 32: - failed on retry, same file

ERROR: make_jp2 command failed: ['/usr/bin/convert', '-quiet', '-format', '-jp2', '-define', 'jp2:rate=10', '/tmp/sim_055_008_001_0182.tif[0]', '/tmp/sim_055_008_001_0182.jp2']
returncode was: 1
output was:
convert: Failed to seek in the stream.
 `OpenJP2' @ error/jp2.c/JP2ErrorHandler/194.
convert: unable to encode image file `/tmp/sim_055_008_001_0182.jp2' @ error/jp2.c/WriteJP2Image/1141.
convert: unable to write file `/tmp/sim_055_008_001_0182.jp2' @ error/constitute.c/WriteImage/1346.

Nuxeo: https://nuxeo.cdlib.org/nuxeo/nxdoc/default/c2a880f5-9e77-4062-a854-e546ba10fac1/view_documents

Calisphere-stage: https://calisphere-stage.cdlib.org/item/ark:/86086/n2hq4151/?order=181
(child record)

[ ] mapped task 38:

ERROR: make_jp2 command failed: ['/usr/bin/convert', '-quiet', '-format', '-jp2', '-define', 'jp2:rate=10', '/tmp/sim_025_000_002_0094.tif[0]', '/tmp/sim_025_000_002_0094.jp2']
returncode was: 1
output was:
convert: Failed to seek in the stream.
 `OpenJP2' @ error/jp2.c/JP2ErrorHandler/194.
convert: unable to encode image file `/tmp/sim_025_000_002_0094.jp2' @ error/jp2.c/WriteJP2Image/1141.
convert: unable to write file `/tmp/sim_025_000_002_0094.jp2' @ error/constitute.c/WriteImage/1346.

Nuxeo: https://nuxeo.cdlib.org/nuxeo/nxdoc/default/bf1ee640-7b8d-418f-bfba-fd04f9142194/view_documents

Calisphere-stage: https://calisphere-stage.cdlib.org/item/ark:/86086/n2pg1t7f/?order=93
(child record)

[ ] mapped task 44:

ERROR: make_jp2 command failed: ['/usr/bin/convert', '-quiet', '-format', '-jp2', '-define', 'jp2:rate=10', '/tmp/sim_180_000_001_0049.tif[0]', '/tmp/sim_180_000_001_0049.jp2']
returncode was: 1
output was:
convert: Failed to seek in the stream.
 `OpenJP2' @ error/jp2.c/JP2ErrorHandler/194.
convert: unable to encode image file `/tmp/sim_180_000_001_0049.jp2' @ error/jp2.c/WriteJP2Image/1141.
convert: unable to write file `/tmp/sim_180_000_001_0049.jp2' @ error/constitute.c/WriteImage/1346.

Nuxeo: https://nuxeo.cdlib.org/nuxeo/nxdoc/default/87c80fac-effb-44f5-95d4-75b88a518a2f/view_documents
Calisphere-stage: https://calisphere-stage.cdlib.org/item/ark:/86086/n2cc12h3/?order=48
(child record)

OSError: [Errno 28] No space left on device

[ ] mapped task 1: OSError: [Errno 28] No space left on device - failed on retry, made it to the same file
[ ] mapped task 8: OSError: [Errno 28] No space left on device
[ ] mapped task 29: OSError: [Errno 28] No space left on device
[ ] mapped task 39: OSError: [Errno 28] No space left on device
[ ] mapped task 40: OSError: [Errno 28] No space left on device
[ ] mapped task 41: OSError: [Errno 28] No space left on device
[ ] mapped task 42: OSError: [Errno 28] No space left on device
[ ] mapped task 43: OSError: [Errno 28] No space left on device
[ ] mapped task 45: OSError: [Errno 28] No space left on device
[ ] mapped task 46: OSError: [Errno 28] No space left on device
[ ] mapped task 47: OSError: [Errno 28] No space left on device
[ ] mapped task 49: OSError: [Errno 28] No space left on device

The make_jp2 errors should be resolved with this PR: https://github.com/ucldc/rikolti/pull/1137
The No space left on device errors should be resolved with this PR: https://github.com/ucldc/rikolti/pull/1135

This collection harvests through without harvest-stopping errors! There are several outstanding issues with the Nuxeo image content files themselves; see new issue: https://github.com/orgs/ucldc/projects/2?pane=issue&itemId=84240640

authors: barbarahui christinklez

repo: ucldc/rikolti


text:
Handle multibranch

With ucoin 0.12 coming, the multibranch feature will change a bit the way we handle network data :
On the network side :

We need to check for current block of every node
A node should be considered "synced" if it's last known block is the majority of all "last blocks" known in the network

On the requests and data handling side :

We should return data encapsulated like in the cache, in a dict :

with a field "data" containing the request response
with a field "metadata" containing the block of the requested node

The client should display data validity. A parameter should be available, saying "Blocks to validate data : K". The number K is how many blocks we wait after a data was written in the blockchain to consider the data validated.
I was thinking of a field with 3 states :

"Not-validated" (data not found on the blockchain, for signatures, transactions, posted but not validated yet)
"Being validated (XX%)" (data found in a block, but we are waiting for K blocks to be mined after this data. Typically, XX = (current_block - data_block)/K )
"Validated" : Enough blocks were mined
This field could be displayed as a table cell, a popup...

Finally, transactions parsing will change a bit since we now transactions wont be validated as soon as a node returns it.

We are almost there. What we need to do now :

Implement blockchain rollback detection

When a new block is detected, check :

If the block number is lower than the previous one -> rollback
If the block number is higher than the previous one :

Check the block under the request Block/[number of previous current block]
If the hash is different than the previous one -> rollback

Implement the new transactions life cycle :

As the states of the transactions are becoming even more complex, we should refactor the code.
A table state machine could be of great help :
http://python-3-patterns-idioms-test.readthedocs.org/en/latest/StateMachine.html#table-driven-state-machine

repo: ucoin-io/cutecoin


text:
Change name of GISTIC datasets

Right now they say “GISTIC - Copy Number Score”. Please change to “GISTIC - focal score by gene”
This will help people see that the copy number data it is displaying is only for focal amplifications and deletions. Not arm-level events like what we see for PTEN

Addressed and merged in #77

authors: maryjgoldman yunhailuo

repo: ucscXena/xena-GDC-ETL


text:
翻译问题 + Markdown样式问题【20.视频：百分位数】

5. 技能方向 - 数据分析与SQL（二选一）> [选修]SQL窗口功能 > 20.视频：百分位数

具体描述

bucket应该翻译为“分桶”而不是“水桶”
红框位置Markdown样式损坏

感谢反馈~

repo: udacity/band-issues-cn


text:
Adding media through the Media Library listing page doesn't work (wp-admin/upload.php)

The user of the plugin, received the message from the website form:
Adding media through the Media Library listing page doesn't work (wp-admin/upload.php). When I try to upload a new image, I don't think wp-stateless intercepts it because I get this error:

Unable to create directory wp-content/uploads/2021/04. Is its parent directory writable by the server?

It only works in wp-admin/media-new.php.

Wondering if you guys have any fix around this or an updated version?

I observe something similar, when I use (wp-admin/upload.php) it saves the image in the local file directory wp-content/uploads/, but with wp-admin/media-new.php, the file is uploaded to gcloud storage as expected
I am running on a kubernetes cluster, so the file system uploads to wp-content/uploads/ will be removed when the container changes, it would be nice to have a feature with disable saving to local storage, so that users don't loose data

I'm unable to add media via the featured image select (request made to /wp-admin/async-upload.php), but fine using wp-admin/media-new.php. Here's the error:
Unable to create directory wp-content/uploads/2021/04. Is its parent directory writable by the server?
This is with stateless enabled.

Having the same issue.  Uploading through custom meta fields works fine but in the media library or featured image I get the same error messages as folks above

I have the same issue on Google Cloud Run. Works on the /wp-admin/media-new.php page though.

I has same problem, then I found that it's because GCS bucket uniform access, #521

The fix was released in version 3.3
Closing the ticket.

I had the problem "Unable to create directory...". I found that the problem was with my docker image when I realised it worked with a "default" wordpress image.
The problem I had was that this option was "Off" in the php.ini settings. This must be on.
allow_url_fopen
I hope this helps someone

authors: BGroever acollinsbl bethios engvie liapotanin planv vigiland vsychov

repo: udx/wp-stateless