can't access jra55 data

When I try
cc.querying.getvar(expt='MRI-JRA55-do-1-4-0', variable='uas',
                          session=session, frequency='3 hourly',
                          start_time='1957-12-31 22:30:00',
                          end_time='2019-01-05 22:30:00')

I get
---------------------------------------------------------------------------
KeyError                                  Traceback (most recent call last)
/g/data/hh5/public/apps/miniconda3/envs/analysis3-21.07/lib/python3.9/site-packages/xarray/backends/file_manager.py in _acquire_with_cache_info(self, needs_lock)
    198             try:
--> 199                 file = self._cache[self._key]
    200             except KeyError:

/g/data/hh5/public/apps/miniconda3/envs/analysis3-21.07/lib/python3.9/site-packages/xarray/backends/lru_cache.py in __getitem__(self, key)
     52         with self._lock:
---> 53             value = self._cache[key]
     54             self._cache.move_to_end(key)

KeyError: [<class 'netCDF4._netCDF4.Dataset'>, ('/g/data/ik11/inputs/JRA-55/MRI-JRA55-do/MRI-JRA55-do-1-4-0/atmos/uas/uas_input4MIPs_atmosphericState_OMIP_MRI-JRA55-do-1-4-0_gr_196501010000-196512312100.nc',), 'r', (('clobber', True), ('diskless', False), ('format', 'NETCDF4'), ('persist', False))]

During handling of the above exception, another exception occurred:

FileNotFoundError                         Traceback (most recent call last)
/jobfs/28073817.gadi-pbs/ipykernel_1224218/2750106142.py in <module>
----> 1 cc.querying.getvar(expt='MRI-JRA55-do-1-4-0', variable='uas',
      2                           session=session, frequency='3 hourly',
      3                           start_time='1957-12-31 22:30:00',
      4                           end_time='2019-01-05 22:30:00')

/g/data/hh5/public/apps/miniconda3/envs/analysis3-21.07/lib/python3.9/site-packages/cosima_cookbook/querying.py in getvar(expt, variable, session, ncfile, start_time, end_time, n, frequency, attrs, attrs_unique, **kwargs)
    230         return d[variables]
    231
--> 232     ds = xr.open_mfdataset(
    233         (str(f.NCFile.ncfile_path) for f in ncfiles),
    234         parallel=True,

/g/data/hh5/public/apps/miniconda3/envs/analysis3-21.07/lib/python3.9/site-packages/xarray/backends/api.py in open_mfdataset(paths, chunks, concat_dim, compat, preprocess, engine, data_vars, coords, combine, parallel, join, attrs_file, combine_attrs, **kwargs)
    919         # calling compute here will return the datasets/file_objs lists,
    920         # the underlying datasets will still be stored as dask arrays
--> 921         datasets, closers = dask.compute(datasets, closers)
    922
    923     # Combine all datasets, closing them in case of a ValueError

/g/data/hh5/public/apps/miniconda3/envs/analysis3-21.07/lib/python3.9/site-packages/dask/base.py in compute(*args, **kwargs)
    566         postcomputes.append(x.__dask_postcompute__())
    567
--> 568     results = schedule(dsk, keys, **kwargs)
    569     return repack([f(r, *a) for r, (f, a) in zip(results, postcomputes)])
    570

/g/data/hh5/public/apps/miniconda3/envs/analysis3-21.07/lib/python3.9/site-packages/dask/threaded.py in get(dsk, result, cache, num_workers, pool, **kwargs)
     77             pool = MultiprocessingPoolExecutor(pool)
     78
---> 79     results = get_async(
     80         pool.submit,
     81         pool._max_workers,

/g/data/hh5/public/apps/miniconda3/envs/analysis3-21.07/lib/python3.9/site-packages/dask/local.py in get_async(submit, num_workers, dsk, result, cache, get_id, rerun_exceptions_locally, pack_exception, raise_exception, callbacks, dumps, loads, chunksize, **kwargs)
    515                             _execute_task(task, data)  # Re-execute locally
    516                         else:
--> 517                             raise_exception(exc, tb)
    518                     res, worker_id = loads(res_info)
    519                     state["cache"][key] = res

/g/data/hh5/public/apps/miniconda3/envs/analysis3-21.07/lib/python3.9/site-packages/dask/local.py in reraise(exc, tb)
    323     if exc.__traceback__ is not tb:
    324         raise exc.with_traceback(tb)
--> 325     raise exc
    326
    327

/g/data/hh5/public/apps/miniconda3/envs/analysis3-21.07/lib/python3.9/site-packages/dask/local.py in execute_task(key, task_info, dumps, loads, get_id, pack_exception)
    221     try:
    222         task, data = loads(task_info)
--> 223         result = _execute_task(task, data)
    224         id = get_id()
    225         result = dumps((result, id))

/g/data/hh5/public/apps/miniconda3/envs/analysis3-21.07/lib/python3.9/site-packages/dask/core.py in _execute_task(arg, cache, dsk)
    119         # temporaries by their reference count and can execute certain
    120         # operations in-place.
--> 121         return func(*(_execute_task(a, cache) for a in args))
    122     elif not ishashable(arg):
    123         return arg

/g/data/hh5/public/apps/miniconda3/envs/analysis3-21.07/lib/python3.9/site-packages/dask/utils.py in apply(func, args, kwargs)
     33 def apply(func, args, kwargs=None):
     34     if kwargs:
---> 35         return func(*args, **kwargs)
     36     else:
     37         return func(*args)

/g/data/hh5/public/apps/miniconda3/envs/analysis3-21.07/lib/python3.9/site-packages/xarray/backends/api.py in open_dataset(filename_or_obj, engine, chunks, cache, decode_cf, mask_and_scale, decode_times, decode_timedelta, use_cftime, concat_characters, decode_coords, drop_variables, backend_kwargs, *args, **kwargs)
    495
    496     overwrite_encoded_chunks = kwargs.pop("overwrite_encoded_chunks", None)
--> 497     backend_ds = backend.open_dataset(
    498         filename_or_obj,
    499         drop_variables=drop_variables,

/g/data/hh5/public/apps/miniconda3/envs/analysis3-21.07/lib/python3.9/site-packages/xarray/backends/netCDF4_.py in open_dataset(self, filename_or_obj, mask_and_scale, decode_times, concat_characters, decode_coords, drop_variables, use_cftime, decode_timedelta, group, mode, format, clobber, diskless, persist, lock, autoclose)
    549
    550         filename_or_obj = _normalize_path(filename_or_obj)
--> 551         store = NetCDF4DataStore.open(
    552             filename_or_obj,
    553             mode=mode,

/g/data/hh5/public/apps/miniconda3/envs/analysis3-21.07/lib/python3.9/site-packages/xarray/backends/netCDF4_.py in open(cls, filename, mode, format, group, clobber, diskless, persist, lock, lock_maker, autoclose)
    378             netCDF4.Dataset, filename, mode=mode, kwargs=kwargs
    379         )
--> 380         return cls(manager, group=group, mode=mode, lock=lock, autoclose=autoclose)
    381
    382     def _acquire(self, needs_lock=True):

/g/data/hh5/public/apps/miniconda3/envs/analysis3-21.07/lib/python3.9/site-packages/xarray/backends/netCDF4_.py in __init__(self, manager, group, mode, lock, autoclose)
    326         self._group = group
    327         self._mode = mode
--> 328         self.format = self.ds.data_model
    329         self._filename = self.ds.filepath()
    330         self.is_remote = is_remote_uri(self._filename)

/g/data/hh5/public/apps/miniconda3/envs/analysis3-21.07/lib/python3.9/site-packages/xarray/backends/netCDF4_.py in ds(self)
    387     @property
    388     def ds(self):
--> 389         return self._acquire()
    390
    391     def open_store_variable(self, name, var):

/g/data/hh5/public/apps/miniconda3/envs/analysis3-21.07/lib/python3.9/site-packages/xarray/backends/netCDF4_.py in _acquire(self, needs_lock)
    381
    382     def _acquire(self, needs_lock=True):
--> 383         with self._manager.acquire_context(needs_lock) as root:
    384             ds = _nc4_require_group(root, self._group, self._mode)
    385         return ds

/g/data/hh5/public/apps/miniconda3/envs/analysis3-21.07/lib/python3.9/contextlib.py in __enter__(self)
    117         del self.args, self.kwds, self.func
    118         try:
--> 119             return next(self.gen)
    120         except StopIteration:
    121             raise RuntimeError("generator didn't yield") from None

/g/data/hh5/public/apps/miniconda3/envs/analysis3-21.07/lib/python3.9/site-packages/xarray/backends/file_manager.py in acquire_context(self, needs_lock)
    185     def acquire_context(self, needs_lock=True):
    186         """Context manager for acquiring a file."""
--> 187         file, cached = self._acquire_with_cache_info(needs_lock)
    188         try:
    189             yield file

/g/data/hh5/public/apps/miniconda3/envs/analysis3-21.07/lib/python3.9/site-packages/xarray/backends/file_manager.py in _acquire_with_cache_info(self, needs_lock)
    203                     kwargs = kwargs.copy()
    204                     kwargs["mode"] = self._mode
--> 205                 file = self._opener(*self._args, **kwargs)
    206                 if self._mode == "w":
    207                     # ensure file doesn't get overriden when opened again

src/netCDF4/_netCDF4.pyx in netCDF4._netCDF4.Dataset.__init__()

src/netCDF4/_netCDF4.pyx in netCDF4._netCDF4._ensure_nc_success()

FileNotFoundError: [Errno 2] No such file or directory: b'/g/data/ik11/inputs/JRA-55/MRI-JRA55-do/MRI-JRA55-do-1-4-0/atmos/uas/uas_input4MIPs_atmosphericState_OMIP_MRI-JRA55-do-1-4-0_gr_196501010000-196512312100.nc'

I don't have this problem when I access other data in ik11.

The weird thing is I don't have this issue. We are both using analysis3-21.07.
Fan is a member of ik11 and can see the file when he does
ls /g/data/ik11/inputs/JRA-55/MRI-JRA55-do/MRI-JRA55-do-1-4-0/atmos/uas/uas_input4MIPs_atmosphericState_OMIP_MRI-JRA55-do-1-4-0_gr_196501010000-196512312100.nc

I cloned /scratch/v45/hh0162/access-om2-iamip2/control/bgc-mdppm-run-01deg-iaf and ran it and (unsurprisingly) hit the same problem.
It appears to happen while loading dic:
 Initializing tracer number           6
  at time level tau. This tracer is called dic
 Reading restart for prog tracer dic from file csiro_bgc.res.nc

(I deleted my last post, which was meant for a different issue)

The data in there are symbolic links to the input4MIPs data in /g/data/qv56:
$ ls -l  /g/data/ik11/inputs/JRA-55/MRI-JRA55-do/MRI-JRA55-do-1-4-0/land/friver/*2019*
lrwxrwxrwx 1 aph502 ik11 178 Aug 21  2020 /g/data/ik11/inputs/JRA-55/MRI-JRA55-do/MRI-JRA55-do-1-4-0/land/friver/friver_input4MIPs_atmosphericState_OMIP_MRI-JRA55-do-1-4-0_gr_20190101-20190105.nc -> /g/data/qv56/replicas/input4MIPs/CMIP6/OMIP/MRI/MRI-JRA55-do-1-4-0/land/day/friver/gr/v20190429/friver_input4MIPs_atmosphericState_OMIP_MRI-JRA55-do-1-4-0_gr_20190101-20190105.nc

You need to go to my.nci.org.au and request membership to qv56
I have added a note that qv56 membership is required to access this data in the Notes in metadata.yaml

d'oh I should have noticed that - thanks @aidanheerdegen

The issue has been solved. Thanks @aidanheerdegen


Full suffix support

Renamed original "GetSuffix" function to "GetAbbSuffix"
GetSuffix now returns the full abbreviation as requested
#2

you removed the .__tostring method. add it back and we can merge


Fix safe core in ordered chunk pool

This commit fixes a bug introduced in this commit by the new batch_row_count related logic.
The root cause was that the adding an unversioned slice now relies on the fact that the current job is not larger than data_size_per_job, i.e. that the job was ended after adding the previous slice.
Meanwhile, the old logic that remained for versioned/unsplittable slices did things in the opposite order: we first checked the size of the current job and added the active slice next. So we would actually end the current job when adding the next slice after the one that hit the limit.
Obviously, these two approaches don't mix well :)
Primarily a problem arises when mixing sorted dynamic and static tables in ordered operations.
I decided to fix this twice:

I changed the order in AddUnsplittablePrimaryDataSlice to add the slice first and check the current job size later. Now all slice addition methods operate the same way, so everything is fine.
I added a safety fallback in AddSplittablePrimaryDataSlice that will end the current job if it is too large and reprocess the current slice.

I also addressed new post-commit comments from #423.

Shipped!


Better intersections + occlusion testing

Please don't merge this just yet, give me a day or three to think about it a bit more.
First part of the commits are pretty straight forward - rewrite + optimisation of IPolygon/IConvexPolygon, making the use of Intersects() and (now) Occludes() to be super efficient and require 0 GC. This also improves performance of load wrappers in scrolling containers - so should improve song select too.
Second part is adding occlusion testing, this is where comments would be helpful. With this PR, the framework now allows attaching IHasOccluder to an IDrawable object. This drawable will occlude any drawables that are rendered below it in the scene graph, regardless of nesting.
To do so, the drawable which has IHasOccluder attached to it writes to the IDrawable Occluder property.
The polygon used for occlusion will be the Occluder's polygon (not the polygon of the IHasOccluder).
The reason this is done is because there are few cases where the IHasOccluder itself is actually the occluder - consider ChatOverlay which has transparent tab background + an opaque inner background. In this case we would want the occluder to be the opaque inner background until the tabs are opaque themselves (at Height = 1), in which case the entire container should be the occluder).
Usage example can be found in https://github.com/ppy/osu/pull/751.

Also want to note that the way that I'm doing the "masking bounds" is wrong at the moment, I'm not quite sure how to deal with it yet.

Closing pending additional changes.


Fixes #258 : Server connection Error shows custom messages

This PR addresses #258
Now custom messages shows on server errors like:

Not connected to internet
Server doesn't exists on that URL
Text written there is not a valid URL

@timabbott @kunall17 Review and let me know if there any changes required. :)

Automated message from Dropbox CLA bot
@saketkumar95, it looks like you've already signed the Dropbox CLA. Thanks!

@kunall17 Review now.

@kunall17 Done! :)

@timabbott LGTM!

@saketkumar95 can you fix the merge conflict?

@timabbott Done! :)

I just cleaned this up and merged, but in the future @saketkumar95 please use git pull --rebase to resolve merge conflicts, not git pull -- Zulip as a project does not use merge commits.

@timabbott Yeah sure, Will keep check of it. Thanks :)

I guess while we're talking about this stuff, you may want to check out the Zulip commit message guidelines for details on how we like commit messages written: https://zulip.readthedocs.io/en/latest/version-control.html#commit-messages.  Usually I make everyone fix commit messages in the main project, though we've been a bit more lose about it in the Android app; but we should at least have regular contributors writing them using the standard style (our style is the same as for other major projects using Git like the Linux kernel).


RDK-37900 : Unit Tests for HdcpProfile and HdmiInput profiles.

Signed-off-by: Rajnish Dey<EMAIL_ADDRESS>(cherry picked from commit 5abc3a00346dc08a12c0ae49f7d16b9a50c3311f) (cherry picked from commit 2f28ea7ae30ecfe9ce2547ac0096f78b757549fd) (cherry picked from commit 2ed8167c09fe6af9721d7620991c1a37a1bd8363)

this was merged without addressing any of the requests asked in https://github.com/rdkcentral/rdkservices/pull/3243

remove unused DS declarations
fix HdcpProfile and HdmiInput reports in valgrind_log

@rajnishdey are you capable of fixing those

@npoltorapavlo
Fixed all the issues in the valgrind log that referenced HdcpProfile and HdmiInput in https://github.com/rdkcentral/rdkservices/pull/3319

valgrind_log looks good
I removed unused DS declarations along with reorganization #3325. There will be no longer headers folder to prevent from copy-paste files


Switch to Protolude 0.2.1.

Is this really an enhancement? This pulls in so many dependencies that compiling hpio requires two hours on the latest Raspberry Pi (and I can hardly utilize more than one core because that would hit the 1 GB RAM limit).

Protolude's dependencies are:
    build-depends:
    base                >= 4.6  && <4.13,
    array               >= 0.4  && <0.6,
    ghc-prim            >= 0.3  && <0.6,
    async               >= 2.0  && <2.3,
    deepseq             >= 1.3  && <1.5,
    containers          >= 0.5  && <0.7,
    hashable            >= 1.2  && <1.3,
    transformers        >= 0.2  && <0.6,
    text                >= 1.2  && <1.3,
    stm                 >= 2.4  && <2.6,
    bytestring          >= 0.10 && <0.11,
    mtl                 >= 2.1  && <2.3,
    mtl-compat          >= 0.2  && <0.3,
    transformers-compat >= 0.4  && <0.7

ref: https://github.com/sdiehl/protolude/blob/9d450cd9ff5d71f3db8f1e0532aa16fc3ea969e2/protolude.cabal#L68
As far as I can tell, using cabal-plan, all of protoludes dependencies are also used by at least one of hpios other dependencies.


Support uploading to remote host

Currently, this utility outputs files only to a local directory.
Should we consider adding a flag that allows the user to specify a URI to a remote FTP or SSH host?  Or might this be out of scope, and just leave it up to the user on what to do with the output?

Personally, I would not do this. There are myriad tools out there to rsync stuff to locations.

Agreed.  This utility should just do what it does without adding additional functionality that is already well-served by other tools.


Fix performance test result download

Description
This PR fixes the performance test results download.
The constructed URL for SMP results was malformed which was fixed in this PR.
Notes for Reviewers
golangci lint was failing in the previous PRs checks, this PR also attempts fix that issue.
Signed commits

[x] Yes, I signed my commits.

@NJnisarg, a good PR to review.

@NJnisarg, a good PR to review.


Is this a commercial product?

This repo/project is a bit confusing, you are using the MIT license and you have packaged sppkg files for 2016/2019 etc. and a source download with no source in it? Also I noticed after trying the 2019 package on my dev machine it has 'Trial Version' watermarked above the Kanban board. I think if this is a commercial product it should really be clearly stated on the front page and the releases page.
Overall it looks/works great and would work really well in a PnP Agile Project site template for example, but the fact it sends 'Telemetry' back and no source makes it a no go.
Edit--
Also just noticed.. It would also be worth letting people know on the front page it will not work without an internet connection, I noticed its pinging out for js files to azuredge.net even with telemetry off and will break with no internet access.

Thanks for your thoughts and suggestions. You're right the Agile Task Board is a commercial product, and we use this GitHub repo as a documentation and publishing channel for the software. I'll be making this clearer in the description in the near future and reviewing the license information to that effect.
Telemetry can be turned off for each board instance. Loading the artifacts via our CDN is recommended according to the Microsoft described procedure for developing SPFx Web Parts. If your company needs a version with an internal CDN, please contact me and we will discuss the requirements. We are specialized in customizing solutions for our customers.


added certificate to travis and enabled management tests for travis

@dpwspoon the build failed in management but for a different test(testServiceDefaultsWithSslCiphers) and doesn't seem related to my changes in this PR
Is it possible that the cause for the failure is because in the travis.yml I added sudo: required?(this changes the build machine from a container to a VM as far as I know)


Adding generic properties context stack to render context

Coverage increased (+0.002%) to 99.497% when pulling 97bede8e230e095bb86c29f085b5cdaef37e00c2 on lyncodev:master into 3a515b04f55caf679bae8e021bef8d1044344c90 on jtwig:master.


[google_identity_services_web] migrate to pkg:web

Required to support wasm compilation
Currently blocking migration of the Flutter Dashboard to Flutter wasm compilation

I wrote google_identity_services_web a long time ago, but with staticInterop and all that jazz, this shouldn't be using dart:html and friends. How can I verify that I've successfully written/migrated a package?

No, actually this required some pretty major revisiting :P
@kevmoo how do I run tests with dart2wasm?


RuntimeWarning: coroutine 'ConnectionHandler.hook_task' was never awaited   super().run_loop(self.loop.run)

Problem Description
This was mentioned in #4451 but not the focus of this issue. It just happened to me.
/mitmproxy/mitmproxy/tools/console/master.py:218: RuntimeWarning: coroutine 'ConnectionHandler.hook_task' was never awaited
  super().run_loop(self.loop.run)
RuntimeWarning: Enable tracemalloc to get the object allocation traceback

Steps to reproduce the behavior:
It happens occasionally when exiting mitmproxy via q + y
I'm not sure how to make it reproducible. Maybe you find the missing await :smile:
System Information
main branch on Ubuntu 20.04

There is no missing await here, this is a more tricky race condition unfortunately. We create a task here and schedule it to run on the event loop, but then the event loop is immediately shut down before the task gets a chance to be executed, which causes this error. We need to wait a bit with shutting down the event loop, but that's a not completely trivial project.

I see. If this can only happen during shutdown I don't think this is important at all, especially if the fix is non-trivial. It's somewhere at the bottom of my list  (it's actually basically falling of) :smile:
At least now people searching for it will find this.


Is this repository compatible with PyTorch 0.4？

You can try. If it's not compatible, it should be trivial to fix.


how to insert a mention programmatically

Hi, I have a button and a textarea and I want to insert a mention when I click the button. I tried something like this:
$('#text').data('atwho').controller('@').insert('someone');

but got an error:
Uncaught TypeError: Cannot read property 'el' of null
EditableController.insert @ jquery.atwho.js:688

Any suggestion?

When you click on a button, textarea will trigger a blur event, it will interrupt At.js's running context.
There is no way to do that as i know.


Thumbs Up and Down Button on Response Card similar to Azure AI Studio Chat Playground

Please implement Thumbs Up and Down Button on Response Card similar to Azure AI Studio Chat Playground.

We have implemented this on our local.  Please find attached the code.
FeedBackButton.zip
We have integrated this feedback with Application Insight (Code not shared here).
Please let us know how we can contribute back.


Add features to enable TLS support in aliri-oauth2 directly

Fixes #22
Users can specify whether to support TLS in aliri-oauth2 directly using the new features:

default-tls
rustls-tls

For example:
# No HTTPS Support
aliri_oauth2 = { version = "0.8", features = ["reqwest"] }

# HTTPS Support with OpenSSL
aliri_oauth2 = { version = "0.8", features = ["reqwest", "default-tls"] }

# HTTPS Support with Rustls
aliri_oauth2 = { version = "0.8", features = ["reqwest", "rustls-tls"] }

Any update on this? I have the same problem.

I'm in the middle of a move. From what I saw of the relevant PR, this looks good. I should be able to get this merged and a new release cut before the end of the week.

No hurries, :) I'll use the "work-around" meanwhile.


Add sample image

Expected Behavior
Should have sample typeset image on the read me.
Actual Behavior
No sample image.
Steps to Reproduce the Problem

Open: https://github.com/xgirma/latex-javaScript

## Specifications
(The version of the project, operating system, hardware etc.)

Sample added.


Parameterize url scheme

Defaults to textile-dev://, updated in env specific builds on CircleCI. Schemes are as follows:

production: textile
beta: textile-beta
dev: textile-dev

So, when you have an invite URL, you can choose with version of the app to open it with by editing the URL scheme accordingly.
Made an update where you can have a url with or without www. in it (important because our web page redirects to www.textile.photos then you may copy that url.

Ok all good here.


bacteriochlorophylls: please update CHEBI:60197 CHEBI:22686 structures

Hi Adnan,
Please could you update the structures of CHEBI:60197 and CHEBI:22686 accordingly to the other forms of bacteriochlorophyll (CHEBI:30033, CHEBI:189438) in order to have consistent data (in particular avoiding the use of bond type==any in CHEBI:60197).
Thank you for your support
Best regards, Anne

The structures have now been updated. There are several ways how these metal complexes can drawn.


linkapps and Spotlight issue

The brew linkapps no longer work with Spotlight. I just figured out why.
Spotlight only displays apps that are NOT symlinks. So instead of linking the dot app folder, brew should generate something like this, I guess
%> cat MacVim.app/Contents/MacOS/MacVim
#!/bin/bash

exec /usr/local/homebrew/bin/gvim "$@"

That works great for me.

I don't think linkapps ever worked with Spotlight.  This issue has been raised numerous times here, e.g:
https://github.com/Homebrew/legacy-homebrew/issues/28798
https://github.com/Homebrew/legacy-homebrew/issues/49033
https://github.com/Homebrew/legacy-homebrew/issues/45429
https://github.com/Homebrew/legacy-homebrew/issues/8970
https://github.com/Homebrew/legacy-homebrew/pull/35050
https://github.com/Homebrew/legacy-homebrew/issues/41238
Each time, as far as I can remember, HB decides not to do anything about it, because the maintainers decide that nothing reasonable can be done about it.

If you alias apps instead of symlinking, it works.

Please read the various issues before this; aliasing has its own issues.


ISPN-1642 Cache loading on remote nodes can be optimised away in certain...

... conditions
See https://issues.jboss.org/browse/ISPN-1642 and http://lists.jboss.org/pipermail/infinispan-dev/2011-December/009737.html

Sure! I was doing that anyway as I have a test to cover this.
Closing this to be replaced by new pull request.


Prediciton Almost flattened

Hello! Thank you for your well-structured code! I am currently doing some task using Informer. I used same network settings as ETTH dataset. But the output is not making sense to me. It is something like that:

Noticing the prediction is almost flattened. Do you have any thoughts about what could be the problem? I think maybe I should adjust the hyperparameters of the network? Do you have any suggestions about that? Thank you very much!

Thanks for your attention to our work, maybe you can increase the seq_len of model, and use multivariate prediction if data allows.


Docker::Error::ServerError: error parsing HTTP 400 response body: unexpected end of JSON input: ""

deployed 2 instances of the stack successfully, then on the third stack install + deploy:
TIME                      TYPE                      MESSAGE
2017-07-24T12:37:58.875Z  service:create_instance   pulling image registry.example.com/mystack/daemon:latest for mystack/daemon-1 (node-1)
2017-07-24T12:38:03.166Z  service:create_instance   unexpected error while creating mystack/daemon-1: error parsing HTTP 400 response body: unexpected end of JSON input: ""
 (node-1)
Deployment of service mygrid/mystack/daemon failed:
  - halting deploy of mygrid/mystack/daemon, one or more instances failed
  - GridServiceInstanceDeployer::ServiceError: Docker::Error::ServerError: error parsing HTTP 400 response body: unexpected end of JSON input: "" (on node node-1)

$ cat /etc/lsb-release
DISTRIB_ID="Container Linux by CoreOS"
DISTRIB_RELEASE=1409.7.0
DISTRIB_CODENAME="Ladybug"
DISTRIB_DESCRIPTION="Container Linux by CoreOS 1409.7.0 (Ladybug)"

$ docker -v
Docker version 1.12.6, build a82d35e

Anything interesting in journalctl -u docker.service from the same time?
Sounds like a Docker daemon error.

okay, resolved: repository didn't exist:
Jul 24 13:33:08 node-1 dockerd[992]: time="2017-07-24T13:33:08.766932539Z" level=error msg="Error trying v2 registry: error parsing HTTP 400 response body: unexpected end of JSON input: \"\""
Jul 24 13:33:08 node-1 dockerd[992]: time="2017-07-24T13:33:08.767477407Z" level=error msg="Attempting next endpoint for pull after error: error parsing HTTP 400 response body: unexpected end of JSON input: \"\""
Jul 24 13:33:08 node-1 dockerd[992]: time="2017-07-24T13:33:08.767703295Z" level=error msg="Handler for POST /v1.22/images/create returned error: error parsing HTTP 400 response body: unexpected end of JSON input: \"\""
Jul 24 13:33:09 node-1 dockerd[992]: time="2017-07-24T13:33:09.299070832Z" level=error msg="Error trying v2 registry: error parsing HTTP 400 response body: unexpected end of JSON input: \"\""
Jul 24 13:33:09 node-1 dockerd[992]: time="2017-07-24T13:33:09.299614815Z" level=error msg="Attempting next endpoint for pull after error: error parsing HTTP 400 response body: unexpected end of JSON input: \"\""
Jul 24 13:33:09 node-1 dockerd[992]: time="2017-07-24T13:33:09.299868935Z" level=error msg="Handler for POST /v1.22/images/create returned error: error parsing HTTP 400 response body: unexpected end of JSON input: \"\""
Jul 24 13:33:09 node-1 dockerd[992]: time="2017-07-24T13:33:09.804902465Z" level=error msg="Error trying v2 registry: error parsing HTTP 400 response body: unexpected end of JSON input: \"\""
Jul 24 13:33:09 node-1 dockerd[992]: time="2017-07-24T13:33:09.805444988Z" level=error msg="Attempting next endpoint for pull after error: error parsing HTTP 400 response body: unexpected end of JSON input: \"\""
Jul 24 13:33:09 node-1 dockerd[992]: time="2017-07-24T13:33:09.805663823Z" level=error msg="Handler for POST /v1.22/images/create returned error: error parsing HTTP 400 response body: unexpected end of JSON input: \"\""

Should this issue be closed or should the error handling be improved?

Based on those logs, it looks like the Docker::Image.create may have failed with raise Docker::Error::ServerError, 'error parsing HTTP 400 response body: unexpected end of JSON input: ""'. It looks like this isn't the agent docker API client getting an unexpected EOF from the local Docker daemon, but the Docker daemon getting a HTTP 400 response + unexpected EOF from the external image registry?
IOW: whatever registry you're pulling from seems to be broken?
The agent could perhaps give some better error with more context, like Docker server error while pulling image foo.io/bar: error parsing HTTP 400 response body: unexpected end of JSON input: ""'

yep. Heroku's container registry apparently returns "" if image not found

IMHO the error should be clarified since a response code "400" is truly misleading


Deprecation of async_register_entity_service

I got the following warning in my home assistant logs:
Detected that custom integration 'garmin_connect' registers an entity service with a non entity service schema which will stop working in HA Core 2025.9 at custom_components/garmin_connect/sensor.py, line 99: platform.async_register_entity_service(, please create a bug report at https://github.com/cyberjunky/home-assistant-garmin_connect/issues

It looks like it'll be almost a year before this is deprecated, but it should be on the roadmap.

Duplicate from issue/194. Please close the ticket.


Payment problem for reservations made  on testnet

For making payments on deployment made on https://deploy3bot.testnet.grid.tf/threebot_deployer/#/ , the 3bot_connect app gives destination account does not exists  error.
Please refer the following screen recording https://youtu.be/dnpBIZtSjtc

I checked the screen recording again, it seems you're using the 3bot connect app (for mainnet) and trying to pay on testnet with it?


[BUG] Doc meu highlighting feature dose not working properly

Description
Description
The documentation menu active page highlighting feature is not working. When I open the documentation menu, the active page is not highlighted. This makes it difficult to know which page I am currently viewing.
And also we can refactor some of the code and can enhance it further.
I would like to work on this issue if all sounds good.
Screenshots
Before
The highlighting function does not work properly.

After
After improvement and refactoring multiple lines of code.

Additional information
I would like to work on this issue if all sounds good.

Yes this feature was not implemented yet - I have assigned it to you @ashrafchowdury


Describe openscd-core architecture

As (potential) contributor/user
I would like to know how the software is structured
So I can understand how to make additions and/or the ways to use it.
Background
Create a diagram of current and future architecture. Also, important to have on the website.
Acceptance criteria:
Blocks of functionality
Description of the software blocks
Global interfaces between software blocks

@pascalwilbrink should we enhance the diagram on https://com-pas.github.io/compas-developers/? Or make a separate one for OpenSCD?

@pascalwilbrink We have a nice diagram now it does not comply with the acceptance criteria atm. The other two items still need to be done. Any ideas on that?

No Idea yet, if possible I would like to prevent double work.


Service Connection reference

I'm working on a custom extension, which includes custom tasks and a service connection. However, I am unable to find a reference section relating to defining a custom service connection. I was able to find some generic examples, but now a reference file of how to actually add inputs.
What am I missing?

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

ID: 90db6e4c-6240-fe2e-3043-0a7d186b9ca7
Version Independent ID: a62ec500-3330-e28a-8019-118a3b9e261f
Content: Create service endpoints - Azure DevOps
Content Source: docs/extend/develop/service-endpoints.md
Product: devops
Technology: devops-ecosystem
GitHub Login: @chcomley
Microsoft Alias: chcomley

@rcomanne Thanks for your question. We're treating it as a doc request, but for now, here are some resources:

Azure DevOps Services
Azure DevOps Support Bot
Azure DevOps on Stack Overflow

Hi @rcomanne, Sorry for the delay here, wondering if you're still experiencing this issue? Please let us know. Thanks so much.

Closing this GitHub Issue, however feel free to @mention me if this remains a challenge for you. Thanks!


Include headers files in cmake

Not having access to header files in the generated solution has been bothering me from the get-go. Though maybe not an issue if you're not working in visual studio like me - any thoughts?
(Also reordered the cpp files.)

Nevermind, realizing this is still missing the most important ones in inlude/OpenColorIO.  I'll revisit later. Should probably done cleanly with source_group instead.


Move SPA templates to latest framework versions (Angular 6, Node 10 etc)

Lets update our SPA templates to use the latest frameworks, and their accompanying best practices.

[x] Angular 6: ~1/2 day to 1 day
[x] React already at latest: 0
[x] ReactRedux redux 3 -> 5: ???
[x] Node 10 : ~ 1/2 day to 1 day
[ ] Upgrade/replace any other deprecated versions/packages: ~ 1/2 day to 1 day

I've included my rough estimates above based on some initial research. @SteveSandersonMS would probably know best if I'm way wrong or have missed any big ticket items.

The Angular work is represented here.

As per this conversation We've decided that we should not yet move to Node10 because it's not stable. That's a build-time dependency anyway.

We are already using "react.redux" 5.x, which as far as I can tell is usually paired with redux 3.x (4.x is only 3 months old).

All the items listed here are done. Any further items we discover we'll re-open or put in a different issue.


When I enable the gpu split,the inference result is unacceptable

When I enable the gpu split,the inference result is unacceptable.

Thank you for your feedback. Currently, we have received a bug issue with the GPU split sometimes not working properly, and we are investigating it.

This is certainly a bug that deserves special attention. If you don't mind, we would greatly appreciate your help in troubleshooting it!
Could you please share the GPU index file generated during this error? It should be located in the same directory as the model, named "[model_name].generated.gpuidx". This file contains no private data and will greatly assist us in reproducing and resolving the issue on our end. Thank you!

This is certainly a bug that deserves special attention. If you don't mind, we would greatly appreciate your help in troubleshooting it!
Could you please share the GPU index file generated during this error? It should be located in the same directory as the model, named "[model_name].generated.gpuidx". This file contains no private data and will greatly assist us in reproducing and resolving the issue on our end. Thank you!

Uploading falcon-40b-relu.q4.powerinfer.gguf.generated.zip…
Uploading llama-70b-relu.q4.powerinfer.gguf.generated.zip…

This is certainly a bug that deserves special attention. If you don't mind, we would greatly appreciate your help in troubleshooting it!
Could you please share the GPU index file generated during this error? It should be located in the same directory as the model, named "[model_name].generated.gpuidx". This file contains no private data and will greatly assist us in reproducing and resolving the issue on our end. Thank you!

falcon-40b-relu.q4.powerinfer.gguf.generated.zip
llama-70b-relu.q4.powerinfer.gguf.generated.zip

HUGE thanks for your cooperation! We will try to reproduce the bug with them and keep you updated!

@Gengchunsheng Would you mind re-testing on our most recent commit and see if there is a difference? We fixed a crucial bug under INT4 inference that I believe is closely related to this issue.
Please don't run with --reset-gpu-index so the program uses the previously generated GPU index file.

I git  pull the project and rebuilt it, the running results look normal now.


Updated .gitignore.

/sig multicluster

@gyliu513 This looks good overall, but I have one small comment.

/approve
/lgtm


Redtail Image Building Errors

Hello,

While building redtail image, there exists lots of errors, such as Failed building wheel for px4tools, Traceback error is related to no module named 'numpy' , some performings tests Failed, and so on (you may want to see images below) Also, when OpenCV modules to be built, there says OpenGL support: No for GUI.

After creating redtail container with run_redtail_docker.sh and before building components with ~/build_redtail.sh /data/src/redtail , do we need to install something else? (to unzip files and etc.)

When ~/build_redtail.sh /data/src/redtail, CMake Warning as follows:

Although the errors and failed tests, px4 node and gazebo runs. However, in the terminal for entering commander takeoff command, there produces lots of warning messages. Is that normal?

What should I do ?
Screen shots to see the errors while building redtail image:

Best regards, Ender.

The warnings that you see can be ignored.
As for build_redtail.sh script error, make sure you have provided full path to your redtail repo (e.g. in your case /data/src/redtail should exist and contain redtail GitHub code). As mentioned in the wiki, our Docker script does not automatically clone redtail repo to avoid unnecessary duplication of the code.
BTW, I've just updated redtail Docker file, the image build process should now be working fine. You don't have to do anything as you already built an image which seems to work.

Note that the command examples are just examples - you should always verify that such commands make sense for your machine/configuration. For example, you may have redtail sources in a directory other than /data/src/redtail.
As for joystick type: AFAIR, the button/axis mapping on XBox One is the same as on Shield so you can use default joystick type (shield) or try other types (supported: shield, xbox_wired, xbox_wireless, shield_2017). The only difference in all those types is button mapping.
Also, make sure you are passing correct joystick device to joy node (e.g. _dev:=/dev/input/js0). Depending on you machine, you may have more than one joystick device, for instance, some mouse devices also act as joystick.
As for the links: most likely you did not provide correct path to build_redtail.sh script. You should delete those broken symlinks and re-run the script again (see the script itself for more details on what it does).

MAVROS, Gazebo and QGroundControl are running well. I can use joystick either. Thank you!
Last but not least, I want to be sure If I did make a mistake at the beginning. I cloned redtail repo into Home directory. When creating container with respect to the explanation for default settings (container_name, host_dir and container_data_dir), I have just run run_redtail_docker.sh without defining any directory and container name. Afterwards, in the container, I have run ~/build_redtail.sh /data/src/redtail. Is that wrong?

As you said, it is because I of wrong path. I provided accessible path from the container. Everything is running now.
BTW, there are another broken links. Should I symlink each other or delete them ? as is seen below


Unit Testing Workshop

Here are my files for the unit testing workshop. I left out the circle test so that people can try it on their own before I show how I did it.

I'll review this weekend.


uv sync: project dev dependencies does not get installed

prior to uv 0.4.9, if i do uv sync in workspace, both dev-dependencies in worspace and project gets installed.  after uv 0.4.10+ uv sync in workspace removes project dev-dependencies
root workspace pyproject.yaml
[project]
name = "workspace"
version = "0.1.0"
dependencies = ["project"]

[tool.uv.sources]
project = { workspace = true }

[tool.uv.workspace]
members = ["project"]

[tool.uv]
package=false
dev-dependencies = [
    "coverage==7.5.3",
]

project pyproject.yaml
[project]
name = "project"
version = "0.1.0"
description = ""
dependencies = [
    ...
]

[tool.uv]
dev-dependencies = [
    "basedpyright==1.17.0"
]

[tools.uv]
package=false

[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"

[tool.hatch.build.targets.wheel]
packages = ["workspace"]

I believe this is related to modification https://github.com/astral-sh/uv/pull/7318.
The PR and its related issue should provide you with more details.
Please note that I am not a member of the UV team, so I can only provide PR that I believe are relevant for your reference. If you have any other ideas, I am not in a position to make decisions.

That sounds correct, thanks @FishAlchemist.
cc @charliermarsh

closing as a dupe of #7541.  thanks for the quick feedback guys


Running valgrind throws General Protection Fault on dl-misc.c

A brief description

Running make;valgrind ./tracegen -M 32 -N 32 -F 1 throws General Protection Fault while not on original Ubuntu 16.04.

Expected results: The command should pass without error
Actual results (with terminal output if applicable)

==742== Memcheck, a memory error detector
==742== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==742== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==742== Command: ./tracegen -M 32 -N 32 -F 1
==742==
==742==
==742== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==742==  General Protection Fault
==742==    at 0x40117B1: _dl_name_match_p (dl-misc.c:288)
==742==
==742== HEAP SUMMARY:
==742==     in use at exit: 0 bytes in 0 blocks
==742==   total heap usage: 2 allocs, 2 frees, 1,064 bytes allocated
==742==
==742== All heap blocks were freed -- no leaks are possible
==742==
==742== For counts of detected and suppressed errors, rerun with: -v
==742== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Segmentation fault (core dumped)

Your Windows build number

Insider build 14955

Steps / All commands required to reproduce the error from a brand new installation

Download and unzip https://1drv.ms/u/s!ArDhQNmhsUj02YdmxTJYPm69bWj4cg
make;valgrind ./tracegen -M 32 -N 32 -F 1
Check a segmentation fault happens

Strace of the failing command

https://gist.github.com/SaschaNaz/cdf4081a03ed13e97090862aff98dd28

Required packages and commands to install

sudo apt-get install valgrind

Hi @SaschaNaz -- thanks for reporting this!  It sounds like a specific instance of the issue discussed in #120 .  You might want to follow up there.  In particular, it would be interesting to know whether the workaround on that thread (compiling Valgrind from source rather than installing the Ubuntu binary version) works for you.

Hi @aseering, unfortunately installing from source doesn't work but generates a different error stack:
==23483== Memcheck, a memory error detector
==23483== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==23483== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info
==23483== Command: ./tracegen -M 32 -N 32 -F 1
==23483==
==23483==
==23483== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==23483==  General Protection Fault
==23483==    at 0x400A476: do_lookup_x (dl-lookup.c:423)
==23483==    by 0xFFEFFF247: ???
==23483==    by 0x400A94E: _dl_lookup_symbol_x (dl-lookup.c:829)
==23483==    by 0x2: ???
==23483==    by 0x403059F: ???
==23483==
==23483== HEAP SUMMARY:
==23483==     in use at exit: 0 bytes in 0 blocks
==23483==   total heap usage: 2 allocs, 2 frees, 1,064 bytes allocated
==23483==
==23483== All heap blocks were freed -- no leaks are possible
==23483==
==23483== For counts of detected and suppressed errors, rerun with: -v
==23483== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Segmentation fault (core dumped)

Thanks @SaschaNaz for the quick turnaround!  That error actually looks different to me; the previous error looked like Valgrind itself was segfaulting, this error looks like Valgrind is intercepting a segfault in your application.  That implies to me that it may have actually identified a bug in your application.
The stack trace is in some function that's performing dynamic loading.  My first guesses would be that you're either trying to find a symbol in a ".so" file that is corrupted in some way, or you have some other sort of buffer overflow (possibly on the stack so Valgrind wouldn't catch it?; also possibly a use-after-free() that, in this run, also occurs after the relevant block has been re-allocated so Valgrind wouldn't catch it as using un-allocated memory.  Could either of those be the case here?  (I admit, I haven't looked closely at your code; I figure you know more about it than I do.
Also -- do you know whether Valgrind runs this application correctly on a real Ubuntu Linux system?  I'm not sitting at one right now so I haven't checked.  But Valgrind basically runs your entire application in an emulated virtual environment; I have hit cases in the past where that emulation was not complete and, as a result, Valgrind failed to run a binary that worked just fine when running natively.

The code is a "cachelab" assignment template from CMU so I don't think there is any big issue. Yes, it runs well on original Ubuntu running on VM.

@SaschaNaz -- hm...  Yeah, I don't see anything wrong with that code.  I'm not sure what's going on here.  I'm just another WSL user; I think someone from the WSL team might know more?
For what it's worth, per #120 , Valgrind has been known to not work for a while now; my assumption is that it depends on some Linux kernel functionality that's somewhere in the WSL team's backlog.

I have a bug internally opened for this.

Hi @misenesi , do we know when there will be a fix for this, or if there is a work-around?

@Grauniad It is one of the items on my todo list, I am not sure yet when I get to it. If there is anyone more familiar with valgrind and could identify the source of the issue/difference between Ubuntu/WSL, I could get in the fix quicker.

Hi @misenesi , as per the investigation here: https://github.com/Grauniad/valgrind I'm fairly sure the issue is with the si_code being raised when a process attempts to access unmapped memory.
Logs / repro binary here: https://github.com/Grauniad/valgrind/tree/master/logs
I think #120 is the same issue.

@Grauniad thank you for your investigation, it is deeply appreciated! I have checked in a fix for this.


Is there a way control the interval between the animations?

Hi. First of all, congratulations for the library. It's very useful.
Could you tell me if there's a way to control the interval between the animation?
And/Or set the animation's duration?
I'm using in my app and (fortunately) the backend respond very quickly so very often it's not possible to see the animation even once...
Thanks in advance.

Hi @nglauber, thanks for using the library.
The animation can be altered by overriding the default theme. A good example can be found here: LoadingCardSample.kt
In your case overriding the animationSpec is probably sufficient. So maybe add the following right after you set the MaterialTheme in your application. Hope that helps. :)
private val shimmerTheme = defaultShimmerTheme.copy(
    animationSpec = infiniteRepeatable(
        animation = tween(
            durationMillis = 600,
            delayMillis = 200,
            easing = LinearEasing,
        ),
        repeatMode = RepeatMode.Restart,
    ),
)

@Composable
fun Sample() {
    MaterialTheme {
        CompositionLocalProvider(
            LocalShimmerTheme provides shimmerTheme
        ) {
            // Your content
        }
    }
}

Awesome! Worked like a charm ;)
Thanks and congratulations again!


Not loading EXDF transforms?

In the latest version, I have loaded an EXDF transform file, as seen below, but it does not load the transforms when booting FFXIV. Not sure what the issue is.

Is there anything printed about it in log window?

Here's the log window:

It works fine for me. Can you try deleting files in %appdata%\XivAlexander\Cached\ and try again? Also, share your runtime config json file.

I don't see a cache folder in either AppData\Local\XivAlexander or AppData\Roaming\XivAlexander.
Here is the json I'm using, although I also tested it with the json provided in the release download:
EnglishWithJapanese_SayQuestEnglish.txt
(GitHub won't let me upload json files so i changed the extension to .txt but it's the same content)

I mean the program configuration file that can be found in %appdata%\XivAlexander\config.runtime.json. It might be possible that something is disabling modding.

Here you go, from the Roaming folder:
config.runtime.txt
Again, had to convert it to .txt.

 Turn that on, and it should work.

OHH i forgot it was turned off by default in a new install lol.
 Anyway it works now, thanks.


Please Port GoogleTestAdapter into vcpkg

Library name: GoogleTestAdapter
Library description: Google test adapter. Can't run c++ unit tests in a sensible way without it.
Source repository URL: https://github.com/csoltenborn/GoogleTestAdapter

I don't think you want GoogleTestAdapter in vcpkg since GoogleTestAdapter is a Visual Studio Extension/Tool which you can simply install via the VS Extension Manager or the other ways mentioned on the github readme.
The library the extension uses is google test and that library is already in VCPKG as the port gtest

I was just looking for alternatives, since all the other options don't seem to work in our vs2019.sln

If you wish to add this port in the future, you can reopen this issue, but we're closing it for now.


gRPC server streaming: stream terminated by RST_STREAM with error code: NO_ERROR

Describe the bug
I have the following setup:
grpc client (local workstation) -> loadbalancer (digital ocean, TCP) -> ambassador (kubernetes cluster) -> grpc backend
Regular (non-streaming) grpc calls work just fine.  If I try to make a streaming call, the first time the server tries to send data back on it, I get the following error:
rpc error: code = Internal desc = stream terminated by RST_STREAM with error code: NO_ERROR

If I remove ambassador from the chain and send traffic directly from the loadbalancer to the backend, the server streaming rpc works just fine.
Expected behavior
Streaming RPC works properly.
Versions (please complete the following information):

Ambassador: Edge stack 1.10.0
Kubernetes environment: Digital Ocean
Version:  1.19.3-do.3

Additional context
Ambassador host config:
apiVersion: getambassador.io/v2
kind: Host
metadata:
  name: pepper-poker-grpc.wetsnow.com
  namespace: ambassador
spec:
  acmeProvider:
    email<EMAIL_ADDRESS>  requestPolicy:
    insecure:
      action: Reject
  hostname: pepper-poker-grpc.wetsnow.com
  tlsSecret:
    name: pepper-poker-grpc.wetsnow.com
---
apiVersion: getambassador.io/v2
kind: TLSContext
metadata:
  name: pepper-poker-grpc.wetsnow.com-context # for the host above
  namespace: ambassador
spec:
  hosts:
    - "pepper-poker-grpc.wetsnow.com"
  secret: pepper-poker-grpc.wetsnow.com
  alpn_protocols: h2,http/1.1 # required for C# grpc client

Ambassador mapping config:
apiVersion: getambassador.io/v2
kind: Mapping
metadata:
  name: pepper-poker-grpc-server-mapping
  namespace: ambassador
spec:
  prefix: /poker.PokerServer/
  rewrite: /poker.PokerServer/
  service: https://pepper-poker-grpc-service.poker:8443
  timeout_ms: 0 # required for streaming grpc
  grpc: True
  headers:
    :authority: pepper-poker-grpc.wetsnow.com
  resolver: endpoint
  load_balancer:
    policy: least_request

Ambassador global config:
apiVersion: getambassador.io/v2
kind: Module
metadata:
  name: ambassador
  namespace: ambassador
spec:
  config:
    use_proxy_proto: true
    envoy_log_type: json
    add_linkerd_headers: true

Note that I've tried turning off proxy proto (both in ambassador and loadbalanacer) and it didn't matter.  I tried to disable linkerd, and that didn't matter either.
Oddly enough though, this used to work a few weeks ago, unfortunately I am not sure what exactly changed to break it, since I didn't catch the break in time (this is just a toy project, so no proper monitoring or any real traffic).
No filters or policies for this host are enabled.
(Side question, when integrating with linkerd, should the linkerd sidecars be injected for the amabassador pods themselves?)
Thank you
Dan

Ok, so it looks like the problem here is the `timeout_ms' setting.
timeout_ms: 0

is supposed to disable the timeout, but it does not. Instead the timeout is the default 3000ms.  I see the connection dropping exactly 3 seconds after starting. I can set it to some other values and it properly waits that long.
Looks like this is a regression?

Hi, @DanTulovsky
can you try setting AMBASSADOR_LEGACY_MODE: true in the deployment env variables and see if that resolves the issue?

Yes, that does fix it.


dataset

where can download the dataset in you training script

I also met the issue. Can anyone fix the issue?


Don't trigger VDKQueue on the main thread

I pushed an updated version of VDKQueue to our fork (there was some movement in the Github Network).
Note that I don't think VDKQueue is responsible for our deadlocks 😉.

Nice. Running this in a test build…

Seems reasonable. To summarise the main VDKQueue changes:

Code cleanup
Switch to ARC
Add the ability to specify the GCD queue for notifications (which Etienne's made use of here)


App crashes on https call when on release mode using Android 19

Steps to Reproduce

Create a release apk and install on Android 19 (KitKat, 4.4).
Make a https call.

https://gist.github.com/IsaNascimento/ee9ceb743748079c43a6900c05abb211
Problem only happens on release mode and on Android 19 device (not sure if it happens on older versions of android, but it works fine on newer versions)
Logs
Analyzing https_test...
No issues found! (ran in 64.1s)

[✓] Flutter (Channel stable, v1.0.0, on Mac OS X 10.13.6 17G3025, locale pt-BR)
    • Flutter version 1.0.0 at /Users/isadora_maria/Downloads/flutter
    • Framework revision 5391447fae (8 weeks ago), 2018-11-29 19:41:26 -0800
    • Engine revision 7375a0f414
    • Dart version 2.1.0 (build 2.1.0-dev.9.4 f9ebf21297)

[✓] Android toolchain - develop for Android devices (Android SDK 28.0.3)
    • Android SDK at /Users/isadora_maria/Library/Android/sdk
    • Android NDK at /Users/isadora_maria/Library/Android/sdk/ndk-bundle
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.1, Build version 10B61
    • ios-deploy 1.9.4
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 27.1.1
    • Dart plugin version 173.4700
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)

[✓] Connected device (1 available)
    • Android SDK built for x86 • emulator-5554 • android-x86 • Android 7.0 (API 24) (emulator)

• No issues found!

Since I don't have Android KitKat device to retest this, although I created an emulator with api 19 (x86) and release mode isn't supported built for x86, I am unable to replicate this to check if issue persists or is resolved.
@IsaNascimento Is there a way for you to check if this is still an issue using latest Flutter version ?

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Unable to import lab 1903

I downloaded the MDLab_1903 as soon as it became available, but I've been unable to import it on two different host computers.
The setup wizard brings up an error "Unable to import virtual machine due to configuration errors. Please use Compare-VM to repair the Virtual Machine."
I used Compare-VM, and there were two incompatibilities listed

Cannot assign the specified number of processors for virtual machine 'HYD-CM1' is out of range. The range is 1 through 4. (Virtual machine ID 87B18423...
Cannot assign the specified number of processors for virtual machine 'BASE' is out of range. The range is 1 through 4. (Virtual machine ID BDEE123B-FD...

The computer i'm importing them on is an Intel Core i5-6500 CPU which is a quad core CPU.
Is there something wrong with the MDLab_1903 that's just been posted?

I was able to manually fix up the issue by:
Editing the file "..\HYD-CM1\Virtual Machines\87B18423-3A2F-4F25-AC94-3AA814032DE5.xml" and changing the 'count' value on line 833 down from 8 to 2.
Editing the file "..\HYD-CM1\Snapshots\BDEE123B-FD15-464E-95A0-BA854A882FB9.xml" and changing the 'count' value on line 836 down from 8 to 2.
Then import the VM using the Import-VM PoSH command.
I suspect anyone trying to run this lab on a Host PC that's unable to assign 8 vCPU's will run in to the same issue.


tw.forwardImage is not returnung the vector in simClassification.cpp

Hi Ahmed,
I am getting segmentation fault (core dumped).
So the code reaches all the way to the following line before segfaulting.
feat(0,i) = train1rep[i];
It segfaults here because train1rep was never initialized by tw. Problem is that tw.forwardImage is not returning the vector. I saw that the openface_server.lua never gets the path of temp_aligned.jpg properly.
Can you please tell me how to solve the issue.
Thanks
Mousmita

i am now facing the same problem....have you solved it ,i think it might because that the subprocess that runs the network do not work ....,by the way ,have you solved it ?

hi mousmita
now i am facing the same problem..i think it was because that the subprocess that runs the network does not work ...btw,have you solved it?

This seems like a path issue to the image - or maybe something deeper. Could you rest using new commits?


[MENFORCER-376] Add excludes/includes functionality to RequireJavaVendor rule

Following this checklist to help us incorporate your
contribution quickly and easily:

[x] Make sure there is a JIRA issue filed
for the change (usually before you start working on it).  Trivial changes like typos do not
require a JIRA issue.  Your pull request should address just this issue, without
pulling in other changes.
[x] Each commit in the pull request should have a meaningful subject line and body.
[x] Format the pull request title like [MENFORCER-XXX] - Fixes bug in ApproximateQuantiles,
where you replace MENFORCER-XXX with the appropriate JIRA issue. Best practice
is to use the JIRA issue title in the pull request title and in the first line of the
commit message.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Run mvn clean verify to make sure basic checks pass. A more thorough check will
be performed on your pull request automatically.

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

[x] I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004

[ ] In any other case, please file an Apache Individual Contributor License Agreement.

I still have one question, what should happen if I define a list of includes but current vendor doesn't satisfy this list? With this implementation it doesn't fail. However, it seem to be aligned with bannedPlugins rule, citing it:
includes - a list of plugin artifacts to include. These are exceptions to the excludes. It is meant to allow wide exclusion rules with wildcards and fine tune using includes. If nothing has been excluded, then the includes have no effect. In otherwords, includes only subtract from artifacts that matched an exclude rule.

That's the only question left so far.

I still have one question, what should happen if I define a list of includes but current vendor doesn't satisfy this list? With this implementation it doesn't fail. However, it seem to be aligned with bannedPlugins rule, citing it:
includes - a list of plugin artifacts to include. These are exceptions to the excludes. It is meant to allow wide exclusion rules with wildcards and fine tune using includes. If nothing has been excluded, then the includes have no effect. In otherwords, includes only subtract from artifacts that matched an exclude rule.

That's the only question left so far.

@rfscholte , @bmarwell , @elharo , can I kindly ask you to review MR again?

The docs that support this feature should be added in this PR as well.

@elharo , what exactly do you mean? I've already made corresponding changes in .apt.vm files. Is there something that should be updated too?

Yes, those changes should be in this PR too.

I may be silly but these changes ARE in the PR right now, still don't get what else should be done. Here is where changes are: https://github.com/apache/maven-enforcer/pull/86/files#diff-b2cfcc9c03ff6b43bade73782c36c14b900b63cb39f57bea78a40a6cf62ae259R33

@hboutemy , I see that you're also requested for a review, do you have any review comments?

Based on a discussion in JIRA ticket, this PR should be reworked to support either excludes or includes, not both at the same time.

This PR was the base for https://github.com/apache/maven-enforcer/commit/3b47fa9627bdf96a9fb45aac31c655bc6cae5060


On iOS devices, video's loaded in using iframe do not play when loading in a Wistia (fast.wistia.net) video until pressing the fullscreen button

[x] I have read the Get Started - Installation section
[x] I have read and done the Get Started - Setup Android section
[x] I have read and done the Get Started - Setup iOS section
[x] I have already searched for the same problem

Environment

Technology
Version

Flutter version
2.0.6

Plugin version
5.3.2

Android version
4.2+

iOS version
12.0+

Xcode version
13.1

Description
Expected behavior:
When loading in an iframe using Wistia, I expect to press play and the Wistia video should play like normal.
Current behavior:
When pressing play on iOS devices, the video does not play. Only when you first press on the fullscreen button, the video can be played. No errors are shown.
Steps to reproduce

Upload a video to Wistia (fast.wistia.net) and retrieve the iframe link to be loaded into the app using this in app web view library.
In the app, retrieve the iframe link and load it into an InAppWebView, filling in this link in initialUrlRequest.
Try to play the video on an iOS device. If it doesn't work, try pressing the fullscreen button to see if it will be playable after that.

Hello, I've got same problem, have you resoled it?

@mac102 nothing yet unfortunately..

Hi, thank you for reply.
I'm using 'native' flutter Webview plugin and figure it out yesterday afternoon that I'm missing:
allowsInlineMediaPlayback: true, initialMediaPlaybackPolicy: AutoMediaPlaybackPolicy.always_allow.
That solved my problem.

@mac102 @appcapsergen
This plugin has also these options:

set IOSInAppWebViewOptions.allowsInlineMediaPlayback with true
set InAppWebViewOptions.mediaPlaybackRequiresUserGesture with false


i18n(es): add github pages

What kind of changes does this PR include?

Translated content

Description

Adds github.md in spanish

Apart from two small comments I made (please leave as is or use the suggestions, as you wish!), LGTM

Good to merge! ✅

@kevinzunigacuellar @agustinmulet Thanks team! 🚀


Add release-manager-1.10 back as codeowners

Required after manually force syncing release-1.10 branch from envoyproxy/envoy main.

@Monkeyanator: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

test-release_envoy_release-1.10
e5d08098313034b811bef36af51b1f7d11f3e7c4
link
/test test-release_envoy_release-1.10

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Monkeyanator: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

test-release_envoy_release-1.10
e5d08098313034b811bef36af51b1f7d11f3e7c4
link
/test test-release_envoy_release-1.10

test-asan_envoy_release-1.10
e5d08098313034b811bef36af51b1f7d11f3e7c4
link
/test test-asan_envoy_release-1.10

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Monkeyanator: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

test-release_envoy_release-1.10
e5d08098313034b811bef36af51b1f7d11f3e7c4
link
/test test-release_envoy_release-1.10

test-asan_envoy_release-1.10
e5d08098313034b811bef36af51b1f7d11f3e7c4
link
/test test-asan_envoy_release-1.10

test-tsan_envoy_release-1.10
e5d08098313034b811bef36af51b1f7d11f3e7c4
link
/test test-tsan_envoy_release-1.10

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@Monkeyanator: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

test-release_envoy_release-1.10
e5d08098313034b811bef36af51b1f7d11f3e7c4
link
/test test-release_envoy_release-1.10

test-tsan_envoy_release-1.10
e5d08098313034b811bef36af51b1f7d11f3e7c4
link
/test test-tsan_envoy_release-1.10

test-asan_envoy_release-1.10
e5d08098313034b811bef36af51b1f7d11f3e7c4
link
/test test-asan_envoy_release-1.10

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Monkeyanator: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

test-release_envoy_release-1.10
e5d08098313034b811bef36af51b1f7d11f3e7c4
link
/test test-release_envoy_release-1.10

test-asan_envoy_release-1.10
e5d08098313034b811bef36af51b1f7d11f3e7c4
link
/test test-asan_envoy_release-1.10

test-tsan_envoy_release-1.10
e5d08098313034b811bef36af51b1f7d11f3e7c4
link
/test test-tsan_envoy_release-1.10

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Monkeyanator: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

test-asan_envoy_release-1.10
e5d08098313034b811bef36af51b1f7d11f3e7c4
link
/test test-asan_envoy_release-1.10

test-tsan_envoy_release-1.10
e5d08098313034b811bef36af51b1f7d11f3e7c4
link
/test test-tsan_envoy_release-1.10

test-release_envoy_release-1.10
e5d08098313034b811bef36af51b1f7d11f3e7c4
link
/test test-release_envoy_release-1.10

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Monkeyanator: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

test-asan_envoy_release-1.10
e5d08098313034b811bef36af51b1f7d11f3e7c4
link
/test test-asan_envoy_release-1.10

test-release_envoy_release-1.10
e5d08098313034b811bef36af51b1f7d11f3e7c4
link
/test test-release_envoy_release-1.10

test-tsan_envoy_release-1.10
e5d08098313034b811bef36af51b1f7d11f3e7c4
link
/test test-tsan_envoy_release-1.10

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Monkeyanator: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

test-release_envoy_release-1.10
e5d08098313034b811bef36af51b1f7d11f3e7c4
link
/test test-release_envoy_release-1.10

test-tsan_envoy_release-1.10
e5d08098313034b811bef36af51b1f7d11f3e7c4
link
/test test-tsan_envoy_release-1.10

test-asan_envoy_release-1.10
e5d08098313034b811bef36af51b1f7d11f3e7c4
link
/test test-asan_envoy_release-1.10

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Monkeyanator: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

test-tsan_envoy_release-1.10
e5d08098313034b811bef36af51b1f7d11f3e7c4
link
/test test-tsan_envoy_release-1.10

test-asan_envoy_release-1.10
e5d08098313034b811bef36af51b1f7d11f3e7c4
link
/test test-asan_envoy_release-1.10

test-release_envoy_release-1.10
e5d08098313034b811bef36af51b1f7d11f3e7c4
link
/test test-release_envoy_release-1.10

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Initialize state & make UI decisions

Initialize the application's state.
Decide what UI library to use, if not Bootstrap.


Repo lifecycle

As the project continues to grow and expand more repos are coming under the organization. It would be great to more formally define the lifecycle of repos under the project. We could take the work from Falco as an example. We should also consider how we handle forked repos.

Falco's repo lifecycle doesn't mention forks and it seems it's more targeted for "big projects" something that we would be expecting to see for things like hubble, tetragon, cilium-cli. However, we might need to define a process for smaller projects similar to https://github.com/cilium/scruffy, https://github.com/cilium/fake, and https://github.com/cilium/json-mock for example.

We should also add how handle experimental and unmaintained/archived repos.

Hi @xmulligan
I liked the lifecycle structure of falcosecurity
We can add more information about the repositories for better understanding of contributors

Handling folks will depend on the purpose of the folk , some folks are intended for personal exploration, contributing back to the original repository and alternative development or distribution. If the fork aims to become a separate project  with its own development and maintenance, the developer should treat it as a distinct entity from the original cilium repository. If the fork is simply for personal use or experimentation, there's no need for any specific governance.
We can only handle forks whose intentions are to contribute changes back to the original repository. It would be nice to place rules that fight against spam in pull requests  and misleading forks. Please , is there any thing else we should consider with forks ?

Something else that I think would help with this discussion is: What do we need beyond just having a maintainer create the repo? What expectations or obligations are there that we need to satisfy for any new repo (whether freshly created due to contributions within the Cilium organization, or as a fork from an external repo for Cilium organization usage).

Hello Everyone!
I would like to work on this issue as part of the LFX Mentorship.

Please apply through the platform https://mentorship.lfx.linuxfoundation.org/project/eeaec4a9-5a9c-4cae-945d-f99265e85275

Hi @xmulligan! I'm Abhay. First and foremost, the project is thriving. I have successfully applied to the mentorship program and completed all the pre-tasks. I am eagerly awaiting the opportunity to work with you, learn more about the projects, and delve into interesting challenges.

Hi there! I am Rudraksh, the project on Cilium governance documentation looks pretty interesting to me. While considering the points mentioned by @xmulligan @joestringer & @aanm. I performed a data analysis on the repos under Cilium project using Pandas. I came up with some figures with Cilium as:

I am looking forward to leveraging it further, to get more details about the individual projects which can help while defining lifecycle. While I found the Falco project repo lifecycle structure to be an excellent reference, I understand that we may need to make certain adjustments in the context of Cilium. I also came across CNCF governance templates which has been incredibly helpful in learning about governance in open source.
In the latest, review of Cilium governance the essence of contributor ladder was one of the major feedback/reviews by TOC, is this an aspect we should prioritize in the context of the Cilium governance project?

It might also be useful to include some guidelines https://github.com/istio/community/blob/master/ONBOARDING-TECH-TO-ISTIO.md


Upgrade the project to be compatible with react-navigation@3

In react-navigation@3, createNavigationContainer is not necessary anymore. Transisioner should be imported from react-navigation-stack.
This is a more completed merge request of #143
This also tries to resolve #139, #137, #135

Hi, @jarvisluong - thanks for submitting the PR! Really appreciate it. Have you tested it against version 2.X of react navigation as well, or do you think we should just upgrade and not be backwards compatible?

At least what I tested was that there are lots of warnings that will annoy people when they are still using react-navigation@2. We should make this not backward-compatible. The upgrades to react-navigation@3 is easy so it wouldn’t be a hassle @chrfalch

What I've done previously is to follow the versioning so that 0.2.x of Fluid Transitions is compatible with React Navigation 2.x, therefore Fluid Transitions 0.3.x should be for React Navigation 3. And then drop backwards compatibility.

Is this PR based on #143, or is #143 required first?

No I was just comparing what i did to what #143 did. There is no relation

When will be merge this pr ?

@jarvisluong do you need any support?

@jaulz sorry I couldn’t find free time at the moment, any helps are very appreciated!


DeprecationWarning: The redirect_output arguement is deprecated

This is a:
Question
OS: Ubuntu 18.04
Describe the Issue:
Hi, I am trying to run Tutorial03_rllib. Only minor adjustments to the Tutorial code is made and the following error was encountered:
Traceback (most recent call last):
File "stabilizing_the_ring.py", line 123, in
ray.init(num_cpus=N_CPUS, redirect_output=True)
File "/home/python/anaconda3/envs/flow/lib/python3.5/site-packages/ray/worker.py", line 1442, in init
_internal_config=_internal_config,
File "/home/python/anaconda3/envs/flow/lib/python3.5/site-packages/ray/parameter.py", line 148, in init
self._check_usage()
File "/home/python/anaconda3/envs/flow/lib/python3.5/site-packages/ray/parameter.py", line 198, in _check_usage
"The redirect_output argument is deprecated.")
DeprecationWarning: The redirect_output argument is deprecated.
I have attached my code if you would like to have a look. Any help would be appreciated.
Thanks.
stabilizing_the_ring_rllib.txt

Hi it worked after deleting  (redirect_output=True)
You may close the issue. Thanks.


Post-Install script incompatible with docker

We're using your library in our app that is running in a docker container. The post-install script relies on a .git file shouldn't be in our container.
><EMAIL_ADDRESS>postinstall /usr/src/app/node_modules/sweetalert2
> git ls-files dist | tr '\n' ' ' | xargs git update-index --assume-unchanged
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS>
Can you make this postinstall conditional so we can skip it for our usage please?

Hi @macpham and thank you for reporting this! Should be fixed in latest version.

Thanks for the quick fix @limonte 👍


Move repo-specific functions to repos module.

Also fix worker update dealing with existing source repo checkouts and deal
with repos with changed git URLs

LGTM


profile: Rework block-io CLI

Before this commit the profile block-io (biolatency) gadget needed
multiple iterations to get a result:
$ kubectl gadget profile block-io start --node worker-node
4b5501BrEjiw2GxG
$ kubectl gadget profile block-io stop 4b5501BrEjiw2GxG

This commit changes it to make it a "single execution" command printing
the results when Ctrl+C is hit:
$ kubectl gadget profile block-io --node worker-node
Tracing block device I/O... Hit Ctrl-C to end^C
Tracing block device I/O... Hit Ctrl-C to end.
 usecs               : count     distribution
     0 -> 1          : 0        |                                        |
     2 -> 3          : 0        |                                        |
     4 -> 7          : 0        |                                        |
     8 -> 15         : 0        |                                        |
    16 -> 31         : 0        |                                        |
    32 -> 63         : 6        |**********                              |
    64 -> 127        : 22       |****************************************|
   128 -> 255        : 9        |****************                        |
   256 -> 511        : 2        |***                                     |
   512 -> 1023       : 1        |*

It's  a RFC, what do you all think?
TODO:

[ ] Update documentation
[x] Update integration tests
[ ] Avoid printing  "Tracing block device I/O... Hit Ctrl-C to end" twice

I like the option to run block-io in one command. Does it work well with --request-timeout 10s? In that case, the user could use that without needing ctrl-c.
I am unsure about keeping the previous mode in 2 commands. If you manage to write the code without making it too complex, I think you can keep both modes.

Maybe we can have both modes but I fear this would add complexity...

I think it's too complex to have both modes.

I like the option to run block-io in one command. Does it work well with --request-timeout 10s? In that case, the user could use that without needing ctrl-c.

I just pushed a change to support timeout. I have forgotten about this.

I am unsure about keeping the previous mode in 2 commands. If you manage to write the code without making it too complex, I think you can keep both modes.

I think it's not only about code but about UX. I think it'll be very confusing to have two different ways to run the same gadget.

I think it's not only about code but about UX. I think it'll be very confusing to have two different ways to run the same gadget.

I see... I agree, I think your UX with a single command is better. Since it supports both interruption with ctrl-c or with the timeout, I think it is good.  And since the CRD interface is unchanged, Headlamp plugins could decide the UX they want independently.

Marking as ready for review as I completed the TODO items.


Installation error (Both OpenUPM and Manual Github)

When attempting both methods I get error after installing package:

Asset Packages/com.lachee.discordrpc/Runtime/DiscordRPC.xml has no meta file, but it's in an immutable folder. The asset will be ignored.

Asset Packages/com.lachee.discordrpc/Runtime/DiscordRPC.xml has no meta file, but it's in an immutable folder. The asset will be ignored.

they are warnings and dont effect anything.

I cannot make them go away from the error tab, do I just have to live with them?


Update README.md

Spent quite some time trying to figure out that those parameters aren't supposed to be passed to the recognize.sh as CLI parameters.

Hi! Thanks for contributing. This issue is already resolved in #2, so I am marking this as closed.


Support PUT calls for REST API

I've been able to use this great library to make actual changes to devices by making these alterations.
Should all be backwards compatible and I also added small unit test in line with existing.
My use case  - I wanted to programmatically control the LED on my UAP. Happy to share that code too in a separate PR.
Thanks for considering!

Not sure how I missed your PR. I see it now. Will work this in soon. Thank you!


After running "scons -j8 release=1 build" this command, gives an error as "unrecognized option : 'release' "

After running "scons -j8 release=1 build" this command, gives an error as "unrecognized option : 'release' "
OS - Ubuntu 14.04
I request to provide the solution

Can you say which directory you are running this in?

"cd earthenterprise/earth_enterprise" from this directory

OK. There was a recent change to the build process and it looks like you've hit a bug in that (or you possibly have an old checkout). Can you try it one level lower (in the src) directory? Then run the build again (without the release=1 part) in the earthenterprise/earth_enterprise before doing the install.
Also, can you check you don't have any spaces in the release=1  part?

Thanks. Actually I was using old repository.

Glad you got it going.


[FEATURE] Add whitelist for blocks that allow riding while the cart has them

Blocks like these would include things like pressure plates, carpets, slabs and buttons.
They could style the cart some more.
There may even be a way to apply multiple blocks in one cart, but only if some calculation is run to determine if they can all fit.

Added whitelist for the whole carts instead.


Refine Serial Handling

After a chat with the team on Google Meet, it seems like the data is not being picked up anyway - so we can treat this one as a bug too.

This can be considered fixed as the serial data handling is a separate component now. I will create a new issue for future things.


docs: fix CommonJS import syntax

A small improvement in the documentation, about the wrong CommonJS import syntax which will appear as a syntax error.

thanks for the PR. I wasn't careful enough to make this documentation


K8s operator for installation and configuration

Will go into another repo.
Placeholder task. To be completed with subtasks when we design it.
### Tasks

Closed as duplicate epic in https://github.com/orgs/grafana/projects/371/views/1


Buiding and using ChakraCore for UWP applications

I can't find instructions on how to build ChakraCore as a library for UWP and I am not sure whether is better to use the ChakraRT that is part of the UWP platform or build and embed your own.

Is the regular build UWP compatible or there is something that I am missing?

What are the differences between using ChakraCore from the OS vs embedding own version?
I know  that if I build my own, I will have to disable the JIT compiler. Does the ChakraCore in the OS JIT?

Hi @dimitarcl - just to be clear, the version that comes with the OS is not ChakraCore.dll but Chakra.dll- the former is the engine that is in this repo, the latter is not open-source, not cross-platform and is the engine that ships with Edge.
For UWP, it's probably better to use Chakra.dll that ships with the OS. ChakraCore.dll is not WACK compliant- it's not a lot of changes to get it to be compliant, but we just haven't gotten to it on our backlog (we welcome PRs here though). It also depends on whether you intend on calling WinRT APIs- since ChakraCore is cross-platform whereas the in-box Chakra.dll is not, ChakraCore also doesn't have support for projection of WinRT APIs into JavaScript.
Finally, the built-in Chakra.dll does support JIT. If you do end up using ChakraCore.dll, you can also have JIT enabled- however, that's one of the items that needs to be completed for WACK compliance (switch from using VirtualAlloc to VirtualAllocFromApp).

Thank you very much for the info.
@digitalinfinity Do you have a list of items that will be required for the WACK compliance?
I think in the long run we will prefer to have a single version of ChakraCore across all plaforms.

Thanks for your feedback- your interest in a single version of ChakraCore for all platforms has been noted.
Here is the list that I have from a couple months ago:
AddAtomW
CharLowerBuffW
CharUpperBuffW
CompareStringW
CreateFileW
DeleteAtom
ExitProcess
FindAtomW
FindResourceExW
GetDateFormatW
GetLocaleInfoW
GetModuleHandleExW
GetModuleHandleW
GetOEMCP
GetProcessIoCounters
GetStartupInfoW
GetTickCount
GetTimeFormatW
GetUserDefaultLCID
LCMapStringW
LoadLibraryExA
LoadLibraryExW
LoadResource
LockResource
QueryThreadCycleTime
RegCloseKey
RegGetValueW
RegOpenKeyExW
SetThreadStackGuarantee
SizeofResource
SystemFunction036
VirtualAlloc
VirtualProtect

In some cases (e.g CreateFile/VirtualAlloc) we need to switch to using the *FromApp variant of the API. For some of the localization related APIs, we could probably use ICU APIs (@jackhorton can confirm). The rest, we understand the usage but need to think through the right thing to do in the UWP context.
(cc @liminzhu)

Hi,
I have started the porting efforts and find several other functions  that need to be replaced for UWP for x86_64:

RtlVirtualUnwind
RtlCaptureContext
RtlAddFunctionTable
RtlDeleteFunctionTable

Do you have any suggestions how to address these?
So far I have got plan only for the RtlCaptureContext - to reimplement that in assembler as it is done for x86/arm.

@dimitarcl, thanks for your interest. Those APIs are not currently allowed by the Store but they should be added in a future update to the WACK Supported APIs check (sorry I can't give you exact timing).

Any update on this?


added clarity for URI vs ResourceID

which is more common elsewhere in Azure.

@omartin2010 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


etcd container stops working aproximately every 20-30 minutes

About every 20 minutes, the etcd container is restarted after the liveness probes fail:
etcdctl -endpoint=http://<IP_ADDRESS>:8001/ cluster-health gives:

member 9ca0c7938a0c3dc5 is unhealthy: got unhealthy result from http://<IP_ADDRESS>:8001
cluster is unavailable

ETCDCTL_API=3 etcdctl endpoint health --endpoints=localhost:8001 gives:

localhost:8001 is unhealthy: failed to commit proposal: context deadline exceeded
Error: unhealthy cluster

The etcd container is restarted seconds later by Openshift after the liveness probe fails.
Environment:

Openshift Enterprise 3.11
trident v19.04.1, etcd 3.3.12
trident PV is on Netapp ontap-nas, mounted over NFS v4.0

We see this happening since more than a month now and couldn't find a reason for this. I'm not sure if it started with update to v18.07.0 where liveness probes were included, or around the same time due to other reasons. It seems to happen
Any hints on how to proceed to further debug this?
 What version of Docker are you running?
I also suspect this is due to liveness probes and possibly related to https://access.redhat.com/solutions/3734981.
To confirm liveness probes are indeed the culprit, you can disable the liveness probes by following these steps:

Generate the deployment.yaml by running below command (This command will not install trident but only generate the yaml files under trident-installer/setup folder)–

root@scs:~/trident-installer# tridentctl install --generate-custom-yaml -n trident
INFO Wrote installation YAML files.                setupPath=/root/trident-installer/setup

Update the trident-deployment.yam’ file by removing following section:

root@scs:~/trident-installer# vi ~/trident-installer/setup/trident-deployment.yaml
[Remove the following from ‘etcd’]

        livenessProbe:
          exec:
            command:
            - etcdctl
            - -endpoint=http://<IP_ADDRESS>:8001/
            - cluster-health
          failureThreshold: 2
          initialDelaySeconds: 15
          periodSeconds: 15
          timeoutSeconds: 10

Re-install the trident with updated custom deployment.yaml by running follwoing command:

root@scs:~/trident-installer# tridentctl install --use-custom-yaml ~/trident-installer/setup/ trident-deployment.yaml -n trident

Hi @kangarlou,
Yes, sorry for not having specified this: I already verified, and the etcd container is indeed killed because of failing liveness probes.
But instead of deactivating those on the long run, I'd be interested in finding out why it is that etcd becomes unhealthy/unresponsive. I already added the --debug flag to the deploymentconfig, but it doesn't yield anyting interesting - just the livenessprobes' requests, followed by openshift's kill signal when it restarts the container:

2019-05-09 12:32:56.493411 D | etcdserver/api/v2http: [GET] /v2/members remote:<IP_ADDRESS>:33714
2019-05-09 12:32:56.494129 D | etcdserver/api/v2http: [GET] /health remote:<IP_ADDRESS>:33716
2019-05-09 12:33:11.485036 D | etcdserver/api/v2http: [GET] /v2/members remote:<IP_ADDRESS>:33758
2019-05-09 12:33:11.485838 D | etcdserver/api/v2http: [GET] /health remote:<IP_ADDRESS>:33760
2019-05-09 12:33:12.800702 N | pkg/osutil: received terminated signal, shutting down...

Please share the kubelet logs and the version of Docker you're running.

$ docker --version
Docker version 1.13.1, build 07f3374/1.13.1
(default version of RHEL 7)

$ oc get events -n trident-os1-prod
LAST SEEN   FIRST SEEN   COUNT     NAME                                        KIND      SUBOBJECT               TYPE      REASON      SOURCE                                    MESSAGE
16m         4h           28        trident-578788cd75-g8tt2.159cff2feebfa251   Pod       spec.containers{etcd}   Warning   Unhealthy   kubelet, $NODENAME   Liveness probe failed: member 9ca0c7938a0c3dc5 is unhealthy: got unhealthy result from http://<IP_ADDRESS>:8001
cluster is unavailable
15m       4h        17        trident-578788cd75-g8tt2.159cff3736e22941   Pod       spec.containers{etcd}   Normal    Killing   kubelet, $NODENAME   Killing container with id docker://etcd:Container failed liveness probe.. Container will be killed and recreated.

extract from journalctl -u atomic-openshift-node.service on the corresponding node:

May 09 18:10:27 $NODENAME atomic-openshift-node[13966]: I0509 18:10:27.495706   13966 prober.go:111] Liveness probe for "trident-578788cd75-g8tt2_trident-os1-prod(07b8e166-7249-11e9-ba9f-005056a65fe9):etcd" failed (failure): member 9ca0c7938a0c3dc5 is unhealthy: got unhealthy result from http://<IP_ADDRESS>:8001
May 09 18:10:42 $NODENAME atomic-openshift-node[13966]: I0509 18:10:42.497532   13966 prober.go:111] Liveness probe for "trident-578788cd75-g8tt2_trident-os1-prod(07b8e166-7249-11e9-ba9f-005056a65fe9):etcd" failed (failure): member 9ca0c7938a0c3dc5 is unhealthy: got unhealthy result from http://<IP_ADDRESS>:8001
May 09 18:10:42 $NODENAME atomic-openshift-node[13966]: I0509 18:10:42.497601   13966 kubelet.go:1898] SyncLoop (container unhealthy): "trident-578788cd75-g8tt2_trident-os1-prod(07b8e166-7249-11e9-ba9f-005056a65fe9)"
May 09 18:10:42 $NODENAME atomic-openshift-node[13966]: I0509 18:10:42.798655   13966 kuberuntime_manager.go:549] Container "etcd" ({"docker" "cc1da604fb844b60758a0b336a850643d6bb017fb400f42240c0b7592ca9dd0b"}) of pod trident-578788cd75-g8tt2_trident-os1-prod(07b8e166-7249-11e9-ba9f-005056a65fe9): Container failed liveness probe.. Container will be killed and recreated.
May 09 18:10:58 $NODENAME atomic-openshift-node[13966]: I0509 18:10:58.817587   13966 kuberuntime_manager.go:757] checking backoff for container "etcd" in pod "trident-578788cd75-g8tt2_trident-os1-prod(07b8e166-7249-11e9-ba9f-005056a65fe9)"
May 09 18:10:59 $NODENAME atomic-openshift-node[13966]: I0509 18:10:59.057130   13966 kubelet.go:1865] SyncLoop (PLEG): "trident-578788cd75-g8tt2_trident-os1-prod(07b8e166-7249-11e9-ba9f-005056a65fe9)", event: &pleg.PodLifecycleEvent{ID:"07b8e166-7249-11e9-ba9f-005056a65fe9", Type:"ContainerDied", Data:"cc1da604fb844b60758a0b336a850643d6bb017fb400f42240c0b7592ca9dd0b"}
May 09 18:10:59 $NODENAME atomic-openshift-node[13966]: I0509 18:10:59.057280   13966 kubelet.go:1865] SyncLoop (PLEG): "trident-578788cd75-g8tt2_trident-os1-prod(07b8e166-7249-11e9-ba9f-005056a65fe9)", event: &pleg.PodLifecycleEvent{ID:"07b8e166-7249-11e9-ba9f-005056a65fe9", Type:"ContainerStarted", Data:"3c1dffa4a41355653eadcc1682f6c94f843a771454e5ba50918864e06929f84e"}

This problem seems to be related to the node where this pod was scheduled on - I don't see this problem anymore since moving the pod to another host.
Closing for now, will update if I ever find the real reason for this.


Unknown shape on placeholder caused by tf.graph_util.convert_variables_to_constants

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Mac OS X 10.13.6
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
N/A
TensorFlow installed from (source or binary):
binary
TensorFlow version (use command below):
v1.10.0-rc1-19-g656e7a2b34 1.10.0
Python version:
Python 3.6.5
Bazel version (if compiling from source):
N/A
GCC/Compiler version (if compiling from source):
N/A
CUDA/cuDNN version:
N/A
GPU model and memory:
N/A
Exact command to reproduce:
N/A

Describe the problem
Placeholders with shape () gets shape <unknown> after tf.graph_util.convert_variables_to_constants has been run on a graph def.
The expected result is that the shape is kept, as it is for tensors with higher rank.
Source code / logs
import tensorflow as tf

with tf.Graph().as_default(), tf.Session() as sess:
    placeholder = tf.placeholder(tf.float32, shape=(), name='placeholder')
    output = tf.identity(placeholder)

    graph_def = tf.graph_util.convert_variables_to_constants(sess, sess.graph_def, [output.op.name])
    print('Before:', placeholder.shape)

with tf.Graph().as_default() as g, tf.Session() as sess:
    tf.import_graph_def(graph_def, name='')
    placeholder = g.get_tensor_by_name('placeholder:0')
    print('After:', placeholder.shape)

Output
Before: ()
After: <unknown>

@reedwm related to #21856?

As per I know Importing an old graphdef will trigger this behavior.


Timestamp format validation hardening

Thanks, @jwilk; this seems reasonable and an improvement. Are there any other PRs you plan on filing soon? If not, I can work on getting this into a small release.