Storenomorpha
Storenomorpha is a genus of spiders in the family Zodariidae. It was first described in 1884 by Simon. As of 2017, it contains 15 species, all from Asia.[1]
| Storenomorpha | |
|---|---|
Scientific classification  | |
| Kingdom: | Animalia |
| Phylum: | Arthropoda |
| Subphylum: | Chelicerata |
| Class: | Arachnida |
| Order: | Araneae |
| Infraorder: | Araneomorphae |
| Family: | Zodariidae |
| Genus: | Storenomorpha Simon[1] |
| Type species | |
| Storenomorpha comottoi | |
| Species | |
|
15, see text | |
Species
Storenomorpha comprises the following species:[1]
- Storenomorpha abramovi Logunov, 2010
- Storenomorpha anne Jäger, 2007
- Storenomorpha arboccoae Jocqué & Bosmans, 1989
- Storenomorpha comottoi Simon, 1884
- Storenomorpha dejiangensis Jiang, Guo, Yu & Chen, 2016
- Storenomorpha falcata Zhang & Zhu, 2010
- Storenomorpha hainanensis Jin & Chen, 2009
- Storenomorpha joyaus (Tikader, 1970)
- Storenomorpha lushanensis Yu & Chen, 2009
- Storenomorpha nupta Jocqué & Bosmans, 1989
- Storenomorpha paguma Grismado & Ramírez, 2004
- Storenomorpha reinholdae Jocqué & Bosmans, 1989
- Storenomorpha stellmaculata Zhang & Zhu, 2010
- Storenomorpha yizhang Yin & Bao, 2008
- Storenomorpha yunnan Yin & Bao, 2008
gollark: Try NodeOS!
gollark: Or Great Information Transfer.
gollark: Git stands for GIT Is Tremendous.
gollark: The stages of git clone are: Receive a "pack" file of all the objects in the repo database Create an index file for the received pack Check out the head revision (for a non-bare repo, obviously)"Resolving deltas" is the message shown for the second stage, indexing the pack file ("git index-pack").Pack files do not have the actual object IDs in them, only the object content. So to determine what the object IDs are, git has to do a decompress+SHA1 of each object in the pack to produce the object ID, which is then written into the index file.An object in a pack file may be stored as a delta i.e. a sequence of changes to make to some other object. In this case, git needs to retrieve the base object, apply the commands and SHA1 the result. The base object itself might have to be derived by applying a sequence of delta commands. (Even though in the case of a clone, the base object will have been encountered already, there is a limit to how many manufactured objects are cached in memory).In summary, the "resolving deltas" stage involves decompressing and checksumming the entire repo database, which not surprisingly takes quite a long time. Presumably decompressing and calculating SHA1s actually takes more time than applying the delta commands.In the case of a subsequent fetch, the received pack file may contain references (as delta object bases) to other objects that the receiving git is expected to already have. In this case, the receiving git actually rewrites the received pack file to include any such referenced objects, so that any stored pack file is self-sufficient. This might be where the message "resolving deltas" originated.
gollark: UPDATE: this is wrong.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.