❌

Normal view

SFO2 Power Feed Maintenance

Jun 7, 19:11 UTC
Completed - Our datacenter provider has informed us that they are not able to perform this maintenance during the communicated window and will be rescheduling it for a later date. We apologize for any confusion from the previous update, but this maintenance did not begin and there was no impact to any services. We will notify you via email and a new maintenance post on status.digitalocean.com with the updated date and timings for this maintenance.

If you have any questions or continue to experience issues, please reach out via a Support ticket on your account.

Jun 7, 11:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Jun 7, 02:44 UTC
Scheduled - Start: 2024-06-07 11:00 UTC
End: 2024-06-07 21:00 UTC

During the above window, our data center team will be performing maintenance on redundant upstream electrical systems in our SFO2 region.

Expected impact:

We don’t expect to see any impact to customer resources as the electrical systems are redundant and our team will isolate one unit at a time during the maintenance. In the highly unlikely event that we lose power to both systems simultaneously, affected Droplets and Droplet-based services would experience downtime for a brief period of time. We will endeavor to keep this to a minimum should that situation arise.

If you have any questions or concerns related to this maintenance, please send us a ticket from your cloud support page https://cloudsupport.digitalocean.com/s/createticket.

FreshRSS 1.24.1

5 June 2024 at 10:35

This is a bug-fix release for the 1.24.0 release, addressing several regressions.

A few highlights ✨:

  • New button to export OMPL of a category
  • Many bug fixes

This release has been made by @Alkarex, @math-GH, and newcomers @ramazansancar, @robinmetral

Full changelog:

  • Features
    • New button to export OMPL of a category #6519
    • Better git error messages in built-in Web update #6496
  • Bug fixing
    • Fix regression HTTP GET curl options #6492
    • Fix regression of mark as read if an identical title already exists #6536, #6543
    • Fix connection to PostgreSQL databases with uppercase letters #6482
    • Fix UI regression hover over title while having the navigation buttons in mobile view #6486
    • Fix UI for some drag & drops #6505, #6508
  • i18n
  • Misc.

Cloud Control Panel and API

Jun 5, 15:30 UTC
Resolved - From 12:10 - 12:41 UTC our Engineering team identified and resolved an issue impacting the Cloud Control Panel and API across multiple regions.

During this time, users may have experienced trouble while viewing the IP address on their newly deployed droplets. Our Engineering team was able to take quick action to mitigate the impact and resolve the issue. All services are now functioning as expected.

Thank you for your patience, and we apologize for any inconvenience. If you continue to experience any issues, please open a Support ticket for further analysis.

Un tribunal arbitral condena a Empresas Bern a pagar $77.7 millones a sus socios en Town Center

9 July 2024 at 17:22

Un tribunal arbitral acaba de condenar al Grupo Empresas Bern (GEB) a pagar $77.7 millones en concepto de daΓ±os, costas e incumplimientos en la construcciΓ³n del centro comercial Town Center, en Costa del Este.

El mismo tribunal tambiΓ©n negΓ³ un reclamo presentado por GEB para que sus socios en el centro comercial le traspasaran una finca valorada en $19.5 millones sobre la cual se levanta un hotel que estΓ‘ casi terminado, asΓ­ como comisiones por venta de locales comerciales, entre otras cosas. En total, GEB reclamaba una cuantΓ­a de $61.1 millones, pero no recibirΓ‘ nada.

De este modo se intenta poner fin a un conflicto que enfrentΓ³ a dos poderosos grupos empresariales del paΓ­s: por un lado GEB, un puΓ±ado de empresas manejadas por el ingeniero HermΓ‘n Bern y su hijo JosΓ© Manuel Bern, y por el otro la sociedad Costa del Este Town Center Group, S.A., conformada a su vez por Inversiones PanamΓ‘ Viejo, S.A. y Townshare, S.A., representadas por Raimundo Casimiro LΓ³pez Arango y Alberto Motta Page, respectivamente.

La decisiΓ³n estΓ‘ contenida en un laudo de 241 pΓ‘ginas firmado el 24 de mayo pasado por el tribunal arbitral integrado por el exmagistrado de la Sala Tercera de lo Contencioso Administrativo, AdΓ‘n Arnulfo Arjona (presidente), y los abogados Narciso Arellano Moreno y Jaime Mora, del Centro de ConciliaciΓ³n y Arbitraje de PanamΓ‘ (CeCAP). Los tres Γ‘rbitros fueron seleccionados de comΓΊn acuerdo entre las partes.

Originalmente, los dos grupos eran socios a partes iguales, segΓΊn consta en un acuerdo de accionistas (SHA, por sus siglas en inglΓ©s) pactado el 24 de octubre de 2013, para la construcciΓ³n de un proyecto inmobiliario comercial sobre tres fincas en Costa del Este, valoradas en $28 millones. Las fincas eran controladas por las familias LΓ³pez y Motta. El aporte de GEB serΓ­a de $28 millones, en β€œespecie”.

Posteriormente, Luzeo Corporation, una sociedad representada por HermΓ‘n Bern, dio en garantΓ­a la mitad de sus acciones en virtud de un prΓ©stamo que le otorgΓ³ Townshare. Al no cumplir con los tΓ©rminos del referido prΓ©stamo, se ejecutΓ³ la garantΓ­a, de tal modo que como accionistas de Costa del Este Town Center Group quedaron Luzeo, con 25%; Townshare, con otro 25%, e Inversiones PanamΓ‘ Viejo, con 50%.

Hasta el 3 de julio de 2023, el presidente de Costa del Este Town Center Group fue JosΓ© Manuel Bern.

El tribunal observΓ³ que entre 2013 y 2018, el control administrativo de todo el proyecto estuvo a cargo de los Bern: JosΓ© Manuel, como presidente de Costa del Este Town Center Grupo, y su padre HermΓ‘n, como presidente de Luzeo. Esta situaciΓ³n originΓ³ circunstancias que, por cinco aΓ±os, β€œno favorecieron el desempeΓ±o de actuaciones independientes” entre ambos grupos, segΓΊn el tribunal arbitral. Como ejemplo estΓ‘ que ni siquiera se conformΓ³ un comitΓ© ejecutivo, en el que se suponΓ­a que debΓ­an estar cuatro directivos: dos por parte de GEB y dos por el grupo de Town Center, es decir, los Motta y los LΓ³pez.

Discrepancias

Los desencuentros entre los socios empezaron cinco aΓ±os despuΓ©s de la firma del SHA, en 2018, por la gestiΓ³n en la administraciΓ³n, construcciΓ³n, comercializaciΓ³n y venta del proyecto. La mayorΓ­a de estas tareas, hasta entonces, fueron asumidas por GEB y sus empresas afiliadas. Costa del Este Town Center Group alegΓ³ que se ejecutaron obras y se adoptaron decisiones sin la aprobaciΓ³n de su junta de accionistas o su junta directiva, como estaba consignado en el acuerdo pactado en octubre de 2013.

Alberto Motta Page y JosΓ© Manuel Bern.
Alberto Motta Page y JosΓ© Manuel Bern.

Ese fue el caso, por ejemplo, de la construcciΓ³n de un hotel, que GEB hizo sin consultar y que no estaba incluido en el plan maestro aprobado por los accionistas. Tampoco estaba contemplado en el contrato de construcciΓ³n suscrito con Constructora Tece, S.A. (una subsidiaria de empresas Bern). Posteriormente, Herman Bern reconociΓ³, en un correo electrΓ³nico enviado a Stanley Motta en el aΓ±o 2017, que fue Γ©l quien adoptΓ³ la decisiΓ³n de construir el hotel, porque consideraba que era un β€œasset” del mall, β€œmΓ‘s que un negocio”.

β€˜Partes relacionadas’

En el proceso arbitral se acreditΓ³ que JosΓ© Manuel Bern firmΓ³ el contrato de construcciΓ³n con Tece el 2 de diciembre de 2013, aunque entonces no era el representante legal del grupo. Tampoco habΓ­a sido autorizado por la junta de accionistas ni la junta directiva de Costa del Este Town Center Group. En tanto, en nombre de la constructora firmΓ³ Juan Carlos MuΓ±oz, β€œun empleado del grupo Bern”.

Aunque GEB, en su demanda, afirmΓ³ que Constructora Tece fue creada exclusivamente para la ejecuciΓ³n del centro comercial, hay informes periciales aportados por la contraparte que indican que tambiΓ©n realizΓ³ obras en otras locaciones (como el hotel Playa Bonita), que al 31 de diciembre de 2022 sumaban $17.9 millones.

El proyecto, originalmente presupuestado en $186.1 millones, terminΓ³ costando $212.6 millones. Y el Γ‘rea de construcciΓ³n, que debΓ­a ser de 182,744 m2, se elevΓ³ a 206,350 m2.

La conciliaciΓ³n fallida

En abril de 2022, las partes se sometieron a un proceso de conciliaciΓ³n, pero, ante la imposibilidad de dirimir sus diferencias, en noviembre de ese mismo aΓ±o pasaron al siguiente nivel: el arbitraje. GEB demandΓ³ a Costa del Este Town Center Group y viceversa.

Luego de escuchar a las partes, testigos, abogados y peritos, los Γ‘rbitros Arjona, Arellano y Mora rechazaron todas las pretensiones de GEB y, en cambio, le condenΓ³ a pagar $77.7 millones por el incumplimiento de sus deberes societarios, conforme fue pactado en el acuerdo de accionistas de octubre de 2013, asΓ­ como de sus obligaciones como administrador del proyecto, daΓ±os causados por la construcciΓ³n y negligencia en la comercializaciΓ³n de los locales del centro comercial. De esa cantidad, $7.5 millones corresponde a costa y gastos.

β€œEl tribunal arbitral ha podido constatar el cΓΊmulo de incumplimientos en que incurriΓ³ Grupo de Empresas Bern en cuanto a sus obligaciones como administrador del proyecto, inobservancia inexcusables del SHA, falta de obtenciΓ³n de autorizaciones de la junta directiva de Town Center para la contrataciΓ³n de servicios, entre otras”, seΓ±ala el laudo.

En cuanto al hotel, el tribunal declarΓ³ que el terreno y las mejoras pertenecen β€œen su totalidad” a Grupo Town Center, β€œy que Grupo Empresas Bern no tiene derechos sobre ello”.

El laudo arbitral se fundamenta en la ConstituciΓ³n, los cΓ³digos de Comercio y Civil de PanamΓ‘, la Ley 131 de 2013 (que regula el arbitraje comercial) y el reglamento de arbitraje del CeCAP.

Β© Presentado por: Town Center Costa del Este

El proyecto, originalmente presupuestado en $186.1 millones, terminΓ³ costando $212.6 millones.

DNS Resolution in Multiple Regions

Jun 3, 15:29 UTC
Resolved - Our engineering team has resolved the issues with increased latency in the time for updating DNS records. If you continue to experience problems, please open a ticket with our support team. We apologize for any inconvenience.

Jun 3, 12:27 UTC
Monitoring - Our engineering team has identified the cause and implemented a fix to resolve the issue with increased latency in the time for updating DNS records and is monitoring the situation. We will post an update as soon as the issue is fully resolved.

Jun 3, 11:30 UTC
Investigating - Our Engineering team is investigating an issue with intermittent failures and increased latency in DNS resolution across multiple regions.

During this time, users may experience issues with DNS resolution, or see errors returned when querying DNS records which are hosted on the DigitalOcean nameservers. Users may also experience DNS resolution issues while reaching out to their Managed Kubernetes Clusters.

We apologize for the inconvenience and will share an update once we have more information.

Event processing in TOR1

May 30, 22:07 UTC
Resolved - Our Engineering team has confirmed that this incident has been fully resolved.

Thank you for your patience. If you continue to experience any problems, please open a ticket with our support team for further review.

May 30, 20:51 UTC
Monitoring - Our Engineering team has implemented a fix to resolve the issue with event processing on the two nodes in TOR1. At this time, users should no longer face issues with powering on, powering off, and power cycling Droplets.

We are monitoring the situation closely and will post an update as soon as we confirm the issue is fully resolved.

May 30, 20:16 UTC
Identified - After further investigation, our Engineering team has determined the scope of this issue to be limited to two physical nodes in our TOR1 datacenter. Power event errors seen in NYC3 are not related to this incident and are a result of a single hypervisor issue, which is being remediated separately.

The root cause for event issues in TOR1 has been identified and a fix is underway. We will update the title of this incident shortly to accurately reflect the scope and will post an update as soon as the fix has rolled out or there is additional information to share.

May 30, 19:42 UTC
Investigating - Our Engineering team is investigating an uptick in reports of issues with Power on, Power off, and Power cycle events in our TOR1 and NYC3 regions. During this period, customers might experience errors and/or delays in powering on, powering off, or rebooting Droplets.

We will post an update as soon as additional information is available.

Kubernetes and App Platform Pages in the Cloud Control Panel for New Users

May 29, 11:47 UTC
Resolved - Our Engineering team has confirmed that the issue with accessing Kubernetes and App Platform for new users has been completely resolved. New users should now be able to access all aspects in the Cloud Control Panel.

If you continue to experience problems, please open a ticket with our support team.

Thank you for your patience and we apologize for any inconvenience.

May 29, 10:47 UTC
Monitoring - Our Engineering team has identified the root cause and deployed a fix for the issue impacting access to Kubernetes and App platform pages for new users. New users should now be able to access Kubernetes and App platform in our Cloud Control Panel successfully.

We will continue to monitor this at our end and will share an update once the problem is resolved completely.

May 29, 07:19 UTC
Investigating - Our Engineering team is investigating an issue where newly signed up users are unable to access Kubernetes and App platform pages in our Cloud Control Panel. Beginning at 07:00 UTC on May 29th, new users may see "Oops, you do not have access to view this resource or page" in our Cloud Control Panel.

We apologize for the inconvenience and will share an update once we have more information.

Uptime Check Creates on the Cloud Panel

May 24, 00:41 UTC
Resolved - Our engineering team has resolved the issue issue with creating new Uptime checks in the Monitoring section of the Cloud Control Panel.

Thank you for your patience. If you continue to experience any problems, please open a support ticket from within your account.

May 24, 00:07 UTC
Monitoring - Our Engineering team has implemented a fix regarding the issue with creating new Uptime checks in the Monitoring section of the Cloud Control Panel. We are monitoring the situation to ensure there is no recurrence.

We will post another update once we confirm the issue is fully resolved.

May 23, 23:26 UTC
Investigating - Our Engineering team is investigating an issue with creating new Uptime checks in the Monitoring section of the Cloud Control Panel. From 15:00 UTC on the 21st, customers may experience errors while creating new Uptime checks on the Monitoring page.

We apologize for the inconvenience and will share an update once we have more information.

FreshRSS 1.24.0

23 May 2024 at 04:54

A few highlights ✨:

  • New shareable user query mechanism to share lists of articles by HTML, RSS, OPML
    • Deprecates RSS sharing with master token
  • New CLI for database backup & restore
  • New JSON scraping mode to consume JSON data and JSON Feeds
  • New support for HTTP POST
  • New option to automatically add labels to incoming articles
  • New button to download a feed configuration as OPML
  • Many bug fixes

This release has been made by several contributors: @aledeg, @Alkarex, @andris155, @CilgaIscan, @cn-tools, @den13501, @eta-orionis, @Frenzie, @FromTheMoon85, @gmgall, @hkcomori, @jakopo87, @laxmanpradhan, @loviuz, @math-GH, @MayMeow, @OctopusET, @PedroPMS, @roughnecks, @soniyaprasad77, @th0mcat, @thomasrenes, @tiborepcek, @wolfpld, @yzqzss, @zukizukizuki
and several newcomers @eta-orionis, @gmgall, @hkcomori, @jakopo87, @jgtorcal, @krm-shrftdnv, @laxmanpradhan, @loviuz, @PedroPMS, @roughnecks, @soniyaprasad77, @th0mcat, @zukizukizuki

Full changelog:

  • Features
    • New shareable user query mechanism to share list of articles by HTML, RSS, OPML #6052
      • Deprecates RSS sharing with master token
    • New JSON scraping mode to consume JSON data #5662, #6317,
      #6369, #6476
    • New support for JSON Feeds #5662
    • New support for HTTP POST #5662
    • New options to automatically add labels to incoming articles #5954
    • New button to download a feed configuration as OPML #6312
    • Web scraping support more encodings such as EUC-JP #6112
    • Web scraping support password-protected queries (refactor some cURL options and use CURLOPT_USERPWD) #6177
    • Web scraping HTTP GET allow UTF-8 even when charset is far from top #6271
    • Allow manual refresh of disabled feeds #6408
    • Allow multiple authors on enclosures #6272
    • New system option in data/config.php for number of feeds to refresh in parallel from UI #6124
  • CLI
  • API
    • New compatible app Read You #4633, #6050
    • Reduce API memory consumption #6137
    • Allow negative feed IDs for future special cases #6010
    • Only return OK for requests without query parameters #6238
  • Bug fixing
    • Better account for some edge cases for cron and automatic labels during feed refresh #6117
    • Better support for thumbnails in RSS feeds #5972
    • Auto-update PostgreSQL or MariaDB / MySQL databases for column details changes since FreshRSS 1.21.0 #6279
      • For SQLite, DB update require running ./cli/db-backup.php ; ./cli/db-restore.php --force-overwrite
    • Fix SQLite import of exports produced before FreshRSS 1.20.0 #6450
    • Fix SQLite release handle to fix deleting users on Microsoft Windows #6285
    • Fix to allow admins to create user even when there are Terms Of Service #6269
    • Fix updating the uncategorized category deletes the title #6073
    • Fix disable master authentication token #6185
    • Fix CSS selector preview #6423
    • Fix CSS selector encoding #6426
    • Fix export of CSS selector in OPML of individual feeds #6435
    • Fix OPML import of CURLOPT_PROXYTYPE #6439
    • Fix favicon with protocol-relative URLs have duplicate slashes #6068
    • Fix feed TTL+muted logic #6115
    • Fix apply mark as read to updated articles too #6334
    • Fix ZIP export on systems with custom temp folder #6392
    • Fix number of posts per page during paging #6268
    • Fix clipboard sharing UI #6301
    • Fix shortcut for clipboard sharing #6277
    • Fix user-query filter display #6421
  • SimplePie
  • Security
    • Replace iframe allow attribute #6274
  • Deployment
    • Disable unused PHP modules in our Debian-based Docker image #5994
  • UI
  • i18n
  • Extensions
    • Sanitize parsing list of extensions names and version number #6016,
      #6155, Extensions#214, #6186
    • Apply filter actions such as mark as read after the entry_before_insert hook for extensions #6091
    • New developer command to test all third-party extensions Extensions#228, #6273
      • composer run-script phpstan-third-party
    • New function Minz_Extension::amendCsp() for extensions to modify HTTP headers for Content Security Policy #6246
    • New property FreshRSS_Entry::isUpdated() for extensions to know whether an entry is new or updated #6334
  • Compatibility
    • Fix PHP 7.4 compatibility for automated tests #6038, #6039
    • Fix PHP 8.2+ compatibility for e-mails #6130
    • Use PHP 8.3+ #[\Override] #6273
  • Misc.

NYC3 Network Maintenance

May 29, 14:00 UTC
Completed - The scheduled maintenance has been completed.

May 29, 10:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

May 22, 17:13 UTC
Scheduled - Start: 2024-05-29 10:00 UTC
End: 2024-05-29 14:00 UTC

During the above window, we will be performing maintenance on core switches in our NYC3 datacenter as part of network upgrades.

Expected Impact:

Inbound and outbound traffic for Droplet-based services in NYC3 may experience a few brief interruptions as traffic is isolated from core switches being upgraded. This impact would be for a duration of 5 to 10 seconds and could occur a few times within the maintenance window. Our team will make every effort to seamlessly drain traffic in order to limit customer impact.

If you have any questions related to this issue please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket

Deployment of Serverless Functions on App platform

May 21, 09:47 UTC
Resolved - As of 09:05 UTC, our Engineering team has confirmed the full resolution of this issue. All users should be able to deploy Serverless Functions from the App UI without any issues.

If you continue to experience problems, please open a ticket with our support team. Thank you for being so patient and we apologize for any inconvenience.

May 21, 09:18 UTC
Update - We are still monitoring the issue impacting Serverless Functions. From the App UI, Serverless Functions should be deployable by all users.

Apologies for the inconvenience caused. We will post an update as soon as the issue is fully resolved.

May 21, 09:12 UTC
Monitoring - Our Engineering team has deployed a fix to resolve an issue with Serverless Functions. All users should be able to deploy Serverless Functions from the App UI.

We are monitoring the situation closely and will share an update once the issue is resolved completely.

May 21, 08:26 UTC
Investigating - As of 06:38 UTC, our Engineering team is investigating an issue with Serverless Functions.

Users may see errors when attempting to deploy Serverless Functions from the App UI.

We apologize for the inconvenience and will share an update once we have more information.

❌