A way to persist precomputed grammars

When using MARPA to create a traditional compiler, I don't want to pay to build and precompute a grammar for each input file.  There should be a way to write out tables that allow a grammar to be quickly reconstructed with minimal data movement.  In particular, it would be ideal if these tables could be captured in statically-initialized data (e.g. global C arrays) and merely “pointed-at” by a new recognizer.

In the early days, the Marpa community looked carefully at this issue.  Precomputation is fast, and it seemed likely that the difference between precomputation and de-serialization of a serialized precomputed grammar would not be measurable.  Optimization is a moving target, and we won't really know the exact gain until we implement the serialization.  But it has an upper bound in the pre-computation time, less the time required to read a file whose size is proportional to the size of the precomputed grammar in its internal form.  This suggests that the potential gain is not likely to repay the time and effort required to make the experiment.

On May 24, 2022, at 12:12 PM, Jeffrey Kegler @.***> wrote:
In the early days, the Marpa community looked carefully at this issue. Precomputation is fast, and it seemed likely that the difference between precomputation and de-serialization of a serialized precomputed grammar would not be measurable.

It’s not just precomputation but also all the calls to build rules and symbols.  That may still not account for much time in practice, of course; I don’t know, and I haven’t measured.
That said, I’m not suggesting deserialization, which, given I/O and dynamic allocation costs, seems unlikely to produce a speedup.  Instead, I’m suggesting the entire precomputed grammar could be encoded in immutable data that’s part of the program image, in a format that can be used directly—by pointing at it.

Within the same run, you can achieve that effect by creating more than one recognizer with the same base grammar.  With this it's quite possible to run two (or more) parses side by side and the precomputation is done only once.
There are some limits because a couple of things are shared by all objects with the same base grammar.  One is the error code, and the other is the event queue.  The idea behind both is that both are supposed to be retrieved immediately after the call that generates them  This does imply that you cannot run recognizers with different base grammars in different threads.
This may still not be what you have in mind.  I know in olden days, there were UNIX programmers who would drop cores at arbitrary points and then re-purpose them as executables, reusing all the work done so far.  And I've toyed with the idea of leveraging pre-complied Lua chunks to similar effect.

On May 24, 2022, at 2:56 PM, Jeffrey Kegler @.***> wrote:
Within the same run, you can achieve that effect by creating more than one recognizer with the same base grammar.

If I was going to parse multiple files in a single run, I’d want to do it in parallel… which doesn’t work because the grammar is shared mutable state for all the recognizers operating on it.

This may still not be what you have in mind. I know in olden days, there were UNIX programmers who would drop cores at arbitrary points and then re-purpose them as executables, reusing all the work done so far. And I've toyed with the idea of leveraging pre-complied Lua chunks to similar effect.

The simplest approach, and what I had in mind, is to eliminate all internal pointers from the grammar data structure and instead use indices into arrays.

Not sure I follow, but there are no pointers from the grammar objects to their child objects.  The reason I don't consider sharing the grammar objects thread-safe is that mutable data in the base grammar object is shared among its child objects.  All of this mutable data could be eliminated without much trouble, with one exception: the reference counting for memory management.
I advertise C89 portability, and C89, if I am correct, neither guarantees the kinds of atomicity, nor offers the kind of locking that would allow me to claim that the reference counting is thread-safe.

On May 25, 2022, at 8:06 AM, Jeffrey Kegler @.***> wrote:
Not sure I follow, but there are no pointers from the grammar objects to their child objects.

I don’t know what MARPA’s internal data structures look like, but…
If there are any pointers between child objects or back to the grammar they would need to be eliminated too.  A grammar constructed as I’m suggesting would probably be a collection of arrays, with “child objects” stored in the array elements and any “child object pointers” replaced by array indices.

I advertise C89 portability, and C89, if I am correct, neither guarantees the kinds of atomicity, nor offers the kind of locking that would allow me to claim that the reference counting is thread-safe.

I would handle that by adding three things:

A marpa_g_new_precomputed(a1, a2, …) constructor that builds a grammar around already-allocated arrays a1…aN, and also makes marpa_g_ref/marpa_g_unref into no-ops for the result.
A marpa_g_new_uncounted() that makes a grammar for which marpa_g_ref and marpa_g_unref are no-ops.    It becomes the users responsibility to call marpa_g_destroy(), or not, at the right time.
A marpa_g_destroy(g) function that unconditionally destroys/deallocates the arrays stored in the grammar

Sure, these operations are unsafe if used improperly, but that’s also true of marpa_g_unref.

I'll summarize the "how to" aspects of threads in this comment, and address "Is it worth it?" in a second comment.
With elimination of a few pieces of data shared with the child objects, we can create a Libmarpa which, after precomputation, has only one shared mutable -- the grammar's reference count.  We can eliminate this along the lines of a suggestion from @dabrahams:
In the configuration, have a "mutable" boolean.  marpa_g_new() copies this to a mutable flag.  If the mutable flag is unset, marpa_g_ref() and marpa_g_unref() are no-ops.  It then becomes necessary to "manually" destroy the grammar once threading ends, which may be done with a new marpa_g_destroy() method.

My opinions on how worthwhiile these changes to allow thread-safe base grammars would be are mainly informed from my C programming of threaded apps, and the disappointing results in the Perl world.  In C threads are great when you can get them working, but they're hard to debug.  A significant part of my income in my consulting days was rewriting threaded apps someone else had failed to get working.  All this cost the client, so the cost vs. risk vs. benefit requires a very important application.
In the Perl world, a lot of time and brainpower has been devoted to threading, with little to show for it AFAICT.  Marpa::R2 is thread-safe in the same sense as Libmarpa (no shared of base grammars) but I don't know of anyone who actually uses that.
I tried to find out how things are in the Swift world and found this:
https://www.hackingwithswift.com/quick-start/concurrency/understanding-threads-and-queues , which seems to counsel moderation.
My impression is that the current thread-safety of Libmarpa, which does not allow the sharing of base grammars, is adequate for the near or even forseeable future.

I don't know if you're trying to make the point that nobody should want to do stuff in parallel, but that's a pretty outdated view.  Swift now has extensive in-language support for concurrency, and IIRC the Swift compiler itself parses multiple files concurrently.
Regardless, the point of these suggestions is to allow persistence and super-cheap construction.  They also happen to allow thread-safety.  Note that without this capability, MARPA will be good for my purposes as an experimental tool for a while, but (unless my project fizzles) I will certainly end up migrating to my own parser implementation.

If you create an experimental tool, then we will have a means to measure the cost of pre-computing the grammar for each thread.  Given an actual example of use, an optimization based on good measurements is likely to quickly move out of the wishlist and straight to the top of the priority queue.

This does imply that you cannot run recognizers with different base grammars in different threads.

I thought that the rule was: accessing a grammar G or a child, grand-child, etc. of it, must run synchroneously.
In other words, if I have different grammars G1 and G2, threads safety is ok as long as the threads do no execute concurrent calls on these grammars (or any child, grand-child etc of them -  this mean recognizers, bocage, valuation and so on) (?)

@jddurand The line you quote in https://github.com/jeffreykegler/libmarpa/issues/113#issuecomment-1199594793 (which is from https://github.com/jeffreykegler/libmarpa/issues/113#issuecomment-1136468145)  was a misstatement.  I've corrected it to

This does imply that you cannot safely run two different recognizers with the same base grammar in different threads.

I'll attempt to summarize my understanding of where this discussion went.  I think the point turned out to be, not so much whether the particular thread-friendly change originally suggested should be made, but whether it could be the first step in making Libmarpa concurrency-safe in the modern sense.  Libmarpa IMHO is not "outdated" (https://github.com/jeffreykegler/libmarpa/issues/113#issuecomment-1140340762) in terms of current practice, but admittedly it falls well short of providing the kind of support for concurrency expected in new languages.
If I were to make adding concurrency safety my top short term priority, I would look long and hard at rewriting Libmarpa in a language which offers support for this, such as Swift or Rust.  There are trade-offs, but leaving behind a language whose concurrency and memory management support is as impoverished as is the case with C language, is certainly tempting.  @dabrahams has decided to do undertake a Swift clone of the Marpa/Earley/Leo algorithm, and I look with interest to the results.
My top short term priority is supportng the current generation of users and applications.  After that I have some ideas for adding new capabilities to the Marpa algorithm.  It is not impossible these will wind in pull requests submitted to a Swift clone of Marpa.

@dabrahams: I have added a comment (https://github.com/jeffreykegler/libmarpa/issues/113#issuecomment-1202993256) that is intended to summarize the result of this discussion from my POV.
Since, for the reasons given in that comment, I plan no near term action on this request, I would like to close this issue.  Absent feedback to the contrary, I will do so after a couple of days.

Closed per https://github.com/jeffreykegler/libmarpa/issues/113#issuecomment-1202997380.

It's interesting that it was fast enough with the R2 front end and ESLIF is embarrassingly faster.  I wonder if your view of the relative cost of preprocessing would change if you adopted a faster front-end.

Numbers could change my POV, yes.

Could you point me to something that works this way?
I'm particularly confused about how an array vs. pointer distinction might confer thread-safety in the C context. A C array, if referred to via a bareword, is a pointer. And indexing a C array is literally synonymous with pointer arithmetic. And all this is before optimization.
Sent with Proton Mail secure email.
------- Original Message -------
On Wednesday, May 25th, 2022 at 12:58 PM, Dave Abrahams @.***> wrote:

On May 25, 2022, at 8:06 AM, Jeffrey Kegler @.***> wrote:
Not sure I follow, but there are no pointers from the grammar objects to their child objects.

I don’t know what MARPA’s internal data structures look like, but…
If there are any pointers between child objects or back to the grammar they would need to be eliminated too. A grammar constructed as I’m suggesting would probably be a collection of arrays, with “child objects” stored in the array elements and any “child object pointers” replaced by array indices.

I advertise C89 portability, and C89, if I am correct, neither guarantees the kinds of atomicity, nor offers the kind of locking that would allow me to claim that the reference counting is thread-safe.

I would handle that by adding three things:

A marpa_g_new_precomputed(a1, a2, …) constructor that builds a grammar around already-allocated arrays a1…aN, and also makes marpa_g_ref/marpa_g_unref into no-ops for the result.
A marpa_g_new_uncounted() that makes a grammar for which marpa_g_ref and marpa_g_unref are no-ops. It becomes the users responsibility to call marpa_g_destroy(), or not, at the right time.
A marpa_g_destroy(g) function that unconditionally destroys/deallocates the arrays stored in the grammar

Sure, these operations are unsafe if used improperly, but that’s also true of marpa_g_unref.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were assigned.Message ID: @.***>

On Oct 11, 2022, at 12:13 AM, Jeffrey Kegler @.***> wrote:
I'm particularly confused about how an array vs. pointer distinction might confer thread-safety in the C context. A C array, if referred to via a bareword, is a pointer. And indexing a C array is literally synonymous with pointer arithmetic. And all this is before optimization.

That wasn’t being suggested in order to achieve thread safety, but to achieve address independence of the representation, so it could be created by one parser-generation executable and persisted as arrays in a generated source file that is compiled into the executable doing the actual parsing.  That’s how Yacc and Bison work, for example.
This array transformation can in fact be leveraged to achieve memory safety, though, because you can encapsulate every array access in a safe function that does bounds checking.  Achieving complete thread-safety of a C API that does mutation is probably nearly impossible, but you can do a LOT to support practical multithreaded usage without the massive copying/regeneration that’s currently required.  Probably the simplest way is to have the grammar post-processing step effectively empty all copies of the incoming mutable grammar type used for grammar construction and return a new immutable grammar type that has taken ownership of the incoming grammar’s contents and that can be used for parsing.  That would amount to manually encoding the semantics of a linear type system into your API.

@dabrahams Thanks!
I've done a bit of reading since this thread began.  I wonder if, rather than try to make C do something it is not really designed to do, it is not better to rewrite in a thread-safety-friendly language.  If I understand correctly, Rust and  Swift are two of these.

First, let me repeat:

the point of these suggestions is to allow persistence and super-cheap construction. They also happen to allow thread-safety.

Second, regarding a change of language: 🤷

In Rust you'd end up doing something similar to what I suggested above for C.
In Swift you could easily keep everything mutable all the time and have thread safety, but it would still be a much better design to do in Swift what I suggested above for C.
Both of these languages create interoperability barriers with other popular languages, so be aware of what you're losing by leaving C.
If you were going to make the change, I'd suggest Swift; you'll be less prone to get tangled up in lifetime annotations and borrow checking.


Persistence of world locking state doesn't seem to be working

When running the WorldLockingBasic example, persistence doesn't work with auto-save enabled, nor when I try to save manually. Everything just resets whenever I completely restart the built app. However, the AnchorManager SupportsPersistence boolean is true.
I'm running Unity version 2020.3.22f1 on HoloLens 2, with Mixed Reality Toolkit v2.7.3,  WLT v1.5.7, and using Windows Mixed Reality, all installed using the Mixed Reality Feature Tool.

Can you tell me what XR pipeline your project is targetting? E.g. Legacy XR, or XR SDK w/ MR OpenXR Plugin, or AR Foundation.
The problem might be that the WorldLockingContext is set for a non-matching pipeline. In the samples it is mostly set to WSA, which is no longer supported on Unity 2020.
An easy way to make sure it is set to the correct Anchor Subsystem is to run the configuration script.
https://docs.microsoft.com/en-us/mixed-reality/world-locking-tools/documentation/howtos/usingwlt/justworldlock#automated-setup
If you run that and are still having a problem, having a look at your UnityPlayer.log might help me figure out what's going wrong. Let me know either way. Thanks!

Thanks!
I am using XR SDK, and even though I had already set the anchor subsystem to XR SDK, running the script seems to have fixed the issue.

Awesome, thanks for the update!

Hi, I had exactly the same problem and was able to solve it this way. But now I get "Lost Tracking" displayed. Did you have this too, or do you know how to solve the problem?
Thanks!

I am facing the same issue with "Lost Tracking" after using the Automated Setup script. See #300 for more details.

In the end I created my application with OpenXR, because I still had some issues with XR SDK. I can't remember what the issues were but it might have also been the "Lost Tracking" thing. Don't forget to update OpenXR on your HoloLens 2 device if you decide to go down this route, because before updating I also had issues with WLT not working correctly.


Issue with rendering alpha at low angles

Is this a bug or an issue I don't know about due to my n00bliness in 3D graphics? :)
Here is my favorite testing cube from #21685 (you're welcome to take that script, add alpha material and see for yourself). With opaque material (transparency set to false), it looks good:

With transparent material and alpha = 0.01, it looks perfect:

With alpha = 0.1, it looks great:

With alpha = 1, which should be completely opaque, it looks like this:

Actually, I think this happens with any alpha, but only becomes noticeable at around 0.3 .
This only happens when you look in a direction almost parallel to those cubes; turn camera a little, and the effect disappears.
This behavior is present in Godot 3.0 stable and Godot master, on Linux and on Windows, on GLES2 and GLES3.

Sounds like a z-sorting thing to me again (there already were a number of similar issues).
To keep it short: I don't think this behavior is wrong.
Rendering with transperency has limitations. The main one being drawing order. Drawing back to front is the correct way but sorting it correctly is not always possible.
If you're using a single mesh the drawing order is fixed and defined by the order of polygons in your mesh. If you're using multiple meshes the engine sorts them (back to front) which works well for nicely separated meshes with transparency.
Other than that you'll always have to fight with these kind of artifacts.

So it is not a "bug", but an "unsolvable feature of 3D graphics", as I thought!
Hmmmm... So then, it would help if I used a MultiMesh instead? Then everything would become one mesh, drawn in one draw call, and ordered by polygons and not meshes?
I tried it. No, it did not help. MultiMesh seems to have its own method of Z-sorting, which produces slightly different, but mostly similar results.
I also tried "separating them nicely" (reduced the size of each building block a little to make them separate). That didn't help, either.

The optimal case would be using mostly opaque objects in your scene and having little transparent ones here and there when needed. The further they are apart (and the more simple their geometry) the less likely z-sorting is going to fail.

Generally, I will do that.  In this case, I wanted to visualize a 3D array, being able to see every block at once.

In Godot master with GLES2, the same thing happens even with opaque cubes (transparent = false). I don't know what does that tell us though...

Strange... so it might be related to something different after all.

I am certainly no expert in this area, especially in math, but I struggle to imagine how can Z-ordering two opaque polygons be much different from Z-ordering two transparent polygons or cubes, especially when they share two vertices, and one of them goes towards the camera, and the other goes away from the camera.
Maybe this was fixed in the opaque ordering algorithm, but missed in transparent ordering mechanism? Since those are different, someone may not have thought to implement some fix in both places, or something like that...

Opaque rendering is different as it's checking against a depth buffer. So even if the drawing order is random it shouldn't cause these artifacts.

Can this still be reproduced with opaque materials in the GLES2 renderer in 3.2 beta4? (The issue with transparent materials is likely impossible to solve in a low-end renderer.

Can this still be reproduced with opaque materials in the GLES2 renderer in 3.2 beta4?
I will check that in a few days.
(The issue with transparent materials is likely impossible to solve in a low-end renderer.)
Does that mean it would be possible to solve with a high-end renderer like maybe GLES3 or Vulkan? ^_^

@dark-penguin I don't think so either, as fixing it requires implementing order-independent transparency. This is very slow (often too slow to be usable in a game).

I've checked it. I think I must have done something wrong; with transparent=false, I can't reproduce the problem on either 3.0, 3.1-stable or 3.2-beta4 , even with GLES2. With transparent=true and alpha=1, the problem is there - as it should be.
I guess we can close this as "impossible" - opaques work, and transparents aren't supposed to.

The proper solution would be for you to manually sort using render priority.
As far as the engine goes, yes it is impossible for us to solve this problem at an engine level unfortunately.
Thanks for revisiting the issue and confirming the problem. Sorry that we couldn't come to a better solution :)

Oh, I did not know there was such a thing as assigning the render priority!.. So there is a "best solution we have" after all. :) Thank you, I'll look into that!


Challenge page should indicate if they have already been completed

In the new beta (currently at https://www.freecodecamp.dev), it would be great if a challenge page indicated somehow when the challenge has already been completed. Currently, since user inputed code is not saved, there is no indication on a challenge page that it has already been completed.

We need a check mark in the title or a badge completed or solved to indicate the same?

The most elegant thing I can think of to have something like the little circular check mark next to the title like how it is on the learn homepage - only if it's been solved, and don't show anything if it hasn't.

That would be a nice way to handle it. Please go forth if you are interested in this?


Compiled Mod Download?

I tried to find a download link to it compiled, but I couldn't find it.
Can you post a download link?

https://ci.appveyor.com/project/SonicFreak94/sadx-d3d11


Some options not available with some printers on Windows Connector

I am running GCPC 1.16 on Windows Server 2012 R2. When printing to a Canon ImageRunner iR-ADV C2225, no color options are given. However, printing to a Dell 3110cn, I am presented with a choice of Black & White or Color when trying to print through Google Chrome.

Having a similar issue when using driver KONICA MINOLTA C658SericesPCL. Via Cloud-Print-Connector 1.16 it does not give me the ability to print in color.

I think the connector gets the capabilities from the printer defaults. Try setting the defaults (e.g. to colour) for a user and then running the connector as that user or moving the defaults to the system user. See here.

Thanks for your tip @sicklittlemonkey, however the printers have color as a default setting but the problem persists.

Hi!
Has anyone found a solution for this? I used Google Cloudprint Service before to share our Canon C5550 printers with specific options -- b/w, recto/verso, inbox -- but last week all printers went offline. Using Google Cloudprint Connector I managed to get them back online but the specific options from the installed printers (on a Windows 10 machine) are ignored in the cloudprinters.
A colleague experienced the same problem -- printers gone offline with Service but for him the Connector works perfect now. The difference: no Canon printers.
I really need this functionality as it worked with GCP Service. Nor Google, nor Canon are helpfull...
Thanx in advance.
Kristof


Use Azure to builds Windows pkgs

See https://conda-forge.org/docs/maintainer/maintainer_faq.html?highlight=ninja#mfaq-windows-cmake

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

license_file entry is missing, but is required.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Terraform Version not updating in new windows terminal tab

After setting the active version of terraform in a powershell session running in Windows Terminal, and then opening a new windows terminal tab in the same window, the Terraform version setting does not carry over.

When setting the active version, this sets three variables;
PATH
TFSWITCH_VERSION
TFSWITCH_PATH
These variables are set in the current session and are persisted using the [system.environment]::SetEnvironmentVariable Method.
When a new tab is opened in an existing Windows Terminal window, the Environment Variables are pulled from the existing Windows Terminal Parent, instead of loading the most current.
This issue is tracked here
Workaround is to:

Open a new window instead of a new tab
If you need to open a new tab then rerun tfswitch to set the version

btw. you can also use tenv that support Terraform as well as OpenTofu (and Terragrunt :) ) in one tool. It allow you to simplify version management and can do much more, than tfswitch.


Model MarketingAnalyzers in Power BI

Describe the bug
Hello, I am trying to implement the powerbi model of marketing analyzers downloaded from gibhub, and I can see jouney created, but the table Emailopened and others tables, does not contain data. In dynamics the route or campaign created, by sending an email, which was opened and this is registeredin dynamics in form correct, but not see register in the table EmailOpened.
Please any help
Thank you
Screenshots
If applicable, add screenshots to help explain your problem.

Please read this post on how to [control the interaction data load.](http://powerbi.dynamicsmarketing.org/controlling-the-marketing-reporting-data-load/)
Hope this solves the issue


fix: allow config bools to default to true

Which problem is this PR solving?

#954

Short description of the changes

add a failing test to reproduce the problem

Do you want to make this a draft PR until you have code for it?

Do you want to make this a draft PR until you have code for it?

Certainly! Drafted ... and there should be code for it shortly.

Yes, I played around with adding the boolean true type a little bit this week, but I'll bump the rest of this work to be completed in #970.


Added optional script to update Discord settings to disable automatic…

Closes #6596

Added an optional script that can stop Discord from performing automatic updates.
Referenced a few online packages that do something similar: NixOS and Flathub
I copy the disable script into the app directory so I can prompt the user to run it given $dir since the "notes" section of the manifest doesn't permit $bucketsdir which would allow me to point directly at the source of the script.

I should also mention ScoopInstaller/Scoop#4605 where there was some preliminary discussion about the best way to tackle this issue.

Download script just as everything do.

Download script just as everything do.

It was my understanding that referencing $bucketsdir is now the preferred method over downloading another copy of the script that is already downloaded. Like vscode or lockhunter to name a couple.

I also support the $bucketsdir method. It's cleaner because we don't have to pollute the manifest with the script's URLs and hashes.


allow logging to be configurable using env variables

Part of https://github.com/Onto-Med/top-deployment/issues/44.
Right now there is a large amount of unnecessary log output:
top-deployment-backend-1   |
top-deployment-backend-1   |   .   ____          _            __ _ _
top-deployment-backend-1   |  /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
top-deployment-backend-1   | ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
top-deployment-backend-1   |  \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
top-deployment-backend-1   |   '  |____| .__|_| |_|_| |_\__, | / / / /
top-deployment-backend-1   |  =========|_|==============|___/=/_/_/_/
top-deployment-backend-1   |  :: Spring Boot ::               (v2.7.10)
top-deployment-backend-1   |
top-deployment-backend-1   | 2023-11-03 08:21:34.989  INFO 1 --- [           main] c.s.top.backend.TopBackendApplication    : Starting TopBackendApplication v0.6.9 using Java 11.0.16 on 31a1e13f6666 with PID 1 (/usr/src/top-backend/top-backend.jar started by root in /usr/src/top-backend)
top-deployment-backend-1   | 2023-11-03 08:21:34.991  INFO 1 --- [           main] c.s.top.backend.TopBackendApplication    : No active profile set, falling back to 1 default profile: "default"
top-deployment-backend-1   | 2023-11-03 08:21:35.641  INFO 1 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Multiple Spring Data modules found, entering strict repository configuration mode
top-deployment-backend-1   | 2023-11-03 08:21:35.641  INFO 1 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data JPA repositories in DEFAULT mode.
top-deployment-backend-1   | 2023-11-03 08:21:35.817  INFO 1 --- [           main] .RepositoryConfigurationExtensionSupport : Spring Data JPA - Could not safely identify store assignment for repository candidate interface care.smith.top.backend.repository.nlp.DocumentRepository; If you want this repository to be a JPA repository, consider annotating your entities with one of these annotations: javax.persistence.Entity, javax.persistence.MappedSuperclass (preferred), or consider extending one of the following types with your repository: org.springframework.data.jpa.repository.JpaRepository
top-deployment-backend-1   | 2023-11-03 08:21:35.818  INFO 1 --- [           main] .RepositoryConfigurationExtensionSupport : Spring Data JPA - Could not safely identify store assignment for repository candidate interface care.smith.top.backend.repository.nlp.ConceptRepository; If you want this repository to be a JPA repository, consider annotating your entities with one of these annotations: javax.persistence.Entity, javax.persistence.MappedSuperclass (preferred), or consider extending one of the following types with your repository: org.springframework.data.jpa.repository.JpaRepository
top-deployment-backend-1   | 2023-11-03 08:21:35.820  INFO 1 --- [           main] .RepositoryConfigurationExtensionSupport : Spring Data JPA - Could not safely identify store assignment for repository candidate interface care.smith.top.backend.repository.nlp.PhraseRepository; If you want this repository to be a JPA repository, consider annotating your entities with one of these annotations: javax.persistence.Entity, javax.persistence.MappedSuperclass (preferred), or consider extending one of the following types with your repository: org.springframework.data.jpa.repository.JpaRepository
top-deployment-backend-1   | 2023-11-03 08:21:35.836  INFO 1 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 190 ms. Found 9 JPA repository interfaces.
top-deployment-backend-1   | 2023-11-03 08:21:35.840  INFO 1 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Multiple Spring Data modules found, entering strict repository configuration mode
top-deployment-backend-1   | 2023-11-03 08:21:35.840  INFO 1 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data Neo4j repositories in DEFAULT mode.
top-deployment-backend-1   | 2023-11-03 08:21:35.847  INFO 1 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 6 ms. Found 3 Neo4j repository interfaces.
top-deployment-backend-1   | 2023-11-03 08:21:36.222  INFO 1 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Multiple Spring Data modules found, entering strict repository configuration mode
top-deployment-backend-1   | 2023-11-03 08:21:36.222  INFO 1 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data Neo4j repositories in DEFAULT mode.
top-deployment-backend-1   | 2023-11-03 08:21:36.228  INFO 1 --- [           main] .RepositoryConfigurationExtensionSupport : Spring Data Neo4j - Could not safely identify store assignment for repository candidate interface care.smith.top.backend.repository.QueryRepository; If you want this repository to be a Neo4j repository, consider annotating your entities with one of these annotations: org.springframework.data.neo4j.core.schema.Node, org.springframework.data.neo4j.core.schema.RelationshipProperties (preferred), or consider extending one of the following types with your repository: org.springframework.data.neo4j.repository.ReactiveNeo4jRepository
top-deployment-backend-1   | 2023-11-03 08:21:36.229  INFO 1 --- [           main] .RepositoryConfigurationExtensionSupport : Spring Data Neo4j - Could not safely identify store assignment for repository candidate interface care.smith.top.backend.repository.EntityVersionRepository; If you want this repository to be a Neo4j repository, consider annotating your entities with one of these annotations: org.springframework.data.neo4j.core.schema.Node, org.springframework.data.neo4j.core.schema.RelationshipProperties (preferred), or consider extending one of the following types with your repository: org.springframework.data.neo4j.repository.ReactiveNeo4jRepository
top-deployment-backend-1   | 2023-11-03 08:21:36.229  INFO 1 --- [           main] .RepositoryConfigurationExtensionSupport : Spring Data Neo4j - Could not safely identify store assignment for repository candidate interface care.smith.top.backend.repository.PhenotypeRepository; If you want this repository to be a Neo4j repository, consider annotating your entities with one of these annotations: org.springframework.data.neo4j.core.schema.Node, org.springframework.data.neo4j.core.schema.RelationshipProperties (preferred), or consider extending one of the following types with your repository: org.springframework.data.neo4j.repository.ReactiveNeo4jRepository
top-deployment-backend-1   | 2023-11-03 08:21:36.230  INFO 1 --- [           main] .RepositoryConfigurationExtensionSupport : Spring Data Neo4j - Could not safely identify store assignment for repository candidate interface care.smith.top.backend.repository.RepositoryRepository; If you want this repository to be a Neo4j repository, consider annotating your entities with one of these annotations: org.springframework.data.neo4j.core.schema.Node, org.springframework.data.neo4j.core.schema.RelationshipProperties (preferred), or consider extending one of the following types with your repository: org.springframework.data.neo4j.repository.ReactiveNeo4jRepository
top-deployment-backend-1   | 2023-11-03 08:21:36.230  INFO 1 --- [           main] .RepositoryConfigurationExtensionSupport : Spring Data Neo4j - Could not safely identify store assignment for repository candidate interface care.smith.top.backend.repository.OrganisationRepository; If you want this repository to be a Neo4j repository, consider annotating your entities with one of these annotations: org.springframework.data.neo4j.core.schema.Node, org.springframework.data.neo4j.core.schema.RelationshipProperties (preferred), or consider extending one of the following types with your repository: org.springframework.data.neo4j.repository.ReactiveNeo4jRepository
top-deployment-backend-1   | 2023-11-03 08:21:36.230  INFO 1 --- [           main] .RepositoryConfigurationExtensionSupport : Spring Data Neo4j - Could not safely identify store assignment for repository candidate interface care.smith.top.backend.repository.CategoryRepository; If you want this repository to be a Neo4j repository, consider annotating your entities with one of these annotations: org.springframework.data.neo4j.core.schema.Node, org.springframework.data.neo4j.core.schema.RelationshipProperties (preferred), or consider extending one of the following types with your repository: org.springframework.data.neo4j.repository.ReactiveNeo4jRepository
top-deployment-backend-1   | 2023-11-03 08:21:36.231  INFO 1 --- [           main] .RepositoryConfigurationExtensionSupport : Spring Data Neo4j - Could not safely identify store assignment for repository candidate interface care.smith.top.backend.repository.OrganisationMembershipRepository; If you want this repository to be a Neo4j repository, consider annotating your entities with one of these annotations: org.springframework.data.neo4j.core.schema.Node, org.springframework.data.neo4j.core.schema.RelationshipProperties (preferred), or consider extending one of the following types with your repository: org.springframework.data.neo4j.repository.ReactiveNeo4jRepository
top-deployment-backend-1   | 2023-11-03 08:21:36.231  INFO 1 --- [           main] .RepositoryConfigurationExtensionSupport : Spring Data Neo4j - Could not safely identify store assignment for repository candidate interface care.smith.top.backend.repository.EntityRepository; If you want this repository to be a Neo4j repository, consider annotating your entities with one of these annotations: org.springframework.data.neo4j.core.schema.Node, org.springframework.data.neo4j.core.schema.RelationshipProperties (preferred), or consider extending one of the following types with your repository: org.springframework.data.neo4j.repository.ReactiveNeo4jRepository
top-deployment-backend-1   | 2023-11-03 08:21:36.233  INFO 1 --- [           main] .RepositoryConfigurationExtensionSupport : Spring Data Neo4j - Could not safely identify store assignment for repository candidate interface care.smith.top.backend.repository.UserRepository; If you want this repository to be a Neo4j repository, consider annotating your entities with one of these annotations: org.springframework.data.neo4j.core.schema.Node, org.springframework.data.neo4j.core.schema.RelationshipProperties (preferred), or consider extending one of the following types with your repository: org.springframework.data.neo4j.repository.ReactiveNeo4jRepository
top-deployment-backend-1   | 2023-11-03 08:21:36.234  INFO 1 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 11 ms. Found 0 Neo4j repository interfaces.
top-deployment-backend-1   | 2023-11-03 08:21:36.632  INFO 1 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'customGlobalMethodSecurityConfiguration' of type [care.smith.top.backend.configuration.CustomGlobalMethodSecurityConfiguration$$EnhancerBySpringCGLIB$$f51a703b] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
top-deployment-backend-1   | 2023-11-03 08:21:36.980  INFO 1 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 8080 (http)
top-deployment-backend-1   | 2023-11-03 08:21:36.991  INFO 1 --- [           main] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
top-deployment-backend-1   | 2023-11-03 08:21:36.991  INFO 1 --- [           main] org.apache.catalina.core.StandardEngine  : Starting Servlet engine: [Apache Tomcat/9.0.73]
top-deployment-backend-1   | 2023-11-03 08:21:37.051  INFO 1 --- [           main] o.a.c.c.C.[Tomcat].[localhost].[/api]    : Initializing Spring embedded WebApplicationContext
top-deployment-backend-1   | 2023-11-03 08:21:37.052  INFO 1 --- [           main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 2005 ms
top-deployment-backend-1   | 2023-11-03 08:21:37.321  INFO 1 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Starting...
top-deployment-backend-1   | 2023-11-03 08:21:37.455  INFO 1 --- [           main] com.zaxxer.hikari.HikariDataSource       : HikariPool-1 - Start completed.
top-deployment-backend-1   | 2023-11-03 08:21:37.543  INFO 1 --- [           main] liquibase.database                       : Set default schema name to public
top-deployment-backend-1   | 2023-11-03 08:21:37.616  INFO 1 --- [           main] liquibase.lockservice                    : Successfully acquired change log lock
top-deployment-backend-1   | 2023-11-03 08:21:37.634  INFO 1 --- [           main] liquibase.changelog                      : Reading resource: db/changelog/changesets/202210170901-init-db.yaml
top-deployment-backend-1   | 2023-11-03 08:21:37.761  INFO 1 --- [           main] liquibase.changelog                      : Reading resource: db/changelog/changesets/202212141550-add-repository-type.yaml
top-deployment-backend-1   | 2023-11-03 08:21:37.763  INFO 1 --- [           main] liquibase.changelog                      : Reading resource: db/changelog/changesets/202301231633-add-value-table.yaml
top-deployment-backend-1   | 2023-11-03 08:21:37.765  INFO 1 --- [           main] liquibase.changelog                      : Reading resource: db/changelog/changesets/202302140945-add-user-table.yaml
top-deployment-backend-1   | 2023-11-03 08:21:37.767  INFO 1 --- [           main] liquibase.changelog                      : Reading resource: db/changelog/changesets/202302141252-add-user-role.yaml
top-deployment-backend-1   | 2023-11-03 08:21:37.768  INFO 1 --- [           main] liquibase.changelog                      : Reading resource: db/changelog/changesets/202302280930-replace-author-column.yaml
top-deployment-backend-1   | 2023-11-03 08:21:37.769  INFO 1 --- [           main] liquibase.changelog                      : Reading resource: db/changelog/changesets/202303221649-add-projection-default_aggregation-function-id.yaml
top-deployment-backend-1   | 2023-11-03 08:21:37.770  INFO 1 --- [           main] liquibase.changelog                      : Reading resource: db/changelog/changesets/202304191653-add-query-created-at.yaml
top-deployment-backend-1   | 2023-11-03 08:21:37.771  INFO 1 --- [           main] liquibase.changelog                      : Reading resource: db/changelog/changesets/202305261404-add-code-uri.yaml
top-deployment-backend-1   | 2023-11-03 08:21:37.785  INFO 1 --- [           main] liquibase.changelog                      : Creating database history table with name: public.databasechangelog
top-deployment-backend-1   | 2023-11-03 08:21:37.796  INFO 1 --- [           main] liquibase.changelog                      : Reading from public.databasechangelog
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-1::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:37.938  INFO 1 --- [           main] liquibase.changelog                      : Sequence hibernate_sequence created
top-deployment-backend-1   | 2023-11-03 08:21:37.940  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-1::ChristophB (generated) ran successfully in 3ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-2::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:37.952  INFO 1 --- [           main] liquibase.changelog                      : Table entity created
top-deployment-backend-1   | 2023-11-03 08:21:37.958  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-2::ChristophB (generated) ran successfully in 15ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-3::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:37.971  INFO 1 --- [           main] liquibase.changelog                      : Table entity_super_entities created
top-deployment-backend-1   | 2023-11-03 08:21:37.973  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-3::ChristophB (generated) ran successfully in 10ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-4::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:37.983  INFO 1 --- [           main] liquibase.changelog                      : Table entity_version created
top-deployment-backend-1   | 2023-11-03 08:21:37.985  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-4::ChristophB (generated) ran successfully in 10ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-5::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:37.996  INFO 1 --- [           main] liquibase.changelog                      : Table entity_version_codes created
top-deployment-backend-1   | 2023-11-03 08:21:37.998  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-5::ChristophB (generated) ran successfully in 11ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-6::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.009  INFO 1 --- [           main] liquibase.changelog                      : Table entity_version_descriptions created
top-deployment-backend-1   | 2023-11-03 08:21:38.010  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-6::ChristophB (generated) ran successfully in 10ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-7::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.016  INFO 1 --- [           main] liquibase.changelog                      : Table entity_version_equivalent_entity_versions created
top-deployment-backend-1   | 2023-11-03 08:21:38.018  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-7::ChristophB (generated) ran successfully in 6ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-8::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.028  INFO 1 --- [           main] liquibase.changelog                      : Table entity_version_synonyms created
top-deployment-backend-1   | 2023-11-03 08:21:38.029  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-8::ChristophB (generated) ran successfully in 9ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-9::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.039  INFO 1 --- [           main] liquibase.changelog                      : Table entity_version_titles created
top-deployment-backend-1   | 2023-11-03 08:21:38.040  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-9::ChristophB (generated) ran successfully in 9ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-10::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.051  INFO 1 --- [           main] liquibase.changelog                      : Table expression created
top-deployment-backend-1   | 2023-11-03 08:21:38.052  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-10::ChristophB (generated) ran successfully in 10ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-11::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.055  INFO 1 --- [           main] liquibase.changelog                      : Table expression_arguments created
top-deployment-backend-1   | 2023-11-03 08:21:38.056  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-11::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-12::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.066  INFO 1 --- [           main] liquibase.changelog                      : Table organisation created
top-deployment-backend-1   | 2023-11-03 08:21:38.068  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-12::ChristophB (generated) ran successfully in 10ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-13::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.078  INFO 1 --- [           main] liquibase.changelog                      : Table query created
top-deployment-backend-1   | 2023-11-03 08:21:38.079  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-13::ChristophB (generated) ran successfully in 10ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-14::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.085  INFO 1 --- [           main] liquibase.changelog                      : Table query_criteria created
top-deployment-backend-1   | 2023-11-03 08:21:38.087  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-14::ChristophB (generated) ran successfully in 6ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-15::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.092  INFO 1 --- [           main] liquibase.changelog                      : Table query_data_sources created
top-deployment-backend-1   | 2023-11-03 08:21:38.094  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-15::ChristophB (generated) ran successfully in 6ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-16::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.101  INFO 1 --- [           main] liquibase.changelog                      : Table query_projection created
top-deployment-backend-1   | 2023-11-03 08:21:38.102  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-16::ChristophB (generated) ran successfully in 6ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-17::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.113  INFO 1 --- [           main] liquibase.changelog                      : Table query_result created
top-deployment-backend-1   | 2023-11-03 08:21:38.114  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-17::ChristophB (generated) ran successfully in 10ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-18::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.124  INFO 1 --- [           main] liquibase.changelog                      : Table repository created
top-deployment-backend-1   | 2023-11-03 08:21:38.125  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-18::ChristophB (generated) ran successfully in 9ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-19::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.132  INFO 1 --- [           main] liquibase.changelog                      : Table restriction created
top-deployment-backend-1   | 2023-11-03 08:21:38.133  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-19::ChristophB (generated) ran successfully in 6ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-20::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.136  INFO 1 --- [           main] liquibase.changelog                      : Table restriction_boolean_values created
top-deployment-backend-1   | 2023-11-03 08:21:38.137  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-20::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-21::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.140  INFO 1 --- [           main] liquibase.changelog                      : Table restriction_date_time_values created
top-deployment-backend-1   | 2023-11-03 08:21:38.141  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-21::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-22::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.143  INFO 1 --- [           main] liquibase.changelog                      : Table restriction_number_values created
top-deployment-backend-1   | 2023-11-03 08:21:38.145  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-22::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-23::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.147  INFO 1 --- [           main] liquibase.changelog                      : Table restriction_string_values created
top-deployment-backend-1   | 2023-11-03 08:21:38.148  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-23::ChristophB (generated) ran successfully in 1ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-24::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.155  INFO 1 --- [           main] liquibase.changelog                      : Unique constraint added to expression_arguments(arguments_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.156  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-24::ChristophB (generated) ran successfully in 6ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-25::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.162  INFO 1 --- [           main] liquibase.changelog                      : Unique constraint added to query_result(query_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.163  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-25::ChristophB (generated) ran successfully in 5ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-26::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.167  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to organisation (super_organisation_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.168  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-26::ChristophB (generated) ran successfully in 3ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-27::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.171  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to entity_super_entities (super_entities_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.172  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-27::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-28::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.174  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to query_criteria (date_time_restriction_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.176  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-28::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-29::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.178  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to repository (organisation_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.180  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-29::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-30::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.182  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to entity_version (restriction_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.183  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-30::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-31::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.186  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to entity_version (expression_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.187  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-31::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-32::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.190  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to expression_arguments (expression_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.191  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-32::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-33::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.193  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to entity_version (entity_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.195  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-33::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-34::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.197  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to entity_super_entities (sub_entities_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.199  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-34::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-35::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.201  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to entity (origin_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.202  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-35::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-36::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.205  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to entity (repository_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.206  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-36::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-37::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.209  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to expression_arguments (arguments_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.210  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-37::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-38::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.213  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to query_projection (query_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.214  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-38::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-39::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.217  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to entity_version_titles (entity_version_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.218  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-39::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-40::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.222  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to entity (current_version_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.223  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-40::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-41::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.226  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to restriction_string_values (restriction_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.227  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-41::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-42::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.230  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to entity_version_synonyms (entity_version_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.231  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-42::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-43::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.234  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to query_criteria (query_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.235  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-43::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-44::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.238  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to entity_version (previous_version_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.239  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-44::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-45::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.242  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to restriction_number_values (restriction_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.243  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-45::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-46::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.245  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to query_data_sources (query_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.247  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-46::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-47::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.249  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to restriction_date_time_values (restriction_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.250  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-47::ChristophB (generated) ran successfully in 1ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-48::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.253  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to query_result (query_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.254  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-48::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-49::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.257  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to query (repository_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.258  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-49::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-50::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.261  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to entity_version_equivalent_entity_versions (equivalent_entity_version_of_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.263  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-50::ChristophB (generated) ran successfully in 3ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-51::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.265  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to restriction_boolean_values (restriction_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.266  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-51::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-52::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.269  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to entity_version_codes (entity_version_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.270  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-52::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-53::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.272  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to entity_version_descriptions (entity_version_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.273  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-53::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202210170901-init-db.yaml::1665990027334-54::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.276  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to entity_version_equivalent_entity_versions (equivalent_entity_versions_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.277  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202210170901-init-db.yaml::1665990027334-54::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202212141550-add-repository-type.yaml::1671028818545-6::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.279  INFO 1 --- [           main] liquibase.changelog                      : Columns repository_type(integer) added to repository
top-deployment-backend-1   | 2023-11-03 08:21:38.280  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202212141550-add-repository-type.yaml::1671028818545-6::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202301231633-add-value-table.yaml::1674488016958-6::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.283  INFO 1 --- [           main] liquibase.changelog                      : Table expression_values created
top-deployment-backend-1   | 2023-11-03 08:21:38.284  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202301231633-add-value-table.yaml::1674488016958-6::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202301231633-add-value-table.yaml::1674488016958-7::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.291  INFO 1 --- [           main] liquibase.changelog                      : Table value created
top-deployment-backend-1   | 2023-11-03 08:21:38.292  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202301231633-add-value-table.yaml::1674488016958-7::ChristophB (generated) ran successfully in 6ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202301231633-add-value-table.yaml::1674488016958-8::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.299  INFO 1 --- [           main] liquibase.changelog                      : Unique constraint added to expression_values(values_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.300  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202301231633-add-value-table.yaml::1674488016958-8::ChristophB (generated) ran successfully in 5ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202301231633-add-value-table.yaml::1674488016958-9::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.303  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to expression_values (values_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.304  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202301231633-add-value-table.yaml::1674488016958-9::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202301231633-add-value-table.yaml::1674488016958-10::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.307  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to expression_values (expression_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.308  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202301231633-add-value-table.yaml::1674488016958-10::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202301231633-add-value-table.yaml::1674488016958-11::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.311  INFO 1 --- [           main] liquibase.changelog                      : Column EXPRESSION.BOOLEAN_VALUE dropped
top-deployment-backend-1   | 2023-11-03 08:21:38.312  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202301231633-add-value-table.yaml::1674488016958-11::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202301231633-add-value-table.yaml::1674488016958-12::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.315  INFO 1 --- [           main] liquibase.changelog                      : Column EXPRESSION.DATE_TIME_VALUE dropped
top-deployment-backend-1   | 2023-11-03 08:21:38.316  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202301231633-add-value-table.yaml::1674488016958-12::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202301231633-add-value-table.yaml::1674488016958-13::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.319  INFO 1 --- [           main] liquibase.changelog                      : Column EXPRESSION.NUMBER_VALUE dropped
top-deployment-backend-1   | 2023-11-03 08:21:38.320  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202301231633-add-value-table.yaml::1674488016958-13::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202301231633-add-value-table.yaml::1674488016958-14::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.322  INFO 1 --- [           main] liquibase.changelog                      : Column EXPRESSION.STRING_VALUE dropped
top-deployment-backend-1   | 2023-11-03 08:21:38.324  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202301231633-add-value-table.yaml::1674488016958-14::ChristophB (generated) ran successfully in 1ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202302140945-add-user-table.yaml::1676364352747-8::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.330  INFO 1 --- [           main] liquibase.changelog                      : Table organisation_membership created
top-deployment-backend-1   | 2023-11-03 08:21:38.331  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202302140945-add-user-table.yaml::1676364352747-8::ChristophB (generated) ran successfully in 6ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202302140945-add-user-table.yaml::1676364352747-9::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.340  INFO 1 --- [           main] liquibase.changelog                      : Table user_table created
top-deployment-backend-1   | 2023-11-03 08:21:38.342  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202302140945-add-user-table.yaml::1676364352747-9::ChristophB (generated) ran successfully in 9ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202302140945-add-user-table.yaml::1676364352747-10::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.349  INFO 1 --- [           main] liquibase.changelog                      : Primary key added to organisation_membership (organisation_id, user_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.350  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202302140945-add-user-table.yaml::1676364352747-10::ChristophB (generated) ran successfully in 6ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202302140945-add-user-table.yaml::1676364352747-11::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.353  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to organisation_membership (user_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.354  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202302140945-add-user-table.yaml::1676364352747-11::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202302140945-add-user-table.yaml::1676364352747-12::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.357  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to organisation_membership (organisation_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.358  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202302140945-add-user-table.yaml::1676364352747-12::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202302141252-add-user-role.yaml::1676375700740-8::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.360  INFO 1 --- [           main] liquibase.changelog                      : Columns role(varchar(255)) added to user_table
top-deployment-backend-1   | 2023-11-03 08:21:38.362  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202302141252-add-user-role.yaml::1676375700740-8::ChristophB (generated) ran successfully in 1ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202302280930-replace-author-column.yaml::1677573038780-8::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.365  INFO 1 --- [           main] liquibase.changelog                      : Columns user_id(varchar(255)) added to entity_version
top-deployment-backend-1   | 2023-11-03 08:21:38.366  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202302280930-replace-author-column.yaml::1677573038780-8::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202302280930-replace-author-column.yaml::1677573038780-9::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.369  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to entity_version (user_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.370  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202302280930-replace-author-column.yaml::1677573038780-9::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202302280930-replace-author-column.yaml::1677573038780-10::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.373  INFO 1 --- [           main] liquibase.changelog                      : Column ENTITY_VERSION.AUTHOR dropped
top-deployment-backend-1   | 2023-11-03 08:21:38.374  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202302280930-replace-author-column.yaml::1677573038780-10::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202303221649-add-projection-default_aggregation-function-id.yaml::1679500200016-8::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.376  INFO 1 --- [           main] liquibase.changelog                      : Columns date_time_restriction_id(bigint) added to query_projection
top-deployment-backend-1   | 2023-11-03 08:21:38.377  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202303221649-add-projection-default_aggregation-function-id.yaml::1679500200016-8::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202303221649-add-projection-default_aggregation-function-id.yaml::1679500200016-9::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.380  INFO 1 --- [           main] liquibase.changelog                      : Columns default_aggregation_function_id(varchar(255)) added to query_projection
top-deployment-backend-1   | 2023-11-03 08:21:38.381  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202303221649-add-projection-default_aggregation-function-id.yaml::1679500200016-9::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202303221649-add-projection-default_aggregation-function-id.yaml::1679500200016-10::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.383  INFO 1 --- [           main] liquibase.changelog                      : Foreign key constraint added to query_projection (date_time_restriction_id)
top-deployment-backend-1   | 2023-11-03 08:21:38.384  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202303221649-add-projection-default_aggregation-function-id.yaml::1679500200016-10::ChristophB (generated) ran successfully in 1ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202303221649-add-projection-default_aggregation-function-id.yaml::1679500200016-11::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.387  INFO 1 --- [           main] liquibase.changelog                      : Column QUERY_PROJECTION.DATE_TIME_RESTRICTION dropped
top-deployment-backend-1   | 2023-11-03 08:21:38.388  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202303221649-add-projection-default_aggregation-function-id.yaml::1679500200016-11::ChristophB (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202303221649-add-projection-default_aggregation-function-id.yaml::1679500200016-12::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.390  INFO 1 --- [           main] liquibase.changelog                      : Column QUERY_PROJECTION.SORTING dropped
top-deployment-backend-1   | 2023-11-03 08:21:38.391  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202303221649-add-projection-default_aggregation-function-id.yaml::1679500200016-12::ChristophB (generated) ran successfully in 1ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202304191653-add-query-created-at.yaml::1681916104935-8::ChristophB (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.393  INFO 1 --- [           main] liquibase.changelog                      : Columns created_at(timestamp) added to query
top-deployment-backend-1   | 2023-11-03 08:21:38.394  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202304191653-add-query-created-at.yaml::1681916104935-8::ChristophB (generated) ran successfully in 1ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202305261404-add-code-uri.yaml::1685102649304-8::Christoph (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.396  INFO 1 --- [           main] liquibase.changelog                      : Columns uri(varchar(255)) added to entity_version_codes
top-deployment-backend-1   | 2023-11-03 08:21:38.398  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202305261404-add-code-uri.yaml::1685102649304-8::Christoph (generated) ran successfully in 2ms
top-deployment-backend-1   | Running Changeset: db/changelog/changesets/202305261404-add-code-uri.yaml::1685102649304-9::Christoph (generated)
top-deployment-backend-1   | 2023-11-03 08:21:38.403  INFO 1 --- [           main] liquibase.changelog                      : Column ENTITY_VERSION_CODES.CODE_SYSTEM_NAME dropped
top-deployment-backend-1   | 2023-11-03 08:21:38.404  INFO 1 --- [           main] liquibase.changelog                      : ChangeSet db/changelog/changesets/202305261404-add-code-uri.yaml::1685102649304-9::Christoph (generated) ran successfully in 2ms
top-deployment-backend-1   | 2023-11-03 08:21:38.407  INFO 1 --- [           main] liquibase.lockservice                    : Successfully released change log lock
top-deployment-backend-1   | 2023-11-03 08:21:38.455  INFO 1 --- [           main] o.hibernate.jpa.internal.util.LogHelper  : HHH000204: Processing PersistenceUnitInfo [name: default]
top-deployment-backend-1   | 2023-11-03 08:21:38.508  INFO 1 --- [           main] org.hibernate.Version                    : HHH000412: Hibernate ORM core version 5.6.15.Final
top-deployment-backend-1   | 2023-11-03 08:21:38.644  INFO 1 --- [           main] o.hibernate.annotations.common.Version   : HCANN000001: Hibernate Commons Annotations {5.1.2.Final}
top-deployment-backend-1   | 2023-11-03 08:21:38.743  INFO 1 --- [           main] org.hibernate.dialect.Dialect            : HHH000400: Using dialect: org.hibernate.dialect.PostgreSQL10Dialect
top-deployment-backend-1   | 2023-11-03 08:21:39.454  INFO 1 --- [           main] o.h.e.t.j.p.i.JtaPlatformInitiator       : HHH000490: Using JtaPlatform implementation: [org.hibernate.engine.transaction.jta.platform.internal.NoJtaPlatform]
top-deployment-backend-1   | 2023-11-03 08:21:39.462  INFO 1 --- [           main] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default'
top-deployment-backend-1   | 2023-11-03 08:21:40.325  INFO 1 --- [           main] org.neo4j.driver.internal.DriverFactory  : Direct driver instance<PHONE_NUMBER> created for server address neo4j:7687

Part 2 due to the character limit of 65536:
top-deployment-backend-1   | 2023-11-03 08:21:40.743  INFO 1 --- [           main] o.s.s.web.DefaultSecurityFilterChain     : Will secure any request with [org.springframework.security.web.session.DisableEncodeUrlFilter@51869ad6, org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter@27a90ce5, org.springframework.security.web.context.SecurityContextPersistenceFilter@3c87e851, org.springframework.security.web.header.HeaderWriterFilter@1fc5c0b2, org.springframework.web.filter.CorsFilter@77f4038c, org.springframework.security.web.authentication.logout.LogoutFilter@4bff28e7, org.springframework.security.oauth2.server.resource.web.BearerTokenAuthenticationFilter@1eb9d69a, org.springframework.security.web.savedrequest.RequestCacheAwareFilter@6124dda2, org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter@380e33c2, org.springframework.security.web.authentication.AnonymousAuthenticationFilter@49a06087, org.springframework.security.web.session.SessionManagementFilter@d2cb2d0, org.springframework.security.web.access.ExceptionTranslationFilter@949d347, org.springframework.security.web.access.intercept.FilterSecurityInterceptor@44e08a7a]
top-deployment-backend-1   | 2023-11-03 08:21:40.897  WARN 1 --- [           main] JpaBaseConfiguration$JpaWebConfiguration : spring.jpa.open-in-view is enabled by default. Therefore, database queries may be performed during view rendering. Explicitly configure spring.jpa.open-in-view to disable this warning
top-deployment-backend-1   | 2023-11-03 08:21:41.539  INFO 1 --- [           main] j.s.t.ScheduledThreadPoolJobRunrExecutor : ThreadManager of type 'ScheduledThreadPool' started
top-deployment-backend-1   | 2023-11-03 08:21:41.541  INFO 1 --- [pool-2-thread-4] org.jobrunr.server.BackgroundJobServer   : Found 0 recurring jobs that need to be updated.
top-deployment-backend-1   | 2023-11-03 08:21:41.543  INFO 1 --- [pool-1-thread-1] org.jobrunr.server.BackgroundJobServer   : JobRunr BackgroundJobServer (e2174be3-a28b-4f51-b56e-ffacdd3bb456) using InMemoryStorageProvider and 160 BackgroundJobPerformers started successfully
top-deployment-backend-1   | 2023-11-03 08:21:41.543  INFO 1 --- [pool-1-thread-1] org.jobrunr.server.ServerZooKeeper       : Server e2174be3-a28b-4f51-b56e-ffacdd3bb456 is master (this BackgroundJobServer)
top-deployment-backend-1   | 2023-11-03 08:21:41.720  INFO 1 --- [           main] o.s.b.a.e.web.EndpointLinksResolver      : Exposing 1 endpoint(s) beneath base path '/actuator'
top-deployment-backend-1   | 2023-11-03 08:21:41.751  INFO 1 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat started on port(s): 8080 (http) with context path '/api'
top-deployment-backend-1   | 2023-11-03 08:21:41.762  INFO 1 --- [           main] c.s.top.backend.TopBackendApplication    : Started TopBackendApplication in 7.15 seconds (JVM running for 7.795)

The corresponding environment variable is LIQUIBASE_LOG_LEVEL. It has a higher precedents than the liquibase.properties file.

After more research I I found the liquibase issue has two parts:

the "Running Changeset: ..." messages are a bug in Liquibase that leaks out to console log, see https://github.com/liquibase/liquibase/issues/4274
JAVA_OPTS=-Dlogging.level.liquibase=WARN works as well in docker-compose.env to get rid of the other INFO messages. But to make sure I will set LIQUIBASE_LOG_LEVEL there as well.

Liquibase v4.25.0 was released on November 13 and mentions the pull request in the bug fixes section: https://github.com/liquibase/liquibase/releases/tag/v4.25.0

The "Running Changeset" messages are now gone after upgrading to Liquibase v4.25.0.

LIQUIBASE_LOG_LEVEL=WARNING has no effect.
  backend:
    image: ghcr.io/onto-med/top-backend:v0.6.9
    [...]
    environment:
      - LIQUIBASE_LOG_LEVEL=WARNING

$ docker compose logs backend | grep liquibase
backend-1  | 2023-12-18 09:21:08.932  INFO 1 --- [           main] liquibase.database                       : Set default schema name to public
backend-1  | 2023-12-18 09:21:08.987  INFO 1 --- [           main] liquibase.lockservice                    : Successfully acquired change log lock
backend-1  | 2023-12-18 09:21:09.004  INFO 1 --- [           main] liquibase.changelog                      : Reading resource: db/changelog/changesets/202210170901-init-db.yaml
[...]

Strangely, the liquibase INFO messages still occurs with backend version v0.7.0-beta-10 where https://github.com/Onto-Med/top-backend/commit/d9bf3f939f2095b455ae02bdcfc0bc505de367a6 is included.


Vulnerability roundup 111: jenkins-2.319.1: 2 advisories [7.5]

search, files

[ ] CVE-2022-0538 CVSSv3=7.5 (nixos-unstable)
[ ] CVE-2022-20612 CVSSv3=4.3 (nixos-unstable)

CVE details
CVE-2022-0538
Jenkins 2.333 and earlier, LTS 2.319.2 and earlier defines custom XStream converters that have not been updated to apply the protections for the vulnerability CVE-2021-43859 and allow unconstrained resource usage.
CVE-2022-20612
A cross-site request forgery (CSRF) vulnerability in Jenkins 2.329 and earlier, LTS 2.319.1 and earlier allows attackers to trigger build of job without parameters when no security realm is set.

Scanned versions: nixos-unstable: 5aaed40d22f.
Cc @coreyoconnor
Cc @earldouglas
Cc @fpletz
Cc @nequissimus

Fixed:

nixos-unstable: jenkins-2.361.1


devicetree: use new macros for zephyr,dtcm & zephyr,ccm

Fine w/ the change other than checkpatch that might have to be fixed

fixed


Request and Response Interceptors

middleware-like functionality where users can register interceptors that process requests and responses

I @rezmoss I 'd like to take this and can you assign it to me.
Would it be okay if I started outlining a proposal for the interceptor API and implementation for your feedback before I dive into the code?

@arrlancore sure,it's yours

Hi @rezmoss, just figure it how it will work, is this design meet with your expectation? or you have any consideration?
package main

import (
    "fmt"
    "github.com/rezmoss/axios4go"
    "net/http"
)

// Define request interceptor (e.g., for adding Authorization header)
func requestInterceptor(req *http.Request) error {
    fmt.Println("Request Interceptor: Adding Authorization header")
    req.Header.Add("Authorization", "Bearer auth_token")
    return nil
}

// Define response interceptor (e.g., logging status code)
func responseInterceptor(resp *http.Response) error {
    fmt.Println("Response Interceptor: Status Code is", resp.StatusCode)
    if resp.StatusCode != http.StatusOK {
        return fmt.Errorf("unexpected status code: %d", resp.StatusCode)
    }
    return nil
}

func main() {
    // Define options with interceptors
    opts := &axios4go.RequestOptions{
        Headers: map[string]string{
            "Content-Type": "application/json",
        },
        Params: map[string]string{
            "query": "myQuery",
        },
        RequestInterceptor:  requestInterceptor,
        ResponseInterceptor: responseInterceptor,
    }

    // Make GET request with interceptors
    resp, err := axios4go.Get("https://api.example.com/data", opts)
    if err != nil {
        fmt.Printf("Error: %v\n", err)
        return
    }

    fmt.Printf("Response Status Code: %d\n", resp.StatusCode)
    fmt.Println("Request completed successfully")
}

@arrlancore It would be great if we could allow multiple interceptors to be chained and pass a context through them. Otherwise, it looks good!
e.g
    Params: map[string]string{"query": "myQuery"},
        InterceptorOptions: &axios4go.InterceptorOptions{
            RequestInterceptors: []axios4go.RequestInterceptorFunc{authInterceptor},
            ResponseInterceptors: []axios4go.ResponseInterceptorFunc{logInterceptor},
        },

alright let me try it

Thx @arrlancore merged