Discussion about pyimgui future

Hello everyone!
As you may have seen, changes are coming. First of all, the repo is now an organization one, which will be easier to manage as a team project. Due to work overload, our dear @swistakm is not able to manage the project anymore and has to retire from the development. The change to an organization repo is here to support this and to allow the project to move forward without him. We can't thank him enough for what he started and I hope he will succeed in his numerous projects outside 'pyimgui'!
In his absence, I inherited admin right on this repository and we have carte blanche for the evolution of the project. I say 'we' because I don't expect to stay the lone manager of pyimgui. I wish to gather a small core team of active contributors that is willing to organize at my side the future of pyimgui. Feel free to contact me (or responds to this post) if you are interested.
I am not yet very familiar with every functionality of GitHub, thus I expect your help to discuss the organization of the repository. What is the best way to manage such a project? Any proposal is welcome to be discussed here.
Concerning the direct future, I think it is time to prepare next major release. I will soon go on pending push requests and merge what needs to be merged. After that, I will look for the merging of the big upgrade to the latest dear imgui, pr #192. I do not have the access to PyPi yet, this will have to wait a little bit. In the meantime, there is still stuff to do on the upgrade before releasing it.

The 'Table' functionalities are to be reviewed a little bit to ease their use and make it feel more natural coming from python.
Documentation may be improved and completed
Many functions have been obsoleted and removed from Dear ImGui since 1.65. During the upgrade, I have dutifully noted them with comments in the source code. How should we deal with them for the release? I think of listing them in the release note. But maybe we should keep a binding that drops an error in case of usage?

We also have to settle on the question of distributing pyimgui as an external dll (which would help with external modules that are wishing to extend pyimgui) or compiled in pyimgui (which facilitate version management and distribution). I don't think this needs to be decided for the next release and can be developed in the future.
For future developpement, we also need to discuss how we will organize futures catch-up with dearimgui upgrades. v1.83 is already here! Should we create an "upgrade" branch which tends to be in sync with dearimgui? Or do we keep working on the master branch?
The question of dearimgui docking branch is back on the table. I was thinking of a branch in pyimgui that is in sync with their dev branch. This rise the question of distributing such a branch. Should we distribute it with PyPi like a normal module? Or do we keep it as a manual installation with documented instructions? Maybe, if we manage to allow easy extension of pyimgui (e.g. with external dll), it would be possible to develop this as an extension (and perhaps another repo of the pyimgui organization)?
I would love to hear about your insights on all that subjects and I hope we will be able to make great things with this project. Feel free to comments and criticize any of my suggestions. As I have said, I am not an expert on the subject and I need your help to manage the project properly. I probably have forgotten many things, please adds them to the discussion.
Best,
KinoxKlark

Hey,
Some random ideas:

Make github issues for 'todo' items, so that contributors have an easier time picking tasks
Is it possible to have multiple PyPi packages? if so, then the whole docking/deprecated thing could be solved like:

One 'primary' package that is more or less close to a recent Dear ImGui
One package that has the docking feature enabled
One package that has deprecated things enabled (In the primary package they could either nag or just straight out not be there)
One package that has Dear ImGui as 'external' module.

For following new versions, it would make sense to stabilize first, and then in the future, based on how fast updates are coming out / how much work it is to upgrade decide on a strategy?

Hello @KinoxKlark,
first of all: thank you very much to take over responsibility for this project!
You wrote:

Concerning the direct future, I think it is time to prepare next major release. I will soon go on pending push requests and merge what needs to be merged. After that, I will look for the merging of the big upgrade to the latest dear imgui, pr #192. [...]
* Many functions have been obsoleted and removed from Dear ImGui since 1.65. During the upgrade, I have dutifully noted them with comments in the source code. How should we deal with them for the release? I think of listing them in the release note. But maybe we should keep a binding that drops an error in case of usage?

I'd do this in a two step process:

merge pull requests that should be merged, fix issues that should be fixed, make a minor release (1.4.0)
merge #192, drop support for EOL Python releases, drop obsoleted and removed functionality, make a major release (2.0.0)

(Dropping support for EOL Python is announced for 2.0.0 in the 1.3.0 Release.)

Yes, it is indeed a good idea. Thanks.

Sorry to answer so late to that, but so about the DLL question, I believe we could use a pattern similar to what's being used for PySDL2: the DLL is distributed by itself as a separate package (could be pyimgui-dll or something), and then the bindings are a python pure wrapper around it, making the package way simpler to deploy and update (no need for building wheels and such)
The other perk we would get from that is the possibility of creating python bindings for implot, either as a separate repo (pyimplot?) or as part of pyimgui

I like that idea as well, it is simple and flexible. I will have to give it a deep thought, try some things, and choose the best option.
I think I will soon push a minor release with recently merged PR and start putting the new major release together. I'll create a branch for the upgrade where I'll merge #192 and where we will try to solve the DLL question. Since it seems to be a major manipulation of the library architecture I think it is best fitting the new major release. It will push the release date a little bit but I think it is better if all possible breaking changes comes simultaneously on a major release.

Shouldn't the DLL question be addressed in a later major release? The next major release being the 1.82 branch.

I think it mostly depends on your capacity. I'd be fine with having them both in the same release, but it might not be worth it if it means postponing 2.0 for several months.
I'd have gladly helped on that, but I won't have any time this year unfortunately, maybe in 2022 though.

Hello, I am not sure that "addon" for dear imgui such as imnodes or implot should be baked inside pyimgui. The reason for that is that if we decide to include one of them, there is no reason to not include every other one of them. Every user of pyimgui doesn't necessarily need all these possibilities and shouldn't be forced to download them just to access the core imgui functionalities. (Without saying that it would be a nightmare to maintains in the long run).
These functionalities are clearly interesting, but it may be preferable to implement them as external modules that depend on pyimgui and are installable separately. And, for this to work, we need to implement the DLL functionality.
I think the plan for now is:

Releasing 1.4.0 with its various bug fixes and small functionalities ASAP
Releasing 2.0 with the upgrade to a more recent version of dear imgui soon after 1.4.0
Working on the DLL functionality in order to permit the implementation of external modules such as implot or imnodes and find a good solution concerning the docking branch

As usual, I am open to suggestions.
I am currently a bit overbooked and I can't work on the new release as much as I want (We may have troked a busy project manager for another busy project manager ^^). I think the only remaining things are to fix the Linux building pipeline (may need some help with that) and ensuring that all little details are correctly set (version number in files, documentation, etc).

Thanks a lot for your valuable insight!
I may be a little biased regarding that question but I don't think of DearPyGui as a competitor of pyimgui. As I understand it, DearPyGui has for objective to propose a complete Retained Mode GUI using in backend DearImGui, which is an Immediate Mode GUI. Pyimgui is a more direct binding of DearImGui and is thus an immediate mode GUI tool. Both have radically different philosophies and thus have a different target audience. The proposal of DearPyGui is to gives their users a complete GUI backend on which to build their applications, i.e. construct a user interface. Pyimgui proposes a lightweight library that one can load on top of his application to quickly display pieces of information in an immediate mode. It is the reason why pyimgui can support so many backends, in fact, one could graft it to any backends, even if not officially distributed with the package (distributed backends are only examples of integration that are already delivered as python code in the package). The main difference between DearPyGui and pyimgui is that the first one is an all in one tool to create GUI and the latter one is a small extra that you add on top of your existing application to not reinvent the wheel and help you render GUI.
It is because of that difference that I am not so inclined to include many other addons of DearImGui to this binding. In my understanding of the philosophy of pyimgui, the user should have the choice of what he is adding to its application, and bindings of implot or imnodes should only come as extra packages.
However, you make very good points concerning the ambitions of the project versus the actual resources that are allowed to it and we should be careful about that. Indeed, it is better to ship something quickly than never ship anything, waiting for the perfect moment. As I see it, both 1.4 and 2.0 are mostly ready to be shipped. I have to solve some issues with the linux build pipeline in order to build the wheels and releases them on pypi. For 2.0 I will have to do a quick "quality" pass, mostly to be sure that the documentation is consistent, that the version number is correct everywhere, and so on, but functionalities are here and some already use the branch in their project for several months. It is in that regard that I think the discussed roadmap is feasible. Concerning the DLL functionalities, it is not really fixed yet. Some tests have been done to studies the possibilities. But all that should wait until 2.0 is out.
You are more than welcome to start a binding of imnodes inside pyimgui if you need it. I don't think that it would be included in 2.0 since, as I said, 2.0 is mostly done. But it would be a good start for what is coming next, whether for inclusion inside pyimgui as you suggested or for the separation in an external package using the DLL functionalities.

No indeed, I don't think they should, you are right. Unfortunately, I didn't have time to go over every one of them. Some should be closed, others should wait until releases, and so on.
Maybe you could help me with that by pointing which ones should be closed? Or is there a way to designate volunteers as moderator or some similar roles? (I am not used to all functionalities of GitHub)

The triage role roughly looks what you are probably asking for:
https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization
I would be willing to close some tickets or apply labels, but cannot give any guarantee about my availability.

On GitHub repo administration:

You seem to have been saying lots of "this is fixed in 2.0" in issues. Why not make a PR or Draft PR for the 2.0 branch, which you can link issues to. This goes for past issues as well.
On my repos, I like to make "Feature Track" issues, which aggregate all issues and PRs related to a certain feature for the lifetime of the project and are a place for discussing a feature. The Discussions feature might be a better fit for that; I haven't tried it yet though.

I make a project with "quality level" columns Discarded, Legacy, Unimplemented, Work in Progress, Stopgap, Feature Complete, and Robust + Correct. I fill it in with Feature Track issues, sorting the features subjectively based on their code quality.

Thanks for the suggestion, it is indeed a good idea. Previously we had the PR #192 which started all of it and which was referred to. Made the #224 PR for discussing 2.0 in general.

I hope this is the right place to pitch this idea.
Something I believe would be very beneficial to pyimgui is a simple way for average users to share their custom widgets made using the library, and I really liked how this is handled in upstream imgui: an issue label called "useful widgets".
Creating issues is quick and easy to do, and allows for easier management compared to setting up a separate repo or committing in the examples directory. Also provides a centralized place for newcomers to see what cool things can be created using pyimgui. I myself have a few such widgets (file browser / picker, star rating widget and a few others) that, while being simple and rudimental, might come in handy to someone else.
I'm sorry if this has been considered already, but I couldn't find any mention of it in the issues...

I have created #282 for this purpose, feel free to post there for now.
If the current simple setup does not prove to be working, we'll think about something else.


Error while improving the project: '/dev/null'

Policy and info

Maintainers will close issues that have been stale for 14 days if they contain relevant answers.
Adding the label "sweep" will automatically turn the issue into a coded pull request. Works best for mechanical tasks. More info/syntax at: https://docs.sweep.dev/

Expected Behavior
I ran GPT Engineer against a project and requested a few changes to update the project.  I expected it to apply some changes especially since gtpe generated a lot of patches.
Current Behavior
GPTE says no changes applied.
Failure Information
Ran using ChatGPT.  You can recreate this by cloning the project located at https://github.com/sec-tools/litefuzz and asking GPT Engineer to make some refactoring changes.
Here's the prompt I used:
Here's a fuzzing tool written in Python.  We need to refactor the code so that it adheres to best practices for modern application architecture.

Also I want the code to support the addition of new mutators.  All mutators should inherit from an abstract base class which takes a mutate() method that takes a file as input and returns a mutated version of the file.

With the file selection:
[files]
"misc.py" = "selected"
"run.py" = "selected"
"test_litefuzz.py" = "selected"
"config.py" = "selected"
# LICENSE = "selected"
"net.py" = "selected"
"litefuzz.py" = "selected"
"mutator.py" = "selected"
# "INSTALL.md" = "selected"
"core.py" = "selected"
#"README.md" = "selected"
"triage.py" = "selected"
"cli.py" = "selected"
"debug.py" = "selected"
"settings.py" = "selected"
"fuzz.py" = "selected"

Failure Logs
If your project includes a debug_log_file.txt, kindly upload it from your_project/.gpteng/memory/ directory. This file encompasses all the necessary logs. Should the file prove extensive, consider utilizing GitHub's "add files" functionality.
debug_log_file.txt

Heya @jasonsgraham, we just discussed this internally and will be looking into it. Our @similato87 is taking the lead on this one, too! 🙏

Hi @jasonsgraham, I'm believe that the recent commit, which introduces "dev/null/" as new files for parsing, has addressed the issue. Could you kindly pull the latest from the main branch and give it another go?

I am no longer getting the error.  Thanks!


Rewrite some code and fixed library behavior

Hello!
I've fixed alphabet characters set for #2.
Also I founded that your for-loop for step variable runs in reversed order. I thought that this is looks not good also because this is not the same different as original implementation.
Also I've rewrite your code a little bit.

Hello, thank you for assembling this pull request!
But I see some issues to address:

You've included the "ModuleSymbhasOwnPr" prefix to the alphabet. Adding the prefix to the JavaScript module makes sense because the gzip algorithm compresses better with it (here is the detailed explanation). In our case, adding the prefix does not make sense as the library is executed server-side :)
You reversed the access order by index inside the "FormatString" function. I do not understand why it's changed, I'd like to have a detailed explanation.

Also, you've included Makefile to the PR. Can you explain the benefits of including it to this repo?
Again, thank you for creating this PR!

Nevertheless, I've taken into account some of your proposals and released new versions of the package. Thank you!


Update handler for JSON fields

Hey, I was looking into the default updateHandler you created and for my usecase I would always be thrown into the Error:
https://github.com/marceljuenemann/rxdb-supabase/blob/main/src/supabase-replication.ts#L260
I suspect because my id field is a uuid in supabase?
So I created my own updateHandler:
push: {
        updateHandler: async (row: RxReplicationWriteToMasterRow<any>) => {
          let query = supabase.from(collections.dumps.name).update(row.newDocumentState, { count: 'exact' });
          Object.entries(row.assumedMasterState!).forEach(([field, value]) => {
            if (field === 'id') {
              query = query.eq(field, value);
            }
          });
          const { error, count } = await query;
          if (error) throw error;
          return count == 1;
        },
      },

And I just wanted to see what you think?
Mainly im not too sure why yours is so complicated compared to just using the id always?
Do you foresee any issues here?

The error you linked to is thrown if the JavaScript type is unsupported, i.e. if you are trying to store an array or object instead of a string or number. It doesn't know about the database type. UUID should be no problem if it's a string in JavaScript.
The default update handler only updates a row if all the fields match the expected state, so if the row was modified by a different client (e.g. a different user or on a different device changed the state while the current client was offline), it will not be updated. Your handler will always update the row, so if your app goes back online, it might override any changes done in the meantime.

The reason the library doesn't support arrays is just that AFAIK there isn't an easy way to compare equality with the supabase client for array or JSON columns.
If you write your own update handler, you can either create your own logic to determine the new values of the rows (e.g. merging tags?), or just ignore the tags field (i.e. check for field === 'tags')
The README of this project should certainly give more guidance on this. Maybe there could also be an option to ignore certain fields, so when you pass the tags field, it would ignore the field for the equality checks

Well, RxDB also knows what the state before the update was locally. If there was no conflicting update from a different client, then that state should be the same as the remote state. Hence this is called assumedMasterState.
The defaultUpdateHandler generates a query like this:
UPDATE foo
SET a=newState.a, b=newState.b
WHERE a=assumedMasterState.a AND b=assumedMasterState.b
So the problem here is just that I didn't know how to do b=assumedMasterState.b if b is an array or JSON object column

Hi,
I had the same problem today and wanted to share my findings.
This should do it:
private async defaultUpdateHandler(
    row: RxReplicationWriteToMasterRow<RxDocType>,
  ): Promise<boolean> {
    let query = this.options.client
      .from(this.table)
      .update(row.newDocumentState, {
        count: 'exact',
      })

    Object.entries(
      row.assumedMasterState!,
    ).forEach(([field, value]) => {
      const type = typeof value
      if (type === 'string' || type === 'number') {
        query = query.eq(field, value)
      } else if (type === 'boolean' || value === null) {
        query = query.is(field, value)
      } else if (type === 'object') {
        query = query.containedBy(field, value)
      } else {
        throw new Error(`replicate: Unsupported field of type ${type}`)
      }
    })
    const { error, count } = await query
    if (error) throw error
    return count === 1
  }

See: https://supabase.com/docs/reference/javascript/containedby?example=on-jsonb-columns
Best,
Colin

@colin-chadwick interesting, that certainly looks like a step in the right direction! containedBy doesn't check for equality though, but rather whether all the elements in the database field are also in the value passed. So there could be cases where the value was modified in the database, yet we still override those changes. Which kind of breaks the contract of the defaultUpdateHandler (although this might be fine in your case or other people's cases).
I guess if we used both containedBy and contains together, that would actually check for equality though :) I'd like to look more into how this handles nested objects, and whether it actually is an equality check, but there might be a general solution here.

 It works for my case, but I think when this is combined with contains, this could be a general solution. I'll keep you posted in case I find something helpful. 🙂

So containedBy plus contains translates to A <@ B AND A @> B in Postgres, which isn't the same as equals because it does not compare the ordering of array elements (see here). I think that's a problem because it's not uncommon to use a JSON field to store the ordering of some elements.
That said, if you use a jsonb field instead of json, a simple = operator actually does what we want in Postgres. So I think the problem when I wrote this code was just that the supabase client did not correctly translate JSON values into an eq. Postgres query. This might just be solved by now, or it should be possible to solve with a pull request to supabase.


Upgrade to pandas >2.0

Would be great to upgrade this repo to use pandas > 2.0.0

can you share a screenshot or any other details?


NFDIV-2504 Update opening times

Updating contact centre opening times
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/NFDIV-2504
Before merging a pull request make sure that:

[x] tests have been updated / new tests has been added (if needed)
[x] README and other documentation has been updated / added (if needed)

If this ticket will have any visible impact on users and is not behind a feature toggle, make sure that:

[ ] this ticket been reviewed by QA
[ ] the user story been signed off by the PO

Note that bug fixes, dependency updates and technical tasks do not directly impact the user experience and can be merged without QA and PO review.
If this user story cannot be immediately merged find a way to put it behind a feature toggle and get it merged.

duplicate pr


[EDIT] 3 monitor setup detection

Not sure what the problem is since I am not running 8.1 but several Win8.1 users have notified me that it does not detect anything except for the game window in 8.1.

Not sure if it's the same problem or not, but screen capture also doesn't work with my triple monitor setup (Windows 7). I get no error message on the log, but it was visible that it wasn't working (the app didn't recognize any event that wasn't coming purely from the game log).
I did some digging through the code and after some quick hacks to check out the output of the capture, it turns out the problem is related to the Win BitBlt function. At least on my system, this function is "caching" the first capture it does, and always returns the same bitmap afterwards. It works fine if:
a) I use a single monitor
b) I disable Aero (no idea why, it was just a hunch to try this)
One possible solution for this is to revert back to standard Java capture (using the Robot class). I saw in the code that this code path is only used if the game is in "fullscreen", but otherwise it uses a C/JNA implementation.
My tweak was to change the getHSWindowBounds function to return the window client bounds in screen coordinates, and then always use robot.createScreenCapture(bounds) in getScreenCapture().
public Rectangle getHSWindowBounds() {
RECT bounds = new RECT();
POINT topLeft = new POINT();
    /*
    User32Extra.INSTANCE.GetWindowRect(windowHandle, bounds);
    */

    User32Extra.INSTANCE.GetClientRect(windowHandle, bounds); // get client coords
    topLeft.x = bounds.left;
    topLeft.y = bounds.top;
    User32Extra.INSTANCE.ClientToScreen(windowHandle, topLeft); // convert top-left
    bounds.left = topLeft.x;
    bounds.top = topLeft.y;
    bounds.right = bounds.right + bounds.left;
    bounds.bottom = bounds.bottom + bounds.top;

    return bounds.toRectangle();
}

This had very little testing, but seems to work perfectly fine in my system. Hope this helps.


.mjs

If .mjs becomes the standard way to name an es module, then that might simplify everything because we can just transpile all .mjs files...and that .mjs file can be typescript or not, and we'll just transpile it. We need to make sure that our typescript plugins will still work for .mjs files

Well, I sure hope this doesn't happen. Even if it does, everything should work fine because Zwitterion can handle arbitrary extensions


Propagate annotations to podman's kube struct

This change propagates the annotations defined in the workload object metadata that are prefixed podman/ to podman's kube structure. The changes are aimed for podman v4.2.0.
This forces several changes:

update podman package dependency to v4.2.0-rc1
migrate to golang 1.17 due to podman's update (cilium needs 1.17 minimum)

$> make build
...
# github.com/cilium/ebpf
vendor/github.com/cilium/ebpf/marshalers.go:102:22: unsafe.Slice requires go1.17 or later (-lang was set to go1.16; check go.mod)
make: *** [Makefile:108: build] Error 2

go mod vendor update due to migration to golang 1.17

This change allows passing the crun annotation run.oci.keep_original_groups:1 from the edgeworkload to podman and enable crun to keep the same host groupIDs  in the container. With this change, it is possible to access devices in /dev/ using file system permissions.
There is a more modest workaround to this change, which is to add the annotation to all containers using the configuration in containers.conf.
Still, this change is not sufficient to allow interacting with certain devices as SELinux forbids it due to invalid access rules.
For instance, in case of a webcam, SELinux still expects to have the following additional access rights:
module v4linux 1.0;

require {
	type v4l_device_t;
	type container_t;
	class chr_file { getattr ioctl map open read write };
}

#============= container_t ==============
allow container_t v4l_device_t:chr_file { getattr ioctl open read write };
allow container_t v4l_device_t:chr_file map;

There is a flag in SELinux that allows some operations by containers to devices (container_use_devices), but it lacks the map operation for the case of a webcam.
[root@localhost-live ~]# sesearch -A -s container_t -t v4l_device_t -c chr_file
allow container_domain device_node:chr_file { append getattr ioctl lock open read write }; [ container_use_devices ]:True
``

rpm build is failing because it won't build for f35 (golang 1.16). Can we move to f36 and deprecate f35?

No, Golang 1.16 is rhel 8 and is needed, I already revert commits for 1.17 twice, please keep 1.16 pray

Can we use rhel 9 then?

@eloycoto @masayag I've removed the changes to migrate to go 1.17. Can you take another look?

I build rpm based on this PR and failed to verify it on fc36 with podman-4.2-rc1.
I had to add the devices's group-id to flotta user and disable selinux, which is the same things as using podman-4.1.

Adding the supplementary group is needed in any scenario. The annotation instructs crun to propagate the same groupids from the flotta user to the container. The default is to create new group ids that don't match in id inside the container.


Add more metadata along with contract

The builds on and extends #241 which is a great idea.
When we upload code, we upload a ~200kB wasm blob.
There is no reason we cannot add even 20kB of metadata like schemas and other references. Let's collect more ideas besides the JSON schemas and see which make sense:

[ ] json-schema-to-typescript interfaces (as this is primary user of json schemas)
[ ] source code??? (rather than a link)
[ ] links to helpers.ts script (as @orkunkl suggested here: https://github.com/CosmWasm/docs2/pull/73#discussion_r470449702)
[ ] links to deployed webapp frontends (or maybe that belongs with the contract, not code)

I wonder if this makes sense to add all of them on the Code itself, or as annotations. In this case, the key technical items - schemas, ts interface, maybe source code would go on the Code. We would then allow any number of "Annotations" that can be attached to a Code blob, not only by the owner. These are suggestions, as {Type, URL} pairs
{
  Type: "cosmjs/cli",
  URL: "https://raw.githubusercontent.com/CosmWasm/cosmwasm-plus/master/contracts/cw20-base/helpers.ts",
  By: "coral162d3zk45ufaqke5wgcd3kh336k6p3kwwkdj3ma",
}

{
  Type: "dApp",
  URL: "https://dapps.coralnet.cosmwasm.com/cw20",
  By: "coral1e86v774dch5uwkks0cepw8mdz8a9flhhapvf6w",
}

// we can even add some "code review" type comments here as claims
{
  Type: "Audit",
  URL: "???",
  By: "coral1dyual04q9m3f0a7qsvfx4hvu8ceyrxw9yldp8w",
}

{
  Type: "Bug"
  URL: "???",
  By: "coral1dyual04q9m3f0a7qsvfx4hvu8ceyrxw9yldp8w",
}

@alpe @webmaster128 I would be curious for your opinions here when you have time. Nothing urgent, just may be a nice polish for 1.0.

I like the idea to store metadata. 🌷
This can be very powerful feature for various use cases that people will come up with.
Though we need some structure and permissions in place at some point so that this does not go wild.
For example if everybody can add metadata to codes then how do we prevent scammers?
The metadata may be displayed in web UIs so it should be safe and (partly) human readable
I can imagine that we want to store metadata with codes and contracts separately. For example: the code was audited by xxxx, the contract UI runs on IP: yyyy

@webmaster128 any opinions, feedback here? I know cosmjs will be the largest provider/consumer of such metadata, so it would be good to know your desires to make the customer happy :smile:

Some of this data is good to have. I like the JSON Schema, as an interface description.
I'm highly sceptical with respect to TypeScript types. I don't consider the JSON Schema -> .d.ts super stable and would also avoid to have better support for one client technology than for others. JSON Schema is stable and universal.
As mentioned elsewhere, I think it is a serious security issue to add helper scripts to the chain. Users will execute them in a node process with their current user's pevillages no matter what they contain. I'd rather have a service that creates the helper scripts dynamically based on some variables than users storing arbitrary code on chain. Also things like fees and RPC endpoints are probably not stable for the lifetime of the contract.
Re: source code
As Ethan wisely noted, people will trust the source code if it is on chain, no matter matches the compiled code. Also is we are moving towards monolytic contract repos (like cosmwasm-plus), we suddenly get a very big source as the whole repo is part of the contract build.

Closing for the same reason as https://github.com/CosmWasm/wasmd/issues/241#issuecomment-756376059
This is too much logic to put in a blockchain, we should put that in an explorer "web app" or "api service" that allows a lot more fleixibllity to iterate and run long-lived tasks

Closing for the same reason as https://github.com/CosmWasm/wasmd/issues/241#issuecomment-756376059
This is too much logic to put in a blockchain, we should put that in an explorer "web app" or "api service" that allows a lot more fleixibllity to iterate and run long-lived tasks


Community Tools for Slack contribution

Challenge
At present, our organization does not have a way to visualize Slack contributions and celebrate community members who are making contributions.
Community tools
Common Room
Pros

A view of what’s happening on various platforms such as Slack, StackOverflow, Reddit, etc

Cons

Expensive

Orbit
Pros

A view of what’s happening on various platforms such as Slack, StackOverflow, Reddit, etc
Cost

Free tier with unlimited community members
Possibility of getting more capacity as a non-commercial open source project

Cons

Recently acquired by Postman
Messaging from the Orbit Team

The current Orbit product will be shutting down, and Orbit users have 90 days to wind down their use of Orbit and export their data
On May 31 we will stop ingesting new data, but you will still have access to explore and export your data until July 11
Existing customers will get support during the 90-day period, and customers who prepaid annually will receive prorated refunds
The Orbit team will be working on the Postman API Network, building new tools to help API publishers grow their developer communities

Waves
Pros

Slack analytics tool that monitors # of Slack threads, and track top messages, and trending posts.

Cons

Sole focus on Slack - cannot extend to other platforms our community members may be contributing to.
Less expensive than Common Room but still incurs monthly costs

Alternative option
Building a custom tool
Pros

Slack webhooks

Cons

Involves writing custom Code
Bandwidth
Who will manage this?

Considering we're moving forward with Community Awards, and the GC has agreed not to encourage the metrification of Slack contributions, does it make sense to keep this open?
I really appreciate your effort here @LisaHJung, this has definitely brought some more info to the table, as there doesn't seem to be an easy solution out there to do this sort of thing.

Hi @danielgblanco !
I really love your idea about the Community Awards and that we are taking steps to make that happen.
Given that we already have something in place to celebrate our community's contributions which was the intention behind considering tools to track Slack contributions, I say we close this issue for the time being and revisit it if necessary.
Thank you so much for your leadership in this area and for taking a great step to start recognizing our community members. This is such an important initiative and I am glad we are playing a part in it!

Thanks @LisaHJung, I'm closing this issue accordingly.


Custom log site and new black box API

Log site
Flogger library provides API for changing the header of log messages via LogSite instances. In this PR we add new logging API for all the entities. In a handler method, a user may obtain a preconfigured logger as follows:
class TaskAggregate extends Aggregate<...> {

    @React
    AssigneeRemoved on(UserDeleted event, EventContext ctx) {
        log().at(Level.FINE).log("Reacting to an event");
        // ...
    }
}

The resulting log would be similar to:
org.example.TaskAggregate on(UserDeleted, EventContext)
FINE: Reacting to an event

Implementation details
A new interface HandlerLifecycle is introduced. This is a set of callbacks regarding a message handler method invocation.
All the entities which extend AbstractEntity now implement this interface. The framework users may choose to implement it in other message handlers, namely AbstractEventReactor, AbstractEventSubscriber, AbstractCommander, and AbstractCommandHandler subclasses.
The framework users may employ the interface for their own needs, such as tracking the performance of the handler methods, adding extra logging, etc.
Custom actor ID for Black Box Bounded Context
With this PR, we add API for configuring the ID and time zone used to produce actor requests in the Black Box Bounded Context.
In some domains, entities and repositories may rely on the details from the ActorContext, such as the actor ID. One common use case for this is routing commands by the actor ID.
In order to simulate real-life actors in black-box tests, we add the API for changing the actor how posts commands via BlackBoxBoundedContext:
BlackBoxBoundedContext
        .from(builder)
        .withActor(actorId)
        .receivesCommand(..)
        ...

Also, users may change the time zone ID and offset via the in method:
BlackBoxBoundedContext
        .from(builder)
        .in(ZoneIds.of("Europe/Kyiv"), ZoneOffsets.ofHours(2))
        .receivesCommand(..)
        ...

Or do both at the same time via the withActorIn method:
BlackBoxBoundedContext
        .from(builder)
        .withActorIn(actorId, ZoneIds.of("Europe/Kyiv"), ZoneOffsets.ofHours(2))
        .receivesCommand(..)
        ...

@armiol, PTAL.

@dmdashenkov, would log trancing improvements work for underscored methods like _debug()?

@alexander-yevsyukov, no, they won't. These logging configurations only apply to the logs created via the log().at(...) construct. The method is deliberately named log() and not logger()  to avoid a naming clash if a user wants to use Logging in their entity.

@armiol, PTAL again.


Add/Remove label on Stale PRs

Feature Request
Is your feature request related to a problem? Please describe.
In a busy Repo it can be that some PRs may become stale as the author or reviewer is not responding. We need an easy way to identify them through labels.
Describe the solution you'd like
Add a label to the PR when it is stale (inactive for X days).
Remove the label when updated.
Describe alternatives you've considered
None

Have just found this Action which provides everything we need. No Dev work will be done.
https://github.com/actions/stale


Support Python 3.7

Subject of the issue
Types in Python 3.7 fail to pass the tests that we currently have. This somewhat relates to #12
Steps to reproduce
Switch the python version that's defined in the Pipfile, to use Python 3.7, and then try to run our tests
Expected behaviour
All of the tests should pass
Actual behaviour
5 tests fail under Python 3.7

This is the PEP that gets rid of GenericMeta: https://www.python.org/dev/peps/pep-0560/

I would agree that it doesn't feel like the correct approach, but in full transparency, I'm not really sure :/
I'm not sure that I understand what happened with GenericMeta when we moved to Python 3.7

I am also looking at this. We can add a dependency to keep GenericMeta? https://pypi.org/project/typing/
We can just create a class for GenericMeta?
First of all the fix @hairychris you could import GenericMeta as generic.
from typing import Generic as GenericMeta


Various things

Reworked API from https://github.com/almond-sh/almond/pull/352
Auto-update vars upon change (see gif below)
Fade-in effect when updating values (see gif too)

Will merge after adding a bit of doc, and having cleaned things up a bit.

Demo: (look at the pretty-printed var n)

Seems auto-updated var-s require >= 2.12.7.


Add a git_stash rule

Thanks!

@nicwest: well, I don't like git stash pop; see https://codingkilledthecat.wordpress.com/2012/04/27/git-stash-pop-considered-harmful/ and plenty others.
@dunn: sure, I will do that tomorrow.

@nwinkler: I think he meant that for you.


ConversationSummaryBufferMemory does not work as expected with MongoDBChatMessageHistory

Checked other resources

[x] I added a very descriptive title to this issue.
[x] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[ ] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
import os
from langchain.memory import ConversationSummaryBufferMemory
from langchain_openai import OpenAI
from langchain_mongodb.chat_message_histories import MongoDBChatMessageHistory
from langchain.chains.conversation.base import ConversationChain

os.environ["OPENAI_API_KEY"] = "#######################"

llm = OpenAI()

connection_string = "mongodb+srv://sa.................."
database_name = "langchain-chat-history"
collection_name = "collection_1"
session_id = "session31"

chat_memory = MongoDBChatMessageHistory(
    session_id=session_id,
    connection_string=connection_string,
    database_name=database_name,
    collection_name=collection_name,
)

memory = ConversationSummaryBufferMemory(
    llm=llm, chat_memory=chat_memory, max_token_limit=10
)

conversation_with_summary = ConversationChain(
    llm=llm,
    memory=memory,
    verbose=True,
)

print(conversation_with_summary.predict(input="Hi, what's up?"))
print(conversation_with_summary.predict(input="Just working on writing some documentation!"))
print(conversation_with_summary.predict(input="For LangChain! Have you heard of it?"))

Error Message and Stack Trace (if applicable)

Entering new ConversationChain chain...
Prompt after formatting:
The following is a friendly conversation between a human and an AI. The AI is talkative and provides lots of specific details from its context. If the AI does not know the answer to a question, it truthfully says it does not know.

Current conversation:
Human: Hi, what's up?
AI:

Finished chain.
Hello! I am an AI program designed and created by a team of developers at OpenAI. Currently, I am running on a server with a powerful processor and a lot of memory, allowing me to process and store vast amounts of information. I am constantly learning and improving my abilities through various algorithms and data sets. Is there something specific you would like to know or discuss?

Entering new ConversationChain chain...
Prompt after formatting:
The following is a friendly conversation between a human and an AI. The AI is talkative and provides lots of specific details from its context. If the AI does not know the answer to a question, it truthfully says it does not know.

Current conversation:
System:
The human greets the AI and asks about its capabilities. The AI explains that it is a program designed and created by a team of developers at OpenAI, constantly learning and improving through algorithms and data sets. It also mentions its powerful processor and memory. The human is curious to know more.
Human: Hi, what's up?
AI:  Hello! I am an AI program designed and created by a team of developers at OpenAI. Currently, I am running on a server with a powerful processor and a lot of memory, allowing me to process and store vast amounts of information. I am constantly learning and improving my abilities through various algorithms and data sets. Is there something specific you would like to know or discuss?
Human: Just working on writing some documentation!
AI:

Finished chain.
That's great to hear! I have access to a vast amount of information and can assist you with any questions you may have. Is there a specific topic or area you need help with in your documentation?

Entering new ConversationChain chain...
Prompt after formatting:
The following is a friendly conversation between a human and an AI. The AI is talkative and provides lots of specific details from its context. If the AI does not know the answer to a question, it truthfully says it does not know.

Current conversation:
System:
The human greets the AI and asks about its capabilities. The AI explains that it is a program designed and created by a team of developers at OpenAI, constantly learning and improving through algorithms and data sets. It also mentions its powerful processor and memory. The human is curious to know more and the AI offers its assistance, stating that it has access to a vast amount of information and can help with any questions about documentation. The human also shares that they are currently working on writing documentation.
Human: Hi, what's up?
AI:  Hello! I am an AI program designed and created by a team of developers at OpenAI. Currently, I am running on a server with a powerful processor and a lot of memory, allowing me to process and store vast amounts of information. I am constantly learning and improving my abilities through various algorithms and data sets. Is there something specific you would like to know or discuss?
Human: Just working on writing some documentation!
AI:  That's great to hear! I have access to a vast amount of information and can assist you with any questions you may have. Is there a specific topic or area you need help with in your documentation?
Human: For LangChain! Have you heard of it?
AI:

Finished chain.
Yes, I am familiar with LangChain. It is a blockchain platform that aims to provide secure and transparent language translation services. Is there anything specific you would like to know about LangChain for your documentation?

Description
Although the conversation is summarized, the entire chat conversation is still sent to llm without pruning the summarized chats. However, this works as expected with default in-memory list in ConversationSummaryBufferMemory.
Example (work as expected):
import os
from langchain.memory import ConversationSummaryBufferMemory
from langchain_openai import OpenAI
from langchain.chains.conversation.base import ConversationChain

os.environ["OPENAI_API_KEY"] = "##########################"

llm = OpenAI()

memory=ConversationSummaryBufferMemory(
    llm=llm, max_token_limit=10
)

conversation_with_summary = ConversationChain(
    llm=llm,
    memory=memory,
    verbose=True,
)

print(conversation_with_summary.predict(input="Hi, what's up?"))
print(conversation_with_summary.predict(input="Just working on writing some documentation!"))
print(conversation_with_summary.predict(input="For LangChain! Have you heard of it?"))

Expected output:

Entering new ConversationChain chain...
Prompt after formatting:
The following is a friendly conversation between a human and an AI. The AI is talkative and provides lots of specific details from its context. If the AI does not know the answer to a question, it truthfully says it does not know.

Current conversation:
Human: Hi, what's up?
AI:

Finished chain.
Hello! Not much is up with me, I am an AI after all. But my servers are running smoothly and I am ready to assist you with any questions or tasks you may have. How about you? Is there anything I can help you with today?

Entering new ConversationChain chain...
Prompt after formatting:
The following is a friendly conversation between a human and an AI. The AI is talkative and provides lots of specific details from its context. If the AI does not know the answer to a question, it truthfully says it does not know.

Current conversation:
System:
The human greets the AI and asks how it is doing. The AI responds by saying it is an AI and its servers are running smoothly. The AI also offers to assist the human with any questions or tasks.
Human: Just working on writing some documentation!
AI:

Finished chain.
That sounds like a productive task! As an AI, I don't experience fatigue or boredom like humans, so I am always ready to assist with any tasks or questions you may have. Is there something specific you need help with?

Entering new ConversationChain chain...
Prompt after formatting:
The following is a friendly conversation between a human and an AI. The AI is talkative and provides lots of specific details from its context. If the AI does not know the answer to a question, it truthfully says it does not know.

Current conversation:
System:
The human greets the AI and asks how it is doing. The AI responds by saying it is an AI and its servers are running smoothly. The AI also offers to assist the human with any questions or tasks, mentioning its lack of fatigue or boredom. The human mentions working on writing documentation, to which the AI offers its assistance and asks for specific needs.
Human: For LangChain! Have you heard of it?
AI:

Finished chain.
Yes, I am familiar with LangChain. It is a blockchain platform that focuses on language and translation services. It was founded in 2019 and has gained significant popularity in the tech industry. Is there something specific you would like to know about LangChain? I can provide you with more detailed information if needed.

System Info
langchain==0.1.17
langchain-community==0.0.36
langchain-core==0.1.50
langchain-mongodb==0.1.3

I tried on my local machine and everything is working as expected. Can you please check your mongodb and see if messages are being stored in the desired collection???

I'm facing the same issue with PostgresChatMessageHistory.
import os
import config
from langchain.memory import ConversationSummaryBufferMemory
from langchain_openai import OpenAI
from langchain_community.chat_message_histories import (
    PostgresChatMessageHistory,
)
from langchain.chains.conversation.base import ConversationChain

os.environ["OPENAI_API_KEY"] = ""

llm = OpenAI()

connection_string = config.POSTGRES_CHAT_MEMORY_CONNECTION_STRING
database_name = "langchain-chat-history"
collection_name = "collection_1"
session_id = "session42"

chat_memory = PostgresChatMessageHistory(
    session_id=session_id,
    connection_string=connection_string,
)

memory = ConversationSummaryBufferMemory(
    llm=llm, chat_memory=chat_memory, max_token_limit=10
)

conversation_with_summary = ConversationChain(
    llm=llm,
    memory=memory,
    verbose=True,
)

print(conversation_with_summary.predict(input="Hi, what's up?"))
print(conversation_with_summary.predict(input="Just working on writing some documentation!"))
print(conversation_with_summary.predict(input="For LangChain! Have you heard of it?"))

I tried on my local machine and everything is working as expected. Can you please check your mongodb and see if messages are being stored in the desired collection???

@keenborder786 yes messages are being stored in the given collection.

Hope this will be fixed with #11374.

I'm facing the same issue with PostgresChatMessageHistory.
import os
import config
from langchain.memory import ConversationSummaryBufferMemory
from langchain_openai import OpenAI
from langchain_community.chat_message_histories import (
    PostgresChatMessageHistory,
)
from langchain.chains.conversation.base import ConversationChain

os.environ["OPENAI_API_KEY"] = ""

llm = OpenAI()

connection_string = config.POSTGRES_CHAT_MEMORY_CONNECTION_STRING
database_name = "langchain-chat-history"
collection_name = "collection_1"
session_id = "session42"

chat_memory = PostgresChatMessageHistory(
    session_id=session_id,
    connection_string=connection_string,
)

memory = ConversationSummaryBufferMemory(
    llm=llm, chat_memory=chat_memory, max_token_limit=10
)

conversation_with_summary = ConversationChain(
    llm=llm,
    memory=memory,
    verbose=True,
)

print(conversation_with_summary.predict(input="Hi, what's up?"))
print(conversation_with_summary.predict(input="Just working on writing some documentation!"))
print(conversation_with_summary.predict(input="For LangChain! Have you heard of it?"))

Thanks man, works for me.


sharing links - lbry.tv

Minor issue
When sharing links, the app uses the retired lbry.tv, instead of odysee.com
Expected behaviour
Should share links with "odysee.com"
Actual behaviour
Inatead links are shared with "lbry.tv"
(The lbry.tv-links is forwarded to odysee.com. So everything is working...)
System Configuration

Device:
Android version: 11
lbry app version: 0.17.1

If fixable, it should be done on lbry-android


Update Uninstall-SPAppInstance.md

Update example formatting.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-server/Uninstall-SPAppInstance.md
:white_check_mark:Succeeded
View (sharepoint-ps)

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.


DOC contribute docs update

… to create test environment

Reference Issue

Updated the contribute DOC with the explanation how to create test conda environments necessary to run the tests
updated the link to the ramp workflow in the environment iris kit

What does this implement/fix? Explain your changes.
Any other comments?

Thanks @maikia


[WIP,ENH] Add simulation generator for image based meta-analysis

Continuation of #343

Changes proposed in this pull request:

TODO

Per convo on Slack, this can be closed. Closing.


Add AdaptiveDockingNode

Greater hubris has hit me so I'll merge in the hope of nothing exploding!


Node.js  Loaders Team Meeting 2024-08-13

Time
UTC Tue 13-Aug-2024 18:00 (06:00 PM):

Timezone
Date/Time

US / Pacific
Tue 13-Aug-2024 11:00 (11:00 AM)

US / Mountain
Tue 13-Aug-2024 12:00 (12:00 PM)

US / Central
Tue 13-Aug-2024 13:00 (01:00 PM)

US / Eastern
Tue 13-Aug-2024 14:00 (02:00 PM)

EU / Western
Tue 13-Aug-2024 19:00 (07:00 PM)

EU / Central
Tue 13-Aug-2024 20:00 (08:00 PM)

EU / Eastern
Tue 13-Aug-2024 21:00 (09:00 PM)

Moscow
Tue 13-Aug-2024 21:00 (09:00 PM)

Chennai
Tue 13-Aug-2024 23:30 (11:30 PM)

Hangzhou
Wed 14-Aug-2024 02:00 (02:00 AM)

Tokyo
Wed 14-Aug-2024 03:00 (03:00 AM)

Sydney
Wed 14-Aug-2024 04:00 (04:00 AM)

Or in your local time:

https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Loaders Team+Meeting+2024-08-13&iso=20240813T1800
or https://www.wolframalpha.com/input/?i=06PM+UTC%2C+Aug+13%2C+2024+in+local+time

Links

Minutes Google Doc: https://docs.google.com/document/d/1tMXU2y9odlfImQYuc0YZ699dW8jke2Mr37wC8w7T48A/edit

Agenda
Extracted from loaders-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node

Support .noderc or similar file-based initialization configurations? #53787
Proposal for a simple, universal module loader hooks API to replace require() monkey-patching #52219
ESM Hook deadlocks since 21.2.0 a3e09b3 #50948

nodejs/loaders

Proposal: Moving hooks on thread #205
Hooks thread direction #201
doc: add synchronous hooks proposal #198

Invited

Loaders team: @nodejs/loaders

Observers/Guests
Notes
The agenda comes from issues labelled with loaders-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.
Joining the meeting

link for participants: https://zoom.us/j/97506450082

For those who just want to watch: https://www.youtube.com/c/nodejs+foundation/live

We weren't able to stream it but @JakobJingleheimer recorded it (cannot find the notes taken from Slack, can you post the link?)

Apologies for the delay: https://youtu.be/4-Kngczc-Pw


correct branch typo in travis yml

Coverage remained the same at 43.156% when pulling 6a90c07b4f74a926a5c22457a142d365a7d3a82e on development into c0cd27b982156a1da9d705498975d93afee5422b on master.


[Feature][Manager] Support maintenance of message queue cluster

Description

Control produce operation and consume operation of Inlong message queue cluster.
Build relationships between DataProxy cluster and MessageQueue cluster.
Remove relationships between DataProxy cluster and MessageQueue cluster.
Synchronize all topic from cluster tag to message queue cluster.
Clear all topic from a message queue cluster.

Use case
No response
Are you willing to submit PR?

[X] Yes, I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

InLong do not include maintenance  feature.


adds optional error message interface

What's this PR do?

adds optional error message in the validation rule
injects options form state into the custom blur callback

Where should the reviewer start?
formContainer.tsx
How should this be manually tested?
manually check if the form validation can be used without an error message provided

Coverage increased (+0.2%) to 70.886% when pulling 4e1855adc82a3622d2b420ded6579643930246a2 on feature/optional-error-msg into 3784cec100fa350492885b29b00f51828b015810 on release/v0.1.1.

Codecov Report

Merging #13 into release/v0.1.1 will increase coverage by 0.26%.
The diff coverage is 50%.

@@                Coverage Diff                 @@
##           release/v0.1.1      #13      +/-   ##
==================================================
+ Coverage           72.38%   72.64%   +0.26%
==================================================
  Files                   4        4
  Lines                 105      106       +1
  Branches               19       19
==================================================
+ Hits                   76       77       +1
  Misses                 20       20
  Partials                9        9

Impacted Files
Coverage Δ

src/FormContainer.tsx
72.72% <50%> (+0.41%)
:arrow_up:

Continue to review full report at Codecov.

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


Update jersey-test-framework-provider-grizzly2 to 2.39

Updates org.glassfish.jersey.test-framework.providers:jersey-test-framework-provider-grizzly2 from 2.25.1 to 2.39.
GitHub Release Notes
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.glassfish.jersey.test-framework.providers", artifactId = "jersey-test-framework-provider-grizzly2" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.glassfish.jersey.test-framework.providers", artifactId = "jersey-test-framework-provider-grizzly2" }
}]

labels: test-library-update, commit-count:1

Superseded by #1718.


economise, ammeline

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[a,e]

/trunk merge


added support for linking account with google credentials

Fixes flutter/flutter#12066

I signed it!

I don't understand why it doesn't pass travis build after last commit. Any help?

Hi @MarcinusX we fixed the Travis issue in https://github.com/flutter/plugins/pull/220, so if you merge with master hopefully it will pass now.

@mit-mit, unfortunately it didn't help. :(

@MarcinusX I restarted Travis for you. It's passing now.

@goderbauer Thank you!

As far as I can tell this looks good to go - could someone with write access please resolve the merge conflicts? :)

I merged the changes; @MarcinusX @bjornbjorn can you sanity check, please?

Thanks @mit-mit! The finished result includes signInWithCustomToken/onAuthStateChanged from 0.2.4 and has added 0.2.5 with linkWithGoogleCredential() so looks sane to me at least:) 👍

@mit-mit For me looks good too :) Thank you :)

@goderbauer can we go ahead and merge this?

LGTM

@goderbauer I don't seem to have access to publish these changes; would you mind doing that? (and add me as an uploaded if possible)

@mit-mit New version is live: https://pub.dartlang.org/packages/firebase_auth
I also added you as an uploader.


What are the es versions supported by skywalking 6.1?

What are the es versions supported by skywalking 6.1?

Please read the document, https://github.com/apache/skywalking/blob/master/docs/en/setup/backend/backend-storage.md


[stable/drone] Drone 2.0.0 rc 8 - Creates source-control secret

What this PR does / why we need it:
The chart is failing if you don't create in advance the provider's secret, It tries to read it from <fullName>-source-control but the secret its not there, it does not create it for you if you want to.
This pr automate the secret creation by reading it form the new Secret field and creates "ClientSecretKey: Secret", while keeping the option to use a pre created secret, as it using the same key (ClientSecretKey).
/edit I also fixed the note, it was pointing the proxy to port 8000, now to 80. working fine :)
Special notes for your reviewer:
@max-rocket-internet @paulczar @christian-roggia
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

Hey guys @prydonius @christian-roggia what do you think?

@cpanato @pedrovaz  I would like some feedback :)

/ok-to-test

@paulczar I know you did a lot of work here, any comments?

Version bumped to rc.9 as yesterday rc.8 was merged

/assign @christian-roggia

Thanks, @christian-roggia and @max-rocket-internet for the feedback.
Changelog:

Merged secrets file back to original "secrets.yaml" with checksum
Updated documentation within a clearer way
Rename .Values.Secret -> clientSecretValue

Let me know if there is something else we can improve here.
updated my deployment, Happy Helming!

/approve
will defer the lgtm to @christian-roggia

@christian-roggia
any comments on this? Thx!!!

/lgtm


backport increase block gas limit

I don't know if v1.0 status but, maybe cool to add it as well

related to https://github.com/paritytech/substrate/pull/2597
and https://github.com/paritytech/substrate/issues/2566

This have no effects on existing chain so why need to bump version?

Good point @xlc. Next question would be, as ink! targets master, do we need this in 1.0?

I see no downside to increase it. Any public chain have to override default values in chain spec to match their economic / security model so this only really applies to dev testnet, and a default value that is too high is better one that is too low cause otherwise contracts may be rejected unexpectedly.


[Migration] wPOKT Migration strategy

Objective
Prepare a migration strategy for the wPOKT bridge.
Origin Document

Related to #144
There are lots of wPOKT libraries which

https://github.com/pokt-network/wpokt-staking-frontend
https://github.com/pokt-network/wpokt-staking-frontend
https://github.com/pokt-network/wpokt-frontend
https://github.com/pokt-network/wpokt-frontend
https://github.com/pokt-network/wpokt-staking-contracts
https://github.com/pokt-network/wpokt-monitor
https://github.com/pokt-network/wpokt
https://github.com/pokt-network/wpokt-validator
https://github.com/pokt-network/wpokt-subgraph

Goals

Research and identify unknown unknowns for the bridge migration
Start preparing a plan for how the wPOKT bridge should be migrated

Deliverables

[ ] A 2-pager determining how the wPOKT bridge should be migrated
[ ] A stakeholder that will own the migration from Morse to Shannon
[ ] The alternative selected (e.g. Axelar) for Ethereum interoperability after the Shannon migration

Non-goals / Non-deliverables

Doing the actual migration
Build out the infrastructure for the post-migration EVM interoperability

General deliverables

[ ] Comments: Add/update TODOs and comments alongside the source code so it is easier to follow.
[ ] Testing: Add new tests (unit and/or E2E) to the test suite.
[ ] Makefile: Add new targets to the Makefile to make the new functionality easier to use.
[ ] Documentation: Update architectural or development READMEs; use mermaid diagrams where appropriate.

Creator: @Olshansk
Co-Owners: @RossiNYC

Current plan coming out of the PNF offsite is that Matteo will reach out to Raid Guild for feedback here.

Wrote up this RFP https://docs.google.com/document/d/17PTh01Vf3aL0V-bfXTMU5cPt3wf0dXWCJuvDHAFCwSA/edit and will provide to Raid Guild - looking for a few other options as well.

@RossiNYC Saw your starting point for the RFP. As we discussed offline, definitely a lot more to unpack and think through here. I think that when the time is right, it might be worth preparing a list of questions for raidguild and "consulting" them on our options.

@RossiNYC Something to consider is that if we end up partnering we an interoperability project (e.g. hyperlane), we could ask them to own/drive this work for us as well. Wdyt?

@Olshansk - yep, agreed. Have been speaking with Dermot about this - the decision tree is something like:
Figure out our bridging strategy based on PNF wPOKT Strategy (what/where do they want it listed, etc.)
Based on that - we could either a. use a team like RG to migrate or b. engage a project (hyperlane, etc.) or c. do both
I have a followup with Dermot/Ben on Wed (Dec 13) to discuss this more - TL;DR - we are aligned on option b 100%

Spoke with RG today (w/Dermot) - they will help us with defining the migration strategy and sequence of events - they will also help evaluate interop propto's like Hyperlane - main ask was around us supporting EVM at the rollup layer (Polaris for e.g.) as even deploying Hyperlane would be easier - they have some strong opinions on security and though that the rollup supporting EVM would help "reduce attack surfaces"
Open Questions:
Will Ledger support the new pocket network? (A. YES)
When it comes the RPC calls changing, does that mean the url extensions of each request in the code below will change? Will the data (aka the request body) section change? And will the JSON format for the response data of each change?
javascript=
requests = {
    getBalance: (address, height) => ({
      url: "/v1/query/balance",
      method: "post",
      data: {
        address,
        height,
      },
    }),
    getTransaction: (id) => ({
      url: "/v1/query/tx",
      method: "post",
      data: {
        hash: id,
      },
    }),
    sendRawTx: (fromAddress, tx) => ({
      url: "/v1/client/rawtx",
      method: "post",
      data: {
        address: fromAddress,
        raw_hex_bytes: tx,
      },
    }),
    getSupportedChains: (height) => ({
      url: "/v1/query/supportedchains",
      method: "post",
      data: {
        height,
      },
    }),
  };

they will also help evaluate interop propto's like Hyperlane

Sounds good.
However, personally, given that Hyperlane & Axelar are the big players and our selected sequencer is partnering with Hyperlane, I'm not sure there's a lot of value to this investigation.

ask was around us supporting EVM at the rollup layer (Polaris for

I asked for an intro to the Polaris team in our channel with Rollkit on slack.

When it comes the RPC calls changing, does that mean the url extensions of each request in the code below will change? Will the data (aka the request body) section change? And will the JSON format for the response data of each change?

Yes. Everything will change. Shannon is a complete rewrite.

X-Ref the corresponding Discord channel to this issue: https://discord.com/channels/553741558869131266/1187104966826008696


AssertionError: loss log variables are different across GPUs!

I met the error at the 87159 iter of 281820 iters.
It seems that the loss at this iter has no dn_loss as previous iter ,which lead to this error.
however, I don't know how to solve it?

This is the normal loss item.

 This is the normal loss item. ( I am trying reproduce the sparse4dv3_r101 performance with the information you mentioned in the last issue. )

Same problem on 8xRTX3090.

It's possible that there are no ground truths in the same batch, which resulted in an error.

So can I just comment this line in the code to refrain from this error. Or Is there any other way to refrain from this error ?
        if dist.is_available() and dist.is_initialized():
            log_var_length = torch.tensor(len(log_vars), device=loss.device)
            dist.all_reduce(log_var_length)
            message = (f'rank {dist.get_rank()}' +
                       f' len(log_vars): {len(log_vars)}' + ' keys: ' +
                       ','.join(log_vars.keys()))
            ## here is the bug reason
            assert log_var_length == len(log_vars) * dist.get_world_size(), \
                'loss log variables are different across GPUs!\n' + message

https://github.com/HorizonRobotics/Sparse4D/blob/main/projects/mmdet3d_plugin/models/detection3d/target.py#L176-L177
Try commenting out these two lines of code.

https://github.com/HorizonRobotics/Sparse4D/blob/main/projects/mmdet3d_plugin/models/detection3d/target.py#L176-L177
Try commenting out these two lines of code.

Does this commenting affect training results?

https://github.com/HorizonRobotics/Sparse4D/blob/main/projects/mmdet3d_plugin/models/detection3d/target.py#L176-L177
Try commenting out these two lines of code.

注释掉这两行之后会报其他错误

So can I just comment this line in the code to refrain from this error. Or Is there any other way to refrain from this error ?
       # anaconda3/envs/sparse4dv3_sl/lib/python3.8/site-packages/mmdet/models/detectors/base.py
        if dist.is_available() and dist.is_initialized():
            log_var_length = torch.tensor(len(log_vars), device=loss.device)
            dist.all_reduce(log_var_length)
            message = (f'rank {dist.get_rank()}' +
                       f' len(log_vars): {len(log_vars)}' + ' keys: ' +
                       ','.join(log_vars.keys()))
            ## here is the bug reason
            assert log_var_length == len(log_vars) * dist.get_world_size(), \
                'loss log variables are different across GPUs!\n' + message

hello,does this commenting work?

So can I just comment this line in the code to refrain from this error. Or Is there any other way to refrain from this error ?
       # anaconda3/envs/sparse4dv3_sl/lib/python3.8/site-packages/mmdet/models/detectors/base.py
        if dist.is_available() and dist.is_initialized():
            log_var_length = torch.tensor(len(log_vars), device=loss.device)
            dist.all_reduce(log_var_length)
            message = (f'rank {dist.get_rank()}' +
                       f' len(log_vars): {len(log_vars)}' + ' keys: ' +
                       ','.join(log_vars.keys()))
            ## here is the bug reason
            assert log_var_length == len(log_vars) * dist.get_world_size(), \
                'loss log variables are different across GPUs!\n' + message

hello,does this commenting work?

I met the same problem https://github.com/open-mmlab/mmdetection/issues/9340#issuecomment-1544975881


log into console even if sentry hasn't been setup yet

All info and error events wait for Sentry to be initialized. This is correct. However, we can still log those events happening in real time before Sentry has been initialized.

this was implemented in 43d0287d10cfd5031c27a2404bf5045a3e46c1ea


"NEW" settings ignored

Installed Win11 Enterprise 23H2 via WDS.
"Left-align the taskbar in Windows 11"
Taskbar was center aligned.
Delete preset icons (like Edge, Explorer, Outlook, Microsoft Store) from the taskbar
Edge icon on taskbar and start menu.
Hide Edge First Run Experience
Edge first run questions popped up.
Every other customization seems to have applied properly. Any thoughts?

I have never used WDS. Also, I am unable to test with Windows 11 Enterprise at the moment because when I try to install from the 22631.2428.231001-0608.23H2_NI_RELEASE_SVC_REFRESH_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-us.iso evaluation image in VMware, Windows Setup repeatedly fails with this error message: “Windows cannot find the Microsoft Software License Terms.”
Anyway, the new settings should produce these commands in your autounattend.xml file:
<Path>powershell.exe -NoProfile -Command "Get-Content -LiteralPath 'C:\Windows\Setup\Scripts\DeleteTaskbarIcons.ps1' -Raw | Invoke-Expression;"</Path>
<Path>reg.exe add "HKU\DefaultUser\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced" /v TaskbarAl /t REG_DWORD /d 0 /f</Path>
<Path>reg.exe add "HKLM\SOFTWARE\Policies\Microsoft\Edge" /v HideFirstRunExperience /t REG_DWORD /d 1 /f</Path>

Make sure that these commands are there. Or better, attach your autounattend.xml here.

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

I have now tested this with the 26100.1.240331-1435.ge_release_CLIENT_ENTERPRISES_OEM_x64FRE_en-us.iso image (24H2) and a valid Enterprise key – the “NEW” settings work flawlessly. They have also worked with the publicly available Win11_23H2_English_x64v2.iso image.
If there is a problem, I believe it is related to WDS, which I will not dive into.


Preview

Merge master and write rspec tests for CreateBeehiveURL

Coverage increased (+0.13%) to 93.01% when pulling 4b327901cbdd78f57acc0e8110976fd1ecb64021 on preview into 380c4b5354f7066cfdd7f8dd47c8af49dd2654cf on master.


docs: token: Added missing information about security audit

for Streamflow Timelock. :)
@joncinque

@joncinque Happy New Year!
Please take a look when you can, should be pretty straightforwars, just adding to our conversation from ~ a month ago.
ty

Looks great, thanks!


[BUG] 1.20.2 Fails to load with Network Channel Builder def not found.

Describe the bug
When loading mimi-mod on any forge version on 1.20.2 minecraft it will fail to load the mod due to not finding the network channel builder. Reverting to 1.20.1 with an appropriate forge version lets the mod load.
To Reproduce
Steps to reproduce the behavior:

Download Minecraft 1.20.2
Download any version of Forge that supports 1.20.2
Start minecraft, experience error.

Expected behavior
Load Mod please. :)!
Screenshots
If applicable, add screenshots to help explain your problem.
Crash Logs
If applicable, add log files or crash reports that were generated.
Environment (please complete the following information):

OS: [e.g. Windows 10, MaxOS Big Sur, Ubuntu 21.0.4]
Mod Version: [e.g. 1.2.0.RELEASE]
Minecraft Version: [e.g. 1.16.5]
Forge Version: [e.g. 1.16.5 - 36.1.0]

Additional context
Add any other context about the problem here.

Hello! Apologies for the super late reply. Life got super crazy for awhile and I had pretty much no time for the mod. I've just released Beta versions for a major 4.0.0 update for versions 1.19.2-1.20.4 which should resolve this problem! Please let me know if you encounter any other issues!


04/08/2018 23:51 : Create Pull Request for branch prTesting_2018040823 -> master

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef.md
: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.


MINIFI-182 Implemented event-driven scheduler

Implemented the event-driven scheduler. Refactored the thread-related code into a base class as most of it is reused between the event-driven scheduler and timer-driven. The event-driven scheduler has a similar loop to the timer-driven, but instead of sleeping, it blocks until notified by another thread that work is available.
Results in logs like this:
[2017-01-11 12:37:59.917] [minifi log] [info] GetFile process /tmp/getfile/test
[2017-01-11 12:37:59.918] [minifi log] [info] PutFile using temporary file /tmp/putfile/.test.5a709b5b-b517-4710-bd56-2f0be2b754c0
[2017-01-11 12:37:59.918] [minifi log] [info] PutFile writing file test into directory /tmp/putfile
[2017-01-11 12:37:59.918] [minifi log] [info] PutFile committing put file operation to /tmp/putfile/test
[2017-01-11 12:37:59.918] [minifi log] [info] PutFile commit put file operation to /tmp/putfile/test succeeded

Note that the PutFile was triggered immediately after GetFile picked up the file, which is what we want.

@benqiu2016 Good point. Fixed.

@achristianson looks good to me.

reviewing

changes and build looks good.  works as anticipated and looks like a solid foundation.  will get this merged in shortly.  Thanks!


[core]Using multiple models can cause new_x  lag feature shift

What happened + What you expected to happen
Hi,

models param in MLForecast class could receive multi models as a list , then use predict method, may cause lag feature drift, therefore, different models may get diferent features
I would expect that different models use the same lag features at the same prediction moment. If I just use date_features, it works well, there confused me when I use lag features or lag_transform features
the same as above, When  I call predict method second time, it's lag features still drift on the basis of the first time, but I just use one model, everything is OK.

Versions / Dependencies

mlforecast: 0.11.3
python: 3.8.16
os: Ubuntu

Reproduction script
python code is below:
import pandas as pd
from mlforecast import MLForecast
from mlforecast.target_transforms import Differences
from sklearn.linear_model import LinearRegression
from xgboost import XGBRegressor
from lightgbm import LGBMRegressor
from IPython.display import display
def inspect_input(new_x):
    """Displays the model inputs to inspect them"""
    display(new_x)
    return new_x
df = pd.read_csv('https://datasets-nixtla.s3.amazonaws.com/air-passengers.csv', parse_dates=['ds'])
fcst = MLForecast(
    models=[LinearRegression(), XGBRegressor(), LGBMRegressor(verbose=-1)],
    freq='MS',  # our serie has a monthly frequency
    lags=[12],
    target_transforms=[Differences([1])],
)
fcst.fit(df, )
fcst.predict(1, before_predict_callback=inspect_input)

then the result is below:

Issue Severity
High: It blocks me from completing my task.

Hey @MrTangsai, thanks for using mlforecast and for the excellent report. I believe this was introduced in #255 and released in 0.11.0, so if this is blocking you you can install a prior version and it should work as expected. We'll work on a fix soon.

thanks a lot! it works well in new version.


fix(basic) - closing quotation marks not required for a PRINT statement

Fixed the closing quotations marks considered for string highlighting in basic.
Resolves #3996
Changes
Before

After

Checklist

[x] Added markup tests, or they don't apply here because...
[x] Updated the changelog at CHANGES.md

@joshgoebel the changes for regex literals are made, please review them once.


REL: Add a short description to setup.py

Noticed that the short description field in setup.py previously just said Empress; this replaces that with a slightly modified version  of the description used for the GitHub repo.
I guess the motivation here is that some websites (e.g. pypi.org) which show information about PyPI packages start with the short description, so it would be nice to have such a description. For comparison, here are the PyPI pages for Empress and Gneiss. The short descriptions are shown in the gray bar in the middle of the page, just below the blue section and above the white section; Gneiss has a short description listed here, while Empress' just says Empress.

Empress
Gneiss

Thanks @fedarko!


Input event doesn't fire in IE

var el = document.getElementById("input");
el.addEventListener("input", function (e) {
	console.log(el.value);
});
new Inputmask({ alias: "date" }).mask(el);

https://jsfiddle.net/dp9uoxz8/
In Chrome and FF the input event fires on each change of the text field. It doesn't fire in IE that way. But when the IE's clear button (X) was pressed it fires the input event with previous content while the text box clears.

I came here to report this exact problem with IE as I depend on the input event to provide suggestions to the user on a masked text input. To me it seems that there are two different issues:

When IE's clear button is pressed the input event is fired but the value of the text box at the time of the event is whatever was in the text box before clear button was pressed.

When deleting input from the text box (e.g. using backspace) the input event is not always fired.


add assign ContractRequest mutation

Coverage increased (+0.008%) to 88.646% when pulling 104b558345998d2c12d89a486db53f2e77cc55e6 on 3194-contract-request-assignee-mutation into 5ad1e5d3cbc3163b01cef552fd4439190ed4d248 on develop.


[UBS-Admin. Orders] System doesn't return to the Orders tab and hangs

Environment: macOS 10.10.5, Google Chrome 87.0.4280.141.
Reproducible: always.
Build found: 21.10.22
Preconditions

User is Logged in to UBS as an Admin: https://www.testgreencity.ga/GreenCityClient/#/ubs
"Замовлення" page is opened
Any order number from the table selected

Steps to reproduce

Go to 'Деталі замовлення'
Make any changes to the "Order Details"
Click on 'Назад' button
Click on "Так"button

Actual result
The system shows "У разі повернення назад внесені зміни будуть втрачені. Чи дійсно Ви бажаєте повернутись до таблиці?" message and doesn't return to the Orders tab, the page is hangs.

Expected result
The system should undo all the changes and return to the Orders tab.
User Story: https://github.com/ita-social-projects/GreenCity/issues/2795
Test case
Labels to be added
"Bug", Priority ("pri: "), Severity ("severity:"), Type ("UI, "Functional"), "API" (for back-end bugs).

The bug is not reproduced now


Auto import feature doesn't work properly

I want to get the auto-import hint when inputing an Class or Function defined in another module. But pylance don't give the correct  hint.
In this case,I want to get the quick fixes suggestion for 'DictCursor' defined in the 'cursors.py' of pymysql package. Bud the amazing thing is when I reload the window ,it will give the correct hint whit quick fixes in a few seconds,and soon disappeared.
After review the trace output of pylance,the 'cursors.py' has been parsed.
(99398) [BG(1)]     parsing: /Users/python/vscode/vscode/venv/lib/python3.9/site-packages/pymysql/cursors.py [fs read 0ms] (9ms)
(99398) [BG(1)]     binding: /Users/python/vscode/vscode/venv/lib/python3.9/site-packages/pymysql/cursors.py (4ms)
What happened,is there any configuration should be setup?
https://user-images.githubusercontent.com/64769877/151911962-18e80282-7302-4041-a702-1b8d54ecad8d.mov

it looks like a bug. thank you for reporting the issue!

It's my honor for getting confirmed by you.The problem also happened with the module in the subdirectory of the package.
Be waiting for the next update for the solution.

it looks like a bug. thank you for reporting the issue!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: @.***>

so, it is happening since DictCursor is not in __ all __ nor there is pyi file. so we don't know whether it is a part of public API or not. so we dropped it.

Since we don't want to bloat completion with bunch of symbols, I dont think we want to enable it by default, but I added a hidden option as an escape patch.
Basically, if one adds this to setting.json, we will treat the package special and scan more symbols from it.
"python.analysis.packageIndexDepths": [[packageName: string, depth: number, forceIndexing: boolean]*],
ex)
"python.analysis.packageIndexDepths": [["pymysql", 3, true]],

packageName is the name of the package, depth means how deep the scanner will scan, forceIndexing means it will include all symbols in the py file discovered regardless of __ all __ or py.typed.

This issue has been fixed in version 2022.3.2, which we've just released. You can find the changelog here: CHANGELOG.md

"python.analysis.packageIndexDepths": [["pymysql", 3, true]],

@heejaechang That is awesome! Would something similar work for local files too? I keep having issues where auto-import / suggestions don't work or symbols aren't found. Even with "python.analysis.indexing": true.
Would love an option to say Pylance "always index these core and helper modules + constants file".
The project I currently work on usually doesn't use __all__ and hasn't added py.typed yet since we are still in the process of adding all full type annotations.
With indexing: true I also get a warning.
Workspace indexing has hit its upper limit: 2000 files

@cdce8p the option should work with multiroot workspace as long as root is installed with pip install -e ...
but that being said, I opened this issue to track UX on multiroot workspace - https://github.com/microsoft/pylance-release/issues/2601

Is there any way to use the packageIndexDepths workaround without specifying the package? The inability to get auto-imports for most of the third-party packages I use is frustrating, and I don't want to have to configure these package by package.

for default 3 levels I believe this is it:
"python.analysis.packageIndexDepths": [
	["",3]
],

Thanks, that works!

Using normal VS code (not Insiders) with this config in settings.json gives me: an "Unknown Configuration Setting" popup in VS Code and the config line looks gray-out. Also can not say that it fixes anything for me.
Do I need to install anything more/else than the latest VS Code + Python/Pylance extensions to make it work for me?


Exclude folder during update

Is there a way to exclude a folder from the archive when doing pgb update ##### .?

nope. not at the moment

added support for
> pgb update 12 ./path --ignore "node_modules" --ignore "*.lock" --ignore "tmp"

you can also put a file called .pgbrc in the root of your application directory.  this file should be json format and can be this:
{ "ignore": [ "node_modules", "*.lock", "tmp" ] }

i'll close this out when the npm package is published

Awesome. I had started looking at this and was thinking of swapping out the zip module you were using because it didn't look to support excludes. Thanks for the fast turn around on that.


[Go Live][Nov 29]

Push to live

Docs Build status updates of commit 01991a6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/apps-in-teams-meetings/API-references.md
:white_check_mark:Succeeded
View

msteams-platform/apps-in-teams-meetings/enable-and-configure-your-app-for-teams-meetings.md
:white_check_mark:Succeeded
View

msteams-platform/assets/images/apps-in-meetings/share-specific-content-to-stage.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/dev-preview/tab-and-devtools.png
:white_check_mark:Succeeded
View

msteams-platform/bots/calls-and-meetings/call-notifications.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/build-and-test/deep-links.md
:white_check_mark:Succeeded
View

msteams-platform/messaging-extensions/what-are-messaging-extensions.md
:white_check_mark:Succeeded
View

msteams-platform/mstdd-landing.yml
:white_check_mark:Succeeded
View

msteams-platform/resources/schema/manifest-schema-dev-preview.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/access-teams-context.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/create-tab-pages/configuration-page.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/developer-tools.md
:white_check_mark:Succeeded
View

msteams-platform/task-modules-and-cards/cards/cards-format.md
:white_check_mark:Succeeded
View

msteams-platform/webhooks-and-connectors/how-to/connectors-using.md
:white_check_mark:Succeeded
View

msteams-platform/whats-new.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel