When upgrading from dev to beta1

Created on 30 October 2024, about 2 months ago

Problem/Motivation

Hi,

Just tried to upgrade from dev to beta1

first composer removed quite a lot of packages, is this normal?

Lock file operations: 0 installs, 1 update, 19 removals
  - Removing carbonphp/carbon-doctrine-types (3.2.0)
  - Removing doctrine/inflector (2.0.10)
  - Removing hkulekci/qdrant (v0.5.7)
  - Removing illuminate/collections (v10.48.22)
  - Removing illuminate/conditionable (v10.48.22)
  - Removing illuminate/contracts (v10.48.22)
  - Removing illuminate/macroable (v10.48.22)
  - Removing illuminate/support (v10.48.22)
  - Removing nesbot/carbon (2.72.5)
  - Removing openai-php/client (v0.10.2)
  - Removing php-http/discovery (1.20.0)
  - Removing php-http/multipart-stream-builder (1.4.2)
  - Removing psr/clock (1.0.0)
  - Removing psr/simple-cache (3.0.0)
  - Removing saloonphp/saloon (v3.10.0)
  - Removing scotteuser/pinecone-php (1.0.2)
  - Removing symfony/translation (v6.4.12)
  - Removing voku/portable-ascii (2.0.1)
  - Removing wpai-inc/anthropic-sdk-php (0.2.1)
  - Upgrading drupal/ai (dev-1.0.x 596c7c1 => 1.0.0-beta1)

the with beta1 run updatedb it gives:

sudo ../vendor/bin/drush updatedb
 [error]   (Currently using External module "ai_provider_lmstudio" should exist and be ready to replace the currently installed "provider_lmstudio". Please run "composer require drupal/ai_provider_lmstudio"
)
 [error]   (Currently using External module "ai_provider_openai" should exist and be ready to replace the currently installed "provider_openai". Please run "composer require drupal/ai_provider_openai"

)

 Requirements check reports errors. Do you wish to continue? (yes/no) [yes]:

then tried to install those missing modules:

composer require drupal/ai_provider_lmstudio

In PackageDiscoveryTrait.php line 332:

  Could not find a version of package drupal/ai_provider_lmstudio matching your minimum-stability (stable). Require it with an explicit version c
  onstraint allowing its desired stability.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

💬 Support request
Status

Active

Version

1.0

Component

AI Core module

Created by

🇫🇮Finland anaconda777

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @anaconda777
  • 🇫🇮Finland anaconda777

    Okey, that was just a composer misue and was able to proceed:
    by first running these:
    composer require 'drupal/ai_provider_openai:^1.0@beta'
    composer require 'drupal/ai_provider_lmstudio:^1.0@beta'

    then run updatedb again and got some warnings:

     -------- ----------- --------------- -----------------------------------
      Module   Update ID   Type            Description
     -------- ----------- --------------- -----------------------------------
      ai       10301       hook_update_n   10301 - Checks to ensure a smooth
                                           migration from AI submodules to
                                           external modules.
     -------- ----------- --------------- -----------------------------------
    
    
     Do you wish to run the specified pending updates? (yes/no) [yes]:
     > yes
    
    >  [notice] Update started: ai_update_10301
    >  [notice] AI module moving to contributed modules has been completed.
    >  [notice] Update completed: ai_update_10301
    >  [notice] Checked fi translation for ai_provider_lmstudio.
    >  [notice] Downloaded fi translation for ai_provider_lmstudio.
    >  [notice] Imported fi translation for ai_provider_lmstudio.
    >  [warning] foreach() argument must be of type array|object, null given Mapping.php:31
    >  [warning] foreach() argument must be of type array|object, null given Mapping.php:230
    >  [warning] foreach() argument must be of type array|object, null given Mapping.php:31
    >  [warning] foreach() argument must be of type array|object, null given Mapping.php:230
    >  [notice] Translations imported: 0 added, 1 updated, 0 removed.
    >  [notice] The configuration was successfully updated. 519 configuration objects updated.
    >  [notice] The configuration was successfully updated. 519 configuration objects updated.
     [success] Finished performing updates.

    After the update to beta1 I noticed ECA models were dissapeared which used AI models:

    and in the drupal logs have these:

    The action plugin eca_ai_automator can not be initialized. ECA is ignoring this action. The issue with this action: You have requested a non-existent service "plugin.manager.ai_automator_type". Did you mean one of these: "plugin.manager.link_relation_type", "plugin.manager.tab_type", "plugin.manager.alias_type"?

  • 🇬🇧United Kingdom scott_euser

    Glad the upgrade is working as expected for the composer side of things.

    Translation import warnings - not sure, schema looks as expected in https://www.drupal.org/project/ai_provider_lmstudio module

    Updated issue summary to reflect the ECA Automator Type Plugin Manager not found that is blocking you.

  • 🇫🇮Finland anaconda777

    I was able to get things working, just created the ECA model again which dissapeared.
    I think this can be closed, because I had dev version where I tried the upgarde from.

  • 🇬🇧United Kingdom scott_euser

    Glad you got it working as well. Let's see what Marcus thinks before closing as I don't know much about Automators myself.

  • 🇩🇪Germany marcus_johansson

    Thanks for the bug ticket @anaconda777. I'll check if I can figure this out and if its a bug in the system.

    Can you verify that you updated from alpha8 to beta1? That's what it looks for from the update output. The reason I'm asking is that the only actual update path of Automators should have happened between alpha7 and alpha8.

    If you can verify that I will check what could have happened here.

  • 🇫🇮Finland anaconda777

    Hi,

    I actually cant anymore verify, but I am pretty sure it was not alpha8, because something was missing in alpha8 and I had to use DEV.
    So I tried upgrading from dev (which was downloaded maybe about 25.10.2024) to beta1.

  • 🇩🇪Germany marcus_johansson

    Oh, I found the bug - did this actually ever work? As far as I can see the plugin manager it has requested has always been wrong and this has never changed since we added Automators to the AI ECA module!

    So, I'm kind of suprised that it works at all. It should have had a bug at all times and always failed, though I'm 100% certain I tested it when I built it :/

    It fails when I use the current DEV version.

    Anyway I have put in the correct service and tested it and its updated on DEV, so it should be working with the current DEV, but no versions before it...

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024