XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Building from source fails with commit cb96de6

    Scheduled Pinned Locked Moved Solved Xen Orchestra
    12 Posts 7 Posters 146 Views 4 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • TeddyAstieT Offline
      TeddyAstie Vates 🪐 XCP-ng Team Xen Guru @joeymorin
      last edited by TeddyAstie

      @joeymorin said in Building from source fails with commit cb96de6:

      Greetings all,

      Subject pretty much says it. Build output goes sideways starting with:

      @xen-orchestra/qcow2:build: src/disk/QcowDisk.mts(94,52): error TS2365: Operator '&' cannot be applied to types 'bigint' and 'number'.
      

      Github CI is failing on this commit, try reverting to a commit that pass CI.

      1 Reply Last reply Reply Quote 0
      • marcoiM Offline
        marcoi
        last edited by marcoi

        getting build error as well. I run the update every morning to build XO.
        Currently running at below version as the update failed

        Xen Orchestra, commit 676b0
        Master, commit bf705

        • Packages in scope: xo-server, xo-server-audit, xo-server-auth-github, xo-server-auth-google, xo-server-auth-ldap, xo-server-auth-oidc, xo-server-auth-saml, xo-server-back
        up-reports, xo-server-load-balancer, xo-server-netbox, xo-server-perf-alert, xo-server-sdn-controller, xo-server-test-plugin, xo-server-transport-email, xo-server-transport
        -icinga2, xo-server-transport-nagios, xo-server-transport-slack, xo-server-transport-xmpp, xo-server-usage-report, xo-server-web-hooks, xo-web
        • Running build in 21 packages
        • Remote caching disabled
        @xen-orchestra/qcow2:build: cache miss, executing e9d3169e4c8d9523
        @xen-orchestra/qcow2:build: yarn run v1.22.22
        @xen-orchestra/qcow2:build: $ tsc
        @xen-orchestra/qcow2:build: src/disk/QcowDisk.mts(94,52): error TS2365: Operator '&' cannot be applied to types 'bigint' and 'number'.
        @xen-orchestra/qcow2:build: error Command failed with exit code 2.
        @xen-orchestra/qcow2:build: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
        @xen-orchestra/qcow2:build: ERROR: command finished with error: command (/opt/xo/xo-builds/xen-orchestra-202510281011/@xen-orchestra/qcow2) /tmp/yarn--1761660713548-0.01268
        3662235605908/yarn run build exited (2)
        @xen-orchestra/qcow2#build: command (/opt/xo/xo-builds/xen-orchestra-202510281011/@xen-orchestra/qcow2) /tmp/yarn--1761660713548-0.012683662235605908/yarn run build exited
        (2)
        
         Tasks:    26 successful, 28 total
        Cached:    0 cached, 28 total
          Time:    11.108s
        Failed:    @xen-orchestra/qcow2#build
        
         ERROR  run failed: command  exited (2)
        error Command failed with exit code 2.
        
        
        1 Reply Last reply Reply Quote 0
        • A Offline
          acebmxer
          last edited by

          Same here also

          Screenshot 2025-10-28 101729.png

          86 Updating Xen Orchestra from '51855c22d' to 'bf705e0a9'
           87 + cd /opt/xo/xo-builds/xen-orchestra-202510281017 && yarn --network-timeout 300000 && yarn --network-timeout 300000 build
           88 yarn install v1.22.22
           89 [1/5] Validating package.json...
           90 [2/5] Resolving packages...
           91 [3/5] Fetching packages...
           92 warning bare-os@3.6.2: The engine "bare" appears to be invalid.
           93 [4/5] Linking dependencies...
           94 warning "@commitlint/cli > @commitlint/load > cosmiconfig-typescript-loader@6.1.0" has unmet peer dependency "@types/node@*".
           95 warning "@commitlint/cli > @commitlint/load > cosmiconfig-typescript-loader@6.1.0" has unmet peer dependency "typescript@>=5".
           96 warning "@typescript-eslint/eslint-plugin > ts-api-utils@1.4.3" has unmet peer dependency "typescript@>=4.2.0".
           97 warning " > @xen-orchestra/web-core@0.32.0" has unmet peer dependency "pinia@^3.0.1".
           98 warning " > @xen-orchestra/web-core@0.32.0" has unmet peer dependency "vue@~3.5.13".
           99 warning " > @xen-orchestra/web-core@0.32.0" has unmet peer dependency "vue-i18n@^11.1.2".
          100 warning " > @xen-orchestra/web-core@0.32.0" has unmet peer dependency "vue-router@^4.5.0".
          101 warning "workspace-aggregator-aee2c1a6-b277-49cd-a7d5-c9240b00a583 > @xen-orchestra/rest-api > inversify@6.2.2" has unmet peer dependency "reflect-      
              metadata@~0.2.2".
          102 warning "workspace-aggregator-aee2c1a6-b277-49cd-a7d5-c9240b00a583 > @xen-orchestra/rest-api > swagger-ui-express@5.0.1" has unmet peer dependency       
              "express@>=4.0.0 || >=5.0.0-beta".
          103 warning "workspace-aggregator-aee2c1a6-b277-49cd-a7d5-c9240b00a583 > xo-server > typed-flash@1.0.1" has unmet peer dependency "@types/express@*".
          104 warning "workspace-aggregator-aee2c1a6-b277-49cd-a7d5-c9240b00a583 > @vates/event-listeners-manager > tap > @tapjs/test > @isaacs/ts-node-temp-fork-for- 
              pr-2009@10.9.7" has unmet peer dependency "@types/node@*".
          105 warning "workspace-aggregator-aee2c1a6-b277-49cd-a7d5-c9240b00a583 > @xen-orchestra/rest-api > inversify > @inversifyjs/core > @inversifyjs/reflect-     
              metadata-utils@0.2.4" has unmet peer dependency "reflect-metadata@0.2.2".
          106 warning "workspace-aggregator-aee2c1a6-b277-49cd-a7d5-c9240b00a583 > @vates/event-listeners-manager > tap > @tapjs/asserts > tcompare > react-element-to-    jsx-string@15.0.0" has unmet peer dependency "react@^0.14.8 || ^15.0.1 || ^16.0.0 || ^17.0.1 || ^18.0.0".
          107 warning "workspace-aggregator-aee2c1a6-b277-49cd-a7d5-c9240b00a583 > @vates/event-listeners-manager > tap > @tapjs/asserts > tcompare > react-element-to-    jsx-string@15.0.0" has unmet peer dependency "react-dom@^0.14.8 || ^15.0.1 || ^16.0.0 || ^17.0.1 || ^18.0.0".
          108 warning Workspaces can only be enabled in private projects.
          109 [5/5] Building fresh packages...
          110 $ husky install
          111 husky - Git hooks installed
          112 Done in 27.79s.
          113 yarn run v1.22.22
          114 $ TURBO_TELEMETRY_DISABLED=1 turbo run build --filter xo-server --filter xo-server-'*' --filter xo-web
          115 turbo 2.5.8
          116 
          117 • Packages in scope: xo-server, xo-server-audit, xo-server-auth-github, xo-server-auth-google, xo-server-auth-ldap, xo-server-auth-oidc, xo-server-auth- 
              saml, xo-server-backup-reports, xo-server-load-balancer, xo-server-netbox, xo-server-perf-alert, xo-server-sdn-controller, xo-server-test-plugin, xo-    
              server-transport-email, xo-server-transport-icinga2, xo-server-transport-nagios, xo-server-transport-slack, xo-server-transport-xmpp, xo-server-usage-   
              report, xo-server-web-hooks, xo-web       
          118 • Running build in 21 packages
          119 • Remote caching disabled
          120 @xen-orchestra/qcow2:build: cache miss, executing e9d3169e4c8d9523
          121 @xen-orchestra/qcow2:build: yarn run v1.22.22
          122 @xen-orchestra/qcow2:build: $ tsc
          123 @xen-orchestra/qcow2:build: src/disk/QcowDisk.mts(94,52): error TS2365: Operator '&' cannot be applied to types 'bigint' and 'number'.
          124 @xen-orchestra/qcow2:build: error Command failed with exit code 2.
          125 @xen-orchestra/qcow2:build: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
          126 @xen-orchestra/qcow2:build: ERROR: command finished with error: command (/opt/xo/xo-builds/xen-orchestra-202510281017/@xen-orchestra/qcow2) /tmp/yarn--  
              1761661100812-0.024448560644666273/yarn run build exited (2)
          127 @xen-orchestra/qcow2#build: command (/opt/xo/xo-builds/xen-orchestra-202510281017/@xen-orchestra/qcow2) /tmp/yarn--1761661100812-0.024448560644666273/   
              yarn run build exited (2)
          128 
          129  Tasks:    26 successful, 28 total
          130 Cached:    0 cached, 28 total
          131   Time:    7.455s
          132 Failed:    @xen-orchestra/qcow2#build
          133 
          134  ERROR  run failed: command  exited (2)
          135 error Command failed with exit code 2.
          136 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
          137 + rm -rf /opt/xo/xo-builds/xen-orchestra-202510281017
          
          M 1 Reply Last reply Reply Quote 0
          • M Online
            manilx @acebmxer
            last edited by

            @acebmxer Fixed. Worked here now. Had the same error before

            marcoiM A 2 Replies Last reply Reply Quote 0
            • marcoiM Offline
              marcoi @manilx
              last edited by

              @manilx same here

              Xen Orchestra, commit 45ef6
              Master, commit 45ef6

              1 Reply Last reply Reply Quote 0
              • A Offline
                acebmxer @manilx
                last edited by

                @manilx

                success. Updated to Commit 45ef6

                1 Reply Last reply Reply Quote 1
                • A Offline
                  Andrew Top contributor @joeymorin
                  last edited by

                  @joeymorin @olivierlambert Same here error... updates have fixed it for me (same day).

                  J 1 Reply Last reply Reply Quote 1
                  • olivierlambertO olivierlambert marked this topic as a question
                  • olivierlambertO olivierlambert has marked this topic as solved
                  • J Offline
                    joeymorin @Andrew
                    last edited by

                    @Andrew For the record, that didn't fix it for me.

                    To be specific, it >>did<< fix the error regarding bigint in QcowDisk.mts, but a new error popped up later in the build:

                    yarn run v1.22.22
                    $ TURBO_TELEMETRY_DISABLED=1 turbo run build --filter xo-server --filter xo-server-'*' --filter xo-web
                    turbo 2.5.8
                    
                    • Packages in scope: xo-server, xo-server-audit, xo-server-auth-github, xo-server-auth-google, xo-server-auth-ldap, xo-server-auth-oidc, xo-server-auth-saml, xo-server-backup-reports, xo-server-load-balancer, xo-server-netbox, xo-server-perf-alert, xo-server-sdn-controller, xo-server-test-plugin, xo-server-transport-email, xo-server-transport-icinga2, xo-server-transport-nagios, xo-server-transport-slack, xo-server-transport-xmpp, xo-server-usage-report, xo-server-web-hooks, xo-web
                    • Running build in 21 packages
                    • Remote caching disabled
                      x Internal errors encountered: external process killed a task
                    
                    error Command failed with exit code 1.
                    info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
                    + rm -rf /opt/xo/xo-builds/xen-orchestra-202510281354
                    
                    

                    That was with commit 740fc03, the latest at the time of my build at 2025-10-28 17:54 UTC.

                    It's unclear to me why the build failed exactly. Except that "Internal errors encountered: external process killed a task". I don't know know what that external process was. Unfortunately the 3rd party build script doesn't seem to preserve failed builds, only a slender log file.

                    I tried again a little later, with commit 87471d9. That succeeded, but it's unclear to me why. Neither commit explains either the failure, nor the success. The only other difference is that with the success, nodejs was updated (automatically, as part of the 3rd party build script) from 22.20.0-1nodesource1 to 22.21.1-1nodesource1, whereas for the failed build it was still 22.20.0-1nodesource1.

                    I don't know enough about the build process to untangle what happened... but I don't really need to. I can remain ignorant 🙂

                    By the way, if my initial post was closer to static noise than useful feedback, please forgive, and please let me know. It was really just an FYI to those who may be both listening and desiring to know. I see things move fast with the repo, with ten or more commits some days, so maybe flooding the forums with 'my build failed!' posts isn't helpful.

                    A 1 Reply Last reply Reply Quote 0
                    • A Offline
                      Andrew Top contributor @joeymorin
                      last edited by

                      @joeymorin I use @ronivay XenOrchestraInstallerUpdater script to help build my XO setups. It keeps the last three successful builds and has a rollback option.

                      J 1 Reply Last reply Reply Quote 1
                      • J Offline
                        joeymorin @Andrew
                        last edited by

                        @Andrew many thanks. As do I. See my OP.

                        A failed build doesn't break XO. It leaves the previous successful build in place.

                        My post wasn't to ask how to fix my problem, but to point out the issue to others who might care to know (see my last post).

                        Cheers.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post