Initial prebake image attempt

What type of PR is this?

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:
/kind bug

/kind cleanup

/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:
This PR provides a different approach to create prebake Nephio Sandbox images
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

/approve

/approved
/lgtm

/approved


Add "enabled" accessor to gem

Solves issue: https://github.com/Schwad/chat_gpt_error_handler/issues/2
This PR proposes adding an enabled accessor to the gem so that it can be opted into after the gem is added to an app.
It's false by default but once someone has set enabled to true, they'll need to have set an access token in their ENV or the initializer. The KeyError here happens currently if someone adds this gem to their app and boots it without an OPENAI_ACCESS_TOKEN
ChatGptErrorHandler.openai_access_token = ENV.fetch('OPENAI_ACCESS_TOKEN', nil)
ChatGptErrorHandler.enabled = ENV.fetch('CHAT_GPT_ERROR_HANDLER', false)

Added some small tests...not totally sure about their implementation 😅 so feedback welcome

I guess.........this is already a breaking change in a way? Folks who have installed this gem will find it stops doing anything unless they go and set enabled = true now. So perhaps it should be true by default?

Breaking changes are fine. We don't have a CHANGELOG if you want to add a default one with the 'unreleased' section with a line about your change? if so I'll merge! 🗡
Thanks so much for your contribution!

I've added a CHANGELOG & updated the README. Haven't had a chance to try this in a fresh app yet which I can do when I've a change if you'd prefer pre-merging
Thanks for taking a look at the work! Much appreciated 🙏

Amazing, thanks @tomajwinter
One nit it I might link to PRs from the changelog, but looks good to go! thanks for this!

Thanks @Schwad 🙏 - much appreciated


RFP - gitextensions.portable

Checklist

[x] The package I am requesting does not already exist on https://chocolatey.org/packages;
[x] There is no open issue for this package;
[x] The issue title starts 'RFP - ';
[x] The download URL is public and not locked behind a paywall / login;

Package Details
Software project URL: https://gitextensions.github.io/
Direct download URL for the software / installer: https://github.com/gitextensions/gitextensions/releases/download/v3.00.00/GitExtensions-Portable-<IP_ADDRESS>33.zip
Software summary / short description: same as package gitextensions
expectation

Embed the package.
Desktop shortcut (different location for admin v.s. non-admin installation).

Under review: https://chocolatey.org/packages/gitextensions.portable


[Event Change] Table 36 - "Sales Header" - OnUpdateSellToCustOnAfterSetFromSearchContact

Hi AL-Team,
can you please add the variable SearchContact by var to the following Publisher?
    [IntegrationEvent(false, false)]
    // local procedure OnUpdateSellToCustOnAfterSetFromSearchContact(var SalesHeader: Record "Sales Header"; SearchContact: Record Contact)
    local procedure OnUpdateSellToCustOnAfterSetFromSearchContact(var SalesHeader: Record "Sales Header"; var SearchContact: Record Contact)
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


FBSW-317 Integrate CodeCov with CICD

This change is

please rebase to latest develop - I fixed build problem so it should work for you now


add llama3's prompt template to conversation.py

#1426

@KazutoshiShinoda  can add preprocess_llama_3 func code? i will test it on prepare stage

what about prepocess during LazySupervisedDataset

Hi @KazutoshiShinoda, @awzhgw , @Jayantverma2 ,
I hope you are doing well. We have just released our project LLaVA++: Extending Visual Capabilities with LLaMA-3 and Phi-3, which features LLaMA-3 and Phi-3-Mini based LLaVA models. Please have a look at this at LLaVA++.

We have released the codes required to support both LLaMA-3 & Phi-3-Mini models in LLaVA framework. The chat formats and corresponding preprocess methods are available at our GitHub repo.
We released all the checkpoints on Hugging Face
On our GitHub repository we have provided .py files that needs to be replaced/added to official LLaVA repository to train and infer LLaMA-3 & Phi-3-Mini based models.

I hope this would be helpful. Please let me know if you have any questions. Thanks

@mmaaz60 In your implementation, I can see the following logic for preprocessing, but I don't quite understand  why
round_len -= 1 when i > 0. Could you explain that a little bit?
    for conversation, target in zip(conversations, targets):
        total_len = int(target.ne(tokenizer.pad_token_id).sum())

        rounds = conversation.split(conv.sep)
        re_rounds = [conv.sep.join(rounds[:3])]
        for conv_idx in range(3, len(rounds), 2):
            re_rounds.append(conv.sep.join(rounds[conv_idx:conv_idx + 2]))
        cur_len = 0
        target[:cur_len] = IGNORE_INDEX
        for i, rou in enumerate(re_rounds):
            if rou == "":
                break

            parts = rou.split(sep)
            if len(parts) != 2:
                break
            parts[0] += sep

            if has_image:
                round_len = len(tokenizer_image_token(rou, tokenizer)) + 1
                instruction_len = len(tokenizer_image_token(parts[0], tokenizer))
            else:
                round_len = len(tokenizer(rou).input_ids) + 1
                instruction_len = len(tokenizer(parts[0]).input_ids)

            if i > 0:
                round_len -= 1
                instruction_len -= 1

            target[cur_len: cur_len + instruction_len] = IGNORE_INDEX

            cur_len += round_len


release-tool.py: add approval subcommand

Add command to modify team approval state labels for release payloads.

/hold
In case you're still working!

Feel free to /unhold if/when you're ready

/hold cancel


EUI disables MPPatch

When I am using the UI mod Enhanced UI (https://forums.civfanatics.com/resources/civ5-enhanced-user-interface.24303/) MPPatch no longer functions.

Can confirm. I just ran into this issue myself.

This is happening for me as well. I was excited to try EUI out, but since I apparently can't have both I will have to uninstall it soon

Just ran into this myself, is this likely to be changed if its possible on this end?

I need the solution too, anyone know how put MMPatch priority to EUI?


Provide a way to integrate with other JSON library provider

Armeria uses Jackson data-bind for parsing and decoding JSON. A user may want to use other libraries than Jackson.
If there is a JSON interop layer in Armeria, users can easily integrate their favorite library(ie. gson, Kotlin klaxon, Scala circe..) with Armeria.
It has the advantage of supporting different JVM languages.

Indeed this would be appreciated. I find the Jackson APIs quite contrived when doing nontrivial serialization. And JSON-B is apparently the "standard", it's quite simple too, in my opinion :)
Right now AnnotatedValueResolver hardcodes JacksonRequestConverterFunction to be statically instantiated, which in turn adds startup overhead of com.fasterxml.jackson.databind.cfg.MapperBuilder.findAndAddModules, even if I'm not planning to use it.


feature: GESDISC management approval step

Description
This is a PR to support the GES DISC workflow, specifically to add a "Manager Approval Step" that no other role has access to.
Note: this has an associated dashboard PR

Adds a new privilege: "REQUEST_REVIEW_MANAGER"
Adds a new management_review step to the GES DISC workflow

Spec
See Ticket: https://bugs.earthdata.nasa.gov/browse/GESDISC-246

Validation

Make sure all merge request checks have passed (CI/CD).
Pull related branches locally.

Change Log
(copy/paste-able change log notes. check the box when the change is also in CHANGELOG.md)

[Add _____](link to commitid)
[Fix _____](link to commitid)

I may be able to help a little later in the week, but we'll need to include a couple other changes to complete this feature:

Need to update https://github.com/eosdis-nasa/earthdata-pub-api/blob/GUUI-3292-gesdisc-management-approval-step/src/postgres/9-updates.sql to include update sql commands which do what your changes in https://github.com/eosdis-nasa/earthdata-pub-api/pull/52/files#diff-9b7c6d89611d305c0a6e2d8aca261210159b847e0e8ad6a29d5d87a7b6784d17
Need to update https://github.com/eosdis-nasa/earthdata-pub-api/blob/GUUI-3292-gesdisc-management-approval-step/src/nodejs/lambda-handlers/submission.js#L150 to restrict API access to review management steps to manager privilege


starknet: describe how to use devnet flag

Current dependencies on/for this PR:

main

PR #107   👈

This comment was auto-generated by Graphite.


Fixes tiny grammatical issues

I stumbled upon this while reading the docs. This PR just adds a few commas and a missing 's'.

Thanks!


Redux refactoring steps

Sharing here what I have in mind for the big Redux refactoring.
Step 1 : Pagination
Migrate all the lists fetched from the API to use pagination
This is the currently ongoing step and is tracked in #751
Step 2 : Single entity retrieval
Migrate all the single entities retrieval to the new API.
This have been done for organizations in #752 for example, and will be tracked once #751 is closed.
Step 4 : Counts
Migrate counting operations to the new API.
For example: Getting the number of notifications.
Step 5  : PUT / PATCH / DELETE
Migrate these operations on single entities to the new API.
Example: Create/Update/Delete comment
Step 6 : Source tree cleaning
When step 5 is closed, all our directories will be looking like below since we will have removed all *.actions.js *.reducer.js *.types.js files:
src/organization/
├── index.js
└── screens
    ├── index.js
    └── organization-profile.screen.js

A PR will be made to get rid of the screens folder:
src/organization/
├── index.js
└── organization-profile.screen.js

Step 7 : Nested schemas in Normalizr & attributes clean up
For now, every Normalizr schema is independent. So a "repository" looks like:
{
  "id": 86202845,
  "name": "git-point",
  "full_name": "gitpoint/git-point",
  "owner": {
    "login": "gitpoint",
    "id": 30082377,
    "avatar_url": "https://avatars0.githubusercontent.com/u/30082377?v=4",
    "gravatar_id": "",
    "url": "https://api.github.com/users/gitpoint",
    "html_url": "https://github.com/gitpoint",
    "followers_url": "https://api.github.com/users/gitpoint/followers",
    "following_url": "https://api.github.com/users/gitpoint/following{/other_user}",
    "gists_url": "https://api.github.com/users/gitpoint/gists{/gist_id}",
    "starred_url": "https://api.github.com/users/gitpoint/starred{/owner}{/repo}",
    "subscriptions_url": "https://api.github.com/users/gitpoint/subscriptions",
    "organizations_url": "https://api.github.com/users/gitpoint/orgs",
    "repos_url": "https://api.github.com/users/gitpoint/repos",
    "events_url": "https://api.github.com/users/gitpoint/events{/privacy}",
    "received_events_url": "https://api.github.com/users/gitpoint/received_events",
    "type": "Organization",
    "site_admin": false
  },
  "private": false,
  "html_url": "https://github.com/gitpoint/git-point",
  "description": "GitHub in your pocket :iphone:",
  "fork": false,
  "url": "https://api.github.com/repos/gitpoint/git-point",
  "forks_url": "https://api.github.com/repos/gitpoint/git-point/forks",
  "keys_url": "https://api.github.com/repos/gitpoint/git-point/keys{/key_id}",
  "collaborators_url": "https://api.github.com/repos/gitpoint/git-point/collaborators{/collaborator}",
  "teams_url": "https://api.github.com/repos/gitpoint/git-point/teams",
  "hooks_url": "https://api.github.com/repos/gitpoint/git-point/hooks",
  "issue_events_url": "https://api.github.com/repos/gitpoint/git-point/issues/events{/number}",
  "events_url": "https://api.github.com/repos/gitpoint/git-point/events",
  "assignees_url": "https://api.github.com/repos/gitpoint/git-point/assignees{/user}",
  "branches_url": "https://api.github.com/repos/gitpoint/git-point/branches{/branch}",
  "tags_url": "https://api.github.com/repos/gitpoint/git-point/tags",
  "blobs_url": "https://api.github.com/repos/gitpoint/git-point/git/blobs{/sha}",
  "git_tags_url": "https://api.github.com/repos/gitpoint/git-point/git/tags{/sha}",
  "git_refs_url": "https://api.github.com/repos/gitpoint/git-point/git/refs{/sha}",
  "trees_url": "https://api.github.com/repos/gitpoint/git-point/git/trees{/sha}",
  "statuses_url": "https://api.github.com/repos/gitpoint/git-point/statuses/{sha}",
  "languages_url": "https://api.github.com/repos/gitpoint/git-point/languages",
  "stargazers_url": "https://api.github.com/repos/gitpoint/git-point/stargazers",
  "contributors_url": "https://api.github.com/repos/gitpoint/git-point/contributors",
  "subscribers_url": "https://api.github.com/repos/gitpoint/git-point/subscribers",
  "subscription_url": "https://api.github.com/repos/gitpoint/git-point/subscription",
  "commits_url": "https://api.github.com/repos/gitpoint/git-point/commits{/sha}",

a lot of this data (assignees_url, tags_url, ..) is irrelevant to us, and simply clutters the store.
a PR will be made to cherry pick what goes in the store by working on our schemas.
Additionnaly, we will start using nested Schemas, so that the "owner" point to the relevant Object for the store, instead of containing all its attribute:
{
  "id": 86202845,
  "name": "git-point",
  "full_name": "gitpoint/git-point",
  "owner": "gitpoint", // <---- This is the "id" of the organization in our store
  "private": false,
  "html_url": "https://github.com/gitpoint/git-point",
  "description": "GitHub in your pocket :iphone:",
 ....

Once done, our store will have a minimal footprint, and visiting the Events screen for example will pre-populate data for next screens. (performance ⚡)
Step 8 : GraphQL
With the store completely restructured, and schemas cherry picking kept attributes, adding GraphQL support should be really painless.
We'll just have to make it so that entities/attributes retrieved from GraphQL match our current structure, and things should work seamlessly. If needed, a second Proxy will be created along with new Schemas to adapt GraphQL attributes names.
Step 9 (or 7.5): Deep Linking
The idea here is to make sure that every screen of our application can be accessed directly, with an empty redux store.
More information about this: https://github.com/gitpoint/git-point/pull/752#discussion_r177601220
Once we're there, GitPoint should be able to intercept & handle any github.com URL, and we will have a nice deep linking feature. (#376)
Step 10: Why only github?
Now that we reached the mountain top, we will be able to consider making GitPoint compatible with GitLab / BitBucket:

Split RestClient into a base Client and a GitHubClient
Implement methods for the other providers with the same namespacing/prototypes as our GitHubClient.
Implement schemas for the new providers, so that once ran through normalizr(), their data structure match the data structure of GitHub entities.
Impement OAuth / Providers settings
Enjoy having the most powerful open source client out there 🎉

This is SO SO SO great.

It's funny, because I was having a discussion earlier with someone discussing the possibility to include GitLab/BitBucket functionality and although it's something down the line - with this thoughtful refactoring it's beyond possible (even though it's only 1 of the MANY reasons why these changes are going to be so useful). And it's all thanks to you mate 🎉 .
Thank you so much for writing this. We can send this link to anyone who we'll need to explain the architecture to.


Any plan to multilanguage training/implementation

For the current speech-to-speech (S2S) pipeline, the LLM typically supports both Chinese and English. If we aim to create an English S2S pipeline, it will be necessary to implement a new Speech-to-Text (STT) class (e.g., Whisper) and a Text-to-Speech (TTS) class (e.g., Parler TTS). Our immediate focus is on enhancing the web UI, improving inference speed, and supporting multiple users. Multi-language support is currently a lower priority. However, if anyone is interested in contributing to this feature, we are willing to provide assistance.


refactor and complete client.search.* mappings

This PR completes mappings for everything in the client.search package.  I have compared against Mojmap and Yarn mappings, but I don't believe that either has names that both accurately and intuitively describe what these things do in this case.
I have also made changes to the existing mappings:

IdentifierSearchTree, PlainTextSearchTree --> IdentifierSearcher, PlainTextSearcher

In Mojmap, Searcher, RefreshingSearcher, and these two are all known as search trees.  Additionally, these two have the features present in Searcher and RefreshingSearcher, and as such I believe their names should be consistent.

Searchable, RefreshingSearchable --> Searcher, RefreshingSearcher

As far as I understand, these interfaces are not implemented on types that can be searched, but rather on types whose purpose is to search another type.  As such, I think types implementing these interfaces could be easily confused with the types that are actually being searched if the names were to remain unchanged.  I do agree that the names Searcher and RefreshingSearcher are more intuitive than Mojmap's SearchTree and RefreshingSearchTree.

SearchManager.put --> SearchManager.registerProvider

I have compared to SoundManager in client.sound, where the word register is used rather than put.  I think this is more intuitive.

I think IdentifierSearch should be renamed.
Using Search would be ok if class instances were single-use, so it truly would be one search, but this class appears to be reusable.
It seems like the only reason not to call it IdentifierSearcher is that that name is currently taken.
Something along the lines of
IdentifierSearch -> IdentifierSearcher
IdentifierSearcher -> AbstractIdentifierSearcher
would be better I think, but using Abstract for an interface is weird.
If this gets renamed, PlainTextSearch would also have to be renamed.

Yeah, I knew that Search wasn't right but I knew they had to be different names and it was an existing name.  How about IdentifierSearcherInterface?  I know it isn't recommended to label interfaces in the names, but I would argue that this is a case where making an exception would be for the best.  It's the most easily understandable name given that they can't be the same.

I believe all suggestions have been applied.  I have renamed IdentifierSearcher and PlainTextSearcher to IdentifierSearcherInterface and PlainTextSearcherInterface for now, as IdentifierSearch and PlainTextSearch are being renamed to IdentifierSearcher and PlainTextSearcher.  Let me know if they aren't suitable names.

Yeah, I knew that Search wasn't right but I knew they had to be different names and it was an existing name. How about IdentifierSearcherInterface? I know it isn't recommended to label interfaces in the names, but I would argue that this is a case where making an exception would be for the best. It's the most easily understandable name given that they can't be the same.

Yeah the Interface suffix is also a bit strange, but I can't think of anything better. It's a sort of strange class separation in the first place so the names likely have to be a little strange to match.

this PR looks fantastic, thank you! my only comment: what's stopping you from calling this Factory instead of ProviderFunction? I think that would be better for conciseness

I'm just not that familiar with the factory pattern in Java.  I looked it up, but it didn't seem like a regular Function was really a factory (may be wrong).  It just extends Function.

I'm just not that familiar with the factory pattern in Java. I looked it up, but it didn't seem like a regular Function was really a factory (may be wrong). It just extends Function.

A 'factory' is just static method that always returns a new instance of the class it is a factory for.
It looks like all calls to SearchManager#registerProvider are passed lambdas that return new instances, so Factory seems appropriate here.

Renamed to factory.

moved to FCP for two days!

Just checking in, was this meant to be merged after two days of the FCP?

my mistake :p


typo: bulding -> building

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

officedocs-dev-word-pia/xml/Microsoft.Office.Interop.Word/WdBuildingBlockTypes.xml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Associated MCRA workshop videos

Is it possible to link or create MCRA videos that would present these slides. The CISO compass videos are quite helpful to understand these concepts in a better way than just the speakers notes.
Although the speaker notes are also quite detailed and is very good. IT would be helpful if we could have a few videos presenting these MCRA PPTs. It might be something that is already in the pipeline so in that case, feel free to ignore this feedback.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a5b0f5d1-01c7-baad-0540-24cebe0b5b84
Version Independent ID: f759fd8d-ce47-4a6f-27c5-f38003cd3464
Content: Microsoft Cybersecurity Reference Architectures - Security documentation
Content Source: security-docs/cybersecurity-reference-architecture/MCRA.md
Service: security
GitHub Login: @MarkSimos
Microsoft Alias: mas

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close


Track loading state per item page

Currently a new item just starts loading and replaces the previous one without notification once all necessary requests are done. This is not ideal as it makes it hard to know what is happening on the page currently after clicking on a new item if the request takes too long.
This can be solved by tracking all request on a page in a joint "loading" value and display a spinner during the loading process.

Closed in #59


Wrong HACS install

sorry to delete this template but I tried to install via HACS and it seems like install is going wrong. It will just install the component directly in custom_components folder and not in a sub directory. I created the folder but it complaints about blueprint not found when doing config check :/

added this to my configuration.yaml
# BluePrint

blueprint:

EVEN WORSE!
It will remove the WHOLE custom_component folder when uninstalling!!!! DANGERUS!!!

This component is not released yet and I haven't found a way to make HACS ignore it. I will remove it from the project to avoid any further issues.


Nested for loop

User input for number of rows
rows = int(input("Enter the rows:"))
Outer loop will print number of rows
for i in range(0,rows+1):
Inner loop will print number of Astrisk
for j in range(i):
    print("*",end = '')
print()

can someone guide me in this

so it will start from i=0
when i = 0 inner loop will not run and last print() will only execute
when i = 1 inner loop will iterate only once and print * only
and so on....
*
**

Hello, all,
After reading @aayushikanojiya 's issue, the original script asks for a number of rows from the user and, if provided with a valid int, will print i number of astricts corresponding to the iteration of the outermost for loop.
To put it more simply, if 3 was input by the user, the following output would occur:
*
**
***

However, there are some optimizations that I think may help make this more clear, as well as fulfill the initial issue's language. Firstly, please reference this w3schools article on Python's range function. Under the Defintion and Usage section, it states:
"The range() function returns a sequence of numbers, starting from 0 by default, and increments by 1 (by default), and stops before a specified number."
This means that we can remove the 0 from the range() function. Addtionalliy, the past of the issue said the number of rows was meant to be printed in the outermost for loop. With these changes in mind, we can modify the script to the following:
rows = int(input("Enter the rows:"))
for i in range(rows+1):
    print('Row: ' + str(i))
    for j in range(i):
        print("*",end = '')
    print()

This is the resulting output:
Enter the rows:3
Row: 0

Row: 1
*
Row: 2
**
Row: 3
***

Looking good so far, but we can actually tweak this further!
This next optimization really is a bit overkill, however, I think it's an important note to take into consideration. Though the issue was originally discussing a nest for loop, we can accomplish this same task without it. This script is not doing much that demands a lot of computational power. A large enough int, however, will cause really begin to slow down the script's output. This relates to the script's time complexity, which relates to the Big O notation which has us go down another rabbit hole, so don't worry about that for now - just keep in mind that the computer is working harder than it needs to.
So, how do we future proof this thing? Python is an amazing language and lets us do all types of things we can't do in other ones, such as C# or JavaScript. For instance, we can actually multiply strings. For example, if we were to run the following:
print('string'*2)

We would get the following outcome:
stringstring

That's crazy, right? If we take some creative liberties, we can further simplify this script, Check it out:
rows = int(input("Enter the rows:"))
for i in range(rows+1):
    string = '*'
    print(f'Row {i}: {string*i}\n')

If you're wondering what the f is in the print() function, it's what's known as a Formatted String Literal (f-Strings) and it simply allows us to represent and manipulate variables within the string without concatenating them using the + sign. Likewise, the \n is what's known as an Escape Sequence and allows us to add an extra space in the output string without having to call print() again.
I know that was a lot to go over, but I hope that this helped you understand the original script as well as pick up a few things along the way!


Insert "* " if enter new line inside a JsDoc comment

Current if entering a new line inside ad JsDoc comment, nothing is inserted in the new line.

Duplicate of #4430


Package metadata

The package should contain some metadata. There are some things to consider:

authors/maintainers

probably only maintainers, since we are not the authors of OpenCV

license must be probably the same as in OpenCV
Readme in rst format, there's probably some conversion tool which can be run in setup.py

Licensing information has been now updated: https://github.com/skvark/opencv-python/commit/9f4dcc2b3ed48693df5a5c6e96a3691439bc635c
The README file can be converted with pypandoc tool. This is now listed in requirements.txt but Linux builds may need to install pandoc separately to be able to use it.

Setup.py contains now necessary metadata and uses pypandoc for README conversion if possible.

It seems that pandoc installation gets too complicated so I just converted the README into rst format. It can be converted back to markdown when PyPI gets markdown support (https://github.com/pypa/packaging-problems/issues/46).


[JENKINS-35150] We can be more forgiving of users with misconfigured HTTPS front-ends

See JENKINS-35150
@reviewbybees

🐝

Even if we forgive them, other routines won't do so...
But 🐝

@oleg-nenashev this is true, but we have the ability to forgive them, so we might as well


fixed bug in Combinator

fixed bug in Combinator which adds pointers to unique empty trees to the rule cache when a rule produces no productions. This solves a problem where memory usage was spiralling upwards.

Thanks!


Symbols API: Empy value is returned for auto-property binding

namespace AutoProperty

type Class1() =
    member val Foo = 123 with get, set

Using results of GetAllUsesOfAllSymbolsInFile():

mfv.EnclosingEntity, mfv.IsProperty return false.
mfv.DisplayName, mfv.CompiledName return "v".

Interestingly enough, #3762 (and another commit that made it into VS 15.4) made it so that autoprop symbols are shown with Find Refs and Inline Rename.  Both appear to be broken on 15.5 Preview 3.


bitcoin gold

the site already have info about the upcoming segwit2x fork but still have no info or the splitted and freezed bitcoin gold fork

Bitcoin Gold has no publicly available software. Because their fork/snapshot has already passed, it will not be listed on the website.


Fix travis pipeline

The dummy pipeline for Travis needs to be replaced with a more suitable one. Perhaps just do a jekyll build and verify it performs correctly.

A fix has been deployed to run html checks on the GitHub pages


How do I build this

I tried to launch the code on a bot created for the occasion but do not know how to launch it (I have a .env file with a DISCORD_CLIENT_TOKEN variable with my bot token)

have you tried to console.log your token and see if it reads it?

maybe you are running it with npm start instead of npm run dev. The start doesn't run with dotenv in it.


Model validator

This PR adds two steps to the model compilation pipeline:

removal of all incomplete endpoints that are missing either a request or response type
validation of the internal consistency of the model (without looking at the REST spec)

Model validation can work in "just log errors" or "fail hard" modes. In this first iteration the model has some inconsistencies so we do not fail hard.
The validations are too numerous to detail here, the code has lots of comments detailing them.

I updated the PR after the removal of annotations.
I also added a validation that checks that a type that children (i.e. used in a implements or inherits) is not used as proprety type, because in that case we don't know what concrete type to instantiate for deserialization. Fixing it will require either refactoring the model or adding additional annotation to identify abstract classes. This happens e.g. with XPackUsage and ErrorCause.
Validations currently produces 119 errors. Some are definitely legit, some I will have to look more closely to understand if the validation is overly zealous (or blatantly wrong).

I also added a validation that checks that a type that has children (i.e. used in a implements or inherits) is not used as proprety type, because in that case we don't know what concrete type to instantiate for deserialization. Fixing it will require either refactoring the model or adding additional annotation to identify abstract classes. This happens e.g. with XPackUsage and ErrorCause.

Not all base classes are abstract so e.g ErrorCause should be able to used on its own. Can we update this check to mandate an @abstract true|false annotation on classes that are used as parents in the spec?

I've updated the validator and now agree with its output. There are more validation to add, but they will come in subsequent PRs.
There are 14 errors:
enum definition query_dsl:Operator - Duplicate enum member identifier 'AND'
enum definition query_dsl:Operator - Duplicate enum member identifier 'OR'
Endpoint ilm.delete_lifecycle / Request - Request path property 'policy_id' doesn't exist in endpoint URL templates
Endpoint ilm.put_lifecycle / Request - Request path property 'policy_id' doesn't exist in endpoint URL templates
enum definition ingest.processors:DateRounding - Duplicate enum member identifier 'M'
Endpoint mget / Response - Type document.multiple.multi_get.request:MultiGetRequest not found
Endpoint ml.delete_expired_data / Request - Url path property 'job_id' is missing in request definition
type_alias definition x_pack.info.x_pack_usage:UrlConfig / union_of / instance_of - Non-leaf type cannot be used here: 'x_pack.info.x_pack_usage:BaseUrlConfig'
request definition search.multi_search:MultiSearchRequest / body / Property 'operations' / dictionary_of / instance_of - 'search.search:SearchRequest' is a request and must only be used in endpoints
Endpoint render_search_template / Request - Url path property 'id' is missing in request definition
request definition modules.snapshot_and_restore.restore:RestoreRequest / body / Property 'index_settings' / instance_of - 'indices.index_settings.update_index_settings:UpdateIndexSettingsRequest' is a request and must only be used in endpoints
interface definition x_pack.sql.translate_sql:TranslateSqlResponse / Property 'result' / instance_of - 'search.search:SearchRequest' is a request and must only be used in endpoints
interface definition x_pack.watcher.input:SearchInputRequestDefinition / Property 'body' / instance_of - 'search.search:SearchRequest' is a request and must only be used in endpoints
interface definition x_pack.watcher.input:SearchInputRequestDefinition / Property 'template' / instance_of - 'search.search_template:SearchTemplateRequest' is a request and must only be used in endpoints
Model validation: 14 errors. 1681 types visited, 179 dangling types.

The "Auto label" task fails with path must not be empty - is this a known issue? How can we debug/fix that?


'Save As' does not truncate existing file leading to file corruption

Bug

NPE version: 4.5.62
Installed from: Windows Store

What is the current result?
Calling 'Save As' command and targeting an existing file copies its content but does not terminate contents correctly leaving previous old content at end of file. For example if the file is XML and was previously longer than the updated file content then the XML will potentially be invalid post 'Save As'.

What is the expected result?
Calling 'Save As' command and targeting an existing file should completely replace its content and none of the previous content should remain.

Are there any workarounds?
You can work around this by deleting the old destination file first. However if your not aware of this issue it may show up as errors (in our case corrupt XML) when opening file in other applications. We originally thought this was a bug in our own code that generated the file in the first place.

Is there a version in which it did work?
This is the first version I've used so not sure.

Is there a package on Nuget.org which shows the bug?
Not sure. I don't believe this is specific to any nuget package.

Do you have any repro steps? I'm looking at the code paths and don't see where this could be happening?
Thanks

Hi @onovotny
I noticed that you've already created a release for the fix for this issue (which I have verified works).
Do you still require repo steps?


prep_manjaro_client: command not found

Description
Script tries to call for a non-existent function.
General Troubleshooting

[X] I carefully followed the instructions in the README and successfully completed the setup wizard
[X] I read the ALVR Wikis here and here

Environment
Hardware
CPU:  Intel i9-9900K (16) @ 5.000GHz
GPU: NVIDIA GeForce RTX 2080 Ti Rev. A
Audio: PulseAudio
Hardware Details: hw-probe
Installation
ALVR Version: 16.0.0, I assume.
SteamVR Version: 1.20.4
Install Type: Source
OS Name and Version: Manjaro Linux - 5.10.84-1-MANJARO
Log: https://imgur.com/HoWcPPy.png

It was the script that didn't work, not a problem with the actual product.


fix: [BaseConfig] string value is set from environment variable even if it should be int/float

Description
Fixes #5688
Supersede #5704,  #5691 and #5690
Checklist:

[x] Securely signed commits
[x] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[x] Conforms to style guide

@MGatner

what about null handling?

This does nothing.

I think it could be quite common to have a Config with public property $foo; as int|null

Not so common. I think it might be bad design.
Now null is converted to a string. This PR changes nothing about null handling.
It is out of scope.
Do you really need null handling?

@MGatner If you type the property like your sample, it is no problem.
See the test passes.
If you don't type it like the following, string 20 is set in the $size.
class Widget extends BaseConfig
{
    property $size = null;
}

It seems typed properties would solve most of the type problems.
So I think we don't need to add extra logic to convert types.
This PR is enough to the current problems.

@paulbalandan Can I merge this?
Or you still have something wrong?

@paulbalandan still keen on your final opinion. @kenjis if he is unavailable over the next 48 hours let's proceed.


Reduce logging noise

The info logging for rsync adds a lot of noise to a test kitchen run. Would it be possible to switch that info output to debug or make it optional to display?

Hi,
That should be possible. Could you please post a small snippet of the log output you would like to get removed?

+1 here
Think, @armiller talking about this:
       [RSYNC] Time taken to upload /var/folders/7l/zfjgk97s69q6ylcmdlzw22s00000gn/T/default-ubuntu1404-chef11-sandbox-20151104-32518-1r5fser/cache to user@<IP_ADDRESS><{:user_known_hosts_file=>"/dev/null", :paranoid=>false, :port=>22, :compression=>true, :compression_level=>6, :keepalive=>true, :keepalive_interval=>60, :timeout=>15, :keys_only=>true, :keys=>["/path/to/my/keyfile"], :auth_methods=>["publickey"], :user=>"user"}>:/tmp/kitchen/cache: 1.89 sec
       [RSYNC] Time taken to upload /var/folders/7l/zfjgk97s69q6ylcmdlzw22s00000gn/T/default-ubuntu1404-chef11-sandbox-20151104-32518-1r5fser/client.rb to user@<IP_ADDRESS><{:user_known_hosts_file=>"/dev/null", :paranoid=>false, :port=>22, :compression=>true, :compression_level=>6, :keepalive=>true, :keepalive_interval=>60, :timeout=>15, :keys_only=>true, :keys=>["/path/to/my/keyfile"], :auth_methods=>["publickey"], :user=>"user"}>:/tmp/kitchen/client.rb: 1.75 sec
       [RSYNC] Time taken to upload /var/folders/7l/zfjgk97s69q6ylcmdlzw22s00000gn/T/default-ubuntu1404-chef11-sandbox-20151104-32518-1r5fser/cookbooks to user@<IP_ADDRESS><{:user_known_hosts_file=>"/dev/null", :paranoid=>false, :port=>22, :compression=>true, :compression_level=>6, :keepalive=>true, :keepalive_interval=>60, :timeout=>15, :keys_only=>true, :keys=>["/path/to/my/keyfile"], :auth_methods=>["publickey"], :user=>"user"}>:/tmp/kitchen/cookbooks: 7.82 sec
       [RSYNC] Time taken to upload /var/folders/7l/zfjgk97s69q6ylcmdlzw22s00000gn/T/default-ubuntu1404-chef11-sandbox-20151104-32518-1r5fser/data_bags to user@<IP_ADDRESS><{:user_known_hosts_file=>"/dev/null", :paranoid=>false, :port=>22, :compression=>true, :compression_level=>6, :keepalive=>true, :keepalive_interval=>60, :timeout=>15, :keys_only=>true, :keys=>["/path/to/my/keyfile"], :auth_methods=>["publickey"], :user=>"user"}>:/tmp/kitchen/data_bags: 2.17 sec
       [RSYNC] Time taken to upload /var/folders/7l/zfjgk97s69q6ylcmdlzw22s00000gn/T/default-ubuntu1404-chef11-sandbox-20151104-32518-1r5fser/dna.json to user@<IP_ADDRESS><{:user_known_hosts_file=>"/dev/null", :paranoid=>false, :port=>22, :compression=>true, :compression_level=>6, :keepalive=>true, :keepalive_interval=>60, :timeout=>15, :keys_only=>true, :keys=>["/path/to/my/keyfile"], :auth_methods=>["publickey"], :user=>"user"}>:/tmp/kitchen/dna.json: 1.72 sec
       [RSYNC] Time taken to upload /var/folders/7l/zfjgk97s69q6ylcmdlzw22s00000gn/T/default-ubuntu1404-chef11-sandbox-20151104-32518-1r5fser/environments to user@<IP_ADDRESS><{:user_known_hosts_file=>"/dev/null", :paranoid=>false, :port=>22, :compression=>true, :compression_level=>6, :keepalive=>true, :keepalive_interval=>60, :timeout=>15, :keys_only=>true, :keys=>["/path/to/my/keyfile"], :auth_methods=>["publickey"], :user=>"user"}>:/tmp/kitchen/environments: 1.70 sec
       [RSYNC] Time taken to upload /var/folders/7l/zfjgk97s69q6ylcmdlzw22s00000gn/T/default-ubuntu1404-chef11-sandbox-20151104-32518-1r5fser/nodes to user@<IP_ADDRESS><{:user_known_hosts_file=>"/dev/null", :paranoid=>false, :port=>22, :compression=>true, :compression_level=>6, :keepalive=>true, :keepalive_interval=>60, :timeout=>15, :keys_only=>true, :keys=>["/path/to/my/keyfile"], :auth_methods=>["publickey"], :user=>"user"}>:/tmp/kitchen/nodes: 1.66 sec
       [RSYNC] Time taken to upload /var/folders/7l/zfjgk97s69q6ylcmdlzw22s00000gn/T/default-ubuntu1404-chef11-sandbox-20151104-32518-1r5fser/roles to user@<IP_ADDRESS><{:user_known_hosts_file=>"/dev/null", :paranoid=>false, :port=>22, :compression=>true, :compression_level=>6, :keepalive=>true, :keepalive_interval=>60, :timeout=>15, :keys_only=>true, :keys=>["/path/to/my/keyfile"], :auth_methods=>["publickey"], :user=>"user"}>:/tmp/kitchen/roles: 1.88 sec
       [RSYNC] Time taken to upload /var/folders/7l/zfjgk97s69q6ylcmdlzw22s00000gn/T/default-ubuntu1404-chef11-sandbox-20151104-32518-1r5fser/validation.pem to user@<IP_ADDRESS><{:user_known_hosts_file=>"/dev/null", :paranoid=>false, :port=>22, :compression=>true, :compression_level=>6, :keepalive=>true, :keepalive_interval=>60, :timeout=>15, :keys_only=>true, :keys=>["/path/to/my/keyfile"], :auth_methods=>["publickey"], :user=>"user"}>:/tmp/kitchen/validation.pem: 1.79 sec

Sure, there is no need at least in in this info in each line: <{:user_known_hosts_file=>"/dev/null", :paranoid=>false, :port=>22, :compression=>true, :compression_level=>6, :keepalive=>true, :keepalive_interval=>60, :timeout=>15, :keys_only=>true, :keys=>["/path/to/my/keyfile"], :auth_methods=>["publickey"], :user=>"user"}> (in case of -l info of course).

Would like for [RSYNC] Time taken to upload... messages to go away as a whole or should it be truncated to something like [RSYNC] Time taken to upload /my/local/path/suites to /tmp/verifier/suites?

In my opinion, as test-kitchen output logs like Preparing data_bags, transport-rsync should also output info about transfers, in way:

debug: [RSYNC] Time taken to upload /var/folders/7l/zfjgk97s69q6ylcmdlzw22s00000gn/T/default-ubuntu1404-chef11-sandbox-20151104-32518-1r5fser/cache to user@<IP_ADDRESS><{:user_known_hosts_file=>"/dev/null", :paranoid=>false, :port=>22, :compression=>true, :compression_level=>6, :keepalive=>true, :keepalive_interval=>60, :timeout=>15, :keys_only=>true, :keys=>["/path/to/my/keyfile"], :auth_methods=>["publickey"], :user=>"user"}>:/tmp/kitchen/cache: 1.89 sec
info: [RSYNC] Time taken to upload /var/folders/7l/zfjgk97s69q6ylcmdlzw22s00000gn/T/default-ubuntu1404-chef11-sandbox-20151104-32518-1r5fser/cache to user@<IP_ADDRESS>:/tmp/kitchen/cache: 1.89 sec
warn: nothing

But, looks like @armiller want completely hide such logs in info level.

Ideally the rsync transport should mimic the default ssh transport where there are no additional messages during the transfer of files (other than the default transferring-files to ...). I think the [RSYNC] Time taken to upload... messages are more useful for debugging. So as a whole I think switching https://github.com/unibet/kitchen-transport-rsync/blob/master/lib/kitchen/transport/rsync.rb#L47 to debug would fix the nosiy output while still giving the user the option to view the information. Thoughts?

@armiller sounds reasonable to me.

0.1.2 released.
Please let me know if there is anything more you would like to be changed.

@i11++. Thanks for the quick response!

@i11 thanks!


[BUG] CLI’s non-index pages do not redirect to “default” version

What / Why

Non-index pages for the npm CLI docs do not currently redirect to the “default” version when omitting the version number (e.g., https://docs.npmjs.com/cli/commands/npx). Because of this, no permalink is available for docs pages to the most relevant version of particular commands (amongst other versioned resources). If this previously worked, those links are currently broken (see below).
When

Malfunctioning (?) for at least the past couple of months

Where

All versioned npm CLI documentation content on the website (npm/documentation repo) deeper than these indices:

https://docs.npmjs.com/cli/v8/commands
https://docs.npmjs.com/cli/v8/configuring-npm
https://docs.npmjs.com/cli/v8/using-npm

How
Current Behavior

Currently, users are only redirected to the npm CLI’s “default” version of docs pages for the “index” pages (e.g., https://docs.npmjs.com/cli/commands redirects to https://docs.npmjs.com/cli/v8/commands/).
Steps to Reproduce

Attempt to visit the “default” version of any page deeper than an “index” page by omitting the version number entirely (e.g., https://docs.npmjs.com/cli/commands/npx)

Expect to be redirected to the npm CLI’s “default” version of the docs page (e.g., https://docs.npmjs.com/cli/v8/commands/npx)

See the 404 error page instead (https://docs.npmjs.com/cli/commands/npx)

Expected Behavior

Be redirected to the npm CLI’s “default” version for docs page deeper than “index” pages when omitting the version number from the URL. Otherwise, we’d currently have to update links to, e.g., particular commands, every new major version of the npm CLI to avoid our links going stale.
Who

@darcyclarke
@ruyadorno
@MylesBorins

References

@rauschma’s Tweet inquiring about this functionality
@ethomson’s Tweet classifying it as a bug

title: Managing teams
redirect_from:

/orgs/managing-teams

@katelyn43

This was fixed by #242


Reify dictionary entries

Found this while bumping another project to use a later version. The error when running computations was:  fold1 cannot be converted; desugar first.

looks good :+1:

Hmm, breaks dictionary persistence.

ah - damn.
can we remove the reify from here, leave the desugar and check, but actually return the original, un-inlined "checked"?
then, when actually running or whatever, inline, desugar and reify before converting?

(this will give prettier info in :set too)

:mag:

all good :meat_on_bone:


Request to implement Shellyplus Smoke

I have some Shellyplus Smoke detectors which are not supported.
Could You please implement them?
Thanks Quaxx1507

Yep, fortunately the device itself is not so complicated, however i do not really like the Gen2 device documentation, Gen1 was way much better to understand.
Based on this article:
https://shelly-api-docs.shelly.cloud/gen2/ComponentsAndServices/Smoke
i guess this device sends data through /status/smoke:0 topic, you can download latest database from testing branch here:
https://raw.githubusercontent.com/enesbcs/shellyteacher4domo/testing/mqtt_templates_gen2.txt

Wow! That was fast :-)
I can confirm it is working.
Many thanks!


Exception: Error when fetching available tools: HTTPConnectionPool(host='localhost', port=8080): Read timed out. (read timeout=10)

Issue Description / 问题描述
When I follow the instruction to start to run the process with 'python run.py --task "put your task here" --model "chatglm3-6b" --config_file "assets/config.yml"' and I get the error
Steps to Reproduce / 复现步骤
I firstly do 'docker-compose up' to do the initialization by the documenation and execute run.py
Expected Behavior / 预期行为
I expect the agent will do the process correctly and return me the correct powerpoint file
Environment / 环境信息

Operating System / 操作系统：ubuntu 18.04
Python Version / Python 版本：3.10.13
Other Relevant Information / 其他相关信息：

Error Screenshots or Logs / 错误截图或日志
  File "/root/miniconda3/envs/xagent/lib/python3.10/site-packages/urllib3/connectionpool.py", line 537, in _make_request
    response = conn.getresponse()
  File "/root/miniconda3/envs/xagent/lib/python3.10/site-packages/urllib3/connection.py", line 461, in getresponse
    httplib_response = super().getresponse()
  File "/root/miniconda3/envs/xagent/lib/python3.10/http/client.py", line 1375, in getresponse
    response.begin()
  File "/root/miniconda3/envs/xagent/lib/python3.10/http/client.py", line 318, in begin
    version, status, reason = self._read_status()
  File "/root/miniconda3/envs/xagent/lib/python3.10/http/client.py", line 279, in _read_status
    line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
  File "/root/miniconda3/envs/xagent/lib/python3.10/socket.py", line 705, in readinto
    return self._sock.recv_into(b)
TimeoutError: timed out

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

Traceback (most recent call last):
  File "/root/miniconda3/envs/xagent/lib/python3.10/site-packages/requests/adapters.py", line 486, in send
    resp = conn.urlopen(
  File "/root/miniconda3/envs/xagent/lib/python3.10/site-packages/urllib3/connectionpool.py", line 845, in urlopen
    retries = retries.increment(
  File "/root/miniconda3/envs/xagent/lib/python3.10/site-packages/urllib3/util/retry.py", line 470, in increment
    raise reraise(type(error), error, _stacktrace)
  File "/root/miniconda3/envs/xagent/lib/python3.10/site-packages/urllib3/util/util.py", line 39, in reraise
    raise value
  File "/root/miniconda3/envs/xagent/lib/python3.10/site-packages/urllib3/connectionpool.py", line 791, in urlopen
    response = self._make_request(
  File "/root/miniconda3/envs/xagent/lib/python3.10/site-packages/urllib3/connectionpool.py", line 539, in _make_request
    self._raise_timeout(err=e, url=url, timeout_value=read_timeout)
  File "/root/miniconda3/envs/xagent/lib/python3.10/site-packages/urllib3/connectionpool.py", line 371, in _raise_timeout
    raise ReadTimeoutError(
urllib3.exceptions.ReadTimeoutError: HTTPConnectionPool(host='localhost', port=8080): Read timed out. (read timeout=10)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/data/mrx/agent/XAgent/XAgent/tool_call_handle.py", line 192, in get_available_tools
    response = requests.post(url, json=payload, timeout=10, cookies=self.cookies)
  File "/root/miniconda3/envs/xagent/lib/python3.10/site-packages/requests/api.py", line 115, in post
    return request("post", url, data=data, json=json, **kwargs)
  File "/root/miniconda3/envs/xagent/lib/python3.10/site-packages/requests/api.py", line 59, in request
    return session.request(method=method, url=url, **kwargs)
  File "/root/miniconda3/envs/xagent/lib/python3.10/site-packages/requests/sessions.py", line 589, in request
    resp = self.send(prep, **send_kwargs)
  File "/root/miniconda3/envs/xagent/lib/python3.10/site-packages/requests/sessions.py", line 703, in send
    r = adapter.send(request, **kwargs)
  File "/root/miniconda3/envs/xagent/lib/python3.10/site-packages/requests/adapters.py", line 532, in send
    raise ReadTimeout(e, request=request)
requests.exceptions.ReadTimeout: HTTPConnectionPool(host='localhost', port=8080): Read timed out. (read timeout=10)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/data/mrx/agent/XAgent/run.py", line 64, in <module>
    cmd.start(
  File "/data/mrx/agent/XAgent/command.py", line 195, in start
    self.run({
  File "/data/mrx/agent/XAgent/command.py", line 166, in run
    asyncio.run(server.interact(interaction=interaction))
  File "/root/miniconda3/envs/xagent/lib/python3.10/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/root/miniconda3/envs/xagent/lib/python3.10/asyncio/base_events.py", line 649, in run_until_complete
    return future.result()
  File "/data/mrx/agent/XAgent/XAgentServer/server.py", line 97, in interact
    subtask_functions, tool_functions_description_list = function_handler.get_functions(
  File "/data/mrx/agent/XAgent/XAgent/tool_call_handle.py", line 463, in get_functions
    output = toolserver_interface.get_available_tools()
  File "/data/mrx/agent/XAgent/XAgent/tool_call_handle.py", line 205, in get_available_tools
    raise Exception(f"Error when fetching available tools: {e}")
Exception: Error when fetching available tools: HTTPConnectionPool(host='localhost', port=8080): Read timed out. (read timeout=10)

Additional Notes / 其他备注
If you have any additional information or notes, please add them here. / 如果有其他补充信息，请在此处添加。

Here is the start log, basides, I checked the port with lsof -i but I did not see 8080 is used by any process
(xagent) root@iZ2zebrqxw523rv59ill69Z:/data/mrx/agent/XAgent/dockerfiles# docker-compose up
[+] Building 0.0s (0/0)                                                                                docker:default
[+] Running 5/0
 ✔ Container xagent-ToolServerNode-1     Created                                                                     0.0s
 ✔ Container xagent-db-1                 Created                                                                     0.0s
 ✔ Container XAgent-Server               Created                                                                     0.0s
 ✔ Container xagent-ToolServerMonitor-1  Created                                                                     0.0s
 ✔ Container xagent-ToolServerManager-1  Created                                                                     0.0s
Attaching to XAgent-Server, xagent-ToolServerManager-1, xagent-ToolServerMonitor-1, xagent-ToolServerNode-1, xagent-db-1
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:37.172+00:00"},"s":"I",  "c":"CONTROL",  "id":23285,   "ctx":"-","msg":"Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'"}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:37.173+00:00"},"s":"I",  "c":"NETWORK",  "id":4915701, "ctx":"-","msg":"Initialized wire specification","attr":{"spec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":13},"incomingInternalClient":{"minWireVersion":0,"maxWireVersion":13},"outgoing":{"minWireVersion":0,"maxWireVersion":13},"isInternalClient":true}}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:37.173+00:00"},"s":"W",  "c":"ASIO",     "id":22601,   "ctx":"main","msg":"No TransportLayer configured during NetworkInterface startup"}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:37.173+00:00"},"s":"I",  "c":"NETWORK",  "id":4648601, "ctx":"main","msg":"Implicit TCP FastOpen unavailable. If TCP FastOpen is required, set tcpFastOpenServer, tcpFastOpenClient, and tcpFastOpenQueueSize."}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:37.174+00:00"},"s":"W",  "c":"ASIO",     "id":22601,   "ctx":"main","msg":"No TransportLayer configured during NetworkInterface startup"}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:37.174+00:00"},"s":"I",  "c":"REPL",     "id":5123008, "ctx":"main","msg":"Successfully registered PrimaryOnlyService","attr":{"service":"TenantMigrationDonorService","ns":"config.tenantMigrationDonors"}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:37.174+00:00"},"s":"I",  "c":"REPL",     "id":5123008, "ctx":"main","msg":"Successfully registered PrimaryOnlyService","attr":{"service":"TenantMigrationRecipientService","ns":"config.tenantMigrationRecipients"}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:37.174+00:00"},"s":"I",  "c":"CONTROL",  "id":5945603, "ctx":"main","msg":"Multi threading initialized"}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:37.174+00:00"},"s":"I",  "c":"CONTROL",  "id":4615611, "ctx":"initandlisten","msg":"MongoDB starting","attr":{"pid":1,"port":27017,"dbPath":"/data/db","architecture":"64-bit","host":"8c5ad536eb4a"}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:37.174+00:00"},"s":"I",  "c":"CONTROL",  "id":23403,   "ctx":"initandlisten","msg":"Build Info","attr":{"buildInfo":{"version":"5.0.5","gitVersion":"d65fd89df3fc039b5c55933c0f71d647a54510ae","openSSLVersion":"OpenSSL 1.1.1f  31 Mar 2020","modules":[],"allocator":"tcmalloc","environment":{"distmod":"ubuntu2004","distarch":"x86_64","target_arch":"x86_64"}}}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:37.174+00:00"},"s":"I",  "c":"CONTROL",  "id":51765,   "ctx":"initandlisten","msg":"Operating System","attr":{"os":{"name":"Ubuntu","version":"20.04"}}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:37.174+00:00"},"s":"I",  "c":"CONTROL",  "id":21951,   "ctx":"initandlisten","msg":"Options set by command line","attr":{"options":{"net":{"bindIp":"*"},"security":{"authorization":"enabled"}}}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:37.175+00:00"},"s":"I",  "c":"STORAGE",  "id":22270,   "ctx":"initandlisten","msg":"Storage engine to use detected by data files","attr":{"dbpath":"/data/db","storageEngine":"wiredTiger"}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:37.175+00:00"},"s":"I",  "c":"STORAGE",  "id":22297,   "ctx":"initandlisten","msg":"Using the XFS filesystem is strongly recommended with the WiredTiger storage engine. See http://dochub.mongodb.org/core/prodnotes-filesystem","tags":["startupWarnings"]}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:37.175+00:00"},"s":"I",  "c":"STORAGE",  "id":22315,   "ctx":"initandlisten","msg":"Opening WiredTiger","attr":{"config":"create,cache_size=62442M,session_max=33000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),builtin_extension_config=(zstd=(compression_level=6)),file_manager=(close_idle_time=600,close_scan_interval=10,close_handle_minimum=250),statistics_log=(wait=0),verbose=[recovery_progress,checkpoint_progress,compact_progress],"}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:37.924+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"[1701068497:924930][1:0x7fb47f62bc80], txn-recover: [WT_VERB_RECOVERY_PROGRESS] Recovering log 5 through 6"}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:37.963+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"[1701068497:963807][1:0x7fb47f62bc80], txn-recover: [WT_VERB_RECOVERY_PROGRESS] Recovering log 6 through 6"}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:38.024+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"[1701068498:24049][1:0x7fb47f62bc80], txn-recover: [WT_VERB_RECOVERY_ALL] Main recovery loop: starting at 5/23168 to 6/256"}}
xagent-ToolServerMonitor-1  | INFO:      Database connected
xagent-ToolServerMonitor-1  | INFO:      Docker client connected
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:38.103+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"[1701068498:103570][1:0x7fb47f62bc80], txn-recover: [WT_VERB_RECOVERY_PROGRESS] Recovering log 5 through 6"}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:38.148+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"[1701068498:148416][1:0x7fb47f62bc80], txn-recover: [WT_VERB_RECOVERY_PROGRESS] Recovering log 6 through 6"}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:38.188+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"[1701068498:188390][1:0x7fb47f62bc80], txn-recover: [WT_VERB_RECOVERY_ALL] Set global recovery timestamp: (0, 0)"}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:38.188+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"[1701068498:188426][1:0x7fb47f62bc80], txn-recover: [WT_VERB_RECOVERY_ALL] Set global oldest timestamp: (0, 0)"}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:38.189+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"initandlisten","msg":"WiredTiger message","attr":{"message":"[1701068498:189103][1:0x7fb47f62bc80], WT_SESSION.checkpoint: [WT_VERB_CHECKPOINT_PROGRESS] saving checkpoint snapshot min: 1, snapshot max: 1 snapshot count: 0, oldest timestamp: (0, 0) , meta checkpoint timestamp: (0, 0) base write gen: 5220"}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:38.193+00:00"},"s":"I",  "c":"STORAGE",  "id":4795906, "ctx":"initandlisten","msg":"WiredTiger opened","attr":{"durationMillis":1018}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:38.194+00:00"},"s":"I",  "c":"RECOVERY", "id":23987,   "ctx":"initandlisten","msg":"WiredTiger recoveryTimestamp","attr":{"recoveryTimestamp":{"$timestamp":{"t":0,"i":0}}}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:38.194+00:00"},"s":"I",  "c":"STORAGE",  "id":4366408, "ctx":"initandlisten","msg":"No table logging settings modifications are required for existing WiredTiger tables","attr":{"loggingEnabled":true}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:38.195+00:00"},"s":"I",  "c":"STORAGE",  "id":22262,   "ctx":"initandlisten","msg":"Timestamp monitor starting"}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:38.199+00:00"},"s":"I",  "c":"NETWORK",  "id":4915702, "ctx":"initandlisten","msg":"Updated wire specification","attr":{"oldSpec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":13},"incomingInternalClient":{"minWireVersion":0,"maxWireVersion":13},"outgoing":{"minWireVersion":0,"maxWireVersion":13},"isInternalClient":true},"newSpec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":13},"incomingInternalClient":{"minWireVersion":13,"maxWireVersion":13},"outgoing":{"minWireVersion":13,"maxWireVersion":13},"isInternalClient":true}}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:38.199+00:00"},"s":"I",  "c":"STORAGE",  "id":5071100, "ctx":"initandlisten","msg":"Clearing temp directory"}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:38.200+00:00"},"s":"I",  "c":"CONTROL",  "id":20536,   "ctx":"initandlisten","msg":"Flow Control is enabled on this deployment"}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:38.200+00:00"},"s":"I",  "c":"FTDC",     "id":20625,   "ctx":"initandlisten","msg":"Initializing full-time diagnostic data capture","attr":{"dataDirectory":"/data/db/diagnostic.data"}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:38.201+00:00"},"s":"I",  "c":"REPL",     "id":6015317, "ctx":"initandlisten","msg":"Setting new configuration state","attr":{"newState":"ConfigReplicationDisabled","oldState":"ConfigPreStart"}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:38.202+00:00"},"s":"I",  "c":"NETWORK",  "id":23015,   "ctx":"listener","msg":"Listening on","attr":{"address":"/tmp/mongodb-27017.sock"}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:38.202+00:00"},"s":"I",  "c":"NETWORK",  "id":23015,   "ctx":"listener","msg":"Listening on","attr":{"address":"<IP_ADDRESS>"}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:38.202+00:00"},"s":"I",  "c":"NETWORK",  "id":23016,   "ctx":"listener","msg":"Waiting for connections","attr":{"port":27017,"ssl":"off"}}
xagent-ToolServerNode-1     | Build complete. Exiting...
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:38.581+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:60702","uuid":"0f34927a-e3f4-4221-949b-d58953c68ce6","connectionId":1,"connectionCount":1}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:38.581+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn1","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:60702","client":"conn1","doc":{"driver":{"name":"PyMongo|Motor","version":"4.6.0|3.3.2"},"os":{"type":"Linux","name":"Linux","architecture":"x86_64","version":"4.15.0-213-generic"},"platform":"CPython 3.10.13.final.0|asyncio"}}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:38.582+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:60704","uuid":"5e780926-a036-4f85-93d1-80964c4a7669","connectionId":2,"connectionCount":2}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:38.582+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:60716","uuid":"2c1c4361-8e99-41d0-a983-459da7210d0c","connectionId":3,"connectionCount":3}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:38.582+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn2","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:60704","client":"conn2","doc":{"driver":{"name":"PyMongo|Motor","version":"4.6.0|3.3.2"},"os":{"type":"Linux","name":"Linux","architecture":"x86_64","version":"4.15.0-213-generic"},"platform":"CPython 3.10.13.final.0|asyncio"}}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:38.582+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn3","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:60716","client":"conn3","doc":{"driver":{"name":"PyMongo|Motor","version":"4.6.0|3.3.2"},"os":{"type":"Linux","name":"Linux","architecture":"x86_64","version":"4.15.0-213-generic"},"platform":"CPython 3.10.13.final.0|asyncio"}}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:01:38.589+00:00"},"s":"I",  "c":"ACCESS",   "id":20250,   "ctx":"conn3","msg":"Authentication succeeded","attr":{"mechanism":"SCRAM-SHA-256","speculative":true,"principalName":"admin","authenticationDatabase":"admin","remote":"<IP_ADDRESS>:60716","extraInfo":{}}}
xagent-ToolServerNode-1 exited with code 0
xagent-ToolServerManager-1  | [2023-11-27 07:01:39 +0000] [1] [INFO] Starting gunicorn 21.2.0
xagent-ToolServerManager-1  | [2023-11-27 07:01:39 +0000] [1] [INFO] Listening at: http://<IP_ADDRESS>:8080 (1)
xagent-ToolServerManager-1  | [2023-11-27 07:01:39 +0000] [1] [INFO] Using worker: uvicorn.workers.UvicornWorker
xagent-ToolServerManager-1  | [2023-11-27 07:01:39 +0000] [7] [INFO] Booting worker with pid: 7
xagent-ToolServerManager-1  | [2023-11-27 07:01:39 +0000] [8] [INFO] Booting worker with pid: 8
xagent-ToolServerManager-1  | [2023-11-27 07:01:39 +0000] [9] [INFO] Booting worker with pid: 9
xagent-ToolServerManager-1  | [2023-11-27 07:01:39 +0000] [10] [INFO] Booting worker with pid: 10
XAgent-Server               | INFO:     Will watch for changes in these directories: ['/app']
XAgent-Server               | INFO:     Uvicorn running on http://<IP_ADDRESS>:8090 (Press CTRL+C to quit)
XAgent-Server               | INFO:     Started reloader process [1] using StatReload
xagent-ToolServerManager-1  | [2023-11-27 07:01:39 +0000] [8] [INFO] Started server process [8]
xagent-ToolServerManager-1  | [2023-11-27 07:01:39 +0000] [8] [INFO] Waiting for application startup.
xagent-ToolServerManager-1  | [2023-11-27 07:01:39 +0000] [8] [INFO] Application startup complete.
xagent-ToolServerManager-1  | [2023-11-27 07:01:39 +0000] [7] [INFO] Started server process [7]
xagent-ToolServerManager-1  | [2023-11-27 07:01:39 +0000] [7] [INFO] Waiting for application startup.
xagent-ToolServerManager-1  | [2023-11-27 07:01:39 +0000] [7] [INFO] Application startup complete.
xagent-ToolServerManager-1  | [2023-11-27 07:01:39 +0000] [9] [INFO] Started server process [9]
xagent-ToolServerManager-1  | [2023-11-27 07:01:39 +0000] [9] [INFO] Waiting for application startup.
xagent-ToolServerManager-1  | [2023-11-27 07:01:39 +0000] [10] [INFO] Started server process [10]
xagent-ToolServerManager-1  | [2023-11-27 07:01:39 +0000] [10] [INFO] Waiting for application startup.
xagent-ToolServerManager-1  | [2023-11-27 07:01:39 +0000] [9] [INFO] Application startup complete.
xagent-ToolServerManager-1  | [2023-11-27 07:01:39 +0000] [10] [INFO] Application startup complete.
XAgent-Server               | INFO:     Started server process [8]
XAgent-Server               | INFO:     Waiting for application startup.
XAgent-Server               | INFO:     Application startup complete.
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:02:33.690+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:54936","uuid":"49f60a14-0ef8-4f76-b2eb-fbb22b9ec99e","connectionId":4,"connectionCount":4}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:02:33.690+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn4","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:54936","client":"conn4","doc":{"driver":{"name":"PyMongo|Motor","version":"4.6.0|3.3.2"},"os":{"type":"Linux","name":"Linux","architecture":"x86_64","version":"4.15.0-213-generic"},"platform":"CPython 3.10.13.final.0|asyncio"}}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:02:33.692+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:54952","uuid":"02e6d05f-4fb6-4c9b-aff1-319bfb5147e2","connectionId":5,"connectionCount":5}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:02:33.692+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:54964","uuid":"6c60e881-5c38-41c7-bbd9-04a8d6e6b7c8","connectionId":6,"connectionCount":6}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:02:33.692+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn5","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:54952","client":"conn5","doc":{"driver":{"name":"PyMongo|Motor","version":"4.6.0|3.3.2"},"os":{"type":"Linux","name":"Linux","architecture":"x86_64","version":"4.15.0-213-generic"},"platform":"CPython 3.10.13.final.0|asyncio"}}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:02:33.692+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn6","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:54964","client":"conn6","doc":{"driver":{"name":"PyMongo|Motor","version":"4.6.0|3.3.2"},"os":{"type":"Linux","name":"Linux","architecture":"x86_64","version":"4.15.0-213-generic"},"platform":"CPython 3.10.13.final.0|asyncio"}}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:02:33.698+00:00"},"s":"I",  "c":"ACCESS",   "id":20250,   "ctx":"conn6","msg":"Authentication succeeded","attr":{"mechanism":"SCRAM-SHA-256","speculative":true,"principalName":"admin","authenticationDatabase":"admin","remote":"<IP_ADDRESS>:54964","extraInfo":{}}}
vigorous_chatelet           | INFO:     Started server process [1]
vigorous_chatelet           | INFO:     Waiting for application startup.
vigorous_chatelet           | Starting Docker: docker.
vigorous_chatelet           | INFO:     Register env FileSystemEnv with 3 tools!
vigorous_chatelet           | WARNING:  Bing API key is not provided, rollback to duckduckgo.
vigorous_chatelet           | INFO:     Register env WebEnv with 2 tools!
vigorous_chatelet           | INFO:     Register env PythonNotebook with 2 tools!
vigorous_chatelet           | INFO:     Register tool shell_command_executor!
vigorous_chatelet           | INFO:     Loaded 8 tools and 3 envs!
vigorous_chatelet           | INFO:     Application startup complete.
vigorous_chatelet           | INFO:     Uvicorn running on http://<IP_ADDRESS>:31942 (Press CTRL+C to quit)
vigorous_chatelet           | INFO:     <IP_ADDRESS>:34674 - "GET / HTTP/1.1" 200 OK
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:02:36.708+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:45400","uuid":"5db86630-a3c9-41e4-8a06-8092b48f5a99","connectionId":7,"connectionCount":7}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:02:36.708+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn7","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:45400","client":"conn7","doc":{"driver":{"name":"PyMongo|Motor","version":"4.6.0|3.3.2"},"os":{"type":"Linux","name":"Linux","architecture":"x86_64","version":"4.15.0-213-generic"},"platform":"CPython 3.10.13.final.0|asyncio"}}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:02:36.709+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:45404","uuid":"45795e4b-f73b-41a6-a64d-f9d919a62aba","connectionId":8,"connectionCount":8}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:02:36.710+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn8","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:45404","client":"conn8","doc":{"driver":{"name":"PyMongo|Motor","version":"4.6.0|3.3.2"},"os":{"type":"Linux","name":"Linux","architecture":"x86_64","version":"4.15.0-213-generic"},"platform":"CPython 3.10.13.final.0|asyncio"}}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:02:36.710+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"Connection accepted","attr":{"remote":"<IP_ADDRESS>:45412","uuid":"4908357b-3da4-4cec-9c6d-1a2a050693a9","connectionId":9,"connectionCount":9}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:02:36.710+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn9","msg":"client metadata","attr":{"remote":"<IP_ADDRESS>:45412","client":"conn9","doc":{"driver":{"name":"PyMongo|Motor","version":"4.6.0|3.3.2"},"os":{"type":"Linux","name":"Linux","architecture":"x86_64","version":"4.15.0-213-generic"},"platform":"CPython 3.10.13.final.0|asyncio"}}}
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:02:36.715+00:00"},"s":"I",  "c":"ACCESS",   "id":20250,   "ctx":"conn9","msg":"Authentication succeeded","attr":{"mechanism":"SCRAM-SHA-256","speculative":true,"principalName":"admin","authenticationDatabase":"admin","remote":"<IP_ADDRESS>:45412","extraInfo":{}}}
vigorous_chatelet           | INFO:     <IP_ADDRESS>:34688 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:34704 - "GET / HTTP/1.1" 200 OK
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:02:38.199+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"Checkpointer","msg":"WiredTiger message","attr":{"message":"[1701068558:199125][1:0x7fb476e19700], WT_SESSION.checkpoint: [WT_VERB_CHECKPOINT_PROGRESS] saving checkpoint snapshot min: 7, snapshot max: 7 snapshot count: 0, oldest timestamp: (0, 0) , meta checkpoint timestamp: (0, 0) base write gen: 5220"}}
vigorous_chatelet           | INFO:     <IP_ADDRESS>:34714 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:34736 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:34754 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:34780 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:34794 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:34818 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36168 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36188 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36216 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36228 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36244 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36262 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36294 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36312 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36330 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36354 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:40898 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:40922 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:40930 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:40940 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:40952 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:40966 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:40978 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:41002 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:41030 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:37898 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:37922 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:37946 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:37958 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:37976 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:37992 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:38016 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:38036 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:38060 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:38088 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:50154 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:50178 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:50186 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:50204 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:50220 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:50230 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:50254 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:50270 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:50286 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:50308 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:33906 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:33924 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:33942 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:33964 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:33974 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:34000 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:34024 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:34038 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:34044 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:41580 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:41604 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:41614 - "GET / HTTP/1.1" 200 OK
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:03:38.209+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"Checkpointer","msg":"WiredTiger message","attr":{"message":"[1701068618:209615][1:0x7fb476e19700], WT_SESSION.checkpoint: [WT_VERB_CHECKPOINT_PROGRESS] saving checkpoint snapshot min: 9, snapshot max: 9 snapshot count: 0, oldest timestamp: (0, 0) , meta checkpoint timestamp: (0, 0) base write gen: 5220"}}
vigorous_chatelet           | INFO:     <IP_ADDRESS>:41624 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:41644 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:41674 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:41690 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:41714 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:41724 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:41744 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:43918 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:43940 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:43966 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:43984 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:44004 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:44024 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:44030 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:44046 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:44066 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:52576 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:52586 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:52604 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:52626 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:52638 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:52664 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:52678 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:52688 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:52698 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:52718 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:59474 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:59492 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:59510 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:59520 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:59532 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:59546 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:59552 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:59576 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:59598 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:38620 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:38626 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:38640 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:38658 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:38672 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:38688 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:38712 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:38734 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:38752 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:38768 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36310 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36324 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36336 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36358 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36370 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36392 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36418 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36446 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36470 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:47190 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:47206 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:47228 - "GET / HTTP/1.1" 200 OK
xagent-db-1                 | {"t":{"$date":"2023-11-27T07:04:38.213+00:00"},"s":"I",  "c":"STORAGE",  "id":22430,   "ctx":"Checkpointer","msg":"WiredTiger message","attr":{"message":"[1701068678:213046][1:0x7fb476e19700], WT_SESSION.checkpoint: [WT_VERB_CHECKPOINT_PROGRESS] saving checkpoint snapshot min: 11, snapshot max: 11 snapshot count: 0, oldest timestamp: (0, 0) , meta checkpoint timestamp: (0, 0) base write gen: 5220"}}
vigorous_chatelet           | INFO:     <IP_ADDRESS>:47250 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:47256 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:47262 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:47274 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:47292 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:47308 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:47324 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36552 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36568 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36584 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36602 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36626 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36646 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36662 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36676 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:36682 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:60066 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:60088 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:60102 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:60110 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:60126 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:60140 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:60158 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:60166 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:60180 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:60188 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:54470 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:54490 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:54502 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:54532 - "GET / HTTP/1.1" 200 OK
vigorous_chatelet           | INFO:     <IP_ADDRESS>:54546 - "GET / HTTP/1.1" 200 OK

Please pull the latest images and try again! It seems that you encounter errors in docker network, maybe a reboot or a upgrade of docker can solve the problem

Please pull the latest images and try again! It seems that you encounter errors in docker network, maybe a reboot or a upgrade of docker can solve the problem

Thanks for the reply. Yes, your are right I have the network issue on my server because I user a http-proxy to connect to the internet. I meet the network issue when I tried to build to dockerfile with docker-compose. The network issue is so annoying so that's why I used my laptop to build and upload images to the server.
I was thinking that after I uploading the images to server, there is not internet required to process with my local deployed LLM. But I would like to ask that why do we need internet for playing locally? Or do we have another way to deal with it? Thanks in advance

Please pull the latest images and try again! It seems that you encounter errors in docker network, maybe a reboot or a upgrade of docker can solve the problem

Thanks for the reply. Yes, your are right I have the network issue on my server because I user a http-proxy to connect to the internet. I meet the network issue when I tried to build to dockerfile with docker-compose. The network issue is so annoying so that's why I used my laptop to build and upload images to the server.
I was thinking that after I uploading the images to server, there is not internet required to process with my local deployed LLM. But I would like to ask that why do we need internet for playing locally? Or do we have another way to deal with it? Thanks in advance

The internet access is required to installing depends and allows XAgent browse website. The docker is also required to make XAgent have full control of the shell, like install missing packages automatically, setup services like database/website.

Please pull the latest images and try again! It seems that you encounter errors in docker network, maybe a reboot or a upgrade of docker can solve the problem

Thanks for the reply. Yes, your are right I have the network issue on my server because I user a http-proxy to connect to the internet. I meet the network issue when I tried to build to dockerfile with docker-compose. The network issue is so annoying so that's why I used my laptop to build and upload images to the server.
I was thinking that after I uploading the images to server, there is not internet required to process with my local deployed LLM. But I would like to ask that why do we need internet for playing locally? Or do we have another way to deal with it? Thanks in advance

After you setup the docker containers, it should be fine to run the XAgent. But as you mentioned that you set up local deployed LLM, please make sure the model support function calling or run our XAgentGen with XAgentLlama(34B is recommanded). Hope you a pleasure day : ) !

Please pull the latest images and try again! It seems that you encounter errors in docker network, maybe a reboot or a upgrade of docker can solve the problem

Thanks for the reply. Yes, your are right I have the network issue on my server because I user a http-proxy to connect to the internet. I meet the network issue when I tried to build to dockerfile with docker-compose. The network issue is so annoying so that's why I used my laptop to build and upload images to the server.
I was thinking that after I uploading the images to server, there is not internet required to process with my local deployed LLM. But I would like to ask that why do we need internet for playing locally? Or do we have another way to deal with it? Thanks in advance

After you setup the docker containers, it should be fine to run the XAgent. But as you mentioned that you set up local deployed LLM, please make sure the model support function calling or run our XAgentGen with XAgentLlama(34B is recommanded). Hope you a pleasure day : ) !

Thanks, you are so kind. I have two questions, the first one is now I use http://url:port/v1 for model base, but there is also http://url:port/v1/chat/completions, which one do you support. The second question is that if there is a safe way to change 8080 port?

Please pull the latest images and try again! It seems that you encounter errors in docker network, maybe a reboot or a upgrade of docker can solve the problem

Thanks for the reply. Yes, your are right I have the network issue on my server because I user a http-proxy to connect to the internet. I meet the network issue when I tried to build to dockerfile with docker-compose. The network issue is so annoying so that's why I used my laptop to build and upload images to the server.
I was thinking that after I uploading the images to server, there is not internet required to process with my local deployed LLM. But I would like to ask that why do we need internet for playing locally? Or do we have another way to deal with it? Thanks in advance

After you setup the docker containers, it should be fine to run the XAgent. But as you mentioned that you set up local deployed LLM, please make sure the model support function calling or run our XAgentGen with XAgentLlama(34B is recommanded). Hope you a pleasure day : ) !

Thanks, you are so kind. I have two questions, the first one is now I use http://url:port/v1 for model base, but there is also http://url:port/v1/chat/completions, which one do you support. The second question is that if there is a safe way to change 8080 port?

If your api support openai official schema, try to use http://url:port/v1. If you does not use command line to run XAgent, you can just close port mapping for toolserver in docker-compose.yml. Else you should you should modify docker-compose.yml and assets/config.yml:

Change 8080 port mapping for ToolServerManager in docker-compose.yml
Change 8080 port of selfhost_toolserver_url in assets/config.yml
Note that XAgent  support remote ToolServer, thus you can change selfhost_toolserver_url to the url that provide toolserver access.

Please pull the latest images and try again! It seems that you encounter errors in docker network, maybe a reboot or a upgrade of docker can solve the problem

Thanks for the reply. Yes, your are right I have the network issue on my server because I user a http-proxy to connect to the internet. I meet the network issue when I tried to build to dockerfile with docker-compose. The network issue is so annoying so that's why I used my laptop to build and upload images to the server.
I was thinking that after I uploading the images to server, there is not internet required to process with my local deployed LLM. But I would like to ask that why do we need internet for playing locally? Or do we have another way to deal with it? Thanks in advance

After you setup the docker containers, it should be fine to run the XAgent. But as you mentioned that you set up local deployed LLM, please make sure the model support function calling or run our XAgentGen with XAgentLlama(34B is recommanded). Hope you a pleasure day : ) !

Thanks, you are so kind. I have two questions, the first one is now I use http://url:port/v1 for model base, but there is also http://url:port/v1/chat/completions, which one do you support. The second question is that if there is a safe way to change 8080 port?

If your api support openai official schema, try to use http://url:port/v1. If you does not use command line to run XAgent, you can just close port mapping for toolserver in docker-compose.yml. Else you should you should modify docker-compose.yml and assets/config.yml:

Change 8080 port mapping for ToolServerManager in docker-compose.yml
Change 8080 port of selfhost_toolserver_url in assets/config.yml
Note that XAgent  support remote ToolServer, thus you can change selfhost_toolserver_url to the url that provide toolserver access.

Thank you so much, here is my configuration on the assets/config.yml file
chatglm3-6b:
    - api_key: None
      api_base: http://<IP_ADDRESS>:8098/v1
      api_type: open_ai
      model: chatglm3-6b

Besides, may I ask that why is that if I use the GUI way to start XAgent I don't need a port mapping and if I run with command with run.py then I need a port mapping? How could I access everything if I use the GUI? Hope to hear from you

The XAgentServer connect other container through a docker network bridge, which does not require package transmission over host networks. Thus you does not need a port forward. The current version of Web GUI has support almost every feature of XAgent. If you have more question, please open a new discussion or pull request.


Use base primitives from terra 0.22

Summary
Since qiskit-terra 0.22 was released, we can use the base primitives from it. Unfortunately we still need the local _circuit_key which is not in the 0.22 release.
Details and comments
Putting in draft until I can confirm it works with QRT primitives (waiting on the Sampler fix)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 4 (100.0%)  changed or added relevant lines in 4 files are covered.
66 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.9%) to 64.295%

Files with Coverage Reduction
New Missed Lines
%

qiskit_ibm_runtime/qiskit/primitives/base_sampler.py
29
29.2%

qiskit_ibm_runtime/qiskit/primitives/base_estimator.py
37
24.83%

Totals

Change from base Build<PHONE_NUMBER>:
-0.9%

Covered Lines:
3434

Relevant Lines:
5341

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

4 of 4 (100.0%)  changed or added relevant lines in 4 files are covered.
66 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.9%) to 64.295%

Files with Coverage Reduction
New Missed Lines
%

qiskit_ibm_runtime/qiskit/primitives/base_sampler.py
29
29.2%

qiskit_ibm_runtime/qiskit/primitives/base_estimator.py
37
24.83%

Totals

Change from base Build<PHONE_NUMBER>:
-0.9%

Covered Lines:
3434

Relevant Lines:
5341

💛  - Coveralls

It's ok to use the local (qiskit-ibm-runtime) _circuit_key. After 0.23, let's use Terra's one.

🎉


Add Y-Foundry CW20 Token to Juno & Y-Foundry DApp

Added Y-Foundry DAO information to Juno chain + Images
Also added Y-Foundry DAO App Info + Image to dApp
linted } line

hello https://app.yfoundry.io/ dapp is not working. Please fix it to exclude dapps.

dApp is down for maintenance, resubmitted a new PR with just token information.
Will send a second PR later after the dApp is live.
Thanks!


Deprecated: Return type of CurrencyCloud\Model\PayerRequirementDetails::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

For php 8.1

@darijuxs thanks for raising this issue. We will take a closer look