OG Image needs a better relative URL

using 1.1.1 with the new OG image tag.
And when I run it through a validator, i get :
https://www.pixeldiamondgames.com/./images/header.png

Yes technically the source image is relative to the generated index.html.... however, the folder itself is relative to the base domain at /presskit/index.html (and thus the image should be /presskit/images/header.png)
So it seems when the <meta ...> OG:image tag is being set up, the website crawler sees a relative URL and assumes top of domain.
Visual of failing to find the image

even MORE complicated is the fact that -- the OG:image tag doesn't also account for the product itself
so the FULL url for the product's OG image is:
domain.com/presskit/product/images/header.png
but instead is generated as:
domain.com/./images/header.png
and even replacing the . in the product case with /presskit wouldn't send the right image either, it would send the company image and not the desired product image

cc @zer0tonin

When using chrome inspector to manually change the URL, it does exist in the right spot too:

fwiw, i do have a yarn command that runs the build command, so I can know at time of generation what the relative URL will be:
yarn run milou build ./company --ignore-thumbnails --clean-build-folder --output build
# copy build folder to website's relative directory

I think the only way to really mathc the spec is to provide an absolute URL.
It can be done using version 1.2.0 and by setting baseURL in the company yaml.
Like here


Fixes the problem that the customer cannot delete his account when the csrf token is generated via Ajax

Why is this change necessary?
If the csrf token is generated via ajax, the customer cannot delete his account in his profile view.

What does this change do, exactly?
the attribute data-form-csrf-handler is added to the form for deleting the account.

Describe each step to reproduce the issue or behaviour.
In the profile view of an existing customer account, try to delete the customer account if csrf mode is set to ajax.

Please link to the relevant issues (if any).

Checklist

[]  I have written tests and verified that they fail without my change
[]  I have created a changelog file with all necessary information about my changes
[]  I have written or adjusted the documentation according to my changes
[]   This change has comments for package types, values, functions, and non-obvious lines of code
[]  I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-22123
Please use this issue to track the state of your pull request.


wrong docker image label of kubernetes/heapster

wrong docker image label of kubernetes/heapster

Can one of the admins verify this patch?

Thanks for catching this, @njuicsgz
We should just push a new image tag v0.14.2 to be consistent with the other tags.
@vishh Can you do a push today?

I updated the hub to have an image with v0.14.2 tag. Thanks for this PR!

good to me.


SearchServices apiKey value does not fall within the expected range

Trying to setup the jfk files project, however, when I try to execute step 12 (run the JFKInitializer), this error was thrown.

This is an issue with Mac and the Mono runtime with the Azure Service Client its passing a blank sting to the ProductHeaderValue (https://github.com/Azure/azure-sdk-for-net/issues/4651 and https://github.com/mono/mono/issues/10227 )and an update is planned in the near future, the guidance i was given is to build on a Windows machine.

@Sighillrob,
Are there currently any workarounds for this?

Unfortunately, there isn't thus far I have continued updating the beta release and there hasn't been a mononoframework to resolve this.  I decided to build out a VirtualBox windows 10 box and install 2017 VS on that it's working just a bit slow for me.

It seems to be fixed on the preview release v<IP_ADDRESS>.
Br

Oh wait. I apologise. My issue is related to this, but not the same. Please disregard my comment. I have not confirmed this issue is solved

IM currently installing <IP_ADDRESS>9 and iterating up on the stable releases right now.  then jumping back to the beta releases.

<IP_ADDRESS> is my next test on the Alpha channel

@dsgouda this is related to the issue you closed on https://github.com/Azure/azure-sdk-for-net/issues/4651

Closing this as the issue is tracked elsewhere: https://github.com/Azure/azure-sdk-for-net/issues/4651


[5.3] Fix lazy eager loading issue in LengthAwarePaginator collection.

Fixes error described in #14468 for 5.3

Already done in #14476

Same fix as here https://github.com/laravel/framework/pull/14476 for 5.2.

Thanks for the PR, but since we already have the same PR already open on 5.2, I'll close this. :)


Add an exemple of how to embed the jpeg stream in a custom html page

First of all, congratulations for your work in this project. I have a backend server and a frontend web app (angular 2+). Also, I'm running a stream on port 8888 as default. I'm not figuring out the proper way to show only the stream in my frontend webpage. Maybe using a  tag or an  tag.
An example of this situation would be great.

Hi, sorry for the very late response. I did not see your question before.
For an example how to embed the video in an HTML page, have a look at the example file included:
https://github.com/Bronkoknorb/PyImageStream/blob/master/static/index.html
Or, if you are using Angular, you can also check out my other project which embeds this stream (actually two streams) into an angular app:
https://github.com/Bronkoknorb/hm-aquarium/tree/master/aquarium-web/src/app/camera


Add Funtoo (Gentoo fork) support or at least support choosing distro in an arguement

Hello, it seems that this program doesn't detect Funtoo as Gentoo, can you do a similar thing to https://github.com/MrPotatoBobx/FetchCord/issues/2#issuecomment-669504792
Below is my terminal output
sako@stalin-sodium ~ $ fetchcord  ['Mono', '11'] Unknown Host, contact us on github to resolve this.(Keyerror) Unsupported Distro, contact me on the GitHub page to resolve this.(keyerror) Connecting RPC connection successful. ^CClosing connection. sako@stalin-sodium ~ $

Can you give --debug log please.

sako@stalin-sodium ~ $ fetchcord --debug laptop: True ['Mono', '11'] out deid: KDE termfontline: Mono 11 amdgpurenderlist: [] intelgpuline: [] sysosline: ['OS: Funtoo Linux 1.4 x86_64 '] gpuinfo: GPU: NVIDIA GeForce GTX 1080  gpuvendor: NVIDIA nvidiagpuline: ['GPU: NVIDIA GeForce GTX 1080 '] cpuvendor: Intel cpumodel: Intel i5 cpuline item 0: CPU: Intel i5-8600 (6) @ 4.300GHz  wmid: KWin termid: konsole termline item 0: Terminal: konsole  packagesline item 0: Packages: 1551 (emerge), 18 (flatpak)  sysosid: Funtoo sysosline item 0: OS: Funtoo Linux 1.4 x86_64  wmline item 0: WM: KWin  Unknown Host, contact us on github to resolve this.(Keyerror) Unsupported Distro, contact me on the GitHub page to resolve this.(keyerror) testing deid: KDE wmid: KWin termid: konsole shellid: bash hostid:  cpumodel: Intel i5 gpuvendor: NVIDIA Connecting RPC connection successful. run-rpc<PHONE_NUMBER>.0<PHONE_NUMBER>79197462 nvidia Packages: 1551 (emerge), 18 (flatpak)  cycle 0 appid:<PHONE_NUMBER>79197462 ^CClosing connection. sako@stalin-sodium ~ $

laptop: True
this is on a desktop, not a laptop

added, also having that say true for laptop is a bug, please make another issue so we can figure that out because that is unintended to occur.


Ability to specify rolling interval for the buffer files in DurableElasticsearchSink

A few questions before you begin:

Is this an issue related to the Serilog core project or one of the sinks or
community projects.
This issue list is intended for Serilog Elasticsearch Sink issues. If this issue relates to another sink or to the code project,
please log on the related repository.  Please use Gitter chat and Stack Overflow  for discussions and questions.

Does this issue relate to a new feature or an existing bug?

[ ] Bug
[x] New Feature

What version of Serilog.Sinks.Elasticsearch is affected?  Please list the related NuGet package.
v. 8.4.1.
What is the target framework and operating system? See target frameworks & net standard matrix.

[ ] netCore 2.0
[ ] netCore 1.0
[ ] 4.7
[ ] 4.6.x
[ ] 4.5.x
[ ] 4.8
[x] netstandard2.0

Please describe the current behavior?
Now we cannot specify rolling interval for the buffer files in DurableElasticsearchSink. RollingInterval.Day is used always. We need more flexibility here to e.g. managing file granularity in a ways different from setting limit by buffer file size and count. We do not want to use these limits to ensure that not synced files won't be deleted in any case before they will be synced to the Elasticsearch. Using this limits we have such possibility (there are some cases when not synced file could be removed), so setting these are not an option for us.
Please describe the expected behavior?
There is a possibility to specify RollingInterval for DurableElasticsearchSink
If the current behavior is a bug, please provide the steps to reproduce the issue and if possible a minimal demo of the problem

Implented in PR https://github.com/serilog-contrib/serilog-sinks-elasticsearch/pull/411

Done in https://github.com/serilog-contrib/serilog-sinks-elasticsearch/pull/416


[BUG] Bugs in some endpoints.

While writing the unit-tests, I found out some bugs in the functions of some endpoints, due to those bugs some endpoints are throwing INTERNAL SERVER ERROR in the response body.Allow me to remove these bugs by assigning this issue to me.

Hello @Codeansh, this is Version 2 of Fintech API repository, there had been few major updates, please go through the CONTRIBUTING.md to make further contributions. Thanks.

Please do not close this issue for now, there are some more bugs to be resolved.


when use master branch code compile proxy, client connect proxy cause "Connection refused".

Bug Report

What version of Pisanix are you using?

newest master code.
What operating system and CPU are you using?

Steps to reproduce

What did you expect?
What did happened?
Server:
Jun 27 10:05:26.206 ERROR runtime_mysql::server::server: err:Error { kind: Protocol(Io(Os { code: 61, kind: ConnectionRefused, message: "Connection refused" })) }
thread 'pisa-proxy' panicked at 'called `Option::unwrap()` on a `None` value', runtime/mysql/src/transaction_fsm.rs:314:43
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Jun 27 10:05:43.582  INFO proxy::listener: pisa-proxy client_ip: <IP_ADDRESS> - backend_type: "mysql"
Jun 27 10:05:43.667 ERROR runtime_mysql::server::server: err:Error { kind: Protocol(Io(Os { code: 61, kind: ConnectionRefused, message: "Connection refused" })) }
thread 'pisa-proxy' panicked at 'called `Option::unwrap()` on a `None` value', runtime/mysql/src/transaction_fsm.rs:314:43

Client:
mysql> show databases;
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id:    2
Current database: *** NONE ***

ERROR 2013 (HY000): Lost connection to MySQL server during query
mysql>

Please provide your configuration and the command of starting. @dongzl

# api 配置块，对应命令行参数和环境变量
[admin]
# api 端口
port = "8081"
# 日志级别
log_level = "INFO"

# pisa-proxy 代理配置块
[proxy]
# config a proxy
[[proxy.config]]
# proxy 代理地址
listen_addr = "<IP_ADDRESS>:9088"
# proxy 认证用户名
user = "root"
# proxy 认证密码
password = "12345678"
# proxy schema
db = "test"
# 配置后端数据源类型
backend_type = "mysql"
# proxy 与后端数据库建连连接池大小，值范围：1 ~ 255, 默认值：64
pool_size = 3

# 后端负载均衡配置
[proxy.config.simple_loadbalance]
# 负载均衡算法：[random/roundrobin], 默认值: random 算法
balance_type = "random"
# 选择挂载后端节点
nodes = ["ds001"]

[[proxy.config.plugin.concurrency_control]]
regex = "aaa"
max_concurrency = 5
duration = 333

[[proxy.config.plugin.concurrency_control]]
regex = "bbb"
max_concurrency = 5
duration = 333

[[proxy.config.plugin.circuit_break]]
regex = "111"

[[proxy.config.plugin.circuit_break]]
regex = "222"

# 后端数据源配置
[mysql]
[[mysql.node]]
# 数据源 name
name = "ds001"
# database name
db = "employees"
# 数据库 user
user = "root"
# 数据库 password
password = "123456"
# 数据库地址
host = "<IP_ADDRESS>"
# 数据库端口
port = 3307
# 负载均衡节点权重
weight = 1

Start proxy server command:
LOCAL_CONFIG=true target/debug/proxy -c examples/example-config.toml

when start pisa-proxy, the config path is error, so start success, but client connect refused.

We will optimize in the future.Thanks for your report. @dongzl


Auto-Login Feature

please provide auto-login functionality in google auth and other services

@Kulothungan16 that's a good feature! Also, I had it in my mind some times ago but, I don't remember, there were some complications regarding this at that time :thinking: . I'll see into it again.

thx bro. If I login and close the app without logging out and when reopening the app, it crashes I think it's because of it had been already a logined.

It doesn't crash upon re-opening for me. However there is a known issue of crashing if you logged in using facebook and then closed the app without logging out and again when you open the app and try logging in using facebook.


Move data augmentation outside of training iterations for better training efficiency

In examples/largedataset_cnn/train_largedata.py, the augmentation should be moved outside of training iterations.
For benchmark datasets, e.g., CIFAR-10 and ImageNet, the augmentation method is pre-defined before the model training, so the augmentation does not need to be carried out on the fly in each iteration.

But, the data augmentation is done with some randomness, e.g., random cropping offset and random rotation degrees. If you move it outside of the training iterations, you may lose this randomness. As a result, you may not get much benefit from data augmentation.

The data augmentation is remained inside each training iteration for better classification accuracy


EncoderFallbackException, with powershell, chcp 65001 and 😂

Environment
Windows build number: 10.0.18362.836, ZH-CN
Windows Terminal version (if applicable): v1.0
Any other software? None.

Steps to reproduce
PowerShell:
>chcp 65001
>.\😂

Can't reproduce with PowerShell itself.
Expected behavior

Run the command, or throw CommandNotFoundException.
Actual behavior

��ѽ���������⡣���ڱ���� Bug ʱ���������ϸ��Ϣ��
�� GitHub �ϱ���: https://github.com/lzybkr/PSReadLine/issues/new
-----------------------------------------------------------------------
�� 15 ����Կ:
 c h c p Space 6 5 0 0 1 Enter
 . \ ? Enter

�쳣:
System.Text.EncoderFallbackException: �޷���λ������ 2 ���� Unicode �ַ� \uD83D ת��Ϊָ���Ĵ���ҳ��
   �� System.Text.EncoderExceptionFallbackBuffer.Fallback(Char charUnknown, Int32 index)
   �� System.Text.EncoderFallbackBuffer.InternalFallback(Char ch, Char*& chars)
   �� System.Text.UTF8Encoding.GetBytes(Char* chars, Int32 charCount, Byte* bytes, Int32 byteCount, EncoderNLS baseEncoder)
   �� System.Text.EncoderNLS.GetBytes(Char[] chars, Int32 charIndex, Int32 charCount, Byte[] bytes, Int32 byteIndex, Boolean flush)
   �� System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder)
   �� System.IO.StreamWriter.Dispose(Boolean disposing)
   �� System.IO.TextWriter.Dispose()
   �� Microsoft.PowerShell.PSConsoleReadLine.<>c__DisplayClass81_0.<WriteHistoryRange>b__0()
   �� Microsoft.PowerShell.PSConsoleReadLine.WithHistoryFileMutexDo(Int32 timeout, Action action)
   �� Microsoft.PowerShell.PSConsoleReadLine.MaybeAddToHistory(String result, List`1 edits, Int32 undoEditIndex, Boolean fromDifferentSession, Boolean fromInitialRead)
   �� Microsoft.PowerShell.PSConsoleReadLine.InputLoop()
   �� Microsoft.PowerShell.PSConsoleReadLine.ReadLine(Runspace runspace, EngineIntrinsics engineIntrinsics)
-----------------------------------------------------------------------

I'm pretty sure the garbage text that looks like
��ѽ���������⡣���ڱ���� Bug ʱ���������ϸ��Ϣ��
�� GitHub �ϱ���: https://github.com/lzybkr/PSReadLine/issues/new

Is supposed to be saying "Please report this issue over at https://github.com/lzybkr/PSReadLine/issues/new". I'd bet that PSReadline doesn't really work with UTF-8 all that well.

Needs-Author-Feedback, What feedback?

Can't reproduce with PowerShell itself.

What a fast msftbot!

If what you mean by

Can't reproduce with PowerShell itself.

is "I removed PSReadline and the issue goes away", then this is definitely an issue that should be filed over at https://github.com/lzybkr/PSReadLine/issues/new. Thanks for following up!

It only appears when using PowerShell through Windows Terminal. Sorry for my bad expression.

@zadjii-msft

Sorry, this must have gotten lost in the inbox. Looking through the PSReadline repo, it looks like they're tracking this issue over at PowerShell/PSReadLine#949. That'll probably be the best thread to contribute to. Thanks!


error in my results

thanks a lot for your help.
as you know, I am working in the image reconstruction field.
first step:
I extracted image features with MatConvNet that didn't work well in reconstruction. then, I extracted Caffe image features and then I extracted brain features with fastl2lir and finally, I did reconstruction and my results were very close to your result.
second step:
I update my Ubuntu to the Ubuntu 22 version and I couldn't install Caffe on it. Therefore, I used Torch for image feature extraction. Then, I used Torch image features in Fasl2lir and extract brain features. recently. you uploaded new codes that did reconstruction with Torch. I ran this code with my torch features, but I received big errors. when I ran this code with your data, I received big errors, too. I report this problem to you and you modified your code and errors decreased with your features.
But, when I run this code with my features that extract in the same way (fastl2lir) I still get big errors. The only difference is that I extract image features with Torch. I am attached my code. Please look at them.
I need to use Torch because I want to use resnet and I don't have a strong system in Iran to train this network in Caffe and get resnet.caffemodel. please help me.
for example in this code I extract conv5_1 image features in Torch:
import numpy as np
from google.colab.patches import cv2_imshow
import pandas as pd
import cv2
import os
import torch
from torchvision.datasets import ImageFolder
from torchvision.transforms import ToTensor
from torch import optim, nn
from torchvision import models, transforms
import torchvision.io as io
import torchvision.transforms as transforms
from PIL import Image
import imghdr
from bdpy.dataform import Features, load_array, save_array
Load the VGG19 model
vgg19 = models.vgg19(pretrained=True)
Access the features module
features = vgg19.features
Define a new model that outputs features from the conv3_1 layer
#model = nn.Sequential(features[0:12])
Set the model to evaluation mode
vgg19.eval()
import numpy as np
from google.colab.patches import cv2_imshow
import pandas as pd
import cv2
import os
import torch
from torchvision.datasets import ImageFolder
from torchvision.transforms import ToTensor
from torch import optim, nn
from torchvision import models, transforms
import torchvision.io as io
import torchvision.transforms as transforms
from PIL import Image
import imghdr
from bdpy.dataform import Features, load_array, save_array
Load the VGG19 model
vgg19 = models.vgg19(pretrained=True)
Access the features module
features = vgg19.features
Define a new model that outputs features from the conv3_1 layer
#model = nn.Sequential(features[10])
conv3_1_features = nn.Sequential(*list(vgg19.features.children())[:29])
Set the model to evaluation mode
conv3_1_features.eval()
Load an image
data_dir='/content/drive/MyDrive/image_feature_python/resultes/pytorch_image_feat_training/pytorch/VGG19/conv5_1/'
img_dir='/content/drive/MyDrive/matconvnet/data/training'
Get image files
imagefiles = []
for root, dirs, files in os.walk(img_dir):
imagefiles = [os.path.join(root, f)
for f in files
if imghdr.what(os.path.join(root, f))]
imgs_path = np.array(imagefiles)
#image name
images_name=[]
images=imagefiles
for f in files:
name=f[:-5]
images_name.append(name)
print ('Image num: %d' % len(imagefiles))
for n in range(imgs_path.shape[0]):
print(n)
img = io.read_image(imgs_path[n])
# Preprocess the image for the VGG16 model

# Load an image using PIL
pil_image = Image.open(imgs_path[n]).convert('RGB')

preprocess = transforms.Compose([
transforms.Resize(256),
transforms.CenterCrop(224),
transforms.ToTensor(),
transforms.Normalize(mean=[0.485, 0.456, 0.406],
                     std=[0.229, 0.224, 0.225])
])

#input_tensor = preprocess(pil_image)
#input_batch = input_tensor.unsqueeze(0)

input_tensor = preprocess(pil_image).unsqueeze(0)
# Pass the input tensor through the model up to the conv3_1 layer
features = conv3_1_features(input_tensor)

# Convert to NumPy Array
features_numpy = features.detach().numpy()

features = np.array(features_numpy)
print(features.shape)
feat = np.reshape(features,(1,512,14,14))

savefile = os.path.join(data_dir, '%s.mat' % images_name[n])
 #Save
save_array(savefile, feat, key='feat', dtype=np.float32, sparse=False)

Thank you. Let me confirm two points.

Are you using the same pretrained model for the image feature extraction and the encoder in the reconstruction script? You extracted features with torchvision's pretrained VGG19 in your code. However, the weights of the VGG19 model used as the encoder in the reconstruction script we provided are different from torchvision's VGG19, and they are not compatible. If the model used to calculate image features and the one used as the encoder in the reconstruction script are not the same, the reconstruction will not work correctly.
When calculating image features using torchvision's VGG-19, please make sure that you are not accidentally saving the ReLU layer's features. In torchvision's VGG-19, ReLU is processed inplace, meaning you might mistakenly extract ReLU's features instead of the features from convolutions or fully connected layers.

Thank you.
I have a question about these features that you used. did you extract image features with Caffe and brain features with Fasl2lir???

did you extract image features with Caffe and brain features with Fasl2lir???

Yes, the shared image and decoded features were extracted using Caffe and decoded using FastL2LiR. Furthermore, the weights of VGG-19 used in our PyTorch reconstruction code were actually imported from Caffe, making them compatible with the image features extracted using the Caffe model.

Thank you very much. I ran your code with your data with the generator and without the generator and the resulting figures were the same as the paper. But errors in with generator code were bigger than without the generator. I think this problem is due to calculate errors in the construction function.
for n02190790_15121.mat
with generator results:
iteration = 193; err = 61842.234375
iteration = 194; err = 61800.95703125
iteration = 195; err = 61347.01171875
iteration = 196; err = 61385.69921875
iteration = 197; err = 61229.046875
iteration = 198; err = 61087.90625
iteration = 199; err = 60957.53515625
iteration = 200; err = 60826.23046875
without generator results and function:
recon_image, loss_list = reconstruct(feat,
encoder,
generator=None,
layer_mapping=layer_mapping,
optimizer=optim.SGD,
image_size=encoder_input_shape,
crop_generator_output=True,
preproc=image_preprocess,
postproc=image_deprocess,
output_dir=save_dir,
save_snapshot=True,
snapshot_dir=snapshots_dir,
snapshot_interval=10,
snapshot_ext='jpg',
snapshot_postprocess=normalize_image,
return_loss=True,
**opts)
iteration = 195; err = 47284.10546875
iteration = 196; err = 47321.4609375
iteration = 197; err = 47359.74609375
iteration = 198; err = 47416.3671875
iteration = 199; err = 47473.265625
iteration = 200; err = 47544.5234375


Cannot trigger a new window's ready-to-show via the existed window

I want to open window bw2 via the trigger button in window bw1,  however, the following codes cannot trigger the event of ready-to-show in bw2.
after trigger 'onClickOpenPage2' in bw1, the new window shows, but its ready-to-show event is not triggered.
// bw1.js
import creatBw from './bw2.js';
const bw1 = new BrowserWindow({
  identifier: 'bw-1',
});
bw1.loadURL('page1');
bw1.webContents.on('onClickOpenPage2', () => {
  createBw();
});

// bw2.js
export default function createBw2() {
  const bw2 = new BrowserWindow({
     identifier: 'bw-2',
  });
  bw2.loadURL('page2');
  bw2.once('ready-to-show', () => {
    // cannot be triggered
    console.log('ready-to-show');
    bw2.show();
    bw2.webContents.executeJavaScript('startApp()');
  })
  return bw2;
}

it should be bw.once('ready-to-show', () => { -> bw2.once('ready-to-show', () => {?

yes, it's misspelling, the question still exists? any solutions?

can you try<EMAIL_ADDRESS>

nice, thanks for your help


Investigate part 6 for encryption flag

It looks like part 6 might contain a flag indicating whether an item's data is encrypted. Compare an encrypted nefs with a non-encrypted one. One of the part 6 fields often has a value of either "3" or "1" depending on if encrypted.
Needs investigation, this is a hunch. Could be a bitfield of some kind.
If there is a flag that indicates if the data is encrypted, then nefsedit/nefslib should use this flag when extracting files.

In the old 10600 format it is almost certainly a bitfield

Added in 0.6.0.
The format for part 6 in nefs version 2.0 appears to be the same as 1.6; however, the flags are different. I've identified a few of them for 2.0 and have documented them in the wiki. The flag fields are now used to determine encryption/compression and also whether an item is a directory or not.


Failed to delete Interval by Id

🐞 Bug Report
Affected Command
./edgex-cli interval rm a77fc53e-603c-479e-84cf-a95cc0a63079
Is this a regression?
No
Description and Minimal Reproduction
Depends on https://github.com/edgexfoundry/edgex-go/issues/2558
Once this issue is fixed ..command interval rm <id> should work
🔥 Exception or Error

Error: 404 - 404 page not found

🌍  Your Environment
Deployment Environment:
EdgeX Version:
Anything else relevant?

The dependent issue moved from edgex-go to go-mod-core contracts https://github.com/edgexfoundry-holding/edgex-cli/issues/202 is Fixed and merged
This issue can be closed


2.0.0 Doesn't work with lodash

It always throws errors like this(no errors in previous version):
9:10  error  throttle not found in 'lodash'  import/named

Node version: 12.11.1
Relevant dependencies:
{
    "@typescript-eslint/parser": "2.3.3",
    "@types/lodash": "4.14.142",
    "eslint": "6.5.1",
    "eslint-import-resolver-typescript": "2.0.0",
    "eslint-plugin-import": "2.18.2",
    "lodash": "4.17.15",
    "typescript": "3.6.3"
}

Then what's your actual codes? I'm using lodash without any problem.

Here's a minimal repro: https://github.com/le0nik/resolver-typescript-repro
If you remove the 'import/extensions': ['.ts', '.tsx', '.d.ts', '.js', '.jsx'], line from .eslintrc.js you get no more errors, but that's just because import plugin doesn't even see the typescript files. You can easily check this by changing throttle import to something non-existent - there still won't be any errors.

As an aside: I think that requirement to add baseUrl to compilerOptions in tsconfig.json should be specified in the README, it's not quite obvious and there is no error if it's not present.

@le0nik OK, I see. Now @types/lodash/index.d.ts takes higher priority than lodash/index.js, but eslint-plugin-import didn't understand ts namespace with esInterop correctly.
@benmosher Please point me if I'm incorrect.
And also, I personally disable import/default and import/named for .ts which should have been handled by typescript-eslint.

With the 2.0.0 update we're now getting an error from:
import Dataloader from "dataloader";
error  No default export found in module  import/default

not sure i this is related though.

@sakulstra I think it is just as expected, you can see<EMAIL_ADDRESS>
And also, I personally disable import/default and import/named for .tsx? files which should have been handled by typescript-eslint.

I'm going to close this issue, because it is just working as expected, see my comments above, and I do think it relates to eslint-plugin-import itself.
@benmosher Any advice for this?

@mickdekkers I don't think it's a proper solution, if eslint-import-resolver-node takes higher priority than eslint-import-resolver-typescript, it may not resolve @types/ packages at all. Because node will resolve node_modules/lodash first instead of node_modules/@types/lodash.

@mickdekkers
I don't think it's a solution at all.
You're essentially using the node resolver instead of the typescript resolver (unless the node resolver fails)
And lodash is mapped to node_modules\lodash\lodash.js.
As a result, it seems that all imports are passes, even non existing ones, e.g. import { xxx} from 'lodash'.


Some sprites are being rendered too high

Yeah, this is an artifact of how game objects are created/destroyed on the fly in order to maintain a decent framerate.
One solution might be to call readd on all monsters after any new tiles are drawn. That changes the monster's _id though, so the hit-detection code in each weapon should probably also be updated to not rely on _id if possible.
https://github.com/aMoniker/Gush/blob/master/levels/visibility.js#L121

Stale


pitch black

idk if its just occurring with mine but whenever i jump off opacity levels, the entire screen goes glitching then pitching black. same as when i completely shut off the luminosity then brighten it lol

I didn't encounter this at all. What mac version are you on?

on 10.14.6
Le lun. 19 juill. 2021, à 11 h 04, Daniel Takacs @.***>
a écrit :

I didn't encounter this at all. What mac version are you on?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tannerc/spf/issues/4#issuecomment-882623244, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AS6U2Q5QVCUXVFWA5GX7GRLTYQ5IXANCNFSM4YCJ47RA
.

I have a fork I modified that might fix your problem, in this version the alpha for the NSWindow overlay is 1, in mine, it's the same as the "color-alpha": https://github.com/themprsn/spf-themprsn/releases/tag/<IP_ADDRESS>

i may be manipulating things wrong but that's what's given once downloaded.
In short, it states that the file cannot open as it needs mac10.10+ to
operate..
[image: Capture d’écran, le 2021-07-19 à 18.18.56.png]
Le lun. 19 juill. 2021, à 17 h 17, Daniel Takacs @.***>
a écrit :

I have a fork I modified that might fix your problem, in this version the
alpha for the NSWindow overlay is 1, in mine, it's the same as the
"color-alpha":
https://github.com/themprsn/spf-themprsn/releases/tag/<IP_ADDRESS>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tannerc/spf/issues/4#issuecomment-882866506, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AS6U2Q4P4S3L6KJUUJYUJCTTYSJAFANCNFSM4YCJ47RA
.

Sorry, I must have sent the Big Sur build... I'll send you the other one as soon as I can!

This is a build for macOS 10.14: https://github.com/themprsn/spf-themprsn/releases/tag/<IP_ADDRESS>.14

it unfortunately seems to keep showing the same content....  :$$
Le lun. 19 juill. 2021, à 18 h 48, Daniel Takacs @.***>
a écrit :

This is a build for macOS 10.14:
https://github.com/themprsn/spf-themprsn/releases/tag/<IP_ADDRESS>.14
[image: Screenshot 2021-07-20 at 0 47 38]
https://user-images.githubusercontent.com/87606345/126237147-7b7a205b-1f37-48bb-b5fc-6b8799930574.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tannerc/spf/issues/4#issuecomment-882910508, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AS6U2Q52ELZYQQXNSV3KGT3TYSTS5ANCNFSM4YCJ47RA
.

Oh..:/ I'll do some research to see if I can get it to work for you, it might be a week or two, but I hope I'll be able to send a fixed version:)

alright ! thanks for the investment. there's really no pressure, so do as
you please.
Le lun. 19 juill. 2021, à 19 h 59, Daniel Takacs @.***>
a écrit :

Oh..:/ I'll do some research to see if I can get it to work for you, it
might be a week or two, but I hope I'll be able to send a fixed version:)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tannerc/spf/issues/4#issuecomment-882941126, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AS6U2Q4RSPUII6YW745ZUU3TYS35ZANCNFSM4YCJ47RA
.


Evaluating value of hasMouse causes node to die

> require('ncurses').hasMouse
node: /usr/include/node/node_object_wrap.h:51: static T* node::ObjectWrap::Unwrap(v8::Handle<v8::Object>) [with T = Window]: Assertion `handle->InternalFieldCount() > 0' failed.
zsh: abort      node

node 0.4.11-1 (packaged by Arch)
node-ncurses 0.2.0 (from npm)

Don't worry about it, I think I know what the problem is but I won't be in a position to push a tested fix until next week.


Remove PlanningTestHelper from plan-consumer-test.ts

argh https://github.com/PolymerLabs/arcs/pull/4123
we need to coordinate better :(
PS: i'll review tomorrow.

Argh^2. I almost didn't continue with this CL, but since it was close to
done just finished it up. I can change to a different task if you're happy
to plough through these, or you can let me know which files you aren't
working on.
On Fri, 22 Nov 2019, 17:05 Maria Mandlis<EMAIL_ADDRESS>wrote:

argh #4123 https://github.com/PolymerLabs/arcs/pull/4123
we need to coordinate better :(
PS: i'll review tomorrow.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/PolymerLabs/arcs/pull/4126?email_source=notifications&email_token=AIHN4TMPPCIIDIGOSN2QIILQU5ZDHA5CNFSM4JQMABF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE4UZDQ#issuecomment-557403278,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIHN4TMNXXP542QGPD3GKCTQU5ZDHANCNFSM4JQMABFQ
.

Thanks for reviewing, but I'll drop this in favour of yours. Sorry for this, I should have communicated that I was still working on the PR.


Inquiry about the pre-trained Mask R-CNN checkpoints

Hi,
Thanks for your interesting work and the release of the source codes!
I'm trying to use the pre-trained Mask R-CNN checkpoints you've published via Google Drive,
but based on what I've examined, it seems that the checkpoint mrcnn_alfred_receptacles_004.pth is associated with 73 classes like mrcnn_alfred_objects_sep13_004.pth, whereas constants.STATIC_RECEPTACLES contains 32 classes:

I'm getting an error if I call load_state_dict() of the Mask R-CNN model created with len(constants.STATIC_RECEPTACLES) + 1 as an argument.
Would there be any possibility that the checkpoint mrcnn_alfred_receptacles_004.pth is in fact for constants.OBJECTS_DETECTOR rather than constants.STATIC_RECEPTACLES?
I would really appreciate it if you could help me with this issue.
Thank you!

@yeda318, good catch. It's been a while, maybe I uploaded the wrong file.
You probably have to train the receptacle detector yourself with this script.

@yeda318, I found the right file: https://github.com/alfworld/alfworld/releases/download/0.2.2/mrcnn_alfred_receptacles_sep13_007.pth
d = torch.load('mrcnn_alfred_receptacles_sep13_007.pth')
d['roi_heads.box_predictor.cls_score.weight'].shape
torch.Size([33, 1024])

I don't know if the checkpoint is good, but I hope this helps!

@MohitShridhar, thank you for your prompt response and for providing the necessary file. It appears to be what I was looking for, and I believe it will greatly benefit our project. Thanks again!


fix: packagePath correctly treated as relative path from service dir

Hey.
This PR ensures that a provided packagePath is always resolved relative to the current working directory e.g serverless.yml dir.
Currently the packagePath is resolved based on the directory containing the currently executing file, i.e /my-project/node_modules/serverless-esbuild/dist/pack-externals.js;
https://github.com/floydspace/serverless-esbuild/blob/2c1d2ac842ac4270c48028d123887193ae957af2/src/pack-externals.ts#L78
If you change the packagePath with this in mind then it fails over when trying to resolve the package-lock.json later due to trying to resolve relative to the current working directory.
https://github.com/floydspace/serverless-esbuild/blob/2c1d2ac842ac4270c48028d123887193ae957af2/src/pack-externals.ts#L311
Considerations:

I have used process.cwd() to determine current working directory as seen in the util function findUp.
This my have gone unnoticed as the log message for whether or not the lock file is used is LEVEL verbose.

I've noticed that localModulePackagePath now contains the cwd() twice since path.dirname(packageJsonPath) will begin with it already.
Example<EMAIL_ADDRESS>This fixes it:
    const localModulePackagePath = path.join(
      process.cwd(),
      path.relative(process.cwd(), path.dirname(packageJsonPath)),
      'node_modules',
      externalModule.external,
      'package.json'
    );

localModulePackagePath

Hey - I think in your case you don't need to set a packagePath at all as it would appear you are calling the command in the directory of the package.json.
Try removing the build option completely?
I think possible the docs could be improved to highlight that packagePath should be a relative path.

@codingnuclei I do not have packagePath set in my config.

@webdeveric yes this does seem to be a bug introduced.
In the mean time, setting packagePath: "./package.json" should fix the problem in the immediate.
I think fixing it higher up might be a better spot.
https://github.com/floydspace/serverless-esbuild/blob/f7f1e9b0d4cbf3a33351824bd429a394a69e949e/src/pack-externals.ts#L240-L241
 const packageJsonPath =     this.buildOptions.packagePath ||     path.relative(process.cwd(), path.join(findUp('package.json'), './package.json'));

@all-contributors
please add @codingnuclei  for maintenance, ideas.
please add @webdeveric  for question, review.


Library to Manual Transfer

This is a transfer from Library (threefoldfoundation) to Manual (threefoldtech), with many important T&C, definitions and legal terms. It would thus be great to have different reviews on this. Especially from legal and dev circles.

To note

We keep the official source of truth disclaimer being the library legal repo, we can discuss when we remove it

We use include to inject an md file (doesn't need to be a file in the SUMMARY) into the current md file

{{#include ./sub/the_single_source_truth.md}}

We use HTML script to print the time of generation of the book (when server runs mdbook build)

<script>
  // Get current date and time
  var now = new Date();
  var threefold_companies0_datetime = now.toLocaleString();

  // Insert date and time into HTML
  document.getElementById("threefold_companies0_datetime").innerHTML = threefold_companies0_datetime;

</script>

We leave some unused files for future library to manual transfer
This should resolve many of the current issues
After this PR is reviewed and accepted, we can then remove the FAQ questions leading to the library material

Users can use the search function and access all info
One of the FAQ functions was/is to link the manual to the library if pages are missing

When we implement the website link checker, we can make sure all links work. For now, I did manual testing of each page locally. Let me know if you find broken links!

Thanks!
@AhmedHanafy725 @scottyeager @xmonader @ramezsaeed @A-Harby @sabrinasadik

Update

Added new commits to finalize the library to manual transfer. Most if not all the transfer should be done.
The new commits answer this issue


Misc minor fixes and typos

A collection of fixes applied while the upstream repo was used in the Kainos Belfast Platform Academy 2023

Hi @thomast1906, would you review this old PR please? Thanks!

Thanks @AlexGidarakos - included most in this https://github.com/thomast1906/DevOps-The-Hard-Way-Azure/pull/9


BeanShell

https://github.com/beanshell/beanshell

BeanShell is heavily used for JEdit scripting.

Thanks!


Review

These are the missing/incorrect validations:

[ ] If there are any non-default proposal types, verify that all receivers support that proposal type.
[ ] If a commit is from a new_member_commit sender:

[ ] Verify at most one Remove proposal.
[ ] If Remove is present, verify new and old credentials represent the same client.
[ ] If Remove is not present, verify credential does not represent a client already in the group.

[ ] If commit is from a member:

[ ] Verify no Update or Remove proposal applies to the same leaf as another.
[ ] Verify Add proposals represent distinct clients.
[ ] Verify no Add proposal represents a client already in the group, unless there's a corresponding Remove proposal.
[ ] If a ReInit is present, verify it is the only proposal.
[ ] Verify there's no ExternalInit proposal.

[ ] If path is populated, verify that none of the public keys of the UpdatePath appear in any node of the ratchet tree.
[ ] For Add proposals, verifying the expiration should be optional.
[ ] For Update proposals, verify new and old credentials represent the same client.
[ ] For GroupContextExtension proposals:

[ ] Verify all members of the new group indicate support for all extensions.
[ ] If there is a RequiredCapabilities extension, verify all members of the new group indicate support for required capabilities.

[ ] If there's no GroupContextExtension proposal:

[ ] Verify all members of the new group indicate support for all extensions in GroupContext.
[ ] If there is a RequiredCapabilities extension in the GroupContext, verify all members of the new group indicate support for required capabilities.

[ ] Verify uniqueness in the new group of all members' signature_key and encryption_key.
[ ] Verify that each LeafNode's credential type is supported by all members of the new group.

Where a validation has been implemented incorrectly, I tried to leave a note in the code.

Thank you! I am starting to go through these. I will create the PRs upstream and then we can merge them here.

@Bren2010 thanks for the overview. Validation is not yet complete in OpenMLS, but some of the checks are tracked here. Note that this is a moving target and we are working towards a more holistic view.
At first sight, it looks like quite a few checks you mention should already be checked. If you think something is incorrect, we'd be interested in knowing what exactly it is.

I have added most of the checks to the (still incomplete) validation dashboard we recently set up. There are a few things I am not sure about, though:

For Add proposals, verifying the expiration should be optional.

Can you elaborate what you mean by this? I understand the RFC allows being more lenient in the validation, but my understanding is that this is up to the implementation.

For Update proposals, verify new and old credentials represent the same client.

I believe that is based on this paragraph, is that correct? the responsibility of the AS, and not OpenMLS. That said, we definitely still have some work to do to help the AS to do all the checks.

Verify all members of the new group indicate support for all extensions.

as well as

Verify all members of the new group indicate support for all extensions in GroupContext.

I don't think so. My understanding of the RFC is that we only have to check that these are in the required capabilities.


[CHANGE] application/json

The mimetype affected
Please enter the mimetype here
The change to make
Add/remove/change description or link, etc
Supporting link
A link to somewhere that authoritatively says why this change should be made

@Tijdloo you missed something 😂


UI/UX: Company dashboard

The company dashboard is a bit difficult to navigate through, I think an update is in place.

Closed in #232


{ARM} Bump azure-mgmt-resource from v2019-07-01 to v2020-06-01

Description

Bump azure-mgmt-resource from v2019-07-01 to v2020-06-01
For PR: #13429 #14241
At the same time, some compatibility logic was made for the breaking change of SDK to ensure that breaking will not be produced on the CLI side, such as: click
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

add to S173

@samkreter Could you please help to review this PR for your part~

/azp run


internal_link: allow streamID without stream name

This commit allows for the internal links to be of the form:
https://chat.zulip.org/#narrow/stream/3/topic/send_message.20API. Previously, only internal links of the form:
https://chat.zulip.org/#narrow/stream/3-backend/topic/send_message.20API were supported.
Fixes #4185

Thanks @AdityaYadavalli1 !
Some discussion in this chat thread.

Thanks @AdityaYadavalli1 !
Some discussion in this chat thread.

Thanks for the revisions, @AdityaYadavalli1!
When I run tools/test on each commit in the branch, I see that not all commits pass.
From your streamID branch (i.e., after running git checkout streamID, you can do git rebase -i --exec 'tools/test' as a shortcut for running tools/test on each new commit in the branch, i.e., each commit that's on streamID but isn't on the branch that streamID is set up to track.
(Normally, it's helpful to set up streamID to track master on https://github.com/zulip/zulip-mobile. E.g., if the remote pointing to https://github.com/zulip/zulip-mobile is called "origin", the default name, streamID would be set up to track it if you've run git branch -u origin/master. In my own dev environment, I've decided to use the name "upstream" instead of the default "origin", but that's up to you.)

Thanks for the revisions, @AdityaYadavalli1!
When I run tools/test on each commit in the branch, I see that not all commits pass.
From your streamID branch (i.e., after running git checkout streamID, you can do git rebase -i --exec 'tools/test' as a shortcut for running tools/test on each new commit in the branch, i.e., each commit that's on streamID but isn't on the branch that streamID is set up to track.
(Normally, it's helpful to set up streamID to track master on https://github.com/zulip/zulip-mobile. E.g., if the remote pointing to https://github.com/zulip/zulip-mobile is called "origin", the default name, streamID would be set up to track it if you've run git branch -u origin/master. In my own dev environment, I've decided to use the name "upstream" instead of the default "origin", but that's up to you.)

Thanks for the revisions, @AdityaYadavalli1!
When I run tools/test on each commit in the branch, I see that not all commits pass.
From your streamID branch (i.e., after running git checkout streamID, you can do git rebase -i --exec 'tools/test' as a shortcut for running tools/test on each new commit in the branch, i.e., each commit that's on streamID but isn't on the branch that streamID is set up to track.
(Normally, it's helpful to set up streamID to track master on https://github.com/zulip/zulip-mobile. E.g., if the remote pointing to https://github.com/zulip/zulip-mobile is called "origin", the default name, streamID would be set up to track it if you've run git branch -u origin/master. In my own dev environment, I've decided to use the name "upstream" instead of the default "origin", but that's up to you.)

Hi @chrisbobbe!, sorry for the late reply. Yes, you are right. Other than the last commit, all the others don't pass the tests. Would you like me to squash those commits?

Thanks for the revisions, @AdityaYadavalli1!
When I run tools/test on each commit in the branch, I see that not all commits pass.
From your streamID branch (i.e., after running git checkout streamID, you can do git rebase -i --exec 'tools/test' as a shortcut for running tools/test on each new commit in the branch, i.e., each commit that's on streamID but isn't on the branch that streamID is set up to track.
(Normally, it's helpful to set up streamID to track master on https://github.com/zulip/zulip-mobile. E.g., if the remote pointing to https://github.com/zulip/zulip-mobile is called "origin", the default name, streamID would be set up to track it if you've run git branch -u origin/master. In my own dev environment, I've decided to use the name "upstream" instead of the default "origin", but that's up to you.)

Hi @chrisbobbe! Sorry for the late reply. Yes, you are right. Other than the last commit, all the others don't pass the tests. Would you like me to squash those commits?

As per our discussions in this chat, I have squashed the commits. You can take a look at it now.

Thanks, @AdityaYadavalli1!
Merged, with a few tweaks:

Added a separate commit, at the beginning, dedicated to clarifying in the tests that an integer by itself isn't malformed in the new format.

Removed the following change from one of the commits, as it wasn't in quite the right direction (see https://github.com/zulip/zulip-mobile/pull/4413/commits/70558725dfa90475749ec2f724ba795d9a814b12#r576315663):
- expectAsName(`-${streamGeneral.stream_id}`);
+ expectAsName(`-${streamGeneral.name}`);

Changed "internal_link" to "internalLinks" in the subject lines of the commits; "internal_link" doesn't correspond to an area of the mobile project's code.

Squashed the last two commits together, so we adjust the tests at exactly the same time as we change the behavior that we're testing.

Added "Fixes: #4185" to the commit that fixes the issue, so the fix is official (:tada:)!

Edited the commit messages a bit, adding a bit more detail in the commit-message bodies, and shortening summary line lengths to 76 or below (https://zulip.readthedocs.io/en/latest/contributing/version-control.html).

I am glad I was of help (however small it is). I will keep these in mind when I contribute in the future :))

Thanks for your help, @AdityaYadavalli1! 🙂


Localization - invalid global fetch commands?

Global fetch commands in the English localization files (for ex. '[CmtGlobalVar.GetValue.CmtVarTermForcedEoc]' on line 27 of CrisisManagerEvent_l_english.yml) are highlited as invalid by the CWTools VScode extension. Verify that these fetches work as intended in localization files; if they don't replace them with something that does.

Tested a few of them; the localization files seem to be reading cm's globals just fine. The issue must be with CWTools. Closing this for now unless issues show up.


Custom Pylint Message Template

Background
I came across this stackoverflow question concluding that vs-code overwrites the pylint message format. It opened #382.
#382 wondered why this is and it's because vs-code needs a specific format in order to parse information from pylint.
This was addressed in #495 when the pylint message was changed to show the human-friendly version of the E/F/W/C/R code. While a discussion was held and a feature almost implemented allowing for a custom message format, the feature was never merged and, in the end, outdated and closed.
Feature
In the discussion, the general opinion came to be that an option for a custom message should be available to allow for more flexible workflow (/ compatible with already established workflows):
"python.linting.pylintMsgTemplate": {
	"type": "string",
	"description": "Controls the message template for linting results, as a new-style python format string. The provided value will be appended to '{line},{column},{category},', which is required by VSCode. The previous message format, using numeric message codes, can be restored by setting this to '{msg_id}:{msg}'. Available fields are described at https://pylint.readthedocs.io/en/latest/user_guide/output.html.",
	"default": "{msg} ({symbol})",
 	"scope": "resource"
},

Where the message could then be customized ny the user in the settings.json like:
"python.linting.pylintMsgTemplate": "[{msg_id}] {msg} ({symbol})", // just an example...

The custom message (default: "{msg} ({symbol})") would then be concatenated after the message required for vs-code to parse the pylint message, and the user would be happy to have more control over.
Discussion
While this is a minor feature, I believe it is in the spirit of vs-code being flexible and customizable. I was shocked when I found out a custom pylint-message was not already supported since I took it for granted already being implemented.
I think the solution to this problem would be general enough to maybe allow for custom message-templates for the other linters as well.
Any thoughts? :)

Thank you for the suggestion! We have marked this issue as "needs decision" to make sure we have a conversation about your idea. We plan to leave this feature request open for at least a month to see how many 👍 votes your idea gets to help us make our decision.

Could be possible to have included as text at least the category and msg_id?

Sorry, I intended the letter indicating the category.

Thanks @EriKWDev! I lost 6 hours to finally understand that "custom pylint-message was not already supported in vscode".
vscode is so close to perfection....
I am fighting against this one:
Module name "Checkin_Main" doesn't conform to snake_case naming style
and I can't find the reason for it... unfortunately here:  no luck to find that "snake" message.
I also tried this in setting.jason:
"python.linting.pylintArgs": ["--extension-pkg-whitelist=wx", "--msg-template={path}:{line}: [{msg_id}({symbol}), {obj}] {msg}"]
but it does not work.
So much was already done here, I hope they will work on this soon.
thanks to all vs code developers, you guys rocks!

Hello. Today I've met the same problem like author of the issue. And for me was surprise that user can't change default  "msg-template". I think if that functionality will not be added, default "msg-template" has to contain code of error (msg_id)  necessarily like for flake8, because in order to I can add some error in disable(ignore) I should look for error code in google by error message what is not so convenient. I believe that in the near future you will find the best way to decide this problem.

The output format can’t add {msg_id} so I can’t stand it, so I would rather use shell to add {msg_id} using pylint.

We now a prototype for linting using pylint over Language server protocol. Please try out the prototype and provide feedback. Instructions here https://github.com/PyCQA/pylint/issues/5796#issue-1133069729 . Let me know if this helps with your issue.


Fix settings docs

The Settings upgrade docs are out of date

Preview is available here:http://developers-pr1024.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr1024.previews.kube001.services.stellar-ops.com


some imports appear to be really really slow

Hello,
I found that some imports take quite a while, at least on my Mac laptop.  Specifically
from kaldi.asr import NnetLatticeFasterOnlineRecognizer

takes over 7 seconds.  Is this just dynamically linking the relevant .so (on on mac .dylib) files?
On my system libkaldi-nnet3.dylib is 17MB, which appears the largest of all the .dylib files, but still this is not a lot to load from disc (maybe the linking takes long?).

There doesn't seem to be much room to work with here since the asr module pretty much imports all pykaldi modules. Seems like the slowness comes from the python code being interpreted and not the linking itself (although it might contribute a bit).
Speeding up this import would require splitting up most large modules inside pykaldi so we can import things separately, but that would not be very nice in terms of user experience.

OK, thanks.  Is it a lot of python code that gets generated by clif? I had the impression it was all precompiled, so there probably is not much leeway there.
BTW on a supposedly beefier linux machine the import mentioned above takes about a second, so perhaps it is related to MacOS or the laptopness.  Usually I don't see such large speed differences.


travis allowing failures on OS X

.travis.yml has:
matrix:
allow_failures:
- os: osx
added in 9d74487e8
I think the build is fine on the mac; if no one objects, I'll remove this in the next few days and see what explodes

:+1:
El 6 mar. 2018 9:59 p. m., "Will Coleda"<EMAIL_ADDRESS>escribió:

.travis.yml has:
matrix:
allow_failures:

os: osx

added in 9d74487
https://github.com/perl6/doc/commit/9d74487e842f3e322273c9bf2e010ff598f7d8ed
I think the build is fine on the mac; if no one objects, I'll remove this
in the next few days and see what explodes
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/perl6/doc/issues/1828, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAB9DzOOICPIpR-9WTZafC1vo8biR6cks5tbviXgaJpZM4Sfa31
.

@coke Create temporarely branch for the .travis.yml changes and see if Travis complains or not?

Nothing exploded, but now this is not tested... So maybe we could try and add it back as part of the matrix.

I think I'm closing this. Now build is docker and executable based. None of them work on the Mac. We might create a new one from scratch to test on the Mac, but that would be a different issue.


Enhancement to support for session management

Flogo needs support for session management. For activities that communicate using session based protocols (thinking JMS here) Flogo activities should be able to 'Register' a Session Handler within the Engine. When the activity Eval method is invoked it should pass within the context the Session Handler interface in order that a valid session can be retrieved (likely from a Pool).
Also Activities require the ability to support lifecycle events such as Start or Stop that are called on initial App instantiation and destruction in order to handle cleanup activities.

This has been implemented and is supported with connections.Refer to project-flogo/edge-contrib#14


Excessive energy consumption

This morning, while trying the app I found that for about 11 minutes of use an energy consumption of 88mah was recorded. Far too many if we consider that a mp3 player consumes about 55~100mah/hour.
I didn't even initiate a node synchronization:
I just explored the app and launched the scanner (camera) a couple of times to detect a qr code (which I never scanned).
How is this possible? Can anything be done to stop this bleeding of energy?
Zap version 0.5.6 (3036)
OS Android 12
Device OnePlus Nord 2T 5G

Thanks for making me aware of that.


Correct class color coding in report

in the jupyter notebook, under "Image Ouput Visualization", the class IDs should be: background (0), root tissue (1), early elongation zone (2), late elongation zone (3), and meristematic zone (4).
https://github.com/qbic-pipelines/root-tissue-analysis/blob/dev/modules/containers/rtsstat/reporting.ipynb

This has been fixed here: https://github.com/qbic-pipelines/root-tissue-analysis/pull/21


Hierarchy Support

Can you add suport for this plugin : https://github.com/CortexPE/Hierarchy
And can y have you comunitis discord(or you don't have one?)?

Hierarchy/HRKChat support has already been added: https://github.com/DaPigGuy/PiggyFactions#hrkchat-tags
Discord: https://discord.com/invite/qmnDsSD


docs: typo in "Working with Sections"

In the web page:  https://python-docx.readthedocs.org/en/latest/user/sections.html
a sample code has a mistake in writing:
Adding a new section
The Document.add_section() method allows a new section to be started at the end of the document. Paragraphs and tables added after calling this method will appear in the new section:

current_section = document.section[-1]  # last section in document

Here,  the "section[-1] "  shoule be  " sections[-1] ".

<<<current_section = document.section[-1]  # last section in document

Thanks @adustinsky, this is fixed and will go out with the upcoming release :)


feat: type declaration

Feature Proposal
Added Declaration files for type support
Changes
There is no breaking changes, only package.json has been updated and added Razorpay, Api instance d.ts files including modules
Api reference
Addon api
Plans api
Items api
Usage
import Razorpay = require("./dist/razorpay")

const instance =  new Razorpay({
    key_id: "",
    key_secret: ""
})

TODO:

Ensure no breaking change is happening cause of types.
Use yalc/verdaccio to test if the public types are correctly defined and getting resolved. (you can also try out this tool https://arethetypeswrong.github.io)

@sidag95 Updated changelog.md for new release. Could you please let me know if it is looking good according to what we made changes?


Implement String#unpack('w')

Another fix for #667
The current state is very much a work in progress, I'm just pushing it here prematurely to both let people know somebody is working on this and to keep myself accountable for actually finishing it

@seven1m Is it okay if I start by splitting the header file into a header and a cpp file? Currently I have to recompile pretty much the whole application when I change an internal of unpack_w, which feels a bit off.

Yeah that's fine. Go for it!

This should fix item for both #195 and #667. We can probably close #667 once this one is merged: there are two FIXMEs left in spec/core/string/unpack, but those are the "cannot unpack a string except from the same object that created it, or a duplicate of it" which is really deep into the internals, and does not exactly match the "good first issue" tag.


Image: setTexture still doesn't leave the scaling intact?

E.g. I seem to need this workaround:
	void onThemeChanged() override {
		setTexture(Theme::getTexture()); // note: e.g. the ARROW is at {{0, 42}, {6, 6}}
		scale(scale()); //!!Should do this itself!
	}

Well, #198 handled it, as an accidental duplicate.


External MySQL DB support

Does the Metabase Operator supports an external MySQL DB? I see from the configurations of the CRD that it supports only a PostgreSQL DB managed via Kubernetes StatefulSet, is that correct?

Thanks for the question, only PostgreSQL DB for the moment. I will think of adding more DBs if enough people ask for it.


Only use proxy pad with web source

Sure, but why is only the web source affected?

I honestly have no idea


[Discussion] Access\hasAccessToAll?

I have been reviewing the majority of the code for Backpack for personal growth and understanding of it all. I noticed a function called "hasAccessToAll" under "PanelTraits\Access" however it is only used within tests. Is this something we really need, planning to implement further or is it something we can cut out to help have less useless functionality?

Seems that PanelTraits\Access\hasAccessToAny() is the exact same code and still only used in tests..

But because -we- don't use it other than in unit tests doesn't imply no-one else uses it...

Correct, I didn't say it couldn't be a potential "breaking change" but Repetitive code/unused code just adds clutter, more processing the CPU does, etc.

Just to unclatter the boards, I'm going to close this:

Firstly, if it were going to "disappear" it probably should have in the latest upgrade;
Secondly, even then it probably should have been deprecated a lot earlier;
Thirdly, we don't know who out there uses it.

Feel free to re-open again if it seems it should be deprecated.


Using the new getOutput of Vaapidecoderbase

use the new getOutput  to replace the old one and modify related code.
remove the global variables.

@xuguangxin
have changed code according to tips

-1
I need more information on background of these requests?  What target project or use case?

In addition to @uartie comments, it's clear some of this was not tested.  This has to be verified as well for all configurations not just the Android use case.

HI @seanvk:
This patch set will remove all getOuputs in current code, excpet SharedPtr getOutput().
just like I mentioned in this comment https://github.com/01org/libyami/pull/207#issuecomment-93186729. It's not for android, just code refact for api simplify.
It's just early code review make sure @clearlylin walk in right way. Before this code committed. we will do full regression test. Maybe @clearlylin  need mention it's a early version in pull request.

have changed.

-1
I don't think it is the right way to go.
codec lib exposes interface to other module to less the low level dependency, it should share common data; with camera by dma_buf (kernel generic concept), with opengl by drm_name/dma_buf, with common media pipeline by raw data; and maybe other generic concept data in the future.
libva/vaSurface is vendor specific driver interface, it is inconvenient to use and incorrect to be shared with external module. you should NOT expect camera/opengl/opencl module to depend on libva.

there are three getOutput(), only the following one is the direction to go:
getOutput(VideoFrameRawData* frame, bool draining = false)
the other two exists because of historical reason.

VideoRenderBuffer *getOutput(bool draining) exposes implements details to support omx (in an ugly way)
getOutput(unsigned long draw, int64_t *timeStamp
, int drawX, int drawY, int drawWidth, int drawHeight, bool draining = false
, int frameX = -1, int frameY = -1, int frameWidth = -1, int frameHeight = -1)
this is convenient for X11 only, with additional gpu copy comparing to exporting buffer handles.

Hi Halley:
current we have 4 getOutputs in IVideoDecoder

virtual SharedPtr<VideoFrame> getOutput() = 0;
virtual const VideoRenderBuffer* getOutput(bool draining) = 0;
virtual Decode_Status getOutput(unsigned long draw, int64_t *timeStamp
, int drawX, int drawY, int drawWidth, int drawHeight, bool draining = false
, int frameX = -1, int frameY = -1, int frameWidth = -1, int frameHeight = -1) = 0;
virtual Decode_Status getOutput(VideoFrameRawData* frame, bool draining = false) = 0;

I prefer use virtual SharedPtr<VideoFrame> getOutput() = 0; to replace other 3.because

It makes api more simpler
We do not need compile any X/android/wayland related thing in decoder. we just decode bitstream and output VASurfaceID. With this VASurfaceID customer can do any thing they want. They can output it to X (even in different thread). They can convert it to drm_name/dma_buf. They can map and and read surface. All just few lines libva code. not difficult to do.

It makes our api orthogonal  with libva's.
If you take a close look at VideoFrameRawData or X version of getOutput, it just a wrapper of libva's function. It do not provide value added things.  Why not let caller call libva api directly?

It make internal  implemention and  external user much more easy.
If we want support RGB in VideoFrameRawData. We must keep a internal RGB VAImage pool in our decoder. But how many RGB image we should keep? What if customer not want use our internal VAImage. They want  use they owned RGB meory?Key point here is, we put two different things in this api  decode and vpp. Split them to two functional block will makes us more flexible.

camera/opengl/opencl module never directly operate with libyami.
It always have some proxy,  such like v4l2decode. we can map the egl image or android native window buffer to VASurfaceID in v4l2decoder. use vpp api do color space conversion.

I prefer getOutput(VideoFrameRawData* frame, bool draining = false).
it is simple, it gets desired data in one call, it doesn't introduce additional dependency.

it is not good choice to force yami client call libva directly.
libva is vendor specific driver interface, yami's client usually are MMF/plugin or application. they needn't  touch driver interface.
the situation is similar to: opengl/opencl clients needn't call directly to libdrm, gtk application needn't call directly to x11.

RGB frame data is required because of hw limitation(usually). such work around should be enclosed inside vendor specific module, not pollute upper layer.
most hw doesn't have such limitation (intel will eliminate such limitation in future platform as well), and the limitation can be worked around in gfx/client side ( draw nv12 as two texture unit) with better performance.
getOutput(VideoFrameRawData* frame, ...) supports VASurface as well, if client requires additional feature, it is possible.

proxy is not must.
we have already seen camera with libva through dma_buf, libyami can go there directly (camera dma_buf example).
we have already seen opengl with yami through drm name (weston).
we talk about v4l2codec recently, the major reason is to standardized the interface; in technical, the proxy is not must.
even when there is a proxy, it's part of codec lib (libyami); not proxy by the client itself.

it is ok to separate color-space conversion to a separate API to avoid implicitly VAImage pool; but vaSurface is not value in else cases.

I see. Big difference between us is you think we should hide libva under libyami. But I think add libva dependent to yami caller is not problem. mediasdk did this, ffmpeg did this too
Because libyami's caller(the proxy i mentined) is not media framework. It should be the media framework plugin. More specifically, it's  gstreamer or v4l2 or omx plugin. Handle drm_name/dma_buf/android_native_window/malloc memory to VASurfaceID mapping in plugin level is more flexible to customer and it makes libyami more simpler.

the reference code you mentioned does vaGetDisplay/vaInitialize() as well; and many other libva details. it's not what yami's client to position.
they shrink core codec lib but provide total solution in the APP. it's the way to support app one by one, not a way to create portable lib.
context and handle are passed by opaque data with internal convention; they are limited by the data structure defined for pure sw codec. I don‘t like such tricks.
you can discuss with more team members to decide go or not.

how about separate libyami to two parts, the core part uses your proposed interface, the utility part helps the input/output variant.
take "V4l2Decoder::createVaSurface(const ANativeWindowBuffer* buf)" as example. it is not only required by v4l2codec, but also other wrappers like omx.

we can talk more in meeting

@xuguangxin
have run regression test. only h264 ,vp9

@xuguangxin
have edited it according to your advise

several vp9 videos have problem.
pull request 401 describe the problem.

this merged to #450, so close it


Set light level before the light turns on

I use Shelly switches for my lights and i can set their light level without turning them on, so when i turn them on they are already at the right level. Is it possible to use this feature with adaptive-lighting? Currently they flicker when i turn them on as they go to 100% then back to to the adaptive-lighting level.
Thanks.

You could turn on your lights with this script:
https://github.com/basnijholt/home-assistant-config/blob/d512ea273c8238a6c642a3e3f26a973662e3e0cb/scripts.yaml#L497-L509
Instead of calling light.turn_on in your automations.

Thanks @basnijholt, I don't think the software that comes with my Shelly lights lets me choose the API call to HA, i believe it just does light.turn_on. Is there a way to override it or something?

This is for turning on the lights with the wall switch. It would be ideal for adaptive lighting to adjust the settings of the light continuously while the light is off, so when it is turned on via the switch it is at the right setting.
I want the same solution for lights I have in ESPHome which use a GPIO switch. I could in theory have the GPIO switch call the HAAS api instead of turn the lights on locally, but that would leave me with no local control of my lights if homeassistant is down. I don't want to put myself in that situation.

I use Shelly switches for my lights and i can set their light level without turning them on, so when i turn them on they are already at the right level. Is it possible to use this feature with adaptive-lighting? Currently they flicker when i turn them on as they go to 100% then back to to the adaptive-lighting level.

I can do the same thing with my Insteon switches and one of my Z-Wave switches, so I set up a flow in Node-RED to update the on values values. While it isn't perfect, every 5 mins it pulls the dim level from Adaptive Lighting and uses it to set the on level in the switches. It runs on a 5 minute timer, so it keeps the value pretty close to what AL will set it to. Doing it this way also allows me to force an on-level in some of the switches for devices that don't come on at all with a lower level. I have some LED lights that are fine running at 30% for example, but I have to turn them on at at least 50% or they won't turn on.

```json
[{"id":"c5aa92e5.22436","type":"tab","label":"Adaptive Lighting","disabled":false,"info":""},{"id":"c19fc9af.8fc3a8","type":"comment","z":"c5aa92e5.22436","name":"Set dim levels based on Adaptive Lighting","info":"","x":200,"y":60,"wires":[]},{"id":"9965eebf.1b0e7","type":"api-current-state","z":"c5aa92e5.22436","name":"Adaptive Lighting Values - Master Bath","server":"a54a6202.f4317","version":3,"outputs":2,"halt_if":"on","halt_if_type":"str","halt_if_compare":"is","entity_id":"switch.adaptive_lighting_master_bath","state_type":"str","blockInputOverrides":false,"outputProperties":[{"property":"payload","propertyType":"msg","value":"","valueType":"entityState"},{"property":"data","propertyType":"msg","value":"","valueType":"entity"}],"for":0,"forType":"num","forUnits":"minutes","x":200,"y":200,"wires":[["2d7492cb.00810e","3edd5f44.cfef"],[]]},{"id":"8551efbb.d277f","type":"api-call-service","z":"c5aa92e5.22436","name":"Set Master Bath Brightness (Z-Wave)","server":"a54a6202.f4317","version":5,"debugenabled":false,"domain":"zwave_js","service":"set_config_parameter","areaId":[],"deviceId":[],"entityId":["light.master_bathroom_light"],"data":"{\"parameter\":10,\"value\":\"{{payload}}\"}","dataType":"json","mergeContext":"","mustacheAltTags":false,"outputProperties":[],"queue":"none","x":1070,"y":220,"wires":[[]]},{"id":"cd33a3a2.42259","type":"api-call-service","z":"c5aa92e5.22436","name":"Set Master Bath Brightness (Local)","server":"a54a6202.f4317","version":5,"debugenabled":false,"domain":"zwave_js","service":"set_config_parameter","areaId":[],"deviceId":[],"entityId":["light.master_bathroom_light"],"data":"{\"parameter\":9,\"value\":\"{{payload}}\"}","dataType":"json","mergeContext":"","mustacheAltTags":false,"outputProperties":[],"queue":"none","x":1060,"y":280,"wires":[[]]},{"id":"2d7492cb.00810e","type":"stoptimer","z":"c5aa92e5.22436","duration":"5","units":"Minute","payloadtype":"num","payloadval":"0","name":"","x":460,"y":140,"wires":[["9965eebf.1b0e7"],[]]},{"id":"51b65564.9071ec","type":"inject","z":"c5aa92e5.22436","name":"","repeat":"","crontab":"","once":true,"onceDelay":"30","topic":"","payload":"Started!","payloadType":"str","x":100,"y":120,"wires":[["9965eebf.1b0e7","265f2ab6.1547a6"]]},{"id":"265f2ab6.1547a6","type":"api-current-state","z":"c5aa92e5.22436","name":"Adaptive Lighting Values - Main","server":"a54a6202.f4317","version":3,"outputs":2,"halt_if":"on","halt_if_type":"str","halt_if_compare":"is","entity_id":"switch.adaptive_lighting_main_white_lights","state_type":"str","blockInputOverrides":false,"outputProperties":[{"property":"payload","propertyType":"msg","value":"","valueType":"entityState"},{"property":"data","propertyType":"msg","value":"","valueType":"entity"}],"for":0,"forType":"num","forUnits":"minutes","x":170,"y":400,"wires":[["667530de.eb109","18f71a5e.ec9896"],[]]},{"id":"11aaeccd.75a6d3","type":"api-call-service","z":"c5aa92e5.22436","name":"Set Hall Brightness ","server":"a54a6202.f4317","version":5,"debugenabled":false,"domain":"isy994","service":"set_on_level","areaId":[],"deviceId":[],"entityId":["light.great_room_switch","light.hall_switch"],"data":"{\"value\":\"{{payload}}\"}","dataType":"json","mergeContext":"","mustacheAltTags":false,"outputProperties":[],"queue":"none","x":1010,"y":400,"wires":[[]]},{"id":"18f71a5e.ec9896","type":"stoptimer","z":"c5aa92e5.22436","duration":"5","units":"Minute","payloadtype":"num","payloadval":"0","name":"","x":460,"y":340,"wires":[["265f2ab6.1547a6"],[]]},{"id":"667530de.eb109","type":"function","z":"c5aa92e5.22436","name":"Brightness -> On_Level","func":"msg.payload = parseInt(msg.data.attributes.brightness_pct / 100 * 255)\nnode.status({ fill: 'green', shape: 'ring', text: 'Brightness ' +  msg.payload});\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":490,"y":400,"wires":[["19e6c0cf.afc35f","11aaeccd.75a6d3","57b76ece.99d3c","2e55e4a0.358d9c","5111b82b.d19e08","ae35f309.bc368"]]},{"id":"19e6c0cf.afc35f","type":"api-call-service","z":"c5aa92e5.22436","d":true,"name":"Set Great Room Table Lamp Brightness ","server":"a54a6202.f4317","version":5,"debugenabled":false,"domain":"isy994","service":"set_on_level","areaId":[],"deviceId":[],"entityId":["light.great_room_table_lamplinc"],"data":"{\"value\":\"{{payload}}\"}","dataType":"json","mergeContext":"","mustacheAltTags":false,"outputProperties":[],"queue":"none","x":1080,"y":460,"wires":[[]]},{"id":"853cb7f5.d9b398","type":"api-call-service","z":"c5aa92e5.22436","name":"Set Kitchen Brightness ","server":"a54a6202.f4317","version":5,"debugenabled":false,"domain":"isy994","service":"set_on_level","areaId":[],"deviceId":[],"entityId":["light.kitchen_light_switch_great_r","light.kitchen_light_switch_door"],"data":"{\"value\":\"{{payload}}\"}","dataType":"json","mergeContext":"","mustacheAltTags":false,"outputProperties":[],"queue":"none","x":1020,"y":520,"wires":[[]]},{"id":"3edd5f44.cfef","type":"function","z":"c5aa92e5.22436","name":"Brightness -> Int","func":"msg.payload = parseInt(msg.data.attributes.brightness_pct) - 1\nnode.status({ fill: 'green', shape: 'ring', text: 'Brightness ' +  msg.payload});\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":470,"y":200,"wires":[["6f4eb8a5f6b68429"]]},{"id":"23cf5331.39fd9c","type":"api-call-service","z":"c5aa92e5.22436","name":"Set Foyer Brightness ","server":"a54a6202.f4317","version":5,"debugenabled":false,"domain":"isy994","service":"set_on_level","areaId":[],"deviceId":[],"entityId":["light.foyer_light_switch"],"data":"{\"value\":\"{{payload}}\"}","dataType":"json","mergeContext":"","mustacheAltTags":false,"outputProperties":[],"queue":"none","x":1020,"y":580,"wires":[[]]},{"id":"c627d5b6.a586a8","type":"server-events","z":"c5aa92e5.22436","name":"ISY Control event","server":"a54a6202.f4317","version":2,"eventType":"isy994_control","exposeToHomeAssistant":false,"haConfig":[{"property":"name","value":""},{"property":"icon","value":""}],"waitForRunning":true,"outputProperties":[{"property":"payload","propertyType":"msg","value":"","valueType":"eventData"},{"property":"topic","propertyType":"msg","value":"$outputData(\"eventData\").event_type","valueType":"jsonata"},{"property":"event_type","propertyType":"msg","value":"$outputData(\"eventData\").event_type","valueType":"jsonata"}],"x":120,"y":800,"wires":[["790f6f3a.56278"]]},{"id":"790f6f3a.56278","type":"switch","z":"c5aa92e5.22436","name":"Hall, Foyer, Garage, or Kitchen Switch","property":"payload.entity_id","propertyType":"msg","rules":[{"t":"eq","v":"light.great_room_switch","vt":"str"},{"t":"eq","v":"light.hall_switch","vt":"str"},{"t":"eq","v":"light.foyer_light_switch","vt":"str"},{"t":"eq","v":"light.kitchen_light_switch_great_r","vt":"str"},{"t":"eq","v":"light.kitchen_light_switch_door","vt":"str"},{"t":"eq","v":"light.garage_lights","vt":"str"}],"checkall":"true","repair":false,"outputs":6,"x":410,"y":800,"wires":[["602685be.bc9aec"],["602685be.bc9aec"],["602685be.bc9aec"],["602685be.bc9aec"],["602685be.bc9aec"],["602685be.bc9aec"]]},{"id":"602685be.bc9aec","type":"switch","z":"c5aa92e5.22436","name":"Fast On/Off","property":"payload.event.control","propertyType":"msg","rules":[{"t":"eq","v":"DFON","vt":"str"},{"t":"eq","v":"DFOF","vt":"str"}],"checkall":"true","repair":false,"outputs":2,"x":690,"y":800,"wires":[["c2b70fb7.7b1c6"],["4eb16fd8.f2b7e"]]},{"id":"c2b70fb7.7b1c6","type":"api-call-service","z":"c5aa92e5.22436","name":"Disable Adaptive Lighting (Main)","server":"a54a6202.f4317","version":5,"debugenabled":false,"domain":"switch","service":"turn_off","areaId":[],"deviceId":[],"entityId":["switch.adaptive_lighting_lighting_main"],"data":"","dataType":"json","mergeContext":"","mustacheAltTags":false,"outputProperties":[],"queue":"none","x":950,"y":760,"wires":[[]]},{"id":"4eb16fd8.f2b7e","type":"api-call-service","z":"c5aa92e5.22436","name":"Enable Adaptive Lighting (Main)","server":"a54a6202.f4317","version":5,"debugenabled":false,"domain":"switch","service":"turn_on","areaId":[],"deviceId":[],"entityId":["switch.adaptive_lighting_lighting_main"],"data":"","dataType":"json","mergeContext":"","mustacheAltTags":false,"outputProperties":[],"queue":"none","x":950,"y":840,"wires":[[]]},{"id":"14fb26ce.7b7799","type":"debug","z":"c5aa92e5.22436","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","x":890,"y":60,"wires":[]},{"id":"1306ac77.eca914","type":"catch","z":"c5aa92e5.22436","name":"","scope":null,"uncaught":false,"x":700,"y":60,"wires":[["14fb26ce.7b7799"]]},{"id":"e68f337d.433fb","type":"comment","z":"c5aa92e5.22436","name":"Disable Adaptive Lighting with Fast On / Enable with Fast Off","info":"","x":260,"y":700,"wires":[]},{"id":"6e6dad18.bf5c24","type":"api-call-service","z":"c5aa92e5.22436","name":"Set Garage Brightness ","server":"a54a6202.f4317","version":5,"debugenabled":false,"domain":"isy994","service":"set_on_level","areaId":[],"deviceId":[],"entityId":["light.garage_lights"],"data":"{\"value\":\"{{payload}}\"}","dataType":"json","mergeContext":"","mustacheAltTags":false,"outputProperties":[],"queue":"none","x":1020,"y":640,"wires":[[]]},{"id":"57b76ece.99d3c","type":"function","z":"c5aa92e5.22436","name":"Garage min 35%","func":"if (msg.payload < 35) {\n    msg.payload = 35\n}\nnode.status({ fill: 'green', shape: 'ring', text: 'Brightness ' +  msg.payload});\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":770,"y":640,"wires":[["6e6dad18.bf5c24"]]},{"id":"2e55e4a0.358d9c","type":"function","z":"c5aa92e5.22436","name":"Kitchen min 35%","func":"if (msg.payload < 35) {\n    msg.payload = 35\n}\nnode.status({ fill: 'green', shape: 'ring', text: 'Brightness ' +  msg.payload});\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":770,"y":520,"wires":[["853cb7f5.d9b398"]]},{"id":"5111b82b.d19e08","type":"function","z":"c5aa92e5.22436","name":"Foyer min 30%","func":"if (msg.payload < 30) {\n    msg.payload = 30\n}\nnode.status({ fill: 'green', shape: 'ring', text: 'Brightness ' +  msg.payload});\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":760,"y":580,"wires":[["23cf5331.39fd9c"]]},{"id":"ae35f309.bc368","type":"api-call-service","z":"c5aa92e5.22436","name":"Set Piano Room Fan Brightness ","server":"a54a6202.f4317","version":5,"debugenabled":false,"domain":"isy994","service":"set_on_level","areaId":[],"deviceId":[],"entityId":["light.piano_room_fan_bulb_1","light.piano_room_fan_bulb_2","light.piano_room_fan_light"],"data":"{\"value\":\"{{payload}}\"}","dataType":"json","mergeContext":"","mustacheAltTags":false,"outputProperties":[],"queue":"none","x":1050,"y":340,"wires":[[]]},{"id":"6f4eb8a5f6b68429","type":"function","z":"c5aa92e5.22436","name":"Master Bath min 50%","func":"if (msg.payload < 50) {\n    msg.payload = 50\n}\nnode.status({ fill: 'green', shape: 'ring', text: 'Brightness ' +  msg.payload});\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":780,"y":220,"wires":[["8551efbb.d277f","cd33a3a2.42259"]]},{"id":"a54a6202.f4317","type":"server","name":"Home Assistant","version":5,"addon":true,"rejectUnauthorizedCerts":true,"ha_boolean":"y|yes|true|on|home|open","connectionDelay":true,"cacheJson":true,"heartbeat":false,"heartbeatInterval":30,"areaSelector":"friendlyName","deviceSelector":"friendlyName","entitySelector":"friendlyName","statusSeparator":"at: ","statusYear":"hidden","statusMonth":"short","statusDay":"numeric","statusHourCycle":"h23","statusTimeFormat":"h:m","enableGlobalContextStore":true}]
```


[SwiftASTContext] Split PerformAutoImport in two functions.

PerformAutoImport was, in fact, doing both auto import and
user import. The former is general and needed in several places
in the debugger. The latter is expression parser specific.
This splits the function in two, improving the API.
rdar://problem/30398933

@swift-ci please test and merge


Problem migrating fonts and sound

No matter what I try, it seems it doesn't want to copy over my fonts and sounds. Now I'm unsure if I'm doing something wrong or something's borked.
I have ticked all the things to migrate in settings, but after update to latest experimental those two folders have only the basic files, although the log states the files are copied over.
If you need more infos, let me know.

after update to latest experimental those two folders have only the basic files

This part makes me suspect that you are used to keeping custom soundpacks and fonts in data/sound/ and data/font/. Catapult tries not to mess with contents of data/, so it just uses sound/ and font/ in the game root instead. Those start out completely empty.
Here's my font setup as an example (old install done without a launcher):

Aah, I missed to adjust the fonts.json. Also, yes, I kept them in data/sound and data/font. After trasfering the files over, everything works like a charm!
Thanks for bumping me in the right direction and a big thanks for this wonderful launcher.
Cheers


ocamlPackages.qcheck: fix for OCaml ≥ 5.0

Description of changes
Quick fix waiting for a new release.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 224778 run on x86_64-linux 1

31 packages built:

acgtk
beluga
comby
coqPackages.coq-lsp
dune-release
easycrypt
flow
fstar
haxe (haxe_4_2)
haxePackages.format
haxePackages.heaps
haxePackages.hlopenal
haxePackages.hlsdl
hxcpp (haxePackages.hxcpp)
haxePackages.hxcs
haxePackages.hxjava
haxePackages.hxnodejs_4
haxe_4_0
haxe_4_1
jackline
jasmin-compiler
libbap
ligo
liquidsoap
python310Packages.bap
python310Packages.bap.dist
python311Packages.bap
python311Packages.bap.dist
satysfi
soupault
stog


Include required properties in --default-values-file-output

What this PR does / why we need it:
Include required properties in --default-values-file-output
Which issue(s) this PR fixes:

Fixes #
Does this PR introduce a user-facing change?

`--default-values-file-output` will also include required properties.

Additional Notes for your reviewer:
Review Checklist:

[ ] Follows the developer guidelines
[ ] Relevant tests are added or updated
[ ] Relevant docs in this repo added or updated
[ ] Relevant carvel.dev docs added or updated in a separate PR and there's
a link to that PR
[ ] Code is at least as readable and maintainable as it was before this
change

Additional documentation e.g., Proposal, usage docs, etc.:

Since this PR has a few refactors/improvements separated by commits I was wondering if it would be worth cleaning up some of the nomenclature in default_values.go

I have done the refactoring in the bash script only and tried to keep the changes in the other files to a minimal. I wanted to do more refactoring in default-values.go but I feel that a separate PR would make more sense?

I think I am fine with a separate PR for this stuff
Track this somewhere maybe?

Track this somewhere maybe?

I will be creating a new PR soon.


Refactoring FPN module to make more flexible

Description
Please include a summary of this pull request in English. If it closes an issue, please mention it here.
This PR is part of #376
We recommend to link at least one existing issue for PR. Before your create a PR, please check if there is an issue for this change.
Change(s)

Add SeparableConvLayer.
Add various options to FPN

upsample_interpolation: Determines interpolation method for upsample
lateral_conv_type: Convolution type which is used for building laterals. One of 'conv' or 'separable_conv'
num_lateral_conv: The number of lateral_conv layers.
fpn_conv_type: Convolution type which is applied after top-down feature mixing.
num_fpn_conv: The number of fpn_conv layers.
norm_type: Batch normalization type of FPN.
act_type: Activation type of FPN.

Code Formatting
If you PR to either master or dev branch, you should follow the code linting process. Please check your code with lint_check.sh in ./scripts directory.
For more information, please read the contribution guide in CONTRIBUTING.md.
Changelog
If your PR is granted to dev branch, codeowner will add a brief summary of the change to the Upcoming Release section of the CHANGELOG.md file including a link to the PR (formatted in markdown) and a link to your github profile.
For example,
- Added a new feature by `@myusername` in [PR 2023](https://github.com/Nota-NetsPresso/netspresso-trainer/pull/2023)

Change branch name, and all works about yolo-fastest will be done at that branch.


(GH-17) Fix typo in filename

Rename file to match function inside.
Fixes #17

@pauby, this looks like a no brainer to me but there's a conflict. Pretty sure a rebase will sort that out quick smart if you have a moment for that?

@Windos it looks like @pauby removed the branch from his fork 🤔
I've checked and it will rebase on master with no problems. So I guess the next steps going forward would be for pauby to recreate the branch on his fork, or for one of us to checkout the PR and push it to our fork and open a new PR. We can discuss this more next week and get this squared away.

@Windos it looks like @pauby removed the branch from his fork 🤔

... That explains why I was having all sorts of issues looking at this yesterday 😅
This'd be a trivial change to recreate in a new PR if required, would be good to get it in regardless of method.

@Windos @corbob to me, re-creating this PR is not necessary.
if this were me, I would be doing the following...
Check out the PR branch locally onto my machine:
gh pr checkout 18

NOTE: This assuming that you are using the GH CLI (If you aren't, you really should be 😄 ) choco install gh or brew install gh, pick your poison!
Rebase the PR:
git rebase master

This will bring the PR up to the head of the master branch, however, I am not sure if this is where it is meant to be.  In all likelihood, this PR should be targetting the develop branch, so then I would be doing the following:
git rebase --onto develop master

NOTE: The above assumes that you are still on the fix/filename-match-function branch.
From there, I would be merging the branch locally into the develop branch, and then pushing back to my upstream (gep13/ChocoCCM) and origin (chocolatey/ChocoCCM):
git checkout develop
git merge --no-ff fix/filename-match-function
git push upstream
git push origin

With all of that done, GitHub will be confused, so we can go ahead and close this PR, but the original person doing the contribution (in this case @pauby) will still be credited with the work, and everything will be updated accordingly.
Let me know if you have any questions about the above.

Thanks for getting this sorted @pauby
I've merged this into develop following @gep13's steps 😁


fix lambda example filepath

Resolves https://github.com/localstack/localstack/issues/6448

The issue does not comes from this, we can close it


Found error converting to Style-dictionary

Describe the bug
I got an error when I use tokens, that I upload to github.  and pull to editor.  build as SCSCC using style-dictionary.
To Reproduce
Steps to reproduce the behavior:

Upload tokens to github repo.
Pull repo to my project on visual studio.
setup config.js from style-dictionary
hit command on git-bash "style-dictionary build"

Expected behavior
my expectation it was no issue as default, when I generated using style-dictionary.
Screenshots or Screencasts
here is the generate result: get an error

here is config.js as default setting from style-dictionary

** another case without error.
I tested and export manual and uncheck global parent key on json.  no upload to github.

and no issue.
Question
is the issue from figma tokens JSON? or from style dictionary?
I follow step by step from style-dictionary without change the command parameter.  FYI.
Thanks,
Dei.

If you're syncing to a single file then you'll need to split your json file into individual sets before passing them into style dictionary.
You can do that in the plugin in Export or by using a script that just takes the first level keys and takes those contents into their own files.
Otherwise you'll have the set names as part of the file you pass into style dictionary, which expects a regular token file without set names.

I am not expert in coding, but I want to learn in practical how to use tokens and convert it. if you don't mind can you share the script and split it, please..  really apricate it.  thank you.

https://gist.github.com/six7/ddb9b1f0d0c6e434be4f1cdb8bfe56e1
Running this file splits a tokens.json dir into the 'tokens' directory, each set becoming a file in it.

Thanks!, it worked.

Awesome! Closing this 👍


Fix pinenty path on macOS

pinentry-mac installed via homebrew has the following path /opt/homebrew/bin/pinentry-mac
The current path used in the guide causes gpg to fail as no pin is captured
Version information:
Homebrew 3.2.12
Homebrew/homebrew-core (git revision 8bec984dd51; last commit 2021-09-15)
Homebrew/homebrew-cask (git revision a0676a5b41; last commit 2021-09-15)

pinentry-mac (pinentry) 1.1.1

Thanks for the PR!
I believe Homebrew uses a different path on Big Sur / M1 vs Catalina / Intel (not sure if it’s OS or hardware related).
I suggested an edit to your PR that should work on both.
Standby!

Good morning @jamescw,
Discovered that GnuPG does not expand variables in ~/.gnupg/gpg-agent.conf so I suggested a fix.
Can you please squash commits at your end (I don’t think it can be done at mine,  running following should work)?
Once squashed, I will merge PR. Btw, in the future, can you please submit PRs to the draft branch?
Thanks again for contributing to the privacy guides. 🙌
git reset --soft 97cdf45
git commit -m "Fix pinenty path on macOS"
git push -f

@sunknudsen thanks for the commits, I have done that and also changed the target to draft, over to you!


Does this work anymore? Nuxt 3

Cannot get a simple setup to work so having to use this workaround for now:
https://github.com/nuxt/nuxt/issues/13690#issuecomment-1397312009
My setup:
nuxt.config.js
export default defineNuxtConfig({
  	buildModules: ['@nuxtjs/style-resources',],

	styleResources: {
    	        scss: [
      		        '~assets/scss/_mixins.scss'
    	        ]
  	}
})

"@nuxtjs/style-resources": "^2.0.0",

Sorry, the README is wrong.
Nuxt 3 does not have buildModules.
Use the modules option instead.

@tibineagu
@nuxtjs/style-resources only supports webpack.
If you want to achieve the same thing with vite, use the following options
https://vitejs.dev/config/shared-options.html#css-preprocessoroptions

@wattanx thanks for the clarification. i implemented the preprocessorOptions and it works decently well.
Thank you!


Update Go to 1.21.5 and k8s.io/* to 0.29.1

This PR also incorporates #14 to fix broken APIs.

@empovit I believe that this PR is no longer required since #77 and #14 have been merged.

Fixed by #77 and #14


Please Halp

how to add the text edditor to imgui

You can see and example in https://github.com/BalazsJako/ColorTextEditorDemo


Revert "samples: net: lwm2m_client: Use Ethernet in QEMU Cortex-M3"

This reverts commit 8e3fc793d3bcb66ef347685bd4d610e04806a59b as it broke main (since the qemu_cortex_m3 excludes all tests with the net tag: https://github.com/zephyrproject-rtos/zephyr/actions/runs/3997309184/jobs/6858462310)
Signed-off-by: Henrik Brix Andersen<EMAIL_ADDRESS>

Does it have to revert all?
This app builds fine, but can we just drop those lines from "integration platforms"?

Does it have to revert all?
This app builds fine, but can we just drop those lines from "integration platforms"?

The exclude was put there in order to limit the number of platforms for running network tests in CI: de8d755c5403d7ac43bfd8c4c5860abb33c1a3a4

Does it have to revert all?
This app builds fine, but can we just drop those lines from "integration platforms"?

As main is broken right now, it is best to revert right away, and reapply after with whatever fixes.

Fix would be https://github.com/zephyrproject-rtos/zephyr/pull/54063

Merging, I'm usually all for fix forward but it looks like the conversation is still open, let's revert and revisit.


Support for case sensitive table names

Problem Statement
NB: this is separate from the existing tickets regarding schema names.
By default, Dataiku names tables combining upper and lower case labels resulting in mixed case names.
On CREATE TABLE CrateDB currently (5.3.0 snapshot from 2023/01/25) rejects mixed case names if the names are in quotes.
Possible Solutions

Support for case sensitive table names, for instance CREATE TABLE "Camelcase" (a int); should create a table called "Camelcase"

Considered Alternatives
No response

Relates to #12110.

Addressed by https://github.com/crate/crate/pull/13528, closing.


draft eoss recap blog

This PR adds our first blog, a brief recap of our CZI EOSS grant.
Pinging those mentioned by name for review:

@shoyer
@rabernat
@dcherian
@benbovy
@andersy005
@alexamici
@aurghs

Note the rendered version of the site in the Vercel bot comment.

🥳 Hooray for the first blog post....  Thank you all! 🎉


re-test the 3 models for demultiplexing using updated deeplexicon code (bug fixed)

Hi Luca, can you update the code to use the lates version found here? (deeplexicon.py)
The models haven't changed. Seems the issue was in the code, but this only became apparent in specific models that had larger images.  Can you pls update code and re-test the 3 models in the repo with the same test data (same as you did before)? Thanks again! Eva
https://github.com/Psy-Fer/deeplexicon

Done