Error service camera snapshot required width and height

Version of the custom_component
0.9.23
Configuration
Describe the bug
When using service camera snapshot I get the an error.
Debug log
Logger: homeassistant.helpers.script.websocket_api_script
Source: components/camera/init.py:751
First occurred: 12:14:15 (1 occurrences)
Last logged: 12:14:15
websocket_api script: Error executing script. Unexpected error for call_service at pos 1: async_camera_image() missing 2 required positional arguments: 'width' and 'height'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 371, in _async_step
await getattr(self, handler)()
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 571, in _async_call_service_step
await service_task
File "/usr/src/homeassistant/homeassistant/core.py", line 1492, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1527, in _execute_service
await handler.job.target(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 213, in handle_service
await self.hass.helpers.service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 658, in entity_service_call
future.result()  # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 843, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 695, in _handle_entity_call
await result
File "/usr/src/homeassistant/homeassistant/components/camera/init.py", line 751, in async_handle_snapshot_service
image = await camera.async_camera_image()
TypeError: async_camera_image() missing 2 required positional arguments: 'width' and 'height'
Logger: homeassistant.components.websocket_api.http.connection
Source: components/camera/init.py:751
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 12:14:15 (1 occurrences)
Last logged: 12:14:15
[547612669888] Error handling message: Unknown error
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 25, in _handle_async_response
await func(hass, connection, msg)
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 525, in handle_execute_script
await script_obj.async_run(msg.get("variables"), context=context)
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1219, in async_run
await asyncio.shield(run.async_run())
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 353, in async_run
await self._async_step(log_exceptions=False)
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 371, in _async_step
await getattr(self, handler)()
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 571, in _async_call_service_step
await service_task
File "/usr/src/homeassistant/homeassistant/core.py", line 1492, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1527, in _execute_service
await handler.job.target(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 213, in handle_service
await self.hass.helpers.service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 658, in entity_service_call
future.result()  # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 843, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 695, in _handle_entity_call
await result
File "/usr/src/homeassistant/homeassistant/components/camera/init.py", line 751, in async_handle_snapshot_service
image = await camera.async_camera_image()
TypeError: async_camera_image() missing 2 required positional arguments: 'width' and 'height'

The IPC-A26 does not take a picture. Error in log
Logger: homeassistant.components.automation.nova_automatizace_3
Source: components/camera/__init__.py:751
Integration: Automatizace (documentation, issues)
First occurred: 22:35:44 (2 occurrences)
Last logged: 22:35:44

Alarm aktivace/foto kamera: Error executing script. Unexpected error for call_service at pos 1: async_camera_image() missing 2 required positional arguments: 'width' and 'height'
While executing automation automation.nova_automatizace_3
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 371, in _async_step
    await getattr(self, handler)()
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 571, in _async_call_service_step
    await service_task
  File "/usr/src/homeassistant/homeassistant/core.py", line 1492, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1527, in _execute_service
    await handler.job.target(service_call)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 213, in handle_service
    await self.hass.helpers.service.entity_service_call(
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 658, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 843, in async_request_call
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 695, in _handle_entity_call
    await result
  File "/usr/src/homeassistant/homeassistant/components/camera/__init__.py", line 751, in async_handle_snapshot_service
    image = await camera.async_camera_image()
TypeError: async_camera_image() missing 2 required positional arguments: 'width' and 'height'

A workaround for this error is to create a separate camera like this.

platform: generic
name: CAMERA
still_image_url: http://192.168.X.X/cgi-bin/snapshot.cgi
stream_source: rtsp://XXX:XXX@192.168.X.X:554/cam/realmonitor?channel=1&subtype=0
verify_ssl: false
username: XXX
password: XXX
authentication: digest

Same problem found after the latest update. It was working well in the previous release
`Logger: homeassistant.components.websocket_api.http.connection
Source: components/camera/init.py:751
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 9:38:02 PM (3 occurrences)
Last logged: 9:40:48 PM
[140174619042864] async_camera_image() missing 2 required positional arguments: 'width' and 'height'
[140174501011856] async_camera_image() missing 2 required positional arguments: 'width' and 'height'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 185, in handle_call_service
await hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 1492, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1527, in _execute_service
await handler.job.target(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 213, in handle_service
await self.hass.helpers.service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 658, in entity_service_call
future.result()  # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 843, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 695, in _handle_entity_call
await result
File "/usr/src/homeassistant/homeassistant/components/camera/init.py", line 751, in async_handle_snapshot_service
image = await camera.async_camera_image()
TypeError: async_camera_image() missing 2 required positional arguments: 'width' and 'height'
`

Same error here, started from HA version 2021.9.7.
TypeError: async_camera_image() missing 2 required positional arguments: 'width' and 'height'

same error for me new set up

Check out here under breaking changes -> scroll down to -> custom integration: camera's
https://www.home-assistant.io/blog/2021/09/01/release-20219/#breaking-changes
I think this should be changed and it's working again?

detailed here:
[https://github.com/home-assistant/core/pull/53835]

Would be nice if this can be fixed soon.

My plan is to work on this over the weekend

@GeitjeG Thanks for that. Now I can reproduce this. Digging deeper now for a fix.

This should do it - https://github.com/rroller/dahua/commit/83c09300098b6e446d218a60280a7d5babfd2c6f
Try 0.9.24
https://github.com/rroller/dahua/releases/tag/0.9.24

I can confirm the snapshot is working again with 0.9.24. Thanks!

it's working again. Thanks!

Great, it's working again! Thanks for your efforts.


editTemplate on row change error throw $inputFrom was not an function

when i first load the grid and click on the row its works but after click on the second row $inputFrom.change function throw erorr i.e, $inputFrom was not an function, please suggest whats an issue?
editTemplate: function (value) {
debugger;
var $inputFrom = jsGrid.fields.timeField.prototype.editTemplate.call(this, value);
$inputFrom.change(function () {
var selectedValue = $(this).val();
validFrom2 = selectedValue;
});
return $inputFrom;
}

The field on which i am applying the edittemplate is date calendar field.


Transaction Rejected

I frequently getting "Transaction Rejected:250 - system error.(1. Please contact customer service.)" on doing transaction. What is the cause of this error?

The integration backend and Payment Engine is connected to our Visa and Mastercard test simulators.
These receive updates, configuration changes etc. overtime and it happens unfortunately that they are down occasionally - in this case  you will get 250 - system error.
You can try to run your test with different card issuer - so e.g. If you get the failures on Mastercard card then try to use Visa instead please.

Temporary disruption of test domain


[projmgr] Add AC5 to common.schema.json

Will there be a AC5 compiler option for a csolution.yml since the AC<IP_ADDRESS>.cmake is already there?

No, the AC<IP_ADDRESS>.cmake is a left-over from the early versions of cbuildgen where AC5 was supported by the cprj format. Since Arm Compiler AC5 is no longer supported, we have decided against adding it to csolution.


1.20.1 image crashes with: errors parsing config: exec: "gcloud": executable file not found in $PATH

Bug Description
Our testing GKE cluster just pulled in the gcr.io/cloudsql-docker/gce-proxy:1.20.1-alpine image (we see the same problem with the buster variant), and all deployments are failing with:
2021/03/04 23:22:07 errors parsing config:
Get "https://sqladmin.googleapis.com/sql/v1beta4/projects/<project id>/instances/<instance>?alt=json&prettyPrint=false": exec: "gcloud": executable file not found in $PATH

Example code (or command)
Auth via workload identity.
      - name: cloud-sql-proxy
        # It is recommended to use the latest version of the Cloud SQL proxy
        # Make sure to update on a regular schedule!
        image: gcr.io/cloudsql-docker/gce-proxy:1.20.1-alpine
        command:
        - "/cloud_sql_proxy"
        # If connecting from a VPC-native GKE cluster, you can use the
        # following flag to have the proxy connect over private IP
        - "-ip_address_types=PRIVATE"
        # Replace DB_PORT with the port the proxy should listen on
        # Defaults: MySQL: 3306, Postgres: 5432, SQLServer: 1433
        - "-instances=<project>:<region>:<name>=tcp:5432"
        securityContext:
          # The default Cloud SQL proxy image is based on distroless, which
          # runs as the "nonroot" user (uid: 65534) by default.
          runAsNonRoot: true

Environment

OS type and version: GKE 1.18.15-gke.1102 with cos_containerd
Cloud SQL Proxy version (./cloud_sql_proxy -version): 1.20.1

Possibly related

#649

Thanks for opening the issue. We're working on a fix.
So far, I was able to reproduce the error with the distroless version of the image using Docker locally. Haven't tried it with GKE, but when I run the following command I get the same error.
docker run -it --rm -v ~/.config/:/root/.config/ {latest image} /cloud_sql_proxy -instances={cloud sql instance name}

Using the previous version of the image works fine.
So far, we think the issue is differing error behavior between go/exec and the execabs version of exec

got the same error here, and I can see from my cloud build log the only difference between my previous success build is the binary file size changed for cloudsql-proxy
i'm using name: gcr.io/cloud-builders/npm:node-10.10.0 as build image, basically download the binary and start the proxy. I then used the proxy to connect to my cloud sql for database migration.
my log:
converted 'https://dl.google.com/cloudsql/cloud_sql_proxy.linux.amd64' (ANSI_X3.4-1968) -> 'https://dl.google.com/cloudsql/cloud_sql_proxy.linux.amd64' (UTF-8)
--2021-03-05 11:35:51--  https://dl.google.com/cloudsql/cloud_sql_proxy.linux.amd64
Resolving dl.google.com (dl.google.com)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to dl.google.com (dl.google.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 14816582 (14M) [application/octet-stream]
Saving to: './ops/cloud_sql_proxy'

     0K .......... .......... .......... .......... ..........  0% 30.4M 0s
    50K .......... .......... .......... .......... ..........  0% 36.1M 0s
 14450K .......... .........                                  100% 79.5M=0.2s

2021-03-05 11:35:51 (58.5 MB/s) - './ops/cloud_sql_proxy' saved [14816582/14816582]

2021/03/05 11:35:52 current FDs rlimit set to 1048576, wanted limit is 8500. Nothing to do here.
2021/03/05 11:35:52 errors parsing config:
	Get "https://sqladmin.googleapis.com/sql/v1beta4/projects/xxxxxxx/instances/us-central1~cotreat?alt=json&prettyPrint=false": exec: "gcloud": executable file not found in $PATH

We suspect that #649 was a red herring, and that it was actually #648 that inadvertently caused us to start trying to rely on gcloud credentials even if the initial gcloud token fails. We've got a couple of solutions in the pipeline, but are trying to make sure we've run a couple of longer tests at the moment.


http: error: SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed

we should have an option to ignore this

Does --verify no work?

It does. I overlooked it. Sorry.
Thanks


Add label smoothing, z_loss and ignore <=0 tokens in loss calculation

Train step loss function makes use of compute_weighted_cross_entropy_and_accuracy() an extended version of compute_weighted_cross_entropy() that also calculates accuracy. This function supports label smoothing and z_loss.
The eval step loss function still makes use of cross_entropy_loss_and_accuracy(), when calling it, the loss function also incorporates (in)validity of label tokens if they are <=0, together with the attention masks.

@erfanzar I just checked output of the first model I trained on it and it produces garbage.. (even though loss was quite nice). It could be anywhere, labels in the dataset, not attending on eos token, shifted wrong..
I think its best to revert this commit and I'll try to figure out where its failing later. Apologies for the noise!

@yhavinga that's fine and thank for reporting.

@yhavinga  ;\ seems like that's fine if you passed all of the tests you can make a pull request and I'll optimize that (I'll use jax.lax  instead of some other APIs, and add some TPU Pallas calls) and if you want we can update beta branch and work on that so we can simply just train some models and test

@erfanzar all tests have turned out ok yay! - I need to rebase next (my tests and fixed code was all based on the main branch from ~6 feb). Is it your preference that I rebase on the beta branch instead of main?

yes cause im about to add new Trainers and Change how loss functions kinda work so it would nice if you could rebase that on beta

@erfanzar so I have two branches with the fixed attention_mask shifting

https://github.com/yhavinga/EasyDeL/tree/ignore_token_label_smooth_z_loss -- on main branch from 7 feb
https://github.com/yhavinga/EasyDeL/tree/beta_ignore_token_label_smooth_z_loss -- on the beta branch

The first one is all ok, everything working.
The second one I get errors if I run e.g. the python_test/easy_causal_language_model_trainer_test.py -- this gives errors  also without my patch.
Traceback (most recent call last):
  File "/home/yeb/Developer/yhavinga/zuchtax/EasyDeL/lib/python/EasyDel/modules/flax_modelling_utils.py", line 438, in block_wise_ffn
    inputs = rearrange(inputs, 'b (c n) d -> b c n d', c=chunk_size)
  File "/home/yeb/Developer/yhavinga/zuchtax/venv/lib/python3.10/site-packages/einops/einops.py", line 483, in rearrange
    return reduce(cast(Tensor, tensor), pattern, reduction='rearrange', **axes_lengths)
  File "/home/yeb/Developer/yhavinga/zuchtax/venv/lib/python3.10/site-packages/einops/einops.py", line 420, in reduce
    raise EinopsError(message + '\n {}'.format(e))
einops.EinopsError:  Error while processing rearrange-reduction pattern "b (c n) d -> b c n d".
 Input tensor shape: (1, 128, 128). Additional info: {'c': 1024}.
 Shape mismatch, can't divide axis of length 128 in chunks of 1024

maybe it is due to a mismatch in a package?
$ pip freeze | grep ax
distrax==0.1.5
flax==0.7.5
jax==0.4.23
jaxlib==0.4.23
optax==0.1.8
orbax-checkpoint==0.5.0
rlax==0.1.6

@yhavinga Hello and thank you for contributing, if you think that's working correctly and it can train the model you can make a pull request again for that, and the error your getting right now is from scan_mlp and you can disable that or use lower chunks.
you can disable that with giving use_scan_mlp=False to model config or change scan_mlp_chunk_size=64<or any other value>

@erfanzar Just tested a bit on tpu-v4-8:

Branch (1) listed above: no problemo here, works as expected.
The beta branch - problems: I can't get use_scan_mlp set to False.

I'm still testing with python_test/easy_causal_language_model_trainer_test.py
When it initialized Qwen2Config, all ok with use_scan_mlp=False, until the call to super.init() is called with -**kwargs (that does NOT include use_scan_mlp) is called, then enters EasyDelPretrainedConfig and now use_scan_mlp is not passed, so set to this class's default use_scan_mlp=True.

it's ok if the loss function works for training you can re-create the functions on FJFormer then we can port that and test that on EasyDeL.

@erfanzar I'm sorry, but I don't understand. Can I reach you on a discord anywhere? E.g. JaxLLM https://discord.gg/T5c48fDT ?

@yhavinga Yes here's my discord id  citifer.
and I said you could make functional changes that you need on FJformer side, and make a new pull request or re-open this pull request and I can debug if there be any issue.


Can I use navigation without hash(# symbol)?

I'd like a hash-free navigation.
Ex:
https://localhost:8000/Counter.elm/0
https://localhost:8000/Counter.elm/1
etc. for this repo's example
I've tried to modify the Counter.elm to achieve this and failed.
toUrl count =
  "/" ++ toString count
fromUrl url =
  String.toInt (String.dropLeftt 1 url)

This will cause a dead-loop(maybe) when using elm-reactor.
When it is compiled to html, it worked partially. The feature is achieved, but the sub-path is overridden:
The compiled html is at localhost/some/path/counter.html, and when the app starts, the address will be overridden to localhost/0, localhost/1, etc. But I want it to be something like localhost/some/path/counter.html/0

duplicates: https://github.com/elm-lang/navigation/issues/3
It can be used with html routes - I do it - but you have you have to get your code perfectly correct, otherwise is crashes badly. I ended up editing the url-parser source code to read
parse : formatter -> Parser formatter a -> String -> Result String a
parse input (Parser actuallyParse) url =
  case actuallyParse (Chunks [] (String.split "/" url |> List.filter ((/=) ""))) input of

You can parse a Location however you want. All the data about the URL is in there.
In the upcoming release, this will be easier to extract with parsePath and parseHash in evancz/url-parser.
Until then, I think this question would be better for elm-discuss or the slack channel.


User Deployments do not work against MPs using DB Replica

That's a non documented Limitation see:
https://twitter.com/djammmer/status/1060903565311520768

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

ID: 6e05b125-c8e8-0eab-5b2b-2bc60fe33654
Version Independent ID: fcf9f58f-1ab5-9132-7de8-539a32b57862
Content: Management point database replicas - Configuration Manager
Content Source: sccm/core/servers/deploy/configure/database-replicas-for-management-points.md
Product: configuration-manager
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Thanks @excelsi for filing the issue. I think this should also include a note on the app deployment article


gv.WMTS zoom in causes "bounce back" behavior

Strange behavior when zooming in on a gv.WMTS slippy map where the map flickers and bounces back to less zoomed in zoom levels. See gif:

Code:
import geoviews as gv
from bokeh.models import WMTSTileSource

 gv.WMTS(WMTSTileSource(url='http://c.tile.openstreetmap.org/{Z}/{X}/{Y}.png'))

Same behavior with other tile sources. Looking in network tab, all tile image file requests are 200.
holoviews 1.9.2
geoviews 1.4.0
bokeh 0.12.11
gv.WMTS is based off of owslib.wmts's  WebMapTileService

Can you try bokeh 0.12.13?

Same behavior with bokeh 0.12.13

Damn.

I haven't reproduced this problem myself, but a colleague of mine suggests that the problem could be triggered when the map tiles reach a level where there is no further resolution available, with a fallback that is very confusing in this case.  If so, that would need to be fixed in Bokeh, not GeoViews.
My personal feeling is that when that happens, whatever map tile zoom level was last successfully retrieved should simply be zoomed up indefinitely as an image, no matter how big the pixels get. For an online map service, it makes sense to clamp the maximum zoom level, but in Bokeh, map tiles are  usually just a backdrop for the real data, and whether the map tiles are available at that resolution or not we'd still need to be able to zoom in to our real data.
@philippjfr, does this sound like a reasonable explanation of this issue?  If so, we should file this as an issue on the Bokeh site and then try to fix it.

Sounds possible, although it seems the zoom level is not nearly sufficient to be running out of resolution. I've also not been able to reproduce, so it might be worth knowing which browser this is occurring with.

I second the above, it's definitely not due to bottoming out on available zoom level tiles.
Have experienced in following browsers:

Chromium  63.0.3239.84
Firefox (Quantum) 58.0b3 (64-bit)

Sorry to resurrect this, but noticed this happening again in a recent notebook.
HoloViews: 1.11.3
GeoViews: 1.6.2
Bokeh: 1.0.4

I also am experiencing this stretchy/bouncy behavior.
bokeh                              1.1.0
geoviews                           1.6.5
datashader                         0.6.9
hvplot                             0.5.2
holoviews                          1.12.6

My best suggestion here is for HoloViews data aspect handling code to become slightly more tolerant of aspect distortion, e.g. going from 1% tolerance to 5% eliminates the bouncing for me.


fix: wrong fabric schemas

Added some comments. You had asked us to help out but I see you're diving into it pretty deeply.
Question, how is Pulumi failing here? Is it that the Terraform spec isn't matching our SwaggerHub spec or is it that the Fabric APIs are returning data that isn't in the SwaggerHub spec? Wanted to sync up on this one.

@thogarty it was related to this issue https://github.com/pulumi/pulumi-terraform-bridge/issues/1951 Pulumi tries to recreate some unmodified resources, I found that they were TypeSet fields with all subfields in the nested schema optional and computed, on the one hand, this was a bug in the pulumi-terraform-bridge plugin which seems to be solved. However, I could also observe that in those resources we were defining all fields as computed and optional some are never computed or they were required.
So taking the example below, AFAIK account_number must be required, actually is a single field in the account schema that is required. However, it is not specified as required in the SwaggerHub specs https://app.swaggerhub.com/apis/equinix-api/fabric/4.13#/SimplifiedAccount. Ideally, this should be well defined in the specs, looking for semi-automated processes to generate the Terraform provider as well as the SDKs. The first problem I see in the specs is that in some of them, the same objects are used for both the POST request and for the GET request/response, so there we cannot even distinguish when a field is read-only, which is what most of them are for the GET.

Added some comments. You had asked us to help out but I see you're diving into it pretty deeply.
Question, how is Pulumi failing here? Is it that the Terraform spec isn't matching our SwaggerHub spec or is it that the Fabric APIs are returning data that isn't in the SwaggerHub spec? Wanted to sync up on this one.

@thogarty it was related to this issue pulumi/pulumi-terraform-bridge#1951 Pulumi tries to recreate some unmodified resources, I found that they were TypeSet fields with all subfields in the nested schema optional and computed, on the one hand, this was a bug in the pulumi-terraform-bridge plugin which seems to be solved. However, I could also observe that in those resources we were defining all fields as computed and optional some are never computed or they were required.
So taking the example below, AFAIK account_number must be required, actually is a single field in the account schema that is required. However, it is not specified as required in the SwaggerHub specs https://app.swaggerhub.com/apis/equinix-api/fabric/4.13#/SimplifiedAccount. Ideally, this should be well defined in the specs, looking for semi-automated processes to generate the Terraform provider as well as the SDKs. The first problem I see in the specs is that in some of them, the same objects are used for both the POST request and for the GET request/response, so there we cannot even distinguish when a field is read-only, which is what most of them are for the GET.

I'm with you that the Fabric Specs are not ideal. We're trying to sort them out as we go along and the collaboration with the many Fabric teams doesn't always get the correct result. The biggest issue being exactly what you've said where we have the same API models that are used as Request/Response which causes a lot of unintended side effects for client interfaces and developer documentation. It doesn't impact the development teams for Back End/Front End quite as much because of how tight their feedback loop with each other and Product on these issues.
I'll cite this issue as a reason for instigating change in the schema from those teams and hopefully get that separated so that the model attribute behaviors can be rectified.
Coming back to your example though, why do you see AccountNumber in the CloudRouter schema as being required? Couldn't follow your message the first time around so looking for more clarity.


Accordion styling issue:

Round corners on last panel
When the last panel of a accordion is expanded, the bottom corners of the panel are still rounded. And it seems that there are two borders at the bottom of the panel.
I consider this as a minor inconsistency as the stackview does not have rounded corners and duplicated borders for the last panel.
Accordion

Stack View

How to reproduce
Go to https://clarity.design/documentation/accordion and open the last panel of the example accordion to see the rounded corners.
Go to https://clarity.design/documentation/stack-view and open the last panel of the example stack view to see no rounded corners.
Expected behavior
There should be no rounded corners and duplicated borders on the last panel of the accordion.
Versions
App
Clarity Documentation for v2.
Device:

Type: Notebook
OS: Windows 10
Browser chrome
Version 67

As a workaround I added this styles to my scss files.
.clr-accordion:not(.clr-stepper-forms) .clr-accordion-panel:last-child {
    .clr-accordion-panel-open {
        .clr-accordion-header {
            border-bottom-left-radius: 0;
            border-bottom-right-radius: 0;
            border-bottom: none;
        }
    }
}


octave.buildEnv: Remove tarballs symlinks only if needed

Motivation for this change
Fix https://github.com/NixOS/nixpkgs/issues/123964 .
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Added a release notes entry if the change is major or breaking
[x] Fits CONTRIBUTING.md.

I have no problems with it. It looks good.
Just curious why it's needed. All packages for this will come from Octave packages' SourceForge location, which always comes down as a zip.


Support reading config from parent directories

(from #11)
Sort of like git will find a .git directory by going upward toward the fs root, let's look for .taskchampion.yml files up the directory hierarchy, and apply them in reverse order.
This will let folks apply defaults to specific subdirectories, e.g., if I'm in ~/my-novel then the default report might just show tasks tagged with +novel.

Isn't this contradictory to the design of TC?

Configs stored in $XDG_CONFIG
Data is stored in $XDG_DATA

I don't quite see this working in a long-term if data backend can't be represented by file/folder structure.

Yeah, that's a good point.  This shouldn't allow overriding the data directory, for example.  Maybe it only overrides certain config properties, like report definitions?

Let's think about user story. Could you come-up with one and I will pick-up where you left tomorrow morning?

@srfraser can you do so ^^?

Any updates?.. Tagging TBD for now.

I think this was a possible effect of my other request, but I don't have a good user story for this variant in particular.

The $PWD-based functionality sounds like it might be addressed by whatever comes out of https://github.com/taskchampion/taskchampion/discussions/163

I think this was a possible effect of my other request, but I don't have a good user story for this variant in particular.

How do you feel about what @dbr is proposing here?

Let's keep this in #163 -- it's still at the "idea" stage and not "issue"


es6 decorator support in description

More information #207

Coverage increased (+0.002%) to 99.26% when pulling fb1cfae3eb51b1622c0d443d83ec250cb9c19d90 on picidaejs:master into fdd0004782f218c4362fd928d82ef0e84a8e64d3 on eslint:master.

Coverage increased (+0.002%) to 99.26% when pulling fb1cfae3eb51b1622c0d443d83ec250cb9c19d90 on picidaejs:master into fdd0004782f218c4362fd928d82ef0e84a8e64d3 on eslint:master.

Coverage increased (+0.002%) to 99.26% when pulling fb1cfae3eb51b1622c0d443d83ec250cb9c19d90 on picidaejs:master into fdd0004782f218c4362fd928d82ef0e84a8e64d3 on eslint:master.

It's a long long time to maintain so closed it


adding skip_service_restart conditional check to skip docker service restart

Hello,
Is there any way to skip handlers from running after all tasks? After some search on the web, it seems not avoidable.
Can you add a conditional check inside the Restart rootless docker to skip it?
I'll provide an example to be clear:
this is handlers/main.yml
---
- name: Restart rootless docker
  become: true
  become_user: "{{ docker_user }}"
  ansible.builtin.systemd:
    name: docker.service
    state: restarted
    scope: user
  when: not skip_service_restart

where skip_service_restart variable default is false
Alternatively, I could leverage ansible_skip_tags if you can add a tag to the task that I can use to avoid restart, something like:
---
- name: Restart rootless docker
  become: true
  become_user: "{{ docker_user }}"
  ansible.builtin.systemd:
    name: docker.service
    state: restarted
    scope: user
  tags:
  - docker_rootless_restart_handler

Thank you in advance

Hi @scicco is there any particular reason for this?
The handler should only trigger when a new Docker release has been installed, https://github.com/konstruktoid/ansible-role-docker-rootless/blob/main/tasks/docker_install_rootless.yml#L57

Hello @konstruktoid,
the reason is that my Ansible procedure is a disaster recovery procedure that builds containers and runs them as the last actions. When I run this procedure the handler runs as the last step, so my running containers will shut down because of the docker restart and I have to do a manual login inside the new server to start containers again. If I can skip that handler with a proper tag or even better use a flag to skip that handler it will be handy for me.

 when: service_restart and service_restart: true as default seems more logical and we don't get any double negatives.

I agree,
so the updated handlers/main.yml will be:
---
- name: Restart rootless docker
  become: true
  become_user: "{{ docker_user }}"
  ansible.builtin.systemd:
    name: docker.service
    state: restarted
    scope: user
  when: service_restart and service_restart: true

when: service_restart is enough since it will trigger when true

I'll update it now.

thank you


ValueError: could not convert string to float: '.'

Hi,when I  run the example in config.ini with this command:
python InterVar.py -c config.ini
I got the following error. The version of python and ANNOVAR on my computer are 3.5.2 and 2017-07-17 respectively.
Notice: Begin the variants interpretation by InterVar
Traceback (most recent call last):
File "Intervar.py", line 2083, in
main()
File "Intervar.py", line 2052, in main
sum2=my_inter_var(annovar_outfile)
File "Intervar.py", line 1805, in my_inter_var
intervar_bp=assign(BP,line,Freqs_flgs,Funcanno_flgs,Allels_flgs)
File "Intervar.py", line 1680, in assign
BP7=check_BP7(line,Funcanno_flgs,Allels_flgs)
File "Intervar.py", line 1601, in check_BP7
if float(cls[Funcanno_flgs['GERP++_RS']]) <= float(cutoff_conserv) or cls[Funcanno_flgs['GERP++_RS']] == '.' :
ValueError: could not convert string to float: '.'
Can you help me? Thanks.

Please update  the intervar by:
https://github.com/WGLab/InterVar/archive/master.zip
Best,
Quan LI, Ph.D
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>http://www.quanli.tk http://www.quanli.tk
From: ZhenhongJiang<EMAIL_ADDRESS>Sent: Wednesday, January 31, 2018 10:27 PM
To: WGLab/InterVar<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [WGLab/InterVar] ValueError: could not convert string to float: '.' (#23)
Hi,when I run the example in config.ini with this command:
python InterVar.py -c config.ini
I got the following error. The version of python and ANNOVAR on my computer are 3.5.2 and 2017-07-17 respectively.
Notice: Begin the variants interpretation by InterVar
Traceback (most recent call last):
File "Intervar.py", line 2083, in
main()
File "Intervar.py", line 2052, in main
sum2=my_inter_var(annovar_outfile)
File "Intervar.py", line 1805, in my_inter_var
intervar_bp=assign(BP,line,Freqs_flgs,Funcanno_flgs,Allels_flgs)
File "Intervar.py", line 1680, in assign
BP7=check_BP7(line,Funcanno_flgs,Allels_flgs)
File "Intervar.py", line 1601, in check_BP7
if float(cls[Funcanno_flgs['GERP++_RS']]) <= float(cutoff_conserv) or cls[Funcanno_flgs['GERP++_RS']] == '.' :
ValueError: could not convert string to float: '.'
Can you help me? Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/WGLab/InterVar/issues/23 , or mute the thread https://github.com/notifications/unsubscribe-auth/APD6JJ4Z5yuL7f1seuB1AfX5Cp0vBUOXks5tQS74gaJpZM4R1ADC .  https://github.com/notifications/beacon/APD6JB05fE2sU2Cnq3pG3jxdvxUPBhAgks5tQS74gaJpZM4R1ADC.gif

Thank you very much. Everything works fine according to your advice.
Best wishes，
Zhenhong Jiang, PhD
Jiangxi Province Key Laboratory of Molecular Medicine
Email<EMAIL_ADDRESS>
在 2018年2月1日，上午11:30，Quan LI<EMAIL_ADDRESS>写道：
Please update the intervar by:
https://github.com/WGLab/InterVar/archive/master.zip
Best,
Quan LI, Ph.D
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>http://www.quanli.tk http://www.quanli.tk
From: ZhenhongJiang<EMAIL_ADDRESS>Sent: Wednesday, January 31, 2018 10:27 PM
To: WGLab/InterVar<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [WGLab/InterVar] ValueError: could not convert string to float: '.' (#23)
Hi,when I run the example in config.ini with this command:
python InterVar.py -c config.ini
I got the following error. The version of python and ANNOVAR on my computer are 3.5.2 and 2017-07-17 respectively.
Notice: Begin the variants interpretation by InterVar
Traceback (most recent call last):
File "Intervar.py", line 2083, in
main()
File "Intervar.py", line 2052, in main
sum2=my_inter_var(annovar_outfile)
File "Intervar.py", line 1805, in my_inter_var
intervar_bp=assign(BP,line,Freqs_flgs,Funcanno_flgs,Allels_flgs)
File "Intervar.py", line 1680, in assign
BP7=check_BP7(line,Funcanno_flgs,Allels_flgs)
File "Intervar.py", line 1601, in check_BP7
if float(cls[Funcanno_flgs['GERP++_RS']]) <= float(cutoff_conserv) or cls[Funcanno_flgs['GERP++_RS']] == '.' :
ValueError: could not convert string to float: '.'
Can you help me? Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/WGLab/InterVar/issues/23 , or mute the thread https://github.com/notifications/unsubscribe-auth/APD6JJ4Z5yuL7f1seuB1AfX5Cp0vBUOXks5tQS74gaJpZM4R1ADC . https://github.com/notifications/beacon/APD6JB05fE2sU2Cnq3pG3jxdvxUPBhAgks5tQS74gaJpZM4R1ADC.gif
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/WGLab/InterVar/issues/23#issuecomment-362147767, or mute the thread https://github.com/notifications/unsubscribe-auth/Aa-J2AVok2JfY33rgUvkIwKnkYT4bqt4ks5tQS_DgaJpZM4R1ADC.


[PIP] PIP-173 : Create a built-in Function implementing the most common basic transformations

Motivation
Currently, when users want to modify the data in Pulsar, they need to write a Function.
For a lot of use cases, it would be handy for them to be able to use a ready-made built-in Function that implements the most common basic transformations like the ones available in Kafka Connect’s SMTs.
This removes users the burden of writing the Function themselves, having to understanding the perks of Pulsar Schemas, coding in a language that they may not master (probably Java if they want to do advanced stuff), and they benefit from battle-tested, maintained, performance-optimised code.
Goal
This PIP is about providing a TransformFunction that executes a sequence of basic transformations on the data.
The TransformFunction shall be easy to configure, launchable as a built-in NAR.
The TransformFunction shall be able to apply a sequence of common transformations in-memory so we don’t need to execute the TransformFunction multiple times and read/write to a topic each time.
This PIP is not about appending such a Function to a Source or a Sink.
While this is the ultimate goal, so we can provide an experience similar to Kafka SMTs and avoid a read/write to a topic, this work will be done in a future PIP.
It is expected that the code written for this PIP will be reusable in this future work.
API Changes
This PIP will introduce a new transform module in pulsar-function multi-module project.
 The produced artifact will be a NAR of the TransformFunction.
Implementation
When it processes a record, TransformFunction will :

Call in sequence the process method of a series of TransformStep implementations.
Each TransformStep will modify the output message and topic as needed.

Send the transformed message to the output topic.

The TransformFunction will read its configuration as Json from userConfig in the format:
{
  "steps": [
    {
      "type": "drop-fields", "fields": "keyField1,keyField2", "part": "key"
    },
    {
      "type": "merge-key-value"
    },
    {
      "type": "unwrap-key-value"
    },
    {
      "type": "cast", "schema-type": "STRING"
    }
  ]
}

Each step is defined by its type and uses its own arguments.
This example config applied on a KeyValue<AVRO, AVRO> input record with value {key={keyField1: key1, keyField2: key2, keyField3: key3}, value={valueField1: value1, valueField2: value2, valueField3: value3}} will give after each step:
{key={keyField1: key1, keyField2: key2, keyField3: key3}, value={valueField1: value1, valueField2: value2, valueField3: value3}}(KeyValue<AVRO, AVRO>)

           |
           | ”type": "drop-fields", "fields": "keyField1,keyField2”, "part": "key”
           |
{key={keyField3: key3}, value={valueField1: value1, valueField2: value2, valueField3: value3}} (KeyValue<AVRO, AVRO>)
           |
           | "type": "merge-key-value"
           |

{key={keyField3: key3}, value={keyField3: key3, valueField1: value1, valueField2: value2, valueField3: value3}} (KeyValue<AVRO, AVRO>)
           |
           | "type": "unwrap-key-value"
           |
{keyField3: key3, valueField1: value1, valueField2: value2, valueField3: value3} (AVRO)
           |
           | "type": "cast", "schema-type": "STRING"
           |
{"keyField3": "key3", "valueField1": "value1", "valueField2": "value2", "valueField3": "value3"} (STRING)

TransformFunction will be built as a NAR including a pulsar-io.yaml service file so it can be registered as a built-in function with name transform.
Reject Alternatives
Create a separate third party project not managed by the Pulsar community.
Problems:

it won't be easily available to all Pulsar users
it would be hard to guarantee compatibility with many Pulsar versions, and the Transformations will use many advanced features of Pulsar APIs

I would not go too much into the implementation details in the PIP like TransformContext
I would only cite the steps, the configurations and the first operations that will be available.
the TransformContext without the PR is very hard to understand and actually, it is a implementation detail, hidden to the users and we will change it in the future as needed.
I would add to "Reject Alternatives":

Create a separate third party project not managed by the Pulsar community.
Problems:
it won't be easily available to all Pulsar users
it would be hard to guarantee compatibility with many Pulsar versions, and the Transformations will use many advanced features of Pulsar APIs

Thanks Enrico. I did the updates.

I would suggest having some concrete implementations of the TransformFunction in a separate repo first instead of starting right in the main pulsar project.

I would suggest having some concrete implementations of the TransformFunction in a separate repo first instead of starting right in the main pulsar project.

@nlu90 see the comment from @eolivelli . We've put this in "Rejected alternatives" for the reasons that:

it won't be easily available to all Pulsar users
it would be hard to guarantee compatibility with many Pulsar versions, and the Transformations will use many advanced features of Pulsar APIs

@nlu90 The transformations will be well tested in the codebase. The use cases do not came out of the blue (in that case you may wonder if they add value for users) but they are inspired by Kafka/Confluent Platform.
The very good thing about this proposal is that they are builtin but they won't be an additional weight for users that do not want to use them.

@nlu90 Would you like to have a conversation with @cbornet to discuss the performance motivations for this change?

@dave2wave @cbornet @nicoloboschi
Thanks for your replies. I really would like to hear more about use cases and performance motivations to better understand it.

This PIP was not accepted
The work has been posted here
https://github.com/datastax/pulsar-transformations
and it is available to anyone, it is Apache 2 licensed


ceph: fix build, 12.2.2 -> 12.2.7

Motivation for this change
Since 772eef91686974b7710081a9a77e5c0e287c25e8, Boost doesn't support by python by default, which broke ceph. Also bump to 12.2.7, the latest release of ceph 12, which is still supported upstream.
Note that ceph 13 is out, and people are working on getting it into nixpkgs, see #42830.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: ceph
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: ceph
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

It's a long build, likely to time out on ofborg.
Builds locally on x86_64-linux and passes nixos/tests/ceph.


Reconsider unconditionally exposing capture offsets on result

Revisiting feedback from https://github.com/tc39/proposal-regexp-match-offsets/issues/1#issuecomment-389887003:
Currently, the proposed changes add an optional bag of args to RegExp.p.exec and multiple other RegExp and String methods. One can pass { capture: "indices" } to tell exec to return capture indices instead of the captured substrings. Indices are returned as a 2-element array [start, end].
I don't think this is the way to go: it doesn't feel like clean API, it opens us up to future complexity ('we already have the options object, why not add more there'), it modifies 7+ functions just to pass through matchOptions, it adds conditional functionality to exec (as the choke-point for all RegExp functions, IMO we should keep exec simple).
It may be cleaner to remove the option args and just expose indices on regexp results unconditionally.

If we carefully specify the way to access these indices, overhead would be low. We'd only need to set a single property (at least in V8, the regexp engine already provides a list of all capture indices). And additional memory use could be just 2 * sizeof(VM integer) * number of captures.
The way to access these could be a method pair on the result object (result.captureStart(i) / result.captureEnd(i)).
A potential complication: currently the result is just an Array with extra data properties. The extra methods would probably be located on the prototype and so we'd have to define a dedicated prototype for the result.
Alternatively, we could expose them as two arrays on the result, 'starts' and 'ends'. But with this approach we'd have the overhead of creating two full new JSArrays and transforming the internal array.

So, my proposal would be: expose indices unconditionally through captureStart(index) and captureEnd(index) on the result object. The only overhead would be that the captures array (which we already have) is kept alive by the result object.

I’d think a single getter or captureIndexes function own property on the match object would be simpler?

This was the original Stage 1 proposal, but I was cautioned against it due to the memory overhead added to every existing RegExp result, even if they didn't use this feature. I agree that a captureIndices property would have been the preferred approach.
A less memory-intrusive approach (though possibly more break-y) would have been to use something like an Integer Indexed Exotic Object for the result of exec/match (etc.) instead of an Array, and have the string elements of the array lazily evaluate based on the stored indices. I'm not certain there's a good way to spec that, however, much less whether it would be a good idea.

I was cautioned against it due to the memory overhead added to every existing RegExp result

If done carefully, the memory overhead would be at most 2 ints per capture. Assuming 4-byte integers, that's comparable to each captured string being 8 characters longer.

I was cautioned against it due to the memory overhead added to every existing RegExp result

To be clear, it was cautioned against by the same people who are now asking to revisit this. We now believe the overhead could be minimal if implemented carefully. It seems like there's agreement this would be strictly better than having to add an options bag to multiple existing methods, so let's do it!
schuay@'s suggestion applies regardless of whether we go with captureStart/captureEnd or captureIndices.

I'm looking into putting together a PR for this change using an "indices" getter on the result that would lazily create an array of start/end tuples, along with its own groups object mapping groups to the same start/end tuples. This would be similar to the original Stage 0/1 proposal, with the only overhead being the need to hold onto the start/end index (and group name, if one is associated with it).
Would that be sufficient to address the memory concerns? If so I can put up a PR by tomorrow.

@ljharb If we don't have options, then it seems there'd be no way to get this information from @@matchAll for a RegExp with the g flag. We might be able to support @@match with g, but it becomes very complicated to lazily evaluate indices, so for @@match with g they would have to be eagerly evaluated.

I'm looking into putting together a PR for this change using an "indices" getter on the result that would lazily create an array of start/end tuples, along with its own groups object mapping groups to the same start/end tuples.

Sounds reasonable.

If we don't have options, then it seems there'd be no way to get this information from @@matchAll for a RegExp with the g flag

Why not? @@matchAll returns an iterator of regexp results, each of which would have the indices getter, right?

@rbuckton I'm not sure what you mean; matchAll could easily create a getter function for each match object that access internal slots to build up the info.

While we are at putting alternatives on the table: we could also introduce a new regexp flag to prescribe getting capture indices. I'm not saying that this is what I would prefer though.
I'm not sure adding indices to match with g makes sense. The same could be achieved with matchAll already, and I was under the assumption that we only want to extend regexp result objects, e.g. ones returned by matchAll or exec. match returns an array of strings.

@hashseed: We've already discussed and generally disliked the idea of making this a regexp flag.
@ljharb: I think I misread part of @@matchAll, so I see that it would not be an issue. However, @@match is still a bit problematic in the g case, since I can't refer to any existing internal slot as I only have an array to work with (since RegExpExec could just return the result of a user-defined custom exec() function). If I try to add a lazily-evaluated indices property to the result for @@match, the lazy-evaluation would be user-observable (assuming that matters).
@@match is already strange in the g case since it doesn't have a groups property.

match returns an array of strings.

Yes and no. match for a RegExp with g returns only an array of strings. match for a RegExp without g returns the result of RegExpExec, which is the more complex array of strings or undefineds with the extra index, input, and group properties.

match for a global regex should be unchanged by this proposal; people can use matchAll if they want any useful output for a global regex.
match for a nonglobal regex should be the same as matchAll's only yielded match object for a nonglobal regex.

@ljharb: So effectively drop any specialization in @@match and @@matchAll since they're no longer needed?
If you would, please take a look at #14 as it contains an alternative to the current Stage 2 semantics that reverts back to adding a property to the result of RegExpBuiltinExec.

A major motivation behind this proposal (changing back to unconditionally including offsets on results) was that we would not have to modify any regexp builtins other than exec. I agree it's totally fine for match not to include offsets, that's why matchAll was introduced.

@rbuckton from this proposal? perhaps; i'll look at the PR.
@schuay note that match would include offsets for nonglobal regexes, which imo is the proper thing to do.

@ljharb right, thanks for clarifying. My point was that happens automatically, without modifying any of the logic in match itself.

@ljharb: For the current version of the proposal (that uses an options object), is it worth supporting an extra argument to match/@@match if matchAll/@@matchAll is the future-preferred alternative? There is concern about threading an options argument through the existing @@match method due to possible user customization and subclassing, however @@matchAll is still fairly new and may not suffer from the same burden.

I think that the API should remain consistent; so yes, it would be good to include the options object on match as well; matchAll being new means it might not be as common, but it's still just as likely to be subclassed as match is (which, imo, is virtually zero likelihood on either; but opinions differ here)

Is there a tool for searching github projects for usages of Symbol.match? For TypeScript there's BigTSQuery: https://bigtsquery.firebaseapp.com/query?selector=PropertyAccessExpression[text%3D"Symbol.match"]. I've tried using GitHub's own search, but it doesn't seem to want to treat the . as an actual ..

@rbuckton If I might offer one opinion from the wild…
I personally explored a lot of subclassing patterns to augment exec behaviours, but forgetting specific details, all my work eventually (probably for at least a few good reasons) moved away from Symbol.… hooks on actual RegExp subclasses.
Also, re argumenting the ‹extends RegExp›.prototype.exec, this proposal itself being out there for quite some time now should have at least cautioned (did for me) otherwise.
Maybe worthwhile considering rolling out experimental but when you do, please consider having a little more visibility+outreach+involvement in the efforts for the community — ie breaking something vital or just outdated feeling very critical to those momentarily affected but also historically subjectively very polarizing and frustrating to those affected permanently as a result.

Subclassing RegExp properly requires overriding 1 or more of the Symbol hooks.

Yes, overriding without making breaking assumptions of the interface.
Here is roughly how I go about it personally:
class extends RegExp {
  overloadedExec(... args) {
    return // somehow get the result
  }

  capture(result, ... args) {
    // somehow augment the result
    return result;
  }

  exec(... args) {
    const result = this.overloadedExec(...args) || super.exec(…args);
    if (result) this.capture(result, ...args);
    return result;
  }
}

Switching to result.indices was the accepted consensus. Merged in #14.


Refresh button doesn't check history for deleted files

Testing #145461

Create a bunch of local history
Delete the local history files from user data dir
Hit refresh button
🐛 Entries still there.

Entries are not there on reload of the window so I would expect clicking the refresh button would force a refresh as well

@JacksonKearl this might need support from the timeline, i.e. when the refresh command is used from the timeline toolbar, give me a hint that I should really go to disk and resolve all entries.
I see how there is this:
https://github.com/microsoft/vscode/blob/d0f7122bb97c6232b4423185ab80c8e17bc0ea33/src/vs/workbench/contrib/timeline/common/timeline.ts#L81-L84
But resetCache seems to be true even when I just go from one editor to the other.
I would rather want to limit going to disk to the refresh action specifically.

Don't think this is critical, it is not advised to tamper with contents in the user data dir.


minimum gpu memory requird and runtime error while running YOLOs, YOLOm, YOLOl

Hi,
Hope you are doing well.
Can you please tell me how much gpu ram is required to reproduce your results with YOLOx?
And upon running YOLOs or YOLOm it gives dimension miss match error, Can you please help me with this?
RuntimeError: Given groups=1, weight of size [1280,1280,3,3], expected input[1,512,4,4] to have 1280 channels, but got 512 channels instead
Thanks!!!

Hello, I ran all the experiments on V100 GPU, which has 32G memory :(
You can run results on YOLOs or YOLOm for comparisons. The key lies in the "Ranker" class here, which maps the feature map to embeddings for alignment. I specific the input dim as 1280, so it produces bugs when you use YOLOs or YOLOm. You can modify this hyperparameter or make it as an input argument.
Feel free to ask me if any other questions exist :)))

Hi,
Oh ok so I was trying it on max 12 GB gpu with batch 2 but it gave Cuda out of memory error.
I will make the required changes in Ranker class and then ask for any help if I want not able to solve it myself.
Thanks alott for helping!!


Docker containers aren't reproducible

Flagged by @james-callahan in #11: https://github.com/tkhq/frames/pull/11#discussion_r1379139620
We could address this with:

COPY into a /newroot
fix timestamps in /newroot
Do a FROM scratch + COPY --from to flatten the COPYs away

Or use toolchain (https://git.distrust.co/public/toolchain)

Example over at https://github.com/tkhq/ecr-proxy/blob/d11338eba841287a1e8326560c5679e2a07d34d3/Dockerfile#L26-L35


3.0 - Final Phase, stage continued #24

Refactoring of \App\Core\BaseModel, on using only the camelCase variables and methods and overall optimizations.
The BaseModel lose the ability to use the snake_case methods, but its logic is simplified and consolidated.

@LuckyCyborg :100: :+1:

@tomvlk Thanks!
But the truth is that was cancelled the specification about compatibility with our "old-style" Components, using snake_case. So, time to simplify the BaseModel! :smirk:

@tomvlk BTW, we wait your updateBatch method in Database Engines... :smirk:
To see what we expect, look in the BaseModel's one.

@tomvlk Also, I believe that a variable called $callbackParameters is Spanish enough to be on your like... :smirk:

Working on it now. Why all spanish btw..? :laughing:

@tomvlk Very descriptive names on a somewhat complex Class.
Worry not, I will fight with their naming! :smirk:

@tomvlk BTW, the Engine's updateBatch will be very nice to have ability to optionally use a Transaction.
Not in our specifications, but very useful overall. :smirk:

@LuckyCyborg I have it working currently, implemented on engine and service. But we should also implement multiple $where keys, for multi primary key support. Currently not done in my forked branch.
I don't have the whole day (not even half) for this unfortunately, also implementing the transaction isn't going to be today. Maybe you could assist in this.

@tomvlk The principle of updateBatch is to have a unique WHERE KEY; for example, as... in example: title.
Then maybe multiKeys shall be in another method.
In other hand, after you design arrive in the main repo, I will look for, too. :smirk:

@LuckyCyborg It can have an array with key columns or a string maybe.

@tomvlk Again, see there:
$data = array(
          array(
              'title'  => 'My title',
              'body'   => 'body 1'
          ),
          array(
              'title'  => 'Another Title',
              'body'   => 'body 2'
          )
      );

The method known the key, and for every record do the match:
WHERE title = `My title`

WHERE title = `Another title`

@LuckyCyborg This is how it's done right now.

@tomvlk Then everything is perfect! :+1:

But it would be cool to have support for this form too:
updateBatch($data, array('title', 'subtitle'));

And will produce SQL:
WHERE title = 'My title' AND subtitle = 'Subtitle Value'

WHERE title = 'Another title' AND subtitle = 'Subtitle Value'

@tomvlk BTW, there was an example, but in real world, most likelly will be something like:
SET body = `body 1` WHERE id = 432

SET body = `body 2` WHERE id = 865

@tomvlk If you made this optionally
as in both
updateBatch($data, 'id');

updateBatch($data, array('title', 'subtitle'));

I don't have nothing against. But what we need is the first variant. :smirk:

@LuckyCyborg Thats the plan, but not for now, as I don't have the time and concentration rates for it :smiley:

@tomvlk OKay, then! :+1:

@daveismyname Please merge this pull-request, as being completed as objectives!


test(e2e) print pod logs if the flaky test fails

What this PR does / why we need it:
dump pod logs if the flaky e2e test case TestDeployAllInOnePostgresWithMultipleReplicas fails
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged):
related to #2670
Special notes for your reviewer:
PR Readiness Checklist:
Complete these before marking the PR as ready to review:

[ ] the CHANGELOG.md release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR

I'm OK with this as is for now but I believe httpGetResponseContains could be made into something like getHttpResponse helper that will return the body of an HTTP call (perhaps parametrized with the method as well) and then the result of that could be called with strings.Contains() at call site.
I believe there are other places in the codebase that would leverage this helper as well, decreasing the amount of test code.
That can be done in a separate PR though. If you agree @randmonkey let's create an issue for that.

OK, let's create a new issue for making some helper functions fore repeated works in tests.


bug(mat-icon-button/radio-button/checkbox): Unable to reduce ripple size

Is this a regression?

[X] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
14.x
Description
For a button of any size, the default ripple size is displayed.
In certain scenarios, we need to fit in the button in smaller UI. As the ripple effect is taking more space than the button, it is creating a UI glitch.
If we reduce the size of button, still the ripple effect is taking unwanted space and hence I had to redesign the application.
Is there any way to override the ripple size "THROUGH CSS" as the other option (density) is not working as expected for our use cases
Reproduction
Reference - https://stackblitz.com/edit/angular-rumxmw?file=src%2Fapp%2Fbutton-overview-example.html
Expected Behavior
The ripple effect also should be relative to the button
Actual Behavior
The ripple effect is not relative to the button
Environment
Angular CLI: 15.2.4
Node: 16.15.0
Package Manager: npm 8.5.5
OS: win32 x64

Angular: 15.2.4
... animations, cdk, cli, common, compiler, compiler-cli, core
... elements, forms, language-service, material
... material-moment-adapter, platform-browser
... platform-browser-dynamic, router

Package                         Version
@angular-devkit/architect       0.1502.4
@angular-devkit/build-angular   15.2.4
@angular-devkit/core            15.2.4
@angular-devkit/schematics      15.2.4
@angular/flex-layout            15.0.0-beta.42
@schematics/angular             15.2.4
ng-packagr                      15.2.2
rxjs                            7.8.0
typescript                      4.9.5

Why doesn't the density mixin work for you? It is the intended public API for cases like this.

Why doesn't the density mixin work for you? It is the intended public API for cases like this.

we are able to provide the density value from -2 to +2 only via mixin. We are trying to reduce the size of the ripple from 48px to 24px which is equivalent to -5 and the density is not allowed by angular theming. Hence we are trying manually via CSS

The density scale is based on the Material Design spec so that's why it's capped at those values. I was able to get the button to be 24x24 with the following styles. Note that doing this is at your own risk since the internal implementation of the buttons can change:
--mdc-icon-button-state-layer-size: 24px;
--mdc-icon-button-icon-size: 24px;
padding: 0;

.mat-mdc-icon-button .mat-icon {
    width: 24px;
    height: 24px;
    font-size: 24px;
}

Are you sure that you're applying all the styles I mentioned above? Here's what the button looks like for me:

we are not utilizing any mixin , directly applying the styles in .scss files
where would you add the below styles, for which class or element we are supposed to provide it
--mdc-icon-button-state-layer-size: 24px;
--mdc-icon-button-icon-size: 24px;
padding: 0;
can you share the styles override as a working scss / css format with selectors

It's likely a specificity issue. You should apply it to the .mat-mdc-button and verify in the dev tools that something else isn't overriding it.

Closing since there hasn't been any activity and there are some suggestions above.


Make attributes composable with Nodes

Hi,
Currently attributes expect Expressions on both sides of the =. The body of elements is composable with more complex nodes like a for loop. It seems like there is no way to do the same for attributes. In my use case i want to compose a class list from a slice/iterator without allocating a temporary string and just directly writing it to the underlying fmt::Write instance.
Currently the only solutions would be:

allocating that temporary string
use markup::raw
Directly implement the Render trait

It would be nice if the attributes would be composable just like the body of html elements. If this would be changed this would obviously be a breaking change if there is no separate syntax implemented for this.
I would like to try implementing this as this crate is really really handy and helps with many of my use cases, thanks for the work.
Thanks :)

Closed via commit 131e185 see #27 for more info.


Add sorting option

Issues are sorted by creation date. That makes sense. But with more filters coming soon, it might be useful to sort using other properties, like stars count, fork count, and so on.
Example:

Hi @lgsreal what we can do is make it like a multi sorting feature, where it'll always give recent issues but then you can get recent issues from huge repos to smaller ones (sort by date always, sort by stars).
I think giving recent issues is and will always be the best way for beginners cause it'll give them time to discuss and understand the issue, If a issue is a bit old, then it might already have a good amount of comments, then it might get tough for them.
Let me know your thoughts, I'm open to ideas

@lgsreal Hi, just want to know the status of this, are you still working on this? If not then please inform here, so that I can assign it to someone else.
I hope you'll understand

Hello @dotslashbit, I'm working on it.
I'll put the options as a second sorting parameter.
One question... Can I put the sorting options in the filtering section, or maybe above the issues card. Which do you prefer?

Hi @lgsreal any updates?
It'll be great if you can just open a draft PR, so that we can steadily review it

Hi @dotslashbit I just have some questions, but I'm in transit right now. Is it ok if I open the PR tomorrow?
About the updates you mentioned, I synced the forked repo with the updates from the original repo and saw the changes.
I had to work a lot this week, but I have reserved some time to try and finish this tomorrow.

@lgsreal take your time, all of us have other things to do and I can totally understand that.
There's no rush
Yeah sure, you can open PR tomorrow, not an issue


Calendar-Error | Calendar-Warning

Icon Request

Icon name: Calendar-x or calendar-error | calendar-warning
Tags of this icon: Business
Use case: A calendar icon with an error mark and/or with warning a user with a date is wrong or invalid
Screenshots of similar icons:

Thanks for the suggestion. Now you can get those icons in version v3.2.0.
https://remixicon.com/icon/calendar-close-line
https://remixicon.com/icon/calendar-close-fill


console部分翻译

Q
A

Is bugfix?
yes/no

New feature?
yes/no

Breaks BC?
yes/no

Tests pass?
yes/no

Fixed issues
comma-separated list of tickets # fixed by the PR, if any

已还原//开头的注释翻译

console directory done


merge from arlac77/npm-package-template-esm-only

.npmignore

chore(npm): update .npmignore from template

Coverage remained the same at 76.225% when pulling f3f45e21238ab49238336c9ec6e5a04cf3cde224 on npm-template-sync/1 into 79ece57ebd75c4d4e85e4da7691080f60f98fe65 on master.

Codecov Report

Merging #561 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #561   +/-   ##
=======================================
  Coverage   75.94%   75.94%
=======================================
  Files           2        2
  Lines         474      474
=======================================
  Hits          360      360
  Misses        114      114

Continue to review full report at Codecov.

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

:tada: This PR is included in version 3.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


rename auto batching cli

rename --enable-autobatching to --enable-auto-batching.
as per https://github.com/meilisearch/specifications/pull/96#issuecomment-1060693721

Bors merge

bors merge


h3 polyfill crash

when I use polyfill with target coordinates and resolution 8, the java application crashed.
here is the coordinates
119.773625,31.339057;119.391881,31.449531;119.180312,31.433757;118.407626,31.354847;118.232851,31.433757;117.846508,31.622867;117.736124,31.370635;117.276192,31.267969;116.825458,31.030618;116.834657,30.705271;116.521903,30.562084;117.073822,30.546161;116.963438,30.219162;117.119815,29.77075;117.147411,29.3203;117.910899,29.296112;117.920097,29.376717;118.370831,29.762724;119.115922,30.075252;119.769026,30.251113;119.842615,29.818891;120.219759,29.666362;120.652096,30.027236;120.799274,30.41071;120.753281,30.760897;120.587705,30.91965;120.100177,30.895854;119.916204,31.204734
here is the err file
hs_err_pid23932.log

Hi, what version of h3-java are you using? This might be fixed in version 3.1.0.

thank you, it works fine in version 3.1.0.


Add remoteclub.io

Added remoteclub.io

These look like remote job postings not remote freelancing sites. I would add it here: https://github.com/lukasz-madon/awesome-remote-job#job-boards
Also is it an aggregator?


Consider removing example code (non blocking)

I would suggest to remove example code from source to ease reading. But that's not blocking of course.

Example code removed by https://github.com/Uwe1958/ioBroker.bluesound/commit/6d6700fbca0c1b31906a8aaec2391edc0e743020


Backup job items and queue

The corpus registry (containing all job info and the queue) are stored on GUIT 2 which is backed-up automatically. For now I don't think we need another backup solution.


Can not connect to truenas webgui

this is probably something stupid I am overlooking but, I can ping out from the host shell of TrueNas to other devices on my tailscale network, but when I try to connect to the webgui from outside I get an instant connection refused. No clue as to why.

to update, I have been trying to resolve this for some time and it seems like the jail is not forwarding to the main truenas install, can not find any setting to indicate as to why.

I just barely got this working for my system today. My issue was that I needed to set tailscale to down, then bring it up using the --advertise-routes flag The example used on the tailscale support site is tailscale up --advertise-routes=<IP_ADDRESS>/24,<IP_ADDRESS>/24 After that all that is needed is to approve the subnet routes in tailscale admin console and then it worked for me

Please see my comment for the related PR. The point of the whole guide and IPFW NAT tinkering has been  to avoid activating the --advertise-routes functionality.

It was setup right, could ping in both directions with no issue, just never got the gui to show. I ended up migrating from core to scale since you can use tailscale directly with truecharts.

I have the same problem. ping works but services don't.
I used:
./setup-ipfw-nat.sh <IP_ADDRESS> 'tcp/22 tcp/443 tcp/445'
<IP_ADDRESS> is the ip of the TrueNas...

Just adding my experience from a fresh install.
I too could not get SMB or HTTP to work (I didn't test others). Pinging both ways (via tailscale ip) worked.
TrueNAS 13.0 U4
TrueNAS Host: <IP_ADDRESS>/24
TrueNAS Jail: <IP_ADDRESS>/24
Static Route: <IP_ADDRESS>/10 GW: <IP_ADDRESS>
ipfw nat 1 config if tailscale0 log same_ports redirect_port tcp <IP_ADDRESS>:28757 28757 redirect_port tcp <IP_ADDRESS>:5201 5201 redirect_port tcp <IP_ADDRESS>:2049 2049 redirect_port tcp <IP_ADDRESS>:445 445 redirect_port tcp <IP_ADDRESS>:443 443 redirect_port tcp <IP_ADDRESS>:22 22
I also just gave up.


Wrap ref index in RefIndex

Stack:

#1712 ⬅
#1711

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.


Begin work on "wrap in function call"

@OliverJAsh after reconsidering this, I don't think it provides much more value compared to:

Put your cursor on the node
Use "Expand Selection" (e.g. I've set editor.action.smartSelection.grow to ⌘ ↑)
Type ( => it wraps the whole thing into parenthesis already
← then write the function name (which we have to do in both cases)

I'm closing the PR for the moment. I'm up to rediscuss this together. I'll make sure this time we document why we want (or don't want) that.
Thank you!


Incorrect package name in README files

Preflight Checklist

[x] I have read the Contributing Guidelines for this project.
[x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Issue Details
Incorrect package name in README file heading. Issue found in below files

packages/aws/README.md
packages/azure/README.md
packages/common/README.md
packages/gcp/README.md

Expected Behavior
Package name mentioned in the title of the readme file should be correctly pointing to the respective package name.
example:
The title in packages/aws/README.md#1  should be # @cloud-carbon-footprint/aws
Actual Behavior
Package name mentioned in the title of the readme file was wrongly pointing to the 'core' package.
example:
The title in packages/aws/README.md#1  was pointing to  # @cloud-carbon-footprint/core
To Reproduce
check below files

packages/aws/README.md
packages/azure/README.md
packages/common/README.md
packages/gcp/README.md

-->
Screenshots

© 2021 Thoughtworks, Inc.

Fixed with PR https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/pull/955
Thanks again for catching this! @gbhasha


Identity Api /  Auth Configuration Api

We need a way to manage the different Authorization Provider Integrations in an abstract way. The Identity Api will provide a way to verify that an Identity Exists in the Scope of the currently configured AuthConfiguration(s). Here is the initial design:
2 Endpoints:

/v1/identity

Query for an Identity GET {?query=String}

Returns A list of identities or 404

Check Identity ExternalID {identity}

Returns 200 if the identity is valid 404 otherwise

/v1/authconfig

This is where you manage authorization providers
Can perform CRUD on the AuthConfig

/v1/token

identities Array of identities for this token.
accountId Account id for user the token goes with.
user identity for the user this token goes with.

Resource Types:

identity Used as members of the site or a project.

ID Unique identifier for this identity
NAME Name for this identity meant for users to see.
TYPE Identity Type Used to differentiate between any type. EX: a Ldap user vs a Github Org
IDENTITYPICTURE Link to a picture representing this identity if one exists.

{Any Authorization IntegrationType}

FIELDS Any number of fields that are specific the the configuration of this Authorization type.
ENABLED Indicating If this Authorization Method is in use or not.

AuthConfig

ENABLED Determines if Authorization is on or off.
FIELDS Field for each Authorization IntegrationType that exists
PROVIDER Currently Enabled Provider

projectMember Change to existing resource

role Role of this member
Identity Identity of this member

Why is project member changed?  You need to make sure this is backwards compatible and you can upgrade.

Because other wise duplicating logic.

In 5 words or less...

Just give serious consideration to the fact that you need to support upgrade w/o a data migration.

Not until ga i thought that is why i want to make this change now to make it easier to manage the api.

Better Api For Ga.

No, I'm telling you we need to support it now.  We aren't supporting API compatibility but we are supporting upgrades.  But if the upgrade means read data, change data, write back in new format.  That is not good.
So I'm telling you you have to support upgrades so be careful about your data structures.  I don't understand why existing project APIs need to change.

Hmm Ill Look Into It. Relax.

identity is phantom proxy

to member


doc add eth_signTransaction endpoint

Pull Request Description
Add documentation for eth_signTransaction endpoint.
Fixed Issue(s)

fixes #99

 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.


Game crashes if a scarab and a few spheres merge past the path exit point

A weird bug where when a sphere group consisting of a scarab and another sphere group consisting of a few spheres in front of it join back together after they completely go past the path exit point, the sphere chain isn't cleared properly. Only the scarab disappears, and a frame later the game crashes while it still holds an empty sphere chain that doesn't disappear. This bricks the save game, as loading it will immediately crash the game again.
An example setup from runtime.json (group offsets may need to be adjusted based on the path length):
"sphereGroups": [
	{
		"offset": 3200,
		"matchCheck": true,
		"spheres": [
			1,
			1
		],
		"speed": 400
	},
	{
		"offset": 2900,
		"matchCheck": true,
		"spheres": [
			0
		],
		"speed": 200
	}
]

Fixed in https://github.com/jakubg1/OpenSMCE/commit/8df06c3621efbb1098361da07597f93e8845fd8a.


Option to add date of export

Is your feature request related to a problem? Please describe.
When I use Generate Sql -> DDL or Export Data I want to see date when this file was created as this is important info and many other tools do this.
Describe the solution you'd like
Add option for this that adds comment at the top to DDL -- Exported date: <ISO8601 date> and similar to data export.
Describe alternatives you've considered
Alternative is to manually add this, which is errorprone as one may forget it. Later, you don't know the date of the artifact.

@majkinetor
Thanks for the request!


Persist br_netfilter module loading

Adresses #1460 and #1708.
As far as I can see, /ect/modules-load.d/ is viable on all supported distributions.

ci check this

@Nonymus Looks good. Now just waiting for CI

@mattymo From what I can tell, there was a (temporary, connectionr reset) error in bootstraping CI.


use goreleaser to simplify and automate releases

https://goreleaser.com/

Release Go projects as fast and easily as possible!

https://github.com/goreleaser/goreleaser

GoReleaser builds Go binaries for several platforms, creates a GitHub release and then pushes a Homebrew formula to a tap repository. All that wrapped in your favorite CI.

https://askcloudarchitech.com/posts/tutorials/create-homebrew-tap-golang-goreleaser-cobra-cli/

Create a Custom CLI Tool and Distribute with HomeBrew Using Goreleaser and Github Actions

This would also automagically solve the request for adding it to the homebrew package manager raised in:

https://github.com/mandiant/GoReSym/issues/44#issuecomment-1827128713

I'll see what I can do to add it myself.

Homebrew formula created and PR submitted to homebrew:

https://github.com/Homebrew/homebrew-core/pull/155716

Originally posted by @0xdevalias in https://github.com/mandiant/GoReSym/issues/44#issuecomment-1828961151


ASG broker

What we're after
We want a broker that will let users add allow rules to spaces with restricted egress ASGs

Further context
This will make a more turn-key solution for users wanting filtered egress
Security considerations
This broker will need admin credentials on the platform
Notes for implementers
The easiest-lift here is most likely brokerpak + terraform. We can probably get help from @mogul to flatten the learning curve.

This problem is solved by https://github.com/GSA-TTS/cg-egress-proxy

It's really not. This should be a brokerable service, rather than yet-another-component that needs to be understood, deployed, operated, and documented in the application's SSPP. You have a huge opportunity here to reduce toil for your customers!

Good point. I'll reopen it.

Maybe change the title from ASG broker to egress rule broker...? The result for the user is the same: "please bind this app to this provisioned domain allowlist". The implementation just so happens to involve configuring a deployed egress proxy with that allowlist in an egress-unrestricted, platform-managed space, but the user doesn't need to know how it happens.


Comparison to Bokeh.

Have you seen bokeh? It seems to get at what you have tried here in a more general way, which is bridge the gap between JS's visualization/plotting goodness and python's number crunching abilities..

I am aware of Bokeh.
Do you have an example of it bridging the gap between Python and all of the existing D3-based libraries that have been built?


SqlMagic.autocommit=True is not applied to connection options

Running
%load_ext sql
%config SqlMagic.autocommit=True
%sql postgresql://localhost/
%sql CREATE DATABASE new_db

returns the following error:
InternalError: (psycopg2.errors.ActiveSqlTransaction) CREATE DATABASE cannot run inside a transaction block

was this executed in a new session? The  error suggests that the CREATE DATABASE statement was executed inside the middle of a transaction

@edublancas it happens when executing the session here.
According to docs, setting the autocommit option should fix it but according to the implementation, setting SqlMagic.autocommit doesn't affect the connection settings.
I didn't reference the original issue since I'm not sure we want to support this feature and if SqlMagic.autocommit=True and conn.autocommit = True are really equal.

Reference

I looked at the code to understand why this is happening.
It turns out, ipython-sql isn't using the psycopg2's  autocommit feature. %config SqlMagic.autocommit=True sets a flag that causes ipython-sql to run COMMIT after each command; so, if we turn it on, running this:
CREATE DATABASE my_test_db

is the same as running this:
BEGIN; -- executed since psycopg2's autocommit is off
CREATE DATABASE my_test_db; -- executed by the user
COMMIT; -- executed by ipython-sql due to the autocommit=True

Which causes the error:

CREATE DATABASE cannot run inside a transaction block

Psycopg2 issues the initial BEGIN command since the native autocommit flag is off (do not confuse it with our config.autocommit flag), as documented in a warning here.
It's best to rely on the driver's autocommit feature rather than manually issuing a COMMIT command. However, since this is driver-dependent, we should only do it selectively. Perhaps something like this:
if config.autocommit:
    try:
        conn.session.execution_options(isolation_level="AUTOCOMMIT")
    except Exception as e:
        # show some warning
        # commit manually
        manual_commit = True
    else:
        manual_commit = False

Then, use the manual_commit flag to issue a COMMIT command after running each query.

since we closed https://github.com/ploomber/jupysql/pull/117, now we can test this.
the first thing is to check what happens when running:
%load_ext sql
%config SqlMagic.autocommit=True
%sql postgresql://localhost/
%sql CREATE DATABASE new_db

we already know that postgres fails, but we'll see what happens with the others.
then, we must check what happens with @yafimvo's solution: https://github.com/ploomber/jupysql/pull/91
my guess is that the final solution will involve some checking logic as I described in my earlier comment.
since you worked on the integration tests, do you want to takes this @tonykploomber ?

I can take this


Meet errors when work with storm1.1.0+kafka<IP_ADDRESS>

I am trying to run your projects on my own storm cluster. However, I meet some problems and can not solve it. Can you give me a help?
My problem is published on the website stackoverflow.
Storm1.1.0 + kafka<IP_ADDRESS>: NoSuchMethodError&ExceptionInInitializerError

The problems have been solved. The reason of the problem is the version of jar is incompatible with the cluster. However, it still can not work. There is no error in storm worker's log, but the spout can not emit data...


Add "rules" button to dashboard & and make it link to rules page

Again problems with the autolink, I'll fill in what I can by hand.

fdaa99006a14264f3fb3d9d73f213781cbd40fab

560bc04c3a112074c16a432ae1c91b0c6bfba39b


If there is an ampersand sign in xml type comment (summary) the whole comment is not shown is swagger ui.

Create an action that returns an object.
Put an xml comment with the summary tag on a property of the class if that object
Include the ampersand sign into the comment
Go to swagger ui and look at the documentation for the property
The comment won't be displayed

I've used ampersands before with no issues.
Are you encoding the ampersand as & so it makes valid xml?

Oh right. Shows how often I use xml comments.


When I use the "FancyZones" tool to merge two or more application windows, the merged window will exceed the range set by the editor

Microsoft PowerToys version
0.43.0
Running as admin

[X] Yes

Area(s) with issue?
FancyZones
Steps to reproduce
When I use the "FancyZones" tool to merge two or more application windows, the merged window will exceed the range set by the editor.
In other words, the upper boundary of the merged window has exceeded the upper boundary of the display supported by the screen.
No matter what I do, this kind of problem will not be solved.
This problem exists in every version after version "0.37.2".
My operating system is Windows 10 Pro.
✔ Expected Behavior
The merged window should be displayed within the set display range, not beyond the display range supported by the screen.
❌ Actual Behavior
When I use the "FancyZones" tool to merge two or more application windows, the merged window will exceed the range set by the editor.
In other words, the upper boundary of the merged window has exceeded the upper boundary of the display supported by the screen.
No matter what I do, this kind of problem will not be solved.
Other Software
I look forward to the developer can properly solve this problem in the next version.
If you need me to provide screenshots and bug files, please contact me in time.

@C-Dragon8 it would be great if you provide screenshots and a bug report (right-click in the PowerToys tray icon, Report Bug).
You mentioned that you opened two or more application windows, are those the same application windows or different applications? Does it happen with every app or with some?

Thank you for your reply. I have provided you with a screenshot file. Since I have reinstalled version “0.37.2”, the bug report may have been inaccurate.
Regardless of the same application window or different applications, as long as I hold down the “shift” key and drag the windows to merge, once the “shift” key is released, the situation I said yesterday will appear.
This is happening in the applications I usually use, such as Office, Chrome, Typora, and Adobe Acrobat DC.
The part enclosed by the red frame is the range supported by the screen. This happens when merging windows, and when I try to hold down the “shift” key and drag to my divided layout, this situation will not be changed.

@C-Dragon8 it would be great if you provide screenshots and a bug report (right-click in the PowerToys tray icon, Report Bug).
You mentioned that you opened two or more application windows, are those the same application windows or different applications? Does it happen with every app or with some?

Is it still happening on a 0.49.1 version?

Is it still happening on a 0.49.1 version?

I'm very sorry, this bug appeared when Powertoy and Groupy were used at the same time. I forgot to describe this situation clearly before.
During this time, I used Powertoy_FancyZones (to keep up to date) and Groupy (v1.50) at the same time, and I also encountered this problem. Until one day I changed a setting item in Gropuy appearance, which can solve this problem. You can check the picture below.

@C-Dragon8 , Thanks for the update. Closing the issue, since it seems to be caused by an external factor.


ci: remove Kubernetes 1.23 from github action

Removed Kubernetes 1.23 from GitHub action as 1.23 is not supported anymore.
Updates: #3636

@merigifyio backport release-v3.8


VGroup should parse iterables

See #3365

CC @MrDiver

Is this issue still open? I would love to contribute if it is!

Of course, feel free too! If you have any questions, let me know :)

Inspiration can be taken from Grant's commit:
https://github.com/3b1b/manim/commit/1372cf101cc6e97a863c0eb2a58a46155bd3a225

Hey I'm keen to code this up into a pull request — is this issue still open? :)

Feel free too :)

Hey, I made a pull request for this issue (see https://github.com/ManimCommunity/manim/pull/3966), would appreciate any and all feedback! 😄


Export online

The code only migrate data from ES to Loki, is possible or what is the difficult to let job export online?
Instead finish job, listen the current index and put this doc into loki online.
Great job.
Thank you

Hello! Great question. I think it is possible to add such functionality, but needs some refactoring. But I have a question - in my mind the process of continuous logs forwarding from es to loki is just unnecessary - you can simply spin up a promtail for "new" logs in parallel with filebeat and transfer all the old logs using es2loki up until the date when promtail started transferring logs. It is the case of when if you're migrating from Elasticsearch to Loki for example.
What is your case? Why promtail (or any other log collector) seems to be not enough?

Hello, thank you for the reply, yes, in most cases the promtail will be the solution, in my case, the application put the logs directly in ES, and as logstash do not have persistence of position, I can't use it  to expose logs from ES to Loki, and promtail can't use ES as input stream, that is my case.
Thank you


img.shields.io using certificate with SHA-1 signature

Chrome displays a warning about the certificate on https://img.shields.io/ URLs:

which appears to be due to its use of SHA-1 for its signature.  Could that be updated to a certificate using a more up-to-date algorithm?
More info on Chrome's deprecation of SHA-1: http://googleonlinesecurity.blogspot.com/2014/09/gradually-sunsetting-sha-1.html

I think @olivierlacan can help.

Any update on this?

Since the server switch, we are relying on CloudFlare's Full SSL offering, which fixes this issue in Chrome (it is using a SHA-2 certificate).
Do you have information on the trusted CA certificate list that bot-ci relies on?

@espadrine TBH I am only guessing if the problem is with shields.io. We are getting this error in our travis-ci build which uses wget https://img.shields.io/badge/clang_analysis-0-00ff00.svg -O badge.svg:
--2015-09-12 08:20:27--  https://img.shields.io/badge/clang_analysis-0-00ff00.svg
Resolving img.shields.io (img.shields.io)... <IP_ADDRESS>, <IP_ADDRESS>
Connecting to img.shields.io (img.shields.io)|<IP_ADDRESS>|:443... connected.
OpenSSL: error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error
Unable to establish SSL connection.

I just found https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/861137 so it appears it is an ubuntu bug, something to do with TLSv1 + SSLv3.
So, disregard. Thanks

Thanks for investigating the issue further!
Strangely, it does work on my machine (with GNU Wget 1.15 and OpenSSL 1.0.1e 11 Feb 2013).

adding --secure-protocol=TLSv1 solved it for me
so in travis ci script I use
wget -O $BUILD_PATH/build-size.svg "https://img.shields.io/badge/build%20size-${BUILD_SIZE}-green.svg" --secure-protocol=TLSv1


CSUB-619 - Support PersonalSign by metamask

Description of proposed changes

Practical tips for PR review & merge:

[ ] All GitHub Actions report PASS
[ ] Newly added code/functions have unit tests

[ ] Coverage tools report all newly added lines as covered
[ ] The positive scenario is exercised
[ ] Negative scenarios are exercised, e.g. assert on all possible errors
[ ] Assert on events triggered if applicable
[ ] Assert on changes made to storage if applicable

[ ] Modified behavior/functions - try to make sure above test items are covered
[ ] Integration tests are added if applicable/needed

Codecov Report

Merging #1166 (01b1775) into dev (181b1d0) will decrease coverage by 0.68%.
The diff coverage is 0.00%.

:exclamation: Current head 01b1775 differs from pull request most recent head 8a5cb87. Consider uploading reports for the commit 8a5cb87 to get more accurate results

@@            Coverage Diff             @@
##              dev    #1166      +/-   ##
==========================================
- Coverage   74.62%   73.94%   -0.68%
==========================================
  Files          74       74
  Lines       10686    10783      +97
==========================================
  Hits         7974     7974
- Misses       2712     2809      +97

Impacted Files
Coverage Δ

pallets/creditcoin/src/helpers.rs
56.07% <0.00%> (-39.17%)
:arrow_down:

pallets/creditcoin/src/lib.rs
78.81% <0.00%> (-4.83%)
:arrow_down:

pallets/creditcoin/src/types.rs
81.97% <0.00%> (-2.42%)
:arrow_down:

pallets/creditcoin/src/weights.rs
84.84% <0.00%> (-1.58%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Do not show the dots under the dates when showing events

Showing events is convenient, but the dots that then appear for all dates with events clutters the calendar display. Either disable completely the dots or make it an option.
(Can't see how to make this an enhancement request and not an issue.)

Never done any macOS development but I kind of want to take a stab at this!

@sfsam has already implemented this enhancement suggestion in a beta he made available in the high energy thread. Thank you for both implementing this and reducing energy consumption of Itsycal.

might want to close issue if already implemented?

@charlottetan  Right you are. Implemented in Itsycal 0.11.7.


Fix for Cloudinary changes in #a1e538031

Changes in (https://github.com/MadeHQ/silverstripe-cloudinary/)

👍


Port 464 UDP/TCP required to perform Kerberos Password Change

Hello All,
Would be possible to review the list of Ports (UDP/TCP) referred in the "Traffic and Ports" section of this page to include the need to consider the port 464 to allow the Kerberos/AD Password Change protocol to be performed:
https://docs.microsoft.com/en-us/troubleshoot/windows-server/identity/password-change-mechanisms
https://docs.microsoft.com/en-us/troubleshoot/windows-server/identity/config-firewall-for-ad-domains-and-trusts
Thanks for your attention,
Luís.

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

ID: 37e93258-ada8-594a-c725-005e5cf94e7c
Version Independent ID: 995e0663-2823-c258-193a-5904620f805d
Content: Deploy in Active Directory mode - SQL Server Big Data Cluster
Content Source: docs/big-data-cluster/active-directory-deploy.md
Product: sql
Technology: big-data-cluster
GitHub Login: @cloudmelon
Microsoft Alias: melqin

Thanks again @lcanastreiro for taking the time to provide this feedback, your suggestions help improve our documentation. This has been updated and a doc update is in flight.


ability to add releases

Are there any plans to be able to include additional releases in the bosh init deployment?
We have a use case where we would like to provide some additional release tarballs and have them automatically injected into the manifest using file:// urls. This is similar to the way the bosh deployment resource rewrites your manifest to include local release tarballs.
We could do a pull request if you are interested in adding this functionality.

@mmb Sorry for the late response. If you like you can provide a pull request. I will have a look into it.
Cheers
Joek


Linux Support?

What do you think about Linux Support?

It's pretty unlikely to happen anytime soon. The program is doing some Windows specific things that I don't know how to make work on Linux. You could try running the program using Wine, but my guess is that there will probably be some problem somewhere.


Deadcode

https://github.com/tevador/randomx-sniffer/blob/8402301b2a87c31647a28cff9c4b9ed25d9e15e2/src/main.cpp#L147
Won't this if statement always be skipped as its already checked here:
https://github.com/tevador/randomx-sniffer/blob/8402301b2a87c31647a28cff9c4b9ed25d9e15e2/src/main.cpp#L142
?

It seems that you are correct. You can submit a PR to fix it.