[BUG] Codex crashes on interrupted upload

Describe the bug
Codex crashes if I start uploading a large file to it and then CTRL+C my curl request before it completes.
To Reproduce

Launch codex.

Do:

dd if=/dev/urandom of=./data.bin bs=200M count=1
curl -iv -XPOST "http://localhost:8080/api/codex/v1/data" --data @data.bin

as the file is being uploaded, interrupt curl with CTRL+C. Codex will crash with:
TRC 2024-01-25 16:01:20.500-03:00 CatchableError exception                   topics="codex node" tid=585029 exc="Stream boundary is not reached yet"
/home/giuliano/Work/Status/nim-codex/codex.nim(131) codex
/home/giuliano/Work/Status/nim-codex/vendor/nim-chronos/chronos/asyncloop.nim(263) poll
/home/giuliano/Work/Status/nim-codex/vendor/nim-chronos/chronos/asyncfutures2.nim(318) futureContinue
/home/giuliano/Work/Status/nim-codex/codex/chunker.nim(95) reader
[[reraised from:
/home/giuliano/Work/Status/nim-codex/codex.nim(131) codex
/home/giuliano/Work/Status/nim-codex/vendor/nim-chronos/chronos/asyncloop.nim(263) poll
/home/giuliano/Work/Status/nim-codex/vendor/nim-chronos/chronos/asyncfutures2.nim(318) futureContinue
/home/giuliano/Work/Status/nim-codex/vendor/nim-chronos/chronos/asyncmacro2.nim(213) reader
]]
[[reraised from:
/home/giuliano/Work/Status/nim-codex/codex.nim(131) codex
/home/giuliano/Work/Status/nim-codex/vendor/nim-chronos/chronos/asyncloop.nim(263) poll
/home/giuliano/Work/Status/nim-codex/vendor/nim-chronos/chronos/asyncfutures2.nim(355) futureContinue
]]
Error: unhandled exception: Stream boundary is not reached yet [Defect]

Expected behavior
Codex should simply handle the aborted upload, either deleting all blocks that belong to the failed upload or accepting the ones that got uploaded.
Environment:

OS: Ubuntu 22.04.3 LTS
Tag/Commit: de88fd2c53a138744b61312782b989fb76eb3c6a
Arch: amd64

Additional context
Add any other context about the problem here.

Error: unhandled exception: Stream boundary is not reached yet [Defect]

Why is this a defect? It's not a Codex crash Chronos is for some reason aborting the process on a malformed stream, which isn't sound.

Looks similar to https://github.com/codex-storage/nim-codex/issues/527, but it is not reproduced anymore on codexstorage/nim-codex:latest-dist-tests - fd3c56.
But some weird and reproducible behaviour observed
Docker - not crashed
# Run
docker run \
  -e CODEX_API_BINDADDR=<IP_ADDRESS> \
  -e CODEX_LOG_LEVEL=TRACE \
  -p 8080:8080 \
  codexstorage/nim-codex:latest-dist-tests

# Generate
dd if=/dev/urandom of=upload.bin bs=1000M count=1

# Test
timeout 5 curl -X POST localhost:8080/api/codex/v1/data \
  -H "Content-Type: application/octet-stream" \
  -H "Expect: 100-continue" -T upload.bin

Binary - crashed
# Run
codex --log-level=TRACE

# Generate
dd if=/dev/urandom of=upload.bin bs=1000M count=1

# Test
timeout 5 curl -X POST localhost:8080/api/codex/v1/data \
  -H "Content-Type: application/octet-stream" \
  -H "Expect: 100-continue" -T upload.bin

I am facing this problem as well. My use-case is that I'm trying to upload a file from the UI and when I cancel the request, the client crashes with this error:
ERR 2024-07-30 19:23:08.468+02:00 Unhandled exception in async proc, aborting topics="codex" tid=41748 msg="Stream boundary is not reached yet"

https://github.com/user-attachments/assets/b1ad6482-84fe-4dcf-9873-3141529b87af

Alright thanks @2-towns, gonna bump this up so we work on it.

I did a git pull this morning and the node is not crashing anymore. Instead, I am seing the following log:
DBG 2024-07-31 12:06:35.308+02:00 Critical error occured while sending response topics="codex" tid=90717 meth=POST peer=<IP_ADDRESS>:57958 uri=/api/codex/v1/data code="400 Bad Request" error_msg="Unable to send response"

I'm seeing the following:
TRC 2024-10-02 10:14:52.685+02:00 Stream created                             topics="libp2p lpstream" tid=938714 s=66fd00fc07c555d6584bf4b5 objName=AsyncStreamWrapper dir=In
INF 2024-10-02 10:14:52.685+02:00 Storing data                               topics="codex node" tid=938714
TRC 2024-10-02 10:14:52.685+02:00 Reading bytes from reader                  topics="libp2p asyncstreamwrapper" tid=938714 bytes=65536
TRC 2024-10-02 10:14:52.906+02:00 CatchableError exception                   topics="codex node" tid=938714 exc="Incomplete chunk received"
ERR 2024-10-02 10:14:52.906+02:00 Unhandled exception in async proc, aborting topics="codex" tid=938714 msg="Incomplete chunk received"

I have a simple golang code which downloads a file from HTTP and passes the stream/buffer to a Codex REST API reques to upload data. When the program is killed I get the error above. It would be good if such en event did not crash the whole node:)

I've tried to reproduce this on v0.1.5 on win and unix, but I cannot. The node seems to handle interrupted uploads correctly, even multiple. No crashes. Can someone someone else plz check this one? Does this happen consistently or is it one of those bugs that happens only sometimes?

Did 3 checks in a row on macOS using v0.1.5, using the steps above - no crashes

I can see 2 different outcomes:

In some cases it results in the WARN shared by @veaceslavdoina
In some cases it results in a crash with following error:

TRC 2024-10-08 11:16:00.690+02:00 Sending block request cancellations to peers topics="codex blockexcengine" tid=1360636 addrs=1
TRC 2024-10-08 11:16:00.690+02:00 Reading bytes from reader                  topics="libp2p asyncstreamwrapper" tid=1360636 bytes=65536
TRC 2024-10-08 11:16:00.690+02:00 Reading bytes from reader                  topics="libp2p asyncstreamwrapper" tid=1360636 bytes=49152
TRC 2024-10-08 11:16:00.690+02:00 Reading bytes from reader                  topics="libp2p asyncstreamwrapper" tid=1360636 bytes=32768
TRC 2024-10-08 11:16:00.690+02:00 Reading bytes from reader                  topics="libp2p asyncstreamwrapper" tid=1360636 bytes=16384
TRC 2024-10-08 11:16:00.691+02:00 Block Stored                               topics="codex repostore" tid=1360636 cid=zDx*89QJjT
TRC 2024-10-08 11:16:00.691+02:00 Sending block request cancellations to peers topics="codex blockexcengine" tid=1360636 addrs=1
TRC 2024-10-08 11:16:00.691+02:00 Reading bytes from reader                  topics="libp2p asyncstreamwrapper" tid=1360636 bytes=65536
TRC 2024-10-08 11:16:00.691+02:00 CatchableError exception                   topics="codex node" tid=1360636 exc="Stream boundary is not reached yet"
ERR 2024-10-08 11:16:00.691+02:00 Unhandled exception in async proc, aborting topics="codex" tid=1360636 msg="Stream boundary is not reached yet"

It's not crashing anymore for me. I have the same warning as Slava.

Successfully reproduced this crash in automated dist-test. It doesn't happen every time. Fix is coming!


error on linting

Hi!
I try to lint my code and get the following error:
(node:48885) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'dependencies' of null
    at contents.map.map.info (/Users/vladimirgolotin/work/danilovsky-web/node_modules/@solid-soda/scripts/utils/projectWithDependency.js:12:33)
    at Array.map (<anonymous>)
    at projectWithDependency (/Users/vladimirgolotin/work/danilovsky-web/node_modules/@solid-soda/scripts/utils/projectWithDependency.js:11:6)
    at checkSvelteProject (/Users/vladimirgolotin/work/danilovsky-web/node_modules/@solid-soda/scripts/utils/defineProjectPlugins.js:11:5)
    at defineProjectPlugins (/Users/vladimirgolotin/work/danilovsky-web/node_modules/@solid-soda/scripts/utils/defineProjectPlugins.js:50:5)
(node:48885) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 5)
(node:48885) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Hello, thanks for reporing. Please, provide repo with minimal code for reporoduce and your Node.js version.


Question: What is the proper / recommended way to use column aliases?

I'm curious what would be the recommended / best-practice way to defining column aliases?  My goal is to allow the javascript code interacting with the Model queries (find, insert, etc.) to work with the aliases and not be required to understand what the actual column names are.  Working with actual column names in the model definition is ok.
users (table)
- uid (alias to id)
- name (alias to username)
- mail (alias to email)

From what I've gathered through the documentation, the options include...
static query / column().
This approach does seem to add the aliases, but it looks like it always adds those columns so if the user only wants the 'id' and 'email' columns, this doesn't work.
static query(...args) {
  const { ref } = UserModel;

  return super
    .query(...args)
    .column({
      id: ref('uid'),
      username: ref('name'),
      email: ref('mail'),
    });
}

select(col as alias)
Similar to the previous example, the user could do query().select('uid as id', ...) but that negates the goal of keeping the javascript code making the query from knowing the column names.
parseDatabaseJson / formatDatabaseJson
From what I understand of these two functions are that I can convert the db json to the model json and vice-versa.  So while it's not technically using column aliases, it "should" convert the quasi-alias to the table column.
Are those the only approaches to handle this?

So what I've found to actually work the best (at least so far) is to use the columnNameMappers() method.  Since I need to define a list of columns -> aliases, especially when it goes behind snake_case -> camelCase, that it made the most sense to just create an object that maps columns -> aliases and then use a custom columnNameMappers() method to read that and convert either way.  That leaves most of the work up to Objection to convert back and forth between the db and the json object.


Support variable maps

Is your feature request related to a problem? Please describe.
I often have solutions where I pass in a parameter like environmentName, with a list of say 3 or 4 allowed values. Depending on the value of that parameter, I want to specify different SKUs for resources or make other configuration changes. It's difficult to do this with the current design - the ternary operator helps but only gives me an easy way to switch out behaviour for two conditions.
Describe the solution you'd like
One option is something like a variable map, where I'd specify a variable like this:
environmentsToSkus: {
  dev: {
    appServiceSkuName: 'S1'
    appServiceCapacity: 1
  }
  test: {
    appServiceSkuName: 'P1v3'
    appServiceCapacity: 1
  }
  production: {
    appServiceSkuName: 'P1v3'
    appServiceCapacity: 5
  }
}

and then access it using a syntax like this:
resource appServicePlan 'Microsoft.Web/serverFarms@2020-06-01' = {
  name: appServicePlanName
  location: location
  sku: {
    name: findInMap(environmentsToSkus, environmentName, 'appServiceSkuName')
    capacity: findInMap(environmentsToSkus, environmentName, 'appServiceCapacity')
  }
  kind: 'app'
}

Hey @johndowns, this should be possible today with the array access syntax - e.g.:
param appServicePlanName string
param location string

@allowed([
  'dev'
  'test'
  'production'
])
param environmentName string

var environmentsToSkus = {
  dev: {
    appServiceSkuName: 'S1'
    appServiceCapacity: 1
  }
  test: {
    appServiceSkuName: 'P1v3'
    appServiceCapacity: 1
  }
  production: {
    appServiceSkuName: 'P1v3'
    appServiceCapacity: 5
  }
}

resource appServicePlan 'Microsoft.Web/serverFarms@2020-06-01' = {
  name: appServicePlanName
  location: location
  sku: {
    name: environmentsToSkus[environmentName].appServiceSkuName
    capacity: environmentsToSkus[environmentName].appServiceCapacity
  }
  kind: 'app'
}

Does that work for your scenario?

Hey thanks @anthony-c-martin - this is a nice solution. Thanks! I'll close this as I think my request is happily covered by that.


Make small tweaks to the profiling documentation

Summary

Uses ruff -e and removes --ignore-failures from hyperfine to not accidentally hide reported panics.
Document --call-graph dwarf

Test Plan
You, reviewing it :)

Current dependencies on/for this PR:

main

PR #5335   👈

This comment was auto-generated by Graphite.


A little dependency injection and tweaks to help subclassing

I'd like to be able to extend some of these classes in my own installations of Curdle, so I'm wondering if you would accept these to make it a little more flexible:

In the Router class, you were instantiating two separate FrontControllers for every request, even if neither of them were used. I've cleaned this up by declaring the route callables as closures instead.

in addition, I've added a config option to App.php 'front_controller_class', that will allow alternate FrontController classes to be instantiated (which I'll be doing soon).

Also, In order to make swapping out BusinessModels easier, I've moved its instantiation in FrontController::main() into the constructor, which is much easier to override in subclasses. main() now jsut instantiates a new businessmodel of the same class with the route parameters, when it gets them. I've also loosened up the visibility to make it easier for FrontController subclasses to swap out its dependencies in the constructor.

This will make keeping up with your upstream a heck of a lot easier for me. Thoughts?
(Please excuse the unnecessary merges near the end; i'm still getting the hang of how Github does things)

Please, see the commit ecb627a..8f16a13

That helps, thanks!
I'm interested to hear your thoughts on how best to swap out subclasses of BusinessModel.

Awesome, thanks!


Remove .aos-animate class when element is scrolled past

Hi, for a site I’m building I need some elements to disappear when the page is scrolled past them.
So I wondered if there was some way to remove the class not only when the element is below the current page fold, but also when it is scrolled past and the element is above the fold.

Made a pull request for this: #41

Hi @LucaRosaldi , sorry for such a delay. Finally I got some time and I reviewed your PR.
Thanks for creating PR with this great feature, which I think more people might be interested in.
I was thinking about it and I left a comment with my concern in PR discussion.

Could we please have this feature?

The Waypoints library has a shortcut for this. I tried both libraries and I really prefer AOS, so it could be great if AOS can add this feature.
As a workaround I was thinking on create a custom reverse animation and using a wrapper to trigger it on data-aos-anchor-placement="top-top".

Hi. Has this feature been implemented?

I'm needing this feature as well. We need to animate a box before and after a certain anchor point... For example, animate a box from left when scrolling is ~250px from anchor point. Then animate OUT same box when ~250px PAST anchor point.
So, as user is scrolling, the box will fade in from left – stay for a while as they scroll – then fade-out animate off-screen (the same way it came in - but in reverse). If user reverses scroll, it'll animate back in, stay for a while, and then fade back out a little after the anchor point. Therefore, animation will work exactly the same whether they start from the bottom of the page or top.
This isn't currently possible with AOS, is it? The way the structure is set up, it looks like this type of effect would be extremely difficult or impossible. Hopefully that's not the case.

gj bro

I just released v3.0.0-beta.1 that has new setting called mirror. That does exactly what @LucaRosaldi proposed and initially developed :)
You can play with it by installing:
yarn add aos@next

Or look at the docs: https://github.com/michalsnik/aos/tree/next

Great, but what if I want to have different animation and direction after the fade in
Let's say
"the box fade in from left – stay for a while as they scroll – then fade-out animate off-screen (fade to right, opposite way of go in)"

I just released v3.0.0-beta.1 that has new setting called mirror. That does exactly what @LucaRosaldi proposed and initially developed :)
You can play with it by installing:
yarn add aos@next

Or look at the docs: https://github.com/michalsnik/aos/tree/next

Great, but what if I want to have different animation and direction after the fade in
Let's say
"the box fade in from left – stay for a while as they scroll – then fade-out animate off-screen (fade to right, opposite way of go in)"

Any Update on this....


Need to delete stuff from the server

Is your feature request related to a problem? Please describe.
Sometimes I need to delete stuff from the server. I want to do this as easily as possible.
Describe the solution you'd like
Type reliably delete -f <file.yaml> and have it deleted.

would it be slo delete command ?

@dmartin35 , that's the plan.
So i'm thinking
reliably slo delete -m <manifest-file-containing item(s) to delete>
If they accidentally delete an objective, it can always be re-synced from the same file.
But let me know if have an alternative approach


Add a metric for the number of running scheduler job commands

What changes are proposed in this pull request?
Add a metric to measure the number of running scheduler job commands.
Why are the changes needed?
To measure the number of running scheduler commands, which can be used in the distributed copy or load.
Does this PR introduce any user facing changes?
No.

alluxio-bot, merge this please


Expected parameter 'refpolicy_makefile' of 'Class[Selinux]' to have type Stdlib::Absolutepath

Affected Puppet, Ruby, OS and module versions/distributions

Puppet:

$ puppet --verison
3.8.6

Ruby:

$ ruby --version
ruby 2.0.0p648 (2015-12-16) [x86_64-linux]

Distribution:

$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.3 (Maipo)

Module version:

$ cat /etc/puppet/environments/production/modules/selinux/metadata.json | head -n 3
{
  "name": "puppet-selinux",
  "version": "1.0.0",

How to reproduce (e.g Puppet code you use)
Update to puppet-selinux v1.0.0 and run the simple manifest:
#
class encore_rp::profile::selinux {
  class { '::selinux':
    mode => 'permissive',
  }
}

What are you seeing
The following error occurs when running puppet agent -t :
[root@nickpuppet6 ~]# puppet agent -t
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Expected parameter 'refpolicy_makefile' of 'Class[Selinux]' to have type Stdlib::Absolutepath, got String at /etc/puppet/environments/production/modules/encore_rp/manifests/profile/selinux.pp:3 on node xxx
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

What behaviour did you expect instead
The documented "Basic usage" in the readme to work without error.
Output log
Any additional information you'd like to impart

The selinux module now uses puppet types for validation, which requires Puppet 4.
I will close this issue, as Puppet 3.8.6 is not supported by 1.0.0 anymore. Puppet 3 is EOL, and I recommend you upgrade to Puppet 4 if at all possible. It's much better in addition to being actually supported.
If you can use the future parser, you can make the module 3.8.7 future parser -compatible by replacing all mentions of  Stdlib::Absolutepath with String. This makes the module a bit more brittle since the parameters won't be validated as paths, but it'll work.

Given that some EL7 users might be stuck with puppet 3.8 for various reasons, I might be persuaded to merge a patch to implement future parser -compatibility. Full Puppet 3 compatibility will not happen though, sorry :)

I have the same issue with Puppet 4 and Centos 7.
puppet --version 4.10.5
My class:
class camara_profiles::portalphp::selinux {   class { '::selinux':     mode => 'disabled',   } }
And when i run the agent:
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Expected parameter 'refpolicy_makefile' of 'Class[Selinux]' to have type Stdlib::Absolutepath, got String at /etc/puppetlabs/code/environments/test/modules/camara_profiles/manifests/portalphp/selinux.pp:2 on node vvmctphp01.redecamara.camara.gov.br

@laurosn can't reproduce.
#> BEAKER_set="centos-7-x64" PUPPET_INSTALL_TYPE="agent" be rspec spec/acceptance/class_disabled_spec.rb
...
centos-7-x64 09:44:40$ yum -y  install puppet-agent
  Loaded plugins: fastestmirror
  Loading mirror speeds from cached hostfile
   * base: pkg.adfinis-sygroup.ch
   * extras: pkg.adfinis-sygroup.ch
   * updates: pkg.adfinis-sygroup.ch
  Resolving Dependencies
  --> Running transaction check
  ---> Package puppet-agent.x86_64 0:1.10.5-1.el7 will be installed
  --> Finished Dependency Resolution

  Dependencies Resolved

  ================================================================================
   Package            Arch         Version             Repository            Size
  ================================================================================
  Installing:
   puppet-agent       x86_64       1.10.5-1.el7        puppetlabs-pc1        26 M

  Transaction Summary

...

selinux class disabled
localhost $ scp /tmp/beaker20170808-9334-19dhzvx centos-7-x64:/tmp/apply_manifest.pp.hrzlkp {:ignore => }
  should run without errors
  Package "selinux-policy-targeted"
    should be installed
  File "/etc/selinux/config"
    content
      should match /^SELINUX=disabled$/
  Command "getenforce"
    stdout
      should match /^Permissive$/
Destroying vagrant boxes
==> centos-7-x64: Forcing shutdown of VM...
==> centos-7-x64: Destroying VM and associated drives...

Finished in 1 minute 5.13 seconds (files took 1 minute 16.17 seconds to load)
4 examples, 0 failures

test created in PR: https://github.com/voxpupuli/puppet-selinux/pull/233/files#diff-c0676cae65dbee3d122d29f3330ec81bR6

Thanks @vinzent ! I really don't know if it's related with the fact that i have environments with different versions of modules (stdlib, for example). I've already tried to clean cache and restart my puppet server without success. I'll try to run your test.

@laurosn I would check your hiera data - I suspect you have set the param there? Please open a new issue if you really have a problem with the param.

I'm having this same problem on puppetlabs/centos-7.0-64-puppet.
[vagrant@localhost ~]$ puppet --version
4.2.1

I installed your module from the forge
$ puppet module install puppet-selinux --version 1.6.1

And when I evaluate the basic include it fails.
[vagrant@localhost ~]$ sudo /opt/puppetlabs/bin/puppet apply -e 'include selinux'
Error: Evaluation Error: Error while evaluating a Function Call, Expected parameter 'refpolicy_makefile' of 'Class[Selinux]' to have type Stdlib::Absolutepath, got String  at line 1:1 on node localhost.fios-router.home

@AnthonyMastrean that version of Puppet is pretty old. Can you try if it happens with a more recent version of 4.x?

Oh, wow, I hadn't realized these were so out of date (the latest is 2 years
old). Do you know if these Vagrant boxes are "abandoned", then? I'm not
sure how to update the puppet package in one of these, as they don't appear
in "yum list installed". Maybe I'll start with centos/7 and install the
latest puppet.
On Thu, Oct 25, 2018 at 3:06 AM Jarkko Oranen<EMAIL_ADDRESS>wrote:

@AnthonyMastrean https://github.com/AnthonyMastrean that version of
Puppet is pretty old. Can you try if it happens with a more recent version
of 4.x?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/voxpupuli/puppet-selinux/issues/212#issuecomment-432938527,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AANS8nLswB7daM-7v6fpwg350I_22Xnqks5uoWL-gaJpZM4M4tD-
.


Web typings acquisition doesn't work on safari

In safai
Set typescript.experimental.tsserver.web.typeAcquisition.enabled: true
Load repo such as https://insiders.vscode.dev/github/mjbvz/vscode-markdown-languageservice

bug
Notice that Initializing JS/TS language features never stops
Works fine in Chrome and Firefox
Possibly:

There's now a developer feature flag for ReadableByteStreams. Once you enable this, everything works as expected
Fingers crossed this goes stable soon
Marking as upstream as I don't think there's any work to be done on our side

Closing as this is fixed upstream. Unfortunately we can't easily work around this on our side


typo - GO:0043923

Def:
"Any process is which..."
should read:
"Any process IN which..."
Birgit

Fixed.  Thanks.


Cleanup github branches

Can we remove branches if they have been merged?

Yes, we should.

Four branches remain:

master
develop
speed
print-tree

I think speed can be deleted, it looks like it was parallelizing the HPCToolkit reader, which has been merged. @bhatele Can you confirm?


Curser is on top line of editor when it is empty

When content is empty in textarea , cursor is on top border line of editor.
You can see it in demo .
1- delete textarea content
2-click on somewhere else in page
3-click in editor.

Setting a placeholder attribute within the emojionearea-editor seems to fix this issue. Note that there has to be a value, even if it's just a space.
placeholder=" "

Placeholder " " doesn't fix. Only a placeholder with a non blank string fixes the issue.

You can use placeholder: "\xa0"(non breaking space)

Placeholder " " (space) works fine for me using latest versions of Chrome, Firefox, Opera, IE and Edge.
See: http://chat.oasiz.net/lobby

Fix emojionearea.css by adding ‘padding-top: 1em;’ to following rule seems to be better:
.emojionearea .emojionearea-editor:empty::before {
            content: attr(placeholder);

            display: block;

            color: #bbb;

            padding-top: 1em;

}


bbmap needs parameter for minid

Description of feature
It Is good to have the minid params in nextflow.config for bbmap

Solved in #282


Browser.chooseFile() sets the file to being modified in the future

From @rsshilli on March 1, 2019 21:25
Environment:

WebdriverIO version: 4.4.0
Mode: Standalone mode (packaged with Chimp)
Node.js version: 8.10.0
NPM version: 6.0.1
Browser name and version: Chrome 72.0.3626.119
Platform name and version: Windows 10
Additional wdio packages used (if applicable):

Config of WebdriverIO
I'm using WebdriverIO through Chimp.  My webdriverio configuration is:
  webdriverio: {
    logLevel: "verbose",
    logOutput: "build/test/report",
    deprecationWarnings: false,
    coloredLogs: !isBuildSystem,
    waitforTimeout: (isBuildSystem ? 120 : 30)*1000,
  },

Describe the bug
When I use browser.chooseFile(), Chrome accepts the file properly and uploads it.  Using the File API (https://www.w3.org/TR/FileAPI/) the code on my webpage is getting the file name, size, and the last modified date to show it in the UI after it's been uploaded.
When I upload a file that was last modified yesterday, the file is uploaded as having been last modified 5 hours from now!  Woah, it's like a glimpse into the future!  Except I'm pretty sure it's because I'm in  UTC-5.
After looking into the Chrome logs, I see that my original file is not the one sent to Chrome, but instead the file is being copied to a new location and being sent from there:
[15:49:40]  COMMAND	POST 	 "/wd/hub/session/fa5b1d54954b4ee5f61be6b445c83c9d/file"
[15:49:40]  DATA		{"file":"[base64] 38744 bytes"}
[15:49:40]  RESULT		"C:\\Users\\ryans\\AppData\\Local\\Temp\\scoped_dir30340_24649\\upload30340_15490\\SampleUpload2.pdf"

That's weird.  When I look at that file, it's also in the future!  Note above that I sent the file at 3:49pm
C:\> dir C:\Users\ryans\AppData\Local\Temp\scoped_dir30340_24649\upload30340_15490\SampleUpload2.pdf
 Volume in drive C is Windows
 Volume Serial Number is 407E-A66F

 Directory of C:\Users\ryans\AppData\Local\Temp\scoped_dir30340_24649\upload30340_15490

03/01/2019  08:49 PM            29,887 SampleUpload2.pdf
               1 File(s)         29,887 bytes
               0 Dir(s)  47,966,064,640 bytes free

I don't know how this magic is happening.  Is it possible that the file doesn't need to be copied?  Or maybe that the last modified date should be kept, as opposed to being set to the current time in UTC?
To Reproduce
Here's my code to use Webdriver.io to upload the file:
    let filePath = path.join(__dirname, "..", "files", fileName);
    browser.chooseFile("#uploadDocumentButton", filePath);

Here's a sample of the code in the browser that gets the date:
  let input = $("#" + event.target.id)[0];

  if (input.files) {
    let file = input.files[0];
    fileData.fileName = file.name;
    fileData.size = file.size;
    fileData.lastModified = file.lastModified;

Expected behavior
I would expect the file's original last modified date to be what I see in my JavaScript running in Chrome.
Log
Chrome log is included in the bug description above.
Additional context
My code in the browser works fine when I choose the file manually.
Copied from original issue: webdriverio/webdriverio#3665

@christian-bromann is there an equivalent to chooseFile in WDIO5?

see #3632

@christian-bromann Awesome, thanks!


Anotate class to map to scalar

Hi
I tried to incorporate Artemis with my already working Hasura endpoint, the problem is Hasura generates multiple types, and it is very confusing if I have to declare the mappers of all these in the build.yaml
Is there any planning on annotating the class to map to scalar? I think that it would be very useful

Hello @tdnghia98!
Do you have any example of how would that work?
Today, as a generator, artemis only have configurations on build.yaml file.

Hello @tdnghia98!
Do you have any example of how would that work?
Today, as a generator, artemis only have configurations on build.yaml file.

Hello @comigor
Sorry for the late reply.
The idea is like when using freezed package or json_serializable where you can simply annotate the class and there will be generated code. So for example if I can annotate a query class with @query and mutation class with @mutation and then have the generated types for the input fields and the output result that would be great. As I understand for now I have to manually write parser for these and include them in the build.yaml file

Hello @comigor
Sorry for the late reply.
The idea is like when using freezed package or json_serializable where you can simply annotate the class and there will be generated code. So for example if I can annotate a query class with @query and mutation class with @mutation and then have the generated types for the input fields and the output result that would be great. As I understand for now I have to manually write parser for these and include them in the build.yaml file


Small error in BN archive extraction command

error: [12:16:43.891] [error] Archive extraction command exited with an error (exit code: 50)
Settings for archived mods is activated. The error only appears for BN.

I can't reproduce it. Please enable debug mode and post the details it prints about the command.

[12:55:25.355] Command data: {args:[/S, /C, rmdir "D:/Games/CDDA-Game/Catapult-loader/catapult/testdir"], name:cmd} [12:55:27.391] Command exited with code 0. Output:
This one?

No. Sorry I wasn't clear enough. When debug mode is enabled, it should print additional messages when the archive extraction fails. Similar to the one you just posted, but for the actual modpack installation. So, enable debug mode, then get this error to happen again.

found this one:
[12:58:33.870] [debug] Failed command: {args:[/C, "D:/Games/CDDA-Game/Catapult-loader/catapult/utils/unzip.exe" -o "D:/Games/CDDA-Game/Catapult-loader/catapult/Bright-Nights-Kenan-Mod-Pack-master.zip" -d "D:/Games/CDDA-Game/Catapult-loader/catapult/bn/tmp"], name:cmd}

Could find the error in debug:
[13:12:10.511] Retrieving Kenan Modpack for BN... [13:12:10.511] Downloading Bright-Nights-Kenan-Mod-Pack-master.zip... [13:12:12.514] Downloading: 3.0 MB at 1.5 MB/s [13:12:13.960] Downloading: 8.0 MB at 3.5 MB/s [13:12:15.238] Downloading: 13.1 MB at 4.0 MB/s [13:12:16.479] Downloading: 18.2 MB at 4.1 MB/s [13:12:16.731] [debug] HTTPRequest info: Result: 0 Response code: 200 Headers: [Access-Control-Allow-Origin: https://render.githubusercontent.com, content-disposition: attachment; filename=BrightNights-Structured-Kenan-Modpack-master.zip, Content-Security-Policy: default-src 'none'; style-src 'unsafe-inline'; sandbox, Content-Type: application/zip, ETag: "74c44bdbcaaa85d1c41747c7ed2181f2c198efbd7da0b438c57dff08967d0875", Strict-Transport-Security: max-age=31536000, Vary: Authorization,Accept-Encoding,Origin, X-Content-Type-Options: nosniff, X-Frame-Options: deny, X-XSS-Protection: 1; mode=block, Date: Mon, 22 Nov 2021 12:12:11 GMT, Transfer-Encoding: chunked, X-GitHub-Request-Id: DF63:1715:1933B0:249E1C:619B891B] [13:12:16.731] Finished downloading Bright-Nights-Kenan-Mod-Pack-master.zip. [13:12:16.731] Extracting Bright-Nights-Kenan-Mod-Pack-master.zip... [13:12:22.027] [error] Archive extraction command exited with an error (exit code: 50) [13:12:22.027] [debug] Failed command: {args:[/C, "D:/Games/CDDA-Game/Catapult-loader/catapult/utils/unzip.exe" -o "D:/Games/CDDA-Game/Catapult-loader/catapult/Bright-Nights-Kenan-Mod-Pack-master.zip" -d "D:/Games/CDDA-Game/Catapult-loader/catapult/bn/tmp"], name:cmd}

All of this looks completely normal, up to the point where it fails.
I've looked up UnZip error codes and found this:

Any chance this could be true?

nah, disk has still 230 GB free.

funny thing is when I downloaded kenan in dda, it all went smooth.
[14:02:53.553] Downloading CDDA-Kenan-Modpack-master.zip... [14:02:55.554] Downloading: 2.6 MB at 1.3 MB/s [14:02:56.983] Downloading: 7.7 MB at 3.5 MB/s [14:02:58.348] Downloading: 12.8 MB at 3.7 MB/s [14:02:59.243] Finished downloading CDDA-Kenan-Modpack-master.zip. [14:02:59.243] Extracting CDDA-Kenan-Modpack-master.zip... [14:03:03.760] Wiping the repository... [14:03:04.861] Adding mods from the pack to repository... [14:03:05.261] Cleaning up... [14:03:06.000] All finished
The error only appears for bn.

maybe this could be the bug?
"filename": "Bright-Nights-Kenan-Mod-Pack-master.zip",
this is the only line where it is written mod-pack instead of modpack.

It shouldn't matter. This is just the name it gives to downloaded archive. It could be anything, and things would still work.
I gave it a test on Windows and still can't reproduce it. I'm kinda out of ideas.
Maybe see if the problem still reproduces with a new, clean copy of Catapult on your C: drive.

Can confirm, on a new install no error. Okay, must be some strange oddity like a bitflip.


How to make PR accepted

Hi, @larryk85.
I really appreciate your efforts to make and improve CDT. I'm sorry that I made a lot of noises (PR) which cannot be merged. Some patches resolve issues in wrong way, and others may not fit in your plan.
However, sometimes even though the contents of my patch are applied, but its application is not by merging PR, but writing new commit. For open source contributors, finding their name from the list of commits is a little pleasure. If you don't mind, can you tell me the policy of contribution in "eosio.cdt" so that open source contributors (including me) make proper PR which can be merged to repository?
I understand you might be too busy to review PR in poor quality, but what about giving people a chance to improve their patches to grow up to be experienced ones like you? :)

Hey, I'm sorry conr2d. It wasn't my intention to rob you of that.  We have had some problems with some of the last releases with submodule changes flying in under the radar and not being tracked appropriately, so I was trying to mitigate that.  I will be more mindful and personally evaluate yours and anyone else's PRs that is currently in the pull requests section and merge those directly.  There is a new safeguard that got put in place last week, so that new PRs will not have this issue.  So, please continue to PR and I will gladly merge those into the code base if they make sense and comment for you to make the appropriate changes if they need to be made.

@larryk85 No problem. Thank you for your kind response! 👍


Error in NullConstraintChecker and other checkers

I run the tool with a config file that was generated from it, and get this:
<===begin===>
Metadata:
model: Identifier
column: id
checker: DatabaseConsistency::Checkers::NullConstraintChecker
Stack trace:
/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `block in find': undefined method `include?' for nil:NilClass (NoMethodError)

      configuration.find { |(k, _)| k.include?('*') && key.match?(generate_regexp(k)) }&.last
                                     ^^^^^^^^^
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `find'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `find'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:40:in `block in enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:39:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:39:in `enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/checkers/base_checker.rb:41:in `enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/checkers/base_checker.rb:34:in `report_if_enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/columns_processor.rb:29:in `block (6 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:20:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:8:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/columns_processor.rb:27:in `block (5 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/columns_processor.rb:26:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/columns_processor.rb:26:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/columns_processor.rb:26:in `block (4 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:20:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:8:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/columns_processor.rb:25:in `block (3 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/columns_processor.rb:24:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/columns_processor.rb:24:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/columns_processor.rb:24:in `block (2 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:20:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:8:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/columns_processor.rb:20:in `block in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/columns_processor.rb:19:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/columns_processor.rb:19:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/columns_processor.rb:19:in `check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:31:in `reports'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:16:in `block in reports'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:15:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:15:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:15:in `reports'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency.rb:112:in `run'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/bin/database_consistency:78:in `<top (required)>'
	from /ruby/3.2.2/bin/database_consistency:25:in `load'
	from /ruby/3.2.2/bin/database_consistency:25:in `<top (required)>'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli/exec.rb:58:in `load'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli/exec.rb:58:in `kernel_load'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli/exec.rb:23:in `run'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli.rb:492:in `exec'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli.rb:34:in `dispatch'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli.rb:28:in `start'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/exe/bundle:45:in `block in <top (required)>'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/friendly_errors.rb:117:in `with_friendly_errors'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/exe/bundle:33:in `<top (required)>'
	from /ruby/3.2.2/bin/bundle:25:in `load'
	from /ruby/3.2.2/bin/bundle:25:in `<main>'
<===end===>
<===begin===>
Metadata:
model: Identifier
attribute: owner
checker: DatabaseConsistency::Checkers::MissingUniqueIndexChecker
Stack trace:
/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `block in find': undefined method `include?' for nil:NilClass (NoMethodError)

      configuration.find { |(k, _)| k.include?('*') && key.match?(generate_regexp(k)) }&.last
                                     ^^^^^^^^^
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `find'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `find'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:40:in `block in enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:39:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:39:in `enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/checkers/base_checker.rb:41:in `enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/checkers/base_checker.rb:34:in `report_if_enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_processor.rb:29:in `block (7 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:20:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:8:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_processor.rb:27:in `block (6 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_processor.rb:26:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_processor.rb:26:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_processor.rb:26:in `block (5 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:20:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:8:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_processor.rb:25:in `block (4 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_processor.rb:24:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_processor.rb:24:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_processor.rb:24:in `block (3 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_processor.rb:21:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_processor.rb:21:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_processor.rb:21:in `block (2 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:20:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:8:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_processor.rb:17:in `block in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_processor.rb:16:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_processor.rb:16:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_processor.rb:16:in `check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:31:in `reports'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:16:in `block in reports'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:15:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:15:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:15:in `reports'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency.rb:112:in `run'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/bin/database_consistency:78:in `<top (required)>'
	from /ruby/3.2.2/bin/database_consistency:25:in `load'
	from /ruby/3.2.2/bin/database_consistency:25:in `<top (required)>'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli/exec.rb:58:in `load'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli/exec.rb:58:in `kernel_load'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli/exec.rb:23:in `run'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli.rb:492:in `exec'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli.rb:34:in `dispatch'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli.rb:28:in `start'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/exe/bundle:45:in `block in <top (required)>'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/friendly_errors.rb:117:in `with_friendly_errors'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/exe/bundle:33:in `<top (required)>'
	from /ruby/3.2.2/bin/bundle:25:in `load'
	from /ruby/3.2.2/bin/bundle:25:in `<main>'
<===end===>
<===begin===>
Metadata:
model: Identifier
association: versions
checker: DatabaseConsistency::Checkers::MissingIndexChecker
Stack trace:
/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `block in find': undefined method `include?' for nil:NilClass (NoMethodError)

      configuration.find { |(k, _)| k.include?('*') && key.match?(generate_regexp(k)) }&.last
                                     ^^^^^^^^^
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `find'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `find'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:40:in `block in enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:39:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:39:in `enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/checkers/base_checker.rb:41:in `enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/checkers/base_checker.rb:34:in `report_if_enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/associations_processor.rb:28:in `block (6 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:20:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:8:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/associations_processor.rb:26:in `block (5 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/associations_processor.rb:25:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/associations_processor.rb:25:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/associations_processor.rb:25:in `block (4 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:20:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:8:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/associations_processor.rb:24:in `block (3 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/associations_processor.rb:23:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/associations_processor.rb:23:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/associations_processor.rb:23:in `block (2 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:20:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:8:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/associations_processor.rb:19:in `block in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/associations_processor.rb:18:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/associations_processor.rb:18:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/associations_processor.rb:18:in `check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:31:in `reports'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:16:in `block in reports'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:15:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:15:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:15:in `reports'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency.rb:112:in `run'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/bin/database_consistency:78:in `<top (required)>'
	from /ruby/3.2.2/bin/database_consistency:25:in `load'
	from /ruby/3.2.2/bin/database_consistency:25:in `<top (required)>'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli/exec.rb:58:in `load'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli/exec.rb:58:in `kernel_load'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli/exec.rb:23:in `run'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli.rb:492:in `exec'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli.rb:34:in `dispatch'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli.rb:28:in `start'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/exe/bundle:45:in `block in <top (required)>'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/friendly_errors.rb:117:in `with_friendly_errors'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/exe/bundle:33:in `<top (required)>'
	from /ruby/3.2.2/bin/bundle:25:in `load'
	from /ruby/3.2.2/bin/bundle:25:in `<main>'
<===end===>
<===begin===>
Metadata:
model: Identifier
attribute: owner
checker: DatabaseConsistency::Checkers::ColumnPresenceChecker
Stack trace:
/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `block in find': undefined method `include?' for nil:NilClass (NoMethodError)

      configuration.find { |(k, _)| k.include?('*') && key.match?(generate_regexp(k)) }&.last
                                     ^^^^^^^^^
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `find'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `find'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:40:in `block in enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:39:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:39:in `enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/checkers/base_checker.rb:41:in `enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/checkers/base_checker.rb:34:in `report_if_enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_fractions_processor.rb:27:in `block (6 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:20:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:8:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_fractions_processor.rb:25:in `block (5 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_fractions_processor.rb:24:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_fractions_processor.rb:24:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_fractions_processor.rb:24:in `block (4 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:20:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:8:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_fractions_processor.rb:21:in `block (3 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_fractions_processor.rb:20:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_fractions_processor.rb:20:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_fractions_processor.rb:20:in `block (2 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:20:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:8:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_fractions_processor.rb:16:in `block in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_fractions_processor.rb:15:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_fractions_processor.rb:15:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/validators_fractions_processor.rb:15:in `check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:31:in `reports'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:16:in `block in reports'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:15:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:15:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:15:in `reports'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency.rb:112:in `run'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/bin/database_consistency:78:in `<top (required)>'
	from /ruby/3.2.2/bin/database_consistency:25:in `load'
	from /ruby/3.2.2/bin/database_consistency:25:in `<top (required)>'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli/exec.rb:58:in `load'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli/exec.rb:58:in `kernel_load'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli/exec.rb:23:in `run'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli.rb:492:in `exec'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli.rb:34:in `dispatch'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli.rb:28:in `start'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/exe/bundle:45:in `block in <top (required)>'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/friendly_errors.rb:117:in `with_friendly_errors'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/exe/bundle:33:in `<top (required)>'
	from /ruby/3.2.2/bin/bundle:25:in `load'
	from /ruby/3.2.2/bin/bundle:25:in `<main>'
<===end===>
<===begin===>
Metadata:
model: Identifier
index: index_identifiers_on_organization_id
checker: DatabaseConsistency::Checkers::UniqueIndexChecker
Stack trace:
/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `block in find': undefined method `include?' for nil:NilClass (NoMethodError)

      configuration.find { |(k, _)| k.include?('*') && key.match?(generate_regexp(k)) }&.last
                                     ^^^^^^^^^
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `find'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `find'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:40:in `block in enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:39:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:39:in `enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/checkers/base_checker.rb:41:in `enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/checkers/base_checker.rb:34:in `report_if_enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/indexes_processor.rb:28:in `block (6 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:20:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:8:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/indexes_processor.rb:26:in `block (5 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/indexes_processor.rb:25:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/indexes_processor.rb:25:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/indexes_processor.rb:25:in `block (4 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:20:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:8:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/indexes_processor.rb:24:in `block (3 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/indexes_processor.rb:23:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/indexes_processor.rb:23:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/indexes_processor.rb:23:in `block (2 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:20:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:8:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/indexes_processor.rb:17:in `block in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/indexes_processor.rb:16:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/indexes_processor.rb:16:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/indexes_processor.rb:16:in `check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:31:in `reports'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:16:in `block in reports'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:15:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:15:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:15:in `reports'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency.rb:112:in `run'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/bin/database_consistency:78:in `<top (required)>'
	from /ruby/3.2.2/bin/database_consistency:25:in `load'
	from /ruby/3.2.2/bin/database_consistency:25:in `<top (required)>'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli/exec.rb:58:in `load'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli/exec.rb:58:in `kernel_load'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli/exec.rb:23:in `run'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli.rb:492:in `exec'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli.rb:34:in `dispatch'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli.rb:28:in `start'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/exe/bundle:45:in `block in <top (required)>'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/friendly_errors.rb:117:in `with_friendly_errors'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/exe/bundle:33:in `<top (required)>'
	from /ruby/3.2.2/bin/bundle:25:in `load'
	from /ruby/3.2.2/bin/bundle:25:in `<main>'
<===end===>
<===begin===>
Metadata:
model: Identifier
enum: identifier_type
checker: DatabaseConsistency::Checkers::EnumTypeChecker
Stack trace:
/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `block in find': undefined method `include?' for nil:NilClass (NoMethodError)

      configuration.find { |(k, _)| k.include?('*') && key.match?(generate_regexp(k)) }&.last
                                     ^^^^^^^^^
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `find'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `find'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:40:in `block in enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:39:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:39:in `enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/checkers/base_checker.rb:41:in `enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/checkers/base_checker.rb:34:in `report_if_enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/enums_processor.rb:24:in `block (6 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:20:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:8:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/enums_processor.rb:22:in `block (5 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/enums_processor.rb:21:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/enums_processor.rb:21:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/enums_processor.rb:21:in `block (4 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:20:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:8:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/enums_processor.rb:20:in `block (3 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/enums_processor.rb:19:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/enums_processor.rb:19:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/enums_processor.rb:19:in `block (2 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:20:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:8:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/enums_processor.rb:15:in `block in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/enums_processor.rb:14:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/enums_processor.rb:14:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/enums_processor.rb:14:in `check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:31:in `reports'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:16:in `block in reports'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:15:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:15:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:15:in `reports'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency.rb:112:in `run'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/bin/database_consistency:78:in `<top (required)>'
	from /ruby/3.2.2/bin/database_consistency:25:in `load'
	from /ruby/3.2.2/bin/database_consistency:25:in `<top (required)>'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli/exec.rb:58:in `load'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli/exec.rb:58:in `kernel_load'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli/exec.rb:23:in `run'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli.rb:492:in `exec'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli.rb:34:in `dispatch'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli.rb:28:in `start'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/exe/bundle:45:in `block in <top (required)>'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/friendly_errors.rb:117:in `with_friendly_errors'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/exe/bundle:33:in `<top (required)>'
	from /ruby/3.2.2/bin/bundle:25:in `load'
	from /ruby/3.2.2/bin/bundle:25:in `<main>'
<===end===>
<===begin===>
Metadata:
model: Webhook::Subscription
checker: DatabaseConsistency::Checkers::MissingTableChecker
Stack trace:
/ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `block in find': undefined method `include?' for nil:NilClass (NoMethodError)

      configuration.find { |(k, _)| k.include?('*') && key.match?(generate_regexp(k)) }&.last
                                     ^^^^^^^^^
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `find'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:58:in `find'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:40:in `block in enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:39:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/configuration.rb:39:in `enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/checkers/base_checker.rb:41:in `enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/checkers/base_checker.rb:34:in `report_if_enabled?'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/models_processor.rb:22:in `block (4 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:20:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:8:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/models_processor.rb:20:in `block (3 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/models_processor.rb:19:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/models_processor.rb:19:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/models_processor.rb:19:in `block (2 levels) in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:20:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/debug_context.rb:8:in `with'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/models_processor.rb:15:in `block in check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/models_processor.rb:14:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/models_processor.rb:14:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/models_processor.rb:14:in `check'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:31:in `reports'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:16:in `block in reports'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:15:in `each'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:15:in `flat_map'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency/processors/base_processor.rb:15:in `reports'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/lib/database_consistency.rb:112:in `run'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/database_consistency-1.7.22/bin/database_consistency:78:in `<top (required)>'
	from /ruby/3.2.2/bin/database_consistency:25:in `load'
	from /ruby/3.2.2/bin/database_consistency:25:in `<top (required)>'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli/exec.rb:58:in `load'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli/exec.rb:58:in `kernel_load'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli/exec.rb:23:in `run'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli.rb:492:in `exec'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli.rb:34:in `dispatch'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/cli.rb:28:in `start'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/exe/bundle:45:in `block in <top (required)>'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/lib/bundler/friendly_errors.rb:117:in `with_friendly_errors'
	from /ruby/3.2.2/lib/ruby/gems/3.2.0/gems/bundler-2.4.12/exe/bundle:33:in `<top (required)>'
	from /ruby/3.2.2/bin/bundle:25:in `load'
	from /ruby/3.2.2/bin/bundle:25:in `<main>'
<===end===>

Facing this same issue, the problem is that if I generate todos with the -g flag, for the missing table inconsistency the yaml looks like
ModelName:
  ! '':
    MissingTableChecker:
      enabled: false

This when fed into the checker again results in an undefined include? for nil class error at
configuration.find { |(k, _)| k.include?('*') && key.match?(generate_regexp(k)) }&.last

database_consistency/configuration.rb:58:in each'`
For now, I've disabled the MissingTableChecker with
DatabaseConsistencyCheckers:
  All:
    enabled: true
  MissingTableChecker:
    enabled: false

For me it was reporting a false negative anyways, the table does exist.

Hi @adamk9k @pmackay!
Thank you for reporting this! It will be fixed in the next release: https://github.com/djezzzl/database_consistency/pull/244


ChRIS Website: Update illustrations on chrisproject.org

(@madelinepeck)

Here's Madeline's initial sketches:

Comments, feedback definitely welcomed!

Comments, feedback definitely welcomed!

Which page's illustrations do you want to update on chrisproject.org?
I remembered the coloring books you designed that has possibly similar concept with the above sketches.

SE Linux
Container commandos
Container

I just searched the URLs by internet.

There are some videos trying to explain simply a difficult thing. I imagine the illustrations can be used like the concept.

Meltdown and Spectre in 3 Minutes
https://www.youtube.com/watch?v=syAdX44pokE
Actually the ranking top 3 popular videos in Red Hat Videos are this kind of video.
https://www.youtube.com/user/Kurzgesagt


No reload on item selection??

Sorry, if this request is going as a bug, I am new and do not know how github works.
I am using this hidden_drawer_menu, I have one Pageview which gets data from the json which is first item in the menu selection.
Everytime I click on this selection, the page reloads which should not happen.
Can you please update the code to get this functionality ?
Thanks in advance !!!

@RafaelBarbosatec , Anything on this ????

Have you tried using stateful widget?

@RafaelBarbosatec, can you please help me, how to use one ?


HHH-15654 Criteria APIs for window and ordered-set aggregate functions

https://hibernate.atlassian.net/browse/HHH-15654

This is looking really nice.
One comment: I would much prefer to see overloads of methods like listagg() than asking users to pass in null arguments.

One comment: I would much prefer to see overloads of methods like listagg() than asking users to pass in null arguments.

Sure thing, I thought about it but was worried of making the interface "too crowded". Added them now.

Looks like a great first attempt at this. I looked over it like you requested and provided some feedback and some ideas for supporting the rest of the window/aggregate functionalities.

Thanks @beikov, I'll go over your suggestions and update the PR

Could you please add @Incubating to the new API methods and classes/interfaces? After that, we can merge this.


added sign-in and sign-up

added sign-in and sign-up.
insert: JWT_SECRET:"secret" to .env

i think you didn't add validation functionality in frontend.
For instances is email is valid or not, password at least 8 character long , contain a number , contain a special character.
Do we store user password as plain text or as hash.
(ignore any message if you add this functionality)

Please check the issue - #22 .

I have mentioned the database and table name to use.
password is stored as plain text
On clicking login button -> it should redirect to /dashboard.
token is not getting stored in local storage

Apart from this - I have added JWT_SECRET to vercel environment variables so that it will work on live :)

changes:

database and collection name renamed.
password is storing as hash now.
redirect to dashboard if sign-in is successful.

if did nothing change with de storing of the token. if i sign-in the token is stored in the localstorage of the browser.


Userscript Not Working in SmartCookieWeb Browser

SmartCookieWeb is a popular lightweight browser for Android (it runs on the system WebView), and it features a userscript manager.
Unfortunately, your script does not appear to work with it (perhaps because this is a mobile device?), with none of the buttons appearing on the page, even if I set the user agent to desktop.
I do not use Discord, due to privacy not being respected there, so I cannot post the issue there (and what is the point of this GitHub repo, if not for issue reporting?).

The GitHub repository exists because it makes pull requests easy and it is the most well-known host for open-source code. We use issues for bug reports attached to PRs and other cases where a "civilized" discussion is useful, not for support questions where a chat is more convenient.
I haven't used SmartCookieWeb before, but does it follow all of the standards that userscript managers like Tampermonkey use?

Thanks for clarifying, I was confused whether the actual development was here it not. Sorry for coming of a ride.
Regarding the userscript standards, I'll ask.

Sorry it took so long, the dev didn't have the chance to look at my issue until now (my issue was marked as stale 2 or 3 times, forcing me to bump it to prevent it from being automatically closed).
Here is the relevant excerpt from his answer: "...@match , @include , @run-at and @grant UserScript header attributes. @resource is supported in some circumstances. ..."

@PeterNjeim Thanks, I'll open an issue there when I have the time.

Reopened as https://github.com/LibreScore/dl-librescore/issues/13
(I can't transfer issue across organizations)


add discord link to homepage

added discord link to list of links
kept the style mostly the same, made the links slightly smaller so they fit inline without much change and work in:

responsive chrome
iphone 14 pro max
iphone XR
iphone SE
pixel 7
samsung galaxy s8
ipad mini
ipad air
ipad pro

#359  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @chrisaddy and the rest of your teammates on  Graphite


data dir not installing via conda-forge

pyrise version:
Python version: 3.9.5
Operating System: Centos7

Description
Installation via conda-forge is not installing the data directory. Perhaps because it does not have an __init__.py file and/or it is not specified in the setup.py.
What I Did
conda create -n hiproc
conda activate hiproc
mamba install -c conda-forge hiproc
condo activate --stack isis5.0.0
hiproc

> `FileNotFoundError: [Errno 2] No such file or directory: '/home/jlaura/anaconda3/envs/hiproc/lib/python3.9/site-packages/hiproc/data/HiJitReg.conf'`

As a work around, I cloned the repo and copied the data files over, so not a big issue.

Hmmmm, maybe I didn't understand the package_data element in setup.py as well as I thought, or maybe I understand it just fine, but I need to do extra work via conda-forge.  I'll work on it.

Ah, needed to have things in MANIFEST.in also, duh.  The new 0.7.0 release (which will propagate to conda-forge soon, I'm sure) will have that, and some other improvements.  However, after that, I realized that I left out a dependency: multidict.  So you'll need to manually conda install multidict to get 0.7.0 to work (grr).  I probably screwed up some other stuff, so I'll hold off on cutting 0.7.1 to make sure that the data directory and other things are working as expected.


Enable spotless to fix markdown formatting and refactor faq.md as an example

Purpose of the pull request

Enable spotless to fix markdown formatting.
This PR closes: #11364

Brief change log

Enable spotless to fix markdown formatting.
Refactor faq.md as an example.

Verify this pull request

Verified by manual tests.

Codecov Report

Merging #11384 (295454a) into dev (8ad6e10) will decrease coverage by 0.32%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev   #11384      +/-   ##
============================================
- Coverage     40.25%   39.92%   -0.33%
+ Complexity     4842     4596     -246
============================================
  Files           974      967       -7
  Lines         37323    36625     -698
  Branches       4142     4082      -60
============================================
- Hits          15023    14623     -400
+ Misses        20754    20491     -263
+ Partials       1546     1511      -35

Impacted Files
Coverage Δ

.../dolphinscheduler/common/utils/ParameterUtils.java
58.53% <ø> (ø)

...e/dolphinscheduler/dao/entity/ProcessInstance.java
0.00% <0.00%> (-65.57%)
:arrow_down:

...ache/dolphinscheduler/dao/entity/TaskInstance.java
40.90% <0.00%> (-23.63%)
:arrow_down:

...er/master/dispatch/host/assign/RandomSelector.java
77.77% <0.00%> (-5.56%)
:arrow_down:

.../org/apache/dolphinscheduler/common/Constants.java
78.26% <0.00%> (-5.08%)
:arrow_down:

...uler/api/controller/ProcessInstanceController.java
70.21% <0.00%> (-1.89%)
:arrow_down:

...dolphinscheduler/remote/future/ResponseFuture.java
81.96% <0.00%> (-1.64%)
:arrow_down:

...r/plugin/task/sqoop/parameter/SqoopParameters.java
55.12% <0.00%> (-1.29%)
:arrow_down:

...er/master/builder/TaskExecutionContextBuilder.java
63.46% <0.00%> (-1.25%)
:arrow_down:

...r/server/master/registry/MasterRegistryClient.java
44.30% <0.00%> (-0.82%)
:arrow_down:

... and 83 more

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

As soon as this one merged, I will start to work on https://github.com/apache/dolphinscheduler/issues/11385

Our FAQ has the html syntax IMG, I think spotless can not auto-fix it, but we should at less find it out, also the other markdown syntax error, or warning

Our FAQ has the html syntax IMG, I think spotless can not auto-fix it, but we should at less find it out, also the other markdown syntax error, or warning. ref #11385 (comment)

Thx for the information, I will take a look.

Our FAQ has the html syntax IMG, I think spotless can not auto-fix it, but we should at less find it out, also the other markdown syntax error, or warning. ref #11385 (comment)

FYI @zhongjiajie I also submitted an issue for Spotless to see if there is anything we could do to fix http code formatting in markdown by Spotless. https://github.com/diffplug/spotless/issues/1272

I guess the reason why we have html code in markdown is to resize the images: https://www.markdownguide.org/hacks/#image-size
With markdown syntax instead of using html, we could insert images but could not resize them. Should we replace those html code? @zhongjiajie

@zhongjiajie It would take some more time for me to add several docs checks in CI and I think that is out of the scope of this PR. Therefore, I'm going to merge this one so that markdown files could get well-formatted from now on. For CI checks mentioned in the comments above, I will submit another PR later to issue: #11347


Semantic versioning of 2.7.5 to 3.0.0.

There was just the release of 2.7.5 but it doesn't seam to be just a bugfix of 2.7.4, it changes behaviour so should be 3.0.0 if we are to follow https://semver.org/:
Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.
Finally we could enforce following the semantic versioning scheme going forward, so that people know what is happening when they upgrade from previous versions.

Further, I was not aware this was going to be officially released until excessive testing was done on testnet...there are already mainnet notes popping up because of this release.

Should be 3.0 and pre-release

@canesin, my friend, I think that this has been solved and good standards are being followed.
However, you are a master in it, thus, fell free to keep pushing good ideas and practices.
I will leave it closed for now.


Fix for mergo dev to dev upgrade issue

Please check the type of change your PR introduces:

[x] Bugfix
[ ] Feature Enhancement
[ ] Test Automation
[ ] Code Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Community Operator listing
[ ] Other (please describe):

What is the current behavior?

We encountered dev to dev upgrade while updating pod security context from below values to empty struct
PodSecurityContext{
RunAsUser: 10001,
RunAsGroup: 10001,
runAsNonRoot: true,
}

What is the new behavior?

As it is mergo issue where merging of empty struct is not supported. We updated pod security context to default values using WithoutDereference option along WithOverride in mergo.
Default values of pod security context as below. we should see these default values for all sidecars after dev to dev upgrade or release to latest dev upgrade with this fix.
PodSecurityContext{
RunAsUser: 0,
RunAsGroup:  0,
runAsNonRoot: false,
}

How risky is this change?

[ ] Small, isolated change
[ x] Medium, requires regression testing
[ ] Large, requires functional and regression testing

Image: quay.io/hemalatha_gajendran/operator_mergo_defaultvalues:latest

@deeghuge @amdabhad can you please help review this PR ?


I added the "will you have a good day" question

Thanks @ChloeL19 I merged your code to the main branch.


Documentation does not include content to manage security using power shell

I would like to add users to reader role using power shell script. I could not find that content in this article. Could you please add a section on how to add/remove users to specific roles of Cosmos DB account.
Can we perform the same using Arm Templates?
Thanks
Venkat

@venkat-vangal -
Thank you for your question.
Can you please share with us the URL of the document that you are having issues with?
Please note that we scope issues on this repo to feedback related to the docs. If you have a product question, please post it on Microsoft QnA or Stack Overflow. Thank you for your understanding.

@venkat-vangal  - Can you please share with us the URL of the document that you are having issues with?
Please note that we scope issues on this repo to feedback related to the docs. If you have a product question, please post it on Microsoft QnA or Stack Overflow. Thank you for your understanding.

@venkat-vangal -
Since we have not heard back from you we will now proceed to close this thread.
However if you can share additional information regarding the documentation you are referring and circle back on this thread , we will gladly reopen the issue and continue the discussion. Thank you.


:seedling: Bump cert-manager version v1.13.0 -> v1.14.0

What this PR does / why we need it:
Bump cert-manager version v1.13.0 -> v1.14.0
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #1548

/ok-to-test

/test-centos-e2e-integration-main
/test-ubuntu-integration-main

/test-e2e-upgrade-main-from-release-1-6

/approve

Unrelated flakes
/test-ubuntu-integration-main
/test-e2e-upgrade-main-from-release-1-6

/test-e2e-upgrade-main-from-release-1-6

/test-e2e-upgrade-main-from-release-1-6

/test-e2e-upgrade-main

/override test-e2e-upgrade-main-from-release-1-6

/test-e2e-upgrade-main

/test-e2e-upgrade-main

/test-e2e-upgrade-main

Hey is there a reason to not update to the latest patch release 1.14.4 ?

Hey is there a reason to not update to the latest patch release 1.14.4 ?

I just used the version given in the linked issue

/test-e2e-upgrade-main

/test-e2e-upgrade-main

/test-e2e-upgrade-main

@adilGhaffarDev why dont I see any trigger here ?

/test-e2e-upgrade-main

/test-e2e-upgrade-main

/test-e2e-upgrade-main

/test-upgrade-main

/hold cancel

test-e2e-upgrade-main has succeeded here https://jenkins.nordix.org/job/metal3_capm3_main_clusterctl_upgrade_test/2/console but the status is not updated for some reason

test-e2e-upgrade-main has succeeded here https://jenkins.nordix.org/job/metal3_capm3_main_clusterctl_upgrade_test/2/console but the status is not updated for some reason

/override test-e2e-upgrade-main