Scott E. MacKenzie

**Same problem here.** redmine@project:~/redmine$ rake redmine:plugins:migrate NAME=redmine_knowledgebase RAILS_ENV=production --trace *\* Invoke redmine:plugins:migrate (first_time) *\* Invoke environment (first_time) *\* Execute environment *\* Execute redmine:plugins:migrate Migrating redmine_knowledgebase (Knowledgebase)... == 20100210212009 CreateCategories: migrating...

I am not sure how best to handle it, but what about an append to the naming convention to ensure no conflict with other plugins? kb_

PS: I have tried release 3.2 (same issue).

Log below: Migrating redmine_knowledgebase (Knowledgebase)... == 20130513154700 AddTagsAndTaggings: migrating =============================== rake aborted! StandardError: An error has occurred, all later migrations canceled: A plugin is already using the "tags" or "taggings"...

Direct request to LocalAI for models returns the model list: `❯ curl http://localhost:8080/v1/models {"object":"list","data":[{"id":"Dollyv2-3B","object":"model"},{"id":"GPT4All-J-13B-Snoozy","object":"model"},{"id":"MPT-7B-Chat","object":"model"},{"id":"RedPajama-INCITE-Chat-3B","object":"model"},{"id":"ggml-gpt4all-j","object":"model"},{"id":"llama-2-13b-chat","object":"model"},{"id":"llama-2-7b-chat","object":"model"}]}%`

Also, noticed in console CORS errors: `Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:8080/v1/models. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 200. Error: TypeError:...