added
stringdate
2025-04-01 04:05:38
2025-04-01 07:14:06
created
timestamp[us]date
2001-10-09 16:19:16
2025-01-01 03:51:31
id
stringlengths
4
10
metadata
dict
source
stringclasses
2 values
text
stringlengths
0
1.61M
2025-04-01T06:41:13.483232
2018-09-18T10:50:35
361245858
{ "authors": [ "SteveSandersonMS" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12729", "repo": "aspnet/Blazor", "url": "https://github.com/aspnet/Blazor/pull/1441" }
gharchive/pull-request
Include TPN file in VSIX and all nupkg files built from "src" directory. Fixes #335 Wow, I feel such approval. Thanks everyone 🤗
2025-04-01T06:41:13.486788
2016-06-23T22:51:38
162041072
{ "authors": [ "Rick-Anderson", "danroth27" ], "license": "CC-BY-4.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12730", "repo": "aspnet/Docs", "url": "https://github.com/aspnet/Docs/pull/1482" }
gharchive/pull-request
Add sphinx-autobuild to requirements.txt @danroth27 sorry looks like when I created this it included other commits.
2025-04-01T06:41:13.488348
2017-07-05T14:44:48
240675131
{ "authors": [ "ardalis", "dnfclas" ], "license": "CC-BY-4.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12731", "repo": "aspnet/Docs", "url": "https://github.com/aspnet/Docs/pull/3629" }
gharchive/pull-request
Minor edits to Razor Pages @ardalis, Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request. Thanks, .NET Foundation Pull Request Bot
2025-04-01T06:41:13.490953
2017-04-18T23:31:10
222574557
{ "authors": [ "halter73", "pakrym", "pranavkm" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12732", "repo": "aspnet/KestrelHttpServer", "url": "https://github.com/aspnet/KestrelHttpServer/pull/1715" }
gharchive/pull-request
Skip ConnectionsGetRoundRobinedToSecondaryListeners (#1691) I don't think skipping this test is terrible, but I think we're going to make a test fix in dev that could be backported. Merging for now, after @natemcmaster fixes it we are going to backport. Thanks @halter73 - we're trying to get a build out of patch and this one's blocking it. I'd be happy if we can fix the actual test, but the first step is to unblock the build while we investigate a solution.
2025-04-01T06:41:13.492811
2017-12-01T18:54:36
278561023
{ "authors": [ "assisrafael", "coveralls", "gavenheim" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12733", "repo": "assisrafael/angular-input-masks", "url": "https://github.com/assisrafael/angular-input-masks/pull/318" }
gharchive/pull-request
Adds documentation for ui-us-phone-number-mask Coverage remained the same at 99.034% when pulling b228144ce067f9b15fb9e4aada24148b576a4586 on gavenheim:feature/us-phone-documentation into 79cb3dd8ddbfe983b6a7648676d9928c637a9932 on assisrafael:master. Thank you for the pull request.
2025-04-01T06:41:13.494161
2016-06-16T15:05:03
160684791
{ "authors": [ "astrofrog", "burnpanck" ], "license": "bsd-2-clause", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12734", "repo": "astrofrog/numtraits", "url": "https://github.com/astrofrog/numtraits/pull/15" }
gharchive/pull-request
fixes #14, and added regression test @burnpanck - can you rebase on the latest master and push to this branch again? I had to fix some issues with Travis in #18 - thanks!
2025-04-01T06:41:13.520275
2017-02-08T21:51:17
206335838
{ "authors": [ "coveralls", "gcotelli" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12735", "repo": "ba-st/Buoy", "url": "https://github.com/ba-st/Buoy/pull/7" }
gharchive/pull-request
Added support for Percentages Coverage remained the same at 100.0% when pulling 7d939c69aed1db11e63a0a196802fbc0c2777811 on percentage into 4f0a3a2bb54c9cbe9d88d19e6568010bd722c0f1 on master.
2025-04-01T06:41:13.523807
2015-07-27T21:37:48
97559889
{ "authors": [ "badboy", "whatisgravity" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12736", "repo": "badboy/jabbot", "url": "https://github.com/badboy/jabbot/pull/13" }
gharchive/pull-request
Update to newest XMPP4r Did you test it with the latest versions? Yes, it works fine. No reason not to use the newest versions. Alright then. Thanks for being flexible, now I don't need my own branch for my silly bot. Good work, I was right about to build my own but I like the level of complexity vs. simplicity in your library. It is a good balance.
2025-04-01T06:41:13.527959
2019-08-19T08:45:13
482181731
{ "authors": [ "balassy", "coveralls" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12737", "repo": "balassy/aws-lambda-typescript", "url": "https://github.com/balassy/aws-lambda-typescript/pull/179" }
gharchive/pull-request
Greenkeeper/serverless offline 5.10.1 Coverage remained the same at 100.0% when pulling 4c0d205bb8502158126c1cf8c36b211f111ff8c4 on greenkeeper/serverless-offline-5.10.1 into 5bc0928fa842b54bca15c50cb1b1691ad6b94580 on master.
2025-04-01T06:41:13.558579
2015-07-27T21:15:59
97556489
{ "authors": [ "RavenHursT", "puzrin" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12738", "repo": "baudehlo/node-phantom-simple", "url": "https://github.com/baudehlo/node-phantom-simple/pull/65" }
gharchive/pull-request
Test for page.clearMemoryCache() Please, squash into single commit Odd.. PR still shows multiple commits.. but on my fork, it shows only 1: https://github.com/CaptoraInc/node-phantom-simple/commits/master Not sure what else to do here... Let's close it. It doesn't tests feature well anyway.
2025-04-01T06:41:13.608261
2021-02-26T21:29:33
817675228
{ "authors": [ "nvunnamm" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12739", "repo": "bcgov/ocp-sso", "url": "https://github.com/bcgov/ocp-sso/pull/187" }
gharchive/pull-request
Updating Kubernetes network policy have these changes been tested in sandbox with zero aporeto based policies? closed this unexpectedly.. Reopening it. The changes which I made are tested in sandbox.. but we had to add 2 aporeto based policies as per the guide.
2025-04-01T06:41:13.636318
2017-03-15T09:19:41
214327726
{ "authors": [ "codecov-io", "sbellem" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12740", "repo": "bigchaindb/bigchaindb", "url": "https://github.com/bigchaindb/bigchaindb/pull/1285" }
gharchive/pull-request
Add logging infrastructure Codecov Report Merging #1285 into master will decrease coverage by 1.05%. The diff coverage is 72.44%. @@ Coverage Diff @@ ## master #1285 +/- ## ========================================== - Coverage 98.08% 97.03% -1.06% ========================================== Files 51 53 +2 Lines 2294 2392 +98 ========================================== + Hits 2250 2321 +71 - Misses 44 71 +27 Continue to review full report at Codecov. Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update c3d9717...c293dce. Read the comment docs.
2025-04-01T06:41:13.644351
2015-07-20T20:51:46
96156993
{ "authors": [ "braydonf" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12741", "repo": "bitpay/bitcoind.js", "url": "https://github.com/bitpay/bitcoind.js/issues/41" }
gharchive/issue
Add tests for daemon VerifyScript method No longer relevant, as the method isn't exposed: https://github.com/bitpay/bitcore-node/commit/d7c16e11a3988c9f0f9d90b907cce9929841696f
2025-04-01T06:41:13.674678
2015-01-28T19:24:11
55802533
{ "authors": [ "ericherdzik" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12742", "repo": "bloomberg/brisket", "url": "https://github.com/bloomberg/brisket/pull/84" }
gharchive/pull-request
CPU optimization for rendering metatags @sylnp0201 You may want to look at this. This is a ~4% optimization in overall CPU time spent rendering a typical page. This is ready to go once Travis finishes.
2025-04-01T06:41:13.718203
2020-12-03T14:14:25
756230133
{ "authors": [ "alfred-landrum", "mattnibs" ], "license": "BSD-3-Clause", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12743", "repo": "brimsec/zq", "url": "https://github.com/brimsec/zq/pull/1743" }
gharchive/pull-request
zng.Marshal: support marshaling to time I'm not sure this if this is best approach for marshaling/unmarshaling fields with nano.Ts. Yet the problem remains. What we should probably do in the long run is have pkg/nano implement the resolver.(Un)Marshaler interface (this is what the go std does with Time and json). The problem with this is that nano.Ts is in pkg which means it shouldn't be dependent on anything outside it. Additionally I think package zng/resolver has nano as a dependency. There's some untangling to do here. What we should probably do in the long run is have pkg/nano implement the resolver.(Un)Marshaler interface (this is what the go std does with Time and json). The problem with this is that nano.Ts is in pkg which means it shouldn't be dependent on anything outside it. Additionally I think package zng/resolver has nano as a dependency. There's some untangling to do here. I agree we need to untangle. I think this PR is currently the best way to get the marshal support in. I think we should remove nano.Ts as a dependency of the zng & zng/resolver packages.
2025-04-01T06:41:13.736425
2015-08-08T15:46:38
99809773
{ "authors": [ "Koronen", "homu", "segiddins" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12744", "repo": "bundler/bundler", "url": "https://github.com/bundler/bundler/pull/3924" }
gharchive/pull-request
Fix Style/RegexpLiteral @homu r+ :pushpin: Commit 122518f has been approved by segiddins :hourglass: Testing commit 122518f with merge 1b3eb24... :sunny: Test successful - status
2025-04-01T06:41:13.763670
2015-07-08T16:03:18
93826821
{ "authors": [ "Bombenleger", "vitorgalvao" ], "license": "BSD-2-Clause", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12745", "repo": "caskroom/homebrew-cask", "url": "https://github.com/caskroom/homebrew-cask/pull/12474" }
gharchive/pull-request
updated flash to <IP_ADDRESS> Thank you for the contribution. It was merged directly as bf6272bf647cc5ce509c59093521c6e6d5a61132 to keep commit history cleaner. Your contribution is still credited to you.
2025-04-01T06:41:13.764414
2015-11-28T21:25:21
119318743
{ "authors": [ "adityadalal924", "reitermarkus" ], "license": "BSD-2-Clause", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12746", "repo": "caskroom/homebrew-cask", "url": "https://github.com/caskroom/homebrew-cask/pull/15465" }
gharchive/pull-request
FreeFileSync 7.6: fix URL Thank you for the contribution. It was merged directly as 82672b355f453a7cee04ca57c324a8c1c55394f1 to keep commit history cleaner. Your contribution is still credited to you.
2025-04-01T06:41:13.766564
2016-02-01T05:49:04
130263671
{ "authors": [ "adidalal", "wickedsp1d3r" ], "license": "BSD-2-Clause", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12747", "repo": "caskroom/homebrew-cask", "url": "https://github.com/caskroom/homebrew-cask/pull/18047" }
gharchive/pull-request
Update Moom.app to v3.2.3 Thank you for the contribution. It needed some fixes, so they were made in 15511ae363ec8b4816a93aebd9401f44f6d39105. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.
2025-04-01T06:41:13.806757
2021-01-07T11:57:13
781260308
{ "authors": [ "chgl" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12748", "repo": "chgl/fhir-server-exporter", "url": "https://github.com/chgl/fhir-server-exporter/pull/14" }
gharchive/pull-request
ci: added daily trivy scan :tada: This PR is included in version 1.1.10 :tada: The release is available on GitHub release Your semantic-release bot :package::rocket: :tada: This PR is included in version 1.1.10 :tada: The release is available on GitHub release Your semantic-release bot :package::rocket:
2025-04-01T06:41:13.833700
2019-11-21T08:12:57
526431818
{ "authors": [ "ketch", "rjleveque" ], "license": "BSD-3-Clause", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12749", "repo": "clawpack/riemann_book", "url": "https://github.com/clawpack/riemann_book/pull/205" }
gharchive/pull-request
Minor revisions. Looks good, thanks! I notice that in some of these early notebooks the %matplotlib inline cell and a cell of import statements appears at the top of the notebook, whereas in most later notebooks we have moved all the code cells to after the initial introductory markdown cells. Should we try to make this more consistent? I notice that in some of these early notebooks the %matplotlib inline cell and a cell of import statements appears at the top of the notebook, whereas in most later notebooks we have moved all the code cells to after the initial introductory markdown cells. Should we try to make this more consistent? Okay, I've incorporated that change into this PR. I'm still working through the chapters, so this is still WIP. In the shallow water chapter, I changed the code so that certain characteristics are plotted by default; this way they show up in the book. This is important since we discuss how these characteristics show that the solution is unphysical in these two cases. I'd like to go ahead and merge this now, since other chapters are being edited concurrently and it would be good to get these changes to the copy editors. Please review. I made the pdf from this PR before I read through it all the other day, and in general it all looks fine to me, and can be merged as far as I'm concerned. I did make a few notes of some minor changes in these notebooks, but I can do those as part of my next pass through updating the notebooks. So if you are done updating for now then once this is merged I'll make a pass in the next couple days. Sounds good. I am planning to go through the remaining chapters, but it looks like I won't get to that for a week or so at least. So go ahead and make a pass.
2025-04-01T06:41:13.836933
2016-02-04T20:59:32
131472382
{ "authors": [ "bemehow", "cliffano" ], "license": "bsd-3-clause", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12750", "repo": "cliffano/packer-post-processor-json-updater", "url": "https://github.com/cliffano/packer-post-processor-json-updater/pull/2" }
gharchive/pull-request
add interpolation of template variables Thanks for the PR, much appreciated :). Just a note, I'm going to separate the two changes. I'll release interpolation support in version 1.1 . But the multi ami-ids / multi regions support will go to 2.0 later on since it changes the behaviour of this post processor. I think the guts of the second change is to handle multi builds, I'll modify your PR a bit to add more flexibility to the output. There are users who do not wish to use region as the output key, others wish to use other field as key like AMI name.
2025-04-01T06:41:13.837856
2018-05-11T10:09:07
322242293
{ "authors": [ "nwmac", "richard-cox" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12751", "repo": "cloudfoundry-incubator/stratos", "url": "https://github.com/cloudfoundry-incubator/stratos/pull/2152" }
gharchive/pull-request
Fix stepper issue with redirect not working Only found one existing place this was used (edit app). Confirmed fixed
2025-04-01T06:41:13.838820
2017-07-19T19:41:31
244151743
{ "authors": [ "evanfarrar" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12752", "repo": "cloudfoundry/docs-bosh", "url": "https://github.com/cloudfoundry/docs-bosh/pull/332" }
gharchive/pull-request
Use BOSH 2.0 syntax in release docs. Also didn't notice #319 . Please merge #319 first and I will resolve conflicts.
2025-04-01T06:41:13.876684
2018-03-07T06:35:39
302980779
{ "authors": [ "sushanthakumar", "vdabbara", "woshihaoren" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12753", "repo": "cni-genie/CNI-Genie", "url": "https://github.com/cni-genie/CNI-Genie/issues/82" }
gharchive/issue
Can genie support contiv? @woshihaoren, we have a sort of generic mechanism wrt various plugin handling which enables the support for most of the plugins seamlessly, we will have a look into this and get back to u with confirmation, thanks I tried cni-genie with contiv-cni added to supported cni list and it worked seamlessly. however i am lost getting flannel cni co-exist. This is in k3s environment and i don't see flannel binary present in /opt/cni/bin directory..
2025-04-01T06:41:13.898702
2021-07-23T08:23:45
951361148
{ "authors": [ "ice1000", "lefou", "lolgab" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12754", "repo": "com-lihaoyi/mill", "url": "https://github.com/com-lihaoyi/mill/pull/1421" }
gharchive/pull-request
Use Java 8 to build release artifacts What's the rationale? Before this PR, we published with Java 9. Although we explicitly select the target as Java 8, some binary incompatibilities sneaked in all of our current releases. So, I think it's safer to just use Java 8 for compiling the release versions. See the output of this experimental integration of MiMa in the mill build: 09:59:20 ⌁ lefou:~/work/opensource/mill mima+* 130 ± mill -j 0 main.__.mimaReportBinaryIssues Using experimental parallel evaluator with 16 threads [#07] [281/306] main.core.compile [#11] Scanning 79 classfiles for binary compatibility in /home/lefou/work/opensource/mill/out/main/api/compile/dest/classes ... [#03] [282/306] scalalib.api.localClasspath [#11] * static method transferTo(java.io.OutputStream)Long in class mill.api.DummyInputStream does not have a correspondent in current version filter with: ProblemFilters.exclude[DirectMissingMethodProblem]("mill.api.DummyInputStream.transferTo") [#11] * static method readNBytes(Array[Byte],Int,Int)Int in class mill.api.DummyInputStream does not have a correspondent in current version filter with: ProblemFilters.exclude[DirectMissingMethodProblem]("mill.api.DummyInputStream.readNBytes") [#11] * static method readAllBytes()Array[Byte] in class mill.api.DummyInputStream does not have a correspondent in current version filter with: ProblemFilters.exclude[DirectMissingMethodProblem]("mill.api.DummyInputStream.readAllBytes") You can see that comparing the HEAD of 0.9.x branch with the 0.9.9 tag, some methods only defined in Java 9 sneak into our API. This happens when I run (and compile) mill with Java 8. Thanks for the explanation! Glad that the mill-mima plugin is already creating some value 😍
2025-04-01T06:41:13.899508
2016-01-29T04:11:33
129661751
{ "authors": [ "Ch4s3", "ybur-yug" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12755", "repo": "cometaworks/fast_fuzzy_search_in_phoenix_and_ecto", "url": "https://github.com/cometaworks/fast_fuzzy_search_in_phoenix_and_ecto/pull/2" }
gharchive/pull-request
typo Totes didnt mean to do this on your fork I'm just tired and inattentive. Thx0rz for not making fun of how absurd this request for a merge was tho haha
2025-04-01T06:41:13.901401
2020-03-04T02:36:52
575095583
{ "authors": [ "pd0wm", "valish" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12756", "repo": "commaai/openpilot", "url": "https://github.com/commaai/openpilot/pull/1192" }
gharchive/pull-request
Refactor frame I see a lot of repeater color definitions in the code. Can we replace those by a define with a name of the color? Why did the jenkins test not run? Can you rebase to latest master so we see CPU usage in CI?
2025-04-01T06:41:13.920864
2017-01-02T12:44:54
198330775
{ "authors": [ "conda-forge-linter", "ocefpaf" ], "license": "BSD-3-Clause", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12757", "repo": "conda-forge/pyqt-feedstock", "url": "https://github.com/conda-forge/pyqt-feedstock/pull/11" }
gharchive/pull-request
rerender with auto Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
2025-04-01T06:41:13.930265
2015-05-08T07:18:10
74262334
{ "authors": [ "a1exsh", "ept" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12758", "repo": "confluentinc/bottledwater-pg", "url": "https://github.com/confluentinc/bottledwater-pg/pull/10" }
gharchive/pull-request
Add missing chars for getopt_long in bwtest and kafka client. Great, thank you! I had totally missed the single-char options.
2025-04-01T06:41:13.937908
2015-11-27T21:08:42
119246318
{ "authors": [ "ddollar", "mattmanning" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12759", "repo": "convox/convox.github.io", "url": "https://github.com/convox/convox.github.io/pull/73" }
gharchive/pull-request
update env doc to explain local functionality document local Environment in environment section of docs Looks good but does not cover the fact that variables specified in the docker-compose.yml are required and convox start will block until they are set.
2025-04-01T06:41:13.947514
2017-06-30T17:28:51
239842053
{ "authors": [ "codecov-io", "dankohn", "david-a-wheeler", "jdossett" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12760", "repo": "coreinfrastructure/best-practices-badge", "url": "https://github.com/coreinfrastructure/best-practices-badge/pull/900" }
gharchive/pull-request
Merge parse yaml @dankohn : Seem okay? Codecov Report Merging #900 into master will not change coverage. The diff coverage is n/a. @@ Coverage Diff @@ ## master #900 +/- ## ===================================== Coverage 100% 100% ===================================== Files 45 45 Lines 1473 1473 ===================================== Hits 1473 1473 Continue to review full report at Codecov. Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 01832c4...21e9ec0. Read the comment docs. Shall I merge? LGTM I'll merge.
2025-04-01T06:41:13.951840
2015-04-22T21:20:42
70237995
{ "authors": [ "marineam", "pbx0", "robszumski" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12761", "repo": "coreos/docs", "url": "https://github.com/coreos/docs/pull/486" }
gharchive/pull-request
mantle: add documentation for mantle Could use some links to it :) Content and everything LGTM @marineam Links to the repository? links from other docs to here so it is discoverable Added a link at the bottom of the main SDK doc, modifying-coreos. LGTM
2025-04-01T06:41:13.968274
2018-04-03T09:11:04
310753802
{ "authors": [ "DaanDeMeyer", "bstaletic" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12762", "repo": "cquery-project/cquery", "url": "https://github.com/cquery-project/cquery/pull/590" }
gharchive/pull-request
Stricter glob This doesn't actually change cmake behaviour because * in cmake glob is recursive anyway. Hmm, you're right. I should test stuff more. Any idea of how this can be fixed? Nothing elegant comes to mind. You can add src/foo/*.{cpp,h} and keep src/*.{cpp,h} manual. Note that I'm using * here as a shell would interpret it, not as cmake would. Actually, I get different results with GLOB and GLOB_RECURSE. GLOB is not going down subdirectories You're right, I didn't notice GLOB vs GLOB_RECURSE in the diff.
2025-04-01T06:41:13.975645
2019-07-15T21:38:59
468347695
{ "authors": [ "DashaMail", "crsde" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12763", "repo": "crsde/PechkinRb", "url": "https://github.com/crsde/PechkinRb/pull/1" }
gharchive/pull-request
Pechkin turns to Dashamail Hello, sorry for late response and thank you for PR. But it seems there is some issue with requiring version.rb, you "DashaMailRb/version", while version.rb seats in "dashamailrb" dir, details available here: https://travis-ci.org/crsde/PechkinRb/builds/559165352#L261, or just bundle console inside project directory.
2025-04-01T06:41:13.979984
2019-03-02T18:19:27
416425205
{ "authors": [ "felixvf", "ysbaddaden" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12764", "repo": "crystal-lang/crystal", "url": "https://github.com/crystal-lang/crystal/pull/7496" }
gharchive/pull-request
Do not use ThreadLocal $errno because this symbol is GLIBC_PRIVATE. Please provide background for this claim, what historical glibc versions we're breaking, ... @ysbaddaden, when running this script #!/bin/sh echo >demo.cr 'puts "errno=#{Errno.value}."' crystal build demo.cr ./demo LD_DEBUG=bindings ./demo 2>&1 | grep -i errno on a system with glibc-2.26, you may get this output: errno=0. 6798: binding file /lib64/libpthread.so.0 [0] to /lib64/libc.so.6 [0]: normal symbol `errno' [GLIBC_PRIVATE] 6798: binding file /lib64/libpthread.so.0 [0] to /lib64/libc.so.6 [0]: normal symbol `__h_errno' [GLIBC_PRIVATE] 6798: binding file /lib64/librt.so.1 [0] to /lib64/libc.so.6 [0]: normal symbol `errno' [GLIBC_PRIVATE] 6798: binding file ./demo [0] to /lib64/libc.so.6 [0]: normal symbol `errno' [GLIBC_PRIVATE] errno=25. The important aspect is binding file ./demo [0] to /lib64/libc.so.6 [0]: normal symbol `errno' [GLIBC_PRIVATE]. It shows that the compild output references the errno symbol. However, the symbol errno is considered GLIBC_PRIVATE. As of https://groups.google.com/forum/#!topic/uk.comp.os.linux/PX3rstGtZRQ, this means that the the symbol errno is only for the purpose of communicating with other parts of the GNU C library. This means that referencing the errno symbol from programs or libraries not being part of the GNU C library is an error. There are standard packaging tools which enforce that binaries to be packaged do not reference symbols they shall not reference. This means that current Crystal-generated binaries which access Errno (including crystal itself) do not pass this check and therefore cannot be packaged. This pull request fixes that situation.
2025-04-01T06:41:14.012929
2020-06-02T14:40:53
629259756
{ "authors": [ "doodlesbykumbi", "izgeri" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12765", "repo": "cyberark/sidecar-injector", "url": "https://github.com/cyberark/sidecar-injector/pull/35" }
gharchive/pull-request
Add NOTICES.txt @izgeri The go.mod has 32 included deps, but there's only 5 reflected here - what's the difference? The difference is that the other dependencies are indirect. I wonder if we should be including indirect licenses too can you please confirm that none of the indirect-marked deps in go.mod are libraries we manually included, and/or that all indirect-marked deps are tier 2+ dependencies? based on the go docs it looks like modules labeled indirect are either there because a direct dep is missing a go.mod file itself, so its dependencies are recorded - or because you manually specified a different version of a 2nd tier dep than what a dep requires (if I'm reading it correctly) I just want to confirm if we're not going to include the indirect deps (which I think is fine) that they are all indeed coming from deps-of-deps, and aren't direct includes / versions that we manually specified / required @izgeri all the indirect-marked deps are 2nd tier and none where manually specified by us.
2025-04-01T06:41:14.019506
2015-12-14T20:05:32
122119917
{ "authors": [ "dalehenrich" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12766", "repo": "dalehenrich/builderCI", "url": "https://github.com/dalehenrich/builderCI/issues/104" }
gharchive/issue
pharo-5.0 moving to spur vm and wget --quiet -O - get.pharo.org/vm | bash will no longer work tests green
2025-04-01T06:41:14.034002
2015-12-04T22:45:37
120501871
{ "authors": [ "codecov-io", "danthorpe" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12767", "repo": "danthorpe/Operations", "url": "https://github.com/danthorpe/Operations/pull/118" }
gharchive/pull-request
Sort out code coverage Current coverage is 60.42% Merging #118 into development will decrease coverage by -3.46% as of bfd77a8 @@ development #118 diff @@ =========================================== Files 48 41 -7 Stmts 3353 2795 -558 Branches 0 0 Methods =========================================== - Hit 2142 1689 -453 Partial 0 0 + Missed 1211 1106 -105 Review entire Coverage Diff as of bfd77a8 Powered by Codecov. Updated on successful CI builds.
2025-04-01T06:41:14.039540
2017-01-12T14:13:09
200376846
{ "authors": [ "coveralls", "cuducos", "gomex" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12768", "repo": "datasciencebr/jarbas", "url": "https://github.com/datasciencebr/jarbas/pull/114" }
gharchive/pull-request
WORKDIR is necessary to mount local folder Changes Unknown when pulling d43a88e79a3ed1af0e82b4a11d6fc52b33fc973f on gomex:patch-3 into ** on datasciencebr:master**. Thanks, @gomex!
2025-04-01T06:41:14.110510
2016-03-24T00:41:54
143115546
{ "authors": [ "deivid-rodriguez", "sethk" ], "license": "BSD-2-Clause", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12769", "repo": "deivid-rodriguez/byebug", "url": "https://github.com/deivid-rodriguez/byebug/pull/224" }
gharchive/pull-request
Modify test to illustrate issue #223. Superseded by #225, thanks a lot for the useful reproduction @sethk !!
2025-04-01T06:41:14.137118
2021-07-11T13:04:26
941448842
{ "authors": [ "CvX" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12770", "repo": "discourse/discourse-assign", "url": "https://github.com/discourse/discourse-assign/pull/169" }
gharchive/pull-request
DEV: Move assignments from custom fields to a table @ZogStriP The PR is now in a reviewable state. The only question I have is regarding this feature: https://github.com/discourse/discourse-assign/commit/23aa28e2b4c38995d25bd3b71c95a44469f34f3a That's the only thing that's using topic custom fields. I kept it as is, since I don't thing adding support for this edge case to the new Assignment model path is worth it. Alternatively I could also just remove it. 😜 Should I keep it?
2025-04-01T06:41:14.165327
2019-07-16T12:38:31
468630055
{ "authors": [ "diversemix", "will-byrne" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12771", "repo": "diversemix/malcolm", "url": "https://github.com/diversemix/malcolm/issues/3" }
gharchive/issue
Configure hot module reloading for devs Current status: Separated Client Server: [x] Hot Module reloading [x] Typescript Single Package: [ ] Hot Module Reloading (50%) [ ] Typescript Future work [ ] Finish the typescript module for single package. (*) [ ] Discuss whether to use one package or the separated client/server (*) Getting the typescript working on the front end shouldn't be too much work (less than a day) but will require some effort and research to ensure that we are doing it properly. The only reason it wasn't before was because of errors that made no sense cause by lack of understanding of typescript. Thanks for the update... I'm mindful we need to choose the right approach. This sounds like the approach we'll take for a PoC ... but we may want to revisit if this PoC is adopted. /cc @hdrury1
2025-04-01T06:41:14.187304
2015-08-11T15:23:49
100337684
{ "authors": [ "dominikzogg" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12772", "repo": "dominikzogg/vagrant-php", "url": "https://github.com/dominikzogg/vagrant-php/issues/15" }
gharchive/issue
fix: ==> default: Forcing shutdown of VM... It seems there is a problem within debian 8 that ssh-server prevents shutdown. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751636 http://serverfault.com/questions/706475/ssh-sessions-hang-on-shutdown-reboot i suggests to use the v1-ubuntu branch, which uses ubuntu 14.04
2025-04-01T06:41:14.243904
2021-07-03T16:45:57
936289401
{ "authors": [ "Youssef1313" ], "license": "CC-BY-4.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12773", "repo": "dotnet/docs-actions", "url": "https://github.com/dotnet/docs-actions/pull/21" }
gharchive/pull-request
Ignore patterns specified in excludes in docfx.json @IEvangelist I'm going to close for now in favor of your suggested simpler approach: https://github.com/dotnet/docs-actions/pull/25.
2025-04-01T06:41:14.245684
2020-10-29T22:37:32
732709918
{ "authors": [ "JakeRadMSFT", "briacht" ], "license": "CC-BY-4.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12774", "repo": "dotnet/machinelearning-modelbuilder", "url": "https://github.com/dotnet/machinelearning-modelbuilder/issues/1072" }
gharchive/issue
Internal users can easily migrate from TLC to ML.NET Related: https://github.com/dotnet/machinelearning-modelbuilder/issues/1175 Related: https://github.com/dotnet/machinelearning-modelbuilder/issues/1175
2025-04-01T06:41:14.249786
2019-08-23T02:44:29
484302050
{ "authors": [ "JeffHsu79", "dougpuob" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12775", "repo": "dougpuob/cpp-namelint", "url": "https://github.com/dougpuob/cpp-namelint/issues/19" }
gharchive/issue
[Bug] Header file don't check fully, only class will check This issue was fixed with (https://github.com/dougpuob/cpp-namelint/commit/09a2779baba670a6560fec320740fc3de27beacb) commit. Add new test sample file Sample07.cpp and Sample07.h. You can run the test with cppnamelint.py bldgtest.
2025-04-01T06:41:14.257900
2016-01-28T17:18:09
129516087
{ "authors": [ "kie-ci", "psiroky", "sometestuser1234" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12776", "repo": "droolsjbpm/droolsjbpm-build-bootstrap", "url": "https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/pull/137" }
gharchive/pull-request
[DO NOT MERGE] just for testing Can one of the admins verify this PR? Comment with 'ok to test' to start the build. ok to test Can one of the admins verify this PR? Comment with 'ok to test' to start the build.
2025-04-01T06:41:14.259807
2017-05-04T05:09:09
226178998
{ "authors": [ "drcrallen", "gianm" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12777", "repo": "druid-io/druid", "url": "https://github.com/druid-io/druid/pull/4248" }
gharchive/pull-request
Add supervisors to overlord console. @gianm could you add a screenshot of this in action in the PR please? It looks like this: If you don't have any supervisors then the top section doesn't show up.
2025-04-01T06:41:14.267357
2019-11-18T16:06:27
524463450
{ "authors": [ "0xdabbad00" ], "license": "BSD-3-Clause", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12778", "repo": "duo-labs/cloudmapper", "url": "https://github.com/duo-labs/cloudmapper/pull/601" }
gharchive/pull-request
Added parliament support I had the same errors locally when I tried to push this. I don't know if something broke upstream. The error is: File "/home/travis/virtualenv/python3.7.1/lib/python3.7/site-packages/pipenv/vendor/toml/decoder.py", line 187, in loads " Reached end of line.", original, i) toml.decoder.TomlDecodeError: Key name found without value. Reached end of line. (line 18 column 11 char 326) Only related issue I can find is from 2018 (https://github.com/pypa/pipenv/issues/3092) so I'm guessing it is not an upstream problem if no one else on the internet is hitting it.
2025-04-01T06:41:14.268868
2020-08-07T09:04:22
674874833
{ "authors": [ "duythinht", "liamnv" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12779", "repo": "duythinht/dbml-go", "url": "https://github.com/duythinht/dbml-go/issues/8" }
gharchive/issue
Can't parse column with name: type, note @liamnv thank you for report the issue, seen this already fixed at latest update
2025-04-01T06:41:14.386414
2018-10-14T17:57:11
369926762
{ "authors": [ "ekmartin", "markddavidoff" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12780", "repo": "ekmartin/slack-pull-reminder", "url": "https://github.com/ekmartin/slack-pull-reminder/pull/9" }
gharchive/pull-request
Add usernames filter Out of curiosity, what would be a good use case for this? @ekmartin for our use case we have multiple teams using the same repos use this and the repos filter to only remind specific team members about their teams prs to specific repos @markddavidoff: In that case, would it be more useful if you could provide teams and have it filter by that? Team, as in https://github.com/orgs/ORGANIZATION/teams/ TEAMS=team1, team2 -> retrieve team members for team1 and for team2 -> filter PRs by members in those teams Unfortunately we don't use GitHub teams, so for us that doesn't work. That would be neat to add but i like having usernames separate as well. @ekmartin Unfortunately we don't use GitHub teams, so for us that doesn't work. That would be neat to add but i like having usernames separate as well. Note:update doc @ekmartin added teams support in another PR but i think this is still useful such as for members not in a team that still might make prs that need to show up (architect, infosec, etc) @ekmartin any chance these features get in? @markddavidoff: Thanks! Sorry about the late response.
2025-04-01T06:41:14.416534
2021-01-25T19:12:26
793651710
{ "authors": [ "stiartsly", "wakqasahmed" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12782", "repo": "elastos/Elastos.NET.Hive.Node", "url": "https://github.com/elastos/Elastos.NET.Hive.Node/pull/62" }
gharchive/pull-request
Fixed double-quote typo to make the command work when copied/pasted to terminal Thanks, your PR has been accepted and merged into master branch. Thanks, it's a surprise to use. Thanks, your PR has been accepted and merged into master branch. Thanks, it's a surprise to use.
2025-04-01T06:41:14.417626
2016-07-15T03:01:02
165701821
{ "authors": [ "3n-mb", "ckerr" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12783", "repo": "electron/spectron", "url": "https://github.com/electron/spectron/pull/88" }
gharchive/pull-request
Clarifying focusing essence of windowByIndex() Yep, this is better. I'm closing this PR due to lack of response over the past year. @3n-mb, please feel free to open a new PR that addresses the changes that @codebytere suggested. I'd be happy for a fixed PR to be merged.
2025-04-01T06:41:14.418329
2018-04-20T20:29:23
316402033
{ "authors": [ "gustavoteodoro", "luiguild" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12784", "repo": "elemencast/elemencast.github.io", "url": "https://github.com/elemencast/elemencast.github.io/pull/5" }
gharchive/pull-request
Feature/responsive Closing this. This code provided by @gustavoteodoro was used in the final release version. Thankss!!!
2025-04-01T06:41:14.447822
2014-01-06T03:51:18
25084719
{ "authors": [ "chrisclark", "leebrooks0" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12785", "repo": "epantry/django-sql-explorer", "url": "https://github.com/epantry/django-sql-explorer/issues/36" }
gharchive/issue
Python 3 compatibility Hi I am interested in adding Python3 compatibility. My boss said I could spend a day working on it, so before I do this, I just want to check that a) you would be interested in accepting a PR and that b) there are no hidden dragons preventing the upgrade. I am assuming that all I need to do is change to the new exception syntax etc and use some from futures import... as needed? Hey Lee -- this sounds great! Definitely interested in a PR. I don't have experience doing 2->3 ports, so can't speak to the work involved, but there shouldn't be any barriers. Explorer relies on 3 packages (Django, Factory Boy, and SQLparse), all of which are Python3 compatible. Let me know if I can do anything to help. Feel free to ping me<EMAIL_ADDRESS>if you have any questions.
2025-04-01T06:41:14.484549
2021-01-18T20:20:17
788525342
{ "authors": [ "ala-n" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12786", "repo": "exadel-inc/esl", "url": "https://github.com/exadel-inc/esl/pull/11" }
gharchive/pull-request
fix: fix providerName type to allow user to extend default providers :tada: This PR is included in version 1.0.1 :tada: The release is available on GitHub release Your semantic-release bot :package::rocket: :tada: This PR is included in version 1.0.1 :tada: The release is available on GitHub release Your semantic-release bot :package::rocket:
2025-04-01T06:41:14.490605
2016-04-26T19:03:43
151214092
{ "authors": [ "deniaz" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12787", "repo": "eyaleizenberg/react-native-floating-label-text-input", "url": "https://github.com/eyaleizenberg/react-native-floating-label-text-input/pull/5" }
gharchive/pull-request
Expose autoCorrect and autoCapitalize Props Oh wow! Since #4 was not active I wasn't expecting this to happen. Thanks for your work on this, I'm loving it so far. Keep up the good work.
2025-04-01T06:41:14.497023
2019-08-29T09:11:37
486835207
{ "authors": [ "arajkumar", "yzainee" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12788", "repo": "fabric8-analytics/fabric8-analytics-vscode-extension", "url": "https://github.com/fabric8-analytics/fabric8-analytics-vscode-extension/issues/339" }
gharchive/issue
[BUG] Analyzed transitive count also includes unknown transitives https://jira.coreos.com/browse/APPAI-830
2025-04-01T06:41:14.498063
2019-03-25T11:10:33
424844379
{ "authors": [ "centos-ci", "pmacko1", "tradej" ], "license": "CC-BY-4.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12789", "repo": "fabric8-launcher/launcher-documentation", "url": "https://github.com/fabric8-launcher/launcher-documentation/pull/1252" }
gharchive/pull-request
swarm -> thorntail minor refactor Can one of the admins verify this patch? ok to test retest this please
2025-04-01T06:41:14.510541
2015-07-23T23:20:15
96924759
{ "authors": [ "akshatnair", "electrum", "gonewandering", "martint", "milespoindexter", "miniway" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12790", "repo": "facebook/presto", "url": "https://github.com/facebook/presto/pull/3337" }
gharchive/pull-request
First draft of Mongodb plugin This looks awesome! Very complete docs, too! Nit: the preferred capitalization, from looking at their website, seems to be "MongoDB" looks good I've rebased on 0.123-SNAPSHOT and fixed various typos in the document. @electrum, apologies if I'm missing something. Is there a merge plan for this? @gonewandering yes, we're super backlogged processing pull requests, but this is definitely on our list. @martint, awesome. Thanks. Looking forward Hi, I am using this as a plugin, with my current version of PrestoDB, and may have found a bug. When creating a schema for a collection, the connector fails with error whenever the db collection has a field name with a mixture or lower-case and upper-case characters. If I rename the field in the collection to be all lower-case, the queries then work fine. This has to be tested with a MongoDB server hosted on a case-sensitive O/S like Linux. The problem does not happen when I use a MongoDB on OSX, which has a case-insensitive file system. Can you rebase on latest master? Merged, thanks!
2025-04-01T06:41:14.537655
2021-05-19T13:34:22
895454024
{ "authors": [ "Ig0r-M-magic42" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12791", "repo": "fetchify-dev/magento2-ukpostcodelookup", "url": "https://github.com/fetchify-dev/magento2-ukpostcodelookup/pull/3" }
gharchive/pull-request
Add support for php 7.4 @paulmaxwell @quantum-llama @GaborSuranyi can you take a look at this PR as it's a simple one. closing due to inactivity
2025-04-01T06:41:14.546299
2016-09-04T16:25:45
174956887
{ "authors": [ "BenFradet", "codecov-io", "vkostyukov" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12792", "repo": "finagle/finch", "url": "https://github.com/finagle/finch/pull/640" }
gharchive/pull-request
Add tests for the examples Current coverage is 75.31% (diff: 100%) Merging #640 into master will increase coverage by 0.36% Powered by Codecov. Last update f165e43...0cb285a @vkostyukov updated :+1: Thanks @BenFradet! Merging this in!
2025-04-01T06:41:14.575977
2017-12-04T03:25:00
278859317
{ "authors": [ "coveralls", "floere", "yamanaltereh" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12793", "repo": "floere/phony", "url": "https://github.com/floere/phony/pull/394" }
gharchive/pull-request
Fix indonesia spec to support 9 digits Coverage remained the same at 99.398% when pulling c18d70a3e2611e76d4dce8717e15997e93fc23c1 on yamanaltereh:fix_indonesia_spec into 53e6aa2b370623646d05518ef14669d54db15d66 on floere:master. @yamanaltereh Thank you! 🎉 Released in 2.16.1 🚀
2025-04-01T06:41:14.577767
2017-07-13T18:22:22
242788549
{ "authors": [ "sivachandra" ], "license": "BSD-3-Clause", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12794", "repo": "flutter/flutter", "url": "https://github.com/flutter/flutter/pull/11203" }
gharchive/pull-request
Fix style issues introduced by dba29aa0fce684b201c6b03efc73ba607c7b507b Submitting on red flutter build as the underlying issue of the red-ness has been fixed now.
2025-04-01T06:41:15.523446
2015-02-08T06:56:55
56941759
{ "authors": [ "daisuda", "fponticelli" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12795", "repo": "fponticelli/edge", "url": "https://github.com/fponticelli/edge/issues/12" }
gharchive/issue
add pool for SystemProcess/Views Not only need pool. Each time SystemProcess call Views.iterator() will alloc extra a lot memory for for map.keys() and a little memory for anonymous function( hasnext(), next(), holder ) in every loop. And another issue: the Views T is anonymous type ,so in some special platform( e.g. C# ), the generated source codes will slower http://haxe.org/manual/types-structure-performance.html . Can macro detect these anonymous structs and create new type class and replace them? I believe the allocation problem is still there but I made a few tests of classes vs anonymous and I cannot find any real difference in terms of performances.
2025-04-01T06:41:15.534651
2015-10-15T19:16:45
111687985
{ "authors": [ "LeMasque", "soycode", "willscott" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12796", "repo": "freedomjs/freedom-social-wechat", "url": "https://github.com/freedomjs/freedom-social-wechat/issues/8" }
gharchive/issue
User-oriented FAQ for WeChat in uProxy Want to check on this - last I heard, this module is essentially blocked by server-side changes in wechat. If that is the case, then maybe this issue should be revised to "note that this module is blocked in the main landing README." Thoughts? as i understand it, it's not 'blocked', it's just a slightly worse user experience where the signaling messages aren't fully hidden from users. Arguably the same as github where the gists/comments are visible to users as well. On Wed, May 11, 2016 at 2:29 PM, soycode<EMAIL_ADDRESS>wrote: Want to check on this - last I heard, this module is essentially blocked by server-side changes in wechat. If that is the case, then maybe this issue should be revised to "note that this module is blocked in the main landing README." Thoughts? — You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/freedomjs/freedom-social-wechat/issues/8#issuecomment-218595901 Ah yeah, I think I recall the conversation more clearly now, but I also think that uProxy basically considers that a pretty unusable state (since with wechat those messages alert your phone). Do we have any plausible path for fixing that? Left this in an issue raised in the uproxy issue, but I'll just copy here for completeness. @soycode, From when I was last looking, Will is right in that it is a usability issue -- the messages can no longer be sent hidden. However, Within the wechat api (last I checked), users don't have to be alerted of messages; i.e. a message can get to a phone, and a user can see the message if they look, but the phone will not vibrate or make any sounds to alert a user that a new/unread message is available in a thread. The current path is to create a separate thread for uproxy's use with your friend, meaning that all uproxy related information will be isolated into a new "contact" where you won't be alerted of any messages passed through there, while keeping a thread between your original contact uncluttered. Some work has been made in order to accomplish this, but hasn't been taken to completion.
2025-04-01T06:41:15.546788
2016-06-28T16:44:15
162732565
{ "authors": [ "adam-lynch", "wheresrhys" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12797", "repo": "ftlabs/fastclick", "url": "https://github.com/ftlabs/fastclick/pull/481" }
gharchive/pull-request
Advise against fastclick use But there are still a lot of those older browsers in use right? Especially in WebViews on Android for example. The title of this PR is actually a lot bolder than the content of the PR, which is more about advising users of when not to use fastclick. If I had the time I would do a PR to turn off fastclick for modern browsers
2025-04-01T06:41:15.551328
2019-11-18T12:08:30
524325465
{ "authors": [ "LiorRabin", "leonprou" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12798", "repo": "fuseio/fuse-wallet2.0", "url": "https://github.com/fuseio/fuse-wallet2.0/pull/1" }
gharchive/pull-request
on-boarding redux implementation using wallet_core This is the implementation of the onboarding process. I would really appreciate if everyone can go over it and suggest improvements/thoughts/etc. @LiorRabin It looks ok, but as long it's not tied up to UI we can't say how good it fits. @creatix thanks! I will try and run with your additions and see why the 400 error @creatix I've fixed the 400 error, you can continue from here Closing this PR, will open a new branch with #2
2025-04-01T06:41:15.554213
2019-07-23T12:42:58
471674848
{ "authors": [ "jmontleon" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12799", "repo": "fusor/mig-operator", "url": "https://github.com/fusor/mig-operator/pull/14" }
gharchive/pull-request
enable velero in tests For UI and Velero we are using api groups (routes, etc.) that do not exist in kubernetes by default in molecule.
2025-04-01T06:41:15.557573
2015-12-17T21:41:45
122828858
{ "authors": [ "agduncan94", "briandoconnor", "denis-yuen" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12800", "repo": "ga4gh/dockstore", "url": "https://github.com/ga4gh/dockstore/issues/79" }
gharchive/issue
Publish vs. Register... pick a term and be consistent in CLI and Web These are the definitions we will use for each term: Register - add container to Dockstore Publish - make a registered container public (visible to all users) The isregistered and ispublic columns of the tool table don't seem to mean what we think they would mean. ispublic refers to if a repo is public on quay, and is registered is used to see if a container is published on Dockstore (using definition of publish mentioned in my above comment). I believe the isregistered can be removed completely, and ispublic replaced with ispublished. This will prevent future confusion between how we store tools and the way quay stores repos. ispublished will just determine if the tool is published. If a tool is registered on the site then it will be in the DB anyways, so it is a redundant field. I think we're consistent with this nomenclature now, in user-facing interfaces, if not totally in code.
2025-04-01T06:41:15.562524
2017-10-30T09:55:59
269539210
{ "authors": [ "coveralls", "gabrieltanchen" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12801", "repo": "gabrieltanchen/xpns-api", "url": "https://github.com/gabrieltanchen/xpns-api/pull/48" }
gharchive/pull-request
Greenkeeper/sequelize 4.20.1 Coverage remained the same at 98.105% when pulling ce1ff6c64874a50652d8c2cac2847fd09ce48fcd on greenkeeper/sequelize-4.20.1 into 32b8055d267111cba38c6eb763a6a81625cbadd4 on master.
2025-04-01T06:41:15.583805
2018-02-22T17:10:35
299434775
{ "authors": [ "codecov-io", "gbprod" ], "license": "WTFPL", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12802", "repo": "gbprod/algolia-specification-bundle", "url": "https://github.com/gbprod/algolia-specification-bundle/pull/6" }
gharchive/pull-request
Updating deps Codecov Report Merging #6 into master will not change coverage. The diff coverage is n/a. @@ Coverage Diff @@ ## master #6 +/- ## ======================================= Coverage 100% 100% Complexity 8 8 ======================================= Files 4 4 Lines 27 27 ======================================= Hits 27 27 Continue to review full report at Codecov. Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update b0736cb...515b3a4. Read the comment docs.
2025-04-01T06:41:15.584741
2017-04-20T13:08:50
223061856
{ "authors": [ "stroomdev66" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12803", "repo": "gchq/stroom", "url": "https://github.com/gchq/stroom/issues/231" }
gharchive/issue
Merge all internal statistics into 'Volumes', 'Memory' and 'CPU' statistics and drop 'Use%' from volume stats Need to create a new content pack for the new stats that does all rollups but not for 'type'. Need to add removal of all existing statistics to the migration SQL.
2025-04-01T06:41:15.586704
2018-07-06T16:21:52
338997598
{ "authors": [ "generic-github-user" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12804", "repo": "generic-github-user/xkcd-Generator", "url": "https://github.com/generic-github-user/xkcd-Generator/issues/15" }
gharchive/issue
Output values of generator network appear to be limited to a very low range, causing a darkened image to be generated All activation functions are set to relu.
2025-04-01T06:41:15.605977
2020-11-11T08:49:11
740584397
{ "authors": [ "lobsterkatie", "untitaker" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12805", "repo": "getsentry/sentry-python", "url": "https://github.com/getsentry/sentry-python/pull/919" }
gharchive/pull-request
fix: Remove duplicate data from sampling context Can we then remove parent_sampled from within the to_json implementation entirely? I don't think we need to send this to the server at all? Is it being sent to the server, though? The only place I see us calling to_json() (other than where I call it in start_transaction()) is here: https://github.com/getsentry/sentry-python/blob/cc08a6bed116e09db41c712c20ab63eb0a839e41/sentry_sdk/tracing.py#L537-L541 where it's being called on spans, not including self, meaning it wouldn't get called on a transaction. EDIT: Yeah, I checked. When I threw a pdb into my transport's _send_envelope method, here's what I got: (Pdb) pp envelope.items[0].payload.json {'_meta': {'...'}, 'contexts': {'runtime': {'...'}, 'trace': {'description': None, 'op': None, 'parent_span_id': None, 'span_id': '979d39004e00edcc', 'trace_id': '5a4fc60521604bfea8d89162ce497dc4'}}, 'environment': 'dev', 'event_id': 'fab597c687f74d9d9b47dffc57dc237b', 'extra': {'secret_word': None, 'sys.argv': ['/Users/Katie/Documents/Sentry/test-apps/flask/server.py'], 'things': 'stuff'}, 'platform': 'python', 'request': {'...'}, 'sdk': {...'}, 'server_name': 'test-server', 'spans': [], 'start_timestamp': '2020-11-12T17:50:33.731546Z', 'tags': {'dogs': 'rule', 'dogtag': 'yes'}, 'timestamp': '2020-11-12T17:50:33.731875Z', 'transaction': 'dogpark', 'type': 'transaction', 'user': {'id': '122112', 'is_silly': True, 'username': 'maiseythedog'}} So I think we're safe. Ok right. Do you agree though that we can remove the field from the to_json return value? Ah, yeah, that would do it, too, at which point the entire PR becomes removing this line: https://github.com/getsentry/sentry-python/blob/c9120691c360336e7ef4767cafa14c7d7a7d8226/sentry_sdk/tracing.py#L561 Works for me. (Looking at it now, I'm not actually sure why I felt like it needed to be there in the first place... Oh - I know. I was trying too hard to copy the JS implementation, which I now actually wish I could go back and redo more like the way I ended up doing it in Python... Anyway, yeah, let's just take out that line.)
2025-04-01T06:41:15.637247
2021-07-27T09:38:15
953695220
{ "authors": [ "codecov-commenter", "glynpu" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12806", "repo": "glynpu/espnet", "url": "https://github.com/glynpu/espnet/pull/6" }
gharchive/pull-request
Fix codev Codecov Report :exclamation: No coverage uploaded for pull request base (master@e60d178). Click here to learn what that means. The diff coverage is n/a. @@ Coverage Diff @@ ## master #6 +/- ## ========================================= Coverage ? 80.66% ========================================= Files ? 357 Lines ? 30737 Branches ? 0 ========================================= Hits ? 24795 Misses ? 5942 Partials ? 0 Continue to review full report at Codecov. Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update e60d178...557290b. Read the comment docs.
2025-04-01T06:41:15.642459
2021-03-05T18:04:34
823305135
{ "authors": [ "BenjaminPrieur", "vmihailenco" ], "license": "bsd-2-clause", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12807", "repo": "go-redis/redis", "url": "https://github.com/go-redis/redis/pull/1685" }
gharchive/pull-request
Add ZMScore cmd @BenjaminPrieur thanks for the PR. I have left one comment, but otherwise this looks good. @vmihailenco I did the changes you mentioned Thanks :+1:
2025-04-01T06:41:15.701078
2021-06-02T08:50:25
909256587
{ "authors": [ "chiafullo", "dodgejesse", "ethansdyer", "guygurari" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12808", "repo": "google/BIG-bench", "url": "https://github.com/google/BIG-bench/pull/428" }
gharchive/pull-request
Added commonsense probe @googlebot I signed it! @dodgejesse We are now requesting that task authors please include an explicit section in the README.md file called "data source", listing exactly where you got your data from (or explicitly state that you made it up yourself). Many thanks! @StellaAthena are one of the assigned reviewers for this task. Please provide feedback and be sure to notify me with a formal accept or does not meet criteria by Tuesday June 22 (if you have not already done so). @nayeon7lee are one of the assigned reviewers for this task. Please provide feedback and be sure to notify me with a formal accept or does not meet criteria by Tuesday June 22 (if you have not already done so). The amount of tasks we received this round is tremendous. With so many tasks to review we have decided to extend the review period to Tuesday, June 29. Reviewers: if the submitter has made revisions please be sure to notify me with a formal ”accept” or ”does not meet criteria” by Tuesday, June 29 (if you haven't already done so). this is an automated message Hello, I just saw the suggested change to update the README.md file with an explicit section about where we got the data. The README.md does say that our "dataset [was] built from ATOMIC (Sap et al., 2019), a commonsense KB", but I'd be happy to add that section to the README.md, as long as it's not too late. I don't see a review (or "accept" or "does not meet criteria") yet? @dodgejesse This task dis not yet have any reviews (apologies!) so I will do a late review. My main comment is regarding correctness: I don't understand most of the sentences in the task. Here are a few examples of labelled sentences I find confusing: PersonX inherits from PersonX's mother and as a result, everyone else die PersonX sees PersonX's sister and as a result, everyone else greets PersonX holds in PersonY's hand and as a result, everyone else is hurt PersonX holds in PersonY's hand and as a result, everyone else cries PersonX takes PersonY's places and as a result, everyone else smile Regarding the data source section: Yes, please add this section to the readme. This will make it easy for us to find this information when we scan through tasks. @dodgejesse Hi Jesse, I am meta-reviewing this task. I wanted to follow up and see if you saw Guy's question and if you are still open to revising the task for the benchmark? Best, Ethan Hi, thanks for the feedback! I've added a section to the README.md file which explicitly states where we got the data. (This task is ATOMIC (Sap et al., 2020) that we transformed into a probing task). About the data quality: ATOMIC is known to be pretty noisy on its own, but the original authors were hesitant to try to filter the annotations too much as it was one of the first large-scale commonsense datasets created (we don't yet have good annotation schemes for commonsense tasks). The examples you point out above are at least somewhat noisy because of the annotations from the Mechanical Turkers for ATOMIC. For example, the first instance you show, "PersonX inherits from PersonX's mother and as a result, everyone else die" is a natural language sentence built from the annotation in ATOMIC {Event: "PersonX inherits from PersonX's mother", Relation: "Others_then", Annotations: {"none", "die", "leave earthly goods behind"}} You can see this example in ATOMIC here: https://mosaickg.apps.allenai.org/kg-atomic2020/?l=PersonX inherits from PersonX's mother Our filtering removed "none" and "leave earthly goods behind", and only kept "die" (as it's a single token, thus appropriate for the cloze-style task). This task can be viewed as a probe for the ATOMIC dataset, which does have some noise; as described in the README, we filtered it in a number of ways (including removing annotations like "none") to make it more grammatical and coherent. We hope the task is still useful at capturing some notion of commonsense. Hi Jesse, Digging into the examples a little bit, I empathize with the concern that at present many are ambiguous. For example here is a typical contiguous block: {"input": "PersonX gives birth to the PersonY and as a result, everyone else is ", "target": ["washed"]}, {"input": "PersonX regards PersonY with eyes and as a result, everyone else ", "target": ["laughs"]}, {"input": "PersonX sees PersonY daughter and as a result, everyone else ", "target": ["waves"]}, {"input": "PersonX amends PersonY act and as a result, everyone else is ", "target": ["scolded"]}, Looking at the ATOMIC graph browser, it looks like though noisy, the full graph structure helps to render examples a bit less ambiguous. Some examples look like the noise is enhanced by subsetting to a specific relation. i.e. in the example PersonX gives birth to the PersonY and as a result, everyone else is, the browser results show that the Others then category results are not great, and in particular are not well suited to being rephrased as everyone else is In other examples, it looks like the restriction to only single word responses enhances the noise. For example in {"input": "PersonX makes PersonY escape and as a result, everyone else ", "target": ["smiles"]}, here, the other multi-word examples (eg Gets away from danger), though not perfect, help strengthen the signal. If you are up for it, I would suggest the following changes: Include single and multi word targets, rather than filtering to single word. Convert the task to multiple choice, rather than generative, where all target's present in the graph give a correct score of 1, and negative examples with score 0 are introduced. These could be taken, for instance, from the targets from other relations. Additionally, if there was some way to do grammatical sanitization of the results, that would be awesome! For instance there are many examples like: {"input": "PersonX plays PersonY's heart and as a result, everyone has ", "target": ["marriage"]} -- though I understand this might be a headache and was not done in the initial work. Thanks again for the task submission! Best, Ethan Hi Jesse, We are trying to finalize all benchmark tasks. Please address the above comments by Monday Aug 16 to be able to be included. Thanks!
2025-04-01T06:41:15.706111
2017-12-12T10:19:51
281328924
{ "authors": [ "jskeet", "mihir1208" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12809", "repo": "google/google-api-dotnet-client-samples", "url": "https://github.com/google/google-api-dotnet-client-samples/issues/20" }
gharchive/issue
Google Calender reminder setting not set for attendees Please give a lot more detail than this, otherwise we'll be unable to help you. Please: Show the code you're using Describe exactly what you've observed vs what you expected to observe var remind = new Event.RemindersData() { UseDefault = false, Overrides = new EventReminder[] { new EventReminder() { Method = "popup", Minutes = 2880 }, } }; i have created a event with reminder before 2 days. but on the attendees calendar the reminder time shows before 30 minutes To be honest, that's what I'd expect anyway - a reminder is a personal thing, I wouldn't expect you to be able to change the reminder for any calendar other than your own. In the resource description it specifically says "Information about the event's reminders for the authenticated user." To put it another way - have you tried doing this in the Calendar web UI? Are you able to set other people's reminders that way? No i can't do it from Calendar web UI Okay, it sounds like this is working as intended then. I'll close this issue now. Please note that this repo is really for the .NET client library specifically; general API questions would be better posted on Stack Overflow.
2025-04-01T06:41:15.707681
2016-02-02T10:57:22
130646792
{ "authors": [ "bshaffer", "thilanga" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12810", "repo": "google/google-api-php-client", "url": "https://github.com/google/google-api-php-client/pull/825" }
gharchive/pull-request
Fixed Opening brace issue to fix php 5.4 build issue This class gets autogenerated. You could add this method to Google\Model, which is the subclass where the property comes from. Can you explain why you need to access the model data here?
2025-04-01T06:41:15.727669
2020-06-10T15:14:22
636333062
{ "authors": [ "grakkit" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12811", "repo": "grakkit/grakkit", "url": "https://github.com/grakkit/grakkit/issues/5" }
gharchive/issue
Enable the NodeJS environment if possible Access to the NodeJS environment has been deemed impossible via standard means. Experimental means will not be pursued.
2025-04-01T06:41:15.753730
2017-04-25T22:31:18
224291215
{ "authors": [ "MakMukhi", "ctiller", "dgquintas", "jtattermusch", "yang-g" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12812", "repo": "grpc/grpc", "url": "https://github.com/grpc/grpc/pull/10848" }
gharchive/pull-request
Fix for cmake test failures asan c failure due to know issue #10169 5aa4158 does not look like your commit, can you get rid of it? This fix is for a failure in portability test linux aggregate_tests.run_tests_c++_linux_dbg_native_default_cmake No issue was created for this. The asan failure in this PR is due to another known issue #10169 Opened another PR since this had incorrect commit messages. @MakMukhi and what PR is that? @MakMukhi, nit: you could have done git rebase -i upstream/master and force push to this branch to reuse this PR. What is the number of the new PR? Guessing https://github.com/grpc/grpc/pull/10869 If it's not solved can we figure out how to rollback?
2025-04-01T06:41:15.765814
2017-05-07T17:05:18
226876037
{ "authors": [ "EPashkin", "GuillaumeGomez" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12813", "repo": "gtk-rs/sys", "url": "https://github.com/gtk-rs/sys/pull/49" }
gharchive/pull-request
Update all versions 👍 Thanks IMHO If you remove version from git dependencies it can even build without error (cairo-rs-sys) I'll start merging cairo's PR then restart tests in here and we'll go up like this. ;) Your way will be same errors for other git dependencies. I merged cairo (I'll restart CI for it later). But as error be in my way too as it build against gtk with versioned dependencies Oh damn, we need to merge everything to test! Well, then let's merge... Hm, I don't see gdk PR but see update branch in your repo :-. I confirm that examples now builds locally I restarted all builds, they seem to succeed as well. :)
2025-04-01T06:41:15.775754
2020-10-06T04:30:14
715328991
{ "authors": [ "FrankHossfeld" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12814", "repo": "gwtproject/gwt-safehtml", "url": "https://github.com/gwtproject/gwt-safehtml/pull/12" }
gharchive/pull-request
update description of SafeCSS & SafeHTML pom Close PR due to the fact, that the description is already updated
2025-04-01T06:41:15.777199
2015-10-06T19:22:53
110081226
{ "authors": [ "paked", "zachlatta" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12815", "repo": "hackclub/meta", "url": "https://github.com/hackclub/meta/issues/191" }
gharchive/issue
Install Steward plugin to record meeting logs :+1: Closing since we haven't been having formal meetings on IRC.
2025-04-01T06:41:15.780340
2018-03-28T22:40:54
309557912
{ "authors": [ "mckinneybock", "znmeb" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12816", "repo": "hackoregon/neighborhoods-2018", "url": "https://github.com/hackoregon/neighborhoods-2018/issues/2" }
gharchive/issue
Geocoding Addresses I've got this coded - how do you want to deploy it? Do you want to geocode a batch of addresses up front and serve the results or do you want to geocode live in the front end / API? Hi! Thanks for commenting. I was testing issue notes with Lynn, and so I'm not the only one looking for a solution to this. It would be good to have a discussion at our Thursday meeting about how to proceed. I can't come to the meeting but you can hit me up in Slack most of the day. Thanks!
2025-04-01T06:41:15.821082
2019-08-22T09:04:19
483863777
{ "authors": [ "CraigBerlin", "ninok" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12817", "repo": "heremaps/harp.gl", "url": "https://github.com/heremaps/harp.gl/pull/739" }
gharchive/pull-request
Update GettingStartedGuide.md Either we need to update it from time to time, or we just put above a sentence saying something like You need to run an installation command similar to the one shown below, although the exact version of three.js might vary Could we tell them to run: $ npm view @here/harp.gl dependencies
2025-04-01T06:41:15.863180
2021-07-28T19:36:52
955175081
{ "authors": [ "coveralls", "pablo1v" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12818", "repo": "hitechline/reactools", "url": "https://github.com/hitechline/reactools/pull/179" }
gharchive/pull-request
Feat: withProps Pull Request Test Coverage Report for Build<PHONE_NUMBER> 10 of 10 (100.0%) changed or added relevant lines in 3 files are covered. No unchanged relevant lines lost coverage. Overall coverage increased (+0.2%) to 94.988% Totals Change from base Build<PHONE_NUMBER>: 0.2% Covered Lines: 304 Relevant Lines: 308 💛 - Coveralls
2025-04-01T06:41:15.884811
2016-05-30T20:17:59
157552183
{ "authors": [ "Witaminer", "therealklanni" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12819", "repo": "hubot-scripts/hubot-ingress", "url": "https://github.com/hubot-scripts/hubot-ingress/pull/55" }
gharchive/pull-request
Added Aegis Nova Badge Thanks! Published v0.19.1 Forget to add Devra 2016 and Chapeau 2016 badges. Added now and pull request sent.
2025-04-01T06:41:15.898682
2021-05-18T15:54:40
894532504
{ "authors": [ "mafintosh", "robertkowalski" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12820", "repo": "hypercore-protocol/hyperbee", "url": "https://github.com/hypercore-protocol/hyperbee/pull/31" }
gharchive/pull-request
docs: small typo fixes Robert to the rescue! haha On Tue, 18 May 2021 at 18:08, Mathias Buus @.***> wrote: Robert to the rescue! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
2025-04-01T06:41:15.918908
2021-01-31T13:15:56
797708838
{ "authors": [ "ibrahimnamdar" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12821", "repo": "ibrahimnamdar/CovidAnalyzer", "url": "https://github.com/ibrahimnamdar/CovidAnalyzer/issues/8" }
gharchive/issue
Create a use-case diagram Created a use-case diagram in the wiki Created a use-case diagram in the wiki
2025-04-01T06:41:15.934715
2021-05-19T03:17:06
894947856
{ "authors": [ "aruniverse", "calebmshafer" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12822", "repo": "imodeljs/extension-sample", "url": "https://github.com/imodeljs/extension-sample/pull/16" }
gharchive/pull-request
Update dependencies are we going to convert this to just be a build time extension? are we going to convert this to just be a build time extension? @aruniverse I was thinking about that when updating this yesterday. I think it makes sense to do so. I'll hopefully get to it in the next few days.
2025-04-01T06:41:15.946760
2018-08-04T18:11:54
347637837
{ "authors": [ "bbigras", "inejge", "masonk", "nevi-me", "quadrupleslap" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12823", "repo": "inejge/ldap3", "url": "https://github.com/inejge/ldap3/issues/29" }
gharchive/issue
tokio-core is deprecated. Any progress on this? Just a short note (as I otherwise don't have the time to work on this library): moving away from tokio_core to tokio would have to account for the use of the former in tokio_proto, also deprecated but unfortunately the foundation of ldap3. I don't see a straightforward way to excise tokio_proto without a massive rewrite of this crate's internals. Yes, I was realizing that last night when I was trying to do the migration myself. Hi @inejge , I had a go at trying to port to tokio today, and have made some progress. It looks like the blocker is tokio_proto more than anything, for the multiplex tcp connections. I'm due to release a program that will be deployed at clients in the coming days, so I don't have a choice but to "make it work". I'm going to try something from the tower ecosystem and see if it works. I'll provide feedback in a few days Right, the tokio_proto multiplexer is the tricky part, and having it available is what made initial development comparatively straightforward. For your immediate problem, I'd recommend starting a dedicated thread for LDAP connection(s), with its own tokio_core event loop, and communicating with the rest of the system via oneshot/mpsc channels. I believe these can work across tokio flavors. I found https://github.com/red75prime/tokio-proto/commit/cd1af828791fcd60dc518eb713a53d00e9aacf91, which while not ideal, still allowed me to get the crate to build. I just got it to build now actually. With the port to Tokio 0.2, this can now be closed. Thanks @inejge
2025-04-01T06:41:15.957501
2015-06-10T23:55:21
87148775
{ "authors": [ "inodb", "raylim" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12824", "repo": "inodb/sufam", "url": "https://github.com/inodb/sufam/pull/4" }
gharchive/pull-request
fix deletions being set as the correct type Thanks! Can't believe the tests didn't catch that. I'll have to add some better ones.
2025-04-01T06:41:15.960327
2021-04-18T19:57:20
860750251
{ "authors": [ "erikd", "kderme" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12825", "repo": "input-output-hk/cardano-db-sync", "url": "https://github.com/input-output-hk/cardano-db-sync/pull/584" }
gharchive/pull-request
fix rollbacks Rebased, squashed, and improved commit message from @kderme . Still testing this. Will keep on rebasing as things are merged to master. Have had one crash running this branch (following the chain). I was not able to see the actual error because it kept on retrying and failing and the real error was not in the scrollback. Ok, this thing crashed again: [2021-04-29 02:07:11.39 UTC] runDBThread: DbInsertException "Tx: 32" ( SqlError {sqlState = "23503" , sqlExecStatus = FatalError , sqlErrorMsg = "insert or update on table \"tx\" violates foreign key constraint \"tx_block_id_fkey\"" , sqlErrorDetail = "Key (block_id)=(5899482) is not present in table \"block\"." , sqlErrorHint = "" }) Something is really wrong in this PR. I highly suspect this is due to trying to implement rollbacks at the source end of the TBQueue instead of the destination end. Indeed there is a race condition. drainQueue is not an good enough check to access the db from the main thread. I'm thinking about changing or adding a new lock, but I havent found a good solution yet.
2025-04-01T06:41:15.961449
2020-05-12T18:25:49
616865567
{ "authors": [ "ArturWieczorek", "oneEdoubleD" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12826", "repo": "input-output-hk/cardano-graphql", "url": "https://github.com/input-output-hk/cardano-graphql/pull/177" }
gharchive/pull-request
Add data parity tests for epoch details @oneEdoubleD Would you mind refactoring your tests to follow this pattern? Yep! I agree, this is better. I'll do it the next time I look at GraphQL :)
2025-04-01T06:41:15.968686
2017-03-23T22:11:12
216588011
{ "authors": [ "rivernate", "westonkd" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12827", "repo": "instructure/lti2_reference_tool_provider", "url": "https://github.com/instructure/lti2_reference_tool_provider/pull/6" }
gharchive/pull-request
Use OAuth2 for tool proxy registration Just wanted to make sure you saw my comment from yesterday morning @rivernate, do we want to merge this before all the features are in Canvas? I know you mentioned adding the security profile and we also need to add support for requesting an access token using the reg key. I have the canvas changes pending right now. We can test this and those changes together.
2025-04-01T06:41:15.970253
2019-02-11T21:41:37
408989451
{ "authors": [ "ifilippov" ], "license": "BSD-3-Clause", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12828", "repo": "intel-go/nff-go", "url": "https://github.com/intel-go/nff-go/issues/552" }
gharchive/issue
burstSize should be configurable (can't be built now) Done by https://github.com/intel-go/nff-go/commit/bae0b7303f9c188348d98d309b6d3c0410c27437
2025-04-01T06:41:15.983375
2016-07-13T10:07:33
165284431
{ "authors": [ "jirikuncar", "tiborsimko" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0000.json.gz:12829", "repo": "inveniosoftware/invenio-config", "url": "https://github.com/inveniosoftware/invenio-config/pull/12" }
gharchive/pull-request
installation: testing support for PyPy Are all our dependencies PyPy friendly already? If not, we'd be introducing N new unnecessary CI jobs in the testing matrix, which is kind of going against the spirit of https://github.com/inveniosoftware/invenio/issues/3647. Note that that PyPy testing seems to take 2x more time on Travis when compared to CPython: https://travis-ci.org/inveniosoftware/invenio-config/builds/144410515 Note that that PyPy testing seems to take 2x more time on Travis when compared to CPython The pip cache was not initialized. Are all our dependencies PyPy friendly already? I'm trying to find out by starting with base packages. Can you repush with allow_failures for Travis CI?