DM11 Retry Missing?

Engine sent busy, yet 2nd DM11 was not not observed in log.
11:57:23.0553 Global DM11 Request
11:57:23.0583 18EAFFF9 [3] D3 FE 00 (TX)
11:57:23.0609 18E8FF13 [8] 00 00 FF FF FF D3 FE 00
Acknowledgment from Steering Controller (19): Response: ACK, Group Function: 0, Address Acknowledged: 255, PGN Requested: 65235
11:57:23.0615 18E8FF17 [8] 00 FF FF FF F9 D3 FE 00
Acknowledgment from Instrument Cluster #1 (23): Response: ACK, Group Function: 255, Address Acknowledged: 249, PGN Requested: 65235
11:57:23.0693 18E8FF00 [8] 03 FF FF FF F9 D3 FE 00
Acknowledgment from Engine #1 (0): Response: Busy, Group Function: 255, Address Acknowledged: 249, PGN Requested: 65235
<IP_ADDRESS>.c - Checking for erased diagnostic information
11:57:28.6612 Destination Specific DM6 Request to Engine #1 (0)
11:57:28.6649 18EA00F9 [3] CF FE 00 (TX)
11:57:28.6703 18FECF00 [8] 00 FF 00 00 00 00 FF FF
DM6 from Engine #1 (0): MIL: off, RSL: off, AWL: off, PL: off, No DTCs
11:57:28.6706 Destination Specific DM12 Request to Engine #1 (0)
11:57:28.6739 18EA00F9 [3] D4 FE 00 (TX)
11:57:28.6802 18FED400 [8] 00 FF [00 00 00 00](tel:00 00 00 00) FF FF
DM12 from Engine #1 (0): MIL: off, RSL: off, AWL: off, PL: off, No DTCs
11:57:28.6812 Destination Specific DM23 Request to Engine #1 (0)
11:57:28.6838 18EA00F9 [3] B5 FD 00 (TX)
11:57:28.6902 18FDB500 [8] 00 FF [00 00 00 00 FF FF
DM23 from Engine #1 (0): MIL: off, RSL: off, AWL: off, PL: off, No DTCs
11:57:28.6911 Destination Specific DM29 Request to Engine #1 (0)
11:57:28.6933 18EA00F9 [3] 00 9E 00 (TX)
11:57:28.7002 189EF900 [8] [00 00 00 00 01 FF FF FF
DM29 from Engine #1 (0):
Emission-Related Pending DTC Count                               0
All Pending DTC Count                                            0
Emission-Related MIL-On DTC Count                                0
Emission-Related Previously MIL-On DTC Count                     0
Emission-Related Permanent DTC Count                             1
11:57:28.7002 Destination Specific DM5 Request to Engine #1 (0)
11:57:28.7039 18EA00F9 [3] CE FE 00 (TX)
11:57:28.7108 18FECE00 [8] [00 00 14 27 E0 1E E0 1E
DM5 from Engine #1 (0): OBD Compliance: HD OBD (20), Active Codes: 0, Previously Active Codes: 0
FAIL: <IP_ADDRESS>.c - Engine #1 (0) did not erase DM5 data
// Engine sent busy… no retry in log

27 is likely correct.
from 13 CCR 1971.1 (h)(4)
(4.1.1)  The  readiness  status  for  the following  component/system  readiness  bits shall  always  indicate “complete”: (A) Diesel  misfire (section (e)(2))  for  engines  with  a  single monitor  designed to detect  both  misfires  identified in section (e)(2.2.1) and subject  to the monitoring  conditions  of  sections  (e)(2.3.1)  and (e)(2.3.2)  and misfires  identified in section (e)(2.2.2)  and subject  to the monitoring  conditions  of  (e)(2.3.3); (B)  Gasoline misfire (section (f)(2));  and (C)  Diesel  and gasoline  comprehensive component  (section (g)(3)).
(4.1.3)  For  2016  and subsequent  model  year  engines,  for  components  and systems  not  listed in section (h)(4.1.1)  above,  the readiness  status  for each component/system  readiness  bit  listed  below  shall  immediately indicate “complete”  if  any  of  the following  conditions  occur:  (1)  all  the respective  supported  monitors  listed below  for  each component/system have fully  executed and determined that  the component  or  system  is not malfunctioning,  or  (2)  at  least  one of  the monitors  listed below  for  each component/system  has  determined that  the component  or  system  is malfunctioning  after  the requisite number  of  decisions  necessary  for determining  the MIL status  have been fully  executed,  regardless  of whether  or  not  the other  monitors  listed have been fully  executed: (A)  Diesel  Fuel  System:  sections  (e)(1.2.1),  (e)(1.2.2),  and  (e)(1.2.3) (B)  Diesel  Misfire:  section  (e)(2.2.1)  for  engines  with a separate monitor designed to detect  misfires  identified in section (e)(2.2.1)  and subject  to the monitoring  conditions  of  sections  (e)(2.3.1)  and (e)(2.3.2) (C)  Diesel EGR/VVT:  sections  (e)(3.2.1),  (e)(3.2.2),  (e)(3.2.3),  (e)(3.2.5), (e)(3.2.6),  and  (e)(10.2) (D)  Diesel Boost  Pressure Control  System:  sections  (e)(4.2.1),  (e)(4.2.2), (e)(4.2.3),  and (e)(4.2.4) (E)  Diesel  NMHC Converting  Catalyst:  sections  (e)(5.2.2)  and (e)(5.2.3)(A) (F)  Diesel  NOx  Converting  Catalyst:  section (e)(6.2.1) (G)  Diesel  NOx  Aftertreatment:  sections  (e)(7.2.1)  and (e)(7.2.2) (H)  Diesel PM  Filter:   (i)  For  2016 through 2023  model  year  engines,  sections  (e)(8.2.1), (e)(8.2.2),  (e)(8.2.5),  and (e)(8.2.6)   (ii) For 2024  and subsequent  model  year  engines,  sections  (e)(8.2.1)  and (e)(8.2.5) (I)  Diesel  Exhaust  Gas  Sensor:   (i)  For  2016 and subsequent  model  year  engines  on  vehicles  using  the SAE  J1939 protocol  for  the standardized functions  required in section (h),  and for  2016 through 2023  model  year  engines  on  vehicles  using the ISO  15765-4 protocol  for  the standardized functions  required in section (h),  sections  (e)(9.2.1)(A)(i),  (e)(9.2.1)(A)(iv),  (e)(9.2.1)(B)(i), (e)(9.2.1)(B)(iv),  (e)(9.2.2)(A),  (e)(9.2.2)(D),  and  (e)(9.2.3)(A) (ii)  For  2024  and subsequent  model  year  engines  on  vehicles  using  the ISO  15765-4 protocol  for  the standardized functions  required in section (h),  sections  (e)(9.2.1)(A)(i),  (e)(9.2.1)(A)(iv),  (e)(9.2.1)(B)(i), (e)(9.2.1)(B)(iv),  (e)(9.2.2)(A),  (e)(9.2.2)(D),  (e)(9.2.3)(A),  and (e)(9.2.4)(A) (J)  Diesel  Exhaust  Gas  Sensor  Heater:  section  (e)(9.2.4)(A)  for  vehicles  using the  SAE J1939  protocol  for  the standardized functions  required in section (h) (JK)  Gasoline Fuel  System:  section (f)(1.2.1)(C) (KL)  Gasoline  EGR/VVT:  sections  (f)(3.2.1),  (f)(3.2.2),  (f)(9.2.1),  (f)(9.2.2), and (f)(9.2.3) (LM)  Gasoline Secondary  Air  System:  sections  (f)(5.2.1),  (f)(5.2.2),  (f)(5.2.3), and (f)(5.2.4) (MN)  Gasoline  Catalyst:  section (f)(6.2.1) (NO)  Gasoline Evaporative System:  sections  (f)(7.2.2)(A)  and (f)(7.2.2)(B) (OP)  Gasoline Oxygen Sensor:  sections  (f)(8.2.1)(A),  (f)(8.2.1)(D), (f)(8.2.2)(A),  and  (f)(8.2.2)(C) (Q)  Gasoline Oxygen/Exhaust  Gas  Sensor  Heater:  section (f)(8.2.3)(A) (4.1.4)  For  2016 and subsequent  model  year  engines,  for  monitors  that  detect faults  of  more than one major  emission-related component  (e.g.,  a single monitor  that  is  used to detect  both oxygen sensor  faults  that  are tied to the oxygen sensor  readiness  bit  and air-fuel  ratio cylinder  imbalance faults that  are tied to the fuel  system  readiness  bit),  the manufacturer  shall include the  monitor  only  in the readiness  status  for  the component/system  that  the monitor  is  primarily  calibrated,  intended,  or expected in-use to detect  faults  of. (4.1.5)  Except  for  the readiness  bits  listed under  section (h)(4.1.1)  above,  the readiness  status  for  each of  the monitored components  or  systems  shall indicate “not  complete”  whenever  fault  memory  has  been cleared or erased by  a means  other  than that  allowed in section (d)(2).   Normal vehicle shut  down (i.e.,  key  off,  engine off)  may  not  cause the readiness status  to indicate “not  complete”.
(4.1.7)  Manufacturers  are not  required to use the following  monitors  in determining  the readiness  status  for  the specific  component  or  system: (A)  Circuit  and out-of-range monitors  that  are required to be continuous; (B)  Gasoline and diesel  exhaust  gas  sensor  feedback  monitors  specified in sections  (e)(9.2.1)(A)(iii),  (e)(9.2.1)(B)(iii),  (e)(9.2.2)(C),  (f)(8.2.1)(C),  and (f)(8.2.2)(E); (C)  Diesel  feedback  control  monitors  specified in sections  (e)(1.2.4), (e)(3.2.4),  (e)(4.2.5),  (e)(6.2.2)(D),  (e)(7.2.3),  and (e)(8.2.7); (D)  Gasoline fuel  system  monitors  specified in sections  (f)(1.2.1)(A), (f)(1.2.1)(B),  (f)(1.2.2),  and  (f)(1.2.4),  and (f)(1.2.5).

Check busy retry language in -84

D. SAE J1939-21 defines query timeouts and provides for two retries of a given information request. Warnings may be provided for responses that exceed 200 ms, from the query to the first frame of the response, whether provided as a single frame response, BAM, RTS frame, or ACK(Busy). [4] Globally addressed queries shall be accorded two retries. Destination specific queries shall be accorded retries only when the acknowledgement control byte value of 3 “Busy” is received. The multiple response time periods for the RTS/CTS transport protocol shown in SAE J193921 Figure C1 shall be individually observed.
E. An acknowledgement PGN control byte value of 3 “Busy” may be received instead of the requested data for a query.

If the original request was a global request, the tool shall retry at least once using a destination specific request addressed to the ECU that provided the busy response. The destination specific acquisition of the data shall be accepted with a warning. The tool shall retry the request at least one additional time (for a total of four4 times) when a control byte value of 3 has been received.
If the original request was a destination specific request, the tool shall retry using only destination specific requests with a period no more frequent than 200 ms until at least one second has elapsed from the original query to the last request, or until the ECU responds with the requested data, or until the ECU stops responding with the control byte value of 3 “Busy.”. Data that is received within the 1.2 second overall timeout provision shall be accepted with no warning or failure message. Data that is not received may be deemed to have timed out and the ECU shall be identified as having failed the test for the given request.

F. The acknowledgement PGN provides the identification of the request in the PGN data field. The data in the field shall be matched to the data in the request along with the address of the sender when an ACK or NACK is used to determine pass or failure outcomes.
[4] Contention between long DM1 messages, which are sent with a fixed 1 Hz period, and Long BAM responses to global queries, including DM19, DM20, and component ID, have been observed. This contention creates race conditions between the global query and the start of the DM1 broadcast (and its completion). Reception of replies sent by the ECM is expected of the test software, when contention occurs.

From 3.1.0. Retries appear to be provided
14:23:31.8153 Destination Specific DM20 Request to Engine #1 (0)
14:23:31.8184 18EA00F9 [3] 00 C2 00 (TX)
14:23:31.8269 18E8FF00 [8] 03 FF FF FF F9 00 C2 00
Acknowledgment from Engine #1 (0): Response: Busy, Group Function: 255, Address Acknowledged: 249, PGN Requested: 49664
14:23:32.0302 18EA00F9 [3] 00 C2 00 (TX)
14:23:32.0369 18E8FF00 [8] 03 FF FF FF F9 00 C2 00
Acknowledgment from Engine #1 (0): Response: Busy, Group Function: 255, Address Acknowledged: 249, PGN Requested: 49664
14:23:32.2405 18EA00F9 [3] 00 C2 00 (TX)
14:23:32.4246 1CC2F900 [53] 70 00 06 00 CA 14 F8 00 00 00 00 B8 12 F8 00 00 06 00 C6 14 F8 00 00 06 00 F2 0B F8 01 00 06 00 F8 0B F8 00 00 06 00 C9 14 F8 00 00 06 00 EF 0B F8 01 00 06 00
DM20 from Engine #1 (0):  [
Except for global DM11
14:23:31.8153 Destination Specific DM20 Request to Engine #1 (0)
14:23:31.8184 18EA00F9 [3] 00 C2 00 (TX)
14:23:31.8269 18E8FF00 [8] 03 FF FF FF F9 00 C2 00
Acknowledgment from Engine #1 (0): Response: Busy, Group Function: 255, Address Acknowledged: 249, PGN Requested: 49664
14:23:32.0302 18EA00F9 [3] 00 C2 00 (TX)
14:23:32.0369 18E8FF00 [8] 03 FF FF FF F9 00 C2 00
Acknowledgment from Engine #1 (0): Response: Busy, Group Function: 255, Address Acknowledged: 249, PGN Requested: 49664
14:23:32.2405 18EA00F9 [3] 00 C2 00 (TX)
14:23:32.4246 1CC2F900 [53] 70 00 06 00 CA 14 F8 00 00 00 00 B8 12 F8 00 00 06 00 C6 14 F8 00 00 06 00 F2 0B F8 01 00 06 00 F8 0B F8 00 00 06 00 C9 14 F8 00 00 06 00 EF 0B F8 01 00 06 00
DM20 from Engine #1 (0):  [
DM11 is a special case.
Start Test 1.10 - DM11: Diagnostic Data Clear/Reset for Active DTCs
13:41:05.2381 Global DM11 Request
13:41:05.2427 18EAFFF9 [3] D3 FE 00 (TX)
13:41:05.2435 18E8FF2A [8] 00 FF FF FF FF D3 FE 00
Acknowledgment from Headway Controller (42): Response: ACK, Group Function: 255, Address Acknowledged: 255, PGN Requested: 65235
13:41:05.2621 18E8FF00 [8] 03 FF FF FF F9 D3 FE 00
Acknowledgment from Engine #1 (0): Response: Busy, Group Function: 255, Address Acknowledged: 249, PGN Requested: 65235
13:41:05.2663 18E8FF17 [8] 00 FF FF FF F9 D3 FE 00
Acknowledgment from Instrument Cluster #1 (23): Response: ACK, Group Function: 255, Address Acknowledged: 249, PGN Requested: 65235
14:08:44.1824 Global DM11 Request
14:08:44.1847 18EAFFF9 [3] D3 FE 00 (TX)
14:08:44.1863 18E8FF2A [8] 00 FF FF FF FF D3 FE 00
Acknowledgment from Headway Controller (42): Response: ACK, Group Function: 255, Address Acknowledged: 255, PGN Requested: 65235
14:08:44.1987 18E8FF00 [8] 03 FF FF FF F9 D3 FE 00
Acknowledgment from Engine #1 (0): Response: Busy, Group Function: 255, Address Acknowledged: 249, PGN Requested: 65235
14:08:44.2023 18E8FF17 [8] 00 FF FF FF F9 D3 FE 00
Acknowledgment from Instrument Cluster #1 (23): Response: ACK, Group Function: 255, Address Acknowledged: 249, PGN Requested: 65235

Request for DM11 is to Global.  The rules are that the tool should try twice, then request DS.  This rule will not work for DM11.  We need a new plan.

We all agree that DM11 needs to work on the tested vehicle or the test alternation need to recover becomes problematic.


[SPARK-23571][K8S] Delete auxiliary Kubernetes resources upon application completion

What changes were proposed in this pull request?
Spark on Kubernetes creates some auxiliary Kubernetes resources such as the headless driver service used by the executors to connect to the driver and the ConfigMap that carries configuration for the init-container. Such resources are no longer needed once an application completes, but they are still persisted by the API server and there should be deleted upon completion. This PR handles the cases when the submission waits for the application to complete, which is the default behavior as spark.kubernetes.submission.waitAppCompletion defaults to true.
Xref: https://github.com/apache-spark-on-k8s/spark/pull/520.
How was this patch tested?
Unit tested.
@felixcheung @foxish

Test build #87903 has started for PR 20722 at commit 9890ebc.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/1241/
Test PASSed.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/testing-k8s-prb-spark-integration/1232/

Test build #87903 has finished for PR 20722 at commit 9890ebc.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/87903/
Test PASSed.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/testing-k8s-prb-spark-integration/1232/

so where are we on this?

@felixcheung I think we want to move resource management to the driver such that the life time of the resources is bound to the life time of the driver pod. This works regardless of if the user chooses to wait for the application to finish or not. One tricky thing is the creation of the headless driver service. It must be created before the executors are created as otherwise the executors wouldn't be able to connect to the driver. I'm trying to figure out how we can achieve this order guarantee in the KubernetesSchedulerBackend.


Test to ensure all free5GC NFs are running

Test to ensure all free5gc NFs are running. This is to make sure all NFs are running on the edge clusters.. This effort is targeted towards making sure the rst of NFs ( in addition to SMF, UPF, AMF) are running successfully on the edge clusters which is deployed with complete shift left mechanism. This effort is not about test automation rather manual verification of the new package deployment.
Parent issue.

Done (manual testing), but we need automated e2e for this.


Cannot locate files when uploading or downloading

Hi satackey, thank you for this amazing tool!
I'm almost ready to use it, but I'm still missing something. I can see that download-to and upload-from are, by default, the current directory. But what do you mean by that? What is this current directory from where I'm meant to upload the files?
Thank you again for your help!

I think I've found one way to solve this: basically, I first checkout the current version of the branch using:
            - name: Checkout source
              uses: actions/checkout@v2

Then, everything is under /github/workspace/. There might be other ways, but I'm closing this for now. Thank you again!


[simulate.jl] PriorityQueue declaration issue

in function EMSEngine:
eventqueue = PriorityQueue{Tuple{Symbol,Int,Int,Int},Int,Base.Order.ForwardOrdering}()

eventqueue = PriorityQueue{Tuple{Symbol,Int,Int,Int},Int}()


Python Error during runtime of NGen example

I am trying to run the NGen on UAHPC cluster and getting python error during runtime of NGen example.
List of Module

 compilers/gcc/5.4.0
cmake/3.20.1
boost/1.72.0
python/python3/3.9.6
compilers/gcc/9.1.0
mpi/openmpi/gcc/4.1.1

Compilation Log
-- The C compiler identification is GNU 9.1.0
-- The CXX compiler identification is GNU 9.1.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /share/apps/gcc/9.1.0/bin/gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /share/apps/gcc/9.1.0/bin/g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found MPI_C: /share/apps/openmpi/openmpi-4.1.1/installed/lib/libmpi.so (found version "3.1")
-- Found MPI_CXX: /share/apps/openmpi/openmpi-4.1.1/installed/lib/libmpi.so (found version "3.1")
-- Found MPI: TRUE (found version "3.1")
-- Found Boost: /share/apps/boost/1.72.0/lib/cmake/Boost-1.72.0/BoostConfig.cmake (found suitable version "1.72.0", minimum required is "1.72.0")
-- Found UDUNITS2: /usr/lib64/libudunits2.so
-- Found Python: /share/apps/python/3.9.6/bin/python3.9 (found suitable version "3.9.6", minimum required is "3.6.8") found components: Interpreter Development NumPy Development.Module Development.Embed
-- pybind11 v2.10.1
-- Performing Test HAS_FLTO
-- Performing Test HAS_FLTO - Success
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Found Python: /share/apps/python/3.9.6/bin/python3.9 (found version "3.9.6") found components: Interpreter
-- Updating submodule /home/trpatel2/ngen/extern/bmi-cxx
Submodule 'extern/bmi-cxx' (https://github.com/csdms/bmi-cxx.git) registered for path 'extern/bmi-cxx'
Cloning into '/home/trpatel2/ngen/extern/bmi-cxx'...

Importing the numpy C-extensions failed. This error can happen for
many reasons, often due to issues with your setup or how NumPy was
installed.

We have compiled some common reasons and troubleshooting tips at:

    https://numpy.org/devdocs/user/troubleshooting-importerror.html

Please note and check the following:

  * The Python version is: Python3.9 from "/share/apps/python/3.9.6/bin/python3"
  * The NumPy version is: "1.22.2"

and make sure that they are the versions you expect.
Please carefully study the documentation linked above for further help.

Importing the numpy C-extensions failed. This error can happen for
many reasons, often due to issues with your setup or how NumPy was
installed.

We have compiled some common reasons and troubleshooting tips at:

    https://numpy.org/devdocs/user/troubleshooting-importerror.html

Please note and check the following:

  * The Python version is: Python3.9 from "/share/apps/python/3.9.6/bin/python3"
  * The NumPy version is: "1.22.2"

and make sure that they are the versions you expect.
Please carefully study the documentation linked above for further help.

Importing the numpy C-extensions failed. This error can happen for
many reasons, often due to issues with your setup or how NumPy was
installed.

We have compiled some common reasons and troubleshooting tips at:

    https://numpy.org/devdocs/user/troubleshooting-importerror.html

Please note and check the following:

  * The Python version is: Python3.9 from "/share/apps/python/3.9.6/bin/python3"
  * The NumPy version is: "1.22.2"

and make sure that they are the versions you expect.
Please carefully study the documentation linked above for further help.

Original error was: /share/apps/python/3.9.6/lib/python3.9/site-packages/numpy/core/_multiarray_umath.cpython-39-x86_64-linux-gnu.so: undefined symbol: PyObject_SelfIter

At:
  /share/apps/python/3.9.6/lib/python3.9/site-packages/numpy/core/__init__.py(52): <module>
  <frozen importlib._bootstrap>(228): _call_with_frames_removed
  <frozen importlib._bootstrap_external>(850): exec_module
  <frozen importlib._bootstrap>(695): _load_unlocked
  <frozen importlib._bootstrap>(986): _find_and_load_unlocked
  <frozen importlib._bootstrap>(1007): _find_and_load
  <frozen importlib._bootstrap>(228): _call_with_frames_removed
  <frozen importlib._bootstrap>(1066): _handle_fromlist
  /share/apps/python/3.9.6/lib/python3.9/site-packages/numpy/__init__.py(144): <module>
  <frozen importlib._bootstrap>(228): _call_with_frames_removed
  <frozen importlib._bootstrap_external>(850): exec_module
  <frozen importlib._bootstrap>(695): _load_unlocked
  <frozen importlib._bootstrap>(986): _find_and_load_unlocked
  <frozen importlib._bootstrap>(1007): _find_and_load

--------------------------------------------------------------------------
Primary job  terminated normally, but 1 process returned
a non-zero exit code. Per user-direction, the job has been aborted.
--------------------------------------------------------------------------
--------------------------------------------------------------------------
mpirun noticed that process rank 1 with PID 70876 on node compute-17-9 exited on signal 6 (Aborted).
--------------------------------------------------------------------------
2 total processes killed (some possibly by mpirun during cleanup)

@TrupeshKumarPatel Do you get the same error if you run with -n 1?
I'm unable to reproduce this locally, so my initial intuition is that this involves a NumPy configuration issue on the cluster nodes, i.e. NumPy on the nodes is different than the NumPy version used to configure ngen. My experience with MPI is limited, so maybe this should be deferred to @donaldwj or @PhilMiller.

With -np 1 it shows same error but of course print only once.

This looks line an environment specific build/link issue
Original error was: .../site-packages/numpy/core/_multiarray_umath.cpython-39-x86_64-linux-gnu.so: undefined symbol: PyObject_SelfIter

The numpy library being loaded is missing a dynamic link to the python runtime library.
You might try using something like this
LD_PRELOAD=<path_to_python_3.9.so>` ./ngen args...

You can find the shared library path using ldd $(which python).

@hellkite500
With ldd $(which python) I get following output, which doesn't have python_3.9.so file.
[trpatel2@uahpc ~]$ ldd $(which python)
	linux-vdso.so.1 =>  (0x00007ffd29d4c000)
	libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00002b0e6ccde000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00002b0e6cf16000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00002b0e6d132000)
	libutil.so.1 => /lib64/libutil.so.1 (0x00002b0e6d336000)
	libm.so.6 => /lib64/libm.so.6 (0x00002b0e6d53a000)
	libc.so.6 => /lib64/libc.so.6 (0x00002b0e6d83c000)
	libfreebl3.so => /lib64/libfreebl3.so (0x00002b0e6dbff000)
	/lib64/ld-linux-x86-64.so.2 (0x000055dbe7e82000)

So it looks like in this environment, the python executable has been statically linked with libpython.  I'm not 💯 sure what the best solution is in this case.  Can you check out the following command so we can verify the python build setup in this environment?
python3 -m sysconfig

Command
python3 -m sysconfig

Output
Platform: "linux-x86_64"
Python version: "3.9"
Current installation scheme: "posix_prefix"

Paths:
	data = "/share/apps/python/3.9.6"
	include = "/share/apps/python/3.9.6/include/python3.9"
	platinclude = "/share/apps/python/3.9.6/include/python3.9"
	platlib = "/share/apps/python/3.9.6/lib/python3.9/site-packages"
	platstdlib = "/share/apps/python/3.9.6/lib/python3.9"
	purelib = "/share/apps/python/3.9.6/lib/python3.9/site-packages"
	scripts = "/share/apps/python/3.9.6/bin"
	stdlib = "/share/apps/python/3.9.6/lib/python3.9"

Variables:
	ABIFLAGS = ""
	AC_APPLE_UNIVERSAL_BUILD = "0"
	AIX_BUILDDATE = "0"
	AIX_GENUINE_CPLUSPLUS = "0"
	ALT_SOABI = "0"
	ANDROID_API_LEVEL = "0"
	AR = "ar"
	ARFLAGS = "rcs"
	BASECFLAGS = "-Wno-unused-result -Wsign-compare"
	BASECPPFLAGS = ""
	BASEMODLIBS = ""
	BINDIR = "/share/apps/python/3.9.6/bin"
	BINLIBDEST = "/share/apps/python/3.9.6/lib/python3.9"
	BLDLIBRARY = "libpython3.9.a"
	BLDSHARED = "gcc -pthread -shared"
	BUILDEXE = ""
	BUILDPYTHON = "python"
	BUILD_GNU_TYPE = "x86_64-pc-linux-gnu"
	BYTESTR_DEPS = "\"
	CC = "gcc -pthread"
	CCSHARED = "-fPIC"
	CFLAGS = "-Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall"
	CFLAGSFORSHARED = ""
	CFLAGS_ALIASING = ""
	CONFIGFILES = "configure configure.ac acconfig.h pyconfig.h.in Makefile.pre.in"
	CONFIGURE_CFLAGS = ""
	CONFIGURE_CFLAGS_NODIST = "-std=c99 -Wextra -Wno-unused-result -Wno-unused-parameter -Wno-missing-field-initializers -Werror=implicit-function-declaration -fvisibility=hidden"
	CONFIGURE_CPPFLAGS = ""
	CONFIGURE_LDFLAGS = ""
	CONFIGURE_LDFLAGS_NODIST = ""
	CONFIG_ARGS = "'--enable-optimizations' '--with-ensurepip=install' '--prefix=/share/apps/python/3.9.6' '--disable-shared'"
	CONFINCLUDEDIR = "/share/apps/python/3.9.6/include"
	CONFINCLUDEPY = "/share/apps/python/3.9.6/include/python3.9"
	COREPYTHONPATH = ""
	COVERAGE_INFO = "/share/apps/src/python/3.9.6/Python-3.9.6/coverage.info"
	COVERAGE_REPORT = "/share/apps/src/python/3.9.6/Python-3.9.6/lcov-report"
	COVERAGE_REPORT_OPTIONS = "--no-branch-coverage --title "CPython lcov report""
	CPPFLAGS = "-I. -I./Include"
	CXX = "g++ -pthread"
	DESTDIRS = "/share/apps/python/3.9.6 /share/apps/python/3.9.6/lib /share/apps/python/3.9.6/lib/python3.9 /share/apps/python/3.9.6/lib/python3.9/lib-dynload"
	DESTLIB = "/share/apps/python/3.9.6/lib/python3.9"
	DESTPATH = ""
	DESTSHARED = "/share/apps/python/3.9.6/lib/python3.9/lib-dynload"
	DFLAGS = ""
	DIRMODE = "755"
	DIST = "README.rst ChangeLog configure configure.ac acconfig.h pyconfig.h.in Makefile.pre.in Include Lib Misc Ext-dummy"
	DISTDIRS = "Include Lib Misc Ext-dummy"
	DISTFILES = "README.rst ChangeLog configure configure.ac acconfig.h pyconfig.h.in Makefile.pre.in"
	DLINCLDIR = "."
	DLLLIBRARY = ""
	DOUBLE_IS_ARM_MIXED_ENDIAN_IEEE754 = "0"
	DOUBLE_IS_BIG_ENDIAN_IEEE754 = "0"
	DOUBLE_IS_LITTLE_ENDIAN_IEEE754 = "1"
	DTRACE = ""
	DTRACE_DEPS = "\"
	DTRACE_HEADERS = ""
	DTRACE_OBJS = ""
	DYNLOADFILE = "dynload_shlib.o"
	ENABLE_IPV6 = "1"
	ENSUREPIP = "install"
	EXE = ""
	EXEMODE = "755"
	EXPORTSFROM = ""
	EXPORTSYMS = ""
	EXTRATESTOPTS = ""
	EXTRA_CFLAGS = ""
	EXT_SUFFIX = ".cpython-39-x86_64-linux-gnu.so"
	FILEMODE = "644"
	FLOAT_WORDS_BIGENDIAN = "0"
	FLOCK_NEEDS_LIBBSD = "0"
	GETPGRP_HAVE_ARG = "0"
	GITBRANCH = ""
	GITTAG = ""
	GITVERSION = ""
	GNULD = "yes"
	HAVE_ACCEPT4 = "1"
	HAVE_ACOSH = "1"
	HAVE_ADDRINFO = "1"
	HAVE_ALARM = "1"
	HAVE_ALIGNED_REQUIRED = "0"
	HAVE_ALLOCA_H = "1"
	HAVE_ALTZONE = "0"
	HAVE_ASINH = "1"
	HAVE_ASM_TYPES_H = "1"
	HAVE_ATANH = "1"
	HAVE_BIND_TEXTDOMAIN_CODESET = "1"
	HAVE_BLUETOOTH_BLUETOOTH_H = "0"
	HAVE_BLUETOOTH_H = "0"
	HAVE_BROKEN_MBSTOWCS = "0"
	HAVE_BROKEN_NICE = "0"
	HAVE_BROKEN_PIPE_BUF = "0"
	HAVE_BROKEN_POLL = "0"
	HAVE_BROKEN_POSIX_SEMAPHORES = "0"
	HAVE_BROKEN_PTHREAD_SIGMASK = "0"
	HAVE_BROKEN_SEM_GETVALUE = "0"
	HAVE_BROKEN_UNSETENV = "0"
	HAVE_BUILTIN_ATOMIC = "1"
	HAVE_CHFLAGS = "0"
	HAVE_CHOWN = "1"
	HAVE_CHROOT = "1"
	HAVE_CLOCK = "1"
	HAVE_CLOCK_GETRES = "1"
	HAVE_CLOCK_GETTIME = "1"
	HAVE_CLOCK_SETTIME = "1"
	HAVE_COMPUTED_GOTOS = "1"
	HAVE_CONFSTR = "1"
	HAVE_CONIO_H = "0"
	HAVE_COPYSIGN = "1"
	HAVE_COPY_FILE_RANGE = "0"
	HAVE_CRYPT_H = "1"
	HAVE_CRYPT_R = "1"
	HAVE_CTERMID = "1"
	HAVE_CTERMID_R = "0"
	HAVE_CURSES_FILTER = "1"
	HAVE_CURSES_H = "1"
	HAVE_CURSES_HAS_KEY = "1"
	HAVE_CURSES_IMMEDOK = "1"
	HAVE_CURSES_IS_PAD = "1"
	HAVE_CURSES_IS_TERM_RESIZED = "1"
	HAVE_CURSES_RESIZETERM = "1"
	HAVE_CURSES_RESIZE_TERM = "1"
	HAVE_CURSES_SYNCOK = "1"
	HAVE_CURSES_TYPEAHEAD = "1"
	HAVE_CURSES_USE_ENV = "1"
	HAVE_CURSES_WCHGAT = "1"
	HAVE_DECL_ISFINITE = "1"
	HAVE_DECL_ISINF = "1"
	HAVE_DECL_ISNAN = "1"
	HAVE_DECL_RTLD_DEEPBIND = "1"
	HAVE_DECL_RTLD_GLOBAL = "1"
	HAVE_DECL_RTLD_LAZY = "1"
	HAVE_DECL_RTLD_LOCAL = "1"
	HAVE_DECL_RTLD_MEMBER = "0"
	HAVE_DECL_RTLD_NODELETE = "1"
	HAVE_DECL_RTLD_NOLOAD = "1"
	HAVE_DECL_RTLD_NOW = "1"
	HAVE_DECL_TZNAME = "0"
	HAVE_DEVICE_MACROS = "1"
	HAVE_DEV_PTC = "0"
	HAVE_DEV_PTMX = "1"
	HAVE_DIRECT_H = "0"
	HAVE_DIRENT_D_TYPE = "1"
	HAVE_DIRENT_H = "1"
	HAVE_DIRFD = "1"
	HAVE_DLFCN_H = "1"
	HAVE_DLOPEN = "1"
	HAVE_DUP2 = "1"
	HAVE_DUP3 = "1"
	HAVE_DYLD_SHARED_CACHE_CONTAINS_PATH = "0"
	HAVE_DYNAMIC_LOADING = "1"
	HAVE_ENDIAN_H = "1"
	HAVE_EPOLL = "1"
	HAVE_EPOLL_CREATE1 = "1"
	HAVE_ERF = "1"
	HAVE_ERFC = "1"
	HAVE_ERRNO_H = "1"
	HAVE_EXECV = "1"
	HAVE_EXPLICIT_BZERO = "0"
	HAVE_EXPLICIT_MEMSET = "0"
	HAVE_EXPM1 = "1"
	HAVE_FACCESSAT = "1"
	HAVE_FCHDIR = "1"
	HAVE_FCHMOD = "1"
	HAVE_FCHMODAT = "1"
	HAVE_FCHOWN = "1"
	HAVE_FCHOWNAT = "1"
	HAVE_FCNTL_H = "1"
	HAVE_FDATASYNC = "1"
	HAVE_FDOPENDIR = "1"
	HAVE_FDWALK = "0"
	HAVE_FEXECVE = "1"
	HAVE_FINITE = "1"
	HAVE_FLOCK = "1"
	HAVE_FORK = "1"
	HAVE_FORKPTY = "1"
	HAVE_FPATHCONF = "1"
	HAVE_FSEEK64 = "0"
	HAVE_FSEEKO = "1"
	HAVE_FSTATAT = "1"
	HAVE_FSTATVFS = "1"
	HAVE_FSYNC = "1"
	HAVE_FTELL64 = "0"
	HAVE_FTELLO = "1"
	HAVE_FTIME = "1"
	HAVE_FTRUNCATE = "1"
	HAVE_FUTIMENS = "1"
	HAVE_FUTIMES = "1"
	HAVE_FUTIMESAT = "1"
	HAVE_GAI_STRERROR = "1"
	HAVE_GAMMA = "1"
	HAVE_GCC_ASM_FOR_MC68881 = "0"
	HAVE_GCC_ASM_FOR_X64 = "1"
	HAVE_GCC_ASM_FOR_X87 = "1"
	HAVE_GCC_UINT128_T = "1"
	HAVE_GETADDRINFO = "1"
	HAVE_GETC_UNLOCKED = "1"
	HAVE_GETENTROPY = "0"
	HAVE_GETGRGID_R = "1"
	HAVE_GETGRNAM_R = "1"
	HAVE_GETGROUPLIST = "1"
	HAVE_GETGROUPS = "1"
	HAVE_GETHOSTBYNAME = "0"
	HAVE_GETHOSTBYNAME_R = "1"
	HAVE_GETHOSTBYNAME_R_3_ARG = "0"
	HAVE_GETHOSTBYNAME_R_5_ARG = "0"
	HAVE_GETHOSTBYNAME_R_6_ARG = "1"
	HAVE_GETITIMER = "1"
	HAVE_GETLOADAVG = "1"
	HAVE_GETLOGIN = "1"
	HAVE_GETNAMEINFO = "1"
	HAVE_GETPAGESIZE = "1"
	HAVE_GETPEERNAME = "1"
	HAVE_GETPGID = "1"
	HAVE_GETPGRP = "1"
	HAVE_GETPID = "1"
	HAVE_GETPRIORITY = "1"
	HAVE_GETPWENT = "1"
	HAVE_GETPWNAM_R = "1"
	HAVE_GETPWUID_R = "1"
	HAVE_GETRANDOM = "0"
	HAVE_GETRANDOM_SYSCALL = "1"
	HAVE_GETRESGID = "1"
	HAVE_GETRESUID = "1"
	HAVE_GETSID = "1"
	HAVE_GETSPENT = "1"
	HAVE_GETSPNAM = "1"
	HAVE_GETWD = "1"
	HAVE_GLIBC_MEMMOVE_BUG = "0"
	HAVE_GRP_H = "1"
	HAVE_HSTRERROR = "1"
	HAVE_HTOLE64 = "1"
	HAVE_HYPOT = "1"
	HAVE_IEEEFP_H = "0"
	HAVE_IF_NAMEINDEX = "1"
	HAVE_INET_ATON = "1"
	HAVE_INET_PTON = "1"
	HAVE_INITGROUPS = "1"
	HAVE_INTTYPES_H = "1"
	HAVE_IO_H = "0"
	HAVE_IPA_PURE_CONST_BUG = "0"
	HAVE_KILL = "1"
	HAVE_KILLPG = "1"
	HAVE_KQUEUE = "0"
	HAVE_LANGINFO_H = "1"
	HAVE_LARGEFILE_SUPPORT = "0"
	HAVE_LCHFLAGS = "0"
	HAVE_LCHMOD = "0"
	HAVE_LCHOWN = "1"
	HAVE_LGAMMA = "1"
	HAVE_LIBDL = "1"
	HAVE_LIBDLD = "0"
	HAVE_LIBIEEE = "0"
	HAVE_LIBINTL_H = "1"
	HAVE_LIBREADLINE = "1"
	HAVE_LIBRESOLV = "0"
	HAVE_LIBSENDFILE = "0"
	HAVE_LIBUTIL_H = "0"
	HAVE_LINK = "1"
	HAVE_LINKAT = "1"
	HAVE_LINUX_CAN_BCM_H = "1"
	HAVE_LINUX_CAN_H = "1"
	HAVE_LINUX_CAN_J1939_H = "0"
	HAVE_LINUX_CAN_RAW_FD_FRAMES = "1"
	HAVE_LINUX_CAN_RAW_H = "1"
	HAVE_LINUX_CAN_RAW_JOIN_FILTERS = "1"
	HAVE_LINUX_MEMFD_H = "1"
	HAVE_LINUX_NETLINK_H = "1"
	HAVE_LINUX_QRTR_H = "0"
	HAVE_LINUX_RANDOM_H = "1"
	HAVE_LINUX_TIPC_H = "1"
	HAVE_LINUX_VM_SOCKETS_H = "1"
	HAVE_LINUX_WAIT_H = "1"
	HAVE_LOCKF = "1"
	HAVE_LOG1P = "1"
	HAVE_LOG2 = "1"
	HAVE_LONG_DOUBLE = "1"
	HAVE_LSTAT = "1"
	HAVE_LUTIMES = "1"
	HAVE_MADVISE = "1"
	HAVE_MAKEDEV = "1"
	HAVE_MBRTOWC = "1"
	HAVE_MEMFD_CREATE = "0"
	HAVE_MEMORY_H = "1"
	HAVE_MEMRCHR = "1"
	HAVE_MKDIRAT = "1"
	HAVE_MKFIFO = "1"
	HAVE_MKFIFOAT = "1"
	HAVE_MKNOD = "1"
	HAVE_MKNODAT = "1"
	HAVE_MKTIME = "1"
	HAVE_MMAP = "1"
	HAVE_MREMAP = "1"
	HAVE_NCURSES_H = "1"
	HAVE_NDIR_H = "0"
	HAVE_NETPACKET_PACKET_H = "1"
	HAVE_NET_IF_H = "1"
	HAVE_NICE = "1"
	HAVE_NON_UNICODE_WCHAR_T_REPRESENTATION = "0"
	HAVE_OPENAT = "1"
	HAVE_OPENPTY = "1"
	HAVE_PATHCONF = "1"
	HAVE_PAUSE = "1"
	HAVE_PIPE2 = "1"
	HAVE_PLOCK = "0"
	HAVE_POLL = "1"
	HAVE_POLL_H = "1"
	HAVE_POSIX_FADVISE = "1"
	HAVE_POSIX_FALLOCATE = "1"
	HAVE_POSIX_SPAWN = "1"
	HAVE_POSIX_SPAWNP = "1"
	HAVE_PREAD = "1"
	HAVE_PREADV = "1"
	HAVE_PREADV2 = "0"
	HAVE_PRLIMIT = "1"
	HAVE_PROCESS_H = "0"
	HAVE_PROTOTYPES = "1"
	HAVE_PTHREAD_CONDATTR_SETCLOCK = "1"
	HAVE_PTHREAD_DESTRUCTOR = "0"
	HAVE_PTHREAD_GETCPUCLOCKID = "1"
	HAVE_PTHREAD_H = "1"
	HAVE_PTHREAD_INIT = "0"
	HAVE_PTHREAD_KILL = "1"
	HAVE_PTHREAD_SIGMASK = "1"
	HAVE_PTY_H = "1"
	HAVE_PWRITE = "1"
	HAVE_PWRITEV = "1"
	HAVE_PWRITEV2 = "0"
	HAVE_READLINK = "1"
	HAVE_READLINKAT = "1"
	HAVE_READV = "1"
	HAVE_REALPATH = "1"
	HAVE_RENAMEAT = "1"
	HAVE_RL_APPEND_HISTORY = "1"
	HAVE_RL_CATCH_SIGNAL = "1"
	HAVE_RL_COMPLETION_APPEND_CHARACTER = "1"
	HAVE_RL_COMPLETION_DISPLAY_MATCHES_HOOK = "1"
	HAVE_RL_COMPLETION_MATCHES = "1"
	HAVE_RL_COMPLETION_SUPPRESS_APPEND = "1"
	HAVE_RL_PRE_INPUT_HOOK = "1"
	HAVE_RL_RESIZE_TERMINAL = "1"
	HAVE_ROUND = "1"
	HAVE_RTPSPAWN = "0"
	HAVE_SCHED_GET_PRIORITY_MAX = "1"
	HAVE_SCHED_H = "1"
	HAVE_SCHED_RR_GET_INTERVAL = "1"
	HAVE_SCHED_SETAFFINITY = "1"
	HAVE_SCHED_SETPARAM = "1"
	HAVE_SCHED_SETSCHEDULER = "1"
	HAVE_SEM_GETVALUE = "1"
	HAVE_SEM_OPEN = "1"
	HAVE_SEM_TIMEDWAIT = "1"
	HAVE_SEM_UNLINK = "1"
	HAVE_SENDFILE = "1"
	HAVE_SETEGID = "1"
	HAVE_SETEUID = "1"
	HAVE_SETGID = "1"
	HAVE_SETGROUPS = "1"
	HAVE_SETHOSTNAME = "1"
	HAVE_SETITIMER = "1"
	HAVE_SETLOCALE = "1"
	HAVE_SETPGID = "1"
	HAVE_SETPGRP = "1"
	HAVE_SETPRIORITY = "1"
	HAVE_SETREGID = "1"
	HAVE_SETRESGID = "1"
	HAVE_SETRESUID = "1"
	HAVE_SETREUID = "1"
	HAVE_SETSID = "1"
	HAVE_SETUID = "1"
	HAVE_SETVBUF = "1"
	HAVE_SHADOW_H = "1"
	HAVE_SHM_OPEN = "1"
	HAVE_SHM_UNLINK = "1"
	HAVE_SIGACTION = "1"
	HAVE_SIGALTSTACK = "1"
	HAVE_SIGFILLSET = "1"
	HAVE_SIGINFO_T_SI_BAND = "1"
	HAVE_SIGINTERRUPT = "1"
	HAVE_SIGNAL_H = "1"
	HAVE_SIGPENDING = "1"
	HAVE_SIGRELSE = "1"
	HAVE_SIGTIMEDWAIT = "1"
	HAVE_SIGWAIT = "1"
	HAVE_SIGWAITINFO = "1"
	HAVE_SNPRINTF = "1"
	HAVE_SOCKADDR_ALG = "1"
	HAVE_SOCKADDR_SA_LEN = "0"
	HAVE_SOCKADDR_STORAGE = "1"
	HAVE_SOCKETPAIR = "1"
	HAVE_SPAWN_H = "1"
	HAVE_SSIZE_T = "1"
	HAVE_STATVFS = "1"
	HAVE_STAT_TV_NSEC = "1"
	HAVE_STAT_TV_NSEC2 = "0"
	HAVE_STDARG_PROTOTYPES = "1"
	HAVE_STDINT_H = "1"
	HAVE_STDLIB_H = "1"
	HAVE_STD_ATOMIC = "1"
	HAVE_STRDUP = "1"
	HAVE_STRFTIME = "1"
	HAVE_STRINGS_H = "1"
	HAVE_STRING_H = "1"
	HAVE_STRLCPY = "0"
	HAVE_STROPTS_H = "0"
	HAVE_STRSIGNAL = "1"
	HAVE_STRUCT_PASSWD_PW_GECOS = "1"
	HAVE_STRUCT_PASSWD_PW_PASSWD = "1"
	HAVE_STRUCT_STAT_ST_BIRTHTIME = "0"
	HAVE_STRUCT_STAT_ST_BLKSIZE = "1"
	HAVE_STRUCT_STAT_ST_BLOCKS = "1"
	HAVE_STRUCT_STAT_ST_FLAGS = "0"
	HAVE_STRUCT_STAT_ST_GEN = "0"
	HAVE_STRUCT_STAT_ST_RDEV = "1"
	HAVE_STRUCT_TM_TM_ZONE = "1"
	HAVE_SYMLINK = "1"
	HAVE_SYMLINKAT = "1"
	HAVE_SYNC = "1"
	HAVE_SYSCONF = "1"
	HAVE_SYSEXITS_H = "1"
	HAVE_SYS_AUDIOIO_H = "0"
	HAVE_SYS_BSDTTY_H = "0"
	HAVE_SYS_DEVPOLL_H = "0"
	HAVE_SYS_DIR_H = "0"
	HAVE_SYS_ENDIAN_H = "0"
	HAVE_SYS_EPOLL_H = "1"
	HAVE_SYS_EVENT_H = "0"
	HAVE_SYS_FILE_H = "1"
	HAVE_SYS_IOCTL_H = "1"
	HAVE_SYS_KERN_CONTROL_H = "0"
	HAVE_SYS_LOADAVG_H = "0"
	HAVE_SYS_LOCK_H = "0"
	HAVE_SYS_MEMFD_H = "0"
	HAVE_SYS_MKDEV_H = "0"
	HAVE_SYS_MMAN_H = "1"
	HAVE_SYS_MODEM_H = "0"
	HAVE_SYS_NDIR_H = "0"
	HAVE_SYS_PARAM_H = "1"
	HAVE_SYS_POLL_H = "1"
	HAVE_SYS_RANDOM_H = "0"
	HAVE_SYS_RESOURCE_H = "1"
	HAVE_SYS_SELECT_H = "1"
	HAVE_SYS_SENDFILE_H = "1"
	HAVE_SYS_SOCKET_H = "1"
	HAVE_SYS_STATVFS_H = "1"
	HAVE_SYS_STAT_H = "1"
	HAVE_SYS_SYSCALL_H = "1"
	HAVE_SYS_SYSMACROS_H = "1"
	HAVE_SYS_SYS_DOMAIN_H = "0"
	HAVE_SYS_TERMIO_H = "0"
	HAVE_SYS_TIMES_H = "1"
	HAVE_SYS_TIME_H = "1"
	HAVE_SYS_TYPES_H = "1"
	HAVE_SYS_UIO_H = "1"
	HAVE_SYS_UN_H = "1"
	HAVE_SYS_UTSNAME_H = "1"
	HAVE_SYS_WAIT_H = "1"
	HAVE_SYS_XATTR_H = "1"
	HAVE_TCGETPGRP = "1"
	HAVE_TCSETPGRP = "1"
	HAVE_TEMPNAM = "1"
	HAVE_TERMIOS_H = "1"
	HAVE_TERM_H = "1"
	HAVE_TGAMMA = "1"
	HAVE_TIMEGM = "1"
	HAVE_TIMES = "1"
	HAVE_TMPFILE = "1"
	HAVE_TMPNAM = "1"
	HAVE_TMPNAM_R = "1"
	HAVE_TM_ZONE = "1"
	HAVE_TRUNCATE = "1"
	HAVE_TZNAME = "0"
	HAVE_UCS4_TCL = "0"
	HAVE_UNAME = "1"
	HAVE_UNISTD_H = "1"
	HAVE_UNLINKAT = "1"
	HAVE_USABLE_WCHAR_T = "0"
	HAVE_UTIL_H = "1"
	HAVE_UTIMENSAT = "1"
	HAVE_UTIMES = "1"
	HAVE_UTIME_H = "1"
	HAVE_UUID_CREATE = "0"
	HAVE_UUID_ENC_BE = "0"
	HAVE_UUID_GENERATE_TIME_SAFE = "1"
	HAVE_UUID_H = "0"
	HAVE_UUID_UUID_H = "1"
	HAVE_WAIT3 = "1"
	HAVE_WAIT4 = "1"
	HAVE_WAITID = "1"
	HAVE_WAITPID = "1"
	HAVE_WCHAR_H = "1"
	HAVE_WCSCOLL = "1"
	HAVE_WCSFTIME = "1"
	HAVE_WCSXFRM = "1"
	HAVE_WMEMCMP = "1"
	HAVE_WORKING_TZSET = "1"
	HAVE_WRITEV = "1"
	HAVE_X509_VERIFY_PARAM_SET1_HOST = "1"
	HAVE_ZLIB_COPY = "1"
	HAVE__GETPTY = "0"
	HOST_GNU_TYPE = "x86_64-pc-linux-gnu"
	INCLDIRSTOMAKE = "/share/apps/python/3.9.6/include /share/apps/python/3.9.6/include /share/apps/python/3.9.6/include/python3.9 /share/apps/python/3.9.6/include/python3.9"
	INCLUDEDIR = "/share/apps/python/3.9.6/include"
	INCLUDEPY = "/share/apps/python/3.9.6/include/python3.9"
	INSTALL = "/bin/install -c"
	INSTALL_DATA = "/bin/install -c -m 644"
	INSTALL_PROGRAM = "/bin/install -c"
	INSTALL_SCRIPT = "/bin/install -c"
	INSTALL_SHARED = "/bin/install -c -m 755"
	INSTSONAME = "libpython3.9.a"
	IO_H = "Modules/_io/_iomodule.h"
	IO_OBJS = "\"
	LDCXXSHARED = "g++ -pthread -shared"
	LDFLAGS = ""
	LDLIBRARY = "libpython3.9.a"
	LDLIBRARYDIR = ""
	LDSHARED = "gcc -pthread -shared"
	LDVERSION = "3.9"
	LIBC = ""
	LIBDEST = "/share/apps/python/3.9.6/lib/python3.9"
	LIBDIR = "/share/apps/python/3.9.6/lib"
	LIBFFI_INCLUDEDIR = ""
	LIBM = "-lm"
	LIBOBJDIR = "Python/"
	LIBOBJS = ""
	LIBPC = "/share/apps/python/3.9.6/lib/pkgconfig"
	LIBPL = "/share/apps/python/3.9.6/lib/python3.9/config-3.9-x86_64-linux-gnu"
	LIBPYTHON = ""
	LIBRARY = "libpython3.9.a"
	LIBRARY_OBJS = "\"
	LIBRARY_OBJS_OMIT_FROZEN = "\"
	LIBS = "-lcrypt -lpthread -ldl  -lutil -lm"
	LIBSUBDIRS = "tkinter tkinter/test tkinter/test/test_tkinter \"
	LINKCC = "gcc -pthread"
	LINKFORSHARED = "-Xlinker -export-dynamic"
	LIPO_32BIT_FLAGS = ""
	LIPO_INTEL64_FLAGS = ""
	LLVM_PROF_ERR = "no"
	LLVM_PROF_FILE = ""
	LLVM_PROF_MERGER = "true"
	LN = "ln"
	LOCALMODLIBS = ""
	MACHDEP = "linux"
	MACHDEP_OBJS = ""
	MACHDESTLIB = "/share/apps/python/3.9.6/lib/python3.9"
	MACOSX_DEPLOYMENT_TARGET = ""
	MAINCC = "gcc -pthread"
	MAJOR_IN_MKDEV = "0"
	MAJOR_IN_SYSMACROS = "0"
	MAKESETUP = "./Modules/makesetup"
	MANDIR = "/share/apps/python/3.9.6/share/man"
	MKDIR_P = "/bin/mkdir -p"
	MODBUILT_NAMES = "posix  errno  pwd  _sre  _codecs  _weakref  _functools  _operator  _collections  _abc  itertools  atexit  _signal  _stat  time  _thread  _locale  _io  faulthandler  _tracemalloc  _peg_parser  _symtable  xxsubtype"
	MODDISABLED_NAMES = ""
	MODLIBS = ""
	MODOBJS = "Modules/posixmodule.o  Modules/errnomodule.o  Modules/pwdmodule.o  Modules/_sre.o  Modules/_codecsmodule.o  Modules/_weakref.o  Modules/_functoolsmodule.o  Modules/_operator.o  Modules/_collectionsmodule.o  Modules/_abc.o  Modules/itertoolsmodule.o  Modules/atexitmodule.o  Modules/signalmodule.o  Modules/_stat.o  Modules/timemodule.o  Modules/_threadmodule.o  Modules/_localemodule.o  Modules/_iomodule.o Modules/iobase.o Modules/fileio.o Modules/bytesio.o Modules/bufferedio.o Modules/textio.o Modules/stringio.o  Modules/faulthandler.o  Modules/_tracemalloc.o  Modules/_peg_parser.o  Modules/symtablemodule.o  Modules/xxsubtype.o"
	MODULE_OBJS = "\"
	MULTIARCH = "x86_64-linux-gnu"
	MULTIARCH_CPPFLAGS = "-DMULTIARCH=\"x86_64-linux-gnu\""
	MVWDELCH_IS_EXPRESSION = "1"
	NO_AS_NEEDED = "-Wl,--no-as-needed"
	OBJECT_OBJS = "\"
	OPENSSL_INCLUDES = ""
	OPENSSL_LDFLAGS = ""
	OPENSSL_LIBS = "-lssl -lcrypto"
	OPT = "-DNDEBUG -g -fwrapv -O3 -Wall"
	OTHER_LIBTOOL_OPT = ""
	PACKAGE_BUGREPORT = "0"
	PACKAGE_NAME = "0"
	PACKAGE_STRING = "0"
	PACKAGE_TARNAME = "0"
	PACKAGE_URL = "0"
	PACKAGE_VERSION = "0"
	PARSER_HEADERS = "\"
	PARSER_OBJS = "\ \ Parser/myreadline.o Parser/parsetok.o Parser/tokenizer.o"
	PEGEN_HEADERS = "\"
	PEGEN_OBJS = "\"
	PGO_PROF_GEN_FLAG = "-fprofile-generate"
	PGO_PROF_USE_FLAG = "-fprofile-use -fprofile-correction"
	PLATLIBDIR = "lib"
	POBJS = "\"
	POSIX_SEMAPHORES_NOT_ENABLED = "0"
	PROFILE_TASK = "-m test --pgo"
	PTHREAD_KEY_T_IS_COMPATIBLE_WITH_INT = "1"
	PTHREAD_SYSTEM_SCHED_SUPPORTED = "1"
	PURIFY = ""
	PY3LIBRARY = ""
	PYLONG_BITS_IN_DIGIT = "0"
	PYTHON = "python"
	PYTHONFRAMEWORK = ""
	PYTHONFRAMEWORKDIR = "no-framework"
	PYTHONFRAMEWORKINSTALLDIR = ""
	PYTHONFRAMEWORKPREFIX = ""
	PYTHONPATH = ""
	PYTHON_FOR_BUILD = "./python -E"
	PYTHON_HEADERS = "\"
	PYTHON_OBJS = "\"
	PY_BUILTIN_HASHLIB_HASHES = ""md5,sha1,sha256,sha512,sha3,blake2""
	PY_BUILTIN_MODULE_CFLAGS = "-Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -std=c99 -Wextra -Wno-unused-result -Wno-unused-parameter -Wno-missing-field-initializers -Werror=implicit-function-declaration -fvisibility=hidden -fprofile-use -fprofile-correction -I./Include/internal -I. -I./Include -DPy_BUILD_CORE_BUILTIN"
	PY_CFLAGS = "-Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall"
	PY_CFLAGS_NODIST = "-std=c99 -Wextra -Wno-unused-result -Wno-unused-parameter -Wno-missing-field-initializers -Werror=implicit-function-declaration -fvisibility=hidden -fprofile-use -fprofile-correction -I./Include/internal"
	PY_COERCE_C_LOCALE = "1"
	PY_CORE_CFLAGS = "-Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -std=c99 -Wextra -Wno-unused-result -Wno-unused-parameter -Wno-missing-field-initializers -Werror=implicit-function-declaration -fvisibility=hidden -fprofile-use -fprofile-correction -I./Include/internal -I. -I./Include -DPy_BUILD_CORE"
	PY_CORE_LDFLAGS = ""
	PY_CPPFLAGS = "-I. -I./Include"
	PY_FORMAT_SIZE_T = ""z""
	PY_LDFLAGS = ""
	PY_LDFLAGS_NODIST = ""
	PY_SSL_DEFAULT_CIPHERS = "1"
	PY_SSL_DEFAULT_CIPHER_STRING = "0"
	PY_STDMODULE_CFLAGS = "-Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -std=c99 -Wextra -Wno-unused-result -Wno-unused-parameter -Wno-missing-field-initializers -Werror=implicit-function-declaration -fvisibility=hidden -fprofile-use -fprofile-correction -I./Include/internal -I. -I./Include"
	Py_DEBUG = "0"
	Py_ENABLE_SHARED = "0"
	Py_HASH_ALGORITHM = "0"
	Py_TRACE_REFS = "0"
	QUICKTESTOPTS = "-x test_subprocess test_io test_lib2to3 \"
	READELF = "readelf"
	RESSRCDIR = "Mac/Resources/framework"
	RETSIGTYPE = "void"
	RUNSHARED = ""
	SCRIPTDIR = "/share/apps/python/3.9.6/lib"
	SETPGRP_HAVE_ARG = "0"
	SGI_ABI = "@SGI_ABI@"
	SHELL = "/bin/sh"
	SHLIBS = "-lcrypt -lpthread -ldl  -lutil -lm"
	SHLIB_SUFFIX = ".so"
	SHM_NEEDS_LIBRT = "1"
	SIGNED_RIGHT_SHIFT_ZERO_FILLS = "0"
	SITEPATH = ""
	SIZEOF_DOUBLE = "8"
	SIZEOF_FLOAT = "4"
	SIZEOF_FPOS_T = "16"
	SIZEOF_INT = "4"
	SIZEOF_LONG = "8"
	SIZEOF_LONG_DOUBLE = "16"
	SIZEOF_LONG_LONG = "8"
	SIZEOF_OFF_T = "8"
	SIZEOF_PID_T = "4"
	SIZEOF_PTHREAD_KEY_T = "4"
	SIZEOF_PTHREAD_T = "8"
	SIZEOF_SHORT = "2"
	SIZEOF_SIZE_T = "8"
	SIZEOF_TIME_T = "8"
	SIZEOF_UINTPTR_T = "8"
	SIZEOF_VOID_P = "8"
	SIZEOF_WCHAR_T = "4"
	SIZEOF__BOOL = "1"
	SO = ".cpython-39-x86_64-linux-gnu.so"
	SOABI = "cpython-39-x86_64-linux-gnu"
	SRCDIRS = "Parser Parser/pegen Objects Python Modules Modules/_io Programs"
	SRC_GDB_HOOKS = "./Tools/gdb/libpython.py"
	STDC_HEADERS = "1"
	STRICT_SYSV_CURSES = "/* Don't use ncurses extensions */"
	STRIPFLAG = "-s"
	SUBDIRS = ""
	SUBDIRSTOO = "Include Lib Misc"
	SYSLIBS = "-lm"
	SYS_SELECT_WITH_SYS_TIME = "1"
	TCLTK_INCLUDES = ""
	TCLTK_LIBS = ""
	TESTOPTS = ""
	TESTPATH = ""
	TESTPYTHON = "./python"
	TESTPYTHONOPTS = ""
	TESTRUNNER = "./python ./Tools/scripts/run_tests.py"
	TESTTIMEOUT = "1200"
	TIMEMODULE_LIB = "0"
	TIME_WITH_SYS_TIME = "1"
	TM_IN_SYS_TIME = "0"
	TZPATH = "/usr/share/zoneinfo:/usr/lib/zoneinfo:/usr/share/lib/zoneinfo:/etc/zoneinfo"
	UNICODE_DEPS = "\"
	UNIVERSALSDK = ""
	UPDATE_FILE = "python ./Tools/scripts/update_file.py"
	USE_COMPUTED_GOTOS = "0"
	VERSION = "3.9"
	WINDOW_HAS_FLAGS = "1"
	WITH_DECIMAL_CONTEXTVAR = "1"
	WITH_DOC_STRINGS = "1"
	WITH_DTRACE = "0"
	WITH_DYLD = "0"
	WITH_LIBINTL = "0"
	WITH_NEXT_FRAMEWORK = "0"
	WITH_PYMALLOC = "1"
	WITH_VALGRIND = "0"
	X87_DOUBLE_ROUNDING = "0"
	XMLLIBSUBDIRS = "xml xml/dom xml/etree xml/parsers xml/sax"
	abiflags = ""
	abs_builddir = "/share/apps/src/python/3.9.6/Python-3.9.6"
	abs_srcdir = "/share/apps/src/python/3.9.6/Python-3.9.6"
	base = "/share/apps/python/3.9.6"
	datarootdir = "/share/apps/python/3.9.6/share"
	exec_prefix = "/share/apps/python/3.9.6"
	installed_base = "/share/apps/python/3.9.6"
	installed_platbase = "/share/apps/python/3.9.6"
	platbase = "/share/apps/python/3.9.6"
	platlibdir = "lib"
	prefix = "/share/apps/python/3.9.6"
	projectbase = "/share/apps/python/3.9.6/bin"
	py_version = "3.9.6"
	py_version_nodot = "39"
	py_version_short = "3.9"
	srcdir = "/share/apps/python/3.9.6/lib/python3.9/config-3.9-x86_64-linux-gnu"
	userbase = "/home/trpatel2/.local"

Definitely an interesting setup here:
CONFIG_ARGS = "'--enable-optimizations' '--with-ensurepip=install' '--prefix=/share/apps/python/3.9.6' '--disable-shared'"

You can see that the shared library was explicitly disabled when python was configured/built for this system.  I will have to do a little looking into pybind11 to see if it can possibly load the interpreter with exported  symbols ( e.g. RTLD_GLOBAL ).


[READY FOR REVIEW] Integrate backend w/ nymjs & Add script to populate posts/upvotes table with test data

This branch merged dan/spec 85cd06ab4135c98c842b5c7bbcffb2eba7f4e54e, so merging this PR implies merging #35 .
I initially planned to include the following two in this PR:

update the backend to adhere to the new spec (by using the latest nymjs).
populate the posts/upvotes table with test data.
populate the merkle tree table with actual public keys of Noun owners.

I got 1. done on this branch, but doing 2. and 3. at the same time was more complicated than I initially thought. So I decided to only do 3., since that will be sufficient to populate the frontend with state.
(I did get 2. partially done on this branch and there are some commits re that, but I will complete 2. on another branch.)
The script to populate posts/upvotes is in test_data/.

I checkout this repo and ran some commands:

pnpm frontend:dev (start the DB)
pnpm -F test_data run populate (populate the DB)
pnpm -F test_data exec prisma studio (set up the GUI)

Got a nice clean set up.

I also ran curl http://localhost:3000/api/v1/posts and got a JSON blob of 10 posts.
Changes I would like to make (in a separate PR):

Add the above commands to package.json scripts so we can more easily set up the dev environment.
Add a timer to see how long populating the test data takes.
Add the prisma generate command to the frontend:prepare field.

@cha0sg0d  Thanks for reviewing!
All 4 comments sound good!
I’ve been using TablePlus for inspecting the db, but the prisma studio also looks nice!


Make README.md more detailed.

I want to contribute to this project so could you make the README.md more understandable.

Thank for raising this issue @RishabhNaik , I will update the readme.md as soon as possible. 😀

Issue is Fixed ✔


Full audio is not playing from URL

I am trying to play audio from URL but it plays 3 to 4 seconds and stopped. Audio is almost 2 minutes long but it is playing only 3 to 4 seconds. Please let me know where is the issue. Thanks
Following is my Code implementation:
try {
val audio = Audio(mp3Url,  false)
audio.play()
} catch (e: Exception) {
e.printStackTrace()
}

I'm attempting to recreate the issue now.  Which platform did you encounter the issue on?  E.g. Android, iOS, JS

I'm attempting to recreate the issue now. Which platform did you encounter the issue on? E.g. Android, iOS, JS

Ok Thanks. it is occurring on ios emulator

I've been playing around for a few minutes, and from what I can tell, it's because the AVPlayer (which is overkill for audio playback) is running on the main thread.  Here's an example of one of the errors I got while tinkering:
[CFNetwork] __delegate_identifier__:Performance Diagnostics__:::____message__:Synchronous URL loading of https://dare.wisc.edu/wp-content/uploads/sites/1051/2008/11/MS072.mp3 should not occur on this application's main thread as it may lead to UI unresponsiveness. Please switch to an asynchronous networking API such as URLSession.

The simple answer is to instead use "stateful" loading of the player.  In version 0.1.6, I'm going to add it to the documentation and switch the player to "AVAudioPlayer" to decrease latency and computational requirements.
Here's an example of how you could load a larger audio file in compose without the risk of it playing before fully loaded:
// Other dependencies are omitted for brevity
import app.lexilabs.basic.sound.Audio
import app.lexilabs.basic.sound.AudioState
import app.lexilabs.basic.sound.ExperimentalBasicSound

val audioPlayer = Audio()
val audioState by audioPlayer.audioState.collectAsState()

Button(onClick = {
    audioPlayer.url = "https://dare.wisc.edu/wp-content/uploads/sites/1051/2008/11/MS072.mp3"
    when (audioState) {
        is AudioState.NONE -> audioPlayer.load()
        is AudioState.READY -> audioPlayer.play()
        is AudioState.ERROR -> println((audioState as AudioState.ERROR).message)
        is AudioState.PAUSED -> audioPlayer.play()
        is AudioState.PLAYING -> audioPlayer.pause()
        else -> { /** DO NOTHING **/ }
    }
}) {
    when (audioState) {
        is AudioState.ERROR -> Text("Error")
        AudioState.LOADING -> Text("Loading")
        AudioState.NONE -> Text("None")
        AudioState.READY -> Text("Ready")
        AudioState.PAUSED -> Text("Paused")
        AudioState.PLAYING -> Text("Playing")
    }
}

Please let me know if this works for you.

Resolved as of v0.1.6


Merge duplicated linear updater parameters.

Additionally to my review comments above, if we ever manage to implement a system that detects if parameters are unused, it would be better for the shared parameter structure to not contain parameters unless they are used by all updaters. Otherwise we will detect that the parameter has been initialised in the parameter struct but the algorithm never uses it.

@RAMitchell

have a secondary parameters structure in each algorithm with more specific parameters

Agree.  I splited top_k out of LinearTrainParam for coordinate descent.  For other part of XGBoost, simply grepping the source code should be able to tell the uniqueness of parameters.  n_gpus and gpu_id should be removed in once #3984 is sorted out.

if we ever manage to implement a system that detects if parameters are unused

Yes, we will have that eventually.  My plan is we put the InitAllowUnknown from dmlc::Parameter into good use.   This method returns all parameters that are not known to that specific dmlc::Parameter.  We then pass it to other components.  One extra effort is we need to make sure future PR doesn't introduce duplicated parameters.  A simple test by parsing XGBoost's code based looking for DMLC_DECLARE_FIELD and DMLC_DECLARE_ALIAS should be able to get the job done.  The only blocker is the binary format, which copies some parameters like num_class from other places.  But I'm optimistic about that.

LGTM. It might be nice if we could use one parameter struct as a base class for another so then we end up with only one struct in the updater. I briefly tried this but it seems unlikely this would work without significant modification of the DMLC parameter manager. So let's just stick with having to two structs per updater.

@RAMitchell Interesting.  I tried that too.  dmlc::Parameter lets parent class inherit child class, which makes thing a little bit tricky.


To establish Continuous Integration for the project

Opt for one of the best cloud-based CI;
Come up with a content of configuration file;
It is needful to build the entire project rather than scattered modules;
Add badge into readme.md.

Accomplished successfully.


Workflow Component : Analysis and report generation

Outputs produced in Energy minimization with Psi4 (QM), OpenMM (MM) #12 should be directly consumable via an entry-point in openff.benchmark.geometry_optimization. We need the following included for each ID from Identifier assignment #8:

Relative energies (E_MM - E_QM)
Geometry comparison (RMSD or TFD, MM vs. QM)

Existing implementations should be drawn from benchmarkff. Where implementations are dependent on OpenEye Toolkit, alternatives must be put in place.

Note for outputs from #12: inputs to this step should SDF files with energies given as SDF tags (key-value); make it a string. Should be " ".


Added NetworkConfigurationDiagnostic rest API + example

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Can one of the admins verify this patch?

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-python

Automation for azure-sdk-for-node

Automation for azure-sdk-for-java

Automation for azure-sdk-for-go

Sorry, was the wrong tab, I never meant to close/open the PR :/

@irrogozh  please don't forget to merge to August branch


7.2.5 Global Sampler

https://pbr-book.org/3ed-2018/Sampling_and_Reconstruction/Sampling_Interface#GlobalSampler

Done with Halton Sampler


“Ok” should be “OK"

The alert when you click the ⓧ  button has a button labeled “Ok” with a lowercase k. That’s incorrect — it should always be spelled “OK”, per Apple’s Style Guide:
https://help.apple.com/applestyleguide/#/apsg9a401e4f

TIL; I've been wondering about this for a long time now.
Thanks @gruber! (I'm a regular DF reader too btw--great stuff.)


tweak listable visit API

Instead of always going via visit_slice, a visit_primitive_slice method
is added. Primitive slices go via there. Non-primitive slices call
visit_item.

Some listable impls are using visit_value instead of visit_item, so I think you will need to update them.
https://github.com/tokio-rs/valuable/blob/74a2b672f842a237f85f318c5812d1e1848d9100/valuable/src/listable.rs#L94-L98

I removed visit_item in favor of calling visit_value which resolves the issue @taiki-e mentioned. Thanks!


Revert "Revert "Wake up rcs when pods get DeletionFinalStateUnknown t…

…ombstones""
Looks like this had nothing to do with us leaking routes. Rerunning e2e.

e2e passed except for a PD test which seems unrelated: https://github.com/GoogleCloudPlatform/kubernetes/issues/7972
@rjnagal (on call) can we get this in, or would you like a re-review?

Will merge when the current e2e run finishes.

LGTM


Add compatibility with TerraFirmaCraft

https://www.curseforge.com/minecraft/mc-mods/terrafirmacraft
Please add compatibility with at least the 1.20.1 version.  Thanks!

Implemented in version 1.3.0

Thank you!


No out animation

Hello,
I would like to have the same animation I see on the demo page, when settings:
fadeInLeft, sequence
fadeOutLeft, reverse
But I just see the IN animation. The out never starts, and the JS console is just silent. Can you help me?

Lorem ipsum dolor sit amet, consectetur adipisicing elit.

hey @CarloMartini,
The out effects are only run as a way to transition to the next in effect. You can use empty text as the next transition.

Some Title

https://stackoverflow.com/a/17428498/1249098


Vector2 doesn't contains "normalized" method in the C# Pong example. (Mono build)

W10, Godot Engine 3.0 beta-1, Nvidia 1050 Ti in a Lenovo y520 i7 7700HQ laptop (8gb Ram)
Trying to run C# example and running. Error thrown in line 31 of Paddle.cs:
  ball.direction = new Vector2(ballDir, (float) new Random().NextDouble() * 2 - 1).normalized();

It should be PascalCase

Yes, the demo should be fixed.

Fixed by https://github.com/godotengine/godot-demo-projects/commit/296da279ea8d2c2d0b8bc1ae644af0491d35fcfa.


[KYUUBI #3124] [Subtask] DorisSQLEngine - Shaded necessary dependency to kyuubi-jdbc-engine_**.jar

Why are the changes needed?

close https://github.com/apache/incubator-kyuubi/issues/3124#issue-1315942800
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Codecov Report

Merging #3125 (bfda89c) into master (b0685f9) will decrease coverage by 0.06%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #3125      +/-   ##
============================================
- Coverage     51.34%   51.27%   -0.07%
  Complexity        6        6
============================================
  Files           458      458
  Lines         25389    25388       -1
  Branches       3536     3536
============================================
- Hits          13036    13018      -18
- Misses        11111    11128      +17
  Partials       1242     1242

Impacted Files
Coverage Δ

...client/exception/RetryableKyuubiRestException.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../org/apache/kyuubi/client/RetryableRestClient.java
48.78% <0.00%> (-24.40%)
:arrow_down:

...main/java/org/apache/kyuubi/client/RestClient.java
82.75% <0.00%> (-3.45%)
:arrow_down:

...rg/apache/kyuubi/ctl/cmd/log/LogBatchCommand.scala
80.00% <0.00%> (-2.00%)
:arrow_down:

...ache/kyuubi/operation/KyuubiOperationManager.scala
80.82% <0.00%> (-1.37%)
:arrow_down:

.../org/apache/kyuubi/operation/KyuubiOperation.scala
68.91% <0.00%> (-1.36%)
:arrow_down:

...a/org/apache/kyuubi/service/TFrontendService.scala
91.17% <0.00%> (-0.30%)
:arrow_down:

...ubi/engine/spark/SparkTBinaryFrontendService.scala
82.89% <0.00%> (-0.23%)
:arrow_down:

...g/apache/kyuubi/operation/BatchJobSubmission.scala
77.63% <0.00%> (ø)

...in/scala/org/apache/kyuubi/config/KyuubiConf.scala
97.34% <0.00%> (+0.09%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us.


make crud store more secure and more efficient

          1 Error

:no_entry_sign:
Please include a CHANGELOG entry.
You can find it at CHANGELOG.md.

  Generated by :no_entry_sign: Danger


In the sence of image recognize. tps of simple_tensorflow_serving not very well ,below 10.

the test pic is about 1160*640

It may be the problem of the complex of you model.
Can you try to inference one image with the pure TensorFlow Session.run()?

Just use Session.run.The model is mobile-SSD-FON. But，Inference machine uses CPU model and  It has 64 cores


Error in cropping the picture

Hello,
I Have the same issue as issue #43
I'm using the Nuget package in my application so will not be able to add the work around (mentioned in the issue discussion) myself.
so my question is: When will the new version (1.2.6) will be released ?

Hi Boxiu,
Unfortunately I still have the same issue even after the upgrade to version 1.2.6

Hi @SarahFathy , seems I've made a mistake while using preprocessor. Please try v1.2.7.
Feel free to contact me if the issue still occurs.

Hi @Chronostasys,
It works fine now after upgrading to v1.2.7.  Thank you so much.
Have a great day!


Setup CI to automatically run tests and build container images

We don't have a CI setup yet.
Let's use the GitHub Actions to push images to the GitHub container registry.

Closed via #12


Non Flight Apps

I'm trying to build a RF communication app and trying to reference other app codes. However, I could find the apps in cFS repository are non flight applications.
What makes them to become a non flight purpose? Is it because it doesn't have RF system?

I think it is a liability thing. Every flight system is different and you would need to configure the app for it and make sure it is a fit for your need.

It has been our experience that RF communications is very unique from one
mission to the next.  Whether it is due to the transceiver hardware,
multiple antennas, encryption, data rates, or how the hardware is attached
to the spacecraft bus.  Some efforts have been made recently to at least
separate the protocol processing (e.g. - CCSDS standards) from the hardware
interface but that is not always as simple as it sounds either because
special operational circumstances seem to always pop up.
On Wed, Jul 24, 2024 at 12:19 PM Jaehyun Park @.***>
wrote:

I'm trying to build a RF communication app and trying to reference other
app codes. However, I could find the apps in this code are non flight
applications.
What makes them to become a non flight purpose? Is it because it doesn't
have RF system?
—
Reply to this email directly, view it on GitHub
https://github.com/nasa/cFS/issues/785, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKJGI2E7OJNFGU4GPGIVKETZN7HZBAVCNFSM6AAAAABLM2NFOWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQZDOOJZHA4DMNY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Closing issue. Please continue in discussions.


does no show all the items in the list

Describe the bug
When displaying a large number of items, scrolling at the bottom of the scroll element does not reach the end of the list
Your minimal, reproducible example
https://codesandbox.io/s/amazing-saha-f0dqsh
Steps to reproduce

Go to the default fixed example at https://tanstack.com/virtual/v3/docs/examples/react/fixed
Edit scr/main.tsx, and change the amount virtualizer option from 10,000 to 1,000,000
Scroll to the bottom of the list view in the browser
Notice the last visible item index is #958,697

Expected behavior
The last index should be 999,999, not 958,697. Not all items are being displayed in the list.
How often does this bug happen?
Every time
Screenshots or Videos

Platform
tested on windows 11, on edge Version 103.0.1264.71 (Official build) (64-bit)
tanstack-virtual version
3.0.0-beta.14
TypeScript version
No response
Additional context
No response
Terms & Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

Hello! I think this is not a tanstack-virtual issue. There is more explaination on react-window/virtualized's discussion linked here
https://github.com/bvaughn/react-window/issues/108
https://github.com/bvaughn/react-virtualized/issues/193#issuecomment-211467531
Try making the size of each row from 35px -> 10px and you will see all 1 million rows :D
TLDR: It's a browser limitation.

Indeed. This is a limitation on max element size.


Refactor environment variables to be more concise

Fix #36
Heads-up: this PR depends on PR https://github.com/atlanticwave-sdx/sdx-continuous-development/pull/109
Description of the change

Changing the approach from calculating OXP_NAME, OXP_URL and SDXLC_URL from OXPO_ID to a more simple approach where environment variables will be provided with those values (no calculation needed)

The initial setup scattered environment variables across various files, including the Docker Compose files, making the system configuration complex and more challenging to maintain. To enhance our configuration management and improve codebase clarity, we proposed consolidating all environment variable values into a single.env file and reorganizing hardcoded values within the Docker Compose files.
Goals:
Centralize Configuration: Aggregate all environment variables into one.env file to streamline configuration changes and improve visibility.
Clarify Docker Compose Files: To maintain clarity and organization, move hardcoded values from Docker Compose files to the.env file or appropriately document them.
Tasks:

Audit all existing configuration files to identify and list all current environment variables.
Create a.env file: Develop a comprehensive.env file that includes all necessary environment variables, appropriate default values, and comments for clarification.
Modify Docker Compose Files: Refactor Docker Compose files to reference the.env file instead of containing hardcoded values. Ensure all references are correctly linked and functional.

Documentation Update: Update all relevant documentation to reflect the new configuration strategy and provide guidelines on managing and updating the.env file.
Testing: Thoroughly test the updated configurations in various environments to ensure no functional compromises.
Expected Outcome: This reorganization will lead to a more maintainable and organized codebase, making it easier for developers to update and manage environment settings without navigating multiple files.
Additional Notes: This task requires careful coordination with the development team to ensure that changes do not disrupt existing functionalities. All team members must update their local development setups after implementation according to the new guidelines.

The initial setup scattered environment variables across various files, including the Docker Compose files, making the system configuration complex and more challenging to maintain. To enhance our configuration management and improve codebase clarity, we proposed consolidating all environment variable values into a single.env file and reorganizing hardcoded values within the Docker Compose files. Goals:
Centralize Configuration: Aggregate all environment variables into one.env file to streamline configuration changes and improve visibility.
Clarify Docker Compose Files: To maintain clarity and organization, move hardcoded values from Docker Compose files to the.env file or appropriately document them.
Tasks:

Audit all existing configuration files to identify and list all current environment variables.
Create a.env file: Develop a comprehensive.env file that includes all necessary environment variables, appropriate default values, and comments for clarification.
Modify Docker Compose Files: Refactor Docker Compose files to reference the.env file instead of containing hardcoded values. Ensure all references are correctly linked and functional.

Documentation Update: Update all relevant documentation to reflect the new configuration strategy and provide guidelines on managing and updating the.env file. Testing: Thoroughly test the updated configurations in various environments to ensure no functional compromises.
Expected Outcome: This reorganization will lead to a more maintainable and organized codebase, making it easier for developers to update and manage environment settings without navigating multiple files.
Additional Notes: This task requires careful coordination with the development team to ensure that changes do not disrupt existing functionalities. All team members must update their local development setups after implementation according to the new guidelines.

Hi @lmarinve thanks for you comment! Is there any specific adjustment you need me to apply? This PR is not related to the actual docker compose or .env files. I'm a bit confused with your comment.


Two effects at once not working?

This may not be a bug but rather my lack of experience with hooks, but I would expect the following to work with dom-augmentor (it does work with React):

// Some hook that sets state when some external callback fires
const usePlus = () => {
  const [ state, setState ] = useState(0);
  const result = useRef(state);
  useEffect( () => {
    console.log("plus effect");
    const handler = () => setState(++result.current);
    document.querySelector(".plus").addEventListener("click", handler);
    return () => {
      console.log("plus cleanup");
      document.querySelector(".plus").removeEventListener("click", handler);
    };
  }, []);
  return state;
};

// The same as usePlus() above
const useMinus = () => {
  const [ state, setState ] = useState(0);
  const result = useRef(state);
  useEffect( () => {
    console.log("minus effect");
    const handler = () => setState(++result.current);
    document.querySelector(".minus").addEventListener("click", handler);
    return () => {
      console.log("minus cleanup");
      document.querySelector(".minus").removeEventListener("click", handler);
    };
  }, []);
  return state;
};

const Content = () => $(() => {
  const plus = usePlus();   // this has no effect at all
  const minus = useMinus(); // this works
  return html`
    <div>
      +${ plus } / -${ minus } (${ plus - minus })
    </div>
  `;
});

render(document.querySelector(".result"), Content());

The second hook always works while the first one never even registers the click event. Is this intentional? If so, how would I use multiple side effects in my Content component?

can you please try useState(0, {async: true}); in both cases and tell me how it goes?

Does not change anything.

It should just work now 👋

Works like a charm, thank you!

Thanks, and BTW, you are basically reproducing neverland by your own, maybe worth having a look there ;-)

Yeah, but then I'd have to wrangle with TypeScript definitons again, gonna procrastinate on this for now.


improve error output

does this error include the current post slider throwing the error? if not it should give enough information so the user knows what file to check for malformed syntax.

fixed in a8bfb9a


ts strict part 8: actions-tsconfig-constants

Please see https://github.com/keybase/client/pull/18383 for an overview

@keybase/react-hackers this is ready


Restructing code to use encypt and decypt function in other sdk's

Motivation and Context

Restructing code to use encypt and decypt function in other sdk's

Jira Link:
Description

Restructing code to use encypt and decypt function in other sdk's

How has this been tested?
By running test cases.
Screenshots (if appropriate):

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[ ] My code follows the code style of this project. (run lint)
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Please update the cocoapods version


Need help for the format of date

Hi node-mysql people can I ask some help,
I have this result for my inner join query.my problem is that the date it display like this
dateregister: Thu Feb 05 2015 16:02:32 GMT+0800 (Taipei Standard Time)
how do I display like this example which is in my table
dateregister: 2015-02-02 23:43:49
Thank you in advance.
    connection.query(options,function(err, results) {

                if(err){
                    console.log(err);
                }
                console.log('result is: ', results);
            });

If you would like to see the date in the exact string format that MySQL sends instead of the format that JavaScript uses, you can use the dateStrings option (from https://github.com/felixge/node-mysql#connection-options):
var connection = mysql.createConnection({
  dateStrings: true,
  // the rest of your connection options here
});

@dougwilson ,
Thank you it works now :)


Operator controller allows old TLS versions

Our vulnerability scanners raised an issue because, the operator controller allows TLS v1.0/1.1 on port 9443.
Please allow only TLS 1.2, because of the legacy versions have many vulnerabilities.

To clarify, did you mean port 8443?  If so, this is the https://github.com/brancz/kube-rbac-proxy.  We currently run with 0.8.0.  In the latest version, 0.11.0, they have an option to specify the TLS version (--tls-min-version).  So, on the surface, it seems reasonable that we can upgrade and/or use this option.

I mean this port from the kubernetes deployment resource:
        ports:
        - containerPort: 9443
          name: webhook-server
          protocol: TCP

Is it chnaged after 1.2.0?

No, it is still 9443.  I see the port you are asking about.
Unfortunately, I don't see anything that we can be done at this time.  The operator inherits this functionality from  https://github.com/kubernetes-sigs/controller-runtime.  We are on an older version (0.7.2), But, even in the current release (0.11.0), it still doesn't allow the TLS to be configured.  There have been a few PRs opened to try and address this but none of them have got in yet (i.e. https://github.com/kubernetes-sigs/controller-runtime/pull/1620)

Thanks! We will ping those PRs.

Turns out there may be a way to set the minimum TLS version now.  There was a merged PR that set the minimum TLS when starting the webhook (https://github.com/kubernetes-sigs/controller-runtime/pull/1548).  However, our operator doesn't call the function that was changed directly.  There are a few layers of abstraction in between.  So, what is missing is how to configure that from the operator.  The community for the controller-runtime has had various proposals to allow this, but nothing is finalized.  PR 1620 referenced above is an example.  Another one is https://github.com/kubernetes-sigs/controller-runtime/issues/852 looks the most promising based on recent activity.
In the mean time, I believe I can set this in our operator still.  It will be a little hacky but it should be okay for now until they settle on a way to properly expose this.
I'll open a PR for this shortly.

Thanks @spilchen !


unable to generate collector using New-Collector.ps1

collector-generator.exe missing is the error

Complied generate-collector.go to collector-generator.exe .. It is working


Update circe-generic, circe-literal, ... to 0.14.10

About this PR
📦 Updates

io.circe:circe-generic
io.circe:circe-literal
io.circe:circe-parser
io.circe:circe-testing

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

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

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "io.circe" }
}]

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

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 0.00%. Comparing base (64c8312) to head (44b0a0e).
Report is 1 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@          Coverage Diff          @@
##            main    #372   +/-   ##
=====================================
  Coverage   0.00%   0.00%
=====================================
  Files          1       1
  Lines         16      16
  Branches       1       1
=====================================
  Misses        16      16

Flag
Coverage Δ

2.13.14
0.00% <ø> (ø)

temurin@11
0.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Why all examples include only Next.js, and so simplistic and few examples with CI/CD?

Describe the feature you'd like to request
I read the documentation and the hype going on about the turborepo.
My concern is that documentation is not very explicit and detailed and the examples involve only Next.js framework presets.
I do understand that Vercel now is behind Next.js and Turborepo, and that Next.js is an awesome framework but...
Describe the solution you'd like
I am wondering, (i know it's possible of course). Why don't you post examples for some services/app which are framework agnostic, or minimalistic/core?
Let's say a preset with express server.
Also, as a new tool which tries to bring innovation and convince us to use, can you show us some examples with CI/CD. A very basic example which we can base of, how do you tackle the monorepo approach with turborepo.
Describe alternatives you've considered
Extend the documentation about examples, include presets other than Next.js.
Also, extend the documentation about CI/CD.

I would be curious to know what specific issues are you running into.  As an outside adopter, turbo is very framework agnostic and I've had very few concerns with documentation during early adoption.  Granted I've come across a few issues/limitations/enhancements/bugs as well as a few documentation clarification that is needed but I don't consider any of them blockers but merely highlight the potential and impact turbo will have to the community once addressed.  We've been successful in using it in production with over 200+ packages, driven by a CI/CD pipeline (and we are not using Next.js)
It would be good to be more explicit about the issues / questions you are running into/facing.  From what i've seen the developers and the community seem very receptive to questions/issues being reported.

Hello @sppatel, actually i have no problems, and yesterday just started testing with core Express server: https://gitlab.com/erkand-imeri/turborepo-gitlab
It works except for those eslint-next warnings which i might have a look into it.
It's just a question at why all examples are being shown with Next.js (actually i think this is a pretty cool framework).


Xml writer

Extended XML writer to write camera timelines and cameras.

Look great, please process the code review comments and then we can merge this.

Nice work, if the checks pass we can merge

Looks good!


"Fire-and-forget" tasks (without results)

Is there a way to create tasks that will not store any results to be received? I want to create fire-and-forget tasks whose results are not used, and therefore I want them not to be accumulated.

See #22 for a (stalled) implementation.

Thanks!


Version 3.8

? no real code additions have been made.

Version 3.7 does not reflect current state of the repo. README states that you can use HtmlFormatter yet class is not available

Because 3.8 hasn't been released yet. Please when you open a PR please describe here what you like to achieve.
I assume you want a new release?

Yes


remove ios13 beta status from themes pages (4.x, 3.x)

This is all, just remove the text (currently in beta) from iOS 13 references on the themes pages

Thanks for the PR!


Is this based on Chaos Monkey of Netflix/SimianArmy?

Hi Jesse,
Excuse me, is the image kubernetes-pod-chaos-monkey  based on Chaos Monkey of Netflix/SimianArmy?
I read through the src and if my understanding is right I think you implement it using k8s kubectl command. Right? But I am not sure about it as give it the name end up with 'chaos-monkey'.
In fact I am looking the docker image of Chaos Monkey ( Netflix/SimianArmy) used for K8s cluster.
Thank you!

No, this project is an interpretation of the Netflix Chaos Monkey project for Kubernetes. When running, this project deletes random pods running in a Kubernetes cluster similar to how Netflix's project terminates EC2 instances. Sorry for the confusion!


Fix shapenet

Ensure ShapeNet dataset works well when entire dataset is downloaded from source.

Added cache-dir argument to allow users to specify where converted representations are cached.
Adapted tests and added decorators to automatically skip tests if dataset is not found at default location.

Great work, can you specify in the PR description on what platform you tested the examples and with what arguments ?

LGTM, can we assume that examples will be working once #26 is correctly using the name of datasets and merged ? Or are there some additional tasks to do ?


New dynamic limiter for very wide dynamic ranges

Well that was a fun exercise! This time I actually think I know what I'm doing.
The current dynamic limiter was an amateur attempt that worked within a limited range and first Rust code I ever wrote. This time I took a article from the Journal of the Audio Engineering Society [1] and wrote a fresh implementation of the most recommended variant (feed-forward in the log domain with a smooth, decoupled peak detector).
So far it seems to work beautifully, including the tracks with wide dynamic range in the linked issue. Would be nice if some of you could give this a spin on various genres and let me know how it goes.
I purposely changed the field names to signal developers downstream that some of these fields now hold values in a different unit. Before in 0.2.0 this caused distorted audio for some other applications and I'd like to prevent that this time.
Closes: #934
[1] Giannoulis, D., Massberg, M., & Reiss, J.D. (2012). Digital Dynamic Range Compressor Design—A Tutorial and Analysis. Journal of The Audio Engineering Society, 60, 399-408

I fond another track.
[2022-01-12T13:50:58Z INFO  librespot_playback::player] <Danse Macabre, Op. 40,R.171> (442693 ms) loaded
[2022-01-12T13:50:58Z WARN  librespot_playback::player] This track will at its peak be subject to 7.44 dB of dynamic limiting.
[2022-01-12T13:50:58Z WARN  librespot_playback::player] Please lower pregain toavoid.
[2022-01-12T13:50:58Z DEBUG librespot_playback::player] Normalisation Data: NormalisationData { track_gain_db: 5.923416, track_peak: 0.94552505, album_gain_db:1.1973114, album_peak: 0.9883812 }
[2022-01-12T13:50:58Z DEBUG librespot_playback::player] Calculated Normalisation Factor for Track: 197.77%

All sounds good. I like it. Thank you.

Great to hear. One more report would be great for me to merge this with confidence.

I will give it a test. There are a couple tracks that I know of that distort.

So far so good. The entire Bush, Sixteen Stones album was pretty bad with the old limiter
( https://open.spotify.com/album/5IJm0boSQuEBLiYNZJKV2Y?si=5q4kkdqFRWOFdQatWWUVdQ ) It's honestly not much better with the new limiter but it's at least somewhat tolerable. Even without a limiter it's really bad. It's a fuzzy, squished hot mess full of inter-sample peaks I'd guess. A victim of the loudness wars and "more me" mixing.

I do notice that it uses a little bit more CPU though. Maybe 2%-ish more on my Raspberry Pi 4. That should still be fine on a Pi Zero I would think though. It should still be under 30%.

So far so good. The entire Bush, Sixteen Stones album was pretty bad with the old limiter
( https://open.spotify.com/album/5IJm0boSQuEBLiYNZJKV2Y?si=5q4kkdqFRWOFdQatWWUVdQ ) It's honestly not much better with the new limiter but it's at least somewhat tolerable. Even without a limiter it's really bad. It's a fuzzy, squished hot mess full of inter-sample peaks I'd guess. A victim of the loudness wars and "more me" mixing.

Oh man that's definitely a throwback! Can't remember much often I played that album back in the days. A lot.
However with the default pregain of 0.0 I don't think the dynamic limiter kicks in at all? The tracks indeed suffer from very low dynamic range. The average ReplayGain for these tracks is around -10 dB. The peaks then all stay under threshold.

I do notice that it uses a little bit more CPU though. Maybe 2%-ish more on my Raspberry Pi 4. That should still be fine on a Pi Zero I would think though. It should still be under 30%.

Yeah, that's quite possible. Though the code is short and sweet, there are more things going on now that the CPU has no intrinsics for. Like linear <> logarithmic conversions, twice for every sample.

Now that you mentioned it I do have some ideas to optimize this when we aren’t attacking or releasing a peak.

dce7944 is a little more efficient and hasn't broken anything right?

Yep, that cut it from about 2% to about 1%,lol!!!
LGTM
After you merge this and your --device fix I'll release a new version of Raspotify. I'm sure if there's any bugs they'll show themselves.

The tracks indeed suffer from very low dynamic range. The average ReplayGain for these tracks is around -10 dB.

I didn't read the logs but I want to say that Glycerine in track mode distorts?

I don't think so -- it's down -5.6 dB. If you mean that guitar, I do think that it clips but already in the recording and possibly even on the guitar amp. This is "Glycerine - Remastered" on "Sixsteen Stone (Remastered)": https://open.spotify.com/track/5buITai6eMzU8rJonMEI6e?si=962443be52484f34

dce7944 is a little more efficient and hasn't broken anything right?

Yep, that cut it from about 2% to about 1%,lol!!!

Well, like it said on the tin 😆 I'll take it.

After you merge this and your --device fix I'll release a new version of Raspotify. I'm sure if there's any bugs they'll show themselves.

For a final check maybe you can compare what Glycerine sounds like in an official Spotify client. On macOS, the official app sounds a little lower in volume, but the guitar no better.

After you merge this and your --device fix I'll release a new version of Raspotify. I'm sure if there's any bugs they'll show themselves.

👍

Testing on my Pi Zero shows CPU usage in the high teens to low 20's. So it's about what I expected. 1% increase on the Pi 4 and 5-10% on the Pi Zero. Not great but not a deal breaker. Still plenty of headroom. When the new API work becomes more complete I will test that on the Zero.

Wow! Thank you for this! I could never use the old dynamic limiter, because this song was always crackling:
[2022-01-16T16:19:01Z INFO  librespot_playback::player] Loading <Feel Like Going Home> with Spotify URI <spotify:track:0qMPttvKZkUXyDgNmZhKsY>
[2022-01-16T16:19:01Z DEBUG librespot_audio::fetch] File 8663bb953f40917e6c295a7e4ac96d06d0074ad2 already in cache
[2022-01-16T16:19:01Z DEBUG librespot_core::audio_key] new AudioKeyManager
[2022-01-16T16:19:01Z INFO  librespot_playback::player] <Feel Like Going Home> (292773 ms) loaded
[2022-01-16T16:19:01Z WARN  librespot_playback::player] This track will at its peak be subject to 7.47 dB of dynamic limiting.
[2022-01-16T16:19:01Z WARN  librespot_playback::player] Please lower pregain to avoid.
[2022-01-16T16:19:01Z DEBUG librespot_playback::player] Normalisation Data: NormalisationData { track_gain_db: 1.2700005, track_peak: 0.81324977, album_gain_db: 0.3600006, album_peak: 1.0166621 }
[2022-01-16T16:19:01Z DEBUG librespot_playback::player] Calculated Normalisation Factor for Track: 230.94%

Now the limiter is finally useful!

Glad to hear it’s appreciated ❤


WIP: Service catalog API resources finalizer token updates

A finalizer token should not be used unless paired with an actual controller that will remove it prior to object deletion.  In addition, the token must be in a domain for service catalog.  Service catalog may set a finalizer token on the associated kubernetes namespace to ensure that its resources take part in namespace lifecycle, but that is a future follow-on.
/cc @pmorie

i see we are using the finalizer token in the broker controller to do cascading deletion.   it seems like we should just be using the garbage collector for that scenario via ownerRef.  need to do some more investigation.  at minimum, we should not be using a "kubernetes" token ;-)

@derekwaynecarr it's more than cascading deletion - we need the token to finalize instances and bindings, which the user indicates we should do by deleting the resource.

@pmorie - ack.  I will keep the token for namespaced resources only , but make sure it is qualified uri

@derekwaynecarr I think there is some follow-up work here to enable the service-catalog specific finalizer token, yes? Can you create an issue for that work, and mention this PR in it?

@derekwaynecarr do we still need this?  Moving to 0.0.4 milestone.

Moving to the beta cycle, this is still in progress

@derekwaynecarr what is the status of this PR?

@arschles -- i need to find time to make sure we are not abusing finalizers.  i will get to it in next few days.

Moving to 0.1.0, as this is not yet finished

closed in favor of https://github.com/kubernetes-incubator/service-catalog/pull/894


[WIP] Add more unit tests

Pull Request Test Coverage Report for Build 900

0 of 0   changed or added relevant lines in 0 files are covered.
6 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-3.0%) to 68.148%

Files with Coverage Reduction
New Missed Lines
%

src/EconomicStrategy/EconomicStrategyHelpers.ts
1
93.75%

src/Actions/Helpers.ts
1
0.0%

src/Scanner/Scanner.ts
1
79.28%

src/Actions/Pending.ts
3
80.95%

Totals

Change from base Build 893:
-3.0%

Covered Lines:
413

Relevant Lines:
578

💛  - Coveralls


a little suggestion

Hi.
I'm new to this git and programming stuff, so please bear with me :)
if I query stocks I'm getting  22049 symbols from 9 exchanges. Since I'd love to have more  I fiddled a bit around and got your tool to get 28094 symbols from 66 exchanges.
All I had to do was in the ytd/SymbolDownloader.py  add " 'm' : 'all' " to params.
This now enables me to filter for stocks which are traded e.g. in Frankfurt which I find awesome ;)
dunno if you want to drop that line but I thought I'd share my idea (:
edith says: I'll try this branching and pull request stuff... let"s see...
edit2: I made a mistake. I was formerly pulling from de.finance.yahoo. Now back at finance.yahoo I get 105539 stocks from 69 exchanges. Still about 9k missing.

Thank you! I'll merge it right away when I get home.
And welcome to github
Sent using the GMX mail app
On 10/05/2017 at 01:41, istzustand wrote:

Hi.
I'm new to this git and programming stuff, so please bear with me :)
if I query stocks I'm getting  22049 symbols from 9 exchanges. Since I'd love to have more  I fiddled a bit around and got your tool to get 28094 symbols from 66 exchanges.
All I had to do was in the ytd/SymbolDownloader.py  add " 'm' : 'all' " to params.
This now enables me to filter for stocks which are traded e.g. in Frankfurt which I find awesome ;)
dunno if you want to drop that line but I thought I'd share my idea (:
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/Benny-/Yahoo-ticker-symbol-downloader/issues/31


/repair does not support modded items

/repair can't fix modded items yet like waterstone picaxes!

Requires a custom version, fixed in future update


use pytest instead of nosetest

nosetest is in maintenance mode, so we should switch to the more modern framework.

@tqchen if you add 'import topi' to test_codegen_llvm.py, and run it, it will failed. do you has any idea?

https://github.com/dmlc/tvm/pull/3595 should fix your issue.

@tqchen @kevinthesun can you guys help review?

Thanks @MarisaKirisame


A web interface for managing multiple bots for free!

Is your feature request related to a problem? Please describe.
Yes, PM2.io features a free web interface that has limited features, if you want more features, you will need to pay for it monthly or yearly($29 a month btw)

Its frustrating when there is limited features for pm2.io plus. Like people dont want to pay $39 a month for pm2.io for more features.  I want it be tf2-related, and has a same similiarity to pm2.io and its free.  There are examples like Bon's Config Generator for TF2-Autobot but that is a different topic.
Describe the feature you'd like
A interface without needing to install it(people without having to assume there are risky computer virus) , but instead a web interface. It has to be tf2-related like for example ZeusJunior's pricelist generator specifically for tf2-automatic(link), but you will need to install that.

Describe alternatives you've considered

app.pm2.io(but has limited features besides this suggestion)
Manually going to a sftp client on your computer , manually login, and then shutting down the bots.(For example WinSCP(Windows SFTP Software) or Filezilla)
Also there is steam chat but its best for individual bots rather than multiple.
Got any bounty as a reward for anyone fulfills your request?

Additional context

I've considered to add something like this to GUI ... but I'm not sure when I'll get back to GUI development


Refactor debian strategy construction

Can you tweak the PR name to mention something that is being refactored? you could also list out the changes in the commit/PR message so there's at least some context provided in the history.


MSBuildLocator 1.6.10

This is #213 plus a fix to disable package validation, which doesn't make sense for the source-built package (which deliberately changes TFs).

Roslyn - https://github.com/dotnet/roslyn/pull/70038
dotnet format - https://github.com/dotnet/format/pull/1957

@dibarbet - what version of dotnet is this intended to go into?

@dibarbet - what version of dotnet is this intended to go into?

I believe .net8 since that is what Roslyn main is targeting?

@dibarbet - what version of dotnet is this intended to go into?

I believe .net8 since that is what Roslyn main is targeting?

This will need to be manually backported to the release/8.0 branch.  This is currently blocking https://github.com/dotnet/installer/pull/17395

This will need to be manually backported to the release/8.0 branch. This is currently blocking dotnet/installer#17395

On it.

#215

I don't see a darc subscription defined for dotnet/format so I defined it and triggered it - https://github.com/dotnet/format/pull/1958

I didn't find a darc subscription defined for dotnet/format so I defined it and triggered it - dotnet/format#1958

Thanks - I just asked Matt and suggested the same.  I've rolled that update into https://github.com/dotnet/format/pull/1957 as it also needs to update the actual referenced version


wont create segments (i use 5:4)

pls help idk whats wrong

5:4 is not supported by crispy.
Either use 4:3 or 16:9 !


Scrap Insta Non followers

Description
Scrap the details of the users who are not following you but are followed by you
Technologies and Languages

python
javascript

Any other language and technology is welcomed
Aditional Work
Make a GUI for this

Hey! Can I give it a try?
Can you please assign this task to me?

Sure.


When model contains blob field, subsequent saves results in multiple GridFS records with duplicate names

I could be using the library incorrectly, but when updating a model with a blob field, additional records are created in the GridFs table with the same name. Seems like deleteBlobs with some logic around it should be called prior to saveBlobs in the Model save2 method.
@Test
public void subsequentSaveResultsInMultipleRecordsWithDuplicateNames() {
File originalImageFile = VirtualFile.fromRelativePath("/public/images/_avatar/default.png").getRealFile();
File newImageFile = VirtualFile.fromRelativePath("/public/images/_avatar/default-24x24.png").getRealFile();
Racer r = new Racer();
r.fullName = "Test User";
r.image = new Blob(originalImageFile, "image/png");
r.save();

r = Racer.find("fullName", "Test User").first();

assertNotNull(r);

r.image = new Blob(newImageFile, "image/png");
r.save();

String name = r.getBlobFileName("image");

DBObject queryObj = new BasicDBObject("name", name);
List<GridFSDBFile> list = MorphiaPlugin.gridFs().find(queryObj);

assertEquals(1,list.size());

}

bug confirmed. Thank you very much for report it this bug.

Fix looks good. Thanks for addressing it so quickly!