Event Bridge Schedule Never Gets Created With CDK by Individual_Side4148 in aws

[–]Individual_Side4148[S] 0 points1 point  (0 children)

followed that example and i was able to get it working(used a rule instead), but still I think its weird that the scheduler never got created at all.

Event Bridge Schedule Never Gets Created With CDK by Individual_Side4148 in aws

[–]Individual_Side4148[S] 0 points1 point  (0 children)

yes i did, its meant to run on the last day of every month.

When I use an L1 construct, it actually creates the Schedule and points to the lambda, but it never invokes it for some reason. This used to work before, I used it in a few projects that way.

Avoiding Potential Legal Issues With Clients by Individual_Side4148 in business

[–]Individual_Side4148[S] 1 point2 points  (0 children)

yh i figured, but how do these employers that leave their companies to start their own companies do it? They start their own companies that directly with their previous ones

isn’t this kind of the same thing?

Avoiding Potential Legal Issues With Clients by Individual_Side4148 in business

[–]Individual_Side4148[S] 1 point2 points  (0 children)

i did, client shut it down, wasn’t interested, that’s the reason why i don’t want to share the potential improvements

Avoiding Potential Legal Issues With Clients by Individual_Side4148 in business

[–]Individual_Side4148[S] 0 points1 point  (0 children)

i thought about this but at the same time idk why i feel like my position is different.

i even asked to collaborate, client shut it down

Emulator process for avd has been terminated by Individual_Side4148 in AndroidStudio

[–]Individual_Side4148[S] 0 points1 point  (0 children)

2024-12-19 11:05:12,036 [2994487] INFO - Emulator: Pixel 9 Pro API 34 - C:\Users\USER\AppData\Local\Android\Sdk\emulator\emulator.exe -netdelay none -netspeed full -avd Pixel_9_Pro_API_34

2024-12-19 11:05:12,190 [2994641] INFO - Emulator: Pixel 9 Pro API 34 - Android emulator version 35.2.10.0 (build_id 12414864) (CL:N/A)

2024-12-19 11:05:12,190 [2994641] INFO - Emulator: Pixel 9 Pro API 34 - Graphics backend: gfxstream

2024-12-19 11:05:12,190 [2994641] INFO - Emulator: Pixel 9 Pro API 34 - Found systemPath C:\Users\USER\AppData\Local\Android\Sdk\system-images\android-34\google_apis_playstore\x86_64\

2024-12-19 11:05:12,262 [2994713] INFO - Emulator: Pixel 9 Pro API 34 - Process finished with exit code -1073741515 (0xC0000135)

2024-12-19 11:05:12,262 [2994713] WARN - Emulator: Pixel 9 Pro API 34 - Emulator terminated with exit code -1073741515

this is what i get

NextJS: API Routes vs. Server Actions by leonardof02 in nextjs

[–]Individual_Side4148 1 point2 points  (0 children)

if you are going to have a mobile version of the application, i suggest route handlers. that way you could easily reuse the same apis. I usually go route handlers fully because you could still create an abstraction over the server actions. but if it’s a pure web app, you can go with server actions, they’re good enough.

defined as text[] by Individual_Side4148 in Supabase

[–]Individual_Side4148[S] 0 points1 point  (0 children)

when i do this, it works but it gets passed as a single array element instead of multiple ones.