Quantitative type theory

Quantify judgements in the type theory according to a usage semiring.
Working from Quantitative Type Theory by Robert Atkey.

This is incomplete (it does the setup to annotate the context but doesn’t actually perform any such annotations), but I don’t currently understand linear logic well enough to complete it. I’m going to merge now and then revisit this later.


[WIP] Migrate main window to flexible layout and mvvm

What did you fix? (provide a description or issue closes statement)
This refactors the MainWindow to be easier to understand, maintain and test by adopting an MVVM architecture.
Not quite done yet, putting this up to help with #198
Contains new dependencies:

Microsoft.Toolkit.Mvvm: A best in class set of MVVM classes (to replace the built-in INPC and provide a messenger)
Microsoft.Xaml.Behaviors: A really useful set of XAML helpers that let you bind commands to old WPF controls that don't have commands

Considerations

Does this contain a new dependency? [Yes]
Have I run the linter? [Yes]
Is is a bug fix, feature request, or enhancement? [Enhancement]

Is there something I can do to assist with this?

Is there something I can do to assist with this?

Resolution of conflict wouldn't hurt :)

I can make an attempt, but it's unclear if the work was completed since it is in draft state + the comment in the opening which may be resolvable but may not compile due to diff decay.
I ran into a harder time trying to do that for #209

@PeterJeff I can't remember how far I got, but looking at the changes I made to the view I imagine I did most of what I intended to. The best way to test would be to just checkout the PR and see if the UI still works properly.
The big problem you'll run into is that I completely rewrote the view into a much easier to maintain form that is completely incompatible with any changes made to the UI since I started this. It might be easier to merge or recreate any UI changes in main since this last synced in this PR, as it should make the UI easier to manage.


Initial websocket request can fail

I've not been able to pinpoint the reason, but it seems like the initial attempt to connect to a VNCserver via websockets when visiting /desktop can sometimes fail. I suspect its a race condition that may make it never happen in some contexts, and often in others.
In #101 there is now a test that often but not always in our CI system on the first attempt, but not the second.
Debugging

I've not reproduced this by visiting /desktop on my laptop for tiger or turbo, but I think it does from my desktop computer
Reproduced using dockerspawner, as seen on the fourth attempt in this GIF:

Ideas on why

viewer.js client sends a websocket handshake before websockify is ready to listen
websockify receives a websocket handshake before vncserver is ready to listen
jupyter-server-proxy's issue https://github.com/jupyterhub/jupyter-server-proxy/issues/459 behavior of accepting the client/proxy websocket handshake before the proxy/server handshake.

I've seen this show up more consistently when the ping is notable (by testing against a hub deployed in USA from Sweden). Three out of three tests made this happen on first attempt to visit /desktop, while doing things locally I just observed it one out of four for example.

@consideRatio I ran into this issue while working on https://github.com/NASA-IMPACT/veda-jupyterhub/issues/2. I have opened a PR with a proposed workaround in #112. Please let me know if that looks reasonable.


Expected prop to be data fetched by Relay

Hi, after i upgraded to isomorphic-relay v0.5.1 All my components started to complain asking that the data has to be data fetched by relay.
Warning: RelayContainer: Expected prop mesupplied toNavbar to be data fetched by Relay. This is likely an error unless you are purposely passing in mock data that conforms to the shape of this component's fragment.

Any idea about this? After hours of debugging still i couldn't find the reason

I am seeing the same on my project after an upgrade, I did not want to say anything because I thought I just messed up something. So ... +1 I guess?

Any ideas on how I can reproduce it? How your setup different from the examples (star-wars, todo)? I suppose you have tried to remove the node_modules and make clean install, right?

Let me try to see how I can make it easiest to reproduce for you, I will follow up with you. Clean install after deleting node_modules did not help in my case.

Definitely does not happen with the todo example from isomprohic-relay-router. I will keep digging to find why and where it happens.

As an experiment I tried to modify the todo sample to use exactly the same packages as my project, and it did not cause it to break ... will continue looking.

Here is where my warning comes from:

At this point I do not think it is necessarily related to isomorphic-relay, could be something to do with relay 0.7. I will post more when I find out more.

@thelordoftheboards, Does the warning show if you comment out the call to IsomorphicRelay.injectPreparedData?

I will test that tomorrow. However, if I initially call a page that is not using, for instance, ToDos, and then in the browser navigate to ToDos I see the warnings in the browser console. I would think by that time we would be done with the server rendering.
That said, I will try it anyway.

@denvned thanks for your promptness and support, I will do trials this evening and try to find out more
@thelordoftheboards thanks to you as well to move forward with debugging

I tried to remove IsomorphicRelay.injectPreparedData but it doesn't seem the problem. I also tried to downgrade to v.0.50 with no luck.
I can say that my project is more similar to the Isomorphic-relay-router repo, I'm exporting queries as a playing object and pass them to the routes from the routes prop.

Haven't had any time for more detailed troubleshooting, but I noticed that at the same time as this project converted to 7 they added ; after the class definition and before the relay wrapper. I am not sure of the meaning of this ...
https://github.com/ryancole/league/commit/af0c63e2f334aec79cc08b2ece72c466e62d373a
Does it matter?

Does it matter?

No, it shouldn't.

Just FYI, I'm having the exact same problems, after upgrading to 0.7.0. The warning also appears on the server side, so .injectPreparedData cannot be the cause of the problem.

@jkempff, sorry you faced it too. Maybe you have any ideas how I can reproduce the error?
@fenos, @thelordoftheboards, @jkempff Maybe any of you can create a small repro project and upload it to GitHub?

@denvned fair enough, i'll do it this evening when i came back from work if no one would do it before me.
Thanks again

@denvned I tried to reproduce the issue outside of my main project using the ToDo example at no avail. I will prepare my 'full' project with the problem. The size should not be an issue hopefully, the problem is fairly isolated.

@denvned here is my repository: https://github.com/codefoundries/isomorphic-material-relay-starter-kit/tree/develop
Here are the steps to reproduce the problem:

Clone the develop branch locally.
Run:

npm run install
npm run config-local
npm run dev

Navigate to http://localhost:4444/.
Click on top left button in nav bar.
Choose Examples, then Ensayo.
The following message will appear in the console 4 times (for each item):

Warning: RelayContainer: Expected prop `Ensayo` supplied to `Ensayo_Item` to be data fetched by Relay. This is likely an error unless you are purposely passing in mock data that conforms to the shape of this component's fragment.

I could not make it any simpler than that, my attempts to reproduce it outside of the project so far have been in vain. The same project works perfectly well in 6.1 (master branch).

@thelordoftheboards You forgot to update babel-relay-plugin-loader to version 0.7. With the correct version your repo does not produce the warnings.
As it turned out, it was a user error, so closing for now.
@fenos, @jkempff What version of babel-relay-plugin are you using?

I am sooo dumb. Sorry to waste your time.

Just for everyone else's reference, I will be using npm-check-updates from now on to make sure I am not missing anything. Seems to work fairly well.

I feel dumb as well :( Thanks denvned to point that thing out, I tried as well to replicate the issue with no luck but that was the cause!! Thanks so much to both of you guys

Same here, after updating all dependencies - which was kind of a hassle - everything works as expected!


Correct name of load_balancer databag

chef-provisioning-aws stores ELB data in the load_balancer databag.

%w(images load_balancer)
Why is images plural and load_balancer singular? That seems inconsistent.

images may be image, I didn't look into that one. load_balancer is definitely load_balancer.

@eheydrick: I'm not doubting your fix, just pointing out the inconsistency in naming. Ideally this inconsistency should be fixed, but that may be complicated because of existing setups.


Create a known issues doc for Flux

Create a doc to house known issues for Flux.

The autoInterval template variable for Flux queries in Chronograf is currently too aggressive and can quickly consume system resources.


add kstreamplify article from Michelin

Add kstreamplify article from michelin blog.
Kstreamplify is our open source librairie based on kafka streams.

:) you are welcome


rAVen - Modern Audio Visualizer for UNIX based systems

rAVen
An all-in-one GUI audio visualizer for UNIX based systems that allows to visualize audio in real-time as well as for any type of audio file with cool visualizations
Why
We all know cava exists for this and it works really well however, it does not use the full power of Fast Fourier Transforms (FFT) to enhance on audio visualization.
Aesthetically so far, people have used cava but with rAVen and its current implementation so far, I can see it beating cava in terms of looks easily if we get the implementation of real-time audio sample gather using audio clients like pipewire, portaudio so on..
The idea does not have great ambitions I do agree.
But that's a plus point if you ask me as this does not seem too out of bounds and unfeasible, which is perfect for taking up a project like this

[!NOTE]
Would like to add that this started out and will likely remain a > simple passion project of mine as I did not
find any great AVs out there that suited for my needs so I tried to make one.

How
rAVen's implementation of the two modes should ideally look like the following:

Real-Time Audio Capture Mode:

a. Capturing Real-Time Audio:

This mode would require us to become clients with audio servers like:

1. Pipewire
2. Portaudio
3. Alsa
4. Jack
5. Pulse

These 5 must be majorly supported as that would significantly increase the compatability across all Linux based distributions

There exists documentation (Doxygen mostly) for each audio server with in depth detail that explains how to capture real-time audio samples and utilize them

b. Performing FFT:

Getting the audio samples is probably the hardest part.

Everything after that has either already been implemented or just need to tweak a few things to get it to work with RTAC

c. Displaying the visualization:

This is done using raylib library in C which makes it look pretty cool and dynamic with a lot of freedom of GUI dev

File Audio Capture Mode:

This part has already been implemented in rAVen which is up for reference.

Challenges Faced

A strict and rigid based system to decide which audio server to become a client of to get the audio samples

Possibly adding a config file that allows users to set a lot of parameters regarding the FFT visualizations, audio server to choose so on

Avoiding getting garbage audio samples from servers in case of other AVs running

(I noticed this issue while testing pipewire audio samples capture when cava was running in the background: TLDR -> I was getting garbage samples which did not make sense and am still not sure on how to fix it)
Good to have features

Powerful user configuration capabilities

Proper implementation of client-server connection with an audio server

Possible enhancements to the raylib UI which is currently implemented

Better and more accurate audio visualization using mathematical concepts like low/highpass filtering, so on

contributed by nots1dd

Seems like a really cool idea.


cgroup: move proccesses from root group to new /init group

Proposed Changes
If there are processes running in the root cgroup on a cgroupv2 enabled system, move them to a new /init group and enable subtree_control.
For further info, see the discussion and links in the previous PR: https://github.com/k3s-io/k3s/pull/3237
Types of Changes
Fix for cgroupv2 support.
Verification
Run on a cgroupv2 enabled system
Linked Issues

rancher/k3d#493
https://github.com/k3s-io/k3s/pull/3237
https://github.com/moby/moby/commit/ed89041433a031cafc0a0f19cfe573c31688d377

Further Comments
This is my first time touching cgroups in Go code and reading/writing that part of the k3s code, so there may be some things that could be done different.
The way it's written now, it should only have an effect if there are processes running under the root cgroup.

Can we have CI for cgroup2? (https://github.com/k3s-io/k3s/pull/2887) :pray:

Can we have CI for cgroup2? (#2887) 🙏
(this is in)

Lets see how the tests look, but you need signoff on your commits.

Could you rebase with https://github.com/k3s-io/k3s/pull/3282 to test the change with rootless?

This looks good, but needs a rebase in order to get the CI checks to run.

Rebased onto https://github.com/AkihiroSuda/k3s/tree/rootless-ci

need rebase code base

@xiaods done :heavy_check_mark:
Rebasing this was an absolute mess, so I effectively dropped my changes during the rebase and re-applied them on top afterwards.
This PR definitely needs to be squashed and merged, as it now contains pretty useless/dumb commits.

Closing as Out of Date and has been superseded by other PRs.


Validate request.form arguments from HTML post form

Hi,
not sure whether there is an option to validate request.form arguments right now, with this package but it would be a nice-to-have feature :)
For example, to use like this:
@validate(form=SomeModel)
Right now, I am validating request.form simply like this:
    try:
        form = LoginFormModel(**request.form)
    except ValidationError as ve:
        return {"validation_error": ve.errors()}, 400

Or is there any other way around?
Any advice would be much appreciated!

Hello,
this would indeed be a nice feature. This package does not support forms yet. I will try to find time to implement it. Feel free to submit PR.
Thank you for suggestion!


Operator Softsign is not supported by the standard TensorFlow Lite runtime

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:a GNU/Linux system with Linux kernel 4.15.0 on 1 6-core 3.60GHz Intel Core CPU i7-6850K with 64 GB RAM equipped with a NVIDIA Corporation GP102 GPUs
TensorFlow installed from (source or binary): source
TensorFlow version (use command below):tensorflow2-GPU
Python version:3.6

Describe the current behavior
When I converted the trained hdf5 model to tflite, the following operator non-support occurred ：Softsign
Describe the expected behavior
The hdf5 model should be successfully converted to the format of tflite.
Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.
batch_size = 80
epochs = 171
num_classes = 10
import os
save_dir = 'model'
model_name = 'model.h5'
import keras as keras
(x_train, y_train), (x_test, y_test) = keras.datasets.fashion_mnist.load_data()
img_rows, img_cols = x_train.shape[1], x_train.shape[2]

x_train = x_train.reshape(x_train.shape[0], img_rows, img_cols, 1)
x_test = x_test.reshape(x_test.shape[0], img_rows, img_cols, 1)
input_shape = (img_rows, img_cols, 1)
x_train = x_train.astype('float32')
x_test = x_test.astype('float32')
x_train /= 255
x_test /= 255
y_train = keras.utils.to_categorical(y_train, num_classes)
y_test = keras.utils.to_categorical(y_test, num_classes)

import keras as keras
model = keras.models.Sequential()
model.add(keras.layers.ThresholdedReLU(theta=0.3514439122821289))
model.add(keras.layers.LeakyReLU(alpha=0.4855740853866919))
model.add(keras.layers.AveragePooling2D(pool_size = (1, 2), padding='same'))

model.add(keras.layers.Flatten())
model.add(keras.layers.Dense(num_classes, activation='softsign'))
model.compile(loss=keras.losses.categorical_crossentropy,optimizer=keras.optimizers.Adadelta(), metrics=['accuracy'])
model.fit(x_train, y_train, batch_size=batch_size, epochs=epochs, verbose=1, validation_data=(x_test, y_test))

model_path = os.path.join(save_dir, model_name)
model.save(model_path)

Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.
Exception: We are continually in the process of adding support to TensorFlow Lite for more ops. It would be helpful if you could inform us of how this conversion went by opening a github issue at https://github.com/tensorflow/tensorflow/issues/new?template=40-tflite-op-request.md
 and pasting the following:

Some of the operators in the model are not supported by the standard TensorFlow Lite runtime. If those are native TensorFlow operators, you might be able to use the extended runtime by passing --enable_select_tf_ops, or by setting target_ops=TFLITE_BUILTINS,SELECT_TF_OPS when calling tf.lite.TFLiteConverter(). Otherwise, if you have a custom implementation for them you can disable this error with --allow_custom_ops, or by setting allow_custom_ops=True when calling tf.lite.TFLiteConverter(). Here is a list of builtin operators you are using: AVERAGE_POOL_2D, CAST, FULLY_CONNECTED, GREATER, MAXIMUM, MUL. Here is a list of operators for which you will need custom implementations: Softsign.

Please consider enabling Softsign operator with TF select option. https://www.tensorflow.org/lite/guide/ops_select

Please consider enabling Softsign operator with TF select option. https://www.tensorflow.org/lite/guide/ops_select

@bugreporter450
I ran the code on colab and do not face any errors, could you please refer to above comment [by abattery] and let us know.

@bugreporter450
I ran the code on colab and do not face any errors, could you please refer to above comment [by abattery] and let us know.

Hi all,
We have the same problem converting our model to tensorflow lite during quantisation stage. Is Softplus being supported now? if not, what would be the solution to convert models with Softplus ops?
Thanks


Add code examples for Try

Add code examples for Try methods.
This change is requested in #2496

Codecov Report

Merging #2504 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #2504   +/-   ##
=========================================
  Coverage     95.07%   95.07%
  Complexity     5402     5402
=========================================
  Files            89       89
  Lines         12821    12821
  Branches       1598     1598
=========================================
  Hits          12189    12189
  Misses          454      454
  Partials        178      178

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/io/vavr/control/Try.java
98.36% <ø> (ø)
103 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6facb84...deea00c. Read the comment docs.

Many thanks and sorry for the delay...


test: fix in memory issue

:white_check_mark: Build TheIdServer 4.0.2-PAT1-0019 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/0bc73c92d9 by @)

:white_check_mark: Build TheIdServer 4.0.2-PAT1-0020 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/469048f57a by @)


Unable to add items to existing Scroll

I had a use case where I wanted to use the scroll for a text log.  As the app is running new text would be added to the log and as such the totalCount would increase.
You can't call Generate a second time so you can't update the totalCount.
In the VerticalUnlimitedScroller, RowCount doesn't have a setter and totalCount is only initialized from Generate.
Is there a way to grow the number of items in a scroll over time as I want to?  Otherwise what would a solution be?  I start at 1 log entry but expect to grow to tens of thousands over the course of the app's lifecycle.

I've done a horrible hack to get the functionality as I want:
        public void ResizeScroller(int newSize)         {             ClearCache();             DestroyAllCells();             totalCount = newSize;             InitParams();             GenerateAllCells();         }
Then the caller:
`            unlimitedScroller.Generate(textPrefab, _logManager.Count, (index, iCell) =>
{
var logEntryUIController = iCell as LogEntryUIController;
if (logEntryUIController)
logEntryUIController.Text = _logManager.TextAt(index);
});
        unlimitedScroller.ResizeScroller(_logManager.Count);
        unlimitedScroller.JumpTo((uint)_logManager.Count - 1, JumpToMethod.OnScreen);`

New log entries are added at the bottom, and then the log scrolls till they're visible.  The vertical scrollbar resizes correctly as new entries are added.  However, obviously it's a horrible hack, but it'll do for prototyping.

Unfortunately, adding and removing cells are not supported yet. But I do have plan to add them soon since I found they are common use cases.

Unfortunately, adding and removing cells are not supported yet. But I do have plan to add them soon since I found they are common use cases.

What happened to this?
Adding new items into the scroll list is something I need.. at least with some good performance.
@doug-w did that end up working a lot better than using the default ugui scrollbar?

I kept with my workaround above since it hasn't caused issues, I'm still using it and for a few thousand entries haven't seen any issues yet.

I found adding and removing items dynamically more difficult than I thought because it affects all cells behind it, and I didn't have time to implement it last year. But I think accepting that workaround can do for now.


Error needs more information

In GitLab by @youldrouis on Feb 18, 2022, 15:02
[18:20:18][000128][PDI] *** error: Type_error: Referencing null data with non-null size

This error needs more information, like data name, context

mentioned in commit 8470da1d17f1749bb18d3a82d83706aaa769ef96

In GitLab by @youldrouis on Feb 23, 2022, 23:27
Thank you, this logging totally answers the problem :
[18:47:15][000128][PDI] *** error: Value_error: Unable to share `TrapFrac_modif' due to Type_error: Referencing null data with non-null size

mentioned in commit 4b26683d93f77933e6b503133e457d231296a2f7

mentioned in commit fe640183c6a76a1cec15f19d0f913990259fa2c8

can you make a run with the exception handling code commented in PDI so as to get a backtrace so that we know where to add the info

mentioned in commit 8c225d4def706b778a3542e989fba83e89af3c70

mentioned in commit 933eda1b44aca12d1ef0b308e76e1d594b82c869

mentioned in commit e33b67b1d248a9dbe5c579b7ba3228ee4367626b

mentioned in commit f3fc6b7459c75f96009d57952da04de9c9193438

In GitLab by @youldrouis on Feb 23, 2022, 23:30
MR !421 solves the issue :
[18:47:15][000128][PDI] *** error: Value_error: Unable to share `TrapFrac_modif' due to Type_error: Referencing null data with non-null size

Thanks @jbigot


Document a possible workaround for Fedora 33

Ref: #1572

@cfergeau did you look into the issue? Do we still need to document this?

Praveen has been testing this change:
# cat /etc/systemd/resolved.conf.d/crc.conf
[Resolve]
DNS=<IP_ADDRESS>
Domains=~. testing
# resolvectl dns
Global: <IP_ADDRESS>
Link 2 (eth0): <IP_ADDRESS> <IP_ADDRESS>
# resolvectl domain
Global: ~. testing

with the hope that it would be generic enough to work both on f33 and ubuntu. This could also be handled by following https://fedoramagazine.org/systemd-resolved-introduction-to-split-dns/ , but Praveen was worried this would not work on Ubuntu which uses systemd-networkd. https://manpages.ubuntu.com/manpages/cosmic/man1/resolvectl.1.html documents that when systemd-networkd is in use, per-interface nameservers must be set in the network interface file, while when it's not in use, it's done in a different place.
I did not test any of this myself.

Do we report this currently as a known issue? An automated solution for this doesnt exist yet

@gbraad This isn't recorded as a known issue at this time. We can add it to the known issues asynchronously, however.

Praveen has been testing this change:
# cat /etc/systemd/resolved.conf.d/crc.conf
[Resolve]
DNS=<IP_ADDRESS>
Domains=~. testing
# resolvectl dns
Global: <IP_ADDRESS>
Link 2 (eth0): <IP_ADDRESS> <IP_ADDRESS>
# resolvectl domain
Global: ~. testing

with the hope that it would be generic enough to work both on f33 and ubuntu. This could also be handled by following https://fedoramagazine.org/systemd-resolved-introduction-to-split-dns/ , but Praveen was worried this would not work on Ubuntu which uses systemd-networkd. https://manpages.ubuntu.com/manpages/cosmic/man1/resolvectl.1.html documents that when systemd-networkd is in use, per-interface nameservers must be set in the network interface file, while when it's not in use, it's done in a different place.
I did not test any of this myself.

One note about ubuntu: ubuntu desktop uses a setup which seems similar to f33 (systemd-resolved + NetworkManager, no systemd-networkd), while ubuntu server uses systemd-resolved+systemd-networkd without NetworkManager.

I have a workaround for this:

First make libvirtd.service a dependency of systemd-resolved.service.  CRC has it's own network, and that needs to be up and running for systemd-resolved.service to pick up.
sudo vi /etc/systemd/system/dbus-org.freedesktop.resolve1.service

and change
After=systemd-sysusers.service systemd-networkd.service

to
After=systemd-sysusers.service systemd-networkd.service libvirtd.service

Save and exit the text editor.

Next, open the systemd-resolved.service configuration file, resolved.conf, for editing to add the CRC DNS and Domains:
sudo vi /etc/systemd/resolved.conf

and add
DNS=<IP_ADDRESS>%crc#apps-crc.testing <IP_ADDRESS>%crc#crc.testing
Domains=~apps-crc.testing ~crc.testing

Save and exit the text editor.

Restart the systemd-resolved service:
sudo systemctl restart systemd-resolved.service

Your system should now properly pick up the CRC network even if you reboot your machine.  Been using it for a few days now without issue.

I've been having success with https://github.com/code-ready/crc/issues/1572#issuecomment-723026134:

I'm currently having success with adding

$ cat 10-crc
#!/bin/sh
This is a NetworkManager dispatcher script to configure split DNS for
the 'crc' libvirt network.
The corresponding bridge is recreated each time the system reboots, so
it cannot be configured permanently through NetworkManager.
Changing DNS settings through nmcli requires the connection to go down/up,
so we directly do the change through resolvectl
export LC_ALL=C
if [ "$1" = crc ] && [ "$2" = up ]; then
resolvectl domain crc ~testing
resolvectl dns crc <IP_ADDRESS>
resolvectl default-route crc false
fi
exit 0
in /etc/NetworkManager/dispatcher.d/10-crc and making the file executable. This will need a destroy/start of the libvirt crc network, or a reboot of the host as this is only triggered when the crc NM interface state changes to up

Mr. Fergeau, that's a fabulous solution, although I changed it slightly:
if [ "$1" = crc ] && [ "$2" = up ]; then
    echo "checking in dispather.d $1"
    resolvectl domain crc crc.testing apps-crc.testing
    resolvectl dns crc <IP_ADDRESS>
    resolvectl default-route crc false
fi

I added the echo statements so I could verify in the system logs, and as you can see I referenced the domains for fully.  I couldn't get it to work with ~testing for some reason, so I started screwing around.  Lots of reboots seem to have it working for me now, although I am noticing that every once in a while the VM isn't coming very quickly (or at least isn't reachable quickly), and so it might have been my impatience that made me think ~testing didn't work?  Dunno.
Thanks much for what looks to be a better solution than the one we came up with.  Appreciate it.

This is now documented as a known issue based on this comment: https://github.com/code-ready/crc/issues/1572#issuecomment-728911700
@gbraad For the future, do you think we should document this in the troubleshooting section of the docs? Primarily asking because "known issues" at this time are entirely downstream, whereas the troubleshooting docs exist in this repository. If this workaround will be applicable for a while, it would make sense for us to have these docs available via GitHub Pages as well. Let me know what you think. :)

@crc-team we need somehow automated or manual tests setup for Ubuntu.

This has been  fixed by #1732


Feature request: Set dynamic tags through request headers

We would like to be able to inject dynamically tags based on the request headers, i.e. be able to configure the plugin to select pre-defined request headers and inject them as tags inside spans.
Does this sound to you as a neat feature?

NOTE It will probably look like the following PR: feat(handler) static tags #84

This is definitively a nice feature to have. We have in some of the zipkin tracers.

Implemented in #102


Installing lite-server error Can't find python executable

I am unable to install lite-server.  I get an error that node-gyp can't find the python executable.  The only solution I find online is to install python and C++ and Windows SDK and build it from scratch.  Am I missing something?

I too am having that error appear during the install

probably a problem with installing other node modules too, right? we need more info to know what the issue is

Nope.  lite-server is the only module I have ever had this problem with.  I switched to http-server to avoid the problem,

If you have more info, we can look into it.

When I get a chance I will re run it and upload the error output

I don't think this is an issue specifically w/ Lite Server, but is related to an issue that an issue that node-gyp has on Windows - apparently it is one of Browser-sync's dependencies.
See this (long) thread for a solution - you may have to install the C++ build tools and Python 2.7 as I did.

seems that is the case. closing


[deconz] Update repository/tag and config mountPath

Description of the change
The deconz image repository has changed from marthoc/deconz to deconzcommunity/deconz and also requires to mount the config to /opt/deCONZ.
Also updated to the lastest stable version "Crossfade 2.12.06" from the Phoscon changelog (https://phoscon.de/en/changelog/).
Benefits
No new images are pushed to the old repository, making the update more or less mandatory.
Possible drawbacks
People that manually set the config mountPath (persistence.config.mountPath) should make sure this is changed too.
Checklist

[X] Chart version bumped in Chart.yaml according to semver.
[X] Title of the PR starts with chart name (e.g. [home-assistant])
[X] Variables are documented in the README.md

Sorry for the missed changes. Was my first time committing to this project and missed the part about helm-docs. Resolved this and hopefully it's as requested!

@all-contributors Please add @TheDJVG for code


Type check window instead of document to detect environment

I think it's generally accepted that to check whether an environment is node or browser, we should type check window, instead of document, because sometimes document is mocked for testing purpose.

I'd rather use process.browser, see https://github.com/mochajs/mocha/blob/master/lib/utils.js#L690
If you'd like to open a PR for this, please do!

process.browser please. I tend to stub window when unit testing my browserified code on the server.

Yeah, process.browser is the way to go. https://github.com/mochajs/mocha/pull/1727 changed a bunch of these env checks to use process.browser, but I pretty much did the bare minimum to get it working so I'm sure there are more.

I'd like to contribute here :)
Was the mentioned TODO the only place to look at? (I doubt it)

@anmuel Thanks.  You could grep around for window or document and see if there's anything else that needs addressing, but that's about all I know of right now.


Logging Subsystem Enhancements

[x] Modify namespace (SYS_LOG -> LOG)
[ ] Support multiple backends

[ ] FCB
[x] memory
[ ] filesystem
[x] networking
[ ] mcumgr(!)

[x] Add timestamps
[x] Provide meta-data (such as log level) separately to the backend (right now it's embedded into the pre-formatted string)
[ ] multi-core support: master - slave configuration where one core acts as slave and the master collects logging from the slave and displays the logs of the system as a whole

@ccollins476ad FYI, for 1.12

CC @pizi-nordic

As part of this cleanup can we look at supporting an API that allows the user to do something like:
LOG(level, log_format, ...)
and have features like COLOR work consistently.

I would like to present a logger design which I think might be suitable for the Zephyr. I will post my proposal in parts, starting from the high-level overview. It will be later followed by some notes about the implementation and advanced features like multi-core support and Trust Zone integration.
Introduction
The complexity of modern embedded systems enforces changes in our working methodology. Challenges we face every day include:

Large amount of data.
The continuously increasing speed of peripherals is a dominating factor that influences rate of debugging data generation, while complexity of the protocols, peripherals and firmware determines size of generated data as more information is needed to describe state of the monitored component and the system. The amount of data generated during testing and debug sessions negatively impact on the data analysis time. As result, we can observe creation of dedicated tools, which are verifying system behaviour basing on the received data, extract required information from data stream or convert the information into a form which is easier to analyse by human.

Existence of multiple separated domains in the system.
This includes multi core and multi CPU systems as well as new technologies like Trust Zone. Usually in such case firmware for each domain is being developed separately, however system behaviour and performance depends on successful cooperation of all components. As result the tools we need must be able to present system-level view of the firmware internals in order to easily trace interaction between domains. The detail view is also needed as complex systems are built from large number of components. Developer must be able to focus on currently developed or tested module and silence all noise coming from other parts of the system.

These challenges faced every day by a developer, tester or system integrator could be addressed by dedicated logger subsystem, presented in this document.
Requirements
The core requirements of the logger are defined by its usability:

Performance.
The performance is the key parameter of the logger subsystem. As the logger acts as observer of the system internals it has to have minimal impact on the observed entities. Minimizing time needed to log data is especially important in real-time subsystems, which just fails if deadlines are not met. The log processing and transmission speed is also important, as there could be a lot of log data which have to be gathered in order trace down complex problem.

Context-free operation and lock-less log gathering.
The  data logging function must neither take any logs now wait for any other kind of resources. Moreover, it should be prepared to be interrupted any time by higher priority code, which could also use the same function for message logging.

Support for multiple log levels and component/instance separation.
Depending on the situation, the system-level or detailed view in needed. The good logger to support different log levels for different components on the system in order to minimize amount of information not relevant to the currently performed task. This is especially important for modules which are re used in multiple places of the system. For example, the pool-based memory allocator must have different log level setting for each pool, as enabling full debug component-wise might generate overwhelming amount of information.

Ease of use.
The logger usability is also defined by the amount and quality of the presented information. The easier it will be to use, the more likely developer will put it in the newly created code and the more information will be available. Moreover, access to the data and integration with both internal (for example memory management subsystem or building infrastructure) and external infrastructure (like custom testing frameworks) should be as simple and straightforward as possible.  The human factor cannot be underestimated while thinking about logger usage - simple features like colours might be used to catch attention to the most important messages significantly reducing time need for log analysis.

Operation Principles
Logger Frontend
The Log Fronted collects logs form the system. From the developer perspective the it mimics printf() interface. Dedicated macro (one for each log level) accepts format string and optional arguments:
LOG_ERROR("This is error");
LOG_WARNING("This is warning with %u argument", 1)
LOG_INFO("This is info message with %u %s", 2, "arguments");
LOG_DEBUG("This is debug message");

The most important difference between the printf()-based solutions and the proposed logger is the processing of data. The macros presented above does not do any processing. Instead they just store the pointer to the format string and optional arguments in the dedicated buffer. As result the cost of message logging is equal to few memory writes. The stored data in converted to to the human-readable string later, in the idle loop of the system in order to avoid negative impact of increased CPU load on the system operation. The proposed behaviour has one limitation, which must be taken under consideration by every developer using the logger: as processing is performed in the idle loop, some time after macro execution, thus all pointers provided to the log system have to be valid all the time.
In addition to the data provided by developer, the macros automatically add some meta data, like timestamps, identifier of module generating logs as well as log level. All the information is stored into a buffer (the circular buffer is an obvious choice, however it has some drawbacks which are discussed later) where waits for the further processing.
Logger Core
The Logger Core is responsible for management of log processing. As the log processing must have minimal impact on the system, the Logger Core is called directly from the idle thread and can be pre-empted any time. Moreover, to minimize latency in systems when no preemption is used, it processes single log message on each call, allowing system to check if there is a more important task to handle as often as possible. On each call, single log entry is fetched from the buffer in which it was stored by the fronted and is passed to connected backends.
Logger Backend
The backed is responsible for log messages presentation, transmission or storage. Usually, at the first stage of processing, backend converts the data received from logger core into a human-readable from: the printf()-like expression is evaluated and converted to string, which is prepended by metadata and terminated by end of line string. Additional presentation tasks, like for example applying colors to warning and error messages, are also performed at this stage. Then, the generated strings are sent to the host:
[00:01:24.548072] <error> example_module: This is error
[00:01:24.548073] <warning> example_module: This is warning with 1 argument
[00:01:24.548074] <info> example_module: This is message with 2 arguments
[00:01:24.548075] <debug> example_module: This is debug message

The backend could also perform any other action on the received logs. This include like storing them in flash or forwarding them to host without rendering.
Basic Features
Log Filtering
The log filtering is done separately for  each backend basing on log level and source of the message (module/instance id). Such approach allows for debugging one backend using another one as well as forwarding selected messages (like errors and warnings) to dedicated backend (for example a flash-based storage).
The log filtering is done in 2 places in order to minimize amount of CPU time needed to collect and process logs. The coarse check is done in the Logger Frontend: the LOG_* macros does not perform any action if there is no backend waiting for a messages of given level from given module. If the message pass this check, the Logger Core do the final filtering by routing the message only to backends requesting the such messages.
Object Dumping
The delayed processing of the log messages might be a problem when a developer would like to log some strings (in general: any data) which is only available au the time of LOG_* macro execution. To address this problem, an object dumping interface is provided. The developer might use dedicated macro (LOG_HEXDUMP()) to insert blob of data into log buffer. Such blob is then presented to the user as a hexdump of stored data. Unfortunately this feature has an significant cost, as the log buffer must be large enough to hold whole dumped object.
Similar mechanism might be used as a compatibility layer in order to provide equivalent of the existing printk() interface.

Would you consider trying to shorten the API names a bit? E.g. LOG_WARN, LOG_INFO, LOG_ERR and LOG_DBG? Part of the parameter list is often a fairly long string, and having to split it up something to be avoided.

@jhedberg: Good idea!

@skordal: Of course the *printf() interface could be provided, but in my opinion we should allow that only during a transition period, as there are essential differences between logger and the behaviour expected from *printf() calls.
The proposed logger is lossy: If there is no time to process logs, they will be dropped in order to maintain system operation. Such loss is not expected in printf(). Moreover direct usage of printf() is more costly, as you are loosing benefit of the delayed log processing.

That's fine, what I mean is, it could be useful to have the possibility to pass a va_list to the logging functions, to make it possible to forward logging messages from other libraries/frameworks (such as libmetal) which implement their own logging frameworks.
The problem here is that I want to forward logging messages from a function, defined as metal_log_handler(enum metal_log_level level, const char *format, ...). If I want to use Zepyr's logging macros I would have to preformat the logging messages in metal_log_handler() (by calling vsprintf() or something similar) before calling LOG_ERROR(), since I cannot forward the argument list from the logging function to Zephyr's logging API for formatting.
If possible, it would be nice to have some additional logging macros which allows us to call the Zephyr logging API in such situations, to remove the overhead of having to format the log messages in the framework before passing the strings on to the Zephyr logging API.

@skordal: I see your problem now. The vsprintf() is a simple, but ineffective solution. What is needed to interface such function to the proposed logging subsystem is a code which extract arguments from the va_list basing on format string and pass them to the logger. Such code might be available through dedicated macros like VLOG_VINFO(), VLOG_ERR() and so on. The only drawback of such approach be a reduced performance of the VLOG_* macros, as format string has to be scanned at the logging time.

As principles of the logger seems to be accepted by everyone, it is time to discuss some implementation details:
Implementation considerations
The data structures used in the Logger Core are the most critical part of the design as they have direct impact on the key logger parameters (especially performance). At the first look, a plain circular buffer satisfies all needs: saving data in the buffer is fast, the data blocks could have different size and memory usage is very efficient. However there are some corner cases which require complex handling when this type of log storage is used.

The first, obvious limitation of the plain circular buffer is a requirement of memory copying shown on the picture above. The data must be copied out from the circular buffer and placed into dedicated backed queues. If the same message is directed to several backends, the same data is copied multiple times, occupying significant amount of the memory. The other problem, presented on the picture below is visible when logging is performed from code running on different priority levels:

In the example presented above a thread producing log entries is preempted by an interrupt which also logs some messages. The preemption occurred when the thread was writing data to the Log buffer, making Log Entry #3 incomplete. As result the Log Entry #3 is stuck in the buffer until execution of interrupted thread is not resumed, which have several implications:

In case of any error triggering a log readout (for example a crash in the interrupt which triggers Panic Mode), this entry must be skipped by code reading log buffer.
If the interrupt will produce enough logs to fill the buffer, the oldest entries will be replaced by the new ones. The stuck entry also have to be skipped during this process. Moreover, in order to keep consistent log output, the skipped entry should not produce any message on the output when system will finally reach log processing in the idle thread as it would be overwritten in normal situation.
The stuck Log Entry #3 also creates fragmentation problem in the log buffer: If the size of the IRQ Log Entry #6 exceed the size of space available between beginning of the log buffer and the stuck entry, a new log entry must be either placed after the Log Entry #3 (but this will create a hole in the buffer, which have to be handled) or simply dropped.

All the issues mentioned above could be resolved by using a slight modified data structures presented below:

In the proposed approach a fixed size log entries are allocated from the dedicated pool, filled in and then placed into circular buffer, eliminating stuck entry issue described earlier. As the entries are fixed size, the buffer pool might use efficient block allocator (like mem_slab) to handle most common cases. In order to satisfy larger requests, like data dumping, the entries could be chained together, as seen on the figure above. Further data handling also requires minimal overhead because the log entries could be shared by multiple backends due to reference counter present in the log entry header. After processing the backends are decrementing the reference counter and the log entry returns into the pool when it is no longer used.

I think it's worth mentioning the limitations of this approach:

using %s with strings which are not permanent. Logger is storing argument value so it will store address of the string which may be on stack. By the time message is processed string content is not valid anymore.
arguments are 32 bit. Logging of doubles is not supported.

closing, need to track any enhancements individually.


Space  will lead to abnormal line breaks in Languages with non Latin alphabets in RichTextLabel

Godot version:

v3.2.3.stable
OS/device including version:

win7
Issue description:

Some languages do not use spaces to separate words, so one word such as 中 in these languages will be treated as a letter in English, while two words such as 中文     will be treated as one English word because of spaces.
Eventually, this will result in a newline exception.
The following is the specific effect, I tested Chinese and Japanese.
Label (Text above) is right, but RichTextLabel (Text below)  is wrong!
The second and fourth lines are treated as one English word in RichTextLabel.

Steps to reproduce:
Copy the following sentence to Label Node and RichTextLabel:
中文 中文 中文中文中文中文中文 日本語 日本語 日本語日本語日本語
Minimal reproduction project:

This is the project file. I'm sorry, I missed the font before
LabelTest.zip

I suppose proper line breaks for non-Latin languages were only added in the TextServer implementation, which is in master but not 3.2.x. Due to the large amount of backward-incompatible changes it contains, it can't be backported to 3.2.x.
cc @bruvzg

I suppose proper line breaks for non-Latin languages were only added in the TextServer implementation, which is in master but not 3.2.x. Due to the large amount of backward-incompatible changes it contains, it can't be backported to 3.2.x.
cc @bruvzg

I tested in 3.2.4 beta5 and master and I don't see difference.

the issue is easy to reappearance

The project would still be useful, because you need custom font to display non-latin letters.

I tested in 3.2.4 beta5 and master and I don't see difference.

the issue is easy to reappearance

The project would still be useful, because you need custom font to display non-latin letters.

@KoBeWi   Maybe 3.2.4 has been fixed? And I have upload the project,I'm sorry I forgot about the problem of language font

@KoBeWi   Maybe 3.2.4 has been fixed? And I have upload the project,I'm sorry I forgot about the problem of language font

Maybe 3.2.4 has been fixed?

It's not.
In 3.2:
In 3.2 Label (top on the screen recordings) is always breaking single characters and RichTextLabel will try to break "words" (anything separated with space or punctuation) first.
https://user-images.githubusercontent.com/7645683/104809911-91d41280-57f9-11eb-8dd7-c2a5acfe5772.mov
In master:
In  the master both use ICU word breaker (language specific rule + dictionary based).
https://user-images.githubusercontent.com/7645683/104809916-98fb2080-57f9-11eb-95e8-051169f70303.mov

Maybe 3.2.4 has been fixed?

It's not.
In 3.2:
In 3.2 Label (top on the screen recordings) is always breaking single characters and RichTextLabel will try to break "words" (anything separated with space or punctuation) first.
https://user-images.githubusercontent.com/7645683/104809911-91d41280-57f9-11eb-8dd7-c2a5acfe5772.mov
In master:
In  the master both use ICU word breaker (language specific rule + dictionary based).
https://user-images.githubusercontent.com/7645683/104809916-98fb2080-57f9-11eb-95e8-051169f70303.mov


[Suggestion] Replace arrow firing sound

It would be awesome if you could replace the arrow firing sound with something that fits the bow pull noise a bit better than the vanilla sound.

Replacing the bow loose sound for skellies and players!

Pushed v<IP_ADDRESS> with the enhancement.


Not allowing to place CONTENT_IGNORE while trying to replace "air" at

Use with other mods to generate errors, disable multidecor to prevent errors from occurring
2023-02-13 14:08:23: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "multidecor:oil_source" at (-350,-248,-294) (block (-22,-16,-19))
2023-02-13 14:08:23: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-427,-69,-384) (block (-27,-5,-24))
2023-02-13 14:08:23: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-427,-69,-386) (block (-27,-5,-25))
2023-02-13 14:08:23: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-428,-69,-385) (block (-27,-5,-25))
2023-02-13 14:08:23: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-367,-19,-362) (block (-23,-2,-23))
2023-02-13 14:08:23: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-367,-19,-361) (block (-23,-2,-23))
2023-02-13 14:08:23: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-285,-12,-364) (block (-18,-1,-23))
2023-02-13 14:08:23: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-284,-12,-365) (block (-18,-1,-23))
2023-02-13 14:08:23: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-285,-13,-365) (block (-18,-1,-23))
2023-02-13 14:08:23: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-327,-21,-260) (block (-21,-2,-17))
2023-02-13 14:08:23: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-328,-21,-259) (block (-21,-2,-17))
2023-02-13 14:08:23: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-362,-9,-271) (block (-23,-1,-17))
2023-02-13 14:08:23: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-299,-27,-374) (block (-19,-2,-24))
2023-02-13 14:08:23: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-278,-30,-557) (block (-18,-2,-35))
2023-02-13 14:08:23: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-183,-17,-429) (block (-12,-2,-27))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-395,-24,-243) (block (-25,-2,-16))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-362,-7,-390) (block (-23,-1,-25))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-266,-46,-326) (block (-17,-3,-21))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-397,-7,-506) (block (-25,-1,-32))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-396,-7,-507) (block (-25,-1,-32))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-397,-8,-507) (block (-25,-1,-32))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-460,-11,-438) (block (-29,-1,-28))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-419,-50,-503) (block (-27,-4,-32))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-449,-60,-466) (block (-29,-4,-30))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-486,-25,-421) (block (-31,-2,-27))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-407,-119,-493) (block (-26,-8,-31))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-408,-119,-492) (block (-26,-8,-31))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-441,-37,-384) (block (-28,-3,-24))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-440,-38,-384) (block (-28,-3,-24))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-386,-90,-542) (block (-25,-6,-34))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-331,-72,-262) (block (-21,-5,-17))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-330,-72,-261) (block (-21,-5,-17))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-331,-73,-261) (block (-21,-5,-17))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-297,-27,-374) (block (-19,-2,-24))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-298,-27,-375) (block (-19,-2,-24))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-297,-26,-373) (block (-19,-2,-24))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-299,-26,-373) (block (-19,-2,-24))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-299,-27,-374) (block (-19,-2,-24))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-360,-19,-236) (block (-23,-2,-15))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-209,-108,-469) (block (-14,-7,-30))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-210,-109,-469) (block (-14,-7,-30))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-241,-121,-266) (block (-16,-8,-17))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-242,-122,-265) (block (-16,-8,-17))
2023-02-13 14:08:24: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-349,-249,-294) (block (-22,-16,-19))
2023-02-13 14:08:25: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-427,-69,-384) (block (-27,-5,-24))
2023-02-13 14:08:25: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-427,-69,-386) (block (-27,-5,-25))
2023-02-13 14:08:25: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-428,-69,-385) (block (-27,-5,-25))
2023-02-13 14:08:25: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-367,-19,-362) (block (-23,-2,-23))
2023-02-13 14:08:25: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-367,-19,-361) (block (-23,-2,-23))
2023-02-13 14:08:25: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-285,-12,-364) (block (-18,-1,-23))
2023-02-13 14:08:25: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-284,-12,-365) (block (-18,-1,-23))
2023-02-13 14:08:25: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-285,-13,-365) (block (-18,-1,-23))
2023-02-13 14:08:25: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-327,-21,-260) (block (-21,-2,-17))
2023-02-13 14:08:25: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-328,-21,-259) (block (-21,-2,-17))
2023-02-13 14:08:25: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-362,-9,-271) (block (-23,-1,-17))
2023-02-13 14:08:25: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-297,-27,-374) (block (-19,-2,-24))
2023-02-13 14:08:25: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-298,-27,-375) (block (-19,-2,-24))
2023-02-13 14:08:25: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-278,-30,-557) (block (-18,-2,-35))
2023-02-13 14:08:25: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-183,-17,-429) (block (-12,-2,-27))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-395,-24,-243) (block (-25,-2,-16))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-362,-7,-390) (block (-23,-1,-25))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-266,-46,-326) (block (-17,-3,-21))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-397,-7,-506) (block (-25,-1,-32))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-396,-7,-507) (block (-25,-1,-32))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-397,-8,-507) (block (-25,-1,-32))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-460,-11,-438) (block (-29,-1,-28))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-419,-50,-503) (block (-27,-4,-32))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-449,-60,-466) (block (-29,-4,-30))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-486,-25,-421) (block (-31,-2,-27))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-407,-119,-493) (block (-26,-8,-31))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-408,-119,-492) (block (-26,-8,-31))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-441,-37,-384) (block (-28,-3,-24))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-440,-38,-384) (block (-28,-3,-24))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-386,-90,-542) (block (-25,-6,-34))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-331,-72,-262) (block (-21,-5,-17))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-330,-72,-261) (block (-21,-5,-17))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-331,-73,-261) (block (-21,-5,-17))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-297,-26,-373) (block (-19,-2,-24))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-299,-26,-373) (block (-19,-2,-24))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-299,-27,-374) (block (-19,-2,-24))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-297,-27,-374) (block (-19,-2,-24))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-298,-27,-375) (block (-19,-2,-24))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-360,-19,-236) (block (-23,-2,-15))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-209,-108,-469) (block (-14,-7,-30))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-210,-109,-469) (block (-14,-7,-30))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-241,-121,-266) (block (-16,-8,-17))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-242,-122,-265) (block (-16,-8,-17))
2023-02-13 14:08:26: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-349,-249,-294) (block (-22,-16,-19))
2023-02-13 14:08:27: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-427,-69,-384) (block (-27,-5,-24))
2023-02-13 14:08:27: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-427,-69,-386) (block (-27,-5,-25))
2023-02-13 14:08:27: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-428,-69,-385) (block (-27,-5,-25))
2023-02-13 14:08:27: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-367,-19,-362) (block (-23,-2,-23))
2023-02-13 14:08:27: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-367,-19,-361) (block (-23,-2,-23))
2023-02-13 14:08:27: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-285,-12,-364) (block (-18,-1,-23))
2023-02-13 14:08:27: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-284,-12,-365) (block (-18,-1,-23))
2023-02-13 14:08:27: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-285,-13,-365) (block (-18,-1,-23))
2023-02-13 14:08:27: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-327,-21,-260) (block (-21,-2,-17))
2023-02-13 14:08:27: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-328,-21,-259) (block (-21,-2,-17))
2023-02-13 14:08:27: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-362,-9,-271) (block (-23,-1,-17))
2023-02-13 14:08:27: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-297,-26,-373) (block (-19,-2,-24))
2023-02-13 14:08:27: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-278,-30,-557) (block (-18,-2,-35))
2023-02-13 14:08:27: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-183,-17,-429) (block (-12,-2,-27))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-395,-24,-243) (block (-25,-2,-16))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-362,-7,-390) (block (-23,-1,-25))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-266,-46,-326) (block (-17,-3,-21))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-397,-7,-506) (block (-25,-1,-32))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-396,-7,-507) (block (-25,-1,-32))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-397,-8,-507) (block (-25,-1,-32))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-460,-11,-438) (block (-29,-1,-28))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-419,-50,-503) (block (-27,-4,-32))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-449,-60,-466) (block (-29,-4,-30))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-486,-25,-421) (block (-31,-2,-27))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-407,-119,-493) (block (-26,-8,-31))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-408,-119,-492) (block (-26,-8,-31))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-441,-37,-384) (block (-28,-3,-24))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-440,-38,-384) (block (-28,-3,-24))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-386,-90,-542) (block (-25,-6,-34))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-331,-72,-262) (block (-21,-5,-17))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-330,-72,-261) (block (-21,-5,-17))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-331,-73,-261) (block (-21,-5,-17))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-299,-26,-373) (block (-19,-2,-24))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-299,-27,-374) (block (-19,-2,-24))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-297,-27,-374) (block (-19,-2,-24))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-298,-27,-375) (block (-19,-2,-24))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-297,-26,-373) (block (-19,-2,-24))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-360,-19,-236) (block (-23,-2,-15))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-209,-108,-469) (block (-14,-7,-30))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-210,-109,-469) (block (-14,-7,-30))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-241,-121,-266) (block (-16,-8,-17))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-242,-122,-265) (block (-16,-8,-17))
2023-02-13 14:08:28: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-349,-249,-294) (block (-22,-16,-19))
2023-02-13 14:08:29: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-427,-69,-384) (block (-27,-5,-24))
2023-02-13 14:08:29: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-427,-69,-386) (block (-27,-5,-25))
2023-02-13 14:08:29: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-428,-69,-385) (block (-27,-5,-25))
2023-02-13 14:08:29: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-367,-19,-362) (block (-23,-2,-23))
2023-02-13 14:08:29: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-367,-19,-361) (block (-23,-2,-23))
2023-02-13 14:08:29: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-285,-12,-364) (block (-18,-1,-23))
2023-02-13 14:08:29: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-284,-12,-365) (block (-18,-1,-23))
2023-02-13 14:08:29: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-285,-13,-365) (block (-18,-1,-23))
2023-02-13 14:08:29: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-327,-21,-260) (block (-21,-2,-17))
2023-02-13 14:08:29: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-328,-21,-259) (block (-21,-2,-17))
2023-02-13 14:08:29: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-362,-9,-271) (block (-23,-1,-17))
2023-02-13 14:08:29: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-299,-26,-373) (block (-19,-2,-24))
2023-02-13 14:08:29: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-278,-30,-557) (block (-18,-2,-35))
2023-02-13 14:08:29: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-183,-17,-429) (block (-12,-2,-27))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-395,-24,-243) (block (-25,-2,-16))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-362,-7,-390) (block (-23,-1,-25))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-266,-46,-326) (block (-17,-3,-21))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-397,-7,-506) (block (-25,-1,-32))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-396,-7,-507) (block (-25,-1,-32))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-397,-8,-507) (block (-25,-1,-32))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-460,-11,-438) (block (-29,-1,-28))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-419,-50,-503) (block (-27,-4,-32))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-449,-60,-466) (block (-29,-4,-30))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-486,-25,-421) (block (-31,-2,-27))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-407,-119,-493) (block (-26,-8,-31))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-408,-119,-492) (block (-26,-8,-31))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-441,-37,-384) (block (-28,-3,-24))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-440,-38,-384) (block (-28,-3,-24))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-386,-90,-542) (block (-25,-6,-34))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-331,-72,-262) (block (-21,-5,-17))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-330,-72,-261) (block (-21,-5,-17))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-331,-73,-261) (block (-21,-5,-17))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-299,-27,-374) (block (-19,-2,-24))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-297,-27,-374) (block (-19,-2,-24))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-298,-27,-375) (block (-19,-2,-24))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-297,-26,-373) (block (-19,-2,-24))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-299,-26,-373) (block (-19,-2,-24))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-360,-19,-236) (block (-23,-2,-15))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-209,-108,-469) (block (-14,-7,-30))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-210,-109,-469) (block (-14,-7,-30))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-241,-121,-266) (block (-16,-8,-17))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-242,-122,-265) (block (-16,-8,-17))
2023-02-13 14:08:30: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-349,-249,-294) (block (-22,-16,-19))
2023-02-13 14:08:31: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-427,-69,-384) (block (-27,-5,-24))
2023-02-13 14:08:31: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-427,-69,-386) (block (-27,-5,-25))
2023-02-13 14:08:31: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-428,-69,-385) (block (-27,-5,-25))
2023-02-13 14:08:31: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-367,-19,-362) (block (-23,-2,-23))
2023-02-13 14:08:31: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-367,-19,-361) (block (-23,-2,-23))
2023-02-13 14:08:31: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-285,-12,-364) (block (-18,-1,-23))
2023-02-13 14:08:31: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-284,-12,-365) (block (-18,-1,-23))
2023-02-13 14:08:31: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-285,-13,-365) (block (-18,-1,-23))
2023-02-13 14:08:31: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-327,-21,-260) (block (-21,-2,-17))
2023-02-13 14:08:31: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-328,-21,-259) (block (-21,-2,-17))
2023-02-13 14:08:31: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-362,-9,-271) (block (-23,-1,-17))
2023-02-13 14:08:31: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-299,-27,-374) (block (-19,-2,-24))
2023-02-13 14:08:31: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-278,-30,-557) (block (-18,-2,-35))
2023-02-13 14:08:31: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-183,-17,-429) (block (-12,-2,-27))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-395,-24,-243) (block (-25,-2,-16))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-362,-7,-390) (block (-23,-1,-25))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-266,-46,-326) (block (-17,-3,-21))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-397,-7,-506) (block (-25,-1,-32))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-396,-7,-507) (block (-25,-1,-32))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-397,-8,-507) (block (-25,-1,-32))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-460,-11,-438) (block (-29,-1,-28))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-419,-50,-503) (block (-27,-4,-32))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-449,-60,-466) (block (-29,-4,-30))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-486,-25,-421) (block (-31,-2,-27))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-407,-119,-493) (block (-26,-8,-31))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-408,-119,-492) (block (-26,-8,-31))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-441,-37,-384) (block (-28,-3,-24))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-440,-38,-384) (block (-28,-3,-24))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-386,-90,-542) (block (-25,-6,-34))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-331,-72,-262) (block (-21,-5,-17))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-330,-72,-261) (block (-21,-5,-17))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-331,-73,-261) (block (-21,-5,-17))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-297,-27,-374) (block (-19,-2,-24))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-298,-27,-375) (block (-19,-2,-24))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-297,-26,-373) (block (-19,-2,-24))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-299,-26,-373) (block (-19,-2,-24))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-299,-27,-374) (block (-19,-2,-24))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-360,-19,-236) (block (-23,-2,-15))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-209,-108,-469) (block (-14,-7,-30))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-210,-109,-469) (block (-14,-7,-30))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-241,-121,-266) (block (-16,-8,-17))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-242,-122,-265) (block (-16,-8,-17))
2023-02-13 14:08:32: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-349,-249,-294) (block (-22,-16,-19))
2023-02-13 14:08:33: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-427,-69,-384) (block (-27,-5,-24))
2023-02-13 14:08:33: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-427,-69,-386) (block (-27,-5,-25))
2023-02-13 14:08:33: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-428,-69,-385) (block (-27,-5,-25))
2023-02-13 14:08:33: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-367,-19,-362) (block (-23,-2,-23))
2023-02-13 14:08:33: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-367,-19,-361) (block (-23,-2,-23))
2023-02-13 14:08:33: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-285,-12,-364) (block (-18,-1,-23))
2023-02-13 14:08:33: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-284,-12,-365) (block (-18,-1,-23))
2023-02-13 14:08:33: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-285,-13,-365) (block (-18,-1,-23))
2023-02-13 14:08:33: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-327,-21,-260) (block (-21,-2,-17))
2023-02-13 14:08:33: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-328,-21,-259) (block (-21,-2,-17))
2023-02-13 14:08:33: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-362,-9,-271) (block (-23,-1,-17))
2023-02-13 14:08:33: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-297,-27,-374) (block (-19,-2,-24))
2023-02-13 14:08:33: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-298,-27,-375) (block (-19,-2,-24))
2023-02-13 14:08:33: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-278,-30,-557) (block (-18,-2,-35))
2023-02-13 14:08:33: ERROR[Server]: Not allowing to place CONTENT_IGNORE while trying to replace "air" at (-183,-17,-429) (block (-12,-2,-27))

Which mods enabled does this kind of the error occur with? I don't get that chat output in any case.

Which mods enabled does this kind of the error occur with? I don't get that chat output in any case.

Using multidecor and journal  together produces this error

I have removed journal from my list of mods


Enabling kubeflow on microk8s

I installed microk8s using sudo snap install microk8s --classic,
I enabled dns, dashboard and storage with microk8s enable dns dashboard storage,
I tried enabling kubeflow with microk8s enable kubeflow, inputted the password and it prompted me to add --ignore-min-mem,
I tried enabling kubeflow with microk8s enable kubeflow --ignore-min-mem, inputted the password and it gave me this error message
Kubeflow could not be enabled:
error: deployment "calico-kube-controllers" exceeded its progress deadline
Command '('microk8s-kubectl.wrapper', '-nkube-system', 'rollout', 'status', 'deployment.apps/calico-kube-controllers')' returned non-zero exit status 1
I expected kubeflow to be enabled and also get a link to access the dashboard
Environment:

Kubernetes platform: microk8s
Kubernetes version: (use kubectl version): Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.2", GitCommit:"faecb196815e248d3ecfb03c680a4507229c2a56", GitTreeState:"clean", BuildDate:"2021-01-15T02:50:16Z", GoVersion:"go1.15.6", Compiler:"gc", Platform:"linux/amd64"}
OS (e.g. from /etc/os-release): ubuntu 20.04 focal

@ktsakalozos: Any idea what might be the issue here?

@ktsakalozos: Any idea what might be the issue here?

Hi @TosinAina would you me able to run microk8s inspect and attach the gathered logs?
For some reason the calico CNI was not setup on time.

Hi @TosinAina would you me able to run microk8s inspect and attach the gathered logs?
For some reason the calico CNI was not setup on time.

Inspecting Certificates
Inspecting services
Service snap.microk8s.daemon-cluster-agent is running
Service snap.microk8s.daemon-containerd is running
Service snap.microk8s.daemon-apiserver is running
Service snap.microk8s.daemon-apiserver-kicker is running
Service snap.microk8s.daemon-control-plane-kicker is running
Service snap.microk8s.daemon-proxy is running
Service snap.microk8s.daemon-kubelet is running
Service snap.microk8s.daemon-scheduler is running
Service snap.microk8s.daemon-controller-manager is running
Copy service arguments to the final report tarball
Inspecting AppArmor configuration
Gathering system information
Copy processes list to the final report tarball
Copy snap list to the final report tarball
Copy VM name (or none) to the final report tarball
Copy disk usage information to the final report tarball
Copy memory usage information to the final report tarball
Copy server uptime to the final report tarball
Copy current linux distribution to the final report tarball
Copy openSSL information to the final report tarball
Copy network configuration to the final report tarball
Inspecting kubernetes cluster
Inspect kubernetes cluster
Inspecting juju
Inspect Juju
Inspecting kubeflow
Inspect Kubeflow
WARNING:  Docker is installed.
File "/etc/docker/daemon.json" does not exist.
You should create it and add the following lines:
{
"insecure-registries" : ["localhost:32000"]
}
and then restart docker with: sudo systemctl restart docker
Building the report tarball
Report tarball is at /var/snap/microk8s/1975/inspection-report-20210121_195748.tar.gz

Inspecting Certificates
Inspecting services
Service snap.microk8s.daemon-cluster-agent is running
Service snap.microk8s.daemon-containerd is running
Service snap.microk8s.daemon-apiserver is running
Service snap.microk8s.daemon-apiserver-kicker is running
Service snap.microk8s.daemon-control-plane-kicker is running
Service snap.microk8s.daemon-proxy is running
Service snap.microk8s.daemon-kubelet is running
Service snap.microk8s.daemon-scheduler is running
Service snap.microk8s.daemon-controller-manager is running
Copy service arguments to the final report tarball
Inspecting AppArmor configuration
Gathering system information
Copy processes list to the final report tarball
Copy snap list to the final report tarball
Copy VM name (or none) to the final report tarball
Copy disk usage information to the final report tarball
Copy memory usage information to the final report tarball
Copy server uptime to the final report tarball
Copy current linux distribution to the final report tarball
Copy openSSL information to the final report tarball
Copy network configuration to the final report tarball
Inspecting kubernetes cluster
Inspect kubernetes cluster
Inspecting juju
Inspect Juju
Inspecting kubeflow
Inspect Kubeflow
WARNING:  Docker is installed.
File "/etc/docker/daemon.json" does not exist.
You should create it and add the following lines:
{
"insecure-registries" : ["localhost:32000"]
}
and then restart docker with: sudo systemctl restart docker
Building the report tarball
Report tarball is at /var/snap/microk8s/1975/inspection-report-20210121_195748.tar.gz

@TosinAina: Could you upload the generated tarball to this thread (/var/snap/microk8s/1975/inspection-report-20210121_195748.tar.gz)?

@TosinAina: Could you upload the generated tarball to this thread (/var/snap/microk8s/1975/inspection-report-20210121_195748.tar.gz)?

Same error here

@dinever: Could you run microk8s inspect and attach the generated tarball?

Hi @knkski, I 'm facing the same issue here, my microk8s version is 1.20/stable. I uploaded the tarball here.
inspection-report-20210610_095430.tar.gz
And I' facing a syntax error, everytime I try to disable kubeflow (I tried as suggestion to disable and enable kubeflow):
ubuntu@xxxx:~$ microk8s disable kubeflow
  File "/snap/microk8s/2213/scripts/wrappers/common/../../../actions/disable.kubeflow.sh", line 52
    click.echo(f"Destroying Kubeflow {resource}...")
                                                  ^
SyntaxError: invalid syntax

I forgot to apply the NO_PROXY on var/snap/microk8s/current/args/containerd-env, while I set the HTTP-PROXY behind my coorporate firewall. 🤦

So I tried to get the information about this 'calico-kube-control'-container with microk8s kubectl describe all  and apparently the container couldn't be created, because there was no direct connection to <IP_ADDRESS>. After setting up the NO_PROXY on var/snap/microk8s/current/args/containerd-env, it worked very well then and this 'calico-kube-control'-container can be created 😄
But after I got this solution, I got another https://github.com/ubuntu/microk8s/issues/1439 problem. 🤦