ik ver 6.4.2
analyze :
_analyze?pretty" -d '{"tokenizer":"ik_max_word", "text":"[email protected]"}'
we got
`{
"tokens" : [
{
"token" : "[email protected]",
"start_offset" : 0,
"end_offset" : 15,
"type" : "LETTER",
"position" : 0
},
{
"token" : "aa",
"start_offset" : 0,
"end_offset" : 2,
"type" : "ENGLISH",

https://www.php.net/uopz_delete is incorrect (one required param, not two). It was also removed in uopz 5.0

internal/reflection_completeness_check.php will help if uopz is installed.

We need to test config file against errors

• Someone can try to use "yes" to turn on a boolean parameter which needs "on"
• Someone can wrong type a parameter
• Someone can write an invalid parameter
• Someone can write an invalid IP address / CIDR

It would be nice to quickly switch builds with arrow keys or a similarly simple shortcut key. Maybe A/D (of WASD) instead or in addition?

测试分词结果
http://192.168.36.140:9200/1/_analyze?text=周大福&analyzer=pinyin_analyzer

tokens
0
token "zhou"
start_offset 0
end_offset 1
type "word"
position 0
1
token "zdf"
start_offset 0
end_offset 3
type "word"
position 0
2
token "da"
start_offset 1
end_offset 2
type "word"
position 1
3
token "fu"
start_offset 2
end_offset 3
type "word"
position 2

查询方式：
curl -XGE

Bug / Feature Request

Work Environment

Problem Description

There are no longer any default dashboards

Possible Solutions

Add the default da

Scanning my current branch of Alamofire, Sitrep gives these LOC results:

Sizes
   Total lines of code: 11102
   Source lines of code: 9481

However, cloc gives these results:

Language                     files          blank        comment           code
-------------------------------------------------------------------------------
Swift                           32          

It will be good to analyze var_dump leftovers in project, and to add support for other functions that cause same behavior.

Include Dockerfile in root of project

Request Type

Feature Request

Description

As part of the development and release cycle, please include the Dockerfile generated by docker.sbt in the root of the project so that the container can be built directly from the repo itself.

As per the respective RFCs, IGMP uses MRD in units of 1/10s while MLD uses units of ms.

Currently the Ostinato GUI shows units as 1/10s for both IGMP and MLD.

We should move our cookbook_vs.md to relevant topic(s) on docs.microsoft.com.

As part of the migration at least this page on docs.microsoft.com should be updated.

The analyzer warns correctly, but the documentation for SCS0007 only has guidance for XmlReader and XmlDocument. The warning also appears for XmlPathDocument/XPathNavigator, which is also insecure by default on .NET version prior to 4.5.2. https://github.com/OWASP/CheatSheetSeries/blob/master/cheatsheets/XML_External_Entity_Prevention_Cheat_Sheet.md#xpathnavigator has guidance on an example fix

Seems that InnoSetup is included by default in AppVeyor to create the Windows installer. We should use it and automatically add it to our release. Some links:

• https://www.appveyor.com/docs/build-environment/
• http://help.appveyor.com/discussions/problems/4482-chocolatey-package-install-failure

There are still some WMS servers, that accept only requests having upper case url parameters.
For more details, see Leaflet/Leaflet#1751.
One more example:
`https://wms.kartes.lv/BM45/lks/15/?BBOX=492853.9711849016,287182.4383909153,516883.9093781112,311212.37658412475&WIDTH=256&HEIGHT=256&KIJS=BM45&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&EXCEPTIONS=application%2Fvnd.ogc.se_inimage&LAYERS=0&SR

https://www.wowhead.com/spell=285652/insatiable-torment

Can't heal yourself with this debuff, someone suggested death recap might be updated to indicate this (healthstones/pots shouldnt appear, etc)

The Table of Contents does not show all the sections in the Install Guide, and the First Start section needs to be updated starting with the title and correcting other verbiage issues within the section text.