profile
viewpoint
Dmitry Semenovskiy dsemenovsky Vaultie Inc. Toronto, Canada https://vaultie.io Co-Founder and CEO of @vaultie, blockchain enthusiast, and passionate technologist.

w3c-ccg/lds-merkle-proof-2019 4

A signature suite created in 2019 for doing Merkle Proofs

dsemenovsky/Secp256k1.Ecdh 1

Secp256k1 Nuget package with Ecdh bindings

dsemenovsky/bottender-ws 0

Bottender WebSockets connector to use in pair with web chat widget

dsemenovsky/bottender-ws-chat 0

Chat widget partner to bottender-ws

dsemenovsky/crypto-js 0

JavaScript library of crypto standards.

dsemenovsky/react-bubble-chart 0

A React+D3 animated bubble chart

dsemenovsky/secp256k1_ios 0

secp256k1 C library wrapped in Pod

startedjossmac/react-images

started time in 21 days

startednatamvo/rethinking-atomic-react

started time in 2 months

startedalexander-elgin/atomic-react-redux

started time in 2 months

issue commentipfs/js-ipfs

ipfs-http-client cat operation doesn't expose X-Content-Size header

Noted, will use files.stat to get the file size.

dsemenovsky

comment created time in 2 months

issue openedipfs/js-ipfs

ipfs-http-client cat operation doesn't expose X-Content-Size header

  • Version: ipfs-http-client 44.2.0

  • Platform: Browser/Any

  • Subsystem: CAT

Severity: High

Description:

When using ipfs.cat(ipfsHash, { progress: progressCallback }) there is no way to access response header X-Content-Size to properly track the progress of downloading, this method returns iterable that only produces chunks of data.

Hence, no way of tracking progress properly.

Steps to reproduce the error:

const iterable = ipfs.cat(ipfsHash, { progress: progressCallback })
console.log(iterable) // AsyncGenerator
for await (const chunk of iterable) {
 console.log(chunk) // Chunk of data
}

created time in 2 months

issue commentipfs/go-ipfs

The progress=true option breaks upload via an Nginx reverse proxy

By the way, I am using Nginx 1.16 if that helps.

IPFS is v0.5.1 same as yours.

— Dmitry Semenovsky +1 (416) 455-0212

On Jun 15, 2020, at 10:20 AM, Jakub notifications@github.com wrote:

Yeah, it's tricky. And just to be clear, I tried all 6 combinations of the options, directly in the location field.

It did work once with just proxy_buffering, but I couldn't reproduce it, and it does sometimes work with smaller files(~7-8MB) without good reason and randomly.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

jakubgs

comment created time in 2 months

issue commentipfs/go-ipfs

The progress=true option breaks upload via an Nginx reverse proxy

Sorry it didn’t.

jakubgs

comment created time in 2 months

issue commentipfs/go-ipfs

The progress=true option breaks upload via an Nginx reverse proxy

Try having only one section that proxies all paths to your IPFS, and try putting everything in the location section.

That’s what I did, and if it works for you too it will be easier for you to debug once you start moving directives to /api/v0/add location one by one.

jakubgs

comment created time in 2 months

issue commentipfs/go-ipfs

The progress=true option breaks upload via an Nginx reverse proxy

Hey @jakubgs can you post your nginx config (location section) and tell me what other load balancers you have in front of nginx?

jakubgs

comment created time in 2 months

fork dsemenovsky/crypto-js

JavaScript library of crypto standards.

fork in 2 months

issue commentipfs/go-ipfs

The progress=true option breaks upload via an Nginx reverse proxy

Hi everyone, I was able to make progress option work behind Nginx proxy using these configuration options:

jakubgs

comment created time in 2 months

PR opened LiquidPlayer/LiquidCore

Fix/app store validation

Closes #180

+1 -0

0 comment

1 changed file

pr created time in 3 months

push eventvaultie/LiquidCore

Dmitry Semenovskiy

commit sha 2730ef0f8a8e8bb5de0529a150f8290bb19a6923

Add -DOPENSSL_NO_ASYNC flag

view details

Dmitry Semenovskiy

commit sha 3d50cbe869c92d6d95b5f0dc113630f9c5da5ad8

Merge pull request #2 from vaultie/fix/app-store-validation Add -DOPENSSL_NO_ASYNC flag

view details

push time in 3 months

PR opened vaultie/LiquidCore

Add -DOPENSSL_NO_ASYNC flag
+1 -0

0 comment

1 changed file

pr created time in 3 months

create barnchvaultie/LiquidCore

branch : fix/app-store-validation

created branch time in 3 months

push eventvaultie/LiquidCore

Eric Lange

commit sha 2c3b9567f6626493c59a3e8c1aec640e595681e9

Added icu static libraries for x86

view details

Eric Lange

commit sha e10cc7c49e4d105670448ce4833574f391a4b5a7

Added ICU to node/v8 builds, updated 64-bit libs

view details

Eric Lange

commit sha ed01cd050ad2f07ed4012bb7bbcc710eca5fc028

Updated x86 libraries for ICU

view details

Eric Lange

commit sha 3de33f14dbee414cd9c639a8b07e2ec32b2e5063

Updated armv7 libraries with ICU

view details

Eric Lange

commit sha 9b2a6c59108164c3a719ee9a929639b8e976560f

Moved liquidcore-cli functionality to liquidcore updated to latest Metro version

view details

Eric Lange

commit sha 8c0d4d156d3e61c59da1b2082e245fe6ab4867df

Added support for mocking native add-ons on desktop Updated scripts to handle postinstall correctly iOS scripts working now

view details

Eric Lange

commit sha e436d4e274f9dab856972cf372f1a033d8b3b583

Added bundling logic on the device

view details

Eric Lange

commit sha 355d2803b1f53c91bd99e4cea8a9c7ac5ff654a5

Fixed #145

view details

Eric Lange

commit sha 786b66b525451b8977d46a5010c82718667d0806

Fixed module naming issue

view details

Eric Lange

commit sha 1395e165e329b8aff9ebc4efbf72d2fcc4550f06

Enabled gradle include files and support workaround for maven packages.

view details

Eric Lange

commit sha 40f812432dc45da79f920d0357f9f1fb354d7ea8

Updated package-lock.json

view details

Eric Lange

commit sha 9146e34ecb0fea9dcdf1db1819aef07799f24f47

Get android package version from package.json Fixed issues in gradle.js

view details

Eric Lange

commit sha b4b9e468580d136f3e130eb6afe3cde37f80ae19

Update LICENSE.md

view details

Eric Lange

commit sha e1672bdadc096270b26c422dc83d8f3aaf89d714

Split v8 and nodejs into separate includes Fixed public exposure of BundlerOptions

view details

Eric Lange

commit sha db6d475ec15ba51227f1eb6954f46dc9811e3b4c

Merge branch 'master' of github.com:LiquidPlayer/LiquidCore

view details

Eric Lange

commit sha 3261c04047876bd2749048363cc9f5d79b435b4b

Create README.md

view details

Eric Lange

commit sha 169e00448b02bf9afa53296fb53dbf100f58f970

Updated the example module

view details

Eric Lange

commit sha b5512c4359baf58ec03645382595ddf05d20f276

Update README.md

view details

Eric Lange

commit sha fb50c4f9e51a8e06afdd27056cd05c53acbedb05

Updated package.json and fixed npm packing issue

view details

Eric Lange

commit sha 2a095adc80b4c4b9ed0864e0165cb53157d99e56

Fixed npm package

view details

push time in 3 months

PR merged vaultie/LiquidCore

Merge in 0.7.8
+11174 -1325

0 comment

195 changed files

dsemenovsky

pr closed time in 3 months

PR opened vaultie/LiquidCore

Merge in 0.7.8
+11174 -1325

0 comment

195 changed files

pr created time in 3 months

issue openedLiquidPlayer/LiquidCore

AppStore won't let upload the binary using LiquidCore

ITMS-90338: Non-public API usage - The app references non-public symbols in Frameworks/LiquidCore.framework/LiquidCore: _getcontext, _makecontext, _setcontext. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at

created time in 3 months

issue commentLiquidPlayer/LiquidCore

Events are not emitted when extending NSObject

Solution:

TestClass in this case wasn't reference anywhere else and delegate in LCMicroService got removed since it is a weak reference.

Closing this issue.

dsemenovsky

comment created time in 3 months

issue closedLiquidPlayer/LiquidCore

Events are not emitted when extending NSObject

I am trying to create a service class which, I believe, is more common approach when talking to JavaScript in the background. However, I cannot get any events emitted.

Here is the class:

import Foundation
import LiquidCore

class TestClass: NSObject, LCMicroServiceDelegate,
  LCMicroServiceEventListener {


    override init() {
        super.init()
        let url = LCMicroService.bundle("example")
        let service = LCMicroService(url: url,
                                       delegate: self)
        print(service)
        service?.start()
    }

  func onStart(_ service: LCMicroService) {
    print(service)
    service.addEventListener("ready",listener: self)
    service.addEventListener("pong", listener: self)
  }

  func onEvent(_ service: LCMicroService,
                   event: String,
                 payload: Any?) {
    print(event)
    if event == "ready" {
      service.emit("ping")
    } else if event == "pong" {
      let p = (payload as! Dictionary<String,AnyObject>)
    print(payload)
      let message = p["message"] as! String
      DispatchQueue.main.async {
        print(message)
      }
    }
  }
}

Here is the ViewController:

import UIKit

class ViewController: UIViewController {

  @IBOutlet weak var textBox: UITextField!

  override func viewDidLoad() {
    super.viewDidLoad()
    
    TestClass()
  }
}

And this is the output:

Optional(<LCMicroService: 0x6000039b6530>)
2020-05-25 14:26:23.980155-0400 Test[24162:4495040] MicroService User-Agent : LiquidCore/0.7.8 (iOS; API=13.5)
2020-05-25 14:26:23.987398-0400 Test[24162:4495025] App Transport Security has blocked a cleartext HTTP (http://) resource load since it is insecure. Temporary exceptions can be configured via your app's Info.plist file.
2020-05-25 14:26:23.987633-0400 Test[24162:4495025] Cannot start load of Task <010A76A4-AFAE-4A16-A08B-0B348D5F4C77>.<1> since it does not conform to ATS policy
2020-05-25 14:26:23.992659-0400 Test[24162:4495025] Task <010A76A4-AFAE-4A16-A08B-0B348D5F4C77>.<1> finished with error [-1022] Error Domain=NSURLErrorDomain Code=-1022 "The resource could not be loaded because the App Transport Security policy requires the use of a secure connection." UserInfo={NSUnderlyingError=0x600001cc8510 {Error Domain=kCFErrorDomainCFNetwork Code=-1022 "(null)"}, NSErrorFailingURLStringKey=http://localhost:8082/example.bundle?platform=ios&dev=true, NSErrorFailingURLKey=http://localhost:8082/example.bundle?platform=ios&dev=true, NSLocalizedDescription=The resource could not be loaded because the App Transport Security policy requires the use of a secure connection.}
2020-05-25 14:26:24.043894-0400 Test[24162:4495040] stdout: Hello, World!

As you can see, events are not getting emitted.

Same sample code works when extending UIViewController.

closed time in 3 months

dsemenovsky

issue openedLiquidPlayer/LiquidCore

Events are not emitted when using extending NSObject

I am trying to create a service class which, I believe, is more common approach when talking to JavaScript in the background. However, I cannot get any events emitted.

Here is the class:

import Foundation
import LiquidCore

class TestClass: NSObject, LCMicroServiceDelegate,
  LCMicroServiceEventListener {


    override init() {
        super.init()
        let url = LCMicroService.bundle("example")
        let service = LCMicroService(url: url,
                                       delegate: self)
        print(service)
        service?.start()
    }

  func onStart(_ service: LCMicroService) {
    print(service)
    service.addEventListener("ready",listener: self)
    service.addEventListener("pong", listener: self)
  }

  func onEvent(_ service: LCMicroService,
                   event: String,
                 payload: Any?) {
    print(event)
    if event == "ready" {
      service.emit("ping")
    } else if event == "pong" {
      let p = (payload as! Dictionary<String,AnyObject>)
    print(payload)
      let message = p["message"] as! String
      DispatchQueue.main.async {
        print(message)
      }
    }
  }
}

Here is the ViewController:

import UIKit

class ViewController: UIViewController {

  @IBOutlet weak var textBox: UITextField!

  override func viewDidLoad() {
    super.viewDidLoad()
    
    TestClass()
  }
}

And this is the output:

Optional(<LCMicroService: 0x6000039b6530>)
2020-05-25 14:26:23.980155-0400 Test[24162:4495040] MicroService User-Agent : LiquidCore/0.7.8 (iOS; API=13.5)
2020-05-25 14:26:23.987398-0400 Test[24162:4495025] App Transport Security has blocked a cleartext HTTP (http://) resource load since it is insecure. Temporary exceptions can be configured via your app's Info.plist file.
2020-05-25 14:26:23.987633-0400 Test[24162:4495025] Cannot start load of Task <010A76A4-AFAE-4A16-A08B-0B348D5F4C77>.<1> since it does not conform to ATS policy
2020-05-25 14:26:23.992659-0400 Test[24162:4495025] Task <010A76A4-AFAE-4A16-A08B-0B348D5F4C77>.<1> finished with error [-1022] Error Domain=NSURLErrorDomain Code=-1022 "The resource could not be loaded because the App Transport Security policy requires the use of a secure connection." UserInfo={NSUnderlyingError=0x600001cc8510 {Error Domain=kCFErrorDomainCFNetwork Code=-1022 "(null)"}, NSErrorFailingURLStringKey=http://localhost:8082/example.bundle?platform=ios&dev=true, NSErrorFailingURLKey=http://localhost:8082/example.bundle?platform=ios&dev=true, NSLocalizedDescription=The resource could not be loaded because the App Transport Security policy requires the use of a secure connection.}
2020-05-25 14:26:24.043894-0400 Test[24162:4495040] stdout: Hello, World!

As you can see, events are not getting emitted.

created time in 3 months

more