shared tempdirs are not created

This happens on rocky linux 9, shared temp dirs are not created with
srun --use-shared-tmpdir --pty bash

cmake -DCMAKE_BUILD_TYPE=Release \
   -DAUTO_TMPDIR_ENABLE_SHARED_TMPDIR=On \
   -DAUTO_TMPDIR_DEFAULT_SHARED_PREFIX=/arc/scratch1/jobs \
   -DSLURM_MODULES_DIR=/usr/lib64/slurm \
   ..

in /etc/slurm/plugstack.conf
optional    auto_tmpdir.so  mount=/tmp mount=/var/tmp local_prefix=/mnt/scratch/tmpdir- shared_prefix=/arc/scratch1/slurm/job- no_rm_shared_only state_dir=/var/tmp/auto_tmpdir_cache

Have you enabled debug logging on slurmd — are there any messages logged that indicate what is failing?

It seems it never executes the code that is supposed to create the shared directory
lurmd: debug:  Log file re-opened
slurmd: debug2: hwloc_topology_init
slurmd: debug2: hwloc_topology_load
slurmd: debug2: hwloc_topology_export_xml
slurmd: debug:  CPUs:2 Boards:1 Sockets:2 CoresPerSocket:1 ThreadsPerCore:1
slurmd: debug4: CPU map[0]=>0 S:C:T 0:0:0
slurmd: debug4: CPU map[1]=>1 S:C:T 1:0:0
slurmd: debug:  CPUs has been set to match cores per node instead of threads CPUs=1:2(hw)
slurmd: error: Node configuration differs from hardware: CPUs=1:2(hw) Boards=1:1(hw) SocketsPerBoard=1:2(hw) CoresPerSocket=1:1(hw) ThreadsPerCore=1:1(hw)
slurmd: debug3: Trying to load plugin /usr/lib64/slurm/cgroup_v2.so
slurmd: debug3: plugin_load_from_file->_verify_syms: found Slurm plugin name:Cgroup v2 plugin type:cgroup/v2 version:0x170b0a
slurmd: debug:  cgroup/v2: init: Cgroup v2 plugin loaded
slurmd: debug3: Success.
slurmd: debug3: _set_slurmd_spooldir: initializing slurmd spool directory `/var/spool/slurmd`
slurmd: debug2: hwloc_topology_init
slurmd: debug2: xcpuinfo_hwloc_topo_load: xml file (/var/spool/slurmd/hwloc_topo_whole.xml) found
slurmd: debug:  CPUs:2 Boards:1 Sockets:2 CoresPerSocket:1 ThreadsPerCore:1
slurmd: debug4: CPU map[0]=>0 S:C:T 0:0:0
slurmd: debug4: CPU map[1]=>1 S:C:T 1:0:0
slurmd: debug3: _pack_context_buf: No GRES context count sent to stepd
slurmd: debug3: Trying to load plugin /usr/lib64/slurm/topology_default.so
slurmd: debug3: plugin_load_from_file->_verify_syms: found Slurm plugin name:topology Default plugin type:topology/default version:0x170b0a
slurmd: topology/default: init: topology Default plugin loaded
slurmd: debug3: Success.
slurmd: CPU frequency setting not configured for this node
slurmd: debug:  Resource spec: No specialized cores configured by default on this node
slurmd: debug:  Resource spec: Reserved system memory limit not configured for this node
slurmd: debug3: NodeName    = localhost
slurmd: debug3: TopoAddr    = localhost
slurmd: debug3: TopoPattern = node
slurmd: debug3: ClusterName = cluster
slurmd: debug3: Confile     = `/etc/slurm/slurm.conf'
slurmd: debug3: Debug       = 3
slurmd: debug3: CPUs        = 1  (CF:  1, HW:  2)
slurmd: debug3: Boards      = 1  (CF:  1, HW:  1)
slurmd: debug3: Sockets     = 1  (CF:  1, HW:  2)
slurmd: debug3: Cores       = 1  (CF:  1, HW:  1)
slurmd: debug3: Threads     = 1  (CF:  1, HW:  1)
slurmd: debug3: UpTime      = 52699 = 14:38:19
slurmd: debug3: Block Map   = 0,1
slurmd: debug3: Inverse Map = 0,1
slurmd: debug3: ConfMemory  = 1
slurmd: debug3: PhysicalMem = 7495
slurmd: debug3: TmpDisk     = 203683
slurmd: debug3: Epilog      = `(null)'
slurmd: debug3: Logfile     = `/var/log/slurmd.log'
slurmd: debug3: HealthCheck = `(null)'
slurmd: debug3: NodeName    = localhost
slurmd: debug3: Port        = 6818
slurmd: debug3: Prolog      = `(null)'
slurmd: debug3: TmpFS       = `/tmp'
slurmd: debug3: Slurmstepd  = `/usr/sbin/slurmstepd'
slurmd: debug3: Spool Dir   = `/var/spool/slurmd'
slurmd: debug3: Syslog Debug  = 10
slurmd: debug3: Pid File    = `/var/run/slurmd.pid'
slurmd: debug3: Slurm UID   = 5829
slurmd: debug3: TaskProlog  = `(null)'
slurmd: debug3: TaskEpilog  = `(null)'
slurmd: debug3: TaskPluginParam = 0
slurmd: debug3: UsePAM      = 0
slurmd: debug3: Trying to load plugin /usr/lib64/slurm/proctrack_cgroup.so
slurmd: debug3: plugin_load_from_file->_verify_syms: found Slurm plugin name:Process tracking via linux cgroup freezer subsystem type:proctrack/cgroup version:0x170b0a
slurmd: debug3: Success.
slurmd: debug3: Trying to load plugin /usr/lib64/slurm/task_affinity.so
slurmd: debug3: plugin_load_from_file->_verify_syms: found Slurm plugin name:task affinity plugin type:task/affinity version:0x170b0a
slurmd: debug3: task/affinity: slurm_getaffinity: sched_getaffinity(0) = 0x3
slurmd: task/affinity: init: task affinity plugin loaded with CPU mask 0x3
slurmd: debug3: Success.
slurmd: debug:  spank: opening plugin stack /etc/slurm/plugstack.conf
slurmd: debug3: plugin_peek->_verify_syms: found Slurm plugin name:auto_tmpdir type:spank version:0x170b0a
slurmd: debug3: plugin_load_from_file->_verify_syms: found Slurm plugin name:auto_tmpdir type:spank version:0x170b0a
slurmd: debug3: Couldn't find sym 'slurm_spank_local_user_init' in the plugin
slurmd: debug3: Couldn't find sym 'slurm_spank_user_init' in the plugin
slurmd: debug3: Couldn't find sym 'slurm_spank_task_init_privileged' in the plugin
slurmd: debug3: Couldn't find sym 'slurm_spank_task_init' in the plugin
slurmd: debug3: Couldn't find sym 'slurm_spank_task_post_fork' in the plugin
slurmd: debug3: Couldn't find sym 'slurm_spank_task_exit' in the plugin
slurmd: debug3: Couldn't find sym 'slurm_spank_slurmd_exit' in the plugin
slurmd: debug3: Couldn't find sym 'slurm_spank_exit' in the plugin
slurmd: debug:  spank: /etc/slurm/plugstack.conf:1: Loaded plugin auto_tmpdir.so
slurmd: debug:  SPANK: appending plugin option "no-rm-tmpdir"
slurmd: debug:  SPANK: appending plugin option "use-shared-tmpdir"
slurmd: debug2: spank: auto_tmpdir.so: init = 0
slurmd: debug3: Trying to load plugin /usr/lib64/slurm/cred_munge.so
slurmd: debug3: plugin_load_from_file->_verify_syms: found Slurm plugin name:Munge credential signature plugin type:cred/munge version:0x170b0a
slurmd: cred/munge: init: Munge credential signature plugin loaded
slurmd: debug3: Success.
slurmd: debug4: xsignal: Swap signal TERM[15] to 0x40cee3 from 0x0
slurmd: debug4: xsignal: Swap signal INT[2] to 0x40cee3 from 0x0
slurmd: debug4: xsignal: Swap signal HUP[1] to 0x40bc56 from 0x0
slurmd: debug4: xsignal: Swap signal USR2[12] to 0x40bc6c from 0x0
slurmd: debug3: slurmd initialization successful
slurmd: slurmd version 23.11.10 started
slurmd: debug3: finished daemonize
slurmd: debug3: create_mmap_buf: loaded file `/var/spool/slurmd/cred_state` as buf_t
slurmd: debug3: cred_unpack: job 103 ctime:1725380631 revoked:1725380631 expires:1725380751
slurmd: debug2: No acct_gather.conf file (/etc/slurm/acct_gather.conf)
slurmd: debug3: Trying to load plugin /usr/lib64/slurm/prep_script.so
slurmd: debug3: plugin_load_from_file->_verify_syms: found Slurm plugin name:Script PrEp plugin type:prep/script version:0x170b0a
slurmd: debug3: Success.
slurmd: debug:  MPI: Loading all types
slurmd: debug3: Trying to load plugin /usr/lib64/slurm/mpi_cray_shasta.so
slurmd: debug3: plugin_load_from_file->_verify_syms: found Slurm plugin name:mpi Cray Shasta plugin type:mpi/cray_shasta version:0x170b0a
slurmd: debug3: Success.
slurmd: debug3: Trying to load plugin /usr/lib64/slurm/mpi_pmi2.so
slurmd: debug3: plugin_load_from_file->_verify_syms: found Slurm plugin name:mpi PMI2 plugin type:mpi/pmi2 version:0x170b0a
slurmd: debug3: Success.
slurmd: debug2: No mpi.conf file (/etc/slurm/mpi.conf)
slurmd: debug3: Successfully opened slurm listen port 6818
slurmd: slurmd started on Tue, 03 Sep 2024 09:26:51 -0700
slurmd: CPUs=1 Boards=1 Sockets=1 Cores=1 Threads=1 Memory=7495 TmpDisk=203683 Uptime=52699 CPUSpecList=(null) FeaturesAvail=(null) FeaturesActive=(null)
slurmd: debug4: xsignal: Swap signal ALRM[14] to 0x0 from 0x0
slurmd: debug4: xsignal: Swap signal ALRM[14] to 0x0 from 0x0
slurmd: debug4: xsignal: Swap signal PIPE[13] to 0x1 from 0x0
slurmd: debug4: xsignal: Swap signal PIPE[13] to 0x0 from 0x1
slurmd: debug:  _handle_node_reg_resp: slurmctld sent back 8 TRES.
slurmd: debug3: _registration_engine complete
slurmd: debug3: in the service_connection
slurmd: debug2: Start processing RPC: REQUEST_BATCH_JOB_LAUNCH
slurmd: debug2: Processing RPC: REQUEST_BATCH_JOB_LAUNCH
slurmd: task/affinity: task_p_slurmd_batch_request: task_p_slurmd_batch_request: 104
slurmd: debug3: task/affinity: _get_avail_map: slurmctld s 1 c 1; hw s 2 c 1 t 1
slurmd: debug3: task/affinity: _get_avail_map: StepId=104.batch core mask from slurmctld: 0x1
slurmd: debug3: task/affinity: _get_avail_map: StepId=104.batch CPU final mask for local node: 0x1
slurmd: task/affinity: batch_bind: job 104 CPU input mask for node: 0x1
slurmd: debug3: task/affinity: _lllp_map_abstract_masks: _lllp_map_abstract_masks
slurmd: task/affinity: batch_bind: job 104 CPU final HW mask for node: 0x1
slurmd: debug4: xsignal: Swap signal PIPE[13] to 0x1 from 0x0
slurmd: debug4: xsignal: Swap signal PIPE[13] to 0x0 from 0x1
slurmd: debug:  prep/script: _run_spank_job_script: _run_spank_job_script: calling /usr/sbin/slurmstepd spank prolog
spank-prolog: debug2: debug level read from slurmd is 'unknown'.
spank-prolog: debug2: _read_slurmd_conf_lite: slurmd sent 8 TRES.
spank-prolog: debug:  Running spank/prolog for jobid [104] uid [1000] gid [1000]
spank-prolog: debug:  spank: opening plugin stack /etc/slurm/plugstack.conf
spank-prolog: debug3: plugin_peek->_verify_syms: found Slurm plugin name:auto_tmpdir type:spank version:0x170b0a
spank-prolog: debug3: plugin_load_from_file->_verify_syms: found Slurm plugin name:auto_tmpdir type:spank version:0x170b0a
spank-prolog: debug3: Couldn't find sym 'slurm_spank_local_user_init' in the plugin
spank-prolog: debug3: Couldn't find sym 'slurm_spank_user_init' in the plugin
spank-prolog: debug3: Couldn't find sym 'slurm_spank_task_init_privileged' in the plugin
spank-prolog: debug3: Couldn't find sym 'slurm_spank_task_init' in the plugin
spank-prolog: debug3: Couldn't find sym 'slurm_spank_task_post_fork' in the plugin
spank-prolog: debug3: Couldn't find sym 'slurm_spank_task_exit' in the plugin
spank-prolog: debug3: Couldn't find sym 'slurm_spank_slurmd_exit' in the plugin
spank-prolog: debug3: Couldn't find sym 'slurm_spank_exit' in the plugin
spank-prolog: debug:  spank: /etc/slurm/plugstack.conf:1: Loaded plugin auto_tmpdir.so
spank-prolog: debug:  SPANK: appending plugin option "no-rm-tmpdir"
spank-prolog: debug:  SPANK: appending plugin option "use-shared-tmpdir"
spank-prolog: debug:  auto_tmpdir::auto_tmpdir_fs_init: 104 for owner 1000:1000
spank-prolog: debug:  auto_tmpdir::auto_tmpdir_fs_init: no_rm_shared_only set, ensuring no should_not_delete bit in options
spank-prolog: debug:  auto_tmpdir::auto_tmpdir_fs_init: local_prefix=/mnt/scratch/tmpdir-
spank-prolog: debug:  auto_tmpdir::auto_tmpdir_fs_init: shared_prefix=/arc/scratch1/jobs/job-
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: created directory `/mnt/scratch/tmpdir-104/tmp`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: set ownership 1000:1000 on directory `/mnt/scratch/tmpdir-104/tmp`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: added bindpoint `/mnt/scratch/tmpdir-104/tmp` -> `/tmp`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: created directory `/mnt/scratch/tmpdir-104/var_tmp`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: set ownership 1000:1000 on directory `/mnt/scratch/tmpdir-104/var_tmp`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: added bindpoint `/mnt/scratch/tmpdir-104/var_tmp` -> `/var/tmp`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: created directory `/dev/shm/slurm-104`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: set ownership 1000:1000 on directory `/dev/shm/slurm-104`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: added bindpoint `/dev/shm/slurm-104` -> `/dev/shm`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_default_state_file: 104
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_default_state_file: state_dir=/var/tmp/auto_tmpdir_cache
spank-prolog: debug:  auto_tmpdir::auto_tmpdir_fs_serialize_to_file: serialized to `/var/tmp/auto_tmpdir_cache/auto_tmpdir_fs-104.cache`
spank-prolog: debug2: spank: auto_tmpdir.so: job_prolog = 0
slurmd: debug:  unsetenv (SPANK__SLURM_SPANK_OPTION_auto_tmpdir_use_shared_tmpdir)
slurmd: Launching batch job 104 for UID 1000
slurmd: debug3: _rpc_batch_job: call to _forkexec_slurmstepd
slurmd: debug3: slurmstepd rank -1 (localhost), parent rank -1 (NONE), children 0, depth 0, max_depth 0
slurmd: debug3: _rpc_batch_job: return from _forkexec_slurmstepd: 0
slurmd: debug2: Finish processing RPC: REQUEST_BATCH_JOB_LAUNCH
slurmd: debug3: in the service_connection
slurmd: debug2: Start processing RPC: REQUEST_TERMINATE_JOB
slurmd: debug2: Processing RPC: REQUEST_TERMINATE_JOB
slurmd: debug:  _rpc_terminate_job: uid = 5829 JobId=104
slurmd: debug:  credential for job 104 revoked
slurmd: debug2: No steps in jobid 104 to send signal 18
slurmd: debug2: No steps in jobid 104 to send signal 15
slurmd: debug4: sent SUCCESS
slurmd: debug4: xsignal: Swap signal PIPE[13] to 0x1 from 0x0
slurmd: debug4: xsignal: Swap signal PIPE[13] to 0x0 from 0x1
slurmd: debug2: set revoke expiration for jobid 104 to<PHONE_NUMBER> UTS
slurmd: debug:  Waiting for job 104's prolog to complete
slurmd: debug:  Finished wait for job 104's prolog to complete
slurmd: debug:  prep/script: _run_spank_job_script: _run_spank_job_script: calling /usr/sbin/slurmstepd spank epilog
spank-epilog: debug2: debug level read from slurmd is 'unknown'.
spank-epilog: debug2: _read_slurmd_conf_lite: slurmd sent 8 TRES.
spank-epilog: debug:  Running spank/epilog for jobid [104] uid [1000] gid [1000]
spank-epilog: debug:  spank: opening plugin stack /etc/slurm/plugstack.conf
spank-epilog: debug3: plugin_peek->_verify_syms: found Slurm plugin name:auto_tmpdir type:spank version:0x170b0a
spank-epilog: debug3: plugin_load_from_file->_verify_syms: found Slurm plugin name:auto_tmpdir type:spank version:0x170b0a
spank-epilog: debug3: Couldn't find sym 'slurm_spank_local_user_init' in the plugin
spank-epilog: debug3: Couldn't find sym 'slurm_spank_user_init' in the plugin
spank-epilog: debug3: Couldn't find sym 'slurm_spank_task_init_privileged' in the plugin
spank-epilog: debug3: Couldn't find sym 'slurm_spank_task_init' in the plugin
spank-epilog: debug3: Couldn't find sym 'slurm_spank_task_post_fork' in the plugin
spank-epilog: debug3: Couldn't find sym 'slurm_spank_task_exit' in the plugin
spank-epilog: debug3: Couldn't find sym 'slurm_spank_slurmd_exit' in the plugin
spank-epilog: debug3: Couldn't find sym 'slurm_spank_exit' in the plugin
spank-epilog: debug:  spank: /etc/slurm/plugstack.conf:1: Loaded plugin auto_tmpdir.so
spank-epilog: debug:  SPANK: appending plugin option "no-rm-tmpdir"
spank-epilog: debug:  SPANK: appending plugin option "use-shared-tmpdir"
spank-epilog: debug:  auto_tmpdir::__auto_tmpdir_fs_default_state_file: 104
spank-epilog: debug:  auto_tmpdir::__auto_tmpdir_fs_default_state_file: state_dir=/var/tmp/auto_tmpdir_cache
spank-epilog: debug:  auto_tmpdir::auto_tmpdir_fs_bindpoint_dealloc: `/dev/shm/slurm-104` -> `/dev/shm` (0|1) 0x1e90430
spank-epilog: debug:  auto_tmpdir::auto_tmpdir_fs_bindpoint_dealloc: removing directory `/dev/shm/slurm-104`
spank-epilog: debug:  auto_tmpdir::auto_tmpdir_fs_bindpoint_dealloc: moving to next directory 0x1e90430
spank-epilog: debug:  auto_tmpdir::auto_tmpdir_fs_bindpoint_dealloc: `/mnt/scratch/tmpdir-104/tmp` -> `/tmp` (0|0) 0x1e90400
spank-epilog: debug:  auto_tmpdir::auto_tmpdir_fs_bindpoint_dealloc: removing directory `/mnt/scratch/tmpdir-104/tmp`
spank-epilog: debug:  auto_tmpdir::auto_tmpdir_fs_bindpoint_dealloc: moving to next directory 0x1e90400
spank-epilog: debug:  auto_tmpdir::auto_tmpdir_fs_bindpoint_dealloc: `/mnt/scratch/tmpdir-104/var_tmp` -> `/var/tmp` (0|0) (nil)
spank-epilog: debug:  auto_tmpdir::auto_tmpdir_fs_bindpoint_dealloc: removing directory `/mnt/scratch/tmpdir-104/var_tmp`
spank-epilog: debug:  auto_tmpdir::auto_tmpdir_fs_bindpoint_dealloc: moving to next directory (nil)
spank-epilog: debug:  auto_tmpdir::auto_tmpdir_fs_bindpoint_dealloc: removing directory `/mnt/scratch/tmpdir-104`
spank-epilog: debug2: spank: auto_tmpdir.so: job_epilog = 0
slurmd: debug:  unsetenv (SPANK__SLURM_SPANK_OPTION_auto_tmpdir_use_shared_tmpdir)
slurmd: debug:  completed epilog for jobid 104
slurmd: debug4: xsignal: Swap signal ALRM[14] to 0x0 from 0x0
slurmd: debug4: xsignal: Swap signal ALRM[14] to 0x0 from 0x0
slurmd: debug4: xsignal: Swap signal PIPE[13] to 0x1 from 0x0
slurmd: debug4: xsignal: Swap signal PIPE[13] to 0x0 from 0x1
slurmd: debug:  JobId=104: sent epilog complete msg: rc = 0
slurmd: debug2: Finish processing RPC: REQUEST_TERMINATE_JOB

It definitely does execute — when the job is started there are prolog lines citing "auto_tmpdir":
spank-prolog: debug:  spank: /etc/slurm/plugstack.conf:1: Loaded plugin auto_tmpdir.so
spank-prolog: debug:  SPANK: appending plugin option "no-rm-tmpdir"
spank-prolog: debug:  SPANK: appending plugin option "use-shared-tmpdir"
spank-prolog: debug:  auto_tmpdir::auto_tmpdir_fs_init: 104 for owner 1000:1000
spank-prolog: debug:  auto_tmpdir::auto_tmpdir_fs_init: no_rm_shared_only set, ensuring no should_not_delete bit in options
spank-prolog: debug:  auto_tmpdir::auto_tmpdir_fs_init: local_prefix=/mnt/scratch/tmpdir-
spank-prolog: debug:  auto_tmpdir::auto_tmpdir_fs_init: shared_prefix=/arc/scratch1/jobs/job-
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: created directory `/mnt/scratch/tmpdir-104/tmp`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: set ownership 1000:1000 on directory `/mnt/scratch/tmpdir-104/tmp`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: added bindpoint `/mnt/scratch/tmpdir-104/tmp` -> `/tmp`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: created directory `/mnt/scratch/tmpdir-104/var_tmp`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: set ownership 1000:1000 on directory `/mnt/scratch/tmpdir-104/var_tmp`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: added bindpoint `/mnt/scratch/tmpdir-104/var_tmp` -> `/var/tmp`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: created directory `/dev/shm/slurm-104`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: set ownership 1000:1000 on directory `/dev/shm/slurm-104`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: added bindpoint `/dev/shm/slurm-104` -> `/dev/shm`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_default_state_file: 104
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_default_state_file: state_dir=/var/tmp/auto_tmpdir_cache
spank-prolog: debug:  auto_tmpdir::auto_tmpdir_fs_serialize_to_file: serialized to `/var/tmp/auto_tmpdir_cache/auto_tmpdir_fs-104.cache`
spank-prolog: debug2: spank: auto_tmpdir.so: job_prolog = 0

There are similar epilog lines in your cited log, too.  How are you determining that the plugin is not creating the necessary directories?

But the auto_tmpdir plugin definitely is executing when the job starts and ends, your log shows that.  Note in your log that the local_prefix is being used, not the shared_prefix, so clearly there will be no directories created in /arc/scratch1/jobs.  So why is the shared prefix not being used for your job — if you add -v to your sbatch/salloc, does the plugin display any information?

Yes, it works well for all local temp.  I just get this with -vvvvvv . /arc/scratch1/jobs is also a local folder owned by the slurm user. .....or are you saying that if I have configured both  local_prefix=/mnt/scratch/tmpdir- and shared_prefix=/arc/scratch1/slurm/job- in plugstack.conf that it will never work ?
[rocky@dirk1 ~]$ sbatch -vvvvvvvvvvvvvv --use-shared-tmpdir --wrap="hostname"
sbatch: auto_tmpdir:  will use shared tempororary directory under `/arc/scratch1/jobs`
sbatch: defined options
sbatch: -------------------- --------------------
sbatch: verbose             : 14
sbatch: wrap                : hostname
sbatch: -------------------- --------------------
sbatch: end of defined options
sbatch: debug2: spank: auto_tmpdir.so: init_post_opt = 0
sbatch: debug:  propagating RLIMIT_CPU=18446744073709551615
sbatch: debug:  propagating RLIMIT_FSIZE=18446744073709551615
sbatch: debug:  propagating RLIMIT_DATA=18446744073709551615
sbatch: debug:  propagating RLIMIT_STACK=8388608
sbatch: debug:  propagating RLIMIT_CORE=0
sbatch: debug:  propagating RLIMIT_RSS=18446744073709551615
sbatch: debug:  propagating RLIMIT_NPROC=29700
sbatch: debug:  propagating RLIMIT_NOFILE=1024
sbatch: debug:  propagating RLIMIT_MEMLOCK=8388608
sbatch: debug:  propagating RLIMIT_AS=18446744073709551615
sbatch: debug:  propagating SLURM_PRIO_PROCESS=0
sbatch: debug:  propagating UMASK=0022
sbatch: debug4: xsignal: Swap signal ALRM[14] to 0x0 from 0x0
sbatch: debug4: xsignal: Swap signal ALRM[14] to 0x0 from 0x0
sbatch: debug4: xsignal: Swap signal PIPE[13] to 0x1 from 0x0
sbatch: debug4: xsignal: Swap signal PIPE[13] to 0x0 from 0x1
Submitted batch job 107

there is a little more on an interactive session:
[rocky@dirk1 ~]$ srun -vvvvvvvvvv --use-shared-tmpdir --pty bash
srun: defined options
srun: -------------------- --------------------
srun: pty                 :
srun: verbose             : 10
srun: -------------------- --------------------
srun: end of defined options
srun: debug:  propagating RLIMIT_CPU=18446744073709551615
srun: debug:  propagating RLIMIT_FSIZE=18446744073709551615
srun: debug:  propagating RLIMIT_DATA=18446744073709551615
srun: debug:  propagating RLIMIT_STACK=8388608
srun: debug:  propagating RLIMIT_CORE=0
srun: debug:  propagating RLIMIT_RSS=18446744073709551615
srun: debug:  propagating RLIMIT_NPROC=29700
srun: debug:  propagating RLIMIT_NOFILE=1024
srun: debug:  propagating RLIMIT_MEMLOCK=8388608
srun: debug:  propagating RLIMIT_AS=18446744073709551615
srun: debug:  propagating SLURM_PRIO_PROCESS=0
srun: debug:  propagating UMASK=0022
srun: debug:  Entering slurm_allocation_msg_thr_create()
srun: debug:  port from net_stream_listen is 42175
srun: debug:  Entering _msg_thr_internal
srun: debug4: eio: handling events for 1 objects
srun: debug3: eio_message_socket_readable: shutdown 0 fd 3
srun: debug4: xsignal: Swap signal INT[2] to 0x4097ff from 0x0
srun: debug4: xsignal: Swap signal QUIT[3] to 0x4097ff from 0x0
srun: debug4: xsignal: Swap signal CONT[18] to 0x4097ff from 0x0
srun: debug4: xsignal: Swap signal TERM[15] to 0x4097ff from 0x0
srun: debug4: xsignal: Swap signal HUP[1] to 0x4097ff from 0x0
srun: debug4: xsignal: Swap signal ALRM[14] to 0x4097ff from 0x0
srun: debug4: xsignal: Swap signal USR1[10] to 0x4097ff from 0x0
srun: debug4: xsignal: Swap signal USR2[12] to 0x4097ff from 0x0
srun: debug4: xsignal: Swap signal PIPE[13] to 0x4097ff from 0x0
srun: debug4: xsignal: Swap signal ALRM[14] to 0x0 from 0x4097ff
srun: debug4: xsignal: Swap signal ALRM[14] to 0x4097ff from 0x0
srun: debug4: xsignal: Swap signal PIPE[13] to 0x1 from 0x4097ff
srun: debug4: xsignal: Swap signal PIPE[13] to 0x4097ff from 0x1
srun: debug4: xsignal: Swap signal ALRM[14] to 0x0 from 0x4097ff
srun: debug4: xsignal: Swap signal ALRM[14] to 0x4097ff from 0x0
srun: debug4: xsignal: Swap signal PIPE[13] to 0x1 from 0x4097ff
srun: debug4: xsignal: Swap signal PIPE[13] to 0x4097ff from 0x1
srun: Nodes localhost are ready for job
srun: jobid 110: nodes(1):`localhost', cpu counts: 1(x1)
srun: debug2: creating job with 1 tasks
srun: debug2: cpu:1 is not a gres
srun: debug:  requesting job 110, user 99, nodes 1 including ((null))
srun: debug:  cpus 1, tasks 1, name bash, relative 65534
srun: debug4: xsignal: Swap signal ALRM[14] to 0x0 from 0x4097ff
srun: debug4: xsignal: Swap signal ALRM[14] to 0x4097ff from 0x0
srun: debug4: xsignal: Swap signal PIPE[13] to 0x1 from 0x4097ff
srun: debug4: xsignal: Swap signal PIPE[13] to 0x4097ff from 0x1
srun: debug2: winsize 45:240
srun: debug2: initialized job control port 40911
                                                srun: debug4: xsignal: Swap signal 28[28] to 0x4174ab from 0x0
                                                                                srun: CpuBindType=(null type)
srun: debug:  Entering slurm_step_launch
srun: debug:  Entering _msg_thr_create()
srun: debug4: eio: handling events for 2 objects
srun: debug3: eio_message_socket_readable: shutdown 0 fd 12
srun: debug3: eio_message_socket_readable: shutdown 0 fd 6
srun: debug:  initialized stdio listening socket, port 36201
srun: debug4: xsignal: Swap signal TTIN[21] to 0x1 from 0x0
srun: debug:  Started IO server thread
srun: debug3: IO thread pid = 23851
srun: debug4: eio: handling events for 4 objects
srun: debug2: Called _file_readable
srun: debug3:   false, all ioservers not yet initialized
srun: debug2: Called _file_writable
srun: debug3:   false
srun: debug3:   eof is false
srun: debug:  Entering _launch_tasks
srun: launching StepId=110.0 on host localhost, 1 tasks: 0
srun: debug2: Called _file_writable
srun: debug3:   false
srun: debug3:   eof is false
srun: debug3: Called _listening_socket_readable
srun: debug3: Trying to load plugin /usr/lib64/slurm/topology_default.so
srun: debug3: plugin_load_from_file->_verify_syms: found Slurm plugin name:topology Default plugin type:topology/default version:0x170b0a
srun: topology/default: init: topology Default plugin loaded
srun: debug3: Success.
srun: debug2: Tree head got back 0 looking for 1
srun: debug3: Tree sending to localhost
srun: debug4: xsignal: Swap signal ALRM[14] to 0x0 from 0x4097ff
srun: debug4: xsignal: Swap signal ALRM[14] to 0x4097ff from 0x0
srun: debug4: xsignal: Swap signal PIPE[13] to 0x1 from 0x4097ff
srun: debug4: xsignal: Swap signal PIPE[13] to 0x4097ff from 0x1
srun: debug2: Tree head got back 1
srun: debug:  launch returned msg_rc=0 err=0 type=8001
srun: debug2: waiting for SIGWINCH
srun: debug3: Called _listening_socket_read
srun: debug2: Activity on IO listening socket 15
srun: debug3: Accepted IO connection: ip=<IP_ADDRESS>:34200 sd=16
srun: debug2: Entering io_init_msg_read_from_fd
srun: debug2: Leaving io_init_msg_read_from_fd
srun: debug2: Entering io_init_msg_validate
srun: debug3:   msg->version = 2800
srun: debug3:   msg->nodeid = 0
srun: debug2: Leaving io_init_msg_validate
srun: debug2: Validated IO connection from <IP_ADDRESS>:34200, node rank 0, sd=16
srun: debug3: msg.stdout_objs = 1
srun: debug3: msg.stderr_objs = 0
srun: debug3: eio_message_socket_accept: start
srun: debug2: eio_message_socket_accept: got message connection from <IP_ADDRESS>:60128 17
srun: debug2: received task launch
srun: Node localhost, 1 tasks started
srun: debug3: task_state_update: StepId=110.0 task_id=0, TS_START_SUCCESS
srun: debug4: xsignal: Swap signal PIPE[13] to 0x1 from 0x4097ff
srun: debug4: xsignal: Swap signal PIPE[13] to 0x4097ff from 0x1
srun: debug4: eio: handling events for 2 objects
srun: debug3: eio_message_socket_readable: shutdown 0 fd 12
srun: debug3: eio_message_socket_readable: shutdown 0 fd 6
srun: debug4: eio: handling events for 5 objects
srun: debug2: Called _file_readable
srun: debug2: Called _file_writable
srun: debug3:   false
srun: debug3:   eof is false
srun: debug2: Called _file_writable
srun: debug3:   false
srun: debug3:   eof is false
srun: debug3: Called _listening_socket_readable
srun: debug4: Called _server_writable
srun: debug4:   false
srun: debug4: Called _server_readable
srun: debug4: remote_stdout_objs = 1
srun: debug4: remote_stderr_objs = 0
srun: debug4: Entering _server_read
srun: debug3: Entering io_hdr_read_fd
srun: debug3: Leaving io_hdr_read_fd
srun: debug4: eio: handling events for 5 objects
srun: debug2: Called _file_readable
srun: debug2: Called _file_writable
srun: debug2: Called _file_writable
srun: debug3:   false
srun: debug3:   eof is false
srun: debug3: Called _listening_socket_readable
srun: debug4: Called _server_writable
srun: debug4:   false
srun: debug4: Called _server_readable
srun: debug4: remote_stdout_objs = 1
srun: debug4: remote_stderr_objs = 0
srun: debug2: Entering _file_write
srun: debug3:   wrote 18 bytes
srun: debug2: Leaving  _file_write
srun: debug4: eio: handling events for 5 objects
srun: debug2: Called _file_readable
srun: debug2: Called _file_writable
srun: debug3:   false
srun: debug3:   eof is false
srun: debug2: Called _file_writable
srun: debug3:   false
srun: debug3:   eof is false
srun: debug3: Called _listening_socket_readable
srun: debug4: Called _server_writable
srun: debug4:   false
srun: debug4: Called _server_readable
srun: debug4: remote_stdout_objs = 1
srun: debug4: remote_stderr_objs = 0
srun: debug4: Entering _server_read
srun: debug3: Entering io_hdr_read_fd
srun: debug3: Leaving io_hdr_read_fd
srun: debug4: eio: handling events for 5 objects
srun: debug2: Called _file_readable
srun: debug2: Called _file_writable
srun: debug2: Called _file_writable
srun: debug3:   false
srun: debug3:   eof is false
srun: debug3: Called _listening_socket_readable
srun: debug4: Called _server_writable
srun: debug4:   false
srun: debug4: Called _server_readable
srun: debug4: remote_stdout_objs = 1
srun: debug4: remote_stderr_objs = 0
srun: debug2: Entering _file_write
srun: debug3:   wrote 8 bytes
srun: debug2: Leaving  _file_write
srun: debug4: eio: handling events for 5 objects
srun: debug2: Called _file_readable
srun: debug2: Called _file_writable
srun: debug3:   false
srun: debug3:   eof is false
srun: debug2: Called _file_writable
srun: debug3:   false
srun: debug3:   eof is false
srun: debug3: Called _listening_socket_readable
srun: debug4: Called _server_writable
srun: debug4:   false
srun: debug4: Called _server_readable
srun: debug4: remote_stdout_objs = 1
srun: debug4: remote_stderr_objs = 0
srun: debug4: Entering _server_read
srun: debug3: Entering io_hdr_read_fd
srun: debug3: Leaving io_hdr_read_fd
srun: debug4: eio: handling events for 5 objects
srun: debug2: Called _file_readable
srun: debug2: Called _file_writable
srun: debug2: Called _file_writable
srun: debug3:   false
srun: debug3:   eof is false
srun: debug3: Called _listening_socket_readable
srun: debug4: Called _server_writable
srun: debug4:   false
srun: debug4: Called _server_readable
srun: debug4: remote_stdout_objs = 1
srun: debug4: remote_stderr_objs = 0
srun: debug2: Entering _file_write
[rocky@dirk1 ~]$ srun: debug3:   wrote 17 bytes
srun: debug2: Leaving  _file_write
srun: debug4: eio: handling events for 5 objects
srun: debug2: Called _file_readable
srun: debug2: Called _file_writable
srun: debug3:   false
srun: debug3:   eof is false
srun: debug2: Called _file_writable
srun: debug3:   false
srun: debug3:   eof is false
srun: debug3: Called _listening_socket_readable
srun: debug4: Called _server_writable

I can confirm that it does not work on our system, either (Slurm 20.11.5).  The problem is w.r.t. getting the SPANK prolog/epilog steps able to "see" the CLI options that were presented to sbatch/salloc.
I made a new branch with modifications meant to fixup the CLI option handling in the prolog/epilog contexts.  Please give the new branch a try.

I tried the new code but it does not seem to make a difference:
cmake -DCMAKE_BUILD_TYPE=Release
 -DSLURM_MODULES_DIR=/usr/lib64/slurm
 -DAUTO_TMPDIR_ENABLE_SHARED_TMPDIR=On
 -DAUTO_TMPDIR_DEFAULT_SHARED_PREFIX=/arc/scratch1/jobs
  ..

[rocky@dirk1 ~]$ sbatch -vvvvvvvvvvvvvv --use-shared-tmpdir --wrap="hostname"
sbatch: auto_tmpdir:  will use shared tempororary directory under `/arc/scratch1/jobs`
sbatch: defined options
sbatch: -------------------- --------------------
sbatch: verbose             : 14
sbatch: wrap                : hostname
sbatch: -------------------- --------------------
sbatch: end of defined options
sbatch: debug2: spank: auto_tmpdir.so: init_post_opt = 0
sbatch: debug:  propagating RLIMIT_CPU=18446744073709551615
sbatch: debug:  propagating RLIMIT_FSIZE=18446744073709551615
sbatch: debug:  propagating RLIMIT_DATA=18446744073709551615
sbatch: debug:  propagating RLIMIT_STACK=8388608
sbatch: debug:  propagating RLIMIT_CORE=0
sbatch: debug:  propagating RLIMIT_RSS=18446744073709551615
sbatch: debug:  propagating RLIMIT_NPROC=29700
sbatch: debug:  propagating RLIMIT_NOFILE=1024
sbatch: debug:  propagating RLIMIT_MEMLOCK=8388608
sbatch: debug:  propagating RLIMIT_AS=18446744073709551615
sbatch: debug:  propagating SLURM_PRIO_PROCESS=0
sbatch: debug:  propagating UMASK=0022
sbatch: debug4: xsignal: Swap signal ALRM[14] to 0x0 from 0x0
sbatch: debug4: xsignal: Swap signal ALRM[14] to 0x0 from 0x0
sbatch: debug4: xsignal: Swap signal PIPE[13] to 0x1 from 0x0
sbatch: debug4: xsignal: Swap signal PIPE[13] to 0x0 from 0x1
Submitted batch job 112

slurmd -D -vvvvvvvv
.
.
.
slurmd: debug:  prep/script: _run_spank_job_script: _run_spank_job_script: calling /usr/sbin/slurmstepd spank prolog
spank-prolog: debug2: debug level read from slurmd is 'unknown'.
spank-prolog: debug2: _read_slurmd_conf_lite: slurmd sent 8 TRES.
spank-prolog: debug:  Running spank/prolog for jobid [112] uid [1000] gid [1000]
spank-prolog: debug:  spank: opening plugin stack /etc/slurm/plugstack.conf
spank-prolog: debug3: plugin_peek: dlopen(/usr/lib64/slurm/auto_tmpdir.so): /usr/lib64/slurm/auto_tmpdir.so: cannot open shared object file: No such file or directory
spank-prolog: debug3: plugin_peek->_verify_syms: found Slurm plugin name:auto_tmpdir type:spank version:0x170b0a
spank-prolog: debug3: plugin_load_from_file->_verify_syms: found Slurm plugin name:auto_tmpdir type:spank version:0x170b0a
spank-prolog: debug3: Couldn't find sym 'slurm_spank_local_user_init' in the plugin
spank-prolog: debug3: Couldn't find sym 'slurm_spank_user_init' in the plugin
spank-prolog: debug3: Couldn't find sym 'slurm_spank_task_init_privileged' in the plugin
spank-prolog: debug3: Couldn't find sym 'slurm_spank_task_init' in the plugin
spank-prolog: debug3: Couldn't find sym 'slurm_spank_task_post_fork' in the plugin
spank-prolog: debug3: Couldn't find sym 'slurm_spank_task_exit' in the plugin
spank-prolog: debug3: Couldn't find sym 'slurm_spank_slurmd_exit' in the plugin
spank-prolog: debug3: Couldn't find sym 'slurm_spank_exit' in the plugin
spank-prolog: debug:  spank: /etc/slurm/plugstack.conf:1: Loaded plugin auto_tmpdir.so
spank-prolog: debug:  SPANK: appending plugin option "no-rm-tmpdir"
spank-prolog: debug:  SPANK: appending plugin option "use-shared-tmpdir"
spank-prolog: debug:  auto_tmpdir::auto_tmpdir_fs_init: 112 for owner 1000:1000
spank-prolog: debug:  auto_tmpdir::auto_tmpdir_fs_init: no_rm_shared_only set, ensuring no should_not_delete bit in options
spank-prolog: debug:  auto_tmpdir::auto_tmpdir_fs_init: local_prefix=/mnt/scratch/tmpdir-
spank-prolog: debug:  auto_tmpdir::auto_tmpdir_fs_init: shared_prefix=/arc/scratch1/jobs/job-
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: created directory `/mnt/scratch/tmpdir-112/tmp`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: set ownership 1000:1000 on directory `/mnt/scratch/tmpdir-112/tmp`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: added bindpoint `/mnt/scratch/tmpdir-112/tmp` -> `/tmp`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: created directory `/mnt/scratch/tmpdir-112/var_tmp`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: set ownership 1000:1000 on directory `/mnt/scratch/tmpdir-112/var_tmp`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: added bindpoint `/mnt/scratch/tmpdir-112/var_tmp` -> `/var/tmp`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: created directory `/dev/shm/slurm-112`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: set ownership 1000:1000 on directory `/dev/shm/slurm-112`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_create_bindpoint: added bindpoint `/dev/shm/slurm-112` -> `/dev/shm`
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_default_state_file: 112
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_default_state_file: state_dir=/var/tmp/auto_tmpdir_cache
spank-prolog: debug:  auto_tmpdir::auto_tmpdir_fs_serialize_to_file: serialized to `/var/tmp/auto_tmpdir_cache/auto_tmpdir_fs-112.cache`
spank-prolog: debug2: spank: auto_tmpdir.so: job_prolog = 0
slurmd: debug:  unsetenv (SPANK__SLURM_SPANK_OPTION_auto_tmpdir_use_shared_tmpdir)
slurmd: Launching batch job 112 for UID 1000
slurmd: debug3: _rpc_batch_job: call to _forkexec_slurmstepd
slurmd: debug3: slurmstepd rank -1 (localhost), parent rank -1 (NONE), children 0, depth 0, max_depth 0
slurmd: debug3: _rpc_batch_job: return from _forkexec_slurmstepd: 0
slurmd: debug2: Finish processing RPC: REQUEST_BATCH_JOB_LAUNCH
slurmd: debug3: in the service_connection
slurmd: debug2: Start processing RPC: REQUEST_TERMINATE_JOB
slurmd: debug2: Processing RPC: REQUEST_TERMINATE_JOB
slurmd: debug:  _rpc_terminate_job: uid = 5829 JobId=112
slurmd: debug:  credential for job 112 revoked
slurmd: debug2: No steps in jobid 112 to send signal 18
slurmd: debug2: No steps in jobid 112 to send signal 15
slurmd: debug4: sent SUCCESS
slurmd: debug4: xsignal: Swap signal PIPE[13] to 0x1 from 0x0
slurmd: debug4: xsignal: Swap signal PIPE[13] to 0x0 from 0x1
slurmd: debug2: set revoke expiration for jobid 112 to<PHONE_NUMBER> UTS
slurmd: debug:  Waiting for job 112's prolog to complete
slurmd: debug:  Finished wait for job 112's prolog to complete
slurmd: debug:  prep/script: _run_spank_job_script: _run_spank_job_script: calling /usr/sbin/slurmstepd spank epilog
spank-epilog: debug2: debug level read from slurmd is 'unknown'.
spank-epilog: debug2: _read_slurmd_conf_lite: slurmd sent 8 TRES.
spank-epilog: debug:  Running spank/epilog for jobid [112] uid [1000] gid [1000]
spank-epilog: debug:  spank: opening plugin stack /etc/slurm/plugstack.conf
spank-epilog: debug3: plugin_peek: dlopen(/usr/lib64/slurm/auto_tmpdir.so): /usr/lib64/slurm/auto_tmpdir.so: cannot open shared object file: No such file or directory
spank-epilog: debug3: plugin_peek->_verify_syms: found Slurm plugin name:auto_tmpdir type:spank version:0x170b0a
spank-epilog: debug3: plugin_load_from_file->_verify_syms: found Slurm plugin name:auto_tmpdir type:spank version:0x170b0a
spank-epilog: debug3: Couldn't find sym 'slurm_spank_local_user_init' in the plugin
spank-epilog: debug3: Couldn't find sym 'slurm_spank_user_init' in the plugin
spank-epilog: debug3: Couldn't find sym 'slurm_spank_task_init_privileged' in the plugin
spank-epilog: debug3: Couldn't find sym 'slurm_spank_task_init' in the plugin
spank-epilog: debug3: Couldn't find sym 'slurm_spank_task_post_fork' in the plugin
spank-epilog: debug3: Couldn't find sym 'slurm_spank_task_exit' in the plugin
spank-epilog: debug3: Couldn't find sym 'slurm_spank_slurmd_exit' in the plugin
spank-epilog: debug3: Couldn't find sym 'slurm_spank_exit' in the plugin
spank-epilog: debug:  spank: /etc/slurm/plugstack.conf:1: Loaded plugin auto_tmpdir.so
spank-epilog: debug:  SPANK: appending plugin option "no-rm-tmpdir"
spank-epilog: debug:  SPANK: appending plugin option "use-shared-tmpdir"
spank-epilog: debug:  auto_tmpdir::__auto_tmpdir_fs_default_state_file: 112
spank-epilog: debug:  auto_tmpdir::__auto_tmpdir_fs_default_state_file: state_dir=/var/tmp/auto_tmpdir_cache
spank-epilog: debug:  auto_tmpdir::auto_tmpdir_fs_bindpoint_dealloc: `/dev/shm/slurm-112` -> `/dev/shm` (0|1) 0x1d8e430
spank-epilog: debug:  auto_tmpdir::auto_tmpdir_fs_bindpoint_dealloc: removing directory `/dev/shm/slurm-112`
spank-epilog: debug:  auto_tmpdir::auto_tmpdir_fs_bindpoint_dealloc: moving to next directory 0x1d8e430
spank-epilog: debug:  auto_tmpdir::auto_tmpdir_fs_bindpoint_dealloc: `/mnt/scratch/tmpdir-112/tmp` -> `/tmp` (0|0) 0x1d8e400
spank-epilog: debug:  auto_tmpdir::auto_tmpdir_fs_bindpoint_dealloc: removing directory `/mnt/scratch/tmpdir-112/tmp`
spank-epilog: debug:  auto_tmpdir::auto_tmpdir_fs_bindpoint_dealloc: moving to next directory 0x1d8e400
spank-epilog: debug:  auto_tmpdir::auto_tmpdir_fs_bindpoint_dealloc: `/mnt/scratch/tmpdir-112/var_tmp` -> `/var/tmp` (0|0) (nil)
spank-epilog: debug:  auto_tmpdir::auto_tmpdir_fs_bindpoint_dealloc: removing directory `/mnt/scratch/tmpdir-112/var_tmp`
spank-epilog: debug:  auto_tmpdir::auto_tmpdir_fs_bindpoint_dealloc: moving to next directory (nil)
spank-epilog: debug:  auto_tmpdir::auto_tmpdir_fs_bindpoint_dealloc: removing directory `/mnt/scratch/tmpdir-112`
spank-epilog: debug2: spank: auto_tmpdir.so: job_epilog = 0
slurmd: debug:  unsetenv (SPANK__SLURM_SPANK_OPTION_auto_tmpdir_use_shared_tmpdir)
slurmd: debug:  completed epilog for jobid 112
slurmd: debug4: xsignal: Swap signal ALRM[14] to 0x0 from 0x0
slurmd: debug4: xsignal: Swap signal ALRM[14] to 0x0 from 0x0
slurmd: debug4: xsignal: Swap signal PIPE[13] to 0x1 from 0x0
slurmd: debug4: xsignal: Swap signal PIPE[13] to 0x0 from 0x1
slurmd: debug:  JobId=112: sent epilog complete msg: rc = 0
slurmd: debug2: Finish processing RPC: REQUEST_TERMINATE_JOB

   :
spank-prolog: debug:  auto_tmpdir::__auto_tmpdir_fs_default_state_file: state_dir=/var/tmp/auto_tmpdir_cache
spank-prolog: debug:  auto_tmpdir::auto_tmpdir_fs_serialize_to_file: serialized to `/var/tmp/auto_tmpdir_cache/auto_tmpdir_fs-112.cache`
spank-prolog: debug2: spank: auto_tmpdir.so: job_prolog = 0
slurmd: debug:  unsetenv (SPANK__SLURM_SPANK_OPTION_auto_tmpdir_use_shared_tmpdir)
   :

The fact that the job environment contains SPANK__SLURM_SPANK_OPTION_auto_tmpdir_use_shared_tmpdir (hence its being removed after the prolog step) should mean that spank_option_getopt() will return that CLI option value.  You're 100% certain the new copy of the plugin you compiled (from the test branch) is installed and being loaded by slurmd?

btw, since the slurm dev install instructions are not good, I documented the install of Slurm running only on localhost for dev purposes on RHEL9/Rocky9 if you find that useful
https://github.com/dirkpetersen/dptests/blob/main/slurm/slurm-install.md


Issue with chunks when combining

pangeo_forge_recipes/rechunking.py
raise ValueError("Cannot combine fragments because they do not form a regular hypercube.")

ValueError: Cannot combine fragments because they do not form a regular hypercube. [while running 'Create|OpenURLWithFSSpec|OpenWithXarray|Preprocess|StoreToZarr/StoreToZarr/Rechunk/MapTuple(combine_fragments)']

Source Code raising the error in pangeo forge:
    # now we need to unstack the 1D concat dims into an ND nested data structure
    # first step is figuring out the shape
    dims_starts_sizes = [(
            dim.name,
            [index[dim].value for index in all_indexes],
            [ds.sizes[dim.name] for ds in all_dsets],
        )
        for dim in concat_dims]
[...]

starts_cube = [np.array(item[1]).reshape(shape) for item in dims_starts_sizes]
    sizes_cube = [np.array(item[2]).reshape(shape) for item in dims_starts_sizes]
    try:
        # reversing order is necessary here because _sort_by_speed_of_varying puts the
        # arrays into the opposite order as wanted by np.meshgrid
        starts = _invert_meshgrid(*starts_cube[::-1])[::-1]
        sizes = _invert_meshgrid(*sizes_cube[::-1])[::-1]
    except AssertionError:
        raise ValueError("Cannot combine fragments because they do not form a regular hypercube.")

I suspect that there is an issue with a scalar dimension. Did you try to drop/squeeze all coords as part of the preprocessing?


Customize Elasticsearch index prefix based on message data

Would you be interested in PR implementing the above?

Sounds reasonable as well.


License requirements for break glass accounts

Customers are asking about license requirements for a break glass account. For example if there are EMS E3 / EMS E5 allocated to all users - is there an advantage of allocating EMS E3 / EMS E5 bundle or just a subset (AAD P1 / AAD P2) licenses to break-glass accounts?
The second question is if there is any benefit from creating mail box associated with break glass account.
This document is great, but licensing and mailbox is not clearly explained.
Regards,
Serg

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

ID: fff5de5d-9a97-73ff-4694-79027720b5c3
Version Independent ID: 566a8387-bbdd-8e35-13cc-f2d891bd5608
Content: Manage emergency access admin accounts - Azure AD
Content Source: articles/active-directory/users-groups-roles/directory-emergency-access.md
Service: active-directory
Sub-service: users-groups-roles
GitHub Login: @markwahl-msft
Microsoft Alias: curtand

@SergGu Thanks for the feedback !  I have assigned this issue to content author to investigate and update the document as appropriate.

#reassign:MicrosoftGuyJFlo Azure AD is licensed per user as discussed in the documentation https://azure.microsoft.com/pricing/details/active-directory/. Conditional Access requires Azure AD Premium P1 or P2 licenses. #please-close


Add dgash to Contributors in material-branch

Dave Gash is the author of the push notifications primer and the new performance codelab docs.
Can we add him to the list of contributors so I can add him as an owner?
Thanks.

He's already in the _contributors.yaml file. I see him on line 196. Are you not seeing him?

I see him in there, so closing. If you don't see him, be sure to sync your branch with the main material-branch


One-dimensional textures

Hi,
Modern OpenGL supports single-dimension textures. A 1-D texture could be used, for example, to store a series of skeleton bone matrices/vec3+quats in a linear (aka: fast to read) format.
Cheers!

Is this just statement or a feature request? :)

Both, lol.
I am glad to state that I've chosen bgfx as the path forward for my own game/graphics platform, and I have already created a fork with the eager intention of packporting improvements. This will likely be one of them, although my experience is limited to (modern) OpenGL and I have found little to suggest that DIrect3D supports such textures either.

Yeah everything supports it, just I never had need for just 1D textures. Even in case when I had to use 1D style lookup it was done inside 2D texture because those lookup tables can be all stored into single 2D texture with V being lookup table selection.

I agree, their uses are definitely limited; my only likely use for them would be to do clever things with voxels.

What about creating 2D texture that has width x 1 size?

Yeah, that was also an inclination of mine. Frankly, the more I think about it, the more it seems that the OpenGL steering commitee wasn't thinking very hard when they introduced this feature. Until my benchmarks prove otherwise, let's call this issue closed. :P


Excel option missing from download table in workspace

This is a must have!!!  Biologists speak excel and in my experience, they don't even know how to take a text file and convert it to excel.  This must come back!

Added excel download.


Update HISTORY in advance of v0.2.0 release

As we prepare to release v0.2.0, let's update the HISTORY file with a description of the new features or changes that have been added since 0.1.0 was tagged. For refactoring, cleaning, and other internal changes, we can just say "other various improvements".

What do you think about just listing the closed PRs?
Maybe for some of them just rephrase the title (f.e. "We need docs" -> "Update README with project description, installation instructions and usage examples")


Fix experimental proto3 build error

Verified both on Ubuntu 22.04 which has issue #77 as well as on Arch Linux with more modern protobuf and no regression

Excellent, much appreciated.  Merged.

@scsibug this also resolves the CI build, tested on my fork https://github.com/yuvadm/nostr-rs-relay/actions/runs/4181611913/jobs/7243733290


Samsung Galaxy A520W

I'm trying to root my device but I'm getting this error when trying to save the .PIT file. I have installed all required dependencies, tried different USB ports. I am running Lubuntu 17.04

sudo heimdall download-pit --output  ~/Desktop/A520W.pit --verbose --no-reboot --stdout-errors
Heimdall v1.4.0

Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
        length: 18
  device class: 2
           S/N: 0
       VID:PID: 04E8:685D
     bcdDevice: 021B

iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
libusb: error [op_set_interface] setintf failed error -1 errno 71
ERROR: Setting up interface failed!
ERROR: Setting up interface failed!
Releasing device interface...

So I built Heimdall from source (upgrading to 1.4.2) and I got a step further but not sure if the .PIT was created correctly because I am given a warning. I'm guessing not.
sudo ./heimdall download-pit --output  ~/Desktop/A520W.pit --verbose --no-reboot --stdout-errors
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
        length: 18
  device class: 2
           S/N: 0
       VID:PID: 04E8:685D
     bcdDevice: 021B

iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
WARNING: Empty bulk transfer after receiving packet failed. Continuing anyway...
WARNING: Empty bulk transfer after receiving packet failed. Continuing anyway...
PIT file download successful.
Ending session...
Releasing device interface...

Here is the contents of my .PIT file
./heimdall print-pit --file ~/Desktop/A520W.pit
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Entry Count: 30
Unknown 1:<PHONE_NUMBER>
Unknown 2: 844251476
Unknown 3: 21324
Unknown 4: 14153
Unknown 5: 14392
Unknown 6: 48
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 80
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOTLOADER
Flash Filename: sboot.bin
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 90
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 0
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CM
Flash Filename: cm.bin
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 91
Attributes: 2 (STL Read-Only)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 6144
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: ECT
Flash Filename: ect.bin
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 34
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: -
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 71
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 50
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MD5HDR
Flash Filename: md5.img
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 1
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 8192
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA0
Flash Filename: -
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 2
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 16384
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOTA1
Flash Filename: -
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 3
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 24576
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.img
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 4
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 65536
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CPEFS
Flash Filename: cpefs.img
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 5
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 81920
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: m9kefs1
Flash Filename: m9kefs1.bin
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 6
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 90112
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: m9kefs2
Flash Filename: m9kefs2.bin
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 7
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 98304
Partition Block Count: 8192
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: m9kefs3
Flash Filename: m9kefs3.bin
FOTA Filename:
--- Entry #12 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 8
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 106496
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CARRIER
Flash Filename: carrier.img
FOTA Filename:
--- Entry #13 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 9
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 108544
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.bin
FOTA Filename:
--- Entry #14 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 10
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 124928
Partition Block Count: 65536
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: BOOT
Flash Filename: boot.img
FOTA Filename:
--- Entry #15 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 11
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 190464
Partition Block Count: 77824
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: recovery.img
FOTA Filename:
--- Entry #16 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 12
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 268288
Partition Block Count: 16384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: OTA
Flash Filename: -
FOTA Filename:
--- Entry #17 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 13
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 284672
Partition Block Count: 92160
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RADIO
Flash Filename: modem.bin
FOTA Filename:
--- Entry #18 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 14
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 376832
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: TOMBSTONES
Flash Filename: tombstones.img
FOTA Filename:
--- Entry #19 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 15
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 378880
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DNT
Flash Filename: dnt.ssw
FOTA Filename:
--- Entry #20 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 16
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 380928
Partition Block Count: 1024
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PERSISTENT
Flash Filename:
FOTA Filename:
--- Entry #21 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 17
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 381952
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: STEADY
Flash Filename: steady.bin
FOTA Filename:
--- Entry #22 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 18
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 384000
Partition Block Count: 9216
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RESERVED2
Flash Filename: -
FOTA Filename:
--- Entry #23 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 19
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 393216
Partition Block Count: 11878400
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SYSTEM
Flash Filename: system.img
FOTA Filename:
--- Entry #24 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 20
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 12271616
Partition Block Count: 819200
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.img
FOTA Filename:
--- Entry #25 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 21
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 13090816
Partition Block Count: 204800
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: HIDDEN
Flash Filename: hidden.img
FOTA Filename:
--- Entry #26 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 22
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 13295616
Partition Block Count: 10240
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CP_DEBUG
Flash Filename: modem_debug.bin
FOTA Filename:
--- Entry #27 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 23
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 13305856
Partition Block Count: 40960
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: NAD_FW
Flash Filename: nad_fw.bin
FOTA Filename:
--- Entry #28 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 24
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 13346816
Partition Block Count: 2048
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: NAD_REFER
Flash Filename: nad_refer.bin
FOTA Filename:
--- Entry #29 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 25
Attributes: 5 (Read/Write)
Update Attributes: 5 (FOTA)
Partition Block Size/Offset: 13348864
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: USERDATA
Flash Filename: userdata.img
FOTA Filename: remained

Tried flashing SuperSU and I receive this. I am running as superuser
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
        length: 18
  device class: 2
           S/N: 0
       VID:PID: 04E8:685D
     bcdDevice: 021B

iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Beginning session...
ERROR: libusb error -7 whilst receiving bulk transfer. Retrying...
ERROR: libusb error -7 whilst receiving bulk transfer. Retrying...
ERROR: libusb error -7 whilst receiving bulk transfer. Retrying...
ERROR: libusb error -7 whilst receiving bulk transfer. Retrying...
ERROR: libusb error -7 whilst receiving bulk transfer. Retrying...
ERROR: libusb error -7 whilst receiving bulk transfer.
Releasing device interface...

Don't forget to make sure that after you've run a command with --no-reboot that the next command includes --resume. I think that might be the issue here.

i even tried with heimdall-frontend with those options selected and I still have the issue.

@shaqaruden That specific error you most recently reported just doesn't make a heap of sense seems as earlier you posted output demonstrating that beginning a session works fine. At that point the commands are yet to do anything differently.
So either the device was not ready to receive packets (need to reboot back into download mode) or there are USB reliability issues with your PC - because I can't see why it would have worked fine earlier but not now with the exact same binary.
It's probably worth noting that users have in past had issues with libusb and/or their kernel i.e. Users had no success with Heimdall until they updated their OS. I don't know specifically why that would be the case, but unfortunately whatever the reason it's out of my/Heimdall's hands.
I should note that I'm not actually sure whether Galaxy A5 works with Heimdall. However, the fact you were able to download your PIT is a positive sign; usually it's all or nothing.

Updating your OS may be a non-option - or perhaps it's already up-to-date. However, you can try downloading and building the latest official libusb release from source, then rebuild Heimdall. No promises, but it's worth a shot.

I will attempt it


LAB_03_AzureLocks.md

English:
learn
Current Translation:
瞭解
Suggested Translation:
了解
Description:
Typo

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Run bugfix tool and waiting for result.


Add issue template

Resolves: #5

@juffalow Thanks for the PR. We look into a template which has more information. If you can improve this I'd be happy to merge this.


Multiple create statement support.

Currently , Creating multiple tables look like this-
   session.query("CREATE TABLE IF NOT EXISTS test (user_id text primary key)",&[],) .await?;
   session.query("CREATE TABLE IF NOT EXISTS test2 (user_id text primary key)",&[],) .await?;
   session.query("CREATE TABLE IF NOT EXISTS test3 (user_id text primary key)",&[],) .await?;

Is their any alternative way where we can batch multiple create statement together and execute it once.
Or is it insignificant to have batching for create query because they are rare and max occurrence can be in hundreds. So wouldn't lead to any performance improvement?

The driver supports sending batches of statements. Did you try it?
https://docs.rs/scylla/latest/scylla/transport/session/struct.Session.html#method.batch
I'm also not sure if it is supported scylla-side, but you should give it a shot.

Thanks for your reply @piodul and @Lorak-mmk  , As per document, batch only supports INSERT, UPDATE and DELETE. I also tested it from my side DDL statements cannot be batched.


Broadcast batch elements in vmap

It would be great to have a way of obtaining elements of a mini batch from within vmap, i.e. an equivalent of pmap's all_gather.
Abstracting away the batch dimension seems like one of the core JAX features, but there are a lot of use cases where batch information is necessary. Some that come to mind are normalizing modules, such as BatchNorm, or contrastive estimation which often depends on positive/negative samples across the minibatch.
Related to this, are there any plans to unify vmap and pmap and potentially expose the rest of the parallel operators for use with vmap?

Great questions! Yes indeed there are plans to unify vmap and pmap, including supporting collectives in vmap. Actually, we've planned to do that for a while, but what's new is we've actually made some progress in the last week!
Here's the status. There's a core rewrite branch called "omnistaging3" that moves around some machinery to make this possible (among other things). In addition, we have some experiments in the "gmap" branch, including a proof-of-concept that we can indeed add collective support to vmap, as well as some experiments with a map primitive where it's easy to re-schedule the evaluation strategy (between mixtures of parallel, vectorized, and iterative evaluation).
Hopefully we'll have some more updates in the next few weeks!
cc @apaszke @hawkinsp

Actually, I think this might be a duplicate of #2939, so let's close it and coalesce the conversation there!


err Error: connect EMFILE

when I use the connector to two days after, the web server  error: "
err Error: connect EMFILE <IP_ADDRESS>:5432 - Local (undefined:undefined)
at /app/node_modules/pg-pool/index.js:45:11
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async PGClient.query (/app/server/util/postgres.js:39:24)
at async PGClient.list (/app/server/util/postgres.js:136:26)
at async Object.loadData (/app/server/util/cache.js:30:26) {
errno: -24,
code: 'EMFILE',
syscall: 'connect',
address: '<IP_ADDRESS>',
port: 5432"
I think maybe this problem is the db connect not use pool or maybe it's not properly closing the connection?

I also encountered this problem, which can cause the docker container to become "unhealthy" after running for about a day, leading to the service becoming unavailable.

I think the problem is log file descriptor leak, it will create two new fd every time loggerHandler called and never released.

number of log file descriptors in the nodejs process.(314452):

lsof -p 314452 | grep 'combined.log' | wc -l
961

after temp fix:

lsof -p 340793 | grep 'combined.log' | wc -l
1

@wengkaer will you please have a look?

When using winston, I incorrectly called the createLogger method in the middleware, causing a file handle leak.
This error will be fixed in 0.0.19.

I think the problem is log file descriptor leak, it will create two new fd every time loggerHandler called and never released.

number of log file descriptors in the nodejs process.(314452):

lsof -p 314452 | grep 'combined.log' | wc -l
961

after temp fix:

lsof -p 340793 | grep 'combined.log' | wc -l
1

@wengkaer will you please have a look?

Thank you for pointing out the error you described. This error will be fixed in the next version 0.0.19.


doesn't reload css after .twig refresh..

when I change+save a .twig file, the css on the website disappear.. is it something that you are experiencing too ?
please let me know.. thanks!

feel free to book a call if you wanna discuss this problem a bit further
https://cal.com/lorenzodossi/30min

Hi!
Please provide more context

ddev version (ddev -v)
operating system
craftcms version
craftcms vite plugin version
vite version

Do you use my example repository or your own custom implementation?

sure!

ddev version v1.23.0
macos sonoma 14.3.1
"craftcms/cms": "^5.0.0",
"nystudio107/craft-vite":"^5.0.0",
"vite": "^5.1.4"

here is a short video showcasing the problem -> https://streamable.com/6gesiq
edit html -> all good
edit scss -> all good
edit html again -> doesn't work
-> need to reload manually the page

Hey,
thanks for detailed description + video! 👍
First of all: Twig reloading is not really "hot module reloading" in craftcms vite plugin, the whole page needs a reload after twig changes (because twigis not tighly integrated like css changes in Vite).
Second: After you run ddev npm run dev, you need to reload your browser one time to get the Vite dev server active. Otherwise manifest.json from previous builds will be used. See config/vite.php:
// this will ping $devServerInternal to make sure it's running,
// otherwise it falls back to web/dist/manifest.json
'checkDevServer' => true,

You can check in devtools if Vite connected - or not:

When you use browser reload once after ddev npm run dev - and Vite devserver is connected, each twig change should be cause a browser reload:
https://github.com/mandrasch/ddev-craftcms-vite/assets/777278/a8a4b914-077f-48c1-849f-4bd8d687d1fc
This is handled by https://www.npmjs.com/package/vite-plugin-restart, see vite.config.js
plugins: [
        ViteRestart({
        restart: [
            './templates/**/*',
        ],
    })]

"Second: After you run ddev npm run dev, you need to reload your browser manually once to get the Vite dev server active."
that was the problem! Thanks immensely
btw if you need some help related to css/motion stuff, don't hesitate to hit me up, I owe you a favor!
https://www.lorenzodossi.com/

Happy to help! 👍


[Snyk] Security upgrade moment from 2.15.1 to 2.19.3

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

package.json
package-lock.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

399/1000  Why? Has a fix available, CVSS 3.7
Regular Expression Denial of Service (ReDoS) npm:moment:20170905
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

test


Fix Markdown formatting so README properly renders on hexdocs

An extra backtick before `web_mailer_module: MyAppWeb` causes the README on hexdocs
 to render everything after it into a giant block of text:

The commit removes that backtick so the README should properly render with this change.

Thanks!


Please add a way to add prefix or custom URL mapping for OidcProviderConfigurationEndpointFilter  /.well-known/openid-configuration/

Expected Behavior
Hello, I would like to add the following Feature.
I have a web application that has the Server Context URL  https://app-server.com/app-context-name/authenticator
The problem is that the OidcProviderConfigurationEndpointFilter class is final and does not allow modifying the filter url endpoint value. In this example the Metadata Endpoint would be
https://app-server.com/app-context-name/.well-known/openid-configuration/
instead of https://app-server.com/app-context-name/authenticator/.well-known/openid-configuration/
after the sub endpoint /authenticator/
It would be possible to modify the ServerSettings class to be able to override the endpoint like in UserInfo, IdToken for example:
OidcProviderConfigurationEndpointFilter.java
		OidcProviderConfiguration.Builder providerConfiguration = OidcProviderConfiguration.builder()
				.metadataPrefix(authorizationServerSettings.getPrefix())
				.issuer(issuer)
				.authorizationEndpoint(asUrl(issuer, authorizationServerSettings.getAuthorizationEndpoint()))
				.tokenEndpoint(asUrl(issuer, authorizationServerSettings.getTokenEndpoint()))`

AuthorizationServerSettings.java
            public static Builder builderWithPrefix(@NonNull String prefix) {
		return new Builder()
				.metadataPrefix(prefix + "/.well-known/openid-configuration")
				.authorizationEndpoint(prefix + "/oauth2/authorize")
				.tokenEndpoint(prefix +"/oauth2/token")
				.jwkSetEndpoint(prefix +"/oauth2/jwks")
				.tokenRevocationEndpoint(prefix +"/oauth2/revoke")
				.tokenIntrospectionEndpoint(prefix +"/oauth2/introspect")
				.oidcClientRegistrationEndpoint(prefix +"/connect/register")
				.oidcUserInfoEndpoint(prefix + "/userinfo");
	}

Current Behavior
it doesn't work, but it could
       public final class OidcProviderConfigurationEndpointFilter extends OncePerRequestFilter {
	/**
	 * The default endpoint {@code URI} for OpenID Provider Configuration requests.
	 */
	private static final String DEFAULT_OIDC_PROVIDER_CONFIGURATION_ENDPOINT_URI = "/.well-known/openid-configuration";

	private final RequestMatcher requestMatcher = new AntPathRequestMatcher(
			PREFIX + DEFAULT_OIDC_PROVIDER_CONFIGURATION_ENDPOINT_URI,
			HttpMethod.GET.name());
	private final OidcProviderConfiguration

Context
You can override the other Endpoints from the configuration: https://docs.spring.io/spring-authorization-server/docs/current/reference/html/configuration-model.html#configuring-authorization-server-settings but the Metadata ( OIDC 1.0 DiscoveyrEndpoint) (/.well-known/openid-configuration) it's not possible.

@FoxNeo We already have an open and related issue. Please add your comments to gh-1342 and I'll close this as a duplicate.


feat(cpo): adhere to upgrade order from kube version skew policy

What this PR does / why we need it:
This CPO change ensures kube-apiserver and openshift-apiserver deployments to roll out all updated replicas before proceeding with reconciliation. This makes it so that hypershift control planes adheres to the supported upgrade order as described in kube version skew policy.
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #1222
Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.
[ ] This change includes docs.
[x] This change includes unit tests.

/retest

/retest

@sjenning @enxebre @csrwng Please re-review and I'm happy to make further adjustments, if needed.

/retest

/retest

/cherry-pick release-4.9

/cherry-pick release-4.10


fix middleware decorator

What does it implement/fix? Explain your changes.
Hi!
When I try to run hacker_news under examples, I got an error. It look like this:

Yes, because of this line of code：
 return register_middleware() in middleware.py (line:31)
Where has this been tested?
Python Version: python3.6.7
Operating System: Ubuntu18.04
Does this close any currently open issues?
No
Does this add any new dependency?
No
Does this add any new command line switch/option?
No
Any other comments you would like to make?
I don't think the exception handling here is very friendly and does not directly reflect the problem.
Some Questions
No

[x] I have documented my code.
[x] I have tested my build before submitting the pull request.

Hi @duolaAOA :
Thanks for your PR, are you talking about this script named middleware_demo.py?

I haven't run middleware_demo.py before, but I just tried it and it worked fine,It look like the img:

but when I run hacker_news.py, it worked wrong.

I maybe  know the cause of the problem, and I'll check back with it after work.

Hi @duolaAOA :
Thanks for your quick reply, the reason for this error is that the example code was not updated in time.
It is fixed now :)


The annotation 'SqlServer:Include' was not found. Ensure that the annotation has been added

I am going to make a null field in database,
I changed long? to long
this is my field :
public long Size { get; set; }
and this is my configuration :
            b.Property(x => x.Size)
                .IsRequired();

and table is empty
and when I want to update database I got this error :
The annotation 'SqlServer:Include' was not found. Ensure that the annotation has been added.
Further technical details
EF Core version: 2.2
Database Provider: Microsoft.EntityFrameworkCore.SqlServer
Operating system: Windows 10
IDE: Visual Studio 2017 15.8.2

@per3ian Please post a runnable project/solution or complete code listing that demonstrates the behavior you are seeing.

I do not know if it helps.
I had the same problem, but in my case I was changing the IdentityDbContext, I ended up having to remove all the migrations and generate the initial again, which I saw was that in the creation of the project in the Migrations folder XXX.Designer. cs, ProductVersion was on preview1  and the new migrations were as preview2

This annotation is about include filter on an index. Changing nullability of a column would change filter defined on index associated with such column.

I just received this as well. On 2.2.0-preview2-35157.
In OnModelCreating, I am calling the following:
modelBuilder.Entity<Company>().HasIndex(t => t.EIN).IsUnique(true).ForSqlServerInclude("LegalName", "Website", "AddressId", "AlternateNames", "ReturnType");
I subsequently increased the length of the LegalName field and am now receiving the same error as reported above.
In the initial migration, I see the entity has
b.HasIndex("EIN").IsUnique().HasAnnotation("SqlServer:Include", new[] { "LegalName", "Website", "AddressId", "AlternateNames", "ReturnType" });
This appears in the field length increase migration file as well, so I'm not sure why it's reporting that SqlServer:Include was not found. Not sure what else I can provide that might be helpful.
I have since removed all (2) migrations and recreated the database with a newly created migration. The issue has not reappeared.

@per3ian @gabrielRibeiroCamargoFerreira @olaeld @cculver What is the full stack trace of the exception?

I just started getting this exception, too.  I did a search in my solution for "SqlServer:Include", and there are 0 matches.
The stack trace is:

0

{"assembly":"Microsoft.EntityFrameworkCore, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60","method":"Microsoft.EntityFrameworkCore.Infrastructure.AnnotatableExtensions.GetAnnotation","level":0,"line":0}

1

{"assembly":"Microsoft.EntityFrameworkCore.SqlServer, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60","method":"Microsoft.EntityFrameworkCore.Migrations.SqlServerMigrationsSqlGenerator+<GetIndexesToRebuild>d__48.MoveNext","level":1,"line":0}

2

{"assembly":"mscorlib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Collections.Generic.List`1..ctor","level":2,"line":0}

3

{"assembly":"System.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Linq.Enumerable.ToList","level":3,"line":0}

4

{"assembly":"Microsoft.EntityFrameworkCore.SqlServer, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60","method":"Microsoft.EntityFrameworkCore.Migrations.SqlServerMigrationsSqlGenerator.Generate","level":4,"line":0}

5

{"assembly":"Microsoft.EntityFrameworkCore.Relational, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60","method":"Microsoft.EntityFrameworkCore.Migrations.MigrationsSqlGenerator.Generate","level":5,"line":0}

6

{"assembly":"Microsoft.EntityFrameworkCore.Relational, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60","method":"Microsoft.EntityFrameworkCore.Migrations.MigrationsSqlGenerator.Generate","level":6,"line":0}

7

{"assembly":"Microsoft.EntityFrameworkCore.SqlServer, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60","method":"Microsoft.EntityFrameworkCore.Migrations.SqlServerMigrationsSqlGenerator.Generate","level":7,"line":0}

8

{"assembly":"Microsoft.EntityFrameworkCore.Relational, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60","method":"Microsoft.EntityFrameworkCore.Migrations.Internal.Migrator.GenerateUpSql","level":8,"line":0}

9

{"assembly":"Microsoft.EntityFrameworkCore.Relational, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60","method":"Microsoft.EntityFrameworkCore.Migrations.Internal.Migrator.Migrate","level":9,"line":0}

10

...

11

{"assembly":"mscorlib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089","method":"System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw","level":11,"line":0}

12

{"assembly":"Microsoft.AspNetCore.Hosting, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60","method":"Microsoft.AspNetCore.Hosting.ConventionBasedStartup.Configure","level":12,"line":0}

13

{"assembly":"Microsoft.AspNetCore.Hosting, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60","method":"Microsoft.AspNetCore.Hosting.Internal.WebHost.BuildApplication","level":13,"line":0}

Here's a better stack trace:

Application startup exception: System.InvalidOperationException: The annotation 'SqlServer:Include' was not found. Ensure that the annotation has been added.
   at Microsoft.EntityFrameworkCore.Infrastructure.AnnotatableExtensions.GetAnnotation(IAnnotatable annotatable, String annotationName)
   at Microsoft.EntityFrameworkCore.Migrations.SqlServerMigrationsSqlGenerator.<GetIndexesToRebuild>d__48.MoveNext()
   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at Microsoft.EntityFrameworkCore.Migrations.SqlServerMigrationsSqlGenerator.Generate(AlterColumnOperation operation, IModel model, MigrationCommandListBuilder builder)
   at Microsoft.EntityFrameworkCore.Migrations.MigrationsSqlGenerator.Generate(MigrationOperation operation, IModel model, MigrationCommandListBuilder builder)
   at Microsoft.EntityFrameworkCore.Migrations.MigrationsSqlGenerator.Generate(IReadOnlyList`1 operations, IModel model)
   at Microsoft.EntityFrameworkCore.Migrations.SqlServerMigrationsSqlGenerator.Generate(IReadOnlyList`1 operations, IModel model)
   at Microsoft.EntityFrameworkCore.Migrations.Internal.Migrator.GenerateUpSql(Migration migration)
   at Microsoft.EntityFrameworkCore.Migrations.Internal.Migrator.Migrate(String targetMigration)
   ...
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Hosting.ConventionBasedStartup.Configure(IApplicationBuilder app)
   at Microsoft.AspNetCore.Hosting.Internal.WebHost.BuildApplication()

Mine's basically the same.
System.InvalidOperationException: The annotation 'SqlServer:Include' was not found. Ensure that the annotation has been added.    at Microsoft.EntityFrameworkCore.Infrastructure.AnnotatableExtensions.GetAnnotation(IAnnotatable annotatable, String annotationName)    at Microsoft.EntityFrameworkCore.Migrations.SqlServerMigrationsSqlGenerator.GetIndexesToRebuild(IProperty property, MigrationOperation currentOperation)+MoveNext()    at System.Collections.Generic.List1.AddEnumerable(IEnumerable1 enumerable)    at System.Linq.Enumerable.ToList[TSource](IEnumerable1 source)
at Microsoft.EntityFrameworkCore.Migrations.SqlServerMigrationsSqlGenerator.Generate(AlterColumnOperation operation, IModel model, MigrationCommandListBuilder builder)
at Microsoft.EntityFrameworkCore.Migrations.MigrationsSqlGenerator.<>c.<.cctor>b__73_4(MigrationsSqlGenerator g, MigrationOperation o, IModel m, MigrationCommandListBuilder b)
at Microsoft.EntityFrameworkCore.Migrations.MigrationsSqlGenerator.Generate(MigrationOperation operation, IModel model, MigrationCommandListBuilder builder)
at Microsoft.EntityFrameworkCore.Migrations.SqlServerMigrationsSqlGenerator.Generate(MigrationOperation operation, IModel model, MigrationCommandListBuilder builder)
at Microsoft.EntityFrameworkCore.Migrations.MigrationsSqlGenerator.Generate(IReadOnlyList1 operations, IModel model)    at Microsoft.EntityFrameworkCore.Migrations.SqlServerMigrationsSqlGenerator.Generate(IReadOnlyList1 operations, IModel model)
at Microsoft.EntityFrameworkCore.Migrations.Internal.Migrator.GenerateUpSql(Migration migration)
at Microsoft.EntityFrameworkCore.Migrations.Internal.Migrator.<>c__DisplayClass13_2.b__2()
at Microsoft.EntityFrameworkCore.Migrations.Internal.Migrator.Migrate(String targetMigration)
at Microsoft.EntityFrameworkCore.Design.Internal.MigrationsOperations.UpdateDatabase(String targetMigration, String contextType)
at Microsoft.EntityFrameworkCore.Design.OperationExecutor.UpdateDatabaseImpl(String targetMigration, String contextType)
at Microsoft.EntityFrameworkCore.Design.OperationExecutor.UpdateDatabase.<>c__DisplayClass0_1.<.ctor>b__0()
at Microsoft.EntityFrameworkCore.Design.OperationExecutor.OperationBase.Execute(Action action)`

It's also happening to me.
I need to increase the max length of a property from 255 to 500.
I spinned a migration that change the maxLength.
Then when I run the update-database. It throws error
here is the stack trace
System.InvalidOperationException: The annotation 'SqlServer:Include' was not found. Ensure that the annotation has been added.
   at Microsoft.EntityFrameworkCore.Infrastructure.AnnotatableExtensions.GetAnnotation(IAnnotatable annotatable, String annotationName)
   at Microsoft.EntityFrameworkCore.Migrations.SqlServerMigrationsSqlGenerator.GetIndexesToRebuild(IProperty property, MigrationOperation currentOperation)+MoveNext()
   at System.Collections.Generic.List`1.AddEnumerable(IEnumerable`1 enumerable)
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at Microsoft.EntityFrameworkCore.Migrations.SqlServerMigrationsSqlGenerator.Generate(AlterColumnOperation operation, IModel model, MigrationCommandListBuilder builder)
   at Microsoft.EntityFrameworkCore.Migrations.MigrationsSqlGenerator.Generate(MigrationOperation operation, IModel model, MigrationCommandListBuilder builder)
   at Microsoft.EntityFrameworkCore.Migrations.MigrationsSqlGenerator.Generate(IReadOnlyList`1 operations, IModel model)
   at Microsoft.EntityFrameworkCore.Migrations.SqlServerMigrationsSqlGenerator.Generate(IReadOnlyList`1 operations, IModel model)
   at Microsoft.EntityFrameworkCore.Migrations.Internal.Migrator.GenerateUpSql(Migration migration)
   at Microsoft.EntityFrameworkCore.Migrations.Internal.Migrator.Migrate(String targetMigration)
   at Microsoft.EntityFrameworkCore.Design.Internal.MigrationsOperations.UpdateDatabase(String targetMigration, String contextType)
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.OperationBase.Execute(Action action)
The annotation 'SqlServer:Include' was not found. Ensure that the annotation has been added.

Environment : Visual Studio 2018 15.8.4
OS : Windows 7 Professional SP1
EF : EntityFrameworkCore.SqlServer (2.2.0 preview1-3509)
Net Core : 2.1


Minor optimization in ignoreElements operator

Description:
Minor optimization in ignoreElements operator.
We don't need to call any kind of noop function, simply do not call anything.
I mean, sure, it's not a bottleneck by no means, but better without, right?

Coverage decreased (-0.0008%) to 97.079% when pulling f40eafbe5e794304c3a2670a02c04c2816f2f29a on fljot:patch-1 into efcd922384116b2a45e7d7859e09cf6da34d7371 on ReactiveX:master.

... will fix commit message later, if PR is needed at all.

Coverage decreased (-0.0008%) to 97.079% when pulling d013820cea3635aabee6fd400d5118cdd2a8cc97 on fljot:patch-1 into efcd922384116b2a45e7d7859e09cf6da34d7371 on ReactiveX:master.


fix: add Stats toJson typings

What kind of change does this PR introduce?
Add typings for Stats['toJson'] method, and typings for the sort field.
Resolving a part of https://github.com/webpack/webpack/issues/11630.
Did you add tests for your changes?
No tests added as this is simply type definitions.
Does this PR introduce a breaking change?
No
What needs to be documented once your changes are merged?
In @types/webpack@^4 we would originally get the structure of the JSON output as webpack.Stats.ToJsonOutput.
In version 5, we would now do ReturnType<webpack.Stats['toJson']> as this appears to be the present limitation of using jsdoc to document typings with the present webpack approach.

Hmm, I signed in the CLA, but after the last build went through. Could someone kick it off again? Also, not sure about how to resolve the coverage decrease as the changes are purely typings rather than actual code change.

After a bit of playing around in the consuming application, this PR isn't yet ready.

Given I need a bit more time to work this out (and personal matters have taken some time) I'll close the ticket and reopen it when it is ready


KERNEL: Land existing Flash Attention 2 performance pieces in IREE

Done with a bunch of commits and the last one with https://github.com/openxla/iree/pull/16455.


PDI-13452 - Automatic Documentation Output Step fails when receiving a reference that doesn't have any steps in it

@mbatchelor, @mattcasters could you review it?
It may be related to PDI-13455 - It is possible to save empty jobs and transformations into the repository.

@mbatchelor, @mattcasters could you review it?
Backport for it https://github.com/pentaho/pentaho-kettle/pull/1111


PF-35 Added R example

This example shows usage of the timeseries_client.R wrapper for getting time-aligned data into R.

@JacobPatenaude-AI Can you have a look at this R example?
@GordPollock-AI You might be interested in this as well.
It's probably enough to simply view the rendered Readme.md and look for typos.


Add spread coefficient - helps understand if the distancing works

Hey,
Can we add a graph showing the delta aka:
(Number of people infected)/(people (infected the day before).
This gives a coefficient that if is greater that 1 means we are in exponential growth. So we hope it will go down as social distancing takes effect.
Video about the math:
https://www.youtube.com/watch?v=Kas0tIxDvrg&t=16

done.
here

Hey seems like its not updating cc @idandrd

Hey seems like its not updating cc @idandrd

I can assure you we update as soon as there is data. Unfortunately the MOH has not updated data on testing for several days now, so updated normalised coefficient is not available until then.

Perhaps we should open an issue at: https://github.com/MohGovIL/hamagen-react-native

Cc @MohGovIL any chance updating your data?

Perhaps we should open an issue at: https://github.com/MohGovIL/hamagen-react-native

Testing has nothing to do with HaMagen app data and owners, and asking MOH to update has not worked so far on our side.


Optimize Data Store for performance

Once the RDS is complete in Phase 1, we'd like to optimize it for performance.  If you have ideas on how to do this with index or other methods, you can make a pull request to add support for it with examples to this repo so everyone can benefit.  Use this issue as a place to discuss and collaborate.

As discussed in #25, there are some pretty big performance gains to be had on insert-heavy workloads (such as when reprocessing lots of old files) if the FKs are removed.  The larger the quantity of files in the queue, the greater the impact, as lock contention only gets worse the more there is.  Just noting all of that here so we can review later.

I've got some scripts to remove all the FKs and some to add them all back in.  I've been backloading data and what I do is remove the FKs and it's more than twice as fast, then add them in at the end.
Once all the data is backloaded (doing it in 1 month chunks now) I'd like to post scripts for creating indexes, which really speed up query analysis.
I'm working on writing these and documenting them and will make a PR to add the docs and scripts to the repo when done.

Working on this here: https://github.com/LouisvilleMetro/WazeCCPProcessor/pull/41


Spacing tweaks to Dictionaries & Language Packs CSS (bug 732529)

Your latest modifications result in the following:

As you can see, it adds two blank lines after all the table cells, not between the lines in the content.
I realize this is sadly a very hard to fix issue for several reasons:
1/ without the data (from production), it's hard to have a table/page to work on and experiment, and coding blind is close to impossible
2/ the content of the table cells are computed by a jinja2 macro (which isn't very straightforward for a beginner)
3/ the css file is a preprocessed less file
All this cumulated made it very hard for a first contribution, but you sticked with it, congratulations! Also, with your attempts, it helped me localize the issue and fix it with the following:
diff --git a/static/css/impala/dictionaries.less b/static/css/impala/dictionaries.less
index 6297e2b..c3c6661 100644
--- a/static/css/impala/dictionaries.less
+++ b/static/css/impala/dictionaries.less
@@ -7,6 +7,12 @@
     tbody {
         td, th {
             width: 25%;
+            p {
+                margin-bottom: 1em;
+            }
+            p:last-child {
+                margin-bottom: 0;
+            }
         }
     }
 }

Thanks a lot @kangareuben! If you want to pick on something else, please do so, I'll be there to help!

@magopian - let's do it.  Thanks @kangareuben for kicking us off.

@magopian, that looks like exactly what I was trying to do! Yes, please go ahead with the fix and merge.
I"m glad I was able to be a little bit helpful, but sorry I couldn't do more. Thanks very much for your assistance through this whole process; I certainly learned a lot!


Explain environment guesses to the user

We've had several tickets recently that came up due to customers not
realizing (and who could blame them) that even if they provide an app
handle and no environment, we're overriding their choice of environment
based on the current git remote.
This patch updates the aptible CLI to explain the decisions it makes,
and specifically to explain what environment it looked in (if it did
scope its search to a single environment), and where that came from.

Another solution would be to not guess the environment from the git remote when an app handle is provided (i.e. either guess everything or nothing). I avoided that solution to avoid breaking backwards compatibility, but it might make sense too. Let me know what you think.
cc @wcpines @fancyremarker

Here's what this looks like when used:
aptible restart --app test-app-v1
Could not find app test-app-v1 in environment aptible (NOTE: environment was derived from git remote aptible-thomas, use --environment to override)

aptible restart --app test-app-v1 --environment v1
Restarting app...
...

[Current coverage][cc-pull] is 84.44%

Merging [#168][cc-pull] into [master][cc-base-branch] will increase coverage by 0.87%

@@             master       #168   diff @@
==========================================
  Files            24         24
  Lines           864        906    +42
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            722        765    +43
+ Misses          142        141     -1
  Partials          0          0

Powered by Codecov. Last updated by [eba5020...ba679ec][cc-compare]
[cc-base-branch]: https://codecov.io/gh/aptible/aptible-cli/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/aptible/aptible-cli/compare/eba50200f695e5397327899b30f4e6874849503e...ba679ec88864f0234632b03482d07fc4b855701b
[cc-pull]: https://codecov.io/gh/aptible/aptible-cli/pull/168?src=pr

CC @blakepettersson.  This came up this week.

Another solution would be to not guess the environment from the git remote when an app handle is provided (i.e. either guess everything or nothing)

I think that should only happen if the handle is indeed present in multiple apps. So:

Get app with matching handle
If multiple apps exist, guess from the git remote (if there is one)
???

@blakepettersson I think this is a little too unpredictable.
Say you have production and staging using the same handles, your git remote is set up so that stuff goes to staging. Now, one of your colleagues ends up deleting staging (or renaming it, whatever). Suddenly, your commands to go prod.
Of course, that's a hypothetical, but IMHO, there are always going to be some edge cases, etc.
I'd rather we don't try to be too smart for our own good (that's the reason we have this PR in the first place). It's not like adding one parameter (after being told so) is such a big deal — is it?

Another solution would be to not guess the environment from the git remote when an app handle is provided (i.e. either guess everything or nothing). I avoided that solution to avoid breaking backwards compatibility, but it might make sense too. Let me know what you think.

I actually prefer this solution, and am not particularly concerned about preserving backward compatibility on this particular point. (I would prefer to have a more intuitive API with some theoretical — although IMO practically very limited — backward incompatibility.)

Perhaps this belongs in a separate PR, but a related issue occurs when users run apps:create (or db:create) without specifying an environment. Perhaps we could help suggest their available environments in that context?
(See https://aptible.zendesk.com/agent/tickets/5934.)

@fancyremarker agreed your suggestion would be a good idea, but this does probably belong to a separate PR.
This one is replaced by https://github.com/aptible/aptible-cli/pull/170