double free or corruption (out)

Hi there,
I get double free or corruption (out) every time I run pyoperon installed using wheels from the actions page. I don't get this error using the released packaged here on github, but that one is considerably outdated.
I've tried on two different linux machines (CentOS7 and arch-based Endeavour OS), with different python versions (3.9 and 3.11).
Any way I can help debug further?
Best,
M
PS: I can't access any artefact on the actions page older than November as they have expired.

Hi,
Could you share a small snippet of code to help reproduce this issue? What CPU are you running it on?
Also, is it possible to try building it yourself? For example,
micromamba env create -f environment.yml
micromamba activate pyoperon

export CC=clang
export CXX=clang++
bash script/dependencies.sh # install dependencies
python setup.py bdist_wheel -- --preset build-linux # build the wheel

Hi there,
The code is simple
from pyoperon.sklearn import SymbolicRegressor

so it has to do with the libraries and maybe compiler versions? I've tried on two different linux machines. One is an HPC workstation (CentOS7) with Intel Xeon Gold 5220, the other is my laptop (Endeavour up-to-date) with Ryzen 7 6800H. Both with very different environments.
I'm not using anaconda, could it be the issue? I'm trying to run the code on an HPC cluster without conda, and in general I don't use conda as it's a pain to transfer code across machines without it.
The problem does not occur with the wheels provided in the releases page of the repository.
I'll try to compile according to the instructions and get back with the result.

I am fairly certain this is a problem with conflicting assumptions about memory alignment (presumably because of a difference in compile flags) between our dll and one of its dependencies (probably operon itself).
I've always tested under conda or nix and have not encountered this issue.
I made a small change to the CI, can you try the new wheels?
We are using x86-64-v3 on linux, which should be widely supported.

I've tried the new wheels (I hadn't had the time to try to compile from scratch yet) I get a new error, which seems unrelated to the previous one
$ python run.py
Traceback (most recent call last):
  File "/home/mcromao/tmp/pyoperon-version-test/run.py", line 7, in <module>
    from pyoperon.sklearn import SymbolicRegressor
  File "/home/mcromao/tmp/pyoperon-version-test/venv/lib/python3.11/site-packages/pyoperon/__init__.py", line 4, in <module>
    from .pyoperon import *
ImportError: generic_type: cannot initialize type "GaussianLikelihoodEvaluator": an object with that name is already defined

Sorry, that was just a typo in the source code, fixed now. Can you try the latest wheel?

Hi again,
It seems like that was not the only case!
$ python run.py
Traceback (most recent call last):
  File "/home/mcromao/tmp/pyoperon-version-test/run.py", line 7, in <module>
    from pyoperon.sklearn import SymbolicRegressor
  File "/home/mcromao/tmp/pyoperon-version-test/venv/lib/python3.11/site-packages/pyoperon/__init__.py", line 4, in <module>
    from .pyoperon import *
ImportError: generic_type: type "PoissonLikelihoodEvaluator" is already registered!

Should be fixed now in 7bab9701bea64438cb87e3c867dd2f8cca3bc09d, thanks for the patience.

It's running! Nothing to apologise for, thank YOU for the patience :)


Added Dutch translations

I created Dutch translations for this extension. Maybe you want to include them?

Looks great, thanks!


Add scan option to build packages in subdirectories

Replaces #81
This PR implements a new top-level option, 'scan', which scans subdirectories, and builds any found packages. It uses the same options as build with a couple of additions: a per-package timeout, and a maximum number of packages.
I've been running variations of this for a few weeks now in a nightly Jenkins build of all ros2:iron packages, so the available output has been tweaked to focus on that environment.
It captures output from each package build in a file stdout.txt in the docs_build folder. Summary information is printed in the more typical console locations. Looking at the notes from #81, I believe this implements most of those requests, with the exception of the request to fail on first error. Plenty of existing packages have errors, so I don't really see the value of this if you are running a full distro. If you are only running a repository, it runs quickly enough that I don't see the value of that option either. I do include though a maximum number of packages options which is useful to limit time when testing. If you really want that feature, let's do that as a followup, it would not be very hard. But please state the use case.
On my system, if I set a -t 1 timeout then about a third of the test packages time out, which can give some idea of what error output looks like. So I can run rosdoc2 scan -p test -t 1 from the rosdoc2 directory as a simple test. Or you could do that on a repository with multiple packages instead.
I used colcon as requested, but I have some comments on that. First, the documentation on colcon that I could find is all from the perspective of using the resulting commands that are generated using colcon. I could find no hints of how to use it as a python library. Second, the code has multiple levels of abstraction, with key features being added through extensions. Examining the code for, say, colcon_core.package_discovery give no clue on what options are supported, as all of that is added in extensions. What extensions? I have no idea. Basically through trial and error and guesswork, I was able to discover that colcon-common-extensions give the functionality that I need, with --base-paths as the option I needed to set. Third, using colcon as a package discovery library requires 7 lines of obscure setup code. Yes this was partly written as a demo for me, but this is not at all the expectation one has when using library code. In summary, I would not recommend to anyone else that they attempt to use colcon as library code like this.

Here is the list of failed packages from a recent ros2:iron run of this with the default 15 minute timeout (this is a 10 year old i7 machine using a physical hard disk):
37 packages failed:
rviz_common: retval=1: RuntimeError Sphinx-build exited with return code '2'
azure_iot_sdks: retval=1: RuntimeError Failed to find a ROS package at given path 'rosindex/_plugins_data/checkout/azure-iot-sdk-c/github-Azure-azure-iot-sdk-c/azure-iot-sdk-c'
ecl_geometry: retval=1: RuntimeError Sphinx-build exited with return code '2'
rotconv: retval=1: RuntimeError Failed to find a ROS package at given path 'rosindex/_plugins_data/checkout/rot_conv_lib/github-AIS-Bonn-rot_conv_lib/rot_conv_lib'
proxsuite: retval=2: TimeoutError runtime 900.351 seconds
gazebo_plugins: retval=1: RuntimeError Sphinx-build exited with return code '2'
magic_enum: retval=1: RuntimeError Sphinx-build exited with return code '2'
avt_vimba_camera: retval=1: RuntimeError Sphinx-build exited with return code '1'
fastcdr: retval=1: RuntimeError Failed to find a ROS package at given path 'rosindex/_plugins_data/checkout/fastcdr/github-eProsima-Fast-CDR/fastcdr'
octomap-distribution: retval=1: RuntimeError Failed to find a ROS package at given path 'rosindex/_plugins_data/checkout/octomap/github-octomap-octomap/octomap'
mrpt2: retval=1: RuntimeError Sphinx-build exited with return code '2'
libcaer: retval=2: TimeoutError runtime 900.348 seconds
mrpt_path_planning: retval=1: RuntimeError Sphinx-build exited with return code '2'
vitis_common: retval=2: TimeoutError runtime 900.349 seconds
sm_multi_stage_1: retval=2: TimeoutError runtime 900.349 seconds
sm_pack_ml: retval=2: TimeoutError runtime 900.349 seconds
VRPN: retval=1: RuntimeError Failed to find a ROS package at given path 'rosindex/_plugins_data/checkout/vrpn/github-vrpn-vrpn/vrpn'
VISP: retval=1: RuntimeError Failed to find a ROS package at given path 'rosindex/_plugins_data/checkout/visp/github-lagadic-visp/visp'
urdfdom_headers: retval=1: RuntimeError Failed to find a ROS package at given path 'rosindex/_plugins_data/checkout/urdfdom_headers/github-ros-urdfdom_headers/urdfdom_headers'
nav2_costmap_2d: retval=1: RuntimeError Sphinx-build exited with return code '2'
ecl_containers: retval=1: RuntimeError Sphinx-build exited with return code '2'
sick_scan_xd: retval=2: TimeoutError runtime 900.347 seconds
robot_localization: retval=1: RuntimeError Sphinx-build exited with return code '2'
naoqi_driver: retval=1: RuntimeError Sphinx-build exited with return code '2'
ecl_manipulators: retval=1: RuntimeError Sphinx-build exited with return code '2'
pinocchio: retval=2: TimeoutError runtime 900.351 seconds
ecl_converters: retval=1: RuntimeError Sphinx-build exited with return code '2'
fastrtps: retval=2: TimeoutError runtime 900.357 seconds
geodesy: retval=1: RuntimeError Sphinx-build exited with return code '2'
ign_rviz: retval=1: RuntimeError Sphinx-build exited with return code '2'
cv_bridge: retval=1: RuntimeError Sphinx-build exited with return code '2'
camera_calibration: retval=1: RuntimeError Sphinx-build exited with return code '2'
transmission_interface: retval=1: RuntimeError Sphinx-build exited with return code '1'
ur_client_library: retval=1: RuntimeError Sphinx-build exited with return code '2'
IFM3D: retval=1: RuntimeError Failed to find a ROS package at given path 'rosindex/_plugins_data/checkout/ifm3d_core/github-ifm-ifm3d/ifm3d_core'
ign_rviz_plugins: retval=1: RuntimeError Sphinx-build exited with return code '2'
rmf_visualization_schedule: retval=1: RuntimeError Sphinx-build exited with return code '2'

I can look at the logs on docs_build, for example, for rviz_common to see that the error was:
Exception occurred:
  File "/rosdoc2/venv/lib/python3.10/site-packages/breathe/renderer/sphinxrenderer.py", line 334, in create
    cls, name = DomainDirectiveFactory.cpp_classes[args[0]]  # type: ignore
KeyError: 'property'

During the active run, the console (Jenkins) output looks like this excerpt:
21:53:08 Begin processing geometry2
21:53:13 Package joint_state_publisher_gui succeeded in 10.981 seconds
[rosdoc2_scan] [INFO] joint_state_publisher_gui successful (1412/1440)
21:53:13 Begin processing system_modes_msgs
21:53:17 Package geometry2 succeeded in 8.858 seconds
[rosdoc2_scan] [INFO] geometry2 successful (1413/1440)
21:53:17 Begin processing mola_test_datasets
21:53:31 Package system_modes_msgs succeeded in 17.519 seconds
[rosdoc2_scan] [INFO] system_modes_msgs successful (1414/1440)
21:53:31 Begin processing ament_cmake_test
21:53:32 Package mola_test_datasets succeeded in 14.247 seconds
[rosdoc2_scan] [INFO] mola_test_datasets successful (1415/1440)

A few notes on the code:

I had to abandon running sphinx-build directly as a python module rather than in a subprocess, because exhale when it dies does an abrupt system exit without cleanup, which tends to hang the process pool since I cannot catch it.
I replaced the pipx tests with a venv test. There does not seem to be any interest in promoting pipx in the ros2 community, while venv is important for development, and the install requirements can be different if not starting from a ros2 enabled system.

I've done additional work on the whole area of locating packages to document in the last couple of weeks. I am now firmly convinced that colcon is the wrong tool for this use in rosdoc2, and I have replaced it with catkin's find_packages_allowing_duplicates in my fork. I'll eventually update this PR with that change, but for now please hold this PR.
Here's some background. colcon seems to be designed to find packages for building. Fine, but that is not what we are doing. Specifically (in addition to the complications mentioned above) it additionally scans CMakeLists.txt to try to find what it thinks is a package. Fine for building, not good for us since we need a real package.xml to process. So colcon is finding packages that we can't actually process, so it just ends up causing errors (like the urdfdom_headers: retval=1: RuntimeError Failed to find a ROS package at given path 'rosindex/_plugins_data/checkout/urdfdom_headers/github-ros-urdfdom_headers/urdfdom_headers' above).
I've fixed that in my fork, but that fix (which would partially be at the buildfarm level) needs more tweaking. In any case, you have to replace colcon with catkin to eliminate nuisance errors.

OK this is the updated version, reverting to catkin from colcon. Reasons are above.
Yes seems like a big PR, but a lot of this is just rearranging the tests so I can reuse code.

The commit I just did addresses all review comments, AFAICT.

Re "If you do find that this helps with that extra bit of debuggability, it's fine to keep it"
If this comment is about the stdout=sys.stdout, stderr=sys.stderr then no, this is not about debugging, it is essential. As for a comment, if I found this strange I would look for the history, which will point here with a lot more detail than is likely in a comment. I can add a comment though if you like (or you could just add one when you land).

What I was thinking is that you set
options.console_output_file_log = os.path.join(options.doc_build_directory, f'{package.name}.txt') after outfile is created: https://github.com/ros-infrastructure/rosdoc2/pull/139/files#diff-4d67c84fa514f2538371532c7f2d3979b42da8852649e61ed9cac143e83f1c55R171
Then the output_file goes into build_main_impl via the options struct.
Then in main_impl https://github.com/ros-infrastructure/rosdoc2/blob/24c51d595e4477f11b3929c19e2fb6031936f42e/rosdoc2/verbs/build/impl.py#L133
The options get passed into the build_context.tool_options: https://github.com/ros-infrastructure/rosdoc2/blob/24c51d595e4477f11b3929c19e2fb6031936f42e/rosdoc2/verbs/build/inspect_package_for_settings.py#L129
So in the builder itself you can use a conditional. just above https://github.com/ros-infrastructure/rosdoc2/blob/24c51d595e4477f11b3929c19e2fb6031936f42e/rosdoc2/verbs/build/builders/doxygen_builder.py#L246
if build_context.tool_options.console_output_file_log:
    with open(build_context.tool_options.console_output_file_log, 'w') as fh_log:
         subprocess.run( ... stdout=fh_log, stderr=subprocess.PIPE)

This will allow you to not rely on running the builds in different processes via the multi process pool in future applications. And others can potentially leverage the redirection of the log files in other verbs. It also keeps the log file opening much closer to the invocation which is better for cleanup as well as understanding that it might be intercepted.

I finally found some time to switch my mental context from rosindex/html/javascript/css back into rosdoc2/python to understand your comments.
The approach that you outline won't really work as specified, at least if I maintain the goal of capturing the full build output in the outfile, because much of the output does not go through a subprocess.run called from the builder. There are at least 3 subprocesses in play: 1) scan subprocess implemented by package_impl. The rosdoc2 python code runs in this subprocess. 2) the Doxygen subprocess, and 3) the Breathe subprocess. The output of all three needs to be mapped to the same outfile. I can't really open the scan subprocess with a remapped output file AFAICT, because that is opened by the Pool. So I still need to do the stdout & stderr remapping in the scan subprocess to capture, for example, simple print statement output.
I could move the remapping logic into build/impl.py, but it would essentially be the same logic currently in package_impl. That though has the serious downside that package_impl cannot easily write to the outfile if it is opened and closed in build_main_impl. I believe it is important for the final termination messages for a particular package build to be written to both the scan output (which typically shows in the Jenkins console output) as well as in the outfile for a particular package. That is the point of code like:
    finally:
        sys.stdout = old_stdout
        sys.stderr = old_stderr
        elapsed_time = '{:.3f}'.format(time.time() - start)
        if return_value != 0:
            print(f'{_clocktime()} Package at {package_path} failed {return_value}: {message}',
                  flush=True)
            logger.error(f'Package at {package_path} failed {return_value}: {message}')
...

because the print goes to the Jenkins output, while the logger is still mapped to the package outfile. This is particularly important when the package build is terminated by the watchdog timer, as without this the package outfile will just terminate without explanation. It is also difficult to close the outfile if the package build is terminated by the watchdog timer.
So I will do this change if you insist, but I personally don't believe the benefits justify the downside.


Sign in with Apple error: json: invalid use of ,string struct tag, trying to unmarshal unquoted value into bool

Sign in with Apple error: json: invalid use of ,string struct tag, trying to unmarshal unquoted value into bool

Fixed by: https://github.com/casdoor/casdoor/commit/8c415be7c7ee95aa071bda14b2c14b1f6dd61c82


highline dependency error

When installing the latest version:
› sudo gem install fastlane
ERROR:  While executing gem ... (Gem::DependencyResolutionError)
    conflicting dependencies highline (>= 1.7.2) and highline (>= 1.7.1)
  Activated highline-1.7.1
  which does not match conflicting dependency (>= 1.7.2)

  Conflicting dependency chains:
    fastlane (>= 0), 0.12.5 activated, depends on
    cupertino (>= 1.3.3), 1.3.3 activated, depends on
    highline (>= 1.7.1), 1.7.1 activated

  versus:
    fastlane (>= 0), 0.12.5 activated, depends on
    fastlane_core (>= 0.6.2), 0.6.2 activated, depends on
    highline (>= 1.7.2)

  Gems matching highline (>= 1.7.2):
    highline-1.7.2

This happened for me too but I ran "sudo gem uninstall fastlane" and then installed again and it worked.

Sadly for me, not this time
in LoadLearningCart/
› sudo gem uninstall fastlane

in LoadLearningCart/
› sudo gem install fastlane
ERROR:  While executing gem ... (Gem::DependencyResolutionError)
    conflicting dependencies highline (>= 1.7.2) and highline (>= 1.7.1)
  Activated highline-1.7.1
  which does not match conflicting dependency (>= 1.7.2)

  Conflicting dependency chains:
    fastlane (>= 0), 0.12.5 activated, depends on
    cupertino (>= 1.3.3), 1.3.3 activated, depends on
    highline (>= 1.7.1), 1.7.1 activated

  versus:
    fastlane (>= 0), 0.12.5 activated, depends on
    fastlane_core (>= 0.6.2), 0.6.2 activated, depends on
    highline (>= 1.7.2)

  Gems matching highline (>= 1.7.2):
    highline-1.7.2

Related https://github.com/KrauseFx/snapshot/issues/140
Sorry for all this, I'll work on a fix and publish a new version today :+1:

Works great now, thanks!

This makes me very happy to read! Thank you!


ci: do_not_merge: check for dev and arch review labels as well

Add "Architecture Review" and "dev-review" to the list of labels that block a PR from merging, less chances to merge these before discussion unintentionally.

Taking this as a hotfix. We had a WIP PR merged because it was blocked with DNM


Synology solution

Apologies if this isn't a smart question - but can you explain what this solution does that's different than this:
https://kb.synology.com/en-my/DSM/tutorial/How_to_join_NAS_to_Azure_AD_Domain
Thanks

My wrapper creates an entire ldap server. So you can use it with several 3rd party (legacy) software in the same network.
It uses the AzureAD Service (which is available for free).
Your link describes how to join just your Synology-NAS to the Azure AD Domain Service. It will be hard to use this in (old) 3rd party (legacy) software. You'll also need to pay for the Domain Services in Azure to use this.

Thanks!  So if I already have Azure AD Premium P1 adn don't need support for older software, the Synology solution would work fine?

Yes, the Synology solution should work fine in your case :)


There isn't any Copy as Json or Copy as Html Table option

There isn't any Copy as Json or Copy as Html Table option in the Results Pane

close as dupe of https://github.com/microsoft/azuredatastudio/issues/168


1103 - Distribute Candies to People

Description of the Problem
We distribute some number of candies, to a row of n = num_people people in the following way:
We then give 1 candy to the first person, 2 candies to the second person, and so on until we give n candies to the last person.
Then, we go back to the start of the row, giving n + 1 candies to the first person, n + 2 candies to the second person, and so on until we give 2 * n candies to the last person.
This process repeats (with us giving one more candy each time, and moving to the start of the row after we reach the end) until we run out of candies.  The last person will receive all of our remaining candies (not necessarily one more than the previous gift).
Return an array (of length num_people and sum candies) that represents the final distribution of candies.
Example 1:
Input: candies = 7, num_people = 4
Output: [1,2,3,1]
Explanation:
On the first turn, ans[0] += 1, and the array is [1,0,0,0].
On the second turn, ans[1] += 2, and the array is [1,2,0,0].
On the third turn, ans[2] += 3, and the array is [1,2,3,0].
On the fourth turn, ans[3] += 1 (because there is only one candy left), and the final array is [1,2,3,1].

Example 2:
Input: candies = 10, num_people = 3
Output: [5,2,3]
Explanation:
On the first turn, ans[0] += 1, and the array is [1,0,0].
On the second turn, ans[1] += 2, and the array is [1,2,0].
On the third turn, ans[2] += 3, and the array is [1,2,3].
On the fourth turn, ans[0] += 4, and the final array is [5,2,3].

Constraints:

1 <= candies <= 10^9
1 <= num_people <= 1000

Code
class Solution:
    def distributeCandies(self, candies: int, num_people: int) -> List[int]:

Link To The LeetCode Problem
LeetCode

Can you please assign this to me?

I can help in solving this.

Can you please assign this issue to me?


Reduce verbosity of maven output

Is your feature request related to a problem? Please describe.
The maven build logs get filled with "useless" messages that hide the actual CVE warnings.

Build log snippet (click to expand)
[INFO] --- dependency-check-maven:5.1.1:check (cve-check) @ pdb-maven-plugin ---
[INFO] Central analyzer disabled
// Useless logs begin
[INFO] Instance is null, returning unconfigured instance
[INFO] thread_pool.default PoolConfiguration = useBoundary = [false] boundarySize = [2000] maximumPoolSize = [150] minimumPoolSize = [4] keepAliveTime = [300000] whenBlockedPolicy = [RUN] startUpSize = [4]
[INFO] Setting default auxiliaries to ODC
[INFO] setting defaultCompositeCacheAttributes to [ useLateral = true, useRemote = true, useDisk = true, maxObjs = 0, maxSpoolPerRun = -1, diskUsagePattern = UPDATE, spoolChunkSize = 2 ]
[INFO] setting defaultElementAttributes to [ IS_LATERAL = false, IS_SPOOL = true, IS_REMOTE = false, IS_ETERNAL = false, MaxLifeSeconds = 86400, IdleTime = 1800, CreateTime =<PHONE_NUMBER>605, LastAccessTime = 1
563192108605, getTimeToLiveSeconds() = 86399, createTime =<PHONE_NUMBER>605 ]
[INFO] initialized MemoryCache for CENTRAL
[INFO] Constructed cache with name [CENTRAL] and cache attributes [ useLateral = true, useRemote = true, useDisk = true, maxObjs = 0, maxSpoolPerRun = -1, diskUsagePattern = UPDATE, spoolChunkSize = 2 ]
[INFO] No cache event logger defined for auxiliary [jcs.auxiliary.ODC]
[INFO] Using standard serializer [org.apache.commons.jcs.utils.serialization.StandardSerializer@77198cce] for auxiliary [jcs.auxiliary.ODC]
[INFO] thread_pool.disk_cache_event_queue PoolConfiguration = useBoundary = [false] boundarySize = [2000] maximumPoolSize = [150] minimumPoolSize = [4] keepAliveTime = [300000] whenBlockedPolicy = [RUN] start
UpSize = [4]
[INFO] Region [CENTRAL] Cache file root directory:
[INFO] Region [CENTRAL] Set maxKeySize to: '1000000'
[INFO] Region [CENTRAL] Indexed Disk Cache is alive.
[INFO] initialized MemoryCache for POM
[INFO] Constructed cache with name [POM] and cache attributes [ useLateral = true, useRemote = true, useDisk = true, maxObjs = 0, maxSpoolPerRun = -1, diskUsagePattern = UPDATE, spoolChunkSize = 2 ]
[INFO] No cache event logger defined for auxiliary [jcs.auxiliary.ODC]
[INFO] Using standard serializer [org.apache.commons.jcs.utils.serialization.StandardSerializer@157002b7] for auxiliary [jcs.auxiliary.ODC]
[INFO] Region [POM] Cache file root directory:
[INFO] Region [POM] Set maxKeySize to: '1000000'
[INFO] Region [POM] Indexed Disk Cache is alive.
[INFO] initialized MemoryCache for NODEAUDIT
[INFO] Constructed cache with name [NODEAUDIT] and cache attributes [ useLateral = true, useRemote = true, useDisk = true, maxObjs = 0, maxSpoolPerRun = -1, diskUsagePattern = UPDATE, spoolChunkSize = 2 ]
[INFO] No cache event logger defined for auxiliary [jcs.auxiliary.ODC]
[INFO] Using standard serializer [org.apache.commons.jcs.utils.serialization.StandardSerializer@66227940] for auxiliary [jcs.auxiliary.ODC]
[INFO] Region [NODEAUDIT] Cache file root directory:
[INFO] Region [NODEAUDIT] Set maxKeySize to: '1000000'
[INFO] Region [NODEAUDIT] Indexed Disk Cache is alive.
[INFO] Parsed regions [CENTRAL, POM, NODEAUDIT]
// Useless logs end
[INFO] Finished configuration in 147 ms.
[INFO] Checking for updates
[INFO] Skipping NVD check since last check was within 4 hours.
[INFO] Skipping RetireJS update since last update was within 24 hours.
[INFO] Check for updates complete (11 ms)
[INFO] Analysis Started
[INFO] Finished Archive Analyzer (0 seconds)
[INFO] Finished File Name Analyzer (0 seconds)
[INFO] Finished Jar Analyzer (0 seconds)
[INFO] Finished Dependency Merging Analyzer (0 seconds)
[INFO] Finished Version Filter Analyzer (0 seconds)
[INFO] Finished Hint Analyzer (0 seconds)
[INFO] Created CPE Index (1 seconds)
[INFO] Finished CPE Analyzer (2 seconds)
[INFO] Finished False Positive Analyzer (0 seconds)
[INFO] Finished NVD CVE Analyzer (0 seconds)
[INFO] Finished Sonatype OSS Index Analyzer (0 seconds)
[INFO] Finished Vulnerability Suppression Analyzer (0 seconds)
[INFO] Finished Dependency Bundling Analyzer (0 seconds)
[INFO] Analysis Complete (4 seconds)
[WARNING]

One or more dependencies were identified with known vulnerabilities in Product-DB Plugin for Maven:

jackson-databind-2.9.9.jar<EMAIL_ADDRESS>cpe:2.3:a:fasterxml:jackson:2.9.9:*:*:*:*:*:*:*, cpe:2.3:a:fasterxml:jackson-databind:2.9.9:*:*:*:*:*:*:*) : CVE-2019-12814
plexus-utils-1.5.15.jar<EMAIL_ADDRESS>cpe:2.3:a:plexus-utils_project:plexus-utils:1.5.15:*:*:*:*:*:*:*) : CVE-2017-1000487, Directory traversal in org.codehaus.plexus.util.Expand,
Possible XML Injection
guava-20.0.jar<EMAIL_ADDRESS>cpe:2.3:a:google:guava:20.0:*:*:*:*:*:*:*) : CVE-2018-10237

See the dependency-check report for more details.

// Useless logs start again
[INFO] Element event queue destroyed: org.apache.commons.jcs.engine.control.event.ElementEventQueue@7b338d46
[INFO] In DISPOSE, [NODEAUDIT] fromRemote [false]
[INFO] In DISPOSE, [NODEAUDIT] auxiliary [NODEAUDIT]
[INFO] In DISPOSE, [NODEAUDIT] put 0 into auxiliary NODEAUDIT
[INFO] No longer waiting for event queue to finish: Pooled Cache Event Queue
Working = true
Alive = false
Empty = true
Queue Size = 0
Queue Capacity =<PHONE_NUMBER>
Pool Size = 0
Maximum Pool Size = 150
[INFO] In dispose, destroying event queue.
[INFO] Region [NODEAUDIT] Saving keys to: NODEAUDIT, key count: 0
[INFO] Region [NODEAUDIT] Finished saving keys.
[INFO] Region [NODEAUDIT] Shutdown complete.
[INFO] In DISPOSE, [NODEAUDIT] disposing of memory cache.
[INFO] Memory Cache dispose called.
[INFO] In DISPOSE, [CENTRAL] fromRemote [false]
[INFO] In DISPOSE, [CENTRAL] auxiliary [CENTRAL]
[INFO] In DISPOSE, [CENTRAL] put 0 into auxiliary CENTRAL
[INFO] No longer waiting for event queue to finish: Pooled Cache Event Queue
Working = true
Alive = false
Empty = true
Queue Size = 0
Queue Capacity =<PHONE_NUMBER>
Pool Size = 0
Maximum Pool Size = 150
[INFO] In dispose, destroying event queue.
[INFO] Region [CENTRAL] Saving keys to: CENTRAL, key count: 0
[INFO] Region [CENTRAL] Finished saving keys.
[INFO] Region [CENTRAL] Shutdown complete.
[INFO] In DISPOSE, [CENTRAL] disposing of memory cache.
[INFO] Memory Cache dispose called.
[INFO] In DISPOSE, [POM] fromRemote [false]
[INFO] In DISPOSE, [POM] auxiliary [POM]
[INFO] In DISPOSE, [POM] put 0 into auxiliary POM
[INFO] No longer waiting for event queue to finish: Pooled Cache Event Queue
Working = true
Alive = false
Empty = true
Queue Size = 0
Queue Capacity =<PHONE_NUMBER>
Pool Size = 0
Maximum Pool Size = 150
[INFO] In dispose, destroying event queue.
[INFO] Region [POM] Saving keys to: POM, key count: 0
[INFO] Region [POM] Finished saving keys.
[INFO] Region [POM] Shutdown complete.
[INFO] In DISPOSE, [POM] disposing of memory cache.
[INFO] Memory Cache dispose called.

Describe the solution you'd like
Turn down the verbosity level of those messages or only print them if the plugin is set to verbose.
Describe alternatives you've considered
Better highlight actual cve results

I've tried a few times to get rid of these log messages - they come from JCS. In an attempt to improve performance we utilized JCS' disk caching for some of the analysis results. However, JCS has what appear to be debug/trace logged at the info level. I've been unable to figure out how to disable those messages in the maven plugin.  PRs are welcome.

The trick is that you configure the logging verbosity in your code.
((SimpleLog) LogFactory.getLog(String)).setLevel(SimpleLog.WARN);
Unfortunately I'm not sure about the implementation class or whether you have to do it once per class/logger or can do it once for all nested packages.

I've tried several ways of controlling the log messages from JCS - and I have not been able to find the right avenue to control the logging in Maven from code.  For instance, using your example above at runtime you get:
A type incompatibility occurred while executing
org.owasp:dependency-check-maven:5.1.2-SNAPSHOT:aggregate:
org.apache.commons.logging.impl.SLF4JLog cannot be cast to
org.apache.commons.logging.impl.SimpleLog

However, thanks to my most trusted coding resource I was able to find a solution:
private void muteJCS() {
        final String[] noisyLoggers = {
            "org.apache.commons.jcs.auxiliary.disk.AbstractDiskCache",
            "org.apache.commons.jcs.engine.memory.AbstractMemoryCache",
            "org.apache.commons.jcs.engine.control.CompositeCache",
            "org.apache.commons.jcs.auxiliary.disk.indexed.IndexedDiskCache",
            "org.apache.commons.jcs.engine.control.CompositeCache",
            "org.apache.commons.jcs.engine.memory.AbstractMemoryCache",
            "org.apache.commons.jcs.engine.control.event.ElementEventQueue",
            "org.apache.commons.jcs.engine.memory.AbstractDoubleLinkedListMemoryCache",
            "org.apache.commons.jcs.auxiliary.AuxiliaryCacheConfigurator",
            "org.apache.commons.jcs.engine.control.CompositeCacheManager",
            "org.apache.commons.jcs.utils.threadpool.ThreadPoolManager",
            "org.apache.commons.jcs.engine.control.CompositeCacheConfigurator"};
        for (String loggerName : noisyLoggers) {
            try {
                //This is actually a MavenSimpleLogger, but due to various classloader issues, can't work with the directly.
                Logger l = LoggerFactory.getLogger(loggerName);
                Field f = l.getClass().getSuperclass().getDeclaredField("currentLogLevel");
                f.setAccessible(true);
                f.set(l, LocationAwareLogger.ERROR_INT);
            } catch (IllegalAccessException | IllegalArgumentException | NoSuchFieldException | SecurityException e) {
                getLog().warn("Failed to reset the log level of " + loggerName + ", it will continue being noisy.", e);
            }
        }
    }

The links on their project site are broken, but the issue tracker is over here: https://issues.apache.org/jira/projects/JCS

Yes, JCS-122 would likely break this workaround. In addition, the next version of JCS could add another noisy logger that would need to be muted. We need to monitor as we upgrade JCS.

@jeremylong - This change appears to have introduced a huge pile of stack traces (~12 of them) getting dumped to the screen when using the Maven plugin. All about noSuchFieldException: currentLogLevel
Was that intentional? This seems far more chatty/noisy than before this change. You can't fix this noSuchFieldException problem?

Can you paste (one of) them?

@davewichers are you using an old version of Maven? I'm not seeing any stack traces with 3.6.1.

Good call. I was using Maven 3.3.9, which is clearly old. :-) I upgraded to 3.5.3 and it worked fine. On another system, which was already not exhibiting this problem, it was using 3.5.4. So, people must use something newer than 3.3.9, but not sure exactly which version is required now.


Gaming Workload Scenarios #1 - Minecraft

PR Summary
Gaming preset
Added a new preset scenario for gaming. 2 cards have been added for Minecraft.

Note that the script we'll need for Minecraft workload will be considerably shorter when bicep extensibility for kubernetes comes out. (It'll drop down to 1 line!)

Closes #445

TODO

[x] Add a preset description h2 to the page
[x] Implement card level post deploy additions (for workload specific scripts) using token replacement for ResourceGroup name
[x] Support public ip per node #452

Other
vm sku chmod
WSL/Windows is messing up the attributes of the generate-vm-sku-list-v2.sh file. For reliability, we need to chmod it during the workflow.
eslint
Incorporated eslint fixes for reported warnings
PR Checklist

[x] PR has a meaningful title
[x] Summarized changes
[x] This PR is ready to merge and is not Work in Progress
[x] Link to a filed issue
[x] Screenshot of UI changes (if PR includes UI changes)

@Gordonby specifically for gaming workloads we would need to enable IPs per node for lower latency and direct client connects.
Reference documentation:
https://learn.microsoft.com/en-us/azure/aks/use-multiple-node-pools#assign-a-public-ip-per-node-for-your-node-pools
https://github.com/PlayFab/thundernetes/blob/main/docs/quickstart/installing-aks.md
https://agones.dev/site/docs/installation/creating-cluster/aks/#creating-the-aks-cluster

@Gordonby specifically for gaming workloads we would need to enable Public IPs per node for lower latency and direct client connectivity.
Reference documentation: https://learn.microsoft.com/en-us/azure/aks/use-multiple-node-pools#assign-a-public-ip-per-node-for-your-node-pools https://github.com/PlayFab/thundernetes/blob/main/docs/quickstart/installing-aks.md https://agones.dev/site/docs/installation/creating-cluster/aks/#creating-the-aks-cluster

Captured this in #452

Feedback
title font too big
workload deploy shellscript box


Update c# docs for release 0.11

-- change C# status to beta
-- change installation instructions on Linux (use debian packages).
-- make the readme.md style more similar to ruby's readme.
-- lots of nits
Missing:
route guide example for C# on grpc.io is out of date and needs to be updated.

route guide example for C# on grpc.io is out of date and needs to be updated.

What about the QuickStart (helloworld) in this repo? will that get updated when routeguide is updated?

Alright, I updated the helloworld README.md as well and fixed some of the links. PTAL.
In the next stage, I will create a PR to update contents of grpc.io site. Then I will delete the route guide's readme.md from this repo.


Add a note on when to use commits

@derekwaynecarr

+100

Lgtm
On Thursday, July 30, 2015, Kubernetes Bot<EMAIL_ADDRESS>wrote:

GCE e2e build/test failed for commit c58e3fb
https://github.com/GoogleCloudPlatform/kubernetes/commit/c58e3fbbb696b130d246e7c0c091ff4542be216c
.

Build Log
https://storage.cloud.google.com/kubernetes-jenkins/pr-logs/c58e3fbbb696b130d246e7c0c091ff4542be216c/kubernetes-pull-build-test-e2e-gce/3889/build-log.txt
Test Artifacts
https://console.developers.google.com/storage/browser/kubernetes-jenkins/pr-logs/c58e3fbbb696b130d246e7c0c091ff4542be216c/kubernetes-pull-build-test-e2e-gce/3889/_artifacts/
Internal Jenkins Results
http://goto.google.com/prkubekins/job/kubernetes-pull-build-test-e2e-gce//3889

—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/12047#issuecomment-126510909
.

Sandwhiches not sausages!


Remove pip packaging

removing the packaging files related to buildtest-framework. This caused confusion reported by @vsoch.

@vsoch cleaning up my mess.

Thank you! I'll start working from devel - is it all set?

yea its fine for now.  I have some ideas on YAML schema but need to carefully work through this.
I have some ideas in covered in and this where i need to put more efforts.
https://github.com/HPC-buildtest/buildtest-framework/issues/135
https://github.com/HPC-buildtest/buildtest-framework/wiki/Yaml-Schema-Draft
Any ideas are always welcomed.

Thank you @shahzebsiddiqui ! if it's okay with you, I'd like a few days to test and do some small changes, and I'll open a PR after that. Once I'm familiar with the structure and general flow of things I can give much better feedback about the specific issues that we've discussed.

Of course, take your time, and your feedback will be great. It would certainly help to know which features are useful and which are not. That will help guide where to put more work. Also there is a devel doc branch https://buildtest.readthedocs.io/en/devel/index.html that can be used for referring to devel changes which i generally add as part of release before merging everything to master.
I try to document everything, but certainly if you come across some missing docs please open an issue.
There is a doc issue template dedicated for these issues


Create documentation for creating themes

Need to create documentation explaining how to use/edit theme_setup.json and themes subfolders to create your own theme.

Done:
https://github.com/JartanFTW/Trade-Notifier/wiki/Themes
https://github.com/JartanFTW/Trade-Notifier/wiki/theme_setup.json

Done:
https://github.com/JartanFTW/Trade-Notifier/wiki/Themes
https://github.com/JartanFTW/Trade-Notifier/wiki/theme_setup.json


Hard wrap support in shortcodes

I'm a hard wrap person because I use Vim and it just makes more sense with it. One of the most interesting things about Hugo is that I can use Vim to write my content with it. Hugo doesn't really support hard wrap, though. You can get away with it without noticing because when hard wrapped content is put in an HTML <p> tag, browsers will join all the lines. But the moment you want to write a Front Matter title that's two lines long, or the moment you want to include long shortcodes, Hugo will throw errors. I don't have a lot of content so it's manageable but I could definitely see that being a problem for others or for me in the future. Here's an example of what Hugo understands:
{{% figure src="Lorem ipsum dolor sit amet, consectetur adipiscing elit." alt="Lorem ipsum dolor sit amet, consectetur adipiscing elit." %}}

And here's what I would like it to understand:
{{% figure src="Lorem ipsum dolor sit amet, consectetur adipiscing elit."
alt="Lorem ipsum dolor sit amet, consectetur adipiscing elit." %}}`

Does that look like much work? I wish I could help but I have no idea.
Thanks!
Maxime

Currently this works:
{{% figure src="Lorem ipsum dolor sit amet, consectetur adipiscing elit."
alt="Lorem ipsum dolor sit amet, consectetur adipiscing elit." %}}

This, however, fails:
{{% figure src="Lorem ipsum dolor sit
amet, consectetur adipiscing elit."  alt="Lorem ipsum dolor sit amet, consectetur adipiscing elit." %}}

Not sure why I put this restriction in there.
It can be fixed by removing the \n case here:
https://github.com/spf13/hugo/blob/master/hugolib/shortcodeparser.go#L429
PRs are welcome.

Sorry I didn't double-check. You're right, the problem is when the quotes don't begin and end on the same line. What about the Front Matter though, why did you rename the title and not include it? Should I create another issue for it?

I think I remember the reason for having that \n check in there:
If you forget the right quote, and don't have any other checks, the parser will run until EOF before it fails.
Not sure if that's a big deal or not.

I changed the title to scope it as I saw it. The front matter is a different issue, and I think you have to live with the spec of TOML YAML and JSON.

Regarding the front matter, I've found this. Is there a reason this doesn't work with v0.13 for me?

Note/Update: This issue is marked as stale, and I may have said something earlier about "opening a thread on the discussion forum". Please don't.
If this is a bug and you can still reproduce this error on the latest release or the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.


Splicing of hooks is broken in mkPythonDerivation

Describe the bug
Various hooks that are put in nativeBuildInputs of a python package by mkPythonDerivation/buildPythonPackage don't get shifted to buildPlatform.
Steps To Reproduce
Steps to reproduce the behavior:
nix-repl> u = import <nixos-unstable> {system =  "x86_64-linux"; crossSystem="aarch64-linux";}

nix-repl> testPythonPackage = u.__splicedPackages.python311Packages.buildPythonPackage {name = "ttt";}

nix-repl> python = builtins.elemAt testPythonPackage.nativeBuildInputs 0

nix-repl> python.stdenv.hostPlatform.system
"x86_64-linux"

nix-repl> hook = builtins.elemAt testPythonPackage.nativeBuildInputs 1

nix-repl> hook.stdenv.hostPlatform.system
"aarch64-linux"

Expected behavior
hook.stdenv.hostPlatform.system should also be "x86_64-linux"

Should be fixed by #228139


[FLINK-21888][hive] Maintain our own ASTNode class

What is the purpose of the change
Add our own ASTNode. This is needed to support hive dialect for different hive versions.
Brief change log

Add HiveParserASTNode and stop using hive's ASTNode.

Verifying this change
Existing tests
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? NA

The failed case is not related to the issue.

Thanks @wuchong for merging the PR. Yes HiveParserErrorMsg will be used in follow-up PRs to replace hive's ErrorMsg::getMsg method to generate error messages with an ASTNode.


Ratio of house usage colour

Nevermind.. was an internal issue.

Sorry.. seems like it was not an internal issue

I currently have "use AC first" set, meaning all the grid will go into house and all the solar will go into battery, Yet the yellow house colour indicates otherwise.

Hi. The card only considers power from the battery and solar and then proportions it based on measured house load. Any shortfall is assumed to be supplied from the grid.  Since you have configured a different priority it wont accurately reflect  your use case  and you should disable the feature.

Gotcha. Thanks for clearing it up
On Mon, 11 Dec 2023 at 10:13, slipx06 @.***> wrote:

Hi. The card only considers power from the battery and solar and then
proportions it based on measured house load. Any shortfall is assumed to be
supplied from the grid. Since you have configured a different priority it
wont accurately reflect your use case and you should disable the feature.
—
Reply to this email directly, view it on GitHub
https://github.com/slipx06/sunsynk-power-flow-card/issues/165#issuecomment-1849523290,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQHYNB64CEKZYTQTLUPQHJ3YI26BZAVCNFSM6AAAAABAKRJIUOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBZGUZDGMRZGA
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


Error "Update mkParentDir failed" when using rclone with ocis

Describe the bug
I run into an issue when trying to sync my home dir to ocis (2.0.0) using rclone (1.61.1). On the client side I see messages like the following:
$ rclone -v -L sync /tmp/blackhole/ocis/ storage:/test
2023/01/31 18:04:15 ERROR : foo/bar/baz/test.txt: Failed to copy: Update mkParentDir failed: Resource not found: Sabre\DAV\Exception\NotFound: 404 Not Found
2023/01/31 18:04:15 INFO  : test.txt: Copied (new)
2023/01/31 18:04:15 ERROR : webdav root 'test': not deleting files as there were IO errors
2023/01/31 18:04:15 ERROR : webdav root 'test': not deleting directories as there were IO errors
2023/01/31 18:04:15 ERROR : Attempt 1/3 failed with 1 errors and: Update mkParentDir failed: Resource not found: Sabre\DAV\Exception\NotFound: 404 Not Found
2023/01/31 18:04:15 ERROR : foo/bar/baz/test.txt: Failed to copy: Update mkParentDir failed: Resource not found: Sabre\DAV\Exception\NotFound: 404 Not Found

Steps to reproduce

Let's assume your working dir is /tmp/blackhole/ocis
create test.txt: echo "Hello ocis" > test.txt
create a simple folder structure mkdir -p foo/bar/baz
copy text.txt to that folder cp test.txt foo/bar/baz/
start sync rclone -v -L sync /tmp/blackhole/ocis/ storage:/test

Expected behavior
I should be able to sync this folder with rclone w/o seeing such an error.
Actual behavior
I get an error with the latest OCIS stable version.
Setup
Please describe how you started the server and provide a list of relevant environment variables or configuration files.
did setcap 'cap_net_bind_service=+ep' ocis and run ocis like this:
OCIS_BASE_DATA_PATH=/var/lib/ocis
ACCOUNTS_DEMO_USERS_AND_GROUPS=false
PROXY_HTTP_ADDR=<IP_ADDRESS>:443
OCIS_URL=https://storage.0x17.ch
PROXY_TRANSPORT_TLS_KEY=/etc/letsencrypt/live/storage.0x17.ch/privkey.pem
PROXY_TRANSPORT_TLS_CERT=/etc/letsencrypt/live/storage.0x17.ch/fullchain.pem
OCIS_INSECURE=false
PROXY_ENABLE_BASIC_AUTH=true

Additional context
I had a similar issue earlier on, see: #2767

@wkloucek I think this may be related to #2767, maybe something you want to have a look at?
(I hope it's fine to highlight you - otherwise just let me know)

I also see this with rclone on a Windows 11 box syncing to the same server.

There was a fix in #6136 which is available on ocis master which might fix this issue.

Hi @micbar I can confirm, that this is fixed in a recent release! I tested with 3.0.0 rc3 and the problem is gone.
Awesome! Thanks a lot for the work on this!


Entity discovery should automatically popualte project id in catalog-info.yaml/backstage.yaml

It would be great if this plugin could collaborate with the @backstage/plugin-catalog-backend-module-gitlab to populate the project id in the entity module automatically if the user does not set the id in the yaml file.
https://github.com/backstage/backstage/issues/13118

Hi @matteosilv, this fix is available with the new release v3.0.0.
This release also adds support of multi-gitlab instances.


chore: Infer key type from public key and private key

Solves #403

Thank you for your review :).


Migrate to EC2

Is your feature request related to a problem? Please describe.
Limitations of Heroku is problematic for a lot of deployments.
Describe the solution you'd like
Use a AWS EC2 Ubuntu VPS for the deployments.
Related Issue
https://github.com/sef-global/scholarx/issues/117

We ended up using heroku and it's already done.


Enable Parallel coverage on CircleCI

@goanpeca Is there any way to get Coveralls parallel reports to work on CircleCI, it seems that notifications get stuck


ES indexed_date field when processing WARC files, and historical data

In today's (2023-01-24) team meeting, I got the understanding from @rahulbot that ES indexed_date is meant to indicate "when the data was processed (ie; parsed)"
In the meeting, I thought ContentMetadata contained a timestamp, but it turns out I was thinking of HTTPMetadata.fetch_timestamp
For the upcomming re-import/re-index from WARC files some choices are:

add ContentMetadata.parse_timestamp field (a small change), have parser.py always set it (to time.time()) and have the archive processing process (arch-queuer.py) default it to the WARC-Date if the field is missing when reading archives, and have the importer use ContentMetadata.parse_timestamp to generate indexed_date from it, or default to datetime.utcnow()
not add the field, fill in HTTPMetadata.fetch_timestamp and pass the importer a command line option to use fetch_timestamp instead of "now" for generation of indexed_date

For processing historical data, some choices are:

same as 1 above: since the data will pass thru the parser, the indexed date will indicate the date it was parsed.
same as 2 above, except have arch-fetcher.py fill in HTTPMetadata.fetch_timestamp with time.time() instead of either the timestamp of the S3 object containing the archived HTML, or the date/time in the CSV file.   BUT, the HTTP data date could be saved in the RSSEntry Story sub-object, but this feels like a terrible crock!

In both cases above one more option is:
3. do nothing, have indexed_date reflect the date the data was entered into ES.
My understanding is that this is not a terrible choice (because it wouldn't be off the parse date by more than 70 days), BUT would be a less ideal choice at some future time, because the indexed date would be off by some large amount)

With a little more time, there is no reason to use timestamp (time.time()):  while a timestamp is only 8 bytes (64-bit double precision number) in memory, it's likely to be 18ish bytes in formatted JSON, and an ISO date YYYY-MM-DD is only 10, and the final destination field indexed_date is an ISO date, so fractional day/second accuracy is pointless.
Please forgive extended discussion: I'm easily confused about timestamps (I've been using Unix for 40 years, and I wouldn't bet my life I can tell you how a given system call might change the three traditional Unix file timestamps ctime, mtime and atime-- note: none of them are file creation time!) and want to leave as many breadcrumbs for the future as possible, and to lay things out without reference to some other description, I propose:
Adding parsed_date to ContentMetadata, string with YYYY-MM-DD format.

if mcmetadata.extract supplies a value it will be transferred to ContentMetadata (default handling of extract output)
if ContentMetadata.parsed_date has not been set, parser will supply datetime.utcnow().strftime("%Y-%m-%d")

importerwill use contents of ContentMetadata.parsed_date if non-empty to populate ES "indexed_date" field

OK, I had falsely thought that indexed_date was just a date, but I see it currently is populated with:
indexed_date = datetime.now().isoformat()
Which I think should be datetime.utcnow().isoformat() to unambiguously indicate that it's always GMT.


Peer review encryption and decryption library implementations

https://reltrack.azurewebsites.net/activity/3762?section=tasks
Security > Peer review encryption and decryption library implementations

No crypto algorithm implemented.


Discord.py 1.6.0 dpytest upgrade

Upgrade dpytest and discord.py to 1.6.0
4 2 tests still fail, all of which are @Unknownlocal 's pls take a look

Only 2 RFR tests left to fix

@JayDwee build success


:fire: Remove coc completion source code

https://github.com/Freed-Wu/requirements-language-server
realize a language server for requirements.txt which has more functions
and better performance and support all editors which supports LSP.
The coc completion source code of this repository can be removed to
avoid the conflict of coc.nvim user.
And can you add me to collaborators? If there are any coc.nvim users confused by
their completion's disappearance, I can do something to solve their confusion.

@Freed-Wu Congratulations on your release.

And can you add me to collaborators? If there are any coc.nvim users confused by
their completion's disappearance, I can do something to solve their confusion.

I have added your account to this repository-collaborators.


[Bug] Widget state is out of sync when returning after previously connecting

Description

After connecting my wallet and subscribing to gm initially, if I reload the page I am still connected in the main UI/web3modal, but the widget shows "Connect Wallet" (see screenshot)

Reproduction

Go to https://notify.gm.walletconnect.com/
Connect Wallet and subscribe to GM
Reload the page
See state shown in screenshot
Clicking "Connect wallet" again in widget does not resolve the issue

Expected Behaviour
The widget is synchronised in state with the main UI and is in a logged in/connected state.

Duplicate of https://github.com/WalletConnect/gm-dapp/issues/23
Closing


Bug: I can't seem to specify YOUTUBEDL_ARGS or YTDLP_EXTRA_ARGS

I'm trying to run an archivebox add command with specific yt-dlp flags, on the latest development commit.
But I'm trying every escaping variation of docker compose exec --user=archivebox archivebox /bin/bash -c "env YTDLP_EXTRA_ARGS=[\"--limit-rate=10M\"] archivebox config --get YTDLP_EXTRA_ARGS" and it doesn't seem to work, and same with YOUTUBEDL_ARGS (did it change?).
I used to be able to do: docker compose run --rm archivebox "config --get URL_BLACKLIST && YOUTUBEDL_ARGS='[\"--restrict-filenames\"]' /usr/local/bin/archivebox add 'https://www.youtube.com/shorts/blahblahblah'" and it would just work. The && was to be able to enter the environment variable before the archivebox command, but now that's not allowed.

You can pass env vars with -e https://docs.docker.com/compose/how-tos/environment-variables/set-environment-variables/#set-environment-variables-with-docker-compose-run---env

Thanks for that! I got it to work with other config options, but can't get the -e method to work with YTDLP_EXTRA_ARGS or YOUTUBEDL_ARGS. I tried everything in #890 but nada

Thanks for that. But even though this works perfectly like this:
sudo docker compose run --rm archivebox config --set YTDLP_EXTRA_ARGS='["--write-description", "--write-info-json", "--write-annotations", "--write-thumbnail", "--no-call-home", "--write-sub", "--all-subs", "--write-auto-sub", "--convert-subs=srt", "--yes-playlist", "--continue", "--ignore-errors", "--geo-bypass", "--add-metadata", "--max-filesize=500m", "--sub-lang=en"]'
...running this with the -e flag doesn't seem to affect the config (even though it works with other config options):
sudo docker compose run --rm -e YTDLP_EXTRA_ARGS='["--write-description", "--write-info-json", "--write-annotations", "--write-thumbnail", "--no-call-home", "--write-sub", "--all-subs", "--write-auto-sub", "--convert-subs=srt", "--yes-playlist", "--continue", "--ignore-errors", "--geo-bypass", "--add-metadata", "--max-filesize=500m", "--sub-lang=en"]' archivebox config --get YTDLP_EXTRA_ARGS


Create NPM package

Having this module on NPM would be great 📦🙂

I don't understand why it's not.

@locness3 @astagi I've created a npm org, added the CI token as a repository secret, and added a start for GitHub Actions:
https://github.com/openfoodfacts/openfoodfacts-nodejs/pull/134
Would you be interested in creating it ? Also, I've invited @astagi to the OFF org on npm
https://docs.github.com/en/actions/guides/publishing-nodejs-packages

@teolemon I've received the invitation, thanks! I'll create the package asap 📦

@teolemon sorry I missed the PR you referenced with the github action for auto publishing, it looks great! I suggest to run tests before publishing as I commented.
I've just opened a new PR to fix tests in CI, please check it out #135

Done: https://www.npmjs.com/package/openfoodfacts-nodejs


Checkpoint 2 Grading Ticket

Team Grade - 0.89

Name
Role
Individual Issue Link
Personally-Evaluated Grade
Total Grade

Yash Parikh
Scrum Master
Link
0.90
1.79

Anvay Vahia
Assistant Scrum Master
Link
0.90
1.79

Mihir Bapat
Developer
Link
0.90
1.79

Aditya Katre
Developer
Link
0.90
1.79

Manas Goel
Developer
Link
0.90
1.79

Pranav Santhosh
Developer
Link
0.89
1.78

You guys are doing great.   The thought you put into everything is remarkable.  We will hold score as some improvements can be made.  I like your cross triangle improvement ideas.


Monorepo [Turborepo]

Can you provide an example of how to cache subfolder node_modules in Monorepo ?
When we have:
Root
package.json
package-lock.json // (1)
node_modules

  | -- Package1
        package.json
        node_modules // <- how i can cache (this node_modules depends of package-lock.json(1))

  | -- Package2
        package.json
        node_modules // <- how i can cache  (this node_modules depends of package-lock.json(1))

  | -- Other Packages

There is an option operating_dir: "./" # optional in the README, which should do what you are looking for.

There is an option operating_dir: "./" # optional in the README, which should do what you are looking for.

      - name: Install Dependencies
        uses: kevincobain2000/action-cache-http@v3
        with:
          version: 18
          lock_file: package-lock.json
          install_command: npm install
          operating_dir: "./" // roo dir
          destination_folder: **/node_modules // all node_modules in all subdirectories
          cache_http_api: "http://cache-http"


Authorisation Error Error 403: access_denied

Got as afar as to actually turn on the script, tried putting the url into chrome and get thrown this.

Thanks for the report. I have never seen this before. The only thing I can recommend is to ensure that you put the correct url into your browser. To ensure that you downloaded the correct google credentials (#3). If nothing else works, wipe everything and try again. Sorry I couldn't be more helpful.

Have you ever solved this problem?

Have you ever solved this problem?

I also encountered this problem.
Have you ever solved this problem?

I also encountered this problem.
Have you ever solved this problem?

Solve this

Solve this

I'm going to close this for now. If you are still experiencing this, please re-open.

I'm going to close this for now. If you are still experiencing this, please re-open.


gax-go: package needs package-level documentation

I stumbled upon the godoc for this package via a link from golang/oauth2#203, and immediately wondered "what the heck is gax"? There was no package-level documentation to answer this. Especially since it has such an odd name, it seems like this package needs some context.

@jacobsa Sorry I haven't gotten to this before. The code hasn't been changed in a while, so I lost track of the repo. Working on this now.


Getting white screen in ios after installing this plugin

Bug Report
Problem
After installing cordova-plugin-wkwebview-engine plugin my cordova ios app, its giving white screen after the splash screen.
What is expected to happen?
It should show application login screen.
What does actually happen?

HelloCordova

        A sample Apache Cordova application that responds to the deviceready event.

        Apache Cordova Team

Information

Command or Code

Environment, Platform, Device

Version information

Checklist

[ ] I searched for existing GitHub issues
[ ] I updated all Cordova tooling to most recent version
[ ] I included all the necessary information above

HelloCordova

        A sample Apache Cordova application that responds to the deviceready event.

        Apache Cordova Team

Seems a duplicate of #138

closing as a dupe


Get config parameters only from the environment rather than from config file

It would be better to get our credentials for our database from our environment rather than from a config file. However, this isn't as nice as it could be for distributing credentials- users would need to manually set their credentials and would need some experience working with Linux systems natively.
Therefore, I think that there are some better steps that we could take here. On this account, we'll accomplish the following transition:

[ ] Describe standard format that could be used to distribute credentials (could be JSON)
[ ] Write a script to break those parameters out of the config file into the user's environment when developing locally
[ ] transition app from using a config file at all to only using environment variables.
[ ] document the preference thoroughly so that incoming users will understand how to use the new process.

@JamesKunstle can this be closed? I thought it was fixed in a prior pr but I might be mistaken


Debug tree views not centerted properly on linux

On linux the text in elements in debug views is not centered properly
This is very weird since I set the line-height to 22px the same way as the explorer does and explorer is centered properly.
@joaomoreno let me know if you have some clue what might be going on here, did some investigation but I ran out of ideas. verticaly centering has no effect. Setting the line-height to 25px fixes the issue but that feels wrong since their actual size is 22px.
I also noticed that one of the contianers is not 100% height, it is 21.67px on linux, but chaning it to have height 100% and go up to 21.99px does not actually fix the issue.
found by @bpasero

I'll fix this like a boss by adopting the new tree, pushing to November 🤠

It will probably not be fixed in the new tree, since this is irrelevant to the tree. Linux is famously bad at text layouting, so you're just gonna have to experiment with height and line-height values.

Sounds fun. I'll still leave this for a rainy november day to match my mood

New tree. Optimistically closing this 🤠


Link WebAssembly runtime

Changes to link the WebAssembly runtime with codegen. This will allow us to start enabling runtime-provided features. This change proves that out by allocating via the runtime (though with no GC reporting, so hopefully it doesn't try to collect). Also includes some codegen fixes required by the new code that we're generating. Fixes #4656.

CC @hippiehunter in case you want to start playing with this.

LGTM (modulo comments). I have not looked at the LLVM specific parts in details.

Thanks for the reviews!


fix scrollbar height

Fix the height of scrollbar so maybe #3 is fixed.

Not sure if this will fix the issue, but let's try it


US281 Server Constants Export

Overview
This PR implements User Story 281, exporting constants from the server side. It does this by using an altered version of Steven's original script for creating the backend constants, and it additionally gathers the cosmo constants.
Route-specific files
Some of the routes were refactored into their own files to help with separation of concerns and organization. Everything still passes tests and works the same. From this perspective it seems to be easier to read as well for those. See blueprints on how that works for Flask. But basically a blueprint works the same as a flask app object.
Cosmo options were found!
Finally the source of the different cosmo models was found (Planck13, Planck15) etc. astropy.cosmology.parameters. Two of them don't seem to work with HMF yet though. So those are skipped.
Library updates
Some libraries were updated to allow for the constants to be pulled. All tests still pass and the site works the same.
Skipped constants
Because some constants like n, z, and sigma_8 do not have different values for each cosmological model, they were left out of the cosmo_defaults section of the constants from the server. They DO have different values as hard-coded by Steven on the front-end of the old site. Because of this, it seems like a better idea to leave constants that cannot be pulled from libraries to be implemented on the front-end, that way they all stay in one place.
Open to suggestions
If there are any constants that are missed, that might be included in the libraries, please feel free to speak up and I will try to grab those as well.
Includes:

server/.flake8
server/halomod_app/init.py
server/halomod_app/routes/ascii.py
server/halomod_app/routes/constants.py
server/halomod_app/routes/create.py
server/halomod_app/routes/plot_types.py
server/halomod_app/utils.py
server/requirements.txt
server/tests/test_ascii.py
server/tests/test_constants.py
server/tests/test_create.py
server/tests/test_halomod.py
server/tests/test_plot_types.py

Developer Checklist:

[x] The code follows the Quality Policy file on Google Drive
[x] My code has been developer-tested and includes unit tests
[x] I have considered proper use of exceptions
[x] I have eliminated IDE warnings
[x] I have included tasks associated with this pull request in the Sprint Progress Sheet.

Refs:

User Story 281

I have very little to say about the code that exports constants but...
There are ALOT of changes here that were outside the scope of the User Story and those changes were applied pretty inconsistently. I am on board with using blueprints and breaking up our server into smaller pieces but maybe there's room for more discussion and thought on how that should actually be done. This refactor is probably something someone needs to commit to as a large-ish user story that overhauls how the entire API is structured, alongside the client-side changes that accompany that.
With that in mind, I think these changes should be excluded from this branch and moved elsewhere until it can be discussed a little more and be done in a more comprehensive way. It's a great start and we can definitely use & extend what you've got if you can tuck the changes away on another branch but I would like to see this particular pull request simplified to what the acceptance criteria called for.
Does that make sense? Can obviously discuss if you have any questions/thoughts.

There wasn't a lot about this that was outside of the scope of the user story, some, yes, but not a lot. The separate routing with blueprints made a lot more sense because of all the initialization logic that was exclusive to the constants endpoint. Putting all of that in the main thread of server startup would have been a mess and probably been rejected by the group because it was already very complicated in there and Steven specifically requested that it was reduced in some way. The libraries had to be updated in order for this to work, and the cosmo-options are part of the constants. The parts that were out of scope were the other routes which were converted to their own files and the separation of a single function into Utils, so that could be accomplished. What else was there?
The files were separated into their own routes along with constants as an example to test the waters. If it caused a problem, then it could be reverted easily, if it needed to be completed, then it could be completed easily. Please note that the conversion didn't require a change in tests whatsoever and the logic is exactly the same. Meaning there was literally no functional change to the endpoints that were moved into their own file.
@Tengelma with that said, would you like the changes to be removed and have just constants in it's own file (or added to the main server startup if wanted, seems like a lot to throw in there, but up to you), or have the routes completed? It is easy to do either way. We discussed this change at the previous meeting so it seemed like something that should just be done whenever someone had the chance. Kind of like adding documentation. It is a simple refactor after all.

@aneuhold The main concern I have is that splitting things up in this way (1:1 route to file) and storing everything in a flat routes directory isn't really a huge improvement. Now file names are ambiguous and you have to go into the file to see what part of the application it interacts with. As an example, I have no idea what the 'create' file does until I look at it and say 'oh this is for models'. I have no idea what 'constants' does until I go in there and see 'oh this is just the defaults for all the different models'. The current single file format at least groups things by functionality and provides pretty clear documentation of what it does right next to the name of thing.
Imo, we probably want to break things up more by functionality --
model/ for crud endpoints
download/ for download endpoints
constants/ for constants endpoints
etc...
and that WOULD require changes to the tests on this end & changes to our front-end store to accommodate.
If we do do that, we'd also probably want to break utils up by those same contexts (makes it easier to extend) and keep init to a single 'blueprint' import & pure server initialization logic.
So I think there's a lot more work to do to do it right and it makes more sense to me to keep this PR relatively clean and focus on the acceptance criteria. Extending our utils file is fine and changes to documentation are welcome but I think route stuff should be relocated to another branch and demoed at our next Sprint planning. That work for you?

@Tengelma it seems like we are going to use blueprints regardless and split things up into separate files regardless, so this would be a good start. But oh well. Everything into one file it is. Working on it now.

@Tengelma just as a side note though, going back to a single file does make it very hard to reason about the code at the moment. So please start working on the refactor you are looking for soon. It is almost prohibitively difficult to work on more complex endpoints without some kind of allowance for abstraction or separation of concerns.

@Tengelma it seems like we are going to use blueprints regardless and split things up into separate files regardless, so this would be a good start. But oh well. Everything into one file it is. Working on it now.

I agree that its a good start and something we can build from which is why I'm suggesting you move these changes to another branch so we can still do that. Still outside the context of the User Story and still not enough thought or consistency put into to warrant inclusion in dev, imo. But that's just, like, my opinion, man. If you want to convince two other teammates to review and send it through, feel free to do so :man_shrugging:

@Tengelma just as a side note though, going back to a single file does make it very hard to reason about the code at the moment. So please start working on the refactor you are looking for soon. It is almost prohibitively difficult to work on more complex endpoints without some kind of allowance for abstraction or separation of concerns.

I can appreciate that the server is in need of a refactor and that it would help to get it done sooner rather than later. Could be something someone can tackle early next Sprint?
And I am not super opinionated on the specifics of how things should be structured but just want the pattern used to be something that's understandable and stable long-term. For real, if you have other good ideas on how that can be done or feedback on what I proposed, I'd love to hear it!

BTW, if you move the generate_constants function to utils (which seems fine as a home for it given the stuff currently in there), init.py only needs a few extra lines, which avoids a lot of your concerns about adding more complexity to that file while we figure routes out :sweat_smile:

@Tengelma it was reverted back to a single file per your request.


AMQP-840: RabbitTemplate add hook for timeouts

JIRA: https://jira.spring.io/browse/AMQP-840

To support that use case directly - there can be a variant of convertSendAndReceive() which passes messages to a Predicate until false is returned (true = continue, false = stop).

@panchenko True, but yikes!!, we already have 46 overloaded convertSendAndReceive() methods; we would have to double that.
Plus, this is a bit of a corner case - first time it's come up in 7+ years.


the home component

Value proposition
As a user,
**I want to navigate between four components.
**so that  i manage my workout and nutrition, and an overview about my statistics.
Description

Acceptance criteria

[ ] the Home button should lead to this component.

Complexity
Small | Medium | Large
Tasks

[ ] Create branch.
[ ] Setup Storybook for the home component.
[ ] Create four buttons that describe the four components of the app.
[ ] Create a home button that appears in all components.
[ ] Style the home component.

Hey Zakaria,
As already discussed, it would be better to implement this user story later on. I am looking forward to your new user stories :)


feat: create function to call execute_withdrawal

Feature Request
Describe the Feature Request
Create a function to execute execute_withdrawal function from satoru in withdrawal_handler contract.
Describe Preferred Solution
Add it as a function in src/keepers/common.rs

Hey, happy to try this one! 😁


Move tfenv to the right section

I believe tfenv should be listed under terraform and not opentofu.

@bajalnyt Thanks for the contribution!!


Add node-gyp build

[x] Add node-gyp config for Windows and Linux
[ ] Write README

error LNK2019: unresolved external symbol __imp_mg_duration_nanoseconds referenced in function "class Napi::Value __cdecl nodemg -> CHECK: https://docs.microsoft.com/en-us/cpp/build/importing-function-calls-using-declspec-dllimport?view=msvc-170&viewFallbackFrom=vs-2019


tests: i2s_state: Fix i2s_state_running_neg test

The current implementation would cause TX underflows thereby switching the TX channel state to I2_STATE_ERROR instead of I2S_STATE_RUNNING. This change removes the loop to check but still checks failure cases in the RUNNING state

@anangl - please review, as we are still able to merge test-only PRs

The current implementation would cause TX underflows thereby switching the TX channel state to I2_STATE_ERROR instead of I2S_STATE_RUNNING. This change removes the loop to check but still checks failure cases in the RUNNING state

I honestly don't see why the current implementation of this test case should cause TX underflows. This test case exists in this form for quite a while and there are drivers that pass it without problems. Perhaps there is an issue in that particular driver that fails this test case?


make qtop compatible with RHEL6

native yaml module now exists (largely untested but working)
lxml module only optional
replaced dict comprehensions with python 2.5 compatible code.


Flickering Mobile Respawns

Bug report

Basic Information

Mission version:
0.96.6
Map used:
Altis
Mods used:
CBA_A3, Vcom AI 3.3.3, LAMBS_Danger.fsm, LAMBS_RPG, LAMBS_Suppression, LAMBS_Turrets, CSW XM8 Pack, FA-18 Super Hornet, CROMOD VHS-2 Rifle, UTS-15 Shotgun, Specialist Military Arms, CZ BREN 2, Project Infinite - All in one, Project Infinite - Attachments CBA_A3, The CSAT Modification Project, The CSAT Modification Project (Replacement), RM Splinter Gear, Enhanced Soundscape, Enhanced Movement, Advanced Urban Rappelling, Advanced Sling loading, Advanced Towing, Advanced Rappelling, Arsenal Search, Walkable Moving Objects, VoyagerCompass HUD lite, Vana - Loadout Management (alpha), MRB Air Visiblity, MRB Vehicle Visibilty, Immerse, Ladder Tweak, Enhanced Video Settings.
Dedicated or local game:
Source of the mission file (URL):

https://steamcommunity.com/sharedfiles/filedetails/?id=878714108
Individual Things
Did you edit anything within the mission files?
No
If yes, what did you edit exactly?
N/A
Short Issue Description
Mobile Respawns such as the Huron or the Hemtt Medical dissapear and reapear on the map (Their icon will flicker in and out of existence on their position where they have been driven to), and then when trying to respawn, their entry in the respawn menu will flicker in and out.  Respawning is still possible but it requires awkward timing to double click the entry in the respawn menu, sometimes accidentally leading to respawning elsewhere and using up your Mobile respawn time out.
Note that this does not reliably happen all the time, to all players at the same time.  It is intermittent and seemingly random.
Expected Behaviour

To be able to spawn on the mobile respawn with no issues, and have no issues seeing the entry in the respawn menu.
Steps to Reproduce the Issue

Purchase mobile respawn
Drive to some location, near an objective such as a town
Die or manually force respawn
Go to respawn menu
Try to select Mobile respawn

Screenshots, Serverlog or any other helpful Information

Already fixed for next update.


my_configs.vim doesn't work in Docker Container

my_configs.vim for customizing my own style does not work in docker file
example: set number, set relativenumber and also doesn't work even after source .vim_runtime/my_configs.vim

Try to follow this comment and see if it works out 👍
https://github.com/amix/vimrc/issues/725#issuecomment-1685303723


Limit size of uploaded files

Is it possible to access to Multer, to restrict the size of uploaded files?

We provide request parsers as a convenience.  If you need to customize them, wire in the parser yourself with your own configuration.  Just make sure to use the same multer version swagger-tools provides.

Sorry for the late response. I am bit unsure on how you would do that without changing the files in the node_modules folder?

You would just install your handler in app.js and ensure that it runs before the swagger handlers. For example, I think with the version of multer that swagger-tools uses it would look something like:
SwaggerExpress.create(config, function(err, swaggerExpress) {
  if (err) { throw err; }

  var mult = require('multer')({/* your multer options */});
  app.use(mult);

  // install middleware
  swaggerExpress.register(app);

(BTW: All of this is the process of being rewritten without swagger-tools and will be exposing the parser configs directly.)

Awesome thanks. Will implement this.
Looking forward to the the changes :+1:


sync ingress status when status.loadbalancer is empty

I'm trying to add a test to this

prior to this change we get:
=== RUN   TestHostnames
([]v1.LoadBalancerIngress) <nil>
--- FAIL: TestHostnames (0.00s)
        albingress_test.go:36: A nil ingress status should result in hostname retrieval error
=== RUN   TestNewALBIngressFromIngress
--- PASS: TestNewALBIngressFromIngress (0.00s)
FAIL
FAIL    github.com/kubernetes-sigs/aws-alb-ingress-controller/internal/albingress       0.032s


Add {CPR}: {CIPHER}

[x] I understand that token listing is not required to use the Polygon Wallet with a token.

Please provide the following information for your token.
Token Name: CIPHER
Token Symbol: CPR
Decimals: 2
Polygon Address: 0xaa404804Ba583c025Fa64c9a276A6127CEB355c6
Ethereum Address:
Logo URI (svg):  https://cipher.com.co/Cipher2.png
Project Name: CIPHER CRYPTO TECHNOLOGIES
Project Summary: Cipher (CPR) is a utility token with the vision and the aim is to create transparency, accountability, and a safe business. All users/customers/investors/traders can participate in the project.
Project Contact<EMAIL_ADDRESS>Project Website: https://cipher.com.co/
Mainnet/Testnet: Polygon Main Network
Additonal Notes:

Dear team,
Kindly add our token CIPHER (CPR),further any information require write to us.
Thank you,
Cipher Team.


Hourly authentication "The authentication flow has completed."

(This has been driving me bananas - apologies in advance if this is not at all related to gcalcli. )
I've been using gcalcli in a custom übersicht widget for years that displays my daily calendar events on my desktop. In the last few weeks, it's started to re-authorize every hour.
Each time, it spawns a new browser window with the title "Authentication Status" and the message "The authentication flow has completed." - It's incredibly disruptive to my already infinitesimal attention span.
The url for this status usually looks something like:
http://localhost:8080/?code=4%2F0XXXXXXXX&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcalendar
I can see that my .gcalcli_oauth file (in my ~/ directory)  is updated hourly as well.
I've searched for others having similar issues, but it seems most are hitting a 7 day re-auth issue (which sounds like a much more appealing problem!). Again, this could be something else not related to gcalcli, but any help/guidance would be tremendous!

Can you make sure you're using the latest auth instructions from the README (with --client-id and such) and see if it's still an issue after I merged #683?


How to upload files in Partner service request?

Code here: https://msdn.microsoft.com/en-us/library/partnercenter/mt805812.aspx

hi @AnandKumar2610,
unfortunately we do not support upload files for service requests through API, the only way to upload files for a service request is through Partner Center website
Thanks,
Ali

thank you for your reply...
why its not supporting through API any security purpose ?

Hi Anand- we won't support this functionality through API and this is not related to security. we do few few things in the UI, and pass it to API- that piece is missing in the SDK, we may enable in the future but no concrete plans at the moment

Hi @jalendar5157 thank you for your reply. Finally no way to upload file through API correct ?

Hi @AnandKumar2610 ,
That is correct, at the moment it is not possible to upload a file related to support tickets through our APIs.
Thanks,
Ali

Hi @alidhia ,
Thank you for your reply!

Hi @alidhia , @jalendar5157  I have one question,
I have successfully created new customer using this api but suppose I'm going to create new customer through microsoft portal at a time how to call my web service from microsoft portal?
Is this possible ???
Thanks in advance

Anand

Hi, @AnandKumar2610
can you give more clarification about your scenario and what are you trying to do? also, since this is a different issue from uploading a file with a service request programmatically, please post your question in a new issue
Thanks,
Ali

Ok


bump go version to 1.19

There are a lot of projects that have been upgraded to 1.19, and it's time for us to upgrade too?

The go version directive in the go.mod file is unrelated to the version of Go used to build the project. We moved to Go 1.19 in our main branch already so this has no effect on the project's use of Go 1.19.

Yes, the Go version in the module is to indicate the minimum known compatible version of Go; while it's not enforced (older versions may work), it gives users an indication what versions of Go can be used to consume the module. As CI in this repository tests against 1.18 and 1.19 (recommendation is to support "latest" and "latest -1", which are the supported versions by Go), go1.18 would be the correct version to put in the go.mod; https://github.com/containerd/containerd/blob/5e51347a636b3b7a8730d2067c4337a16aa34113/.github/workflows/ci.yml#L241

Yes, the Go version in the module is to indicate the minimum known compatible version of Go; while it's not enforced (older versions may work), it gives users an indication what versions of Go can be used to consume the module. As CI in this repository tests against 1.18 and 1.19 (recommendation is to support "latest" and "latest -1", which are the supported versions by Go), go1.18 is the correct version to put in the go.mod;

It's reasonable,  we'll look at pr when go is updated to 1.20?

It's reasonable, we'll look at pr when go is updated to 1.20?

Yes; we can close this for now, but feel free to open a PR soon after a new Go release; you can find prior PRs when we update to make sure to change all the right locations where the Go version is defined (across several GitHub Actions yaml files and a few others places like contributed Dockerfile and Vagrant configuration).


Support allow_pickle in cupy.load and cupy.save

Fix #2289
TODO: NumPy 1.9 support

Jenkins, test this please.

Jenkins CI test (for commit a229861b3537a56372a632a15869b7a304bd8a18, target branch master) failed with status FAILURE.

When backporting, change the default behavior of allow_pickle to True in cupy.load.

Jenkins, test this please.

Jenkins CI test (for commit f59e96283a7bd56a4d071b78d0677e0834d5e4fc, target branch master) succeeded!

LGTM.


[BUG] - Unify frame time

Frame time can very, it should be consistent between rounds.

@oconn is there a way for me to test this best?


Ordering of results is broken in 3.7.7

After upgrading to 3.7.7 I can no longer order results by clicking on arrows in column headers. I click and nothing happens.

Correction - ordering does not work only when there are more rows than are loaded initially. Maybe this issue existed prior to 3.7.7 as well, not sure.

Order result set confirmation is set to "Always"

This is a bug in one of recent versions. Thanks for report.
Actually ordering happens but it is not visualized in column header.
Workaround: to click in descending order use ALT+click. Also you can use filter dialog.


Issues concerning dequatorial_radius interval using fit_ellipse() method

Hello,
I am doing an ellipse fitting for a 5 positive occultation observations. I am trying to fit an ellipse using the fit_ellipse() method on sora.occultation but depending on the optimization method used I have a different result regarding the equatorial radius.
I fixed equatorial_radius = 2410.3 km and dequatorial_radius = 1.5 km
Results using "least_square" or "differential_evolution" method:
equatorial_radius:
1-sigma: 2407.325 +/- 0.000
3-sigma: 2407.418 +/- 0.105
Here the result is out of the given interval [2408.8,2411.8]
Results using "chisqr" method:
equatorial_radius:
1-sigma: 2408.824 +/- 0.023
3-sigma: 2408.908 +/- 0.108
Can we explain this difference by scipy_optimization methods (used in least_square and differential_evolution methods)?
Thanks

Hi Raph65,
There is a fundamental difference between chisqr and the methods based on SciPy. The 'chisqr' approach relies on Monte Carlo simulations, meaning that with a sufficient number of iterations or guesses, you can achieve a value similar to what would be obtained using the convergence techniques employed by SciPy's least_squares and differential_evolution methods. While 'chisqr' provides a probabilistic approximation through repeated random sampling, SciPy's methods use deterministic algorithms to systematically converge on an optimal solution.
However, it's important to note that while the convergence methods are effective in finding the best solution, 'chisqr' is still used to compute the error bars. Therefore, when using this approach, it's crucial to carefully consider the appropriate range for parameters, especially since some error bars might be too small, potentially leading to inaccurate interpretations.
For questions like these, please feel free to use our Slack channel. For software-related issues, we prefer that you raise them via GitHub issues.

HI Rodrigo,
Thanks for your quick answer, I understand know. It s then better to adapt parameters to use « ls » or « de » methods even if they are not physically accurate at the beginning ?
Concerning the Slack channel thank you for sharing and sorry for the confusion, do you want me to delete my question on Github it is not a problem for me.
Sincerely,
Raphaël

Le 12 août 2024 à 16:13, Rodrigo Boufleur @.***> a écrit :
Hi Raph65,
There is a fundamental difference between chisqr and the methods based on SciPy. The 'chisqr' approach relies on Monte Carlo simulations, meaning that with a sufficient number of iterations or guesses, you can achieve a value similar to what would be obtained using the convergence techniques employed by SciPy's least_squares and differential_evolution methods. While 'chisqr' provides a probabilistic approximation through repeated random sampling, SciPy's methods use deterministic algorithms to systematically converge on an optimal solution.
However, it's important to note that while the convergence methods are effective in finding the best solution, 'chisqr' is still used to compute the error bars. Therefore, when using this approach, it's crucial to carefully consider the appropriate range for parameters, especially since some error bars might be too small, potentially leading to inaccurate interpretations.
For questions like these, please feel free to use our Slack channel https://join.slack.com/t/sora-grupo/shared_invite/zt-16cuhoa81-oX29_r78RQX1WefKaeeTwg. For software-related issues, we prefer that you raise them via GitHub issues.
—
Reply to this email directly, view it on GitHub https://github.com/riogroup/SORA/issues/92#issuecomment-2284102322, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFF3K4O5NM3RDY2VNUE2MODZRC7JZAVCNFSM6AAAAABMMHHZG2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBUGEYDEMZSGI.
You are receiving this because you authored the thread.

Hi Raphaël,
I’m not entirely sure I fully grasp your question, but here are my thoughts on when each method might be more appropriate. Convergence methods, like least_squares and differential_evolution, are generally much faster than Monte Carlo simulations. However, they can sometimes get stuck in local minima during the convergence process. While this is rare in the context of SORA, it could happen with lower-quality data. Despite this, these methods are usually the most straightforward way to find the best-fit parameters.
On the other hand, the chisqr method has the advantage of always finding the best-fit region, though it comes at the cost of longer computation times. Additionally, it’s used to estimate the uncertainty in the parameters, which provides context for how meaningful the best fit is, regardless of the method used.
So, a combination of both approaches might be the most efficient choice. Experimenting with both methodologies could also give you a better perspective on which is more suitable for your specific case, especially when analyzing the chi-square maps that are generated.
As for your GitHub question, there’s no need to delete it. It’s valuable for the community and might help others who have similar inquiries.

Hi Raphaël,
That does indeed sound like strange behavior, especially if the case is with the differential_evolution method that by design only works if bounds are provided. Please reach out to me in the Slack channel so I can provide more specific support for your case.


[web] Customize path of index.html and/or web directory.

Use case
I am running multiple flutter apps in the same repo by specifying the main.dart file
flutter build web -t lib/appOne/appOne.dart
flutter build web -t lib/appTwo/appTwo.dart

These apps share quite a bit of code, which is why I was doing it this way. So this works great. Now the issue is, I was using the flutter-web splashscreen trick of editing the HTML file so that the user does not have to wait for the app to load to see something. Now that I have multiple apps, it would be nice to specify the HTML file name on run or build. This way I can have separate splash screens per app.
I have not found too much information about what I am trying to do. I think for now I will create three separate html files and just copy them into index.html using a script before running or building.

Proposal
Be able to specify an optional html file path when building or running a flutter-web app.
flutter build web -t lib/appOne/appOne.dart --htmlPath web/appOne.html

I have not yet dove into flutters source code to see how/if this could be possible yet but I will do so soon.

:))) same issue

I think this is a "new feature", but I'd love to have it for some of our tests where we use slightly different variations of the index.html. Good call!

I don't have time to work on this for now, but here's some info that I've learned from working on the flutter tooling for web:

flutter run and flutter build use different code paths

flutter run: https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/isolated/resident_web_runner.dart
flutter build: https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/build_system/targets/web.dart

flutter run uses an in-memory filesystem, whereas build writes files to disk
index.html is a magic name in a bunch (quite a lot) of places, and is modified "on the fly" when doing build (to inject some build metadata. This probably needs to be configurable.
the output of a dart build is always main.dart.js, unless that is customized, builds with different commands will produce incompatible outputs (different builds with different input parameters will produce outputs with same names: index.html, main.dart.js, flutter_service_worker.js...

we have a new API for the initialization of flutter that would let an index.html, here.

@abegehr had a nice extension to this idea in the proposal I linked above (#103777), having completely separate web directories:

app

lib

main.dart
admin_main.dart

web

index.html

web_admin

index.html

The commands would be:

flutter build web -t lib/main.dart --webRoot web (produces a build/web directory)
flutter build web -t lib/admin_main.dart --webRoot web_admin (produces a build/web_admin directory)

I have some concerns with regards to this approach, for example: what to do with the different assets that are globally available (and now, copied straight to the output web directory) and things like that, but I think being able to specify the whole "web" directory is a good extension to this feature request!

+1
Thank you for merging the FRs, @ditman! Specifying web-root is essential for build flavors on web that effect the web directory: manifest.json, app icon, html metadata tags, ...

I really need this feature to handle flavors in flutter web

Ditto - I build different flavours of the app for different environments (dev, qa, prod etc) and would really like to change the name in manifest.json to be dependent on the flavour.


Feature Request: Define functions for numeric values of AVALC

Feature Idea
Functions should be defined for numeric values of AVALC:

[ ] For "CR", "PR", "SD", "NON-CR/NON-PD", "PD", "NE" values 1 to 6 should be used (for derivation of AVALN for response values).
[ ] For "Y" and "N" values 1 and 0 respectively should be used (for derivation of AVALN for binary response values).
[ ] For  'PD', 'NE', 'NON-CR/NON-PD', 'SD', 'PR', 'CR' values 1 to 6 should be used (for selecting worst response if there is more than one per date).

If implemented the class from https://github.com/pharmaverse/admiral/issues/1021, should be used.
Relevant Input
What should the input look like? REMINDER: no patient level data or company sensitive information should be shared via this open public issue
Relevant Output
What should the output look like? REMINDER: no patient level data or company sensitive information should be shared via this open public issue
Reproducible Example/Pseudo Code
We love example code and it will speed up the process! REMINDER: no patient level data or company sensitive information should be shared via this open public issue

@bundfussr do you see this as still needed with the ADRS workflow? let me know and i can add it in if so. i think the worst order at least is probably no longer needed here.

I am not sure. It could be helpful to ensure that the derivation of AVAL is consistent.
Worst order is not used in admiralonco. Should we move it to admiralroche?
The second one is not onco specific. Should we move it to admiral core?

@bundfussr in hindsight we probably cant make a decision on this until we get a decision from the core leads on whether we'll implement get_map() or just let the user define their own function using case_when(). let me know the resolution of that one from the Q&A meets you have at core team and then we could make a call on this one. whichever way i'm not really seeing anything needed for admiralonco here as we dont use AVAL in any of the derivation functions, and in our Step1 of ADRS workflow we're clear such pieces are done by the user as pre-processing.

ON HOLD for now as explained above - not needed for foundational release of {admiralonco}

Not needed anymore.


Add optional count argument to Semaphore::post

Implements a new optional argument in Semaphore.post to allow resuming multiple threads at once.

May I ask in what occasion would this be useful? It is a relatively innocent change, but it's still worth knowing why it would need to be done.

It's just so you dont have to do a for loop anymore to resume more and more threads, and it would be way more optimized than constantly locking and unlocking the mutex, adding 1 to the count and running notify_one.

Was a named method considered (post_n or something)? Not sure what's the usual API design in such cases.

The co-author additions for just reviews aren't necessary by the way, feel free to remove them

I think we can safely push this to 4.4 . Still waiting on the GDExtension and DotNet teams for review.

Thanks!

I've found something a bit concerning... One of my PRs was tested against 4.3, where it worked. On master it broke. The reason was that on master I had to add .bind(1) to a Callable to core_bind::Semaphore::post(); otherwise, I would get too-few-args error. On 4.3, adding the .bind(1) makes the code fail with too-many-args error. Therefore, there's a compat breakage here. Or is the reason that we have an issue with the binding-call system not honoring the default arg in case the .bind(1) is missing?

It's been discussed (forget where) and I've looked at some tricks to make it easier by creating a custom callable from a MethodBind but haven't done much on it as it's a bit convoluted, and would require fetching the method (also wouldn't work with non-bound methods, though we could use the bind without using the ClassDB system)
But will see about opening some issue to track it and look at ideas when I can

If this is a severe problem reverting this PR should be fine as it's a relatively small Quality-of-Life feature.


Sudoku: Generation does not finish

The sudoku generation sometimes takes to long such that the apple counter needs to break the loop and therefore no valid sudoku is generated. Either remove the apple counter or restart the process in case the algorithm takes to long.

Done with commit: 3fdaa211792fafc27c7f481da16fa8c98f29f614
The algorithm for generating the sudoku was improved slightly.
By iterating the empty cells from right to left while solving it was possible to speed up the process a little bit (no measurements were taken).
The improvement originates from the third quad that is to be filled. When filling from top right to bottom left, the third quad has 9 cells from which to take information, reducing the amount of possible entries. While using the left to right approach would only yield 6 cells for the third quad. The idea is to also use the new data that the quads provide that were filled by the algorithm.


Support service class declarations

Description:
service class {
   *ServiceType;

}

Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Closing since this was added.


we can not play video

Unfortunately, you did not provide enough information for me to help you. Please have a look at how to submit an issue.

No reply from original poster, so I’m closing the issue.


Hosting

We should look into hosting (preferably free hosting with CI/CD support)
We could use Shuttle as we fit nicely in their free tier, but there are loads of other platforms we can look into.

I've started to look into this, looks viable even though it adds three more dependencies.