Typical "ffmpeg could not be found" location problem? No it isn´t.

Checklist

[ x] I'm asking a question
[x ] I've looked through the README and FAQ for similar questions
[ x] I've searched the bugtracker for similar questions including closed ones

Question

Hi there, I have a question for you all.
I know I MUST look around for similar questions or troubleshooting but my problem is really different and yeah, I have looked so many pages without similar scenarios even.
I´m running this script https://github.com/MaZED-UP/bunny-cdn-drm-video-dl from a Macbook for your concern.
Problem.
There are a video series from a tutorial page I have been downloading (one by one) a long time ago but today I realized I can´t download a special one: it is posted in first place of the same section page I used to download.
The script still RUNS perfectly with other videos in the same section except for this one.
Following you´ll find the entire error message, and It would seems to be a ffmpeg permission or location directory problem but it doesn´t because (I repeat) the script runs perfectly with other videos in the same page section:
[generic] Extracting URL: https://iframe.mediadelivery.net/emedID/1920x1080/video.drm?context...74-aa33-96dfb607dbbd
[generic] video: Downloading webpage
[generic] video: Downloading m3u8 information
[generic] video: Checking m3u8 live status
[info] video: Downloading 1 format(s): 0
[download] Destination: /Users/---/Movies/.videofilename.mp4/videofilename.mp4
ERROR: m3u8 download detected but ffmpeg could not be found. Please install
Traceback (most recent call last):
File "/Users/---/b-cdn-drm-vod-dl.py", line 188, in
video.download()
File "/Users/---/b-cdn-drm-vod-dl.py", line 174, in download
ydl.download(url)
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/yt_dlp/YoutubeDL.py", line 3541, in download
self.__download_wrapper(self.extract_info)(
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/yt_dlp/YoutubeDL.py", line 3516, in wrapper
res = func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/yt_dlp/YoutubeDL.py", line 1576, in extract_info
return self.__extract_info(url, self.get_info_extractor(key), download, extra_info, process)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/yt_dlp/YoutubeDL.py", line 1587, in wrapper
return func(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/yt_dlp/YoutubeDL.py", line 1743, in __extract_info
return self.process_ie_result(ie_result, download, extra_info)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/yt_dlp/YoutubeDL.py", line 1802, in process_ie_result
ie_result = self.process_video_result(ie_result, download=download)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/yt_dlp/YoutubeDL.py", line 2952, in process_video_result
self.process_info(new_info)
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/yt_dlp/YoutubeDL.py", line 3418, in process_info
success, real_download = self.dl(temp_filename, info_dict)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/yt_dlp/YoutubeDL.py", line 3139, in dl
return fd.download(name, new_info, subtitle)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/yt_dlp/downloader/common.py", line 455, in download
ret = self.real_download(filename, info_dict)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/yt_dlp/downloader/external.py", line 50, in real_download
retval = self._call_downloader(tmpfilename, info_dict)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/yt_dlp/downloader/external.py", line 481, in _call_downloader
self.report_error('m3u8 download detected but ffmpeg could not be found. Please install')
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/yt_dlp/YoutubeDL.py", line 1054, in report_error
self.trouble(f'{self._format_err("ERROR:", self.Styles.ERROR)} {message}', *args, **kwargs)
File "/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/site-packages/yt_dlp/YoutubeDL.py", line 993, in trouble
raise DownloadError(message, exc_info)
yt_dlp.utils.DownloadError: ERROR: m3u8 download detected but ffmpeg could not be found. Please install
Thanks for your comments!!!!!

#30839: "if you were actually running yt-dlp ..."
But what you will be asked there is this: what version of ffmpeg is installed on your system (paste the text output of the command ffmpeg -version run in a Terminal), and, if none, why didn't you install it as the diagnostic asks.
yt-dl and yt-dlp can generally download media from m3u8 manifests but ffmpeg is needed for "live" media.

Thanks Dirkf, You were totally right It wasn´t installed ffmpeg.
I already tried to install ffmpeg with this instructions (https://amiaopensource.github.io/ffmpeg-artschool/). I had already installed brew but I have the following error installing ffmpeg:
==> Fetching libvorbis
==> Downloading https://raw.githubusercontent.com/Homebrew/homebrew-core/85c487f7d18b4c15cab0d4f3b22854cd03364fa6/Formula/lib/libvorbis.rb
################################################################################################################################################################ 100.0%
==> Downloading https://upload.wikimedia.org/wikipedia/commons/c/c8/Example.ogg
Already downloaded: /Users/rock/Library/Caches/Homebrew/downloads/e163886f3d57674f022eb584f07ef6d71dbbf58fb39c481a2c516ce6bfd4af18--Example.ogg
Error: ffmpeg: Failed to download resource "libvorbis"
Download failed: Homebrew-installed curl is not installed for: https://downloads.xiph.org/releases/vorbis/libvorbis-1.3.7.tar.xz
And ffmpeg was not installed.
Could you help me, please?

Really you should ask at the brewery, but it seems to be saying that curl is needed first.

Hey Dirkf, last was a Macos version problem I had to change to windows and now I have a new problem, sorry bother you with ths basic issues.
I really need ur help. I already install ffmpeg in Windows but I can´t still these two specific videos from a list of 20. The following is the new traceback and telling video url is not found but it really exists!!! I search for possible workarounds but I don´t find anything.

[generic] Extracting URL: https://iframe.mediadelivery.net/22f40a69-3da7-4047-818d-5d24936d0374/1982x1080/video.drm?context...0c-a5a1-4eba158173a9
[generic] video: Downloading webpage
[generic] video: Downloading m3u8 information
[generic] video: Checking m3u8 live status
[info] video: Downloading 1 format(s): 0
[download] Destination: C:\Users\Rock\Documents.Premium-25-23022024.mp4\Premium-25-23022024.mp4
[https @ 0000021a1e4c4700] HTTP error 404 Not Found
[in#0 @ 0000021a1e4c21c0] Error opening input: Server returned 404 Not Found
Error opening input file https://iframe.mediadelivery.net/22f40a69-3da7-4047-818d-5d24936d0374/1982x1080/404 - File Not Found404File Not Found.
Error opening input files: Server returned 404 Not Found
ERROR: ffmpeg exited with code<PHONE_NUMBER>
Traceback (most recent call last):
File "C:\Users\Rock\Documents\bunny2.py", line 188, in
video.download()
File "C:\Users\Rock\Documents\bunny2.py", line 174, in download
ydl.download(url)
File "C:\Users\Rock\AppData\Local\Programs\Python\Python312\Lib\site-packages\yt_dlp\YoutubeDL.py", line 3511, in download
self.__download_wrapper(self.extract_info)(
File "C:\Users\Rock\AppData\Local\Programs\Python\Python312\Lib\site-packages\yt_dlp\YoutubeDL.py", line 3486, in wrapper
res = func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Rock\AppData\Local\Programs\Python\Python312\Lib\site-packages\yt_dlp\YoutubeDL.py", line 1556, in extract_info
return self.__extract_info(url, self.get_info_extractor(key), download, extra_info, process)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Rock\AppData\Local\Programs\Python\Python312\Lib\site-packages\yt_dlp\YoutubeDL.py", line 1567, in wrapper
return func(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Rock\AppData\Local\Programs\Python\Python312\Lib\site-packages\yt_dlp\YoutubeDL.py", line 1723, in __extract_info
return self.process_ie_result(ie_result, download, extra_info)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Rock\AppData\Local\Programs\Python\Python312\Lib\site-packages\yt_dlp\YoutubeDL.py", line 1782, in process_ie_result
ie_result = self.process_video_result(ie_result, download=download)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Rock\AppData\Local\Programs\Python\Python312\Lib\site-packages\yt_dlp\YoutubeDL.py", line 2922, in process_video_result
self.process_info(new_info)
File "C:\Users\Rock\AppData\Local\Programs\Python\Python312\Lib\site-packages\yt_dlp\YoutubeDL.py", line 3388, in process_info
success, real_download = self.dl(temp_filename, info_dict)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Rock\AppData\Local\Programs\Python\Python312\Lib\site-packages\yt_dlp\YoutubeDL.py", line 3109, in dl
return fd.download(name, new_info, subtitle)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Rock\AppData\Local\Programs\Python\Python312\Lib\site-packages\yt_dlp\downloader\common.py", line 455, in download
ret = self.real_download(filename, info_dict)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Rock\AppData\Local\Programs\Python\Python312\Lib\site-packages\yt_dlp\downloader\external.py", line 80, in real_download
self.report_error('%s exited with code %d' % (
File "C:\Users\Rock\AppData\Local\Programs\Python\Python312\Lib\site-packages\yt_dlp\YoutubeDL.py", line 1045, in report_error
self.trouble(f'{self._format_err("ERROR:", self.Styles.ERROR)} {message}', *args, **kwargs)
File "C:\Users\Rock\AppData\Local\Programs\Python\Python312\Lib\site-packages\yt_dlp\YoutubeDL.py", line 984, in trouble
raise DownloadError(message, exc_info)
yt_dlp.utils.DownloadError: ERROR: ffmpeg exited with code<PHONE_NUMBER>

yt-dlp (wrong tracker), but neither project knows about your video host iframe.mediadelivery.net.
Search the Web for that host name to find hints that may or (probably) may not help.
Or create a Site Support Request for the actual site that is using this video host.

Thanks man!!!!
Regards!!


Flipping flag for contain

I am working on geo coordinates and needed to check if the point is inside the polygon, what i found is an issue whenever the condition is met the inside flag is flipped in my case it is always showing me false.
https://github.com/d3/d3-polygon/blob/master/src/contains.js#L11
Shouldn't it be like if it matches once it should be considered inside.

We’re not going to change the expected orientation of this method. If you are using spherical coordinates, you should probably be using d3.geoContains instead of d3-polygon. If you’re using planar (e.g., projected) coordinates that have the y-axis flipped, then you can negate the return value of d3.polygonContains or reverse the coordinates to get the desired behavior.


chore(release): v0.9.3 🎉

:robot: I have created a release beep boop
0.9.3 (2023-09-11)
Bug Fixes

contact: expose getTokenFromAuthCookie method (e7a0e4d)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/whodisio/simple-jwt-auth/releases/tag/v0.9.3 :sunflower:


Request the token with the window.location.search

https://github.com/cloudtty/cloudtty/blob/40f8e3c357f7321f547ca813454af361c4d07e7a/html/src/components/app.tsx#L14
Issue Reference: https://github.com/kubevela/kubevela/issues/5005
In our use case, the request token of the proxy server is in the window.location.search, without it the request is denied.
BTW, The Cloudtty instance works without the token.

@youhonglian PTAL, thanks

@youhonglian  and I just dig a bit about the /token
By default , the /token API will return nothing but no impact the normal behavior.
But when ttyd runs with --credential(username/password),  the /token API will return a "secret"(base64ed user/password) to frontend browser, then frontend will attach the "secret" to  ws(web socket) connection. When the "secret" in the ws is invalid, backend will reject this ws connection request.
That's why @youhonglian  asked whether you have enabled --credential for ttyd start parameter.
And moreover, when ttyd runs with --credential parameter,  it requires human to type the user/password on the  browser  popup box like below snapshot

if the user/password is correct, then the /token API will return the base64 credit and attach it to ws connection.
We didn't find any way to attach the "user/password" in  location.search in URL . it seems only browser interaction available.
So at the end, when you run ttyd with --credential, you can encounter the problem of unauthorized web socket connection.
But if you didn't enable  --credential, the issue should not happen.


'NoneType' object has no attribute 'headers' (completions endpoint)

When trying to use the completions endpoint (rather than chat_completions) on a vLLM runpod serverless instance I get a server error. This happens with all models that I've tried. The chat_completions endpoint works as expected.
This example from the vLLM quick start shows the issue
from openai import OpenAI

# Modify OpenAI's API key and API base to use vLLM's API server.
openai_api_key = "<MyApiKey>"
openai_api_base = "https://api.runpod.ai/v2/<endpoint_id>/openai/v1"
client = OpenAI(
    api_key=openai_api_key,
    base_url=openai_api_base,
)
completion = client.completions.create(model="Phi-3-small-8k-instruct",
                                      prompt="San Francisco is a")
print("Completion result:", completion)

On the client side I get a 500 Error response. On the Server I can see the error is 'NoneType' object has no attribute 'headers'
This is using the most recent vLLM 0.5.4

Update I installed vLLM 0.5.4 locally through pip and did not have this issue. It's specific to the runpod worker

Seeing this too

Same issue in vLLM 0.5.3 (runpod/worker-v1-vllm:stable-cuda12.1.0)

@Permafacture thanks for reporting this problem.
We are working on resolving this, I will keep you updated!

Is the issue resolved ?

Same issue in vLLM 0.5.4 on runpod. Any news about this?

We are also getting consistent issues from Runpod , and it is hampering our production pipelines . I think this issue is pending since 2-3 weeks , and the support team is not responding .
I think , it is the high time to switch from runpod to any other trustful vendor

@ericflo @naaviii12345 @jamorell @Permafacture @Juhong-Namgung @prashantjoshi22
We just released a bug fix: runpod/worker-v1-vllm:v1.3.1dev-cuda12.1.0. Can you please check if this is working for you?

How do I try this on Runpod? I've only used the quick deploy for the vllm worker

This has been fixed.

Thanks team :-)
On Thu, 19 Sept 2024 at 03:48, Marut Pandya @.***>
wrote:

This has been fixed.
—
Reply to this email directly, view it on GitHub
https://github.com/runpod-workers/worker-vllm/issues/104#issuecomment-2359501394,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADIQDET2OSA4ZO6OMGBV2H3ZXH34ZAVCNFSM6AAAAABNAK7LBGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJZGUYDCMZZGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: https://inference.memgpt.ai/chat/completion

I have tried many conversation with memGPT agent using https://inference.memgpt.ai .
It sounds good, at the beginning
But at some point of the conversation, after about 10 or 20 exchange between user and agent, it falls with a 4xx/5xx error
If i start another conversation from scratch, it is ok at the beginning but crashes same way at some point.
Is there a limitation of query per minute ( i don't think so , because if i wait for 2 min , my conversation is broken, and i can get something else than this error)
here is my config
cat ~/.memgpt/config
[defaults]
preset = memgpt_chat
persona = sam_pov
human = basic

[model]
model = memgpt-openai
model_endpoint = https://inference.memgpt.ai
model_endpoint_type = openai
context_window = 8192

[embedding]
embedding_endpoint_type = hugging-face
embedding_endpoint = https://embeddings.memgpt.ai
embedding_model = BAAI/bge-large-en-v1.5
embedding_dim = 1024
embedding_chunk_size = 300

[archival_storage]
type = postgres
path = /home/smag/.memgpt/chroma
uri = postgresql+pg8000://memgpt:memgpt@localhost:5432/memgpt

[recall_storage]
type = postgres
path = /home/smag/.memgpt
uri = postgresql+pg8000://memgpt:memgpt@localhost:5432/memgpt

[metadata_storage]
type = postgres
path = /home/smag/.memgpt
uri = postgresql+pg8000://memgpt:memgpt@localhost:5432/memgpt

[version]
memgpt_version = 0.3.19

[client]
anon_clientid = 00000000-0000-0000-0000-000000000000

and here is the crash

NFO:     <IP_ADDRESS>:41156 - "POST /api/agents/ecd4b98c-456d-44cf-8902-849dca9747a7/messages HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:34314 - "POST /api/agents/ecd4b98c-456d-44cf-8902-849dca9747a7/messages HTTP/1.1" 200 OK
[HTTP] launching GET request to https://spoggy-test2.solidcommunity.net/public/brains/Chateau_des_Robots/
archival_memories: [{'id': '5e1e9092-8379-1167-092e-bf5654ac26f3', 'contents': "Le 17 juillet 2024, j'ai eu une conversation avec l'utilisateur au sujet du container de Pod Solid à l'adresse suivante : https://spoggy-test2.solidcommunity.net/public/brains/Chateau_des_Robots/. J'ai récupéré et interprété les données en format Turtle et fourni des liens vers ces données. Cela pourrait être pertinent pour les interactions futures."}]
INFO:     <IP_ADDRESS>:33098 - "GET /api/agents/ecd4b98c-456d-44cf-8902-849dca9747a7/archival/all HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:39098 - "POST /api/agents/ecd4b98c-456d-44cf-8902-849dca9747a7/messages HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:45254 - "POST /api/agents/ecd4b98c-456d-44cf-8902-849dca9747a7/messages HTTP/1.1" 200 OK
[HTTP] launching GET request to https://spoggy-test2.solidcommunity.net/public/brains/Chateau_des_Robots/710924c4-26d0-45f4-8e26-8a3e9bcee1a3
Task exception was never retrieved
future: <Task finished name='Task-41' coro=<to_thread() done, defined at /usr/lib/python3.11/asyncio/threads.py:12> exception=HTTPError('500 Server Error: Internal Server Error for url: https://inference.memgpt.ai/chat/completions')>
Traceback (most recent call last):
  File "/usr/lib/python3.11/asyncio/threads.py", line 25, in to_thread
    return await loop.run_in_executor(None, func_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/smag/dev/MemGPT/memgpt/server/server.py", line 602, in user_message
    usage = self._step(user_id=user_id, agent_id=agent_id, input_message=packaged_user_message, timestamp=timestamp)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/smag/dev/MemGPT/memgpt/server/server.py", line 391, in _step
    new_messages, heartbeat_request, function_failed, token_warning, usage = memgpt_agent.step(
                                                                             ^^^^^^^^^^^^^^^^^^
  File "/home/smag/dev/MemGPT/memgpt/agent.py", line 722, in step
    raise e
  File "/home/smag/dev/MemGPT/memgpt/agent.py", line 646, in step
    response = self._get_ai_reply(
               ^^^^^^^^^^^^^^^^^^^
  File "/home/smag/dev/MemGPT/memgpt/agent.py", line 345, in _get_ai_reply
    raise e
  File "/home/smag/dev/MemGPT/memgpt/agent.py", line 320, in _get_ai_reply
    response = create(
               ^^^^^^^
  File "/home/smag/dev/MemGPT/memgpt/llm_api/llm_api_tools.py", line 106, in wrapper
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/home/smag/dev/MemGPT/memgpt/llm_api/llm_api_tools.py", line 212, in create
    response = openai_chat_completions_request(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/smag/dev/MemGPT/memgpt/llm_api/openai.py", line 399, in openai_chat_completions_request
    raise http_err
  File "/home/smag/dev/MemGPT/memgpt/llm_api/openai.py", line 389, in openai_chat_completions_request
    response.raise_for_status()  # Raises HTTPError for 4XX/5XX status
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/smag/dev/MemGPT/.venv/lib/python3.11/site-packages/requests/models.py", line 1024, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: https://inference.memgpt.ai/chat/completions

to avoid this error, i have changed agent.py line 710
to use  self.summarize_messages_inplace() . and now it works . it seems that the messages send were too long
        except Exception as e:
            printd(f"step() failed\nuser_message = {user_message}\nerror = {e}")

            # If we got a context alert, try trimming the messages length, then try again
            #if is_context_overflow_error(e):
                # A separate API call to run a summarizer

            self.summarize_messages_inplace()

                # Try step again
            return self.step(user_message, first_message=first_message, return_dicts=return_dicts)
            #else:
            #    printd(f"step() failed with an unrecognized exception: '{str(e)}'")
            #    raise e

to avoid this error, i have changed agent.py line 710 to use self.summarize_messages_inplace() . and now it works . it seems that the messages send were too long
        except Exception as e:
            printd(f"step() failed\nuser_message = {user_message}\nerror = {e}")

            # If we got a context alert, try trimming the messages length, then try again
            #if is_context_overflow_error(e):
                # A separate API call to run a summarizer

            self.summarize_messages_inplace()

                # Try step again
            return self.step(user_message, first_message=first_message, return_dicts=return_dicts)
            #else:
            #    printd(f"step() failed with an unrecognized exception: '{str(e)}'")
            #    raise e

did you write a PR for this?  ..  the free inference.memgpt.ai  made available since the beginning I really appreciate as do others with limited gpu/ compute power .. but the experience you describe has been going on since the beginning.  please make a pr - Thanks for finding a pos solution  .. will be testing it out

wow this little fix really worked!  Thanks!

Hi @quantumalchemy thxs for your feedback of my fix. ;-)
it seems that the only error catched making a summarize is "if is_context_overflow_error(e):"
but the inference process return a 404/500 error, when a too long message is send to the inference server that is not catched. this way if i get a 400/500 error i try a summarization and retry the step. but if it is another error it does it too, so could possibly loop with infinity run and potentialy infinity api consumption if we does not take care. perharps @sarahwooders or @cpacker could find a better way to summarize, or traet this 400/500 errors

thanks again for figuring this out .. I think your patch here only works for the memgpt llm endpoint
so I created a fork .. testing it works on latest v. + patch
was getting --> Failed to put inner thoughts in kwargs: Invalid control character at: line 2 column 270 (char 271)
without patch -- but like you said .. goes a little slower because of some extra looping.. but knock wood -- not on error.


Update relationship snapshot when recording dangling entities

Issue #5734
When we encounter an untracked entity in a navigation we save it for later fixup, but we were not adding these entities to the snapshot for the navigation. This later caused change detection to be confused, which resulted in the entities being removed from the navigation.

:shipit:


chore(main): release 1.1.0

:robot: I have created a release beep boop
1.1.0 (2024-02-28)
Features

Update workflow CI/CD, adjust gitflow. (d444b9d)
Update workflow CI/CD, adjust gitflow. (668f394)
Update workflow CI/CD, adjust gitflow. (45740c8)
Update workflow CI/CD, adjust gitflow. (857fd8d)
Update workflow CI/CD, adjust gitflow. (8680f44)
Update workflow CI/CD, adjust gitflow. (9c12b5f)
Update workflow CI/CD, adjust gitflow. (2f3e26f)
Update workflow CI/CD, adjust gitflow. (7a1bb65)
Update workflow CI/CD, adjust gitflow. (6356801)
Update workflow CI/CD, adjust gitflow. (dcd430a)
Update workflow CI/CD, adjust gitflow. (558bdc6)
Update workflow CI/CD, adjust gitflow. (37836dc)
Update workflow CI/CD. (eccb907)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/diillson/calculador-de-plr/releases/tag/v1.1.0 :sunflower:


test discover bug with Autodata in a base class

public class A
{
        [Theory]
        [AutoData]
        public void testsum_auto(int a )
        {
            var c = a + 1;
            Assert.False(false);
        }
}

public class B : A
{
// some tests
}

testsum_auto and tests after this are not discovered , comment out autodata / replace with inline data and its fine.
It may have been introduced in the latest xunit release but i cant confirm that.

likely due to Data Attribute now having different method to override.

copying the latest code into my own autoatribute works so either its fixed already and not published to general release nuget or it has to do with autodata not being in the same assembly which seems unlikely.

I've just tested that code on my environment and it appeared work fine. See details of my environment below.
Packages.config:
  <package id="AutoFixture" version="3.50.2" targetFramework="net452" />
  <package id="AutoFixture.Xunit2" version="3.50.2" targetFramework="net452" />
  <package id="xunit" version="2.2.0" targetFramework="net452" />
  <package id="xunit.abstractions" version="2.0.1" targetFramework="net452" />
  <package id="xunit.assert" version="2.2.0" targetFramework="net452" />
  <package id="xunit.core" version="2.2.0" targetFramework="net452" />
  <package id="xunit.extensibility.core" version="2.2.0" targetFramework="net452" />
  <package id="xunit.extensibility.execution" version="2.2.0" targetFramework="net452" />

Code:
public class InheritanceTestBase
{
    [Theory]
    [AutoData]
    public void testsum_auto(int a)
    {
        var c = a + 1;
        Assert.False(false);
    }
}

public class NestedClass : InheritanceTestBase
{
}

R# runner result:

Could you please clarify whether this issue is still reproducible? If so, could you please clarify more details. For instance, is that .NET Core project or not; are you able to repro it on a small empty project, etc.
Thanks.

Closing this one due to inactivity. @bklooste Feel free to re-open the issue if it still happens.


Add helpful toString() for Response Objects

Right now I see <momento.cache_operation_responses.CreateCacheResponse object at 0x1014d3430>

Got user feedback as well:
"I expect repr methods to be defined in the classes here. For example, CacheGetResponse should render the status (hit/miss) and value (if there is one). Without the repr methods it's difficult to introspect the objects interactively."

Response objects are now dataclasses which include appropriate __str__ and __repr__ implementations.


[Enhancement]: Add File Slot 3

Adds support for a 3rd file slot that can be used for saves.
The File Choose system largely already supported this (from JP 1.0), but just had early escapes for rendering and menu navigation.
The Sram system needed more work in terms of the actual management of the writing/reading processes and owl save management.
Opening as a draft to show what it looks like and pose some questions on implementation. Currently everything is behind a user toggle that is defaulted on.
Open Questions:

Should this be a user facing toggle?
If it is user facing, should it default on?
Should we create/maintain separate structs, functions, and code paths for Sram related functions based on the toggle, or should we modify the originals, and only have the toggle visually hide the file slot on the File Choose menus?

Build Artifacts

2ship-linux.zip
2ship-mac.zip
2ship-windows.zip

or should we modify the originals, and only have the toggle visually hide the file slot

Example of this PR if it were to modify original structs/funcs instead: https://github.com/HarbourMasters/2ship2harkinian/compare/develop...Archez:2ship2harkinian:file-slot-3-alt

Since you listed this as a open question I am gonna throw my 2 cents.
Unlike other enhancements I cannot see a sufficiently good reason why anyone would want to disable this. Aside from maybe the rare person who might be upset to see it "because it was not on my version of the game."
I personally think having this on by default is fine, and even having it always on could be fine.

I'm all for default on. No reason it can't be.
Inb4 "I opened my but it's OoT, how do I load mm in 2ship?"

Same as above, I don't see any problems to have this by default, unless the File3 texture isn't present in the PAL version or its supported language
However, we're far beyond the point of even considering that possibility anyway :D


Error with textlint config (== No rules found, textlint hasn’t done anything ==)

Is there an existing issue for this?

[X] I have searched the existing issues

Are you using the latest Super-linter version available?

[X] I am using the latest Super-linter version.

[X] I can reproduce the issue running Super-linter using complete version identifier (example: vX.Y.Z), and not just with a partial one (example: vX)

[X] I am using the super-linter/super-linter action or container image, and not the deprecated github/super-linter action or container image.

Are you resonably sure that it's a Super-linter issue, and not an issue related to a tool that Super-linter runs?

[X] I think that this is a Super-linter issue.

Current Behavior
Even with default linttext config (meaning, created by --init) super-linter throws an error.
This is .textlintrc.json:
{
  "plugins": {},
  "filters": {},
  "rules": {
    "date-weekday-mismatch": true,
    "editorconfig": true,
    "footnote-order": true,
    "no-curly-quotes": true,
    "no-todo": false,
    "period-in-header": true,
    "spelling": {
      "language": "en",
      "skipPatterns": ["JavaScript"],
      "wordDefinitionRegexp": "/[\\w']+/g",
      "suggestCorrections": true
    },
    "terminology": true
  }
}

Textlint works perfectly locally, checked with "lint-staged" hooks.

Required packages for textlint (and custom rules) are installed;

Expected Behavior
Otherwise throw an error of real "textlint" linting result or successful lint.
Super-Linter version
v7.2.0

Super-linter configuration
name: Lint
on: # yamllint disable-line rule:truthy
  push: null
  pull_request: null
permissions: {}
jobs:
  build:
    name: Lint
    runs-on: ubuntu-latest
    permissions:
      contents: read
      packages: read
      # To report GitHub Actions status checks
      statuses: write
    steps:
      - name: Checkout code
        uses: actions/checkout@v4
        with:
          # super-linter needs the full git history to get the
          # list of files that changed across commits
          fetch-depth: 0
      - name: Super-linter
        uses<EMAIL_ADDRESS># x-release-please-version
        env:
          # To report GitHub Actions status checks
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          MARKDOWN_CONFIG_FILE: .markdownlint.json
          FILTER_REGEX_EXCLUDE: .*workflows/.*
          LINTER_RULES_PATH: /
          IGNORE_GITIGNORED_FILES: true
          # super-linter doesn't support v9 ESLint
          #JAVASCRIPT_ES_CONFIG_FILE: 'eslint.config.mjs'
          #TYPESCRIPT_ES_CONFIG_FILE: 'eslint.config.mjs'
          JAVASCRIPT_ES_CONFIG_FILE: '.eslintrc.cjs'
          TYPESCRIPT_ES_CONFIG_FILE: '.eslintrc.cjs'
          NATURAL_LANGUAGE_CONFIG_FILE: '.textlintrc.json'
          # We are choosing ESLint and Standard over Prettier
          # because they are more robust and efficient, while prettier stays as the "primitive" base
          # it does not provide advanced settings and etc.
          VALIDATE_JAVASCRIPT_PRETTIER: false
          VALIDATE_TYPESCRIPT_PRETTIER: false
          VALIDATE_JSON_PRETTIER: false
          VALIDATE_MARKDOWN_PRETTIER: false
          VALIDATE_YAML_PRETTIER: false
          # super-linter doesn't support v9 ESLint, reason:
          # Invalid option '--ext' - perhaps you meant '-c'?
          VALIDATE_JSON: false
          FIX_JAVASCRIPT_STANDARD: true
          FIX_TYPESCRIPT_STANDARD: true

Relevant log output
2024-11-27 12:42:05 [INFO]   Linting NATURAL_LANGUAGE items...
Error: -27 12:42:05 [ERROR]   Found errors when linting NATURAL_LANGUAGE. Exit code: 1.
2024-11-27 12:42:05 [INFO]   Command output for NATURAL_LANGUAGE:
------

== No rules found, textlint hasn’t done anything ==

Possible reasons:
* Your textlint config file has no rules.
* You have no config file and you aren’t passing rules via command line.
* Your textlint config has a syntax error.

=> How to set up rules?
https://github.com/textlint/textlint/blob/master/docs/configuring.md
------

Steps To Reproduce

In this environment, with this config, make any push to "trigger" workflow;
Wait for the error.

Anything else?
If helpful, this is the repository's branch on which error occurs:
https://github.com/Falcion/Patternugit/tree/release/v2.2.0

Hi. Can you post the entire super-linter log so we can have a look?

Hi. Can you post the entire super-linter log so we can have a look?

Yes, of course, sorry for the waiting, this is ZIP with logs:
logs_31395913880.zip
And there is a link of run in GitHub Actions (if it may help):
https://github.com/Falcion/Patternugit/actions/runs/12050482245/job/33599458621

It seems that Super-linter is finding the textlint configuration file:
  2024-11-27 12:41:38 [INFO]   User provided file:[/github/workspace/.textlintrc.json] exists, setting rules file...

Can you please re-run the workflow with debug logging enabled? That would help getting the command that super-linter uses to run textlint.

It seems that Super-linter is finding the textlint configuration file:
  2024-11-27 12:41:38 [INFO]   User provided file:[/github/workspace/.textlintrc.json] exists, setting rules file...

Can you please re-run the workflow with debug logging enabled? That would help getting the command that super-linter uses to run textlint.

https://github.com/Falcion/Patternugit/actions/runs/12142690735/job/33917187721
In ZIP-format:
logs_31608964311.zip

That's useful.
Super-linter is running textlint with the following command: textlint -c /github/workspace/.textlintrc.json
I was able to reproduce this issue, and it's about missing textlint plugins. We currently install:
https://github.com/super-linter/super-linter/blob/d929d049cb8f37aaea41733aee6e456e5c74362a/dependencies/package.json#L51-L54
The textlint message is a bit cryptic here because it doesn't tell you what's actually happening. If you run textlint with the --debug option, you get a clearer error message:
...
error: { message: 'Can not load rule', errors: [
ReferenceError: Failed to load textlint's rule module: "no-todo" is not found.
See FAQ: https://github.com/textlint/textlint/blob/master/docs/faq/failed-to-load-textlints-module.md
...

In your configuration file, you enable the following rules that aren't installed:

date-weekday-mismatch
editorconfig
footnote-order
no-curly-quotes
no-todo
period-in-header
spelling

The only installed rule is terminology.
Turning this into a feature request.

Oh, so that's what it is: thanks for the detailed answer and your project! I'll wait for more updates.


Use 'trunk' as default label for Subversion repositories

This commit adds a new AbstractEnvironmentRepository that includes
a getDefaultLabel() method for all EnvironmentRepository
implementations. The default implementation returns 'master'.
SvnKitEnvironmentRepository overrides this method to return 'trunk'.
ConfigServerMvcConfiguration and ConfigServerBootstrapConfiguration
will utilize labels configured on the client and server before falling
back to the repository's default label.
Resolves #107

I'm not sure I understand why AbstractEnvironmentRepository (or any EnvironmentRepository implementation) needs a default label. Isn't the label always passed into the findOne() method explicitly? I'd expect the caller to always be responsible for providing the label.

Considering the labels, "master" and "trunk" are fairly specific to Git and Subversion respectively, it seems reasonable OOD to make those properties of the EnvironmentRepository implementations. I considered another findOne() method that did not accept a label (to correspond with the same method in the controller). Then it could use the default label from the repository internally. In the end it felt a bit like clutter to add another method though, but maybe that would be a good idea? An alternative route could be to set this in ConfigServerConfiguration when the Profile specific settings/beans are applied.

I see. I just hate using base classes for contracts I guess. Maybe we should add the method to the EnvironmentRepository interface? Or else the externalization concerns should go in ConfigServerProperties. I think I prefer the latter, but without seeing it I'm not sure.

Deleting AbstractEnvironmentRepository and moving getDefaultLabel() to EnvironmentRepository seems like a good way to go.

I did add getDefaultLabel() to EnvironmentRepository since the interface is what is passed around everywhere. So in terms of a contract, it's not reliant on a base class. I didn't really want to add the base class, but the reason I did was to have a single place to define the default label for all repository implementations. Removing AbstractEnvironmentRepository would obviously mean adding getDefaultLabel() into each repository class. Otherwise, I'm happy to remove it.

Let's remove it then. I'm sure there is no actual "base class" of common shared defaults since the default label is very backend specific.

ok, will do. thanks.

Changes have been pushed. I removed AbstractEnvironmentRepository as discussed and updated the affected repository implementations.

:+1:


Use recent perl version

Hey @judofyr, thank you so much for your work!
Please use a more recent perl version than the hard-coded 5.18.1 from your AWS, at least 5.20+. Is there maybe a better way than using the tarball from AWS nowadays?
Thank you, best wishes

I don't know what's the recommended way to build custom buildpacks these days. I'm guessing it's based on Dockerfile. I'm not using this for anything so I don't have any big plans in making an updated one unfortunately.

OK, thanks anyway!


Add UUID implementation compatibility with OSSP uuid

The current UUID calls rely on libuuid. Other UUID implementations or existing libraries are not compatible with this Azure utility.
The OSSP uuid is another well-known UUID library for embedded targets, which is currently not supported. Therefore, despite of having an UUID library available, I have to install another dependency (libuuid-dev) to build for my target, or modify the source code.
Would it be possible to add compatibility with OSSP uuid?

No longer required. Boost UUID library is a better alternative.


Support for Ailunce HD1 addition?

Hi @un-creatrix ! Thanks for logging an issue. Can you elaborate a bit more on this? It's hard to tell if you're asking for a new feature to be added, or if you're asking if the maintainers are open to a specific contribution.
PS: If I do not hear back in a few weeks, I'll assume this is abandoned.

I am looking to have this radio supported and would be willing to do the work just don't know where to start


Error in index space launcher

This is the error I get when I added the index space launch, could you please tell me what's wrong with this? Thanks a lot!
main: /home/xyyue/legion/runtime/legion/legion_tasks.cc:8818: virtual void LegionRuntime::HighLevel::IndexTask::trigger_dependence_analysis(): Assertion `rerun_analysis_requirements.empty()' failed.
*** Caught a fatal signal: SIGABRT(6) on node 0/1
[0] /usr/bin/gdb -nx -batch -x /tmp/gasnet_UkxE5e '/local/home/xyyue/cg_codes/./main' 29205
[0] [New LWP 29213]
[0] [New LWP 29212]
[0] [New LWP 29211]
[0] [New LWP 29210]
[0] [New LWP 29209]
[0] [New LWP 29208]
[0] [New LWP 29207]
[0] [New LWP 29206]
[0] [Thread debugging using libthread_db enabled]
[0] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[0] pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[0]   Id   Target Id         Frame
[0]   9    Thread 0x7f9f02d1a700 (LWP 29206) "main" 0x00007f9f057d812d in poll () at ../sysdeps/unix/syscall-template.S:81
[0]   8    Thread 0x7f9eff14a700 (LWP 29207) "main" 0x00007f9f057dcda3 in select () at ../sysdeps/unix/syscall-template.S:81
[0]   7    Thread 0x7f9efe539700 (LWP 29208) "main" 0x00007f9f057d812d in poll () at ../sysdeps/unix/syscall-template.S:81
[0]   6    Thread 0x7f9ec9937700 (LWP 29209) "main" 0x0000000000d67230 in gasnetc_snd_reap.constprop ()
[0]   5    Thread 0x7f9f003e8700 (LWP 29210) "main" pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[0]   4    Thread 0x7f9ec9136700 (LWP 29211) "main" pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[0]   3    Thread 0x7f9f045d9700 (LWP 29212) "main" 0x00007f9f057abb99 in __libc_waitpid (pid=29233, stat_loc=stat_loc@entry=0x7f9ec83fb150, options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:40
[0]   2    Thread 0x7f9f045d5700 (LWP 29213) "main" pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[0] * 1    Thread 0x7f9f06ddd7c0 (LWP 29205) "main" pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[0]
[0] Thread 9 (Thread 0x7f9f02d1a700 (LWP 29206)):
[0] #0  0x00007f9f057d812d in poll () at ../sysdeps/unix/syscall-template.S:81
[0] #1  0x00007f9f05001196 in poll_dispatch () from /usr/local/openmpi-1.8.2/lib/libopen-pal.so.6
[0] #2  0x00007f9f04ff84fb in opal_libevent2021_event_base_loop () from /usr/local/openmpi-1.8.2/lib/libopen-pal.so.6
[0] #3  0x00007f9f052a396e in orte_progress_thread_engine () from /usr/local/openmpi-1.8.2/lib/libopen-rte.so.7
[0] #4  0x00007f9f067c0182 in start_thread (arg=0x7f9f02d1a700) at pthread_create.c:312
[0] #5  0x00007f9f057e547d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
[0]
[0] Thread 8 (Thread 0x7f9eff14a700 (LWP 29207)):
[0] #0  0x00007f9f057dcda3 in select () at ../sysdeps/unix/syscall-template.S:81
[0] #1  0x00007f9f014ed856 in service_thread_start () from /usr/local/openmpi-1.8.2/lib/openmpi/mca_btl_openib.so
[0] #2  0x00007f9f067c0182 in start_thread (arg=0x7f9eff14a700) at pthread_create.c:312
[0] #3  0x00007f9f057e547d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
[0]
[0] Thread 7 (Thread 0x7f9efe539700 (LWP 29208)):
[0] #0  0x00007f9f057d812d in poll () at ../sysdeps/unix/syscall-template.S:81
[0] #1  0x00007f9f014ec5f5 in btl_openib_async_thread () from /usr/local/openmpi-1.8.2/lib/openmpi/mca_btl_openib.so
[0] #2  0x00007f9f067c0182 in start_thread (arg=0x7f9efe539700) at pthread_create.c:312
[0] #3  0x00007f9f057e547d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
[0]
[0] Thread 6 (Thread 0x7f9ec9937700 (LWP 29209)):
[0] #0  0x0000000000d67230 in gasnetc_snd_reap.constprop ()
[0] #1  0x0000000000d6f89c in gasnetc_AMPoll ()
[0] #2  0x0000000000d22ea7 in gasneti_AMPoll () at /usr/local/gasnet-1.22.4-openmpi/include/gasnet_help.h:597
[0] #3  0x0000000000d38820 in gasnet_AMPoll () at /usr/local/gasnet-1.22.4-openmpi/include/gasnet_help.h:712
[0] #4  0x0000000000d37d8a in EndpointManager::polling_worker_loop (this=0x1726380) at /home/xyyue/legion/runtime/activemsg.cc:2141
[0] #5  0x0000000000d3f2b0 in Realm::Thread::thread_entry_wrapper<EndpointManager, &EndpointManager::polling_worker_loop> (obj=0x1726380) at /home/xyyue/legion/runtime/realm/threads.inl:127
[0] #6  0x0000000000cf1061 in Realm::KernelThread::pthread_entry (data=0x172bf00) at /home/xyyue/legion/runtime/realm/threads.cc:562
[0] #7  0x00007f9f067c0182 in start_thread (arg=0x7f9ec9937700) at pthread_create.c:312
[0] #8  0x00007f9f057e547d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
[0]
[0] Thread 5 (Thread 0x7f9f003e8700 (LWP 29210)):
[0] #0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[0] #1  0x0000000000d36c5c in IncomingMessageManager::get_messages (this=0x172bf60, sender=@0x7f9f003e7cac: -1, wait=true) at /home/xyyue/legion/runtime/activemsg.cc:715
[0] #2  0x0000000000d36dd1 in IncomingMessageManager::handler_thread_loop (this=0x172bf60) at /home/xyyue/legion/runtime/activemsg.cc:754
[0] #3  0x0000000000d3efae in Realm::Thread::thread_entry_wrapper<IncomingMessageManager, &IncomingMessageManager::handler_thread_loop> (obj=0x172bf60) at /home/xyyue/legion/runtime/realm/threads.inl:127
[0] #4  0x0000000000cf1061 in Realm::KernelThread::pthread_entry (data=0x172c1c0) at /home/xyyue/legion/runtime/realm/threads.cc:562
[0] #5  0x00007f9f067c0182 in start_thread (arg=0x7f9f003e8700) at pthread_create.c:312
[0] #6  0x00007f9f057e547d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
[0]
[0] Thread 4 (Thread 0x7f9ec9136700 (LWP 29211)):
[0] #0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[0] #1  0x0000000000ca7b4c in GASNetCondVar::wait (this=0x172c248) at /home/xyyue/legion/runtime/activemsg.h:169
[0] #2  0x0000000000cc1109 in LegionRuntime::LowLevel::DmaRequestQueue::dequeue_request (this=0x172c220, sleep=true) at /home/xyyue/legion/runtime/lowlevel_dma.cc:329
[0] #3  0x0000000000cc6ccb in LegionRuntime::LowLevel::DmaRequestQueue::worker_thread_loop (this=0x172c220) at /home/xyyue/legion/runtime/lowlevel_dma.cc:3558
[0] #4  0x0000000000cd6a64 in Realm::Thread::thread_entry_wrapper<LegionRuntime::LowLevel::DmaRequestQueue, &LegionRuntime::LowLevel::DmaRequestQueue::worker_thread_loop> (obj=0x172c220) at /home/xyyue/legion/runtime/realm/threads.inl:127
[0] #5  0x0000000000cf1061 in Realm::KernelThread::pthread_entry (data=0x172c4c0) at /home/xyyue/legion/runtime/realm/threads.cc:562
[0] #6  0x00007f9f067c0182 in start_thread (arg=0x7f9ec9136700) at pthread_create.c:312
[0] #7  0x00007f9f057e547d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
[0]
[0] Thread 3 (Thread 0x7f9f045d9700 (LWP 29212)):
[0] #0  0x00007f9f057abb99 in __libc_waitpid (pid=29233, stat_loc=stat_loc@entry=0x7f9ec83fb150, options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:40
[0] #1  0x00007f9f057312e2 in do_system (line=<optimized out>) at ../sysdeps/posix/system.c:148
[0] #2  0x0000000000d7ca58 in gasneti_bt_gdb ()
[0] #3  0x0000000000d7f8bb in gasneti_print_backtrace ()
[0] #4  0x0000000000dd83f1 in gasneti_defaultSignalHandler ()
[0] #5  <signal handler called>
[0] #6  0x00007f9f05721cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
[0] #7  0x00007f9f057250d8 in __GI_abort () at abort.c:89
[0] #8  0x00007f9f0571ab86 in __assert_fail_base (fmt=0x7f9f0586b830 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0xdf6f50 "rerun_analysis_requirements.empty()", file=file@entry=0xdf4e90 "/home/xyyue/legion/runtime/legion/legion_tasks.cc", line=line@entry=8818, function=function@entry=0xdfd980 <LegionRuntime::HighLevel::IndexTask::trigger_dependence_analysis()::__PRETTY_FUNCTION__> "virtual void LegionRuntime::HighLevel::IndexTask::trigger_dependence_analysis()") at assert.c:92
[0] #9  0x00007f9f0571ac32 in __GI___assert_fail (assertion=0xdf6f50 "rerun_analysis_requirements.empty()", file=0xdf4e90 "/home/xyyue/legion/runtime/legion/legion_tasks.cc", line=8818, function=0xdfd980 <LegionRuntime::HighLevel::IndexTask::trigger_dependence_analysis()::__PRETTY_FUNCTION__> "virtual void LegionRuntime::HighLevel::IndexTask::trigger_dependence_analysis()") at assert.c:101
[0] #10 0x0000000000a67221 in LegionRuntime::HighLevel::IndexTask::trigger_dependence_analysis (this=0x1774420) at /home/xyyue/legion/runtime/legion/legion_tasks.cc:8818
[0] #11 0x0000000000c0f04c in LegionRuntime::HighLevel::Internal::high_level_runtime_task (args=0x7f9ec861b180, arglen=12, p=...) at /home/xyyue/legion/runtime/legion/runtime.cc:16022
[0] #12 0x0000000000d4d37a in Realm::Task::execute_on_processor (this=0x7f9ec861d380, p=...) at /home/xyyue/legion/runtime/realm/tasks.cc:106
[0] #13 0x0000000000d4fcb8 in Realm::UserThreadTaskScheduler::execute_task (this=0x172cb00, task=0x7f9ec861d380) at /home/xyyue/legion/runtime/realm/tasks.cc:923
[0] #14 0x0000000000d4e343 in Realm::ThreadedTaskScheduler::scheduler_loop (this=0x172cb00) at /home/xyyue/legion/runtime/realm/tasks.cc:482
[0] #15 0x0000000000d530e6 in Realm::Thread::thread_entry_wrapper<Realm::ThreadedTaskScheduler, &Realm::ThreadedTaskScheduler::scheduler_loop> (obj=0x172cb00) at /home/xyyue/legion/runtime/realm/threads.inl:127
[0] #16 0x0000000000cf1c81 in Realm::UserThread::uthread_entry () at /home/xyyue/legion/runtime/realm/threads.cc:747
[0] #17 0x00007f9f057348b0 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
[0] #18 0x0000000000000000 in ?? ()
[0]
[0] Thread 2 (Thread 0x7f9f045d5700 (LWP 29213)):
[0] #0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[0] #1  0x0000000000ca7b4c in GASNetCondVar::wait (this=0x172d320) at /home/xyyue/legion/runtime/activemsg.h:169
[0] #2  0x0000000000d4d52f in Realm::ThreadedTaskScheduler::WorkCounter::wait_for_work (this=0x172d2e8, old_counter=15) at /home/xyyue/legion/runtime/realm/tasks.cc:230
[0] #3  0x0000000000d4e702 in Realm::ThreadedTaskScheduler::wait_for_work (this=0x172d1e0, old_work_counter=15) at /home/xyyue/legion/runtime/realm/tasks.cc:574
[0] #4  0x0000000000d4fee9 in Realm::UserThreadTaskScheduler::wait_for_work (this=0x172d1e0, old_work_counter=15) at /home/xyyue/legion/runtime/realm/tasks.cc:1017
[0] #5  0x0000000000d4e636 in Realm::ThreadedTaskScheduler::scheduler_loop (this=0x172d1e0) at /home/xyyue/legion/runtime/realm/tasks.cc:550
[0] #6  0x0000000000d530e6 in Realm::Thread::thread_entry_wrapper<Realm::ThreadedTaskScheduler, &Realm::ThreadedTaskScheduler::scheduler_loop> (obj=0x172d1e0) at /home/xyyue/legion/runtime/realm/threads.inl:127
[0] #7  0x0000000000cf1c81 in Realm::UserThread::uthread_entry () at /home/xyyue/legion/runtime/realm/threads.cc:747
[0] #8  0x00007f9f057348b0 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
[0] #9  0x0000000000000000 in ?? ()
[0]
[0] Thread 1 (Thread 0x7f9f06ddd7c0 (LWP 29205)):
[0] #0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
[0] #1  0x0000000000ca7b4c in GASNetCondVar::wait (this=0x15c88f8) at /home/xyyue/legion/runtime/activemsg.h:169
[0] #2  0x0000000000ca6753 in Realm::RuntimeImpl::run (this=0x15c8820, task_id=0, style=Realm::Runtime::ONE_TASK_ONLY, args=0x0, arglen=0, background=false) at /home/xyyue/legion/runtime/realm/runtime_impl.cc:1121
[0] #3  0x0000000000ca22c0 in Realm::Runtime::run (this=0x7fffd4d7a280, task_id=0, style=Realm::Runtime::ONE_TASK_ONLY, args=0x0, arglen=0, background=false) at /home/xyyue/legion/runtime/realm/runtime_impl.cc:136
[0] #4  0x0000000000c0cf04 in LegionRuntime::HighLevel::Internal::start (argc=3, argv=0x7fffd4d7a468, background=false) at /home/xyyue/legion/runtime/legion/runtime.cc:15025
[0] #5  0x00000000009fa7ad in LegionRuntime::HighLevel::Runtime::start (argc=3, argv=0x7fffd4d7a468, background=false) at /home/xyyue/legion/runtime/legion/legion.cc:3694
[0] #6  0x00000000009ccbdd in main (argc=3, argv=0x7fffd4d7a468) at main.cc:318
Aborted

That's an interesting failure mode.  Do you think you can make a minimal test case and attach it to this issue?

I have narrowed down the problem, it is in the constructor of the Index Launcher. There I try to add some Region Requirements, and if I delete them, then things work well. I will further check the validity of the Logical Regions. But in the meantime, could you please give me some hint on the possible reasons for this? Thanks a lot!!

I don't think this is your fault, but is instead a bug in the runtime.  It would be good if you could create a small test case for me to work with so I can better understand the nature of the problem.

Actually, I have a guess as to the cause.  Here are a few questions that will help narrow down the problem.  There should be one region requirement in your index space launch that is causing this issue.

What are the privileges on this region requirement (read-only, read-write, reduce)?
Is this is a projection region requirement?
If yes, what is the projection function you are using?
If it is a projection region requirement with a custom projection are the regions it is computing disjoint from each other?
If it is a projection region requirement, but you are using the default projection function, is the partition you are projecting over disjoint or aliased?

My hypothesis is that you are getting interfering region requirements for multiple points in your index space task launch and the runtime is not doing a good job reporting this error.  However, I would like to confirm this is the issue first.  Answers to those questions will help.  A small test case that reproduces the problem would be even better.

Thanks a lot for the message.
•	Actually I have tried adding several region requirements, some of them are read-only and some of them are read-write. Adding any of them will cause the failure.
•	They are all projection region requirements and I’m using the default projection function.
•	The partition I’m using is disjoint.
I do know that all the points within an index space task launch are required to be non-interfering with each other either because use disjoint regions or non-interfering privileges. I’ll double check, and maybe I got something wrong in my code. At the same time, I’ll try to reduce the problem and provide a small test case.
Thanks again!!

Hmm interesting.  Yeah, a small test case would be very useful.

Just an update. I have figured out that the reason for some of the failure is that I forgot to unmap the physical region before I use the aliased logical region in the subtasks. But one region requirement is still causing failure, I'll continue trying to figure it out...

Ok, even if that is the case, the runtime should automatically be unmapping and then remapping the conflicting region around your index space task launch (it does this implicitly to avoid deadlock, but it will incur a performance cost).  Play around with that to see if it is impacting the manifestation of the bug.

Do you mean whether there are unmapping statements in my code won't affect it's correctness? But the fact is that if I do the unmapping by myself, it works; then I simply comment the single line of unmapping statement, and the error occurs...

Yes, the unmapping statements should only impact the performance of your code.  If it changes the correctness, then that is a runtime bug.  If that is part of the problem, make sure to include that in the small example you are working on generating.

This issue has been resolved as result of poor warning messages being issued for interfering region requirements.


stacked_themes Dependencies rxdart ^0.26.0

can you please upgrade rxdart dependencies to latest ^0.26.0

Will do so. I should get to it today at some point.

Updated in 0.2.4


Always pass the QueryContext into TransformFunctionFactory

So that the literal transform values can be reused

Codecov Report

Merging #10320 (1028fc5) into master (1fce07e) will decrease coverage by 55.07%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             master   #10320       +/-   ##
=============================================
- Coverage     68.82%   13.75%   -55.07%
+ Complexity     5851      221     -5630
=============================================
  Files          2027     1973       -54
  Lines        109891   107491     -2400
  Branches      16685    16418      -267
=============================================
- Hits          75637    14790    -60847
- Misses        28897    91522    +62625
+ Partials       5357     1179     -4178

Flag
Coverage Δ

integration2
?

unittests1
?

unittests2
13.75% <0.00%> (-0.02%)
:arrow_down:

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

Impacted Files
Coverage Δ

...core/operator/filter/ExpressionFilterOperator.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...perator/filter/H3InclusionIndexFilterOperator.java
0.00% <0.00%> (-82.70%)
:arrow_down:

...ot/core/operator/filter/H3IndexFilterOperator.java
0.00% <0.00%> (-82.30%)
:arrow_down:

.../core/operator/query/SelectionOrderByOperator.java
0.00% <0.00%> (-95.31%)
:arrow_down:

...erator/transform/PassThroughTransformOperator.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...not/core/operator/transform/TransformOperator.java
0.00% <0.00%> (-96.67%)
:arrow_down:

...r/transform/function/TransformFunctionFactory.java
0.00% <0.00%> (-89.94%)
:arrow_down:

...ava/org/apache/pinot/core/plan/FilterPlanNode.java
0.00% <0.00%> (-83.21%)
:arrow_down:

.../org/apache/pinot/core/plan/TransformPlanNode.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../core/startree/plan/StarTreeTransformPlanNode.java
0.00% <0.00%> (-60.00%)
:arrow_down:

... and 1577 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Display performance in online documentation

Use the html output from the performance analysis directly as a page in the online documentation.
I uploaded directly as index.html under /docs/performance/, but this does not seem to work.
Figure it out.

This was addressed in the version released and submitted for review in Bioinformatics (May, 2023).


handlr-regex: init at 0.8.5

Description of changes
Add handlr-regex, a fork of the resource opener handlr that adds a handful of features, most notably the ability to associate files and URIs to programs using regular expressions.

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2205

Thank you!


nuclei: 2.9.15 -> 3.0.0

Description of changes

Diff: https://github.com/projectdiscovery/nuclei/compare/v2.9.15...v3.0.0
Changelog: https://github.com/projectdiscovery/nuclei/releases/tag/v3.0.0
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 262171 run on x86_64-linux 1

1 package built:

nuclei

Result of nixpkgs-review pr 262171 run on x86_64-linux 1

1 package built:

nuclei


Assignment1_XinminChu

I finished it 4 days ago, but failed to create new pull request. Thank you very much.

good job. you need to answer the question for task 2. your grade 128


Add Readme to public api and document

When using howfairis as library I would like to compare the checkers compliance with the readmes. To do that I need to call the Readme.get_compliance() method. However this method is currently not public and undocumented.

Agreed, let's add it to the public interface. Probably together with #230 and #226

PR was merged, closing


Tests: fix flake by ensuring source-protection finalizer is removed

What this PR does
Hey all,
We've seen some flakes in CI caused by a finalizer preventing a VM from being deleted. The finalizer is being left by this test, which creates a failed snapshot but doesn't wait for the deadline to exceed. The test finishes with the finalizer being left on the VM.
This PR aims to fix this behavior by ensuring the snapshot fails and the finalizer is removed.
Why we need it and why it was done in this way
Follow up for: https://github.com/kubevirt/kubevirt/pull/11051.
Special notes for your reviewer

Release note

NONE

/test pull-kubevirt-e2e-k8s-1.26-sig-storage
/test pull-kubevirt-e2e-k8s-1.27-sig-storage
/test pull-kubevirt-e2e-k8s-1.28-sig-storage


PATH order is not correct

As of v3, this GitHub action does not add entries to PATH in the right order, because it iterates over the PATH entries set by VsDevCmd and calls core.addPath() for each one. This reverses their order -- core.addPath prepends PATH entries!)
One result of this is that if you request the x64_x86 toolchain (host_arch=x64 arch=x86), you get the following entries in PATH:
\path\to\VC\Tools\MSVC\14.28.29333\bin\HostX64\x64;\path\to\VC\Tools\MSVC\14.28.29333\bin\HostX64\x86
These entries are back to front, and this causes the wrong cl.exe being found.
Also, it's important to note that VsDevCmd also both appends and prepends entries to PATH. cl.exe and friends go the front, but other tools like the Visual Studio-bundled CMake and Ninja are appended at the end (so existing installs take precedence).
I suspect this action shouldn't be special-casing PATH, and should instead respect the value set by the vsdevcmd script.

This reverses their order -- core.addPath prepends PATH entries!)

It prepends them after the action. Each path given to addPath is appended to the paths file (https://github.com/actions/toolkit/blob/c861dd8859fe5294289fcada363ce9bc71e9d260/packages/core/src/file-command.ts#L21) which is only applied at the end of the action's execution.
Though perhaps GitHub adds the entries from that file in reverse order?

I suspect this action shouldn't be special-casing PATH, and should instead respect the value set by the vsdevcmd script.

I'm not sure I follow the suggestion here.
The action has to treat path specially since GitHub uses a different API to set path values vs other kinds of environment variables.

This reverses their order -- core.addPath prepends PATH entries!)

It prepends them after the action. Each path given to addPath is appended to the paths file (https://github.com/actions/toolkit/blob/c861dd8859fe5294289fcada363ce9bc71e9d260/packages/core/src/file-command.ts#L21) which is only applied at the end of the action's execution.
Though perhaps GitHub adds the entries from that file in reverse order?

I suspect this action shouldn't be special-casing PATH, and should instead respect the value set by the vsdevcmd script.

I'm not sure I follow the suggestion here.
The action has to treat path specially since GitHub uses a different API to set path values vs other kinds of environment variables.

It prepends them after the action. Each path given to addPath is appended to the paths file (https://github.com/actions/toolkit/blob/c861dd8859fe5294289fcada363ce9bc71e9d260/packages/core/src/file-command.ts#L21) which is only applied at the end of the action's execution.
Though perhaps GitHub adds the entries from that file in reverse order?

Yes, that seems to be what's happening. The docs suggest:

The runner will prepend the path given to the jobs PATH.

So if vsdevcmd generates a Path of A;B;<OldPath>;C, this GitHub action will call core.addPath("A"); core.addPath("B"); core.addPath("C"); and the resulting Path will be C;B;A;<OldPath>.

The action has to treat path specially since GitHub uses a different API to set path values vs other kinds of environment variables.

I don't think anything actually stops you calling exportVariable() for "Path" just like any other environment variable. addPath() function does more harm than good here I think.

It prepends them after the action. Each path given to addPath is appended to the paths file (https://github.com/actions/toolkit/blob/c861dd8859fe5294289fcada363ce9bc71e9d260/packages/core/src/file-command.ts#L21) which is only applied at the end of the action's execution.
Though perhaps GitHub adds the entries from that file in reverse order?

Yes, that seems to be what's happening. The docs suggest:

The runner will prepend the path given to the jobs PATH.

So if vsdevcmd generates a Path of A;B;<OldPath>;C, this GitHub action will call core.addPath("A"); core.addPath("B"); core.addPath("C"); and the resulting Path will be C;B;A;<OldPath>.

The action has to treat path specially since GitHub uses a different API to set path values vs other kinds of environment variables.

I don't think anything actually stops you calling exportVariable() for "Path" just like any other environment variable. addPath() function does more harm than good here I think.

Would be open to a PR to fix this. I'll get to it eventually, but it's low-priority for me so far.
(Frankly, I wish Microsoft would just release their own microsoft/setup-vsdev Action so I can deprecate this one...)


potentially package dependency as a far jar

another solution is to use spark-submit --package to define the dependency
in HDInsight side, we can add the fat jar to the class path

this might be not necessary after we replace the rest caller with new API

done in 2.0.4


elementShorthandPropsMapping override bug

elementShorthandPropsMapping when overriding with shorthand props, will not honor falsy theme-resolved values.
Reproduce

Set the canonical m, my, mb/mt shorthand props.
Pass values m={x1}, my={x2}, mb={x3}.
If x3 is a falsy value (e.g. 0 pixels), it does not explicitly override this.

Will research the issue more but I believe the issue is in https://github.com/uinix-js/uinix-ui/blob/main/lib/util/resolve-shorthand-props.js#L35, where we cannot naively use the || logical operator since falsy values are valid values.  We should do an explicit check if the resolved value is undefined.

Fixed in 7c0d7ce865da4a478f6f8ff36ddafcc41b4b069f using ?? instead of || in resolveShorthandProps


Some labels missing 'activity' in MF branch

Hi,
GO:0043495 'protein membrane adaptor' and its 3 children seem to be missing 'activity' at the end of their labels.
Same for GO:0044183 'protein folding chaperone', and, possibly, GO:0031386 'protein tag'.
Other adaptor and chaperone MF terms in GO are always appended with 'activity'.
Thanks,
Paola

I hadn't put 'activity' because those didn't seem like they could be mistaken for BPs. I am not sure it is a strong rule to have 'activity' on every MF. Let's discuss this on the next ontology call.

I made a spreadsheet of all types of 'activities' that are NOT under the 'catalytic activity branch:
https://docs.google.com/spreadsheets/d/1t4Oene3WmUIFaAAH2S37k-Pa81qdU2V5IKVq8eYYSL8/edit#gid=0
My plan would be to fix branch by branch, removing 'activity' as appropriate.
To be approved by the ontology group.
Thanks, Pascale

Pascale: to check if the usage matches the design patterns.

will be fixed by https://github.com/geneontology/go-ontology/issues/15323


[engineering]DocumentLabelTest is runtime dependent

assert.equal(getDocumentTreeItemLabel(doc), 0); depends on the function getDocumentLabelFields, which picks up the local workspace settings.
We need a default for the documentLabelFields array so that the success of the test does not depend on who is running it.

Might be interesting to if the functions extension is handling this in their tests.  In docker, I've been adding injectable functions/etc into extensionVariables.ts, similar to ext.ui.  Perhaps there should be a ext.settings.{get,set,etc} type of functionality that can be modified by tests.

This already available with the current release.


[RFC][Frontend] Return module for Relay frontend converter

As we have pass manager in Relay optimization and mostly use module as optimization unit, I suggest we change the Relay frontend converter to return a module instead of a function. The change also makes easier add prelude and global var in the frontend converter in the future. Frontend converter will preset the main function in the module to the converted function as
mod[mod.entry_func] = converted_func

Correspondingly we need to change the relay executor to be able to run the converted module. I use MxNet as an exmple to show the proposed change:
mod, _ = relay.frontend.from_mxnet(mx_sym, shapes, dtype)
for kind in ["graph", "debug"]:
    intrp = relay.create_executor(kind, mod=mod, ctx=ctx, target=target)
    op_res = intrp.evaluate()(*args)

When executor is given no input, it will execute the mod.entry_func by default.
cc @jroesch @tqchen @wweic @zhiics

Yeah, this is exactly what I think as well.

+1

+1

@icemelon9 #3353 was the draft I haven't finished yet.

+1

#3353


Smoothing in the Joint Metric

Hi, thanks for the great work and sharing the code!
May I ask which part of the code reflects your two observations mentioned in the paper, the Laplace smooth and Logistic function used to filter the visual and temporal information, I have some difficulties locate those implementations, thank you!

Found the Logistic smoothing, still have difficulties find Laplace smoothing

Found the Logistic smoothing, still have difficulties find Laplace smoothing

No laplace smoothing in this paper. It is just an observation in machine learning.

No Laplace  smoothing in this paper. It is just an observation in machine learning. Logistic smoothing shares similar idea with Laplace smoothing, which is used to adjust the probability of rare (but not impossible).

Thanks for the explanation!


Upgrade Ant to latest 1.9 version in OT 1.8.6

Is it possible to upgrade the version of Ant in the 1.8.6 OT? 1.8.5 ships with Ant 1.8.4 but 1.9.4 is the current version.
Starting with 1.9.1 there is a new option on the Zip target, zip64Mode, on which the EPUB transform depends in order to produce EPUBs that pass epubcheck. As far as I can tell there is no way to produce correct EPUB zips using Ant before 1.9.1.
I'm assuming that the OT-specific Ant code in 2.0 is based on the latest Ant source, so the required Zip support should be there.

Closing as obsolete.


[Search pipeline] Support query context modification in script processor

In the https://github.com/opensearch-project/OpenSearch/pull/7607, script processor only supported primitive types. As a next step, we should consider support query context modification.

Step 1, we will need a proposed Painless API for manipulating queries, since there are many query types, and IMO we don't just want to pass through the Java API.

Should we replace this issue with https://github.com/opensearch-project/OpenSearch/issues/9200 ?
How do RFCs and tasks interact?


sum panics on overflow..

gluesql> create table mytable (id int(8));
gluesql> insert into mytable values (100);
1 row inserted

gluesql> insert into mytable values (50);
1 row inserted

gluesql> select sum(id) from mytable;
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Value(BinaryOperationOverflow { lhs: I8(100), rhs: I8(50), operator: Add })', core/src/executor/aggregate/state.rs:62:72

I assume if we get an overflow, we need to try to upcast it to the next largest supported data type (I8 to I64) before throwing an overflow?
I8(100) + I8(50) => I8(150)  (overflow) vs
I8(100 + I8(50) => I64(150)    **** right answer.. (no overflow).

modifying try_add like so, seems to fix the issue:
 I8(rhs) => match lhs
                .checked_add(rhs) {
                    Some(x) => Ok(I8(x)),
                    None => self.try_add(&I64(rhs as i64)),
                },

I think we need a discussion about which type to cast to.

I think we need a discussion about which type to cast to.

I agree..   I also plan on implementing i32 (after the i128 PR is merged), so we could cast it to an i32 instead if that is what people want.
As everyone knows, we could also reach the same limits for other data types, i64 for example.  If checked_add returns None, we could auto promote to the next largest data type.  This makes sense to me.
What do other think?   If we implement this, each time we hit an overflow, we could just promote to the next largest data type, and then only i128 would throw an overflow.  (this of course is ignoring the decimal data type).


HBASE-24592 [brnach-2.2] Upgrade junit to 4.13

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 30s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-0 :warning:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-2.2 Compile Tests _

+1 :green_heart:
mvninstall
5m 37s
branch-2.2 passed

+1 :green_heart:
compile
3m  9s
branch-2.2 passed

+1 :green_heart:
shadedjars
4m 23s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
2m 46s
branch-2.2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 11s
the patch passed

+1 :green_heart:
compile
3m  7s
the patch passed

+1 :green_heart:
javac
3m  7s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  2s
The patch has no ill-formed XML file.

+1 :green_heart:
shadedjars
4m 21s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
28m 21s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 2.10.0 or 3.1.2 3.2.1.

+1 :green_heart:
javadoc
3m  1s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
258m 49s
root in the patch passed.

+1 :green_heart:
asflicense
0m 43s
The patch does not generate ASF License warnings.

327m 39s

Subsystem
Report/Notes

Docker
Client=19.03.11 Server=19.03.11 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1927/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1927

Optional Tests
dupname asflicense javac javadoc unit shadedjars hadoopcheck xml compile

uname
Linux 49d0d72d1fd7 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1927/out/precommit/personality/provided.sh

git revision
branch-2.2 / e7f17fe68d

Default Java
1.8.0_181

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1927/1/testReport/

Max. process+thread count
4843 (vs. ulimit of 10000)

modules
C: . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1927/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


Fix Availability Selection in Symbol Graph Loader

Bug/issue #, if applicable:  rdar://118207413
Summary
Currently, when the availability information comes from the SGFs and the Info.plist default availability section, the symbol graph loader fills each symbol with all the defined platforms in the Info.plist. This results in incorrect availability information being displayed in the subsequent documentation, as symbols are shown as available for platforms where they are not actually available, and, since DocC selects only one symbol from the unified symbol graph, the chosen symbol does not have the correct availability information for all its variants.
With this fix, each symbol will appear as available only in the platforms defined in the symbol SGF info. If there's default availability information defined in the Info.plist, we use it to fill any missing introduced version information, but only if the symbol exists in that platform.

Before this fix, the symbol graph loading looked like this (from the availability perspective):
Input:
tvOS-swift.symbols.json:
A -> { domain: tvOS }
watchOS-swift.symbols.json:
A -> { domain: watchOS, introduced: 8 }
Info.plist:
| tvOS | 3.0 |
| watchOS | 2.0 |
| iOS | 1.0 |
Symbols after symbol graph loading:
A -> { { domain: tvOS, introduced: 3 }, { domain: watchOS, introduced: 2.0 }, { domain: iOS, introduced: 1.0 } }
A -> { { domain: tvOS, introduced: 3 }, { domain: watchOS, introduced: 8.0 }, { domain: iOS, introduced: 1.0 } }
Resulting symbol availability in the docs:
A -> { { domain: tvOS, introduced: 3 }, { domain: watchOS, introduced: 2.0 }, { domain: iOS, introduced: 1.0 } }

Now it behaves like the following:
Input:
tvOS-swift.symbols.json:
A -> { domain: tvOS }
watchOS-swift.symbols.json:
A -> { domain: watchOS, introduced: 8 }
Info.plist:
| tvOS | 3.0 |
| watchOS | 2.0 |
| iOS | 1.0 |
Symbols after symbol graph loading:
A -> { { domain: tvOS, introduced: 3 } }
A -> { { domain: watchOS, introduced: 8.0 } }
Resulting symbol availability in the docs:
A -> { { domain: tvOS, introduced: 3 }, { domain: watchOS, introduced: 8.0 } }
Dependencies
N/A
Testing
Steps:

Preview the attached documentation catalog with the provided SGFs
Assert that the symbol A:

Is not available in VisionOS
Is available in watchOS from version 12 (availability defined in SGF)
Is available in tvOS from version 1.0 (availability defined in info.plist)

Testing.zip
Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[X] Added tests
[x] Ran the ./bin/test script and it succeeded
[ ] Updated documentation if necessary

Now it behaves like the following:
...
Info.plist:
| tvOS | 3.0 |
| watchOS | 2.0 |
| iOS | 1.0 |
...
Resulting symbol availability in the docs:
A -> { { domain: tvOS, introduced: 3 }, { domain: watchOS, introduced: 8.0 } }

I'm not sure that this is the right behavior but I could be convinced that it is.
I would have thought that this example would display iOS availability because a default value was specified in the Info.plist and there wasn't an iOS symbol graph file to provide more accurate, per-symbol availability for iOS.
In my mind, the lack of a symbol graph file for a given platform doesn't mean that the project is unavailable for that platform, just that there's no per-symbol availability information for that platform.

I would have thought that this example would display iOS availability because a default value was specified in the Info.plist and there wasn't an iOS symbol graph file to provide more accurate, per-symbol availability for iOS.

In the example described, I chose not to define any iOS SGF. This decision wasn't necessarily due to its nonexistence but rather because it lacks the symbol 'A.'
The way I see it is that the SGF is the source of truth for per-symbol availability information. If a symbol is not defined in the iOS SGF then it's because the non-existence on that platform. Default availability is useful when the symbol is available for a given platform but doesn't specify the introduced version; in such case it uses the default one, like I showed in the example for tvOS.
The main reason why I think this is how it should behave is because the Swift compiler can't tell the unavailability of a symbol; instead, the symbol simply does not exist within the scope of that platform (in contrast to the clang compiler, which provides information on unavailability), so, identifying the unavailability of a symbol on a platform involves comparing the domains where the symbol is defined against all other defined platforms. The difference operation between these two sets indicates the unavailable platforms.

In my mind, the lack of a symbol graph file for a given platform doesn't mean that the project is unavailable for that platform, just that there's no per-symbol availability information for that platform.

I don't share this idea because SGFs are essentially the JSON representation of the API. Therefore, the idea of being able to overwrite it through an info.plist file seems inappropriate to me.

I'm not sure that this is the right behavior but I could be convinced that it is.

I'm happy to further discuss this with you.

Similar to this https://github.com/apple/swift-docc/pull/807#pullrequestreview-1853490692 we can consider a unconditionallyAvailable property to cover the case you are mentioning.

In the example described, I chose not to define any iOS SGF. This decision wasn't necessarily due to its nonexistence but rather because it lacks the symbol 'A.'

That doesn't match the behavior of either Swift of Clang. If you extract symbols for a module without any public symbols you still get a symbol graph file with an empty list of symbols.

The way I see it is that the SGF is the source of truth for per-symbol availability information. If a symbol is not defined in the iOS SGF then it's because the non-existence on that platform. Default availability is useful when the symbol is available for a given platform but doesn't specify the introduced version; in such case it uses the default one, like I showed in the example for tvOS.

I agree with this. However, the lack of a symbol graph file for a platform doesn't mean that the module is unconditionally unavailable for that platform.

I agree that if there was an iOS symbol graph file and "A" wasn't in it, then A shouldn't display the default iOS availability from the Info.plist because the iOS symbol graph file provides more accurate, per-symbol information.
However, the way this PR is currently implemented; "A" doesn't get the default iOS availability (from the Info.plist) unless there's also an iOS symbol graph file and I feel like that is incorrect behavior.

However, the way this PR is currently implemented; "A" doesn't get the default iOS availability (from the Info.plist) unless there's also an iOS symbol graph file and I feel like that is incorrect behavior.

@d-ronnqvist Can you give an example of a scenario in which there would not be a iOS symbol graph file, but we would want to give symbols default iOS availability?

However, the way this PR is currently implemented; "A" doesn't get the default iOS availability (from the Info.plist) unless there's also an iOS symbol graph file and I feel like that is incorrect behavior.

@d-ronnqvist Can you give an example of a scenario in which there would not be a iOS symbol graph file, but we would want to give symbols default iOS availability?

The simplest example would be when building documentation for any multi platform target in Swift PM or in Xcode. That build is only for one platform at a time, meaning that if you built for macOS you won't have an iOS symbol graph file in that particular build.
Sofia has more details on various scenarios and what availability information is available to DocC.


Support Haskell number 'Infinity'

From rescript-v11 branch
https://github.com/plow-technologies/all/issues/13593
replaces this PR:
https://github.com/plow-technologies/rescript-aeson/pull/35

@mirko-plowtech the tests are slightly different one starts with a float and goes to a float, the other starts with a string and goes to a float to mimic what the value coming from Haskell.

@mirko-plowtech the tests are slightly different one starts with a float and goes to a float, the other starts with a string and goes to a float to mimic what the value coming from Haskell.

Ohh I see now! Sorry, I was to sleepy I guess..


[MapView] MapView has no propType for native prop RCTMap.mapType of native type MKMapType

Getting this bug in react-native 0.7.0-rc.2 at
React = require('react-native')

I'm not using MapView anywhere.

It looks like we're missing an entry in RCTConvert to handle this, PR coming, thanks for the report!

Scratch that, looks like those are in place - you might have to clean your Xcode build

This seems fine now– my React Pod's version didn't match my react-native version.

I ran into this same error by creating a new project react-native init TestProject and then changing the version in package.json to "react-native": "0.7.0-rc.2" and running npm install.

@asamiller - are you using cocoapods? Did you restart your packager after upgrading?

I had the same error, it is indeed resolved by restarting the packager

@brentvatne got this error and it doesnt make any sense to me. have been trying to upgrade my app to react native 0.8.0

@jawadrehman - did you restart the packager? try doing that as well as re-opening Xcode

I am seeing this on android.  I have restarted packager about 10 times, I have reinstalled react 10 times,  restarted the computer, restarted android studio.  I am using rn 19.

same error :

I was able to fix this by updating react from 19 to 25


Dont create Service Accounts through the operator

The current situation is kindof suboptimal.

The operator creates the KSA
The operator launches a daemonset/deployment using KSAs

But the KSAs need to be annotated to point to the GSA (GSAs are not managed by operator, they are managed by the SDK as they are done with gcloud). This means that there's always a moment in which the KSA is not associated with a GSA, and that moment causes problems.
One solution to this problem is to create the GSAs ahead of time, and tell the operator to do the annotations itself. The sequence of events would be:

Create cluster
Create GSAs and add corresponding policy bindings
Configure operator to use the correct GSAs
Create operator

Alternatively, a simpler solution would just be to stop creating the KSAs in the operator, and instead manage those purely in the SDK. This is likely confusing, but probably less confusing than what we have at the moment.
See #201 for some symptoms of this problem.

KSA=Kubernetes Service Account
GSA=Google Service Account

IMO, we should just move all the startup code out of the operator.
It would have been nice if you only had to install the operator and get a working kctf cluster, but that's not possible without giving the operator more gce permissions.

IMO, we should just move all the startup code out of the operator.
It would have been nice if you only had to install the operator and get a working kctf cluster, but that's not possible without giving the operator more gce permissions.

I'll try to move some things out and clean it up a bit.
I think we might not be able to fully remove the setup, because some of it is "internal" to the operator (like the pow secrets, network policy, etc), but we can start with https://github.com/google/kctf/blob/beta/kctf-operator/pkg/resources/service-accounts-sa.go
In the future we might wanna move all services (external-dns, certbot, gcsfuse) out of the operator and version them independently (say, with helm or something). But for now I think we can at least move the service accounts out, as they are the ones that have the weirdest setup.

I'll try to move some things out and clean it up a bit.
I think we might not be able to fully remove the setup, because some of it is "internal" to the operator (like the pow secrets, network policy, etc), but we can start with https://github.com/google/kctf/blob/beta/kctf-operator/pkg/resources/service-accounts-sa.go
In the future we might wanna move all services (external-dns, certbot, gcsfuse) out of the operator and version them independently (say, with helm or something). But for now I think we can at least move the service accounts out, as they are the ones that have the weirdest setup.

some of it is "internal" to the operator (like the pow secrets, network policy, etc)

Can you expand on this? I don't see why we couldn't create them outside the operator.

some of it is "internal" to the operator (like the pow secrets, network policy, etc)

Can you expand on this? I don't see why we couldn't create them outside the operator.

if we move everything out, including all services, then we could yes.
but with what we have at the moment, we will end up splitting maintenance of resources in 2 places, which isnt gr8

if we move everything out, including all services, then we could yes.
but with what we have at the moment, we will end up splitting maintenance of resources in 2 places, which isnt gr8


raise AttributeError(f"No {package_name} attribute {name}") AttributeError: No huggingface_hub attribute hf_api

Describe the bug
rta.sh
Traceback (most recent call last):
File "run.py", line 7, in
import datasets
File "/home/appuser/miniconda3/envs/pt2/lib/python3.8/site-packages/datasets/init.py", line 37, in
from .builder import ArrowBasedBuilder, BeamBasedBuilder, BuilderConfig, DatasetBuilder, GeneratorBasedBuilder
File "/home/appuser/miniconda3/envs/pt2/lib/python3.8/site-packages/datasets/builder.py", line 44, in
from .data_files import DataFilesDict, _sanitize_patterns
File "/home/appuser/miniconda3/envs/pt2/lib/python3.8/site-packages/datasets/data_files.py", line 120, in
dataset_info: huggingface_hub.hf_api.DatasetInfo,
File "/home/appuser/miniconda3/envs/pt2/lib/python3.8/site-packages/huggingface_hub/init.py", line 290, in getattr
raise AttributeError(f"No {package_name} attribute {name}")
AttributeError: No huggingface_hub attribute hf_api
Reproduction
No response
Logs
Traceback (most recent call last):
  File "run.py", line 7, in <module>
    import datasets
  File "/home/appuser/miniconda3/envs/pt2/lib/python3.8/site-packages/datasets/__init__.py", line 37, in <module>
    from .builder import ArrowBasedBuilder, BeamBasedBuilder, BuilderConfig, DatasetBuilder, GeneratorBasedBuilder
  File "/home/appuser/miniconda3/envs/pt2/lib/python3.8/site-packages/datasets/builder.py", line 44, in <module>
    from .data_files import DataFilesDict, _sanitize_patterns
  File "/home/appuser/miniconda3/envs/pt2/lib/python3.8/site-packages/datasets/data_files.py", line 120, in <module>
    dataset_info: huggingface_hub.hf_api.DatasetInfo,
  File "/home/appuser/miniconda3/envs/pt2/lib/python3.8/site-packages/huggingface_hub/__init__.py", line 290, in __getattr__
    raise AttributeError(f"No {package_name} attribute {name}")
AttributeError: No huggingface_hub attribute hf_api

System info
- huggingface_hub version: 0.13.2
- Platform: Linux-5.4.0-144-generic-x86_64-with-glibc2.10
- Python version: 3.8.5
- Running in iPython ?: No
- Running in notebook ?: No
- Running in Google Colab ?: No
- Token path ?: /home/appuser/.cache/huggingface/token
- Has saved token ?: False
- Configured git credential helpers:
- FastAI: N/A
- Tensorflow: N/A
- Torch: 1.7.1
- Jinja2: N/A
- Graphviz: N/A
- Pydot: N/A
- Pillow: 9.3.0
- hf_transfer: N/A
- ENDPOINT: https://huggingface.co
- HUGGINGFACE_HUB_CACHE: /home/appuser/.cache/huggingface/hub
- HUGGINGFACE_ASSETS_CACHE: /home/appuser/.cache/huggingface/assets
- HF_TOKEN_PATH: /home/appuser/.cache/huggingface/token
- HF_HUB_OFFLINE: False
- HF_HUB_DISABLE_TELEMETRY: False
- HF_HUB_DISABLE_PROGRESS_BARS: None
- HF_HUB_DISABLE_SYMLINKS_WARNING: False
- HF_HUB_DISABLE_IMPLICIT_TOKEN: False

Hi @wccccp, thanks for reporting.
That's weird since huggingface_hub has a module called hf_api and you are using a recent version of it.
Which version of datasets are you using? And is it a bug that you experienced only recently? (cc @lhoestq can it be somehow related to the recent release of datasets?)
@wccccp what I can suggest you is to uninstall and reinstall completely huggingface_hub and datasets. My first guess is that there is a discrepancy somewhere 😕


[JENKINS-15][JENKINS-28] Added option to notify repeated failure

Option is set to true by default.
Also added two test connection buttons in global and build slack settings.
And finally, did some code cleanup at places.

Candidate for merge means I will first merge your change locally, compile locally, and test locally in Jenkins before merging.

This will be in for the next release if all goes well in my testing.

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

Great. As I said, the code styling is all Netbeans. My part was only adding bugs in ;-)

For the note, I wish I had made the Repeat Failure Notification only showing when the Failure Notification is enabled (possibly below it, indented) but I'm not so familiar with Jelly... If anyone wants to make it better, feel free to patch accordingly.

I'm delaying the release until tomorrow.  Im currently not able to release right now.  Just giving you a heads up.

Currently working on the release.    I would expect there to be no output.  Not even the started message.  Just my 2c.

When you say JENKINS-15 and JENKINS-28 are you referring to the Jenkins issue tracker or the Slack GitHub project issues?  If you're referring to the GitHub project then you should simply do #15 and #28.

To the issue tracker, as information in Jenkins documentation ;-)

Referring your comment above, the check box is Notify Repeated Failures (which is the previous default), not Ignore Repeated Failures. I didn't want to go away from the current naming convention "notifyXXX" by using "doNotNotifyXXX"... Not sure it makes sense... :-)

Understood, I explained the feature for its function.  Perhaps that was a mistake.
The Jenkins documentation states when referencing issues at https://issues.jenkins-ci.org/.  In your case, you're not referencing issues at jenkins-ci.org.  You're referencing GitHub issues.  Please use #[0-9]+ for GitHub issues and JENKINS-[0-9]+ for jenkins-ci.org issues.

My bad. I misunderstood the jenkins bot was closing the issues here automatically...

No worries. If you include fixes #[0-9]+ or closes #[0-9]+ then GitHub will automatically close issues when pull requests are merged.


Implement decoupling queue between REST call to the event service and the REST call to the process engine.

Scenario
 Given task in tasklist
 when user complets task in tasklist
 then complete task event is created in eventservice store
 and the task is no longer in tasklist

 Given active task in event service store
 when a complete task event arrives
 then a rest call "complete" is send to coresponding process engine
 and the task is completed

TODO: Implement Error handling if Engine returns 500 (Task not found ...)
https://github.com/OpenFeign/feign/tree/master/hystrix
But there is no FallbackFactory in our version ...


triangle_wgpu imgui demo segfault on exit

Steps to reproduce:

zig build triangle_wgpu-run
Open imgui demo -> Examples -> Miniapps -> Console
Close with esc or with X window button.

No repo at fc64152b84ceaa9e3f20be9549ffa4f2d2f92175 on windows-x86_64

I think the bug is the destructor is never called upon this static: https://github.com/zig-gamedev/zig-gamedev/blob/fc64152b84ceaa9e3f20be9549ffa4f2d2f92175/libs/zgui/libs/imgui/imgui_demo.cpp#L7430

The destructor is called if console is made global:
``cpp
diff --git a/libs/zgui/libs/imgui/imgui_demo.cpp b/libs/zgui/libs/imgui/imgui_demo.cpp
index 9b4ba871..ca67882d 100644
--- a/libs/zgui/libs/imgui/imgui_demo.cpp
+++ b/libs/zgui/libs/imgui/imgui_demo.cpp
@@ -7425,9 +7425,9 @@ struct ExampleAppConsole
}
};
+static ExampleAppConsole console;
static void ShowExampleAppConsole(bool* p_open)
{

static ExampleAppConsole console;
console.Draw("Example: Console", p_open);
}

I think clang is incorrectly removing the destructor thinking that is an unobservable change.

Ah, is the problem there is an attempt to call the destructor but the allocator is already been deinit?
Seems similar to https://github.com/ocornut/imgui/issues/538

The destructor is called if console is made global:

This looks like the fix to me.

The destructor is called if console is made global:

This looks like the fix to me.

If so can we repo this and fix it upstream?

I think we should consider this "not an issue" since it is a deliberate choice as per https://github.com/ocornut/imgui/issues/538#issuecomment-202407310
We can "fix" this issue by removing the imgui demo window from triangle_wgpu


Initialize random once to ensure different random values

This fixes intermittent failures in TestLongPostings that error out with a message stating that files are being used by other process: http://teamcity.codebetter.com/viewLog.html?buildId=180872&tab=buildResultsDiv&buildTypeId=LuceneNet_Core#testNameId4501500834530776105
The issue is actually that sometimes NUM_DOCS is low enough where all Random() execute with the same seed and result in NextBoolean() returning the same value. As a result, test documents are not initialized as expected, resulting in some test asserts failing afterwards which then results in not all objects being disposed properly and holding open files which test tear down tries to clean up.

This needs to happen on the base class level to leverage randomized testing properly:
https://github.com/apache/lucene-solr/blob/trunk/lucene/core/src/test/org/apache/lucene/index/TestLongPostings.java#L105
https://github.com/apache/lucene-solr/blob/trunk/lucene/test-framework/src/java/org/apache/lucene/util/LuceneTestCase.java#L729
I'm trying to solve this via a ThreadStatic, lets see if it works