stable/rabbitmq-ha fails to start using NFS storage provisioner

Is this a request for help?:

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Version of Helm and Kubernetes: helm 2.9.1 and kubernetes v1.11.1
Which chart: stable/rabbitmq-ha
What happened:
Pod continually fails to start with error
chown: /var/lib/rabbitmq: Operation not permitted
chown: /var/lib/rabbitmq: Operation not permitted

What you expected to happen:
Pod to start successfully
How to reproduce it (as minimally and precisely as possible):
I'm using NFS as a Persistence Storage Provisioner.
I'm using a storageClass to set my nfs-storage-provisioner.
helm install \
-f values.yaml \
--name rabbitmq \
stable/rabbitmq-ha

Anything else we need to know:

Maybe a solution could be include in the service template.
securityContext:
  enabled: true
  fsGroup: 1001
  runAsUser: 1001


Audio loss  & Video skip for Live HLS streams on Samsung & LG Devices

Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
4.3.2
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from main?
Yes
Are you using the demo app or your own custom app?
Both custom app & shaka demo app
If custom app, can you reproduce the issue using our demo app?
Yes
What browser and OS are you using?
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
LG 2020 & 2023 & Samsung 2018
LG 2023
Model : 43LM5600PTC WebOS : 4.9.7-14
Firmware version : 05.30.25
Samsung 2017
Model : UA49MU6470
Firmware version : T-KTMUABC-1310.1
What are the manifest and license server URIs?

What configuration are you using?  What is the output of player.getConfiguration()?
{
"drm": {
"retryParameters": {
"maxAttempts": 3,
"baseDelay": 1000,
"backoffFactor": 2,
"fuzzFactor": 0.5,
"timeout": 30000,
"stallTimeout": 5000,
"connectionTimeout": 10000
},
"servers": {},
"clearKeys": {},
"advanced": {},
"delayLicenseRequestUntilPlayed": false,
"logLicenseExchange": false,
"updateExpirationTime": 1,
"preferredKeySystems": []
},
"manifest": {
"retryParameters": {
"maxAttempts": 3,
"baseDelay": 1000,
"backoffFactor": 2,
"fuzzFactor": 0.5,
"timeout": 30000,
"stallTimeout": 5000,
"connectionTimeout": 10000
},
"availabilityWindowOverride": 840,
"disableAudio": false,
"disableVideo": false,
"disableText": false,
"disableThumbnails": false,
"defaultPresentationDelay": 0,
"dash": {
"clockSyncUri": "https://time.akamai.com/",
"ignoreDrmInfo": false,
"disableXlinkProcessing": false,
"xlinkFailGracefully": false,
"ignoreMinBufferTime": true,
"autoCorrectDrift": true,
"initialSegmentLimit": 1000,
"ignoreSuggestedPresentationDelay": false,
"ignoreEmptyAdaptationSet": false,
"ignoreMaxSegmentDuration": false,
"keySystemsByURI": {
"urn:uuid:1077efec-c0b2-4d02-ace3-3c1e52e2fb4b": "org.w3.clearkey",
"urn:uuid:edef8ba9-79d6-4ace-a3c8-27dcd51d21ed": "com.widevine.alpha",
"urn:uuid:9a04f079-9840-4286-ab92-e65be0885f95": "com.microsoft.playready",
"urn:uuid:79f0049a-4098-8642-ab92-e65be0885f95": "com.microsoft.playready",
"urn:uuid:f239e769-efa3-4850-9c16-a903c6932efb": "com.adobe.primetime"
}
},
"hls": {
"ignoreTextStreamFailures": false,
"ignoreImageStreamFailures": false,
"useFullSegmentsForStartTime": false,
"defaultAudioCodec": "mp4a.40.2",
"defaultVideoCodec": "avc1.42E01E"
}
},
"streaming": {
"retryParameters": {
"maxAttempts": 3,
"baseDelay": 1000,
"backoffFactor": 2,
"fuzzFactor": 0.5,
"timeout": 30000,
"stallTimeout": 5000,
"connectionTimeout": 10000
},
"rebufferingGoal": 3,
"bufferingGoal": 16,
"bufferBehind": 8,
"ignoreTextStreamFailures": true,
"alwaysStreamText": false,
"startAtSegmentBoundary": false,
"gapDetectionThreshold": 0.1,
"smallGapLimit": 0.5,
"jumpLargeGaps": false,
"durationBackoff": 1,
"forceTransmuxTS": false,
"safeSeekOffset": 5,
"stallEnabled": true,
"stallThreshold": 3,
"stallSkip": 0.1,
"useNativeHlsOnSafari": true,
"inaccurateManifestTolerance": 2,
"lowLatencyMode": false,
"autoLowLatencyMode": false,
"forceHTTPS": false,
"preferNativeHls": false,
"updateIntervalSeconds": 1,
"dispatchAllEmsgBoxes": false,
"observeQualityChanges": false
},
"offline": {
"usePersistentLicense": true
},
"abr": {
"enabled": true,
"useNetworkInformation": true,
"defaultBandwidthEstimate": 11856503.700387241,
"switchInterval": 8,
"bandwidthUpgradeTarget": 0.85,
"bandwidthDowngradeTarget": 0.95,
"restrictions": {
"minWidth": 0,
"maxWidth": null,
"minHeight": 0,
"maxHeight": null,
"minPixels": 0,
"maxPixels": null,
"minFrameRate": 0,
"maxFrameRate": null,
"minBandwidth": 0,
"maxBandwidth": null
},
"advanced": {
"minTotalBytes": 128000,
"minBytes": 16000,
"fastHalfLife": 2,
"slowHalfLife": 5
}
},
"preferredAudioLanguage": "",
"preferredTextLanguage": "",
"preferredVariantRole": "",
"preferredTextRole": "",
"preferredAudioChannelCount": 2,
"preferredVideoCodecs": [],
"preferredAudioCodecs": [],
"preferForcedSubs": false,
"preferredDecodingAttributes": [],
"restrictions": {
"minWidth": 0,
"maxWidth": null,
"minHeight": 0,
"maxHeight": 1080,
"minPixels": 0,
"maxPixels": null,
"minFrameRate": 0,
"maxFrameRate": null,
"minBandwidth": 0,
"maxBandwidth": null
},
"playRangeStart": 0,
"playRangeEnd": null,
"cmcd": {
"enabled": false,
"sessionId": "",
"contentId": "",
"useHeaders": false
}
}
What did you do?

Play any HLS live content
You will frequently notice Audio is lost for few seconds & video also stucks quite frequently

What did you expect to happen?
Playback to play smoothly , without audio loss or video freezing
What actually happened?
There are very frequent audio losses & video freezes faced while playing any live HLS content
https://github.com/shaka-project/shaka-player/assets/108855875/ba82d794-dcce-4f23-8574-41d6c799f5fb

We've recently fixed a lot of issues with HLS, can you check again against the main branch? Thanks!


Add visible rendering for the <gap> element

We don't really have any rendering for the <gap> element, although it's widely used. In some cases it's used badly:
<gap reason="illegible" extent="1 letter"/>
where I think we should be using:
<gap reason="illegible" unit="em" quantity="1"/>
and I think we should constrain the values of @unit to a subset of valid CSS units. We could easily convert @extent="1 letter" to "@unit="ex" @quantity="1", and then we could render a realistic-sized grey box or similar default, which of course anthologies could override as they wish.

I've experimented with this locally, and I think we need a discussion on how to represent gaps: how they should appear initially, whether a switch should be available in the Tools panel to highlight them, and what they should look like when highlighted. Right now they just show up as empty spaces, which is basically puzzling to the reader, I think.

After thinking a bit more, this is what I would propose:

Replace @extent with @unit and @quantity, and get rid of @extent from the schema.
Add 'ex' to the allowed values of @unit, since it's closer to what people meant by "letter" in @extent.
Assume that when @unit and @quantity are used, the intention is to describe an inline gap, and process accordingly.
If anyone wants to encode a multiline gap shape, they must do it with @style, in which case we just copy the style to the output and Schematron disallows the use of @unit and @quantity.

How does this sound?

That makes good sense. I assume you mean 'em' rather than 'ex'

@JanelleJenstad: Record our encoding protocol here. @dim is not allowed on <gap> so it's not possible to indicate that the gap is horizontal or vertical (that's on <space>)

@martindholmes are we still going to use "ex" rather than "em"? If so, can you please add that to the allowed values today? I'll switch the values out so that you can add your rendering.

The value 'ex' added to gap/@unit in rev 15569.

@LEMDO-PM: Let's add this to documentation now.

Reassigning to myself and @LEMDO-PM for documentation.

@LEMDO-PM @JanelleJenstad: As far as I can see, all proper usages of <space> and <gap> are rendering correctly, so I think all that's left here is the documentation.


Syntax highlight for Webstorm?

Any ideas about how to "teach" Webstorm to highlight syntax correctly inside the media query?
Right now it looks like this:

I know about the hack with adding css, but maybe there is something better?

Hi @SilencerWeb,
I tried to go at this problem with #20, but sadly the highlighting plugin in IntelliJ / Webstorm only seems to interact with css directly exported from styled-components(/native) : (.
So while I'm completely with you, syntax highlighting really would be great, I don't see a way for us to make this possible atm (without rewriting the plugins for the Jetbrains products ; ).
Best,
Tim.

You can use styled-components plugin and add additional template tag prefixes in plugin settings


accessing messages from outside the handler and bookkeeping of custom messages

I want to receive a message from python in js.
I followed the example on https://anywidget.dev/en/jupyter-widgets-the-good-parts/ regarding custom messages.
this.on("msg:custom", msg => {
      console.log("msg custom", msg)
        ret = msg}
    )
    console.log("ret:", ret)
  }

"this" refers to a message handler wrote for the javascript side.
In my little text example I run send() on a button click and then echo the message.
This is what gets printed to the console on the first run
ret: undefined
msg custom
Object { fn: "fun", args: (2) […] }

on subsequent runs the number of "msg custom" lines increases
ret: undefined
msg custom
Object { fn: "fun", args: (2) […] }

ret: undefined
msg custom
Object { fn: "fun", args: (2) […] }
msg custom
Object { fn: "fun", args: (2) […] }

How can I access the message outside of the msg handler and why do the messages pile up. Do I need to clear some queue?

Can you please provide a minimal reproducible example?
class Widget(anywidget.AnyWidget):
  _esm = """
  export function render({ model, el }) {
    model.on("msg:custom", (msg) => {
      el.innerText = msg.text;
    });
  }
  """

w = Widget()

w.send({ "text": "hi" })


Can I train yolov1 by using single GPU?

Hi. Thanks for your great works.
I have one GPU, so I can use single GPU training strategy.
But in https://github.com/yakhyo/yolov1-pytorch/blob/main/main.py#L63, I think your codes use multi GPU strategy.
How can I train using single GPU?
Thanks.

Hi @PeterKim1, it should work for single GPU also


Update Node Version in serverless-raw examples

Node 6.10 can no longer be used to create new AWS Lambda functions, it
has been EOL'd upstream and Amazon no longers supports creating new
lambdas with this runtime:
Error creating Lambda function: InvalidParameterValueException:
The runtime parameter of nodejs6.10 is no longer supported for
creating or updating AWS Lambda functions. We recommend you use the
new runtime (nodejs8.10)

This also includes a change to bump the version of pulumi we are using in the webserver-py example, so it gets a newer version that has the custom resource options.  We can change the codegen to now require this, but for now I want to get these builds healthy again and there may be more stuff lingering behind this we also have to change.


change dict to OrderedDict in format_row_as_dict method to allow for preservation of column order during queries

In pandas (and more generally, in python), collections of unordered key-value pairs (such as a list of dicts to be converted to a DataFrame) are key-aligned by alphabetizing the keys. By changing this set of unordered key-value pairs to an ordered data structure (i.e. the OrderedDict) we can circumvent this problem and maintain column order.
This was a problem during queries -- I was querying Vertica and my columns were being alphabetized instead of preserving their original order. This workaround is hopefully a solution to avoid writing a million .loc statements in my Jupyter notebooks! :)

seems like this data structure was added in python 2.7.
in theory (i havent validated this recently) this library should support 2.6, so im hesitant to potentially break this for any 2.6 users.

would it be possible to use the ordereddict module (link) which is the same implementation, but for python 2.4-2.6?

yea i think using that would be fine

@alexjikim I finally got around to updating this. Thoughts/feedback?


[fix] Broadcast optimizer state using broadcast_dp without shard-resh…

…ard.

PR types

PR changes

Description

 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.kebo01 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.


Hello sir

I want your help in a code

直接发问题，不要发无意义的内容。
Send questions directly, don't send meaningless content.


Create Alphabeticpattern2.py

issue #120

please rename the file in all small case like alphabeticpattern1.py, or else the file will not be recognized by the frontend of the website

Done


Home Assistant returned a response with an error status code 500

System Health details
Home Assistant 2023.7.1
Supervisor 2023.07.1
Operating System 10.3
Frontend 20230705.1 - latest
Checklist

[X] I have read the FAQ to see if there is a known solution to my problem.
[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..

Describe the issue
Got this error when start light measurement:
(updated both HA and powercal-measure docker image)
Powercalc measure: v1.7.0:docker

2023-07-12 05:46:59,693 [INFO] Selected powermeter: hass
2023-07-12 05:46:59,693 [INFO] Selected light controller: hass
[?] What kind of measurement session do you want to run?: Light bulb(s)
 > Light bulb(s)
   Smart speaker
   Recorder
   Average

2023-07-12 05:47:04,585 [INFO] Starting measurements. Estimated duration: 3.6h
Traceback (most recent call last):
  File "//measure.py", line 330, in <module>
    main()
  File "//measure.py", line 322, in main
    measure.start()
  File "//measure.py", line 127, in start
    runner_result = self.runner.run(answers, export_directory)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/runner/light.py", line 109, in run
    self.light_controller.change_light_state(
  File "/light_controller/hass.py", line 40, in change_light_state
    self.client.trigger_service("light", "turn_on", **json)
  File "/app/.venv/lib/python3.11/site-packages/homeassistant_api/rawclient.py", line 262, in trigger_service
    data = self.request(
           ^^^^^^^^^^^^^
  File "/app/.venv/lib/python3.11/site-packages/homeassistant_api/rawclient.py", line 108, in request
    return self.response_logic(response=resp, decode_bytes=decode_bytes)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/.venv/lib/python3.11/site-packages/homeassistant_api/rawclient.py", line 113, in response_logic
    return Processing(response=response, decode_bytes=decode_bytes).process()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/.venv/lib/python3.11/site-packages/homeassistant_api/processing.py", line 103, in process
    raise InternalServerError(status_code, content)
homeassistant_api.errors.InternalServerError: Home Assistant returned a response with an error status code 500.
'500 Internal Server Error\n\nServer got itself in trouble'

Reproduction steps

run this command from Windows PowerShell as Administrator docker run --rm --name=measure --env-file=.env -v ${pwd}/export:/app/export -v ${pwd}/.persistent:/app/.persistent -it bramgerritsen/powercalc-measure:latest

...
Debug logs
Questo errore ha avuto origine da un'integrazione personalizzata.

Logger: aiohttp.server
Source: custom_components/tapo/utils.py:15
Integration: Tapo Controller (documentation, issues)
First occurred: 07:41:32 (3 occurrences)
Last logged: 07:47:08

Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 433, in _handle_request
    resp = await request_handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_app.py", line 504, in _handle
    resp = await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 85, in security_filter_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 80, in ban_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 236, in auth_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 148, in handle
    result = await handler(request, **request.match_info)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/api/__init__.py", line 329, in post
    await hass.services.async_call(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1957, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 1997, in _execute_service
    return await cast(
           ^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 235, in handle_service
    return await service.entity_service_call(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 845, in entity_service_call
    response_data = task.result()  # pop exception if have
                    ^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1192, in async_request_call
    return await coro
           ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 889, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/light/__init__.py", line 582, in async_handle_light_on_service
    await light.async_turn_on(**filter_turn_on_params(light, params))
  File "/config/custom_components/tapo/light.py", line 165, in async_turn_on
    await self._change_brightness(brightness)
  File "/config/custom_components/tapo/light.py", line 185, in _change_brightness
    value_or_raise(await self.coordinator.device.set_brightness(brightness_to_set))
  File "/config/custom_components/tapo/utils.py", line 15, in value_or_raise
    raise value_or_error
plugp100.responses.tapo_exception.TapoException: Returned unknown error_code: -1008  msg: No message

Diagnostics dump or YAML config
No response

I have no idea, this is an issue with the Tapo integration in HA.
The measure tool just calls service to turn on the light and set to a given brightness.
Could you try to call that service from HA developer tools and see if you get similar error?

Looking at the error again:
plugp100.responses.tapo_exception.TapoException: Returned unknown error_code: -1008  msg: No message
Plug P100 is a smart plug. Did you somehow set your light entity to the smart plug?

this is my .env file ... so, why it take P100 as light?
# Set the power meter to use (hass, shelly, tuya, kasa, manual, tasmota)
POWER_METER=hass

# Set the light controller to use (hass, hue)
LIGHT_CONTROLLER=hass

# Set the media controller to use (for measuring smart speakers).
MEDIA_CONTROLLER=hass

# Set the log level (CRITICAL, ERROR, WARNING, INFO, DEBUG)
LOG_LEVEL=INFO

# time between changing the light params and taking the measurement
SLEEP_TIME=3

# time between taking multiple samples for the same light setting
SLEEP_TIME_SAMPLE=3

# additional time to wait for each significant change in hue
SLEEP_TIME_HUE=2

# additional time to wait for each significant change in saturation
SLEEP_TIME_SAT=2

# additional time to wait for each significant change in color temperature
SLEEP_TIME_CT=1

# Set to a value higher than 1 to take multiple samples to reduce noise
SAMPLE_COUNT=2

# Power Meter Nudging configuration (Useful if PM doesn't report a new reading if readings are unchanged)
# How many times should nudging the Power Meter be attempted?
MAX_NUDGES=3
# When Nudging, how long to hold the non-desired state for?
PULSE_TIME_NUDGE=6
# How long to wait for the Power Meter to settle on the desired measurement after nudging
SLEEP_NUDGE=30

# Precision for the HS mode loop. You can increase it up to 4 to improve the precision
# of the profile by taking more measurements

HS_BRI_PRECISION=1.0
HS_HUE_PRECISION=1.0
HS_SAT_PRECISION=1.0

# Shelly
SHELLY_IP=x.x.x.x
SHELLY_TIMEOUT=60

# Tuya
TUYA_DEVICE_ID=aaaaaaaaad89682385bbb
TUYA_DEVICE_IP=x.x.x.x
TUYA_DEVICE_KEY=aaaaaaaae1b8abb
TUYA_DEVICE_VERSION=3.3

# Hue
HUE_BRIDGE_IP=x.x.x.x

# Home assistant
HASS_URL=http://<IP_ADDRESS>:8123/api
#HASS_TOKEN=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiI2N2M0YmQzMjIzZTU0MTRiYjQzNzJjMTlmYjQ5ZDBkOCIsImlhdCI6MTY4NDA4MzA5OCwiZXhwIjoxOTk5NDQzMDk4fQ.E-mSGB4QYzUEc1uo1kH3K2K9xxdI0bmnYFcg5bzhmEk
HASS_TOKEN=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJkNDdlNzkzN2NiODI0OGZhODY2YzFjOWUxMzg4OWUzMyIsImlhdCI6MTY4NDY1NDU1NiwiZXhwIjoyMDAwMDE0NTU2fQ.WVD0IWw8SPYcd11lY_EOATYiRMVn4s0k9xdJAzOeXaQ
# Set to true when you want to call update_entity service before requesting a power value.
# This can help when your power sensor does not update frequently enough
HASS_CALL_UPDATE_ENTITY_SERVICE=false

# Tasmota
TASMOTA_DEVICE_IP=x.x.x.x

# Kasa
KASA_DEVICE_IP=x.x.x.x

# Predefine answers to questions
COLOR_MODE=color_temp
GENERATE_MODEL_JSON=true
GZIP=true
MULTIPLE_LIGHTS=false
LIGHT_ENTITY_ID=light.lampadina_smart_5
MEASURE_DEVICE=Tapo P110
NUM_LIGHTS=1
LIGHT_MODEL_ID=L630
MODEL_NAME=Tapo L630
DUMMY_LOAD=false
POWERMETER_ENTITY_ID=sensor.presa_smart_8_current_power
RESUME=true

this the output from docker cli:

2023-07-12 08:38:41,084 [INFO] Starting measurements. Estimated duration: 3.6h
Traceback (most recent call last):
  File "//measure.py", line 330, in <module>
    main()
  File "//measure.py", line 322, in main
    measure.start()
  File "//measure.py", line 127, in start
    runner_result = self.runner.run(answers, export_directory)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/runner/light.py", line 109, in run
    self.light_controller.change_light_state(
  File "/light_controller/hass.py", line 40, in change_light_state
    self.client.trigger_service("light", "turn_on", **json)
  File "/app/.venv/lib/python3.11/site-packages/homeassistant_api/rawclient.py", line 262, in trigger_service
    data = self.request(
           ^^^^^^^^^^^^^
  File "/app/.venv/lib/python3.11/site-packages/homeassistant_api/rawclient.py", line 108, in request
    return self.response_logic(response=resp, decode_bytes=decode_bytes)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/.venv/lib/python3.11/site-packages/homeassistant_api/rawclient.py", line 113, in response_logic
    return Processing(response=response, decode_bytes=decode_bytes).process()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/.venv/lib/python3.11/site-packages/homeassistant_api/processing.py", line 103, in process
    raise InternalServerError(status_code, content)
homeassistant_api.errors.InternalServerError: Home Assistant returned a response with an error status code 500.
'500 Internal Server Error\n\nServer got itself in trouble'

Please try in HA first:
In developer tools call service:
service: light.turn_on
data:
  color_temp: 257
  brightness: 50
  transition: 0
target:
  entity_id: light.lampadina_smart_5

Does this work correctly?

The bulb shouldn't go out, it should when using light.turn_off service, but obviously not when using light.turn_on.
Btw I checked powercalc measure code and it sets the light to brightness level 1 without a color temperature first in the beginning of measure script.
That would be the following HA service call:
service: light.turn_on
data:
  brightness: 1
  transition: 0
target:
  entity_id: light.lampadina_smart_5

Could you try executing that one manually please and see if you get the same error in HA?
p100 is correct btw, it's just the underlying library used by Tapo integration in HA, which is named that way.
Also several reports are there to be found with error 1008. https://github.com/fishbigger/TapoP100/issues/110

I think is the same error:
websocket_api script: Error executing script. Unexpected error for call_service at pos 1: Returned unknown error_code: -1008 msg: No message
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 468, in _async_step
    await getattr(self, handler)()
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 703, in _async_call_service_step
    response_data = await self._async_run_long_action(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 665, in _async_run_long_action
    return long_task.result()
           ^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 1965, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2005, in _execute_service
    return await cast(
           ^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 235, in handle_service
    return await service.entity_service_call(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 848, in entity_service_call
    response_data = task.result()  # pop exception if have
                    ^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1192, in async_request_call
    return await coro
           ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 892, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/light/__init__.py", line 602, in async_handle_toggle_service
    await async_handle_light_on_service(light, call)
  File "/usr/src/homeassistant/homeassistant/components/light/__init__.py", line 582, in async_handle_light_on_service
    await light.async_turn_on(**filter_turn_on_params(light, params))
  File "/config/custom_components/tapo/light.py", line 165, in async_turn_on
    await self._change_brightness(brightness)
  File "/config/custom_components/tapo/light.py", line 185, in _change_brightness
    value_or_raise(await self.coordinator.device.set_brightness(brightness_to_set))
  File "/config/custom_components/tapo/utils.py", line 15, in value_or_raise
    value_or_error: Union[T, Exception] = either.fold(lambda x: x, lambda y: y)
        ^^^^^^^^^^^^^^^^^^^^
plugp100.responses.tapo_exception.TapoException: Returned unknown error_code: -1008  msg: No message

I removed the initial call setting brightness to 1 in the measure tool (as this caused issues with your Tapo integration).
Are you able to try again by running latest master docker container? bramgerritsen/powercalc-measure:master.
Make sure to pull first when you were already using the same docker container version.

Sorry for the delayed reply!
Same error :(
Following error from HA logs.
Logger: aiohttp.server
Source: custom_components/tapo/helpers.py:11
Integration: TP-Link Tapo (documentation, issues)
First occurred: 15:12:52 (3 occurrences)
Last logged: 15:17:13

Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 433, in _handle_request
    resp = await request_handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_app.py", line 504, in _handle
    resp = await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 85, in security_filter_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 80, in ban_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 236, in auth_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 148, in handle
    result = await handler(request, **request.match_info)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/api/__init__.py", line 349, in post
    await hass.services.async_call(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1974, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2011, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 235, in handle_service
    return await service.entity_service_call(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 870, in entity_service_call
    response_data = await _handle_entity_call(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 942, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/light/__init__.py", line 580, in async_handle_light_on_service
    await light.async_turn_on(**filter_turn_on_params(light, params))
  File "/config/custom_components/tapo/light.py", line 167, in async_turn_on
    await self._change_brightness(brightness)
  File "/config/custom_components/tapo/light.py", line 187, in _change_brightness
    value_or_raise(await self.coordinator.device.set_brightness(brightness_to_set))
  File "/config/custom_components/tapo/helpers.py", line 11, in value_or_raise
    raise value_or_error
plugp100.responses.tapo_exception.TapoException: Returned error_code: TapoError.ERR_PARAMS: Request params error

Following the response from command line:
PS C:\Users\webma\powercalc-measure> docker run --rm --name=measure --env-file=my.env -v ${pwd}/export:/app/export -v ${pwd}/.persistent:/app/.persistent -it bramgerritsen/powercalc-measure:latest
Powercalc measure: v1.8.5:docker

2023-08-03 12:33:37,065 [INFO] Selected powermeter: hass
2023-08-03 12:33:37,065 [INFO] Selected light controller: hass
[?] What kind of measurement session do you want to run?: Light bulb(s)
 > Light bulb(s)
   Smart speaker
   Recorder
   Average

2023-08-03 12:33:38,484 [INFO] Starting measurements. Estimated duration: 3.6h
2023-08-03 12:33:38,652 [INFO] Start taking measurements for color mode: color_temp
2023-08-03 12:33:38,653 [INFO] Waiting 10 seconds...
2023-08-03 12:33:48,653 [INFO] Progress: 0%, Estimated time left: 3.6h
2023-08-03 12:33:48,653 [INFO] Changing light to: ColorTempVariation(bri=1, ct=153)
Traceback (most recent call last):
  File "//measure.py", line 330, in <module>
    main()
  File "//measure.py", line 322, in main
    measure.start()
  File "//measure.py", line 127, in start
    runner_result = self.runner.run(answers, export_directory)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/runner/light.py", line 126, in run
    self.light_controller.change_light_state(
  File "/light_controller/hass.py", line 40, in change_light_state
    self.client.trigger_service("light", "turn_on", **json)
  File "/app/.venv/lib/python3.11/site-packages/homeassistant_api/rawclient.py", line 262, in trigger_service
    data = self.request(
           ^^^^^^^^^^^^^
  File "/app/.venv/lib/python3.11/site-packages/homeassistant_api/rawclient.py", line 108, in request
    return self.response_logic(response=resp, decode_bytes=decode_bytes)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/.venv/lib/python3.11/site-packages/homeassistant_api/rawclient.py", line 113, in response_logic
    return Processing(response=response, decode_bytes=decode_bytes).process()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/app/.venv/lib/python3.11/site-packages/homeassistant_api/processing.py", line 103, in process
    raise InternalServerError(status_code, content)
homeassistant_api.errors.InternalServerError: Home Assistant returned a response with an error status code 500.
'500 Internal Server Error\n\nServer got itself in trouble'

You get a different error now and on another place.
The measure tool uses HA service to change the light to brightness 1 and color temperature 153.
However the Tapo integration is misbehaving on that again.
Let's try manually executing the same service call in HA and see if you get similar error in HA logs:
service: light.turn_on
data:
  brightness: 1
  color_temp: 153
  transition: 0
target:
  entity_id: light.lampadina_smart_5

this is the error on the log (I've moved change from light.lampadina_smart_5 to light.lampadina_smart_9):
Logger: homeassistant.helpers.script.websocket_api_script
Source: custom_components/tapo/helpers.py:11
Integration: TP-Link Tapo ([documentation](https://github.com/petretiandrea/home-assistant-tapo-p100), [issues](https://github.com/petretiandrea/home-assistant-tapo-p100/issues))
First occurred: 07:57:03 (1 occurrences)
Last logged: 07:57:03

websocket_api script: Error executing script. Unexpected error for call_service at pos 1: Returned error_code: TapoError.ERR_PARAMS: Request params error
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 468, in _async_step
    await getattr(self, handler)()
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 703, in _async_call_service_step
    response_data = await self._async_run_long_action(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 665, in _async_run_long_action
    return long_task.result()
           ^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 1974, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2011, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 235, in handle_service
    return await service.entity_service_call(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 870, in entity_service_call
    response_data = await _handle_entity_call(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 942, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/light/__init__.py", line 580, in async_handle_light_on_service
    await light.async_turn_on(**filter_turn_on_params(light, params))
  File "/config/custom_components/tapo/light.py", line 167, in async_turn_on
    await self._change_brightness(brightness)
  File "/config/custom_components/tapo/light.py", line 187, in _change_brightness
    value_or_raise(await self.coordinator.device.set_brightness(brightness_to_set))
  File "/config/custom_components/tapo/helpers.py", line 11, in value_or_raise
    raise value_or_error
plugp100.responses.tapo_exception.TapoException: Returned error_code: TapoError.ERR_PARAMS: Request params error

That's what I already suspected. You get the exact same error when doing the service call directly from HA.
It's really an issue with Tapo integration. I cannot give support on that, so I suggest you to create an issue at HA issue tracker.
You could try playing around with the parameters, and see if that makes any difference.
For example increase brightness. As I see the error is raised during set_brightness call in tapo integration.
Let me know your findings.


Motion Dataset: Discrepancy between Point Cloud and Agent Box

Hi!
I have successfully decoded 11 frames of point cloud data and transformed them into the global frame. However, upon analyzing the trajectory data (which is in the global frame too), I've noticed a mismatch between the agent box in the trajectory and the corresponding point cloud.
Steps to Reproduce:

scenario_id:<PHONE_NUMBER>491d50
point cloud frame: 10 (start from 0)

The blue bounding boxes represent agents at time-index 10, while the green ones correspond to agents at time-index 6. Upon comparison, it becomes evident that the green boxes are well-aligned with the point cloud data. Could there be some problems in my point cloud processing pipeline?
Below is the code I am utilizing:
from waymo_open_dataset import dataset_pb2
from waymo_open_dataset.utils import womd_lidar_utils
def _get_laser_calib(frame_lasers, laser_name):
    for laser_calib in frame_lasers.laser_calibrations:
        if laser_calib.name == laser_name:
            return laser_calib
    return None
path = os.path.join(lidar_path, f'{scenario_id}.tfrecord')
dataset = tf.data.TFRecordDataset(path, compression_type='')
for cnt, data in enumerate(dataset):
    frame_points_xyz = {}  # map from frame indices to point clouds
    frame_points_feature = {}
    frame_points_xyz_world = {}
    frame_pose_list = []
    scenario = scenario_pb2.Scenario()
    scenario.ParseFromString(bytearray(data.numpy()))
    lidar_data = scenario.compressed_frame_laser_data
    frame_i = 0
    for frame_lasers in lidar_data:
        points_xyz_list = []
        points_feature_list = []
        points_xyz_list_world = []
        # frame_pose: It decides the vehicle frame at which the cartesian points are computed.
        frame_pose = np.reshape(np.array(frame_lasers.pose.transform),(4, 4))
        vehicle_to_world = frame_pose
        vehicle_to_world_rotation = vehicle_to_world[0:3, 0:3]
        vehicle_to_world_translation = vehicle_to_world[0:3, 3]

        for laser in frame_lasers.lasers:
            if laser.name == dataset_pb2.LaserName.TOP:
                c = _get_laser_calib(frame_lasers, laser.name)
                (points_xyz, points_feature,
                    points_xyz_return2,
                    points_feature_return2) = womd_lidar_utils.extract_top_lidar_points(laser, frame_pose, c)
                points_xyz_world = tf.matmul(vehicle_to_world_rotation, tf.transpose(points_xyz))
                points_xyz_world = tf.transpose(points_xyz_world) + vehicle_to_world_translation
                points_xyz_return2_world = tf.matmul(vehicle_to_world_rotation, tf.transpose(points_xyz_return2))
                points_xyz_return2_world = tf.transpose(points_xyz_return2_world) + vehicle_to_world_translation
            else:
                c = _get_laser_calib(frame_lasers, laser.name)
                (points_xyz, points_feature,
                points_xyz_return2,
                points_feature_return2) = womd_lidar_utils.extract_side_lidar_points(laser, c)
                points_xyz_world = tf.matmul(vehicle_to_world_rotation, tf.transpose(points_xyz))
                points_xyz_world = tf.transpose(points_xyz_world) + vehicle_to_world_translation
                points_xyz_return2_world = tf.matmul(vehicle_to_world_rotation, tf.transpose(points_xyz_return2))
                points_xyz_return2_world = tf.transpose(points_xyz_return2_world) + vehicle_to_world_translation
            points_xyz_list.append(points_xyz.numpy())
            points_xyz_list.append(points_xyz_return2.numpy())
            points_feature_list.append(points_feature.numpy())
            points_feature_list.append(points_feature_return2.numpy())
            points_xyz_list_world.append(points_xyz_world)
            points_xyz_list_world.append(points_xyz_return2_world)

        frame_points_xyz[frame_i] = np.concatenate(points_xyz_list, axis=0)
        frame_points_feature[frame_i] = np.concatenate(points_feature_list, axis=0)
        frame_points_xyz_world[frame_i] = np.concatenate(points_xyz_list_world, axis=0)

Hi @martinchen0776,
could you please confirm the version of the dataset you're using?
We introduced some changes to fix this type of issues with the last version (1.2.1) so just want to make sure this still an issue.

Hi @martinchen0776, could you please confirm the version of the dataset you're using? We introduced some changes to fix this type of issues with the last version (1.2.1) so just want to make sure this still an issue.

Hi @nicomon24,
I wanted to inquire if there have been any recent developments or progress regarding the issue.

Hi @martinchen0776 thanks for confirming the version, let me check internally and get back to you asap.

Hi @martinchen0776 thanks for confirming the version, let me check internally and get back to you asap.

Hi,
I would like to ensure if there any update regarding this issue? Thank you!

Hi @martinchen0776, sorry about the delay but the people responsible for the lidar part of the dataset have been out of office for the week. I'll let you know ASAP.

Hi, I was wondering if there have been any recent developments or updates regarding this issue.

Hi martinchen0776, thanks for your interest in the WOMD challenge. The mismatch in the box locations you identified is a known issue with the data, so your processing pipeline is likely correct in this regard.
There is inherent temporal misalignment between the LiDAR frames and original WOMD data.  When preparing the LiDAR data, we minimize this skew such that the frequency of shifts greater than 5 frames is only 0.85% in the training split and 0.94% in the validation split. The test split has a similar frequency.  It’s our expectation that this small degree of misalignment will not affect research in any substantial way.


IGNITE-8827 disable WAL logging

The ticket is resolved, closing PR. Feel free to reopen if needed.


App icon+splash

All updates made and merged in the last PR (#76) in this nested chain of collection execution PRs


Import-Subscription | copy-Subscription - does not seem to work with SSRS 2019

Do you want to request a feature or report a bug?
BUG
What is the current behavior?

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
Import-RsSubscriptionXml MySubscriptions.xml | Copy-RsSubscription -ReportServerUri $reportServerUri_tgt -RsItem "/Path/To/Report"
What is the expected behavior?
To copy the subscription
Which versions of Powershell and which OS are affected by this issue? Did this work in previous versions of our scripts?
Windows Server 2019 Desktop

In order to allow the community to consider it , please add more details like the scenario and the error message in text so it can be translated

I get the a similar error when attempting to move a Subscription from SQL Server 2014 to SQL Server 2019
Do you want to request a feature or report a bug?
BUG
What is the current behavior?
When attempting to move a subscription using Import-RsSubscriptionXml MySubscriptions.xml | Copy-RsSubscription -ReportServerUri $reportServerUri_tgt -RsItem "/Path/To/Report" syntax I get the below error:
Copy-RsSubscription : Error occurred while creating subscription 7235448a-7fbf-4686-b610-19ca9196a249 because: Cannot convert argument "ExtensionSettings", with value:
"Microsoft.PowerShell.Commands.NewWebserviceProxy.AutogeneratedTypes.WebServiceProxy1tserver_ReportService2010_asmx.ExtensionSettings", for "CreateDataDrivenSubscription" to
type "Microsoft.PowerShell.Commands.NewWebserviceProxy.AutogeneratedTypes.WebServiceProxy9tServer_ReportService2010_asmx.ExtensionSettings": "Cannot convert the
"Microsoft.PowerShell.Commands.NewWebserviceProxy.AutogeneratedTypes.WebServiceProxy1tserver_ReportService2010_asmx.ExtensionSettings" value of type
"Microsoft.PowerShell.Commands.NewWebserviceProxy.AutogeneratedTypes.WebServiceProxy1tserver_ReportService2010_asmx.ExtensionSettings" to type
"Microsoft.PowerShell.Commands.NewWebserviceProxy.AutogeneratedTypes.WebServiceProxy9tServer_ReportService2010_asmx.ExtensionSettings"."
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
Import-RsSubscriptionXml MySubscriptions.xml | Copy-RsSubscription -ReportServerUri $reportServerUri_tgt -RsItem "/Path/To/Report"
What is the expected behavior?
To copy the subscription
Which versions of Powershell and which OS are affected by this issue? Did this work in previous versions of our scripts?
Windows 11 and PowerShell 5.1.19041.1682

I am getting the exact same error. I reached a dead end trying to follow the source code to the culprit. has anyone found the solution?

Is anyone working on these issues?


[Bun - REST API] Failed to find Response internal state key

If we run Blaze server with Bun, it will show the following message:

Keep in mind that these messages will pop up when we try to run it normally or as a Bun single-file executable. If run it normally, the server will work normally but if we try to build it as Bun single-file executable, Bun seems doesn't recognize any REST API.

Fixed on PR #127


add control C-0255 to framework security

Overview

This PR:

adds rule workload-mounted-secrets that is used by control C-0255
adds control C-0255 to framework security

Additional Information
The use of relatedObjects field might be changed slightly in the future, TBD

@YiscahLevySilas1 note the control checks only volume and not the volumeMount.
See below an example of a fix for another control:
https://github.com/kubescape/regolibrary/pull/455

@YiscahLevySilas1 note the control checks only volume and not the volumeMount.
See below an example of a fix for another control:
#455

@YiscahLevySilas1 note that I've fixed and pushed the volumeMounts thing...


Cannot specify dependency on RELEASED version

Describe the bug
When sfdx-project.json package definition specifies a dependency on another package's RELEASED version, the orchestrator fails with following error:

Validating Org Authentication Mechanism..
Error: Unable to execute command .. MALFORMED_QUERY:
PatchVersion=1 and BuildNumber=RELEASED and ValidationSkipped

Example sfdx-project.json snippet:
"path": "src/case-management",
"default": false,
"package": "case-management",
"versionName": "ver 0.1",
"versionNumber": "0.1.0.NEXT",
"definitionFile": "config/package-def.json",
"dependencies": [
	{
		"package": "core",
		"versionNumber": "0.5.1.RELEASED"
	}
]

SF Documentation about dependency config allowing use of RELEASED
https://developer.salesforce.com/docs/atlas.en-us.pkg2_dev.meta/pkg2_dev/sfdx_dev_dev2gp_config_keywords.htm
To Reproduce

In a project with 2 packages with 1 depending on the other, set the dependency on major.minor.patch.RELEASED version
Promote the parent package at version from step 1
Run orchestrator script (tested with prepare pool)

Expected behavior
No errors
Platform Details (please complete the following information):

OS: Mac OS
Version: @dxatscale/sfpowerscripts/25.0.6 darwin-arm64 node-v20.8.0
Salesforce CLI(sfdx cli) Version: @salesforce/cli/2.28.6 darwin-arm64 node-v20.8.0
CI Platform: n\a

Hi @packocz Fix/feature is in progress #20

Done


[SPARK-29108][SQL][TESTS] Port window.sql (Part 2)

What changes were proposed in this pull request?
This PR ports window.sql from PostgreSQL regression tests https://github.com/postgres/postgres/blob/REL_12_STABLE/src/test/regress/sql/window.sql from lines 320~562
The expected results can be found in the link: https://github.com/postgres/postgres/blob/REL_12_STABLE/src/test/regress/expected/window.out
How was this patch tested?
Pass the Jenkins.
Why are the changes needed?
To ensure compatibility with PGSQL
Does this PR introduce any user-facing change?
No
How was this patch tested?
Comparison with PgSQL results.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

add to whitelist

cc @maropu, @dongjoon-hyun, @wangyum, @MaxGekk

Test build #112097 has started for PR 26121 at commit 2d86681.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/17096/
Test PASSed.

Test build #112097 has finished for PR 26121 at commit 2d86681.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/112097/
Test PASSed.

@DylanGuedes Thanks for the work.
Please wait until #26107 is merged.

#26107 is merged. Thanks, @gengliangwang .

Retest this please.

Test build #112122 has started for PR 26121 at commit 2d86681.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/17118/
Test PASSed.

Test build #112122 has finished for PR 26121 at commit 2d86681.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/112122/
Test PASSed.

I'm going to just merge this. It has been open so long and I am sure it has been exposed to reviewers enough time.

Merged to master.


Mono/C#: Don't try to load project assembly in project manager

This was causing an error message when launching the manager,
because there is no project assembly to load.

Thanks!

Is this relevant for 3.2 too?

Yes, but it isn't that important. Just gets rid of a false error in the project manager.
I say try it and just discard it if there are conflicts.

Cherry-picked for 3.2.2.


Update FLAMEGPU to v2.0.0-rc.2

Tested in google collab

I actually added that to the master branch


ci: build docker images on linux/arm64

Summary
This PR adds linux/arm64 to a list of platforms docker images are built on. The goal is to make local testing and development easier.
Backstory
I got an error Failed to pull image "ghcr.io/stac-utils/titiler-pgstac:uvicorn-1.3.0": no matching manifest for linux/arm64/v8 in the manifest list entries while trying to use the image
  image:
    name: ghcr.io/stac-utils/titiler-pgstac
    tag: uvicorn-1.3.0

locally on M1 macbook.

Sadly I don't think rasterio wheels are available for arm64 which is why we're only building image for amd64

Sadly I don't think rasterio wheels are available for arm64 which is why we're only building image for amd64

I can see arm64 wheels available on PyPI for latest stable version - link
although I am not sure where and how exactly are they built.

Wheels are not available for manylinux_arm64 so this won't work
you can try by changing https://github.com/stac-utils/titiler-pgstac/blob/main/docker-compose.yml#L8
to fix your issue you'll need to do
  platform: linux/amd64
  image:
    name: ghcr.io/stac-utils/titiler-pgstac
    tag: uvicorn-1.3.0


Conform Rows failing

Which version are you using?
When running the conform rows query without a where statement (for applying it to all the rows in a table), nSQL code seems to be expecting it to be provided always, thus failing
Describe the bug
Example code:
function alterTable(tableSchema) {
  return nSQL(tableSchema.name)
    .query("alter table", tableSchema)
    .exec()
    .then(() =>
      nSQL(tableSchema.name)
        .query("conform rows") // <--- here
        .exec()
    );
}

Exception backtrace:

Example
https://codepen.io/benoror/pen/VwZWJRG
Expected behavior
Allow a conform rows query without an explicit where statement

Update: It actually seems to fail even with a where statement, and fails in the _getRecords function, prior to _conform as shown in the screenshot

This issue should be resolved in nanoSQL 2.3.7, just released on NPM.


Upgrade to Vert.x 3.5.1

It should fix the annoying Netty warning linked to modules in JDK 9+

Need to wait for a new release. 3.5.1 still doesn't fix it.
https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/vertx/_bJhlRarzRs/bfh5TSXRAgAJ

Done in #31 (to version 3.5.2)


NOTICE_DEFAULT is empty but scan-report-web-app.html is fine

Hello,
i am use the oss review-toolkit on mac book with intener chip to run following command
./ort report -f PlainTextTemplate,StaticHtml,WebApp -i /Users/tony/Desktop/code/hcp3/evaluator/evaluation-result.yml  -o /Users/tony/Desktop/code/hcp3/report
the NOTICE_DEFAULT is empty, bu web app report is fine. how to fix this issue

./ort --version
bce0e4ec6d

@Tony10245  The empty notices as the right options are not passed to the reporter in order for it to generated the contents of the NOTICE file. Please PlainTextTemplate reporter documentation at https://github.com/oss-review-toolkit/ort/blob/main/docs/reporters/plain-text-templates.md and for example templates files such as NOTICE_SUMMARY.ftl see https://github.com/oss-review-toolkit/ort-config/tree/main/text-templates.
You will need to do something like the below
./ort report -f PlainTextTemplate,StaticHtml,WebApp -i /Users/tony/Desktop/code/hcp3/evaluator/evaluation-result.yml -o /Users/tony/Desktop/code/hcp3/report  -O PlainTextTemplate=template.id=NOTICE_SUMMARY -O PlainTextTemplate=template.path=~/.ort/config/text-templates/NOTICE_SUMMARY.ftl

Hi @tsteenbe ,
yes actually i have also seen the document at  https://github.com/oss-review-toolkit/ort/blob/main/docs/reporters/plain-text-templates.md, i also try the command on my environment. it seems not work. just now i also try with following command, but also the same result as before
command: ./ort report -f PlainTextTemplate -i /Users/tony/Desktop/code/hcp3/evaluator/evaluation-result.yml   -o /Users/tony/Desktop/code/hcp3/report -O PlainTextTemplate=template.id=NOTICE_SUMMARY -O PlainTextTemplate=template.path=/Users/tony/Desktop/code/oss_review_toolkit/ort_git/ort/reporter/src/main/resources/templates/plain-text/NOTICE_SUMMARY.ftl
NOTICE_SUMMARY content:
This project contains or depends on third-party software components pursuant to the following licenses:

@Tony10245 are you still affected by the issue?


Support for windows

There doesn't seem to be a working method in this release to compile chipmunk 2d into windows .dll file's. Can this please be addressed? My project will be splintered if I can't get this engine compiled for Windows.

The library was written using Visual Studio and windows.. it must be compiled without problem... I need more info or logs to figure out your problem.

The physics base library doesn't have any dependence. You only need to create your own provider for the rendering.
Yes, this code was done 4 years ago... I need to update the examples... and probably move the library to use NetStandard to make it compatible with NetCore too.
BTW I am preparing some new interesting examples of use.


ENH: Support shared library builds on windows

Hey, I help maintain grpc (and many downstream users of it) in conda-forge, where we're extremely strongly inclined to build shared libraries for everything, because we can handle the ABI impacts (by recompiling where necessary; package metadata is good enough to ensure no published artefacts will collide or crash), and because static libs bloat up all consumers.
Grpc is one of the few libraries where for reasons of pragmatism, we've so far stayed on static builds for windows, because the shared ones just don't compile. This is because MSVC requires all the horrible, horrible, HORRIBLE __declspec(dllimport) / __declspec(dllexport) notations, which need to be macros that switch based on whether you're building or consuming the library (for each shared library individually).
In most cases, there's a magic CMake variable called CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS, however, this doesn't work for for global data symbols, where it still is necessary to use the declspec stuff.
Abseil has an implementation of the required switch and annotated all its functions/symbols accordingly. I have a prototype implementation based on that switch that only annotates the global data symbols (relying on the above-mentioned CMake magic otherwise) and at least passes the compilation phase, see https://github.com/conda-forge/grpc-cpp-feedstock/pull/243. It's not a pretty sight, as it needs 4 different switches (one each for GPR, gRPC, gRPC++ & UBP).
For easier inspection, I've pushed a branch with the relevant commits for that (the PR on the feedstock is mixed with fixing https://github.com/grpc/grpc/issues/30838). The branch doesn't cleanly rebase on master, so it's based on the v1.54.x branch. Key commit is this one: https://github.com/h-vetinari/grpc/commit/de89137c824e9838099dc94e2657b785ef99d66e.
The grpcio python bindings built on top of that shared library fail a simple test however, with an error that seems to be caused by an access violation, which could e.g. be a NULL-pointer dereference. For now I'm a bit stuck and wanted to open this discussion if people here are interested in this work. If so, I'm happy to rebase the branch on master and open a PR.
PTAL @jtattermusch @veblush
CC @coryan, who had some encouraging words about this effort.

This would be very useful, thanks.  I left a comment in your commit suggesting a different (and probably more correct) fix.

This would be very useful, thanks. I left a comment in your commit suggesting a different (and probably more correct) fix.

Thanks so much!, this was enough to turn our CI green, so I've pushed the updated commit based on your suggestion to my branch again.

@h-vetinari Thank you for the issue. WINDOWS_EXPORT_ALL_SYMBOLS sounds promising, would you mind creating a PR?

@h-vetinari Thank you for the issue. WINDOWS_EXPORT_ALL_SYMBOLS sounds promising, would you mind creating a PR?

#33175 🙃

CC @jtattermusch

Xref previous issue for this #15333

Also perhaps worth noting: we've been running on shared windows builds (based on https://github.com/grpc/grpc/pull/33175 and equivalents) for over two months now, with no reported issues.
We haven't yet reached every nook & cranny because grpc 1.55+ is tied to protobuf 4.23 (at least for the purposes of our infra), and not all protobuf-dependent packages have builds for 4.23.x yet. However, the number of stragglers is pretty small, and I'd say it's pretty representative of most of conda-forge nowadays.


Convert to swift4.2

I updated project language to 4.2.
Could you check it, please?

Hi @horita-yuya
Thank you for your PR.


Rename Individual to Solution

These are boring, mostly mechanical indiv -> sol changes. This PR:

[x] Is part of #239.
[ ] Adds and passes relevant tests.
[x] Has well-formatted code and documentation.

Notes:

It is essential that you add a test when making code changes.
This keeps the code coverage level up, and helps ensure the changes work as intended.
When fixing a bug, you must add a test that would produce the bug in the master branch, and then show that it is fixed with the new code.
New code additions must be well formatted. Changes should pass the pre-commit workflow, which you can set up locally using pre-commit.
Docstring additions must render correctly, including escapes and LaTeX.

@leonlan can you have another look?

OK. The next one after this is pyvrp.educate to pyvrp.search.


ARROW-8279: [C++] Do not export Codec implementation symbols, remove codec-specific headers

This reduces a lot of boilerplate associated with Codec implementation.

The test failures here are ARROW-8280

Roger that, I'll move things to anonymous namespaces and add the internal header.

+1. Will merge on green

Hm grpc_ep continuing to fail in the MinGW builds
CMake Error at D:/a/arrow/arrow/build/cpp/grpc_ep-prefix/src/grpc_ep-stamp/grpc_ep-build-RELEASE.cmake:62 (message):
  Command failed: 2

   'D:/a/arrow/msys64/usr/bin/make'

  See also

    D:/a/arrow/arrow/build/cpp/grpc_ep-prefix/src/grpc_ep-stamp/grpc_ep-build-*.log

make[2]: *** [CMakeFiles/grpc_ep.dir/build.make:130: grpc_ep-prefix/src/grpc_ep-stamp/grpc_ep-build] Error 1
make[1]: *** [CMakeFiles/Makefile2:1066: CMakeFiles/grpc_ep.dir/all] Error 2
make: *** [Makefile:158: all] Error 2

Another flaky googletest download. Hopefully this stops happening
FAILED: googletest_ep-prefix/src/googletest_ep-stamp/googletest_ep-download
cmd.exe /C "cd /D C:\projects\arrow\cpp\build\googletest_ep-prefix\src && C:\Miniconda37-x64\envs\arrow\Library\bin\cmake.exe -P C:/projects/arrow/cpp/build/googletest_ep-prefix/src/googletest_ep-stamp/googletest_ep-download-RELEASE.cmake && C:\Miniconda37-x64\envs\arrow\Library\bin\cmake.exe -E touch C:/projects/arrow/cpp/build/googletest_ep-prefix/src/googletest_ep-stamp/googletest_ep-download"
CMake Error at googletest_ep-stamp/googletest_ep-download-RELEASE.cmake:49 (message):
  Command failed: 1
   'C:/Miniconda37-x64/envs/arrow/Library/bin/cmake.exe' '-Dmake=' '-Dconfig=' '-P' 'C:/projects/arrow/cpp/build/googletest_ep-prefix/src/googletest_ep-stamp/googletest_ep-download-RELEASE-impl.cmake'
  See also
    C:/projects/arrow/cpp/build/googletest_ep-prefix/src/googletest_ep-stamp/googletest_ep-download-*.log
[9/269] Performing configure step for 'mimalloc_ep'

Appveyor passed on my fork :man_shrugging: https://ci.appveyor.com/project/wesm/arrow/builds/31856939

+1


feat: Pure JS custom host objects

Avoids substantial slowdown caused by host objects with embedder fields.

Depends on: denoland/rusty_v8#1322
Depends on: denoland/rusty_v8#1324
Deno bug: denoland/deno#12067

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

For some reason v8::Symbol::for_global is returning a different symbol to the one defined in 01_core.js.

Is it possible that you are getting a SymbolObject back from the key iterator rather than a Symbol?

Have tracked this down to a rusty_v8 bug and filed denoland/rusty_v8#1323.

I think this is now ready for review. The relevant tests in deno pass:
$ ./target/debug/deno test cli/tests/unit/message_channel_test.ts
running 2 tests from ./cli/tests/unit/message_channel_test.ts
messagechannel ... ok (35ms)
messagechannel clone port ... ok (20ms)

ok | 2 passed | 0 failed (146ms)

Running some benchmarks with this branch it looks like the ~30% slowdown I observed in my Deno.serve benchmarks comes specifically from calling createHostObject().
I had thought that ObjectSetPrototypeOf(result, Prototype) was the culprit, but after trying both the following options I'm at a loss to explain why one is consistently much faster than the other:
function fromInnerRequest(inner, signal, guard) {
  const request = core.createHostObject(RequestPrototype);
  request[webidl.brand] = webidl.brand;
  request[_request] = inner;
  request[_signal] = signal;
  request[_getHeaders] = () => headersFromHeaderList(inner.headerList, guard);
  return request;
}

is 30% slower than both:
function fromInnerRequest(inner, signal, guard) {
  const request = webidl.createBranded(Request);
  request[core.hostObjectBrand] = core.hostObjectBrand;
  request[_request] = inner;
  request[_signal] = signal;
  request[_getHeaders] = () => headersFromHeaderList(inner.headerList, guard);
  return request;
}

and:
function fromInnerRequest(inner, signal, guard) {
  const request = ObjectCreate(RequestPrototype);
  request[webidl.brand] = webidl.brand;
  request[core.hostObjectBrand] = core.hostObjectBrand;
  request[_request] = inner;
  request[_signal] = signal;
  request[_getHeaders] = () => headersFromHeaderList(inner.headerList, guard);
  return request;
}

But either way, deno currently has 32 calls to webidl.createBranded(...) vs one call to createHostObject(), so it seems to makes sense to deprecate createHostObject given only one can be used.

Hey @lrowe, sorry for a slow turnaround. I will review all your PRs in the coming days 👍

Unfortunately it's not possible to run the CI workflow when rusty_v8 is set to a git checkout:
Run cargo test --locked --release --all-features --bins --tests --examples && cargo test --doc
    Updating git repository `[https://github.com/lrowe/rusty_v8`](https://github.com/lrowe/rusty_v8%60)
    Updating git submodule `[https://chromium.googlesource.com/chromium/src/base/trace_event/common.git`](https://chromium.googlesource.com/chromium/src/base/trace_event/common.git%60)
    Updating git submodule `[https://github.com/denoland/chromium_build.git`](https://github.com/denoland/chromium_build.git%60)
    Updating git submodule `[https://github.com/denoland/chromium_buildtools.git`](https://github.com/denoland/chromium_buildtools.git%60)
    Updating git submodule `[https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libcxx.git`](https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libcxx.git%60)
error: failed to get `v8` as a dependency of package `deno_core v0.218.0 (D:\a\deno_core\deno_core\core)`

Caused by:
  failed to load source for dependency `v8`

Caused by:
  Unable to update https://github.com/lrowe/rusty_v8?rev=2545a6159f7ef174538c84c5a0c0e0949222835c

Caused by:
  failed to update submodule `buildtools`

Caused by:
  failed to update submodule `third_party/libc++/trunk`

Caused by:
  path too long: 'C:/Users/runneradmin/.cargo/git/checkouts/rusty_v8-c975a1bffb547bc0/2545a61/buildtools/third_party/libc++/trunk/test/std/experimental/utilities/propagate_const/propagate_const.class/propagate_const.non-const_observers/explicit_operator_element_type_ptr.pass.cpp'; class=Filesystem (30)

@bartlomieju it would be great if you could take a look at the associated rusty_v8 change first, https://github.com/denoland/rusty_v8/pull/1322.  Not having to recompile v8 makes development much easier.

@lrowe so sorry for a slow turnaround. I'm in the process of doing a rusty_v8 release which will include you PR. I'll ping you here again once it's all done.

Question for reviewers: What's the best way to deprecate createHostObject?
Per the comment above, it is much slower than assigning the brand directly. The only place it is currently used is in the deno MessagePort code (PR changing that: https://github.com/denoland/deno/pull/21358.)
Should we simply remove createHostObject entirely and ensure the deno PR is merged when deno is updated or should we add a @deprecated JSDoc tag and remove later (I don't see any in deno_core itself)?

Question for reviewers: What's the best way to deprecate createHostObject?
Per the comment above, it is much slower than assigning the brand directly. The only place it is currently used is in the deno MessagePort code (PR changing that: denoland/deno#21358.)
Should we simply remove createHostObject entirely and ensure the deno PR is merged when deno is updated or should we add a @deprecated JSDoc tag and remove later (I don't see any in deno_core itself)?

It's fine to remove it outright, no need to deprecate this one since it's mostly "internal" API

Benchmark from https://github.com/denoland/deno/pull/20730 with addition of structuredClone many objects to show the performance hit.
Deno.bench("structuredClone object", () => {
  structuredClone({ foo: "bar" });
});

Deno.bench("structuredClone transferables", () => {
  const buf = new Uint8Array([97]);
  structuredClone(buf, {
    transfer: [buf.buffer],
  });
});

Deno.bench("structuredClone many objects", (b) => {
  const array = Array.from({ length: 1000 }, (_, index) => ({ index }));
  b.start();
  structuredClone(array);
  b.end();
});

This PR with v8::String::new:
% ./deno-6b5fac477 bench bench_structuredClone.js
cpu: Apple M1
runtime: deno 1.38.3 (aarch64-apple-darwin)

file:///Users/lrowe/devel/deno/bench_structuredClone.js
benchmark                          time (avg)        iter/s             (min … max)       p75       p99      p995
----------------------------------------------------------------------------------- -----------------------------
structuredClone object            980.31 ns/iter   1,020,081.8 (966.96 ns … 993.25 ns) 984.45 ns 993.25 ns 993.25 ns
structuredClone transferables       2.11 µs/iter     473,489.7      (2.08 µs … 2.2 µs)   2.12 µs    2.2 µs    2.2 µs
structuredClone many objects      337.97 µs/iter       2,958.8 (322.62 µs … 690.04 µs) 337.92 µs 443.17 µs 468.96 µs

This PR with v8::String::new_external_onebyte_static:
% ./deno-8682cf494 bench bench_structuredClone.js
cpu: Apple M1
runtime: deno 1.38.3 (aarch64-apple-darwin)

file:///Users/lrowe/devel/deno/bench_structuredClone.js
benchmark                          time (avg)        iter/s             (min … max)       p75       p99      p995
----------------------------------------------------------------------------------- -----------------------------
structuredClone object              1.07 µs/iter     935,048.9     (1.03 µs … 1.41 µs)   1.08 µs   1.41 µs   1.41 µs
structuredClone transferables       2.14 µs/iter     467,981.1     (2.11 µs … 2.25 µs)   2.14 µs   2.25 µs   2.25 µs
structuredClone many objects      387.88 µs/iter       2,578.1   (366.58 µs … 1.91 ms) 383.67 µs  495.5 µs 563.25 µs

Current main at base commit:
% ./deno-d65a29794 bench bench_structuredClone.js
cpu: Apple M1
runtime: deno 1.38.3 (aarch64-apple-darwin)

file:///Users/lrowe/devel/deno/bench_structuredClone.js
benchmark                          time (avg)        iter/s             (min … max)       p75       p99      p995
----------------------------------------------------------------------------------- -----------------------------
structuredClone object            856.37 ns/iter   1,167,716.9 (831.56 ns … 874.13 ns) 860.18 ns 874.13 ns 874.13 ns
structuredClone transferables       2.12 µs/iter     471,814.7     (2.08 µs … 2.18 µs)   2.14 µs   2.18 µs   2.18 µs
structuredClone many objects      232.64 µs/iter       4,298.5 (219.08 µs … 586.75 µs) 231.92 µs 309.62 µs 328.96 µs

With the benchmark showing 6x faster usage of host objects vs 50% slower structuredClone of many objects I wonder if we can minimize the structuredClone performance penalty when dealing with many objects.
I could try looking up the Deno.core.hostObject symbol once as a v8::Global then use it per is_host_object invocation.
In addition to the code from this PR in is_host_object called per object there is also the code in the rusty_v8 wrapper which creates the scope here: https://github.com/denoland/rusty_v8/pull/1322/files#diff-d6cd4105f704c4d4e4deeb302ad57c0a59152e1abb911f1fe738954de3761295R60-R72
Does that scope object need to be created per invocation of is_host_object or could it be created once and reused?

So stashing the symbol global in the serializer cuts out most of the overhead for many objects. Benchmark added above, it's about ~12% hit which seems acceptable given the much larger speed up for working with host objects.

I think this is ready to merge now. I've tweaked it so that the global symbol is only looked up in op_serializer and not op_deserializer.

Thanks @bartlomieju! Note that https://github.com/denoland/deno/pull/21358 will need to be merged when deno's deno_core dependency is updated since createHostObject has been removed.

Yup, I'll cut another release this week


fix build failure on Windows

Hey Felix :) Small fix for the tool, maybe some Windows users exist out there.
error was:
.\common.go:75: cannot use syscall.Stdout (type syscall.Handle) as type int in argument to terminal.IsTerminal
found solution here:
https://github.com/golang/go/issues/12978#issuecomment-149035393
tested both terminal and non terminal :)
$ ./kt consume -pretty -topic WordsWithCountsTopic
{
"partition": 0,
"offset": 0,
"key": "",
"value": "1"
}
$ ./kt consume -pretty -topic WordsWithCountsTopic > x
$ cat x
{"partition":0,"offset":0,"key":"","value":"1"}

hey misha! :)
what a weird case - thanks for looking into it and providing a solution!


Cloud Code with npm packages

Hi everyone. Sorry if this is a really noob question but I just don't know how to proceed.
I want to connect my cloud code with third party modules such as Cloudinary which has an npm module. I know how to install the npm module to my heroku server. What I don't know is how to call this module trough Cloud Code.
I found an old tutorial for the old Cloud Code where they call the mailgun module like this
var client = require('cloud/myMailModule-1.0.0.js') client.initialize('myDomainName','myApyKey')
and then they call the client functions. Does it work now the same way? I'm really lost in this topic since I'm completely new to servers, and node.js
I would really appreciate if someone can point me to the right direction
Thanks in advance, and sorry for my bad english

The same way should work just fine. If you run into errors, make sure the npm module you are require ing is in your package.json.


Is it possible to add a custom XlsxError

Feature Request
XlsxError::form_str("custom XlsxError")

Hi,
That is a good suggestion. I'll add that.
It would look something like this:
use rust_xlsxwriter::XlsxError;

fn main() -> Result<(), XlsxError> {
    Err(XlsxError:: CustomError("Some custom error message".to_string()))
}

With output:
Error: CustomError("Some custom error message")

Is that what you are looking for?

Yes this looks great thank you

I've added a XlsxError::CustomError(String) enum to main. It will be in the next release (v0.61.0).

This is now upstream in the v0.61.0 crate.


Add an option for simple setups

I have been using this to mark outgoing interfaces consistently so that I can write portable pf.conf fragments for container networking. For simple setups where there is a single FIB and the same interface for v4 and v6, if would be nice if there was an option to simplify the group naming to just 'egress' similar to OpenBSD.

I can implement shorter group by removing fib0 if only one fib exists, but I'm afraid v4/v6 has to stay. Imagine the situation where v4 and v6 egress is the same and having only "egress" is fine. But then for some reason, your v6 default route changes so that v4 and v6 egress differ. There is no way to tell PF "hey, when you say egress I will know if it's v4 or v6".
Anyway, I'll start with removing fib0 and let's see what else we can do.

It's implemented now without "fib0". Can you compile it from git and let me know if it works for you, too?

What I think would be good is to add like "-p 4" or "-p 6" to watch only for ipv4/ipv6. That way "v4/v6" from the start would be lost and if there's only one fib, then fib0 would be lost, leaving you only with "egress".  I will have to research it a bit, but what do you think about that? I mean, in that case every user could configure it the way they want.

I added -p and documented it in man page. Is that sufficiently good?

I guess that would probably work for my setup where both default routes are on the same interface. I'm still not quite understanding the problem with putting the interface in 'egress' as well as egress. Having an interface in multiple groups seems to work well:
ifconfig lan0.42
lan0.42: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 9000
        ...
	groups: vlan v4egress v6egress

I'm just suggesting to add egress as well as v4egress and v6egress to support simple setups without losing the ability to distinguish different v4 and v6 interfaces.

Anyway, for now, something like 'egress-monitor -p 4' will be fine for me and probably for many others.

When you get around to updating the port, I guess we need a way to specify flags for the egress-monitor command line as well.

Updated port with https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268117. The way to add options is to add egress_monitor_flags="-p 4" in rc.conf.


Datepicker popup now honors locale and pickerLocaleOverrides

Datepicker popup items now respect locale format
Fixed a bug in zoom calendar mapping for datetime datepicker
Fixed 'es' locale for consistency

(*) Partially addresses #164
Before submitting a pull request, please make sure you have at least performed the following:

[X] read and followed the CONTRIBUTING.md guide.
[X] linted, built and tested the changes locally.
[X] added/updated any applicable API documentation.
[X] added/updated any applicable demos.

Thank you for the PR 🎉 will get this looked at properly tomorrow 😄


Square order state is still OPEN after redirecting from checkout

Contacted Square Support to troubleshoot, case 72454804

This is due to a mandatory OrderFulfillment being associated with the order. Square developer support indicated that there is no way to prevent this at this time.


[Bug] Average judge seen stat on admin panel is not updating

Expected Behavior
It should show the average number of times an active judge has seen a project
Current Behavior
It shows a big fat 0
Describe the Bug
No response
Steps to Reproduce

Have judges see projects
Go to admin panel
Judge average seen is still 0 aaaaaaaaaaaaaa

What device are you seeing this issue on?
No response
What browser are you seeing this issue on?
No response
Possible Solutions
I don't know if this is because of the aggregation or something in the frontend but it should be a relatively easy fix...

Resolved by #116


Link Owner Setup Help Center Article

What is this feature about? (1 sentence)
Reference Help Center article about Safe owner setup considerations during onboarding
Why is it needed? What is the value? For whom do we build it?
User might need some additional guidance when settling on their specific owner setup during Safe creation. We recently created a Help Center article to give more background to this evaluation. It would be helpful to link to this article during the Safe creation flow.
High-level overview of the feature

Link to this help center article in the second step of the Safe creation flow: https://help.gnosis-safe.io/en/articles/4772567-what-gnosis-safe-setup-should-i-use
Suggested text: "Learn about which Safe setup to use."

@posthnikova this one might be something for the next web release since it's a smaller fix. Could you please create screen, how/where you would position that link to the help center article?

@posthnikova this one might be something for the next web release since it's a smaller fix. Could you please create screen, how/where you would position that link to the help center article?

I think it's logical to add a link after 'the more confirmations required, the more secure is your Safe'.

I think it's logical to add a link after 'the more confirmations required, the more secure is your Safe'.

This makes sense to me, I think it looks good like that.

This makes sense to me, I think it looks good like that.


Exporting Spec with (2) notes freezes export; no spec is exported (Sketch 52.6)

Looks like bug #224 is back in Sketch 52.6, unfortunately. The export just hangs forever with these two notes (see screenshot)

ive found ungrouping the note-box rectangle should fix this

Is there no other fix than to ungroup the notes? It's such a round-about way of doing it. Aka, any edits on the code that can negate this duplicate shape?


RD2: Disable the RD Next Payment Date Customizable Rollup during enablement

When Enhanced Recurring Donations is enabled, disable the RD Next Payment Date Rollup

Critical Changes
Changes
Issues Closed
New Metadata
Deleted Metadata

**lurch: attach W-037191

Tracking W-037191

Thanks @RadSFDeveloper. Changes made.

QE testing for this PR is complete.  Tests have passed.
For further testing details and comments, see:
https://foundation.lightning.force.com/lightning/r/agf__ADM_Work__c/a2x1E000001Ho4cQAC/view
https://salesforce.quip.com/aCMIAa6HyjpL
Merging PR and setting WI status to Closed.


GAUD-292 - Use new release token

The brightspace-bot and D2L_GITHUB_TOKEN are no longer needed for release workflows. Instead, we have a new D2L_RELEASE_TOKEN that has the ability to bypass the repo ruleset (configured in https://github.com/Brightspace/repo-settings/pull/1602) and org-level ruleset.
Before merging, I will:

Confirm the new ruleset matches the old branch protection rule before deleting it
Remove brightspace-bot as a repo contributor
Confirm the D2L_RELEASE_TOKEN is available and remove this repo's access to D2L_GITHUB_TOKEN

If you need to make a cert or hotfix, this will need to be backported to the 20.24.02 and 20.24.01 release branches.

Not updating this repo to node 20 at this time - will add to list blocking semantic-release version bump.


Enhanced styling and interaction support for mentions, hashtags, and URLs

Issue Description
Summary
I propose adding enhanced styling and interaction capabilities for specific text patterns within ReadMoreText, such as mentions, hashtags, and URLs. This feature would allow developers to customize the appearance of these elements and define custom actions when they are tapped, such as navigating to a user's profile when a mention is clicked.
Use Case
In many applications, text content includes special elements like mentions (<@userId>), hashtags (#topic), and URLs that users expect to interact with. For example, tapping on a mention might navigate to that user's profile page, and clicking a hashtag could show related content. Additionally, these elements often require distinct styling to stand out from the surrounding text, signaling to users that they are interactive.
Proposed Solution
Introduce a mechanism to define custom styles and tap actions for mentions, hashtags, and URLs within the ReadMoreText widget. This could be achieved through a list of Annotation objects (or a similar construct) where each annotation includes:

A RegExp to match the specific pattern (mention, hashtag, URL).
A TextSpan Function that allows developers to customize the style and define tap actions for matched text.

This approach would not only enhance the visual differentiation of these special text elements but also enable developers to implement interactive behaviors, enhancing user engagement with the content.
Handling Modified Data
An important aspect of this feature is handling cases where the displayed text is modified, such as converting a mention from <@userId> to a readable username (e.g., UserA). The solution should gracefully support such transformations, ensuring that the custom styles and interactions are preserved.
Impact
Implementing this feature would significantly increase the utility and flexibility of the ReadMoreText widget, making it a more powerful tool for developers creating content-rich applications.

FYI, this is available in PR #54
https://github.com/jonataslaw/readmore/assets/8436039/3c7fc530-e550-4636-8de7-367cfe6ba9bd


Set Rerun flag when setting RerunOf

https://github.com/nvborisenko/reportportal-extensions-ci/blob/9503a4d8b40355ad552807551fcf27ca74541120/src/ReportPortal.Extensions.CI/Providers/AzureDevOpsProvider.cs#L47
Here we need to set ReRun flag as well. Breaking changes are coming in Shared packade.
https://github.com/reportportal/commons-net/issues/102

Done in 0.1.2


Added appveyor and travis badges

Pull Request Test Coverage Report for Build 300

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 73.847%

Totals

Change from base Build 299:
0.0%

Covered Lines:
2081

Relevant Lines:
2818

💛  - Coveralls


Feature request: Detect the number of gpu devices

Related to issue #971, it would be useful to have functionality to detect the number of gpu devices on a machine. I am thinking of something like torch.cuda.device_count(): https://pytorch.org/docs/stable/cuda.html#torch.cuda.device_count.

jax.local_device_count() implements this.

Awesome! I will close the issue.


Environment Comonad

Need this for Eric's project. Implement the holes in https://github.com/maxsnew/multi-poly-cats/blob/main/Cubical/Categories/Comonad/Instances/Environment.agda .

completed in https://github.com/maxsnew/multi-poly-cats/commit/05a58210080752a1765aaf0e2451cb27ba2eaed7


change in btn class not applying

This is the default button code in jquery.tableedit.js file:
buttons: {
                edit: {
                    class: 'btn btn-sm btn-default',
                    html: '',
                    action: 'edit'
                },

while changing the above code to this code in jquery.tableedit.js file, the changes are not being implemented:
buttons: {
                edit: {
                    class: 'btn btn-sm btn-warning',
                    html: '',
                    action: 'edit'
                },

Is this a some kind of issue or am I missing something?

Oh, It seems I was doing it wrong and now I have fixed it.
I shouldn't have changed anything in the jquery.tableedit.js file but instead I would have to use in my page where I am using this script.


vscode-extensions.just: init at 2.0.0

Motivation for this change
Add a VSCode extension for just
Things done

Built on platform(s)

[N/A] x86_64-linux
[N/A] aarch64-linux
[N/A] x86_64-darwin
[N/A] aarch64-darwin

[N/A] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[N/A] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[N/A] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[N/A] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[N/A] (Package updates) Added a release notes entry if the change is major or breaking
[N/A] (Module updates) Added a release notes entry if the change is significant
[N/A] (Module addition) Added a release notes entry if adding a new NixOS module
[N/A] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

There is a recent change that moved misc/vscode-extensions to applications/editors/vscode/extensions (#160344), do you mind update your PR to resolve the merge conflict?

@bobby285271 should be good to go

is this PR good to go? just making sure I'm not holding this back

@ofborg build vscode-extensions.skellock.just

great, thanks for the feedback!
just for anyone stumbling upon this in the future:

I know the extension is unmaintained, it is nevertheless functional as of today
I looked for active forks, none seem to be maintained either. I might make a fork of my own soon-ish


change fixImports into public FixImports

Pull request for issue https://github.com/golang/go/issues/23782
Makes imports/ library FixImports function public. Lets you fix imports on a file's AST instead of only working with files.

I signed it!


R.I.P. manual-update CURRENT_YEAR

Fix #1681 , auto-update the CURRENT_YEAR constant using Rails helper.

Can we make it a method on the main Tfpullrequests::Application class? https://github.com/24pullrequests/24pullrequests/blob/master/config/application.rb
That way I won't need to restart the app on new year's eve to get it to update the year

@andrew
My PR Fix #1681.
Your suggestion is another improvement point, would you add another Issue?
I can not self-assign because I do not have permission, but I will push PR :)

Ok cool, will merge this now


Question about handling EOF from registry

Bug report:

Greetings from Agoda! We're facing an issue with Dragonfly v2.0.3. When a network problem occurs and requests to our Harbor registry only returns EOF, it appears Dragonfly is caching that EOF response. This results in an unexpected EOF error anytime users attempt to pull that image layer.
Error displayed:
Failed to pull image "reg-as.agodadev.io/papi/content/content-platform/release:0.8.555": rpc error: code = Unknown desc = failed to pull and unpack image "reg-as.agodadev.io/papi/content/content-platform/release:0.8.555": failed to read expected number of bytes: unexpected EOF

Could you please help clarify:

Does Dragonfly refrain from caching a layer if EOF is returned from the registry?
Will upgrading to the latest version resolve this issue?

Expected behavior:
Dragonfly should not cache if EOF is returned from the registry.

How to reproduce it:
Create a scenario of network instability, such as blocking access from Dragonfly nodes to registry nodes.

Environment:

Dragonfly version: 2.0.3
OS: Centos 7
Kernel (e.g. uname -a): Linux 3.10.0-1160.53.1.el7.x86_64 #1 SMP Fri Jan 14 13:59:45 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Others: -

If any information needed please let me know.
Thank you for creating and maintaining such an excellent product.
Merry Christmas 🎄 and Happy new year 🥳

I also encountered the same problem, how to solve it?

I also encountered the same problem, how to solve it?

Hi, the version you are using is outdated. Please try using the latest version. If you encounter any issues adapting to the new version, feel free to ask at any time~
@supakornbabe @MouseSun846

I also encountered the same problem, how to solve it?

Hi, the version you are using is outdated. Please try using the latest version. If you encounter any issues adapting to the new version, feel free to ask at any time~ @supakornbabe @MouseSun846

The version I am using is V2.16.0.

Could you provide the tag link under https://github.com/dragonflyoss/Dragonfly2/releases?
If you still encounter this issue under v2.1.63, please provide more information(how to reproduce the issue) please~


Add check for when object.inspect is frozen

There was a very intermittent problem wherein when an object's inspect returned a frozen string, AP would blow up because #<< would attempt to modify it.
I added a call to #dup to reset the frozen status but only in cases where the string is in fact frozen, so the performance impact should be negligible.

This should be fixed in the latest v1.0.1, at least the specs pass ;-)

Thanks Michael.  I'll give it a shot!


fixing typos and formatting issues

fixes to formatting and typos

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


Can't transition from encryption_key to byok_key[0].id without cluster recreation

I'm upgrading my own modules to comply with this guide: https://registry.terraform.io/providers/confluentinc/confluent/latest/docs/guides/version-2-upgrade
I currently have a dedicated AWS cluster with encryption. I'd like to continue managing that with terraform so I wanted to import the (already in use) KMS key, and link that to the existing cluster (so I expect 0 changes while doing that)
I ran:
confluent byok list

and I couldn't see the KMS Key I always used, so I ran:
confluent byok create "arn:aws:kms:us-east-1:xxxxxx:key/xxxxx"

With the exact same ARN I'm using.
Then I imported:
terraform import 'module.confluent-kafka-cluster["misc-use1"].confluent_byok_key.byok_key[0]' 'cck-xxxx'

and ran a plan, but Terraform wants to remove everything.
Why can't we keep managing this for existing clusters with Terraform? this change alongside the schema registry change, seems to be removing more and more power from IaC.

@Israphel thanks for creating the issue!
Did you get a chance to look at https://github.com/confluentinc/terraform-provider-confluent/issues/398?

I have seen all the issues related to this but I don't agree with the answer. In infra as code, the code has to match the infra, you want us to remove part of the code instead of providing backward compatibility with existing clusters.
specially this:
Unfortunately, in-place updates are not supported in TF because they are not supported at the API level.
Both the provider and the API belong to Confluent, as a company. There're no excuses to make them incompatible.
About the schema registry, you can read me here: https://github.com/confluentinc/terraform-provider-confluent/issues/399#issuecomment-2226251214
I gonna talk with confluent about this, in our monthly sync, because so far the 2.0.0 provider is a disaster.

I have seen all the issues related to this but I don't agree with the answer. In infra as code, the code has to match the infra, you want us to remove part of the code instead of providing backward compatibility with existing clusters.

@Israphel, there's an update from our side: we talked to the backend team, and we're considering reverting our deprecation change. More specifically:

When creating new Kafka clusters, you should use the byok_key[0].id attribute instead of the dedicated[0].encryption_key attribute, since the latter is no longer supported in the Confluent Cloud API's POST cmk/v2/clusters request.

However, for existing instances of the confluent_kafka_cluster resource, dedicated[0].encryption_key is still supported as a read-only attribute.

In short, your existing instances of the confluent_kafka_cluster resource will not require any updates when using the v2.0.0 version of the TF Provider, and you'll no longer see deprecation messages. Let us know if that helps!

even tho that's better than before, it's still not ideal.
Why? because if I update my terraform module for kafka creation to comply with 2.0.0 (which I already did), then existing clusters can't transition to byok_key, and they will always be in a legacy state.
The ideal move here is being able to import an existing key, and the cluster should see no changes.
The same happened with s3_bucket back in aws 3.x.x, where every single config was moved into its own terraform resoruce, and existing buckets were not affected after doing the imports.
Below are fragments of my Terraform module:
# main.tf

# Confluent Kafka cluster
resource "confluent_kafka_cluster" "kafka_cluster" {
  display_name = var.name
  availability = var.type == "basic" ? "SINGLE_ZONE" : var.availability
  cloud        = var.cloud
  region       = var.region

  dynamic "basic" {
    for_each = var.type == "basic" ? [true] : []
    content {}
  }

  dynamic "standard" {
    for_each = var.type == "standard" ? [true] : []
    content {}
  }

  dynamic "dedicated" {
    for_each = var.type == "dedicated" ? [true] : []
    content {
      cku = var.type != "dedicated" ? null : var.cku
    }
  }

  dynamic "byok_key" {
    for_each = anytrue([local.encrypted.aws, local.encrypted.azure]) ? [true] : []
    content {
      id = one(confluent_byok_key.byok_key[*].id)
    }
  }

  dynamic "network" {
    for_each = var.type == "dedicated" && var.network_id != null ? [true] : []
    content {
      id = var.network_id
    }
  }

  environment {
    id = var.environment_id
  }
}

# Confluent encryption key
resource "confluent_byok_key" "byok_key" {
  count = anytrue([local.encrypted.aws, local.encrypted.azure]) ? 1 : 0

  dynamic "aws" {
    for_each = local.encrypted.aws ? [true] : []
    content {
      key_arn = var.kms_key_arn
    }
  }

  dynamic "azure" {
    for_each = local.encrypted.azure ? [true] : []
    content {
      tenant_id      = var.tenant_id
      key_vault_id   = var.key_vault_id
      key_identifier = var.key_identifier
    }
  }
}

# locals.tf

locals {
  # Determines encryption status
  encrypted = {
    aws   = alltrue([var.type == "dedicated", var.cloud == "AWS", var.kms_key_arn != null])
    azure = alltrue([var.type == "dedicated", var.cloud == "AZURE", var.tenant_id != null, var.key_vault_id != null, var.key_identifier != null])
  }
}

So, as explained before, I can't transition my confluent repo to my updated module because the plan wants to make a cluster recreation.
Please consider supporting the byok import.

@petrkarytka @Israphel could you try to update TF Provider to 2.0.0 by following this guide and then reimport your Kafka clusters and see whether it resolves terraform plan issue?
Your new TF config should still include encryption_key attribute for old Kafka clusters and it should not use byok { id } block:

Thank you!

@linouk23 I don't have any issues with terraform plan  but it leads to maintaining two versions of the cluster module - one for clusters that were deployed with encryption_key and one for clusters with byok_key. This process would be significantly easier and faster if it was possible to update the old clusters to start using byok_key somehow

@petrkarytka

I don't have any issues with terraform plan

Nice!

It leads to maintaining two versions of the cluster module - one for clusters that were deployed with encryption_key and one for clusters with byok_key. This process would be significantly easier and faster if it was possible to update the old clusters to start using byok_key somehow

We fully agree with this statement 💯. However, unfortunately, based on our conversation with the backend team, updating the old clusters to start using byok_key may be very challenging at this point.

Your new TF config should still include encryption_key attribute for old Kafka clusters and it should not use byok { id } block:

That's not what I want. Existing clusters should be able to move to the new resource, because I'm not changing the encryption key, it still is the same KMS ARN it always had. You changed some naming internally, not my fault.