implemented process search filter marker to include all childen proce…

I've implemented a 'process list' 'search filter' marker that will include all children processes for a process matched by its name or pid.
For example, if you filter the process list with 'devenv', you'll end up with devenv.exe process(es) only. With my change, if you filter by 'devenv*', you'll end up with devenv.exe and all its children process subtree.
If * marker is not used, search will behave as before. Using * with multiple filters separated with | is fully supported.
As said in the beginning, * will be applied only on processes matched by process name or pid. Otherwise, a resulting tree would often end up with a mess.
If my change will be accepted, as a future enchantment, I would likely implement a + marker which would specify how many levels of children will be displayed. For example, 'devenv+' would display only immediate children, 'devenv++' would display two levels etc.

I have read the CLA Document and I hereby sign the CLA

The PR changes the filter callback type from BOOLEAN to an enum but only the one callback was updated to the enum while the others are still returning BOOLEAN/TRUE/FALSE?

Why were spaces removed from if statements?

No, that's not the case. The signature of a callback is still:
BOOLEAN ProcessTreeFilterCallback

The original callback's code became a new function:
static MatchType ProcessTreeFilterCallback2
as I needed to call it twice from the new code in the callback.
Having MatchType in all callbacks wouldn't make sense as it's specific for ProcessTree filter...

Yikes. I have autoformatting and my diff tool ignored whitespace changes. Sorry, I've committed the fix.

I've merged the PR and made some changes to fix naming and improve performance: ecc8906
The wildcards are disabled by default and you need to set EnableChildWildcardSearch to enable. Let me know if those changes broke anything or if you think it's ready and stable and I'll change EnableChildWildcardSearch so wildcards are enabled by default 👍

Unfortunately, if the new option is enabled, filter doesn't seem to be working at all (3.0.6383), regardless if wildcard is specified or not.

if the new option is enabled, filter doesn't seem to be working

It was left enabled by default and setting 1 disabled the wildcard. I've updated the nightly to r6384 and fixed the setting.


Could not create cudnn handle: CUDNN_STATUS_ALLOC_FAILED

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): I don't really how to tell
TensorFlow version: 2.1
Python version: 3.6.10
Installed using virtualenv? pip? conda?: pip
Bazel version (if compiling from source): Im not really sure what that means either
GCC/Compiler version (if compiling from source): again can't tell
CUDA/cuDNN version: 10.1 / 7.6.5
GPU model and memory: Nividia Geforce RTX 2060 4604 MB memory

Describe the problem
I ran then ran this code to check if the compiler can discover my gpu and to see the difference in speed between it and cpu:
import tensorflow as tf
device_name = tf.test.gpu_device_name()
if device_name != '/device:GPU:0':
  raise SystemError('GPU device not found')
print('Found GPU at: {}'.format(device_name))
import timeit

device_name = tf.test.gpu_device_name()
if device_name != '/device:GPU:0':
  print(
      '\n\nThis error most likely means that this notebook is not '
      'configured to use a GPU.  Change this in Notebook Settings via the '
      'command palette (cmd/ctrl-shift-P) or the Edit menu.\n\n')
  raise SystemError('GPU device not found')

def cpu():
  with tf.device('/cpu:0'):
    random_image_cpu = tf.random.normal((100, 100, 100, 3))
    net_cpu = tf.keras.layers.Conv2D(32, 7)(random_image_cpu)
    return tf.math.reduce_sum(net_cpu)

def gpu():
  with tf.device('/device:GPU:0'):
    random_image_gpu = tf.random.normal((100, 100, 100, 3))
    net_gpu = tf.keras.layers.Conv2D(32, 7)(random_image_gpu)
    return tf.math.reduce_sum(net_gpu)

# We run each op once to warm up; see: https://stackoverflow.com/a/45067900
cpu()
gpu()

# Run the op several times.
print('Time (s) to convolve 32x7x7x3 filter over random 100x100x100x3 images '
      '(batch x height x width x channel). Sum of ten runs.')
print('CPU (s):')
cpu_time = timeit.timeit('cpu()', number=10, setup="from __main__ import cpu")
print(cpu_time)
print('GPU (s):')
gpu_time = timeit.timeit('gpu()', number=10, setup="from __main__ import gpu")
print(gpu_time)
print('GPU speedup over CPU: {}x'.format(int(cpu_time/gpu_time)))

and it returned the following error:
Found GPU at: /device:GPU:0
---------------------------------------------------------------------------
UnknownError                              Traceback (most recent call last)
<ipython-input-1-121519b30cf2> in <module>
     29 # We run each op once to warm up; see: https://stackoverflow.com/a/45067900
     30 cpu()
---> 31 gpu()
     32
     33 # Run the op several times.

<ipython-input-1-121519b30cf2> in gpu()
     24   with tf.device('/device:GPU:0'):
     25     random_image_gpu = tf.random.normal((100, 100, 100, 3))
---> 26     net_gpu = tf.keras.layers.Conv2D(32, 7)(random_image_gpu)
     27     return tf.math.reduce_sum(net_gpu)
     28

~\anaconda3\lib\site-packages\tensorflow_core\python\keras\engine\base_layer.py in __call__(self, inputs, *args, **kwargs)
    820           with base_layer_utils.autocast_context_manager(
    821               self._compute_dtype):
--> 822             outputs = self.call(cast_inputs, *args, **kwargs)
    823           self._handle_activity_regularization(inputs, outputs)
    824           self._set_mask_metadata(inputs, outputs, input_masks)

~\anaconda3\lib\site-packages\tensorflow_core\python\keras\layers\convolutional.py in call(self, inputs)
    207       inputs = array_ops.pad(inputs, self._compute_causal_padding())
    208
--> 209     outputs = self._convolution_op(inputs, self.kernel)
    210
    211     if self.use_bias:

~\anaconda3\lib\site-packages\tensorflow_core\python\ops\nn_ops.py in __call__(self, inp, filter)
   1133           call_from_convolution=False)
   1134     else:
-> 1135       return self.conv_op(inp, filter)
   1136     # copybara:strip_end
   1137     # copybara:insert return self.conv_op(inp, filter)

~\anaconda3\lib\site-packages\tensorflow_core\python\ops\nn_ops.py in __call__(self, inp, filter)
    638
    639   def __call__(self, inp, filter):  # pylint: disable=redefined-builtin
--> 640     return self.call(inp, filter)
    641
    642

~\anaconda3\lib\site-packages\tensorflow_core\python\ops\nn_ops.py in __call__(self, inp, filter)
    237         padding=self.padding,
    238         data_format=self.data_format,
--> 239         name=self.name)
    240
    241

~\anaconda3\lib\site-packages\tensorflow_core\python\ops\nn_ops.py in conv2d(input, filter, strides, padding, use_cudnn_on_gpu, data_format, dilations, name, filters)
   2009                            data_format=data_format,
   2010                            dilations=dilations,
-> 2011                            name=name)
   2012
   2013

~\anaconda3\lib\site-packages\tensorflow_core\python\ops\gen_nn_ops.py in conv2d(input, filter, strides, padding, use_cudnn_on_gpu, explicit_paddings, data_format, dilations, name)
    931             input, filter, strides=strides, use_cudnn_on_gpu=use_cudnn_on_gpu,
    932             padding=padding, explicit_paddings=explicit_paddings,
--> 933             data_format=data_format, dilations=dilations, name=name, ctx=_ctx)
    934       except _core._SymbolicException:
    935         pass  # Add nodes to the TensorFlow graph.

~\anaconda3\lib\site-packages\tensorflow_core\python\ops\gen_nn_ops.py in conv2d_eager_fallback(input, filter, strides, padding, use_cudnn_on_gpu, explicit_paddings, data_format, dilations, name, ctx)
   1020   explicit_paddings, "data_format", data_format, "dilations", dilations)
   1021   _result = _execute.execute(b"Conv2D", 1, inputs=_inputs_flat, attrs=_attrs,
-> 1022                              ctx=ctx, name=name)
   1023   if _execute.must_record_gradient():
   1024     _execute.record_gradient(

~\anaconda3\lib\site-packages\tensorflow_core\python\eager\execute.py in quick_execute(op_name, num_outputs, inputs, attrs, ctx, name)
     65     else:
     66       message = e.message
---> 67     six.raise_from(core._status_to_exception(e.code, message), None)
     68   except TypeError as e:
     69     keras_symbolic_tensors = [

~\anaconda3\lib\site-packages\six.py in raise_from(value, from_value)

UnknownError: Failed to get convolution algorithm. This is probably because cuDNN failed to initialize, so try looking to see if a warning log message was printed above. [Op:Conv2D]

I've tried the solutions mentioned here https://forums.developer.nvidia.com/t/could-not-create-cudnn-handle-cudnn-status-alloc-failed/108261/2 but to no avail.
Provide the exact sequence of commands / steps that you executed before running into the problem
I've tried using Tensorflow GPU accelerator in google colab with local runtime on my machine, I've followed all the steps precisely on https://www.tensorflow.org/install/gpu
Any other info / logs
this is the log from the jupyter terminal:
2020-08-09 04:37:22.168805: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cudart64_101.dll
2020-08-09 04:37:24.322956: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2
2020-08-09 04:37:24.329330: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library nvcuda.dll
2020-08-09 04:37:25.599803: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1555] Found device 0 with properties:
pciBusID: 0000:01:00.0 name: GeForce RTX 2060 computeCapability: 7.5
coreClock: 1.335GHz coreCount: 30 deviceMemorySize: 6.00GiB deviceMemoryBandwidth: 312.97GiB/s
2020-08-09 04:37:25.607874: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cudart64_101.dll
2020-08-09 04:37:25.616921: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cublas64_10.dll
2020-08-09 04:37:25.626584: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cufft64_10.dll
2020-08-09 04:37:25.635135: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library curand64_10.dll
2020-08-09 04:37:25.650044: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cusolver64_10.dll
2020-08-09 04:37:25.659390: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cusparse64_10.dll
2020-08-09 04:37:25.681098: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cudnn64_7.dll
2020-08-09 04:37:25.686397: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1697] Adding visible gpu devices: 0
2020-08-09 04:37:26.217444: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1096] Device interconnect StreamExecutor with strength 1 edge matrix:
2020-08-09 04:37:26.222044: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1102]      0
2020-08-09 04:37:26.225124: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1115] 0:   N
2020-08-09 04:37:26.228586: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1241] Created TensorFlow device (/device:GPU:0 with 4604 MB memory) -> physical GPU (device: 0, name: GeForce RTX 2060, pci bus id: 0000:01:00.0, compute capability: 7.5)
2020-08-09 04:37:26.239786: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1555] Found device 0 with properties:
pciBusID: 0000:01:00.0 name: GeForce RTX 2060 computeCapability: 7.5
coreClock: 1.335GHz coreCount: 30 deviceMemorySize: 6.00GiB deviceMemoryBandwidth: 312.97GiB/s
2020-08-09 04:37:26.249100: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cudart64_101.dll
2020-08-09 04:37:26.254350: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cublas64_10.dll
2020-08-09 04:37:26.260971: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cufft64_10.dll
2020-08-09 04:37:26.265307: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library curand64_10.dll
2020-08-09 04:37:26.271569: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cusolver64_10.dll
2020-08-09 04:37:26.276251: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cusparse64_10.dll
2020-08-09 04:37:26.281798: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cudnn64_7.dll
2020-08-09 04:37:26.287682: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1697] Adding visible gpu devices: 0
2020-08-09 04:37:26.291846: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1096] Device interconnect StreamExecutor with strength 1 edge matrix:
2020-08-09 04:37:26.298235: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1102]      0
2020-08-09 04:37:26.300794: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1115] 0:   N
2020-08-09 04:37:26.305262: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1241] Created TensorFlow device (/device:GPU:0 with 4604 MB memory) -> physical GPU (device: 0, name: GeForce RTX 2060, pci bus id: 0000:01:00.0, compute capability: 7.5)
2020-08-09 04:37:26.313775: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1555] Found device 0 with properties:
pciBusID: 0000:01:00.0 name: GeForce RTX 2060 computeCapability: 7.5
coreClock: 1.335GHz coreCount: 30 deviceMemorySize: 6.00GiB deviceMemoryBandwidth: 312.97GiB/s
2020-08-09 04:37:26.328318: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cudart64_101.dll
2020-08-09 04:37:26.339994: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cublas64_10.dll
2020-08-09 04:37:26.345874: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cufft64_10.dll
2020-08-09 04:37:26.352587: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library curand64_10.dll
2020-08-09 04:37:26.359694: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cusolver64_10.dll
2020-08-09 04:37:26.365286: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cusparse64_10.dll
2020-08-09 04:37:26.371099: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cudnn64_7.dll
2020-08-09 04:37:26.375749: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1697] Adding visible gpu devices: 0
2020-08-09 04:37:26.380113: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1555] Found device 0 with properties:
pciBusID: 0000:01:00.0 name: GeForce RTX 2060 computeCapability: 7.5
coreClock: 1.335GHz coreCount: 30 deviceMemorySize: 6.00GiB deviceMemoryBandwidth: 312.97GiB/s
2020-08-09 04:37:26.393424: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cudart64_101.dll
2020-08-09 04:37:26.403150: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cublas64_10.dll
2020-08-09 04:37:26.408577: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cufft64_10.dll
2020-08-09 04:37:26.423141: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library curand64_10.dll
2020-08-09 04:37:26.428838: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cusolver64_10.dll
2020-08-09 04:37:26.434061: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cusparse64_10.dll
2020-08-09 04:37:26.438479: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cudnn64_7.dll
2020-08-09 04:37:26.443288: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1697] Adding visible gpu devices: 0
2020-08-09 04:37:26.446511: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1096] Device interconnect StreamExecutor with strength 1 edge matrix:
2020-08-09 04:37:26.453204: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1102]      0
2020-08-09 04:37:26.458931: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1115] 0:   N
2020-08-09 04:37:26.463016: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1241] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 4604 MB memory) -> physical GPU (device: 0, name: GeForce RTX 2060, pci bus id: 0000:01:00.0, compute capability: 7.5)
2020-08-09 04:37:26.823644: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library cudnn64_7.dll
2020-08-09 04:37:27.877441: E tensorflow/stream_executor/cuda/cuda_dnn.cc:329] Could not create cudnn handle: CUDNN_STATUS_ALLOC_FAILED
2020-08-09 04:37:27.882143: E tensorflow/stream_executor/cuda/cuda_dnn.cc:329] Could not create cudnn handle: CUDNN_STATUS_ALLOC_FAILED

Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

@elarbi93
I have tried in colab with TF version 2.1, 2.3 and i am not seeing any issue.Please, find the gist here.
The possible solution which I found can be found in #24828.Thanks!

@elarbi93
Please add the CUDA, CUPTI, and cuDNN installation directories to the %PATH% environmental variable.Please refer this doc. Thanks!

@elarbi93
Please add the CUDA, CUPTI, and cuDNN installation directories to the %PATH% environmental variable.Please refer this doc. Thanks!

as you can see, I already got those in my environmental variables

@elarbi93
I have tried in colab with TF version 2.1, 2.3 and i am not seeing any issue.Please, find the gist here.
The possible solution which can be found in #24828.Thanks!

I've tried it with TF 2.1, 2.2 and 2.3 and I saw no difference, I've also checked the attached issue before and tried the solutions mentioned there but to no avail.

I also opened this issue but I don't know some people closed that saying set allow_growth=True and closed it. But that's not permanent solution, so since then trying different things.
Literally, when I installed only Visual Studio 2019 and created a Virtual Environment with tensorflow-gpu==2.3.0. Trust me on this, I ran a sample code which I get this error in previous which is:
import tensorflow as tf
inp = tf.random.normal([32,10,8])
lsmt_out = tf.keras.layers.LSTM(4)(inp)
I didn't get error, believe me! I thought wow, it worked but then I messed it up or I didn't. I installed Anaconda and installed tensorflow-gpu=2.3.0 same. And run that code, Unfortunately I got error saying this thing. And when i ran this on Visual Studio virtual environment, to my freaking misluck I am getting this error. I will definitely find some solution. Trust me on this one.

Tested  the issue with TF v2.5 with no error ,please find the gist here ..Thanks!


re-deprecate opaque Struct config

Structs are deprecated once and un-deprecated in #6346. Now protobuf hashing are sorted and moving away from hashing in long term (#8231, #8301). So we can deprecate this and migrate all docs/examples.
cc @htuch @alyssawilk @moderation

@lizan agreed. We have a short window to have the deprecation actually remove it from v3, if you can land the relevant PRs in the next week or so. If not, we can do the deprecation in v3 and removal in v4.

Actually, while working on https://github.com/envoyproxy/envoy/issues/8082, I realized that it might end up being best to tackle this in 1.12.0. Specifically, if we can ensure all opaque Structs have a type URL included, we can identify whether a Struct is from v2 or v3alpha. After chatting with @lizan, the best course of action seems to be:

Deprecate the existing untyped Struct fields.
Introduce a new typed Struct, e.g.

message TypedStruct {
  string type_url = 1;
  google.protobuf.Struct value = 2;
}

The v3alpha API will no longer have the untyped Struct fields, and we can use the type_url going forward to figure out major version.
In addition to tagging the relevant fields as deprecated, we need to:

Implement the ability for Envoy to accept TypedStruct embedded inside Any fields. There should be some validation that the type_url matches the filter's empty proto type name.
Update all docs and examples to typed configs.

There's a few places missed from #8472, @yanavlasov can you deprecate them as well?
api/envoy/api/v2/auth/cert.proto:113:    google.protobuf.Struct config = 2;
api/envoy/api/v2/listener/udp_listener_config.proto:26:    google.protobuf.Struct config = 2;
api/envoy/config/filter/accesslog/v2/accesslog.proto:248:    google.protobuf.Struct config = 2;


How Can I handle no response?

If i don't have any response from destination, how can i handle the result(no response)?

If you set a timeout interval in the PingConfiguration, it will trigger a timeout error if no response is received within the specified interval.


[Drawer] flicker when zooming in on Chrome

Steps to reproduce

Render a drawer, or just go to the material-ui website
Zoom in the page
You can see the drawer flicker (playing the transition)

In comparison, Firefox doesn't seem to have the issue.  Also doesn't happen when zooming-out.
Versions

Material-UI: 0.15.4
React: 15.3.1
Browser: Chrome 51.0.2704.106 on Linux

Sounds like a Chrome rendering issue.


Added reaction-timer uwp project under_site/demo/uwp

UWP section
Added a reaction timer uwp
Here the gif demo:

Let me know if you want a small how to

Thanks! It would be awesome if you could write a tutorial so that users know how to recreate it!

@samayshamdasani Please review my GettingStarted file!

Looks good, but do you mind submitting another pull request that's in the root demo file - and not the one under _site? _site has just the compiled static files and it gets overwritten...

Ok i think its ok now!


Selected object contains git sign and dev icon

Info

Operating System: MacOS
Shell: ZSH
Terminal: Alacritty
nvim --version: 0.8.0
fzf --version: 0.33.0(brew)

[ ] The issue is reproducible with mini.sh

fzf-lua configuration

local fzf_lua = require('fzf-lua')
local util = require('util')
local profile = require('profile')

fzf_lua.setup {
  winopts = {
    preview = { default = 'bat_native' },
    height = 0.6,
    width = 0.6,
  }
}

local buf_opt = { noremap = true, silent = true }
util.nmap(
  '<C-M-f>',
  "<cmd>lua require('fzf-lua').files()<CR>",
  buf_opt
)

local obj = {}
obj.foo = function()
  require 'fzf-lua'.files({
    fzf_opts = { ['--preview-window'] = 'nohidden,down,50%' },
    actions = {
      ['ctrl-y'] = {
        function(selected)
          print("selected:", selected[1])
          -- uncomment to enable deletion
          -- vim.fn.delete(selected[1])
        end,
        require 'fzf-lua'.actions.resume
      }
    }
  })
end

return obj

Description
I'm trying to write a custom defined functionality with fzf-lua. With the foo function in my configuration, If i hit Ctrl-y key, then the selected item will be printed in the excution line. However, as you can see in the picture below, the selected item is being printed with dev icons and git signs. Is there any way to get the absolute path just like how fzf works in terminal?

To setup the dev icon you can use the path module to parse the entry.
To get the full path join with the current working directory
local path = require("fzf-lua").path

local custom_action = function(selected, opts)
  local entry = path.entry_to_file(selected[1])
  local fullpath = entry.path
  if not path.starts_with_separator(fullpath) then
    fullpath = path.join({ opts.cwd or vim.loop.cwd(), fullpath })
  end
  print(fullpath)
end

Great answer. thanks!


Do not add CSS shorthands in runtime

We don't allow to use CSS shorthands:
https://github.com/microsoft/griffel/blob/b4c7acc77e5e7b4883ca32249418a3d93dc43e77/packages/core/src/types.ts#L5-L49
We should implement something in runtime to prevent adding rules with shorthands. Currently shorthands usage produces TS errors, but rules are still inserted to DOM. That creates confusion and feeling that something is wrong with typings.

This should be based on typings that we have
The runtime check should be development (non-production) to avoid contributions to bundle size

Expected behavior
import { makeStyles } from "@griffel/react";

const useClasses = makeStyles({
  root: {
    // ⏭ "background" is not inserted to DOM & a warning is produced (currently inserted)
    // 💥 produces TS error (already done)
    background: "red"
  }
});

I have a question, why don't we support this writing style?

@Aloento you find out more details in that comment, https://github.com/microsoft/griffel/issues/30#issuecomment-1045959297. If you have questions, let's continue there.

Maybe your document seems like didn't mention that.
and I don't know why I can't scroll down your docs page
https://user-images.githubusercontent.com/11802769/164110688-ea06a010-fefc-41e1-a1dd-b6f58553da75.mp4
.

Maybe your document seems like didn't mention that.
and I don't know why I can't scroll down your docs page

This looks really strange. Can you please share details about your environment? OS, browser?

@layershifter Microsoft Edge 100.0.1185.44, Windows 11 64bit

@Aloento you find out more details in that comment, #30 (comment). If you have questions, let's continue there.

https://github.com/microsoft/fluentui/blob/master/rfcs/react-components/convergence/no-css-shorthands-in-make-styles.md


update config directory in docs

to match path hardcoded in selfmedicate.sh
See: selfmedicate.sh file at master at line 12

Excellent, thank you.


chore(PR_TEMPLATE): update link to writer's guide

Current coverage is 86.40% (diff: 100%)

Merging #362 into master will not change coverage

@@             master       #362   diff @@
==========================================
  Files             4          4
  Lines           331        331
  Methods          68         68
  Messages          0          0
  Branches         69         69
==========================================
  Hits            286        286
  Misses           45         45
  Partials          0          0

Powered by Codecov. Last update 13c72b2...8106243


sync upstream KF into midstream ODH

this will require a new image build

/approve

@tarilabs not sure this was really merged with merge-commit :thinking:

@tarilabs @rkubis not sure this was really merged with merge-commit 🤔

yes, that's a BIG problem the label was maintained: https://github.com/opendatahub-io/model-registry/pull/15#event-11995977332


Provide timestamps metrics about WM job

Fixes #11604
Status
In development
Description
Provides timestamps metrics, job wall clock time, etc. (in GMT and UNIX since epochs data-format), to WMCore FJR (Report.pkl) file during job execution script
Is it backward compatible (if not, which system it affects?)
YES
Related PRs
#11575 , https://github.com/dmwm/WMCore/pull/11659
External dependencies / deployment changes

test this please

test this please

test this please

@amaltaro , additional (independent) WMArchive changes can be found in https://github.com/dmwm/WMCore/pull/11659 and https://github.com/dmwm/WMArchive/pull/360

@amaltaro , I adjusted the code to provide only TotalWallClockTime under Timing. But this is a question for me now. Originally I created Timing section to include 4 metrics, but now if we have only one does it make sense to have Timing section with one metric? May be we should put TotalWallClockTIme at top level of the document. Please provide your feedback that I can correct the codebase.

I forgot to mention, I believe the next steps are:

test these changes at runtime
look into ArchiveDataReporter to start publishing this new metric, otherwise it will be contained only in the agent.

@amaltaro , I fixed all pylint/pep suggestions and jenkins build is clean now. Please review again.

test this please

test this please

Alan, I made necessary changes. Regarding your question about possibility of empty file, it can be as simple as local file storage is full (disk reaches 100% of its capacity, or someone by mistake change permission of the file, etc.) Botton line, the check is useful before you (re)write and if you need a rewrite a file you better save previous version.

If disk is full, then you cannot create the new pickle file either. If permissions are wrong, then it would have failed in previous steps that write that report. In addition, it is created by the user running the job, so there are no expected permission issues.
On what concerns location of the script, as we have specific sub-packages under WMRuntime, my preference is to use the Scripts sub-package. Please see this comment for specifics:
https://github.com/dmwm/WMCore/pull/11656#issuecomment-1660540621

Alan, the disk can become full once you write first pickle file such that there is no room to write another one since its size will be bigger than original file.

Yes, and if disk becomes full after you write the first pickle file, it would of course fail to write the pickle.new that you implemented in the script. In other words, there is no extra protection offered by creating a new file + move compared to updating the current pickle.

Alan, I don't want to argue more, but it is a possibility on system which support multiple users or jobs that when I write first file and second file then I'll not have disk space to overwrite original file, and there is a possibility that  during a time when I'll overwrite existing file the disk will not be filled with other stuff by another user or process. In other words, the original file may be lost and this is what I try to avoid by writing completely new file and only then (when both are written and safe) to overwrite original file. If you still think that few lines of code is worth to remove to make code simpler but still open a possibility to lost original file I'll be happy to remove them.

test this please

Alan, I resolved issues you pointed out and adjusted code with pep8 suggestions. Now it is clean. Please have a final review of this PR.

It needs to be squashed and initial description updated.

Jenkins reported the following failure:
WMCore_t.WMSpec_t.Steps_t.Executors_t.CMSSW_t.CMSSW_t:testSubprocessTime was added with status failure. Must be fixed

which should not fail IMO. You might want to reproduce it tomorrow with the docker unit test image.

Alan, I looked at jenkins log output and it complains about test provided in #11665 in particular at this line:
https://github.com/dmwm/WMCore/pull/11665/files#diff-b66e4eefedb43252aea569121f9e099cf9166a8c732af9923b4568b89409e73dR264
It means that subprocess didn't sleep (as in test I provided a sleep 1 function). I'm not sure how this happens but I may adjust this test to either have larger interval, or use a different command, like ls or df or du, and/or modify test condition to be self.assertTrue(userTime1 >= userTime0). Let me know if you prefer any of this solution and I can provide separate PR to the test in question.


[BUG] filelist's findall() should prefer original over links

setuptools version
62.1.0
Python version
3.8.13
OS
Windows 10
Additional environment information
No response
Description
When trying to package an sdist of a library I maintain, certain folders were no longer being included when using a recent version of setuptools. Stepping through the code with PDB, I realized that the UniqueFolder filter was excluding them (introduced in https://github.com/pypa/setuptools/pull/2714). For context, this is the kind of folder setup in use:
folderA/links/[symlink to folderB]
folderA/links/[symlink to folderC]
folderB/links/[symlink to folderC]
folderC

The problem is that instead of including folderB and folderC, only the links in folderA/links is included.
For me, these links gets created as part of some Javascript assets that I build an distribute with my package (https://github.com/vidartf/ipydatawidgets). The workarounds I can see:

Rename the folders so that os.walk traverses them in the "right" order. This is brittle as the docs for os.walk says "Whether or not the lists are sorted depends on the file system." This is another argument for why the current implementation is also problematic: The paths of the files that get included in your build are dependent on the OS implementation details!
Add a separate build step that unlinks these folders before building, and then re-links them afterwards.

Expected behavior
The expectation would be that the original folders (folderA, folderB and folderC) are all included, and if anything the symlinks pointing to them are excluded.
How to Reproduce
import tempfile
import os
import pathlib
from setuptools._distutils.filelist import findall

with tempfile.TemporaryDirectory() as root:
    d = pathlib.Path(root)
    os.mkdir(d / "A")
    os.mkdir(d / "B")
    os.mkdir(d / "C")
    (d / "A" / "fileinA.txt").write_text("foo")
    (d / "B" / "fileinB.txt").write_text("foo")
    (d / "C" / "fileinC.txt").write_text("foo")
    # Note: This will work if the sort order is changed!
    os.symlink(d / "C", d / "B" / "linkC", target_is_directory=True)
    os.symlink(d / "C", d / "A" / "linkC", target_is_directory=True)
    os.symlink(d / "B", d / "A" / "linkB", target_is_directory=True)

    files = findall(d)
    print(files)

Output
[
'<tmp root>\\tmpjswv9fx2\\A\\fileinA.txt',
'<tmp root>\\tmpjswv9fx2\\A\\linkB\\fileinB.txt',
'<tmp root>\\tmpjswv9fx2\\A\\linkB\\linkC\\fileinC.txt'
]

Possible solutions that I see:

Do not follow symlinks in the walk.
Only prevent infinite recursions, instead of enforcing folder uniqueness.
Only follow symlinks if the target they point to would not also be included in the walk.


Webcomponent not connected when using insertAdjacentHTML

Bug report
A skate web component is not correctly connected when using insertAdjacentHTML to add the html.

Skate version: 5.1.1

Affected browsers (and versions): Chrome

Current behaviour
If you use the following code, mySkateComponent is not connected, i.e. the custom tag is not connected to the web component javascript.
document.body.insertAdjacentHTML('beforeend', '<mySkateComponent></mySkateComponent>');
However, if I do it like this, everything works as expected:
document.body.insertAdjacentHTML('beforeend', '

'); document.querySelector('#myDiv').innerHTML= '<mySkateComponent></mySkateComponent>';
Expected behaviour
Adding a web component via  insertAdjacentHTML should also work.

This sounds like a bug in Chrome as Skate doesn't do anything with the native methods. Does innerHTML work?

Thank you for the investigation. Yes, innerHTML does work.

Yeah, I think it's probably a bug in the shadow DOM polyfill. Best to probably raise an issue over there :)


Remove unused internal functions evp_pkey_ctx_get1_id_prov and evp_pkey_ctx_get1_id_len_prov

Fixes #20701
Remove unused internal functions evp_pkey_ctx_get1_id_prov and evp_pkey_ctx_get1_id_len_prov

CI is relevant.

As this is just removal it would be acceptable with CLA: trivial.

Maybe I should also remove get1_id_data function, which is not used after the changes and so failed checks?

And can I do the same Pull Request in the 3.0 branch, because I use this branch? And what about 3.1 branch?

Maybe I should also remove get1_id_data function, which is not used after the changes and so failed checks?

Yes, please.

And can I do the same Pull Request in the 3.0 branch, because I use this branch? And what about 3.1 branch?

This will not be merged to 3.0 branch as this is just a cleanup and not a bug fix.

Is there anything else I need to do?

We will squash the commits when merging.

Is evp_pkey_ctx_set1_id_prov() used anywhere?

Is evp_pkey_ctx_set1_id_prov() used anywhere?

I agree with this. Function evp_pkey_ctx_set1_id_prov() is not used now and there is function EVP_PKEY_CTX_set1_id instead

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

What else can I do?

Merged to master, thanks for the contribution.


test_s3:test_bucket_list_return_data_versioning bug

@zhangsw for this test case : s3tests.functional.test_s3:test_bucket_list_return_data_versioning
need to changes in boto/s3/key.py endElement  function as well, otherwise test case always failed , could u help to check? Thanks
def endElement(self, name, value, connection):         if name == 'Key':             self.name = value         elif name == 'ETag':             self.etag = value         elif name == 'IsLatest':             if value == 'true':                 self.is_latest = True             else:                 self.is_latest = False         elif name == 'LastModified':             self.last_modified = value         elif name == 'Size':             self.size = int(value)         elif name == 'StorageClass':             self.storage_class = value         elif name == 'Owner':             pass         elif name == 'VersionId':             self.version_id = value         else:             setattr(self, name, value)
need to set key's  'Content-Encoding'

@YuanyuanZh I test it on ceph master branch and it is passed.

If GET key doesn't return Content-Encoding header, this test will pass , since eq(key.content_encoding, key_data['content_encoding']), both side is None. As I know AWS GET/HEAD key doesn't return Content-Encoding header, if you don't specify the Content-Encoding header when you create the key. But if you provide Content-Encoding header when you create key, this test will failed.Did you test this case?

Yes, you're right! But unfortunately we can't modify the boto... Maybe we should remove the ‘Content-Encoding’.


Give better error messages when provides is missing in header

Fixes this issue

Thanks @KilianVounckx :)
Could you add a test for this case (as shown in the issue) as well?

Do I just add a test at the end of crates/reporting/tests/test_reporting.rs for this?

It would probably be best to add it after this test


Brute force web research

Research Chain
This is an experimental research chain that tries to answer "researchy" questions using information on the web.
For example,
Compile information about Albert Einstein.
Ignore if it's a different Albert Einstein.
Only include information you're certain about.

Include:
* education history
* major contributions
* names of spouse
* date of birth
* place of birth
* a 3 sentence short biography

Format your answer in a bullet point format for each sub-question.

Or replace Albert Einstein with another person of interest (e.g., John Smith of Boston).
The chain is composed of the following components:

A searcher that searches for documents using a search engine.

The searcher is responsible to return a list of URLs of documents that
may be relevant to read to be able to answer the question.

A downloader that downloads the documents.
An HTML to markdown parser (hard coded) that converts the HTML to markdown.

Conversion to markdown is lossy
However, it can significantly reduce the token count of the document
Markdown helps to preserve some styling information
(e.g., bold, italics, links, headers) which is expected to help the reader
to answer certain kinds of questions correctly.

A reader that reads the documents and produces an answer.

Limitations

Quality of results depends on LLM used, and can be improved by providing more specialized parsers (e.g., parse only the body of articles).
If asking about people, provide enough information to disambiguate the person.
Content downloader may get blocked (e.g., if attempting to download from linkedin) -- may need to read terms of service / user agents appropriately.
Chain can be potentially long running (use initialization parameters to control how many options are explored) -- use async implementation as it uses more concurrency.
This research chain only implements a single hop at the moment; i.e.,
it goes from the questions to a list of URLs to documents to compiling answers.
Without continuing the crawl, web-sites that require pagination will not be explored fully.
The reader chain must match the type of question. For example, the QA refine chain
isn't good at extracting a list of entries from a long document.

Extending

Continue crawling documents to discover more relevant pages that were not surfaced by the search engine.
Adapt reading strategy based on nature of question.
Analyze the query and determine whether the query is a multi-hop query and change search/crawling strategy based on that.
Break components into tools that can be exposed to an agent. :)
Add cheaper strategies for selecting which links should be explored further (e.g., based on tf-idf similarity instead of gpt-4)
Add a summarization chain on top of the individually collected answers.
Improve strategy to ignore irrelevant information.

i try to run and encounter
File ~/workplace/langchain/langchain/chains/research/search.py:149, in _run_searches(queries, top_k)
    147         organic_results = result["organic_results"]
    148     else:
--> 149         organic_results = result["organic_results"][:top_k]
    150     results.extend(organic_results)
    151 return results

KeyError: 'organic_results'

Have you tried async version? I may have messed up the sync path

Fixed up the organic_results looks like upstream API treated it as an optional key.
@hwchase17 if we want to commit any parts of this -- we should cut out the blob crawler (since it's not hooked up yet). Also can add tests to catch some issues like the one above, but up to you.


feat(booking): add new fields to passenger data

add new loyalty programme fields to the OfferRequestPassenger interface
validate new loyalty programme fields on order creation

Thanks @matthewp5 !


Establish Clear Contribution Guidelines

As an open source project, there is a currently lack clear guidelines for contributors. This absence of documentation makes it challenging for new contributors to understand how to effectively participate in the project. Specifically, there's uncertainty around how to structure pull requests for code reviews and other important aspects of the contribution process.
Key Issues to Address:

Lack of clear process for submitting contributions
Uncertainty about how to structure pull requests for effective code reviews
Absence of coding standards and best practices documentation

Proposed Solution:
Create a CONTRIBUTING.md file that addresses these issues and provides clear guidance for contributors. This document should cover:

Introduction to the project and its goals
Step-by-step guide on how to contribute

How to set up the development environment
Process for finding or creating issues to work on
How to fork the repository and create branches

Pull Request guidelines

How to structure PRs (e.g., size, scope, breaking up large changes)
Commit message format
Required documentation or tests

Code review process

What to expect during review
How to respond to feedback

Coding standards and best practices
Testing requirements
Documentation guidelines

Benefits:

Lowers the barrier to entry for new contributors
Ensures consistency in contributions and code quality
Streamlines the review process for maintainers
Improves overall project organization and documentation

Thank you for the very helpful suggestion! We just add an initial CONTRIBUTING.md to convey what we are specifically looking for help at this stage.
I will keep this issue open and welcome suggestions from everyone.


solarlfish isn't registered as a valid RDoc generator

Ruby 2.7.0, RDoc 6.2.1
$ rdoc -o solarfishdoc -f solarfish
invalid options: -f solarfish
(invalid options are ignored)
Parsing sources...

I hope it's fixed.


Docker compose with webpack

I've added dev mode for webpack in docker-compose
Command to run app: docker-compose -f docker-compose.yml -f docker-compose.dev.yml up
There is problem with node-sass: it should be compiled for a specific OS.
It was solved so:

docker installs npm modules in tmp files
docker-comopose mount host folders to container (cvat-ui, cvat-core, cvat-canvas)
in case when there is no node_modules folder it will be copied from container to local machine (once at first run)

@nglazov , as discussed a debugging session can be started using npm start command and it is more convenient for now.


Cannot commit and push container image from Kubernetes pods

Hello folks! :wave:
I'm experiencing a strange behavior while committing a container (from Kubernetes pod) and pushing it to some container registry after. I always get the same error from the push command: content digest sha256:898c46f3b1a1f39827ed135f020c32e2038c87ae0690a8fe73d94e5df9e6a2d6: not found.
I'm filing this issue here but there's a chance the problem is on containerd side because I've already seen it working in an earlier version. I'm trying to find out which version it stopped to work.
I'm still investigating but no idea so far... suggestions are welcome.
Steps to reproduce:

Create an arbitrary Kubernetes pod (for simplicity w/ just one container).

$ kubectl run --image tsuru/go:latest my-app -- sleep Inf

Execute arbitrary commands to generate changes in the container image (to be committed):

$ kubectl exec my-app -- mkdir -p /tmp/foo/bar

Commit the container to a local image:

$ CONTAINER_ID=$(kubectl get pods my-app -o 'jsonpath={ .status.containerStatuses[0].containerID }' | sed -E 's|(.+)://||g')
$ nerdctl --namespace k8s.io commit ${CONTAINER_ID} registry.example.com/my-app:v1

Push to local registry (no credentials needed):

$ nerdctl --namespace k8s.io push registry.example.com/my-app:v1
FATA[0000] failed to create a tmp single-platform image "registry.example.com/my-app:v1-tmp-reduced-platform": content digest sha256:898c46f3b1a1f39827ed135f020c32e2038c87ae0690a8fe73d94e5df9e6a2d6: not found

Environment information:

nerdctl:  0.17.0
containerd: v1.4.12 7b11cfaabd73bb80907dd23182b9347b4245eb5d
OS: Buildroot 2021.02.4 (from minikube)
Kernel: 4.19.202
Kubernetes version: v1.20.6
kubectl version: v1.20.6
Minikube: v1.25.1

I can't reproduce this problem on containerd with latest and 1.5.10 version.
jun@lima-k8s-test:~$ kubectl version
Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.6", GitCommit:"8a62859e515889f07e3e3be6a1080413f17cf2c3", GitTreeState:"clean", BuildDate:"2021-04-15T03:28:42Z", GoVersion:"go1.15.10", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.6", GitCommit:"8a62859e515889f07e3e3be6a1080413f17cf2c3", GitTreeState:"clean", BuildDate:"2021-04-15T03:19:55Z", GoVersion:"go1.15.10", Compiler:"gc", Platform:"linux/amd64"}
jun@lima-k8s-test:~$ containerd -v
containerd containerd.io 1.5.10 2a1d4dbdb2a1030dc5b01e96fb110a9d9f150ecc

In addition, I can't start the corresponding containerd version through minikube.

I closed it because containerd v1.4.x reached EOL.
Feel free to open it up if you have any other questions.

could you please open this issue, @junnplus  thanks.
I meet the same problem :  I commit the image from a  running container, then i need push the new image to my repo.
when i use   nerdctl -n k8s.io push  xxx  ,an error occurs:
FATA[0000] failed to create a tmp single-platform image "xxx.com/hjmtest/nginx:hjm-tmp-reduced-platform": content digest sha256:550fe1bea624a5c62551cf09f3aa10886eed133794844af1dfb775118309387e: not found
here is my env info:
nerdctl -v nerdctl version 1.4.0
containerd -v  containerd github.com/containerd/containerd v1.6.14-42-g21f32b2c3 21f32b2c394bc1ccfbf1744876a0fcdd4ef2390d

could you please open this issue, @junnplus thanks. I meet the same problem : I commit the image from a running container, then i need push the new image to my repo. when i use nerdctl -n k8s.io push xxx  ,an error occurs: FATA[0000] failed to create a tmp single-platform image "xxx.com/hjmtest/nginx:hjm-tmp-reduced-platform": content digest sha256:550fe1bea624a5c62551cf09f3aa10886eed133794844af1dfb775118309387e: not found
here is my env info: nerdctl -v nerdctl version 1.4.0 containerd -v containerd github.com/containerd/containerd v1.6.14-42-g21f32b2c3 21f32b2c394bc1ccfbf1744876a0fcdd4ef2390d

In addition:
if i pull images from others, not commit a new image, nerdctl can work.

I got the same issue but with finch.
Solved with --platform arg:
finch push xxx.dkr.ecr.us-east-1.amazonaws.com/infra/calico/apiserver:v3.25.1 --platform linux/amd64

WARN[0000] unable to determine buildctl version: exec: "buildctl": executable file not found in $PATH
Client:
 Version:       v1.5.0
 OS/Arch:       linux/amd64
 Git commit:    b33a58f288bc42351404a016e694190b897cd252
 buildctl:
  Version:

Server:
 containerd:
  Version:      1.7.1+azure-1
  GitCommit:    1677a17964311325ed1c31e2c0a3589ce6d5c30d
 runc:
  Version:      1.1.7
  GitCommit:    860f061b76bb4fc671f0f9e900f7d80ff93d4eb7

could not produce this bug. would you guys mind to give me reproduce step with more detail? like what's registry you use

Recently, my GKE cluster's worker node upgraded to v1.27.3-gke.100 which also upgraded containerd from 1.6.18 to 1.7.0. After the upgrade, I encountered the exact same issue.
Client:
 Version:	v1.7.0
 OS/Arch:	linux/amd64
 Git commit:	e674fe7ba6e49f12e88cd9c6c442e7ea5232502c
 buildctl:
  Version:	v0.12.3
  GitCommit:	438f47256f0decd64cc96084e22d3357da494c27

Server:
 containerd:
  Version:	1.7.0
  GitCommit:	1fbd70374134b891f97ce19c70b6e50c7b9f4e0d
 runc:
  Version:	1.1.10
  GitCommit:	v1.1.10-0-g18a0cb0f

Reproduce
The commit command: nerdctl -n k8s.io commit bbe68406a258 some.registry.com/my-app:0.1
The push command like: nerdctl -n k8s.io push some.registry.com/my-app:0.1
Output: FATA[0000] failed to create a tmp single-platform image "some.registry.com/my-app:0.1-tmp-reduced-platform": content digest sha256:c95ff01263cbbb536e71f8ae823d3e63f15f7a0f1ba9ecb7b3126a63654d2b23: not found.
Work around
Add --all-platforms option.
If I run the push command like: nerdctl -n k8s.io push --all-platforms some.registry.com/my-app:0.1, the image can be pushed if the registry is valid.
The option is added to avoid converter.Convert. Related code:
https://github.com/containerd/nerdctl/blob/ce2f63d275c80f1ba2a3e2d9bfdc15ded3ff73c7/pkg/cmd/image/push.go#L98-L111
Other info
The issue is not registry related. I tried different registries, the same error is thrown, even with random invalid registry.
The container I am committing from is built on an Ubuntu machine with docker build . command, without specifying the platform as linux/amd64.

I started a container using the nydus format and then packaged the container into an image. However, I encountered the same problem when I tried to push this image.
Steps to reproduce:

Create an container with nydus image

nerdctl --snapshotter nydus run --cap-add=CAP_SYS_ADMIN  --net host -it  registry-test.xx.info/library/nydus-image:old

Commit the container to a local image:

nerdctl  commit ${CONTAINER_ID} registry-test.xx.info/library/nydus-image:new

Push to registry (no credentials needed):

nerdctl push registry-test.xx.info/library/nydus-image:new
FATA[0000] failed to create a tmp single-platform image " registry-test.xx.info/library/nydus-image:new-tmp-reduced-platform": content digest sha256:cfc7393224358fb100dabf40f7d59c2578c0a6a47781b1a6b56406922aeb6e95: not found

env info:

Kernel: 4.9.144
nerdctl version 1.6.2
containerd: v1.5.9
nydusd version: v2.2.3
containerd-nydus-grpc version: v0.13.3
Does the container launched by on-demand loading of images support commit and push operations?

I have the same problem on Azure

env info:
kubernetes: v1.27.7
Kernel: 5.15.0-1053-azure
nerdctl version 1.7.3
containerd: 1.7.1+azure-1

Hi I'm having the same issue. Is there a specific version of containerd that I can use that doesn't have this problem?

I am encountering the same issue.
It seems to occur from kubernetes 1.27 version, and it remains unresolved even when using the latest version of nerdctl (1.7.6). As someone else pointed out, the --all-platforms or --platform flag does not work while pushing.
Looking at the issue, it seems that it starts from failing to save a committed image.
This has been an ongoing issue since the past and I am wondering if there have been any follow-ups on this matter.

this work for me : nerdctl tag with a new image neme ,then push again

Maybe config descriptor missed.
https://github.com/containerd/nerdctl/blob/main/pkg/imgutil/commit/commit.go#L245
err = content.WriteBlob(ctx, r.contentstore, configDesc.Digest.String(), bytes.NewReader(newConfigJSON), configDesc)
if err != nil {
   return nil, err
}

By default, commit image will not be unpacked to snapshots.
ctr --namespace=k8s.io i check
REF                                                                     TYPE                                                 DIGEST                                                                  STATUS           SIZE                UNPACKED
docker.io/cbluebird/devbox-system:latest                                application/vnd.oci.image.index.v1+json              sha256:895fdc91f14cab98864ab0c3b24752c42ff4d7c46bdeafca5f9f4d7e01f057a8 complete (3/3)   28.3 MiB/28.3 MiB   true
docker.io/lingdie/busybox:commit                                        application/vnd.docker.distribution.manifest.v2+json sha256:a7dce96e72a59c80479569d48a1376a36a2c2b0e9d2ba0e3dca707e2021d5e72 complete (4/4)   28.3 MiB/28.3 MiB   false

Unpacking the image may solve the problem:
ctr --namespace=k8s.io snapshots unpack sha256:a7dce96e72a59c80479569d48a1376a36a2c2b0e9d2ba0e3dca707e2021d5e72

nerdctl --namespace k8s.io image convert lingdie/busybox:commit lingdie/busybox:tmp
sha256:a7dce96e72a59c80479569d48a1376a36a2c2b0e9d2ba0e3dca707e2021d5e72

this pr may fix this:
https://github.com/containerd/nerdctl/pull/3268

@lingdie testing on main from today, the issue is still there (as described by OP).
Wondering what we are missing here...

Here is my testing process. Could you please provide your testing?

@lingdie
kind version 0.23.0
nerdctl latest main
ubuntu 24.04 (in lima on a mac M1 with Sonoma 14.5)
kind.yaml:
# https://pkg.go.dev/sigs.k8s.io/kind/pkg/apis/config/v1alpha4#Cluster
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
  - role: control-plane
    extraMounts:
      - hostPath: _output/nerdctl
        containerPath: /usr/local/bin/nerdctl
      - hostPath: /tmp/go
        containerPath: /usr/local/go
      - hostPath: .
        containerPath: /nerdctl-source

Create the cluster:
make binaries

KIND_EXPERIMENTAL_PROVIDER=nerdctl kind create cluster --config=./kind.yaml

nerdctl exec -ti kind-control-plane bash

Inside the control plane from above:
kubectl run --image debian my-app -- sleep Inf
kubectl exec my-app -- mkdir -p /tmp/foo/bar
CONTAINER_ID=$(kubectl get pods my-app -o "jsonpath={ .status.containerStatuses[0].containerID }" | sed -E "s|(.+)://||g")

nerdctl --namespace k8s.io commit ${CONTAINER_ID} registry.example.com/my-app:v1
nerdctl --namespace k8s.io push registry.example.com/my-app:v1

More info:
root@kind-control-plane:/# nerdctl info
Client:
 Namespace:	default
 Debug Mode:	false

Server:
 Server Version: v1.7.15
 Storage Driver: overlayfs
 Logging Driver: json-file
  Cgroup Driver:  : systemd
  Cgroup Version: : 2
 Plugins:
  Log:     fluentd journald json-file syslog
  Storage: native overlayfs fuse-overlayfs
 Security Options:
  apparmor
  seccomp
   Profile:	builtin
  cgroupns
 Kernel Version:   6.8.0-31-generic
 Operating System: Debian GNU/Linux 12 (bookworm)
 OSType:           linux
 Architecture:     aarch64
 CPUs:             4
 Total Memory:     3.814GiB
 Name:             kind-control-plane
 ID:               c74d79a4-7d13-4eca-ae50-6e2e95ae5043

WARNING: No swap limit support

@lingdie let me know if I am missing something here, or if you need anything.
Also, when we get #3296 in we will be able to test for Kube on the CI.

I encountered the same issue when using the same test plan as you.😥

And I found that the missing digest never existed in the image. This issue also occurred when I was implementing layer-suqash project. I fixed the issue by writing the config into the content store as well: https://github.com/labring/layer-squash/blob/main/pkg/runtime/runtime.go#L256

@lingdie there is clearly something wrong going on with this.
This issue keeps cropping up on a variety of operations - save, commit, with or without kube - https://github.com/containerd/nerdctl/pull/3179
I believe these have all the same root issue, but I cannot pinpoint it...

@lingdie there is clearly something wrong going on with this.
This issue keeps cropping up on a variety of operations - save, commit, with or without kube - #3179
I believe these have all the same root issue, but I cannot pinpoint it...
Regarding the issue of saving snapshots into tar files, has it been resolved? Do I use the latest version 2.0.0-rc1, but it still prompts that some levels of sha256 cannot be found. Is it lost due to garbage collection?

@lingdie这显然有什么问题。
这个问题在各种操作中不断出现 - save，，commit有或没有 kube - #3179
我相信这些都是同一个根本问题，但我无法准确指出它……

Regarding the issue of saving snapshots into tar files, has it been resolved? Do I use the latest version 2.0.0-rc1, but it still prompts that some levels of sha256 cannot be found. Is it lost due to garbage collection?

@ouyangningdong if your issue is the same that is being discussed here, it is not resolved - and the ticket is still open.
If your issue is different, I suggest you open a new ticket.
Also, it does not seem like a garbage collection problem.

@lingdie I did add the scenario as a test (https://github.com/containerd/nerdctl/blob/main/cmd/nerdctl/container_commit_linux_test.go#L28) - right now, the test expectation is to fail (until we fix the problem).
Interestingly, the test failed once on an unrelated PR:
https://github.com/containerd/nerdctl/actions/runs/10497512059/job/29080522608
... meaning the problem might be racy?

The only thing I can think of is that containerd might have garbage collected some essential layers...

I believe I have found the source of the problem. Below is my reproduction process:

Start the pod

kubectl run busybox --image busybox -- sleep 12000

Check the original image, find it's in an incomplete state

ctr --namespace=k8s.io i check | grep busybox
docker.io/library/busybox:latest                                                                  application/vnd.oci.image.index.v1+json                   sha256:34b191d63fbc93e25e275bfccf1b5365664e5ac28f06d974e8d50090fbb49f41 incomplete (1/2) 390.0 B/1.8 MiB     true
docker.io/library/busybox@sha256:34b191d63fbc93e25e275bfccf1b5365664e5ac28f06d974e8d50090fbb49f41 application/vnd.oci.image.index.v1+json                   sha256:34b191d63fbc93e25e275bfccf1b5365664e5ac28f06d974e8d50090fbb49f41 incomplete (1/2) 390.0 B/1.8 MiB     true

Commit the container

containerID=$(kubectl get pods -o go-template='{{range .items}}{{range .status.containerStatuses}}{{if eq .name "busybox"}}{{.containerID}}{{"\n"}}{{end}}{{end}}{{end}}' | grep -oP '(?<=containerd://)\w+')

nerdctl commit $containerID docker.io/lingdie/busybox:dev

Check the committed image, it's also in an incomplete state

ctr --namespace=k8s.io i check | grep busybox
docker.io/library/busybox:latest                                                                  application/vnd.oci.image.index.v1+json                   sha256:34b191d63fbc93e25e275bfccf1b5365664e5ac28f06d974e8d50090fbb49f41 incomplete (1/2) 390.0 B/1.8 MiB     true
docker.io/library/busybox@sha256:34b191d63fbc93e25e275bfccf1b5365664e5ac28f06d974e8d50090fbb49f41 application/vnd.oci.image.index.v1+json                   sha256:34b191d63fbc93e25e275bfccf1b5365664e5ac28f06d974e8d50090fbb49f41 incomplete (1/2) 390.0 B/1.8 MiB     true
docker.io/lingdie/busybox:dev                                                                     application/vnd.docker.distribution.manifest.v2+json      sha256:66b5ca932bd733887d3c4c4d808b6816f9bafed9ea5fb1d350d0a1e84f86781e incomplete (2/3) 791.0 B/1.8 MiB     true

Try to push the image using nerdctl, which of course fails

nerdctl push docker.io/lingdie/busybox:dev
FATA[0000] failed to create a tmp single-platform image "docker.io/lingdie/busybox:dev-tmp-reduced-platform": content digest sha256:75e8ca8f509fb8f7ee74430edbdc5b78fd863a4f08e06c53828e9a996a79f642: not found

Use ctr to pull the image again

ctr --namespace k8s.io image pull docker.io/library/busybox:latest
docker.io/library/busybox:latest:                                                 resolved       |++++++++++++++++++++++++++++++++++++++|
index-sha256:34b191d63fbc93e25e275bfccf1b5365664e5ac28f06d974e8d50090fbb49f41:    exists         |++++++++++++++++++++++++++++++++++++++|
manifest-sha256:e7e097403ca9266ab43ca83b3b55c272c248cf46489a40bcc4864bd7dd945f18: exists         |++++++++++++++++++++++++++++++++++++++|
layer-sha256:75e8ca8f509fb8f7ee74430edbdc5b78fd863a4f08e06c53828e9a996a79f642:    done           |++++++++++++++++++++++++++++++++++++++|
config-sha256:fd633c23ab56c682e69aacf7fea8d0eaa8d18bd72c4b1c6d82eb5eaace658f1a:   exists         |++++++++++++++++++++++++++++++++++++++|
elapsed: 8.0 s                                                                    total:  1.0 Mi (128.0 KiB/s)
unpacking linux/arm64/v8 sha256:34b191d63fbc93e25e275bfccf1b5365664e5ac28f06d974e8d50090fbb49f41...
done: 9.078793ms

Check the image

ctr --namespace=k8s.io i check | grep busybox
docker.io/library/busybox:latest                                                                  application/vnd.oci.image.index.v1+json                   sha256:34b191d63fbc93e25e275bfccf1b5365664e5ac28f06d974e8d50090fbb49f41 complete (2/2)   1.8 MiB/1.8 MiB     true
docker.io/library/busybox@sha256:34b191d63fbc93e25e275bfccf1b5365664e5ac28f06d974e8d50090fbb49f41 application/vnd.oci.image.index.v1+json                   sha256:34b191d63fbc93e25e275bfccf1b5365664e5ac28f06d974e8d50090fbb49f41 complete (2/2)   1.8 MiB/1.8 MiB     true
docker.io/lingdie/busybox:dev                                                                     application/vnd.docker.distribution.manifest.v2+json      sha256:66b5ca932bd733887d3c4c4d808b6816f9bafed9ea5fb1d350d0a1e84f86781e complete (3/3)   1.8 MiB/1.8 MiB     true

Push the image using nerdctl, success...

nerdctl push docker.io/lingdie/busybox:dev
INFO[0000] pushing as a reduced-platform image (application/vnd.docker.distribution.manifest.v2+json, sha256:66b5ca932bd733887d3c4c4d808b6816f9bafed9ea5fb1d350d0a1e84f86781e)
manifest-sha256:66b5ca932bd733887d3c4c4d808b6816f9bafed9ea5fb1d350d0a1e84f86781e: done           |++++++++++++++++++++++++++++++++++++++|
layer-sha256:eb86545fdbaa77abb944627619e66fb8c1853b427fc930493c561988674054be:    done           |++++++++++++++++++++++++++++++++++++++|
config-sha256:f78592bf867943251d217918b2299bbd7191970ae83dc52a8afc5e7ad98bf71d:   done

see: https://github.com/containerd/containerd/issues/8973


Data Annotations seems doesn't work in derived class

Hi~
When I am using EF core to create MySQL table (using  MySQL.Data.EntityFrameworkCore Package), I found some problems that Data Annotations [Column( TypeName = "varchar(200)" ] seems doesn't work.
Steps to reproduce
Here is my code:
public class BasicObject
{
        [DatabaseGenerated(DatabaseGeneratedOption.Identity)]
        public int Id { set; get; }

        public string Name { set; get; }

        [Column(TypeName = "varchar(200)")]
        public string Description { set; get; }
}

public class Item : BasicObject
{
        public int Type { set; get; }

        public double Price { set; get; }

        public string Image { set; get; }
}

public class DBManager : DbContext
{
    public DBManager(DbContextOptions<DBManager> options)
    : base(options)
    { }

    public DbSet<Item> Items { get; set; }

    protected override void OnModelCreating(ModelBuilder modelBuilder)
    {
        modelBuilder.Entity<Item>().ToTable("Items");
    }
}

When the database created, the type of column 'Description' is still varchar(255).
However, when I use 'Fluent API' as follow:
modelBuilder.Entity<Item>().ToTable("Items")
                        .Property(b=>b.Description).HasColumnType("varchar(200)");

It can change the column type to varchar(200).
So, Is this a bug ?
Further technical details
Visual studio version: 2015-community update3

What version of EF Core are you using?

MySQL.Data.EntityFrameworkCore (7.0.6-IR31)

@BigVan This should have been fixed in 1.0.1. Update Microsoft.EntityFrameworkCore.Relational to 1.0.1 and try again.

I'm getting this too - my annotations don't seem to work for SQLite, but they're fine through the fluent api.
here are my dependencies:
"dependencies": {
    "Microsoft.EntityFrameworkCore": "1.1.0",
    "Microsoft.EntityFrameworkCore.Relational": "1.1.0",
    "Microsoft.EntityFrameworkCore.Relational.Design": "1.1.0",
    "Microsoft.EntityFrameworkCore.Sqlite": "1.1.0",
    "Microsoft.EntityFrameworkCore.Sqlite.Design": "1.1.0",
    "Microsoft.EntityFrameworkCore.Tools": "1.1.0-preview4-final",
    "Microsoft.NETCore.UniversalWindowsPlatform": "5.2.2"
  },

Or am I using the wrong annotation library? I couldn't find any mention of the one to use in the documentation, but I saw System.ComponentModel.DataAnnotations being used in some of the tests.
Here is an example class:
using System;
using System.ComponentModel.DataAnnotations;
using System.ComponentModel.DataAnnotations.Schema;
using System.Collections.Generic;

namespace Foo.models
{
    public class Foo
    {
        public int Id { get; set; }

        [Required, MaxLength(512)]
        public string Name { get; set; }
    }
}

This is a known issue: data annotations don't work on UWP, see https://github.com/aspnet/EntityFramework/issues/5471


Fix User AutoCMD error

Only call the autocmd if it is defined. This avaoids errors "No matching
autocmd" when running the plugin.

Ah, good catch, thanks. I completely forgot to test without an autocommand set :).

Well, I only tested the negative case,
Today I tried to define an autocmd and it didn't work, the correct way is using exists('#User#LinediffBufferReady'). Just an extra 5 characters, it's not worth it to open another PR for this.
Sorry about that, I was really sleepy last night.

Whoops, should have tested it myself :). Committed and pushed.


env:import silently failing (leaving user in the dark) any time .env includes reserved environment variables > Output a warning.

Running env:import silently fails when .env includes reserved environment variables, in my case SITE_NAME.
I made a .env and ran $ netlify env:import .env
Despite multiple attempts I could not get the command to work, leading me down a garden path of attempted other fixes.
An explicit error message would turn a 2 hour random walk into a quick fix 🥺.
The command should return an explicit fail and provide the same warning that is shown in the visual interface.
Add an error message that is similar to what's in the web validation message, something like:

env:import failed. Reason: SITE_NAME is a reserved environment variable. Remove reserved variables from file and retry.

Issue initially reported in the forums here: https://answers.netlify.com/t/netlify-env-import-env-not-uploading-environment-variables-into-the-linked-netlify-project/87695
Steps to reproduce
How to reproduce:

Add a reserved environment variable to .env for example SITE_NAME=Example and VALID_VAR=Something
Run $ netlify import:env:import .env
Command will silently complete with no indication of success or failure, but it will have failed
Check $ netlify env:import and your variables will not have be added
Running the command with $ netlify import:env:import .env --debug provides not further insight, but the error should display whether debug is on or not.

Configuration
My config:
### .env
SITE_NAME=Common Guide
REPO_NAME=commonguide
REPO_URL=[GitHub - CommonGuide/commonguide](https://github.com/CommonGuide/commonguide)
EDIT_URI=edit/main/docs/
THEME_NAME=material

### Log from running ‘netlify env:import .env --debug’:
branch: main
buildDir: /Users/me/projects/commonguide
configPath: /Users/me/projects/commonguide/netlify.toml
context: dev
env:

    DEPLOY_ID
    BUILD_ID
    REPOSITORY_URL
    NETLIFY_LOCAL
    HEAD
    COMMIT_REF
    CACHED_COMMIT_REF
    PULL_REQUEST
    LANG
    LANGUAGE
    LC_ALL
    GATSBY_TELEMETRY_DISABLED
    NEXT_TELEMETRY_DISABLED

❯ Resolved config
build:
command: mkdocs build
commandOrigin: config
publish: /Users/me/projects/commonguide/site
publishOrigin: config

Environment
System:
OS: macOS 11.7.4
CPU: (8) x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Memory: 273.87 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 18.15.0 - ~/.asdf/installs/nodejs/18.15.0/bin/node
npm: 9.5.0 - ~/.asdf/plugins/nodejs/shims/npm
npmGlobalPackages:
netlify-cli: 13.1.3

@danez I wanted to know if the Netlify API was changed recently before pushing a fix.
The code is throwing an undefined value which is why things are failing silently.
The actual error was of this structure:
{
  name: "JSONHTTPError",
  status: 422,
  json: {
    code: 422,
    message: "{\"code\":422,\"msg\":\"SITE_NAME is a reserved key name\",\"error_id\":\"{:request_id=\\u003e\\\"cde27457-eb68-4524-9b03-b1dfc7cedda8\\\"}\"}",
  },
}

But, in the code we're accessing .json.msg instead of .json.message.msg.
https://github.com/netlify/cli/blob/be1f66d277ed88133df92dc579fd72d97edd31e3/src/commands/env/env-import.mjs#L108-L112
Note:

Use of .json.msg was added in this PR: https://github.com/netlify/cli/pull/4751
There are other sub-commands under the env command accessing the same value so they might be failing silently too. I'll check this & try to add tests.

//cc @jasonbarry

Hi @evolve2k -- thanks for reporting, and sorry for the inconvenience this has caused you! I can relate to the frustrations of swallowed errors -- there should definitely be some feedback in the output here.
We recently migrated all sites to use a new environment variable service, and it turns out that errors from that service are getting wrapped in the error message of the API we proxy through. In short, there wasn't a change to our Netlify API as a whole, but rather a change in site data that is causing nested error messages for endpoints proxied to this new service.
@tinfoil-knight, I've filed an issue for our backend team to take a look at. I think we should handle it there, rather than in the CLI, for uniformity and so that the fix will work with old versions of the CLI too. Let's leave this issue open though until the issue is resolved.

Hi @evolve2k! The fix for this will roll out shortly. This was an API fix so should be fixed with the CLI version you currently have installed.


Travis-CI integration

I'm currently working on getting Travis-CI builds running using their Docker system, but until certain packages get approved (libv8-dev), the builds will fail.

Quick status update: on the machines available from Travis (running Ubuntu 12.04 LTS), libv8-dev is too outdated for the code written for greenbot, thus any configuration will have to obtain the libs manually.
@emgram769 what's the minimum libv8 version needed to run greenbot, again?

I forget, wheres that dump of the logs? If you google the error stack overflow has details on versions.


[BUG] unexpected addition of AND NOASSERTION to license when updating pywin32-ctypes

Describe the bug
When updating to<EMAIL_ADDRESS>from 0.2.2 the licensed is identified as BSD-3-Clause AND NOASSERTION instead of BSD-3-Clause.  The NOASSERTION is causing an unwanted failure.
I have looked at the repo (https://github.com/enthought/pywin32-ctypes/compare/v0.2.2..v0.2.3) and I am unclear what is triggering the new AND NOASSERTION.  I also looked at the wheels on PyPI and did not identify any seemingly relevant changes around the license metadata or file.
To Reproduce
https://github.com/Chia-Network/chia-blockchain/pull/18497
https://github.com/Chia-Network/chia-blockchain/actions/runs/10457582039/job/28957737729?pr=18497#step:3:23
##[debug]Filtered Changes: [{"change_type":"added","manifest":"poetry.lock","ecosystem":"pip","name":"pywin32-ctypes","version":"0.2.3","package_url":"pkg:pypi/pywin32-ctypes@0.2.3","license":"BSD-3-Clause AND NOASSERTION","source_repository_url":"https://github.com/enthought/pywin32-ctypes","scope":"runtime","vulnerabilities":[]},{"change_type":"removed","manifest":"poetry.lock","ecosystem":"pip","name":"pywin32-ctypes","version":"0.2.2","package_url":"pkg:pypi/pywin32-ctypes@0.2.2","license":"BSD-3-Clause","source_repository_url":"https://github.com/enthought/pywin32-ctypes","scope":"runtime","vulnerabilities":[]}]
Expected behavior
No change to the license is noted and it is accepted.
Screenshots
If applicable, add screenshots to help explain your problem.
Action version
What version of the action are you using in your workflow?
latest v4

Similar issue here for another dependency:
The validity of the licenses of the dependencies below could not be determined. Ensure that they are valid SPDX licenses:
pom.xml »<EMAIL_ADDRESS>– License: Apache-2.0 AND NOASSERTION
Error: Dependency review could not detect the validity of all licenses.
https://github.com/dolorsfg/proves/actions/runs/10561223320


Login issue on multi-server setup (xhr post error, Session ID unknown)

Hi! I have a problem logging into the admin panel when I have multiple servers in a load-balancing group.
Му instrument configuration looks like:
instrument(io, {
  readonly: true,
  auth: false,
  store: new RedisStore(redisClient)}
})

My socket.io configuration:
{
    "allowEIO3": true,
    "transports": ["polling", "websocket"],
    "cors": {
        "origin": ["https://admin.socket.io"]
    }
}

When I try to connect to application with single server in load-balancing group everything works fine and I can see the connection metadata in Redis.
But when I try to connect to application with multiple servers I get error xhr post error
Request:
POST /socket.io/?EIO=4&transport=polling&t=NayhWmL&sid=jlBhx1IfS1dZEpWOAANq HTTP/2
Host: develop.myserver.app:3001
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:88.0) Gecko/20100101 Firefox/88.0
Accept: */*
Accept-Language: ru-RU,ru;q=0.8,en-US;q=0.5,en;q=0.3
Accept-Encoding: gzip, deflate, br
Content-type: text/plain;charset=UTF-8
Content-Length: 1
Origin: https://admin.socket.io
Connection: keep-alive
Referer: https://admin.socket.io/
TE: Trailers

Response:
HTTP/2 400 Bad Request
date: Wed, 05 May 2021 13:18:29 GMT
content-type: application/json
set-cookie: AWSALB=/3ZFJ1ljYdZVVpueuztmZeLiyAzPiZ+m9iRf0L8SZLZw2Y44fUk6E5IThvk0+5Z+FurdStn9oIWXtqtGWB5ibYLcEU6OlqOWcMC75zpmSks+cT1WNg7YVcEHe; Expires=Wed, 12 May 2021 13:18:29 GMT; Path=/
set-cookie: AWSALBCORS=/3ZFJ1ljYdZVVpueuztmZeLiyAzPiZ+m9iRf0L8SZw2Y44fUk6E5IThvk0+5Z+FurdStn9oIWXtqtGWB5ibYLcEU6OlqOWcMCh5W75zpmSks+cT1WNg7YVcEHe; Expires=Wed, 12 May 2021 13:18:29 GMT; Path=/; SameSite=None; Secure
access-control-allow-origin: https://admin.socket.io
vary: Origin
X-Firefox-Spdy: h2

Response body:
{"code":1,"message":"Session ID unknown"}

Did you enable sticky-session?
Reference: https://socket.io/docs/v4/using-multiple-nodes/

@darrachequesne thanks for responding!
Yes, sticky-session is set in my environment.
That is how my application load balancer setup looks:

Arf, I think I found the problem, the client must be initialized with withCredentials: true, in order to send the AWSALBCORS cookie (since we are in a CORS situation).

I forgot to say I am using socket.io version 3
Now I set credentials: true in cors like that:
const options: Partial<ServerOptions> = {
  allowEIO3: true,
  transports: TRANSPORTS,
  pingInterval: PING_INTERVAL,
  pingTimeout: PING_TIMEOUT,
  cors: {
    origin: ['https://admin.socket.io'],
    credentials: true
  }
};

But nothing changes 😔

There are few cases when I want the server to connect from various origins (for example in a chrome extension), and hence I have to set "*" in the origin of cors options, but then the connection is disallowed due to CORS policy. In such cases, do I have to rebuild the admin UI with withCredentials: false and then self-host it, or is there any way around it? @darrachequesne

@aryaman-titan in that case, I think you should be able to provide a noop function to the cors module:
const io = new Server(httpServer, {
  cors: {
    origin: function (origin, cb) {
      cb(null, true); // WARNING: all origins are allowed
    },
    credentials: true
  }
});

Reference: https://www.npmjs.com/package/cors

Thanks @darrachequesne! That works 👍🏻


bug: ion-note with mode ios does not fully apply the style

Hello everyone, I hope you are doing good! I'm not sure if this is a bug really, but it doesn't seem to be the expected behavior.
Bug Report
Ionic version:

[x] 5.1.0
Current behavior:
When setting the mode property of ion-note to ios, only the color is applied (and not the font size difference) on any other device :

But when rendering the application using an iOS device, you can see that the font size of the ion-note is completely different :

Expected behavior:
When using mode ios, the ion-note styling should be the same on iOS devices and other devices.
Steps to reproduce:
Add an ion-note and apply the ios mode.
Related code:
https://stackblitz.com/edit/ionic-angular-v5-trzue5
<ion-note mode="ios">Test</ion-note>

Have a nice day everyone!

Thanks for the issue. I am going to close this as this is not a bug in Ionic Framework. The font-size for ion-note when slotted inside of ion-item is controlled by the ion-item CSS: https://github.com/ionic-team/ionic/blob/master/core/src/components/item/item.md.scss#L150-L156.
Since the ion-item mode is not changing, the font-size will not change either. You can see the difference by setting mode="ios" on ion-item.
If you want to change the font-size of the note, you should set it on the note directly. Hope this clears things up!

Thank you very much @liamdebeasi ! :)


feat: Update Sponsor Tiers | Add DO & Sawo

Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.

[X] Make sure you are requesting to pull a topic/feature/bugfix branch (right side). Don't request your default branch!
[X] Make sure you are making a pull request against the default branch (left side). Also you should start your branch off default branch.
[X] Check the commit's or even all commits' message styles matches our requested structure.
[X] Check your code additions will fail neither code linting checks nor unit test.
[X] I have added necessary documentation (if appropriate)

Description
Please describe your pull request.
❤Thank you!
Post merge checklist

[ ] Follow steps from the guidelines for contributing to this repository.
[ ] If you are a new contributor, ping in the thread and one of the maintainers will add you to all-contributors list.

@CIPHERTron This addition is reducing our performance :(

@CIPHERTron This addition is reducing our performance :(

DO's size is 6.5kb & Sawo's size is 5.2kb :')


Crash during a write, left us with a database file that was corrupted

First of all sorry for not having more details, but this happened now 2x.

Yesterday I was debugging our app and during write block the app crashed and restarted the phone.
After that I tried to run the app and I notice that the realm database crashed during opening of the file. I was in a hurry and didn't make a copy of the database file, which I now regret but was late...

Other case was user that was doing heavy changes with the app, and the app crashed and restarted the phone.  After that Realm couldn't open the project file anymore and he needed to delete app.

Questions:
a) Is there anything special we should take into account when writing, our write blocks are small updates and only do writes.
b) Any options we can turn on to make sure that writes are maybe slower but can't cause files to be corrupted?
c) Is there a backup workflow we could do, like store copy in the app, etc.. but not sure how I can recover in that case, because in example 1, it was hard crash from Realm during opening of the file. I was running in debug mode.
marc

Hi Marc, it looks like you've hit an issue that we recently fixed in v0.93.2:

Fix a case where data loss would occur if a device was hard-powered-off shortly after a write transaction was committed which had to expand the Realm file.

If you experience this issue with 0.93.2 or later, then it means there are cases that we were unable to fix and having steps to reproduce would be key to fixing further scenarios.
To answer your questions specifically:

a) Is there anything special we should take into account when writing, our write blocks are small updates and only do writes.

No, we generally designed Realm to handle any write/read patterns. If you find yourself doing otherwise, please let us know so we can be aware.

b) Any options we can turn on to make sure that writes are maybe slower but can't cause files to be corrupted?

We may offer an option to have extreme durability guarantees in the future, but that would incur a very significant performance hit, but our team is under the impression that our fix in 0.93.2 will be sufficient to cover all realistic data loss situations.

c) Is there a backup workflow we could do, like store copy in the app, etc.. but not sure how I can recover in that case, because in example 1, it was hard crash from Realm during opening of the file. I was running in debug mode.

Realm asserts if it finds any corruption in the file, preventing you from handling that scenario. We expect the 0.93.2 to eliminate these situations so that these assertions are never hit.

Thanks for the quick feedback! Much appreciated, will be upgrading to this new version in our next update will keep you informed of our testing.

Great! Please reopen this issue if you're still experiencing difficulties with the new version.


Export MeshGradientPainter

Can we export MeshGradientPainter in the package? Sometimes we may render the mesh in the background and it needs the painter to draw the canvas. Thanks!

@RockStone fixed with this pr, hope this helps


Implement ToString for ElasticUserTypeMapping

Make ToString for ElasticUserTypeMapping call TypeMapper::to_string() so it's simpler to use.
The sample can also be updated to use this. So you'd have MyStruct::mapping().to_string().

The example in the docs should also be updated to use mapping().to_string().

This can't really be done because you can't blanket implement traits you don't own.


Worker Dashboard

Midway with worker dashboard. TODO:

actually populate data table with the values we get for in progress and accepted tasks
allow user to check out in progress tasks and complete or skip them (go back to accept task or stay on dashboard?)
log and display payment information
Post microsoft - allow workers to rate requesters for their accepted tasks

lgtm, please include returned tasks as well :)


Refactor ADPilatus tests to use the ad_standard_det_factory

Closing in favor of different PR that does this for pilatus + sim detector + more ad standard det test simplification.


upgrade xstream due to cves

ISSUE TYPE

Bug Report

https://mvnrepository.com/artifact/com.thoughtworks.xstream/xstream

Fixed in #5947


--type argument ignored

Currently, the --type argument has no effect in the CLI.
Looking at cli.ts, I noticed that type is listed as a valid parameter but isn’t being passed as an option to the jsonSchemaToZod() call.
Is it actually unsupported, or was it just missed?

I also submitted this PR #103 to fix a typo for the --output argument shorthand in the README file which was confused with --type.

Woops! Fixed in 2.3.1.


⚠ Spryr has degraded performance

In 9318626, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 4677 ms

Resolved: Spryr performance has improved in a44ab88 after 10 minutes.


Publish new image docker

See https://github.com/linkedin/Burrow/issues/307
The dockerfile is correct now but in public repo the image has not been updated
Could it be possible to do it ?

I think this has been resolved?
See: https://github.com/linkedin/Burrow/packages/104930?version=v1.3.4

Good point, thanks.


Adapter should show a custom icon in Extensions and Updates

e.g. like NUnit Test Adapter.

Available with v0.1.2


Get inventory error only happens some times while starting.

This appears to be an issue with the bot. I have had success with the new development version. Try updating PokemonGo-Bot-Desktop

I had same error. I just ignored it, press Ctrl+C to interrupt and run npm start again and it's working.


Improve tooltips descriptions

Expected behavior and actual behavior.
We need to improve some tooltips and create new ones that are missing. The tooltips are:

Auto Capture: Include "Just for credit cards."
Interest Rates: Explain what is "Interest rates". You can talk to Roger, Lici or Cezar (me) to explain it.
Advanced options: Add some tooltips to explain better the fields.

Steps to reproduce the problem.
Specifications like the version of the project, operating system, or hardware.
v1.7.0

Waiting for messages from Larissa


"Activities successfully updated!" alert showing instead of launching activity

When clicking on the launch activity action icon, sometimes instead of opening the activity, the "Activities successfully updated!" alert is displayed!

Looks like you're dragging the activity instead of clicking on the action. Are you using a touch screen or something?

@NikhilM98 Yeah that was the reason.
It took me a while to find out it, but I've just submitted a PR with a fix.

I really doubt if it's an issue here. I've been using trackpad and mouse and I never faced this issue. This application is supposed to be used by network administrators and teachers. I don't think that they would be confused with such a trivial operation.

It won't hurt. If I faced it, it means someone else might as well.

I'm agree with @NikhilM98. It's not an issue, it's a standard feature on draggable element.

@llaske I know that this is the expected behavior for a draggable element, but I think that only allowing the dragging action to take place by only dragging through the three dotted icon as shown here #88 would be a nicer idea than dragging anywhere on the row. Plus, nobody would have to face this issue as in the GIF.

I must confess that your fix is nice and dragging using three dotted icon is standard in lot of UI.
BTW I'm not fully sure that this update is pertinent.
@tarunsinghal92 could you give us your opinion?

Fixed in https://github.com/llaske/sugarizer-server/pull/88


Refactor FilterPicker

This component is always the same but we define it from scratch for every page.
We should be able to create a generic component for this that is then used in all pages.

Hey team! Please add your planning poker estimate with ZenHub @andraskvr @Stijnkool

Hey team! Please add your planning poker estimate with ZenHub @andraskvr @bartv @Stijnkool


add cocoapods support

can use cocoapods instead of link
add to Podfile
pod 'ReactNativeToast', :path => '../node_modules/@remobile/react-native-toast'

@ElvisChiang is there any reason this did not get into release? I just hit the issue with this repo not having a cocoapods integration.

The author of this repo didn't accept any PR for long time so I just close it. Just fix it by yourself or use another similar library.


Giving crash with Sodium mod

crash-2021-09-30_17.32.04-client.txt
This is the crash report i recieve on startup

Hm this is a really odd crash. Can you verify that not having TRansliterationlib(and the mods that need it Nea/firstperson) does not cause this crash?

ah yes its not related to Transliterationlib, I apologize for the trouble, i found the reason why it was not working, one of the mods packaged sodium inside their own jar files and then when i added it myself it caused a crash. i overlooked that mod since it was not mentioned in modpack. Thank you anyway for taking the time to look at my issue.


RenderDoc file got imported to blender with errors

I booked a ticket (https://developer.blender.org/T93972) in blender support regarding the subject,
I am facing some issues:
Some blender function like knifescut crashes blender.
Black faces.

corruption in view port.

at the end we found that the rdc file was imported with errors.

Hi there, your issue has been closed due to not correctly following the issue template. Please read the documentation about filing issues and open a new issue which does follow the issue template. Do not reply to this issue with more information or with a correctly formatted issue, as that will only lead to confusion.
I try to address all github issues and fix bugs quickly, but badly formatted issues or poorly described bug reports especially are a significant drain on project resources. Taking a few minutes to file a good issue makes a huge difference and will get it addressed faster - everybody wins!
In github when you first create a new issue the form is pre-populated with a template which you should read over and follow. As linked above there is documentation going into more detail about what makes a good issue.


Fix command matching

Reproduce steps:
alias yst='yarn start'
yarn start:ja

Expected behavior:
(nothing output)

Actual behavior:
💡 yst:ja

Slightly different occurrence:
alias g=git
alias gs="git status"
git status

Expected behavior:
💡 gs

Actual behavior:
💡 gstatus

Slightly different occurrence:
alias g=git
alias gs="git status"
git status

Expected behavior:
💡 gs

Actual behavior:
💡 gstatus

unable to replicate as of the current latest branch.


RF lib - Step 1

Ping #340

Note, that some coverage decrease in onyo.py is to be expected, because functions calling each other used to do that within Repo whereas now, that shim remaining in Repo isn't actually used. That should be alright, since this PR does not intend to change Repo's interface yet.


gcc files, .c, ,ld, .o etc left in tmp directory

This is partly to put my mind at rest, but when I start the python container using the podman run command a gcc process is spawned inside the container, that then compiles some file/s.
Detritus is left in the tmp directory, as per the attached file.  Is this expected behaviour?

My mistake, it looks like I have installed gunicorn which is, for some reason, compiling these files.


maximize() not working

windowManager.maximize() is not working.
I use it like this: It appears to be maximized for a short time, but then immediately returns to its default size.
Future<void> main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await windowManager.ensureInitialized();

  windowManager.waitUntilReadyToShow(null, () async {
    await windowManager.maximize();
    await windowManager.show();
    await windowManager.focus();
  });
  runApp(const MyApp());
}

Tested on Windows 10 with Flutter 3.13.7.

Same problem here using Windows 11 Pro, but I don't think is related to the system. Maybe windowmanager is been called again and setting the size somehow.

After some searching, I have found a workaround. You need to update in windows/runner/win32_window.cpp by changing the parameter in the ShowWindow function from SW_SHOWNORMAL to SW_MAXIMIZE (https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-showwindow).
bool Win32Window::Show() {   return ShowWindow(window_handle_, SW_MAXIMIZE); }

I add a delay to call the maximize method:
Future.delayed(Durations.long4, () {
  if (Settings.maximize.val) windowManager.maximize();
});


net: Pipe does not properly implement the Conn interface

The in-memory net.Conn implementations returned by net.Pipe are just thin wrappers over io.Pipe and do not properly implement net.Conn due to lack of SetDeadline support. Should net.Pipe implement deadline support?
\cc @bradfitz

I suppose they could. For testing, I assume?

Is there interest in a CL implementing deadline support (to make net.Pipe more suitable for testing, yes)?

@flyingmutant, yes, seems like @dsnet and I think it could. I haven't heard objections from others.
@rsc, @ianlancetaylor?

I've adjusted enough net.Conn implementations to respect deadlines, that doing the same here would be fairly straightforward. I just didn't want to add complexity to net.Pipe if it isn't really being used.

Does https://github.com/flyingmutant/go/commit/f63b38c8b35c4cfc7f1050d6fb13b18b7d3778e7 (untested) look like a reasonable direction and complexity/performance tradeoff?

@flyingmutant, sorry, we can only look at and review code on Gerrit. See https://golang.org/doc/contribute.html

Also, be sure your implementation passes https://godoc.org/golang.org/x/net/nettest

A brief glance at your implemention seems to show that deadlines are not extendable, refreshable. There also seems to allow for possible raciness when deadlines occur on a read or write call since the buffers are still accessed by the opFn.

@dsnet good point about possible race, thanks.
Am I right that SetDeadline calls should only be made between Read/Write calls? If so, I don't quite understand what do you mean by "not extendable, refreshable".

@flyingmutant, we spent some time polishing the docs on the Conn interface during Go 1.8.  See if this addresses your questions:
https://beta.golang.org/pkg/net/#Conn
If not, we should fix the docs.

@bradfitz thanks! It seems that it should be possible to SetDeadline concurrently with Read/Write calls (and pending bit in the new docs), and my naive implementation certainly does not allow that.

I've got a working implementation which passes nettest (with -race). However, it required modifications to io.Pipe: support for interrupting I/O much like Close does, but only for 1 operation. Is this an acceptable API addition, and is there interest in this style of implementation?

Instead of making net.Pipe more complex, adding a decent abstraction of http://man7.org/linux/man-pages/man2/socketpair.2.html and using that might be more rewarding in terms of realistic test scenarios. That also allows way more settings enabling even more test scenarios.


Note MiniportInitializeEx-DriverEntry relationship

While NdisMRegisterMiniportDriver should do the necessary work to render MiniportInitializeEx calls valid, NDIS will not call MiniportInitializeEx until DriverEntry returns. This allows MiniportInitializeEx to rely on locks allocated using NdisAllocateRWLock which uses (and, as I read its doc for Windows 7 and Vista, requires) the NDIS_HANDLE returned by NdisMRegisterMiniportDriver.

Hi @jkunkee , congrats on your first contribution to the Microsoft driver DDI reference docs! You're absolutely right, as backed up by this sentence on Initializing a Miniport Driver: "Drivers that call NdisMRegisterMiniportDriver must be prepared for NDIS to call their MiniportInitializeEx functions any time after DriverEntry returns."
I condensed your wording into the preceding sentence, but otherwise that's a great addition. I'll merge this PR for you, and it should be live within the next 24 hours. Thanks again!

Great simplification -- I struggled with that structure a bit -- and the crosslink is a great addition. Cheers!


Properties to be enabled for tenant OIDC logout

In 5.8.0 'SignJWTWithSPKey' property will be set to true by default. Please refer https://github.com/wso2/product-is/issues/4722. Enabling this property will use the keystore of service provider's tenant when signing and validating id tokens. If user wants to make this property to false, in order to sign/validate tokens with keystore of user's tenant domain, they have to set the following two properties to true in <IS_HOME>/repository/conf/identity/identity.xml
<AddTenantDomainToIdToken>true</AddTenantDomainToIdToken>
<AddUserstoreDomainToIdToken>true</AddUserstoreDomainToIdToken>

These configuration has not been templated for the new configuration model.


How can I add a schedule state to my post

Please I have being looking for away to add the schedule state to my post.
Any help will be appreciated .

The pytumblr.TumblrRestClient._post_valid_options = new_post_valid_options line is basically monkey-patching the pytumblr code to change its behavior.
Because the pytumblr code that you're using was probably installed with pip, you can't easily edit it and it does not currently allow you to use the param publish_on, so this code changes how pytumblr works when used in this file to add publish_on as a valid parameter to use.


Aggerate data from leaderboard to use for Effectiveness/Proficiency routing

Create a script to scrape data from leaderboard. Ensure this is reusable:
https://huggingface.co/spaces/lmsys/chatbot-arena-leaderboard

@TheVicBro Will be using GPT instead to scrape the data


Archiving the database records does not prevent duplicates from being added but they are unnecessary

@OllieGYoung I can finish this if you want me to fix it

panel_genes_archive should be protected against duplication through logic checking

Needs testing to see if the record would be the same after the panel has been updated.

Fixed and tested


Editor goes black

Editor goes black at times when I refresh. Description of problem:

Begum Akhtar's Babul Mora. I haven't experienced this with other tracks yet.
I go on "loop" mode with the speed slowed.
I go off loop mode, press escape, and I'm not able to turn the synthesizer knob up (separate problem)
I refresh
The editor comes up black. The original recording can be heard, but not the synthesis. But the analysis tab shows data

line 4921 seems to be hitting an error, in EditorComponent.vue

Seems to be working now ... getting rid of the issues that were causing the scribble ( in addVowel and moveVowel seems to have alleviated this as well. So, closing.


Install headers

When atlas-orca is built and installed as a package, make sure the header files are installed when creating the libatlas-orca.so library.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

@wdeconinck @twsearle please review.

I don't have permission to merge this change. What else do I need to do to get this merged? Thanks. 😄

@wdeconinck Thanks for merging. 👍🏼


Create tts.deva.is-cool.dev.json

Requirements

[x] You have completed your website.
[x] The website is reachable.
[x] The CNAME record doesn't contain https:// or /.
[x] There is sufficient information at the owner field.

Description
text to speech api
Link to Website
deva.is-cool.dev

pls merge asap