@edgarsj@berzins404 Nu man tur diezgan skaidri 3.3.6 punkts pasaka, ka pretendents piegādā tikai SIEM platformu, incidentu izvērtēšanu veic pats pasūtītājs
@agris_krusts@androns@krizdabz Toyota hibrīdiem ar ecvt arī nav raustīšanās un braukšanai izmanto gan benzīna motoru, gan elektro, man kaut kā šis variants labāk patīk - korķos ar elektro, uz šosejas benzīna :)
🚀 Gitea v1.24.0 is here!
This release is loaded with 🔒 security, ⚡ performance, and 🛠 quality-of-life improvements:
• Mandatory 2FA (TOTP or WebAuthn) for all users via security.TWO_FACTOR_AUTH
• Anonymous access now supports private/unlisted repos — browse issues, wikis, and code publicly
• New file tree in the repo file view for easier navigation
• Fullscreen mode for a distraction‑free project experience
• Material icons theme for file lists (enable via ui.FILE_ICON_THEME=material)
• ⚡ Performance boosts: database query caching, optimized PR/file list & heatmap loading
🔗 Dive into the full release notes: https://t.co/yo71OWWcKj
#Gitea #Git #DevOps #SelfHosted #DevTools
https://t.co/gEHDRA3QoY
Today KDE has made its biggest release ever, never before in the 25 year history of the project have we announced so many new products at the same time but it brings the newly refreshed base to keep our software foundation strong.
#Plasma6@kdecommunity
New Blog Post From the @golang team: Fixing For Loops in Go 1.22
You can read the original blog post here: https://t.co/Z46akYL1Cf, summary below.
The problem
The below should print a,b,c right?
It will actually print c,c,c. This is due to https://t.co/ELHfLEq4oq
Its also possible to face this issue without concurrency:
In Go 1.22, the Go team are changing for loops to have per iteration scope instead of per loop scope.
This is kind of a big change, so this will only apply to go programs that declare go 1.22 in their go.mod file, or use the GOEXPERIMENT=loopvar environment variable.
Google have been running this change in production since May 2023 and have yet to see any issues with it.
Another great milestone and another great blog post by the Go team!
@laacz Nu man personīgi nepatīk github actions sintakse, man klusais plāns ir nākotnē arī woodpecker CI ieintegrēt tuvāk gitea (vismaz tāds bija sākotnējais plāns, kad iesāku PoC taisīt), ka dažādi CI var pipeline izpildes logus, rezultātus uz gitea sūtīt