![]() The maximum permitted deviation from an ideal match of topsides and shaft was a mere 40 millimetres – so accuracy was essential in all stages of the operation.Īs large volumes of water were pumped from its storage cells, the GBS rose, took over the weight from the barges and continued to raise the topsides high above the sea surface. Mating was accomplished by manoeuvring the barges into position over the concrete shaft and deballasting the gravity base structure (GBS). Photo: Dag Magne Søyland/Norwegian Petroleum Museum bygging av betongdelen til plattformen, engelsk, plattformen plasseres på feltet, The topside was mated with the GBS in Yrkjefjorden. On 6 March, this structure was transferred to two huge barges and towed to Vats by five tugs. In the meantime, the topsides were being completed at Stavanger’s Rosenberg Verft yard. Photo: A/S Norske Shell/Norwegian Petroleum Museum plattformen plasseres på feltet, engelsk, The topside is placed on two huge barges and towed to Vats by five tugs. This operation was a nervous time, with the Sleipner sinking (see separate article) the year before still fresh in the minds of most people present. On 24 March, the concrete structure underwent a trial submersion which left only a few metres of the shaft visible above the sea surface. The Condeep monotower was readied in March 1993 to receive the topsides, which were to be towed from Stavanger to the deepwater mating site at Vats. bygging av betongdelen til plattformen, plattformen plasseres på feltet, forsidebilde The GBS raises high against the sky where it is located in Yrkjefjorden, soon ready to be mated with the topside. It was also the first fixed installation to be positioned above the 62nd parallel – making the tow-out the longest to date on the Norwegian continental shelf (NCS). Which makes me think there's something lurking in there.To start with, the platform ranked at the time as the tallest structure ever towed. Yarn -version //-> showed corepack version instead of project version I could only repro the problem via corepack corepack enable Yarn -version // still respects project version cd ~/exampleprojectįurther, re-enabling telemetry did not have the same effect. However, this was not enough to fix, as the watcher showed that node was still accessing that file even after everything was deleted, so I had to shutdown all terminals, VSCode, etc.Īfter taking the above steps, and restarting a new terminal, I was able to get the yarn version to respect the project settings. I disabled it globally yarn config set -home enableTelemetry 0 This showed me that global telemetry on was recreating the. ![]() In a second terminal, I ran cd ~/exampleproject On my macos in a new terminal, I watched what was accessing the ~/.yarnrc.yml sudo fs_usage | grep /Users/exampleuser/.yarn Thanks for the helpful pointers on the homepath. ![]() $ npm install -g 1 package, and audited 2 packages in 326ms # disable corepack so there's no yarn installed In addition installing using npm install -g also doesn't seem to work correctly. So using Corepack I don't seem to be able to convince it to use version of Yarn. # manually ask corepack to run yarn 1.22.19, but it again ignores it # manually ask corepack to use v1.22.19, but it again ignores this "packageManager": enable corepack, and it ignores the packageManager version # package.json has packageManager set for Yarn v1.22.19 I think I must be missing something.Ĭommented Terminal session: # using node16.18.0 I've cloned a project which uses Yarn 1.x and am trying to run it, but I can't find a way to get the right version of Yarn.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |