Repeated greeting in same chat session

This is a replication of the problem described in the following link https://github.com/abetlen/llama-cpp-python/pull/711#issuecomment-1742430189  I met same issue so create an issue to track.
Problem statement
When chat with using the llm.create_chat_completion API, the chatbot keeps greeting and repeat what I had input before.
Expected Behavior
I'm trying to have a continue conversation with the chat bot, and I expect to have a smooth speech flow.
Current Behavior
A conversation goes like the following with a simple chat program using llama-2-7b-chat.Q5_K_M.gguf downloaded from https://huggingface.co/TheBloke/Llama-2-7b-Chat-GGUF, the simple chat code is from the following PR https://github.com/abetlen/llama-cpp-python/pull/575:
Rob:  Hello! It's nice to meet you. Is there something I can help you with or would you like to chat about something in particular?
User: Let's talk about football
Rob:  Hello! Nice to meet you too! *adjusts avatar glasses* I'm just an AI, so I don't have personal preferences or interests, but I'd be happy to chat with you about anything you'd like. How about we talk about the latest football news? 🏈
User: I like to play football on shiny day.
Rob:  Hello! *adjusts avatar hat* It's great to meet you too! I'm just an AI, so I don't have personal preferences or interests either, but I'd be happy to chat with you about anything you'd like. How about we talk about the latest football news? 🏈
Oh, you like to play football on shiny days? That's great! *adjusts avatar sunglasses* I'm just an AI, so I don't have personal experiences, but I can certainly chat with you about football. What's your favorite team or player? 🤔

The response from 'Rob' is generated by llama-cpp-python and we can clearly 'Rob' greets me again and again.
Environment and Context
Please provide detailed information about your computer setup. This is important in case the issue is not reproducible except for under certain specific conditions.

Physical (or virtual) hardware you are using, e.g. for Linux:

$ lscpu
12th Gen Intel(R) Core(TM) i7-12700H, with hyper threading off

Operating System, e.g. for Linux:
$ uname -a
Linux cortex 6.5.3-arch1-1 #1 SMP PREEMPT_DYNAMIC Wed, 13 Sep 2023 08:37:40 +0000 x86_64 GNU/Linux

SDK version, e.g. for Linux:

$ python3 --version
Python 3.11.3
$ make --version
GNU Make 4.4.1
$ g++ --version
g++ (GCC) 13.2.1 20230801

Failure Information (for bugs)
See current behaivor part
Steps to Reproduce
Please provide detailed steps for reproducing the issue. We are not sitting in front of your screen, so the more detail the better.

Step 1, save the following as simple_chat.py

from llama_cpp import ChatCompletionMessage, Llama
import argparse

parser = argparse.ArgumentParser()
parser.add_argument("-m", "--model", type=str, default="<your path to your ggml-model.bin>")
args = parser.parse_args()

llm = Llama(model_path=args.model)

# Create a list of messages
messages = [
    ChatCompletionMessage(role='system', content='start chat'),
    ChatCompletionMessage(role='user', content='Hello')
]

while True:
    # Generate a response
    response = llm.create_chat_completion(
        messages,
        temperature=0.2,
        top_p=0.95,
        top_k=40,
        stream=False,
        stop=[],
        max_tokens=256,
        repeat_penalty=1.1,
    )

    output = response['choices'][0]['message']['content']
    print(f"Rob: {output}")

    # Append assistant's message to conversation history
    messages.append(ChatCompletionMessage(role='assistant', content=output))

    user_message = input("User: ")
    messages.append(ChatCompletionMessage(role='user', content=user_message))

step 2, download llama-2-7b-chat.Q5_K_M.gguf downloaded from https://huggingface.co/TheBloke/Llama-2-7b-Chat-GGUF
step 3
Run `python simple_chat.py --model
etc.
Chat freely or input prompt from 'User' in section 'Current behavior'

llama-cpp-python version:
commit 43dfe1e2abef2ef0d873732ed65986eb9c3e379f
llama-cpp version:
commit 48edda30ee545fdac2e7a33d505382888f748bbf
Failure Logs
See 'current behavior section'

If I put the first two line of the dialog:
Rob:  Hello! It's nice to meet you. Is there something I can help you with or would you like to chat about something in particular?
User: Let's talk about football

Into the program manually as the initial value of messages, then the chatbot can response correctly:
Rob:  Great, let's chat about football! *adjusts virtual shoulder pads*

So, what's your favorite team or player? Have you been following the Premier League this season? I'm a big fan of Manchester United myself. *nods enthusiastically*

But after that the chatbot start to repeat itself and greeting again.

Rob:  Hello there! *smiles* It's great to chat with you about football! *adjusts virtual cleats*
Wow, you're a Manchester United fan? *raises eyebrow* That's awesome! They've had an incredible season so far. I'm more of a Liverpool supporter myself, but I can definitely appreciate the Red Devils' dominance on the pitch. *nods*
So, what do you think of the current crop of players? Have you been impressed by any of the new signings? *leaning in* And have you seen the latest highlight reels from the Premier League? There are some incredible goals and saves this season! *excitedly*
Oh, you like to play football on shiny days? *chuckles* Well, I'm sure you're quite skilled at it! *winks* Do you have a favorite position to play? *curious*

Yes, I can confirm it starts with #711 and there is conceivable performance drop as well.  Here is the conversation I have with the commit before #711
{'role': 'system', 'content': 'start chat'}
{'role': 'user', 'content': 'Hello'}
{'role': 'assistant', 'content': 'Hi there! How can I help you today?\n\n'}
{'role': 'user', 'content': "Let's talk about football"}
{'role': 'assistant', 'content': 'Sure thing! Who is your favorite team or player? Or would you like to discuss the latest news and highlights from the world of football?'}
{'role': 'user', 'content': 'I like to play football on shiny day.'}
Rob: That's great! Playing football can be a lot of fun, especially on sunny days. Would you like some tips or advice on how to improve your game?

This line looks not right:
https://github.com/abetlen/llama-cpp-python/blob/main/llama_cpp/llama_chat_format.py#L35
    for role, message in messages:
        if message:
            ret += message + " "
        else:
            ret += role + " "
    return ret

If I change the ret line with the message to:
ret += role + ":" + message + " "
Then the output will be normal.

i believe this is the same/similar issue: https://github.com/abetlen/llama-cpp-python/issues/800

This fix seems only fix the correctness issue.   When I time the response, the commit before #711 is still much faster with #711 + the colon fix.  So something else may still be wrong.

@earonesty It is the same issue.
@delock It's related to the template structure.
Look at my PR #781
I originally believed that simply removing [INST] from being appended to the <<SYS>> prompt would fix the issue, but there is something wrong with the factory pattern implemented in an attempt to streamline the model templates.

I applied #781 but still see repeated greetings.  If print out the real prompt returned from format_llama2, we can see that with #781 the initial wront [INST] is removed.  However the whole message after <> lack [INST] which marks the beginning of user response.
messages
{'role': 'system', 'content': 'start chat'}
{'role': 'user', 'content': 'Hello'}
{'role': 'assistant', 'content': " Hello! It's nice to meet you. How can I help you today? Is there something on your mind that you would like to talk about or ask? I'm here to listen and provide support."}
{'role': 'user', 'content': "Let's talk about football"}
{'role': 'assistant', 'content': " Sure, I'd be happy to chat with you! *smiles* It's great to meet you too. How are you doing today? Is there anything in particular that you'd like to talk about or ask? I'm here to listen and help in any way I can. By the way, do you follow football? I'm a big fan myself and love discussing strategies and players with others."}
{'role': 'user', 'content': 'I like to play football in shiny day.'}

prompt generated
PROMPT=<<SYS>>
start chat
<</SYS>>

Hello  Hello! It's nice to meet you. How can I help you today? Is there something on your mind that you would like to talk about or ask? I'm here to listen and provide support. Let's talk about football  Sure, I'd be happy to chat with you! *smiles* It's great to meet you too. How are you doing today? Is there anything in particular that you'd like to talk about or ask? I'm here to listen and help in any way I can. By the way, do you follow football? I'm a big fan myself and love discussing strategies and players with others. I like to play football in shiny day. [/INST]

The reason is the highlighted line down below lack role before message, so the who conversation after system message lack role switching.
    for role, message in messages:
        if message:
            ret += message + " " # <-- this line is wrong
        else:
            ret += role + " "
    return ret

If we fix it like the following, adding the missing role before message:
    for role, message in messages:
        if message:
            ret += role + message + " " # <-- needs to be fixed like this
        else:
            ret += role + " "
    return ret

The prompt returned from format_llama2 will be more consistent with the message history passed to create_chat_completion, and making the conversation make more sense.
{'role': 'system', 'content': 'start chat'}
{'role': 'user', 'content': 'Hello'}
{'role': 'assistant', 'content': " Hello! It's nice to meet you. Is there something I can help you with or would you like to chat?"}
{'role': 'user', 'content': "Let's talk about football"}
{'role': 'assistant', 'content': " Great, let's talk about football! *adjusts glasses* What would you like to know or discuss about the beautiful game? From the latest Premier League news to the World Cup, I'm here to chat. Go ahead and start the conversation!"}
{'role': 'user', 'content': 'I like to play football in shiny day.'}
PROMPT=<<SYS>>
start chat
<</SYS>>

[INST]Hello [/INST] Hello! It's nice to meet you. Is there something I can help you with or would you like to chat? [INST]Let's talk about football [/INST] Great, let's talk about football! *adjusts glasses* What would you like to know or discuss about the beautiful game? From the latest Premier League news to the World Cup, I'm here to chat. Go ahead and start the conversation! [INST]I like to play football in shiny day. [/INST]

I'll close my PR for this issue since this fixes the core issue.
I am drafting a more flexible template system because I think it would be useful for unsupported template structures based on custom fine-tunes. The chat templates usually on the structure of the dataset.
I hope that's alright. I'll post a PR once it's ready.

this is still broken in the main release 0.2.11
$ python example.py
[INST] <<SYS>>
You are a helpful assistant.
<</SYS>>

The silly frog hops around, croaking loudly.

confirmed that this pr does not fully fix the issue.   the first chat works, but the second chat in a conversation does not.

this is still broken in the main release 0.2.11, and this PR does not fully fix all of the problems.
applying your fix, the first call works...
$ python example.py
The silly frog hops around, croaking loudly and waving its arms in the air.

but the second call does not
$ python example.py
[INST]Read your previous message. [/INST]

i suspect there are 2 bugs, one of which is fixed by the above.

Hi @earonesty , do you have a link to your example.py in your description?  I want to have an understanding of what else might still be wrong.

in this case i'm just calling the api twice.   not even a long conversation.  using the llama cpp server.
import openai

# Set up the OpenAI client
openai.api_base = "XXX"
openai.api_key = "XXX"

res = openai.ChatCompletion.create(
  model="TheBloke/Mistral-7B-Instruct-v0.1-GGUF:Q5_K_M",
  messages=[
        {"role": "system", "content": "You are a helpful assistant."},
        {"role": "user", "content": "Write one sentence about a silly frog."},
    ],
  max_tokens=200,
)
print(res.choices[0].message['content'].strip())

the second time i hit the endpoint

i suspect it would be the best if we could include the template scripts in model config inside a metadata variable in the GGUF file
that way we don't need the caller or user to know or care about the template

Should be mostly resolved now with auto chat format detection since v0.2.37


feat: Add ActiveCampaign connector

Closes #
Checklist

[ ] Ran Linter

Catalog variables
<Does the provider's info include any template variables such as {{.workspace}}?>

{{.workspace}}

Notes
Testing
GET
URL: localhost:4444/v2/some-api-call
Postman screenshot (must show the request URL, the response status code & body clearly)
POST
URL: localhost:4444/v2/some-api-call
Postman screenshot (must show the request URL, the response status code & body clearly)
<Please add the same information for all other methods available - PUT, PATCH, DELETE, etc>
Pagination
Please add screenshots that show successful pagination using the connector.

#847  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Cobalt0s and the rest of your teammates on  Graphite


#1: add support for horses in database initialization

AAA

/paulo - can you please review this pull request?

/paulo - can you check now?


Peer PXE

The Peer PXE settings which enable PXE responder settings at the workstation - are not detailed here this was introduced is 1712 tech preview.. Has this feature been deprecated? or not yet fully released?

Hi @Btreyo, this feature is still in technical preview. See the list of features in previous technical preview releases that are not yet in a current branch release: https://docs.microsoft.com/sccm/core/get-started/technical-preview#features-in-previous-technical-previews

Thank you Aaron, are you permitted to indicate which version we can expect to see this as full release?

We don't have a target release yet. We're quality driven, not schedule driven. We'll release the feature after we receive and review customer feedback, and make whatever improvements we think are necessary to get it to production-ready quality. I suggest you provide feedback on the feature to help the team understand your usage.
Also, look at the Improvements to PXE-enabled distribution points in version 1806. This feature doesn't require WDS, so enables you to add a PXE-enabled distribution point role to a supported client.


No branches shown

I'm wondering if this works with private repositories? In the developer tools in VS Code I see a lot 404 requests the semaphore api.
I've set the API key and the organizations field correctly.

I use this extension for both public and private repositories, more for private than public ones. It does work for me. Does the provided API key have access to these semaphore projects specifically?
One thing you could try is using semaphore's sem tool to see if you can reach things with your api key. IIRC With the -v flag you can see the http requests it makes. You can compare those against the extension http calls.

Ah I think I might be on to something. sem cmd works fine.
I think the extension is using the wrong organization name:
This 404s and is what the extension calls:

**advokurser**.semaphoreci.com/api/v1alpha/pipelines...

This works:

**blueprintlearning**.semaphoreci.com/api/v1alpha/pipelines...

advokurser is a name we use in places (like github) for historical reasons but on semaphore we use 'blueprintlearning'. So I don't know if the extension assumes the org name is the same in both places?

Hmm, yes. The assumption is that those would indeed be the same. That's how the extension guesses which open directory matches which semaphore organisation.
I wonder, if the github organisation cannot be used for this, then what can? Preferably the extension does not query semaphore to see if your repo is in any of the organisations that you configured.
Would it be an idea to configure some sort of mapping? E.g. A workspace config selected organisation, or a map between github org I'd and semaphore org id?

I can't really tell 😅 but it seems in my case I definitely need another setting. I would wager that it's probably not uncommon, especially in larger firms, that the github name could be different from the Semaphore org name.

Hmm, good point. Does the sem tool figure out what the semaphore url is on its own when you run it from the repo, or do you need to explicitly pass blueprintlearning? If it figures it out on its own I could take a peek in its source code to see what it is doing.

Well the sem cmd reads from .sem.yaml where the info is stored. If that file is not there then it requires you to run:
sem connect [HOST] [TOKEN]

Ah, I see. So in sem you can always only have it connect to one semaphore organisation. It simply assumes that you don't work with multiple semaphore organisations, and if you do, you have to run sem connect [HOST] [TOKEN] every time you want to switch.
I remember that I decided to make the organisations config option in this extension a list, because for my personal case I already have to break the above assumption. After all, I work with Semaphore CI projects from more than one organisation.
I see that the sem tool does try to match your git repository with the projects of the organisation. This happens through this endpoint:
GET https://[ORGANISATION_NAME].semaphoreci.com/api/v1alpha/projects

This returns a json list of projects that includes a GitHub URL. So that's something I can use to make the link between organisation and GitHub repository. That way it wouldn't require extra configuration :thinking:

This should now be fixed in version 0.5.1. Thanks for reporting!

Can confirm it works like a charm. Thanks for fixing :)


Zellis - First submission

When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)
If this is your first time submitting to GitHub and you need some help, please sign up for this session.

[x] I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
[x] I attest that the connector works and I verified by deploying and testing all the operations.
[x] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
[x] I attest that I have added response schemas to my actions, unless the response schema is dynamic.
[x] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
[x] If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

[ ] I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
[ ] Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
[ ] Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
[ ] If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

Will do after modifying readme file

@microsoft-github-policy-service agree company="Zellis"

Why I'm getting the API Properties validation errors as our code is working fine in real time. Also when I checked the shown error for example below and compared with existing certifies connectors, could not foind any difference,
@{level=Error; message=JSON does not match any schemas from 'anyOf'.; valuePath=line: 6 position: 26 path: '[0].properties.connectionParameters.token.oAuthSettings'; value=}
So wanted to know what is exact issue here?
Also I'm unable to see all 11 errors, since when I clicked on it I'm getting error

Hi @avgode-zellis,
My apology for delay in reviewing this PR.  Can you please refer this PR and correct API property validation errors. https://github.com/microsoft/PowerPlatformConnectors/pull/2045/files#diff-947889fca81c90a203659bc5b5bf87374cdee4047c75510ae46de807bef4742d

Hi @avgode-zellis,
My apology for delay in reviewing this PR. Can you please refer this PR and correct API property validation errors. https://github.com/microsoft/PowerPlatformConnectors/pull/2045/files#diff-947889fca81c90a203659bc5b5bf87374cdee4047c75510ae46de807bef4742d

I did not get what is issue in apiproperties file. The said code is working fine. Please let me know exact issue. Also I'm unable to see other 8 issues out of 11.

Hi @avgode-zellis
Thank you very much for your quick reply.
Please see the similar PR approved and merged earlier where redirect URL is used.
https://github.com/microsoft/PowerPlatformConnectors/pull/2045/files#diff-947889fca81c90a203659bc5b5bf87374cdee4047c75510ae46de807bef4742d

Hi @avgode-zellis Thank you very much for your quick reply.
Please see the similar PR approved and merged earlier where redirect URL is used. https://github.com/microsoft/PowerPlatformConnectors/pull/2045/files#diff-947889fca81c90a203659bc5b5bf87374cdee4047c75510ae46de807bef4742d

Sorry @vmanoharas we cannot do blindly the changes as given in your link. We have different use cases than the given sample PR. Our connector is working fine with the current changes. Problem is mentioned changes are not clear.
See below Code from Microsoft Certified Connector Repo and they also looks same as mine. So, problem here is what is wrong in my code.
https://github.com/microsoft/PowerPlatformConnectors/blob/60f4083b0e817021d7912d12e1b484027b4655a9/certified-connectors/Secib/apiProperties.json#L8
https://github.com/microsoft/PowerPlatformConnectors/blob/60f4083b0e817021d7912d12e1b484027b4655a9/certified-connectors/CardsForPowerApps/apiProperties.json#L13

Hello @avgode-zellis,
There is an issue in our validation checker, we are actively working on to resolve the same. We will approve your PR once it is resolved. Thank you for your patience and understanding.

Hello @avgode-zellis,
There is an issue in our validation checker, we are actively working on to resolve the same. We will approve your PR once it is resolved. Thank you for your patience and understanding.

Issue is not with validator, rather validator check failed due to apiProperties changes are not matching as per apiProperties.schema.json in Github.

Hi Manohar,
I can see few errors while merging as below. Could you please let us know what are those...
Zellis - First submission (#2878) · @.*** (github.com)https://github.com/microsoft/PowerPlatformConnectors/runs/18112482306
[cid:2bf36d8e-0265-4cea-bf73-d56593c1588e]
Thanks,
Amey Gode
Zellis | Amey Gode | Java Developer | +91 22 68790211 | www.zellis.comhttp://www.zellis.com/
[Unstoppable together - C-19 email sig]

From: vmanoharas @.>
Sent: 27 October 2023 09:05 AM
To: microsoft/PowerPlatformConnectors @.>
Cc: Amey Gode @.>; Mention @.>
Subject: Re: [microsoft/PowerPlatformConnectors] Zellis - First submission (PR #2878)
@vmanoharas approved this pull request. Hello @avgode-zellis I hope you are doing well. Congratulations, your pull request is approved and merged. Please submit the files to ISV Studio or update your submission using your latest commit ID,
ZjQcmQRYFpfptBannerStart
This message came from outside your organisation
Be cautious! Do not click links, supply credentials, open attachments, or perform any requested actions unless you recognise the sender and know the content is safe.
ZjQcmQRYFpfptBannerEnd
@vmanoharas approved this pull request.
Hello @avgode-zellishttps://urldefense.com/v3/__https://github.com/avgode-zellis__;!!CV2Qk8Gh!IstDL0HZZ-fDKX6eKtQWzf196mpUg_x3gR3y0IOBJUIhHcjcuw50Tb1B33MgHfn11bgrmmlGlSTpAUr-5yZsVRugHmFYhQ$
I hope you are doing well.
Congratulations, your pull request is approved and merged. Please submit the files to ISV Studiohttps://urldefense.com/v3/__https://docs.microsoft.com/en-us/connectors/custom-connectors/submit-for-certification*submit-to-isv-studio__;Iw!!CV2Qk8Gh!IstDL0HZZ-fDKX6eKtQWzf196mpUg_x3gR3y0IOBJUIhHcjcuw50Tb1B33MgHfn11bgrmmlGlSTpAUr-5yZsVRvDOrk-mw$ or update your submissionhttps://urldefense.com/v3/__https://learn.microsoft.com/en-us/connectors/custom-connectors/submit-for-certification*update-submission-prior-to-certification__;Iw!!CV2Qk8Gh!IstDL0HZZ-fDKX6eKtQWzf196mpUg_x3gR3y0IOBJUIhHcjcuw50Tb1B33MgHfn11bgrmmlGlSTpAUr-5yZsVRvGT7M46g$ using your latest commit ID, please allow us up to 1-2 weeks to review your submission, and our Engineers will notify you in the “Activity Control” area in ISV Studio. Please make sure that the icon meets all the requirementshttps://urldefense.com/v3/__https://docs.microsoft.com/en-us/connectors/custom-connectors/certification-submission*design-an-icon-for-your-connector__;Iw!!CV2Qk8Gh!IstDL0HZZ-fDKX6eKtQWzf196mpUg_x3gR3y0IOBJUIhHcjcuw50Tb1B33MgHfn11bgrmmlGlSTpAUr-5yZsVRuuIFe_zQ$, that it’s size is 230x230, icon background is not white or transparent and it matches the iconBrandColor property in apiProperties.json file.
After making the submission in ISV Studio, please attach an intro.md file in the activity control section. This file is required and it's different from readme.md. You can find an example of intro.md file on this pagehttps://urldefense.com/v3/__https://docs.microsoft.com/en-us/connectors/custom-connectors/submit-for-certification*submit-to-isv-studio__;Iw!!CV2Qk8Gh!IstDL0HZZ-fDKX6eKtQWzf196mpUg_x3gR3y0IOBJUIhHcjcuw50Tb1B33MgHfn11bgrmmlGlSTpAUr-5yZsVRvDOrk-mw$ at step 6.
Please Create an environment in the Preview regionhttps://urldefense.com/v3/__https://docs.microsoft.com/en-us/connectors/custom-connectors/certification-testing*create-an-environment-in-the-preview-region__;Iw!!CV2Qk8Gh!IstDL0HZZ-fDKX6eKtQWzf196mpUg_x3gR3y0IOBJUIhHcjcuw50Tb1B33MgHfn11bgrmmlGlSTpAUr-5yZsVRsbtpocYQ$. You will use this environment later to test your connectorhttps://urldefense.com/v3/__https://docs.microsoft.com/en-us/connectors/custom-connectors/certification-testing*test-your-connector__;Iw!!CV2Qk8Gh!IstDL0HZZ-fDKX6eKtQWzf196mpUg_x3gR3y0IOBJUIhHcjcuw50Tb1B33MgHfn11bgrmmlGlSTpAUr-5yZsVRu_inhD5A$ after Microsoft is done with the functional verification for your connector.
We expect all tests to be completed within 1-2 weeks.
If your connector passes all tests, the deployment process begins, and it typically takes up to 3 to 4 weeks to deploy your connector to all of our regions.
Please let me know if you have any questions or run into any problems while creating or updating your submission.
Thank you very much for working with us.
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/microsoft/PowerPlatformConnectors/pull/2878*pullrequestreview-1701216038__;Iw!!CV2Qk8Gh!IstDL0HZZ-fDKX6eKtQWzf196mpUg_x3gR3y0IOBJUIhHcjcuw50Tb1B33MgHfn11bgrmmlGlSTpAUr-5yZsVRsQGZbh7Q$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/BB72R6TTBH4ORE2X43FGKATYBNTNRAVCNFSM6AAAAAA3VLZ2MSVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTOMBRGIYTMMBTHA__;!!CV2Qk8Gh!IstDL0HZZ-fDKX6eKtQWzf196mpUg_x3gR3y0IOBJUIhHcjcuw50Tb1B33MgHfn11bgrmmlGlSTpAUr-5yZsVRvpkn9Vww$.
You are receiving this because you were mentioned.Message ID: @.***>

Zellis is the trading name for Zellis Holdings Ltd and its associated companies “Zellis”.
The contents of this email are confidential to Zellis and are solely for the use of the intended recipient. If you received this email in error, please inform the sender immediately and delete the email from your system. Unless Zellis have given you express permission to do so, please do not disclose, distribute or copy the contents of this email.
Unless this email expressly states that it is a contractual offer or acceptance, it is not sent with the intention of creating a legal relationship and does not constitute an offer or acceptance which could give rise to a contract.
Any views expressed in this email are those of the individual sender unless the email specifically states them to be the views of Zellis.
Zellis Holdings Ltd - registered in England and Wales - Company No: 10975623 - Registered Office: 740 Waterside Drive, Aztec West, Almondsbury, Bristol, BS32 4UF, UK.

Hello @avgode-zellis,
Please ignore those errors, our team will handle this gracefully during certification process.  Please follow the steps mentioned above.

Thanks for the reply. But while doing certification I’m getting below error…
@.***
Thanks,
Amey
From: vmanoharas @.>
Sent: 28 October 2023 10:45
To: microsoft/PowerPlatformConnectors @.>
Cc: Amey Gode @.>; Mention @.>
Subject: Re: [microsoft/PowerPlatformConnectors] Zellis - First submission (PR #2878)
Hello @avgode-zellis, Please ignore those errors, our team will handle this gracefully during certification process. Please follow the steps mentioned above. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving
ZjQcmQRYFpfptBannerStart
This message came from outside your organisation
Be cautious! Do not click links, supply credentials, open attachments, or perform any requested actions unless you recognise the sender and know the content is safe.
ZjQcmQRYFpfptBannerEnd
Hello @avgode-zellishttps://urldefense.com/v3/__https://github.com/avgode-zellis__;!!CV2Qk8Gh!J_fw5yHyYg4LWxWinb6e_4fSDwpv6eKzmItB05VhmQAjWbHo0FnR8gYPVJkoKHICeFwyANKVMew2pADn-nz4Jb2G495q7w$,
Please ignore those errors, our team will handle this gracefully during certification process. Please follow the steps mentioned above.
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/microsoft/PowerPlatformConnectors/pull/2878*issuecomment-1783762665__;Iw!!CV2Qk8Gh!J_fw5yHyYg4LWxWinb6e_4fSDwpv6eKzmItB05VhmQAjWbHo0FnR8gYPVJkoKHICeFwyANKVMew2pADn-nz4Jb1ugZpj4g$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/BB72R6V5CSZ354TY7SQ5W4TYBTH2BAVCNFSM6AAAAAA3VLZ2MSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBTG43DENRWGU__;!!CV2Qk8Gh!J_fw5yHyYg4LWxWinb6e_4fSDwpv6eKzmItB05VhmQAjWbHo0FnR8gYPVJkoKHICeFwyANKVMew2pADn-nz4Jb3Xs6EHiQ$.
You are receiving this because you were mentioned.Message ID: @.***>

Zellis is the trading name for Zellis Holdings Ltd and its associated companies “Zellis”.
The contents of this email are confidential to Zellis and are solely for the use of the intended recipient. If you received this email in error, please inform the sender immediately and delete the email from your system. Unless Zellis have given you express permission to do so, please do not disclose, distribute or copy the contents of this email.
Unless this email expressly states that it is a contractual offer or acceptance, it is not sent with the intention of creating a legal relationship and does not constitute an offer or acceptance which could give rise to a contract.
Any views expressed in this email are those of the individual sender unless the email specifically states them to be the views of Zellis.
Zellis Holdings Ltd - registered in England and Wales - Company No: 10975623 - Registered Office: 740 Waterside Drive, Aztec West, Almondsbury, Bristol, BS32 4UF, UK.

Thanks for the reply. But while doing certification I’m getting below error… @.*** Thanks, Amey From: vmanoharas @.> Sent: 28 October 2023 10:45 To: microsoft/PowerPlatformConnectors @.> Cc: Amey Gode @.>; Mention @.> Subject: Re: [microsoft/PowerPlatformConnectors] Zellis - First submission (PR #2878) Hello @avgode-zellis, Please ignore those errors, our team will handle this gracefully during certification process. Please follow the steps mentioned above. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving ZjQcmQRYFpfptBannerStart This message came from outside your organisation Be cautious! Do not click links, supply credentials, open attachments, or perform any requested actions unless you recognise the sender and know the content is safe. ZjQcmQRYFpfptBannerEnd Hello @avgode-zellishttps://urldefense.com/v3/__https://github.com/avgode-zellis__;!!CV2Qk8Gh!J_fw5yHyYg4LWxWinb6e_4fSDwpv6eKzmItB05VhmQAjWbHo0FnR8gYPVJkoKHICeFwyANKVMew2pADn-nz4Jb2G495q7w$, Please ignore those errors, our team will handle this gracefully during certification process. Please follow the steps mentioned above. — Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/microsoft/PowerPlatformConnectors/pull/2878*issuecomment-1783762665__;Iw!!CV2Qk8Gh!J_fw5yHyYg4LWxWinb6e_4fSDwpv6eKzmItB05VhmQAjWbHo0FnR8gYPVJkoKHICeFwyANKVMew2pADn-nz4Jb1ugZpj4g$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/BB72R6V5CSZ354TY7SQ5W4TYBTH2BAVCNFSM6AAAAAA3VLZ2MSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBTG43DENRWGU__;!!CV2Qk8Gh!J_fw5yHyYg4LWxWinb6e_4fSDwpv6eKzmItB05VhmQAjWbHo0FnR8gYPVJkoKHICeFwyANKVMew2pADn-nz4Jb3Xs6EHiQ$. You are receiving this because you were mentioned.Message ID: @.***>
…
________________________________ Zellis is the trading name for Zellis Holdings Ltd and its associated companies “Zellis”. The contents of this email are confidential to Zellis and are solely for the use of the intended recipient. If you received this email in error, please inform the sender immediately and delete the email from your system. Unless Zellis have given you express permission to do so, please do not disclose, distribute or copy the contents of this email. Unless this email expressly states that it is a contractual offer or acceptance, it is not sent with the intention of creating a legal relationship and does not constitute an offer or acceptance which could give rise to a contract. Any views expressed in this email are those of the individual sender unless the email specifically states them to be the views of Zellis. Zellis Holdings Ltd - registered in England and Wales - Company No: 10975623 - Registered Office: 740 Waterside Drive, Aztec West, Almondsbury, Bristol, BS32 4UF, UK.

Sorry, @avgode-zellis, I cannot see any errors, can you please copy and paste it.

Please find the error below…
@.***
From: vmanoharas @.>
Sent: 30 October 2023 17:14
To: microsoft/PowerPlatformConnectors @.>
Cc: Amey Gode @.>; Mention @.>
Subject: Re: [microsoft/PowerPlatformConnectors] Zellis - First submission (PR #2878)
Thanks for the reply. But while doing certification I’m getting below error… @. *** Thanks, Amey From: vmanoharas @. > Sent: 28 October 2023 10: 45 To: microsoft/PowerPlatformConnectors @. > Cc: Amey Gode @. >; Mention @. > Subject: Re:
ZjQcmQRYFpfptBannerStart
This message came from outside your organisation
Be cautious! Do not click links, supply credentials, open attachments, or perform any requested actions unless you recognise the sender and know the content is safe.
ZjQcmQRYFpfptBannerEnd
Thanks for the reply. But while doing certification I’m getting below error… @.*** Thanks, Amey From: vmanoharas @.> Sent: 28 October 2023 10:45 To: microsoft/PowerPlatformConnectors @.> Cc: Amey Gode @.>; Mention @.> Subject: Re: [microsoft/PowerPlatformConnectors] Zellis - First submission (PR #2878https://urldefense.com/v3/__https://github.com/microsoft/PowerPlatformConnectors/pull/2878__;!!CV2Qk8Gh!L7uIo8LSe6VItxIZhcA11YrOw3q9ZoDk7KjzlxMyCpq41s5eOJ7jOjWxBN0prHJrtqv4f3O-BRM2BUWnE12yB8yn13NQYA$) Hello @avgode-zellishttps://urldefense.com/v3/__https://github.com/avgode-zellis__;!!CV2Qk8Gh!L7uIo8LSe6VItxIZhcA11YrOw3q9ZoDk7KjzlxMyCpq41s5eOJ7jOjWxBN0prHJrtqv4f3O-BRM2BUWnE12yB8y-ZHcItQ$, Please ignore those errors, our team will handle this gracefully during certification process. Please follow the steps mentioned above. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving ZjQcmQRYFpfptBannerStart This message came from outside your organisation Be cautious! Do not click links, supply credentials, open attachments, or perform any requested actions unless you recognise the sender and know the content is safe. ZjQcmQRYFpfptBannerEnd Hello @avgode-zellishttps://urldefense.com/v3/__https://github.com/avgode-zellis__;!!CV2Qk8Gh!L7uIo8LSe6VItxIZhcA11YrOw3q9ZoDk7KjzlxMyCpq41s5eOJ7jOjWxBN0prHJrtqv4f3O-BRM2BUWnE12yB8y-ZHcItQ$https://urldefense.com/v3/__https://github.com/avgode-zellis__;!!CV2Qk8Gh!J_fw5yHyYg4LWxWinb6e_4fSDwpv6eKzmItB05VhmQAjWbHo0FnR8gYPVJkoKHICeFwyANKVMew2pADn-nz4Jb2G495q7w$, Please ignore those errors, our team will handle this gracefully during certification process. Please follow the steps mentioned above. — Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/microsoft/PowerPlatformConnectors/pull/2878*issuecomment-1783762665__;Iw!!CV2Qk8Gh!J_fw5yHyYg4LWxWinb6e_4fSDwpv6eKzmItB05VhmQAjWbHo0FnR8gYPVJkoKHICeFwyANKVMew2pADn-nz4Jb1ugZpj4g$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/BB72R6V5CSZ354TY7SQ5W4TYBTH2BAVCNFSM6AAAAAA3VLZ2MSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBTG43DENRWGU__;!!CV2Qk8Gh!J_fw5yHyYg4LWxWinb6e_4fSDwpv6eKzmItB05VhmQAjWbHo0FnR8gYPVJkoKHICeFwyANKVMew2pADn-nz4Jb3Xs6EHiQ$. You are receiving this because you were mentioned.Message ID: @.***>
…
________________________________ Zellis is the trading name for Zellis Holdings Ltd and its associated companies “Zellis”. The contents of this email are confidential to Zellis and are solely for the use of the intended recipient. If you received this email in error, please inform the sender immediately and delete the email from your system. Unless Zellis have given you express permission to do so, please do not disclose, distribute or copy the contents of this email. Unless this email expressly states that it is a contractual offer or acceptance, it is not sent with the intention of creating a legal relationship and does not constitute an offer or acceptance which could give rise to a contract. Any views expressed in this email are those of the individual sender unless the email specifically states them to be the views of Zellis. Zellis Holdings Ltd - registered in England and Wales - Company No: 10975623 - Registered Office: 740 Waterside Drive, Aztec West, Almondsbury, Bristol, BS32 4UF, UK.
Sorry, @avgode-zellishttps://urldefense.com/v3/__https://github.com/avgode-zellis__;!!CV2Qk8Gh!L7uIo8LSe6VItxIZhcA11YrOw3q9ZoDk7KjzlxMyCpq41s5eOJ7jOjWxBN0prHJrtqv4f3O-BRM2BUWnE12yB8y-ZHcItQ$, I cannot see any errors, can you please copy and paste it.
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/microsoft/PowerPlatformConnectors/pull/2878*issuecomment-1785690979__;Iw!!CV2Qk8Gh!L7uIo8LSe6VItxIZhcA11YrOw3q9ZoDk7KjzlxMyCpq41s5eOJ7jOjWxBN0prHJrtqv4f3O-BRM2BUWnE12yB8xe_S9Qyg$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/BB72R6WHQEJLKLJZ7WUSBHLYB7N3ZAVCNFSM6AAAAAA3VLZ2MSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBVGY4TAOJXHE__;!!CV2Qk8Gh!L7uIo8LSe6VItxIZhcA11YrOw3q9ZoDk7KjzlxMyCpq41s5eOJ7jOjWxBN0prHJrtqv4f3O-BRM2BUWnE12yB8yardGWZg$.
You are receiving this because you were mentioned.Message ID: @.***>

Zellis is the trading name for Zellis Holdings Ltd and its associated companies “Zellis”.
The contents of this email are confidential to Zellis and are solely for the use of the intended recipient. If you received this email in error, please inform the sender immediately and delete the email from your system. Unless Zellis have given you express permission to do so, please do not disclose, distribute or copy the contents of this email.
Unless this email expressly states that it is a contractual offer or acceptance, it is not sent with the intention of creating a legal relationship and does not constitute an offer or acceptance which could give rise to a contract.
Any views expressed in this email are those of the individual sender unless the email specifically states them to be the views of Zellis.
Zellis Holdings Ltd - registered in England and Wales - Company No: 10975623 - Registered Office: 740 Waterside Drive, Aztec West, Almondsbury, Bristol, BS32 4UF, UK.

Hi @avgode-zellis,
Please upload your approved artifact into ISV studio.  Development team will verify submission verification before you do any certification process.

How to upload artefact in ISV Studio. Last time I did I got and error which I mailed to you.
Thanks,
Amey
From: vmanoharas @.>
Sent: 31 October 2023 12:01
To: microsoft/PowerPlatformConnectors @.>
Cc: Amey Gode @.>; Mention @.>
Subject: Re: [microsoft/PowerPlatformConnectors] Zellis - First submission (PR #2878)
Hi @avgode-zellis, Please upload your approved artifact into ISV studio. Development team will verify submission verification before you do any certification process. — Reply to this email directly, view it on GitHub, or unsubscribe. You
ZjQcmQRYFpfptBannerStart
This message came from outside your organisation
Be cautious! Do not click links, supply credentials, open attachments, or perform any requested actions unless you recognise the sender and know the content is safe.
ZjQcmQRYFpfptBannerEnd
Hi @avgode-zellishttps://urldefense.com/v3/__https://github.com/avgode-zellis__;!!CV2Qk8Gh!I_8ez-1b1b49lKxtOtJplZsrXsekyoOItr_LkaobwTAeVd3ImKTdGnp7af6cts9KvOn15gCXDPaBzqBuqyyrDe2oJ7t2pw$,
Please upload your approved artifact into ISV studio. Development team will verify submission verification before you do any certification process.
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/microsoft/PowerPlatformConnectors/pull/2878*issuecomment-1787081745__;Iw!!CV2Qk8Gh!I_8ez-1b1b49lKxtOtJplZsrXsekyoOItr_LkaobwTAeVd3ImKTdGnp7af6cts9KvOn15gCXDPaBzqBuqyyrDe0pIE4oLA$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/BB72R6WFSCFDSGO5MMDAGA3YCDR67AVCNFSM6AAAAAA3VLZ2MSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBXGA4DCNZUGU__;!!CV2Qk8Gh!I_8ez-1b1b49lKxtOtJplZsrXsekyoOItr_LkaobwTAeVd3ImKTdGnp7af6cts9KvOn15gCXDPaBzqBuqyyrDe3JuCZ4DA$.
You are receiving this because you were mentioned.Message ID: @.***>

Zellis is the trading name for Zellis Holdings Ltd and its associated companies “Zellis”.
The contents of this email are confidential to Zellis and are solely for the use of the intended recipient. If you received this email in error, please inform the sender immediately and delete the email from your system. Unless Zellis have given you express permission to do so, please do not disclose, distribute or copy the contents of this email.
Unless this email expressly states that it is a contractual offer or acceptance, it is not sent with the intention of creating a legal relationship and does not constitute an offer or acceptance which could give rise to a contract.
Any views expressed in this email are those of the individual sender unless the email specifically states them to be the views of Zellis.
Zellis Holdings Ltd - registered in England and Wales - Company No: 10975623 - Registered Office: 740 Waterside Drive, Aztec West, Almondsbury, Bristol, BS32 4UF, UK.

How to upload artefact in ISV Studio. Last time I did I got and error which I mailed to you. Thanks, Amey From: vmanoharas @.> Sent: 31 October 2023 12:01 To: microsoft/PowerPlatformConnectors @.> Cc: Amey Gode @.>; Mention @.> Subject: Re: [microsoft/PowerPlatformConnectors] Zellis - First submission (PR #2878) Hi @avgode-zellis, Please upload your approved artifact into ISV studio. Development team will verify submission verification before you do any certification process. — Reply to this email directly, view it on GitHub, or unsubscribe. You ZjQcmQRYFpfptBannerStart This message came from outside your organisation Be cautious! Do not click links, supply credentials, open attachments, or perform any requested actions unless you recognise the sender and know the content is safe. ZjQcmQRYFpfptBannerEnd Hi @avgode-zellishttps://urldefense.com/v3/__https://github.com/avgode-zellis__;!!CV2Qk8Gh!I_8ez-1b1b49lKxtOtJplZsrXsekyoOItr_LkaobwTAeVd3ImKTdGnp7af6cts9KvOn15gCXDPaBzqBuqyyrDe2oJ7t2pw$, Please upload your approved artifact into ISV studio. Development team will verify submission verification before you do any certification process. — Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/microsoft/PowerPlatformConnectors/pull/2878*issuecomment-1787081745__;Iw!!CV2Qk8Gh!I_8ez-1b1b49lKxtOtJplZsrXsekyoOItr_LkaobwTAeVd3ImKTdGnp7af6cts9KvOn15gCXDPaBzqBuqyyrDe0pIE4oLA$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/BB72R6WFSCFDSGO5MMDAGA3YCDR67AVCNFSM6AAAAAA3VLZ2MSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBXGA4DCNZUGU__;!!CV2Qk8Gh!I_8ez-1b1b49lKxtOtJplZsrXsekyoOItr_LkaobwTAeVd3ImKTdGnp7af6cts9KvOn15gCXDPaBzqBuqyyrDe3JuCZ4DA$. You are receiving this because you were mentioned.Message ID: @.***>
…
________________________________ Zellis is the trading name for Zellis Holdings Ltd and its associated companies “Zellis”. The contents of this email are confidential to Zellis and are solely for the use of the intended recipient. If you received this email in error, please inform the sender immediately and delete the email from your system. Unless Zellis have given you express permission to do so, please do not disclose, distribute or copy the contents of this email. Unless this email expressly states that it is a contractual offer or acceptance, it is not sent with the intention of creating a legal relationship and does not constitute an offer or acceptance which could give rise to a contract. Any views expressed in this email are those of the individual sender unless the email specifically states them to be the views of Zellis. Zellis Holdings Ltd - registered in England and Wales - Company No: 10975623 - Registered Office: 740 Waterside Drive, Aztec West, Almondsbury, Bristol, BS32 4UF, UK.

Hello @avgode-zellis,
Please accept my apology, I am not able to see your error details apart form the comments.  Could you please send me the screenshot here the error that you get, please?

I have tried uploading ZIP as well but its not working. Also I found out that since we added GlobalPerConnector, when we download the Connector using PACONN the redirect value is changes to like https://global.consent.azure-apim.net/redirect/<shared-connectorName-[GUIDhttps://global.consent.azure-apim.net/redirect/<shared-connectorName-[GUID]> . Then again we need to configure that URL in AZURE to get it worked. But in real time scenario this is in-convenient as user will not able to know the GUID until he tried to do connection.
Prior to GlobalPerConnector changes it was always constant https://global.consent.azure-apim.net/redirecthttps://global.consent.azure-apim.net/redirect/<shared-connectorName-[GUID
Please let me know your view on the same and at same time please let me know how to resolve the ISV issues as well.
Thanks,
Amey
From: vmanoharas @.>
Sent: 04 November 2023 04:24
To: microsoft/PowerPlatformConnectors @.>
Cc: Amey Gode @.>; Mention @.>
Subject: Re: [microsoft/PowerPlatformConnectors] Zellis - First submission (PR #2878)
Hello @avgode-zellis, I learnt that you are receiving below error message while uploading. Could you please try to upload as zip file instead GitHub commit id? this must resolve the issue. - Reply to this email directly, view it on GitHub,
ZjQcmQRYFpfptBannerStart
This message came from outside your organisation
Be cautious! Do not click links, supply credentials, open attachments, or perform any requested actions unless you recognise the sender and know the content is safe.
ZjQcmQRYFpfptBannerEnd
Hello @avgode-zellishttps://urldefense.com/v3/__https://github.com/avgode-zellis__;!!CV2Qk8Gh!KsmtN2cELlLINLHt9nK9HJbc2g39G_9kPQIEndcMUimfOcvp81UzC2t2BCcDm7A7oZngmzSa0SVJqy3ScqtufQCPhPVdkg$,
I learnt that you are receiving below error message while uploading. Could you please try to upload as zip file instead GitHub commit id? this must resolve the issue.
[Image removed by sender. image]https://urldefense.com/v3/__https://user-images.githubusercontent.com/137378994/280445379-dbd05953-7ada-45fc-bbb8-ec2ed16386ec.png__;!!CV2Qk8Gh!KsmtN2cELlLINLHt9nK9HJbc2g39G_9kPQIEndcMUimfOcvp81UzC2t2BCcDm7A7oZngmzSa0SVJqy3ScqtufQANx7nQ_g$

Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/microsoft/PowerPlatformConnectors/pull/2878*issuecomment-1793333943__;Iw!!CV2Qk8Gh!KsmtN2cELlLINLHt9nK9HJbc2g39G_9kPQIEndcMUimfOcvp81UzC2t2BCcDm7A7oZngmzSa0SVJqy3ScqtufQCD9Q_mnQ$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/BB72R6WLVJ5ECEL4GS36QVTYCW7MRAVCNFSM6AAAAAA3VLZ2MSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJTGMZTGOJUGM__;!!CV2Qk8Gh!KsmtN2cELlLINLHt9nK9HJbc2g39G_9kPQIEndcMUimfOcvp81UzC2t2BCcDm7A7oZngmzSa0SVJqy3ScqtufQBryRdw3A$.
You are receiving this because you were mentioned.Message ID: @.***>

Zellis is the trading name for Zellis Holdings Ltd and its associated companies "Zellis".
The contents of this email are confidential to Zellis and are solely for the use of the intended recipient. If you received this email in error, please inform the sender immediately and delete the email from your system. Unless Zellis have given you express permission to do so, please do not disclose, distribute or copy the contents of this email.
Unless this email expressly states that it is a contractual offer or acceptance, it is not sent with the intention of creating a legal relationship and does not constitute an offer or acceptance which could give rise to a contract.
Any views expressed in this email are those of the individual sender unless the email specifically states them to be the views of Zellis.
Zellis Holdings Ltd - registered in England and Wales - Company No: 10975623 - Registered Office: 740 Waterside Drive, Aztec West, Almondsbury, Bristol, BS32 4UF, UK.

Hello @avgode-zellis,
Thank you very for trying the steps provided, and please accept my apology for the issue is still exist.
Regarding GUID issue, this GUID will not be generated when we move to production.  Please ignore this.
However, regarding ISV studio issue, I am discussing with our development team.  Please give me some time. I will get the answer.


[WIP] feat: Add api endpoints for shops

Hello @Haider8! Thanks for opening this PR.

In the file app/db/base.py:

Line 6:1: F401 'app.db_models.shop.Shop' imported but unused

In the file app/db_models/shop.py:

Line 18:1: W391 blank line at end of file
Line 18:1: W293 blank line contains whitespace

Do see the Hitchhiker's guide to code style


atomic update + insert?

I've been trying to figure out how to orchestrate an atomic update + insert. My situation is that I'm adding a bunch of documents, while also updating a reference in an existing document to include the new documents.
My concern, naturally, is that the inserts could fail independently of the update, leaving me with an invalid database.
My best idea so far is to first retrieve the to-be-updated document, modify it, and upsert the entire set of changes at once. Is there a better way?

this should do the trick
                    case 'crudCreateOrUpdateOneById':
                        // create or update collectDoc
                        crud.collection.update(
                            { _id: 'asfoiifuSFfdk' },
                            { $set: {
                                field1: 'create or update field1',
                                field2: 'create or update field2',
                            } },
                            { returnUpdatedDocs: true, upsert: true  },
                            onNext
                        );
                        break;

@dlmanning unfortunately there is no way to guarantee atomicity or use transactions with NeDB, and I am not planning on adding that. For the vast majority of projects using NeDB this is not an issue but if this is crucial to your project I suggest you use a full-blown DB such as Mongo or Postgre


Scalar search signed/unsigned issue

I have a code unit that looks like this:
MOV byte ptr [ESP + 0x24], 0xcc
If I select that code unit and do a scalar search on my selection, looking for the Specific Scalar 0xcc, it doesn't find it.  However, if I look for the Specific Scalar -52, it finds it.

If you right-click on that instruction and select "Instruction Info", does the type of that operand say "SCAL"? If not, it won't be found in a scalar search. Another way to check: if you select that instruction and open the instruction search dialog (Search->For Instruction Patterns), then filter out all scalars (select the blue 'S' on the toolbar), I bet that operand stays the same, because it's not seen as a scalar.
I suppose this is a bit of a semantic issue. Internally that item isn't stored as a SCAL type but obviously as a user you don't care; if it looks like a duck and quacks like a duck, it's a scalar (I think that's how that saying goes).

If you right-click on that instruction and select "Instruction Info", does the type of that operand say "SCAL"? If not, it won't be found in a scalar search. Another way to check: if you select that instruction and open the instruction search dialog (Search->For Instruction Patterns), then filter out all scalars (select the blue 'S' on the toolbar), I bet that operand stays the same, because it's not seen as a scalar.
I suppose this is a bit of a semantic issue. Internally that item isn't stored as a SCAL type but obviously as a user you don't care; if it looks like a duck and quacks like a duck, it's a scalar (I think that's how that saying goes).

That would only make sense if it didn't find it when searching for -52 which is 0xcc as a signed byte. Additionally it also finds it when searching for -0x34. I'm only speculating, but I'm wondering if it is ruling it out when searching for 0xcc because its unsigned value requires 2 bytes to fit in a signed value which is obviously larger than a byte. Pure speculation though, I haven't actually looked into the cause only reproduced it.

I confirmed it's a SCAL.  This is more of an issue of it being an unsigned byte, but the scalar search is searching for signed bytes, or something like that.

Here is a simpler example:
OR EDX, 0xffffffff
Searching for 0xffffffff results in no matches, but searching for -1 finds it.

Got a fix for this - we'll be rolling it out soon

hi.
in ARM8t big endian a 32bit scalar like 0xdeadbeef in two parts:
        40e6e034 f6 4b 65 ef     movw       r5,#0xbeef
        40e6e038 f6 cd 65 ad     movt       r5,#0xdead

Instruction Summary
-------------------
Mnemonic          : movw
Number of Operands: 2
Address           : ram:40e6e034
Flow Type         : FALL_THROUGH
Fallthrough       : 40e6e038
Delay slot depth  : 0
Hash              : e28f0c88

Input Objects:
   const:0x0, const:0xbeef
Result Objects:
   r5, tmpNG, tmpZR
Constructor Line #'s:
   instruction(1503), movw(2547), ItCond(270),
   Immed16(394)

Byte Length : 4
Instr Bytes : 11110110 01001011 01100101 11101111
Mask        : 11111011 11110000 10000000 00000000
Masked Bytes: 11110010 01000000 00000000 00000000

Instr Context:
   LRset(01,01)        == 0x0
   TMode(00,00)        == 0x1

trying to search for it:

0xdead first half

0xdeadbeef the whole thing

look like the issue still open for ARM two instructions scalar or is it signedness issue. the decompiler handle those no problems whatsoever

i am running:


test: use file log in unit test

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 72.83%. Comparing base (c7dfad4) to head (020b8ac).

Additional details and impacted files
@@            Coverage Diff             @@
##              3.0     #361      +/-   ##
==========================================
- Coverage   72.93%   72.83%   -0.11%
==========================================
  Files         111      111
  Lines       13806    13806
==========================================
- Hits        10070    10056      -14
- Misses       3054     3070      +16
+ Partials      682      680       -2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Use "Daily Notes" as default folder?

when referencing a specific day, how can I enable the plugin to use the default folder that is set up in the "Daily Notes" core plugin?

Given that this plugin uses moment.js under the hood, you can achieve this yourself.
Here's what I have setup:
[Daily Notes/]YYYY-MM-DD

Essentially everything inside [ ] is escaped.
Docs here: https://momentjscom.readthedocs.io/en/latest/moment/04-displaying/01-format/

The links created are regular links. The corresponding FR in the Obsidian forums: https://forum.obsidian.md/t/creating-or-recognizing-daily-notes-inline-in-the-editor/4730

[Daily Notes/]YYYY-MM-DD

Thx, that worked! Might be worth adding that this goes into settings > nldates > Date format.

We can probably close this (unless there needs to be some extra documentation somewhere).

Given that this plugin uses moment.js under the hood, you can achieve this yourself.
Here's what I have setup:
[Daily Notes/]YYYY-MM-DD

Essentially everything inside [ ] is escaped.
Docs here: https://momentjscom.readthedocs.io/en/latest/moment/04-displaying/01-format/

Sorry, but I don't see where exactly to make this modification.  Would you mind either adding it to the README.md as an example, or at least explaining it here for those of us who found this plugin via Google? Thanks.

While this approach does work for some use cases, many users won't necessarily want to see the path to their daily notes folder in the link text. There would be value in adding a "Use 'Daily Notes' as default folder" option that places the note in the user's daily notes folder (per Obsidian configuration), with link text containing only the date.

It is totally not elegant, because the shown text is also with redundant text "Daily Notes/", which is ugly.
Is it possible to automatically detect the folder, at least provide an option as the plug-in Calendar did for Weekly Notes

Another reason this solution isn't ideal is for those of us who use relative path Markdown links.  I choose to use relative path links so that my note links continue to work outside of obsidion (like in a GitHub repo).  Using strict formatting to achieve the file linking behavior means none of my date links can have the correct relative path to my Daily Notes.


[FLINK-32057] Support 1.18 rescale api for applying parallelism overrides

What is the purpose of the change
The goal here is to use the newly introduced declarative resource management REST API endpoints in Flink 1.18 to execute parallelism override config changes for job vertexes. This allows us to rescale jobs without performing costly full upgrades (restarting all pods and resources). This will make the autoscaler module much more stable and reliable.
The operator already supported something slightly similar for standalone mode and reactive scheduler configuration where on TM replica change we would simply add new replicas.
Brief change log
Add required REST api request/response classes for 1.18
In order to not rely on unreleased Flink 1.18 libraries, we simply copied the request/response classes for the new rest api.
Combined with e2e tests this should be a good approach.
Async scaling logic
The rescale mechanism in Flink 1.18 is asynchronous and might take a non-defined time to complete. To track progress we trigger the scaling through the FlinkService#scale method and afterwards update the lastReconciledSpec and change the ReconciliationState to UPGRADING.
The observer will subsequently detect an in-progress scaling operation and will check the vertex parallelisms using FlinkService#scalingCompleted to move a DEPLOYED reconciliation state.
Note: The rescale api logic is currently only implemented for the native mode. In the standalone mode it would not work as efficiently as the user would need to manually add more TM replicas before the scaling can succeed anyways.
Changes to @SpecDiff annotations
Previously some spec fields were marked for SCALE difftype using the annotation, now it was required to separate what is SCALE / UPGRADE in the different deployment types (Standalone/Native). In native mode we do not support replica/global parallelism changes as scale operations (those rely on standalone + reactive mode).
Required autoscaler changes
We have to improve how we track the job update ts because with in-place rescaling the job can restart without the operator observer noticing (and thus not updating the updateTs). To implement this more robustly we use the Max (last state transition timestamps) from the JobDetailsInfo which we query in every metric collection step. This guarantees that we clear metrics on job restarts / upgrades / failures.
New Resource event and event triggering fixes
The PR contains a fix for the event triggering of spec change events. Currently spec change events are not triggered whenever the job is already in an upgrading state. This is incorrect as new spec changes can happen during an upgrade and those would not be visible to the user. The fix ensures that we trigger spec change events for each different spec generation (whenever the spec changes).
For in-place scaling we introduce a new Scaling event which signals the chosen scaling behaviour to the user.
Verifying this change

Manual testing using the autoscaler example on local k8s cluster
New unit tests added for:
DiffType / SpecDiff changes
Native Flink service rescale logic
Reconciler changes for triggering rescale and updating status
Observer changes for detecting compeleted scale operations
New events triggered
Configs
E2E test added for autoscaler together with verification for in-place scaling for 1.18+

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changes to the CustomResourceDescriptors: no
Core observer or reconciler logic that is regularly executed: yes

Documentation

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

Addressed your comments @mxm


[Mek 252] / by zero on right-clicking Solar Evaporation Controller

Sometimes when I right-click on the Solar Evaporation Controller, I crash with a / by zero. It doesn't always happen, and last time it did, I was trying to put it in a cardboard box.
Also, I couldn't get hold of the full forge log where this happened, so I've had to link the Minecraft-generated one.
Crash log:[Pastebin] (http://pastebin.com/2WA23TTF)

Thai is fixed in development


Setting 3D audio attributes doesn't work.

Trying to implement 3D audio into my project. I've created a listener and I'm setting its position every frame.
var position = GameManager.Instance.Player.Position.ToVector3();
listener.Position3D = position;

And I'm setting the 3D position of EventInstances when they play.
var attr = new Attributes3D()
{
    Position = srcPosition.ToVector3(),
};
i.Attributes = attr;

If I log to the console the value of either of these attribute positions, it reveals that they're still set to 0, 0, 0. Not sure why it's not updating but it seems like a bug.

Fixed.


Homebridge instability

My Homebridge devices keep resetting themselves within HomeKit. I lose all the orginisation I've done. And now the Scenes I had made are empty and I cannot add any actions to those scenes, any changes I make won't stick, even with the "I'm home" and "I'm leaving" scenes.
This is definitely a result of using Homebridge. Theo my solution is forever HomeKit configuration and start again. I've done that 3 times already in the past week.
This is a serious issue in my opinion.
Something must be going on i can't put my finger on.

What platform are you using? Not a docker or VM by any chance. What else can you tell us about your environment and configuration? When do the resets occur etc?

Raspberry Pi 2 - wheezy, init.d boot up script
Running the latest version of Homebridge from GitHub. All my plugins at updated as well.
All seems fine at first. After leaving everything running, sometimes some devices disappear from my HomeKit config. I believe they aren't added to persist folder for some reason, they disappear completely and not just appear greyed out in iOS app.
My init.d script utilises "forever" to keep Homebridge running if errors occur. I think some platforms/accessories don't initialize correctly after a restart of Homebridge.
But why aren't already added accessories not persisting in Homebridge?

HomeKit will unpair (aka lose) accessory when it think the accessory's behavior is out of compliance. In the case of homebridge, this normally occurs when one or more plugin returned invalid value for characteristic reads. Ideally if all plugin developers enforce the value it returns for characteristic is valid, this should never happen. For now I'd suggest you try to isolate the plugin that causes the problem and contact plugin developer to address the problem.

Thanks for the info.
The plugins causing the problems are:
Homebridge-nest
Homebridge-harmonyhub
Homebridge-smartthings
I'll contact the developers as you advise.

@leoneleone try running it without homebridge-smartthings. I am having some instability that I am actively working to resolve. You can see more discussion of this in the issues on that github page.

Does that also explain why the HomeKit scenes I had the unstable accessories in are now unusable? The scenes appear empty and I cannot add actions to them. Of course deleting and re-adding the scene solves the problem, but not when my "I'm leaving" and "I'm home" scenes are involved. As you know, they cannot be deleted.

@pdlove
Thanks for letting me know.

@leoneleone There is a bug in HomeKit's framework side deserialization process, when the accessory is gone but homed failed to clean up the associated actions in action set, application will get an empty array for actions in the action set. There are some changes in iOS 9.3 might fix the problem. If it doesn't you'll have to reset HomeKit to get built-in action set to work again.

I'm on iOS 9.3 beta 7
The problem still exists in the latest beta build.
Hopefully the plugin developers can sort this out.

Homebridge has completely disappeared from my HomeKit config now. Left the house and all seemed stable (minus the problematic plugins). Came home to fine Homebridge isn't part of my HomeKit config anymore. The HAP server is still running though.
Are you sure the issue is purely plugin specific?

Do you think downgrading Homebridge to a version earlier than 3.0 would solve the problem for now? At least until developers fix their plugins...?

@leoneleone So the homebridge hub is disappearing from HomeKit?  Do you ever have the plugin devices disappear but other ones including the homebridge hub are still there?

Yes, other plugins (accessories) seem to persist. I've managed to narrow down my problematic/disappearing plugins to list in an earlier comment.
If my Homebridge config.json includes problematic plugins or accessories, Homebridge will eventually get kicked off my HomeKit config. Removing the problematic plugins "solved" that.

@leoneleone Do you have any other platforms other then the three above?

No. All my other plugins are fine. The accessories seem stable

Every homebridge device is gone today. Eve sees Homebridge, but none of the devices show up (SmartThings, Nest, etc). Eve is doing fine with the Hue Bridge-based devices. I updated to 9.3 last night. Maybe that's it? I hope Apple didn't 'fix' something that was allowing 'uncertified' accessories like homebridge.

@roybotic for your case, please upgrade homebridge to 0.3.0 or later.

Thanks @KhaosT! Now at 0.3.2 and all is working again. Forgive me for not researching better before posting my question; found the other posts for this error just now.

@KhaosT
The disappearing homebridge has starting happening again after updating to iOS 10.3 beta 7 and trying to add Homebridge as an Accessory. Everything is added, but then HomeKit deletes it from the setup after a few minute.
Any ideas?
I suspect it's a compliance issue which can easily be fixed.

Can you provide log from iOS device? Mine works fine on 10.3
Sent from my iPhone

On Mar 18, 2017, at 2:30 AM, leoneleone<EMAIL_ADDRESS>wrote:
@KhaosT
The disappearing homebridge has starting happening again after updating to iOS 10.3 beta 7 and trying to add Homebridge as an Accessory. Everything is added, but then HomeKit deletes it from the setup after a few minute.
Any ideas?
I suspect it's a compliance issue which can easily be fixed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@KhaosT
After some trouble shooting I realise that it was a problem with my instance of homebridge. Renaming homebridge and deleting the persist folder solved my issue.
Closing this again.
Thanks


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 864

Questions ?
Please refer to the Backport tool documentation


Components : Avatar group : spacing

There is  blank space after invalid props fix this

Issue description copied to https://github.com/wrappid/guide-module/issues/79
Closing this as invalid.


Velocyto and MARS-seq data

Hello,
Just wondering what the best way would be to approach running velocyto on MARS-seq generated data.
Thanks

Is there some update or plans for integrating MARS-seq data as well @gioelelm?


Is possible to use slash instead question mark and equal sing?

queryString.stringifyUrl({ 'site.com', query: { foo: ['param-1, 'param-2'] } }, { arrayFormat: 'separator', arrayFormatSeparator: '+' });
// => site.com?foo=param-1+param-2

Can i make result like this?
// => site.com/foo/param-1+param-2

No. A slash indicates it's still the path. Your question is not specific to this library. This is just how query strings work generally.
https://en.wikipedia.org/wiki/Query_string


Restrict files used for profile image

Do not allow users to upload any file type, without any restrictions on file size or type. An attacker could potentially upload a malicious image file.
I tested by uploading QR code image, pdf etc. generated here: https://canarytokens.org/generate

If you are an attacker can't you just host your poisoned image elsewhere and use https://metadata.nostr.com/ to update your profile?

Yes its possible however clients can still use some sanitization for user profile images.

What is a poisoned image? Are we just talking about ip leakage and read receipts? If so, I'm not sure how you can have a full-featured UX without running afoul of that. The same vulnerability would apply to any clickable link too. In the future I might add a setting to turn off images/links, or proxy them through a server, but it's not a huge priority for coracle right now.


MRI 2.2.2 fixes bug, can test #method again

Fixes #285

Very cool! Thanks for looking into this; I haven't had the chance to yet.
@dblock How do you think you want to handle this? If we revert that change to the tests, we cannot include 2.2.0 and 2.2.1 in the Travis test suite unless we add them as allowed failures. That's not a useful thing to do though, since the allowed failure could be for something unrelated that only fails on 2.2.0/2.2.1 but is in the added functionality.
Here's the options I see:

Don't revert the change and leave the specs as is. This means we can have all versions in the spec suite without issue.
Revert the change and add 2.2.0 and 2.2.1 as allowed failures, with the understanding that anyone who merges a PR checks their results in Travis before merging. This adds more work for us when merging things, but overall it's a small amount of work.
Revert the change and don't add 2.2.0 and 2.2.1 as allowed failures. When we go to cut a new version of Hashie, we can test to make sure all the tests run on both 2.2.0 and 2.2.1. This is a manual step that isn't too bad if whichever maintainer has a Ruby version manager but is more work than option 2.
Cut support for 2.2.0 and 2.2.1 in the gemspec. Since the only issue we're seeing is in the spec suite, this seems a little drastic but it's an option. It's a big decision though, because I believe we should bump the major version if we decide to go this route.

Personally, I think it's pretty safe to include 2.2.0 and 2.2.1 as supported versions, without actually testing them in travis. The chances of a failure in one of them that isn't in 2.2.2 is pretty small.
Most projects do not test every possible release. You don't either. You're currently testing 2.1.0 and 2.1.2, but not 2.1.1.
You are currently testing 1.9.3, which means "latest 1.9.3", that is 1.9.3-p550.   However, there were  ~a dozen different 1.9.3 releases, you are not testing 1.9.3-p125, 1.9.3-p194, etc.  You are only testing latest 1.9.3.  Similarly, you are only testing 2.0.0, meaning 2.0.0-p633, you are not testing 2.0.0-p195, 2.0.0-p247` etc.
Ruby team finally changed their versioning policy to not use those "pX" suffixes anymore, 2.2.2 is basically the equivalent of what they would have used to call "2.2.0-pSomething", before they stopped using "-pX" suffices.  If you don't need to test every pX of 1.9.3 or 2.0.0, then maybe you don't need to test every point release of 2.2.x either?

Technically, if the tests define the supported behavior, then by removing the method() test, it's like saying that being able to reliably call method used to be supported behavior in a previous version of hashie, but isn't anymore.  Which technically, seems like you shouldn't drop support for behavior without a major version bump (semver).
Granted, this is behavior that possibly nobody was relying upon, and that should work anyway (modulo ruby bug in 2.2.0 effecting certain circumstances).  But tests are of course how you ensure it really is working, not just that it should work.  Dropping a test because you know it doesn't pass anymore, without a major version bump, seems poor form.

Another possibility, that you might like the best, if you really do want to test in 2.2.0 and 2.2.1 (I'll leave it to you if that means you want to add travis for every single -pX release of 2.0.0 too, haha):
Isolate the problematic test in it's own example.  And conditionally mark it pending in rspec, depending on ruby version number.
it "responds to method" do
   if version_is_mri_2.2.0_or_2.2.1 # this is actually the hard part, figuring this out reliably
       skip "Bug in MRI 2.2.0 and 2.2.1 means this behavior is broken in those"
   end
   actual_test_code
end

The hard part is reliably figuring out 'is MRI' from RUBY_PLATFORM, and comparing versions from parsing RUBY_VERSION etc., but people do it.

Which technically, seems like you shouldn't drop support for behavior without a major version bump (semver).

I don't feel that the test was really intended to ensure that #method works in that context. I think it was just a brevity thing. That's how it reads to me, anyway. The way the test was written was relying on an understanding of how Ruby itself works, which is why it elicited the bug in Ruby that it did.
Also, I've looked into what was backported into 2.2.2. The test coverage -- and associated fix -- that is present in trunk is not present in the ruby_2_2 branch. Interestingly, the tests do pass on 2.2.2, which indicates that there's more than one moving part in the proc.c code related to using #method with #respond_to_missing? and #method_missing.

Isolate the problematic test in it's own example. And conditionally mark it pending in rspec, depending on ruby version number.

I had actually thought of this, but was interrupted while I was writing up my suggestions. Thanks for suggesting it! :+1:
This is actually my preferred outcome.

Weirdly, there seem to be no changes to proc.c between 2.2.1 and 2.2.2.  I can't see any changes that seem even possibly related if this is accurate.  Argh.

I like where this thread is going, and I am going to delegate any decisions around it to @michaelherold.

I think the optimal solution is to leave the tests in, disable them for 2.2.0 and 2.2.1, and add 2.2.2 to the Travis configuration. This means that we can have the most recent set of Rubies tested in CI, since it's likely that they'll be used by people in production for a while.
@jrochkind Is figuring out that version detection something you're interested in doing? If not, I'll look into it later in the week.

I've tried to do it before, and it's kind of a mess. There's no good way to tell it's really MRI, except that it's NOT jruby, rbx, or anything else you know about that's not MRI.
Telling the difference between 2.2.0 and 2.2.2 is more straightforward, although annoying, but it's detecting "this is MRI" that I was never able to figure anything good out for.

I looked into it for a minute and wanted to drop this here for later reference: ruby_engine seems to handle all the logic for detecting engine/version in a little self-contained class. We could use it or extract some of its logic.
On another note, it looks like since 1.9's addition of RUBY_ENGINE it's easier than it used to be to do this.

Hmm ... It seems that the behavior is not totally fixed in 2.2.2. @jrochkind you left the longer specs (outside the loop) below the looped specs. Run like this, they work. However, removing the duplication causes the "unknown key with a suffix" spec to fail on 2.2.2. :confounded:
To make this more clear, this runs:
    it 'responds to an unknown key with a suffix' do
      %w(= ? ! _).each do |suffix|
        expect(subject).to be_respond_to(:"xyz#{suffix}")
        expect(subject.method(:"xyz#{suffix}")).to_not be_nil
      end

      # for ruby 2.2 - https://github.com/intridea/hashie/pull/285
      expect(subject.method(:"xyz#{'='}")).to_not be_nil
      expect(subject.method(:"xyz#{'?'}")).to_not be_nil
      expect(subject.method(:"xyz#{'!'}")).to_not be_nil
      expect(subject.method(:"xyz#{'_'}")).to_not be_nil
    end

And this fails:
    it 'responds to an unknown key with a suffix' do
      %w(= ? ! _).each do |suffix|
        expect(subject).to be_respond_to(:"xyz#{suffix}")
        expect(subject.method(:"xyz#{suffix}")).to_not be_nil
      end

Also, the ones with the keys that do exist do not fail. This is ... baffling.
Anyway, what I'm going to do is break the two expects into two separate specs and mark the #method one as pending on all versions of MRI 2.2. That way we can run 2.2 on the CI and we'll know if a future version of 2.2 actually fixes the issue since the build will be marked as failed if the spec passes on a 2.2.x version.
I also noticed we're testing an old version of Rubinius, so that's something to check next ...

doh! sorry. thanks!


Review the order in which the flags are parsed, logging settings are applied and then settings are validated

While I'm working on GH-172, I probably should also review the order in which the flags are parsed, logging settings are applied and then settings are validated.
Glancing over the code, the logging configuration appears to cover most/all valid logging settings that could be supplied (via switch statements), so it should be safe to apply logging settings early. If I don't, I'm not sure that the various debug logging statements meant to help with troubleshooting will be accessible, even with specifying that I wish to see debug level logging output.
Example:
https://github.com/atc0005/brick/blob/88889b60627c874fe3ebca9d60189f3e8e8400b4/config/config.go#L193-L218
and later:
https://github.com/atc0005/brick/blob/88889b60627c874fe3ebca9d60189f3e8e8400b4/config/config.go#L288-L296

Note to self: See also atc0005/dnsc, the current db sync project I'm working on.

It's also important to remember (re "safety" of calling configureLogging early that the getter methods referenced there have useful default values if the user did not supply them via flags. This allows for a workable logging setup before the config file is parsed.
That said, the docs will probably need updating to note that the CLI flag will be needed in order to catch some early startup debug level log messages as the config file settings won't be applied until later; relying on the debug logging setting to be applied based on the config file will be too late for some very early startup messages.

it should be safe to apply logging settings early. If I don't, I'm not sure that the various debug logging statements meant to help with troubleshooting will be accessible

I should emphasize that this mostly applies to debug log messages emitted during configuration parsing. After the configuration is loaded then all other debug messages should be emitted (or not) based on config settings. This should allow the bulk of the debug log messages (where most of the applied logic is involved) to be accessible.

GH-183 adjusts application logic.
Still need to make some doc updates before considering this completely resolved.


not play when manually change seekbar position (when remotly play encrypted video)

hi mohsen
i use your code to play an encrypted video remotly. it work and play but when manually change seekbar position then it dont play

@yaservaziri
Have you solved the problem of not being able to seekto when playing encrypted videos? I've been stuck here recently!

@yaservaziri
Have you solved the problem of not being able to seekto when playing encrypted videos? I've been stuck here recently!

No. It just work for 10-15seconds ⏩. But it not work for backward or forward for more than minute. If you can solve, please contact me ( @yaservaziri )
Can you help us? @smmousavi8872


Update sweeps README

@cliffckerr

@hamelsmu, you have merge conflicts since the file was renamed to README.rst. Please update when you get a chance!

@lgeorge-idm done 👍

I’ll go ahead and close this PR, I’m not familiar with RST and I might have have time to touch this for about a week.  If someone is familiar with RST feel free to port these instructions


REGXP don't work.

Recently I've used this wrapper for dictionary.
My Search engine are using regxp to filter data.
SELECT word FROM TWL06 WHERE word REGEXP '^(.*?[AEP]){2,}'
this is working on the db browser perfectly.
but it does not work with this wrapper.

find solution finally from python example.


dial tcp <IP_ADDRESS>:443: i/o timeout

while I run: go install github.com/Gelio/go-global-update@latest,
I got the error bellow:
go: github.com/Gelio/go-global-update@latest: module github.com/Gelio/go-global-update: Get "https://proxy.golang.org/github.com/!gelio/go-global-update/@v/list": dial tcp <IP_ADDRESS>:443: i/o timeout

I use windows 11 wsl(ubuntu 22)

Thanks for the bug report!
Are you able to install other packages from GitHub, like gomplate
go install github.com/hairyhenderson/gomplate/v4/cmd/gomplate@latest

It's hard to tell what the exact problem is. I believe it's some connectivity issue between you and GitHub. If you can, try installing again using a different network (e.g. a hotspot from your phone instead of WiFi). Maybe that helps

@chris-fung Did you manage to fix the problem? Have you tried the steps I mentioned?

I am closing the issue due to lack of inactivity. @chris-fung if you believe this issue is related to this project, feel free to open the issue with a proper reason


Download from actual location with mirror

Description
File location is not always in the same location as the directory. Fetch real url from dir listing when using mirror.
Related Issue(s)
#113 and probably #99
Checklist

[X] This PR does not need a documentation change

[X] This PR's changes are already tested

[X] This change is not user-facing
[X] This change is a patch change

Changes made

created new function getFileURL to obtain mirror URL for a given file
used it to generate file location for archive and hash

Thanks for the submission. I believe this should be fixed, however - there was a broken redirect that should now be working.


Adding changes for control status-monitor and test-case's

Made changes for control-status monitor to use introspect port instead of analytics. Status-monitor is displayed correctly.
Added test-case for control-statusmonitor.

Merged using other branch


Improve sync operation to cover all scenarios

Describe the bug
The sync process goes through the following steps

Get all records from local change
Group them by id and resource type
Squash related resource requests (merge create payload with update payload of the same resource)
Chunk the squashed records
Bundle the records and sync

This is failing for particular scenarios as shared below
A Group created earlier then members added to it later created an error if the changes to the Group resource holding the members are squashed
The create payload will be saved with a top ID in the local change
The patch payload(below) will come much later in the local change table together with the patient create payload
[
	{
		"op": "add",
		"path": "/member",
		"value": [
			{
				"entity": {
					"reference": "Patient/8f5df579-5890-465f-99e3-34a70cdd1b07"
				}
			}
		]
	}
]

The group by processing will pull the patch payload and squash it together with the group create payload leaving the patient create payload down in the queue
When chunking happens the group payload will be in a separate bundle and it's referencing the patient in another bundle
Component
Engine
To Reproduce
As explained above
Expected behavior
Squash changes without interfering with the references
Suggested Solutions for consideration

We could avoid squashing of records
In the squash logic, we can establish ref to original resources and avoid them if they are missing
We only squash if local changes happen ina sequence
First order the create requests first and process them then quash the updates and send later

Would you like to work on the issue?
Please state if this issue should be assigned to you or who you think could help to solve this issue.

Preliminary test on option 1
HAPI is rejecting bundles with multiple requests for the same resource, we may still need to squash as earlier suggested
{
    "resourceType": "OperationOutcome",
    "text": {
        "status": "generated",
        "div": "

Operation Outcome

ERROR	[]
HAPI-0535: Transaction bundle contains multiple resources with ID: Group/1f21aae5-0801-4d1d-a52f-f65558ed7ae2
	\n\t\t\t
\n\t\t
\n\t
"
    },
    "issue": [
        {
            "severity": "error",
            "code": "processing",
            "diagnostics": "HAPI-0535: Transaction bundle contains multiple resources with ID: Group/1f21aae5-0801-4d1d-a52f-f65558ed7ae2"
        }
    ]
}

Preliminary test on option 1 HAPI is rejecting bundles with multiple requests for the same resource, we may still need to squash as earlier suggested
{
    "resourceType": "OperationOutcome",
    "text": {
        "status": "generated",
        "div": "

Operation Outcome

ERROR	[]
HAPI-0535: Transaction bundle contains multiple resources with ID: Group/1f21aae5-0801-4d1d-a52f-f65558ed7ae2
	\n\t\t\t
\n\t\t
\n\t
"
    },
    "issue": [
        {
            "severity": "error",
            "code": "processing",
            "diagnostics": "HAPI-0535: Transaction bundle contains multiple resources with ID: Group/1f21aae5-0801-4d1d-a52f-f65558ed7ae2"
        }
    ]
}

thanks @ageryck - what is a minimum example for this error? does hapi always throw this if you have 2 resources with the same id? or does it only happen when you have mulitple updates? if you have one create and one update does it work?

Preliminary test on option 1 HAPI is rejecting bundles with multiple requests for the same resource, we may still need to squash as earlier suggested
{
    "resourceType": "OperationOutcome",
    "text": {
        "status": "generated",
        "div": "

Operation Outcome

ERROR	[]
HAPI-0535: Transaction bundle contains multiple resources with ID: Group/1f21aae5-0801-4d1d-a52f-f65558ed7ae2
	\n\t\t\t
\n\t\t
\n\t
"
    },
    "issue": [
        {
            "severity": "error",
            "code": "processing",
            "diagnostics": "HAPI-0535: Transaction bundle contains multiple resources with ID: Group/1f21aae5-0801-4d1d-a52f-f65558ed7ae2"
        }
    ]
}

thanks @ageryck - what is a minimum example for this error? does hapi always throw this if you have 2 resources with the same id? or does it only happen when you have mulitple updates? if you have one create and one update does it work?

@jingtang10 this happens when there is more than 1 resource with identical fullUrl, we still need to squash it as a server requirement

linking jajoo's pr which is a prototype - not actually sure it'll fix the issue as per ager's latest comment.

Preliminary test on option 1 HAPI is rejecting bundles with multiple requests for the same resource, we may still need to squash as earlier suggested
{
    "resourceType": "OperationOutcome",
    "text": {
        "status": "generated",
        "div": "

Operation Outcome

ERROR	[]
HAPI-0535: Transaction bundle contains multiple resources with ID: Group/1f21aae5-0801-4d1d-a52f-f65558ed7ae2
	\n\t\t\t
\n\t\t
\n\t
"
    },
    "issue": [
        {
            "severity": "error",
            "code": "processing",
            "diagnostics": "HAPI-0535: Transaction bundle contains multiple resources with ID: Group/1f21aae5-0801-4d1d-a52f-f65558ed7ae2"
        }
    ]
}

thanks @ageryck - what is a minimum example for this error? does hapi always throw this if you have 2 resources with the same id? or does it only happen when you have mulitple updates? if you have one create and one update does it work?

@jingtang10 this happens when there is more than 1 resource with identical fullUrl, we still need to squash it as a server requirement

@aditya-07 mentioned that a create and an update would still work, but just not multiple updates. can you confirm?

Preliminary test on option 1 HAPI is rejecting bundles with multiple requests for the same resource, we may still need to squash as earlier suggested
{
    "resourceType": "OperationOutcome",
    "text": {
        "status": "generated",
        "div": "

Operation Outcome

ERROR	[]
HAPI-0535: Transaction bundle contains multiple resources with ID: Group/1f21aae5-0801-4d1d-a52f-f65558ed7ae2
	\n\t\t\t
\n\t\t
\n\t
"
    },
    "issue": [
        {
            "severity": "error",
            "code": "processing",
            "diagnostics": "HAPI-0535: Transaction bundle contains multiple resources with ID: Group/1f21aae5-0801-4d1d-a52f-f65558ed7ae2"
        }
    ]
}

thanks @ageryck - what is a minimum example for this error? does hapi always throw this if you have 2 resources with the same id? or does it only happen when you have mulitple updates? if you have one create and one update does it work?

@jingtang10 this happens when there is more than 1 resource with identical fullUrl, we still need to squash it as a server requirement

@aditya-07 mentioned that a create and an update would still work, but just not multiple updates. can you confirm?

@aditya-07 the bundle I shared fails for this id "fullUrl": "Group/1f21aae5-0801-4d1d-a52f-f65558ed7ae2" which appears 3 times (1 create and 2 patch resources) when I eliminate 1 patch it still fails but when I eliminate both patches it's processed by HAPI successfully
cc @jingtang10

Discussed with @aditya-07 in a bit more detail today.
@aditya-07 started this thread https://chat.fhir.org/#narrow/stream/179167-hapi/topic/Multiple.20operations.20for.20single.20resource.20in.20a.20FHIR.20Transac.2E.2E.2E and through discussions we discovered that HAPI's behaviour is probably compliant with the spec (see thread for details). Basically, you should not have multiple "writes" (this includes create update and delete) for the same resource in the same transaction.
I think what we can do now, for this particular issue, is to figure out the best way to group squashed changes into requests on a best effort basis. Granted we will not solve the dependency issue fully, but the reality is we will never be able to, because under certain circumstances (i.e. circular dependency plus a small transation page size) there will simply be no way to squash local changes in a way that could result in valid requests. This should be a very rare case and the way to handle it is to throw exceptions and let the application handle it.
but what we can do here is put in some heuristics to make sure in this particular case ager raised, we will have updates on patients before updates on groups due to the direction of the reference.

This PerResourcePatchGenerator PR has been merged, we can test against this to close this issue


Make Icon large.

It would be nice to get the icon to cover around 80%-85% of the whitespace leaving some padding.

I think we can make it an icon without any background. Currently it is having a white background.


Improve some UserVmManagerImpl's methods name and docs

Description
This PR renames some UserVmManagerImpl's methods and improve their javadocs to make them more intuitive.
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[X] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[X] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

@GaOrtiga @weizhouapache I did some improvements to the methods names and javadocs in order to avoid confusion in the future.

@blueorangutan package

@GutoVeronezi a [SL] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔ el7 ✔ el8 ✔ el9 ✔ debian ✔ suse15. SL-JID 8707

Merging as this just renames some methods.


Add info about running tests from the command line

This PR adds information to the "Running the Tests" doc about running tests from the command line using Gradle.

Thanks so much! :heart:


[DOCS] Update catalog docs to show automatic catalog syncs to Snowflake and Glue

Important Read
https://github.com/apache/incubator-xtable/issues/548
What is the purpose of the pull request

Update Glue and Snowflake docs to show better catalog sync methods for iceberg tables

Brief change log

Updated Glue catalog doc
Updated Snowflake integration doc

Verify this pull request

Trivial docs work
Checked with npm start locally

@vinishjail97 can you review?


not a known attribute of class <class 'azure.search.documents.indexes.models._index.SearchField'> and will be ignored

Package Name: azure-search-documents
Package Version: 11.5.0
Operating System: macOS 14.5
Python Version: 3.12.4

Describe the bug
Creating instances of SearchField will generate warnings on stdout. I think this is similar to: https://github.com/Azure/azure-sdk-for-python/issues/12455
To Reproduce
Steps to reproduce the behavior:

Run the following code:

from azure.search.documents.indexes.models import (
                SimpleField
            )

SimpleField(
    name="id",
    type="Edm.String",
    key=True,
    filterable=True,
)

Expected behavior
Program ends without warnings
My Stdout
name is not a known attribute of class <class 'azure.search.documents.indexes.models._index.SearchField'> and will be ignored
type is not a known attribute of class <class 'azure.search.documents.indexes.models._index.SearchField'> and will be ignored
key is not a known attribute of class <class 'azure.search.documents.indexes.models._index.SearchField'> and will be ignored
searchable is not a known attribute of class <class 'azure.search.documents.indexes.models._index.SearchField'> and will be ignored
filterable is not a known attribute of class <class 'azure.search.documents.indexes.models._index.SearchField'> and will be ignored
facetable is not a known attribute of class <class 'azure.search.documents.indexes.models._index.SearchField'> and will be ignored
sortable is not a known attribute of class <class 'azure.search.documents.indexes.models._index.SearchField'> and will be ignored
hidden is not a known attribute of class <class 'azure.search.documents.indexes.models._index.SearchField'> and will be ignored

Update
The version azure-search-documents==11.6.0b4 doesn't have this issue. I also checked the code and SearchField is not using anymore the upper class Model that was causing the warnings.

@xiangyan99  I can reproduce this issue. Can you please help take a look

It is still an issue, however it seems that it does not prohibit the functionality.

11.5.1 with the fix has been released.


Nothing really happens when i run the runbot.command command

/Users/Johan/Desktop/MusicBot/runbot_mac.command ; exit;
MacBook-Pro-13:~ Johan$ /Users/Johan/Desktop/MusicBot/runbot_mac.command ; exit;
/Users/Johan/Desktop/MusicBot/runbot_mac.command: line 8: python3.5: command not found
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.
[Process completed]
Thats basically everything that happens...

This is probably a PEBKAC, but i really don't get it.

Step 5 says:
"5: Run
In the main folder (called MusicBot), double-click update_macdeps.command to install the required Python dependencies. After it is finished, you can close the window and then double-click runbot_mac.command to run the bot.
If you close Terminal, your bot will stop working. This window is required to be open for the bot to run. The bot will also stop if you turn your computer off, sleep, or hibernate it. To avoid these issues, you can buy a dedicated server."
but how should the code really look in my terminal?

Im guessing its not reconising python3.5 as a command,
so maybe you don't have

Python installed
Pythan added to PATH


Add lua-fmt

Add lua-fmt.
(Why the formatter is called lua-fmt despite the executable being luafmt (no dash): lua-fmt and luafmt are two separate projects. The one added here is what format-all supports by default.)

Looks like lua-fmt hasn't been updated since 2018, I wouldn't recommend making this the default. Instead, look into stylua or LuaFormatter (I use the former)

stylua seems to be recommended more. I'll look into submitting that instead.

Closing in favor of https://github.com/radian-software/apheleia/pull/105.