This repository has been archived by the owner on Sep 12, 2023. It is now read-only.
test: add a test for investigating nsfw in a stream #479
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
Added CodeQL workflow
Added CodeQL for Windows
use Ubuntu for CMake
* feat: add nudity detection codes to the wolf engine issue WolfSource#444 * feat: requested changes in pr is applied issue WolfSource#444 * feat: update files isuue WolfSource#444
* feat: add gstreamer wrapper issue WolfSource#441 * refactor: rename wolf::gst to wolf::media::gst namespace issue WolfSource#441
* index on badri: b6f6d64 fix: cmake preset * feat: write grpc wrapper issue WolfSource#468 * feat: add grpc test issue WolfSource#468
PooyaEimandar
force-pushed
the
main
branch
6 times, most recently
from
0ba01d7 to
8c5272a
Compare
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.
Pull Request Checklist
Please check if your pull request fulfils the following requirements:
Pull Request Type
What kind of change does this pull request introduce?
What is the current behaviour?
Issue #460
What is the new behaviour?
Does this Pull Request introduce a breaking change?
Other information
Closes #460