Distribution Support Request

Details of the Distribution

Name of the Distribution:
Version of the Distribution:
Package Types

[x] Deb
[x] RPM
[x] Tar.gz
Snap - Please file issue in https://github.com/powershell/powershell-snap.  This issues type is unrelated to snap packages with a distribution neutral.

Processor Architecture (One per request):
[x] Required - An issues has been filed to create a Docker image in https://github.com/powershell/powershell-docker
The following is a requirement for supporting a distribution without exception.

[ ] The version and architecture of the Distribution is supported by .NET Core.

The following are requirements for supporting a distribution.
Please write a justification for any exception where these criteria are not met and
the PowerShell committee will review the request.

[x] The version of the Distribution is supported for at least one year.
[x] The version of the Distribution is not an interim release or equivalent.

Progress - For PowerShell Team ONLY

[x] Docker image created
[x] Docker image published
[x] Distribution tested
[x] Update packages.microsoft.com deployment
[x] Lifecycle updated
[x] Documentation Updated

Details of the Distribution

Name of the Distribution:
Version of the Distribution:
Package Types

[x] Deb
[x] RPM
[x] Tar.gz
Snap - Please file issue in https://github.com/powershell/powershell-snap.  This issues type is unrelated to snap packages with a distribution neutral.

Processor Architecture (One per request):
[x] Required - An issues has been filed to create a Docker image in https://github.com/powershell/powershell-docker
The following is a requirement for supporting a distribution without exception.

[ ] The version and architecture of the Distribution is supported by .NET Core.

The following are requirements for supporting a distribution.
Please write a justification for any exception where these criteria are not met and
the PowerShell committee will review the request.

[x] The version of the Distribution is supported for at least one year.
[x] The version of the Distribution is not an interim release or equivalent.

Progress - For PowerShell Team ONLY

[x] Docker image created
[x] Docker image published
[x] Distribution tested
[x] Update packages.microsoft.com deployment
[x] Lifecycle updated
[x] Documentation Updated

Closing due to lack of information.


Implement prEN1992-1-1 shear resistance formula

For now, this is put on hold due to the surprising VRmin values.

Closing this pull request without merge as part of the cleaning up of the repo (deleting branches). The only valuable and potentially useful code from this PR (prEN resistance formula implementation) is salvaged in this gist:
https://gist.github.com/rozsasarpi/eb5aa2eb441c11e59dff3b26626160dc


Databroker can't read Eiger images

We can't read Eiger images under 'Collection'
In [65]: hdr = db[-1]

In [66]: hdr
Out[66]:
{'descriptors': [{'data_keys': {'eiger_4M_cam_img_acquire_period': {'dtype': 'number',
     'shape': [],
     'source': 'PV:XF:11IDB-BI{Det:Eig4M}cam1:AcquirePeriod_RBV'},
    'eiger_4M_cam_img_acquire_time': {'dtype': 'number',
     'shape': [],
     'source': 'PV:XF:11IDB-BI{Det:Eig4M}cam1:AcquireTime_RBV'},
    'eiger_4M_cam_img_image_lightfield': {'dtype': 'array',
     'external': 'FILESTORE:',
     'shape': [2167, 2070],
     'source': 'PV:XF:11IDB-BI{Det:Eig4M}'},
    'eiger_4M_cam_img_stats_total1': {'dtype': 'number',
     'shape': [],
     'source': 'PV:XF:11IDB-BI{Det:Eig4M}Stats1:Total_RBV'},
    'eiger_4M_cam_img_stats_total2': {'dtype': 'number',
     'shape': [],
     'source': 'PV:XF:11IDB-BI{Det:Eig4M}Stats2:Total_RBV'},
    'eiger_4M_cam_img_stats_total3': {'dtype': 'number',
     'shape': [],
     'source': 'PV:XF:11IDB-BI{Det:Eig4M}Stats3:Total_RBV'},
    'eiger_4M_cam_img_stats_total4': {'dtype': 'number',
     'shape': [],
     'source': 'PV:XF:11IDB-BI{Det:Eig4M}Stats4:Total_RBV'},
    'eiger_4M_cam_img_stats_total5': {'dtype': 'number',
     'shape': [],
     'source': 'PV:XF:11IDB-BI{Det:Eig4M}Stats5:Total_RBV'},
    'eiger_4M_cam_imgsequenceid': {'dtype': 'number',
     'shape': [],
     'source': 'PV:XF:11IDB-BI{Det:Eig4M}cam1:SequenceId'}},
   'run_start': '574bb68b-f493-4f45-bd6e-fabc66c6f894',
   'time':<PHONE_NUMBER>.1088412,
   'uid': '4ae706a4-3355-4b30-a866-c8779b3e9d9a'}],
 'start': {'beamline_id': 'CHX',
  'config': {},
  'group': 'chx',
  'owner': 'xf11id',
  'project': 'Undulator spectrum studies',
  'sample': {},
  'scan_args': {'delay': '0',
   'detectors': "[AreaDetectorFileStoreEiger(name='eiger_4M_cam_img', basename='XF:11IDB-BI{Det:Eig4M}', stats=range(1, 6), shutter=None, shutter_rb=None, shutter_val=None, file_path='/XF11ID/data/', ioc_file_path=None)]",
   'num': '1'},
  'scan_id': 289,
  'scan_type': 'Count',
  'time':<PHONE_NUMBER>.0575428,
  'uid': '574bb68b-f493-4f45-bd6e-fabc66c6f894'},
 'stop': {'exit_status': 'success',
  'reason': '',
  'run_start': '574bb68b-f493-4f45-bd6e-fabc66c6f894',
  'time':<PHONE_NUMBER>.1293712,
  'uid': 'e39e559e-57e8-4883-9fb4-adb8d7742596'}}

In [67]: img = get_images( hdr, 'eiger_4M_cam_img_image_lightfield' )
---------------------------------------------------------------------------
KeyError                                  Traceback (most recent call last)
<ipython-input-67-a307ab930b8b> in <module>()
----> 1 img = get_images( hdr, 'eiger_4M_cam_img_image_lightfield' )

/opt/conda_envs/collection/lib/python3.4/site-packages/databroker-0.3.0-py3.4.egg/databroker/pims_readers.py in get_images(headers, name)
     23             # do something
     24     """
---> 25     return Images(headers, name)
     26
     27

/opt/conda_envs/collection/lib/python3.4/site-packages/databroker-0.3.0-py3.4.egg/databroker/pims_readers.py in __init__(self, headers, name)
     47         self._datum_uids = [event.data[name] for event in events]
     48         self._len = len(self._datum_uids)
---> 49         example_frame = retrieve(self._datum_uids[0])
     50         self._dtype = example_frame.dtype
     51         self._shape = example_frame.shape

/opt/conda_envs/collection/lib/python3.4/site-packages/filestore/commands.py in inner(*args, **kwargs)
     19         port = int(conf.connection_config['port'])
     20         db_connect(database=database, host=host, port=port)
---> 21         return func(*args, **kwargs)
     22     return inner
     23

/opt/conda_envs/collection/lib/python3.4/site-packages/filestore/commands.py in retrieve(eid)
    136         The requested data as a numpy array
    137     """
--> 138     return _get_data(eid)

/opt/conda_envs/collection/lib/python3.4/site-packages/filestore/retrieve.py in get_data(eid, handle_registry)
    261                         "datum cache can hold.")
    262
--> 263     handler = get_spec_handler(datum['resource'], handle_registry)
    264     return handler(**datum['datum_kwargs'])

/opt/conda_envs/collection/lib/python3.4/site-packages/filestore/retrieve.py in get_spec_handler(resource, handle_registry)
    204
    205     spec = resource['spec']
--> 206     handler = handle_registry[spec]
    207     key = (str(resource['_id']), handler.__name__)
    208     if key in _HANDLER_CACHE:

KeyError: 'AD_EIGER'

We also don't have EigerImages functions in chxtools.pims_reader
In [69]: from chxtools.pims_readers import EigerImages
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
<ipython-input-69-330a75e1c6f7> in <module>()
----> 1 from chxtools.pims_readers import EigerImages

/home/xf11id/shared/chxtools/chxtools/pims_readers/__init__.py in <module>()
----> 1 from eiger import EigerImages
      2 from edf import EDFImages

ImportError: cannot import name 'EigerImages'

In [70]:

What happed?

Because you have not registered the eiger handler.  Someplace in your other code there is something like register_handler('AD_EIGER', ....).  You just need to run the same code in your collection environment.

But, I don't have access to modify the /opt/... code.
How can run it under collection, using the commandline?
In [70]: register_handler
---------------------------------------------------------------------------
NameError                                 Traceback (most recent call last)
<ipython-input-70-7ebeee835877> in <module>()
----> 1 register_handler

NameError: name 'register_handler' is not defined

See http://nsls-ii.github.io/filestore/#the-payoff-retrieving-data-is-dead-simple

try from chxtools.pims_readers.eiger import EigerImages

Ah, the problem is the bad import line in chxtools.pims_readers.init.py. I'll put in a PR to fix this

https://github.com/NSLS-II-CHX/chxtools/pull/5

@yugangzhang have a look at this PR and merge it if you are :+1:

I wrote a plot_sid function in chxtools/chxtools/ yesterday and will put to  github.

@tacaswell
That's what I did for registered the eiger handler:

In [83]: from filestore.api import register_handler, retrieve

In [84]: class HDF5DatasetHandler(object):
       ....:     def __init__(self, filename):
           ....:         self.file = h5py.File(filename)
           ....:     def __call__(self, key):
           ....:         return self.file[key].value
   ....:
In [85]: register_handler('AD_EIGER',  HDF5DatasetHandler)

But I got a wrong message:
In [86]: img = get_images( hdr, 'eiger_4M_cam_img_image_lightfield' )
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-86-a307ab930b8b> in <module>()
----> 1 img = get_images( hdr, 'eiger_4M_cam_img_image_lightfield' )

/opt/conda_envs/collection/lib/python3.4/site-packages/databroker-0.3.0-py3.4.egg/databroker/pims_readers.py in get_images(headers, name)
     23             # do something
     24     """
---> 25     return Images(headers, name)
     26
     27

/opt/conda_envs/collection/lib/python3.4/site-packages/databroker-0.3.0-py3.4.egg/databroker/pims_readers.py in __init__(self, headers, name)
     47         self._datum_uids = [event.data[name] for event in events]
     48         self._len = len(self._datum_uids)
---> 49         example_frame = retrieve(self._datum_uids[0])
     50         self._dtype = example_frame.dtype
     51         self._shape = example_frame.shape

/opt/conda_envs/collection/lib/python3.4/site-packages/filestore/commands.py in inner(*args, **kwargs)
     19         port = int(conf.connection_config['port'])
     20         db_connect(database=database, host=host, port=port)
---> 21         return func(*args, **kwargs)
     22     return inner
     23

/opt/conda_envs/collection/lib/python3.4/site-packages/filestore/commands.py in retrieve(eid)
    136         The requested data as a numpy array
    137     """
--> 138     return _get_data(eid)

/opt/conda_envs/collection/lib/python3.4/site-packages/filestore/retrieve.py in get_data(eid, handle_registry)
    261                         "datum cache can hold.")
    262
--> 263     handler = get_spec_handler(datum['resource'], handle_registry)
    264     return handler(**datum['datum_kwargs'])

/opt/conda_envs/collection/lib/python3.4/site-packages/filestore/retrieve.py in get_spec_handler(resource, handle_registry)
    210     kwargs = resource['resource_kwargs']
    211     rpath = resource['resource_path']
--> 212     ret = handler(rpath, **kwargs)
    213     _HANDLER_CACHE[key] = ret
    214     return ret

TypeError: __init__() got an unexpected keyword argument 'frame_per_point'

You didn't register the EigerHandler. You registered the HDF5DatasetHandler, which correctly raised because it does not know how to handle Eiger's HDF5 files.

Also, don't use self.file[key].value, use self.file[key][:] instead.

@tacaswell  and @danielballan , I change the code:

In [4]: import h5py
In [5]: class EigerHandler(object):
    def __init__(self, filename):
        self.file = h5py.File(filename)
        def __call__(self, key):
            return self.file[key][:]
   ...:

In [6]: from filestore.api import register_handler, retrieve

In [7]: register_handler('AD_EIGER', EigerHandler)

In [8]: hdr=db[-1]

I still got a same wrong message:

In [9]: img = get_images( hdr, 'eiger_4M_cam_img_image_lightfield' )
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-9-a307ab930b8b> in <module>()
----> 1 img = get_images( hdr, 'eiger_4M_cam_img_image_lightfield' )

/opt/conda_envs/collection/lib/python3.4/site-packages/databroker-0.3.0-py3.4.egg/databroker/pims_readers.py in get_images(headers, name)
     23             # do something
     24     """
---> 25     return Images(headers, name)
     26
     27

/opt/conda_envs/collection/lib/python3.4/site-packages/databroker-0.3.0-py3.4.egg/databroker/pims_readers.py in __init__(self, headers, name)
     47         self._datum_uids = [event.data[name] for event in events]
     48         self._len = len(self._datum_uids)
---> 49         example_frame = retrieve(self._datum_uids[0])
     50         self._dtype = example_frame.dtype
     51         self._shape = example_frame.shape

/opt/conda_envs/collection/lib/python3.4/site-packages/filestore/commands.py in inner(*args, **kwargs)
     19         port = int(conf.connection_config['port'])
     20         db_connect(database=database, host=host, port=port)
---> 21         return func(*args, **kwargs)
     22     return inner
     23

/opt/conda_envs/collection/lib/python3.4/site-packages/filestore/commands.py in retrieve(eid)
    136         The requested data as a numpy array
    137     """
--> 138     return _get_data(eid)

/opt/conda_envs/collection/lib/python3.4/site-packages/filestore/retrieve.py in get_data(eid, handle_registry)
    261                         "datum cache can hold.")
    262
--> 263     handler = get_spec_handler(datum['resource'], handle_registry)
    264     return handler(**datum['datum_kwargs'])

/opt/conda_envs/collection/lib/python3.4/site-packages/filestore/retrieve.py in get_spec_handler(resource, handle_registry)
    210     kwargs = resource['resource_kwargs']
    211     rpath = resource['resource_path']
--> 212     ret = handler(rpath, **kwargs)
    213     _HANDLER_CACHE[key] = ret
    214     return ret

TypeError: __init__() got an unexpected keyword argument 'frame_per_point'

All you did was change the class name, the body is still the same.
The eiger saves many frames per point, the frame_per_point kwarg tells the handler how many frames to extract from the hdf5 file per 'datum'.

No, actually I changed  from return self.file.value to  return self.file[key][:]
I guess need to do more.
I can't use my computer to debug due to #37, @tacaswell do you have a suggestion?
Now, I have to use the beamline computer to do debug, painful!!!

Tom confused the issue; his comment about [:] was an unrelated issue.
You need to use the actual Eiger...Handler class which is not the same as the HDF5...Handler we wrote for CSX's detector. That class is, I believe, defined in chxtools.

Can you debug through a notebook using jupyterhub?

Great! The jupyterhub works! I will debug by it.

@danielballan I looked through chxtools and only found a class python class EigerImages(FramesSequence):  and did not find the definition of   ```python  Eiger...Handler '''

@danielballan
on jupyterhub, we don't have chxtools
import chxtools
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
<ipython-input-5-886d7eb7d21e> in <module>()
----> 1 import chxtools

ImportError: No module named 'chxtools'

I also can't install chxtools in jupyterhub, suggestion?

Just to make sure we are clear, the ... stands for "I don't remember the exactly name."
Re, chxtools in the jupyterhub environment: Ah, I should have done that for you. This will have to wait for tomorrow now.
Meanwhile, we need to find this missing handler code. Tom and I wrote it and ran for the train. I remember cleaning it up somewhat recently, but I can't remember where we put it. I doesn't seem to be in chxtools on github. Could it be in a local branch? I know we at least committed it. Does chxtools need to be pushed to github?

@danielballan, I know your meaning for python ...  :)
For Jupterhub, can we have access to install code?
I will try to find the missing handler code. We have a chxtools github
https://github.com/NSLS-II-CHX/chxtools

Yeah I know you have it on GitHub, but I'm questioning whether GitHub's
copy is up to date with your local copy.
Customizable jupyterhub environments are coming. I have a way to do it but
no time yet to set it up.
On Wed, Oct 14, 2015 at 5:47 PM Yugang Zhang<EMAIL_ADDRESS>wrote:

@danielballan https://github.com/danielballan, I know your meaning for python
... :)
For Jupterhub, can we have access to install code?
I will try to find the missing handler code. We have a chxtools github
https://github.com/NSLS-II-CHX/chxtools
—
Reply to this email directly or view it on GitHub
https://github.com/NSLS-II/Bug-Reports/issues/36#issuecomment-148211890.

Yes, I check our localone and the git one. They are same now. I guess Eirc just update them.

It's conceivable that the latest version of that code fell into the window
of what was lost during the NFS failure, but at minimum some version of
this code has been around for awhile. It must be there somewhere.
On Wed, Oct 14, 2015 at 5:55 PM Yugang Zhang<EMAIL_ADDRESS>wrote:

Yes, I check our localone and the git one. They are same now. I guess Eirc
just update them.
—
Reply to this email directly or view it on GitHub
https://github.com/NSLS-II/Bug-Reports/issues/36#issuecomment-148213354.

Up to now, I did not find it. We might need you come to our beamline tomorrow.

I still did not mange to open eiger by databroker, then I tried to open a disk file. I found a problem of HDF5_PLUGIN_PATH.
In [21]: img = entry[ keys[0] ][0]
---------------------------------------------------------------------------
IOError                                   Traceback (most recent call last)
<ipython-input-21-98d831a2dbe5> in <module>()
----> 1 img = entry[ keys[0] ][0]

h5py/_objects.pyx in h5py._objects.with_phil.wrapper (-------src-dir-------/h5py/_objects.c:2458)()

h5py/_objects.pyx in h5py._objects.with_phil.wrapper (-------src-dir-------/h5py/_objects.c:2415)()

/nfs/xf11id/mc/envs/ophyd/lib/python2.7/site-packages/h5py/_hl/dataset.pyc in __getitem__(self, args)
    449         mspace = h5s.create_simple(mshape)
    450         fspace = selection._id
--> 451         self.id.read(mspace, fspace, arr, mtype)
    452
    453         # Patch up the output for NumPy

h5py/_objects.pyx in h5py._objects.with_phil.wrapper (-------src-dir-------/h5py/_objects.c:2458)()

h5py/_objects.pyx in h5py._objects.with_phil.wrapper (-------src-dir-------/h5py/_objects.c:2415)()

h5py/h5d.pyx in h5py.h5d.DatasetID.read (-------src-dir-------/h5py/h5d.c:3058)()

h5py/_proxy.pyx in h5py._proxy.dset_rw (-------src-dir-------/h5py/_proxy.c:1670)()

h5py/_proxy.pyx in h5py._proxy.H5PY_H5Dread (-------src-dir-------/h5py/_proxy.c:1336)()

IOError: Can't read data (Required filter 'hdf5 lz4 filter; see http://www.hdfgroup.org/services/contributions.html' is not registered)

I knew this problem came from a hdf5-plugin path.
On our previous ophyd, we use
and we can open a eiger-hdf5 file.

Now, on current collection,
I tried
 ```python export HDF5_PLUGIN_PATH=/nfs/xf11id/mc/envs/ophyd/lib '''
but, the collection doesn't work. I guess we have to use /opt/ path
so I changed it to
 ```python export HDF5_PLUGIN_PATH=/opt/conda_envs/collection/lib```
But, I got a same problem.

```python
In [21]: img = entry[ keys[0] ][0]
---------------------------------------------------------------------------
IOError                                   Traceback (most recent call last)
<ipython-input-21-98d831a2dbe5> in <module>()
----> 1 img = entry[ keys[0] ][0]

h5py/_objects.pyx in h5py._objects.with_phil.wrapper (-------src-dir-------/h5py/_objects.c:2458)()

h5py/_objects.pyx in h5py._objects.with_phil.wrapper (-------src-dir-------/h5py/_objects.c:2415)()

/nfs/xf11id/mc/envs/ophyd/lib/python2.7/site-packages/h5py/_hl/dataset.pyc in __getitem__(self, args)
    449         mspace = h5s.create_simple(mshape)
    450         fspace = selection._id
--> 451         self.id.read(mspace, fspace, arr, mtype)
    452
    453         # Patch up the output for NumPy

h5py/_objects.pyx in h5py._objects.with_phil.wrapper (-------src-dir-------/h5py/_objects.c:2458)()

h5py/_objects.pyx in h5py._objects.with_phil.wrapper (-------src-dir-------/h5py/_objects.c:2415)()

h5py/h5d.pyx in h5py.h5d.DatasetID.read (-------src-dir-------/h5py/h5d.c:3058)()

h5py/_proxy.pyx in h5py._proxy.dset_rw (-------src-dir-------/h5py/_proxy.c:1670)()

h5py/_proxy.pyx in h5py._proxy.H5PY_H5Dread (-------src-dir-------/h5py/_proxy.c:1336)()

IOError: Can't read data (Required filter 'hdf5 lz4 filter; see http://www.hdfgroup.org/services/contributions.html' is not registered)

Another problem for a piece of code in  /home/xf11id/shared/chxtools/chxtools/pims_readers/eiger.py
under ophyd:
In [13]: lengths
Out[13]: [1]
In [14]: toc = np.concatenate(
   ....:                 [zip(i*np.ones(length, dtype=int),
   ....:                      np.arange(length, dtype=int))
   ....:                 for i, length in enumerate(lengths)])

In [15]: toc
Out[15]: array([[0, 0]])

but, using collection,
In [13]: lengths
Out[13]: [1]

In [14]: toc = np.concatenate(
   ....:                 [zip(i*np.ones(length, dtype=int),
   ....:                      np.arange(length, dtype=int))
   ....:                 for i, length in enumerate(lengths)])
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-14-a479f3fe7f3b> in <module>()
      2                 [zip(i*np.ones(length, dtype=int),
      3                      np.arange(length, dtype=int))
----> 4                 for i, length in enumerate(lengths)])

ValueError: zero-dimensional arrays cannot be concatenated

I guess a python version problem?

(1) chxtools.pims_readers.eiger.py can read eiger hdf5 file now.
I found a bug in chxtools.pims_readers.eiger.py, the self._toc work well for python 2, but not for python 3.  I modified self._toc and the eiger.py can read a eiger file now:
In [8]: from chxtools.pims_readers.eiger import EigerImages as Images
In [9]: path ='/XF11ID/data/2015/10/14/'
In [10]: fn = 'fe294a59-f2e4-477a-8e88_15_master.h5'
In [11]: fp = path + fn
In [12]: img = Images( fp)
In [13]: img
Out[13]:
<Frames>
Length: 1 frames
Frame Shape: 2167 x 2070
Pixel Datatype: uint32

(2) a problem for Handler class.
I did not find @danielballan and @tacaswell 's  python Eiger...Handler class, then I wrote a class:
from chxtools.pims_readers.eiger import EigerImages
class HDF5Handler(object):
   def __init__(self, filename):
      self.filename =  filename
   def __call__(self):
      return  EigerImages( self.filename )

to register 'AD_EIGER'.
But, when I try to read filestore data, i got a wrong message "unexpected keyword argument 'frame_per_point'"  as previously.
In [68]: from databroker import DataBroker as db, get_events, get_images, get_table

In [69]: hdr = db['fedb7385-3255-43fd-9785']

In [70]: name = 'eiger_4M_cam_img_image_lightfield'

In [71]: get_images( hdr,name )
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-71-ddd2768ec494> in <module>()
----> 1 get_images( hdr,name )

/opt/conda_envs/analysis/lib/python3.4/site-packages/databroker-0.3.0-py3.4.egg/databroker/pims_readers.py in get_images(headers, name)
     23             # do something
     24     """
---> 25     return Images(headers, name)
     26
     27

/opt/conda_envs/analysis/lib/python3.4/site-packages/databroker-0.3.0-py3.4.egg/databroker/pims_readers.py in __init__(self, headers, name)
     47         self._datum_uids = [event.data[name] for event in events]
     48         self._len = len(self._datum_uids)
---> 49         example_frame = retrieve(self._datum_uids[0])
     50         self._dtype = example_frame.dtype
     51         self._shape = example_frame.shape

/opt/conda_envs/analysis/lib/python3.4/site-packages/filestore/commands.py in inner(*args, **kwargs)
     19         port = int(conf.connection_config['port'])
     20         db_connect(database=database, host=host, port=port)
---> 21         return func(*args, **kwargs)
     22     return inner
     23

/opt/conda_envs/analysis/lib/python3.4/site-packages/filestore/commands.py in retrieve(eid)
    136         The requested data as a numpy array
    137     """
--> 138     return _get_data(eid)

/opt/conda_envs/analysis/lib/python3.4/site-packages/filestore/retrieve.py in get_data(eid, handle_registry)
    261                         "datum cache can hold.")
    262
--> 263     handler = get_spec_handler(datum['resource'], handle_registry)
    264     return handler(**datum['datum_kwargs'])

/opt/conda_envs/analysis/lib/python3.4/site-packages/filestore/retrieve.py in get_spec_handler(resource, handle_registry)
    210     kwargs = resource['resource_kwargs']
    211     rpath = resource['resource_path']
--> 212     ret = handler(rpath, **kwargs)
    213     _HANDLER_CACHE[key] = ret
    214     return ret

TypeError: __init__() got an unexpected keyword argument 'frame_per_point'

I wonder should I add the 'frame_per_point' keyword to my handler class?  Or there is a bug in filestore.api.retrieve fucntion?

Yes, you should add frame_per_point keyword to your handler class. In our Eiger...Handler class there was quite a bit of logic to handle the particular structure of the Eiger's HDF5 files. You will need to replicate that as well.

Aha! Do you have any clue to find it?

With these commands, you can find the EigerHandler:
$ cd /home/xf11id/Repos
$ grep -r Eiger
...
1de40 Daron Chabot<EMAIL_ADDRESS>1438798631 -0400 commit: ENH: Add
EigerHandler.
filestore/.git/COMMIT_EDITMSG:ENH: Add EigerHandler.
filestore/filestore/handlers.py:from chxtools.pims_readers import
EigerImages
filestore/filestore/handlers.py:class EigerHandler(HandlerBase):
filestore/filestore/handlers.py:        return
np.array(EigerImages(master_path))
Binary file filestore/filestore/handlers.pyc matches
$ cat filestore/filestore/handlers.py

class EigerHandler(HandlerBase):
    specs = {'AD_EIGER'} | HandlerBase.specs

    def __init__(self, fpath, frame_per_point):
        # create pims handler
        self._base_path = fpath
        self.fpp = frame_per_point

    def __call__(self, seq_id):
        master_path = '{}_{}_master.h5'.format(self._base_path, seq_id)
        # TODO Return a multi-dimensional PIMS seq.
        return np.array(EigerImages(master_path))

I would imagine that is the handler that you are looking for.
On Fri, Oct 16, 2015 at 11:39 AM, Yugang Zhang<EMAIL_ADDRESS>wrote:

Aha! Do you have any clue to find it?
—
Reply to this email directly or view it on GitHub
https://github.com/NSLS-II/Bug-Reports/issues/36#issuecomment-148749573.

--
Dr. Eric Dill
Assistant Computational Scientist
National Synchrotron Light Source 2

@ericdill Wait, so that code is in a rogue branch of filestore that has a dependency on chxtools?

Sure looks that way
On Fri, Oct 16, 2015, 11:59 AM Dan Allan<EMAIL_ADDRESS>wrote:

@ericdill https://github.com/ericdill Wait, so that code is in a rogue
branch of filestore that has a dependency on chxtools?
—
Reply to this email directly or view it on GitHub
https://github.com/NSLS-II/Bug-Reports/issues/36#issuecomment-148754807.

@yugangzhang Please copy the code for that class into chxtools. Let me know when it is done and please paste that path to chxtools into this issue. Then I will install chxtools into collection and the jupyterhub env.
As we've discussed, I do plan to make it possible for you to do this yourself, but I can't take time to set that up just now.

@yugangzhang I changed my mind. I will make a special (very small) package just for that handler. I've done this kind of thing for pims, and I think it makes things simple. You don't have to do anything. Give me a couple minutes....

Thanks to  @ericdill , it works now!

In [9]: hdr = db['fedb7385-3255-43fd-9785']

In [10]: name = 'eiger_4M_cam_img_image_lightfield'

In [11]: imgs = get_images( hdr,name )

In [12]: imgs
Out[12]:
<Frames>
Length: 1 frames
Frame Shape: 1 x 2167
Pixel Datatype: uint32

It's great! In the future, I would like to change the  Frame Shape: 1 x 2167  to   1X2167X...

@yugangzhang How did you get that working? In what environment?

@danielballan , I just did... It might not be the best way.
I did it in analysis environment.

My guess: you happened to start ipython while sitting in the Repos directory, so the "rogue" branch of filestore on your system overrode the version installed in the analysis environment.

Yeah!

Talk more after lunch.

Taking a step back...
It's generally good and useful to put separate concerns in separate repos. They have very different dependencies and usually different "rates of change", meaning frequency with which they are edited/updated.
To that end, I created a new project, eiger-io, uploaded it to github, and installed it in collection and analysis on xf11id-ws1.
In [6]: from filestore.api import register_handler

In [7]: import eiger_io

In [8]: register_handler('AD_EIGER', eiger_io.fs_handler.EigerHandler)

In [9]: get_images(h, 'eiger_4M_cam_img_image_lightfield')

For me, that reproduces the error you reported above:
ValueError: zero-dimensional arrays cannot be concatenated

That's what we will address next.

cc @klauer @ericdill Can I call in some help debugging it from here?

Sorry for making this mess!
On Fri, Oct 16, 2015, 13:03 Dan Allan<EMAIL_ADDRESS>wrote:

Taking a step back...
It's generally good and useful to put separate concerns in separate repos.
They have very different dependencies and usually different "rates of
change", meaning frequency with which they are edited/updated.
To that end, I created a new project, eiger-io, uploaded it to github
https://github.com/NSLS-II-CHX/eiger-io, and installed it in collection
and analysis on xf11id-ws1.
In [6]: from filestore.api import register_handler
In [7]: import eiger_io
In [8]: register_handler('AD_EIGER', eiger_io.fs_handler.EigerHandler)
In [9]: get_images(h, 'eiger_4M_cam_img_image_lightfield')
For me, that reproduces the error you reported above:
ValueError: zero-dimensional arrays cannot be concatenated
That's what we will address next.
—
Reply to this email directly or view it on GitHub
https://github.com/NSLS-II/Bug-Reports/issues/36#issuecomment-148773028.

@danielballan ,
python ValueError: zero-dimensional arrays cannot be concatenated
That's the bug I talked about in code "self._toc" of  chxtools.pims_readers.eiger.py, the self._toc works well for python 2, but not for python 3. I already modified self._toc.

change python  self._toc = np.concatenate(  [zip(i*np.ones(length, dtype=int), np.arange(length, dtype=int)) for i, length in enumerate(lengths)])
to
        toc=[]
        for i, length in enumerate(lengths):
           a,b=i*np.ones(length, dtype=int), np.arange(length, dtype=int)
           #print (a,b)
           toc.append([ [x,y] for [x,y] in zip(a,b) ])
        self._toc = np.concatenate(toc )

Why?

Oh, I think I know why. Could you try this simpler change:
self._toc = np.concatenate(
 [list(zip(i*np.ones(length, dtype=int)),
np.arange(length, dtype=int))
for i, length in enumerate(lengths)])

If you think it works, please open a pull request against the eiger-io repo on GitHub. It will be good Github practice!

To elaborate on my last comment, this is the specific change between python 2 and 3:
Python 3:
In [1]: zip([1,2,3], [4,5,6])  # lazily evaluated, not immediately turned into a list
Out[1]: <zip at 0x7f696daa2a08>

In [2]: list(zip([1,2,3], [4,5,6]))
Out[2]: [(1, 4), (2, 5), (3, 6)]

Python 2:
In [1]: zip([1,2,3], [4,5,6])  # returns a list
Out[1]: [(1, 4), (2, 5), (3, 6)]

Ok! I assume it works and I will make a pull request.

I misplaced a parenthesis in my example. list() should go around zip(...) of course.

Thanks to Sameera for github upload.
I guess something wrong during our upload.
I am upload a new one.

What?

I just did merge it. should not!

@danielballan please check the code is ok?

Oh I see.

I think this time the code is correct. what should i do now?  git push again?

Yes. And open a new PR. :- )

can you merge?

You will do the next to add eiger-io into collection and analysis?

Done. Now we have a new error, related I think to inability to access the drive where the files are stored. This may be a permissions issue.
I am done for the night. We'll pick this up next week.
In [1]: from filestore.api import register_handler

In [2]: from databroker import DataBroker as db, get_images

In [3]: import eiger_io.fs_handler

In [4]: register_handler('AD_EIGER', eiger_io.fs_handler.EigerHandler)

In [5]: h = db['574bb68b']

In [6]: get_images(h, 'eiger_4M_cam_img_image_lightfield')
---------------------------------------------------------------------------
OSError                                   Traceback (most recent call last)
<ipython-input-6-4903318bce0e> in <module>()
----> 1 get_images(h, 'eiger_4M_cam_img_image_lightfield')

/opt/conda_envs/analysis/lib/python3.4/site-packages/databroker-0.3.0-py3.4.egg/databroker/pims_readers.py in get_images(headers, name)
     23             # do something
     24     """
---> 25     return Images(headers, name)
     26
     27

/opt/conda_envs/analysis/lib/python3.4/site-packages/databroker-0.3.0-py3.4.egg/databroker/pims_readers.py in __init__(self, headers, name)
     47         self._datum_uids = [event.data[name] for event in events]
     48         self._len = len(self._datum_uids)
---> 49         example_frame = retrieve(self._datum_uids[0])
     50         self._dtype = example_frame.dtype
     51         self._shape = example_frame.shape

/opt/conda_envs/analysis/lib/python3.4/site-packages/filestore/commands.py in inner(*args, **kwargs)
     19         port = int(conf.connection_config['port'])
     20         db_connect(database=database, host=host, port=port)
---> 21         return func(*args, **kwargs)
     22     return inner
     23

/opt/conda_envs/analysis/lib/python3.4/site-packages/filestore/commands.py in retrieve(eid)
    136         The requested data as a numpy array
    137     """
--> 138     return _get_data(eid)

/opt/conda_envs/analysis/lib/python3.4/site-packages/filestore/retrieve.py in get_data(eid, handle_registry)
    262
    263     handler = get_spec_handler(datum['resource'], handle_registry)
--> 264     return handler(**datum['datum_kwargs'])

/opt/conda_envs/analysis/lib/python3.4/site-packages/eiger_io/fs_handler.py in __call__(self, seq_id)
     20         master_path = '{}_{}_master.h5'.format(self._base_path, seq_id)
     21         # TODO Return a multi-dimensional PIMS seq.
---> 22         return np.array(EigerImages(master_path))

/opt/conda_envs/analysis/lib/python3.4/site-packages/pims/base_frames.py in <genexpr>(.0)
    205
    206     def __iter__(self):
--> 207         return (self._get(i) for i in self.indices)
    208
    209     def __len__(self):

/opt/conda_envs/analysis/lib/python3.4/site-packages/pims/base_frames.py in _get(self, key)
    196     def _get(self, key):
    197         "Wrap ancestor's get_frame method in a processing function."
--> 198         return self._proc_func(self._ancestor[key])
    199
    200     def __repr__(self):

/opt/conda_envs/analysis/lib/python3.4/site-packages/pims/base_frames.py in __getitem__(self, key)
    285         if isinstance(key, int):
    286             i = key if key >= 0 else len(self) + key
--> 287             return self.get_frame(i)
    288         else:
    289             return SliceableIterable(self, range(len(self)), len(self))[key]

/opt/conda_envs/analysis/lib/python3.4/site-packages/eiger_io/pims_reader.py in get_frame(self, i)
     65         with h5py.File(self.master_filepath) as f:
     66             try:
---> 67                 img = f['entry']['data'][key][elem_number]  # Eiger firmware v1.3.0 and onwards
     68             except KeyError:
     69                 img = f['entry'][key][elem_number]          # Older firmwares

h5py/_objects.pyx in h5py._objects.with_phil.wrapper (-------src-dir-------/h5py/_objects.c:2458)()

h5py/_objects.pyx in h5py._objects.with_phil.wrapper (-------src-dir-------/h5py/_objects.c:2415)()

/opt/conda_envs/analysis/lib/python3.4/site-packages/h5py/_hl/dataset.py in __getitem__(self, args)
    449         mspace = h5s.create_simple(mshape)
    450         fspace = selection._id
--> 451         self.id.read(mspace, fspace, arr, mtype)
    452
    453         # Patch up the output for NumPy

h5py/_objects.pyx in h5py._objects.with_phil.wrapper (-------src-dir-------/h5py/_objects.c:2458)()

h5py/_objects.pyx in h5py._objects.with_phil.wrapper (-------src-dir-------/h5py/_objects.c:2415)()

h5py/h5d.pyx in h5py.h5d.DatasetID.read (-------src-dir-------/h5py/h5d.c:3058)()

h5py/_proxy.pyx in h5py._proxy.dset_rw (-------src-dir-------/h5py/_proxy.c:1670)()

h5py/_proxy.pyx in h5py._proxy.H5PY_H5Dread (-------src-dir-------/h5py/_proxy.c:1336)()

OSError: Can't read data (Can't open directory)

For posterity, start debugging with this puzzling state of affairs:

In [10]: h5py.File('/XF11ID/data/2015/10/14/7dbd2dd3-d6fb-425f-9ebe_16_master.h5')
Out[10]: <HDF5 file "7dbd2dd3-d6fb-425f-9ebe_16_master.h5" (mode r)>

In [16]: list(f['entry']['data']['data_000001'])

(...)

OSError: Can't read data (Can't open directory)

In [18]: !ls /XF11ID/data/2015/10/14/7dbd2dd3-d6fb-425f-9ebe*
/XF11ID/data/2015/10/14/7dbd2dd3-d6fb-425f-9ebe_16_data_000001.h5  /XF11ID/data/2015/10/14/7dbd2dd3-d6fb-425f-9ebe_16_master.h5

Got it! This was an old issue rearing its head again. As @yugangzhang probably already knows, one must
export HDF5_PLUGIN_PATH=/opt/conda_envs/collection/lib

Then it works:
In [1]: from databroker import DataBroker as db, get_images

In [2]: h = db['574bb68b']

In [3]: import eiger_io.fs_handler

In [4]: imcport h5py
KeyboardInterrupt

In [4]: from filestore.api import register_handler

In [5]: register_handler('AD_EIGER', eiger_io.fs_handler.EigerHandler)

In [6]: get_images(h, 'eiger_4M_cam_img_image_lightfield')[0].shape
Out[6]: (1, 2167, 2070)

@tacaswell Do you think it's reasonable to add that bash export to a post-link.sh script? If so, which one? eiger-io?

Export thing is also the reason I can not run analysis using my computer!

@yugangzhang  Because it doesn't work on jupyterhub?

Ha! I got it. I updated the conda package for hdf5-lz4 and now you don't need to manually set the bash variable HDF5_PLUGIN_PATH using export. It will be set automatically by conda when you source activate .... I tested it; it works. I tried to do this months ago, and all I missed was a single backslash. Ha!
Unfortunately, it still won't work via jupyterhub because source activate is never called when you access the environment through jupyterhub. I have anticipated this issue for awhile. I will try to find a way around it soon.

Yeah!
@ericdill I knew, why I can't run analysis under my acount@xf11id now!
On my acount@xf11id,  I source activate analysis, but my .bashrc file export that PLUG thing to /nfs/... for eiger reading, then when  import databroker, it cause a problem. I guess this analysis source only allows a /opt/... path.
Then, I delete that line in .bashrc, I can run analysis and import databroker now. I hope that after Dan conda install that package, I also can read eiger hdf5 file.

The package is installed. Try it!
On Fri, Oct 16, 2015 at 9:18 PM Yugang Zhang<EMAIL_ADDRESS>wrote:

Yeah!
@ericdill https://github.com/ericdill I knew, why I can't run analysis
under my acount@xf11id now!
On my acount@xf11id, I source activate analysis, but my .bashrc file
export that PLUG thing to /nfs/... for eiger reading, then when import
databroker, it cause a problem. I guess this analysis source only allows a
/opt/... path.
Then, I delete that line in .bashrc, I can run analysis and import
databroker now. I hope that after Dan conda install that package, I also
can read eiger hdf5 file.
—
Reply to this email directly or view it on GitHub
https://github.com/NSLS-II/Bug-Reports/issues/36#issuecomment-148874010.

Try it on Jupter or myacount@xf11id

Your account. Read my comments above about Jupyter - that will take more
thinking.
On Fri, Oct 16, 2015 at 9:53 PM Yugang Zhang<EMAIL_ADDRESS>wrote:

Try it on Jupter or myacount@xf11id
—
Reply to this email directly or view it on GitHub
https://github.com/NSLS-II/Bug-Reports/issues/36#issuecomment-148876163.

No work on my account@xf11id.

But, I think for some reason my conda env was broken. I am trying to install a new env.

Could you try using the analysis env? Not a new env of your own?
On Fri, Oct 16, 2015 at 10:02 PM Yugang Zhang<EMAIL_ADDRESS>wrote:

But, I think for some reason my conda env was broken. I am trying to
install a new env.
—
Reply to this email directly or view it on GitHub
https://github.com/NSLS-II/Bug-Reports/issues/36#issuecomment-148876657.

Eric helped to install a new one and at the same time he deleted my old ones.

 One sure way to activate it is to type:
source activate /opt/conda_envs/analysis
On Fri, Oct 16, 2015 at 10:04 PM Yugang Zhang<EMAIL_ADDRESS>wrote:

Eric helped to install a new one and at the same time he deleted my old
ones.
—
Reply to this email directly or view it on GitHub
https://github.com/NSLS-II/Bug-Reports/issues/36#issuecomment-148877081.

P.S. This is me texting while riding shotgun on the way to Tom'a wedding!
Only seems right that I should be debugging during the trip.
On Fri, Oct 16, 2015 at 10:22 PM Dan Allan<EMAIL_ADDRESS>wrote:

Either way, the environment I want you to use is root installed and
available to all users. One sure way to activate it is to type:
source activate /opt/conda_envs/analysis
On Fri, Oct 16, 2015 at 10:04 PM Yugang Zhang<EMAIL_ADDRESS>wrote:

Eric helped to install a new one and at the same time he deleted my old
ones.
—
Reply to this email directly or view it on GitHub
https://github.com/NSLS-II/Bug-Reports/issues/36#issuecomment-148877081
.

Great! I works! Under /opt/conda_envs/analysis

xf11id@xf11id-ws1:~$ conda create -n user_analysis --clone /opt/conda_envs/analysis

Actually I don't think that works. Long story. But:
conda create -n user_analysis analysis
works as long as the user does not have a custom .condarc file in their
home dir.
On Sat, Oct 17, 2015 at 9:00 AM Eric Dill<EMAIL_ADDRESS>wrote:

xf11id@xf11id-ws1:~$ conda create -n user_analysis --clone
/opt/conda_envs/analysis
—
Reply to this email directly or view it on GitHub
https://github.com/NSLS-II/Bug-Reports/issues/36#issuecomment-148914928.

Actually, I tried both and both did not work!

the '--clone /opt/conda_envs/analysis' doesn't work, i think, due to a /opt/ permission problem.
'conda create -n user_analysis analysis' But, I did not have analysis env any more on my account@xf11id.

You created an environment called " analysis". Yes, there is a space in front of analysis.
yuzhang@xf11id-ws1:~$ conda info -e
# conda environments:
#
test                     /home/yuzhang/.conda/envs/test
 analysis                /home/yuzhang/.conda/envs/ analysis
root                  *  /opt/conda

You need to be very careful with your commands when you type them in.  You typed
 1899  conda create -n  analysis --clone /opt/conda_envs/analysis\

which has an extra space between the '-n' and the 'analysis', which conda apparently interprets as a literal space.
Also, please do not sudo conda create anything.
You cannot create an environment with the analysis metapackage because your .condarc does not contain the latest channel.  Please run the following command:
echo "channels:
  - CHX
  - latest
  - anaconda

create_default_packages:
  - pip
  - anaconda-client" > ~/.condarc

Then try to create an environment again, by typing conda create -n user_analysis analysis chx_configuration.

@ericdill Thanks! It works for the env-create.

Great. Is this issue resolved?

I can use ipython to open Hdf5 file and do analysis now.
But, as Dan mentioned before, I still can't use Jupyter to open Eiger file due to the python HDF_plug... thing.

OK. We are on the same page then. You can leave this open as a reminder. I think I can circle back to this within ~2 weeks.

Please also give us a way how to install customized package, like chxtools, in Jupyter.
I will leave this bug-report open at this moment.

Ok, given that the original issue was that you could not access the Eiger images via databroker. I am going to consider this issue to be completed.
The reason that I am advocating for closing this issue is that the reason why it would remain open (as per @danielballan and @yugangzhang 's comments directly above this one) is completely different from the title of this issue.  It is therefore too easy to lose the primary reason why this issue remains open.
@yugangzhang I need you to open a new issue on [our feature requests tracker] (https://github.com/NSLS-II/wishlist) for getting customized packages installed on jupyterhub. We know that it is important to everyone and we are working on it.

I added a feature for my "remotekernel" package, and now the conda activation scripts can be run by jupyterhub. This is working and deployed. This is a big win. cc @tacaswell @ericdill


Switch on debugger - WIP

switch on debugger

Pull Request Test Coverage Report for Build 641242159

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.007%) to 43.179%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/common/ports.ts
4
74.14%

Totals

Change from base Build 641062394:
-0.007%

Covered Lines:
25300

Relevant Lines:
53438

💛  - Coveralls

Closing to clean up older PRs.  There is a new related PR open now.


Disable Transition(sliding) animation while navigating between Scenes

I m using react-native-router-flux v4.0.4
I m trying to disable animation while navigation between screens. Not in tabs.
I have used this one
<Scene key="home" component={home} duration={0} hideNavBar={true}/>
duration={0} and animationEnabled={false} are not working .Are there any solution

@Kazn, it worked for me in this way:
<Router> 	<Tabs hideTabBar key="root"> 		<Scene key="loading" component={Loading} initial hideNavBar /> 		<Scene key="login" component={Login} hideNavBar /> 		<Scene key="loginForm" component={LoginForm} hideNavBar /> 		... 	</Tabs> </Router>

I m not using in tabs.have you checked in iphone as well

I m not using in tabs.have you checked in iphone as well

Try use this:
<Scene key="home" component={home} hideNavBar  swipeEnabled={false} animationEnabled={false} panHandlers={null} />
It worked on both iOS and Android for me. (I'm using the 4.0.5 react native router flux version).

@marciobera is correct

I m not using in tabs.have you checked in iphone as well

Try use this: <Scene key="home" component={home} hideNavBar swipeEnabled={false} animationEnabled={false} panHandlers={null} />
It worked on both iOS and Android for me. (I'm using the 4.0.5 react native router flux version).

thanks


proposal.metadata is always blank

Strange that none of the proposals contain any metadata field
https://docs.cosmos.network/v0.47/modules/gov#proposal-3
GraphQL
query{
  proposals(orderBy:block__number, where:{metadata_not:""}) {
    id
    block{
      number
      date
    }
    proposer
    title
    metadata
    summary,
  }
}

I don't think that's a bug. Metadata field is not included in MsgSubmitProposalV1Beta1, so we default to an empty string in that case. For MsgSuibmitProposalV1, most proposals decide to just leave an empty string anyway

Ah yes, noticed that too, seems like it's just empty
Just figured it might of been an error, but it's just there's no data


Resolve syncing conflicts from live-sync-work to live

Pull request opened by OPS to resolve syncing conflicts from live-sync-work to live.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-sdk-dotnet, working directory: W:\1lbd-s, target branch: live, target branch commit: 99b01965ee24d93f87dec1ebe0d72e03c59ee082, source branch: live-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-sdk-dotnet, working directory: W:\j1bn-s, target branch: live, target branch commit: 99b01965ee24d93f87dec1ebe0d72e03c59ee082, source branch: live-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-sdk-dotnet, working directory: W:\wt1k-s, target branch: live, target branch commit: 99b01965ee24d93f87dec1ebe0d72e03c59ee082, source branch: live-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-sdk-dotnet, working directory: W:\kblc-s, target branch: live, target branch commit: 99b01965ee24d93f87dec1ebe0d72e03c59ee082, source branch: live-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-sdk-dotnet, working directory: W:\eoc2-s, target branch: live, target branch commit: 99b01965ee24d93f87dec1ebe0d72e03c59ee082, source branch: live-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/OPS-E2E-PPE/azure-docs-sdk-dotnet, working directory: W:\355c-s, target branch: live, target branch commit: 99b01965ee24d93f87dec1ebe0d72e03c59ee082, source branch: live-sync-work, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


use ^ compatible ranges, not open ended >= ranges

nan just recently published a breaking change (a total rewrite) as 2.0.0
This broke node-sodium, because it was using open ended version ranges.
That is a bad idea, because it makes it easy for modules you depend on to break your code.
The solution is to use ^ ranges, which mean "compatible" ^ ranges will give you new patches, new features but not breaking changes.

fixed the dependencies, but left the devDependecies unchanged. If it breaks in the future we'll fix it in the mean time we get the benefits of newer versions.

With ^ ranges you still get new features. so if you ask for ^1.2.9 you could get 1.9.0 but not 2.0.0.
so we'll still get new versions, but just not the new versions that might break our code.
Sure, it is possible that the breaking change might not affect the parts that we are using.
A better solution might be to use https://david-dm.org/ which adds a badge in your readme to tell you when you do not have the most uptodate version of a dependency.


'Hello World' in WhiteSpace

I would like to add WhiteSpace program for 'Hello World'

Go ahead, @Hrily !


Attach node script dialogue window proposes filenames inconsistent with GDScript syle guide.

Godot version
v4.2.dev3.official.013e8e3af
System information
Windows 10.0.19045 - GLES3 (Compatibility)
Issue description
When attaching a new script to a node with the "attach node script" dialogue window, it proposes a default script file name based on the name of the node the script is being attached to.
So for example: when attaching a new script to a node named "Test", the proposed script file name is Test.gd.
This is inconsistent with the GDScript style guide (file names section), which states: "Use snake_case for file names."
To follow the guide, the proposed name should be converted to snake_case instead, in this case: "test.gd".
Steps to reproduce

Create a new project.
Add any node.
Rename the node to any name, or leave the default one.
Right click the node and click "Attach Script".
Observe the value in the "Path" field not following the GDScript style guide.

Minimal reproduction project
N/A

There is editor/naming/scene_name_casing project setting. Unfortunately, the name is not successful, since there are many other types of files besides scenes. Perhaps we should add a file_name_casing setting? Also C# uses PascalCase.

Maybe add a setting for gdscript_name_casing instead of file_name_casing ?

Thanks for the report! Consolidating in https://github.com/godotengine/godot/issues/39441.


bring back /warning

if it continues we're gonna be left with only commands that show some stupid info and gambling (and then milenakos gonna add a shitton p2w things)

look ma im in milenakos mods

it was removed solely and exclusively because it wouldnt make sense to new people who havent seen old cattype images please stop making conspiracy theories up


ci(c++): Implement C++ CI scripts using python

Implement C++ CI scripts using python.

Code Style Check CI continues to error, but I cannot get the cause of the error from the log.

PTAL, thanks.

Could we add windows CI in this PR?

Windows CI has not been added yet, windows bazel requires some additional configuration, I am trying it locally based on the current run_ci.py.
For the current linux and mac os C++ CI, it can work. Maybe we can merge the pr first.

Hi @PragmaTwice, It has been revised according to the comments mentioned.
In addition, the local adaptation of Windows C++ CI has been completed in the past two days. After this PR is merged, another PR will be created to implement the final adaptation of Windows C++ CI.

Can this PR be merged?


modify values-test for big-int value

What this PR does / why we need it:
Helm render uses yaml.Unmarshal to read yaml files, and then we manually traverse the yaml structure to convert to chartutil.Values which is of type map[string]interface{}. So any float64 values in yaml will be stringified as is without looking at their types
This PR tries to break TestCoalesceValues to reproduce this issue
Special notes for your reviewer:
I made this PR just to reference in the issue https://github.com/helm/helm/issues/5929. Will close this immediately
If applicable:

[ ] this PR contains documentation
[ ] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

This was from CI before closing the issue


Fix race in test

Description
Add no agent backoff
was done on iso6 already: https://github.com/inmanta/inmanta-core/pull/6561
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[ ] Attached issue to pull request
[x] Changelog entry
[ ] Type annotations are present
[ ] Code is clear and sufficiently documented
[ ] No (preventable) type errors (check using make mypy or make mypy-diff)
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
[ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing this pull request

Merged into branches master in 04e0f451c9767344773cf5d09871c3d3712b54d7

Processing #7240.


warnings coming from dependent library fst

Expected behavior
This is observed in JDK11 JVM. There should be no warnings, especially those that indicate that code may stop working in a future release.
Actual behavior
Warnings issued. See also (fst 295) Reporting here to make redisson committers aware.
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.nustaq.serialization.FSTClazzInfo (file:/.../fst-2.57.jar) to field java.lang.String.value
WARNING: Please consider reporting this to the maintainers of org.nustaq.serialization.FSTClazzInfo
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

Steps to reproduce or test case
Running the app that uses redisson
Redis version
N/A
Redisson version
3.12.2
Redisson configuration
N/A

As workaround use Kryo5Codec, JsonJacksonCodec or SerializationCodec


[Bug] Mistral-7B-Instruct-v0.2 Model is creating garbage responses to prompts

🐛 Bug

To Reproduce
Steps to reproduce the behavior:

Download the android.tar prebuilt file for Mistral-7B-Instruct-v0.2 from https://github.com/mlc-ai/binary-mlc-llm-libs/tree/main/Mistral-7B-Instruct-v0.2
Build the android app for MLC Chat based on the instructions provided in https://llm.mlc.ai/docs/prebuilt_models.html#overview
Either run app in USB-debug mode on an Android device or build apk file and install it on an Android device.

Expected behavior

LLM should be able to generate meaningful responses to the questions (prompts) provided.
Environment

Platform (e.g. WebGPU/Vulkan/IOS/Android/CUDA):
Operating system (e.g. Ubuntu/Windows/MacOS/...): Android
Device (e.g. iPhone 12 Pro, PC+RTX 3090, ...): OnePlus 12
How you installed MLC-LLM (conda, source): pip
How you installed TVM-Unity (pip, source):
Python version (e.g. 3.10): 3.10
GPU driver version (if applicable):
CUDA/cuDNN version (if applicable):
TVM Unity Hash Tag (python -c "import tvm; print('\n'.join(f'{k}: {v}' for k, v in tvm.support.libinfo().items()))", applicable if you compile models):
Any other relevant information:

Additional context

The observed behavior is that only Mistral-7B-Instruct-v0.2 is generating garbage responses as shown below,

we did a major revamp to our android sdk https://llm.mlc.ai/docs/deploy/android.html which might help some of the issues


add piln.xyz

Piln is a new service that enables seamless (and crowdfunded) pinning of objects on IPFS. It requires no registration, pinning is paid for with Bitcoin over the Lightning Network. All currently pinned objects are public and everybody can extend the pin time of each others' objects. Although this is priced in satoshis and not dollars, the price is much cheaper than other services in the market, but bandwidth is reduced.
https://piln.xyz/

Forgot to mention: if window.ipfs is present Piln's dashboard will behave much better.

Does it just charge people to store content on the IPFS network? Why wouldn't someone just install an IPFS node themselves as the protocol intends? I think we should be encouraging people to install more nodes to grow the network vs consolidating into fewer nodes but maybe that is just me.

Does it just charge people to store content on the IPFS network? Why wouldn't someone just install an IPFS node themselves as the protocol intends? I think we should be encouraging people to install more nodes to grow the network vs consolidating into fewer nodes but maybe that is just me.

@lifeBCE what happens if you want to share a file and your computer is down, what happens when your computer crashes and you haven't got all the files pinned, what happens when the content was made in the cloud
Sent with GitHawk

Closing because the service was closed.

Just in time.


spidermonkey_115: init at 115.2.0

Description of changes
Based on https://src.fedoraproject.org/rpms/mozjs115/blob/rawhide/f/mozjs115.spec#_137.

js/src/configure.in is gone.
build/cargo-linker is ported to python.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@ofborg build spidermonkey_115 spidermonkey_115.passthru.tests

ERROR: SDK version "10.12" is too old. Please upgrade to at least 13.3. Try updating your system Xcode.

Oh well

Checking previous bumps, the darwin rebuild count should be small, and I don't aware of channel blockers, so hopefully we are fine here
@ofborg build spidermonkey_115 spidermonkey_115.passthru.tests


#6773 Product_of_Array

Have you read the Contributing Guidelines on Pull Requests?
Yes

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
#6773

Please check

But this issue was closed that why I am working on it
On Wed, May 5, 2021, 18:38 Agam Gupta @.***> wrote:

On Wed, May 5, 2021, 18:35 Ankit Aggarwal @.***>
wrote:

Closed #6779 https://github.com/TesseractCoding/NeoAlgo/pull/6779.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/TesseractCoding/NeoAlgo/pull/6779#event-4688877274,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASAFULUGGJURZXRTB4XRG7TTME7CVANCNFSM44CURI3A
.


Update to Meteor <IP_ADDRESS>

To make sure nothing is cached, remember to:

delete any ./.meteor/local
delete any ./node_modules
run 'meteor reset'

That seems to be working, thank you so much, still there are a lot to do to migrate 1.3+ :)


Wedding date bug

From user: 'When no wedding date nor divorce date has been entered in the “People Edit” screen, then the blank results in a date still being displayed. So, it’s a bogus date.'

You mean Anniversary date right?

FIxed by https://github.com/LiveChurchSolutions/ChumsApp/pull/37
Yep, got the confirmation it is the same date


build: added codecov configurations

Status
READY
Description
Added codecov conf
Impacted Areas in Application

Build

Current coverage is 100% (diff: 100%)

Merging #9 into master will not change coverage

@@           master    #9   diff @@
===================================
  Files           3     3
  Lines          19    19
  Methods         0     0
  Messages        0     0
  Branches        0     0
===================================
  Hits           19    19
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update 8279c3c...743c746


pinned verida packages version

Pinned verida-packages version to 1.x.x, due to the public version of verida-ts 2.0 being on  NPM we should pin the version in our demos to 1.x

Hey @cmcWebCode40 can we close this PR without merging?


[FLINK-21585][metrics] Add options for in-/excluding metrics

This PR introduces 2 new configuration options that allow users to define filters for each reporter that control whether a given metric is passed to the reporter or not.
Effectively this allows the user to select the metrics to be reported.

CI Failure seems unrelated, reported it here https://issues.apache.org/jira/browse/FLINK-26882

@flinkbot run azure


feat: Avro Container File output support

The support for writing Avro Container Files.
Classes that are generic for Parquet and Avro are refactored, renamed and moved to be public classes and inherited/used where applicable.
Avro specific output writer class and helpers are introduced.
Related GCS Connector PR: https://github.com/aiven/gcs-connector-for-apache-kafka/pull/267

Created https://github.com/aiven/commons-for-apache-kafka-connect/issues/159 to follow up improvements for Schema Builder


CIL version on conda install

Running:
conda create --name cil_test -c conda-forge -c intel -c ccpi/label/dev cil
gives:
 cil                ccpi/label/dev/linux-64::cil-21.3.1-np120py39_27
Which is the latest dev build _27
Running:
conda create --name cil_test -c conda-forge -c intel -c ccpi/label/dev cil tomophantom=1.4.10
gives
  cil                ccpi/label/dev/linux-64::cil-21.3.1-np120py39_27
  tomophantom        ccpi/label/dev/linux-64::tomophantom-1.4.10-np120py39_0
Also gives dev build _27 along with the requested tomophantom version. This is our current build instructions.
However we have added this constraint to meta.yaml:
https://github.com/TomographicImaging/CIL/blob/a0ed9a2c3baa3ec5b2624f21b59cf51fe74856f4/recipe/meta.yaml#L77
Which should constrain the tomophantom versions and make it unnecessary to specify 1.4.10
However:
conda create --name cil_test -c conda-forge -c intel -c ccpi/label/dev cil tomophantom
gives:
 cil                ccpi/label/dev/linux-64::cil-21.3.1-np120py39_20
tomophantom        ccpi/label/dev/linux-64::tomophantom-2.0.0_2-np120py39_0
So instead we get a rolled back version of CIL (dev build _20), which allows it to freely pick the tomophantom version as it is the version before the constraint was added.

Updating the build command is not going to be viable, IMHO.
The second option is much easier, although it will be a matter of chance which nightly build you get. But in the end that's the nightly build: it depends on the night!

This will require to simplify the version and remove the number here
https://github.com/TomographicImaging/CIL/blob/9d07ef1f4ac67dcc524f9bfb53136878da7e8984/recipe/meta.yaml#L3-L10

After #1228 running on vishighmem:
conda create --name cil_test -c conda-forge -c intel -c ccpi/label/dev cil would install
package                    |            build
---------------------------|-----------------
cil-21.3.1                 |     np120py39_29         342 KB  ccpi/label/dev

conda create --name cil_test -c conda-forge -c intel -c ccpi/label/dev cil tomophantom=1.4.10 would install
package                    |            build
---------------------------|-----------------
cil-21.3.1                 |     np120py39_29         342 KB  ccpi/label/dev
tomophantom-1.4.10         |      np120py39_0         185 KB  ccpi/label/dev

conda create --name cil_test -c conda-forge -c intel -c ccpi/label/dev cil tomophantom would install
package                    |            build
---------------------------|-----------------
cil-21.3.1                 |     np120py39_20         335 KB  ccpi/label/dev
tomophantom-2.0.0_2        |      np120py39_0         187 KB  ccpi/label/dev

So, it seems to roll back CIL again and select tomophantom 2

On Windows with mamba (0.15.3) we get what we describe in the recipe:
mamba create --name cil_test -c conda-forge -c intel -c ccpi/label/dev cil would install
package                    |            build
---------------------------|-----------------
cil 21.4.0                 |  np120py39_0             ccpi/label/dev/win-64

mamba create --name cil_test -c conda-forge -c intel -c ccpi/label/dev cil tomophantom=1.4.10 would install
package                    |            build
---------------------------|-----------------
cil 21.4.0                 |  np120py39_0             ccpi/label/dev/win-64
tomophantom 1.4.10         |  np120py39_0             ccpi/label/dev/win-64

mamba create --name cil_test -c conda-forge -c intel -c ccpi/label/dev cil tomophantom would install
package                    |            build
---------------------------|-----------------
cil 21.4.0                 |  np120py39_0             ccpi/label/dev/win-64
tomophantom 1.4.10         |  np120py39_0             ccpi/label/dev/win-64

now that #1276 has been merged, it may mean that this issue vanishes?

On Linux, vishighmem,  pinning the version of cil worked, without needing to specify matplotlib:
conda create --name cil -c conda-forge -c intel -c astra-toolbox -c ccpi cil astra-toolbox tigre ccpi-regulariser tomophantom=1.4.10
gave:
cil ccpi/linux-64::cil-21.3.0-np120py39_0
conda create --name cil=21.4.1 -c conda-forge -c intel -c astra-toolbox -c ccpi cil astra-toolbox tigre ccpi-regulariser tomophantom=1.4.10
gave:
 cil                ccpi/linux-64::cil-21.4.1-np120py39_0

Just spotted my mistake above, in my command I was setting the environment name to be cil=21.4.1 instead of the cil version to be 21.4.1!!


How to add api key with 4days and 15 days weather forecast ? i added the api key and it was only showing the current weather

@yashdholam07
You can use the student API key that provides 15 days of forecast data.
Please read this issue:
#25


chore: upgrade ruby to 3.3

Overview
This pull request encompasses the upgrade of our Ruby project from version 3.1 to version 3.3. The upgrade aims to leverage the latest features, enhancements, and performance improvements offered by Ruby 3.3, ensuring the long-term stability, security, and maintainability of our codebase.
Changes Made:

Updated .ruby-version to specify Ruby version 3.3

Integration Steps

Integrated Continuous Integration (CI) pipelines to ensure that all tests pass successfully with the upgraded Ruby version, and all the older supported versions.

Testing:

Executed comprehensive test suites to verify the correctness of our codebase after the Ruby 3.3 upgrade

Dependencies:

Ensured that all project dependencies are compatible with Ruby 3.3 and adhere to best practices for version management and dependency resolution

@ricardojcribeiro with this change the "required" checks need to be changed. since the "test" job was rewritten to be a matrix with the ruby versions


Appstraction download hangs and does not complete

Hi, downloading appstraction in both npm and yarn is hanging, this is the output from yarn:
yarn add v1.22.19
warning package.json: No license field
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
warning No license field
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning "appstraction ><EMAIL_ADDRESS>has unmet peer dependency "@types/node@*".
warning "appstraction ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "appstraction > ipa-extract-info > zipjs-browserify ><EMAIL_ADDRESS>has unmet peer dependency "browserify@>= 2.3".
[4/4] 🔨  Building fresh packages...
[1/4] ⠂ frida
[2/4] ⠂ cpu-features
[-/4] ⠂ waiting...
warning Error running install script for optional dependency: "/Users/jlee/node_modules/cpu-features: Command failed.
Exit code: 127
Command: node buildcheck.js > buildcheck.gypi && node-gyp rebuild
Arguments:
Directory: /Users/jlee/node_modules/cpu-features
[4/4] ⢀ appstraction

The first time you download appstraction, it has to download a whole bunch of dependencies. That can take a few minutes. That's probably what's happening.
But I can absolutely see how that looks like it's hanging. We should add some output that informs the user that this can take a while without any output.

I waited a considerable number of minutes but I can try it again - I think I was waiting for at least 10-30 minutes at that point!

Oh, that's a lot. :o
@zner0L How long did it take on your MacBook?

Likewise installing via npm is taking forever (more than 10-30 mins by now) and hanging after the step:
(##################) ⠹ reify:typescript: timing reifyNode:node_modules/typescript Completed in 3013ms

It shouldn’t take that long. I think sometimes pip fails if you don’t have a c compiler set up and then the installation might not complete. That would be my best guess. Do you have clang installed on your system?

I have clang installed! Are there other package managers I could try besides npm and yarn?

Well, we test against yarn, so if that fails there is bug we need to fix. Can you tell me the contents of your ~/.cache/autopy/venv directory?

It doesn't exist as I don't have autopy - do I need it?

Autopy should be installed automatically when you install appstraction. But @zner0L gave you the wrong path, on macOS, it's actually ~/Library/Caches/venv.

I'm currently testing this in a virtual machine with macOS Monterery 12.2.1 and Node 18.16.1 (I had to manually install Node 18 (brew install node@18)—frida-node doesn't work on newer versions currently). I'm seeing the same behaviour as you. npm i appstraction has now been running for almost half an hour and is still not done.
In the meantime, I've done some investigation. Here's what I found:

Autopy worked quickly and without issues. I have a Python installation in ~/Library/Caches/autopy/python/3.11.3 and a venv in ~/Library/Caches/autopy/venv/appstraction with the expected symlinks in ~/Library/Caches/autopy/venv/appstraction/bin.

Andromatic successfully created the licenses (~/Library/Caches/andromatic/licenses) and installed the Android command-line tools (~/Library/Caches/andromatic/cmdline-tools). That was also done within a few minutes.

Since then, the installation has been stuck. I can see a java process that has been at ~88% CPU usage the whole time. That process is essentially sdkmanager platform-tools build-tools;33.0.2 (the full command is a lot longer, but it's just the java command that the sdkmanager shell script expands into).

I'm not sure but I think that process is actually doing something. The CPU usage is fluctuating and the open files that Activity Monitor is showing are changing from time to time.

After 1:20h, it was still not finished and I gave up.

Turns out we already have an issue for this: https://github.com/tweaselORG/andromatic/issues/6

@synapticlee As a workaround until we have fixed and released this, you should be able to manually install Java, run /usr/libexec/java_home to find your Java home and export that as an env var (export JAVA_HOME=<path>).

Glad I wasn't the only one with this issue! I installed Java (I hadn't yet as this is a fairly new computer) and added it to the path. It is still hanging on the appstraction step though!

Did you also export the JAVA_HOME? And do you have anything in the ~/Library/Caches/autopy/venv and ~/Library/Caches/andromatic folders?

I did export JAVA_HOME, yes, and in '~/Library/Caches/autopy/venv' I have appstraction and cyanoacrylate folders which are not empty (bin        include    lib        pyvenv.cfg in cyanoacrylate, bin        data       include    lib        pyvenv.cfg share in appstraction). Nothing in ~/Library/Caches/andromatic

I have just released a new version of andromatic that should fix this bug, so until we release the fix in appstraction, you can also try this:
# Install the newest version of andromatic manually first.
yarn add andromatic
# Then install appstraction. This should use the new, fixed version of andromatic instead of the old version that appstraction currently depends on.
yarn add appstraction

Re: the earlier conversation, I didn't have JDK installed, only Java, so I downloaded the latest JDK (20) and still having the same issue sadly.
For the new fix, I successfully added andromatic but appstraction failed after that:
Error: ENOENT: no such file or directory, uv_cwd
    at process.wrappedCwd [as cwd] (node:internal/bootstrap/switches/does_own_process_state:126:28)
    at main (/usr/local/lib/node_modules/corepack/dist/corepack.js:16198:128)
    at Object.runMain (/usr/local/lib/node_modules/corepack/dist/corepack.js:16238:5)
    at Object.<anonymous> (/usr/local/lib/node_modules/corepack/dist/yarn.js:2:23)
    at Module._compile (node:internal/modules/cjs/loader:1218:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1272:10)
    at Module.load (node:internal/modules/cjs/loader:1081:32)
    at Module._load (node:internal/modules/cjs/loader:922:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:23:47

Wait, nevermind, I tried it again and it worked!! Thanks! Now trying to install the tweasel-cli

Hmm sadly while installing yarn global add tweasel-cli, it's still hanging on the appstraction step for many many minutes, even though yarn add appstraction was successful, do you know why?

Hmm sadly while installing yarn global add tweasel-cli, it's still hanging on the appstraction step for many many minutes, even though yarn add appstraction was successful, do you know why?

yarn global installs into a different node_modules directory than when you run yarn in a package, so yarn global add tweasel-cli won't use the updated andromatic that you installed elsewhere.
I haven't tested this but I would imagine that running yarn global add appstraction beforehand should fix this.

Hmm sadly while installing yarn global add tweasel-cli, it's still hanging on the appstraction step for many many minutes, even though yarn add appstraction was successful, do you know why?

yarn global installs into a different node_modules directory than when you run yarn in a package, so yarn global add tweasel-cli won't use the updated andromatic that you installed elsewhere.
I haven't tested this but I would imagine that running yarn global add appstraction beforehand should fix this.

Thanks, this makes sense! Running yarn global add andromatic worked but weirdly yarn global add appstraction is hanging, even though installing it locally worked earlier..

@zner0L I'm assuming the latter two were also actually yarn global?

After fiddling around a little I was able to download tweasel-cli! Thanks everyone for your help. Hopefully that's the end of the issues

Glad to hear that! Thanks for helping us debug.


Fix s390x-installer paths

@bors r+

:pushpin: Commit 43956dbadc5c1de82e9d83599416ef2aada91dde has been approved by JohnTitor
It is now in the queue for this repository.

:hourglass: Testing commit 43956dbadc5c1de82e9d83599416ef2aada91dde with merge a537611f1e6b74c03ac795adefafcaa9f20e2701...

:broken_heart: Test failed - checks-actions

@bors retry

:hourglass: Testing commit 43956dbadc5c1de82e9d83599416ef2aada91dde with merge 4df398162fab0d0b13b6ff7c7f4073a83d7d25d8...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13, checks-cirrus-freebsd-14
Approved by: JohnTitor
Pushing 4df398162fab0d0b13b6ff7c7f4073a83d7d25d8 to main...


Add fee APY to pool detail

Inspired by issue #64.
Leverages new individual fee revenue API endpoint thanks to @IbrarMakaveli.
I think this will be really valuable for LPrs shopping for pools over the long term. This metric reveals the relationship between volume vs liquidity vs fee rate. Interested to see if/how this will affect the tokenomics of osmosis.

Just noticed the "My Bondings" table refers to "Current APR." I could see updating the string to "Current Fee APY" since it is based on the past week of activity.

This is awesome, we can add fee earnings to the upcoming filter-by categories

Closing due to refactor


Move EC2 copy snapshot to functional tests

This refactors our EC2 copy snapshot customization tests to be functional instead of integration. The important part of these tests is to validate that we inject a correct presigned url for the cross region copy.
The motivation behind moving away from these integration tests is that they are rather slow, even timing out our waiters in the encrypted copy case.

Codecov Report

Merging #1881 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #1881   +/-   ##
========================================
  Coverage    92.56%   92.56%
========================================
  Files           53       53
  Lines        10001    10001
========================================
  Hits          9257     9257
  Misses         744      744

Continue to review full report at Codecov.

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


ADD NEW FEATURE: Mouse Gesture

Description of the new feature / enhancement

Use mouse gestures to trigger actions: maximize, minimize, close, etc.
Customize mouse actions.
Texture, like Snipaste.
Quickly adjust the volume: ALT + mouse wheel

Scenario when this would be used?
EVERY TIME
Supporting information
A similar software: https://github.com/shuax/MouseInc.Settings

/dup #19041


Configuration Docs page has non-functional example yaml

Our config parameters docs page starts out boldly with an example YAML config file, and we've observed users trying to copy-paste the example as a template for configuring their service.
Unfortunately, the example yaml is gobbledygook that doesn't doesn't compile, let alone work as a functional template...
At minimum, we should provide a config template that compiles. The best case would be to provide a minimal config example for each component -- it may be possible to provide one big config template that acts as a minimal working example for all components, but that might be more confusing than helpful. @aowen-uwmad, what do you think is ideal here? I'm inclined to think we create one minimal config per component.

In discussion with @aowen-uwmad, and we think a minimal config per component is good, but we'd also like to link out to osg-htc.org where we can host an example for each service of "how we do things in production"

What is the goal of a minimal config?
The best config is the default values, so our minimal config would be the default values. Depending on how dynamic the default values are this might cause pain if we change the default values without updating this minimal config.

There are some defaults that can't be filled in for generic cases, e.g. if you're setting up an origin, you still need to define the origin's exports, capabilities, federation discovery url, etc. I think most of our services can be set up as bare bones in ~15-20 lines of config. My goal is that someone could copy-paste, fill in a few blanks, and then run the service without any crashes/errors.

Ah makes sense, so this won't compile but it will be closer to compiling.


A.1 logic component

added COMMAND_ALIAS for all the commands including exit and history.

Coverage remained the same at 92.159% when pulling 66bb587935c4f0318661c93be7cb1a71f199d64e on DarrenCzen:A.1LogicComp into 392b6232191b3aca9a97d5ad333b5d078062678f on CS2103AUG2017-T15-B3:master.

Keep up the good work


Maximum URL size

According to Google's documentation for Static Map, the max size for url is 8192 characters, https://developers.google.com/maps/documentation/static-maps/intro#url-size-restriction.
But, when building an static map with gm.staticMap(params),
I get the following error:
Error: Request too long for google to handle (2048 characters).
at module.exports (.../node_modules/googlemaps/lib/utils/makeRequest.js:63:13)
at module.exports [as staticMap] (.../node_modules/googlemaps/lib/staticMap.js:116:10)
It's thrown an error before making a request for google, so it's internal.
Could it be fixed? Or should I make a fork for doing so? Or is there a reason as not working?

The setting is in lib/config/constants.json MAX_REQUEST_LENGTHS, you may modify and test it.

if there are only 2045 chars and the lmit is 8192... why is it throwing this error at all?

Because the error is being thrown by the node-googlemaps, and not by google itself.

Yes i am facing same problem. I created an issue also for the same.

In the /lib/requests/contants.json file it has the max values listed as 2048.
We could up that to 8192 and solve the issue.
"MAX_REQUEST_LENGTHS": {
"directions":          2048,
"distance-matrix":     2048,
"elevation":           -1,
"geocode":             2048,
"place-details":       2048,
"place-search-nearby": 2048,
"place-search-text":   2048,
"place-autocomplete":  2048,
"reverse-geocode":     2048,
"static-map":          2048,
"timezone":            2048,
"street-view":         2048
},


Performance test unexpected success in scrolltable

[SUCCESS!?!]
Reason: 'Index scan to find appropriate storeID starting point once the value index has been used to seek to /near/ the correct starting place causes this to be O(N) on the number of rows with duplicate values.'

xmantissa.test.test_scrolltable.InequalityPerformanceTests.test_rowsAfterItemWithDuplicatesAtStart
xmantissa.test.test_scrolltable.InequalityPerformanceTests.test_rowsBeforeItemWithDuplicatesAtStart

This is probably not worth spending any brain cycles on since I think the plan was to deprecate scrolltable anyway.

Oh, it was tdb that was going to be deprecated, not scrolltable. Well, maybe the .todo attribute should just be removed from these tests? I guess the SQLite query optimizer got smarter or something, although I think that just means the test isn't testing what it thinks it is anymore :/

Turns out these tests don't fail on the older version of SQLite that Travis has.


log4j 1.2.16 performance test issue

Description
When doing the performance test, we find that the performance reduce lots of when adding the log4j 1.2.16, many threads are blocking, as below image shows.

so.. upgrade this log4j to log4j2 ?
Environment

Pinpoint version: 1.7.2

Log4j is the bottleneck in a pressure situation for it's sync lock appender.
The following example is particularly obvious and deteriorated.
      //com.navercorp.pinpoint.profiler.sender.AsyncQueueingExecutor#execute
        if (!offer) {
            if (isWarn) {
                logger.warn("{} Drop data. queue is full. size:{}", executorName, queue.size());
            }
        }

Just upgrades to log4j2.

@lawrencewu
Hi~
You are using the debug log level.
It is recommended to use debug level.

@emeroad  seen from the picture, i guess this issue is something to do with class 'Slf4jPLoggerAdapter' which is under the profiler module.

@emeroad  I'm having a try.


Unable to build Tensorflow 2.3 on OSX with LLVM

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

OS Platform and Distribution: OSX 10.15.6
TensorFlow installed from: source
TensorFlow version: 2.3
Python version: 3.7
Installed using virtualenv? pip? conda?: conda
Bazel version (if compiling from source): 3.1.0
GCC/Compiler version (if compiling from source): clang version 10.0.1
CUDA/cuDNN version: No
GPU model and memory: No GPU

Describe the problem
I am unable to build from source and I keep getting errors around:

bazel-out/darwin-opt-exec-50AE0418/bin/tensorflow/core/protobuf/saved_object_graph.pb.h:131:3: error: expected identifier TRUE = 1,
In file included from bazel-out/darwin-opt-exec-50AE0418/bin/tensorflow/core/protobuf/meta_graph.pb.h:43:
bazel-out/darwin-opt-exec-50AE0418/bin/tensorflow/core/protobuf/saved_object_graph.pb.h:132:3: error: expected identifier
FALSE = 2,
^
/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/mach/boolean.h:85:17: note: expanded from macro 'FALSE'
#define FALSE   0

I tried with different compilers from brew but this error keeps appearing.
Provide the exact sequence of commands / steps that you executed before running into the problem
% export BAZEL_USE_CPP_ONLY_TOOLCHAIN=1
% export CC=/usr/local/opt/llvm/bin/clang
% bazel build --action_env CC=/usr/local/opt/llvm/bin/clang  --config=noaws --config=nogcp --config=mkl -c opt --copt=-O2 --cxxopt=-D_GLIBCXX_USE_CXX11_ABI=0 --copt=-mfma --copt=-mavx2 //tensorflow/tools/pip_package:build_pip_package
Any other info / logs
Starting local Bazel server and connecting to it...
INFO: Options provided by the client:
Inherited 'common' options: --isatty=1 --terminal_columns=174
INFO: Reading rc options for 'build' from /Users/stb/tensorflow/.bazelrc:
Inherited 'common' options: --experimental_repo_remote_exec
INFO: Reading rc options for 'build' from /Users/stb/tensorflow/.bazelrc:
'build' options: --apple_platform_type=macos --define framework_shared_object=true --define open_source_build=true --java_toolchain=//third_party/toolchains/java:tf_java_toolchain --host_java_toolchain=//third_party/toolchains/java:tf_java_toolchain --define=tensorflow_enable_mlir_generated_gpu_kernels=0 --define=use_fast_cpp_protos=true --define=allow_oversize_protos=true --spawn_strategy=standalone -c opt --announce_rc --define=grpc_no_ares=true --noincompatible_remove_legacy_whole_archive --noincompatible_prohibit_aapt1 --enable_platform_specific_config --config=short_logs --config=v2
INFO: Reading rc options for 'build' from /Users/stb/tensorflow/.tf_configure.bazelrc:
'build' options: --action_env PYTHON_BIN_PATH=/Users/stb/opt/anaconda3/envs/tfmkl_py37/bin/python3 --action_env PYTHON_LIB_PATH=/Users/stb/opt/anaconda3/envs/tfmkl_py37/lib/python3.7/site-packages --python_path=/Users/stb/opt/anaconda3/envs/tfmkl_py37/bin/python3 --config=xla --action_env TF_CONFIGURE_IOS=0
INFO: Found applicable config definition build:short_logs in file /Users/stb/tensorflow/.bazelrc: --output_filter=DONT_MATCH_ANYTHING
INFO: Found applicable config definition build:v2 in file /Users/stb/tensorflow/.bazelrc: --define=tf_api_version=2 --action_env=TF2_BEHAVIOR=1
INFO: Found applicable config definition build:xla in file /Users/stb/tensorflow/.bazelrc: --define=with_xla_support=true
INFO: Found applicable config definition build:noaws in file /Users/stb/tensorflow/.bazelrc: --define=no_aws_support=true
INFO: Found applicable config definition build:nogcp in file /Users/stb/tensorflow/.bazelrc: --define=no_gcp_support=true
INFO: Found applicable config definition build:mkl in file /Users/stb/tensorflow/.bazelrc: --define=build_with_mkl=true --define=enable_mkl=true --define=tensorflow_mkldnn_contraction_kernel=0 -c opt
INFO: Found applicable config definition build:macos in file /Users/stb/tensorflow/.bazelrc: --copt=-w --define=PREFIX=/usr --define=LIBDIR=$(PREFIX)/lib --define=INCLUDEDIR=$(PREFIX)/include --cxxopt=-std=c++14 --host_cxxopt=-std=c++14
DEBUG: Rule 'io_bazel_rules_docker' indicated that a canonical reproducible form can be obtained by modifying arguments shallow_since = "1556410077 -0400"
DEBUG: Repository io_bazel_rules_docker instantiated at:
no stack (--record_rule_instantiation_callstack not enabled)
Repository rule git_repository defined at:
/private/var/tmp/_bazel_stb/c17790719609824de969482a41b5bf78/external/bazel_tools/tools/build_defs/repo/git.bzl:195:18: in
INFO: Analyzed target //tensorflow/tools/pip_package:build_pip_package (390 packages loaded, 30618 targets configured).
INFO: Found 1 target...
ERROR: /Users/stb/tensorflow/tensorflow/compiler/mlir/tensorflow/BUILD:1620:1: C++ compilation of rule '//tensorflow/compiler/mlir/tensorflow:compile_mlir_util_no_tf_dialect_passes' failed (Exit 1)
In file included from tensorflow/compiler/mlir/tensorflow/utils/compile_mlir_util.cc:16:
In file included from ./tensorflow/compiler/mlir/tensorflow/utils/compile_mlir_util.h:29:
In file included from ./tensorflow/core/common_runtime/device.h:42:
In file included from ./tensorflow/core/framework/resource_mgr.h:32:
./tensorflow/core/framework/type_index.h:61:17: warning: unused variable 'hash_bit' [-Wunused-variable]
static bool hash_bit[1];
^
In file included from tensorflow/compiler/mlir/tensorflow/utils/compile_mlir_util.cc:45:
In file included from ./tensorflow/compiler/mlir/tensorflow/translate/import_model.h:25:
In file included from ./tensorflow/cc/saved_model/bundle_v2.h:28:
In file included from bazel-out/darwin-opt-exec-50AE0418/bin/tensorflow/core/protobuf/meta_graph.pb.h:43:
bazel-out/darwin-opt-exec-50AE0418/bin/tensorflow/core/protobuf/saved_object_graph.pb.h:131:3: error: expected identifier
TRUE = 1,
^
/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/mach/boolean.h:81:17: note: expanded from macro 'TRUE'
#define TRUE    1
^
In file included from tensorflow/compiler/mlir/tensorflow/utils/compile_mlir_util.cc:45:
In file included from ./tensorflow/compiler/mlir/tensorflow/translate/import_model.h:25:
In file included from ./tensorflow/cc/saved_model/bundle_v2.h:28:
In file included from bazel-out/darwin-opt-exec-50AE0418/bin/tensorflow/core/protobuf/meta_graph.pb.h:43:
bazel-out/darwin-opt-exec-50AE0418/bin/tensorflow/core/protobuf/saved_object_graph.pb.h:132:3: error: expected identifier
FALSE = 2,
^
/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/mach/boolean.h:85:17: note: expanded from macro 'FALSE'
#define FALSE   0
^
In file included from tensorflow/compiler/mlir/tensorflow/utils/compile_mlir_util.cc:45:
In file included from ./tensorflow/compiler/mlir/tensorflow/translate/import_model.h:25:
In file included from ./tensorflow/cc/saved_model/bundle_v2.h:28:
In file included from bazel-out/darwin-opt-exec-50AE0418/bin/tensorflow/core/protobuf/meta_graph.pb.h:43:
bazel-out/darwin-opt-exec-50AE0418/bin/tensorflow/core/protobuf/saved_object_graph.pb.h:138:31: error: cannot initialize a variable of type 'const tensorflow::ExperimentalCompile' with an rvalue of type 'int'
constexpr ExperimentalCompile ExperimentalCompile_MAX = FALSE;
^                         ~~~~~
1 warning and 3 errors generated.
Target //tensorflow/tools/pip_package:build_pip_package failed to build
Use --verbose_failures to see the command lines of failed build steps.
ERROR: /Users/stb/tensorflow/tensorflow/python/tools/BUILD:82:1 C++ compilation of rule '//tensorflow/compiler/mlir/tensorflow:compile_mlir_util_no_tf_dialect_passes' failed (Exit 1)
INFO: Elapsed time: 4667.715s, Critical Path: 318.82s
INFO: 5927 processes: 5927 local.
FAILED: Build did NOT complete successfully

@ianlokh
Just to verify did you follow the instructions mentioned here..
Plese, see tested build configurations from here.Thanks!

Hi Ravikyram, thanks for the follow up. Yes I followed the instructions but as my Xcode version is 12, I downloaded llvm 10.0.1 from brew and tried to compile using the llvm 10.0.1 as per build configuration. However I keep getting into the same issue

Hi as a correction, I used bazel 3.1 and llvm 10.0.1

@ianlokh
Just to verify did you follow the instructions mentioned here..
Please, see tested build configurations from here.Thanks!

Hi Ravikyram, thanks for the follow up. Yes I followed the instructions but as my Xcode version is 12, I downloaded llvm 10.0.1 from brew and tried to compile using the llvm 10.0.1 as per build configuration. However I keep getting into the same issue.
As a correction to the issue posted, I used bazel 3.1 and llvm 10.0.1. This is as per tested build configuration listed on the Tensorflow webpage

I am running into the same problem with XCode 12.
@ravikyram it seems like the problem has been introduced by 57f0a5e0b67720f0bc94e4decefc09fbff2f2416. Reverting the commit fixes the build issue for me.

I am running into the same problem with XCode 12.
@ravikyram it seems like the problem has been introduced by 57f0a5e. Reverting the commit fixes the build issue for me.

Hi Lukas, thanks for your inputs. How do I go about getting the previous commit? I ran "git clone https://github.com/tensorflow/tensorflow.git" and assumed that it was the latest stable version.

use ON/OFF instead of TRUE/FALSE should work.
diff --git a/tensorflow/core/protobuf/saved_object_graph.proto b/tensorflow/core/protobuf/saved_object_graph.proto
index e4293bcddf..c915d0224c 100644
--- a/tensorflow/core/protobuf/saved_object_graph.proto
+++ b/tensorflow/core/protobuf/saved_object_graph.proto
@@ -153,8 +153,8 @@ message SavedVariable {
 // See `tf.function` for details.
 enum ExperimentalCompile {
   NONE = 0;
-  TRUE = 1;
-  FALSE = 2;
+  ON = 1;
+  OFF = 2;
 }

 // Represents `FunctionSpec` used in `Function`. This represents a
diff --git a/tensorflow/python/saved_model/function_serialization.py b/tensorflow/python/saved_model/function_serialization.py
index 777af9bd5b..9660710c9d 100644
--- a/tensorflow/python/saved_model/function_serialization.py
+++ b/tensorflow/python/saved_model/function_serialization.py
@@ -50,8 +50,8 @@ def _serialize_function_spec(function_spec, coder):
   # See `tf.function` and the ExperimentalCompile proto for details.
   proto.experimental_compile = {
       None: saved_object_graph_pb2.ExperimentalCompile.NONE,
-      True: saved_object_graph_pb2.ExperimentalCompile.TRUE,
-      False: saved_object_graph_pb2.ExperimentalCompile.FALSE,
+      True: saved_object_graph_pb2.ExperimentalCompile.ON,
+      False: saved_object_graph_pb2.ExperimentalCompile.OFF,
   }.get(function_spec.experimental_compile)

   return proto

Hi Lukas and Koan-sin, thank you for your help!
I eventually managed to compile it as suggested by Lukas - to revert to the previous commit.
git checkout b95f88a5e759367ae80bad988fdd35cbd0f604b4
Thanks again!