CodingTrain / CodingTrain/Live-Poll
No more than one vote?
- Langage dominant
- JavaScript
- Étoiles
- 29
- Forks
- 35
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
Hi there,
I was trying your project on glitch and succesfully created a poll.
But as I try to vote from different browsers and IPs, I see that only one vote is taken in account.
Try it at https://livepoll.glitch.me/vote/6Uy0D8EymKk7ApAY
Did I miss something?
BTW, fsevent is a pain:
```
No Node version was specified; we are using default version 10. You can change this in package.json: https://glitch.happyfox.com/kb/article/59-can-i-change-the-version-of-node-js-my-project-uses/
Initializing node_modules, hold on...
/opt/watcher/app-types/node/install.sh: line 106: ((: <= 12: syntax error: operand expected (error token is "<= 12")
node v10.23.0, npm 6.14.8
Installing...
npm WARN deprecated fsevents@2.1.3: "Please update to latest v2.3 or v2.2"
> live-poll@1.0.0 postinstall /app
> husky install
On branch master
nothing to commit, working directory clean
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.1 (node_modules/nodemon/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
added 111 packages from 117 contributors, removed 49 packages, moved 325 packages and audited 467 packages in 72.124s
37 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
Total install time: 87161ms
```
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Commencez par reproduire le rapport à l’URL du sondage liée en utilisant des navigateurs et des IP distincts, puis suivez le point d’entrée d’enregistrement des votes dans l’application JavaScript/Node.js. Confirmez si le comportement à un seul vote est prévu ; le travail est terminé lorsque le comportement est corrigé ou clairement documenté et couvert par une vérification de régression.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- javascript, node.js
- Domaine
- backend
- Type d'issue
- Bug
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 30/100