Harvester does not install

I attempted to install Harvester on a Dell SN 5000, which boasts an impressive range of specifications including an AMD EPYC Series Processor with up to 64 cores and 128 threads, PCIe Gen 4 I/O, extensive storage options with 15TB M.2 NVMe, a maximum of 512GB DDR4 memory, and advanced networking capabilities including 10Gbps Ethernet and optional configurations for traffic ingest exceeding 33 Gbps. Despite these robust features, I encountered persistent issues during the installation process.
Harvester failed to detect a DHCP server on the network, leading me to set up a static IP. Additionally, it was unable to locate an NTP server, regardless of whether I used the default settings or specified a domain name or IP address. This resulted in an error message indicating the absence of an NTP server. Progress stalled during the installation at the "rke2-images.linux-amd64-v1.25.9-rke2r1.tar.zst" step, as evidenced in the attached file, and remained there for an entire day.

Subsequently, I initiated a reset, which led to the display shown in the second attached file.

This issue is a significant roadblock, especially considering my position at the Department of Defense, where I am exploring Harvester as a potential alternative to ESXi. Any guidance on resolving these installation challenges would be greatly appreciated. Thank you.

Here are some screen shots of the console.log file:
At the top:

At the middle:

At the bottom:

The content looks pretty much the same throughout the log file.

Wanted to say I accidently pushed the close button - I tried to push the comment button but I thought it did not post. This issue is not closed.

Hey! I’m Brian, a solutions architect at RGS. Would love to chat with you and get you unblocked. Can also provide some tips around harvester and how several customers in the DoD are already leveraging it successfully.
shoot me an email at<EMAIL_ADDRESS>

@ThomasGLAllen

Did the interfaces show as Up in the installer? You'll get a list of interfaces and those plugged would show UP.
If the interfaces were up and you selected those for the mgmt network, then we need to ensure the VLAN and network is indeed configured correctly.

Hopefully Brian can help you further.

Yes, all the interface prompts showed up in the installer for the installation if that is what you’re talking about, in other words after you select the harvester iso it gave me “Harvester Installer v1.2.0”, choose installation mode, etc. My vlan is configured correctly. Harvester just stays at the “Status: Setting up Harvester” and “Status: Setting up node” screen. It still says that the Management URL is unavailable.
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Alejandro @.>
Sent: Wednesday, November 15, 2023 11:04 AM
To: @.>
Cc: @.>; @.>
Subject: Re: [harvester/harvester] Harvester does not install (Issue #4728)
@ThomasGLAllenhttps://github.com/ThomasGLAllen

Did the interfaces show as Up in the installer? You'll get a list of interfaces and those plugged would show UP.
If the interfaces were up and you selected those for the mgmt network, then we need to ensure the VLAN and network is indeed configured correctly.

Hopefully Brian can help you further.
—
Reply to this email directly, view it on GitHubhttps://github.com/harvester/harvester/issues/4728#issuecomment-1812923297, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALPKUMICFAU6ZMMFVVUOKM3YETYYDAVCNFSM6AAAAAA7L5ZVSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJSHEZDGMRZG4.
You are receiving this because you were mentioned.Message ID: @.***>

I also would like to know who in industry or what government agencies are presently using Harvester. Just curious.
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Thomas @.>
Sent: Wednesday, November 15, 2023 11:19 AM
To: @.>; @.>
Cc: @.>
Subject: RE: [harvester/harvester] Harvester does not install (Issue #4728)
Yes, all the interface prompts showed up in the installer for the installation if that is what you’re talking about, in other words after you select the harvester iso it gave me “Harvester Installer v1.2.0”, choose installation mode, etc. My vlan is configured correctly. Harvester just stays at the “Status: Setting up Harvester” and “Status: Setting up node” screen. It still says that the Management URL is unavailable.
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Alejandro @.>
Sent: Wednesday, November 15, 2023 11:04 AM
To: @.>
Cc: @.>; @.>
Subject: Re: [harvester/harvester] Harvester does not install (Issue #4728)
@ThomasGLAllenhttps://github.com/ThomasGLAllen

Did the interfaces show as Up in the installer? You'll get a list of interfaces and those plugged would show UP.
If the interfaces were up and you selected those for the mgmt network, then we need to ensure the VLAN and network is indeed configured correctly.

Hopefully Brian can help you further.
—
Reply to this email directly, view it on GitHubhttps://github.com/harvester/harvester/issues/4728#issuecomment-1812923297, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALPKUMICFAU6ZMMFVVUOKM3YETYYDAVCNFSM6AAAAAA7L5ZVSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJSHEZDGMRZG4.
You are receiving this because you were mentioned.Message ID: @.***>

Feel free to reach out to me at @.***
On Wed, Nov 15, 2023 at 1:09 PM ThomasGLAllen @.***>
wrote:

I also would like to know who in industry or what government agencies are
presently using Harvester. Just curious.
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for
Windows 10
From: Thomas @.>
Sent: Wednesday, November 15, 2023 11:19 AM
To: @.>; @.>
Cc: @.>
Subject: RE: [harvester/harvester] Harvester does not install (Issue
#4728)
Yes, all the interface prompts showed up in the installer for the
installation if that is what you’re talking about, in other words after you
select the harvester iso it gave me “Harvester Installer v1.2.0”, choose
installation mode, etc. My vlan is configured correctly. Harvester just
stays at the “Status: Setting up Harvester” and “Status: Setting up node”
screen. It still says that the Management URL is unavailable.
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for
Windows 10
From: Alejandro @.>
Sent: Wednesday, November 15, 2023 11:04 AM
To: @.>
Cc: @.>; @.>
Subject: Re: [harvester/harvester] Harvester does not install (Issue
#4728)
@ThomasGLAllenhttps://github.com/ThomasGLAllen

Did the interfaces show as Up in the installer? You'll get a list of
interfaces and those plugged would show UP.
If the interfaces were up and you selected those for the mgmt network,
then we need to ensure the VLAN and network is indeed configured correctly.

Hopefully Brian can help you further.
—
Reply to this email directly, view it on GitHub<
https://github.com/harvester/harvester/issues/4728#issuecomment-1812923297>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/ALPKUMICFAU6ZMMFVVUOKM3YETYYDAVCNFSM6AAAAAA7L5ZVSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJSHEZDGMRZG4>.
You are receiving this because you were mentioned.Message ID: @.***>
—
Reply to this email directly, view it on GitHub
https://github.com/harvester/harvester/issues/4728#issuecomment-1813106482,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJGAH5G2I6IB7IHGDHVREN3YEUHNVAVCNFSM6AAAAAA7L5ZVSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJTGEYDMNBYGI
.
You are receiving this because you commented.Message ID:
@.***>

This issue is still known valid on SN5000 hardware.
On Sun, Jan 14, 2024 at 9:10 PM github-actions[bot] <
@.***> wrote:

This repository uses an automated workflow to automatically label issues
which have not had any activity (commit/comment/label) for 60 days. This
helps us manage the community issues better. If the issue is still
relevant, please add a comment to the issue so the workflow can remove the
label and we know it is still valid. If it is no longer relevant (or
possibly fixed in the latest release), the workflow will automatically
close the issue in 14 days. Thank you for your contributions.
—
Reply to this email directly, view it on GitHub
https://github.com/harvester/harvester/issues/4728#issuecomment-1891194545,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJGAH5FNAKJQREX3MIRBV4TYOSFX5AVCNFSM6AAAAAA7L5ZVSCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJRGE4TINJUGU
.
You are receiving this because you commented.Message ID:
@.***>

I'm having the same problem while attempting to install a new cluster (version 1.1.3) on Cisco gear.  I tried the installation on a Cisco C220 and a C240.  Both systems stall at the same place, with no helpful information in the console.log file, apart from what is displayed in the screenshot.
I'm wondering if this issue could be related to some rsync processes running in the background that never seem to complete.  These have been running for ~12 hours:
root      3825  3486  0 Jan24 tty1     00:00:06 rsync -ah --progress /run/initramfs/live/bundle/harvester/images/ /run/cos/target//var/lib/rancher/tmp/images root      3826  3825  0 Jan24 tty1     00:00:00 rsync -ah --progress /run/initramfs/live/bundle/harvester/images/ /run/cos/target//var/lib/rancher/tmp/images root      3827  3826  0 Jan24 tty1     00:00:13 rsync -ah --progress /run/initramfs/live/bundle/harvester/images/ /run/cos/target//var/lib/rancher/tmp/images

This is such a major issue, a huge bug with Harvester. how could this issue be closed?

This is such a major issue, a huge bug with Harvester. how could this issue be closed?

Issues are closed automatically if there was no activity for a specific time.
Does the error still occur for you with the latest Harvester 1.3.1, 1.3.2 (RC) or 1.4 (dev)?


Integration: Publisher can choose a dataset from dropbox and start an upload

Placeholder for any required FE-BE integration.
TEAM COMMENTS

feature flags are: cc=true and auth=true
I think it's currently working in development env, and we're waiting to deploy to staging on Wednesday for QA!

QA steps once in staging:

Use this feature flag enabled staging link: https://cellxgene.staging.single-cell.czi.technology/?cc=true&auth=true
Log into your account
If you already have collections, click on My Collections link to a access a collection page
Once you're on a collection page, click on "Add dataset from Dropbox" to start the upload flow

Thank you!

I'll do this ticket along with #642! Thank you!

Deployed to staging and can confirm that it's working in staging. But @brianraymor please feel free verify too as product owner (QA steps in ticket description) 🙏 Thank you!

Deployed to staging and can confirm that it's working in staging. But @brianraymor please feel free verify too as product owner (QA steps in ticket description) 🙏 Thank you!

Confirmed working in prod! Closing!


Use healthcheck to get weblog info in nodejs

Motivation
#2799
Changes

Workflow

⚠ Create your PR as draft ⚠
Work on you PR until the CI passes (if something not related to your task is failing, you can ignore it)
Mark it as ready for review

Test logic is modified? -> Get a review from RFC owner. We're working on refining the codeowners file quickly.
Framework is modified, or non obvious usage of it -> get a review from R&P team

:rocket: Once your PR is reviewed, you can merge it!
🛟 #apm-shared-testing 🛟
Reviewer checklist

[ ] If PR title starts with [<language>], double-check that only <language> is impacted by the change
[ ] No system-tests internal is modified. Otherwise, I have the approval from R&P team
[ ] CI is green, or failing jobs are not related to this change (and you are 100% sure about this statement)
[ ] A docker base image is modified?

[ ] the relevant build-XXX-image label is present

[ ] A scenario is added (or removed)?

[ ] Get a review from R&P team

@cbeauchesne Does this support parametric tests? It looks like parametric tests are still looking for a file to be present in the image and not in the container.

No, it's only working for end-to-end scenarios.


Improved Terragrunt Provider Cache logs

Description
Improved Terragrunt Provider Cache logs.

TODOs
Read the Gruntwork contribution guidelines.

[ ] Update the docs.
[x] Run the relevant tests successfully, including pre-commit checks.
[ ] Ensure any 3rd party code adheres with our license policy or delete this line if its not applicable.
[ ] Include release notes. If this PR is backward incompatible, include a migration guide.

Release Notes (draft)

Added / Removed / Updated [X].
Migration Guide

@denis256, thanks for the review!


Data streaming using chunks

Known issues in this PR:

[x] There are no get frame REST API methods.

[x] Crash browser tab on 4k video after several navigation events (Possible solution: change the size of the decoded frames buffer dynamically).

[x] Some number of  fast clicks (>10-20) on the navigation bar leads to the corresponding number of chunk request. Decoding begins after all requests have finished. Possible solution: implement the same logic as for cvat-data (process only the last request).

[x] Build instruction for avc.wasm and Decoder.js as first step and dockerized build as final solution.

[x] There are no access to original quality chunks and frames.

[ ] Need to check the creation task time for both case (images and video) and compare with current version.

[ ] Estimate network traffic for new and old version on the same data.

[ ] Add small-size preview for the navigation slider.

[x] Video playback is not smooth - player freezes and skips some frames after that. Partially fixed. Need to implement a buffering on the player side to make playback more smoothly.

[x] Player issue: now player is requiring frames every 1/25s. It may leads to the following case: the frame which requested later will be received by the player earlier. (If decoder works slow on the large frame resolution).

[x] Decoder potentially may has performance problems and decoding speed may be not enough to play the video smoothly, especially on the high resolution videos. Solution: use downscaled images on the backend and upscale on the frontend. Implemented https://github.com/ygnn123/cvat/pull/7/files

[ ] Don't create decoder worker threads for each chunk, it leads to extra server requests, etc. (Checked: h264 decoder works fine).

[x]  Access to the original data for old tasks issue (data migration)

[x] Cleanup code, fix codacy issues.

[x] auto_segmentation, reid and datumaro are broken

[x] compressed and original data contains incorrect data

@azhavoro , the server part looks good. I will test/debug on Friday but I don't have any critical comments for code now.

Let's update CONTRIBUTING.md
Add step:
cd ../cvat-data && npm install

before starting UI server

Also need to add a statement into CONTRIBUTING.md about av libraries
  File "/Users/nmanovic/Workspace/cvat/cvat/urls.py", line 28, in <module>
    path('', include('cvat.apps.engine.urls')),
  File "/Users/nmanovic/.virtualenvs/cvat/lib/python3.7/site-packages/django/urls/conf.py", line 34, in include
    urlconf_module = import_module(urlconf_module)
  File "/Users/nmanovic/.virtualenvs/cvat/lib/python3.7/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
  File "<frozen importlib._bootstrap>", line 983, in _find_and_load
  File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 728, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/Users/nmanovic/Workspace/cvat/cvat/apps/engine/urls.py", line 7, in <module>
    from . import views
  File "/Users/nmanovic/Workspace/cvat/cvat/apps/engine/views.py", line 32, in <module>
    from . import annotation, task, models
  File "/Users/nmanovic/Workspace/cvat/cvat/apps/engine/task.py", line 15, in <module>
    from cvat.apps.engine.media_extractors import get_mime, MEDIA_TYPES, Mpeg4ChunkWriter, ZipChunkWriter, Mpeg4CompressedChunkWriter, ZipCompressedChunkWriter
  File "/Users/nmanovic/Workspace/cvat/cvat/apps/engine/media_extractors.py", line 13, in <module>
    import av
  File "/Users/nmanovic/.virtualenvs/cvat/lib/python3.7/site-packages/av/__init__.py", line 9, in <module>
    from av._core import time_base, pyav_version as __version__
ImportError: dlopen(/Users/nmanovic/.virtualenvs/cvat/lib/python3.7/site-packages/av/_core.cpython-37m-darwin.so, 2): Library not loaded: /usr/local/opt/openssl/lib/libssl.1.0.0.dylib
  Referenced from: /usr/local/opt/ffmpeg/lib/libavfilter.7.dylib
  Reason: image not found

[ ] compressed and original data contains incorrect data

compressed:

original:

Probably we want to have original file names. Need to think about that at least. In general there are two possible approaches:

frameN.jpeg and has mapping inside meta information frameN -> filename
use filename (in this case for videos we will have its name as directory and inside 0.jpeg, 1.jpeg, ...). The similar strategy can be applied for pdfs. We can think that an archive is a directory as well.

@azhavoro , what is the status of the PR? Please resolve conflicts.

@azhavoro , what is the current status. Did we test the patch internally? Can we merge it already? What is the plan?

@azhavoro , what is the current status. Did we test the patch internally? Can we merge it already? What is the plan?

@nmanovic We tested the patch internally, I suggest merge it after we will migrate all data.

@azhavoro , need to resolve conflicts

@azhavoro , could you please resolve the conflict and I will merge the branch into develop.

@azhavoro , please send fix with preview and progress into develop branch after that.

To install av package under windows do either:

conda install av -c conda-forge
Manual install:# download shared and dev packages of ffmpeg: https://ffmpeg.zeranoe.com/builds/
# download https://github.com/mikeboers/PyAV, move to the dir
python setup.py build --ffmpeg-dir=C:\ffmpeg
python setup.py install
# possibly, copy DLL libraries to venv\Lib\site-packages\av<...>.egg\av


⚠ Bofrost.lu has degraded performance

In 03cb9bf, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2447 ms

Resolved: Bofrost.lu performance has improved in 94981a1 after 17 minutes.


 I grouped methods into categories and gave each category a new module file. It might need more refactors down the line.

Story is pretty big and this split is something I wanted to do, so, thanks for this PR! I will review it ASAP.

Thank you. Sorry the diff is so long.

(Rebased onto the updated main branch.)


Esrally command broken on Windows because of invalid default logging configuration

Rally version (get with esrally --version):
Latest? (esrally --version fails)
Invoked command:
any esrally command (for example esrally configure)
Configuration file (located in ~/.rally/rally.ini)):
Not yet created
JVM version:
1.8
OS version:
Windows 10 Pro version 1803
Description of the problem including expected versus actual behavior:
The esrally command fails to run due to invalid escape in %userprofile%\.rally\logging.json on line 23.  This error occurs because esrally attempts to mix Windows and Linux paths and does not escape the \ in Windows paths.  Ideally the generated logging.json should use the local systems path separator and properly escape it.
Steps to reproduce:

Open an administrator prompt in c:\Program Files\Python36\Scripts
Run .\pip install esrally
Run .\esrally configure (or any other esrally command)
It errors due to an invalid escape on line 23

Provide logs (if relevant):
Line 23 reads as follows:
"filename": "C:\Users\mhardy\.rally\logs/rally.log",
Traceback (most recent call last):
  File "c:\program files\python36\lib\runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "c:\program files\python36\lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "C:\Program Files\Python36\Scripts\esrally.exe\__main__.py", line 9, in <module>
  File "c:\program files\python36\lib\site-packages\esrally\rally.py", line 487, in main
    log.configure_logging()
  File "c:\program files\python36\lib\site-packages\esrally\log.py", line 90, in configure_logging
    logging.config.dictConfig(load_configuration())
  File "c:\program files\python36\lib\site-packages\esrally\log.py", line 61, in load_configuration
    return json.load(f)
  File "c:\program files\python36\lib\json\__init__.py", line 299, in load
    parse_constant=parse_constant, object_pairs_hook=object_pairs_hook, **kw)
  File "c:\program files\python36\lib\json\__init__.py", line 354, in loads
    return _default_decoder.decode(s)
  File "c:\program files\python36\lib\json\decoder.py", line 339, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "c:\program files\python36\lib\json\decoder.py", line 355, in raw_decode
    obj, end = self.scan_once(s, idx)
json.decoder.JSONDecodeError: Invalid \escape: line 23 column 22 (char 688)

@danielmitterdorfer, @michardy,
I still was digging a little about this topic.
I found after installation the logging configuration template is being written into directory
\Lib\site-packages\esrally\resources\logging.json
The culprits in this JSON file are the two places for filename under
rally_log_handler
rally_profile_handler
I just replaced there the slashes with backslashes.
Then after starting esrally under windows, this template was copied into path %USERPROFILE%.rally and rally started working.
If I understand the whole thing correctly, then the file logging_1_0_0.json is again used for generating the logging.json, which holds the following content in my case for filename:
rally_log_handler ${LOG_PATH}/rally.log
rally_profile_handler ${LOG_PATH}/profile.log
And the solution could be to correct the variable $LOG_PATH.
A fix could be in this block of log.py
`def remove_obsolete_default_log_config():
"""
Log rotation is problematic because Rally uses multiple processes and there is a lurking race condition when
rolling log files. Hence, we do not rotate logs from within Rally and leverage established tools like logrotate for that.
Checks whether the user has a problematic out-of-the-box logging configuration delivered with Rally 1.0.0 which
used log rotation and removes it so it can be replaced by a new one in a later step.
"""
log_config = log_config_path()
if io.exists(log_config):
    source_path = io.normalize_path(os.path.join(os.path.dirname(__file__), "resources", "logging_1_0_0.json"))
    with open(source_path, "r", encoding="UTF-8") as src:
        contents = src.read().replace("${LOG_PATH}", default_log_path())
        source_hash = hashlib.sha512(contents.encode()).hexdigest()
    with open(log_config, "r", encoding="UTF-8") as target:
        target_hash = hashlib.sha512(target.read().encode()).hexdigest()
    if source_hash == target_hash:
        os.rename(log_config, "{}.bak".format(log_config))

def install_default_log_config():
"""
Ensures a log configuration file is present on this machine. The default
log configuration is based on the template in resources/logging.json.
It also ensures that the default log path has been created so log files
can be successfully opened in that directory.
"""
log_config = log_config_path()
if not io.exists(log_config):
    io.ensure_dir(io.dirname(log_config))
    source_path = io.normalize_path(os.path.join(os.path.dirname(__file__), "resources", "logging.json"))
    with open(log_config, "w", encoding="UTF-8") as target:
        with open(source_path, "r", encoding="UTF-8") as src:
            contents = src.read().replace("${LOG_PATH}", default_log_path())
            target.write(contents)
io.ensure_dir(default_log_path())`

and replace it with this block
at the beginning:
import platform
and the places before:
`def remove_obsolete_default_log_config():
"""
Log rotation is problematic because Rally uses multiple processes and there is a lurking race condition when
rolling log files. Hence, we do not rotate logs from within Rally and leverage established tools like logrotate for that.
Checks whether the user has a problematic out-of-the-box logging configuration delivered with Rally 1.0.0 which
used log rotation and removes it so it can be replaced by a new one in a later step.
"""
log_config = log_config_path()
log_platform = platform.system()
if io.exists(log_config):
    source_path = io.normalize_path(os.path.join(os.path.dirname(__file__), "resources", "logging_1_0_0.json"))
    with open(source_path, "r", encoding="UTF-8") as src:
        if log_platform == "Windows":
            contents = src.read().replace("${LOG_PATH}", default_log_path()).replace('\\','/')
        else:
            contents = src.read().replace("${LOG_PATH}", default_log_path())
        source_hash = hashlib.sha512(contents.encode()).hexdigest()
    with open(log_config, "r", encoding="UTF-8") as target:
        target_hash = hashlib.sha512(target.read().encode()).hexdigest()
    if source_hash == target_hash:
        os.rename(log_config, "{}.bak".format(log_config))

def install_default_log_config():
"""
Ensures a log configuration file is present on this machine. The default
log configuration is based on the template in resources/logging.json.
It also ensures that the default log path has been created so log files
can be successfully opened in that directory.
"""
log_config = log_config_path()
log_platform = platform.system()
if not io.exists(log_config):
    io.ensure_dir(io.dirname(log_config))
    source_path = io.normalize_path(os.path.join(os.path.dirname(__file__), "resources", "logging.json"))
    with open(log_config, "w", encoding="UTF-8") as target:
        with open(source_path, "r", encoding="UTF-8") as src:
            if log_platform == "Windows":
                contents = src.read().replace("${LOG_PATH}", default_log_path()).replace('\\','/')
            else:
                contents = src.read().replace("${LOG_PATH}", default_log_path())
            target.write(contents)
io.ensure_dir(default_log_path())

This could be one approach at generation level. Or otherwise the log_config_path and default_log_path and maybe other places with.replace('\','/')`

What do you mean?

Ok, think I get it, now are next difficulties with tracks, after fixing this, there were errors finding the templates. So it seems there is gonna be a lot to do to fix this...

@littlesnitch thanks for looking into this. Apart from what you found out, there are other problems on Windows as well. I am specifically thinking of the internal communication between Rally components. As you can distribute Rally, e.g. to support use-cases that require to generate load from multiple machines, we use an actor system internally. I did some tests a while ago and ran into all sorts of stability issues with it. We will likely do something about this in the mid-term but this will require quite a few changes.

Ok, thank you for you answer. I understand.


[Nintendo DS] Compilation clones?

Atlantic Quest + Galactic Quest (Europe) (En,Fr,De,Nl)
Jewel Link Double Pack (Europe)

These two games are both compilations, but also both clones of each other. Both are tagged as compilations of their respective individual games in clone lists, and the individual ones get filtered out, but both compilations still end up in the final output.
+ Atlantic Quest + Galactic Quest (Europe) (En,Fr,De,Nl)
  - Atlantic Quest (Europe) (Fr,De)
  - Jewel Link - Atlantic Quest (Europe)
  - Jewel Link - Atlantic Quest (Europe) (Fr,Nl)
  - Jewel Link - Galactic Quest (Europe)

+ Jewel Link Double Pack (Europe)     *no clones*

Tried adding a new entry in the clone lists to group the two compilations together, but no luck. Does it need a more complicated definition, or is it a logic issue?

Compilations automatically get associated with each other by being defined as compilations for different individual titles.
In this case, the issue is there's a tie between the compilations — Retool can't decide which is better. If you set a priority of 2 for one of them, the lower priority title gets dismissed during the compilation comparison phase. Retool then can't decide if the remaining compilation is better than the individual titles, and so falls back on said individual titles.
{
  "group": "Jewel Link - Atlantic Quest",
  "titles": [
    {"searchTerm": "Jewel Link - Atlantic Quest"},
    {"searchTerm": "Atlantic Quest", "priority": 2}
  ],
  "compilations": [
    {"searchTerm": "Atlantic Quest + Galactic Quest"},
    {"searchTerm": "Jewel Link Double Pack", "priority": 2}
  ]
},
{
  "group": "Jewel Link - Galactic Quest",
  "titles": [
    {"searchTerm": "Jewel Link - Galactic Quest"}
  ],
  "compilations": [
    {"searchTerm": "Atlantic Quest + Galactic Quest"},
    {"searchTerm": "Jewel Link Double Pack", "priority": 2}
  ]
},

Given languages have been specified on one title, I'm leaning toward making that the higher priority. And perhaps I should cycle through all languages as a tie-breaker later on...


Add: SBS

Channel Name
SBS
Alternative Names (optional)
No response
Network (optional)
No response
Owners (optional)
Seoul Broadcasting System
Country
KR
Subdivision (optional)
No response
City (optional)
No response
Broadcast Area
c/KR
Languages
kor
Categories (optional)
No response
NSFW
FALSE
Launched (optional)
No response
Closed (optional)
No response
Replaced By (optional)
No response
Website (optional)
https://www.sbs.co.kr/
Logo
https://blog.naver.com/sunny0382/222705048367?photoView=0
Notes
No response

Will add in next update and thank you for the compliments.

Well, it appears to be there already so colour me confused.

Oh, I checked that there is Korean. It's my mistake that I didn't see. I will do my best to contribute to this project. Thank you.

Already in the database: https://iptv-org.github.io/channels/kr/SBSTV


updating Composites and Components sections in Storybook Overview page to be more visual

What
added visual explanations to Composites and Components sections in Storybook Overview page
Why
Too much text there
task https://skype.visualstudio.com/SPOOL/_workitems/edit/2641270
How Tested
ran Storybook locally

Composites

Components

Process & policy checklist

[x] I have updated the project documentation to reflect my changes if necessary.
[ ] I have read the CONTRIBUTING documentation.

Is this a breaking change?

[ ] This change causes current functionality to break.

nit: for this I think a person's name would be better to make it clear that the text is the person's name:

Can we remove Overview from the headings?

And just have "Composites"
"UI Components"
In a seperate PR I think we should also remove this big chunk of text at the start so these new composite screenshots can be seen as soon as you land on the page:

(can leave one or two lines as an intro)

Any work to add these to the Get Started page of the Composites?

It feels really lacking now

nit: for this I think a person's name would be better to make it clear that the text is the person's name:
(and then remove "with name "I'm joing from ACS" from the text above)

done :)

ork to add these/similar to the Get Started page of the Composites?

Not that I know but we always can create a task for it ;)


feat: update notify error logging and remove sendMagicLinkToIP function

Describe your changes

Make error logging from notify clearer and more consistent
Remove unused Notify 'magic link' functionality

https://pins-ds.atlassian.net.mcas.ms/jira/software/c/projects/APPLICS/boards/242?selectedIssue=APPLICS-295
Notify common package will also be updated to surface more errors in the API.

Useful information to review or test

Type of change 🧩

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[ ] Other (please explain in the description section above)

Checklist before requesting a review

[x] I have performed a self-review of my own code
[x] I have double checked this work does not include any hardcoded secrets or passwords
[ ] I have made corresponding changes to the documentation
[ ] I have provided details on how I have tested my code
[x] I have referenced the ticket number above
[x] I have provided a description of the ticket
[x] I have included unit tests to cover any testable code changes

:tada: This PR is included in version 2.30.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.36.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.15.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Detach LocatedSource from CommandSource heirarchy

API | Common
Pretty self-explanatory. This opens up the opportunity for a variety of use cases. For instance, say I want to track a player's eye location over time.
Locatable locatable = () -> new Location(player.getWorld(), player.getProperty(EyeLocationProperty.class).get().getValue())

+1 to what @Zidane said, was about to say something similar

@kashike Well then it is impossible to generify this without breaking commands completely. Can't have it both ways ;)

Updates, thoughts on this?


Repeating action improvements

This works best along #2950

Repeating entity targeting actions don't become deselected once they enter a cooldown now.
You can now toggle repeating actions while they're on cooldown.
Not clicking on an entity while using a repeating entity-targeting action no longer deselects it.

(CC @chairbender)

fixes #2960

fixes #2960

Honestly, this PR was a bit of a quick and dirty fix to this issue so feel free to do something better! @chairbender

Honestly, this PR was a bit of a quick and dirty fix to this issue so feel free to do something better! @chairbender


everything seems to work except for cgiNodeInfo();

hello -   (using CentOS-7)
so far so good, except i cannot seem to get <? cgiNodeInfo(); ?> working.  i see this error:
EXCEPTION: cgiNodeInfo is not defined
i am not sure if this is the problem or not, but i already had node installed.  so i did
which node;
and that gave me:
/usr/local/bin/node
so i used this in the first line of /cgi-bin/cgi-node.js and changed the SessionPath:
#!/usr/local/bin/node
SessionPath: '/tmp/'
however, this little script seems to work fine:
<?  write('test test');  ?>
<?  var xx = 123; write( xx + 45 );  ?>

any suggestions on getting cgiNodeInfo() working?  i fear i did something horribly wrong in my setup.

It is a typo in the instructions.   The correct function name is:  CgiNodeInfo
Notice the Capitol C in Cgi

THANK YOU !   i was questioning my own sanity at the time.    the sanity is still in question, but now for other reasons.

Additional note: the name has been changed in the repository to a lower case c, and the current version is 2.1 ... but the download link has not been updated nor has a new release been made...  Also, there is a bug fix that is in the repository ( 2.1 ) that is not in 2.0...

Where can you test the cginodeinfo() ?


npm Authenticate task failing TypeError: Cannot read property 'retrieveSecret' of undefined

Troubleshooting
Done
Environment

Server - VSTS or TFS on-premises?

N/A

Agent - Hosted or Private:

N/A
Issue Description
Running npm authenticate finds the npmrc file but fails to run saying TypeError: Cannot read property 'retrieveSecret' of undefined
As a note, this worked without any changes on Friday.
Error logs

2018-04-02T14:00:59.7935943Z ##[debug]Evaluating condition for step: 'npm Authenticate'
2018-04-02T14:00:59.7935943Z ##[debug]Evaluating: succeeded()
2018-04-02T14:00:59.7935943Z ##[debug]Evaluating succeeded:
2018-04-02T14:00:59.7935943Z ##[debug]=> (Boolean) True
2018-04-02T14:00:59.7935943Z ##[debug]Expanded: True
2018-04-02T14:00:59.7935943Z ##[debug]Result: True
2018-04-02T14:00:59.7935943Z ##[section]Starting: npm Authenticate
2018-04-02T14:00:59.7935943Z ==============================================================================
2018-04-02T14:00:59.7935943Z Task         : npm Authenticate (for task runners)
2018-04-02T14:00:59.7935943Z Description  : Don't use this task if you're also using the npm task. Provides npm credentials to an .npmrc file in your repository for the scope of the build. This enables npm task runners like Gulp and Grunt to authenticate with private registries.
2018-04-02T14:00:59.7935943Z Version      : 0.0.1
2018-04-02T14:00:59.7935943Z Author       : Microsoft Corporation
2018-04-02T14:00:59.7935943Z Help         :
2018-04-02T14:00:59.7935943Z ==============================================================================
2018-04-02T14:01:00.0436262Z ##[debug]agent.workFolder=F:\agent_work
2018-04-02T14:01:00.0436262Z ##[debug]loading inputs and endpoints
2018-04-02T14:01:00.0436262Z ##[debug]loading ENDPOINT_AUTH_PARAMETER_SYSTEMVSSCONNECTION_ACCESSTOKEN
2018-04-02T14:01:00.0436262Z ##[debug]loading ENDPOINT_AUTH_SCHEME_SYSTEMVSSCONNECTION
2018-04-02T14:01:00.0436262Z ##[debug]loading ENDPOINT_AUTH_SYSTEMVSSCONNECTION
2018-04-02T14:01:00.0436262Z ##[debug]loading INPUT_WORKINGFILE
2018-04-02T14:01:00.0436262Z ##[debug]loading SECRET_TSBLOBKEY
2018-04-02T14:01:00.0436262Z ##[debug]loaded 5
2018-04-02T14:01:00.2623836Z ##[debug]check path : F:\agent_work_tasks\npmAuthenticate_ad884ca2-732e-4b85-b2d3-ed71bcbd2788\0.0.1\task.json
2018-04-02T14:01:00.2623836Z ##[debug]set resource file to: F:\agent_work_tasks\npmAuthenticate_ad884ca2-732e-4b85-b2d3-ed71bcbd2788\0.0.1\task.json
2018-04-02T14:01:00.2623836Z ##[debug]system.culture=en-US
2018-04-02T14:01:00.2623836Z ##[debug]workingFile=<FILE_PATH>.npmrc
2018-04-02T14:01:00.2623836Z Adding authentication to the .npmrc file at F:\agent_work\40\s<FILE_PATH>.npmrc
2018-04-02T14:01:00.2623836Z ##[debug]SAVE_NPMRC_PATH=undefined
2018-04-02T14:01:00.2623836Z ##[debug]Agent.BuildDirectory=F:\agent_work\40
2018-04-02T14:01:00.2623836Z ##[debug]testing directory 'F:\agent_work\40\npmAuthenticate'
2018-04-02T14:01:00.2623836Z ##[debug]set SAVE_NPMRC_PATH=F:\agent_work\40\npmAuthenticate\zI982M
2018-04-02T14:01:00.2623836Z ##[debug]Processed: ##vso[task.setvariable variable=SAVE_NPMRC_PATH;issecret=false;]F:\agent_work\40\npmAuthenticate\zI982M
2018-04-02T14:01:00.2623836Z ##[debug]set NPM_AUTHENTICATE_TEMP_DIRECTORY=F:\agent_work\40\npmAuthenticate
2018-04-02T14:01:00.2623836Z ##[debug]Processed: ##vso[task.setvariable variable=NPM_AUTHENTICATE_TEMP_DIRECTORY;issecret=false;]F:\agent_work\40\npmAuthenticate
2018-04-02T14:01:00.2779842Z ##[warning]Resource file haven't set, can't find loc string for key: SavingFile
2018-04-02T14:01:00.2779842Z ##[debug]Processed: ##vso[task.issue type=warning;]Resource file haven't set, can't find loc string for key: SavingFile
2018-04-02T14:01:00.2779842Z ##[debug]SavingFile F:\agent_work\40\s<FILE_PATH>.npmrc
2018-04-02T14:01:00.2779842Z ##[debug]customEndpoint=null
2018-04-02T14:01:00.2779842Z ##[debug]Npm.PackagingCollectionUrl=undefined
2018-04-02T14:01:00.2779842Z ##[debug]System.TeamFoundationCollectionUri=https://<VSTS_URL>.visualstudio.com/
2018-04-02T14:01:00.2936119Z ##[warning]Resource file haven't set, can't find loc string for key: FoundLocalRegistries
2018-04-02T14:01:00.2936119Z ##[debug]Processed: ##vso[task.issue type=warning;]Resource file haven't set, can't find loc string for key: FoundLocalRegistries
2018-04-02T14:01:00.2936119Z ##[debug]FoundLocalRegistries 1
2018-04-02T14:01:00.2936119Z ##[debug]Agent.BuildDirectory=F:\agent_work\40
2018-04-02T14:01:00.2936119Z ##[debug]testing directory 'F:\agent_work\40\npm'
2018-04-02T14:01:00.2936119Z ##[debug]testing directory 'F:\agent_work\40'
2018-04-02T14:01:00.2936119Z ##[debug]mkdir 'F:\agent_work\40\npm'
2018-04-02T14:01:00.2936119Z ##[debug]rm -rf F:\agent_work\40\npm
2018-04-02T14:01:00.2936119Z ##[debug]removing directory
2018-04-02T14:01:00.2936119Z ##[debug]task result: Failed
2018-04-02T14:01:00.2936119Z ##[error]TypeError: Cannot read property 'retrieveSecret' of undefined
2018-04-02T14:01:00.2936119Z ##[debug]Processed: ##vso[task.issue type=error;]TypeError: Cannot read property 'retrieveSecret' of undefined
2018-04-02T14:01:00.2936119Z ##[debug]Processed: ##vso[task.complete result=Failed;]TypeError: Cannot read property 'retrieveSecret' of undefined
2018-04-02T14:01:00.2936119Z ##[section]Finishing: npm Authenticate

Just an update, this is no longer repro this morning.
Feel free to close and take any action if investigation is worthwhile.

I fought with this issue quite a bit today and i think i figured out what caused it @jmyersmsft and @justinmwarner
If you import the vsts-task-tool-lib/tool before vsts-task-lib/task then this error is reproduced. If i switch the order to load vsts-task-lib/task first then the error goes away.
I noticed that the vsts-task-tool-lib/tool module takes a dependency on vsts-task-lib. Since there is some global state being kept within the vsts-task-lib module (global['_vsts_task_lib_loaded']) then i suspected this may be causing the state data to not get loaded properly if another dependency invoked the module. To test this, i flipped the import order and it resolved the issue.

We have the same problem on all our repositories

Seems to be a regression, was working few days ago. Noticed it happening this morning.

Yep also happened to me. Build succeeded on 4/2 and then today it failed with no change to the repo.

Same here. It has been working for us, and started receiving this error this afternoon.

In my case I'm using Twine authentication for python but the issue is the same.
I tried to:

Clear and recreate Azure Agent
Recreate the task (thru the UI)
Manual authentication

As this issue is major, it would be appreciate a faster investigation or point-out the right place to raise that.
A workaround is required ASAP, because uploading artifact is broken!

Can one of you who started seeing this recently @steevegldev @jpenniman @grantal can you give a detailed log? We'll take a prompt look.

FYI to folks. We have a fix for the above task. Will be trying to hotfix that now. Also verifying which other tasks this might be affecting. Stay tuned.

The Azure Pipeline task "Package and deploy Helm charts" [1] is also affected. It fails in the pre-job phase with TypeError: Cannot read property 'retrieveSecret' of undefined.
[1] https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/helm-deploy?view=azure-devops

I'm seeing this with "Package and deploy Helm charts" as well.

fyi TwineAuthenticate task has been hotfixed and should be GTG. @AddonContributor @32technologies Artifacts folks don't own this the "Package and deploy Helm charts" task so the cause is likely different even though symptom might be the same. I also ran a query against that task and did not see it systemically failing across scale units. But I will still share this thread with some folks who own that task and ask them to take a look.

I confirm the issue has been fixed. Thanks @tkrick

I am also seeing the issue with Helm charts. It appears to be related to having TLS enabled for communication between Helm and Tiller. If this isn't the right place to post this, can someone please point me in the right direction? This is currently block deployments for us. Thanks!

Confirming, the problem with Twine Auth has been fixed.

Same as @michaelbpalmer , all our Helm based pipelines are not working, we have TLS enabled.
This is blocking our deployment.

Update on my previous comment: I guess it has been fixed? seems to be working now

Working for me now as well.

hi @rigerosa , @michaelbpalmer. i reached out to a contact internally that works on those helm tasks. He asked that you file a new issue and put the info there. it will be more easy to route if it says helm in the title/etc. so if one of you could do that that would be great. sorry for the delay.

thanks @tkrick but the problem seems to be solved now

Yes, fixed for me as well. Thanks!

Closing this as it looks resolved :)

The issue seems to be occurring again on the VSTS pipeline I am getting
##[error]TypeError: Cannot read properties of undefined (reading 'retrieveSecret')

Same here. Failing since this morning.

@shelmobd @SESA18621 I found another thread in the developer community, seems the issue is being investigated. https://developercommunity.visualstudio.com/t/npmAuthenticate0-Failing-for-version--0/10249182?q=npmauthenticate

##[debug]TypeError: Cannot read properties of undefined (reading 'retrieveSecret')
at Object.getEndpointAuthorization (D:\a_tasks\npmAuthenticate_ad884ca2-732e-4b85-b2d3-ed71bcbd2788\0.214.2\node_modules\azure-pipelines-tasks-packaging-common\node_modules\azure-pipelines-task-lib\task.js:449:26)
at getSystemAccessToken (D:\a_tasks\npmAuthenticate_ad884ca2-732e-4b85-b2d3-ed71bcbd2788\0.214.2\node_modules\azure-pipelines-tasks-packaging-common\locationUtilities.js:111:21)
at Object. (D:\a_tasks\npmAuthenticate_ad884ca2-732e-4b85-b2d3-ed71bcbd2788\0.214.2\node_modules\azure-pipelines-tasks-packaging-common\locationUtilities.js:88:29)
at Generator.next ()
at D:\a_tasks\npmAuthenticate_ad884ca2-732e-4b85-b2d3-ed71bcbd2788\0.214.2\node_modules\azure-pipelines-tasks-packaging-common\locationUtilities.js:8:71
at new Promise ()
at __awaiter (D:\a_tasks\npmAuthenticate_ad884ca2-732e-4b85-b2d3-ed71bcbd2788\0.214.2\node_modules\azure-pipelines-tasks-packaging-common\locationUtilities.js:4:12)
at Object.getPackagingUris (D:\a_tasks\npmAuthenticate_ad884ca2-732e-4b85-b2d3-ed71bcbd2788\0.214.2\node_modules\azure-pipelines-tasks-packaging-common\locationUtilities.js:77:12)
at D:\a_tasks\npmAuthenticate_ad884ca2-732e-4b85-b2d3-ed71bcbd2788\0.214.2\npmauth.js:76:56
at Generator.next ()
##[debug]NPM_AUTHENTICATE_TEMP_DIRECTORY=D:\a\1\npmAuthenticate
##[debug]NPM_AUTHENTICATE_TEMP_DIRECTORY=D:\a\1\npmAuthenticate
##[debug]rm -rf D:\a\1\npmAuthenticate
##[debug]removing directory D:\a\1\npmAuthenticate
##[debug]set SAVE_NPMRC_PATH=
##[debug]Processed: ##vso[task.setvariable variable=SAVE_NPMRC_PATH;isOutput=false;issecret=false;]
##[debug]set NPM_AUTHENTICATE_TEMP_DIRECTORY=
##[debug]Processed: ##vso[task.setvariable variable=NPM_AUTHENTICATE_TEMP_DIRECTORY;isOutput=false;issecret=false;]
##[debug]task result: Failed
##[error]TypeError: Cannot read properties of undefined (reading 'retrieveSecret')
##[debug]Processed: ##vso[task.issue type=error;]TypeError: Cannot read properties of undefined (reading 'retrieveSecret')
##[debug]Processed: ##vso[task.complete result=Failed;]TypeError: Cannot read properties of undefined (reading 'retrieveSecret')
Finishing: npm Authenticate MULTIORG/FE/AGFE/.npmrc
I am getting above error in my pipeline .please help me to resolve

I've fixed my build pipeline's task to<EMAIL_ADDRESS>until this is fixed

i am using MS hosted agent with task version  with classic  pipeline .now my pipeline is working now with authenticator version of 0.2081 in earlier it was used "0.214.2"


Typo

Double "we"
https://github.com/flutter/flutter/blob/ff2dde2c7fc9a72b221250d1dad7cedb044e43a9/packages/flutter_tools/lib/src/asset.dart#L406
cc @jonahwilliams

👍

we we accept PRs :)

I'd fix it in https://github.com/flutter/flutter/pull/82589, though I don't completely understand the meaning of this sentence


Self-service portal for being onboarded to the cluster

In a couple places you link to a Google form (which I presume sends email to scicomp?) requesting a new cluster account.
We actually have a new tool which users can use to onboard themselves. I am not sure if we are ready to announce it to the world - @chrisequalsdev can you speak to that?
I am also concerned that a google form on the public internet could be a portal for spam.

I was originally thinking that I would wait and and automate this later, however i'm now envisioning lots of requests coming in and wishing I did this first.  I started working on a new landing page for the self service portal earlier.  Current thinking is that the landing page will serve to check if a user has all the access needed to complete the Cluster 101 course and if the check fails then they can reach out to scicomp in some fashion. I should have a demo available in the next few days.

I think the self service will be great to add and replace this form, but in the meantime, I could incorporate a captcha (or similar) to prevent spam. Does that sound okay?

That would be great!


Enablement of certificate_authorities TLS extension via openssl.cnf not working

Intro
OpenSSL has support to add certificate_authorities as TLS extension in TLS ClientHello. See here (and here). This is relevant for a client to have a means to indicate to the server which CAs it would support.
Issue
However, when adding requestCAFile = <path/to/ca-cert-file-selection/pem-format> to openssl.cnf in the relevant ssl_conf sesction (see below), no such extension is sent in the ClientHello. This can easily be verified by monitoring a the content of the ClientHello with e.g. WireShark.
The reason is believed to be caused by this line which seemingly is not parsed as intended during an OpenSSL context configuration.
Remediation
When inserting a single line with SSL_CONF_CMD_STRING(RequestCAFile, "requestcafile", 0), right below this line, the certificate_authorities extension is created in the ClientHello as expected, obviously only when also adding a requestCAFile = <path/to/ca-cert-file> line to openssl.cnf (IOW, it is not created when no such line is in openssl.cnf).
It is further suggested to check for client or server mode flags here. Not 100% sure whether this is required or has a benefit.
Additional info
Remediation checked with OpenSSL v3.3.0 (commit 4cb31128b5790819dfeea2739fbde265f71a10a2), via s_client and cURL as client applications.
For completeness, example excerpt of `openssl.cnf':
ssl_conf = ssl_module

[ ssl_module ]
system_default = tls_system_default

[ tls_system_default ]
TLS.MinProtocol = TLSv1.2
TLS.MaxProtocol = TLSv1.3
DTLS.MinProtocol = DTLSv1.2
DTLS.MaxProtocol = DTLSv1.2
Groups = secp521r1:secp384r1:X25519:prime256v1:X448
Ciphersuites = TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256:TLS_AES_128_CCM_SHA256
CipherString = ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384
requestCAFile = /etc/pki/tls/certs/ca-bundle.crt

I would argue that adding certificate_authorities to a ClientHello has nothing to do with certificate configuration options. From my perspective, it's in the same class as specifying Sigalgs, Groups, or Ciphers via the `openssl.cnf' file.

No, IMO it is something that is closely related to individual application settings. There could be different acceptable CAs for an application connecting to some private internal server and different for public internet web access.
The intent for the system_default configuration is for system-wide policy settings such as minimal protocol versions, minimal security level, etc.

I understand your point.
My motivation was two-fold (sequence is [strong] priority):

Enable the likes of cURL without the need to change application code, where per request control can readily be achieved by using $ENV::currentValue in openssl.cnf. Absence of the ENV variable automatically results in not generating/sending the extension, at which point it "hurts" nobody else.
Have a means to simplify experiments with "fake" root certs added to the certificate_authorities extension. The term "fake" in this context means "pack information about trust stores" in the certificate_authorities extension by using carefully tailor made values for CN etc. This to find out whether a new extension trust_expressions is really required in the context of this discussion.

Given the former, I still think enabling control over the certificate_authorities extension via openssl.cnf makes sense.
For the latter, I have my own build which I can use. And others can see above how to enable the feature.
Somewhat related to this (don't know whether I should start a fresh issue): The client can at least indicate to the server which root cert type it would support via the signature_algorithms and signature_algorithms_cert extensions.
The TLSv1.3 standard (RFC8446 in section 4.2.3) states that
If no "signature_algorithms_cert" extension is present,
then the "signature_algorithms" extension also applies
to signatures appearing in certificates.

Given that generating signature_algorithms_cert extension is not supported, I made an experiment specifying exactly one entry in the signature_algorithms extension, but had to notice that the cert-chain - which had certs with different algs - was successfully verified. This seems to indicate deviation from the standard ?!?
Specifically, I used the OQS provider, specified dilithium5 as the one-and-only signature algorithm, and issued a cURL request against https://test.openquantumsafe.org:6156/. Result: Verification succeeded against the OQS interop server root cert (RSA4k).
Same successful verification when limiting to ECDSA sigalgs against an RSA root cert.

OK, understood. As I have what I need, I'm closing this issue for good house-keeping.
While I perfectly understand that specifying the expected sigalgs for cert-chains in the ClientHello is not necessarily sufficient to make the best choice for a purely Q-safe cert chain, it nevertheless would be a easy first step in that direction. It would therefore have been appreciated if OpenSSL would adhere to this aspect of the standard.

Given that generating signature_algorithms_cert extension is not supported, I made an experiment specifying exactly one entry in the signature_algorithms extension, but had to notice that the cert-chain - which had certs with different algs - was successfully verified. This seems to indicate deviation from the standard ?!?

This is a separate issue - AFAIK we currently do not validate the signature algorithm in certs against the sigalgs. @mattcaswell might want to confirm this. It would be a valid feature request.

It is already filled as https://github.com/openssl/openssl/issues/11438


Uncaught Exception: Cannot read property '1' of null

An uncaught exception was reported.
Info:
OS: darwin
Arch: x64
GPMDP Version: 3.3.0
Time: Fri Jul 29 2016 11:23:05 GMT 0100 (BST)
Error:
Cannot read property '1' of null
TypeError: Cannot read property '1' of null
    at Request._callback (/Applications/Google Play Music Desktop Player.app/Contents/Resources/app/build/main/features/core/lyrics/source_lyricsFreak.js:9:1201)
    at Request.self.callback (/Applications/Google Play Music Desktop Player.app/Contents/Resources/app/node_modules/request/request.js:200:22)
    at emitTwo (events.js:106:13)
    at Request.emit (events.js:191:7)
    at Request.<anonymous> (/Applications/Google Play Music Desktop Player.app/Contents/Resources/app/node_modules/request/request.js:1067:10)
    at emitOne (events.js:101:20)
    at Request.emit (events.js:188:7)
    at IncomingMessage.<anonymous> (/Applications/Google Play Music Desktop Player.app/Contents/Resources/app/node_modules/request/request.js:988:12)
    at emitNone (events.js:91:20)
    at IncomingMessage.emit (events.js:185:7)

This issue was created automatically inside the uncaughtException handler

Closing this automatically reported issue as a duplicate of #1281


README "Database Steps" and steps.json do not match when created via prisma2 dev

Create a project
Run prisma2 dev
Change something in the schema.prisma to test out Dev Mode
Exit Dev Mode and run prisma2 lift save
Apply the migration to the DB with prisma2 lift up
Observe that the "Database Steps" are empty and steps.json has content:

As the database was created and filled via the dev/watch migrations during prisma2 dev this is of course correct, but super confusing and makes the README.md very environment dependent. The content created on the dev or staging system can be very different than what is actually executed in prod.

The fix PR (https://github.com/prisma/prisma-engine/pull/106) was just merged. It will be in the next preview (15).


Question about decoder models

Great work, i just took a look to the code and found parts where you declare mappings containing gpt2
Models like opt should be adaptable too i think, but what about gpt neox, which only has query_key_value instead of query, key, value seperated layers ?
It would be interesting for open-assistant project and if it works it would have huge potential

Hi @flozi00 ,
Thank you for your interest in our work and for your kind words!
Initially, we experimented with Unlimiformer-GPT2, but after some time we decided to focus on encoder-decoder models, so the code no longer supports GPT2, and we will clean the GPT2 remainings.
Best,
Uri

Then Flan-t5 could be still interesting and as far as i see it is supported
Do you think about converting the repo to an installable package ?
So its possible to install from github source or pypi instead of copy paste the files ?

Yes, definitely, once we converge to a stable version.

So is there anything practically preventing this work from being applied to decoder-only models?
This work is great for encoder-decoder models, but if it'd also be applicable to current decoder-only models, I feel the whole LLM playing field would suddenly change.
Pair this work with a (decoder-only) model like LLAMA (or open source alternatives), and you'd be able to feed entire codebases into it and do codebase-wide analysis/code gen.
Add an agent framework around it and it would run circles around any current agent design.
If this work could be applied/adapted to current decoder-only models I think that'd be huge, as that's where most of the current hype is.

There's nothing that practically prevents this from being applied to decoder-only models.
Just implementation and making sure that the right tensors fall into the right locations.

Hey @flozi00 ,
Unlimiformer now supports Flan-T5, Llama and Llama-2 (and all their derivatives)!
Check it out, and let us know if you have any questions!
https://github.com/abertsch72/unlimiformer#august-2023---unlimiformer-now-supports-llama-2-and-all-its-derivatives
Best,
Uri


About Swin-T

Hi, in the backbone folder, I did not see the code for swin-t. How did you use swin-t as the backbone to extract features

mmdet has swin-t, we can quickly init swin-t by define type = 'mmdet.SwinTransformer' in the config.
For the code of swin-t, look at https://github.com/open-mmlab/mmdetection/blob/main/mmdet/models/backbones/swin.py.


[BUG] Can not access Wallet

Describe the bug
see: https://x.com/T3kNoLogic/status/1854377924939710799?t=RlyGiq2U7e1Arl0HWVgQDw
I'm experiencing a BUG that is not allowing me to access my wallet.
To Reproduce
unknown
Expected behavior
Login should work
Screenshots

Desktop (please complete the following information):
unknown
Smartphone (please complete the following information):
unknown
Additional context
unknown

Duplicate https://github.com/dfinity/oisy-wallet/issues/3390


[WIP] Easier api - reorder parameters

Current coverage is 74.76%

Merging #1266 into master will increase coverage by +0.16% as of 579e3ae

@@            master   #1266   diff @@
======================================
  Files          267     267
  Stmts        15407   15468    +61
  Branches      1615    1621     +6
  Methods          0       0
======================================
+ Hit          11494   11565    +71
- Partial        378     383     +5
+ Missed        3535    3520    -15

Review entire Coverage Diff as of 579e3ae

Uncovered Suggestions

+0.09% via ...gingConfiguration.cs#375...388
+0.09% via ...gingConfiguration.cs#341...354
+0.09% via ...argets/FileTarget.cs#1704...1716
See 7 more...

Powered by Codecov. Updated on successful CI builds.

Superseded by https://github.com/NLog/NLog/pull/1286


fix #6168

I've just put the 2 example snippets from the site in one, so they render in one single <pre> tag to align to the right. It's just a trivial change, let me know if you find any issues. All tests passed.

Thanks!


[SPARK-29392][CORE][SQL][FOLLOWUP] Avoid deprecated (in 2.13) Symbol syntax 'foo in favor of simpler expression, where it generated deprecation warnings

What changes were proposed in this pull request?
Where it generates a deprecation warning in Scala 2.13, replace Symbol shorthand syntax 'foo with an equivalent.
Why are the changes needed?
Symbol syntax 'foo is deprecated in Scala 2.13. The lines changed below otherwise generate about 440 warnings when building for 2.13.
The previous PR directly replaced many usages with Symbol("foo"). But it's also used to specify Columns via implicit conversion (.select('foo)) or even where simple Strings are used (.as('foo)), as it's kind of an abstraction for interned Strings.
While I find this syntax confusing and would like to deprecate it, here I just replaced it where it generates a build warning (not sure why all occurrences don't): $"foo" or just "foo".
Does this PR introduce any user-facing change?
Should not change behavior.
How was this patch tested?
Existing tests.

Test build #114779 has started for PR 26748 at commit e1fb2d5.

Test build #114779 has finished for PR 26748 at commit e1fb2d5.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Merged build finished. Test PASSed.

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

Test build #114783 has started for PR 26748 at commit 1c0818a.

Merged build finished. Test PASSed.

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

@srowen this means the 'foo sintax will be not longer available?

Test build #114783 has finished for PR 26748 at commit 1c0818a.

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

Merged build finished. Test PASSed.

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

Oh no, that syntax is still present in 2.13, it's just deprecated. The implicit conversions in Spark, to things like Column, are still there too. I just changed the instances that generate a warning in 2.13 (and I don't know why many do not?) to explicitly use a Column or String.

Also, please fix the following file together for Hive-2.3 (default) profile.

sql/core/v2.3/src/test/scala/org/apache/spark/sql/execution/datasources/orc/OrcFilterSuite.scala

Test build #114876 has started for PR 26748 at commit 37748f0.

Merged build finished. Test PASSed.

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

Test build #114876 has finished for PR 26748 at commit 37748f0.

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

Merged build finished. Test PASSed.

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

Merged to master.


Add typing_extensions as a dependency

The typing_extensions module contains backports of new typing features for earlier versions of Python. It is understood by type checkers like Mypy and Pyre. In https://github.com/numpy/numpy-stubs/pull/59 it is proposed that we add it as a dependency, which I think is a good idea. Beyond just that PR, some potential benefits are:

Using Literal to better type specific (but fairly common) overloads, e.g.np.array(..., dtype="float")

Protocol might be a good way to approach typing ArrayLike
Using TypedDict to better describe complex dtypes.

I imagine that the biggest concern would be forcing it to be a hard dependency of NumPy should the stubs be moved there, but I believe we can avoid that.

If everything stays stubs only, then it's not a problem

If we do add annotations to source files, we can still work around it with constructs like
from typing import TYPE_CHECKING

if TYPE_CHECKING:
    from typing_extensions import Literal

x: 'Literal[1]' = 1  # Or use `from __future__ import annotations` post 3.8
...

Objections? In the absence of them we'll move forward with including it.

Sounds like a good idea to me

A separate pull request has just been created for the addition of typing_extensions (https://github.com/numpy/numpy-stubs/pull/63).

Thanks. I’ll give people a little bit longer to raise any objections here, and then we’ll move forward.

Closed by https://github.com/numpy/numpy-stubs/pull/63.


Add is_a link between mitochondrial tRNA modification and mitochondrial tRNA processing

GO:0070900: mitochondrial tRNA modification should be a is_a child of GO:0090646: mitochondrial tRNA processing.
. . <-  GO:0090646: mitochondrial tRNA processing
. . . <- is_a GO:0070900: mitochondrial tRNA modification
I find the separation between 'mitochondrial tRNA modification' and 'mitochondrial tRNA processing' very small to begin with. But it's strange that these two terms are not even related, because further up 'tRNA modification' is a child of 'tRNA processing'.
Thanks,
petra

Hi @pfey03 ,
FYI, I haven’t had a chance to work on this ticket until now, and I’ll be on leave next week. Thanks for your patience.

Thanks Paola, have a great week end and next week!

Isn't the problem here the fact that tRNA modification is a child of tRNA processing?
Processing refers to alterations to the primary transcript doesn't it (nucleotide cleavage or addition), but excludes modifications? Is that correct?

@pfey03 , @ValWood , @hdrabkin
Welcome to the daily can of worms.
Looks like there’s a wider problem with consistency in the use of ‘modification’ and ‘processing’ in GO. Probably because the usage in the literature isn’t. Looking at different macromolecule branches:
protein metabolic process

(is_a) protein maturation

(is_a) protein processing

(is_a) protein modification process
=> ‘modification’ and ‘processing’ are distinct; there is the presence of an intermediate parent (’maturation’) above ‘processing’

DNA metabolic process

(is_a) DNA modification

RNA metabolic process

(is_a) RNA modification
(is_a) RNA processing

ncRNA metabolic process

(is_a) ncRNA processing

(is_a) tRNA processing

(is_a) tRNA modification
(same for rRNA processing and others)

macromolecule modification = The covalent alteration of one or more monomeric units in a polypeptide, polynucleotide, polysaccharide, or other biological macromolecule, resulting in a change in its properties.
I’ll ask @hdrabkin for help here. The situation may be different for different types of macromolecules, but we need to be consistent. What would be the correct way to go? Thanks.

A long time ago, when @hdrabkin, Ceri van Slyke and I worked on some rRNA processing and ribosome biogenesis stuff, we felt that "modification" was included in "processing" for rRNA, as one of the many types of processing that can occur.
Harold may be more up-to-date on this. He's on vacation this week and then will go to a PRO meeting next week, so he probably won't respond till after that.

Thanks @krchristie .
@pfey03 and @ValWood , I'll set this to pending then, waiting for @hdrabkin to take a look.
Feel free to 'ping' him or me by commenting here if too long goes by without an update. Thanks.

Welcome to the daily can of worms.

This is a great phrase

Hi @hdrabkin ,
When you have a chance, could you please take a look at this ticket, and summarise what the best action plan would be. Many thanks.

Hi @pfey03,
Going back to your initial request in this ticket:
“GO:0070900: mitochondrial tRNA modification should be a is_a child of GO:0090646: mitochondrial tRNA processing.
. . <- GO:0090646: mitochondrial tRNA processing
. . . <- is_a GO:0070900: mitochondrial tRNA modification
I find the separation between 'mitochondrial tRNA modification' and 'mitochondrial tRNA processing' very small to begin with. But it's strange that these two terms are not even related, because further up 'tRNA modification' is a child of 'tRNA processing’.”
My understanding is that you came across this while you were annotating to (or looking for) related terms, but that you do not strictly need this to be resolved in order to be able to annotate papers you’re working on. Could you please confirm if this is correct?
Many thanks.

Looking at this ticket again. In summary:
The use of ‘modification’ and ‘processing’ in class labels in GO doesn’t seem to be consistent (see https://github.com/geneontology/go-ontology/issues/12757#issuecomment-259110495). Is this because the usage in the literature is indeed different depending on the type of macromolecule, and if so, do we need to add definition comments to explain any discrepancy? Or is the inconsistency a problem we need to fix more radically, and if so what branch(es) should we rename/restructure, and how?
The impression was that @hdrabkin may be the best person to lead on this. I’ll assign to him. (My understanding is that this issue is not preventing any specific annotation, if that helps prioritising.) Thanks.

@paolaroncaglia to answer your question from December (sorry went on break mid December and then fell through cracks).
I saw this because I annotated a paper/gene, but found GO:0070900: mitochondrial tRNA modification a good term as reflected in the definition, for what I needed (PMID:21307182, TLP4 / tip4).
Since the same paper had functional data for a non mitochondrial protein, I saw the discrepancy between the 'tRNA modification/processing' relationship versus the 'mitochondrial tRNA modification /processing' NON relationship.
In sum, I could use the term I needed to annotate and just thought the structural inconsistency has to be addressed. That it's such a huge can of worms, really sorry for opening!!

Thanks @pfey03 for clarifying!

Logical Def was added; relationship is already there.


Ability to combine visibilities

We should provide functions to combine measurements from multiple simulations.

This is addressed in #185 & #195.


Create Countdown.py

Thanks for your Contribution!
Keep Contributing!
Give a Star to this project if you like this!
Happy Hacktober!


New package: aoguai.QQtoExcel version 1.0

拉取请求使用此工具创建： komac v2.9.0 :rocket:

https://github.com/microsoft/winget-pkgs/pull/201276#issuecomment-2558327640

Microsoft Reviewers: Open in CodeFlow

Retry-1

Manual Validation ended with:

2024-12-24 17:55:43.965 [FAIL] Installer failed security check. Url: https://github.com/aoguai/QQtoExcel/releases/download/V1.0.0-20220719/QQtoExcelV1.0_windows.zip Result: 0x80004005

(Automated response - build 931.)

Manual Validation ended with:

2024-12-24 17:55:43.965 [FAIL] Installer failed security check. Url: https://github.com/aoguai/QQtoExcel/releases/download/V1.0.0-20220719/QQtoExcelV1.0_windows.zip Result: 0x80004005

(Automated response - build 931.)

https://www.virustotal.com/gui/file/57d9278804693de3205a0549a45dba64c5e682d1134da86839736b274885648e/detection

Sorry, the virus signature must have been old.
Verify:

The VM isn't prepared to display the characters.


set dependabot to PR to develop

update .github/dependabot.yml so dependabot PRs to develop instead of main

Merge this to main since the original PR went to develop, and recent dependabot PRs are still going to main instead of develop


Fix tests with pytest 6.2

Summary of changes
The latest pytest deprecates pytest.yield_fixture in favor of
pytest.fixture [1]. The changelog [2] says that both are the same.
[1] https://github.com/pytest-dev/pytest/pull/7988
[2] https://docs.pytest.org/en/stable/changelog.html#pytest-6-2-0-2020-12-12
Pull Request Checklist

[ ] Changes have tests
[x] News fragment added in changelog.d/.
(See documentation for details)

@jaraco Is there anything I can do to help either get this in, or restrict to pytest 5.x?  I have a PR that's dependent on this one...

Beautiful. Thank you!


Weaviate Metadata

When storing embeddings into Weaviate we are loosing the content metadata. The goal of this PR is to store those metadata as fields in weaviate so that we can get them back when we are finding the content.
Context
When doing RAG with weaviate as vector database for embeddings we are loosing the metadata associated with the textSegment
Change
I now store and get back the metadata in Weaviate
Checklist
Before submitting this PR, please check the following points:

[X] I have added unit and integration tests for my change
[X] All unit and integration tests in the module I have added/changed are green
[X] All unit and integration tests in the core and main modules are green
[x] I have added/updated the documentation
[ ] I have added an example in the examples repo (only for "big" features)
[ ] I have added my new module in the BOM (only when a new module is added)

I moved from batch to data to create the objects. i don't understand why but the batch operation didn't create them while using the data API worked. I don't really understand why, all the more so as batch seemed to be the correct way to do it.

@dliubars I think I fixed all your comments.

@dliubars can you have a look, please?


where is documentation for writing memcached client

I am dissatisfied with the performance of the nio-based java memcached client that seems most used (spymemcached).  nio sockets are based on polling, as in there is no callback when the data is received for the socket response as in nodejs.  My java server application is 95% cpu utilized, so apparently the spymemcached library does not poll for the socket response well enough.  measurements with this java library give 1 millisecond on my development machine, but 25 or even much more millis on the cpu-utillized server for a GET.
It seems like java nio is appropriate only for dedicated servers like tomcat, and not for libraries that are clients of a server like memcached, especially my client that is close to 100% cpu utilized.
Therefore I want to write my own blocking java.net.Socket java library to make GET, and CAS calls etc.  However, I need to know what the format of the send packets is, and the response packets for the various memcached entry points.  Also, how it is different for binary mode.

In the doc/ directory in the source tarball (or here on github). protocol.txt describes the ASCII protocol, and then protocol-binary.xml for binprot.
There're a few other java clients you could use for examples too (at least xmemcached comes to mind)

I think I only had a couple question about possible unsigned fields.  With the "flags" for get/set etc, if I choose to use 16 bit fields the decimal values will always be unsigned.  But if I choose to use 32-bit flags for the versions of memcached that I plan to use, should I send unsigned 32-bit decimal values?  I.e. if the high bit of the 32-bits is set, do I send an the decimal of that 32-bit value as unsigned?  And if so, do I receive it as unsigned?
Likewise, with the "cas value", for gets/cas, which is 64-bits, I am not in control of the values I receive, but if memcached wants to return a 64-bit cas-value with the high bit set, will it give me the unsigned decimal version of this number, or the signed version?  Likewise, if I send it back to memcached with "cas", I assume I send it back the same way.  Assuming signed since the docs did not say specifically!
Are there any other signed/unsigned decimal gotchas?

CAS should be unsigned. It's just a counter anyway; you send it back as-is if you want a GETS to match a CAS command. flags are unsigned for any version in the last few years. It was an error that it was ever signed for ASCII, and while I assumed some clients ended up treating that specially no one did, so we just fixed it in the server.

By the way, currently, unix secs fit in a signed 32 bit int.  But in 15 years I think, they won't.  Does memcached currently require the exptime to fit in an int32?

exptime is relative, but there's a mode (+ 30 days expiration) where it interprets it as a unix timestamp. 32bit will always be fine for the internal expiration time, but to fix y2038 some of the supporting code will have to change.


Change tagging to not include hash ? e.g. v0.0-3255-gfe86b47d -> v0.0.3255

Currently, the tags in the releases contain the full output of git describe.
While this is generating unique versions even across branches, that pin-pointing to a particular hash is not needed, but we have not very convenient tags that are hard to easily 'read' as a version number, and in particular impossible to guess to what a 'next' one would be.
So instead of v0.0-3255-gfe86b47d, I propose to have the tags numbered as v0.0.3255.
It would also be less confusing for packaging folks as they currently seem to come up with different ways to formulate a version number ( seen here: https://repology.org/project/verible/versions ). If we had a common three-dot format of the version number, it would be very unambiguous how to name a package version.
Change would be something like this:
--- a/.github/workflows/verible-ci.yml
+++ b/.github/workflows/verible-ci.yml
@@ -541,7 +541,7 @@ jobs:
         git config --local user.email "$BOT_EMAIL"

         # Create a tag of form v0.0-183-gdf2b162-20191112132344
-        TAG="${TAG:-$(git describe --match=v*)}"
+        TAG="${TAG:-$(git describe --match=v* | sed 's/\(v[0-9]\+\.[0-9]\+\)-\([0-9]\+\)-.*/\1.\2/')}"

         git tag "$TAG" || true
         echo "TAG=$TAG" >> $GITHUB_ENV

This will result in nice <major>.<minor>.<patchlevel> tags such as v0.0.3255
Opening this up for discussion, as there might be reasons to not do that, that I am missing ?
Adding @proppy  @mithro @umarcor as folks who have dealt with versioning and packaging before.

The patchlevel in the proposed format is the number of commits since the last tag. Therefore, it is ambiguous because multiple feature branches with the same number of diverging commits will produce the same version string. As a result, it can only be used if tags are only ever created from a linear main branch (or a linear segment of it) and it is never force-pushed.

Yes, but a linear main branch is the only thing we do and release.


Improve documentation

Scope
Refactor the documentation to be more user-friendly. The most important documentation How to configure and run a node will not be addressed on this PR since there are some blockers to getting the information required and some clean PRs going on at the same moment. This documentation will be addressed in a subsequent PR.
For better user experience reviewing this PR, I recommend taking a look at: https://github.com/vtleonardo/alicenet/tree/refactor-docs to see how the docs will appear after they are merged.

@vtleonardo I added build/test/running locally to https://github.com/alicenet/alicenet/wiki

Follow up with creating configuring node wiki page.


the download leaves my local document blank.

Expected Behavior
when I click on download, puchar-file the server and replace my file.
Actual Behavior
when I click download it leaves my local document blank.
Steps to Reproduce the Problem

open the document
2.click on the open document
3.click on sftp: download

Requisites (important to diagnose the problem!)
Extension Logs
[set option sftp.printDebugLog to true, then reload vscode, reproduce the problem, get the logs(view -> output-> sftp)]
Specifications

Version: 0.8.10
Platform: win10

Maybe the remote document is blank？So you just
download a blank file. And please provide extension logs.

No, my html file on the server is with content. my local file is also with content.
But when I ask to download only my local file goes blank.
the upload works very well, even by clicking or saving. The problem is only in the download
and how can I get the logs?

Preference -> setting -> sftp.printDebugLog to true, then reload vscode, reproduce the problem, get the logs(view -> output-> sftp)

[info]: config at c:/Users/Ross/Google Drive/7startups/Sites/urbi/siteUrbi/www {
"host": "",
"port": 21,
"username": "",
"password": "**********",
"protocol": "ftp",
"agent": null,
"privateKeyPath": null,
"passphrase": null,
"passive": false,
"interactiveAuth": false,
"remotePath": "/",
"uploadOnSave": true,
"syncMode": "update",
"watcher": {
"files": false,
"autoUpload": false,
"autoDelete": false
},
"ignore": [
"c:/Users/Ross/Google Drive/7startups/Sites/urbi/siteUrbi/www//.vscode/",
"c:/Users/Ross/Google Drive/7startups/Sites/urbi/siteUrbi/www//.git/",
"c:/Users/Ross/Google Drive/7startups/Sites/urbi/siteUrbi/www//.DS_Store",
"//.vscode/",
"//.git/",
"//.DS_Store"
],
"configRoot": "c:/Users/Ross/Google Drive/7startups/Sites/urbi/siteUrbi/www"
}
[debug]: task: download
[debug]: conncet to remote
[debug]: download /public/wp-content/themes/travel-time/footer.php at Sat Nov 25 2017 11:56:29 GMT-0200 (Horário brasileiro de verão)

Does it only happen with this file?

No, any file. if it is saved on the computer, and I do the download, the file will go blank.
I made other ftp accounts, and other domains. all the same.

I've made a fix. Try debug-pacakge and give me some feedbacks.

[debug]: task: download
[debug]: conncet to remote
[error]: context: undefined reason: TypeError: Cannot read property 'type' of undefined
at srcFs.lstat.then.stat (C:\Users\Ross.vscode\extensions\liximomo.sftp-0.8.11\out\src\modules\conveyer.js:387:17)
at
at process._tickCallback (internal/process/next_tick.js:109:7)

It's very close. Try debug-pacakge again.

[debug]: task: download
[debug]: conncet to remote
[error]: context: undefined reason: TypeError: Cannot read property 'type' of undefined
at srcFs.lstat.then.stat (C:\Users\Ross.vscode\extensions\liximomo.sftp-0.8.11\out\src\modules\conveyer.js:387:17)
at

I mean the new debug-pacakge again. I have made some change.

[debug]: task: download
[debug]: conncet to remote
[error]: context: undefined reason: TypeError: Cannot read property 'type' of undefined
at srcFs.lstat.then.stat (C:\Users\Ross.vscode\extensions\liximomo.sftp-0.8.11\out\src\modules\conveyer.js:387:17)
at
I had already downloaded your new debug yesterday. I downloaded it again, the same message, the file is not going blank, but it gives an error.

?

Do you use ftp? If so, It's weird about your debug logs. I've added more logs. Try debug-pacakge.

I sent it to your email because I have a lot of information.
Yes I use ftp normally, today I have to download the file over ftp, override my local file, then edit in vscode and upload by vscode-sftp.

The logs say that everything works well? Can you confirm this?


Add Algoua

Алгоритми | Algoua:
https://algoua.com
Contributor's Checklist:

[x] I have read and understood the contribution rules. My submission complies with these rules.
[x] My submission is grammatically correct.

By submitting this pull request I confirm I've read and complied with the below requirements

Пінг


removeListener() executes the listener

Quick test
> print(Emitter)
table: 008CB508
> e = Emitter()
> e:emit('test')
> function u() print('Hello') end
> e:on('test', u)
> e:emit('test')
Hello
> e:removeListener('test', u)
Hello

I looked into your code and in the function rmEntry() pred gets executed
local function rmEntry(tbl, pred)
    local x, len = 0, #tbl
    for i = 1, len do
        local trusy, idx = false, (i - x)
        if (type(pred) == 'function') then trusy = pred(tbl[idx]) -- this line
        else trusy = tbl[idx] == pred
        end

        if (tbl[idx] ~= nil and trusy) then
            tbl[idx] = nil
            table.remove(tbl, idx)
            x = x + 1
        end
    end
    return tbl
end

removeListener() calls rmEntry() like this: rmEntry(evtbl, listener), which causes the listener to get executed with parameters tbl[idx]. Is this behavior intended?

rmEntry(evtbl, function(v) return v == listener end) this would probably be the solution

Having changed that, I've started having another issue. I've been trying to debug my code for like 3 hours and it's probably related to this. One of my listeners would never get called, nor does it appear when I call emitter:listeners(ev). But, for some reason, after I bind another instance of that listener (not actually the same object, just the same local function redefined inside a scope) it shows back up. I'm going to trace this problem myself and report here on any updates.

I probably know what had happened! I was removing a listener off an event while inside such a listener (i.e. called by emitter:emit()). I got it only upon creating my own little emitter library, which I'm going to use from now on. Your code probably just loops from start to finish and lets removeListener() do its thing, effectively letting it potentially intervene with the normal execution procedure of events. Inspect my code if you'd like to know how I fixed this issue. So the initial issue posted above is not the root of this second one, this is another bug.

Duplicate of #
same bug
@AntonC9018 absolutely right
rmEntry should not call listener
looks like
rmEntry(evtbl, function(v) return v == listener end)
been writen that rmEntry(evtbl, listener )

Duplicate of #
same bug
@AntonC9018 absolutely right
rmEntry should not call listener
looks like
rmEntry(evtbl, function(v) return v == listener end)
been writen that rmEntry(evtbl, listener )

I met the same bug.
However, I think trusy = tbl[idx] == pred in rmEntry  should be called when callingremoveListener()


Add DdRum.addFeatureFlagEvaluation to jest mock

What does this PR do?
Fixes TypeError: _mobileReactNative.DdRum.addFeatureFlagEvaluation is not a function in jest unit tests
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)
[ ] If this PR is auto-generated, please make sure also to manually update the code related to the change

Hi @stevoland, thanks for catching this one!
I'll release it in a patch, and find a way to make sure we keep the mock updated in the future :)


Docs give wrong example for create-service-key

Please fill out the issue checklist below and provide ALL the requested information.

[x] I tried updating to the latest version of the CF CLI to see if it fixed my problem.
[x] I attempted to run the command with CF_TRACE=1 to help debug the issue.
[x] I am reporting a bug that others will be able to reproduce.

Describe the bug and the command you saw an issue with
This isn't a bug per se but a mismatch of information from what the docs say and what the cli does
What happened
Docs give the example of cf create-service-key mydb mykey -c '{"permissions":"read-only"}' for the create-service-key command but we get the following response.
Creating service key read-only-test-key for service instance mydb as uXXXXXX... Service broker error: Invalid arbitrary parameter syntax. Please check the documentation for supported arbitrary parameters. FAILED
Expected behavior
When we run the command like this cf create-service-key mydb mykey -c '{"read-only":true}' the key gets created as expected.
To Reproduce
Steps to reproduce the behavior; include the exact CLI commands and verbose output:

Run cf create-service-key mydb mykey -c '{"permissions":"read-only"}'
See the error message
Run cf create-service-key mydb mykey -c '{"read-only":true}'
See the key created successfully

Provide more context

macOD High Sierra 10.13.6 iTerm
cf version 6.43.0+815ea2f3d.2019-02-20

Hey @NickyBobby ,
Thanks for submitting this issue. Perhaps we can rope in @ljarzynski from the Docs team to see if he knows how we can handle this.
The doc mentioned

Thanks @NickyBobby for bringing this to our attention, and @bwasmith for contacting the docs team.
Looks like that page is outdated.
I'm going to go ahead and replace it with the correct parameters.
This change should be reflected on the site momentarily.

Thanks for the quick response and fix! My team and I had been struggling with this for a few days, so when we figured out that the params in the docs were bad, we thought it would be a good idea to let y'all know.
Thanks again!

Hi, I know this issue was close but I found the example mistake on another doc site. https://cli.cloudfoundry.org/en-US/cf/create-service-key.html . Can this example be updated as well?

Hi @NickyBobby
The JSON configuration parameters provided to the create-service-key command are broker dependant, i.e. one broker might accept permissions, another broker might accept read-only, and another might accept any arbitrary JSON.
Where did you get the broker from, that you are trying to run this command against ?
Was it mentioned at the docs ?
Otherwise I don't think it makes any sense to update the document, because whatever we do will only work for one particular broker.
Best,
@williammartin  and @nmaslarski

We going to close this issue because we don't think this is issue with the CLI. If you still think it's a issue or you have any more questions, please don't hesitate to ask.

When I try to connect and write default-env.json via the service key, below error message is always happened.
May I can get any help from you?
user: CustomUIForCapex $ hana-cli serviceKey capexdatamodel-db default ⠋  ERROR: Error: Command failed: xs service-key capexdatamodel-db default /bin/sh: 1: xs: not found

When I try to connect and write default-env.json via the service key, below error message is always happened.
May I can get any help from you?
user: CustomUIForCapex $ hana-cli serviceKey capexdatamodel-db default ⠋  ERROR: Error: Command failed: xs service-key capexdatamodel-db default /bin/sh: 1: xs: not found


[SPARK-33872][SQL] Throw more specific exceptions when relations/namespaces are not found

What changes were proposed in this pull request?

This is to address a concerned raised in https://github.com/apache/spark/pull/30862#discussion_r546563641
Currently, when relations/namespaces are not found, a general AnalysisException is thrown in CheckAnalysis. This can be improved by throwing more specific (already existing) exceptions such as NoSuchNamespaceException and NoSuchTableException.
Why are the changes needed?

To use more specific exceptions.
Does this PR introduce any user-facing change?

Yes, a more specific exception will be thrown. Since these specific exceptions derive the AnalysisException, no change is required if the client code already catching AnalysisException.
How was this patch tested?

Existing tests

@cloud-fan / @MaxGekk Do we also want to update the tests to catch more specific exceptions? There are many places, so I wanted to check with you first. Thanks!

Test build #133182 has started for PR 30878 at commit 6893510.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/37780/

Test build #133182 has finished for PR 30878 at commit 6893510.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/37780/

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

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

We don't need to update the tests. The concrete exception classes all extend AnalysisException.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38835/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38835/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38835/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38835/

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

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

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


Update prometheus and grafana image and fixed prom spec

TODO:
Push required images to rancher's docker hub:
prom/prometheus:v2.11.1 -> rancher/prom-prometheus:v2.11.1
grafana/grafana:6.2.5 -> rancher/grafana-grafana: 6.2.5

Related Issue:

Update Prometheus and Grafana image to the latest version
https://github.com/rancher/rancher/issues/21827
Prometheus creationTimestamp is required for its podMetadata.
https://github.com/rancher/rancher/issues/21964

Solution:

Update Prometheus version from v2.7.1 to v.2.11.1
Update Grafana version from 5.4.3 to 6.2.5
Add default creationTimestamp of Prometheus object

This is much needed to be able to add Elastic 7.x as a source in Grafana!

LGTM

Grafana 6.3 was released yesterday, may want to update this ticket.
https://grafana.com/blog/2019/08/06/grafana-v6.3-released/

On my test cluster I just changed the Grafana deployment images to tag 6.3.0 and it still works
:-)

@guangbochen @loganhz please see @gabrielcalderon and let me know what you think

Update Grafana to latest 6.3.2.

@guangbochen Grafana 6.3.3 was just released. :-)


Review Publisher Information in Yaml before publishing

Description of the new feature/enhancement
A simple example is #131654 (https://github.com/microsoft/winget-pkgs/blob/4e76aed0d59412f0be0ecfefabfa14b5df05bec4/manifests/z/zokugun/MrCode/<IP_ADDRESS>53/zokugun.MrCode.locale.en-US.yaml#L7C1-L7C33) where someone published an app stating that it was published by Microsoft Corporation. This leads to end users being misled and could have been resolved by having, at least in this case, only certain accounts able to publish "Microsoft" applications or manually vet all that state they are, in some way, associated with Microsoft. This will be hard to police across all vendors, but I would hope that we can account for Microsoft publisher names being accurate in the future.
Proposed technical implementation details (optional)
No response

https://github.com/microsoft/winget-pkgs/issues/131654#issuecomment-1867812234


Add Eq1 Ord1 to NonEmptyList LazyNonEmptyList

Description of the change
Adds Eq1 and Ord1 instances to NonEmptyList and (todo) LazyNonEmptyList
Fixes #186

Checklist:

[ ] Added the change to the changelog's "Unreleased" section with a reference to this PR (e.g. "- Made a change (#0000)")
[ ] Linked any existing issues or proposals that this pull request should close
[ ] Updated or added relevant documentation
[ ] Added a test for the contribution (if applicable)

CI shows that the Lazy version of this change fails to compile, but the non-Lazy version works fine. Don't know why.

CI shows that the Lazy version of this change fails to compile, but the non-Lazy version works fine. Don't know why.

Should these changes be tested, and if so, I guess I should also add the same tests to the empty-able lists too?
Also, holding off on editing the changelogs for each of these PR, since that's going to cause a merge conflict after each PR is merged. Will do that right before 0.14

Should these changes be tested, and if so, I guess I should also add the same tests to the empty-able lists too?
Also, holding off on editing the changelogs for each of these PR, since that's going to cause a merge conflict after each PR is merged. Will do that right before 0.14

Actually let’s include the changelog updated in each PR please; the merge conflicts that would be introduced will all be very easy to fix.

Actually let’s include the changelog updated in each PR please; the merge conflicts that would be introduced will all be very easy to fix.

Thank you!

Thank you!


T adjust

Codecov Report

Merging #616 into master will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #616      +/-   ##
==========================================
- Coverage   90.37%   90.37%   -0.01%
==========================================
  Files          21       21
  Lines        1538     1537       -1
==========================================
- Hits         1390     1389       -1
  Misses        148      148

Flag
Coverage Δ

#unittests
90.37% <100.00%> (-0.01%)
:arrow_down:

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

Impacted Files
Coverage Δ

lineage/BaumWelch.py
94.66% <100.00%> (-0.08%)
:arrow_down:

lineage/tests/test_StateEstimation.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Address android devices disconnected alert

Open grafana alert: https://dotnet-eng-grafana.westus2.cloudapp.azure.com/d/mobileDevices/mobile-devices?editPanel=15&tab=alert&orgId=1
The instructions on how to resolve this alert can be found in the dnceng wiki
(grafana issue automation is one of the casualties of https://github.com/dotnet/dnceng/issues/4405)

Release Note Category

[ ] Feature changes/additions
[ ] Bug fixes
[ ] Internal Infrastructure Improvements

Release Note Description

https://github.com/dotnet/dnceng/issues/4452 is a better tracking issue now