text:
Updates The Azure Queue Storage Payload

When the following example payload is passed into the Queue:
{
  "id": "/subscriptions/97e01fd4-3326-41f4-b9e3-3cfd6809e10f/resourceGroups/Sample-RG/providers/Microsoft.Security/locations/centralus/alerts/2517538088722812591_ee939333-c75e-461d-83c2-712ba9abfadb",
  "name": "2517538088722812591_ee939333-c75e-461d-83c2-712ba9abfadb",
  "type": "Microsoft.Security/Locations/alerts",
  "properties": {
    "vendorName": "Microsoft",
    "alertDisplayName": "[SAMPLE ALERT] Suspected successful brute force attack",
    "alertName": "SIMULATED_SQL.VM_BruteForce",
    "detectedTimeUtc": "2022-03-28T18:25:27.7187408Z",
    "description": "THIS IS A SAMPLE ALERT: A successful login occurred after an apparent brute force attack on your resource",
    "remediationSteps": "Go to the firewall settings in order to lock down the firewall as tightly as possible.",
    "actionTaken": "Undefined",
    "reportedSeverity": "High",
    "compromisedEntity": "Sample-VM",
    "associatedResource": "/SUBSCRIPTIONS/97e01fd4-3326-41f4-b9e3-3cfd6809e10f/RESOURCEGROUPS/Sample-RG/providers/Microsoft.Compute/virtualMachines/Sample-VM",
    "subscriptionId": "97e01fd4-3326-41f4-b9e3-3cfd6809e10f",
    "instanceId": "ee939333-c75e-461d-83c2-712ba9abfadb",
    "extendedProperties": {
      "resourceType": "SQL Server 2019",
      "potential causes": "Brute force attack; penetration testing.",
      "client principal name": "Sample-account",
      "alert Id": "00000000-0000-0000-0000-000000000000",
      "client IP address": "00.00.00.00",
      "client IP location": "san antonio, united states",
      "client application": "Sample-app",
      "successful logins": "1",
      "oms workspace ID": "00000000-0000-0000-0000-000000000000",
      "failed logins": "0",
      "oms agent ID": "00000000-0000-0000-0000-000000000000",
      "enrichment_tas_threat__reports": "{\"Kind\":\"MultiLink\",\"DisplayValueToUrlDictionary\":{\"Report: Brute Force\":\"https://interflowwebportalext.trafficmanager.net/reports/DisplayReport?callerIdentity=ddd5443d-e6f4-441c-b52b-5278d2f21dfa&reportCreateDateTime=2022-03-28T17%3a59%3a38&reportName=MSTI-TS-Brute-Force.pdf&tenantId=52aab34c-2534-4485-bf2f-b4e7e5c42e44&urlCreateDateTime=2022-03-28T17%3a59%3a38&token=ubgWSjyr0wFBBiPZyz2jJ5lmrPmwXy2jLxDNy7RVz7k=\"}}",
      "killChainIntent": "PreAttack"
    },
    "state": "Active",
    "reportedTimeUtc": "2022-03-28T18:26:47.490371Z",
    "confidenceReasons": [],
    "canBeInvestigated": true,
    "isIncident": false,
    "entities": [
      {
        "$id": "centralus_1",
        "hostName": "Sample-VM",
        "azureID": "/SUBSCRIPTIONS/97e01fd4-3326-41f4-b9e3-3cfd6809e10f/RESOURCEGROUPS/Sample-RG/providers/Microsoft.Compute/virtualMachines/Sample-VM",
        "omsAgentID": "00000000-0000-0000-0000-000000000000",
        "type": "host"
      },
      {
        "$id": "centralus_2",
        "address": "00.00.00.00",
        "location": {
          "countryCode": "sample",
          "countryName": "united states",
          "state": "texas",
          "city": "san antonio",
          "longitude": 0,
          "latitude": 0,
          "asn": 0,
          "carrier": "sample",
          "organization": "sample-organization",
          "organizationType": "sample-organization",
          "cloudProvider": "Azure",
          "systemService": "sample"
        },
        "type": "ip"
      },
      {
        "$id": "centralus_3",
        "sourceAddress": {
          "$ref": "centralus_2"
        },
        "protocol": "Tcp",
        "type": "network-connection"
      },
      {
        "$id": "centralus_4",
        "name": "Sample-SA",
        "host": {
          "$ref": "centralus_1"
        },
        "type": "account"
      }
    ]
  }
}

This PR proposes the payload of the event be changed from:
'{
  "ID": "9dd43d62-ec1e-4369-b337-4229d52a513c",
  "InsertionTime": "2022-06-15T20:04:59Z",
  "ExpirationTime": "2022-06-22T20:04:59Z",
  "PopReceipt": "AgAAAAMAAAAAAAAALn6FW7yB2AE=",
  "NextVisibleTime": "2022-06-16T20:04:59Z",
  "DequeueCount": 1,
  "Text": "{\n \"id\": \"/subscriptions/97e01fd4-3326-41f4-b9e3-3cfd6809e10f/resourceGroups/Sample-RG/providers/Microsoft.Security/locations/centralus/alerts/2517538088322968242_7951468c-3909-4b52-a442-c1f4b92d5162\",\n \"name\": \"2517538088322968242_7951468c-3909-4b52-a442-c1f4b92d5162\",\n \"type\": \"Microsoft.Security/Locations/alerts\",\n \"properties\": {\n \"vendorName\": \"Microsoft\",\n \"alertDisplayName\": \"[SAMPLE ALERT] Unusual amount of data extracted from a storage account\",\n \"alertName\": \"SIMULATED_Storage.Blob_DataExfiltration.AmountOfDataAnomaly\",\n \"detectedTimeUtc\": \"2022-03-28T18:26:07.7031757Z\",\n \"description\": \"THIS IS A SAMPLE ALERT: Someone has extracted an unusual amount of data from your Azure Storage account 'Sample-Storage'.\",\n \"remediationSteps\": \"• Limit access to your storage account, following the 'least privilege' principle: https://go.microsoft.com/fwlink/?linkid=2075737.\\r\\n• Revoke all storage access tokens that may be compromised and ensure that your access tokens are only shared with authorized users.\\r\\n• Ensure that storage access tokens are stored in a secured location such as Azure Key Vault. Avoid storing or sharing storage access tokens in source code, documentation, and email.\",\n \"actionTaken\": \"Undefined\",\n \"reportedSeverity\": \"High\",\n \"compromisedEntity\": \"Sample-Storage\",\n \"associatedResource\": \"/SUBSCRIPTIONS/97e01fd4-3326-41f4-b9e3-3cfd6809e10f/RESOURCEGROUPS/Sample-RG/providers/Microsoft.Storage/storageAccounts/Sample-Storage\",\n \"subscriptionId\": \"97e01fd4-3326-41f4-b9e3-3cfd6809e10f\",\n \"instanceId\": \"7951468c-3909-4b52-a442-c1f4b92d5162\",\n \"extendedProperties\": {\n \"resourceType\": \"Storage\",\n \"investigation steps\": \"{\\\"displayValue\\\":\\\"View related storage activity using Storage Analytics Logging. See how to configure Storage Analytics logging and more information.\\\",\\\"kind\\\":\\\"Link\\\",\\\"value\\\":\\\"https:\\\\/\\\\/go.microsoft.com\\\\/fwlink\\\\/?linkid=2075734\\\"}\",\n \"potential causes\": \"This alert indicates that an unusually large amount of data has been extracted compared to recent activity on this Storage container.\\r\\nPotential causes:\\r\\n• An attacker has extracted a large amount of data from a Storage container (for example: data exfiltration/breach, unauthorized transfer of data).\\r\\n• A legitimate user or application has extracted an unusual amount of data from a Storage container (for example: maintenance activity).\",\n \"client IP address\": \"00.00.00.00\",\n \"client location\": \"Azure Data Center: East Us\",\n \"authentication type\": \"Anonymous\",\n \"operations types\": \"GetBlob\",\n \"service type\": \"Azure Blobs\",\n \"user agent\": \"dummyAgent\",\n \"container\": \"eicarTestStorageContainer\",\n \"extracted data\": \"140 MB\",\n \"test: Slice start time\": \"03/28/2022 18:26:07\",\n \"test: Pipeline name\": \"1.0.4656.1_storagetd-brs-a3\",\n \"extracted blobs\": \"500\",\n \"killChainIntent\": \"Exfiltration\"\n },\n \"state\": \"Active\",\n \"reportedTimeUtc\": \"2022-03-28T18:26:47.1036441Z\",\n \"workspaceArmId\": \"/subscriptions/97e01fd4-3326-41f4-b9e3-3cfd6809e10f/resourcegroups/csnf/providers/microsoft.operationalinsights/workspaces/csnfsentinel\",\n \"confidenceReasons\": [],\n \"canBeInvestigated\": true,\n \"isIncident\": false,\n \"entities\": [\n {\n \"$id\": \"centralus_1\",\n \"address\": \"00.00.00.00\",\n \"location\": {\n \"countryName\": \"United States\",\n \"city\": \"Washington\"\n },\n \"type\": \"ip\"\n }\n ]\n }\n}"
}'

in favour of :
{
                                "id": "/subscriptions/97e01fd4-3326-41f4-b9e3-3cfd6809e10f/resourceGroups/Sample-RG/providers/Microsoft.Security/locations/centralus/alerts/2517538088322968242_7951468c-3909-4b52-a442-c1f4b92d5162",
                                "name": "2517538088322968242_7951468c-3909-4b52-a442-c1f4b92d5162",
                                "type": "Microsoft.Security/Locations/alerts",
                                "properties": {
                                  "vendorName": "Microsoft",
                                  "alertDisplayName": "[SAMPLE ALERT] Unusual amount of data extracted from a storage account",
                                  "alertName": "SIMULATED_Storage.Blob_DataExfiltration.AmountOfDataAnomaly",
                                  "detectedTimeUtc": "2022-03-28T18:26:07.7031757Z",
                                  "description": "THIS IS A SAMPLE ALERT: Someone has extracted an unusual amount of data from your Azure Storage account 'Sample-Storage'.",
                                  "remediationSteps": "• Limit access to your storage account, following the 'least privilege' principle: https://go.microsoft.com/fwlink/?linkid=2075737.\r\n• Revoke all storage access tokens that may be compromised and ensure that your access tokens are only shared with authorized users.\r\n• Ensure that storage access tokens are stored in a secured location such as Azure Key Vault. Avoid storing or sharing storage access tokens in source code, documentation, and email.",
                                  "actionTaken": "Undefined",
                                  "reportedSeverity": "High",
                                  "compromisedEntity": "Sample-Storage",
                                  "associatedResource": "/SUBSCRIPTIONS/97e01fd4-3326-41f4-b9e3-3cfd6809e10f/RESOURCEGROUPS/Sample-RG/providers/Microsoft.Storage/storageAccounts/Sample-Storage",
                                  "subscriptionId": "97e01fd4-3326-41f4-b9e3-3cfd6809e10f",
                                  "instanceId": "7951468c-3909-4b52-a442-c1f4b92d5162",
                                  "extendedProperties": {
                                        "resourceType": "Storage",
                                        "investigation steps": "{\"displayValue\":\"View related storage activity using Storage Analytics Logging. See how to configure Storage Analytics logging and more information.\",\"kind\":\"Link\",\"value\":\"https:\\/\\/go.microsoft.com\\/fwlink\\/?linkid=2075734\"}",
                                        "potential causes": "This alert indicates that an unusually large amount of data has been extracted compared to recent activity on this Storage container.\r\nPotential causes:\r\n• An attacker has extracted a large amount of data from a Storage container (for example: data exfiltration/breach, unauthorized transfer of data).\r\n• A legitimate user or application has extracted an unusual amount of data from a Storage container (for example: maintenance activity).",
                                        "client IP address": "00.00.00.00",
                                        "client location": "Azure Data Center: East Us",
                                        "authentication type": "Anonymous",
                                        "operations types": "GetBlob",
                                        "service type": "Azure Blobs",
                                        "user agent": "dummyAgent",
                                        "container": "eicarTestStorageContainer",
                                        "extracted data": "140 MB",
                                        "test: Slice start time": "03/28/2022 18:26:07",
                                        "test: Pipeline name": "1.0.4656.1_storagetd-brs-a3",
                                        "extracted blobs": "500",
                                        "killChainIntent": "Exfiltration"
                                  },
                                  "state": "Active",
                                  "reportedTimeUtc": "2022-03-28T18:26:47.1036441Z",
                                  "workspaceArmId": "/subscriptions/97e01fd4-3326-41f4-b9e3-3cfd6809e10f/resourcegroups/csnf/providers/microsoft.operationalinsights/workspaces/csnfsentinel",
                                  "confidenceReasons": [],
                                  "canBeInvestigated": true,
                                  "isIncident": false,
                                  "entities": [
                                        {
                                          "$id": "centralus_1",
                                          "address": "00.00.00.00",
                                          "location": {
                                                "countryName": "United States",
                                                "city": "Washington"
                                          },
                                          "type": "ip"
                                        }
                                  ]
                                }
                          }

The current way we nest the message makes it hard to use/parse.

after farther thought.. I think this is wrong.. we are expecting always JSON. this is obviously not right.

repo: triggermesh/triggermesh


text:
Add HWM settings in Ledger

[x] Add HWM to N_data persistent storage
[x] Add HWM to settings in nano home layout
[x] Add HWM switch to stax settings page
[ ] Change behavior of HWM tracking in ledger based on HWM setting.
[ ] Do not display HWM when HWM setting is turned off.

The hwm settings does not have any impact on the app, is that on purpose?

The app behaviour changes are in progress. I just got the display and button changes done.

source: gharchive/pull-request

repo: trilitech/ledger-app-tezos-baking

license_type: permissive

license_source: github-api


text:
Tab Broken Down into smaller Elements

Enable the designer to decide about the amount of tabs and allow text style definition, e.g. all caps. Compare to XD too. See survey results https://docs.google.com/presentation/d/1ekou3J2SY6XXj1asQVgnNJT4UXDhz6hAR_bmSnPmEbc/edit#slide=id.g18d0eacc774_0_60

Related to https://github.com/trimble-oss/modus/issues/480

source: gharchive/issue

repo: trimble-oss/modus

license: MIT


text:
Add count-based stabilization

The count based algorithm can be enabled by using the --window-size flag. I didn't reuse the -p flag because it still would require another flag to interpret the meaning of -p flag.

This is still not fixed.. We must keep #include "inference_profiler.h" as the first include.
I think you commented on the previous commit. It is fixed in the latest commit.

Can you fix the message in inference_profiler.cc L735-L736 so that it can read correct for count_windows mode? Otherwise the change looks good to me.

@tanmayv25 The latency size can never be zero for the other mode because we won't exit the while loop until enough requests are captured. I have a check when parsing the CLIs which ensures that --measurement-request-count is greater than zero.

repo: triton-inference-server/client

license_source: bigquery


text:
fix: Fix typo with 'false' and pre-commit failures

Fixes this obscure error when running the python backend implementation of the tensorrt_llm model:
tritonclient.utils.InferenceServerException: Traceback (most recent call last):
  File "/mnt/triton/hackathon/trtllm/tensorrtllm_backend/all_models/inflight_batcher_llm/tensorrt_llm_bls/1/model.py", line 108, in execute
    for res in res_gen:
  File "/mnt/triton/hackathon/trtllm/tensorrtllm_backend/all_models/inflight_batcher_llm/tensorrt_llm_bls/1/lib/decode.py", line 230, in decode
    for gen_response in self._generate(
  File "/mnt/triton/hackathon/trtllm/tensorrtllm_backend/all_models/inflight_batcher_llm/tensorrt_llm_bls/1/lib/triton_decoder.py", line 295, in _generate
    for r in self._exec_triton_request(triton_req):
  File "/mnt/triton/hackathon/trtllm/tensorrtllm_backend/all_models/inflight_batcher_llm/tensorrt_llm_bls/1/lib/triton_decoder.py", line 109, in _exec_triton_request
    raise pb_utils.TritonModelException(r.error().message())
c_python_backend_utils.TritonModelException: An error occurred when processing the input values for request id , the error was 'name 'false' is not defined'

Closing in favor of gitlab.


text:
Improves building by clearing out some directories

This fix removes the dist and tmp folder before building to prevent issues when creating these directories. This could also have been fixed by mkdir -p but it's better practice to clear out the directories to really insure a fresh build.

Oh, I forgot to add that the change from #!/bin/bashto #!/usr/bin/env bash changes how bash is found since some systems have bash in other directories. This makes it a bit more portable. On my OS it is located in /nix/store/a9iznl51izkxbh5qz47bs1a4x1fq4md9-system-path/bin/bashsince I use NixOS.
References regarding this:
https://unix.stackexchange.com/q/29608
https://stackoverflow.com/a/16365367/1294363

Thanks for the enhancement. I fixed a spelling type-o then merged.

authors: emilhem trodi

license: mit


text:
🛑 Sonarr Anime is down

In b59fcdb, Sonarr Anime (https://tronflix.app/sonarr-anime/login) was down:

HTTP code: 520
Response time: 110 ms

Resolved: Sonarr Anime is back up in b7e5b11.

repo: tronyx/upptime


text:
🛑 Nagios is down

In df7ec1e, Nagios (https://nagios.tronflix.app) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nagios is back up in 8038643.


text:
🛑 Bitwarden is down

In 2940002, Bitwarden (https://bitwarden.tronflix.app) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Bitwarden is back up in 9bab31b after 7 minutes.


text:
🛑 Plex is down

In 99de74c, Plex (https://tronflix.app/plex/web/index.html) was down:

HTTP code: 520
Response time: 45 ms

Resolved: Plex is back up in 7202749 after 8 minutes.


text:
can you split sub module “beanSearcher-annotation” ?

能否拆一个 annotation 的工程出来？
因为 beansearcher 一些查询的 view 对象，是放在 api 里面作为定义pojo 包里的，不希望再 api 里依赖 beanSearcher 的所有包

Bean Searcher 一共两个包：

cn.zhxu:bean-searcher
cn.zhxu:bean-searcher-boot-starter
cn.zhxu:bean-searcher-solon-plugin

在你的 api 模块里，这样即可：
compileOnly 'cn.zhxu:bean-searcher'

repo: troyzhxu/bean-searcher


text:
diazoalkane, addeem

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,d]

/trunk merge

repo: trunk-io/mergequeue-staging


text:
emyd, bearm

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b,e]

/trunk merge


text:
frontispieced

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[f]

/trunk merge


text:
blackguard, gasometrical

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b,g]

/trunk merge


text:
admiration, dispelling

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,d]

/trunk merge


text:
bloodlines, enchiridion

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b,e]

/trunk merge


text:
grimed, akawai

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 5
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[a,g]

/trunk merge


text:
devoutlessly, evanescently

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[d,e]

/trunk merge


text:
fl, bairnteam

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b,f]

/trunk merge


text:
boatwoman, agisted

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,b]

/trunk merge


text:
clock, enchains

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[c,e]

/trunk merge


text:
function

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[f]

/trunk merge


text:
amovable, demonetizes

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,d]

/trunk merge


text:
alveololingual, gesticulation

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,g]

/trunk merge


text:
gumminess, bronzesmith

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b,g]

/trunk merge


text:
flintlock, aged

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,f]

/trunk merge


text:
farmout, doggone

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[d,f]

/trunk merge


text:
gamphrel, clamminess

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[c,g]

/trunk merge


text:
extractor, distyle

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[d,e]

/trunk merge


text:
announces, cardinalic

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,c]

/trunk merge

repo: trunk-io/mergequeue


text:
epithecal, canzon

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[c,e]

/trunk merge


text:
glamourous, bombycids

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b,g]

/trunk merge


text:
enticements, devitalised

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[d,e]

/trunk merge


text:
birdcatching, dextropedal

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b,d]

/trunk merge


text:
ascidia, chibouk

This pull request was generated by the 'mq' tool

/trunk merge


text:
footstall

This pull request was generated by the 'mq' tool

/trunk merge


text:
cyclanthaceae, guzzlers

This pull request was generated by the 'mq' tool

/trunk merge


text:
antihectic, demoniast

This pull request was generated by the 'mq' tool

/trunk merge


text:
epaxially, greeve

This pull request was generated by the 'mq' tool

/trunk merge


text:
balding, foetuses

This pull request was generated by the 'mq' tool

/trunk merge


text:
basimesostasis, eomecon

This pull request was generated by the 'mq' tool

/trunk merge


text:
figurational, degasses

This pull request was generated by the 'mq' tool

/trunk merge


text:
ashkoko, febrifacient

This pull request was generated by the 'mq' tool

/trunk merge


text:
fempty, growing

This pull request was generated by the 'mq' tool

/trunk merge


text:
forestian, deterrers

This pull request was generated by the 'mq' tool

/trunk merge


text:
aeroscopic, fluoridizing

This pull request was generated by the 'mq' tool

/trunk merge


text:
dubiocrystalline, bismuthic

This pull request was generated by the 'mq' tool

/trunk merge


text:
flairs, disjects

This pull request was generated by the 'mq' tool

/trunk merge


text:
dainful, grungier

This pull request was generated by the 'mq' tool

/trunk merge


text:
divelling, acridest

This pull request was generated by the 'mq' tool

/trunk merge


text:
censuses, globigerina

This pull request was generated by the 'mq' tool

/trunk merge


text:
frustration, breastwise

This pull request was generated by the 'mq' tool

/trunk merge


text:
exhibitor, alveolodental

This pull request was generated by the 'mq' tool

/trunk merge


text:
equivocally, ciborium

This pull request was generated by the 'mq' tool

/trunk merge


text:
beefish, glucolipide

This pull request was generated by the 'mq' tool

/trunk merge


text:
compactification, disbudding

This pull request was generated by the 'mq' tool

/trunk merge


text:
episcopizing, freudism

This pull request was generated by the 'mq' tool

/trunk merge


text:
brichette, formaldehyde

This pull request was generated by the 'mq' tool

/trunk merge


text:
daybreaks, ferrums

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[d,f]

/trunk merge


text:
euthytropic

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[e]

/trunk merge


text:
fleabiting, alantol

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[a,f]

/trunk merge


text:
epidendron, amphibolic

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[a,e]

/trunk merge


text:
eoan, angiospastic

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[a,e]

/trunk merge


text:
attracted, gwen

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[a,g]

/trunk merge


text:
entozoan, coryphaena

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[c,e]

/trunk merge


text:
fashionize, edificant

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[e,f]

/trunk merge


text:
bandeng, enterosyphilis

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b,e]

/trunk merge


text:
engastrimyth, cuminyl

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[c,e]

/trunk merge


text:
entwist, blackprint

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b,e]

/trunk merge


text:
flattered, aphyllous

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,f]

/trunk merge


text:
bricked, churchmanly

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b,c]

/trunk merge


text:
fyce, commiserated

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[c,f]

/trunk merge


text:
afterrider, backhouse

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,b]

/trunk merge


text:
breathily, donning

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b,d]

/trunk merge


text:
Check possible bug in processing TrustlineUpdate

Check if setting the m_time in update_trustline is the right thing to do, or a bug (https://github.com/trustlines-protocol/relay/blob/master/relay/network_graph/graph.py#L531). In a comment further down it says is represents the last modification time of the balance (https://github.com/trustlines-protocol/relay/blob/master/relay/network_graph/graph.py#L544).

If you change the interest rates, you need to calculate the accrued interests and apply them, so you need to update the m_time.
More code-wise:
This is called when receiving a TrustlinesUpdate event: https://github.com/trustlines-protocol/relay/blob/master/relay/relay.py#L717
This event is emitted here: https://github.com/trustlines-protocol/contracts/blob/master/contracts/CurrencyNetwork.sol#L1148
As you can see, a few line above we have _applyInterests(_trustline) which will update the m_time.

Yes, but I would argue like this:
if you change the interest rate, you need to calculate the accrued interests and apply them, so the balance will change. This should fire a BalanceUpdate event, and in reaction to that event the m_time needs to change.
So there is no need to update m_time on TrustlineUpdate directly.

Yes, we should probably remove the edge if we close the trustline.

We currently do not emit a BalanceUpdate event on changing credit limits even though the balance may be updated as far as I can tell.
We could change this in the contracts and then stop updating the m_time on the relay on TrustlinesUpdate. But I am not sure it makes it better, since every trustlines update on a trustlines with interest will then fire a BalanceUpdate.

I would suggest we change the TrustlinesUpdate event to add the balance to it so that the user is aware of the new balance with the interest.
We handle this on the relay server by calling the update_balance() function if the balance changed.
There is no way for the relay to make the difference between a closed trustlines and a trustlines with 0 credit limits and balances, so I would just remove the edge from the graph when any of these cases occur within update_trustline().

(I just noticed your other issue, this works too, then we can remove the update of m_time on update_trustline() in the relay server, even though it does not really matter)

I would rather fix it by firing a BalanceUpdate, as for me that the Balance changes is just a side effect of the weird way that we handle the interests, so for my having a balance in TrustlineUpdate is really weird.

Created task: https://github.com/trustlines-protocol/relay/issues/295
I cannot see how to know that a trustlines has been closed from the events though. When someone calls closeTrustlineByTriangularTransfer, we will receive a TrustlineUpdate event with (0,0,0,0). However, we do not know if the balance is 0 and if the edge in the graph must be removed unless we already processed the corresponding BalanceUpdate event. Same goes for the BalanceUpdate events.
If we do not handle events concurrently, we can try to remove the edge of the graph on both event, otherwise we might introduce a bug.

can you not trigger a check for all values to be zero at both events as last step?
So do all things, and if now all values are zero, remove the edge.

Ah I should finish reading you message first. We are using gevent, so we use some threading, but what you want to do should be fine. We can have a short chat about it.

Tasks have been created, i believe this can be closed.

authors: berndbohmeier cducrest

repo: trustlines-protocol/relay


text:
Updating Articles Database

Please do all work in a branch called 'issue-017.'
Feedback provided by the users should probably be stored in a database. We can just continue using MongoDB here since it's already baked in with Meteor. Please discuss the attributes you think would be relevant to keep with each feedback object.

Probably unintentional, but this work has largely been done in the branch 'issue-016.' Refer to the getEmbeddings function in chat-controller. Basically called an update method on the collection each time a source is used.


text:
InternalServerException

I keep getting InternalServerException with one of my accounts but not the other. It happens less than 5 requests in to my session.
Anyone else had this issue that was able to resolve it?
EDIT: It happens on a SearchAsync()

I figured it out. Didn't play enough on the secondary account to access the transfer market.

What was the problem?
I get the same Error on SearchAsyn().

repo: trydis/FIFA-Ultimate-Team-Toolkit


text:
test

test

repo: trypear/pear-landing-page


text:
🛑 Fintin.pl is down

In 47ee88a, Fintin.pl (https://fintin.pl/pl/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Fintin.pl is back up in 2df59e3 after 6 minutes.


text:
描述 | Description
可以自動刪除舊的apk版本，避免資源浪費。
僅保存最多 5 個最近的 apk 版本，並刪除超過 30 天的 apk。

关联 ＃376

节后考虑加一个这样最多保留数的功能

authors: icyleaf maichanchinh

repo: tryzealot/zealot


text:
fix: return errors from fastify route handlers

requestValidationErrorHandler currently only handles RequestValidationError while silently consuming all other errors. This means that if there is any unhandled error in a route handler, the request never completes.
I added a test case for demonstration, and fixed the issue by re-throwing errors other than RequestValidationError.

Can you add a changeset bump to the fastify package @suphon-t?

authors: michaelangelo-io suphon-t

repo: ts-rest/ts-rest


text:
tsstuff over estimating input bit rate and overstuffing file

I'm trying to stuff a transport stream that has 100 programs in it and i'm trying to stuff it to about 42Mb/s. output from
tsbitrate -a originalFile.ts is
TS bitrate: 33,156,038 b/s (188-byte), 35,977,828 b/s (204-byte)
using tsstuff tsstuff -b 42283562 o [originalFile.zip](https://github.com/tsduck/tsduck/files/2319910/originalFile.zip) riginalFile.ts > stuffed.ts
gives the error tsstuff: input bitrate higher than target bitrate, cannot stuff
and over stuffs the stream to
tsbitrate stuffed.ts
TS bitrate: 55,091,052 b/s (188-byte), 59,779,652 b/s (204-byte)

Hi @marti566
Your stream is a bit weird. Its average bitrate is 33 Mb/s but it is extremely erratic, much more than a standard variable bitrate stream.
I have enhanced the tsstuff command to display more accurate messages:
using PID 101 (0x0065) as reference
tsstuff: input bitrate locally higher (86,134,080 b/s) than target bitrate, cannot stuff
tsstuff: input bitrate locally higher (206,153,280 b/s) than target bitrate, cannot stuff
tsstuff: input bitrate locally higher (99,264,000 b/s) than target bitrate, cannot stuff
tsstuff: input bitrate locally higher (86,134,080 b/s) than target bitrate, cannot stuff
tsstuff: input bitrate locally higher (203,446,080 b/s) than target bitrate, cannot stuff
...

These messages are the same as the ones you mention, except that the local bitrate (between two PCR's) is displayed, explaining why stuffing is not locally possible.
The way tsstuff works is the following:

Find a reference PID with PCR (system clock).
Work on segments which are defined by two successive PCR timestamps.
Consider all segments in the file, one by one.
Evaluate how many null packets should be inserted in this segment to reach the target bitrate.
Insert this amount of null packets all along the segment.
Account the remaining bits (less than one full packet) for next segment.

In your file, the bitrate of each segment is erratic, sometimes exceeding the target bitrate by far.
Moreover, most video PID's are incorrectly stamped. There are 100 services and 100 video PID's. The PMT of each service indicates its video PID as PCR PID. However, only the PID 101 seems correctly stamped (1519 PCR values). The PID 151 contains only 18 PCR values. All other 98 video PID's have zero PCR values. So, at least the signalization is incorrect (PCR PID's in PMT's do not contain PCR's).
The final bitrate value includes parts which were stuffed to 42 Mb/s and parts which were already much higher than this, giving an average which is higher than 42 Mb/s.
Anyway, given the extremely erratic nature of the stream, average bitrate values do not really mean anything here.

Some more debug message:
segment: 33 ms, 181 packets, 8,166,720 b/s
segment: 33 ms, 718 packets, 32,396,160 b/s
segment: 33 ms, 298 packets, 13,445,760 b/s
segment: 33 ms, 218 packets, 9,836,160 b/s
segment: 33 ms, 218 packets, 9,836,160 b/s
segment: 33 ms, 200 packets, 9,024,000 b/s
segment: 33 ms, 9 packets, 406,080 b/s
segment: 33 ms, 1,909 packets, 86,134,080 b/s
segment: 33 ms, 233 packets, 10,512,960 b/s
segment: 33 ms, 255 packets, 11,505,600 b/s
segment: 33 ms, 213 packets, 9,610,560 b/s
segment: 33 ms, 200 packets, 9,024,000 b/s
segment: 33 ms, 188 packets, 8,482,560 b/s
segment: 33 ms, 216 packets, 9,745,920 b/s
segment: 33 ms, 4,569 packets, 206,153,280 b/s
segment: 33 ms, 2,200 packets, 99,264,000 b/s
segment: 33 ms, 218 packets, 9,836,160 b/s
segment: 33 ms, 222 packets, 10,016,640 b/s
segment: 33 ms, 20 packets, 902,400 b/s
segment: 33 ms, 255 packets, 11,505,600 b/s
segment: 33 ms, 213 packets, 9,610,560 b/s
segment: 33 ms, 200 packets, 9,024,000 b/s
segment: 33 ms, 1,909 packets, 86,134,080 b/s
segment: 33 ms, 200 packets, 9,024,000 b/s
segment: 33 ms, 182 packets, 8,211,840 b/s
...

The PCR in PID 101 have a steady interval of 33 ms but the number of total packets between two of them is not constant. There are bursts and holes. The most frequent pattern is about 200 packets per PCR segment, giving a plausible bitrate of 9 Mb/s. But there are bursts of thousands of packets, making the stream impossible to smoothen.

I see, well i'll close the issue as it seems a problem with my source file rather than the software, thank you.

repo: tsduck/tsduck


text:
[BUG] Page Keycloak - /tutorials/keycloak

After I run npm install --save keycloak-connect , folders under node_modules/@tsed are removed. No matter I use npm or yarn. If use yarn, @tsed folder will be removed.

This is the package.json generated by "tsed init .".
{
  "name": "tsed",
  "version": "1.0.0",
  "description": "",
  "scripts": {},
  "dependencies": {
    "express-session": "^1.17.3",
    "keycloak-connect": "^21.1.1"
  },
  "tsed": {
    "convention": "default",
    "architecture": "default",
    "packageManager": "npm"
  },
  "devDependencies": {
    "@types/express-session": "^1.17.7"
  }
}

`

Hello @yingl
The latest release fix that :)

authors: Romakita yingl

repo: tsedio/tsed


text:
🛑 glarnerland.ch is down

In 1d11e06, glarnerland.ch (https://glarnerland.chh) was down:

HTTP code: 0
Response time: 0 ms

Resolved: glarnerland.ch is back up in 18451c8 after 1 minute.

repo: tsolenthaler/upptime


text:
Added new 404 page template

Hello @matteobruni again, this time I have tried to fulfill all your needs. I have added a new 404 page template. Please accept my PR.

LGTM


text:
Uncaught TypeError: Cannot read property 'querySelector' of null

[Enter steps to reproduce below:]

Opened a js-file

Atom Version: 1.2.4
System: Mac OS X 10.11.1
Thrown From: atom-ternjs package, v0.10.2
Stack Trace
Uncaught TypeError: Cannot read property 'querySelector' of null
At /Users/viljami/.atom/packages/atom-ternjs/lib/atom-ternjs-manager.js:352

TypeError: Cannot read property 'querySelector' of null
    at /Users/viljami/.atom/packages/atom-ternjs/lib/atom-ternjs-manager.js:352:45
    at Workspace.module.exports.Workspace.observeTextEditors (/Applications/Atom.app/Contents/Resources/app.asar/src/workspace.js:282:9)
    at Manager.registerEvents (/Users/viljami/.atom/packages/atom-ternjs/lib/atom-ternjs-manager.js:325:42)
    at Manager.activate (/Users/viljami/.atom/packages/atom-ternjs/lib/atom-ternjs-manager.js:59:10)
    at Manager.startServer (/Users/viljami/.atom/packages/atom-ternjs/lib/atom-ternjs-manager.js:163:14)
    at Manager.initServers (/Users/viljami/.atom/packages/atom-ternjs/lib/atom-ternjs-manager.js:127:14)
    at Manager.init (/Users/viljami/.atom/packages/atom-ternjs/lib/atom-ternjs-manager.js:44:10)

Commands

Config
{
  "core": {
    "themes": [
      "one-dark-ui",
      "chester-atom-syntax"
    ],
    "disabledPackages": [
      "git-plus",
      "auto-indent",
      "SFTP-deployment",
      "jsdoc",
      "language-cshtml",
      "merge-conflicts",
      "project-manager",
      "Remote-FTP",
      "atom-color-highlight"
    ],
    "packagesWithKeymapsDisabled": [
      "tidy-tabs"
    ]
  },
  "atom-ternjs": {}
}

Installed Packages
# User
aligner, v0.17.3
atom-pair, v2.0.10
atom-spotify2, v2.1.2
atom-ternjs, v0.10.2
change-case, v0.6.0
chester-atom-syntax, v0.1.1
emmet, v2.3.15
file-icons, v1.6.12
minimap, v4.16.2
php-cs-fixer, v2.5.1
php-twig, v4.0.0
remote-sync, v3.5.0
symbols-tree-view, v0.10.1
sync-settings, v0.6.0
tidy-tabs, v0.3.0

# Dev
No dev packages

Is Use Shadow DOM disabled?

Thanks for the fix! :)

authors: thatsprettyfaroutman tststs

repo: tststs/atom-ternjs


text:
Parallelize browser processes rather than pages

I've created this for #7 :)
This PR makes parallelization in the CAPTURE phase more efficient. It because that considering TCP connection restrictions of Chromium, parallelization of browser processes can use CPU more efficiently than parallelization of pages in one browser process.

@tsuyoshiwada I also want to parallelize the PREPARE phase. But I do not know when I do it 😅  If I would do this, I open another PR.

Hi @Quramy, Thank you for contribute!!
Released as 1.1.0-alpha.2 :tada:

authors: Quramy tsuyoshiwada


text:
babel-loader version conflict with CRA (react-scripts)

Hey,
I only ran into this problem when I was doing a full reinstall of all my modules. Turns out CRA (currently) wants only babel-loader 8.0.6, but because of the semver in your package.json ("babel-loader": "^8.0.0"), your package is grabbing babel-loader 8.1.0, which CRA complains about when it's time to load its dependencies ("cra-append-sw" comes before "react-scripts" alphabetically, so your deps install first).
To get around this, I had to install all my modules EXCEPT for cra-append-sw, and then manually re-install cra-append-sw afterward.
This will be a problem during my deploy (coming up soon) because the module install and build steps are triggered automatically, and so they'll fail in the same way on my production server.
I'm not really sure how this issue can be fixed, short of removing "cra-append-sw" from my deps before each deploy, and then adding a postinstall script to install it.
Any ideas?

Alright, the only (real) solution I could find is to use yarn instead of npm. It looks like their dep hoisting is better than npm.
In my project, removing node_modules, package-lock, and yarn.lock, and then re-installing all deps using "yarn install" was able to dedupe the babel-loader dependency, and everything works fine.
If you've got nothing else to add, you can close this issue.

Didn't solve to me, I need to specify the --skip-compile option

@joaomantovani If you install cra-append-sw AFTER your complete install of CRA, then npm/yarn should be able to pick up the shared deps (webpack and babel). Just make sure you don't remove your package-lock.json or yarn.lock, which should be keeping track of the overlap. If you do ever need to remove your package-lock/yarn.lock, then you'll have to remove cra-append-sw from your deps, reinstall everything, and then install cra-append-sw separately.
CRA has very specific versioning in their deps, but cra-append-sw can piggyback off of whatever CRA grabs, so as long as CRA is installed first, cra-append-sw can share what is already in your node_modules.

Thanks for the good explanation :)

Sure thing. Hope it works out for ya.

repo: tszarzynski/cra-append-sw


text:
redundant init file are generated

code
-- ...
,['flare-nvim'] = {
  loaded = false,
  config = function()
  local success, err_msg = pcall(dofile, '/nix/store/20gs2w4i6dr707s3sm9km6q3aqh5gl8j-flare-nvim')
  if not success then
    err_msg = err_msg or '-- no msg --'
    logger.warn('[flare-nvim] configure error: ' .. err_msg)
  end
end
,
  opt_depends = {},
  opt_depends_after = {},
}
,['flutter-tools-nvim'] = {
  loaded = false,
  config = function()
  local success, err_msg = pcall(dofile, '/nix/store/z9g5inm28vbjfsgwpqlj6zp70ak7l0xv-flutter-tools-nvim')
  if not success then
    err_msg = err_msg or '-- no msg --'
    logger.warn('[flutter-tools-nvim] configure error: ' .. err_msg)
  end
end
-- ...

a36e8a3


text:
[feature request]Recommended to support the ability to get the line number where the nginx directive is located

Description.
It is recommended that the project support getting the location of the nginx directives in the original configuration file.
Scenarios of use.
Currently there is this need to configure constraints for a certain instruction block. Check whether this instruction configuration to meet the rules, check the verification piece by parsing the configuration instructions, enumeration or recursive implementation of the check rule comparison, but if the check does not meet the requirements, now need to return to the original file is located in the line, the front-end needs to highlight this line, and then for the error message or modification suggestions.
Currently found github.com/tufanbarisyildirim/gonginx.parser syntax parser on the line number is there, just missing the token into the parsing object (config.Block) on the missing, increase the set line number and get the line number method can be.
Solution.
Just add the GetLine(), SetLine(int) interface constraints to the IDirective interface and an implementation of that interface.
// github.com/tufanbarisyildirim/gonginx.parser
// lexer is the main tokenizer
type lexer struct {
    reader *bufio.Reader
    file string
    line int
    column int
    inLuaBlock bool
    Latest token.Token
}

// IDirective represents any directive
type IDirective interface {
    GetName() string //the directive name.
    GetParameters() []string
    GetBlock() IBlock
    GetComment() []string
    SetComment(comment []string)
    SetParent(IBlock)
    GetParent() IBlock
    GetLine() int // Get the line number of the command in the configuration file.
    SetLine(int) // set the line number of the command in the configuration file
    InlineCommenter
}

Interface constraints added

Entities that need to implement the interface

Test screenshots
Local analog data files
user                 nobody;
pid                  /run/nginx.pid;
worker_processes     auto;  # ok
# 配置Nginx worker进程最大打开文件数
worker_rlimit_nofile 8192;

# Load modules
include              /etc/nginx/modules-enabled/*.conf;

events {
    multi_accept       on;
    # 单个进程允许的客户端最大连接数
    worker_connections 4096;  # ok
    # 使用epoll模型
    use epoll;
}

http {
    charset                utf-8;
    sendfile                on;
    keepalive_timeout      65;
    tcp_nopush             on;
    tcp_nodelay            on;
    types_hash_max_size    2048;
    types_hash_bucket_size 64;

    # # 指定 DNS 解析器地址，这里使用了 Google 的公共 DNS 服务器
    resolver 8.8.8.8 [::1]:5353 valid=30s;

    #gzip模块设置
    gzip on; #开启gzip压缩输出
    gzip_min_length 1k;    #最小压缩文件大小
    gzip_buffers 4 16k;    #压缩缓冲区
    gzip_http_version 1.0;    #压缩版本（默认1.1，前端如果是squid2.5请使用1.0）
    gzip_comp_level 2;    #压缩等级
    gzip_types text/plain application/x-javascript text/css application/xml;    #压缩类型，默认就已经包含textml，所以下面就不用再写了，写上去也不会有问题，但是会有一个warn。
    gzip_vary on;

    #设定通过nginx上传文件的大小
    client_max_body_size 8m;
    #客户端请求头部的缓冲区大小。这个可以根据你的系统分页大小来设置，一般一个请求的头部大小不会超过1k，不过由于一般系统分页都要大于1k，所以这里设置为分页大小。分页大小可以用命令getconf PAGESIZE取得。
    client_header_buffer_size 32k;
    #缓冲区代理缓冲用户端请求的最大字节数
    client_body_buffer_size 128k;

    # MIME
    include                mime.types;
    default_type           application/octet-stream; # ok

    # Log Format
    log_format             cloudflare '$remote_addr - $remote_user [$time_local] "$request" $status $body_bytes_sent "$http_referer" "$http_user_agent" $http_cf_ray $http_cf_connecting_ip $http_x_forwarded_for $http_x_forwarded_proto $http_true_client_ip $http_cf_ipcountry $http_cf_visitor $http_cdn_loop';

    # Logging
    access_log             off;  # ok
    error_log              /var/log/nginx/error.log warn;

    # SSL
    ssl_session_timeout    1d;
    ssl_session_cache      shared:SSL:10m;
    ssl_session_tickets    off;

    # Diffie-Hellman parameter for DHE ciphersuites
    ssl_dhparam            /etc/nginx/dhparam.pem;

    # Mozilla Intermediate configuration
    ssl_protocols          TLSv1.2 TLSv1.3;
    ssl_ciphers            ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384;

    # OCSP Stapling
    ssl_stapling           on;
    ssl_stapling_verify    on;
    resolver               1.1.1.1 1.0.0.1 8.8.8.8 8.8.4.4 208.67.222.222 208.67.220.220 valid=60s;
    resolver_timeout       2s;

    upstream dynamic {
        zone upstream_dynamic 64k;
        ip_hash;
        keepalive 32;

        server backend1.example.com      weight=5;
        server backend2.example.com:8080 fail_timeout=5s slow_start=30s;
        server 192.0.2.1                 max_fails=3;
        server backend3.example.com      resolve;
        server backend4.example.com      service=http resolve;

        server backup1.example.com:8080  backup;
        server backup2.example.com:8080  backup;
    }

    upstream hi {
        zone upstream_dynamic 32k;
        server 192.0.2.11                 max_fails=3;
        server 192.0.2.12                 max_fails=3;
        server 192.0.2.13                 max_fails=3;
    }

    server {
        location / {
            proxy_pass http://dynamic;
            health_check;
        }

        location /hi {
            proxy_pass http://hi;
            health_check;
        }
    }

    server {
        listen       80  default_server;
        listen      8080;
        server_name  _;
        return       444;
    }

    server {
        listen 80;
        listen      8081;
        server_name domain1.com www.domain1.com;
        location / { proxy_pass http://127.0.0.1:8080; }
    }

    # Load configs
    include                /etc/nginx/conf.d/*.conf;
    include                /etc/nginx/sites-enabled/*;

    # 隐藏版本号
    server_tokens off;
}

Test Results
===========GlobalBlocks==============
keyword: user, path: global.user, line: 1 params: [nobody]
keyword: pid, path: global.pid, line: 2 params: [/run/nginx.pid]
keyword: worker_processes, path: global.worker_processes, line: 3 params: [auto]
keyword: worker_rlimit_nofile, path: global.worker_rlimit_nofile, line: 5 params: [8192]
keyword: include, path: global.include, line: 8 params: [/etc/nginx/modules-enabled/*.conf]
===========EventsBlocks==============
keyword: multi_accept, path: events.multi_accept, line: 11 params: [on]
keyword: worker_connections, path: events.worker_connections, line: 13 params: [4096]
keyword: use, path: events.use, line: 15 params: [epoll]
===========HttpBlock.HttpGlobalBlocks==============
keyword: charset, path: http.charset, line: 19 params: [utf-8]
keyword: sendfile, path: http.sendfile, line: 20 params: [on]
keyword: keepalive_timeout, path: http.keepalive_timeout, line: 21 params: [65]
keyword: tcp_nopush, path: http.tcp_nopush, line: 22 params: [on]
keyword: tcp_nodelay, path: http.tcp_nodelay, line: 23 params: [on]
keyword: server_tokens, path: http.server_tokens, line: 24 params: [off]
keyword: types_hash_max_size, path: http.types_hash_max_size, line: 25 params: [2048]
keyword: types_hash_bucket_size, path: http.types_hash_bucket_size, line: 26 params: [64]
keyword: resolver, path: http.resolver, line: 29 params: [8.8.8.8 [::1]:5353 valid=30s]
keyword: gzip, path: http.gzip, line: 32 params: [on]
keyword: gzip_min_length, path: http.gzip_min_length, line: 33 params: [1k]
keyword: gzip_buffers, path: http.gzip_buffers, line: 34 params: [4 16k]
keyword: gzip_http_version, path: http.gzip_http_version, line: 35 params: [1.0]
keyword: gzip_comp_level, path: http.gzip_comp_level, line: 36 params: [2]
keyword: gzip_types, path: http.gzip_types, line: 37 params: [text/plain application/x-javascript text/css application/xml]
keyword: gzip_vary, path: http.gzip_vary, line: 38 params: [on]
keyword: client_max_body_size, path: http.client_max_body_size, line: 41 params: [8m]
keyword: client_header_buffer_size, path: http.client_header_buffer_size, line: 43 params: [32k]
keyword: client_body_buffer_size, path: http.client_body_buffer_size, line: 45 params: [128k]
keyword: include, path: http.include, line: 48 params: [mime.types]
keyword: default_type, path: http.default_type, line: 49 params: [application/octet-stream]
keyword: log_format, path: http.log_format, line: 52 params: [cloudflare '$remote_addr - $remote_user [$time_local] "$request" $status $body_bytes_sent "$http_referer" "$http_user_agent" $http_cf_ray $http_cf_connecting_ip $http_x_forwarded_for $http_x_forwarded_proto $http_true_client_ip $http_cf_ipcountry $http_cf_visitor $http_cdn_loop']
keyword: access_log, path: http.access_log, line: 55 params: [off]
keyword: error_log, path: http.error_log, line: 56 params: [/var/log/nginx/error.log warn]
keyword: ssl_session_timeout, path: http.ssl_session_timeout, line: 59 params: [1d]
keyword: ssl_session_cache, path: http.ssl_session_cache, line: 60 params: [shared:SSL:10m]
keyword: ssl_session_tickets, path: http.ssl_session_tickets, line: 61 params: [off]
keyword: ssl_dhparam, path: http.ssl_dhparam, line: 64 params: [/etc/nginx/dhparam.pem]
keyword: ssl_protocols, path: http.ssl_protocols, line: 67 params: [TLSv1.2 TLSv1.3]
keyword: ssl_ciphers, path: http.ssl_ciphers, line: 68 params: [ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384]
keyword: ssl_stapling, path: http.ssl_stapling, line: 71 params: [on]
keyword: ssl_stapling_verify, path: http.ssl_stapling_verify, line: 72 params: [on]
keyword: resolver, path: http.resolver, line: 73 params: [1.1.1.1 1.0.0.1 8.8.8.8 8.8.4.4 208.67.222.222 208.67.220.220 valid=60s]
keyword: resolver_timeout, path: http.resolver_timeout, line: 74 params: [2s]
keyword: include, path: http.include, line: 125 params: [/etc/nginx/conf.d/*.conf]
keyword: include, path: http.include, line: 126 params: [/etc/nginx/sites-enabled/*]
keyword: server_tokens, path: http.server_tokens, line: 129 params: [off]
===========HttpBlock.ServerGlobalBlocks==============
keyword: listen, name: http.server[1].listen, path: http.server.listen, line: 111 params: [80 default_server]
keyword: listen, name: http.server[1].listen, path: http.server.listen, line: 112 params: [8080]
keyword: server_name, name: http.server[1].server_name, path: http.server.server_name, line: 113 params: [_]
keyword: return, name: http.server[1].return, path: http.server.return, line: 114 params: [444]
keyword: listen, name: http.server[2].listen, path: http.server.listen, line: 118 params: [80]
keyword: listen, name: http.server[2].listen, path: http.server.listen, line: 119 params: [8081]
keyword: server_name, name: http.server[2].server_name, path: http.server.server_name, line: 120 params: [domain1.com www.domain1.com]
===========HttpBlock.UpstreamBlocks==============
keyword: upstream, name: http.upstream[0], path: http.upstream.upstream, line: 89 params: [dynamic]
keyword: zone, name: http.upstream[0].zone[0], path: http.upstream.zone, line: 77 params: [upstream_dynamic 64k]
keyword: ip_hash, name: http.upstream[0].ip_hash[0], path: http.upstream.ip_hash, line: 78 params: []
keyword: keepalive, name: http.upstream[0].keepalive[0], path: http.upstream.keepalive, line: 79 params: [32]
keyword: server, name: http.upstream[0].server[0], path: http.upstream.server, line: 81 params: [backend1.example.com weight=5]
keyword: server, name: http.upstream[0].server[1], path: http.upstream.server, line: 82 params: [backend2.example.com:8080 fail_timeout=5s slow_start=30s]
keyword: server, name: http.upstream[0].server[2], path: http.upstream.server, line: 83 params: [192.0.2.1 max_fails=3]
keyword: server, name: http.upstream[0].server[3], path: http.upstream.server, line: 84 params: [backend3.example.com resolve]
keyword: server, name: http.upstream[0].server[4], path: http.upstream.server, line: 85 params: [backend4.example.com service=http resolve]
keyword: server, name: http.upstream[0].server[5], path: http.upstream.server, line: 87 params: [backup1.example.com:8080 backup]
keyword: server, name: http.upstream[0].server[6], path: http.upstream.server, line: 88 params: [backup2.example.com:8080 backup]
keyword: upstream, name: http.upstream[1], path: http.upstream.upstream, line: 96 params: [hi]
keyword: zone, name: http.upstream[1].zone[0], path: http.upstream.zone, line: 92 params: [upstream_dynamic 32k]
keyword: server, name: http.upstream[1].server[0], path: http.upstream.server, line: 93 params: [192.0.2.11 max_fails=3]
keyword: server, name: http.upstream[1].server[1], path: http.upstream.server, line: 94 params: [192.0.2.12 max_fails=3]
keyword: server, name: http.upstream[1].server[2], path: http.upstream.server, line: 95 params: [192.0.2.13 max_fails=3]

Hopefully this suggestion will be taken up.
I will also raise a PR for support of this feature and hopefully adopt the merge.

I had a similar need to get the line number of the directive.

authors: amassx sharelinux

repo: tufanbarisyildirim/gonginx


text:
行内代码字体显示不正常

只有IE上能显示出是monospace字体，Chrome和Firefox上都认不出来，被替换成了系统默认的宋体，导致展示效果不佳。

这个应该是跟文章中其它文字一起变的，但目前还真不清楚怎么控制。

在style.scss中增加
code {
    font-family: Menlo, Consolas, monospace !important;
}

似乎在FireFox、Chrome和IE中可行。

@YetAnotherCP 能否说一下具体是添加在了style.scss中的哪个位置？

我是加在body之前，测试有效，感谢@YetAnotherCP提供的方法

多谢，已经添加上了。

authors: YetAnotherCP kloudmuka tufu9441


text:
KafkaJS is not re-auhtenticating to all brokers

Describe the bug
When I run kafkajs with multiple brokers I see in logs that it authenticated to all of them successfuly
[KafkaJS] [SASLOAuthBearerAuthenticator][DEBUG] - Authenticate with SASL OAUTHBEARER kafka-1.flucivja.local:9094
[KafkaJS] [SASLOAuthBearerAuthenticator][DEBUG] - SASL OAUTHBEARER authentication successful kafka-1.flucivja.local:9094

[KafkaJS] [SASLOAuthBearerAuthenticator][DEBUG] - Authenticate with SASL OAUTHBEARER kafka-2.flucivja.local:9094
[KafkaJS] [SASLOAuthBearerAuthenticator][DEBUG] - SASL OAUTHBEARER authentication successful kafka-2.flucivja.local:9094

then I see it succesfully receving topics and when reauthenticationThreshold  is hit then re-authentication happes but only to first broker
[KafkaJS] [SASLOAuthBearerAuthenticator][DEBUG] - Authenticate with SASL OAUTHBEARER kafka-1.flucivja.local:9094
[KafkaJS] [SASLOAuthBearerAuthenticator][DEBUG] - SASL OAUTHBEARER authentication successful kafka-1.flucivja.local:9094

then it is working for a while and suddenly I got this error where it is clearly visible that connection was closed by second broker because client didn't re-authenticate to it.
[KafkaJS] [Connection][DEBUG] - Kafka server has closed connection kafka-2.flucivja.local:9094
[KafkaJS] [Connection][DEBUG] - disconnecting...
[KafkaJS] [Connection][DEBUG] - disconnected
[KafkaJS] [Runner][DEBUG] - Error while fetching data, trying again...
[KafkaJS] [ConsumerGroup][DEBUG] - Fetching from 1 partitions for 1 out of 1 topics
 [KafkaJS] [Connection][DEBUG] - Request Fetch(key: 1, version: 11)
 [KafkaJS] [Connection][DEBUG] - Response Fetch(key: 1, version: 11)
 [KafkaJS] [Runner][DEBUG] - Error while fetching data, trying again...
... repeated several times
[KafkaJS] [Consumer][ERROR] - Crash: KafkaJSNumberOfRetriesExceeded: Not connected
[KafkaJS] [Runner][DEBUG] - stop consumer group
[KafkaJS] [Consumer][INFO] - Stopped
[KafkaJS] [Consumer][DEBUG] - consumer has stopped, disconnecting
[KafkaJS] [Connection][DEBUG] - disconnecting...
[KafkaJS] [Connection][DEBUG] - disconnected
[KafkaJS] [Consumer][ERROR] - Restarting the consumer
...then consumer is restarted and same happens every 5 minutes

To Reproduce
You need to run KafkaJS with multiple brokers with SASL OAUTHBEARER auth and server brokers must be configured that client needs to reauthenticate every e.g. 5 minutes.
Expected behavior
KafkaJS re-authenticates to all connected brokers
Environment:

Mac OS and also Linux
KafkaJS version 1.15.0
NodeJS version 14

I found possible root cause:

it connects to consumer group leader and coordinator
it does re-authentication to group leader but not to coordinator
it runs heartbeat requests only to coordinator
when session expires, coordinator disconnects consumer and re-connects again

Possible fix: re-authenticate before heartbeat when needed and created PR #1241 with this fix which runs ok and without any errors within my environment.

Great contribution, @flucivja. Thanks.

authors: flucivja giulliano-bueno

repo: tulios/kafkajs


text:
Obstacle Detector

Port LMS crossing detection to ROS. Seems to be written a lot less nicer than the other components, so requires much more work:

obstacle_detection.h
obstacle_detection.cpp

Use OpenCV for edge detection algorithms and line iteration (can use a common header with related operations), line-related geometric operations can be added  here, will be using boost::geometry as base, if you want to use CGAL or something else, please feel free to suggest.

We have a clustering-based obstacle detection working. A corner-based detector remains a goal, but since this is working initially, I am closing this.


text:
Remove ignored namespaces check

What and why?
Fixes #44 and #52.
Remove the ignored namespaces check from the code in favour of a namespaceSelector in the webhook example. Not only does this allow users to inject into pods in kube-system if they want to, it also provides more protection against problems with the webhook as pods from ignored namespaces won't be forwarded to the webhook at all.
This PR also tweaks the logging in the mutate function to account for the fact that the object metadata may not contain name or namespace information.
Testing Steps
Please provide adequate testing steps (including screenshots if necessary).
Include any test fixtures or sample configurations in your commit.

[x] Added unit tests for this feature (make test)

Reviewers
Required reviewers: @byxorna
Request reviews from other people you want to review this PR in the "Reviewers" section on the right.

:warning: this PR must have at least 2 thumbs from the MAINTAINERS.md of the project before merging!

Ping - just checking if anyone has had a chance to look at this?


text:
native_inline_images option borks

Using native_inline_images option for photo posts is failing.
client.photo(req.body.blogname, {
		source: 'https://img.buzzfeed.com/buzzfeed-static/static/2014-04/enhanced/webdr03/4/16/enhanced-26552-1396642701-1.jpg?no-auto',
		native_inline_images: true,
	}, function(){});

Stack trace:
_http_outgoing.js:443
    throw new TypeError('first argument must be a string or Buffer');
    ^

TypeError: first argument must be a string or Buffer
    at ClientRequest.OutgoingMessage.write (_http_outgoing.js:443:11)
    at Request.write (/Volumes/space/server/node_modules/request/request.js:1371:25)
    at FormData.ondata (stream.js:31:26)
    at emitOne (events.js:90:13)
    at FormData.emit (events.js:182:7)
    at FormData.CombinedStream.write (/Volumes/space/server/node_modules/combined-stream/lib/combined_stream.js:118:8)
    at FormData.CombinedStream._pipeNext (/Volumes/space/server/node_modules/combined-stream/lib/combined_stream.js:106:8)
    at FormData.CombinedStream._getNext (/Volumes/space/workspace/server/node_modules/combined-stream/lib/combined_stream.js:79:10)
    at FormData.CombinedStream._pipeNext (/Volumes/space/workspace/server/node_modules/combined-stream/lib/combined_stream.js:107:8)
    at FormData.CombinedStream._getNext (/Volumes/space/server/node_modules/combined-stream/lib/combined_stream.js:79:10)

Maybe I misunderstood what this option is for. The docs are super vague, but it seems like this is only for html images and not photo posts.

Convert any external image URLs to Tumblr image URLs

Maybe it's failing because I'm not supplying a caption? Either way, I don't think it should bork if caption is missing.

I got this problem today, use
native_inline_images: "true"

I got this problem today, solution:
native_inline_images: 'true'
work with html format, don't work with markdown, what a shame >_<

@positlabs: yeah, the documentation for native_inline_images could be a little clearer. it only applies to images in the body/caption field of posts, where we consider images "inline" with the text caption as opposed to being the front-and-center media content of the post.
for the case you're describing, what you're trying to do, you shouldn't need native_inline_images in the first place; source: 'https://img.buzzfeed.com/buzzfeed-static/static/2014-04/enhanced/webdr03/4/16/enhanced-26552-1396642701-1.jpg?no-auto' should be enough to create a photo post from that external image.
@nemesisqp: you're right that native_inline_images doesn't currently work for markdown posts. sorry!
closing this for now since it's behaving correctly.

authors: kmck nemesisqp positlabs


text:
Remove "reblog" comment on reblog action

Hi.
I would like to know if there a way to remove "reblog comments" of a post when reblogging through the API, like it's possible on the Tumblr web interface.
thanks

Tumblr API#reblogging doesn't mentions anything like this, so I think it isn't possible.

authors: Colir matheusmariano


text:
Add the Tetra Mod

What is the problem you're trying to solve with this change?
The tetra mod is a great mod that fits into the Create theme of this pack. You can make custom tools with different parts, but its different from Tinkers construct as there is no smelting.
What do you propose as a solution?
https://www.curseforge.com/minecraft/mc-mods/tetra

Tetra is already in the modpack.

repo: tungstonminer/blocky-go-round


text:
[Feature request]: Add ability to set server.origin to fix CORS with Vite

Is your feature request related to a problem? Please describe.
Using certain features, such as Workers/SharedWorkers requires that the loaded resource has the same origin.
With tuono dev I'm now getting the following error when loading a SharedWorker:
Uncaught (in promise) SecurityError: Failed to construct 'SharedWorker': Script at 'http://localhost:3000/vite-server/@fs/project/src/lib/worker.ts?worker_file&type=classic' cannot be accessed from origin 'https://project.localhost'.

The file is confirmed available from the URL https://project.localhost/vite-server/@fs/project/src/lib/worker.ts?worker_file&type=classic'.
Describe the solution you'd like
It appears that being able to control the Vite setting server.origin would allow fixing this CORS issue.
At the same time, it would be good if the functionality of server.host and server.port could be controlled as well.
Describe alternatives you've considered
No response
Additional context
No response

To reproduce, add the following to tuono-app example:
tuono-app/src/routes/worker.ts
onmessage = function(e) {
  console.log('Worker: Message received from main script');
  const result = e.data[0] * e.data[1];
  if (isNaN(result)) {
    postMessage('Please write two numbers');
  } else {
    const workerResult = 'Result: ' + result;
    console.log('Worker: Posting message back to main script');
    postMessage(workerResult);
  }
}

tuono-app/src/routes/index.tsx
import type { JSX } from 'react'
import type { TuonoProps } from 'tuono'

interface IndexProps {
	subtitle: string
}

export default function IndexPage({
	data,
	isLoading,
}: TuonoProps<IndexProps>): JSX.Element {
    const setupWorker = () => {
        const myWorker = new Worker(new URL("./worker.ts", import.meta.url));
    };

	return (
        <button onClick={setupWorker}>Setup Worker</button>
	)
}

Running tuono dev and accessing the application at http://localhost:3000 and clicking the button works fine and does not result in errors in the developer console, as the worker can be loaded.
Running tuono dev and accessing the application via a HTTPS proxy such as nginx or caddy from a URL such as https://project.localhost and clicking the button results in the following error in the developer console, as the worker cannot be loaded due to mismatching CORS origin:

Uncaught SecurityError: Failed to construct 'Worker': Script at 'http://localhost:3000/vite-server/@fs/tuono-app/src/routes/worker.ts?worker_file&type=classic' cannot be accessed from origin 'https://project.localhost'. at setupWorker (index.tsx:13:26) setupWorker	@ index.tsx:13

See info about same-origin policy: https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy

Note that it is easiest to test with Chrome, as Firefox does not seem to provide this error message in the developer console.

on tuono we hardcoded localhost:3000 for the vite hmr https://github.com/tuono-labs/tuono/blob/main/packages/tuono/src/ssr/index.tsx#L20
maybe we can change it to window.location.hostname ?

nvm, i just realize it's part of the code that run on the worker. can't get the hostname that way

const myWorker = new Worker(new URL("./worker.ts", import.meta.url));
To access this file it needs to be within the public/ folder

The issue is not that the script is not available. It is available and can be downloaded from the URL:
http://localhost:3000/vite-server/@fs/project/src/lib/worker.ts?worker_file&type=classic
The issue is that when using a HTTPS proxy with the site hosted at https://project.localhost, the file cannot be used by the browser, as it is not allowed to load certain resource types from different origins. SharedWorker scripts must be loaded from the same origin. This is why I believe controlling the server.origin will resolve the issue, as it will allow the script to be loaded from the same origin as the client sees, which is the URL http://project.localhost/vite-server/@fs/project/src/lib/worker.ts?worker_file&type=classic.
I've only used the routes/ folder for the worker.ts in the example. In my own project I have worker.ts in src/lib with the same issue. Placing the script in the public folder and loading it from new URL("/worker.ts", import.meta.url) results in the same issue:
The URL http://localhost:3000/vite-server/@fs/mnos-v2/crates/mnos_web/public/storePathWorker.ts?worker_file&type=module is valid and contains the script, however it cannot be accessed from the origin https://project.localhost as the same-origin policy requires resources to be loaded from the same origin.

authors: Valerioageno mustafasegf pveierland

repo: tuono-labs/tuono


text:
Fix link

fix #211

Chez moi ça marche (tm)

authors: dmerejkowsky maggick

license: WTFPL


text:
Consider Renaming the Repository

As Cyph0n said on Hacker News:

I'd recommend naming the repo turbo or turbojs, instead of just js.

It is odd find a folder merely named js after you clone the repository.

Soon.

authors: msimpson turbo

repo: turbo/js


text:
Enable Analysis of AWS Metrics with Extended Metrics Points aws_cloudwatch_metric_statistic_data_point

Table name
aws_cloudwatch_metric_statistic_data_point
New column name
ExtendedStatistics - like p95 or p99
Description
This feature request proposes extending the listCloudWatchMetricStatisticDataPoints function in Steampipe to support retrieving extended statistics like p95 and p99 for AWS metrics.
Current limitation
The current implementation only retrieves the basic statistics for AWS metrics.
Proposed Solution
Introduce a new optional argument ExtendedStatistics of type []string to the listCloudWatchMetricStatisticDataPoints function. This argument will allow users to specify a list of extended statistics (e.g., "p99", "p95") to be retrieved along with the basic statistics.
Update the function to include the ExtendedStatistics argument in the request to the CloudWatch API.
Add new columns to the output schema to accommodate the retrieved extended statistics values.
Additionally, I suggest augmenting the function to include support for reading and processing these extended metric results. I have already implemented these modifications locally and verified their functionality through thorough testing.
Furthermore, I aim to generalise the codebase to facilitate future extensibility. By implementing a flexible mechanism, users will have the capability to specify any desired extended metric, such as "p65", in their select queries and retrieve the corresponding data points. This approach enhances the versatility of the codebase and accommodates potential future requirements effortlessly.
Alternatives Considered
I have contemplated alternative approaches, including generating all possible combinations of extended metrics points ranging from p1 to p99. However, this approach is deemed impractical as it would result in excessive data retrieval, potentially burdening the system with unnecessary processing overhead. Therefore, I am seeking guidance from the team to explore the most effective approach to address this requirement.

I saw the release 0.133.0 and tried it out. end_time is coming as null.
Couple of other columns are coming in as null such as
resource_name
resource_type

The ExtendedStatistics parameter in GetMetricStatisticsInput is of type []string and is used for specifying percentile statistics between p0.0 and p100. In the GetMetricStatistics API call, you must choose either Statistics or ExtendedStatistics, but not both. For example, you can specify ExtendedStatistics as []string{"p95", "p100"}. The response for these parameters will be in the format map[string]float64, such as {"p100": 0.500000000000303, "p95": 0.49568533302992535}.
However, when attempting to query this data, matching the extended_statistics directly in a WHERE clause can be problematic. This is because the WHERE condition expects a string representation of the array, which does not directly correspond to the map structure returned in the response.
select
  *
from
  aws_cloudwatch_metric_statistic_data_point
where
  namespace = 'AWS/EC2'
  and metric_name = 'CPUUtilization'
  and extended_statistics = '["p100"]'
  and dimensions = '[
    {"Name": "InstanceId", "Value": "i-04a9bf67bc23432432"}
    ]'
order by
  timestamp;

To address this, consider modifying the schema by introducing two new columns: extended_statistics_labels and extended_statistics. The extended_statistics_labels should be a JSON column to store the labels (e.g., ["p100", "p95"]) as an optional parameter. The extended_statistics column should be a JSON type to hold the actual numerical values (e.g., {"p100": 0.500000000000303, "p95": 0.49568533302992535}).
@cbruno10 @misraved @kaushikkishore please share your thoughts.

authors: bigdatasourav kartik7153 kaushikkishore

repo: turbot/steampipe-plugin-aws


text:
Add check to not entirely abort when invalid DNS entry is found

Example query results

Results

echo "select domain, not_after from net_certificate where domain IN ('www.tamu.edu', 'blahblah.blah');" | steampipe query
+--------------+---------------------------+
| domain       | not_after                 |
+--------------+---------------------------+
| www.tamu.edu | 2023-01-19T17:59:59-06:00 |
+--------------+---------------------------+

Thanks again, @bdd4329, for raising the bug and submitting the PR to fix it! We'll release this in a new plugin version later this week.

repo: turbot/steampipe-plugin-net


text:
Version 1.4.7 is not published on npm registry

It seems like the version 1.4.7 has not been published on the npm registry.
Was it done on purpose or it is a mistake ?

This was a mistake on my side. I'm fixing this right now. Thanks for reporting!

1.4.7 was just published on npm:
https://www.npmjs.com/package/@turingpointde/cvss.js?activeTab=versions

authors: Fubinator antoinm


text:
Sending blank response body does not provide runtime type safety

having schema set like this
export const schema = {
    response: {
        201: z.object({
            status: z.literal('success'),
            data: z.object({
                id: z.number()
            })
        })
    }
}

sending blank response DOES NOT raise ts error
export const testCommandHandler = async (
    req: FastifyRequestZod<typeof schema >,
    reply: FastifyReplyZod<typeof schema >
) => {
    return reply.status(201).send()
}

changing it to object does raise ts err
return reply.status(201).send({})

It's a behavior from Fastify.
The send method param is optional, so you can pass whatever was inferred from the schema or undefined (nothing).
I've already opened an issue to discuss this point https://github.com/fastify/fastify/issues/5534

authors: JonRC tzezar

repo: turkerdev/fastify-type-provider-zod


text:
Complement tests are trying to set a profile (displayname) now

Needs more proxy

Complement tests just won't work for this project.


text:
changes

Dark/light button was covering text, I fixed it. In Contributing.md I changed Healthcare-Platform to Medical-Website. And I also changed OriginalOwner to tushargupta1504. Thank you, this is my first open source contribution.


text:
[bug] Close the world when connecting

Game version: 1.21.22
Only the port and time zone were modified,
When I connect, the world will be closed directly. Even when re-entering the world, it will be closed again.

Have you disabled the Require Encrypted Websockets?
Currently this library doesn't support encryption.

It seems that it cannot be disabled...

Leave the world and try again from main menu

Leave the world and try again from main menu

This doesn't work, but restarting Minecraft can.


text:
Can't get the Authorization to work.

I love the idea behind slim-jwt-auth and i'm trying to use it for my API, but i'm completely stuck trying to get my supersecret key to even validate.
Somehow it is not clear to me, how to properly pass the secret key to the Middleware for it to properly authenticate it, and respond.
I get constantly an 401 in my browser, or when testing with test-cors http://client.cors-api.appspot.com/client#?client_method=GET&client_credentials=true&client_headers=Authorization%3ABearer r8uGz9YQFPLdmWQBHRU9eNYe2j3FP4rLQ9NgrShQTBv7FMxjaXnjhJcvUkXeh7gS&server_url=https%3A%2F%2Fapi.teamglobalapp.com%2Fv1%2Fslides&server_enable=true&server_status=200&server_credentials=false&server_tabs=remote
I already added the configuration needed to the .htaccess.
Maybe i'm doing something wrong ? Do i need to encode the secret pass first at http://jwt.io/ ??
I have spent hours trying to understand how to properly validate this and nothing, if you can kindly point me in the right direction, i will most likely appreciate it, as it is not clear in the docs.
Thank you so much !

You pass the secret key for verifying signature in the secret parameter.
$app->add(new \Slim\Middleware\JwtAuthentication([
    "secret" => "supersecretkeyyoushouldnotcommittogithub"
]));

I do not know how you generated the token, but looking at the example url above the header it tries to send is.
Authorization: Bearer r8uGz9YQFPLdmWQBHRU9eNYe2j3FP4rLQ9NgrShQTBv7FMxjaXnjhJcvUkXeh7gS

The token part is not a valid JWT.
Header with valid example JWT token looks something like below. You can also verify this. Token is signed using secret fearlex (you need to write that in the verify box).
Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJuYW1lIjoiQXJsZXlzIFJlc2NvIiwiYWRtaW4iOnRydWV9.Rvsr4CScemkXpY0qvA21iF1hD07yGiGZJSo9REoXYcE

Middleware itself expects to find the token in either the Authorization: Bearer header or cookie named token.

Thank you so much, your response help clarify a few things. I appreciate you taking your time to help and to build such an amazing tool.
Thanks again.

authors: fearlex tuupola

repo: tuupola/slim-jwt-auth


text:
Make concepts into a cabal library package

This way it can be used by others easily. Should be published as well.

So, I propose the following course of action:

[ ] Move both C-element examples from Main.hs to Test.hs.
[ ] After that there is pretty much nothing left in Main.hs, so it can be dropped.
[ ] Add haddock comments, see separate issue: #10.
[ ] Update .cabal file to turn it into library.
[ ] Find an appropriate category to release the package, perhaps Hardware.Concepts? See https://hackage.haskell.org/packages/#cat:Hardware
[ ] Push to Hackage!

I've pushed a major source structure refactoring, addressing two tasks above. Feedback welcome.

I would add another item: formally tagging our first release, e.g. v0.0.1 on git. Anything that is pushed to hackage should be tagged on git.

Move both C-element examples from Main.hs to Test.hs.

I had this in mind, will post a PR soon.

After that there is pretty much nothing left in Main.hs, so it can be dropped.

Sure. It could be turned into our simulate executable, but I don't know what the easiest course of action would be since we'd have to hard-code what is being simulated. The same applies to what I'm building - how will the user specify the haskell file containing the circuit, initial state, etc? Surely it has to be at compile time, but I don't know if we could do it via build flags, by modifying the cabal file, ...

I would add another item: formally tagging our first release, e.g. v0.0.1 on git. Anything that is pushed to hackage should be tagged on git.

Added. IIRC this happens automatically when we do a github release.

It could be turned into our simulate executable, but I don't know what the easiest course of action would be since we'd have to hard-code what is being simulated.

I think we better just drop it, replacing it with tests and possibly some overview haddock section.

The same applies to what I'm building - how will the user specify the haskell file containing the circuit, initial state, etc? Surely it has to be at compile time, but I don't know if we could do it via build flags, by modifying the cabal file

Not sure yet. Maybe it's possible to use GHC API to compile a given concepts spec.hs in runtime. Could you check?

I think we better just drop it, replacing it with tests and possibly some overview haddock section.

SGTM

Not sure yet. Maybe it's possible to use GHC API to compile a given concepts spec.hs in runtime (the filename could passed via command line). Could you check?

Remember what you said about requiring GHC to be installed to be too much? This is pretty much the same - we would have to bundle at least part of the compiler with our binary. If the compiler is modular enough this should be possible, and if it's well written enough the overhead in size should not be too large. I'll look into it.

@mvdan Good point. However, as a first step you should implement your conversion algorithm just as a library function, e.g.:
deriveSTG :: (Eq a, Show a) => CircuitConcept a -> STG a

I guess a logical place to put it inside the source tree is Hardware.Concepts.STG, where you will also create appropriate type STG a, .g import and export, etc.
. There will then be a separate executable project

Sure. So you can transform either at compile time by using it as a library or at runtime (though also compiling) via the executable.

Yep, that's the point.
We could later add other 'backends': FSM (probably the most straightforward one), CPOG, etc.

Just so we're on the same page, STG a would be a data type, much like a struct, correct? Then showing that would actually generate the string that is the .g file.

Just so we're on the same page, STG a would be a data type, much like a struct, correct?

Yes, I think so.

Then showing that would actually generate the string that is the .g file.

I would avoid using Show for this purpose. Non-derived Show instances are frowned upon in general, so I should remove some of my Show instances too. Instead I suggest:
exportDotG :: STG String -> String
importDotG :: String -> STG String

If you make STG a Functor then the user will be free to do the renaming/retyping of labels in any way, maybe by show-ing all labels, maybe via other means. If you want to get a more fancy API you could also provide the following functions:
exportDotG' :: Show a => STG a -> String
exportDotG' = exportDotG . fmap show

importDotG' :: Read a => String -> STG String
importDotG' = fmap read . importDotG

As you can see the implementations are pretty trivial, so not sure it is worth it.

Haskell is weird. In any other language, feeding a string would be horrible - you would want to feed a reader, e.g. an open file. Unless there's something I'm missing here, it looks like importDotG would require to fully read the input file and then pass it.

Yes, due to laziness it is possible to get away with passing String's around as if they were streams.
It is possible to screw up though by accidentally adding a strict function into such pipeline. But I guess such a screw up is possible in a strict language too even when explicitly operating with streams.

it looks like importDotG would require to fully read the input file and then pass it.

Not necessarily. If your STG representation is a list of arcs, just as they are represented in the file, then importDotG will provide arcs one by one to the consumer.

@snowleopard the first two items are done, and there is an open issue about doc/comments already. I suggest we close this issue and tag as soon as first-release is completed.

@mvdan Agreed.

authors: mvdan snowleopard

repo: tuura/concepts


text:
🛑 Plex is down

In 7419325, Plex (http://plex.eighty-three.me:32400/identity) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Plex is back up in 7892954.

repo: tuxpeople/monitoring


text:
SwitchButton Size属性不传报错

组件
组件名称 SwitchButton
版本

组件版本： 4.5.2
react 版本：16.8.3
react-native 版本：0.59.10

概述
SwitchButton 组件没传入size值，页面崩溃
重现步骤

页面引入SwitchButton组件
进入页面
页面崩溃

Bug 行为
页面崩溃
期望行为
正常展示
期望发布日期
4.5.3
附件

@yefengxing 经过验证，不会出现崩溃现象，demo 可参考 https://github.com/tuya/tuya-panel-kit/blob/master/example/src/scenes/Switch/index.js

authors: ZengBeauty yefengxing

repo: tuya/tuya-panel-kit


text:
.NET MAUI sample app not compiled well on .NET 8

The linker step 'Registrar' failed during processing
1>C:\Program Files\dotnet\packs\Microsoft.iOS.Windows.Sdk\17.2.8004\tools\msbuild\iOS\Xamarin.iOS.Common.After.targets(364,3): error IL7000: An error occured while executing the custom linker steps. Please review the build log for more information.
1>C:\Program Files\dotnet\packs\Microsoft.iOS.Windows.Sdk\17.2.8004\tools\msbuild\iOS\Xamarin.iOS.Common.After.targets(364,3): error MT2362: The linker step 'Registrar' failed during processing: Object reference not set to an instance of an object.
1>C:\Program Files\dotnet\packs\Microsoft.iOS.Windows.Sdk\17.2.8004\tools\msbuild\iOS\Xamarin.iOS.Common.After.targets(406,3): error MSB3371: The file "obj\Debug\net8.0-ios\ios-arm64\linked\Link.semaphore" cannot be created. Could not find a part of the path 'dotnet-mapbox-quickstart\src\quickstart\DotnetMaui.MapboxQs\obj\Debug\net8.0-ios\ios-arm64\linked\Link.semaphore'.

https://github.com/xamarin/xamarin-macios/issues/20148

@tuyen-vuduc they automatically closed ticket. But from convesation I get this:

So for this particular xcframework you're binding, I would recommend building the binding project on macOS, and then consuming the NuGet from Windows.

So nuget package that we're consuming now was not build directly from Mac and that's case due symlinks and solution would be to recompile it under Mac and give a try again?
Do you think that I should be able to do it by self or it's something that you can verify?

@jmielczarkowski The libraries are supplied by Mapbox officially. I believe they are built on a Mac.
We will need to dig into further to check.

A snapshot of reported error.
/usr/local/share/dotnet/packs/Microsoft.iOS.Sdk/17.2.8053/targets/Xamarin.Shared.Sdk.targets(3,3): Error: clang++ exited with code 1:
Undefined symbols for architecture arm64:
  "_OBJC_CLASS_$_MBXExceptionHandler", referenced from:
      objc-class-ref in registrar.o
  "_OBJC_CLASS_$__TtC10MapboxMaps10CameraView", referenced from:
      objc-class-ref in registrar.o
  "_OBJC_CLASS_$__TtC10MapboxMaps14GestureHandler", referenced from:
      objc-class-ref in registrar.o
  "_OBJC_CLASS_$__TtC10MapboxMaps15AttributionView", referenced from:
      objc-class-ref in registrar.o
  "_OBJC_CLASS_$__TtC10MapboxMaps15CameraDebugView", referenced from:
      objc-class-ref in registrar.o
  "_OBJC_CLASS_$__TtC10MapboxMaps16PaddingDebugView", referenced from:
      objc-class-ref in registrar.o
  "_OBJC_CLASS_$__TtC10MapboxMaps17DistanceFormatter", referenced from:
      objc-class-ref in registrar.o
  "_OBJC_CLASS_$__TtC10MapboxMaps17PanGestureHandler", referenced from:
      objc-class-ref in registrar.o
  "_OBJC_CLASS_$__TtC10MapboxMaps17SizeTrackingLayer", referenced from:
      objc-class-ref in registrar.o
  "_OBJC_CLASS_$__TtC10MapboxMaps18InfoBu (DotnetIOS.MapboxQs)

authors: jmielczarkowski tuyen-vuduc

repo: tuyen-vuduc/dotnet-mapbox-quickstart


text:
🛑 Bimnext-DB is down

In f3600f6, Bimnext-DB (https://bimnextapiv3-dev.dpunity.com/v3/users/email/tuyencaovn%40gmail.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Bimnext-DB is back up in 2afa4c7 after 10 minutes.

repo: tuyencaovn/dpunitystatus


text:
🛑 KKK is down

In b806744, KKK (https://www.kkk.tsk.tr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: KKK is back up in 09cfa8d after 4 minutes.

repo: tuz-z/upp


text:
Fix doc build

Simple fix to get docs to build

Okay! I think the docs are actually fixed now, @binaryaaron


text:
Carousel ignoring borders

I've got a strange issue with Bootstrap 4.  My carousel seems to be ignoring the div borders to which its set in.   The orange border in the attached picture is the div in which the carousel is set.  It's completely ignoring that div.  I've even tried adding the 'img-fluid' class with no success.  Any ideas?

            <s:iterator value="%{#slideShow.images}" status="idx">
                <li data-target="#carousel-title" data-slide-to="<s:property value='%{#idx.index+1}'/>">

            </s:iterator>

                <img class="d-block w-100" src="<s:url value='/assets/home.png' />" alt="HSC" />

                    Hulmeville Soccer Club, Hulmeville, PA

            <s:iterator value="%{#slideShow.images}">

                    <img class="d-block w-100" src="<s:property value="src" />" />

                        <s:property value="caption" />

            </s:iterator>

Bug reports must include a live demo of the problem. Per our contributing guidelines, please create a reduced test case via JS Bin and report back with your link, Bootstrap version, and specific browser and OS details.

This is a saved reply.

Mark,
My apologies..
Here’s the JS Bin
https://jsbin.com/dixipeb/edit?html,css,output
Google Chrome is up to date
Version 67.0.3396.99 (Official Build) (64-bit)
Windows 10 Home with the latest patches, etc.
Thanks,
Scott
From: Mark Otto [mailto:notifications@github.com]
Sent: Wednesday, July 11, 2018 11:39 PM
To: twbs/bootstrap bootstrap@noreply.github.com
Cc: Scott Glass scott.glass@gmail.com; Author author@noreply.github.com
Subject: Re: [twbs/bootstrap] Carousel ignoring borders (#26858)
Bug reports must include a live demo of the problem. Per our contributing guidelines, please create a reduced test case via JS Bin https://jsbin.com  and report back with your link, Bootstrap version, and specific browser and OS details.

This is a saved reply.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/twbs/bootstrap/issues/26858#issuecomment-404379025 , or mute the thread https://github.com/notifications/unsubscribe-auth/ACKHHOlfYcsmyyvNaE0FgBEZcEbOyID6ks5uFsS5gaJpZM4VLbVq .  https://github.com/notifications/beacon/ACKHHEiF7F89kL_i-6-01Zglmv2dxLWdks5uFsS5gaJpZM4VLbVq.gif

@glassputan, every .col or .col-... class adds padding to the left and right, that's why the carousel isn't spread over the full width.
Also, you can better ask these questions on https://stackoverflow.com/, unless you really found a bug and can scope what's wrong.

authors: MartijnCuppens glassputan mdo

repo: twbs/bootstrap


text:
label.form-floating position is too far to the left in .row

Reproduction
<!DOCTYPE html>

    <meta charset="UTF-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>form-floating</title>

    <link href="https://cdn.jsdelivr.net/npm/bootstrap@5.0.1/dist/css/bootstrap.min.css" rel="stylesheet"
        integrity="sha384-+0n0xVW2eSR5OomGNYDnhzAbDsOXxcvSN1TPprVMTNDbiYZCxYbOOl7+AMvyTG2x" crossorigin="anonymous">

        <fieldset class="form-floating mb-3">
            <input type="email" class="form-control" id="floatingInput" placeholder="name@example.com">
            Email address
        </fieldset>
        <fieldset class="form-floating">
            <input type="password" class="form-control" id="floatingPassword" placeholder="Password">
            Password
        </fieldset>

results in:

(^this is good! exactly as expected)
however:
<!DOCTYPE html>

    <meta charset="UTF-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>form-floating</title>

    <link href="https://cdn.jsdelivr.net/npm/bootstrap@5.0.1/dist/css/bootstrap.min.css" rel="stylesheet"
        integrity="sha384-+0n0xVW2eSR5OomGNYDnhzAbDsOXxcvSN1TPprVMTNDbiYZCxYbOOl7+AMvyTG2x" crossorigin="anonymous">

        <fieldset class="form-floating mb-3">
            <input type="email" class="form-control" id="floatingInput" placeholder="name@example.com">
            Email address
        </fieldset>
        <fieldset class="form-floating">
            <input type="password" class="form-control" id="floatingPassword" placeholder="Password">
            Password
        </fieldset>

results in:
 (I added .row in this version)
Notice how in the second img, the label is too far to the left because .row adds padding-left and padding-right
Workaround
manually increase padding-right on the label
Environment

macOS 11.5 Beta (20G5023d)
Chrome 91.0.4472.77

Duplicate of #33040


text:
Low contrast of table-striped rows in dark mode

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
Example can be seen in the Bootstrap docs. In light mode the striping of the table rows is quite clearly visible but in dark mode the difference is very subtle

Reduced test cases

      #
      First

      1
      Mark

      2
      Jacob

      3
      Larry the Bird

      #
      First

      1
      Mark

      2
      Jacob

      3
      Larry the Bird

What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Firefox
What version of Bootstrap are you using?
5.3.0-alpha3

I just saw Heads up! Because of the more complicated CSS used to generate our table variants, they most likely won’t see color mode adaptive styling until v6.. I missed that yesterday. Sorry for the noise.


text:
Add prefix to footer.html search.json

Add prefix {{ site.baseurl }} to footer.html search.json

Thanks.

authors: cvrebert xcatliu


text:
Docs: clarify rationale for button group on links

clarify that putting links in a button group is, in essence, an alternative to using the navigation component (and cross-reference it)
remove the non-sequitur about using .active...that's irrelevant here, as it's already mentioned in the docs page for .btn. otherwise, this would then also need the whole extra explanation about conveying meaning with aria-current etc, which is already covered in ample detail in the navs page

@patrickhlauke this needs to be backported manually, I don't even know if we have those snippets in v4-dev.

This doesn't seem to apply to v4-dev. If you still think it does, re-add it in the v4-next project and make a PR against v4-dev.

ah you're right, could have sworn v4 also had a link button group example, but i must have dreamt it

authors: XhmikosR patrickhlauke