Successful ResponseMessage with no content should have "result": null, not "result": {}

Per the specification:

If a request doesn’t provide a result value the receiver of a request still needs to return a response message to conform to the JSON-RPC specification. The result property of the ResponseMessage should be set to null in this case to signal a successful request.

haskell-language-server complains when it gets an empty object instead.
LSP debug message transcript:
02/20/24 10:37:32: Received {'id': 4, 'jsonrpc': '2.0', 'method': 'window/workDoneProgress/create', 'params': {'token': '37'}}
02/20/24 10:37:32: Sent {'id': 4, 'jsonrpc': '2.0', 'result': {}}

haskell-language-server complaint:
2024-02-20T18:37:32.356511Z | Error | LSP: incoming message parse error:
Error in $.result: expected 'null'
when processing
{"id":4,"jsonrpc":"2.0","result":{}}

It would be more compliant with the spec to send "result": null here.

Can you try changing the second parameter to null in https://github.com/yegappan/lsp/blob/main/autoload/lsp/handlers.vim#L193?

Yes, that change makes HLS cease complaining, I see this debug transcript and no error from the language server:
02/20/24 23:02:15: Received {'id': 2, 'jsonrpc': '2.0', 'method': 'window/workDoneProgress/create', 'params': {'token': '18'}}
02/20/24 23:02:15: Sent {'id': 2, 'jsonrpc': '2.0', 'result': null}

I have committed https://github.com/yegappan/lsp/commit/a4cdb9c723d83664fbad70ae070ea569459a2400 now to add this.  Let me know if you see any additional issues with the latest plugin.


Support TLSv1 on DH (and other?) tests

Most sites that enable DHE, do so to get Forward Secrecy on older clients that don't support ECDHE. By only negotiating TLSv1.2 and TLSv1.1 on the DH2048/1024/512 pages, none of the legacy systems/browsers can even connect to the page. Appreciate this may not be the primary use case for this project/site but it would be very useful to be able to confirm DH2048 support on things like OS X before 10.9, Chrome before 22, Firefox before 23 and lots and lots of mobile devices.

It's totally a fair use case. After all, the site is called "bad ssl".
Some of the subdomains require certain TLS versions to support the proper features, but I've changed the default config, which is used by these domains.
Would you mind testing if that serves your need for those domains?
If so, I can try to put in the work to expand to more subdomains.

A slight problem with the DH*.badssl.com domains. It looks like RSA-3DES snuck in on the TLS1/SSLv3 protocol configs so DH2048.badssl.com is visible on winXP with ie6 because it connects using a non-DHE cipher suite (and thus gives false positives). Other than that, this is exactly what I needed.

Here is the output from sslyze for dh2048.badssl.com, it believes that only SSLv3 ciphers are non-DHE. ssllabs.com seemed to think it was connecting via tlsv1 and 3DES for IE8+XP, but as that is an simulation, I'm more inclined to test sslyze here.

TLSV1_2 Cipher Suites:
Preferred:
DHE-RSA-AES128-GCM-SHA256     DH-2048 bits   128 bits      HTTP 200 OK
Accepted:
DHE-RSA-AES256-SHA256         DH-2048 bits   256 bits      HTTP 200 OK
DHE-RSA-AES256-SHA            DH-2048 bits   256 bits      HTTP 200 OK
DHE-RSA-AES256-GCM-SHA384     DH-2048 bits   256 bits      HTTP 200 OK
DHE-RSA-AES128-SHA256         DH-2048 bits   128 bits      HTTP 200 OK
DHE-RSA-AES128-SHA            DH-2048 bits   128 bits      HTTP 200 OK
DHE-RSA-AES128-GCM-SHA256     DH-2048 bits   128 bits      HTTP 200 OK

TLSV1_1 Cipher Suites:
Preferred:
DHE-RSA-AES128-SHA            DH-2048 bits   128 bits      HTTP 200 OK
Accepted:
DHE-RSA-AES256-SHA            DH-2048 bits   256 bits      HTTP 200 OK
DHE-RSA-AES128-SHA            DH-2048 bits   128 bits      HTTP 200 OK

SSLV3 Cipher Suites:
Preferred:
ECDHE-RSA-AES128-SHA          ECDH-256 bits  128 bits      HTTP 200 OK
Accepted:
ECDHE-RSA-AES256-SHA          ECDH-256 bits  256 bits      HTTP 200 OK
DHE-RSA-CAMELLIA256-SHA       DH-1024 bits   256 bits      HTTP 200 OK
DHE-RSA-AES256-SHA            DH-1024 bits   256 bits      HTTP 200 OK
CAMELLIA256-SHA               -              256 bits      HTTP 200 OK
AES256-SHA                    -              256 bits      HTTP 200 OK
ECDHE-RSA-AES128-SHA          ECDH-256 bits  128 bits      HTTP 200 OK
DHE-RSA-CAMELLIA128-SHA       DH-1024 bits   128 bits      HTTP 200 OK
DHE-RSA-AES128-SHA            DH-1024 bits   128 bits      HTTP 200 OK
CAMELLIA128-SHA               -              128 bits      HTTP 200 OK
AES128-SHA                    -              128 bits      HTTP 200 OK
ECDHE-RSA-DES-CBC3-SHA        ECDH-256 bits  112 bits      HTTP 200 OK
DES-CBC3-SHA                  -              112 bits      HTTP 200 OK

TLSV1 Cipher Suites:
Preferred:
DHE-RSA-AES128-SHA            DH-2048 bits   128 bits      HTTP 200 OK
Accepted:
DHE-RSA-AES256-SHA            DH-2048 bits   256 bits      HTTP 200 OK
DHE-RSA-AES128-SHA            DH-2048 bits   128 bits      HTTP 200 OK

Closing this issue because the original ask was completed (but opening a new issue given the false positive problem)


OSIDB-2737: Remove flaw resolution field

The attribute Flaw.resolution represents the Bugzilla resolution which is no more relevant in the future workflow but is being often confused with the actual workflow stuff.
This field was deprecated in #171
This change is part of the 4.0 release
Closes OSIDB-2737

Just a small note, after merging #545, you will need to rebase and move the migration from 133 to 134. Sorry for the inconvenience.


fixes #130

Fixes Issue #130
(Metagenomics -> Metagenomic)

CI error appears to be a build issue w/Qiita and SSL. Will review later.

Looks good, my only concern is that notebooks/metagenomics_samplesheet_generator.ipynb was executed while the original version wasn't; is this OK or is better to not have it executed?

Oh sure, that's okay. All I did was clear the outputs - I tested it before clearing them.


chore(erigon): update erigon v.2.45.1 -> v2.45.2

It's strange that there are no changes in hash here

The vendor hash will only change if one of the module dependencies changes. I guess they've only been making adjustments to the erigon source.

I needed to manually break the source hash and the vendor hash to get a hash mismatch to then update with the correct hashes.
I don't understand why we weren't getting a mismatch before after changing the version.

@selfuryon after speaking with @NinjaTrappeur:

The fixed output derivations (FOD, the derivation for which you give an expected sha256) are output-adressed. Their hash is not computed from their inputs but via the specified sha256.
Here, you did not change the output hash, Nix considered the output hash as derivation hash. You already had this path in your store, Nix did not try to rebuild it, you did not see the hash mismatch.
You do not face this issue with "regular" derivations because changing any input changes the derivation output hash.

So moral of the story is always break the hash on update to get a mismatch and hence figure out what the new hash should be.


Random recipes

If there are any mistakes I'm sorry, I just proofread about 3000 to 4000 wiki pages.

I don't know where I can get the item's ntbtag to check.

just replace the 580 in the nbt tag for a 750 and it should stop screaming at you

Most of your changes have a random space behind the modver is there a reason why?

Yes, because I have a habit of putting a space at the end, and I ended up forgetting to delete it before uploading.


{CI} Enable component detection in release branch

CG only runs in default branch.
Set ComponentDetection.ForceScan to enable CG in release branch.

ComponentDetection.ForceScan - When enabled, the auto-injected build task will execute a scan in your build no matter if the branch is not in scope (e.g. non-default branch)  ---https://docs.opensource.microsoft.com/tools/cg/component-detection/variables/

##[info]Looking for pipeline information in Product Catalog...
##[info]Evaluating Branch...
##[info]SourceBranch: refs/heads/release
##[info]DefaultBranch: refs/heads/dev
##[info]Result: Skipping scan. Reason: Pipeline is not in-scope for automatic open source vulnerability scans and not default branch.

It also skip running when CFS is not enabled.

You are using a private feed for PIP, set by the PIP_INDEX_URL variable, or the Pip Authenticate build task  ---Ref: https://docs.opensource.microsoft.com/tools/cg/component-detection/tsg/pipreport/

Skipping pip report due to invalid PIP_INDEX_URL.

PipReport: Found PipReportOverrideBehavior environment variable set to Skip. Skipping pip detection for 'D:\a\_work\1\s\requirements.txt'.

Thank you for your contribution! We will review the pull request and get back to you soon.


Fix ONNX export for the latest non-streaming zipformer.

See https://github.com/k2-fsa/icefall/commit/c3e23ec8d2a3ed2547bd94dee7280bd3f193a47e#commitcomment-120481693
TODO

[ ] Add GitHub actions to covert ONNX export-related scripts in separate pull requests.

@joazoa
Please try this pull request. I have tested it locally that  both zipformer/export-onnx.py and zipformer/export-onnx-streaming.py  work as expected with this change. Also, the exported non-streaming and streaming models are able to decode files with onnx_pretrained.py and onnx_pretrained-streaming.py, respectively.

This solved he problem, thank you for fixing it (and apologies for not clarifying earlier that this was the offline export).


[NEW]: Binance leaves the Canadian market

Date
2023-05-12
Description
Binance will withdraw from the Canadian market, the cryptocurrency exchange announced on Twitter on May 12. It called its withdrawal “proactive” as new guidance issued by Canadian regulators continues to take a toll on the country’s crypto industry.
Links
https://cointelegraph.com/news/binance-calls-it-quits-in-canada-blames-new-rules
https://twitter.com/binance/status/1657099651210969088?s=20
Agreement

[X] I irrevocably agree to release my contribution under the CC-BY 3.0 License

Attribution name
Sander van Kasteel
Personal link
https://mastodon.online/@SuitedUpDev

Thanks! https://web3isgoinggreat.com/?id=binance-exits-canada


TF 2.0.0 Python 3.8 TypeError: _logger_find_caller() takes from 0 to 1 positional arguments but 2 were given

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):  See script from Tensorflow training session and uploaded file below.  Nb: There is no error with TF2.0.0 and python 3.6 or 3.7.  The error occurs with TF2.0.0 and python 3.8.
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 18.04
TensorFlow installed from (source or binary): source
TensorFlow version (use command below): 2.0.0
Python version: 3.8
Bazel version (if compiling from source): 0.26.1
GCC/Compiler version (if compiling from source): 7.4.0
CUDA/cuDNN version: CUDA 10/cuDNN 7.6.4
GPU model and memory: NVidia RTX 2080 TI and 2080 MaxQ

Describe the current behavior
After running the code below (with the attached file), you get the following error:

AssertionError                            Traceback (most recent call last)
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/autograph/impl/api.py in converted_call(f, args, kwargs, caller_fn_scope, options)
525         options=options, autograph_module=tf_inspect.getmodule(converted_call))
--> 526     converted_f = conversion.convert(target_entity, program_ctx)
527
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/autograph/impl/conversion.py in convert(entity, program_ctx)
324
--> 325   converted_entity_info = _convert_with_cache(entity, program_ctx,
326                                               free_nonglobal_var_names)
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/autograph/impl/conversion.py in _convert_with_cache(entity, program_ctx, free_nonglobal_var_names)
238
--> 239     nodes, converted_name, entity_info = convert_entity_to_ast(
240         entity, program_ctx)
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/autograph/impl/conversion.py in convert_entity_to_ast(o, program_ctx)
474   elif tf_inspect.ismethod(o):
--> 475     nodes, name, entity_info = convert_func_to_ast(o, program_ctx)
476   elif hasattr(o, 'class'):
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/autograph/impl/conversion.py in convert_func_to_ast(f, program_ctx, do_rename)
672   context = converter.EntityContext(namer, entity_info, program_ctx, new_name)
--> 673   node = node_to_graph(node, context)
674
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/autograph/impl/conversion.py in node_to_graph(node, context)
702   node = converter.standard_analysis(node, context, is_initial=True)
--> 703   node = converter.apply_(node, context, function_scopes)
704   node = converter.apply_(node, context, arg_defaults)
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/autograph/core/converter.py in apply_(node, context, converter_module)
408   node = standard_analysis(node, context)
--> 409   node = converter_module.transform(node, context)
410   return node
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/autograph/converters/function_scopes.py in transform(node, ctx)
119 def transform(node, ctx):
--> 120   return FunctionBodyTransformer(ctx).visit(node)
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/autograph/core/converter.py in visit(self, node)
345     try:
--> 346       return super(Base, self).visit(node)
347     finally:
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/autograph/pyct/transformer.py in visit(self, node)
479     if not anno.hasanno(node, anno.Basic.SKIP_PROCESSING):
--> 480       result = super(Base, self).visit(node)
481     self.ctx.current_origin = parent_origin
/usr/local/lib/python3.8/ast.py in visit(self, node)
359         visitor = getattr(self, method, self.generic_visit)
--> 360         return visitor(node)
361
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/autograph/converters/function_scopes.py in visit_FunctionDef(self, node)
101     """
--> 102     wrapped_body = templates.replace(
103         template,
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/autograph/pyct/templates.py in replace(template, **replacements)
268   for node in nodes:
--> 269     node = ReplaceTransformer(replacements).visit(node)
270     if isinstance(node, (list, tuple)):
/usr/local/lib/python3.8/ast.py in visit(self, node)
359         visitor = getattr(self, method, self.generic_visit)
--> 360         return visitor(node)
361
/usr/local/lib/python3.8/ast.py in generic_visit(self, node)
435                     if isinstance(value, AST):
--> 436                         value = self.visit(value)
437                         if value is None:
/usr/local/lib/python3.8/ast.py in visit(self, node)
359         visitor = getattr(self, method, self.generic_visit)
--> 360         return visitor(node)
361
/usr/local/lib/python3.8/ast.py in generic_visit(self, node)
444             elif isinstance(old_value, AST):
--> 445                 new_node = self.visit(old_value)
446                 if new_node is None:
/usr/local/lib/python3.8/ast.py in visit(self, node)
359         visitor = getattr(self, method, self.generic_visit)
--> 360         return visitor(node)
361
/usr/local/lib/python3.8/ast.py in generic_visit(self, node)
435                     if isinstance(value, AST):
--> 436                         value = self.visit(value)
437                         if value is None:
/usr/local/lib/python3.8/ast.py in visit(self, node)
359         visitor = getattr(self, method, self.generic_visit)
--> 360         return visitor(node)
361
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/autograph/pyct/templates.py in visit_Name(self, node)
199
--> 200     new_nodes = self._prepare_replacement(node, node.id)
201
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/autograph/pyct/templates.py in _prepare_replacement(self, replaced, key)
138
--> 139     new_nodes = ast_util.copy_clean(repl, preserve_annos=self.preserved_annos)
140     if isinstance(new_nodes, gast.AST):
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/autograph/pyct/ast_util.py in copy_clean(node, preserve_annos)
75   """
---> 76   return CleanCopier(preserve_annos).copy(node)
77
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/autograph/pyct/ast_util.py in copy(self, node)
53       if not f.startswith('__') and hasattr(node, f):
---> 54         new_fields[f] = self.copy(getattr(node, f))
55     new_node = type(node)(**new_fields)
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/autograph/pyct/ast_util.py in copy(self, node)
40     if isinstance(node, list):
---> 41       return [self.copy(n) for n in node]
42     elif isinstance(node, tuple):
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/autograph/pyct/ast_util.py in (.0)
40     if isinstance(node, list):
---> 41       return [self.copy(n) for n in node]
42     elif isinstance(node, tuple):
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/autograph/pyct/ast_util.py in copy(self, node)
54         new_fields[f] = self.copy(getattr(node, f))
---> 55     new_node = type(node)(**new_fields)
56
~/tf38/lib/python3.8/site-packages/gast/gast.py in create_node(self, *args, **kwargs)
9         nbparam = len(args) + len(kwargs)
---> 10         assert nbparam in (0, len(Fields)),
11             "Bad argument number for {}: {}, expecting {}".\
AssertionError: Bad argument number for keyword: 1, expecting 2
During handling of the above exception, another exception occurred:
TypeError                                 Traceback (most recent call last)
 in
----> 1 tf_model.fit(Xs_train[:, 0:1], y_train.reshape(-1, 1));
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/eager/def_function.py in call(self, *args, **kwds)
566         xla_context.Exit()
567     else:
--> 568       result = self._call(*args, **kwds)
569
570     if tracing_count == self._get_tracing_count():
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/eager/def_function.py in _call(self, *args, **kwds)
613       # This is the first call of call, so we have to initialize.
614       initializers = []
--> 615       self._initialize(args, kwds, add_initializers_to=initializers)
616     finally:
617       # At this point we know that the initialization is complete (or less
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/eager/def_function.py in _initialize(self, args, kwds, add_initializers_to)
494     self._graph_deleter = FunctionDeleter(self._lifted_initializer_graph)
495     self._concrete_stateful_fn = (
--> 496         self._stateful_fn._get_concrete_function_internal_garbage_collected(  # pylint: disable=protected-access
497             *args, **kwds))
498
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/eager/function.py in _get_concrete_function_internal_garbage_collected(self, *args, **kwargs)
2363       args, kwargs = None, None
2364     with self._lock:
-> 2365       graph_function, _, _ = self._maybe_define_function(args, kwargs)
2366     return graph_function
2367
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/eager/function.py in _maybe_define_function(self, args, kwargs)
2671
2672       self._function_cache.missed.add(call_context_key)
-> 2673       graph_function = self._create_graph_function(args, kwargs)
2674       self._function_cache.primary[cache_key] = graph_function
2675       return graph_function, args, kwargs
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/eager/function.py in _create_graph_function(self, args, kwargs, override_flat_arg_shapes)
2551     arg_names = base_arg_names + missing_arg_names
2552     graph_function = ConcreteFunction(
-> 2553         func_graph_module.func_graph_from_py_func(
2554             self._name,
2555             self._python_function,
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/framework/func_graph.py in func_graph_from_py_func(name, python_func, args, kwargs, signature, func_graph, autograph, autograph_options, add_control_dependencies, arg_names, op_return_value, collections, capture_by_value, override_flat_arg_shapes)
956                                           converted_func)
957
--> 958       func_outputs = python_func(*func_args, **func_kwargs)
959
960       # invariant: func_outputs contains only Tensors, CompositeTensors,
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/eager/def_function.py in wrapped_fn(*args, **kwds)
437         # wrapped allows AutoGraph to swap in a converted function. We give
438         # the function a weak reference to itself to avoid a reference cycle.
--> 439         return weak_wrapped_fn().wrapped(*args, **kwds)
440     weak_wrapped_fn = weakref.ref(wrapped_fn)
441
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/eager/function.py in bound_method_wrapper(*args, **kwargs)
3179     # However, the replacer is still responsible for attaching self properly.
3180     # TODO(mdan): Is it possible to do it here instead?
-> 3181     return wrapped_fn(*args, **kwargs)
3182   weak_bound_method_wrapper = weakref.ref(bound_method_wrapper)
3183
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/framework/func_graph.py in wrapper(*args, **kwargs)
935           # TODO(mdan): Push this block higher in tf.function's call stack.
936           try:
--> 937             return autograph.converted_call(
938                 original_func,
939                 args,
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/autograph/impl/api.py in converted_call(f, args, kwargs, caller_fn_scope, options)
552           'Cause: %s', target_entity, e)
553     else:
--> 554       logging.warn(
555           'AutoGraph could not transform %s and will run it as-is.\n'
556           'Please report this to the TensorFlow team. When filing the bug, set'
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/autograph/utils/ag_logging.py in warn(msg, *args, **kwargs)
144
145 def warn(msg, *args, **kwargs):
--> 146   logging.warn(msg, *args, **kwargs)
147   if echo_log_to_stdout:
148     _output_to_stdout('WARNING: ' + msg, *args, **kwargs)
~/tf38/lib/python3.8/site-packages/tensorflow_core/python/platform/tf_logging.py in warn(msg, *args, **kwargs)
159 @tf_export(v1=['logging.warn'])
160 def warn(msg, *args, **kwargs):
--> 161   get_logger().warning(msg, *args, **kwargs)
162
163
/usr/local/lib/python3.8/logging/init.py in warning(self, msg, *args, **kwargs)
1444         """
1445         if self.isEnabledFor(WARNING):
-> 1446             self._log(WARNING, msg, args, **kwargs)
1447
1448     def warn(self, msg, *args, **kwargs):
/usr/local/lib/python3.8/logging/init.py in _log(self, level, msg, args, exc_info, extra, stack_info, stacklevel)
1563             #IronPython can use logging.
1564             try:
-> 1565                 fn, lno, func, sinfo = self.findCaller(stack_info, stacklevel)
1566             except ValueError: # pragma: no cover
1567                 fn, lno, func = "(unknown file)", 0, "(unknown function)"
TypeError: _logger_find_caller() takes from 0 to 1 positional arguments but 2 were given
Describe the expected behavior
There should be no error.  It works fine with TF2.0.0 and Python 3.6 or Python 3.7.
Code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate the problem.
import tensorflow as tf
import numpy as np
import gzip
import json
from sklearn.model_selection import ShuffleSplit
with gzip.open("small_data/cal_house.json.gz", "r") as fin:
housing = json.load(fin)
for train, test in ShuffleSplit(1, 0.2, random_state=42).split(housing['data']):
X_train = np.array(housing['data'])[train].astype(np.float32)
y_train = np.array(housing['target'])[train].astype(np.float32)
X_test = np.array(housing['data'])[test].astype(np.float32)
y_test = np.array(housing['target'])[test].astype(np.float32)
X_mean = X_train.mean(axis=0)
X_std = X_train.std(axis=0)
Xs_train = (X_train - X_mean) / X_std
Xs_test = (X_test - X_mean) / X_std
class LinearRegressionTF():
def init(self, eta=.1):
self.W = tf.Variable(0.)
self.b = tf.Variable(0.)
self.opt = tf.keras.optimizers.SGD(learning_rate=eta)
def loss(self, X, y, return_func=False):
    def loss_():
        return tf.reduce_mean(tf.square(X * self.W + self.b - y))

    if not return_func:
        return loss_()

    return loss_

@tf.function
def fit(self, X, y, steps=1):
    for _ in range(steps):
        self.opt.minimize(self.loss(X, y, return_func=True), [self.W, self.b])

tf_model = LinearRegressionTF()
tf_model.fit(Xs_train[:, 0:1], y_train.reshape(-1, 1));
cal_house.json.gz
Other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
Nil

@dbonner
I tried to reproduce the issue. However i am seeing the different error.`AttributeError: 'LinearRegressionTF' object has no attribute 'fit' .Please, help me with the reproducible code . It helps in localizing the issue faster.

@ravikyram
I've finally got this right.  Sorry to mess you around with this.  Github markdown removed the underscores on the init part of the LinearRegressionTF() class when I pasted it in.  This got transferred through to the code file.  The correct code is attached.  It runs fine in Python 3.7 but errors in Python 3.8.  I have also removed the reference to the subdirectory "small_data" so you can run the code with the file "cal_house.json.gz" in the current working directory.
code_py38_tf2_error.txt
cal_house.json.gz

Hi @ymodak,
Have you had a chance to test the python 3.8 error I reported (Issue: #33799).
All the best,
Dan

I am able to reproduce the issue with the following command on python 3.8 (master build):
bazel test -s --verbose_failures --disk_cache=/home/ubuntu/bazel //tensorflow/python:image_ops_test

Haven't figure out the reason yet.

@dbonner @ymodak Added a PR #33953 for the fix. Please take a look.

I recieved this error also when using tensorflow 1.13.2 + python 3.8 I am considering opening a separate issue.


Issue downloading antelopev2 using insightface

https://github.com/deepinsight/insightface/releases/download/v0.7/antelopev2.zip
does not exist

Link on main page to alternative url: https://github.com/deepinsight/insightface/issues/1896#issuecomment-1023867304


chore: Release 0.4.0

:robot: I have created a release beep boop
0.4.0 (2023-06-07)
⚠ BREAKING CHANGES

Recursion (#207)

Features

Recursion (#207) (6fc479b)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/noir-lang/acvm-backend-barretenberg/releases/tag/v0.4.0 :sunflower:


ChangeLog: Ability to refer to a ticket ID when the published change is a bug fix

When we publish changes related to a product bug fix, today there is no way to specify which ticket is resolved with this fix. If we'd have this feature and content, users of changelog can easily identify if the fix is related to a bug they may've raised.
We don't need to have any deeplinking from the ticket reference, but just the free text field would be enough.
I can understand this will require change on CH one model, integration and also on the front end. We may want to ask Frank's opinion in means of design if needed.
Thanks, Recai

@markvanaalst : I think this has been addressed in a recent release, correct?

Mark has confirmed that this is implemented in the Changelog.


data repetition

Possible hiccup in the May 12th release.
picking up the last archives performed about every 20 mins & re-posts it to browser.
(note: doesn't re-archive, just re-posts)

Resolved


feat: add graphql-js template

Implementation
Modify core to output according to template type. Use a key templateType in .template.json in the project root.

Let's chat about this. It works nicely.

Approved by mistake. Do you think that my arguments are sane?

Yes, what do you suggest then?

Yes. This is quite tricky to test and makes the generator much more complex.
Let's imagine that we want to generate a different format than knex and in this generator, we will need to also have template type covered. This change makes things much more complex and less contributor friendly. Our success depends on extensibility - if it is hard to extend

If we would want a different format then knex, similarily we would be generating metadata we are doing here and using it in template. How do we make it extensible. Maybe we can separate the generating metadata and putting it in a template?


Slider. The center of thumb doesn't always correspond a mouse click

0.4.0-build210
https://user-images.githubusercontent.com/5963351/119486995-8a9db200-bd61-11eb-9f4d-b6b2ba1c3ef7.mp4
We can see that if we click:

on the left side of the Slider - thumb will be to the right of the cursor
on the right side - to the left of the cursor
on the middle - near the center

Closed in upstream

Should be fixed in 1.1.0 too

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


EasyCLA GitHub App says Missing CLA Authorization for signed commits with CLA

Summary
Several days ago we noticed that EasyCLA GitHub App now always saying that the commit is not authorized under a signed CLA.
EasyCLA shows status:  Missing CLA Authorization.
If trying to follow the links in the comments from EasyCLA they don't work. The return the next response: {"message": "Internal server error"}.
Background
Provide context to the issue - provide steps to reproduce the behavior, such as:

Go to https://github.com/JanusGraph/janusgraph/pull/2731 or https://github.com/JanusGraph/janusgraph/pull/2657
Click on 'Please click here to be authorized'.
See error {"message": "Internal server error"}

Expected behavior

Go to https://github.com/JanusGraph/janusgraph/pull/2731 or https://github.com/JanusGraph/janusgraph/pull/2657
Click on 'Please click here to be authorized'.
See steps to get authorization.

Environment
Please complete the following information:

Environment:

[ ] ALL
[ ] DEV
[ ] STAGING
[X] PROD

Browser:

[X] Chrome/Brave
[X] Firefox
[ ] Opera
[ ] Vivaldi
[ ] LibreWolf
[ ] SRware Iron
[ ] Dissenter
[ ] Slimjet
[ ] Midori
[ ] Edge
[ ] Lynx

I don't know if that's related to EasyCLA or something else but I see in response headers the next header:
x-cache | Error from cloudfront which would mean that it's a problem on cloudfront side but I'm not sure.

@porunov - two points:

We observed an issue on Friday where the app did not properly report status (status did not update).  We apologize for the inconvenience. This was due to an indexing issue in our database that caused the process to fail. As a result, PR's that were opened during this time window were blocked since the EasyCLA app did not report status.  This was resolved on Friday.
While evaluating this issue, we also discovered that the "/easycla" comment is not properly triggering the app to re-evaluate the CLA status in all cases. We are currently investigating this issue. Until we get this resolved, you can close and re-open the PR to force the EasyCLA app to report status.

CC: @WillsonHG

@porunov this issue should be resolved now.  I see that your PR referenced above passed the CLA authorization/gating and was merged.  Awesome! Thanks for the ticket and for helping us resolve the issue. Closing this ticket.


Clickable Wizard Step

Is there any chance for you to make wizard steps clickable? For example I want to click on the title or icon or number of any wizard step?
This is very nice plugin but lacking this only feature which is much needed for my project.

We can utilize [canExit] and (canEnter) for validation purpose and avoid jumping back and fourth between un-allowed stats. What you think?

The question then is how do we visualize which steps can be entered in the navigation bar?
I think it should be easily possible for the user to see this.
In addition we need to take subsequent steps into account, e.g. if step 2 can't be entered step 3 and 4 should automatically not be enterable, because they likely depend on step 2, right?

If I am on step 1 and wanna jump to step 3, It should validate just like:

canExit Step 1
canEnter and canExit Step 2
canEnter Step 3
Can do this kind of iteration.

We can do it recursively. Lets say canExit of Step 1 is failed we can make step 1 navigation circle red kinda and return an error via an event.

In addition we would need some kind of indicator that tells us if the step has been entered once, otherwise the whole wizard navigation bar will show up red when the user opens it.
Do you want to give it a try?

Ok, I've put some more thoughts into this.
My idea is to introduce three "navigation modes" for the wizard. These modes describe the possible behavior for the navigation between steps:

strict navigation:
The first navigation mode is strict navigation. This mode describes the status quo, i.e. the current navigation behavior of the wizard. Currently you can only navigate through the wizard steps in a linear fashion, where you can only enter the next step if all previous steps have been completed and the exit condition of your current step have been fulfilled. In this mode it is not possible to jump between different steps, i.e. move to step 3 from step 1, then go to step 2 to finally go to step 4. The only exception to this rule are optional steps, which a user can skip. Therefore you are required to do the steps in the order 1 -> 2 -> 3 -> 4.
semi-strict navigation:
The second navigation mode is semi-strict navigation. This mode lets the user navigate between the steps in any order he likes. This means that in this navigation mode a user could complete the steps in the order 1 -> 3 -> 2 -> 4, if the exit conditions have been fulfilled. This mode has only one restriction, where the user can enter the completion step after he has completed all previous steps. Again optional steps are skipable in this mode.
free navigation:
The third navigation mode is free navigation. This mode let's the user navigate freely between the different steps, including the completion step, in any order he desires.

To let the wizard stay backwards compatible strict navigation mode will be the default mode.
What do you think, would this full your needs?

Ok, I've now implemented the three navigation modes and merged them to the master branch.
Before I do a new release I first want to do some of the other open issues, therefore you will need to wait a while before you can see the changes on npm.
In case you want to give the new modes a try feel free to build the master branch and test it.


upgrade golang to 1.9.6 and fix model auto registry problem - [closed]

In GitLab by @tmon546596046 on May 24, 2018, 07:53
Merges updatek8s18 -> updatek8s18

In GitLab by @wknet123 on Nov 13, 2019, 11:01
closed


properties to set window size globally

added two params browserWindowWidth and browserWindowHeight
set window size in DriverFactoryHelper
update WebTests
create two input params to index.html

Please check the test results, I believe the code is just missing x,y which can be set to zero and zero @georgii-musikhin

@MohabMohie sorry, but I didn't get you
Do you mean that with unit tests the windows size will be 0x0?
I've run then and it was 1920x1080, because they are default values


feat: add kns and kctx tools to bluefin

Need to find a clean way to also include completion for bash/zsh but that could be a userland/just follow-up :)

Looks like the latest versions have been ported to golang and are available on the releases page: https://github.com/ahmetb/kubectx/releases
For that I would just copy the pattern earlier in the containerfile that we use for kind to get the binaries that way. And then just git clone the completion directory wherever in /usr/share they're supposed to go: https://github.com/ahmetb/kubectx/tree/master/completion


Blackjack is broken, bot doesnt respond to .hit .stand or .double

I can't reproduce it using latest github pull on a Debian 9 box. Blackjack is working fine for me.

Blackjack is fixed. Update your bot. If you're on latest version of windows, then it didn't make it in the last patch and will be fixed in the next one.


More robust version checking

update isGreaterEqualMinVersion for more robust version checking. Works with any number of . separators, and multi-digit version numbers in any position

resolves #251


Add multi mentions support for f!pat, f!cuddle and f!hug

just realized that its not possible lul, fml

done, somehow


Not a Function

Hallo thank you for a nice package, but when I running,  I got Error on
/pathFile/node_modules/allure-single-html-file-js/src/combine-allure.js:65
const ext = file.split('.').at(-1);
^
TypeError: file.split(...).at is not a function
and after I change to length - 1 got this error:
/pathFile/node_modules/allure-single-html-file-js/src/combine-allure.js:148
content = `${d.content.replaceAll('\', '\\').replaceAll('"', '\"').replaceAll('\r\n', '\n').replaceAll('\n', '\n')
^
TypeError: d.content.replaceAll is not a function
Can you fix that on the next update? thank you!

Hello. What browser you are using and which version it has?

Also, please attach your report in zip-archive

@Fulki88 I've discovered that you are using not my script, but it's port to javascript, written by another author.
Here is the repo, you should create issue there: https://github.com/aruiz-caritsqa/allure-single-html-file-js


ZEN17 endpoints improperly mapped

Describe the bug
The new Zooz ZEN17 Universal Relay allows the two inputs (S1/S2) to be decoupled from control of the two relays (R1/R2). The prototypical use case for this is a garage door connected to R1 and a reed switch connected to S2, which is templated in HA to be the open/close state of the door.
At present, when S2 is decoupled from R2, a change to S2 causes R1 to switch. The log file shows:
14:10:17.365 CNTRLR   [Node 140] Mapping unsolicited report from root device to first supporting end
                      point #1

Adding the preserveRootApplicationCCValueIDs compat flag to the device file fixes this aspect and a third entity is created for the root endpoint. I've merged a draft PR to this effect.
However, S2 changing still causes R2 to physically change. I'm unsure if this is a device bug (not respecting the parameter setting) or we're commanding the R2 endpoint to on:
14:25:40.237 DRIVER « [Node 140] [REQ] [ApplicationCommand]
           └─[BinarySwitchCCReport]
             current value: true
             target value: true
             duration:   [Duration: 0seconds]
14:25:40.312 DRIVER « [Node 140] [REQ] [ApplicationCommand]
           └─[MultiChannelCCCommandEncapsulation]
            │ source:   2
            │ destination: 0
            └─[BinarySwitchCCReport]
              current value: true
              target value: true
              duration:   [Duration: 0seconds]

Additionally, commanding S1 to on causes the root endpoint to also turn on, so this may confuse HA/users. (It does technically work because the root endpoint stays on if either R1 or R2 is on, so what happens at present is you command S1 on, R1 triggers door (then goes back off), root endpoint turns on with S1, reed sensor opens, report is received from S2, R2 physically turns on (shouldn't happen), S2 goes off, R2 goes off, root endpoint goes off.)
14:34:20.307 DRIVER » [Node 140] [REQ] [SendData]
           │ transmit options: 0x25
           │ callback id:   210
           └─[MultiChannelCCCommandEncapsulation]
            │ source:   0
            │ destination: 1
            └─[BinarySwitchCCSet]
              target value: true
14:34:20.316 DRIVER « [RES] [SendData]
            was sent: true
14:34:20.390 DRIVER « [REQ] [SendData]
            callback id:   210
            transmit status: OK
14:34:20.814 DRIVER « [Node 140] [REQ] [ApplicationCommand]
           └─[BinarySwitchCCReport]
             current value: true
             target value: true
             duration:   [Duration: 0seconds]
14:34:20.884 DRIVER « [Node 140] [REQ] [ApplicationCommand]
           └─[MultiChannelCCCommandEncapsulation]
            │ source:   1
            │ destination: 0
            └─[BinarySwitchCCReport]
              current value: true
              target value: true
              duration:   [Duration: 0seconds]
14:34:21.444 DRIVER » [Node 140] [REQ] [SendData]
           │ transmit options: 0x25
           │ callback id:   211
           └─[MultiChannelCCCommandEncapsulation]
            │ source:   0
            │ destination: 1
            └─[BinarySwitchCCGet]
14:34:21.452 DRIVER « [RES] [SendData]
            was sent: true
14:34:21.536 DRIVER « [REQ] [SendData]
            callback id:   211
            transmit status: OK
14:34:21.728 DRIVER « [Node 140] [REQ] [ApplicationCommand]
           └─[MultiChannelCCCommandEncapsulation]
            │ source:   1
            │ destination: 0
            └─[BinarySwitchCCReport]
              current value: true
              target value: true
              duration:   [Duration: 0seconds]

What should happen is: S1 triggers R1 to trigger door (then goes off), reed sensor opens, report is received from S2, S2 turns on, S2 goes off.) If our endpoint is tracking R2 and not S2 then fixing that would actually cause a different issue I think as we would no longer have an entity to template to track the door open/close state (unless the root endpoint) continues to turn on with S2, but we'd need to see.

node_interview.txt
node_140.json.zip

The new Zooz ZEN17 Universal Relay allows the two inputs (S1/S2) to be decoupled from control of the two relays (R1/R2)

Did Zooz say how this is supposed to work in terms of Z-Wave? What you describe (or at least what's happening in the logs) seems like its not conforming with the specifications. Since it is a new device, I'm 99.9% sure we shouldn't need to use the compat flag to preserve root endpoint values:

I haven't reached out to them yet as I wanted to understand if it was us or them. The issue seems to be that we always map the message on the root endpoint to endpoint 1, so when a message comes through for 2 we turn on 1.

Their original email does say to exclude and re-include so a new entity is created.

That's required by the Z-Wave specs for actions which change the capabilities of a device. So it might just be that the device is only halfway there. It's a bit unfortunate, but you'll actually have to re-include without hard-resetting the device.

Ok, I'll try it.

FWIW, I am seeing the exact same thing with my Zooz ZEN16 (originally opened as an issue in HA Core).  I hadn't gotten around to creating a PR to add the preserveRootApplicationCCValueIDs flag to the ZEN16 yet, so I guess I will first try excluding and re-including to see if that works.

It didn't make any difference on mine. I don't have any switches connected to my zen16 to test it.

Ok, after more info from Zooz. The root endpoint thing is something they're looking at but we need the compat flag for the ZEN17. Based on the description, we also need this for the ZEN16.
The relay controlling despite parameter 10/11 being enabled is because this only works with certain switch types. I've edited our description to make this clear.
Healing nearby nodes seems to have fixed my interview issues, at least the parameter values are now loading up on interview.
I think my PR closes these issues and renders this relay good-to-go.


Invalid "main" entry

Hello, I've encountered this error and I can't seem to get rid of it.

Here what my package.json looks like:
{   "name": "",   "version": "1.0.0",   "main": "index.js",   "license": "MIT",   "scripts": {     "dev:server": "tsnd --respawn --transpileOnly src/index.ts"   },   "devDependencies": {     "@types/express": "^4.17.7",     "ts-node-dev": "^1.0.0-pre.61",     "typescript": "^4.0.2"   },   "dependencies": {     "@types/node": "^14.6.0",     "express": "^4.17.1"   } }
Is there anything missing?

Happens in any project that uses ts-node-dev?

Yes, every project i create from now on it throws me that error, i feel like i'm doing something wrong, but i'm following typescript documentation...
Would you advice me a way to debug this error?
I go into the node_modules folder and there's not an index.js file as it said in the error, but since it's a typescript module there's no need right? I might sound like a complete nood haha, but i'm getting into typescript now so...

Funny i've tried on a differente machine and it works perfectly fine, i'm trying to figure out why and i'll post the solution here if anyone else encounters this error.

Maybe ts-node package is installed globally on the machine?

well there's that

Here's what I did to fix (don't ask me why)
I ran with npm instead of yarn:
npm install -D typescript npm install -D ts-node npm fun

UPDATE
I guess there really was something wrong with my yarn, so I ran yarn clean cache and created a new project and now it works perfectly.


Heavy traffic on the local docker socket seems to break it

Describe the bug
When I run some test codes that spawn and destroy multiple Docker containers and compose clusters in parallel, at some point, the Docker socket is broken:
$ docker ps
error during connect: Get "http://%2FUsers%2Fjoongi%2F.orbstack%2Frun%2Fdocker.sock/v1.24/containers/json": EOF

I have to restart the OrbStack's docker service to get it working again.
To Reproduce
Steps to reproduce the behavior:

Install pyenv and pyenv install 3.11.3
brew install pantsbuild/tap/pants (see https://www.pantsbuild.org)
git clone https://github.com/lablup/backend.ai bai-dev
cd bai-dev; git switch test/avoid-using-filelocks-for-port-mapping
Run pants test tests/common:: (maybe several times again to reproduce)

When re-executing, you may need to run:

docker ps -a -q|xargs docker rm -f -v
docker network prune

See some failures like: error during connect: Post "http://%2FUsers%2Fjoongi%2F.orbstack%2Frun%2Fdocker.sock/v1.42/containers/49cacc5c790371716a662094b4dbcf6046d6a6efa15d1d075128746bdbba8002/start": EOF

From this point, all other Docker CLI and OrbStack GUI shows the same error until reset.

Expected behavior
The docker engine should keep replying to the CLI commands and the socket.
Screenshots

Logs
console | [37584.373460] eth0: renamed from veth7d5a1f7
console | [37584.571443] IPv6: ADDRCONF(NETDEV_CHANGE): veth59d8854: link becomes ready
console | [37584.571740] br-75a00f6dbe8b: port 4(veth59d8854) entered blocking state
console | [37584.571869] br-75a00f6dbe8b: port 4(veth59d8854) entered forwarding state
console | [37584.645718] eth0: renamed from veth78843f7
console | [37584.703894] eth0: renamed from vethba51b07
console | [37584.746352] eth0: renamed from veth49ff1f4
console | [37584.773639] IPv6: ADDRCONF(NETDEV_CHANGE): veth9f18235: link becomes ready
console | [37584.773894] br-c3669336a326: port 5(veth9f18235) entered blocking state
console | [37584.774053] br-c3669336a326: port 5(veth9f18235) entered forwarding state
console | [37584.774229] IPv6: ADDRCONF(NETDEV_CHANGE): veth3732dd7: link becomes ready
console | [37584.774357] br-75a00f6dbe8b: port 5(veth3732dd7) entered blocking state
console | [37584.774503] br-75a00f6dbe8b: port 5(veth3732dd7) entered forwarding state
console | [37584.774844] IPv6: ADDRCONF(NETDEV_CHANGE): vethb60dcd5: link becomes ready
console | [37584.775094] br-c3669336a326: port 4(vethb60dcd5) entered blocking state
console | [37584.775220] br-c3669336a326: port 4(vethb60dcd5) entered forwarding state
console | ERRO[05-17 12:15:38] failed to handle docker connection            error="write unixgram @: sendmsg: transport endpoint is not connected"
time="05-17 21:15:38" level=error msg="tcp pump2 error 1" error="read tcp <IP_ADDRESS>:48007: connection reset by peer"
time="05-17 21:15:38" level=error msg="tcp pump2 error 1" error="read tcp <IP_ADDRESS>:48006: connection reset by peer"
console | ERRO[05-17 12:15:38] failed to handle docker connection            error="write unixgram @: sendmsg: transport endpoint is not connected"
time="05-17 21:15:38" level=error msg="tcp pump2 error 1" error="read tcp <IP_ADDRESS>:48008: connection reset by peer"
console | ERRO[05-17 12:15:38] failed to handle docker connection            error="write unixgram @: sendmsg: transport endpoint is not connected"

...

console | ERRO[05-17 12:16:48] failed to handle docker connection            error="write unixgram @: sendmsg: transport endpoint is not connected"
time="05-17 21:16:48" level=error msg="tcp pump2 error 1" error="read tcp <IP_ADDRESS>:48437: connection reset by peer"
console | ERRO[05-17 12:16:48] failed to handle docker connection            error="write unixgram @: sendmsg: transport endpoint is not connected"
time="05-17 21:16:48" level=error msg="tcp pump2 error 1" error="read tcp <IP_ADDRESS>:48438: connection reset by peer"
console | ERRO[05-17 12:16:48] failed to handle docker connection            error="write unixgram @: sendmsg: transport endpoint is not connected"
time="05-17 21:16:48" level=error msg="tcp pump2 error 1" error="read tcp <IP_ADDRESS>:48439: connection reset by peer"
console | ERRO[05-17 12:16:48] failed to handle docker connection            error="write unixgram @: sendmsg: transport endpoint is not connected"
time="05-17 21:16:48" level=error msg="tcp pump2 error 1" error="read tcp <IP_ADDRESS>:48440: connection reset by peer"
console | ERRO[05-17 12:16:55] failed to handle docker connection            error="write unixgram @: sendmsg: transport endpoint is not connected"
time="05-17 21:16:55" level=error msg="tcp pump2 error 1" error="read tcp <IP_ADDRESS>:48441: connection reset by peer"
console | ERRO[05-17 12:23:17] failed to handle docker connection            error="write unixgram @: sendmsg: transport endpoint is not connected"
time="05-17 21:23:17" level=error msg="tcp pump2 error 2" error="read tcp <IP_ADDRESS>:48444: connection reset by peer"
time="05-17 21:23:24" level=error msg="tcp pump2 error 1" error="read tcp <IP_ADDRESS>:48445: connection reset by peer"
console | ERRO[05-17 12:23:24] failed to handle docker connection            error="write unixgram @: sendmsg: transport endpoint is not connected"

Info report
OrbStack info:
  Version: 0.10.2 (100200)
  Commit: e502994dbd2170853d7d7d8614018af65ff6d17d (v0.10.2)

System info:
  macOS: 13.3.1 (22E261)
  CPU: arm64, 10 cores
  CPU model: Apple M1 Max

Additional context
Running the same workload inside a multipass VM (Ubuntu 22.04 + native Docker) works fine.

orb logs -a docker output:
Runtime:
ctr<PHONE_NUMBER>0623.809 NOTICE   conf - ../src/ctr/conf.c:ctr_setup:4511 - The container "01GQQVF6C60000000000DOCKER" is set up
ctr<PHONE_NUMBER>0623.810 NOTICE   utils - ../src/ctr/utils.c:ctr_drop_groups:1367 - Dropped supplimentary groups
ctr<PHONE_NUMBER>0623.810 NOTICE   start - ../src/ctr/start.c:start:2194 - Exec'ing "/usr/bin/docker-init"
ctr<PHONE_NUMBER>0623.810 NOTICE   start - ../src/ctr/start.c:post_start:2205 - Started "/usr/bin/docker-init" with pid "911"
ctr<PHONE_NUMBER>0623.811 WARN     attach - ../src/ctr/attach.c:get_attach_context:478 - No security context received
ctr<PHONE_NUMBER>0623.812 NOTICE   utils - ../src/ctr/utils.c:ctr_drop_groups:1367 - Dropped supplimentary groups
ctr<PHONE_NUMBER>0623.812 NOTICE   utils - ../src/ctr/utils.c:ctr_switch_uid_gid:1343 - Switched to gid 0
ctr<PHONE_NUMBER>0623.812 NOTICE   utils - ../src/ctr/utils.c:ctr_switch_uid_gid:1352 - Switched to uid 0

Console:
ERRO[2023-05-17T08:22:30.801265945Z] 18b435be042dead25d87c36a1bd4fa62b8672a9df60593af3f9e57c21283b8b5 cleanup: failed to delete container from containerd: no such container
ERRO[2023-05-17T08:22:30.801328570Z] Handler for POST /v1.42/containers/18b435be042dead25d87c36a1bd4fa62b8672a9df60593af3f9e57c21283b8b5/start returned error: driver failed programming external connectivity on endpoint test-84e8ee2b50a2bcb4_8649a97a956a3bfd-backendai-half-redis-node03-1 (21ea4bf417551ERRO[2023-05-17T08:22:30.963267798Z] 9164c394b0c7cadb6798f3f07a90a353f3e8be493729bdebc2cf
59adc6f6bf74 cleanup: failed to delete container from containerd: no such container
ERRO[2023-05-17T08:22:30.963335256Z] Handler for POST /v1.42/containers/9164c394b0c7cadb6798f3f07a90a353f3e8be493729bdebc2cf59adc6f6bf74/start returned error: driver failed programming external connectivity on endpoint test-84e8ee2b50a2bcb4_8649a97a956a3bfd-backendai-half-redis-node02-1 (a4a8a84cc4bf020da11441c28d2faf11b089bda739d602adde569edc101009b9): Bind for <IP_ADDRESS>:9217 failed: port
is already allocated
WARN[2023-05-17T08:22:31.013620311Z] Failed to allocate and map port 9216-9216: Bind for <IP_ADDRESS>:9216 failed: port is already allocated
ERRO[2023-05-17T08:22:31.173489619Z] Handler for POST /v1.42/containers/36d686bd73a1803eefa849cbcdd512c0fe517f7aa497e9c4cee1dbf315db0f86/unpause returned error: Container 36d686bd73a1803eefa849cbcdd512c0fe517f7aa497e9c4cee1dbf315db0f86 is not paused
ERRO[2023-05-17T08:22:31.194169825Z] c742c82326052b42c94d02584d76d5b1f79aeb1a89f9377591fad2cabdb162ba cleanup: failed to delete container from containerd: no such container
ERRO[2023-05-17T08:22:31.194206784Z] Handler for POST /v1.42/containers/c742c82326052b42c94d02584d76d5b1f79aeb1a89f9377591fad2cabdb162ba/start returned error: driver failed programming external connectivity on endpoint test-84e8ee2b50a2bcb4_8649a97a956a3bfd-backendai-half-redis-node01-1 (3da7d404d5c87d2ea853d3913f7c3243fb6fcb54278cef040dd54ac8a8927207): Bind for <IP_ADDRESS>:9216 failed: port
is already allocated
ERRO[2023-05-17T08:22:32.989341403Z] Handler for POST /v1.42/containers/d1dbe7640b19c6e3f8a25a41c82c329df163e9212e0b1c72cfb7f71a99038a67/unpause returned error: Container d1dbe7640b19c6e3f8a25a41c82c329df163e9212e0b1c72cfb7f71a99038a67 is not paused
WARN[2023-05-17T08:22:34.375825778Z] Failed to allocate and map port 9248-9248: Bind for <IP_ADDRESS>:9248 failed: port is already allocated
WARN[2023-05-17T08:22:34.430680716Z] Failed to allocate and map port 9249-9249: Bind for <IP_ADDRESS>:9249 failed: port is already allocated
ERRO[2023-05-17T08:22:34.493011545Z] 82c469b93738db54fadf0cd7270515779b1619fc66789c74307e1b5319d06884 cleanup: failed to delete container from containerd: no such container
ERRO[2023-05-17T08:22:34.493038920Z] Handler for POST /v1.42/containers/82c469b93738db54fadf0cd7270515779b1619fc66789c74307e1b5319d06884/start returned error: driver failed programming external connectivity on endpoint test-7010375a63bad85e_60b1c3431d0ddd69-backendai-half-redis-node01-1 (71d248eed1ff2f4b5d4099108b895c68d8d41e89cf0d02e7cd33ae03ee6e2a83): Bind for <IP_ADDRESS>:9248 failed: port
is already allocated
ERRO[2023-05-17T08:22:34.585379764Z] 144bd69bcd4e4aa7ffb1c1585b39c6f069a518b9a1902c5eb047300cc052b3d4 cleanup: failed to delete container from containerd: no such container
ERRO[2023-05-17T08:22:34.585421222Z] Handler for POST /v1.42/containers/144bd69bcd4e4aa7ffb1c1585b39c6f069a518b9a1902c5eb047300cc052b3d4/start returned error: driver failed programming external connectivity on endpoint test-7010375a63bad85e_60b1c3431d0ddd69-backendai-half-redis-node02-1 (2cd3ed773cac12b29b15f48227e7b80cca4b64f54bc4c1717c8ef813327514b4): Bind for <IP_ADDRESS>:9249 failed: port
is already allocated
WARN[2023-05-17T08:22:34.634980526Z] Failed to allocate and map port 9250-9250: Bind for <IP_ADDRESS>:9250 failed: port is already allocated
ERRO[2023-05-17T08:22:34.773205125Z] 6a71f883077281362c98607e149c635aefebc8b2f599572e9f0c5f472b6c9c66 cleanup: failed to delete container from containerd: no such container
ERRO[2023-05-17T08:22:34.773235584Z] Handler for POST /v1.42/containers/6a71f883077281362c98607e149c635aefebc8b2f599572e9f0c5f472b6c9c66/start returned error: driver failed programming external connectivity on endpoint test-7010375a63bad85e_60b1c3431d0ddd69-backendai-half-redis-node03-1 (13440d1ecdb55813ab5306e8c2a43c7f607f7761fcd1000afe80c8277623d364): Bind for <IP_ADDRESS>:9250 failed: port
is already allocated
WARN[2023-05-17T08:22:35.014941798Z] Failed to allocate and map port 9248-9248: Bind for <IP_ADDRESS>:9248 failed: port is already allocated
WARN[2023-05-17T08:22:35.069710904Z] Failed to allocate and map port 9249-9249: Bind for <IP_ADDRESS>:9249 failed: port is already allocated
ERRO[2023-05-17T08:22:35.122589380Z] 1ee387239762db285b3a22667cd1277d39c56ee786e597c876fb0c23111dd65b cleanup: failed to delete container from containerd: no such container
ERRO[2023-05-17T08:22:35.122617714Z] Handler for POST /v1.42/containers/1ee387239762db285b3a22667cd1277d39c56ee786e597c876fb0c23111dd65b/start returned error: driver failed programming external connectivity on endpoint test-7010375a63bad85e_7483b22b40cd7583-backendai-half-redis-node01-1 (3c8b7a119c0b64c2fe3ce899c9b51a245313ce3e9879fe0a039f3f5350e93392): Bind for <IP_ADDRESS>:9248 failed: port
is already allocated
ERRO[2023-05-17T08:22:35.256780180Z] e1d18af19079b2731850fe8764576c99440b89a69dd5304e45b0120f828e2933 cleanup: failed to delete container from containerd: no such container
ERRO[2023-05-17T08:22:35.256828722Z] Handler for POST /v1.42/containers/e1d18af19079b2731850fe8764576c99440b89a69dd5304e45b0120f828e2933/start returned error: driver failed programming external connectivity on endpoint test-7010375a63bad85e_7483b22b40cd7583-backendai-half-redis-node02-1 (fc345d439c0c61513b464329d37362d33166eb5c477d53420bf4826fe958b8ea): Bind for <IP_ADDRESS>:9249 failed: port
is already allocated
WARN[2023-05-17T08:22:35.307109444Z] Failed to allocate and map port 9250-9250: Bind for <IP_ADDRESS>:9250 failed: port is already allocated
ERRO[2023-05-17T08:22:35.392285482Z] 26c3ecaf77799e0e80ddf66712f5e58c21cb784b2958d9ba922532e3e1f6d15d cleanup: failed to delete container from containerd: no such container
ERRO[2023-05-17T08:22:35.392372316Z] Handler for POST /v1.42/containers/26c3ecaf77799e0e80ddf66712f5e58c21cb784b2958d9ba922532e3e1f6d15d/start returned error: driver failed programming external connectivity on endpoint test-7010375a63bad85e_7483b22b40cd7583-backendai-half-redis-node03-1 (51f7c65eec5277e9d504d49abfbc644d349ef45c4ea02f4eb442d2a4141ea62c): Bind for <IP_ADDRESS>:9250 failed: port
is already allocated
time="2023-05-17T08:22:54.335253122Z" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
time="2023-05-17T08:22:54.335470706Z" level=info msg="loading plugin \"io.containerd.ttrpc.v1.pause\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
...
(repeats normal logs)

Maybe related to #243.

Please share both logs in full without removing any lines. It looks like only the connection is breaking here, which is different from #243 (where the Docker engine seems to be crashing). Can't tell for sure without full logs.

I'll attach the full logs once I reproduce the issue.

Will dig into this more and see if I can reproduce it, but so far heavy concurrency tests with 1000 connections aren't causing issues like this.

The reproducer is failing for me (not because of this issue):
00:57:43.35 [INFO] Completed: Run Pytest - tests/common/redis/test_stream_consume.py:tests - succeeded.
00:57:43.80 [INFO] Completed: Run Pytest - tests/common/redis/test_stream_subscribe.py:tests - succeeded.
00:57:53.95 [ERROR] Completed: Run Pytest - tests/common/redis/test_connect.py:tests - failed (exit code 1).
============================= test session starts ==============================
platform darwin -- Python 3.11.3, pytest-7.3.1, pluggy-1.0.0 -- /Users/dragon/.cache/pants/named_caches/pex_root/venvs/s/44747fc2/venv/bin/python3.11
cachedir: .pytest_cache
rootdir: /Users/dragon/code/docker/bai-dev/.tmp/pants-sandbox-gZODHR
configfile: pyproject.toml
plugins: asyncio-0.21.0, custom-exit-code-0.3.0, mock-3.10.0, cov-4.1.0, dependency-0.5.1, typeguard-2.13.3, aiohttp-1.0.4
asyncio: mode=Mode.AUTO
collecting ... collected 3 items

tests/common/redis/test_connect.py::test_connect PASSED                  [ 33%]
tests/common/redis/test_connect.py::test_instantiate_redisconninfo PASSED [ 66%]
tests/common/redis/test_connect.py::test_connect_cluster_sentinel FAILED [100%]

=================================== FAILURES ===================================
________________________ test_connect_cluster_sentinel _________________________
  + Exception Group Traceback (most recent call last):
  |   File "/Users/dragon/code/docker/bai-dev/.tmp/pants-sandbox-gZODHR/tests/common/redis/test_connect.py", line 90, in test_connect_cluster_sentinel
  |     async with aiotools.TaskGroup() as tg:
  |   File "/Users/dragon/.cache/pants/named_caches/pex_root/venvs/s/44747fc2/venv/lib/python3.11/site-packages/aiotools/taskgroup/base.py", line 40, in __aexit__
  |     raise TaskGroupError(eg.message, eg.exceptions) from None
  | aiotools.taskgroup.types.TaskGroupError: unhandled errors in a TaskGroup (1 sub-exception)
  +-+---------------- 1 ----------------
    | Traceback (most recent call last):
    |   File "/Users/dragon/.cache/pants/named_caches/pex_root/venvs/s/44747fc2/venv/lib/python3.11/site-packages/redis/asyncio/connection.py", line 645, in _connect
    |     reader, writer = await asyncio.open_connection(
    |                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/Users/dragon/.pyenv/versions/3.11.3/lib/python3.11/asyncio/streams.py", line 48, in open_connection
    |     transport, _ = await loop.create_connection(
    |                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/Users/dragon/.pyenv/versions/3.11.3/lib/python3.11/asyncio/base_events.py", line 1045, in create_connection
    |     infos = await self._ensure_resolved(
    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/Users/dragon/.pyenv/versions/3.11.3/lib/python3.11/asyncio/base_events.py", line 1419, in _ensure_resolved
    |     return await loop.getaddrinfo(host, port, family=family, type=type,
    |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/Users/dragon/.pyenv/versions/3.11.3/lib/python3.11/asyncio/base_events.py", line 867, in getaddrinfo
    |     return await self.run_in_executor(
    |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^
    | asyncio.exceptions.CancelledError
    |
    | The above exception was the direct cause of the following exception:
    |
    | Traceback (most recent call last):
    |   File "/Users/dragon/.cache/pants/named_caches/pex_root/venvs/s/44747fc2/venv/lib/python3.11/site-packages/redis/asyncio/connection.py", line 608, in connect
    |     await self.retry.call_with_retry(
    |   File "/Users/dragon/.cache/pants/named_caches/pex_root/venvs/s/44747fc2/venv/lib/python3.11/site-packages/redis/asyncio/retry.py", line 59, in call_with_retry
    |     return await do()
    |            ^^^^^^^^^^
    |   File "/Users/dragon/.cache/pants/named_caches/pex_root/venvs/s/44747fc2/venv/lib/python3.11/site-packages/redis/asyncio/connection.py", line 644, in _connect
    |     async with async_timeout(self.socket_connect_timeout):
    |   File "/Users/dragon/.pyenv/versions/3.11.3/lib/python3.11/asyncio/timeouts.py", line 111, in __aexit__
    |     raise TimeoutError from exc_val
    | TimeoutError
    |
    | During handling of the above exception, another exception occurred:
    |
    | Traceback (most recent call last):
    |   File "/Users/dragon/code/docker/bai-dev/.tmp/pants-sandbox-gZODHR/tests/common/redis/test_connect.py", line 116, in test_connect_cluster_sentinel
    |     await slave.ping()
    |   File "/Users/dragon/.cache/pants/named_caches/pex_root/venvs/s/44747fc2/venv/lib/python3.11/site-packages/redis/asyncio/client.py", line 513, in execute_command
    |     conn = self.connection or await pool.get_connection(command_name, **options)
    |                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/Users/dragon/.cache/pants/named_caches/pex_root/venvs/s/44747fc2/venv/lib/python3.11/site-packages/redis/asyncio/connection.py", line 1413, in get_connection
    |     await connection.connect()
    |   File "/Users/dragon/.cache/pants/named_caches/pex_root/venvs/s/44747fc2/venv/lib/python3.11/site-packages/redis/asyncio/sentinel.py", line 61, in connect
    |     return await self.retry.call_with_retry(
    |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/Users/dragon/.cache/pants/named_caches/pex_root/venvs/s/44747fc2/venv/lib/python3.11/site-packages/redis/asyncio/retry.py", line 64, in call_with_retry
    |     raise error
    |   File "/Users/dragon/.cache/pants/named_caches/pex_root/venvs/s/44747fc2/venv/lib/python3.11/site-packages/redis/asyncio/retry.py", line 59, in call_with_retry
    |     return await do()
    |            ^^^^^^^^^^
    |   File "/Users/dragon/.cache/pants/named_caches/pex_root/venvs/s/44747fc2/venv/lib/python3.11/site-packages/redis/asyncio/sentinel.py", line 55, in _connect_retry
    |     return await self.connect_to(slave)
    |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |   File "/Users/dragon/.cache/pants/named_caches/pex_root/venvs/s/44747fc2/venv/lib/python3.11/site-packages/redis/asyncio/sentinel.py", line 41, in connect_to
    |     await super().connect()
    |   File "/Users/dragon/.cache/pants/named_caches/pex_root/venvs/s/44747fc2/venv/lib/python3.11/site-packages/redis/asyncio/connection.py", line 614, in connect
    |     raise TimeoutError("Timeout connecting to server")
    | redis.exceptions.TimeoutError: Timeout connecting to server
    +------------------------------------
---------------------------- Captured stdout setup -----------------------------
("ps_output=[{'ID': "
 "'a1a5a7db9d47ab4a2932f6985dc8a286c8a46bce836bdd9f7a6b86b92ddb7b00', 'Name': "
 "'test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-node01-1', "
 "'Image': 'redis:7-alpine', 'Command': 'docker-entrypoint.sh redis-server "
 '--port 9208 --requirepass develove --masterauth develove '
 '--replica-announce-ip node01 --min-slaves-to-write 1 --min-slaves-max-lag '
 "10', 'Project': 'test-f92ea8a18415449d_ad54bd17367a8c4f', 'Service': "
 "'backendai-half-redis-node01', 'Created':<PHONE_NUMBER>, 'State': 'running', "
 "'Status': 'Up 2 seconds', 'Health': '', 'ExitCode': 0, 'Publishers': "
 "[{'URL': '', 'TargetPort': 6379, 'PublishedPort': 0, 'Protocol': 'tcp'}, "
 "{'URL': '<IP_ADDRESS>', 'TargetPort': 9208, 'PublishedPort': 9208, 'Protocol': "
 "'tcp'}]}, {'ID': "
 "'e9ddc93ca7f567915e28a5b48e9adeaccb6f06723a9a43dd777feac93c5aee75', 'Name': "
 "'test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-node02-1', "
 "'Image': 'redis:7-alpine', 'Command': 'docker-entrypoint.sh redis-server "
 '--port 9209 --requirepass develove --masterauth develove --slaveof node01 '
 '9208 --replica-announce-ip node02 --min-slaves-to-write 1 '
 "--min-slaves-max-lag 10', 'Project': "
 "'test-f92ea8a18415449d_ad54bd17367a8c4f', 'Service': "
 "'backendai-half-redis-node02', 'Created':<PHONE_NUMBER>, 'State': 'running', "
 "'Status': 'Up 2 seconds', 'Health': '', 'ExitCode': 0, 'Publishers': "
 "[{'URL': '', 'TargetPort': 6379, 'PublishedPort': 0, 'Protocol': 'tcp'}, "
 "{'URL': '<IP_ADDRESS>', 'TargetPort': 9209, 'PublishedPort': 9209, 'Protocol': "
 "'tcp'}]}, {'ID': "
 "'b6815f4db3383e933dfa8e038a93fa78153bc587f051af1a406e13aa1ab78f5b', 'Name': "
 "'test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-node03-1', "
 "'Image': 'redis:7-alpine', 'Command': 'docker-entrypoint.sh redis-server "
 '--port 9210 --requirepass develove --masterauth develove --slaveof node01 '
 '9208 --replica-announce-ip node03 --min-slaves-to-write 1 '
 "--min-slaves-max-lag 10', 'Project': "
 "'test-f92ea8a18415449d_ad54bd17367a8c4f', 'Service': "
 "'backendai-half-redis-node03', 'Created':<PHONE_NUMBER>, 'State': 'running', "
 "'Status': 'Up 1 second', 'Health': '', 'ExitCode': 0, 'Publishers': [{'URL': "
 "'', 'TargetPort': 6379, 'PublishedPort': 0, 'Protocol': 'tcp'}, {'URL': "
 "'<IP_ADDRESS>', 'TargetPort': 9210, 'PublishedPort': 9210, 'Protocol': 'tcp'}]}, "
 "{'ID': '47611ce21b847e20ceee0e3a4af3b6bab10dd6cccc9702c6e778a953177b6094', "
 "'Name': "
 "'test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-sentinel01-1', "
 "'Image': 'redis:7-alpine', 'Command': 'docker-entrypoint.sh redis-server "
 "/config/sentinel01.conf --sentinel --port 9211', 'Project': "
 "'test-f92ea8a18415449d_ad54bd17367a8c4f', 'Service': "
 "'backendai-half-redis-sentinel01', 'Created':<PHONE_NUMBER>, 'State': "
 "'running', 'Status': 'Up 1 second', 'Health': '', 'ExitCode': 0, "
 "'Publishers': [{'URL': '', 'TargetPort': 6379, 'PublishedPort': 0, "
 "'Protocol': 'tcp'}, {'URL': '<IP_ADDRESS>', 'TargetPort': 9211, 'PublishedPort': "
 "9211, 'Protocol': 'tcp'}]}, {'ID': "
 "'33359fafca587923cc204367bf3b1043c3b8fa9b89d4c87bde4c3e4255612e28', 'Name': "
 "'test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-sentinel02-1', "
 "'Image': 'redis:7-alpine', 'Command': 'docker-entrypoint.sh redis-server "
 "/config/sentinel02.conf --sentinel --port 9212', 'Project': "
 "'test-f92ea8a18415449d_ad54bd17367a8c4f', 'Service': "
 "'backendai-half-redis-sentinel02', 'Created':<PHONE_NUMBER>, 'State': "
 "'running', 'Status': 'Up 1 second', 'Health': '', 'ExitCode': 0, "
 "'Publishers': [{'URL': '', 'TargetPort': 6379, 'PublishedPort': 0, "
 "'Protocol': 'tcp'}, {'URL': '<IP_ADDRESS>', 'TargetPort': 9212, 'PublishedPort': "
 "9212, 'Protocol': 'tcp'}]}, {'ID': "
 "'ce90565b3ba097850f90bd437bc3efcc39015589567ec7b3b349ad2d326fab02', 'Name': "
 "'test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-sentinel03-1', "
 "'Image': 'redis:7-alpine', 'Command': 'docker-entrypoint.sh redis-server "
 "/config/sentinel03.conf --sentinel --port 9213', 'Project': "
 "'test-f92ea8a18415449d_ad54bd17367a8c4f', 'Service': "
 "'backendai-half-redis-sentinel03', 'Created':<PHONE_NUMBER>, 'State': "
 "'running', 'Status': 'Up 1 second', 'Health': '', 'ExitCode': 0, "
 "'Publishers': [{'URL': '', 'TargetPort': 6379, 'PublishedPort': 0, "
 "'Protocol': 'tcp'}, {'URL': '<IP_ADDRESS>', 'TargetPort': 9213, 'PublishedPort': "
 "9213, 'Protocol': 'tcp'}]}]")
--- logs of a1a5a7db9d47ab4a2932f6985dc8a286c8a46bce836bdd9f7a6b86b92ddb7b00 ---
1:C 28 May 2023 07:57:37.024 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 28 May 2023 07:57:37.024 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 28 May 2023 07:57:37.024 # Configuration loaded
1:M 28 May 2023 07:57:37.024 * monotonic clock: POSIX clock_gettime
1:M 28 May 2023 07:57:37.028 * Running mode=standalone, port=9208.
1:M 28 May 2023 07:57:37.028 # Server initialized
1:M 28 May 2023 07:57:37.029 * Ready to accept connections
1:M 28 May 2023 07:57:37.329 * Replica node03:9210 asks for synchronization
1:M 28 May 2023 07:57:37.329 * Full resync requested by replica node03:9210
1:M 28 May 2023 07:57:37.329 * Replication backlog created, my new replication IDs are '0adea842efb77f1ffff6d9aebc0591a2982f545d' and '0000000000000000000000000000000000000000'
1:M 28 May 2023 07:57:37.329 * Delay next BGSAVE for diskless SYNC
1:M 28 May 2023 07:57:37.611 * Replica node02:9209 asks for synchronization
1:M 28 May 2023 07:57:37.611 * Full resync requested by replica node02:9209
1:M 28 May 2023 07:57:37.611 * Delay next BGSAVE for diskless SYNC
--- end of logs ---
--- logs of e9ddc93ca7f567915e28a5b48e9adeaccb6f06723a9a43dd777feac93c5aee75 ---
1:C 28 May 2023 07:57:36.591 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 28 May 2023 07:57:36.591 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 28 May 2023 07:57:36.591 # Configuration loaded
1:S 28 May 2023 07:57:36.591 * monotonic clock: POSIX clock_gettime
1:S 28 May 2023 07:57:36.592 * Running mode=standalone, port=9209.
1:S 28 May 2023 07:57:36.592 # Server initialized
1:S 28 May 2023 07:57:36.592 * Ready to accept connections
1:S 28 May 2023 07:57:36.592 * Connecting to MASTER node01:9208
1:S 28 May 2023 07:57:36.593 * MASTER <-> REPLICA sync started
1:S 28 May 2023 07:57:37.611 * Non blocking connect for SYNC fired the event.
1:S 28 May 2023 07:57:37.611 * Master replied to PING, replication can continue...
1:S 28 May 2023 07:57:37.611 * Partial resynchronization not possible (no cached master)
--- end of logs ---
--- logs of b6815f4db3383e933dfa8e038a93fa78153bc587f051af1a406e13aa1ab78f5b ---
1:C 28 May 2023 07:57:37.326 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 28 May 2023 07:57:37.326 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 28 May 2023 07:57:37.326 # Configuration loaded
1:S 28 May 2023 07:57:37.326 * monotonic clock: POSIX clock_gettime
1:S 28 May 2023 07:57:37.327 * Running mode=standalone, port=9210.
1:S 28 May 2023 07:57:37.327 # Server initialized
1:S 28 May 2023 07:57:37.328 * Ready to accept connections
1:S 28 May 2023 07:57:37.328 * Connecting to MASTER node01:9208
1:S 28 May 2023 07:57:37.329 * MASTER <-> REPLICA sync started
1:S 28 May 2023 07:57:37.329 * Non blocking connect for SYNC fired the event.
1:S 28 May 2023 07:57:37.329 * Master replied to PING, replication can continue...
1:S 28 May 2023 07:57:37.329 * Partial resynchronization not possible (no cached master)
--- end of logs ---
--- logs of 47611ce21b847e20ceee0e3a4af3b6bab10dd6cccc9702c6e778a953177b6094 ---
1:X 28 May 2023 07:57:38.068 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:X 28 May 2023 07:57:38.068 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started
1:X 28 May 2023 07:57:38.068 # Configuration loaded
1:X 28 May 2023 07:57:38.068 * monotonic clock: POSIX clock_gettime
1:X 28 May 2023 07:57:38.069 * Running mode=sentinel, port=9211.
1:X 28 May 2023 07:57:38.074 * Sentinel new configuration saved on disk
1:X 28 May 2023 07:57:38.074 # Sentinel ID is 3aa2d84b256c5047a9e844b67b2316a94e5d2590
1:X 28 May 2023 07:57:38.074 # +monitor master mymaster node01 9208 quorum 2
1:X 28 May 2023 07:57:38.077 * +slave slave node03:9210 node03 9210 @ mymaster node01 9208
1:X 28 May 2023 07:57:38.085 * Sentinel new configuration saved on disk
1:X 28 May 2023 07:57:38.087 * +slave slave node02:9209 node02 9209 @ mymaster node01 9208
1:X 28 May 2023 07:57:38.093 * Sentinel new configuration saved on disk
--- end of logs ---
--- logs of 33359fafca587923cc204367bf3b1043c3b8fa9b89d4c87bde4c3e4255612e28 ---
1:X 28 May 2023 07:57:38.068 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:X 28 May 2023 07:57:38.068 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started
1:X 28 May 2023 07:57:38.068 # Configuration loaded
1:X 28 May 2023 07:57:38.069 * monotonic clock: POSIX clock_gettime
1:X 28 May 2023 07:57:38.070 * Running mode=sentinel, port=9212.
1:X 28 May 2023 07:57:38.076 * Sentinel new configuration saved on disk
1:X 28 May 2023 07:57:38.076 # Sentinel ID is d88a3d0f0a1824e70eac5e076990c16b232c6ae9
1:X 28 May 2023 07:57:38.076 # +monitor master mymaster node01 9208 quorum 2
1:X 28 May 2023 07:57:38.078 * +slave slave node03:9210 node03 9210 @ mymaster node01 9208
1:X 28 May 2023 07:57:38.086 * Sentinel new configuration saved on disk
1:X 28 May 2023 07:57:38.087 * +slave slave node02:9209 node02 9209 @ mymaster node01 9208
1:X 28 May 2023 07:57:38.093 * Sentinel new configuration saved on disk
--- end of logs ---
--- logs of ce90565b3ba097850f90bd437bc3efcc39015589567ec7b3b349ad2d326fab02 ---
1:X 28 May 2023 07:57:38.075 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:X 28 May 2023 07:57:38.075 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started
1:X 28 May 2023 07:57:38.075 # Configuration loaded
1:X 28 May 2023 07:57:38.075 * monotonic clock: POSIX clock_gettime
1:X 28 May 2023 07:57:38.076 * Running mode=sentinel, port=9213.
1:X 28 May 2023 07:57:38.085 * Sentinel new configuration saved on disk
1:X 28 May 2023 07:57:38.085 # Sentinel ID is 312a406a781bb245466691996856f19fe3ad0a66
1:X 28 May 2023 07:57:38.085 # +monitor master mymaster node01 9208 quorum 2
1:X 28 May 2023 07:57:38.088 * +slave slave node03:9210 node03 9210 @ mymaster node01 9208
1:X 28 May 2023 07:57:38.093 * Sentinel new configuration saved on disk
1:X 28 May 2023 07:57:38.094 * +slave slave node02:9209 node02 9209 @ mymaster node01 9208
1:X 28 May 2023 07:57:38.095 * Sentinel new configuration saved on disk
--- end of logs ---
cids=['a1a5a7db9d47ab4a2932f6985dc8a286c8a46bce836bdd9f7a6b86b92ddb7b00', 'e9ddc93ca7f567915e28a5b48e9adeaccb6f06723a9a43dd777feac93c5aee75', 'b6815f4db3383e933dfa8e038a93fa78153bc587f051af1a406e13aa1ab78f5b', '47611ce21b847e20ceee0e3a4af3b6bab10dd6cccc9702c6e778a953177b6094', '33359fafca587923cc204367bf3b1043c3b8fa9b89d4c87bde4c3e4255612e28', 'ce90565b3ba097850f90bd437bc3efcc39015589567ec7b3b349ad2d326fab02']
cid_mapping={'backendai-half-redis-node01': 'a1a5a7db9d47ab4a2932f6985dc8a286c8a46bce836bdd9f7a6b86b92ddb7b00', 'backendai-half-redis-node02': 'e9ddc93ca7f567915e28a5b48e9adeaccb6f06723a9a43dd777feac93c5aee75', 'backendai-half-redis-node03': 'b6815f4db3383e933dfa8e038a93fa78153bc587f051af1a406e13aa1ab78f5b', 'backendai-half-redis-sentinel01': '47611ce21b847e20ceee0e3a4af3b6bab10dd6cccc9702c6e778a953177b6094', 'backendai-half-redis-sentinel02': '33359fafca587923cc204367bf3b1043c3b8fa9b89d4c87bde4c3e4255612e28', 'backendai-half-redis-sentinel03': 'ce90565b3ba097850f90bd437bc3efcc39015589567ec7b3b349ad2d326fab02'}
---------------------------- Captured stderr setup -----------------------------
 Network test-f92ea8a18415449d_ad54bd17367a8c4f_testnet  Creating
 Network test-f92ea8a18415449d_ad54bd17367a8c4f_testnet  Created
 Container test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-node01-1  Creating
 Container test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-node02-1  Creating
 Container test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-node03-1  Creating
 Container test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-node03-1  Created
 Container test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-node01-1  Created
 Container test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-node02-1  Created
 Container test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-sentinel01-1  Creating
 Container test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-sentinel02-1  Creating
 Container test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-sentinel03-1  Creating
 Container test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-sentinel02-1  Created
 Container test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-sentinel03-1  Created
 Container test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-sentinel01-1  Created
 Container test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-node01-1  Starting
 Container test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-node02-1  Starting
 Container test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-node03-1  Starting
 Container test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-node02-1  Started
 Container test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-node01-1  Started
 Container test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-node03-1  Started
 Container test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-sentinel03-1  Starting
 Container test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-sentinel02-1  Starting
 Container test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-sentinel01-1  Starting
 Container test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-sentinel01-1  Started
 Container test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-sentinel02-1  Started
 Container test-f92ea8a18415449d_ad54bd17367a8c4f-backendai-half-redis-sentinel03-1  Started
CheckReady.PING... 9208
CheckReady.PING... 9209
CheckReady.PING... 9210
CheckReady.PING... 9211
CheckReady.PING... 9212
CheckReady.PING... 9213
CheckReady.PONG 9211
CheckReady.PONG 9212
CheckReady.PONG 9213
CheckReady.PONG 9210
CheckReady.PONG 9208
CheckReady.PONG 9209
----------------------------- Captured stdout call -----------------------------
CONNECT REPEAT 0
MASTER ('node01', 9208)
SLAVE [('node02', 9209), ('node03', 9210)]
- generated xml file: /Users/dragon/code/docker/bai-dev/.tmp/pants-sandbox-gZODHR/tests.common.redis.test_connect.py.tests.xml -
=========================== short test summary info ============================
FAILED tests/common/redis/test_connect.py::test_connect_cluster_sentinel - aiotools.taskgroup.types.TaskGroupError: unhandled errors in a TaskGroup (1...
========================= 1 failed, 2 passed in 20.83s =========================

00:58:27.30 [INFO] Completed: Run Pytest - tests/common/redis/test_stream_consume_cluster.py:tests - succeeded.
00:58:27.45 [INFO] Completed: Run Pytest - tests/common/redis/test_stream_subscribe_cluster.py:tests - succeeded.

✓ tests/common/redis/test_list.py:tests succeeded in 6.76s (memoized).
✓ tests/common/redis/test_list_cluster.py:tests succeeded in 5.50s (memoized).
✓ tests/common/redis/test_pipeline.py:tests succeeded in 24.72s (memoized).
✓ tests/common/redis/test_pubsub.py:tests succeeded in 7.00s (memoized).
✓ tests/common/redis/test_stream_consume.py:tests succeeded in 10.93s.
✓ tests/common/redis/test_stream_consume_cluster.py:tests succeeded in 54.87s.
✓ tests/common/redis/test_stream_subscribe.py:tests succeeded in 11.37s.
✓ tests/common/redis/test_stream_subscribe_cluster.py:tests succeeded in 55.02s.
✓ tests/common/test_argparse.py:tests succeeded in 0.74s (memoized).
✓ tests/common/test_config.py:tests succeeded in 2.97s (memoized).
✓ tests/common/test_distributed.py:tests succeeded in 19.00s (memoized).
✓ tests/common/test_docker.py:tests succeeded in 4.36s (memoized).
✓ tests/common/test_etcd.py:tests succeeded in 5.95s (memoized).
✓ tests/common/test_events.py:tests succeeded in 7.54s (memoized).
✓ tests/common/test_identity.py:tests succeeded in 3.86s (memoized).
✓ tests/common/test_json.py:tests succeeded in 0.65s (memoized).
✓ tests/common/test_logging.py:tests succeeded in 2.54s (memoized).
✓ tests/common/test_msgpack.py:tests succeeded in 2.94s (memoized).
✓ tests/common/test_plugin.py:tests succeeded in 12.33s (memoized).
✓ tests/common/test_service_ports.py:tests succeeded in 2.82s (memoized).
✓ tests/common/test_types.py:tests succeeded in 2.70s (memoized).
✓ tests/common/test_utils.py:tests succeeded in 1.72s (memoized).
✓ tests/common/test_validators.py:tests succeeded in 0.65s (memoized).
✕ tests/common/redis/test_connect.py:tests failed in 21.52s.

The branch no longer exists so I used the following commit:
commit 6a855930b93b0c934b4bfad4a07ee36fe9dbf89b (grafted, HEAD -> main, origin/main, origin/HEAD)
Author: Joongi Kim<EMAIL_ADDRESS>Date:   Fri May 26 23:35:36 2023 +0900

    ci: Upgrade mypy to 1.3.0 (#1310)

Also added this to /etc/hosts:'
<IP_ADDRESS> node01
<IP_ADDRESS> node02
<IP_ADDRESS> node03

Any idea what might be wrong?

@achimnol Is this still an issue? Happy to look into it if I can reproduce it.

@achimnol Is this still an issue? Happy to look into it if I can reproduce it.

After then, it did not reproduce until yet. I'm happy to close the issue for now, and if I encounter this again with more complete logs, I'll reopen.


Avoid installing README into $PREFIX

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge/mysql-connector-c Ready for review
I had issues due to the existence of $CONDA_PREFIX/README which triggered me to notice that these files from the "standalone" build are being installed when they shouldn't be (the CMake config avoids them for RPM and DEB builds).

@chrisburr thanks, you are also more than welcome to add yourself to the maintainer list.

Thanks @druvus! I've added myself to the maintainers


--action visualize seems to ignore the language

I've run
java -jar Mustang-CLI-2.8.0.jar --action visualize

both with --language de and --language en, with this sample as input file.
Both runs produced identical results, which seems fishy to me. If the language setting doesn't affect the outcome, why require it all?

hi, I believe you are using a ZUGFeRD version 1 input, try with a version 2, like https://www.mustangproject.org/files/factur-x.xml .
C:\Users\jstaerk\workspace\mustangproject\Mustang-CLI\target>java -jar Mustang-CLI-2.9.0.jar --action visualize --source \Users\jstaerk\Downloads\factur-x.xml --language de
ZUGFeRD XML source set to \Users\jstaerk\Downloads\factur-x.xml
Output language set to de
Target file (default: factur-x.html):
Warning at char 27 in xsl:value-of/@select on line 1985 column 166
  SXWN9000: Comparison of xs:untypedAtomic? to xs:boolean will fail unless the first operand is empty
Warning at xsl:for-each on line 2083 column 78
  SXWN9009: An empty xsl:for-each instruction has no effect
Warning at char 6 in xsl:value-of/@select on line 1010 column 126
  SXWN9000: Comparison of xs:untypedAtomic? to xs:boolean will fail unless the first operand is empty
Warning at char 6 in xsl:value-of/@select on line 1927 column 119
  SXWN9000: Comparison of xs:untypedAtomic? to xs:boolean will fail unless the first operand is empty
Warning at char 27 in xsl:value-of/@select on line 1985 column 166
  SXWN9000: Comparison of xs:untypedAtomic? to xs:boolean will fail unless the first operand is empty
Warning at char 6 in xsl:value-of/@select on line 1010 column 126
  SXWN9000: Comparison of xs:untypedAtomic? to xs:boolean will fail unless the first operand is empty
Warning at char 6 in xsl:value-of/@select on line 1927 column 119
  SXWN9000: Comparison of xs:untypedAtomic? to xs:boolean will fail unless the first operand is empty
Warning at char 27 in xsl:value-of/@select on line 1985 column 166
  SXWN9000: Comparison of xs:untypedAtomic? to xs:boolean will fail unless the first operand is empty
Written to factur-x.html
xrechnung-viewer.css and xrechnung-viewer.js written as well (to local working dir)

respectively

C:\Users\jstaerk\workspace\mustangproject\Mustang-CLI\target>java -jar Mustang-CLI-2.9.0.jar --action visualize --source \Users\jstaerk\Downloads\factur-x.xml --language en
ZUGFeRD XML source set to \Users\jstaerk\Downloads\factur-x.xml
Output language set to en
Target file (default: factur-x.html):factur-x.en.html
Warning at char 27 in xsl:value-of/@select on line 1985 column 166
  SXWN9000: Comparison of xs:untypedAtomic? to xs:boolean will fail unless the first operand is empty
Warning at xsl:for-each on line 2083 column 78
  SXWN9009: An empty xsl:for-each instruction has no effect
Warning at char 6 in xsl:value-of/@select on line 1010 column 126
  SXWN9000: Comparison of xs:untypedAtomic? to xs:boolean will fail unless the first operand is empty
Warning at char 6 in xsl:value-of/@select on line 1927 column 119
  SXWN9000: Comparison of xs:untypedAtomic? to xs:boolean will fail unless the first operand is empty
Warning at char 27 in xsl:value-of/@select on line 1985 column 166
  SXWN9000: Comparison of xs:untypedAtomic? to xs:boolean will fail unless the first operand is empty
Warning at char 6 in xsl:value-of/@select on line 1010 column 126
  SXWN9000: Comparison of xs:untypedAtomic? to xs:boolean will fail unless the first operand is empty
Warning at char 6 in xsl:value-of/@select on line 1927 column 119
  SXWN9000: Comparison of xs:untypedAtomic? to xs:boolean will fail unless the first operand is empty
Warning at char 27 in xsl:value-of/@select on line 1985 column 166
  SXWN9000: Comparison of xs:untypedAtomic? to xs:boolean will fail unless the first operand is empty
Written to factur-x.en.html
xrechnung-viewer.css and xrechnung-viewer.js written as well (to local working dir)

produces the attached files (sorry for the special character mishap, I'm on windows and I didn't specify the utf8 charset on commandline)
factur-x.zip
please feel free to either close the issue or change the subject to zugferd v1 visualisation should be translatable, unfortunately the official xslt is currently single language only so one would need translators :-(

Hi @jstaerk,
thank you for the quick response.
You are right, it works with zugferd 2 / factur-x files, and that it doesn't really work with version 1 isn't really an issue for me, so I'm closing this.


Random button area to click

Hello, its possible to randomize the cordinates inside the element? If the clicks goes always on certer its easy to detect

You can use offsets for reach it:
import random
from emunium import EmuniumSelenium

driver = webdriver.Chrome()
wait = WebDriverWait(driver, 10)
emunium = EmuniumSelenium(driver)

driver.get('https://duckduckgo.com/')

element = wait.until(EC.element_to_be_clickable((By.CSS_SELECTOR, '[data-state="suggesting"]')))

# coordinate randomization with respect to the center
emunium.find_and_move(element, click=True, offset_x=random.uniform(0.0, 1.5), offset_y=random.uniform(0.0, 1.5))

Okay, can we use the area of the button instead of center?


setup Sphinx

I set up Sphinx and added a simple quickstart.

I guess the remaining errors can be cleaned up once we have CI.


Example data for ccmpp

#35

I decided to add in the ccmpp/leslie functions to the PR since they are so tightly related to the example data and matrix/dt helper functions. Sorry for that change

It is really annoying that checks pass fine locally but not with github actions. Long term solution  is probably docker but does anyone have suggestions for debugging this? I assume its package version differences

It is really annoying that checks pass fine locally but not with github actions. Long term solution is probably docker but does anyone have suggestions for debugging this? I assume its package version differences

Fixed these by updating to R 4.0 which github actions was using and installing the latest versions of all package dependencies remotes::install_deps(dependencies = TRUE) like is done in github actions


Drag between groups?

I tried looking thru the docs, but it seems dragging elements is limit to its container, if I have several containers is it possible to drag elements between them.
My use case is this
Level A - Categories List
     Level B - Category - Contains draggable items
             Level C - Individual Draggable Item
             ...
      Level B (2)
             ....

I need to be able to drag a level C element between level B containers.

see #138


New podman version introduce new issue with selinux and relabelling: relabel failed "/run/netns": operation not supported

kind bug
Description
With latest podman release (see bellow), we encounter an issue when we mount /run/netns with "z,shared" flags:
relabel failed "/run/netns": operation not supported

Steps to reproduce the issue:

Create some network namespace in order to ensure /run/netns exists

Create a container with /run/netns mounted as a volume (--volume /run/netns:/run/netns:z,shared)

Describe the results you received:
The container crashes with an error on the relabelling of /run/netns
Describe the results you expected:
It should start the container and proceed to the relabelling.
Additional information you deem important (e.g. issue happens only occasionally):
Output of podman version:
Version:       <IP_ADDRESS>
Go Version:    go1.10.2
OS/Arch:       linux/amd64

Output of podman info:
host:
  BuildahVersion: 1.6-dev
  Conmon:
    package: podman-<IP_ADDRESS>-2.git9551f6b.el7.x86_64
    path: /usr/libexec/podman/conmon
    version: 'conmon version 1.12.0-dev, commit: 97d5f1232f62307696c8b4b2d430e8b771a45873-dirty'
  Distribution:
    distribution: '"centos"'
    version: "7"
  MemFree: 755589120
  MemTotal:<PHONE_NUMBER>
  OCIRuntime:
    package: runc-1.0.0-57.dev.git2abd837.el7.centos.x86_64
    path: /usr/bin/runc
    version: 'runc version spec: 1.0.0'
  SwapFree:<PHONE_NUMBER>
  SwapTotal:<PHONE_NUMBER>
  arch: amd64
  cpus: 8
  hostname: undercloud.localdomain
  kernel: 3.10.0-957.1.3.el7.x86_64
  os: linux
  rootless: false
  uptime: 1h 53m 11.26s (Approximately 0.04 days)
insecure registries:
  registries:
  - <IP_ADDRESS>:8787
  - <IP_ADDRESS>:8787
registries:
  registries:
  - registry.centos.org
  - registry.access.redhat.com
  - docker.io
  - quay.io
store:
  ContainerStore:
    number: 88
  GraphDriverName: overlay
  GraphOptions: null
  GraphRoot: /var/lib/containers/storage
  GraphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
  ImageStore:
    number: 35
  RunRoot: /var/run/containers/storage

Additional environment details (AWS, VirtualBox, physical, etc.):

@EmilienM I took the liberty to open this one ;). If you have some other things to add, feel free to do so.

Since /run/netns mount does not support labeling, remove the :z.  Should fix the issue.
What is the label on  /run/netns?
ls -lZd /run/netns

Hello @rhatdan
Thanks for your quick answer. The labels (before anything is done with podman or whatever) are:
drwxr-xr-x. root root unconfined_u:object_r:ifconfig_var_run_t:s0 netns/

We have containers that are actually using netns, for creation, removal and global management, and this directory is mounted in multiple containers. That's why I used the ":z" flag - maybe the "shared" will be enough?
Cheers,
C.

Well that is the label of the directory, but the contents of the directory seem to be process labels of the process that created the network namespace.
I see unconfined_t and container_runtime_t.
I believe the container_t process should be allowed to read those.

Hmm ok. So here's the labels for the content of netns:
ls -lZ netns/
-r--r--r--. root root system_u:object_r:proc_t:s0      removeme

This is a namespace created from the host directly. For now I don't have the right process creating the namespaces - I need to patch my code locally in order to drop the ":z", else it won't work as podman will reject that flag and make an error.
We already pushed some patches in our CI in order to get rid of those "z" flags, and apparently it seems to work, at least we can deploy the app - now we have to ensure all related containers can access that directory, and manage the namespaces in it. That's another story.
I'll keep this issue updated accordingly.

@cjeanner have you manually tested the changes in tripleo with selinux enforced? (I haven't yet)

@EmilienM it's on the bench right now with under + overcloud deploy.

@rhatdan ah, forgot to say, it's on a permissive environment… podman shouldn't try to relabel things on a permissive env, should it? I'm not sure docker actually tries that…

@EmilienM so once the patches are applied, I get my containers running with the netns mount, and apparently it's working as expected.
@rhatdan so basically, this seems to be once again the issue that podman tries to relabel things on a non-SELinux enabled system. I think we already hit that in the past.

Thanks Cedric, that's good news. We'll probably be able to restore podman
in our CI asap.
On Fri, Dec 21, 2018, 10:32 AM Cédric Jeanneret<EMAIL_ADDRESS>wrote:

@EmilienM https://github.com/EmilienM so once the patches are applied,
I get my containers running with the netns mount, and apparently it's
working as expected.
@rhatdan https://github.com/rhatdan so basically, this seems to be once
again the issue that podman tries to relabel things on a non-SELinux
enabled system. I think we already hit that in the past.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/containers/libpod/issues/2034#issuecomment-449352081,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABnCoRkojWwEgBPHf4knGG3oFoZYqIGTks5u7LjCgaJpZM4Zb_R0
.

Permsisive does not mean Disabled.  All SELinux actions will take place and only actions denied by SELinux AVC messages will be allowed. Any activity like relabeling, is still going to be blocked if it is not supported.

@cjeanner This is a case where the file system does not support SELinux XAttr labeling.  So the kernel denies the label.  In those cases we have three choices
1: Attempt to mount the file system with a context="LABEL" flag so we treat the entire mount point with a single label
2: we use the default labels contained in the file system and make changes to containers to be able to use these labels
3: Disable SELinux separation.


Can you add the DiscordX.app to the releases tab?

Why didn't you add it to the releases tab?

Can you not just build it yourself? It's an app for Xcode users

How to run it without Xcode ?

If you don't have Xcode, why do you need it?

Why didn't you add it to the releases tab?

https://drive.google.com/file/d/1aL-qcBkKqa2JNBh6Sm2S0fothkvmxU3l/view?usp=sharing


Problem with compiling kinectfusion

Hello! YuXiang, I have problems with compiling with Kinectfusion, it seems like  that the errors related to a statement in dualQuaternion.h. Would you like to help me fix it ? Thanks!
/home/wyx/PoseCNN/lib/kinect_fusion/include/df/util/dualQuaternion.h:109:44: error: expected primary-expression before ‘(’ token
return DualQuaternion(nondual_.cast(),dual_.cast());
^
/home/wyx/PoseCNN/lib/kinect_fusion/include/df/util/dualQuaternion.h:109:71: error: expected primary-expression before ‘>’ token
return DualQuaternion(nondual_.cast(),dual_.cast());
^
/home/wyx/PoseCNN/lib/kinect_fusion/include/df/util/dualQuaternion.h:109:73: error: expected primary-expression before ‘)’ token
return DualQuaternion(nondual_.cast(),dual_.cast());
^
/home/wyx/PoseCNN/lib/kinect_fusion/include/df/util/dualQuaternion.h:109:98: error: expected primary-expression before ‘>’ token
return DualQuaternion(nondual_.cast(),dual_.cast());
^
/home/wyx/PoseCNN/lib/kinect_fusion/include/df/util/dualQuaternion.h:109:100: error: expected primary-expression before ‘)’ token
return DualQuaternion(nondual_.cast(),dual_.cast());

@yuxng


Add Mavlink Status Text.

Waiting for backend to merge.

Awesome, thanks! Yes, let's merge that once backend is ready!

Thank you!


DICOM dose files

Is there an easy way to read DICOM RT_dose files within SimpleITK?
I'm currently loading the 3D dose matrix as numpy and converting to sitk, but I was hoping to find a better way to do this within sitk.
I look forward to hearing from you! Thank you for all your help

We have focused SimpleITK to provide access to DICOM bulk image data and generic access to the meta-data. SimpleITK does not have access to extended structured DICOM data like RT_dose information.