Provide way to name compose file when creating new stack

As per the title, currently my compose files are named "docker-compose.yml" which now runs fine in dockge, however if I create a new stack via dockge it creates it in a compose.yaml file. This is rather minor but it would be nice to have a way to provide the filename to use.
I have a local change that should do this via a new environment variable, however I am having trouble building the image locally, when I add the following to my docker compose, I get errors in the log even though the image seems to have completed successfully.
dockge:
    #image: louislam/dockge:1.1.0
    build:
      context: ../../repos/dockge
      dockerfile: docker/Dockerfile

Errors:
Container started
19/11/2023 17:39:19
2023-11-19T17:39:19Z [SERVER] INFO: Welcome to dockge!
19/11/2023 17:39:19
2023-11-19T17:39:19Z [SERVER] INFO: NODE_ENV: production
19/11/2023 17:39:19
2023-11-19T17:39:19Z [SERVER] ERROR: Error: Cannot find 'frontend-dist/index.html', did you install correctly?
19/11/2023 17:39:29
2023-11-19T17:39:29Z [SERVER] INFO: Welcome to dockge!
19/11/2023 17:39:29
2023-11-19T17:39:29Z [SERVER] INFO: NODE_ENV: production
19/11/2023 17:39:29
2023-11-19T17:39:29Z [SERVER] ERROR: Error: Cannot find 'frontend-dist/index.html', did you install correctly?

If I can figure out how to build and then test my change, I will submit a PR to fix the compose filename

Sorry, didn't notice that FR should go in discussions, are you able to move this into a discussion @louislam ?


PasswordEntry's Password parameter binding is incorrect

The PasswordEntry component which is referenced twice on this page seems to be faulty. It's Password parameter is never used inside the component's logic, but it's private password member is referenced both in the markup and the event handler. Because of this, the parent component is notified of changes, but if the parent component sets the initial value of this parameter (like it does in the PasswordBinding example), nothing happens. So currently, it's essentially a one-way binding: from the child to it's parent, but not a two-way one, which it supposed to be.

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

ID: b211df59-e1c9-86c0-c904-31fa3c361e6d
Version Independent ID: 3f912dfc-5ba5-6c6c-ba93-1ae78508a5cc
Content: ASP.NET Core Blazor data binding
Content Source: aspnetcore/blazor/components/data-binding.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @peterbozso ... I might need to get back to you further tomorrow morning because my brain got fried out on Blazor form validation and other tasks this morning 😅. But .... isn't that property set via attribute in the example of the parent ...
<PasswordEntry @bind-Password="password" />

Ok ... I'm baaaaack. The idea here was merely to show the chained bind UP. That 'Not Set' piece was purely for the initial value display in the parent component. It wasn't intend to bind down, IIRC. I mean that it doesn't, of course as you say, so I think that's what I assumed would be understood. It's causing confusion here, so it needs a bit of work.
If you want that behavior, you can get it with the pattern in next example (next section), which avoids the shared component writing to its own parameter by setting up a 2nd property with accessors ...
private string BoundValue
{
    get => Password;
    set => PasswordChanged.InvokeAsync(value);
}

... and then bind the <input> to that ...
<input @oninput="OnPasswordChanged"
        required
        type="@(showPassword ? "text" : "password")"
        value="@BoundValue" />

... then you get a bind down to the child. You can go both ways at that point. Note that even thus far with such an update that password in the child only gets an update when the field is changed, not if updated from the parent on an initial load of the shared component or if the password in the parent is updated, say via an event in the parent --- the field would be updated, but the actual value of password in the child is unchanged until that field gets an oninput fired. I think it's fair to assume tho that if one has a "password entry" shared component that what they're often trying to do is get a little reusable, shared HTML/CSS/form thing going that takes the password from the user and gets the value up to the parent. By the time the parent uses it, the child has validated/modified it or whatever the dev wants to do.
I'll look in the morning and see what I can do to clarify this password entry scenario further. I'll probably write out a bit more on this example and what's up with the 'Not Set' bit. It might be a good idea to go ahead and mention this angle on the 2nd property (and a component avoiding writing to its own parameter). Thanks for commenting on this.


[Bug] AttributeError: 'ConfigDict' object has no attribute 'searcher' for DARTS

Describe the bug
A clear and concise description of what the bug is.
I got AttributeError: 'ConfigDict' object has no attribute 'searcher' when I search on DARTS.
It seems that mmrazor has GreedySearcher() and EvolutionSearcher(), but not for DARTS.
Please help me if I miss something in the config. Thank you very much!
To Reproduce
The command you executed.
CUDA_VISIBLE_DEVICES=0 python ./tools/mmcls/search_mmcls.py   configs/nas/darts/darts_supernet_unroll_1xb64_cifar10.py   none   --work-dir logs/darts

Post related information

The output of pip list | grep "mmcv\|mmrazor\|^torch"
mmcv-full               1.5.0
mmrazor                 0.3.1
torch                   1.12.1+cu116
torchvision             0.13.1+cu116

Your config file if you modified it or created a new one.
No modified config file

Your train log file if you meet the problem during training.
/data/hwzheng/anaconda3/envs/open-mmlab/bin/python3.7 /data/hwzheng/Downloads/pycharm-community-2021.2.3/plugins/python-ce/helpers/pydev/pydevd.py --multiproc --qt-support=auto --client <IP_ADDRESS> --port 42859 --file /data/hwzheng/mmrazor/tools/mmcls/search_mmcls.py configs/nas/darts/darts_supernet_unroll_1xb64_cifar10.py none --work-dir logs/darts
Connected to pydev debugger (build 212.5457.59)
/data/hwzheng/mmrazor/mmrazor/utils/setup_env.py:33: UserWarning: Setting OMP_NUM_THREADS environment variable for each process to be 1 in default, to avoid your system being overloaded, please further tune the variable for optimal performance in your application as needed.
f'Setting OMP_NUM_THREADS environment variable for each process '
/data/hwzheng/mmrazor/mmrazor/utils/setup_env.py:43: UserWarning: Setting MKL_NUM_THREADS environment variable for each process to be 1 in default, to avoid your system being overloaded, please further tune the variable for optimal performance in your application as needed.
f'Setting MKL_NUM_THREADS environment variable for each process '
2022-12-06 15:19:48,920 - mmcls - INFO - Environment info:

sys.platform: linux
Python: 3.7.11 (default, Jul 27 2021, 14:32:16) [GCC 7.5.0]
CUDA available: True
GPU 0: Tesla V100S-PCIE-32GB
CUDA_HOME: /usr/local/cuda
NVCC: Cuda compilation tools, release 11.5, V11.5.50
GCC: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
PyTorch: 1.12.1+cu116
PyTorch compiling details: PyTorch built with:

GCC 9.3
C++ Version: 201402
Intel(R) oneAPI Math Kernel Library Version 2021.4-Product Build 20210904 for Intel(R) 64 architecture applications
Intel(R) MKL-DNN v2.6.0 (Git Hash 52b5f107dd9cf10910aaa19cb47f3abf9b349815)
OpenMP 201511 (a.k.a. OpenMP 4.5)
LAPACK is enabled (usually provided by MKL)
NNPACK is enabled
CPU capability usage: AVX2
CUDA Runtime 11.6
NVCC architecture flags: -gencode;arch=compute_37,code=sm_37;-gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_80,code=sm_80;-gencode;arch=compute_86,code=sm_86
CuDNN 8.3.2  (built against CUDA 11.5)
Magma 2.6.1
Build settings: BLAS_INFO=mkl, BUILD_TYPE=Release, CUDA_VERSION=11.6, CUDNN_VERSION=8.3.2, CXX_COMPILER=/opt/rh/devtoolset-9/root/usr/bin/c++, CXX_FLAGS= -fabi-version=11 -Wno-deprecated -fvisibility-inlines-hidden -DUSE_PTHREADPOOL -fopenmp -DNDEBUG -DUSE_KINETO -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DSYMBOLICATE_MOBILE_DEBUG_HANDLE -DEDGE_PROFILER_USE_KINETO -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-unused-parameter -Wno-unused-function -Wno-unused-result -Wno-unused-local-typedefs -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-psabi -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Werror=cast-function-type -Wno-stringop-overflow, LAPACK_INFO=mkl, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, TORCH_VERSION=1.12.1, USE_CUDA=ON, USE_CUDNN=ON, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=OFF, USE_MPI=OFF, USE_NCCL=ON, USE_NNPACK=ON, USE_OPENMP=ON, USE_ROCM=OFF,
TorchVision: 0.13.1+cu116
OpenCV: 4.6.0
MMCV: 1.5.0
MMCV Compiler: GCC 9.4
MMCV CUDA Compiler: 11.5
MMClassification: 0.24.1+a0aff4d

2022-12-06 15:19:48,921 - mmcls - INFO - Distributed training: False
2022-12-06 15:19:49,765 - mmcls - INFO - Config:
dataset_type = 'CIFAR10'
img_norm_cfg = dict(
mean=[125.307, 122.961, 113.8575],
std=[51.5865, 50.847, 51.255],
to_rgb=False)
train_pipeline = [
dict(type='RandomCrop', size=32, padding=4),
dict(type='RandomFlip', flip_prob=0.5, direction='horizontal'),
dict(
type='Normalize',
mean=[125.307, 122.961, 113.8575],
std=[51.5865, 50.847, 51.255],
to_rgb=False),
dict(type='ImageToTensor', keys=['img']),
dict(type='ToTensor', keys=['gt_label']),
dict(type='Collect', keys=['img', 'gt_label'])
]
test_pipeline = [
dict(
type='Normalize',
mean=[125.307, 122.961, 113.8575],
std=[51.5865, 50.847, 51.255],
to_rgb=False),
dict(type='ImageToTensor', keys=['img']),
dict(type='Collect', keys=['img'])
]
data = dict(
samples_per_gpu=64,
workers_per_gpu=8,
train=dict(
type='CIFAR10',
data_prefix='data/cifar10',
pipeline=[
dict(type='RandomCrop', size=32, padding=4),
dict(type='RandomFlip', flip_prob=0.5, direction='horizontal'),
dict(
type='Normalize',
mean=[125.307, 122.961, 113.8575],
std=[51.5865, 50.847, 51.255],
to_rgb=False),
dict(type='ImageToTensor', keys=['img']),
dict(type='ToTensor', keys=['gt_label']),
dict(type='Collect', keys=['img', 'gt_label'])
]),
val=dict(
type='CIFAR10',
data_prefix='data/cifar10',
pipeline=[
dict(
type='Normalize',
mean=[125.307, 122.961, 113.8575],
std=[51.5865, 50.847, 51.255],
to_rgb=False),
dict(type='ImageToTensor', keys=['img']),
dict(type='Collect', keys=['img'])
],
test_mode=True),
test=dict(
type='CIFAR10',
data_prefix='data/cifar10',
pipeline=[
dict(
type='Normalize',
mean=[125.307, 122.961, 113.8575],
std=[51.5865, 50.847, 51.255],
to_rgb=False),
dict(type='ImageToTensor', keys=['img']),
dict(type='Collect', keys=['img'])
],
test_mode=True),
split=True)
checkpoint_config = dict(interval=1)
log_config = dict(interval=100, hooks=[dict(type='TextLoggerHook')])
dist_params = dict(backend='nccl')
log_level = 'INFO'
load_from = None
resume_from = None
workflow = [('train', 1)]
model = dict(
type='mmcls.ImageClassifier',
backbone=dict(
type='DartsBackbone',
in_channels=3,
base_channels=16,
num_layers=8,
num_nodes=4,
stem_multiplier=3,
out_indices=(7, )),
neck=dict(type='GlobalAveragePooling'),
head=dict(
type='LinearClsHead',
num_classes=10,
in_channels=256,
loss=dict(type='CrossEntropyLoss', loss_weight=1.0),
topk=(1, 5),
cal_acc=True),
pretrained=None)
algorithm = dict(
type='Darts',
architecture=dict(
type='MMClsArchitecture',
model=dict(
type='mmcls.ImageClassifier',
backbone=dict(
type='DartsBackbone',
in_channels=3,
base_channels=16,
num_layers=8,
num_nodes=4,
stem_multiplier=3,
out_indices=(7, )),
neck=dict(type='GlobalAveragePooling'),
head=dict(
type='LinearClsHead',
num_classes=10,
in_channels=256,
loss=dict(type='CrossEntropyLoss', loss_weight=1.0),
topk=(1, 5),
cal_acc=True))),
mutator=dict(
type='DartsMutator',
placeholder_mapping=dict(
node=dict(
type='DifferentiableOP',
with_arch_param=True,
choices=dict(
zero=dict(type='DartsZero'),
skip_connect=dict(
type='DartsSkipConnect',
norm_cfg=dict(type='BN', affine=False)),
max_pool_3x3=dict(
type='DartsPoolBN',
pool_type='max',
norm_cfg=dict(type='BN', affine=False)),
avg_pool_3x3=dict(
type='DartsPoolBN',
pool_type='avg',
norm_cfg=dict(type='BN', affine=False)),
sep_conv_3x3=dict(
type='DartsSepConv',
kernel_size=3,
norm_cfg=dict(type='BN', affine=False)),
sep_conv_5x5=dict(
type='DartsSepConv',
kernel_size=5,
norm_cfg=dict(type='BN', affine=False)),
dil_conv_3x3=dict(
type='DartsDilConv',
kernel_size=3,
norm_cfg=dict(type='BN', affine=False)),
dil_conv_5x5=dict(
type='DartsDilConv',
kernel_size=5,
norm_cfg=dict(type='BN', affine=False)))),
node_edge=dict(
type='DifferentiableEdge', num_chosen=2,
with_arch_param=False))),
retraining=False,
unroll=True)
optimizer = dict(
architecture=dict(type='SGD', lr=0.025, momentum=0.9, weight_decay=0.0003),
mutator=dict(type='Adam', lr=0.0003, weight_decay=0.001))
optimizer_config = None
lr_config = dict(
policy='CosineAnnealing', min_lr=0.001, freeze_optimizers=['mutator'])
runner = dict(type='MultiLoaderEpochBasedRunner', max_epochs=50)
custom_hooks = [dict(type='SearchSubnetHook', interval=1, priority=70)]
find_unused_parameter = True
use_ddp_wrapper = True
work_dir = 'logs/darts'
/data/hwzheng/mmrazor/tools/mmcls/search_mmcls.py:150: UserWarning: Class names are not saved in the checkpoint's meta data, use imagenet by default.
warnings.warn('Class names are not saved in the checkpoint's '
2022-12-06 15:19:53,676 - mmcls - INFO - build search...
Traceback (most recent call last):
File "/data/hwzheng/Downloads/pycharm-community-2021.2.3/plugins/python-ce/helpers/pydev/pydevd.py", line 1483, in _exec
pydev_imports.execfile(file, globals, locals)  # execute the script
File "/data/hwzheng/Downloads/pycharm-community-2021.2.3/plugins/python-ce/helpers/pydev/_pydev_imps/_pydev_execfile.py", line 18, in execfile
exec(compile(contents+"\n", file, 'exec'), glob, loc)
File "/data/hwzheng/mmrazor/tools/mmcls/search_mmcls.py", line 184, in
main()
File "/data/hwzheng/mmrazor/tools/mmcls/search_mmcls.py", line 171, in main
cfg.searcher,
File "/data/hwzheng/anaconda3/envs/open-mmlab/lib/python3.7/site-packages/mmcv/utils/config.py", line 513, in getattr
return getattr(self._cfg_dict, name)
File "/data/hwzheng/anaconda3/envs/open-mmlab/lib/python3.7/site-packages/mmcv/utils/config.py", line 49, in getattr
raise ex
AttributeError: 'ConfigDict' object has no attribute 'searcher'

Other code you modified in the mmrazor folder.
[here]

Additional context
Add any other context about the problem here.
[here]

Thank you for your issue.

The mmrazor:searcher is not required for DARTS. DARTS is known as a classical NAS algorithm with constructing a matrix (refers to alpha in the paper) to build the search space, the structure of a single subnet in the built supernet of DARTS can be easily parsed according to the value of the mentioned matrix after supernet training, or so to speak, DARTS searches the subnet during supernet training (alternate optimization). The process is as follows:

By the way, you are welcomed to try our new branch mmrazor:dev-1.x instead of branch master to get more features with OpenMMLab 2.0 project~

Thanks! That's great! I will try it.


show kr/l

Checklist

[X] I have filled out the template to the best of my ability.
[X] This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
[X] This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.
please fix the sensor to showing kr/l even in history and not only like now it shows only 16,88
Describe the solution you'd like
I want it to show like 16,88 kr/l even in history tab
Describe alternatives you've considered
.
Additional context
.

Thank you for creating the issue, I will try to implement the unit as soon as possible

The issue has been fixed in 1.2.0


fix(datepicker): time zone bug

This bug is quite difficult to reproduce because it depends on OS, OS updates, browser, current timezone and even current date.
As I understand, it's connected with daylight savings.
The bug was discussed here: #1098.
The problem with repeated days seems to be fixed here: 7f4b40eb8bc57f03bd306330a6ad227790c33f27 (line 145) . But the problem with repeated months and years still exists.
Some screenshots:

OS: Windows 7; current day: December 10, 2014; current time zone: +6 GMT; browser: Firefox 36.0.4
Wrong January:

Wrong 2014:

OS: Debian Jessie / Ubuntu 14.04; current day: December 10, 2014 / March 24, 2015; current time zone: +3 GMT / +6 GMT; browser: Firefox 31.5.0, 33.0, 34.0.
Wrong April:

You can see the reason of the bug in this piece of code:
var date = new Date(2014, 0, 1);
console.log(date.getFullYear(), date.getMonth(), date.getDate(), date.getHours());

The expected result is "2014 0 1 0", but in some cases it will be "2013 11 31 23".
One more example. I printed the dates which is used to display months in monthpicker:
// February: correct
{
	"date":"Date {Wed Feb 01 1984 00:00:00 GMT+0600 (OMST)}",
	"label":"February",
        . . .
}
// March: correct
{
	"date":"Date {Thu Mar 01 1984 00:00:00 GMT+0600 (OMST)}",
	"label":"March",
        . . .
}
// April: error, 1 hour is missing
{
	"date":"Date {Sat Mar 31 1984 23:00:00 GMT+0600 (OMST)}",
	"label":"March",
        . . .
}
// May: correct
{
	"date":"Date {Tue May 01 1984 00:00:00 GMT+0700 (OMSST)}",
	"label":"May",
        . . .
}

Discussions of this bug can be found on the Internet. Some of them:
http://stackoverflow.com/questions/5859959/dst-problem-storing-date-in-javascript-date-object
https://code.google.com/p/chromium/issues/detail?id=417640
I've implemented a possible workaround. We should determine whether a date is created with the bug. If the bug arises then we just add 2 hours to the date (adding one hour has no effect in this case). It should guarantee the correct handling of all the bug cases.
Fixes #3079

Instead of manage date/time problem manually, maybe it would be a good decision to use moment.js?

This is interesting - at first I was skeptical about the solution, but thinking about it some more in the context to the datepicker automatically setting the hours to 0, this might be a sufficient fix.
The only question is whether this is sufficient for us - this would be a breaking change if a developer is supporting the entering of a time.

Interesting. This problem arises because the calling the new Date() hits a non-existent time in the local timezone. Hence, the time is adjusted forward/backwards to pick a time that exists.
I think this is a good reason to refactor and remove the need to even create these Date objects. It looks like they're just created so that they can be used in the click handler. There's no need to use Date objects in the month picker since there's always 12 months and it's always Jan - Dec. We can instead add a method that allows you to set the month / year of the current model object instead of providing a Date object to replace it with.
By removing the need for Date objects, we should isolate the timezone issues to the select method.
May need to think about this more, but this is what I've come up with.

With regards to this solution, this could work. But we'll want to remove this code soon because of the reasons outlined above.

I think breaking changes should wait until we split the datepicker into a different repository.  I would rather the datepicker just delegated this behavior to moment.js, it would address most of these woes.

I plan on merging this today, but one thing I plan on doing with the datepicker is modifying it to allow usage of a custom parser (i.e. moment.js), with the fallback being the current behavior.

Oops, forgot the PR # in my rebasing...this has landed as f14120149b9f4ff67e8abb8907b5ab973fe3987f


Changed tabs count from ~ (tilde)  to first two numbers ending with for tabs>99

Task/Issue URL: https://github.com/duckduckgo/Android/issues/1331
Tech Design URL:
CC:
Description:
When the tabs count exceeds 99, the app shows a ~  (Tilde) sign signifying problems as addressed in issue #1331.
This PR proposed changes as shown below:

Changed tabs from ~ to the first two digits of the number of tabs opened ending with a  . (dot) where . signifying a short form of  .... (too many dots).

Points to be considered:

[x] It is more human-understandable.

Example:

1000 can be shown as 10.
5555 can be shown as 55.

Steps to test this PR:

Install App.
Keep opening tabs until the tabs count is greater than 99.

Internal references:
Software Engineering Expectations
Technical Design Template

For more discussion about the issue check #1334.

Thanks @Akshit6828, we only accept contributions for Issues or Feature requests labeled as help wanted.
Please refer to our contribution guidelines for more details.


Refresh page using F5 or CTRL + R is not requesting with complete params

My controller method needs id to fetch data from database table which will be sent in params. When using turbolinks, when refresh page using the key F5 and CTRL + R the params to the controller contains only action and controller name only not the id.
Note: Without using turbolinks when refreshing page using  the key F5 and CTRL + R, I was getting prompt as "The page you are searching for uses the information you entered. If you return to this page, you may have to try again. Do you want to continue?". After confirming, the request to server is with the complete params.

My controller method needs id to fetch data from database table which will be sent in params.

Is this a POST? If so, you might be experiencing the bug described in #495

@domchristie  Yes, It is a POST request. I have the updated turbolinks with the fix but doesnot work for me.

@domchristie No its a GET request.

Are you able to share an example which demonstrates the problem? Thanks

Here is the demontration code for that error
https://github.com/kumaranubhaw/default_refresh_page_error
For setup please read the README Note.
Thank you

Thanks for taking the time to create an example. The form you are using does perform a POST request, so you are seeing the issue described in #495
By default the Rails form_tag helper creates a form with method="post". To make this a GET, change your view template to look something like:
<%= form_tag({ :action => 'get_detail' }, :method => :get) do %>
…
<% end %>

This will put the form parameters in the browser's address bar, so when refreshing, the parameters are sent as expected. I hope that helps.

Thank you for the help, It worked fine after using the get method in form_tag.


"internal" directories no longer show subdirectory listing

This used to work not long ago, and I suspect (but haven't verified) that this is related to the recent change in #402. /cc @rakyll
Normally, directories that have no .go files (i.e., no Go package) but contain subdirectories with Go packages are displayed on godoc.org as a simple directory listing. E.g.:

https://godoc.org/compress
https://godoc.org/go

However, now, if the directory is named "internal", then it always appears without any subdirectories, e.g.:

https://godoc.org/go/internal
https://godoc.org/cmd/go/internal

This bug hurts usability because it's no longer possible to reliably traverse, explore, discover, find packages on godoc.org. Also, it makes certain existing links useless. E.g., start at https://godoc.org/go/internal/gcimporter, and click on "internal" link on top:

You'll get to an empty page.
I used examples from standard library, but this affects all Go packages, including 3rd party ones.

:( Do we want to revert the previous change? I may find sometime later today to fix if it is not critical.

If no one has time to get to this soon, I think it's better to revert to bring things back to a functional (albeit more noisy) state. Then, the original CL can be iterated on and re-applied without this bug and extra test cases for it.

I sent a CL: https://go-review.googlesource.com/c/gddo/+/93196.

I reverted it to an earlier version.

If no one has time to get to this soon, I think it's better to revert to bring things back to a functional (albeit more noisy) state. Then, the original CL can be iterated on and re-applied without this bug and with extra test cases for it.

I sent a revert CL 130937. When merged, we can re-open #402 for further tracking of that issue.


dev-cmd: add pr-automerge

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew tests with your changes locally?

This is the last developer command needed in our master plan in https://github.com/Homebrew/brew/issues/6255#issuecomment-589916227. brew pr-automerge checks homebrew/core for pull requests with passing tests and the "ready to merge" label. Optionally add --publish to run brew pr-publish on those as well.
After this is merged, we can add this as a scheduled task in homebrew/core.
Example output:
% brew pr-automerge --publish --verbose --debug
==> Searching: is:pr is:open repo:Homebrew/homebrew-core label:"ready to merge" -label:"do not merge" status:success
/usr/bin/curl --disable --globoff --show-error --user-agent Homebrew/2.2.12-58-g9e4dfaf\ \(Macintosh\;\ Intel\ Mac\ OS\ X\ 10.15.4\)\ curl/7.64.1 --retry 3 --location https://api.github.com/search/issues\?q=is\%3Apr\+is\%3Aopen\+repo\%3AHomebrew\%2Fhomebrew-core\+label\%3A\%22ready\+to\+merge\%22\+-label\%3A\%22do\+not\+merge\%22\+status\%3Asuccess\&per_page=100 --header Accept:\ application/vnd.github.v3\+json --write-out '
'\%\{http_code\} --header Accept:\ application/vnd.github.antiope-preview\+json --user jonchang:****** --dump-header /private/tmp/github_api_headers20200413-68197-sa8ds8
==> 4 matching pull requests:
#52984: xerces-c 3.2.3
#52890: emscripten 1.39.12
#52817: gtk+3 3.24.18
#52797: qpdf 10.0.1
==> Running:
  brew pr-publish \
    https://github.com/Homebrew/homebrew-core/pull/52984 \
    https://github.com/Homebrew/homebrew-core/pull/52890 \
    https://github.com/Homebrew/homebrew-core/pull/52817 \
    https://github.com/Homebrew/homebrew-core/pull/52797
/usr/local/bin/brew pr-publish https://github.com/Homebrew/homebrew-core/pull/52984 https://github.com/Homebrew/homebrew-core/pull/52890 https://github.com/Homebrew/homebrew-core/pull/52817 https://github.com/Homebrew/homebrew-core/pull/52797
==> Dispatching homebrew/core pull request #52984
==> Dispatching homebrew/core pull request #52890
==> Dispatching homebrew/core pull request #52817
==> Dispatching homebrew/core pull request #52797

On the practical applications of this new workflow:

Maintainers add a "ready to merge" label.
This Action picks all of those on a schedule and runs brew pr-publish for each, closing the PRs and the software and bottles are updated.

What's the interaction with brew pr-publish run by a maintainer? Does that go away entirely?
What about the interaction with brew pr-pull for if users don't know how to squash their commits? Do we just not label a PR? Should we instead remove brew pr-pull and be more liberal in force-pushing contributors' branches to make commit messages confirm to standard and squash commits?
Also, would bottle :unneeded formulae also follow this process? These are the only formulae that currently show as "merged" (purple) in the UI which is quite satisfying for users. We don't want to use Actions runtime for those unnecessarily, I feel.

What's the interaction with brew pr-publish run by a maintainer? Does that go away entirely?

It could go away entirely, but I can definitely see for some people's workflows where running brew pr-publish is faster than adding labels to pull requests and such. I'm inclined to keep it in until we're more confident with this approach.

What about the interaction with brew pr-pull for if users don't know how to squash their commits? Do we just not label a PR?

For now, yeah. I'm thinking of digging out the logic in brew pull --bump and making it a bit smarter so we can do something similar for our workflow automation.

Should we instead remove brew pr-pull and be more liberal in force-pushing contributors' branches to make commit messages confirm to standard and squash commits?

I think brew pr-pull will still be needed for these cases, at least until our new ML/AI commit system (trained on over a decade of commit messages and using $10,000 of Amazon credits) is online.

Also, would bottle :unneeded formulae also follow this process? These are the only formulae that currently show as "merged" (purple) in the UI which is quite satisfying for users. We don't want to use Actions runtime for those unnecessarily, I feel.

It would be cool if pr-publish checked for bottle :unneeded and executed the GitHub API "Rebase and merge" button, which is how I envision that feature going.

For now, yeah. I'm thinking of digging out the logic in brew pull --bump and making it a bit smarter so we can do something similar for our workflow automation.

Yeh, I could see squashing to the "recommended commit message format" being the right thing for most cases. We could perhaps preserve the original commit message in the commit body.

Thanks for the reviews!


DocsArchive-1.0.20260.2Auto archive content

Auto archive content from https://github.com/opstestppe1/E2E_DocsArchive.git

Docs Build status updates of commit b780cba:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

.openpublishing.redirection.json
:white_check_mark:Succeeded

e2e_archiveDocs_20200916193103/TOC.yml
:white_check_mark:Succeeded
View

e2e_archiveDocs_20200916193103/breadcrumb/e2e_archiveDocs_20200916193103/toc.yml
:white_check_mark:Succeeded

e2e_archiveDocs_20200916193103/docfx.json
:white_check_mark:Succeeded

e2e_archiveDocs_20200916193103/fallback.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


[FEATURE] allow 'using' to be... used

using does work. it just does not work in an autocomplete sense. would be cool ;)

You might want to post that at the vshaxe issue tracker instead.

actually yeah, you are right. will post ;)

OK, closing here. Please check with current vshaxe, Kode Studio's vshaxe is a few months old.


SPM-4 Relays don't show accurate state

Hi,
I integrated my SPM 4 relay properly but when I turn off a switch, it automatically switches back to ON state.
So it doesn't show the actual state of the relays.
Here's the diagnostic :
{
  "home_assistant": {
    "installation_type": "Home Assistant OS",
    "version": "2023.3.6",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.10.10",
    "docker": true,
    "arch": "aarch64",
    "timezone": "Europe/Brussels",
    "os_name": "Linux",
    "os_version": "5.15.84-v8",
    "supervisor": "2023.04.0",
    "host_os": "Home Assistant OS 9.5",
    "docker_version": "20.10.22",
    "chassis": "embedded",
    "run_as_root": true
  },
  "custom_components": {
    "hacs": {
      "version": "1.31.0",
      "requirements": [
        "aiogithubapi>=22.10.1"
      ]
    },
    "sonoff": {
      "version": "3.5.1",
      "requirements": [
        "pycryptodome>=3.6.6"
      ]
    },
    "linkplay": {
      "version": "3.1.8",
      "requirements": [
        "async-upnp-client>=0.27",
        "validators~=0.12",
        "chardet>=4.0.0"
      ]
    }
  },
  "integration_manifest": {
    "domain": "sonoff",
    "name": "Sonoff",
    "config_flow": true,
    "documentation": "https://github.com/AlexxIT/SonoffLAN",
    "issue_tracker": "/api/sonoff/f6fcf76b-14b4-4fdd-8f5f-d84aa3854401",
    "codeowners": [
      "@AlexxIT"
    ],
    "dependencies": [
      "http",
      "zeroconf"
    ],
    "requirements": [
      "pycryptodome>=3.6.6"
    ],
    "version": "3.5.1",
    "iot_class": "local_push",
    "is_built_in": false
  },
  "data": {
    "version": "122751c",
    "cloud_auth": true,
    "config": null,
    "options": {
      "mode": "auto",
      "debug": true
    },
    "errors": [
      {
        "name": "custom_components.sonoff.core.ewelink.cloud",
        "message": [
          "Cloud WS Connection error: Cannot connect to host eu-dispa.coolkit.cc:443 ssl:default [Try again]"
        ],
        "level": "WARNING",
        "source": [
          "custom_components/sonoff/core/ewelink/cloud.py",
          272
        ],
        "timestamp":<PHONE_NUMBER>.1796143,
        "exception": "",
        "count": 10,
        "first_occurred":<PHONE_NUMBER>.4742436
      }
    ],
    "device": {
      "uiid": 128,
      "params": {
        "bindInfos": "***",
        "version": 8,
        "rssi": -37,
        "sledOnline": "on",
        "fwVersion": "1.2.0",
        "subChipFwVer": "1.2.0",
        "subDevices": [
          {
            "subDevId": "7f64474c3831300e35363734",
            "deviceid": "ab300005b3",
            "uiid": "130",
            "index": 0
          },
          {
            "subDevId": "6857474c3831300e35363734",
            "deviceid": "ab300005b4",
            "uiid": "130",
            "index": 0
          },
          {
            "subDevId": "443e474c3831300e35363734",
            "deviceid": "ab300005b5",
            "uiid": "130",
            "index": 0
          },
          {
            "subDevId": "5b2d474c3831311947313130",
            "deviceid": "ab300005b6",
            "uiid": "130",
            "index": 0
          }
        ],
        "timeZone": 2,
        "only_device": {
          "ota": "success"
        }
      },
      "model": "SPM-Main",
      "online": true,
      "local": null,
      "localtype": null,
      "host": null,
      "deviceid": "10014a70eb"
    }
  }
}

I already checked some similar issues with the SPM here but it said that it's been fixed in 3.5.1 but on my side it still doesn't work.
Could you help?
Thank you so much :)

You need to collect integration debug logs

Hi,
Thanks for the fast answer and sorry for not sending it right away.
Here is the debug log :
f6fcf76b-14b4-4fdd-8f5f-d84aa3854401.txt
Hope you'll find something.
Thank you

Hi there,
Any news on that?
We would really appreciate if you could look it up when you have time, we can also send you the devices if you want to make some testings.
Thanks a lot

Hi,
Any news on that subject ? We are willing to work closely and supply you all the necessary infos.
Would be greatly appreciated.
Thank you

Yes. I can confirm problem. It's similar like for zigbee devices. Cloud doesn't return new devices state...

If you share this device with my account<EMAIL_ADDRESS>and allow me to switch on/off one of channels - I can try to fix this.

Hello, i am currently facing a same issue. I have 3 SPM-4Relays connected to a SPM-Main and at random times even though the devices are connected and i can see them through app i cannot trigger them ON/OFF. I have to press the rescan button from the SPM-Main device inside the app. How did you fix the issue from the @EscapeRush ? Maybe i can apply the same fix. Thanks


CoreDispatcherScheduler does not work in UWP Single Process Model Background Activation

The CoreDispatcherScheduler relies on DispatcherTimer for its implementation. DispatcherTimer only works when the app is running in the foreground with an activated main CoreApplicationView CoreWindow.
Repro steps:

In a UWP app, override OnBackgroundActivated in App.xaml.cs:

        protected override void OnBackgroundActivated(BackgroundActivatedEventArgs args)
        {
            base.OnBackgroundActivated(args);
            Debug.WriteLine($"[App] Background started");
            var deferral = args.TaskInstance.GetDeferral();
            var sas = new SingleAssignmentDisposable();
            sas.Disposable = Observable.Timer(
                    DateTimeOffset.Now,
                    TimeSpan.FromTicks(166666),
                    new CoreDispatcherScheduler(CoreApplication.MainView.Dispatcher))
                .Subscribe(tick =>
                {
                    Debug.WriteLine($"[App] Tick {tick}");
                    if (tick == 10)
                    {
                        sas.Dispose();
                        deferral.Complete();
                    }
                });
        }

Register the app to trigger a background activation off some system activity (e.g., time zone change):

            var requestTask = await BackgroundExecutionManager.RequestAccessAsync().AsTask().ConfigureAwait(false);
            var builder = new BackgroundTaskBuilder();
            builder.Name = "Registration";
            var trigger = new SystemTrigger(SystemTriggerType.TimeZoneChange, false);
            builder.SetTrigger(trigger);
            builder.Register();

Run the app, register the background task, then close the app
Perform the system activity to trigger the background task (e.g., change time zone)

The result is that only the first Timer tick will fire, you can track the activity using DebugView.

Is this still an issue?

It can probably be closed, I don't know if it's still an issue, but it's not a priority bug for the project I was working on anymore.

Thanks @rozele for the confirmation.


Terraform changes to get access token via client credentials (#20)

Review comments addressed

Adding files for hosting the terraform provider

Added files to host the terraform provider  (#9)

Review comments addressed

Adding files for hosting the terraform provider

Updated the Address in main

Changed the address of the provider (#10)

Review comments addressed

Adding files for hosting the terraform provider

Updated the provider address in tf files

Updated the provider address in tf files (#11)

Review comments addressed

Adding files for hosting the terraform provider

Updated the Address in main

Updated the provider address in tf files

Updated the address of the terraform provider

Added tests for users and service account

change provider address to registry.terraform.io

fix api_token access issue

Fix related to service account create and update

Fix related to service account create and update

[MDSS-1658]: Terraform changes to get access token

[MDSS-1658]: Updated the docs

Ok

run go generate to update user resource docs


Updating Speed in Domoticz incorrect

          Hi,

I do not agree... the speed is recorded as it should and reported to the rawdata.
Is it possible that domoticz just stores the value every 5 minutes... I did ride the bike during 5 minutes. That is less then the next interval at 10 min...

Originally posted by @Sloeber71 in https://github.com/TurnOfAFriendlyCard/Domoticz-GPSLogger-Plugin/issues/6#issuecomment-2034028415

See additional remark: https://github.com/TurnOfAFriendlyCard/Domoticz-GPSLogger-Plugin/issues/6#issuecomment-2034196660

Took a test yesterday and rode a public transport bus for 40 minutes. The speed is logged at the interval set in GPSLogger. The speed is also updated live in the Speed device. But it is true that Domoticz only stores 1 registration every 5 minutes in the database. This is a domoticz problem.

Chart

DateTime
Custom Sensor

3/04/2024   13:20
0

3/04/2024   13:25
3

3/04/2024   13:30
39

3/04/2024   13:35
32

3/04/2024   13:40
31

3/04/2024   13:45
42

3/04/2024   13:50
62

3/04/2024   13:55
36

3/04/2024   14:00
4

3/04/2024   14:05
2

3/04/2024   14:10
11

3/04/2024   14:15
0

3/04/2024   14:20
0

3/04/2024   14:25
0

3/04/2024   16:30
0

3/04/2024   16:35
0

3/04/2024   16:40
58

3/04/2024   16:45
41

3/04/2024   16:50
27

3/04/2024   16:55
6

3/04/2024   17:00
46

3/04/2024   17:05
0

3/04/2024   17:10
0

Did some digging on the forum:
https://www.domoticz.com/forum/viewtopic.php?t=10183
The log inverval can be changed, but this must be done in source ... then re-compile is needed
Just thinking how this will affect the load, db size, etc...


Routing Stage Failing

Describe the bug
While i run eth_top design at routing stage get stopped with below error.
Notice 0: Split top of 1 T shapes.
Notice 0: Split top of 3 T shapes.
Notice 0: Split top of 1 T shapes.
Notice 0: error, net 26404, shorts to another term
Notice 0: wire point<PHONE_NUMBER>00)
Notice 0:  clknet_leaf_256_wb_clk_i
Error 0: order_wires failed
Notice 0: error, net 26404, shorts to another term
Notice 0: wire point<PHONE_NUMBER>00)
Notice 0:  clknet_leaf_256_wb_clk_i
Error 0: order_wires failed
Notice 0: error, net 26404, shorts to another term
Notice 0: wire point<PHONE_NUMBER>00)
Notice 0:  clknet_leaf_256_wb_clk_i
Error 0: order_wires failed
Notice 0: error, net 26404, shorts to another term
Notice 0: wire point<PHONE_NUMBER>00)
Notice 0:  clknet_leaf_256_wb_clk_i
Error 0: order_wires failed
Notice 0: error, net 26404, shorts to another term
Notice 0: wire point<PHONE_NUMBER>00)
Notice 0:  clknet_leaf_256_wb_clk_i
Error 0: order_wires failed
Notice 0: error, net 26404, shorts to another term
Notice 0: wire point<PHONE_NUMBER>00)
Notice 0:  clknet_leaf_256_wb_clk_i
Error 0: order_wires failed
To Reproduce
Steps to reproduce the behavior:

Go to ' https://github.com/vijayank88/vijayank88/blob/main/eth_top.tar.xz '
Click on 'eth_top.tar.xz'
Scroll down to 'untar and goto eth_top/runs/ untar coreModify.tar.xz coreModify2/logs/routing/fastroute.log'
See fastroute.log end of the file for error message

Expected behavior
Expecting run_routing stage to complete successfully.
Desktop (please complete the following information):

OS: [e.g. Centos 7]
Openlane Version [e.g. v0.22]
open_pdks Version: [open_pdks 1d93a6bd9d6e481acfdf88f26aa3bb0600303d98]
skywater-pdk Version: [skywater-pdk 00bdbcf4a3aa922cc1f4a0d0cd8b80dbd73149d3]

Additional context
I am able to run successfully in OpenROAD flow . If I add same design in openLane setup its getting stopped at routing stage

"To Reproduce" is a description of how to see the log file not how to reproduce the problem (ie run the tool to produce that result).
@dralabeing if "I am able to run successfully in OpenROAD flow" why is this an OR issue?

@maliberty this is to address the Notice message which originates in OpenROAD, does it not?

@dralabeing "While i run the_top design at routing stage get stopped with below error."   Is this just about the formatting of the message or the failure?  I assumed the later.

@maliberty This is both an error in routing through the OpenLane flow and the formatting as indicated by the report. Not sure, why the OR standalone flow passes successfully.
@vijayank88 : Can you please clarify if the OR flow passed successully? Please provide the log file for this section of the test.

@dralabeing messaging is covered by https://github.com/The-OpenROAD-Project/OpenROAD/issues/907.

@dralabeing
OpenLane flow i used with sky130A library. It failing at routing stage with the message "Error 0: order_wires failed
Notice 0: error, net 26404, shorts to another term
Notice 0: wire point<PHONE_NUMBER>00)
Notice 0: clknet_leaf_256_wb_clk_i"
In OpenRoad flow i used with nangate45 platform. Its completed successfully. Refer below links for logs.
https://github.com/vijayank88/vijayank88/blob/main/logs.tar.xz
Thanks.,

Running on a different pdk is completely different.  You should use either sky130hd or sky130hs (I'm not sure which library OL uses) in ORFS to reproduce the issue.

I'm not familiar enough with OL to figure out how to take your tar and turn it into a run of openroad that I can look at.  Would you or @donn provide steps.

@maliberty
Thanks for your time to debug this issue. In ORFS no issues to run my eth_top design. Problem comes with OpenLane Flow.
Please follow below steps to run my design.
step 1: Hope you have installed openlane flow: https://github.com/The-OpenROAD-Project/OpenLane#installation-notes
step 2: change your current directory into openlane and start mount openlane : $ make mount
step 3: Create new design setup for eth_top design: bash$ ./flow.tcl -design eth_top -init_design_config
Now check the path ./designs/eth_top/config.tcl and src directory created.
Edit eth_top/config.tcl and  change CLOCK_PORT name "clk" to "wb_clk_i"
Untar https://github.com/vijayank88/vijayank88/blob/main/eth_top.tar.xz this file and src/* netlist file copy under ./designs/eth_top/src/
Now design setup is ready. By default OL takes sky130A PDK library. Type the below command to run the design in OpenLane.
step 4: bash$ ./flow.tcl -design eth_top
Check the status its completing or stops with error message as I posted.
Thanks...

Packaged. Ball's in your field, OR team.

@donn Yosys default core size 940-955 taken with clock period 10ns. I've manually increased core size to 1200 -1250 with clock of 15ns able to pass routing stage. Testing with 10ns clock period again. Thanks...

@donn i am able to complete eth_top design routing with core area 960-980 with 10ns clock period. Also made repair_design post placement. Able to generate GDSII now without any stop.
Default core taken from OLFS is 940-955.

Packaged. Ball's in your field, OR team.

Thanks @Donn- @maliberty - Could you please take a look?

OR team confirms issue is fixed in HEAD: would require merging an OpenROAD update to fix this. Will investigate.

@vijayank88 Can you rerun this with ORFS to verify before the merge?

@dralabeing At the time of GH issue filing I checked with ORFS with sky130A_hd PDK RTL to GDSII generation working fine. Issue comes from OLFS with sky130A PDK.

The original testcase did not work in the OL flow- default core size fails. The ORFS message is more actionable the allows flow completion through modification of config.tcl for die size.
There error messages in OL  need to be clear and actionable and issued earlier in the flow.

#547, please don't reopen stale issues for requests already captured.

@donn  today updated OL repo at my end and got below error message for this eth_top design.
[INFO GRT-0003] Macros: 0
[INFO GRT-0004] Blockages: 2566655
[INFO GRT-0001] Minimum degree: 2
[INFO GRT-0002] Maximum degree: 299
[INFO GRT-0017] Processing 1733061 blockages on layer li1.
[INFO GRT-0017] Processing 336278 blockages on layer met1.
[INFO GRT-0017] Processing 13 blockages on layer met4.
[INFO GRT-0017] Processing 13 blockages on layer met5.
[INFO GRT-0009] Nets to reroute: 32103.
[INFO GRT-0101] Running extra iterations to remove overflow.
[WARNING GRT-0164] Initial grid wrong y1 x1 [132 34], net start [56 60] routelen 46.
[WARNING GRT-0165] End grid wrong y2 x2 [132 34], net start [18 52] routelen 46.
[ERROR GRT-0167] Invalid 2D tree for net 19655.
Error: or_groute.tcl, 68 GRT-0167
[ERROR]: during executing: "openroad -exit /openLANE_flow/scripts/openroad/or_groute.tcl |& tee >&@stdout /openLANE_flow/designs/eth_top/runs/6thRun/logs/routing/18-fastroute.log"
[ERROR]: Exit code: 1
[ERROR]: Last 10 lines:
child process exited abnormally
[ERROR]: Please check openroad  log file
[ERROR]: Dumping to /openLANE_flow/designs/eth_top/runs/6thRun/error.log
[INFO]: Calculating Runtime From the Start...
[INFO]: flow failed for eth_top/31-08_16-07 in 0h13m7s
[INFO]: Generating Final Summary Report...
[ERROR]: during executing: "openroad -python /openLANE_flow/report_generation_wrapper.py -d /openLANE_flow/designs/eth_top -dn eth_top -t 6thRun -o /openLANE_flow/designs/eth_top/runs/6thRun/reports/final_summary_report.csv -m /openLANE_flow/designs/eth_top/runs/6thRun/reports/manufacturability_report.rpt -rs /openLANE_flow/designs/eth_top/runs/6thRun/reports/runtime_summary_report.rpt -r /openLANE_flow/designs/eth_top/runs/6thRun"
[ERROR]: Exit code: 1
[ERROR]: Last 10 lines:
Traceback (most recent call last):
File "", line 1, in
EOFError: EOF when reading a line
grep: /openLANE_flow/designs/eth_top/runs/6thRun/logs/routing/fastroute.log: No such file or directory
sed: can't read /openLANE_flow/designs/eth_top/runs/6thRun/logs/routing/fastroute.log: No such file or directory
sed: can't read /openLANE_flow/designs/eth_top/runs/6thRun/logs/routing/fastroute.log: No such file or directory
sed: can't read /openLANE_flow/designs/eth_top/runs/6thRun/logs/routing/fastroute.log: No such file or directory
sed: can't read /openLANE_flow/designs/eth_top/runs/6thRun/logs/routing/fastroute.log: No such file or directory
sed: can't read /openLANE_flow/designs/eth_top/runs/6thRun/logs/routing/fastroute.log: No such file or directory
sed: can't read /openLANE_flow/designs/eth_top/runs/6thRun/logs/routing/fastroute.log: No such file or directory
[ERROR]: Please check openroad  log file
[ERROR]: Dumping to /openLANE_flow/designs/eth_top/runs/6thRun/error.log


Turn off editing in preview mode on TSVs

Issue:
There are a number of complications to editing the text in preview mode. Users have said that they would prefer not to use it.  Editing in preview mode should be disabled. Markdown mode should be the default view on opening a file.
DoD:
Preview mode should be view only.

@jincypjose per Zach and Klappy, when the preview button is clicked, set Preview: true and Editable: false.

Looks good in translationCore Create - v1.4.4 build 153-d1b4fc1.


[SMALLFIX] Use static imports for standard test utilities

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/2823/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/2823/
Test FAILed.

jenkins, test this please

jenkins, test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/2826/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/2827/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/2829/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/2831/
Test PASSed.

alluxio-bot, merge this please


App crashes after LNURL withdraw

App is newly installed
Open an app with a fresh wallet
Scan LNURL on the Receive tab
Once you hit Withdraw app crashes

However sats are received and after reopening the app funds are there and everything seems ok. This happens every time when you use LNURL, not only after fresh install. I am attaching the log, might help I guess.
phoenix.log

Hello,
There was a similar bug that has been fixed in v1.1.1.
What version of Phoenix are you using? You can see the current installed
version in your Android system settings > applications > Phoenix
On Wed, Feb 19, 2020, 19:29 Mário Havel<EMAIL_ADDRESS>wrote:

App is newly installed
Open an app with a fresh wallet
Scan LNURL on the Receive tab
Once you hit Withdraw app crashes

However sats are received and after reopening the app funds are there and
everything seems ok. This happens every time when you use LNURL, not only
after fresh install. I am attaching the log, might help I guess.
phoenix.log https://github.com/ACINQ/phoenix/files/4226650/phoenix.log
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ACINQ/phoenix/issues/26?email_source=notifications&email_token=ABL7SO5ILPK5BTDGCNRDVZTRDV275A5CNFSM4KX7ABL2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IOXIXGQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABL7SO6HPPIRWCPFXTSVFC3RDV275ANCNFSM4KX7ABLQ
.

It says 1.1.1, newest update from Play Store.

My bad, the fix was not included in 1.1.1, but in the next version which will be released very soon.

Perfect, thanks! Looking forward to the new version.


Re-submission of demo biocat vocabulary

re-submission after fixing the id_ranges.toml file

... now it progressed a little bit further:
it looks, like there is an argument too much ....
Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.11.8/x64/lib/python3.11/site-packages/voc4cat/cli.py", line 450, in run_cli_app
    main_cli(raw_args)
  File "/opt/hostedtoolcache/Python/3.11.8/x64/lib/python3.11/site-packages/voc4cat/cli.py", line 441, in main_cli
    process_common_options(args, raw_args)
  File "/opt/hostedtoolcache/Python/3.11.8/x64/lib/python3.11/site-packages/voc4cat/cli.py", line 47, in process_common_options
    config.load_config(config_file=Path(args.config))
  File "/opt/hostedtoolcache/Python/3.11.8/x64/lib/python3.11/site-packages/voc4cat/config.py", line 142, in load_config
    new_conf["IDRANGES"] = IDrangeConfig(**conf)
                           ^^^^^^^^^^^^^^^^^^^^^
  File "pydantic/main.py", line 341, in pydantic.main.BaseModel.__init__
pydantic.error_wrappers.ValidationError: 1 validation error for IDrangeConfig
vocabs -> biocatalysis_demo -> id_range -> 0 -> ror_id
  __init__() takes exactly 1 positional argument (2 given) (type=type_error)
Error: Process completed with exit code 3.

Sorry. The multi-vocabulary use is still a rough path. The error is related to parsing of the multi-vocabulary config file. I was able to reproduce it locally and will have a look.

@markdoerr - The message is a validation error from pydantic but difficult to understand: The problem is that ROR-Ids have to start with https://ror.org/ (in contrast ORCID where the domain its optional).
In IDrange.toml you have to change the line ror_id = "00r1edq15" to ror_id = "https://ror.org/00r1edq15".

I made the fix in IDrange.toml in main as well and restarted the pipeline. Finally its green!

If you plan to submit the vocabulary in #2, you can close this one. Since I fixed main directly there would be nothing left here after resolving conflicts. IDranges.toml in main now has:
[[vocabs.biocatalysis_demo.id_range]]
first_id = 1
last_id = 300
gh_name = "markdoerr"
orcid =   "0000-0003-3270-6895"
ror_id = "https://ror.org/00r1edq15"

Hi @dalito,
I think we changed the same file simultaneously.
Could you please quickly resolve the issue.
Then I would finally try to submit the demo vocabulary and we will see... thanks

Which issue exactly? I think you need to resolve the conflict in the standard git way and rebase the PR-branch on current head of origin/master. (either here or in the branch used in #2)

@dalito ,
the fastest way with githbub to resolve the conflict is, if you simply click on the "resolve conflicts" button below and accept the change :) - I am not allowed to press the accept button.

I don't have a resolve conflict button. I just see the warning "This branch has conflicts that must be resolved" without any link or button. Did you "allow edits by maintainers" on the PR?

Ah. Now I can merge. Should I?

@dalito , interesting, that the button was only shown to me.
Yes, please merge now. Thanks.


What Parts of the Body Correspond to the Model Output

First of all, great work with this implementation! Thanks for sharing the code!
I wrote code using the original openpose implementation and am trying to use the mobile version to run it on an ios device.
I am getting confused with the model output (shown below):

It seems that the mobile version of openpose outputs 10 segments per frame (with each segment having a start and end coordinate).
However the full version of openpose outputs 25 coordinates for each frame according to the following format.

Is there a similar diagram for mobile openpose which maps the keypoints generated by the model to their location on the human body?
Thanks!

For KeyPoint, please see coco(Common Objects in Context).
Also see this code for KeyPoint settings.


Update README.md

Moved Flounder project URL -- it's now on GitHub

@alexwennerberg Would be great if you could write in the commit title what exactly changed. Atm it's the very generic default from github Update README.md. Thanks in advance!

Hi Kr1sp1n -- did a force push and changed the commit message. Hope that helps!

@alexwennerberg Thank you so much for the changes. 👍


Not connecting to remote server

[19:58:09.144] Log Level: 2
[19:58:09.146]<EMAIL_ADDRESS>[19:58:09.146] linux x64
[19:58:09.148] SSH Resolver called for "ssh-remote+google_colab_ssh", attempt 1
[19:58:09.148] SSH Resolver called for host: google_colab_ssh
[19:58:09.148] Setting up SSH remote "google_colab_ssh"
[19:58:09.151] Acquiring local install lock: /tmp/vscode-remote-ssh-google_colab_ssh-install.lock
[19:58:09.157] Looking for existing server data file at /home/thunderclap/.config/Code/User/globalStorage/ms-vscode-remote.remote-ssh/vscode-ssh-host-google_colab_ssh-ff915844119ce9485abfe8aa9076ec76b5300ddd-0.51.0/data.json
[19:58:09.159] Using commit id "ff915844119ce9485abfe8aa9076ec76b5300ddd" and quality "stable" for server
[19:58:09.161] Install and start server if needed
[19:58:09.164] Checking ssh with "ssh -V"
[19:58:09.186] > OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n  7 Dec 2017
[19:58:09.188] askpass server listening on /run/user/1000/vscode-ssh-askpass-cfa7f897a39b00f982c913953e2f0b4a69d8a1a4.sock
[19:58:09.189] Spawning local server with {"ipcHandlePath":"/run/user/1000/vscode-ssh-askpass-357e3b838994d0c2d8588f1d0deab8c67b433f0a.sock","sshCommand":"ssh","sshArgs":["-v","-T","-D","39511","-o","ConnectTimeout=15","google_colab_ssh"],"dataFilePath":"/home/thunderclap/.config/Code/User/globalStorage/ms-vscode-remote.remote-ssh/vscode-ssh-host-google_colab_ssh-ff915844119ce9485abfe8aa9076ec76b5300ddd-0.51.0/data.json"}
[19:58:09.189] Local server env: {"DISPLAY":"1","ELECTRON_RUN_AS_NODE":"1","SSH_ASKPASS":"/home/thunderclap/.vscode/extensions/ms-vscode-remote.remote-ssh-0.51.0/out/local-server/askpass.sh","VSCODE_SSH_ASKPASS_NODE":"/usr/share/code/code","VSCODE_SSH_ASKPASS_MAIN":"/home/thunderclap/.vscode/extensions/ms-vscode-remote.remote-ssh-0.51.0/out/askpass-main.js","VSCODE_SSH_ASKPASS_HANDLE":"/run/user/1000/vscode-ssh-askpass-cfa7f897a39b00f982c913953e2f0b4a69d8a1a4.sock"}
[19:58:09.195] Spawned 6947
[19:58:09.263] > local-server> Spawned ssh: 6955
[19:58:09.265] stderr> OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n  7 Dec 2017
[19:58:26.197] Terminating local server
[19:58:26.203] Resolver error: Connecting with SSH timed out
[19:58:26.216] ------
[19:58:26.219] Local server exit: 15

Can you please provide us with more information and the parameters you passed to the function

Could you give more instructions for vscode? After running the cell in colab, I click on the vscode link. In the platform of host selection, I chose Linux, but it crashed, and I tried the macOS and Windows too but they also crashed.  I've attached the log below.
The error I got was "Could not establish connection to '0.tcp.ngrok.io'. The process tried to write to a nonexistent pipe."
My parameters were:
`# Install colab_ssh on google colab
launch_ssh(ngrokToken,password,'ap')
Optional: if you want to clone a github repository
init_git("https://github.com//<REPO_NAME>.git",
personal_token="<my_GITHUB_PERSONAL_TOKEN>",
branch="master",
email="<my_EMAIL>",
username="<my_USERNAME>")`
Other questions
I'm curious about what are some of your use case workflows? How do you store datasets, models, results? Some of mine are too big to store on Github? Do you use it with Google Drive and are you able to access Google Drive on vscode? How do you work on let's say a week-long project?
`
$ ./ngrok authtoken 1cgHgtV6L4D8k04lt5p3mc26oqP_SgtYhjxa59MnixqHR3E7
[01:58:00.479] Log Level: 2
[01:58:00.485]<EMAIL_ADDRESS>[01:58:00.485] win32 x64
[01:58:00.487] SSH Resolver called for "ssh-remote+root@0.tcp.ngrok.io:17498", attempt 1
[01:58:00.487] SSH Resolver called for host<EMAIL_ADDRESS>[01:58:00.487] Setting up SSH remote "0.tcp.ngrok.io"
[01:58:00.515] Using commit id "5763d909d5f12fe19f215cbfdd29a91c0fa9208a" and quality "stable" for server
[01:58:00.517] Install and start server if needed
[01:58:04.225] Checking ssh with "ssh -V"
[01:58:04.269] > OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5
[01:58:04.272] Running script with connection command: ssh -T -D 56891 -p 17498<EMAIL_ADDRESS>bash
[01:58:04.277] Terminal shell path: C:\WINDOWS\System32\cmd.exe
[01:58:04.427] >

]0;C:\WINDOWS\System32\cmd.exe
[01:58:04.427] Got some output, clearing connection timeout
[01:58:04.432] >
[01:58:25.465] > ssh: connect to host 0.tcp.ngrok.io port 17498: Connection timed out

[01:58:25.474] > The process tried to write to a nonexistent pipe.

[01:58:25.747] "install" terminal command done
[01:58:25.748] Install terminal quit with output: The process tried to write to a nonexistent pipe.
[01:58:25.748] Received install output: The process tried to write to a nonexistent pipe.
[01:58:25.749] Resolver error: The process tried to write to a nonexistent pipe
[01:58:25.755] ------
`

Could you give more instructions for vscode? After running the cell in colab, I click on the vscode link. In the platform of host selection, I chose Linux, but it crashed, and I tried the macOS and Windows too but they also crashed. I've attached the log below.
The error I got was "Could not establish connection to '0.tcp.ngrok.io'. The process tried to write to a nonexistent pipe."
My parameters were:
launch_ssh(ngrokToken,password,'ap')
init_git("https://github.com/<OWNER>/<REPO_NAME>.git",
         personal_token="<my_GITHUB_PERSONAL_TOKEN>",
         branch="master",
         email="<my_EMAIL>",
         username="<my_USERNAME>")

Can you please provide some information about your local machine's OS and the version of VSCode you are using ?

Local Machine is running Windows 10, running vscode 1.45.1
Steps:

Copy the code cell, enter details, and set up ngrok & init_git. Follow instructions in the README for this repo.
Click on the vscode link generated by the cell.
Enter the password requested.
Successfully connected (most of the time)
Install the extension on colab -> needs reload -> reloads
Error, can't establish connection.

I have the same OS and exactly the same VSCode version.

Successfully connected (most of the time)
Install the extension on colab -> needs reload -> reloads
Error, can't establish connection.

Can you please clarify what you meant by "the" extension in step 5 ? and what do you mean by "... on colab" ?
Meanwhile, I tried several scenarios to reproduce the issue:

Scenario 1: Click on the generated VSCode link without having the "Remote - SSH" VSCode extension installed
Scenario 2: Successfully connect via the link and then install several extensions and click the "Reload Required" button each time.

Unfortunately, all the scenarios work as expected. Reloading the window doesn't reproduce the issue.
This might be related to the VSCode "Remote - SSH" extension configuration, maybe there is a setting that produces the issue. Would you please provide us with your VSCode configuration file (settings.json).
Thank you

Other questions
I'm curious about what are some of your use case workflows? How do you store datasets, models, results? Some of mine are too big to store on Github? Do you use it with Google Drive and are you able to access Google Drive on vscode? How do you work on let's say a week-long project?

I would be glad to answer your questions if you can post these questions on stackoverflow using the following tag colab-ssh since they are not related to software bugs or issues.

I have the same OS and exactly the same VSCode version.

Successfully connected (most of the time)
Install the extension on colab -> needs reload -> reloads
Error, can't establish connection.

Can you please clarify what you meant by "the" extension in step 5 ? and what do you mean by "... on colab" ?
Meanwhile, I tried several scenarios to reproduce the issue:

Scenario 1: Click on the generated VSCode link without having the "Remote - SSH" VSCode extension installed
Scenario 2: Successfully connect via the link and then install several extensions and click the "Reload Required" button each time.

Unfortunately, all the scenarios work as expected. Reloading the window doesn't reproduce the issue.
This might be related to the VSCode "Remote - SSH" extension configuration, maybe there is a setting that produces the issue. Would you please provide us with your VSCode configuration file (settings.json).
Thank you

It's the second scenario with which I'm facing issues. My .ssh/config file is empty and my settings.json file is below.
# settings.json
 "remote.SSH.remotePlatform": {
        "0.tcp.ngrok.io": "linux"
    },
    "remote.SSH.defaultForwardedPorts": [

    ]
}

Your settings.json looks normal, there is nothing out of the ordinary. I did try and I couldn't reproduce the issue with your settings.json. One last thing to test is the ssh command, this will let us know if the problem is with VSCode or some sort of SSH problem.
If you don't mind, would you please run the following command in your command line once VSCode displays the message Error, can't establish connection (you can keep the VSCode open):
ssh -p <PORT> root@<HOST>
# For example
ssh -p 123456<EMAIL_ADDRESS>
As you may know, you can find the port and host in the cell output.


Issue 360 add terms of service

Issue #360

[x] On the cold message screen add a checkbox to the form stating "I understand that if I hire #{developer's name} then I will pay railsdevs 10% of their first year salary."
[x] Invalidate the form if the checkbox is not checked
[ ] BONUS: Disable the form if JavaScript is enabled and the checkbox is not checked
[x] Add conditional for only businnesses with $299/month full-time plan

Screenshots

Form Preview

Form error message when checkbox is not selected.

Pull request checklist

[x] Your code contains tests relevant for code you modified
[x] You have linted and tested the project with bin/check
[ ] You have added significant changes and product updates to the changelog

Hey @kaushikhande, do you still have appetite to get this over the finish line? If not let me know and I can take over!

Hey again! I had some free time this weekend and really wanted to get this out. Hope you don't mind that I took it the last 10%.
Thanks for your contribution!


[firebase_dynamic_links] dynamically generated link is not routing to custom web page

I’m trying to share a link (with deep linking) through my mobile app using library share: ^0.6.3. If the app is installed the link should open the app and if app is not installed it should open the custom webpage on the browser. I'm using firebase library firebase_dynamic_links: ^0.5.0+8 for deep linking.
The actual URL which requires for the website is like https://sub-domain.myDomain.com/post/share/5e09d71336a7ce1e40b4b74f
I have added our domain https://sub-domain.myDomain.com in the firebase dynamic link console on firebase. I'm using the following code to create firebase dynamic shortened URLs which looks like https://sub-domain.myDomain.com/j3j4hiu4k.
When the link is clicked the app does open and i am able to achieve “Deep Liking”. But if the app is not installed the custom web page does not load.
final DynamicLinkParameters parameters = DynamicLinkParameters(
   uriPrefix: 'https://sub-domain.myDomain.com/',
   link: Uri.parse('https://sub-domain.myDomain.com/post/share/5e09d71336a7ce1e40b4b74f'),
   androidParameters: AndroidParameters(
       packageName: 'com.package.projectDemo',
       minimumVersion: 101,
       ),
   iosParameters: IosParameters(
       bundleId: 'com.package.projectDemo',
       minimumVersion: '1.0.1',
       appStoreId: '',
       ),

 );
 final dynamicUrl = await parameters.buildShortLink();

Share.share(dynamicUrl.tostring());

**Flutter doctor result**
[✓] Flutter (Channel unknown, v1.9.1+hotfix.6, on Mac OS X 10.13.6 17G10017, locale en-IN)
    • Flutter version 1.9.1+hotfix.6 at /Users/SagarAdmin/Desktop/flutter
    • Framework revision 68587a0916 (4 months ago), 2019-09-13 19:46:58 -0700
    • Engine revision b863200c37
    • Dart version 2.5.0

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.0-rc1)
    • Android SDK at /Users/SagarAdmin/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.0-rc1
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 9.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 9.4, Build version 9F1027a
    • CocoaPods version 1.8.3

[✓] Android Studio (version 3.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 33.4.1
    • Dart plugin version 182.5215
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)

[✓] VS Code (version 1.41.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.7.1

[✓] Connected device (1 available)
    • Redmi Note 3 • 57713893 • android-arm64 • Android 6.0.1 (API 23)

Any news on this?


chore: :wrench: update user-agent

update httplib2 version in user-agent after dependabot upgrade

Oh yea thanks

I tried to use the real user agent from the lib but I still got 404 errors on some websites. From what I could figure out, some websites require a knows user agent, else they return a 404 error. I checked the logs and the 404 errors are back.
Perhaps PR #1428 and#1427 should be reverted.

Can you confirm we're talking about https://www.petfinder.com/developers/v2/docs/ and https://www.amiiboapi.com/?
We should not fake our User Agent to validate links. I think we should remove these links if they're not able to answer correctly when given a correct User Agent.

https://www.petfinder.com/developers/v2/docs/ and https://www.amiiboapi.com/ are the links I was refering to.
From my tests, I found out that the two websites return a 404 page when accessed with no user agent or a dummy one. When I used Chrome's user agent in the script, a valid page with the description of the API description is returned.
I chose a user agent from an existing browser in the script since the use case I had in mind was not accessing the API directly but the documentation page. In this use case, the developer which is interested in this API will access the documentation page using a browser first. If the website can be accessed with a browser then from my point of view the link is valid.
It's up to you what you want to do with those two links.

I sent an email to Petfinder support and opened an issue on AmiiboAPI. Will wait for them to fix the issue.

Seems to be a host issue. Sorry for the inconvenient. Is it possible to get delisted? I will request again once I decided to change host.

Sure thing. Thanks for looking at it. Let us know! 😄


The bots use an old Firefox version for testing

Steps to reproduce the problem:
Look at recent bot logs, for both Linux and Windows. Some recent examples (taken from PR #16899):

http://<IP_ADDRESS>:8877/5de7eb750fa6ace/output.txt
http://<IP_ADDRESS>:8877/4779353b9acdc6f/output.txt

What is the expected behavior? (add screenshot)
That the latest Firefox version is being used for testing, such that we're able to catch browser regressions.
What went wrong? (add screenshot)
The bots still use Firefox 115 during the reference tests, since the following user-agents are logged:

User agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0
User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0

Looking at the logs it does seem that Firefox 119 was correctly downloaded, however it's not actually being used.
Please note: I don't know exactly when this started, but I wonder if the trimCache-functionality (see PR #16519) isn't working as intended since older Firefox versions are apparently not being removed!?
As far I can tell, old Firefox versions not being removed seem to reproduce locally as well. @timvandermeij Would you have time to take a look?
In the short term, would it be possible to manually clear old Firefox versions from the Puppeteer-cache on the bots? @calixteman Do you have time to do that?

I just removed the directories containing 115, 116, 117 and 118 on both bots.

Interesting find; it might imply an upstream bug in Puppeteer. I'll have a look this weekend and try to find out what's happening.

I have reproduced this problem locally and found that it's indeed an upstream bug in Puppeteer. Old Chrome revisions do get cleaned up correctly, but old Firefox releases don't, even though there is code to do so in the trimCache implementation upstream. However, the test that was added on the Puppeteer side only tests Chrome cleanup which is likely how the Firefox bug went unnoticed.
I'll try to debug the problem in Puppeteer and report a bug upstream.


Casting To ContainerInternal Prevents Proper Unit Testing Patterns

https://github.com/Azure/azure-cosmos-dotnet-v3/blob/cb7f923a136a1d44ee169f019cf66ad6a581e6ec/Microsoft.Azure.Cosmos/src/ChangeFeedProcessor/ChangeFeedProcessorBuilder.cs#L178C9-L202C10
When attempting to Mock the behavior of ChangeFeedProcessorBuilder.WithLeaseContainer(leaseContainer) an exception occurs.
System.InvalidCastException: 'Unable to cast object of type 'Castle.Proxies.ContainerProxy' to type 'Microsoft.Azure.Cosmos.ContainerInternal'.'
The WithLeaseContainer() method should be able to handle mocked Container objects so that consumers can write proper unit tests.

The Change Feed Processor Builder is not unit-testeable. What exactly is the scenario?

https://github.com/Azure/azure-cosmos-dotnet-v3/issues/4243#issuecomment-1883192893
https://github.com/Azure/azure-cosmos-dotnet-v3/issues/3486


eth_blockNumber

Inviting @tkstanczak, @MicahZoltu for review.

Thank you @MicahZoltu!

I left the tabulated view of specifications because I want them all to be consistent and in some cases like eth_call there are more specifications than bullet points can sensibly represent.

Is this PR still relevant, @alita-moore ?

Yeah @timbeiko


chromedriver 78.0.3904.70 => 80.0.3987.16

Motivation for this change
To have chromedriver compatible with Google Chrome 80
Things done
This is the same change as in this pull request https://github.com/NixOS/nixpkgs/commit/07ba5ae8f7268d002bf1552f499c689f3ca4e7c3

Thank you for your interest. Usually, the changes happen in the master branch.
nixos-unstable is a protected branch to for the unstable channel, it would automatically advance once the hydra builds succeeds.
You can read more about channels here https://nixos.wiki/wiki/Nix_channels; unfortunately is a bit outdated given some recent changes https://github.com/NixOS/nixpkgs/issues/71176


Multilanguage support for markers used in data

Currently we can only use English with section headers, settings, and other such markers in the data. For example:
*** Settings ***
Documentation     Some doc here.

Supporting other languages would be great. For example, the above could look like this in Finnish:
*** Asetukset ***
Dokumentaatio    Jotain dokua täällä.

Getting this done requires:

Deciding how to enable support for different languages. Probably with a command line option like --language FI.
Deciding how to handle multiple languages in one execution. Could be --language FI --language EN to allow customizing how a certain language is used e.g. like --language FI:some:config.
Deciding what to translate. Section headers and settings for sure, but what about control structures like IF/ELSE? Perhaps we should allow translating everything and let translators to select do they want to use common IF/ELSE or some local variant. Could also be customizable when enabling support for a certain language.
Getting translations for built-in support for common languages. These can be added in future releases.
Deciding how to use languages that don't have built-in support. Perhaps --language mylang.txt.

I hope the wider community can help with translations when we get that far. Comments about the design decisions above are appreciated as well.
I consider making Robot Framework more native in non-English speaking languages pretty important and thus assign this to RF 5.0 scope with critical priority. The old issue about non-English Given/When/Then prefixes (#519) is highly related and already in RF 5.0 scope.
There are many other related enhancements like translating log and report, translating error message, translating keywords used in generic libraries, and so on. They all require their own issues and probably need to wait for future RF versions.

Leaving myself here so I will remember to add option for robotidy to autotranslate tokens. And it would be interesting to add support for polish. Although I don't have idea how to translate some of the keywords such as [Teardown] (probably not [Zburzyć] :D). Maybe to avoid problems with not accurate translations it would be good idea to let people vote on certain translations? Or use https://crowdin.com .

Yeah, coming up with good translations for some of these terms is going to be hard. No idea what Teardown could be in Finnish either. A major problem related to this is that changing terms would be backwards incompatible. Perhaps we should support English always so that hard-to-translate terms could be initially skipped.

Great Idea.

We decided to move this one and highly related non-English Given/When/Then support (#519) to RF 5.1. That wasn't done because we don't consider these issues important, on the contrary, but simply because RF 5.0 already contains lot of great new features and we want to get it out as soon as possible. These translation related issues will be the highest priority issues in RF 5.1 and the plan is to start its development right after RF 5.0 has been released.

We need to do some technical choices before proceeding with the implementation.
The goals here are:

offer simple way for users to provide translations
use a file format which can be parsed easily with the Python standard library
introduce no performance penalty

Since this is mostly a lookup problem (does a given string, say *** testitapaukset ***, represent a valid token), some kind of configuration file is most likely appropriate. A full-blown translation framework like gettext might be too complicated.
In addition, it needs to be decided whether we support multiple forms for some tokens. For example, currently the table headers allow both singular and plural English form (test case and test cases). For the sake of simplicity and clarity, it might be better to allow just one form in the translations.
Based on all the above, some options for the configuration file format are:

INI files
JSON
YAML
TOML

Of these, INI files and JSON are the ones having parsers in the Python standard library.
JSON is quite unwieldy to edit by hand and it does not support comments, and additionally no benefit is gained by it's support for a wider range of data types than INI files.

I would really like to also results be considered. How does log.html look like
and could we allow to some extent results automatic translations.

@yanne one thing I would also think are the existing standards and work beyond Python standard libs.
JSON is pretty much used in projects like i18next and all over the content of internet (like in headless cms).
It might actually result in best tooling for content creation for the translations.

Translating log and report is important but it would most likely be better to update their underlying tech first. We are planning to do such tech update with Libdoc already in RF 5.1 (#4304) and if that goes well then log/report could be next.

Regarding  technical choices:
What about the python gettext  API, it comes with python and is a well established standard, editing and handling PO files is easy and there are several tools wich helps you to write your translations.

Yeah, coming up with good translations for some of these terms is going to be hard. No idea what Teardown could be in Finnish either. A major problem related to this is that changing terms would be backwards incompatible. Perhaps we should support English always so that hard-to-translate terms could be initially skipped.

This supporting English forever would solve (or work-around) the problem of deciding what to translate and what to leave in English. I rather wish RF not to enforce using translations even if they are available---then everyone can decide whether e.g. whether they will write RETURN in English or in their language. (This is Robocop what I probably wish to (optionally) check whether a translation was used wherever possible.)

gettext is an option later but an overkill now. We just need to match strings during parsing.
The plan is to support English as an alternative automatically. In the future we may make that configurable if there are needs. Notice also that at least in the beginning we don't plan to support translating control structures like RETURN or IF. Support for that can be added later.

Markers to translate, that are covered by this issue, are just headers and settings. With headers we support both singular and plural formats in English and we can support them also with other languages. For test related headers and settings we have task related aliases.
Headers:

Settings, Setting
Variables, Variable
Test Cases, Test Case
Tasks, Task
Keywords, Keyword

Settings in the Settings section:

Documentation
Metadata
Suite Setup
Suite Teardown
Test Setup
Test Teardown
Test Template
Test Timeout
Task Setup
Task Teardown
Task Template
Task Timeout
Force Tags
Default Tags
Library
Resource
Variable

Settings for tests/tasks:

Documentation
Tags
Setup
Teardown
Template
Timeout

Settings for keywords:

Documentation
Arguments
Teardown
Timeout
Tags
Return (this will be deprecated in somewhat near future and can be omitted)

We obviously need help from the community with translations. We have decided to use the #localication channel on our Slack as the main collaboration place and separate language specific channels can be created for each language. If you are interested to help, join the channel! If you aren't yet on our Slack, you can get an invite here.

If anyone wants to join in on the translation of RF please submit your translation here https://robotframework.crowdin.com/robot-framework

I added initial translations for Finnish for testing and demonstration purposes in bfec5a53346b2cfb1a537aeb3814bab748272910. Everything that was needed is the new Fi class in the languages module. I would prefer additional languages to be added via pull requests by their respective authors to have contact info for them automatically stored. It's fine to leave some of the terms untranslated, the English terms will nevertheless work. You many also decide not to translate [Return] because it will be deprecated and removed in the somewhat near future anyway.

Notice that the class in the languages module will be the name of the language to use from the command line. Matching name is case-insensitive so, for example, the aforementioned Fi class can be used like --language fi.
Language variants such as Brazilian Portuguese could have a class name like PtBr and be used like --language ptbr. If the usage would be more convenient like pt-br or pt_br, we can ignore - and/or _ when matching. Alternatively we could make it possible for each class to provide a custom name to be used with them. Do you @HelioGuilherme66 have a preference?

Better use the hyphen then. The following should be accepted:  pt (this is the preferable, nice to have a lookup for regional LANG code page, and switch to it, otherwise, default would be pt-pt),  pt-pt and  pt-br.
There may be more regional variants, like for example, Angola.
(I haven't looked at code, but maybe a specific Robot Framework language environment variable could exist):
No --language option ==> Lookup ROBOT_LANG ==> English (en´) If None else ROBOT_LANG  With --language pt==> Lookup ROBOT_LANG ==>pt-ptIf None else ROBOT_LANG (user would need--language ento bypass ROBOT_LANG)  With--language pt-pt==> no lookup for ROBOT_LANG ==>pt-pt With--language pt-br==> no lookup for ROBOT_LANG ==>pt-br With--language fi==> no lookup for ROBOT_LANG ==>fi`  (applicable for all languages with no regional variants)

I don't think we need an environment variable to control the language. We already support ROBOT_OPTS and giving it a value like --language pt has the same effect as the proposed ROBOT_LANG with value pt. I'd also rather think about adding support for config files than add more environment variables. I'm not entirely against the idea, though, so you can submit a separate issue to discuss it further.

I don't want to make handling language codes too complicated at least in RF 5.1. For example, I don't want to do any extra lookups if someone uses pt and not pt-pt. We just need to decide which one to use or make it so that both mean the same thing.
The hyphen in pt-br is easiest to handle so that we simply ignore it when matching the given language code to the available ones. Then the class name can be just PtBr and matching it works. Alternatively we could require the class name to be Pt_Br in this case or require the class to have an attribute telling the language code to use. I don't think these have any concrete benefits over simply ignoring the hyphen in matching. That obviously means that ptbr works in addition to pt-br, but I don't think that really matters.

Big thanks for @leeuwe for setting up Crowdin to have a place where the community can work together with translations. Thanks also to everyone who has already participated in translation efforts.
If you want to test translations created at Crowdin, you need to download the language file (seems to be named Core.yml) and convert it to Python that Robot Framework understands. I have created a script that can do conversion automatically. Just download the script and run it like this:
python crowdin.py Core.yml lang.py

The generated Python code can be used directly with Robot Framework like robot --language lang.py tests.robot. The generated class can also be added to Robot's languages module via a pull request to get it included as a built-in language.

The support for localized markers ought to be done now. We still need to add actual translations and document all this, but that's covered by #4390.


webpack 2 is compiling multiple times per file change

add a handler to compiler.done
run pie info --log-file out.log --log-level silly

your handler will be fired up to ~10 times.
This shouldnt be happening. We have a debounce in there to make the cli a bit quieter but it's a bit messy. Find out what's causing it.

Looks like this is causing it:
https://github.com/PieLabs/pie-cli/blob/develop/src/apps/item/index.ts#L61-L66

Looks like it's a bug in compiler.watch. can repro with this:
const webpack = require('webpack');
const { readJsonSync, writeFileSync, statSync } = require('fs-extra');
const { join } = require('path');

function run() {

  const root = process.cwd();

  const entryPath = join(root, 'entry.js');
  writeFileSync(entryPath, 'console.log("hi")', 'utf8');

  const config = {
    context: root,
    entry: entryPath,
    output: {
      path: root,
      filename: 'bundle.js'
    }
  };

  const compiler = webpack(config);

  compiler.plugin('compile', () => {
    console.log('compiling...');
  });

  compiler.plugin('done', () => {
    console.log('done');
  });

  compiler.watch({
    aggregateTimeout: 1000
  }, (err, stats) => {
    console.log('run complete', err);
  });
}

run();

it's being caused by the following:
https://github.com/webpack/watchpack/blob/master/lib/DirectoryWatcher.js#L13
and this:
https://github.com/webpack/watchpack/blob/master/lib/DirectoryWatcher.js#L206-L208
It basically means that if the file has no modifications, changes will be emitted for 10 seconds until the timestamp is >= the start time.

There is an open issue on it: https://github.com/webpack/watchpack/issues/25


feat(cli): Dry run

This change adds a new flag --dry-run that when
given, prevents otherwise destructive file
overwrite operations and instead prints a rich
diff. The diff contains names of files which would be modified, and a git-like diff of what
modifications would be made.
The diff is human-readable, and not designed to be easily machine-readable.
The change leverages the similar crate, on which we transitively depended on already anyway.
Closes #152.

Codecov Report
Attention: Patch coverage is 70.00000% with 6 lines in your changes missing coverage. Please review.

Project coverage is 86.52%. Comparing base (3f64519) to head (82e5429).

Files with missing lines
Patch %
Lines

src/main.rs
70.00%
6 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #156      +/-   ##
==========================================
- Coverage   86.67%   86.52%   -0.16%
==========================================
  Files          32       32
  Lines        1876     1892      +16
==========================================
+ Hits         1626     1637      +11
- Misses        250      255       +5

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Looks like:

There's already a search mode, and as opposed to normal diffing tools, we know the exact actions we took. Thus it makes sense to leverage that search mode, and not do (much) extra work to see what changed. Results now look like:

which looks different from "normal" git-style diffs, as lines are never grouped. There's also no + and - prefix. I'd think this diff is for human consumption, where the colors and word-style diff make sense.


[Fix][Relay] Fix axis transformation in squeeze shape function

This PR fix the issue https://github.com/apache/tvm/issues/14134.
Currently in squeeze shape function do not transform axis, which means negative axis such as -1 will lead to wrong result.
This PR fix this issue and add simple testcases.

Thanks for the bugfix! Can you add a commit message as per TVM's commit message guidelines and fix the typo in the PR title?

@ekalda Thanks for the reminder! I have updated the title and commit message.


docs(v2): Removed unnecessary closing parenthesis

Motivation
There was an extra closing parenthesis.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Preview.
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

thanks 👍


Consider supporting pending in tests

Does this work with JUnit?
I like the idea, but I'm not sure whether pending is needed when we already have ignored, what comes close. I would say that pending makes only sense, if the JUnit runner is able to list pending tests as such. That is the way ScalaTests handles pending tests.

Really I just brainstorm when I'm bored at work. Some ideas might make no sense.

Doesn't look like it would be possible using a junit runner.


Fix matching for new version scheme

ping @vdemeester @icecrime @vieux PTAL

This is now handled by poule, so we don't really need this


reorder menu items in alphabetical order - i1735

Signed-off-by: amanda-ariyaratne<EMAIL_ADDRESS>Description
Nginx Service Mesh was put between Network Service Mesh and Octarine
This PR fixes #1735
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Whoo-hoo, @amanda-ariyaratne! 🎈

@amanda-ariyaratne there's much more where this comes from. I welcome you to join the Layer5 community (http://slack.layer5.io) and dig into any of the projects - https://docs.google.com/document/d/17OPtDE_rdnPQxmk2Kauhm3GwXF1R5dZ3Cj8qZLKdo5E/edit?usp=sharing

@amanda-ariyaratne there's much more where this comes from. I welcome you to join the Layer5 community (http://slack.layer5.io) and dig into any of the projects - https://docs.google.com/document/d/17OPtDE_rdnPQxmk2Kauhm3GwXF1R5dZ3Cj8qZLKdo5E/edit?usp=sharing

Thank you! Hoping to contribute more to this project.


Fix ingress template to work with k8s >=1.19-0

In the newest k8s releases " apiVersion: networking.k8s.io/v1beta1" got obsoleted and trying to install the chart there errors out with:
Error: resource mapping not found for name: "ckan" namespace: "" from "": no matches for kind "Ingress" in version "networking.k8s.io/v1beta1"
This patch updates the ingress template to work with k8s releases >=1.19-0

@Filip3mac FYI


Introduce a beta channel tag and logic for driver binary versions

Introduce a beta configuration tag to separate the event of getting latest stable vs latest beta.

Noticing some failures after the latest updated to driver 81 because it is in beta channel
https://github.com/webdriverextensions/webdriverextensions-maven-plugin-repository/commit/99d63eae2858220200e92cdf5953dbbea76c94c8
We could test against this locally but our CI build server isn't going to use beta versions of Chrome.  So for now we will have to specify the 80.x version.

I can revert the changes for the other repo. I misread the main site.

@jsmithe I reverted the change.  You should be in the clear.  Sorry for the hang up.

In most cases we are speaking of Chromedriver and beta version is likely to become the stable version of tomorrow.
I would keep it simple:

separate the beta drivers into a their own repository file
add an option to include beta drivers
if this option is enabled, the beta-repository file will be loaded as well and merged into the list of the stable drivers
if the beta-repository includes a newer version of a driver than the regular (stable) then the newer (beta) version will be used, otherwise the (newer) stable version


Add disabled state to toggler widget

Requirement
In our pigg app, we encountered a scenario where it was necessary to disable the toggler based on user interactions. This functionality was crucial to ensure better control and flexibility within the app's user interface.

Implementation
To address this need, I implemented the disable feature for the Toggler widget in Iced. When disabled, the toggler prevents any interaction, thereby enhancing the overall user experience by providing more control over the UI components.
I have also incorporated this feature into the Tour example of Iced to showcase its functionality and usage.

Your feedback and suggestions for further improvements are highly appreciated!

Thanks @hecrj
Would love to contribute more to this repo