Core dump in SSLAccept / SSLNetVConnection::sslServerHandShakeEvent

We (@randall) ran into an odd crashes that seems fairly similar (but not identical) to https://issues.apache.org/jira/browse/TS-4363. Since Jira is now read-only, I'm opening this up here as a new Issue (but, odds are that this is the same as the TS-4363 issue).
Backtrace:
#0  0x00002aaaad74437d in __libc_waitpid (pid=<optimized out>, stat_loc=<optimized out>, options=<optimized out>)
    at ../sysdeps/unix/sysv/linux/waitpid.c:41
#1  0x00002aaaaab83297 in crash_logger_invoke (signo=11, info=0x2aaab610a8f0, ctx=0x2aaab610a7c0) at Crash.cc:164
#2  <signal handler called>
#3  0x00002aaaac715005 in ?? () from /opt/bazinga/lib/libcrypto.so.10
#4  0x00002aaaac7155cc in lh_retrieve () from /opt/bazinga/lib/libcrypto.so.10
#5  0x00002aaaac672c6f in ?? () from /opt/bazinga/lib/libcrypto.so.10
#6  0x00002aaaac67369b in ?? () from /opt/bazinga/lib/libcrypto.so.10
#7  0x00002aaaac700247 in DH_new_method () from /opt/bazinga/lib/libcrypto.so.10
#8  0x00002aaaac70170e in DHparams_dup () from /opt/bazinga/lib/libcrypto.so.10
#9  0x00002aaaac3d717a in ssl_cert_dup () from /opt/bazinga/lib/libssl.so.10
#10 0x00002aaaac3d56a4 in SSL_set_SSL_CTX () from /opt/bazinga/lib/libssl.so.10
#11 0x00002aaaaaea3724 in set_context_cert (ssl=ssl@entry=0x2aea13f9f800) at SSLUtils.cc:361
#12 0x00002aaaaaea3ad6 in ssl_cert_callback (ssl=0x2aea13f9f800) at SSLUtils.cc:398
#13 0x00002aaaac3abd40 in ssl3_get_client_hello () from /opt/bazinga/lib/libssl.so.10
#14 0x00002aaaac3b0f3f in ssl3_accept () from /opt/bazinga/lib/libssl.so.10
#15 0x00002aaaac3c0230 in ssl23_accept () from /opt/bazinga/lib/libssl.so.10
#16 0x00002aaaaaeaa383 in SSLAccept (ssl=0x2aea13f9f800) at SSLUtils.cc:2265
#17 0x00002aaaaae97a4f in SSLNetVConnection::sslServerHandShakeEvent (this=this@entry=0x2aea3b4c23e0, err=@0x2aaab610b980: 0)
    at SSLNetVConnection.cc:1068
#18 0x00002aaaaae9a058 in SSLNetVConnection::sslServerHandShakeEvent (this=0x2aea3b4c23e0, err=<optimized out>) at SSLNetVConnection.cc:1014
#19 0x00002aaaaae9a4c9 in SSLNetVConnection::sslStartHandShake (this=0x2aea3b4c23e0, event=<optimized out>, err=@0x2aaab610b980: 0)
    at SSLNetVConnection.cc:979
#20 0x00002aaaaae9cfc3 in SSLNetVConnection::net_read_io (this=0x2aea3b4c23e0, nh=0x2aaab30116f0, lthread=0x2aaab300d9c0) at SSLNetVConnection.cc:451
#21 0x00002aaaaaeaf254 in NetHandler::mainNetEvent (this=0x2aaab30116f0, event=<optimized out>, e=<optimized out>) at UnixNet.cc:526
#22 0x00002aaaaaf0758e in Continuation::handleEvent (data=0x2aaab17893a0, event=5, this=<optimized out>) at I_Continuation.h:153
#23 EThread::process_event (calling_code=5, e=0x2aaab17893a0, this=0x2aaab300d9c0) at UnixEThread.cc:143
#24 EThread::execute (this=0x2aaab300d9c0) at UnixEThread.cc:270
#25 0x00002aaaaaf06136 in spawn_thread_internal (a=0x2aaab0998460) at Thread.cc:84
#26 0x00002aaaad73caa1 in start_thread (arg=0x2aaab610c700) at pthread_create.c:301
#27 0x00002aaaae5f393d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

I'm curious if @oknet recognizes this as well? This is running v7.0.0, with a small number of cherry picks:
* 0412dec (HEAD -> 7.0.x, origin/7.0.x) TS-5102 parent metrics
* cd53220 Fix for: TS-5108-SSL requests might stall because enabled write is ignored
* d908dc0 TS-5069: Fixes CID 1366771 and 1366771
* c95d0ff TS-5076: Test and set the in_enabled_list by atomic function
* 486cc02 TS-4429: Fixes missing curly brackets with new option
* eff5595 TS-4429: Adds a --concise (-C) option for logstats, excludes % metrics

I only saw the TS-4363 once and can not repeat it. How about your issue ? Is it repeatable ?

Closing this for now.


Containerize your microservice using Docker

As a developer I need to containerize microservices using Docker
so that agile methods can be applied to the creation process.

As a developer
I need to containerize my microservice using Docker
So that I can deploy it easily with all of its dependencies
Assumptions

Create a Dockerfile for repeatable builds
Use a Python:3.9-slim image as the base
It must install all of the Python requirements
It should not run as root
It should use the gunicorn wsgi server as an entry point

Acceptance Criteria
Given the Docker image named accounts has been created
When I use docker run accounts
Then I should see the accounts service running in Docker


Update to .NET 7 paths and add error reporting

I by mistake compile from x86 dev tools on Windows and that cause silent error failure. Hopefully my error reporting does not clutter code too much.
/cc @MichalStrehovsky

@MichalStrehovsky can you review again?


Cannot read property 'crypto' of undefined

Hey guys,
I'm getting a

Cannot read property 'crypto' of undefined

error in my Angular/Node.js project written in TypeScript. I looked in object_hash.js:1 and my guess would be it's coming from the line
r.crypto&&crypto.getRandomValues
I'm totally new to Angular and Node and have no idea how to handle this. I've "npm install"-ed both object-hash and @types/object-hash. I've uninstalled and reinstalled. No luck.
When I open a new folder somewhere else and just try hash( [1, 'hello world'], { algorithm: 'sha512' }) and logging it to the console, it seems to work just fine. There's no problem in my project until it hits the line console.log(hash([string1, string2], { algorithm: 'sha512' })); Any help here?
I should also mention that in a previous non-Angular project, it all worked just fine. I had at the top import hash from 'object-hash';, but now I've had to import * as hash from 'object-hash'; due to a

Module can only be default-imported using the 'allowSyntheticDefaultImports' flag

error. Please help! This might be a super-simple fix, but I have no idea how to fix this.

Same here.

I have a feeling that this is Angular 8 problem, I started getting this as well after upgrade.

同样有问题

Not sure. But possibly related. https://github.com/montagejs/collections/issues/162

Has anyone found a solution to this issue?

I have a feeling that this is Angular 8 problem, I started getting this as well after upgrade.

Same - updated from Angular 6 to 8 and now have this issue

Version 2.0.1 fixed this for me:
https://github.com/puleos/object-hash/commit/1e0835cad7d273b521b8a3beee6c7cb8bd778bee
https://github.com/puleos/object-hash/issues/71

Closing this issue, as it seems to have been fixed in 2.0.1.


Remove warning about “empty abstract block.”

This where clause doesn't need to exist at all.

Thanks!


Extension causes high cpu load

Issue Type: Performance
Extension Name: azure-pipelines
Extension Version: 1.147.2
OS Version: Darwin x64 18.2.0
VSCode version: 1.32.3

Likely dupe of #215


Percentage provider doesn't update

Hi, Im migrating from feline to heirline and the percentage provider doesn't update when you move the cursor in a file.
It's displaying "Top" in the first 48 lines of a 233 line file. When I reach the bottom it displays "Bottom" but going up It displays "Bottom" for 48 lines up too.

That is exactly what %P does.
from :h statusline
	p N   Percentage through file in lines as in |CTRL-G|.
	P S   Percentage through file of displayed window.  This is like the
	      percentage described for 'ruler'.  Always 3 in length, unless
	      translated.

You can rebuild your own using vim.api.nvim_buf_line_count(0) & vim.api.nvim_win_get_cursor(0) OR you could evaluate %p using vim.api.nvim_eval_statusline() and then output "top" or "bottom" when the result is 0 or 100

Oh my bad, didn't know that was the functionality.
Thanks for the help and this is an amazing plugin!


Use parity-ethereum rev 02c54d42398f to fix build

Fix v0.2 build by pointing to an old commit in parity-ethereum.

Not sure why there's no CI here – missing .gitlab-ci.yml? Tests run green for me.

Looks like it's there https://github.com/paritytech/substrate/blob/master/.gitlab-ci.yml

Looks like it's there

Not on the v0.2 branch. :/

Ah, I see, can you try to push it?

hmm, it needs scripts/ too I think.


Add supported webhooks of DingTalk.

Can I provide kubewatch's new support of DingTalk to push messages?

I more then like support of WorkWechat ~

Can I provide kubewatch's new support of DingTalk to push messages?

Why not make a pr?


Weird XYPlot curveCardinal

Any idea why the curves are so erratic?

Code example:
https://github.com/thomasnordquist/MQTT-Explorer/blob/master/app/src/components/Sidebar/ValueRenderer/PlotHistory.tsx

I am no longer certain that this is a bug, or just a bad choice of curve function.
Switching to curveMonotoneX yielded the expected results.
https://github.com/d3/d3-shape#curves


NIFI-8623 Changed repositories from conjars.org to public.nexus.pentaho.org

Description of PR
NIFI-8623 Changes the conjars.org repository to public.nexus.pentaho.org in order to download pentaho-aggdesigner-algorithm 5.1.5-jhyde currently required as a transitive dependency in nifi-hive-processors.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[X] Has your PR been rebased against the latest commit within the target branch (typically main)?

[X] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] Have you verified that the full build is successful on JDK 8?
[ ] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Reviewing...

LGTM, will merge when Github Actions are successful


SyntaxError: EOL while scanning string literal during run_train.py

I was able to successfully extract both my 'train' and 'valid' patches for the CoNSeP data, but get this error when using the run_train.py --view=<dset> execution.
The .npy files are in the 540x540_164x160\ file and the path is correctly going to that location. I know this, because it says Error: no .npy file found, if the path is incorrectly set.
PS C:\Users\jpw011> python run_train.py --view='train'
Traceback (most recent call last):
  File "C:\Users\jpw011\run_train.py", line 36, in <module>
    from config import Config
  File "C:\Users\jpw011\config.py", line 52
    "dataset\training_data\consep\consep\train\540x540_164x164\"
                                                                ^
SyntaxError: EOL while scanning string literal

PS C:\Users\jpw011> python run_train.py --view='valid'
Traceback (most recent call last):
  File "C:\Users\jpw011\run_train.py", line 36, in <module>
    from config import Config
  File "C:\Users\jpw011\config.py", line 52
    "dataset\training_data\consep\consep\train\540x540_164x164\"
                                                                ^
SyntaxError: EOL while scanning string literal

How can I complete the path to no longer receive this EOL message?

Looks like there is a problem with the formatting of the string to the data path


[Autocomplete]: add prop disbleResetInputOnSelect

For the useAutocomplete hook, every time an option is selected/unselected, the search input value is reset. I'd like to be able to control that via a prop so it's possible to build a dropdown where the search stays always the same and the user has to manually clear it.

@taleschaves I'm moving the discussion to #21380


Query parameter to set a prefilled cron expression

So maybe something like https://crontab.cronhub.io/?cronExpression=*/5 * * * * would just prefill the input otherwise if empty, leave it at default.

Just like https://crontab.guru/#0_0,11,12,13,14,15,16,17,18,19,20,21,22,23__

Yep I'd love this, will submit a PR.

Hi @cwilby,
How was this feature from client requests? We need to help that.

If I understand correctly, somebody could "just" update this value at startup accordingly to the current window.location.hash:
https://github.com/cronhub/crontab/blob/master/src/ui/containers/Home.tsx#L38
So maybe the patch is just this:
diff --git a/src/ui/containers/Home.tsx b/src/ui/containers/Home.tsx
index 9b31443..23a234a 100644
--- a/src/ui/containers/Home.tsx
+++ b/src/ui/containers/Home.tsx
@@ -35,7 +35,7 @@ const DecoratedHomeForm = reduxForm({
   destroyOnUnmount: false,
   validate,
   initialValues: {
-    cronExpression: "*/5 * * * *"
+    cronExpression: window.location.hash || "*/5 * * * *"
   }
 })(Home);

What do you think about?


[CUE] #Exec: allow capturing exit status if command fails

Currently, core.#Exec will interrupt DAG execution entirely if the command returns a non-zero exit code, aka an error. This makes it very difficult to write a Dagger configuration with custom behavior on command failure. The only way is to execute a wrapper command, for example a shell script, that will implement the exit code capture, and communicate back to the CUE config. This is repetitive and a bad DX.
Ideally, core.#Exec would allow 1) configuring whether or not to abort DAG execution on command failure, and 2) retrieving the exit code and perhaps error messages from the CUE configuration.
A first step in this direction is the current #Exec: exit: int & 0. The & 0 indicates that, at the moment, the if exit can be queried, that means that its value is zero (otherwise DAG execution would be terminated). This makes the field effectively useless - but it plants a flag in the ground for future API expansion. That API expansion is to be discussed, and its details finalized, in this issue.

I'm currently working on embedding (shell) tests as directly into Dagger as possible. I hope(!) this will help advance the state of art of short scripts being "simple" enough to embed directly into Plans, but where -- as we know happens all too often -- they accrete complexity and nuance over time ... but because no first-class-citizen test framework is available, they simultaneously accumulate no extra tests, if any were even present to begin with.
Having the ability to assert against the exit code of a core.#Exec would reduce the implementation complexity of this subsystem /significantly/, as it would allow for meaningful negative assertions/tests to be part of the DAG. This is mentioned by @samalba in https://github.com/dagger/dagger/issues/989#issue-999626190.
As it stands, right now I'll have to do as @aluzzardi mentions in https://github.com/dagger/dagger/issues/74#issuecomment-788529711, and inject a custom entry point into each container that's used as a script execution environment, as well as dealing with stdin/stdout as per the options mentioned in #1620.

Sorry about the open/close flip-flop.

This capability has been merged in main. It will be shipped in Dagger Engine 0.3.0.
The Go SDK will benefit immediately, as it targets 0.3
However the CUE SDK will only benefit after upgrading to engine 0.3: #3060

I'm closing this, since it's specific to the CUE SDK and we are not adding features to the CUE API at this time. Note that the issue is not yet fixed in the GraphQL API either, but it will be eventually. That is tracked in https://github.com/dagger/dagger/issues/3192


Charm config to set the reclaim policy on the default storage class

Overview
Allow the user to set the reclaim policy of the default storage class created by the charm
Details
Expose through charm config  two options for the reclaim policy: "Delete" or "Retain".  Users can fat-finger the casing, and the charm will fix it to be appropriately title-cased
The charm will block on other invalid or missing config.
The default "Delete" is maintained

Thanks to @nishant-dash for spotting the issue


Segmentation fault: 11 (Python3, Conda env, GPU)

What related GitHub issues or StackOverflow threads have you found by searching the web for your problem?
I've tried importing numpy or scipy before importing tensorflow, but it does not help from issue #2034
Environment info
Operating System: Max OSX 10.12.3
Installed version of CUDA and cuDNN:
(bigfish) jenniferstark@Jennifers-MacBook-Pro:~/Documents/Repositories/bigfish$ brew cask info cuda
cuda: 8.0.61
https://developer.nvidia.com/cuda-zone
Not installed
From: https://github.com/caskroom/homebrew-cask/blob/master/Casks/cuda.rb
==> Name
Nvidia CUDA
==> Artifacts
(bigfish) jenniferstark@Jennifers-MacBook-Pro:~/Documents/Repositories/bigfish$

(please attach the output of ls -l /path/to/cuda/lib/libcud*):
(bigfish) jenniferstark@Jennifers-MacBook-Pro:~/Documents/Repositories/bigfish$ ls -l /Users/jenniferstark/cuda/lib*
total 289880
lrwxr-xr-x  1 jenniferstark  staff    13B Mar  4 19:32 libcuda.1.dylib@ -> libcuda.dylib
-rwxr-xr-x@ 1 jenniferstark  staff    78M Nov  7 02:58 libcudnn.5.dylib*
lrwxr-xr-x@ 1 jenniferstark  staff    16B Nov  7 03:19 libcudnn.dylib@ -> libcudnn.5.dylib
-rw-r--r--@ 1 jenniferstark  staff    63M Nov  7 02:58 libcudnn_static.a

If installed from binary pip package, provide:

A link to the pip package you installed:

https://www.tensorflow.org/versions/master/install/install_mac#NVIDIARequirements
Installing for Anaconda, GPU, Python3  inside a conda environment.
using command:

/bigfish$ pip install --ignore-installed --upgrade https://storage.googleapis.com/tensorflow/mac/gpu/tensorflow_gpu-1.0.1-py3-none-any.whl
Collecting tensorflow-gpu==1.0.1 from https://storage.googleapis.com/tensorflow/mac/gpu/tensorflow_gpu-1.0.1-py3-none-any.whl
  Downloading https://storage.googleapis.com/tensorflow/mac/gpu/tensorflow_gpu-1.0.1-py3-none-any.whl (89.0MB)
    100% |████████████████████████████████| 89.0MB 9.7kB/s
Collecting protobuf>=3.1.0 (from tensorflow-gpu==1.0.1)
  Using cached protobuf-3.2.0-py2.py3-none-any.whl
Collecting numpy>=1.11.0 (from tensorflow-gpu==1.0.1)
  Using cached numpy-1.12.1-cp35-cp35m-macosx_10_6_intel.macosx_10_9_intel.macosx_10_9_x86_64.macosx_10_10_intel.macosx_10_10_x86_64.whl
Collecting six>=1.10.0 (from tensorflow-gpu==1.0.1)
  Using cached six-1.10.0-py2.py3-none-any.whl
Collecting wheel>=0.26 (from tensorflow-gpu==1.0.1)
  Using cached wheel-0.29.0-py2.py3-none-any.whl
Collecting setuptools (from protobuf>=3.1.0->tensorflow-gpu==1.0.1)
  Downloading setuptools-34.3.3-py2.py3-none-any.whl (389kB)
    100% |████████████████████████████████| 399kB 1.8MB/s
Collecting appdirs>=1.4.0 (from setuptools->protobuf>=3.1.0->tensorflow-gpu==1.0.1)
  Using cached appdirs-1.4.3-py2.py3-none-any.whl
Collecting packaging>=16.8 (from setuptools->protobuf>=3.1.0->tensorflow-gpu==1.0.1)
  Using cached packaging-16.8-py2.py3-none-any.whl
Collecting pyparsing (from packaging>=16.8->setuptools->protobuf>=3.1.0->tensorflow-gpu==1.0.1)
  Using cached pyparsing-2.2.0-py2.py3-none-any.whl
Installing collected packages: appdirs, six, pyparsing, packaging, setuptools, protobuf, numpy, wheel, tensorflow-gpu
Successfully installed appdirs-1.4.3 numpy-1.12.1 packaging-16.8 protobuf-3.2.0 pyparsing-2.2.0 setuptools-34.3.3 six-1.10.0 tensorflow-gpu-1.0.1 wheel-0.29.0

The output from python -c "import tensorflow; print(tensorflow.__version__)".

(bigfish) jenniferstark@Jennifers-MacBook-Pro:~/Documents/Repositories/bigfish$ python -c "import tensorflow; print(tensorflow.__version__)"
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcublas.8.0.dylib locally
Segmentation fault: 11
(bigfish) jenniferstark@Jennifers-MacBook-Pro:~/Documents/Repositories/bigfish$

If possible, provide a minimal reproducible example (We usually don't have time to read hundreds of lines of your code)
Python 3.5.2 |Continuum Analytics, Inc.| (default, Jul  2 2016, 17:52:12)
[GCC 4.2.1 Compatible Apple LLVM 4.2 (clang-425.0.28)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy
>>> numpy.__version__
'1.12.1'
>>> import tensorflow
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcublas.8.0.dylib locally
Segmentation fault: 11

What other attempted solutions have you tried?

Installing the equivalent version for CPU Python3 version based on these instructions worked fine. e.g.:

Seems like the solution for issue #2034 was for python2 and solved by using an older version of numpy, so not relevant here.

Additional information:
When running from Spyder, I get this Traceback
import keras
Using TensorFlow backend.
Traceback (most recent call last):

  File "<ipython-input-2-c74e2bd4ca71>", line 1, in <module>
    import keras

  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/keras/__init__.py", line 3, in <module>
    from . import activations

  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/keras/activations.py", line 3, in <module>
    from . import backend as K

  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/keras/backend/__init__.py", line 64, in <module>
    from .tensorflow_backend import *

  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/keras/backend/tensorflow_backend.py", line 1, in <module>
    import tensorflow as tf

  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/tensorflow/__init__.py", line 24, in <module>
    from tensorflow.python import *

  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/tensorflow/python/__init__.py", line 72, in <module>
    raise ImportError(msg)

ImportError: Traceback (most recent call last):
  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/tensorflow/python/__init__.py", line 61, in <module>
    from tensorflow.python import pywrap_tensorflow
  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/tensorflow/python/pywrap_tensorflow.py", line 28, in <module>
    _pywrap_tensorflow = swig_import_helper()
  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/tensorflow/python/pywrap_tensorflow.py", line 24, in swig_import_helper
    _mod = imp.load_module('_pywrap_tensorflow', fp, pathname, description)
  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/imp.py", line 242, in load_module
    return load_dynamic(name, filename, file)
  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/imp.py", line 342, in load_dynamic
    return _load(spec)
ImportError: dlopen(/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/tensorflow/python/_pywrap_tensorflow.so, 10): Library not loaded: @rpath/libcudart.8.0.dylib
  Referenced from: /Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/tensorflow/python/_pywrap_tensorflow.so
  Reason: image not found

Failed to load the native TensorFlow runtime.

My .bash_profile should be right, but I've followed so many different tutorials, that I may have mixed up different ways of setting things up. It's totally possible I've messed up here 😢
Path to library in question:
/Developer/NVIDIA/CUDA-8.0/lib/libcudart.8.0.dylib
.bash_profile
#export PATH=/Developer/NVIDIA/CUDA-8.0/bin:$PATH
export PATH=/Developer/NVIDIA/CUDA-8.0/bin${PATH:+:${PATH}}   # from http://docs.nvidia.com/cuda/cuda-installation-guide-mac-os-x/#axzz4aOAsXP00
export DYLD_LIBRARY_PATH="$DYLD_LIBRARY_PATH:$CUDA_HOME/lib:/Developer/NVIDIA/CUDA-8.0/lib"
export DYLD_LIBRARY_PATH=/Developer/NVIDIA/CUDA-8.0/lib${DYLD_LIBRARY_PATH:+:${DYLD_LIBRARY_PATH}}  # from http://docs.nvidia.com/cuda/cuda-installation-guide-mac-os-x/#axzz4aOAsXP00

# NVIDIA cuDNN extracted to ~/
#export CUDA_ROOT=~/cuda
#export LIBRARY_PATH=$CUDA_ROOT/lib:$CUDA_ROOT/lib64:$LIBRARY_PATH

####
# INSTALLING TENSORFLOW-GPU FOR PYTHON 3
# pip install --ignore-installed --upgrade https://storage.googleapis.com/tensorflow/mac/gpu/tensorflow_gpu-1.0.0-py3-none-any.whl
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/Users/jenniferstark/cuda/lib"
export CUDA_HOME=/Users/jenniferstark/local/cuda

Thank you in advance!!!

In my macbookpro, I expanded my DYLD_LIBRARY_PATH as follows to get around this issue.
cant verify further as the macbook I tried this on is now a brick, but I hope this helps:
export DYLD_LIBRARY_PATH=/Developer/NVIDIA/CUDA-8.0:/Developer/NVIDIA/CUDA-8.0/lib:/usr/local/cuda:/usr/local/cuda/lib:$DYLD_LIBRARY_PATH

We seem to be resolving some libraries with the lib in the path and some without.
That seems to be causing the problem.

@gunan thank you so much! My .bash_profile now reads
export DYLD_LIBRARY_PATH=/Developer/NVIDIA/CUDA-8.0:/Developer/NVIDIA/CUDA-8.0/lib:/usr/local/cuda:/usr/local/cuda/lib:$DYLD_LIBRARY_PATH

export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/Users/jenniferstark/cuda/lib"
export CUDA_HOME=/Users/jenniferstark/cuda

keras and tensorflow now each import successfully. Running
import tensorflow as tf

# Creates a graph.
a = tf.constant([1.0, 2.0, 3.0, 4.0, 5.0, 6.0], shape=[2, 3], name='a')
b = tf.constant([1.0, 2.0, 3.0, 4.0, 5.0, 6.0], shape=[3, 2], name='b')
c = tf.matmul(a, b)

# Creates a session with log_device_placement set to True.
sess = tf.Session(config=tf.ConfigProto(log_device_placement=True))

# Runs the op.
print sess.run(c)

also seems to do what it should, as far as I can tell. However, now when I try to run my keras cnn model, I run into an issue with scipy.linalg, which is called in Keras' image preprocessing code:
(bigfish) jenniferstark@Jennifers-MacBook-Pro:~/Documents/Repositories/kaggle/bigfish/src/models$ python train_keras_model.py
Using TensorFlow backend.
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcublas.8.0.dylib locally
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcudnn.5.dylib locally
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcufft.8.0.dylib locally
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcuda.1.dylib locally
I tensorflow/stream_executor/dso_loader.cc:135] successfully opened CUDA library libcurand.8.0.dylib locally
Traceback (most recent call last):
  File "train_keras_model.py", line 5, in <module>
    from keras.preprocessing.image import ImageDataGenerator, array_to_img, img_to_array, load_img
  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/keras/preprocessing/image.py", line 10, in <module>
    from scipy import linalg
  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/scipy/linalg/__init__.py", line 175, in <module>
    from .misc import *
  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/scipy/linalg/misc.py", line 5, in <module>
    from .blas import get_blas_funcs
  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/scipy/linalg/blas.py", line 155, in <module>
    from scipy.linalg import _fblas
ImportError: dlopen(/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/scipy/linalg/_fblas.cpython-35m-darwin.so, 2): Library not loaded: /usr/local/lib/libgcc_s.1.dylib
  Referenced from: /Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/scipy/linalg/_fblas.cpython-35m-darwin.so
  Reason: image not found

While in Spyder, I still get what appears to be the original error:
import keras
Using TensorFlow backend.
Traceback (most recent call last):

  File "<ipython-input-4-c74e2bd4ca71>", line 1, in <module>
    import keras

  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/keras/__init__.py", line 3, in <module>
    from . import activations

  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/keras/activations.py", line 3, in <module>
    from . import backend as K

  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/keras/backend/__init__.py", line 64, in <module>
    from .tensorflow_backend import *

  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/keras/backend/tensorflow_backend.py", line 1, in <module>
    import tensorflow as tf

  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/tensorflow/__init__.py", line 24, in <module>
    from tensorflow.python import *

  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/tensorflow/python/__init__.py", line 72, in <module>
    raise ImportError(msg)

ImportError: Traceback (most recent call last):
  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/tensorflow/python/__init__.py", line 61, in <module>
    from tensorflow.python import pywrap_tensorflow
  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/tensorflow/python/pywrap_tensorflow.py", line 28, in <module>
    _pywrap_tensorflow = swig_import_helper()
  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/tensorflow/python/pywrap_tensorflow.py", line 24, in swig_import_helper
    _mod = imp.load_module('_pywrap_tensorflow', fp, pathname, description)
  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/imp.py", line 242, in load_module
    return load_dynamic(name, filename, file)
  File "/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/imp.py", line 342, in load_dynamic
    return _load(spec)
ImportError: dlopen(/Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/tensorflow/python/_pywrap_tensorflow.so, 10): Library not loaded: @rpath/libcudart.8.0.dylib
  Referenced from: /Users/jenniferstark/anaconda/envs/bigfish/lib/python3.5/site-packages/tensorflow/python/_pywrap_tensorflow.so
  Reason: image not found

Failed to load the native TensorFlow runtime.

So now I am unsure whether this issue is related to TensorFlow, Keras, or Scipy 😟
Again, thank you in advance 🤖

>>> keras.__version__
'2.0.1'
>>> scipy.__version__
'0.19.0'
>>> tensorflow.__version__
'1.0.1'

Ok, I downgraded scipy based on this
 conda install scipy=0.17.0

which seems to have helped (at least in the terminal. Spyder still displays original error).
Now I get memory issues, which I think are unrelated to this original issue, so I'm going to close this issue.
Thanks 👯♂


Added keyboard text selection support

Issue
Previously, only the pointer-based selection was captured and processed by the SelectionHandler and the TextAnnotatorPopup. When the user initiated the selection with the Shift + Arrow or Ctrl + A - it wasn't represented in the annotation selection state. Therefore, we couldn't know when or whether the annotation popup should appear.
Instead, for better a11y support, the selection should be able to start and conclude using exclusively keyboard events. The ability to start the selection anywhere on the page is already provided by the caret browsing mode.
Relations

This PR depends on the:

https://github.com/annotorious/annotorious/pull/420, which generalizes the user's selection event capturing.
https://github.com/recogito/text-annotator-js/pull/140, which fixed leaving zombie annotations upon changing the selection direction.
https://github.com/recogito/text-annotator-js/pull/137, which fixed reading obsolete isCollapsed value when processing pointerup event.

After consulting with a11y UX expert there made a few popup behavior decisions - https://github.com/annotorious/annotorious/issues/419#issuecomment-2225716121
Addresses the https://github.com/recogito/text-annotator-js/issues/111

Changes Made

I generalized the lastPointerDown to just the lastDownEvent event, which preserves both the pointerdown and keydown events. Both can be used to create the annotation selection state from the onSelectionChange callback.
Added listeners for the text selection "completion" events like lifting Shift or Ctrl + A. When the currentTarget is present it means that a user paused their annotating process and we can show the annotator popup. However, a user can still proceed to select if needed.
Replaced PointerSelectAction with UserSelectAction in re-exports and throughout the code

⏫ I discovered a bug that makes the 1-character annotations to create upon changing the selection direction:
https://github.com/user-attachments/assets/8bbba7cf-0b02-457e-a451-ce19a791081b
Working on the fix/workaround for that 👌🏻

We'd have to build a solution that supports both then. I agree on the accessibility aspect. But we used to have it working that way in an earlier system, and there was pretty much a flood of user complaints that the extra click is slowing people down too much. I think there are simply different use cases: some where people read the document and make the occasional annotation once in a while vs. some where people create massive amount of annotations. (E.g. use cases more similar to named entity annotation.)

I agree on the accessibility aspect. But we used to have it working that way in an earlier system, and there was pretty much a flood of user complaints that the extra click is slowing people down too much

Okay, then we might wanna be more flexible here 🤔
For example, when the selection comes from the mouse - we should apply the autofocus to the input area. That would match people's expectations, plus won't break the existing behavior.
But on the keyboard selection, the autofocus will be removed. Instead, we can have an aria-live element that says smth like: "Press Tab to move to &&&& dialog". In that way, the selection won't get abruptly interrupted by the focus shift

Hello @rsimon 👋🏻
I've just pushed changes for the "Keyboard Selection 2.0" that preserve your focusing behavior recommendation. See updated Readme to find the demos and change list 🔍


RandomString is 0

When i put Random String past some time the value is always 0
Variable Name (Single) =<PHONE_NUMBER>000000

Which version of OB are you running?

Last one. Also ive updated today to latest version but still same problem.

With latest one do you mean 1.2.2? Or are you on a modded version? Because I fixed this problem long ago...

it does for me too, im running 1.4.4

@urmommagey 1.4.4 is not supported on here, it's not an official version. Use 1.2.2


feat: exposing request from event in interaction handler in order to Ack event with custom payload

this PR addressing https://github.com/slack-io/slacker/issues/22

There is no much sense in first commit without the second one

I'll fix the workflow error, the line length shouldn't prevent progression.
I'll try and look at this later today. I have questions but need to dig in a bit to make sure they're not self explanatory.

btw if it is needed to add an example i will happily add one

Examples are always welcome!

@arusso Let us know when you have had the chance to review the PR.


Add URL To Repo Description

It would be nice to have the URL as part of the description for the repo similar to how Sarah did it here 🙂

https://gitexplorer.com/
Please, add it.

@marcospb19 I am required to be a collaborator on the project to do so 😇

I know, I'm just saying, please (developers)

It's there, but the URL isn't displayed by the Markdown/HTML. The link on the line:
Website: Click to find the right git commands without digging through the web.

@tet3 here's a repository that links to the website at the repository description (about).


Remove deprecation warning

Auto-creation of non-existing host directories is no longer deprecated (see https://github.com/docker/docker/pull/21666), so this warning is no longer relevant.
This removes the deprecation warning.
Thanks @csandanov for noticing https://github.com/docker/docker/issues/16072#issuecomment-210306750 :smile:

oops, fixing

So, I'm not really sure why we do os.Stat first, given that system.MkdirAll()
(which is basically os.MkdirAll()) already checks if the target directory exists
(and otherwise doesn't do anything).
If Windows does support bind-mounts, it could probably become (perhaps even simpler);
diff --git a/volume/volume.go b/volume/volume.go
index 1abd1cc..2e5e9e9 100644
--- a/volume/volume.go
+++ b/volume/volume.go
@@ -74,15 +74,14 @@ func (m *MountPoint) Setup() (string, error) {
                return m.Volume.Mount()
        }
        if len(m.Source) > 0 {
-               if _, err := os.Stat(m.Source); err != nil {
-                       if !os.IsNotExist(err) {
+               if runtime.GOOS = "windows" {
+                       // Windows does not auto-create source directory
+                       if _, err := os.Stat(m.Source); err != nil {
                                return "", err
                        }
-                       if runtime.GOOS != "windows" { // Windows does not have deprecation issues here
-                               logrus.Warnf("Auto-creating non-existent volume host path %s, this is deprecated and will be removed soon", m.Source)
-                               if err := sytem.MkdirAll(m.Source, 0755); err != nil {
-                                       return "", err
-                               }
+               } else {
+                       if err := os.MkdirAll(m.Source, 0755); err != nil {
+                               return "", err
                        }
                }
                return m.Source, nil

Ps Windows does support bind mounta

@jhowardmsft well, auto-creation is no longer deprecated (sure, it's for backward-compatibility), but for consistency it should probably both in Windows and Linux then? In that case, it would become;
--- a/volume/volume.go
+++ b/volume/volume.go
@@ -74,16 +74,8 @@ func (m *MountPoint) Setup() (string, error) {
                return m.Volume.Mount()
        }
        if len(m.Source) > 0 {
-               if _, err := os.Stat(m.Source); err != nil {
-                       if !os.IsNotExist(err) {
-                               return "", err
-                       }
-                       if runtime.GOOS != "windows" { // Windows does not have deprecation issues here
-                               logrus.Warnf("Auto-creating non-existent volume host path %s, this is deprecated and will be removed soon", m.Source)
-                               if err := system.MkdirAll(m.Source, 0755); err != nil {
-                                       return "", err
-                               }
-                       }
+               if err := system.MkdirAll(m.Source, 0755); err != nil {
+                       return "", err
                }
                return m.Source, nil
        }

In which case yes.

@jhowardmsft let me open a separate PR for the Windows changes; that keeps the option open to cherry-pick this PR into 1.11.1 (if we have one, and if we think it's needed), and keep the discussion on auto-creation for windows separate from this.

opened https://github.com/docker/docker/issues/22094 for the other changes

LGTM

LGTM


DependencyNotFoundError on Kitchen Sink example

react-location-jsurl dependency is missing from the example.
To Reproduce
Steps to reproduce the behavior:

Go to the official react-location website.
See Kitchen Sink example.

Expected behavior
The example should work.
Desktop (please complete the following information):

OS: Fedora 34, Linux
Browser: Brave

Fixed!


Document earliest supported node version as 8.12 in the SDK

Discussed this in SIG meeting - the docs need to be updated to state support from node 8.12 and up.
Originally posted by @Rauno56 in https://github.com/open-telemetry/opentelemetry-js/issues/2834#issuecomment-1076571625

I can take this issue.

Fixed in #2860


位置编码是根据mask生成的。如果不考虑mask，直接用固定的位置编码，效果会下降吗？

用固定的位置编码方便部署。

The mask here is used to distinguish the padding area. However, as long as you apply the fixed positional encoding during training, I think the model can adapt to it and the performance will not drop.


[macOS] Support policy changes; Xcode 14 and 16 will be removed from macOS 14 on November 4

Breaking changes
Current support policy:
- all OS compatible versions side-by-side
- for beta, GM versions - latest beta only
- old patch versions are deprecated in 3 months

New support policy:
- only one major version of Xcode will be supported per macOS version
- all minor versions of the supported major version will be available
- beta and RC versions will be provided "as-is" in the latest available macOS image only no matter of beta/GA status of the image
- when a new patch version is released, the previous patch version will be replaced

What does it means in general terms? Starting from the specified date, all minor versions of Xcode 14 and Xcode 16 will be removed from the macOS-14 image.
What about other images? These changes will not affect macOS-12 and macOS-13 images. The changes will affect macOS-14 and all subsequent images. As a result, macOS-14-based images will contain only Xcode 15.x versions, macOS-15 images will contain only Xcode 16.x versions, and so on.
What happens when a new major Xcode beta is released and there is no next revision of the macOS image? Such a beta will be shipped as part of the latest macOS image that supports this Xcode, until the next base macOS image is released, for example: Xcode 16 was shipped as part of macOS-14 until we released macOS-15.

Target date
November 4, 2024
The motivation for the changes
Recently, mainly due to the introduction of the new visionOS platform, macOS-based images have grown to such sizes that they are becoming more difficult to maintain, and users are experiencing difficulties with available disk space, which is critical for completing builds. Parent issue:

https://github.com/actions/runner-images/issues/10511

Possible impact
Workflows based on macOS-14 will stop running if they depend on Xcode 14 and/or Xcode 16
Platforms affected

[X] Azure DevOps
[X] GitHub Actions

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] Ubuntu 24.04
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[X] macOS 14
[X] macOS 14 Arm64
[X] macOS 15
[X] macOS 15 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Mitigation ways
Users whose workflows depend on Xcode 14 and/or Xcode 16 will be forced to use the macOS-13 image for Xcode-14 and the macOS-15 image for Xcode-16, respectively. Be aware that macos-13 YAML label refer to Intel-based image.

This is a bit messed up since macos-15 is not available in Azure DevOps Pipelines. Will they be available in time for this change?

Won't this basically break any iOS/Swift pipeline that depends on macOS-14 out there? What's the remediation path here?
Moving to macOS-15 forces Xcode 16 to my understanding.

This is a bit messed up since macos-15 is not available in Azure DevOps Pipelines. Will they be available in time for this change?

Can we get a response on this?

Hey @Cheesebaron and @LotskiAndrej!
We are working on adding macOS-15 to ADO, but no ETA or promises are available now. I'll publish info in https://github.com/actions/runner-images/issues/10686 once available.

Is there any way to use Xcode 16 currently using macOS-14 ? I run task for checking Xcode version on ADO and got this, but it says it cannot locate xcode 16
Xcode.app
Xcode_14.3.1.app
Xcode_14.3.app
Xcode_15.0.1.app
Xcode_15.0.app
Xcode_15.1.0.app
Xcode_15.1.app
Xcode_15.2.0.app
Xcode_15.2.app
Xcode_15.3.0.app
Xcode_15.3.app
Xcode_15.4.0.app
Xcode_15.4.app
Xcode_16.0.0.app
Xcode_16.0.app
Xcode_16.1.0.app
Xcode_16.1.app
Xcode_16.1_beta_2.app
Xcode_16.app

Is there any way to use Xcode 16 currently using macOS-14 ?

Yes, we have not removed Xcode 16 from macOS-14. It will be done on October 28.

I run task for checking Xcode version on ADO and got this, but it says it cannot locate xcode 16

Recommended task: https://learn.microsoft.com/en-us/azure/devops/pipelines/ecosystems/xcode?view=azure-devops

Thanks for the response, but since I'm using MAUI, I cannot add xcWorkspacePath, and ADO crashes if I don't enter anything

I tried it few times, changed the order of the tasks in yaml, and managed to get it to work, tnx for the responses.

Hey @Cheesebaron and @LotskiAndrej!
We are working on adding macOS-15 to ADO, but no ETA or promises are available now. I'll publish info in #10686 once available.

We have numerous customers with production MAUI applications that are targeting the Apple App Store, actively being built with Xcode 16, as is currently supported [and 'required' by the current .NET 8 MAUI workloads].  Many of those same customers pay for ADO hosted pipeline time so they can successfully build, test and deploy their applications.  Removing this support before Azure DevOps has an available macos-15 alternative feels short sighted at best.  Doing so with less than 1 month notice will be hard to explain to our customers that rely on this functionality.
I understand the difficulty of managing all the various Xcode versions, but the answer cannot be that we leave customers without viable options.

👋 We are shifting our plans for the week due to a number of circumstances.

Thanks that gives us a bit more time to figure out how to tackle this issue, whether to run on our own hardware or move from Azure DevOps Pipelines.

Hey @Cheesebaron, macos-15 image with Xcode 16 will be available on Azure DevOps before the deprecation anyway.

macOS-15 is available using Azure DevOps 🚀
More info: https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml

macOS-15 is available using Azure DevOps 🚀 More info: https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml

Thank you to the team!

Some of the tooling for migrating from macOS-14 to 15 is inaccessible and first should be fixed:
(https://github.com/actions/runner-images/pull/10856)

We changed to macOS-15 vM, but we are having issues with android build
Starting: Build Android MAUI app
Task         : Bash
Description  : Run a Bash script on macOS, Linux, or Windows
Version      : 3.246.1
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/bash
Generating script.

/Users/runner/hostedtoolcache/dotnet/packs/Microsoft.Android.Sdk.Darwin/34.0.143/targets/Microsoft.Android.Sdk.Tooling.targets(31,5): error XA5205: Cannot find aapt. Please install the Android SDK Build-Tools package with the /Users/runner/Library/Android/sdk/tools/android program.
Workload updates are available. Run dotnet workload list for more information.
##[error]Bash exited with code '1'.
Finishing: Build Android MAUI app
Is this a known issue, on macOS-14 it worked ok, but iOS stopped working on macOS-14
ILLINK : error MT2362: The linker step 'ClassHandleRewriter' failed during processing: One or more errors occurred. (The type 'UIKit.UITextFormattingViewController' (used as a parameter in UIKit.UITextView/_UITextViewDelegate.DidBeginFormatting) is not available in iOS 17.5 (it was introduced in iOS 18.0). Please build with a newer iOS SDK (usually done by using the most recent version of Xcode).
a lot of these errors were popping up

@mjosipovic-tgr Were you able to solve your issue? I am asking because I am facing the same issue currently.

@mjosipovic-tgr Were you able to solve your issue? I am asking because I am facing the same issue currently.

We just do our Android builds on macos-14, which continues to work fine :)

macOS-15 is available using Azure DevOps 🚀 More info: https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml

Hi @erik-bershel , Is there any plan to support macOS-15-arm in ADO?

Hey @zjhch123!
Not at the moment as I know. Updates will be available here: https://github.com/actions/runner-images/issues/8971
List of available images and related updates also are available to track here.

@erik-bershel It would be nice if in the future blog posts like this one included ALL breaking changes upcoming. https://github.blog/changelog/2024-11-05-notice-of-breaking-changes-for-github-actions/
Since this change was not in the blog post, we were blind sided by this change, as we don't check the runner-images repository regularly for CI that has continued to work for a long time.

With this change, I no longer have an image that has both Xcode 16 and visionOS (needs an ARM machine) with Azure Pipelines. That breaks our workflows heavily.

Is this a joke? Why would anyone remove something in the same image version introducing a breaking change in the same version? Doesn't this completely destroys the meaning of having a version system in the first place?
This is breaking all of our iOS build + release pipelines.

Looking at the PR's that have been mentioned in this issue and the thumbs down emoticons from people, a very large number of people don't like this change and is blocked by this change.
I understand that lack of disk space is an issue, but at least it can be solved simply by rm xcode16.0.app. However, removing the pre-installed Xcode 16.0 would require users to spend a long time manually downloading it themselves.
@erik-bershel  So can we think about revert this change? Or at least we can consider this change after ADO provides MacOS-15 Arm64?

@mjosipovic-tgr Were you able to solve your issue? I am asking because I am facing the same issue currently.

@thisisthekap , Yes, I added new task into the yaml file
`  - task: Bash@3
displayName: "Install Android SDK and Build Tools"
inputs:   targetType: "inline"
script: |
export ANDROID_HOME=$HOME/Library/Android/sdk
export PATH=$ANDROID_HOME/cmdline-tools/latest/bin:$ANDROID_HOME/build-tools/34.0.0:$ANDROID_HOME/platform-tools:$PATH
mkdir -p $ANDROID_HOME/cmdline-tools/latest
mkdir -p $ANDROID_HOME/build-tools
sdkmanager --install "cmdline-tools;latest" "platform-tools" "build-tools;34.0.0" "platforms;android-34"
yes | sdkmanager --licenses`
and for the iOS certificate issue, in task for installing certificates I added this
 opensslPkcsArgs: "-legacy"             continueOnError: true
Now both android and iOS works on macOS-15

@mjosipovic-tgr Is there any specific reason why you added continueOnError: true for iOS?

@mjosipovic-tgr Is there any specific reason why you added continueOnError: true for iOS?

@thisisthekap ah yes, sorry, I have tasks for both SSL compatibility, in case one of them fails, it will continue and won't stop the build. Depending what you are using you can use only one of them, if you using old certificate and new version of OpenSSL you can remove the one without legacy flag, vice versa. Hope this helps
 # Two tasks for handling OpenSSL compatibility
          - task: InstallAppleCertificate@2
            inputs:
              certSecureFile: nameOfFile.p.12
              keychain: "temp"
              certPwd: yourPassword
              deleteCert: true
              opensslPkcsArgs: "-legacy"
            continueOnError: true
            displayName: "Install Apple Certificate with Legacy Flag"

          - task: InstallAppleCertificate@2
            inputs:
              certSecureFile: nameOfFile.p.12
              keychain: "temp"
              certPwd: yourPassword
              deleteCert: true
            continueOnError: true
            displayName: "Install Apple Certificate without Legacy Flag"

@mjosipovic-tgr Thank you for that! Thats a perfect workaround for the mess with different image versions used randomly we are currently facing.

Looking at the PR's that have been mentioned in this issue and the thumbs down emoticons from people, a very large number of people don't like this change and is blocked by this change.

This change has completely disrupted our release process, and it was with zero notice. This PR doesn't satisfy any kind of "notice".
And to rub salt in that, we've been getting billed for the minimum time, every. time. we. restart.
Why? because this has been intermittently failing our builds, but today it's been near-every-time.
Since this wasn't any kind of notification, we assumed it was something wrong with our builds, then later chalked up to "that terrible github experience" - turns out we were correct, just the reasons for the terrible experience were outright choices on GH's end.
Fix this; revert it and give us time.

It makes no sense to remove new software from a system (XCode 16) while preserving older software (XCode 15), unless there are known problems with the newer software. If you want to keep just one version, keep XCode 16.
This change forced us to migrate to macos-15, but this doesn't work because of https://github.com/microsoft/azure-pipelines-tasks/issues/20628#issuecomment-2472701880 .

Can you please clarify what the final decision is on this? It appears that this was implemented in this PR https://github.com/actions/runner-images/pull/10834 and then reverted again yesterday in this PR https://github.com/actions/runner-images/pull/10962 ...

Hey there! 👋
Due to a combination of factors (including some unexpected issues with dependencies on Xcode 16), we've decided to mitigate the issue by reverting Xcode 16 to macOS-14 images. We'll be working on the notification model and testing, and will be back with more details on upcoming changes and plans.

Please keep Xcode 16. Thanks to Xamarin.UITest we need to build IPA's with Xcode 16 and run the tests with Xcode 15.4

Hey there! 👋
Due to a combination of factors (including some unexpected issues with dependencies on Xcode 16), we've decided to mitigate the issue by reverting Xcode 16 to macOS-14 images. We'll be working on the notification model and testing, and will be back with more details on upcoming changes and plans.

When we will be able to see the changes, Xcode 16 is still not available with macos-14-xlarge runner?

Hey there! 👋
Due to a combination of factors (including some unexpected issues with dependencies on Xcode 16), we've decided to mitigate the issue by reverting Xcode 16 to macOS-14 images. We'll be working on the notification model and testing, and will be back with more details on upcoming changes and plans.

@erik-bershel  I hope you don't remove it from macOS-15 since I managed to got it to work.

Hey there! 👋
Due to a combination of factors (including some unexpected issues with dependencies on Xcode 16), we've decided to mitigate the issue by reverting Xcode 16 to macOS-14 images. We'll be working on the notification model and testing, and will be back with more details on upcoming changes and plans.

@erik-bershel I hope you don't remove it from macOS-15 since I managed to got it to work.

Which Xcode version it works for you in macOS-15?

@yasali xcode 16

Hey there! 👋
Due to a combination of factors (including some unexpected issues with dependencies on Xcode 16), we've decided to mitigate the issue by reverting Xcode 16 to macOS-14 images. We'll be working on the notification model and testing, and will be back with more details on upcoming changes and plans.

@erik-bershel Will this happen on Azure DevOps as well? We have there the same issues like on GitHub Runners, but still don't have the Xcode 16 on mac os 14 again. Our builds are blocked right now.

This change means it is not impossible to build against iOS 17 and iOS 18. Can the iOS 17 Simulator be added to the macOS-15 image please?

Hey there! 👋
Due to a combination of factors (including some unexpected issues with dependencies on Xcode 16), we've decided to mitigate the issue by reverting Xcode 16 to macOS-14 images. We'll be working on the notification model and testing, and will be back with more details on upcoming changes and plans.

@erik-bershel I hope you don't remove it from macOS-15 since I managed to got it to work.

Which Xcode version it works for you in macOS-15?

@yasali , what fix you have given to make xcode16 work on macOS-15. Can you please help me.

Hey there! 👋
Due to a combination of factors (including some unexpected issues with dependencies on Xcode 16), we've decided to mitigate the issue by reverting Xcode 16 to macOS-14 images. We'll be working on the notification model and testing, and will be back with more details on upcoming changes and plans.

@erik-bershel I hope you don't remove it from macOS-15 since I managed to got it to work.

Which Xcode version it works for you in macOS-15?

@yasali , what fix you have given to make xcode16 work on macOS-15. Can you please help me.
We are using Xcode 16.1 with macOS-15, it works well now.

Hey @yasali and @yeftha!
I will be very grateful if you share the problems you have when migrating from macos-14 to macos-15 or simply when using the macos-15 image. This can be done either as a separate issue or here. Sooner or later the macos-15 image will be the latest and we would like to resolve all possible problems by then.

Hey @yasali and @yeftha!
I will be very grateful if you share the problems you have when migrating from macos-14 to macos-15 or simply when using the macos-15 image. This can be done either as a separate issue or here. Sooner or later the macos-15 image will be the latest and we would like to resolve all possible problems by then.

@erik-bershel , Thank you for the quick response, since morning I faced issues with the pipeline (macos-15,xcode16.1) for installApplecertificate.
Error message:
Error outputting keys and certificates
40AB4351F87F0000:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:crypto/evp/evp_fetch.c:355:Global default library context, Algorithm (RC2-40-CBC : 0), Properties ()
Could not find certificate from
##[warning]Error parsing certificate. This might be caused by an unsupported algorithm. If you're using old certificate with a new OpenSSL version try to set -legacy flag in opensslPkcsArgs input.
##[error]Error: /usr/local/bin/openssl failed with return code: 1
Finishing: InstallAppleCertificate
I have just tried running the pipeline and it worked fine without any issues. Thank you

Hey @yasali and @yeftha!
I will be very grateful if you share the problems you have when migrating from macos-14 to macos-15 or simply when using the macos-15 image. This can be done either as a separate issue or here. Sooner or later the macos-15 image will be the latest and we would like to resolve all possible problems by then.

Hi @erik-bershel ,
I am running the pipeline in Azure DevOps, using xcode16.1 with macOS-15, getting below error at install apple certificate task.
Error message
Error outputting keys and certificates
40AB5345F87F0000:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:crypto/evp/evp_fetch.c:355:Global default library context, Algorithm (RC2-40-CBC : 0), Properties ()
Could not find certificate from
##[warning]Error parsing certificate. This might be caused by an unsupported algorithm. If you're using old certificate with a new OpenSSL version try to set -legacy flag in opensslPkcsArgs input.
##[error]Error: /usr/local/bin/openssl failed with return code: 1
Finishing: InstallAppleCertificate
can you please help me on this

@yeftha For this you can check th solution provided by mjosipovic-tgr in
https://github.com/actions/runner-images/issues/10703#issuecomment-2472826230

Heads up! ⏰
To provide immediate mitigation, we have decided to roll back the current macos-14 images in production to the previous stable version from November 22. This should take about 24 hours, but may take up to 48 hours for some specific cases that can be worked around with a restart.

@yeftha For this you can check th solution provided by mjosipovic-tgr in #10703 (comment)

@MerSpyro This fix is working fine . Thank you

XCode 16 still does not seem available in the macOS-14 image?
When will this be available again?

@woutermeuwis please switch to Xcode 16 before running your workflow. Issue states that the current Xcode version is set to 15.4, but it does not mean that there is no Xcode 16 at all.
Example action: https://github.com/maxim-lobanov/setup-xcode

👋
For those tracking these changes or encountering issues for the first time, here’s some context and clarification.
As you may know, we recently faced significant challenges where many users began running out of disk space during tests and builds on macOS-based runners. 😞  This issue was triggered by the inclusion of visionOS simulators in the latest Xcode builds. The root cause, however, lies in our policy of providing nearly all supported minor versions of Xcode on each macOS image, leading to steadily increasing disk usage as Apple’s ecosystem grows.
Here’s how we’ve approached resolving the issue so far:

Immediate action: We temporarily stopped pre-installing visionOS platform tools in Xcode on macOS-14 images.
Strategic adjustment: We introduced a policy to limit the number of major Xcode versions installed per macOS image, alongside reinstating visionOS tools for supported Xcode versions. This aimed to free up significant disk space. https://github.com/actions/runner-images/pull/10876

However, we’ve discovered that some projects rely on multiple major versions of Xcode simultaneously, making these strict measures overly restrictive. This prompted us to refine our strategy, prioritising functionality alongside disk space optimisation.
Current Strategy 📏
Our updated approach balances reducing installed Xcode versions with maintaining runner usability:

macOS-14 images:

Will include all minor releases of Xcode 15 with the full platform tools suite (as before).
Will now also include two minor releases of Xcode 16 (excluding visionOS tools). These will follow a “last two” principle, with the oldest replaced by the newest as updates are released. Beta versions will not be included. https://github.com/actions/runner-images/pull/10962

macOS-15 images:

Will include all minor releases of Xcode 16 with the full platform tools suite (as before).
Will also include the latest available release of Xcode 15 with the full platform tools suite. https://github.com/actions/runner-images/pull/11023

Disk Space and Future Adjustments:

Currently, macOS-14 images have approximately 60 GB of free space. However, this is not a guaranteed figure and may decrease over time.
When free space approaches 30 GB, we will reassess our policies and toolsets to ensure compliance with our promised minimum of 14 GB of free space.
macOS-15 images are not currently impacted by this issue. However, with future Xcode updates, policies may need to be revisited. 🤷♂

Recommendations 🦮

If your workflows depend on visionOS, we recommend switching to macOS-15 images.
If your tasks require significant disk space, consider preparing the runner by removing unnecessary large components before starting your workflows.

@erik-bershel is the macos-15 for the ado now stable? I did an Android build which uses Android API level 34 on the macos-15 and got the following error below. This runs fine on the macos-14
error XA5207: Could not find android.jar for API level 34. This means the Android SDK platform for API level 34 is not installed; it was expected to be in

Hey @amit-thapa! macOS-15 is expected to be fine. I think your issue related to the fact that the first available platform on macOS-15 is 35. You need to install it manually or to switch to the next. See the difference here:
macOS-14,
macOS-15.


Create DB queries.

Create and prepare the templates for the following queries:

[x] Get Games to add
[x] Remove Game from profile
[x] Match Suggestions
[x] Get Matches
[x] Swipe No
[x] Swipe Yes
[x] Check Match
[x] Get User from ID

others can be added.

Get Matches might be unnecessary so put on hold because it'll entail a limitation.

Query templates all used so deleting unnecessary branch and closing issue.


[wip] try again fix block manager decom flakyness

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

Test build #126576 has started for PR 29245 at commit 989af05.

Merged build finished. Test PASSed.

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

This won't work

Test build #126576 has finished for PR 29245 at commit 989af05.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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


test hash before publishing it

We should have a test on the publish-to-dns makefile target: we should check the hash we'll use is correct, by testing some well known things like an image.
i say this because i hosed the website by publishing the root (below /ipfs.io) instead of the ipfs.io dir and for a while broke the site. (totally my fault, should've verified the hash before using it, but this could be a test) The TTL is very low now, so this wont be a big deal in the future. but still avoidable.

I think this may be fixed with https://github.com/ipfs/dnslink-deploy/issues/6.


Some fields while mapping from JIRA to ADO are showing old revision data

Describe the problem
While mapping the fields, some fields in ADO are showing the old revision (mostly first that I could see) data instead of the latest one
To Reproduce
Steps to reproduce the behavior:

Try mapping the fields like Target Release, Requesting Company (3.0.266 was fine in 3.0.115) having multiple revisions
In ADO the target fields shows old data

Tool version

3.0.115, 3.0.266

Attachments
Please attach the following files:
jira-export-log-231129-110224.txt
wi-import-log-231129-110256.txt
config-agile.json
Screenshots
If applicable, add screenshots to help explain your problem.

Please make sure you have read through the FAQ on mapping and troubleshooting custom fields, I suspect you will find your answer there: https://github.com/solidify/jira-azuredevops-migrator/blob/master/docs/faq.md

Thanks I got them correct now by changing in the custom field mapping.


Add callback for requests locked by lock_navigation

The on_navigation_locked callback proposed here is useful to track requests even after calling splash:lock_navigation().

Looks awesome, thanks @vfcosta! Code is good, docs and tests are in place 👍
Would you mind fixing small issues with docs before a merge>

underlines should match text length;
it'd be great to have these new methods mentioned in https://splash.readthedocs.io/en/stable/scripting-overview.html

@kmike done! Thanks for your feedback

It was quick :) Thanks @vfcosta!


Add documentation about the usage of the --storage-directory flag.

The description of the --storage-directory flag was missing in the guide of the CHIP tool, so I added it.

 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.


Move template from array to file

To write custom template it ll be easy if it is in separate file and include it using templateUrl

Hi,
I will check that and add it to the next release. I hope I'm able to do this this week.
Thanks for the idea and regards,
Guy

I've added the ability to specify a template-url attribute on the directive to be able to pass in an external template. You can read more here: https://github.com/guylabs/ion-autocomplete#template-url. Can you please test it on the master and tell me if it works for you because I want to release 0.2.0 this Sunday.
Thanks and regards,
Guy


⚠ Bofrost.de has degraded performance

In 1ffab6d, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1431 ms

Resolved: Bofrost.de performance has improved in 5292bfa.


MIO Reform

Currently a work in progress
I am posting a PR here to hopefully get some feedback as the work happens.
Goals

Update mio to track the latest changes in Rust std.
Get rid of MioResult and MioError in favor of std::io::Result and std::io::Error.
Get rid of the IoAcceptor trait
Remove re-implementations of the various net types that already exist in std.
Freshen up the APIs to match more recent Rust idioms.
Be friendlier to using blocking sockets with mio.
Remove "windows support" and any related abstractions
Misc cleanup

Rename IoReader to TryRead and IoWriter
Now that std::io::Read and std::io::Write are light wrappers over their respective sys calls, it should be fine to use them with mio, especially if we want to be friendlier to using blocking sockets as well. However, there still should be an API optimized for non-blocking operations. This will be handled by TryRead and TryWrite.
Get rid of MioResult and MioError
std::io::Error is now a wrapper around errnos, it should be possible to just use that vs. having a separate type in mio.
Get rid of IoAcceptor
Rust std got rid of it, and I don't think we need it either.
Remove re-implementations of the various net types that already exist in std.
Now that all of the various std::net types are light wrappers around system calls, it should be possible for mio to use them directly. mio will be able to implement TryRead and TryWrite for them as well, making them friendlier for the non-blocking case.
Mio will keep TcpSocket (and the other raw socket types) around to enable more advanced socket setup / configuration, but the socket will need to be converted to either a TcpListener or a TcpStream before accepting, reading, or writing.
The Socket trait will remain to allow configuring socket options.
Be friendlier to using blocking sockets with mio.
Polling isn't just for non-blocking sockets (though it probably is the majority case). I do want to make sure there are no assumptions that all sockets are non-blocking. TcpSocket::v4() currently returns a non-blocking socket w/ CLOEXEC set. I would propose keeping this, but also adding TcpSocket::v4_opt(SockOpt::nonblocking() | SockOpt::cloexec()) or something like that. TcpSocket::v4_opt(...) would not set any flags by default.
Now, there should probably be more functions on TcpSocket as well, for example: TcpSocket::connect(...) -> TcpStream would create a non-blocking socket by default.
Remove "windows support" and any related abstractions
Originally, I was thinking that mio would support windows as well. However, I am starting to lean against this. I am currently leaning to have mio be for systems that support the readiness model. Windows supports the completion model (via IOCP). I'm thinking there should be a higher level IO library that supports both windows & posix systems.
As such, we can get rid of IoDesc in favor of just Fd. I also would like to rename IoHandle to Listenable.
I am interested in feedback. cc @wycats  @rrichardson @reem @vhbit @rozaliev @fhartwig @vberger @vbuslov

Also, the current state of the PR is an initial deep dive. I may start over and try to do it more incrementally now that I have a better sense of the dependencies.

" I'm thinking there should be a higher level IO library that supports both windows & posix systems."
This is exactly right. Let the lower levels expose their platform distinctions, which will temporarily reduce portability of code. But then people will build multiple(and that's a good thing)  abstractions on top that unify the two.

I would propose keeping this, but also adding TcpSocket::v4_opt(SockOpt::nonblocking() | SockOpt::cloexec()) or something like that. TcpSocket::v4_opt(...) would not set any flags by default.

Another option is to add methods on the TcpSocket to configure the socket.
let socket = TcpSocket::v4().nonblocking().cloexec();

See pseudo/untested implementation.

@ayosec I initially thought of adding a builder style API, however there needs to be a way to atomically create the socket and set the flags. So, either there is an explicit socket builder type that has a "build" call, or there would need to be fns that can create the sockets w/ the flags in one go.

+1 for these changes. I'd vote towards keeping the APIs streamlined/defaulted for non-blocking, since that is the niche mio is filling nicely right now.

A big +1 for the unification with std types and traits.
Other than that, as a mere user not knowing a lot about epoll and others... I can't really say more. It overall looks really nice.

+1 on this!! Personal opinion, builder APIs with an explicit build() method are really great for separating mutation and object construction from object use

LGTM.
I can see a pain point with multicast sockets on ipv6 (std lib has the same issue), but that's definitely should be addressed separately.

Starting to work with Mio, one aspect that slightly bothers me is having to do something like the following...
extern crate mio;

use self::mio::*;
use self::mio::net::udp::*;
use self::mio::buf::{RingBuf, SliceBuf};

... without really knowing what's going on.  I may be biased because even in C++ I usually never use things like using namespace std or what have you, and in Python I never use from foo import *, so this could be chalked up to personal preference, but as @carllerche offered on IRC:

teotwaki | I have to admit, I'm not a massive fan of use foo::;
~carllerche | teotwaki: even if it's foo::prelude::?

Obviously, using foo::prelude::* wouldn't give access to everything inside udp or tcp or whatever new APIs are exposed, but it should provide enough traits/structs with names that have little chance of collision with user-code to allow use of specific items in the rest of the Mio API.

+1 for unification with Rust std types.
Dropping potential Windows support is definitely necessary to keep implementation simple and fast.

After reading the whole changeset, I have some thoughts.
I am particularly averse to the disappearance of the IoDesc type, whose logic I'd much rather stayed in one place rather than being copied to every type which holds an Fd. It was already possible to get an Fd out of an IoDesc, so I don't really see a need to drop the type entirely.
I also dislike Listenable, since it contains the able suffix which is traditionally undesirable for traits and we already have an io action listen that this could be easily confused with. I'd much rather Io or another simple name, which simply indicates that this thing is an io object and can produce an Fd or IoDesc, and as a result can be registered on the event loop.
The elimination of windows support as a goal is unfortunate in the short term (as there is no replacement), but probably an unavoidable step for the project and healthy for long term goals. IOCP/Windows support can go in another library and a higher-level IO lib can select between the two.
I'm a big fan of most other cuts and changes, like renaming to TryRead and TryWrite, dropping MioError, MioResult, and IoAcceptor as well as many of the io types, and all the other stuff.

IOCP/Windows support can go in another library

There is a rust-iocp create. I guess that it still needs a lot of work.

@reem re: naming, I am open to alternatives.

Ideas for the old IoHandle: Io, IoDesc, Desc, AsDesc, AsIoDesc, AsFd, AsRawFd, IoHandle

Also, another big reason for getting rid of it was the unification with std types. Mio will do away with a significant chunk of net types. For the others, it makes sense to me to keep them similar to impls in std.

I am no a huge fan of Io as well since not all types that can be registered with the Mio event loop represent IO. There could be signal abstractions, timers, notifications of changed to shared mem, etc...
Another option I was considering was Evented

I'm actually surprised there is no IoDesc-like abstraction used in the implementation of std::{io, net}.
Evented is pretty good. I have a trait in rust-aio called Evented as well, which is basically a rolling combo of Handler and IoHandle in the old/current mio.

These goals are mostly completed by https://github.com/carllerche/mio/commit/06bf140e6928a4505df1520c0805905909f7b68a (and prior commits). However, there are still changes pending on figuring out #131


Improvement to application diagnostics

Is your feature request related to a problem? Please describe.
I've come up with two improvements that can be made to the application diagnostics components.
Firstly, there's no way to have a custom file name or log folder name for the EventLogger component. There may be a requirement where the log needs to be a specific file name or type in a specific application folder.
Secondly, when an exception is observed by the AppDiagnostics component, there is no way to know if that has happened apart from the event logging. There should be a way to bubble up the exception when it has been observed in case something else would like to know of the exception.
Describe the solution you'd like
For the first part, change the constant strings which declare the file and folder name to properties which can be set manually to alter the variables.
For the second, I recommend adding an event to the AppDiagnostics component which allows others to hook onto it. When an exception is observed as part of the AppDiagnostics, it would then pass the observed exception off through the event handler.

Closing this off as the work is complete. Thanks @jamesmcroft


Copy + Paste on multiple files automatically opens them

VSCode Version 1.20.1
Commit f88bbf9137d24d36d968ea6b2911786bfe103002
Date 2018-02-13T15:34:36.336Z
Shell 1.7.9
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64

OS Version:  Windows 10

Steps to Reproduce:

Shift + Click a number of files.
Cntrl + C to copy the files.
Click on a different folder in the workspace explorer
Cntrl + V to paste the files in the new directoty

Expected: Files are simply copied into the selected directory.
What actually happens:  Files are copied but also a new workspace tab is opened for each file that was copied.
At the very least this should not even be a default behaviour thing if it's a desired feature. When performing explorer operations I expect the explorer functionality to work similar to every generic file explorer released where copying and pasting files doesn't mean I also perform additional operations on those files.

@ISInminkler I can not reproduce this behavior.
Do you see this with latest vscode insiders https://code.visualstudio.com/insiders/

@isidorn - Yes.

@isidorn - I even went in and disabled all plugins in my workspace and tried again. selecting multiple files in the explorer then pressing Ctrl + C to copy then selecting another folder and pressing Ctrl +V will paste the selected files but they will automatically open in the workspace.

@ISInminkler can you please attach a video of this?
I can not reproduce what you are seeing. Do you have any keybindings in your keybinds.json?

Also verified reproducible on my debian test VM, nothing special installed on it. Load up latest code:  1.20.1-1518535978. Ctrl + C to copy multiple files, create a new 'test' folder in another directory. Ctrl + V to paste, all files copied are automatically opened.
@isidorn - I don't have any video recording software.

@ISInminkler when you say opened you mean opened inside vscode (as in a new vscode tab). Not that every file gets a new VSCode window?

@isidorn that is probably some very old code from the time where you could drop files onto the explorer to import them. I would maybe check which cases we have and then decide what to do. Opening the file after an operation like this one seems OK to me because it is probably the intent to work on the files after copying them, no?

@bpasero probably the intent -> not so sure, I would say 50%. What if you are just moving some code around. I checked the golden standard Visual Studio and they are not opening.
However nobody else complained for the previous 3 years so I am also not convinced this needs changing.
This paste file action is only used when pasting files and nowehere else, so there are no other cases except pasting via keyboard or mouse.

@isidorn I also feel this is hard to judge and we didn't hear complaints so far. What is a bit ugly is that we open multiple files not just the last one, and since we now support multi-select it is more likely to happen that multiple unwanted files open. But then again, I bet we will get the opposite bug if we change this.

@bpasero I could change the paste file to only open the focused file while copying.
But let's leave this open for now and wait for user feedback. If nobody else complains I suggest no action.

@bpasero It wasn't something I really noticed until the multi-select. I will say though, opening the files being copied around automatically is a huge annoyance (even if it's only a single file). It's just less of an annoyance when it's only a single file as you can easily just close the single opened doc. I'm not sure why vscode breaks from other established conventions for file operations however.

This will sound like a "me too," but I wanted to agree that I didn't notice this behavior until multi-select became available. I copied a bunch of minified JavaScript files from a build folder into a mock-up deployment folder, and it opened all of them in all their minified glory--not only jarring, but also not useful.
I get that this behavior is useful when bringing in multiple files from outside the workspace, but--in the use-case described in this issue--the action is originating from within VSCode. Still, some users might like this.
I think the best option here is to add a setting to disable the feature, preferably when copying locally within the workspace, or--worst case--globally for all file-paste actions.

I would also prefer a setting or disable it completely. I'm copying some files frequently and everytime I have to close them. So +1 for it.

Yep, this is annoying purely in the case @TheJim01 mentioned. Frequently copy paste a bunch of large minified files and it opens them all... would love to be able to turn this off.

This is still happening in 2019, very annoying :(

Этот баг работает даже у Русских в 2020. =)

Has a setting been added to disable this ongoing issue? Would really like to stop the tabs from opening on paste. Thanks!

This works as expected. We no longer open files on paste


Make Joiner choices more explicit.

Expected Behavior
Choices used to be displayed in a dropdown.

Actual Behavior
Choices are now typed into a textbox. The options are not displayed, which makes it hard to figure out what to type.

Steps to Reproduce the Problem

Run a board with a Joiner, such as the Novel Outliner

Caveat
Two solutions come to mind:

Mention that the input format is "Choice 1", "Choice 2", etc.
Bring back the dropdown. (The best IMHO, but I suppose it was removed for a reason.)

@paullewis ohhhh, I think the new controls don't yet support the enums. Is that right?

Yes, oversight on my part. Fix inbound.


Objectrocket-ifying and adding helm chart + circleci pieces

Moving all references from sensu/sensu-operator -> objectrocket/sensu-operator
Updating circleci file to add relevant OR pieces
adding markdownlint for readme
updating k8s in gopkg to non-beta
Adding addition makefile calls
Ensuring we can build on mac, with a build-linux as well
adding helm chart

Overall LGTM. Two concerns that I'm not sure need to be addressed in this PR are

the version of the k8s deps we're pulling in. I haven't checked for .12 and .13 but at least .11 was backwards compatible
a .dockerignore might be helpful


Not updating Database in MySql: Specified key was too long; max key length is 767 bytes

The application doesn't run the migration on startup. It throws an error about length of key.
To Reproduce

Create Application in Visual Studio using the dotnet new command
Change the Connection strings and ProviderType to point to MySQL
Change all references to UseInmem to UseMySql
Run Application

2021-03-24 15:13:16.104 +01:00 [ERR] Failed executing DbCommand (18ms) [Parameters=[], CommandType='"Text"', CommandTimeout='30']
CREATE TABLE `DeviceCodes` (
    `UserCode` varchar(200) CHARACTER SET utf8mb4 NOT NULL,
    `DeviceCode` varchar(200) CHARACTER SET utf8mb4 NOT NULL,
    `SubjectId` varchar(200) CHARACTER SET utf8mb4 NULL,
    `SessionId` varchar(100) CHARACTER SET utf8mb4 NULL,
    `ClientId` varchar(200) CHARACTER SET utf8mb4 NOT NULL,
    `Description` varchar(200) CHARACTER SET utf8mb4 NULL,
    `CreationTime` datetime(6) NOT NULL,
    `Expiration` datetime(6) NOT NULL,
    `Data` longtext CHARACTER SET utf8mb4 NOT NULL,
    CONSTRAINT `PK_DeviceCodes` PRIMARY KEY (`UserCode`)
);
2021-03-24 15:13:17.071 +01:00 [FTL] Host terminated unexpectedly
MySql.Data.MySqlClient.MySqlException (0x80004005): Specified key was too long; max key length is 767 bytes
 ---> MySql.Data.MySqlClient.MySqlException (0x80004005): Specified key was too long; max key length is 767 bytes
   at MySqlConnector.Core.ServerSession.ReceiveReplyAsyncAwaited(ValueTask`1 task) in /_/src/MySqlConnector/Core/ServerSession.cs:line 806
   at MySqlConnector.Core.ResultSet.ReadResultSetHeaderAsync(IOBehavior ioBehavior) in /_/src/MySqlConnector/Core/ResultSet.cs:line 51
   at MySql.Data.MySqlClient.MySqlDataReader.ActivateResultSet() in /_/src/MySqlConnector/MySql.Data.MySqlClient/MySqlDataReader.cs:line 130
   at MySql.Data.MySqlClient.MySqlDataReader.CreateAsync(CommandListPosition commandListPosition, ICommandPayloadCreator payloadCreator, IDictionary`2 cachedProcedures, IMySqlCommand command, CommandBehavior behavior, IOBehavior ioBehavior, CancellationToken cancellationToken) in /_/src/MySqlConnector/MySql.Data.MySqlClient/MySqlDataReader.cs:line 391
   at MySqlConnector.Core.CommandExecutor.ExecuteReaderAsync(IReadOnlyList`1 commands, ICommandPayloadCreator payloadCreator, CommandBehavior behavior, IOBehavior ioBehavior, CancellationToken cancellationToken) in /_/src/MySqlConnector/Core/CommandExecutor.cs:line 62
   at MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQueryAsync(IOBehavior ioBehavior, CancellationToken cancellationToken) in /_/src/MySqlConnector/MySql.Data.MySqlClient/MySqlCommand.cs:line 218
   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteNonQueryAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteNonQueryAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteNonQueryAsync(RelationalCommandParameterObject parameterObject, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Migrations.Internal.MigrationCommandExecutor.ExecuteNonQueryAsync(IEnumerable`1 migrationCommands, IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Migrations.Internal.MigrationCommandExecutor.ExecuteNonQueryAsync(IEnumerable`1 migrationCommands, IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Migrations.Internal.MigrationCommandExecutor.ExecuteNonQueryAsync(IEnumerable`1 migrationCommands, IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Migrations.Internal.MigrationCommandExecutor.ExecuteNonQueryAsync(IEnumerable`1 migrationCommands, IRelationalConnection connection, CancellationToken cancellationToken)
   at Microsoft.EntityFrameworkCore.Migrations.Internal.Migrator.MigrateAsync(String targetMigration, CancellationToken cancellationToken)
   at IIIJ.sso.Admin.EntityFramework.Shared.Helpers.DbMigrationHelpers.EnsureDatabasesMigratedAsync[TIdentityDbContext,TConfigurationDbContext,TPersistedGrantDbContext,TLogDbContext,TAuditLogDbContext,TDataProtectionDbContext](IServiceProvider services) in C:\VHosts\IIIJ\IIIJ.sso\src\IIIJ.sso.Admin.EntityFramework.Shared\Helpers\DbMigrationHelpers.cs:line 72
   at IIIJ.sso.Admin.EntityFramework.Shared.Helpers.DbMigrationHelpers.ApplyDbMigrationsWithDataSeedAsync[TIdentityServerDbContext,TIdentityDbContext,TPersistedGrantDbContext,TLogDbContext,TAuditLogDbContext,TDataProtectionDbContext,TUser,TRole](IHost host, Boolean applyDbMigrationWithDataSeedFromProgramArguments, SeedConfiguration seedConfiguration, DatabaseMigrationsConfiguration databaseMigrationsConfiguration) in C:\VHosts\IIIJ\IIIJ.sso\src\IIIJ.sso.Admin.EntityFramework.Shared\Helpers\DbMigrationHelpers.cs:line 49
   at IIIJ.sso.Admin.Program.ApplyDbMigrationsWithDataSeedAsync(String[] args, IConfiguration configuration, IHost host) in C:\VHosts\IIIJ\IIIJ.sso\src\IIIJ.sso.Admin\Program.cs:line 58
   at IIIJ.sso.Admin.Program.Main(String[] args) in C:\VHosts\IIIJ\IIIJ.sso\src\IIIJ.sso.Admin\Program.cs:line 35

Check this issue #256

Thanks, I have been able to resolve it.


[+] --profile="release" should use -Wl,--build-id=none linker flag to avoid embedding BuildID[sha*]

Hi, this is a minor nitpick, but --profile="release" should also strip BuildID from final executables.
Building a lot of binaries and doing file $BINARY spams the logs.
No worries if this doesn't get added, this is just personal preference, and it might actually be helpful for people to have the BuilID in their binaries for easy identification.

build-id might be useful for some people. I will consider this and test it.
I also will add more options like --ccfalgs --ldflags to allow user pass their comipler and linker flags.

I just learnt that I can use objcopy to do it an automated way, so you may close this Issue:
objcopy --remove-section=".note.gnu.build-id" "${BINARY}"

Adding --ccflags --ldflags will be great


clip skip

Are there any plans to add the clip skip function in the near future?

Suggested previously by me here: https://github.com/nod-ai/SHARK/issues/1865
They've mentioned it before, but no concrete yes or no on implementation.


How to open a selected file by "less " instead of "vim"

Hi,
fff  is a wonderful tool I think which is easy to use. But When I want to open a selected text file whose sizes may be large than several GBs,  it's not easy to open it with vim. So how to change the tools (eg. less) to open a text file?
Thanks.

VISUAL is used for opening text files and those without an extension, with EDITOR and then vi as fallbacks. In your bashrc you can set one or both to less, but there is then no way to get to vi/m through fff. less allows you to press 'v' to go to vi/m, but that references the same environment variables and so will just launch itself. What I did is set both to 'editor', and then put the following in an executable file named editor in a folder on my path:
#!/bin/bash
[[ "$(ps -o comm= $PPID)" == "less" ]] && vim "$@" || less "$@"

This will launch less first, then if you press 'v' will switch to vim.

Hi! In my fork of fff I added an ability to open with any file (or multiple marked files) with a command provided by you e.g. pressing o and inputting less will open less with file(s) you wanted. Hope it helps.


[Bug]: BibTeX Batch Upload Error

Steps to reproduce the bug
1. BibTeX Batch Load Sources
2. Uploaded .bib file with some invalid entries highlighted in the preview
3. Upon selecting "create", I received the 500 error.
...
(Upon trying to recreate this issue today, the valid source entries were created.)

Screenshot
Cenozoic-Mollusca-Types_Zotero-Export_20240326 copy.txt
(this is a text version of the .bib file which is not supported in this box)
Expected behavior
When I upload a batch of sources with some invalid, I expect the valid entries to be created.
Additional Screenshots
No response
Environment
Sandbox
Sandbox Used
SANDBOX - build b12beec67
Version
No response
Browser Used
Chrome

@alexpaleo note that one entry in the file, when using the preview you can see that it has a formatting error.

So, all entries except any in red ought to upload.
Testing: to upload (after you do a Preview) you need to click to get the file again, then click Create
Result:

BibTeX Batch Load Sources
Imported 115 records.
Failed to import 3 records
You can see the errors for the entries that failed to upload.
You can
a) try to fix these errors manually if you can figure them out, then use the individual BibTeX import route
b) use a BibTeX linter (like https://flamingtempura.github.io/bibtex-tidy/index.html?) for these three entries
c) enter these manually
d) try to find the entries with a full-text search (as we demoed for you) in the New Source task
Hope this helps?

@alexpaleo I'm closing this ticket because I think this is solved ... by noting that after the preview step you have to go and click to (browse to) the file again, then click create to get the "green" sources to upload. If you still have an issue, with the same task, you can reopen the ticket.

Thank you!! Yes, I definitely have a greater understanding of entering the publications now.


feat: add icon for Vite

Syncing with https://github.com/jesseweed/seti-ui/pull/709 to bring in the icon for Vite config (following these instructions).

Thanks for the review @offensive-vk ! I think your approval didn't unblock the PR because of permission issues. It appears as a gray checkmark, and quoting from the docs:

Approvals with a gray check mark do not affect whether the pull request can be merged.


MySQLdb._exceptions.ProgrammingError: execute() first

I get that error when try to login...
MySQLdb._exceptions.ProgrammingError: execute() first

I get the same.. somebody could please help ?

Hi
Apologies for the lack of response.
Have you tried to edit the following bit:
https://github.com/Madpilot0/FlaskDashboard/blob/master/lib/Database.py#L32
And add prints for the sql and arguments to determine where the sql error lies.
			except MySQLdb.Error as e:
				print(e)
                                print(f"Query: {sql}")
                                print(f"Args: {str(args)}")

I'm currently not actively maintaining this project but in the future I'll probably make an updated version with better error handling.

I tried that.. still get the exact same error tho ..

Yes, but i was curious about the output ;-) Printing the messages won't fix the issue. I'm trying to see if I could quickly help you.

Seems that the error comes from the database/SQL side:
(1064, "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'groups G ON G.id = M.gid WHERE user = 'admin'' at line 1") Query: SELECT pass,firstname,lastname, G.name FROM users LEFT JOIN groupmembers M ON M.uid = id LEFT JOIN groups G ON G.id = M.gid WHERE user = %s Args: ['admin'] [2021-02-04 11:24:01,878] ERROR in app: Exception on /login [POST]

Ah, my best guess is that at the time of writing this I used MySQL 5.something. The latest version is (I think) 8.X which has some more reserved words. 'Groups' is one of those.


No module named 'requests'

I have runed python3 main.py -h but this show:
Traceback (most recent call last):
File "/Users/xxx/TikTok-Live-Recorder/main.py", line 4, in
from tiktokbot import TikTok
File "/Users/xxx/TikTok-Live-Recorder/tiktokbot.py", line 2, in
import requests as req
ModuleNotFoundError: No module named 'requests'
Plz help me, I am non coder

pip install -r requirements.txt

Hi i have installed Ffmpeg but this show " no module named ffmpeg ". Plz help me, thank u so much

pip install ffmpeg-python