web
Here are 10,797 public repositories matching this topic...
We should discuss how to best support a library author providing translations for their library.
Bug report
It's not clear from the website's documentation, or the --help output, how to do the following equivalent curl task:
Post a raw JSON query to ElasticSearch:
curl \
--header "Content-Type: application/json" \
--request POST \
--data '{ "_source": [ "restricted_countries.*" ], "query": { "match_all": {} }, "size": 1000 }' \
'http://localhost:9200/_search'
T
Previously when using material icons I used the <i> tag and I believe I recall that material.io suggested that tag as well. Having checked again today I'm now seeing material.io suggesting that a <span> tag be used (which according to a lot of highly debated stack overflow answers is the correct tag to use for icons).
The issue is that material.io and the github pages documentation are not
🐛 bug report
parcel watch doesn't appear to use the --cert or --key flags, though its help output states it supports them. I don't know that the --https flag is affecting anything either.
Not sure if this is related to the recent work done in #4417.
🤔 Expected Behavior
$ parcel serve --cert cert.pem --key key.pem index.html
$ parcel watch --cert cert.pem --keyThe double dollar assertion: https://github.com/GoogleChrome/lighthouse/blob/e87a8b76e66208be0266c6e3a3b648dbebe79521/lighthouse-core/scripts/i18n/collect-strings.js#L344
Is a bit aggressive, it should check for basic $$ but allow $ICU_0$$ICU_1$. This should be validated with regex like \$([^$]*?)\$ and asserting that each capture group isn't empty instead of a more basic \$\$.
followed the docs for has manyhttp://gorm.io/docs/has_many.html for sqlilite
package main
import (
"fmt"
"github.com/jinzhu/gorm"
_ "github.com/mattn/go-sqlite3"
)
type User struct {
Id string
Name string
CreditCards []CreditCard `gorm:"FOREIGNKEY:user_id;ASSOCIATION_FOREIGNKEY:id"`
}
type CreditCard struct {
Id int
Number string
UserID
Issue Description
If you attempt to use the Echo logger before the server is started no output is actually written
Checklist
- Dependencies installed
- No typos
- Searched existing issues and docs
Expected behaviour
Using e.Logger.Info() writes output to log outside a handler
Actual behaviour
Using e.Logger.Info() does not write output to log ou
Description
Bug: In the latest Mac OS versions, memory usage changed https://apple.stackexchange.com/a/190935/135247
Because of this, even when there are no memory issues, Glances is showing false alarms for memory usage.
<img width="1370" alt="Screen Shot 2020-01-29 at 10 24 33 AM" src="https://user-images.githubusercontent.com/4463796/73330328-7ee1ce80-4286-11ea-9809-b8ddb22c76eb.pn
Was somebody able to make this thing work with react and functional components? Would be great if somebody could share some ideas.
I was not able to open port, may be that's because of my ISP, I see on HelloZeroNet page that,
Your port xxxxx is closed, but your Tor gateway is running well.
I see the above message, so if I had a site on ZeroNet, am I considered as a seeder to my site, if I was the only seeder to my site, assuming it is a new site. is it enough that tor gateway is running but without open port ?
Feature Request
We've had several issues related to confusion around the Sass module system. We should improve our documentation per component that explains how to import mixins, customize variables, and apply core styles.
Proposed solution
For example, take button's [README](h
Thanks for publishing this! How about adding it to GitHub.com/topics/terminal-share alongside similar tools by adding that topic to this repo? Thank you :-)
I noticed an undocumented behavior with listeners, where some of them run in reverse order of registration
- What is the rationale for that?
- Can this be added to the docs?
Additional context
Relevant lines of code from https://github.com/huge-success/sanic/blob/master/sanic/app.py#L1356
# -------------------------------------------- #
# Register start/stop eIs your feature request related to a problem
Coming from this issue: tiangolo/fastapi#817
The docs have some sections with functions using *, in the parameters.
It is explained here: https://fastapi.tiangolo.com/tutorial/path-params-numeric-validations/#order-the-parameters-as-you-need-tricks
But in other sections like: https://fastapi.tiangolo.com/tutor
Add examples.
Index:
formatXMLElementFn-- a function handling rich text formatting, passed tovalues. Name is used as referred in source code,
The problem
While using RichText, formatXMLElementFn are called with possible many arguments (chunks) which could be collected with rest operator and passed to component.
Example
<FormatMessage
defaultMessage="This is <i>exampleDescription
yew and yew-stdweb generate the same docs.rs documentation because yew-stdweb is an alias of yew (wi
better error logging
I'm submitting a feature request
- Library Version:
aurelia-script 1.3.1
Current behavior:
If you make a typo, or on this case I forgot to add async to a function, you get a long but useless stacktrace pointing to inside of aurelia but nowhere in the stack trace does it give me any clue of what view, class, file is at fault. I've had this issue for years, ever since Aurelia w
Page Affected: https://developers.google.com/web/android/trusted-web-activity/integration-guide#add-splash-markup
What needs to be done?
The meta-data for Android Manifest should include the recently added Dark Theme tags for the status and nav bar:
<meta-data
android:name="android.support.customtabs.trusted.STATUS_BAR_COLOR"
android:res
-
Updated
Apr 27, 2020 - JavaScript
What is wrong?
On Windows, brain.js installs correctly and runs correctly only if the version of Node.Js is greater than 13.0. This is in no way mentioned in the README.md.
Where does it happen?
In the installation
How do we replicate the issue?
In a Windows machine with the LTS version of Node.Js installed try to install brain.Js with the command npm install brain.js
I think it's unexpected. I have to use Detector.canCollide on my own when I want to use Query.collides. I think it should be changed or at least mention in documentation.
Improve this page
Add a description, image, and links to the web topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the web topic, visit your repo's landing page and select "manage topics."
A description is incomplete. It should mention:
These patterns are not competing, but complementing each other. To achieve availability, one needs both fail-over and replication.
right after
"There are two main patterns to support high availability: fail-over and replication. "