Gigantic cube operation failed a stress test

I tried stress-testing our dask stuff by doing some operations on a 680 GB cube.
The stress test is this:
https://github.com/ALMA-IMF/reduction/blob/1fecfdceb94ab5a673cc4ce7bce9ee82224033f9/reduction/cube_finalizing.py
which loads 5 cubes, the image, residual, model, psf, and pb cubes.  4 of those are combined in some way; the PSF cube is just measured on its own.
The stress-test results look like this:
In [1]: from spectral_cube import SpectralCube

In [2]: import dask.array as da
   ...: from dask.diagnostics import ProgressBar

In [3]: %run /orange/adamginsburg/ALMA_IMF/reduction/reduction/cube_finalizing.py

In [4]: with ProgressBar():
   ...:     beam_correct_cube('S255IR-SMA1_sci.spw3.cube.I.manual')
   ...:
/blue/adamginsburg/adamginsburg/repos/casa-formats-io/casa_formats_io/casa_dask.py:230: RuntimeWarning: divide by zero encountered in long_scalars
  factors = [f for f in range(stacks[dim] + 1) if stacks[dim] % f == 0]
WARNING: BeamWarning: No beam information found in CASA image. [spectral_cube.io.casa_image]
WARNING: StokesWarning: Cube is a Stokes cube, returning spectral cube for I component [spectral_cube.io.core]
/blue/adamginsburg/adamginsburg/repos/casa-formats-io/casa_formats_io/casa_dask.py:230: RuntimeWarning: divide by zero encountered in long_scalars
  factors = [f for f in range(stacks[dim] + 1) if stacks[dim] % f == 0]
WARNING: StokesWarning: Cube is a Stokes cube, returning spectral cube for I component [spectral_cube.io.core]
/blue/adamginsburg/adamginsburg/repos/casa-formats-io/casa_formats_io/casa_dask.py:230: RuntimeWarning: divide by zero encountered in long_scalars
  factors = [f for f in range(stacks[dim] + 1) if stacks[dim] % f == 0]
WARNING: BeamWarning: No beam information found in CASA image. [spectral_cube.io.casa_image]
WARNING: StokesWarning: Cube is a Stokes cube, returning spectral cube for I component [spectral_cube.io.core]
/blue/adamginsburg/adamginsburg/repos/casa-formats-io/casa_formats_io/casa_dask.py:230: RuntimeWarning: divide by zero encountered in long_scalars
  factors = [f for f in range(stacks[dim] + 1) if stacks[dim] % f == 0]
WARNING: BeamWarning: No beam information found in CASA image. [spectral_cube.io.casa_image]
WARNING: StokesWarning: Cube is a Stokes cube, returning spectral cube for I component [spectral_cube.io.core]
INFO: Completed reading. t=3.079984188079834 [unknown]
INFO: Starting minimize. t=3.315718650817871 [unknown]
[########################################] | 100% Completed | 19min  9.6s
[########################################] | 100% Completed | 18min 12.6s
[########################################] | 100% Completed | 17min 29.8s
INFO: Completed minimize. t=3300.095191717148.  minimizing took 3296.779483795166 [unknown]
INFO: Completed minslice. t=3300.7892508506775 [unknown]
INFO: Epsilon beginning. t=3300.7909491062164 [unknown]
[########################################] | 100% Completed |  2.2s
[########################################] | 100% Completed |  1.3s

******* SNIP : cut for brevity *********

[########################################] | 100% Completed |  1.3s
[########################################] | 100% Completed |  0.2s
INFO: Epsilon completed. t=11251.39980506897, eps took 7950.6088609695435 [unknown]
INFO: Convolving.  t=11251.443447828293 [unknown]
INFO: Done convolving, now rescaling.  t=11252.022993803024 [unknown]
creating restor
/orange/adamginsburg/miniconda3/envs/python39/lib/python3.9/site-packages/dask/array/core.py:4458: PerformanceWarning: Increasing number of chunks by factor of 10
  result = blockwise(
done creating restor
INFO: Done rescaling.  t=11254.715781450272 [unknown]
WARNING: VerifyWarning: Keyword name 'JvM_epsilon_max' is greater than 8 characters or contains characters not allowed by the FITS standard; a HIERARCH card will be created. [astropy.io.fits.card]
WARNING: VerifyWarning: Keyword name 'JvM_epsilon_min' is greater than 8 characters or contains characters not allowed by the FITS standard; a HIERARCH card will be created. [astropy.io.fits.card]
WARNING: VerifyWarning: Keyword name 'JvM_epsilon_median' is greater than 8 characters or contains characters not allowed by the FITS standard; a HIERARCH card will be created. [astropy.io.fits.card]
INFO: Beginning JvM write.  t=11254.803322076797 [unknown]
[###                                     ] | 9% Completed |  1hr 20min 35.3sKilled

the files:
$ du -csh S255IR-SMA1_sci.spw3.cube.I.manual*
680G    S255IR-SMA1_sci.spw3.cube.I.manual.image
375G    S255IR-SMA1_sci.spw3.cube.I.manual.image.pbcor
15G     S255IR-SMA1_sci.spw3.cube.I.manual.JvM.image.fits
660G    S255IR-SMA1_sci.spw3.cube.I.manual.mask
660G    S255IR-SMA1_sci.spw3.cube.I.manual.model
680G    S255IR-SMA1_sci.spw3.cube.I.manual.pb
660G    S255IR-SMA1_sci.spw3.cube.I.manual.psf
680G    S255IR-SMA1_sci.spw3.cube.I.manual.residual
84K     S255IR-SMA1_sci.spw3.cube.I.manual.sumwt
4.4T    total

It was running on a machine with 32 GB of memory allocated.
It looks like it died only a small fraction of the way through writing.
This probably indicates that somewhere along the path, there is a compute step happening - or something that is loading to memory instead of dumping direct to disk.

This was done based on #783

I'm trying a simpler test:
In [1]: from spectral_cube import SpectralCube

In [2]: from dask.diagnostics import ProgressBar

In [3]: with ProgressBar():
   ...:     cube = SpectralCube.read('S255IR-SMA1_sci.spw3.cube.I.manual.image')
   ...:     print(f"Loaded cube {cube}")
   ...:     result = cube*cube
   ...:     print(f"Created square cube {result}")
   ...:     result.write("test.fits")
   ...:     print("Wrote test.fits")
   ...:
/blue/adamginsburg/adamginsburg/repos/casa-formats-io/casa_formats_io/casa_dask.py:230: RuntimeWarning: divide by zero encountered in long_scalars
  factors = [f for f in range(stacks[dim] + 1) if stacks[dim] % f == 0]
WARNING: StokesWarning: Cube is a Stokes cube, returning spectral cube for I component [spectral_cube.io.core]
Loaded cube DaskVaryingResolutionSpectralCube with shape=(1920, 9600, 9600) and unit=Jy / beam and chunk size (10, 100, 9600):
 n_x:   9600  type_x: RA---SIN  unit_x: deg    range:    93.219155 deg:   93.230930 deg
 n_y:   9600  type_y: DEC--SIN  unit_y: deg    range:    17.984139 deg:   17.995338 deg
 n_s:   1920  type_s: FREQ      unit_s: Hz     range:<PHONE_NUMBER>18.890 Hz:221436973845.577 Hz
Created square cube DaskVaryingResolutionSpectralCube with shape=(1920, 9600, 9600) and unit=Jy2 / beam2 and chunk size (10, 100, 9600):
 n_x:   9600  type_x: RA---SIN  unit_x: deg    range:    93.219155 deg:   93.230930 deg
 n_y:   9600  type_y: DEC--SIN  unit_y: deg    range:    17.984139 deg:   17.995338 deg
 n_s:   1920  type_s: FREQ      unit_s: Hz     range:<PHONE_NUMBER>18.890 Hz:221436973845.577 Hz
[                                        ] | 0% Completed | 10.7s

hmm, looks like a success:
In [1]: from spectral_cube import SpectralCube

In [2]: from dask.diagnostics import ProgressBar

In [3]: with ProgressBar():
   ...:     cube = SpectralCube.read('S255IR-SMA1_sci.spw3.cube.I.manual.image')
   ...:     print(f"Loaded cube {cube}")
   ...:     result = cube*cube
   ...:     print(f"Created square cube {result}")
   ...:     result.write("test.fits")
   ...:     print("Wrote test.fits")
   ...:
/blue/adamginsburg/adamginsburg/repos/casa-formats-io/casa_formats_io/casa_dask.py:230: RuntimeWarning: divide by zero encountered in long_scalars
  factors = [f for f in range(stacks[dim] + 1) if stacks[dim] % f == 0]
WARNING: StokesWarning: Cube is a Stokes cube, returning spectral cube for I component [spectral_cube.io.core]
Loaded cube DaskVaryingResolutionSpectralCube with shape=(1920, 9600, 9600) and unit=Jy / beam and chunk size (10, 100, 9600):
 n_x:   9600  type_x: RA---SIN  unit_x: deg    range:    93.219155 deg:   93.230930 deg
 n_y:   9600  type_y: DEC--SIN  unit_y: deg    range:    17.984139 deg:   17.995338 deg
 n_s:   1920  type_s: FREQ      unit_s: Hz     range:<PHONE_NUMBER>18.890 Hz:221436973845.577 Hz
Created square cube DaskVaryingResolutionSpectralCube with shape=(1920, 9600, 9600) and unit=Jy2 / beam2 and chunk size (10, 100, 9600):
 n_x:   9600  type_x: RA---SIN  unit_x: deg    range:    93.219155 deg:   93.230930 deg
 n_y:   9600  type_y: DEC--SIN  unit_y: deg    range:    17.984139 deg:   17.995338 deg
 n_s:   1920  type_s: FREQ      unit_s: Hz     range:<PHONE_NUMBER>18.890 Hz:221436973845.577 Hz
[####################################    ] | 91% Completed |  3hr 42min 33.0s

so I suspect the convolution plays a role here... dang.

This is a warning that should truly inspire fear:
  File "/blue/adamginsburg/adamginsburg/repos/spectral-cube/spectral_cube/dask_spectral_cube.py", line 1545, in convfunc
    out[index] = convolve(img[index], kernel, normalize_kernel=True, **kwargs)
  File "/orange/adamginsburg/miniconda3/envs/python39/lib/python3.9/site-packages/astropy/nddata/decorators.py", line 246, in wrapper
    result = func(data, *args, **kwargs)
  File "/orange/adamginsburg/miniconda3/envs/python39/lib/python3.9/site-packages/astropy/convolution/convolve.py", line 650, in convolve_fft
    raise ValueError(f"Size Error: Arrays will be {human_file_size(array_size_B)}.  "
ValueError: Size Error: Arrays will be 1.4G.  Use allow_huge=True to override this exception.

wow, convolution is not fast.
In [11]: with ProgressBar():
    ...:     cube = SpectralCube.read('S255IR-SMA1_sci.spw3.cube.I.manual.image')
    ...:     print(f"Loaded cube {cube}")
    ...:     result = cube.convolve_to(cube.beams.common_beam(), allow_huge=True)
    ...:     print(f"Created smooth cube {result}")
    ...:     result.write("test.fits")
    ...:     print("Wrote test.fits")
    ...:
/blue/adamginsburg/adamginsburg/repos/casa-formats-io/casa_formats_io/casa_dask.py:230: RuntimeWarning: divide by zero encountered in long_scalars
  factors = [f for f in range(stacks[dim] + 1) if stacks[dim] % f == 0]
WARNING: StokesWarning: Cube is a Stokes cube, returning spectral cube for I component [spectral_cube.io.core]
Loaded cube DaskVaryingResolutionSpectralCube with shape=(1920, 9600, 9600) and unit=Jy / beam and chunk size (10, 100, 9600):
 n_x:   9600  type_x: RA---SIN  unit_x: deg    range:    93.219155 deg:   93.230930 deg
 n_y:   9600  type_y: DEC--SIN  unit_y: deg    range:    17.984139 deg:   17.995338 deg
 n_s:   1920  type_s: FREQ      unit_s: Hz     range:<PHONE_NUMBER>18.890 Hz:221436973845.577 Hz
Created smooth cube DaskSpectralCube with shape=(1920, 9600, 9600) and unit=Jy / beam and chunk size (1, 9600, 9600):
 n_x:   9600  type_x: RA---SIN  unit_x: deg    range:    93.219155 deg:   93.230930 deg
 n_y:   9600  type_y: DEC--SIN  unit_y: deg    range:    17.984139 deg:   17.995338 deg
 n_s:   1920  type_s: FREQ      unit_s: Hz     range:<PHONE_NUMBER>18.890 Hz:221436973845.577 Hz
[                                        ] | 1% Completed | 11hr  4min 46.9s

And that's with FFT? Though for a small kernel, the plain astropy.convolution.convolve might actually be faster.

It will be fast-ish with fft:
In [12]: %timeit astropy.convolution.convolve_fft(img, astropy.convolution.Gaussian2DKernel(3), allow_huge=True)
21.3 s ± 1.58 s per loop (mean ± std. dev. of 7 runs, 1 loop each)

In [16]: with ProgressBar():
    ...:     cube = SpectralCube.read('S255IR-SMA1_sci.spw3.cube.I.manual.image')
    ...:     print(f"Loaded cube {cube}")
    ...:     result = cube.convolve_to(cube.beams.common_beam(), allow_huge=True, convolve=astropy.convolution.convolve_fft)
    ...:     print(f"Created smooth cube {result}")
    ...:     result.write("test.fits")
    ...:     print("Wrote test.fits")
    ...:
/blue/adamginsburg/adamginsburg/repos/casa-formats-io/casa_formats_io/casa_dask.py:230: RuntimeWarning: divide by zero encountered in long_scalars
  factors = [f for f in range(stacks[dim] + 1) if stacks[dim] % f == 0]
WARNING: StokesWarning: Cube is a Stokes cube, returning spectral cube for I component [spectral_cube.io.core]
Loaded cube DaskVaryingResolutionSpectralCube with shape=(1920, 9600, 9600) and unit=Jy / beam and chunk size (10, 100, 9600):
 n_x:   9600  type_x: RA---SIN  unit_x: deg    range:    93.219155 deg:   93.230930 deg
 n_y:   9600  type_y: DEC--SIN  unit_y: deg    range:    17.984139 deg:   17.995338 deg
 n_s:   1920  type_s: FREQ      unit_s: Hz     range:<PHONE_NUMBER>18.890 Hz:221436973845.577 Hz
Created smooth cube DaskSpectralCube with shape=(1920, 9600, 9600) and unit=Jy / beam and chunk size (1, 9600, 9600):
 n_x:   9600  type_x: RA---SIN  unit_x: deg    range:    93.219155 deg:   93.230930 deg
 n_y:   9600  type_y: DEC--SIN  unit_y: deg    range:    17.984139 deg:   17.995338 deg
 n_s:   1920  type_s: FREQ      unit_s: Hz     range:<PHONE_NUMBER>18.890 Hz:221436973845.577 Hz
[                                        ] | 1% Completed | 25min 14.4s

21s * 1920 = 11h
100 * 25m = 42h
so somewhere in that range is expected.

I thought astropy.convolution.convolve_fft is the default already.

no, for dask_spectral_cube, it's direct convolve

Ah, wrong subclass again!

Looks like ~35h anticipated, so I'm gonna stop it:
In [16]: with ProgressBar():
    ...:     cube = SpectralCube.read('S255IR-SMA1_sci.spw3.cube.I.manual.image')
    ...:     print(f"Loaded cube {cube}")
    ...:     result = cube.convolve_to(cube.beams.common_beam(), allow_huge=True, convolve=astropy.convolution.convolve_fft)
    ...:     print(f"Created smooth cube {result}")
    ...:     result.write("test.fits")
    ...:     print("Wrote test.fits")
    ...:
/blue/adamginsburg/adamginsburg/repos/casa-formats-io/casa_formats_io/casa_dask.py:230: RuntimeWarning: divide by zero encountered in long_scalars
  factors = [f for f in range(stacks[dim] + 1) if stacks[dim] % f == 0]
WARNING: StokesWarning: Cube is a Stokes cube, returning spectral cube for I component [spectral_cube.io.core]
Loaded cube DaskVaryingResolutionSpectralCube with shape=(1920, 9600, 9600) and unit=Jy / beam and chunk size (10, 100, 9600):
 n_x:   9600  type_x: RA---SIN  unit_x: deg    range:    93.219155 deg:   93.230930 deg
 n_y:   9600  type_y: DEC--SIN  unit_y: deg    range:    17.984139 deg:   17.995338 deg
 n_s:   1920  type_s: FREQ      unit_s: Hz     range:<PHONE_NUMBER>18.890 Hz:221436973845.577 Hz
Created smooth cube DaskSpectralCube with shape=(1920, 9600, 9600) and unit=Jy / beam and chunk size (1, 9600, 9600):
 n_x:   9600  type_x: RA---SIN  unit_x: deg    range:    93.219155 deg:   93.230930 deg
 n_y:   9600  type_y: DEC--SIN  unit_y: deg    range:    17.984139 deg:   17.995338 deg
 n_s:   1920  type_s: FREQ      unit_s: Hz     range:<PHONE_NUMBER>18.890 Hz:221436973845.577 Hz
[####                                    ] | 11% Completed |  3hr 51min 24.2s

I don't think this adds up as I want it to; it's too slow.

But you do need the frames convolved to a common resolution?
Should be possible to get some speedup by passing the multi-threaded FFTs from Scipy or PyFFTW, and in particular trimming the memory footprint (if you can go with single precision), to astropy.convolution
convolve_fft(img, kernel, fftn = lambda a: scipy.fft.fft2(a, workers=-1), ifftn = lambda a: scipy.fft.ifft2(a, workers=-1), complex_dtype=np.complex64)
and handing that over to convolve_to, but it won't be orders of magnitude, I am afraid.

Yeah, this isn't a case where I actually need this for science right now, but this is an incredibly common use case and one where CASA has optimized performance a lot.
I like the idea of switching to single-precision and multithreaded FFTs.  Might also try using rfft.
I've tried also using dask's multithreading/multiprocessing, but that had no effect (I tried with dask.config.set(scheduler='processes', num_workers=8): and  with dask.config.set(scheduler='threads', pool=ThreadPool(20)): and  with dask.config.set(scheduler='threads'):, all with the same outcome).

But not using dask.array.fft I assume? Seems nontrivial to get around casting to ndarray in astropy.convolution.

No, hm, ok, maybe that's the problem.  I'll try that too

The FFT itself seems unrealistically fast (1 ms), looks like %timeit is stumbling there over delayed execution.

yeah for timeit tests, you may need to force a .compute

ETA ~25h for this one:
In [46]: with ProgressBar():
    ...:     # skip with dask.config.set(scheduler='processes', num_workers=8):
    ...:         cube = SpectralCube.read('S255IR-SMA1_sci.spw3.cube.I.manual.image')
    ...:         print(f"Loaded cube {cube}")
    ...:         result = cube.convolve_to(cube.beams.common_beam(), allow_huge=True, convolve=astropy.convolution.convolve_fft, fftn=lambda x: scipy.fft.fftn(x, workers=8), ifftn=lambda x: scipy.fft.ifftn(x, workers=8))
    ...:         print(f"Created smooth cube {result}")
    ...:         result.write("test.fits")
    ...:         print("Wrote test.fits")
    ...:
/blue/adamginsburg/adamginsburg/repos/casa-formats-io/casa_formats_io/casa_dask.py:230: RuntimeWarning: divide by zero encountered in long_scalars
  factors = [f for f in range(stacks[dim] + 1) if stacks[dim] % f == 0]
WARNING: StokesWarning: Cube is a Stokes cube, returning spectral cube for I component [spectral_cube.io.core]
Loaded cube DaskVaryingResolutionSpectralCube with shape=(1920, 9600, 9600) and unit=Jy / beam and chunk size (10, 100, 9600):
 n_x:   9600  type_x: RA---SIN  unit_x: deg    range:    93.219155 deg:   93.230930 deg
 n_y:   9600  type_y: DEC--SIN  unit_y: deg    range:    17.984139 deg:   17.995338 deg
 n_s:   1920  type_s: FREQ      unit_s: Hz     range:<PHONE_NUMBER>18.890 Hz:221436973845.577 Hz
Created smooth cube DaskSpectralCube with shape=(1920, 9600, 9600) and unit=Jy / beam and chunk size (1, 9600, 9600):
 n_x:   9600  type_x: RA---SIN  unit_x: deg    range:    93.219155 deg:   93.230930 deg
 n_y:   9600  type_y: DEC--SIN  unit_y: deg    range:    17.984139 deg:   17.995338 deg
 n_s:   1920  type_s: FREQ      unit_s: Hz     range:<PHONE_NUMBER>18.890 Hz:221436973845.577 Hz
[                                        ] | 2% Completed | 33min 24.3s

so <2x boost, if anything.  Trying with dask fft now

dang, astropy convolution doesn't play nice with dask.fft:
  File "/blue/adamginsburg/adamginsburg/repos/spectral-cube/spectral_cube/dask_spectral_cube.py", line 1545, in convfunc
    out[index] = convolve(img[index], kernel, normalize_kernel=True, **kwargs)
  File "/orange/adamginsburg/miniconda3/envs/python39/lib/python3.9/site-packages/astropy/nddata/decorators.py", line 246, in wrapper
    result = func(data, *args, **kwargs)
  File "/orange/adamginsburg/miniconda3/envs/python39/lib/python3.9/site-packages/astropy/convolution/convolve.py", line 782, in convolve_fft
    arrayfft = fftn(bigarray)
  File "/orange/adamginsburg/miniconda3/envs/python39/lib/python3.9/site-packages/dask/array/fft.py", line 180, in func
    if len(a.chunks[each_axis]) != 1:
AttributeError: 'numpy.ndarray' object has no attribute 'chunks'

this might be an issue I need to tackle in astropy core

What I meant. Or clone the entire convolve_fft to create an own, daskified version.

yeah, this is really unfortunate; we'd like to be able to work with dask arrays, but np.array(daskarr) triggering a compute makes the code a total mess.

see https://github.com/astropy/astropy/pull/12596 as an attempt to enable this.
@dhomeier yes I will definitely do the computation at some point, but we want dask to handle the "do compute; write to disk; unload from memory; do next compute" stuff


TypeError: 'undefined' is not an object (evaluating '_ref.length')

Seeing this intermittently in our test suite with Poltergeist 1.6.0 (also tested master) and PhantomJS 1.9.8 on CircleCI. Any tips on diagnosing the problem?
     Capybara::Poltergeist::BrowserError:
       There was an error inside the PhantomJS portion of Poltergeist. This is probably a bug, so please report it.

       TypeError: 'undefined' is not an object (evaluating '_ref.length')
       [object Object]
           at /home/ubuntu/sitthetest/vendor/bundle/ruby/2.2.0/gems/poltergeist-1.6.0/lib/capybara/poltergeist/client/compiled/web_page.js:447
           at /home/ubuntu/sitthetest/vendor/bundle/ruby/2.2.0/gems/poltergeist-1.6.0/lib/capybara/poltergeist/client/compiled/web_page.js:42
           at /home/ubuntu/sitthetest/vendor/bundle/ruby/2.2.0/gems/poltergeist-1.6.0/lib/capybara/poltergeist/client/compiled/node.js:23
           at /home/ubuntu/sitthetest/vendor/bundle/ruby/2.2.0/gems/poltergeist-1.6.0/lib/capybara/poltergeist/client/compiled/node.js:48
           at /home/ubuntu/sitthetest/vendor/bundle/ruby/2.2.0/gems/poltergeist-1.6.0/lib/capybara/poltergeist/client/compiled/browser.js:302
           at /home/ubuntu/sitthetest/vendor/bundle/ruby/2.2.0/gems/poltergeist-1.6.0/lib/capybara/poltergeist/client/compiled/browser.js:320
           at /home/ubuntu/sitthetest/vendor/bundle/ruby/2.2.0/gems/poltergeist-1.6.0/lib/capybara/poltergeist/client/compiled/browser.js:51
           at /home/ubuntu/sitthetest/vendor/bundle/ruby/2.2.0/gems/poltergeist-1.6.0/lib/capybara/poltergeist/client/compiled/main.js:21
           at /home/ubuntu/sitthetest/vendor/bundle/ruby/2.2.0/gems/poltergeist-1.6.0/lib/capybara/poltergeist/client/compiled/connection.js:16
           at /home/ubuntu/sitthetest/vendor/bundle/ruby/2.2.0/gems/poltergeist-1.6.0/lib/capybara/poltergeist/client/compiled/connection.js:1

Here’s the debug output from Poltergeist at the point of failure:
{"name":"find","args":["xpath",".//input[./@type = 'submit' or ./@type = 'reset' or ./@type = 'image' or ./@type = 'button'][((./@id = 'Sit the Test' or ./@value = 'Sit the Test') or ./@title = 'Sit the Test')] | .//input[./@type = 'image'][./@alt = 'Sit the Test'] | .//button[(((./@id = 'Sit the Test' or ./@value = 'Sit the Test') or normalize-space(string(.)) = 'Sit the Test') or ./@title = 'Sit the Test')] | .//input[./@type = 'image'][./@alt = 'Sit the Test']"]}
{"response":{"page_id":3,"ids":[2]}}
{"name":"visible","args":[3,2]}
{"response":true}
{"name":"disabled","args":[3,2]}
{"response":false}
{"name":"click","args":[3,2]}
{"error":{"name":"Poltergeist.BrowserError","args":["TypeError: 'undefined' is not an object (evaluating '_ref.length')","[object Object]\n    at /home/ubuntu/sitthetest/vendor/bundle/ruby/2.2.0/bundler/gems/poltergeist-e3fc25919afb/lib/capybara/poltergeist/client/compiled/web_page.js:456\n    at /home/ubuntu/sitthetest/vendor/bundle/ruby/2.2.0/bundler/gems/poltergeist-e3fc25919afb/lib/capybara/poltergeist/client/compiled/web_page.js:42\n    at /home/ubuntu/sitthetest/vendor/bundle/ruby/2.2.0/bundler/gems/poltergeist-e3fc25919afb/lib/capybara/poltergeist/client/compiled/node.js:23\n    at /home/ubuntu/sitthetest/vendor/bundle/ruby/2.2.0/bundler/gems/poltergeist-e3fc25919afb/lib/capybara/poltergeist/client/compiled/node.js:48\n    at /home/ubuntu/sitthetest/vendor/bundle/ruby/2.2.0/bundler/gems/poltergeist-e3fc25919afb/lib/capybara/poltergeist/client/compiled/browser.js:302\n    at /home/ubuntu/sitthetest/vendor/bundle/ruby/2.2.0/bundler/gems/poltergeist-e3fc25919afb/lib/capybara/poltergeist/client/compiled/browser.js:320\n    at /home/ubuntu/sitthetest/vendor/bundle/ruby/2.2.0/bundler/gems/poltergeist-e3fc25919afb/lib/capybara/poltergeist/client/compiled/browser.js:51\n    at /home/ubuntu/sitthetest/vendor/bundle/ruby/2.2.0/bundler/gems/poltergeist-e3fc25919afb/lib/capybara/poltergeist/client/compiled/main.js:21\n    at /home/ubuntu/sitthetest/vendor/bundle/ruby/2.2.0/bundler/gems/poltergeist-e3fc25919afb/lib/capybara/poltergeist/client/compiled/connection.js:16\n    at /home/ubuntu/sitthetest/vendor/bundle/ruby/2.2.0/bundler/gems/poltergeist-e3fc25919afb/lib/capybara/poltergeist/client/compiled/connection.js:1"]}}

This certainly doesn’t seem like a recent issue. I’ve reproduced it on Poltergeist 1.5.1 and PhantomJS 1.9.7 as well.

This certainly doesn’t seem like a recent issue. I’ve reproduced it on Poltergeist 1.5.1 and PhantomJS 1.9.7 as well.

Can you show us a test case?

It’s a fairly complex app, so whittling it down to a test case would prove difficult. Is there anything else I can do? Is there some way to get more information out of PhantomJS, for example?
Do I understand correctly that the TypeError: 'undefined' is not an object (evaluating '_ref.length') is being generated by our application’s code and not anything internal to Poltergeist or PhantomJS? If so, I’d love to get a filename and line number or even a stack trace. Is there some way to get that out of PhantomJS?

It looks like poltergeist issue for me, so we need to track it down.

@route I’m not opposed to giving someone temporary access to our code and CI environment (where I’m currently able to reproduce the issue 100% reliably by running a single test). Contact me at<EMAIL_ADDRESS>if you’d like to set something up.
Failing that, I’ve got a long road ahead to whittle this big app down to a simple test case. Any advice or alternatives welcome.

Interestingly, running my app without stylesheets prevents the error from occurring. I’m continuing to try to simplify it to something approaching a test case.

Yes sure let's figure it out! I'll give you some direction for now and mail you a little bit later if you won't solve this. Basically everything works good in my opinion, the link is found and when you try to click it poltergeist sends command click to PhantomJS, browser.mouse_event function is called and then node.mouseEvent which calls mouseEventTest next, which is delegated in the end to agent.mouseEventTest. So I would start with cloning the poltergeist repo, then you can add this cloned repo to your app like this gem 'poltergeist', path: 'where-it-is-locally', this will give you an ability to patch/debug poltergeist, then you can start debugging the result of that last function mouseEventTest in agent.coffee. Don't forget to recompile coffee to js with rake compile

@route Thanks! Will do.

@route We think we may have found the culprit. The page under test is similar to this: https://sitthetest.com/sitthetest/css-core The test is failing when it attempts to click the green “Sit the Test” button. Notice the blue UserVoice speech bubble in the bottom-right, which depending on the viewport size can overlap the button. Could that lead to the error we’re seeing here, do you think?
Here’s the screenshot that the test is generating on failure:

As you an see, the speech bubble is nowhere near that button, but perhaps it’s using a different viewport size for the screenshot than it is for the test?
I’m happy to continue working towards debugging the issue if you think it’s still worthwhile. Let me know.

OK, that screenshot was being generated by the capybara-screenshot gem. Here’s a screenshot generated by Poltergeist just before the button click:

The floating blue speech bubble isn’t visible for some reason, but if I set my desktop browser to a viewport of that size, it definitely sits right over the button. What do you think? Mystery solved? Still worth debugging if only to handle issues like this better?

We have an ability in Poltergeist to catch overlapping elements and the error is different for this sort of issues.. It still looks for me like poltergeist issue, we just have to find why, what and when it's happening :)

@route OK, I’ll get to work on some debugging tomorrow. In the meantime, however, we’ve found that both disabling the UserVoice widget and increasing the Poltergeist window size resolve the test failure completely in our case.

Sounds reasonable to me since we see cut off button, but still weird :)

OK, I’ve done some debugging and I can confirm the problem is definitely the click coordinates mapping to an overlapping element (the Uservoice widget in this case).
Looking at mouseEventTest in agent.coffee:
  mouseEventTest: (x, y) ->
    frameOffset = this.frameOffset()

    x -= frameOffset.left
    y -= frameOffset.top

    el = origEl = document.elementFromPoint(x, y)

    while el
      if el == @element
        return { status: 'success' }
      else
        el = el.parentNode

    { status: 'failure', selector: origEl && this.getSelector(origEl) }

The method is called with coordinates 973, 740.5. The frameOffset is (0,0), so it calls document.elementFromPoint(973. 740.5). This returns an SVGSVGElement, rather than the expected HTMLInputElement (which is @element). The only SVG on the entire page is that Uservocie widget, so that’s clearly what it’s finding.
The while loop then walks the parent element chain from the SVGSVGEleemnt looking for the HTMLInputElement. It gets an HTMLDivElement, an HTMLBodyElement, an HTMLHtmlElement, an HTMLDocument, and finally null. When it then tries to access el.parentNode when el is null, that’s what triggers the error.
So, I’d say that whatever mechanism is supposed to detect when an overlapping element has interfered with a click is not doing the trick here. The loop should probably bail out cleanly if el is null, allowing the failure status to be returned on the final line of this method.

I believe this error is actually from getSelector where the code attempts to iterate through the classList of the overlapping element.  PhantomJS < 2 doesn't support classList on SVG elements so it returns undefined -- fixing

Should be fixed via PR #682

Hi Guys,
Am also receiving same error while running then test cases. My error is
`Safari 10.1.0 (Mac OS X 10.11.6) ERROR TypeError: undefined is not an object (evaluating '_ref.input.onChange') at
webpack:///src/components/customIncrementDecrementButton/CustomIncrementDecrementButton.js:53:21 <- /Users/vikas.bose/canadasalesapp/CanadaSalesApp/src/components/customIncrementDecrementButton/CustomIncrementDecrementButton.test.js:44179
Chrome 57.0.2987 (Mac OS X 10.11.6) ERROR Uncaught TypeError: Cannot read property 'onChange' of undefined at webpack:///src/components/customIncrementDecrementButton/CustomIncrementDecrementButton.js:53:21 <- /Users/vikas.bose/canadasalesapp/CanadaSalesApp/src/components/customIncrementDecrementButton/CustomIncrementDecrementButton.test.js:44179
Am trying to find the resolution and read lots of block but issue / error not been resolve. Please help me and it is urgent as well.
Thanks

@nodejquery11 That error is coming from code (as evidenced by the error location) in your project, not in Poltergeist - You've either got an error in your code/libraries, or you're using ES6 features (which the latest released PhantomJS doesn't support) without transpiling/polyfilling them to <=ES5


[Typed throws] Implement reabstraction thunks that change the error

Introduce SILGen support for reabstractions thunks that change the error, between indirect and direct errors as well as conversions amongst error types (e.g., from concrete to any Error).

@swift-ci please smoke test

@swift-ci please build toolchain

@swift-ci please smoke test

@swift-ci please build toolchain

macOS toolchain failure is unrelated. I have more fixes coming, but this is a good step forward---one can write and use a basic map implementation using typed throws.


force new build of selfSigner image

change line 3 of self-signer-utility.sh from
tag=$(yq r ./cockroachdb/values.yaml 'tls.selfSigner.image.tag')
to
tag=$(yq e '.tls.selfSigner.image.tag' ./cockroachdb/values.yaml)

Thanks for the suggestion!
For context, I'm not as familiar with the self-signer work. More came over here because we're seeing this error in the cockroachdb repository scan alert emails:
error scanning image gcr.io/cockroachlabs-helm-charts/cockroach-self-signer-cert:1.2: image not found (package cockroachdb:6.2.8)

After tweaking the make commands as per @JorritSalverda 's suggestion, running make build-self-signer worked locally for me (See #200)
@prafull01 @udnay @DuskEagle - I don't have write permissions to gcr.io/cockroachlabs-helm-charts/cockroach-self-signer-cert, but if the above looks good to you, perhaps you could push a 1.2 image via make push-self-signer, to resolve the error?

@JorritSalverda @celiala The helm-chart is fixed now with this PR: https://github.com/cockroachdb/helm-charts/pull/199 The issue was around the CI tag change job was not working properly. I have fixed it and now it should work for you..


Support levels (core, extended, custom) are not documented

This was discussed in one of our recent meetings. I know the original sketch doc briefly mentions core and extended types, but I'm not sure what custom would mean. It would be good to document how these should be interpreted. As an example, these three levels are referenced here.
/assign @bowei

Delineating support levels could be tricky when multiple features interact.

This issue arose during our office hours discussion on per target actions. Actions can be categorized as core, extended or custom, but creating a route rule containing a combination of them may be implementation specific.


IEasingFunction not found on angular-cli (webpack with RC5)

I just installed the directive with "npm install ng2-page-scroll --save", I imported the "PageScroll" to my app.module.ts file without a problem, when the chrome developer tools it says:
./~/ng2-page-scroll/src/ng2-page-scroll.directive.ts
161:55 export 'IEasingFunction' was not found in './ng2-page-scroll-config'
Error: export 'IEasingFunction' was not found in './ng2-page-scroll-config'
It's very strange because I checked your files and everything is in order, the ng2-page-scroll-config exports correctly the interface, but still, it isn't working, maybe it's not compatible with the angular-cli webpack version?

I'm having the same issue after upgrading to angular-cli@webpack.  There was no error when using angular-cli with System.js.

Please see the new demo app and the latest release 3.0.0


Caret (^) key on French (Canada) keyboard does not work in 1.20

Windows Terminal version
1.20.10293.0
Windows build number
10.0.19045.0
Other Software
No response
Steps to reproduce

Switch keyboard layout to "French (Canada) - Canadian Multilingual Standard"
Open Terminal Preview (1.20)
Type the key to the right of the P, which is ^ on physical "French (Canada)  Canadian Multilingual Standard" -  keyboards, or [ on US keyboards
Type Space

Expected Behavior
A caret (^) character appears on the command line.
Actual Behavior
A space appears instead.
Notes:

It also happens with the older "French (Canada) - Canadian French Keyboard"
It also happens with my custom layout based on "French (Canada) - Canadian Multilingual Standard"
I did not find other keys that do not work correctly since I upgraded a couple days ago.

P.S. So glad to finally be able to double click long paths that wrap and have the whole thing selected !!

Thanks for the report! I'll be closing this in favor of #16641 which describes the same underlying cause. /dup #16641

Thanks! I did read that issue but I was not sure it was related as in my case AltGr is not involved.


didexchange & outofband clients: excessive coupling to lower-layer packages

This is a design point.
These two client packages seem excessively coupled to lower-level packages. We're employing the wrong level of abstraction here and are violating key principles of dependency injection.
Case in point: #1474 adds 2 low-level packages as well as 2 extra functions from the provider (LegacyKMS() and Service()) just so it can get what it needs: a well-formed did.Service data structure:
Now it implements all the wiring that:

knows how to form did.Service correctly (including that magical "did-communication" type)
creates new keys
performs lookups of the route protocol service
registers the new keys with the routers
handles all error paths introduced with the above dependencies.

The outofband package is now less testable and 8 new test cases had to be added just to cover these extra paths.
The above is the more egregious failure of this package to declare dependencies of an adequate level of abstraction.
The other failure is the tight coupling to the connection package because the latter's dependency is tightly coupled to the context object. A "connectionRecorder" dependency should be satisfied by something that is injected into the client, not manually wired by the client itself.

Another example of a failure to declare dependencies with the proper level of abstraction is #1107


inplace_abn does not seem to support Pytorch 1.12.1

I'm getting the following error when running a training job that was working fine in Pytorch 1.11 with 1.12:
  File "/pip-dl_inplace_abn/inplace_abn/functions.py", line 227, in inplace_abn
    return InPlaceABN.apply(
  File "/pip-dl_inplace_abn/inplace_abn/functions.py", line 86, in forward
    mean, var, count = _backend.statistics(x)
RuntimeError: Tensors of type TensorImpl do not have sizes

Is inplace_abn not compatible with Pytorch 1.12 or is the problem somewhere else?

I think the reason is that the inplace-abn extension is too old


Adding Slackemojis pack.

Converted the slackmojis.com list into a pack, has a bunch all in one.
slackemojis.txt

Slackmojis.com guy here. I just added an yaml endpont to slackmojis that should make bulk importing via emojipacks easier (now with 100% less regex-fu!)
http://slackmojis.com/emojis.yaml
@lambtron let me know if this format works for emojipacks

@jkupferman did not work for me, just froze at "Getting emoji page"

@ckcollab which one? The one @jkupferman posted isn't formatted correctly, since I'm guessing it's key based.
You can even paste the link to the txt file in my comment and it'll run just fine.

@jkupferman's link -- that's why I tagged him, unless I'm confused?

Hah, sorry, I wasn't paying attention. It's late. ;)

S'all good mang ;)

https://github.com/lambtron/emojipacks/commit/aa65fdbaa2d37b05943266f26f0b5d1f8252655f
Thanks everyone!!

Slackmojis allows for multiple emojis with the same name (e.g. mario, carlton), does emojipacks just take the first one?

Emojipacks will take the first one; every subsequent one will just be ignored. :(


Arm Support

Is there any way that you could release arm binaries?

Hello! do you mean a ydls docker image for ARM or just ydls ARM binaries?
Building ydls binaries should be more or less just clone the repo and do GOOS=linux GOARCH=arm GOARM=5 go build ./cmd/ydls and you get a ydls binary.
Docker image shouldn't be that much trouble either i think but i haven't worked with multi arch images, would be interesting. Also need to get a nice ffmpeg build for ARM. Have and experience with it?

Have any experience with it?

Unfortunately no

Image is now multi-arch amd64 and arm64. Other arm variants etc would require build with own ffmpeg binaries.


This is more a question than anything else

I tried using your code and it worked fine until I changed it to work with my real data and found that I was losing packets.  In my scenario, I work with devices listening on some port.  I send a request on the broadcast ip (<IP_ADDRESS>) on that port and wait for each device to say hello back (on my desktop) same port.  So I am mixing a client and server in one which might be a threading problem.  This works with a couple of devices but with a couple hundred devices, I am losing many responses.
I am curious if you are planning to use System.IO.Pipelines.  It seems that it might be faster at consuming data off the wire and adding it to be consumed by a reader later when it is ready.

Pipelines are not really suitable for UDP. If you are experiencing packet loss, then you should consider looking into an R-UDP protocol. Or implementing your own.


Label songs in Soundcheck tracks

Some soundchecks are single tracks (intentionally combined) but we should indicate which songs they include like (Check) Song A > Song B

Done


Add Cut to menus

Summary
Adds "Cut" to the shortcuts menu (when you right click) and the keyboard shortcuts list (when you click the keyboard icon in the corner)
Responds to: Missing "Cut" from list of keybindings and right click menu
TODO: Add "Cut" to the other translation files!!
Tests
Didn't add any tests, but changed a few existing ones to expect "Cut" in the menus

Looks good. Thanks for the PR!

TODO: Add "Cut" to the other translation files!!

All you need to do is add it to en.json, and Crowdin takes care of the rest.


fix empty mocking that cause a error to happen

Ticket
No ticket.
What this does
Fixes mocking where we did not return a response
Why we did this
To fix mocking, whats happening is we did not have a fixture for some responses so we would return nil to braintree gem. When braintree trys to debug that message we get a error.
https://github.com/braintree/braintree_ruby/blob/02db6f8d75830aa3338d61985183aab4eebfab9b/lib/braintree/http.rb#L106
We should be atleast returning a empty response so the braintree gem does not blow up since it expects something.
Overall, I feel this way about this code
Shame, pride, exasperation, glee, relief, exhaustion

This is mad science. I like it. Well done!


Delete key doesn't delete across thousand seperators

When cursor is placed in front of a thousand seperator, the delete-key does nothing.
Initial:
12|,345
press [delete] key
Result:
12|,345
Expected:
1|,245

Thanks for reporting this @bastaware. It's related to #230. (I'll link to this issue from #230 and close this one.)
Thanks!


Fee Waiver

If the user elects to have the fee waived, it does not appear that the court is currently informed of this on the Motion to Stay. Should they be? @nonprofittechy
The Affidavit of Indigency only appears on the final review screen. Should there be a review screen sooner to allow for review? Similarly, for the NOA, should it be on the same screen as the Motion to Stay, or a different one? Three different preview screens: (1) Motion to Stay, (2) NOA, (3) Affidavit of Indigency?

No, fee waiver status is confidential
On Fri, Nov 13, 2020, 7:56 AM Mia Bonardi<EMAIL_ADDRESS>wrote:

If the user elects to have the fee waived, it does not appear that the
court is currently informed of this on the Motion to Stay. Should they be?
@nonprofittechy https://github.com/nonprofittechy
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SuffolkLITLab/docassemble-MotionToStayEviction/issues/27,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB2KTSPL6BE6AELA7EMIZMDSPUUIRANCNFSM4TURR3RA
.

No, fee waiver status is confidential
…

What about for 2?

The preview screen in #61 will actually have the entire user bundle shown, which would include all of the documents. I'm a bit more inclined towards that approach, as we only have the user sign once, and that's the primary purpose of the preview page.


Azure Functions Creation Scripts

@SyntaxC4,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Cinnamon updates 2022-12-02

Description of changes
Slick greeter now supports cursor theme settings because mint want to override it in mint-artwork.
Other updates here are basically translation updates.
Previous one: https://github.com/NixOS/nixpkgs/pull/203589
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.05 Release Notes (or backporting 22.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg test cinnamon

@ofborg test cinnamon


Tests involving numbers that should fail are passing

First, thanks for chai-as-promised: I love it.
I'm using mocha, and isNumber, isNotNumber and typeOf using promises don't seem to fail when they should. A coworker is experiencing the same issue on his machine. Tests fail properly without eventually.  I get the error both running just mocha and mocha  --require babel-polyfill --compilers js:babel-register.
'use strict';

const chai = require('chai');
const chaiAsPromised = require('chai-as-promised');
chai.use(chaiAsPromised);
const assert = chai.assert;

describe('Number promise test', () => {

    it('should pass', () => {
        assert.isNumber(55);
    });

    it('should pass', () => {
        assert.eventually.isNumber(Promise.resolve(6));
    });

    it('should fail', () => {
        assert.isNumber('string');
    });

    it('should fail but passes', () => {
        assert.eventually.isNumber(Promise.resolve('string'));
    });

    it('should pass', () => {
        assert.isNotNumber('string');
    });

    it('should pass', () => {
        assert.eventually.isNotNumber(Promise.resolve('string'));
    });

    it('should fail', () => {
        assert.isNotNumber(55);
    });

    it('should fail but passes', () => {
        assert.eventually.isNotNumber(Promise.resolve(55));
    });

    it('should pass', () => {
        assert.typeOf(55, 'number');
    });

    it('should pass', () => {
        assert.eventually.typeOf(Promise.resolve(55), 'number');
    });

    it('should fail', () => {
        assert.typeOf('string', 'number');
    });

    it('should fail but passes', () => {
        assert.eventually.typeOf(Promise.resolve('string'), 'number');
    });
});

You appear to be forgetting to return your assertions; please see the readme.

Oh my god. I wish I could delete this issue. Thank you for your patience and have a great day :)


[ZEPPELIN-1695] Apply regular maven indent

What is this PR for?
First of all, this PR doesn't affect on runtime application behaivor and existing build processes. Just styling all pom.xml files
We have not standardized maven indent currently. I referred maven code convention and applied it to this PR.
This is the sub issue of https://github.com/apache/zeppelin/pull/1662
What type of PR is it?
[Improvement]
What is the Jira issue?
ZEPPELIN-1695
How should this be tested?
CI will be enough.
Screenshots (if appropriate)
Questions:

Does the licenses files need update? - NO
Is there breaking changes for older versions? - NO
Does this needs documentation? - NO

\cc @bzz for reviewing this issue. (related to https://github.com/apache/zeppelin/pull/1662)
thanks!

AFAIK there is going to be at least few other changes that will most probably affect this PR i.e #1674  and #1339 - may be we should prioritize those smaller ones, and then rebase\merge this guy?
What do you think, @1ambda ?

@bzz We can rebase and merge smaller PRs first like https://github.com/apache/zeppelin/pull/1668 and #1339 you mentioned.
I will rebase #1668 first.

Sounds good, let's take care of small parts first, and then rebase and merge this guys in a bulk!

Let's close. Since it's outdated.


iOS SDK

Hey,
Quick question: when should we expect an iOS SDK? Thanks.

Thanks for reaching out. We don't have an exact estimate right now, but we hope to have an initial beta later this year.


Confirmable / Approvable

One more question :)
I'm also creating a module that requires a user is approved before they log in. These same questions apply to confirmable or any other sort of hook that prevents login if a condition isn't met on the user. I was going to use a plug and hooks
for the plug, is the best way to use the pattern in VerifySession? Namely:
if not approved?
conn
|> Plug.Conn.delete_session(base_key(key))
|> Guardian.Plug.set_claims({:error,'Not Approved'}, key)

and for the hook
def after_sign_in(conn, key)
  if not approved?
    conn |> sign_out_via_key(key)
 or
   conn |> sign_out(key)
 or
   something else?
end

This seems reasonable to me @ericsullivan 👍


[BUG] show a Errors when use Storage in background

What happened?
Enter demo code in background.ts file:
import { Storage } from "@plasmohq/storage"

const storage = new Storage()

await storage.set("key", "value")

const data = await storage.get("key") // value

the extensions report an error: Uncaught SyntaxError: Unexpected reserved word

expect to happen:
no errors
Version
Latest
What OS are you seeing the problem on?
MacOSX
What browsers are you seeing the problem on?
Chrome
Relevant log output
No response
(OPTIONAL) Contact Details
<EMAIL_ADDRESS>Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate problems.

I solved this problem by using await storage.get(key) instead of top level or constructor in the concrete function.


Issue all OS provisioning commands from jump host

We are using hammer host to generate a build job in foreman which updates the host to provision with new OS on next boot.
https://github.com/redhat-performance/jetpack/blob/master/setup_undercloud.yml#L60-L89
The other tasks i.e

setting boot device to pxe
reboot the node

are doing from the ansible host. If we use hammer host for these tasks as well, then we can avoid installing packages needed for these tasks on the ansible host.

Closed via c28766067d4bff3e1f3988a0eb54abdb417d68d2


Fix builds on Solaris/AIX using native compilers.

These commits fix the build on Solaris using Oracle Studio and the build on AIX using IBM Visual Age  compilers. I built these changes on both Solaris/AIX using the native compilers as well as using GCC 6 just to verify that there were no regressions. Each commit log entry has an explanation.

cc/ @joransiu @jBarz @jbajwa for the AIX code.

@apaprocki - curious to know - in general, what is your motivation behind building with non-gcc compilers? any performance goals? or integration libuv with some legacy systems? or some new use case?

@gireeshpunathil I implemented AHAFS detection in #372 and it worked perfectly fine until #1156 broke the code. I agree you need to force it on in the gyp build because it has no auto-detection functionality, but auto-detection works perfectly fine in autoconf.
We use the native compilers on Solaris and AIX because we link libuv into binaries that do not (and can not) build with GCC.

@apaprocki - can you elaborate on until #1156 broke the code part? Are you hinting at the current code failure on compilation complaining sys/ahafs_evProds.h is missing? (for both autoconf and gyp)
Are you proposing that the AHAFS feature should be opted out through autoconf via auto-detection, if the package is missing, and retain the behavior when built via gyp?

On the use case part, thanks for the explanation. I thought that the GCC-built images can link and co-exist with natively built libraries. That isn't the case?

This is adding GPL code into a MIT licensed project, I don't think that is workable.

@sam-github Does the special exemption at the end of the license not cover this use case?

@gireeshpunathil After #1156, -DHAVE_SYS_AHAFS_EVPRODS_H is always passed on the command line instead of only being passed if the system has the header installed. gyp has no way to auto-detect features, so if the gyp build wants to force AHAFS on and the community wants that, then it is fine. The autoconf build, on the other hand, was auto-detecting the header just fine and does not need help by putting -DHAVE_SYS_AHAFS_EVPRODS_H in Makefile.am.

@apaprocki : yes, agree - but then this will have two implications:

Building through the two means will exhibit two different behaviors
The autoconf build will now allow building a libuv with handicapped watch feature.

I am not arguing the current one is better over the proposal etc.,  just placing things into perspectives and letting the reviewers know the context better.

It seems like this PR might have run its course. I'm going to close. Please let me know if that is the wrong thing to do.


Unable to run cell with jupyter notebook with pyenv

Issue Type: Bug
Click Run cell and always get error message:
Executing code failed : Error: Activating Python 3.7.1 64-bit ('3.7.1': pyenv) to run Jupyter failed with Error: StdErr from ShellExec, pyenv: activate: command not found .
Below is my test code
#%%
msg = "Hello World"
print(msg)
#%%
msg = "Hello again"
print(msg)
Change pyenv or python version still occur. Can execute code or debug directly, but cannot execute via jupyter / Python interactive window.
Extension version: 2019.9.34911
VS Code version: Code 1.38.1 (b37e54c98e1a74ba89e03073e5a3761284e3ffb0, 2019-09-11T13:31:32.854Z)
Version: 1.38.1
Commit: b37e54c98e1a74ba89e03073e5a3761284e3ffb0
Date: 2019-09-11T13:31:32.854Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Darwin x64 18.7.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz (4 x 2300)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
2, 3, 4

Memory (System)
16.00GB (1.54GB free)

Process Argv

Screen Reader
no

VM
0%

I believe this is a dupe of this bug here:
https://github.com/microsoft/vscode-python/issues/7029

Closing as a duplicate of this issue here:
https://github.com/microsoft/vscode-python/issues/7029
If you still see this issue after that bug is closed just comment here and we can reactivate.


Crash if the search is used (MacOSX Ventura)

The app crash anytime I try to search something, this is the error that I am getting:
Translated Report (Full Report Below)
-------------------------------------

Process:               Maccy [84610]
Path:                  /Applications/Maccy.app/Contents/MacOS/Maccy
Identifier:            org.p0deje.Maccy
Version:               0.24.0 (13)
Code Type:             ARM-64 (Native)
Parent Process:        launchd [1]
User ID:               501

Date/Time:             2022-11-14 19:56:12.0926 +0100
OS Version:            macOS 13.0.1 (22A400)
Report Version:        12
Anonymous UUID:        371DAE41-3698-4887-C472-A52AE0720E8A

Sleep/Wake UUID:       3FAEA986-94F4-452C-A847-060A4C9C7136

Time Awake Since Boot: 70000 seconds
Time Since Wake:       1390 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000

Application Specific Information:
abort() called

Application Specific Backtrace 0:
0   CoreFoundation                      0x000000019ee94418 __exceptionPreprocess + 176
1   libobjc.A.dylib                     0x000000019e9deea8 objc_exception_throw + 60
2   Foundation                          0x000000019fd2a5b4 blockForLocation + 0
3   Foundation                          0x000000019fd3ae7c -[NSConcreteMutableAttributedString addAttribute:value:range:] + 116
4   Maccy                               0x0000000102599e5c Maccy + 155228
5   Maccy                               0x000000010259085c Maccy + 116828
6   Maccy                               0x000000010258f808 Maccy + 112648
7   Maccy                               0x000000010258f230 Maccy + 111152
8   libdispatch.dylib                   0x000000019ebc263c _dispatch_block_async_invoke2 + 148
9   libdispatch.dylib                   0x000000019ebb3504 _dispatch_client_callout + 20
10  libdispatch.dylib                   0x000000019ebb6994 _dispatch_continuation_pop + 504
11  libdispatch.dylib                   0x000000019ebc9fa0 _dispatch_source_invoke + 1588
12  libdispatch.dylib                   0x000000019ebc1c70 _dispatch_main_queue_drain + 756
13  libdispatch.dylib                   0x000000019ebc196c _dispatch_main_queue_callback_4CF + 44
14  CoreFoundation                      0x000000019ee5ad6c __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16
15  CoreFoundation                      0x000000019ee187ec __CFRunLoopRun + 2036
16  CoreFoundation                      0x000000019ee178a4 CFRunLoopRunSpecific + 612
17  HIToolbox                           0x00000001a848b3bc RunCurrentEventLoopInMode + 292
18  HIToolbox                           0x00000001a848b200 ReceiveNextEventCommon + 672
19  HIToolbox                           0x00000001a848af48 _BlockUntilNextEventMatchingListInModeWithFilter + 72
20  AppKit                              0x00000001a2070630 _DPSNextEvent + 632
21  AppKit                              0x00000001a206f7c0 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 728
22  AppKit                              0x00000001a27143dc _NSHLTBMenuEventProc + 304
23  HIToolbox                           0x00000001a84f1cec _ZL19IsUserStillTrackingP14MenuSelectDataPh + 224
24  HIToolbox                           0x00000001a862fe5c _ZL15TrackMenuCommonR14MenuSelectDataPhP13SelectionDataP10MenuResultS5_ + 1396
25  HIToolbox                           0x00000001a862c2a0 _ZL19PopUpMenuSelectCoreP8MenuData5PointdS1_tjjPK4RecttjS4_S4_PK14__CFDictionaryPK10__CFStringPP13OpaqueMenuRefPt + 1624
26  HIToolbox                           0x00000001a862b830 _ZL26_HandlePopUpMenuSelection8P13OpaqueMenuRefP14OpaqueEventRefj5PointtjjPK4RecttS6_S6_PK14__CFDictionaryPK10__CFStringPS0_Pt + 612
27  HIToolbox                           0x00000001a84dfc7c _HandlePopUpMenuSelectionWithDictionary + 380
28  AppKit                              0x00000001a245cd5c SLMPerformPopUpCarbonMenu + 1552
29  AppKit                              0x00000001a231c260 _NSSLMPopUpCarbonMenu3 + 692
30  AppKit                              0x00000001a245ba14 -[NSCarbonMenuImpl _popUpMenuPositioningItem:atCocoaIndex:atLocation:inView:withPrivateFlags:appearance:] + 232
31  AppKit                              0x00000001a25d70dc -[NSMenu popUpMenuPositioningItem:atLocation:inView:appearance:] + 240
32  Maccy                               0x00000001025a4ef8 Maccy + 200440
33  Maccy                               0x00000001025a9780 Maccy + 219008
34  Maccy                               0x00000001025a7868 Maccy + 211048
35  Maccy                               0x00000001025a3560 Maccy + 193888
36  Foundation                          0x000000019fd5867c __NSFireTimer + 104
37  CoreFoundation                      0x000000019ee33578 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 32
38  CoreFoundation                      0x000000019ee33220 __CFRunLoopDoTimer + 940
39  CoreFoundation                      0x000000019ee32d78 __CFRunLoopDoTimers + 356
40  CoreFoundation                      0x000000019ee18760 __CFRunLoopRun + 1896
41  CoreFoundation                      0x000000019ee178a4 CFRunLoopRunSpecific + 612
42  HIToolbox                           0x00000001a848b3bc RunCurrentEventLoopInMode + 292
43  HIToolbox                           0x00000001a848b200 ReceiveNextEventCommon + 672
44  HIToolbox                           0x00000001a848af48 _BlockUntilNextEventMatchingListInModeWithFilter + 72
45  AppKit                              0x00000001a2070630 _DPSNextEvent + 632
46  AppKit                              0x00000001a206f7c0 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 728
47  AppKit                              0x00000001a2063bf0 -[NSApplication run] + 464
48  AppKit                              0x00000001a203b058 NSApplicationMain + 880
49  Maccy                               0x000000010257830c Maccy + 17164
50  dyld                                0x000000019ea0fe50 start + 2544

Thanks

Looks like there is something in your history that cause this to fail. Any chance yo could share ~/Library/Containers/org.p0deje.Maccy/Data/Library/Application Support/Maccy/ for inspection? If yes, please make sure there is nothing private/confidential in your Maccy history.

Looks like there is something in your history that cause this to fail. Any chance yo could share ~/Library/Containers/org.p0deje.Maccy/Data/Library/Application Support/Maccy/ for inspection? If yes, please make sure there is nothing private/confidential in your Maccy history.

Inside the folder I can see three files: Storage.sqlite, Storage.sqlite-shm and Storage.sqlite-wal.
Is there a way to eliminate little by little to find out what the problem was?

You can try opening Maccy and look through the history items searching for anything that looks unusual (empty records, records with strange unicode characters, etc).

No, it happens with any foto I copy from the fotos app

Hi, I had the same bug and it was fixed when i removed two photos from the history. They were copied from Photos.app (macos 13.0.1)
Hope it helps and thanks for your application ❤

Hi, I had some photos in the list and indeed search was not possible anymore. I cleared the list, now it's fine, I'll report if it comes back.

Can anyone share a photo which would crash Maccy?

Hi, I had maccy crashing as well, and going through GH issues I found this one.
This seems to match my experience as well. To replicate:

Copy any photo from the Photos.app (right click the photo and click "copy")
Open maccy through hotkey
Start typing for searching something in the clipboard history
Maccy will crash.

I've tried with many different photos from my gallery and all of them made maccy crash. Removing photos copied from the Photos app makes the search work again.
Maccy 0.25.0
MacOS 13.1 (22C65)

@gallois Thank you for the explanation. That is exactly the problem I also have. I think the photo doesn't matter, the problem comes from the source (Photos.app).

@gallois @elalemanyo I don't think it's that straightforward, I cannot reproduce it, please see video below
https://user-images.githubusercontent.com/665846/212935007-20bc97f0-75d6-4472-ba9d-fcb6e530f888.mov

Interesting! Any other bit of info I can provide to help troubleshoot?

@gallois Can you share the photo that causes the crash in addition to usual:

Can you please provide the Maccy version you use? You can get it in the "About" window.
Can you please record a screen video showing the problem? You can do this using QuickTime.app.
Can you please share output of running defaults read org.p0deje.Maccy in Terminal.app?

Alright... the plot thickens!!

As for the photos, it's literally any photo causes that, there's no particular one.
Maccy version can be found in my previous comment, 0.25.0

There was an additional detail to the behaviour that might help you reproduce that I didn't notice before. If you type the the first letter of the most recent entry in the history, it works—but if you type anything else, it crashes. In short, it seems like it's able to search for the first entry, but not others.
E.g. if the entries in the clipboard are:

foo
bar

If you copy an image from Photos.app, so that your clipboard history will look liek

image
foo
bar

If you bring up maccy and type: f, foo will show up correctly. If you type b, though, maccy will crash.
I hope that helps

@gallois Ok, I can reproduce this now, thank you!


Add files via upload

@fawad-qureshi-access First stage of verification passed, official domain is kite.edu.pk as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@fawad-qureshi-access Thank you for your patience while waiting for a review and processing your request. Pull request merged.


win10 ，using tesseract for LSTM training,Iteration termination,no error message

Before you submit an issue, please review the guidelines for this repository.
Please report an issue only for a BUG, not for asking questions.
Note that it will be much easier for us to fix the issue if a test case that
reproduces the problem is provided. Ideally this test case should not have any
external dependencies. Provide a copy of the image or link to files for the test case.
Please delete this text and fill in the template below.

Environment

Tesseract Version: tesseract v5.0.0-alpha.20200328（w64）
Commit Number:
Platform: Window 64
My steps:1、Using jtessboxeditor(v2.3.1) to generate TIF
2、tesseract chi.test.exp0.tif chi.test.exp0 -l chi_sim --psm 6 lstmbox
3、Using jtessboxeditor to correct characters
4、tesseract chi.test.exp0.tif chi.test.exp0 -l chi_sim --psm 6 lstm.train
5、generate chi.training_files.txt
6、combine_tessdata -e chi_sim.traineddata chi_sim.lstm
training ,but error
result :

one picture was used

I've got the same problem. Don't have any error message to turn off, but can't generate  ".checkpoint" file

I've got the same problem. Don't have any error message to turn off, but can't generate ".checkpoint" file

This problem is caused by the Chinese training set. I can train normally after changing a Chinese training set. I don't know why the Chi SIM training downloaded from GitHub will report errors.


Revert "Merge pull request #99 from jjstickel/regularization"

This reverts commit 2f56d6039a235b1bd2ca74332191c2d51d793442, reversing changes made to 4b6fad18b42651f7b94c1455f83fe2696f4da016.
The PR pulled in a GPL dependency and therefore incompatible with the license of this package. The functionality would have to be rewritten without depending on RegularizationTools.
cc @jjstickel

Instead of a revert, this should be a subpackage. Can we please do this via a subpackage instead of just throwing it away?

The code is still in the git history so it shouldn't be too much work to add as a sub-package once somebody has the time to do so. Fixing the license violation is pretty urgent, though, so we'd have to move forward with that right away.

The primary developer of RegularizationTools might consider changing the license. What are typical license options that would be acceptable?

The primary developer of RegularizationTools might consider changing the license. What are typical license options that would be acceptable?

MIT

@jjstickel Is there a conclusion with respect to the licensing issue here?

@jjstickel Is there a conclusion with respect to the licensing issue here?

This slipped my mind with the Thanksgiving holiday. I emailed Markus (RegularizationTools developer) just now.

@andreasnoack Markus agreed to switch the license to MIT, and a PR has been merged with that change. He also tagged a new release (v0.6.1).

Great. I've reverted this one in https://github.com/PumasAI/DataInterpolations.jl/pull/130


Fix prometheus-postgres-exporter manifest

Fix broken prometheus-postgres-exporter manifest

Below is a summarization created by an LLM (gpt-4-0125-preview). Be mindful of hallucinations and verify accuracy.
Why
The changes improve configuration consistency, enhance monitoring capabilities, and ensure compatibility with monitoring tools by making labels and port names clearer and more precise.
What

charts/chainlink/Chart.yaml

Updated the chart version from 0.2.10 to 0.2.11. This change indicates an incremental improvement or fix in the chart.

charts/chainlink/templates/pg-deployment.yaml

Modified the prometheus-postgres-exporter label value from true to 'true' to ensure consistency in value type representation.
Changed the port name for the Prometheus PostgreSQL exporter from prom-pg-exporter to prom-pg-exp to make it more concise.

charts/chainlink/templates/pod-monitor.yaml

Added a name field with the value "{{ .Release.Name }}-pod-monitor" to the PodMonitor metadata, ensuring the resource is properly identified.
Added a name field with the value "{{ .Release.Name }}-pg-pod-monitor" to the second PodMonitor metadata for the PostgreSQL exporter, ensuring it's distinctly named for better resource management.
Adjusted the prometheus-postgres-exporter label value from true to 'true' in the second PodMonitor for consistency.
Changed the port reference in the second PodMonitor from prom-pg-exporter to prom-pg-exp to match the updated port name in the PostgreSQL deployment, ensuring compatibility with the monitoring setup.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 17.74%. Comparing base (65566a5) to head (5e8b123).
Report is 5 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #905   +/-   ##
=======================================
  Coverage   17.74%   17.74%
=======================================
  Files          41       41
  Lines        4576     4576
=======================================
  Hits          812      812
  Misses       3674     3674
  Partials       90       90

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Chart Scale problem in Mobile Mode

When opening the web browser and going to mobile mode the Bar chart and Pie chart scale incorrectly, but in designer with the same width they render correctly.
Also in normal sizes in the Browser, these two charts are OK.
Other charts are totally fine in any mode.

This issue has been fixed in 1.0.17:
https://github.com/Kyvis-Labs/ignition-apexcharts-module/releases/tag/1.0.17


Getting results from generic nodes

Is your feature request related to a problem? Please describe.
Seems to be difficult to return generic nodes if we don't know the properties before hand, because Neo4j.Driver.Internal.Types.Node is internal. E.g., I'm building an interface that lets the end user specify their database and a query, so it is not possible to map results, since MATCH (n) RETURN n can return any kind of entity, having any number of properties.
The package does not have an easy way to iterate over the available Labels and Properties  of the results because the Node is internal.
Describe the solution you'd like
Make Neo4j.Driver.Internal.Types.Node  public.
Describe alternatives you've considered
Reverse engineer Neo4j.Driver.Internal.Types.Node into a local class, Neo4jDriverTypesNode, and use "Deserialize-Cast" to convert the generic nodes returned from  driver.ExecutableQuery into objects of type Neo4jDriverTypesNode . It works, but making Neo4j.Driver.Internal.Types.Node public would be so much easier.

The drivers expose IEntity, INode, and IRelationship, These can be mapped to, if you have a need for the concrete class, please explain that.


TorchVision Main branch fails with slow_conv2d: grad_weight must be contiguous

🐛 Describe the bug
It looks like a breakage caused by the 20220512 PyTorch Core Nightly.
Several CI jobs fail with:
test_classification_model[cpu-convnext_base]
Traceback (most recent call last):
  File "/root/project/test/test_models.py", line 628, in test_classification_model
    _check_input_backprop(model, x)
  File "/root/project/test/test_models.py", line 181, in _check_input_backprop
    out[0].sum().backward()
  File "/root/project/env/lib/python3.10/site-packages/torch/_tensor.py", line 399, in backward
    torch.autograd.backward(self, gradient, retain_graph, create_graph, inputs=inputs)
  File "/root/project/env/lib/python3.10/site-packages/torch/autograd/__init__.py", line 173, in backward
    Variable._execution_engine.run_backward(  # Calls into the C++ engine to run the backward pass
RuntimeError: slow_conv2d: grad_weight must be contiguous

So far I've identified the following PRs as potential causes:

https://github.com/pytorch/pytorch/pull/68101
https://github.com/pytorch/pytorch/pull/70665

Given that this network uses LayerNorm changes from the following PRs are also like to have caused it:

https://github.com/pytorch/pytorch/pull/71376
https://github.com/pytorch/pytorch/pull/73844

cc @mingfeima @VitalyFedyunin
Versions
Latest main branch 03bb324576d9fe86a15a7b86a43638a838234fbd

@datumbox  is there any method to run the a single failed test case, for example, test_classification_model? That would be easier to debug the issue.

@mingfeima Thanks fore coming back to me.
You can run something like:
pytest test/test_models.py -k "convnext"

2 out of the 4 variants of convnext fail.

#77347 is submitted to fix this failure @datumbox
My local run with -k "convnext" passed:
(pytorch-mingfei) [mingfeim@mlt-skx089 test]$ pytest test_models.py -k "convnext"
======================================================================== test session starts =========================================================================
platform linux -- Python 3.7.11, pytest-7.1.2, pluggy-1.0.0
rootdir: /home/mingfeim/pytorch/vision, configfile: pytest.ini
plugins: hypothesis-6.23.3, hydra-core-1.1.1
collected 253 items / 245 deselected / 8 selected

test_models.py ....ssss                                                                                [100%]

========================================================================== warnings summary ==========================================================================
../../../anaconda3/envs/pytorch-mingfei/lib/python3.7/site-packages/torchvision-0.13.0a0+9166b67-py3.7-linux-x86_64.egg/torchvision/io/image.py:13
  /home/mingfeim/anaconda3/envs/pytorch-mingfei/lib/python3.7/site-packages/torchvision-0.13.0a0+9166b67-py3.7-linux-x86_64.egg/torchvision/io/image.py:13: UserWarning: Failed to load image Python extension:
    warn(f"Failed to load image Python extension: {e}")

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
====================================================================== short test summary info =======================================================================
SKIPPED [4] test_models.py:595: CUDA device not available
====================================================== 4 passed, 4 skipped, 245 deselected, 1 warning in 13.90s ======================================================

@mingfeima Thanks for the ultra prompt fix.
Could you confirm that the test fails on your local without the patch? I ask because for some reason, the failure seems OS specific. It fails on Linux and Windows on CPU but not on Mac.

yes, they used to fail without the patch, the following is the old log (i add some log for debugging purpose):
(pytorch-mingfei) [mingfeim@mlt-skx089 test]$ pytest test_models.py -k "convnext"
======================================================================== test session starts =========================================================================
platform linux -- Python 3.7.11, pytest-7.1.2, pluggy-1.0.0
rootdir: /home/mingfeim/pytorch/vision, configfile: pytest.ini
plugins: hypothesis-6.23.3, hydra-core-1.1.1
collected 253 items / 245 deselected / 8 selected

test_models.py ..FFssss                                                                                [100%]

============================================================================== FAILURES ==============================================================================
____________________________________________________________ test_classification_model[cpu-convnext_base] ____________________________________________________________
Traceback (most recent call last):
  File "/home/mingfeim/pytorch/vision/test/test_models.py", line 628, in test_classification_model
    _check_input_backprop(model, x)
  File "/home/mingfeim/pytorch/vision/test/test_models.py", line 181, in _check_input_backprop
    out[0].sum().backward()
  File "/home/mingfeim/anaconda3/envs/pytorch-mingfei/lib/python3.7/site-packages/torch/_tensor.py", line 399, in backward
    torch.autograd.backward(self, gradient, retain_graph, create_graph, inputs=inputs)
  File "/home/mingfeim/anaconda3/envs/pytorch-mingfei/lib/python3.7/site-packages/torch/autograd/__init__.py", line 175, in backward
    allow_unreachable=True, accumulate_grad=True)  # Calls into the C++ engine to run the backward pass
RuntimeError: slow_conv2d: grad_weight must be contiguous
------------------------------------------------------------------------ Captured stdout call ------------------------------------------------------------------------
slow_conv2d_backward_out_cpu:
input.sizes(): [1, 512, 4, 4]; [8192, 1, 2048, 512]
grad_output.sizes(): [1, 1024, 2, 2]; [4096, 4, 2, 1]
weight.sizes(): [1024, 512, 2, 2]; [2048, 4, 2, 1]
### slow_conv2d_backward_weight_out_cpu_template
input.sizes(): [1, 512, 4, 4]; [8192, 1, 2048, 512]
grad_weight.sizes(): [1024, 512, 2, 2]; [2048, 4, 2, 1]
___________________________________________________________ test_classification_model[cpu-convnext_large] ____________________________________________________________
Traceback (most recent call last):
  File "/home/mingfeim/pytorch/vision/test/test_models.py", line 628, in test_classification_model
    _check_input_backprop(model, x)
  File "/home/mingfeim/pytorch/vision/test/test_models.py", line 181, in _check_input_backprop
    out[0].sum().backward()
  File "/home/mingfeim/anaconda3/envs/pytorch-mingfei/lib/python3.7/site-packages/torch/_tensor.py", line 399, in backward
    torch.autograd.backward(self, gradient, retain_graph, create_graph, inputs=inputs)
  File "/home/mingfeim/anaconda3/envs/pytorch-mingfei/lib/python3.7/site-packages/torch/autograd/__init__.py", line 175, in backward
    allow_unreachable=True, accumulate_grad=True)  # Calls into the C++ engine to run the backward pass
RuntimeError: slow_conv2d: grad_weight must be contiguous
------------------------------------------------------------------------ Captured stdout call ------------------------------------------------------------------------
slow_conv2d_backward_out_cpu:
input.sizes(): [1, 768, 4, 4]; [12288, 1, 3072, 768]
grad_output.sizes(): [1, 1536, 2, 2]; [6144, 4, 2, 1]
weight.sizes(): [1536, 768, 2, 2]; [3072, 4, 2, 1]
### slow_conv2d_backward_weight_out_cpu_template
input.sizes(): [1, 768, 4, 4]; [12288, 1, 3072, 768]
grad_weight.sizes(): [1536, 768, 2, 2]; [3072, 4, 2, 1]
========================================================================== warnings summary ==========================================================================
../../../anaconda3/envs/pytorch-mingfei/lib/python3.7/site-packages/torchvision-0.13.0a0+9166b67-py3.7-linux-x86_64.egg/torchvision/io/image.py:13
  /home/mingfeim/anaconda3/envs/pytorch-mingfei/lib/python3.7/site-packages/torchvision-0.13.0a0+9166b67-py3.7-linux-x86_64.egg/torchvision/io/image.py:13: UserWarning: Failed to load image Python extension:
    warn(f"Failed to load image Python extension: {e}")

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
====================================================================== short test summary info =======================================================================
SKIPPED [4] test_models.py:595: CUDA device not available
FAILED test_models.py::test_classification_model[cpu-convnext_base] - RuntimeError: slow_conv2d: grad_weight must be contiguous
FAILED test_models.py::test_classification_model[cpu-convnext_large] - RuntimeError: slow_conv2d: grad_weight must be contiguous
================================================= 2 failed, 2 passed, 4 skipped, 245 deselected, 1 warning in 13.54s =================================================

Awesome, thanks for confirming.

i will check if i need to add more test case in pytorch (the old test cases failed to find out the code flaw)

Fixed on latest nightly


Added db_parameter to resource aws_db_parameter_group

What

Added db_parameter to resource aws_db_parameter_group

Why

Sometimes we need to add special parameters to the RDS database

Plan

Tested.


Do you know thermite

https://github.com/omphalos/thermite/issues/1#issuecomment-143411319

That looks like it's trying to be a more portable version of Amokify. Here's a similar discussion about comparing Browserify-HMR and Amokify. The HMR way is simple if your modules have an easily defined life cycle that you define yourself or use an add-on to (e.g. react-transform-hmr). I think HMR makes a good base for such tools. The Amokify and Thermite ways seem to be more about trying to automatically make arbitrary hot-patchable.


Add inboxkitten link to repo?

hi @marataziat ! what do you mean by that?

I meant add here https://github.com/uilicious/inboxkitten website link on the top right.

Ohhh xD thanks!
Added!! :)


[Request for external] SII module objects for Spanish localization

I would like these procedures not having OnPrem scope in the Spanish localization:

codeunit 10756 "SII Management"

GetSIIStyle
GetNoTaxablePurchAmount
GetNoTaxableSalesAmount
SIIStateDrilldown
IsVATEntryCashFlowBased
IsDetailedLedgerCashFlowBased
IsLedgerCashFlowBased
IsIntracommunity
FindVatEntriesFromLedger
FindOriginalLedgerFromDetailedPaymentLedger
FindOriginalLedgerFromPaymentLedger
FindVatEntriesReferringToDocLedger
FindDetailedPaymentApplicationLedgerFromLedger
FindDetailedLedgerFromVatEntry
FindLedgerFromVatEntry
FindPaymentDetailedCustomerLedgerEntries
FindPaymentDetailedVendorLedgerEntries
NoTaxableEntriesExistPurchase
NoTaxableEntriesExistSales
DoesPaymentDetailedLedgerCloseInvoice
DoesPaymentLedgerCloseInvoice
CountryIsLocal
CountryAndVATRegNoAreLocal
IsDomesticCustomer
CustomerIsIntraCommunity
VendorIsIntraCommunity
CombineOperationDescription
SplitOperationDescription
CharIsCapitalLetter
IsAllowedSalesInvType
IsAllowedServInvType
Run347DeclarationToGenerateCollectionsInCash

table 10740 "No Taxable Entry"

FilterNoTaxableEntry
FilterNoTaxableEntriesForSource
InitFromGenJnlLine
InitFromServiceDocument
InitFromVendorEntry
InitFromCustomerEntry
Reverse
Update

codeunit 10750 "SII XML Creator"

FormatDate
FormatNumber

codeunit 10753 "SII Job Upload Pending Docs."

GenJnlLineHasSIIDocType
HandlePendingEntries

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 51281.


Update custom circuit guide and correct typos

@pacosynthesis Due to metadata in jupyter notebooks, we'll not use pull requests for ipynb files. I'm trying to update things manually this time, and we will determine a better workflow for the future.


Arrows displayed with rectangle

environment

vim: 7.4.1795
vim-airline: latest (04/29/16)
OS: Ubuntu 16.04 LTS
terminal: gnome-terminal
$TERM variable: xterm-256color
color configuration (:set t_Co?): 256

actual behavior

expected behavior

I've added the customization suggested in this FAQ (https://github.com/vim-airline/vim-airline/wiki/FAQ), though, it seems that the original style is displayed as well as the powerline's. Also checked on these topics for similar problems :

http://vi.stackexchange.com/questions/5622/how-to-configure-vim-airline-plugin-to-look-like-its-own-project-screenshot
https://vi.stackexchange.com/questions/3359/how-to-fix-status-bar-symbols-in-airline-plugin?rq=1

I think what you are seeing is the result of truncation. Get rid of some of the warnings and it should look good again.

By warnings, are you referring to these lines ?
let g:airline#extensions#ycm#error_symbol = 'E:' let g:airline#extensions#ycm#warning_symbol = 'W:
If yes, nothing changed after having removed it.

No, I refer to the whitespace warnings that are displayed in the statusline and your overlong date section.

Hm, I have kept only what is suggested in customization section, and the result is more or less the same :

I think he means go for "T" instead of "trailing" and maybe "MI" instead of
"mix-indent-file"
On Fri, Apr 29, 2016 at 9:08 AM, Leeshe<EMAIL_ADDRESS>wrote:

Hm, I have kept only what is suggested in customization section, and the
result is more or less the same :
[image: airline]
https://cloud.githubusercontent.com/assets/16366403/14918509/97f6104c-0e24-11e6-8e8d-714bbd4a0a1f.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/vim-airline/vim-airline/issues/1153#issuecomment-215727721

--
rd

I tried those lines :
 let g:airline#extensions#whitespace#trailing_format = 'T[%s]' let g:airline#extensions#whitespace#mixed_indent_file_format = 'MI[%s]'
same issue remains

I don't use powerline fonts and don't see the point of having those little angle pointers, so I just use a rather plain boxy looking status line.

Guess it's just a stylish effect. May I know your vimrc setting for Vim-Airline ?

if !exists('g:airline_symbols')
let g:airline_symbols = {}
endif
let g:airline_right_alt_sep = ''
" unicode symbols
let g:airline_left_sep = ''
let g:airline_right_sep = ''
let g:airline_symbols.linenr = 'Ξ'
let g:airline_symbols.paste = 'ρ'
let g:airline_detect_spell=0
" Airline White Space Handling:
let g:airline#extensions#whitespace#enabled = 1
let g:airline_symbols.whitespace = '□□'
"configure the formatting of the warning messages. >
let g:airline#extensions#whitespace#mixed_indent_format = 'MI[%s]'
let g:airline#extensions#whitespace#trailing_format = 'T[%s]'
" regex for trailing white space, looks for TWO spaces, not one
let g:airline#extensions#whitespace#trailing_regexp = '\s\s$'
" orange for mixed-indent
let g:airline#extensions#whitespace#checks = [ 'indent', 'trailing']
let g:airline#extensions#branch#enabled = 0
" Show Obsession Status:
" Prepend $ sign if Obsession is active
let g:airline_section_z = airline#section#create(['%{ObsessionStatus(''$'', '''')}', 'windowswap', '%3p%% ', 'linenr', ':%3v '])
" File Type File Encoding File Format:
" Tells airline not to display file format
let g:airline_section_x =''
" Tells airline not to display fileencoding or fileformat
let g:airline_section_y =''
" If need to know these then simply do:
" set ff for fileformat
" set fenc for fileencoding
" set ft for filetype
" Airline Short Form Mode Indicators:
" Paste the following into your vimrc for shortform text
" N instead of NORMAL, I instead of INSERT
let g:airline_mode_map = {
\ '__' : '-',
\ 'n'  : 'N',
\ 'i'  : 'I',
\ 'R'  : 'R',
\ 'c'  : 'C',
\ 'v'  : 'V',
\ 'V'  : 'V',
\ '' : 'V',
\ 's'  : 'S',
\ 'S'  : 'S',
\ '' : 'S',
\ }

Thanks.

okay, I seem to be missing something. Please indicate clearly what your problem is. I have the feeling we are going round in circles here.

I'll try to do my best to explain it.
Let's take the message "buffers" appearing on the top-right of the screen (first screenshot). It seems that there is two themes displayed at the same time : the original one (a rectangle) and powerline's (an arrow). The result is an arrow not perfectly suiting the rectangle. I hope this screen will explain it better :

Sorry, laking of English vocabularies to explain it clearly.

Looks like you are not using a powerline patched font. Here you'll find some fonts. With that you should see your expected result.

Hm, that's precisely what I installed (git cloning it and using the script install.sh), and also this link https://powerline.readthedocs.io/en/latest/installation/linux.html#font-installation
Or is there something I'm missing ?

Not that I know of. And you are actually using a patched font in your terminal?

I use default font on Ubuntu 16.04 (gnome-terminal).

Am 2016-05-01 23:23, schrieb Chris Smith:

I use default font on Ubuntu 16.04 (gnome-terminal).

You need to configure your terminal to use a patched font then.

By configuring the terminal, is it setting a Powerline's font (checking 'Custom font') ? If yes, I've tried some Powerline's fonts.

Or I've tried a reinstall of Powerline's font (http://askubuntu.com/questions/283908/how-can-i-install-and-use-powerline-plugin).
Also tried to set manually powerline's fonts :
gsettings set org.gnome.desktop.interface monospace-font-name 'different_powerline_font'

@Leeshe you need select Custom font in terminal config windows. see pic above.

Yeah, on the pic, the button is not checked. But, yes, I did it.

Well from your screenshot I think it is clear, that the wrong font was used. Please setup your terminal font correctly and everything will work.


How to refer bundled modules from external JS template loading dynamically

Do you want to request a feature or report a bug?
I am having an issue which i am facing and unable to figure out solution.

I already asked on stackoverflow but didn't got any solution yet.
What is the current behavior?
If the current behavior is a bug, please provide the steps to reproduce.
The link to question asked on Stackoverflow:
https://stackoverflow.com/questions/45216324/webpack-how-to-refer-bundled-modules-from-external-js-template-loading-dynamica

Webpack configuration files: webpack.config.js and webpack.shim.js
https://gist.github.com/imsurinder90/a5ebf5690336667f2fb9679eb3c95a2e.js

Project repo
https://github.com/postgres/pgadmin4/tree/master/web

What is the expected behavior?
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
node --version
v8.0.0
./web/node_modules/webpack/bin/webpack.js --version
3.0.0
Mac OSx Yosemite 10.10.2

webpack doesn't provide a mechanism for this. You need to use globals or pass arguments to the external.


Cover OperatingSystemExtensions with unit tests

I will look on this one.

Hi @StrnadRichard :) Any progress?


Allow to set custom WS URL waiting time

With a heavy CPU utilization, Chrome sometimes does not start in 20 seconds.
This adds a custom option to set the WS URL waiting time.

Suggested changes:

Add a commit to change the arrangement of the ExecAllocator struct. wg works like a mutext hat here.

diff --git a/allocate.go b/allocate.go
index f639ea2..3de99b1 100644
--- a/allocate.go
+++ b/allocate.go
@@ -105,11 +105,11 @@ type ExecAllocator struct {
    initFlags map[string]interface{}
    initEnv   []string

+   modifyCmdFunc func(cmd *exec.Cmd)
+
    wg sync.WaitGroup

    combinedOutputWriter io.Writer
-
-   modifyCmdFunc func(cmd *exec.Cmd)
 }

Add another commit to implement WSURLReadTimeout:

diff --git a/allocate.go b/allocate.go
index 3de99b1..1958308 100644
--- a/allocate.go
+++ b/allocate.go
@@ -37,7 +37,8 @@ type Allocator interface {
 // to create the allocator without the unnecessary context layer.
 func setupExecAllocator(opts ...ExecAllocatorOption) *ExecAllocator {
    ep := &ExecAllocator{
-       initFlags: make(map[string]interface{}),
+       initFlags:        make(map[string]interface{}),
+       wsURLReadTimeout: 20 * time.Second,
    }
    for _, o := range opts {
        o(ep)
@@ -107,6 +108,11 @@ type ExecAllocator struct {

    modifyCmdFunc func(cmd *exec.Cmd)

+   // Chrome will sometimes fail to print the websocket, or run for a long
+   // time, without properly exiting. To avoid blocking forever in those
+   // cases, give up after a specified timeout.
+   wsURLReadTimeout time.Duration
+
    wg sync.WaitGroup

    combinedOutputWriter io.Writer
@@ -224,11 +230,6 @@ func (a *ExecAllocator) Allocate(ctx context.Context, opts ...BrowserOption) (*B
        close(c.allocated)
    }()

-   // Chrome will sometimes fail to print the websocket, or run for a long
-   // time, without properly exiting. To avoid blocking forever in those
-   // cases, give up after twenty seconds.
-   const wsURLReadTimeout = 20 * time.Second
-
    var wsURL string
    wsURLChan := make(chan struct{}, 1)
    go func() {
@@ -237,7 +238,7 @@ func (a *ExecAllocator) Allocate(ctx context.Context, opts ...BrowserOption) (*B
    }()
    select {
    case <-wsURLChan:
-   case <-time.After(wsURLReadTimeout):
+   case <-time.After(a.wsURLReadTimeout):
        err = errors.New("websocket url timeout reached")
    }
    if err != nil {
@@ -494,6 +495,14 @@ func CombinedOutput(w io.Writer) ExecAllocatorOption {
    }
 }

+// WSURLReadTimeout sets the waiting time for reading the WebSocket URL.
+// The default value is 20 seconds.
+func WSURLReadTimeout(t time.Duration) ExecAllocatorOption {
+   return func(a *ExecAllocator) {
+       a.wsURLReadTimeout = t
+   }
+}
+
 // NewRemoteAllocator creates a new context set up with a RemoteAllocator,
 // suitable for use with NewContext. The url should point to the browser's
 // websocket address, such as "ws://<IP_ADDRESS>:$PORT/devtools/browser/...".

Will do

Commit updated..

Any news?

@waybackarchiver hey. I realized this is a bit nonsensical; when the CPU usage is high, and chrome does not start in 20 seconds, in my experience, it still doesn't start in 1 minute or 2 minutes or ever; so this PR is a bit useless.
I still think it should be user-settable though, as the 20 seconds timeout is a bit random and should not be hardcoded; but I don't have it as priority 1 to merge this :)

@karelbilek are you planning to finish this PR or should we take it over?

I lambda, during cold start is occasionally takes like ~30 sec or more. And start each time, having this hard-coded artificial timeout removed from the source code.

I'm going to cherry-pick the changes.

done.

@ZekeLu When is the next release planned? I want to plan switch on this repo from our fork

@8tomat8 v0.8.4 has just been released.


neo logo in footer doesn't work

Change to point to:
https://neo-cdn.azureedge.net/images/neo_logo.svg

Fixed with #69