Babel error on npm start

These errors are thrown when I run npm start after cloning the repository and executing npm install:
> browserify example/src/app.js -t babelify --extension=.jsx> example/dist/app.js

ReferenceError: [BABEL] /projectDir/react-geosuggest/example/src/app.js: Unknown option: /projectDir/react-geosuggest/.babelrc.presets while parsing file: /projectDir/react-geosuggest/example/src/app.js
    at Logger.error (/projectDir/react-geosuggest/node_modules/babelify/node_modules/babel-core/lib/transformation/file/logger.js:58:11)
    at OptionManager.mergeOptions (/projectDir/react-geosuggest/node_modules/babelify/node_modules/babel-core/lib/transformation/file/options/option-manager.js:126:29)
    at OptionManager.addConfig (/projectDir/react-geosuggest/node_modules/babelify/node_modules/babel-core/lib/transformation/file/options/option-manager.js:107:10)
    at OptionManager.findConfigs (/projectDir/react-geosuggest/node_modules/babelify/node_modules/babel-core/lib/transformation/file/options/option-manager.js:168:35)
    at OptionManager.init (/projectDir/react-geosuggest/node_modules/babelify/node_modules/babel-core/lib/transformation/file/options/option-manager.js:229:12)
    at File.initOptions (/projectDir/react-geosuggest/node_modules/babelify/node_modules/babel-core/lib/transformation/file/index.js:147:75)
    at new File (/projectDir/react-geosuggest/node_modules/babelify/node_modules/babel-core/lib/transformation/file/index.js:137:22)
    at Pipeline.transform (/projectDir/react-geosuggest/node_modules/babelify/node_modules/babel-core/lib/transformation/pipeline.js:164:16)
    at Babelify._flush (/projectDir/react-geosuggest/node_modules/babelify/index.js:28:24)
    at Babelify.<anonymous> (_stream_transform.js:118:12)

npm ERR! Linux 3.13.0-37-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "js:example"
npm ERR! node v5.10.0
npm ERR! npm  v3.8.5
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>js:example: `browserify example/src/app.js -t babelify --extension=.jsx> example/dist/app.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>js:example script 'browserify example/src/app.js -t babelify --extension=.jsx> example/dist/app.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the react-geosuggest package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     browserify example/src/app.js -t babelify --extension=.jsx> example/dist/app.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs react-geosuggest
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls react-geosuggest
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /projectDir/react-geosuggest/npm-debug.log

npm ERR! Linux 3.13.0-37-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "prepare:example"
npm ERR! node v5.10.0
npm ERR! npm  v3.8.5
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>prepare:example: `rm -rf example/dist && mkdir example/dist && npm run copy:assets && npm run js:example && npm run css`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prepare:example script 'rm -rf example/dist && mkdir example/dist && npm run copy:assets && npm run js:example && npm run css'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the react-geosuggest package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     rm -rf example/dist && mkdir example/dist && npm run copy:assets && npm run js:example && npm run css
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs react-geosuggest
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls react-geosuggest
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /projectDir/react-geosuggest/npm-debug.log

npm ERR!  Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>server script 'npm run prepare:example && light-server -s example/dist -p 8000 -w 'src/*.jsx,example/src/*.js # npm run js:example' -w 'src/*.css,example/src/*.css # npm run css # reloadcss' -w 'example/src/*.html # npm run copy:assets # reload''.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the react-geosuggest package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run prepare:example && light-server -s example/dist -p 8000 -w 'src/*.jsx,example/src/*.js # npm run js:example' -w 'src/*.css,example/src/*.css # npm run css # reloadcss' -w 'example/src/*.html # npm run copy:assets # reload'
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs react-geosuggest
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls react-geosuggest
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /projectDir/react-geosuggest/npm-debug.log

npm ERR! Linux 3.13.0-37-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "start"
npm ERR! node v5.10.0
npm ERR! npm  v3.8.5
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: `npm run server`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'npm run server'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the react-geosuggest package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run server
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs react-geosuggest
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls react-geosuggest
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /projectDir/react-geosuggest/npm-debug.log

BTW npm install throws this warnings:
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS>

It works if I remove .babelrc.

Solved by #111. Those babel upgrades…
Thanks for reporting!


Consistent style, docs, classifiers

This library looks neat, and similar to something I'm doing as well. This first PR is just some minor cleanup to remove an unused import, make some of the style more consistent, adding some extra metadata to setup.py, and expanding the docstring for safeeval (also adding a doctest, which can become part of the test suite if you pip install xdoctest and run pytest).
This also adds a __version__ attribute to the package itself, which is fairly standard (although unfortunately not ubiquitious). By adding a bit of logic to setup.py you can also make it such that __version__ is the one source of truth for the version number, so it doesn't have to be changed in two places, but I didn't include that in this PR.

Thank you for PR, accepting it! :-)


BGE chironomid data

🤖 - Hi! This is an automated message from the barcode validation robot. I'm going to validate the FASTA files in your request. Please wait while I process the files. This takes about two minutes per sequence.

Validation Results

 ❗ Process ID: BSNHM1133-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Synorthocladius tripilatus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

❗ Sequence length

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

✅ 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: BSNHM1136-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Smittia brevifurcata (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

❗ Sequence length

Net length aligned to marker region: 470
Full sequence length: 1005

✅ Sequence quality

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

Rankings:

Barcode rank: 5
Full rank: 2
Messages:
⚠ Useful marker sequence
❗ Not BIN compliant
🥈 Good full length, no ambiguities

 ❗ Process ID: BSNHM1147-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta

✅ No errors

❗ Taxonomic check

Expected species as registered at BOLD: Paratrissocladius excerptus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

❗ Sequence length

Net length aligned to marker region: 12
Full sequence length: 60

✅ 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: BSNHM1150-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
❗ Taxonomic check

Expected species as registered at BOLD: Paraphaenocladius cuneatus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chloropidae
Drosophilidae
Muscidae
Calliphoridae
Tachinidae

✅ Sequence length

Net length aligned to marker region: 504
Full sequence length: 1131

✅ 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: BSNHM1153-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
❗ Taxonomic check

Expected species as registered at BOLD: Paracladius inserpens (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Carabidae
Nymphalidae

❗ Sequence length

Net length aligned to marker region: 69
Full sequence length: 339

✅ 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: BSNHM1164-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Metriocnemus adjunctus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

❗ Sequence length

Net length aligned to marker region: 58
Full sequence length: 303

✅ 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: BSNHM1167-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
❗ Taxonomic check

Expected species as registered at BOLD: Heterotrissocladius marcidus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Cerambycidae
Curculionidae
Muscidae

❗ Sequence length

Net length aligned to marker region: 49
Full sequence length: 96

✅ 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: BSNHM1226-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta

✅ No errors

❗ Taxonomic check

Expected species as registered at BOLD: Heleniella ornaticollis (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

❗ Sequence length

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

✅ 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: BSNHM1228-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Gymnometriocnemus subnudus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

❗ Sequence length

Net length aligned to marker region: 424
Full sequence length: 822

❗ Sequence quality

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

Rankings:

Barcode rank: 8
Full rank: 5
Messages:
⛔ Unacceptable marker sequence
🥉 Acceptable full length
❗ Some ambiguities in full sequence

 ❗ Process ID: BSNHM1229-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Gymnometriocnemus brumalis (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

❗ Sequence length

Net length aligned to marker region: 126
Full sequence length: 516

✅ 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: BSNHM1232-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Eukiefferiella hospita (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 549
Full sequence length: 1224

✅ 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: BSNHM1234-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
❗ Taxonomic check

Expected species as registered at BOLD: Cricotopus lygropis (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Crambidae

❗ Sequence length

Net length aligned to marker region: 23
Full sequence length: 36

✅ 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: BSNHM1238-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Cricotopus subcoerulescens (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Culicidae
Chironomidae
Tanyderidae
Drosophilidae
Xylophagaidae

❗ Sequence length

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

❗ Sequence quality

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

Rankings:

Barcode rank: 6
Full rank: 5
Messages:
⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length

 ❗ Process ID: BSNHM1240-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Cricotopus lacuum (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 663
Full sequence length: 1101

❗ Sequence quality

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

Rankings:

Barcode rank: 1
Full rank: 2
Messages:
🥇🌟 BIN compliant, perfect
🥈 Good full length, no ambiguities

 ❗ Process ID: BSNHM1242-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Corynoneura lobata (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Scarabaeidae
Chironomidae
Anthomyiidae

❗ Sequence length

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

✅ 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: BSNHM1244-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Corynoneura innupta (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

❗ Sequence length

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

✅ 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: BSNHM1246-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Corynoneura coronata (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Dytiscidae
Cleridae
Culicidae
Chironomidae

❗ Sequence length

Net length aligned to marker region: 262
Full sequence length: 288

✅ 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: BSNHM1251-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Chaetocladius dentiforceps (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Hydraenidae
Culicidae
Chironomidae
Calliphoridae
Noctuidae

❗ Sequence length

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

✅ 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: BSNHM1259-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Bryophaenocladius femineus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae
Simuliidae

✅ Sequence length

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

✅ Sequence quality

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

Rankings:

Barcode rank: 1
Full rank: 4
Messages:
🥇🌟 BIN compliant, perfect
🥈 Good full length
❗ Some ambiguities in full sequence

 ❗ Process ID: BSNHM1269-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Tanytarsus pallidicornis (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

❗ Sequence length

Net length aligned to marker region: 367
Full sequence length: 804

✅ Sequence quality

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

Rankings:

Barcode rank: 6
Full rank: 5
Messages:
⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length
❗ Some ambiguities in full sequence

 ❗ Process ID: BSNHM1271-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta

✅ No errors

❗ Taxonomic check

Expected species as registered at BOLD: Tanytarsus verralli (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

❗ Sequence length

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

✅ 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: BSNHM1272-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta

✅ No errors

❗ Taxonomic check

Expected species as registered at BOLD: Tanytarsus reflexens (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

❗ Sequence length

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

✅ 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: BSNHM1274-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Chironomus dolens (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Scarabaeidae
Cerambycidae
Culicidae
Chironomidae
Tabanidae
Nepticulidae

❗ Sequence length

Net length aligned to marker region: 372
Full sequence length: 477

❗ Sequence quality

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

Rankings:

Barcode rank: 7
Full rank: 5
Messages:
⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length
❗ Some ambiguities in full sequence

 ❗ Process ID: BSNHM1275-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Chironomus hebescens (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae
Gelechiidae
Bedelliidae
Noctuidae

❗ Sequence length

Net length aligned to marker region: 50
Full sequence length: 288

✅ 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: BSNHM1277-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Cryptochironomus obreptans (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae
Agromyzidae

✅ Sequence length

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

✅ Sequence quality

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

Rankings:

Barcode rank: 2
Full rank: 4
Messages:
🥇 BIN compliant
🥈 Good full length
❗ Some ambiguities in full sequence

 ❗ Process ID: BSNHM1280-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta

✅ No errors

❗ Taxonomic check

Expected species as registered at BOLD: Dicrotendipes futilis (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

❗ Sequence length

Net length aligned to marker region: 125
Full sequence length: 639

✅ Sequence quality

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

Rankings:

Barcode rank: 7
Full rank: 6
Messages:
⚠ Useful marker sequence
‼ Not BIN compliant
⛔ Unacceptable full sequence

 ❗ Process ID: BSNHM1282-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta

✅ No errors

❗ Taxonomic check

Expected species as registered at BOLD: Dicrotendipes pulsus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

❗ Sequence length

Net length aligned to marker region: 24
Full sequence length: 72

✅ 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: BSNHM1283-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta

✅ No errors

❗ Taxonomic check

Expected species as registered at BOLD: Chironomus macani (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

❗ Sequence length

Net length aligned to marker region: 52
Full sequence length: 219

✅ 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: BSNHM1284-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Endochironomus impar (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Carabidae
Silvanidae
Culicidae
Chironomidae
Syrphidae
Tephritidae
Sarcophagidae

✅ Sequence length

Net length aligned to marker region: 512
Full sequence length: 612

❗ Sequence quality

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

Rankings:

Barcode rank: 2
Full rank: 5
Messages:
🥇 BIN compliant
🥉 Acceptable full length

 ❗ Process ID: BSNHM1285-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta

✅ No errors

❗ Taxonomic check

Expected species as registered at BOLD: Endochironomus involitans (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

❗ Sequence length

Net length aligned to marker region: 55
Full sequence length: 171

✅ Sequence quality

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

Rankings:

Barcode rank: 7
Full rank: 5
Messages:
⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length
❗ Some ambiguities in full sequence

 ❗ Process ID: BSNHM1286-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta

✅ No errors

❗ Taxonomic check

Expected species as registered at BOLD: Endochironomus trichopus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

❗ Sequence length

Net length aligned to marker region: 10
Full sequence length: 30

✅ 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: BSNHM1292-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Microtendipes diffinis (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

❗ Sequence length

Net length aligned to marker region: 452
Full sequence length: 549

✅ Sequence quality

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

Rankings:

Barcode rank: 5
Full rank: 5
Messages:
⚠ Useful marker sequence
❗ Not BIN compliant
🥉 Acceptable full length

 ❗ Process ID: BSNHM1298-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta

✅ No errors

❗ Taxonomic check

Expected species as registered at BOLD: Microtendipes separatus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

❗ Sequence length

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

✅ 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: BSNHM1299-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta

✅ No errors

❗ Taxonomic check

Expected species as registered at BOLD: Microtendipes tarsalis (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

❗ Sequence length

Net length aligned to marker region: 29
Full sequence length: 36

✅ 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: BSNHM1305-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Parachironomus irretitus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

❗ Sequence length

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

✅ 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: BSNHM1307-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Parachironomus parilis (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

❗ Sequence length

Net length aligned to marker region: 102
Full sequence length: 309

✅ Sequence quality

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

Rankings:

Barcode rank: 7
Full rank: 5
Messages:
⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length
❗ Some ambiguities in full sequence

 ❗ Process ID: BSNHM1312-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta

✅ No errors

❗ Taxonomic check

Expected species as registered at BOLD: Polypedilum patens (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

❗ Sequence length

Net length aligned to marker region: 23
Full sequence length: 222

✅ 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: BSNHM1314-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Arctopelopia expalpans (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae
Syrphidae
Tachinidae

❗ Sequence length

Net length aligned to marker region: 30
Full sequence length: 144

✅ 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: BSNHM1315-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Conchapelopia intersepta (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Baetidae
Mycetophilidae
Culicidae
Chironomidae

❗ Sequence length

Net length aligned to marker region: 100
Full sequence length: 411

✅ 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: BSNHM1321-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Thienemannimyia fusciceps (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 629
Full sequence length: 1482

✅ Sequence quality

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

Rankings:

Barcode rank: 2
Full rank: 4
Messages:
🥇 BIN compliant
🥈 Good full length
❗ Some ambiguities in full sequence

 ❗ Process ID: BSNHM1324-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Diamesa incallida (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

❗ Sequence length

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

❗ Sequence quality

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

Rankings:

Barcode rank: 7
Full rank: 5
Messages:
⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length
❗ Some ambiguities in full sequence

 ❗ Process ID: BSNHM1325-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Diamesa nexilis (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Carabidae
Gyrinidae
Staphylinidae
Hydraenidae
Buprestidae
Chironomidae
Lauxaniidae

❗ Sequence length

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

✅ 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: BSNHM1326-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
❗ Taxonomic check

Expected species as registered at BOLD: Diamesa pergens (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Oecophoridae
Tortricidae

❗ Sequence length

Net length aligned to marker region: 47
Full sequence length: 117

✅ Sequence quality

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

Rankings:

Barcode rank: 7
Full rank: 5
Messages:
⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length
❗ Some ambiguities in full sequence

 ❗ Process ID: BSNHM1327-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta

✅ No errors

❗ Taxonomic check

Expected species as registered at BOLD: Diamesa pertracta (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

❗ Sequence length

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

✅ Sequence quality

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

Rankings:

Barcode rank: 7
Full rank: 5
Messages:
⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length
❗ Some ambiguities in full sequence

 ❗ Process ID: BSNHM1330-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Potthastia inscendens (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Leiodidae
Mycetophilidae
Chironomidae
Boreidae
Oecophoridae

❗ Sequence length

Net length aligned to marker region: 46
Full sequence length: 291

✅ 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: BSNHM1335-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta

✅ No errors

❗ Taxonomic check

Expected species as registered at BOLD: Pseudokiefferiella parva (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

❗ Sequence length

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

✅ 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: BSNHM1336-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Parochlus peregrinus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

❗ Sequence length

Net length aligned to marker region: 91
Full sequence length: 228

❗ Sequence quality

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

Rankings:

Barcode rank: 7
Full rank: 5
Messages:
⚠ Useful marker sequence
‼ Not BIN compliant
🥉 Acceptable full length
❗ Some ambiguities in full sequence

 ❗ Process ID: BSNHM1338-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Prodiamesa obdita (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Buprestidae
Culicidae
Chironomidae
Noctuidae

❗ Sequence length

Net length aligned to marker region: 49
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: BSNHM1339-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
❗ Taxonomic check

Expected species as registered at BOLD: Prodiamesa perpessa (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Dytiscidae
Carabidae
Curculionidae
Erebidae

❗ Sequence length

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

✅ 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: BSNHM1342-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Protanypus caudatus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Culicidae
Chironomidae

✅ Sequence length

Net length aligned to marker region: 522
Full sequence length: 1290

✅ 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: BSNHM1344-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Zavrelimyia hirtimana (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae
Agromyzidae

❗ Sequence length

Net length aligned to marker region: 134
Full sequence length: 483

❗ 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: BSNHM1345-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
❗ Taxonomic check

Expected species as registered at BOLD: Glyptotendipes viridis (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Gryllidae
Carabidae
Staphylinidae
Culicidae

❗ Sequence length

Net length aligned to marker region: 413
Full sequence length: 882

✅ Sequence quality

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

Rankings:

Barcode rank: 5
Full rank: 5
Messages:
⚠ Useful marker sequence
❗ Not BIN compliant
🥉 Acceptable full length

 ❗ Process ID: BSNHM1349-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
❗ Taxonomic check

Expected species as registered at BOLD: Thienemanniella lutea (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Heptageniidae
Reduviidae
Pediculidae
Drosophilidae
Tephritidae
Gracillariidae
Pieridae
Crambidae

❗ Sequence length

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

✅ 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: BSNHM1350-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta

✅ No errors

❗ Taxonomic check

Expected species as registered at BOLD: Thienemanniella majuscula (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

❗ Sequence length

Net length aligned to marker region: 12
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: BSNHM1353-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta

✅ No errors

❗ Taxonomic check

Expected species as registered at BOLD: Cladotanytarsus mancus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

❗ Sequence length

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

✅ 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: BSNHM1356-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta

✅ No errors

❗ Taxonomic check

Expected species as registered at BOLD: Micropsectra aristata (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

❗ Sequence length

Net length aligned to marker region: 4
Full sequence length: 39

✅ 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: BSNHM1358-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta

✅ No errors

❗ Taxonomic check

Expected species as registered at BOLD: Micropsectra nacta (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

❗ Sequence length

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

✅ 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: BSNHM1359-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta

✅ No errors

❗ Taxonomic check

Expected species as registered at BOLD: Micropsectra notescens (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

❗ Sequence length

Net length aligned to marker region: 48
Full sequence length: 162

✅ 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: BSNHM1360-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Micropsectra occipiens (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Hymenopodidae
Scarabaeidae
Scirtidae
Cleridae
Chironomidae

❗ Sequence length

Net length aligned to marker region: 47
Full sequence length: 279

✅ 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: BSNHM1361-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
❗ Taxonomic check

Expected species as registered at BOLD: Micropsectra offectus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Heleomyzidae

❗ Sequence length

Net length aligned to marker region: 245
Full sequence length: 528

✅ 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: BSNHM1362-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta

✅ No errors

❗ Taxonomic check

Expected species as registered at BOLD: Paratanytarsus affinis (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

❗ Sequence length

Net length aligned to marker region: 37
Full sequence length: 105

✅ 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: BSNHM1363-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Paratanytarsus bituberculatus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae
Muscidae

✅ Sequence length

Net length aligned to marker region: 588
Full sequence length: 1305

✅ Sequence quality

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

Rankings:

Barcode rank: 2
Full rank: 4
Messages:
🥇 BIN compliant
🥈 Good full length
❗ Some ambiguities in full sequence

 ✅ Process ID: BSNHM1368-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Paratanytarsus perlevis (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae
Muscidae

✅ Sequence length

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

✅ Sequence quality

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

Rankings:

Barcode rank: 2
Full rank: 4
Messages:
🥇 BIN compliant
🥈 Good full length
❗ Some ambiguities in full sequence

 ✅ Process ID: BSNHM1369-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Micropsectra chionophila (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae
Drosophilidae

✅ Sequence length

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

✅ Sequence quality

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

Rankings:

Barcode rank: 1
Full rank: 3
Messages:
🥇🌟 BIN compliant, perfect
🥇 Excellent full length
❗ Some ambiguities in full sequence

 ❗ Process ID: BSNHM1372-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
❗ Taxonomic check

Expected species as registered at BOLD: Smittia contingens (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Staphylinidae
Culicidae
Pipunculidae
Tephritidae
Erebidae
Lycaenidae

❗ Sequence length

Net length aligned to marker region: 52
Full sequence length: 216

✅ 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: BSNHM1373-24

File: data/2024-08-26 BGE chironomids NOT UPLOADED to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Cladotanytarsus vanderwulpi (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

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

✅ Sequence quality

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

Rankings:

Barcode rank: 1
Full rank: 3
Messages:
🥇🌟 BIN compliant, perfect
🥇 Excellent full length
❗ Some ambiguities in full sequence

 ❗ Process ID: BSNHM1138-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Rheocricotopus effusus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

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

❗ Sequence quality

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

Rankings:

Barcode rank: 3
Full rank: 3
Messages:
🥈 BIN compliant
❓ Marker may be chimeric
🥇 Excellent full length
❗ Some ambiguities in full sequence

 ✅ Process ID: BSNHM1141-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Pseudosmittia recta (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 656
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: BSNHM1145-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Psectrocladius calcaratus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 657
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: BSNHM1157-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Orthocladius grampianus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 657
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: BSNHM1160-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Metriocnemus paganicus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 657
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: BSNHM1161-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Metriocnemus fertus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 657
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: BSNHM1162-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Metriocnemus deproperans (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 657
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: BSNHM1227-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Halocladius fucicola (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 657
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: BSNHM1235-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Cricotopus laricomalis (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 657
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: BSNHM1241-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Cricotopus biformis (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae
Tipulidae
Drosophilidae

✅ Sequence length

Net length aligned to marker region: 656
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: BSNHM1276-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Chironomus moerens (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 657
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: BSNHM1289-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Glyptotendipes mancunianus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 657
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: BSNHM1290-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Glyptotendipes paripes (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 656
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: BSNHM1301-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Omisus caledonicus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 657
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: BSNHM1320-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Rheopelopia eximia (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Culicidae
Chironomidae
Drosophilidae

✅ Sequence length

Net length aligned to marker region: 657
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: BSNHM1322-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Thienemannimyia northumbrica (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Culicidae
Chironomidae

✅ Sequence length

Net length aligned to marker region: 656
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: BSNHM1323-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Thienemannimyia woodi (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Culicidae
Chironomidae

✅ 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: BSNHM1329-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Potthastia campestris (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 657
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: BSNHM1331-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Potthastia montium (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 657
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: BSNHM1332-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Potthastia pastoris (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 656
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: BSNHM1333-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Potthastia pastoris (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 656
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: BSNHM1334-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Pseudokiefferiella parva (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 657
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: BSNHM1340-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Diamesa gregsoni (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 657
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: BSNHM1341-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Boreoheptagyia cintipes (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 657
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: BSNHM1343-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Thalassomya frauenfeldi (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae
Drosophilidae
Pallopteridae

✅ Sequence length

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

✅ Sequence quality

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

Rankings:

Barcode rank: 1
Full rank: 6
Messages:
🥇🌟 BIN compliant, perfect
⛔ Unacceptable full sequence

 ✅ Process ID: BSNHM1346-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Glyptotendipes foliicola (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 657
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: BSNHM1347-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Chironomus crassiforceps (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 657
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: BSNHM1348-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Graceus ambiguus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 657
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: BSNHM1351-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Thienemanniella vittata (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

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

✅ Sequence quality

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

Rankings:

Barcode rank: 1
Full rank: 6
Messages:
🥇🌟 BIN compliant, perfect
⛔ Unacceptable full sequence

 ❗ Process ID: BSNHM1352-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Tvetenia calvescens (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

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

❗ Sequence quality

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

Rankings:

Barcode rank: 8
Full rank: 6
Messages:
⛔ Unacceptable marker sequence
⛔ Unacceptable full sequence

 ❗ Process ID: BSNHM1354-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Cladotanytarsus modicellus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

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

❗ Sequence quality

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

Rankings:

Barcode rank: 8
Full rank: 6
Messages:
⛔ Unacceptable marker sequence
⛔ Unacceptable full sequence

 ✅ Process ID: BSNHM1355-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Micropsectra apposita (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 656
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: BSNHM1357-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Micropsectra intrudens (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 656
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: BSNHM1364-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Paratanytarsus inopertus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 657
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: BSNHM1365-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Paratanytarsus laccophilus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

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

❗ Sequence quality

Ambiguities in marker region: 36
Ambiguities in full sequence: 258
Stop codons: 1

Rankings:

Barcode rank: 8
Full rank: 6
Messages:
⛔ Unacceptable marker sequence
⛔ Unacceptable full sequence

 ✅ Process ID: BSNHM1366-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Paratanytarsus penicillatus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae
Muscidae

✅ Sequence length

Net length aligned to marker region: 656
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: BSNHM1367-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Paratanytarsus penicillatus (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

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

✅ Sequence quality

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

Rankings:

Barcode rank: 1
Full rank: 6
Messages:
🥇🌟 BIN compliant, perfect
⛔ Unacceptable full sequence

 ✅ Process ID: BSNHM1370-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Micropsectra monticola (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Chironomidae

✅ Sequence length

Net length aligned to marker region: 656
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: BSNHM1371-24

File: data/2024-08-26 BGE chironomids uploaded to BOLD.fasta
✅ No errors
✅ Taxonomic check

Expected species as registered at BOLD: Stempellinella brevis (species)
Expected family as registered at BOLD: Chironomidae (family)
Observed BLAST hits at family level:

Staphylinidae
Chironomidae
Drosophilidae
Tachinidae

✅ Sequence length

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

❗ Sequence quality

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

Rankings:

Barcode rank: 8
Full rank: 6
Messages:
⛔ Unacceptable marker sequence
⛔ Unacceptable full sequence

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


Server timezone configuration

Currently server time zone is configured using double (hours offset). What if the server has a timezone where they switch to winter/summer time? Then the offset will be dynamic, not constant? Maybe timezone configuration should use standard dotnet functionality that can account for such cases?

As you seem to have a clear preconception of the technique and details of what should be done, could you provide details / code / PR of a possible enhancement towards this goal?

Here is an example of using TimeZoneInfo:
TimeZoneInfo easternZone = TimeZoneInfo.FindSystemTimeZoneById("Eastern Standard Time");
DateTime currentEasternTime = TimeZoneInfo.ConvertTimeFromUtc(DateTime.UtcNow, easternZone);

Oh, thanks. So?

As FTP servers report times (such as file creation timestamps) in a way that is undefined in the RFCs, typically though UTC, any timezone logic in FluentFTP is actually just added value - there is no-one stopping you from converting times again yourself in those cases where you know the timezone of the server, i.e. you know the server and its locale.
If you think that there should be additional code in the current timezone logic (which is just there to help a little bit), then be so kind as to provide it and save us some work.
I do also think you might have a valid point to do automatic daylight saving time conversion as it setup for those locations that have that.

This is a good point. We had been using an outdated means of configuring timezones using offsets.
This has been fixed in the latest release: https://www.nuget.org/packages/FluentFTP/52.0.0
Please read: https://github.com/robinrodricks/FluentFTP/wiki/Timezone-Conversion

@yarmoliq I would request you to check the new API and report back if there are any issues.


Question about reference aggregation

Hi, thank you for releasing this package.
I have a question about reference aggregation.
https://github.com/jvamvas/fastChrF/blob/b59c9274014f47c938710082061209bb56b06520/src/lib.rs#L227
In this line, n-grams of a hypothesis are multiplied by num_references, instead of dividing n-grams for all references by num_references (multiplying 1/m) like Equation (6) in the paper https://arxiv.org/pdf/2402.04251.
I understood that this is because the final result is probably the same, and also by not dividing, there is no need to convert the type from u32 to f32, making it easier to utilize the existing function get_match_statistics, is this correct?

Hi @de9uch1, thanks for having a look at the code! :)
Yes, you are right, this is a micro-optimization to avoid having to cast to f32. Mathematically, it's equivalent, so the final result should be exactly the same.

It makes sense.
Thank you so much for your quick reply.


Add API to extend and overload actions

Extend new API to easily override actions:
Run,
File Open
Save, etc...

See also #9514, #8798, #7794.

To make this simpler, the new core plugin will probably create all the menus that handles "global" actions, like the ones described here. I will then add a couple of methods to the plugin api something like
def extend_action(self, action, triggered=None, toggled=None):
    # to add additional behavior when triggered

# and

def overload_action(self, action, triggered=None, toggled=None, condition=None):
    # to add additional behavior when triggered

On the second case need to think about possible conditions, having the overloader plugin be in Focus seems to be the common use case.
@ccordoba12 and @jitseniesen any other cases to take into account?

I would start the design from the user stories: what do we want the user experience to look like?
I am thinking of the notebook plugin, because that is occupying my mind at the moment.
For File > New, perhaps we want a submenu with "New notebook" and "New file" (and perhaps "New project"). This does not seem to fall neatly in your overload / extend cases.
For File > Open, I would expect the file to open in the notebook plugin if it is a notebook file and in the editor otherwise. This also does not seem to fall neatly in your overload / extend cases.
For File > Save, perhaps we want the plugin which has focus to do the save. So this seems an example of an overloadable action as described above, conditioned on focus. How far do we take this, e.g. the variable explorer has a Save action, which the user may not expect to be triggered by File > Save. And what do we do if the plugin with focus can't save?
For File > Save All, I guess we want all plugins to save all files. This is an extendable action as described above.
For Run, this looks like an overloadable action conditioned on focus, but I am not sure whether it would be clear to the user what this does on a notebook. Perhaps we want to change the label to "Run Entire Notebook". Or perhaps we want to overload the entire "Run" menu?
For inspiration, Jupyter Lab uses something called Semantic Menu Items to achieve this.
I do think we want to restrict the actions that can be overloaded / extended, at least initially.

Hi @jitseniesen
Thanks for the feedback.
For the first case you describe that is not really an extension or overload it is just a new action inside a submenu. This is aimed at the other cases you describe.
There should probably be a default action and in case there is no focus we could either use the latest used or use this default.
Will take a look at the jlab thinguie.

I do think we want to restrict the actions that can be overloaded / extended, at least initially.

I agree with this.


tensorflow/example/mutilbox_detector bazel build error

I think there are lots of out of date docs in this repo, for example:
tensorflow/example/mutilbox_detector

this example show build mutilbox_detector using bazel and generate an binary executable file, however I just got bunch of errors:
WARNING: Config values are not defined in any .rc file: opt
ERROR: /Users/jintian/tensorflow/tensorflow/core/BUILD:1279:1: no such target '//tensorflow/tools/git:gen/spec.json': target 'gen/spec.json' not declared in package 'tensorflow/tools/git' defined by /Users/jintian/tensorflow/tensorflow/tools/git/BUILD and referenced by '//tensorflow/core:version_info_gen'.
ERROR: /Users/jintian/tensorflow/tensorflow/core/BUILD:1279:1: no such target '//tensorflow/tools/git:gen/head': target 'gen/head' not declared in package 'tensorflow/tools/git' defined by /Users/jintian/tensorflow/tensorflow/tools/git/BUILD and referenced by '//tensorflow/core:version_info_gen'.
ERROR: /Users/jintian/tensorflow/tensorflow/core/BUILD:1279:1: no such target '//tensorflow/tools/git:gen/branch_ref': target 'gen/branch_ref' not declared in package 'tensorflow/tools/git' defined by /Users/jintian/tensorflow/tensorflow/tools/git/BUILD and referenced by '//tensorflow/core:version_info_gen'.
ERROR: Analysis of target '//tensorflow/examples/multibox_detector:detect_objects' failed; build aborted.
INFO: Elapsed time: 26.050s

Suggest develop team upgrade useless docs and fix those tutorial that makes us confuse and even lead us to the wrong road.....

You may follow the installation instructions on the official site.

Yes, you'll have to run ./configure before building anything.


Change text -> numeric and evaluate is broken

In the Titanic dataset I've changed the name column to "Numeric" instead of "Text". This trains fine, but causes a problem in evaluate tab.

@beccamc I wonder which one is the bug? train without error or evaluate page error?

The error on the evaluate page appears to be wrong. Investigation could prove that the training is incorrect, but this looks like a problem with evaluate. The fact that it is able to generate the code correctly shows this is probably an evaluate problem.

This looks good


AWS Support

I want to start using Fiber to make my ES experiments management workflow easier.
All my compute credits are on AWS so using GCP is not a good alternative 😢
I am ready to work on a PR to make the CLI work with AWS as well,
can someone guide me to the right place to put a new abstraction for the different cloud services?
What functions do I need to change?
Is fiber using some K8s features that are only available on GCP?

Thanks Justin! Fiber should be able to work with AWS. You may need to change these places:

get_default_project() in cli.py, currently it's calling gcloud command to get the default project.
Docker registry: get_docker_registry_image_name() in cli.py

Another thing is persistent storage. I'm using https://github.com/kubernetes/examples/tree/master/staging/volumes/nfs to provision NFS to use as persistent storage. It mentioned AWS but I didn't see an example over there. You might need to tweak it a little bit to make it work.

Thanks for the tips! I’ll try to get something working over the weekend

I've also been experimenting with AWS to see what is the missing part. The good thins is that it seems the only thing missing from the current version of Fiber is that the command line tool needs a way to specify a docker registry. I'm thinking about adding a --docker-registry  argument to fiber command so that  fiber knows where to push the image to. For AWS, it's ECR and for GCP it's GCR. Other than that, everything else seems to work.
And of course, all of these are based on the assumption that kubectl is configured with EKS and is able to connect to the cluster. And also, docker is authenticated with ECR and is able to push images.

Do you want me to work on something specific or wait for you to get something working? It would be good to avoid implementing the same thing in parallel (even if it’s one function)
Is there a branch with the AWS support?

Can you try this branch feature/cloud-providers? I made a quick change to allow fiber command to take a docker registry as an input. You can run something like this:
fiber -d [aws_project_id].dkr.ecr.[aws_regoin].amazonaws.com run python3 your_command

If you don't pass -d as an input, the command will ask what docker registry to use. Give it a try and let me know how that works for you :smiley:

See #6


Remove T.untyped from RBI for Enumerable#inject

Motivation

Fixes #1361
Test plan

See included automated tests.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_M7srf6j2JVIGDP
→ https://go/builds/bui_M7srBOWSIkrf5l

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_M8CnpRcN9orKje
→ https://go/builds/bui_M8CnDQ6tNcSxvY

Going to punt on this for the time being. If you want better type coverage, consider using .reduce instead of .inject, which has already had the RBI improvement landed as of #6087

Stripe's codebase has 2x the usage of inject vs reduce (and thus 2x the number of errors that need to be fixed), and I am tired of doing codemods for the time being.
I agree that it feels weird, and we should probably pick this up again sometime in the future.


Missing "Uninstall" plugin section #1531

Removing Plugins from a Jenkins Installation
The Jenkins Docker documentation provides detailed instructions for adding plugins to a Jenkins controller image. However, it lacks guidance on removing plugins from an existing Jenkins installation, which can be non-intuitive for users unfamiliar with how the image and entrypoint script work. This guide aims to fill that gap with clear, actionable steps.
Steps to Remove a Plugin

Update the plugins.txt or Equivalent jenkins-plugin-cli Call
If you’re using a custom Docker image with a plugins.txt file or jenkins-plugin-cli, start by ensuring the plugin is removed from this configuration. For example:

If your plugins.txt includes the plugin windows-slaves, remove the corresponding line:
diff
Copy code

windows-slaves
Alternatively, if using jenkins-plugin-cli commands, ensure the plugin is excluded from any install-plugin commands in your Dockerfile.

Verify Plugins in the Base Image
Build your custom Docker image and ensure the plugin is no longer present in /usr/share/jenkins/ref/plugins/. Use the following command to diagnose:

bash
Copy code
docker run --rm your-custom-jenkins-image ls -l /usr/share/jenkins/ref/plugins/
If the plugin windows-slaves.jpi is absent, you’ve successfully removed it from the base image.

Check and Remove the Plugin from $JENKINS_HOME
Even after removal from the base image, the plugin may persist in the Jenkins data volume ($JENKINS_HOME/plugins/) because the entrypoint script does not automatically delete plugins. To completely remove the plugin:

Option 1: Remove via the Jenkins UI
Navigate to Manage Jenkins > Manage Plugins, locate the plugin in the Installed tab, and uninstall it. Then, restart Jenkins to apply the changes.
Option 2: Remove Manually from the File System
If you prefer a manual approach, delete the plugin files directly from $JENKINS_HOME/plugins/:
bash
Copy code
docker exec -it jenkins-container bash
rm -rf $JENKINS_HOME/plugins/windows-slaves*
Afterward, restart the Jenkins container:
bash
Copy code
docker restart jenkins-container
4. Validate Plugin Removal
Confirm the plugin has been completely removed by checking both directories:
Ensure it’s not present in the base image’s plugin directory:
bash
Copy code
docker exec -it jenkins-container ls -l /usr/share/jenkins/ref/plugins/
Verify it’s absent from $JENKINS_HOME/plugins/:
bash
Copy code
docker exec -it jenkins-container ls -l $JENKINS_HOME/plugins/
Additionally, inspect the Jenkins UI to confirm the plugin no longer appears under Manage Plugins.
Example: Removing the windows-slaves Plugin
Using the above steps, here’s a practical example for removing the windows-slaves plugin:
Update your plugins.txt file or jenkins-plugin-cli command to exclude windows-slaves.
Rebuild your custom Jenkins Docker image and verify the plugin is not in /usr/share/jenkins/ref/plugins/.
Remove the plugin files from $JENKINS_HOME/plugins/ via the Jenkins UI or manually delete them from the filesystem.
Restart the Jenkins container and confirm the removal.
Key Considerations
Data Persistence: Jenkins stores plugin configurations and data in $JENKINS_HOME. Removing a plugin from the base image does not automatically clean up data from the persistent volume.
Restart Required: Always restart the Jenkins container after removing plugins to ensure changes take effect.
By following these steps, you can confidently remove plugins from your Jenkins installation, maintaining a clean and optimized environment.

Duplicate of #1531
Also, please do not use an LLM to generate content wasting maintainers time. We expect a proper discussion and due diligence in searching existing issues. Additionally, the problem has to be treated on the www.jenkins.io and adding an eventual link in this repository.


k web

I decided to trying this sample to see if I got the same error from running my own application and guess what I did. This error is produced when I run this sample application.
Any idea how to fix this.
An unhandled exception occurred while processing the request.

MissingMethodException: Method not found: 'Microsoft.AspNet.Http.Interfaces.Security.ISignOutContext Microsoft.AspNet.Security.Infrastructure.AuthenticationHandler.get_SignOutContext()'.
Microsoft.AspNet.Security.Cookies.CookieAuthenticationHandler.<ApplyResponseGrantAsync>d__15.MoveNext()

Stack Query Cookies Headers Environment
MissingMethodException: Method not found: 'Microsoft.AspNet.Http.Interfaces.Security.ISignOutContext Microsoft.AspNet.Security.Infrastructure.AuthenticationHandler.get_SignOutContext()'.

Uh, Uh, I can answer this!!!!
Using ASP.NET 5.0 Dev (vNext) Branch
kvm install latest -a default -x86 -r CLR
Determining latest version
KRE-CLR-x<IP_ADDRESS>-beta3-10921 already installed.
Adding G:\tools\.kre\packages\KRE-CLR-x<IP_ADDRESS>-beta3-10921\bin to process PATH
Updating alias 'default' to 'KRE-CLR-x<IP_ADDRESS>-beta3-10921'
Press any key to continue!:

Well, IdentitySample.Mvc project is cloned from the dev branch. So, the project.json is using Microsoft.AspNet.Identity version 3.0.0-*.
{
    "authors": [
        "Microsoft"
    ],
    "description": "Identity sample MVC application on K",
    "version": "1.0.0-*",
    "dependencies": {
        "Microsoft.AspNet.Server.IIS": "1.0.0-*",
        "Microsoft.AspNet.Mvc": "6.0.0-*",
        "Microsoft.AspNet.Server.WebListener": "1.0.0-*",
        "Microsoft.AspNet.Diagnostics": "1.0.0-*",
        "Microsoft.AspNet.Identity": "3.0.0-*",
        "Microsoft.AspNet.Identity.EntityFramework": "3.0.0-*",
        "Microsoft.AspNet.Security.Cookies": "1.0.0-*",
        "Microsoft.AspNet.Security.Facebook": "1.0.0-*",
        "Microsoft.AspNet.Security.Google": "1.0.0-*",
        "Microsoft.AspNet.Security.Twitter": "1.0.0-*",
        "Microsoft.AspNet.StaticFiles": "1.0.0-*",
        "EntityFramework.SqlServer": "7.0.0-*",
        "Microsoft.Framework.ConfigurationModel.Json": "1.0.0-*",
        "Microsoft.Framework.OptionsModel": "1.0.0-*"
    },
    "commands": {
        "web": "Microsoft.AspNet.Hosting --server Microsoft.AspNet.Server.WebListener --server.urls http://localhost:41532",
        "run": "run server.urls=http://localhost:41532"
    },
    "webroot": ".",
    "frameworks": {
        "aspnet50": {
        },
        "aspnetcore50": {
        }
    }
}

I execute the k package manager restore with the following options (Completed successfuly).
PS C:\>kpm restore -s https://www.myget.org/F/aspnetvnext/api/v2 -s https://www.nuget.org/api/v2

Also, the CopyAspNetLoader.cmd script had an error. It should look something like this
echo off

set KPM_HOME=%AppData%\.kpm

REM copy the AspNet.Loader.dll to bin folder
md bin

REM figure out the path of AspNet.Loader.dll
FOR /F %%j IN ('dir /b /o:-d %KPM_HOME%\packages\Microsoft.AspNet.Loader.IIS.Interop\*') do
(SET AspNetLoaderPath=%KPM_HOME%\packages\%%j\tools\AspNet.Loader.dll)
echo Found AspNetLoader.dll at %AspNetLoaderPath%. Copying to bin\
copy %AspNetLoaderPath% bin\

CopyAspNetLoader was written to make it easier to launch iisexpress before any tooling existed.This is not needed anymore with tooling.

That's good to know but back to my original issues. Why the error?
An unhandled exception occurred while processing the request.

MissingMethodException: Method not found: 'Microsoft.AspNet.Http.Interfaces.Security.ISignOutContext Microsoft.AspNet.Security.Infrastructure.AuthenticationHandler.get_SignOutContext()'.
Microsoft.AspNet.Security.Cookies.CookieAuthenticationHandler.<ApplyResponseGrantAsync>d__15.MoveNext()

So you are using beta3 of KRE and restoring packages from vnext feed which is beta4. That might be one possible cause. Can you update your KRE to use beta4 bits and restore packages from https://www.myget.org/F/aspnetrelease/api/v2

Explain this to me. Here's my scenario. The Microsoft.AspNet.Mvc folder contains

Active KRE is beta3.
PS G:\apps> kvm list

Active Version           Runtime Architecture Location               Alias
------ -------           ------- ------------ --------               -----
       1.0.0-beta3-10907 CLR     x86          G:\tools\.kre\packages
       1.0.0-beta3-10914 CLR     x86          G:\tools\.kre\packages
  *    1.0.0-beta3-10921 CLR     x86          G:\tools\.kre\packages default
       1.0.0-rc1-10889   CLR     x86          G:\tools\.kre\packages
       1.0.0-rc1-10894   CLR     x86          G:\tools\.kre\packages

And project.json list dependencies without any reference to beta, rc and anything else. So, should the k web command detect beta3 and use any dependencies with -beta3-?
Cause right now between you and Praburaj, this is becoming more complicated than it needs to be. How does the KRE reference KPM dependencies?

Ok, I removed ALL .\kpm\packages and I did what you asked
$env:KRE_FEED="https://www.myget.org/F/aspnetrelease/api/v2"
kvm install latest -x86 -r CLR
PS G:\apps\aspnet\dev\Identity\samples\IdentitySample.Mvc> sqllocaldb start mssq
llocaldb
LocalDB instance "MSSQLLocalDB" started.
PS G:\apps\aspnet\dev\Identity\samples\IdentitySample.Mvc> sqllocaldb info mssql
localdb
Name:               MSSQLLocalDB
Version:            12.0.2000.8
Shared name:
Owner:              PUBLIC\BLCPublic
Auto-create:        Yes
State:              Running
Last start time:    1/27/2015 12:42:10 PM
Instance pipe name: np:\\.\pipe\LOCALDB#0B57F919\tsql\query
PS G:\apps\aspnet\dev\Identity\samples\IdentitySample.Mvc> k web
Started

kpm restore -s https://www.myget.org/F/aspnetrelease/api/v2 -s https://www.nuget.org/F/api/v2
k web
Now I get the following error
An unhandled exception occurred while processing the request.

InvalidOperationException: Unable to resolve service for type 'Microsoft.Framework.Runtime.ICompilerOptionsProvider' while attempting to activate 'Microsoft.AspNet.Mvc.Razor.RoslynCompilationService'.
Microsoft.Framework.DependencyInjection.ServiceLookup.Service.CreateCallSite(ServiceProvider provider, ISet`1 callSiteChain)

Stack Query Cookies Headers Environment
InvalidOperationException: Unable to resolve service for type 'Microsoft.Framework.Runtime.ICompilerOptionsProvider' while attempting to activate 'Microsoft.AspNet.Mvc.Razor.RoslynCompilationService'.
 This is just some small troubleshooting where my environment is configured incorrectly.

My path is point to what https://www.myget.org/F/aspnetrelease/api/v2 pulled down for KRE.
.kpm was wiped cleaned and configured with https://www.myget.org/F/aspnetrelease/api/v2 and https://www.nuget.org/F/api/v2 as source on the kpm restore command
SQLLocalDB was running before call k web

This appears to be an issue with KRE

BTW. I also cloned the Identity.git using
git clone https://github.com/aspnet/Identity.git --branch release

@kscott5 It was slightly confusing since we moved from rc1 to beta3 hence even though the packages were downloaded for beta3, since there were stale rc1 packages, they were being referenced since they are higher semantically.
Here is what I did. I installed KRE 1.0.0-beta3-10921 from the release MyGet feed. Then cloned Identity repo with branch pointing to release. Then did kpm restore which pulled in packages from release feed. I had no .kpm folder so there are no stale packages. Now I navigated to samples\IdentitySample.Mvc and ran k web. I was able to navigate to the home page.
Also the nuget feed you mentioned should be https://www.nuget.org/api/v2 and not https://www.nuget.org/F/api/v2

We SCORED!!!! I'm using https://www.myget.org/F/aspnetrelease/api/v2. Thank you and Praburaj.

@kscott5 Glad it worked. I'll close this issue. re open if you still hit any problems


commands: Learn 'debuglog'.

Replicates i3 option. Verbosity level given as command line argument
becomes default log level, and using 'debuglog toggle' switches back and
forth between default and debug (or L_ERROR and debug if default is also
L_DEBUG).

Let's take this command out of the man page.

No problem, done. The code works well, but if you want it implemented differently just let me know.

Excellent, thanks for your time!


cannot read property 'bind' of undefined

Often I'm getting these cannot read property 'bind' of undefined messages with absolutely no additional information. I don't know where to look for to fix this. This error message is completely useless. Please improve error messaging.
I'm using RN 0.29.2, but I've seen this in earlier versions too. I'm on Mac, making an iOS app. Here is a screenshot.

I think this error appears when you bind an undefined function, for example in the constructor .
This isn't normal that you don't have any more informations about this error, anyway.
Try to get a clean install of react-native, maybe it should solve the problem that you don't have more information :
rm -rf node_modules && npm i

Hey, we use Github for issues only and all questions should be asked on StackOverflow.
This is for us to keep the number of issues smaller so that we can iterate on React Native versions faster and provide you with the better developer experience.
If you have any ideas on how we could improve the entire process, please share your thoughts on React Native Community group.
PS: Turn on Chrome Debugger and select Stop on uncaught exceptions to see which exact line is causing this exception to happen.