text:
Error with importing Corner Pool

I tried to run these two lines to import the necessary modules for inference on Faster_RCNN_r50_FPN. I cloned the latest version of MMDetection for this. I am unable to import certain "ext" modules like corner_pool_ext. I'm new to this platform, so I would greatly appreciate any insight you have. Thank you!
from mmcv.runner import load_checkpoint
from mmdet.apis import inference_detector, show_result, init_detector

Environment
sys.platform: linux
Python: 3.6.9 (default, Apr 18 2020, 01:56:04) [GCC 8.4.0]
CUDA available: True
CUDA_HOME: /usr/local/cuda
NVCC: Cuda compilation tools, release 10.1, V10.1.243
GPU 0: Tesla K80
GCC: gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
PyTorch: 1.5.0+cu101
PyTorch compiling details: PyTorch built with:

GCC 7.3
C++ Version: 201402
Intel(R) Math Kernel Library Version 2019.0.5 Product Build 20190808 for Intel(R) 64 architecture applications
Intel(R) MKL-DNN v0.21.1 (Git Hash 7d2fd500bc78936d1d648ca713b901012f470dbc)
OpenMP 201511 (a.k.a. OpenMP 4.5)
NNPACK is enabled
CPU capability usage: AVX2
CUDA Runtime 10.1
NVCC architecture flags: -gencode;arch=compute_37,code=sm_37;-gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_61,code=sm_61;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_37,code=compute_37
CuDNN 7.6.3
Magma 2.5.2
Build settings: BLAS=MKL, BUILD_TYPE=Release, CXX_FLAGS= -Wno-deprecated -fvisibility-inlines-hidden -fopenmp -DNDEBUG -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DUSE_INTERNAL_THREADPOOL_IMPL -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-sign-compare -Wno-unused-parameter -Wno-unused-variable -Wno-unused-function -Wno-unused-result -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Wno-stringop-overflow, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, USE_CUDA=ON, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=ON, USE_MPI=OFF, USE_NCCL=ON, USE_NNPACK=ON, USE_OPENMP=ON, USE_STATIC_DISPATCH=OFF,

TorchVision: 0.6.0+cu101
OpenCV: 4.1.2
MMCV: 0.5.9
MMDetection: 2.1.0+8951a8a
MMDetection Compiler: GCC 7.5
MMDetection CUDA Compiler: 10.1
Error traceback
ImportError                               Traceback (most recent call last)
<ipython-input-6-24b0dc9ad91b> in <module>()
      1 from mmcv.runner import load_checkpoint
----> 2 from mmdet.apis import inference_detector, show_result, init_detector

8 frames
/content/mmdetection/mmdet/apis/__init__.py in <module>()
----> 1 from .inference import (async_inference_detector, inference_detector,
      2                         init_detector, show_result_pyplot)
      3 from .test import multi_gpu_test, single_gpu_test
      4 from .train import get_root_logger, set_random_seed, train_detector
      5

/content/mmdetection/mmdet/apis/inference.py in <module>()
      7 from mmcv.runner import load_checkpoint
      8
----> 9 from mmdet.core import get_classes
     10 from mmdet.datasets.pipelines import Compose
     11 from mmdet.models import build_detector

/content/mmdetection/mmdet/core/__init__.py in <module>()
      1 from .anchor import *  # noqa: F401, F403
----> 2 from .bbox import *  # noqa: F401, F403
      3 from .evaluation import *  # noqa: F401, F403
      4 from .fp16 import *  # noqa: F401, F403
      5 from .mask import *  # noqa: F401, F403

/content/mmdetection/mmdet/core/bbox/__init__.py in <module>()
      5                     TBLRBBoxCoder)
      6 from .iou_calculators import BboxOverlaps2D, bbox_overlaps
----> 7 from .samplers import (BaseSampler, CombinedSampler,
      8                        InstanceBalancedPosSampler, IoUBalancedNegSampler,
      9                        PseudoSampler, RandomSampler, SamplingResult)

/content/mmdetection/mmdet/core/bbox/samplers/__init__.py in <module>()
      7 from .random_sampler import RandomSampler
      8 from .sampling_result import SamplingResult
----> 9 from .score_hlr_sampler import ScoreHLRSampler
     10
     11 __all__ = [

/content/mmdetection/mmdet/core/bbox/samplers/score_hlr_sampler.py in <module>()
      1 import torch
      2
----> 3 from mmdet.ops import nms_match
      4 from ..builder import BBOX_SAMPLERS
      5 from ..transforms import bbox2roi

/content/mmdetection/mmdet/ops/__init__.py in <module>()
      1 from .context_block import ContextBlock
      2 from .conv_ws import ConvWS2d, conv_ws_2d
----> 3 from .corner_pool import CornerPool
      4 from .dcn import (DeformConv, DeformConvPack, DeformRoIPooling,
      5                   DeformRoIPoolingPack, ModulatedDeformConv,

/content/mmdetection/mmdet/ops/corner_pool/__init__.py in <module>()
----> 1 from .corner_pool import CornerPool
      2
      3 __all__ = ['CornerPool']

/content/mmdetection/mmdet/ops/corner_pool/corner_pool.py in <module>()
      2 from torch.autograd import Function
      3
----> 4 from . import corner_pool_ext
      5
      6

ImportError: cannot import name 'corner_pool_ext'

Did you compile and install it correctly?

Same question. I am trying to debug mmdetection on Linux CPU.
I first run /home/gt/Py36/bin/python3 setup.py install in the root directory.
Then I run tools/train.py in Pychram.

ImportError: cannot import name 'corner_pool_ext'

Hello, I want to know how you solved this problem 'ImportError: cannot import name 'corner_pool_ext'.

python setup.py develop

python3 setup.py develop

Thank you.I will try it.

authors: ShreyasKallingal guotong1988 hellock hyhyni


text:
The old API of register_module(module, force=False) is deprecated

I think I have updated mmdetection and mmcv to the latest version but the warning bellow still occurs. I don't know which function has triggered this warning.
The old API of register_module(module, force=False) is deprecated and will be removed, please use the new API register_module(name=None, force=False, module=None) instead.

Old API:
@xxx.register_module
class xxx:
    xxxx

New API:
@xxx.register_module()
class xxx:
    xxxx

This warning will not affect the results.

!python tools/train.py configs/cascade_rcnn_x101_32x4d_fpn_1x.py --resume-from work_dirs/cascade_rcnn_x101_32x4d_fpn_1x/epoch_12.pth
/usr/local/lib/python3.7/site-packages/mmcv/utils/registry.py:64: UserWarning: The old API of register_module(module, force=False) is deprecated and will be removed, please use the new API register_module(name=None, force=False, module=None) instead.

source: gharchive/issue

authors: hellock nidhi6553 strongwolf

repo: open-mmlab/mmdetection

license_type: permissive

license_source: github-api


text:
What's the function of legacy in pillar encoder ?

Hi, I want to know what's the function of legacy in https://github.com/open-mmlab/mmdetection3d/blob/master/mmdet3d/models/voxel_encoders/pillar_encoder.py#L116 ?
Legacy is set True in default, so we will run https://github.com/open-mmlab/mmdetection3d/blob/master/mmdet3d/models/voxel_encoders/pillar_encoder.py#L128:
              f_center = features[:, :, :3]
              f_center[:, :, 0] = f_center[:, :, 0] - (
                  coors[:, 3].type_as(features).unsqueeze(1) * self.vx +
                  self.x_offset)
              f_center[:, :, 1] = f_center[:, :, 1] - (
                  coors[:, 2].type_as(features).unsqueeze(1) * self.vy +
                  self.y_offset)
              f_center[:, :, 2] = f_center[:, :, 2] - (
                  coors[:, 1].type_as(features).unsqueeze(1) * self.vz +
                  self.z_offset)

Here, I find raw features[..., :3] has been changed and features[..., :3] == features[..., -3:], is there a bug ?
Looking forward to your reply.

        legacy (bool, optional): Whether to use the new behavior or             the original behavior. Defaults to True.
Turning on the legacy option actually violates the original paper implementation, because we do not want to make inplace operations while computing the center features. It is a little interesting that previous experiments seem to show that setting legacy to True can yield better performance, you can regard it as a training trick.

Thanks for your quick reply.
I'm still confused. As you mentioned above, inplace operations is an empirical trick to yield better performance.
However, it can cause data redundancy between the first 3 dimensions and the last 3 dimension in the encoded pillar features(10 dimensions), as shown in the following figure.

Here, I debuged an older mmdet3d, where the encoded pillar features are in 9 dimensions, and the first 2 dimensions and the last 2 dimension are the same.  Then, my questions are:

The raw point coordinate information (the first 2 or 3 dimensions) is lost and replaced with relative coordinate. Will it affect the features ?
Why don't you use features[:-2] or features[:-3] instead of features ?

I'm a beginner to 3d detection, and sorry to bother you.
Looking forward to your reply.

You can refer to https://github.com/open-mmlab/mmdetection3d/issues/1150 , maybe it would be helpful.


text:
border_align_forward miss in module _ext when run demo.py

Hi, after I installed mmdetection3d according to the getting_started.md. When I run the demo.py "python demo/pcd_demo.py demo/data/kitti/kitti_000008.bin configs/second/hv_second_secfpn_6x8_80e_kitti-3d-car.py checkpoints/hv_second_secfpn_6x8_80e_kitti-3d-car_20200620_230238-393f000c.pth --out-dir data/output_result/".
An error occured like:

Hi, @sherylwang
Have you installed and built mmcv, mmdet, mmdet3d successfully.
For checking, you can run python with your environment and running import mmcv, mmdet, mmdet3d.

mmdet3d

No error occured after running" import mmcv, mmdet, mmdet3d".

Hi, @sherylwang
Have you installed and built mmcv, mmdet, mmdet3d successfully.
For checking, you can run python with your environment and running import mmcv, mmdet, mmdet3d.

Thanks for reply. No error occured after running "import mmcv, mmdet, mmdet3d".

It's a strange problem. What's the version of mmcv, mmdet, mmseg, mmdet3d?

@sherylwang Try running python mmdet3d/utils/collect_env.py and put the log here? It will show your environment as well as package versions.

@sherylwang Try running python mmdet3d/utils/collect_env.py and put the log here? It will show your environment as well as package versions.

The same error occured. After I commented the 2 lines in "/opt/conda/lib/python3.7/site-packages/mmcv/utils/ext_loader.py ". The log looked like:
sys.platform: linux
Python: 3.7.7 (default, Mar 23 2020, 22:36:06) [GCC 7.3.0]
CUDA available: True
GPU 0,1,2,3,4,5,6,7: GeForce GTX 1080 Ti
CUDA_HOME: /usr/local/cuda
NVCC: Cuda compilation tools, release 10.2, V10.2.89
GCC: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.12) 5.4.0 20160609
PyTorch: 1.7.1
PyTorch compiling details: PyTorch built with:
  - GCC 7.3
  - C++ Version: 201402
  - Intel(R) Math Kernel Library Version 2020.0.0 Product Build 20191122 for Intel(R) 64 architecture applications
  - Intel(R) MKL-DNN v1.6.0 (Git Hash 5ef631a030a6f73131c77892041042805a06064f)
  - OpenMP 201511 (a.k.a. OpenMP 4.5)
  - NNPACK is enabled
  - CPU capability usage: AVX2
  - CUDA Runtime 10.2
  - NVCC architecture flags: -gencode;arch=compute_37,code=sm_37;-gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75
  - CuDNN 7.6.5
  - Magma 2.5.2
  - Build settings: BLAS=MKL, BUILD_TYPE=Release, CXX_FLAGS= -Wno-deprecated -fvisibility-inlines-hidden -DUSE_PTHREADPOOL -fopenmp -DNDEBUG -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DUSE_VULKAN_WRAPPER -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-sign-compare -Wno-unused-parameter -Wno-unused-variable -Wno-unused-function -Wno-unused-result -Wno-unused-local-typedefs -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-psabi -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Wno-stringop-overflow, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, USE_CUDA=ON, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=ON, USE_MPI=OFF, USE_NCCL=ON, USE_NNPACK=ON, USE_OPENMP=ON,

TorchVision: 0.8.2
OpenCV: 4.5.2
MMCV: 1.3.9
MMCV Compiler: GCC 5.4
MMCV CUDA Compiler: 10.2
MMDetection: 2.14.0
MMSegmentation: 0.14.1
MMDetection3D: 0.15.0+e58684a

According to the error message, it seems you didn't compile some custom ops in mmcv. Did you install mmcv or mmcv-full? The compilation command for mmcv-full should be MMCV_WITH_OPS=1 pip install -e ..

@sherylwang Any updates here? Do you still have the problem and we can discuss further about how to solve it? Or is it solved and I can close the issue?

Feel free to reopen this issue should you have any further questions :)

authors: Wuziyi616 sherylwang wHao-Wu


text:
Getting AssertionError when executing python3 -m pip install flask-socketio fastapi uvicorn datamodel_code_generator

Before proceeding, is there an existing issue or discussion for this?

[X] I have done a search for similar issues and discussions.

OS and version
22.04
Open-RMF installation type
Binaries
Other Open-RMF installation methods
https://github.com/open-rmf/rmf#binary-installation
Open-RMF version or commit hash
2.3.0
ROS distribution
Humble
ROS installation type
Binaries
Other ROS installation methods
No response
Package or library, if applicable
No response
Description of the bug
When executing python3 -m pip install flask-socketio fastapi uvicorn datamodel_code_generator in rmf setup section (https://github.com/open-rmf/rmf), the following error is received

Did I missed out anything?
Steps to reproduce the bug

Follow the instruction in rmf setup section (https://github.com/open-rmf/rmf)
execute python3 -m pip install flask-socketio fastapi uvicorn datamodel_code_generator
datamodel_code_generator will produce the error.

Expected behavior
No response
Actual behavior
No response
Additional information or screenshots
No response

Please refrain from posting screenshots of logs or errors, this makes it difficult to search or selectively copy any meaningful text for debugging, use https://gist.github.com/ instead in the future. As of now, we are unable to see error's entire output.
I believe the issue is that the package is called datamodel-code-generator, could you try python3 -m pip install flask-socketio fastapi uvicorn datamodel-code-generator instead?

Hi @aaronchongth, noted on the screenshot comment.
I have tried the command you suggested, the errors are still the same. The output is as follows
https://gist.github.com/Steven-NYP/b0d86383a9a2322d8cc44ce74ecc60c2

Hello @Steven-NYP! After some internal discussions we have decided that the proper fix is to remove datamodel_code_generator from the main installation instructions, as it is only used in dev. https://github.com/open-rmf/rmf/pull/375 removes it. You can proceed with the installation without it, python3 -m pip install flask-socketio fastapi uvicorn

@aaronchongth, thanks for the update. Installation is working now.

authors: Steven-NYP aaronchongth

repo: open-rmf/rmf


text:
fix: add package lock file and lock semi ver on a few packages

This is done because there was an issue with a dependency that
recently changed. The lock file is from a working version.
This is a temporary stop gap until we update gatsby and our deps
to later versions, which will result in a cleaner lock file and
a probable smaller footprint.

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:

source: gharchive/pull-request

authors: openrpc-bastion zcstarr

repo: open-rpc/generator


text:
Support more WinterCG-like runtimes (export actual fetch-like API)

I really love the functions, but they're quite limited. I understand a lot is for the sake of performance, but flexibility would be nice too.
For example, I'd love to create a static site adapter for Astro to use with open-runtime functions.
The issue is it's still a bit limited because the open-runtime export default async ({ req, res, log, error }) isn't "web standard". The req, res.send, res.json are not really standard. They're super stubbed-down versions.
Or what if I wanted to implement easy routing using a micro-backend framework like Elysia or Hono?
Scenario:

I want to create a code documentation website
I generate the static site with Astro
I use openruntime-adapter (WInterCG-compatible)
Serve static site files on a function-based runtime
Allow custom routes that even accept buffer, etc.

I don't think this is possible without a lot of tinkering with the current API.

In addition, the limit for formData should be customizable. I'd love for my users to upload things through functions.

repo: open-runtimes/open-runtimes

license: MIT


text:
Bug: Repository page throws a hydration error on smaller screens

here's some hydration errors with smaller screens sizes.

This seems to be causing some of the flakiness in E2E tests also. Looking into it as part of #3946

authors: brandonroberts nickytonline

repo: open-sauced/app


text:
[BUG] 刚升级新版本，出现了插件打开异常的情况

今天刚更新了插件，结果自己打开插件半天没有在底部状态栏显示出复习的卡片，我重启插件多次，还是一样的现象。
在更新前，插件并没有开启，而且不同的是数据是从远程过来的，这意味着这太机器的数据和新的，所有新的数据和新版本造成了插件不能用了？
下面是报错
Uncaught (in promise) TypeError: Cannot read properties of null (reading 'setTracked')
    at _ItemToDecks.toRevDeck (plugin:obsidian-spaced-repetition-recall:28950:12)
    at eval (plugin:obsidian-spaced-repetition-recall:28930:22)
    at Array.forEach (<anonymous>)
    at _ItemToDecks.itemToReviewDecks (plugin:obsidian-spaced-repetition-recall:28900:11)
    at _SRPlugin.sync_trackfiles (plugin:obsidian-spaced-repetition-recall:29528:44)
    at async _SRPlugin.sync (plugin:obsidian-spaced-repetition-recall:29423:7)
    at async Object.callback (plugin:obsidian-spaced-repetition-recall:29278:11)

main.zip
应该是以前数据包含null项导致的，试下这版，解压替换

我重启 ob 就可以开启卡片复习了，我试试你的新的。

替换后没报错了，但是我看文件的大小相比多了1 m多。。


text:
Update nock to v13 and use "delayConnection" instead of socketDelay

Nock in version 13 removed socketDelay in favour of delayConnection. So to upgrade to v13 we have to change some unit tests.
More details here:
https://github.com/open-telemetry/opentelemetry-js/pull/1298

Please, assign this issue to me. I will submit the pull request before the end of the next week.

Hi, is this still up for grabs? If so, could I pick this up?

@eunice98k yes it is still valid, I'm assigning this to you, thank you

I am sorry. I have been quite busy these months.
Let me update the issue today before the end of the day (UTC) to clarify why it is blocked.

I am sorry. I have been quite busy these months.
Let me update the issue today before the end of the day (UTC) to clarify why it is blocked.

Sounds good! Thank you.

My progress is available in this (very outdated) pull request: #1504. As its description says, the major release changed the expected behavior and some tests can no longer be reproduced.
To simulate several specific scenarios, I had to replace some setup blocks that were using nock with custom http servers. I was close to fixing them all when I ran into a bug in the code itself (not the tests).
I do not remember the cases properly, but they were related to the aborted event on request object and some specific versions of Node.js. In those days, the project was still using Circle CI and I had some problems that did not allow me to take a look at the errors.
I remember it as a tricky good-first-issue despite it seems very trivial at first sight. Fortunately, the project has evolved a lot since then. Anyway, I will have free time this month, so feel free to ping me in case you need something else :hugs:

This is super helpful. Thank you!
Will get working on it and ping you if I have any questions 😁

Can I pick this up?

@cole-easton Do you know if @eunice98k is still working on this ? If not i don't see any issue

Hi, I can take over this issue @alolita

@dyladan should this be closed due to being fixed by https://github.com/open-telemetry/opentelemetry-js/pull/2652?

Fixed by #2652

authors: cole-easton eunice98k legendecas obecny rltoSD sergioregueira spencerwilson vmarchaud

repo: open-telemetry/opentelemetry-js


text:
Typescript compatiblitly

[x] This only affects the JavaScript OpenTelemetry library
[ ] This may affect other libraries, but I would like to get opinions here first

Followup on https://github.com/open-telemetry/opentelemetry-js-contrib/pull/549#discussion_r664733898
Currently we use the latest version of typescript in our CI setup and we also use the latest features like override keyword. Besides such "visible" features like override there are also more hidden features like better type deduction,... which would result in problems if people try to use an older version.
If someone would like to consume the raw TS files the same, new typescript version is needed which if often challenging.
As of now it should be no problem for consumers of transpiled packages but I'm not sure if there is a gurantee from TS side regarding this compatiblity.
@MSNev indicates that they would prefer a more conservative approach regarding this.
I think this is a valid point to consider. But if we decide to go this way I think following points should be done:

sync API, core and contrib repo regarding the version used
use this older typescript version in CI to ensure no new feature is used
clearly document this decission
specify a timeframe for updating typescript to avoid we stick on an ancient version forever
specify if moving to a newer typescript version is semver major or minor

I'd believe we can set up alternative CI for the latest and older typescript versions for 1. testing generated d.ts compatibility, 2. source code compatibility. (1) should be the most common one since most consumers depend on the published d.ts files. (2) might not be that popular option since we didn't publish the ts source files anyway.
As TypeScript generally releases every 3 months, I'd believe supporting the latest 2-4 versions should cover 6 months of upgrading period. For above (1) and (2), I suppose we can apply different rules for them:
(This is just a possible solution)

for generated d.ts consumers, we guarantee 3 versions / 6 months (latest+2 versions) of typescript support,
for source code consumers, we guarantee 2 versions / 3 months (latest+1 versions) of typescript support.

For version bumping, https://github.com/open-telemetry/opentelemetry-js-api/issues/153 our cadence of release should be considered. I don't see another major version bump will happen in the near future, but we have to let go of the older typescript versions.

TypeScript supports specifying different .d.ts files for different versions: https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html#version-selection-with-typesversions
downlevel-dts rewrites .d.ts files created by any version of TypeScript so that they work with TypeScript 3.4 or later. This package is used by typescript-eslint, for example.

Closed in favor of #4870

authors: Flarna Ugzuzg dyladan legendecas


text:
docs(instrumentation): update links in the Readme

Signed-off-by: Olivier Albertini olivier.albertini@montreal.ca
Short description of the changes
plugins have been moved to a new experimental folder and links are broken.
Checklist:

[x] Followed the style guidelines of this project
[ ] Unit tests have been added
[x] Documentation has been updated

@OlivierAlbertini I don't have permission to update your branch but this is mergeable IMO

This can be merged when the branch is up to date

authors: OlivierAlbertini dyladan


text:
chore(deps): replace semver with compare-versions to reduce bundle size

Which problem is this PR solving?
Semver makes up 1/4 of the output of our bundled opentelemetry distribution whilst not providing much utility.
In aws-lambda environments, this contributes significantly to the coldstart (about 30ms)

Fixes # (issue)
https://github.com/open-telemetry/opentelemetry-js/issues/3537
Short description of the changes
replaces semver with compare-versions in

instrumentation-http
instrumentation
sdk-base-node

The API should be comparable and behaviour should be very similar.
With the changes in instrumentation, the prerelease flag is no longer needed because this is a default of the satisfies method is not broken by prerelease tags
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A

Checklist:

[x] Followed the style guidelines of this project
[x] Unit tests have been added
[x] Documentation has been updated

Also any advice on the best ways to test this, I have sanity-checked the compare-versions methods and confirmed they behave the same way as semver. The unit tests pass (also helped catch a bug :partying_face:) anything else needed?


text:
Emit Honeycomb API marker events using this library

Is it possible to relay these types of events: https://docs.honeycomb.io/api/markers/ through otel+otlp ... that is to say, is there an otel equivalent for honeycomb "markers"?

I think that's a question for Honeycomb. This might be relevant: https://www.honeycomb.io/blog/uniting-tracing-logs-open-telemetry-span-events/. I don't know whether Span Events would map to Markers. If so, you'd use span.add_event(...).

I'd propose closing this issue until a time that the OpenTelemetry spec includes a concept equivalent to a Honeycomb Marker. I think until it is in the spec, Markers-or-whatever-they-are-named are out of scope for this API/SDK.

ok thanks @robbkidd / @arielvalentin / @fbogsany  ... I will keep my eye on the specification, you are correct in that it would not be proper just yet to include any vendor specific features into the library before they were standardized.

authors: diclophis fbogsany robbkidd

repo: open-telemetry/opentelemetry-ruby

license_source: bigquery


text:
[CI] Some commits (force push, update with main?) trigger wrong reviewer requests & labelling

I saw this happening a few times now, but I am not 100% sure how this happens, and we need to investigate:
if a contributor updates their PR with the latest main (force push for example), sometimes the actions for labelling and requesting reviews get triggered in a way that they request reviews and add labels across all files that have been part of that rebase. I am not 100% sure how to address that, but I wanted to record it as a bug.
Example: https://github.com/open-telemetry/opentelemetry.io/pull/5575

Run examples:
https://github.com/open-telemetry/opentelemetry.io/actions/runs/11949606337/job/33309393503?pr=5575
Related bug in the labeler action:
https://github.com/actions/labeler/issues/784

We might want to restrict the action types in the workflow files, e.g. exclude synchronize ("A pull request's head branch was updated. For example, the head branch was updated from the base branch or new commits were pushed to the head branch."), via https://docs.github.com/en/webhooks/webhook-events-and-payloads?actionType=synchronize#pull_request

By default, a workflow only runs when a pull_request_target event's activity type is opened, synchronize, or reopened.

So we should change that to opened and reopened


text:
how to use spring RestTemplate, RestClient, WebClient

Depends https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/11038

@jeanbisutti please check again

@jeanbisutti please check again

LGTM Thanks!

/fix:all

authors: jeanbisutti svrnm zeitlinger


text:
fix issues in languages index

https://github.com/open-telemetry/opentelemetry.io/pull/5204 introduced 2 wrong links

/fix:all

I only see one link changed?

Yes. Another one was fixed by a different PR and I merged the changes


text:
Add spec version in as part of generated SDK

Maybe something like this:
import snappi
api = snappi.api()

api.info()
# output
{
    "title": "Open Traffic Generator API",
    "version": "0.4.5",
    "url": "https://github.com/open-traffic-generator/models",
    "license": "https://opensource.org/licenses/MIT"
}

Fixed with https://github.com/open-traffic-generator/openapiart/issues/389

repo: open-traffic-generator/openapiart


text:
Not able to collect docker logs for OTG-HW

This is continuation of this PR  https://github.com/open-traffic-generator/fp-testbed-nokia/pull/17 though I feel that fix will regress current intention of this script which is to pull logs for all three dockes.
So, I am proposing this fix.

close this PR as open it in another repo https://github.com/open-traffic-generator/fp-testbed-template/pull/8

repo: open-traffic-generator/otg-examples


text:
Expose watch-debounce field to config?

I see there's an internal --watch-debounce internal config field, defaults to 100ms, but this value is not configurable by users.
Can we make this value configurable?
I'm seeing an issue with many of my projects where I save a single .ts file, and web dev server in watch mode restarts multiple times. Investigating the issue, the problem comes down to Typescript takes longer than 100ms between changes when writing the source map files, resulting in multiple reloads:

In the above screenshot, notice there is a > 100ms delay between the change of index.html and the change of pwabuilder-sw.js.map.
If I could control the watch debounce time, it would make my edit->debug->test cycle much smoother.
Would you accept a pull request enabling this?

in @web/dev-server which is the successor of es-dev-server it's a small plugin you could "fork" in your config and change to whatever logic/value you need
https://github.com/modernweb-dev/web/blob/master/packages/dev-server/src/plugins/watchPlugin.ts
PS: es-dev-server will likely not get any feature releases so it's probably best to move to @web/dev-server if possible

authors: JudahGabriel daKmoR

repo: open-wc/es-dev-server


text:
[karma-esm] Monorepo typescript decorators not working

Hello guys! I am having a problem using karma-esm. when running es-dev-server everything works properly but when running tests with karma-esm I get an error.
Am I making a mistake?
I have this folders structure:
.
├── .config
│   └── babel
│       ├── .components
│       └── .root
├── components
│   └── base
│       ├── .babelrc -> ../../.config/babel/.components
│       ├── MnvBase.spec.ts
│       ├── MnvBase.stories.ts
│       ├── MnvBase.ts
│       ├── index.html
│       ├── package.json
│       └── src
│           ├── index.ts
│           └── styles.ts
├── .babelrc -> .config/babel/.root
├── karma.conf.js
├── karma.conf.ts
├── lerna.json
└── package.json

".babelrc" file in root:
{
    "plugins": [
      [
        "@babel/plugin-proposal-decorators",
        {
          "legacy": true
        }
      ],
      [
        "@babel/plugin-proposal-class-properties",
        {
          "loose": true
        }
      ]
    ],
    "presets": [
      "@babel/preset-typescript"
    ]
}

".babelrc" file in component:
{ "extends": "../../.babelrc" }

karma.conf.js:
require('ts-node').register({
   compilerOptions: {
      module: 'commonjs',
   },
})
require('./karma.conf.ts')

karma.conf.ts:
import { createDefaultConfig } from '@open-wc/testing-karma'
import merge from 'deepmerge'

export default config => {
   config.set(
      merge(createDefaultConfig(config), {
         files: [
            { pattern: 'components/**/*.spec.ts', type: 'module' },
            { pattern: 'components/**/*.test.ts', type: 'module' },
         ],
         exclude: ['**/@ufrj/**', './.config/**'],
         esm: {
            babel: true,
            nodeResolve: true,
            fileExtensions: ['.ts'],
         },
      })
   )
   return config
}

package.json in root:
...
"devDependencies": {
    "@babel/core": "^7.5.5",
    "@babel/plugin-proposal-class-properties": "^7.5.5",
    "@babel/plugin-proposal-decorators": "^7.4.4",
    "@babel/preset-typescript": "^7.3.3",
    "@open-wc/testing": "^2.3.2",
    "@open-wc/testing-karma": "^3.1.26",
    ...
},
...

Output:
$ npx karma start ./karma.conf.ts --log-level debug
25 08 2019 20:09:06.120:DEBUG [config]: Loading config /Users/vcarvalho/dev/mnv/karma.conf.ts
25 08 2019 20:09:06.126:DEBUG [karma-server]: Final config Config {
  LOG_DISABLE: 'OFF',
  LOG_ERROR: 'ERROR',
  LOG_WARN: 'WARN',
  LOG_INFO: 'INFO',
  LOG_DEBUG: 'DEBUG',
  frameworks: [
    'esm',
    'mocha',
    'snapshot',
    'mocha-snapshot',
    'source-map-support'
  ],
  protocol: 'http:',
  port: 9876,
  listenAddress: '0.0.0.0',
  hostname: 'localhost',
  httpsServerConfig: {},
  basePath: '/Users/vcarvalho/dev/mnv',
  files: [
    Pattern {
      pattern: '/Users/vcarvalho/dev/mnv/__snapshots__/**/*.md',
      served: true,
      included: true,
      watched: true,
      nocache: false,
      weight: [ 1, 1, 1, 0, 0, 0 ],
      type: undefined
    },
    Pattern {
      pattern: '/Users/vcarvalho/dev/mnv/node_modules/axe-core/axe.min.js',
      served: true,
      included: true,
      watched: true,
      nocache: false,
      weight: [ 1, 0, 0, 0, 0, 0 ],
      type: undefined
    },
    Pattern {
      pattern: '/Users/vcarvalho/dev/mnv/components/**/*.spec.ts',
      served: true,
      included: true,
      watched: true,
      nocache: false,
      weight: [ 1, 1, 1, 0, 0, 0 ],
      type: 'module'
    },
    Pattern {
      pattern: '/Users/vcarvalho/dev/mnv/components/**/*.test.ts',
      served: true,
      included: true,
      watched: true,
      nocache: false,
      weight: [ 1, 1, 1, 0, 0, 0 ],
      type: 'module'
    }
  ],
  browserConsoleLogOptions: { level: 'debug', format: '%b %T: %m', terminal: true },
  customContextFile: null,
  customDebugFile: null,
  customClientContextFile: null,
  exclude: [
    '/Users/vcarvalho/dev/mnv/**/@ufrj/**',
    '/Users/vcarvalho/dev/mnv/.config/**',
    '/Users/vcarvalho/dev/mnv/karma.conf.ts'
  ],
  logLevel: 'DEBUG',
  colors: true,
  autoWatch: false,
  autoWatchBatchDelay: 250,
  restartOnFileChange: true,
  usePolling: false,
  reporters: [ 'mocha' ],
  singleRun: true,
  browsers: [ 'ChromeHeadlessNoSandbox' ],
  captureTimeout: 60000,
  proxies: {},
  proxyValidateSSL: true,
  preprocessors: [Object: null prototype] {
    '/Users/vcarvalho/dev/mnv/**/__snapshots__/**/*.md': [ 'snapshot', 'snapshot-filename' ]
  },
  urlRoot: '/',
  upstreamProxy: undefined,
  reportSlowerThan: 0,
  loggers: [
    {
      type: 'console',
      layout: { type: 'pattern', pattern: '%[%d{DATE}:%p [%c]: %]%m' }
    }
  ],
  transports: [ 'polling', 'websocket' ],
  forceJSONP: false,
  plugins: [
    '/Users/vcarvalho/dev/mnv/node_modules/@open-wc/karma-esm/karma-esm.js',
    '/Users/vcarvalho/dev/mnv/node_modules/karma-mocha/lib/index.js',
    '/Users/vcarvalho/dev/mnv/node_modules/karma-mocha-reporter/index.js',
    '/Users/vcarvalho/dev/mnv/node_modules/karma-source-map-support/lib/index.js',
    '/Users/vcarvalho/dev/mnv/node_modules/karma-coverage-istanbul-reporter/src/reporter.js',
    '/Users/vcarvalho/dev/mnv/node_modules/karma-snapshot/lib/index.js',
    '/Users/vcarvalho/dev/mnv/node_modules/karma-mocha-snapshot/lib/index.js',
    '/Users/vcarvalho/dev/mnv/node_modules/karma-chrome-launcher/index.js',
    '/Users/vcarvalho/dev/mnv/node_modules/@open-wc/testing-karma/src/snapshot-filename-preprocessor.js',
    'karma-*',
    [Object: null prototype] {
      'launcher:ChromeHeadlessNoSandbox': [ 'factory', [Function] ]
    }
  ],
  client: {
    args: [],
    useIframe: true,
    runInParent: false,
    captureConsole: true,
    clearContext: true,
    mocha: { reporter: 'html' }
  },
  defaultClient: {
    args: [],
    useIframe: true,
    runInParent: false,
    captureConsole: true,
    clearContext: true,
    mocha: { reporter: 'html' }
  },
  browserDisconnectTimeout: 2000,
  browserDisconnectTolerance: 0,
  browserNoActivityTimeout: 30000,
  processKillTimeout: 2000,
  concurrency: Infinity,
  failOnEmptyTestSuite: true,
  retryLimit: 2,
  detached: false,
  crossOriginAttribute: true,
  browserSocketTimeout: 20000,
  cmd: 'start',
  configFile: '/Users/vcarvalho/dev/mnv/karma.conf.ts',
  customLaunchers: {
    ChromeHeadlessNoSandbox: {
      base: 'ChromeHeadless',
      flags: [ '--no-sandbox', '--disable-setuid-sandbox' ]
    }
  },
  esm: {
    coverage: undefined,
    compatibility: 'none',
    babelModernExclude: [
      '**/node_modules/sinon/**/*',
      '**/node_modules/mocha/**/*',
      '**/node_modules/chai/**/*',
      '**/node_modules/sinon/chai/**/*'
    ],
    polyfills: { webcomponents: true, fetch: true },
    exclude: [ '**/__snapshots__/**/*' ],
    babel: true,
    nodeResolve: true,
    fileExtensions: [ '.ts' ]
  },
  mochaReporter: { showDiff: true },
  coverageIstanbulReporter: {
    reports: [ 'html', 'lcovonly', 'text-summary' ],
    dir: 'coverage',
    combineBrowserReports: true,
    skipFilesWithNoCoverage: false,
    thresholds: {
      global: { statements: 80, branches: 80, functions: 80, lines: 80 }
    }
  },
  snapshot: {
    update: undefined,
    prune: undefined,
    limitUnusedSnapshotsInWarning: -1,
    pathResolver: [Function: pathResolver]
  }
}
25 08 2019 20:09:06.131:DEBUG [plugin]: Loading plugin /Users/vcarvalho/dev/mnv/node_modules/@open-wc/karma-esm/karma-esm.js.
25 08 2019 20:09:06.362:DEBUG [plugin]: Loading plugin /Users/vcarvalho/dev/mnv/node_modules/karma-mocha/lib/index.js.
25 08 2019 20:09:06.363:DEBUG [plugin]: Loading plugin /Users/vcarvalho/dev/mnv/node_modules/karma-mocha-reporter/index.js.
25 08 2019 20:09:06.371:DEBUG [plugin]: Loading plugin /Users/vcarvalho/dev/mnv/node_modules/karma-source-map-support/lib/index.js.
25 08 2019 20:09:06.372:DEBUG [plugin]: Loading plugin /Users/vcarvalho/dev/mnv/node_modules/karma-coverage-istanbul-reporter/src/reporter.js.
25 08 2019 20:09:06.507:DEBUG [plugin]: Loading plugin /Users/vcarvalho/dev/mnv/node_modules/karma-snapshot/lib/index.js.
25 08 2019 20:09:06.527:DEBUG [plugin]: Loading plugin /Users/vcarvalho/dev/mnv/node_modules/karma-mocha-snapshot/lib/index.js.
25 08 2019 20:09:06.528:DEBUG [plugin]: Loading plugin /Users/vcarvalho/dev/mnv/node_modules/karma-chrome-launcher/index.js.
25 08 2019 20:09:06.531:DEBUG [plugin]: Loading plugin /Users/vcarvalho/dev/mnv/node_modules/@open-wc/testing-karma/src/snapshot-filename-preprocessor.js.
25 08 2019 20:09:06.531:DEBUG [plugin]: Loading karma-* from /Users/vcarvalho/dev/mnv/node_modules
25 08 2019 20:09:06.533:DEBUG [plugin]: Loading plugin /Users/vcarvalho/dev/mnv/node_modules/karma-chrome-launcher.
25 08 2019 20:09:06.533:DEBUG [plugin]: Loading plugin /Users/vcarvalho/dev/mnv/node_modules/karma-coverage-istanbul-reporter.
25 08 2019 20:09:06.533:DEBUG [plugin]: Loading plugin /Users/vcarvalho/dev/mnv/node_modules/karma-mocha.
25 08 2019 20:09:06.533:DEBUG [plugin]: Loading plugin /Users/vcarvalho/dev/mnv/node_modules/karma-mocha-reporter.
25 08 2019 20:09:06.534:DEBUG [plugin]: Loading plugin /Users/vcarvalho/dev/mnv/node_modules/karma-mocha-snapshot.
25 08 2019 20:09:06.534:DEBUG [plugin]: Loading plugin /Users/vcarvalho/dev/mnv/node_modules/karma-snapshot.
25 08 2019 20:09:06.534:DEBUG [plugin]: Loading plugin /Users/vcarvalho/dev/mnv/node_modules/karma-source-map-support.
25 08 2019 20:09:06.534:DEBUG [plugin]: Loading plugin /Users/vcarvalho/dev/mnv/node_modules/karma-sourcemap-loader.
25 08 2019 20:09:06.534:DEBUG [plugin]: Loading inlined plugin (defining launcher:ChromeHeadlessNoSandbox).
25 08 2019 20:09:06.550:DEBUG [web-server]: Instantiating middleware
25 08 2019 20:09:06.552:DEBUG [reporter]: Trying to load reporter: mocha
25 08 2019 20:09:06.579:DEBUG [reporter]: Trying to load color-version of reporter: mocha (mocha_color)
25 08 2019 20:09:06.579:DEBUG [reporter]: Couldn't load color-version.

START:
25 08 2019 20:09:06.615:DEBUG [filelist]: Excluded file "/Users/vcarvalho/dev/mnv/components/base/node_modules/@ufrj/mnv-utils/MnvUtils.spec.ts"
25 08 2019 20:09:06.615:DEBUG [filelist]: Excluded file "/Users/vcarvalho/dev/mnv/components/titles/node_modules/@ufrj/mnv-base/MnvBase.spec.ts"
25 08 2019 20:09:06.615:DEBUG [filelist]: Excluded file "/Users/vcarvalho/dev/mnv/components/titles/node_modules/@ufrj/mnv-base/node_modules/@ufrj/mnv-utils/MnvUtils.spec.ts"
25 08 2019 20:09:06.621:WARN [filelist]: Pattern "/Users/vcarvalho/dev/mnv/__snapshots__/**/*.md" does not match any file.
25 08 2019 20:09:06.621:WARN [filelist]: Pattern "/Users/vcarvalho/dev/mnv/components/**/*.test.ts" does not match any file.
25 08 2019 20:09:06.629:INFO [karma-server]: Karma v4.2.0 server started at http://0.0.0.0:9876/
25 08 2019 20:09:06.630:INFO [launcher]: Launching browsers ChromeHeadlessNoSandbox with concurrency unlimited
25 08 2019 20:09:06.633:INFO [launcher]: Starting browser ChromeHeadless
25 08 2019 20:09:06.633:DEBUG [launcher]: null -> BEING_CAPTURED
25 08 2019 20:09:06.633:DEBUG [temp-dir]: Creating temp dir at /var/folders/st/1v9r0sf5015cthwt58lgmcd00000gn/T/karma-89714435
25 08 2019 20:09:06.634:DEBUG [launcher]: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome --user-data-dir=/var/folders/st/1v9r0sf5015cthwt58lgmcd00000gn/T/karma-89714435 --no-default-browser-check --no-first-run --disable-default-apps --disable-popup-blocking --disable-translate --disable-background-timer-throttling --disable-renderer-backgrounding --disable-device-discovery-notifications --no-sandbox --disable-setuid-sandbox http://localhost:9876/?id=89714435 --headless --disable-gpu --remote-debugging-port=9222
25 08 2019 20:09:06.777:DEBUG [web-server]: serving: /Users/vcarvalho/dev/mnv/node_modules/karma/static/client.html
25 08 2019 20:09:06.822:DEBUG [web-server]: serving: /Users/vcarvalho/dev/mnv/node_modules/karma/static/karma.js
25 08 2019 20:09:06.921:DEBUG [karma-server]: A browser has connected on socket -0VpZA-Or9dUiGHLAAAA
25 08 2019 20:09:06.924:DEBUG [web-server]: upgrade /socket.io/?EIO=3&transport=websocket&sid=-0VpZA-Or9dUiGHLAAAA
25 08 2019 20:09:06.940:DEBUG [HeadlessChrome 76.0.3809 (Mac OS X 10.13.6)]: undefined -> CONNECTED
25 08 2019 20:09:06.940:INFO [HeadlessChrome 76.0.3809 (Mac OS X 10.13.6)]: Connected on socket -0VpZA-Or9dUiGHLAAAA with id 89714435
25 08 2019 20:09:06.941:DEBUG [launcher]: BEING_CAPTURED -> CAPTURED
25 08 2019 20:09:06.941:DEBUG [launcher]: ChromeHeadless (id 89714435) captured in 0.311 secs
25 08 2019 20:09:06.941:DEBUG [HeadlessChrome 76.0.3809 (Mac OS X 10.13.6)]: CONNECTED -> CONFIGURING
25 08 2019 20:09:06.946:DEBUG [middleware:karma]: custom files /Users/vcarvalho/dev/mnv/node_modules/@open-wc/karma-esm/src/esm-context.html /Users/vcarvalho/dev/mnv/node_modules/@open-wc/karma-esm/src/esm-debug.html null
25 08 2019 20:09:06.946:DEBUG [middleware:karma]: Serving customContextFile /Users/vcarvalho/dev/mnv/node_modules/@open-wc/karma-esm/src/esm-context.html
25 08 2019 20:09:06.947:DEBUG [web-server]: serving: /Users/vcarvalho/dev/mnv/node_modules/@open-wc/karma-esm/src/esm-context.html
25 08 2019 20:09:06.954:DEBUG [web-server]: serving: /Users/vcarvalho/dev/mnv/node_modules/karma/static/context.js

Error compiling: /components/titles/src/index.ts: Support for the experimental syntax 'decorators-legacy' isn't currently enabled (14:4):

  12 |
  13 | export class MnvTitles extends LitElement {
> 14 |    @property({ type: Number }) level = 1
     |    ^
  15 |
  16 |    static get styles() {
  17 |       return stylesComponent
HeadlessChrome 76.0.3809 (Mac OS X 10.13.6) ERROR: 'failed to load element http://localhost:9876/base/components/titles/MnvTitles.spec.ts?8525a94f12f0c41695288ebc485408b90ce0d30a'
25 08 2019 20:09:09.149:DEBUG [HeadlessChrome 76.0.3809 (Mac OS X 10.13.6)]: CONFIGURING -> EXECUTING
  mnv-base
    ✔ works
25 08 2019 20:09:09.160:DEBUG [HeadlessChrome 76.0.3809 (Mac OS X 10.13.6)]: EXECUTING -> CONNECTED
25 08 2019 20:09:09.161:DEBUG [launcher]: CAPTURED -> BEING_KILLED
25 08 2019 20:09:09.162:DEBUG [launcher]: BEING_KILLED -> BEING_FORCE_KILLED

Finished in 0.011 secs / 0.002 secs @ 20:09:09 GMT-0300 (Brasilia Standard Time)

SUMMARY:
✔ 1 test completed
25 08 2019 20:09:09.163:DEBUG [karma-server]: Run complete, exiting.
25 08 2019 20:09:09.163:DEBUG [launcher]: Disconnecting all browsers
25 08 2019 20:09:09.163:DEBUG [launcher]: BEING_FORCE_KILLED -> BEING_FORCE_KILLED
25 08 2019 20:09:09.169:DEBUG [launcher]: Process ChromeHeadless exited with code null and signal SIGTERM
25 08 2019 20:09:09.170:DEBUG [temp-dir]: Cleaning temp dir /var/folders/st/1v9r0sf5015cthwt58lgmcd00000gn/T/karma-89714435
25 08 2019 20:09:09.195:DEBUG [launcher]: Finished all browsers
25 08 2019 20:09:09.195:DEBUG [launcher]: BEING_FORCE_KILLED -> FINISHED
25 08 2019 20:09:09.195:DEBUG [launcher]: FINISHED -> FINISHED

For LitElement decorators you need a different configuration for your plugins:
{
    "presets": [
      "@babel/preset-typescript"
    ],
    // for libraries that support babel decorators (lit-element) use:
    "plugins": [
      ["@babel/plugin-proposal-decorators", { "decoratorsBeforeExport": true }],
      "@babel/plugin-proposal-class-properties"
    ]
}

I will update the docs on the website

Hi, @LarsDenBakker!
this config did not solve the issue.
.babelrc:
{
  "presets": ["@babel/preset-typescript"],
  "plugins": [
    [
      "@babel/plugin-proposal-decorators",
      { "decoratorsBeforeExport": true }
    ],
    "@babel/plugin-proposal-class-properties"
  ]
}

Output:
$ npx karma start ./karma.conf.ts

START:
26 08 2019 07:49:59.345:WARN [filelist]: Pattern "/Users/vcarvalho/dev/mnv/__snapshots__/**/*.md" does not match any file.
26 08 2019 07:49:59.346:WARN [filelist]: Pattern "/Users/vcarvalho/dev/mnv/components/**/*.test.ts" does not match any file.
26 08 2019 07:49:59.357:INFO [karma-server]: Karma v4.2.0 server started at http://0.0.0.0:9876/
26 08 2019 07:49:59.357:INFO [launcher]: Launching browsers ChromeHeadlessNoSandbox with concurrency unlimited
26 08 2019 07:49:59.361:INFO [launcher]: Starting browser ChromeHeadless
26 08 2019 07:49:59.681:INFO [HeadlessChrome 76.0.3809 (Mac OS X 10.13.6)]: Connected on socket Qs2zdmRmVU2j64TcAAAA with id 7194271

Error compiling: /components/titles/src/index.ts: Support for the experimental syntax 'decorators-legacy' isn't currently enabled (14:4):

  12 |
  13 | export class MnvTitles extends LitElement {
> 14 |    @property({ type: Number }) level = 1
     |    ^
  15 |
  16 |    static get styles() {
  17 |       return stylesComponent

HeadlessChrome 76.0.3809 (Mac OS X 10.13.6) ERROR: 'failed to load element http://localhost:9876/base/components/titles/MnvTitles.spec.ts?a6d4e47ac24fda97be642bf4a808ea7f4ee518bc'
  mnv-base
    ✔ works

Finished in 0.014 secs / 0.002 secs @ 07:50:01 GMT-0300 (Brasilia Standard Time)

SUMMARY:
✔ 1 test completed

Do you have any clues?

I just updated the demo with the correct config, it's working there: https://github.com/open-wc/open-wc/pull/775

Hi @LarsDenBakker, I put the configuration directly in karma.conf.ts and it works, but shouldn't .babelrc work?

Ah I see, what's missing in that case is babel: true in your config. You need to explicitly enable reading a custom babel config.

repo: open-wc/open-wc


text:
Support new fungible traits

https://github.com/paritytech/substrate/pull/8425
https://github.com/paritytech/substrate/pull/8435

Some imbalance related implementation in #5 should be helpful.

authors: shaunxw xlc


text:
feat: move the Connections, Models and Images sections to the admin panel settings

The Connections, Models and Images sections of the Settings form all are actions available to admins only. Therefore, they should be in the admin panel settings instead.

Connections, Models should stay for ease of access, I agree with Images section. Feel free to make a PR.

authors: Lanhild tjbck

repo: open-webui/open-webui


text:
enh: open PDF citations on the associated page

Description

If you use PDFs, the file is now opened on the right page of the text snippet citation on supported browsers.
Styling changes to clarify to the user that the link is clickable.
Additional "tippyOptions" property to add specific properties to the Tooltip (needed to remove the off-mount delay for scrolling containers).
"page" is now a i18n key
German locales

Changelog Entry
Added

📄 PDF Citation Support & UI Enhancements: PDFs now open directly at the referenced page in supported browsers, improving navigation. Additionally, clickable links in the citation modal have updated styling to make them more visually clear and user-friendly.

Thanks!

authors: jannikstdl tjbck


text:
feat: jwt utils

Resolves #566

Nice! Tested it, maybe this should recreate the token in the localstorage since setting this from the admin panel itself don't change the setting directly. You need to delete the token and login.


text:
When statement to be updated to LayerProtocolNameType

Name of Enumeration changed from LayerProtocolName to LayerProtocolNameType
Change to be documented in UML and YANG

UML changed

YANG updated

repo: openBackhaul/macInterface


text:
[TBBAS-1057] Support input ports in readers

Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[ ] This change requires a documentation update

Checklist:

[x] Pull request title reflects its content
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Description:

another PR on branch TBBASS-1057_support_inputports_in_readers_experiment has made

repo: openDAQ/openDAQ


text:
Same PtSituation sent twice (but with different ref)

For the connection from Bern to Lugano at 15:02 on the second TimedLeg there are 2 PtSituations with the same content (only different SituationNumber. Seems to be a data issue of the corresponding TU.
Refs on the Leg:

ch:1:sstid:100001:ddab72c0-eb3a-47d6-a7e1-3d863c38e47a-1
ch:1:sstid:100001:ddab72c0-eb3a-47d6-a7e1-3d863c38e47a-0

Gist for the whole response: https://gist.github.com/michaelruppen/8061bd8e7d76ada1c3c0838d9fa6919f
According textualContent:
<siri:TextualContent>
    <siri:SummaryContent>
        <siri:SummaryText xml:lang="de">Der Bahnverkehr zwischen St. Margrethen SG und
            Zürich HB ist eingeschränkt.
        </siri:SummaryText>
    </siri:SummaryContent>
    <siri:ReasonContent>
        <siri:ReasonText xml:lang="de">Der Grund dafür sind Bauarbeiten.</siri:ReasonText>
    </siri:ReasonContent>
    <siri:DescriptionContent />
    <siri:ConsequenceContent>
        <siri:ConsequenceText xml:lang="de">Es ist ein geänderter Fahrplan zu erwarten.
        </siri:ConsequenceText>
    </siri:ConsequenceContent>
    <siri:RecommendationContent>
        <siri:RecommendationText xml:lang="de">Prüfen Sie Ihre Verbindung im
            Online-Fahrplan.
        </siri:RecommendationText>
    </siri:RecommendationContent>
    <siri:DurationContent>
        <siri:DurationText xml:lang="de">Die Einschränkung dauert von 28.08.2024, 00:00
            bis 31.08.2024, 23:59.
        </siri:DurationText>
    </siri:DurationContent>
    <siri:RemarkContent />
</siri:TextualContent>

Adding @knr2000 also in the loop

In the productive system, there are still 3 duplicate disruption messages. I informed the EMS team to clean them up.
But the bug is fixed, there are no new added duplicate disruption messages.

ch:1:sstid:1:4e8ec1f0-2c53-5825-b30e-525e9183f12b
image.png

ch:1:sstid:1:5cdcfa49-c4bb-5bcc-8cb5-46a41915225e
image.png

ch:1:sstid:1:d51781ea-b77f-5b76-88b4-bf076ec6fa90
image.png

authors: TO-mdv michaelruppen vasile

repo: openTdataCH/ojp-sdk


text:
Typo in Bern?

There seems to be a strange high number in Bern on 2020-10-08

https://github.com/openZH/covid_19/blob/master/fallzahlen_kanton_total_csv_v2/COVID19_Fallzahlen_Kanton_BE_total.csv
Seems to be this commit:
https://github.com/openZH/covid_19/commit/69b0ec147f3a1622834daed4ac3b8a311d5213cf

The be.ch/corona site messed up with the dates 08.10.2020 instead of 08.10.2020 today.. 19'233 reflects the total number to date - I suspect this was then scraped?

I adapted out scraper to fix the typo here: https://github.com/openZH/covid_19/pull/1345
The new data should be there in a minute.

Merci!

authors: metaodi nachkontrolle rsalzer


text:
Possible incorrect mapping for NZ data

Hi there
Just taking a look at the NZ countrywide.json and it struck me that the mappings for don't seem quite right.
"city": "suburb_locality",
"district": "town_city",

If you query the data you see something like this
 'number': 75A, 'street': McElwee Street, 'unit': , 'city': Jervoistown, 'district': Napier,
but in the source data it's the other way around?

@andrewharvey  I'm assuming this could be intentional so the suburbs level is captured? Is this common elsewhere in OA schemas?

Hi there,
Not an expert but familar with the sources. Will ask others to verify, but:
Given the hierarchy of addresses, the current configuration for city/disctrict looks correct. We essentially don't use the "distrcit" (or territorial authority) for addressing purposes, and the data is structured such that suburb_locality + town_city will give an addressable location, dispite the apparent mismatch. (e.g. from the example above Jervoistown is a suburb of the city of Naper).
The source data used above is the "NZ Street Address" dataset, which was superceded in Jan 2023 by the "NZ Addresses" data available at https://data.linz.govt.nz/layer/105689-nz-addresses/ - it looks like the reference to layer ID 53353 needs ot be updated to 105689. The linked data dictionary at https://data.linz.govt.nz/document/24489-nz-addresses-data-dictionary/view/ describes how it should be used.
Note that it includes full address examples. It looks like full_address_number can be used in place of the existing number definition (since it is "All number components concatenated for an address").

@mtravis I think to be consistent with other global sources within OA, the NZ "town_city" field should be mapped to the OA "city" field, however OA doesn't have a field corresponding to the NZ "suburb_locality" and since this field is essential for addressing in NZ, bumping the NZ "town_city" up to the OA "district" to leave space for the NZ "suburb_locality" in the OA "city" field as in the current schema mapping is the best solution we have.
The hierarchy order of both the NZ data (suburb_locality, town_city) and OA (city, district, region) must be retained with the mapping we use.
I suspect the reason OpenAddresses doesn't have a sub-city field is due to the US roots of the project where suburb/locality doesn't form part of the address.
Take this example 4542 Irving St, San Francisco, CA 94122, United States

Although within "Outer Sunset" that it's not represented in the address.
Note that the same applies to the AU sources, where we map suburb/locality into the "city" field, and at least in the AU case the actual city (eg. San Francisco) doesn't form part of the address at all.

The source data used above is the "NZ Street Address" dataset, which was superceded in Jan 2023 by the "NZ Addresses" data available at https://data.linz.govt.nz/layer/105689-nz-addresses/ - it looks like the reference to layer ID 53353 needs to be updated to 105689. The linked data dictionary at https://data.linz.govt.nz/document/24489-nz-addresses-data-dictionary/view/ describes how it should be used.
Note that it includes full address examples. It looks like full_address_number can be used in place of the existing number definition (since it is "All number components concatenated for an address").

Thanks @hamishcampbell I can fix that.

Interesting that OA doesn't have a "sub-city" field.
I agree with @hamishcampbell and @andrewharvey's comments, and I work for Land Information New Zealand.

In the US the sub-city/neighborhood/suburb is mostly made up (usually by realtors or developers) and subjective/changes over time, so it's not used as part of addressing (even informally).
We could definitely consider adding a field that represents this in the output schema for OpenAddresses, especially if it's an important part of addressing elsewhere.

Note that it includes full address examples. It looks like full_address_number can be used in place of the existing number definition (since it is "All number components concatenated for an address").

@hamishcampbell The full_address_number includes both the address and unit, which OA provides separate fields for, so we either split full_address_number into the parts, or continue to reconstruct the unit and number fields from the sources.
Given this I wanted to validate the mapping so in QGIS I created a new field with expression
if("unit_value" != '', "unit_value" || '/', '') ||
"address_number_prefix" ||
"address_number" ||
"address_number_suffix" ||
if(
   "address_number_high" != '',
   '-' || "address_number_prefix" || "address_number_high"  || "address_number_suffix",
   ''
)

Then compared those values against full_address_number and found it always matched, so that's good.
In search of edge cases I found "1A-7A Puka Place, Inglewood" which shows the suffix applying to both the low and high number parts, which is something the current mapping we use gets wrong as OA will format it as "1A-7"

By the way, it looks like it's been a while since the NZ addressing data was updated. What's the usual frequency?

By the way, it looks like it's been a while since the NZ addressing data was updated. What's the usual frequency?

It should be weekly, but thhe OA data has been stuck at November 2022 due to the reason you mentioned. I have a PR which updates this as you suggested.

The source data used above is the "NZ Street Address" dataset, which was superceded in Jan 2023 by the "NZ Addresses" data available at https://data.linz.govt.nz/layer/105689-nz-addresses/

authors: andrewharvey dwsilk hamishcampbell iandees mtravis

repo: openaddresses/openaddresses


text:
[DON'T MERGE YET] adding Nelson Mandela Bay Municipality, South Africa

Couldn't find a license, but here's the conform in case anyone has more luck.
Website: http://www.nelsonmandelabay.gov.za/Business.aspx?pageID=154

Wow, look at that density!

I've asked them about the license today via http://www.nelsonmandelabay.gov.za/DepartmentFeedback.aspx.

I think this is fine to merge, it's CC-BY.
Here's the response to my email about the license:
Good Day

We are still in the process of updating the terms and conditions but in
essence below are the terms.

1)
NMBM makes no warranty of any kind, expressed or
implied, with regard to the data and shall not be held liable
in any event for any incidental or consequential damages in
connection with or arising out of the use of this data.
2)
Provide credit to the NMBM when using the data.

3)
You can redistribute the data but please then also send on the T&C.

Kind Regards
Franco Cilliers
GIS Analyst
NMBM
Tel: 041 506 1979
-33.961766, 25.621739
2nd Floor Algoa House
Chapel Street, Central, PE

LGTM, merging.

authors: migurski nvkelso thatdatabaseguy


text:
Doesn't work for continuous_mountain_car

Hello, the algo doesn't work for continuous_mountain_car, because it's reward is -pow(action[0],2)*0.1. What means, the car's initial state is a local max reward, all the exploration will decrease the reward and cannot get evoluated.
Of course, if the car can explore the final solution by one try, it will work. But the probability is negligible.
How do you handle such local max initial state issue???

What do you mean by Of course, if the car can explore the final solution by one try, it will work. .
I think that if it finds good solution (Reaching the final state) by accident then update in weights will be too small anyway as most of the population will want to keep the policy "Do nothing" . Correct me if I'm wrong but I think that for this experiment you would have to change the way in which policy weights are updated to give more value to much better results and ignore the rest, and you would have to increase the noise so it's possible to find good policy by adding noise to policy that does nothing.
This example is quite hard. I managed to get good results for discrete version (MountainCar-v0) but no success for this one.

@PatrykChrabaszcz Hello, after the solution is found quickly, the new weight will all be based on that solution.

I don't see how one proper solution would drag the weights for the current policy such that it makes it more probable to draw more policies that reach final state in the next generation (for this enviroment). Influence from policies doing nothing will be much bigger when you use current default updating rule.
Maybe you mean initializing current policy (by accident) such that big part of the first population reaches the goal state.

@PatrykChrabaszcz No, whenever it reachs the goal state, the influence will be big and immediate to the following biased and random weights. Because it's reward is huge compared with other opponents of doing nothing.

Reward might be huge but by default if I understand correctly it uses weighted average to update parameters. But the weights in this average are from <-0.5, 0.5> centered_rank . So if there is only one good solution in this population it will be counted as 0.5 but the next one assuming for example population of size 100 will be counted as 0.49. That's why I said you could change the way those weights are updated so it gives this good solution higher importance.
Am I right?

It's not average. It's only based on
(R_positive_rank-R_negative_rank)/number_of_rewards, so the huge reward =
1, the tiny reward is 0.0000001. They are independent.
On 11 May 2017 at 19:22, Patryk Chrabaszcz notifications@github.com wrote:

Reward might be huge but by default if I understand correctly it uses
weighted average to update parameters. But the weights in this average are
from <-0.5, 0.5> centered_rank . So if there is only one good solution
in this population it will be counted as 0.5 but the next one assuming for
example population of size 100 will be counted as 0.49. That's why I said
you could change the way those weights are updated so it gives this good
solution higher importance.
Am I right?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openai/evolution-strategies-starter/issues/9#issuecomment-300858409,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARFboFbmvTzAs32_hOB-s3yY0in5QaVvks5r40PegaJpZM4NW9SV
.

authors: PatrykChrabaszcz joyousrabbit

repo: openai/evolution-strategies-starter


text:
Figures Appendix C of the paper

Hello,
Congrats on the great work and thanks for sharing the code!
I wonder how you generated Figure 8 of Appendix C in your paper?
How are the images so similar, even when the scale is so reduced? Is there any conditioning beyond classifier guidance?
Many thanks!

This is the picture.

It looks like the diffusion models themselves can be class-conditional, notice how this model's forward() has a class label input that must be specified if the model is the conditional variant: https://github.com/openai/guided-diffusion/blob/main/guided_diffusion/unet.py#L638

The key word in the caption is "fixed seed". We fix the noise used to sample, which tends to result in very similar images even when changing classifier scale. To achieve this, simply call torch.manual_seed(n) with some fixed seed n before sampling.

I see, thanks.
I got a bit confused because the images at scale 0.0 are also class-conditioned. But the conditioning uses the other mechanism. The image illustrates how classifier guidance improves image quality, but the generated images are conditioned anyway...
Thanks!

authors: SANCHES-Pedro crowsonkb unixpickle woctezuma

repo: openai/guided-diffusion


text:
Refactored to latest version of pykube 0.15.0

pykube 0.15.0 resolves the host name issue

cluster.py : Removed "HACK https://github.com/kelproject/pykube/issues/29#issuecomment-230026930" and "Monkey-patch" code
requirements.txt : removed backports.ssl_match_hostname and replaced pykube git pull with pykube 0.15.0 release version

Replaced scaling-controller.yaml Replication Controller example with a Deployment autoscaler-dep.yaml.  Deployments provide declarative updates for Pods and Replica Sets (the next-generation Replication Controller).
Added an example secret yaml named autoscaler-secret.yaml
Updated README.md to reflect the changes, fixed the namespace issue in README.md and scaling-controller.yaml to be "kube-system" instead of "system".

Thank you!

authors: BrentDorsey vicki-c

license: mit


text:
READMEに除外リストの項目を追加

概要
AmebaのVisionを除外リストにいれることを推奨する主旨をREADMEに追加してみました。
誰がみても実装イメージが湧いている文脈かどうかみていただけると。

commit messageのtype、どちらもdocsにしちゃってください！

docsにしつつコミット1つにまとめましたー。

authors: herablog yasuda-shin

repo: openameba/textlint-rule-preset-ameba


text:
Dev

Merge @tghoward's pump.ini stuff (and some related text around adding a .gitignore for pump.ini).

Ok, I think this is ready to merge if someone can give it a quick once-over.

repo: openaps/docs


text:
Removing "enable" requirement for SMB - use preferences only

Per discussion in https://github.com/openaps/oref0/issues/737, moving forward with the community-voted option of removing the requirement to "enable" SMB, and only have to turn it on via preferences, to prevent edge case and unnecessary confusion. This needs testing before it merges.

To test: cd ~/src/oref0 && git fetch && git checkout smb-in-preferences-only && git pull && npm run global-install and then re-run oref0-setup.

Any volunteers to test this so we can merge it?

I'm testing it now. I switched to this branch, ran global install, took microbolus out of oref0-runagain.sh and re-ran setup. It is looping now with  Starting oref0-pump-loop at Thu Nov  2 10:51:02 EDT
However, I need to wait for lunch time to test SMB's. My current preferences are as follows:
{         "max_iob": 9,         "max_daily_safety_multiplier": 13,         "current_basal_safety_multiplier": 14,         "autosens_max": 1.5,         "autosens_min": 0.5,         "rewind_resets_autosens": true,         "adv_target_adjustments": false,         "exercise_mode": false,         "unsuspend_if_no_temp": true,         "enableSMB_with_COB": true,         "enableSMB_with_temptarget": true,         "enableUAM": true,         "curve": "rapid-acting" }

SMB isn't working for me. I think the problem may be unrelated to this branch's changes. My NS site is up and running and getting treatments, but openaps isn't able to communicate with it for some reason. I can't figure out why yet.

OK - I got my unrelated npm install issues all sorted out and fixed. Testing this branch and it works great for me. 👍
SMB's are working and I didn't use enable microbolus when I re-ran oref0-runagain.sh.

Thanks.  Based on @efidoman's testing I think we're good to merge this if nobody else wants to test anything specific before it goes to dev.

authors: danamlewis efidoman scottleibrand


text:
Remove Django requirement from openbadges_bakery

Python package openbadges_bakery is a dependency of badgecheck - Replace usage of Django's File class with underlying python class and post a new version before reincluding it in badgecheck.

https://github.com/concentricsky/openbadges-bakery This package, at tag 1.0.0b0+ is now updated to remove this requirement. Looking for comments on the python API before we integrate it into this project.
It expects an open file. Is that weird?
from openbadges_bakery import unbake

with open('filename.png', 'r') as f:
    data = unbake(f)

@mgylling and @ViktorHaag Comments welcome. When we get to a sprint or two from now, we'll be allowing files as an input format for the CLI and python interfaces.

digression: @mgylling Have the licensing implications of this dependency been considered? I'm not sure what the disposition is between IMS and the openbadges initiative -- i.e. is the openbadges badgecheck project going to take place "within the IMS unmbrella"?
I know that I can contribute work (a) to Apache-licensed projects, and (b) to projects within the IMS umbrella, but the bakery's license is different and not sure how that affects the general licensing situation here. (For example -- if this project uses the bakery project, is it subject to free and open distribution of its source?)

On the matter at hand -- Python's compression utils in the stdlib seems to use a pattern something like this:
from openbadges_bakery import bakery

with bakery.open('/my/file/foo.png', 'rb') as f:
   unbaked_content = f.read()

content = 'badge content'
with bakery.open('/my/file/foo.png', 'wb') as f:
    f.write(content)

Does that make more sense than what the bakery does now (where it expects file handles)?

@ViktorHaag, licensing etc: yes, this project will be done under the IMS umbrella, and under Apache. (We will be moving the entire OB github organization into the IMS organization any time now btw.) As for the bakery dependency, yes this might be an issue. I will discuss with @ottonomy and see what solution we can find to keep things clean and tidy licensewise. Stay tuned.

Thanks, @mgylling, and thanks for your understanding. 8/

I will relicense as Apache2 pending approval from CSky leadership.

That would be cool; thanks so much, @ottonomy.

Relicensed as Apache2. See: https://github.com/concentricsky/openbadges-bakery

authors: ViktorHaag mgylling ottonomy

repo: openbadges/badgecheck


text:
Network byte compare fix

URI:https://xx.xx.xx.xx/xyz/openbmc_project/network//eth0/attr/MACAddress, method:Get, args:{}
Response code:200, Content:{
  "data": "70:e2:84:14:2a:8",
  "message": "200 OK",
  "status": "ok"
}
Configure Valid MAC And Verify :: Configure valid MAC and verify.     | FAIL |
Parent suite setup failed:
MAC address does not exist.: '70:e2:84:14:2a:08' does not contain '70:e2:84:14:2a:8'

The MAC last nibble is 08 so a string compare won't work here..

In rvewiew https://gerrit.openbmc-project.xyz/#/c/9098/

repo: openbmc/openbmc-test-automation


text:
lib/bmc_network_security_utils.robot   *** Keywords *** header missing

Several tests in security/test_bmc_network_security.robot had been working until recent changes to lib/bmc_network_security_utils.robot. After the changes several formerly passing tests failed with the message:
No keyword with name 'Send Network Packets And Get Packet Loss'
I found that the *** Keywords *** header was missing in lib/bmc_network_security_utils.robot and added it.
Subsequently, the aforementioned error disappeared.

The upstream has the resource added https://github.com/openbmc/openbmc-test-automation/blob/master/security/test_bmc_network_security.robot#L10
Resource                ../lib/resource.robot
Resource                ../lib/bmc_redfish_resource.robot
Resource                ../lib/ipmi_client.robot
Resource                ../lib/bmc_network_security_utils.robot

so probably you level is bit lower where the recent changes were made, Please rebase

authors: generatz gkeishin


text:
[REQUEST] Automaticaly go to the Lolicode's part

When I select a block and then I switch to the Lolicode section, I would like to go automaticaly to the part of the code. It will be much more convenient, especially when you deal with huge config ...
Thanks

OB Settings > On config edit navigate to > LoliCode

Sorry I misread the issue and closed it by mistake 😅

Sorry I don't think I will do this, please give labels to blocks and then simply CTRL+F to find it. Implementing this would take too much time for the small benefit it will give.


text:
[BUG]  rules for wordlists pass do not work

Describe the bug
The rules for wordlists password do not work, If I enable one option it works, example digit, but if I enable other options with it does not work.
To Reproduce
Steps to reproduce the behavior:
https://gyazo.com/252a180d76919fd135979bf290d7cc0b
Expected behavior
Fix
Screenshots
https://i.gyazo.com/c27468340c3a9340e09a79a03a359de4.png
https://i.gyazo.com/669a289a2b950b95e87c8e471fd851a5.png
Version
1.0.1
Additional context
Add any other context about the problem here.

https://github.com/openbullet/openbullet/commit/f5330c97387d545f65199eded0ce3e23f9cb0ed9 Thanks for reporting, done

repo: openbullet/openbullet


text:
In prepare_ml_data.py, maybe don't allow create_files_specifying_spatial_and_temporal_locations_of_each_example to be run if a subset of data_sources is passed in at the command line

The issue is that, if the files specifying the spatial and temporal locations of each example are computed with less DataSources than the number of DataSources used to create batches, then we're likely to attempt to sample from locations that don't exist in at least one datasource.
Maybe the mechanism should be:
By default, if prepare_ml_data.py is called with at least one --data_source command line argument, and if the files specifying locations don't exist, then throw an error.  But allow users to overwrite this behaviour with a --force_creation_of_locations flag, or something like that??

And/or, check against start_time and end_time (after those have been implemented by issue #425) - as suggested by Peter in comment https://github.com/openclimatefix/nowcasting_dataset/issues/439#issuecomment-972728948


text:
added issue1.txt

Issue: #2

Hey @sahsudhanshu
Thanks for opening this PR 🚀. Mentor will review your pull request soon and till then, keep contributing and stay calm.
Thanks for contributing in OpenCode'24 ✨✨!

authors: Opencodeiiita-Bot sahsudhanshu


text:
Change the layout of the RegisterActivity in order to match with the rest of the application.

Currently the RegisterActivity has different colors and style as compared to the rest of the application. You have to make it so that the RegisterActivity looks similar to the Login and Forgot Password Activities. The background color should be white, the EditText's should look similar to the one's in the LoginActivity, use icons for FirstName, LastName and ConfirmPassword  as well at the side. Make sure the I agree to the Terms and Conditions is centered properly. Change the color of the button accordingly as well and make sure it has rounded edges. . Also, shift the back button at the top left of the screen to a bit more left and implement it's functioning. Clicking on it should take you back to the LoginActivity.
THE ID'S OF EVERY ELEMENT SHOULD REMAIN THE EXACT SAME. DO NOT CHANGE THEM.
Attach a screenshot of the new RegisterActivity layout when submitting a PR.

Claim

repo: opencodeiiita/SuperQuizzer


text:
Organization avatars not updating site-wide after being changed.

Describe the bug
Organization avatars on contributions pages and badges not updating.
To Reproduce
Steps to reproduce the behavior:

Contribute to a project as an organization.
Update organization profile with new avatar.
Go to contributions page of previously contributed to project.
See that avatar is still the old avatar.

Expected behavior
The avatar should be updated site-wide to the new avatar.
Desktop (please complete the following information):

OS: Linux
Browser Firefox
Version 78

We're normally adding a hash in the images URL to make sure that it's updated side wide.
Ie: https://images.opencollective.com/znarf/e534a60/avatar/256.png
I just checked and it's true that we don't use this versioned URLs for displaying contributors (ie: on https://opencollective.com/excalidraw), that should be looked at.

authors: LogoiLab znarf

repo: opencollective/opencollective


text:
Receipt showing wrong currency

Describe the bug
My NZ based organization has a recurring contribution to an OCEU Collective for EUR5/month. However, the receipt uses the $ symbol and doesn't specify currency. This is dangerous in two ways: the amounts I'm using this receipt to document for my tax reporting will not match the conversion rates to the wrong currency, and also my country uses the $ symbol as many do, so it's further ambiguous whether this is wrongly claiming to be NZD or USD.
To Reproduce
Steps to reproduce the behavior:

Make a contribution to a Collective in another currency
Download the receipt
See the $ symbol

Expected behavior
It should display both the symbol and the currency ID like USD, EUR, NZD.
Screenshots

@alanna I've deployed a potential fix for this problem, let me know if you still get this issue when downloading the receipt

authors: Betree alanna


text:
Add conformance tests for new v1.1 behaviour

Look through this milestone and see what we should be testing against:
https://github.com/opencontainers/distribution-spec/milestone/6
(both closed and open items)

closing as duplicate of https://github.com/opencontainers/distribution-spec/issues/370

repo: opencontainers/distribution-spec


text:
config-linux: add idle option for container cgroup

sched: Cgroup SCHED_IDLE support is introduced in Linux 5.15
we can mark a container SCHED_IDLE with this feature which means its sched weight are configured to the minimum
see also #1135

Looking at https://github.com/torvalds/linux/commit/304000390f88d049c85e9a0958ac5567f38816ee, I think this was even in 5.15. :sweat_smile:

Looking at torvalds/linux@3040003, I think this was even in 5.15. 😅

yes, updated issue & pr comment.

authors: tianon wineway

repo: opencontainers/runtime-spec


text:
Exception from GET when process has no name property

Describe the bug
Kestrel raises an exception when you try to GET process objects from a STIX bundle that don't have the name property (which is not required by STIX 2.0 and invalid in STIX 2.1).
Details of the bug

What is the hunt flow/script you are executing?

procs = GET process
        FROM file:///home/pcoccoli/github/kestrel-lang/tests/test_process_without_name.json
        WHERE pid > 4

What is the command that failed?
GET
What is the error message?

Traceback (most recent call last):
  File "/home/pcoccoli/github/firepit/firepit/sqlitestorage.py", line 157, in _do_execute
    cursor.execute(query)
sqlite3.OperationalError: no such column: procs_local.name

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/pcoccoli/.pyenv/versions/gh392/bin/kestrel", line 8, in <module>
    runpy.run_module('kestrel', run_name='__main__')
  File "/home/pcoccoli/.pyenv/versions/3.9.2/lib/python3.9/runpy.py", line 213, in run_module
    return _run_code(code, {}, init_globals, run_name, mod_spec)
  File "/home/pcoccoli/.pyenv/versions/3.9.2/lib/python3.9/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/home/pcoccoli/github/kestrel-lang/src/kestrel/__main__.py", line 59, in <module>
    outputs = session.execute(huntflow)
  File "/home/pcoccoli/github/kestrel-lang/src/kestrel/session.py", line 268, in execute
    return self._execute_ast(ast)
  File "/home/pcoccoli/github/kestrel-lang/src/kestrel/session.py", line 406, in _execute_ast
    output_var_struct, display = execute_cmd(stmt, self)
  File "/home/pcoccoli/github/kestrel-lang/src/kestrel/codegen/commands.py", line 101, in wrapper
    return func(stmt, session)
  File "/home/pcoccoli/github/kestrel-lang/src/kestrel/codegen/commands.py", line 72, in wrapper
    ret = func(stmt, session)
  File "/home/pcoccoli/github/kestrel-lang/src/kestrel/codegen/commands.py", line 321, in get
    prefetch_ret_entity_table = _filter_prefetched_process(
  File "/home/pcoccoli/github/kestrel-lang/src/kestrel/codegen/commands.py", line 641, in _filter_prefetched_process
    entity_ids = fine_grained_relational_process_filtering(
  File "/home/pcoccoli/github/kestrel-lang/src/kestrel/codegen/relations.py", line 254, in fine_grained_relational_process_filtering
    ref_processes = _query_process_with_time_and_ppid(store, local_var.entity_table)
  File "/home/pcoccoli/github/kestrel-lang/src/kestrel/codegen/relations.py", line 334, in _query_process_with_time_and_ppid
    rows = store.run_query(query).fetchall()
  File "/home/pcoccoli/github/firepit/firepit/sqlstorage.py", line 765, in run_query
    return self._query(query_text, query_values)
  File "/home/pcoccoli/github/firepit/firepit/sqlitestorage.py", line 184, in _query
    cursor = self._do_execute(query, values=values, cursor=cursor)
  File "/home/pcoccoli/github/firepit/firepit/sqlitestorage.py", line 164, in _do_execute
    raise InvalidAttr(m) from e
firepit.exceptions.InvalidAttr: invalid attribute: procs_local.name

To Reproduce
Steps to reproduce the behavior:

setup a data source: modify a bundle by removing all instances of process:name
test STIX-Shifter: n/a
run hunt flow: kestrel <huntflow file>

Expected behavior
No exceptions, and procs should contain 1 process object
Environment (please complete the following information):

OS: RHEL 8.7
Python version: Python 3.9.2
Python install environment: Python virtual environment
STIX-Shifter version: 4.6.2
kestrel-lang version: 1.5.2

Turns out this is fixed already in commit fe50950fa407e118672fd579c15133de721311cc

repo: opencybersecurityalliance/kestrel-lang


text:
Search: Results: Add support for entities of type Data Quality

Added support for entities of type Data Quality
Refactored ResultItem, decomposing some code to ResultItemTruncatedCell coomponent.

@Leshe4ka,

'Entities' column must show entities that are linked to the DataQualityTest
Please fix type 'Suit URL' -> 'Suite URL'

@Leshe4ka,

'Entities' column must show entities that are linked to the DataQualityTest
Please fix type 'Suit URL' -> 'Suite URL'

dataset_list comes null from backend...

repo: opendatadiscovery/odd-platform


text:
[WIP] Setup build images for Pytorch & Tensorflow with base ROCm image

Fixes for https://issues.redhat.com/browse/RHOAIENG-6377
Description

How Has This Been Tested?

Merge criteria:

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[ ] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[ ] The developer has manually tested the changes and verified that the changes work

Moreover, something that would be super useful for the PR review, but also as a complementary step to fulfill this work, is to set up the OCP-CI to build the newly created AMD PyTorch and TensorFlow notebooks.

Whoa, was wondering why the gha is failing, and it looks like it is running out of disk space
Total download size: 2.2 G
Installed size: 25 G
Downloading Packages:

Is it really necessary to install this much stuff? If yes, I'll get you more disk space tomorrow ;)

This ci fail is about missing lock file, https://github.com/opendatahub-io/notebooks/actions/runs/9600777904/job/26477839250?pr=557

Whoa, was wondering why the gha is failing, and it looks like it is running out of disk space

Here you go

https://github.com/opendatahub-io/notebooks/pull/577

Adding this here as ref: https://github.com/openshift/release/pull/53309

This is look good to me
i will be merging this for now.
The size is definitely as concern, we should take a deeper look at this.
and try to see, if this can be reduced.
Thanks all for the review and great work on this.
/lgtm
/approve

repo: opendatahub-io/notebooks


text:
Score results

Hi, please update always the score of this season

Note: You can always build your own up-to-date copy from the football.db - https://github.com/openfootball.  Cheers.


text:
chore(workspace): add version info script

Fix

3690986

Chore

replace craco to vite.

:tada: This PR is included in version 1.0.0-alpha.24 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.21 :tada:
The release is available on npm package (@alpha dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.15 :tada:
The release is available on npm package (@alpha dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.1 :tada:
The release is available on npm package (@alpha dist-tag)
Your semantic-release bot :package::rocket:

repo: opendatalab/labelU-Kit


text:
add lunarlander dqn&qrdqn main

add lunarlander dqn&qrdqn entry in lunarlander

This PR will be closed, related content has been fixed.

repo: opendilab/DI-engine


text:
Unable to install on Mac OSX

I am trying to following the instructions to install from a tar file. I have downloaded the tar file and extracted it and after running the ./opendistro-tar-install.sh script. I am getting an error that it can't find the bundled java. It is looking for it in a directory that does not exist:
could not find java in bundled jdk at //opendistroforelasticsearch-1.6.0/jdk.app/Contents/Home/bin/java
I found the bundled java in the folder opendistroforelasticsearch-1.6.0/jdk/bin. If I try to execute the java executable manually then I get an error:
% ./java
zsh: exec format error: ./java
Is it that the installation is not compatible with the latest version of OSX?

Hey @seanmbowen, I've only tested in High Sierra, but as far as I know, the bundled JDK doesn't work. We note in the documentation, "If you have your own Java installation and you set JAVA_HOME in the terminal, macOS works as well."

authors: aetter seanmbowen

repo: opendistro/for-elasticsearch-docs


text:
Include Openshift as a supported platform in Litmus

Is this a BUG REPORT or FEATURE REQUEST?
FEATURE REQUEST

What happened:

Currently, AWS, GCP (both via kops), GKE, Packet (kubeadm), Azure (AKS) are the platforms supported where litmus jobs can be run.

Openshift is a popular K8s platform which has to be included to the above list.

This involves:

Ansible playbooks to setup OpenShift cluster from Litmus
Test Litmus jobs on openshift & update jobs to enable successful run

What you expected to happen:

Enable litmus jobs to run on OpenShift clusters

How to fix it:

Openshift cluster creators can be created using a OpenShift-Ansible project. There are standard roles available for the same. Refer for ex: https://galaxy.ansible.com/openshift/openshift-ansible, https://galaxy.ansible.com/newswangerd/openshift-ansible

Once cluster is up, run the litmus pre-requisites & any existing test job.  Report/fix any failures on the litmus side (esp wrt default security policies, kubeconfig configmap, commands used etc.,)

Thanks @debojitkakoti ! Go ahead - looking forward to your PR! Marking the issue as 'taken'

Removing the issue-taken label as there have been no PRs on this.

This is now available https://github.com/openebs/litmus/blob/master/k8s/on-prem/openshift-installer/create_openshift_cluster.yml

authors: dargasudarshan ksatchit

repo: openebs/litmus


text:
chore: update charts to add 2Gi as a minimum hugepages

Rather than adding 1Gi extra just set 2Gi as the minimum.

bors merge

repo: openebs/mayastor


text:
Add performance benchmarking section

Include steps to run performance benchmarking section, help to compare with different cStor tunables.

It has been added in the documentation. Refer: https://docs.openebs.io/docs/next/performance.html
Here are the contents.
Steps for performance testing
Setup cStorPool and StorageClass
Choose the appropriate disks (SSDs or SAS or Cloud disks) and create pool and create StorageClass. For performance testing, performance numbers vary based

on the number of OpenEBS replicas (1 vs 3) (latency between cStor target and cStor replica)
on whether all the replicas are in one zone or across multiple zones
the network latency between the application pod and iSCSI target (cStor target)

Run fio test through OpenEBS Litmus

Clone litmus repositorygit clone https://github.com/openebs/litmus.git
cd litmus/apps/fio/tests/performance

Edit run_litmus_test.yaml and modify the following- name: PROVIDER_STORAGE_CLASS
  value: openebs-standard
 #value: local-storage

- name: APP_NODE_SELECTOR
  value: percona

- name: FIO_TEST_PROFILE
  value: standard-ssd

- name: FIO_SAMPLE_SIZE
  value: "128m"

- name: FIO_TESTRUN_PERIOD
  value: "60"

Run the fio performance testkubectl create -f run_litmus_test.yaml

Observe the results at the end of the test

Steps are documented under "Advanced Topics"
https://docs.openebs.io/docs/next/performance.html

authors: kmova ranjithwingrider

repo: openebs/openebs-docs


text:
[BD-46] fix: use fixed position for ProductTour Checkpoints's

Description
Include a description of your changes here, along with a link to any relevant Jira tickets and/or Github issues.
Deploy Preview
Include a direct link to your changes in this PR's deploy preview here (e.g., a specific component page).
Merge Checklist

[ ] If your update includes visual changes, have they been reviewed by a designer? Send them a link to the Netlify deploy preview, if applicable.
[ ] Does your change adhere to the documented style conventions?
[ ] Do any prop types have missing descriptions in the Props API tables in the documentation site (check deploy preview)?
[ ] Were your changes tested using all available themes (see theme switcher in the header of the deploy preview, under the "Settings" icon)?
[ ] Were your changes tested in the example app?
[ ] Is there adequate test coverage for your changes?
[ ] Consider whether this change needs to reviewed/QA'ed for accessibility (a11y). If so, please add wittjeff and adamstankiewicz as reviewers on this PR.

Post-merge Checklist

[ ] Verify your changes were released to NPM at the expected version.
[ ] If you'd like, share your contribution in #show-and-tell.
[ ] 🎉 🙌 Celebrate! Thanks for your contribution.

Thanks for the pull request, @viktorrusakov!
When this pull request is ready, tag your edX technical lead.

authors: openedx-webhooks viktorrusakov

repo: openedx/paragon


text:
Use NW.js to test html5 target

Instead of opening a webserver + opening the browser, what about using?: http://nwjs.io/
Right now lime test html5 doesn't end after closing the browser because it doesn't know when browser has terminated.
NW.js would provide a predictable lifecycle + a window that can center to the screen + enable chrome/v8 debugger.

I want to the website and the "normal" link is a 50Mo tar.gz,
too heavy to include.

I was going to recommend electron instead, but its only marginally smaller.

I think it is possible to install with npm: https://github.com/nwjs/npm-installer
Another option could be to download on demand. Just as happens when "setup" other stuff.
Also it could be a switch to decide whether to use plain server+browser or nw.js.
I like it because the command would close when closing the window.
Right now I'm integrating gdx-backend-jtransc with gradle:
https://github.com/jtransc/gdx-backend-jtransc/blob/master/cuboc-demo/build.gradle
And I have a task called runHtml5. So people just do: gradle runHtml5 and it works. But since it starts a webserver and it doesn't exit automatically when closing the windo, is a bit annoying and hard to integrate with debuggers and stuff.

I didn't know about electron. But it looks good to me :) :+1:

Electron has the advantage of being really well known and used,
no idea about nwjs.
Although it seems to be the other way for @soywiz :)
A lime setup html5 could work.
It would allow for traces to go into the console like all other targets,
and indeed to stop when the window is closed.
Could be nice indeed.

Ok. I have already integrated without lime. And I'm going to describe the process:
Stuff related to electron command (there is a npm package called electron-prebuilt that provides a cli interface for electron, so you can install it with npm -g install electron-prebuilt)
@JTranscRegisterCommand(target = "js", name = "electron", command = "electron", check = { "electron", "--version" }, getFolderCmd = { "npm", "list", "-g" }, install = {"npm", "-g", "install", "electron-prebuilt" })
@JTranscRunCommand(target = "js", value = { "electron", "{{ outputFolder }}/electron-main.js" })

At the javascript side:
if (typeof require !== 'undefined') {
	var electron = require('electron');
	if (electron) {
		var ipcRenderer = electron.ipcRenderer;
		console.log = function() { ipcRenderer.send('console.log', Array.from(arguments)); };
		console.warn = function() { ipcRenderer.send('console.warn', Array.from(arguments)); };
		console.error = function() { ipcRenderer.send('console.error', Array.from(arguments)); };
	}
}

The electron main:
const {app, BrowserWindow} = require('electron');

let mainWindow;

//console.log('electron');

// Quit when all windows are closed.
app.on('window-all-closed', function() {
	if (process.platform != 'darwin') app.quit();
});

// In main process.
const {ipcMain} = require('electron');
ipcMain.on('console.log', (event, arg) => { console.log.apply(console, arg); });
ipcMain.on('console.warn', (event, arg) => { console.warn.apply(console, arg); });
ipcMain.on('console.error', (event, arg) => { console.error.apply(console, arg); });

// This method will be called when Electron has done everything
// initialization and ready for creating browser windows.
app.on('ready', function() {
	// Create the browser window.
	mainWindow = new BrowserWindow({
		title: {{ title|quote }},
		width: {{ initialWidth }},
		height: {{ initialHeight }},
		autoHideMenuBar: true,
		frame: true,
	});

	// and load the index.html of the app.
	mainWindow.loadURL('file://' + __dirname + '/index.html');

	// Emitted when the window is closed.
	mainWindow.on('closed', function() {
		// Dereference the window object, usually you would store windows
		// in an array if your app supports multi windows, this is the time
		// when you should delete the corresponding element.
		mainWindow = null;
	});

	mainWindow.on('unresponsive', function() {
		console.log('Window got unresponsive!');
	});
});

I think this should be a separate target
openfl test windows -js perhaps?
We could also possibly do this as the node.js target

Tracking here, would be happy to see this :smile:
https://trello.com/c/AElshKia

authors: ibilon jgranick skial soywiz

repo: openfl/lime


text:
Accelerometer doesn't work correctly in Legacy

I have tested with openfl 3.3.9 and lime 2.6.9 for Android

If we change the orientation of device the datas that we receive ( accelerationX, accelerationY ) are inversed.
We should have the possibiliy to listen at least the event "orientationChange".

repo: openfl/openfl


text:
Rename allergen alert to ingredient alert for Open Beauty Facts

Open Beauty Facts has both allergens like Open Food Facts, but also undesirable ingredients (that are not allergens).
For OBF, the allergen alert should be renamed ingredient alert (and this might be the opportunity to do so for OFF, since there might be non-allergy reasons for banning an ingredient)

repo: openfoodfacts/OpenFoodFacts-androidApp


text:
The Rounded icon for Nougat doesn't work

It should fill up the circle

https://developer.android.com/guide/practices/ui_guidelines/icon_design_adaptive.html

@teolemon Is this still the case?  In my nougat the icon fills the circle.

fixed, closing, thanks @sachincool

authors: sachincool teolemon

repo: openfoodfacts/openfoodfacts-androidapp


text:
Fix NPE while changing language preference

Description

Fix Null Pointer Exception on changing language preference.
Occurs when you change the language preference for the second time.
LOGS
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'void io.reactivex.disposables.CompositeDisposable.dispose()' on a null object reference
at openfoodfacts.github.scrachx.openfood.features.HomeFragment.onDestroy(HomeFragment.java:100)
at androidx.fragment.app.Fragment.performDestroy(Fragment.java:3205)
at androidx.fragment.app.FragmentStateManager.destroy(FragmentStateManager.java:758)
Related issues
#3540

Related PRs

Screenshots

@sarah541 right one! Except I would like it more if it was initialized in the field declaration so we don't have to check for nullability.
Something like:
private final CompositeDisposable compDisp = new CompositeDisposable();

What do you think about it?

initialized in the field declaration

@VaiTon Makes sense. I will push a new commit.


text:
feat: New scan algorithm for Android devices

Some Android devices (mainly Samsung & < Android 12) have sometimes some difficulties to obtain the focus.
A new algorithm is available in the native code of our fork of the camera package.
The app will now be able to choose between the two from the settings.
I have also revamped a little bit the Settings by adding some titles:

Will fix #2251

Codecov Report

Merging #2265 (7019e72) into develop (2ea0da3) will decrease coverage by 1.15%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           develop   #2265      +/-   ##
==========================================
- Coverage     8.86%   7.70%   -1.16%
==========================================
  Files          161     181      +20
  Lines         6623    9238    +2615
==========================================
+ Hits           587     712     +125
- Misses        6036    8526    +2490

Impacted Files
Coverage Δ

...kages/smooth_app/lib/widgets/attribute_button.dart
0.00% <0.00%> (-92.00%)
:arrow_down:

...s/smooth_app/lib/data_models/user_preferences.dart
8.73% <0.00%> (-23.57%)
:arrow_down:

packages/smooth_app/lib/themes/smooth_theme.dart
60.00% <0.00%> (-22.98%)
:arrow_down:

...p/lib/generic_lib/dialogs/smooth_alert_dialog.dart
19.23% <0.00%> (-14.98%)
:arrow_down:

...mooth_app/lib/data_models/product_preferences.dart
26.47% <0.00%> (-4.96%)
:arrow_down:

.../smooth_app/lib/pages/onboarding/welcome_page.dart
0.00% <0.00%> (-3.13%)
:arrow_down:

.../smooth_app/lib/pages/onboarding/scan_example.dart
0.00% <0.00%> (-2.28%)
:arrow_down:

packages/smooth_app/lib/main.dart
15.74% <0.00%> (-2.16%)
:arrow_down:

...s/smooth_app/lib/pages/onboarding/next_button.dart
2.22% <0.00%> (-1.78%)
:arrow_down:

...p/lib/pages/onboarding/consent_analytics_page.dart
0.00% <0.00%> (-1.57%)
:arrow_down:

... and 169 more

Continue to review full report at Codecov.

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

repo: openfoodfacts/smooth-app