profile
viewpoint

moonchanyong/adt 0

Almighty Data Transmitter

moonchanyong/algorithm 0

baekjoonandcodeground

moonchanyong/amphtml 0

AMP HTML source code, samples, and documentation. See below for more info.

moonchanyong/amp_translate 0

amp공식 문서 번역하면서 이해하려고

moonchanyong/angularspree 0

Angular(5.1) E-Commerce front-end framework

moonchanyong/anime 0

JavaScript animation engine

moonchanyong/ant-design 0

🌈 A UI Design Language

moonchanyong/armeria 0

Asynchronous RPC/REST library built on top of Java 8, Netty, HTTP/2, Thrift and gRPC

push eventline/armeria

minwoox

commit sha 9fb000b85629ccfcf4531ec0f8e42b1f69bf4d24

Add missing dependency for example

view details

push time in 3 hours

push eventline/armeria

Snōwball

commit sha 70cc3552bb856148b316ab54e187a1400b99a6e9

nit: service misspelled in example (#3211)

view details

push time in 3 hours

PR merged line/armeria

nit: service misspelled in example cleanup
+1 -1

1 comment

1 changed file

tobias-

pr closed time in 3 hours

startedDmitrySoshnikov/syntax

started time in 12 hours

Pull request review commentline/armeria

nit: service misspelled in example

 executor.scheduleWithFixedDelay(() -> {     HttpRequest req = HttpRequest.of(HttpMethod.POST, "/expire_stall_sessions");     ServiceRequestContext ctx = ServiceRequestContext.of(req);     try {-        HttpResponse res = sessionManagementService.servce(ctx, req);+        HttpResponse res = sessionManagementService.service(ctx, req);

haha, I'll fix it

tobias-

comment created time in 19 hours

pull request commentline/armeria

Fix flaky test in `ZooKeeperRegistrationTest.curatorRegistrationSpec()`

Codecov Report

Merging #3210 (17c8f50) into master (535873b) will decrease coverage by 0.01%. The diff coverage is n/a.

Impacted file tree graph

@@             Coverage Diff              @@
##             master    #3210      +/-   ##
============================================
- Coverage     74.18%   74.16%   -0.02%     
+ Complexity    12887    12886       -1     
============================================
  Files          1119     1119              
  Lines         48743    48743              
  Branches       6230     6230              
============================================
- Hits          36158    36150       -8     
- Misses         9406     9412       +6     
- Partials       3179     3181       +2     
Impacted Files Coverage Δ Complexity Δ
...inecorp/armeria/common/ClosedSessionException.java 54.54% <0.00%> (-18.19%) 5.00% <0.00%> (-1.00%)
...orp/armeria/client/eureka/EurekaEndpointGroup.java 60.71% <0.00%> (-3.58%) 23.00% <0.00%> (-1.00%)
.../armeria/client/endpoint/dns/DnsEndpointGroup.java 78.12% <0.00%> (-3.13%) 13.00% <0.00%> (-2.00%)
...meria/client/DefaultDnsQueryLifecycleObserver.java 73.23% <0.00%> (-2.82%) 11.00% <0.00%> (-1.00%)
...com/linecorp/armeria/server/saml/SamlEndpoint.java 62.50% <0.00%> (-2.50%) 10.00% <0.00%> (-1.00%)
...eria/internal/common/DefaultSplitHttpResponse.java 77.84% <0.00%> (-2.40%) 14.00% <0.00%> (ø%)
.../com/linecorp/armeria/server/docs/ServiceInfo.java 78.94% <0.00%> (-1.76%) 20.00% <0.00%> (-1.00%)
...a/com/linecorp/armeria/client/HttpChannelPool.java 79.77% <0.00%> (-1.67%) 67.00% <0.00%> (-2.00%)
...corp/armeria/client/RefreshingAddressResolver.java 76.42% <0.00%> (-1.43%) 19.00% <0.00%> (ø%)
...corp/armeria/internal/common/KeepAliveHandler.java 82.91% <0.00%> (-1.27%) 35.00% <0.00%> (ø%)
... and 11 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 535873b...17c8f50. Read the comment docs.

ikhoon

comment created time in 19 hours

Pull request review commentline/armeria

nit: service misspelled in example

 executor.scheduleWithFixedDelay(() -> {     HttpRequest req = HttpRequest.of(HttpMethod.POST, "/expire_stall_sessions");     ServiceRequestContext ctx = ServiceRequestContext.of(req);     try {-        HttpResponse res = sessionManagementService.servce(ctx, req);+        HttpResponse res = sessionManagementService.service(ctx, req);

I think it's serve 😄

tobias-

comment created time in 19 hours

pull request commentline/armeria

nit: service misspelled in example

Codecov Report

Merging #3211 (97017ce) into master (535873b) will decrease coverage by 0.07%. The diff coverage is n/a.

Impacted file tree graph

@@             Coverage Diff              @@
##             master    #3211      +/-   ##
============================================
- Coverage     74.18%   74.10%   -0.08%     
+ Complexity    12887    12873      -14     
============================================
  Files          1119     1119              
  Lines         48743    48743              
  Branches       6230     6230              
============================================
- Hits          36158    36121      -37     
- Misses         9406     9438      +32     
- Partials       3179     3184       +5     
Impacted Files Coverage Δ Complexity Δ
...inecorp/armeria/common/ClosedSessionException.java 54.54% <0.00%> (-18.19%) 5.00% <0.00%> (-1.00%)
...om/linecorp/armeria/client/HttpSessionHandler.java 72.18% <0.00%> (-8.88%) 50.00% <0.00%> (-4.00%)
.../armeria/client/endpoint/dns/DnsEndpointGroup.java 78.12% <0.00%> (-3.13%) 13.00% <0.00%> (-2.00%)
...meria/client/DefaultDnsQueryLifecycleObserver.java 73.23% <0.00%> (-2.82%) 11.00% <0.00%> (-1.00%)
...com/linecorp/armeria/server/saml/SamlEndpoint.java 62.50% <0.00%> (-2.50%) 10.00% <0.00%> (-1.00%)
...eria/internal/common/DefaultSplitHttpResponse.java 77.84% <0.00%> (-2.40%) 14.00% <0.00%> (ø%)
...a/com/linecorp/armeria/client/HttpChannelPool.java 79.50% <0.00%> (-1.94%) 67.00% <0.00%> (-2.00%)
...linecorp/armeria/server/file/DeferredHttpFile.java 50.00% <0.00%> (-1.62%) 14.00% <0.00%> (-1.00%)
...corp/armeria/client/RefreshingAddressResolver.java 76.42% <0.00%> (-1.43%) 19.00% <0.00%> (ø%)
.../linecorp/armeria/client/Http1ResponseDecoder.java 66.24% <0.00%> (-1.28%) 43.00% <0.00%> (-2.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 535873b...97017ce. Read the comment docs.

tobias-

comment created time in 20 hours

PR opened line/armeria

nit: service misspelled in example
+1 -1

0 comment

1 changed file

pr created time in 20 hours

PR opened line/armeria

Reviewers
Fix flaky test in `ZooKeeperRegistrationTest.curatorRegistrationSpec()` cleanup

Motivation:

Occasionally ZooKeeperRegistrationTest failed because of a duplicate port number.

ZooKeeperRegistrationTest > curatorRegistrationSpec() FAILED
    org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a lambda expression in com.linecorp.armeria.common.zookeeper.ZooKeeperTestUtil that uses com.linecorp.armeria.server.Server
    Expecting code not to raise a throwable but caught
      <"java.util.concurrent.CompletionException: io.netty.channel.unix.Errors$NativeIoException: bind(..) failed: Address already in use

Modifications:

  • Allocate a new port if a server fails to start

Result:

  • Clean up flaky tests
+25 -8

0 comment

1 changed file

pr created time in 20 hours

issue openedline/armeria

Return custom eror page when the execution time is long then armeria sends a response with 503

Our service, https://store.line.me using armeria and embedding tomcat service. ref: https://armeria.dev/docs/server-servlet

When tomcat execution is long then ameria got timeout error, "503 Service Unavailable" message appears in browser. We would like to response custom error page to users instead of "503 Service Unavailable" message.

As-Is: Just "503 Service Unavailable" message. It's not user friendly.

To-Be: Should be an error page with message and image. It's more user friendly. ex.twitter c9dd260c

FYI: our service's code base is not public but I prepared a project with same architecture. ref: https://github.com/policeman-kh/armeria_spring_web

created time in a day

pull request commentsindresorhus/awesome

Add Games of Coding

Thanks for making an Awesome list! 🙌

It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

michelpereira

comment created time in a day

release line/armeria

armeria-1.3.0

released time in a day

pull request commentsindresorhus/awesome

Add Games of Coding

unicorn

michelpereira

comment created time in a day

PR opened sindresorhus/awesome

Add Games of Coding

https://github.com/michelpereira/awesome-games-of-coding/

The purpose of this list is to practice a new programming language by coding a game, solving puzzles or teaching robots to attack and defend itself like in Vindinium.

  • The list is around for 4+ years.
  • Have been discussed on Hackernews: https://news.ycombinator.com/item?id=13566247
  • Reviewed PRs: https://github.com/sindresorhus/awesome/pull/1886
  • Comments made: https://github.com/sindresorhus/awesome/pull/1912#issuecomment-736183488
  • Suggestion made to other lists: https://github.com/sindresorhus/awesome/pull/1907#issuecomment-736186556

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

Requirements for your pull request

  • Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
  • You have to review at least 2 other open pull requests. Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions.
  • You have read and understood the instructions for creating a list.
  • This pull request has a title in the format Add Name of List.
    • Add Swift
    • Add Software Architecture
    • Update readme.md
    • Add Awesome Swift
    • Add swift
    • add Swift
    • Adding Swift
    • Added Swift
  • Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.
    • - [iOS](…) - Mobile operating system for Apple phones and tablets.
    • - [Framer](…) - Prototyping interactive UI designs.
    • - [iOS](…) - Resources and tools for iOS development.
    • - [Framer](…)
    • - [Framer](…) - prototyping interactive UI designs
  • Your entry should be added at the bottom of the appropriate category.
  • The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

  • Has been around for at least 30 days.<br>That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
  • Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
  • Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
  • The default branch should be named main, not master.
  • Includes a succinct description of the project/theme at the top of the readme. (Example)
    • Mobile operating system for Apple phones and tablets.
    • Prototyping interactive UI designs.
    • Resources and tools for iOS development.
    • Awesome Framer packages and tools.
  • It's the result of hard work and the best I could possibly produce. If you have not put in considerable effort into your list, your pull request will be immediately closed.
  • The repo name of your list should be in lowercase slug format: awesome-name-of-list.
    • awesome-swift
    • awesome-web-typography
    • awesome-Swift
    • AwesomeWebTypography
  • The heading title of your list should be in title case format: # Awesome Name of List.
    • # Awesome Swift
    • # Awesome Web Typography
    • # awesome-swift
    • # AwesomeSwift
  • Non-generated Markdown file in a GitHub repo.
  • The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
  • Not a duplicate. Please search for existing submissions.
  • Only has awesome items. Awesome lists are curations of the best, not everything.
  • Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
  • Includes a project logo/illustration whenever possible.
    • Either centered, fullwidth, or placed at the top-right of the readme. (Example)
    • The image should link to the project website or any relevant website.
    • The image should be high-DPI. Set it to maximum half the width of the original image.
  • Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
  • Includes the Awesome badge.
    • Should be placed on the right side of the readme heading.
      • Can be placed centered if the list has a centered graphics header.
    • Should link back to this list.
  • Has a Table of Contents section.
    • Should be named Contents, not Table of Contents.
    • Should be the first section in the list.
    • Should only have one level of nested lists, preferably none.
    • Must not feature Contributing or Footnotes sections.
  • Has an appropriate license.
    • We strongly recommend the CC0 license, but any Creative Commons license will work.
      • Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).
    • A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
    • Place a file named license or LICENSE in the repo root with the license text.
    • Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
    • To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.
  • Has contribution guidelines.
    • The file should be named contributing.md. Casing is up to you.
    • It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
    • The section should not appear in the Table of Contents.
  • All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
  • Has consistent formatting and proper spelling/grammar.
    • The link and description are separated by a dash. <br>Example: - [AVA](…) - JavaScript test runner.
    • The description starts with an uppercase character and ends with a period.
    • Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
  • Doesn't use hard-wrapping.
  • Doesn't include a Travis badge.<br>You can still use Travis for list linting, but the badge has no value in the readme.
  • Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

+1 -0

0 comment

1 changed file

pr created time in a day

pull request commentsindresorhus/awesome

Add Translations

Added a PR to add: Python i18n package https://github.com/mbiesiad/awesome-translations/pull/11

niedev

comment created time in a day

pull request commentsindresorhus/awesome

Add Awesome-autism

Hello, there. I had a look at your list and I'm not seeing something that I can't have Googling it.

One thing that got my attention was the Shoes listing, and the Brands does not look awesome. I can search that easily. The purpose of an awesome list is to have something that no one noticed or are different from the common point of view.

aspergirl-git

comment created time in a day

push eventline/armeria

Trustin Lee

commit sha 65a63e9885ca3e73f50b144eafce1bd9b8cffcba

Deploy the web site

view details

push time in a day

created tagline/armeria

tagarmeria-1.3.0

Your go-to microservice framework for any situation, from the creator of Netty et al. You can build any type of microservice leveraging your favorite technologies, including gRPC, Thrift, Kotlin, Retrofit, Reactive Streams, Spring Boot and Dropwizard.

created time in a day

push eventline/armeria

minwoox

commit sha 535873b866ef6b6849014841d12b813dff591666

Update the project version to 1.3.1-SNAPSHOT

view details

push time in a day

push eventline/armeria

minux

commit sha fad98ced8d32410f7800e5cff16d8a3007887c05

Add release note for 1.3.0 (#3207)

view details

push time in a day

PR merged line/armeria

Add release note for 1.3.0 documentation
+301 -0

5 comments

1 changed file

minwoox

pr closed time in a day

issue closedline/armeria

Why armeria prefer @Nullable to Optional?

It's not an issue but a question, so feel free to close it if it not fit your issue policy :P.

  1. Armeria used Optional long long ago, and then change it to xxxOrNull style API. why you prefer this?
  2. There're many @nullable variant in different library, like jsr305, jetbrains-annotations, could you, skillful developers, share your practice which and why to use one rather than another?

Big thanks!

closed time in a day

alex-lx

pull request commentsindresorhus/awesome

Add Robotic Tooling

Thanks @agamm I solved all of that.

Ly0n

comment created time in 2 days

pull request commentsindresorhus/awesome

Add Developer-First Products List

Unicorn.

agamm

comment created time in 2 days

PR opened sindresorhus/awesome

Add Developer-First Products List

<!-- Congrats on creating an Awesome list! 🎉 -->

<!-- Please fill in the below placeholders -->

https://github.com/agamm/awesome-developer-first

There is a growing trend of developer-first products, products that target developers specifically. There is currently no place that aggregates all of them. This can help developers to find relevant products and tools. This is highly related to the trend of outsourcing tasks (JAMStack mantra) like auth0/firebase and more replace a lot of the work required for authentication which was coded again and again. Now there are more products in several areas that solve the same developer pain points. This is why I decided to help myself and others find these products.

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

Requirements for your pull request

  • Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.

Check

  • You have to review at least 2 other open pull requests. Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions.

Check https://github.com/sindresorhus/awesome/pull/1905 https://github.com/sindresorhus/awesome/pull/1912

Check

  • This pull request has a title in the format Add Name of List.
    • Add Swift
    • Add Software Architecture
    • Update readme.md
    • Add Awesome Swift
    • Add swift
    • add Swift
    • Adding Swift
    • Added Swift

Check

  • Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.
    • - [iOS](…) - Mobile operating system for Apple phones and tablets.
    • - [Framer](…) - Prototyping interactive UI designs.
    • - [iOS](…) - Resources and tools for iOS development.
    • - [Framer](…)
    • - [Framer](…) - prototyping interactive UI designs

Check

  • Your entry should be added at the bottom of the appropriate category.

Check

  • The suggested Awesome list complies with the below requirements.

Check

Requirements for your Awesome list

  • Has been around for at least 30 days.<br>That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.

Check

  • Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.

Check

  • Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.

Check

Check

  • Includes a succinct description of the project/theme at the top of the readme. (Example)
    • Mobile operating system for Apple phones and tablets.
    • Prototyping interactive UI designs.
    • Resources and tools for iOS development.
    • Awesome Framer packages and tools.

Check

  • It's the result of hard work and the best I could possibly produce. If you have not put in considerable effort into your list, your pull request will be immediately closed.

Check

  • The repo name of your list should be in lowercase slug format: awesome-name-of-list.
    • awesome-swift
    • awesome-web-typography
    • awesome-Swift
    • AwesomeWebTypography

Check

  • The heading title of your list should be in title case format: # Awesome Name of List.
    • # Awesome Swift
    • # Awesome Web Typography
    • # awesome-swift
    • # AwesomeSwift

Check

  • Non-generated Markdown file in a GitHub repo.

Check

  • The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.

Check

  • Not a duplicate. Please search for existing submissions.

Check

  • Only has awesome items. Awesome lists are curations of the best, not everything.

Check

  • Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.

Check

  • Includes a project logo/illustration whenever possible.
    • Either centered, fullwidth, or placed at the top-right of the readme. [(Example)] (https://github.com/sindresorhus/awesome-electron)
    • The image should link to the project website or any relevant website.
    • The image should be high-DPI. Set it to maximum half the width of the original image.

Not needed, but tried.

  • Entries have a description, unless the title is descriptive enough by itself. It rarely is though.

Check

  • Includes the Awesome badge.
    • Should be placed on the right side of the readme heading.
      • Can be placed centered if the list has a centered graphics header.
    • Should link back to this list.

Check

  • Has a Table of Contents section.
    • Should be named Contents, not Table of Contents.

Check - Should be the first section in the list. Check - Should only have one level of nested lists, preferably none. Check - Must not feature Contributing or Footnotes sections. Check

  • Has an appropriate license.

Check - We strongly recommend the CC0 license, but any Creative Commons license will work. - Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly). - A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense. Check - Place a file named license or LICENSE in the repo root with the license text. Check - Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo. Check - To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn. Check

Check - The file should be named contributing.md. Casing is up to you. Check - It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content. Check - The section should not appear in the Table of Contents. Check

  • All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.

Check

  • Has consistent formatting and proper spelling/grammar.

Check - The link and description are separated by a dash. <br>Example: - [AVA](…) - JavaScript test runner. Check - The description starts with an uppercase character and ends with a period. Check - Consistent and correct naming. For example, Node.js, not NodeJS or node.js. Check

Check

  • Doesn't include a Travis badge.<br>You can still use Travis for list linting, but the badge has no value in the readme.

Check

  • Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Check

Go to the top and read it again.

+1 -0

0 comment

1 changed file

pr created time in 2 days

pull request commentsindresorhus/awesome

Add Robotic Tooling

Your links here are not formatted:

[https://github.com/protontypes/awesome-robotic-tooling]

[Robotic resources and tools for professional development in C++ or Python with a touch of ROS, autonomous driving and aerospace. This list was created mainly at my work at the department of autonomous logistics at DHL. Our goal was to create a complete development environment for robotics based on open tooling. All the tools we used and other interesting resources we found are in this list. It is the largest list of free and open resources in robotics. Many members of the open-source robotic community participated on this list. As the field of robotics today also has a lot of overlaps with the automotive and aerospace sector, there are also many projects in this area. ]

should be:

[awesome-robotic-tooling](https://github.com/protontypes/awesome-robotic-tooling)

Robotic resources and tools for professional development in C++ or Python with a touch of ROS, autonomous driving and aerospace. This list was created mainly at my work at the department of autonomous logistics at DHL. Our goal was to create a complete development environment for robotics based on open tooling. All the tools we used and other interesting resources we found are in this list. It is the largest list of free and open resources in robotics. Many members of the open-source robotic community participated on this list. As the field of robotics today also has a lot of overlaps with the automotive and aerospace sector, there are also many projects in this area. 

You also have a duplicate link:

https://github.com/TUMFTM/global_racetrajectory_optimization  remark-lint:double-link
Ly0n

comment created time in 2 days

pull request commentsindresorhus/awesome

Add Awesome-autism

I see that you didn't repalce the placeholders, like:

[Insert URL to the list here]

[Explain what this list is about and why it should be included here]

@aspergirl-git So it is really hard to check if the list is valid or not, if not impossible :)

aspergirl-git

comment created time in 2 days

startedgithub/git-sizer

started time in 2 days

issue openedline/armeria

Consider `Http2Exception: Stream x does not exist` as a expected exception after GOAWAY is sent

When a server receives a stream after a GOAWAY frame is sent to a client, the server warns the received stream like the following:

2020-11-30 14:07:47.100|INFO|armeria-common-worker-epoll-7-5||||DefaultHttp2ConnectionDecoder.java:584|[id: 0x17425acd, L:/10.112.183.21:8080 - R:/10.113.105.95:60932] ignoring DATA frame for stream 49. Stream sent after GOAWAY sent
2020-11-30 14:07:47.100|WARN|armeria-common-worker-epoll-7-5||||AbstractHttp2ConnectionHandler.java:87|[id: 0x17425acd, L:/10.112.183.21:8080 - R:/10.113.105.95:60932] HTTP/2 connection error:
io.netty.handler.codec.http2.Http2Exception: Stream 49 does not exist
        at io.netty.handler.codec.http2.Http2Exception.connectionError(Http2Exception.java:103)
        at io.netty.handler.codec.http2.DefaultHttp2ConnectionDecoder$FrameReadListener.verifyStreamMayHaveExisted(DefaultHttp2ConnectionDecoder.java:636)
        at io.netty.handler.codec.http2.DefaultHttp2ConnectionDecoder$FrameReadListener.onDataRead(DefaultHttp2ConnectionDecoder.java:257)

I think it is worth to consider Stream x does not exist as an expected exception after a GOAWAY is sent.

created time in 2 days

more