blueprint | Magical blueprints for procedural generation

be sure that the ref-column has exact the same type as the source column (signed, unsigned etc.)

You should really encrypt them before the application goes into production. Otherwise, you probably want an alphanumeric column, like CHAR(9) or VARCHAR(9).

That error has to do with the string length. By default, laravel's creates string columns with a length of 255 using the charset/collation utf8mb4 (4-byte UTF-8 Unicode Encoding).

Simply lower the default setting in your AppServiceProvider class. (app\Providers\AppServiceProvider.php)

First, a few naming conventions that are probably not (but may be) contributing to the issues here:

• By convention, package names begin with a single capital, so I would recommend changing the name to Blueprint everywhere
• By default, ] test runs tests found in the test/runtests.jl, so I would recommend naming your top-level testing script runtests.jl to avoid confusion, even though it does seem from the errors here that test is finding your test_blueprint.jl file one way or another.

Now, while I can't test this without the full code of your package, what I suspect is happening here is the following:

• Normally, dependencies of the package you are testing (let's say MyPackage) are not required in test/Project.toml because they are implicit in MyPackage. So after a successful using MyPackage, while they will still not be available to any functions written in your test scripts (test/runtests.jl), will be available to the functions written in MyPackage -- just as if you had typed ]using MyPackage at the REPL and then run your test code there. This is the only reason you don't normally need to duplicate all the deps from the main Project.toml in test/Project.toml.
• Since the using Blueprint approach is failing here for other reasons, when you simply include the code from src/blueprint.jl, the usings within that file will in turn fail because those packages are not present in the active environment at test/Project.toml (even if they are present on your system elsewhere).
• Consequently, one quick fix to your problem with the current include("../src/blueprint.jl") approach would be to simply add those dependencies to your test/Project.toml

However, it would be more satisfying to fix the problem you are having with using Blueprint. I don't have enough information to debug this without seeing the full structure of your packages, but I would suggest as a start

• making sure that your code is properly structured as a package
• testing that, even if unregistered, you can ] add your package from the REPL by git repo URL (i.e. ] add https://some_website.com/you/Blueprint.jl)

EDIT: Upon inspection of the code linked in the comments (https://github.com/jonasseglare/Blueprint), a few other issues:

• Although they are already installed by default, standard libraries these days do need to be included in [deps]. In this case, that means the LinearAlgebra stdlib
• Any packages you are explicitly using in your test scripts, other than your package itself, do need to be added to test/Project.toml. I.e., any packages that you are directly using functions from in your test scripts (rather than just indirectly using via the exported functions of your package) do need to be included in test/Project.toml. In your case, the latter would appear to mean LinearAlgebra and FunctionalCollections, but not Setfield (that one only needs to be included in the regular Project.toml, since it's not being directly used in runtests.jl).

Consequently, with a few minor changes to your repo we are able to simply

Same problem here. Tried different settings but with no solution.

Workaround: Downgrade RabbitMQ to 3.8. After downgrading there were no connection errors anymore. So, I think it must have something to do with different behavior of v3.9.

If you are the only one working on that branch, you should do a git rebase -i (interactive rebase) in order to re-order your commits, putting first the one that should be merged to master, and leaving as most recent the one for branch only.

You're missing the CSRF token in your form which is causing the error.

You should add the CSRF token in your form and send it with the post request.

Add @csrf within the

Mongoose has just updated and in 6+ version we have to pass the object as first parameter followed by call back function with params of error and result of query!!

To GET ALL records just pass the empty object.