profile
viewpoint

issue commentqm3ster/zigbeer-rs

interoperability with rust's zigbee "common interface for the interoperability"

@garro95

  1. Where can I contact you in a more realtime fashion?
  2. Do you have any Zigbee dongles/end devices?
akrpic77

comment created time in 5 days

push eventqm3ster/zigbeer-rs

qm3ster

commit sha 4e56baf98597c4c51a4f326b8f38b95198cb5652

Add interrogation commands, concept of sender

view details

push time in 6 days

push eventqm3ster/zigbeer-rs

qm3ster

commit sha 7b8cf96cd7cbc117cc5ed8b034eb41c93febebf7

Fix FrameControl order

view details

qm3ster

commit sha 9091284500f6fae88a1b8573fd9118d061390e40

Rename UnimplementedCmd to UnknownCmd

view details

qm3ster

commit sha 8c888b169cfc1a1820187cfc682ef41cd1b66a8d

Replace `for_each` with `while next()`

view details

qm3ster

commit sha 5b2181a757b7bc035c89425a8252f000dffba06b

Add more clusters, commands, value types

view details

push time in 8 days

issue commentqm3ster/zigbeer-rs

interoperability with rust's zigbee "common interface for the interoperability"

@akrpic77 I am probably going to continue this project now, do you know anything about the status of standardization of a Zigbee interface in Rust, or what @garro95 is up to now?

akrpic77

comment created time in 8 days

push eventqm3ster/zigbeer-rs

qm3ster

commit sha 673a5299c047d21f44e3cd513173afc676ec53a6

Bulkhead before tokio 0.2

view details

qm3ster

commit sha deb64ae3ab7705b2968ddfd591ebde0434014802

Update to tokio 0.2 Also updated other dependencies

view details

push time in 11 days

issue commenttokio-rs/tokio

framed with framed

I only find examples for sync adaptors: AES, Cryptostream, gzip. But it seems the differences would be very small, you just have to poll the underlying Read instead of blocking on it.

nnovikov

comment created time in 14 days

issue commenttokio-rs/tokio

framed with framed

Do these shorter buffers each contain exactly one serialized struct? Exactly multiple? Or can these structs be fragmented across the buffers you are producing?

nnovikov

comment created time in 19 days

issue commenttokio-rs/tokio

framed with framed

It doesn't sound like you need another Framed. What is the type of Item your Decoder produces?

nnovikov

comment created time in 20 days

pull request commentdilame/instagram-private-api

Add ListReelMediaViewerFeed and DirectThreadEntity.broadcastVideo()

So, in #891, by not having direct_v2 = '1' I was uploading it in a way that would never be accessible to a DM? For future reference, where did you get this information from?

Also, what does the "sampled" option mean?

Nerixyz

comment created time in a month

issue openeddilame/instagram-private-api

How to send a video as a direct?

Henlo, trying to make a DM out of an mp4.

Based on what I found here: https://github.com/dilame/instagram-private-api/blob/d5fc6a7a2c6b2aefa639bee53195886102ac5c7b/src/entities/direct-thread.entity.ts#L50-L62

I tried:

    const vidUp = await ig.upload.video({
      video: await fs.readFile(
        path.resolve(__dirname, "../data/SampleVideo_1280x720_1mb.mp4")
      ),
      duration: 5312,
      height: 720,
      width: 1280
    })
    console.log("vidUp", vidUp)

The video upload process returns: vidUp { xsharing_nonces: {}, status: 'ok' } (no upload_id in response body)

I based configure_video not just on similarity, but also these lines from mgp25/Instagram-API (see URL).

Not sure what video_result there stands for.

It's strange I am not getting an upload_id back despite the 'ok', it seems to be expected.

I also tried this:

    const uploadId = "1568498701788"
    const vidUp = await ig.upload.video({
      uploadId,
      video: await fs.readFile(
        path.resolve(__dirname, "../data/SampleVideo_1280x720_1mb.mp4")
      ),
      duration: 5312,
      height: 720,
      width: 1280
    })
    console.log("vidUp", vidUp)
    console.log("uploadId", uploadId)
    const res = await ig.directThread.broadcast({
      item: "configure_video",
      form: {
        upload_id: uploadId
      },
      threadIds: "340282366841710300949128112692906930936"
    })

which is probably stupid since the ID I should get back is probably different than the option ID. (I didn't check in the photo case, but the current code uses the returned one.) Anyway, this gives 403 Forbidden (probably because I am referencing someone else's or nonexistent video upload).

created time in a month

issue closedfacebook/flow

Impossible to refine away 'uninitialized variable'

It seems that uninitialized variable is a different type than void/typeof undefined I can make an uninitialized variable of type ?T or T|undefined, but then refinements don't work.

Neither throws an error, however in the below case:

let lastNumber: ?number
const output = []
if (lastNumber != null) {
  output.push(lastNumber /* lastNumber is Uncovered code */)
}

OR

let lastNumber: number | void
const output = []
if (lastNumber !== undefined) {
  output.push(lastNumber /* lastNumber is Uncovered code */)
}

flow type-at-pos into lastNumber gives (unknown) because uninitialized variable (at declaration)

But this has full coverage:

let lastNumber: ?number = undefined // Initialized with undefined
const output = []
if (lastNumber != null) {
  output.push(lastNumber /* Fully covered, type-at-pos is number */)
}

Can't reproduce at flow.org/try as it's just a coverage issue no error even if I assert (lastNumber: number)

closed time in 2 months

qm3ster

issue commentfacebook/flow

Impossible to refine away 'uninitialized variable'

It was a coverage issue, and years ago. Closing.

qm3ster

comment created time in 2 months

fork qm3ster/relogio

Terminal clock in Rust

fork in 2 months

CommitCommentEvent

issue commenttokio-rs/tokio

tokio-process: stdout / stderr not read in the order they are produced by underlying process

What happens if you tokio::spawn() stdout_fut and stderr_fut instead of joining them?

sfmunoz

comment created time in 2 months

issue commenttower-rs/tower-grpc

Implement Authorization

So what actually is gRPC auth after all? Is it really just a Authorization: BearerSIGNED_JWT header on the request?

spacejam

comment created time in 2 months

PR closed jest-community/eslint-plugin-jest

feat(rules): add `short` parameter to `no-alias-methods`

Fixes #234

@macklinu please have a look if you think this should be improved

+234 -21

7 comments

3 changed files

qm3ster

pr closed time in 3 months

delete branch qm3ster/firebase-event-store

delete branch : patch-1

delete time in 3 months

issue commenttokio-rs/tokio

rfc: collapse Tokio sub crates into single `tokio` crate

To me, the most important factors are:

  • Ease of contribution (for first time contributors and for everyone)
  • Build time
  • Build size

It seems that this change makes the first one harder, and allows the latter to grow with lesser negligence than the current arrangement.

Why should monolith v0.2 depend on monolith v0.3 instead of them both depending on unchanged-type v0.1? The superficial issue of "bloat" in a number of tiny packages from the same reputable organization is replaced by the more real issue of "churn" of unchanged types and code being republished over and over again.

carllerche

comment created time in 3 months

push eventqm3ster/firebase-event-store

Mihail Malo

commit sha 2881d6eecd74525dca24c5084bef215abe7127b8

Improve rules highlighting

view details

push time in 3 months

PR opened Rotorsoft/firebase-event-store

Add npm link
+4 -1

0 comment

1 changed file

pr created time in 3 months

push eventqm3ster/firebase-event-store

Mihail Malo

commit sha 990ffea63ef28c2eaf17566855748e1178e7000b

Add npm link

view details

push time in 3 months

fork qm3ster/firebase-event-store

CQRS style Event Sourcing backend and Kafka like bus on Firebase Firestore

fork in 3 months

pull request commentjest-community/eslint-plugin-jest

feat(rules): add `short` parameter to `no-alias-methods`

Yes, it me! I agree with that viewpoint. I suppose this PR should be closed. If I go ahead with that, it should be a new one.

qm3ster

comment created time in 3 months

more