xjia

7 ms·

1.
Lummis Announces Revolutionary Proposal to Supercharge the Dollar(lummis.senate.gov)
1 points by xjia 2y ago|0 comments
2.
SDV Deprecation Announcement(learn.microsoft.com)
1 points by xjia 2y ago|0 comments
3.
Technical Details on Today's Outage(crowdstrike.com)
124 points by xjia 2y ago|131 comments
4.
867-5309/Jenny(en.wikipedia.org)
3 points by xjia 2y ago|1 comments
5.
by xjia 3y ago
Indeed. We are already optimizing this. And spot instances are coming soon as well :-)
6.
by xjia 3y ago
Before this we were using https://github.com/actions/actions-runner-controller but that's running on K8s instead of VMs. So along with common limitations of running CI jos in K8s/container, it cannot have exa
7.
by xjia 3y ago
Persistent disks are implemented as EBS snapshots, so the process is something like: 1. Create EC2 instance for runner #1. Find out there is no existing snapshot, so an empty volume is created and attached. 2. Runner #1 runs exactly 1 job a
8.
Show HN: DimeRun v2 – Run GitHub Actions on AWS EC2(github.com)
5 points by xjia 3y ago|6 comments
9.
by xjia 3y ago
We are working on an alternative that's 100% compatible with GHA but much cheaper and faster. Check out https://dime.run/
10.
by xjia 3y ago
From [0]: > gShoe is an internal joke about a product [Google] shouldn't make, and is used in many internal trainings as a placeholder for any Google product [0]: https://www.reddit.com/r/google/s/fHCB
11.
by xjia 3y ago
IIUC the actual computation (e.g. compiling, linking, ...) happens on client (CI or developer) machines and the results are written to the server-side cache. By spoofing I meant to say that an authenticated but malicious client (intentional
12.
by xjia 3y ago
What is the benefit of using a remote cache instead of a local ~/.cache directory? Is it only for sharing build results among team members? How do you make sure the build results are not spoofed?
13.
by xjia 3y ago
Awesome! If there is any problem just post it in GitHub issues. We will also be releasing 2023.4 very soon.
14.
by xjia 3y ago
Yes, the code of the analyzer itself cannot be built on macOS or Windows directly. In those cases you will have to use either podman or docker to use the binaries prebuilt on/for Linux. The whole system depends on a lot of other stuff
15.
by xjia 3y ago
That's running the prebuilt container image. The README has instructions on how to build from source.
16.
by xjia 3y ago
I'm not sure about the timeline because that depends on a lot of things. In the meantime I guess you could start with AUTOSAR C++14. MISRA C++:2023 is essentially built on top of that. For enterprise edition simply email to hello[AT]na
17.
by xjia 3y ago
If you build it from source it's actually a bunch of regular executables. Running as a container is for the purpose of making the environments hermetic/reproducible so that it's easier to support users.
18.
by xjia 3y ago
No. Using GPL software has nothing to do with the code processed by it. Think about the GCC compiler :)
19.
NaiveSystems Analyze – FOSS static analyzer for MISRA C/C++, AUTOSAR C++14, etc.(github.com)
45 points by xjia 3y ago|13 comments
20.
by xjia 3y ago
Clang has its own limitations. And it takes more effort than just writing the checkers. We open sourced our previously proprietary static analyzer (mostly based on Clang but also integrated other useful tools) but the commercial/enter
21.
by xjia 3y ago
2023 is supported in the enterprise edition but not in the community edition yet. We gradually move features from EE to CE as new features added to EE. So you can expect 2023 support in CE in the future :-)
22.
by xjia 3y ago
If you are interested in this, take a look at NaiveSystems Analyze [0] which is a free and open source static analyzer for checking MISRA compliance etc. Disclaimer: I'm the founder. It has been battle tested with real customers in aut
23.
by xjia 3y ago
Yes I totally understand the concern. We are actively working on SOC 2 and other compliance stuff to help with this. But honestly I feel the compliance requirements are weaker than what we actually implemented. For example proper secure boo
24.
by xjia 3y ago
I had a similar experience with ARC (actions-runner-controller). One of the machines in the fleet failed to sync its clock via NTP. Once a job X got scheduled to it, the runner pod failed authentication due to incorrect clock time, and then
25.
by xjia 3y ago
If you are interested in persistent cache, maybe take a look at https://dime.run
26.
by xjia 3y ago
We have persistent disks support in https://dime.run
27.
by xjia 3y ago
We support machines with large core counts in https://dime.run so check it out :)
28.
by xjia 3y ago
We are essentially competing in the same space with https://dime.run/ We also use VMs. But they are persistent. So you always see your runners as Online in GitHub UI. We achieve this by investing in virtualization technolog
29.
by xjia 3y ago
Or base58, e.g. https://api.rubyonrails.org/classes/SecureRandom.html#method...
30.
by xjia 3y ago
We are slowly onboarding customers in batch. The waitlist is for batching, not because the service is not ready. We do need more traffic to get better efficiency and predictability in batching.

More ›