text:
SISSEGV in libclDNNPlugin.so

Hi,
I am trying to run an SSD model using clDNN plugin. I got the following crash:

Thread 1 "objdetect.test" received signal SIGSEGV, Segmentation fault.
0x0000000016c14080 in ?? ()
(gdb) bt
#0  0x0000000016c14080 in ?? ()
#1  0x00007ffff79a7827 in __pthread_once_slow (once_control=0x7fffdb2e67a8, init_routine=0x7fffe7831830 <__once_proxy>) at pthread_once.c:116
#2  0x00007fffd8c6e4a8 in ?? () from /usr/lib/x86_64-linux-gnu/libopencl-clang.so.9
#3  0x00007fffd8c58031 in ?? () from /usr/lib/x86_64-linux-gnu/libopencl-clang.so.9
#4  0x00007fffd74cf5bd in ?? () from /usr/lib/x86_64-linux-gnu/libopencl-clang.so.9
#5  0x00007fffd716d21f in ?? () from /usr/lib/x86_64-linux-gnu/libopencl-clang.so.9
#6  0x00007ffff7de5733 in call_init (env=0x10742bc0, argv=0x7fffffffe2a8, argc=5, l=) at dl-init.c:72
#7  _dl_init (main_map=main_map@entry=0x21018000, argc=5, argv=0x7fffffffe2a8, env=0x10742bc0) at dl-init.c:119
#8  0x00007ffff7dea1ff in dl_open_worker (a=a@entry=0x7fffffffb570) at dl-open.c:522
#9  0x00007ffff53b72df in __GI__dl_catch_exception (exception=0x7fffffffb550, operate=0x7ffff7de9dc0 , args=0x7fffffffb570) at dl-error-skeleton.c:196
#10 0x00007ffff7de97ca in _dl_open (file=0x7fffffffb880 "libigdfcl.so.1", mode=-2147483639, caller_dlopen=0x7fffdd1d3df9, nsid=, argc=5, argv=, env=0x10742bc0)
    at dl-open.c:605
#11 0x00007ffff7794f96 in dlopen_doit (a=a@entry=0x7fffffffb7a0) at dlopen.c:66
#12 0x00007ffff53b72df in __GI__dl_catch_exception (exception=exception@entry=0x7fffffffb740, operate=0x7ffff7794f40 , args=0x7fffffffb7a0) at dl-error-skeleton.c:196
#13 0x00007ffff53b736f in __GI__dl_catch_error (objname=0x106b8d70, errstring=0x106b8d78, mallocedp=0x106b8d68, operate=, args=) at dl-error-skeleton.c:215
#14 0x00007ffff7795735 in _dlerror_run (operate=operate@entry=0x7ffff7794f40 , args=args@entry=0x7fffffffb7a0) at dlerror.c:162
#15 0x00007ffff7795051 in __dlopen (file=, mode=) at dlopen.c:87
#16 0x00007fffdd1d3df9 in ?? () from /usr/lib/x86_64-linux-gnu/intel-opencl/libigdrcl.so
#17 0x00007fffdd1d3e4d in ?? () from /usr/lib/x86_64-linux-gnu/intel-opencl/libigdrcl.so
#18 0x00007fffdd177cf6 in ?? () from /usr/lib/x86_64-linux-gnu/intel-opencl/libigdrcl.so
#19 0x00007fffdd178935 in ?? () from /usr/lib/x86_64-linux-gnu/intel-opencl/libigdrcl.so
#20 0x00007fffdd18e627 in ?? () from /usr/lib/x86_64-linux-gnu/intel-opencl/libigdrcl.so
#21 0x00007fffdd1d8396 in ?? () from /usr/lib/x86_64-linux-gnu/intel-opencl/libigdrcl.so
#22 0x00007fffdd13cc1a in ?? () from /usr/lib/x86_64-linux-gnu/intel-opencl/libigdrcl.so
#23 0x00007fffe685b818 in clBuildProgram () from /usr/local/lib/libOpenCL.so.1
#24 0x00007fffe6dd2cdd in ?? () from /usr/local/lib/dldt_ie_plugins/libclDNNPlugin.so
#25 0x00007fffe6dd44e2 in ?? () from /usr/local/lib/dldt_ie_plugins/libclDNNPlugin.so
#26 0x00007fffe6d82804 in ?? () from /usr/local/lib/dldt_ie_plugins/libclDNNPlugin.so
#27 0x00007fffe6db1b6c in ?? () from /usr/local/lib/dldt_ie_plugins/libclDNNPlugin.so
#28 0x00007fffe6db1fdf in ?? () from /usr/local/lib/dldt_ie_plugins/libclDNNPlugin.so
#29 0x00007fffe6d81b72 in ?? () from /usr/local/lib/dldt_ie_plugins/libclDNNPlugin.so
#30 0x00007fffe6d9c12b in ?? () from /usr/local/lib/dldt_ie_plugins/libclDNNPlugin.so
#31 0x00007fffe6d81bde in ?? () from /usr/local/lib/dldt_ie_plugins/libclDNNPlugin.so
#32 0x00007fffe6e1948f in ?? () from /usr/local/lib/dldt_ie_plugins/libclDNNPlugin.so
#33 0x00007fffe6e1987e in ?? () from /usr/local/lib/dldt_ie_plugins/libclDNNPlugin.so
#34 0x00007fffe6dae10f in ?? () from /usr/local/lib/dldt_ie_plugins/libclDNNPlugin.so
#35 0x00007fffe6dae601 in ?? () from /usr/local/lib/dldt_ie_plugins/libclDNNPlugin.so
#36 0x00007fffe6dae7fa in ?? () from /usr/local/lib/dldt_ie_plugins/libclDNNPlugin.so
#37 0x00007fffe6db1b58 in ?? () from /usr/local/lib/dldt_ie_plugins/libclDNNPlugin.so
#38 0x00007fffe6db1da4 in ?? () from /usr/local/lib/dldt_ie_plugins/libclDNNPlugin.so
#39 0x00007fffe6d81b06 in ?? () from /usr/local/lib/dldt_ie_plugins/libclDNNPlugin.so
#40 0x00007fffe6da91a2 in ?? () from /usr/local/lib/dldt_ie_plugins/libclDNNPlugin.so
#41 0x00007fffe6be09e2 in ?? () from /usr/local/lib/dldt_ie_plugins/libclDNNPlugin.so
#42 0x00007fffe6be1b14 in ?? () from /usr/local/lib/dldt_ie_plugins/libclDNNPlugin.so
#43 0x00007fffe6b658da in ?? () from /usr/local/lib/dldt_ie_plugins/libclDNNPlugin.so
#44 0x00007fffe6b50543 in ?? () from /usr/local/lib/dldt_ie_plugins/libclDNNPlugin.so
#45 0x00007fffe6b4785a in ?? () from /usr/local/lib/dldt_ie_plugins/libclDNNPlugin.so
#46 0x00007fffe6b45314 in ?? () from /usr/local/lib/dldt_ie_plugins/libclDNNPlugin.so
#47 0x00007fffe6b3a4a5 in ?? () from /usr/local/lib/dldt_ie_plugins/libclDNNPlugin.so
#48 0x00000000023a2913 in InferenceEngine::InferencePlugin::LoadNetwork (config=std::map with 0 elements, network=..., this=0x1073b770) at /usr/local/include/dldt/cpp/ie_plugin_cpp.hpp:88

dldt version 2019_R3.1. clinfo outputs:

  Platform Name                                   Intel(R) OpenCL HD Graphics
Number of devices                                 1
  Device Name                                     Intel(R) Gen9 HD Graphics NEO
  Device Vendor                                   Intel(R) Corporation
  Device Vendor ID                                0x8086
  Device Version                                  OpenCL 2.1 NEO
  Driver Version                                  19.46.14807
  Device OpenCL C Version                         OpenCL C 2.0
  Device Type                                     GPU
  Device Profile                                  FULL_PROFILE
  Device Available                                Yes
  Compiler Available                              Yes
  Linker Available                                Yes
  Max compute units                               23
  Max clock frequency                             1150MHz
  Device Partition                                (core)
    Max number of sub-devices                     0
    Supported partition types                     None
    Supported affinity domains                    (n/a)
  Max work item dimensions                        3
  Max work item sizes                             256x256x256
  Max work group size                             256
  Preferred work group size multiple              32
  Max sub-groups per work group                   32
  Sub-group sizes (Intel)                         8, 16, 32
  Preferred / native vector sizes
    char                                                16 / 16
    short                                                8 / 8
    int                                                  4 / 4
    long                                                 1 / 1
    half                                                 8 / 8        (cl_khr_fp16)
    float                                                1 / 1
    double                                               1 / 1        (cl_khr_fp64)
  Half-precision Floating-point support           (cl_khr_fp16)
    Denormals                                     Yes
    Infinity and NANs                             Yes
    Round to nearest                              Yes
    Round to zero                                 Yes
    Round to infinity                             Yes
    IEEE754-2008 fused multiply-add               Yes
    Support is emulated in software               No
  Single-precision Floating-point support         (core)
    Denormals                                     Yes
    Infinity and NANs                             Yes
    Round to nearest                              Yes
    Round to zero                                 Yes
    Round to infinity                             Yes
    IEEE754-2008 fused multiply-add               Yes
    Support is emulated in software               No
    Correctly-rounded divide and sqrt operations  Yes
  Double-precision Floating-point support         (cl_khr_fp64)
    Denormals                                     Yes
    Infinity and NANs                             Yes
    Round to nearest                              Yes
    Round to zero                                 Yes
    Round to infinity                             Yes
    IEEE754-2008 fused multiply-add               Yes
    Support is emulated in software               No
  Address bits                                    64, Little-Endian
  Global memory size                              26877263872 (25.03GiB)
  Error Correction support                        No
  Max memory allocation                           4294959104 (4GiB)
  Unified memory for Host and Device              Yes
  Shared Virtual Memory (SVM) capabilities        (core)
    Coarse-grained buffer sharing                 Yes
    Fine-grained buffer sharing                   No
    Fine-grained system sharing                   No
    Atomics                                       No
  Minimum alignment for any data type             128 bytes
  Alignment of base address                       1024 bits (128 bytes)
  Preferred alignment for atomics
    SVM                                           64 bytes
    Global                                        64 bytes
    Local                                         64 bytes
  Max size for global variable                    65536 (64KiB)
  Preferred total size of global vars             4294959104 (4GiB)
  Global Memory cache type                        Read/Write
  Global Memory cache size                        524288 (512KiB)
  Global Memory cache line size                   64 bytes
  Image support                                   Yes
    Max number of samplers per kernel             16
    Max size for 1D images from buffer            268434944 pixels
    Max 1D or 2D image array size                 2048 images
    Base address alignment for 2D image buffers   4 bytes
    Pitch alignment for 2D image buffers          4 pixels
    Max 2D image size                             16384x16384 pixels
    Max planar YUV image size                     16384x16352 pixels
    Max 3D image size                             16384x16384x2048 pixels
    Max number of read image args                 128
    Max number of write image args                128
    Max number of read/write image args           128
  Max number of pipe args                         16
  Max active pipe reservations                    1
  Max pipe packet size                            1024
  Local memory type                               Local
  Local memory size                               65536 (64KiB)
  Max number of constant args                     8
  Max constant buffer size                        4294959104 (4GiB)
  Max size of kernel argument                     1024
  Queue properties (on host)
    Out-of-order execution                        Yes
    Profiling                                     Yes
  Queue properties (on device)
    Out-of-order execution                        Yes
    Profiling                                     Yes
    Preferred size                                131072 (128KiB)
    Max size                                      67108864 (64MiB)
  Max queues on device                            1
  Max events on device                            1024
  Prefer user sync for interop                    Yes
  Profiling timer resolution                      83ns
  Execution capabilities
    Run OpenCL kernels                            Yes
    Run native kernels                            No
    Sub-group independent forward progress        Yes
    IL version                                    SPIR-V_1.2
    SPIR versions                                 1.2
  printf() buffer size                            4194304 (4MiB)
  Built-in kernels                                block_motion_estimate_intel;block_advanced_motion_estimate_check_intel;block_advanced_motion_estimate_bidirectional_check_intel;
  Motion Estimation accelerator version (Intel)   2
    Device-side AVC Motion Estimation version     1
      Supports texture sampler use                Yes
      Supports preemption                         No
  Device Extensions                               cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_fp16 cl_khr_depth_images cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_icd cl_khr_image2d_from_buffer cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_intel_subgroups cl_intel_required_subgroup_size cl_intel_subgroups_short cl_khr_spir cl_intel_accelerator cl_intel_media_block_io cl_intel_driver_diagnostics cl_khr_priority_hints cl_khr_throttle_hints cl_khr_create_command_queue cl_khr_fp64 cl_khr_subgroups cl_khr_il_program cl_intel_spirv_device_side_avc_motion_estimation cl_intel_spirv_media_block_io cl_intel_spirv_subgroups cl_khr_spirv_no_integer_wrap_decoration cl_khr_mipmap_image cl_khr_mipmap_image_writes cl_intel_unified_shared_memory_preview cl_intel_planar_yuv cl_intel_packed_yuv cl_intel_motion_estimation cl_intel_device_side_avc_motion_estimation cl_intel_advanced_motion_estimation cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_intel_unified_sharing

/usr/local/lib/libOpenCL.so.1

Why is it from some "local" and not from a system package?
What application are you using? Do you have LLVM dependency in your project?
Did your try to run OpenVINO/DLDT samples on GPU?
BTW, LD_DEBUG=libs or more verbose LD_DEBUG=symbols may help with investigation of the problem (if it is LLVM symbols conflict).

@alalek
Thanks. It turns out to be not related to dldt. It was caused by I used tcmalloc in the program.

authors: YijinLiu alalek

repo: opencv/dldt


text:
PYTHON cv2.resize Error “(-215:Assertion failed) !dsize.empty()”

I am trying to resize an image with cv2.resize function in PYTHON3 and I get the following error:
error: OpenCV(4.5.1) C:\Users\appveyor\AppData\Local\Temp\1\pip-req-build-oduouqig\opencv\modules\imgproc\src\resize.cpp:3688: error: (-215:Assertion failed) !dsize.empty() in function 'cv::hal::resize'
My images are uint16 arrays:
img_ms.shape
(4, 57, 62)
img_pan.shape
(1, 1140, 1240)
The sample function I am using inside an image pansharpening script is:
downsampled_img_pan = cv2.resize(img_pan, (img_ms.shape[2], img_ms.shape[1]),
interpolation = cv2.INTER_AREA)[:, :, np.newaxis]
Thanks!

I dont think will work since you cannot convert a 4D img into 1D like this.

last dim must be lower than 512.  but 1240 > 512

source: gharchive/issue

repo: opencv/opencv-python

license: MIT

license_type: permissive

license_source: github-api


text:
Unexpected Error When running python3.6 train_single.py --dataset-folder <LIP_HOME> --checkpoint-path mobilenet_sgd_68.848.pth.tar --from-mobilenet

When I followed the guide :

In the second step, error occurred:

And I noticed the place where the error occurred:

However, there are not 'optimizer', 'scheduler' and ... in checkpoint

##Environment

Linux Ubuntu 16.04
Python version:3.6.7
Pytorch version:0.4.1
CUDA/cuDNN version:

Can you help me?@Daniil-Osokin @AlexanderDokuchaev @grib0ed0v @snosov1   Very thankful!

I cannot reproduce this. BTW, <LIP_HOME> should be substituted to the real path to the dataset. This error may happen, if --from-mobilenet key is missed, make sure, that passed it.

authors: Daniil-Osokin YOKE


text:
component-mlmd overlay is not working.

/kind bug
When adding component-mlmd overlay, metadata-writer pod fails to deploy
What did you expect to happen:
MLMD components deployed
Environment:

Python Version (use python --version):
SDK Version:
Tekton Version (use tkn version):
Kubernetes Version (use kubectl version):
OS (e.g. from /etc/os-release):

stale issue, we now have a working mlmd prototype and are in process of adding this as an optional component to dspo: https://github.com/opendatahub-io/data-science-pipelines-operator/pull/129

authors: HumairAK rimolive

repo: opendatahub-io/data-science-pipelines


text:
In Web Views, back button should navigate back through the Web View history instead of exiting it

####Tool: ODK Tables
We are taking advantage of the ability to add custom html and JavaScript to ODK Tables.  We have some single-page navigation in our custom page.  Right now, when we press the back button, the Web View closes and the user's position is lost.  We need to be able to respond to the event produced by the back button and suppress the native handling.  This needs to be enabled from the Java side.
The expected behavior from a user's point of view would be to navigate back through the Web View's history until there is no more, than exit the Web View after that.
Something like:
@Override
public void onBackPressed() {
    if (webView.canGoBack()) {
        webView.goBack();
    } else {
        super.onBackPressed();
    }
}

You can do this with a launchHtml call. When you hit back you will go to the caller of launchHtml. With this you can construct whatever back stack you like

authors: jbeorse magdalenacassel

repo: opendatakit/opendatakit

license_source: bigquery


text:
Add unit test support for tree value.

More details of this requirement need to be defined later.

@PaParaZz1 @liuyuisanai Some advices?

repo: opendilab/treevalue


text:
Use scripted metrics instead of terms query to reduce number of buckets

Issue #, if available:

#40
https://github.com/opensearch-project/trace-analytics/issues/21

Description of changes:
To calculate trace group average latency, dashboard previously aggregate on traceGroup first, then within each trace group, aggregate again on traceId (required because of https://github.com/opendistro-for-elasticsearch/trace-analytics/issues/27#issuecomment-805238691) and sample 1 traceGroupFields.durationInNanos from each trace bucket towards trace group average latency.
The implementation leads to two problems:

terms aggregation has a limit on bucket size of 10000, thus the metric is calculated based on most recent 10000 traces only
number of buckets grows quickly and we'll soon exceed the default max_bucket limit of 65536 for entire query

So we are changing the DSL implementation to use scripted metrics by maintaining a hashmap to guarantee uniqueness. This doesn't have the above problems, but needs more testing on performance.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Posted 2 questions/concerns on the current scripted_metric impl. Was testing another implementation, the steps are broken down like this:
...

Ah yes you are right, to ensure results are correct over multiple shards we have to reduce after we have all results. Updated PR to use your implementation, thanks!

source: gharchive/pull-request


text:
Revoke a client.crt?

Is there a way to revoke a generated client configuration, so that client can no longer be allowed to connect to the OpenDXL broker?

The OpenDXL broker supports revocation but it is a manual process and requires restart of the broker.
Please submit an enhancement request to make this process dynamic.
Steps

Create a text file called 'revokedcerts.lst' in the keysore folder in the configuration location
with similar permissions as the other files in the folder.
Ex In the Docker image, configuration folders are in the volume mount: /dxlbroker-volume)
Add the sha1 of the revoked cert and restart the broker. The client using that cert can no longer connect.

Note: The McAfee Managed Broker does support revocation dynamically without requiring a restart

authors: vkrish-mcafee wmunyan

repo: opendxl/opendxl-broker


text:
refactor(operator): add klog into NDM operator

Signed-off-by: Akhil Mohan akhil.mohan@mayadata.io
Why is this PR required? What issue does it fix?:
When using controller runtime logs, the logs contained information even from vendored packages with the complete stack rather than the point of error. This was making it difficult for debugging and also flooded the logs.
{"level":"info","ts":1588942250.7956839,"logger":"controller_deviceclaim","msg":"BlockDeviceClaim State is:Pending","Request.Namespace":"default","Request.Name":"bdc-ssa"}
{"level":"error","ts":1588942250.7958782,"logger":"controller_deviceclaim","msg":"Error selecting device","Request.Namespace":"default","Request.Name":"bdc-ssa","error":"no devices found matching the criteria","stacktrace":"github.com/openebs/node-disk-manager/vendor/github.com/go-logr/zapr.(*zapLogger).Error\n\t/home/travis/gopath/src/github.com/openebs/node-disk-manager/vendor/github.com/go-logr/zapr/zapr.go:128\ngithub.com/openebs/node-disk-manager/pkg/controller/blockdeviceclaim.(*ReconcileBlockDeviceClaim).claimDeviceForBlockDeviceClaim\n\t/home/travis/gopath/src/github.com/openebs/node-disk-manager/pkg/controller/blockdeviceclaim/blockdeviceclaim_controller.go:176\ngithub.com/openebs/node-disk-manager/pkg/controller/blockdeviceclaim.(*ReconcileBlockDeviceClaim).Reconcile\n\t/home/travis/gopath/src/github.com/openebs/node-disk-manager/pkg/controller/blockdeviceclaim/blockdeviceclaim_controller.go:121\ngithub.com/openebs/node-disk-manager/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/home/travis/gopath/src/github.com/openebs/node-disk-manager/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:215\ngithub.com/openebs/node-disk-manager/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func1\n\t/home/travis/gopath/src/github.com/openebs/node-disk-manager/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:158\ngithub.com/openebs/node-disk-manager/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1\n\t/home/travis/gopath/src/github.com/openebs/node-disk-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133\ngithub.com/openebs/node-disk-manager/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil\n\t/home/travis/gopath/src/github.com/openebs/node-disk-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:134\ngithub.com/openebs/node-disk-manager/vendor/k8s.io/apimachinery/pkg/util/wait.Until\n\t/home/travis/gopath/src/github.com/openebs/node-disk-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:88"}

With the change to klog
I0508 12:53:23.038552       1 blockdeviceclaim_controller.go:110] BDC bdc-ssa claim phase is Pending
E0508 12:53:23.038814       1 blockdeviceclaim_controller.go:170] Error selecting device for bdc-ssa: no devices found matching the criteria
I0508 12:53:28.038732       1 blockdeviceclaim_controller.go:110] BDC bdc-ssa claim phase is Pending
E0508 12:53:28.039020       1 blockdeviceclaim_controller.go:170] Error selecting device for bdc-ssa: no devices found matching the criteria

What this PR does?:

klog has also been added to make logs more readable
controller logs has been changed to klog
zap logger is still initialized so that controller runtime logs
are logged into console

Does this PR require any upgrade changes?:
No
If the changes in this PR are manually verified, list down the scenarios covered::
Any additional information for your reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:

[ ] Fixes #
[x] PR Title follows the convention of  <type>(<scope>): <subject>
[ ] Has the change log section been updated?
[ ] Commit has unit tests
[ ] Commit has integration tests
[ ] (Optional) Are upgrade changes included in this PR? If not, mention the issue/PR to track:
[ ] (Optional) If documentation changes are required, which issue on https://github.com/openebs/openebs-docs is used to track them:

Codecov Report

Merging #420 into master will decrease coverage by 0.33%.
The diff coverage is 25.00%.

@@            Coverage Diff             @@
##           master     #420      +/-   ##
==========================================
- Coverage   44.43%   44.10%   -0.34%
==========================================
  Files          60       60
  Lines        2858     2859       +1
==========================================
- Hits         1270     1261       -9
- Misses       1486     1494       +8
- Partials      102      104       +2

Impacted Files
Coverage Δ

...g/controller/blockdevice/blockdevice_controller.go
13.20% <0.00%> (-2.18%)
:arrow_down:

...er/blockdeviceclaim/blockdeviceclaim_controller.go
40.71% <31.81%> (-0.60%)
:arrow_down:

cmd/ndm_daemonset/probe/udevprobe.go
60.56% <0.00%> (-2.82%)
:arrow_down:

cmd/ndm_daemonset/probe/eventhandler.go
10.82% <0.00%> (-1.55%)
:arrow_down:

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 62fb2d9...083f716. Read the comment docs.

authors: akhilerm codecov-commenter

repo: openebs/node-disk-manager


text:
rancher kubelet iscsiadm fails to mount volumes to pods

Is this a BUG REPORT or FEATURE REQUEST? Bug Report

What happened:
I've installed OpenEBS into my cluster (three nodes total, all running centos), and created a PVC for jenkins. Originally the mount would fail due to timeout, which is when I discovered these instructions:
https://rancher.com/docs/rancher/v2.x/en/k8s-in-rancher/volumes-and-storage/#iscsi-volumes-with-rancher-launched-kubernetes-clusters
Which were created as a product of this report:
https://github.com/rancher/rancher/issues/15118
I've edited the cluster directly to add the bind mounts, and I've also tried building the entire cluster from scratch. I receive timeouts without the bind mounts, and I receive the below error with them:
  Type     Reason                  Age               From                     Message
  ----     ------                  ----              ----                     -------
  Normal   Scheduled               23s               default-scheduler        Successfully assigned jenkins/jenkins-5fb776c646-zktrj to worker16-0
  Warning  FailedAttachVolume      23s               attachdetach-controller  Multi-Attach error for volume "jenkins-jenkins-2704536410" Volume is already exclusively attached to one node and can't be attached to another
  Normal   SuccessfulAttachVolume  21s               attachdetach-controller  AttachVolume.Attach succeeded for volume "jenkins-jenkins-2704536410"
  Warning  FailedMount             3s (x6 over 19s)  kubelet, worker16-0      MountVolume.WaitForAttach failed for volume "jenkins-jenkins-2704536410" : failed to get any path for iscsi disk, last err seen:
iscsi: failed to sendtargets to portal 10.43.77.58:3260 output: libkmod: ERROR ../libkmod/libkmod.c:514 lookup_builtin_file: could not open builtin file '/lib/modules/3.10.0-862.14.4.el7.x86_64/modules.builtin.bin'
libkmod: ERROR ../libkmod/libkmod.c:586 kmod_search_moddep: could not open moddep file '/lib/modules/3.10.0-862.14.4.el7.x86_64/modules.dep.bin'
libkmod: ERROR ../libkmod/libkmod.c:586 kmod_search_moddep: could not open moddep file '/lib/modules/3.10.0-862.14.4.el7.x86_64/modules.dep.bin'
libkmod: ERROR ../libkmod/libkmod-module.c:832 kmod_module_insert_module: could not find module by name='iscsi_tcp'
iscsiadm: Could not insert module tcp. Kmod error -2
iscsiadm: Could not load transport tcp.Dropping interface default.
, err exit status 21

What you expected to happen:
Existing PVC should successfully mount to jenkins pod.
How to reproduce it (as minimally and precisely as possible):

Delete existing rancher cluster and manually clean nodes:

https://rancher.com/docs/rancher/v2.x/en/admin-settings/removing-rancher/user-cluster-nodes/

Configure iscsi initiator on each node per Rancher 2.0 documentation:

https://rancher.com/docs/rancher/v2.x/en/k8s-in-rancher/volumes-and-storage/#iscsi-volumes-with-rancher-launched-kubernetes-clusters

Create new custom cluster in rancher, applying bind mounts to kubelet container spec:

  kubelet:
    extra_binds:
      - "/etc/iscsi:/etc/iscsi"
      - "/sbin/iscsiadm:/sbin/iscsiadm"

Install OpenEBS 0.7.0 according to these instructions:

https://docs.openebs.io/docs/next/scheduler.html

Create PVC from YAML:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: jenkins
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 30Gi
  storageClassName: openebs-jiva-default

Install Jenkins from helm, configured to use above PVC.

running a kubectl describe pod <jenkins-pod-name> yields the error pasted above.
Anything else we need to know?:
Cluster info:
$ kubectl get nodes -o wide
NAME         STATUS    ROLES                      AGE       VERSION   INTERNAL-IP    EXTERNAL-IP   OS-IMAGE                KERNEL-VERSION               CONTAINER-RUNTIME
ceph01       Ready     controlplane,etcd,worker   37m       v1.11.3   192.168.0.20   <none>        CentOS Linux 7 (Core)   3.10.0-862.14.4.el7.x86_64   docker://17.3.2
nova02       Ready     controlplane,etcd,worker   34m       v1.11.3   192.168.0.24   <none>        CentOS Linux 7 (Core)   3.10.0-862.14.4.el7.x86_64   docker://17.3.2
worker16-0   Ready     controlplane,etcd,worker   34m       v1.11.3   192.168.0.23   <none>        CentOS Linux 7 (Core)   3.10.0-862.14.4.el7.x86_64   docker://17.3.2

$ kubectl get pods --all-namespaces
NAMESPACE       NAME                                              READY     STATUS      RESTARTS   AGE
cattle-system   cattle-cluster-agent-7cf96c6989-k2lkz             1/1       Running     0          34m
cattle-system   cattle-node-agent-9grsh                           1/1       Running     0          34m
cattle-system   cattle-node-agent-cbc7r                           1/1       Running     0          34m
cattle-system   cattle-node-agent-cd8cm                           1/1       Running     0          34m
ingress-nginx   default-http-backend-797c5bc547-95vlx             1/1       Running     0          37m
ingress-nginx   nginx-ingress-controller-4hs9d                    1/1       Running     0          35m
ingress-nginx   nginx-ingress-controller-6qv2d                    1/1       Running     0          35m
ingress-nginx   nginx-ingress-controller-hggm7                    1/1       Running     0          37m
jenkins         jenkins-5fb776c646-zktrj                          0/1       Init:0/1    0          12m
jenkins         jenkins-jenkins-2704536410-ctrl-8b44f8749-xmfvv   2/2       Running     0          32m
jenkins         jenkins-jenkins-2704536410-rep-6d79b84cdc-gm6jp   1/1       Running     0          32m
jenkins         jenkins-jenkins-2704536410-rep-6d79b84cdc-txzhh   1/1       Running     0          32m
jenkins         jenkins-jenkins-2704536410-rep-6d79b84cdc-znqhg   1/1       Running     0          32m
kube-system     canal-2t96d                                       3/3       Running     0          37m
kube-system     canal-m7mkb                                       3/3       Running     0          35m
kube-system     canal-vx64h                                       3/3       Running     0          35m
kube-system     kube-dns-7588d5b5f5-vxtc4                         3/3       Running     0          37m
kube-system     kube-dns-autoscaler-5db9bbb766-crsxf              1/1       Running     0          37m
kube-system     metrics-server-97bc649d5-ktvcr                    1/1       Running     0          37m
kube-system     rke-ingress-controller-deploy-job-dfrsm           0/1       Completed   0          37m
kube-system     rke-kubedns-addon-deploy-job-b92kp                0/1       Completed   0          37m
kube-system     rke-metrics-addon-deploy-job-l8dqr                0/1       Completed   0          37m
kube-system     rke-network-plugin-deploy-job-6qhz7               0/1       Completed   0          37m
kube-system     tiller-deploy-5474cdb876-mjntq                    1/1       Running     0          33m
openebs         cstor-sparse-pool-bg9u-5c87cc8859-mqxfp           2/2       Running     0          32m
openebs         cstor-sparse-pool-ll1w-7c4b585b56-b2kkn           2/2       Running     0          32m
openebs         cstor-sparse-pool-z2h6-77746f5844-gnb6f           2/2       Running     0          32m
openebs         maya-apiserver-6c78f488b4-q227r                   1/1       Running     0          32m
openebs         openebs-ndm-2p8p6                                 1/1       Running     0          32m
openebs         openebs-ndm-66w7n                                 1/1       Running     0          32m
openebs         openebs-ndm-bq28g                                 1/1       Running     0          32m
openebs         openebs-provisioner-764944c485-4tzlv              1/1       Running     0          32m
openebs         openebs-snapshot-operator-d896cff65-9b297         2/2       Running     0          32m

$ kj get svc
NAME                                  TYPE        CLUSTER-IP     EXTERNAL-IP   PORT(S)             AGE
jenkins                               ClusterIP   10.43.26.167   <none>        8080/TCP            32m
jenkins-agent                         ClusterIP   10.43.32.186   <none>        50000/TCP           32m
jenkins-jenkins-2704536410-ctrl-svc   ClusterIP   10.43.77.58    <none>        3260/TCP,9501/TCP   33m

$ kj get sc
NAME                        PROVISIONER                                                AGE
openebs-cstor-sparse        openebs.io/provisioner-iscsi                               35m
openebs-jiva-default        openebs.io/provisioner-iscsi                               35m
openebs-snapshot-promoter   volumesnapshot.external-storage.k8s.io/snapshot-promoter   35m

$ kj get pv
NAME                         CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS    CLAIM             STORAGECLASS           REASON    AGE
jenkins-jenkins-2704536410   30Gi       RWO            Delete           Bound     jenkins/jenkins   openebs-jiva-default             29m

$ kj get pvc
NAME      STATUS    VOLUME                       CAPACITY   ACCESS MODES   STORAGECLASS           AGE
jenkins   Bound     jenkins-jenkins-2704536410   30Gi       RWO            openebs-jiva-default   29m

Node info:
[root@worker16-0 ~]# cat /etc/os-release
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

[root@worker16-0 ~]# uname -r
3.10.0-862.14.4.el7.x86_64

Kubelet info:
root@worker16-0:/# lsmod | grep iscsi
iscsi_target_mod      291713  1
target_core_mod       340809  2 iscsi_target_mod
iscsi_tcp              18333  0
libiscsi_tcp           25146  1 iscsi_tcp
libiscsi               57233  2 libiscsi_tcp,iscsi_tcp
scsi_transport_iscsi    99909  3 iscsi_tcp,libiscsi
root@worker16-0:/# modprobe iscsi_tcp
modprobe: ERROR: ../libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file '/lib/modules/3.10.0-862.14.4.el7.x86_64/modules.dep.bin'
modprobe: FATAL: Module iscsi_tcp not found in directory /lib/modules/3.10.0-862.14.4.el7.x86_64

kubelet is running rancher/hyperkube:v1.11.3-rancher1 image.

For me it seems like just one volume per node seems to work - the moment a second pod wants to bind-mount a persistent volume on this host gets a failed to get any path for iscsi disk, last err seen: Could not attach disk: Timeout after 10s- anybody facing the same issue?

I am getting this as well

For me it seems like just one volume per node seems to work - the moment a second pod wants to bind-mount a persistent volume on this host gets a failed to get any path for iscsi disk, last err seen: Could not attach disk: Timeout after 10s- anybody facing the same issue?

Same issue:

For anyone interested, I bind mounted the /lib/modules folder to the kubelet in addition to the other two bind mounts:
  kubelet:
    extra_binds:
      - "/etc/iscsi:/etc/iscsi"
      - "/sbin/iscsiadm:/sbin/iscsiadm"
      - "/lib/modules"

I have no idea if it's a dangerous thing to do, but it resolved my issue.

Good to me after setting these params under cluster yaml.
I wonder whether this issue is due to:

I suspect it has to do with the jiva.replicas which is default set to 3. In this case a cluster must have at least 3 nodes.
My setup is one cluster and one node (1x bare metal machine)

Rancher 2.1.5
Ubuntu 16.04

Here is what I did to make OpenEBS working:
[Cleanup]

Remove openebs catalog app, and remove openebs from namespaces
remove the extra_binds from kubelet (if exists)
remove open-iscsi from host (if installed)

[On hosts]
Add "iscsi_tcp" (without quotes) to /ect/modules so this will be loaded on reboots, then execute the following commands
modprobe iscsi_tcp
mkdir /mnt/openebs-gpd

It's time to install OpenEBS from catalog library and wait for it to finish installing.
Now create a new StoragePool where we mount  "/mnt/openebs-gpd" and add  a new StorageClass where we set the jiva replicas to 1. Launch kubectl and paste the following:
cat <<EOF | kubectl create -f -
apiVersion: openebs.io/v1alpha1
kind: StoragePool
metadata:
  name: gpdpool
  type: hostdir
spec:
  path: "/mnt/openebs-gpd"
---
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: openebs-jiva-gpd-1repl
  annotations:
    cas.openebs.io/config: |
      - name: ReplicaCount
        value: "1"
      - name: StoragePool
        value: gpdpool
    openebs.io/cas-type: jiva
provisioner: openebs.io/provisioner-iscsi
reclaimPolicy: Delete
volumeBindingMode: Immediate
EOF

From here we can use this new "openebs-jiva-gpd-1repl" class to create pvc's on a single node.

@BalaBalaYi, what is the file you set the iscsi configuration?
Thanks.

@gilmararaujo
By rancher doc:
https://rancher.com/docs/rancher/v2.x/en/cluster-admin/volumes-and-storage/#iscsi-volumes-with-rancher-launched-kubernetes-clusters

From @atulabhi @avishnu == who hit a similar issue on AWS and had to do the following:
you have to run below two commands on nodes
modprobe iscsi_tcp
echo iscsi_tcp >/etc/modules-load.d/iscsi-tcp.conf

and lsmod | grep iscsi should return below output
[ec2-user@ip-x.x.x.x ~]$ lsmod | grep iscsi
iscsi_tcp              20480  2
libiscsi_tcp           24576  1 iscsi_tcp
libiscsi               61440  2 libiscsi_tcp,iscsi_tcp
scsi_transport_iscsi   106496  3 iscsi_tcp,libiscsi
scsi_mod              245760  5 sd_mod,scsi_transport_iscsi,iscsi_tcp,libiscsi,sg

authors: BalaBalaYi JannikZed aaahrens gbates101 gilmararaujo kmova nvoskuilen

repo: openebs/openebs


text:
openebes-hostpath is over-provisioning and we would like thick proviosining

Hello,
We are using openebs-hostpath 4.1.0 provisioners for our kube clusters deployed over Vspehere VMs. I see that openebs provisioner does over-proviosioning: on a 40Gi node I created 3 PVC with 30Gi, 40Gi and 50Gi. They were all created and volumes assigned. The problem with this behavior is our kube users create a lot of volumes that go over the available disk size and the apps crash when there is no more space to write to.
Is there a way we could configure it for thick provisioning? Ideally to take into account the size available and the size already reserved by other volumes.

Hi, have you looked at quotas?

authors: dedeira tiagolobocastro


text:
fix: fixed semantic-release preview

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.

@PKulkoRaccoonGang Even though your pull request wasn’t merged, please take a moment  to answer a two question survey so we can improve your experience in the future.

authors: PKulkoRaccoonGang openedx-webhooks

repo: openedx/paragon


text:
feat: import event-sink-clickhouse plugin

Description
This PR imports the code from the openedx-event-sink-clickhouse repository.

Thanks for the pull request, @Ian2012! Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.

@Ian2012 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.

repo: openedx/platform-plugin-aspects


text:
Openengsb 1712/service roles

based on OPENENGSB-1743

merged with OPENENGSB-200

repo: openengsb/openengsb-framework


text:
Template submission request: Crystal HTTP

I'd like to submit my Crystal template for the new HTTP of-watchdog.
It has a similar handler contract than the Python template.
https://github.com/koffeinfrei/crystal-http-template

The README looks good, please go ahead and raise the PR.

authors: alexellis koffeinfrei

repo: openfaas/store


text:
Validate datastore engine

Adding code to verify datastore engine, if its in permissible set of values which is provided in configuration
Description

Added

Added a DatastoreEngine type which takes up const permissible engine type values
Added helper methods for the type DatastoreEngine
Added checks to validate engine AFTER it is marshalled into config type
Added tests

References

Addresses comment - https://github.com/openfga/openfga/pull/712#issuecomment-1574015631
Review Checklist

[x] I have clicked on "allow edits by maintainers".
[x] I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
[x] The correct base branch is being used, if not main
[x] I have added tests to validate that the change in functionality is working as expected

Hi @jon-whit, based on our last discussion, raised this PR to verify Datastore engine. Please have a look. Thanks

Left some comments for review.

@jon-whit Addressed comments, plz check.

Left some comments for review.

@jon-whit Addressed comments, plz check.

Hey @jon-whit plz have a look and let me know if the changes are OK

Hi @Himanshu372, i apologize for taking so long to review this. I took the liberty of updating this PR with respect to main. I also added some more validations to the datastore configs.

Thank you for opening the PR.  At this time we are closing the PR as it has gone stale and needs to be brought up to date.  In the future feel free to re-open the PR.  Thanks again.

authors: Himanshu372 curfew-marathon miparnisari

repo: openfga/openfga


text:
Updates to project.xml within this repository's README.md

Within this repository's README.md, it looks like the project.xml example displayed has become dated.  For example, in my discussion regarding issues with html5 target, it was suggested to remove the 'dom' haxedef flag from the project.xml as Away3d primarily targets WebGL.
<project>
    <haxedef name="dom" if="html5" />
</project>

Can this be reviewed, potentially removing the 'dom' haxedef?

I've updated the README.md to reflect the current 'typical' project.xml. Thanks for pointing out the issue.


text:
can't compile on openfl 8.4 (swf)

Called from openfl/_internal/renderer/opengl/GLGraphics.hx line 43
Called from openfl/display/BitmapData.hx line 150
Called from openfl/display/BitmapData.hx line 300
Called from lime/graphics/Image.hx line 600
Called from lime/_internal/graphics/ImageDataUtil.hx line 394
Called from /usr/share/haxe/std/neko/Lib.hx line 42
Uncaught exception - load.c(237) : Failed to load library : lime.ndll
Error: Could not process asset libraries (swf)
Build halted with errors.

Temporary “solution”…
I used haxelib set [project-name] [version] to set the “current” version to the previous version.
To be safe, I did this for ALL the updates, including the samples.
Here’s a list of the projects I had to (re)set:
hxcpp: 3.4.188 [4.0.4]
lime-samples: 6.2.0 [7.0.0]
lime: 6.4.0 [7.0.0]
openfl-samples: 6.0.0 [8.4.0]
openfl: 8.2.2 8.3.0 [8.4.0]
RESULT:

actuate: [1.8.7]
as3hx: [1.0.6]
box2d: [1.2.3]
gsap: [1.0.4]
hxcpp: [3.4.188] 4.0.4
layout: [1.2.1]
lime-samples: [6.2.0] 7.0.0
lime: [6.4.0] 7.0.0
openfl-samples: [6.0.0] 8.4.0
openfl: 8.2.2 [8.3.0] 8.4.0

NOTE the version numbers in brackets…

Resolved, thank you :smile:

authors: jgranick loudoweb shigimcp

repo: openfl/openfl

license: mit


text:
Playing sound with flash.media.Sound.loadPCMFromByteArray generates clicks

Hello !
I tried multiple entry points for sound playing api, so far it works realllly well.
One minor hiccups is loadPCMFromByteArray, when I load a file and play it with this API on windows - debug, there is a "click" on sound startup ( I guess some buffers or setup is not okay )
Other entry points like :
new lime.media.AudioSource( lime.media.AudioBuffer.fromBytes( ))
flash.media.Sound.fromFile()
new lime.media.AudioSource( lime.utils.Assets.getAudioBuffer())
flash.media.Sound.fromAudioBuffer( lime.media.AudioBuffer.fromBytes( ))
Do work flawlessly withut glitch/click though so it's really a loadPCMFromByteArray  thing.
I'll change my sound path but you may want to have a look at loadPCMFromByteArray
Thanks a lot.
ps : I use openfl for lime-switch stuff
Keep me posted if you want a full reproducible example with source, I'll upload something
Bye and thanks a lot for the awesome work.
gallop_loop.zip

Thanks for letting us know :smile:
You said it works if you use AudioBuffer, does your code look at all like this code from loadPCMFromByteArray?
https://github.com/openfl/openfl/blob/develop/src/openfl/media/Sound.hx#L500-L504

Sorry I havent understood clearly :)
The source with the glitch is the one you linked.
Me, I l fell back on :
flash.media.Sound.fromAudioBuffer( AudioBuffer.fromBytes( ... ))
So I kinda guess something diverges in the loadpcm scenario :)
Keep me posted if you want a full sample.
Bye :)
Le mer. 6 mars 2019 à 19:37, Joshua Granick notifications@github.com a
écrit :

Thanks for letting us know 😄
You said it works if you use AudioBuffer, does your code look at all like
this code from loadPCMFromByteArray?
https://github.com/openfl/openfl/blob/develop/src/openfl/media/Sound.hx#L500-L504
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openfl/openfl/issues/2144#issuecomment-470223757, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAnVXAk-ASuKUtNcRQoXPdyTWqvwRE5Fks5vUArmgaJpZM4bg5yf
.

Okay! Thank you :smile:
Using your description, I reproduced the problem. Flash has the same problem!
Turns out, the loadPCMFromByteArray method does not expect the WAV file container. When try copying the bytes for your sound to position 736 (which appears to be the offset to the initial data), the click goes away.
Use the loadCompressedDataFromByteArray method and we'll use AudioBuffer.fromFile internally to decode the file and advance automatically around the file headers :wink:

Oh okay I never heard the glitch/click in my flash version of Dkh, it is
interesting.
Thank you for your time. ❤
Le mer. 6 mars 2019 à 22:00, Joshua Granick notifications@github.com a
écrit :

Okay! Thank you 😄
Using your description, I reproduced the problem. Flash has the same
problem!
Turns out, the loadPCMFromByteArray method does not expect the WAV
file container. When try copying the bytes for your sound to position 736
(which appears to be the offset to the initial data), the click goes away.
Use the loadCompressedDataFromByteArray method and we'll use
AudioBuffer.fromFile internally to decode the file and advance
automatically around the file headers 😉
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openfl/openfl/issues/2144#issuecomment-470274487, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAnVXLPoUZnuubO8Jcg8_PJX9g3ciGiHks5vUCxvgaJpZM4bg5yf
.

After checking I skipped the header in my actual code.
Nevermind I ll submit a full example after a few checks around your lead.
Thanks!
Le mer. 6 mars 2019 à 22:03, David Elahee david.elahee@gmail.com a écrit :

Oh okay I never heard the glitch/click in my flash version of Dkh, it is
interesting.
Thank you for your time. ❤
Le mer. 6 mars 2019 à 22:00, Joshua Granick notifications@github.com a
écrit :

Okay! Thank you 😄
Using your description, I reproduced the problem. Flash has the same
problem!
Turns out, the loadPCMFromByteArray method does not expect the WAV
file container. When try copying the bytes for your sound to position 736
(which appears to be the offset to the initial data), the click goes away.
Use the loadCompressedDataFromByteArray method and we'll use
AudioBuffer.fromFile internally to decode the file and advance
automatically around the file headers 😉
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openfl/openfl/issues/2144#issuecomment-470274487,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAnVXLPoUZnuubO8Jcg8_PJX9g3ciGiHks5vUCxvgaJpZM4bg5yf
.

I did just add some code to handle the number of samples specified. Perhaps we were adding a click at the end of the file, not before, or weren't handling the offset properly. Does Flash respect the position of the incoming byte object?

Yep position is respected in flash.
I ll reproduce tomorrow and will keep you posted if we have to reopen.
Thanks :)
Le mer. 6 mars 2019 à 22:09, Joshua Granick notifications@github.com a
écrit :

I did just add some code to handle the number of samples specified.
Perhaps we were adding a click at the end of the file, not before, or
weren't handling the offset properly. Does Flash respect the position of
the incoming byte object?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openfl/openfl/issues/2144#issuecomment-470277560, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAnVXEsEaFCX-49Auf5sbwULOhCR5kU8ks5vUC6JgaJpZM4bg5yf
.

I just made some commits that I think may help :smile:

Aww thanks
Le mer. 6 mars 2019 à 22:26, Joshua Granick notifications@github.com a
écrit :

I just made some commits that I think may help 😄
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openfl/openfl/issues/2144#issuecomment-470283258, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAnVXF7iyhrlcml-gAwxTO19fOI8OPSEks5vUDKEgaJpZM4bg5yf
.

Okay I confirm that the bug was caused by position not taken into account. I am testing the fix right now.

Something else I just discovered, on cpp target haxe.io.input does not advance bytearray position, which was the cause of the bug on my side. I'll investigate.

And okay I fixed my wav reader to retain byteinput pos rather than byte array pos and everything works.
Thank you very much :)

authors: delahee jgranick


text:
[ON HOLD] Fixes #2216: Cache the tagline.json

Description
An alternative apiClient was made to take care of caching the tagline.json file. The stale period (time after which the cached data would no longer be used) is currently set to 1 day and can be changed, if required.
Related issues and discussion
#fixes #2216

@jaindiv26 Can you provide comment, based on what you did for the tagline ?

@teolemon Sure, I'm just working on some other issue, will share the details soon.

@subhanjansaha @teolemon Here's the link to my merged PR. https://github.com/openfoodfacts/openfoodfacts-androidapp/pull/2012

@subhanjansaha I've expanded the tagline to all flavors and the PR is open please wait till this PR merger and then you can work on this issue.

@jaindiv26 Yes no problem, I will wait.

@subhanjansaha some small conflicts present. Could you also comment the code so that others know what the code does? This future-proofs the application.

@Karljoones Yes, I'll push a commit which resolves the merge conflict and documents the code well.

@subhanjansaha what's the current status of this? :)

Closing due to inactivity

authors: Karljoones jaindiv26 subhanjansaha teolemon

repo: openfoodfacts/openfoodfacts-androidapp


text:
🛑 .net deployment is down

In 8b44831, .net deployment (https://world.openfoodfacts.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: .net deployment is back up in 77511fa.

repo: openfoodfacts/openfoodfacts-upptime


text:
Implement the source fields from the Knowledge Panel API

What

[x] Implement the source fields from the Knowledge Panel API
[ ] Open questions

[ ] Instead of something custom, could it be passed directly in the main body of the panel ?
[ ] What about buttonization "Learn more on Wikipedia" ?

cc @jasmeet0817 @stephanegigandet
Code pointer

https://world.openfoodfacts.org/api/v0/product/5425015401027.json?fields=knowledge_panels

Part of

#499

Screenshots

@monsieurtanuki @M123-dev I'm assigning this issue to @g123k who's joining the core team to work on Flutter.
It seems that the field is not implemented in openfoodfacts-dart (https://github.com/openfoodfacts/openfoodfacts-dart/search?q=source), amirite ?
If not, @g123k you should file it there: https://github.com/openfoodfacts/openfoodfacts-dart
Also pointed in Smoothie's code: https://github.com/openfoodfacts/openfoodfacts-dart/blob/master/lib/model/KnowledgePanelElement.dart

I'm ready to code the openfoodfacts-dart part if needed (adding source_text, source_url, ...) if @g123k is supposed to do only the "flutter" part (@teolemon your comment was ambiguous on that aspect).

I have opened https://github.com/openfoodfacts/openfoodfacts-dart/issues/408 and assigned @g123k

@teolemon Yes we can :)

Published @teolemon https://github.com/openfoodfacts/openfoodfacts-dart/pull/406

cc @g123k

https://github.com/openfoodfacts/openfoodfacts-dart/pull/409/files

authors: M123-dev monsieurtanuki teolemon

repo: openfoodfacts/smooth-app


text:
Build fails because of `Theme.AppCompat.Light.NoActionBar not foundà

What

Build fails because of `Theme.AppCompat.Light.NoActionBar not foundà
Introduced by https://github.com/openfoodfacts/smooth-app/pull/981

Log
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:processDebugResources'.

A failure occurred while executing com.android.build.gradle.internal.res.LinkApplicationAndroidResourcesTask$TaskAction
Android resource linking failed
ERROR:/home/runner/work/smooth-app/smooth-app/packages/smooth_app/build/app/intermediates/packaged_manifests/debug/AndroidManifest.xml:62: AAPT: error: resource style/Theme.AppCompat.Light.NoActionBar (aka org.openfoodfacts.app:style/Theme.AppCompat.Light.NoActionBar) not found.

@M123-dev any idea what might have caused it in the Package merge ?

@teolemon @M123-dev My hunch: compileSdkVersion 31 and targetSdkVersion 31 in build.gradle.
In another 100% Android java project of mine, I've recently upgraded to 31. Could compile. But the app crashed at init time on Android 12 (not nice to have customers report that). Not the same issue, but I think 31 is problematic.

We are having the same issue on version 1 of OFF. I had to revert. It's probably some behavior change.

@monsieurtanuki sounds very likely like it.
From Stackoverflow it sounds like this is some change which happend 2015 when android 3 came out, so it's now probably completely removed.
https://stackoverflow.com/a/31402188/13313941

Example
heme.AppCompat.Light.NoActionBar
Becomes
Theme.Holo.Light.NoActionBar

I tried updating to Theme.Holo.Light.NoActionBar and without a theme at all, both didn't work. So I created a issue https://github.com/Yalantis/uCrop/issues/816, we have to wait what the maintainer responds

I just tried it with version 30 instead of 31 here https://github.com/openfoodfacts/smooth-app/tree/android-target-30 and it didn't work
The intersting things building on my machine works on 30 and 31

So we only need to import these line cause the image editing library depends on this native package, I was thinking about switching to a complete dart alternative, this solved this error, allows better debugging, support for other platforms etc...
Probably little less performance but we're not building a photo editing tool

For example https://pub.dev/packages/crop_your_image or https://pub.dev/packages/image_cropping

I am same Issue here,
Has there any solution yet?

We switched to a different image crop @Excel-Adeniyi  https://github.com/openfoodfacts/smooth-app/pull/1063

authors: Excel-Adeniyi M123-dev monsieurtanuki teolemon


text:
Introducing a simple "Rate app" link in settings

What

[ ] Introducing a simple "Rate app" link in settings
[ ] Example of what Citymapper does

Part of

#2515

Screenshot

Can I work on this ?

@AshAman999 @M123-dev I have made the pr for this, kindly review it ! Thanks

authors: Sudhanva-Nadiger teolemon


text:
feat: Force the Android app to be in landscape

Will fix #3331

Codecov Report

Merging #3334 (e8172e0) into develop (b0b52c5) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #3334   +/-   ##
========================================
  Coverage    10.48%   10.49%
========================================
  Files          251      253    +2
  Lines        12322    12313    -9
========================================
  Hits          1292     1292
+ Misses       11030    11021    -9

Impacted Files
Coverage Δ

packages/smooth_app/lib/pages/image_crop_page.dart
1.38% <0.00%> (-0.26%)
:arrow_down:

...s/smooth_app/lib/helpers/product_cards_helper.dart
0.00% <0.00%> (ø)

...smooth_app/lib/pages/product/new_product_page.dart
0.00% <0.00%> (ø)

...ooth_app/lib/background/background_task_image.dart
0.00% <0.00%> (ø)

...ooth_app/lib/pages/hunger_games/question_card.dart
0.00% <0.00%> (ø)

...th_app/lib/background/background_task_details.dart
0.00% <0.00%> (ø)

...th_app/lib/cards/data_cards/image_upload_card.dart
0.00% <0.00%> (ø)

...th_app/lib/pages/product/add_new_product_page.dart
0.00% <0.00%> (ø)

...th_app/lib/pages/product/product_image_viewer.dart
0.00% <0.00%> (ø)

...h_app/lib/pages/product/edit_ingredients_page.dart
0.00% <0.00%> (ø)

... and 7 more

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

iOS is already handled, right ?

Yes, I've checked


text:
Bug in worldcup.db built on 2018.06.22

Hi,
Fantastic work. I just came across some wrong result entries. I had a look at the world cup from 1954 using the worldcup.db built on 2018.06.22. It appears that the result at half time made it into the database, rather than the final result. Compare e.g. game 21 GER-BEL (database: 1:2, wiki: 5:2), Game 22 ESP-BRA (database: 3:0, wiki: 3:1) and the following games... I didn't test any further. Would be great if this was taken care of.
Cheers

Thanks for reporting. It's best (and recommended) to build yourself a fresh up-to-date copy (e.g. use $ sportdb new worldcup.  PS: There's nobody here to taken care of - unless you help.

authors: geraldb jmuec

repo: openfootball/world-cup


text:
Implement molecule equality operators

Implement

is_isomorphic for SMILES comparison
__eq__ for comparison of atoms (and their ordering), bonds, conformations, partial charges, and VirtualSites (note that this will be index-dependent)
"is" for object identity tests

Any others?

Update: We have changed what is desired behavior from these functions.

is_isomorphic does graph matching
__eq__ is the same as is_isomorphic
"is" should use the default python definition

This is currently what is implemented. We will therefore close this issue.
Note: SMILES comparison is hairy because we'll get different SMILESes out of different toolkits (and toolkit versions, and settings), and this could potentially get confusing. SMILES comparison is more thoroughly addressed by CMILES, and folks are free to use that if they really know what they want to accomplish.

repo: openforcefield/openforcefield


text:
ParameterError after update

Hi all,
I updated openforcefield/openforcefields using conda install -c omnia openforcefield openforcefields this morning and tried to use ff = ForceField('openff-1.0.0.offxml') but I may have missed something, as now code that used to work is getting a ParameterError after createSystem. Would appreciate if anyone can point me to a solution?
Thankyou!
Gist with minimal example using just propane:
https://gist.github.com/ljmartin/77e01e2b1cc5e9b4c274fff565e4fe96
error:
##Create drug system:
drug_system = drug_structure.createSystem(nonbondedMethod=PME, nonbondedCutoff=0.9*nanometer)
>>>
---------------------------------------------------------------------------
ParameterError                            Traceback (most recent call last)
<ipython-input-6-2c7ab80dfea0> in <module>
----> 1 drug_system = drug_structure.createSystem(nonbondedMethod=PME, nonbondedCutoff=0.9*nanometer)

~/miniconda3/envs/lew_conda/lib/python3.7/site-packages/parmed/utils/decorators.py in new_fcn(*args, **kwargs)
     29         if not SUPPORTED_VERSION:
     30             raise ImportError('You must have at least OpenMM 6.3 installed')
---> 31         return fcn(*args, **kwargs)
     32
     33     return new_fcn

~/miniconda3/envs/lew_conda/lib/python3.7/site-packages/parmed/structure.py in createSystem(self, nonbondedMethod, nonbondedCutoff, switchDistance, constraints, rigidWater, implicitSolvent, implicitSolventKappa, implicitSolventSaltConc, temperature, soluteDielectric, solventDielectric, useSASA, removeCMMotion, hydrogenMass, ewaldErrorTolerance, flexibleConstraints, verbose, splitDihedrals)
   2028         LOGGER.info('Adding bonds...')
   2029         self._add_force_to_system(system,
-> 2030                 self.omm_bond_force(constraints, rigidWater, flexibleConstraints)
   2031         )
   2032         LOGGER.info('Adding angles...')

~/miniconda3/envs/lew_conda/lib/python3.7/site-packages/parmed/utils/decorators.py in new_fcn(*args, **kwargs)
     29         if not SUPPORTED_VERSION:
     30             raise ImportError('You must have at least OpenMM 6.3 installed')
---> 31         return fcn(*args, **kwargs)
     32
     33     return new_fcn

~/miniconda3/envs/lew_conda/lib/python3.7/site-packages/parmed/structure.py in omm_bond_force(self, constraints, rigidWater, flexibleConstraints)
   2258                 continue
   2259             if bond.type is None:
-> 2260                 raise ParameterError('Cannot find necessary parameters')
   2261             force.addBond(bond.atom1.idx, bond.atom2.idx, bond.type.req*length_conv,
   2262                           2*bond.type.k*frc_conv)

ParameterError: Cannot find necessary parameters

Hi @ljmartin ,
Thanks for the report and reproducing example!
This is happening because openff-1.0.0.offxml includes hydrogen bond length constraints in the force field definition, which makes the original bond k values get lost in this workflow. We quietly updated the examples to fix this, but probably should have been more verbose about the needed changes.
To fix this, you should load the force field without hbond length constraints (openff_unconstrained-1.0.0.offxml):
ff = ForceField('openff_unconstrained-1.0.0.offxml')

and have ParmEd apply them with the constraints=HBonds keyword argument to create_structure in the last cell:
from simtk.openmm import app
drug_system = drug_structure.createSystem(nonbondedMethod=PME,
                                          nonbondedCutoff=0.9*nanometer,
                                          constraints=app.HBonds)

This fix worked for me in the notebook you sent. Please let me know if it clears up the issue for you.

This is a peculiarity of going through the OpenMM System representation, and would be resolved once we can implement https://github.com/openforcefield/openforcefield/issues/310

Thankyou very much for the explanation! That works.
Didn't realise the examples had been updated but it's pretty clear in the one you linked.
cheers

authors: j-wags jchodera ljmartin


text:
Adding Sam to About page, updating Bios, linking Bios from headshots

Oct 15 -- Added an object for Sam Hudgens to the members array in src/pages/app-about/app-about.tsx.
Oct 16 -- Updated bio page to include content about Sam, then linked the headshots on the About page to their respective bio pages by inserting a element into the app-member component.

Hey @samhudgens
I briefly looked over the changes within this PR, and noticed that your changes may not have been pushed to this branch. Could you review this over? You can view the difference(s) between the base branch and the branch you want to merge into it by navigating to the Files changed tab at the top of this page.
Let me know and I can circle back to review this.
Also - If you could please update the base branch (it is currently master) to develop then a developer will review, test, and see if we can get this merged in and closed out. You can edit the base branch by clicking the edit button on the right-hand side by the PR name up at the top of this view.
If you have questions at all feel free to message me on slack :)
Thanks!

Hey @samhudgens
I am going to set up a meeting with you, myself, and Young to review your changes together tomorrow morning. Look out for a google calendar invite in your email! :)
Thanks.

authors: PaulPaulDevelops samhudgens


text:
feat: add preload property to resources

Task: https://openforge.teamwork.com/#/tasks/16322266

QA Passes


text:
📝(project) improve README

Proposal

README should emphasise that Ralph is an LRS along with a CLI and library.
README should point quickly to the documentation.
Adding Ralph logo as it would be a nice eye-catcher.
Adding shields for Tests, PyPi package and python versions supported.
- Adding a Contributors section to thank every contributor.

@Leobouloc you're right! Removing Contributors section

Perhaps we could make things clearer by showing the different functions in higher level titles ?
⚡ Quick start guide : Run a LRS
⚡ Quick start guide : Manipulate data with the cli

authors: Leobouloc wilbrdt

repo: openfun/ralph


text:
Add test case for ThreadPoolExecutorUtil

Fixes #1330
Changes proposed in this pull request:

Add test case for ThreadPoolExecutorUtil

contains history code

authors: barret-yzh magestacks


text:
Abstracting terminal reference

branch to resolve:
terminal page load flickerting
make terminal v2 available on /terminal instead of /terminalv2

@vaughnangoy Please code review this and comment when you are happy with this PR.

authors: purificant vaughnangoy


text:
rm command types that aren't used

removes the unused types added during Valkyrie training.
@gizatt : is this ok? the code has been changed to use atlas_command_t. I'm happy to reintroduce robot_command_t if its needed in future, but it would be different from what this.

Going ahead and accepting this.

repo: openhumanoids/oh-distro


text:
Explore ways to transclude yaml files

The permalink generation method like the below looks very nice (good find @liesenf). However, it is tied to a particular commit, so it won't update. (This is where the hash comes from.)
https://github.com/opening-up-chatgpt/opening-up-chatgpt.github.io/blob/4dfeae8db12bdd00b8bc7a1c83405b82c99b0aa1/projects/BELLE.yaml#L3-L70
Any other methods available?

I wonder if we can trigger a github action to the the updating for us: any time a yaml file is updated, regenerate permalinks to the code and update readme.md with the latest versoin.

This would be GREAT

closing as stale

authors: liesenf mdingemanse


text:
Dependency ignored when it contains default package

I have found that if a dependency contains code in the default package, it is not included in the running app.
Here is an example maven project that shows the problem. It depends on com.fimtra:clearconnect:3.16.0 (which contains code in the default package)
jfx-test.zip

Duplicated from this issue #18. There is already a PR to fix it #17 . Maybe you want to give it a try?

Ah, I should have spotted it was already raised. Anyhow, I have tried the fix and it works - thanks.

Thanks for testing.

authors: jperedadnr paulmackinlay

repo: openjfx/javafx-maven-plugin


text:
Remove nameHash, bodyHash, spaceHash

Expected behavior
We don't need to add the newly added fields in the erc712 branch for:

nameHash
bodyHash
spaceHash

Here is a record from a Slack conversation:

Jeremiah Trein
For ERC712 Snapshot Hub, are the new POST /message requirements for spaceHash, nameHash, bodyHash hashed using a function like Web3.utils.sha3

Felipe Forbeck
Yes, they use sha3. But I am changing these attribute names to: space, name and body as requested per David Roon

Actual behavior
They are required by the API, but we only use them before submitting to Moloch.
Steps to reproduce the behavior
N/A

cc: @adridadou

Important note from @fforbeck :

about removing the nameHash, spaceHash, bodyHash I am not sure, because they are part of the signature of ERC712, if we remove them it changes the signature and then it also breaks the signature validation

I think we will need to use the prepareMessage helper to provide Snapshot this information.

Important note from @fforbeck :

about removing the nameHash, spaceHash, bodyHash I am not sure, because they are part of the signature of ERC712, if we remove them it changes the signature and then it also breaks the signature validation

I think we will need to use the prepareMessage helper to provide Snapshot this information.

OK, confirmed with @adridadou that we can remove these values from the API. Below is an excerpt of the conversation:

regarding nameHash an bodyHash, it does not change the signature scheme because using name string or nameHash bytes32 is basically the same

we only need it when we call the smart contract

because the name of the property does not affect the result of the hash only the values (and a certain order )

OK, confirmed with @adridadou that we can remove these values from the API. Below is an excerpt of the conversation:

regarding nameHash an bodyHash, it does not change the signature scheme because using name string or nameHash bytes32 is basically the same

we only need it when we call the smart contract

because the name of the property does not affect the result of the hash only the values (and a certain order )

https://github.com/openlawteam/snapshot-hub/blob/erc-712/server/index.ts#L212
This one does not mention nameHash or bodyHash but I think the length requirement needs updating.

https://github.com/openlawteam/snapshot-hub/blob/erc-712/server/index.ts#L212
This one does not mention nameHash or bodyHash but I think the length requirement needs updating.

https://github.com/openlawteam/snapshot-hub/blob/erc-712/server/index.ts#L212
This code does not mention nameHash or bodyHash but I think the length requirement needs updating.

actually we have that as the last 2 parameters, it is just the line comment that is wrong. I already updated that. Thanks for flagging.

https://github.com/openlawteam/snapshot-hub/blob/erc-712/server/index.ts#L212
This code does not mention nameHash or bodyHash but I think the length requirement needs updating.

actually we have that as the last 2 parameters, it is just the line comment that is wrong. I already updated that. Thanks for flagging.

Done: docker pull openlaw/snapshot-hub:erc-712-7dc333f5

Done: docker pull openlaw/snapshot-hub:erc-712-7dc333f5

authors: fforbeck jtrein

repo: openlawteam/snapshot-hub


text:
Selecting a feature programatically does not apply the selected style to it

Describe the bug
It might be possible to select a feature programatically by pushing it to the selection and dispatching the accoring event. This triggers the "select" event. However the style of the feature is not updating.
To Reproduce
I have a function like:
public selectFeature(featureId) {
    let feature: Feature = this.vectorSource.getFeatureById(featureId)
    console.log("selectedFeature", this.select)
    if (feature) {
      this.select.getFeatures().push(feature)
      this.select.dispatchEvent({
        type: 'select',
        selected: [feature],
        deselected: []
      });
    }
  }
[...]
 this.select.on("select", ev => {
      console.log("on select", ev);
})

where this.select is the Select Interaction. Clicking on a feature in the map highlights the feature normally in the selected style. However calling the function to select the according feature, does not. The on select is triggered for both, so I would expect the style to be applied equally.
Seems like a bug to me.
Expected behavior
Update the style accordingly.
Using ol 6.0.1

I think I have the same issue. I'll explain it within one of the ol example:
Describe the bug:
Same as the post above.
To Reproduce

Use the example: https://openlayers.org/en/latest/examples/select-features.html
In the js example, create a const selections = new Collection();

Then:

If you use this selections as a option.feature of one Select, the style is still updated.
If you use this selections as a option.feature of multiple Select, the style is never removed.

So this won't work:
const selections = new Collection();

const selectSingleClick = new Select({
  features: selections,
});

const selectClick = new Select({
  condition: click,
  features: selections,
});

(but if you set one of the two features option to null, it works)
Expected behavior
Update the style accordingly.
Using ol 6.1.1

This issue is still present in the version ol: ^8.2.0.
Are there any plans to fix it, or is it not considered important? If so, is there some useable workaround?

authors: Chris1234567899 ger-benjamin mathudak

repo: openlayers/openlayers


text:
Not rendering TileWMS on iPhone

For some reason all my WMS Tile layers are not rendering on iPhone's and iPad's, what could be the problem? Regular ImageWMS renders just fine but i cannot use that for all features as it will take too long to load.
Here's part of my code:
	  var testLayer = new ol.layer.Tile({ 		  source: new ol.source.TileWMS({ 				url: 'http://localhost/WMSServer', 				params: {'LAYERS': 'mylayer,andanotherone'},   		  }) 	  });
...
      var map = new ol.Map({ 		controls: [],         layers: testLayer,         target: 'map', 		allOverlays:true,          view: new ol.View({           center: [1658377.765675, 8357930.420814],           zoom: zoom         })       });
Any ideas on how to solve?

Impossible to guess from the code snippets you provided. Maybe you're maxing out phone memory by stacking too many layers? Also note that there is no allOverlays: true option.

I think i have isolated the problem, it has nothing to do with the above code. For some reason if i comment out these lines that gets the users position everything works on iOS aswell, but then i cannot get the user position.
The isolated code that's causing the trouble:
`		if ("geolocation" in navigator) {
navigator.geolocation.getCurrentPosition(do_something);
} else {
// geolocation IS NOT available
}
	function do_something(position) {
			  console.log(position);
		var latUser = position.coords.latitude;
		var longUser = position.coords.longitude;

		var newCoord = ol.proj.transform([longUser, latUser], 'EPSG:4326', 'EPSG:3857');

		//console.log(newCoord);
		map.setView(new ol.View({
				center: newCoord,
				zoom: zoom
		 }));

		// Adds map marker...
		addmarker(latUser, longUser, 'marker.png');

	}`

The above code works on PC and Android, but not on iOS.
Any suggestions?

Not related to OpenLayers. But you should also set an ol.View on devices that do not support geolocation.

authors: TheBoXon ahocevar


text:
The browser changes the scale translation  then fun getPixelFromCoordinate is still start number

when The browser changes the scale translation  then fun getPixelFromCoordinate is still  original value,
is it a issue?

Are you referring to the device pixel ratio (what is "changes the scale translation")?
Can you provide an example that demonstrates the issue?

yes ， i mean i   changed the  window.devicePixelRatio，
i did a canvas animation .
like this:
map.on('postcompose',evt=>{
....
let piex = map.getPixelFromCoordinate([50,50]);
})
after changed it, the piex is not  change but the vector had scale.

the red circle shuld overlay the green circle


text:
View Create Title: Missing requirements for database

The document describes in one sentence that the user can change between Journal, Book and Database, but Database is not further explained.
(p.53)

Database has neither the book fields nor the journal fields. As object, it is comparable to journal.

authors: darupp dirk-ecker

repo: openlibraryenvironment/gokb


text:
Content fixes

https://trello.com/c/m6JLh8pq/16-incorrect-content

Changes are sensible and look good to merge. Only unknown is whether there is a proper class for highlighting the syntax under explore/index.html. @lunson: do you have more hindsights?

@lunson Wrap or indent?  It's verbatim preformatted text, with explicit indentation which is why I also added <pre> tags around the <code>.
Could the highlighting be due to missing CSS?

@sbesson The code class should be "html" not "sh".

@lunson Why is the code class html when the content here is not HTML?  It's shell script; is there a class for this we could use instead?  Is there a list of the possible classes for the <code> element?

@rleigh-codelibre It was just a style name that stuck. You can call the class whatever you want, but be sure to change the CSS selector in openmicroscopy.css (line 57) to match. For example, if you change it to <code class="shell-script">, the selector in the CSS file should be changed from code.html to code.shell-script.

@lunson Ah, OK.  I was assuming this hooked into the jekyll Rouge or Markdown code formatting/highlighting stuff.

Should all be fixed up now.

Thanks @rleigh-codelibre!

authors: lunson rleigh-codelibre sbesson


text:
如何获取每一层卷积的scale和激活的scale

输出的json文件中看不太懂是啥意思，我想拿到每一层卷积的scale和每一层激活的scale，这个该怎么获取

from ppq import QuantableOperation
for opname, op in quantized.operations.items():
    if isinstance(op, QuantableOperation):
        print(
            opname,
            op.type,
            op.config.input_quantization_config[0].scale,
            op.config.output_quantization_config[0].scale
        )

# export quantized graph.
export_ppq_graph(graph=quantized, platform=TargetPlatform.ONNXRUNTIME,
                 graph_save_to='Output/quantized(onnx).onnx',
                 config_save_to='Output/quantized(onnx).json',
                 quantized_param=False)

ok，感谢回复！！

authors: SSriven ZhangZhiPku

repo: openppl-public/ppq


text:
Update/doc concepts

Describe your changes
mention api file formats specification in concepts page
Checklist before requesting a review

[x] I have performed a self-review of my code

Check the correct box. Does this PR contain:

[ ] Breaking changes
[ ] New functionality
[ ] Major changes
[x] Minor changes
[ ] Bug fixes

[ ] Proposed changes are described in the CHANGELOG.md

[ ] CI Preview succeeds and looks good!

Already merged #280

repo: openproblems-bio/website


text:
App error when changing register. Fix issue #86

The method collect doesn't exist in the class Parameters

Fix #86

repo: openregister/managing-registers


text:
StringOutOfBoundsException on Spring Boot's ApplicationContextAssert

This one is in spring boot. ApplicationContextAssert produces a string index out of bounds exception parsing an annotation.

Exception in thread "main" java.lang.StringIndexOutOfBoundsException: begin 20623, end 18717, length 21274
at java.base/java.lang.String.checkBoundsBeginEnd(String.java:3319)
at java.base/java.lang.String.substring(String.java:1874)
at org.openrewrite.java.Java11ParserVisitor.visitAnnotation(Java11ParserVisitor.java:101)

Fix in rewrite-java-8: https://github.com/openrewrite/rewrite-java-8/commit/c8e18f2c949e0a1b8147858c1ef387d5941c2a7a

repo: openrewrite/rewrite


text:
Adding add hoc taint tracking support for local flow

@pway99  and I did some pair programming on this one to add support for ad-hoc taint tracking leveraging data flow analysis as a basis.
This adds a new API to LocalFlowSpec called isAdditionalFlowStep. It takes an existing flow-step in the graph and offers a potential next flow step. The method can then decide if the offered potential next flow step should be considered a valid next flow step in the graph.

thanks @JLLeitschuh


text:
Add scope to injected class

What's changed?
This is a recipe to detect injected classes and add a Dependent class anotation to that class if there isn't one already present
What's your motivation?
The need was prompted while trying to migrate jave EE projects to quarkus. quarkus  doesn't use beans.xml and needs bean scope to create a bean
Anything in particular you'd like reviewers to focus on?
The unit test fails, because when the test classes are instantiated the parser doesn't create the member variable's @Inject annotation meaning that the recipe doesn't fire. I'm creating this PR to raise an issue as to why this happens
Apologies in advance if it's a coding error on my part!
Anyone you would like to review specifically?

Have you considered any alternatives or workarounds?

Any additional context

Checklist

[ ] I've added unit tests to cover both positive and negative cases
[ ] I've added the license header to any new files through ./gradlew licenseFormat
[ ] I've used the IntelliJ auto-formatter on affected files
[ ] I've updated the documentation (if applicable)

Hi @m-brophy, seems the unit test is failing, can you double-check?
and also, should this recipe be part of jakarta-ee and move to repo rewrite-migrate-java?
like this https://github.com/openrewrite/rewrite-migrate-java/blob/main/src/main/resources/META-INF/rewrite/jakarta-ee-9.yml
Also, it's missing license headers, you can run ./gradlew lF to generate license headers automatically.

Hi @kunli2 , I raised the PR so I could raise an issue as to why the unit test was failing, here it is - https://github.com/openrewrite/rewrite/issues/3338
The test is failing because the test framework doesn't include the member variable annotation in the class it creates from the test spec, and I think that's a bug

Should this PR possibly be moved to rewrite-migrate-java?

moving this to rewrite-migrate-java so closing this PR

authors: knutwannheden kunli2 m-brophy


text:
Also add link to CVMFS client install to the Data/CVMFS section of the TOC

I found it confusing that the CVMFS section of the docs did not have instructions on installing the CVMFS client.

Since the CVMFS client is for WNs, I'd prefer if we just renamed HTTP & CVMFS to HTTP

How about "HTTP and OASIS"?

Sure, either way works for me

authors: brianhlin matyasselmeci

repo: opensciencegrid/docs


text:
NavaThread exception

Reference Issues/PRs
What does this implement/fix? Explain your changes.

NavaThread exception bug fixed

Any other comments?
Local tests on OSs

[x] macOS

[x] Sonoma

[x] Windows

[x] Windows 11

[ ] Linux

[ ] Ubuntu 20.04

LGTM. Just a point I wanted to mention here for future reference. Since we are using WINSOUND API, but call alsa directly from the system, they still have difference. For example in MacOS, for async mode, when running Winsound, it gave the error and process is done, but when calling Alsa, it stuck and needed a Ctrl + C to exit.
You can merge it, I just don't merge it so that you see my message here.

What's the meaning of stuck? It's really weird! This process run on another thread. Can you provide a reproducible example?

LGTM. Just a point I wanted to mention here for future reference. Since we are using WINSOUND API, but call alsa directly from the system, they still have difference. For example in MacOS, for async mode, when running Winsound, it gave the error and process is done, but when calling Alsa, it stuck and needed a Ctrl + C to exit.
You can merge it, I just don't merge it so that you see my message here.

What's the meaning of stuck? It's really weird! This process run on another thread. Can you provide a reproducible example?

Yes, checkout this on Ubuntu (for example) and see the differnece:
play("path/to/file.wav", engine=Engine.WINSOUND)

and
play("path/to/file.wav", engine=Engine.AFPLAY)

We decided to fix the raised issue in a separate PR.

authors: sadrasabouri sepandhaghighi

repo: openscilab/nava


text:
Fields display corruption

This has happened since switching to Kicad 7.0. I have components that have a certain number of custom fields and it seems that iBom cannot cope with it. I ran some tests with a simple BOM and worked out that if I remove enough fields, the corruption disappears. Basically, the number of custom fields should not exceed 9. This is not something that used to happened when I used Kicad 6 and probably an older version of iBom.

I believe this was fixed in 3302982ea7918ce4544ec6c3b9f0ce0350b74f23
Can you try it? You will have to uninstall the plugin from kicad's plugin manager and follow manual installation instructions in wiki.

Excellent, thank you for your quick response. I fixed the lines manually in the code for now and it works fine.

repo: openscopeproject/InteractiveHtmlBom


text:
v2.2.1 Image load aborted

I was using openseadragon 2.1.0 version with IIP Image Server. Everything was fine but
i faced, i see tile edge in jp2 files so i updated to 2.2.1..
And it gives an error :
GET https://www.xxxx.com/fcgi-bin/iipsrv.fcgi_files/9/0_0.jpg 404 (Not Found)
Tile a.Tile failed to load: /fcgi-bin/iipsrv.fcgi_files/9/0_0.jpg - error: Image load aborted
0_0.jpg:1 GET https://www.xxxx.com/fcgi-bin/iipsrv.fcgi_files/8/0_0.jpg 404 (Not Found)
Tile a.Tile failed to load: /fcgi-bin/iipsrv.fcgi_files/8/0_0.jpg - error: Image load aborted
var viewportHeight = $(window).height() - $(".headerbar").height();
        $("#openseadragon1").css("height", viewportHeight);

 viewer = OpenSeadragon({
            id: "openseadragon1",
            prefixUrl: "/images/openseadragon/",
            showNavigator: true,
            navigatorPosition:   "BOTTOM_RIGHT",
            crossOriginPolicy: 'Anonymous',
            zoomInButton:   "zoom-in",
            zoomOutButton:  "zoom-out",
            homeButton:     "home",
            fullPageButton: "full-page",
            tileSources : viewer_image,
            maxZoomLevel : 9999
        });

        viewer.addHandler("tile-drawn", function(event) {
            $("#loading").hide();
        });

And viewer_image is : viewer_image = '/fcgi-bin/iipsrv.fcgi?Deepzoom=/images/'+current_plink+'.jp2.dzi';
current_plink come from ajax method, after jquery ajax method success, i am calling openseadragon init.
Any advice ?

It's possible you're getting https://github.com/openseadragon/openseadragon/pull/1199... can you try building the latest from master?
We're close to a new release, but not quite ready...

@iangilman i build with latest from master. But i got a new error:
OpenSeaDragon.Viewer is undefined and OpenSeaDragon.setString is not a function..
Did this change ?

Those still exist... perhaps it's a capitalization issue? It should be OpenSeadragon not OpenSeaDragon.

Have you solved it, can you share the solution?

authors: ghost iangilman linruicheng1997 ozgunlu

repo: openseadragon/openseadragon


text:
Selection not working after first selection - Chrome + tablet touch mode

There is a issue which happens after a image selection has been made.
To reproduce:

start chome browser
open webpage https://picturae.github.io/openseadragonselection/
open chrome developer tools (More tools / Developer tools)
developer tools - select the Toogle device toolbar to set tablet touch mode
webpage - select the tool selection icon (empty square)
create a selection on the image
confirm or cancel the selection
try to create a new selection (this will not be possible)

Sounds like a bug in https://github.com/picturae/openseadragonselection/ ...you should file an issue over there. Go ahead and link it from here as well, in case someone here has any ideas. I'm not familiar enough with that plugin to know. I assume you've tried it on actual touch devices as well? Are there any errors on the console?

No errors appear on the console and this defect also appears on Android phones and tablets.
I have create a defect on the selection plugin GitHub -https://github.com/picturae/openseadragonselection/issues/35

Issue is fixed by on cancel calling
this.outerTracker.setTracking(false); this.outerTracker.setTracking(true);
So I am not sure what needs to be changed but it solves the problem

Interesting... So something's getting hung up in the tracker. I'm not sure if this is a bug in OpenSeadragon or in the plugin, but it might be OSD, so I'll mark this as a bug here.

Taking a further look into the code it looks like its likely an issue from the mousetracker.js in openseadragon

@sekwah41 Cool... Any thoughts about what the fix would be?

@iangilman I can take a better look at it this weekend. I am currently busy with some uni work. Hopefully I can try to find what specifically is triggering this. I mean the drag event data seems to be the same other than the name being touch rather than mouse so I cant see why that could cause it. A lot of these issues are caused by mobile browsers being different like IOS (because stupid reasons) but the issue seems to be caused directly by the different events being triggered and that alone which I cant see as to why that would be the case.
Though I can help narrow down the cause at least hopefully by debugging it the same way I found that fix.

@sekwah41 sounds good... I agree it can get complicated with browser differences! Thank you for looking into it :)


text:
d3 objects disappearing on zoom/move

I've added a number of d3 shapes (circles and rectagles) as an overlay to a rather large image (the original file was ~2GB) and when zooming or moving around some of them flicker and/or disappear. Is this a known issue?

I've observed it on some browsers; I think Firefox does this more than Chrome, for instance. At any rate, I think it has to do with the scale of the coordinate system you're using. Did you stick with the default OSD coordinate system where the width of your image is 1? You might try bumping that up to 1000 or something and see if that affects the issue (of course remember to update the coordinates for your d3 shapes).

I'm marking this as a bug, although I think it's more of a browser limitation... I'm not sure what we can do beyond recommending changing the coordinates for your project. I'd love to hear ideas though!

Yeah, I should have thought to try this it in a different browser.  Chrome works perfecftly, so it's probably a Safari issue.  I was using default OSD coordinates, nothing fancy:
        var overlay = viewer.svgOverlay();

        for (var i = 0; i < points.length; i++) {
            var d3Circle = d3.select(overlay.node()).append("circle")
                .style('fill', 'rgba(255,0,0,0.25)')
                .attr("id", "svg-circle-" + i)
                .attr("cx", (points[i][0] /width))
                .attr("cy", (points[i][1] / height))
                .attr("r", 0.005)
                .attr("class", "svg-circle")
        }

        for (var i = 0; i < lines.length; i++) {
            var d3Line = d3.select(overlay.node()).append("line")
                .style('stroke', 'rgba(0,255,0,0.25)')
                .attr("id", "svg-line-" + i)
                .attr("x1", lines[i][0] / width)
                .attr("y1", lines[i][1] / height)
                .attr("x2", lines[i][2] / width)
                .attr("y2", lines[i][3] / height)
                .attr("stroke-width", 0.001)
                .attr("class", "svg-line")

        }

Where width and height are the width/height of the full image in pixels and the point/line values are also in pixels.  So that should scale everything between 0 and 1.
I even set up a toggle to show/hide the "svg-line" and "svg-circle" classes and this still wouldn't make them show up, so I'm thinking maybe the zIndex of the image tiles are somehow getting in front of the svgs?

The first thing to try is scaling up your coordinate system. When you open your image, give it a width of 1000 or something, and then scale your overlays as appropriate. My theory is that it has to do with rounding in the transform math.
That said, if you do find something related to z-index, I'd love to know about it!

I've experienced the same issue. Actually, it can be observed on the site: https://openseadragon.github.io/examples/ui-overlays/ (try zooming in and then drag the image; the blue frame will wobble).
The problem is that browsers (at least chrome) don't handle sub-pixel offsets (top, left, etc). However, they do handle sub-pixel "transform:translate" well. I've tested the hypothesis by setting translate instead of top/left offsets here, and it fixed the issue.
If somebody with good expertise with OSD code could implement this change (taking into account possible rotations), that would be amazing.

I hope it's okay to comment on this many years later. I had this same issue, and there aren't many reports about it.
All browsers have a hard limit on rendering svgs very far zoomed-in. Chrome/Firefox that limit is around 1e-6 for things like stroke-width. On Safari, there is a hard limit for stroke-width at 0.001, below which the path just disappears.
I made a demo at https://codepen.io/robbykraft/pen/LYMJKmE and filed a report with Apple, it would be nice if they could match the 1e-6 limit.
So, it's not a bug in Safari, it's just Safari's limit. And the work around is as you mention @iangilman to enlarge the viewBox so you are not working with such small numbers. I'm bet you're correct about the rounding/transform math too.

@robbykraft Thank you for adding this additional detail! Always welcome ❤

authors: EvilTosha iangilman robbykraft travisdesell

repo: openseadragon/svg-overlay


text:
Remove unused systemd service files

Is your feature request related to a problem? Please describe.
I was looking into the service files in this repo and was surprised that they don't match what got installed on the system.
https://github.com/opensearch-project/OpenSearch/blob/main/distribution/packages/src/common/systemd/opensearch.service
The actual file seems to originate from the build repo here:
https://github.com/opensearch-project/opensearch-build/blob/main/scripts/pkg/service_templates/opensearch/usr/lib/systemd/system/opensearch.service
Describe the solution you'd like
Remove the unused service files to reduce potential confusion.

Hi @peterzhuamazon Can you take a look at this? Wondering if the other service file is required starting min distribution independently of the distribution.
Thanks!

authors: Earlopain gaiksaya

repo: opensearch-project/OpenSearch


text:
IpFieldMapper should use IndexOrDocValuesQuery where possible

Is your feature request related to a problem? Please describe.
While going through the IpFieldMapper class and looking through IpFieldMapperType I noticed that the termQuery, termsQuery, and rangeQuery all use underlying lucene index queries. The documentation also incorrectly points to the fact that IP address do not have doc_values enabled by default. This is incorrect, ref: https://github.com/opensearch-project/OpenSearch/blob/b78176afefd8c09a19de6bc52907b40c8c4fedf2/server/src/main/java/org/opensearch/index/mapper/IpFieldMapper.java#L89
Describe the solution you'd like
Wrap all three queries in IndexOrDocValuesQuery and add checks to ensure that we return the index query if the field is only indexed and doc_values query if we only have doc_values enabled.
Describe alternatives you've considered
Alternative is to leave this as is. But there is potentially a lot of performance improvement to be had. Consider a query that looks like
{
  query: {
  "range":{
  "timestamp: {
      "from" :xyz,
       "to": xyz
    }
   },
"terms": {
"ipaddress" :["0.0.0.0", "1.1.1.1"]
}
}
}

We could let the range on the timestamp drive the query and use the doc_values to match the documents for the terms in the ipaddress.
Additional context
#7057

Hi @harshavamsi , will this require documentation for 2.12? If so, can you please create a doc issue, let me know who will be responsible for the doc PR, and add this to the unified tracker project? Thank you!

Hi, are we on track for this to be released in 2.12 ?

@reta Is there are reason we should move this to 3.0? Given the PR is already out by @vamshin we might be able to close it in before 2.12?

@reta Is there are reason we should move this to 3.0? Given the PR is already out by @vamshin we might be able to close it in before 2.12?

Yeah, I think so, the issue is tagged to 2.12.0 (and 3.0.0 surely) :)

@reta Does this require documentation for 2.12?

@reta Does this require documentation for 2.12?

I believe there are no user facing changes here