Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SST Init fails on hardware that doesn't support bun #4485

Closed
remirth opened this issue Jun 27, 2024 · 2 comments
Closed

SST Init fails on hardware that doesn't support bun #4485

remirth opened this issue Jun 27, 2024 · 2 comments

Comments

@remirth
Copy link

remirth commented Jun 27, 2024

Maybe it's out of scope to support hardware that isn't supported by bun baseline however I can run almost everything but Bun on my Lenovo Thinkpad W500 from 2008.

This would be the related hardware issue oven-sh/bun#11946

This is the output from sst init --verbose

$ sst init --verbose
time=2024-06-27T22:58:02.404+02:00 level=INFO msg="checking for pulumi" path=/home/jaber/.config/sst/bin/pulumi
time=2024-06-27T22:58:02.686+02:00 level=INFO msg="checking for bun" path=/home/jaber/.config/sst/bin/bun

   ███████╗███████╗████████╗
   ██╔════╝██╔════╝╚══██╔══╝
   ███████╗███████╗   ██║   
   ╚════██║╚════██║   ██║   
   ███████║███████║   ██║   
   ╚══════╝╚══════╝   ╚═╝   

>  JS project detected. This will...
   - use the JS template
   - create an sst.config.ts


? ‏‏‎ ‎Continue: 

  ▸ Yes

    No



✓  Template: js


? ‏‏‎ ‎Where do you want to deploy your app? You can change this later: 

  ▸ aws

    cloudflare



✓  Using: aws

time=2024-06-27T22:58:22.082+02:00 level=INFO msg="creating project" name=sst-test
time=2024-06-27T22:58:22.083+02:00 level=INFO msg=step type=copy
time=2024-06-27T22:58:22.083+02:00 level=INFO msg="copying template" path=templates/js-aws/files/sst.config.ts
time=2024-06-27T22:58:22.083+02:00 level=INFO msg="copying template" path=templates/js-aws/files/tsconfig.json
time=2024-06-27T22:58:22.083+02:00 level=INFO msg=step type=npm
time=2024-06-27T22:58:22.084+02:00 level=INFO msg="installing npm package" package=sst version=ion
time=2024-06-27T22:58:22.084+02:00 level=INFO msg="reading package.json" file=package.json
time=2024-06-27T22:58:22.084+02:00 level=INFO msg=step type=npm
time=2024-06-27T22:58:22.084+02:00 level=INFO msg="installing npm package" package=@types/aws-lambda version=""
time=2024-06-27T22:58:22.084+02:00 level=INFO msg="fetching latest version" package=@types/aws-lambda
time=2024-06-27T22:58:22.084+02:00 level=INFO msg="getting package" name=@types/aws-lambda version=latest
time=2024-06-27T22:58:22.406+02:00 level=INFO msg="latest version" version=8.10.140
time=2024-06-27T22:58:22.407+02:00 level=INFO msg="esbuild building"
time=2024-06-27T22:58:22.414+02:00 level=INFO msg="esbuild built" outfile=/home/jaber/dev/menas/sst-test/.sst/eval/eval-1719521902407.mjs
time=2024-06-27T22:58:22.414+02:00 level=INFO msg="evaluating config"
time=2024-06-27T22:58:22.481+02:00 level=INFO msg="config evaluated"
time=2024-06-27T22:58:22.481+02:00 level=INFO msg="installing platform"
time=2024-06-27T22:58:22.527+02:00 level=INFO msg="installing deps"
time=2024-06-27T22:58:22.527+02:00 level=INFO msg="getting package" name=@sst-provider/aws version=latest
time=2024-06-27T22:58:22.738+02:00 level=INFO msg="getting package" name=@pulumi/aws version=latest
time=2024-06-27T22:58:23.073+02:00 level=INFO msg="writing package.json"
time=2024-06-27T22:58:23.073+02:00 level=INFO msg="adding dependency" name=aws
time=2024-06-27T22:58:23.074+02:00 level=INFO msg="fetching deps"
time=2024-06-27T22:58:23.252+02:00 level=ERROR msg="exited with error" err="failed to run bun install "
× Unexpected error occurred. Please check the logs or run with --verbose for more details.

I feel like this issue could be resolved by simply defaulting to npm i or trying to detect if the user is already using a different package manager, for example i had pnpm already set up in the repository where I wanted to run sst init.

It's not really a breaking bug since I can just install my dependencies manually, however I was already aware that my system wasn't compatible with bun - a user that isn't familiar with this issue might feel a bit more perplexed.

If you guys decide this is a case you would like to support then I would be happy to assist and provide a PR, but I would also understand if you determine that it's out of scope.

This is really an issue with Bun so I don't know how much my hardware specs will contribute, but I can provide them anyway to give you guys an idea of what I'm working with.

$ lscpu
Architecture:                       x86_64
CPU op-mode(s):                     32-bit, 64-bit
Address sizes:                      36 bits physical, 48 bits virtual
Byte Order:                         Little Endian
CPU(s):                             2
On-line CPU(s) list:                0,1
Vendor ID:                          GenuineIntel
Model name:                         Intel(R) Core(TM)2 Duo CPU     T9400  @ 2.53GHz
CPU family:                         6
Model:                              23
Thread(s) per core:                 1
Core(s) per socket:                 2
Socket(s):                          1
Stepping:                           10
Frequency boost:                    enabled
CPU max MHz:                        2534.0000
CPU min MHz:                        800.0000
BogoMIPS:                           5054.01
Flags:                              fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts nopl cpuid aperfmperf pni dtes64 monitor ds_cpl smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm pti dtherm ida
L1d cache:                          64 KiB (2 instances)
L1i cache:                          64 KiB (2 instances)
L2 cache:                           6 MiB (1 instance)
NUMA node(s):                       1
NUMA node0 CPU(s):                  0,1
Vulnerability Gather data sampling: Not affected
Vulnerability Itlb multihit:        KVM: Mitigation: VMX unsupported
Vulnerability L1tf:                 Mitigation; PTE Inversion
Vulnerability Mds:                  Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
Vulnerability Meltdown:             Mitigation; PTI
Vulnerability Mmio stale data:      Unknown: No mitigations
Vulnerability Retbleed:             Not affected
Vulnerability Spec rstack overflow: Not affected
Vulnerability Spec store bypass:    Vulnerable
Vulnerability Spectre v1:           Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:           Mitigation; Retpolines, STIBP disabled, RSB filling, PBRSB-eIBRS Not affected
Vulnerability Srbds:                Not affected
Vulnerability Tsx async abort:      Not affected
$ dmidecode -t memory
# dmidecode 3.3
Getting SMBIOS data from sysfs.
SMBIOS 2.4 present.

Handle 0x0007, DMI type 5, 20 bytes
Memory Controller Information
	Error Detecting Method: None
	Error Correcting Capabilities:
		None
	Supported Interleave: One-way Interleave
	Current Interleave: One-way Interleave
	Maximum Memory Module Size: 4096 MB
	Maximum Total Memory Size: 8192 MB
	Supported Speeds:
		Other
	Supported Memory Types:
		DIMM
		SDRAM
	Memory Module Voltage: 2.9 V
	Associated Memory Slots: 2
		0x0008
		0x0009
	Enabled Error Correcting Capabilities:
		Unknown

Handle 0x0008, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: DIMM Slot 1
	Bank Connections: 0 1
	Current Speed: 42 ns
	Type: DIMM SDRAM
	Installed Size: 4096 MB (Double-bank Connection)
	Enabled Size: 4096 MB (Double-bank Connection)
	Error Status: OK

Handle 0x0009, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: DIMM Slot 2
	Bank Connections: 2 3
	Current Speed: 42 ns
	Type: DIMM SDRAM
	Installed Size: 4096 MB (Double-bank Connection)
	Enabled Size: 4096 MB (Double-bank Connection)
	Error Status: OK

Handle 0x002B, DMI type 16, 15 bytes
Physical Memory Array
	Location: System Board Or Motherboard
	Use: System Memory
	Error Correction Type: None
	Maximum Capacity: 8 GB
	Error Information Handle: Not Provided
	Number Of Devices: 2

Handle 0x002C, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x002B
	Error Information Handle: No Error
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 4 GB
	Form Factor: SODIMM
	Set: None
	Locator: DIMM 1
	Bank Locator: Bank 0/1
	Type: DDR3
	Type Detail: Synchronous
	Speed: 1066 MT/s
	Manufacturer: 80CE            
	Serial Number: 458591D7        
	Asset Tag: 1003
	Part Number: M471B5273BH1-CF8  

Handle 0x002D, DMI type 17, 27 bytes
Memory Device
	Array Handle: 0x002B
	Error Information Handle: No Error
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 4 GB
	Form Factor: SODIMM
	Set: None
	Locator: DIMM 2
	Bank Locator: Bank 2/3
	Type: DDR3
	Type Detail: Synchronous
	Speed: 1066 MT/s
	Manufacturer: 80CE            
	Serial Number: 458591D3        
	Asset Tag: 1003
	Part Number: M471B5273BH1-CF8  

Else you could just send me a new laptop init

@chrisandrewcl
Copy link

I had a similar error some time ago, although not in init. As a workaround, try setting NO_BUN=true in your env.

@remirth
Copy link
Author

remirth commented Jun 28, 2024

This solved my issue, thanks!

@remirth remirth closed this as completed Jun 28, 2024
@thdxr thdxr transferred this issue from sst/ion Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants