profile
viewpoint
Irakli Nadareishvili inadarei @capitalone http://freshblurbs.com Changing fintech for good, one microservice at a time

apiacademy/class-scheduling 20

Support materials for InfoQ articles series

apiacademy/ansible-consul-demo 14

Demo of Consul & Ansible @ AnsibleFest NY, 2015. Accompanying slide deck:

apiacademy/representor 12

Node.js implementation of a serializer for major Hypermedia Formats, in the context of Representor Pattern.

apiacademy/designing-apis-for-the-web 11

code and docs for the O'Reilly video series "Designing APIs for the Web"

inadarei/alpine-jekyll 6

Minimal Jekyll Docker container based on Alpine Linux

apiacademy/ndcoslo2015 5

Sample code for for Mike Amundsen's 2015 NDC Oslo talk on Learning Client Hypermedia

apiacademy/tasks-hypermedia 5

simple hypermedia-style server and client for a "tasks" service

inadarei/alignequals.chocmixin 4

Equal Sign Aligner Mixin for Chocolat Text Editor

apiacademy/rapido-spa 2

Single page frontend app for the Rapido designer

inadarei/alpine-nodejs 2

DEPRECATED. Tiny (50MB) Alpine Linux-based Nodejs Container for Docker

push eventinadarei/nodebootstrap-cli

snyk-bot

commit sha 5e6eb80456ab3df131891fa29a6fa815b6cf2dd6

fix: package.json to reduce vulnerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-MOCHA-561476

view details

push time in 18 hours

push eventinadarei/nodebootstrap

snyk-bot

commit sha 234a58c71e0d67b1a41fca6271f2e8fe56b3deaa

fix: package.json to reduce vulnerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-MOCHA-561476

view details

push time in 2 days

push eventinadarei/nodebootstrap-cli

snyk-bot

commit sha f5a09f580cbc09b9d0b161ab69ef3ba841fe40a3

fix: package.json to reduce vulnerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-MINIMIST-559764

view details

push time in 8 days

push eventinadarei/nodebootstrap

snyk-bot

commit sha 68a314e53bd4db5658e0b4b68bf73027a5779b42

fix: package.json to reduce vulnerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-MINIMIST-559764

view details

push time in 9 days

push eventinadarei/nodebootstrap-cli

snyk-bot

commit sha a4bb2602d83b110516b0a4ae083386e2e9844a26

fix: package.json to reduce vulnerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-YARGSPARSER-560381

view details

push time in 15 days

push eventinadarei/nodebootstrap-microservice

Irakli Nadareishvilii

commit sha a093ad0b3bb03bd708a8d13da0796121faa5fa20

updated dependencies and added validation test

view details

push time in 17 days

push eventinadarei/spieler

Irakli Nadareishvilii

commit sha b472ed28f0462c77bede41849118eb2b388ea8af

updating syntax

view details

push time in 17 days

push eventinadarei/spieler

Irakli Nadareishvilii

commit sha 97ed83fc2238bfde0cc3205ba9c70bd4099e355b

updated dependencies

view details

push time in 17 days

push eventinadarei/kokua

Irakli Nadareishvilii

commit sha 132d7ac8287bc2719f932835a75a896786040bdb

updated dev tools

view details

push time in 17 days

push eventinadarei/kokua

Irakli Nadareishvilii

commit sha c2889c808c86ec4ef23224bd2677bef70682cc08

updated dev tools

view details

push time in 17 days

push eventinadarei/fakepromise

Irakli Nadareishvilii

commit sha e37ac7e434fb522de59cdd6053ae0523dd76ab0d

updated dependencies

view details

push time in 19 days

push eventinadarei/kokua

snyk-bot

commit sha b6036d29d1e274143b9dfdadde06b9ee5df598cc

fix: package.json to reduce vulnerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-ACORN-559469

view details

push time in 22 days

create barnchinadarei/kokua

branch : snyk-fix-a26d019fc1941bdafc7147d614ad97a7

created branch time in 22 days

push eventinadarei/nodebootstrap

snyk-bot

commit sha 96a5e3cba100ea0041b00121bab312c639dfb84a

fix: package.json to reduce vulnerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-ACORN-559469

view details

push time in 23 days

startedaio-libs/aiobotocore

started time in 2 months

issue commentinadarei/rfc-healthcheck

In Details, report threshold

Can you share details on how you implemented failThreshold and passThreshold? How does a client know if "more than" that value is good, or "less than" that value is good?

Thank you

christianhujer

comment created time in 3 months

issue commentinadarei/rfc-healthcheck

Ability to provide HTTP verb for affectedEndpoints

I think the cleanest way would be:

to extend this

"affectedEndpoints" : [
          "/users/{userId}",
          "/customers/{customerId}/status",
          "/shopping/{anything}"
        ],

to this

"affectedEndpoints" : [
          {"/users/{userId}": ["GET", "PUT"]},
          "/customers/{customerId}/status",
          {"/shopping/{anything}": ["PATCH", "POST"}
        ],

where if the element of "afectedEndpoints is a string rather than an object a "GET" is assumed. So "/customers/{customerId}/status" as an element in the array becomes equivalent to {"/customers/{customerId}/status" : ["GET"]

This would make the enhancement backwards-compatible but parsing will be significantly more awkward than if we insisted every element to always be an object. It will probably make parsing very painful for strictly-typed languages. JSON RFC states that it is legal: "There is no requirement that the values in an array be of the same type." but that doesn't mean it is nice to do such things.

I know parsing mixed array will be no problem in JS/Node or Python. I know it will be super annoying but doable in Go. Would love to hear from people who use Java and .Net regularly. I assume it will at the bery least be error-prone.

If we assume that most people will not care for the level of detail of HTTP verbs then for the sake of backwards compatibility having mixed elements makes sense, but parsing implications make me worry about it a lot.

Colin-b

comment created time in 3 months

push eventinadarei/rfc-healthcheck

Irakli Nadareishvilii

commit sha 228bff5f82228d3382f72e4616d8e6a31e4be94e

rebuilt generated spec files

view details

Irakli Nadareishvilii

commit sha 5ed85b85a8745663a3d4ed3e4e6f5704ede5c69d

date

view details

push time in 3 months

push eventinadarei/rfc-healthcheck

Irakli Nadareishvilii

commit sha 4812646159d9d9ca24d8e60a7efe3389841d8d0d

rebuilt generated spec files

view details

Irakli Nadareishvilii

commit sha db5bda5aa3b7d831fbab256f587ef84f9db63324

removed thresholdValue until further discussions

view details

Irakli Nadareishvilii

commit sha ac3320575c556508652f01457514902e98d6f740

removed thresholdValue until further discussions

view details

push time in 3 months

push eventinadarei/rfc-healthcheck

Irakli Nadareishvilii

commit sha aafb062c4a72a5269d8b96a4e9d3410afd5cdf77

formatting fix

view details

push time in 3 months

push eventinadarei/rfc-healthcheck

Irakli Nadareishvilii

commit sha cff1b4310813b2ed93f4ac258bfef19b187a1cec

rebuilt generated spec files

view details

push time in 3 months

issue commentinadarei/rfc-healthcheck

Ability to provide HTTP verb for affectedEndpoints

I have mixed feeling about it. We'll have to discuss how/if it can be implemented in the next version.

Thank you

Colin-b

comment created time in 3 months

issue commentinadarei/rfc-healthcheck

In Details, report threshold

Interesting idea, but I think it should be failRange and passRange otherwise directionality etc. may become a problem and range seems to provide more flexibility, anyway

christianhujer

comment created time in 3 months

issue closedinadarei/rfc-healthcheck

Minor feedback

Hi, nice initiative!

Fwiw, here some minor observations from my experience trying your proposal:

  • There's a typo in section 4 (value eside).
  • When talking about status:
    • 'warn' is mentioned with a MUST and later with a SHOULD.
    • It may be time-saving for the reader to give some specific examples of which HTTP codes could be used in the returns. It could say 207 for 'warn' and 424 for 'fail' maybe? It's an example of course, but saves time having to go an read all http codes.
  • In details, take "cassandra:connections" for example. It may be an overkill to use arrays. I believe if this proposal promotes "hierarchies" of health reports, then "cassandra:connections" should be responsible for aggregating the health of its upstream dependencies. Otherwise it may bring duplication and/or risk inconsistencies, wouldn't it?

Cheers!

closed time in 3 months

taliaga

issue closedinadarei/rfc-healthcheck

"affectedEndpoints" field should be optional

Currently, every other field in the checks object is optional. As there are many types of sub-component that don't have affectedEndpoints, it makes sense to mark this field as optional as well.

closed time in 3 months

smoyer64

issue commentinadarei/rfc-healthcheck

"affectedEndpoints" field should be optional

Correct. This is fixed in the latest.

smoyer64

comment created time in 3 months

push eventinadarei/rfc-healthcheck

Irakli Nadareishvilii

commit sha 59b04d1f4a509c977ec930b831199d73959a8920

fixed alignment

view details

push time in 3 months

PR closed inadarei/rfc-healthcheck

Add Details field thresholdValue.

Adds a detaisl field named "thresholdValue". Fixes #39

+436 -408

1 comment

6 changed files

christianhujer

pr closed time in 3 months

pull request commentinadarei/rfc-healthcheck

Add Details field thresholdValue.

The notion of threshold is interesting but requires more conversation. If we introduce it then is way, then how do you indicate "direction"? I.e. whether problem occurs if we go above or below.

It may be better to introduce an acceptableRange instead, avoiding the problem of directionality and providing more flexibility.

christianhujer

comment created time in 3 months

push eventinadarei/rfc-healthcheck

K. Alex Mills

commit sha 29ecd88b9d48afbd80b12ac7427eea17fc17a692

Close #53 Bring overall style in-line with remaining sections.

view details

K. Alex Mills

commit sha 79d02434b223ce545820c441da9696e0c87a0882

Small typo fix.

view details

Irakli Nadareishvili

commit sha 4aa679242f07467e52a28794fb063ade29cae9d6

Merge pull request #59 from kalexmills/optional-affected-endpoints Optional affectedEndpoints field

view details

push time in 3 months

PR merged inadarei/rfc-healthcheck

Optional affectedEndpoints field

Bring overall style in-line with remaining sections. Closes #53

+3 -2

0 comment

1 changed file

kalexmills

pr closed time in 3 months

issue closedinadarei/rfc-healthcheck

AffectedEndpoints should be optional

The affectedEndpoints section of the specification states:

A typical API has many URI endpoints. Most of the time we are interested in the overall health of the API, without diving into details. That said, sometimes operational and resilience middleware needs to know more details about the health of the API (which is why “checks” property provides details). In such cases, we often need to indicate which particular endpoints are affected by a particular check’s troubles vs. other endpoints that may be fine. The affectedEndpoints property is a JSON array containing URI Templates as defined by [RFC6570].

Each of the other sections starts with <name> (optional) is ... but from the sentence above, it's unclear whether this value is optional or required. The example clearly shows that it's optional and that if the array is empty, the whole field can be omitted. This paragraph should also state that, like the output section that the field should be omitted for “pass” state.

Perhaps the existing paragraph (which describes why the field exists) could be preceded by a paragraph that states what the field is (like the other fields). I'd propose the following text:

affectedEndpoints (optional) contains the URI for unhealthy endpoints. This field SHOULD be omitted for “pass” status.

closed time in 3 months

smoyer64

pull request commentinadarei/rfc-healthcheck

Add python implementation to readme

Thank you

Colin-b

comment created time in 3 months

push eventinadarei/rfc-healthcheck

Colin Bounouar

commit sha 4b899ed480b0a1886b1c9d5173398b1decccb165

Add python implementation to readme This implementation also allows to tweak details and status to handle custom needs depending on the underlying check system. For example it allows to use a specific http error code for warning as Consul only consider a single http code as warning.

view details

Irakli Nadareishvili

commit sha 40aa0912c5a66bebc6fd26b970ff3d6272b78144

Merge pull request #73 from Colin-b/patch-1 Add python implementation to readme

view details

push time in 3 months

PR merged inadarei/rfc-healthcheck

Add python implementation to readme

This implementation also allows to tweak details and status to handle custom needs depending on the underlying check system. For example it allows to use a specific http error code for warning as Consul only consider a single http code as warning.

+2 -1

0 comment

1 changed file

Colin-b

pr closed time in 3 months

PR closed inadarei/nodebootstrap-microservice

[Snyk] Fix for 1 vulnerable dependencies

Description

This PR fixes one or more vulnerable packages in the npm dependencies of this project. See the Snyk test report for more details.

Snyk Project: inadarei/nodebootstrap-microservice:package.json

Snyk Organization: inadarei

Changes included in this PR

  • A Snyk policy (.snyk) file, with updated settings.

Vulnerabilities that will be fixed

With a Snyk patch:

You can read more about Snyk's upgrade and patch logic in Snyk's documentation.

Check the changes in this PR to ensure they won't cause issues with your project.

Stay secure, The Snyk team

Note: You are seeing this because you or someone else with access to this repository has authorised Snyk to open Fix PRs. To review the settings for this Snyk project please go to the project settings page.

+45 -3

0 comment

2 changed files

snyk-bot

pr closed time in 4 months

PR closed inadarei/nodebootstrap-microservice

[Snyk] Fix for 1 vulnerable dependencies

Description

This PR fixes one or more vulnerable packages in the npm dependencies of this project. See the Snyk test report for more details.

Snyk Project: inadarei/nodebootstrap-microservice:package.json

Snyk Organization: inadarei

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • package.json

Vulnerabilities that will be fixed

With an upgrade:

You can read more about Snyk's upgrade and patch logic in Snyk's documentation.

Check the changes in this PR to ensure they won't cause issues with your project.

Stay secure, The Snyk team

Note: You are seeing this because you or someone else with access to this repository has authorised Snyk to open Fix PRs. To review the settings for this Snyk project please go to the project settings page.

+1 -1

0 comment

1 changed file

snyk-bot

pr closed time in 4 months

PR closed inadarei/nodebootstrap-microservice

[Snyk] Fix for 1 vulnerable dependencies

Description

This PR fixes one or more vulnerable packages in the npm dependencies of this project. See the Snyk test report for more details.

Snyk Project: inadarei/nodebootstrap-microservice:package.json

Snyk Organization: inadarei

Changes included in this PR

  • A Snyk policy (.snyk) file, with updated settings.

Vulnerabilities that will be fixed

With a Snyk patch:

You can read more about Snyk's upgrade and patch logic in Snyk's documentation.

Check the changes in this PR to ensure they won't cause issues with your project.

Stay secure, The Snyk team

Note: You are seeing this because you or someone else with access to this repository has authorised Snyk to open Fix PRs. To review the settings for this Snyk project please go to the project settings page.

+15 -3

0 comment

2 changed files

snyk-bot

pr closed time in 4 months

PR closed inadarei/nodebootstrap

fix unary operator, set NB_IS_CONTAINER to 0 unless set in Dockerfile question

gives NB_IS_CONTAINER a default value.

+2 -0

0 comment

1 changed file

vitosans

pr closed time in 4 months

push eventinadarei/rfc-healthcheck

Brian Friesen

commit sha 3b69c38c9fee8768430b247d7a859dae60410b1f

Add .NET implementation to readme

view details

Irakli Nadareishvili

commit sha 3e77f0d480b8837ba5fd1ec2d2df877bf7a2fccd

Merge pull request #72 from bfriesen/rocklib Add .NET implementation to readme

view details

push time in 4 months

PR merged inadarei/rfc-healthcheck

Add .NET implementation to readme

Our .NET implementation of the draft RFC, RockLib.HealthChecks, includes a base package that defines a mechanism for performing health checks in the draft RFC format, along with several satellite packages that make registering health check routes easy.

Also included in our implementation is a response writer package that integrates with Microsoft's health check system. It allows users to take advantage of its existing ecosystem of health checks while writing responses in the draft RFC format.

+1 -0

1 comment

1 changed file

bfriesen

pr closed time in 4 months

pull request commentinadarei/rfc-healthcheck

Add .NET implementation to readme

Fantastic. Thank you!

bfriesen

comment created time in 4 months

fork inadarei/TypeSmart-beta

Chrome extension that automatically formats quotes, apostrophes, dashes, and symbols with their typographically correct characters.

fork in 4 months

issue commentround/TypeSmart-beta

Cursor jumping when typing ½ on Twitter

@round is there a reliable way to reproduce the problem? I have only seen this sporadically and a browser refresh usually fixes it, which makes things hard to debug/test.

mknepprath

comment created time in 4 months

issue commentround/TypeSmart-beta

1 / 3 becomes !53

This is one of the issues described in #4 and is fixed by PR f17d19fd79620d81ba60c19350e081743b6d12db

whale

comment created time in 4 months

issue commentround/TypeSmart-beta

Space bar stops working

I believe this is duplicate of #7 and is fixed by PR f17d19fd79620d81ba60c19350e081743b6d12db

whale

comment created time in 4 months

issue closedround/TypeSmart-beta

What do these regexes do?

Trying to understand what these regexes do and can’t figure it out. When removing them, everything still seems to be working, anyway?

  .replace(new RegExp('(\\s|^|\\(|\\>|\\])(\")(?=[^>\\]]*(<|\\[|$))', 'g'), "$1“")
  .replace(new RegExp("(\\s|^|\\(|\\>|\\])(')(?=[^>\\]]*(<|\\[|$))", 'g'), "$1‘")
  .replace(new RegExp('(.)(\")(?=[^>\\]]*(<|\\[|$))', 'g'), "$1”")
  .replace(new RegExp("(.)(')(?=[^>\\]]*(<|\\[|$))", 'g'), "$1’")

closed time in 4 months

inadarei

issue commentround/TypeSmart-beta

Three minor bugs

Right, and that is what previous PR broke, unintentionally :)

inadarei

comment created time in 4 months

issue commentround/TypeSmart-beta

Problems inserting a new word inside an existing sentence

Fixed by f17d19f

inadarei

comment created time in 5 months

push eventinadarei/TypeSmart-beta

Irakli Nadareishvilii

commit sha f17d19fd79620d81ba60c19350e081743b6d12db

fixing #7 inability to insert word

view details

push time in 5 months

issue openedround/TypeSmart-beta

Problems inserting a new word inside an existing sentence

Describe the bug Because you are forcing “single space everywhere” you are not allowing what is a natural way of inserting a new word in an existing sentence

Expected behavior Stop replacing consecutive spaces with a single one. Benefits are low and downside is – you are creating a major bug.

Screenshots

  • What happens now: http://media.froyo.io/ec25a8e92707
  • What should happen: http://media.froyo.io/1f20161b5ffc

Additional context Need to get rid of this regex .replace(/ +(?= )/g,'');

created time in 5 months

push eventinadarei/TypeSmart-beta

Irakli Nadareishvilii

commit sha e3995482374570c54317de96ca83f8a9b1e9431c

using unicode codes is less fragile than trying to type em dash and en dash out

view details

push time in 5 months

issue openedround/TypeSmart-beta

What do these regexes do?

Trying to understand what these regexes do and can’t figure it out. When removing them, everything still seems to be working, anyway?

  //.replace(new RegExp('(\\s|^|\\(|\\>|\\])(\")(?=[^>\\]]*(<|\\[|$))', 'g'), "$1“")
  //.replace(new RegExp("(\\s|^|\\(|\\>|\\])(')(?=[^>\\]]*(<|\\[|$))", 'g'), "$1‘")
  //.replace(new RegExp('(.)(\")(?=[^>\\]]*(<|\\[|$))', 'g'), "$1”")
  //.replace(new RegExp("(.)(')(?=[^>\\]]*(<|\\[|$))", 'g'), "$1’")

created time in 5 months

issue commentround/TypeSmart-beta

Cursor jumping when typing ½ on Twitter

I have also seen this, on Chrome, but I cannot reliably reproduce it since it doesn’t happen all the time. Most of the time it works on Twitter and on Github, and I have seen this broken on both as well. For a while I thought it was something related to disabling/enabling, but - no.

After refresh (of the page) it usually goes away. ¯_(ツ)_/¯

mknepprath

comment created time in 5 months

PR opened round/TypeSmart-beta

fixing #4

Fixing 2 and a half minor bugs (one isn’t really a bug).

+5 -3

0 comment

1 changed file

pr created time in 5 months

push eventinadarei/TypeSmart-beta

Irakli Nadareishvilii

commit sha 2da39c07d0e441031ae4bb26d1d5dbf28b02f24d

fixing #4

view details

push time in 5 months

fork inadarei/TypeSmart-beta

Chrome extension that automatically formats quotes, apostrophes, dashes, and symbols with their typographically correct characters.

fork in 5 months

issue openedround/TypeSmart-beta

Three minor bugs

Describe the bug Several bugs:

  1. Previous PR broke "_A" and "_C" etc. in its attempt to implement case insensitivity
  2. Typing of "2/2" and "1/3" never worked
  3. Technically it isn't a bug, but HOW DID YOU NOT IMPLEMENT a "shrug" replacement?

Expected behavior The aforementioned three things working well

created time in 5 months

push eventinadarei/TypeSmart-beta

Irakli Nadareishvilii

commit sha 72071cd25ca88d6943fab0b4aab2e537648172a3

fixed 1/3 and 2/3 as well as case insensitivity and added shrug

view details

push time in 5 months

issue openedround/TypeSmart-beta

More contrast for “on” and “off” icons

Describe the bug It’s hard to tell between “on” and “off” states of the icon.

Expected behavior Clear distinction between on and off. E.g. “on” state “T” is bright green, while “off” is what it is now.

Additional context I am truly terrified to share opinions about colors. Don't mean to sound uppity, just really struggling to quickly tell when this thing is on or off.

created time in 5 months

PR opened round/TypeSmart-beta

Fixing bugs and optimizing additional replacements

There are several issues with the "additional replacements" section:

  1. It only replaces first occurrences of these strings, because you are passing a string to .replace() instead of a regex. E.g. if your text contains "1/2" twice, your current code will only replace first one.

  2. Your replacements are not case-sensitive, e.g. you will replace (r) but not (R)

  3. You are using multiple regexes for these simple replacements (one per each) which is wasteful. You can replace these with a single regex, which in my quick tests improved performance by 50-100% depending on the size of the text etc.

This PR fixes those three issues

+83 -62

0 comment

1 changed file

pr created time in 5 months

push eventinadarei/TypeSmart-beta

Irakli Nadareishvili

commit sha 37bdad60c8077954ebbce29727674a316ae468a8

Fixing first-only bug with add replacements, adding case insensitivity and optimizing performance

view details

push time in 5 months

fork inadarei/TypeSmart-beta

Chrome extension that automatically formats quotes, apostrophes, dashes, and symbols with their typographically correct characters.

fork in 5 months

push eventinadarei/kokua

snyk-bot

commit sha 85509eff7360621d697b895948399b6b905e2b36

fix: package.json & .snyk to reduce vulnerabilities The following vulnerabilities are fixed with a Snyk patch: - https://snyk.io/vuln/SNYK-JS-HTTPSPROXYAGENT-469131

view details

push time in 6 months

create barnchinadarei/kokua

branch : snyk-fix-9182841660944edef5b5b5a19d011db4

created branch time in 6 months

more