[GSK-2179] Limit size of artifact name and display_name to 255 chars when uploading to Giskard Hub

[kevinmessiaen]

Description

Limit size of artifact name and display_name to 255 chars when uploading to Giskard Hub

Related Issue

• [GSK-2179] Slicing function DB insert fails because of the long name #1605
• GSK- 2179 (Available on linear)

Type of Change

• 📚 Examples / docs / tutorials / dependencies update
• 🔧 Bug fix (non-breaking change which fixes an issue)
• 🥂 Improvement (non-breaking change which improves an existing feature)
• 🚀 New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to change)
• 🔐 Security fix

Checklist

• I've read the CODE_OF_CONDUCT.md document.
• I've read the CONTRIBUTING.md guide.
• I've updated the code style using make codestyle.
• I've written tests for all new methods and classes that I created.
• I've written the docstring in Google format for all the methods and classes that I used.

[linear]

GSK-2179 Slicing function DB insert fails because of the long name #1605

#1605

If the feature name is long, it will cause issues when uploading scan result since generated function name will exceed the db max char allowed

[Inokinoki]

LGTM

Tested with titanic (even though without special characters or exceeded length)

[kevinmessiaen]

LGTM

Tested with titanic (even though without special characters or exceeded length)

You can try with this code:

import giskard

@giskard.slicing_function(name="🏃" * 500)
def sf_long_name(row):
    return True

client = giskard.GiskardClient(
    url="http://localhost:9000",  # URL of your Giskard instance
    key="gsk-...")

sf_long_name.upload(client, "project_key")

I tried with different emojis and it worked (🧑‍🚒 counted as 5 characters, 👩‍👩‍👧‍👦 counted as 11, ...).

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

83.3% Coverage
0.0% Duplication