Posts for: #news

Gitea 1.20.5: The Latest Release

Gitea has announced the release of version 1.20.5 of their software. This update includes important bug fixes, making it highly recommended for users to update to this version.

To create this release, the Gitea team merged 24 pull requests. Users can download pre-built binaries for their specific platform from the downloads page. Detailed installation instructions can be found in the installation guide.

The changelog for version 1.20.5 includes the following enhancements and bug fixes:

Enhancements:

  • Fix z-index on markdown completion
  • Use secure cookie for HTTPS sites

Bug Fixes:

  • Fix git 2.11 error when checking IsEmpty
  • Allow get release download files and lfs files with oauth2 token format
  • Fix orphan check for deleted branch
  • Quote table release in sql queries
  • Fix release URL in webhooks
  • Fix successful return value for SyncAndGetUserSpecificDiff
  • Fix pagination for followers and following
  • Fix issue templates when blank issues are disabled
  • Fix context cache bug & enable context cache for dashboard commits’ authors
  • Fix INI parsing for value with trailing slash
  • Fix PushEvent NullPointerException jenkinsci/github-plugin
  • Fix organization field being null in POST /orgs/{orgid}/teams
  • Fix bug of review request number

Additionally, there have been improvements in testing and documentation, as well as miscellaneous changes.

The contributors to this release include:

Argo CD Releases Version v2.9.0-rc2: Declarative Continuous Delivery for Kubernetes

Argo CD, a declarative continuous delivery tool for Kubernetes, has announced the release of release candidate version v2.9.0-rc2. Argo CD enables users to manage their Kubernetes applications through GitOps, providing a streamlined and efficient approach to continuous delivery of infrastructure.

The new v2.9.0 is set to introduce several new features and improvements to Argo CD. Some of the notable additions in the release candidates include:

  • Support for ignoring application differences in appset
  • Health status and force-sync action for PushSecret
  • AnsibleJob CRD health checks
  • Kustomize patches field
  • Support for AzureDevops Webhooks in appset
  • Dynamic rebalancing of clusters across shards
  • Tree view option in output flag for app sync, app wait, and app rollback
  • Automatic application of extension configs without restarting API-Server
  • Addition of patch_ms and setop_ms timings to reconciliation logs
  • Button for wrapping lines in pod logs viewer in the UI
  • Tree view option in output flag for app get and app resources CLI commands
  • Support for preserving labels and global fields in appset
  • Enablement of haproxy metrics through Helm Chart
  • Shorthand flags for follow and container in app logs
  • Additional environment variable for cluster cache list page buffer size
  • Improved RBAC support for discovery/sync
  • Addition of Dott to users
  • Upgraded notification engine
  • Support for extra attributes for opentelemetry
  • Parallel execution of refresh from UI
  • Topic filter for Gitlab SCM in appset
  • Timeout option for update cluster info
  • Support for apply out of sync flag only in CLI
  • Support for AzureDevops Webhooks
  • SCM Provider option for Gitlab generator to filter shared projects from subgroups projects
  • Short revision in ARGOCD_APP_REVISION_SHORT env variable
  • Integration of kubelogin capability to argocd-k8s-auth
  • Alias application as apps for consistency with notifications engine
  • Restriction of SCM provider URLs
  • Autosync_enabled field in the argocd_app_info gauge
  • Support for self-signed TLS/Certificates for Gitlab SCM Provider
  • Respect RBAC for resource exclusions/inclusions

In addition to these new features, the rc2 release candidate includes various bug fixes and improvements.

For a complete list of changes and enhancements being introduced in v2.9.0, users can refer to the full changelogs of v2.9.0-rc1 and v2.9.0-rc2.

Designing the Raspberry Pi 5: Insights from James Adams and Eben Upton

Raspberry Pi has recently released the highly anticipated Raspberry Pi 5, and it’s been a culmination of years of hard work and decision-making. In an interview with Eben Upton, the co-founder of Raspberry Pi, James Adams dives deep into the design process behind this new iteration of the popular single-board computer. The conversation between Adams and Upton is lengthy and comprehensive, covering all aspects of the design process. For those who prefer watching, there is a video available on the Raspberry Pi YouTube channel.

For more information on the design process of the Raspberry Pi 5, visit the Raspberry Pi website.

Linux 6.7 Indicates Disabled AMD SVM Virtualization in /proc/cpuinfo

Phoronix reports that Linux will now indicate via /proc/cpuinfo if AMD virtualization (SVM) is disabled. This is a quality of life improvement for home lab virtualization when using AMD CPUs. Previously, checking for the presence of Intel virtualization support and its status could easily be done by looking at the flags in /proc/cpuinfo. However, SVM was always shown in /proc/cpuinfo regardless of whether it was disabled in the BIOS. This oversight is finally being corrected in the upcoming Linux 6.7 kernel cycle, with the possibility of back-porting the fix to existing kernel series.

The patch, developed by Red Hat’s Paolo Bonzini, has been queued into TIP’s x86/cpu branch. This patch will now read the appropriate MSR to verify if SVM has been disabled on AMD and Hygon processors. If SVM is disabled, the CPU capability will be cleared, and it will no longer show in /proc/cpuinfo. Previously, the only indication of AMD SVM being disabled was appearing in the kernel log or KVM virtualization failing to work. This small but useful change makes it much easier to check if virtualization is available via the widely-used /proc/cpuinfo interface.

Source: Phoronix.

GLAuth Releases Version 2.3.0: Lightweight LDAP Server for Development, Home Lab, or CI/CD

Go-lang LDAP Authentication (GLAuth) has released version 2.3.0 of its lightweight LDAP server, providing a secure and easy-to-use solution for development, home lab use, or CI/CD environments.

The release introduces both new features and bug fixes to enhance the functionality and stability of the server software. However, it is important to note that there is a breaking change in this version, as the groups table has been renamed to ldapgroups.

The main feature of the v2.3.0 release include an update to the migration code, which now supports table names. In addition to the new feature, a bug fix has been implemented in this release, also regarding ldapgroups.

With this latest release, GLAuth continues to provide a reliable and efficient LDAP server solution for users in development, home lab, and CI/CD environments. The project’s commitment to security, ease of use, and continuous improvement is commendable.

For more information and to download the latest version of GLAuth, visit the official GitHub repository.

Jellyfin Issues Call for Developers

Jellyfin, an open-source media streaming server, has issued a call for developers to join their project and help make it better. As an explicitly anti-commercial platform, Jellyfin relies on a team of volunteers who contribute their time and skills to improve the server, the web interface, and clients. However, the team is currently under strain, with a small core contributor base and a lack of new developers joining the project.

One of the biggest complaints about Jellyfin is the lack of client support and the rough edges in its interface. The team acknowledges these concerns and wants to address them. They are seeking volunteers who can help make the code better, write new code, improve documentation, and contribute to the overall development of the project. They are particularly interested in finding developers, writers, UI/UX designers, non-English language speakers, and enthusiastic individuals who are willing to help.

Jellyfin provides resources and support for new contributors, including active chat channels and forums where the team is available to assist. They emphasize that every contribution, no matter how small, can make a difference in improving the software. They also have an official process for individuals to join the team after proving themselves through quality contributions and a willingness to participate.

The goal of Jellyfin is to address user concerns, limitations, and bugs, and to create the best streaming server possible, free for everyone forever. By joining the project, developers have the opportunity to help shape the future of Jellyfin and make media streaming accessible to a wider audience.

Jellyfin calls on the wider community to support their project and contribute their skills and ideas to help make Jellyfin better. Whether you are a developer, writer, designer, or simply an enthusiast, your help is needed to push the project forward and turn Jellyfin into the ultimate streaming server.