map.js triggers assertion when encountering an integer-keyed map with key 0
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Accessibilité débutants
- 35/100
- Type d'issue
- Bug
- Clarté
- Clairement spécifiée
- Activité
- À l'abandon
- Stack technique
- javascript
- Domaine
- backend-api-design
Piste de recherche
Commencez dans js/map.js, à la fonction jspb.Map.deserializeBinary, vers la ligne 507, et reproduisez l’échec avec l’entrée base64 et la définition de PlayerData de l’issue. Comparez le décodage des entrées de la map à clés entières pour les clés 0 et 1. C’est terminé lorsque les données fournies sont désérialisées sans assertion tout en conservant l’entrée de la clé 0.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
Version: 3.12.2
Language: Javascript
Following is a base64 string of bytes that has been coded from C# side. I could immediately decode at C# side just fine, but it failed to decode at JS library.
CiRlZjlhNTJlNC0wZDRmLTQyNzEtOGQzYi02ODZjYWE3N2M4ZWUSClBMQVlFUjc2MTYiCUxZWERQQkFDRkocaEpRQnFhT0t3SmZVbWtyTzF5UjZ5WVBXSWMxM1oCEgBaBggBEgIIAbIBAggBwgEMCIaVuPgFEOjNpLcB
It is coming from this proto definition. Please ignore references to other unknown messages, because the problem is on just field index 11.
message PlayerData {
option (private_message) = true;
reserved 3,5,7,8, 13 to 16;
string player_id = 1;
string display_name = 2;
string short_player_id = 4;
string start_playing = 6;
string firebase_uid = 9;
map<string,MinigameProgress> minigame_progresses = 10;
//Problematic field on JS side
map<int32,CharacterConfiguration> character_configurations = 11;
int32 chilli = 12;
int32 match_count_two_players = 17;
int32 selected_character_configuration = 18;
repeated UnlockedSet unlocked_sets = 19;
repeated PermanentEvent permanent_events = 20;
map<string, google.protobuf.Timestamp> trial_timestamps = 21;
SavedConfigurations saved_configurations = 22;
repeated PurchasableFeatureId purchasable_features = 23;
google.protobuf.Timestamp start_playing_20 = 24;
}
message CharacterConfiguration{
E7.DuelOtters.Core.CharacterKind kind = 1;
string headgear_system_name = 2;
string clothing_system_name = 3;
int32 winning_dance_id = 4;
ColorMutation color_mutation = 5;
EyeMutation eye_mutation = 6;
CheekMutation cheek_mutation = 7;
ClothingKind clothing_kind = 8;
HeadgearKind headgear_kind = 9;
}
This is a ToString of real data coming from C#. Many were default, so it seems they had been efficiently stripped off.
{ "playerId": "ef9a52e4-0d4f-4271-8d3b-686caa77c8ee", "displayName": "PLAYER7616", "shortPlayerId": "LYXDPBACF", "firebaseUid": "hJQBqaOKwJfUmkrO1yR6yYPWIc13", "characterConfigurations": { "0": { }, "1": { "kind": "CharacterKind_Bomberjack" } }, "savedConfigurations": { "autoGameCenter": true }, "startPlaying20": "2020-07-14T19:41:58.384378600Z" }
When trying to deserialize in JS :
const b64 = "CiRlZjlhNTJlNC0wZDRmLTQyNzEtOGQzYi02ODZjYWE3N2M4ZWUSClBMQVlFUjc2MTYiCUxZWERQQkFDRkocaEpRQnFhT0t3SmZVbWtyTzF5UjZ5WVBXSWMxM1oCEgBaBggBEgIIAbIBAggBwgEMCIaVuPgFEOjNpLcB"
const buf = Buffer.from(b64, "base64")
PlayerData.deserializeBinary(buf)
It produces assertion failure :
Error [AssertionError]: Assertion failed
at new goog.asserts.AssertionError (/Users/Sargon/Documents/Unity Projects/Main Projects/DuelOtters/Firebase/functions/node_modules/google-protobuf/google-protobuf.js:81:876)
at Object.goog.asserts.doAssertFailure_ (/Users/Sargon/Documents/Unity Projects/Main Projects/DuelOtters/Firebase/functions/node_modules/google-protobuf/google-protobuf.js:82:257)
at Object.goog.asserts.assert [as assert] (/Users/Sargon/Documents/Unity Projects/Main Projects/DuelOtters/Firebase/functions/node_modules/google-protobuf/google-protobuf.js:83:83)
at Function.jspb.Map.deserializeBinary (/Users/Sargon/Documents/Unity Projects/Main Projects/DuelOtters/Firebase/functions/node_modules/google-protobuf/google-protobuf.js:411:241)
When compared with original source code, this assertion should be line 507 in js/map.js, jspb.Map.deserializeBinary : goog.asserts.assert(key != undefined); The key and value is going to be used in the map.set that follows so two asserts are there.
The problematic part in the data is the field index 11, map<int32,CharacterConfiguration> character_configurations = 11;
It is an int mapped to an another message. In the bytes, it has 2 members, int 0 mapped to an empty message, and int 1 mapped to a message with a bit of string data. Again, this is what they are at C#'s ToString debug :
"characterConfigurations": { "0": { }, "1": { "kind": "CharacterKind_Bomberjack" } }
By simply removing the 0 keyed entry with default message value, and add it back to be keyed with 2 instead :
"characterConfigurations": { "1": { "kind": "CharacterKind_Bomberjack" }, "2": { } }
JS is able to deserialize without triggering the assertion error. It seems like there is something with integer key at number 0. (C# could deserialize 0-keyed map in the protobuf bytes just fine)
- Langage dominant
- JavaScript
- Étoiles
- 471
- Forks
- 91
- Merge moyen
- 3 h 57 min
- PR mergées (30 j)
- 2
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de protocolbuffers/protobuf-javascript
-
Difficulté 5/5 Plus d'une semaine Accessibilité débutants 25/100
-
Difficulté 5/5 Plus d'une semaine Accessibilité débutants 30/100
protocolbuffers/protobuf-javascript#248 · 1 commentaire · 13 réactions ·
-
question
Difficulté 3/5 1-2 jours Accessibilité débutants 45/100
protocolbuffers/protobuf-javascript#222 · 9 commentaires ·
-
Why map.js sort keys? Ouverteenhancement port-fix triaged
Difficulté 4/5 3-5 jours Accessibilité débutants 35/100
protocolbuffers/protobuf-javascript#185 · 1 commentaire ·
-
enhancement port-fix triaged
Difficulté 4/5 3-5 jours Accessibilité débutants 35/100
protocolbuffers/protobuf-javascript#182 · 3 commentaires · 1 réaction ·
Toutes les issues de protocolbuffers/protobuf-javascript
Issues similaires
-
area/install-update comp/cli comp/desktop P3 sweeper:risk-compatibility type/bug
Difficulté 2/5 1-3 heures Accessibilité débutants 86/100
NousResearch/hermes-agent#122386 · 1 commentaire ·
-
Difficulté 2/5 1-3 heures Accessibilité débutants 74/100
-
security
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
IBM/node-sdk-core#373 ·
-
docs web/
Difficulté 2/5 1-3 heures Accessibilité débutants 68/100
-
Difficulté 2/5 1-3 heures Accessibilité débutants 65/100