Welcome @lakhithaD, you're exactly the kind of user I have been expecting to discover Drupal, and realize the enormous power for web site building it contains out of the box, but also with contrib modules. I am sure we will see many more of your kind over the next few years. Also, note that the "paid modules" concept don't really exist in Drupal, as much as in WordPress.
If you haven't already tried it, perhaps check out Starshot? It's an attempt at making a more usable Drupal, out of the box:
I don't have the answers to your questions, maybe someone else can answer those. But I am pretty sure they can be solved in Drupal.
You're welcome @Kristen Pol, thanks for all the great work you are doing with Project Browser!
Since it looks like this issue is fixed, will you be setting credits, or perhaps someone else will? I ask because during the last year, automatic crediting in issues has been disabled, to avoid cheating ... I am not sure this was such a great idea, because now maintainers need to actively set them, after an issue reaches the "Fixed" status ... and credit is sometimes not set.
For more about crediting, see #3395901-27: Use Gitlab CI in Simplenews → . (though, you likely are already aware of this ...)
Perfect @Marcus_Johansson, thanks for confirming! I asked @hansfn, because so many doc pages elsewhere end up in limbo without menu item .... But great to know that maintainers do get an alert. Then all is well in that aspect.
Do feel free to add me as AI doc maintainer, there may be more AI doc pages to be created, updated, etc. in the future.
And there's no hurry -- as you may have seen, I got the Ollama Provider working. So take your time to get well, take some C-vitamin, drink some tea, and so on, until you're on top again :-)
Thanks @hansfn! Is there a way, to better make sure that doc maintainers such as AI team are notified and made aware, when a new page is created?
Update Issue Summary.
Update command example DDEV to $ curl host.docker.internal:11434/api/tags.
I found the missing piece of the puzzle. Maybe there's a better way? Anyhow, I needed to also start Ollama, which I assumed ollama serve would take care of, but looks like it doesn't ... I absolutely be mistaken, and doing something wrong?
I tried to write a list of the steps, and created AI > How to set up a provider → .
Add Ollama provider documentation.
Perhaps someone can add it in the menu, or add me to the AI module doc team?
Thanks for the video, it's great!
(It looks like the bottom of the screen is missing, where the commands are shown ... also, perhaps you could consider making the fonts slightly bigger in your videos? But let me emphasize that I very much appreciate your videos, they really are very good. The smallish font is only a minor beauty mark.)
I tried to follow your tips, and am getting close, though I can't connect to the models ...
Firewall
In Debian 12, I opened port 11434 for Ollama in ufw, using Gufw:
- Open "Report"
- Select "ollama"
- Click "+" to create rule
- Select "Policy: Allow" and "Direction: Both"
... which created this rule:
$ sudo iptables -S
[...]
-A ufw-user-input -p tcp -m tcp --dport 11434 -j ACCEPT
-A ufw-user-output -p tcp -m tcp --dport 11434 -j ACCEPTOllama
Stop Ollama and serve with 0.0.0.0 as IP, check before with netstat (install net-tools):
$ sudo netstat -tunlp | grep 11434
tcp 0 0 127.0.0.1:11434 0.0.0.0:* LISTEN 10728/ollama
$ sudo systemctl stop ollama
$ sudo netstat -tunlp | grep 11434
The last command gives no result.
Serve under 0.0.0.0 and check with netstat, and check Ollama IP's:
$ OLLAMA_HOST=0.0.0.0 ollama serve
$ sudo netstat -tunlp | grep 11434
tcp6 0 0 :::11434 :::* LISTEN 11027/ollama
$ curl http://127.0.0.1:11434
Ollama is running
$ curl http://0.0.0.0:11434
Ollama is running
DDEV and host.docker.internal
Check inside DDEV:
$ ddev ssh
$ ping host.docker.internal
PING host.docker.internal (172.17.0.1) 56(84) bytes of data.
64 bytes from host.docker.internal (172.17.0.1): icmp_seq=1 ttl=64 time=0.123 ms
[...]
$ curl host.docker.internal:11434
Ollama is running
... but no models are available:
$ curl host.docker.internal:11434/api/tags
{"models":[]}
Ollama Authentication
Add these values:
Host Name: http://host.docker.internal
Port: 11434
Chat explorer
When I select Ollama, there are no models in the dropdown ...
PS. I spent a looong time trying to make it work with port 11343, since it is the port number in the placeholder :-) I'll create a MR to fix this.
Thanks!
Perhaps the link to Gitlab under "Resources" can be updated? Currently it points to the old branch https://git.drupalcode.org/project/leaflet_more_maps/-/blob/8.x-1.x/READ...
Instead the link text could be "Documentation" and the link point to https://git.drupalcode.org/project/leaflet_more_maps -- this way, the latest version of the README will always be shown.
Beautiful thorough description, thanks! I'll try it later today, and add it to the documentation after verifying. I am on Debian 12, but if you verify if it works on Windows also, that would be very nice as well.
A video would be fantastic, and perhaps you could include an uncensored LLM such as dolphin-llama3, to cover that aspect of AI as well? Or do that model instead of Gemma (Google), if the steps are identical? Or do both? :)
Thanks for fast answers @Marcus_Johansson!
Do you have slightly more concrete suggestions? (like "Insert this in the Ollama config file /home/user/.ollama/config.env, add IP: host.docker.internal in the DDEV config file, and restart DDEV")
My thinking is that, as soon as I get it working with DDEV (which is the officially recommended developer tool) I'll document it in README, and the AI documentation → . But rather than spending a lot of time experimenting with different solutions from the page you link to, more concrete actionable suggestions would save me a lot of time, which I can use better on documenting using Drupal AI module and Ollama in DDEV.
I agree with @mindausgad:
Resembles OpenAI logo, a flower and Drupal.
[...]
I vote for dropping company resemblance, and make it more neutral. Plus adding colors.
I suggested in #15 to use the AI Web Connect group logo as inspiration, but around 3 minutes into the great Introductory Video to the AI Module video (thanks @yautja_cetanu!) I now see that it looks a lot like the Amazon Bedrock logo ...
So, just as basing the Drupal AI module logo on OpenAI (backed by Microsoft) is not ideal, basing it on Amazon Bedrock would be equally not great.
Basing the Drupal AI logo on the OpenAI logo is kinda the same as if the Debian logo had been based on the Windows logo ...
I do think the logo looks amazing. It's just too close to OpenAI ... so I think we should try to create our own unique logo and identity for Drupal AI.
@simon23 and @tarasiadis: This issue is closed as a duplicate, see 📌 [10.3] Update ConditionManager to support PHP Attributes Active instead.
The challenge is probably to get DDEV connected to an IP on the host machine, I think ...
Thanks @Marcus_Johansson, I tried the module, and almost got it working ...
System
- Debian 12
- DDEV 1.23.2
Modules
I enabled these modules:
- AI Core
- Key
- AI API Explorer
- Ollama Provider
drush in ai key ai_api_explorer provider_ollama
I see that key module is a requirement in the ai module, but Ollama has no need for a key ... maybe the requirement should be set under the individual providers instead?
$ grep -iR -A 2 "dependencies:" .
./ai.info.yml:dependencies:
./ai.info.yml- - key:key
Setup Ollama Authentication
I entered:
- Host Name:
http://127.0.0.1 - Port:
11434
Ollama
Ollama is available:
$ curl 127.0.0.1:11434
Ollama is running
Two Ollama models are installed:
$ ollama list
NAME ID SIZE MODIFIED
dolphin-llama3:latest 613f068e29f8 4.7 GB 2 weeks ago
llama3:latest 365c0bd3c000 4.7 GB 3 weeks ago
Two Ollama models are available via command line:
$ curl 127.0.0.1:11434/api/tags
{"models":[{"name":"dolphin-llama3:latest","model":"dolphin-llama3:latest","modified_at":"2024-06-06T22:40:03.181858319+02:00","size":4661235994,"digest":"613f068e29f863bb900e568f920401b42678efca873d7a7c87b0d6ef4945fadd","details":{"parent_model":"","format":"gguf","family":"llama","families":["llama"],"parameter_size":"8B","quantization_level":"Q4_0"}},{"name":"llama3:latest","model":"llama3:latest","modified_at":"2024-05-27T12:53:40.033272983+02:00","size":4661224676,"digest":"365c0bd3c000a25d28ddbf732fe1c6add414de7275464c4e4d1c3b5fcb5d8ad1","details":{"parent_model":"","format":"gguf","family":"llama","families":["llama"],"parameter_size":"8.0B","quantization_level":"Q4_0"}}]}AI Chat Explorer
When I select Ollama from the dropdown, "Provider Configuration" pops up but is empty, and I get an error "Error message -- Oops, something went wrong. Check your browser's developer console for more details." where I should have had the two models presented I guess?
From the console:
XHRPOST
https://drupal10.ddev.site/admin/config/ai/development/chat-generation?ajax_form=1&_wrapper_format=drupal_ajax
[HTTP/2 500 Internal Server Error 55ms]
POST
https://drupal10.ddev.site/admin/config/ai/development/chat-generation?ajax_form=1&_wrapper_format=drupal_ajax
Status
500
Internal Server Error
VersionHTTP/2
Transferred4.69 kB (4.32 kB size)
Referrer Policystrict-origin-when-cross-origin
Request PriorityHighest
Uncaught
Object { message: "\nAn AJAX HTTP error occurred.\nHTTP Result Code: 500\nDebugging information follows.\nPath: /admin/config/ai/development/chat-generation?ajax_form=1\nStatusText: Internal Server Error\nResponseText: The website encountered an unexpected error. Try again later.GuzzleHttp\\Exception\\ConnectException: cURL error 7: Failed to connect to 127.0.0.1 port 11343 after 0 ms: Couldn't connect to server (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://127.0.0.1:11343/api/tags in GuzzleHttp\\Handler\\CurlFactory::createRejection() (line 210 of /var/www/html/vendor/guzzlehttp/guzzle/src/Handler/CurlFactory.php). GuzzleHttp\\Handler\\CurlFactory::finishError(Object, Object, Object) (Line: 110)\nGuzzleHttp\\Handler\\CurlFactory::finish(Object, Object, Object) (Line: 47)\nGuzzleHttp\\Handler\\CurlHandler->__invoke(Object, Array) (Line: 28)\nGuzzleHttp\\Handler\\Proxy::GuzzleHttp\\Handler\\{closure}(Object, Array) (Line: 48)\nGuzzleHttp\\Handler\\Proxy::GuzzleHttp\\Handler\\{closure}(Object, Array) (Line: 35)\nGuzzleHttp\\PrepareBodyMiddleware->__invoke(Object, Array) (Line: 31)\nGuzzleHttp\\Middleware::GuzzleHttp\\{closure}(Object, Array) (Line: 71)\nGuzzleHttp\\RedirectMiddleware->__invoke(Object, Array) (Line: 66)\nGuzzleHttp\\Middleware::GuzzleHttp\\{closure}(Object, Array) (Line: 75)\nGuzzleHttp\\HandlerStack->__invoke(Object, Array) (Line: 333)\nGuzzleHttp\\Client->transfer(Object, Array) (Line: 169)\nGuzzleHttp\\Client->requestAsync('GET', Object, Array) (Line: 189)\nGuzzleHttp\\Client->request('GET', 'http://127.0.0.1:11343/api/tags', Array) (Line: 106)\nDrupal\\provider_ollama\\OllamaControlApi->makeRequest('api/tags', Array, 'GET') (Line: 49)\nDrupal\\provider_ollama\\OllamaControlApi->getModels() (Line: 62)\nDrupal\\provider_ollama\\Plugin\\AiProvider\\OllamaProvider->getConfiguredModels('chat')\nReflectionMethod->invokeArgs(Object, Array) (Line: 106)\nDrupal\\ai\\Plugin\\ProviderProxy->wrapperCall(Object, Array) (Line: 78)\nDrupal\\ai\\Plugin\\ProviderProxy->__call('getConfiguredModels', Array) (Line: 127)\nDrupal\\ai\\Service\\AiProviderFormHelper->generateAiProvidersForm(Array, Object, 'chat', 'chat_', 2, 1003) (Line: 159)\nDrupal\\ai_api_explorer\\Form\\ChatGenerationForm->buildForm(Array, Object)\ncall_user_func_array(Array, Array) (Line: 536)\nDrupal\\Core\\Form\\FormBuilder->retrieveForm('ai_api_chat_generation', Object) (Line: 375)\nDrupal\\Core\\Form\\FormBuilder->rebuildForm('ai_api_chat_generation', Object, Array) (Line: 633)\nDrupal\\Core\\Form\\FormBuilder->processForm('ai_api_chat_generation', Array, Object) (Line: 326)\nDrupal\\Core\\Form\\FormBuilder->buildForm(Object, Object) (Line: 73)\nDrupal\\Core\\Controller\\FormController->getContentResult(Object, Object)\ncall_user_func_array(Array, Array) (Line: 123)\nDrupal\\Core\\EventSubscriber\\EarlyRenderingControllerWrapperSubscriber->Drupal\\Core\\EventSubscriber\\{closure}() (Line: 638)\nDrupal\\Core\\Render\\Renderer->executeInRenderContext(Object, Object) (Line: 121)\nDrupal\\Core\\EventSubscriber\\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext(Array, Array) (Line: 97)\nDrupal\\Core\\EventSubscriber\\EarlyRenderingControllerWrapperSubscriber->Drupal\\Core\\EventSubscriber\\{closure}() (Line: 181)\nSymfony\\Component\\HttpKernel\\HttpKernel->handleRaw(Object, 1) (Line: 76)\nSymfony\\Component\\HttpKernel\\HttpKernel->handle(Object, 1, 1) (Line: 53)\nDrupal\\Core\\StackMiddleware\\Session->handle(Object, 1, 1) (Line: 48)\nDrupal\\Core\\StackMiddleware\\KernelPreHandle->handle(Object, 1, 1) (Line: 28)\nDrupal\\Core\\StackMiddleware\\ContentLength->handle(Object, 1, 1) (Line: 32)\nDrupal\\big_pipe\\StackMiddleware\\ContentLength->handle(Object, 1, 1) (Line: 106)\nDrupal\\page_cache\\StackMiddleware\\PageCache->pass(Object, 1, 1) (Line: 85)\nDrupal\\page_cache\\StackMiddleware\\PageCache->handle(Object, 1, 1) (Line: 48)\nDrupal\\Core\\StackMiddleware\\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 51)\nDrupal\\Core\\StackMiddleware\\NegotiationMiddleware->handle(Object, 1, 1) (Line: 36)\nDrupal\\Core\\StackMiddleware\\AjaxPageState->handle(Object, 1, 1) (Line: 51)\nDrupal\\Core\\StackMiddleware\\StackedHttpKernel->handle(Object, 1, 1) (Line: 741)\nDrupal\\Core\\DrupalKernel->handle(Object) (Line: 19)\n", name: "AjaxError", stack: "@https://drupal10.ddev.site/sites/default/files/js/js_jQzZ_qeL-aNiRqFwdB8MFdA5vskuvL7sZ7mgMrXNFuQ.js?scope=footer&delta=0&language=en&theme=claro&include=eJx9juEOgjAMhF9obs_gk5BSTpmOdXaF6NsLCiYY46-23-Wux5INdxsphU7HQsnzhxxSzNfqWBSbSGxxwkvYcZaUqFTsYDUyrP44h2qe4eU2Qh_-JDo4E0ktaVino26IuVmvpoKU-_Aejv8V_RmwxXpTwPcyQZcW2b7_elSmguNidm08NyUWhG15AmcicU0:180:2411\n@https://drupal10.ddev.site/sites/default/files/js/js_jQzZ_qeL-aNiRqFwdB8MFdA5vskuvL7sZ7mgMrXNFuQ.js?scope=footer&delta=0&language=en&theme=claro&include=eJx9juEOgjAMhF9obs_gk5BSTpmOdXaF6NsLCiYY46-23-Wux5INdxsphU7HQsnzhxxSzNfqWBSbSGxxwkvYcZaUqFTsYDUyrP44h2qe4eU2Qh_-JDo4E0ktaVino26IuVmvpoKU-_Aejv8V_RmwxXpTwPcyQZcW2b7_elSmguNidm08NyUWhG15AmcicU0:180:19740\n" }
js_jQzZ_qeL-aNiRqFwdB8MFdA5vskuvL7sZ7mgMrXNFuQ.js:180:2411
Could the AI Web Connect group logo be used as inspiration, replacing the five circles in the right side with Drupal drops, using the Dark Blue, Light Blue, and Lime Green Drupal colors as a gradient?
Nice work @Marcus_Johansson, thanks! I'll try to test Ollama LLM Provider later today.
You could consider creating a Drupal core issue? I usually get fast answers there, since quite a few people are scanning new issues: https://www.drupal.org/project/issues/drupal →
Please feel free to share a link to the issue in this Forum post, if you create it. Thanks!
You could consider creating Drupal core issues for your recent challenges after updating to Drupal 10.3 ... I usually get fast answers there, since quite a few people are scanning new issues: https://www.drupal.org/project/issues/drupal →
Please feel free to share links to your issue(s) here in the Forum, if you decide to create them.
You're welcome! Feel free to share a link to the issue here, if you create one :-)
Ok, thanks for clarifying, and I agree that direct database wrangling is risky, and that script or UI is preferred.
I do think this should be prioritized, for all the reasons I list in the Issue Summary of 📌 Clean up Drupal Planet for old posts Active . Feel free to reopen that issue, and add a "Create script or UI, to remove old, duplicate posts" under "Remaining tasks" and set to "Needs Work", if you agree that it's a good idea :-)
A new official release of Chi-teck's Drupal Code Generator will probably solve this problem, see Release new version, to allow installing Drush in Drupal 11 #177.
PS. Since it seems like you have database access @fjgarlin: Just in case you have time, the Planet Drupal has been flooded recently, and deleting the recent 47 old posts would be a huge improvement: #3402661-16: Clean up Drupal Planet for old posts → .
This is great, much better, thanks @fjgarlin.
Thanks @jgarlin, that would be fantastic, making "Reduce tag options" and "Taller select box" redundant.
Update Issue summary.
Thanks @fjgarlin. Actually, simply reversing the sort order would solve it, and let the older tags live at the bottom. I updated the Issue Summary, adding this suggestion:
- Drupal 11.x
- Drupal 10.x
- Drupal 9.x
- Drupal 8.x
- Drupal 7.x
- Drupal 6.x or older
- None
But can't posts with those ancient tags (4.5, 4.6, 4.7, etc.) be re-tagged with a "Drupal 6.x or older" tag, and then those old tags deleted?
Of course, it would be nice to keep the tags for the posts, but hide in the form, if that's possible. It doesn't make a lot of sense to include 4.5, 4.6, 4.7, etc. under "Drupal version" when creating a new Forum post in 2024.
I don't think that's a realistic scenario, or that it would even be a problem. As it is now, we too often have to ask for details.
Moving up the Composer forum would increase the likelihood that a forum post enters the correct forum, with the right amount of details, so that we can much more efficiently help the user.
I found the issue. In the Gitlab issue system, where Drupal issues are moving soon, crediting will be part of the process of closing an issue, from #3395901-28: Use Gitlab CI in Simplenews → :
We could create an automated message, but that will actually happen when we are in "GitLab issues" as it is already implemented via a webhook when closing the issue.
Thanks @itamair, and @Orkut Murat Yılmaz for reviewing!
To prevent abuse, for example by creating a branch or uploading a file only to get credit (I searched, but can't find the issue where it was decided), credits are no longer added automatically. So the maintainer needs to remember do it ...
A maintainer has not commented and given credit yet.
Thanks @luqmaan.essop. Everything looks perfect, and I look forward to seeing your posts on Planet Drupal.
@apaderno: The feed can be added.
Thanks for updating the issue template from:
"Add your-domain to Planet Drupal"
... to:
"Add [your-domain] to Planet Drupal" ... and adding "(Replace [your-domain] with the effective domain used by the feed.)"
This will prevent many redundant updates ... I suggested this in December 2023, but maybe you don't read comments? I ask, since I also suggested setting a limit to 10 posts in November 2023, but never got a reply ...
@mariohernandez: Maybe you already are aware of this, but Drupal Planet is receiving the old posts ... see also #3402661-16: Clean up Drupal Planet for old posts → .
I still think being able to clean up duplicate, old posts should be considered. Recently there has been a deluge ... 47 posts, what looks like the same twenty posts, posted repeatedly, with a few days between.
That's under https://www.drupal.org/project/issues/drupalorg → .
But since issues are moving to Gitlab soon, it probably needs to be a small change, for it to be considered.
Thanks for sharing @benjamin_dk, be bold! https://www.drupal.org/community/contributor-guide/reference-information... →
Fix Hetzner issue link.
Add "Make sure to actually install a few modules" step, add link.
Add "Make sure to actually install a few modules" step, add link.
Add "Make sure to actually install a few modules" step, add link.
Add "Make sure to actually install a few modules" step, add link.
Add "Make sure to actually install a few modules" step, add link.
Add "Make sure to actually install a few modules" step, add link.
Add "Make sure to actually install a few modules" step, add link.
Add "Make sure to actually install a few modules" step, add link.
Add "Make sure to actually install a few modules" step, add link.
Add "Make sure to actually install a few modules" step, add link.
Add "Make sure to actually install a few modules" step, add link.
Add "Make sure to actually install a few modules" step, add link.
Add "Make sure to actually install a few modules" step, add link.
Add "Make sure to actually install a few modules" step, add link.
Add "Make sure to actually install a few modules" step, add link.
Add "Make sure to actually install a few modules" step, add link.
Add "Make sure to actually install a few modules" step.
Add "Make sure to actually install a few modules" step.
Add link.
Thanks @kathc for a very thorough and detailed description!
I was skimming all issues, to see if any hosts had been tested yet, and only saw your great work by chance, when I wanted to edit the issue summary, and add the "Make sure to actually install a few modules" step.
I have taken the liberty of moving it into the Issue Summary, and changing Status to "Fixed", since you have verified that Project Browser works on Cloudways. This way, the Cloudways issue will visibly be marked as "Fixed" in the list on 📌 [META] Test Project Browser on hosting providers Drupal people are using Active .
I assume that "Allow installing via UI (experimental)" is not yet expected to work? But if it is, feel free to change Status to "Needs work".
Thanks @cbovard for a very thorough and detailed description!
I was skimming all issues, to see if any hosts had been tested yet, and only saw your great work by chance, when I wanted to edit the issue summary, and add the "Make sure to actually install a few modules" step.
I have taken the liberty of moving it into the Issue Summary, and changing Status to "Fixed", since you have verified that Project Browser works on Dreamhost. This way, the Dreamhost issue will visibly be marked as "Fixed" in the list on 📌 [META] Test Project Browser on hosting providers Drupal people are using Active .
Feel free to revert the list to manual links, if you prefer that :) I just thought I'd be bold and do the change, to try it out.
Alphabetize the list -- also, switch to using reference links for easier alphabetization, and more easily see the status of individual issues ("Active", "Needs review", "Fixed", etc.).
Add Hetzner, and extra step in the "Please add a child issue by", to update parent issue in the cloned issue.
Thanks for clarifying @DamienMcKenna -- with fora inside containers it works fine. Shouldn't we require containers, if they are in actuality required?
Thanks for pursuing this @TravisCarden. Streamlining the Starshot experience is a great incentive to getting the Ctools module issue sorted out, and removed from Pathauto.
Thanks, I tried the patch, but get a "No forum categories were found." under /forum, even though there are two fora.
Thanks, sounds good!
I just saw it, thanks!
Beautiful, thanks @naveenvalecha!
I tried both patches, but don't see much difference ... perhaps the change can be put into words, or an image? Maybe I need to reinstall the module after patching, for the changes to take effect?
It's so great that you created these issues @naveenvalecha, thanks!
I checked ~10 issues, and they indeed all lack (except for one) an automated Drupal 11 readiness issue. I added them to a list in the issue I created. If I may add one suggestion, it would be to include the module name in the title, to easier discern in lists, emails, etc. so that they don't all have the same title. Perhaps like this?
"Drupal 11 Compatibility for "
Thanks! This and ✨ Recreate Advanced Forum's forum list display Needs review are great features to add to the Forum module.
Update the Issue Summary.
I just now see a contrib module, which got an automatic issue: 📌 Automated Drupal 11 compatibility fixes for geofield RTBC ...
Strangely, some issues have received an automatic Drupal 11 issue, 📌 Automated Drupal 11 compatibility fixes for geofield RTBC ...
Thanks for clearing that up @drubb, the file name needs to get updated then, so changing Status.
- Present in 4.24:
https://github.com/yairEO/tagify/blob/v4.24.0/dist/tagify.min.js - Removed in 4.25:
https://github.com/yairEO/tagify/blob/v4.25.0/dist/tagify.min.js
Drupal 11 will be released late July 2024, so it would be great to get this patch committed to dev, and released officially shortly thereafter.
Perfect, thanks for proactively creating those issues! Let's see if possibly automated issues can be created for the projects, where they haven't already been created.
Thanks @naveenvalecha! I expected Drupal 11 readiness issues to be created automatically in all contrib modules for Drupal 11, since it may be released last week of July, in only 6 weeks ... but maybe not this time? I created an issue.
Thanks for confirming that the upgrade to Drupal 10 documentation page works well @faraid. It's a balancing act to include the most necessary steps, highlight solutions for common problems, while keeping the page from ballooning into too many steps.
Thanks for a fast reply @Marcus_Johansson.
So I guess there is no way to turn up a time parameter, max. characters ... I assumed that a free account gets for example 5 seconds execution, and 500 characters max., whereas paying customers could in theory be allowed to set a max. execution time and amount of text, for example 30 seconds and 5000 characters.
But since you write "I don't see any difference between them.", so maybe it's not possible. It's just odd, because locally Ollama and Llama3 has no problem crunching a prompt for 15-25 seconds and returning ~5000 characters, but the same model on HuggingFace only thinks for ~5 seconds and returns ~500 characters.
Drupal 11 is planned to be released the week of July 29, 2024. It would be great to include this improvement.
Great that it worked, feel free to add [Solved] first in the title.
Thanks for adding this feature, it will be really useful to help understand what goes on behind the scene, like which prompt and parameters are being sent (role, max. tokens, and so on).
This feature will probably help answer questions like the one I posed recently?:
Bonus question: Does anyone have any experience with getting fairly fast and short answers (max. 500 characters) from HuggingFace, but getting longer processing time and thereby answers, after upgrading to a paying account?
HuggingFace answers after only 5 seconds with a short reply, whereas OpenAI, which I used previously, spent up to 30 seconds, returning very elaborate replies with up to 4000 character ...
From #3454202-4: Enable token support for AI Interpolator Rule Huggingface Text Generation → .
Thanks @berramou, perhaps @RdeBoer can make you maintainer as well?
Thanks for creating this issue @yautja_cetanu, it would be a nice feature to be able to block prompts based on some rules, before passing them on to a LLM.
It says on the top of the page of Updating Drupal core via Composer → :
This guide covers minor and patch version site updates, for example 10.0 to 10.1. For upgrading Drupal to a new major version, see How to upgrade from Drupal 9 to Drupal 10 → .
You should instead follow How to upgrade from Drupal 9 to Drupal 10 → .
Add link to the great resource Migrating Your Data from Drupal 7 to Drupal 10.