boards: arm: lpcxpresso55s69: Force TF-M when using NS boards

This commit forces the CONFIG_BUILD_WITH_TFM=y option when using the _ns build targets for the LPC55sXX.
Using these targets in samples or in CI without an accompanying secure environment image (ex. TF-M) leads to execution failures, since the NS images are offset a predetermined amount.
Fixes #35100
Test Output
$ ./scripts/twister -v --device-testing --build-only -p lpcxpresso55s69_ns -T tests/lib/sprintf
$ JLinkExe -device lpc55s69 -if swd -speed 2000 -autoconnect 1

Then in the JLink shell:
J-Linke>r
J-Link>erase
J-Link>loadfile twister-out/lpcxpresso55s69_ns/tests/lib/sprintf/libraries.libc.sprintf/tfm_merged.hex

Serial output (post reset):
*** Booting Zephyr OS build zephyr-v2.5.0-3928-gfa836cc00d4f  ***
Running test suite test_sprintf
===================================================================
START - test_sprintf_misc
 PASS - test_sprintf_misc in 0.1 seconds
===================================================================
START - test_sprintf_double
 PASS - test_sprintf_double in 0.3 seconds
===================================================================
START - test_sprintf_integer
 PASS - test_sprintf_integer in 0.1 seconds
===================================================================
START - test_vsprintf
 PASS - test_vsprintf in 0.1 seconds
===================================================================
START - test_vsnprintf
 PASS - test_vsnprintf in 0.1 seconds
===================================================================
START - test_sprintf_string
 PASS - test_sprintf_string in 0.1 seconds
===================================================================
START - test_snprintf
 PASS - test_snprintf in 0.1 seconds
===================================================================
START - test_print
3
 PASS - test_print in 0.1 seconds
===================================================================
START - test_fprintf
3
 PASS - test_fprintf in 0.1 seconds
===================================================================
START - test_vfprintf
This 3
        3
/%/a/
11
 PASS - test_vfprintf in 0.3 seconds
===================================================================
START - test_vprintf
This 3

@henrikbrixandersen I'm a bit confused about the LPC55S16 and LPC55S28 having _ns targets here since neither of those boards are supported upstream in TF-M. What was the goal adding those, and do you have an out of tree solution for these targets? Just realized after creating this PR that only the LPC55S69 can really pull in TF-M today.

So only the LPC55S69 seems to have TFM support, so this doesn't make sense.
I still don't quite understand why we have _ns variants for 55s28 and 55s16 in zephyr.

Correct ... updated this to only force TF-M for the 55s69.

@microbuilder I have submitted a PR for renaming the lpcxpresso55s16_ns to drop the _ns part: #35416

Does this need any documentation change? E.g. For nordic we write it down that tfm is build by default.

Good point ... fixed.

@ioannisg can you take another look


Problem with detecting if element is inView

On my website I have been experiencing a problem with the script where it doesn't detect correctly whether an element is in view or not. It's because some images on my website ( bredymer.dk/biler.aspx ) return ele.getBoundingClientRect().left value less than zero meaning that their left coordinate starts outside viewport. This has caused some of the images not to load and I fixed it by
I have fixed it by modifying
	function elementInView(ele) {
		var rect = ele.getBoundingClientRect();
		var bottomline = winHeight + options.offset;

	    return (
		 // inside horizontal view
		 rect.left >= -20
		 && rect.right <= winWidth + options.offset
		 && (
		 // from top to bottom
		 rect.top  >= 0
		 && rect.top  <= bottomline
		 // from bottom to top
		 || rect.bottom <= bottomline
	 	 	&& rect.bottom >= 0 - options.offset
			)
		);

		return inView;
	 }

where I set rect.left >= -20 . This is not a universal solution and only helped fixed problem in my website. Perhaps there are some universal ways to solve it?

Fixed in version 1.3.0


Out-of-memory errors

I've encountered some new OOM errors while trying to reimplement statcont's main function (c_sigmaclip) to use dask.  This relies on code here:
https://github.com/radio-astro-tools/statcont/pull/6
from spectral_cube import SpectralCube
from dask.diagnostics import ProgressBar
pbar = ProgressBar()
pbar.register()

from statcont.cont_finding import c_sigmaclip_scube

cube = SpectralCube.read('G008.67_B3_spw1_12M_spw1.image').rechunk([-1, 'auto', 'auto'])

with cube.use_dask_scheduler('threads', num_workers=8):
    result = c_sigmaclip_scube(cube, 0.001)

resulted in:
[                                        ] | 0% Completed | 25min 11.3sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[                                        ] | 0% Completed | 25min 30.4sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[                                        ] | 0% Completed | 26min 47.7sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[                                        ] | 1% Completed | 27min 42.6sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[                                        ] | 1% Completed | 27min 45.6sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[                                        ] | 1% Completed | 28min 23.0sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[                                        ] | 1% Completed | 28min 58.2sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[                                        ] | 1% Completed | 29min  7.2sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[#                                       ] | 2% Completed | 29min 15.8sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[#                                       ] | 3% Completed | 29min 43.6sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
WARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[#                                       ] | 3% Completed | 29min 56.7sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[#                                       ] | 3% Completed | 30min  4.5sKilled

The data for this are at https://bio.rc.ufl.edu/pub/adamginsburg/test-spectral-cube/
This is operating on a slurm machine with 32 GB of RAM and 8 threads.
Because sigmaclip_spectrally is called as part of a dask chain lazily, I can't be entirely certain where the failure point is.

In [15]: cube
Out[15]:
DaskVaryingResolutionSpectralCube with shape=(1928, 1728, 2160) and unit=Jy / beam and chunk size (1928, 36, 360):
 n_x:   2160  type_x: RA---SIN  unit_x: deg    range:   271.552327 deg:  271.623302 deg
 n_y:   1728  type_y: DEC--SIN  unit_y: deg    range:   -21.647186 deg:  -21.594416 deg
 n_s:   1928  type_s: FREQ      unit_s: Hz     range:<PHONE_NUMBER>0.885 Hz:92660820639.443 Hz

The cube size on disk is 28GB.
We should be able to handle larger-than-memory cubes, though.
I'm trying again with save_to_tmp_dir disabled.

Another attempt, but with 32 threads,  resulted in:
WARNING: StokesWarning: Cube is a Stokes cube, returning spectral cube for I component [spectral_cube.io.core]
[                                        ] | 0% Completed | 20min 29.3sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[                                        ] | 0% Completed | 20min 44.6sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[                                        ] | 0% Completed | 20min 52.8sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[#                                       ] | 3% Completed | 21min 18.6sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[#                                       ] | 3% Completed | 21min 20.9sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[#                                       ] | 3% Completed | 21min 21.6sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[#                                       ] | 3% Completed | 21min 22.5sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[#                                       ] | 3% Completed | 21min 23.4sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[#                                       ] | 3% Completed | 21min 23.7sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[#                                       ] | 3% Completed | 21min 24.6sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[#                                       ] | 3% Completed | 21min 25.4sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[#                                       ] | 3% Completed | 21min 27.4sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[#                                       ] | 3% Completed | 21min 30.7sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[#                                       ] | 3% Completed | 21min 33.4sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[#                                       ] | 3% Completed | 21min 36.6sIllegal instruction (core dumped)

Latest try is still going with 3h elapsed on nodes that have enough memory.
--ntasks=8 --mem=32gb

DaskVaryingResolutionSpectralCube with shape=(1929, 1764, 2240) and unit=Jy / beam and chunk size (1929, 28, 320):
 n_x:   2240  type_x: RA---SIN  unit_x: deg    range:   271.554357 deg:  271.621269 deg
 n_y:   1764  type_y: DEC--SIN  unit_y: deg    range:   -21.645286 deg:  -21.596314 deg
 n_s:   1929  type_s: FREQ      unit_s: Hz     range:<PHONE_NUMBER>56.282 Hz:103059995512.838 Hz
[######                                  ] | 17% Completed |  3hr 40min  8.2s

--ntasks=32 --mem=128gb

DaskVaryingResolutionSpectralCube with shape=(1985, 1728, 2160) and unit=Jy / beam and chunk size (1985, 36, 360):
 n_x:   2160  type_x: RA---SIN  unit_x: deg    range:   271.552327 deg:  271.623302 deg
 n_y:   1728  type_y: DEC--SIN  unit_y: deg    range:   -21.647186 deg:  -21.594416 deg
 n_s:   1985  type_s: FREQ      unit_s: Hz     range:<PHONE_NUMBER>5.868 Hz:93224230564.339 Hz
[######                                  ] | 16% Completed |  3hr 14min 41.5s

Using save_to_tmp_dir results in IllegalInstructionErrors:
WARNING: StokesWarning: Cube is a Stokes cube, returning spectral cube for I component [spectral_cube.io.core]
DaskVaryingResolutionSpectralCube with shape=(960, 640, 640) and unit=Jy / beam and chunk size (32, 640, 640):
 n_x:    640  type_x: RA---SIN  unit_x: deg    range:   273.533353 deg:  273.578133 deg
 n_y:    640  type_y: DEC--SIN  unit_y: deg    range:   -17.950554 deg:  -17.907954 deg
 n_s:    960  type_s: FREQ      unit_s: Hz     range:<PHONE_NUMBER>72.130 Hz:219591417100.799 Hz
[########################################] | 100% Completed |  2.5s
[######                                  ] | 16% Completed |  4min 20.2sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[###########                             ] | 28% Completed |  4min 24.5sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[############                            ] | 30% Completed |  4min 26.4sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[############                            ] | 32% Completed |  4min 27.3sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[############                            ] | 32% Completed |  4min 27.6sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[############                            ] | 32% Completed |  4min 27.9sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[############                            ] | 32% Completed |  4min 28.8sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[############                            ] | 32% Completed |  4min 31.7sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[############                            ] | 32% Completed |  4min 35.0sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[#############                           ] | 34% Completed |  4min 41.8sWARNING: Input data contains invalid values (NaNs or infs), which were automatically clipped. [astropy.stats.sigma_clipping]
[#############                           ] | 34% Completed | 38min  0.9sIllegal instruction (core dumped)

MWE:
In [4]: cube = SpectralCube.read('G012.80_B6_spw4_12M_spw4.image')
/orange/adamginsburg/repos/casa-formats-io/casa_formats_io/casa_dask.py:232: 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]

In [5]: cube._data.to_zarr(fn+".test.zarr")
[                                        ] | 0% Completed |  0.3sIllegal instruction (core dumped)

Additional info (based on https://github.com/zarr-developers/numcodecs/issues/252):
In [1]:     from cpuinfo import get_cpu_info

In [2]:

In [2]:     for key, value in get_cpu_info().items():
   ...:             print("{0}: {1}".format(key, value))
   ...:
python_version: 3.7.3.final.0 (64 bit)
cpuinfo_version: [7, 0, 0]
cpuinfo_version_string: 7.0.0
arch: X86_64
bits: 64
count: 64
arch_string_raw: x86_64
vendor_id_raw: AuthenticAMD
brand_raw: AMD Opteron(tm) Processor 6378
hz_advertised_friendly: 2.4000 GHz
hz_actual_friendly: 2.4000 GHz
hz_advertised: [2400000000, 0]
hz_actual: [2400000000, 0]
model: 2
family: 21
flags: ['3dnowprefetch', 'abm', 'aes', 'amd_dcm', 'aperfmperf', 'apic', 'arat', 'art', 'avx', 'bmi1', 'clflush', 'cmov', 'cmp_legacy', 'constant_tsc', 'cpb', 'cr8_legacy', 'cx16', 'cx8', 'de', 'decodeassists', 'extapic', 'extd_apicid', 'f16c', 'flushbyasid', 'fma', 'fma4', 'fpu', 'fxsr', 'fxsr_opt', 'ht', 'hw_pstate', 'ibpb', 'ibs', 'lahf_lm', 'lbrv', 'lm', 'mca', 'mce', 'misalignsse', 'mmx', 'mmxext', 'monitor', 'msr', 'mtrr', 'nodeid_msr', 'nonstop_tsc', 'nopl', 'npt', 'nrip_save', 'nx', 'osvw', 'pae', 'pat', 'pausefilter', 'pclmulqdq', 'pdpe1gb', 'perfctr_core', 'perfctr_nb', 'pfthreshold', 'pge', 'pni', 'popcnt', 'pse', 'pse36', 'rdtscp', 'rep_good', 'retpoline_amd', 'sep', 'skinit', 'ssbd', 'sse', 'sse2', 'sse4_1', 'sse4_2', 'sse4a', 'ssse3', 'svm', 'svm_lock', 'syscall', 'tbm', 'tce', 'topoext', 'tsc', 'tsc_scale', 'vmcb_clean', 'vme', 'vmmcall', 'wdt', 'xop', 'xsave']
l3_cache_size: 2097152
l2_cache_size: 2097152
l1_data_cache_size: 16384
l1_instruction_cache_size: 65536

I was on numcodecs 0.6.4; going to try to upgrade...

ok, upgrading numcodecs solved the illegal instruction error

I've gotten another OOM error on another case:
Found some matches for fn ['W51-E_B3_spw0_12M_spw0.image'], using W51-E_B3_spw0_12M_spw0.image.
Beginning field W51-E band 3 config 12M line  spw 0 suffix .image
/orange/adamginsburg/repos/casa-formats-io/casa_formats_io/casa_dask.py:232: 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]
DaskVaryingResolutionSpectralCube with shape=(2129, 2016, 2016) and unit=Jy / beam and chunk size (32, 224, 2016):
 n_x:   2016  type_x: RA---SIN  unit_x: deg    range:   290.905186 deg:  290.963009 deg
 n_y:   2016  type_y: DEC--SIN  unit_y: deg    range:    14.480193 deg:   14.536165 deg
 n_s:   2129  type_s: FREQ      unit_s: Hz     range:<PHONE_NUMBER>8.487 Hz:93227659461.147 Hz
computing max(axis=(1,2))
[####                                    ] | 12% Completed |  1min  4.3sKilled

This hints at a memory leak in my script, which is looping through a lot of different cubes, but I can see no obvious location there should be a leak.  It's not clear whether the above issue is reproducible with a MWE.

Another case, ran for many cubes before dying on this one:
INFO: Loading data back from /blue/adamginsburg/adamginsburg/tmp/tmppow2w002 [spectral_cube.dask_spectral_cube]
[########################################] | 100% Completed |  6min 11.7s
[########################################] | 100% Completed |  6min 11.8s
[########################################] | 100% Completed |  6min 14.4s
[########################################] | 100% Completed |  6min 14.5s
[########################################] | 100% Completed |  1.4s
[########################################] | 100% Completed |  1.5s
[########################################] | 100% Completed | 49.5s
[########################################] | 100% Completed | 49.6s
W43-MM2_B6_spw2_12M_spw2.image -> W43-MM2_B6_spw2_12M_spw2.image.statcont.cont.fits in 6529.982861042023s
G337.92_B6_spw4_12M_spw4.image 2.805955515243113
WARNING: StokesWarning: Cube is a Stokes cube, returning spectral cube for I component [spectral_cube.io.core]
DaskVaryingResolutionSpectralCube with shape=(1181, 686, 896) and unit=Jy / beam and chunk size (44, 686, 896):
 n_x:    896  type_x: RA---SIN  unit_x: deg    range:   250.266864 deg:  250.321697 deg
 n_y:    686  type_y: DEC--SIN  unit_y: deg    range:   -47.148427 deg:  -47.119885 deg
 n_s:   1181  type_s: FREQ      unit_s: Hz     range:<PHONE_NUMBER>57.157 Hz:219647739971.915 Hz
[########################################] | 100% Completed |  5.8s
[########################################] | 100% Completed |  5.9s
INFO: Writing temporary file to /blue/adamginsburg/adamginsburg/tmp/tmpo_id74uc [spectral_cube.dask_spectral_cube]
[                                        ] | 0% Completed | 18min 34.2sKilled

Latest in this saga:
  File "/orange/adamginsburg/miniconda3/lib/python3.7/site-packages/fsspec/mapping.py", line 94, in <dictcomp>
    for k, v in out.items()
AttributeError: 'FSMap' object has no attribute 'missing_exceptions'

afaict, this sort of thing with fsspec did not happen on smaller cubes

That last error came from fsspec 0.8.4, which is the latest, and when I googled the error, the issues said either to upgrade - or downgrade - fsspec.  I'm trying again on a fresh conda-forge based install

The latest entry in this tale:
WARNING: StokesWarning: Cube is a Stokes cube, returning spectral cube for I component [spectral_cube.io.core]
DaskVaryingResolutionSpectralCube with shape=(2005, 1120, 1120) and unit=Jy / beam and chunk size (42, 224, 1120):
 n_x:   1120  type_x: RA---SIN  unit_x: deg    range:   281.887004 deg:  281.918107 deg
 n_y:   1120  type_y: DEC--SIN  unit_y: deg    range:    -2.029922 deg:   -1.998839 deg
 n_s:   2005  type_s: FREQ      unit_s: Hz     range:<PHONE_NUMBER>30.101 Hz:231439191431.723 Hz
[########################################] | 100% Completed |  6min 43.6s
DaskVaryingResolutionSpectralCube with shape=(2005, 1120, 1120) and unit=Jy / beam and chunk size (2005, 56, 280):
 n_x:   1120  type_x: RA---SIN  unit_x: deg    range:   281.887004 deg:  281.918107 deg
 n_y:   1120  type_y: DEC--SIN  unit_y: deg    range:    -2.029922 deg:   -1.998839 deg
 n_s:   2005  type_s: FREQ      unit_s: Hz     range:<PHONE_NUMBER>30.101 Hz:231439191431.723 Hz
INFO: Writing temporary file to /blue/adamginsburg/adamginsburg/tmp/tmpggz_xw3u [spectral_cube.dask_spectral_cube]
[########################################] | 100% Completed | 14hr 42min 35.5s
INFO: Loading data back from /blue/adamginsburg/adamginsburg/tmp/tmpggz_xw3u [spectral_cube.dask_spectral_cube]
[########################################] | 100% Completed | 16min  8.9s
[########################################] | 100% Completed | 17min 48.9s
Traceback (most recent call last):
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/distributed/protocol/pickle.py", line 49, in dumps
    result = pickle.dumps(x, **dump_kwargs)
TypeError: cannot pickle '_thread.lock' object

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/orange/adamginsburg/ALMA_IMF/reduction/analysis/statcont_cubes.py", line 111, in <module>
    fits.PrimaryHDU(data=result[1], header=cube[0].header).writeto(outfn,
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/astropy/utils/decorators.py", line 535, in wrapper
    return function(*args, **kwargs)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/astropy/io/fits/hdu/base.py", line 371, in writeto
    hdulist.writeto(name, output_verify, overwrite=overwrite,
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/astropy/utils/decorators.py", line 535, in wrapper
    return function(*args, **kwargs)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/astropy/io/fits/hdu/hdulist.py", line 943, in writeto
    hdu._writeto(hdulist._file)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/astropy/io/fits/hdu/base.py", line 677, in _writeto
    self._writeto_internal(fileobj, inplace, copy)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/astropy/io/fits/hdu/base.py", line 683, in _writeto_internal
    data_offset, data_size = self._writedata(fileobj)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/astropy/io/fits/hdu/base.py", line 615, in _writedata
    size += self._writedata_internal(fileobj)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/astropy/io/fits/hdu/image.py", line 623, in _writedata_internal
    return self._writeinternal_dask(fileobj)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/astropy/io/fits/hdu/image.py", line 709, in _writeinternal_dask
    output.store(outarr, lock=True, compute=True)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/dask/array/core.py", line 1433, in store
    r = store([self], [target], **kwargs)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/dask/array/core.py", line 981, in store
    result.compute(**kwargs)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/dask/base.py", line 167, in compute
    (result,) = compute(self, traverse=False, **kwargs)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/dask/base.py", line 452, in compute
    results = schedule(dsk, keys, **kwargs)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/distributed/client.py", line 2705, in get
    futures = self._graph_to_futures(
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/distributed/client.py", line 2641, in _graph_to_futures
    "tasks": valmap(dumps_task, dsk),
  File "cytoolz/dicttoolz.pyx", line 181, in cytoolz.dicttoolz.valmap
  File "cytoolz/dicttoolz.pyx", line 206, in cytoolz.dicttoolz.valmap
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/distributed/worker.py", line 3358, in dumps_task
    return {"function": dumps_function(task[0]), "args": warn_dumps(task[1:])}
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/distributed/worker.py", line 3367, in warn_dumps
    b = dumps(obj, protocol=4)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/distributed/protocol/pickle.py", line 60, in dumps
    result = cloudpickle.dumps(x, **dump_kwargs)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/cloudpickle/cloudpickle_fast.py", line 73, in dumps
    cp.dump(obj)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/cloudpickle/cloudpickle_fast.py", line 563, in dump
    return Pickler.dump(self, obj)
TypeError: cannot pickle '_thread.lock' object

[#################                       ] | 43% Completed | 15min 28.4sdistributed.worker - WARNING - Memory use is high but worker has no data to store to disk.  Perhaps some other process is leaking memory?  Process memory: 707.59 MB -- Worker memory limit: 1000.00 MB
[#################                       ] | 43% Completed | 15min 28.6sdistributed.worker - WARNING - Memory use is high but worker has no data to store to disk.  Perhaps some other process is leaking memory?  Process memory: 707.59 MB -- Worker memory limit: 1000.00 MB
[#################                       ] | 43% Completed | 15min 28.7sdistributed.worker - WARNING - Memory use is high but worker has no data to store to disk.  Perhaps some other process is leaking memory?  Process memory: 707.59 MB -- Worker memory limit: 1000.00 MB
distributed.worker - WARNING - Memory use is high but worker has no data to store to disk.  Perhaps some other process is leaking memory?  Process memory: 707.59 MB -- Worker memory limit: 1000.00 MB
distributed.worker - WARNING - Memory use is high but worker has no data to store to disk.  Perhaps some other process is leaking memory?  Process memory: 707.59 MB -- Worker memory limit: 1000.00 MB
[#################                       ] | 43% Completed | 15min 29.4sdistributed.worker - WARNING - Memory use is high but worker has no data to store to disk.  Perhaps some other process is leaking memory?  Process memory: 707.59 MB -- Worker memory limit: 1000.00 MB
[#################                       ] | 43% Completed | 15min 29.5sdistributed.worker - WARNING - Memory use is high but worker has no data to store to disk.  Perhaps some other process is leaking memory?  Process memory: 707.59 MB -- Worker memory limit: 1000.00 MB
distributed.worker - WARNING - Memory use is high but worker has no data to store to disk.  Perhaps some other process is leaking memory?  Process memory: 707.59 MB -- Worker memory limit: 1000.00 MB
[#################                       ] | 43% Completed | 15min 30.0sdistributed.worker - WARNING - Memory use is high but worker has no data to store to disk.  Perhaps some other process is leaking memory?  Process memory: 707.59 MB -- Worker memory limit: 1000.00 MB
[#################                       ] | 43% Completed | 15min 30.2sdistributed.worker - WARNING - Memory use is high but worker has no data to store to disk.  Perhaps some other process is leaking memory?  Process memory: 707.59 MB -- Worker memory limit: 1000.00 MB
[#################                       ] | 43% Completed | 15min 30.5sdistributed.worker - WARNING - Memory use is high but worker has no data to store to disk.  Perhaps some other process is leaking memory?  Process memory: 707.59 MB -- Worker memory limit: 1000.00 MB
[#################                       ] | 43% Completed | 15min 30.7sdistributed.worker - WARNING - Memory use is high but worker has no data to store to disk.  Perhaps some other process is leaking memory?  Process memory: 707.59 MB -- Worker memory limit: 1000.00 MB
[#################                       ] | 43% Completed | 15min 30.9sdistributed.worker - WARNING - Memory use is high but worker has no data to store to disk.  Perhaps some other process is leaking memory?  Process memory: 707.59 MB -- Worker memory limit: 1000.00 MB
[#################                       ] | 43% Completed | 15min 31.0sdistributed.worker - WARNING - Memory use is high but worker has no data to store to disk.  Perhaps some other process is leaking memory?  Process memory: 707.59 MB -- Worker memory limit: 1000.00 MB
[#################                       ] | 43% Completed | 15min 31.2sdistributed.worker - WARNING - Memory use is high but worker has no data to store to disk.  Perhaps some other process is leaking memory?  Process memory: 707.59 MB -- Worker memory limit: 1000.00 MB
[########################                ] | 60% Completed | 21min 44.3sdistributed.worker - WARNING - Memory use is high but worker has no data to store to disk.  Perhaps some other process is leaking memory?  Process memory: 712.99 MB -- Worker memory limit: 1000.00 MB
distributed.worker - WARNING - Memory use is high but worker has no data to store to disk.  Perhaps some other process is leaking memory?  Process memory: 712.99 MB -- Worker memory limit: 1000.00 MB
[########################                ] | 60% Completed | 21min 44.5sdistributed.worker - WARNING - Memory use is high but worker has no data to store to disk.  Perhaps some other process is leaking memory?  Process memory: 712.99 MB -- Worker memory limit: 1000.00 MB
[########################                ] | 60% Completed | 21min 44.6sdistributed.worker - WARNING - Memory use is high but worker has no data to store to disk.  Perhaps some other process is leaking memory?  Process memory: 712.99 MB -- Worker memory limit: 1000.00 MB
[########################                ] | 60% Completed | 21min 44.8sdistributed.worker - WARNING - Memory use is high but worker has no data to store to disk.  Perhaps some other process is leaking memory?  Process memory: 712.99 MB -- Worker memory limit: 1000.00 MB
[########################                ] | 60% Completed | 21min 44.9sdistributed.worker - WARNING - Memory use is high but worker has no data to store to disk.  Perhaps some other process is leaking memory?  Process memory: 712.99 MB -- Worker memory limit: 1000.00 MB
[########################################] | 100% Completed | 34min  9.6s
Traceback (most recent call last):
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/distributed/protocol/pickle.py", line 49, in dumps
    result = pickle.dumps(x, **dump_kwargs)
TypeError: cannot pickle '_thread.lock' object

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/orange/adamginsburg/ALMA_IMF/reduction/analysis/statcont_cubes.py", line 111, in <module>
    fits.PrimaryHDU(data=result[1], header=cube[0].header).writeto(outfn,
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/astropy/utils/decorators.py", line 535, in wrapper
    return function(*args, **kwargs)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/astropy/io/fits/hdu/base.py", line 371, in writeto
    hdulist.writeto(name, output_verify, overwrite=overwrite,
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/astropy/utils/decorators.py", line 535, in wrapper
    return function(*args, **kwargs)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/astropy/io/fits/hdu/hdulist.py", line 943, in writeto
    hdu._writeto(hdulist._file)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/astropy/io/fits/hdu/base.py", line 677, in _writeto
    self._writeto_internal(fileobj, inplace, copy)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/astropy/io/fits/hdu/base.py", line 683, in _writeto_internal
    data_offset, data_size = self._writedata(fileobj)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/astropy/io/fits/hdu/base.py", line 615, in _writedata
    size += self._writedata_internal(fileobj)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/astropy/io/fits/hdu/image.py", line 623, in _writedata_internal
    return self._writeinternal_dask(fileobj)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/astropy/io/fits/hdu/image.py", line 709, in _writeinternal_dask
    output.store(outarr, lock=True, compute=True)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/dask/array/core.py", line 1433, in store
    r = store([self], [target], **kwargs)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/dask/array/core.py", line 981, in store
    result.compute(**kwargs)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/dask/base.py", line 167, in compute
    (result,) = compute(self, traverse=False, **kwargs)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/dask/base.py", line 452, in compute
    results = schedule(dsk, keys, **kwargs)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/distributed/client.py", line 2705, in get
    futures = self._graph_to_futures(
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/distributed/client.py", line 2641, in _graph_to_futures
    "tasks": valmap(dumps_task, dsk),
  File "cytoolz/dicttoolz.pyx", line 181, in cytoolz.dicttoolz.valmap
  File "cytoolz/dicttoolz.pyx", line 206, in cytoolz.dicttoolz.valmap
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/distributed/worker.py", line 3358, in dumps_task
    return {"function": dumps_function(task[0]), "args": warn_dumps(task[1:])}
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/distributed/worker.py", line 3367, in warn_dumps
    b = dumps(obj, protocol=4)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/distributed/protocol/pickle.py", line 60, in dumps
    result = cloudpickle.dumps(x, **dump_kwargs)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/cloudpickle/cloudpickle_fast.py", line 73, in dumps
    cp.dump(obj)
  File "/orange/adamginsburg/miniconda3/envs/dask-new/lib/python3.8/site-packages/cloudpickle/cloudpickle_fast.py", line 563, in dump
    return Pickler.dump(self, obj)
TypeError: cannot pickle '_thread.lock' object

Solution to the  _thread.lock may be, for this specific case where we can afford to do this, to compute() into memory before writing to disk as FITS.  Alternative might be to write that intermediate result to zarr.
It's also possible that I effectively tried to change schedulers between different dask steps, and that screwed it up

@astrofrog I'm encountering further OOM errors in places I don't expect to.  For example:
stdspec = mcube.mad_std(axis=(1,2))#, how='slice')

fails (w/OOM kill) on a cube with these properties:
DaskVaryingResolutionSpectralCube with shape=(2066, 2000, 2240) and unit=Jy / beam and chunk size (322, 250, 320):
 n_x:   2240  type_x: RA---SIN  unit_x: deg    range:   239.440501 deg:  239.556884 deg
 n_y:   2000  type_y: DEC--SIN  unit_y: deg    range:   -53.996495 deg:  -53.935415 deg
 n_s:   2066  type_s: FREQ      unit_s: Hz     range:<PHONE_NUMBER>1.500 Hz:93245261123.212 Hz

which suggests that too much is being loaded at once.  Do we need to enforce spectrally smaller chunks for planar operations like ths?

Rechunking fixed the previous problem, which is not very encouraging.  Dask seems to be extremely tetchy about how it handles memory and really needs to be carefully fine-tuned to avoid using more than its allotted memory.
Spatial mad_std
DaskVaryingResolutionSpectralCube with shape=(2066, 2000, 2240) and unit=Jy / beam and chunk size (16, 1250, 1600):
 n_x:   2240  type_x: RA---SIN  unit_x: deg    range:   239.440501 deg:  239.556884 deg
 n_y:   2000  type_y: DEC--SIN  unit_y: deg    range:   -53.996495 deg:  -53.935415 deg
 n_s:   2066  type_s: FREQ      unit_s: Hz     range:<PHONE_NUMBER>1.500 Hz:93245261123.212 Hz
[########################################] | 100% Completed | 18min 20.6s
Elapsed: 1105.749336719513

These issues keep coming up, so this is a log of my woes, but I'm closing the issue because we haven't come up with any way to take action on it.  The general problem of OOM issues remains, but it will be better to address them with specific test cases, if I can identify some.


Update jsoniter-scala-core, ... to 2.27.3

About this PR
📦 Updates

com.github.plokhotnyuk.jsoniter-scala:jsoniter-scala-core
com.github.plokhotnyuk.jsoniter-scala:jsoniter-scala-macros

from 2.17.9 to 2.27.3
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.github.plokhotnyuk.jsoniter-scala" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.github.plokhotnyuk.jsoniter-scala" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:early-semver, commit-count:1

Superseded by #843.


#692 - [Manual] - Incorrect list of actions for user in offline mode - Implemented

#692 - Implemented

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: Vadim-Bulavin sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Add experimental batch processing command line interface for collageradiomics

This pull request adds an experimental command line interface version of collageradiomics for batch processing. This tries to extend the cli with an option for extended stats (mean and IQR), as well as the selection for specific labels (e.g., mask contains 3 labels but we just want to analyse one of those).
The output is saved on a csv were the rows are the cases and the columns contained the case_id, image file path, mask file path, options used (for reference of options utilised) and the collage radiomics features.
Hope you find this useful and I am here to contribute and solve any issues this code may have

Forgot to mention that the input file is expected to be a csv with 3 columns with header as follows:
ID,Image,Mask
<case_id_01>,<image_filepath_01>,<mask_filepath_01>
...
<case_id_n>,<image_filepath_n>,<mask_filepath_n>

An additional change so that the error file name matches the output file name prefixed by "errors_"

@JoaoSantinha Thanks for this! Taking a look now.

@JoaoSantinha These additions look good overall, and I like adding extra extended statistics. We'd prefer to have this option integrated with our existing cli, as opposed to making another separate module. Could you please port the changes to https://github.com/radxtools/collageradiomics/blob/master/cli/collageradiomicscli.py while also maintaining backwards compatibility with the existing interface?
I would suggest checking to see if the -i parameter is a CSV or an image. If it's an image, it should process an individual image, and if it is a CSV file, it should do the batch processing.

@nathanhillyer thanks for the feedback!
I agree with your suggestions and with having a unique cli integrating both approaches.
I will try to do these this weekend and open a new PR for this additional features of the cli.

@JoaoSantinha Great, looking forward to it!

@nathanhillyer I am getting my hands on this (sorry it took some time to have some buffer for this)
Currently if more than one label is included in the mask it will consider all the different labels as a single label. In this pull request I included an option to select the value of the label to be included or use all of these labels as unique segmentation by setting the label value to -1. Do you want something like this?
I can put the default value to -1, so that the default works as previously by I think it would be nice to have the option to select specific labels.

@nathanhillyer I am getting my hands on this (sorry it took some time to have some buffer for this)
Currently if more than one label is included in the mask it will consider all the different labels as a single label. In this pull request I included an option to select the value of the label to be included or use all of these labels as unique segmentation by setting the label value to -1. Do you want something like this?
I can put the default value to -1, so that the default works as previously by I think it would be nice to have the option to select specific labels.

@JoaoSantinha Sure, that sounds reasonable.

@JoaoSantinha Sure, that sounds reasonable.


Add dotnet8 AOT

Still testing...

Thanks @slang25 , I'm closing this PR in favor of https://github.com/maxday/lambda-perf/pull/935


Removing QBFT warning

considering QBFT is not longer a beta.

Pull Request Description
Fixed Issue(s)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Port the source code to TypeScript

Coverage decreased (-0.4%) to 81.061% when pulling 88b5de60522f4a38f61cded1cc2825060cbddeed on feature/typescript into 6a68c70a792434d9644bbb99d3d64c5e8af540ba on develop.


demo-app: Removable chips in a form field (behavioral differences between Firefox and Chrome)

Bug, feature request, or proposal:
Bug
What is the expected behavior?
the same behavior in all browsers
What is the current behavior?
In chrome the chips exit from the "bound" of the form field.

In Firefox the form field will vertically grow when required.

I think that the Firefox behavior is the better one but when adding a certain number of chips you can't see the text cursor (issue already open here)
What are the steps to reproduce?
Simply run the demo-app and go to this url in Firefox and in chrome:
http://localhost:4200/accessibility/chips
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Current latest of this repo, I don't know if with the previous versions show the same problem.

I think this is obsolete. Now the behaviors are the same in chrome and firefox.


Automated cherry pick of #4779: fix(esxi-agent): Avoid redundant agent & Adjust workspace path

Cherry pick of #4779 on release/3.0.
#4779: fix(esxi-agent): Avoid redundant agent & Adjust workspace path

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/3.0@ba89e19). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff              @@
##             release/3.0   #4794   +/-   ##
=============================================
  Coverage               ?   6.78%
=============================================
  Files                  ?     524
  Lines                  ?   89763
  Branches               ?       0
=============================================
  Hits                   ?    6093
  Misses                 ?   83163
  Partials               ?     507

Flag
Coverage Δ

#aFlag
6.78% <0%> (?)

Impacted Files
Coverage Δ

pkg/multicloud/esxi/storage.go
0% <0%> (ø)

Continue to review full report at Codecov.

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


[ENH] select columns by level

PR Description
Please describe the changes proposed in the pull request:

allow column selection by level
allow slicing on non unique labels that are sorted

This PR resolves #1105 .

PR Checklist

Please ensure that you have done the following:

[ ] PR in from a fork off your branch. Do not PR from <your_username>:dev, but rather from <your_username>:<feature-branch_name>.

[ ] If you're not on the contributors list, add yourself to AUTHORS.md.

[ ] Add a line to CHANGELOG.md under the latest version header (i.e. the one that is "on deck") describing the contribution.

Do use some discretion here; if there are multiple PRs that are related, keep them in a single line.

Automatic checks
There will be automatic checks run on the PR. These include:

Building a preview of the docs on Netlify
Automatically linting the code
Making sure the code is documented
Making sure that all tests are passed
Making sure that code coverage doesn't go down.

Relevant Reviewers

Please tag maintainers to review.

@ericmjl

🚀 Deployed on https://deploy-preview-1111--pyjanitor.netlify.app

Added comments to the updated code. Kindly have a review when U can @ericmjl

Approved! Thank you, @samukweku!

The PR has been open for about a week. I'd vote that we wait another day before merging.

Thanks for d review @ericmjl , as it prompted me to review d logic

@samukweku are we good to merge?

@ericmjl kindly give it a day or two ...

@ericmjl ok to merge :grin:

Merged!! Thank you, @samukweku!


Implement NSGeometry NSMake* funcs, simplify init methods, add unit tests

This PR implements the following:

NSMake* functions from NSGeometry

NSMakePoint
NSMakeSize
NSMakeRect

Simplify the default initializers to delegate to the memberwise initializers
Unit tests for all additions/changes

I decided to make CGFloat implement Comparable mostly to simplify testing. (Since CGFloat(1.0).native became very verbose and repetitive.) However, I noticed that a PR for conforming NSDate to Comparable was declined because it was considered an API change. It's not clear if this is also considered an API change that necessitates following the Swift evolution process since CGFloat is more or less a a basic type? In any case, I'm happy to make any necessary changes.

Oh I just noticed #35. Ha, I should have looked more closely. Sorry for the dupe. :smile:
This could still be considered for the unit tests alone. (Or considered altogether since it is a smaller change.)

I'm going to ask for #35 to be rebased, then we can incorporate your unit tests as a PR on top of that.

Thanks @parkera !
Updated:

rebased
some formatting

My original tests don't cover everything added from #35, but I'll submit another PR for those to keep this one small. :smile:


"Dump Your Brain:" textarea doesn't allow for spellcheck

When creating a note (and presumably editing), the "Dump Your Brain:" section doesn't trigger Google Chrome to spellcheck the text.
As someone who misspells things hourly, this issue really hurts my productivity by having to re-read my notes several times more than normal.
A built-in spell checker could be an alternate or additional solution.

As much as I hate +1
+1

This was fixed with the new editor.


Are component-level annotations available?

I was wondering if the annotations for an element (a region comprising one or more tokens), such as for example a paragraph (similar to the annotations for PubLayNet) are available, or if there exists a mechanism to compute them. I suppose running some sort of clustering algorithm could do the work decently, but I would like to know if these annotations already exist.
Thanks in advance for your help!

Yes, we convert DocBank to the format of the object detection models and evaluate Faster R-CNN on the test set. The newest result has been updated in GitHub.
The converting process will be given on the newest paper and we will also provide a converting script. Both of them will come soon.

https://github.com/doc-analysis/DocBankLoader

Thanks for the pointers!


fix: clear target test runner state after each run

The target test framework had weird behavior where all 14 default tests passed for me but when I looked closer only 1 table was getting created in the destination database. I figured out it was because the input file was getting stuck on the first test's input file.
The test overrides the runner input_filepath https://github.com/meltano/sdk/blob/fda24cfba259b917d0ab3a74b355346e7b0027e9/singer_sdk/testing/templates.py#L325 to pass in the path to the test's JSONL data but it only gets used on the first test because the second test uses the runner while it still has self._input state from the previous run so it skips the logic for reading in the new file. Ultimately all following tests get no input so they silently pass but dont actually do anything.
I confirmed this fix worked in https://github.com/MeltanoLabs/target-snowflake/pull/38.

:books: Documentation preview :books:: https://meltano-sdk--1749.org.readthedocs.build/en/1749/

@pnadolny13 @edgarrmondragon I think the issue and fix is a bit broader than resetting the target_input (though that obviously works).
A reset is needed because we made the runner instance a pytest fixture with scope="class". This is desirable for Taps as it means they can run once (to hydrate the runners record/state/messages attributes) and then run multiple tests on the same record set. It was done to minimise the number of times the Taps actually has to run. However, with Target tests and especially with the file-based ones, we actually want to allow the Target to sync multiple times with the different file inputs. So I believe the change needed is to set the runner scope to function when constructing Target classes 🙂 This has a similar effect to resetting the runners input as each runner is 'fresh' and so doesn't have any previous state.
Will raise a PR in target-snowflake to test the fix.

Closing in favor of https://github.com/meltano/sdk/pull/1752 and I also found another bug for tests that follow a pytest.raises( we weren't getting a reset, I fixed that in target-snowflake for now though.


fix: no heading tags in footer

🚧 Fixes Issue
closes #1039
Changes made

move ToastContainer and Modal component outside from the footer section.
replace <h1> tag with <p> tag.

Screenshots  📸
after made changes

Please close this PR, and make a PR to the beta branch with the latest changes pulled as said earlier.

Please close this PR, and make a PR to the beta branch with the latest changes pulled as said earlier.

Apologies for the confusion. I accidentally created the pull request against the main branch instead of the beta branch. I'll make the necessary adjustments and create a new pull request targeting the beta branch. Thank you for your time.


Cholesterol likelihood

Hi,
I just would like to raise a concern about the number of eggs we're scrambling
Would it be any risk of having a cholesterol attack after this breakfast?
best,
Angelica

Sounds great! Do you want to eat it anyway?
Regards,
Anna

sure!
eggs are eggs after all, right?! :P

#2 and go to the trening;)
regards
Anna


[warning] ofGraphics: ofPushStyle():

Always get this:
[warning] ofGraphics: ofPushStyle(): maximum number of style pushes << 32 reached, did you forget to pop somewhere?
And no particles :-(
Mac Os 10.10
Any suggestions?

pop fixed
what kind of computer / videocard are you using?

MacBookPro10,2
Intel Core i5
Intel HD Graphics 4000
32-Bit Color (ARGB8888) Retina

And with init I got:
[warning] Framebuffer with id: cannot be bound onto itself.
Most probably you forgot to end() the current framebuffer before calling begin() again.
[ error ] unbalanced fbo bind/unbind binding default framebuffer
May be this is a reason. I am also switch of USE_PROGRAMMABLE_GL.

The addon is made for discrete videocards from nvidia or ati.
I'm surprised it works on the hd4000 at all.
My macbook also has the hd4000, but i could not reproduce the error.
The particles work

If you can find more about this bug let me know

Thanks, will try to figure out.


Improve logic to extract identifier names

Description
Previously, the logic to extract original identifier names from query string was
not proper and could not handle the identifiers with special characters or object
name being prefix of schema name. This logic was there to extract original table
name and original function/procedure name from the query and due to this issue,
we were storing wrong original names.
Implemented helper function extract_multipart_identifier_name which improves
the logic to extract original name from a multi-part identifier in a query string taking
care of spaces or possibly quoted identifier. It internally uses extract_identifier
function to extract individual parts of an identifier.
Additional fixes:

Fixed sp_rename to properly handle rename of a table so that it also updates the
underlying original table name (bbf_original_rel_name).
Fixed helper function babelfish_sp_rename_word_parse which is used by sp_rename
to split multi-part identifier names. Previously, it was using string_split() for the splitting
which could not handle the quotes or special characters. Implemented helper SQL function
babelfish_split_identifier which is mostly a wrapper over split_object_name C function
to correctly split multi-part identifiers.
Updated logic to fetch original table_name/column_name in sql views information_schema_tsql.columns_internal
and information_schema_tsql.tables so that they don't assume that bbf_original_rel_name
or bbf_original_name is always the first option in reloptions and attoptions list respectively,
instead now the logic is to iterate over the whole list and search of the desired option.

Task: BABEL-5089
Signed-off-by: Rishabh Tanwar<EMAIL_ADDRESS>Test Scenarios Covered

Use case based -

Boundary conditions -

Arbitrary inputs -

Negative test cases -

Minor version upgrade tests -

Major version upgrade tests -

Performance tests -

Tooling impact -

Client tests -

Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

83 of 85 (97.65%)  changed or added relevant lines in 5 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.02%) to 73.455%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

contrib/babelfishpg_tsql/src/hooks.c
30
31
96.77%

contrib/babelfishpg_tsql/src/procedures.c
18
19
94.74%

Files with Coverage Reduction
New Missed Lines
%

contrib/babelfishpg_tsql/src/procedures.c
1
88.43%

Totals

Change from base Build<PHONE_NUMBER>0:
0.02%

Covered Lines:
42231

Relevant Lines:
57492

💛  - Coveralls


[Bug] Error while viewing workflow that contains local activities. “13 INTERNAL: Failed to parse server response”

Describe the bug
I'm getting error in temporal-web while trying to view workflow that contains local activities without return parameters.
To Reproduce
Steps to reproduce the behavior:

I took an example from the Go getting started guide and changed it to use Local Activities.

After I run this sample, I get “13 INTERNAL: Failed to parse server response” while viewing the workflow inside of temporal-web

I also get this error inside of temporal-web docker container

Expected behavior
I can view such workflows without getting an error
Desktop

OS: Windows
Browser: Chrome
Temporal Web Version: 1.5.2 (Docker)
Temporal Version: 1.6.0 (Docker)

Additional details

I also noticed that as soon as I add at least an empty return result to the activities, it starts to open without any error

2. I have started a discussion in community

Seems node grpc is failing at parsing MarkerRecordEvent when the result is set to null (which corresponds to returning error in activity implementation)

In case of returning (interface {}, error), the result payload is filled:

I'm considering changing the result key in map from nil to empty array. Asked the temporal server side of the team whether this would be backwards compatible change
Some details:
when we add Marker Recorded event, we populate the details field with map<Payloads>
Then the result key value may be set to nil if activity's return type is error (set to nil):

we've discussed with the SDK team: there is no value from having empty result in the MarkerRecordedEventAttributes.details of type map<string, Payloads>. Both old (grpc) and new (@grpc/grpc-js) libs fail to process such payload. The easiest is to fix this in go SDK itself
The issue didn't repro with sdk-java as it doesn't set null value in details of type map<string, Payloads>


Update configuring-teams-calling-quickstartguide.md

@nenonix @JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@LanaChin PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


Restore ESLint warnings as errors (ignoring them for now)

Explanation

Currently, yarn lint produces a bunch of warnings from ESLint. These warnings were added in a previous commit that upgraded ESLint packages as a way to avoid fixing lint violations created by the upgrade. However, this causes two problems:

They produce a lot of noise that makes it very difficult to find true errors, especially when looking at a CI run.
They allow new instances of these violations to show up (because warnings don't cause eslint to fail).

This commit removes the overrides from the ESLint config for these rules so that they go back to being errors and adds eslint-disable directives above the lines that cause the violations. Note that this is not intended to be a long-term solution, and in the future, we should dedicate time to either fixing the violations or explaining why ignoring them is necessary.
References

Fixes #4381.
Changelog

(There are no changes to functionality.)
Checklist

[x] I've updated the test suite for new or updated code as appropriate
[x] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
[x] I've highlighted breaking changes using the "BREAKING" category above as appropriate

@MajorLift I don't have plans for the changes you mention, but they sound good, so feel free to create tickets/PRs!


Don't crash when failing to read an h5 file

It's pretty good about not crashing when trying to read something that it doesn't think is an h5, but if it thinks it's an h5 and fails to read, it does crash.

Fixed in 0.12.0


Get all forms and childrens

I don't want to the whole stuff of listing, my problem is : NO solutions are working.
I would like to get all forms in a page, then being able to get all childs from any of the forms i gathered before.
I am not asking anything more.
I want to find the form with a filter either form or form[id="hello"]
That's all i am asking.

const puppeteer = require('puppeteer');

(async () => {
  const browser = await puppeteer.launch();
  const page = await browser.newPage();
  // Replace URL_FORMS with the URL you need it to go to
  await page.goto(URL_FORMS);
  const forms = await page.$$('form') // Selects all form elements on the page
  // Loop over each form
  forms.forEach( async form => {
     // Grab all children elements of the form
      const formChildren = await page.evaluateHandle(el => el.children, form);
      // Do what you want with form children per form.
  })
  await browser.close();
})();

Writing this without testing but this is what you are looking for. Please look at the puppeteer API documentation for the functions I have used and the descriptions to expand this further.


different colors?

Is there a way to [easily] customize the colors used for the headings and data?
For example, the Size column magenta color is very difficult to read.

Yes, maybe I should make this customizable.
For now what you could do is to add

	const elements = this.document.querySelectorAll('.size');
	elements.forEach(element => {
		element.style.color = 'red';
	});

at the end of your registerParser function.
Before you ask :-) the other columns are called

offset
size
name
value
description

Perfect, thank you.
Yes, making it customizable would be nice but as long as there is a workaround time better spent on higher priority functional enhancements.
However, I think the 'detail' expansion is lazily executed and the code in registerParser doesn't seem to affect that, any suggestions for getting the detail color changed?

Just as an additional note to this, I used a method to set the css vars directly because my vscode theme has conflicting colours for the 2 chosen.
const root = this.document.querySelector(":root");
root.style.setProperty("--vscode-editorIndentGuide-background", "#1b1b1b");
root.style.setProperty("--vscode-badge-background", "#222");


added go.mod #195

added go.mod #195
hopefully fixes the build issue.

Codecov Report

Merging #196 (723201d) into master (d48afd6) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #196   +/-   ##
=======================================
  Coverage   58.74%   58.74%
=======================================
  Files           9        9
  Lines         143      143
=======================================
  Hits           84       84
  Misses         57       57
  Partials        2        2

Continue to review full report at Codecov.

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

Codecov Report

Merging #196 (723201d) into master (d48afd6) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #196   +/-   ##
=======================================
  Coverage   58.74%   58.74%
=======================================
  Files           9        9
  Lines         143      143
=======================================
  Hits           84       84
  Misses         57       57
  Partials        2        2

Continue to review full report at Codecov.

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

@xitongsys could you please help (again) on updating the parquet APIs? It will be nice not to be fixed to an old version.

@xitongsys could you please help (again) on updating the parquet APIs? It will be nice not to be fixed to an old version.


sftp: allow customizing MaxConcurrentRequestsPerFile and MaxPacket

What does this PR change? What problem does it solve?
It allows customizing connection parameters in the underlying sftp library, which should help with the currently poor sftp performance to some extent.

Was the change previously discussed in an issue or on the forum?
See https://github.com/restic/restic/issues/4209

Checklist

[x] I have read the contribution guidelines.
[x] I have enabled maintainer edits.
[ ] I have added tests for all code changes.
[ ] I have added documentation for relevant changes (in the manual).
[x] There's a new file in changelog/unreleased/ that describes the changes for our users (see template).
[x] I have run gofmt on the code in all commits.
[ ] All commit messages are formatted in the same style as the other commits in the repo.
[ ] I'm done! This pull request is ready for review.

I've fixed the actual underlying problem of the SFTP performance issue in https://github.com/restic/restic/pull/4782 . That makes this parameter tuning completely obsolete. In addition, changing MaxConcurrentRequestsPerFile using this PR never had any effect, see my PR for details.


Create Netman File Explorer UI

Netman currently does not have a UI in place for traversing directories, and instead relies purely on the user knowing the path to the file they wish to browse.

Consider additionally creating 3rd party integrations with some of the popular file managers out there (such as telescope file picker or  even telescope as a whole)

Migrating to Milestone 1.0 as this is already "done"


Write HTML to a fmt::Write instead of a String.

My motivation is that I would like to use this library in a static blogging engine but I use a custom buffer type.
The downside is error handling. This may significantly impact performance (I don't know what benchmarks you usually run). The upside is that users can write directly to custom buffers as long as those buffers implement fmt::Write.
Error Handling Alternatives:

Panic on error and tell users to not pass in writers that can fail. Users can always record write errors on the side.
Provide a custom Write trait that doesn't support error reporting.

Also, I kept the current fresh_line behavior but we could probably make this faster if we allow extra newlines.
Compatibility note: This requires rust 1.1 beta for Write::write_char.
FYI, I've signed the CLA.

I think it'd be better to use io::Write instead of fmt::Write, so you can write directly to a file or similar. Tests that me an @raphlinus did seem to suggest that writing the output is a surprisingly large amount of the time. Using io::Write is slight trickier, but for the most part the write_strs can be replaced with write_all and byte-string literals.

Actually, looking more carefully at the code, it'd be trivial to switch to io::Write given that you've already abstracted the "buffer".

io::Write is won't work because it doesn't guarantee utf8 encoding which makes it impossible to safely write to a String. If you want to support io::Write, I could implement an adapter (like the one used in io::Write::fmt) and provide two functions: push_html_fmt, push_html_io.

@Stebalien but isn't almost everything pushed either already a str or is a literal? I'm not sure what the issue is.

@Aatch It is. The problem is that io::Write throws away the fact that the data is utf8 so if you want to write to a String, you need to re-assure rust that the data really is utf8. Basically, if you want to be able to write to both files and strings, there are two ways to go:

Accept io::Write and implement struct IPromiseThisIsUtf8WriteAdapter<W: fmt::Write>(&mut W) (implements io::Write).
Accept fmt::Write and implement struct WriteAdapter<W: io::Write>(&mut W) (implements fmt::Write).

The second method is safer because it doesn't convert from utf8 to raw bytes and back again.

@Stebalien ah, I didn't think of that. I definitely think we should support both options, assuming that push_html_io is just a helper fn over push_html_fmt I can't see anything wrong with doing it that way.

I wanted to benchmark this, but it seems to introduce logic bug. The easiest way to provoke it is RUST_BACKTRACE=1 cargo run -- -s ~/dl/cmark/test/spec.txt 50, where spec.txt is from cmark. That's Example 50, which doesn't seem particularly exotic.
Backtrace below:
thread '<main>' panicked at 'arithmetic operation overflowed', src/html.rs:37
stack backtrace:
   1:        0x107192145 - sys::backtrace::write::hce8edc3761615a91fas
   2:        0x107195794 - panicking::on_panic::haf19346a6a6623d7vvw
   3:        0x10718c018 - rt::unwind::begin_unwind_inner::h84a637bb4fc9a013Ndw
   4:        0x10718c63c - rt::unwind::begin_unwind_fmt::he799ce251af7040fTcw
   5:        0x10719504c - rust_begin_unwind
   6:        0x1071b6af5 - panicking::panic_fmt::h16e5884fd9bf851ci5B
   7:        0x1071b63d4 - panicking::panic::h37c142b5f2d1829eP3B
   8:        0x107118b0c - html::FreshLineAdapter<'b, W>.Write::write_str::h5689971399085283464
   9:        0x10711b244 - escape::escape_html::h11118945503011952733
  10:        0x107115b48 - html::Ctx<'b, I, W>::run::h2540889576962225024
  11:        0x107115630 - html::push_html::h3609764159648968415
  12:        0x107113be7 - render_html::h56419a67795c2b60qaa
  13:        0x1071290d0 - run_spec::hcec7f0b6257f74f5Bja
  14:        0x10712c0ac - main::h073de8bb5db93de6bsa
  15:        0x1071970b8 - rust_try_inner
  16:        0x1071970a5 - rust_try
  17:        0x107195fa0 - rt::lang_start::h9fbea85581be889fzqw
  18:        0x10713f75e - main
[50]An unknown error occurred

I'm ok with using a Writer of some kind instead of a string, as long as it doesn't negatively impact performance. My sense is that the API with string is easier because you don't have to worry about errors, and pretty much just as flexible. I haven't measured it carefully, but I suspect that the actual cost of the extra string copy is pretty minimal, as it should all be done with wide SIMD instructions on modern CPU's.

Sorry about that. Fixed (although I'm still failing the 4 spec tests that master fails).

I'm seeing a 0.96x speedup (i.e. slowdown) when benching the spec so it's not too bad. Also, I've added a method for pushing to an io::Write. Would you like that now or in a new pull request?

Ping.

I'm on vacation right now and away from my development machine. In any
case, I am skeptical about this patch. I'll try to give a full review when
I get back.
On Jul 13, 2015 12:04 PM, "Steven Allen"<EMAIL_ADDRESS>wrote:

Ping.
—
Reply to this email directly or view it on GitHub
https://github.com/google/pulldown-cmark/pull/3#issuecomment-121024344.


EntitlementManagement - AccessPackages

General Issue tracker for everything related to AccessPackage implementation within Identity & Governance Management. Will leave PR in draft state any comments, suggestions or contributions welcome
https://docs.microsoft.com/en-us/graph/api/resources/entitlementmanagement-root?view=graph-rest-beta

[x] accessPackage
[x] accessPackageAssignmentPolicy
[x] accessPackageCatalog
[x] accessPackageResourceRequest - Non-Standard Implementation (For adding resources to Catalogs)
[x]  accessPackageResource - RO Non-Standard

Rest of endpoints do not have Creation/Deletion capabiltity / Directly related to IDAG IaC flows

@manicminer Could you potentially give some of this a  glance on in the draft PR? The first three endpoints are pretty straightforward CRUD, but "accessPackageResourceRequest" endpoint only has List and Create availiable where having some workaround implementation on the SDK would be needed. Specifically take a look at accesspackageresourcerequest.go - In order to delete you need to POST as if it where a Create Method. Also seems to be some lag on the backend potentially if youve just created an AP / Group to waited the Create func for 15s
Return is also a bit weird as a resource creation request != resource, therefore the resource ID (but the ID of the Request) is not returned and while can be figured out via pseduo get method on the corresponding tests file (L92) its a bit weird
Let me know what you think about it,  if we are ok with a few work arounds and impact on downstream implemnetation this is definetly do-able, elsewise will remove accessPackageResourceRequest  for this PR
Tests so far are all good
ok      github.com/manicminer/hamilton/msgraph  27.013s

@petr-stupka Thanks this is extremely useful, understood requests are non standard and have a pseduo delete using admin remove. Have pretty much done exactly what youve said if you look at the PR
Mustve looked over the execute immediately option - Will add, @manicminer will leave Consistency func in but should shorten time if we are OK to hardcore that? No idea why wouldnt be always on.
Elsewise have an issue with the RoleScope endpoint, from what i currently understand once a request has been done to add something to a Catalog, you call the RoleScope endpoint to add it to an AP - but Theres no deletion capability so i cant implement it? Unless its just not documented properly - would be big help if you know.

@kaovd pls don't take me wrong if i say something what is already in, i need to dig in your PR to have full understanding. We have PowerShell script for that and i spend some time to understand the dependencies and the process so i'm happy to try to explain questions you may have to be able to complete it or help with some development. So will give you info about the RoleScopes asap

Thanks, interested to see potential implementations

Documentation
For the development I used two documentation as both of them missing some important information and reference
MS Graph: https://docs.microsoft.com/en-us/graph/api/resources/entitlementmanagement-root?view=graph-rest-beta
Powershell: https://docs.microsoft.com/en-us/powershell/module/microsoft.graph.identity.governance/?view=graph-powershell-beta
Powershell cmdlets have BodyParameter input, which is basically Graph API request body body and all the properties are listed (in a bit messy way)
As example AccessPackageResourceRequest and the executeImmediately parameter. You can find it in PWSH under BODYPARAMETER object (json object) docs and it is not in the Graph Documentation examples.
RoleScope
from what I currently understand once a request has been done to add something to a Catalog, you call the RoleScope endpoint to add it to an AccessPackage in the catalog
that's correct.
To delete it, pwsh have cmdlet for it. And I assume the cmdlet just set null because of as you said, there is no endpoint for that
This can be done on AccessPackage object
see: https://docs.microsoft.com/en-us/powershell/module/microsoft.graph.identity.governance/update-mgentitlementmanagementaccesspackage?view=graph-powershell-beta
BODYPARAMETER object / [AccessPackageResourceRoleScopes <IMicrosoftGraphAccessPackageResourceRoleScope[]>]: Nullable
as this sis array, the specific object in the array is deleted (replaced by null?)

After a bit of battling and looking at requests in Azure Portal itself, I've finally figured out where in the world some of these endpoints actually are.
The RoleScope DELETE endpoint is not documented, however as you mentioned @petr-stupka it is in Ms Graph Powershell Beta, only problem is its not implemented properly there as it does not work

Not sure if what you found was any different - This is effectively doing DELETE accessPackages/id/accessPackageRoleScopes/id
However, looking at portal behaviour as obviously this endpoint has to exist somewhere - we see
DELETE accessPackages/id/accessPackageRoleScopes
with a Body of the resource, which is standard Creation style behaviour. However its used in a delete context here and comes back with 200

For the rest of the UPDATE Methods in pwsh but not the docs I'm going to assume it just deletes and recreates the resources or dosen't work - I want to deviate from the docs as least as possible for SDK Sanity
Only problem is this DELETE endpoint is broken in offical MS Graph Endpoint - Also it requires a body which is weird for DELETE behaviour

I have no idea what its complaining does not fall in range using same requests as Azure Portal - so I'm not going to try and keep attempting to implement an undocumented endpoint - although even if I could not sure if its SDK legal
Meantime I will implement the Create, List and pseduo Get endpoints but will be unusable downstream (terraform) as theres no delete

Yeah, the PowerShell module is full of bugs (first release). Many cmdlet's often reference v1 instead of beta or have other bugs in it.
I think you right with the endpoint .. let's check thatin Microsoft Graph metadata instead of searching MS Docs: https://raw.githubusercontent.com/microsoftgraph/msgraph-metadata/master/openapi/beta/openapi.yaml
search for this operation:
identityGovernance.entitlementManagement.accessPackageCatalogs.accessPackages.DeleteAccessPackageResourceRoleScopes

you can see example how to form the request:
/identityGovernance/entitlementManagement/accessPackageCatalogs/{accessPackageCatalog-id}/accessPackages/{accessPackage-id}/accessPackageResourceRoleScopes/{accessPackageResourceRoleScope-id}/accessPackageResourceRole
as I can see there is no requestBody required like on 'patch' operation
btw, https://github.com/microsoftgraph/msgraph-metadata as source for informations

Hi @kaovd had you chance to test it. I'm interested if the Graph Metadata can be used as reliable source. Btw, if I can help with any part of the development, please let me know

Hi @kaovd had you chance to test it? I'm interested if the Graph Metadata can be used as reliable source. Btw, if I can help with any part of the development, please let me know

@petr-stupka some reason git didnt notify me on the thread just seen this, will test again today

@petr-stupka It dosen't seem the endpoints actually exist - as mentioned the closest thing I got was what the portal throws back which is at  DELETE /identityGovernance/entitlementManagement/accessPackages/{id}/accessPackageResourceRoleScopes but takes a request body in the delete for some reason - even structing it perfectly though this does not work and throws and argument error.
Your welcome to experiment in graph explorer https://developer.microsoft.com/en-us/graph/graph-explorer and try to figure out if any improperly documented endpoint for it exists and go create a sample package in the portal and assign a group at a root scope - but elsewise dont see any way around this one than creating the scopes via null resource pwsh provsioner or something like that with tf output downstream, will wait for your response but if no dice then will just go ahead with current implemenation

Hi @kaovd I'm not sure how they doing it in the portal as seems like they have some logic behind. The endpoint returned from portal referenced v1 which is completely wrong - entitlementManagement is not available in v1 only in beta. So this is weird.
I tried digging into graph-explored - no success with delete operation.
Looking in our PowerShell script, we do not have the method to delete 'AccessPackagesResourceRoleScopes' we just recreate the AccessPackage
Then (until the method will be available) it can be also created is following way:

Create Catalog
Create Catalog Resources
Create AccessPackage with argument AccessPackagesResourceRoleScopes' containing array of  AccessPackagesResourceRoleScope` objects

So if someone would need to remove object from the 'AccessPackagesResourceRoleScopes' array the whole 'AccessPackage' would 'force new".
I know it is a bit limiting because of deleting 'AccessPackage' will also delete all the assignments however it can be some kind of workaround until the endpoint will be available.
Or as you said, let the 'AccessPackagesResourceRoleScopes' to be managed using portal, null_resource, or any other way until the endpoint is there - where i agree it may be the right way for now, not to complicate it at the moment and at least get the available resources into azurerm provider
Another option how to progress on it is to open issue in the graph-repo asking the guys how to perform the operation (will do it) or if the Hashicorp guys (@manicminer) have MSFT support contact (and I believe they have) to request the endpoint/information

@petr-stupka Yep opening the issue would be great thanks.
If we can force new the AP that actually works out pretty well and can be a downstream implementation. Imagine the AP Resource will have a role scopes block then separate resources for catalogs, policy and resource requests.

Just weighing in, both the portal and Azure CLI (not sure about the various pwsh modules) aren't always a great model of behavior as they hold special first-party access tokens that allow them to query undocumented endpoints. Often those endpoints are "private" or otherwise behave differently depending on whether a first-party access token or a regular token are used for authorization. This was common in the AAD Graph API and it's entirely possible the same sort of thing has been done in places with MS Graph.

@manicminer was pretty much the logic I went along but just seems the graph backend isnt there yet. Not a problem though likely to have the full IDAG flow by working around downstream with as mentioned force replacmenets where needed.

@kaovd in the meantime I've raised the question within our internal team (MVPs) if they can reach any of the MSFT product group working with MS Graph. Once I will get any feedback I will let you know.

@kaovd just quick update from MSFT. The current beta API is the latest implementation of API which has been ready to ship. The missing API endpoint for delete operation will be released in the future (without ETA)

@kaovd just quick update from MSFT. The current beta API is the latest implementation of API which has been ready to ship. The missing API endpoint for delete operation will be released in the future (without ETA)

Well suppose thats reassuring that we can just toggle 1.0 or whatever they push to when they are done. For now the way i planned it downstream should work although still few things to raise with them


static_tf: 0.0.1-1 in 'indigo/distribution.yaml' [bloom]

Increasing version of package(s) in repository static_tf to 0.0.1-1:

upstream repository: https://github.com/DLu/static_tf.git
release repository: https://github.com/wu-robotics/static_tf_release.git
distro file: indigo/distribution.yaml
bloom version: 0.5.25
previous version for package: null

bloom printed a message that in order to enable pull request testing you need to make sure that the buildfarm user has the necessary access to your repo: see https://github.com/ros-infrastructure/bloom/blob/cd86c548c9c4ae024478f49f0cd45c0c8bfeb72f/bloom/commands/release.py#L533-L536

I have updated the pull request, and the checks pass.

Consider it done.


Improve timeout situation with large files

Fixes #185
This is not the asynchronous fix, but at least on my setup it resolves the situation.

I like it. Sweet and short ;)
Approved.


bug/Malformed pptx template preventing pptx parsing

Describe the bug
Certain elements in PowerPoint templates that have no shape.top and shape.left cause the function unstructured.partition.pptx._order_shapes to fail. I have multiple files where this issue has somehow occurred. I'm not sure how to reproduce from scratch but I have attached an example file.
To Reproduce
Run:
partition_pptx(filename='fake-power-point-malformed.pptx')
With input file:
fake-power-point-malformed.pptx
Desktop (please complete the following information):

OS: windows
Python version: 3.11.4

Additional context

Issue seems to be cleared when the theme / template is changed for the source document.
Issue results in a placeholder at top left of the slide but with top and left attributes == None.

@arms3 - Thanks for reporting this! We're tracking it and will pick it up as soon as we can. Appreciate you adding the example malformed file.

@MthwRobinson I actually have a fix see PR 761

Closed by #761


fix: removes atob usage and fixes #24

Removes atob usage and fixes #24

Yeah, sorry, didn't notice. Since I saw the pnpm lock, I thought pnpm was being used. Going to fix it right now.

Fixed @gabivlj

LGTM. Thank you!


fix(license): Updating MIT license

:tada: This PR is included in version 1.0.1 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


Add directive to prettify radio buttons and checkboxes

Should this be optional? Devs don't have to add a directive to their inputs, but LESS would force the matter

It could still be a directive that is automatically attached to the radio or checkbox element...the developer would not need to code anything.  something like https://code.angularjs.org/1.2.27/docs/api/ng/directive/input

Yep. Didn't think about using it that way.

On Jun 30, 2015, at 2:19 PM, robert mcguinness<EMAIL_ADDRESS>wrote:
It could still be a directive that is automatically attached to the radio or checkbox element...the developer would not need to code anything. something like https://code.angularjs.org/1.2.27/docs/api/ng/directive/input
—
Reply to this email directly or view it on GitHub.

this is handled by CSS now


[foundation.reveal.js] replace bind(this) with local context variable

Fix compatibility issue with the use of .bind(this) and the Capybara (2.1.0) testing framework. Exceptions were encountered when using the Capybara WebKit driver or PhantomJS  Poltergeist driver.

@gakimball any update on this?

So the fix is just to make it work with Capybara, which ordinarily wouldn't concern is, but as long as it doesn't mess with any existing functionality it should be fine. Have you tested the change in multiple browsers?

Yup :D

That works for me, then! Thanks for the PR, and sorry we didn't get to it sooner. :)


Add documentation for adding Custom widgets by external contributors [Docs]:

Is there an existing issue for this?

[X] I have searched the existing issues

Documentation Link
https://discord.com/channels/725602949748752515/760761686549463060/978643283381215242
Describe the problem
As of today, it is possible for external contributors to add custom widgets, but there's no documentation for the steps they can take to do this. It would be nice to have a documented guideline for contributors to follow to achieve this.
Describe the improvement
Add guidelines, steps and best practices for Contributors to follow to add a custom widget.

Closing this issue with the link to the Appsmith Widget development ReadMe. https://github.com/appsmithorg/appsmith/blob/release/contributions/AppsmithWidgetDevelopmentGuide.md


Cow: Watch fwddigi.com

Cow requests the watch of the watch_keyword fwddigi\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

fwddigi\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Rejected by double-beep in Charcoal HQ. Reason: 'I watched this moments after the PR was opened'


Fix panics on operations on 0-capacity RingBuf

These two methods currently panic when called on a RingBuf with cap = 0 (not that that would be all that useful ;-)

Thanks!


I can't send message on android because I can't find any contact list

Hi, @madeindra
I followed your instruction and my signal server is working.
And I build the android version.
when searching contact, android app requests /v1/attestation/********** to signal server.
but signal server responds 404
and /v1/token/********, it's 404 too
I need it is the issues related to CDS and pin.
Please help me.

@pyDjangoDev First install? Rrstart the mobile app first, it's normal


DL: Make model_id naming consistent

Prior to this PR, model_id was referenced with names like
model_arch_id and model_arch_table_id. This commit ensures, that its
consistent throughout using model_id.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/madlib-pr-build/1144/


Provide get call for splitting only returns updatable parameters.

Add options on following api which returns only valid parameters for update.
/reqmgr2/data/splitting/

For this specific case, I think we should GET all splitting parameters but when one POSTs it, we should update only what's allowed.
For the record, another issue created on the same subject a week ago: https://github.com/dmwm/WMCore/issues/8453

I have a little different approach to that. Since we are getting strict about validation. I think we shouldn't ignore the some parameters blindly. If we want to be more flexible, we should at least report back which parameters won't be updated. But also, user shouldn't try to modify some parameters which is allowed to be changed.

I have a little different approach to that. Since we are getting strict about validation. I think we shouldn't ignore the some parameters blindly.

I completely agree! However, in this case we'd need to return only changeable parameters with the GET api, which might not be optimal if someone wants to check all job splitting parameters.

I completely agree! However, in this case we'd need to return only changeable parameters with the GET api, which might not be optimal if someone wants to check all job splitting parameters.

Oh, I meant add "option" to retrieve only updatable parameters. So we can add query string ?only_updatable=true. Than, returns the list of values which can be updated. Without that option behavior of get will be the same.

Approved!!! :)

Thank you, Sir. 😄


Internal Error

Type of issue: bug report
[info] [2.699] Done elaborating.
[error] (run-main-0) firrtl.FIRRTLException: Internal Error! Please file an issue at https://github.com/ucb-bar/firrtl/issues
[error] firrtl.FIRRTLException: Internal Error! Please file an issue at https://github.com/ucb-bar/firrtl/issues
[error] 	at firrtl.Utils$.error(Utils.scala:396)
[error] 	at firrtl.Utils$.throwInternalError(Utils.scala:178)
[error] 	at firrtl.Driver$$anonfun$execute$1.apply(Driver.scala:237)
[error] 	at firrtl.Driver$$anonfun$execute$1.apply(Driver.scala:209)
[error] 	at logger.Logger$$anonfun$makeScope$1.apply(Logger.scala:138)
Chisel version 3.1.5
OS: macOS
To reproduce:
git clone https://github.com/leros-dev/leros.git
checkout version 45d299a0ae0ea98bcd3308a4f1ff7445f8eceefb
run make

I found my Chisel error/mistake that triggered it:
https://github.com/leros-dev/leros/blob/45d299a0ae0ea98bcd3308a4f1ff7445f8eceefb/src/main/scala/leros/Decode.scala#L127
So it is NOT critical for me. But maybe it is worth something (or maybe already known issue).

Clarifying without running your code: this is a duplicate of https://github.com/freechipsproject/firrtl/issues/852, yes? Use of a when construct to assign to a not-fully-initialized hardware component that is later overwritten?
We should probably clarify the throwInternalError stuff (see: #974) to indicate that the originating exception is one exception down. throwInternalError is used a number of places to try and indicate something that we think really bad happened. However, it's also used to wrap any unexpected exceptions that show up during compilation. Unfortunately, this means that the first block of the stack trave provides very limited information on what happened...

As Schulyler noted, it would be useful to see the stacktrace that follows.

Should be fixed now with merging of #1039 , can you verify it fixes your issue?

Yes, I can do this. What is the procedure for this? Do I need to do a local clone from FIRRTL, build it, publish it local, and reference it how to be picked up by Chisel? Or do I also need to have a local published version of Chisel?
Or does the fix live in a SNAPSHOT on the server?
Cheers,
Martin

On 28 Feb, 2019, at 18:53, Adam Izraelevitz<EMAIL_ADDRESS>wrote:
Should be fixed now with merging of #1039 https://github.com/freechipsproject/firrtl/pull/1039 , can you verify it fixes your issue?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/freechipsproject/firrtl/issues/977#issuecomment-468371067, or mute the thread https://github.com/notifications/unsubscribe-auth/AAntmN3kA0qhS77ppC83VzKGAILDmEgpks5vSBeVgaJpZM4ZaBCf.

Retested with actual version and is fixed now.


Preprint tasks

Two new tasks:

ProteinProteinInterfaceTask: Binary classification on residues of a protein complex 1 if is in interface, 0 else. Models should be given the chains of the complex separately to not make the task trivial.
StructureSearchTask: Information retrieval task. Given a query, the relevant proteins are those with at least 0.9 similarity to the query.

I think it would be good if we translate all chains to the origin and do a random rotation in the PPI task. If you're working with a point cloud or voxel rep it's quite trivial for the model to guess the interface, even if you hand them separately.

agreed about the center+rotate, on it now.


[CPU] Add an e2e test for i4 store emulation.

Fixes https://github.com/openxla/iree/issues/15369

We probably have to disable the test on some platforms because currently we don't support vector.maskedstore emulation (https://github.com/openxla/iree/issues/15540).


openbgpd: 6.8p0 -> 7.2

Motivation for this change
Version bump. I didn't end up using the software, but 6.8p0 had a crashing bug in v6-only mode which is fixed by 7.2.

Fix typo in pname.

OPENBSD_BRANCH is gone, and I couldn't find an obvious replacement
("VERSION" is now .gitignore'd) so we can't rely on this to check
consistency. Instead, derive the fetched version from a single
variable.

We make that variable the "version" of the derivation so that bots can
figure out what to bump when a new release is out.

Things done

Built on platform(s)

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

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] 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

[x] 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/)
22.05 Release Notes (or backporting 21.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.

Did not try to build, diff looks good to me

I also prefer your approach. Since nobody seems to want to merge this PR anyway, I suggest we close this one and reopen yours. WDYT?


[Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0

Client 29744: error Error: could not find context's information in config file
at Fabric.getContext (/home/ubuntu/caliper/src/fabric/fabric.js:84:35)
at Blockchain.getContext (/home/ubuntu/caliper/src/comm/blockchain.js:87:27)
at doTest (/home/ubuntu/caliper/src/comm/client/local-client.js:164:23)
at process. (/home/ubuntu/caliper/src/comm/client/local-client.js:218:17)
at emitTwo (events.js:126:13)
at process.emit (events.js:214:7)
at emit (internal/child_process.js:772:12)
at _combinedTickCallback (internal/process/next_tick.js:141:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
(node:29744) UnhandledPromiseRejectionWarning: Error: could not find context's information in config file
at Fabric.getContext (/home/ubuntu/caliper/src/fabric/fabric.js:84:35)
at Blockchain.getContext (/home/ubuntu/caliper/src/comm/blockchain.js:87:27)
at doTest (/home/ubuntu/caliper/src/comm/client/local-client.js:164:23)
at process. (/home/ubuntu/caliper/src/comm/client/local-client.js:218:17)
at emitTwo (events.js:126:13)
at process.emit (events.js:214:7)
at emit (internal/child_process.js:772:12)
at _combinedTickCallback (internal/process/next_tick.js:141:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
(node:29744) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 3)
(node:29744) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0
[Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0
[Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0
[Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0
[Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0
[Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0
[Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0
[Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0
[Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0
[Transaction Info] - Submitted: 0 Succ: 0 Fail:0 Unfinished:0

good in Mac OS  , wrong in ubuntu

Hi Julien,
The problem is that the code can't find one of the contexts in your Fabric config file.
The error message is quite clear about this:

UnhandledPromiseRejectionWarning: Error: could not find context's information in config file
at Fabric.getContext (/home/ubuntu/caliper/src/fabric/fabric.js:84:35)

Go and check the path or the variable name of that specific context in your config file.

@Caoxuyang Thanks, I changed rounds.label from "open"n to "invoke" , but didn't change it in code

@JulienGuo NP.