profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/tmc/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Travis Cline tmc @VirtaHealth Earth ๐Ÿš€

grpc-ecosystem/grpc-gateway 10727

gRPC to JSON proxy generator following the gRPC HTTP spec

grpc/grpc-web 5518

gRPC for Web Clients

rogchap/v8go 1285

Execute JavaScript from Go

jmoiron/modl 465

golang database modelling library

alex/django-ajax-validation 256

A reusable application to preform ajax validation on django forms.

seancribbs/riak_zmq 22

Publish writes to Riak KV to 0MQ (based on linked gist)

rhencke/glut 18

GLUT bindings for Go

foobaz/gdal 4

Go (golang) wrapper for GDAL, the Geospatial Data Abstraction Library

tmc/adt 3

Package adt provides read access to ADT (Advantage) database files

startedipinfo/cli

started time in an hour

fork alexlovelltroy/wks-quickstart-firekube

Example configuration to create Kubernetes clusters powered by ignite and gitops

fork in an hour

push eventrogchap/v8go

Genevieve

commit sha 69de0c53eb430e05502fbb7f3d1aa72a6f42fca4

Correct example in readme (#128)

view details

push time in 3 hours

PR merged rogchap/v8go

Correct example in readme
+1 -1

1 comment

1 changed file

genevieve

pr closed time in 3 hours

issue openedrogchap/v8go

Not providing console does not fail

It looks like console is defined by default, just it does not work - it does not print anything to the terminal. I have a script which uses console and running it did not raise any error (while if I try to access some other symbol it fails).

So I suggest the default console is removed, or a working implementation is provided instead.

created time in 5 hours

Pull request review commentrogchap/v8go

promise: run callbacks on resolution

 func (p *Promise) Result() *Value { 	val := &Value{ptr, p.ctx} 	return val }++// Then accepts 1 or 2 callbacks.+// The first is invoked when the promise has been fulfilled.+// The second is invoked when the promise has been rejected.+// The returned Promise resolves after the callback finishes execution.+//+// V8 only invokes the callback when processing "microtasks".+// The default MicrotaskPolicy processes them when the call depth decreases to 0.+// Call (*Context).PerformMicrotaskCheckpoint to trigger it manually.+func (p *Promise) Then(cbs ...FunctionCallback) *Promise {+	p.ctx.register()+	defer p.ctx.deregister()++	var ptr C.ValuePtr+	switch len(cbs) {+	case 1:+		cbID := p.ctx.iso.registerCallback(cbs[0])+		ptr = C.PromiseThen(p.ptr, C.int(cbID))+	case 2:+		cbID1 := p.ctx.iso.registerCallback(cbs[0])+		cbID2 := p.ctx.iso.registerCallback(cbs[1])+		ptr = C.PromiseThen2(p.ptr, C.int(cbID1), C.int(cbID2))++	default:+		panic("1 or 2 callbacks required")

OK. So will you then change the API now? Like template.Set currently returns err. It seems it should not anymore and just panic?

robfig

comment created time in 5 hours

issue openedrogchap/v8go

How to construct an array and pass it in through global

I could not find any documentation how to construct an array and pass it in through global.

created time in 5 hours

issue openedrogchap/v8go

Explanation of architecture

I would like to better understand how this package integrates V8 with Go. I could not find it in documentation, so I am making this question/documentation request issue.

How does V8 integrate with Go? Are threads used by V8 completely separate from threads used by Go? How you control how many threads are used? By the number of isolates you make? Is isolate always bound to one thread or does it move around?

I understand why V8 has isolates and contexts (isolate is one tab, while contexts can be multiple frames shown on that tab), but in the context of Go, I do not see a reason why would one use multiple contexts and not simply multiple isolates? Using multiple contexts seem that can introduce only problems by one context maybe blocking another context? Is it any easier to share data between contexts than it is between isolates? It looks to me like it all cases data goes first to Go and then back in?

Are isolates/context thread safe? How they work with goroutines? If I create one isolate, can I spawn contexts from different goroutines?

In my view, ideally, isolate should be tied to the current goroutine, so that it can also be moved between threads as Go runtime sees fit. Or even better, if contexts could be in each in its own (parallel) goroutine, while sharing one isolate. So my use case is to run some JS for every HTTP request (similar to server-side rendering) and spawning isolate for each request seems costly. On the other hand, if isolates are separate threads from regular Go threads, then it is tricky to know what is the pool of isolates I have to keep around and how large and so on. Then it becomes almost like I would have some background node processes I send things to for processing.

created time in 6 hours

push eventgrpc-ecosystem/grpc-gateway

Renovate Bot

commit sha 9acc39a4a85e3267a953f207bdd7525aaf89e9ab

chore(deps): update dependency com_google_protobuf to v3.16.0

view details

push time in 8 hours

delete branch grpc-ecosystem/grpc-gateway

delete branch : renovate/master-com_google_protobuf-3.x

delete time in 8 hours

PR merged grpc-ecosystem/grpc-gateway

chore(deps): update dependency com_google_protobuf to v3.16.0 (master) cla: yes

WhiteSource Renovate

This PR contains the following updates:

Package Type Update Change
com_google_protobuf http_archive minor v3.15.8 -> v3.16.0

Release Notes

<details> <summary>protocolbuffers/protobuf</summary>

v3.16.0

Compare Source

C++

  • Fix compiler warnings issue found in conformance_test_runner #โ€‹8189 (#โ€‹8190)
  • Fix MinGW-w64 build issues. (#โ€‹8286)
  • [Protoc] C++ Resolved an issue where NO_DESTROY and CONSTINIT are in incorrect order (#โ€‹8296)
  • Fix PROTOBUF_CONSTINIT macro redefinition (#โ€‹8323)
  • Delete StringPiecePod (#โ€‹8353)
  • Fix gcc error: comparison of unsigned expression in '>= 0' is always โ€ฆ (#โ€‹8309)
  • Fix cmake install on iOS (#โ€‹8301)
  • Create a CMake option to control whether or not RTTI is enabled (#โ€‹8347)
  • Fix endian.h location on FreeBSD (#โ€‹8351)
  • Refactor util::Status (#โ€‹8354)
  • Make util::Status more similar to absl::Status (#โ€‹8405)
  • Fix -Wsuggest-destructor-override for generated C++ proto classes. (#โ€‹8408)
  • Refactor StatusOr and StringPiece (#โ€‹8406)
  • Refactor uint128 (#โ€‹8416)
  • The ::pb namespace is no longer exposed due to conflicts.
  • Allow MessageDifferencer::TreatAsSet() (and friends) to override previous calls instead of crashing.
  • Reduce the size of generated proto headers for protos with string or bytes fields.
  • Move arena() operation on uncommon path to out-of-line routine
  • For iterator-pair function parameter types, take both iterators by value.
  • Code-space savings and perhaps some modest performance improvements in RepeatedPtrField.
  • Eliminate nullptr check from every tag parse.
  • Remove unused $name$_cached_byte_size fields.
  • Serialize extension ranges together when not broken by a proto field in the middle.
  • Do out-of-line allocation and deallocation of string object in ArenaString.
  • Streamline ParseContext::ParseMessage<T> to avoid code bloat and improve performance.
  • New member functions RepeatedField::Assign, RepeatedPtrField::{Add, Assign}.
  • Fix undefined behavior warning due to innocuous uninitialization of value on an error path.
  • Avoid expensive inlined code space for encoding message length for messages

    = 128 bytes and instead do a procedure call to a shared out-of-line routine.

  • util::DefaultFieldComparator will be final in a future version of protobuf. Subclasses should inherit from SimpleFieldComparator instead.

C

  • Add .NET 5 target and improve WriteString performance with SIMD (#โ€‹8147)

Java

  • deps: update JUnit and Truth (#โ€‹8319)
  • Detect invalid overflow of byteLimit and return InvalidProtocolBufferException as documented.
  • Exceptions thrown while reading from an InputStream in parseFrom are now included as causes.
  • Support potentially more efficient proto parsing from RopeByteStrings.
  • Clarify runtime of ByteString.Output.toStringBuffer().
  • Added UnsafeByteOperations to protobuf-lite (#โ€‹8426)

JavaScript

  • Make Any.pack() chainable.

Python

  • Fix some constness / char literal issues being found by MSVC standard conforming mode (#โ€‹8344)
  • Switch on "new" buffer API (#โ€‹8339)
  • Enable crosscompiling aarch64 python wheels under dockcross manylinux docker image (#โ€‹8280)
  • Fixed a bug in text format where a trailing colon was printed for repeated field.
  • When TextFormat encounters a duplicate message map key, replace the current one instead of merging.

Objective-C

PHP

  • read_property() handler is not supposed to return NULL (#โ€‹8362)
  • Changed parameter type from long to integer (#โ€‹7613)
  • fix: README supported PHP version for C extension (#โ€‹8236)

Ruby

  • Fixed quadratic memory usage when appending to arrays. (#โ€‹8364)
  • Fixed memory leak of Ruby arena objects. (#โ€‹8461)
  • Add support for proto3 json_name in compiler and field definitions. (#โ€‹8356)

Other

  • Some doc on AOT compilation and protobuf (#โ€‹8294)
  • [CMake] Ability to pass options to protoc executable from cmake (#โ€‹8374)
  • Add --fatal_warnings flag to treat warnings as errors (#โ€‹8131)
  • [bazel] Remove deprecated way to depend on googletest (#โ€‹8396)
  • add error returns missing from protoc to prevent it from exiting withโ€ฆ (#โ€‹8409)

</details>


Configuration

:date: Schedule: At any time (no schedule defined).

:vertical_traffic_light: Automerge: Enabled.

:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

:no_bell: Ignore: Close this PR and you won't be reminded about this update again.


  • [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

+3 -3

0 comment

1 changed file

renovate[bot]

pr closed time in 8 hours

startedSamVerschueren/tsd

started time in 8 hours

startedandygeiss/ecs

started time in 9 hours

PR opened grpc-ecosystem/grpc-gateway

chore(deps): update dependency com_google_protobuf to v3.16.0 (master)

WhiteSource Renovate

This PR contains the following updates:

Package Type Update Change
com_google_protobuf http_archive minor v3.15.8 -> v3.16.0

Release Notes

<details> <summary>protocolbuffers/protobuf</summary>

v3.16.0

Compare Source

C++

  • Fix compiler warnings issue found in conformance_test_runner #โ€‹8189 (#โ€‹8190)
  • Fix MinGW-w64 build issues. (#โ€‹8286)
  • [Protoc] C++ Resolved an issue where NO_DESTROY and CONSTINIT are in incorrect order (#โ€‹8296)
  • Fix PROTOBUF_CONSTINIT macro redefinition (#โ€‹8323)
  • Delete StringPiecePod (#โ€‹8353)
  • Fix gcc error: comparison of unsigned expression in '>= 0' is always โ€ฆ (#โ€‹8309)
  • Fix cmake install on iOS (#โ€‹8301)
  • Create a CMake option to control whether or not RTTI is enabled (#โ€‹8347)
  • Fix endian.h location on FreeBSD (#โ€‹8351)
  • Refactor util::Status (#โ€‹8354)
  • Make util::Status more similar to absl::Status (#โ€‹8405)
  • Fix -Wsuggest-destructor-override for generated C++ proto classes. (#โ€‹8408)
  • Refactor StatusOr and StringPiece (#โ€‹8406)
  • Refactor uint128 (#โ€‹8416)
  • The ::pb namespace is no longer exposed due to conflicts.
  • Allow MessageDifferencer::TreatAsSet() (and friends) to override previous calls instead of crashing.
  • Reduce the size of generated proto headers for protos with string or bytes fields.
  • Move arena() operation on uncommon path to out-of-line routine
  • For iterator-pair function parameter types, take both iterators by value.
  • Code-space savings and perhaps some modest performance improvements in RepeatedPtrField.
  • Eliminate nullptr check from every tag parse.
  • Remove unused $name$_cached_byte_size fields.
  • Serialize extension ranges together when not broken by a proto field in the middle.
  • Do out-of-line allocation and deallocation of string object in ArenaString.
  • Streamline ParseContext::ParseMessage<T> to avoid code bloat and improve performance.
  • New member functions RepeatedField::Assign, RepeatedPtrField::{Add, Assign}.
  • Fix undefined behavior warning due to innocuous uninitialization of value on an error path.
  • Avoid expensive inlined code space for encoding message length for messages

    = 128 bytes and instead do a procedure call to a shared out-of-line routine.

  • util::DefaultFieldComparator will be final in a future version of protobuf. Subclasses should inherit from SimpleFieldComparator instead.

C

  • Add .NET 5 target and improve WriteString performance with SIMD (#โ€‹8147)

Java

  • deps: update JUnit and Truth (#โ€‹8319)
  • Detect invalid overflow of byteLimit and return InvalidProtocolBufferException as documented.
  • Exceptions thrown while reading from an InputStream in parseFrom are now included as causes.
  • Support potentially more efficient proto parsing from RopeByteStrings.
  • Clarify runtime of ByteString.Output.toStringBuffer().
  • Added UnsafeByteOperations to protobuf-lite (#โ€‹8426)

JavaScript

  • Make Any.pack() chainable.

Python

  • Fix some constness / char literal issues being found by MSVC standard conforming mode (#โ€‹8344)
  • Switch on "new" buffer API (#โ€‹8339)
  • Enable crosscompiling aarch64 python wheels under dockcross manylinux docker image (#โ€‹8280)
  • Fixed a bug in text format where a trailing colon was printed for repeated field.
  • When TextFormat encounters a duplicate message map key, replace the current one instead of merging.

Objective-C

PHP

  • read_property() handler is not supposed to return NULL (#โ€‹8362)
  • Changed parameter type from long to integer (#โ€‹7613)
  • fix: README supported PHP version for C extension (#โ€‹8236)

Ruby

  • Fixed quadratic memory usage when appending to arrays. (#โ€‹8364)
  • Fixed memory leak of Ruby arena objects. (#โ€‹8461)
  • Add support for proto3 json_name in compiler and field definitions. (#โ€‹8356)

Other

  • Some doc on AOT compilation and protobuf (#โ€‹8294)
  • [CMake] Ability to pass options to protoc executable from cmake (#โ€‹8374)
  • Add --fatal_warnings flag to treat warnings as errors (#โ€‹8131)
  • [bazel] Remove deprecated way to depend on googletest (#โ€‹8396)
  • add error returns missing from protoc to prevent it from exiting withโ€ฆ (#โ€‹8409)

</details>


Configuration

:date: Schedule: At any time (no schedule defined).

:vertical_traffic_light: Automerge: Enabled.

:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

:no_bell: Ignore: Close this PR and you won't be reminded about this update again.


  • [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

+3 -3

0 comment

1 changed file

pr created time in 10 hours

fork therealjeffg/heroku-ipfs-ghost

The Ghost blog system upgraded with Heroku deploys & IPFS support.

fork in 12 hours

startedkylebarron/usgs-topo-tiler

started time in 12 hours

push eventgoogle/fhir

Nick George

commit sha 66ddca4edbf0b7dd95d5ae9dca70e2af5de6edf2

Fixes bug where non-resource ids were being printed in analytic mode PiperOrigin-RevId: 361957406

view details

push time in 12 hours

push eventgoogle/fhir

Cameron Tew

commit sha a13c306551ffd3aa929ec9bfb31bdd65e64f197d

Bump `rules_python` to 0.1.0. Loosen constraints for `requirements.txt` to allow for compatible package versions. Closes #30. PiperOrigin-RevId: 361707956

view details

push time in 12 hours

issue closedgoogle/fhir

Overly strict Python dependency requirements

I'm getting this warning (even though it looks like an error) about the new PIP dependency resolver.

ERROR: After October 2020 you may experience errors when installing or updating packages. This is because pip will change the way that it resolves dependency conflicts.

We recommend you use --use-feature=2020-resolver to test your packages with the new resolver before it becomes the default.

google-fhir 0.6.2 requires protobuf==3.13.0, but you'll have protobuf 3.14.0 which is incompatible.

I can see that the requirements are set exactly: https://github.com/google/fhir/blob/master/py/requirements.txt For a library, would it be better to do something like this?

absl-py >= 0.10.0 < 0.11.0
backports.zoneinfo >= 0.2.1 < 0.3.0
mypy-protobuf >= 1.23 < 2
protobuf >= 3.13.0 < 4
python-dateutil >= 2.8.1 < 3
six >= 1.15.0 < 2

(I haven't tested those exactly, it's just speculation and assuming those are all semver.)

Thank you!

closed time in 12 hours

gitpushdashf

startedkoekeishiya/yabai

started time in 12 hours

push eventgoogle/fhir

Cameron Tew

commit sha b73adb1fac3dbfc198dfa14ebe242e1626434a72

Move mypy-protobuf dep into `build_distribution.sh`. The mypy-protobuf plugin is only necessary for generating the mypy stubs. This doesn't need to be enforced as a requirement for an installer of the package. PiperOrigin-RevId: 361686508

view details

push time in 12 hours

push eventgoogle/fhir

Ryan Brush

commit sha f52a7eccc542ab9096d108d646ba11665625ffb0

Add an ErrorReporter to expose all profile conversion and validation issues, rather than just the first one encountered. This also exposes validation issues via an FHIR OperationOutcome resource so they can be easily reported to external callers. PiperOrigin-RevId: 361213811

view details

push time in 12 hours

pull request commentgrpc-ecosystem/grpc-gateway

fix(deps): update google.golang.org/genproto commit hash to 4a47615 (master)

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will ignore this upgrade updateType and you will not receive PRs for any future google.golang.org/genproto:v0.0.0-20210505142820-a42aa055cf76 digest updates. Digest updates will resume if you update the specified tag at any time.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.

renovate[bot]

comment created time in 12 hours

delete branch grpc-ecosystem/grpc-gateway

delete branch : renovate/master-google.golang.org-genproto-digest

delete time in 12 hours

PR closed grpc-ecosystem/grpc-gateway

fix(deps): update google.golang.org/genproto commit hash to 4a47615 (master) cla: yes

WhiteSource Renovate

This PR contains the following updates:

Package Type Update Change
google.golang.org/genproto require digest a42aa05 -> 4a47615

Configuration

:date: Schedule: At any time (no schedule defined).

:vertical_traffic_light: Automerge: Enabled.

:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

:no_bell: Ignore: Close this PR and you won't be reminded about this update again.


  • [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

+1 -1

2 comments

1 changed file

renovate[bot]

pr closed time in 12 hours

push eventgrpc-ecosystem/grpc-gateway

Renovate Bot

commit sha 5152b13588c25df0baf4b95811a153ada8d8a2da

chore(deps): update golang docker tag to v1.16.4

view details

Renovate Bot

commit sha fd475298da9ac5e58eb03d1976a3161807261ffb

fix(deps): update google.golang.org/genproto commit hash to 4a47615

view details

push time in 12 hours

push eventgrpc-ecosystem/grpc-gateway

Renovate Bot

commit sha 5152b13588c25df0baf4b95811a153ada8d8a2da

chore(deps): update golang docker tag to v1.16.4

view details

push time in 13 hours

delete branch grpc-ecosystem/grpc-gateway

delete branch : renovate/master-docker-golang-1.x

delete time in 13 hours