fr(Drag-Drop): Setting z-index

In source code I see that z-index of preview is hard coded: https://github.com/angular/components/blob/master/src/cdk/drag-drop/drag-ref.ts
extendStyles(preview.style, {
      // It's important that we disable the pointer events on the preview, because
      // it can throw off the `document.elementFromPoint` calls in the `CdkDropList`.
      pointerEvents: 'none',
      // We have to reset the margin, because it can throw off positioning relative to the viewport.
      margin: '0',
      position: 'fixed',
      top: '0',
      left: '0',
      zIndex: '1000'
    });

Problem is that I'm using drag-drop feature n bootstrap modal which has z-index 1050 - so I have to change it, but I cannot.

Yeah, we use cdk drag and drop in a bootstrap dialog, and we had to configure the all the variables for z-index in bootstrap to work correctly.


Compilation with cuda.jit randomly fails with segfault

[X] I have tried using the latest released version of Numba (most recent is
visible in the change log (https://github.com/numba/numba/blob/master/CHANGE_LOG).
[X] I have included below a minimal working reproducer (if you are unsure how
to write one see http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports).

I'm porting a code over to python and using numba with cuda. I'm getting random segfaults that appear to be during the cuda compilation. It usually runs, but maybe one out of 5 times it segfaults.
This is an example that (sometimes) reproduces the problem.
import numpy as np
import math
from numba import cuda, float32

NUM_SAMPLES = 2
NUM_THREADS = 128

@cuda.jit
def computeValues(data_input, angle, total_size):
  threadID = cuda.threadIdx.x + cuda.blockIdx.x * cuda.blockDim.x
  if threadID >= total_size:
    return

  s1 = cuda.local.array(shape=(NUM_SAMPLES,4), dtype=float32)

  for i in range(NUM_SAMPLES):
    for j in range(4):
      s1[i,j] = data_input[threadID,i,j]

    s1[i,2] = math.sin(angle) * s1[i,1] + math.cos(angle) * s1[i,2]

if __name__ == "__main__":
    total_size = 200

    data_input = np.zeros((total_size, NUM_SAMPLES, 4), dtype='float32')

    BlockSize = int(math.ceil(total_size / NUM_THREADS))

    num_gpu = len(cuda.gpus)
    print(f"number of CUDA devices: {num_gpu}")
    cuda.select_device(2)

    for value in [280.0, 285.0, 290.0]:
      print(f"value = {value} starting\n")
      computeValues[BlockSize, NUM_THREADS](data_input, 0.0, total_size)

Most times it works as expected:
$ PYTHONFAULTHANDLER=1 python3 ../test.py import numpy as np
number of CUDA devices: 4
value = 280.0 starting

value = 285.0 starting

value = 290.0 starting

Other times it fails like this:
$ PYTHONFAULTHANDLER=1 python3 ../test.py
number of CUDA devices: 4
value = 280.0 starting

Fatal Python error: Segmentation fault

Current thread 0x00007f169eaf4740 (most recent call first):
  File "/lib/python3.7/site-packages/numba/cuda/cudadrv/nvvm.py", line 230 in compile
  File "/lib/python3.7/site-packages/numba/cuda/cudadrv/nvvm.py", line 512 in llvm_to_ptx
  File "/lib/python3.7/site-packages/numba/cuda/compiler.py", line 451 in get
  File "/lib/python3.7/site-packages/numba/cuda/compiler.py", line 480 in get
  File "/lib/python3.7/site-packages/numba/cuda/compiler.py", line 603 in bind
  File "/lib/python3.7/site-packages/numba/cuda/compiler.py", line 862 in compile
  File "/lib/python3.7/site-packages/numba/cuda/compiler.py", line 843 in specialize
  File "/lib/python3.7/site-packages/numba/cuda/compiler.py", line 832 in __call__
  File "../test.py", line 38 in <module>
Segmentation fault (core dumped)

It looks like this is happening during the cuda compilation. Is there anything I can change in my code to fix this?

@gtsmisc thanks for submitting this, I am having trouble reproducing this now. I have the following. GPUs:
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 410.79       Driver Version: 410.79       CUDA Version: 10.0     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  Tesla K40c          Off  | 00000000:17:00.0 Off |                    0 |
| 25%   49C    P0    66W / 235W |      0MiB / 11441MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  GeForce GTX 1080    Off  | 00000000:65:00.0 Off |                  N/A |
| 34%   51C    P0    37W / 180W |      0MiB /  8118MiB |      4%      Default |
+-------------------------------+----------------------+----------------------+

And I am using the following OS:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.4 LTS"

And these CUDA libraries:
CUDA Librairies Test Output:
Finding cublas from System
        named  libcublas.so.10.0.130
        trying to open library...       ok
Finding cusparse from System
        named  libcusparse.so.10.0.130
        trying to open library...       ok
Finding cufft from System
        named  libcufft.so.10.0.145
        trying to open library...       ok
Finding curand from System
        named  libcurand.so.10.0.130
        trying to open library...       ok
Finding nvvm from System
        named  libnvvm.so.3.3.0
        trying to open library...       ok

And Numba from today's master at 0.51.0dev0-317-gd3b7ea1344.
I'm going to run it in the following loop now for some time:
while true ; do python foo003.py && [ $? != 0 ] && echo "breaking" && break ; done ;

to see if I can reproduce it. But in the meantime, it would be good for you to submit the output of numba -s so that we can perhaps diagnose this further.

I can reproduce the error. There appears to be a bad memory access going on in llvmlite, which I suspect is resulting in bad IR going to NVVM:
==20397== Conditional jump or move depends on uninitialised value(s)
==20397==    at 0x182B5AE1: llvm::ConstantExpr::getGetElementPtr(llvm::Type*, llvm::Constant*, llvm::ArrayRef<llvm::Value*>, bool, llvm::Optional<unsigned int>, llvm::Type*) (in /home/gmarkall/numbadev/llvmlite/llvmlite/binding/libllvmlite.so)
==20397==    by 0x1743FC97: llvm::LLParser::ParseValID(llvm::ValID&, llvm::LLParser::PerFunctionState*) (in /home/gmarkall/numbadev/llvmlite/llvmlite/binding/libllvmlite.so)
==20397==    by 0x1743CF89: llvm::LLParser::ParseGlobalValue(llvm::Type*, llvm::Constant*&) (in /home/gmarkall/numbadev/llvmlite/llvmlite/binding/libllvmlite.so)
==20397==    by 0x1743D181: llvm::LLParser::ParseGlobalTypeAndValue(llvm::Constant*&) (in /home/gmarkall/numbadev/llvmlite/llvmlite/binding/libllvmlite.so)
==20397==    by 0x1743D1F3: llvm::LLParser::ParseGlobalValueVector(llvm::SmallVectorImpl<llvm::Constant*>&, llvm::Optional<unsigned int>*) (in /home/gmarkall/numbadev/llvmlite/llvmlite/binding/libllvmlite.so)
==20397==    by 0x1743D5B3: llvm::LLParser::ParseValID(llvm::ValID&, llvm::LLParser::PerFunctionState*) (in /home/gmarkall/numbadev/llvmlite/llvmlite/binding/libllvmlite.so)
==20397==    by 0x1743CF89: llvm::LLParser::ParseGlobalValue(llvm::Type*, llvm::Constant*&) (in /home/gmarkall/numbadev/llvmlite/llvmlite/binding/libllvmlite.so)
==20397==    by 0x17455818: llvm::LLParser::ParseGlobal(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, llvm::SMLoc, unsigned int, bool, unsigned int, unsigned int, bool, llvm::GlobalValue::ThreadLocalMode, llvm::GlobalValue::UnnamedAddr) (in /home/gmarkall/numbadev/llvmlite/llvmlite/binding/libllvmlite.so)
==20397==    by 0x174562C1: llvm::LLParser::ParseNamedGlobal() (in /home/gmarkall/numbadev/llvmlite/llvmlite/binding/libllvmlite.so)
==20397==    by 0x174582CB: llvm::LLParser::ParseTopLevelEntities() (in /home/gmarkall/numbadev/llvmlite/llvmlite/binding/libllvmlite.so)
==20397==    by 0x17458400: llvm::LLParser::Run() (in /home/gmarkall/numbadev/llvmlite/llvmlite/binding/libllvmlite.so)
==20397==    by 0x1740D45C: llvm::parseAssemblyInto(llvm::MemoryBufferRef, llvm::Module*, llvm::ModuleSummaryIndex*, llvm::SMDiagnostic&, llvm::SlotMapping*, bool, llvm::StringRef) (in /home/gmarkall/numbadev/llvmlite/llvmlite/binding/libllvmlite.so)

Actually the valgrind error might gave been spurious / a red herring. I notice that prior to optimization, there are no memset intrinsics in the IR. However, after optimization, we have:
  call void @llvm.memset.p0i8.i64(i8* nonnull align 4 %0, i8 0, i64 32, i1 false)

The LLVM 3.4 IR specification (upon which NVVM is based) expects 5 parameters to the memset instrinsic (ref):
declare void @llvm.memset.p0i8.i32(i8* <dest>, i8 <val>,
                                   i32 <len>, i32 <align>, i1 <isvolatile>)
declare void @llvm.memset.p0i8.i64(i8* <dest>, i8 <val>,
                                   i64 <len>, i32 <align>, i1 <isvolatile>)

Whereas LLVM 9 only has 4 arguments for memset (ref):
declare void @llvm.memset.p0i8.i32(i8* <dest>, i8 <val>,
                                   i32 <len>, i1 <isvolatile>)
declare void @llvm.memset.p0i8.i64(i8* <dest>, i8 <val>,
                                   i64 <len>, i1 <isvolatile>)

My understanding right now is that NVVM is parsing the optimized IR, but its last parameter is junk, leading to an occasional segfault.
Also, the segfault goes away if I disable optimization prior to sending the IR to NVVM, as in https://github.com/numba/numba/issues/5576#issuecomment-646548553
I think this is another argument for not optimizing the IR with llvmlite's LLVM prior to sending the IR to NVVM.

I can confirm that disabling the optimization as described above gets rid of the segfault for me. What are the consequences of doing that? I see in the comments on the optimization code that it is a work around for another bug.
output of numba -s is below
__Time Stamp__
Report started (local time)                   : 2020-07-23 12:11:40.035898
UTC start time                                : 2020-07-23 17:11:40.035904
Running time (s)                              : 0.912693

__Hardware Information__
Machine                                       : x86_64
CPU Name                                      : broadwell
CPU Count                                     : 40
Number of accessible CPUs                     : 32
List of accessible CPUs cores                 : 0-39
CFS Restrictions (CPUs worth of runtime)      : None

CPU Features                                  : 64bit adx aes avx avx2 bmi bmi2
                                                cmov cx16 cx8 f16c fma fsgsbase
                                                fxsr invpcid lzcnt mmx movbe
                                                pclmul popcnt prfchw rdrnd rdseed
                                                rtm sahf sse sse2 sse3 sse4.1
                                                sse4.2 ssse3 xsave xsaveopt

Memory Total (MB)                             : 515889
Memory Available (MB)                         : 506085

__OS Information__
Platform Name                                 : Linux-3.10.0-1127.13.1.el7.x86_64-x86_64-with-redhat-7.8-Maipo
Platform Release                              : 3.10.0-1127.13.1.el7.x86_64
OS Name                                       : Linux
OS Version                                    : #1 SMP Fri Jun 12 14:34:17 EDT 2020
OS Specific Version                           : ?
Libc Version                                  : glibc 2.10

__Python Information__
Python Compiler                               : GCC 7.3.0
Python Implementation                         : CPython
Python Version                                : 3.7.7
Python Locale                                 : en_US.UTF-8

__LLVM Information__
LLVM Version                                  : 9.0.1

__CUDA Information__
CUDA Device Initialized                       : True
CUDA Driver Version                           : 10010
CUDA Detect Output:
Found 4 CUDA devices
id 0    b'GeForce GTX TITAN X'                              [SUPPORTED]
                      compute capability: 5.2
                           pci device id: 0
                              pci bus id: 2
id 1    b'GeForce GTX TITAN X'                              [SUPPORTED]
                      compute capability: 5.2
                           pci device id: 0
                              pci bus id: 3
id 2    b'GeForce GTX TITAN X'                              [SUPPORTED]
                      compute capability: 5.2
                           pci device id: 0
                              pci bus id: 131
id 3    b'GeForce GTX TITAN X'                              [SUPPORTED]
                      compute capability: 5.2
                           pci device id: 0
                              pci bus id: 132
Summary:
	4/4 devices are supported

CUDA Librairies Test Output:
Finding cublas from Conda environment
	named  libcublas.so.10.0.130
	trying to open library...	ok
Finding cusparse from Conda environment
	named  libcusparse.so.10.0.130
	trying to open library...	ok
Finding cufft from Conda environment
	named  libcufft.so.10.0.145
	trying to open library...	ok
Finding curand from Conda environment
	named  libcurand.so.10.0.130
	trying to open library...	ok
Finding nvvm from Conda environment
	named  libnvvm.so.3.3.0
	trying to open library...	ok
Finding libdevice from Conda environment
	searching for compute_20...	ok
	searching for compute_30...	ok
	searching for compute_35...	ok
	searching for compute_50...	ok

__ROC information__
ROC Available                                 : False
ROC Toolchains                                : None
HSA Agents Count                              : 0
HSA Agents:
None
HSA Discrete GPUs Count                       : 0
HSA Discrete GPUs                             : None

__SVML Information__
SVML State, config.USING_SVML                 : False
SVML Library Loaded                           : False
llvmlite Using SVML Patched LLVM              : True
SVML Operational                              : False

__Threading Layer Information__
TBB Threading Layer Available                 : True
+-->TBB imported successfully.
OpenMP Threading Layer Available              : True
+-->Vendor: GNU
Workqueue Threading Layer Available           : True
+-->Workqueue imported successfully.

__Numba Environment Variable Information__
None found.

__Conda Information__
Conda Build                                   : not installed
Conda Env                                     : 4.8.3
Conda Platform                                : linux-64
Conda Python Version                          : 3.7.7.final.0
Conda Root Writable                           : True

__Installed Packages__
_libgcc_mutex             0.1                        main
blas                      1.0                         mkl
ca-certificates           2020.6.24                     0
certifi                   2020.6.20                py37_0
cffi                      1.14.0           py37he30daa8_1
chardet                   3.0.4                 py37_1003
conda                     4.8.3                    py37_0
conda-package-handling    1.6.1            py37h7b6447c_0
cryptography              2.9.2            py37h1ba5d50_0
cudatoolkit               10.0.130                      0
cudnn                     7.6.5                cuda10.0_0
cupy                      6.0.0            py37hc0ce245_0
fastrlock                 0.4              py37he6710b0_0
h5py                      2.10.0           py37hd6299e0_1
hdf5                      1.10.6               hb1b8bf9_0
idna                      2.9                        py_1
intel-openmp              2020.1                      217
ld_impl_linux-64          2.33.1               h53a641e_7
libedit                   3.1.20181209         hc058e9b_0
libffi                    3.3                  he6710b0_1
libgcc-ng                 9.1.0                hdf63c60_0
libgfortran-ng            7.3.0                hdf63c60_0
libllvm9                  9.0.1                h4a3c616_1
libstdcxx-ng              9.1.0                hdf63c60_0
llvmlite                  0.33.0           py37hc6ec683_1
mkl                       2020.1                      217
mkl-service               2.3.0            py37he904b0f_0
mkl_fft                   1.1.0            py37h23d657b_0
mkl_random                1.1.1            py37h0573a6f_0
nccl                      1.3.5                cuda10.0_0
ncurses                   6.2                  he6710b0_1
numba                     0.50.1           py37h0573a6f_1
numpy                     1.18.5           py37ha1c710e_0
numpy-base                1.18.5           py37hde5b4d6_0
openssl                   1.1.1g               h7b6447c_0
pip                       20.0.2                   py37_3
pycosat                   0.6.3            py37h7b6447c_0
pycparser                 2.20                       py_0
pyopenssl                 19.1.0                   py37_0
pysocks                   1.7.1                    py37_0
python                    3.7.7                hcff3b4d_5
readline                  8.0                  h7b6447c_0
requests                  2.23.0                   py37_0
ruamel_yaml               0.15.87          py37h7b6447c_0
setuptools                46.4.0                   py37_0
six                       1.14.0                   py37_0
sqlite                    3.31.1               h62c20be_1
tbb                       2020.0               hfd86e86_0
tk                        8.6.8                hbc83047_0
tqdm                      4.46.0                     py_0
urllib3                   1.25.8                   py37_0
wheel                     0.34.2                   py37_0
xz                        5.2.5                h7b6447c_0
yaml                      0.1.7                had09818_2
zlib                      1.2.11               h7b6447c_3

No errors reported.

__Warning log__
Warning (roc): Error initialising ROC: No ROC toolchains found.
Warning (roc): No HSA Agents found, encountered exception when searching: Error at driver init:
NUMBA_HSA_DRIVER /opt/rocm/lib/libhsa-runtime64.so is not a valid file path.  Note it must be a filepath of the .so/.dll/.dylib or the driver:
Warning (psutil): psutil cannot be imported. For more accuracy, consider installing it.

I don't expect any noticeable consequences - I'm working on a PR that disables optimization before sending to NVVM, but there are some test fails it causes that I need to work through. Will update this issue once I've made the PR.

BTW,  I believe the original nvvm bug it worked around is gone.

PR to fix is in #6030.

@gmarkall Thank you for your help. I appreciate it.

Now that #6030 is merged, this should be resolved.

Actually the valgrind error might gave been spurious / a red herring. I notice that prior to optimization, there are no memset intrinsics in the IR. However, after optimization, we have:
  call void @llvm.memset.p0i8.i64(i8* nonnull align 4 %0, i8 0, i64 32, i1 false)

The LLVM 3.4 IR specification (upon which NVVM is based) expects 5 parameters to the memset instrinsic (ref):
declare void @llvm.memset.p0i8.i32(i8* <dest>, i8 <val>,
                                   i32 <len>, i32 <align>, i1 <isvolatile>)
declare void @llvm.memset.p0i8.i64(i8* <dest>, i8 <val>,
                                   i64 <len>, i32 <align>, i1 <isvolatile>)

Whereas LLVM 9 only has 4 arguments for memset (ref):
declare void @llvm.memset.p0i8.i32(i8* <dest>, i8 <val>,
                                   i32 <len>, i1 <isvolatile>)
declare void @llvm.memset.p0i8.i64(i8* <dest>, i8 <val>,
                                   i64 <len>, i1 <isvolatile>)

My understanding right now is that NVVM is parsing the optimized IR, but its last parameter is junk, leading to an occasional segfault.
Also, the segfault goes away if I disable optimization prior to sending the IR to NVVM, as in #5576 (comment)
I think this is another argument for not optimizing the IR with llvmlite's LLVM prior to sending the IR to NVVM.

That was really helpful!


minor update for README.md

guys renamed redux-simple-router to react-router-redux, lets fix README.md

Thank you!


Display Auth Request on application

Background
A quick way to test out the configuration of an application or organization requires generating an Auth Request which triggers the behavior in ZITADEL. As a quality of life improvement and to reduce friction, we could display an Auth request already to the user with a minimum configuration.
Considerations

Use the minimum required parameters
Add a link to the docs for further customization
Dynamically add values for client_id and redirect_uri
I would suggest to always take the first redirect url from the configuration
Use response_type=code as default
Use scope=openid urn:zitadel:iam:org:id:{org_id} (org_id populated!) as default; I would explicitly configure the org_id to avoid confusion on why the branding / policies were not triggered

Acceptance criteria

[ ] Show minimum auth request in /ui/console/projects/{project_id}/apps/{app_id} > Urls
[ ] Required parameters are dynamically populated
[ ] Link to the docs for further reference and optional parameters

@hifabienne as discussed today. I think this would be a small and valuable QoL improvement for initial testing.

Upvote!

relates to #3573


Update existing comment

When alt-text is added (and the flagged problem is resolved) the comment placed by the workflow should be removed or hidden (and marked as resolved)

I love this idea!
Each comment should have a unique ID associated with it so we could try including that as a data attribute in the posted comment like @kendallgassner suggests. For example, @kendallgassner comment URL is https://github.com/github/accessibility-alt-text-bot/issues/31#issuecomment-1686597422. I believe<PHONE_NUMBER> is the unique issue comment ID.

Searching through each comment might be costly though.

Could we filter by bot author and comment body content?

Could we filter by bot author and comment body content?

O! genius 🧠!!


Implement Redis Channel for Webhook Delivery Status Updates

To enhance the visibility and tracking of webhook deliveries, we need a dedicated Redis channel for reporting the status of each webhook attempt. This channel will notify whether a webhook has been successfully delivered or if it failed, including relevant details for each event.
How?

Channel Creation: Set up a Redis channel dedicated to webhook status updates.

Payload Design: Create a standard message format for this channel that includes:

Webhook ID

Delivery status (Success or Failure)

Error message/details (in case of a failure)

Integration with Webhook Module: Modify the existing webhook sender module to publish status updates to this Redis channel after each delivery attempt.

Error Handling: Ensure that error details are accurately captured and published in case of delivery failure.

Configurability: Allow the name of the Redis channel to be parameterized through an environment variable. If not set, it should default to a pre-defined name.

Default Channel Name suggestion: webhook-status-updates🫣

Added in https://github.com/Transfa/sendhooks-engine/pull/38


[New Feature] Toggle Auto-run submissions

Provide a toggle option to organizers in competition settings, to enable/disable auto-run submissions.

By default auto-run submissions will be enabled
When this is disabled, all submissions submitted will have run submission button infront of them and by clicking this button, organizers can run the submission.

I do not understand. When the auto-rerun going to be triggered?

by default now we have auto-run which means that when you submit a submission it is added to the queue. When you turn this off (in this feature) then organizer can manually run it


Add tests of /_describe and /_list features

This prepares the FGA PR (which will add
another test).

rebasing


getThreadInfo imageSrc undefined

Trying to get chat thread icons displaying in an app and was getting undefined for the imageSrc, tracked it down to this line (43) in getThreadInfo.js:
threadData.image_src = userData != null && userData.thumbSrc != null ? userData.thumbSrc : threadData.imageSrc;
threadData.imageSrc doesn't seem to exist (plus would be pretty redundant if it did), pretty sure it is simply mean to be:
threadData.image_src = userData != null && userData.thumbSrc != null ? userData.thumbSrc : threadData.image_src;
With this change everything works as intended for my application.

Thanks for catching this and tracking down the cause.
For a while I was thinking thumbSrc looked wrong as well, but apparently not.
Can you submit a quick PR for this? Thanks again!


Gh action linter

Will wait for #9 to be merged into main to push this forward.

#12 Comes in with CI we can leverage. Closing PR in favor for that branch.


Why Raspberry Pi specific?

Hi,
First of all, thank you for this very nice crate, with a lot of features and a nicely documented.
But I wonder why did you make it Raspberry Pi specific?
The strength of an OS like Linux is to provide common abstraction layers to different hardware.
So using i2cdev, spidev, gpiochip interfaces should allow to use any Linux board like all the fruitPi boards based on different chips from Allwinner, Rockchip, Amlogic and so on.
From what I understand of your crate, mainly the GPIO interface through direct memory access and maybe the software PWM are using BCM specific interfaces.
Would it be possible to use gpiochip character device to interact with the GPIO and make this crate hardware agnostic or it would result in slower operations making the software PWM too slow?

Thanks for your question! You're correct in your assessment that directly accessing the GPIO registers is what mainly makes RPPAL Pi-specific. The other peripherals also implement Pi-specific code, but that's mostly to make the interface easier to use by automatically opening the correct device files and limiting features based on the Pi's capabilities.
I've looked into using gpiochip exclusively before. Besides potential performance problems, the main issues I encountered are gpiochip's interface preventing me from using it to read the mode of an unconfigured Pin or configure an IoPin when any of the Pi-specific alternative functions are involved, and not being able to configure the built-in pull-ups/pull-downs.
Requesting a handle requires providing a pin mode (if flags is kept 0, the pin mode will still be changed to Input). Since gpiochip's ioctl interface doesn't yet provide a way to set (or read) any of the ALT function modes, that means requesting a handle will always overwrite those modes unless I subsequently reset them through the registers, which ends up requiring a messy workaround that briefly changes the pin mode (which could cause issues), and would still require direct register access.
However, supporting other SBCs has been on my mind for a while, and I think it's something to consider after I'm done adding UART support, which is the last peripheral on my list. I don't have a clear solution for the above-mentioned issues, but other platforms might offer similar direct access to the registers (although that would still tie RPPAL to specific platforms), or gpiochip might receive Pi-specific changes in the future. I could leave the current implementation as is for the Pi, and add a generic gpiochip interface for other boards, provided those won't have the same issues with gpiochip as I ran into on the Pi.

Ok, tank you for your detailed answer.
I see your pitfalls and like your aim to open your crates to other boards.
Out of curiosity, why do you need to read the current config of a pin?
To check that it is not already in use before using it?
In that case, the kernel should know that the pin is used by a certain module and gpiochip should report it. But from what I remember while trying it, it was not always the case.
I am not sure of the actual code path of a gpiochip call within the kernel but do you know if the overhead is still high compared to direct memory access?

A nice example where reading the current pin mode is useful is the gpio_status example in the examples directory, which displays the mode and logic level of all pins on the GPIO header. It behaves similarly to the gpio command line tool that's included in one of the Pi's packages (I think it's in wiringPi?). That would be impossible to do with gpiochip, because it would change any pin that's configured for one of the ALT functions (for instance, when you enable pins for I2C or SPI) and set those to Input. It wouldn't even be able to just skip those pins, because gpiochip has no way to indicate which pin is configured for something other than Input or Output.
I've also run into some issues when different applications try to open a pin through gpiochip simultaneously (see this comment). I could probably fix that with a workaround, but I stopped looking into it after I discovered the other issues.
I never got around to actually benchmarking gpiochip versus direct access. I know it'll be slower simply because of the additional calls, but it might still be an acceptable speed. If you come across any data, or end up doing a comparison yourself, I'd love to hear about the results.

Ok, thank you again for the details.
Indeed a benchmark would be nice to do.

Ok so for now I think that the best thing to do would be to create a new crate (I am not aware of an existing one) to replace rust-sysfs-gpio to use gpiochip interface.
And use it with rust-spidev and rust-i2cdev instead of your crate on other board while gpiochip do not provide the interfaces you need.
Did you ever try to reach out the libgpiod developer to expose your feature requests?

There are two gpiochip crates available on crates.io although I haven't tried them myself, so I don't know how well they work. Either way, replacing sysfs gpio is definitely a good idea, since that interface was deprecated a while ago and will disappear at some point.
Other than that, I think what you suggest is probably the best solution for now.
RPPAL doesn't use libgpiod. Instead, it directly interfaces with gpiochip through ioctl calls, which is where any changes would need to be made. I do know some people have already brought up missing support for configuring pull-ups/pull-downs after moving from sysfs gpio to gpiochip, and it's being worked on.
I'm not sure if anything is planned regarding Pi-specific ALT function mode support, but https://github.com/raspberrypi/linux/issues is probably the best place to bring that up as a platform-specific patch (for instance by adding additional flags) unless other platforms require similar support. For now, my current solution works fine for the Pi, so I haven't brought it up, but I'll look into it again once I start working on supporting other platforms.
Out of curiosity, is there a specific board you're working with, or are you just interested in platform-agnostic support in general?

Oh nice, I have never seen these crates before (but never really look for it). For my use case, the sysfs was sufficient.

Out of curiosity, is there a specific board you're working with, or are you just interested in platform-agnostic support in general?

I don't have any use case in mind right now and I use boards using different SoC that's why is it more the plaform-agnostic support in general.
I do not use Rust a lot yet but I have been following the rust-embedded progress and found your crate. It was well documented and seemed to provide a lot of features so I have checked if it was supporting other boards.
Anyway, it was a very instructive discussion. Thanks a lot for all the explanations and once again, congratulations for this crate.


Launching always first project in multiroot project

Issue Description
Code seems to be ingoring project I am launching using its launch.json . It always launches first project in the multiroot workspace.
Projects are azure functions with generated launch.json and tasks.json
Expected Behavior
Launch the project I selected.
Actual Behavior
Launches first project in multiroot project.
Environment information
VSCode version: 1.65.2
C# Extension: 1.24.1
Mono Information
        OmniSharp using built-in mono
Dotnet Information
.NET SDK (reflecting any global.json):
 Version:   6.0.102
 Commit:    49861cb924
Runtime Environment:
OS Name:     fedora
OS Version:  35
OS Platform: Linux
RID:         fedora.35-x64
Base Path:   /usr/lib64/dotnet/sdk/6.0.102/
Host (useful for support):
Version: 6.0.2
Commit:  839cdfb0ec
.NET SDKs installed:
3.1.416 [/usr/lib64/dotnet/sdk]
5.0.206 [/usr/lib64/dotnet/sdk]
6.0.102 [/usr/lib64/dotnet/sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 3.1.22 [/usr/lib64/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.9 [/usr/lib64/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.2 [/usr/lib64/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.1.22 [/usr/lib64/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.9 [/usr/lib64/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.2 [/usr/lib64/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET runtimes or SDKs:
https://aka.ms/dotnet-download

Visual Studio Code Extensions

Extension
Author
Version

armview
bencoleman
0.4.6

azure-account
ms-vscode
0.10.1

azure-pipelines
ms-azure-devops
1.195.0

azurecli
ms-vscode
0.5.0

csharp
ms-dotnettools
1.24.1

vscode-azureappservice
ms-azuretools
0.23.1

vscode-azurefunctions
ms-azuretools
1.6.0

vscode-azureresourcegroups
ms-azuretools
0.4.0

vscode-azurestorage
ms-azuretools
0.13.0

vscode-azurevirtualmachines
ms-azuretools
0.5.0

vscode-cosmosdb
ms-azuretools
0.18.1

vscode-docker
ms-azuretools
1.20.0

vscode-node-azure-pack
ms-vscode
0.2.1

vscodeintellicode
VisualStudioExptTeam
1.2.17

Thanks! Looks like you already opened an issue in the vscode-azurefunctions repo, which I think is where this belongs (https://github.com/microsoft/vscode-azurefunctions/issues/3077).
Closing as external.


Extension making Vscode hang

Summary:
I often notice that Vscode hangs for couple of seconds while typing or switching windows. Here is the debug data below. In case more info is needed please let me know

Issue Type: Bug
Extension Name: vscode-pull-request-github
Extension Version: 0.40.0
OS Version: Darwin x64 20.6.0
VS Code version: 1.67.0

{
	"messages": [
		{
			"type": 1,
			"message": "`remoteHub/pullRequest` is not a valid menu identifier",
			"extensionId": {
				"value": "GitHub.vscode-pull-request-github",
				"_lower": "github.vscode-pull-request-github"
			},
			"extensionPointId": "menus"
		}
	],
	"activationTimes": {
		"codeLoadingTime": 73,
		"activateCallTime": 0,
		"activateResolvedTime": 2321,
		"activationReason": {
			"startup": true,
			"extensionId": {
				"value": "GitHub.vscode-pull-request-github",
				"_lower": "github.vscode-pull-request-github"
			},
			"activationEvent": "*"
		}
	},
	"runtimeErrors": [
		{
			"name": "TypeError",
			"message": "Cannot read properties of undefined (reading 'findIndex')"
		},
		{
			"name": "TypeError",
			"message": "Cannot read properties of undefined (reading 'findIndex')"
		},
		{
			"name": "TypeError",
			"message": "Cannot read properties of undefined (reading 'findIndex')"
		}
	],
	"runningLocation": {
		"affinity": 0,
		"kind": 1
	}
}

@rahmathu next time you see this would you be able to take a CPU profile? https://github.com/microsoft/vscode/wiki/Performance-Issues#profile-the-running-extensions

@alexr00 : Thanks, let me do this and get back with the requested information

Also, do you by chance have the vim extension installed? Maybe related: https://github.com/microsoft/vscode-pull-request-github/issues/3562

@alexr00 : I will share the info you have requested. I dont have the vim extension installed as i don't use vim at all.

@alexr00 : I think this Pull requests extension is not working good for me. All my queries are failing and i see this error below "remoteHub/pullRequest is not a valid menu identifier". I am not sure if it's related to this one or different. Can you please let me know what this error means and why my queries wont work ?
Here are the Non working queries from the extension but work on the github UI
    "githubIssues.queries": [
        {
            "label": "My Issues",
            "query": "default"
        },
        {
            "label": "Created Issues",
            "query": "author:rahmathu state:open repo:${owner}/${repository} sort:created-desc"
        },
        {
            "label": "Recent Issues",
            "query": "state:open repo:${owner}/${repository} sort:updated-desc"
        }
    ],
    "githubPullRequests.queries": [
        {
            "label": "Waiting For My Review",
            "query": "is:open review-requested:rahmathu"
        },
        {
            "label": "Assigned To Me",
            "query": "is:open assignee:rahmathu"
        },
        {
            "label": "Created By Me",
            "query": "is:open author:rahmathu"
        },
        {
            "label": "Mentions Me",
            "query": "is:open mentions:rahmathu archived:false "
        }
    ],

Error dump from the extension
{
	"messages": [
		{
			"type": 1,
			"message": "`remoteHub/pullRequest` is not a valid menu identifier",
			"extensionId": {
				"value": "GitHub.vscode-pull-request-github",
				"_lower": "github.vscode-pull-request-github"
			},
			"extensionPointId": "menus"
		}
	],
	"activationTimes": {
		"codeLoadingTime": 25,
		"activateCallTime": 0,
		"activateResolvedTime": 1851,
		"activationReason": {
			"startup": true,
			"extensionId": {
				"value": "GitHub.vscode-pull-request-github",
				"_lower": "github.vscode-pull-request-github"
			},
			"activationEvent": "*"
		}
	},
	"runtimeErrors": [],
	"runningLocation": {
		"affinity": 0,
		"kind": 1
	}
}

Screenshot of the extension error

When you see it again, can you also share the output from the developer console (command: Developer: Toggle Developer Tools) and from GitHub Pull Request in the Output panel?

@alexr00 : Here you go after a reload of the developer window

Here is the developer console view in detail

In case this is not helpful and font is too small please let me know step by step on how to take logs for each window

Thanks! There's nothing very suspicious there either. What is leading you to think that this extension is causing VS Code to hang?
Can you set the setting "githubPullRequests.logLevel": "debug", then when you next see the hang can you share the "GitHub Pull Request" output again?

@alexr00 : I turned all extensions off and started turning on one by one, then what i noticed that this github pull loads the slowest and also during vscode hangs the extension is pulling updates . That made my suspicious about this. Let me make the log level debug and get back to you

@alexr00 : I am not able to see the problem any more, not sure what helped. After an update things are working good. Closing this issue. Thanks a lot for your help

@rahmathu thanks for the update! If you see it again we can always take another look.


StaticVariableLengthArray

Add a subclass of cetl::VariableLengthArray that contains its own array storage and implements its own allocator. E.g:
template<typename T, std::size_t max_length>
class StaticVariableLengthArray : public VariableLengthArray<T, pf17::pmr::polymorphic_allocator<T>>

See proposed version of this in janky.hpp in libcyphal (garage)


Add a dark-light theme switch to docs

We can use this plugin. Easy.
https://docsify-darklight-theme.boopathikumar.me
Update: this is even better. Docsify uses this https://github.com/anikethsaha/docsify-plugin/tree/master/packages/docsify-dark-mode

Since we are moving all the docs to a central repo shabados/docs and it already has a dark theme implemented in it https://github.com/shabados/docs/pull/7


chore: bdd-gh-1583822580 to 0.0.1

chore: Promote bdd-gh-1583822580 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Add Mainnet tomls for SIP-373 and SIP-376

awesome all tests green for today's release, thank you @noisekit @leomassazza


Respect Permission Set permissions when validating "System Admin" level permissions

Critical Changes

When validating that a User is considered a "System Administrator" for access to NPSP Settings and for Error alerts, NPSP will now respect permissions assigned through a Permission Set as well as through a Profile. The three permissions checked for are: Modify All Data, Customize Application, and Author Apex. For more information, read https://powerofus.force.com/s/article/NPSP-Set-Required-Permissions

Changes
Issues Closed

Fixes #5584

Community Ideas Delivered
New Metadata
Deleted Metadata

W-7782149

Test charter related - https://salesforce.quip.com/EojEA1ntL29K


Staged Copy documentation is misleading

Reading this documentation, I would assume that i could use staged copy to copy from On-Prem SQL thru IR1 to Azure SQL Database Managed Instance thru IR2 - however that is not the case.
The pipeline with the activity will not validate with an error message stating that both source and sink needs to use same IR.
I do think that this sentence "Currently, you can't copy data between two on-premises data stores by using a staging store" is trying to explain that, but fails to explain that it is true even for cloud sinks, when you need to use self hosted IR to connect to it.
Could you please clarify?
BR David

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

ID: 0bbd66af-d49f-e595-a7bc-c48cd3675ddc
Version Independent ID: d3e43062-2f4e-a7a9-17f0-9c3e05d36f27
Content: Copy Activity performance and tuning guide in Azure Data Factory
Content Source: articles/data-factory/copy-activity-performance.md
Service: data-factory
GitHub Login: @linda33wj
Microsoft Alias: jingwang

@DBojsen Thanks for your question. We are checking on this and will respond to you soon.

@linda33wj Can you please take a look at this?

Thanks for the feedback. I've updated the specific sentence you referred to in Staged copy section, to clarify the non-supported scenario.
#please-close


Data Factory and Purview account are not connected

After the deployment is completed, I did not see the catalogUri tag on the ADF resource and ADF connection was in Disconnected status in Azure Purview.

We will not add this for now, since SHIR and Service Principal are required anyways for scans, if all services are behind private endpoints (e.g. Purview, Synapse, Data Factory, etc.). Therefore, we will hold off for now, since this is not something that is actually required when using private endpoints end-to-end.

Update: I am working on Full Automation of Lineage and Data Source onboarding here: https://github.com/marvinbuss/PurviewAutomation


port price bot

added to only work in channel provided or DM, already set up for #bot-sandbox channel, also added proper sign to price output

Thanks!


More features and fixes (Secrets/ENVs/ServicePort)

What this PR does / why we need it:

Support ACLs for topics
Use service port for external distinct service
be able to control competing dns annotations
be able to provide extra non KAFKA_ prefixed ENV variables
be able to mount k8s secrets without subpath / keys

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
This includes ACLs from pull request https://github.com/helm/charts/pull/7505 which will be closed.

/ok-to-test

@stevie - awesome pr -- these features are great and sorely needed by the chart.
/ok-to-test

I think you just need a version bump

@benjigoldberg versioned bumped and fixed a bug if multiple operations should be applied

@unguiculus solved merge issues and bumped version again

/assign benjigoldberg
@unguiculus assigning back to owner, since git history is fixed

/lgtm


add transfer to simple benchmark and fix transfer issue in chaincode

add transfer to simple benchmark and fix transfer issue in chaincode

Sorry for the late reply. Thanks for the contribution, but first you should use 'commit -s' to sign the commitment.
And I think the simple benchmark is only an 'example' to show how to write a benchmark. We have another benchmark named smallbank which implements a more comprehensive benchmark including transferring money.

OK, then I will close the pull request


Disabling Anti-Aliasing Modifier

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues

Expected Behaviour
I need to see the images in raw form without any modification when I zoom in and I'm working on pixel level
(for example what you see in windows photo viewer when you zoom in)
Current Behaviour
Right now CVAT uses an anti-aliasing modifier which smoothens the edges of every pixel
Context
I don't know if this modifier is normal in other cases but I guess I'm gonna be able to annotate with higher precision if images are shown without any modification
Your Environment

Server version: 1.3
Core version: 3.10.0
Canvas version: 2.3.1
UI version: 1.14.2

@mat48 , is Smooth image something you are looking for? https://openvinotoolkit.github.io/cvat/docs/manual/basics/settings/

Yes that's exactly what I was looking for. We'll upgrade CVAT to get that feature.
Thank you!

Hi @nmanovic I was also looking for Smooth image option but I can't see the option in the menu even thought I installed CVAT today by following the installation guide


Wiki Issue : Command Line Params

Describe the bug
Command Line Wiki is missing details
To Reproduce
Steps to reproduce the behavior:

Go to '.https://github.com/Appdynamics/AppDynamics.DEXTER/wiki/Command-Line-Parameters"

Expected behavior
-j, --job-file                      Required. Input file defining the parameters of the ETL job to process.
-o, --output-folder                 Output folder where to store results of processing.
-c, --compare-states-file           Required. Compare file defining the mappings of the state comparison to perform.
-l, --left-from-state-folder        Required. Folder of the ETL job to use as a left side/reference/from comparison.
-r, --right-to-state-folder         Required. Folder of the ETL job to use as a right side/difference/to comparison.
-d, --delete-previous-job-output    If true, delete any results of previous processing.
-s, --sequential-processing         If true, process certain items during extraction and conversion sequentially.
-v, --skip-version-check            If true, skips the version check against GitHub repository.
--help                              Display this help screen.
--version                           Display version information.

The Functionality behind -c and -l are not yet complete so they are not documented

@danielodievich ok cool, I was looking into using it, but not sure how to. Thanks!


Release D-FINE on Hugging Face

Hello @Peterande 🤗
I'm Niels and work as part of the open-source team at Hugging Face. I discovered your work as it was trending on PapersWithCode and indexed the paper page here: https://huggingface.co/papers/2410.13842. The paper page lets people discuss about your paper and lets them find artifacts about it (your model for instance) you can also claim the paper as yours which will show up on your public profile at HF.
Would you like to host the checkpoints you've trained on https://huggingface.co/models? Hosting on Hugging Face will give you more visibility/enable better discoverability. We can add tags in the model cards so that people find the models easier, link it to the paper page, etc.
If you're down, leaving a guide here. If it's a PyTorch model, you can use PyTorchModelHubMixin class which adds from_pretrained and push_to_hub to the model which lets you to upload the model and people to download and use models right away.
If you do not want this and directly want to upload model through UI or however you want, people can also use hf_hub_download.
After uploaded, we can also link the models to the paper page (read here) so people can discover your model.
You can also build a demo to your model on Spaces we can provide you an A100 grant.
What do you think?
Kind regards,
Niels

Dear Niels,
Thank you so much for reaching out! I'm really glad to hear about the great opportunities on Hugging Face. I'll work on it in the near future and follow the instructions you provided.
Best regards,
Yansong Peng

Great :)
Also, in case you're interested in contributing D-FINE to the Transformers library, let me know!
We integrated models like DETR, Deformable DETR, RT-DETR and more.

I will look at some relevant cases and give it a try. Thank you～

Thank you @Peterande, would it be possible to open this issue so that we can keep track of it?


SZ sugar

Adds capabilities to compute tSZ-related quantities.
Things left to do:

[x] Fourier transform FFTLog.
[x] GNFW instead of just Planck2013.
[x] Check documentation.
[x] Finish unit test with class_sz.

If you need benchmark code, I got some for the tSZ kernel.

Ah great. You were already on my list of suspects for this!

OK @tilmantroester what kind of benchmarks could you provide?
Ideally something like C_ell^yy and C_ell^ym would be great... Note that I've only implemented the Arnaud GNFW profile here for now

What I could provide easily is a the tSZ redshift kernel. Cls would require a bit more work. I have
C_ell^ym in principle from CosmoSIS but those would be based on a non-UPP halo model (Alex Mead's HMx). The python interface is not yet stable though. But in principle that could be plugged into the generalised tracers in CCL to get C_ell^ym to compare.

Pull Request Test Coverage Report for Build 4782

13 of 90 (14.44%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-2.3%) to 94.316%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pyccl/tracers.py
3
10
30.0%

pyccl/halos/profiles.py
10
80
12.5%

Totals

Change from base Build 4742:
-2.3%

Covered Lines:
2987

Relevant Lines:
3167

💛  - Coveralls

@tilmantroester would you mind reviewing this?
I've benchmarked the full power spectrum calculation against class_sz, after iterating with @borisbolliet (who has been most helpful!).
@beckermr I've introduced functionality to update the internal parameters of halo profiles through this kind of stuff. Having will be very useful, since many of these parameters are "fast" and shouldn't trigger a recalculation of slow things like Fourier transforms (this will be also true when we implement HODs and other profiles). I know you don't like kwargs, so I'd like to hear your thoughts on this particular point (no need to look at the full PR).

@damonge Why do you need the kwargs? Just list each one and set it to None. Then you can test and if it is non-None, then reset it.

yep, that would work too. I just wondered if kwargs would be useful for likelihood design (e.g. if all the likelihood parameters are in a dictionary, you can just pass the full dictionary through, without having to pick the params in it that this particular profile depends on)

This sounds convenient but ultimately it is a recipe for errors. By making things explicit, we can help catch cases where ppl pass things that they think do one thing but don't actually do anything at all.

Alright, let me do this.

Alright, done. @tilmantroester , let me know if you think you'll be able to take a look.

Thanks @tilmantroester ! Back to you.

Awesome, thanks!


Add serviceAccountJson to constructor

This adds the serviceAccountJsonFile to the constructor for the
GooglePlay object. Additionally, it removes some redundant checks for
the versionCode check.

@PEConn - This is the first in several refactors. I am pushing these changes to a branch called playExperiment so we can do smaller revisions before merging all the changes to the main branch.


Can't scroll on VODs page

Overflow on VODs page no longer scrolls after the React conversion.

Same thing for screenshots

Fixed in: 479bbb3


add clarification on same package import & export

Closes #745
add note about possible side effects if resolver choses "External"
TODO still WIP

I really like the idea to show in examples what problems could happen, and what advantages and disadvantages several approaches of imports and Exports and embedding APIs or not can have.
But should we really add recommendation to handle Exports and imports like this in the spec.?
@tjwatson
@timothyjward
@pkriens
@bosschaert

But should we really add recommendation to handle Exports and imports like this in the spec.?

Good question and I am very open to suggestions. I just followed a proposal from a slack chat to suggest a spec adddition here like I did. But I am fine with any other suggestion. I just simply would like to have an "official" place (where I can link to from other places) for stuff like this (given the information I added is correct.. what is still to be determined by the group).

But should we really add recommendation to handle Exports and imports like this in the spec.?

As an example we have similar for Require Bundle here:
https://docs.osgi.org/specification/osgi.core/8.0.0/framework.module.html#i3198951

e.g. It is unclear why import+export improves collaboration, this is questionable as they can simply collaborate by not embedding API in a much better way.

How would you explain it?
Here is my attempt:

Bundles willing to import exported packages allow the framework to substitute exports for imports and improve collaboration, because the framework can try to avoid separate class-spaces.

Not optimal. I tried to somehow use this blog post but could not really come up with a easier explanation without giving a  huge example.

Thanks a lot @timothyjward for your review and suggestions. I committed them all.

@laeubi thanks for your suggestions, I added them.


Genes with no transcripts

People are still getting confused about what is happening when genes have no transcripts. Go to the demo data for gene TRA as an example. Gene.iobio will spin forever on TRA (if you click on it while it's loading RAI1, it will show 4 variants in the count and spin forever - 4 is the number of variants in RAI1). Here are some things I think we should do:

[ ] The error message says "No Gencode transcripts for TRA. Using Refseq transcripts instead." This implies that results will be forthcoming from Refseq transcripts, but there are no Refseq transcripts either, so nothing gets loaded. If there are no transcripts, can we change the message to something more like "No transcripts are available for TRA and so many annotations cannot be determined"?
[ ] Gene.iobio spins forever, but it should still be able to display the variants. If there are no transcripts, can we just not run annotation tools that require a transcript, but still show the variants. The impact would be Unknown (grey) for them all and they could still have e.g. gnomAD annotations

The gene TRA presents an interesting scenario. There is a gene in the RefSeq gff, but no transcripts. So without a transcript, we can't do any of the annotate variants analysis because transcript is required. It would take a significant amount of effort to rework annotate variants to work without a transcript.
I will fix the bug so that gene doesn't attempt to annotate the variants since there is no transcript. It will fail gracefully with a message that indicates there are no transcripts for this gene.
There is an existing issue to rework the gene model so that genes that are not in RefSeq or Gencode (or genes that don't have transcripts) and better handled in gene.iobio and other iobio apps. #839

Ok. We should include in the message that no variants are being shown because of this. The implication to the user is that there are no variants in the gene, but that isn't necessarily the case - we're just not showing any if there are no transcripts. Longer term, just displaying the variants would be good.

As to the first point, we need to make it as clear as possible that a lack of transcripts is not a bug, but a lack of information that makes gene.iobio unable to annotate the variants. I keep getting lots of messages from people about this message and I have to keep explaining to people what is going on.

Test with genes: TRA, WAR

@tonydisera How much effort would it be to just skip the annotation step? For example, IGH does have variants that appear in ClinVar so seeing the variants that fall into this region would still be useful without the annotations. I think you said this is a reasonable amount of work, so it might need to be broken out into its own issue for later, but just wondering.
The alternative solutions are to remove these genes from the list (I'm not a big fan of this as people will still complain - just that they can't pick their gene of interest), or suggest other genes. For example there are a million genes in the same region as IGH that do have transcripts.


Loads should be shown per stakeholder for the electricity network

In practice the price a customer pays is calculated according to a cascade: e.g. the customers that are connected to the medium voltage grid don't pay for the low voltage grid. In order to calculate this in the business case, and calculate other future alternative tariff models, you want to know what the share of different customers & cooperations is in the load and especially the peaks on the medium and high voltage levels. At the moment you can view this per technology in the stacked curve, but it would be nice if there would also be an option to view this per stakeholder. Preferably the profiles for the full year, similar to technologies. A nice-to-have is that it automatically shows the share of the different stakeholders in the highest peaks at the different voltage levels or integrates this in the market model.

I have rephrased the title to reflect the idea better.

Transfering the issue from me to @MarjoleinSchwachofer


Getting access token as Null in Google service account

I am using Google service account to get access Token from service side using below code. But I am getting access token as Null. The same returned token will be used to open Google file picker on client side for the same userEmailId. Please suggest what I am doing wrong in my code.
private static final List SCOPE = Arrays.asList("https://www.googleapis.com/auth/drive");
public String getAccessToken(String SERVICE_ACCOUNT_EMAIL, String SERVICE_ACCOUNT_PKCS12_FILE_PATH,String userEmailId){
    try {
        HttpTransport httpTransport = new NetHttpTransport();
        JsonFactory jsonFactory = new JacksonFactory();
        GoogleCredential credential = new GoogleCredential.Builder()
                                        .setTransport(httpTransport)
                                        .setJsonFactory(jsonFactory)
                                        .setServiceAccountId(SERVICE_ACCOUNT_EMAIL)
                                        .setServiceAccountScopes(SCOPE)
                                        .setServiceAccountUser(userEmailId)
                                        .setServiceAccountPrivateKeyFromP12File(new java.io.File(SERVICE_ACCOUNT_PKCS12_FILE_PATH))
                                        .build();
        credential.getRefreshToken();
        return credential.getAccessToken();
            } catch (Exception e) {
                // TODO: handle exception
                log.severe("Error while getting Drive  credentilas. 5.0"+ e.getMessage());
                return null;
            }
        }

Did you resolve it? It seems to me like you might be putting in wrong client-id or scopes.

just replace  credential.getRefreshToken(); to credential.refreshToken();

Thank you for filing this issue. We asked some clarifying questions a week or more ago and never heard back from you. We are unable to proceed with this issue until then, so we are closing it. Please feel free to re-open this issue with more information.


Target-specific features reimplemented #1197

r? @alexcrichton

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Eh2406 (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

failures:

---- build::deterministic_cfg_flags stdout ----
running `/home/vsts/work/1/s/target/debug/cargo build -v`
thread 'build::deterministic_cfg_flags' panicked at '
Expected: execs
    but: differences:
  3 - |[RUNNING] `rustc --crate-name foo [..] --cfg[..]default[..]--cfg[..]f_a[..]--cfg[..]f_b[..]--cfg[..]f_c[..]--cfg[..]f_d[..] --cfg cfg_a --cfg cfg_b --cfg cfg_c --cfg cfg_d --cfg cfg_e`|
    + |     Running `rustc --crate-name foo src/main.rs --color never --crate-type bin --emit=dep-info,link -C debuginfo=2 --cfg 'feature="f_a"' --cfg 'feature="default"' --cfg 'feature="f_b"' --cfg 'feature="f_c"' --cfg 'feature="f_d"' -C metadata=135da3956bdec8cb -C extra-filename=-135da3956bdec8cb --out-dir /home/vsts/work/1/s/target/cit/t219/foo/target/debug/deps -L dependency=/home/vsts/work/1/s/target/cit/t219/foo/target/debug/deps --cfg cfg_a --cfg cfg_b --cfg cfg_c --cfg cfg_d --cfg cfg_e`|

Happens because of features_sorted() replaced with features(). Will fix ASAP.

:umbrella: The latest upstream changes (presumably #7137) made this pull request unmergeable. Please resolve the merge conflicts.

Thanks for the submission! I don't have time to give this the review it deserves. I am sorry.
Currently the lockfile that is generated is completely independent of the system it is built on, does this PR maintain that property?
The metadata output is stable so we need to be careful to include the new info in a way that doesn't break anyone.
(cc #1197)

I was relying on the unit tests to keep the existing functionality alive, did not pay a specific attention to the lock files (though no new information should be added to the lockfile, as far as I have inspected several of the live projects that I need the platform features for). Perhaps if you find a need to check the lockfile stability, I may try implementing it as a unit test.
In principle, my change replaces the str/String/InternedString that replesents a feature, with a tuple (str/String/InternedString, Option<Platform>), and Set<String> with Map<String, Option<Platform>>, for the places where the parser interacts with the input Cargo.toml and the platform triple.

:umbrella: The latest upstream changes (presumably #7186) made this pull request unmergeable. Please resolve the merge conflicts.

The tricky case I see is
root depends on a and c="1.1.0"
a depends on b and on OSX depends on b's flag maybe
b depends on c="=1.0.0" if maybe is active.
c v1.0.0 and c v1.1.0 has no dependency
On OSX we get an error "can not have two semver compatible versions of c". Do we get that error on Windows?

Something utterly terrible had happened during the upstream merge.


⚠ Bofrost.fr has degraded performance

In 7b2531f, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1048 ms

Resolved: Bofrost.fr performance has improved in debeec7 after 6 minutes.


[SPARK-35897][SS] Support user defined initial state with flatMapGroupsWithState in Structured Streaming

What changes were proposed in this pull request?
This PR aims to add support for specifying a user defined initial state for arbitrary structured streaming stateful processing using [flat]MapGroupsWithState operator.

Why are the changes needed?
Users can load previous state of their stateful processing as an initial state instead of redoing the entire processing once again.

Does this PR introduce any user-facing change?

Yes this PR introduces new API
  def mapGroupsWithState[S: Encoder, U: Encoder](
      timeoutConf: GroupStateTimeout,
      initialState: KeyValueGroupedDataset[K, S])(
      func: (K, Iterator[V], GroupState[S]) => U): Dataset[U]

  def flatMapGroupsWithState[S: Encoder, U: Encoder](
      outputMode: OutputMode,
      timeoutConf: GroupStateTimeout,
      initialState: KeyValueGroupedDataset[K, S])(
      func: (K, Iterator[V], GroupState[S]) => Iterator[U])

How was this patch tested?

Through unit tests in FlatMapGroupsWithStateSuite

@tdas can you enable CI on this

Can one of the admins verify this patch?

cc: @tdas can you enable CI on this

add to whitelist

Test build #140337 has started for PR 33093 at commit 4a0b591.

Test build #140337 has finished for PR 33093 at commit 4a0b591.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140337/

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44868/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/44868/

Test build #140342 has started for PR 33093 at commit 69b3c7e.

Test build #140342 has finished for PR 33093 at commit 69b3c7e.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140342/

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44873/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/44873/

Can one of the admins verify this patch?

ok to test

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44877/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/44877/

Test build #140347 has started for PR 33093 at commit 69b3c7e.

Test build #140347 has finished for PR 33093 at commit 69b3c7e.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140347/

Can one of the admins verify this patch?

@rahulsmahadev, mind keeping the PR description template (https://github.com/apache/spark/blob/master/.github/PULL_REQUEST_TEMPLATE)?

Test build #140405 has started for PR 33093 at commit 6c1443c.

Test build #140405 has finished for PR 33093 at commit 6c1443c.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
trait WatermarkSupport

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140405/

Test build #140407 has started for PR 33093 at commit ec2b972.

Test build #140407 has finished for PR 33093 at commit ec2b972.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140407/

Test build #140413 has started for PR 33093 at commit f221358.

Test build #140415 has started for PR 33093 at commit 673008d.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44920/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44922/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44920/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/44920/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44922/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/44922/

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44928/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/44928/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44930/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44930/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/44930/

Test build #140413 has finished for PR 33093 at commit f221358.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #140415 has finished for PR 33093 at commit 673008d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140413/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140415/

Test build #140458 has started for PR 33093 at commit a25ea47.

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44972/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/44972/

Test build #140458 has finished for PR 33093 at commit a25ea47.

This patch passes all tests.
This patch does not merge cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140458/

Test build #140465 has started for PR 33093 at commit ef50c79.

Test build #140467 has started for PR 33093 at commit 7629d2e.

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44979/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44981/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/44979/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/44981/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/44981/

Test build #140465 has finished for PR 33093 at commit ef50c79.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #140467 has finished for PR 33093 at commit 7629d2e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140465/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140467/

Test build #140488 has started for PR 33093 at commit e2234a8.

Test build #140488 has finished for PR 33093 at commit e2234a8.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140488/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45000/

Test build #140497 has started for PR 33093 at commit 7d7b5a9.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45000/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/45000/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45008/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45008/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/45008/

Test build #140514 has started for PR 33093 at commit 57c9c2f.

Test build #140518 has started for PR 33093 at commit 4e85a62.

Test build #140497 has finished for PR 33093 at commit 7d7b5a9.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140497/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45027/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45027/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/45027/

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45031/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/45031/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140514/

Test build #140518 has finished for PR 33093 at commit 4e85a62.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140518/

Test build #140538 has started for PR 33093 at commit 0374bdb.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45051/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45051/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/45051/

Test build #140543 has started for PR 33093 at commit b8c70ab.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45056/

Test build #140545 has started for PR 33093 at commit b47ac23.

Test build #140545 has finished for PR 33093 at commit b47ac23.

This patch fails Java style tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45056/

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45058/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140545/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/45056/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/45058/

Test build #140550 has started for PR 33093 at commit eb83b68.

Test build #140538 has finished for PR 33093 at commit 0374bdb.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45063/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140538/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/45063/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/45063/

Test build #140543 has finished for PR 33093 at commit b8c70ab.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140543/

Thanks, merging to master

Test build #140550 has finished for PR 33093 at commit eb83b68.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/140550/


Fixed shifting content on page load

Fixed shifting content when page is loaded in docs.
@ericjim @naomiblack Please review and merge thanks!

CLOSES:
https://github.com/angular/angular.io/issues/1015

LGTM, here is a test link if anyone wants to test it out https://api-doc-styling-2.firebaseapp.com
@naomiblack @petebacondarwin

merged.


chore: pin dependencies version for better stability of the build.

This PR tweaks the dockerfile to get better stability when it comes to the build e.g. pinning specific tags or branches to make this breaks with further notice.

LGTM

Any news on this?

Any news on this?

Thank you for your contribution!


Do not show single-thread in Call Stack during multi-session debugging

Issue Type: Bug
When debugging with a single session and a single thread, the thread is omitted in the »call stack« hierarchy. However, if there are multiple sessions, even if they have only a single thread, the thread is included as a level in the call stack tree. In other words, is:

Call stack

Process 1

Thread 1

function

Process 2

Thread 1

function

want:

Call stack

Process 1

function

Process 2

function

Space is precious there if you have multiple processes.
VS Code version: Code 1.31.1 (1b8e8302e405050205e69b59abb3559592bb9e60, 2019-02-12T02:19:29.629Z)
OS version: Linux x64 4.15.0-45-generic

None of them is a duplicate.

This is a fair feature request and I think it makes sense.
Assigning to on-deck so we look into this when we find some time.

We fixed this in latest vscode that we are about to ship! Check it out and let us know what you think


Feature Request - Insight endpoint for Config Server

So , this was a problem we were generally facing while deploying our applications. As different environment/profile files grew in complexity , often it would happen that there would be few properties which would be present in one profile property file and absent in other , as addition of properties was done manually by an individual.
For example - Consider you have 4 profiles , DEV , SIT1 , SIT2 , UAT . So you have 4 profile specific file , application-DEV.yml , application-SIT1.yml , application-SIT2.yml , application-UAT.yml.
As , these files grew in complexity , it would often happen , that an individual would forget to add some properties in one file , or maybe mixed up the values in between environments . As were deploying our applications as a WAR and using legacy infrastructure , if a certain property was missing in one environment , obviously an application would not start as it was expecting that , but the amount of time taken , to identify what is missing and change the property files , make them consistent , and restart the application , as it was legacy infrastructure , would take 30 minutes and screw up productivity .
I propose to add an endpoint by which after deploying the config Server , you can demand to see the 'diff' between property files . This would return the response , where it would tell you the difference between property files . Difference like how many properties are present in one file and how many in other . Are there any properties present in one and not in other , if the same property exists in both , what is difference in their values and so on .

Not sure how this would work because not all repositories use files.

By that u mean jdbc and vault?

Indeed

I have never personally used either of them , but when property sources objects get sent to the config client , what are the name fields populated with?

Maybe we wouldn't need files, but we might need history (which those stores do not support). I'm kind of unsure at the moment, though, what the actual requirement is. Since you have a real use case, do you think you could expand a bit? You mentioned an "endpoint". What would it's contract be? Show use some example requests and responses.

Okay I will post a detailed example in the evening.

This is a very basic example .
The endpoint would be /compare/{application}/{profiles} . Here application is the prefix  of the file's name  and profiles is a comma separated list of profile values . So , if application is given the value of TemplatingApp and profiles is DEV,UAT. So your request is ,
http://localhost:8081/compare/application/DEV,UAT
In such a scenario , you will first check if such a prefix exists for any file , and if the prefix exists , do these various profiles exist. So , in a nutshell , it will look for files - TemplatingApp-DEV.yml and TemplatingApp-UAT.yml , if either or both are not found , it will throw back a response with status code
404 Files not found.
In the happy scenario it would send back a response which would be a comparison between TemplatingApp-DEV.yml and TemplatingApp-UAT.yml .
This is a very basic implementation I have created right now , the response is ,
                              {
                                 "Comparing UAT to DEV": {
                                     "commonKeys": [
                                          "c",
                                          "d",
                                           "e"
                                     ],
                                     "differentKeys": [
                                          "f",
                                          "g",
                                          "l"
                                      ],
                                 "description": [
                                     "Same key found but values are different.Key is:c and values are fgh and ere respectively.",
                                      "Same key and value found . Key is d and value is fdf",
                                      "Same key found but values are different.Key is:e and values are lki and hghj respectively.",
                                      "Key not found.Key is f and value is lmn",
                                      "Key not found.Key is g and value is opq",
                                      "Key not found.Key is l and value is abc"
                                     ]
                              },
                                   "Comparing DEV to UAT": {
                                       "commonKeys": [
                                         "c",
                                         "d",
                                         "e"
                                        ],
                                       "differentKeys": [
                                        "a",
                                         "b"
                                         ],
                                      "description": [
                                         "Key not found.Key is a and value is abc",
                                         "Key not found.Key is b and value is dsd",
                                         "Same key found but values are different.Key is c and values are ere and fgh respectively.",
                                         "Same key and value found . Key is d and value is fdf",
                                          "Same key found but values are different.Key is e and values are hghj and lki respectively."
                                       ]
                               }
               }

Obviously , this response can be improved and made more user friendly . This is my initial draft on the above . Let me know what you guys feel about it.

The semantics of what the profile values mean is kind of problematic there. What if the you want to know the difference between configuration using 2 profiles and the default?
In summary, I'm not sure we should get into this business. The data are all available to you, so you can create the report  yourself with a bit of command line fu.

Yeah I have already done it myself. Closing the issue then, as I could not convince u guys.


More games to add d3d9.deferSurfaceCreation = True

Frogs,
I have confirmed with the newly merged v1.5 the following game exes that also need d3d9.deferSurfaceCreation = True to become playable.
Will add more games to the list if I find them.

Nelke_and_the_Legendary_Alchemists.exe
Atelier_Lulua.exe

:frog:

There's already a discussion going on about that here, please continue there.
I'll add these, but I'd like to have a more or less complete list of affected games rather than having dozens of commits adding each one individually.


Files generated with version 3.2.0 fail to load in various applications

Hi,
Some CloudCompare users have reported that the files saved with version 3.2.0 of libE57Format won't open with Rhino8, SolidWorks 2023 and FARO Scene. Reverting to version 3.1.1 seems to fix the issue.
It seems to be related to this commit: feaa963f704ab5b677ad8978c4f9a42f0ceb145d (I've generated files with version 3.2.0 with only this commit reverted, and it seems to work fine). Even though it seems to be 'required by the standard', I guess these SW solutions are not able to handle the single CV index packet properly?
Maybe a solution would be to add a boolean somewhere to control whether this CV index packet should be automatically added or not? (with a default state to true)
@dancergraham I've attached a file that fails to load with the above applications. pumpsA_3.2.0.e57.zip

the rust e57 library seems to skip over index packets - I can read this file successfully with my e57 python library https://github.com/cry-inc/e57/blob/bdb8fa9015b1e87d5c600860c51002e25cb95c7d/src/queue_reader.rs#L80

Problems here too for v3.2.0 E57 to Cintoo cloud service.
Reverting the mentioned commit works for us too.
https://cintoo.com/

This should be reported to the applications that are failing. They will fail on any E57 file containing index packets.
My guess is they are based on either the original reference implementation or an older version of this library - both of which fail to read index packets properly (they throw an exception).
I fixed it in libE57Format somewhere along the way, so if they are using this they just need to update.

It's not realistic for us to require all our customers to chase their vendors to update their E57 reader.
We're going to want a compile-time opt-out for this for a good while, I expect.
I am happy to raise it with Cintoo, but I'm not sure our relationship with them is going to be a particularly high priority.


DEPS: pydantic 2 compatibility

migration guide: https://docs.pydantic.dev/dev-v2/migration/

Any chance of getting this merged and a new release?

I had to further apply this to make things work (not sure why Optional for container_config doesn't work):
diff -urN a/_vendor/python_docker-orig/schema.py a/_vendor/python_docker/schema.py
--- a/_vendor/python_docker-orig/schema.py	2024-02-13 10:26:07
+++ a/_vendor/python_docker/schema.py	2024-02-13 10:41:29
@@ -87,14 +87,16 @@
 class DockerConfigHistory(BaseModel):
     created: str = Field(default_factory=_docker_datetime_factory)
     created_by: str = ""
+    empty_layer: bool = False

 class DockerConfig(BaseModel):
     architecture: str = "amd64"
+    author: str = None
     os: str = "linux"
     config: DockerConfigConfig
     container: Optional[str] = None
-    container_config: Optional[DockerConfigConfig]
+    container_config: Optional[DockerConfigConfig] = None
     created: str = Field(default_factory=_docker_datetime_factory)
     docker_version: str = "18.09.7"
     history: List[DockerConfigHistory] = []


1024 (iPad landscape) - not touch enabled and open the link

Hi, on iPad 1024 res, it work as Desktop normal hover behaviour, it needs to work as on first touch expand the mega-menu then if touch again goes to first level link.

any update?


UniqueIndexChecker does not infer association key from association

In the following code, Rails can correctly infer that validates :category, uniqueness: { scope: :post } refers to the unique index_categorisations_on_category_id_and_post_id but the UniqueIndexChecker doesn't do that inference correctly.
class Categorisation < ActiveRecord::Base
  belongs_to :category
  belongs_to :post

  # Rails correctly infers `category_id` and `post_id` here but UniqueIndexChecker doesn't and so fails
  validates :category, uniqueness: { scope: :post }
end

I tried to follow the Rails source code for the UniquenessValidator to see how UniqueIndexChecker can be adapted to infer the key too, but I got stuck. Any pointers?

Hi @christos,
Thank you for letting me know! Indeed, I see we have this issue. I'll fix this today and share with you the new released version.

Any pointers?

It happens here in ActiveRecord:
def build_relation(klass, attribute, value)
        relation = klass.unscoped
        comparison = relation.bind_attribute(attribute, value) do |attr, bind|
          return relation.none! if bind.unboundable?

So they check if it's an association first:
def bind_attribute(name, value) # :nodoc:
      if reflection = klass._reflect_on_association(name)
        name = reflection.foreign_key
        value = value.read_attribute(reflection.klass.primary_key) unless value.nil?
      end

      attr = table[name]
      bind = predicate_builder.build_bind_attribute(attr.name, value)
      yield attr, bind
    end

Fixed here: https://github.com/djezzzl/database_consistency/pull/141.
Released in 1.3.2. Please try it and let me know if it works fine for you. Feel free to reopen the issue!
BTW, feel free to share any ideas for the gem that could be valuable for you and your projects. Have a great day!

@djezzzl Working great now. Thanks for the quick fix!

BTW, feel free to share any ideas for the gem that could be valuable for you and your projects.

Will do!

Thank you @christos,  for quickly validating this! Have a great time!


Accordion: list inside accordion causes content to be duplicated (only in primevue-nuxt)

If you include a list within an Accordion, its contents are duplicated.
This error only happens with primevue-nuxt, I was unable to reproduce the same problem with primevue only.
Reproducer: https://stackblitz.com/edit/primevue-nuxt-issue-template-7scwyq?file=app.vue
    <Accordion>
      <AccordionTab>
        <template #header>
          1. Introduction
        </template>

            MY LIST

Item 1

Item 2

Item 3

           Lalalla

      </AccordionTab>
    </Accordion>

Interesting! I'll check it and get back to you.

Unfortunately, I couldn't replicate it. Could you please try the new @primevue/nuxt-module package?


to fix no empty directories error for libmysql-macosx

when i instal libmysql ,there some error info:

feimamacdeMBP:vcpkg feima-mac$ ./vcpkg install libmysql
The following packages will be built and installed:
    libmysql[core]:x64-osx
Starting package 1/1: libmysql:x64-osx
Building package libmysql[core]:x64-osx...
-- Using cached /Users/feima-mac/GitWorkspace/vcpkg/downloads/mysql-mysql-server-mysql-8.0.4.tar.gz
-- Using source at /Users/feima-mac/GitWorkspace/vcpkg/buildtrees/libmysql/src/ysql-8.0.4-6271934d70
-- Applying patch /Users/feima-mac/GitWorkspace/vcpkg/ports/libmysql/ignore-boost-version.patch
-- Applying patch failed. This is expected if this patch was previously applied.
-- Applying patch /Users/feima-mac/GitWorkspace/vcpkg/ports/libmysql/system-libs.patch
-- Applying patch failed. This is expected if this patch was previously applied.
-- Configuring x64-osx-dbg
-- Configuring x64-osx-rel
-- Building x64-osx-dbg
-- Building x64-osx-rel
-- Performing post-build validation
There should be no empty directories in /Users/feima-mac/GitWorkspace/vcpkg/packages/libmysql_x64-osx
The following empty directories were found:

    /Users/feima-mac/GitWorkspace/vcpkg/packages/libmysql_x64-osx/lib/plugin/debug

If a directory should be populated but is not, this might indicate an error in the portfile.
If the directories are not needed and their creation cannot be disabled, use something like this in the portfile to remove them:

    file(REMOVE_RECURSE ${CURRENT_PACKAGES_DIR}/a/dir ${CURRENT_PACKAGES_DIR}/some/other/dir)

Found 1 error(s). Please correct the portfile:
    /Users/feima-mac/GitWorkspace/vcpkg/ports/libmysql/portfile.cmake
-- Performing post-build validation done
Error: Building package libmysql:x64-osx failed with: POST_BUILD_CHECKS_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: libmysql:x64-osx
  Vcpkg version: 2018.11.23-unknownhash

Additionally, attach any relevant sections from the log files above.

so,I try to fix it.

@jimmyleeking, thanks for contributing to vcpkg!
Here is failed triplet(arm-uwp) and ports with your PR.
Processing arm-uwp                        367 vs 407
     boost-contract                **regression**                Fail vs Pass
     boost-thread                  **regression**                Fail vs Pass
     ffmpeg                        **regression**                Fail vs Pass
     forest                        **regression**                Fail vs Pass
     libvpx                        **regression**                Fail vs Pass
     socket-io-client              **regression**                Fail vs Pass
     spdlog                        **regression**                Fail vs Pass
     tiff                          **regression**                Fail vs Pass
     tinyspline                    **regression**                Fail vs Pass

 Processing arm64-windows                  458 vs 458
 Processing x64-linux                      595 vs 595
 Processing x64-osx                        587 vs 587
 Processing x64-uwp                        435 vs 435
 Processing x64-windows                    850 vs 850
 Processing x64-windows-static             767 vs 767
 Processing x86-windows                    830 vs 830

@jimmyleeking, could you also update CONTROL revision in https://github.com/Microsoft/vcpkg/blob/master/ports/libmysql/CONTROL?
More information in https://github.com/Microsoft/vcpkg/blob/master/docs/maintainers/control-files.md

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: jimmyleeking sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


[Table] Add some props to patch css only style overrides

These elements can only be styled through css classes. This PR temporary patches this component until we come up with a better solution than all these nested divs and tables. I won't add documentation since this is probably only temporary so people can have some way of overriding these elements without having to resort to css classes.

@oliviertassinari All done.

Thanks. Could you also add them to the documentation (in an alphabetic order)?

Alright I'll do that too. but then we'll have to support them for some time :sweat_smile:

@oliviertassinari Is this ok?

but then we'll have to support them for some time

That's already the case for the className api.

I'd say rewrite table, it's better not to use HTML table and instead do it all with div. This will give very flexible api and capability that would otherwise be impossible with table. But that is too far fetched. For now the least we can do is move the wrappers from Table to TableHeader, TableBody and TableFooter. If there are couplings between the parent and the child it should be resolved with carefully designed props instead of wrapping them within divs and tables. The latter hurts composibility and customizability.
But I guess if we decide to do this we have to rewrite all the table components. Therefore, deprecation will be very hard.
The best solution I can come up with is:

Keep the Table as it is for now.
Merge this PR as it is.
Create new Table components.
Deprecate the old components with a migration guide.
Remove the old Table components after some time.

@subjectix Thanks.
Regarding how we can improve the table component, I think that we should open a new issue to discuss this.


Update tf_stage.cpp - corrected Inference time display unit

The inference time (time_taken) is displayed as "ms" which is the standard abbreviation for millisecond, however the variable time_taken is declared in microseconds. The abbreviate for that is "us" if displayed with a standard character set.
auto time_taken = ExecutionTimestd::micro(&TfStage::runInference, this).count();

The change looks good.  However, would you be able to update the commit message to match our standard format?  Have a look at the git log for examples.  You will also need to include a Signed-off-by tag in the commit message.