Druid docker builds failing, docker won't start

Affected Version
0.19.0
Description
Installed docker from https://hub.docker.com/r/apache/druid (tag 0.19.0). Noticed build status on docker hub is failing.
When starting the docker container I get:

2020-07-29T18:15:46+0000 startup service

Setting <IP_ADDRESS>= in /runtime.properties

cat: can't open '/jvm.config': No such file or directory

2020-07-29T18:15:50,348 INFO [main] org.hibernate.validator.internal.util.Version - HV000001: Hibernate Validator 5.2.5.Final

2020-07-29T18:15:52,125 INFO [main] org.apache.druid.initialization.Initialization - Loading extension [druid-hdfs-storage], jars: commons-codec-1.13.jar, commons-net-3.6.jar, druid-hdfs-storage-0.19.0.jar, hadoop-hdfs-client-2.8.5.jar, jackson-databind-2.10.2.jar, httpcore-4.4.11.jar, hadoop-mapreduce-client-app-2.8.5.jar, apacheds-kerberos-codec-2.0.0-M15.jar, hadoop-yarn-api-2.8.5.jar, json-smart-2.3.jar, hadoop-auth-2.8.5.jar, api-asn1-api-1.0.0-M20.jar, curator-recipes-4.3.0.jar, htrace-core4-4.0.1-incubating.jar, jackson-core-2.10.2.jar, leveldbjni-all-1.8.jar, hadoop-common-2.8.5.jar, hadoop-annotations-2.8.5.jar, jetty-sslengine-6.1.26.jar, aws-java-sdk-core-1.11.199.jar, ion-java-1.0.2.jar, apacheds-i18n-2.0.0-M15.jar, hadoop-yarn-server-common-2.8.5.jar, hadoop-mapreduce-client-core-2.8.5.jar, hadoop-yarn-client-2.8.5.jar, curator-framework-4.3.0.jar, nimbus-jose-jwt-4.41.1.jar, hadoop-aws-2.8.5.jar, httpclient-4.5.10.jar, commons-collections-3.2.2.jar, hadoop-mapreduce-client-jobclient-2.8.5.jar, jackson-dataformat-cbor-2.10.2.jar, jmespath-java-1.11.199.jar, commons-configuration-1.6.jar, joda-time-2.10.5.jar, hadoop-mapreduce-client-shuffle-2.8.5.jar, aws-java-sdk-s3-1.11.199.jar, jackson-core-asl-1.9.13.jar, commons-digester-1.8.jar, api-util-1.0.3.jar, aws-java-sdk-kms-1.11.199.jar, gson-2.2.4.jar, asm-7.1.jar, hadoop-client-2.8.5.jar, xmlenc-0.52.jar, jsp-api-2.1.jar, accessors-smart-1.2.jar, commons-logging-1.1.1.jar, hadoop-mapreduce-client-common-2.8.5.jar, jcip-annotations-1.0-1.jar, jackson-annotations-2.10.2.jar, jackson-mapper-asl-1.9.13.jar

2020-07-29T18:15:52,178 INFO [main] org.apache.druid.initialization.Initialization - Loading extension [druid-kafka-indexing-service], jars: zstd-jni-1.3.3-1.jar, druid-kafka-indexing-service-0.19.0.jar, kafka-clients-2.5.0.jar, lz4-java-1.7.1.jar, snappy-java-<IP_ADDRESS>.jar

2020-07-29T18:15:52,182 INFO [main] org.apache.druid.initialization.Initialization - Loading extension [druid-datasketches], jars: druid-datasketches-0.19.0.jar, commons-math3-3.6.1.jar

usage: druid <command> [<args>]

The most commonly used druid commands are:

help Display help information

index Run indexing for druid

internal Processes that Druid runs "internally", you should rarely use these directly

server Run one of the Druid server types.

tools Various tools for working with Druid

version Returns Druid version information

See 'druid help <command>' for more information on a specific command.

2020-07-29T18:16:00+0000 startup service

Setting <IP_ADDRESS>= in /runtime.properties

cat: can't open '/jvm.config': No such file or directory

2020-07-29T18:16:02,026 INFO [main] org.hibernate.validator.internal.util.Version - HV000001: Hibernate Validator 5.2.5.Final

2020-07-29T18:16:03,218 INFO [main] org.apache.druid.initialization.Initialization - Loading extension [druid-hdfs-storage], jars: commons-codec-1.13.jar, commons-net-3.6.jar, druid-hdfs-storage-0.19.0.jar, hadoop-hdfs-client-2.8.5.jar, jackson-databind-2.10.2.jar, httpcore-4.4.11.jar, hadoop-mapreduce-client-app-2.8.5.jar, apacheds-kerberos-codec-2.0.0-M15.jar, hadoop-yarn-api-2.8.5.jar, json-smart-2.3.jar, hadoop-auth-2.8.5.jar, api-asn1-api-1.0.0-M20.jar, curator-recipes-4.3.0.jar, htrace-core4-4.0.1-incubating.jar, jackson-core-2.10.2.jar, leveldbjni-all-1.8.jar, hadoop-common-2.8.5.jar, hadoop-annotations-2.8.5.jar, jetty-sslengine-6.1.26.jar, aws-java-sdk-core-1.11.199.jar, ion-java-1.0.2.jar, apacheds-i18n-2.0.0-M15.jar, hadoop-yarn-server-common-2.8.5.jar, hadoop-mapreduce-client-core-2.8.5.jar, hadoop-yarn-client-2.8.5.jar, curator-framework-4.3.0.jar, nimbus-jose-jwt-4.41.1.jar, hadoop-aws-2.8.5.jar, httpclient-4.5.10.jar, commons-collections-3.2.2.jar, hadoop-mapreduce-client-jobclient-2.8.5.jar, jackson-dataformat-cbor-2.10.2.jar, jmespath-java-1.11.199.jar, commons-configuration-1.6.jar, joda-time-2.10.5.jar, hadoop-mapreduce-client-shuffle-2.8.5.jar, aws-java-sdk-s3-1.11.199.jar, jackson-core-asl-1.9.13.jar, commons-digester-1.8.jar, api-util-1.0.3.jar, aws-java-sdk-kms-1.11.199.jar, gson-2.2.4.jar, asm-7.1.jar, hadoop-client-2.8.5.jar, xmlenc-0.52.jar, jsp-api-2.1.jar, accessors-smart-1.2.jar, commons-logging-1.1.1.jar, hadoop-mapreduce-client-common-2.8.5.jar, jcip-annotations-1.0-1.jar, jackson-annotations-2.10.2.jar, jackson-mapper-asl-1.9.13.jar

2020-07-29T18:16:03,252 INFO [main] org.apache.druid.initialization.Initialization - Loading extension [druid-kafka-indexing-service], jars: zstd-jni-1.3.3-1.jar, druid-kafka-indexing-service-0.19.0.jar, kafka-clients-2.5.0.jar, lz4-java-1.7.1.jar, snappy-java-<IP_ADDRESS>.jar

2020-07-29T18:16:03,260 INFO [main] org.apache.druid.initialization.Initialization - Loading extension [druid-datasketches], jars: druid-datasketches-0.19.0.jar, commons-math3-3.6.1.jar

usage: druid <command> [<args>]

The most commonly used druid commands are:

help Display help information

index Run indexing for druid

internal Processes that Druid runs "internally", you should rarely use these directly

server Run one of the Druid server types.

tools Various tools for working with Druid

version Returns Druid version information

See 'druid help <command>' for more information on a specific command.

Hi @chreds i  have been getting pretty much same error after setting the metadata store to either mysql or postgres druid won't start and says cooridnator and middleManager failed to load so what is the solution for this?


Gap after a swing

I'm noticing a little gap in the sound before each time I swing, but there's no gaps before a clash sound (only some very random times). I'm using the "base soundpack".

Do you mean the sound pack included in the repository?
Jason "Kuma" Brinkerhoff
*Mad Science Workshoppe, *proprietor
http://jbkuma.com/workshoppe
On Fri, May 26, 2017 at 4:08 PM, Stiffartic<EMAIL_ADDRESS>wrote:

I'm noticing a little gap in the sound after each time I swing, but
there's no gaps after a clash sound. I'm using the "base soundpack".
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/neskweek/LightSaberOS/issues/60, or mute the thread
https://github.com/notifications/unsubscribe-auth/ATdCMD5cttqkrl6RUPzIaOfUN1HWfYexks5r9zE7gaJpZM4NoAxN
.

Yeah! With that pack!


Section 1 Test

The links for how to take the test and submit answers are broken

I got to this module through a redirect, and it seems as though I am not registered for it. The old class is deprecated, so getting credit here is unlikely.


Update README to clarify usage instructions

docs: Clarify how to use hours/days.
Fixes #34

All good to me, thanks you ! @NicoHaase what do you think ?


Create nl.js

Added the Dutch language. You still gotta add the option to use it (with the buttons etc)

:)

Added the Dutch language. You still gotta add the option to use it (with the buttons etc)

Thank you for everything, but after you there were new additions to the language file, if you update them, I will think about the pull request.

I addedthe new messages!

Id  you add more strings in the future hit me up and I'll add the Dutch translation

If you add new words to the language files you can just add the english translation to nl.js and ill translate it:)


Pick one way to write license in README

Used the US grammar to keep it easy.
https://www.grammarly.com/blog/licence-license/

Thank you very much for this PR!

My pleasure, nice project you for going here.


WIP: Allow for train/test splits of data

Oh, also, this is not yet tested in the presence of a train/test split since stitch currently crashes on all the inputs I have saved that have such a split

@theoxo Oh sorry for testing use --no-mismatch-check to disable to crashes

Ah, so there's a lot of duplicated output. Will change the output formatting to get rid of that.
Also, this seems a bit suspicious:
train: fn_11 (1.14x wrt orig): utility: 4042 | final_cost (train): 134371 | multiplier (train): 1.03x | uses (train): 43 | final_cost(test): 134371 | multiplier (test): 1.x | uses (test): 43 | body: [fn_11 arity=0: (logo_MULL logo_UL)]
test: fn_11 (3.08x wrt orig): utility: 4042 | final_cost (train): 134371 | multiplier (train): 1.03x | uses (train): 43 | final_cost(test): 134371 | multiplier (test): 1.x | uses (test): 43 | body: [fn_11 arity=0: (logo_MULL logo_UL)]

Why would the compression factor be so much higher for the test set when the number of uses is the same? Something must be getting calculated wrong.

Ah, so there's a lot of duplicated output. Will change the output formatting to get rid of that.
Also, this seems a bit suspicious:
train: fn_11 (1.14x wrt orig): utility: 4042 | final_cost (train): 134371 | multiplier (train): 1.03x | uses (train): 43 | final_cost(test): 134371 | multiplier (test): 1.x | uses (test): 43 | body: [fn_11 arity=0: (logo_MULL logo_UL)]
test: fn_11 (3.08x wrt orig): utility: 4042 | final_cost (train): 134371 | multiplier (train): 1.03x | uses (train): 43 | final_cost(test): 134371 | multiplier (test): 1.x | uses (test): 43 | body: [fn_11 arity=0: (logo_MULL logo_UL)]

Why would the compression factor be so much higher for the test set when the number of uses is the same? Something must be getting calculated wrong.

Yeah somethings up there, my guess is you're accidentally using the training utility or final_cost or something for the test se which is affecting the rest of the calculations but I havent actually looked at the code

I just added a hand-rolled implementation of inspect() and inspect_or() to src/util.rs in bc37690 that seem to do the trick. This seemed like the most elegant solution to me in the places where cloning would otherwise be needed. I looked into as_deref() and it felt like it would be more code (Deref isn't a trait you can #derive, apparently). This way we can just drop back to the std lib once inspect and its siblings have been stabilized.

Yeah somethings up there, my guess is you're accidentally using the training utility or final_cost or something for the test se which is affecting the rest of the calculations but I havent actually looked at the code

I think 0c4779d resolves this issue...

Sweet I havent had a chance to look thru all this yet but I will in a minute! Thanks for doing all this

Oh  wait on comparing your inspect defintiion to the rust one https://doc.rust-lang.org/src/core/option.rs.html#906-909 Im realizing that their closure actually doesnt return anything... in fact theirs is *not* like map at all, it cant mutate or return a new value or anything it just happens to return the same value you give it. Its meant for inspecting the contents of an Option with a read only reference, not for producing a new value based on that. So for clarity we probably shouldnt name this inspect`.
Also... sorry I misread the signatures (and didnt know enough basic rust to realize as_deref would be dereferncing instead of creating a reference).
On closer inspection as_ref() makes more sense than as_deref(). That should work fine.
@theoxo I just tested as_ref() on one example and I think it should work fine.
before:"test_result": inspect(&self.test_data, |d| d.json(&self.inv.name).to_string()),
after: "test_result": self.test_data.as_ref().map(|d| d.json(&self.inv.name).to_string())

Also, does serde_json automatically turn None into null and Some(x) into x? That's what im gathering from the code you wrote, if so thats cool!

Oh wait on comparing your inspect defintiion to the rust one https://doc.rust-lang.org/src/core/option.rs.html#906-909 Im realizing that their closure actually doesnt return anything... in fact theirs is not like map at all, it cant mutate or return a new value or anything it just happens to return the same value you give it. Its meant for inspecting the contents of an Option with a read only reference, not for producing a new value based on that. So for clarity we probably shouldnt name this inspect.
Also... sorry I misread the signatures (and didnt know enough basic rust to realize as_deref would be dereferncing instead of creating a reference).
On closer inspection as_ref() makes more sense than as_deref(). That should work fine.
@theoxo I just tested as_ref() on one example and I think it should work fine. before:"test_result": inspect(&self.test_data, |d| d.json(&self.inv.name).to_string()), after: "test_result": self.test_data.as_ref().map(|d| d.json(&self.inv.name).to_string())

Good catch; changed to use .as_ref() in 9a14e87.

Also, does serde_json automatically turn None into null and Some(x) into x? That's what im gathering from the code you wrote, if so thats cool!

Yes, that's my understanding! I didn't manage to chase it down in the source but inspecting the test_original field in out.json for example this does seem to be the case.

I've realized this still has some issues. Won't merge until after OOPSLA.

@mlb2251 Do you remember what issues there still were with this? The only things that immediately comes to mind are:

Fast rewriting doesn't work for the test set
Slow rewriting isn't equivalent to fast rewriting due to race conditions
The combination of the above two factors means we have some pretty ugly hacks in the code right now (in the impl CompressionStepData) that should be cleaned up once they're no longer necessary

@theoxo can we close this? we already separately added train/test to main ofc


Added user profile and user deletion

Admin user can view a user's profile/information
Admin user can delete all non-admin users

Looks good

Good to merge.


[Registration Workspace] remove the redo/undo area

In order to homogenize workspaces, we could remove the redo/undo area in Registration workspace. What do you think? This is never used by users (or us).

If you want to do image registration, you should start from global rigid / affine before any non-rigid transformation so this area is very useful (and was a lot of efforts to do properly) so please do not remove it.

Oki, however, i just checked and this area is not used when we run Manual Registration, nothing happen in the redo/undo area. It's working for Diffeomorphic Demons.
An other question: why can't we use the system of the other workspaces: user calls a process, the result is saved in the DB, users put the result in the view, and uses another process?

You often try different registration parameters before finding the right ones, so it is nice to be able to do this undo. Otherwise you have to export the previous transfo, reload it (which we actually cannot do currently I think)...

it could be nice to stack the manual registration in this system as well, to be able to export it and to undo it in case of an error

Oki, i put this issue at "Enhancement" then


--help is not working

I expected npx qx create --help to provide help for the create sub-command. It did not. Resulting output was as if the sub-command help had not been requested:

qooxdoo command line interface
==============================
Versions: @qooxdoo/compiler v1.0.0-beta.20200408-1929

Typical usage:
        qx <commands> [options]

      Type qx <command> --help for options and subcommands.

Options:
  --version          Show version number
  [boolean]
  --help             Show help
  [boolean]
  --force, -F        Override warnings
  [boolean] [default: false]
  --config-file, -c  Specify the config file to use
  [string]
  --verbose, -v      enables additional progress output to console
  [boolean]
  --quiet, -q        suppresses normal progress output to console
  [boolean]

done with #671


Configure the TensorFlow integration (SAP HANA EML) with SAP HANA, express edition

Hello!
Very detailed and good tutorial!
Helps me a lot with installation of TFS on Redhat.
Thank you very much!!!
Victor Soukhov. Nornickel, Moscow, Russia.

Thanks for the feedback. And nice work, @adadouche.


New feature: on-entry-delay & on-exit-delay flags

Hi,
Would you add a new delay flag for on-entry and on-exit (console, command and teleport maybe)
It could be useful to delay commands if player move between regions quickly
Delay flag could also be added to delay greeting and farewell WG messages
Thanks for reading.

Delayed commands should be handled by other plugins as for example Skript, creates too much complexity for this plugin in my opinion


how can I add a mime type

I'd like to add a mime type to serve a text/cache.manifest manifest file from my app.
I'm trying to create a html5 offline app. I could use the php buildpack to accomplish this, but it seems like overkill given this app has no local NETWORK resources in the manifest.
If you would accept this in mime.types globally I'll do a pull request ASAP.

If you can find an example nginx snippet on the Internet for this then it can be merged into the nginx.conf being used here. Possible for you to do that?
On Thu, Mar 5, 2015 at 12:25 PM, Lucas Bickel<EMAIL_ADDRESS>wrote:

I'd like to add a mime type to serve a text/cache.manifest manifest file from my app.
I'm trying to create a html5 offline app. I could use the php buildpack to accomplish this, but it seems like overkill given this app has no local NETWORK resources in the manifest.
Reply to this email directly or view it on GitHub:
https://github.com/cloudfoundry-incubator/staticfile-buildpack/issues/16

I added an example in #17. It's in mime.types rather than nginx.conf.

If it helps in the meantime, you should also be able to create a custom mime.types:
https://github.com/cloudfoundry-incubator/staticfile-buildpack/blob/caa6cea1527f4bc8720ee566ff1c4f99331746c1/bin/compile#L52
I've added this to the README in #25.

#25 helps a lot and perfectly answers my original question so I'm closing this issue.
It's nice to know that I can override the nginx.conf as well.
I'm keeping #17 open since I still believe having it as default might have its merits. Feel free to close it if you feel otherwise.


ISPN-11179 Ignore OkHttp thread leaks and close our responses

https://issues.redhat.com/browse/ISPN-11179

@danberindei we need a backport to 10.1.x


⚠ Bofrost.de has degraded performance

In fd90114, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 835 ms

Resolved: Bofrost.de performance has improved in 5839b5d after 6 minutes.


Events announced on discord are displayed on the website

New Folder in APIFunction/Discord.js that contains a method to get messages from discord using the api Modified Event Card and Event List with the discord api integration Added a new term to the config.example.json that is a authentication token to get the the discord to work

I forgot to change the channel_id to the announcement channel


Add multithreading

So this PR aim to add multithreading to nphysics.
This is still a draft, and a lot of things still need to be done.
I prefer to get some opinion before going further, in order to be sure we agree on the design choice.
So here is the actual choices made for this PR :
1. In Bodyset, body and ground are now locked by a RwLock (from parking_lot) :

When body or body_mut are called, It's returning a  RwLockReadGuard and RwLockWriteGuard.
This require rigid_bidy() and multibody() methods from world to be changed so I made them returning a MappedReadLockGuard (or MappedWriteLockGuard for the "mut" methods), in order to have downcast() working.

when add_body() is called it was returning a &mut to a body trait object. With this PR, it should return the RwLock. I changed it and made it return the BodyHandle instead, because I thought it may be better than directly manipulate the RwLock. I am not really sure about this!

One of the problem with RwLock, is that if you want to manipulate a body from your app, and let's say having a write lock, and then you call step(). If you forgot to unlock the body, it's going to block the app, and finally, you are going to have a lot of responsability when using nphysics!!
A solution would be to make the RwLock internal to the body, and each time you call a method, it's internally acquiring the appropriate lock ( read or write ) and then releasing it when finished. The problem is that it would probably kill performance.

Another radically different alternative is to change N: RealField to N: Atomic<RealField> with the atomic crate for example. Then It would be totally non-blocking, and the RwLock problem would not exist. We could use Relaxed ordering for maximum performance and rely on fence for memory barrier.
One possible issue would be for performance on weekly ordered architecture. I don't have experience on theses ones so I am not sure, but it seems that atomic operations are more expansive. How is it in reality? ( like on ARM for example)

2. A step is divided in two methods. The master, and the slaves.

The master function ( named step_multithread_master() here ) distribute and manage work made by the "slaves" ( step_multithread_slave() ).

Basically, the user clone a ref to the World struct between thread (with Arc for example), the main thread call the master function and the others call the slave one. In order to work with safe Rust, it need to entirely rely on interior mutability in order to safely share World between trade (With RwLock and/or Atomic like said upper).

Master and slaves communicate through MultithreadStep struct, and each step has his own. The struct is still very basic and can be improved (with Barrier instead of constantly loading atomic values in a loop for example)

nphysics itself doesn't manage threads.

3. Example in Testbed3d

Testbed3d has been changed to support multithreading with the possibility to choose the number of threads with set_thread_number(). If it's 0, then the original step() method is called.

Things That need to be done :
1. Use exclusively interior mutability in World with RwLock/Atomic

For the moment, only Bodyset has been rewritten. Because of that, unsafe is temporary used in testbed3d to make multithreading work.

2. Complete master and slave method

Only update_kinematics() and update_dynamics() have been done.

3. Reorganize step in smaller step ?

comment

4. Rebase on top of CCD ?

Reading the blog of rustsim, you want to implement multithreading after ccd, so I can rebase it on top  of the ccd branch if you want.

5. Make ncollide multithreaded

One possibility is to make the master/slave system identical in ncollide. This way, we can call the slave and master methods of ncollide in the respective methods of nphysics

6. Other suggestions ?

If you have other design ideas ? Suggestions ? Remark ?

Hi @psincf! Thank you for trying to add multithreading and sorry, I've not had the time to review your PR yet in details. Hopefully I will have some time to look at it in detail within the next few weeks.

@sebcrozet Thanks for taking the time to reply! And no worries, there is no hurry :)

This PR seems no longer relevant, and is now really different from the actual master branch. Also I think that the design choice wasn't good.
I think it's better to close it, and let someone make a better proposal


RuntimeError: CUDA out of memory.

When I tried to train the RESIDE-6k, I met some problems.
"python train.py --model dehazeformer-b --dataset RESIDE-6k --exp reside6k"
/usr/local/lib/python3.7/dist-packages/torch/functional.py:568: UserWarning: torch.meshgrid: in an upcoming release, it will be required to pass the indexing argument. (Triggered internally at  ../aten/src/ATen/native/TensorShape.cpp:2228.)
return _VF.meshgrid(tensors, **kwargs)  # type: ignore[attr-defined]
/usr/local/lib/python3.7/dist-packages/torch/utils/data/dataloader.py:490: UserWarning: This DataLoader will create 16 worker processes in total. Our suggested max number of worker in current system is 4, which is smaller than what this DataLoader is going to create. Please be aware that excessive worker creation might get DataLoader running slow or even freeze, lower the worker number to avoid potential slowness/freeze if necessary.
cpuset_checked))
==> Start training, current model name: dehazeformer-b
0% 0/1001 [00:04<?, ?it/s]
Traceback (most recent call last):
File "train.py", line 127, in
loss = train(train_loader, network, criterion, optimizer, scaler)
File "train.py", line 44, in train
output = network(source_img)
File "/usr/local/lib/python3.7/dist-packages/torch/nn/modules/module.py", line 1110, in _call_impl
return forward_call(*input, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/torch/nn/parallel/data_parallel.py", line 166, in forward
return self.module(*inputs[0], **kwargs[0])
File "/usr/local/lib/python3.7/dist-packages/torch/nn/modules/module.py", line 1110, in _call_impl
return forward_call(*input, **kwargs)
File "/content/drive/MyDrive/DehazeFormer-main/models/dehazeformer.py", line 486, in forward
feat = self.forward_features(x)
File "/content/drive/MyDrive/DehazeFormer-main/models/dehazeformer.py", line 466, in forward_features
x = self.layer2(x)
File "/usr/local/lib/python3.7/dist-packages/torch/nn/modules/module.py", line 1110, in _call_impl
return forward_call(*input, **kwargs)
File "/content/drive/MyDrive/DehazeFormer-main/models/dehazeformer.py", line 308, in forward
x = blk(x)
File "/usr/local/lib/python3.7/dist-packages/torch/nn/modules/module.py", line 1110, in _call_impl
return forward_call(*input, **kwargs)
File "/content/drive/MyDrive/DehazeFormer-main/models/dehazeformer.py", line 266, in forward
x = identity + x
RuntimeError: CUDA out of memory. Tried to allocate 24.00 MiB (GPU 0; 14.76 GiB total capacity; 12.17 GiB already allocated; 10.75 MiB free; 12.29 GiB reserved in total by PyTorch) If reserved memory is >> allocated memory try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF
I have tried to reduce the batch size to 4, however, it is stuck at
"==> Start training, current model name: dehazeformer-b
0% 0/1001 [00:04<?, ?it/s]"
Somebody can help me? It will be appreciated!

what is your GPU?
My guess is that your GPU is not powerful enough.
DehazeFormer-B with batch size 4 may takes 8 days to train for one RTX 2080Ti, so about 12min for one epoch.

When changing the batch size to 4, it works. However, it is too slow. A epoch training need more than one hour.
I train on Google Colab and use Tesla T4 GPU.

Is there a faster way to optimize?

I have not used TESLA T4, it seems to be a low-power GPU with weaker performance than RTX 2080Ti (Turing, 75W, 8.1TFLOPS).
As far as the information is available now, I think it is likely that the performance of the hardware is insufficient.
However, 1h13min for each epoch still abnormal (maybe 30min is ok).
The memory of T4 is 16GB, is your GPU damaged?

UserWarning: This DataLoader will create 16 worker processes in total. Our suggested max number of worker in current system is 4, which is smaller than what this DataLoader is going to create. Please be aware that excessive worker creation might get DataLoader running slow or even freeze, lower the worker number to avoid potential slowness/freeze if necessary.

I see this.
You may decrease the num_worker intrain.py (16 -> 4 or less)
parser.add_argument('--num_workers', default=4, type=int, help='number of workers')

UserWarning: This DataLoader will create 16 worker processes in total. Our suggested max number of worker in current system is 4, which is smaller than what this DataLoader is going to create. Please be aware that excessive worker creation might get DataLoader running slow or even freeze, lower the worker number to avoid potential slowness/freeze if necessary.

I see this.
It seems that Colab only provides very weak CPU power (4 threads).
You may decrease the num_worker in train.py (16 -> 4 or less)
parser.add_argument('--num_workers', default=4, type=int, help='number of workers')

Thanks!


Mossy: Set link width by distance does not work

Still not resolved

Still  not resolved

See https://github.com/CDCgov/MicrobeTrace/issues/887


Use CSI TokenRequest for obtaining service account tokens

Other providers for the Secrets Store CSI driver leverage the CSI driver's (not the provider's) ability to obtain service account tokens for pods that use that CSI driver (see here). This way, the providers nor the driver need the create serviceaccounts/token role.
Code in question:
https://github.com/aws/secrets-store-csi-driver-provider-aws/blob/b8df4953967406978a6199ab5321ee2308a387a7/auth/auth.go#L49-L62
Examples of this from other providers:
https://github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp/blob/main/auth/auth.go#L187-L198
https://github.com/Azure/secrets-store-csi-driver-provider-azure/blob/41b07df322b82a56915ba63abb56c16c37730d33/pkg/auth/auth.go#L304-L327
Without this, the AWS provider will continue to be over-privileged.

Thank you @dronenb, we've noted this as a feature request.


GBStudio gives me an error saving music

Describe the bug
When I try to save music, in some instances it will give me an error (HUGETracker)
To Reproduce
Go to music editor
Add some music notes
Try to save
Then it will give you an error
Expected behavior
Error: EPERM: operation not permitted, rename 'C:/Users/(name)/Google Drive/bit/Revision 3 (Glitchy Ammo)/assets/music/song_template 1.uge.new' -> 'C:/Users/(name)/Google Drive/bit/Revision 3 (Glitchy Ammo)/assets/music/song_template 1.uge'
at Object.renameSync (fs.js:643:3)
at file:///C:/Users/(name)/AppData/Local/gb_studio/app-3.0.0/resources/app.asar/.webpack/renderer/main_window/index.js:41851:18
at file:///C:/Users/(name)/AppData/Local/gb_studio/app-3.0.0/resources/app.asar/.webpack/renderer/main_window/index.js:41796:70
at file:///C:/Users/(name)/AppData/Local/gb_studio/app-3.0.0/resources/app.asar/.webpack/renderer/main_window/index.js:14505:14
at FSReqCallback.oncomplete (fs.js:146:23)
Platform

OS: Windows 10
App version 3.0.0

I will wrote here as well - this hugetracker has some problems, doesn't work (as it should).
Example: SAVE tool button - doesn'y work.
To save a music you need to choose a new track (music), so there will be some window asking if you want to save your progress.
Platform:

OS: Windows 10 Pro (64)
App version 3.0.0

Please confirm if this is still happening with version 3.0.1 and close the issue if it's been resolved. Thanks!

Please confirm if this is still happening with version 3.0.1 and close the issue if it's been resolved. Thanks!

Can confirm, it works now.

Seems that 3.0.1fix few problems (save button works fine thank you!), but there are still problems with the "music editor".
As for now I won't post a new issue, only will put here few things as a suggestion @pau-tomas
Example:
Tempo. Usually it is set to "6", if you will change it (example 20), it will not do anything.
You have to SAVE the song, pick different one, and get back to your song.

THIS way TEMPO will work.
Seems like problem with "song refreshing" or something.

Other suggestions (if no one thought about them yet):

Is it possible to make the [+] new music to have some sort of a window/wizard or something that will ask the "name of the song" and it will create a file like that? So users do not need to go to project folder, and rename the sample song template all the time :D
It doesn't need to be a window/wizard - but it would be nice for the user to be able to change the file name from the GBS, and not bother to go to the project folders for renaming the samples each time.

if there is [+] for making a new music, add [-] for deleting a music, maybe COPY/PASTE would also be nice

tool bar - missing stuff like, for example:

STOP; it will stop playing the song, and it will go back to start (as in any music player it works)
how about COPY,PASTE,DELETE menu for the patterns (and other stuff as well... em SONGS)?


REST API serves configuration inefficiently

Describe the bug
I think the configuration REST endpoint  is inefficient.
It was created for a single use case, back in 2020. To pass the Google Analytics key to the front end from the backend. By now there are 17 backend configuration variables exposed via the rest end point
You can only get one variable per request at the moment, the findAll method is not implemented. A separate call is needed for each config you want, this creates overhead work and uses resources.
The RSS component, which is embedded by the way in the Pagination component makes at least two requests for metadata properties every time it's loaded.
A request for the Google Analytics key is being made on every single load of a page because the front end does not know if GA is enabled and needs to ask the backend every single time (see #9014).
It's not surprising that the new frontend is resource intensive if it is making several requests per page load.
Example
https://sandbox.dspace.org/browse/dateissued, half a sec wasted on GA. There is also another request for a metadata property there, registration.verification.enabled taking 185 ms and 1.1 kb, bandwidth and resources

Solution
To deprecate the configuration REST endpoint as it will have no practical use.
Instead, repurpose the whitelisting functionality for the REST configuration endpoint to expose those properties in the root REST endpoint. /server/api.
The root REST endpoint already fetches config to display so conceptually the root endpoint already exposes configuration properties.
Another reason to use the root endpoint is that, to the best of my understanding, every page load requests that endpoint early in it's build stage. So there is no need for a separate request for config.
it already has:
{
  "dspaceUI" : "https://sandbox.dspace.org/",
  "dspaceName" : "DSpace Sandbox",
  "dspaceServer" : "https://sandbox.dspace.org/server",
  "dspaceVersion" : "DSpace 8.0-SNAPSHOT",
  "type" : "root",
}

why not add
{
  "dspaceUI" : "https://sandbox.dspace.org/",
  "dspaceName" : "DSpace Sandbox",
  "dspaceServer" : "https://sandbox.dspace.org/server",
  "dspaceVersion" : "DSpace 8.0-SNAPSHOT",
  "type" : "root",
  "configuration" : [
    {
       "name": "google.analytics.key",
       "values": [
           "UA-XXXXXX-X"
      ]
   }]
}

This would also resolve the issue of returning 404 or anything at all if a request is made for a non defined property.
Finally, this will increase efficiency by reducing the number of request per page load by anywhere from two to several, depending on the page.

This was discussed in today's DevMtg.  Generally consensus that we need to improve the manner in which we make backend configurations available to the frontend.  All agree this is inefficient & this design doesn't scale well.
Option 1: Some discussion of @J4bbi 's proposal (see "Solution" section of description above) to potentially remove the /api/config/properties endpoint entirely, and move all configurations to the root endpoint /api (as some core configs like dspace.server.url and dspace.ui.url already are shared on root endpoint).

Benefit: This endpoint is already called/used frequently and has some configs embedded.  Using it would be one less endpoint to call.
Downside: this root endpoint /api is called by the UI to simply determine if the backend is responding. That means its response couldn't be cached (like other endpoints).

This also would be a major change to REST Contract, and would break backwards compatibility.

Option 2: Another option is to update the existing endpoint to return all exposed configurations when calling GET /api/config/properties.  (Currently this returns a 405 per the contract)

Benefit: Can still load all the configs at once instead of the current one-by-one approach.

While this changes the REST Contract minimally, it's "backwards compatible".  The one-by-one approach will still work, but this allows for better performance if you load them all at once.  @tdonohue feels this might be allowed in a bug-fix release, as it is arguably fixing a performance bug, and it doesn't break backwards compatibility.

Downside: None, except that we see the potential benefits to "Option 1" (see above) in possibly removing the endpoint. But, that would require much larger code changes.

@abollini, @benbosman and @KevinVdV :  I want to ping all three of you regarding this discussion as you / your teams were all involved with the original design of the /api/config/properties endpoint in https://github.com/DSpace/RestContract/pull/119 and https://github.com/DSpace/DSpace/pull/2762  If you have strong opinions on this possible improvement, I'd love to hear them.  I'd especially like to hear if "Option 2" above seems reasonable to you as I'm seriously considering whether we should do this in a bug fix release to fix the inefficient behavior we are seeing (which can impact performance)

This was discussed again in today's DevMtg.
During that meeting, @abollini pointed out that this might be better resolved via a new /search endpoint like the following:

/api/config/properties/search/exposed  -> return a list of all properties listed in "rest.properties.exposed" in backend configs.

This would be a "canned search" (similar to /communities/search/top) which doesn't allow for any additional parameters.  The behavior would be identical to "Option 2" in my prior comment.
The two main benefits to this search endpoint are as follows:

Completely backwards compatible & could be added easily to 7.6.x.  Requires no changes to current endpoint behavior as this is a new endpoint.
Better describes the purpose of the endpoint, which is to return all "exposed" properties... and not all properties (obviously we are not sharing most configs via this endpoint).  So, it's more self-explanatory.


[WIP] Refactor legacy informer/handler framework

The legacy event driven informer/handler framework has flaws with performance. The regular "informer" object is not multi-threaded and handles events without a queue. The federated "queued informer" sends events to queues where worker threads pull items off and process them. In either informer version, the processing of objects is paused when a new handler is added to the informer. When a new handler is added, all existing objects in the cluster are processed as ADDs. This is extremely slow with UDN and adding new handlers on the fly as UDNs are created. Additionally, the previous model for queued informer did not actually stop the shared informer from enqueuing objects directly. It only paused the workers, which indirectly would eventually stop the shared informer from enqueuing after the channel buffer (size 10) was full.
To address this, the following has been changed:

Classic informer type object is removed, all legacy informers now use a queued informer. These queued informers only use 1 worker thread.
The queued informer now only enqueues events on initial add. The queue size has been adjusted to 10k to account for buffering initial add objects. Can tweak this later.
Locking has been modified. The informer lock is now used to control event flow into the queues. In order to enqueue events from the informer cache, a read lock must be obtained. When a handler is added the informer lock is temporarily taken, to stop the informer cache so that initial objects can be enqueued. Additionally a new handlerMutex is introduced to control adding/removing handlers on an queued informer object.
Since now all objects are enqueued when a handler is added and all handlers will iterate over these already processed objects, a map has been added to the handler. This processedInitialAdd map allows the handler to determine if it has already processed the object or not. In the case of existing handlers, they will ignore adds for objects they already procesed. For newly added handlers, they will ignore updates and deletes received before they have first added the object.

unit tests are broken
testing downstream https://github.com/openshift/ovn-kubernetes/pull/2372


[CI] Bump runner image from Ubuntu 22.04 to 24.04

:mag: Description
Issue References 🔗

This pull request fixes #
Describe Your Solution 🔧

The Ubuntu 24.04 image for Actions is now generally available since Sep 2024 : https://github.blog/changelog/2024-09-25-actions-new-images-and-ubuntu-latest-changes/

Types of changes :bookmark:

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Test Plan 🧪
Behavior Without This Pull Request :coffin:
Behavior With This Pull Request :tada:
Related Unit Tests

Checklist 📝

[ ] This patch was not authored or co-authored using Generative Tooling

Be nice. Be informative.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 0.00%. Comparing base (c6212d0) to head (2d120d1).

Additional details and impacted files
@@          Coverage Diff           @@
##           master   #6739   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files         684     684
  Lines       42281   42281
  Branches     5768    5768
======================================
  Misses      42281   42281

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Thanks, merged to master (1.10.0) .


nixos/mysql: add settings and configFile option

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

cc @thorstenweber83

Not working this configuration:
    ...
    mysqldump = {
      quick;
      max_allowed_packet = "16M";
    };
    ...

error:
syntax error, unexpected ';', at /home/user/works/nixops/deploy/hetzner-all/pve2-test/mysql.nix:57:45

if use package mariadb.server builded withoutClient = true; error:
2mcwly6c6yz8rf70ikz7zjjf278g2gfi-mysql-setup[96574]: /nix/store/2mcwly6c6yz8rf70ikz7zjjf278g2gfi-mysql-setup: line 30: /nix/store/9zjrpl0blyi7rzlzsd2nx4pjjacgpybx-mariadb-server-10.3.22/bin/mysql: No such file or directory

After this update poorly view the current configuration /etc/my.cnf.
Example after:
[client]
default_character_set=utf8mb4

[myisamchk]
key_buffer_size=256M
myisam_sort_buffer_size=256M
read_buffer_size=2M

[mysql]
default_character_set=utf8mb4

[mysqld]
aria_log_dir_path=/var/data/db/mysql/dblogs
aria_sort_buffer_size=2M
back_log=2048
bind_address=<IP_ADDRESS>
binlog_cache_size=2M
binlog_format=ROW
character_set_server=utf8mb4
collation_server=utf8mb4_unicode_ci
datadir=/var/data/db/mysql/db
default_storage_engine=InnoDB
expire_logs_days=7
innodb_autoinc_lock_mode=1
innodb_buffer_pool_dump_at_shutdown=ON
innodb_buffer_pool_load_at_startup=ON
innodb_buffer_pool_size=256M
innodb_compression_algorithm=lz4
innodb_compression_default=ON
innodb_data_file_path=ibdata1:12M:autoextend
innodb_data_home_dir=/var/data/db/mysql/db
innodb_defragment=ON
innodb_file_per_table=ON
innodb_flush_log_at_trx_commit=2
innodb_flush_method=O_DIRECT
innodb_log_buffer_size=16M
innodb_log_checksums=ON
innodb_log_compressed_pages=ON
innodb_log_file_size=128M
innodb_log_group_home_dir=/var/data/db/mysql/dblogs
innodb_max_dirty_pages_pct=5
innodb_sort_buffer_size=2M
innodb_temp_data_file_path=ibtmp1:12M:autoextend
innodb_thread_concurrency=16
interactive_timeout=3600
join_buffer_size=256K
key_buffer_size=16M
key_cache_division_limit=70
log_bin=/var/data/db/mysql/dblogs/mysql_bin.log
log_bin_index=/var/data/db/mysql/dblogs/mysql_bin.index
log_error=/var/data/db/logs/mysql_error.log
log_warnings=2
long_query_time=0.500000
max_allowed_packet=32M
max_binlog_cache_size=4G
max_binlog_size=256M
max_connect_errors=10240
max_connections=1024
max_heap_table_size=1024M
max_user_connections=128
myisam_sort_buffer_size=2M
performance_schema=OFF
plugin-load-add=ha_rocksdb.so;ha_tokudb.so
port=3306
query_cache_limit=2M
query_cache_size=32M
query_cache_type=ON
read_buffer_size=2M
read_rnd_buffer_size=2M
relay_log=/var/data/db/mysql/dblogs/mysql_relay_bin.log
rocksdb_datadir=/var/data/db/mysql/db_rocksdb
secure_auth=ON
skip_name_resolve=ON
slow_query_log=ON
slow_query_log_file=/var/data/db/logs/mysql_slow.log
sort_buffer_size=2M
symbolic_links=OFF
sync_binlog=0
table_definition_cache=4096
table_open_cache=2048
thread_cache_size=64
thread_handling=pool-of-threads
thread_pool_size=8
tmp_table_size=1024M
tokudb_data_dir=/var/data/db/mysql/db_tokudb
tokudb_dir_per_db=ON
tokudb_log_dir=/var/data/db/mysql/dblogs
transaction_isolation=READ-COMMITTED
wait_timeout=3600

[mysqld_safe]
collation_server=utf8mb4_unicode_ci
default_character_set=utf8mb4
log_error=/var/data/db/logs/mysql_error.log
malloc-lib=/nix/store/k78fbnb3167dwiryiv12fanaqp9j575g-jemalloc-4.5.0/lib/libjemalloc.so

Before:
[mysqld]
port = 3306
datadir = /var/data/db/mysql/db

### Paths
datadir = /var/data/db/mysql/db
innodb_data_home_dir = /var/data/db/mysql/db
innodb_log_group_home_dir = /var/data/db/mysql/dblogs
aria_log_dir_path = /var/data/db/mysql/dblogs
innodb_data_file_path = ibdata1:12M:autoextend
innodb_temp_data_file_path = ibtmp1:12M:autoextend

### General options
character_set_server = utf8mb4
collation_server = utf8mb4_unicode_ci
default_storage_engine = InnoDB
innodb_autoinc_lock_mode = 1
innodb_defragment = ON
innodb_compression_algorithm = lz4
innodb_compression_default = ON
innodb_file_per_table = ON
innodb_flush_method = O_DIRECT
innodb_flush_log_at_trx_commit = 2
innodb_max_dirty_pages_pct = 5
innodb_buffer_pool_load_at_startup = ON
innodb_buffer_pool_dump_at_shutdown = ON
performance_schema = OFF
symbolic_links = OFF
transaction_isolation = READ-COMMITTED

### Connections
bind_address = <IP_ADDRESS>
back_log = 2048
max_allowed_packet = 32M
max_connect_errors = 10240
max_connections = 1024
max_user_connections = 128
secure_auth = ON
skip_name_resolve = ON

### Threads
innodb_thread_concurrency = 16
thread_cache_size = 64
thread_handling = pool-of-threads
thread_pool_size = 8

### Timeout
wait_timeout = 3600
interactive_timeout = 3600

### Logs
innodb_log_file_size = 128M
innodb_log_checksums = ON
innodb_log_compressed_pages = ON
innodb_log_buffer_size = 16M
log_error = /var/data/db/logs/mysql_error.log
log_warnings = 2
long_query_time = 0.500000
slow_query_log_file = /var/data/db/logs/mysql_slow.log
slow_query_log = ON

### Binlogs
binlog_format = ROW
expire_logs_days = 7
log_bin = /var/data/db/mysql/dblogs/mysql_bin.log
log_bin_index = /var/data/db/mysql/dblogs/mysql_bin.index
relay_log = /var/data/db/mysql/dblogs/mysql_relay_bin.log
binlog_cache_size = 2M
max_binlog_size = 256M
max_binlog_cache_size = 4G
sync_binlog = 0

### Buffers
aria_sort_buffer_size = 2M
innodb_sort_buffer_size = 2M
myisam_sort_buffer_size = 2M
sort_buffer_size = 2M
join_buffer_size = 256K
key_buffer_size = 16M
read_buffer_size = 2M
read_rnd_buffer_size = 2M
innodb_buffer_pool_size = 256M

### Caches
query_cache_type = ON
query_cache_limit = 2M
query_cache_size = 32M
key_cache_division_limit = 70
table_definition_cache = 4096
table_open_cache = 2048
max_heap_table_size = 1024M
tmp_table_size = 1024M

### zfs
innodb_doublewrite = OFF
innodb_compression_algorithm = none
innodb_compression_default = OFF
innodb_use_atomic_writes = OFF
innodb_use_native_aio = OFF

### zfs, checksums
#aria_page_checksum = OFF
#innodb_checksums = OFF
#innodb_checksum_algorithm = NONE
#innodb_log_checksums = OFF
#binlog_checksum = NONE

### RocksDB
plugin-load-add = ha_rocksdb.so
rocksdb_datadir = /var/data/db/mysql/db_rocksdb

### TokuDB
plugin-load-add = ha_tokudb.so
tokudb_dir_per_db = ON
tokudb_data_dir = /var/data/db/mysql/db_tokudb
tokudb_log_dir = /var/data/db/mysql/dblogs

[client]
default_character_set = utf8mb4

[mysql]
default_character_set = utf8mb4

[mysqld_safe]
default_character_set = utf8mb4
collation_server = utf8mb4_unicode_ci
log_error = /var/data/db/logs/mysql_error.log

### TokuDB
malloc-lib = /nix/store/k78fbnb3167dwiryiv12fanaqp9j575g-jemalloc-4.5.0/lib/libjemalloc.so

[mysqldump]
quick
max_allowed_packet = 16M

[myisamchk]
key_buffer_size = 256M
myisam_sort_buffer_size = 256M
read_buffer_size = 2M

@Izorkin thank you for your feedback and testing! You are always so reliable :smile:

Not working this configuration:
    ...
    mysqldump = {
      quick;
      max_allowed_packet = "16M";
    };
    ...

I'm under the impression this is a shorthand syntax for what should be written as:
mysqldump = {
  quick = true;
  max_allowed_packet = "16M";
};

if use package mariadb.server builded withoutClient = true; error:
2mcwly6c6yz8rf70ikz7zjjf278g2gfi-mysql-setup[96574]: /nix/store/2mcwly6c6yz8rf70ikz7zjjf278g2gfi-mysql-setup: line 30: /nix/store/9zjrpl0blyi7rzlzsd2nx4pjjacgpybx-mariadb-server-10.3.22/bin/mysql: No such file or directory

Can you please provide /nix/store/2mcwly6c6yz8rf70ikz7zjjf278g2gfi-mysql-setup?
@Izorkin it is very true that RFC42 doesn't let you hand craft beautiful configuration files which is disappointing to you. I don't know how to address this. I think you should mention this in https://github.com/NixOS/rfcs/pull/42 for a discussion point. Any comment @Infinisil?

Yeah I guess commenting in config files themselves isn't something supported by this approach, but I think that's rather minor compared to the benefits it gives. It's still possible to have comments in the Nix code at least.

I'm under the impression this is a shorthand syntax for what should be written as:

https://dev.mysql.com/doc/refman/5.7/en/mysqldump.html#option_mysqldump_quick

Can you please provide /nix/store/2mcwly6c6yz8rf70ikz7zjjf278g2gfi-mysql-setup?

#!/nix/store/8gy2bmpz3qawxr3g8hqhfgkf32wb0wfl-bash-4.4-p23/bin/bash -e

# Wait until the MySQL server is available for use
count=0
while [ ! -e /run/mysqld/mysqld.sock ]
do
    if [ $count -eq 30 ]
    then
        echo "Tried 30 times, giving up..."
        exit 1
    fi

    echo "MySQL daemon not yet started. Waiting for 1 second..."
    count=$((count++))
    sleep 1
done

if [ -f /tmp/mysql_init ]
then

# Execute initial script
# using toString to avoid copying the file to nix store if given as path instead of string,
# as it might contain credentials
cat /nix/store/36wz42cljwgx94kba5pgfavrkjw57g61-mysql_init.sql | /nix/store/9zjrpl0blyi7rzlzsd2nx4pjjacgpybx-mariadb-server-10.3.22/bin/mysql -u root -N
    rm /tmp/mysql_init
fi

l /nix/store/9zjrpl0blyi7rzlzsd2nx4pjjacgpybx-mariadb-server-10.3.22/bin/mysql
ls: невозможно получить доступ к '/nix/store/9zjrpl0blyi7rzlzsd2nx4pjjacgpybx-mariadb-server-10.3.22/bin/mysql': No such file or directory

@Izorkin it is very true that RFC42 doesn't let you hand craft beautiful configuration files which is disappointing to you. I don't know how to address this. I think you should mention this in NixOS/rfcs#42 for a discussion point. Any comment @Infinisil?

You can process the block while maintaining the layout of the lines from the configuration?

@Infinisil I just realized I missed something here... any thoughts on how to deal with this? https://dev.mysql.com/doc/refman/8.0/en/option-files.html#option-file-inclusions

https://dev.mysql.com/doc/refman/5.7/en/mysqldump.html#option_mysqldump_quick

services.mysql.settings.mysqldump.quick = true; is compatible with this. If you test you should see this works :+1: I will add this to examples for clarification.

l /nix/store/9zjrpl0blyi7rzlzsd2nx4pjjacgpybx-mariadb-server-10.3.22/bin/mysql
ls: невозможно получить доступ к '/nix/store/9zjrpl0blyi7rzlzsd2nx4pjjacgpybx-mariadb-server-10.3.22/bin/mysql': No such file or directory

This appears to be a bug in master, unrelated to this PR. Can you possibly test and confirm?

You can process the block while maintaining the layout of the lines from the configuration?

I don't think this is possible :disappointed:

This appears to be a bug in master, unrelated to this PR. Can you possibly test and confirm?

Yes, this bug in master
diff --git a/nixos/modules/services/databases/mysql.nix b/nixos/modules/services/databases/mysql.nix
index 8d520b82fb5..d1f06e2b328 100644
--- a/nixos/modules/services/databases/mysql.nix
+++ b/nixos/modules/services/databases/mysql.nix
@@ -398,7 +398,7 @@ in
                         # Execute initial script
                         # using toString to avoid copying the file to nix store if given as path instead of string,
                         # as it might contain credentials
-                        cat ${toString cfg.initialScript} | ${mysql}/bin/mysql -u root -N
+                        cat ${toString cfg.initialScript} | ${mariadb.client}/bin/mysql -u root -N
                       ''}

                     rm /tmp/mysql_init

Only this option will not work with MySQL 5.7 and 8.0.

Only this option will not work with MySQL 5.7 and 8.0.

Thanks for confirming the bug exists in master. If you can file an issue that would be appreciated.

Thanks to @Infinisil I believe this is ready for final testing and merging.

@Infinisil I just realized I missed something here... any thoughts on how to deal with this? https://dev.mysql.com/doc/refman/8.0/en/option-files.html#option-file-inclusions

I realized that include directives really work against the new declarative/merging nature of a settings option, so I resolved this outstanding issue by including a configFile escape hatch.
Does anyone have any other requests before merging this?

@GrahamcOfBorg test mysql


delay the CRM tier check until serviceFeatures data is fetched for in…

…active tabs

Coverage decreased (-0.01%) to 38.392% when pulling c580e5d9a7f783afc43335d08d70fc6c67dec922 on u9520107:rcint-4582 into 3ee90f76acaa71d0447229e16c0a71c9b0527651 on ringcentral:dynamics-1.1.1.


Paket.PowerShell support for Package Manager Console

This is for #874 and is not ready yet to be merged. It is in progress and ready for review. I could use some help solving the async / trace dilemma. PowerShell requires that the tracing be on the same thread and it appears async puts it on another.

I asked around at work about how to get all the messages on the same thread. I was told to look at Async.SwitchContext. There is some good related code already in Utils.fs. Hoping that I can capture SynchronizationContext.Current instead of the ManagedThreadId and use it to put all the messages on the right thread for PowerShell. I'll try it out tonight.

I spent hours on this, this evening, without any luck. I opened up a stackover question:
http://stackoverflow.com/questions/30859885/post-messages-on-async-thread-to-original-thread-in-f

I believe this is ready to go. Logging now works correctly in PowerShell and in Package Manager Console. It displays output as it goes.

I created type EventSink and function processWithLogging to allow the trace messages to be output on the main PowerShell thread, which is required by PowerShell (according to the error messages I get when I don't do so).

The feature is Paket.PowerShell support for Paket Manager Console and to add support I had to refacto Logging to use Trace observable.

cool. thanks

maybe it even fixes the logging issues in paket.vs - you never know ;-)

Did this by any chance changed the exit code behavior? It seems we always get exit code 1 - even on success.

:/ I'll have a look.

I mean it's probably something different, but I have no idea at the moment
On Jun 20, 2015 8:18 PM, "Cameron Taggart"<EMAIL_ADDRESS>wrote:

:/ I'll have a look.
—
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/pull/875#issuecomment-113799462.

Looking at the changes I made to Program.fs, I think I see this issue.

@forki Just to be clear, the exit code wasn't broken. What was broken was the exception not being logged.

I tried to update Paket.VisualStudio and got:

What do I need to do?

Paket.Logging.event is public. event.Publish can be subscibed to.
On Jun 23, 2015 1:32 AM, "Steffen Forkmann"<EMAIL_ADDRESS>wrote:

I tried to update Paket.VisualStudio and got:
[image: image]
https://cloud.githubusercontent.com/assets/57396/8301978/1e504036-1993-11e5-88bf-60f4f1eb7fdc.png
What do I need to do?
—
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/pull/875#issuecomment-114406051.

I don't get it working. Could you please help me a bit? thx

@forki Can you change event to use DelegateEvent to use += notation in C#? See https://github.com/fsprojects/VisualFSharpPowerTools/blob/40bd0f678925a4e64c60d09014660e1f03c9c1e0/src/FSharpVSPowerTools.Logic/ShellEventListener.fs#L28

https://github.com/fsprojects/Paket.VisualStudio/commit/8bb932a16699c84786cc93d8bdf6395f1705f3b4 does this look OK?


Fix the location bar not updating with the new page url in some cases, regressed by ae29930

Fixes https://github.com/mozilla/tofino/issues/1154
Signed-off-by: Victor Porof<EMAIL_ADDRESS>

Coverage decreased (-0.01%) to 33.327% when pulling a8fb9e13fd56a247c80616b1b7bb869128839953 on victorporof:urlbar-regression into a1bf0e8cf2a94e886d2f7a4b0ebc2d54dd758867 on mozilla:master.

Coverage decreased (-0.006%) to 33.333% when pulling a8fb9e13fd56a247c80616b1b7bb869128839953 on victorporof:urlbar-regression into a1bf0e8cf2a94e886d2f7a4b0ebc2d54dd758867 on mozilla:master.


Occasionally resets of brightness.

I'm using the REST-Api to turn my LEDs on and off. To toggle on i'm calling "/rainbow" and for off "/off".
At some random times the strip is getting powered and displays rainbow mode.

Sometimes at random times the strip is turning on again without me calling the api.

HI @davidblumer ,
these ransom reboot often happen because of not 100% stable power supplies. The ESP is quite sensitive to power supply. What is your setup (how many LEDs, power supply, board, ...)?
Have also a look here: https://learn.adafruit.com/adafruit-neopixel-uberguide/powering-neopixels
Regards
Tobias

I bought a new power supply 5V 8A - same one i use for my ambilight without any problems. Reboots still happen randomly. I got 3 meters 2812b / 60 - so ~ 180 LEDs. My board is a ESP8266 NodeMCU.

I also have random reboots on every single unit I use with McLighting, or random drops back to solid blue lights until I reset the device. It is still connected to wifi when the latter happens.
My power supplies are rock solid, tested on an oscilloscope, metered for output to verify 5v, etc. In one case, I'm running 48 LEDs, and still encountering the issue on a 4 amp power supply.


Snowflake query tag

resolves #1030

Description
Add the ability to set snowflake query tags upon creation of a connection or at the start of a materialization. For query tags used during materialization the session parameter that controls query tags will be returned to whatever value it was before the materialization began
Not sure what/how to test for this addition.

Checklist

[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[ ] This PR includes tests, or tests are not required/relevant for this PR
[x] I have updated the CHANGELOG.md and added information about my change to the "dbt next" section.

It would also be great if you could add tests, though if tests aren't really reasonable here I understand that. Does snowflake have an API or something we could query that shows this stuff?

Snowflakes query tags are session level parameters. They can be viewed by running the sql SHOW PARAMETERS [ LIKE '<pattern>' ][ IN { SESSION | ACCOUNT | ... }]. The query_tag parameter does not appear to be accessible by introspecting the snowflake connection object and I am not aware of any way to find session parameters for arbitrary open sessions. So any kind of testing would require running the SQL in the get_current_query_tag macro from inside the session at appropriate times or looking at the snowflake query_history view, which has some obnoxious lag. I think given the mentioned complications testing for this feature might be too difficult.

One thing I would like to bring up: On errors, it seems to me that this will result in the query tag getting "stuck", because the unset_query_tag never runs, right? Is that a big problem? If it is, I think we could add a dbt feature to make cleanup more feasible (some sort of adapter-level pre/post model hooks, or a finally equivalent in jinja, or something similar).

In my view query_tags are primarily a tacking and observability tool, not a functional part of the transformation process. To my knowledge they cannot impact the running of SQL against snowflake. So "getting stuck" with an incorrect query_tag will not stop dbt from running properly.
Also I am not familiar enough with how dbt handles SQL failures in the middle of runs with multiple materializations. Will connections/sessions be reused for subsequent models if one model fails?

The stakes here feel pretty low. I haven't used query tags in Snowflake, but I could imagine them being most compelling as a mechanism for longitudinal analysis of models across production runs where builds are almost always successful, e.g. to measure performance timing. If I needed to debug a run with failed models from within Snowflake's query history, I'd more likely look to the query-comment or raw SQL as a starting point.
That said, I agree that we should have a construct for end-of-materialization cleanup steps that aren't precluded by model SQL errors.

Cool, let's just add this as-is then. We can add support for proper cleanups at a later date. I'm going to test it out locally manually before I kick off tests - I will try to get to this today, but it may be next week.

This looks ready to go to me! I've merged the changelog updates and once the tests pass I'll merge this in for 0.18.0. Thanks for your contribution, @DrMcTaco!


This seems to work decently for all boards except the two boards with the worst outages (BOARD_ID=0 and 5). For these boards, the flats have a lot of negative pixels that get set to nans. This will be addressed in a subsequent PR.
Also the default timeout for astrometry was 900 sec. That is changed to a more reasonable 45 sec., as WINTER astrometry usually solves within this time or fails always.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 5 (60.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.004%) to 81.99%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

mirar/pipelines/winter/load_winter_image.py
2
4
50.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.004%

Covered Lines:
8695

Relevant Lines:
10605

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

3 of 5 (60.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.004%) to 81.99%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

mirar/pipelines/winter/load_winter_image.py
2
4
50.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.004%

Covered Lines:
8695

Relevant Lines:
10605

💛  - Coveralls


Resynchronize data portal environments, api definitions, db schema management

Various bits of the data portal have drifted apart over time:

DB migrations that work in dev fail in staging and cannot be run at all in prod
There's a required table in present in dev but mentioned nowhere in any alembic migrations
The API definition and the actual API responses are related, but like cousins not twins
The API doesn't distinguish between required and optional fields, so the frontend appears to be treating everything as required.
etc.

We have a little tech debt to address so we can smoothly promote, deploy, and migrate.

Closed by #564 #566 and #567


override the emmet html template

Would like to be able to change the default html template that is generated by emmet.
! generates a basic doc, but it would be great if we could personalize this, and override it to add more tags such as link and script tags.
existing:
"doc": "html[lang=${lang}]>(head>meta[charset=${charset}]+meta:vp+title{${1:Document}})+body",
my personalized one:
"doc": "html[lang=${lang}]>(head>meta[charset=${charset}]+meta:vp+title{${1:Document}})+link:css+script:src+body",

See https://code.visualstudio.com/docs/editor/emmet#_using-custom-emmet-snippets.
The snippet files allows you to add more tenplates, but also to replace existing ones (reload might be needed after making changes to the snippet file)

Thanks for this. Is there a trick to overriding an exiting emmet with another emmet? When I do it's no longer parsed as an emmet but regular text.
The body is the existing emmet for "doc", I'm simply overriding it but it is no longer expanding out.
"Extended html template": {
		"prefix": "doc",
		"body": [
			"html[lang=${lang}]>(head>meta[charset=${charset}]+meta:vp+title{${1:Document}})+body",
		],
		"description": "Better html template"
	}

This looks like a regular user snippet.
Did you try the emmet snippets as described in the link? Here are the steps I tested this with

in your workspace, create a folder emmet
put inside a file called snippets.json

{
  "html": {
    "snippets": {
      "doc": "html[lang=${lang}]>(head>meta[charset=${charset}]+meta:vp+title{${1:Document}})+body"
    }
  }
}

in the workspace settings (Command: Preferences: Open workspace settings (JSON)) add

{
    "emmet.extensionsPath": "./emmet"
}

reload the vscode window (Command: Developer: Reload Window)
type doc in html file

Yes, I was trying to make it a global emmet replacement... The change you suggest seems to be a workspace specific change.


Upgrade Solr/Lucene and Elasticsearch

Problem description
Giving it another try.... ElasticSearch and Apache Lucene/Solr could be upgraded to newer versions.
There is an change / issue with the highlighter in Solr 8.5, so some code changes could be required.
Preferred solution
Upgrade to latest Lucene and Solr 8.x versions +ES 7.x
Unfortunately this might be slightly too ambitious, since ES 7.16 removes (geo) shapebuilder to another (legacy) package, which isn't readily available from maven.
So use ES 7.15.2 and Lucene/Solr 8.9.0
Are you interested in contributing a solution yourself?
Yes
Alternatives you've considered
No response
Anything else?
See also discussion in #2392
Automated Dash-license request for
Solr 8.9.0

[x] solr-core (61353)
[x] solr-solrj (61341)

For some unknown reason also a dependency

[x] solr-solrj (61344) 8.11.2

Apache Curator (Solr sub-dependency) 2.13.0

[x] curator-framework (6162)
[x] curator-recipes (6163)
[x] curator-client (6164)

Lucene 8.9.0:

[x] lucene-suggest (6134)
[x] lucene-grouping (6135)
[x] lucene-memory (6136)
[x] lucene-highlighter (6137)
[x] lucene-spatial-extras (6138)
[x] lucene-expressions (6139)
[x] lucene-spatial3d (6140)
[x] lucene-analyzers-nori (6142)
[x] lucene-codecs (6143)
[x] lucene-join (6145)
[x] lucene-analyzers-phonetic  (6146)
[x] lucene-analyzers-kuromoji (6147)
[x] lucene-test-framework (6148)
[x] lucene-queries (6149)
[x] lucene-classification (6150)
[x] lucene-backward-codecs (6151)
[x] lucene-analyzers-common (6152)
[x] lucene-queryparser  (6154)
[x] lucene-core (6155)
[x] lucene-sandbox (6156)
[x] lucene-misc (6157)

Elasticsearch 7.15.2:

[ ] elasticsearch (6158)
[x] additional jars (6398 - 6408 and 6410 - 6414)
[ ] additional jars (7315, 7317, 73818)

Maven plugin

[ ] elasticsearch-maven-plugin 6.26 (7316)

~elasticsearch-cluster-runner (6409)~

As a reminder, something seems to have changed in the Solr Highlighter (8.5 and up): the org.eclipse.rdf4j.sail.solr.SolrIndex query() method does seem to get the correct number of search results in 8.5 and up, but no highlight results (which are retrieved separately) whatsoever, and as a result the tests in the SolrSailIndexedPropertiesTest fail

The Solr DefaultHighlighter is processing fields differently in 8.5, an option would be to use the UnifiedHighlighter, but this fails the testUnionQuery...

Although RDF4J is probably not at risk, upgrading to Lucene / Solr 8.11.2 would get rid of warnings about log4j 1.2 and 2.14 CVEs (since the newer libraries will use the log4j v2.17.1 instead)
Using 8.11.2, Solr compliance test fails on  AbstractLuceneSailTest.testSnippetLimitedToPredicate()
Also, solr/cores/embedded/conf/solrconfig.xml could be changed to run the Solr tests in memory
	<directoryFactory class="org.apache.solr.core.RAMDirectoryFactory"/>
	<indexConfig>
		<lockType>single</lockType>
	</indexConfig>

(otherwise using 8.11 seems to break tests using disk storage: write.lock file issue, maybe due to multiple threads or race condition...)

Be slightly less ambitious, since ES 7.16 removes (geo) shapebuilder to another (legacy) package, which isn't readily available from maven.
So using Solr/Lucene 8.9 and ES 7.15.2 as a compromise
Assuming we move to Solr/Lucene 9.x and ES 8.x in RDF4J 5.0.0 (which may have breaking changes)

How is the licensing compatibility for ES now a days?

I've filed an automated request for 1 ES dependency ( https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/6158.) so let's see if/how it works out ...

Could be a non-issue, since it's a more relaxed "works-with" dependency (but looks like dash-tool does not support / is not mean to handle "works-with", see https://github.com/eclipse/dash-licenses/issues/13) and we don't distribute elasticsearch jars
(we do distribute lucene / solr jars, but they are approved so no problem there)

We had a constructive meeting with Eclipse, they are looking into the final nitty-gritty details but basically they are OK with our setup ("works-with", not required, no distribution of ES-jars).
It would, however, be a good idea to clearly mention on our website / in the javadocs that users should check the ES-license if they want to use ES, especially in a service-offering model.

Created a series of IP requests (using dash-license) for the various ES client jar files, most of them are now under investigation

Some discussion on ElasticSearch runner, a component used for testing (very convenient for starting an ES server, running tests and stopping/removing the test-ES)
See https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/6409

I think we should go with Testcontainers.
https://www.testcontainers.org/modules/elasticsearch/

Sounds good, I'm using testcontainers for other projects, and it works as advertised...

Actually the maven elasticearch plugin works just fine with openjdk-19 on my debian machine, but for some reason ES fails to start on the github machine (action with ubuntu-latest, not sure which JDK-brand) :-/

In the series "it works fine on my machine", apparently this issue makes it somewhat tricky to repeat that on the github CI machine: https://github.com/elastic/elasticsearch/issues/49124

Finally got it to work, so now waiting for the last CQ requests

Still no updates on the last CQ requests, I've added a few friendly reminders to the comments to the Eclipse IP gitlab issues...

Slowly inching towards approval, 2 more dependencies have been approved, 3 to go

Al approved, but we'll need to double-check our documentation to clearly mention that (re)users really must check the ES conditions / FAQ in the (unlikely ?) case they provide an as-a-service solution using ES Sail/Search (also see comments at the bottom of https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/7318)


Include example with traditional state container (Sans Redux/Mobx?)

I have been working through the tutorials of Next JS via learnnextjs.com, and I have a better understanding of the framework now thanks to that, in addition to the documentation provided on the official repo right here - much appreciated!
I'm somewhat still fairly new to using React, and I have a grasp on container/presentation components. The apps I have written typically do not need the complexity that Redux and Mobx bring to the table. I want to keep the architecture fairly lean and intuitive for my team to jump into - and introducing an alternative state container later on if I need it.
The way I set up my apps is as follows:
AppContainer - initializes a state object. Pretty much all of my application's state resides here with the exception of local state for smaller components (form validation etc). State changes are also set here via functions, and then tunneled to different routes via React Router. I'm happy with this architectural pattern, and was just wondering how Next JS handles this pattern? The current examples show how to manage state via Mobx, but a more "pure" example would be beneficial to me, and hopefully some others too!
Thanks

@fdidron might be able to answer this. Feel free to join https://zeit.chat


Apex website

"As a developer, I want to easily learn more about Apex on an easy resourceful webpage."
One page site (apex.github.io) which shows more info about what Apex does, which languages it supports, and how it works.
Let me know your thoughts guys.

So basically, readme but on a subpage? Can't see the real plus of it

I think we'll eventually have something, but it'll most likely be powered by the wiki. We just need some more docs there I think, first at least :D

Alright TJ, sounds good! :+1:

+1 for Wiki-focused docs. Github repo with well-organized readme and wiki pages is self-explanatory in most cases. apex wiki command can potentially be a great resource for learning too.

I'd much rather have the documentation in a git repo than in a github wiki. This information can still be pulled by the client.

@lpil Could you share your insights on why you think git repo is better than wiki? Why do you think we should consider making this switch?

I've just discovered that github wikis are repos.
https://github.com/apex/apex.wiki.git
I still prefer using a regular repo as it is easier to view the contents, make pull requests, etc. A nice interface for reading can be created with Jekyll or similar static site generator.

In my experience it gets a little annoying having both in the same repo, if anything I'd rather have apex/docs or similar

I'll move them over to apex/docs tonight and start a little iste

I was suggesting a different repo rather than the same one :)

Thanks TJ! :)

Main reason I like docs in the repo is that the docs are versioned. As long as you can find docs for previous releases though, I've never had too much of a preference. At the very least just make sure that the docs on master aren't ahead of the latest release, that's the worst!

true true, we could do that in another repo but it would be harder to enforce

almost ready, I'll move the docs right away and finish it up sometime soon

Thanks!

No domain yet but it's a start: https://github.com/apex/web

Looking really nice!


Start looking at Travis configuration

Import first version of travis conf file

looks like an easy fix : ERROR! You must specify a playbook file to run


Include backport branches in publishing

Realized we'll need to update sbt-slamdata's publishAndTag similarly. Will include that here once available.

@drostron when you've pushed everything you need to, just let me know, and I'll take another look!

@alissapajer Ready for another look


landscaper resources can't be deleted

How to categorize this issue?

/area robustness
/kind bug
/priority 3
What happened:
There are several situations that will lead to landscaper resources that can't be deleted anymore.
This list aims to collect situations/constellation which lead to non-deletable landscaper resources (installations, executions, deployitems).

Installation references a non-existing component descriptor. The installation will fail and can't be delete afterwards.
A Helm deployment contains a namespace. In some instances the helm deployment can't be deleted anymore.
This could possibly also happen with other resources.

{"level":"error","ts":"2021-09-09T08:50:58.140Z","logger":"setup.deployer.HelmDeployer.controller.deployitem","msg":"Reconciler error","reconciler group":"landscaper.gardener.cloud","reconciler kind":"DeployItem","name":"landscaper-rbac-pg5sr","namespace":"default","error":"waiting for the deletion of \"ls-system/ls-system(Namespace)\" to be completed"}

A subinstallation imports a target that is created by a different subinstallation. It seems that the dependeny detection is not correctly working for target imports. This leads to a situation where both subinstallations are executed simultaneously and result in an error. Deleting the installation fails afterwards.
When the target for a deployitem is no longer reachable/accessible, the deployitem can't be deleted and will be stuck.

What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

Landscaper version: 0.12.0
Kubernetes version (use kubectl version): N/A
Others:

Installation references a non-existing component descriptor. The installation will fail and can't be delete afterwards.

this likely is the same category of issues as https://github.com/gardener/landscaper/issues/230

Installation references a non-existing component descriptor. The installation will fail and can't be delete afterwards.

Deletion fixed.

A Helm deployment contains a namespace. In some instances the helm deployment can't be deleted anymore.
This could possibly also happen with other resources.

{"level":"error","ts":"2021-09-09T08:50:58.140Z","logger":"setup.deployer.HelmDeployer.controller.deployitem","msg":"Reconciler error","reconciler group":"landscaper.gardener.cloud","reconciler kind":"DeployItem","name":"landscaper-rbac-pg5sr","namespace":"default","error":"waiting for the deletion of \"ls-system/ls-system(Namespace)\" to be completed"}

Fixed.

A subinstallation imports a target that is created by a different subinstallation. It seems that the dependeny detection is not correctly working for target imports. This leads to a situation where both subinstallations are executed simultaneously and result in an error. Deleting the installation fails afterwards.

Fixed.

When the target for a deployitem is no longer reachable/accessible, the deployitem can't be deleted and will be stuck.

Still open, but this is not easy, e.g. if the cluster is not reachable...

Open:

When the target for a deploy item is no longer reachable/accessible, the deploy item can't be deleted and will be stuck.

Still open, but this is not easy, e.g. if the cluster is not reachable...
We should at least provide a simple solution for some cleanup. Thereby we should consider that it is not only about the complete deletion of an installation with one deploy item but also about installations with sub-installations and many deploy items. Thereby the deletion of the root installation must be considered as well as the deletion of only some deploy items.
Two possible solutions:

If the root installation gets a force-delete annotation, this is propagated to all deploy items and every deploy item where the deletion has failed is deleted without deleting the resources on the target cluster. Afterwards the force-delete annotations must have been removed from all landscaper resources belonging to the root installation.
We just add a simple command to the landscaper-cli just to delete all relevant deploy items with respect to a root installation without triggering some deinstallation on the target cluster. We must check if the current landscaper implementation continues afterwards the processing of the root installation and should come to a success state if no other problems occurs.

Closing this, as a similar issue is now on the bew backlog project.


AnimationBehavior.SetSourceUri does not work with relative path

When you call AnimationBehavior.SetSourceUri with a relative GIF file URI (i.e. file name only), the image appears blank, even if UriKind.Relative or UriKind.RelativeOrAbsolute is specified in the Uri instance.

This is not a question about the samples in this repo. You can open a support case with our Developer Support team who can help with the problem you are experiencing. Please use these steps below for further help:

Visit http://aka.ms/storesupport and sign-in with your Microsoft account
Under the “App Development” section choose "Windows 10 universal app development", then choose the appropriate problem type and category to get engaged through a formal support channel.


Error with sbt-jshint

When sbt-jshint plugin is added, jshint task fails with the following error:
[info] Fast optimizing /home/guersam/study/play-with-scalajs-example/example-client/target/scala-2.11/exampleclient-fastopt.js
[info] JavaScript linting on 2 source(s)
[trace] Stack trace suppressed: run last exampleServer/web-assets:jshint for the full output.
[error] (exampleServer/web-assets:jshint) No mapping for /home/guersam/study/play-with-scalajs-example/example-client/target/scala-2.11/exampleclient-fastopt.js
[error] application -

! @6l7obo21d - Internal server error, for (GET) [/] ->

play.PlayExceptions$UnexpectedException: Unexpected exception[RuntimeException: No mapping for /home/guersam/study/play-with-scalajs-example/example-client/target/scala-2.11/exampleclient-fastopt.js]
	at play.PlayReloader$$anon$1$$anonfun$play$PlayReloader$$anon$$taskFailureHandler$1.apply(PlayReloader.scala:237) ~[na:na]
	at play.PlayReloader$$anon$1$$anonfun$play$PlayReloader$$anon$$taskFailureHandler$1.apply(PlayReloader.scala:230) ~[na:na]
	at scala.Option.map(Option.scala:145) ~[scala-library-2.11.5.jar:na]
	at play.PlayReloader$$anon$1.play$PlayReloader$$anon$$taskFailureHandler(PlayReloader.scala:230) ~[na:na]
	at play.PlayReloader$$anon$1$$anonfun$reload$2.apply(PlayReloader.scala:90) ~[na:na]
Caused by: java.lang.RuntimeException: No mapping for /home/guersam/study/play-with-scalajs-example/example-client/target/scala-2.11/exampleclient-fastopt.js
	at scala.sys.package$.error(package.scala:27) ~[scala-library-2.11.5.jar:na]
	at sbt.Mapper$$anonfun$fail$1.apply(PathMapper.scala:37) ~[na:na]
	at sbt.Mapper$$anonfun$fail$1.apply(PathMapper.scala:37) ~[na:na]
	at sbt.Alternatives$$anon$1$$anonfun$$bar$1$$anonfun$apply$3.apply(PathMapper.scala:117) ~[na:na]
	at sbt.Alternatives$$anon$1$$anonfun$$bar$1$$anonfun$apply$3.apply(PathMapper.scala:117) ~[na:na]

Although it's unusual to have jshint with scala-js, It's annoying when it happens.

Hi @guersam,
You can use excludeFilter in JshintKeys.jshint := "*-fastopt.js" || "*-launcher.js" in the Play settings. JSHint won't be run on Scala.js output and you won't get that error message.

Hi @guersam, if you upgrade to sbt-play-scalajs v0.2.2, the Scala.js output will not be used by jshint anymore. So you won't get this error anymore and you don't need to use excludeFilter.

Awesome, thanks a lot!


Migrating from Thucydides

Add migration guide. Write about tricks/hints/problems.

I guess I will not fix this one


Update play_sudoku.py

Fixed documentation in inside_reject() function for better accuracy. Changed "accept button" to "reject button" in docstring to match the actual function purpose.
Changes:

Corrected documentation inaccuracy in inside_reject() function
Improved consistency between function name and its documentation
Documentation-only change, no functional changes

@uncomputable
Changed the docstring on line 82

@uncomputable  I will create a new clean PR instead of removing the old commit. It will be easier and cleaner this way.

@donatik27 Thanks. I encourage you to look into interactive rebases. They let you clean up existing branches and PRs.


ghci config path still not visible

After upgrading to 0.6.1, the ghci path still does not show up in the Tidal package settings. This is on Windows 8.1, Atom 0.182.0,  I see no issue with the package code as-is, so I don't know what the problem is. I'm able to add/modify settings in other packages without issue. Curious if anyone besides me cannot see the ghci setting either.

not sure it's an windows only problem? I don't have a window machine around :( Can you reproduce on other window machine?

If you boot Tidal in Atom first, then the config settings will show. The package has to be "activated" first before the settings show up. This is a known bug in Atom, see https://discuss.atom.io/t/configuration-vars-dont-show-up/14480 and https://github.com/atom/settings-view/issues/356.


Swap os.sep.join to os.path.join

From the documentation:
os.sep

    The character used by the operating system to separate pathname components. This is '/' for POSIX and '\\' for Windows. Note that knowing this is not sufficient to be able to parse or concatenate pathnames — use os.path.split() and os.path.join() — but it is occasionally useful. Also available via os.path.

Example of one place where this occurs: https://github.com/IATI/iati.core/blob/69387f84161f4c724fb9fb4b114c1d83bfe80008/iati/core/resources.py#L29

Similarly, instances of path.split(os.sep) should be switched to os.path.split()


stuck on first boot rg353m 10162023 version

On the initial install of the newest version of arkos(10162023) on a new rg353m, the device will not get past the first screen. Sometimes it will get to the screen with the four dots but then stops

Other than making sure you're using a Samsung or Sandisk sd card and not using Balena Etcher, you can try this temporary solution here: https://github.com/christianhaitian/arkos/issues/837.

okay, i will try that, will there be anyway to fix this issue in the future through a software update?

If I can ever replicate the issue, maybe.  None of my 353 units exhibit this issue so I can't replicate it yet.


Rollback bullmq 2.0.0

Coverage increased (+0.006%) to 94.299% when pulling 7bac66511615cf0fe97c6e138471a0c199d5a476 on cody-bullmq2-rollback into 4b424c0f22b9e4e9a1acb130a2969d0479d1e5ed on main.


feat: allow for alternative separator character in CSV files

Commas are far too common in text and replacing them with , apparently doesn't actually render the commas on the final text. Please add a setting to allow for the separator character to be modified to something less common (ie pipe char).
Thanks!

Please see PRs #11 and #12.

Hey @bkuri thanks for the suggestion and PR.
Adding the flexibility to set a custom separator is good, please take note that if you need to do pluralization with vue-i18n it uses the pipe char to do that, I have an example here. You can use commas in your translations string by wrapping them in double quotes
using-comma,"Using comma, then some text","Using comma, then some text","Using comma, then some text"

@samk-dev thanks for the heads up regarding the pipe character. :+1:
I could've sworn that I had tried using quotes to separate between translations. At any rate, not having to use them in the first place should be more maintainable in the long run.
I've now sent a proper PR your way. Sorry for the all the PR noise earlier. Cheers!

@bkuri thanks for the pr. I'll release it tonight or tomorrow.


Pancake Sort in JavaScript

💥 Pancake Sort
Idea is to implement the Pancake sort algorithm in JavaScript
Have you read the Contributing Guidelines on Pull Requests?
Yes

/assign


Add the Lustre language

Currently we're not accepting/merging new languages to the core repo, but if you'd like to become the long-term maintainer of this language we'd be happy to host a separate repo for you in the highlightjs organization and give you push access.  It's pretty easy for your language to exist as a stand-alone module that then people can just add themselves with registerLanguage (the README has examples of doing this).
Though there aren't really official docs or an official template yet...  You can find other examples already there:
https://github.com/highlightjs/
After the holidays I plan to work on making this whole process (or using and integrating 3rd party languages) a bit easier and more official.

Would you like us to create a highlightjs-lustre repo for you?

Sorry forgot to link the larger discussion of things: https://github.com/highlightjs/highlight.js/issues/2149

That would be nice. Thanks Josh.
R1
14 déc. 2019 15:38:28 Josh Goebel<EMAIL_ADDRESS>
Would you like us to create a highlightjs-lustre repo for you?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub[https://github.com/highlightjs/highlight.js/pull/2321?email_source=notifications&email_token=AAUIWL23NISVCYRAR5WOZRTQYTVWHA5CNFSM4J2BFNS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG4ECXI#issuecomment-565723485], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAUIWL3H2D6ZYIND6JPIPP3QYTVWHANCNFSM4J2BFNSQ].[https://github.com/notifications/beacon/AAUIWLYUHY6B6G2KM5YMDJDQYTVWHA5CNFSM4J2BFNS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG4ECXI.gif]

https://github.com/highlightjs/highlightjs-lustre
I sent you an invite.  @egor-rogov Have we just been giving people "Write" permissions when we create new language repos? This is the first one I've done.

@jahierwan There ya go!

I give admin permissions (e.g. to be able to invite new maintainers etc).
That's all what's needed.

Ok, admin it is then!


montage supported ? example

Hello
Is the montage option (merging multiple uploaded images into one) currently supported ? I haven't found anything in the code.
http://www.imagemagick.org/Usage/montage/#montage
Could you provide an example how to set this option ?
Thanks

Ok i looked into the source more closely seems like you create a separate class method for each option, so one would need to create a montage method that calls gm. Is this something you are planning to do ?


VSCode should have a table listing its versions against the corresponding Electron (or NODE_MODULE_VERSION) versions.

This table helps a lot when one builds a native Node.js addon and needs to know which Node.js versions have which NODE_MODULE_VERSION. Without such table for VSCode I simply don't know which VSCode versions should I test against. Installing every non-patch VSCode version to figure that out is not fun.

Something like this but official and up-to-date. I am currently reading its source code and figuring out if I can do that myself.

I think I've found an easier way to figure out Electron versions in different VSCode versions. I can browse repository tags and look at the .yarnc file. I just hope this is reliable enough, and someone can confirm that.

		VSCODE ELECTRON
		master (insiders?) - 6.1.5
		1.40.2 - 6.1.5 // new
		1.40.1 - 6.1.2
		1.40 - 6.1.2 // new
		1.39.2 - 4.2.10
		1.39.1	 - 4.2.10
		1.39.0 - 4.2.10
		1.38.1 - 4.2.10
		1.38.0 - 4.2.10	// new
		1.37.1 - 4.2.7
		1.37.1 - 4.2.7
		1.37.0 - 4.2.7 // new
		1.36.1 - 4.2.5
		1.36.1 - 4.2.5
		1.36.0 - 4.2.5	// new
		1.35.1 - 3.1.8
		1.35 - 3.1.8	// new
the rest can be found here: https://github.com/Sneezry/vscode-version-watcher

@anurbol yes .yarnrc file contains the electron version that went in that branch.
Any major electron version bump is always a change in NODE_MODULE_VERSION https://github.com/nodejs/node/blob/master/doc/abi_version_registry.json , as long as your module is recompiled, matching the version shouldn't be something the author should be worried about.
Also I would suggest to have module written in N-API to avoid this scenario completely https://nodejs.org/api/n-api.html.


Allow configuring bridged user display name format

I think it should be possible for the bridge administrator to be able to change how display names are formatted and if it's changed, sync the change to existing clients.
TeleIRC has options:
// formatting of Telegram usernames on IRC.
// the following placeholders are available:
//
// - %firstName% (first name of sender)
// - %lastName% (last name of sender)
// - %username% (optional Telegram username of sender)
config.nameFormat = '%username%';

// fallback format string for %username% if sender lacks username
config.usernameFallbackFormat = '%firstName% %lastName%';

Currently the Telegram users have display name Firstname Lastname (Telegram) at Telegram and thus Matrix users don't know how to ping Telegram users. If the display name format was set to @%username% (Telegram), automatically completing the Telegram name would be possible and everyone would know how to do it at least from Matrix.

Other issues we have encoutered at SailfishOS Fan Club in case someone else will find them through this issue:

IRC bridge repeats Telegram users who originally had no ASCII characters in their display name - https://github.com/matrix-org/matrix-appservice-irc/issues/27
IRC bridged display name cannot be changed - https://github.com/matrix-org/matrix-appservice-irc/issues/413

This is an interesting case, as the %firstname% %lastname% name in Telegram could be viewed as a display name, just like the display name on Matrix. It is indeed a problem that Telegram users can't be pinged however — maybe this can be done with some conversion magic in the bridge

Oh I just saw that Matrix indeed does have a mentioning API now. Fixing #36 should fix the problem this solves as well, and I'm a major supporter of keeping the name behaviour as it is now, so I'm closing this for now.