XlaRuntimeError: FAILED_PRECONDITION: DNN library initialization failed.

Description
The OUTPUT:
[1]
2023-07-31 01:53:45.016563: E external/xla/xla/stream_executor/cuda/cuda_dnn.cc:427] Loaded runtime CuDNN library: 8.5.0 but source was compiled with: 8.6.0.  CuDNN library needs to have matching major version and equal or higher minor version. If using a binary install, upgrade your CuDNN library.  If building from sources, make sure the library loaded at runtime is compatible with the version specified during compile configuration.
[2]
XlaRuntimeError                           Traceback (most recent call last)
Cell In[4], line 29
26 model = trainer.make_model(nmask)
28 lr_fn, opt = trainer.make_optimizer(steps_per_epoch=len(train_dl))
---> 29 state = trainer.create_train_state(jax.random.PRNGKey(0), model, opt)
30 state = checkpoints.restore_checkpoint(ckpt.parent, state)
File /mnt/data/miniconda/envs/energy_transformer_117/lib/python3.11/site-packages/jax/_src/random.py:137, in PRNGKey(seed)
134 if np.ndim(seed):
135   raise TypeError("PRNGKey accepts a scalar seed, but was given an array of"
136                   f"shape {np.shape(seed)} != (). Use jax.vmap for batching")
--> 137 key = prng.seed_with_impl(impl, seed)
138 return _return_prng_keys(True, key)
File /mnt/data/miniconda/envs/energy_transformer_117/lib/python3.11/site-packages/jax/_src/prng.py:320, in seed_with_impl(impl, seed)
319 def seed_with_impl(impl: PRNGImpl, seed: Union[int, Array]) -> PRNGKeyArrayImpl:
--> 320   return random_seed(seed, impl=impl)
File /mnt/data/miniconda/envs/energy_transformer_117/lib/python3.11/site-packages/jax/_src/prng.py:734, in random_seed(seeds, impl)
732 else:
733   seeds_arr = jnp.asarray(seeds)
--> 734 return random_seed_p.bind(seeds_arr, impl=impl)
File /mnt/data/miniconda/envs/energy_transformer_117/lib/python3.11/site-packages/jax/_src/core.py:380, in Primitive.bind(self, *args, **params)
377 def bind(self, *args, **params):
378   assert (not config.jax_enable_checks or
379           all(isinstance(arg, Tracer) or valid_jaxtype(arg) for arg in args)), args
--> 380   return self.bind_with_trace(find_top_trace(args), args, params)
File /mnt/data/miniconda/envs/energy_transformer_117/lib/python3.11/site-packages/jax/_src/core.py:383, in Primitive.bind_with_trace(self, trace, args, params)
382 def bind_with_trace(self, trace, args, params):
--> 383   out = trace.process_primitive(self, map(trace.full_raise, args), params)
384   return map(full_lower, out) if self.multiple_results else full_lower(out)
File /mnt/data/miniconda/envs/energy_transformer_117/lib/python3.11/site-packages/jax/_src/core.py:790, in EvalTrace.process_primitive(self, primitive, tracers, params)
789 def process_primitive(self, primitive, tracers, params):
--> 790   return primitive.impl(*tracers, **params)
File /mnt/data/miniconda/envs/energy_transformer_117/lib/python3.11/site-packages/jax/_src/prng.py:746, in random_seed_impl(seeds, impl)
744 @random_seed_p.def_impl
745 def random_seed_impl(seeds, *, impl):
--> 746   base_arr = random_seed_impl_base(seeds, impl=impl)
747   return PRNGKeyArrayImpl(impl, base_arr)
File /mnt/data/miniconda/envs/energy_transformer_117/lib/python3.11/site-packages/jax/_src/prng.py:751, in random_seed_impl_base(seeds, impl)
749 def random_seed_impl_base(seeds, *, impl):
750   seed = iterated_vmap_unary(seeds.ndim, impl.seed)
--> 751   return seed(seeds)
File /mnt/data/miniconda/envs/energy_transformer_117/lib/python3.11/site-packages/jax/_src/prng.py:980, in threefry_seed(seed)
968 def threefry_seed(seed: typing.Array) -> typing.Array:
969   """Create a single raw threefry PRNG key from an integer seed.
970
971   Args:
(...)
978     first padding out with zeros).
979   """
--> 980   return _threefry_seed(seed)
[... skipping hidden 12 frame]

File /mnt/data/miniconda/envs/energy_transformer_117/lib/python3.11/site-packages/jax/_src/dispatch.py:463, in backend_compile(backend, module, options, host_callbacks)
458   return backend.compile(built_c, compile_options=options,
459                          host_callbacks=host_callbacks)
460 # Some backends don't have host_callbacks option yet
461 # TODO(sharadmv): remove this fallback when all backends allow compile
462 # to take in host_callbacks
--> 463 return backend.compile(built_c, compile_options=options)
XlaRuntimeError: FAILED_PRECONDITION: DNN library initialization failed. Look at the errors above for more details.
`
What jax/jaxlib version are you using?
jax0.4.10, jaxlib0.4.10+cuda11.cudnn86
Which accelerator(s) are you using?
GPU
Additional system info
python3.11.4, Ubuntu22.04, cuda11.7,cudnn86
NVIDIA GPU info
`+-----------------------------------------------------------------------------+
| NVIDIA-SMI 520.61.05    Driver Version: 520.61.05    CUDA Version: 11.8     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA GeForce ...  On   | 00000000:18:00.0 Off |                  N/A |
| 30%   33C    P8    22W / 350W |    258MiB / 12288MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   1  NVIDIA GeForce ...  On   | 00000000:3B:00.0 Off |                  N/A |
| 30%   30C    P8     6W / 350W |      8MiB / 12288MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   2  NVIDIA GeForce ...  On   | 00000000:86:00.0 Off |                  N/A |
| 30%   34C    P8    23W / 350W |      8MiB / 12288MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   3  NVIDIA GeForce ...  On   | 00000000:AF:00.0 Off |                  N/A |
| 30%   30C    P8    10W / 350W |      8MiB / 12288MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A      2565      G   /usr/lib/xorg/Xorg                  4MiB |
|    0   N/A  N/A      2861    C+G   ...ome-remote-desktop-daemon      249MiB |
|    1   N/A  N/A      2565      G   /usr/lib/xorg/Xorg                  4MiB |
|    2   N/A  N/A      2565      G   /usr/lib/xorg/Xorg                  4MiB |
|    3   N/A  N/A      2565      G   /usr/lib/xorg/Xorg                  4MiB |
+-----------------------------------------------------------------------------+
`

The error message says what's wrong:
 Loaded runtime CuDNN library: 8.5.0 but source was compiled with: 8.6.0. CuDNN

You installed a version of jax that needs CuDNN 8.6, but CuDNN 8.5 was found. I suggest reinstalling using the cuda11_pip or cuda12_pip packages, in a fresh virtual environment.
Hope that helps!

@hawkinsp Thank you so much！


adding workaround for docker/docker-registry#892

ok. now atomic as properly rebased on top of your master :smile:

Works as expected. Will take on this and increase resilience.


Add Linaro Aarch64 builds to community

As per - https://github.com/tensorflow/build/issues/15 and discussion in SigBuild.

@googlebot I signed it!

@angerson Hello, just wondering if there's an update about this pull request for the Community builds please

@neuralmimicry Thanks for the ping. Sorry this got lost!
This looks good to me.


How to stay logged in?

From my understanding, logging in is only possible via launchAuth, which in turn takes forever to do its job even if the user signed in previously. Is there a way to store the authentication data until logout() is called? I can't find any api tokens exposed by this thing.

Nevermind, I think I figured it out. The firebase_auth package keeps track of the user so you can use that one to get the current logged in status.


Add discord link to the cufries website

Done, added in ce3302f31d52a5ed3e7187b467cffd79b8b030f7. Also went ahead and added a link to the GitHub repo in 11eed0d7082a1501e48b644d1b0fcc38fce5c7ce


Altered bower.json

Removed references to /src files in bower.json

According to this specification (https://github.com/bower/bower.json-spec#main), main section should include full version of files such as sources or compiled sources(from CoffeeScript, etc.)
It should remove references to min files instead of sources

So can we get one or the other removed? 'Cause now I'm getting both files included in index.html bower build sections whenever running bower install from scratch. Or are there other fixes for this behavior?

@rallin @simonasdev I've removed the references to the minified source files. Just needs pulling.


Getting TypeError: quantize_dynamic() got an unexpected keyword argument 'optimize_model'

Hi all, I am trying to quantize the onnx model using the following code section mentioned in the onnx notebook,
'''
onnx_model_quantized_path = "sam_onnx_quantized_example.onnx"
quantize_dynamic(
model_input=onnx_model_path,
model_output=onnx_model_quantized_path,
optimize_model=True,
per_channel=False,
reduce_range=False,
weight_type=QuantType.QUInt8,
)
onnx_model_path = onnx_model_quantized_path
'''
but getting the following error
'''
TypeError                                 Traceback (most recent call last)
 in <cell line: 2>()
1 onnx_model_quantized_path = "sam_onnx_quantized_example.onnx"
----> 2 quantize_dynamic(
3     model_input=onnx_model_path,
4     model_output=onnx_model_quantized_path,
5     optimize_model=True,
TypeError: quantize_dynamic() got an unexpected keyword argument 'optimize_model'
'''
any help on this would be highly appreciated
Thank you

This seems to be caused by a change in newer versions of the onnxruntime library. Specifically, the quantize_dynamic(...) function no longer has the optimize_model argument.
At the moment, the simplest fix is to just delete or comment out the line that's giving the error (i.e. optimize_model=True,).
If you're comfortable with modifying the installation, the other fix is to uninstall the current version of the library and then install an older version (version 1.15.1 seems to work). This has the benefit of working longer term in case, for example, the library is updated even further breaking compatibility elsewhere in the future. You can fix the installation with:
pip uninstall onnxruntime
pip install onnxruntime==1.15.1

great thank you

It seems not works on me


Arash/Mobile Footer

Description
Add Accordion to footer and adjustment
Type of change

[ ] Bug fix
[ ] New feature
[ ] Refactor code
[ ] Update translation text
[ ] Breaking change
[ ] Dependency update
[ ] This change requires a documentation update
[ ] Release

We can add a short name for languages inside the config file instead of using the substring function to cut the 3 first letter of the language name.


cmd/compile: invalid instruction on nacl amd64p32

Please answer these questions before submitting your issue. Thanks!

What version of Go are you using (go version)?
tip

What operating system and processor architecture are you using (go env)?
nacl amd6432

What did you do?
See change: https://go-review.googlesource.com/#/c/21872/

What did you expect to see?
To compile:

What did you see instead?
cmd/compile/internal/ssa/zcse.go:83: invalid instruction: 01074 (/tmp/workdir/go/src/cmd/compile/internal/ssa/phiopt.go:66)	MOVQL	16(R15)(R8*1), BX

https://storage.googleapis.com/go-build-log/c2282152/nacl-amd64p32_0c3a4e20.log
@randall77

Small repro:
package main

type T struct {
	i int64
}

func f(v *T) int32 {
	ops := [2]int32{3, 4}
	return ops[v.i]

}


autoDeleteOnIdle cannot be set on queue creation when also setting a dead letter forward

Package Name:  @azure/service-bus
Package Version: 7.0.3
Operating system: linux
[x] nodejs

version: v12.21.0

[x] browser

name/version:

[x] typescript

version: 3.7.5

Is the bug related to documentation in

[ ] README.md
[ ] source code documentation
[ ] SDK API docs on https://docs.microsoft.com

Describe the bug
autoDeleteOnIdle cannot be set on queue creation when also setting a dead letter forward, it is always created with the maximum period value, on asb on login I can set autodelete for this kind of queue
To Reproduce
Steps to reproduce the behavior:
import { ServiceBusAdministrationClient } from '@azure/service-bus';
(async () => {
  const admin = new ServiceBusAdministrationClient(process.env.AZURE_SB_CONNECTION_STRING!);
  const q = 'test-idle-out';
  await admin.createQueue('deadletterqueue');
  const props = await admin.createQueue('test-idle-out', { autoDeleteOnIdle: 'PT20M' });
  const props2 = await admin.createQueue('test-idle-out-deadletter', { autoDeleteOnIdle: 'PT20M', forwardDeadLetteredMessagesTo: 'deadletterqueue' });
  console.log(props.autoDeleteOnIdle);
  console.log(props2.autoDeleteOnIdle);
  admin.deleteQueue('test-idle-out');
  admin.deleteQueue('test-idle-out-deadletter');
  admin.deleteQueue('deadletterqueue');
})();

Output:
PT20M
P10675199DT2H48M5.4775807S
Expected behavior
Output:
PT20M
PT20M

hi @hartwig-wutscher-ibm, I was able to replicate this bug and I really appreciate you taking the time to report it.
The actual bug was with the way we're sending the ATOM requests, which handle the entity update you're trying to do. I've got a fix submitted in this PR(#14692). This bug was actually causing forwarding to not be properly setup, even though the API claimed that it was.
With that said, the normal behavior of forwarding and autoDeleteOnIdle is actually correct, as explained here in the note at the end of the linked section.

#14692 is merged, we'll release a new version for the package soon.


URL is shortened on every upload

Hi!
We are running the latest bootstrap filestyle 1.2.1. Our forms have multiple file upload buttons where the user will upload documents, go back another time to the same form and upload a new version. On the second submit, our code takes the relative URL and turns it into a full URL. The issue is that the filestyle library is shortening the relative URL on every submit until it becomes too short for the underlying Umbraco layer.
Please help!
Tom

I regret to inform you but the plugin does not change the url of the requested image. What happens is that browsers deliver the url in different ways. This operation is standard browsers and you will have to adapt to it, since javascript does not have access to the file system to return a different url.


Add a free full-stack programming course to free-courses-en.md

Hi I am learning with MigraCode Barcelona, and find its syllabus comprehensive, and interesting with loads of good exercises. It's entirely free and open to everyone. I would love to add this to free-courses-en.md  file. Thank you!

Feel free to add it and raise a PR. No need to have an issue open to contribute to the repo. Hope it helps

Hi @shrn01  I have created pull request  #9076 for this.

added


GetAllAsync() in CosmosDB connector does not return all records

Describe the bug
GetAllAsync() in CosmosDB connector does not return all records.
This issue also impacts GetNearestMatchAsync() as it does not count all the records in the comparation.
To Reproduce
Steps to reproduce the behavior:

Create Instance of CosmosDBStorage
Execute GetAllAsync() on the instance

Expected behavior
returns all memory instance stored in cosmosDB
Additional context
The root cause is code not reading all result from cosmosDB
Current code:
        var items = await iterator.ReadNextAsync(cancel).ConfigureAwait(false); //only reads first batch of results

        foreach (var item in items)
        {
            var vector = System.Text.Json.JsonSerializer.Deserialize<float[]>(item.EmbeddingString);

            if (vector != null)
            {
                yield return MemoryRecord.FromJson(
                    item.MetadataString,
                    new Embedding<float>(vector),
                    item.Id,
                    item.Timestamp);
            }
        }

correct code:
        while (iterator.HasMoreResults) //read all result in batch
        {
            var items = await iterator.ReadNextAsync(cancel).ConfigureAwait(false);

            foreach (var item in items)
            {
                var vector = System.Text.Json.JsonSerializer.Deserialize<float[]>(item.EmbeddingString);

                if (vector != null)
                {
                    yield return MemoryRecord.FromJson(
                        item.MetadataString,
                        new Embedding<float>(vector),
                        item.Id,
                        item.Timestamp);
                }
            }
        }

Actually, a stored procedure should be more efficient, I'm working on an improved version of CosmosDB which uses UDF and StoredProcedure.

Thank you so much! Looking forward to the improvements.

PR for your suggested fix for now https://github.com/microsoft/semantic-kernel/pull/452

Thanks for your fix.
I've finished changing CosmosDB to use server side UDF, this could greatly reduces network IO. As CosmosDb connector does not have unit tests. Now I'm refactorying the unit tests to create a basic test class for IMemoryStore, this can make futher connector easier to implement unit test.


Debug Procedure

Confused about the debug procedure of pixsfm.
I've searched for pybind11 debug and tried methods mentioned in stackoverflow and nadiah.org.
Finally I debug with vscode+Python C++ Debugger extension by BeniBenj.
It worked fine for simple example project, while failed for pixsfm. And I've add self.debug=True in setup.py in order to preserve debug info.
Maybe PyCharm is the solution?

SORRY for bother, it seems that I mixed debug and release version of .so file. After reinstalling debug version _pixsfm.cpython-37m-x86_64-linux-gnu.so it worked well.
This issue can be deleted now.


Add support for bytes sent and received in message events

Originally filed by @ alexamies at https://github.com/census-instrumentation/opencensus-go/issues/1130
Describe the bug
The trace.MessageEvent struct has a field for UncompressedByteSize:
https://godoc.org/go.opencensus.io/trace#MessageEvent
but those are not included in the Zipkin exporter
https://github.com/census-instrumentation/opencensus-go/blob/master/exporter/zipkin/zipkin.go#L184
To Reproduce
Need PR #1129 (https://github.com/census-instrumentation/opencensus-go/pull/1129)
Steps to reproduce the behavior:

Run the Go HTTP integration example
https://opencensus.io/guides/http/go/net_http/server/

Go to Zipkin
http://localhost:9411/zipkin/

Click on a span.
As per the screenshot, all that is shown is 'SENT' or 'RECV'

Expected behavior
The number of bytes sent and received.
Additional context
These should be included and it is very important in determining why one trace might be taking longer than another trace. I submit a PR to fix the issue.

Addressed by PR here:
https://github.com/census-ecosystem/opencensus-go-exporter-zipkin/pull/7

Fixed in #7.


Add shl and shr to llvmir

Saw chenyu pr on shl and shr refactor of transcendental and most of llvm tests failed due to the lack of support of those op in the backend. I don't know if it was removed or never added to the backend for some specific reason but I believe it is worth having support for them in llvm backend.

i ended up not doing that because for the middle uop phrase we want to keep a minimal ops, so prefer *2 over <<1 because we can keep the simplification rules minimum. don't want to double rules to have one for mul and one for shl for example.

I see, okay, closing then! Thanks

But having support in cstyle and ptx don't force that? Why having support in llvm different?

Reopening, I believe I incorrectly assessed your comment

something broke fro ptx, making it a draft, reviewing in 1h

i think it's easier to cast in llvm renderer, but if you are changing SHR/SHL spec you also need to update this https://github.com/tinygrad/tinygrad/blob/53db3478fef19d2c74d10a7b99e49a266e3abe16/tinygrad/ops.py#L786

i think it's easier to cast in llvm renderer, but if you are changing SHR/SHL spec you also need to update this
https://github.com/tinygrad/tinygrad/blob/53db3478fef19d2c74d10a7b99e49a266e3abe16/tinygrad/ops.py#L786

Can't change shl and shr spec as llvmir and ptx have different requirements. How is this solved? I guess the spec just covers the tighter case that covers both?
Given x << y or x >> y:

llvmir require x.dtype == y.dtype
ptx requires y.dtype == uint

what about the following spec?
*[(UPat(UOps.ALU, src=(UPat(name="x"), UPat(name="y")), name="alu", arg=shift),
 lambda alu,x,y: alu.dtype == x.dtype and (x.dtype == y.dtype or y.dtype == dtypes.uint)) for shift in (BinaryOps.SHL, BinaryOps.SHR)],

That spec is fine

That spec is fine

current one or the one in the comment?


Add Python 3.12 to release workflow

Add Python 3.12 to release workflow so we also build wheels for this version
https://github.com/iotaledger/iota-sdk/blob/4883f7c7e7d304254825ceba1d37ebbdc61b8ab7/.github/workflows/bindings-python-publish.yml#L14

@Thoralf-M Can I please work on this ? If yes please assign it to me :)


Question about upsampling function

Hi everyone,
Can anyone tell me, for upsample_layer function(in layer_util.py), why should we use resize_nearest_neighbor method instead of upsampling function offered by tensorflow？
Thank you

This comes from the yolo source code. see yolo cfg here: https://github.com/pjreddie/darknet/blob/master/cfg/yolov3-voc.cfg#L630
yolo uses the nearest neighbor resizing.

@wizyoung Thank you and good to know this.
Please allow me to follow-up. You just said "yolo uses the nearest neighbor resizing". Do you have any reference to it? I will be appreciate if you can point me out some clues. I do checked the link you attached but I do not think it suggests what you said above.

@Cli98 The C source code of the upsample layer in the config file is defined here: https://github.com/pjreddie/darknet/blob/master/src/blas.c#L334. So you see, it's the nearest neighbor resize.

@wizyoung My bad. I'm not quite familiar with C. Still thank you for your kindly response.

Actually, I think is a good question. So I will mark it as good first issue tag.


(First) publish as alpha on crates.io

Items:

[x] wxrust-config

0.0.1-alpha is published on https://crates.io/crates/wxrust-config but void for #162
[x] 0.0.1-alpha2

[x] wxrust-base

[x] 0.0.1-alpha

https://crates.io/crates/wxrust-base

[x] wxrust-core

[x] 0.0.1-alpha

https://crates.io/crates/wxrust

Published.
I'll dogfooding with this!


Send extra information to accompany table schema

For each table:

The schema
How many rows

And for each column in the table:

How many unique values?
3 most common values (truncated) - to help it understand things like state of CA v.s. California

I should cache this as it may be expensive to calculate, especially for wide tables
YAML is a good format here.

Alternative idea for sending example rows - send one or two whole row example, but try to find rows that have the least null or blank columns possible.
Here's a query to generate a query to find the rows with the least blank columns:
SELECT
    'SELECT
  ' || GROUP_CONCAT('(CASE WHEN ' || name || ' IS NOT NULL AND ' || name || ' != '''' THEN 1 ELSE 0 END)', ' +
  ')
    || ' AS non_empty_count, *
  FROM ' || :table || ' ORDER BY non_empty_count DESC limit 3' AS query
FROM pragma_table_info(:table);

https://datasette.io/content?sql=SELECT+
++++'SELECT
++'+||+GROUP_CONCAT('(CASE+WHEN+'+||+name+||+'+IS+NOT+NULL+AND+'+||+name+||+'+!%3D+''''+THEN+1+ELSE+0+END)'%2C+'+%2B
++')+
++++||+'+AS+non_empty_count%2C+*
++FROM+'+||+%3Atable+||+'+ORDER+BY+non_empty_count+DESC+limit+3'+AS+query
FROM+pragma_table_info(%3Atable)%3B
&table=releases
And here's an example of running one of those generated queries:
https://datasette.io/content?sql=SELECT
++(CASE+WHEN+html_url+IS+NOT+NULL+AND+html_url+!%3D+''+THEN+1+ELSE+0+END)+%2B
++(CASE+WHEN+id+IS+NOT+NULL+AND+id+!%3D+''+THEN+1+ELSE+0+END)+%2B
++(CASE+WHEN+author+IS+NOT+NULL+AND+author+!%3D+''+THEN+1+ELSE+0+END)+%2B
++(CASE+WHEN+node_id+IS+NOT+NULL+AND+node_id+!%3D+''+THEN+1+ELSE+0+END)+%2B
++(CASE+WHEN+tag_name+IS+NOT+NULL+AND+tag_name+!%3D+''+THEN+1+ELSE+0+END)+%2B
++(CASE+WHEN+target_commitish+IS+NOT+NULL+AND+target_commitish+!%3D+''+THEN+1+ELSE+0+END)+%2B
++(CASE+WHEN+name+IS+NOT+NULL+AND+name+!%3D+''+THEN+1+ELSE+0+END)+%2B
++(CASE+WHEN+draft+IS+NOT+NULL+AND+draft+!%3D+''+THEN+1+ELSE+0+END)+%2B
++(CASE+WHEN+prerelease+IS+NOT+NULL+AND+prerelease+!%3D+''+THEN+1+ELSE+0+END)+%2B
++(CASE+WHEN+created_at+IS+NOT+NULL+AND+created_at+!%3D+''+THEN+1+ELSE+0+END)+%2B
++(CASE+WHEN+published_at+IS+NOT+NULL+AND+published_at+!%3D+''+THEN+1+ELSE+0+END)+%2B
++(CASE+WHEN+body+IS+NOT+NULL+AND+body+!%3D+''+THEN+1+ELSE+0+END)+%2B
++(CASE+WHEN+repo+IS+NOT+NULL+AND+repo+!%3D+''+THEN+1+ELSE+0+END)+%2B
++(CASE+WHEN+reactions+IS+NOT+NULL+AND+reactions+!%3D+''+THEN+1+ELSE+0+END)+%2B
++(CASE+WHEN+mentions_count+IS+NOT+NULL+AND+mentions_count+!%3D+''+THEN+1+ELSE+0+END)+AS+non_empty_count%2C+*
++FROM+releases+ORDER+BY+non_empty_count+DESC+limit+3&table=releases

Results from that probably still need a bit of truncation before turning them into an example.
Would need to use evals to decide if passing one or two example rows in full gives better results than passing a set of example values for each column, as in https://github.com/datasette/datasette-query-assistant/issues/2#issuecomment-2021892973


[AutoRelease] t2-containerservice-2023-09-21-85273(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/4535
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=982
BuildTargetingString
azure-mgmt-containerservice
Skip.CreateApiReview
true

issue link:https://github.com/Azure/sdk-release-request/issues/4535


Fixes #14

Merged in f9d962386b846b7c2de3df40b4c36278aa79b272 (I was supposed to push to the branch before merging it, but gh checkout pr left my local branch aliasing XTermConsoleAddon/master)


Restore fix for DNS config in DB with changed db migration order

All changes from reversed https://github.com/kyma-project/control-plane/pull/1481 with modified migration order for dns table to fix problem with provisioner database

/retest

/retest

/retest

/retest


Migrate DB to MySQL

The default configuration will remain SQLite. To overwrite the default configuration with MySQL:

Install mysqlclient with pip
Create local_settings.py in the root of the project with the desired database configuration
Run the migrate command of manage.py using the --settings=local_settings command


[MINOR] fix(test): remove useless code from ServletTest.testRequestWithWrongCredentials

What changes were proposed in this pull request?
Remove useless code from ServletTest.testRequestWithWrongCredentials.
Why are the changes needed?
The logic of sleep is useless. This is a mistake.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
CI

@jerqi @rickyma Thanks for your review.


Bogus "Patterns are incomplete" error for if-then-else

The following code
assume val bar : p:Type -> Tot bool
val foo : unit -> Tot bool
let foo _ = (if bar False then true else false)

raises a bogus "Patterns are incomplete" error:
Error bug121.fst(7,0-8,0): The following problems were found:
	Patterns are incomplete (bug121.fst(7,12-7,47))

The encoding fails to prove that False:Type.
This is because we have logic type False in the prelude and the encoding has been omitting kind information for logic types.
If you wrote (if bar int then true else false) then it goes through.
I'll restore kind information for logic types too.

I'm getting this problem again in lambda_omega.

Nik's latest changes also fixed this.


wrong xaxis labels generation

Codepen
https://codepen.io/y_nk/pen/MWgMGNP
Explanation
When using series with [x, y] point format, xaxis labels are calculated in a wrong way.
In this codepen, you can see :
dates in a generated array for 2019-10-01 to 2019-10-07
serie is a pseudo random generated serie with data points for 2019-10-01, 2019-10-03 and 2019-10-05
In the current codepen, there's no use for dates for now, but ideally it should be provided in xaxis.categories. regardless of this, xaxis labels are wrongly generated. You can see the logs i've provided in the <pre> block and compare the x values in serie and what is given as val to xaxis.labels.formatter

What is the behavior you expect?
ideally, xaxis.categories is taken in consideration for xaxis.type === 'datetime' so we can use dates instead of auto-generated labels.

What is happening instead?
labels are wrongly generated.

What error message are you getting?
none

If you want complete control over datetime generation, along with the formatter function, you can use xaxis.min, xaxis.tickAmount and xaxis.max like below
xaxis: {
  type: 'datetime',
  min: new Date('2019-10-01 GMT').getTime(),
  max: new Date('2019-10-10 GMT').getTime(),
  tickAmount: 10,
  labels: {
    formatter: (val, series, index) => {
      return new Date(val).toString()
    }
  }
}


Added hover effect to navbar

🛠 Issue (Number)1422

Closes #
Description
Please include a summary of the change. Please also include relevant motivation and context. List any dependencies that are required for this change.
Added  Hover Effect to the navbar in the Triposity Project .

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[ ] I have made this from my own
[ ] I have taken help from some online resourses
[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] The title of my pull request is a short description of the requested changes.

ATTACH SCREEN-SHOTS / DEPLOYMENT [LINK](

)

Make the project more attractive

@TusharKesarwani  could you please let me know the changes you  want me to bring?

Make the project more attractive

@TusharKesarwani could you please let me know the changes you want me to bring?

Work on the UI of the website
Change the look
Make it attractive


Fetch APIs from docs/* folder of repo

@redonkulus @jedireza
Fixes #51

CLA is valid!

Before merging we need to move the Docs into the right folders in all the individual repos.

@Vijar i updated this branch to use the createKey for docs. Also fixed up the tests. Lastly, I created the associated readme docs in each repo so the API links would work.
/cc @jedireza

Coverage decreased (-1.19%) to 98.81% when pulling d8a6f1e30008ed528dd71d22da77c6fb09fa176d on apidocs into 72311e573f09493c4dbaa0698091ede1306f5b34 on master.

Coverage remained the same at 100.0% when pulling 1ddfce383f8c1e1a7379012dc1a594c2519db8c0 on apidocs into 72311e573f09493c4dbaa0698091ede1306f5b34 on master.

@redonkulus your changes look good

Love it, :boat:


Recycling Bad MySQL Connections

Resolves ceros/ceros-product#3986
Running unit tests locally:

Login sharejs
NODE_ENV=development npm install
npm test

To run off your local ceros-sharejs code:

In ~/utils/build_docker_sharejs.sh, change the line 6: docker run -d -p 8000:8000 --env-file /vagrant/data/envfile -v /home/vagrant/ceros-sharejs/:/usr/lib/node_modules/share --name sharejs sharejs
Run ~/utils/build_docker_sharejs.sh just once.

Reviewer Notes:

Refactored the mysql.js driver to use promises and lodash. The old implementation looked auto-converted from coffeescript and was just callback hell. To make sure we handle fatal errors after ALL queries, I made a common query method.
We now checks for any "fatal" errors returned from queries and recreates the db connection and rollbars.
The test/db.coffee is actually integration tests that require a running mysql instance. Test tables are created in the database.  The test/mysql.js is a collection of pure unit tests specifically for the mysql driver.

Some comments and questions for you @kirkeverett

@danielBingham back to you

Looks good, Code +1 @kirkeverett

Well after much difficulty, I finally got this to do what it's supposed to do. Among my difficulties was our local db having a max_allowed_packet of 64mb causing the tests to hang, our local db not allowing the max_allowed_packet to be updated in my.cnf and requiring it to be done in a query, the restoredb script restarting the mysql server and wiping out my max_allowed_packet change. In the end, none of problems I had were with this story, except maybe the hanging test and that's fixed now.
So functional 👍 and also code 👍 on that last commit.

And by functional 👍 , I mean on the dev testing side. I do not speak for the rest of QA. I'd rather not be associated with that lot.

Not so fast @danwashable Can you review the last 2 commits on the tests?

Last commits 👍

Functional 👍
♻ 🏬


We are THE only one

Reflecting the repo description: https://github.com/wp-cli/wp-cli

👌

@szepeviktor there's more:
https://github.com/wp-cli/wp-cli/search?utf8=✓&q=A+command+line+interface&type=
https://github.com/wp-cli/handbook/search?utf8=✓&q=A+command+line+interface&type=

@diggy We welcome PR-s!


large error between linear velocity of "framelinvel" and J*qdot

Hi,
I'm a student and I'm trying to use MuJoCo for IK controller.
I'm looking for some help with the computation of spatial velocity of end effector.
I used two methods to get the linear velocity of the site 'ee'. One is the sensor "framelinvel" and the other is jacp @ data.qvel. However, I found the quantities didn't match.
Here is a simple model with one joint:

minimal exmaple
import mujoco
import time
import itertools
from mujoco import viewer
import numpy as np
import matplotlib.pyplot as plt

xml = """
<mujoco>
  <worldbody>
    <light name="top" pos="0 0 1"/>
    <body name="box" euler="0 0 30">
      <joint name="swing" type="hinge" axis="0 1 0" pos="-.2 -.2 -.2"/>
      <geom name="red_box" type="box" size=".2 .2 .2" rgba="1 0 0 1"/>
      <site name="ee" pos='.5 .5 .5' size="0.1 0.1 0.1" rgba="0 0 1 1"/>
    </body>
  </worldbody>

  <sensor>
    <framepos name="ee_pos" objtype="site" objname="ee"/>
    <framelinvel name="ee_vel" objtype="site" objname="ee"/>
  </sensor>
</mujoco>
"""
model = mujoco.MjModel.from_xml_string(xml)
renderer = mujoco.Renderer(model)
model.opt.timestep = 0.002
data = mujoco.MjData(model)

mujoco.mj_forward(model, data)
sparse_Jac = bool(mujoco.mj_isSparse(model))

print(f'Is Jacobian Sparse: {sparse_Jac}')

# print(model.nkey, model.ngeom, model.njnt)

# compute Jacobian of 'ee' site
jacp = np.zeros((3, model.nv), dtype=np.float64)
jacr = np.zeros((3, model.nv), dtype=np.float64)

vel_error = []

for i in range(2000):
    mujoco.mj_step(model, data)

    mujoco.mj_jacSite(model, data, jacp, jacr, 0)
    jqdot_vel = jacp @ data.qvel

    sensed_vel = data.sensor('ee_vel').data
    e = jqdot_vel - sensed_vel

    print(f'error: {e}')
    vel_error.append(e)

viewer.launch(model, data)
vel_error_norm = [np.sqrt(np.sum(err ** 2)) for err in vel_error]
plt.figure(1)
plt.plot(vel_error_norm)
plt.show()

Here is a screenshot of L2 norm of the error illustrating my question:

The sensor is updated during mj_forward and contains the velocity value before time integration, whereas qvel contains joint velocities after the time integration. See https://colab.research.google.com/drive/1SqI8K29QDVWWK-H3iebhoFad14JUohtH


HDDS-5615 Add a simple test suite for HTTPFS GW

What changes were proposed in this pull request?
Added robot tests for the HttpFS gateway. In the tests we use curl command to try out the operations and check the response for the expected objects. The robot tests are added in the compose/ozone test.sh script.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-5615
How was this patch tested?
The robot tests were run by the test.sh script in the compose/ozone directory and all the test cases passed.

Hi @dombizita thank you for your work on this one. I have merged back the master into HDDS-5447-httpfs branch, and also merged the changes to your PR's branch, in order to have the CI changes and reduce our testing footprint on the branches and PRs whenever it is possible.
Please don't forget to update your local branches.
I owe you a review on this, and plan to do it next week.

Hi @dombizita I have took a look into the changes, and left a few inline comments requesting for some improvements and clarification, thank you for your work on this so far, I hope you don't mind to implement a few more requests, to make the test more comprehensive, it would also be nice to at least clarify weird or unexpected behaviour in comments where appropriate. For details see the inline comments plese.

Hi Zita, great work on this so far, so it turned out that some of the functionality is not working properly, I am happy to see that the effort put into those tests are preserved and just commenting them out is a good idea.
As a basic test set, I think it is good, we need to further check into the missing pieces and re-enable the tests but that we can do in a separate effort.
If CI is fixed after reverting the curator dependency removal from the httpfs branch, I am +1 to commit this.
Can you please trigger a new CI run?


Allow upgrading regular pipes to high-pressure versions with the upgrade planner

Upgrading all the pipes in my existing save by hand would have been very tedious!

Thanks for being interested enough to make a PR!
Unfortunately, I think I won't merge this, because it would be confusing with bob's mods. There are many kinds of pipes in bob's, so there is no single upgrade path. It is simpler to have the player choose which pipe to upgrade to.
The player can still upgrade pipes with the upgrade planner, they just need to select the high-pressure version.

No worries. I don't use Bob's mods so it did the job for me.
It might be possible to set the attributes conditionally on a mod being present or not.


Throw up a warning on LPM.

Describe the feature you'd like
You can notify a user that has LPM on to disable it (as afaik, you can't jailbreak with it enabled)
Additional context
Here's a blog post about it: https://useyourloaf.com/blog/detecting-low-power-mode/
// Swift
if NSProcessInfo.processInfo().lowPowerModeEnabled {
  // stop battery intensive actions
}

// Objective-C
if ([[NSProcessInfo processInfo] isLowPowerModeEnabled]) {
  // stop battery intensive actions
}

my XS max jailbreaks just fine with LPM enabled.

Weird. Must’ve taken me 10 attempts with Airplane Mode on + No siri.

On Jul 1, 2020, at 2:29 AM, Hamlock-maneuverr<EMAIL_ADDRESS>wrote:

my XS max jailbreaks just fine with LPM enabled.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Allow hiding "Missing version constraint" warning via configuration, or only warn for entire workspace

The configuration:

virtual workspace with A & B
package A that depends on "torch"
package B that depends on "torch==2.5.1"

doing a uv sync gives a warning about a missing version constraint for torch, I assume while it's processing A's dependencies. I'd like to hide these warnings, since they're just noise for my developers. I also tried with --all-packages by turning my workspace root into a non-virtual workspace and adding a torch>1 dependency into the workspace root; but I still got the warning, so this seems like it's a per-package warning, not an overall workspace warning.
Alternatively, this request could be to wait until the entire workspace constraints are collected and only then print the warnings.
(I've got a bunch of pre-pyproject external python projects in a monorepo; I'm creating the pyproject to mirror their requirements.txt files exactly, so I'd rather go in and fix the dependencies in their individual pyproject files)
Also -- thank you for uv! It's brought a lot of sanity to my developers :)
Also also -- I'm happy to make a PR for stuff like this; just let me know if it's a PR you'd be OK with accepting

Thanks for the kind words and the offer :)
I'm open to this but can I ask why you can't add a lower-bound on torch in package A? Is it inconvenient, or is it impossible?

Another question for my understanding: Are the packages in the workspace intended to be published, or do the run without publishing (e.g. deploying in docker container)?

I'm open to this but can I ask why you can't add a lower-bound on torch in package A? Is it inconvenient, or is it impossible?

It's not impossible, but very inconvenient -- since it's not just package A, it's package A...Z (currently around two dozen in our monorepo) :) Whenever we pull an update to one of those packages I've been just doing a uv add -r requirements.txt to pull in updated dependencies into our pyproject files (since those are not in the upstream packages).
Easiest thing would be to add a uv.tool config option for missing_version_constraint=ignore vs. warn; more complex would be to add the ability to warn only if the workspace is missing a constraint (which would be the most useful I think). I'd probably do the config first, and then extend it to missing_version_constraint=workspace or something to do the second.

Lower bounds may be useful for libraries, but they are entirely irrelevant for applications that always work with all packages pinned to exact versions in a lock file. In my typical application, I encounter around 50 warnings of this type, creating significant noise and increasing the likelihood of missing important warnings.

Why is a lower-bound irrelevant for an application?

An application (like microservice), in contrast to a library, does not need to work with multiple versions of its dependencies. The typical workflow involves updating some or all dependencies (manually or using a tool like Renovate), testing the application with the updated versions, and deploying if everything works fine. If issues arise, the problematic dependency version is restricted (typically using !=, rarely with <), and the process is repeated. Since updates generally involve moving forward rather than downgrading versions, lower bounds have no impact on the outcome.
The best practice is to justify every version restriction on dependencies. For a library, this typically involves specifying the oldest version that provides the required features or, at the very least, the lowest version tested in a matrix. For an application, however, there is no need to support older versions of dependencies, and testing in a matrix is often too resource-intensive. Consequently, there is little reason to test with older versions. If lower bounds are set, they often become arbitrary numbers that cannot be justified or guaranteed to work with the application. Alternatively, if the lower bounds are updated along with the versions in the lock file, they end up duplicating the lock file’s role.

...however, there is no need to support older versions of dependencies, and testing in a matrix is often too resource-intensive. Consequently, there is little reason to test with older versions. If lower bounds are set, they often become arbitrary numbers that cannot be justified or guaranteed to work with the application...

Unfortunately these lower bounds are important for resolution purposes. For example, prevent one package from being downgraded to an unsupported version when another is upgraded. They're also not entirely devoid of meaning, e.g., updating your lower bounds on semver boundaries is normal and comes with a set of expectations.


basis set presentation

adding presentations from @b-v-henders and myself covering various basis set options

I'm disappointed in my additional commit from merging into my own master branch. Would I just have to manually squash my master branch to avoid this?

You could but I would be fine with it the way that it is. 2 commits is fine as long as its not like 10 haha


Added base styles

Changes proposed in this pull request:

Added base styles required for different components in the project.

Link to live demo: http://pr-182-evalai.surge.sh

Codecov Report

Merging #182 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #182   +/-   ##
=======================================
  Coverage   52.19%   52.19%
=======================================
  Files          60       60
  Lines        3148     3148
  Branches      367      367
=======================================
  Hits         1643     1643
  Misses       1421     1421
  Partials       84       84

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 99dc91a...b86b9b9. Read the comment docs.

@RishabhJain2018 @lunayach LGTM! :tada: Now it can be merged.

Thanks, @Sanji515 for verifying the changes!


Fix readme example (Fixes #5)

Changes made [In readme]:

Pass app from main.py to back_end.py to maintain singleton app
Fix indent in main.py

Fixes #5

Right, this fix #5 but you end up with a huge mega file. I think the back-end idea was to prevent this.

I cant see which file has substantially increased size in this edit? They have hardly changed wrt line no. count in any file.

I mean, BackEnd class will end up being really big. Maybe that was the idea of importing it from another file. Anyways, this fix is still a good option.

You could alternatively do back_end.app_gui=app from main.py and then it will be available as a global variable within back_end too - but usually you do have a main backend class which responds to different function calls.

I'm still trying to figure out a good pattern for solving this import inconsistency. The one you put in the pull request seems good. I want to see it there's anything else that can be done. If not, I'll merge this one.
PS. The back-end class shouldn't get really big. You can modularize back-end as per the application requirement and bind multiple modules to the GUI.

@amol-mandhane Just saw #5 then found this and the example now works. Merge ftw?

Fixed the example.


Error when using .over() in new version of polars 1.x

Thanks for this great tool!
I see that closed issue Get coefficients when using .over.
In April, the new version of polars-ols gave one method to run .over().
I tested the code shown in the issue. It indeed works on polars 0.x.
But recently polars published some new versions 1.x and made some changes.
When I run .over() with 1.x, for instance, 1.3.0, I receive the error message ComputeError: this expression cannot run in the group_by context shown below.

Any thoughts on this?

Apologies for the previous statement, it's not that there is a problem with the 1.x version as a whole; it's just that there is an issue with version 1.3.0. Version 1.2.1 still works normally. Perhaps it's a temporary bug introduced during the update, and I guess Polars might fix this issue later on.

Oh I see, thanks for documenting. Will keep an eye on if things work after 1.3 and otherwise will put a fix in and add a test for a modern version of polars (as haven’t looked at things for a while now)

Thank you for your reply and continued attention. I have noticed that Polars has recently been updated to version 1.4.1. I have tried the .over() function, and it works as expected.


click event doesn't trigger on mobile devices after binding v-close-popper directive

video:
https://github.com/Akryum/floating-vue/assets/21301288/f57cfd69-b2f5-47e5-a5ab-aaf5ebbf66d3
minimal reproduction: https://stackblitz.com/edit/vitejs-vite-ncpzhj?file=src%2FApp.vue

hello! i have the same issue :( have you find a solution? thanks

hello! i have the same issue :( have you find a solution? thanks

You can refer to: https://github.com/halo-dev/halo/tree/main/console/packages/components/src/components/dropdown

Hi I have the same issue


fix: disk input erase storage_id by backend

这个 PR 实现什么功能/修复什么问题:
修复: disk 转换成调度参数时根据 backend 去掉 storage_id
是否需要 backport 到之前的 release 分支:

release/2.8.0

/area region
/cc @wanyaoqi

Codecov Report

Merging #1104 into master will increase coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #1104      +/-   ##
=========================================
+ Coverage    7.87%   7.87%   +<.01%
=========================================
  Files         356     356
  Lines       56592   56592
=========================================
+ Hits         4456    4458       +2
+ Misses      51739   51738       -1
+ Partials      397     396       -1

Flag
Coverage Δ

#aFlag
7.87% <0%> (ø)
:arrow_up:

Impacted Files
Coverage Δ

pkg/compute/models/guests.go
0.73% <0%> (ø)
:arrow_up:

pkg/appsrv/response.go
69.23% <0%> (+3.07%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f25bbcd...94c4d67. Read the comment docs.

/lgtm
/approve


Unable to extract nsig function code

Checklist

[ ] I'm reporting a broken site support issue
[ ] I've verified that I'm running youtube-dl version 2021.12.17
[ ] I've checked that all provided URLs are alive and playable in a browser
[ ] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[ ] I've searched the bugtracker for similar bug reports including closed ones
[ ] I've read bugs section in FAQ

Verbose log

PASTE VERBOSE LOG HERE

Description

WRITE DESCRIPTION HERE
ERROR: Unable to extract nsig function code (caused by RegexNotFoundError(u'Unable to extract \x1b[0;34mInitial JS player n function name\x1b[0m; please report this issue on https://github.com/ytdl-org/youtube-dl/issues
It was fixed a couple weeks ago, then the same error is back again :-(
$ youtube-dl --version
2024.07.11

Why do you suppose there is a checklist in the issue template?


[node server] update response format

update response format to match the selenium version
return all tiles from nl response

thanks for update!


The type or namespace 'FixedBuffer' could not be found.

Can't seem to resolve a missing package or file.
I have tried:

Performing 'git pull' on each HouraiTeahouse repo.
Deleting "Temp" and "Library" in Unity project root and restarting my PC.
Restoring NuGet packages.

BackrollConnection.cs
Line 600 causing the build error.
Other lines with errors within file:

157 (directly related)
218
225 (related to FixedBuffer)

I strongly suggest using the Unity Package Manager version to fetch the dependencies. It should resolve any version mismatches that occur. This is likely occuring because you are pulling the HEAD of HouraiNetworking, HouraiCore, and Backroll, which may not be synchronized. I recently replaced FixedBuffer in HouraiCore with the standard System.(ReadOnly)Span, and had not updated Backroll to use it yet.
a77a996 should fix this if you are pulling from HEAD, but you will likely need to pull the updated dependencies via the Package Manager.


Missing variable declarations

I use to add "Option Explicit" to every module (module/cls/frm), and after I added it to stdHTTP I spotted this:

Not sure if you intended to:
a) leave them empty, as it currently does (without Option Explicit)
b) pass them as arguments
c) add them into the "info" Type (info.User and info.Pass)

For now I've set them to Empty - not sure they are required at all, but for now at least I've managed to use the class with them Empty anyway. It's possible that my intention was to allow them to be passed as arguments somehow... not sure.


RuntimeError: Performance Monitor must be activated

Hi Marius,
Currently if Performance monitor is not on, OptimusPy will try to get the RAM 4 times before generating the python error below:
Failed to retrieve RAM consumption. Waiting 15s before retry
Failed to retrieve RAM consumption. Waiting 15s before retry
Failed to retrieve RAM consumption. Waiting 15s before retry
Failed to retrieve RAM consumption. Waiting 15s before retry
Fatal error
Traceback (most recent call last):
  File "optimuspy.py", line 120, in main
    permutation_results += original_order.execute(reset_counter=True)
  File "C:\TM1py\optimus\executors.py", line 106, in execute
    return [self._evaluate_permutation(
  File "C:\TM1py\optimus\executors.py", line 69, in _evaluate_permutation
    ram_usage = self._retrieve_ram_usage()
  File "C:\TM1py\optimus\executors.py", line 92, in _retrieve_ram_usage
    raise RuntimeError("Performance Monitor must be activated")
RuntimeError: Performance Monitor must be activated

Screenshot below:

Instead of waiting for 4*15sec and generating an error, it would be great if OptimusPy could check first if the parameter PerformanceMonitor = True:

If it is not True, OptimusPy should not even start and just ends with a message like. OptimusPy requires PerformanceMonitor = True, please update the tm1s.cfg file before running OptimysPy again*
Cheers,
Vincent

We can't do that I'm afraid.
Some users may still use the Architect and turn on the PerformanceMonitor through right-click on the instance.
By waiting 15s we are essentially giving the user the opportunity to turn it on ad-hoc.

Wait can be helpful, but we should reword the message thrown. Something like Please check if Performance monitor is turned ON. Waiting 15s before retry can be more straight-forward.

I just recently learned that the PerformanceMonitorOn field in the config is "in sync" with the PerformanceMonitor configuration in good old Architect.
I think Optimus can simply activate it in the beginning and turn it back to pre-state when done.


Create a config object for the blaze client and allow HTTP/1.X parser configuration

closes #534
This PR was motivated by commit 05ad145. Each commit is relatively self contained

5693cb7: Add the BlazeClientConfig class to trim down the number of parameters passed around
05ad145: Add the ability to configure the blaze http1 parser for things like max header lengths
b7a79b2: unify the client ExecutorService management

:+1:, but I'd still like to figure out a solution to the connection managers, perhaps in another PR.


Can't run anima - project.gd broken

After trying to activate Anima in Godot, the editor says: "Can't activate Shape plugin, broken project.gd"

I think it is because I use Godot 3.4 and Ceccepa 3.3.4 as I saw in a Video

Having same issue.

@BenHerbst @middlepattern I just pushed a fix for this. Mind double-checking?

@ceceppa I did git pull and it works now. But the Visual Editor is too big scaled.
Screenshot:


Explore resurrecting the canvas prototype for flex context on-canvas target insertion + popup menu

experiments/insertion-plus-button-1

but instead of inserting an empty 50x50 div, the plus button should trigger the floating insert menu

I just realized there's some complexity: we need to be able to give a desired "child index" to the floating insert menu so that it inserts the child where the plus button was clicked, and not as last element


hGetBufSome: resource exhausted (Not enough space)

I'm getting an error trying to use pandoc-citeproc on a x64 Windows 7 system:
pandoc-citeproc --version

pandoc-citeproc 0.9

pandoc-citeproc --help

Usage: pandoc-citeproc [options] [file..]
-h         --help           show usage information
-V         --version        show program version
-y         --bib2yaml       convert bibliography to YAML
-j         --bib2json       convert bibliography to JSON
-f FORMAT  --format=FORMAT  bibliography format

pandoc-citeproc

pandoc-citeproc.exe: : hGetBufSome: resource exhausted (Not enough space)

pandoc --version

pandoc.exe <IP_ADDRESS>

I installed both pandoc and pandoc-citeproc with cabal install pandoc pandoc-citeproc.
I found a related issue on pandoc here: https://github.com/jgm/pandoc/issues/874
Any idea what could be causing this?
-update:
I'm positive this didn't work earlier:
pandoc essay.md -o essay.pdf --toc -N --filter pandoc-citeproc --csl style.csl
but now it does.
pandoc-citeproc
Still gives the same error.

So this arises if you do pandoc-citeproc with no arguments?  Do you then hit ^Z or does it immediately come up with the error?
jgm/pandoc#874 was solved by using strict instead of lazy IO.  So this might be a lazy IO issue.
If you look at Text.Pandoc.JSON in pandoc-types, you'll see that it uses lazy IO.  pandoc-citeproc uses this toJSONFilter function.
My guess is that replacing
BL.getContents >>=

in these instances with
((fromChunks . (:[])) <$> B.getContents) >>=

might solve it.

Does anyone else see this using pandoc-citeproc on Windows?  It would be good to get some idea of how widespread/reproducible the problem is.  Please give Windows version + archictecture, as well as pandoc-citeproc version.

It arises when I do pandoc-citeproc with no arguments, and it happens immediately without me doing anything.
I'm not sure how to test that change myself, but I'll update here if I figure out how.

+++ Stian Lågstad [Jan 17 16 04:00 ]:

It arises when I do pandoc-citeproc with no arguments, and it happens
immediately without me doing anything.
I'm not sure how to test that change myself, but I'll update here if I
figure out how.

If you want to try it, here's how.
Install stack for Windows.
https://github.com/commercialhaskell/stack/releases
Clone these repositories:  jgm/pandoc, jgm/texmath,
jgm/pandoc-types, jgm/pandoc-citeproc, in parallel
directories
Go into the pandoc directory and do
git submodule update --init

Now make the needed modifications in pandoc-citeproc (to
Text/Pandoc/JSON), and then go back to the pandoc directory
and do
stack install --install-ghc --stack-yaml=stack.full.yaml

Can someone who uses pandoc-citeproc on Windows confirm that the problem is fixed?
(Try the latest release, <IP_ADDRESS>; this is included in the pandoc binary package installer.)

Closing.  If the problem can be reproduced with the latest version, please open a new issue.


How can I range all of the beacons

I am using a library for android, and in them I don't need to set uuid for ranging, and it will range all of the devices
Is that possible with your library too?

That's not possible with iOS as it's a limitation of the underlying iOS SDK. Please see #31 for a thorough explanation.


Testing Duplex Streams

Is there a good way to test duplex streams (S: Read + Write) with this library? I could not really find a good way to do this, although that might be because of my unfamiliarity with rust.
A simple solution would be to provide an impl<R: Read> Read for PartialWrite<R> {...} which simply delegates to the inner reader. That way, you could simply wrap a stream in both a PartialRead and a PartialWrite. Analogously, there would be an impl<W: Write> Write for PartialRead<W> {...}.
Or there could be new wrapper structs PartialDuplex and PartialAsyncDuplex which would each maintain two separate lists of PartialOps, one for reads and one for writes.

I really like the first idea because it makes it clear what the operations list applies to. I'll see if I can put up a fix shortly. Thanks for reporting this!

Hey -- I've landed support for these and published version 0.2.3 -- could you give it a shot? Thanks!

Thanks for the fast update. It works (also with quickcheck) and suffices to express my use case.

Awesome, glad to hear that! :)


custom tip format

This implements a new format option for the tip mark that specifies how to format values. The option is specified as an object whose property names are channel names and whose values are formats; each format may either be a shorthand string for a number or time format, or a function that takes a channel value and zero-based index and returns the corresponding formatted string.
For example, to customize the number format of the x channel:
format: {x: ".2f"}

Equivalently:
format: {x: (d) => d.toFixed(2)}

To suppress a channel (similar to #1822), set the corresponding format to null:
format: {x: null}

As before, if you want the tip to display a paragraph of text, you can use the title channel; if you want to add additional name-value pairs to the tip, you can declare extra channels using the channels option; if you want to change the label, you can either change the corresponding channel or scale label. This PR improves the channels option slightly, allowing the label option to be declared alongside a channel #1734, and defaulting the channel label to its name when expressed as a shorthand string (e.g., channels: {Sport: "sport"} now uses the label “Sport” instead of “sport”.)
Lastly, the tip mark option now supports passing arbitrary options through to the derived tip mark, including the format option. The tip mark option also now takes a pointer option to control which pointer mode is used (x, y, or xy, for pointerX, pointerY, or pointer respectively).
Fixes #1612.
Fixes #1733.
Fixes #1734.

Love the API design.
color, opacity… can we have symbol too, maybe? :-)

Very exciting! Would it be possible to pass up the format option from other marks in the inferTip function? The first thing I tried to do was use a tip formatter with another mark where tip: true.
I think it would be a big win for new-ish users to be able to format their tips without ejecting from tip: true to adding another tip mark (might also make it easier to add the UI in the chart cell?).

Yes @mkfreeman; see the top description.

Does it make sense to put the swatch at the beginning of each line (to match legends)? Just wanted to compare:

Start
Middle
end

@mkfreeman I’m not changing the display functionality of tips in this PR; I’m just giving more control how the contents of the tip are specified. See #1767 for a more general issue, but feel free to open another issue if you want to suggest changes to the default design of tips.

@mbostock thanks, will take a look at that issue!

I’m wondering if I over-engineered this by adding the ability to derive anonymous channels as part of the format. I could do something that is more focused on just how the channels are formatted. For example, instead of this:
format: [{channel: "x", format: ".2f"}]

maybe you’d say:
format: {x: ".2f"}

and it wouldn’t change which channels were displayed, but it would change how the x channel is formatted (or perhaps how any channel bound to the x scale is formatted? not sure). And maybe you could suppress a channel by saying:
format: {x: ".2f", y: null}

I think that might be enough. 🤔

After much exploration, I’ve decided to pare this PR down to its essentials, focusing solely on formatting channel values and suppressing channels. The other functionality (declaring additional channels, and overriding labels) is already covered by the existing API, so I didn’t want to introduce a competing mechanism.

Great!! Besides the missing documentation, two minor (non-blocking) remarks:

I was tempted to say format: {x: true} to just use the standard format (for instance, when I wanted to revert {x: null}).

Looks like this enables to set the order of the fields by setting the order in the channels options, and possibly suppressing the corresponding standard channels. For example:

Plot.dot(penguins, {
  x: "body_mass_g",
  y: "culmen_length_mm",
  fill: "species",
  channels: {
    culmen_length_mm: "culmen_length_mm",
    species: { value: "species", label: "species", scale: "color" },
    body_mass_g: "body_mass_g"
  },
  tip: { format: { fill: null, culmen_length_mm: ".1f", x: null } }
}).plot()

results in the order (culmen_length_mm, species, body_mass_g)

I feel that this is a bit arbitrary and hacky (and also bad performance-wise). Since it's something that I think users will want to do anyways, it would be nicer to design this such that it followed the order given in the format instead. This would be an additional reason to support {x: true}, btw.

To expand my remark about symbols: it would be great to have a symbol (where there is a swatch) for channels that use the symbol scale. And the combo color+symbol should apply too. Again not a blocker, I can try to do this separately.

Let’s do the symbol swatch separately.
The order of channels is hard and not addressed in this PR. The formats are sparse and I think using “true” as a format is weird — that doesn’t work for a tickFormat, for example. I think channel order might need to be a separate PR or option too, but I’ll think about it today. (I’ve already spent a lot of time on this and want to move forward to other things for 1.0.)

I could change it to do whatever is listed in the format option first, followed by any remaining channels (in arbitrary order). That seems like a reasonable improvement although it might complicate the code some. We will see! I can probably address the improvement I mentioned above at the same time. But then I want to move on!

The format option now determines the order in which channels are shown, and you can set the format to true (or equivalently undefined) if you just want to use it to specify the order. I also added the optimization I described above to materialize the defaults, fixed a bug with facet settings (facet and facetAnchor) for the tip mark option, and removed the data pseudochannel.
Still need documentation and tests, I guess. Maybe that could be a followup PR? 😬

Is it supposed to work for default channels? I'm not able to suppress / reorder default those, only works for extra channels.

@dperetti Yes, it does. Please open a discussion here or in the Observable Forum if you’d like help, and please include a live code example to demonstrate. Thank you.

Thanks, finally got it! Turns out the channels were x and y, not the keys in the data object. This was too much convolution for my aging brain.


apt::key: puppetlabs-apt check now the full GPG fingerprints.

Since commit 531ef9 of puppetlabs-apt, the gpg key (apt::key) is
checked, and should use the long format.
This value is validated with a regex enforcing it to only contain valid
hexadecimal characters, be precisely 8 or 16 hexadecimal characters long
and optionally prefixed with 0x for key IDs, or 40 hexadecimal
characters long for key fingerprints.
https://github.com/puppetlabs/puppetlabs-apt/commit/f588f2651a68c5863aac7dac910d96bbc7531ef9
This patch fixes the puppet warning below:
Warning: /Apt_key[Add key: 7BD9BF62 from Apt::Source nginx]: The id should be a full fingerprint (40 characters), see README.

Excellent. Thanks!

I'm still getting a warning with the 16 character gpg key:

Warning: /Apt_key[Add key: ABF5BD827BD9BF62 from Apt::Source nginx]: The id should be a full fingerprint (40 characters), see README.
The fix is put in was to add the 40 character key instead of the 16 character key.

@errygg Ok. Great... misunderstood. Can you re-open and add tests then?

erf… sorry for that…


Extra white space is seen below review button when user comes back from scan QR code page to withdraw Amount page

Frequency : 100%
Repro on build version: Android Internal Release Build V:1.30.1 Android Playstore Build V:1.30.1
Repro on device : OnePlus 7t(11.0), Google Pixel 2XL(11.0)
Does not Repro on build : iOS Internal TestFlight Release Build V:1.30.1,iOS Appstore Build V:1.30.1
Does not Repro on device : iPhone 12(14.7.1), iPhone 13 mini(15.1.1)
Pre-condition:
1] User must have installed the application
2] User must have completed onboarding process
3] User must have funds in the account
4] User must be on CELO landing page
Repro Steps:
1] Click on Withdraw CELO
2] click on account address field
3] keyboard will be seen opened
4] now click on scan qr code
5] scan a wrong QR code and observe the withdraw CELO page
Bug : Extra white space is seen when user uses device back to come back to CELO withdrawal page
Expected Behavior : No extra space should be seen and review button should be seen on its original place
Investigation :

it works fine on iOS application as review button is seen on its original place

Impact : Bad user experience
Attachment : space.mp4

@ValoraQA a good first issue?


Adding All CNCF sites link to footer

Implemented as part of https://github.com/cncf/cncf.io/issues/715
Describe your changes
Adding "All CNCF Sites" button to the sites footer

Related issue number or link (ex: resolves #issue-number)
https://github.com/cncf/cncf.io/issues/715
Checklist before opening this PR (put x in the checkboxes)

[x] This PR does not contain plagiarism

don’t copy other people’s work unless you are quoting and contributing it to them.

[x] I have signed off on all commits

signing off (ex: git commit -s) is to affirm that commits comply DCO. If you are working locally, you could add an alias to your gitconfig by running git config --global alias.ci "commit -s".

@thetwopct Thanks!
Looks nice to me. :)
I think supporting localization for the button 'All CNCF Sites' would be nice. Could you help us on that?

I think supporting localization for the button 'All CNCF Sites' would be nice. Could you help us on that?

Sure. Added.


Added information to code sections on leasesTableName

Added information to code sections on leasesTableName

@JetterMcTedder - open a PR against azure-docs-pr instead, where you can also update the author field.  let me know via IM if you need access
#please-close


refactor: rollback to block and upgrade ckb deps

Codecov Report

Merging #56 (fd12466) into develop (10f712b) will increase coverage by 0.23%.
The diff coverage is 24.56%.

@@             Coverage Diff             @@
##           develop      #56      +/-   ##
===========================================
+ Coverage    33.09%   33.33%   +0.23%
===========================================
  Files           22       22
  Lines         3366     3354      -12
  Branches       467      465       -2
===========================================
+ Hits          1114     1118       +4
+ Misses        2137     2120      -17
- Partials       115      116       +1

Flag
Coverage Δ

unittests
33.33% <24.56%> (+0.23%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/protocols/filter/block_filter.rs
71.42% <ø> (ø)

...cols/light_client/components/send_block_samples.rs
43.86% <0.00%> (+0.45%)
:arrow_up:

src/protocols/light_client/mod.rs
0.00% <0.00%> (ø)

src/protocols/relayer.rs
0.00% <ø> (ø)

src/protocols/synchronizer.rs
0.00% <ø> (ø)

src/storage.rs
85.84% <82.35%> (-0.07%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Cross-student imports

Students should be able to import library projects (see #12) from other students.

I'm collapsing this into #12


CLOUDSTACK-6975: Prevent dnsmasq from starting on backup redundant RvR

Rebase of PR #1509 against the 4.7 branch as requested by @swill
One LGTM from @ustcweizhou carried from previous PR. Previous PR will be closed.
Description from PR #1509:
CLOUDSTACK-6975 refers to service monitoring bringing up dnsmasq but this is no-longer accurate, as service monitoring is not active on the post-4.6 routers. These routers still suffer an essentially identical issue, however, because "dnsmasq needs to be restarted each time configure.py is called in order to avoid lease problems." As such, dnsmasq is still running on backup RvRs, causing the issues described in CLOUDSTACK-6975.
This PR is based on a patch submitted by @ustcweizhou. The code now checks the redundant state of the router before restarting dnsmasq.
RvR networks without this patch have dnsmasq running on both master and backup routers. RvR networks with this patch have dnsmasq running on only the master router.

@dsclose would it be possible for you to enhance test/ntegration/component/test_redundant_router_services.py to verify that dnsmasq is only running on the master router and that dnsmasq properly starts on failover?

@jburwell - sure, I should be able to look at that this week. I'll investigate why the CI build failed as well.

@dsclose don't worry about the travis failure, it is due to a timeout.  Just do a force push to kick it off again and it will probably pass next time.  I will start a CI run on this now.  Thx...

CI RESULTS
Tests Run: 85
  Skipped: 0
   Failed: 1
   Errors: 0

Summary of the problem(s):
FAIL: test_03_vpc_privategw_restart_vpc_cleanup (integration.smoke.test_privategw_acl.TestPrivateGwACL)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/data/git/cs2/cloudstack/test/integration/smoke/test_privategw_acl.py", line 265, in test_03_vpc_privategw_restart_vpc_cleanup
    self.performVPCTests(vpc_off, True)
  File "/data/git/cs2/cloudstack/test/integration/smoke/test_privategw_acl.py", line 331, in performVPCTests
    self.check_pvt_gw_connectivity(vm1, public_ip_1, vm2.nic[0].ipaddress)
  File "/data/git/cs2/cloudstack/test/integration/smoke/test_privategw_acl.py", line 559, in check_pvt_gw_connectivity
    "Ping to outside world from VM should be successful"
AssertionError: Ping to outside world from VM should be successful
----------------------------------------------------------------------
Additional details in: /tmp/MarvinLogs/test_network_FCU6EL/results.txt

Associated Uploads
/tmp/MarvinLogs/DeployDataCenter__Apr_27_2016_06_55_22_XGXMQ6:

dc_entries.obj
failed_plus_exceptions.txt
runinfo.txt

/tmp/MarvinLogs/test_network_FCU6EL:

failed_plus_exceptions.txt
results.txt
runinfo.txt

/tmp/MarvinLogs/test_vpc_routers_3IQGOS:

failed_plus_exceptions.txt
results.txt
runinfo.txt

Uploads will be available until 2016-06-27 02:00:00 +0200 CEST
Comment created by upr comment.

The test that failed is one that periodically fails in my env, so I don't think we can assume it is related to this PR.

Good pr, let's ask comments from @remibergsma @DaanHoogland @wido and others?
tag:needlove

@rhtyd I'd love to. But I never used the Redundant VR, so I can't tell.

code looks good and functionally sane but this needs extensive testing. Especially when master fails the dns functionality needs to be still available, i.e. be started on the new master. @dsclose did you test this?

@DaanHoogland yes, the line CsHelper.service("dnsmasq", "restart") in set_master is in systemvm/patches/debian/config/opt/cloud/bin/cs/CsRedundant.py. When a backup router transitions to master, it successfully launches the dnsmasq service.
I should point out that I have only verified that the service is running. I have not confirmed that it is successfully configured.

LGTM. Tested in hardware lab and works as designed.
tag:mergeready

@dsclose can you force push or close and reopen the PR to kick off travis and jenkins again?  Thanks...

@dsclose we have pushed fixes to both Jenkins and Travis today.  Can you please do a force push or close and reopen this PR in order to kick off Jenkins and Travis again.  I think this one is pretty close...

@dsclose can you rebase and re-push this PR to try to get it green.  We are down to the wire now.  I will probably merge some PRs that only have jenkins failing if travis is passing, but I don't think I can make exceptions if both jenkins and travis are failing.

@dsclose can you please rebase and repush this one to kick off jenkins and travis again.  We have fixes in both travis and jenkins so we should be able to get this one green.  Thanks...

CI RESULTS
Tests Run: 85
  Skipped: 0
   Failed: 0
   Errors: 0
 Duration: 8h 44m 23s

Associated Uploads
/tmp/MarvinLogs/DeployDataCenter__May_20_2016_06_52_13_R81P2X:

dc_entries.obj
failed_plus_exceptions.txt
runinfo.txt

/tmp/MarvinLogs/test_network_YQPLQU:

failed_plus_exceptions.txt
results.txt
runinfo.txt

/tmp/MarvinLogs/test_vpc_routers_WA26EB:

failed_plus_exceptions.txt
results.txt
runinfo.txt

Uploads will be available until 2016-07-20 02:00:00 +0200 CEST
Comment created by upr comment.

This one is coming back clean.  If we can get Jenkins and Travis green I think this one is ready...

I would like to get this one re-pushed or closed and reopened so we can kick the CI again to see if we can get things green.  I am getting very close to freezing and this is one of the PRs on the edge.  Thanks...

@swill
Pardon me - I was on leave for a week. I'll get this force pushed momentarily.

@dsclose  you can close/reopen this PR instead.

@dsclose we install this patch in our environment(ACS 4.7.1, KVM) to solve the password issue with RVR.
We found the new password for VM is still incorrect unless we restart the password service manually. Should it be OK since we have destroy and rebuild VR ?

@luhaijiao I've seen the same error in our XenServer setup but wasn't sure what the cause is. I'd be surprised if this was the cause but it's worth exploring.
I will try to boot some system VMs now without this patch to see if the password server starts properly and then apply the patch to see if it subsequently fails. I'll report back here shortly.

@luhaijiao I reverted to a vanilla Cloudstack 4.8.0 ISO. The cloud-passwd-srvr service failed to start. The following appears in /var/log/messages on the router:
Password server failed with error code 1. Restarting it...
The same was true with this patch as well. In both cases, manually restarting the service (as the root user) was successful. I think we should treat the password server issue as separate and raise that elsewhere.
I'll kick off the tests again here.

This one is green.  I think this one is ready???  Please verify if there is anything outstanding on this one.  Thanks...  :)

@swill There is a question about enhanced integration testing but no code supplied so, tag:mergeready

@swill if you are happy to merge this without including the tests requested by @jburwell then this PR is ready to merge.
@luhaijiao I've created CLOUDSTACK-9385 to deal with the password server not running on redundant virtual routers. Please can you post your findings there if they do not match what I've described?


Adding button which push user from last top.

What feature?
button for direct push to top.
Show us the magic with screenshots
No response
Agreement to Code of Conduct

[X] I agree to follow this project's Code of Conduct

@Sushilverma002 I am assigning this task to you.


Refactor the pkg public API to improve organization.

The /pkg directory has a lot of top-level subdirectories which could perhaps be organized a little better.
pkg
├── api
├── auth
├── browser
├── cluster
├── cmd
├── color
├── common
│   ├── cmdutil
│   │    ├── arguments
│   │    ├── dump
│   │    ├── flags
│   │    ├── status
│   │    └── profile
│   └── errors
├── connection
│   ├── keycloak_connection
├── doc
├── httputil
├── iostreams
├── service
│   ├── kafka
│   │    ├── cmdutil
│   │    ├── consumergroup
│   │    └── topic
│   ├── serviceregistry
│   ├── serviceaccount
├── localize
│   ├── goi18n
│   ├── locales
└── logging

[Controversial] I think with multiple services we could additionally move service code out of pkg and use root folders for services.
My take could be
├── kafka-mgmt
├── kafka-instance
│   │    ├── cmdutil
│   │    ├── consumergroup
│   │    └── topic
|── serviceregistry-mgmt

pkg can still exist or we can have shared folder
shared
├── api
├── auth
├── browser
├── cluster
├── cmd
├── color
├── common
│   ├── cmdutil
│   │    ├── arguments
│   │    ├── dump
│   │    ├── flags
│   │    ├── status
│   │    └── profile
│   └── errors
├── connection
│   ├── keycloak_connection
├── doc
├── httputil
├── iostreams
├── serviceaccount
├── localize
│   ├── goi18n
│   ├── locales
└── logging

This will also let us refactor some of the key components of the CLI to be more scalable towards more services -
keycloak_connection
status
cluster etc.
Refactoring work on cluster commands is currently in progress but I feel that if we do this base refactor it will also help us to organize elements properly a

[Controversial] I think with multiple services we could additionally move service code out of pkg and use root folders for services.

What would be the benefit of this? I think the pkg/internal/cmd works well. The root folder is already busy with mostly non-Go code so there is a nice separation.

My take could be
├── kafka-mgmt
├── kafka-instance
│   │    ├── cmdutil
│   │    ├── consumergroup
│   │    └── topic
|── serviceregistry-mgmt
├── serviceregistry-instance

Suffixes like -mgmt and -instance make sense in SDKs, but the CLI never refers to these terms. So I'd like to avoid that.

pkg can still exist or we can have shared folder

pkg is more or less the norm in Go.

@craicoverflow This might require some context so maybe we could chat about it in the next occasion.
My take is that we cannot introduce full plugin architecture at start and we need to start with step in the middle by separating services in the folders that were suggested by Pete months ago. Once we do that and have solid shared library we can take some of the code out to apicurio CLI and also provide place for the teams to simply add their logic without us doing the work.

What would be the benefit of this? I think the pkg/internal/cmd works well. The root folder is already busy with mostly non-Go code so there is a nice separation.

Sure - multiple benefits.

Currently if you want to add service you need to be aware of the structure of the pkg.
Patterns and helpers are mixed. There is lots of common elements that are not documented and needed to be explored.

Yep and this proposal keeps services under pkg/service/{kafka,serviceregistry}.

We done POC with charmil exposing current helpers but challenge is to keep them up to date with changes in the cli.

Probably common helpers which are somewhat generic could move to Charmil and imported to the CLI?

As well there is a lot of elements that needs to be refactored in the CLI to enable multi service architecture.
3. Documenting services and reviewing it's codebase will be easier
4. Preparing set of commands to be extracted out of the CLI (after we nail share components) for registry and others.

What do you mean by extract them out? To where?

We can have example service that one can adapt for their needs (equivalent to charmil starter)

pkg is more or less the norm in Go.

We can keep pkg if you wish. The target here is to have clean separation per service (helpers) + shared elements that all CLI needs. Shared components can become future charmil or be SDK released with CLI that others can use. We can document those and keep their API consistent. Without that we do not have really good extensibility story and addition of every service/commands will require very deep knowledge of the CLI (even after you read all those guidelines it will be all about using helpers)

Suffixes like -mgmt and -instance make sense in SDKs, but the CLI never refers to these terms. So I'd like to avoid that.

Names are irrelevant for me. All we need is separation.
How about
pkg/shared
pkg/kafka ( cmd, utils etc.)
pkg/registry

I'm fine with this. I have been more or less suggesting the same thing only inverted - having the common components at the root and moving service packages under pkg/service.

What do you mean by extract them out? To where?

For example:
https://github.com/Apicurio/apicurio-cli

having the common components at the root and moving service packages under pkg/service.

I think that is not good as we going to see specific services leaking out to the cluster, status commands.
If we have shared/core/framework/sdk folder in pkg and be strict about this we can enforce some SDK breaking changes etc.
Good example of that is openshift with plugins and shared components/sdk
https://github.com/openshift/console/tree/master/frontend/packages

Yeah I'm fine with that.

Would that fit into reformating of the CLI/Improvements of the packages?

This is dev change. no epic but were already discussed and fine to fo


docker-engine installation fails due to conflict with docker package

Raising this more so that this is logged and reasons for https://github.com/CiscoCloud/microservices-infrastructure/commit/c61031951d03c714527093f4e6f7ced691fd5e01 and https://github.com/CiscoCloud/microservices-infrastructure/commit/aba8d2fde4ba69215e2f57a36a9136bb3f9c176a are captured.
During deployment the "install docker packages" task fails with the following error.
TASK: [docker | install docker packages] **************************************
failed: [<IP_ADDRESS>] => (item=docker-engine-1.7.0,docker-selinux) => {"changed": true, "item": "docker-engine-1.7.0,docker-selinux", "rc": 1, "results": [<snipped>]}
msg: Error: docker-engine conflicts with docker-1.7.1-108.el7.centos.x86_64

The use case where the OS provided docker package is pre-installed in the environment seems quite common. In my case, this was done so as to configure VM templates with specific docker-storage configurations.

Should this be supported from the project's perspective?
If so, would skipping this task if docker is already installed be sufficient? Or is there a need for using the docker-engine package from docker itself? ie., are there specific features that are leveraged that are not present in the OS packages? (Note: the OS package is 1.7.1 on CentOS 7.1).
If there is no need to use the docker repos, can we remove these tasks?

Happy to submit a PR, figured this is something that would require input from the maintainers. @BrianHicks maybe?

I think docker (the daemon/main project) was renamed to docker-engine at some point, which is why they conflict...
The way I think (reproducible builds), using thin/minimal CentOS images is the best way, because then mantl can behave the same across providers. Yhere are already some workarounds for different CentOS images, but in general that's a pretty big technical debt to manage. For example, how should it be automatically tested? (So the answer is no?) But then again, if docker-workarounds aren't supported in Mantl, that requires users of Mantl to have access to a clean CentOS image without Docker preinstalled. So if somebody only has thick CentOS bundles, that will be hard. Which cloud provider and image are you using? (At our place we use CentOS 7.0, not 7.1)

The package name 'docker-engine' seems to be only used by the docker upstream RPM repositories. Cannot find a reference for that in CentOS.
The problem here from my pov is introduced by the use of the Docker provided repositories (and hence the use of docker-engine-1.7.0 package) for installing the docker daemon, while this can be useful to get the bleeding edge, it often introduces more issues than it resolves. The CentOS packages in my experience has worked better than the ones put together by upstream.
With regards to technical debt, as an example, taking the following task into account, while this is fine for most cases; this overrides platform specific changes that may be required to run the daemon. The technical debt introduced by changes like these are more significant imho. This introduces https://github.com/docker/docker/issues/11135 into the deployment.
- name: create local docker service override
  sudo: yes
  copy:
    dest: /etc/systemd/system/docker.service.d/local.conf
    content: |
      [Service]
      EnvironmentFile=-/etc/sysconfig/docker
      ExecStart=
      ExecStart=/usr/bin/docker -d -H fd:// $other_arg
  notify:
    - reload docker
  tags:
    - docker

This should really be adding the following to the end of /etc/sysconfig/docker instead to achieve what it seems to be doing.
OPTIONS="${OPTIONS} --dns {{ private_ipv4 }} --dns-search service.{{ consul_dns_domain }} --log-driver=syslog"

The case that I ran into the issue was mainly because we wanted to set-up docker storage prior to deployment of MANTL. I suppose this can be made optional at the very least; to not rely on upstream provided packaging for docker. Might submit a PR for that as that might be less controversial.
As for the cloud provider; at the moment we are using on premise IaaS (oVirt) and AWS. For the former we use a clean CentOS 7.1 minimal but install docker and set-up storage so as to use device-mapper over loopback.
Trying to achieve reproducible builds (well as best as possible) across all platform versions and providers is hard task. To balance this with manlt behaving functionally equivalent across the versions, I'd recommend relying on the platform provided versions of docker daemon and other packages unless there is an obvious reason (eg: some feature that exists only in upstream). With Red Hat's current indulgence in docker, the docker package on CentOS should be relatively up-to-date and stable.

Just as a bit of context, we're using the upstream package because of a bug in the interaction between the CentOS packaged docker daemon and selinux that meant we couldn't mount volumes from the glusterfs mount.
Regarding the sysconfig file, I addressed it in docker/docker#15043, see the discussion there. The long and the short of it: they want people to use overrides. See docker/docker#15301 for the updated documentation. Since we don't want to package Docker ourselves (yet) we're going to comply with upstream's recommendation on how to fix the issue we had.
We'll review your PR, thanks for submitting it.

@BrianHicks thanks for the reply; that definitely puts things into context. Note that the -H fd://  in the current local.conf file will cause issues with CentOS 7.1. See docker/docker#11135.
Is there an issue open with Red Hat/CentOS for the SELinux issue? Oh, and +1 for not re-packaging.

It was actually an issue with Docker, not SELinux. Basically, it didn't know how to correctly request access to a different mount, even when the flag was correct specified. Just for visibility, would you mind opening a separate ticket about the -H fd:// issue please?

Ah; so I'd assume that using the CentOS docker-1.7.1 package should work.
Created #695 to capture the socket activation issue.

We're going to move back to the CentOS versions of Docker unless there are any objections.
@abn @eirslett

Closing as #803 has been merged.

fyi, until we get a new version of the image published, vagrant builds will fail with the docker-engine conflict. see #815


jdk-17 builds will not be reproducible if built with pre jdk-17.0.4 BootJDK

Reproducible jdk-17 builds depends on jdk-17.0.4 bootjdk otherwise jrt-fs.jar will not be identical.
We need to ensure boot jdk selection uses jdk-17.0.4

@andrew-m-leonard Has this been handled? I thought we had a PR in place to ensure we were building JDK17 with a suitable boot JDK now.

Yeah, this is implicitly fixed since we download the latest GA for jdk-17, hence get jdk-17.0.7 now.
@sxa


Where is Fablab Fribourg Eggbot Gcode sender

I cant find Fablab Fribourg Eggbot Gcode sender in any folder. How can I use it?

Just go to the releases page => https://github.com/fablab-fribourg/EggBot/releases


Expose command-line tags to the playbook

Proposal: export-tags
Author: Dag Wieers <@dagwieers> IRC: dag
Date: 2018-05-14

Status: New
Proposal type: core
Targeted Release: 2.7
Associated PR: <link to GH PR in ansible/proposals if PR was submitted>
Estimated time to implement: hours

Motivation
The provided tags can influence how the playbook behaves or is executed. As a result it is useful to have this information available.
Problems
We send out mails on failure (callback plugin) and send out a mail after successful execution of a complex playbook (mail module), but both do not report exactly with what tags the playbook was executed while this is a crucial part of understanding what has happened.
Exposing this information to the playbook makes it possible to report this information as part of the mail body together with other relevant information.
Solution proposal

Expose the used tags as ansible_tags

Testing (optional)
Tests are not optional
Documentation (optional)
Documentation is not optional.

3 things:

you already have ansible_only_tags and ansible_skip_tags to reflect such options
variables are not normally passed to callbacks
callbacks already have access to the cli options via self._options, when using CallbackBase

Thanks @bcoca

@bcoca I couldn't find this in the Ansible documentation, maybe I wasn't looking right. Do you know where this is documented ?


Make html-pdf dependency optional?

Hi,
The html-pdf dependency pulls in all of phantomjs which is IMO a bit heavy for deploying an API sdk. Would be great if that dependency wasn't a hard requirement as it's not needed for many use cases.

hmm, I figured it wasn't such a big deal with server installs, but I'll see if I can seperate the backup tool into a seperate package.


Clean fixes

Hello @samaloney! Thanks for submitting the PR.

In the file xrayvision/Clean.py, following are the PEP8 issues :

Line 198:101: E501 line too long (109 > 100 characters)


Run with another data

Hi, I want to run Merlin with my local language data. The problem is i have only .wav files and .data file.
May i please know the process of generating remaining required data. For example: for arctic data there is .lab files and folder merlin_baseline_practice. How to generate these files..?
Thanks and Regards
Giridhar

Hello,
to train with merlin you need the wav and corresponding text. Then, from the text to obtain the labs, you need a front end like festival or marytts. .data is something which is not standard so we actually don't know what it is representing.

If you have the wavs and text, you can follow the https://github.com/CSTR-Edinburgh/merlin/tree/master/egs/build_your_own_voice recipe to extract labels, and then build the voice.

Hi,
I have both wavs and text files. I followed build_your_own_voice and in label_normalisation I selected without time stamp option for labelling. So, my lab file looks like only one phoneme in each line. (No time stamp).
But, in duration modelling it is asking for timestamps. Is timestamps mandatory for duration modelling.?
If so, then why is it kept optional in label_normalisation.?
Please  help in this issue.
Thanks and regards
Giridhar.

Is timestamps mandatory for duration modelling.?

Yes

why is it kept optional in label_normalisation.?

For synthesis time you want: text->labels(w/o time stamps)->predict dur->predict acoustic feats.


wback subset01 implementation

Following tests are failing at the moment,

assign8-v.bal: This has an int array. Not sure whether arrays are in subset01.
add2-p.bal, div1-p.bal, div3-p.bal, rem1-p.bal: These tests are failing since they are throwing exceptions and exception handling is not implemented in from the WASM side yet.
rel-v.bal: This test fails due to it calling println function with a i32(boolean) value than a i64 which it expects.

Just for the record:
assign8-v.bal and rel-v.bal are there in the subset 1 by a mistake.
Need to fix p cases by throwing an exception. Any function that blows up wasm execution should work, no need to wait for exceptions proposal form wasm.

equal-v.bal failing: function return type set to any in this testcase.

Expression record type holds an array of tokens instead of a string. This tokens are later joined in creating the wat file. The sub types of Expression WasmBlock, WasmLoop, If and Break in the previous code were removed.


Zip files corrupted when downloaded from a docker volume

Bug description
Volume download works for plain text files, but if the file is a zip, somehow the downloaded one cannot be extracted by any zip tools.
Expected behavior
Zip files should be intact after download.
Steps to reproduce the issue:
Steps to reproduce the behavior:

create volume and abc.tar.gz file in it:
[vweng@bugatti ~]$ docker volume create test
test
[vweng@bugatti ~]$ docker run -d -it -v test:/test busybox
1dac573e7ef25406b26429c2d8c24b073709f08e8ac0204502ec0c195e5625e7
[vweng@bugatti ~]$ docker exec -it 1dac573e7ef2 sh
/ # cd test
/test # touch abc
/test # tar zcf abc.tar.gz abc
/test # ls -l
total 4
-rw-r--r--    1 root     root             0 Jan 28 16:46 abc
-rw-r--r--    1 root     root            86 Jan 28 16:47 abc.tar.gz

now go to portainer UI and find the volume "test" and download the abc.tar.gz from browser

try open the abc.tar.gz file:
$ tar zxf abc.tar.gz
tar: Unrecognized archive format
tar: Error exit delayed from previous errors.

Technical details:

Portainer version: 1.20.0
Docker version (managed by Portainer): 18.03.1-ce, build 9ee9f40
Platform (windows/linux): linux
Command used to start Portainer (docker run -p 9000:9000 portainer/portainer):
Browser: google chrome

Additional context
Add any other context about the problem here.

The same with mp3 files  Portainer-Agent: 1.2.1 , portainer 1.20.2


FEATURE REQUEST - make bar able to "execute" the downloads

Sorry, i know this is the best place for this.
The Feature Request is so that we can execute the downloads directly, instead of having to open the folder and then execute.
Thanks for your work.

already requested #14

Duplicate of #14


Select component does not propagate PromptOpts to survey

Bug description
When we use SelectConfig.Run(..) we should be able to pass PrompOpt.. as argument similar to PromptConfig. When we're not able to do this interactive testing for MultiSelect becomes impossible.
Expected behavior
To be able to pass PromptOpt to SelectConfig.Run(..)
Steps to reproduce the bug / Relevant debug output
Plugin Runtime version (also obtainable from tanzu <pluginName> info)
1.4.2
Environment where the bug was observed (cloud, OS, etc)
Local Development for a plug-in

I will prepare an MR that fixes the issue.


Run WMCore central services validation for HG2208

Impact of the new feature
WMCore central services
Is your feature request related to a problem? Please describe.
Monthly task
Describe the solution you'd like
Validate central services in cmsweb-testbed (well, it might have to be in one of our VMs due to the current Rucio setup) and provide the final feedback by the June deadline specified by the CMSWEB team.
It also includes the creation of the service release notes and the validation check-list twiki.
Describe alternatives you've considered
None
Additional context
None

Validation is completed and no issues have been found. Release 2.1.1.pre3 is ready to go to production. I have also just made a stable 2.1.1 release on top of it.
Release notes can be found at: https://github.com/dmwm/WMCore/releases/tag/2.1.1
Validation twiki: https://twiki.cern.ch/twiki/bin/view/CMS/WMAgentEndtoEndValidationHG2208
This new version is getting deployed in the coming Tuesday, Aug 9.
Closing this ticket.