https://github.com/tylfin/restructedpyjs
Hey everyone,While developing, I realized that there aren't great existing JS libraries to convert reStructuredText (RST) to HTML. Without WASM, I would've either tried to port the docutils code or pre-compute the rendered HTML.It's exciting to start to leverage these new tools, and I hope this small demo gives you inspiration when thinking about client-side libraries :)
The reason being that there's no relevance to the kernel, and modular kernels, also take this approach with replaceable plug-ins or extensions.
Joking aside, it's really neat to see the scale and sophistication of error detection appearing in these data centers.
I think if revenue or product quality is tied to a VCS, having an active-active or active-passive setup is the way to go.
Fortunately, I'm on an on-prem product so that investment hasn't seemed worth it yet.
This doesn't mean we don't escrow our code, but rather than try to rebuild from source, I just take a short coffee break and wait for the impacted service to come back up :)
I wonder if they have a big feature underway or are just migrating more infrastructure to Azure?
EDIT: Either way, some postmortems would be appreciated before more customers have to look for a backup solution...
https://www.mastercard.us/en-us/vision/corp-responsibility/c...
If you're on a system with cgo available, you can use `GODEBUG=netdns=cgo` to avoid making direct DNS requests.
This is the default on MacOS, so if it was running on four Mac Pro's I wouldn't expect it to be the root cause.
I think the outages could be related to:
1. Github mobile just went public so they may of changed the scaling params to keep up with expected increase in traffic 2. The new notification system seems to be a lot heavier, and they could still be catching up to the changes 3. They were somewhat recently acquired by Microsoft so maybe they're migrating to Azure to reduce expenses
Whatever the cause, 11 days with outages out of 90 is pretty rough when you rely on Github for project management, a central hub for viewing CI, and all VC concerns. Feel bad for the smaller companies that wholly adopted GitOps and are blocked deploying hotfixes during these outages.
> Commenters: please don't reply to job posts to complain about something. It's off topic here.
Specifically can you go into more details about what worries you with containers. Is it insecure images with out of date software, or risky applications inside the containers? Something else?
Obviously having more accessible internet for the rest of the world is a positive.
Ref: https://www.space.com/8791-giant-telescope-50-million-fundin...
The parallel docker build / pushing to a registry is definitely cool.
Isn't the parallel Kubernetes deployment the same as `kubectl apply -f .`?
My experience has always been: GitOps w/ version controlled yaml so when a deploy is triggered all the tests run, if that's successful then a sed is performed to replace some placeholder with the new image tags then it's just `kubectl apply -f .`
I really agree with this. I was working at a company where we were exploring switching from Github enterprise to Gitlab for the K8s integrations, the docker registry, and the CI features.
Following the helm chart installation instructions was a nightmare because we were on-prem w/ a custom cluster. There were a lot of assumptions we had to find workarounds for (e.g. we used an f5 integration to manage our ingresses and performed SSL termination elsewhere so the nginx thing was awful).
The other terrifying bit was the number of services / pods that got brought up with the installation. If I have to monitor my team's services, I really don't want to monitor the health of: NGINX, Postgres, Redis, Minio, Registry, GitLab/sidekiq, GitLab/gitlab-shell, GitLab/gitaly, GitLab/unicorn, and GitLab/migrations.
When it comes to on-prem or self-hosted software I actually prefer running a monolithic application that worst-case I can just bounce or reboot the server.
Slow down, simplify things, and improve the user experience. Gitlab already has enough features to be competitive for a while with the Github + marketplace model.
The part I'm not so sure I agree with is the "system is too jammed up so don't come," sentiment.
I think if someone is having a hard time & they want to reach out to a medical professional that's probably for the best.
Unfortunately that does shift the burden onto the system to train professionals to determine the difference between prescribing antidepressants or talk and time therapy. It's a lot easier to write someone that prescription than hear them out.
Just seems like marketing to me.
Cogo Labs is a startup accelerator. We are looking for a Senior Software Engineer on our Platform Team to take ownership of key initiatives and systems that support our incubating teams and companies in their high growth efforts.
You'll work with engineers, analysts, and exec staff to flesh out requirements, scope projects, and lead implementation and rollout. Ownership and accountability are core to how we build successful teams and as a Senior Software Engineer you will enjoy a high degree of autonomy as we continue building some of Boston's fastest growing startups.
Our team is about 8 people, all local to Cambridge. We're passionate about Golang + Kubernetes, improving as engineers, and helping our customers as much as possible.
Other jobs available, and you can apply directly via https://grnh.se/dko5gxn42
A big part of building successful companies is reaching the right audience. Here at Cogo Labs, we try to build reliable, scalable, and customizable tool chains that allow our businesses to find and attract users who will become loyal customers.
We mostly use Golang + Python + Docker/Kubernetes
See the full list of jobs and details to apply here: https://grnh.se/dko5gxn42
Cheers!