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-01T04:36:13.103676
2016-10-18T22:17:17
183817616
{ "authors": [ "apurtell", "dimaspivak" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12958", "repo": "clusterdock/framework", "url": "https://github.com/clusterdock/framework/issues/4" }
gharchive/issue
Add an option to 'nuke' that also removes all volumes This has been done; volumes are automatically removed when the containers they're created for are removed.
2025-04-01T04:36:13.105091
2016-06-07T19:32:26
159005365
{ "authors": [ "cmaclell", "eharpste" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12959", "repo": "cmaclell/apprentice_learner_api", "url": "https://github.com/cmaclell/apprentice_learner_api/issues/5" }
gharchive/issue
Create LogicalWhenHow that utilizes focus of attention. @cmaclell do you remember the context on this one? I think we are thinking of basically doing this to support authoring and basically re-constructing classic SimStudent. Would you mind if I close this placeholder? You can close the placeholder. The idea was to be able to provide FOA to the agent, so that it could only search for how explanations using information the trainer thought was relevant. Or some variation of this idea. I'm going to consider this redundant with #25 and close this one.
2025-04-01T04:36:13.109271
2021-04-21T07:13:11
863524534
{ "authors": [ "cmougan", "rohaan2614", "sunayana" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12960", "repo": "cmougan/WRI_WellBeing_Data_Layer", "url": "https://github.com/cmougan/WRI_WellBeing_Data_Layer/issues/10" }
gharchive/issue
[DOC] : Add documentation to the dssg directory README on the organization of code. With this you mean describe in a paragraph all the sections? Hey @sunayana , I see this is self-assigned but can I help with this? (I don't fully understand the issue description though, a little clarification will help :) ) Hi @rohaan2614 thanks, that would be great, if you could do that, I would have done it next week otherwise. It is more about creating a documentation for the code, something along the lines https://developer.lsst.io/python/numpydoc.html And then compile it to markdown files or rst files. This would mean to go through the code in the dssg/dataio folder mainly and add comments, something along these lines """Sum numbers in an array. Parameters ---------- values : iterable Python iterable whose values are summed. Returns ------- sum : `float` Sum of ``values``. """ I would look into it Monday or Tuesday next week otherwise. I will add some on Sunday. You can review them on Monday or whenever you have time. Just to confirm, this is the directory of the codes, right? I will add some on Sunday. You can review them on Monday or whenever you have time. Just to confirm, this is the directory of those codes, right? Yes that is the directory. Thanks!
2025-04-01T04:36:13.138714
2018-07-08T14:05:59
339228579
{ "authors": [ "cockroach-teamcity", "jseldess" ], "license": "CC-BY-4.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12961", "repo": "cockroachdb/docs", "url": "https://github.com/cockroachdb/docs/pull/3364" }
gharchive/pull-request
Update 2.1 full sql grammar diagram This change is  http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/c6f5605567a0c1ec84414829552d4810132832f8/
2025-04-01T04:36:13.143020
2020-10-01T04:11:44
712460504
{ "authors": [ "WhoIsSethDaniel", "cocopon", "nganhkhoa" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12962", "repo": "cocopon/vaffle.vim", "url": "https://github.com/cocopon/vaffle.vim/pull/55" }
gharchive/pull-request
Preserve alternate file This should resolve issue #49 Oh my god, I don't even know keepalt exists. Thanks. Could you tell me a test case to be fixed by this change? I tried a scenario below in main branch and it seems to be working fine without your change: :e foo.txt :e bar.txt " Open Vaffle :Vaffle " show alternate file :b# " it should show bar.txt If you, say, launch Vaffle and then go up a directory the alternate file becomes incorrect. E.g.: :e alternate.file :Vaffle :ls! 1 # "alternate.file" line 1 2 %a- "vaffle://0//home/seth/tmp" line 1 h :ls! 1 "alternate.file" line 1 2 %a- "vaffle://1//home/seth" line 6 3u# "vaffle://0//home/seth/tmp" line 1 And now the alternate file is the previous directory you were viewing and not the file that was being edited prior to entering Vaffle. This is unintuitive and not in keeping with other, similar tools such as netrw or dirvish. This PR preserves the most recently edited file as the alternate file. I understand, thank you for detailed explanation! Added a test case and merged. Thank you for merging. I really like Vaffle!
2025-04-01T04:36:13.186948
2020-12-09T19:10:41
760596469
{ "authors": [ "conda-forge-linter", "felixchenier" ], "license": "BSD-3-Clause", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12963", "repo": "conda-forge/limitedinteraction-feedstock", "url": "https://github.com/conda-forge/limitedinteraction-feedstock/issues/3" }
gharchive/issue
@conda-forge-admin,please add bot automerge Hi! This is the friendly automated conda-forge-webservice. I just wanted to let you know that I added bot automerge in conda-forge/limitedinteraction-feedstock#4.
2025-04-01T04:36:13.194442
2016-12-03T19:32:47
193308843
{ "authors": [ "conda-forge-linter", "jakirkham", "jjhelmus", "jschueller", "ocefpaf" ], "license": "BSD-3-Clause", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12964", "repo": "conda-forge/pyside-feedstock", "url": "https://github.com/conda-forge/pyside-feedstock/pull/5" }
gharchive/pull-request
Build long prefix package using conda-build 2.x 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. Sorry, the dependencies required to build a long prefix package for this feedstock are not yet available. Specifically curl needs to be re-build so that cmake can use used in a long prefix environment. I'm closing this issue for the time being. Once the long prefix version of the needed dependencies are ready I will re-open this PR or create a new PR. The linux long-prefix build still needs some additional packages rebuild (glib and harfbuzz at minimum). I think this can be ignored for the time being. I'll close and re-open this when those packages are ready. glib and harfbuzz at minimum glib is ready and I have a PR almost ready for harfbuzz. I'm only waiting for CircleCI to get back online. oh, I wondered why circleci wasn't starting, they do not mention the issue on their status page. xref: https://github.com/conda-forge/status/issues/30 Closing, will create a new PR when ready. Replaced with PR ( https://github.com/conda-forge/pyside-feedstock/pull/11 ).
2025-04-01T04:36:13.201401
2017-04-29T21:09:14
225285420
{ "authors": [ "bollwyvl", "conda-forge-linter" ], "license": "BSD-3-Clause", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12965", "repo": "conda-forge/whichcraft-feedstock", "url": "https://github.com/conda-forge/whichcraft-feedstock/pull/5" }
gharchive/pull-request
bump to 0.4.1, Re-rendered with conda-smithy 2.3.0 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-01T04:36:13.208122
2017-05-04T04:16:52
226174144
{ "authors": [ "bigkraig", "coveralls" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12966", "repo": "coreos/alb-ingress-controller", "url": "https://github.com/coreos/alb-ingress-controller/pull/82" }
gharchive/pull-request
Fix the missing condition mentioned in issue #81 Coverage remained the same at 0.72% when pulling 38ab5dd1a0810dcc7dd984a130e336a4fe7521cc on 81-fix into d9792d4475978bce5b869b596c6c16e138529647 on master.
2025-04-01T04:36:13.230890
2018-09-16T18:29:50
360665389
{ "authors": [ "cosmic-cortex", "nikolay-bushkov" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12967", "repo": "cosmic-cortex/modAL", "url": "https://github.com/cosmic-cortex/modAL/issues/22" }
gharchive/issue
Refactoring documentation Once you decide which style for docstrings to use, I can start refactoring. A look at this http://www.sphinx-doc.org/en/master/usage/extensions/napoleon.html page shouldn't take more than 10 minutes. I took a look, I think we should follow the NumPy style. The reason for this is that the types of arguments can be lengthier (for instance Union[modAL.models.BaseLearner, modAL.models.BaseCommittee]), which is easier to read in the NumPy format. Another important detail is that I have decided to move the repository to an organizational GitHub account (https://github.com/modAL-python). As a first step, I would like to move the website and API documentation first from the modAL repository itself to a separate one (https://github.com/modAL-python/modAL-python.github.io). I'll add you as a collaborator to this organization, so we can work there together. Considering docstrings style, if there is type annotation (that I propose to use) in function signatures, then it is redundant to specify types also in docstrings (it will lead to inconvenient duplications which eventually result in inconsistency, http://www.sphinx-doc.org/en/master/usage/extensions/napoleon.html#type-annotations). Considering website, both scikit-learn and PyTorch use Sphinx to build html-pages for their websites, doing commits with these artifacts to special repositories. So, after every change in your documentation sources, you should not forget to rebuild the doc and make a commmit to this special repo. You definetely should set up CI step for this, for instance in Travis. However, readthedocs suggests building documentation automatically after each commit to the repo with sources. So, if you don't think of making quite a rich website it is possible to use a simpler solution (i.e. readthedocs). What I plan is to combine the modAL tutorial page (https://cosmic-cortex.github.io/modAL/) with the readthedocs API reference (https://modal-python.readthedocs.io/en/latest/) to a single website in the style of the PyTorch documentation. So, I would like to get rid of readthedocs completely and use Sphinx only to build the website. I'll go ahead and try to set this up. I have set up the new website at https://modal-python.github.io, the old website redirects from here also. The new one uses Sphinx instead of Jekyll. See https://github.com/modAL-python/modAL-python.github.io/compare/notebooks_rendering?expand=1 for the demonstration of my suggestion on dealing with jupyter notebooks (make clean && make html locally). Every time documentation is built, notebooks are executed, and it is an additional way of testing and consistency checking. This kind of deduplication could become even more efficient if sources for the doc and the code itself are stored in a single repo (i.e. main modAL repo). I still don't understand why aren't you go with ReadTheDocs instead of GitHub Pages? RTD provides a very convenient way of triggering documentation build with webhooks from GitHub. RTD allows for better URLs (without 'build/html' in it). RTD provides hosting of several versions of the doc simultaneously... Thanks, awesome! This GitHub pages hosted website is not a final solution. The thing is, I am not very familiar with neither Sphinx nor RTD, so in order to keep the problems manageable, I focused on converting the previous website to Sphinx. Since RTD uses Sphinx, it was the logical thing to do. I'll set up the current website on RTD soon in the main repository, then we add the API reference generated automatically from the docstrings, and finally the modAL main repository can be moved to the organizational account. Ok, I have set up the new RTD site, check it out! I have two issues however. I was unable to find how to link to pages build from a Jupyter notebook from an external page. Since I was unable to link documents from directories higher than the docs, I copied the Jupyter notebooks from the examples folder to docs/source/content/examples. Do you have a solution in mind for these? Perhaps you have encountered them before. If you have some progress in refactoring the docstrings, let me know! Now it should be easy to include the documentation in the RTD site. Yeah, I also faced this problem... my solution was to use '.' instead of 'source' for .rst files... so docs/examples/my_notebook.ipynb looks more discoverable if you surf directly on GitHub. Moreover, .rst files could be partially rendered by GitHub also. I haven't started docstrings refactoring yet. Since it is semi-automatic task, I will try to make pull request tomorrow.
2025-04-01T04:36:13.252194
2015-01-03T20:17:09
53314188
{ "authors": [ "Dakta", "agentlame", "creesch" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12968", "repo": "creesch/reddit-moderator-toolbox", "url": "https://github.com/creesch/reddit-moderator-toolbox/issues/422" }
gharchive/issue
Move mod macros out of beta Can we thing of any features they need? One day I'd like to add user-configurable actions to take when sending a macro (IE: also remove the comment it is in reply to, maybe make auto-distinguish a per-macro action, etc) But for now, they aren't all that complex. I recall a single report of them working across subs, but can't confirm it. If we can't confirm it before 3.1, lets just drop them out. I'd love it if we somehow could trick RES into adding their markdown support stuff (Did talk a little bit with @andytuba about this) but that is not a must have. I'd also love it if they inserted the comment you just made... we have the template for comments so it might even be possible. For what we have now I think they are production ready. I still think macros should hijack the comment box, but :P
2025-04-01T04:36:13.253352
2021-03-25T15:13:45
841031622
{ "authors": [ "oberstet" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12969", "repo": "crossbario/autobahn-python", "url": "https://github.com/crossbario/autobahn-python/pull/1479" }
gharchive/pull-request
expand wamp auth scram and xbr argon2/hkdf this PR is supposed to add all the helper functions we need for this:
2025-04-01T04:36:13.259790
2017-07-01T16:29:11
239958833
{ "authors": [ "KKyang", "csantosbh" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12970", "repo": "csantosbh/gdb-imagewatch", "url": "https://github.com/csantosbh/gdb-imagewatch/pull/10" }
gharchive/pull-request
Change some GL settings to fit OpenCV data structure Hi @KKyang, thanks for the bug report! Unfortunately these changes only work around the reported issues circumstantially, leaving the root cause still there. To fully update the visualized buffer upon type changes, we must make sure the shaders are recompiled when necessary. I'm working on this and will be releasing the fix soon. As for the RGB vs BGR, the best way to deal with that is to include an API entry that describes the channel order when a buffer enters the imagewatch tool. This is because the tool is not opencv-specific, but should work with any arbitrary image format. By having an additional API entry, the tool user can determine at runtime the order of the channels in the gdbiwtype.py script. Issues fixed by the latest merge: https://github.com/csantosbh/gdb-imagewatch/commit/c07ade7a5a42137538212d2406d4b3a797bdf0c0 I'm closing the pull request. Thanks again for the initiative!
2025-04-01T04:36:13.261643
2021-05-24T01:40:03
899169795
{ "authors": [ "cscherrer" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12971", "repo": "cscherrer/KeywordCalls.jl", "url": "https://github.com/cscherrer/KeywordCalls.jl/pull/18" }
gharchive/pull-request
codegen conditional on hasmethod Currently passing everything except precompilation. Here's the error: caching with precompilation: Test Failed at /home/chad/git/KeywordCalls/test/runtests.jl:86 Expression: Precompile2.test() == (a = 2, b = 1) Evaluated: (b = 1, a = 2) == (a = 2, b = 1) Stacktrace: [1] macro expansion @ ~/git/KeywordCalls/test/runtests.jl:86 [inlined] [2] macro expansion @ /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.6/Test/src/Test.jl:1151 [inlined] [3] top-level scope @ ~/git/KeywordCalls/test/runtests.jl:86 Test Summary: | Fail Total caching with precompilation | 1 1 ERROR: LoadError: Some tests did not pass: 0 passed, 1 failed, 0 errored, 0 broken. in expression starting at /home/chad/git/KeywordCalls/test/runtests.jl:85 ERROR: Package KeywordCalls errored during testing Think it's working, what do you think @mileslucas ? Just to be clear, this doesn't yet address #17 , but only #16 Great point, I've updated the docstrings
2025-04-01T04:36:13.265168
2021-06-11T00:17:45
918073995
{ "authors": [ "cscherrer", "icweaver" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12972", "repo": "cscherrer/KeywordCalls.jl", "url": "https://github.com/cscherrer/KeywordCalls.jl/pull/25" }
gharchive/pull-request
static_hasmethod tweaks Hi @mileslucas @icweaver , I was having some issues using KeywordCalls with MeasureTheory where using MeasureTheory would give me a few screenfulls of warnings. I managed to fix it here. One problem is that it's failing tests for contructors with default values. I'll try to find a workaround, but if no one's using it I might consider removing it temporarily. OTOH functions with defaults seem to be fine, and Breakage says Transits.jl tests still pass. Hi @cscherrer, sorry for missing your ping! Thanks for the update, right, things still look to be working alright on our end! Just to make sure I am following the potential issue here, is the problem with just using default values with @kwstruct? No worries :) Yeah, so in runtests.jl, the setup is struct Bar{N,T} nt::NamedTuple{N,T} end @kwstruct Bar(a,b,c=0) Then julia> Bar((a=2,b=3,c=4)) Bar{(:a, :b, :c), Tuple{Int64, Int64, Int64}}((a = 2, b = 3, c = 4)) julia> Bar((a=2,b=3)) Bar{(:a, :b), Tuple{Int64, Int64}}((a = 2, b = 3)) so basically defaults don't work with @kwstruct. I didn't spend too long trying to get it working, but I don't use this feature anyway and it looked like it wasn't coming up in your library either so I went ahead with it. Ah, sounds good. Right, I think we're happy to just keep using outer constructors for our use case!
2025-04-01T04:36:13.331284
2017-11-20T10:25:05
275304338
{ "authors": [ "isoos", "kevmoo", "mkustermann" ], "license": "BSD-3-Clause", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12973", "repo": "dart-lang/pub-dartlang-dart", "url": "https://github.com/dart-lang/pub-dartlang-dart/pull/604" }
gharchive/pull-request
V2 design: change landing page images Guess you have compressed the images using the usual tool? Guess you have compressed the images using the usual tool? No, what tool are we using for that? I'm doing it now :-) On Mon, Nov 20, 2017 at 4:52 AM, István Soós<EMAIL_ADDRESS>wrote: Guess you have compressed the images using the usual tool? No, what tool are we using for that? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/dart-lang/pub-dartlang-dart/pull/604#issuecomment-345686931, or mute the thread https://github.com/notifications/unsubscribe-auth/AABCilhPOpfuh6RsvokiaiDFQWpkE8lJks5s4XYTgaJpZM4QkCUm .
2025-04-01T04:36:13.332249
2017-01-11T20:18:06
200196519
{ "authors": [ "rmacnak-google" ], "license": "BSD-3-Clause", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12974", "repo": "dart-lang/sdk", "url": "https://github.com/dart-lang/sdk/issues/28345" }
gharchive/issue
cc/EmbeddedScript leaks strdup'd script cc/EmbeddedScript: Fail The initial stack trace was misleading because it reported frames with inlining.
2025-04-01T04:36:13.335620
2021-05-29T18:40:21
906534927
{ "authors": [ "rafamizes" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12975", "repo": "dartoos-dev/eo_color", "url": "https://github.com/dartoos-dev/eo_color/issues/78" }
gharchive/issue
Fix weird sentence in README Fix the sentence: "The use of "cryptic" indexes such as 100, 200 ... 800, 900 to select the degree of darkness has been deliberately dropped in favour of a more friendly approach" . Replace: "cryptic" with "obscure" "degree of darkness" with "shade of a color".
2025-04-01T04:36:13.373320
2019-08-17T20:27:08
481923312
{ "authors": [ "fzeiser", "tanyachawla412" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12976", "repo": "deedy/Deedy-Resume", "url": "https://github.com/deedy/Deedy-Resume/pull/53" }
gharchive/pull-request
Update deedy_resume.xtx This seems like you pulled in your changes, not just updates/fixes to the Deedy template. I don't understand why they should be pulled in.
2025-04-01T04:36:13.374964
2019-11-30T15:38:21
530593811
{ "authors": [ "Sai-Adarsh", "deepak2431", "nimishgo" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12977", "repo": "deepak2431/djangoBlog", "url": "https://github.com/deepak2431/djangoBlog/issues/7" }
gharchive/issue
Add new issue template @deepak2431 Can I work on this? @nimishgo Sure, have a go. @deepak2431 What's the status? Shall I work on this? @Sai-Adarsh Until it's open you can work on this. @nimishgo @Sai-Adarsh Are you working on this? As this issue won't require more than 1 days I think.
2025-04-01T04:36:13.396870
2015-05-27T12:16:10
81424636
{ "authors": [ "aloisdg", "delaneyj", "migueldeicaza" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12978", "repo": "delaneyj/three.net", "url": "https://github.com/delaneyj/three.net/pull/1" }
gharchive/pull-request
Sharp Fire() with a quick Linq optimization I will propose a lot of small modifications like this one, if you agree. Does Sharpification of the code include Coding Conventions, Linq optimization, var keyword utilization, this removal, etc.? In general yes I wan to utilize all of the features of modern C# where appropriate. Things like this removal, code conventions, var usage are all probably going to merged without much concern. When you say linq optimization I think we need to look at actual profiling metrics because for foundational (low level if you will) 3d engine related stuff this can add up. I'm all for Linq in game/busniess logic areas, but i'd consider even removing the foreach usage and going for straight for(var i=0... depending on the profiling. Are there actual optimizations that I'm unaware of for Linq? When you say linq optimization I think we need to look at actual profiling metrics because for foundational (low level if you will) 3d engine related stuff this can add up. I use the wrong word. I thought about readibility and clean code. As far as I know, Where is slower than a foreach loop. The difference between for and foreach is near 0 but still exist. Stack Overflow agrees with us. See 1 and 2. You can reject this merge. I think a nice idea would be to add a Contributing doc. ;) Great points, I will add some more detail to the README (specifically about linq for example). Please don't hesitate to help with the general style of the project, but adding linq for brevity at this level should be avoid until we have 100% functionality with the original Three.js. In general, it is a good thing to avoid LINQ in frameworks. As noted above, it is slower and also generates unwanted garbage at runtime. And unlike user code, the end user usually has no control over this, so it is best to avoid it in principle You don't know how happy it makes me to see you in the issues @migueldeicaza. Do you think its possible to find some help getting the cross platform-ness of this project started? I had originally just done on the work on a single machine, even the VS2013 support is a bit cludegy. I would LOVE to see a proper xamerian/vs solution/project structure. I'm totally open to revamping anything structurally to make this happen. @delaneyj xamarin ;) @migueldeicaza Good point. Thank you for mention it. A bit off topic, but before editing Coding Coventions, it may be nice to select the Mono Coding Style or the Microsoft Coding Style. @aloisdg I honestly don't know the differences, will have to look into it. Do you have a suggestion? Pros/Cons? If @migueldeicaza and associates can help get this into a better state for cross platform I'd be happy to bow to their needs. @delaneyj There is a lot of debate about coding style. I don't think there is a true right way to do it. I am going to open an new issue for this topic. Hey guys, only today I setup a solid filter for github notifications, sorry about that. While I would love to help, I am not sure that I have much time right now, but perhaps we can reach out to folks in the mono-list mailing list? Hey @migueldeicaza. I figured you wouldn't have the time directly but if you know the right kind of people to get this working within the Xamarin development world it would be greatly appreciated!
2025-04-01T04:36:13.447269
2019-12-24T08:48:33
542049190
{ "authors": [ "GabiGVeesto", "Zandor300" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12979", "repo": "devicekit/DeviceKit", "url": "https://github.com/devicekit/DeviceKit/issues/225" }
gharchive/issue
iPhoneSE returns true on has3dTouchSupport, should be false Note to self: https://github.com/devicekit/DeviceKit/blob/f19f9f868e8cc26c0fc94a58b46a10d2c100a499/Source/Device.swift.gyb#L55 Second to last argument should be false. I will fix this first thing when I have time.
2025-04-01T04:36:13.470599
2018-08-10T08:42:40
349426792
{ "authors": [ "dfeyer", "vertexvaar" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12980", "repo": "dfeyer/flow-debugproxy", "url": "https://github.com/dfeyer/flow-debugproxy/pull/22" }
gharchive/pull-request
TASK: Add a detailed documentation on how to run the flow-debugproxy in docker containers Thanks, the next step will be to provide an official docker image, to make the setup a bit more easy ;)
2025-04-01T04:36:13.483308
2016-10-25T02:34:16
185003873
{ "authors": [ "asfaltboy", "divmain", "randy3k", "stoivo" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12981", "repo": "divmain/GitSavvy", "url": "https://github.com/divmain/GitSavvy/pull/518" }
gharchive/pull-request
Fix: copied sha needs to be trimed Looks good, but would like for someone to comment before we merge. Still I think we should make it as a practice and always follow it. Not tried to be harsh, just want to make an agreement. Also, a little background around this would help, e.g in the body of the commit or PR Yep, let's wait for another reviewer to give their :+1:, except possibly in cases of emergency bug fixes. 👌 I concur
2025-04-01T04:36:13.486255
2017-05-31T12:54:18
232555050
{ "authors": [ "balcsida", "djavorszky" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12982", "repo": "djavorszky/ddn", "url": "https://github.com/djavorszky/ddn/pull/109" }
gharchive/pull-request
[Janitorial] [Low Priority] Optimize image assets Hi @balcsida, Thanks so much for this pull! The image sizes have been reduced to half their original value, nice catch :-) The failing check on Travis has nothing to do with this pull by the way, it's a time rounding issue coming from database tests, is safe to ignore. I'll work on fixing those tests. Cheers!
2025-04-01T04:36:13.521152
2017-09-27T17:36:56
261058673
{ "authors": [ "coveralls", "donutloop" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12983", "repo": "donutloop/toolkit", "url": "https://github.com/donutloop/toolkit/pull/22" }
gharchive/pull-request
Added: Simple hook implementation Coverage increased (+1.2%) to 86.826% when pulling 440faf53ec044194434eae746eef6ccecc35f721 on feat/hooks into 50e0d0fd4f4c64251ff0599e10f5208c7ae9c702 on master.
2025-04-01T04:36:13.543174
2019-03-28T01:28:06
426252433
{ "authors": [ "codecov-io", "rameshvk" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12984", "repo": "dotchain/dot", "url": "https://github.com/dotchain/dot/pull/238" }
gharchive/pull-request
x/dotc: cleanup unions implementation and add more generated tests Codecov Report Merging #238 into master will increase coverage by 0.42%. The diff coverage is n/a. @@ Coverage Diff @@ ## master #238 +/- ## ========================================== + Coverage 99.25% 99.68% +0.42% ========================================== Files 67 24 -43 Lines 2941 1254 -1687 ========================================== - Hits 2919 1250 -1669 + Misses 12 2 -10 + Partials 10 2 -8 Flag Coverage Δ #dot_changes 100% <ø> (ø) :arrow_up: #dot_changes_diff 100% <ø> (ø) :arrow_up: #dot_changes_run 100% <ø> (ø) :arrow_up: #dot_changes_table 100% <ø> (ø) :arrow_up: #dot_changes_types 100% <ø> (ø) :arrow_up: #dot_ops 98.52% <ø> (-0.24%) :arrow_down: #dot_ops_bolt 97.56% <ø> (ø) :arrow_up: #dot_ops_nw ? #dot_ops_pg ? #dot_refs ? #dot_streams ? #dot_streams_undo ? #dot_test_seqtest ? #dot_x_dotc ? #dot_x_fold ? #dot_x_heap ? #dot_x_rt ? #dot_x_ui_collab ? #dot_x_ui_dom ? #dot_x_ui_html ? #dot_x_ui_input ? Impacted Files Coverage Δ streams/undo/stream.go streams/scheduler.go x/dotc/structs.go x/dotc/slice.go streams/s16.go x/ui/collab/node.go refs/caret.go ops/nw/server.go x/dotc/slices.go x/ui/html/html.go ... and 31 more 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 4f19091...0258eb0. Read the comment docs.
2025-04-01T04:36:13.642068
2016-05-19T15:30:16
155766414
{ "authors": [ "ansnecsy", "kie-ci" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12985", "repo": "droolsjbpm/drools-wb", "url": "https://github.com/droolsjbpm/drools-wb/pull/180" }
gharchive/pull-request
6.4.x Can one of the admins verify this PR? Comment with 'ok to test' to start the build. Can one of the admins verify this PR? Comment with 'ok to test' to start the build.
2025-04-01T04:36:13.649595
2018-09-02T02:05:44
356246363
{ "authors": [ "coveralls", "dustinengle" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12986", "repo": "dustinengle/bulwark-ui", "url": "https://github.com/dustinengle/bulwark-ui/pull/50" }
gharchive/pull-request
fixes #25 adds menu and menu item Coverage remained the same at 100.0% when pulling 09e67703efd084cfed16c3adc0872b5f8f6c6695 on menu into 57ce945e35988cbf0fa8b3677b745debd3fc2057 on master.
2025-04-01T04:36:13.664826
2019-06-05T19:51:37
452685589
{ "authors": [ "codecov-io", "twentylemon" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12987", "repo": "dynodao/dynodao", "url": "https://github.com/dynodao/dynodao/pull/35" }
gharchive/pull-request
add dynodao-aggreator project Codecov Report Merging #35 into master will not change coverage. The diff coverage is n/a. @@ Coverage Diff @@ ## master #35 +/- ## ========================================= Coverage 92.08% 92.08% Complexity 658 658 ========================================= Files 83 83 Lines 1807 1807 Branches 80 80 ========================================= Hits 1664 1664 Misses 110 110 Partials 33 33 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 b567cc1...ab7b07e. Read the comment docs.
2025-04-01T04:36:13.680159
2015-06-28T14:04:41
91603252
{ "authors": [ "qwIvan", "rbygrave" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12988", "repo": "ebean-orm/avaje-ebeanorm-mocker", "url": "https://github.com/ebean-orm/avaje-ebeanorm-mocker/issues/1" }
gharchive/issue
Ebean.mock() has protected access? Yes it does. MockiEbean via avaje-ebeanorm-mocker has public access. Question answered then? So to add to that ... I have just added a runWithMock() to MockiEbean that takes a mock and either a Runnable or Callable so: MockiEbean.runWithMock(mock, new Runnable() { @Override public void run() { // test code in here } }); So with Java8 lambda instead of the runnable that becomes nice. Would that do what you want?
2025-04-01T04:36:13.773871
2021-03-19T04:18:00
835541875
{ "authors": [ "HexF", "Shivansh-007", "dvargas46" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12989", "repo": "engineer-man/piston", "url": "https://github.com/engineer-man/piston/pull/178" }
gharchive/pull-request
pkg(pure-0.68): Add pure-lang 0.68 couple things here to get you going further: on line 11 in the build script, those directories you are trying to move will not exist. tar xfz llvm.tar.gz --strip-components=1 <-- --strip-components will remove the root dir of the archive tar xfz clang.tar.gz --strip-components=1 mv clang llvm/tools/clang <-- therefore, "clang" and "llvm" dirs won't exist rm llvm.tar.gz && rm clang.tar.gz I haven't looked at how to build both llvm and clang, but are you sure that this is a way to build both at the same time? I would think it'd need to be separate, but not sure. use SemVer on your folder structure and metadata. I think that's important for the api to detect where to go try those out and see if it helps. then we can squash whatever issues might come after :) Ok thanks @dvargas46 will try them out, one question, what is SemVer? Yes, this is a way to build them correctly, I have been following this: https://agraef.github.io/pure-docs/install.html. You forgot the -O flag on curl, so it just outputs to stdout @Shivansh-007 try these updates: In the build.sh script Change the first configure command (the one for llvm/clang) to be: ./congure --prefix="$PREFIX" --enable-optimized --enable-targets=host-only --enable-docs="no" --enable-assertions="no" Change the second configure command (the one for pure) to be: ./configure --prefix="$PREFIX" --enable-release --with-tool-prefix="$PREFIX/bin" --with-static-llvm in the environment file Add this above the path export: export LD_LIBRARY_PATH=$PWD/lib
2025-04-01T04:36:13.786102
2018-08-09T04:31:39
348973981
{ "authors": [ "omguddu100", "sugardave" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12990", "repo": "enyojs/enyo", "url": "https://github.com/enyojs/enyo/issues/1485" }
gharchive/issue
How to implement google map api..?? Hello! This question is a little vague, but if they provide the API you can just include it and use any of their "web" examples for using it. I remember having some trouble with certain Google APIs (namely ads) in mobile web apps, but I think the map API might be okay. Please check through the Enyo forums for others who may have done this already.
2025-04-01T04:36:13.852674
2019-02-01T08:23:09
405597824
{ "authors": [ "codecov-io", "tisnik" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12991", "repo": "fabric8-analytics/fabric8-analytics-nvd-toolkit", "url": "https://github.com/fabric8-analytics/fabric8-analytics-nvd-toolkit/pull/39" }
gharchive/pull-request
Use Radon 2.4.0 instead of 3.0.0 Codecov Report :exclamation: No coverage uploaded for pull request base (master@532f229). Click here to learn what that means. The diff coverage is n/a. @@ Coverage Diff @@ ## master #39 +/- ## ========================================= Coverage ? 90.01% ========================================= Files ? 19 Lines ? 1042 Branches ? 0 ========================================= Hits ? 938 Misses ? 104 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 532f229...bce929a. Read the comment docs.
2025-04-01T04:36:13.873388
2018-10-18T16:58:22
371622978
{ "authors": [ "Brymon", "codecov-io" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12992", "repo": "fac-14/OSCEBossKey", "url": "https://github.com/fac-14/OSCEBossKey/pull/153" }
gharchive/pull-request
Tick displayed Codecov Report Merging #153 into master will not change coverage. The diff coverage is n/a. @@ Coverage Diff @@ ## master #153 +/- ## ======================================= Coverage 81.81% 81.81% ======================================= Files 15 15 Lines 143 143 Branches 19 19 ======================================= Hits 117 117 Misses 21 21 Partials 5 5 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 60eae6f...632ecc9. Read the comment docs.
2025-04-01T04:36:13.879806
2018-11-28T05:45:50
385111384
{ "authors": [ "alishir", "codecov-io", "fafhrd91" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12993", "repo": "fafhrd91/actix-http", "url": "https://github.com/fafhrd91/actix-http/pull/9" }
gharchive/pull-request
echo example with impl Future Also could you run cargo fmt with stable rustfmt Codecov Report Merging #9 into master will not change coverage. The diff coverage is n/a. @@ Coverage Diff @@ ## master #9 +/- ## ======================================= Coverage 67.82% 67.82% ======================================= Files 44 44 Lines 5324 5324 ======================================= Hits 3611 3611 Misses 1713 1713 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 756bf0a...4028f6f. Read the comment docs. Thanks
2025-04-01T04:36:13.888323
2020-08-07T22:35:12
675321922
{ "authors": [ "KushajveerSingh", "hamelsmu" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12994", "repo": "fastai/fastai2", "url": "https://github.com/fastai/fastai2/pull/501" }
gharchive/pull-request
remove **kwargs in load_image Hi @KushajveerSinghI will update your branch so you we can put your PR through the corrected CI Suites. This is just a rebase cc: @jph00 this is the flow of what happens when someone makes a mistake with nbdev. LMK if you would like to tweak the messaging at all.
2025-04-01T04:36:13.914287
2021-05-24T17:51:48
899874421
{ "authors": [ "coveralls", "ncilfone" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12995", "repo": "fidelity/spock", "url": "https://github.com/fidelity/spock/pull/57" }
gharchive/pull-request
Updating some docs Pull Request Test Coverage Report for Build 872226932 0 of 0 changed or added relevant lines in 0 files are covered. No unchanged relevant lines lost coverage. Overall coverage increased (+0.3%) to 95.704% Totals Change from base Build 828404100: 0.3% Covered Lines: 958 Relevant Lines: 1001 💛 - Coveralls
2025-04-01T04:36:13.967139
2019-08-03T16:55:20
476469709
{ "authors": [ "patrickmichalina" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12996", "repo": "flocasts/flo-angular", "url": "https://github.com/flocasts/flo-angular/pull/199" }
gharchive/pull-request
chore: update packages :tada: This PR is included in version 10.0.0 :tada: The release is available on GitHub release Your semantic-release bot :package::rocket:
2025-04-01T04:36:14.039968
2016-09-14T09:55:17
176864374
{ "authors": [ "7sharp9", "forki" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12997", "repo": "fsharp/FSharp.Compiler.Service", "url": "https://github.com/fsharp/FSharp.Compiler.Service/pull/633" }
gharchive/pull-request
Yo Tha maintainers Yo - thug life I don't think Robin is maintaining anymore, or did he just step away from """The project cracker""" /cc @rneatherway (tbh I just wanted to fix the typo)
2025-04-01T04:36:14.045575
2020-07-27T22:03:18
666612695
{ "authors": [ "Brian-Williams", "initialed85" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12998", "repo": "ftpsolutions/python-third-party-license-file-generator", "url": "https://github.com/ftpsolutions/python-third-party-license-file-generator/pull/5" }
gharchive/pull-request
Don't rely on distutils init importing spawn /shrug Looks like this one is broken- if you wanna resubmit it just lemme know @Brian-Williams
2025-04-01T04:36:14.065576
2019-04-11T21:31:28
432261416
{ "authors": [ "mgabdev", "propolisor" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:12999", "repo": "gab-ai-inc/gab-dissenter-extension", "url": "https://github.com/gab-ai-inc/gab-dissenter-extension/issues/59" }
gharchive/issue
Add support for .onion URLs and other alternative URL schemas Hi @propolisor upon testing a few .onion URLs they are working. (For instance: https://dissenter.com/discussion/begin?url=http://wallstyizjhkrvmj.onion) Can you please include some URLs as examples (.onion and any other alternative ones) that you believe are not supported? Closing this issue as it appears that .onion urls work correctly in recent Dissenter build. Please feel free to reopen if there is any specific .onion url that is not working.
2025-04-01T04:36:14.088396
2015-05-27T21:13:11
81627338
{ "authors": [ "jandm", "janvenstermans" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13000", "repo": "geomajas/geomajas-project-graphics", "url": "https://github.com/geomajas/geomajas-project-graphics/pull/18" }
gharchive/pull-request
GGP-79: update GWT and geomajas version in dependencies Jan Venstermans: +1 Jan De Moerloose: +1 (binding)
2025-04-01T04:36:14.134290
2017-12-06T14:21:16
279769824
{ "authors": [ "kortschak", "vladimir-ch" ], "license": "bsd-3-clause", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13001", "repo": "gonum/gonum", "url": "https://github.com/gonum/gonum/pull/327" }
gharchive/pull-request
blas/gonum: add Zhpr PTAL Please remember to send a PR adding the tests here and running check-generate.sh in netlib after this is merged.
2025-04-01T04:36:14.138154
2021-06-28T10:10:34
931403615
{ "authors": [ "gdgate", "no23reason", "yenkins" ], "license": "BSD-3-Clause", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13002", "repo": "gooddata/gooddata-ui-apidocs", "url": "https://github.com/gooddata/gooddata-ui-apidocs/pull/7" }
gharchive/pull-request
RELATED: RAIL-3511 Upgrade readme reflecting the new scripting Build succeeded (check pipeline). Sonar scan result More detail, see in https://sonarqube-gate.intgdc.com/dashboard?id=gooddata-ui-apidocs-gate-PR7 To scan for vulnerabilities in dependencies and run unit tests (to get coverage report in sonar) please comment your PR with 'extended check sonar'. Build succeeded (gate pipeline). https://checklist.intgdc.com/job/compliance/job/gooddata-ui-apidocs-fossa-scanning-zuul-el7/13/ : SUCCESS in 39s (non-voting) https://checklist.intgdc.com/job/compliance/job/gooddata-ui-apidocs-sonarqube-scan-zuul-gate/18/ : SUCCESS in 45s https://checklist.intgdc.com/job/compliance/job/gooddata-ui-apidocs-merge-compliance-check/13/ : SUCCESS in 21s
2025-04-01T04:36:14.141728
2016-06-02T21:55:34
158248784
{ "authors": [ "AnmAtAnm", "RoboErikG", "geppy" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13003", "repo": "google/blockly-android", "url": "https://github.com/google/blockly-android/issues/305" }
gharchive/issue
Drag-to-trash should abort if a block is not deletable. What's the desired behavior here? A bounce? Reverting the drag? Reverting the drag. And this will be easier once events are in place since we'll be collecting the right information to do the revert. On Jun 23, 2016 5:12 PM, "geppy"<EMAIL_ADDRESS>wrote: What's the desired behavior here? A bounce? Reverting the drag? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/google/blockly-android/issues/305#issuecomment-228222588, or mute the thread https://github.com/notifications/unsubscribe/AKjbp0Wdgeu95Zgw2cq8dpC9iojbenxIks5qOyEDgaJpZM4ItBSO . Open question #370. Current behavior respects the dragged root block's deletable flag. Respecting children is an open question in #370.
2025-04-01T04:36:14.146269
2020-11-10T11:13:59
739817622
{ "authors": [ "j-towns", "mattjj" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13004", "repo": "google/jax", "url": "https://github.com/google/jax/pull/4854" }
gharchive/pull-request
Rm redundant pre-omnistaging attribute annotations from core.TraceStack Thanks! I suspect this was a result of a bad rebase. I think we want to add back correct annotations though, which should probably be class TraceStack: stack: List[MainTrace] dynamic: MainTrace I'll see if I can push those onto this PR.
2025-04-01T04:36:14.149137
2016-12-15T11:28:21
195781942
{ "authors": [ "drinckes", "goncalo-oliveira" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13005", "repo": "google/open-location-code", "url": "https://github.com/google/open-location-code/pull/60" }
gharchive/pull-request
added csharp implementation Hi, thanks for this! To add it into the repo, we'll need you to add shorten and recover methods as well as the encoding/decoding. (See the API summary.) Also add build and test instructions to the README.md (thanks for having one by the way). If you don't want to do that, but have your own repo, we could link to it from the wiki? Let me know what you decide, and thanks again!
2025-04-01T04:36:14.151576
2021-02-01T15:24:52
798455127
{ "authors": [ "amanda-tarafa", "chrisdunelm" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13006", "repo": "googleapis/google-cloud-dotnet", "url": "https://github.com/googleapis/google-cloud-dotnet/pull/5895" }
gharchive/pull-request
Add sync Create() method to PublisherClient and SubscriberClient OK, I'll merge this now, can add anything extra in a further PR. Looks good to me. @amanda-tarafa was there anything specific that you think it's worth testing? No, that's fine.
2025-04-01T04:36:14.168015
2020-12-23T18:37:00
773979052
{ "authors": [ "codecov-io", "ernado" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13007", "repo": "gotd/td", "url": "https://github.com/gotd/td/pull/68" }
gharchive/pull-request
ci: update coverage bash script Codecov Report Merging #68 (d2d0ef0) into main (05a7822) will increase coverage by 4.70%. The diff coverage is n/a. @@ Coverage Diff @@ ## main #68 +/- ## ========================================== + Coverage 56.66% 61.36% +4.70% ========================================== Files 94 112 +18 Lines 2432 3228 +796 ========================================== + Hits 1378 1981 +603 - Misses 837 975 +138 - Partials 217 272 +55 Impacted Files Coverage Δ internal/tmap/tmap.go 100.00% <0.00%> (ø) telegram/internal/tgtest/server.go 74.19% <0.00%> (ø) telegram/internal/tgtest/proto.go 52.38% <0.00%> (ø) internal/gen/internal/bindata.go 48.27% <0.00%> (ø) telegram/internal/bindata.go 20.00% <0.00%> (ø) cmd/gotdecho/main.go 0.00% <0.00%> (ø) telegram/internal/tgtest/handler.go 100.00% <0.00%> (ø) telegram/internal/tgtest/exchange.go 61.53% <0.00%> (ø) telegram/internal/tgtest/test_transport.go 75.40% <0.00%> (ø) cmd/gotdchats/main.go 0.00% <0.00%> (ø) ... and 39 more 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 05a7822...d2d0ef0. Read the comment docs.
2025-04-01T04:36:14.170448
2016-11-12T22:40:26
188939108
{ "authors": [ "bradleyfalzon", "coveralls", "hung-yueh" ], "license": "bsd-3-clause", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13008", "repo": "grafov/m3u8", "url": "https://github.com/grafov/m3u8/pull/76" }
gharchive/pull-request
Add EXT-X-SESSION-KEY support for offline playback Coverage decreased (-1.9%) to 57.091% when pulling e6eb0a0730f727cfbb9cee9022d5830ca2804bda on hung-yueh:master into 4c69ce4c839a9b1313fd747e44fe27053bde78e8 on grafov:master. Excellent, thank you, are you able to include a test and sample playlist for the reader and writer functions? Sure. Will do it.
2025-04-01T04:36:14.180520
2015-01-09T21:40:50
53918239
{ "authors": [ "obfuscurity", "ryan-williams" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13009", "repo": "graphite-project/graphite-web", "url": "https://github.com/graphite-project/graphite-web/pull/1091" }
gharchive/pull-request
add architecture diagram to faq.rst Would you mind also backporting this to 0.9.x? Restarted the failed job. OK. Should I do that in addition to or in lieu of sending PRs to master? Not at all. But in this case it makes sense to have it in both master and 0.9.x. I don't know why that TOXENV=py27-django16-pyparsing1 keeps failing due to the image but I'm probably going to merge it anyways. Oops, I mean TOXENV=docs. Hmm. On second thought, we need to fix whatever's breaking the docs build or it will never pass again. @ryan-williams Check out the failed build at https://travis-ci.org/graphite-project/graphite-web/jobs/46499107 and see if you can figure out how to fix the local image issue. @gwaldo might be able to offer assistance here. Ok, it looks like the proper fix is to refer to the local image. Fortunately we already have it at webapp/content/img/overview.png so you'll just need to point to that instead. Please change this in #1092 as well. @ryan-williams The following patch should fix it for you. I can't test it locally because there's something broken about libcairo on the Mac. diff --git a/docs/faq.rst b/docs/faq.rst index 5150a35..1777748 100644 --- a/docs/faq.rst +++ b/docs/faq.rst @@ -75,7 +75,7 @@ Is there a diagram of Graphite's architecture? ---------------------------------------------- There sure is! Here it is: -.. image:: https://raw.githubusercontent.com/graphite-project/graphite-web/master/webapp/content/img/overview.png +.. image:: ../webapp/content/img/overview.png .. _Django: http://www.djangoproject.com/ P.S. Please update #1092 with the same change if this one passes tests. sorry for dropping this, applying your fix now, thanks Cool, thanks. Looks good. http://graphite.readthedocs.org/en/latest/faq.html hooray, thanks! On Mon Jan 12 2015 at 4:53:09 PM Jason Dixon<EMAIL_ADDRESS>wrote: Looks good. http://graphite.readthedocs.org/en/latest/faq.html — Reply to this email directly or view it on GitHub https://github.com/graphite-project/graphite-web/pull/1091#issuecomment-69653470 .
2025-04-01T04:36:14.188027
2016-12-16T01:20:11
195959015
{ "authors": [ "dgquintas", "yang-g" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13011", "repo": "grpc/grpc", "url": "https://github.com/grpc/grpc/pull/9136" }
gharchive/pull-request
Make sure grpc_init() is called before threadpool'd CB @jboeuf FYI hmm nevermind, that was a red herring. Closing.
2025-04-01T04:36:14.209333
2017-02-22T15:49:44
209494139
{ "authors": [ "h6ah4i", "polyak01" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13012", "repo": "h6ah4i/android-advancedrecyclerview", "url": "https://github.com/h6ah4i/android-advancedrecyclerview/pull/360" }
gharchive/pull-request
fixed crash during dragging items and device rotation @polyak01 Hi, thanks for the contribution! When I saw your code, I thought that it looked like a weird fix, so there must be a different fault causing the issue. I checked another lines of my code carefully and then I found them! The culprit I use removeCallbacks(null) in the InternalHandler.release() method, but it should be removeCallbacksAndMessages(null). Asks Please fix the issue in correct way and update this PR 🙇 Revert the line 2222 change Change removeCallbacks(null) to removeCallbacksAndMessages(null) IMPORTANT The same fault exists in the RecyclerViewSwipeManager, fix this too. Confirm that the problem has been resolved. Change the base branch of this PR to develop https://github.com/h6ah4i/android-advancedrecyclerview/pull/362 PR #362 has been merged now. @h6ah4i I would like to import the library into the project with most of the new fixes. When I can do it?) @polyak01 I'm now prepareing the next version (v0.10.4) release. Just a moment... @h6ah4i Thanks!) @polyak01 I have just finished releasing v0.10.4 🎉
2025-04-01T04:36:14.226916
2019-09-19T04:43:27
495569743
{ "authors": [ "QuestofIranon" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13013", "repo": "hashgraph/MyHbarWallet", "url": "https://github.com/hashgraph/MyHbarWallet/pull/9" }
gharchive/pull-request
Use Hbar Wrapper from the SDK Having to do heavy refactoring to avoid pulling the sdk statically. I'm going to redo this with a newer version of the sdk that fixes gripes I ran into while working on this branch.
2025-04-01T04:36:14.231130
2021-01-21T20:30:55
791471183
{ "authors": [ "hashicorp-cla", "mihaistanciu-techdev" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13014", "repo": "hashicorp/hashicat-aws", "url": "https://github.com/hashicorp/hashicat-aws/pull/237" }
gharchive/pull-request
Feature/changing deploy app Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement Learn more about why HashiCorp requires a CLA and what the CLA includes Have you signed the CLA already but the status is still pending? Recheck it. Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement Learn more about why HashiCorp requires a CLA and what the CLA includes Have you signed the CLA already but the status is still pending? Recheck it.
2025-04-01T04:36:14.246196
2016-06-17T12:20:04
160876036
{ "authors": [ "jpkrohling" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13015", "repo": "hawkular/hawkular-services", "url": "https://github.com/hawkular/hawkular-services/pull/19" }
gharchive/pull-request
HAWKULAR-1089 - Updated Commons, removing embedded Cassandra @pilhuhn , could you please review, specially the docker/MacOS commands to start Cassandra? I copied them from your instructions on IRC, but would be good to double check. The Fedora instructions were added based on my Ansible playbooks. Ready for review. Alright, I removed the part that has instructions on how to run it on different OSes.
2025-04-01T04:36:14.248970
2019-10-04T19:19:55
502802995
{ "authors": [ "deppp" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13016", "repo": "heartexlabs/label-studio", "url": "https://github.com/heartexlabs/label-studio/pull/76" }
gharchive/pull-request
duration it takes to create a new completion @shevchenkonik When you have a minute can you please check that I'm not missing anything here? especially that loadDate is correctly initialized
2025-04-01T04:36:14.568977
2019-02-25T09:02:14
413997933
{ "authors": [ "marcoscaceres" ], "license": "BSD-3-Clause", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13017", "repo": "highlightjs/highlight.js", "url": "https://github.com/highlightjs/highlight.js/pull/1985" }
gharchive/pull-request
fix(package): bin path not resolving correctly Ok, fingers crossed! 🤞😅 doing the release magic now locally now...
2025-04-01T04:36:14.574251
2020-05-31T21:00:19
628043157
{ "authors": [ "NathanLovato", "otavioschwanck" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13018", "repo": "hlissner/doom-emacs", "url": "https://github.com/hlissner/doom-emacs/pull/3265" }
gharchive/pull-request
GDScript for doom Already opened a PR a few days ago here: https://github.com/hlissner/doom-emacs/pull/3239
2025-04-01T04:36:14.588320
2018-09-18T08:37:07
361194272
{ "authors": [ "attilapalfi92", "jenkins-cloudbreak" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13019", "repo": "hortonworks/cloudbreak", "url": "https://github.com/hortonworks/cloudbreak/pull/4008" }
gharchive/pull-request
testing jenkinsfile Refer to this link for build results (access rights to CI server needed): ci-cloudbreak.eng.hortonworks.com/job/cloudbreak-build-pipeline/2/ Refer to this link for build results (access rights to CI server needed): ci-cloudbreak.eng.hortonworks.com/job/cloudbreak-build-pipeline/4/
2025-04-01T04:36:14.626367
2015-04-08T20:44:27
67216237
{ "authors": [ "horsburgh", "jsadler2", "pkdash" ], "license": "bsd-3-clause", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13020", "repo": "hydroshare/hydroshare", "url": "https://github.com/hydroshare/hydroshare/issues/289" }
gharchive/issue
Message Block in Resource Landing Page @jsadler2 I think we can use django messaging framework (https://docs.djangoproject.com/en/1.8/ref/contrib/messages/) to display messages and our base.html already includes code to display messages from this framework. @jsadler2 - is this still an issue or can it be closed? @jsadler2 Please close this issue.
2025-04-01T04:36:14.635464
2019-05-17T14:11:42
445462442
{ "authors": [ "gvanbrakel", "nielsm5" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13021", "repo": "ibissource/iaf", "url": "https://github.com/ibissource/iaf/pull/133" }
gharchive/pull-request
Avoid memory bomb exploding when test-xmls are validated It might be good to add that this is because Eclipse validates all resources, and crashes while validating scenario09/in.xml
2025-04-01T04:36:14.640620
2018-10-12T23:17:59
369739712
{ "authors": [ "ijacquez", "razor85" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13022", "repo": "ijacquez/libyaul", "url": "https://github.com/ijacquez/libyaul/pull/59" }
gharchive/pull-request
Fix sprintf parsing of %d as int16_t. Thanks. I'll merge once I merge from my private upstream repo. Changed repositories / branches.
2025-04-01T04:36:14.641592
2016-09-13T06:54:47
176564045
{ "authors": [ "chrisandreae", "thefloweringash" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13023", "repo": "iknow/cerego_view_models", "url": "https://github.com/iknow/cerego_view_models/pull/19" }
gharchive/pull-request
Flip Reference.from_viewmodel(vm) to vm.to_reference LGTM. Assuming motivation is coming from the future.
2025-04-01T04:36:14.644170
2018-05-27T09:27:48
326801492
{ "authors": [ "DaniellMesquita", "Thunder33345", "imachug" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13024", "repo": "imachug/ZeroNet-Instant-Messenger", "url": "https://github.com/imachug/ZeroNet-Instant-Messenger/issues/11" }
gharchive/issue
Status (chatty/do not disturb/etc.) group #13 #12 into one? but as checboxes task? since it can show checkbox too ah ok Also: [ ] Busy [ ] Away I think "Tipping" is a sub status. Merged.
2025-04-01T04:36:14.655211
2016-08-05T11:29:04
169587489
{ "authors": [ "henrahmagix", "hippogriffic", "wytrych" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13025", "repo": "incuna/djangular-rest-framework", "url": "https://github.com/incuna/djangular-rest-framework/pull/22" }
gharchive/pull-request
Form field updates @incuna/js @incuna/frontend Please review. @hippogriffic Please take a look at the form-field.html template template looks good 👍 @incuna/js @henrahmagix bump 👍 @incuna/js @incuna/frontend updated 👍
2025-04-01T04:36:14.657383
2019-03-19T14:26:00
422762625
{ "authors": [ "birdayz", "nishanthvijayan" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13026", "repo": "infinimesh/kaf", "url": "https://github.com/infinimesh/kaf/issues/36" }
gharchive/issue
groups list: sort by name Doesn't groups ls already return a sorted list? (Implemented in 45de94e7cfe14a3c9e110ccb1b0ed882dd022ae0)
2025-04-01T04:36:14.675387
2020-07-08T16:02:41
653416521
{ "authors": [ "Tim-Linschoten", "codecov-commenter" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13027", "repo": "ing-bank/baker", "url": "https://github.com/ing-bank/baker/pull/596" }
gharchive/pull-request
Interaction starter spring Codecov Report Merging #596 into master will increase coverage by 0.09%. The diff coverage is 76.56%. @@ Coverage Diff @@ ## master #596 +/- ## ========================================== + Coverage 78.04% 78.14% +0.09% ========================================== Files 120 120 Lines 3913 3912 -1 Branches 90 90 ========================================== + Hits 3054 3057 +3 + Misses 859 855 -4 Impacted Files Coverage Δ ...in/scala/com/ing/baker/baas/interaction/Main.scala 0.00% <0.00%> (ø) ...ker/baas/interaction/RemoteInteractionLoader.scala 0.00% <0.00%> (ø) ...cala/com/ing/baker/baas/state/KafkaEventSink.scala 18.18% <ø> (ø) ...src/main/scala/com/ing/baker/baas/state/Main.scala 0.00% <0.00%> (ø) ...ry/clustercontroller/BakeryControllerService.scala 0.00% <0.00%> (ø) .../scala/com/ing/bakery/clustercontroller/Main.scala 0.00% <ø> (ø) ...la/com/ing/baker/baas/state/StateNodeService.scala 79.41% <79.41%> (ø) ...er/baas/interaction/RemoteInteractionService.scala 78.57% <100.00%> (ø) ...ing/baker/runtime/serialization/JsonDecoders.scala 95.45% <100.00%> (ø) ...ing/baker/runtime/serialization/JsonEncoders.scala 100.00% <100.00%> (ø) ... and 5 more 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 a13da2c...1ee3cf4. Read the comment docs.
2025-04-01T04:36:14.699707
2018-02-23T15:31:34
299749510
{ "authors": [ "Techworker", "robinlehrmann" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13028", "repo": "iota-php/client", "url": "https://github.com/iota-php/client/pull/46" }
gharchive/pull-request
fixed tests and use guzzle You are write. I would prefer to include them in the travis-ci build. Then we have the last stable version of it. For the the examples too. What do you think about a phar file for it ? We should made it compatible with php natively. Then you'd need a custom .phar for each target (OS). I think you should just leave it out, document what should be done to make it work. Travis does not need the lib, we will have to mock it (see PowInterface). The POW takes a lot of time, it does not make sense at all to call it in the tests (from my pov).
2025-04-01T04:36:14.701232
2018-09-25T17:38:19
363693023
{ "authors": [ "achingbrain", "nicola" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13029", "repo": "ipfs/js-ipfs-mfs", "url": "https://github.com/ipfs/js-ipfs-mfs/pull/14" }
gharchive/pull-request
IPFS mispelling Thanks for submitting this. The tests are passing on Jenkins now but the build is still failing because the commit message doesn't meet the proscribed format. Fixed in 104139ba
2025-04-01T04:36:14.718010
2019-07-09T09:51:56
465684127
{ "authors": [ "Morpheu5", "jsharkey13", "mlt47" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13030", "repo": "isaacphysics/isaac-cs-app", "url": "https://github.com/isaacphysics/isaac-cs-app/pull/81" }
gharchive/pull-request
Add 'View in the Content Editor' button @mlt47 - is there not an easier / better way of loading this constant from the API? Surely we can load it once into the state store and then use it from there? @mlt47 - is there not an easier / better way of loading this constant from the API? Surely we can load it once into the state store and then use it from there? The action code already does this. The request action just returns if the value is already set. Perhaps an improvement would be to move the useEffect(()=>{action()}) for requesting the constant into IsaacApp so that it is only tried once, at the time that the react component for isaac app is created. Then you could remove the use effects from question, concept and generic pages.
2025-04-01T04:36:14.742374
2019-06-04T03:48:32
451784579
{ "authors": [ "fpesce", "istio-testing", "wattli" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13031", "repo": "istio/istio", "url": "https://github.com/istio/istio/pull/14547" }
gharchive/pull-request
Update CA root cert TTL to 10 years [APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: wattli The full list of commands accepted by this bot can be found here. The pull request process is described here Needs approval from an approver in each of these files: security/OWNERS [wattli] Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment @wattli: The following test failed, say /retest to rerun them all: Test name Commit Details Rerun command prow/integ-framework-local-presubmit-tests.sh 8c96b6aee05dc90adefed29f6bfe9c32296d7af7 link /test integ-framework-local-presubmit-tests-release-1.2 Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. @wattli: The following tests failed, say /retest to rerun them all: Test name Commit Details Rerun command prow/integ-framework-local-presubmit-tests.sh 8c96b6aee05dc90adefed29f6bfe9c32296d7af7 link /test integ-framework-local-presubmit-tests-release-1.2 prow/e2e-simpleTests.sh 8c96b6aee05dc90adefed29f6bfe9c32296d7af7 link /test e2e-simpleTests-release-1.2 Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. /test e2e-simpleTests-release-1.2 /test integ-framework-local-presubmit-tests-release-1.2 @wattli It doesn't look like master has this change c.f. 5th point of 1.2 Release branch cut Please submit the change to master first, before I can merge this to 1.2 @linsun: changing LGTM is restricted to assignees, and assigning you to the PR failed. In response to this: /lgtm /approve Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. [APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: linsun, wattli The full list of commands accepted by this bot can be found here. The pull request process is described here Needs approval from an approver in each of these files: security/OWNERS [linsun,wattli] Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment
2025-04-01T04:36:14.758080
2016-11-07T19:18:32
187801992
{ "authors": [ "StrawsonDesign", "jadonk" ], "license": "CC-BY-4.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13032", "repo": "jadonk/beaglebone-blue-jadonk", "url": "https://github.com/jadonk/beaglebone-blue-jadonk/issues/38" }
gharchive/issue
Need spec on conformal coating MG chemicals 419D Acrylic Conformal Coating was my original suggestion to Embest. However they used Humiseal 1B73 which is an almost identical product and seems to have worked well on our prototypes. @StrawsonDesign What areas on the A2 layout? Can you mark-up the board PDF? Graphic added... https://github.com/jadonk/beaglebone-blue/commit/432ebf36c79731519eb745985146eb871d6f98e4 Now we just need to add related information to the README.md in the MFG directory and we can close this issue. Issue migrated to beagleboard/beaglebone-blue#49
2025-04-01T04:36:14.760465
2021-06-23T11:36:41
928161502
{ "authors": [ "ChrisNeedham24", "jamesgiu" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13033", "repo": "jamesgiu/quick-hit", "url": "https://github.com/jamesgiu/quick-hit/issues/33" }
gharchive/issue
Firebase auth quota limit After doing some research on this, I'm not sure that we can actually do anything about this, while we're all using the same account. The limit is 25 requests in 10 minutes, which isn't that low, but still. So yeah, if we want to address this, we'd need to add multiple accounts, I think. Yeah I guess we'll close this until it becomes a huger issue, though we could do some cheeky account rotation in the background if we have to Thanks for looking into it btw IT'S BACK Could also modify the polling with this one. 🦀
2025-04-01T04:36:14.766111
2017-01-14T03:33:15
200777323
{ "authors": [ "homunkulus", "japaric" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13034", "repo": "japaric/cross", "url": "https://github.com/japaric/cross/pull/55" }
gharchive/pull-request
support older versions of the openssl crate @homunkulus r+ :pushpin: Commit e972216 has been approved by japaric :hourglass: Testing commit e972216 with merge 40552ae... :broken_heart: Test failed - status-travis :pushpin: Commit 51f37c5 has been approved by japaric @homunkulus r+ :hourglass: Testing commit 51f37c5 with merge 57f1f6d... :sunny: Test successful - status-travis Approved by: japaric Pushing 57f1f6d5232817bb2b7f774d7df1d626b2a4819f to master...
2025-04-01T04:36:14.774242
2015-10-30T10:59:50
114248301
{ "authors": [ "danieldietrich", "ruslansennov" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13035", "repo": "javaslang/javaslang-jackson", "url": "https://github.com/javaslang/javaslang-jackson/pull/1" }
gharchive/pull-request
refactoring Mmhh, travis completed the job successfully. But the history on travis says that there are no jobs. Something in the .travis.yml? I did not change the security tokens... Coveralls.io on the other hand works like a charme It was a little experiment. OK, I'll waiting for your settings :) later today or tomorrow - we will get it working!
2025-04-01T04:36:14.779465
2020-11-23T14:41:44
748859634
{ "authors": [ "camilonova", "hugovk", "jezdez" ], "license": "bsd-3-clause", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13036", "repo": "jazzband/sorl-thumbnail", "url": "https://github.com/jazzband/sorl-thumbnail/pull/656" }
gharchive/pull-request
Bump version @aleksihakli would you help me out? @jezdez it did not show up at jazzband releases. Can you take a look? @camilonova Ah right, I think there is some weirdness around GitHub releases versus Git tags. When we were on Travis-CI it was enough to release when a tag was created, for GitHub Actions (and the way I've seen it more often configured) the condition under which a release process is triggered is when a "GitHub release" is published. I just checked on https://github.com/jazzband/sorl-thumbnail/releases and saw the 12.7.0 not as a "release" but just as a "tag", clicked "Edit" and then "Publish release". This should be rolling out now. The release workflow ran now: https://github.com/jazzband/sorl-thumbnail/runs/1442977373?check_suite_focus=true#step:9:13 I'm currently wondering how to handle this, whether we should try to find a solution like we had with Travis-CI where a Git tag was enough to trigger the release process. @hugovk I know you've had some experience with this, can you shed some light on the topic of GitHub releases versus Git tags? Ah yes, have a look at https://github.com/jazzband/prettytable/blob/master/RELEASING.md, you need to go to https://github.com/jazzband/prettytable/releases and create a "GitHub release" from the Git tag. And then deploy.yml is triggered by that GitHub release: release: types: - published That workflow is good for that project because it's using Release Drafter to generate release notes in the GitHub release. And in general it's good to create a GitHub release because that notifies people who are watching releases on the repo. It may be possible to trigger from a Git tag instead. Or I have seen GitHub Actions to automatically create a GitHub release from Git tag. Yeah, the tricky part is that I can't disable either the releases web UI or git tag pushes, so both use cases need to be supported for Jazzband I'm afraid. I'm a bit wary to let project leads decide on one way to choose since Jazzband's open door policy would still allow bad actors to ignore and create the tag on thir own. And having different workflow setups for all the projects sounds like a maintenance problem. For the case in which a GitHub release is created when a tag is pushed, I think that could lead to a problem when someone were to create a release, which in effect creates the tag and would trigger the release creation again, right? Unless I could check if there is already a release with that name? For the case in which a GitHub release is created when a tag is pushed, I think that could lead to a problem when someone were to create a release, which in effect creates the tag and would trigger the release creation again, right? I don't think so: you can only create a single release for any given tag. For example, this repo already has a 0.2 release. Attempting to create a new release with the same version shows: Ignore, click publish, error: Right, but would the create-release action that you linked above when triggered from a tag push event fail if there would already be a tag? I think so. So I think I'd like to lean towards just listening to pushed tags instead of published releases for triggering the Jazzband release process by default. And project leads can make the optional decision to additionally use release-drafter etc and listen to the "release published" event instead. Good idea, sounds sensible to default to the simpler method, especially to match the Travis way.
2025-04-01T04:36:14.813684
2017-08-14T17:47:50
250103304
{ "authors": [ "jeffward01", "thom1337" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13037", "repo": "jeffward01/Chaincoin-MN-SetupScript", "url": "https://github.com/jeffward01/Chaincoin-MN-SetupScript/pull/3" }
gharchive/pull-request
Added missing dependencies for Ubuntu & added automatic installs Fantastic I am glad it helped! Thats what it is there for! I am super stoked for you to add more features onto it! That would be really helpful to add remote controlled MN support. that would be very useful as most people have 2+ CHC Masternodes! Let me know if I can help :) Thanks again! Just found this: https://github.com/chaoabunga/chc-scripts/blob/master/install-mn.sh Looks like someone already did it?! Kind regards, Thomas Maarseveen This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Any views or opinions presented in this email are solely those of the author. On 14 August 2017 at 18:13, Jeff Ward<EMAIL_ADDRESS>wrote: Fantastic I am glad it helped! Thats what it is there for! I am super stoked for you to add more features onto it! That would be really helpful to add remote controlled MN support. that would be very useful as most people have 2+ CHC Masternodes! Let me know if I can help :) Thanks again! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jeffward01/Chaincoin-MN-SetupScript/pull/3#issuecomment-322324451, or mute the thread https://github.com/notifications/unsubscribe-auth/AFaOOjb0-fQEkAc7N5V5DzO6SbNxyfIgks5sYMZ5gaJpZM4O2rqR .
2025-04-01T04:36:14.825968
2019-06-16T21:34:20
456684535
{ "authors": [ "jenkinsx-bot-sposcar", "sharepointoscar" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13038", "repo": "jenkins-oscar/rollout-app", "url": "https://github.com/jenkins-oscar/rollout-app/pull/3" }
gharchive/pull-request
Environment readfile [APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: To fully approve this pull request, please assign additional approvers. We suggest the following additional approver: sharepointoscar If they are not already assigned, you can assign the PR to them by writing /assign @sharepointoscar in a comment when ready. The full list of commands accepted by this bot can be found here. The pull request process is described here Needs approval from an approver in each of these files: OWNERS Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment :star: PR built and available in a preview environment jenkins-oscar-rollout-app-pr-3 here /approve [APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sharepointoscar The full list of commands accepted by this bot can be found here. The pull request process is described here Needs approval from an approver in each of these files: OWNERS [sharepointoscar] Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment
2025-04-01T04:36:14.835827
2020-12-30T09:53:13
776368927
{ "authors": [ "jenkins-x-bot-test", "jstrachan" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13039", "repo": "jenkins-x/jx3-versions", "url": "https://github.com/jenkins-x/jx3-versions/pull/1930" }
gharchive/pull-request
chore: upgrade bucketrepo [APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: To complete the pull request process, please assign jstrachan You can assign the PR to them by writing /assign @jstrachan in a comment when ready. The full list of commands accepted by this bot can be found here. Needs approval from an approver in each of these files: OWNERS Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment @jstrachan: The following test failed, say /retest to rerun them all: Test name Commit Details Rerun command gsm 5539a644b7a0958ae8833f911eb74de1637d4308 link /test gsm Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here. /retest @jstrachan: The following tests failed, say /retest to rerun them all: Test name Commit Details Rerun command gsm 5539a644b7a0958ae8833f911eb74de1637d4308 link /test gsm tls 5539a644b7a0958ae8833f911eb74de1637d4308 link /test tls Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here. /retest
2025-04-01T04:36:14.837055
2015-09-01T18:32:08
104327774
{ "authors": [ "carlossg", "jenkinsadmin" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13040", "repo": "jenkinsci/docker-ssh-slave", "url": "https://github.com/jenkinsci/docker-ssh-slave/pull/2" }
gharchive/pull-request
Link to GitHub so it shows up at the Docker Hub Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests
2025-04-01T04:36:14.843452
2017-12-12T11:38:18
281352402
{ "authors": [ "FichteFoll", "emako", "jfcherng" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13041", "repo": "jfcherng/Sublime-ASS", "url": "https://github.com/jfcherng/Sublime-ASS/issues/2" }
gharchive/issue
插件能不能追加一个根据颜色码显示对应的颜色 A possible solution would be asking Color Helper for supporting &HBBGGRRAA color format. Done in 2.2.0. Codes are borrowed from my another unpublished plugin OpenUriInBrowser :P Would you mind sharing your rationale for duplicating this behavior in this package over adding the required settings to ColorHelper? I tried to find a statement from @facelessuser regarding supporting rarely used syntaxes but I wasn't able to. Ideally, CH would have the capability of honoring view-specific settings that other packages could then provide through syntax-specific settings files. (related: https://github.com/facelessuser/ColorHelper/issues/60) @FichteFoll Do you mean let's implement the color phantom in CH? That's what I thought back to 2017. Just add something like "allowed_colors": ["abgr"], and some scopes containing color codes. But CH's codebase is a little too large for me. I don't mind we move this feature to CH since CH has more features than simply showing the color. Hm, I don't think it'd be too much work, but I certainly don't have the time to work on it for the forseeable future. Also I'd probably focus on doing that view-specific settings check on CH first because that sure sounds useful.
2025-04-01T04:36:14.862050
2015-08-29T21:12:54
103883430
{ "authors": [ "johannhof", "michyprima" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13042", "repo": "johannhof/emoji-helper", "url": "https://github.com/johannhof/emoji-helper/pull/47" }
gharchive/pull-request
Add click to insert for chrome and firefox @michyprima Hello, thanks very much for you pull request. I'll try to review it as soon as possible, just wanted to let you know you've not been forgotten. :) There are 2 tests failing, in case you want to try and reproduce locally check out https://github.com/johannhof/emoji-helper#testing Thanks again :+1: :+1: Thanks to you! I'm using a build including my commit right now, and CTRL+E/Y correctly opens the emoji window. Searching works, but you need to focus the search box with tab/mouse first. is this the correct behaviour? @michyprima I finally got around investigating the issue, tests were failing because the insertName option is not available on all platforms, you have to wrap it in an if. I made two remarks in the code, please look at them and we can get this merged. :+1: :+1: @johannhof thank you! fixed. should be fine now :+1: Great! let's go! Thanks for the contribution :heart: hello, would you mind updating the extension on the store with this additions built in? I'm looking forward to get it auto-installed wherever I login with my firefox account :) hello, would you mind updating the extension on the store with this additions built in? I'm looking forward to get it auto-installed wherever I login with my firefox account :) yup, let's make a release
2025-04-01T04:36:14.864022
2016-05-26T20:55:11
157077061
{ "authors": [ "coveralls", "johnhamelink", "mjc" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13043", "repo": "johnhamelink/exrm_deb", "url": "https://github.com/johnhamelink/exrm_deb/pull/18" }
gharchive/pull-request
Update timex to 2.1.5 Coverage remained the same at 76.744% when pulling 692f3ae6aa326de68d161530e7e2c8de1eecf2f9 on mjc:update_timex into efc01740cf8fd5146957fb24f7d720c8a8f88ad4 on johnhamelink:master. Brilliant thanks @mjc! Can I ask, are you using exrm_deb in production? How are you finding it?
2025-04-01T04:36:14.865553
2018-03-10T00:24:44
304021152
{ "authors": [ "BenMusch" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13044", "repo": "jolynch/mit-tab", "url": "https://github.com/jolynch/mit-tab/issues/133" }
gharchive/issue
Show available rooms somewhere select * from tab_room as room where room.rank > 0 and not exists (select * from tab_round as round where round.room_id = room.id);
2025-04-01T04:36:14.870676
2015-06-29T21:11:20
91910621
{ "authors": [ "doowb", "jonschlinkert" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13045", "repo": "jonschlinkert/template", "url": "https://github.com/jonschlinkert/template/pull/30" }
gharchive/pull-request
Use app cache damn, sorry @doowb now I know what you meant. I thought I did see this pr but I didn't. I remember reviewing the actual code with you, but I don't know how I didn't see this.
2025-04-01T04:36:14.902459
2016-12-13T16:14:53
195296540
{ "authors": [ "caio1982", "chuckbutler", "marcoceppi" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13046", "repo": "juju-solutions/bundle-canonical-kubernetes", "url": "https://github.com/juju-solutions/bundle-canonical-kubernetes/pull/149" }
gharchive/pull-request
Include containers logs in the collection by filebeat so docker images spilling info to its stdout will be collected too @mbruzek Gonna need your input here I like this change, however we're discussing on breaking out the beats stack into a separate bundle and making them trivial to relate, or yet another bundle permutation. We can carry this patch forward, but it wouldn't be in this repository as its final resting place. But this is a great contribution and thanks for sending it over @caio1982 I'm going to mark this as help-wanted so we remember to track this when that split happens. (expected around the time we release our 1.5 offering) :+1: we should land this now and carry it over into the canonical-kubernetes-elastic bundle when #138 lands SGTM. Landed and issues are linked so we should be G2G
2025-04-01T04:36:14.904976
2015-05-17T17:18:34
77351872
{ "authors": [ "jumanjiman" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13047", "repo": "jumanjihouse/puppet-on-coreos", "url": "https://github.com/jumanjihouse/puppet-on-coreos/pull/5" }
gharchive/pull-request
build and test on circleci https://circleci.com/gh/jumanjihouse/puppet-on-coreos/9 is clean :ship:
2025-04-01T04:36:14.988521
2021-03-25T01:25:58
840473823
{ "authors": [ "Dxu528", "Shmizzy" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13048", "repo": "kcallaghan1/traveltracker", "url": "https://github.com/kcallaghan1/traveltracker/issues/17" }
gharchive/issue
remove/delete locations Way more difficult than initially described, because of how many pieces of the database actually connect back to Locations.
2025-04-01T04:36:15.003219
2020-06-23T13:52:19
643860193
{ "authors": [ "denis-bogdanas", "ehildenb" ], "license": "BSD-3-Clause", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13049", "repo": "kframework/evm-semantics", "url": "https://github.com/kframework/evm-semantics/pull/834" }
gharchive/pull-request
Functional #lookup with Int range checks @denis-bogdanas please add some tests of the new #lookup to tests/specs/functions/lemmas-spec.k
2025-04-01T04:36:15.024060
2020-07-05T08:12:46
651024068
{ "authors": [ "Stranger6667", "codecov-commenter" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13050", "repo": "kiwicom/schemathesis", "url": "https://github.com/kiwicom/schemathesis/pull/644" }
gharchive/pull-request
chore: Refactoring & comments Codecov Report Merging #644 into master will decrease coverage by 0.06%. The diff coverage is 100.00%. @@ Coverage Diff @@ ## master #644 +/- ## ========================================== - Coverage 99.60% 99.54% -0.07% ========================================== Files 57 57 Lines 3541 3506 -35 Branches 610 610 ========================================== - Hits 3527 3490 -37 - Misses 5 6 +1 - Partials 9 10 +1 Flag Coverage Δ #unittests 99.54% <100.00%> (-0.07%) :arrow_down: Impacted Files Coverage Δ src/schemathesis/models.py 99.38% <ø> (-0.02%) :arrow_down: src/schemathesis/_hypothesis.py 100.00% <100.00%> (ø) src/schemathesis/extra/pytest_plugin.py 97.53% <0.00%> (-2.47%) :arrow_down: src/schemathesis/specs/graphql/schemas.py 96.55% <0.00%> (-0.23%) :arrow_down: src/schemathesis/runner/impl/core.py 98.59% <0.00%> (-0.02%) :arrow_down: src/schemathesis/lazy.py 100.00% <0.00%> (ø) src/schemathesis/hooks.py 100.00% <0.00%> (ø) src/schemathesis/stateful.py 100.00% <0.00%> (ø) src/schemathesis/cli/context.py 100.00% <0.00%> (ø) ... and 7 more 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 deee01b...0abeb67. Read the comment docs.
2025-04-01T04:36:15.033236
2020-10-06T23:57:08
716097041
{ "authors": [ "dprotaso", "mattmoor", "n3wscott" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13051", "repo": "knative/pkg", "url": "https://github.com/knative/pkg/pull/1781" }
gharchive/pull-request
2025-04-01T04:36:15.036024
2011-10-22T09:43:35
2022082
{ "authors": [ "stloyd" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13052", "repo": "knplabs/Gaufrette", "url": "https://github.com/knplabs/Gaufrette/issues/24" }
gharchive/issue
[Tests] Skip LocalTest if test directory is not available @Herzult Changed basing on your feedback.
2025-04-01T04:36:15.076795
2016-07-18T15:51:08
166127094
{ "authors": [ "krzysiekpiasecki" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13053", "repo": "krzysiekpiasecki/Predicate", "url": "https://github.com/krzysiekpiasecki/Predicate/issues/6" }
gharchive/issue
New predicate NullPredicate It's a concrete predicate. So make a domain predicate library for php types or incorporate it into this framework.
2025-04-01T04:36:15.094152
2016-11-10T21:28:33
188623095
{ "authors": [ "BrandonLegault", "kshyju" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13054", "repo": "kshyju/ProjectPlanningTool", "url": "https://github.com/kshyju/ProjectPlanningTool/pull/9" }
gharchive/pull-request
Add ignores for user-based Visual Studio files. Fixes issue #8 Merged. Thank you @BrandonLegault 👍
2025-04-01T04:36:15.114796
2019-02-22T02:39:53
413216491
{ "authors": [ "DanyC97", "Rajakavitha1", "cody-clark", "makocchi-git", "zparnold" ], "license": "CC-BY-4.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13055", "repo": "kubernetes/website", "url": "https://github.com/kubernetes/website/pull/12771" }
gharchive/pull-request
Update command outputs to k8s 1.13 based preview is here original Thanks for your PR @makocchi-git !!!! I checked the updates on https://deploy-preview-12771--kubernetes-io-master-staging.netlify.com/docs/tasks/job/automated-tasks-with-cron-jobs/ I just made some suggestions based on the changes you have made. I do not have a 1.13 version environment to check the output so may be I will assign it to someone who can validate it. /assign @chenopis @chenopis Please review this PR for the output in 1.13. @Rajakavitha1 Thank you for your comments. I fixed following: Add downloading yaml process LAST-SCHEDULE to LAST SCHEDULE Update datetime in a pod log (k8s 1.13 is not born yet in 2016...😉) @makocchi-git One slight nit, then it looks good to go @zparnold Thank you for your review! @chenopis ping /lgtm Thanks for the PR, @makocchi-git! This is great! /approve
2025-04-01T04:36:15.120857
2019-03-18T06:54:27
422063339
{ "authors": [ "hiepndd", "kylesliu" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13056", "repo": "kylesliu/awesome-golang-leetcode", "url": "https://github.com/kylesliu/awesome-golang-leetcode/pull/51" }
gharchive/pull-request
Add solution problem 0122 thanks Note : the contributor mode in README will auto-update for me As long as, you mention me into this open-source as a contributor. This is something that must be done and I will consider sorting more submitted content in the future.
2025-04-01T04:36:15.133960
2019-07-03T12:34:12
463726957
{ "authors": [ "gaving", "langjt" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13057", "repo": "langjt/node-http-proxy-json", "url": "https://github.com/langjt/node-http-proxy-json/pull/18" }
gharchive/pull-request
Handle empty response body without throwing JSON parse error Hi @langjt - Any chance of this getting merged? Hi @langjt - Any chance of this getting merged? Sorry, your PR did not solve the problem of empty response body Hi @langjt - Any chance of this getting merged? If the JSON parsing exception, return an empty object?
2025-04-01T04:36:15.179811
2020-05-21T21:59:48
622816633
{ "authors": [ "bors-libra", "davidiw" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:13058", "repo": "libra/libra", "url": "https://github.com/libra/libra/pull/4022" }
gharchive/pull-request
[management] doc update :v: @davidiw can now approve this pull request @bors-libra r=mgorven :pushpin: Commit b9c3bf9 has been approved by mgorven :hourglass: Testing commit b9c3bf95cca6e1a27c0ea6bac5c4ab4e27ce12c7 with merge 67bf8515dfe6dd6b220f816afc740c9452ba48f8... :sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow Approved by: mgorven Pushing 67bf8515dfe6dd6b220f816afc740c9452ba48f8 to master...