chore(release): merge develop into main branch #838
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There was a bug in PSA where if in splunk_ingest_data first worker errors out or throws exception then it does not write to a file, now other workers would be waiting indefinitely for the file to be present, So the execution would continue in infinitly. To handle this scenario, we can handle the exception thrown by the first worker and make sure that in any case it writes to a file, so that other workers don't wait indefinitly
## [5.2.6-beta.1](v5.2.5...v5.2.6-beta.1) (2024-04-19) ### Bug Fixes * handling infinite loop ([#812](#812)) ([d3111a6](d3111a6))
At the end of the test suite file _event is deleted, but _event.lock is not. This PR fixes it
Current regex for data models support only basic ipv6 regex. Support for advanced representation of ipv6 is required, hence this pr supports that. ref: ipv6 represenation - https://en.wikipedia.org/wiki/IPv6#Address_representation Tested it with gcp addon which as combination of ipv4 and v6 samples in host fields, also tested it on splunk/splunk-add-on-for-okta-identity-cloud#261 where advanced ipv6 represenation is present Added e2e test which tests extraction of some ipv6 formats using src_ip and dest_ip fields in network_traffic data model Tested regex with below samples: Regex : `(?:(?:::ffff:)|(?:[0-9a-fA-F]{1,4}:){6}ffff:)\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}|(?>([a-f0-9]{1,4})(?>:(?1)){7}|(?!(?:.[a-f0-9](?>:|$)){8,})^((?1)(?>:(?1)){0,6})?::(?2)?(?!(?:.[a-f0-9](?>:|$))))|(?>(?>(?1)(?>:(?1)){5}:|(?!(?:.*[a-f0-9]:){6,})(?3)?::(?>((?1)(?>:(?1)){0,4}):)?)?(25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9]?[0-9])(?>\.(?4)){3})` 1234:: 2001:db8:: ::1334 :: ::1325 2001:0db8::1:2:3456 2001::1:2:3 2001:db8::1:2 ::ffff:192.168.1.1 :: ::ffff:192.168.1.112 ::1 2001:0db8::1:2:3 0000:0000:0000:0000:0000:0000:0000:0001 ff02:0000:0000:0000:0000:0000:0000:0001 fe80:0000:0000:0000:a299:9bff:fe18:50d1 2001:0db8:1111:000a:00b0:0000:9000:0200 2001:0db8:0000:0000:abcd:0000:0000:1234 2001:0db8:cafe:0001:0000:0000:0000:0100 2001:0db8:cafe:0001:0000:0000:0000:0200 2001:db80:1000:a000:0000:bc00:abcd:d0b0 1:2:3:4:5:6:7:: fe80::a299:9bff:fe18:50d1 ::3212 ::1212 2001::abcd::1234 2001:db80:1000:a000:0000:bc00:abcd:d0b0 2001::abcd 2001:0000:0000:0000:abcd:0000:0000:1234 2001:0000:0000:abcd:0000:0000:0000:1234 2001:0000:abcd:0000:0000:0000:0000:1234 2001:db8:1111:a:b0:0:9000:200 fe80:0:0:0:a299:9bff:fe18:50d1 0:0:0:0:0:0:0:1 0000:0000:0000:0000:0000:0000:0000:0001 0:0:0:0:0:0:ffff:192.168.10.10 2001:0000:0000:0000:0000:abcd:0000:1 ::ffff:192.168.10.10 2001:0db8::1:2:3
Updating dependecies
harshilgajera-crest
approved these changes
May 15, 2024
|
🎉 This PR is included in version 5.2.6 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Making a new release of PSA.