Skip to content

Issues: googleapis/nodejs-bigtable

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clear current search query, filters, and sorts
42 Open 301 Closed
42 Open 301 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Bigtable/ReadRows should silently resume after server or network error: with an error at a random position failed api: bigtable Issues related to the googleapis/nodejs-bigtable API. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
#1536 by flaky-bot bot was closed Dec 5, 2024
1
Cluster Update cluster Updating manual scaling for a cluster: should change cluster to autoscaling failed api: bigtable Issues related to the googleapis/nodejs-bigtable API. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
#1445 by flaky-bot bot was closed Jul 11, 2024
1
Bigtable/ReadRows: should silently resume after server or network error failed api: bigtable Issues related to the googleapis/nodejs-bigtable API. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
#1388 by flaky-bot bot was closed Apr 10, 2024
1
Read Row Format api: bigtable Issues related to the googleapis/nodejs-bigtable API. priority: p3 Desirable enhancement or fix. May not be included in next release. type: question Request for information or clarification. Not an issue.
#1378 by Neofield-Dylan was closed Apr 4, 2024
@danieljbruce
1
Bigtable rows .exists(): "before each" hook for "should check if a row exists" failed api: bigtable Issues related to the googleapis/nodejs-bigtable API. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p3 Desirable enhancement or fix. May not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
#1377 by flaky-bot bot was closed May 29, 2024
@danieljbruce
deletes: "before all" hook for "should delete column from a row" failed api: bigtable Issues related to the googleapis/nodejs-bigtable API. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p3 Desirable enhancement or fix. May not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
#1376 by flaky-bot bot was closed May 29, 2024
@danieljbruce
📦 pack-n-play test: TypeScript code failed api: bigtable Issues related to the googleapis/nodejs-bigtable API. flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
#1359 by flaky-bot bot was closed Nov 2, 2023
3
Bigtable column families: should create a family with nested gc rules failed api: bigtable Issues related to the googleapis/nodejs-bigtable API. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
#1353 by flaky-bot bot was closed Oct 18, 2023
1
Cluster: "after each" hook for "should change nodes for manual scaling" failed api: bigtable Issues related to the googleapis/nodejs-bigtable API. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p3 Desirable enhancement or fix. May not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
#1345 by flaky-bot bot was closed Oct 2, 2023
The build failed api: bigtable Issues related to the googleapis/nodejs-bigtable API. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p3 Desirable enhancement or fix. May not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
#1344 by flaky-bot bot was closed Oct 18, 2023
writes: "before all" hook for "should do a simple write" failed api: bigtable Issues related to the googleapis/nodejs-bigtable API. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p3 Desirable enhancement or fix. May not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
#1343 by flaky-bot bot was closed Oct 18, 2023
reads: "before all" hook for "should read one row" failed api: bigtable Issues related to the googleapis/nodejs-bigtable API. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p3 Desirable enhancement or fix. May not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
#1342 by flaky-bot bot was closed Oct 18, 2023
filters: "after all" hook for "should filter with condition" failed api: bigtable Issues related to the googleapis/nodejs-bigtable API. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p3 Desirable enhancement or fix. May not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
#1341 by flaky-bot bot was closed Oct 18, 2023
1
filters: "before all" hook for "should filter with row sample" failed api: bigtable Issues related to the googleapis/nodejs-bigtable API. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p3 Desirable enhancement or fix. May not be included in next release. samples Issues that are directly related to samples. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
#1340 by flaky-bot bot was closed Oct 18, 2023
deletes: "before all" hook for "should delete column from a row" failed api: bigtable Issues related to the googleapis/nodejs-bigtable API. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p3 Desirable enhancement or fix. May not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
#1339 by flaky-bot bot was closed Oct 18, 2023
Bigtable: "after all" hook in "Bigtable" failed api: bigtable Issues related to the googleapis/nodejs-bigtable API. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p3 Desirable enhancement or fix. May not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
#1338 by flaky-bot bot was closed Oct 18, 2023
1
Bigtable: "before all" hook in "Bigtable" failed api: bigtable Issues related to the googleapis/nodejs-bigtable API. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p3 Desirable enhancement or fix. May not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
#1337 by flaky-bot bot was closed Oct 18, 2023
📦 App Profile 📦 Create a profile: "after all" hook for "should ensure clusters match an updated profile" failed api: bigtable Issues related to the googleapis/nodejs-bigtable API. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p3 Desirable enhancement or fix. May not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
#1328 by flaky-bot bot was closed Mar 4, 2024
@danieljbruce
1
📦 App Profile 📦 Create a profile: "before all" hook for "should create a profile with a single cluster" failed api: bigtable Issues related to the googleapis/nodejs-bigtable API. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p3 Desirable enhancement or fix. May not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
#1327 by flaky-bot bot was closed Oct 18, 2023
Bigtable/ReadRows: should create read stream and read synchronously failed api: bigtable Issues related to the googleapis/nodejs-bigtable API. flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
#1326 by flaky-bot bot was closed Oct 18, 2023
2
📦 pack-n-play test: JavaScript code failed api: bigtable Issues related to the googleapis/nodejs-bigtable API. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
#1299 by flaky-bot bot was closed Aug 10, 2023
1
📦 pack-n-play test: TypeScript code failed api: bigtable Issues related to the googleapis/nodejs-bigtable API. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
#1298 by flaky-bot bot was closed Aug 10, 2023
1
Bigtable/Table close: "after all" hook for "should fail when invoking readRows with closed client" failed api: bigtable Issues related to the googleapis/nodejs-bigtable API. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
#1292 by flaky-bot bot was closed Oct 23, 2023
1
3
Bigtable/Table close: should fail when invoking readRows with closed client failed api: bigtable Issues related to the googleapis/nodejs-bigtable API. flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
#1291 by flaky-bot bot was closed Oct 23, 2023
1
1
readStream.end() called asynchronously returns 16 extra rows before stopping api: bigtable Issues related to the googleapis/nodejs-bigtable API. priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
#1286 by alexander-fenster was closed Aug 17, 2023
2
@danieljbruce
1
ProTip! Type g p on any issue or pull request to go back to the pull request listing page.