[SOLVED] Error: Max depth in build dependencies reached, aborting

[t.heroult]

Good morning
Since this afternoon, I have been encountering this error on several machines:

Code: Select all

Get packages index from [<WaptRepo https://srvwapt.XXXXXX.local/wapt verify_cert=False client_cert_path=C:\Program Files (x86)\wapt\private\heroult.XXXXXX.local.crt>, <WaptHostRepo https://srvwapt.XXXXXX.local/wapt-host for host_id heroult.XXXXXX.local >]
Max depth in build dependencies reached, aborting
Traceback (most recent call last):
  File "<string>", line 1943, in run
  File "C:\Program Files (x86)\wapt\waptservice\waptservice_common.py", line 737, in run
    self._run()
  File "C:\Program Files (x86)\wapt\waptservice\waptservice_common.py", line 923, in _run
    self.result = self.wapt.update(force=self.force, register=self.notify_server_on_finish)
  File "C:\Program Files (x86)\wapt\common.py", line 4874, in update
    "upgrades": self.list_upgrade(),
  File "C:\Program Files (x86)\wapt\common.py", line 5916, in list_upgrade
    depends = self.check_depends(result['install']+result['upgrade']+result['additional'])
  File "C:\Program Files (x86)\wapt\common.py", line 5039, in check_depends
    (depends, conflicts, missing) = self.waptdb.build_depends([p[0] for p in packages])
  File "C:\Program Files (x86)\wapt\common.py", line 1527, in build_depends
    alldepends = dodepends(packages, depth)
  File "C:\Program Files (x86)\wapt\common.py", line 1509, in dodepends
    newdepends = dodepends(available_depends, depth+1)
  File "C:\Program Files (x86)\wapt\common.py", line 1509, in dodepends
    newdepends = dodepends(available_depends, depth+1)
  File "C:\Program Files (x86)\wapt\common.py", line 1509, in dodepends
    newdepends = dodepends(available_depends, depth+1)
  [Previous line repeated 28 more times]
  File "C:\Program Files (x86)\wapt\common.py", line 1484, in dodepends
    raise Exception('Max depth in build dependencies reached, aborting')
Exception: Max depth in build dependencies reached, aborting

Any idea what's going on?

Sincerely,
Tom

[t.heroult]

Good morning
Today, all machines are paralyzed at the WAPT level because of this.
Even a simple audit is impossible...

In the machine logs, I see this every 10 seconds:

Code: Select all

2024-08-05 09:19:15,635 [wapttasks WaptTaskManager 19392] CRITICAL Error for update in check_scheduled_tasks: Max depth in build dependencies reached, aborting

[t.heroult]

Okay, I found it after some research; it was a loop between two packages that were strangely interdependent (one dependent on the other).
It's fixed!