query history gets a long time to fetch data

Bug description
When I select the query history tab, it takes a long time to retrieve the logs. The logs has exceeded 30K rows in the table, and I believe an index is needed on the table from which the query is fetching.
How to reproduce the bug
When select query history tab.
Screenshots/recordings
No response
Superset version
4.0.2
Python version
3.11
Node version
16
Browser
Not applicable
Additional context
No response
Checklist

[X] I have searched Superset docs and Slack and didn't find a solution to my problem.
[X] I have searched the GitHub issue tracker and didn't find a similar bug report.
[X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

@dosu

@dosu what indexes is needed on the table query.

@dosu one more question: Could low memory be affecting query log fetching, or is it unrelated?

@dosu how can I prevent Superset's Gunicorn from consuming all the server memory, which is causing it to crash?

The query table needs the following indexes to optimize performance:

Index on the results_key column:op.create_index(
    op.f("ix_query_results_key"), "query", ["results_key"], unique=False
)

Index on the combination of user_id and changed_on columns:op.create_index(
    op.f("ti_user_id_changed_on"), "query", ["user_id", "changed_on"], unique=False
)

Index on the sql_editor_id column:op.create_index(
    op.f("ix_query_sql_editor_id"), "query", ["sql_editor_id"], unique=False
)

These indexes should help improve the performance of queries on the query table [1][2][3].
To continue talking to Dosu, mention @dosu.

@dosu need index also for user filtration.

To prevent Superset's Gunicorn from consuming all the server memory and causing it to crash, you can configure Gunicorn with specific settings to manage memory usage more effectively. Here is an example configuration that you can use, based on the docker/run-server.sh script from the Superset repository:
gunicorn \
    --bind "${SUPERSET_BIND_ADDRESS:-<IP_ADDRESS>}:${SUPERSET_PORT:-8088}" \
    --access-logfile "${ACCESS_LOG_FILE:-"-"}" \
    --error-logfile "${ERROR_LOG_FILE:-"-"}" \
    --workers ${SERVER_WORKER_AMOUNT:-10} \
    --worker-class ${SERVER_WORKER_CLASS:-gevent} \
    --worker-connections ${WORKER_CONNECTIONS:-1000} \
    --threads ${SERVER_THREADS_AMOUNT:-20} \
    --log-level "${GUNICORN_LOGLEVEL:-info}" \
    --timeout ${GUNICORN_TIMEOUT:-120} \
    --keep-alive ${GUNICORN_KEEPALIVE:-2} \
    --max-requests ${WORKER_MAX_REQUESTS:-1000} \
    --max-requests-jitter ${WORKER_MAX_REQUESTS_JITTER:-50} \
    --limit-request-line ${SERVER_LIMIT_REQUEST_LINE:-0} \
    --limit-request-field_size ${SERVER_LIMIT_REQUEST_FIELD_SIZE:-0} \
    "${FLASK_APP}"

In this configuration:

--workers 10 sets the number of worker processes.
--worker-class gevent uses the gevent worker class for asynchronous workers.
--worker-connections 1000 sets the maximum number of simultaneous clients.
--max-requests 1000 ensures that each worker will be restarted after handling 1000 requests, which helps in freeing up memory.
--max-requests-jitter 50 adds a random jitter to the max requests setting to prevent all workers from restarting at the same time.

Additionally, you can configure the SUPERSET_WEBSERVER_TIMEOUT setting in the superset/config.py file to ensure that the web server timeout is properly managed. This setting should be lower than your load balancer or proxy timeout settings:
SUPERSET_WEBSERVER_TIMEOUT = int(timedelta(minutes=1).total_seconds())

These settings can help in managing memory usage and preventing crashes due to memory exhaustion [1][2][3].
To continue talking to Dosu, mention @dosu.

@dosu can I assigned specific memory overall cannot exceeded with no limits for workers.

Awesome!


Minor Code Fixes

There are few fixes require in this sample code.

Code line
hostName:'https:/flow.microsoft.com'
should be
hostName:'https://flow.microsoft.com'

2.Code line
container: 'flowDiv'
should have ',' preceding statment
container: 'flowDiv',

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: fac3ad92-eb8f-554a-5de3-14c430e594aa
Version Independent ID: fab1ceb3-5110-4452-0a0d-99346cc31230
Content: Integrate Microsoft Flow with websites and apps - Microsoft Flow
Content Source: flow-docs/developer/embed-flow-dev.md
Service: flow
GitHub Login: @bbarath
Microsoft Alias: barathb

@parthpnp Thanks for using Microsoft Flow. I've fixed this issue.


Can I PayPal a Donation?

The proxy is killer good and your support worthy of praise. I'd rather not give my personal data and donate via GitHub. Is there a way I can donate by sending money via PayPal? Thanks

Thanks for the kind words and offer - I typically use the sponsors feature here for ease, but you can also use my GitHub username @gmail.com for PayPal.

Thanks. Just sent...

Thank you – always great to hear this tool is useful for others.


[UNDERTOW-2211] Fix deny uncovered methods handling

Jiras:
https://issues.redhat.com/browse/UNDERTOW-2188
https://issues.redhat.com/browse/UNDERTOW-2209
https://issues.redhat.com/browse/UNDERTOW-2211

@baranowb I added the comment you suggested, and I also noticed I had added the isDefaultPathSecurityEmpty() as public by mistake, so I fixed that, now it is private.


Version 4.0 progress?

I renamed most recent "types.dat" to "structdb.dat" to test it in DisUnity 3.4, but of course got all kind of errors.
is there a way to use the newer github files, to work with DisUnity 3.4? I'm no coder, so I'm checking daily for V4.0 release,
Thanks for your skills ata4.

I just want Unity4.6 extracted text file, hoping to get the new version :)


Fixed ${PREFIX} in Makefile

I made a mistake in the previous pull request; now this is a correction to that.

@solusipse please look at this pull request. Thank you in advance.

Hello. I'm very sorry, but I had to rewrite the whole code base. This means that you have to adjust your code to the new version if you still want to contribute. Feel free to open new PR if you decide to do that. Thank you and sorry again.


Adapt console window to the screen

Summary
The console window will be resized to the screen dimensions - 200px.
PR Checklist

Is this a multi-tenancy feature/bug?

[ ] Yes, the relevant RBAC changes are at:

Do we need to backport changes to the old Rancher UI, such as RKE1?

[ ] Yes, the relevant PR is at:

Are backend engineers aware of UI changes?

[ ] Yes, the backend owner is:

Related Issue  https://github.com/harvester/harvester/issues/2467

Occurred changes and/or fixed issues

Technical notes summary

Areas or cases that should be tested

Areas which could experience regressions

Screenshot/Video

@mergify backport release-harvester-v1.2 release-harvester-v1.3


BGE00177_S2M_cox1

🤖 - Hi! This is an automated message from the barcode validation robot. I'm going to validate the FASTA files in your request. This takes less than two minutes per sequence (about two hours per plate). Subscribe to this thread to get updates. You can safely close this tab.

🤖 - Validation complete. If all looks good, notify @rvosa to merge.

🤖 - Hi! This is an automated message from the barcode validation robot. I'm going to validate the FASTA files in your request. This takes less than two minutes per sequence (about two hours per plate). Subscribe to this thread to get updates. You can safely close this tab.

🤖 - Hi! This is an automated message from the barcode validation robot. I'm going to validate the FASTA files in your request. This takes less than two minutes per sequence (about two hours per plate). Subscribe to this thread to get updates. You can safely close this tab.

Validation Results for data/BGE00177_S2M_cox1.fasta

 ✅ Process ID: BGENL1665-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Populicerus nitidissimus (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1696-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Selenocephalus corsicus (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 656
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1693-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Opsius cypriacus (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 654
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1680-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Aglena ornata (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1539

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1694-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Opsius scutellaris (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 656
Full sequence length: 1374

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 2
Messages:

🥇🌟 BIN compliant, perfect
🥈 Good full length, no ambiguities

 ❗ Process ID: BGENL1694-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Opsius scutellaris (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Coreidae
Cicadellidae
Staphylinidae
Buprestidae
Cimbicidae

❗ Sequence length

Net length aligned to marker region: 113
Full sequence length: 198

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 7
Full rank: 5
Messages:

⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length

 ❗ Process ID: BGENL1694-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Opsius scutellaris (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae
Staphylinidae
Buprestidae
Chironomidae

❗ Sequence length

Net length aligned to marker region: 64
Full sequence length: 123

❗ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 2

Rankings:

Barcode rank: 7
Full rank: 5
Messages:

⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length

 ✅ Process ID: BGENL1619-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Zygina angusta (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 656
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ❗ Process ID: BGENL1621-24

File: data/BGE00177_S2M_cox1.fasta

✅ No errors

❗ Taxonomic check

Expected species as registered at BOLD: Cixius simplex (species)
Expected family as registered at BOLD: Cixiidae (family)
Observed BLAST hits at family level:

❗ Sequence length

Net length aligned to marker region: 97
Full sequence length: 174

❗ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 2

Rankings:

Barcode rank: 7
Full rank: 5
Messages:

⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length

 ✅ Process ID: BGENL1632-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Tremulicerus tremulae (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 656
Full sequence length: 1386

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 2
Messages:

🥇🌟 BIN compliant, perfect
🥈 Good full length, no ambiguities

 ✅ Process ID: BGENL1627-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Paraliburnia clypealis (species)
Expected family as registered at BOLD: Delphacidae (family)
Observed BLAST hits at family level:

Delphacidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1539

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1686-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Araldus propinquus (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 656
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1685-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Paragygrus rotundiceps (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 577
Full sequence length: 1395

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 2
Full rank: 2
Messages:

🥇 BIN compliant
🥈 Good full length, no ambiguities

 ✅ Process ID: BGENL1639-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Craspedolepta innoxia (species)
Expected family as registered at BOLD: Aphalaridae (family)
Observed BLAST hits at family level:

Triozidae
Carsidaridae
Aphalaridae
Liviidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1530

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1692-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Xestocephalus freyi (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cercopidae
Cicadellidae

✅ Sequence length

Net length aligned to marker region: 656
Full sequence length: 1539

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ❗ Process ID: BGENL1649-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Brachycoleus pilicornis (species)
Expected family as registered at BOLD: Miridae (family)
Observed BLAST hits at family level:

Mesoveliidae
Corixidae
Miridae
Anthocoridae
Aradidae
Staphylinidae

❗ Sequence length

Net length aligned to marker region: 97
Full sequence length: 201

❗ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 1

Rankings:

Barcode rank: 7
Full rank: 5
Messages:

⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length

 ✅ Process ID: BGENL1684-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Paraglena paludosa (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1296

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 2
Messages:

🥇🌟 BIN compliant, perfect
🥈 Good full length, no ambiguities

 ❗ Process ID: BGENL1684-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Paraglena paludosa (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Veliidae
Reduviidae
Cicadellidae
Curculionidae

❗ Sequence length

Net length aligned to marker region: 107
Full sequence length: 267

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 7
Full rank: 5
Messages:

⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length

 ✅ Process ID: BGENL1635-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Zygina suavis (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 656
Full sequence length: 1509

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1676-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Doratulina acuticeps (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1633-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Metidiocerus poecilus (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 635
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 2
Full rank: 1
Messages:

🥇 BIN compliant
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1622-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Cixius dubius (species)
Expected family as registered at BOLD: Cixiidae (family)
Observed BLAST hits at family level:

Cixiidae

✅ Sequence length

Net length aligned to marker region: 655
Full sequence length: 1569

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1664-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Assiuta salina (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1663-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Austroagallia hilaris (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 656
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ❗ Process ID: BGENL1705-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Laburrus quadratus (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

❗ Sequence length

Net length aligned to marker region: 203
Full sequence length: 1020

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 7
Full rank: 2
Messages:

⚠ Useful marker sequence
‼ Not BIN compliant
🥈 Good full length, no ambiguities

 ❗ Process ID: BGENL1705-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Laburrus quadratus (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

❗ Sequence length

Net length aligned to marker region: 313
Full sequence length: 360

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 6
Full rank: 5
Messages:

⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length

 ❗ Process ID: BGENL1656-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Calligypona reyi (species)
Expected family as registered at BOLD: Delphacidae (family)
Observed BLAST hits at family level:

Delphacidae

❗ Sequence length

Net length aligned to marker region: 127
Full sequence length: 471

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 7
Full rank: 5
Messages:

⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length

 ✅ Process ID: BGENL1661-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Neophilaenus modestus (species)
Expected family as registered at BOLD: Aphrophoridae (family)
Observed BLAST hits at family level:

Cercopidae
Aphrophoridae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1539

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1636-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Delphax pulchellus (species)
Expected family as registered at BOLD: Delphacidae (family)
Observed BLAST hits at family level:

Delphacidae

✅ Sequence length

Net length aligned to marker region: 654
Full sequence length: 1539

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1641-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Aphalara exilis (species)
Expected family as registered at BOLD: Aphalaridae (family)
Observed BLAST hits at family level:

Triozidae
Carsidaridae
Aphalaridae
Liviidae

✅ Sequence length

Net length aligned to marker region: 655
Full sequence length: 1530

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1626-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Paraliburnia adela (species)
Expected family as registered at BOLD: Delphacidae (family)
Observed BLAST hits at family level:

Delphacidae

✅ Sequence length

Net length aligned to marker region: 654
Full sequence length: 1539

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1671-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Euscelis (genus)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1667-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Tremulicerus vitreus (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 655
Full sequence length: 1543

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ❗ Process ID: BGENL1630-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Cacopsylla visci (species)
Expected family as registered at BOLD: Psyllidae (family)
Observed BLAST hits at family level:

Psyllidae

❗ Sequence length

Net length aligned to marker region: 131
Full sequence length: 165

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 7
Full rank: 5
Messages:

⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length

 ✅ Process ID: BGENL1630-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Cacopsylla visci (species)
Expected family as registered at BOLD: Psyllidae (family)
Observed BLAST hits at family level:

Psyllidae

✅ Sequence length

Net length aligned to marker region: 558
Full sequence length: 864

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 2
Full rank: 5
Messages:

🥇 BIN compliant
🥉 Acceptable full length

 ❗ Process ID: BGENL1698-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Amblytelinus insularis (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

❗ Sequence length

Net length aligned to marker region: 167
Full sequence length: 984

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 7
Full rank: 5
Messages:

⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length

 ❗ Process ID: BGENL1698-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
❗ Taxonomic check

Expected species as registered at BOLD: Amblytelinus insularis (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Culicidae
Limoniidae
Lonchopteridae
Drosophilidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 705

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 5
Messages:

🥇🌟 BIN compliant, perfect
🥉 Acceptable full length

 ✅ Process ID: BGENL1624-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Kelisia guttula (species)
Expected family as registered at BOLD: Delphacidae (family)
Observed BLAST hits at family level:

Alydidae
Delphacidae

✅ Sequence length

Net length aligned to marker region: 656
Full sequence length: 1539

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1673-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Fieberiella ida (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 656
Full sequence length: 1539

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1658-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Neophilaenus angustipennis (species)
Expected family as registered at BOLD: Aphrophoridae (family)
Observed BLAST hits at family level:

Cercopidae
Aphrophoridae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1539

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ❗ Process ID: BGENL1640-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Craspedolepta artemisiae (species)
Expected family as registered at BOLD: Aphalaridae (family)
Observed BLAST hits at family level:

Triozidae
Phacopteronidae
Carsidaridae
Aphalaridae
Liviidae

❗ Sequence length

Net length aligned to marker region: 280
Full sequence length: 1092

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 7
Full rank: 2
Messages:

⚠ Useful marker sequence
‼ Not BIN compliant
🥈 Good full length, no ambiguities

 ✅ Process ID: BGENL1702-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Thamnotettix exemtus (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1617-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Ribautiana tenerrima (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1515

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1669-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Chloropelix canariensis (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 656
Full sequence length: 1062

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 2
Messages:

🥇🌟 BIN compliant, perfect
🥈 Good full length, no ambiguities

 ❗ Process ID: BGENL1655-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Salda morio (species)
Expected family as registered at BOLD: Saldidae (family)
Observed BLAST hits at family level:

Saldidae

❗ Sequence length

Net length aligned to marker region: 211
Full sequence length: 255

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 7
Full rank: 5
Messages:

⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length

 ✅ Process ID: BGENL1687-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Canariotettix brachypterus (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 656
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1691-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Planaphrodes trifasciatus (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 656
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1678-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Selenocephalus nervosus (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 656
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1657-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Neophilaenus albipennis (species)
Expected family as registered at BOLD: Aphrophoridae (family)
Observed BLAST hits at family level:

Cercopidae
Aphrophoridae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1539

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1660-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Neophilaenus longiceps (species)
Expected family as registered at BOLD: Aphrophoridae (family)
Observed BLAST hits at family level:

Cercopidae
Aphrophoridae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1539

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1628-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Megamelodes lequesnei (species)
Expected family as registered at BOLD: Delphacidae (family)
Observed BLAST hits at family level:

Delphacidae

✅ Sequence length

Net length aligned to marker region: 654
Full sequence length: 1539

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ❗ Process ID: BGENL1682-24

File: data/BGE00177_S2M_cox1.fasta

✅ No errors

❗ Taxonomic check

Expected species as registered at BOLD: Brachypterona viridissima (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

❗ Sequence length

Net length aligned to marker region: 1
Full sequence length: 87

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 7
Full rank: 5
Messages:

⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length

 ❗ Process ID: BGENL1682-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Brachypterona viridissima (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Veliidae
Mesoveliidae
Tingidae
Cymidae
Cicadellidae

❗ Sequence length

Net length aligned to marker region: 136
Full sequence length: 285

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 7
Full rank: 5
Messages:

⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length

 ❗ Process ID: BGENL1682-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
❗ Taxonomic check

Expected species as registered at BOLD: Brachypterona viridissima (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Veliidae
Nabidae
Delphacidae
Culicidae

❗ Sequence length

Net length aligned to marker region: 1
Full sequence length: 51

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 7
Full rank: 5
Messages:

⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length

 ✅ Process ID: BGENL1703-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Thamnotettix minoidis (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1677-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Anoplotettix graecus (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ❗ Process ID: BGENL1637-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Ribautodelphax imitans (species)
Expected family as registered at BOLD: Delphacidae (family)
Observed BLAST hits at family level:

Delphacidae

❗ Sequence length

Net length aligned to marker region: 80
Full sequence length: 330

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 7
Full rank: 5
Messages:

⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length

 ✅ Process ID: BGENL1623-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Cixius stigmatus (species)
Expected family as registered at BOLD: Cixiidae (family)
Observed BLAST hits at family level:

Cixiidae

✅ Sequence length

Net length aligned to marker region: 655
Full sequence length: 1443

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 2
Messages:

🥇🌟 BIN compliant, perfect
🥈 Good full length, no ambiguities

 ❗ Process ID: BGENL1623-24

File: data/BGE00177_S2M_cox1.fasta

✅ No errors

❗ Taxonomic check

Expected species as registered at BOLD: Cixius stigmatus (species)
Expected family as registered at BOLD: Cixiidae (family)
Observed BLAST hits at family level:

❗ Sequence length

Net length aligned to marker region: 70
Full sequence length: 150

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 7
Full rank: 5
Messages:

⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length

 ✅ Process ID: BGENL1668-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Viridicerus ustulatus (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 656
Full sequence length: 1543

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1683-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Arocephalus lakonicus (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 655
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1681-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Brachypterona grisea (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1654-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Pygolampis bidentata (species)
Expected family as registered at BOLD: Reduviidae (family)
Observed BLAST hits at family level:

Reduviidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1539

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1662-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Triecphorella geniculata (species)
Expected family as registered at BOLD: Cercopidae (family)
Observed BLAST hits at family level:

Cercopidae
Aphrophoridae

✅ Sequence length

Net length aligned to marker region: 656
Full sequence length: 1539

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1674-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Placotettix gravesteini (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1515

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1634-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Sorhoanus assimilis (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 655
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1646-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Anthocoris pilosus (species)
Expected family as registered at BOLD: Anthocoridae (family)
Observed BLAST hits at family level:

Anthocoridae

✅ Sequence length

Net length aligned to marker region: 643
Full sequence length: 1533

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 2
Full rank: 1
Messages:

🥇 BIN compliant
🥇 Excellent full length, no ambiguities

 ❗ Process ID: BGENL1688-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Goldeus harpago (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

❗ Sequence length

Net length aligned to marker region: 253
Full sequence length: 621

❗ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 1

Rankings:

Barcode rank: 7
Full rank: 5
Messages:

⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length

 ✅ Process ID: BGENL1618-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Zygina tiliae (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 656
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1643-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Cacopsylla moscovita (species)
Expected family as registered at BOLD: Psyllidae (family)
Observed BLAST hits at family level:

Psyllidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1542

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1670-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Paradorydium occidentale (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 656
Full sequence length: 1569

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1651-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Empicoris baerensprungi (species)
Expected family as registered at BOLD: Reduviidae (family)
Observed BLAST hits at family level:

Anthocoridae
Reduviidae
Pentatomidae
Rhyparochromidae

✅ Sequence length

Net length aligned to marker region: 654
Full sequence length: 1539

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1642-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Cacopsylla elegantula (species)
Expected family as registered at BOLD: Psyllidae (family)
Observed BLAST hits at family level:

Psyllidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1539

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ❗ Process ID: BGENL1647-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Anthocoris visci (species)
Expected family as registered at BOLD: Anthocoridae (family)
Observed BLAST hits at family level:

Anthocoridae

✅ Sequence length

Net length aligned to marker region: 509
Full sequence length: 828

❗ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 11

Rankings:

Barcode rank: 2
Full rank: 5
Messages:

🥇 BIN compliant
🥉 Acceptable full length

 ✅ Process ID: BGENL1704-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Handianus flavovarius (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1708-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Jassargus bispinatus (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1700-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Mocydiopsis monticola (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 656
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1629-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Florodelphax leptosoma (species)
Expected family as registered at BOLD: Delphacidae (family)
Observed BLAST hits at family level:

Delphacidae

✅ Sequence length

Net length aligned to marker region: 655
Full sequence length: 1539

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1675-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Docotettix cornutus (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 656
Full sequence length: 1539

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1699-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Mocydia aegea (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1653-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Jalla dumosa (species)
Expected family as registered at BOLD: Pentatomidae (family)
Observed BLAST hits at family level:

Pentatomidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1542

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1710-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Oxytettigella viridinervis (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ❗ Process ID: BGENL1672-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Euscelis ormaderensis (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Pentatomidae
Cicadellidae

❗ Sequence length

Net length aligned to marker region: 143
Full sequence length: 579

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 7
Full rank: 5
Messages:

⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length

 ✅ Process ID: BGENL1616-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Ribautiana scalaris (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 655
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1697-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Rhopalopyx vitripennis (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 656
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1652-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Emblethis duplicatus (species)
Expected family as registered at BOLD: Rhyparochromidae (family)
Observed BLAST hits at family level:

Lygaeidae
Berytidae
Malcidae
Rhyparochromidae
Blissidae

✅ Sequence length

Net length aligned to marker region: 653
Full sequence length: 1515

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1631-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Rhytidodus decimusquartus (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1537

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1645-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Bactericera acutipennis (species)
Expected family as registered at BOLD: Triozidae (family)
Observed BLAST hits at family level:

Psyllidae
Triozidae
Carsidaridae
Liviidae

✅ Sequence length

Net length aligned to marker region: 655
Full sequence length: 1533

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1638-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Jassidaeus lugubris (species)
Expected family as registered at BOLD: Delphacidae (family)
Observed BLAST hits at family level:

Delphacidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1666-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Tremulicerus dimidiatus (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 634
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 2
Full rank: 1
Messages:

🥇 BIN compliant
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1690-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Anaceratagallia glabra (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 656
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1707-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Adarrus exornatus (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 657
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

 ✅ Process ID: BGENL1679-24

File: data/BGE00177_S2M_cox1.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Euscelidius schenckii (species)
Expected family as registered at BOLD: Cicadellidae (family)
Observed BLAST hits at family level:

Cicadellidae

✅ Sequence length

Net length aligned to marker region: 656
Full sequence length: 1536

✅ Sequence quality

Ambiguities in marker region: 0
Ambiguities in full sequence: 0
Stop codons: 0

Rankings:

Barcode rank: 1
Full rank: 1
Messages:

🥇🌟 BIN compliant, perfect
🥇 Excellent full length, no ambiguities

🤖 - Error processing PR 35: Git command failed: git push origin pr-35
Stack trace:
Traceback (most recent call last):
File "/data/rutger.vos/barcode_validator/barcode_validator/daemon.py", line 76, in process_pr
self.post_pr_results(config, pr_number, results)
File "/data/rutger.vos/barcode_validator/barcode_validator/daemon.py", line 227, in post_pr_results
self.gc.run_git_command(['git', 'push', 'origin', f"pr-{pr_number}"], f"Failed to push branch pr-{pr_number}")
File "/data/rutger.vos/barcode_validator/barcode_validator/github.py", line 66, in run_git_command
raise RuntimeError(f"Git command failed: {' '.join(command)}")
RuntimeError: Git command failed: git push origin pr-35


Multiple Groups

I'd like to suggest the ability to have multiple groups. Since all permissions in the current system are deny unless assigned, it also makes inheritance possible and organic. Also, if done correctly, this might even resolve issue #194.
The primary use case I have so far is that I want moderators and admins to be able to talk in one channel (moderator group chat) while also maintaining their own groups (and group chat channel). I've had to set everyone in the moderator group and manually assign names to permissions I'd give admins (or myself as owner) to commands. It is quite tedious. If I could assign admins to the moderator group as well, then this would be far easier to manage.
Because having multiple groups could become quite complex, I think it would be necessary to expand the /setgroup command to a /group command that allows the ability to set, unset, list the groups that a user is in, and list who is in a named group. I also think it would be a good idea to use group/name as the identifier (case insensitive) instead of numbers to resolve what group is what.
Example usage of new /group command:

List groups /group list
Add a username to a group /group <groupId> add <username>  -> /group admin add kevinpeno
Remove a username from a group /group <groupId> remove <username>  -> /group admin remove kevinpeno
List members of a group /group <groupId> members -> /group admin members

I like the idea but I don't think the current group system would work well with this, just because you would run into trouble both uniquely identifying groups (say for command permissions) and also allowing players to create/destroy as required. I'd suggest adding player groups or something; distinct from the current groups in that they are only used for chat and possibly area permissions (so you could have group constructions) and can be dynamically created by players.

I don't see conflict for command permissions, since I talked about them above, specifically that all commands are blacklisted unless specified (though I realize that some are defaulted in the config). For example, exclude defaults for now, I have a moderator group that has /tpto permission and I have an admin group that has /warptome permission. The system should be able to determine, by virtue of allowance, that I have both commands available to me without breaking backwards compatibility (since no one has multiple groups yet). The only exception to this is that the 0+ (plus specifically) breaks since there is no concept of a group greater than another. However, given that is the only break I see so far, the config could be updated by the server on first run to support group "promotions" or you could just call it a BC break.


[SDP-1049] Validate the Distribution account balance before starting a Disbursement

What
Add a extra validation step before transitioning disbursement to the READY status to check whether distribution account holds enough of target asset balance to fulfill any pending payments along with the payments on the target disbursement.
Pending payments from other disbursements are any in the status

PAUSED
READY
PENDING

and exclude those in any terminal statuses SUCCESS, CANCELED and FAILED as we as PAUSED as those payments can remain in that state indefinitely.
Why
[TODO: Why this change is being made. Include any context required to understand the why.]
Known limitations
[TODO or N/A]
Checklist
PR Structure

[x] This PR has a reasonably narrow scope (if not, break it down into smaller PRs).
[x] This PR title and description are clear enough for anyone to review it.
[x] This PR does not mix refactoring changes with feature changes (split into two PRs otherwise).

Thoroughness

[x] This PR adds tests for the new functionality or fixes.
[x] This PR contains the link to the Jira ticket it addresses.

Configs and Secrets

[x] No new CONFIG variables are required -OR- the new required ones were added to the helmchart's values.yaml file.
[x] No new CONFIG variables are required -OR- the new required ones were added to the deployments (pr-preview, dev, demo, prd).
[x] No new SECRETS variables are required -OR- the new required ones were mentioned in the helmchart's values.yaml file.
[x] No new SECRETS variables are required -OR- the new required ones were added to the deployments (pr-preview secrets, dev secrets, demo secrets, prd secrets).

Release

[ ] This is not a breaking change.
[ ] This is ready for production.. If your PR is not ready for production, please consider opening additional complementary PRs using this one as the base. Only merge this into develop or main after it's ready for production!


Update libANGLE

The version of libANGLE the project uses is very old, but it was the last version that would compile with Visual C++ 2017. Now that the target platform is Visual C++ 2019, should be able to update this further.
This is a serious pain to do, and shouldn't have any effect on the application, so it's not a priority by any means. When I have a free weekend with absolutely nothing better to do.

This project will be archived, closing Issue as unresolved.


dsym_zip action should allow zipping of all dsyms, not just the app dsym

Currently if you feed an xcarchive to dsym_zip action it will only pull out the app dsym. With iOS 8 and prevalence of dynamic frameworks there's typically loads of dsyms that need to be included for proper symbolication.
Was curious if this is something that should be a flag all: true or just a default?

Sounds good, the action can be found here if you want to add this functionality :+1:

Probably a all: true would be a good idea as we don't want to break/change existing setups.

@KrauseFx done via the PR, it's an optional and defaults to false.

Thanks for the pull request @robertjpayne! Fastest response time :rocket:


✨[Feature Request]: Tilt image

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
To make the image tilt in the cursor direction
Add ScreenShots

After adding tilt effect

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@varshith257 please assign me this issue.


Add new JSLovers logo in the website

Is your feature request related to a problem? Please describe.
Add new JSLovers logo to the website from here: https://jslovers.com/
Describe the solution you'd like
Add new JSLovers logo to the website
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Can this be assigned to me


Add SMK Raden Umar Said Kudus to lists

@NevanAPH First stage of verification passed, official domain for SMK Raden Umar Said Kudus is smkrus.sch.id as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

Alright, thanks!

But, our student are primarily use email with domain smkradenumarsaidkudus.sch.id. should i also add this to the lists? Thanks.

@NevanAPH Yes, please. If the school needs to have two domains added, please add both of them. Thank you.

Add another domain, thanks for the information!

@NevanAPH Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Support Ansible check mode when calling repmgr cluster show commands

Always run the idempotent repmgr cluster show commands to avoid undefined variables in subsequent steps.

LGTM


Common hooks notation

https://docs.feathersjs.com/hooks/common.html
It seems a notation like remove(fieldName: string, ...fieldNames?: string[]): HookFunc means that you should pass string and then an optional array of strings. This is confusing and should be changed to something more comprehensible.

Isn't this correct TypeScript syntax?

@eddyystop as far as I remember string[] means array of strings according the TypeScript syntax.

I checked TypeScript docs and ...rest: string[] appears to be commonly used.
Please reopen this if its otherwise.


Added error_type and error_class to easily classify worker errors

While there might be other errors we know in advance, these are getting the foundations for further improvement. Get insights by running:
SELECT
  count(*),
  feedback#>>'{error_type}'
FROM
  core_job
WHERE
  created_at > now() - '1 day'::interval and status = 'failed' group by 2

Admin:

Task linked: QF-2654 Classify job errors for monitoring


The test time is more than 11 hours!

Dir sir!
Thanks for your great jobs!
I have ran your test code with the corresponding weights and the mAP is correct on dota1.0/task1 (mAP=80.03).
However, the test time is more than 11 hours with GPU 1080ti.
Do you have any suggestions?

Yeah, It's slow for two reasons:

Large mounts of multi-scale testing samples.
We use rotate_aug for testing which is not well optimized.

hellosir!  I also have this question，i have run the multi-scale test code on DOTAv1.5 , it took more than a day to complete the test，i also run the single-scale code on DOTAv1.5，it also took a lot of time.
I would like to ask what is the specific reason for the slow test, and I have tried to modify the confidence and IOU threshold, but nothing worked.
 I also have this question，i have run the multi-scale test code on DOTAv1.5 , it took more than a day to complete the test，i also run the single-scale code on DOTAv1.5，it also took a lot of time.
I would like to ask what is the specific reason for the slow test, and I have tried to modify the confidence and IOU threshold, but nothing worked.
Do you have any suggestions,  thank you !


Handle no selected ConnectionSecurity

Fixes #1877

This only addresses the symptom, not the root of the problem.
We also really want to avoid offering no transport security as default.

Superseded by #2013


Expired reason iota fix

rebasing https://github.com/allegro/bigcache/pull/181 to versions/v3-prep

Codecov Report

Merging #255 (83cd9cd) into versions/v3-prep (92a824f) will increase coverage by 0.45%.
The diff coverage is n/a.

@@                 Coverage Diff                  @@
##           versions/v3-prep     #255      +/-   ##
====================================================
+ Coverage             86.56%   87.01%   +0.45%
====================================================
  Files                    15       15
  Lines                   640      647       +7
====================================================
+ Hits                    554      563       +9
+ Misses                   71       68       -3
- Partials                 15       16       +1

Impacted Files
Coverage Δ

bigcache.go
98.79% <ø> (ø)

queue/bytes_queue.go
87.82% <0.00%> (-1.07%)
:arrow_down:

shard.go
86.75% <0.00%> (+1.82%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 92a824f...83cd9cd. Read the comment docs.

What exactly does it fix? Can you provide a failing test that is fixed by this change?

@janisz this PR is mainly moving https://github.com/allegro/bigcache/pull/181 to "v3-prep" branch. All the discussion can be found in original PR..
I can certainly add test case for this scenario.

@janisz i already wrote test case back TestBigCache_GetWithInfo and that tests this scenario..
Let me know if you need more testing on top of that.
Also https://github.com/allegro/bigcache/pull/216 adjusted the values for const.
My changes are just adding iota for better code readability and removing the explicit values.

@mxplusb will this make cut for v3 ?


Your flist chatflow gets stuck

When opening your_flist chatflow, the spinner appears and the chatflow is stuck and doesn't proceed to take the user info

The loop to make sure the ssh key was added was within a form and so is checked before the form.ask() is reached and so will remain in this infinite loop and no question will ever be triggered to the user as the questions in a form will be triggered once form.ask() is done.
Fix : remove the form and use single questions that are seperated so that the input for ssh key is not through any form
https://github.com/threefoldtech/jumpscaleX_threebot/commit/3b1f6d4f77483aec845d54e23a24761c8e558d08

For verification purposes:

init threebot identity locally using  j.tools.threebot.init_my_threebot(name=3BOT_NAME,eail=EMAIL)
start threebot server
access admin panel {IP}/admin
Go to solutions --> generic flist
If not installed, install/load package through the admin panel, or with package manager client
Chatflow starts without being stuck

Verrfied
chatflow is started and I could enter the flist.


New profile images

Hello @uzluisf
thank you for adding the images! I will replace the old person.png later on.

No problem, @salomonelli !


Not a combobox?

A combobox is a combination of an input and a select list: You can either choose from the list or enter your own value. Am I missing it, or does this not have that second part?

+1, the name is misleading


Add burn feature

I tried to add burn feature for ERC721A contract. Currently address(0) is occupied for ownership inclusion, so I used address(1) for marking burned address.

@chiru-labs Is there a concern for this change?

Hey, thanks for the PR. We will have a more built out version of the repo soon after which we'll need you to write some tests for this. Stay tuned

Was just looking at this again, and it looks like _safeBurn(uint256) just calls itself

Was just looking at this again, and it looks like _safeBurn(uint256) just calls itself

no @MrMcGoats, as you can see from @AndreiD, it has another function to cover implementation like _safeMint

You should check tokenId+1 and update it accordingly just like transfer or the tokens after tokenId will be burnt as well.
Also using 0x0000...dead for burn address would be more intuitive IMO.

In addition, most of the view functions need to be updated to consider the burnt tokens.

You should check tokenId+1 and update it accordingly just like transfer or the tokens after tokenId will be burnt as well.
Also using 0x0000...dead for burn address would be more intuitive IMO.

This is true. I will add that

In addition, most of the view functions need to be updated to consider the burnt tokens.

I am not sure if there is a view function to check burns in usual ERC721 though. For the backward compatibility, I will pass on this and let frontend handle.

Was just looking at this again, and it looks like _safeBurn(uint256) just calls itself

no @MrMcGoats, as you can see from @AndreiD, it has another function to cover implementation like _safeMint
@hskang9
I'm not seeing any other function defined as _safeMint(uint256) apart from the one on line 331. However, if that exists, I don't see the point in wrapping it with a function that has the exact same name and parameters.

As far as I can tell, this is not done with _safeMint(address,uint256). The only implementation of that function that I can find (line 350) calls _safeMint(address,uint256,bytes)

@MrMcGoats I think you can see it in line 340 for _safeBurn's implementation. Same as _safeMint, _safeBurn impl function has bytes data_ as a parameter just in case of receiver as referred before. Would you mind checking the whole logs of comments?

I think we should close this, cause #61 is more likely to be merged soon.

Thanks for the contribution, closing this since we've merged in burn functionality


Removing PDF Button as PDF is not supported for reference builds

Docs Build status updates of commit 1512fc4:
:clock10: Full build: the average full build time is 28 min(s) 39 sec(s), this is based on the last 462 build(s) for this repository.

Docs Build status updates of commit 1512fc4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 5812df5:
:clock10: Full build: the average full build time is 28 min(s) 40 sec(s), this is based on the last 463 build(s) for this repository.

Docs Build status updates of commit 5812df5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


⚠ Bofrost.lu has degraded performance

In 3b1a299, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1887 ms

Resolved: Bofrost.lu performance has improved in 19c89be after 40 minutes.


crash with avocado trees

so it crashed trying to spawn an avacado tree into the world while i was wandering around at least thats what the log and crash log point to
https://pastebin.com/NScMwzyZ
latest.log

the log was too big to put in a pastebin so i uploaded it straight to github. sorry


[WIP] JSDocs

This adds documentation for the majority of the non-JSX source code. There are three pending areas that need to be documented:

[ ] model/signals
[ ] model/rules
[ ] model/primitives/marks/manipulators

For the latter two, I wasn't entirely sure which JSDoc tag I should be using since both of those extend the Mark prototype. It's not exactly an @interface and using @memberof suggests that they're static members, which they're not.
It might, of course, be a sign that there's no good JSDoc tag to describe that design pattern. So perhaps they need to be refactored and moved into Mark proper? The reason they are where they are now, though, is I felt it better encapsulated functionality (i.e., all rules logic together, and all manipulators logic together rather than spread across different modules).

I've created issue #269 to capture the remaining TODOs; I will rebase and merge this


Manual fails to build from master

Describe the bug
From revision 604b7c139f4d44d9fb0e84d812efdfcf5dda3448 to the current master ( f86bbb218cacd968aecdd1374a42d23262c23d3b) the documentation fails to build
To Reproduce
Steps to reproduce the behavior:

git clone https://github.com/NixOS/nixpkgs
git checkout 604b7c139f4d44d9fb0e84d812efdfcf5dda3448
nixos-rebuild build (I used nixops deploy --build-only because I found out the bug when deploying nixops deployment from master)

Expected behavior
Manual should build.
Screenshots
A build log shall be attached to this issue: failure.log
Additional context
The revisions mentioned earlier were determined using git bisect on the master branch.
Metadata
Please run nix run nixpkgs.nix-info -c nix-info -m and paste the result.
Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:
 - nixos/doc/manual/default.nix

Fixed already, rebase onto the latest revision.

Fix confirmed. Closing.


Heap use after free with async rsa

@pnoltes Do you have an idea where this heap after use comes from?  The tracker should ensure that the service cannot be deregistered till the service tracker remove service callback call is completed. So i am not sure what is going wrong here.

No. The tracker should ensure that the service cannot be deregistered till the service tracker remove service callback call is completed. So i am not sure what is going wrong here.

Issue can be found in 9ea86497fffeb7dd1016393576708360ae8c639b

Issue can be found in 9ea86497fffeb7dd1016393576708360ae8c639b

I believe this has been fixed in celix master by having the bundle activator clear all the registered services in the destructor.


Color aesthetic issue with Julia 0.5-rc4?

Can anyone replicate this error?  I'm using Julia 0.5-rc4, Gadfly 0.4.4, and IJulia 1.3 (note I've used the REPL below for convenience). The error doesn't occur:

if I output to a PNG file
in any case, with Julia 0.5-rc3
in any case, if you leave out the color=id aesthetic from the plot statement.

Are you using the masters for Gadfly and Compose?

I can reproduce this on 0.5-rc4. Shoot.

As far as I'm able to tell, this looks like a bug in Base.

Yes, using masters. Since the error doesn't occur in 0.5-rc3 (image below), it seems that some change has been made in 0.5-rc4, such that a conflict occurs between Gadfly and Base.

Is it related to those #NULL statements  ?

Yeah it probably is related to that. Let me see if I can make a minimal example. Kind of hard to post this to base as an issue until we narrow this down a bit.

This works on RC4
julia> a = Dict(Type, Nullable{Type})
ERROR: MethodError: no method matching Dict{K,V}(::Type{Type}, ::Type{Nullable{Type}})
Closest candidates are:
  Dict{K,V}(::Any) at dict.jl:383
  Dict{K,V}{T}(::Any) at sysimg.jl:53

julia> a = Dict{Type, Nullable{Type}}()
Dict{Type,Nullable{Type}} with 0 entries

julia> a[Int64] = Nullable{Float64}()
Nullable{Float64}()

julia> show(a)
Dict{Type,Nullable{Type}}(Pair{Type,Nullable{Type}}(Int64,#NULL))

The error is pointing to dict.jl:71 which was last touched by @vtjnash between RC3 and RC4. The corresponding Compose code hasn't changed in three years. https://github.com/JuliaLang/julia/commit/256a29627b79690eb5e43bc90ffe78c4efd13005 looks like it made a lot of changes to printing dicts and might be the culprit here.

This might be fixed by https://github.com/JuliaLang/julia/pull/18534, but I don't seem to be able to reproduce right now since I get:
julia> using Gadfly

julia> id = ["a","a","b","b","c"];

julia> p = plot(x=1:5, y=rand(5), color=id, Geom.point); draw(PNG(4inch, 3.3inch), p);
ERROR: UndefVarError: minheight not defined
 in realize_brute_force(::Compose.Table, ::Compose.ParentDrawContext) at /Users/jameson/.julia/v0.6/Compose/src/table.jl:246
 in drawpart(::Compose.Image{Compose.PNGBackend}, ::Compose.Table, ::Compose.IdentityTransform, ::NTuple{4,Float64}, ::Measures.BoundingBox{Tuple{Measures.Length{:mm,Float64},Measures.Length{:mm,Float64}},Tuple{Measures.Length{:mm,Float64},Measures.Length{:mm,Float64}}}) at /Users/jameson/.julia/v0.6/Compose/src/container.jl:472
 in drawpart(::Compose.Image{Compose.PNGBackend}, ::Compose.Context, ::Compose.IdentityTransform, ::NTuple{4,Float64}, ::Measures.BoundingBox{Tuple{Measures.Length{:mm,Float64},Measures.Length{:mm,Float64}},Tuple{Measures.Length{:mm,Float64},Measures.Length{:mm,Float64}}}) at /Users/jameson/.julia/v0.6/Compose/src/container.jl:590 (repeats 2 times)
 in draw(::Compose.Image{Compose.PNGBackend}, ::Compose.Context) at /Users/jameson/.julia/v0.6/Compose/src/container.jl:434
 in draw(::Compose.Image{Compose.PNGBackend}, ::Gadfly.Plot) at /Users/jameson/.julia/v0.6/Gadfly/src/Gadfly.jl:822

@vtjnash That's really weird, must be something that has been changed upstream.

Just updating that my original issue occurs in Julia 0.5.0 release. Gadfly plots with a  color aesthetic don't plot to screen when using a PNG backend (they will plot to file).

Paging @vtjnash again, this is a problem. Thanks for checking

I've been using Julia-0.6-pre.alpha for a while, and this issue has disappeared.  Hope it doesn't reappear in the anticipated 0.6-rc's!

if this is no longer a problem in 0.6 we should close this issue.

Ok by me. Also #936 is a duplicate of this.


Release v2.3.0

This is an auto-generated release PR for version 2.3.0.

Can we wait for #1115 to be merged?

Will recreate after
https://github.com/NASA-AMMOS/aerie-ui/pull/1115
is merged in


Deploy test

Should solve issue of deployment with GA.

Codecov Report

Merging #492 (0614a4e) into devel (57cd2d1) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##            devel     #492   +/-   ##
=======================================
  Coverage   51.32%   51.32%
=======================================
  Files          33       33
  Lines       19293    19293
=======================================
  Hits         9903     9903
  Misses       9390     9390

Impacted Files
Coverage Δ

tofu/version.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 57cd2d1...0614a4e. Read the comment docs.


BUG: playing armature animation does not play child/nested armatures

So this one is weird... used to work "as expected" in dragonbones v2.4.
I attach this simple animation arrow_nested.zip
It contains:

outer_animation (1 keyframe at 0, duration 60 frames )
on the keyframe there is an instance/nested clip that has the "real" animation, with multiple keyframes

Now, "outer_animation" once placed on screen it plays its nested animation, but when i call it's .play() method nothing happens.
It seems that the first time it is played on construction (even without telling it to play) by a call from BaseFactory.buildArmature >> Armature.advanceTime >> Slot._update, and later on i can´t get it to play by playing the parent/main armature...
Any ideas how to solve this use case? Although it is a simplified example, i have some animations that make heavy use of this "feature"/"bug" with v2.4, but would LOVE to update to the latest dragonbones and PIXI.

Hi,
Armature will play child/nested armature animation.
It seems not played in this case, because in the skeleton.json the "rotation"(animation) in "spinning_arrow"(armature) loop is 1, that means the animation only play once. If you want the animation infinite loop, you cound set "loop" to 0.

Thanks for the quick response @akdcl!
I do not want it to loop endlessly, i want it to play every time i call ".play()" on the animation. But this happens only the first time i instantiate the armature (without even calling play) but never again.
Imagine the following use case:
// create my armature...
var armature = dragonBones.PixiFactory.factory.buildArmature("outer_spin");

dragonBones.WorldClock.clock.add(armature);

// at this point, the "spinning_arrow" is already in a playing state,
// but i just want it to add to the stage, without playing the animation yet...
pixiStage.addChild(armature);

// ...i see the animation playing on screen...

// after a while i want it to play "again"...
setTimeout(()=>{armature.play()}, 3000);

// ...but it won´t play

As far i understand

i can´t have an armature instance on screen initially stopped
once i instantiate the armature i can´t make it play its child armatures again, without instantiating a new copy

Correct? Feature or bug?

Just tried out the "DragonBonesDesignPanel" plugin of Flash, and i can confirm the same behavior.

import the zip file to the Panel
the "outer_spin" skeleton should be selected, and it doesn't play
clicking the play button does not play the animation neither
select the "spinning_arrow" skeleton, it starts to play immediately
click as many times as You want on the play button, the animation plays each time
select "outer_spin" again, this time it plays once
clicking the play button does not play the animation again (although the icon changes to "pause")

I hope this helps in explaining/reproducing the bug.

Hi,
You could code like this:
outer_spin.getSlot("layer").childArmature.animation.play("rotation"); // Control child armature animation.

Armature  animation is independent of.
Like this:
hero.animation.play("run");
hero.getSlot("gun").childArmature.animation.play("fire");
hero.getSlot("hair").childArmature.animation.play("flowing");

Thanks again @akdcl.
As You can imagine this use case is oversimplified, not the real one i have to face.

Hence the description "playing armature animation does not play child/nested armatures".
Should i close the issue with "won't fix" or do You consider this as "not-a-bug", maybe hope for the team to look into it?

Hi,
You could play all child armature animation like this.
function playAllAnimation (armature: Armature)
{
    armature.getSlots().forEach((slot: Slot) => {
        let childArmature = slot.childArmature;
        if (childArmature) {
            childArmature.play();
            playAllAnimation(childArmature);
        }
    });
}

armature.play("animationName");
playAllAnimation (armature);

I think the issue is not a bug, because api should be flexible enough to suit the needs.

Another solution,  edit this file in DragonBones Pro:
Edit the "outer_spin"(armature) -> "outer"(animation), add a keyframe on the "layer"(slot) timeline, enable the "play" attributes of the frame, and select an animation name to play. (Make "spinning_arrow" in the frame to play "rotation" animation).

The first alternative (code) is exactly what i would expect from the base library - doing so from outside feels "hackish" (workaround a bug).
armature.play("animationName");
playAllAnimation (armature);

The second solution got my hopes up, but it just gives partial solution. Did what You proposed, edited and exported the data again, now i'm down to 2 fails out of 6.
let anims = [
    { armature: "outer_spin", anim: "outer" },  // PLAYS OK
    { anim: "outer" },  // DOES NOT PLAY
    { armature: "spinning_arrow", anim: "rotation" },  // PLAYS OK
    { anim: "rotation" },  // PLAYS OK
    { armature: "outer_spin", anim: "outer" },  // PLAYS OK
    { anim: "outer" }  // DOES NOT PLAY
]

Consecutive calls on armature.play() (without playAllAnimation) fail to play the nested armatures.
Thanks for the suggestions, will keep looking for alternatives!

For the second solution, i think it is a bug, it will be fixed :)


Fix logger implementation so that it actually works as intended

Currently the logger isn't working as intended. Removed the direct calls to the Python logging module and added the custom logger Rohan built. Does not affect or change any unit tests. With this change the logging files get written as expected.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Same comment here as on #146 for the breaking tests.

@jlmaurer can you rebase.


Something about the support on android.

What is your question?
Could you please support the android or ios,you know that the mobile phones will have more convince than computers when we can't use computer to play it.

Ask every game dev that

there's already an unofficial mobile version of the engine


Version 2.0.1 still failing

Version 2.0.1 still failing

I know. I cant seem to build. It's related to this

finally fixed with cake 0.22.1


Exclude tests from packages

Hey there, the utilities here were moved into huggingface_hub.

Guide here
API Reference Docs here

I can still merge this PR if it helps you, but I would suggest using the above instead of this repo :)

Might make sense to archive this repo @nateraw


transform-property-literals should not transform numbers outside safe range

{
  '306887048457879552': {}
}

becomes
{
<PHONE_NUMBER>57879550: {}
}

note the 0 at the end

this already seems to be fixed, just not released?
https://github.com/babel/babili/commit/c545d0a6b858e64aca5b46af85847985352ba6e2#diff-085799e127967f84d83f6427b98b8a58R16

Seems so. Thanks.


annotation support

adding annotations to the
sql.databases/v1beta2 Galera template
which could be added to the Galera pods created by the operator would be very useful feature. (maybe labels also?)

Have you an example about your needs ? Today, Labels and Annotations are available for the Galera object, and are not copied to pods (and we do not have labels and annotations in pod template) because you should not manage pods but only Galera objects. Today we are missing a client or an api (api is experimented but it is not a clean solution, the design of mysql and Galera is cli oriented) to execute commands on Galera cluster and we have to connect at the beginning to create tables, users and so on. Have you something else in mind ?

Our monitoring solution needs pods to have annotations, in order to export the metrics.
The idea is not to really manage the pods, but to be able to select them based on annotations by other tools/scripts/jobs.
I don't have any use case for labels currently.
We also generate pod usage reports for cost allocations based on annotations and labels (still proof of concept).
Just considering that is 'passing annotations and labels' from Galera object to the pods it manages, it shouldn't really cause any issues I can see, and adds other possibilities.

ok so Annotations and Labels can be implemented in PodTemplate, It means it can be different from Annotations and Labels provided for the Galera Object. I will check that.


Drop illuminate/collections

Pull Request
Related issue
Fixes #184
What does this PR do?

Continues work from #190

I've extracted all necessary methods to a custom Collection class not to break any test.
At least the dropped dependency now won't block other dependencies to update in apps.
PR checklist
Please check if your PR fulfills the following requirements:

[x] Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
[x] Have you read the contributing guidelines?
[x] Have you made sure that the title is accurate and descriptive of the changes?

OMG that's amazing @norkunas 🎉
I'll review it soon!

This message is sent automatically
Thanks again for contributing to Meilisearch :heart:
If you are participating in Hacktoberfest, and you would like to receive some gift from Meilisearch too, please complete this form.


Add support for collapsed stack file format

Example of the format:
foo;bar;baz 7
foo;bar 2
test;fun 3
This is the format supported by some tools like https://github.com/brendangregg/FlameGraph and speedscope.app

Discussed offline, will close.