adobe/aio-lib-state

Issues

• state.get bad performance under cold and warm starts

  #66 opened 2 months ago by shazron
  7

• e2e Docker image is amd64 only

  #149 opened 5 months ago by shazron
  3

• Handle 429s errors

  #58 opened a year ago by moritzraho
  1

• test failures with new joi@17.8.x dependency

  #89 opened a year ago by shazron
  2

• Throws firewall error when using invalid characters for keys

  #86 opened 2 years ago by MichaelGoberling
  0

• optimize using in-memory caching

  #38 opened 2 years ago by moritzraho
  2

• extend strong consistency to the process level instead of instance level

  #30 opened 2 years ago by moritzraho
  4

• Explore reducing probability of hitting rate limit of cosmos metadata

  #77 opened 2 years ago by Himavanth
  2

• StateLibError not defined error when using lib in typescript

  #79 opened 2 years ago by davidbenge
  4

• put doesn't throw validation error if ttl is a number as string

  #73 opened 3 years ago by honstar
  1

• Invalid key name leads to obscure error message

  #67 opened 3 years ago by yesil
  4

• [aio-lib-state] retrieving value via State.get takes more than 60s under load

  #64 opened 3 years ago by honstar
  4

• Large overhead from State initialization during action cold start

  #63 opened 3 years ago by duynguyen
  17

• Correct configuration of bring-your-own cosmosdb account

  #55 opened 3 years ago by duynguyen
  6

• Feature request: add api to query/list keys

  #60 opened 3 years ago by purplecabbage
  3

• Very long init times on cold start

  #61 opened 3 years ago by honstar
  4

• Firewall restrictions are reported as bad credentials

  #40 opened 4 years ago by dominique-pfister
  12

• VSCode intellisense doesn't use the types.d.ts file

  #52 opened 4 years ago by moritzraho
  0

• Abstract StateStore class methods do not need to be `async`

  #48 opened 4 years ago by avoidwork
  5

• Broken auto completion in vscode on instance object

  #25 opened 5 years ago by moritzraho
  2

• Document consistency model

  #26 opened 5 years ago by moritzraho
  0

• An in-range update of @azure/cosmos is breaking the build 🚨

  #19 opened 5 years ago by greenkeeper
  4