That said; it is amazing how many sign languages can come to similar conclusions due to "always trying to find the simplest way of explaining yourself".
1,162 karma · joined November 6, 2013
Check out what I do at https://github.com/jbergstroem.
[ my public key: https://keybase.io/jbergstroem; my proof: https://keybase.io/jbergstroem/sigs/xNH99zh5DSCLJR_hrHtShFLmo8RcAbg79Hs506_5KdI ]
That said; it is amazing how many sign languages can come to similar conclusions due to "always trying to find the simplest way of explaining yourself".
I've seen this used in a few contexts, for instance batching requests to a origin (logflare: https://github.com/Logflare/cloudflare-app/blob/master/worke...).
Is this generally seen as ok? I'm planning on building similar things for sending page metrics in parallel to serving traffic.
> > Inability to rate limit Workers in a cost effective way gives me sleepless nights
Agreed, there is something very challenging with the current design of how requests flow through cloudflare.
I have played around with dynamic rules in firewall by manually handling "firewall rules" in a worker as part of a request flow and using KV to share this state. I would then update the cloudflare firewall with api. I had to create a separate service to poll both API and KV to maintain them though.
1: Social. By seeing my coworkers over video I remind myself that I work with people, not pull requests or comments. Perhaps more relevant these times.
2: Discovery. 2.1: A minute or two to just touch on overall goals can instill team spirit. Sales target hit? No angry customers? Perhaps a complaint. It helps with team alignment 2.2: A quick rundown on how each persons day is looking / what people are working on. Perhaps not for blocking but sometimes it is useful to connect two people and let them follow up post-meeting.
https://github.com/marketplace/todo is one of them.
One is called "tiered routing" and is a dropdown in settings whereas the "nat" solution nowadays is implemented as cloudflared.
> Apr 15 17:01:37 mysite cloudflared[12412]: time="2020-04-15T17:01:37Z" level=info msg="Connected to SJC" connectionID=0
> Apr 15 17:03:09 mysite cloudflared[12412]: time="2020-04-15T17:03:09Z" level=error msg="Register tunnel error from server side" connectionID=0 error="Server error: Reached maximum retry 5: dial tcp 198.41.248.96:9100: connect: connection timed out"
> Apr 15 17:03:09 mysite cloudflared[12412]: time="2020-04-15T17:03:09Z" level=info msg="Retrying in 8s seconds" connectionID=0
> For more than 99% of customers, these changes have lowered their GitHub bills, in many cases quite dramatically. For a very small number of customers who use a large percentage of the free Actions minutes allotment each month, these changes have the potential to cause your bill to increase by $20-50/month, depending on how much you use Actions in the future. To offset that possibility, we’re adding a free credit of $500 to your organization’s GitHub account for you to use in any way you want.
I'm sure they have enough info about onboarding and unit economics to see how it will pay off mid to long term.
I'll happily pay for use though, it makes sense and it makes the value addition of github core vs extra more clear.
I personally do client hints polyfilling via workers (dpi matters for things like "fit" even if you use srcset) and transpose images off-workers (github.com/h2non/imaginary). Will do testing and see how they match up in terms of quality.
- Tunnel (cloudflared): https://github.com/cloudflare/cloudflared
- Argo as ingress (k8s): https://github.com/cloudflare/cloudflare-ingress-controller/
No, first version with "NPM support" (see my other comment as why I don't consider it being "supported") was gitlab 11.7, end of january 2019. I was really looking forward to this and were following your verdaccio (an open source npm registry) thread closely. Development then made a 180 and chose to re-implement rudimentary support for npm on top of your current package abstraction instead.
Network Connectivity
Engineers are currently investigating DNS resolution
issues affecting network connectivity to Azure services.
More information will be provided as it becomes available. hotmail-com.olc.protection.outlook.com[104.47.1.33] said: 550 5.7.1
Unfortunately, messages from [<redacted>] weren't sent. Please contact
your Internet service provider since part of their network is on our block
list (S3150). You can also refer your provider to
http://mail.live.com/mail/troubleshooting.aspx#errors.
[VE1EUR01FT028.eop-EUR01.prod.protection.outlook.com] (in reply to MAIL
FROM command)
Reporting-MTA: dns; <redacted>
X-Postfix-Queue-ID: 14A41FEB66
X-Postfix-Sender: rfc822; <redacted>
Arrival-Date: Thu, 14 Mar 2019 14:07:42 +0200 (CEST)I can understand how their huge success of "built-in CI" quickly leads to "built-in XYZ", but competing with github that lets other companies solve developer/ci problems via marketplace (and now CI via their new terraform actions) may lead to loosing market-leader [my take on their product] position for a code/test/review/merge ecosystem.
[1]: https://about.gitlab.com/2018/10/01/gitlab-product-vision/