using local models instead of openAI?

I am using GPT4All to pull various different LLM images, it can start a local server for API access ( https://docs.gpt4all.io/gpt4all_chat.html ) would it possible to customize to use that API instead , to go truly open source?

Yes, metagpt can do that. But your should modify some code to suit your LLM API.

I would be interested to know what code. I started by making the config use my mini_orca configuration. I started running and ran into this issue and am wondering how much is OpenAI specific and where to change what is. Maybe I am missing some config, but if I am needing code to write, a summary of the files needed to be replaced or rewritten with how to access that path would be great. Here is where I ran into an authentication after initially bypassing it by having my own model.                            (MetaGPT) D:\Github\MetaGPT>python startup.py "Write a cli snake game based on pygame"
Found model file at  d:\\models\\GPT4ALL\orca-mini-3b.ggmlv3.q4_0.bin
llama.cpp: loading model from d:\\models\\GPT4ALL\orca-mini-3b.ggmlv3.q4_0.bin
llama_model_load_internal: format     = ggjt v3 (latest)
llama_model_load_internal: n_vocab    = 32000
llama_model_load_internal: n_ctx      = 2048
llama_model_load_internal: n_embd     = 3200
llama_model_load_internal: n_mult     = 240
llama_model_load_internal: n_head     = 32
llama_model_load_internal: n_layer    = 26
llama_model_load_internal: n_rot      = 100
llama_model_load_internal: ftype      = 2 (mostly Q4_0)
llama_model_load_internal: n_ff       = 8640
llama_model_load_internal: n_parts    = 1
llama_model_load_internal: model size = 3B
llama_model_load_internal: ggml ctx size =    0.06 MB
llama_model_load_internal: mem required  = 2862.72 MB (+  682.00 MB per state)
llama_new_context_with_model: kv self size  =  650.00 MB
2023-08-10 13:55:31.896 | INFO     | metagpt.config:init:46 - Config loading done.
2023-08-10 13:55:35.595 | INFO     | metagpt.software_company:invest:39 - Investment: $3.0.
2023-08-10 13:55:35.599 | INFO     | metagpt.roles.role:_act:167 - Alice(Product Manager): ready to WritePRD
Traceback (most recent call last):
File "D:\Github\MetaGPT\lib\site-packages\tenacity-8.2.2-py3.10.egg\tenacity_asyncio.py", line 50, in call
result = await fn(*args, **kwargs)
File "D:\Github\MetaGPT\metagpt\actions\action.py", line 57, in aask_v1
content = await self.llm.aask(prompt, system_msgs)
File "D:\Github\MetaGPT\metagpt\provider\base_gpt_api.py", line 44, in aask
rsp = await self.acompletion_text(message, stream=True)
File "D:\Github\MetaGPT\lib\site-packages\tenacity-8.2.2-py3.10.egg\tenacity_asyncio.py", line 88, in async_wrapped
return await fn(*args, **kwargs)
File "D:\Github\MetaGPT\lib\site-packages\tenacity-8.2.2-py3.10.egg\tenacity_asyncio.py", line 47, in call
do = self.iter(retry_state=retry_state)
File "D:\Github\MetaGPT\lib\site-packages\tenacity-8.2.2-py3.10.egg\tenacity_init.py", line 314, in iter
return fut.result()
File "C:\Users\bartl.pyenv\pyenv-win\versions\3.10.11\lib\concurrent\futures_base.py", line 451, in result
return self.__get_result()
File "C:\Users\bartl.pyenv\pyenv-win\versions\3.10.11\lib\concurrent\futures_base.py", line 403, in __get_result
raise self._exception
File "D:\Github\MetaGPT\lib\site-packages\tenacity-8.2.2-py3.10.egg\tenacity_asyncio.py", line 50, in call
result = await fn(*args, **kwargs)
File "D:\Github\MetaGPT\metagpt\provider\openai_api.py", line 222, in acompletion_text
return await self._achat_completion_stream(messages)
File "D:\Github\MetaGPT\metagpt\provider\openai_api.py", line 151, in _achat_completion_stream
response = await openai.ChatCompletion.acreate(**self._cons_kwargs(messages), stream=True)
File "D:\Github\MetaGPT\lib\site-packages\openai-0.27.8-py3.10.egg\openai\api_resources\chat_completion.py", line 45, in acreate
return await super().acreate(*args, **kwargs)
File "D:\Github\MetaGPT\lib\site-packages\openai-0.27.8-py3.10.egg\openai\api_resources\abstract\engine_api_resource.py", line 217, in acreate
response, _, api_key = await requestor.arequest(
File "D:\Github\MetaGPT\lib\site-packages\openai-0.27.8-py3.10.egg\openai\api_requestor.py", line 382, in arequest
resp, got_stream = await self._interpret_async_response(result, stream)
File "D:\Github\MetaGPT\lib\site-packages\openai-0.27.8-py3.10.egg\openai\api_requestor.py", line 726, in _interpret_async_response
self._interpret_response_line(
File "D:\Github\MetaGPT\lib\site-packages\openai-0.27.8-py3.10.egg\openai\api_requestor.py", line 763, in _interpret_response_line
raise self.handle_error_response(
openai.error.AuthenticationError: Incorrect API key provided: dummyval. You can find your API key at https://platform.openai.com/account/api-keys.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "D:\Github\MetaGPT\startup.py", line 40, in
fire.Fire(main)
File "D:\Github\MetaGPT\lib\site-packages\fire-0.4.0-py3.10.egg\fire\core.py", line 141, in Fire
component_trace = _Fire(component, args, parsed_flag_args, context, name)
File "D:\Github\MetaGPT\lib\site-packages\fire-0.4.0-py3.10.egg\fire\core.py", line 466, in _Fire
component, remaining_args = _CallAndUpdateTrace(
File "D:\Github\MetaGPT\lib\site-packages\fire-0.4.0-py3.10.egg\fire\core.py", line 681, in _CallAndUpdateTrace
component = fn(*varargs, **kwargs)
File "D:\Github\MetaGPT\startup.py", line 36, in main
asyncio.run(startup(idea, investment, n_round, code_review, run_tests))
File "C:\Users\bartl.pyenv\pyenv-win\versions\3.10.11\lib\asyncio\runners.py", line 44, in run
return loop.run_until_complete(main)
File "C:\Users\bartl.pyenv\pyenv-win\versions\3.10.11\lib\asyncio\base_events.py", line 649, in run_until_complete
return future.result()
File "D:\Github\MetaGPT\startup.py", line 24, in startup
await company.run(n_round=n_round)
File "D:\Github\MetaGPT\metagpt\software_company.py", line 60, in run
await self.environment.run()
File "D:\Github\MetaGPT\metagpt\environment.py", line 67, in run
await asyncio.gather(*futures)
File "D:\Github\MetaGPT\metagpt\roles\role.py", line 240, in run
rsp = await self._react()
File "D:\Github\MetaGPT\metagpt\roles\role.py", line 209, in _react
return await self._act()
File "D:\Github\MetaGPT\metagpt\roles\role.py", line 168, in _act
response = await self._rc.todo.run(self._rc.important_memory)
File "D:\Github\MetaGPT\metagpt\actions\write_prd.py", line 145, in run
prd = await self.aask_v1(prompt, "prd", OUTPUT_MAPPING)
File "D:\Github\MetaGPT\lib\site-packages\tenacity-8.2.2-py3.10.egg\tenacity_asyncio.py", line 88, in async_wrapped
return await fn(*args, **kwargs)
File "D:\Github\MetaGPT\lib\site-packages\tenacity-8.2.2-py3.10.egg\tenacity_asyncio.py", line 47, in call
do = self.iter(retry_state=retry_state)
File "D:\Github\MetaGPT\lib\site-packages\tenacity-8.2.2-py3.10.egg\tenacity_init.py", line 326, in iter
raise retry_exc from fut.exception()
tenacity.RetryError: RetryError[<Future at 0x2168a720f70 state=finished raised AuthenticationError>]  ------------------------------(disclaimer, I am not much of a programmer but Claude and ChatGPT enable me as a meat puppet to to many things)

@geekan @stellaHSR

I started trying to use ChatGPT to use the base class and the configuration to add something in but I think it is beyond our ability. So I will have to wait for someone who is smarter to do it or I will need to be a bit smarter about the architecture to do it. I guess that's the same thing, really :)

openai.error.AuthenticationError: Incorrect API key provided: dummyval. You can find your API key at https://platform.openai.com/account/api-keys.

check your key

@bartanderson I am attempting the same thing.  You'll need to change the server address for the api to your local host:
OPENAI_API_BASE: "http://<IP_ADDRESS>:8000/v1"
OPENAI_API_KEY: "xxxxxxxxxxxxxxxxxxxxxxxxxx"
This can be found in: MetaGPT/config/config.yaml

However, when I run it locally, I get the following error:
> python startup.py "Write a cli snake game based on pygame" --code_review True
2023-08-14 16:24:22.781 | INFO     | metagpt.config:__init__:44 - Config loading done.
2023-08-14 16:24:23.819 | INFO     | metagpt.software_company:invest:39 - Investment: $3.0.
2023-08-14 16:24:23.819 | INFO     | metagpt.roles.role:_act:167 - Alice(Product Manager): ready to WritePRD
You are a Product Manager, named Alice, your goal is Efficiently create a successful product, and the constraint is .
You are a Product Manager, named Alice, your goal is Efficiently create a successful product, and the constraint is .
Traceback (most recent call last):
  File "<redacted>/miniconda3/envs/metagpt/lib/python3.11/site-packages/tenacity/_asyncio.py", line 50, in __call__
    result = await fn(*args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<redacted>/MetaGPT/metagpt/actions/action.py", line 60, in _aask_v1
    parsed_data = OutputParser.parse_data_with_mapping(content, output_data_mapping)
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<redacted>/MetaGPT/metagpt/utils/common.py", line 121, in parse_data_with_mapping
    block_dict = cls.parse_blocks(data)
                 ^^^^^^^^^^^^^^^^^^^^^^
  File "<redacted>/MetaGPT/metagpt/utils/common.py", line 43, in parse_blocks
    block_title, block_content = block.split("\n", 1)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: not enough values to unpack (expected 2, got 1)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "<redacted>/MetaGPT/startup.py", line 40, in <module>
    fire.Fire(main)
  File "<redacted>/miniconda3/envs/metagpt/lib/python3.11/site-packages/fire/core.py", line 141, in Fire
    component_trace = _Fire(component, args, parsed_flag_args, context, name)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<redacted>/miniconda3/envs/metagpt/lib/python3.11/site-packages/fire/core.py", line 466, in _Fire
    component, remaining_args = _CallAndUpdateTrace(
                                ^^^^^^^^^^^^^^^^^^^^
  File "<redacted>/miniconda3/envs/metagpt/lib/python3.11/site-packages/fire/core.py", line 681, in _CallAndUpdateTrace
    component = fn(*varargs, **kwargs)
                ^^^^^^^^^^^^^^^^^^^^^^
  File "<redacted>/MetaGPT/startup.py", line 36, in main
    asyncio.run(startup(idea, investment, n_round, code_review, run_tests))
  File "<redacted>/miniconda3/envs/metagpt/lib/python3.11/asyncio/runners.py", line 190, in run
    return runner.run(main)
           ^^^^^^^^^^^^^^^^
  File "<redacted>/miniconda3/envs/metagpt/lib/python3.11/asyncio/runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<redacted>/miniconda3/envs/metagpt/lib/python3.11/asyncio/base_events.py", line 653, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "<redacted>/MetaGPT/startup.py", line 24, in startup
    await company.run(n_round=n_round)
  File "<redacted>/MetaGPT/metagpt/software_company.py", line 60, in run
    await self.environment.run()
  File "<redacted>/MetaGPT/metagpt/environment.py", line 67, in run
    await asyncio.gather(*futures)
  File "<redacted>/MetaGPT/metagpt/roles/role.py", line 240, in run
    rsp = await self._react()
          ^^^^^^^^^^^^^^^^^^^
  File "<redacted>/MetaGPT/metagpt/roles/role.py", line 209, in _react
    return await self._act()
           ^^^^^^^^^^^^^^^^^
  File "<redacted>/MetaGPT/metagpt/roles/role.py", line 168, in _act
    response = await self._rc.todo.run(self._rc.important_memory)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<redacted>/MetaGPT/metagpt/actions/write_prd.py", line 145, in run
    prd = await self._aask_v1(prompt, "prd", OUTPUT_MAPPING)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<redacted>/miniconda3/envs/metagpt/lib/python3.11/site-packages/tenacity/_asyncio.py", line 88, in async_wrapped
    return await fn(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<redacted>/miniconda3/envs/metagpt/lib/python3.11/site-packages/tenacity/_asyncio.py", line 47, in __call__
    do = self.iter(retry_state=retry_state)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<redacted>/miniconda3/envs/metagpt/lib/python3.11/site-packages/tenacity/__init__.py", line 326, in iter
    raise retry_exc from fut.exception()
tenacity.RetryError: RetryError[<Future at 0x7f11aebbdc50 state=finished raised ValueError>]

I don't intend to use openai, does this have its own local ai that I missed?
On Mon, Aug 14, 2023, 3:31 PM Brian Toner @.***> wrote:

However, when I run it locally, I get the following error:

python startup.py "Write a cli snake game based on pygame" --code_review True
2023-08-14 16:24:22.781 | INFO     | metagpt.config:init:44 - Config loading done.
2023-08-14 16:24:23.819 | INFO     | metagpt.software_company:invest:39 - Investment: $3.0.
2023-08-14 16:24:23.819 | INFO     | metagpt.roles.role:_act:167 - Alice(Product Manager): ready to WritePRD
You are a Product Manager, named Alice, your goal is Efficiently create a successful product, and the constraint is .
You are a Product Manager, named Alice, your goal is Efficiently create a successful product, and the constraint is .
Traceback (most recent call last):
File "/miniconda3/envs/metagpt/lib/python3.11/site-packages/tenacity/_asyncio.py", line 50, in call
result = await fn(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/MetaGPT/metagpt/actions/action.py", line 60, in _aask_v1
parsed_data = OutputParser.parse_data_with_mapping(content, output_data_mapping)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/MetaGPT/metagpt/utils/common.py", line 121, in parse_data_with_mapping
block_dict = cls.parse_blocks(data)
^^^^^^^^^^^^^^^^^^^^^^
File "/MetaGPT/metagpt/utils/common.py", line 43, in parse_blocks
block_title, block_content = block.split("\n", 1)
^^^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: not enough values to unpack (expected 2, got 1)

The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/MetaGPT/startup.py", line 40, in
fire.Fire(main)
File "/miniconda3/envs/metagpt/lib/python3.11/site-packages/fire/core.py", line 141, in Fire
component_trace = _Fire(component, args, parsed_flag_args, context, name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/miniconda3/envs/metagpt/lib/python3.11/site-packages/fire/core.py", line 466, in _Fire
component, remaining_args = _CallAndUpdateTrace(
^^^^^^^^^^^^^^^^^^^^
File "/miniconda3/envs/metagpt/lib/python3.11/site-packages/fire/core.py", line 681, in _CallAndUpdateTrace
component = fn(*varargs, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^
File "/MetaGPT/startup.py", line 36, in main
asyncio.run(startup(idea, investment, n_round, code_review, run_tests))
File "/miniconda3/envs/metagpt/lib/python3.11/asyncio/runners.py", line 190, in run
return runner.run(main)
^^^^^^^^^^^^^^^^
File "/miniconda3/envs/metagpt/lib/python3.11/asyncio/runners.py", line 118, in run
return self._loop.run_until_complete(task)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/miniconda3/envs/metagpt/lib/python3.11/asyncio/base_events.py", line 653, in run_until_complete
return future.result()
^^^^^^^^^^^^^^^
File "/MetaGPT/startup.py", line 24, in startup
await company.run(n_round=n_round)
File "/MetaGPT/metagpt/software_company.py", line 60, in run
await self.environment.run()
File "/MetaGPT/metagpt/environment.py", line 67, in run
await asyncio.gather(*futures)
File "/MetaGPT/metagpt/roles/role.py", line 240, in run
rsp = await self._react()
^^^^^^^^^^^^^^^^^^^
File "/MetaGPT/metagpt/roles/role.py", line 209, in _react
return await self._act()
^^^^^^^^^^^^^^^^^
File "/MetaGPT/metagpt/roles/role.py", line 168, in _act
response = await self._rc.todo.run(self._rc.important_memory)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/MetaGPT/metagpt/actions/write_prd.py", line 145, in run
prd = await self._aask_v1(prompt, "prd", OUTPUT_MAPPING)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/miniconda3/envs/metagpt/lib/python3.11/site-packages/tenacity/_asyncio.py", line 88, in async_wrapped
return await fn(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/miniconda3/envs/metagpt/lib/python3.11/site-packages/tenacity/_asyncio.py", line 47, in call
do = self.iter(retry_state=retry_state)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/miniconda3/envs/metagpt/lib/python3.11/site-packages/tenacity/init.py", line 326, in iter
raise retry_exc from fut.exception()
tenacity.RetryError: RetryError[<Future at 0x7f11aebbdc50 state=finished raised ValueError>]
—
Reply to this email directly, view it on GitHub
https://github.com/geekan/MetaGPT/issues/180#issuecomment-1678017048,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMXAKGKXC6KR7QJWZOT3FTXVKDK3ANCNFSM6AAAAAA3KIYTSI
.
You are receiving this because you were mentioned.Message ID:
@.***>

@bartanderson
You'll need to run your own local, OpenAI-like server running the llm of your choice.  For instance, I am testing on llama-cpp-python's sever mode.  In my case, my server is running on port 8000, on my localhost.

Yup, I have my eye on localai, which has a build problem currently I am
trying to get help with and simpleai which may be too simple yet but who
knows. So many projects to learn about and try. Did you do much other than
expose it? The instructions I saw didn't say anything about how to
interface to other than openai. I'd be interested in what you did.
On Tue, Aug 15, 2023 at 10:45 AM Brian Toner @.***>
wrote:

@bartanderson https://github.com/bartanderson
You'll need to run your own local, OpenAI-like server running the llm of
your choice. For instance, I am testing on llama-cpp-python's sever mode.
In my case, my server is running on port 8000, on my localhost.
—
Reply to this email directly, view it on GitHub
https://github.com/geekan/MetaGPT/issues/180#issuecomment-1679168119,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMXAKEVUASJYZ4IMIARLDTXVOKQLANCNFSM6AAAAAA3KIYTSI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hello, @dasam  joining weeks late in the wagon, could you please help me understand if any locally running models are providing desired results?
As I see, @bartanderson & @brian-toner have been  discussing on the same note. Bests.

@bartanderson
I can hit my OpenAI-like server fine.  I've been debugging MetaGPT to try and sort out where my issue is coming from.  But unfortunately I don't have a lot of time. I'll probably have more time over the weekend to see if I can figure it out.

Here is an update on my progress. I can validate that MetaGPT does work on a local server. It seems the "stop" field in the request body can take on a null value. The OpenAI like api I am using (llama-cpp) doesn't handle nulls properly in that field.  Upon fixing it on the server side, Metagpt seems to work.  Though I did encounter another error:
2023-08-18 20:57:35.198 | INFO     | metagpt.provider.openai_api:update_cost:81 - Total running cost: $0.073 | Max budget: $3.000 | Current cost: $0.047, prompt_tokens: 845, completion_tokens: 361
Traceback (most recent call last):
  File "/<redacted>miniconda3/envs/metagpt/lib/python3.11/site-packages/tenacity/_asyncio.py", line 53, in __call__
    result = await fn(*args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/<redacted>/MetaGPT/metagpt/actions/action.py", line 62, in _aask_v1
    instruct_content = output_class(**parsed_data)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "pydantic/main.py", line 341, in pydantic.main.BaseModel.__init__
pydantic.error_wrappers.ValidationError: 8 validation errors for prd
Original Requirements
  field required (type=value_error.missing)
Product Goals
  field required (type=value_error.missing)
User Stories
  field required (type=value_error.missing)
Competitive Quadrant Chart
  field required (type=value_error.missing)
Requirement Analysis
  field required (type=value_error.missing)
Requirement Pool
  field required (type=value_error.missing)
UI Design draft
  field required (type=value_error.missing)
Anything UNCLEAR
  field required (type=value_error.missing)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/<redacted>/MetaGPT/startup.py", line 40, in <module>
    fire.Fire(main)
  File "/<redacted>miniconda3/envs/metagpt/lib/python3.11/site-packages/fire/core.py", line 141, in Fire
    component_trace = _Fire(component, args, parsed_flag_args, context, name)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/<redacted>miniconda3/envs/metagpt/lib/python3.11/site-packages/fire/core.py", line 466, in _Fire
    component, remaining_args = _CallAndUpdateTrace(
                                ^^^^^^^^^^^^^^^^^^^^
  File "/<redacted>miniconda3/envs/metagpt/lib/python3.11/site-packages/fire/core.py", line 681, in _CallAndUpdateTrace
    component = fn(*varargs, **kwargs)
                ^^^^^^^^^^^^^^^^^^^^^^
  File "/<redacted>/MetaGPT/startup.py", line 36, in main
    asyncio.run(startup(idea, investment, n_round, code_review, run_tests))
  File "/<redacted>miniconda3/envs/metagpt/lib/python3.11/asyncio/runners.py", line 190, in run
    return runner.run(main)
           ^^^^^^^^^^^^^^^^
  File "/<redacted>miniconda3/envs/metagpt/lib/python3.11/asyncio/runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/<redacted>miniconda3/envs/metagpt/lib/python3.11/asyncio/base_events.py", line 653, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/<redacted>/MetaGPT/startup.py", line 24, in startup
    await company.run(n_round=n_round)
  File "/<redacted>/MetaGPT/metagpt/software_company.py", line 60, in run
    await self.environment.run()
  File "/<redacted>/MetaGPT/metagpt/environment.py", line 67, in run
    await asyncio.gather(*futures)
  File "/<redacted>/MetaGPT/metagpt/roles/role.py", line 240, in run
    rsp = await self._react()
          ^^^^^^^^^^^^^^^^^^^
  File "/<redacted>/MetaGPT/metagpt/roles/role.py", line 209, in _react
    return await self._act()
           ^^^^^^^^^^^^^^^^^
  File "/<redacted>/MetaGPT/metagpt/roles/role.py", line 168, in _act
    response = await self._rc.todo.run(self._rc.important_memory)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/<redacted>/MetaGPT/metagpt/actions/write_prd.py", line 145, in run
    prd = await self._aask_v1(prompt, "prd", OUTPUT_MAPPING)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/<redacted>miniconda3/envs/metagpt/lib/python3.11/site-packages/tenacity/_asyncio.py", line 93, in async_wrapped
    return await fn(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/<redacted>miniconda3/envs/metagpt/lib/python3.11/site-packages/tenacity/_asyncio.py", line 47, in __call__
    do = self.iter(retry_state=retry_state)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/<redacted>miniconda3/envs/metagpt/lib/python3.11/site-packages/tenacity/__init__.py", line 326, in iter
    raise retry_exc from fut.exception()
tenacity.RetryError: RetryError[<Future at 0x7fbf25361510 state=finished raised ValidationError>]

Have you tried using [llama2-wrapper]?
It runs an OpenAI like API server locally.(https://pypi.org/project/llama2-wrapper/)

Have you tried using llama2-wrapper
It’d let you use an OpenAI compatible API for your models.

Here is an update on my progress. I can validate that MetaGPT does work on a local server. It seems the "stop" field in the request body can take on a null value. The OpenAI like api I am using (llama-cpp) doesn't handle nulls properly in that field. Upon fixing it on the server side, Metagpt seems to work. Though I did encounter another error:
2023-08-18 20:57:35.198 | INFO     | metagpt.provider.openai_api:update_cost:81 - Total running cost: $0.073 | Max budget: $3.000 | Current cost: $0.047, prompt_tokens: 845, completion_tokens: 361
Traceback (most recent call last):
  File "/<redacted>miniconda3/envs/metagpt/lib/python3.11/site-packages/tenacity/_asyncio.py", line 53, in __call__
    result = await fn(*args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/<redacted>/MetaGPT/metagpt/actions/action.py", line 62, in _aask_v1
    instruct_content = output_class(**parsed_data)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "pydantic/main.py", line 341, in pydantic.main.BaseModel.__init__
pydantic.error_wrappers.ValidationError: 8 validation errors for prd
Original Requirements
  field required (type=value_error.missing)
Product Goals
  field required (type=value_error.missing)
User Stories
  field required (type=value_error.missing)
Competitive Quadrant Chart
  field required (type=value_error.missing)
Requirement Analysis
  field required (type=value_error.missing)
Requirement Pool
  field required (type=value_error.missing)
UI Design draft
  field required (type=value_error.missing)
Anything UNCLEAR
  field required (type=value_error.missing)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/<redacted>/MetaGPT/startup.py", line 40, in <module>
    fire.Fire(main)
  File "/<redacted>miniconda3/envs/metagpt/lib/python3.11/site-packages/fire/core.py", line 141, in Fire
    component_trace = _Fire(component, args, parsed_flag_args, context, name)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/<redacted>miniconda3/envs/metagpt/lib/python3.11/site-packages/fire/core.py", line 466, in _Fire
    component, remaining_args = _CallAndUpdateTrace(
                                ^^^^^^^^^^^^^^^^^^^^
  File "/<redacted>miniconda3/envs/metagpt/lib/python3.11/site-packages/fire/core.py", line 681, in _CallAndUpdateTrace
    component = fn(*varargs, **kwargs)
                ^^^^^^^^^^^^^^^^^^^^^^
  File "/<redacted>/MetaGPT/startup.py", line 36, in main
    asyncio.run(startup(idea, investment, n_round, code_review, run_tests))
  File "/<redacted>miniconda3/envs/metagpt/lib/python3.11/asyncio/runners.py", line 190, in run
    return runner.run(main)
           ^^^^^^^^^^^^^^^^
  File "/<redacted>miniconda3/envs/metagpt/lib/python3.11/asyncio/runners.py", line 118, in run
    return self._loop.run_until_complete(task)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/<redacted>miniconda3/envs/metagpt/lib/python3.11/asyncio/base_events.py", line 653, in run_until_complete
    return future.result()
           ^^^^^^^^^^^^^^^
  File "/<redacted>/MetaGPT/startup.py", line 24, in startup
    await company.run(n_round=n_round)
  File "/<redacted>/MetaGPT/metagpt/software_company.py", line 60, in run
    await self.environment.run()
  File "/<redacted>/MetaGPT/metagpt/environment.py", line 67, in run
    await asyncio.gather(*futures)
  File "/<redacted>/MetaGPT/metagpt/roles/role.py", line 240, in run
    rsp = await self._react()
          ^^^^^^^^^^^^^^^^^^^
  File "/<redacted>/MetaGPT/metagpt/roles/role.py", line 209, in _react
    return await self._act()
           ^^^^^^^^^^^^^^^^^
  File "/<redacted>/MetaGPT/metagpt/roles/role.py", line 168, in _act
    response = await self._rc.todo.run(self._rc.important_memory)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/<redacted>/MetaGPT/metagpt/actions/write_prd.py", line 145, in run
    prd = await self._aask_v1(prompt, "prd", OUTPUT_MAPPING)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/<redacted>miniconda3/envs/metagpt/lib/python3.11/site-packages/tenacity/_asyncio.py", line 93, in async_wrapped
    return await fn(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/<redacted>miniconda3/envs/metagpt/lib/python3.11/site-packages/tenacity/_asyncio.py", line 47, in __call__
    do = self.iter(retry_state=retry_state)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/<redacted>miniconda3/envs/metagpt/lib/python3.11/site-packages/tenacity/__init__.py", line 326, in iter
    raise retry_exc from fut.exception()
tenacity.RetryError: RetryError[<Future at 0x7fbf25361510 state=finished raised ValidationError>]

This can be worked around by increasing the number of stop attempts in action.py (around line 49) changing
    @retry(stop=stop_after_attempt(2), wait=wait_fixed(1))

to something like:
    @retry(stop=stop_after_attempt(99), wait=wait_fixed(1))

Do you have that fix in llamacpp? Or could you make a PR there?
Would run llama2-wrapper (and it does work) but it doesn't support cuBLAS so it ends up running the model on the CPU instead of the GPU

@TinaTiel unfortunately the code I used wasn't merged to main. The code I worked from was:
https://raw.githubusercontent.com/ggerganov/llama.cpp/d8a8d0e536cfdaca0135f22d43fda80dc5e47cd8/examples/server/api_like_OAI.py
I found this linked on stack exchange, I think, explaining that there was a bug in the open-ai-like api, so I didn't work off of the main branch.  I was hoping that it would get merged and then I would push up my changes, but it doesn't seem like that is going to happen.
From this obscure branch, I changed the line:
  if(is_present(body, "stop")): postData["stop"] += body["stop"]

to
  if(is_present(body, "stop") and body["stop"] is not None ): postData["stop"] += body["stop"]

@bartanderson You'll need to run your own local, OpenAI-like server running the llm of your choice. For instance, I am testing on llama-cpp-python's sever mode. In my case, my server is running on port 8000, on my localhost.

Are still using the LLAMA on meta GPT without any problem?
What did you just do? only change the link and API key? isn;t there any option to access LLAMA from remote API?

I have local code llama running via FastChat OpenAI API and would love to use MetaGPT with it.
Are there any other changes other than config and stop attempts that need to be made?

Due to the lack of updates or replies by the user for a long time, we will close it. Please reopen it if necessary.


update header Accept

Got 403 Forbidden with "X-APP-VERSION: 1.10.0" again:
ComfortCloud-App has in the header ("Accept", "application/json; charset=utf-8") -> no token creation was possible.

mmm... are you kidding me? :P

nope sry - i had several errors the last few hours - seems fine now again.


"build-web" places resulting script in root directory

The current "build-web" script places the GridEngine.min.js file into the root project directory, not dist/. Because of this, you can't import the non-ESM build easily into any other projects.
Easy fix; just add dist/ to the --outfile argument for "build-web"

Hey @splashsky
This is intentional. The reason for it not being in dist is that it is not supposed to be exported as an npm module. The non-esm version is intended for manual download only. Putting it in the dist directory would make the npm package twice as large.
Unfortunately I could not find a way to exclude single files from being published to npm.

Because of this, you can't import the non-ESM build easily into any other projects.

Could you be more specific about this case? I think I don't understand the issue.

In my use case, I was trying to make a script that would contain accessible instances of both Phaser and Grid Engine. However, they wouldn't be in the global namespace as ESM modules so that was out of the question. I then set up a simple script to copy the minified scripts from node_modules, which worked for Phaser but not for Grid Engine, because Grid Engine's minified universal script wasn't there.
While I understand wanting to save the Mb, would it be alright for the sake of convenience to simply let the universal script exist there? Phaser does it, and those versions are each ~3Mb. Realistically, letting another +/- 48Kb  be downloaded seems trivial at worst, convenient at best.

I merged it. It will be part of the next release.


en: add document for optimistic mode sharding merge

What is changed, added or deleted? (Required)
add a document for optimistic mode sharding merge
This PR aligns a part of https://github.com/pingcap/docs-dm/pull/155. The rest part will be aligned by @ireneontheway.

Which DM version(s) do your changes apply to? (Required)

[x] master (the latest development version, including v2.0 changes for now)
[ ] v1.0 (TiDB DM 1.0 versions)

What is the related PR or file link(s)?

This PR is translated from: https://github.com/pingcap/docs-dm/pull/155
Other reference link(s):

Do your changes match any of the following descriptions?

[ ] Delete files
[ ] Change aliases
[ ] Have version specific changes
[ ] Might cause conflicts

@ran-huang All comments are addressed, PTAL again, thanks!

See the link.  I‘m confused that whether “同步" in PR155 means "（增量）复制" or "（全量+增量模式）迁移"? Shall we replace replication into migration? @csuzhangxc @TomShawn @ran-huang

See the link. I‘m confused that whether “同步" in PR155 means "（增量）复制" or "（全量+增量模式）迁移"? Shall we replace "replication" into "migration"? @csuzhangxc @TomShawn @ran-huang

IMO, sharding DDL (https://github.com/pingcap/docs-dm/pull/155) describes an incremental scenario, so we should use replication.


Segmentation fault in examples/charm++/arraysection and cleanup

Original issue: https://charm.cs.illinois.edu/redmine/issues/1978

Segmentation fault when the example in
charm++/arraysection is run.
On a different system setup it runs into an error
contribute: SectionID is not initialized
Also, the example needs to be cleaned up to reflect what is quoted in the manual.
2D section array example needs to be added.

Original date: 2018-09-12 02:25:18

Some things to clean up:

It doesn't compile on my Mac using GCC:

check.C:35:37: error: use of parameter outside function body before ']' token
  void done(int q, int output[q]){

That line should be:
  void done(int q, int output[]){

The CkArgMsg* passed to the Mainchare's constructor is not deleted anywhere.

Section creation should use the std::vector-based API rather than the old CkVec one.

There are several lines of commented-out code, which should just be removed.

The recvMsg() currently calls 'CkFreeMsg(msg);', but I think it's cleaner / more consistent to do 'delete msg;'

Original date: 2018-09-12 13:20:43

Cleanup here: ~~https://charm.cs.illinois.edu/gerrit/#/c/charm/+/4566/~~ https://github.com/UIUC-PPL/charm/commit/e1f98b3c31a50844411612f9b0dbd0f6c46839e5
Still need a 2D example...

Original date: 2018-09-12 13:26:51

The example builds and runs correctly now for me. Can you try it, and then add a 2D example?

Original date: 2018-09-12 15:25:13

Yes, it works for me. Will add a 2D array example.

Original date: 2018-09-13 00:51:43

2D section example: ~~https://charm.cs.illinois.edu/gerrit/#/c/charm/+/4568/~~ https://github.com/UIUC-PPL/charm/commit/9212ce48e779fc3360e491b224cae977df4dd0eb


cpu and memory  resource parameters  doesn't work correctly

Description of problem
start contanier use kata-runtime,  resource parameters  doesn't work correctly:

use param: --cpus 4, but it shows 5 cpu use “top” command （more 1 core cpu than set）
use param: --memory 2G, but  it shows 4G memory use “free” command（more 2G memory than set）

container run command:
docker run -d --net vlan1008 --ip <IP_ADDRESS> --cpus 4 --memory 2g  --storage-opt size=200G registry.lwsite.net:5000/c7-systemd-kata

Container internal command
[root@b7bf07e84a26 /]# ls -d /sys/devices/system/cpu/cpu[0-9]*
/sys/devices/system/cpu/cpu0  /sys/devices/system/cpu/cpu3
/sys/devices/system/cpu/cpu1  /sys/devices/system/cpu/cpu4
/sys/devices/system/cpu/cpu2

[root@b7bf07e84a26 /]# free -m
              total        used        free      shared  buff/cache   available
Mem:           4034          70        3930           8          33        3898
Swap:             0           0           0

We provide default 1U2G for a sandbox. See https://github.com/kata-containers/runtime/issues/933. Discussion is welcome.

@caoruidong @devimc - I would love to have the algorithms and different scenarios (single containers, pods etc.) documented in https://github.com/kata-containers/documentation/wiki/UserGuide#memory
;-)

@grahamwhaley Agreed. Seems it already has something related.

@coos you see 5 cpus, but your container can use only 4, the extra cpu is used by kata-agent, systemd, and in the case of k8s, containers without constraints.
see https://github.com/kata-containers/documentation/blob/master/constraints/cpu.md#do-not-waste-resources.

We use kata-runtime to solve the problem of poor runc isolation (users can see all the CPU, memory information of the host), we use kata-runtime to create virtual machines, but this problem will be given to the virtual machine Users are bothered, they don't know how much real resources their virtual machines have. So this is a very serious flaw.   (from google translate)

I think the view of cpu/memory has no difference comparing to what's in the docker.
the real problem the kata runtime did not reflect user setting at the cgroups level, see my issue here:https://github.com/kata-containers/runtime/issues/1079


Rename 'pyiree' to 'iree'

Renames all non-BUILD references to pyiree (BUILD files are changed in an internal patch). Simplifies the imports in some places to be more consistent. Also deletes some old test files that use the old API and enables the tests for iree.tf.support. (These tests are enabled in a somewhat hacky way to get around the build system symlinking them into the python package, but we'll delete that directory in the near future anyway).
The individual commits are chunked into parts that should be easier to review on their own.

The C++ includes might be a bit confusing now. I'm surprised that they work with the name 'conflict', but 🤷♀ might be good to use python/iree or bindings/python/iree in the future, but I have no clue how to do that.

The C++ includes might be a bit confusing now. I'm surprised that they work with the name 'conflict', but  might be good to use python/iree or bindings/python/iree in the future, but I have no clue how to do that.

They look in every directory on the include path in order, so this will continue to work as long as we don't have any files that have the same path relative to both. Then if someone tries to include that they would potentially get the wrong file. Fun! So I think we should probably remove bindings/python from the include path. I'm not exactly sure where it's set though... I think the IREE repo root should still be on the include path though, so you should be able to just prefix all these with bindings/python now and it will work

Ah, it's relative: https://github.com/google/iree/blob/9f0148fa15692bd16d9193fa3fc94f114114cad9/bindings/python/pyiree/rt/CMakeLists.txt#L34-L35
@stellaraccident can we just kill that and write out the full include paths?

The C++ includes might be a bit confusing now. I'm surprised that they work with the name 'conflict', but  might be good to use python/iree or bindings/python/iree in the future, but I have no clue how to do that.

They look in every directory on the include path in order, so this will continue to work as long as we don't have any files that have the same path relative to both. Then if someone tries to include that they would potentially get the wrong file. Fun! So I think we should probably remove bindings/python from the include path. I'm not exactly sure where it's set though... I think the IREE repo root should still be on the include path though, so you should be able to just prefix all these with bindings/python now and it will work

cool, testing locally.


Add draft scientific metadata to projects & test cases record pages

This is related to #111 , that issue is regarding adding the relevant metadata to the index (search pages). This issue is for adding the draft scientific metadata to the individual project or test case page

Scientific metadata for projects and test cases may change in the future but what's currently been agreed has been implemented


"You are using the runtime-only" Warning on version 2.2.0

Version
2.2.0
Vue.js version
2.4.4
What is exptected?
To not get this warning, as it was in version 2.1.3
What is actually happening?
I am getting a warning:
[Vue warn]: You are using the runtime-only build of Vue where the template compiler is not available. Either pre-compile the templates into render functions, or use the compiler-included build.
found in
--->

How to repreduce this problem?
Create a version using:
vue init webpack my-project

with runtime-only configuration.

That error is unrelated to this component (you will see the same warning even with v2.1.3 if you don't change anything else). Here.

@syn-zeta I am aware of this vue behavior and that's not the case.
I verified multiple times, on versoin 2.2.0 I am getting the warning, on version 2.1.3 I am not - nothing else changed.

I am actually pretty sure it's from commit https://github.com/PeachScript/vue-infinite-loading/commit/6168c31961e0c0d744b6ebdcaf0e37b40da048b3.

My bad for the wrong assumption. Moving out the spinners to its own component in a .vue file should fix this issue (and also reduce the bloat in the main component).

My mind is the spinners just need a template, so use the local registration may be better, is this problem caused by the local registration of component?

The warning is happening on usage, not on registration. I am registering infinite-loader just once, globally, in my main.js:
import VueVirtualScroller from 'vue-virtual-scroller/dist/vue-virtual-scroller';
Vue.use(VueVirtualScroller);

And then, each time I am using a component with  I am getting the warning.

#87

@asafyish Hey. I have the same problem. Have you found a solution?

@Jussiadev @asafyish you can use Runtime + Compiler build of Vue.js to solve this temporarily, and could you tell me the reason that you want to the Runtime-only build of Vue.js?

@PeachScript I was mistaken. I am registering vue-infinite-loading in a local component, not global and still getting the warning.
@Jussiadev No solution so far. The right solution is probably a fix in the library itself.

@PeachScript why this happens even I use your base example

@asafyish @Jussiadev perhaps I did not make it clear.
This component use the local registration component as the spinners, and the local registration component was not be pre-compiled when this component be released, but your project use the Runtime-only build version of Vue.js, it does not include the template compiler, the warning will be thrown when the Vue.js try to render a uncompiled template.
So there has a temporary solution to solve it, just change your Vue.js version from Runtime-only to Runtime + Compiler, simply to do it in your webpack configurations:
...
resolve: {
  alias: {
    'vue$': 'vue/dist/vue.esm.js'
  }
}
...

@PeachScript Yeah that's a great temporary solution, but long-term, I think it's better not to mandate including the compiler in addition to the runtime.

@asafyish of course! I will replace all spinners templates with the compiled templates in the next version.

Hi @asafyish @Jussiadev , the new version v2.2.1 has been released, includes this fix, you can try it now.

@PeachScript Thank you so much.
Sorry, that is off topic, but how to hide the spinner

@Jussiadev it does not matter, they are same problem.
You can create a empty element to hide the spinner through slot feature.

Can verify that it's working correctly in 2.2.1.

@PeachScript Does not help
<infinite-loading @infinite="infiniteHandler" spinner="circle">

            </infinite-loading>

Do you mean
<infinite-loading @infinite="infiniteHandler" spinner="circle">

  </infinite-loading>

@asafyish Thank you. Now it works


Supriyo

I have created the following checks as part of the project. This pull request is for your review and merge. Below is the list of the checks that I have implemented:
NetworkFirewall::MultiAZEnabled
RDS::InstanceStorageEncrypted
RDS::InstanceIntegrationCloudWatchLoggingEnabled
RDS::InstanceMinorVersionUpgradeEnabled
Route53::DomainsPrivacyProtectionEnabled
S3::BucketDefaultEncryption
S3::ObjectVersioning
S3::BucketSecureTransportPolicy
S3::BucketACLProhibited
S3::BucketNoMFADelete
SecretsManager::AutomaticRotationEnabled
SecurityHub::Enabled
SNS::TopicKMSEncryptionAtRestEnabled
SSM::DocumentSecretsPresent
SSM::ManagedCompliantPatching
SSM::PatchManagerEnabled
SSM::EC2InstanceManagedBySSM
SSM::EC2InstanceManagedBySSM
VPC::FlowLogsEnabled
VPC::FlowLogsEnabled
VPC::DefaultSecurityGroupClosed
VPC::EndpointServicesAllowedPrincipalsTrustBoundaries
VPC::SecurityGroupPortRestrictionCheck
VPC::ServiceVPCEndpointEnabled
VPC::FlowLogsEnabled
WellArchitectedTool::WorkloadNoHighOrMediumRisks
CloudFront::WAFProtectionEnabled
CloudTrail::Enabled
CloudTrail::S3BucketAccessLoggingEnabled
CloudTrail::CloudWatchLoggingEnabled
CloudTrail::MultiRegionEnabled
CloudWatch::LogMetricFilterRootUsage
CloudWatch::LogMetricFilterSecurityGroupChanges
CloudWatch::LogMetricFilterUnauthorizedAPICalls
CloudWatch::LogMetricFilterPolicyChanges
CloudWatch::LogMetricFilterVPCAlarmConfigured
CloudWatch::LogMetricFilterAuthenticationFailures
I have added Regular Expression for some cloudwatch checks for proper validation. will remove it if not needed

@supriyo-bhakat-comprinno - Kindly update your branch i.e. supriyo with the main branch. Ping me if you need help.

@supriyo-bhakat-comprinno - Kindly remove/comment all print statements from this PR.

@supriyo-bhakat-comprinno - Kindly remove/comment all print statements from this PR.

Sure .Noted

@supriyo-bhakat-comprinno - Kindly update your branch i.e. supriyo with the main branch. Ping me if you need help.

Sure. will do that


[type:feature] add github flow to publish docker image to ghcr.io

This PR is intended to build docker image for every PR and publish it to ghrc.io.
it is helpful for building CI in sub-repos, like shenyu-nginx.

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #3496 (a4fe5a4) into master (f53e811) will decrease coverage by 0.42%.
The diff coverage is n/a.

:exclamation: Current head a4fe5a4 differs from pull request most recent head 964d65f. Consider uploading reports for the commit 964d65f to get more accurate results

@@             Coverage Diff              @@
##             master    #3496      +/-   ##
============================================
- Coverage     62.94%   62.52%   -0.43%
+ Complexity     5564     5522      -42
============================================
  Files           840      840
  Lines         23256    23256
  Branches       2109     2109
============================================
- Hits          14638    14540      -98
- Misses         7271     7362      +91
- Partials       1347     1354       +7

Impacted Files
Coverage Δ

...plugin/logging/rocketmq/LoggingRocketMQPlugin.java
22.72% <0.00%> (-72.73%)
:arrow_down:

...ache/shenyu/plugin/grpc/cache/GrpcClientCache.java
75.00% <0.00%> (-25.00%)
:arrow_down:

...controller/ShenyuClientHttpRegistryController.java
77.77% <0.00%> (-22.23%)
:arrow_down:

...ogging/rocketmq/body/LoggingServerHttpRequest.java
0.00% <0.00%> (-20.00%)
:arrow_down:

...yu/sync/data/http/refresh/AbstractDataRefresh.java
70.00% <0.00%> (-13.34%)
:arrow_down:

...henyu/plugin/grpc/resolver/ShenyuNameResolver.java
59.57% <0.00%> (-12.77%)
:arrow_down:

...ruptor/RegisterClientServerDisruptorPublisher.java
52.94% <0.00%> (-11.77%)
:arrow_down:

.../plugin/grpc/loadbalance/AbstractLoadBalancer.java
70.65% <0.00%> (-8.70%)
:arrow_down:

.../apache/shenyu/admin/model/dto/BatchCommonDTO.java
50.00% <0.00%> (-7.15%)
:arrow_down:

...apache/shenyu/admin/model/dto/AuthPathWarpDTO.java
57.14% <0.00%> (-7.15%)
:arrow_down:

... and 29 more

Continue to review full report at Codecov.

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


You already added the platform "debian-openssl-1.1.x" to the "generator" block in the "schema.prisma" file as described in https://pris.ly/d/client-generator, but something went wrong.

I'm getting an error on a Docker node:slim container:
{
  "errors": [
    {
      "message": "\nInvalid `prisma.user.findUnique()` invocation:\n\n\nQuery engine library for current platform \"debian-openssl-1.1.x\" could not be found.\nYou incorrectly pinned it to debian-openssl-1.1.x\n\nThis probably happens, because you built Prisma Client on a different platform.\n(Prisma Client looked in \"/usr/src/app/generated/prisma-client/runtime/libquery_engine-debian-openssl-1.1.x.so.node\")\n\nSearched Locations:\n\n  /usr/src/app/.prisma/client\n  /usr/src/app/src/generated/prisma-client\n  /usr/src/app/generated/prisma-client\n  /usr/src/app/generated/prisma-client\n  /usr/src/app/prisma\n  /tmp/prisma-engines\n  /usr/src/app/generated/prisma-client\n\nYou already added the platform \"debian-openssl-1.1.x\" to the \"generator\" block\nin the \"schema.prisma\" file as described in https://pris.ly/d/client-generator,\nbut something went wrong. That's suboptimal.\n\nPlease create an issue at https://github.com/prisma/prisma/issues/new",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "posts"
      ],
      "extensions": {
        "code": "INTERNAL_SERVER_ERROR",
        "exception": {
          "clientVersion": "4.4.0"
        }
      }
    }
  ],
  "data": {
    ...
  }
}

My schema:
generator client {
    provider      = "prisma-client-js"
    output        = "../generated/prisma-client"
    binaryTargets = ["native"]
}

generator pothos {
    provider      = "prisma-pothos-types"
    output        = "../generated/pothos-types.ts"
    binaryTargets = ["native"] //, "debian-openssl-1.1.x"]
}

datasource db {
    provider = "postgresql"
    url      = env("DATABASE_URL")
}

model User {
    id        Int      @id @default(autoincrement())
    createdAt DateTime @default(now())
    updatedAt DateTime @updatedAt
    username  String   @unique
    email     String   @unique
    password  String
    posts     Post[]
}

model Post {
    id        Int      @id @default(autoincrement())
    createdAt DateTime @default(now())
    updatedAt DateTime @updatedAt
    title     String
    content   String?
    author    User     @relation(fields: [authorId], references: [id])
    authorId  Int
    points    Int      @default(0)
}

I had been gotten the same issue for long time ago
could you try to change node:slim to node:16?
This is my prisma config
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["interactiveTransactions"]
  binaryTargets   = ["native", "linux-musl"]
}

my full Docker file. please skip prisma generate because I have 3 databases instances 😄
FROM node:16
WORKDIR /app

COPY ./dist/apps/auth-backend .
COPY prisma ./prisma/
COPY .env .

EXPOSE 3001

RUN apt-get update
RUN apt-get install -y openssl
RUN npm install -g pnpm

RUN pnpm install
RUN pnpm install pino-pretty

RUN npx prisma generate --schema prisma/primary/schema.prisma
RUN npx prisma generate --schema prisma/job/schema.prisma
RUN npx prisma generate --schema prisma/internal/schema.prisma

CMD node ./main.js

What fixed it for me was using a single build container for Docker rather than a multi-step builds. I'm not sure why exactly it helped but it might have been something to do with how Prisma detects differences between builds.

Maybe related to base os binary is different when you build with multiple step buils.

Hey @satvikpendem would you able to share the exact steps for us to reproduce this? Only if you have time, we'd appreciate a reproduction. That would be very helpful. Thanks @annibuliful for the extra information!

I'm not sure exactly what caused the issue in the first place so I'm not sure how to reproduce. What I do know is that I was using a multistep Docker build.

I have a src folder inside which I have the prisma and generated folders. This is because I wanted to create a fully contained dist folder for production.
I run prisma generate which generates a new generated folder.
In src I am using swc to compile my TypeScript files into JS into the dist folder.
swc doesn't copy non-TS files so I cp src/prisma src/generated dist.
When I try to run node dist/index.js Prisma complains as above.

I believe what happened was Prisma somehow knows it was copied to dist and throws an error.

Thanks for the detail. Have you also copied the engine file near your new bundle?

Thanks. So I guess this did not only happen in docker, but also in your dev environment?
I think I can see why (in the code) why the engine would not be found in such a case.

Hm I am actually generating it in a custom location already:
generator client {
    provider      = "prisma-client-js"
    output        = "../generated/prisma-client" // this becomes src/generated/prisma-client
    binaryTargets = ["native"]
}

And yes it happens in my dev env as well as Docker, however it seems to be fixed now that I have copied over the query engine file to dist.

Hey, we wanted to give you an update about this. We have around 10 issues that we have identified to be in the "engine not found" category. Looking at these, we learned that there are four main categories responsible for these errors:

Your client was generated with native (default) on one platform, but used on a different platform at runtime.
You pinned binaryTargets incorrectly, and the correct engine was therefore not included at runtime.
A bundler/framework changed the Prisma Client but did not copy the necessary engine for the runtime.
Deployment/tooling did not copy the engine correctly so the correct engine was not included at runtime.

These cases were previously not detected. On top of that, the error messages were confusing and were neither helpful for you or us. With that, it is likely that many of the cases above overlapped each other. So while we cannot fix a missing engine, we can detect how and why it happened. Thanks to that, we now display more useful errors to help you out of trouble. And in some cases, we will ask some input from you to learn more about your project so we can further improve.
If something is still off for you, feel free to create a new issue.


chore: add react compiler eslint rules

Summary
If we want better support for the React Compiler, adding eslint-plugin-react-compiler might be a good choice, I think.
Check List

[x] yarn run prettier for formatting code and docs

Thanks for the suggestion.
Can you open PRs to zustand and jotai too?
We try to keep the same eslint config among the three.

Thanks for the suggestion. Can you open PRs to zustand and jotai too? We try to keep the same eslint config among the three.

@dai-shi Done

valtio: https://github.com/pmndrs/valtio/pull/908
zustand: https://github.com/pmndrs/zustand/pull/2612
jotai: https://github.com/pmndrs/jotai/pull/2629

Thanks for the suggestion. Can you open PRs to zustand and jotai too? We try to keep the same eslint config among the three.

@dai-shi Done

valtio: chore: add react compiler eslint rules #908
zustand: chore: add react compiler eslint rules zustand#2612
jotai: chore: add react compiler eslint rules jotai#2629

@L-Qun 😊 Please let me know if there is anything else I need to do


[SQLLab, CSV export] UnicodeEncodeError when tab/filename contains non-ascii characters

Make sure these boxes are checked before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if any
[x] I have reproduced the issue with at least the latest released version of superset
[x] I have checked the issue tracker for the same issue and I haven't found one similar

Superset version
0.20.6
Expected results
Exporting a query in SQLLab to CSV works regardless of the presence of non-ascii characters in the tab label.
Actual results
If a tab cointains non-ascii characters , like e.g. 'ü', the following error is thrown:
2017-11-29 09:40:07,000:INFO:root:Exporting CSV file [Hkqwzx3gM]
2017-11-29 09:40:07,004:INFO:root:Parsing with sqlparse statement SELECT 1
2017-11-29 09:40:07,004:INFO:root:Fetching CSV from results backend [41ae1238-57cf-4a5a-ba21-7ff2776062d3]
2017-11-29 09:40:07,005:INFO:root:Decompressing
2017-11-29 09:40:07,006:INFO:root:Using pandas to convert to CSV
2017-11-29 09:40:07,006:INFO:root:Ready to return response
[2017-11-29 09:40:07 +0100] [79851] [ERROR] Error handling request /superset/csv/Hkqwzx3gM
Traceback (most recent call last):
  File "/opt/apps/superset/venv_superset_0.20.5/lib64/python3.4/site-packages/gunicorn/workers/sync.py", line 135, in handle
    self.handle_request(listener, req, client, addr)
  File "/opt/apps/superset/venv_superset_0.20.5/lib64/python3.4/site-packages/gunicorn/workers/sync.py", line 182, in handle_request
    resp.write(item)
  File "/opt/apps/superset/venv_superset_0.20.5/lib64/python3.4/site-packages/gunicorn/http/wsgi.py", line 341, in write
    self.send_headers()
  File "/opt/apps/superset/venv_superset_0.20.5/lib64/python3.4/site-packages/gunicorn/http/wsgi.py", line 337, in send_headers
    util.write(self.sock, util.to_bytestring(header_str, "ascii"))
  File "/opt/apps/superset/venv_superset_0.20.5/lib64/python3.4/site-packages/gunicorn/util.py", line 509, in to_bytestring
    return value.encode(encoding)
UnicodeEncodeError: 'ascii' codec can't encode character '\xfc' in position 206: ordinal not in range(128)

Steps to reproduce
Rename a tab to, e.g., 'ü', run a query and try to expoprt it.

I suspect that the filename generated from the tab label is the culprit.

Are you using it on python 2? I suggest you migrate to python 3.

Python 3.4. Therefore I am fairly surprised as well...

The errors suggests that gunicorn does not like non-ascii chars in http headers. I think it's right and so we have to be more careful on what we are sending.

Looks like unidecode or Unicode data might be helpful here: https://stackoverflow.com/questions/517923/what-is-the-best-way-to-remove-accents-in-a-python-unicode-string/517974


install/micro_ros_setup/lib/micro_ros_setup/yaml_filter.py

Hello! I am trying to run an example on the Zephyr Emulator by following the micro-ROS application tutorial for RTOS and getting some errors while building.
Operating System:

Ubuntu 20.04.2 LTS

Steps to reproduce the issue

$ros2 run micro_ros_setup create_firmware_ws.sh zephyr host
...
Skip distro "ardent" different from requested "foxy"
Skip distro "bouncy" different from requested "foxy"
Skip distro "crystal" different from requested "foxy"
Skip distro "dashing" different from requested "foxy"
Skip distro "eloquent" different from requested "foxy"
Add distro "foxy"
Skip distro "galactic" different from requested "foxy"
Skip distro "groovy" different from requested "foxy"
Skip distro "hydro" different from requested "foxy"
Skip distro "indigo" different from requested "foxy"
Skip distro "jade" different from requested "foxy"
Skip distro "kinetic" different from requested "foxy"
Skip distro "lunar" different from requested "foxy"
Skip distro "melodic" different from requested "foxy"
Skip distro "noetic" different from requested "foxy"
Skip distro "rolling" different from requested "foxy"
updated cache in /home/harmony/.ros/rosdep/sources.cache
#All required rosdeps installed successfully
Traceback (most recent call last):
File "/home/harmony/workspace/microros_ws_zephyr/install/micro_ros_setup/lib/micro_ros_setup/yaml_filter.py", line 15, in
for key in repos_info["repositories"]:
TypeError: 'NoneType' object is not subscriptable
is there any package i am missing? or any other steps to follow?
Thank you very much.

Which release of micro-ROS are you targeting? Galactic or Foxy?

foxy.I've tried many times and it's the same error

Check this patch: https://github.com/micro-ROS/micro_ros_setup/pull/365

thanks.the error message disappears. it should download some packages from github,e.g. ament/ament_cmake,but it didn`t,i wonder why.
also
when Configuring the firmware with the following command:
$ros2 run micro_ros_setup configure_firmware.sh ping_pong --transport udp --ip <IP_ADDRESS> --port 8888
the following error appears:
~/workspace/microros_ws_zephyr/firmware/zephyr_apps/apps: No such file or directory

Which version of Python are you using?

Python 3.8.10 (default, Jun  2 2021, 10:49:15)
[GCC 9.4.0] on linux

I have had no problems replicating this: https://asciinema.org/a/v5U7tsx80e52owitp90kafZ9K

i appreciate it, and i will check

Closing, feel free to reopen on any update.


add delayed process for etcdv3 watch

If there is no new change happening after 5 seconds since last change, the rest job of Processor will continue.

@zyf0330 does it fix #629 ? Also, I'm not sure about the 5 seconds sleep, it's too much of a delay, I was thinking of something under 1 second, like 200ms or 400ms. What are you thoughts?

This fix isn't needed anymore, because reusing previous watch has solved this.

No, I just want another demand.
This feature can avoid frequently reloading when multiple keys are changed.

Please tell me a situation where people want frequent reloading.

@zyf0330 it's not about reloading frequency, but rather about feedback latency. For example, when confd is used to configure Nginx I want the change to happen as soon as possible.

Ok, maybe we can set a flag to open it optionally.

Just fix a bug. If rch is closed, case wresp = <-rch: will loop forever and cpu usage high.


Dropping capitalised ukftt/TC/2022/343

https://github.com/nationalarchives/ds-caselaw-custom-pdfs/tree/main/files/ukftt/TC/2022/343 deleted in favour of https://github.com/nationalarchives/ds-caselaw-custom-pdfs/tree/main/files/ukftt/tc/2022/343

Approval: https://dxw.slack.com/archives/C02TP2L2Z0F/p1665483406920899?thread_ts=1665483077.171309&cid=C02TP2L2Z0F

 Don't generate WeasyPrint PDFs for judgments with emf images. Somehow!


hi,i wanna to know how this bot can get history version of map ?

and how this bot can get none-public map of users ?

Hey
Well, it's just a feature of SC2. All past revisions of a map are stored on the server indefinitely (unless explicitly deleted by author (or by Blizzard), but I've seen cases where even that didn't remove it for good).
It's possible thanks to SC2's architecture - the client must have a way to request any existing map, regardless of the version, or privacy settings - several features depend on it:

sc2replay's, of course - in order to replay some old match, the client must have access to specific version of the map the game was played on.
In-game match history, the underlying data behind match details (s2gs) is structured in the way that it references certain definitions (for instance, units listed in the build order section) and this kind of data from the map's header.
As an example, whenever you navigate into someone's match history, and open up a match played on a private version of the map, SC2 will download headers of that map in the background and will store it in the local cache.
Map's dependencies - sc2map can depend on other mods published on Battle.net. These can be locked to specific version of such mod, which is often used to maintain backwards compatibility, and avoid situations where updating the mod by the author, could break all other maps that depend on it.
And there's likely a lot more reasons, but these are the things I'm aware of.

About private maps in particular: there's nothing special about them. They appear in the system like any other map. If it can be seen in the system, then it can be retrieved. I'm pretty sure that was even intended - the privacy system only keeps things unlisted in the game - away from the wide public. But it likely never meant to be a security measure - it doesn't protect the map's content.
Retrieving any map by the bot is possible thanks to the customized sc2 client. And as I've mentioned in the README, I don't not plan to disclose code responsible for communicating with Battle.net. Thus I can't elaborate on it further, sorry.


UK/AU Datepicker format

Select one ...  (check one with "x")
[*] bug
[ ] feature request
[ ] enhancement

Expected behavior
I'm trying to get the datepicker to display in dd/mm/yyyy format. I've followed the instructions and run the cli app as GB and AU (i.e. ng serve --locale en-gb)
The datepicker should use the format of dd/mm/yyyy
Actual behavior
The datepicker comes up in mm/dd/yyyy format
Environment details

Angular version: 5.2.4
Clarity version: 0.11.9

@kuba-010: ng serve --aot --locale en-GB should work. You need the aot flag to load the locale data. For JIT compiler (which is without the aot flag), you need to follow the instructions in the docs:

More details here: https://angular.io/guide/i18n
Let us know if that helps. Closing this issue based on the above info. Please feel free to reopen if you have more questions. Thanks!

Oops overlooked the --aot and JIT differences, my bad! Thanks for that!

Hi @adityarb88 ,
Is it possible to get 'YYYY-MM-DD' formate because after this it gets the format of 'DD-MM-YYYY'.

@delockdown: You could bind to clrDateChange. That emits a Javascript Date object.  Would that help? You could also refer to this issue for more information: https://github.com/vmware/clarity/issues/2056

Hi @adityarb88, Can you create a example of doing that change that for me. It would be very helpful to me.

@delockdown: We already have an example of that in our docs:
https://vmware.github.io/clarity/documentation/v0.11/datepicker

Let us know if that helps.

Hi @adityarb88 , i am set locale to my app in app.module file like ' providers: [{ provide: LOCALE_ID, useValue: 'en-IN' }]', but this ' en-IN' locale need to show format as DDMMYYYY but actually it showing MMDDYYYY format. check once Stackblitz.
One more doubt is now date picker have change detection option , i mean change the actual date emit any event ?.
Thank you.

@adityarb88 This doesn't actually appear to be working in the current version (0.12.5), setting LOCALE_ID in the way shown doesn't affect the date format at all in the case of en-GB and in fact causes errors in the app when you attempt to set it to any non en locale


Does alienfan need to be always open in the background?

Describe the bug
Doesn't seem to work, when closed, or is it just my pc problem? Does it generally work when the app is closed?
To Reproduce
Open alienfan-gui, set curves, close the app, do some test, like open a game, the fans won't start till I open the alienfan again
Expected behavior
should automatically fans spin according to temps in background
Screenshots
You gotta feel the heat
System (please complete the following information):

Model: Dell g15 5515
OS: Windows 11 stable

Yes, fan control is only active then app running.
System state stored at app start and restored at quit.
There is no other way for manual fan control, AWCC using the same, they just close UI, but not the app.


chore: 🔖 release 1.1.1

:robot: I have created a release beep boop
1.1.1 (2023-12-05)
Documentation

📝 Fix discovery example in the README (#69) (7657e6e)
📝 remove dropped service parameter from the discovery example in README (#71) (3e02562)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/h2oai/authn-py/releases/tag/v1.1.1 :sunflower:


Added the activerecord-session_store gem

As of https://github.com/rails/rails/commit/0ffe19056c8e8b2f9ae9d487b896cad2ce9387ad the session store was extracted into a gem. We need it for the session_store: sql functionality.
https://bugzilla.redhat.com/show_bug.cgi?id=1300018

@Fryguy @gtanzillo

Do we even need session_store in the database anymore?  Let's just :scissors: it.  @dclarizio ?

Also MemoryStore is probably not need either, except for maybe tests

This is still required for people looking to use load balancing.

Oh well...I tried to get a free :scissors: :D

:+1:

:+1:

Can we write a spec or something around this so we can avoid it being a problem in the future?


Support InitContainer for node-red pod

In the values.yaml we should add a key initcontainer to define a whole initcontainer. In the template we can reference on it with toYaml

I would recommend to classify this a bug, since the helm chart is not properly working on EKS or GKE in persistent mode.
How to reproduce the error
helm repo add node-red https://schwarzit.github.io/node-red-chart/
helm repo update
helm upgrade --install node-red-test node-red/node-red -f values.yml --namespace dev --version 0.3.2

While the values.yml is defined as follows:
replicaCount: 1

env:
  - name: "TZ"
    value: "UTC"
  - name: "NODE_RED_ENABLE_SAFE_MODE"
    value: "false"
  - name: "NODE_RED_ENABLE_PROJECTS"
    value: "false"
  - name: "FLOWS"
    value: "flows.json"

persistence:
  enabled: true
  accessMode: ReadWriteOnce
  size: 10Gi

ingress:
  enabled: false

resources:
  limits:
    cpu: 100m
    memory: 256Mi

service:
  type: NodePort
  port: 1880

done, thx again @Langhalsdino for the contribution!


TypeError: Object ... has no method 'split'

Hi
I'm trying to run a Rails 2.3.10 app and I get the erro below. Meanwhile I'm trying to write a failing test case, but I'm still figuring out how to use cake.
Meanwhile, I edit the lines 257-261 on nack/lib/client.js from:
        for (k in rawHeaders) {
          vs = rawHeaders[k];
          v = vs.split("\n");
          this.headers[k] = v.length > 0 ? v.join("\r\n" + k + ": ") : vs;
        }

to
        for (k in rawHeaders) {
          vs = rawHeaders[k];
          this.headers[k] = vs;
        }

and I could run the app.
The error is this:
TypeError: Object _loja_session=BAh7BzoTdXNlci5yZXR1cm5fdG8iCy9hZG1pbjoPc2Vzc2lvbl9pZCIlNzI2OThmZmU0M2FlYmYzOGIzZGZjN2U3MDBjMzNjMTk%3D--3a112c99fb073ac3889376db7612d608af144918; path=/; HttpOnly has no method 'split'
TypeError: Object _loja_session=BAh7BzoTdXNlci5yZXR1cm5fdG8iCy9hZG1pbjoPc2Vzc2lvbl9pZCIlNzI2OThmZmU0M2FlYmYzOGIzZGZjN2U3MDBjMzNjMTk%3D--3a112c99fb073ac3889376db7612d608af144918; path=/; HttpOnly has no method 'split'
at ClientResponse._receiveData (/Users/marcus/Library/Application Support/Pow/Versions/0.2.2/node_modules/nack/lib/client.js:259:22)
at [object Object].<anonymous> (/Users/marcus/Library/Application Support/Pow/Versions/0.2.2/node_modules/nack/lib/client.js:46:33)
at [object Object].emit (events.js:64:17)
at Client.<anonymous> (/Users/marcus/Library/Application Support/Pow/Versions/0.2.2/node_modules/nack/node_modules/netstring/lib/ns.js:206:26)
at Client.emit (events.js:64:17)
at Client._onReadable (net.js:672:14)
at IOWatcher.onReadable [as callback] (net.js:177:10)

Look at any headers that are being set in your app. For me, it was pagination headers, which were being set to numeric values.
  headers['X-Page'] = @page
  headers['X-Per-Page'] = @per_page
  headers['X-Total-Pages'] = @total_count

Turning the numeric values into a string fixed this issue.
  headers['X-Page'] = @page.to_s
  headers['X-Per-Page'] = @per_page.to_s
  headers['X-Total-Pages'] = @total_count.to_s


more correct way to build node stats in distributed fast hist

the current approach is to choose the first feature's histogram to build node stats,
however, when this feature is too sparse, it will lead to a tree without any growth
so this PR addresses the issue by
(1) calculating local stats by summing up all samples stats
(2) adding an additional bin in each node's histogram and use it to sync the node's stats across workers
closes https://github.com/dmlc/xgboost/issues/4127

there is a bug when dealing with dense data layout................sigh....

@CodingCat Do you need help?

@hcho3 thanks, it's fine now, though the logic for depthwise becomes a bit tricky

it's ready to review now

@trivialfis @RAMitchell @hcho3  I believe it is the last commit I would put in distributed hist....thanks for the review

Can you please explain a little bit in words the purpose of this PR and what led you to make these changes? I think I have an idea but I want to make sure I understand.
I don't like using the last slot of the histogram to store the node stats. I believe if something has a distinct purpose it should be a separate variable. This can very easily create problems later given that the histogram array may not always be the same size depending on some state. I definitely recommend reading this as a reference for c++ architecture: https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#Rp-direct
Some recent changes of mine (#4015) may actually mean that we can get the summary statistics from a cache after split finding and we do not need to recalculate these at every node, only the root. This might simplify your PR.

@RAMitchell so the current approach in master branch is to use first feature's histogram to build the node's stats, which assumes that the feature is not "too sparse" and summing up all values in the bins across workers will make an approximate result....but it's not true for some cases, and it will lead to a no-grow tree as indicated in #4127
using the last bin to store stats is to mimic the behavior of approx which is motivated by saving a rabit call (which is slow and the main reason that we don't see a significant speedup when increasing worker number beyond some values)
If I understand #4015 correctly, a lot of code (e.g. https://github.com/dmlc/xgboost/blob/d506a8bc633fea3c8d535c70a5c11047122f07b5/src/tree/updater_quantile_hist.cc#L757-L796) is unnecessary?

I like the idea in #4015 @RAMitchell , this should save a significant amount of cpu cycles.....I would move forward to remove InitNewNode in hist here....

@RAMitchell I have made the changes based on #4015, thanks for the review

@CodingCat Is this ready to merge?

I think it's ready, waiting for confirm from anyone of you


Map horizontal alignment is inconsistent between browsers

Describe the bug
The accessibility map has inconsistent horizontal alignment within the Map page, depending on which browser is being used to view the site. In Chrome, the entire map and filters "assembly" is justified to the left side of the page, while in Firefox, it is centred. The result is not aesthetically pleasing, and a little jarring considering the main website navigation and footer are centre-justified.
To Reproduce
Steps to reproduce the behaviour:

In an affected version of Chrome, go to https://wecount.inclusivedesign.ca/map
See that the page contents are left-justified.

Expected behavior
The page contents should be centre-justified across all browsers, as it is in Firefox.
Screenshots
Chrome (undesired behaviour)

Firefox (desired behaviour)

Desktop:

OS: Windows 10 Pro v20H2
Browser: Chrome 91, Firefox 89
Affects version: 2.6.0

Smartphone:
N/A, the issue will not present itself at smaller viewport widths.
Additional context
There may be other browsers affected by this issue. A workable fix may be to apply justify-content: center; to the rule #defaultContainer.map .content-wrapper
Another solution to consider which may require more work would be to make the page contents occupy the full width of the page at all times.

Hi @BlueSlug,
Adding margin:auto; to #defaultContainer.map .content-wrapper aligns  the map to the center.
Browsers
Safari 13.1.3
Firefox 89.0
Fixes #611

Hi!
I'm new at open source.
Could I take this issue?

@carlosmarin96, thanks for your interest in this ticket. @rwgers has described the solution.
Thanks for your help, @rwgers. Feel free to issue a pull request if you want.


Fix nodejs deprecated warning

This Pr fix the issue about deprecated warning reference from https://github.com/cloudflare/pages-action/issues/117

Any ETA for its release?

@riderx can we also update the build cli esbuild target from es2021 to node20?
From
https://github.com/cloudflare/pages-action/blob/aeb0d936a7e08b4861c3d0ac8811fe39138085f9/package.json#L7
To
"build": "npx esbuild src/index.ts --bundle --platform=node --target=node20 --outfile=index.js",

Any reason this hasn't been merged yet?

what's the blocker of this?

Thanks @andykenward i modified it!
I'm not a core contributor, so I cannot do much more than a PR

Maybe @WalshyDev if you can report internally it, it would me super nice <3

cc: @cloudflare/banda-team

Also need to update @types/node to 20. Plus we can remove the usage of the NPM package "undici" for fetch as Node.js 20 supports fetch natively.

What is preventing merging this PR?

Is there any reason this hasn't been merged yet?

This repo is going to be deprecated. https://github.com/cloudflare/pages-action/issues/131
Use wrangler-action instead to deploy pages.
https://github.com/cloudflare/wrangler-action?tab=readme-ov-file#deploy-your-pages-site-production--preview

Thank you for your help in maintaining this repository 🧡. We've migrated to wrangler-action and are making improvements to ensure that contributions like this will be more easily integrated and better supported. Please come join us at wrangler-action!


Windows GUI- Saving Client password

Is there a way to save the client password on the windows GUI?
I tried this guide which suggests adding a line "auth-user-pass auth.txt" to the config file and saving the username & password to a text file "auth.txt" in the config folder, but it doesn't work. Also when I manually connect, it only asks for a password, not a username.
https://vpn.ac/knowledgebase/40/How-to-save-Username-and-Password-in-OpenVPN-GUI-Windows.html
Also is there a way to create a client profile without a password, to avoid adding it to the client config?

it isn't a user pass which is why you can't save it.  its a pass to decrypt the certificate.
you can create the certificate with no pass as detailed here http://www.pivpn.io/ look at the pivpn command.  the add subcommand takes an optional nopass argument.  if you use that you won't be prompted for anything.  To be clear it is still rather secure.  you are using certificate auth instead of user/pass.  the default is to use the certificate auth that is encrypted with a password.  in your case you can just use the certificate after you create with the nopass options.

Closing as there is a pivpn add nopass option now as well.


haskellPackages.xml-extractors: broken -> unbroken

Motivation for this change
Remove xml-extractors from the broken set since the package builds successfully.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@liff Thanks for fixing this, and @sternenseemann thanks for the review!


refactor(batch): Use futures-async-stream to implement StreamScan executor

Signed-off-by: d2lark<EMAIL_ADDRESS>Implement StreamScanExecutor  using Executor2 trait
PLEASE DO NOT LEAVE THIS EMPTY !!!
Please explain IN DETAIL what the changes are in this PR and why they are needed:

Summarize your change (mandatory)
How does this PR work? Need a brief introduction for the changed logic (optional)
Describe clearly one logical change and avoid lazy messages (optional)
Describe any limitations of the current code (optional)

Checklist

[x] I have written necessary docs and comments
[x] I have added necessary unit tests and integration tests

Refer to a related PR or issue link (optional)
close https://github.com/singularity-data/risingwave/issues/1944

https://github.com/singularity-data/risingwave/actions/runs/2243726092

CI failed due to an unstable test and someone is working on fix it, please wait a moment.

CI: https://github.com/singularity-data/risingwave/actions/runs/2243765265

CI: https://github.com/singularity-data/risingwave/actions/runs/2244511049

my bad？

CI: https://github.com/singularity-data/risingwave/actions/runs/2244511049

my bad？

seems not, I will investigate on it

(rerun) CI is running: https://github.com/singularity-data/risingwave/actions/runs/2244749127

Thanks!


client: improve connection cancellation handling

Introduce default read deadlines
Handle them in readLoop
Close transport connection on context done

Looks like it was already done.


Added travis ci support for modern node versions

Let’s keep 0.10. There’s an awful lot of that in production systems. I’m adding you as a collaborator so you can manage this yourself.

Thanks! Added it back. Do you also mind if I updated the readme to es6?

@amilajack I’d be fine with adding a section describing the ES6 equivalent syntax. The future is not distributed evenly.

Sounds good!


Added: Documentation for adding alerts in Grafana with PostgreSQL

Description
I wrote a detailed documentation and step by step tutorial about alerts in Grafana:
-Why to use them
-How to create an alert and how to link it to certain contacts and services
Checklist

[x] I have read the contributing guidelines and the code of conduct.
[x] I have followed the documentation style.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


[DIA-34] Add Sentry monitoring

Also fixes sort order when retrieving all stories

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


Determine whether OpenJ9 builds still need the mingw-cygwin label

All of our machines should be configured the same so the mingw-cygwin label locks it onto the ibmcloud systems unnecessarily (in theory). We should verify whether the openj9 builds will run elsewhere (I think @Haroon-Khel has probably already verified the alibaba windows boxes)

Have asked Haroon to confirm about the alibaba machine on Slack.
Running builds on the azure machines now.

As per @adamfarley's request, a fresh openj9 build on build-alibaba-win2012r2-x64-1
https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-windows-x64-openj9/936/console

@Haroon-Khel Isn't that the same test you've alreayd done that worked at https://github.com/AdoptOpenJDK/openjdk-infrastructure/issues/1818#issuecomment-785190334?

@Haroon-Khel Isn't that the same test you've already done that worked at AdoptOpenJDK/openjdk-infrastructure#1818 (comment)?

Yes, I mentioned that in the slack thread. Wouldnt hurt to run another one though; more recent

The only other two windows machines we could run on are the two azure machines. Here's a pair of jdk8 and jdk16 runs to check those:
build-azure-win2012r2-x64-1 (JDK16) - https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk16/job/jdk16-windows-x64-hotspot/57/
build-azure-win2012r2-x64-2 (JDK8) - https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-windows-x64-openj9/1007/

Ok, results:
Azure machines: Builds and tests are green.
Alibaba machine: Build is green, handful of failures in the tests. Checking to make sure that there's nothing new.

Alibaba machine: Build is green, handful of failures in the tests. Checking to make sure that there's nothing new.

Presumably that was just with the build running on alibaba - the tests were still just running on whatever random machines they happened to land on?

Yes. The Alibaba build was tested on test-ibmcloud-win2012r2-x64-1.

Re-running the lang tests for the alibaba build on the machine that ran and passed the testing for the azure machines (which was, ironically, build-alibaba-win2012r2-x64-2).
https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/7366/console

Ok, those all passed.
Looks to me like the sanity.openjdk tests can all pass on builds generated from the alibaba and azure machines, so the mingw label can be safely removed from the list of windows build requirements.
@Haroon-Khel - Your thoughts?


may vai_q_onnx causes OOM error

My work follow this url.
https://docs.xilinx.com/r/en-US/ug1414-vitis-ai/ONNX-Runtime-Version-vai_q_onnx
my env as follow:
Cerberus               1.3.5
coloredlogs            15.0.1
exceptiongroup         1.1.2
flatbuffers            23.5.26
glog                   0.3.1
humanfriendly          10.0
imageio                2.31.1
iniconfig              2.0.0
mkl-fft                1.3.6
mkl-random             1.2.2
mkl-service            2.4.0
mpmath                 1.3.0
numpy                  1.25.2
onnx                   1.14.0
onnxruntime            1.15.1
onnxruntime-extensions 0.8.0
opencv-python          <IP_ADDRESS>
packaging              23.1
Pillow                 10.0.0
pip                    23.2.1
protobuf               4.24.0
pyreadline3            3.4.1
pytest                 7.4.0
python-gflags          3.1.2
python-opencv          <IP_ADDRESS>
setuptools             68.0.0
sympy                  1.12
tomli                  2.0.1
torch                  1.10.1
torchaudio             0.10.1
torchvision            0.11.2
typing_extensions      4.7.1
vai-q-onnx             1.14.0
wheel                  0.38.4

my code:
import vai_q_onnx
import cv2
import numpy
import os
from torch.utils.data import DataLoader
from onnxruntime.quantization import CalibrationDataReader, QuantFormat

# data
imgs_path = '../data/'

class ImageReader(CalibrationDataReader):
    def __init__(self, input_name="input") -> None:
        super().__init__()
        self.input_name = input_name
        self.img_list = []
        # print
        self.img_counter = 0

        for line in os.listdir(imgs_path):
            if line.endswith(".png"):
                img = cv2.imread(imgs_path + line)
                img = numpy.transpose(img, (2, 0, 1))
                img_data = numpy.expand_dims(img,axis=0).astype(numpy.float32)
                self.img_list.append(img_data)

        self.iterator = iter(DataLoader(self.img_list, batch_size=1))

    def get_next(self) -> dict:
        self.img_counter = self.img_counter + 1
        print("get {} image!".format(self.img_counter))
        next_data = next(self.iterator)[0].numpy()
        ret = {self.input_name: next_data}
        return ret

if __name__ == "__main__":
    input_model = '../onnxs/in.onnx'
    output_model = '../onnx/out.onnx'

    dr = ImageReader()

    # quant
    vai_q_onnx.quantize_static(
        model_input=input_model,
        model_output=output_model,
        calibration_data_reader=dr,
        quant_format=QuantFormat.QDQ
    )

When i run this script in Ubuntu, task be Killed! According to the system logs, the reason is that it occupies too much memory(the Ubuntu has 32GB memory).
Image sample as follow:
shape = (3, 512, 512)
size almost: 450KB

Copy .whl files and install to Windows. To reproduce:

However Windows, system will not kill the task. So i still get quantified model.

@Liuqh12 I can see some evidence that there are a variety of ONNX Runtime memory settings that may influence this, but I have no idea whether this has the potential to solve the problem that you are seeing.  For example: https://github.com/microsoft/onnxruntime/issues/1725
If it is possible for you to do so, perhaps you could test your model leveraging ONNX Runtime on your board without the Vitis AI Execution Provider and report back whether you see the issue with your model executing with just the CPU execution provider.


scrolling issue w/multiple long modals

Steps
Go to example. http://codepen.io/anon/pen/aWLdxg?editors=0011
Child modal's dimmerattribute set to true
Click the trigger button
Click the proceed button on the modal
Click on dimmer of the child modal
The child modal closes.
Expected Result
Parent modal's scrolling should work
Actual Result
It doesn't
Version
0.68.2
Testcase
http://codepen.io/anon/pen/aWLdxg?editors=0011

Duplicate #1157


Vcpkg install aws sdk 1.8

Confirm by changing [ ] to [x] below to ensure that it's a bug:

[ x] I've gone though Developer Guide and API reference
[x ] I've searched for previous similar issues and didn't find any solution

Describe the bug
Cannot set tag specicifacations when creating internet gateway in 1.7 sdk.
SDK version number
1.7.333 <-installed by vcpkg
Platform/OS/Hardware/Device
Windows 10 VS2019
To Reproduce (observed behavior)
Install skd via official

Hi @kenkit ,
A little confused here, the title says that it installs 1.8, but I've checked vcpkg repo and it says 1.7.33...
Is it safe to assume that you are asking us to update the vcpkg version to be 1.8?

yes, sorry for the confusion.

Just as an update,
I opened a PR on vcpkg, hopefully it will be resolved pretty soon.

It has been merged and should be available now, thanks.


Fix email parsing for multiple text parts and inline images

Modified EmailData.from_email_message to handle both inline and attachment images
Fixed handling of multiple text/plain parts by combining them
Added comprehensive tests for multipart email handling
Fixed image MIME subtype specification in tests
Applied code formatting

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 0% with 6 lines in your changes missing coverage. Please review.

Files with missing lines
Patch %
Lines

src/pymailai/message.py
0.00%
6 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files with missing lines
Coverage Δ

src/pymailai/message.py
0.00% <0.00%> (ø)


Mitigate HTTPoxy Vulnerability

https://www.nginx.com/blog/mitigating-the-httpoxy-vulnerability-with-nginx/

LGTM


Hope to have a plugin manager

For users who have lots of plugins, it's difficult for them to manage different
language's plugins.Especially when they want to remove one plugin.So I hope in next version we can have a plugin manager to divide plugins into different groups.
eg.
C/C++:
C++ Intellisense
C++ Clang
Web:
HTML CSS Support
HTML Snippets
thanks:)

@stdKonjac Can you please elaborate your requirement and what you are expecting in detail?

@sandy081 I mean a tree view like this:

We'd need to have some type of specific categorization from the marketplace otherwise this doesn't scale properly. Right now there is only an array of categories and tags, so this would need to be supported from the marketplace. Given this, will be closing this as out of scope until we get that support.


Pull Stampy info directly from coda

Sample code on how to pull updated Stampy data from data:
https://github.com/StampyAI/stampy-nlp/blob/main/src/stampy_nlp/utilities/coda_utils.py

Just to be sure, is this a good time to close the issue

Yep! A little trick is in your PR or commits, you can mention this issue by number to associate them.


[DNM] west.yml: Update mcuboot revision

Update mcuboot revision to include following updates:
[8cf78cbd] Fix serial recovery compilation warnings
Signed-off-by: Dominik Ermel<EMAIL_ADDRESS>

already satisfied by #28967


Logout option

Can you please add logout option
Thanks

If you run dumper with -logout flag, it will close it's Telegram session and remove .session file. Isn't that what you are looking for?

Oh sorry I wasn't realized you already add it 2 months  ago. Thank you so much.


Added support for multi-tenant authentication for Key Vault clients.

Description
Fixes: #24146.
All SDK Contribution checklist:

[X] The pull request does not introduce [breaking changes]
[X] CHANGELOG is updated for new features, bug fixes or other significant changes.
[X] I have read the contribution guidelines.

General Guidelines and Best Practices

[X] Title of the pull request is clear and informative.
[X] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

/check-enforcer override


Construct the about us page with accordance to the current design

assign me this issue

I'd like to work on this issue.Kindly assign it to me

Assigned it to you @vaibhv232
Best of luck 🥳

Can I try working on this issue?


Create k8s cert for *.leapfrogai.bigbang.dev

When attempting to hit a user facing application (doug-translate, leapfrog-ui) using the host *.leapfrogai.bigbang.dev some browsers will fail to load due to the DUBBD cert being designed for *.bigbang.dev.

Closing this issue. Using UDS should be all we need.


when advertisement data become null, it cache last one

my ble device broadcast data in advertisement data area, and it changes times to times,
in this case:
a few seconds ago, adv data got a buffer like
peripheral.advertisement.manufacturerData: 0101000f000700000007000300f200c901b50ede
and now adv data, some how ,is null from device, but i still got
peripheral.advertisement.manufacturerData: 0101000f000700000007000300f200c901b50ede
i believe this issue came from javascript Object reference, peripheral.advertisement is the same one Object and when advdata is null we should execute 'delete peripheral.advertisement.manufacturerData' to avoid this issue
i guess it is in ../build/Release/binding.node file?

@javaxiu this is the expected behaviour from noble, it stores the old data and "or's" in the new: https://github.com/sandeepmistry/noble/blob/master/lib/hci-socket/gap.js#L98-L238
If you have a proposal to change this, please open a pull request.