Separate logic to follow references from TaskRun resource validation

In the TaskRun reconciler, there were several different places where logic exists to retrieve references Tasks and Resources; now we use a library that allows us to retrieve these references up front and use them instead of using Listers everywhere.
We now use the resolved TaskRun when validating the TaskRun, so we no longer need access to the reconciler or to do any listing when validating the TaskRun.
This is a step along the way to #213. Next we can do a similar refactoring to the PipelineRun validation. (The goal is that we can share the validation logic, since it's looking at the same thing just the structure of the input objects is different.) We'll probably also separate the param validation out from the resource validation.
The current validation will miss the case where extra resources or parameters that aren't needed are supplied (this was the case already).

/lgtm


creating vehicle audi failed

Describe the bug
Nach dem Update auf 0.131.5 (nightly zwecks Fehlersuche ebenfalls) erhalte ich beim initialisieren meines Fahrzeuges folgende error message:
[main ] ERROR 2024/11/14 20:08:25 creating vehicle audi failed: cannot create vehicle type 'template': cannot create vehicle type 'etron': cannot get vehicles: Message: Post "https://app-api.live-my.audi.com/vgql/v1/graphql": dial tcp: lookup app-api.live-my.audi.com: i/o timeout, Locations: [], Extensions: map[code:request_error], Path: []
bzw. in nightly:
[main ] ERROR 2024/11/14 20:22:11 creating vehicle audi failed: cannot create vehicle type 'template': cannot create vehicle type 'etron': Get "https://identity.vwgroup.io/oidc/v1/authorize?client_id=f4d0934f-32bf-4ce4-b3c4-699a7049ad26%40apps_vw-dilab_com&code_challenge=JWjPg1lbSLahj9lzvf3UmKePROEvrLHBHaH3ZQJemNw&code_challenge_method=S256&prompt=login&redirect_uri=myaudi%3A%2F%2F%2F&response_type=code+id_token+token&scope=openid+profile+mbb&ui_locales=de-DE&nonce=aFxkhgTyEyuCrswklvWoIjrwowwKGdrbcGBrgUfCDnV&state=303b9690-2401-45bd-a026-c9416e094563": dial tcp: lookup identity.vwgroup.io: i/o timeout
Bestätigen von Terms&Conditions ist in der App nicht angeboten.
Steps to reproduce

Audi inkl. credentials anlegen
Applikation starten
Logs prüfen

Configuration details
network:
  # schema is the HTTP schema
  # setting to `https` does not enable https, it only changes the way URLs are generated
  schema: http
  # host is the hostname or IP address
  # if the host name contains a `.local` suffix, the name will be announced on MDNS
  # docker: MDNS announcements don't work. host must be set to the docker host's name.
  host: <IP_ADDRESS>
  # port is the listening port for UI and api
  # evcc will listen on all available interfaces
  port: 7070

interval: 30s # control cycle interval. Interval <30s can lead to unexpected behavior, see https://docs.evcc.io/docs/reference/configuration/interval

# database configuration for persisting charge sessions and settings
# database:
#   type: sqlite
#   dsn: <path-to-db-file>

sponsortoken: ***

# telemetry enables aggregated statistics

plant: ***

#
# Telemetry allows collecting usage data (grid and green energy, charge power).
# Data is aggregated, no individual charging sessions are tracked. The collected,
# anonymous data can be retrieved using https://api.evcc.io.
#
# See https://github.com/evcc-io/evcc/pull/4343 or details.
#
# For time being, this is only available to sponsors, hence data is associated with
# the sponsor token's identity.
#
# telemetry: true

# log settings
log: info
levels:
  site: debug
  lp-1: debug
  lp-2: debug
  cache: error
  db: error

# modbus proxy for allowing external programs to reuse the evcc modbus connection
# each entry will start a proxy instance at the given port speaking Modbus TCP and
# relaying to the given modbus downstream device (either TCP or RTU, RS485 or TCP)
#modbusproxy:
#  #  - port: 5200
#  #    uri: solar-edge:502
#  #    # rtu: true
#  #    # readonly: true # use `deny` to raise modbus errors

# meter definitions
# name can be freely chosen and is used as reference when assigning meters to site and loadpoints
# for documentation see https://docs.evcc.io/docs/devices/meters
meters:
  - name: shelly
    type: template
    template: shelly-3em
    usage: pv
    host: <IP_ADDRESS>
#  - name: pv
#    type: ...
#  - name: battery
#    type: ...
#  - name: charge
#    type: ...
#  - name: aux
#    type: ...

# charger definitions
# name can be freely chosen and is used as reference when assigning charger to vehicle
# for documentation see https://docs.evcc.io/docs/devices/chargers
chargers:
  - name: Go-e
    type: template
    template: go-e-v3
    host: ***
#    status: A # optional
#    power: 0 # optional
#    enabled: true # optional

# vehicle definitions
# name can be freely chosen and is used as reference when assigning vehicle to loadpoint
# for documentation see https://docs.evcc.io/docs/devices/vehicles
vehicles:
  - name: audi
    type: template
    template: audi
    title: Audi Q4 e-tron
    capacity: 77 # kWh
    user: *** # user
    password: *** # password
    vin: ***
#    onIdentify: # set defaults when vehicle is identified
#      mode: pv # enable PV-charging when vehicle is identified

# site describes the EVU connection, PV and home battery
site:
  title: Home # display name for UI
  meters:
#   grid: shelly # grid meter
   pv: shelly
#    battery:
#      - battery # list of battery meters
#    aux:
#      - aux # list of auxiliary meters for adjusting grid operating point
  residualPower: # additional household usage margin
  maxGridSupplyWhileBatteryCharging: 0 # ignore battery charging if AC consumption is above this value

# loadpoint describes the charger, charge meter and connected vehicle
loadpoints:
  - title: Garage # display name for UI
    charger: Go-e # charger
#    meter: charge # external charge meter (if charger has no meter included). NOT grid or pv meter.
#    mode: "off" # default charge mode to apply when vehicle is disconnected; use "off" to disable by default if charger is publicly available

    # remaining settings are experts-only and best left at default values
    priority: 0 # relative priority for concurrent charging in PV mode with multiple loadpoints (higher values have higher priority)
    soc:
      # polling defines usage of the vehicle APIs
      # Modifying the default settings it NOT recommended. It MAY deplete your vehicle's battery
      # or lead to vehicle manufacturer banning you from API use. USE AT YOUR OWN RISK.
      poll:
        # poll mode defines under which condition the vehicle API is called:
        #   charging: update vehicle ONLY when charging (this is the recommended default)
        #   connected: update vehicle when connected (not only charging), interval defines how often
        #   always: always update vehicle regardless of connection state, interval defines how often (only supported for single vehicle)
        mode: charging
        # poll interval defines how often the vehicle API may be polled if NOT charging
        interval: 60m
      estimate: true # set false to disable interpolating between api updates (not recommended)
    enable: # pv mode enable behavior
      delay: 1m # threshold must be exceeded for this long
      threshold: 0 # grid power threshold (in Watts, negative=export). If zero, export must exceed minimum charge power to enable
    disable: # pv mode disable behavior
      delay: 3m # threshold must be exceeded for this long
      threshold: 0 # maximum import power (W)

# tariffs are the fixed or variable tariffs
tariffs:
  currency: EUR # three letter ISO-4217 currency code (default EUR)
  grid:
    # either static grid price (or price zones)
    type: fixed
    price: 0.2863 # EUR/kWh
#    zones:
#      - days: Mon-Fri
#        hours: 2-5
#        price: 0.2 # EUR/kWh
#      - days: Sat,Sun
#        price: 0.15 # EUR/kWh

    # or variable tariffs
    # type: tibber
    # token: "476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4" # access token
    # homeid: "cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c" # optional if multiple homes associated to account

    # type: awattar
    # region: de # optional, choose at for Austria
    # charges: # optional, additional charges per kWh
    # tax: # optional, additional tax (0.1 for 10%)

    # type: octopusenergy
    # tariff: AGILE-FLEX-22-11-25 # Tariff code
    # region: A # optional

    # type: elering # Nordpool
    # region: ee # or lt, lv, fi
    # charges: # optional, additional charges per kWh
    # tax: # optional, additional tax (0.1 for 10%)

    # type: energinet # Energinet using the price in DKK
    # region: dk1 # or dk2
    # charges: # optional, additional charges per kWh
    # tax: # optional, additional tax (0.1 for 10%)

    # type: entsoe # Entso-E european market data
    # domain: BZN|DE-LU # https://transparency.entsoe.eu/content/static_content/Static%20content/web%20api/Guide.html#_areas
    # securitytoken: # api token
    # charges: # optional, additional charges per kWh
    # tax: # optional, additional tax (0.1 for 10%)

    # type: pun # PUN - Prezzo unico nazionale - Hourly Italian wholesale prices
    # charges: 0 # optional, additional charges per kWh
    # tax: 0 # optional, additional tax (0.1 for 10%)

    # type: amber
    # token: # api token from https://app.amber.com.au/developers/
    # siteid: # site ID returned by the API
    # channel: general

    # type: custom # price from a plugin source; see https://docs.evcc.io/docs/reference/plugins
    # price:
    #   source: http
    #   uri: https://example.org/price.json
    #   jq: .price.current

  feedin:
    # rate for feeding excess (pv) energy to the grid
    type: fixed
    price: 0.1231 # EUR/kWh

    # type: octopusenergy
    # tariff: AGILE-FLEX-22-11-25 # Tariff code
    # region: A # optional

    # type: amber
    # token: # api token from https://app.amber.com.au/developers/
    # siteid: # site ID returned by the API
    # channel: feedIn
  co2:
    # co2 tariff provides co2 intensity forecast and is for co2-optimized target charging if no variable grid tariff is specified
     type: grünstromindex # GrünStromIndex (Germany only)
     zip: ***

    # type: electricitymaps # https://app.electricitymaps.com/map
    # uri: <uri>
    # token: <token> # needs to be a token with forecast (not in the free tier)
    # zone: DE

    # type: ngeso # National Grid Electricity System Operator data (Great Britain only) https://carbonintensity.org.uk/
    # provides national data if both region and postcode are omitted - Choose ONE only!
    # region: 1 # optional, coarser than using a postcode - The region details are at https://carbon-intensity.github.io/api-definitions/#region-list
    # postcode: SW1 # optional - Outward postcode i.e. RG41 or SW1 or TF8. Do not include full postcode, outward postcode only

# mqtt message broker
mqtt:
  # broker: localhost:1883
  # topic: evcc # root topic for publishing, set empty to disable
  # user:
  # password:

# influx database
influx:
  # url: http://localhost:8086
  # database: evcc
  # user:
  # password:

# eebus credentials
eebus:
  # uri: # :4712
  # interfaces: # limit eebus to specific network interfaces
  # - en0
  # certificate: # local signed certificate, required, can be generated via `evcc eebus-cert`
  #   public: # public key
  #   private: # private key

# push messages
messaging:
  events:
    start: # charge start event
      title: Charge started
      msg: Started charging in "${mode}" mode
    stop: # charge stop event
      title: Charge finished
      msg: Finished charging ${chargedEnergy:%.1fk}kWh in ${chargeDuration}.
    connect: # vehicle connect event
      title: Car connected
      msg: "Car connected at ${pvPower:%.1fk}kW PV"
    disconnect: # vehicle connected event
      title: Car disconnected
      msg: Car disconnected after ${connectedDuration}
    soc: # vehicle soc update event
      title: Soc updated
      msg: Battery charged to ${vehicleSoc:%.0f}%
    guest: # vehicle could not be identified
      title: Unknown vehicle
      msg: Unknown vehicle, guest connected?
  services:
  # - type: pushover
  #   app: # app id
  #   recipients:
  #   - # list of recipient ids
  # - type: telegram
  #   token: # bot id
  #   chats:
  #   - # list of chat ids
  # - type: email
  #   uri: smtp://<user>:<password>@<host>:<port>/?fromAddress=<from>&toAddresses=<to>
  # - type: ntfy
  #   uri: https://<host>/<topics>
  #   priority: <priority>
  #   tags: <tags>

Log details
[main ] INFO 2024/11/14 20:21:59 evcc 0.131.5 (6836749c)
[main ] INFO 2024/11/14 20:21:59 using config file: /etc/evcc.yaml
[db ] INFO 2024/11/14 20:21:59 using sqlite database: /root/.evcc/evcc.db
[main ] INFO 2024/11/14 20:22:06 listening at :7070
[main ] ERROR 2024/11/14 20:22:11 creating vehicle audi failed: cannot create vehicle type 'template': cannot create vehicle type 'etron': Get "https://identity.vwgroup.io/oidc/v1/authorize?client_id=f4d0934f-32bf-4ce4-b3c4-699a7049ad26%40apps_vw-dilab_com&code_challenge=JWjPg1lbSLahj9lzvf3UmKePROEvrLHBHaH3ZQJemNw&code_challenge_method=S256&prompt=login&redirect_uri=myaudi%3A%2F%2F%2F&response_type=code+id_token+token&scope=openid+profile+mbb&ui_locales=de-DE&nonce=aFxkhgTyEyuCrswklvWoIjrwowwKGdrbcGBrgUfCDnV&state=303b9690-2401-45bd-a026-c9416e094563": dial tcp: lookup identity.vwgroup.io: i/o timeout
[lp-1 ] DEBUG 2024/11/14 20:22:18 charge total import: 324.056kWh
[site ] INFO 2024/11/14 20:22:18 site config:
[site ] INFO 2024/11/14 20:22:18 meters: grid ✗ pv ✓ battery ✗
[site ] INFO 2024/11/14 20:22:18 pv 1: power ✓ energy ✓ currents ✓
[site ] INFO 2024/11/14 20:22:18 vehicles:
[site ] INFO 2024/11/14 20:22:18 vehicle 1: range ✗ finish ✗ status ✗ climate ✗ wakeup ✗
[lp-1 ] INFO 2024/11/14 20:22:18 loadpoint 1:
[lp-1 ] INFO 2024/11/14 20:22:18 mode: off
[lp-1 ] INFO 2024/11/14 20:22:18 charger: power ✓ energy ✓ currents ✓ phases ✓ wakeup ✗
[lp-1 ] INFO 2024/11/14 20:22:18 meters: charge ✓
[lp-1 ] INFO 2024/11/14 20:22:18 charge: power ✓ energy ✓ currents ✓
[lp-1 ] DEBUG 2024/11/14 20:22:18 phase timer inactive
[lp-1 ] DEBUG 2024/11/14 20:22:18 pv timer inactive
[site ] DEBUG 2024/11/14 20:22:18 ----
[lp-1 ] DEBUG 2024/11/14 20:22:18 charge power: 0W
[lp-1 ] DEBUG 2024/11/14 20:22:18 charge currents: [0 0 0]A
[site ] DEBUG 2024/11/14 20:22:18 pv power: 0W
[site ] DEBUG 2024/11/14 20:22:18 site power: 0W
[lp-1 ] DEBUG 2024/11/14 20:22:18 charge total import: 324.056kWh
[lp-1 ] DEBUG 2024/11/14 20:22:18 charger status: B
[lp-1 ] DEBUG 2024/11/14 20:22:18 charge start energy: 324.056kWh
[lp-1 ] INFO 2024/11/14 20:22:18 car connected
[lp-1 ] DEBUG 2024/11/14 20:22:18 vehicle api refresh
[lp-1 ] DEBUG 2024/11/14 20:22:18 pv timer elapse
[lp-1 ] DEBUG 2024/11/14 20:22:18 pv timer inactive
[lp-1 ] DEBUG 2024/11/14 20:22:18 charge total import: 324.056kWh
[lp-1 ] DEBUG 2024/11/14 20:22:18 !! pvScalePhases DOWN activePhases: 3, available power: 0W, scalable: true
[lp-1 ] DEBUG 2024/11/14 20:22:18 available power 0W < 4140W min 3p threshold
[lp-1 ] DEBUG 2024/11/14 20:22:18 phase scale1p in 0s
[lp-1 ] DEBUG 2024/11/14 20:22:18 switched phases: 1p
[lp-1 ] DEBUG 2024/11/14 20:22:18 phase timer inactive
[lp-1 ] DEBUG 2024/11/14 20:22:18 pv charge current: 0A = 0A + -0A (0W @ 1p)
[lp-1 ] DEBUG 2024/11/14 20:22:18 pv enable timer reset
[lp-1 ] DEBUG 2024/11/14 20:22:18 pv timer inactive
[lp-1 ] INFO 2024/11/14 20:22:40 vehicle updated: unknown -> Audi Q4 e-tron
[site ] DEBUG 2024/11/14 20:22:48 ----
[lp-1 ] DEBUG 2024/11/14 20:22:48 charge power: 0W
[lp-1 ] DEBUG 2024/11/14 20:22:48 charge currents: [0 0 0]A
[site ] DEBUG 2024/11/14 20:22:48 pv power: 0W
[site ] DEBUG 2024/11/14 20:22:48 site power: 0W
[lp-1 ] DEBUG 2024/11/14 20:22:48 charge total import: 324.056kWh
[lp-1 ] DEBUG 2024/11/14 20:22:48 charger status: B
[lp-1 ] DEBUG 2024/11/14 20:22:48 switched phases: 3p
[lp-1 ] DEBUG 2024/11/14 20:22:48 max charge current: 16A
[lp-1 ] DEBUG 2024/11/14 20:22:48 charger enable
[lp-1 ] DEBUG 2024/11/14 20:22:48 wake-up timer: start
[lp-1 ] DEBUG 2024/11/14 20:22:48 pv timer elapse
[lp-1 ] DEBUG 2024/11/14 20:22:48 pv timer inactive
[site ] DEBUG 2024/11/14 20:23:18 ----
[lp-1 ] DEBUG 2024/11/14 20:23:18 charge power: 3211W
[lp-1 ] DEBUG 2024/11/14 20:23:18 charge currents: [4.94 5.02 5.02]A
[site ] DEBUG 2024/11/14 20:23:18 pv power: 0W
[site ] DEBUG 2024/11/14 20:23:18 site power: 3211W
[lp-1 ] DEBUG 2024/11/14 20:23:18 charge total import: 324.070kWh
[lp-1 ] DEBUG 2024/11/14 20:23:18 charger status: C
[lp-1 ] DEBUG 2024/11/14 20:23:18 charge start energy: 324.070kWh
[lp-1 ] INFO 2024/11/14 20:23:18 start charging ->
[lp-1 ] DEBUG 2024/11/14 20:23:18 wake-up timer: stop
[site ] ERROR 2024/11/14 20:23:24 telemetry: upload failed: Post "https://api.evcc.io/v1/charge": context deadline exceeded

What type of operating system are you running?
Docker container
Nightly build

[X] I have verified that the issue is reproducible with the latest nightly build

Version
evcc version 0.131.5 (6836749c)

Hat sich nach  langem probieren und nach dem erstellen des Bugs von selbst gelöst :-O


How do it show me the build time

help me ,please!
when i use 'npm run start',it tall me 'Compiled successfully!'.
but It didn't tell me how long it took,and create those files？
i want to get it,What should I do？

Hey @liuzhiyang0113,
I don't think we show build times for the development builds, but you get build times when running the actual production builds with npm build.

But I need to optimize the packing time，Is there any way to know？

How long it takes to package the development build is irrelevant, it'll take a little while because it has to bundle a load of things, the live reload, the fancy error page, and a few other things it needs. Once you've ran yarn build, it will be a minimal build of the codebase. Could you elaborate on why you'd like to know the build time other than needing to optimise the packaging time please?

Are you running on macOS or Linux? You can prefix the command with time npm run build.
Alternatively, you can add Yarn and it will tell you the build time at the end.


Cannot read properties of undefined (reading 'startLine')

Description
While using WebC in 11ty with<EMAIL_ADDRESS>you get a TypeError that prevents 11ty from writing pages if your WebC layout/page has a tag that is a void element or self closing.
I could not get this error to reproduce in the WebC test repository but I believe this can be confirmed by checking how Parse5 parses void elements - prepared snippet in the Parse5 playground.
You can see in the snippet if you expand the sourceCodeLocation of the meta tag that it does not contain an endTag object. This means that let end = node.sourceCodeLocation.endTag; will be undefined in those cases - resulting in end.startLine producing the error below.
Debug Output
[11ty] Problem writing Eleventy templates: (more in DEBUG output)
[11ty] 1. Having trouble writing to "_site/test/index.html" from "./src/test.webc" (via EleventyTemplateError)
[11ty] 2. Cannot read properties of undefined (reading 'startLine') (via TypeError)
[11ty]
[11ty] Original error stack trace: TypeError: Cannot read properties of undefined (reading 'startLine')
[11ty]     at AstSerializer.getPreparsedRawTextContent (file:///C:/Users/andyb/Documents/Projects/andy.bond/node_modules/@11ty/webc/src/ast.js:1150:28)
[11ty]     at AstSerializer.transformContent (file:///C:/Users/andyb/Documents/Projects/andy.bond/node_modules/@11ty/webc/src/ast.js:778:29)
[11ty]     at AstSerializer.compileNode (file:///C:/Users/andyb/Documents/Projects/andy.bond/node_modules/@11ty/webc/src/ast.js:1199:20)
[11ty]     at AstSerializer.getChildContent (file:///C:/Users/andyb/Documents/Projects/andy.bond/node_modules/@11ty/webc/src/ast.js:635:40)
[11ty]     at AstSerializer.compileNode (file:///C:/Users/andyb/Documents/Projects/andy.bond/node_modules/@11ty/webc/src/ast.js:1319:46)
[11ty]     at processTicksAndRejections (node:internal/process/task_queues:96:5)
[11ty]     at async AstSerializer.getChildContent (file:///C:/Users/andyb/Documents/Projects/andy.bond/node_modules/@11ty/webc/src/ast.js:635:29)
[11ty]     at async AstSerializer.compileNode (file:///C:/Users/andyb/Documents/Projects/andy.bond/node_modules/@11ty/webc/src/ast.js:1358:36)
[11ty]     at async AstSerializer.getChildContent (file:///C:/Users/andyb/Documents/Projects/andy.bond/node_modules/@11ty/webc/src/ast.js:635:29)
[11ty]     at async AstSerializer.compileNode (file:///C:/Users/andyb/Documents/Projects/andy.bond/node_modules/@11ty/webc/src/ast.js:1358:36)

Can you provide the full <meta> element input you’re parsing? I’m guessing this only applies when webc:raw is in play

Just to be clear, this test passes fine with WebC 0.6:
test("Using webc:raw on void elements #67", async t => {
	let component = new WebC();

	component.setContent(`<!DOCTYPE html>

	<meta name="viewport" content="width=device-width, initial-scale=1.0" />

My First Heading

My first paragraph.

`);

	let { html } = await component.compile();

	t.is(html, `<!doctype html>

	<meta name="viewport" content="width=device-width, initial-scale=1.0">

My First Heading

My first paragraph.

`);
});

so I’m trying to figure out how to make it fail!

Here is where I get the error - made a very small project to test this with.
_layouts/base.webc
<!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" />
    <meta name="generator" :content="eleventy.generator" />

    <meta webc:is="meta-social" />

    <template webc:nokeep @html="content"></template>

index.webc
---
layout: base
title: Test
---

Test

_components/head/meta-social.webc

What's interesting is that this doesn't occur if I swap <meta webc:is="meta-social" /> for <meta webc:is="meta-favicons" />
_components/head/meta-favicons.webc
<link
  rel="apple-touch-icon"
  sizes="180x180"
  :href="url('/static/favicon/apple-touch-icon.png')"
/>
<link
  rel="icon"
  type="image/png"
  sizes="32x32"
  :href="url('/static/favicon/favicon-32x32.png')"
/>
<link
  rel="icon"
  type="image/png"
  sizes="16x16"
  :href="url('/static/favicon/favicon-16x16.png')"
/>
<link rel="manifest" :href="url('/static/favicon/site.webmanifest')" />
<meta name="apple-mobile-web-app-title" :content="this.metadata.name" />
<meta name="application-name" :content="this.metadata.name" />
<meta name="msapplication-TileColor" content="#15273d" />
<meta name="theme-color" content="#0d1b2a" />

Regression from #61

Shipping with v0.6.2, appreciate you!
I took a bit different approach from your PR—you can have a look here https://github.com/11ty/webc/commit/5a8224d0a8c0ff5f3409b46d6e876b0f5bff906f

https://github.com/11ty/webc/releases/tag/v0.6.2 is out!


MediaStream support?

I was wondering what the current state/progress is with MediaStream support? I'd like to help implement this if possible, primarily for voice chat, and would appreciate some pointers.

Came here also after starting to do some research on implementing voice chat in Godot. Sounds like WebRTCMediaSteamTrack would be a great addition, I created a proposal as you suggested @Faless
https://github.com/godotengine/godot-proposals/issues/813

Without a plain to support MediaStream, what's the purpose of implementing WebRTC in Godot?

My company would be happy to sponsor some work on this. We are offering $1500 bounty for this feature, https://gitcoin.co/issue/29615#
We will be putting up some other bounties for other video chat features in Godot. Feel free to get with if you want to get paid to build this out<EMAIL_ADDRESS>


Minier Doge coin

Hi Goodmorning,
I want to understand why, the payment remains pending and is not inserted in the available salfo to be able to download it in my Wallet, am I wrong?
thank you very much for your attention
sAx
-->

Pending balance must reach the payout threshold on Zergpool.  Click 'View payout information' to see the amount.


Can we have the same background color for all the IDE?

I really like this theme, but i feel like I'd like it more if we had the same background color for all the IDE, like in the explorer etc.

Hi! Could you please explain what you mean? It's somewhat similar.

Hi,
Idk if it's possible to use the same blue-ish background color in the whole IDE instead of just behind the code, but I'd really like that. ^^

You can change the source control editor background in settings: Editor / Color Scheme / General / Text / Default Text / Background.
Apart from this, other colors are similar to each other, I don't think they should be exactly the same. You probably need another theme for this change, it should be easy to fork and change them.


Add a tip for a way to run tests within a Python interpretor

Codecov Report

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

@@            Coverage Diff             @@
##           master     #630      +/-   ##
==========================================
- Coverage   92.93%   90.28%   -2.66%
==========================================
  Files          31       31
  Lines        5053     5053
==========================================
- Hits         4696     4562     -134
- Misses        357      491     +134

Impacted Files
Coverage Δ

databricks/koalas/usage_logging/__init__.py
23.14% <0%> (-74.08%)
:arrow_down:

databricks/koalas/usage_logging/usage_logger.py
50% <0%> (-50%)
:arrow_down:

databricks/koalas/__init__.py
76.31% <0%> (-7.9%)
:arrow_down:

databricks/conftest.py
90.69% <0%> (-6.98%)
:arrow_down:

databricks/koalas/utils.py
97.43% <0%> (-2.57%)
:arrow_down:

databricks/koalas/frame.py
92.81% <0%> (-1.88%)
:arrow_down:

databricks/koalas/namespace.py
87.6% <0%> (-1.61%)
:arrow_down:

databricks/koalas/plot.py
92.51% <0%> (-1.58%)
:arrow_down:

databricks/koalas/internal.py
98.63% <0%> (-0.69%)
:arrow_down:

databricks/koalas/testing/utils.py
77.35% <0%> (-0.63%)
:arrow_down:

... and 1 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 37e783c...82266d8. Read the comment docs.

Thanks! merging.


Remove duplicated imports

Proposed changes:

Remove unnecessary server imports from core/run.py
Resolves issue #7009

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[X] updated the changelog (please check changelog for instructions)
[X] reformat files using black (please check Readme for instructions)

Thanks for submitting a pull request 🚀 @Ghostvv will take a look at it as soon as possible ✨


Able to run this command from a workstation

The documentation states "This cmdlet normally can be run on the affected Mailbox server only. An exception is that this cmdlet can be run on an administrator's workstation when using the ConfigurationOnly parameter with a value of $true." However, I was able to run the command and successfully move a mailbox database multiple times from the Exchange Management shell on my Windows 10 workstation.
I'm running Exchange Server 2019 CU2

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: aaaf61e7-5bf9-d72e-69fe-f1679ff5fc8c
Version Independent ID: 06dfb699-6733-97ff-a7a7-4323bd16f3b7
Content: Move-DatabasePath (exchange)
Content Source: exchange/exchange-ps/exchange/mailbox-databases-and-servers/Move-DatabasePath.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@officedocsbot assign @yogkumgit

Any update?

Hi @chrisda,
Could you help with this? I think it could work in Exch 2016/19 (even 2013) but not in Exchange 2010. What do you think?
Thanks!

That sounds reasonable to me.

It appears the documentation needs some updating.

@chrisda Please merge this PR #3940

@dariomws306  Thank you very much for the contribution and updating the documentation with PR. @chairborne33 Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


F-lock  menu seems broken

After latest Commits .. When I set F-lock to unlock all    it always defaults  too 144-148    420-450 or what ever else may have been chosen to check, .... It used to work ok on previous builds....
TX does still work on all  just the Menus does not show the actual change to the setting..

This is on purpose. It didn't used to work on previous builds because it wasn't there. TX doesn't work on all, does it TX on 80MHz or 1200MHz?
Before I make a release I'll add necessary manual to the wiki.

There was never "unlock all(or similar".
I changed some names long time ago, and did some modifications now, that is it.
It certainly won't TX on 84-86mh
It also didn't work on any previous builds.

I already made myself clear.

What is the F Lock set on?

Are you a sane person?
What did I tell you? This is on purpose, before I make a release I'll add necessary manual to the wiki.
You said that you can transmit on 84-86mhz, regardless.
I asked what is the F Lock set on.

I explained to you everything as clear as I could, but you decided to be a smartass, just like the last time.
I know you will find some excuse, so let's not continue this conversation. I'm fine with you not rising any issues again.


The command: operator-sdk generate crds does not support kubectl explain?

Feature Request
Is your feature request related to a problem? Please describe.
Due to some product requirement, I would like to enable the kubectl explain command for my CRDs. It can be done by adding preserveUnknownFields: false key in the CRD definitions.
However, this feature will be overwritten when running operator-sdk generate crds.
Describe the solution you'd like
I am not sure if there are commands/scripts or tools in operator-sdk that I can leverage to enable this kubectl explain feature.
Thanks a lot !

You can set preserveUnknownFields using the field-level +kubebuilder:pruning:PreserveUnknownFields. The docs say this cannot be set to false, but that may not be the case for v1 CRDs since controller-gen allows that top-level field to be false.

Thank you for the answer.
I will close this issue.


Database Provider change to support Heroku

Motivation:
Allow Heroku to Build and Deploy the API while connecting to a PSQL DB
Changes:

Added Procfile that runs npm run start:prod
Added heroku-postbuild step to run nest build
Updated database.provider.ts to allow either a DATABASE_URL (like heroku uses) or the normal dev .env file

Apologies in advance for stacking all the changes from master back onto this :(


Is this app abandoned?

Just curious

@hohommx2015 it doesn't seem to be.

@hohommx2015 it doesn't seem to be.

I hope so,but the dev isn't active for almost 3 months now

Sorry for the waiting, in this period I was unable to continue updating the app.
Now the problem is fixed so I will restart to updating it.

Nice to hear it


"Sfințești" is listed in the drop-down menu

Description:
"Sfințești" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Sfințești" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Sfințești, TELEORMAN (Sfințești)" and "Comuna Sfințești, TELEORMAN".


Missing Code for latest versions on google-play

This repo last commit is from "Feb 4, 2021" and contain only 5 commits and 1 tag for version 1.0,0 while android app with appid "com.pundix.functionx":
https://play.google.com/store/apps/details?id=com.pundix.functionx
last updated in: "August 9, 2021" with version: 1.7.2 and according to appbrain had several version before that:
https://www.appbrain.com/app/fxwallet-by-pundi-x-labs/com.pundix.functionx
Please publish the source code for the latest version and older versions that was uploaded to google-play in this repo.

@0xCarlRock Any Update regarding publishing the source code? the version in google-play is: 1.13.0 from "December 10, 2021" while this repo last commit is still from "Feb 4, 2021"


Capturing primary vs. conditional signals in reported results (OTG)

Following up from the feedback on OTG functionalities provided by BMS on 8-6-22.
As a user, I need to be able to gather info on whether a reported SNP/trait association is coming from a primary or conditional analysis - these tags are important for downstream analyses/customised pipelines.
This info should be visualised on the study and gene prioritisation pages.
Tasks
STUDY PAGE

[ ] Adding a new column in the associations' table, populated with different shapes to report primary and secondary signals (see one option below). In the example below, two lead variants mapping very close to each other are shown in curly bracket - which one is the primary? Which one is the secondary signal?

Screenshot from GCST002221
![Screenshot 2022-07-06 at 12.41.18.png]
(https://images.zenhubusercontent.com/5ef1da283f096f8317c9ca44/71a98f0d-0099-4464-b106-94c25944c6f7
GENE PRIORITISATION PAGE:

[ ] Adding variant signal info to the Association Summary (at a variant level) see option below:

[ ] Additional Action Item for @bruno-ariano: to investigate where to extract this info in investigate where to extract this info  in GCTA-cojo and to look at the locus-zoom like regional plot / FinnGen regional plot for benchmarking.

Acceptance tests
How do we know the task is complete?

When data and visualisations are successfully deployed for the users.

Hi I have found a nice example describing a secondary signal:
This involve the study GCST002221.  In this study there is a leading variant 19_44919689_A_G which is close to another leading variant named 19_44912678_G_T.
If we click on the variant summary page of the first variant (https://genetics.opentargets.org/variant/19_44919689_A_G) we see the second one(19_44912678_G_T) is tagging the primary one for the GCST002221 study. This is an example of secondary signal
Given that we must have the credible set information stored of the leading and tagging variants (respectively 19_44919689_A_G and 19_44912678_G_T ) for the study GCST002221.
The credible set file store also the conditional p-value information for 19_44912678_G_T given the leading variant (19_44919689_A_G) which we should add to the page

@JarrodBaker could you please take a look at Bruno's example and let us know if it is indeed a good use-case to progress with this task?

I'll get to it as soon as I can.

To add to the feature request document

feature added to partners feedback doc

feature added to partners feedback doc


Adding external agents to Hreoku deployment

I have deployed Huginn using the Deploy to Heroku button. I have also created an external agent. In the local environment, I can simply add, ADDITIONAL_GEMS=huginn_price_agent(git: https://github.com/nevilleomangi/huginn_price_agent.git) to the .env file to add the agent, and it works as expected.
How can I add the agent to the Heroku setup?
What I have tried
Setting the environment variable ADDITIONAL_GEMS in the Heroku settings panel. The app crashed.

I solved the issue by cloning the Heroku repo, updating the gem file with a Github source, then pushing both the Gemfile and Gemfile.lock (after bundle install) to Heroku.


Cannot bind argument to parameter 'Path' because it is null.

I'm getting this error in upgrade-npm.ps1
Cannot bind argument to parameter 'Path' because it is null.
 + CategoryInfo          : InvalidData: (:) [upgrade-npm.ps1], ParameterBindingValidationException
 + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,upgrade-npm.ps1

Thanks for reporting! I believe that a your issue should have been fixed in the latest version (v0.1.4). Can you update (npm install -g npm-windows-upgrade@latest) and try again?

I receive the same with 0.1.4, I think it's related to #3

My User PATH
C:\Program Files\nodejs\;C:\Users\jonno\AppData\Roaming\npm

My System PATH
C:\Users\jonno\AppData\Roaming\npm

to that effect anyway

Thanks! I'm certain that it's not your fault, but a System variable pointing to a user directory is exactly the kind of mess that brought us here ;-) I'll make sure that this tools solves your needs. I'll keep both issues until then.

Yeah, that would be my doing... I'm currently doing a fresh install of Node

A fresh install of<EMAIL_ADDRESS>with<EMAIL_ADDRESS>leaves me with no npm reference in my System PATH and a single reference to C:\Users\btp\AppData\Roaming\npm in my User PATH
I still receive the following
C:\Users\btp\AppData\Roaming\npm\node_modules\npm-windows-upgrade\powershell\upgrade-npm.ps1 : Cannot bind argument to parameter 'Path' because it is null.
    + CategoryInfo          : InvalidData: (:) [upgrade-npm.ps1], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,upgrade-npm.ps1

Had the same error. In my case I solved it by following option 2:
Option 2: remove both of

    %ProgramFiles%\nodejs\npm
    %ProgramFiles%\nodejs\npm.cmd

Thanks to all of you (@jdoose, @MhSaadany, @BarryThePenguin) - This error should now be fixed. For those curious: I checked the wrong path for existence.

Woo! Looks good here


Error: input: Clusters has not been activated for your organization when modifying provider settings without clusters enabled

Describe the bug
Setup:
Agent: v3.47.0 (local)
Provider: v0.19.0
Using a basic setup of the provider and creating a pipeline resource, once the pipeline is created and you attempt to add the following provider settings:
provider_settings {
        publish_commit_status_per_step = true
}

You will get the error:
│ Error: input: Clusters has not been activated for your organization
│
│
│   with buildkite_pipeline.test-pipeline,
│   on test-pipeline.tf line 1, in resource "buildkite_pipeline" "test-pipeline":
│    1: resource "buildkite_pipeline" "test-pipeline" {

To Reproduce
Steps to reproduce the behavior:

Create a basic pipeline resource (mine just has buildkite-agent pipeline upload as the command) without provider_settings publish_commit_status_per_step being set.
Init, Plan and Apply using Terraform and check that the pipeline created successfully.
Go back to the resource and attempt to add:

provider_settings {
        publish_commit_status_per_step = true
}

You will get the error:

│ Error: input: Clusters has not been activated for your organization
│
│
│   with buildkite_pipeline.test-pipeline,
│   on test-pipeline.tf line 1, in resource "buildkite_pipeline" "test-pipeline":
│    1: resource "buildkite_pipeline" "test-pipeline" {

Expected behavior
No error as you are not passing a clusterID at this point in time. The apply should complete successfully.
Additional context
I also tested this by adding cluster_id = "" to see if it was a work around, to no success.

Oh no! Thanks for the bug report.
I think this might actually apply to any time you try update a pipeline, regardless of what you update.
#279 modified the UpdatePipeline function to use a new GraphQL library and it now sets cluster_id in the mutation no matter what. It should work because it sets it as null if not used but the API musn't be handling that properly.
I'll look into it and get back with a path forward. For now, downgrading to <0.19.0 should fix this issue

Oh no! Thanks for the bug report.
I think this might actually apply to any time you try update a pipeline, regardless of what you update. #279 modified the UpdatePipeline function to use a new GraphQL library and it now sets cluster_id in the mutation no matter what. It should work because it sets it as null if not used but the API musn't be handling that properly.
I'll look into it and get back with a path forward. For now, downgrading to <0.19.0 should fix this issue

That's actually a great call out and something I didn't test when I was going through this. Thanks for checking on this.


fix: factor DB code out of view

This commit factors out the database code into a new db_interface.py
file. This is needed for the upcoming listener changes.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@d642013). Click here to learn what that means.
The diff coverage is 84.61%.

@@            Coverage Diff            @@
##             master      #18   +/-   ##
=========================================
  Coverage          ?   94.07%
=========================================
  Files             ?        8
  Lines             ?      152
  Branches          ?        0
=========================================
  Hits              ?      143
  Misses            ?        9
  Partials          ?        0

Impacted Files
Coverage Δ

historical_system_profiles/app.py
100% <100%> (ø)

historical_system_profiles/config.py
100% <100%> (ø)

historical_system_profiles/views/v0.py
87.17% <75%> (ø)

historical_system_profiles/db_interface.py
78.57% <78.57%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d642013...65564d5. Read the comment docs.


package restructure

Hello,
I further implemented deletestatus and addoutput
I restructured the code quite a bit. This might not be compatible with previous versions any more, but the contents of init.py should be able to resolve this.
I think this is still not optimal, the life documentation generation cannot server from src directly for some unknown reason to me.
unit tests run on the pvoutput system configured pvoutput.json
it runs addstatus, getstatus and deletestatus in this order, so should always succeed.
this still messes up the final day statistics, even when deletestatus is run :-(
idem for register and deregister
there are now tests for the normal pvoutput and the async pvoutput
If you would like any more changes, or things differently just let me know.
This is just a suggestion to code changes, I am open to discuss things.

I will close this pull request, and create new smaller ones, step by step, from the current aiohttp branch


issue in creating a vm

I tried you api it works fine...But when i was creating a OpenVZ container using create function the data  is displayed, but somehow it does not create CT...:(...Can you provide some help
$vps_creation = $proxmox->create('/nodes/'.$nodename.'/openvz -vmid '.$params['vmid'].' -hostname '.$params['hostname'].' -storage '.$params['storage'].' -password '.$params['password'].' -ostemplate '.$params['ostemplate'].' -memory '.$params['memory'].' -swap '.$params['swap'].' -disk '.$params['disk'].' -cpus '.$params['cpus'].' -ip_address '.$params['ip_address'], $params);
This is the command i tried...

Hi, can you provide the given response? It may contain more info about the issue.
Thanks

The output i get says that the vps is created but there isnt any.....
Thanks.

I know this is a very late response, but I for others reading, the mistake here is that you can't pass the params in flags directly in the string as the first argument, any params should come as a second argument in an associative array, you can see an example in the Creating resources section file.

Hi,
Its okay even if it was late, still appreciated the help...:D...And yes i understood your answer, what you mean send it as a post array which is associative array, then it will execute successfully.


Enable CCM demo to work on nrf51

Signed-off-by: Daniel Egger<EMAIL_ADDRESS>

nRF51 devices only support payloads of up to 27 bytes.

Maybe we should change the example to use smaller payloads, I remember that I used those sizes because I wanted to try some bench-marking. Since I already included the example as a "benchmark" (see stopwatch.rs) maybe we should use some cfgs also on the buffer size.

Huh? Where does that quoted comment come from? 😅

From the docs:
https://github.com/nrf-rs/nrf-hal/blob/af83e6ed69c5ec03b1e0f6b4adae53258f57e83a/nrf-hal-common/src/ccm.rs#L40
And from the manual:
Encryption (Page 121):

The AES CCM is limited to read maximum 27 bytes of the unencrypted payload (PL) regardless of what is specified in
the length field of the unencrypted packet.

Decryption (Page 122):

The AES CCM is limited to read maximum 27 bytes of the encrypted payload and four bytes of the MIC regardless of
what is specified in the length field of the encrypted packet.

I'll modify the example to use less payload on nrf51 when I find time (or someone beats me to it 😉 ).


Labelling Kiuwan Analysis' doesn't seem to be implemented

https://github.com/lsacera/KiuwanBaselineAction/blob/5fe31c724672c06060af11af716f5e604ce17c8e/kla.py#L46
At this point, there is no --label or -l tag, where the environment variable INPUT_LABEL is called, furthermore, the environment variable is never extracted from the environment in the code. This is leading to blank runs which should be labelled.

Hello,
I left Kiuwan near two years ago and I am not sure if we had "-l" as input parameter of kiuwan local analyzer.
I developed these two github actions in python as a proof of concept thing and left here for others to use. Unfortunately I do not have the time or the environment to test again this action, so I cannot help you right now.
Feel free to take the code and change it as necessary; also my recommendation is to review the base docker images that I am using for this actions as maybe they are not up to date from a security point of view (python version, etc...)
Sorry not being more helpful.

No problem, I've forked it and added a bunch more security features, and aim to get it much cleaner and release it again to github marketplace.

Great!! Thanks a lot.
In the beginning this was a little side project to see the feasibility of using Kiuwan in Github actions. To be true, I did not like the way actions were working at that time... maybe now is different.
But it is good to know this can be enhanced.
Cheers!


Explicit Group Init in Boot Config

Summary
Had to rebase a bit since my commits weren't attributed to my user, but the only commit needed is the last one.  Essentially I'm just adding the -group flag to the boot start command since it's not there currently, and that causes some drift from the expected configs of the file permissions.
Changes
Changed roles/splunk/tasks/configure_splunk_boot.yml to include -group {{ splunk_nix_group }}

Thanks for the PR. Sorry I was out for a bit, so I wasn't able to have a look at it.
This is a goo suggestion, but the reason it loops it because if a certain package does not exist, the whole operation will fail, and it will not install any packages at all.
This has been suggested before, but the packages should be split out by platform and version. For example, policycoreutils-python is RHEL only.
Any suggestions?

Good suggestion. I tested this, and it seems that when you restart the splunk service, it gets set to the primary group the splunk_nix_user is set to. the splunk_nix_group is only set as an additional group to that user. The primary group is automatically set by the OS to the same of the user name when the user is created initially.
Some further research is needed to get this straightened out.

Awesome - thanks.

Now I'm thinking if this shoud have been group anstead of groups.

It definitely should be, but the issue with the splunk init boot config still requires a patch. I can add it to the PR if you'd like.


custom library-level exceptions

As pointed out in #177

we could solve this by creating our own kind of exceptions so that we can handle them cleaner internally.

It would also make it easier / possible for users to have different logic for different errors, i.e. ignore network related issues when using the cache.
Worth noting that without something like #201, it will be easy for a user making heavy use of the offline queue to shoot themselves in the foot by pretending mutations succeeded when they didn't and will never run again.

closed by #393

:tada: This issue has been resolved in version 3.0.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 3.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


BOOST_FOREACH changes

so far everything appears to be in good working order. lets give this a good test. i tested what i cud and some of course will be tested in testnet.

You forgot to remove the includes :D
alert.cpp:#include <boost/foreach.hpp>
bitcoinrpc.cpp:#include <boost/foreach.hpp>
checkpoints.cpp:#include <boost/foreach.hpp>
net.h:#include <boost/foreach.hpp>
script.cpp:#include <boost/foreach.hpp>
util.cpp:#include <boost/foreach.hpp>

problem is with those gone i cant figure out which is being used in main.cpp for reverse i was gonna do it after i change the reverse


AWS Data API fixes

This PR address multiple issues on AWS Data API driver, each via a separate commit.
1. Reconciliation of AwsDataApiSession with PgSession base class
The third parameter of AwsDataApiSession.prepareQuery should be the name to stay compatible with the postgres query builder especially the .prepare(name: string) method. - https://github.com/drizzle-team/drizzle-orm/issues/1171

The transactionId is now the fifth one. Anyway it is used internally only. Note that it is also possible to remove the parameter as we have the value on the session instance properties.
the name parameter is ignored (as on neon-http driver & some others)

2. Fix the transaction id propagation
If the transaction id is not provided on the query, the session should use the current one, the one stored on the instance.
3. Fix nested transactions

await for the savepoint to be created / rollback / released before continuing
await for the transaction handler to be executed for releasing the savepoint
do not use parameters on savepoints queries as it is not supported by AWS Data API - https://github.com/drizzle-team/drizzle-orm/issues/1936

4. Tests fixes
Fix outdated tests (mainly because the returned values doesn't match the type on raw execution).
We probably should update the AwsDataApiPgQueryResultHKT.type: aws.ExecuteStatementCommandOutput but i'm not sure of that would be the right value. Probably something similar to the neon-serverless version NeonQueryResultHKT.type: QueryResult<Assume<this['row'], QueryResultRow>>;

Before
After

You should check out these PRs as well:
https://github.com/drizzle-team/drizzle-orm/pull/1933
https://github.com/drizzle-team/drizzle-orm/pull/1931
https://github.com/drizzle-team/drizzle-orm/pull/1911

Hi @dankochetov @AndriiSherman 👋
What are the next steps to merge these fixes? Do you think there is any change to merge them during the month?

@hugo082 please sign your commits
https://docs.github.com/articles/about-gpg/

@hugo082 please sign your commits docs.github.com/articles/about-gpg

@dankochetov done ✅

@dankochetov, any updates?

@hugo082 yes, I'm testing it myself and making adjustments, hoping to merge in the next few days

I've pushed this PR with my changes into a separate branch, will continue it in #2119


Plugin does not fully comply with CEF standard

Hello,
I've been trying to use this plugin with several products but they all got rejected, perhaps this plugin was written for an older revision of CEF?
According to revision v23 of CEF events coming through syslog should look like
Jan 18 11:07:53 host CEF:Version|Device Vendor|Device Product|Device Version|Device Event Class ID|Name|Severity|[Extension]
According to the regex and test implemented here the plugin is not expecting a host in the syslog message.
<132>Aug 14 14:26:55 CEF:0|Trend Micro Inc.|OSSEC HIDS|v2.8.3|2502|User.....
There's also an option to remove the syslog header and use the start & end CEF fields for timestamp, not sure if it'll be best to check for both or split to to different inputs (or just a checkbox option in the input settings)
Let me know what you think, I'll be happy to write the fix

sorry the mess, trying to avoid multiple issues in a single commit

Thanks! I'll be looking into this soon.

@lennartkoopmann ?

This can be solved using processing pipeline steps since the v1.2.0 release of the CEF plugin. See: https://github.com/Graylog2/graylog-plugin-cef/blob/master/README.md#usage


Integrating new version of ome_seadragon freehand drawing tool

For further details on new tools check
https://github.com/crs4/ome_seadragon/pull/42

This release requires ome_seadragon v0.6.8 or later


[Bug] docker-compose breaking

Hi,
docker-compose up throw the error :
WARNING: The BACKEND_PORT variable is not set. Defaulting to a blank string.
ERROR: The Compose file './docker-compose.yml' is invalid because:
services.sleekwaredb-nginx.ports contains an invalid type, it should be a number, or an object

How about your .env file? Is initialize right?

Sure i tried docker-compose up in root directory.
I fixed this 'issue' with the PR #35


Update pl.js

Updated transaltion for Polish language.
Cannot find strings:

scroll into view
Toggle show only unread

sorry for taking so long and thanks for the contribution


About  Min() and Auxiliary fields

当我执行select min(price),hostName from host，使用min函数再加辅助字段时，在返回的结果中，我希望辅助字段hostName的值和price值的最小值是属于同一个point的。就像使用first函数那样。

HI @liurunchao, min(price) is an aggregator and works on just one field. There currently isn't a way to include auxiliary fields belonging to the same selected point in the result. This is why you will see the wrong hostName value associated with the price value.
In future, the mailing list would be better for these types of questions, and please use English.

Dupe of #7719.

@e-dard I told him use Chinese and I will translate later. Not everyone good at English in China. You can understand Chinese？ Maybe google, lol

@oiooj I used Google translate 😄


Add prettier plugin support for Gherkin

🤔 What's the problem you're trying to solve?
To help enforce style standards, prettier is often used for files like TypeScript, PHP, etc. Having (official) support for Gherkin would be beneficial for git hooks.
✨ What's your proposed solution?
Add plugin for Prettier that formats Gherkin.
⛏ Have you considered any alternatives or workarounds?
Current formatters seem to only be supported through VSCode or Monaco.
This prettier plugin seems limited in options if you want slightly different configurations.
📚 Any additional context?

This text was originally generated from a template, then edited by hand. You can modify the template here.

Does an implementation of a Prettier plugin for Gherkin already exist, such as the one found at https://github.com/mapado/prettier-plugin-gherkin?

Some of these plugins are very subjective. Each to their own - and each language will likely "bleed over" some of their thoughts to their language equivalent feature files.


Large values from borrowing non-BTC coins?

It seems like I'm getting some very large negative values on coins that I previously shorted on margin and therefore borrowed coins other than BTC.  In the earnings columns it seems like it is calulating the value of those borrowed coins as BTC even though they were something else.  In my case DOGE coin so it is showing values that are hugely negative.

There's a nice README explanation on how the earnings (and all other columns) are computed. Notice that all the columns are optional. and not all are necessarily useful to everyone.
Ideally this would work for everyone in every case but the fact is I'm developing features aligned with my own trading experience and with some input from other traders.
Currently I'm not actively maintaining the extension, but I'll surely do some improvements this autumn/winter. If you feel like having a stab at it, I'm welcoming pull requests and will do my best to review in a timely fashion.
Cheers!


Objects in payload values are not parsed correctly

-> Create a payload value with an array objects like below and pass it to the OCDoResource GET request.
var test_payload = {
  Event:'Add',
  Type:'Light',
  att:{on_off: true}
};

payload = {
  type: iotivity.OCPayloadType.PAYLOAD_TYPE_REPRESENTATION,
    values: {
    }
  };
payload.values = test_payload;

-> Check the actual outcome:
"payload": {
        "type": 4,
        "values": {
            "Event": "Add",
            "Type": "Light",
            "att": {
                "type": 4
            }
        }
    }

This is still reproducible with the high-level API, so reopening.


mysql_conf error when installing setup.bash with postgres

Please use the following template when submitting issues:
Issue Template
Issue Type

[x ] Bug
[ ] Enhancement

Description
When executing setup.bash on Centos 7 systems using postgres db type (without mysql installed), receive error that mysql_config is not found.  Then remainder of install fails

If the issue is a bug, please also include the following:
Operating System
Please include the version number (ex: Ubuntu 16.04)
centos 7.4
Install

[x ] setup.bash
[ ] docker

Steps to Reproduce
Follow for production directions, chose postgres db.
Sample Scan File (if applicable)
Screenshots (optional)
attached
Console Logs (optional)

Hey Eric, according to this thread (
https://stackoverflow.com/questions/13922955/installing-mysql-python-without-mysql-server-on-centos),
can you try to install mysql-devel on OS level?
If this works, we should probably add it to "the yum part" of setup.bash...
Best, Manuel J.
On Tue, Mar 20, 2018, 21:30 Eric Kelson<EMAIL_ADDRESS>wrote:

Please use the following template when submitting issues:
Issue Template Issue Type

[x ] Bug
Enhancement

Description
When executing setup.bash on Centos 7 systems using postgres db type
(without mysql installed), receive error that mysql_config is not found.
Then remainder of install fails
[image: image]
https://user-images.githubusercontent.com/20729707/37680806-614b9358-2c5b-11e8-8424-94e1e00ca10f.png
If the issue is a bug, please also include the following: Operating System
Please include the version number (ex: Ubuntu 16.04)
centos 7.4
Install

[x ] setup.bash
docker

Steps to Reproduce
Follow for production directions, chose postgres db.
Sample Scan File (if applicable) Screenshots (optional)
attached
Console Logs (optional)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/DefectDojo/django-DefectDojo/issues/516, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ABg3RQpeYh9FPbX7TN7_ElvaUTx_ge_Cks5tgWbtgaJpZM4SymcG
.

Hm, a better solution would probably be to comment out the python mysql dependency (mysqlclient) in setup.py, so you don't install unnecssary software. This would mean we'd need to adapt the dependency installation in function of the target operating environment... food for thought, I guess.

Will try. If I am not using MySQL should this be installed at all?
On Tue, Mar 20, 2018 at 5:30 PM Manuel Jeckelmann<EMAIL_ADDRESS>wrote:

Hm, a better solution would probably be to comment out the python mysql
dependency (mysqlclient) in setup.py, so you don't install unnecssary
software. This would mean we'd need to adapt the dependency installation in
function of the target operating environment... food for thought, I guess.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/DefectDojo/django-DefectDojo/issues/516#issuecomment-374763474,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATxPa8rku-FYaSJRooC6ht9QxBkaPkebks5tgXTfgaJpZM4SymcG
.

Oh I like the second one. Agreed. The bash script should use the dB
selection to drive install.
On Tue, Mar 20, 2018 at 5:41 PM Eric Kelson<EMAIL_ADDRESS>wrote:

Will try. If I am not using MySQL should this be installed at all?
On Tue, Mar 20, 2018 at 5:30 PM Manuel Jeckelmann <
<EMAIL_ADDRESS>wrote:

Hm, a better solution would probably be to comment out the python mysql
dependency (mysqlclient) in setup.py, so you don't install unnecssary
software. This would mean we'd need to adapt the dependency installation in
function of the target operating environment... food for thought, I guess.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/DefectDojo/django-DefectDojo/issues/516#issuecomment-374763474,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATxPa8rku-FYaSJRooC6ht9QxBkaPkebks5tgXTfgaJpZM4SymcG
.

fyi, the install seems to try to do a yum install for yarn,  libpq-dev, libmysqlclient-dev
At least for libpq-dev, its postgresql-libs on centos.

https://github.com/DefectDojo/django-DefectDojo/pull/600


#pragma once warning

Hey :wink:
When I try to lint a header file (with extension .h),  the linter will give me the following warning:
warning: #pragma once in main file.  When I switch to the default include guards, gcc will not output this error, however my project has over 100 header files and I don't want to switch from #pragma once to the include guards.
Do you have any help? Thanks in advance.

Here's a perl script to make that change:
change_header.pl
#!/usr/bin/perl
open INFILE, "<$ARGV[0]" or die "Unable to open <$ARGV[0]: $!\n";
@lines = <INFILE>;
close (INFILE);

$header_name = uc($ARGV[0]);
$header_name =~ s/\./\_/g;

@output = ();

$pragma_flag = 0;

foreach $line(@lines) {
  if ($line =~ m/\#pragma\s+once/gi) {
    push @output, "#ifndef $header_name\n";
    push @output, "#define $header_name\n";
    $pragma_flag = 1;
  }
  else {
    push @output, $line;
  }
}
if ($pragma_flag == 1){
  push @output, "#endif\n";
}

open OUTFILE, ">$ARGV[0]" or die "Unable to open >$ARGV[0]: $!\n";
foreach $line(@output) {
  print OUTFILE $line;
}
close (OUTFILE);

This is how the script works. Note that it overwrites the file.
$ cat header.h
#pragma once
Line 1
Line 2
Line 3
$ ./change_header.pl header.h
$ cat header.h
#ifndef HEADER_H
#define HEADER_H
Line 1
Line 2
Line 3
#endif

And this is how you run it on all your files.. Make a backup first though, and do a test run with a dummy file to make sure everything works as expected!!
find . -name \*.h -exec ./change_header.pl {} \;

Hello. Has your issue been resolved?

Well technically yes, the script works, but why does gcc warn me about using pragma once?

The reason is that although #pragma once is widely supported, it is still a non-standard feature. You can read more about this here. What I do in these scenarios is switch to a standard feature to remove the warning. I think it's a good idea to favour a clean build (one with no warnings, even with all warning options switched on) as it helps you to identify problems easily. However, the choice is entirely yours.

Ah thank you very much, I actually didn't know that. I don't know why it would be non-standard, as it is much more practical than the default include guards... Whatever.

Sorry for the bump, but saying that #pragma once is a non-standard feature is irrevelant to the warning, @hebaishi. The warning is because gcc is seeing one file being passed to it, the header file with the #pragma once in it, and it 'thinks': "Hey, this is a main file, why does it have a pragma that tells me not to include it more than once? I'll let the developer know about this."
This warning is a problem with how the linter works, it passes the file you are working on as the main file to gcc. In this case, I would reccomend passing the flag to disable the #pragma once warning to gcc, -Wno- ... wait a moment, this flag doesn't exist.
I'd recomend re-opening this issue, or perhaps I can open a new issue that references this one.
My thoughts for fixing this -- you could create a file that includes the header file you're trying to lint, or you could match on that warning and remove it. I'd recomend the former, though the latter might be useful as a configuration option so that users can remove warnings that they can't disable.
Example commands for the former:
gcc -c -fsyntax-only myheader.h

as opposed to:
echo '#include "myheader.h"' | gcc -x c++-header -c -fsyntax-only -

Reference: http://stackoverflow.com/questions/16726352/is-is-possible-to-disable-this-warning-in-clang-warning-pragma-once-in-main-f

@kitling thanks for the useful info. I think the second option would be better: it avoids the creation of a temporary file, and adds flexibility so that the user can potentially remove other warnings (if there are any) that can't be disabled.

Well, piping the #include to gcc avoids the temporary file, which is why I provided a (shell) example demonstrating that.
I do agree that the second option would give extra flexibility, but it could also encourage people to block specific warnings that do have flags to disable them. And, honestly, I'd prefer the first method because it's better to just plain not generate the spurious warning than to filter it out.


Seil not working with OS X (10.11.1) El Capitan

Hi, been using Seil successfully to switch caps lock for years, right up to Yosemite. Great app, and real convenience for VIM bindings. Recently downloaded OS X El Capitan, which I thought was a minor dot update to Yosemite, and it now appears that Seil caps lock switch to use Escape action is no longer working.  The symptoms are that Seil runs etc, and is setup to use key code 53 but nothing happens. Please could let me know if this is an issue because you don't yet support El Capitan, and whether you plan to provide such support.

Seil-11.3.0 works well with OS X 10.11.
Please confirm your Seil is the latest stable release.
https://pqrs.org/osx/karabiner/seil.html.en
If you are using Seil-11.3.0, please confirm "No Action" configuration.
(The system setting might be reset after OS upgrade.)
https://pqrs.org/osx/karabiner/seil.html.en#usage

Hi @tekezo - thank you for your quick reply. Yes, I can confirm it now works. I was indeed on an older version. Curiously, I did have the settings set so that "Misc & Uninstall -> Check for updates on startup" was set to "The stable release only (default)"  Assuming therefore that 11.3.0 is not considered a stable release. Perhaps I should modify the default settings too.  All the same, great app, thank you very much for the assistance. Closing this as user error only.


Add Support for Advanced Activation Functions

Integrate more advanced activation functions like Swish and ELU for better performance on deeper networks.
Objective:
Enhance model expressiveness and performance.
Implementation Suggestions:

Implement additional activation functions in the activation module.
Provide options to choose these functions in model configurations.
Test and benchmark new activations against existing ones.

Hello @ravin-d-27 will you please assign me this one.

Hi @Sohammhatre10 ! I'm assigning this issue to you!


Add JUnit test engine

For some reason, Gradle did not discover JUnit tests. This PR adds the JUnit Jupiter test engine to discover those tests. Now we finally have coverage of the web module.

Codecov Report

Merging #239 into master will increase coverage by 1.78%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #239      +/-   ##
============================================
+ Coverage     75.73%   77.52%   +1.78%
- Complexity      412      427      +15
============================================
  Files            57       57
  Lines          1286     1286
  Branches        208      208
============================================
+ Hits            974      997      +23
+ Misses          224      197      -27
- Partials         88       92       +4

Impacted Files
Coverage Δ
Complexity Δ

...alidationpipeline/githubtestreporter/Properties.kt
63.63% <0%> (+9.09%)
5% <0%> (+1%)
:arrow_up:

...tionpipeline/githubtestreporter/WebHookReceiver.kt
87.5% <0%> (+12.5%)
7% <0%> (+3%)
:arrow_up:

...ionpipeline/githubtestreporter/CustomHttpClient.kt
18% <0%> (+18%)
3% <0%> (+3%)
:arrow_up:

...dationpipeline/githubtestreporter/events/Shared.kt
100% <0%> (+33.33%)
0% <0%> (ø)
:arrow_down:

.../kotlin/org/cafejojo/schaapi/web/WebApplication.kt
50% <0%> (+50%)
1% <0%> (+1%)
:arrow_up:

...ine/githubtestreporter/events/InstallationEvent.kt
83.33% <0%> (+83.33%)
5% <0%> (+5%)
:arrow_up:

.../kotlin/org/cafejojo/schaapi/web/HomeController.kt
100% <0%> (+100%)
2% <0%> (+2%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 84da361...9973334. Read the comment docs.


[Feature] Translate en-US i18n to de-DE

I'm currently working on a translation of the (kinda) new i18n file from eng => ger.

I just remembered I might need to clean up the en-US file, since some of the translations might not be used anymore 😅 But I can remove the unused one from the de-DE file if you create one so no worries! 😄

https://github.com/carlssonemil/interstellar/pull/74


[Bug] Audio and Video Meta Search load Image Results

Bug Description

When applying a Use filter while in the Audio or Video meta search tabs, the Image results for the same query are loaded.  Instead, the Use filter(s) should remain selected, and should apply to the Meta Search source that the user clicks on. (This does appear to be working).

If the user presses enter in the search box while on the Audio or Video tab, the Image results tab loads. Instead, it should do nothing.

Ah yes, so bascially when you apply a filter or submit a query on the audio or video tabs, it redirects to the image tab. definitely fixable!

@zackkrida @annatuma shouldn't this be on the frontend repo?

Yes, I didn't even notice it wasn't 😊


Bugfix/design reviews

GitHub Issue
Design Review Changes
Changes
Small style based changes from design review.
Packages Added
NA
Checks
Before making your PR, please check the following:

[x] Critical lint errors are resolved
[x] App runs locally
[x] App builds locally (run the build command for any impacted package and check for any errors before the PR)

Already merged


can't generate Doxygen document

hi
Thanks for your great job
I try to read online docs at v2.6.0
but can't find any useful data there
it like Doxygen can't find any classes to generate the document
then I try to generate it by my self but after I run CMake
I get
make: *** No rule to make target 'docs'.  Stop.
so I try to run Doxygen  directly by
doxygen docs
but generated document still same as the online version

You must pass BUILD_DOC to cmake to enable the docs target.
See here for more details.

Updated. I'm pushing on master the changes to make it possible to generate the doc locally again.


Logging for WASM httpCall

This is a recreation of https://github.com/envoyproxy/envoy-wasm/pull/640
I had some difficulties troubleshooting a WASM filter that made an httpCall. I needed some simple logging to see what my AssemblyScript was doing incorrectly. This is my first contribution to this repo.
Commit Message: Logging for WASM httpCall
Additional Description: When writing filters in AssemblyScript it is easy to make coding mistakes. Envoy will return WasmResult::BadArgument but it isn't easy to know which argument is the problem. My code had two mistakes and these log messages helped me find them.
Risk Level: Low
Testing: I tested this manually applied to envoyproxy/envoy-wasm, in Istio, building a Docker image using https://github.com/istio/proxy containing an Envoy with these changes and then manually inspected the logs while troubleshooting my WASM filter.
Docs Changes: N/A
Release Notes: N/A

@PiotrSikora I am looking for advice.

I am on a Mac.  I am nervous about enabling the Git hooks suggested by the Envoy docs.
How can I run just the linux_x64 coverage locally manually?
I suspect code coverage tests are failing because either the tests aren't logging at a detailed-enough level to trigger my trace logging, or because my debug logging isn't firing because no tests pass invalid values to WASM httpGet().  How do I see detailed info on why the code coverage failed?

@PiotrSikora I am looking for advice.

I am on a Mac.  I am nervous about enabling the Git hooks suggested by the Envoy docs.
How can I run just the linux_x64 coverage locally manually?
I suspect code coverage tests are failing because either the tests aren't logging at a detailed-enough level to trigger my trace logging, or because my debug logging isn't firing because no tests pass invalid values to WASM httpGet().  How do I see detailed info on why the code coverage failed?

I don't have those Git hooks enabled, they are not mandatory, so if you're nervous, then you can just skip them.
Coverage failure is unrelated to your changes. Other PRs are also failing because of it, and the error on the CI says: Code coverage for source/server is lower than limit of 94.6 (94.5), so you need wait until it's fixed on master branch, and then update your PR.

@PiotrSikora what would it take to get a review?  This has been sitting here for two weeks, now it has a conflict.  Should I rebase and wait?
This inspiration for this was the difficulties I had using WASM with AssemblyScript to write my own plugin.  It can be extremely difficult to debug a plugin without logging.  For example, I wanted to invoke an httpCall() in the onResponse() callback instead of the onRequest() callback.  It turns out the Solo.io runtime forgets the request headers.  I had printed them earlier, I passed them to httpCall().  It would have been super handy to see a log statement telling me what was wrong.  I spent several days trying to figure this out.
This change seems to have minimal risk.  It only affects people using WASM with Envoy running with DEBUG logging.

@PiotrSikora Fair enough.  I have greatly reduce the size of this PR.  I have removed all logging on the Wasm success path and reduced the logging on the WASM failure path from DEBUG to TRACE.  Does this make it palatable?
As an aside, how do you recommend users debug their WASM filters?  I am using Istio.  I put the .wasm binary in a ConfigMap, mount it on the Istio sidecar, and attach it using an EnvoyFilter.  When I call an ABI function and get a WasmResult::BadArgument I can log it from my filter but without a way to trace into the Envoy C++ code I am really stuck if the reason isn't obvious.  It is also easy to crash Envoy with accidental indirect infinite recursion in a buggy filter.  Is there a group looking into better sandbox and better filter debug experience?

Actually, I suffered from this when I was initially developing my Go SDK, and I'd done the exactly the same thing in this PR in my local Envoy builds. So it makes sense for code alone.
But I agree with @PiotrSikora, and if I could, I would add these logging to all of other Wasm calls.
The point is that we should think about host calls of Proxy-Wasm as "system-calls" just like WASI, and WASI runtimes never emits this kind of debugging messages, but we never suffer from this kind of debugging issue with WASI since it has more descriptive and variety of error codes returned by WASI "system-call"s.
In any way, we should update proxy-wasm's spec and define more kinds of error status for users and SDK devs to debug their programs easily.

Regards to debug messages for "system-call"s, we should be able to do strace equivalent for those "system-call"s.

Agreed. We had that originally, but it was "lost" during migration to the proxy-wasm-cpp-host repo :(

That's probably a separate topic about the ABI spec. Regards to debug messages for "system-call"s, we should be able to do strace equivalent for those "system-call"s.

Totally agree +1, and let me take a look envoy-wasm repo and rescue "strace" in proxy-wasm
With regard to error code varieties, I will file an issue in proxy-wasm/spec repo

Ah, I see what Lizan means by "strace equivalent" is this kind of trace logs in this PR. Got it.

Can we you use this api and the host call to provide debugging functionality? I guess these are the ones @PiotrSikora mentioned as "lost" in the migration since status_message_ is almost always empty string in the Envoy's current implementation

https://github.com/proxy-wasm/proxy-wasm-cpp-host/blob/master/include/proxy-wasm/context_interface.h#L563-L567
https://github.com/proxy-wasm/proxy-wasm-cpp-host/blob/master/include/proxy-wasm/exports.h#L63

Can we use this api and the host call to provide debugging functionality? I guess these are the ones @PiotrSikora mentioned as "lost" in the migration since status_message_ is almost always empty string in the Envoy's current implementation

https://github.com/proxy-wasm/proxy-wasm-cpp-host/blob/master/include/proxy-wasm/context_interface.h#L563-L567
https://github.com/proxy-wasm/proxy-wasm-cpp-host/blob/master/include/proxy-wasm/exports.h#L63

No, what I meant is that we had a real trace messages for each call that crossed ABI boundary, including all parameters and return values, see:

source/extensions/common/wasm/v8/v8.cc#L597-L598,
source/extensions/common/wasm/v8/v8.cc#L604,
source/extensions/common/wasm/v8/v8.cc#L658,
source/extensions/common/wasm/v8/v8.cc#L667.

You can still see those if you run Istio Proxy 1.6 with trace logs, e.g.:
[trace][wasm] [source/extensions/common/wasm/v8/v8.cc:626] [host->vm] proxy_on_tick(1)
[trace][wasm] [source/extensions/common/wasm/v8/v8.cc:595] [vm->host] env.proxy_get_current_time_nanoseconds(1048312)
[trace][wasm] [source/extensions/common/wasm/v8/v8.cc:525] setMemory(1048312, 8)
[trace][wasm] [source/extensions/common/wasm/v8/v8.cc:601] [vm<-host] env.proxy_get_current_time_nanoseconds return: 0
[trace][wasm] [source/extensions/common/wasm/v8/v8.cc:595] [vm->host] env.proxy_log(2, 1114184, 62)
[trace][wasm] [source/extensions/common/wasm/v8/v8.cc:516] getMemory(1114184, 62)
[info][wasm] [source/extensions/common/wasm/context.cc:1107] wasm log : It's 2020-12-07 06:50:04.304281 UTC, there is no lucky number.
[trace][wasm] [source/extensions/common/wasm/v8/v8.cc:601] [vm<-host] env.proxy_log return: 0
[trace][wasm] [source/extensions/common/wasm/v8/v8.cc:634] [host<-vm] proxy_on_tick return: void

Looks fantastic! I really would like to retrieve these trace logs, and it's going to be fairly simple to get it implemented in proxy-wasm-cpp-host repo

https://github.com/envoyproxy/envoy/pull/14433
https://github.com/proxy-wasm/proxy-wasm-cpp-host/pull/118
now that strace equivalent is implemented in proxy-wasm-cpp-host(https://github.com/proxy-wasm/proxy-wasm-cpp-host/pull/118), and Envoy's side integration is ready(https://github.com/envoyproxy/envoy/pull/14433)

in addition to the strace I introduced above PR, maybe it's useful to implement getStatus ABI for more detailed messages (it's easy to implement by just setting status_message_ to the ones like in this PR.
@PiotrSikora thoughts?

in addition to the strace I introduced above PR, maybe it's useful to implement getStatus ABI for more detailed messages (it's easy to implement by just setting status_message_ to the ones like in this PR.
@PiotrSikora thoughts?


Added my page in the Students folder

Hi!
I added my own page to the students folder.
@rishabh-bansal can you please review it.


Proposed: Support null uuid fields

Currently we can't set uuid fields to null.
Added support for this
Tested: Working :+1:

Whoops: wrong Repo...


evaluator: infinite loop on cycle with embeddings

What version of CUE are you using (cue version)?

$ cue version
cue version v0.5.0-rc.1

go version go1.20.2
      -buildmode exe
       -compiler gc
       -trimpath true
     CGO_ENABLED 0
          GOARCH amd64
            GOOS linux
         GOAMD64 v1

Also loops on tags v0.6.0-beta.1 and v0.6.0-rc.1, but not v0.4.3.
Bisected to 887f5649
What did you do?
x
x: {
	y
	y: x
}

What did you expect to see?
Something like
x.y: structural cycle
What did you see instead?
Apparently a non terminating evaluation.

Thank you - as far as I can tell, this hang hasn't been reported before.


snakecase template function turns abc_123_def into abc_123__def

As per the title, running
{{ "abc_123_def" | snakecase }}

in my template givesabc_123__def. I would expect it to give abc_123_def.
I've tracked down the issue to an indirect dependency and raised a PR - https://github.com/huandu/xstrings/pull/52 . However I still want to raise this in helm directly to track until it's fixed and updated.
Thanks!
Output of helm version:
version.BuildInfo{Version:"v3.9.4", GitCommit:"dbc6d8e20fe1d58d50e6ed30f09a04a77e4c68db", GitTreeState:"clean", GoVersion:"go1.17.13"}

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.3", GitCommit:"434bfd82814af038ad94d62ebe59b133fcb50506", GitTreeState:"clean", BuildDate:"2022-10-12T10:57:26Z", GoVersion:"go1.19.2", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"23+", GitVersion:"v1.23.10-eks-15b7512", GitCommit:"cd6399691d9b1fed9ec20c9c5e82f5993c3f42cb", GitTreeState:"clean", BuildDate:"2022-08-31T19:17:01Z", GoVersion:"go1.17.13", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.):
N/A

@hickeyma  we need to upgrade https://github.com/Masterminds/sprig if https://github.com/huandu/xstrings/pull/52 has been merged.

@yxxhero would you like to push a PR to https://github.com/Masterminds/sprig?

@hickeyma yes. if https://github.com/huandu/xstrings is released. I will push a PR for this issue.

see: https://github.com/Masterminds/sprig/pull/348

@mattfarina ping

see: https://github.com/helm/helm/pull/11582


[REF-2132]Deprecate Admin Dashboard

All Submissions:

[ ] Have you followed the guidelines stated in CONTRIBUTING.md file?
[ ] Have you checked to ensure there aren't any other open Pull Requests for the desired changed?

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

New Feature Submission:

[ ] Does your submission pass the tests?
[ ] Have you linted your code locally prior to submission?

Changes To Core Features:

[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your core changes, as applicable?
[ ] Have you successfully ran tests with your changes locally?

After these steps, you're ready to open a pull request.
a. Give a descriptive title to your PR.

b. Describe your changes.

c. Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes (if such).

Hi @ElijahAhianyo May I know why we decided to deprecate the Admin Dashboard?

Hi @ElijahAhianyo May I know why we decided to deprecate the Admin Dashboard?

Is this a feature you are currently using? It wasn't documented previously, so we were not sure how many people are using it.
In general we have been trying to slim down your dependencies to avoid conflicts with other packages, this was part of that.

Admin Dashboard maybe a good feature to have (even if optional)
I would prefer that it be documented, rather than deprecated 😄

@mandarvaze our plan was to make our own using Reflex in the future, but we can keep this one for now until we have that.
@ElijahAhianyo I'll close this PR, let's add docs for now for this.


client: proxy: allow passing SOCKS5 proxies as env. vars

Hi,
For some reason, when SOCKS5 support was added, SOCKS5 proxies could not be passed via environment variables. This PR fixes that shortcoming.

@freerdp-bot test

Nice patch, but for consistency could you also update the proxy_prepare environment variable checks?

Hi, I'm not sure what is missing from it. Should we parse another variable like socks_proxy?


Roll Flutter from 6c3a0e4d21da to 09c5863b9f79 (45 revisions)

Roll Flutter from 6c3a0e4d21da to 09c5863b9f79 (45 revisions)
https://github.com/flutter/flutter/compare/6c3a0e4d21da...09c5863b9f79
2022-06-28<EMAIL_ADDRESS>Roll Flutter Engine from 6cff45c25c34 to 7a300ec0f52b (2 revisions) (flutter/flutter#106744)
2022-06-28<EMAIL_ADDRESS>Refactor daemon to check for project's supported platforms (flutter/flutter#106704)
2022-06-28<EMAIL_ADDRESS>[flutter_tools] add packages_autoroller to .ci.yaml as bringup (flutter/flutter#106711)
2022-06-28<EMAIL_ADDRESS>Make TextInputClient a mixin (flutter/flutter#104291)
2022-06-28<EMAIL_ADDRESS>Roll Plugins from 1d327c4a5684 to 4e29c26dedcf (1 revision) (flutter/flutter#106739)
2022-06-28<EMAIL_ADDRESS>Roll Flutter Engine from 7b569d51d6f8 to 6cff45c25c34 (1 revision) (flutter/flutter#106733)
2022-06-28<EMAIL_ADDRESS>Roll Flutter Engine from b372fb4d11b0 to 7b569d51d6f8 (2 revisions) (flutter/flutter#106728)
2022-06-28<EMAIL_ADDRESS>Roll Flutter Engine from 8f07aeb1fcea to b372fb4d11b0 (1 revision) (flutter/flutter#106723)
2022-06-28<EMAIL_ADDRESS>Roll Flutter Engine from 6301c5cb306e to 8f07aeb1fcea (1 revision) (flutter/flutter#106719)
2022-06-28<EMAIL_ADDRESS>Roll Flutter Engine from 379209acebf8 to 6301c5cb306e (1 revision) (flutter/flutter#106716)
2022-06-28<EMAIL_ADDRESS>Roll Flutter Engine from<PHONE_NUMBER>66 to 379209acebf8 (2 revisions) (flutter/flutter#106710)
2022-06-28<EMAIL_ADDRESS>Roll Flutter Engine from fe05fffab67d to<PHONE_NUMBER>66 (4 revisions) (flutter/flutter#106707)
2022-06-27<EMAIL_ADDRESS>Roll Flutter Engine from 6e4c5157e90b to fe05fffab67d (1 revision) (flutter/flutter#106702)
2022-06-27<EMAIL_ADDRESS>add old gallery page transition (flutter/flutter#106701)
2022-06-27<EMAIL_ADDRESS>Bump debian from bullseye-20220527-slim to bullseye-20220622-slim in /dev/ci/docker_linux (flutter/flutter#106700)
2022-06-27<EMAIL_ADDRESS>Roll Flutter Engine from cfbfb0c1776c to 6e4c5157e90b (2 revisions) (flutter/flutter#106699)
2022-06-27<EMAIL_ADDRESS>Roll pub packages (flutter/flutter#106693)
2022-06-27<EMAIL_ADDRESS>[flutter_tools] refactor packages_autoroller.dart script (flutter/flutter#106580)
2022-06-27<EMAIL_ADDRESS>Updated positional parameter ordering for IndexedStack example (flutter/flutter#106687)
2022-06-27<EMAIL_ADDRESS>Implement frameData for TestWindow (flutter/flutter#105537)
2022-06-27<EMAIL_ADDRESS>Roll Flutter Engine from 83a16dd53a8f to cfbfb0c1776c (1 revision) (flutter/flutter#106690)
2022-06-27<EMAIL_ADDRESS>Export SpellOutStringAttribute and LocaleStringAttribute (flutter/flutter#106682)
2022-06-27<EMAIL_ADDRESS>Roll Plugins from 8bf46f15bfe8 to 1d327c4a5684 (3 revisions) (flutter/flutter#106681)
2022-06-27<EMAIL_ADDRESS>Roll Flutter Engine from ce4156d519b9 to 83a16dd53a8f (2 revisions) (flutter/flutter#106680)
2022-06-27<EMAIL_ADDRESS>Sync CONTRIBUTING.md with .github copy (flutter/flutter#106677)
2022-06-27<EMAIL_ADDRESS>Fix typo in compute documentation: "captures" -> "capture" (flutter/flutter#106624)
2022-06-27<EMAIL_ADDRESS>Roll Flutter Engine from 1aefda015236 to ce4156d519b9 (1 revision) (flutter/flutter#106675)
2022-06-27<EMAIL_ADDRESS>[Windows] Flow version information to the build output (flutter/flutter#106145)
2022-06-27<EMAIL_ADDRESS>Roll Flutter Engine from ee56813c14c8 to 1aefda015236 (3 revisions) (flutter/flutter#106671)
2022-06-26<EMAIL_ADDRESS>Roll Flutter Engine from d3be1c33681e to ee56813c14c8 (1 revision) (flutter/flutter#106639)
2022-06-26<EMAIL_ADDRESS>Roll Flutter Engine from b64be81fb409 to d3be1c33681e (1 revision) (flutter/flutter#106628)
2022-06-26<EMAIL_ADDRESS>Roll Flutter Engine from aea6a1c3e421 to b64be81fb409 (1 revision) (flutter/flutter#106622)
2022-06-25<EMAIL_ADDRESS>Roll Flutter Engine from 9caf2f9e0688 to aea6a1c3e421 (1 revision) (flutter/flutter#106616)
2022-06-25<EMAIL_ADDRESS>Roll Flutter Engine from 674b90f6226c to 9caf2f9e0688 (1 revision) (flutter/flutter#106600)
2022-06-25<EMAIL_ADDRESS>Roll Flutter Engine from a1dd50405992 to 674b90f6226c (1 revision) (flutter/flutter#106598)
2022-06-25<EMAIL_ADDRESS>Fix BidirectionalIterator deprecation warning and roll engine to a1dd50405992 (flutter/flutter#106595)
2022-06-25<EMAIL_ADDRESS>Roll Flutter Engine from 83b9a591a3d5 to 4446e3edda6a (5 revisions) (flutter/flutter#106591)
2022-06-25<EMAIL_ADDRESS>Fix .packages breakage and roll engine to 83b9a591a3d5 (flutter/flutter#106584)
2022-06-24<EMAIL_ADDRESS>Export public API types from foundation/scheduler/gestures/semantics (flutter/flutter#106409)
2022-06-24<EMAIL_ADDRESS>Update 2_bug.md to ask for backtrace explicitly (flutter/flutter#103001)
2022-06-24<EMAIL_ADDRESS>[flutter_tools] tool exit from flutter create when provided just a drive letter (flutter/flutter#106451)
2022-06-24<EMAIL_ADDRESS>Roll Flutter Engine from fc08bf45b0a8 to ea756c55f29a (39 revisions) (flutter/flutter#106574)
2022-06-24<EMAIL_ADDRESS>[flutter_tools] migrate project-validate to analyze --suggestions (flutter/flutter#106149)
2022-06-24<EMAIL_ADDRESS>feat(tools): Arbitrary browser flags (closes #65575)  (flutter/flutter#104935)
2022-06-24<EMAIL_ADDRESS>Roll Plugins from dfd1b6e7d83e to 8bf46f15bfe8 (9 revisions) (flutter/flutter#106564)
...

Commit queue failed; closing this roll.

closing in favor of https://github.com/flutter/plugins/pull/6055


feat: 添加圆型进度条添加宽度配置

添加圆型进度条添加宽度配置

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.刘菲 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


show framenumber instead of timecode

It would be very nice if there was an option to show the framenumber like the old djv versions did.
Doing mostly 3d animation it is sometimes tedious to convert the timecode back to the corresponding framenumber, especially if they don't start at 0.
I would like to place a enhancement request to give users the option to show the framenumber as it is in the sequence filenames.

Nevermind. I wasn't looking. it's there already.


add minor versions to changelog

#3201? That is OOB

Here I'm just copying what we had in the individual release note.

Hello
Is the year for the last two entries correct? Should it be 2024 instead?

Hello Is the year for the last two entries correct? Should it be 2024 instead?

Yes, thanks, I will fix it...


TLS draft-28

This should make mint interoperable for draft-28 changes in TLS.  I can take a swing at implementing the record layer changes for DTLS, but that is a far bigger change and I'd like to do that separately.  (Either that, or get @ekr to do those because I made the changes in NSS.)

I tried this building this and succeeded running mint-client-https -url https://tls13.crypto.mozilla.org:443

We should merge this soon.
@martinthomson: Any idea why the tests are failing on the CI? They're passing locally, but we should probably fix that before merging.

No idea why this is failing, it's DTLS (and the DTLS code is not right for other reasons).


Use passenger standalone in development

So we are closer to production.

Look reasonable for me :+1:


kubectl exec fails on aws

Ansible version (ansible --version): 1.9.6
Python version (python --version): 2.7.6
Git commit hash or branch: master
Cloud Environment: aws
Terraform version (terraform version): v0.6.16

When running kubectl exec locally on AWS, you will see an error like the following:
$ kubectl --namespace=default exec -it nginx-3137573019-zuayi bash
Error from server: x509: certificate is valid for localhost, resching-aws-kubeworker-002, resching-aws-kubeworker-002.node.consul, ip-10-1-2-209, ip-10-1-2-209.node.consul, *.service.consul, kubernetes.default.svc.cluster.local, not ip-10-1-2-209.ec2.internal

Kubernetes derives the node names from the cloud provider and there is currently no way to override it (https://github.com/kubernetes/kubernetes/issues/22984). For now, we should probably add the internal EC2 private dns name to the certificate.

@ryane Is there a way to derive the cloud provider's DNS name as an Ansible variable?

@siddharthist I believe it is available as an ansible var on the first run before we change the hostname in the common role. after that, it will report the changed hostname. we might be able to preserve it from /etc/hostname before we change it and that might work across platforms. it is always available from the aws instance metadata but that is aws-specific, of course: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html

This is fixed in https://github.com/mantl/mantl/commit/391181ba5b5370d46b5877a424c3290aaba9f709


Owner is not a valid argument to GAM update course

The issue tracker is for reporting product deficiencies. "How do I?" questions should be posted to the discussion forum at https://groups.google.com/group/google-apps-manager. When in doubt, start at the discussion forum and return here only when instructed to do so.
Please confirm the following:

I have upgraded to the latest GAM release from https://git.io/gamreleases and I still have this issue.
I am typing the command as described in the GAM Wiki at https://github.com/jay0lee/gam/wiki

Full steps to reproduce the issue:

I created a class and added a user as a teacher sucessfully
When I came to change the teacher into a owner it said owner is not a valid argument of gam update course. I'm using the same format as here, and changing it to my alias/id and teacher email. Everything else worked as expected including syncing of students to CSV.
gam update course coursename owner<EMAIL_ADDRESS>

Expected outcome (what are you trying to do?):
Change the owner to that of an existing teacher in the class. I
Actual outcome (what errors or bad behavior do you see instead?):
ERROR: owner is not a valid argument to "gam update course"

Needed an upgrade sorry, thought I had the latest version.


Issue when using handleUpdate

I'm writing some tests using handleUpdate, but it keeps failing. I think it's because factory-guy returns an empty set on PUT requests.
The error message is the following:
"An adapter cannot assign a new id to a record that already has an id. <my-app@model:mymodel::ember882:1> had id: 1 and you tried to update it with null. This likely happened because your server returned data in response to a find or update that had a different id than the one you sent."
In this project I'm using ember-data-tastypie-adapter, ember 1.9.1 and ember-data beta.14. Maybe returning the id would solve, or serializing the hole object, not sure though. Maybe this specific for this adapter, or related to beta.14.

True, @pedrokiefer  about the return of empty for PUT's.  I put a notice on the README saying I was having problems with the beta.14.1 release and was going to wait for beta.15 to come out to see if that was better ( whacky issues that seemed ember data related ) .. so my question is, can you revert to ember-data beta.12 for now ( that is what I am doing ) .. and it should  be fine.

@danielspaniel sure I can. It's just hard to keep up with ember folks, there is always a new release and lots of new features. I haven't read the changelog for what is going on on beta.15, so I can't comment if this issue will go away.
My idea to solve this issues was to serialize the object and return it. The problem is, we need to serialize it just before returning the data and not on handleUpdate registration, or else the update will return the old object data.

Exactly @pedrokiefer ... not so simple .. and in the ember beta.12 release returning empty is the standard  when nothing changes except the updates you made, so that strategy was pretty good.
For the next beta release I will have to adjust and as you say .. I may have to do something tricky to get that to work ..  not sure yet though, but in the next few weeks when that is released I will try and fix it.

I was reading mockjax docs, and it accepts a function for response and calls it before returning data. So we can have something like:
function create_response_callback(modelName, record, mapping) {
    return function (settings) {
        var json = record.toJSON({includeId: true});
        var responseJson = mapping(modelName, json);
        this.responseText = responseJson;
    }
}

Where modelName is the model name, record is the record being updated and mapping is FactoryGuyTestMixin.mapFind function.
stubEndpointForHttpRequest would need to accept a the result of this function and set mockjax options to use this function.
What do you think about that? I can try and make a PR if this works as expected.

It's true about the function .. and it just might work to do something like this @pedrokiefer.
Take a look at the handleCreate method. It's using a function to check the data.
I think you could do same kind of thing to accomplish this for handleUpdate ( check request data and set response data ).
If you do make a pull request, make sure to add a test or two that fail without this new functionality you are adding ( if you know what I mean )

Closing this one since releasing new version 0.9.10 with you new code I just pulled in.

@pedrokiefer,  I am reworking the was factory guy handles buiding json, so return properly formated json that is ready to be send to adapter ( see issue #113 )
This means that the mapFind method might be out of the loop is building ( unless I can figure out how to bring it back in ).
This means that now the handleFind method will no longer have to make the build and then call mapFind as it does now, since the json returned will already be setup with modelName preset:
 handleFind: function () {
   var args = Array.prototype.slice.call(arguments);
   var modelName = args.shift();
   var json = FactoryGuy.build.apply(FactoryGuy, arguments);
   var id;

   if (FactoryGuy.useJSONAPI()) {
     id = json.data.id
   } else {
     id = json.id;
     json = this.mapFind(modelName, json);
   }

   var url = this.buildURL(modelName, id);
   new MockGetRequest(url, modelName, json);
   return id;
 },

What will happen now is that the build funciton will produce this:
  var json = build('user', 'with_hats');

  // json ->
  {
    user: {
      id: 1,
      name: 'User1',
      hats: [{type: 'big_hat', id:1},{type: 'big_hat', id:2}],
    },
    'big_hats': [
      {
        id: 1,
        type: "BigHat"
      },
      {
        id: 2,
        type: "BigHat"
      }
    ]
  }

So mapFind will be removed since its already mapped.
Maybe there is a way to use a method like afterBuild or afterFind or convertJsonAfterFind ?  to convert the json to something you want?  rather than mapFind ??
any thoughts? questions comments ?  before I change this?


refactor: add a method which returns an error

This PR adds a new method to the Localizer interface, which returns an error instead of a string. This is useful and can reduce boilerplate by handling error creation directly.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation change
[x] Refactor

Checklist

[x] Documentation added for the feature
[x] CI and all relevant tests are passing
[ ] Code Review completed
[ ] Verified independently by reviewer

CC @ankithans