text:
Addition of flif crate

🎉

authors: frewsxcv newpavlov

repo: rust-fuzz/trophy-case


text:
Doc usage in-tree

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see CONTRIBUTING.md for more information.

source: gharchive/pull-request

authors: rust-highfive steveklabnik

repo: rust-lang/rustc-serialize

license_type: permissive

license_source: bigquery


text:
One way associations

Would love for people to test this out soon, I'll write up some of the changes needed.
Basically you need to define inverses (if they are defined), similar to how Ember Data works. Other than that things should work.

I'll test it once I have an example to follow 👍

@knownasilya here ya go! https://ember-twiddle.com/ec3a4c625c43e7a38f3c6c0c1b8232ec?openFiles=mirage.scenarios.default.js%2C

Hey this is really great!
Dropping into my GraphQL app Just Continued to Work
myManyRelationship.add( is a welcome addition
Doing this in my scenarios/default.js works as well!:
export default function(server) {
  server.createList('project', 2, {
    todos: server.createList('todo', 3)
  });
}

Nice work @samselikoff 👍

Wow that's great news! I'm writing a blog post now with more information.
One piece that's not in there right now is updating foreign keys after a delete, so you'll need to handle that logic yourself at the moment. I'm going to work it in soon though.

Dependents are now cleaned up after deletions (i.e. foreign key consistency)

@samselikoff I'm using 0.3.0-beta in a new project and it's working fine. Would be nice if you could release a beta6 dropping requirement of Object.assign().

@HeroicEric Thanks for fixing!

Will cut new beta release soon

authors: dustinfarris jelhan knownasilya samselikoff

repo: samselikoff/ember-cli-mirage

license: mit


text:
Update README.md

Pull Request Test Coverage Report for Build 817138454

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.064%

Totals

Change from base Build 817128370:
0.0%

Covered Lines:
438

Relevant Lines:
442

💛  - Coveralls

authors: coveralls samsmithnz

repo: samsmithnz/BattleSimulator

license: MIT

license_source: github-api


text:
Create a symlink to owncloud in the default apache directory (fix #13)

LGTM

authors: QuentinPerez moul

repo: scaleway-community/scaleway-owncloud


text:
Add fallback for wrong class version.

The reason a test was removed is because it relied on the previous brokenness of its instance versions, which would have been corrected by reading its streamers. Now, though, we switch to the right version preemptively, without relying on a deserialization error to kick us back to the streamers. There are now fewer cases that read streamers, but the test was hard-coded to expect it to have read streamers. I don't know of a case to replace it with.


text:
Allow user to set the transpilation target and ts warnings / errors

This is done, though the ts warnings and errors are a bit messy

source: gharchive/issue

repo: scramjs/scram-engine


text:
Split static doc gen into separate package

Done in https://github.com/seagreen/unison-code-explorer/commit/24280c27914075fa1839c96160c3f14065a13b2d

repo: seagreen/unison-code-explorer


text:
web端如何直接加载vue文件

vue 文件需要vue-loader解析成js的

您好，我是黄丽，您的邮件我已收到，谢谢

authors: joeyer leehomeok summerhll

repo: seajs/seajs


text:
Update doc comments and regenerate README.md.

Follow-up to #824.  :)

Also, it looks like you need to re-run npm run gendocs (Travis uses this to catch for inconsistencies between the README and the doc-comments).

Codecov Report

Merging #825 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #825   +/-   ##
=======================================
  Coverage   95.49%   95.49%
=======================================
  Files          34       34
  Lines        1266     1266
=======================================
  Hits         1209     1209
  Misses         57       57

Impacted Files
Coverage Δ

shell.js
100% <ø> (ø)
:arrow_up:

src/sed.js
100% <ø> (ø)
:arrow_up:

src/echo.js
100% <ø> (ø)
:arrow_up:

src/touch.js
100% <ø> (ø)
:arrow_up:

src/ln.js
96.87% <ø> (ø)
:arrow_up:

src/rm.js
85.07% <ø> (ø)
:arrow_up:

src/uniq.js
100% <ø> (ø)
:arrow_up:

src/ls.js
91.48% <ø> (ø)
:arrow_up:

src/mv.js
97.77% <ø> (ø)
:arrow_up:

src/find.js
100% <ø> (ø)
:arrow_up:

... and 15 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 9077f41...7040551. Read the comment docs.

authors: Zearin codecov-io nfischer

repo: shelljs/shelljs


text:
[modify] gws/link : use Gws::Addon::Link (m2)

引き継ぎました。#2085

authors: itowtips tany

repo: shirasagi/shirasagi


text:
テスト(RSpec)

expenses合計の計算やpayの計算ロジック周りだけでも早くかかなければ、テストがすごい大変

バリデーション
・current_userかpartnerが持っているカテゴリ以外は入力できないように。
・noteの文字制限
・入力金額の桁数制限

2019/2/17 進捗
factory_botを使って以下ができるようになった。

1組みのカップルの挿入
1カテゴリーの挿入
自分だけの出費の挿入

2019/3/31 進捗
精算ページの設計


text:
Time function in sAddNote should be lowercase

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/#/issues/SW-15070.
Please use this issue to track the state of your pull request.

Thanks for your PR. Merged with 377dd1e7d8b.

authors: Haehnchen janbuecker shopwareBot

repo: shopware/shopware


text:
sbt 1.1.1

please merge @sksamuel

repo: sksamuel/sbt-scapegoat


text:
Update copyright year to 2016

Change on LICENSE.md too :)

authors: akrabat mathmarques

repo: slimphp/Slim


text:
Blog Page

Can I work on this

Please assign me this issue:)

overflow property should be used for the content.

Excess margin on both the sides on the blog posts.

Hey @smaranjitghose i want too work on this issue.

Cleaning -  Removing

Inline CSS
Deprecated tags like font, center etc.

Sir, may I work on this issue? @smaranjitghose

@smaranjitghose Can I still work on this? I need to link social media icons and improve the first section.

Ya sure

@smaranjitghose Sir, it has the following issues:

Navbar is inconsistent
The styling of heading, subheads etc is completely off from another page
The section is filled with inline styles and I would like to clean that out because it will create specificity issues!
Also I can make the header look a little than it is right now.

May I move forward if you feel they are important to address?

Sure move ahead!

Sure move ahead!

Thank you! :)

authors: Satyam3976 aashimgarg abhu-A-J anushbhatia ashishnagpal2498 goyalmuskan shwetagurnani smaranjitghose


text:
alright

Coverage remained the same at 51.978% when pulling d22c163188e021e4b2ae4df73205375f4e219369 on StefanBranch into 09dff3d335d5cf5dbabb4a30a9147ddc29b41617 on master.

Coverage remained the same at 51.978% when pulling d22c163188e021e4b2ae4df73205375f4e219369 on StefanBranch into 09dff3d335d5cf5dbabb4a30a9147ddc29b41617 on master.

authors: coveralls stefanks

repo: smith-chem-wisc/MetaMorpheus


text:
removed duplicated subtitle

Thanks!

authors: johanneskoester wdecoster


text:
data-live-search="true" not working

More details ? @syan1992

Bug reports must include a live demo of the problem. Per our contributing guidelines, please create a reduced test case (you can use our preconfigured Plunker), and report back with:

your link
Bootstrap version
bootstrap-select version
specific browser and OS details.

If you're not using the latest version of bootstrap-select, please try that as well.

authors: caseyjhol fabienwnklr syan1992

repo: snapappointments/bootstrap-select


text:
Update GitHub actions workflow to also trigger on external pull requests

Fixed

Fixed

repo: softprops/shiplift


text:
Bugfix/n UI 3143 dialog is not dismissed upon navigation change with browser buttons

very nice job overall!

authors: dmytrofirsov dmytrognatyshyn

repo: solarwinds/nova


text:
Fit addon does not work properly when terminal container has heavily customized text-related CSS

Reopening, since this seems to not have been completely solved.

A fix has been opened already -> #43

closing again since #43 was merged

authors: TDaglis akalipetis parisk


text:
Disposals outlets

What's the purpose of this? Is it to drop the items on the floor like the trunk does? Or is it a reverse disposals unit that spits things out with some force (so they can be spaced or thrown towards a recycler / conveyor)

items not exiting a trunk are already flung

authors: DrSmugleaf Peptide90 deltanedas


text:
Protect so that only CDN can call service

Which CDN are you referring to?
Sent with GitHawk

Which CDN are you referring to?

KeyCDN uses a X-Pull secret, that would be nice to implement:
https://www.keycdn.com/support/pull-zone-settings#x-pull

Cloudflare has Authenticated Origin Pulls:
https://blog.cloudflare.com/protecting-the-origin-with-tls-authenticated-origin-pulls/

On Cloudfront you can set custom headers and get a similar feature:
https://www.metaltoad.com/blog/how-to-protect-origin-with-aws-waf-shield

authors: ericwenn timbrandin

repo: spacechop/spacechop


text:
create drone.yml to test drone configurations

This issue should be closed.


text:
use travis to build and test

closed, duplicate of #19

repo: spencergibb/battleschool


text:
update dubbo examples

Codecov Report

Merging #400 into master will decrease coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #400      +/-   ##
==========================================
- Coverage   38.95%   38.91%   -0.05%
==========================================
  Files         209      209
  Lines        5370     5366       -4
  Branches      554      554
==========================================
- Hits         2092     2088       -4
  Misses       3129     3129
  Partials      149      149

Impacted Files
Coverage Δ

...alibaba/nacos/endpoint/NacosDiscoveryEndpoint.java
86.66% <ø> (ø)
:arrow_up:

.../alibaba/nacos/discovery/NacosDiscoveryClient.java
78.78% <ø> (-2.3%)
:arrow_down:

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 bc01277...bed1e91. Read the comment docs.


text:
Update to Spring Boot 2.1.13

Fixed via fa51edb50b3243c655baf9291b5c4cb95c5fb226


text:
Edges of the floor are causing issues with wheel collision

Is this still an issue? https://github.com/srobo/competition-simulator/pull/230 fixed a bunch of things -- any chance it fixed this too?

The arena itself was fully rebuilt in #260.
I'm going to close this as we don't seem to have a reproduction of the issue. However if it reappears we can open this again.

authors: Adimote PeterJCLaw

repo: srobo/competition-simulator


text:
Automatically add new issues to js-waku board

bors merge

repo: status-im/js-waku


text:
Development

Sorry Stef, wrong merging target. This hasn't been tested on FEI microscope....

Hi @taimin, no worries! Nice to see that you picked up working on this. Let me know if there is anything I can do to help.

authors: Taimin stefsmeets

repo: stefsmeets/instamatic


text:
Fix RabbitMQ configuration

Codecov Report

Merging #37 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #37   +/-   ##
=======================================
  Coverage   95.78%   95.78%
=======================================
  Files          63       63
  Lines         996      996
  Branches       43       43
=======================================
  Hits          954      954
  Misses         41       41
  Partials        1        1

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 c0e9575...2f007e9. Read the comment docs.

authors: codecov-io marxjmoura

repo: storefront-community/menu-api


text:
Add option to install using poetry

Wrong repo, sorry

repo: strawberry-graphql/strawberry


text:
feat: Add remove method for useList

:tada: This PR is included in version 5.5.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: TheSharpieOne streamich

repo: streamich/react-use

license: Unlicense


text:
validating CRD

might duplicate with #78

repo: streamnative/function-mesh


text:
Fix required validator and add tests

Coverage increased (+0.0%) to 99.72% when pulling f632c9aa60c3afb73acf9141297c19931a1f83fb on dnephin:fix_validation_bug into d47dfd9b6dbb728f2ccb67c53c01c61b9ae135b3 on striglia:master.

Coverage increased (+0.0%) to 99.72% when pulling f632c9aa60c3afb73acf9141297c19931a1f83fb on dnephin:fix_validation_bug into d47dfd9b6dbb728f2ccb67c53c01c61b9ae135b3 on striglia:master.

Coverage increased (+0.0%) to 99.72% when pulling f632c9aa60c3afb73acf9141297c19931a1f83fb on dnephin:fix_validation_bug into d47dfd9b6dbb728f2ccb67c53c01c61b9ae135b3 on striglia:master.

authors: coveralls dnephin


text:
fix loduser -> loaduser

Thanks for PR @anthonyk1225 👍

repo: sudheerj/reactjs-interview-questions


text:
Deprecate in favour of postcss plugins or tools like cssnext

So I'm thinking that postcss-cli could be viable, but it there is a known issue with postcss-import and 5.x compat currently - https://github.com/postcss/postcss-import/issues/75
I suppose the main reason to use it would be to swap the existing packages over with little fuss, but it does mean each one would need several additional dependencies instead of just one.
One nice touch of postcss-cli is allowing the options to reside in a JSON file which could help.
cssnext is also another option but when I looked at what plugins are actually needed to build SUIT packages it's quite small compared to the several that cssnext provides, so I've always opted to construct the exact pipeline needed per project.
A postcss-suit plugin is an option too (similar to rework-suit) but that felt quite similar to cssnext also.
Thoughts?

The benefits of picking a tool like cssnext could include no maintenance burden, fewer dependencies, clear docs. We might also want to move all these individual components into the main suit repo so they can be developed together with one set of tools...and published as individual packages to npm.

I think `cssnext

no maintenance burden, fewer dependencies, clear docs

Very good points. That kind of decides it.

Has anyone tried to compile Suit Components with cssnext? If that didn't work for you, would it make sense to write a wrapper around it or a custom preprocessor using postcss to make suitcss/preprocessor backwards compatible? @necolas (Twitter) & others do you care about backwards compatibility?

It has worked fine for me in the past, and I did do it that way for a while. Once I realised I only needed a handful of the actual plugins in cssnext (plus wanting to mix others into the pipeline) I moved away from it. However I would agree that for sake of simplicity using cssnext to build SUIT packages would be good

Same for me, I have done it without complication, but currently use my own set of postcss plugins.

I was thinking that maybe we can deprecate preprocessor and create a yeoman generator to create suitcss preprocessors like the following:
postcss()
.use(postcss-import)
.use(suit-comformance)
.use(plugins)
.use(autoprefixer)

where plugins are custom plugins, or a bundle like cssnext, or the current set of suitcss plugins (rework-suit).

Looking back on this, I think the idea of using just the plugins necessary is a good start. After all, cssnext is just a collection of all of those and they are maintained independently so we don't lose any maintenance overhead.
This whole tool could be replaced with postcss-cli and a list of the needed plugins in a JSON file.

@simonsmith I'm good with that

I like @simonsmith's initial thinking around constructing the exact pipeline each project needs, such that we can:

Keep the build as simple and modular as possible
Avoid surprises that can occur when the css-next-big-thing is refactored
Isolate build issues per plugin / module
Get more flexibility to experiment / prototype with features that css-next-big-thing might not support
Upgrade parts in the event that something better comes along (underscore vs. lodash).

It would be great if it also supported agile development / watching with browsersync, etc.

It would be great if it also supported agile development / watching with browsersync, etc.

I think this should be as simple as possible, just a list of postcss plugins. Baking that stuff in seems way of out scope to me.

I think this should be as simple as possible, just a list of postcss plugins. Baking that stuff in seems way of out scope to me.

@timkelty  I'm a little surprised because you seem to like the idea here?
https://github.com/suitcss/suit/issues/115
I'm not necessarily leaning toward any one solution.  I do like to have the ability to easily add features as they start to make sense in terms of maximizing productivity both for users and maintainers, and to switch out packages that are under performing or obsolete.
Something in line what what is done in this article, Breaking up with Sass, seems like it serves as a good cross section for the various ideas discussed so far.

Also seems like cssnext is moving to just a postcss plugin anyway - https://github.com/cssnext/postcss-cssnext#readme
I vote deprecate this repo and all the components move to using postcss in their relevant package.json files. We coud do something like in npm run build:
postcss -u postcss-import -u autoprefixer -u postcss-custom-media -d build -o build.css

Or include a config json file in each repo if that gets too unwieldy.

@timkelty I'm a little surprised because you seem to like the idea here?

For me the difference is including as part of the preprocessor vs. part of the testing suite. If we can get BS to pop open browsers at all different breakpoint widths when running a test, I'm all for that.

@simonsmith the postcss-cli option sounds good to me. The other option would be to pick another task runner (Gulp, etc) and run Postcss through there.
When it comes down to it, aren't we mostly just talking about what our test suite is going to run? It seems like most people using this would be feeding it into an existing postcss pipeline.

I think the focus of this issue is replacing this pre-processor with postcss. Implementing a browser testing solution is not trivial and is definitely a separate task.
I think a good approach for now is get all the packages of the dead rework ecosystem.
Thoughts?

Just read up on it some more, and it seems like we can easily wrap postcss in gulp if we need to augment the workflow later on, so :+1:

@simonsmith agreed - migration to Postcss should be top priority.
As far as how to build Postcss, I think our viable options are:

use postcss-cli
use Gulp or another build tool to run things through Postcss

A postcss-suit plugin is an option too (similar to rework-suit) but that felt quite similar to cssnext also.

I didn't include making a postcss-suit plugin, as I don't think it solves any problems. We would still need something on top of that that actually did the build.

I'm not sure what advantage gulp would bring. It tends to be the right tool when you want to perform several different transforms on a stream, but here we just want to run one plugin.
Also, in every project I've used SUIT in I've found there already tends to be a pipeline setup (be it gulp, grunt or whatever) and the CSS files can be put through that directly after being installed via npm. Be interested to know other experiences.
I've kinda seen the npm run build tasks as a lightweight way to build the SUIT packages if you need it, but for more complex projects they tend to have their own build pipelines already.

@simonsmith Agreed about Gulp, just wanted to list our options.
So I think we're on the same page?
Proceed converting everything to Postcss, and use postcss-cli.

Sounds good to me. Maybe we can get a PR on one component to see how it works and discuss it there.

+1 for @simonsmith's idea.

Yesterday @giuseppeg and I had a discussion about how viable this is and what we'd lose (bower support, issues, PRs and git tags) and it seems like a lot to give up vs the gain. Plus the tooling for a monorepo isn't massively easy.
I think we're leaning towards refactoring this tool to use a handful of PostCSS plugins directly. It could have the bem-linter rolled in, and perhaps even stylelint. Would also consider simplifying it by removing the minification option, and leaving that up to to existing build pipelines that most users should have (cssnano spring to mind here).
Using cssnext directly doesn't offer much as it uses multiple plugins anyway, and from what I understand it is soon to become just a postcss plugin itself - https://github.com/cssnext/cssnext/issues/230
Would make sense to manage the package from one single build tool. We could then deprecate/remove rework-suit and rework-suit-conformance
Here's our discussion from yesterday - https://gitter.im/suitcss/suit?at=564902c58b242470793dea82
But i think I'm sold on the refactor route

@simonsmith @giuseppeg glad you guys discussed this, I've been leaning in this direction as well.
Could a possible tradeoff be to maintain all the docs and tooling in the main SUIT repo, and have each package have the main repo as a dependency?

authors: giuseppeg necolas oleersoy simonsmith timkelty

repo: suitcss/preprocessor


text:
added initial project template from yo aspnet

looks good

authors: imachiever sumitjolly

repo: sumitjolly/DotNetCoreLinux


text:
Fix reflection baking is disabled in unity 2019 when executed as editor mode.

Thanks!

repo: svermeulen/Extenject


text:
Meetar/tweaks

@nvkelso Please to review!

Thanks!

authors: meetar nvkelso

repo: tangrams/outdoor-style


text:
Fix typo in index.html

Whoops, thank!

authors: JasonEtco maxbeier

repo: tawian/text-spinners


text:
updating parameter passing to rl module

Need to resolve conflicts, or is this already corrected anyway?

authors: lukaszkaiser piotrmilos


text:
Branch 170096704

Jenkins, test this please.

repo: tensorflow/tensorflow


text:
Fixes all Grunt semicolon-related warnings

Perfection! LGTM, ready to land

FTR, I pulled the branch and ran locally to confirm, but in the future travis-ci can do that confirmation for us :)


text:
bump boots to 03795133adf7f7177677f3d58a0018e2

:thinking: why does the PR title not match the sha-... ?

Who knows what I copy pasted @mmlb !

:stuck_out_tongue:

authors: gianarb mmlb

repo: tinkerbell/sandbox


text:
support deletion in the backend interface

solved in https://github.com/tivvit/shush/commit/cfbf59d77ba9c2c8e5d1d56fc8f9829d4ff76290

repo: tivvit/shush


text:
Add Discord + Fix Tokyo Metro typo

Thanks

repo: toddmotto/public-apis


text:
Add user guide

https://old.reddit.com/r/RemarkableTablet/comments/r9io3l/1liner_to_build_an_app_gui_included/

From #13:

Regarding setting a default value in the environment for CMAKE_TOOLCHAIN_FILE, I’m actually not convinced it’s the best solution. Consider projects that need to build some executables with the “normal” gcc compiler, and then use the resulting executables in the cross build [1]. Setting a default for CMAKE_TOOLCHAIN_FILE in this case will break the part that needs the normal gcc. We would need to unset the env var before running cmake to build the first part, and then setting the env var back before building the second part. This is also the reason why I haven’t overridden the CC and CXX env vars in the image: some parts of the build may want the normal gcc, and some other parts the cross gcc. I think it’s best that each part explicitly declares which compiler it wants, for example by passing the CMAKE_TOOLCHAIN_FILE argument for CMake projects, or setting the CXX variable, etc.
As you’ve mentioned, having such a behavior differ from the oecore toolchain means both toolchains need to be handled differently. This may not be desirable. But the oecore behavior is really not ideal for projects having a dual-compiler layout.
[1] I have encountered such cases before. This can be used for example to generate some code that is used for the second half of the build.

Originally posted by @matteodelabre in https://github.com/toltec-dev/toolchain/issues/13#issuecomment-1008074952

repo: toltec-dev/toolchain


text:
Added FTPProvider

@tomaszzmuda  : i have made a changes corresponding to your comment. Is it okay for you ?

@tomaszzmuda : hope it'll be ok this time :)


text:
tutorial/06-bindings/07-multiple-select-bindingsの翻訳

ここをやります

私は次のAPIドキュメントの翻訳の準備などを行うため、一旦こちらのアサインから抜けます。
もしやってくださる方がいらっしゃったら、お願いいたします。

これやっておきます

すみません、ありがとうございます！

authors: myLifeAsaDog tomoam

repo: tomoam/svelte-site-jp


text:
Add feature to configure DI via the config

@tomphp
Looks good, and restores the functionality from 1.0, so :+1:!

authors: localheinz tomphp

repo: tomphp/config-service-provider


text:
Tests: Extensions

Current coverage is 78.34% (diff: 96.55%)

Merging #950 into master will increase coverage by 0.98%

@@             master       #950   diff @@
==========================================
  Files           131        136     +5
  Lines          7006       7223   +217
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           5420       5659   +239
+ Misses         1586       1564    -22
  Partials          0          0

Powered by Codecov. Last update a7870fa...80d32f2

authors: codecov-io tonioo

repo: tonioo/modoboa

license: isc


text:
#5994 fix comboBox setting value

i am not seeing sync from kernel to client:

Fixed

still not seeing it

I have removed some part of the widget as Michael's changes for value in selectWidget are already in master.

authors: mjurowicz-xsolve scottdraves

repo: twosigma/beakerx


text:
CBOR/ByteString squash

Was attempting to keep the contributors intact during the squash.
When doing an interactive rebase, the merges caused a number of conflicts that needed to be resolved. Rather than having to deal with resolving conflicts, I attempted to squash locally using the technique described in https://stackoverflow.com/a/44789323/196486. Unfortunately this technique does not preserve the other contributors whom helped with this effort.
I was hopefully that GitHub had some magical way of squashing while preserving contributors; unfortunately it appears that it may use a similar technique as is linked above (and did not preserve other contributors in the squashed commit).


text:
Document the Java FFI

Done, we have the docs on eta-lang.org now.

repo: typelead/eta


text:
OneBox: Expose front-end service in the interface

Coverage decreased (-0.04%) to 66.411% when pulling ad86cc1a5c5afef15907220ac9b34afa160ce076 on sivakku:interface_onebox into 20f962fce8dfc7290c42e71daae04b1fe8eae309 on uber:master.

authors: coveralls sivakku

repo: uber/cadence


text:
Add new nominee - QGIS

@rachita19082 could you please merge pull requests #460, #459, #458, #457, #456 & #455 into this pull request for easier tracking of your submissions, then close all the remaining pull requests. Thanks.

@rachita19082 could you please merge pull requests #460, #459, #458, #457, #456 & #455 into this pull request for easier tracking of your submissions, then close all the remaining pull requests. Thanks.

Sure, I will merge all the PRs.

@nathanbaleeta I have made the required changes. Please let me know if anything else is needed.

repo: unicef/publicgoods-candidates


text:
Add preview of selected controller in list

Linked Issue: #22.


text:
Qa

Coverage decreased (-0.06%) to 85.643% when pulling daccc7616588f9f1f83333cc26d83e5eae0f8380 on qa into 2505e81bd179a8ab6b5d4be7034c8de1f3e32242 on master.

authors: coveralls mikeseibel

repo: uw-it-aca/uw-restclients


text:
怎样删除有数据的数据库和里面的全部数据呢

调用删除表的接口即可，参见https://vearch.readthedocs.io/zh_CN/latest/use_op/op_space.html#id4

repo: vearch/vearch


text:
Add Mathias Brossard to the AUTHORS file

AWS CodeBuild CI Report

CodeBuild project: Veracruz
Commit ID: 78c35b194e39ee278fcd98ec4bf8deb307f3b685
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

+1 reached, merging.

repo: veracruz-project/veracruz


text:
add 02-where

👍

Agree with Marta's comments otherwise +1

authors: knaufk morsapaes sjwiesman

repo: ververica/flink-sql-cookbook


text:
tap on day X, create event for that date

done #166

repo: vinhnx/Clendar


text:
feat(operation-button): 点击按钮的时候，可以通过confirmText显示弹窗进行二次确认

good。目前配置event的方式也能支持：
deleteItem: {
type: 'button',
label: '删除',
event: 'confirm:二次确认弹窗信息? delete'
}

repo: vipshop/ams


text:
Please, document where the script should be located

What, why?

authors: agustisanchez aviau

repo: vishnubob/wait-for-it


text:
enable buffer default for node

Unfortunately this is a breaking change

What was the purpose of this @lyykfi?

authors: lyykfi niftylettuce pornel

repo: visionmedia/superagent


text:
Current page and size not set correctly by default (when undefined)

Fixed as part of #11

repo: vlsergey/react-bootstrap-pagetable


text:
no return comment __construct

We prefer to always put the return annotation in order to differentiate between actually returning nothing, and just forgetting to document the return type.

return type does not match
A number of parameters, their names or types  (if any) in PHPDoc comment do not match the respective function or method declaration.
but https://github.com/phpDocumentor/fig-standards/blob/master/proposed/phpdoc.md#715-return
[functions and methods without a return value: the @return tag MAY be omitted here, in which case an interpreter MUST interpret this as if @return void is provided.]

The return type does match. That function has do return statement, so it doesn't return anything.
I'm not sure what you mean by quoting those docs? They don't back up your point?

Locking since this discussion isn't useful.

authors: GrahamCampbell nicolas-wallerand

repo: vlucas/phpdotenv


text:
vnpy 2.0大约什么时候提供release版本和对应文档呢？

目前已经收尾vnpy和vnstation的2.0开发，正在做VNConda的，不出意外程序应该下周发布，然后开始文档的编写。

authors: Paleozoic vnpy

repo: vnpy/vnpy


text:
Display text matches Col.span value

Thanks!

authors: ckmahoney vrimar

repo: vrimar/construct-ui


text:
src/v2/guide/unit-testing.md

Lưu ý là dòng cuối cùng không dịch, vì bản tiếng Anh có thể cũng sẽ thay đoạn này bằng giới thiệu cho vue-test-utils.


text:
feat(reactivity): improve types

same problem with #106 #113 :)

Okay, I will close it.

repo: vuejs/vue-next


text:
chore(share): menuitem tag is deprecated

Thanks but it's still worth having in the list as it could collide in Firefox


text:
Rework builder to diff and mutate existing tree over time

Fixed by #179

repo: waybeams/waybeams


text:
Padding on outlined mode

We need to have it for all variants of the input: https://callstack.github.io/react-native-paper/text-input.html
so
mode=flat/outlined
in combination with
dense=true/false

add to examples so it won't break in the future

authors: RichardLindhout Rubenvdveen


text:
Improve readability of text

I don't see any improvement with this change.
Can you please expand and tell me how I can see any changes impled by this CSS?
The browsers you see an improvement with for exampl?

repo: web-tiki/responsive-grid-of-hexagons


text:
get new code

fllow new code

repo: wei-yi/presto


text:
Feature/cache adapters

Merged to zendframework/zf2 master. Thanks!

authors: ezimuel weierophinney


text:
Fix minor issues

Coverage remained the same at 99.497% when pulling fe3da47ee9a429a59ad83de229492db87617f9d0 on lqez:minor/fix-typo into 8bfd5c8f77800c3257b70f16969a7fe2ad8f01bc on what-studio:master.

authors: coveralls lqez

repo: what-studio/tossi


text:
Fix typos in Readme.md

Thanks @jamespfarrell !

authors: jamespfarrell wighawag

repo: wighawag/hardhat-deploy


text:
WFLY-9534 Remove some unused code from the EJB subsystem

LGTM

authors: bstansberry stuartwdouglas

repo: wildfly/wildfly


text:
display webmentions

done in 4307a7bbdeecaa32c3357fb8c257c89ae90c68a6 and related commits


text:
Fix broken demo link in README file

Thanks @allanpereira

authors: allanpereira caioincau

repo: wirecardBrasil/awesome-mask


text:
Improve height offset limit

https://github.com/wiremod/advdupe2/blob/master/lua/weapons/gmod_tool/stools/advdupe2.lua#L1069

Also increase 16k to 32k


text:
Fix PVR section back navigation

This should fix #508?

authors: SyncedSynapse poisdeux

repo: xbmc/Kore


text:
Feat/layouts

@ehtishamSaleem @midmiddleton I think we should be okay to squash these commits into master, what do you guys think? These changes appear to be mostly additions, so I don't expect any change in functionality to existing stuff... In theory.

@ehtishamSaleem @midmiddleton I think we should be okay to squash these commits into master, what do you guys think? These changes appear to be mostly additions, so I don't expect any change in functionality to existing stuff... In theory.

yeah think we can merge this is in, we will have to if the stuff of on UI has gone in.

Yeah looks like sensible changes to me 👍

authors: CallumEddisford adamwiteszczak ehtishamSaleem midmiddleton

repo: xedi/sdk-js


text:
项目数据访问不到

嗯，刚刚打开看了下，确实没有数据。应该是网站挂了或者是规则变了，有空了我去看看原因。

authors: tardisTao xfhy

repo: xfhy/DeepNight-in-kotlin


text:
Sublime-like changes

@msirringhaus do you mind explaining a bit what you added in https://github.com/xi-frontend/xi-term/pull/109/commits/db5488b012b922239bd4a68f60fd99f7dcbcedca ? Where are the cursors rendered here? It seems like what this adds is the ability to select multiple regions corresponding to a search result, is that right?

It seems like what this adds is the ability to select multiple regions corresponding to a search result, is that right?

That is correct. Its the ctrl+d-feature of sublime. You either pre-select some text and press ctrl+d or you press ctrl+d twice to select the current word under the cursor and go from there. Luckily, that is xi-cores behavior too, when trying to "select under cursor" + "find next" with no selection.
Once you have something selected, repeated ctrl+d presses will search for the selected text and add a new cursor there.

Where are the cursors rendered here?

Indeed, they are currently not. xrl is hiding the annotations-part of the update notification from xi-core. In it would be the information of where the cursors are (albeit a bit clumsy to parse out of (see here )

Selecting lines suffers the same issue than https://github.com/xi-frontend/xi-term/pull/99#issuecomment-488005732

@msirringhaus ctrl+d is pretty neat :D

@msirringhaus I've looked at every commit at this point although I just glanced at some, and I played a bit with the editor. This is pretty awesome work, and I'd love to integrate it into xi-term. But as it stands, this PR a bit too big to review properly, and I won't be able to do a good job at merging it. Do you think you could try to split it into smaller PRs and rework the git history so that commits don't have some unrelated changes? (No pressure, I'm not in a hurry).

In principle yes. First off, it might be way less work to just review HEAD as it is. Most of the commits are me reworking my own features a bazillion times. Thus adding a lot of noise which is not visible on HEAD anymore.
But if that is still too big, I could in theory split it up. But do you require for those intermediate commits to actually work and compile? That would be a lot of work, and unfortunately my "work on whatever project you want"-week is now over :-( So time is again limited.

authors: little-dude msirringhaus

repo: xi-frontend/xi-term


text:
Repackage and deploy to pypi

Fixed with 2e03b01726f00bf3a092325c0f7639b28d5da16d.

repo: xn-twist/xn-twist


text:
How to customize the Stickers Tool or create my own custom Tool and place it into the list?

This is what the stickers look like after the implementation. But I have to replace the stickers with my own path which contains .json file all the urls for the images. And load them in multiple lines as shown below:

hello Rakesh !
can you tell me how u did for iPhone X safe area padding ?
thanks

hello Rakesh !
can you tell me how u did for iPhone X safe area padding ?
thanks

Make sure you are not navigating through the base navigation controller when you open CLImageEditor VC

repo: yackle/CLImageEditor


text:
Added Elevator Pitch section

Thank you for your contribution! This is great and I would very much like to merge it. Just to check, is this content entirely original? If it isn't, it would be good to add them as references. Else, all is good and I'd merge it.
More PRs are welcome! It's a good way to contribute to Hacktoberfest 😎

@yangshun Yes, it is original content.

That's awesome! Merging this. Thanks! (:

authors: cburwell yangshun

repo: yangshun/tech-interview-handbook


text:
Typo guides pt-BR [ci skip]

https://github.com/yiisoft/yii2/commit/44c70a8011504b3fd01f2e51d40a6bdd36d316d0 Thanks!

authors: davidsonalencar samdark


text:
is it possible to resize the nodes?

I mean you can customize the CSS however you want but you should just create a custom node that fits your needs.

Do you have a suggestion on how to do this?

You can look at the custom node demo (https://github.com/zHaytam/Blazor.Diagrams/tree/master/samples/SharedDemo/Demos) and the sample project (https://github.com/zHaytam/Blazor.DatabaseDesigner).

I assume the question has been answered, if not, feel free to re-open!

authors: carlosast zHaytam


text:
upgrade: .travis.yml Updated to 1.10

@elithrar
I fixed one point so that the test passed.
Is there anything else to fix?

The version specification of go is made to all string according to the doc of travis.
https://docs.travis-ci.com/user/languages/go/

Only if you provide a string:
https://docs.travis-ci.com/user/languages/go/#Specifying-a-Go-version-to-use
See this tweet: https://twitter.com/dgryski/status/964626204488695808 - if
you just provide 1.10 instead of “1.10” you will not get the intended
behavior.
On Tue, Mar 6, 2018 at 1:35 PM smith30 notifications@github.com wrote:

The version specification of go is made to all string according to the doc
of travis.
https://docs.travis-ci.com/user/languages/go/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zenazn/goji/pull/192#issuecomment-370669127, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AABIcFj-6Ec6onr_3_WEt0pl2Y2ht92nks5tbiAOgaJpZM4SeFaF
.

i fixed. thanks!

Thanks for working on this! I left one comment about the change you made to the test—I'm curious why it started failing

Go 1.10 runs go vet on tests: https://golang.org/doc/go1.10#test

The go test command now automatically runs go vet on the package being
tested, to identify significant problems before running the test. Any such
problems are treated like build errors and prevent execution of the test.
Only a high-confidence subset of the available go vet checks are enabled
for this automatic check. To disable the running of go vet, use go test
-vet=off.

This is why this occurs. It's because many users are likely comparing the
wrong thing, even though that's actually what we want here. The error is
called here: https://golang.org/src/cmd/vet/print.go#L622
On Wed, Mar 7, 2018 at 5:07 PM smith30 notifications@github.com wrote:

@smith-30 commented on this pull request.
In web/func_equal_test.go
https://github.com/zenazn/goji/pull/192#discussion_r172777162:

@@ -65,7 +65,7 @@ func TestFuncEqual(t *testing.T) {
r := funcEqual(test.a, test.b)
if r != test.result {
t.Errorf("funcEqual(%v, %v) should have been %v",

		test.a, test.b, test.result)

		test.a(), test.b(), test.result)

this is strange. specified function test is succeeded.
failed
$ go test -v .# github.com/smith-30/goji/web
./func_equal_test.go:67: Errorf format %v arg test.a is a func value, not called
FAIL    github.com/smith-30/goji/web [build failed]
succeeded
Running tool: /usr/local/bin/go test -v -timeout 15s github.com/smith-30/goji/web -run ^TestFuncEqual$
=== RUN   TestFuncEqual
--- PASS: TestFuncEqual (0.00s)
PASS
ok  	github.com/smith-30/goji/web	0.014s
Success: Tests passed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zenazn/goji/pull/192#discussion_r172777162, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AABIcGzBZ3RFepYzJ58wibqNjCMBnDR-ks5tb6NHgaJpZM4SeFaF
.

@elithrar
Thank you very much for your detailed information.
I think it would be better to write the code so that vet passes through rather than disabling vet.
what do you think of this?

Oh, interesting! (TIL)
Can we print the functions out with %p instead? https://play.golang.org/p/PiqcpZey7qG

@zenazn
I updated %v to %p, all test is passed! thank you!

Thanks!

authors: elithrar smith-30 zenazn

repo: zenazn/goji


text:
你好我想统计stream模式下的同类数据，有类似的lua吗

你是想统计location的吗？
如果是的话，可以改造这个lua脚本。通过获取uri.

我是想统计请求数和延迟，然后你的这个似乎是个http使用的,stream模式无法统计

您好，可以给我你的QQ或者其他联系方式吗？

您好，我们现在使用了nginx和tomcat的架构，nginx每秒扛1W8的请求，现在会出现nginx和tomcat不同步扛不住的问题，用的是upstream模式，现在希望使用stream模式，但是我们要求延迟有严格的要求，没有了监控就没办法进行调试，所以希望您能教我一下怎么是用stream模式的延迟监控。


text:
Update to bitvec 0.22

The MSRV bump to 1.51 is necessary as that's the MSRV for bitvec 0.22, but we get const generics for it, so I'm happy.

repo: zkcrypto/ff


text:
template: change the delete button with delete icon.

Duplicate of #17691
Why did you create two PRs?

authors: Signior-X mandepsingh

repo: zulip/zulip


text:
docs: Add user guide for Browse and join streams feature

Automated message from Dropbox CLA bot
@synicalsyntax, it looks like you've already signed the Dropbox CLA. Thanks!

@synicalsyntax, looks good. You probably want to fix your commit message. You will need another review as well. Thanks.

@synicalsyntax Thanks for all your hard work on this!
@timabbott This is ready to merge pending Travis.  If we refine streams some in the next couple weeks, we may want to remember to give this doc another pass, but we have pretty recent screenshots of the latest design changes.
GCI mentors--I have approved this task already.

I did a quick pass on the doc to change:

line-wrap many long lines
Designed streams -> default streams
join -> subscribe to

(The last two being how Zulip refers to these features) and merged this.  Thanks @synicalsyntax!!

authors: showell smarx synicalsyntax timabbott umairwaheed


text:
Add node tests for message_edit.get_editability.

Automated message from Dropbox CLA bot
@rishig, it looks like you've already signed the Dropbox CLA. Thanks!

@timabbott updated!

Looks great, merged, thanks @rishig!!

authors: rishig smarx timabbott