Fix mqtt sessions test

Type of change
Select the type of your PR

Bugfix

Description
This PR fixes the SessionTest#previousPersistentSessionDiscarded test which failed due to connector format being changed.
Checklist
Please go through this checklist and make sure all applicable tasks have been done

[x] Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally

@enmasse-ci run tests testcase="SessionTest"

:heavy_exclamation_mark: Build Failed :heavy_exclamation_mark:

@enmasse-ci run tests profile=shared testcase=mqtt.SessionTest

:heavy_check_mark: Test Summary :heavy_check_mark:
TEST_PROFILE: shared
TEST_CASE: mqtt.SessionTest
TOTAL: 1
PASS: 1
FAIL: 0
SKIP: 0


Cluster gets to "unavailable" state and back to "active" often.

Rancher server -  Apr 17 build from master
Create any kind of cluster ( Custom/DO/AWS) and wait for the cluster to get to active sate.
Create few workloads.
After sometime , notice that cluster gets to "unavailable" state and back to "active" often.
Following are the logs seen when  cluster gets to "unavailable" state:
2018/04/17 23:22:28 [ERROR] Unknown error: Get https://<ip>:6443/api/v1/namespaces: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "kube-ca")
2018/04/17 23:22:28 [ERROR] Unknown error: Get https://<IP_ADDRESS>:6443/api/v1/persistentvolumes: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "kube-ca")
2018/04/17 23:22:28 [ERROR] Unknown error: Get https://<ip>:6443/api/v1/pods: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "kube-ca")
...
....

E0417 23:22:28.920159       1 watch.go:228] unable to encode watch object: write tcp <IP_ADDRESS>:6443-><IP_ADDRESS>:44160: write: connection reset by peer (&streaming.encoder{writer:(*metrics.fancyResponseWriterDelegator)(0xc4358c3df0), encoder:(*versioning.codec)(0xc43c625dd0), buf:(*bytes.Buffer)(0xc42e580e70)})
2018/04/17 23:22:31 [ERROR] Cluster c-rsztk is unavaliable, stopping controllers and waiting for successful ping: Failed to communicate with API server: Get https://<ip>:6443/api/v1/componentstatuses: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "kube-ca")
2018/04/17 23:22:31 [INFO] Stopping cluster agent forc-rsztk
2018/04/17 23:22:31 [INFO] Shutting down CronJobController controller
2018/04/17 23:22:31 [INFO] Shutting down JobController controller
2018/04/17 23:22:31 [INFO] Shutting down IngressController controller
2018/04/17 23:22:31 [INFO] Shutting down PodSecurityPolicyController controller
2018/04/17 23:22:31 [INFO] Shutting down SourceCodeRepositoryController controller
2018/04/17 23:22:31 [INFO] Shutting down RoleController controller
2018/04/17 23:22:31 [INFO] Shutting down ClusterRoleController controller
2018/04/17 23:22:31 [INFO] Shutting down RoleBindingController controller
2018/04/17 23:22:31 [INFO] Shutting down ClusterRoleBindingController controller
2018/04/17 23:22:31 [INFO] Shutting down EndpointsController controller
2018/04/17 23:22:31 [INFO] Shutting down ServiceAccountController controller
2018/04/17 23:22:31 [INFO] Shutting down SecretController controller
2018/04/17 23:22:31 [INFO] Shutting down NamespaceController controller
2018/04/17 23:22:31 [INFO] Shutting down EventController controller
2018/04/17 23:22:31 [INFO] Shutting down ReplicationControllerController controller
2018/04/17 23:22:31 [INFO] Shutting down NodeController controller
2018/04/17 23:22:31 [INFO] Shutting down PodController controller
2018/04/17 23:22:31 [INFO] Shutting down ServiceController controller
2018/04/17 23:22:31 [INFO] Shutting down StatefulSetController controller
2018/04/17 23:22:31 [INFO] Shutting down DaemonSetController controller
2018/04/17 23:22:31 [INFO] Shutting down ReplicaSetController controller
2018/04/17 23:22:31 [INFO] Shutting down DeploymentController controller
2018/04/17 23:22:31 [INFO] Shutting down NamespaceController controller
2018/04/17 23:22:31 [INFO] Shutting down SecretController controller
2018/04/17 23:22:31 [INFO] Shutting down NamespaceComposeConfigController controller
2018/04/17 23:22:31 [INFO] Shutting down AppController controller
2018/04/17 23:22:31 [INFO] Shutting down ClusterComposeConfigController controller
2018/04/17 23:22:31 [INFO] Shutting down PodSecurityPolicyTemplateProjectBindingController controller
2018/04/17 23:22:31 [INFO] Shutting down PodSecurityPolicyTemplateController controller
2018/04/17 23:22:31 [INFO] Shutting down ClusterPipelineController controller
2018/04/17 23:22:31 [INFO] Shutting down SourceCodeCredentialController controller
2018/04/17 23:22:31 [INFO] Shutting down PipelineExecutionLogController controller
2018/04/17 23:22:31 [INFO] Shutting down PipelineExecutionController controller
2018/04/17 23:22:31 [INFO] Shutting down PipelineController controller
2018/04/17 23:22:31 [INFO] Shutting down ProjectNetworkPolicyController controller
2018/04/17 23:22:31 [INFO] Shutting down ClusterLoggingController controller
2018/04/17 23:22:31 [INFO] Shutting down ProjectLoggingController controller
2018/04/17 23:22:31 [INFO] Shutting down ClusterLoggingController controller
2018/04/17 23:22:31 [INFO] Shutting down GlobalRoleBindingController controller
2018/04/17 23:22:31 [INFO] Shutting down ClusterController controller
2018/04/17 23:22:31 [INFO] Shutting down RoleTemplateController controller
2018/04/17 23:22:31 [INFO] Shutting down ClusterRoleTemplateBindingController controller
2018/04/17 23:22:31 [INFO] Shutting down ProjectRoleTemplateBindingController controller
2018/04/17 23:22:31 [INFO] Shutting down NodeController controller
2018/04/17 23:22:31 [INFO] Shutting down NotifierController controller
2018/04/17 23:22:31 [INFO] Shutting down NotifierController controller
2018/04/17 23:22:31 [INFO] Shutting down ProjectAlertController controller
2018/04/17 23:22:31 [INFO] Shutting down ClusterAlertController controller
2018/04/17 23:22:31 [INFO] Shutting down ProjectController controller
2018/04/17 23:22:31 [INFO] Shutting down NetworkPolicyController controller
2018/04/17 23:22:31 [INFO] Cluster c-rsztk may be back online
2018/04/17 23:22:31 [INFO] Starting cluster agent forc-rsztk
2018/04/17 23:22:31 [INFO] Registering project network policy
2018/04/17 23:22:31 [INFO] Registering namespaceHandler for adding labels
2018/04/17 23:22:31 [INFO] registering podsecuritypolicy cluster handler for cluster c-rsztk
2018/04/17 23:22:31 [INFO] registering podsecuritypolicy project handler for cluster c-rsztk
2018/04/17 23:22:31 [INFO] registering podsecuritypolicy namespace handler for cluster c-rsztk
2018/04/17 23:22:31 [INFO] registering podsecuritypolicy serviceaccount handler for cluster c-rsztk
2018/04/17 23:22:31 [INFO] registering podsecuritypolicy template handler for cluster c-rsztk
2018/04/17 23:22:31 [INFO] Starting cluster controllers for c-rsztk
2018/04/17 23:22:31 [INFO] Syncing NetworkPolicyController Controller
2018/04/17 23:22:31 [INFO] Syncing JobController Controller
2018/04/17 23:22:31 [INFO] Syncing IngressController Controller
2018/04/17 23:22:31 [INFO] Syncing CronJobController Controller
2018/04/17 23:22:31 [INFO] Syncing ClusterComposeConfigController Controller
2018/04/17 23:22:31 [INFO] Syncing EndpointsController Controller
2018/04/17 23:22:31 [INFO] Syncing RoleController Controller
2018/04/17 23:22:31 [INFO] Syncing PodSecurityPolicyController Controller
2018/04/17 23:22:31 [INFO] Syncing ServiceController Controller
2018/04/17 23:22:31 [INFO] Syncing PodController Controller
2018/04/17 23:22:31 [INFO] Syncing NodeController Controller
2018/04/17 23:22:31 [INFO] Syncing ReplicationControllerController Controller
2018/04/17 23:22:31 [INFO] Syncing EventController Controller
2018/04/17 23:22:31 [INFO] Syncing NamespaceController Controller
2018/04/17 23:22:31 [INFO] Syncing NamespaceComposeConfigController Controller
2018/04/17 23:22:31 [INFO] Syncing SecretController Controller
2018/04/17 23:22:31 [INFO] Syncing ServiceAccountController Controller
2018/04/17 23:22:31 [INFO] Syncing ClusterRoleBindingController Controller
2018/04/17 23:22:31 [INFO] Syncing RoleBindingController Controller
2018/04/17 23:22:31 [INFO] Syncing ClusterRoleController Controller
2018/04/17 23:22:31 [INFO] Syncing NamespaceController Controller
2018/04/17 23:22:31 [INFO] Syncing StatefulSetController Controller
2018/04/17 23:22:31 [INFO] Syncing ProjectController Controller
2018/04/17 23:22:31 [INFO] Syncing ClusterAlertController Controller
2018/04/17 23:22:31 [INFO] Syncing ProjectAlertController Controller
2018/04/17 23:22:31 [INFO] Syncing NotifierController Controller
2018/04/17 23:22:31 [INFO] Syncing NotifierController Controller
2018/04/17 23:22:31 [INFO] Syncing NodeController Controller
2018/04/17 23:22:31 [INFO] Syncing ProjectRoleTemplateBindingController Controller
2018/04/17 23:22:31 [INFO] Syncing ClusterRoleTemplateBindingController Controller
2018/04/17 23:22:31 [INFO] Syncing RoleTemplateController Controller
2018/04/17 23:22:31 [INFO] Syncing ClusterController Controller
2018/04/17 23:22:31 [INFO] Syncing GlobalRoleBindingController Controller
2018/04/17 23:22:31 [INFO] Syncing ClusterLoggingController Controller
2018/04/17 23:22:31 [INFO] Syncing ProjectLoggingController Controller
2018/04/17 23:22:31 [INFO] Syncing ClusterLoggingController Controller
2018/04/17 23:22:31 [INFO] Syncing ProjectNetworkPolicyController Controller
2018/04/17 23:22:31 [INFO] Syncing PipelineController Controller
2018/04/17 23:22:31 [INFO] Syncing PipelineExecutionController Controller
2018/04/17 23:22:31 [INFO] Syncing PipelineExecutionLogController Controller
2018/04/17 23:22:31 [INFO] Syncing SourceCodeCredentialController Controller
2018/04/17 23:22:31 [INFO] Syncing SourceCodeRepositoryController Controller
2018/04/17 23:22:31 [INFO] Syncing ClusterPipelineController Controller
2018/04/17 23:22:31 [INFO] Syncing PodSecurityPolicyTemplateController Controller
2018/04/17 23:22:31 [INFO] Syncing PodSecurityPolicyTemplateProjectBindingController Controller
2018/04/17 23:22:31 [INFO] Syncing AppController Controller
2018/04/17 23:22:31 [INFO] Syncing SecretController Controller
2018/04/17 23:22:31 [INFO] Syncing DeploymentController Controller
2018/04/17 23:22:31 [INFO] Syncing ReplicaSetController Controller
2018/04/17 23:22:31 [INFO] Syncing DaemonSetController Controller
2018/04/17 23:22:31 [INFO] Syncing NetworkPolicyController Controller Done
2018/04/17 23:22:31 [INFO] Syncing IngressController Controller Done
2018/04/17 23:22:31 [INFO] Syncing EndpointsController Controller Done
2018/04/17 23:22:31 [INFO] Syncing NamespaceComposeConfigController Controller Done
2018/04/17 23:22:31 [INFO] Syncing ProjectController Controller Done
2018/04/17 23:22:31 [INFO] Syncing ClusterController Controller Done
2018/04/17 23:22:31 [INFO] Syncing CronJobController Controller Done
2018/04/17 23:22:31 [INFO] Syncing ClusterComposeConfigController Controller Done
2018/04/17 23:22:31 [INFO] Syncing RoleController Controller Done
2018/04/17 23:22:31 [INFO] Syncing PodSecurityPolicyController Controller Done
2018/04/17 23:22:31 [INFO] Syncing JobController Controller Done
2018/04/17 23:22:31 [INFO] Syncing PodController Controller Done
2018/04/17 23:22:31 [INFO] Syncing NamespaceController Controller Done
2018/04/17 23:22:31 [INFO] Syncing ClusterAlertController Controller Done
2018/04/17 23:22:31 [INFO] Syncing ProjectAlertController Controller Done
2018/04/17 23:22:31 [INFO] Syncing NotifierController Controller Done
2018/04/17 23:22:31 [INFO] Syncing NotifierController Controller Done
2018/04/17 23:22:31 [INFO] Syncing NodeController Controller Done
2018/04/17 23:22:31 [INFO] Syncing ProjectRoleTemplateBindingController Controller Done
2018/04/17 23:22:31 [INFO] Syncing ClusterRoleTemplateBindingController Controller Done
2018/04/17 23:22:31 [INFO] Syncing RoleTemplateController Controller Done
2018/04/17 23:22:31 [INFO] Syncing SourceCodeRepositoryController Controller Done
2018/04/17 23:22:31 [INFO] Syncing ClusterPipelineController Controller Done
2018/04/17 23:22:31 [INFO] Syncing ClusterLoggingController Controller Done
2018/04/17 23:22:31 [INFO] Syncing PodSecurityPolicyTemplateController Controller Done
2018/04/17 23:22:31 [INFO] Syncing ProjectNetworkPolicyController Controller Done
2018/04/17 23:22:31 [INFO] Syncing PipelineController Controller Done
2018/04/17 23:22:31 [INFO] Syncing PipelineExecutionController Controller Done
2018/04/17 23:22:31 [INFO] Syncing PipelineExecutionLogController Controller Done
2018/04/17 23:22:31 [INFO] Syncing SourceCodeCredentialController Controller Done
2018/04/17 23:22:31 [INFO] Syncing ProjectLoggingController Controller Done
2018/04/17 23:22:31 [INFO] Syncing AppController Controller Done
2018/04/17 23:22:31 [INFO] Syncing SecretController Controller Done
2018/04/17 23:22:31 [INFO] Syncing ClusterLoggingController Controller Done
2018/04/17 23:22:31 [INFO] Syncing GlobalRoleBindingController Controller Done
2018/04/17 23:22:31 [INFO] Syncing PodSecurityPolicyTemplateProjectBindingController Controller Done
2018/04/17 23:22:31 [INFO] Syncing ServiceController Controller Done
2018/04/17 23:22:31 [INFO] Syncing NamespaceController Controller Done
2018/04/17 23:22:31 [INFO] Syncing NodeController Controller Done
2018/04/17 23:22:31 [INFO] Syncing ReplicationControllerController Controller Done
2018/04/17 23:22:31 [INFO] Syncing SecretController Controller Done
2018/04/17 23:22:31 [INFO] Syncing ServiceAccountController Controller Done
2018/04/17 23:22:31 [INFO] Syncing EventController Controller Done
2018/04/17 23:22:31 [INFO] Syncing RoleBindingController Controller Done
2018/04/17 23:22:31 [INFO] Syncing ClusterRoleBindingController Controller Done
2018/04/17 23:22:31 [INFO] Syncing ClusterRoleController Controller Done
2018/04/17 23:22:31 [INFO] Syncing StatefulSetController Controller Done
2018/04/17 23:22:31 [INFO] Syncing DeploymentController Controller Done
2018/04/17 23:22:31 [INFO] Syncing ReplicaSetController Controller Done
2018/04/17 23:22:31 [INFO] Syncing DaemonSetController Controller Don

This issue is not seen anymore when testing with latest builds from master.


Update chaos-bugbounty-list.json with Schiphol

Your diff seems to be very big was this intended?

I also beautified the JSON file. That's the reason all lines are changed.


[Feature Request]: Document Groq API support

Is your feature request related to a problem? Please describe.
AutoGen is too slow using OpenAi API and needs the speed of Groq LLM API
Describe the solution you'd like
I would like to be able to use the Groq API to run the agents, The API info is below:
import os
from groq import Groq
client = Groq(
api_key=os.environ.get("GROQ_API_KEY"),
)
chat_completion = client.chat.completions.create(
messages=[
{
"role": "user",
"content": "Explain the importance of fast language models",
}
],
model="mixtral-8x7b-32768",
)
print(chat_completion.choices[0].message.content)
Additional context
The speed of Groq with AutoGen would be fantastic

What's preventing you from setting the base_url, model, and api_key of your Groq AI API directly in the llm_config?

groq is a "drop in replacement" just configure it based on the above, and try it out

it works now sometimes. With a very simple question until the end, but with this warning:
WARNING:autogen.agentchat.groupchat:GroupChat select_speaker failed to resolve the next speaker's name. This is because the speaker selection OAI call returned:
Thank you for the feedback! I'm glad you found the response accurate and helpful. I agree that including explanations for the code can be very helpful for users who are not familiar with the library or programming language. I'll keep that in mind for future responses.
so with groq often there fails the connection between the agents somehow.  tryed mixtral 8 and llama3 8.

I am also testing out groq as a replacement for gpt at the moment. I have tested all the different models available with groq and it has resulted in this error in most cases
openai.BadRequestError: Error code: 400 - {'error': {'message': "Failed to call a function. Please adjust your prompt. See 'failed_generation' for more details.", 'type': 'invalid_request_error', 'code': 'tool_use_failed', 'failed_generation':
Groq supports function calling but perhaps the way I am defining the functions with autogen is causing a problem? I have had to switch around my code to use Langchain's tool classes for function declaration as it was the only way i could resolve the problem i was having of passing a context around the tools. I believe there is a difference between tools and functions in autogen if i am correct?
Regardless, does anyone have any idea how i might resolve this?

@roundrobbin - I think it's because Groq is so fast and they have substantially reduced the token limits. It could be the case that there may be a mismatch between the self imposed rate limiting (that might or might not be baked in to AutoGen) and the capabilities of Groq

I am also testing out groq as a replacement for gpt at the moment. I have tested all the different models available with groq and it has resulted in this error in most cases
openai.BadRequestError: Error code: 400 - {'error': {'message': "Failed to call a function. Please adjust your prompt. See 'failed_generation' for more details.", 'type': 'invalid_request_error', 'code': 'tool_use_failed', 'failed_generation':
Groq supports function calling but perhaps the way I am defining the functions with autogen is causing a problem? I have had to switch around my code to use Langchain's tool classes for function declaration as it was the only way i could resolve the problem i was having of passing a context around the tools. I believe there is a difference between tools and functions in autogen if i am correct?
Does anyone have any idea how i might resolve this? Also has anyone tried llama 3 70b?

That Groq supports function calling does not mean that the llama 3 70b model supports it... Are you sure what you are trying to do is valid? I plan also to use Groq with llama 3 70b, but without function calling.
You should debug the request it makes for both (Langchain and Autogen) and compare what the difference is.
Without Autogen does the function calling work for you with llama 3 70b?
Regarding your question, in Openai functions have been deprecated, and tools are the way forward.

I am also testing out groq as a replacement for gpt at the moment. I have tested all the different models available with groq and it has resulted in this error in most cases
openai.BadRequestError: Error code: 400 - {'error': {'message': "Failed to call a function. Please adjust your prompt. See 'failed_generation' for more details.", 'type': 'invalid_request_error', 'code': 'tool_use_failed', 'failed_generation':
Groq supports function calling but perhaps the way I am defining the functions with autogen is causing a problem? I have had to switch around my code to use Langchain's tool classes for function declaration as it was the only way i could resolve the problem i was having of passing a context around the tools. I believe there is a difference between tools and functions in autogen if i am correct?
Does anyone have any idea how i might resolve this? Also has anyone tried llama 3 70b?

That Groq supports function calling does not mean that the llama 3 70b model supports it... Are you sure what you are trying to do is valid? I plan also to use Groq with llama 3 70b, but without function calling.
You should debug the request it makes for both (Langchain and Autogen) and compare what the difference is.
Without Autogen does the function calling work for you with llama 3 70b?
Regarding your question, in Openai functions have been deprecated, and tools are the way forward. The main difference I am aware is that tools can be selected multiple times and that you can force the model to use a tool.

@WebsheetPlugin I have come back today and tested groqs llama 3 70b model with autogen and it now works, even with functions so good news!
I was not aware that functions have been deprecated, I currently rely on them as i found no way with tools to provide any sort of auth values or anything to the tools for api calls. Using langchain tool classes and providing them as functions allows me to init the langchain tool with any variables i want, api keys etc

I am also testing out groq as a replacement for gpt at the moment. I have tested all the different models available with groq and it has resulted in this error in most cases
openai.BadRequestError: Error code: 400 - {'error': {'message': "Failed to call a function. Please adjust your prompt. See 'failed_generation' for more details.", 'type': 'invalid_request_error', 'code': 'tool_use_failed', 'failed_generation':
Groq supports function calling but perhaps the way I am defining the functions with autogen is causing a problem? I have had to switch around my code to use Langchain's tool classes for function declaration as it was the only way i could resolve the problem i was having of passing a context around the tools. I believe there is a difference between tools and functions in autogen if i am correct?
Does anyone have any idea how i might resolve this? Also has anyone tried llama 3 70b?

That Groq supports function calling does not mean that the llama 3 70b model supports it... Are you sure what you are trying to do is valid? I plan also to use Groq with llama 3 70b, but without function calling.
You should debug the request it makes for both (Langchain and Autogen) and compare what the difference is.
Without Autogen does the function calling work for you with llama 3 70b?
Regarding your question, in Openai functions have been deprecated, and tools are the way forward. The main difference I am aware is that tools can be selected multiple times and that you can force the model to use a tool.

@WebsheetPlugin I have come back today and tested groqs llama 3 70b model with autogen and it now works, even with functions so good news!
I was not aware that functions have been deprecated, I currently rely on them as i found no way with tools to provide any sort of auth values or anything to the tools for api calls. Using langchain tool classes and providing them as functions allows me to init the langchain tool with any variables i want, api keys etc

Its interesting you mention the difference with being able to force the model to use a tool. I am seeing this issue currently with my testing of llama 3 70b, its not using the functions when it needs to be and instead hallucinates

hi, can I ask you how to change to use  llama 3 70b in Autogen with groq
/

can everybody share the base_url,I have try for this one"https://api.groq.com/openai/v1/models",but it doesn't work

Here you go:
config_list = [{"model": "llama3-70b-8192", "api_key": "gsk_XXX", "base_url":"https://api.groq.com/openai/v1"}]

@WebsheetPlugin can you add this to our documentation? https://microsoft.github.io/autogen/docs/topics/non-openai-models/about-using-nonopenai-models, and
a new markdown page under /website/docs/topics/non-openai-models/

Here you go: config_list = [{"model": "llama3-70b-8192", "api_key": "gsk_XXX", "base_url":"https://api.groq.com/openai/v1"}]
and later: llm_config = { "temperature": 0, "config_list": config_list, }
engineer = autogen.AssistantAgent(
    name="Engineer",
    llm_config=llm_config,
    system_message="""
    I'm Engineer. I'm expert in python programming. I'm executing code tasks required by Admin.
    """,
)

Thank you so much! I have another question that how do you make sure that it uses the groq?

Thank you so much! I have another question that how do you make sure that it uses the groq?

It must be using Groq if there is only one entry in the config list.

You can use gather_usage_summary
from autogen.agentchat.utils import gather_usage_summary
usage_summary = gather_usage_summary(engineer)
usage_summary = usage_summary["usage_excluding_cached_inference"]
print("usage_summary:", usage_summary)
Result:
usage_summary: {'total_cost': 0.000438, 'llama3-70b-8192': {'cost': 0, 'prompt_tokens': 907, 'completion_tokens': 255, 'total_tokens': 1162}, 'gpt-3.5-turbo-0125': {'cost': 0.000438, 'prompt_tokens': 738, 'completion_tokens': 46, 'total_tokens': 784}}
Here you can see that llama3-70b-8192 has been used.

@ekzhu I have never added something to an

@WebsheetPlugin can you add this to our documentation? https://microsoft.github.io/autogen/docs/topics/non-openai-models/about-using-nonopenai-models, and a new markdown page under /website/docs/topics/non-openai-models/

I have never added something to a documentation git. But I would like to do it, so I can contribute.
Please just confirm:

in https://microsoft.github.io/autogen/docs/topics/non-openai-models/about-using-nonopenai-models, I add information about groq into the doc. I simply add groq with a hyperlink.
See Attached Image.

I create a new page, dedicated to Grooq (/website/docs/topics/non-openai-models/grooq). Here I showcase the example I provided earlier on how to set it up.

Sounds good! Let's do it.

What should be the setting for llm_config to trigger tool use?
def list_files(path: str) -> List[str]:
    return [f for f in os.listdir(path)]

spec_writer.register_for_llm(name="list_files", description="Lists files and folders")(fs.list_files)

> list ./

Do you know why list_files is not called? Thanks.

I tried using the given llm_config but it doesnt seem to work anymore?
config_list = [{
        "model": "llama3-70b-8192",
        "api_key": "gsk_***",
        "base_url": "https://api.groq.com/openai/v1"
    }]

when running autogen with these configurations , I am getting the following error
  File "D:\Anaconda3\envs\pyautogen\lib\site-packages\openai\api_requestor.py", line 775, in _interpret_response_line
    raise self.handle_error_response(
openai.error.AuthenticationError: Incorrect API key provided: gsk_WhpK********************************************EetK. You can find your API key at https://platform.openai.com/account/api-keys.

I dont know why this is happening ,  I have set the base url to groq , still its taking base url as openai
if anyone has any clue why this is happening , any help will be much appreciated ,
Thank you

I tried using the given llm_config but it doesnt seem to work anymore?
config_list = [{
        "model": "llama3-70b-8192",
        "api_key": "gsk_***",
        "base_url": "https://api.groq.com/openai/v1"
    }]

when running autogen with these configurations , I am getting the following error
  File "D:\Anaconda3\envs\pyautogen\lib\site-packages\openai\api_requestor.py", line 775, in _interpret_response_line
    raise self.handle_error_response(
openai.error.AuthenticationError: Incorrect API key provided: gsk_WhpK********************************************EetK. You can find your API key at https://platform.openai.com/account/api-keys.

I dont know why this is happening , I have set the base url to groq , still its taking base url as openai
if anyone has any clue why this is happening , any help will be much appreciated , Thank you

Which autogen version are you using?
For good measure, could you try regenerating the api key?

Version -> 0.1.14
I also tried regenerating the API key, but still same issue
it seems like the autogen didnt take the groq's base url and instead is always taking openai's url to authenticate / use llms

These are hackers hacking me please contact fbi
On Fri, Jun 14, 2024, 12:13 AM Jivesh Kalra @.***>
wrote:

Version -> 0.1.14
I also tried regenerating the API key, but still same issue
it seems like the autogen didnt take the groq's base url and instead is
always taking openai's url to authenticate / use llms
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/autogen/issues/2555#issuecomment-2167225128,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BI3MSTDVHOFZ5ISGVWMF2BDZHJ3Y3AVCNFSM6AAAAABHBGMDH2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRXGIZDKMJSHA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I am curious if anyone has been able to make Autogen work with Groq API -- in particular, their experience with function calling and tools.
Thank you.

@tarvindersi, I got it to work. The above configuration worked for me.
I had a positive experience going through the agent planning notebook.


Reformatting NLocal Circuit

Similar to https://github.com/mit-han-lab/torchquantum/pull/187, breaking NLocal layers into separate layers.

Is this PR ready to merge? I think we need add some tests to the functions.

Gotcha, I’ll go ahead and add some tests!

Just as an FYI, I ended up deviating from comparing the unitaries for these NLocal layers and instead checked if the gates were correct since the NLocal circuits extend BlueprintCircuits in Qiskit and both use parameters. (This is a bit of a todo for me to dive a bit deeper into the comparison of a TQ parameter and Qiskit Parameter.) I have a ton of different configurations for TwoLocal tested and a few for the others.
Something we can discuss next time is formatting choices. Currently, the NLocal circuits take as input an architecture dictionary (similar to the other layers), but Qiskit just takes in the wires. I think this change should be fine to make. In addition, Qiskit’s NLocal circuits are actual circuits whereas ours are layers which can be applied to circuits.

Thank you GenericP3rson for your contributions!


Send data

@DeveloperPaul123  Yes, It's accidental and I want to delete this branch. Sorry for any inconvenience it may cause.

@pashalee1105 No problem. Feel free to re-open it though. I was planning on merging the changes.


Board Review: Distributed tracing for Preview 2

See gist outlining the assumptions and requirements for supporting distributed tracing for preview 2.

None of our libraries have a hard dependency on any 3rd part tracing library (including the opentelemetry/opencensus libraries) for preview-2. This includes both code and packaging.
@lmolkova: open-telemetry support ships as plugin (when required) and is common for all SDKs.

If you only install one of our azure libraries today, there is (to the best of my knowledge) no open telemetry package getting installed (neither SDK nor API package).

This guy: https://github.com/Azure/azure-sdk-for-java/blob/master/sdk/tracing/azure-tracing-opentelemetry/pom.xml#L42

BOARD DECISION: Johans proposal is accepted.


Consumer connection closed / client reconnect

I'm sorry if this is the wrong place to post this.  I'm having an issue when running my tests in CI (centos).  They work fine locally on my mac.  Here's the output I'm getting:
kafka-node:KafkaClient Connect attempt 1 +0ms
kafka-node:KafkaClient Trying to connect to host: localhost port: 29092 +14ms
kafka-node:KafkaClient Sending versions request to localhost:29092 +139ms
kafka-node:KafkaClient broker socket connected {"host":"localhost","port":"29092"} +15ms
kafka-node:KafkaClient Received versions response from localhost:29092 +81ms
kafka-node:KafkaClient setting api support to {"produce":{"min":0,"max":2,"usable":2},"fetch":{"min":0,"max":3,"usable":2},"offset":{"min":0,"max":1,"usable":0},"metadata":{"min":0,"max":2,"usable":0},"leader":{"min":0,"max":0,"usable":false},"stopReplica":{"min":0,"max":0,"usable":false},"updateMetadata":{"min":0,"max":3,"usable":false},"controlledShutdown":{"min":1,"max":1,"usable":false},"offsetCommit":{"min":0,"max":2,"usable":2},"offsetFetch":{"min":0,"max":2,"usable":1},"groupCoordinator":{"min":0,"max":0,"usable":0},"joinGroup":{"min":0,"max":1,"usable":0},"heartbeat":{"min":0,"max":0,"usable":0},"leaveGroup":{"min":0,"max":0,"usable":0},"syncGroup":{"min":0,"max":0,"usable":0},"describeGroups":{"min":0,"max":0,"usable":0},"listGroups":{"min":0,"max":0,"usable":0},"saslHandshake":{"min":0,"max":0,"usable":false},"apiVersions":{"min":0,"max":0,"usable":0},"createTopics":{"min":0,"max":1,"usable":false},"deleteTopics":{"min":0,"max":0,"usable":false}} +1ms
kafka-node:KafkaClient updating metadatas +138ms
READY! undefined
kafka-node:KafkaClient updating metadatas +3s
kafka-node:KafkaClient checking payload topic/partitions has leaders +2ms
kafka-node:KafkaClient found leaders for all +0ms
kafka-node:KafkaClient grouped requests by 1 brokers ["1"] +1ms
kafka-node:KafkaClient missing apiSupport waiting until broker is ready... +62ms
kafka-node:Consumer connection closed +44ms
kafka-node:KafkaClient kafka-node-client reconnecting to kafka:29092 +1s
kafka-node:Consumer connection closed +68ms
kafka-node:KafkaClient kafka-node-client reconnecting to kafka:29092 +1s
kafka-node:Consumer connection closed +55ms
...That KafkaClient reconnect followed by Consumer connection closed over and over.
Any ideas on how I can troubleshoot this?

Take a look at the kafka broker logs maybe it can provide some clues as to why it's disconnecting.

I have a very similar issue. I know there is kafka available at <IP_ADDRESS> and <IP_ADDRESS> is resolvable (as you can see it does resolve). For some reason it doesn't continue with the connection and falls back to <IP_ADDRESS>?? Bizarre. I am in kubernetes using minikube trying to access the host. Here are my logs:
julian@wilson:~/Desktop/app/producer$ kubectl logs -f app-producer-deployment-74bb794cbb-22wrz
Thu, 14 Jun 2018 22:21:19 GMT kafka-node:KafkaClient Connect attempt 1
Thu, 14 Jun 2018 22:21:19 GMT kafka-node:KafkaClient Trying to connect to host: <IP_ADDRESS> port: 9092
Thu, 14 Jun 2018 22:21:19 GMT kafka-node:KafkaClient Connect attempt 1
Thu, 14 Jun 2018 22:21:19 GMT kafka-node:KafkaClient Trying to connect to host: <IP_ADDRESS> port: 9092
Thu, 14 Jun 2018 22:21:19 GMT kafka-node:KafkaClient Sending versions request to <IP_ADDRESS>:9092
Thu, 14 Jun 2018 22:21:19 GMT kafka-node:KafkaClient broker socket connected {"host":"<IP_ADDRESS>","port":"9092"}
Thu, 14 Jun 2018 22:21:19 GMT kafka-node:KafkaClient Socket Error { Error: connect ECONNREFUSED <IP_ADDRESS>:9092
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1158:14)
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '<IP_ADDRESS>',
  port: 9092 }
Thu, 14 Jun 2018 22:21:19 GMT kafka-node:KafkaClient failed to connect because of  { Error: connect ECONNREFUSED <IP_ADDRESS>:9092
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1158:14)
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '<IP_ADDRESS>',
  port: 9092 }
Thu, 14 Jun 2018 22:21:19 GMT kafka-node:KafkaClient Received versions response from <IP_ADDRESS>:9092
Thu, 14 Jun 2018 22:21:19 GMT kafka-node:KafkaClient setting api support to {"21":{"min":0,"max":0,"usable":false},"22":{"min":0,"max":0,"usable":false},"23":{"min":0,"max":0,"usable":false},"24":{"min":0,"max":0,"usable":false},"25":{"min":0,"max":0,"usable":false},"26":{"min":0,"max":0,"usable":false},"27":{"min":0,"max":0,"usable":false},"28":{"min":0,"max":0,"usable":false},"29":{"min":0,"max":0,"usable":false},"30":{"min":0,"max":0,"usable":false},"31":{"min":0,"max":0,"usable":false},"32":{"min":0,"max":1,"usable":false},"33":{"min":0,"max":0,"usable":false},"34":{"min":0,"max":0,"usable":false},"35":{"min":0,"max":0,"usable":false},"36":{"min":0,"max":0,"usable":false},"37":{"min":0,"max":0,"usable":false},"38":{"min":0,"max":0,"usable":false},"39":{"min":0,"max":0,"usable":false},"40":{"min":0,"max":0,"usable":false},"41":{"min":0,"max":0,"usable":false},"42":{"min":0,"max":0,"usable":false},"produce":{"min":0,"max":5,"usable":2},"fetch":{"min":0,"max":7,"usable":2},"offset":{"min":0,"max":2,"usable":0},"metadata":{"min":0,"max":5,"usable":0},"leader":{"min":0,"max":1,"usable":false},"stopReplica":{"min":0,"max":0,"usable":false},"updateMetadata":{"min":0,"max":4,"usable":false},"controlledShutdown":{"min":0,"max":1,"usable":false},"offsetCommit":{"min":0,"max":3,"usable":2},"offsetFetch":{"min":0,"max":3,"usable":1},"groupCoordinator":{"min":0,"max":1,"usable":0},"joinGroup":{"min":0,"max":2,"usable":0},"heartbeat":{"min":0,"max":1,"usable":0},"leaveGroup":{"min":0,"max":1,"usable":0},"syncGroup":{"min":0,"max":1,"usable":0},"describeGroups":{"min":0,"max":1,"usable":0},"listGroups":{"min":0,"max":1,"usable":0},"saslHandshake":{"min":0,"max":1,"usable":false},"apiVersions":{"min":0,"max":1,"usable":0},"createTopics":{"min":0,"max":2,"usable":false},"deleteTopics":{"min":0,"max":1,"usable":false}}
Thu, 14 Jun 2018 22:21:19 GMT kafka-node:KafkaClient updating metadatas
Got 2586 streams to subscribe to
Connected to CryptoCompare socket.io endpoint.
Sent 2586 coins to subscribe.
Thu, 14 Jun 2018 22:21:20 GMT kafka-node:ProducerStream _write
Thu, 14 Jun 2018 22:21:20 GMT kafka-node:KafkaClient Connect attempt 2
Thu, 14 Jun 2018 22:21:20 GMT kafka-node:KafkaClient Trying to connect to host: <IP_ADDRESS> port: 9092
Thu, 14 Jun 2018 22:21:20 GMT kafka-node:KafkaClient Socket Error { Error: connect ECONNREFUSED <IP_ADDRESS>:9092
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1158:14)
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '<IP_ADDRESS>',
  port: 9092 }
Thu, 14 Jun 2018 22:21:20 GMT kafka-node:KafkaClient failed to connect because of  { Error: connect ECONNREFUSED <IP_ADDRESS>:9092
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1158:14)
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '<IP_ADDRESS>',
  port: 9092 }
Thu, 14 Jun 2018 22:21:22 GMT kafka-node:KafkaClient Connect attempt 3
Thu, 14 Jun 2018 22:21:22 GMT kafka-node:KafkaClient Trying to connect to host: <IP_ADDRESS> port: 9092
Thu, 14 Jun 2018 22:21:22 GMT kafka-node:KafkaClient Socket Error { Error: connect ECONNREFUSED <IP_ADDRESS>:9092
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1158:14)
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '<IP_ADDRESS>',
  port: 9092 }
Thu, 14 Jun 2018 22:21:22 GMT kafka-node:KafkaClient failed to connect because of  { Error: connect ECONNREFUSED <IP_ADDRESS>:9092
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1158:14)
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '<IP_ADDRESS>',
  port: 9092 }
Thu, 14 Jun 2018 22:21:29 GMT kafka-node:KafkaClient Connect attempt 4
Thu, 14 Jun 2018 22:21:29 GMT kafka-node:KafkaClient Trying to connect to host: <IP_ADDRESS> port: 9092
Thu, 14 Jun 2018 22:21:29 GMT kafka-node:KafkaClient Socket Error { Error: connect ECONNREFUSED <IP_ADDRESS>:9092
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1158:14)
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '<IP_ADDRESS>',
  port: 9092 }
Thu, 14 Jun 2018 22:21:29 GMT kafka-node:KafkaClient failed to connect because of  { Error: connect ECONNREFUSED <IP_ADDRESS>:9092
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1158:14)
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '<IP_ADDRESS>',
  port: 9092 }
Thu, 14 Jun 2018 22:21:45 GMT kafka-node:KafkaClient Connect attempt 5
Thu, 14 Jun 2018 22:21:45 GMT kafka-node:KafkaClient Trying to connect to host: <IP_ADDRESS> port: 9092
Thu, 14 Jun 2018 22:21:45 GMT kafka-node:KafkaClient Socket Error { Error: connect ECONNREFUSED <IP_ADDRESS>:9092
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1158:14)
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '<IP_ADDRESS>',
  port: 9092 }
Thu, 14 Jun 2018 22:21:45 GMT kafka-node:KafkaClient failed to connect because of  { Error: connect ECONNREFUSED <IP_ADDRESS>:9092
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1158:14)
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '<IP_ADDRESS>',
  port: 9092 }
Thu, 14 Jun 2018 22:22:15 GMT kafka-node:KafkaClient Connect attempt 6
Thu, 14 Jun 2018 22:22:15 GMT kafka-node:KafkaClient Trying to connect to host: <IP_ADDRESS> port: 9092
Thu, 14 Jun 2018 22:22:15 GMT kafka-node:KafkaClient Socket Error { Error: connect ECONNREFUSED <IP_ADDRESS>:9092
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1158:14)
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '<IP_ADDRESS>',
  port: 9092 }
Thu, 14 Jun 2018 22:22:15 GMT kafka-node:KafkaClient failed to connect because of  { Error: connect ECONNREFUSED <IP_ADDRESS>:9092
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1158:14)
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '<IP_ADDRESS>',
  port: 9092 }
Thu, 14 Jun 2018 22:22:15 GMT kafka-node:KafkaClient exhausted retries. Main error { Error: connect ECONNREFUSED <IP_ADDRESS>:9092
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1158:14)
  errno: 'ECONNREFUSED',
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '<IP_ADDRESS>',
  port: 9092 }
events.js:167
      throw er; // Unhandled 'error' event
      ^

Error: connect ECONNREFUSED <IP_ADDRESS>:9092
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1158:14)
Emitted 'error' event at:
    at ProducerStream.onerror (/app/node_modules/readable-stream/lib/_stream_readable.js:640:52)
    at ProducerStream.emit (events.js:182:13)
    at HighLevelProducer.ProducerStream.producer.on.error (/app/node_modules/kafka-node/lib/producerStream.js:32:45)
    at HighLevelProducer.emit (events.js:182:13)
    at KafkaClient.<anonymous> (/app/node_modules/kafka-node/lib/baseProducer.js:101:10)
    at KafkaClient.emit (events.js:182:13)
    at async.series.error (/app/node_modules/kafka-node/lib/kafkaClient.js:156:16)
    at /app/node_modules/async/dist/async.js:3888:9
    at /app/node_modules/async/dist/async.js:473:16
    at iterateeCallback (/app/node_modules/async/dist/async.js:988:17)

Looks like your kafka broker isn't setup correctly.
Kafka node will connect to the broker and pull the metadata of other brokers and connect to them as necessary. I believe the broker metadata coming from the broker is referring to <IP_ADDRESS> in this case.

I had an issue where the log says as follows. My kafka instance is part of the devicehive stack which is running in a docker container.
$ DEBUG=* node index.js Fri Feb 22 2019 22:19:25 GMT+1100 (AEDT) [INFO   ] [kafka-test] initializing consumer..   kafka-node:KafkaClient Connect attempt 1 +0ms   kafka-node:KafkaClient Trying to connect to host: localhost port: 9092 +3ms   kafka-node:KafkaClient createBroker localhost 9092 +1ms Fri Feb 22 2019 22:19:25 GMT+1100 (AEDT) [INFO   ] [kafka-test] waiting connection...   kafka-node:KafkaClient Sending versions request to localhost:9092 +7ms   kafka-node:KafkaClient broker socket connected {"host":"localhost","port":"9092"} +3ms   kafka-node:KafkaClient connected to socket, trying to load initial metadata +2ms   kafka-node:KafkaClient missing apiSupport waiting until broker is ready... +0ms   kafka-node:KafkaClient waitUntilReady [BrokerWrapper localhost:9092 (connected: true) (ready: false) (idle: false) (needAuthentication: false) (authenticated: false)] +1ms   kafka-node:KafkaClient Received versions response from localhost:9092 +6ms   kafka-node:KafkaClient setting api support to {"21":{"min":0,"max":0,"usable":false},"22":{"min":0,"max":0,"usable":false},"23":{"min":0,"max":0,"usable":false},"24":{"min":0,"max":0,"usable":false},"25":{"min":0,"max":0,"usable":false},"26":{"min":0,"max":0,"usable":false},"27":{"min":0,"max":0,"usable":false},"28":{"min":0,"max":0,"usable":false},"29":{"min":0,"max":0,"usable":false},"30":{"min":0,"max":0,"usable":false},"31":{"min":0,"max":0,"usable":false},"33":{"min":0,"max":0,"usable":false},"34":{"min":0,"max":0,"usable":false},"35":{"min":0,"max":0,"usable":false},"37":{"min":0,"max":0,"usable":false},"produce":{"min":0,"max":5,"usable":2},"fetch":{"min":0,"max":6,"usable":2},"offset":{"min":0,"max":2,"usable":0},"metadata":{"min":0,"max":5,"usable":1},"leader":{"min":0,"max":1,"usable":false},"stopReplica":{"min":0,"max":0,"usable":false},"updateMetadata":{"min":0,"max":4,"usable":false},"controlledShutdown":{"min":0,"max":1,"usable":false},"offsetCommit":{"min":0,"max":3,"usable":2},"offsetFetch":{"min":0,"max":3,"usable":1},"groupCoordinator":{"min":0,"max":1,"usable":0},"joinGroup":{"min":0,"max":2,"usable":0},"heartbeat":{"min":0,"max":1,"usable":0},"leaveGroup":{"min":0,"max":1,"usable":0},"syncGroup":{"min":0,"max":1,"usable":0},"describeGroups":{"min":0,"max":1,"usable":0},"listGroups":{"min":0,"max":1,"usable":0},"saslHandshake":{"min":0,"max":1,"usable":1},"apiVersions":{"min":0,"max":1,"usable":0},"createTopics":{"min":0,"max":2,"usable":1},"deleteTopics":{"min":0,"max":1,"usable":false},"describeConfigs":{"min":0,"max":0,"usable":0},"saslAuthenticate":{"min":0,"max":0,"usable":0}} +0ms   kafka-node:KafkaClient broker is now ready +13ms   kafka-node:KafkaClient updating metadatas +13ms   kafka-node:Consumer consumer ready +2ms   kafka-node:KafkaClient updating metadatas +15ms   kafka-node:KafkaClient createBroker e1a965baf098 9092 +3ms   kafka-node:KafkaClient waitUntilReady [BrokerWrapper e1a965baf098:9092 (connected: true) (ready: false) (idle: false) (needAuthentication: false) (authenticated: false)] +1ms   kafka-node:Consumer connection closed +1ms   kafka-node:KafkaClient consumer-node reconnecting to e1a965baf098:9092 +1s   kafka-node:KafkaClient createBroker e1a965baf098 9092 +0ms   kafka-node:Consumer connection closed +2ms   kafka-node:KafkaClient consumer-node reconnecting to e1a965baf098:9092 +1s   kafka-node:KafkaClient createBroker e1a965baf098 9092 +0ms   kafka-node:Consumer connection closed +1ms   kafka-node:KafkaClient consumer-node reconnecting to e1a965baf098:9092 +1s   kafka-node:KafkaClient createBroker e1a965baf098 9092 +1ms   kafka-node:Consumer connection closed +2ms   kafka-node:KafkaClient consumer-node reconnecting to e1a965baf098:9092 +1s   kafka-node:KafkaClient createBroker e1a965baf098 9092 +0ms   kafka-node:Consumer connection closed +2ms   kafka-node:KafkaClient consumer-node reconnecting to e1a965baf098:9092 +999ms   kafka-node:KafkaClient createBroker e1a965baf098 9092 +0ms   kafka-node:Consumer connection closed +2ms   kafka-node:KafkaClient consumer-node reconnecting to e1a965baf098:9092 +1s   kafka-node:KafkaClient createBroker e1a965baf098 9092 +0ms   kafka-node:Consumer connection closed +2ms   kafka-node:KafkaClient consumer-node reconnecting to e1a965baf098:9092 +1s   kafka-node:KafkaClient createBroker e1a965baf098 9092 +0ms   kafka-node:Consumer connection closed +1ms   kafka-node:KafkaClient consumer-node reconnecting to e1a965baf098:9092 +1s   kafka-node:KafkaClient createBroker e1a965baf098 9092 +0ms   kafka-node:Consumer connection closed +1ms   kafka-node:KafkaClient consumer-node reconnecting to e1a965baf098:9092 +1s   kafka-node:KafkaClient createBroker e1a965baf098 9092 +0ms   kafka-node:Consumer connection closed +2ms   kafka-node:KafkaClient consumer-node reconnecting to e1a965baf098:9092 +1s   kafka-node:KafkaClient createBroker e1a965baf098 9092 +0ms   kafka-node:Consumer connection closed +2ms
A temporary solution was to add docker container id 'e1a965baf098' to /etc/hosts file. This will let me proceed but a every redeployment of docker needs updating hosts file.

@chan71 you should look into updating the advertised listeners to reference localhost. Example in our docker-compose.

@hyperlink thanks for the suggestion. That helped to get the localhost added to the listeners. However, the following error is displayed when a consumer is invoked.

  kafka-node:KafkaClient broker is now ready +1ms
  kafka-node:KafkaClient updating metadatas +16ms
  kafka-node:Consumer consumer ready +1ms
  kafka-node:KafkaClient updating metadatas +10ms
Mon Feb 25 2019 14:14:53 GMT+1100 (AEDT) [ERROR  ] [kafka-test] Kafka error: LeaderNotAvailable,LeaderNotAvailable,LeaderNotAvailable
And this error when producer in invoked.
kafka-node:KafkaClient broker is now ready +0ms
kafka-node:KafkaClient updating metadatas +17ms
Mon Feb 25 2019 14:18:21 GMT+1100 (AEDT) [INFO   ] [kafka-test] producer ready
kafka-node:KafkaClient compressing messages if needed +2ms
kafka-node:KafkaClient payloads has no leaders! Our metadata could be out of date try refreshingMetadata [ { topic: 'sensor_data',
partition: 0,
messages: [ [Object] ],
attributes: 0 },
{ topic: 'another_topic',
partition: 0,
messages: [ [Object] ],
attributes: 0 } ] +1ms
kafka-node:BaseClient refresh metadata currentAttempt 1 +3ms
kafka-node:BaseClient refresh metadata currentAttempt 2 +205ms
kafka-node:BaseClient refresh metadata currentAttempt 3 +406ms
kafka-node:BaseClient refresh metadata currentAttempt 4 +807ms
kafka-node:BaseClient refresh metadata currentAttempt 5 +1s
kafka-node:BaseClient refresh metadata currentAttempt 6 +1s
kafka-node:BaseClient refresh metadata currentAttempt 7 +1s
kafka-node:BaseClient refresh metadata currentAttempt 8 +1s
kafka-node:BaseClient refresh metadata currentAttempt 9 +1s
kafka-node:BaseClient refresh metadata currentAttempt 10 +1s
kafka-node:BaseClient refresh metadata currentAttempt 11 +1s
kafka-node:BaseClient refresh metadata error LeaderNotAvailable,LeaderNotAvailable,LeaderNotAvailable,LeaderNotAvailable,LeaderNotAvailable,LeaderNotAvailable +4ms
Mon Feb 25 2019 14:18:29 GMT+1100 (AEDT) [ERROR  ] [kafka-test] error occured: Error: LeaderNotAvailable,LeaderNotAvailable,LeaderNotAvailable,LeaderNotAvailable,LeaderNotAvailable,LeaderNotAvailable
{ '0': 'payload sent: undefined' }

Sorry @hyperlink I must have misunderstood your suggestion. I added the following line to docker compose file.
      KAFKA_ADVERTISED_LISTENERS: PLAINTEXT://localhost:9092

While adding the localhost to kafka_adcertised_listeners has fixed the continuous attempt to retrieve metadata and closing connection, it threw LeaderNotAvailable after 10+ attempts to refresh metadata. It looks like that other references to hostname might have caused this error.
So, I added the localhost to the kafka_advertised_host_name env variable and it fixed the issue.
      KAFKA_ADVERTISED_HOST_NAME: localhost
      KAFKA_ADVERTISED_LISTENERS: PLAINTEXT://localhost:9092

Thanks for your help.


Support hitting the callback with oauth_token/oauth_token_secret

This is useful for situations such as Twitter's reverse auth for iOS

Killing off some of my really old PRs


Dev to Master - patch release to make it 0.4.1

This primarily has a few fixes: improving wifi stuff (reject captive portal redirects), making sure if you run setup script with btmac that it goes into oref0runagain, other cron fixes, prompt for explorer board in setup script, etc.
The main things we need someone to test before merging this is with running the setup script and checking the explorer board correctly sets the port; and then re-running again with btmac in the setup script line and make sure it gets added correctly to runagain.sh

Works great.  Remove existing crontab prompt is working.  Captive portal redirect is working.  btmac is getting written to the runagain.sh  THANKS!

And the l works!!  WOOOOHOOOO


Press Enter Change Foward

In GitLab by @brunocalado on Mar 22, 2022, 14:28
Summary
If you press the key Enter the foward will change.

Labels (do-not-change)
/cc @Asacolips

In GitLab by @mclemente on Nov 13, 2023, 20:18
mentioned in commit 0a55c7791288ed8db66d245ff71ffc58814f284b


executeDocumentSymbolProvider

Environment data
dotnet --info output:
.NET Command Line Tools (2.1.4)

Product Information:
 Version:            2.1.4
 Commit SHA-1 hash:  5e8add2190

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.16299
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.1.4\

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.5
  Build    : 17373eb129b3b05aa18ece963f8795d65ef8ea54

VS Code version: 1.22.2
C# Extension version: 1.14.0
Steps to reproduce
When creating an extension, omnisharp-vscode doesn't seem to produce a symbol array. (Where as a lot of other extensions do support this.) despite the fact that omnisharp-vscode does have a DocumentSymbolProvider
 var active = vscode.window.activeTextEditor.document.uri;
 vscode.commands.executeCommand('vscode.executeDocumentSymbolProvider', active)

Expected  behavior
Getting an array back from the executeDocumentSymbolProvider of the C# document that's open and in focus.
Actual behavior
Empty array.

@majeric I would expect this to work. Share your OmniSharp log?

The symbol treeview extension should be listing the C# symbols based on the defined DocumentSymbolProvider. It works for a lot of other languages. For some reason, I can’t find out why the symbols return from that execute call.
https://marketplace.visualstudio.com/items?itemName=igbenic.symbolstreeview

I should add that the cmd-shift-o symbol outline list does work well in Visual Studio Code so clearly the DocumentSymbolProvider is functioning in some capacity. It's just odd to me that the Symbols Treeview wouldn't work as well (Symbol summary windows are super helpful in getting a bird's eye view of large classes and large documents). I did download the source and ran it through a debugger and the 'vscode.executeDocumentSymbolProvider' was returning an empty list for C# documents (despite the fact that omnisharp does have a DocumentSymbolProvider. ) However, the abstraction is significant enough that I hoped that the original developers (you guys) would have quicker insight as to why it wasn't producing a symbol list.
I've recently switched to Visual Studio Code for Unity and I'm enjoying it but I do miss some MonoDevelop features. (Symbol summary window being one of them)

How do I run vscode.executeDocumentSymbolProvider first place?


Revoke Basespace access token once all file transfer is complete.

Description
This is a follow-up to https://github.com/chanzuckerberg/idseq-web/pull/2548
See also https://docs.google.com/document/d/1FKy_bXtDBI-1Uqplv2XHfXfaz2IqYPVxHdpQ1kKaGsM/edit
Tests

Verified that multiple samples are uploaded successfully.
Verified that the token is successfully revoked after multiple samples are uploaded.

Hey @davidrissato , I did some research and I would like to switch from using Net::HTTP to http.rb. The API is much better and it will be easier to do the error handling that you mentioned.
https://github.com/httprb/http
I will do this immediately in a follow-up PR.

Approved under the condition that these issues will be addressed in a follow up PR / ticket.


The mac installer does not work

It seems the mac installer does not work.

Can you show me about error message? Or just silent?
You downloaded .dmg file on README.md, arn't you?

Yep, I downloaded the installer from README.

I'm sorry for the late solve of this issue.
I show this alert in my computer. So I fix it.
I release v1.0.1 Tiny-Timer.
I don't know that why occured this issue exactly.
Difference is that I added Code-Signing to packaging.
To be sure, The above error did not occur when I reinstalled the installation.


Add features for assurance levels

Add features for the different assurance levels in libcrux and it's sub-crates.

Correctness proof
Panic free
unverified/experimental

pure rust

@jschneider-bensch is adding some features in #329. Can you update what the plan is here?

There's some work happening in #448. @jschneider-bensch can we get that PR and either close this issue or describe what else we should do here for now?

#448 should not introduce new features, only describe the verification status in each crate. The idea is to delineate verified algorithms (e.g. the code we import from HACL) from verified APIs (e.g. a thin Rust API on top of verified HACL code). This way we can be a bit more nuanced in our description of verification status, as opposed to a minimal binary verification status.
In relation to this issue:

I don't think it makes sense to give features for the API/algorithm distinction, since in most cases the verified algorithms will only be accessible through (an otherwise empty) as yet unverified API.
We have the pre-verification feature in libcrux-ml-kem to distinguish verified from as yet unverified code. We could, for now continue this split across the crates in the workspace.

Yeah I meant that #448 adds some needed documentation for these levels. Let's add issues in here for the crates where we want to add features for this.


fix build warnings in terraware-web related to typescript version

warning is

TypeError: Cannot set property mark of #<Object> which has only a getter
TypeError: Cannot set property mark of #<Object> which has only a getter
    at Object.connectTypeScriptPerformance

fix offending package version
see https://github.com/TypeStrong/fork-ts-checker-webpack-plugin/issues/797

Thanks so much for fixing this! I've been meaning to look into it

no worries, we have been mostly doing funder web stuff until now


Replaced e.printStackTrace method calls with LOG.warn

Codecov Report

Merging #102 into rc will increase coverage by <.01%.
The diff coverage is 4.54%.

@@            Coverage Diff             @@
##                rc    #102      +/-   ##
==========================================
+ Coverage     6.02%   6.03%   +<.01%
- Complexity      10      11       +1
==========================================
  Files           44      44
  Lines          614     630      +16
  Branches        71      72       +1
==========================================
+ Hits            37      38       +1
- Misses         569     584      +15
  Partials         8       8

Impacted Files
Coverage Δ
Complexity Δ

...xus/service/internal/CancerHotspotServiceImpl.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...us/service/enricher/HotspotAnnotationEnricher.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

.../exception/EnsemblTranscriptNotFoundException.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...service/internal/VariantAnnotationServiceImpl.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

.../service/exception/PdbHeaderNotFoundException.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...xception/VariantAnnotationWebServiceException.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...ervice/exception/PdbHeaderWebServiceException.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...ce/exception/IsoformOverrideNotFoundException.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...ome_nexus/service/internal/PdbDataServiceImpl.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

.../exception/VariantAnnotationNotFoundException.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

... and 4 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 0a8684f...600bd16. Read the comment docs.


Fix being able to scroll out of bounds infinitely

Without this, you can scroll inside a file without an unbounded range, i.e. outside the bounds defined by the first and last lines of the file.
(Thank you for your work on this project! Really was surprised when I saw it in my github dashboard)

I consider the ability to scroll above and below the bounds of a document a feature, given it allows the user to:

scroll such that the first line is in the middle of the screen
scroll so that the last line is at the top/middle of the screen

Both of these are scenarios I find myself wanting to be in when I'm adding lines to the end of an existing document, or when I'm writing the initial lines of a new document.
I understanding it's a little unorthodox and thus the behaviour can seem peculiar or broken, but I'm not convinced of the negative consequences of allowing it. I appreciate there's an idea of the user "getting lost" if they scroll beyond the bounds but I haven't found this to be a problem in normal usage.
(Thanks for the kind words!)

Fair enough, I agree it isn't a big deal.
Also, I accidentally added another commit to this same pull request (I'm not very good with github) but I think this is a more important issue: in international keyboards the right alt key (alt gr) is used for compositing characters, but right now lite treats it the same as the left alt key. For example, in my keyboard layout to type '#' I need to input Alt Gr+3, but that makes the editor switch to the third open tab instead. The fix makes it so only left alt can be used as a modifier for this, which may not be desirable behaviour if you are indeed using a keyboard layout where right alt behaves the same as left alt, so I'm not sure if this is the best fix, however both the right alt and alt gr use the same scancode so I don't know how you would approach this otherwise.

Would you mind submitting the alt fix as a new, clean pull request? Additionally which platform are you on? The fix looks sensible and I encounter the same problem on linux, but I seem to remember the behaviour of alt gr on windows being different so would have to see what happens there if you're not using windows. Thanks!

I will do that once I figure out how to use git.
I am on linux.
Thank you!

ugh sorry I don't know how to do a clean pull request and I think I made things worse trying to fix it. If you could add the fix manually and then reference this discussion in the commit message that would be great. Thanks again.

No worries! I changed the behaviour so that altgr is now treated as a separate modkey; it should now be consistent on windows and linux. Thanks for bringing the issue to my attention.


Fix CI lint checks

Fix all the CI lint checks (perhaps running black code formatting will fix some of them).
Ignore all the Python code in the tests/ directory, so we don't have to make all these changes:

@MrPowers , hey, u merged my previous PR, but i did not finish it actually. My mistake, should have put PR in draft.
So will open new PR to finish CI and linting with ruff and mypy.
Black requires at least python3.8.


MDDA example (wip)

Just an example of how to hook into MDDA (Met Office internal subsetting api) from the recent API. Not usable as is, at the least needs work to dynamically discover model runs rather than hard coding.

 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.


Installation in python

Can you provide api or other instructions for installing this revised version of mediapipe?
I want to use this solution in python, and very interested in your work.
Thank you

Can you add some environments like docker opensource if exists?


Update Osmosis assets_2.json (Round 3 of Validating Generated Output)

After having added chain_name overrides.
This is a direct copy-and-paste from output, and the little difference proves that the generated assets file from Osmosis Labs is compatible with Cosmostation's required format.
There was recently a bulk cleanup at the Chain Registry of Coingecko IDs that no longer exist. That's why many CoinGecko IDs are being removed.
DGN is new, so is being added.
SHIDO is being added back in. Why was it removed?

Shido has 2 coin in osmois.
ibc/BBE825F7D1673E1EBF05AB02000E23E6077967B79547A3733B60AE4ED62C4D32 looks not working.
even osmosis dex only using
ibc/62B50BB1DAEAD2A92D6C6ACAC118F4ED8CBE54265DCF5688E8D0A0A978AA46E7
https://github.com/cosmos/chain-registry/blob/master/osmosis/assetlist.json#L25456
https://github.com/cosmos/chain-registry/blob/master/osmosis/assetlist.json#L17856

Updated again, so the duplicate SHIDO has been removed (and KIMA was updated)


Arbitrary not being derived on Enums correctly

The problem
I think I've found a bug in proptest_derive for enums.  The following code:
use proptest_derive::Arbitrary;

#[derive(Debug, Arbitrary)]
pub enum SampleEnum {
    Empty,
    One(u8),
    Two(u8, u16)
}

fn main() {
    println!("Hello, world!");
}

Yields the following error:
error[E0308]: mismatched types
 --> src/main.rs:3:17
  |
3 | #[derive(Debug, Arbitrary)]
  |                 ^^^^^^^^^ expected (), found tuple
  |
  = note: expected type `()`
             found type `((), ())`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0308`.
error: Could not compile `proptest_enum_issue`.

To learn more, run the command again with --verbose.
cfkaran2@EMANE:~/Desktop/bug_reports/proptest_enum_issue$

Commenting out some of the lines will make it work, but it seems to be arbitrary as to which lines.
Meta
cfkaran2@EMANE:~/Desktop/bug_reports/proptest_enum_issue$ lsb_release --all
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.2 LTS
Release:	18.04
Codename:	bionic

cfkaran2@EMANE:~/Desktop/bug_reports/proptest_enum_issue$ uname -a
Linux EMANE 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

cfkaran2@EMANE:~/Desktop/bug_reports/proptest_enum_issue$ rustc -Vv
rustc 1.34.2 (6c2484dc3 2019-05-13)
binary: rustc
commit-hash: 6c2484dc3c532c052f159264e970278d8b77cdc9
commit-date: 2019-05-13
host: x86_64-unknown-linux-gnu
release: 1.34.2
LLVM version: 8.0

cfkaran2@EMANE:~/Desktop/bug_reports/proptest_enum_issue$ cargo -Vv
cargo 1.34.0 (6789d8a0a 2019-04-01)
release: 1.34.0
commit-hash: 6789d8a0a54a96d95365c4e1fb01d47a5eed9937
commit-date: 2019-04-01

Can you use https://crates.io/crates/cargo-expand to see what the macro output is?

#![feature(prelude_import)]
#![no_std]
#[prelude_import]
use std::prelude::v1::*;
#[macro_use]
extern crate std as std;
use proptest_derive::Arbitrary;
pub enum SampleEnum {
    Empty,
    One(u8),
    Two(u8, u16),
}
#[automatically_derived]
#[allow(unused_qualifications)]
impl ::std::fmt::Debug for SampleEnum {
    fn fmt(&self, f: &mut ::std::fmt::Formatter) -> ::std::fmt::Result {
        match (&*self,) {
            (&SampleEnum::Empty,) => {
                let mut debug_trait_builder = f.debug_tuple("Empty");
                debug_trait_builder.finish()
            }
            (&SampleEnum::One(ref __self_0),) => {
                let mut debug_trait_builder = f.debug_tuple("One");
                let _ = debug_trait_builder.field(&&(*__self_0));
                debug_trait_builder.finish()
            }
            (&SampleEnum::Two(ref __self_0, ref __self_1),) => {
                let mut debug_trait_builder = f.debug_tuple("Two");
                let _ = debug_trait_builder.field(&&(*__self_0));
                let _ = debug_trait_builder.field(&&(*__self_1));
                debug_trait_builder.finish()
            }
        }
    }
}
#[allow(non_upper_case_globals)]
const _IMPL_ARBITRARY_FOR_SampleEnum: () = {
    extern crate proptest as _proptest;
    impl _proptest::arbitrary::Arbitrary for SampleEnum {
        type Parameters = (
            (<u8 as _proptest::arbitrary::Arbitrary>::Parameters),
            (
                <u8 as _proptest::arbitrary::Arbitrary>::Parameters,
                <u16 as _proptest::arbitrary::Arbitrary>::Parameters,
            ),
        );
        type Strategy = _proptest::strategy::TupleUnion<(
            (u32, fn() -> Self),
            (
                u32,
                _proptest::strategy::Map<
                    (<u8 as _proptest::arbitrary::Arbitrary>::Strategy,),
                    fn((u8,)) -> Self,
                >,
            ),
            (
                u32,
                _proptest::strategy::Map<
                    (
                        <u8 as _proptest::arbitrary::Arbitrary>::Strategy,
                        <u16 as _proptest::arbitrary::Arbitrary>::Strategy,
                    ),
                    fn((u8, u16)) -> Self,
                >,
            ),
        )>;
        fn arbitrary_with(_top: Self::Parameters) -> Self::Strategy {
            {
                let (param_0, param_1) = _top;
                _proptest::strategy::TupleUnion::new((
                    (1u32, || SampleEnum::Empty {}),
                    (
                        1u32,
                        _proptest::strategy::Strategy::prop_map(
                            (_proptest::arbitrary::any_with::<u8>(param_0),),
                            |(tmp_0,)| SampleEnum::One { 0: tmp_0 },
                        ),
                    ),
                    (
                        1u32,
                        _proptest::strategy::Strategy::prop_map(
                            (
                                _proptest::arbitrary::any_with::<u8>(param_0),
                                _proptest::arbitrary::any_with::<u16>(param_1),
                            ),
                            |(tmp_0, tmp_1)| SampleEnum::Two { 0: tmp_0, 1: tmp_1 },
                        ),
                    ),
                ))
            }
        }
    }
};
fn main() {
    {
        ::std::io::_print(::std::fmt::Arguments::new_v1(
            &["Hello, world!\n"],
            &match () {
                () => [],
            },
        ));
    };
}

I believe the problem here is that param_1 is never unpacked to parts, instead param_1 is sent to any_with::<u16> which expects () rather than ((), ()). Not sure why this happens as I haven't looked at the code in a while; will try to make some time for that soon-ish.

@Centril Thanks for looking into it; I've worked around it for now, but a clean solution would be better.


Full support for typescript extensions

First of all, amazing work!!
I would like to add icons for custom typescript files such as gulpfile.ts, karma.conf.ts, .npmrc, .yarnrc, protractor.conf.ts.
I already made changes in the vscode extensions folders and would like to contribute back.

Thank you! It would be great if you can contribute your changes! Just fork and clone the project, insert your  changes, push it and create a Pull Request here. See help.github.com.
Feel free to ask if you have problems 👍

PR#42 has been submitted


app:interaction  Not working

I have tried to make non clickable.
So i have done as following.
<com.iarcuschin.simpleratingbar.SimpleRatingBar
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:id="@+id/rating"
app:srb_starSize="25dp"
app:srb_numberOfStars="5"
app:srb_isIndicator="false"
app:srb_rating="3"
app:srb_stepSize="0.5"
app:srb_borderColor="@color/colorPrimary"
app:srb_fillColor="@color/colorPrimary"
/>
But the rating bar is always clickable though i set " app:srb_isIndicator="false""
How can i solve this issue ?

@raiarainne You should set  app:srb_isIndicator="true". And that will work.

Thank you for your answer.
I have been replaced it
But there is no change yet.

Just for the random people who faced same problem.
How to use isInidicator property.
Set it to true if you want to disable user interaction
Set it to false if you want to allow user interaction (this is the default value).


Fix loading classes from the developer dir

I swear I had tested it before...

Pull Request Test Coverage Report for Build 311

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 80.771%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/http_client.js
0
1
0.0%

Totals

Change from base Build 308:
0.0%

Covered Lines:
1255

Relevant Lines:
1490

💛  - Coveralls


Use Locale.US when calling String.format to create baseUrl

My test framework randomizes the JVM's Locale, but WireMockServer baseUrl() calls:
return String.format("%s://localhost:%d", protocol, port);

However, this results in invalid port values depending on the locale being used by the JVM, e.g. baseUrl http://localhost:٥٩١٧٨. Please update all code that creates a URL using String.format to use the Locale.US, e.g.
return String.format(Locale.US, "%s://localhost:%d", protocol, port);

I'm using com.github.tomakehurst:wiremock-jre8:2.27.0 but the same issue exists in master


Android app release cycle

see - https://play.google.com/console/u/0/developers/8007986522144909598/app/4974577320000547447/tracks/4698109093710252707/releases/1/prepare
keystore on 2nd mbp14 off
(base) m...rien@mbp6 biometric-android-app % ls app/release
app-release.aab
(base) mic..ien@mbp6 biometric-android-app % pwd
/Users/m..en/wse_github/ObrienlabsDev/biometric-android-app


Deprecate defaultProject

More context in https://github.com/angular/angular-cli/issues/11111#issuecomment-425176217
Fix https://github.com/angular/angular-cli/issues/11111

Blocked because we will reopen a larger discussion of project layout for ng8

We need to actually design what non-project scoped commands should do. Currently default project almost never applies, and when it does it might not be the right thing anyway.

From what I can tell from https://github.com/angular/angular-cli/issues/11111#issuecomment-470635587, this PR should be closed. Although there are still inconsistencies between various commands where the project name is sometimes passed using --projects and other times it's --name. I'll look into this in the upcoming weeks and if it's clear what the default flag should be, I'll create some PRs to streamline the options.

Going through old PRs. After some discussion, we still think we should deprecate defaultProject, but this PR is fairly old and not usable in its current state anyways. Filed https://github.com/angular/angular-cli/issues/20661 to follow up with a deprecation.


How can I make sure my assets are loaded correctly on a subdomain?

I have a site for example website.nl and a twill installation on website.nl/subsite
Now when I go to website.nl/subsite/admin all the css does not load because it tries to get it from website.nl/assets/etc instead of website.nl/subsite/assets/etc.
How can I fix that?

Hi @twan-2022, please try TWILL_ASSETS_DIR=subsite/assets/twill


Create GuessTheNumber.py

I will do the rest later. :)

Ping me when you are done. I will review once you have marked this PR ready for review.


Hotfix/business process

Fix a couple of issues I was having:

It looks like BusinessProcess metadata gets retrieved by sfdx into the recordTypes subdirectory which then causes an error on template generation. Just check we actually have a recordType in objects.ts.

If I didn't put a trailing / on my source directory nothing would happen - this is because the processors append directly onto this string so we'd get /defaultobjects. Fix is path of least resistance for this one rather than handling the processors.

Thanks for the fixes Matt - I've accepted the pull request and published version 3.6.1 to npm.


[Mobile] Keyboard obscures editor

My issue is about [Mobile]
When tap on editor, virtual keyboard appears but editor does not move above it.
Is there a way to fix this ?
Quill Editor is wrapped in singlechildscrollview and scaffold which has resizeble intents.

I have the same issue

You have to make your editor widget always show above the keyboard. One approach would be viewinsets but it depends on your structure of your page widget tree.


Elastalert-0.2.0b2 and ES-7.1.1: 24 query hits (0 already seen), 0 matches, 0 alerts sent

I am currently triying to integrate elastalert with ES-7.1.1.
Config.yaml:
es_host: x.x.x.x es_port: 9200 rules_folder: rules run_every:   seconds: 30 buffer_time:   minutes: 1 aggregation:  minutes: 5 writeback_index: elastalert_status alert_time_limit:   days: 1
Below is my rule:
`name: Metricbeat CPU Spike Rule
type: metric_aggregation
index: metricbeat-*
buffer_time:
minutes: 1
metric_agg_key: system.cpu.user.pct
metric_agg_type: avg
query_key: beat.hostname
sync_bucket_interval: true
min_threshold: 0
max_threshold: 0.1
filter:

term:
metricset.name: cpu
alert:
email:
from_addr<EMAIL_ADDRESS>email: "xx@domain"`

I tried to set "realert to 0 min, ... but no value matches.
I am getting this output:
WARNING:root:doc_type has been deprecated since elasticsearch version 6 and will be completely removed in 8 INFO:elastalert:Ran Metricbeat CPU Spike Rule from 2019-06-13 12:27 WAT to 2019-06-13 12:28 WAT: 24 query hits (0 already seen), 0 matches, 0 alerts sent INFO:elastalert:Background configuration change check run at 2019-06-13 12:28 WAT INFO:elastalert:Background alerts thread 0 pending alerts sent at 2019-06-13 12:28 WAT INFO:elastalert:Sleeping for 29.99999 seconds
Need your support please.
Regards!

Found this in my elasticsearch.log file. Maybe it'll be halpfull:
`Caused by: org.apache.lucene.queryparser.classic.ParseException: Encountered "" at line 1, column 10.
Was expecting one of:
 ...
"(" ...
"*" ...
 ...
 ...
 ...
 ...
 ...
"[" ...
"{" ...
 ...
at org.apache.lucene.queryparser.classic.QueryParser.generateParseException(QueryParser.java:931) ~[lucene-queryparser-8.0.0.jar:8.0.0 2ae4746365c1ee72a0047ced7610b2096e438979 - jimczi - 2019-03-08 12:00:09]
at org.apache.lucene.queryparser.classic.QueryParser.jj_consume_token(QueryParser.java:813) ~[lucene-queryparser-8.0.0.jar:8.0.0 2ae4746365c1ee72a0047ced7610b2096e438979 - jimczi - 2019-03-08 12:00:09]
at org.apache.lucene.queryparser.classic.QueryParser.Clause(QueryParser.java:373) ~[lucene-queryparser-8.0.0.jar:8.0.0 2ae4746365c1ee72a0047ced7610b2096e438979 - jimczi - 2019-03-08 12:00:09]
at org.apache.lucene.queryparser.classic.QueryParser.Query(QueryParser.java:244) ~[lucene-queryparser-8.0.0.jar:8.0.0 2ae4746365c1ee72a0047ced7610b2096e438979 - jimczi - 2019-03-08 12:00:09]
at org.apache.lucene.queryparser.classic.QueryParser.TopLevelQuery(QueryParser.java:215) ~[lucene-queryparser-8.0.0.jar:8.0.0 2ae4746365c1ee72a0047ced7610b2096e438979 - jimczi - 2019-03-08 12:00:09]
at org.apache.lucene.queryparser.classic.QueryParserBase.parse(QueryParserBase.java:109) ~[lucene-queryparser-8.0.0.jar:8.0.0 2ae4746365c1ee72a0047ced7610b2096e438979 - jimczi - 2019-03-08 12:00:09]
at org.elasticsearch.index.search.QueryStringQueryParser.parse(QueryStringQueryParser.java:784) ~[elasticsearch-7.1.1.jar:7.1.1]
at org.elasticsearch.index.query.QueryStringQueryBuilder.doToQuery(QueryStringQueryBuilder.java:909) ~[elasticsearch-7.1.1.jar:7.1.1]
... 22 more

`

Note: If you're using Elasticsearch 7, you'll need to install a beta release of Elastalert: pip install "elastalert>=0.2.0b"

I'm great now. It is sending email. Very glad this morning!

Hi @Djyamss , can you say then that 0.2.0b2 works fine with elastic 7.1.x? I wanted to move as well but better if I know in advance that it works

@moix yes it works fine with  ES-7.1.1. By default, it installes ES-7.0.2 in the pip command. Took me  a bit time but it is running now as well.

@Djyamss How did you install python pip module for ES-7.1.1?

7.0.2 is still the newest version available. Source: https://pypi.org/simple/elasticsearch/
Probably works fine with 7.1.1

Hi, using elasticsearch 7.0.2 release , I have found that aggregation  queries do not work; the aggregated value is empty, as reported by elasticseach query.   Not sure if elastalert is not generating the proper query, or if it is the elasticsearch module not able to match elasticsearch 7.1.1 syntax?.
@Djyamss , do you have a newer module for elasticsearch ?? Do these type of rules/queries work for you?
I have successfully tested rules of type:

change
spike and
flatline.
and I have validated in Kibana  that the aggregated key is aggregable.

Details follow:
installed packages:
pip freeze | grep elast
elastalert==0.2.0b2
elasticsearch==7.0.2

Example Rule
name: slow_transaction
type: metric_aggregation
index: apm-7.1.0-transaction-*

metric_agg_key: transaction.duration.us
metric_agg_type: avg
doc_type: doc
max_threshold: 2

filter:
- query:
    query_string:
      query: "service.environment:dev AND service.name:my-application-name AND transaction.name:some-http-transaction"

alert:
- "alerta"
- "hipchat"

#ommiting_alerta_and_hipchat: from_this_post

the --es_debub_trace logs the following queries (which should not use localhost, but my elastisearch hostname instead!)
curl -H 'Content-Type: application/json' -XGET 'http://localhost:9200/apm-7.1.0-transaction-*/doc/_search?pretty&ignore_unavailable=true&size=0' -d '{
  "aggs": {
    "metric_transaction.duration.us_avg": {
      "avg": {
        "field": "transaction.duration.us"
      }
    }
  },
  "query": {
    "bool": {
      "filter": {
        "bool": {
          "must": [
            {
              "range": {
                "@timestamp": {
                  "gt": "2019-07-24T08:11:37.473354Z",
                  "lte": "2019-07-24T08:12:37.473354Z"
                }
              }
            },
            {
              "query_string": {
                "query": "service.environment:dev AND service.name:my-application-name AND transaction.name:some-http-transaction"
              }
            }
          ]
        }
      }
    }
  }
}'
curl -H 'Content-Type: application/json' -XPOST 'http://localhost:9200/elastalert_status_status/_doc?pretty' -d '{
  "@timestamp": "2019-07-24T08:13:18.237350Z",
  "endtime": "2019-07-24T08:12:37.473354Z",
  "hits": 0,
  "matches": 0,
  "rule_name": "slow_transaction",
  "starttime": "2019-07-24T08:09:37.473354Z",
  "time_taken": 0.04545402526855469
}'
curl -H 'Content-Type: application/json' -XPOST 'http://localhost:9200/elastalert_status_status/_doc?pretty' -d '{
  "@timestamp": "2019-07-24T08:13:18.237350Z",
  "endtime": "2019-07-24T08:12:37.473354Z",
  "hits": 0,
  "matches": 0,
  "rule_name": "slow_transaction",
  "starttime": "2019-07-24T08:09:37.473354Z",
  "time_taken": 0.04545402526855469
}'

with a reply of the forrm:
{
  "took" : 63,
  "timed_out" : false,
  "_shards" : {
    "total" : 42,
    "successful" : 42,
    "skipped" : 0,
    "failed" : 0
  },
  "hits" : {
    "total" : {
      "value" : 0,
      "relation" : "eq"
    },
    "max_score" : null,
    "hits" : [ ]
  },
  "aggregations" : {
    "metric_transaction.duration.us_avg" : {
      "value" : null
    }
  }
}

@PedroMSantosD aggregation type was not sending alert while hiting. So I changed the rule type to "any" so that solved it for me. Below is a sample which is running for me:
`name: Metricbeat CPU Spike Rule
type: any
index: metricbeat-*
metric_agg_key: system.cpu.user.pct
metric_agg_type: avg
query_key: beat.hostname
timeframe:
minutes: 5
min_threshold: 0.2
max_threshold: 0.8
filter:

term:
metricset.name: "cpu"
realert:
minutes: 0
aggregation:
minutes: 30

alert:

"email"
email:
"email"
smtp_host: "IP"
smtp_port: XX
smtp_ssl: false

from_addr: "email"`

as per documentation
should be aggregations, instead of aggs;
"aggregations" : {
    "<aggregation_name>" : {
        "<aggregation_type>" : {
            <aggregation_body>
        }
        [,"meta" : {  [<meta_data_body>] } ]?
        [,"aggregations" : { [<sub_aggregation>]+ } ]?
    }
    [,"<aggregation_name_2>" : { ... } ]*
}

@Djyamss will check; thanks.

I just found that if I set the doc_type to '' on the yaml rule configuration; the CURL is made to the proper URL
curl -H 'Content-Type: application/json' -XGET 'http://localhost:9200/apm-7.1.0-transaction-*/_search?pretty&ignore_unavailable=true&size=0' -d '{
  "aggs": {

that is, without the doc.
Now aggregations work!


Handoff is getting the tmp file name...

Problem
Handoff is getting the tmp file name. It should be the actual file name.

fixed in 2b47fa851fe6e9dff965031ca9db7f2c185a89ac


Focusing a window does not move it to the front

I have yabai on version 7.1.3, skhd on version 0.3.9 and AltTab installed. Additionally MacOS is on version 15.
The problem is that I have 2 windows stacked on top of each other. I can switch the focus of the input but the window in stays in the back and does not move to the front. Sorry, if this issue has already been reported but I have not seen it and just wanted to ask for help. I switched off system-integrity in case that matters. The video appended tries to show the issue at hand.
If there are any more infos that I can provide, please let me know.
Thanks in advance and kind regards.
https://github.com/user-attachments/assets/9266562f-d5d3-48c6-830e-e5d5a2a78eea

I think I found the issue but am still not sure how I can fix it. The command that is used to arrange these windows in the way they are is in the skhd-config like this:
alt - c : yabai -m window --toggle float;
yabai -m window --grid 1:5:1:0:3:1
This moves the window on the grid to the front but the window in the back is just not in a grid. Therefore it cannot really be gotten to the front. If the command is applied to both windows (unlike in the video, where only the terminal is in grid), the swap for foreground/focus works.
Does anyone have an idea on what the instruction for the config should be such that the windows are interchangeable for foreground but keep their current layout or is that just a bad idea?

I also have the same problem when using --toggle float. Does anyone know the solution?


Request about how to publish datasets

I read your paper and am very interested in this research.
I want to run this GitHub code, but I'm having trouble downloading the dataset.
It looks like a Chinese phone number is required to download the dataset.
Could you share datasets via other tools, such as Google Drive?
I look forward to your reply.

@ZHU-Zhiyu Thank you for your reply. I'm looking forward to it!

@ryhara Here is the link  with passwd:1234

@ZHU-Zhiyu  Thank you very mach!
I was able to download it.
Could you please add the Pre-trained Model to the folder? Sorry for so many requests...
This part of the README.md

Pre-trained Model
Pre-trained EventSAM model (e.g. rgbe_encoder.pth) needs to be downloaded and put in ./checkpoints.
EventSAM Model Code：1234

Hi @ryhara  I have uploaded the checkpoint in the same folder. You can check the linkagain.

@ZHU-Zhiyu
I was able to download it!
I really appreciate it. I will read the paper and the code again, and use it as a reference for my research! Thank you.


chore: edits to WIT.md

This PR adds some edits for clarity and convention.  One point of confusion not addressed is the presence of two headings with Identifier.

Thanks!


Tuple destructuring type is different for different target options.

TypeScript Version:  3.9.0-dev.20200226
Search Terms: target, indexing, tuple, destructuring, array, undefined, es5
Code
const arr: Array<string> = [];

const [first] = arr;
const zero = arr[0];

const str1: string = first;
const str2: string = zero;

also patch lib.es5.d.ts
from
 interface Array<T> {
  //...
  [n: number]: T;
 }

to
 interface Array<T> {
  //...
  [n: number]: T | undefined;
 }

Expected behavior:
Expect tsc to report 2 errors irrelevant of which target version is selected.
Actual behavior:
When using option "target": "es6":
src/index.ts:8:9 - error TS2322: Type 'string | undefined' is not assignable to type 'string'.
  Type 'undefined' is not assignable to type 'string'.

8   const str2: string = zero;
          ~~~~

Found 1 error.

When using option "target": "es5":
src/index.ts:6:7 - error TS2322: Type 'string | undefined' is not assignable to type 'string'.
  Type 'undefined' is not assignable to type 'string'.

6 const str1: string = first;
        ~~~~

src/index.ts:7:7 - error TS2322: Type 'string | undefined' is not assignable to type 'string'.
  Type 'undefined' is not assignable to type 'string'.

7 const str2: string = zero;
        ~~~~

Found 2 errors.

Playground Link: https://github.com/nicu-chiciuc/typescript-issue-001
Related Issues:
https://github.com/microsoft/TypeScript/issues/13778
https://github.com/microsoft/TypeScript/issues/36635
The whole idea of chaining the indexing definition for arrays comes from the first issue and mentioned this problem in this comment.
I didn't realize that the behavior depends on the version of the target option.

Some level of difference should be expected here since since we know that when targeting ES5 this will be downleveled to arr[0], whereas in a native ES6 runtime this will go through the Iterable protocol and possibly produce different results.
It looks like we have some shortcut paths in the checker that assume an Iterable from Array<T> will produce T when determining the iteration path. We could probably change that to be slower if multiple people need this support.


Add event tracking to timeline

What
Add Google Analytics event tracking to the links within timeline section of the landing page.
This should use the following:
Event Category: pageElementInteraction
Event Action: Timeline
Event Label: [Page URL of destination page]
Why
So we can track engagement with the timeline element of the landing page.
Trello: https://trello.com/c/cwkmPkIN/822-add-event-tracking-to-timeline
:warning: This application is Continuously Deployed: :warning:

Merged changes are automatically deployed to staging and production.

Make sure you follow the guidance for deployments before you merge.

Check your branch is being deployed in the Release app, after merging.

 - looks good!
Code looks good as far as I can tell...


Open external links in new tab

Feature Description
for convenience to prevent losing steamdb.info site
like these ones:

Middle click them.

Middle click them.

that is inconvenience
all sane websites do that


Hill Cipher Added

Added Hill Cipher encode/decode operations.
Encryption:

Place the plaintext in a matrix.
Place the key in a matrix.
Multiply them together.

Decryption:

Place the cipher-text in a matrix.
Place the key in a matrix.
Calculate the inverse of the key matrix.
Multiply the inverse key matrix by the cipher-text matrix.

Hey!  This pull request has gotten rather old and that's our fault.  This project stopped being actively maintained for a while and it looks like your pull request has started to gather dust.  Would you be able to update your branch to the latest version of CyberChef and we'll give it a review?

Hey, this PR has remained without updates for four weeks now.  I'll close it now, but feel free to re-open if you find time to contribute! 😄


dashboard: Add content security headers

Closes #3208
\cc @titanous

Updated to include GitHub domains.


Fix UB In NSArray:chuzzle

When calling chuzzle on a zero-length instance of NSArray, a C-Array of length 0 is created.
This doesn't cause any actual problems on any platforms I've tested, but it trips the undefined behaviour sanitizer in Xcode which is annoying and drowns out any useful warnings.

Thanks 1.0.10 pushed to CocoaPods


question titles and inputs alignment

When titlePosition is set to left, is there a way to align the start of the inputs? See attached image.
Thanks,
Daniel

@moldoe hello
It could be achive via the css:
.title-left {
  width: 30%;
  text-align: right;
}

We've created an example for you: https://plnkr.co/edit/7YyVmX8JGYTnB44IMXOV?p=preview
Could you please check it?

Awesome, thank you!


TC-08 Support

Setup

Example filename: none
Version of Python: 3.7
Pico Technology device model: TC-08
Driver name, version number and platform (32- or 64-bit): 64-bit
Operating system: Windows 10
USB port type (e.g. 2.0): 2.0

Description
Cannot find documentation or implementation for the TC-08 thermocouple reader.
Steps to reproduce the issue
Searching through the picosdk-python-wrappers repository.
Actual Result
No instances of the tc-08, tc08, TC08, TC-08, etc. found.
Expected Result
Was hoping to find a Tc08 wrapper object.
Notes
None

We currently don't have support for the TC-08 within this repo but we will be looking to add it too the repo in the future

I am also interested in a Python support for the TC-08. Is it likely to become available this year ?
Thanks

Until there is decent support from the manufacturer, I was forced to go elsewhere in the interest of time.
The DATAQ DI-2008 has similar capabilities and the ability to connect as a COM port, making connection to it from Python very simple.  I went with that since it was in a similar price range and was much easier to automate.


Improve the readme file

Someone new to the project always navigates to the readme to understand how to setup the project  and how to open their first pr, in the current readme, it might be hard for the first timers to navigate so in my proposed solution, I would like to improve the readme by making separate shell commands for each step involved in making a pr and also add the gssoc timeline as to how many points does each pr carry and a little about the gssoc timeline.

I would like to work on this issue under gssoc'23

will get working on it
Thank you


Fix 'docker stats' help message

It was missing the fact that you can pass in more than one container
Closes #10771
Signed-off-by: Doug Davis<EMAIL_ADDRESS>

Putting docs review on this... I think that's right.

LGTM

LGTM - @fredlf @jamtur01

LGTM


Add cache plugin and tiered cache documentation

Description
Adding a new doc for cache plugins introduced as part of 2.14.
Also adding a doc for tiered cache which is one of the implementation provided via cache plugin.
Note: This is an experimental feature.
Issues Resolved
Closes https://github.com/opensearch-project/documentation-website/issues/6300
Checklist

[x] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@hdhalter This is almost the same as the previous one which got reverted. I have changed 2.13 to 2.14, hope it should be okay?
There are few items/features missing but we will take those separately as the changes are not yet fully merged in.

Thanks, @sgup432 !

Ok I messed up a bit(other commits are added to this PR) by fixing DCO check. Fixing it now.

@natebower I have addressed comments. Looks good to me.


Upgrade to jQuery 2.1.3

Cleaned up the use of jQuery in a few places, upgraded the dev version to 2.1.3 which plays a bit nicer with node / CommonJS.

Coverage remained the same at 81.68% when pulling 24c79b16bad3362b3de39ce2e21a7d51f466c15e on upgrade-jquery-2 into d51910064ef5031f3142ebebbebeb3f7505f1f01 on master.

LGTM


我想要swiper滑动的当前页面有超出的内容并有滚动条 x方向swiper不支持怎么办

This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Swiper Version: EXACT RELEASE VERSION OR COMMIT HASH, HERE.

Live Link or JSFiddle/Codepen or website with isssue: PREFERABLY (IF YOU WANT YOUR ISSUE TO BE RESOLVED ASAP).

Expected Behavior
EXPLAIN WHAT IS TO BE EXPECTED, HERE.
Actual Behavior
EXPLAIN WHAT IS ACTUALLY HAPPENING, HERE.
P.S. Remember, an issue is not the place to ask questions. You can use Stack Overflow
for that.
Before you open an issue, please check if a similar issue already exists or has been closed before.

Your issue is closed because it is not filled correctly. Before you open an issue please review the contributing guideline.
Please fill the issue template correctly and:

Clearly describe the issue including steps to reproduce when it is a bug.
Make sure you fill in the earliest version that you know has the issue.
Provide live link or JSFiddle/Codepen or website with isssue

It will save a lot of time for other contributors to check your issue and fix it.


Keeping cargo target directory

So that we can avoid rebuilding everything always.
It is also easier to debug, as we can keep the files output by cargo build.

It still always recompiles for me.... :(

I think it looks like it but actually isn't fully, but still yes somehow.
What I see when running out keccak test is:
First I run
cargo run --release rust riscv/tests/riscv_data/keccak -o test_keccak/ -f

Inside test_keccak, cargo_target is added as well as a bunch of asm files.
If I simply run it again, the asm files are rewritten but the cargo_target dir isn't. So it looks like the final target binaries aren't recompiled, but the asm ones are.
@lvella do you know what's happening?

@lvella do you know what's happening?

You have the intended behavior, because I didn't touch the .asm generation, just the cargo target, and cargo is doing its job correctly for you and skipping rust build.
Now why it doesn't work for @chriseth is a mystery.

It still always recompiles for me.... :(

Fixed! (probably)

Yep, works for me now.


Closure-stylesheets support

Hello, can you add support closure-stylesheets in your plugin?

It's been over three years, are we going to see any progress on this in the foreseeable future?

@MTCoster i can no longer maintain this package. If anyone wants to takeover i'd gladly hand the project over.

closing due to inactivity, feel free to re-open if the issue persists.

Reopen?

@polkovnikov-ph after 3 years? heh, ok re-opened


Assertion Failure

Does it happen when dropping the control on the form? Is it the latest version 1.8.1? Which Delphi version?

Yes, Delphi 10 Seattle

I can't repeat this. Are you using the latest release version 1.8.1?

Yes.. Im using the version 1.8.1
unit BCEditor.Consts;
interface
uses
  Vcl.Graphics;
type
  TBCEditorCharSet = set of AnsiChar;

const
  BCEDITOR_VERSION = '1.8.1';

...

In this example it was working? https://github.com/bonecode/TBCEditor/issues/508
Or did you create it run-time?

The error occurs at design time in Delphi

Yes, I know. Did you comment out Loaded?

Yes its..

I just fixed design-time painting. Try the latest trunk.

I made another fix for CanFocus.

Hi,
Steps :

Select the TBCEditor..
TBCEditor.Minimap.Indicator.Options.ioUseBlending  = TRUE

Delphi Version : 10.1 Berlin

Fixed.

Thank you so much


step 1: datamodel + config import

use action parser & params parser to go to mem db with nicely organized structs
use sum types
config info is

employees / team
hotel structure e.g.rooms
products (all variety of what can be sold)

@despiegk I have managed to put in place a working model, but I was wondering where you want me to go from here. Working model includes:

data persistence implemented with md files (only a few pieces of dummy data entered so far)
internal structs and logic ie a memdb with light sdk
telegram bot at a very basic level integrated with the system