caosdb-server issueshttps://gitlab.indiscale.com/caosdb/src/caosdb-server/-/issues2024-02-20T13:47:45Zhttps://gitlab.indiscale.com/caosdb/src/caosdb-server/-/issues/336Extern: Value in string queries may not start with large number of digits2024-02-20T13:47:45ZDaniel HornungExtern: Value in string queries may not start with large number of digits---
extern: https://gitlab.com/linkahead/linkahead-server/-/issues/253
---
```
db.execute_query("FIND Record WITH some_prop = '0123456789012345678901234567890123456789world'")
```
This is interpreted as a large number somehow and fed t...---
extern: https://gitlab.com/linkahead/linkahead-server/-/issues/253
---
```
db.execute_query("FIND Record WITH some_prop = '0123456789012345678901234567890123456789world'")
```
This is interpreted as a large number somehow and fed to SQL, which chokes.
- [ ] Fixed this bug
- [ ] Followup issues created if necessaryDaniel HornungDaniel Hornunghttps://gitlab.indiscale.com/caosdb/src/caosdb-server/-/issues/335Investigate: Job Failed #2644852024-03-18T00:05:06ZHenrik tom WördenInvestigate: Job Failed #264485Job [#264485](https://gitlab.indiscale.com/caosdb/src/caosdb-server/-/jobs/264485) failed for b7cdc7f5a82b10bc6cf77e1c2e46592d90124563:
Job is flaky. What can be done?Job [#264485](https://gitlab.indiscale.com/caosdb/src/caosdb-server/-/jobs/264485) failed for b7cdc7f5a82b10bc6cf77e1c2e46592d90124563:
Job is flaky. What can be done?Timm Fitschent.fitschen@indiscale.comTimm Fitschent.fitschen@indiscale.comhttps://gitlab.indiscale.com/caosdb/src/caosdb-server/-/issues/331Extern: Querying for entities with property fails if using ID2024-03-18T00:05:06ZDaniel HornungExtern: Querying for entities with property fails if using ID---
extern: https://gitlab.com/linkahead/linkahead-server/-/issues/248
---
https://gitlab.com/linkahead/linkahead-server/-/issues/248
Possible duplicate of https://gitlab.com/linkahead/linkahead-server/-/issues/247
- [ ] Reproduced
- ...---
extern: https://gitlab.com/linkahead/linkahead-server/-/issues/248
---
https://gitlab.com/linkahead/linkahead-server/-/issues/248
Possible duplicate of https://gitlab.com/linkahead/linkahead-server/-/issues/247
- [ ] Reproduced
- [ ] Fixed or documented (if intentional behavior)
- [ ] Followup issues created if necessaryBatCAT WP4 - Knowledge IntegrationTimm Fitschent.fitschen@indiscale.comTimm Fitschent.fitschen@indiscale.comhttps://gitlab.indiscale.com/caosdb/src/caosdb-server/-/issues/330Extern: Unexpected Server Error when updating an Entity with a FILE Property2024-03-04T08:35:34ZHenrik tom WördenExtern: Unexpected Server Error when updating an Entity with a FILE Propertyhttps://gitlab.com/linkahead/linkahead-server/-/issues/246https://gitlab.com/linkahead/linkahead-server/-/issues/246Henrik tom WördenHenrik tom Wördenhttps://gitlab.indiscale.com/caosdb/src/caosdb-server/-/issues/329Remove Read-Permission for group and other of authtoken files2023-12-06T11:12:59ZHenrik tom WördenRemove Read-Permission for group and other of authtoken filesIt seems the file is created with the following permission by default:
`-rw-r--r-- 1 999 1006 266 Dec 6 10:45 admin_token_crud.txt`
Thus, everyone can read the token. Also, if this is created within Docker and it is copied outside Do...It seems the file is created with the following permission by default:
`-rw-r--r-- 1 999 1006 266 Dec 6 10:45 admin_token_crud.txt`
Thus, everyone can read the token. Also, if this is created within Docker and it is copied outside Docker, the permissions stay the same which again allows (by default) everyone to read the token.Henrik tom WördenHenrik tom Wördenhttps://gitlab.indiscale.com/caosdb/src/caosdb-server/-/issues/320Extern: Cannot update entity permissions if file is missing.2024-03-18T00:05:06ZTimm Fitschent.fitschen@indiscale.comExtern: Cannot update entity permissions if file is missing.https://gitlab.com/linkahead/linkahead-server/-/issues/36https://gitlab.com/linkahead/linkahead-server/-/issues/36Timm Fitschent.fitschen@indiscale.comTimm Fitschent.fitschen@indiscale.comhttps://gitlab.indiscale.com/caosdb/src/caosdb-server/-/issues/318EXTERN: Case mismatch causes permissions to be invalid2024-03-18T10:21:26ZFlorian SpreckelsenEXTERN: Case mismatch causes permissions to be invalidhttps://gitlab.com/caosdb/caosdb-server/-/issues/234https://gitlab.com/caosdb/caosdb-server/-/issues/234Florian SpreckelsenFlorian Spreckelsenhttps://gitlab.indiscale.com/caosdb/src/caosdb-server/-/issues/317EXTERN: Server handles states of properties incorrectly2024-03-18T10:21:30ZFlorian SpreckelsenEXTERN: Server handles states of properties incorrectlyhttps://gitlab.com/caosdb/caosdb-server/-/issues/225https://gitlab.com/caosdb/caosdb-server/-/issues/225Florian SpreckelsenFlorian Spreckelsenhttps://gitlab.indiscale.com/caosdb/src/caosdb-server/-/issues/316EXTERN: Bug: Error message when text for "name" for new record is too long2023-12-11T09:50:15ZFlorian SpreckelsenEXTERN: Bug: Error message when text for "name" for new record is too longhttps://gitlab.com/caosdb/caosdb-server/-/issues/235https://gitlab.com/caosdb/caosdb-server/-/issues/235Daniel HornungDaniel Hornunghttps://gitlab.indiscale.com/caosdb/src/caosdb-server/-/issues/315EXTERN: RecordTypes with name duplicates cannot be used as list datatype2024-01-03T13:59:20ZFlorian SpreckelsenEXTERN: RecordTypes with name duplicates cannot be used as list datatypehttps://gitlab.com/caosdb/caosdb-server/-/issues/230https://gitlab.com/caosdb/caosdb-server/-/issues/230Florian SpreckelsenFlorian Spreckelsenhttps://gitlab.indiscale.com/caosdb/src/caosdb-server/-/issues/314ENH: API to get date of last cache invalidation2023-09-21T14:30:54ZDaniel HornungENH: API to get date of last cache invalidation## Summary
It would be nice if the server had a low-latency API resource to get the time of the last cache invalidation. Such a feature would allow more general client-side caching of queries.
## Possible fixes
* This might be possib...## Summary
It would be nice if the server had a low-latency API resource to get the time of the last cache invalidation. Such a feature would allow more general client-side caching of queries.
## Possible fixes
* This might be possible as a part of the `/info` resource.
* This resource should be served fast even (and especially) when the server is under high load.https://gitlab.indiscale.com/caosdb/src/caosdb-server/-/issues/313EXTERN: Server handles states of properties incorrectly2023-09-14T11:26:46ZFlorian SpreckelsenEXTERN: Server handles states of properties incorrectlyhttps://gitlab.com/caosdb/caosdb-server/-/issues/225
## Steps to Reproduce the Problem
Reproducible with Geomar's production dump in `/nextCloud/Customer/GEOMAR/Dump Testinstanz/*2023-07-28*`
1. Restore from this dump
2. Run mygration...https://gitlab.com/caosdb/caosdb-server/-/issues/225
## Steps to Reproduce the Problem
Reproducible with Geomar's production dump in `/nextCloud/Customer/GEOMAR/Dump Testinstanz/*2023-07-28*`
1. Restore from this dump
2. Run mygrations in `geomar/database-schema/migrations` up to `003_...`
3. Look at the output of `FIND Sample WHICH HAS A "Nagoya Case"`Henrik tom WördenHenrik tom Wördenhttps://gitlab.indiscale.com/caosdb/src/caosdb-server/-/issues/312TODO UPDATE AbstractProperties2023-09-08T12:03:14ZAlexander SchlemmerTODO UPDATE AbstractPropertiesI found this note in the documentation (during cleanup) in an article about abstract properties. I guess this is a feature request? Is it still valid? @timm
```
## TODO
### UPDATE AbstractProperties
Notes:
* ids are persistent. They ca...I found this note in the documentation (during cleanup) in an article about abstract properties. I guess this is a feature request? Is it still valid? @timm
```
## TODO
### UPDATE AbstractProperties
Notes:
* ids are persistent. They cannot be changed.
* Maybe we should take the PropertyTypes as persistent, too or just allow a few changes: Double <-> Integer?
Roadmap:
1) Specify and implement changing the name, description and unit of AbstractProperties.
2) Specify and implement changing the reference of an abstract reference property.
3) Anything else...
```Timm Fitschent.fitschen@indiscale.comTimm Fitschent.fitschen@indiscale.comhttps://gitlab.indiscale.com/caosdb/src/caosdb-server/-/issues/310Context Root does not work2023-06-30T11:06:42ZHenrik tom WördenContext Root does not work
Steps to reproduce:
- use demo profile of deploy
- add a file named `profiles/default/custom/caosdb-server/conf/ext/server.conf.d/50-default.conf` with content `CONTEXT_ROOT=/demo` and start the server
- when starting, server prints in...
Steps to reproduce:
- use demo profile of deploy
- add a file named `profiles/default/custom/caosdb-server/conf/ext/server.conf.d/50-default.conf` with content `CONTEXT_ROOT=/demo` and start the server
- when starting, server prints in debug `caosdb-server_1 | [20-Feb-13 14:15:32:731] [INFO] [ServerProperties:173] - CONTEXT_ROOT=/demo`
- visit `https://localhost:10443/demo`
- Basically, what ever you do (Send a query, click on "Entities", click on "Filesystem". The context root is removed.Timm Fitschent.fitschen@indiscale.comTimm Fitschent.fitschen@indiscale.comhttps://gitlab.indiscale.com/caosdb/src/caosdb-server/-/issues/308Syntactic sugar eats "a" or "an" from property names2023-05-30T11:54:59ZHenrik tom WördenSyntactic sugar eats "a" or "an" from property names## Summary
`find VolumetricSegmentation with analysis_task` is parsed as ` <ParseTree>(cq find (entity VolumetricSegmentation) (entity_filter (which_exp with an) (filter_expression (pov (property alysis_task)))) &lt;EOF&gt;)</Pars...## Summary
`find VolumetricSegmentation with analysis_task` is parsed as ` <ParseTree>(cq find (entity VolumetricSegmentation) (entity_filter (which_exp with an) (filter_expression (pov (property alysis_task)))) <EOF>)</ParseTree>`
## Expected Behavior
The property name is parsed correctly.
## Actual Behavior
"an" was eaten by the syntactic sugar.
## Steps to Reproduce the Problem
1. Send the query
2. check the parsetree
## Specifications
SERVER 868f3134a2d6ae9e1e88fdf452f4517fa5d14b30
## Possible fixes
Force a white space after 'a'/'an'https://gitlab.indiscale.com/caosdb/src/caosdb-server/-/issues/307Extern: Parentheses lead to incorrect query results2023-06-26T07:49:56ZHenrik tom WördenExtern: Parentheses lead to incorrect query resultshttps://gitlab.com/caosdb/caosdb-server/-/issues/202https://gitlab.com/caosdb/caosdb-server/-/issues/202https://gitlab.indiscale.com/caosdb/src/caosdb-server/-/issues/306Extern: Syntactic sugar for which2023-05-30T07:20:44ZHenrik tom WördenExtern: Syntactic sugar for whichhttps://gitlab.com/caosdb/caosdb-server/-/issues/223
https://gitlab.indiscale.com/caosdb/src/caosdb-server/-/merge_requests/87https://gitlab.com/caosdb/caosdb-server/-/issues/223
https://gitlab.indiscale.com/caosdb/src/caosdb-server/-/merge_requests/87https://gitlab.indiscale.com/caosdb/src/caosdb-server/-/issues/305Allow Properties w/o datatype2023-05-25T08:29:49ZTimm Fitschent.fitschen@indiscale.comAllow Properties w/o datatype# Description
Allow properties (abstract and concrete) without datatype. The datatype is not strictly necessary when there is no value (value = `NULL`) because datatypes are primarily used to check the consistency of values (and determi...# Description
Allow properties (abstract and concrete) without datatype. The datatype is not strictly necessary when there is no value (value = `NULL`) because datatypes are primarily used to check the consistency of values (and determine the right table in the backend for the value).
# Use-Case
1) This could be useful for super-types of properties which are not actually used apart from the query
2) This could be useful for properties which have an arity of zero (like `yellowness`) - however, these are better represented by boolean in the most cases.https://gitlab.indiscale.com/caosdb/src/caosdb-server/-/issues/303EXTERN: Cache of children is not removed when parent is updated2024-03-18T00:05:06ZFlorian SpreckelsenEXTERN: Cache of children is not removed when parent is updatedhttps://gitlab.com/caosdb/caosdb-server/-/issues/220https://gitlab.com/caosdb/caosdb-server/-/issues/220Timm Fitschent.fitschen@indiscale.comTimm Fitschent.fitschen@indiscale.comhttps://gitlab.indiscale.com/caosdb/src/caosdb-server/-/issues/300LinkAhead renaming: Allow but deprecate old CAOSDB_CONFIG_ environment variab...2024-03-04T08:35:37ZDaniel HornungLinkAhead renaming: Allow but deprecate old CAOSDB_CONFIG_ environment variables.From `README_SETUP.md`:
> All configuration environment variables should be change from `CAOSDB_CONFIG_...` to
`LINKAHEAD_CONFIG_...`. The old environment variables will remain deprecated but valid for some
time, but mixing old and new...From `README_SETUP.md`:
> All configuration environment variables should be change from `CAOSDB_CONFIG_...` to
`LINKAHEAD_CONFIG_...`. The old environment variables will remain deprecated but valid for some
time, but mixing old and new variables is forbidden: If you rename one, you have to rename all.
- [ ] Deprecation and consistency check (either CAOSDB or LINKAHEAD, not both) is implemented.
- [ ] Followup issues created if necessaryLinkAhead RelaunchHenrik tom WördenHenrik tom Wörden