Nov 24, 20:19 UTC
Resolved - From 18:55 to 19:32 UTC, Our Engineering team observed an issue with all control plane operations (Create, Scale, Fork, etc ) for all non-Mongo Managed Database clusters. During this time, users encountered long running requests made either through the Cloud Console UI or API, including provisioning new clusters, listing clusters, etc. Our team has fully resolved the issues as of 19:32 UTC All services for non-Mongo Managed Databases should now be operating normally. If you continue to experience problems, please open a ticket with our support team from within your Cloud Control Panel. We apologize for any inconvenience caused.
Reading view
Billing clients for module fixes when multiple clients need same fix
Just wondering if anybody is in this kind of situation. Let's say I need a fix or a custom feature for a module that will be the same fix/feature for multiple clients. How do you handle billing for this kind of work? Record the time and split it among all the clients? Bill each client for the total amount of work as if you did the fix/feature each time? Bill one client and let the others get the fix/feature for free?
This is happening more and more for me and I have clients on monthly retainers so I make fixes and updates on their request or when I am working on my own features.
For example, recent Drupal updates to CKEditor broke a lot of features in LinkIt, Link Attributes and other related modules. I was taking part in the issue queues, testing solutions and reporting on fixes. For other modules, I provide my own patches and merge requests for the modules.
[link] [comments]
The UAE’s AI strategy winds through Silicon Valley

© Mike Kai Chen for Rest of World