oh-my-posh: 12.0.1 -> 12.1.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/jandedobbeleer/oh-my-posh/releases.
meta.description for oh-my-posh is: "A prompt theme engine for any shell"
meta.homepage for oh-my-posh is: "https://ohmyposh.dev"
meta.changelog for oh-my-posh is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 12.1.0 with grep in /nix/store/5z1s89m2f1693pm07i018vaqnjvpmnxn-oh-my-posh-12.1.0
found 12.1.0 in filename of file in /nix/store/5z1s89m2f1693pm07i018vaqnjvpmnxn-oh-my-posh-12.1.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
oh-my-posh

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/5z1s89m2f1693pm07i018vaqnjvpmnxn-oh-my-posh-12.1.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A oh-my-posh https://github.com/r-ryantm/nixpkgs/archive/271578d10355fec800c5bca37be2df97ef97f96e.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/5z1s89m2f1693pm07i018vaqnjvpmnxn-oh-my-posh-12.1.0
ls -la /nix/store/5z1s89m2f1693pm07i018vaqnjvpmnxn-oh-my-posh-12.1.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

oh-my-posh

Maintainer pings
cc @lucperkins for testing.

Result of nixpkgs-review pr 195461 run on x86_64-linux 1

1 package built:

oh-my-posh


WT_VERSION Environment Variable

In addition to the WT_PROFILE_ID and WT_SESSION, would be nice to see a WT_VERSION environment variable as well... this could be used to allow some level of feature detection in order to allow some more advanced features without complex interrogation.
Such as with #204 when implemented, such as via supports-hyperlinks

This feels like the wrong solution to this problem IMO. When the Terminal does eventually get hyperlink support, it will come first through the Windows Console. In that case, both the console and the Terminal will support hyperlinks, but if people rely on the presence of WT_VERSION, then the console will incorrectly be detected as not supporting hyperlinks.

Yeah, I'm going to NAK this one hard. It's also somewhat of a /duplicate of #1040 :smile:


Add support for bop.fm

Please and thank you!

Feel free to run with the branch I've put up and let me know how it goes.

Seems to work great! I had no idea the code changes were so easy. Next time I'll know how to do it myself. :D

Closed by #529


DeepONet tutorial for Advection Problem

In this PR I uploaded a new tutorial for the DeepONet class since it was missing.
When writing the tutorial I noticed some bugs which I corrected.
Here I report a list of the bugs:

The aggregation (MIONet._aggregator) had the problem that the input was already stacked, but sometimes it is not possible to stack (e.g. net1 output shape [T, N, d], net2 output shape [T, d] and aggregation performs einsum('TNd,Td->TNd', ...)). So to avoid this problem now the MIONet._aggregator function takes as input a tuple of tensors (also more simple for the user to understand).
I replaced the .reshape with .unsqueeze in output_ = self._reduction(aggregated).reshape(-1, 1) since the final aim of the operation is to add an extra dimension, and not reshape the tensor.

Finally, I remove the check consistency of the network outputs before aggregation and put a warning message that the consistency is up to the user to check. This is not because I believe it should be up to the user the check, but it is a permanent fix since the way we were checking the consistency is wrong. Indeed consider what we were doing:
# check trunk branch nets consistency
shapes = []
for key, value in networks.items():
    check_consistency(value, (str, int))
    check_consistency(key, torch.nn.Module)
    input_ = torch.rand(10, len(value))
    shapes.append(key(input_).shape[-1])

if not all(map(lambda x: x == shapes[0], shapes)):
    raise ValueError('The passed networks have not the same '
                     'output dimension.')

This is wrong if the user wants to specify a custom network whose inputs is not in the form [N, len(value)]. For example, consider the following net:
class Net(torch.nn.Module):
    def __init__(self):
        super().__init__()
        self.layer = torch.nn.Linear(2, 100)
    def forward(self, x):
        x_ = x[:, 0, :]
        return self.layer(x_)

Due to the input reshape the line shapes.append(key(input_).shape[-1]) will raise an error since we are trying to slice a two dimensional tensor (input_ = torch.rand(10, len(value))) like a three dimensional one (line x[:, 0, :]).
The problem to check network consistency is more general than just MIONet or DeepONet, as also in FNO we have the same problem. Maybe we can think to make a PR just for this problem.

The comments are made because the checks are just correct for 2D inputs. I commented because it is not still clear what is the data format for all models (2d/3d?).

@ndem0 can we merge or do we wait for fixing the input format?


⚠ Tukarcoid has degraded performance

In 185d5b6, Tukarcoid (https://tukar.co.id) experienced degraded performance:

HTTP code: 200
Response time: 2643 ms

Resolved: Tukarcoid performance has improved in 58f38fb after 12 minutes.


CalcuLaTeX Integration

It would be neat if the templates were paired with CalcuLaTeX solutions such that a LaTeX solution with steps could be autogenerated. I can help get it started if you would like

That looks like a cool tool, but I don't think it's what I'm going for with this project. I'd rather have a straightforward problem and answer generator and leave the process to be taught by teachers and curriculum creators. I also want it to be a solely python library so that I'm not forcing people into using other libraries.


bytes is currently rendered wrong

Currently bytes becomes 'format': 'binary' in JSON Schema, which in turn means it get's rendered as a file input.
I'm not sure what the best solution is, maybe we just support the base64 types and solve it that way.

For some reason, I am not experiencing this. I just changed the Users model in the README demo to have the name as bytes and it renders the same.

Does it submit ok?

Oh, I understand now.


don't remind to track time all the time

“Remind to track time” on desktop app, can it either A) automatically detect when to remind (user normally tracks time every weekday from 7am-4pm) or B) set a schedule of when to notify

Could also learn user behaviour intelligently

This has since been added, hasn't it?

This is done with the tracking reminder improvements.


HHH-9593 Remove superfluous references to enclosing class

1.) Great catches...
2.) Apologies that this took so long to merge -- things fall through the cracks, it seems.

Manually merging...


Extensibility

Allow custom notification systems to be added by apps.
This would require making the service field "soft choices" (drop constraints), so subscriptions can have invalid services (as they could be removed after subscription was configured), but just log normal notification error for those.
Take advantage of this new dynamic service choices to only show services that are configured (ie: slack is not an option if token is not in settings)

If services can be added externally, consider moving slack to its own package to cleanup required dependencies https://github.com/surface-security/django-notification-sender/issues/9#issuecomment-1385416663


RD2024-124: Job runner method

The motivation for this PR is to greater facilitate usage of lm-buddy as a standalone tool outside of Ray.
A user may be interested in running an LM Buddy job from a Jupyter notebook on a dev pod entirely in-memory. This is currently possible, but a user has to manually import the correct entrypoint function from the .jobs module, which is intended to be a bit more shielded.
This PR introduces a generic run_job method that accepts any config and dispatches to the appropriate entrypoint. This seems like a cleaner public API for calling the package.
I've also gone and removed the optional dependency groups, since everything relies on the HuggingFace libraries atm (even lm-harness), and this allows us to get rid of the internal function imports in the CLI.

any README docs that need to change as a result of this? could you describe high-level the expected change in behavior, i.e. how does running CLI change, etc?

any README docs that need to change as a result of this? could you describe high-level the expected change in behavior, i.e. how does running CLI change, etc?

Running the CLI does not change
Ive updated CONTRIBUTING.md to account for the now-removed optional dependency groups


Dep should error if toml/lock contains current package.

I think dep should error (and fail hard) on jobs if the toml and/or lock files have the current package listed.
It refuses to add the current package with dep ensure -add <pkg> throwing cannot add current project to itself, but if it's already there for some reason, terrible things can happen.
For example, I was recently bitten by this badly. Here's the rough breakdown:

Working in package gihub.com/foo Previously v0.1.0, has a file with a constant BAR="123"
For whatever reason*, Gopkg.toml and Gopkg.lock included references to<EMAIL_ADDRESS>Upgrade to v0.2.0, incluing changing the constant to `BAR="ABC"
When our build system runs bin/dep ensure -v -vendor-only version 0.1.0 and BAR=123 gets checked out into the /vendor folder.
Finally, on go build, the vendor directory overrides the local file, and the built binary contains 123 instead of ABC (confirmed from both running/failing and from grepping the file.)

This is a pretty subtle and disastrous bug: not only does it mean that /vendor takes precedence over top-level files (which was unexpected to me), it means that you end up with scary mixed-state bugs, where a new feature of the binary exists (so it appears to be the new code), but where some constants will be set to older values, causing unexpected failures and broken functionailty.
I can't think of any situation where you'd want to vendor yourself - and this is supported by the fact that dep ensure -add doesn't let you do it. My proposal is that dep should check for this possibility on normal dep ensure runs, and fail hard, alerting the user of the issue.
But I'd welcome any solution that would have helped me prevent this issue, rather than wasting a couple of hours trying to figure out why my application was trying to read from the wrong database table (the real use for BAR, which had been changed months ago.
Thoughts?
*Why were these values in the toml/lock files, you may ask? I suspect it was from a bad copy/paste when it was initially created and/or migrated to dep. But either way, I think dep should help protect users from shooting themselves in the foot like this.

Dep was officially deprecated earlier this year, and the proposal to archive this repository was accepted. As such, I'm closing outstanding issues before archiving the repository. For any further comments, please use the proposal thread on the Go issue tracker. Thanks!


Add simple Streaming example

Similar to #6 , we want to have a separate main dedicated for a minimal example of using the streaming API

I will take this :) will update the readme as well

this has been completed by #9


client-auth.c: Fix authentication denial for valid logins

According man pages, getgrouplist() always return non-zero number, so we have to handle only the case when user is in more groups than we have static array for.

getgrouplist returns 0 or -1 on all BSD-derived implementations. Only glibc returns numbers > 0.


AI breaks Server when playing words

When the AI connects to the server, the first word is played.  On subsequent turns, however, the server breaks with an error of:

toUpperCase is not a function
Uncaught Promise Rejection

@cking20 This may not be an issue now that we are moving to sockets fully instead?

Fixed in latest PRs.


Project Pages should include artifacts in a nice way

Describe the feature you'd like to request
The goal is to incentivize projects to discover which artifacts (e.g. treasury addresses, contracts, repos), are associated so far and what might be missing.
Then we can provide a call to action to add more data in the right way.
Describe the solution you'd like

Enumerate all contracts that have been 'discovered' by the deployer
Enumerate all treasury addresses that reflect funding
etc

Describe alternatives you've considered
TBD

Partially completed by #1933 #1934 #1935

@ryscheng should we just close this now? We have links but I'm not sure it's "nice". Additionally we're missing links to downstream addresses.


Cannot mint Kitty Items on emulator

Describe the bug
Fresh KI installation, log in to service account and complete initialization. Go to the minting page (http://localhost:3001/admin/mint/). click mint.
The UI doesn't show an error but the "transaction sealed" status never changes. The console shows this error:
useMintAndList.js?0e5d:11 Uncaught (in promise) execution error code 1101: [Error Code: 1101] cadence runtime error Execution failed:
error: mismatched types
  --> 77320623f6e7242b82c227af9a1bc7a1f9f546a8d5cf001f104ad74fcefd973b:56:70
   |
56 |         let result = self.minter.mintNFT(recipient: receiver, typeID: typeID, rarityID: rarityID)
   |                                                                       ^^^^^^ expected `KittyItems.Kind`, got `UInt64`

error: mismatched types
  --> 77320623f6e7242b82c227af9a1bc7a1f9f546a8d5cf001f104ad74fcefd973b:56:88
   |
56 |         let result = self.minter.mintNFT(recipient: receiver, typeID: typeID, rarityID: rarityID)
   |                                                                                ^^^^^^^^ expected `KittyItems.Rarity`, got `UInt64`

error: incorrect argument label
  --> 77320623f6e7242b82c227af9a1bc7a1f9f546a8d5cf001f104ad74fcefd973b:56:62
   |
56 |         let result = self.minter.mintNFT(recipient: receiver, typeID: typeID, rarityID: rarityID)
   |                                                               ^^^^^^ expected `kind`, got `typeID`

error: incorrect argument label
  --> 77320623f6e7242b82c227af9a1bc7a1f9f546a8d5cf001f104ad74fcefd973b:56:78
   |
56 |         let result = self.minter.mintNFT(recipient: receiver, typeID: typeID, rarityID: rarityID)
   |                                                                               ^^^^^^^^ expected `rarity`, got `rarityID`

error: cannot access `itemRarityPriceMap`: field has private access
  --> 77320623f6e7242b82c227af9a1bc7a1f9f546a8d5cf001f104ad74fcefd973b:61:20
   |
61 |             amount: KittyItems.itemRarityPriceMap[rarityID]!
   |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

error: mismatched types
  --> 77320623f6e7242b82c227af9a1bc7a1f9f546a8d5cf001f104ad74fcefd973b:61:50
   |
61 |             amount: KittyItems.itemRarityPriceMap[rarityID]!
   |                                                   ^^^^^^^^ expected `KittyItems.Rarity`, got `UInt64`

Expected behavior
Minting works without any errors

I was not able to reproduce this. I was able to initialize and mint without issues.
Is there anything else about the setup that might have caused this?

weird. I thought I did a fresh install based on the latest of the repo. let me try again

just completed it. still the same error. can someone else try to replicate? I don't know if my local setup is the reason

Your api is out of date, clean docker images.
Or you can try to start with: 'docker-compose --env-file .env.dev --profile dev up -d --build'
Let me know if it helps, if not I can try to help you debug more

Or you can try to start with: 'docker-compose --env-file .env.dev --profile dev up -d --build'

wow, that actually resolved the issue for me. thanks @bluesign!
I wonder how common this might be? worth adding a troubleshooting section to the readme? if not, please close @10thfloor

I think there is a related issue @alxflw , which will make kitty items more friendly.
https://github.com/onflow/kitty-items/issues/214

Closing because resolved. Work is in progress to remove the dependency on Docker.


How to order by position on Pivot table

Hello,
Thank you for the fantastic plugin!!
How do you order by an attribute, which is in a pivot table of a Many-to-Many relationship?
I thought this would do, but it doesn't seem to pick up on the position in the pivot:
Layout.query().where('isInLayoutTree', true).with('components', (query) => {
      query.orderBy('position')
}).first()

The position is in the ComponentLayout pivot table and I'm trying to order the 'components'.
Any advice would be appreciated.
Thank you.

@cizza Hi! Thank you so much for trying out Vuex ORM!
Unfortunately, there's no way to access pivot table data from a related entity, which in this case components. There is an issue about this, and we're planning to add that support.
For now, you could fetch ComponentLayout with nested components to achieve this. It needs to have 1 level deep nesting, and querying is going to be a bit dirty though...

Hi kiaking,
thank you for your reply.  I'm glad I know now that it's not possible at the moment. I've resolved the ordering in a different way, but it would be a really nice functionality to have. I think you've mentioned you are using Laravel on projects and the Eloquent ORM has got this baked it. It's a really useful functionality.
Let me thank you one more time for creating Vuex-ORM, I find it the best addition to the Vue.js ecosystem ever. I wish I knew about it a year ago.

@cizza Ah, OK! Great hear you found a way out. There is an issue to resolve this one, so I'll be closing this issue and let the other issue do the tracking.

Let me thank you one more time for creating Vuex-ORM, I find it the best addition to the Vue.js ecosystem ever. I wish I knew about it a year ago.

Thank you so much! Those words are what makes us keep moving! Please feel free to open other issues if there's anything! 🤝


getImageDataForMinWidth API

Getting image data was also improved by the switch to index meta data on the block... no longer need to decode the image data to determine the correct the data url prefix - can use the indexed encoding format.
fixes #232

This looks good. I feel good about the change, but thinking about it, I'm not 100% sure about how exactly we're going to implement the image data API, passing in the target width. Might take a little experimentation. For that reason, think maybe we should leave that API change in a branch while we experiment with integrating it into the app, just to be sure it's something we want to commit to 100%.

Actually, I guess you're leaving the old API in place? If that's the case, then merge away.

Yep, left it there. Cool, thanks!


Algorithm nice names

This adds support for both PCR lists and algorithm specifiers to use human friendly names rather than hex. I also organized the man pages a little but so the redundant what algorithms are supported are grouped into common files. System tests were updated to use the new nice names.
TODO: Add unit tests.

@williamcroberts this is great! I've tested your branch and it works good for me. It also allowed me to remove code in a script that only had to convert from pretty names for users to the hex values to pass to the tools. Thanks!
I just had a few minor comments in case you want to take it into account.

@martinezjavier I think I got all your comments either addressed or fixed. Thank you for the review. I added the tests back in, that provide (I think) ample coverage. I'll leave this up for another day and see if any new feedback is left.


Adding short name

oc get osaee short for oc get openstackansibleee

/test openstack-ansibleee-operator-build-deploy
recheck

recheck

/lgtm

recheck


GraphQL subscriptions

Howdy 👋
Absolutely love the project. Are there are plans to support GraphQL subscriptions? I see a lot of potential to have rock solid, performant subscriptions with Delta Lake Tables. But it would also be handy to have a polling fallback mechanism like liveQuery implemented in other projects like Hasura.

Definitely seems like a very cool idea and something not hard to implement! There is no active plan to working on this feature, but PRs are very welcome :D

It is cool idea. Looks like this will depends on ROAPI auto refresh? e.g. option 2 or 3 from https://github.com/roapi/roapi/issues/55#issuecomment-962533615

yeah, we will need option 2 or 3 to implement this.


SPEEDTEST_SPEEDTEST_INTERVAL variable should be SPEEDTEST_INTERVAL?

Hi There,
The README lists one of the environment variables as SPEEDTEST_SPEEDTEST_INTERVAL but this is actually referenced in the code as SPEEDTEST_INTERVAL. the .env.sample and docker-compose.yml also reference this as SPEEDTEST_SPEEDTEST_INTERVAL and $SPEEDTEST_SPEEDTEST_INTERVAL but this should just be SPEEDTEST_INTERVAL?
Thanks!

It should be SPEEDTEST_INTERVAL in the README.  I was using some {{CONTAINER}}_{{KEY}} format for environment keys in the .env file some time ago.

The pull request I raised for "enhanced-logging" also fixed this README issue.


Incorrect precedence of UV_INDEX_URL vs --index-url in reqs file

If an index url has been specified directly in the requirements file using -i or --index-url, this should have precedence over env var.
Currently uv will use UV_INDEX_URL if it's set, and ignore the one in the requirements file. Reproducer:
$ uv --version
uv 0.3.1 (be17d132a 2024-08-21)
$ python3 -VV
Python 3.12.4 (v3.12.4:8e8a4baf65, Jun  6 2024, 17:33:18) [Clang 13.0.0 (clang-13<IP_ADDRESS>)]
$ python3 -m venv .venv --without-pip
$ vi reqs.txt
$ cat reqs.txt
--index-url https://test.pypi.org/simple
uv-reqs-example==0.1
$ UV_INDEX_URL=https://pypi.org/simple uv pip install -r reqs.txt
  × No solution found when resolving dependencies:
  ╰─▶ Because uv-reqs-example was not found in the package registry and you require uv-reqs-example==0.1, we can conclude that your requirements are unsatisfiable.
$ UV_INDEX_URL=https://example.org/ uv pip install -r reqs.txt
⠴ Resolving dependencies...
error: HTTP status server error (500 Internal Server Error) for url (https://example.org/uv-reqs-example/)

This is in contrast to pip, where the index url from environment is lower priority to the cmd:
$ uv pip install pip
Resolved 1 package in 308ms
Prepared 1 package in 573ms
Installed 1 package in 11ms
 + pip==24.2
$ PIP_INDEX_URL=https://example.org/ .venv/bin/pip install -r reqs.txt
Looking in indexes: https://test.pypi.org/simple
Collecting uv-reqs-example==0.1 (from -r reqs.txt (line 2))
  Downloading https://test-files.pythonhosted.org/packages/78/20/c8431c9645d1390acce2f2da698539f473818e77a168d135c09279dd7bf5/uv_reqs_example-0.1-py3-none-any.whl.metadata (58 bytes)
Downloading https://test-files.pythonhosted.org/packages/78/20/c8431c9645d1390acce2f2da698539f473818e77a168d135c09279dd7bf5/uv_reqs_example-0.1-py3-none-any.whl (986 bytes)
Installing collected packages: uv-reqs-example
Successfully installed uv-reqs-example-0.1

This makes uv + UV_INDEX_URL somewhat dangerous to use as a drop-in replacement for pip + PIP_INDEX_URL. A failure to install is not the worst scenario, the worst is that you succeed to install potentially totally different packages from a totally different index (note: checksums in the reqs file could protect you from that).

I'm intending to convince you that retaining compatibility with pip is a better choice than documenting as an incompatibility.
Consider when there is a custom default index set. This is pretty common in corporate environments, where PyPI packages may need to be cached, whitelisted or shadowed with patched versions, e.g. by using an internal devpi-server.
The custom index is set as the default index (for all users) by /etc/pip.conf file, owned by root and placed by sysadmin or config mgmt. Now, uv doesn't look at /etc/pip.conf, nor allow a global default configuration, only considers the user's ~/.config/uv/uv.toml.
The next-best option for the sysadmin to put a sensible default would probably be setting UV_INDEX_URL (perhaps in /etc/environment, or by wrapping the uv executable).
However, if the UV_INDEX_URL takes precedence over the index specified by requirements files, that's an unfortunate situation - users would have to unset the env var (which they might not even know about) to allow using the index which the requirements file was attempting to provide.
As I mentioned earlier, the simple failure mode is that packages are not found, but the more confusing and hard-to-debug failure mode is if the installation succeeds but uses the wrong packages (because it was using the wrong index). Switching from pip to uv pip should not be so error-prone.
The failure mode I describe might sound like a weird edge-case, but could actually be quite common especially with devpi-server, where "team-specific" indices could inherit and mirror a default index, to host a mix of their own/patched local versions layered over the default versions.

... and the one in a requirements.txt in a file was picked up (which could be from another project or similar).

I'm not sure what you mean here? Unless I'm mistaken, it is part of the requirements file format that the file can control the index-url. This is not dangerous, because requirements files and their custom indices can not be used during dependency resolving from an index, the requirements file would be installed directly with -r. At least, it's not any more dangerous than a direct url requirement, as specified in PEP 508.


Where is DataAugmentationDino transform being applied to the Images?

I am trying replicate the pre-training of DINOv2 on my custom dataset. I made by own dataset by extending the 'ExtendedVision' dataset and did all the necessary changes.
When I run the pre-training using
python dinov2/train/train.py \     --config-file <output-dir> \     --output-dir <output-dir> \     train.dataset_path=CustomDataset
I can see that the collate_fn is expecting the DataAugmentationDINO transform to be applied to the data. However, the transform does not seem to be applied.
Can someone confirm where this is being applied?

https://github.com/facebookresearch/dinov2/blob/2302b6bf46953431b969155307b9bed152754069/dinov2/train/train.py#L175
https://pytorch.org/tutorials/beginner/basics/data_tutorial.html
Its applied to the dataset class, if you have a your own dataset implementation make sure you call with it the DataAugmentationDINO transform


"Recipes" tab when viewing a recipe detail is not appearing

Describe the bug
Recipe enable/disable not available in recipe detail flyout
To Reproduce
Steps to reproduce the behavior:

Add a recipe with multiple possible recipes (e.g. petroleum)
Open recipe detail dropdown
Observe a lack of "Recipes" tab

Expected behavior
Recipes tab should be available to enable or disable individual source recipes (advanced oil processing, coal liquefaction, cracking, etc)

OS: [e.g. iOS]
Firefox 131.0.3_1
Chromium 129.0.6668.58_1
Version [e.g. 22]

Additional context
Looking at the page in the inspector makes it seem like the portion of the script that handles creating that tab simply isn't getting run as opposed to failing due to a browser-side error.

So this actually isn't a bug. Recipes are now picked under the recipe icon next to the machine that produces it. Unintuitive (at least for people who are used to the old way) but not actually broken. Low discoverability but probably a better approach overall.


[research] show all languages

would need to also filter out the langauges as option

Any news about the topic?

Not yet but I have an idea or two on it now

still nothing, however many readers would be interested -_-

Any news? Shouldn't be too hard to implement since mangadex already does it...

well its not straight forward since tachiyomi normally makes a separate source per a language.  I will add this to this list of things to work on now that the latest release seems stable.

in 2.0.11


Build failed on Xcode 7.3

I try to build FuzzyAutocompletePlugin on the latest Xcode 7.3 (7D175). But it failed.
Undefined symbols for architecture x86_64:
  "_OBJC_CLASS_$_DVTTextCompletionInlinePreviewController", referenced from:
      l_OBJC_$_CATEGORY_DVTTextCompletionInlinePreviewController_$_FuzzyAutocomplete in DVTTextCompletionInlinePreviewController+FuzzyAutocomplete.o
      objc-class-ref in FuzzyAutocomplete.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

do you have solved this problem？ i have the same problem

@liuzhecodekiller https://github.com/erikolofsson/FuzzyAutocompletePlugin @erikolofsson fixed it by ignoring some unavailable functions in Xcode 7.3. You can try it.

Thanks ，i have solve it by same way with you！
------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2016年3月25日(星期五) 下午2:36
收件人<EMAIL_ADDRESS>抄送<EMAIL_ADDRESS>主题: Re: [FuzzyAutocompletePlugin] Build failed on Xcode 7.3 (#121)
@liuzhecodekiller https://github.com/erikolofsson/FuzzyAutocompletePlugin @erikolofsson fixed it by ignoring some unavailable functions in Xcode 7.3. You can try it.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

Duplicate of #118


Schedule's top nav can be improved

I realised the top nav in Schedule, wouldn't it be nice to have each of them evenly distributed using layout_weight

I would like get assigned to solve this for my task https://codein.withgoogle.com/dashboard/task-instances/6039001716752384/

this thing is achieved by doing this
app:tabMaxWidth="0dp"
app:tabGravity="fill"
app:tabMode="fixed"

But now the problem is previously tapMode was set to scrollable. So I am not sure about actually if I should do that change (what if it was set that because some cases have more days?), so if we want it scrollable, then following material design, I was thinking maybe I shoud try adding at 72dp gap, not exactly sure how to do this. One way I can think of is by adding blank tab with width 72dp, if there is any better way please say so? And if making it fixed is fine, then thats also cool.
@mariobehling @the-dagger

Keep it scrollable @rhemon.
We don't want to hardcode anything.

ok so then I should add the 72dp gap at the beginning?

Not sure why that is needed though.
Best,
Harshit Dwivedi
Contact : +919968195588
GitHub https://github.com/the-dagger | LinkedIn
https://in.linkedin.com/in/hadwivedi
Google Play https://goo.gl/wl3loD | Facebook
https://www.facebook.com/daggerdwivedi
On Mon, Dec 5, 2016 at 8:46 PM, Ridhwanul Haque<EMAIL_ADDRESS>wrote:

ok so then I should add the 72dp gap at the beginning?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fossasia/open-event-android/issues/804#issuecomment-264880238,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGQtljpL9BpCH3ZWvOCuRpwgZ9zbdxOSks5rFCrQgaJpZM4LDTf3
.


setState infinity loop in onRegionChange

Hi, when I use this.setState inside of onRegionChange function, program stuck on an infinity loop.
Code :
 onRegionChange(region) {
   this.setState({myVar : 2 });
 }
render() {
return (
         <MapView region={this.state.region} onRegionChange={(region) =>this.onRegionChange(region)} >
           {this.state.markerLevel1} // some marker is here!
         </MapView>
)
}

Is this a bug? what I do this for?

No template, I'll close this.
Don't make the region state dependent, make a search among the issues and you'll find more info about.

But in main doc I see something like this : Using a MapView while controlling the region as state.
what is other way for that? please give me a link or code to find that.

I think this will need to be changed.

So does the documentation is wrong about it ?


Issue with getting container height during mouseup event

We've run into a problem regarding getting the height of a button class we've created for our projects. What we've done is created a class that inherits from PIXI.Container, this class will then add a PIXI.Sprite to itself which is used for displaying the button itself. We then add an instance of PIXI.Text to the sprite, this displays the caption on the button.
We set the sprite to be interactive and bind "mouseover", "mouseout", "mousedown", and "mouseup" on the sprite in order for the button to change it's state. We also bind "click" where we fire any callbacks bound to the button.
Now here's the problem, when we let go of the mouse while the mouse is still over the button it triggers a "mouseout" event shortly followed by a new "mouseover" event, this leads to undesired behaviour of the button, for example, clicking the button fast then holding down the mouse can cause the button to be in it's "over" state rather than the "down" state.
The reason this happens is because we move the caption by a certain offset when the button is clicked, to do this we recalculate the vertical center of the button every time it is clicked, in the process of calculating the vertical center we use "this.height" on our button. Now I believe the problem has to do with the recalculation of bounds that happens in the getter for "height", since, if we get the height directly from one of the textures we assigned to the sprite the problem disappears.
Here's a JSFiddle showing the problem: https://jsfiddle.net/ejbkv8cy/
Looking at line 75 you'll find the method used when moving the caption. There's a line I've commented out, if you swap the line currently there with the one commented out you should see the button start working as desired.

".height" calls getLocalBounds() which breaks up everything. Don't use it.
@GoodBoyDigital I told you so.

Yeah I switched to getting the height from the texture instead, at least for the time being.

Yeah, texture works too.

Duplicate of #2823


bringing this PR up to date

Hi @Angelelz, hope you don't mind but i'm trying to bring this PR up to date in an attempt to get it merged. All I've done is pull main and update */dialect.ts to use the latest Subquery structure. This is my first time contributing to Drizzle so 🤞 i didn't break anything too bad

Anything holding this up from being merged? We could really use it


Allow more commands to happen in the same transaction as deleteMessage

The deleteMessage command serves as an ACK that signals a job is done.
In some cases (mine included), the worker ACKing the job also writes its output to the same redis instance holding the queue.
In such cases, it would be great if writing a job's output and ACKing it will happen within the same transaction, to provide the ultimate atomicity guarantee.
I propose the following syntax:
with rsmq_instance.deleteMessage(id=message_id).transaction() as tx:
    tx.set("output", output)

Where tx is a Pipeline instace pre-populated with the deleteMessage commands and is executed upon __exit__

Interesting. I would need to look to see if the transaction is handled in code or in the Lua script - if in code, this should be doable I would think...

Good news! I just checked, deleteMessage uses only a simple transaction with two commands (zrem and hdel).
Exposing this transaction should be pretty simple.
I will submit a POC PR.

This should be released with 0.4.4+ (somehow Travis/Pypi refused to release it, checking on it now)


2023.9.1: Added accent for days of week

In the dark, it is very difficult to tell the time of the week as you can only see the current streak of the day, but this way it will be clear what day it is in any light.

can you show a sketch or sample what this does?


Implement triaging process

I think it is time to professionalize our issue / PR ingest process by implementing a triage process. As of the Kubernetes maintainers (see here)

Issue triage is a process by which a SIG intakes and reviews new GitHub issues and requests, and organizes them to be actioned - either by its own members, or by other SIGs. Triaging involves categorizing issues and pull requests based on factors such as priority/urgency, SIG ownership of the issue, and the issue kind (bug, feature, etc.).

According to them triaging has the following benefits, such as

Speeding up issue management
Keeping contributors engaged by shortening response times
Preventing work from lingering endlessly
Replacing special requests and one-offs with a neutral process that acts like a boundary
Greater transparency, interesting discussions, and more collaborative, informed decision-making
Building prioritization, negotiation and decision-making skills, which are critical to most tech roles
Reinforcement of SIG community and culture

I think there is room for improvement in several of these areas in the Carbyne Stack project, hence my request to implement a triage process.
Personally, I am inclined to go for the Linux Foundation, in particular the CNCF, when we decide it is time to donate the project to a foundation. Hence, it makes a lot of sense for me to adopt their process (when it makes sense) already now. However, deploying the heavy machinery they use, like Prow, would be overkill as of today considering the current size of the Carbyne Stack community.
Hence, my suggestion is to implement a lightweight version of the process described here. This would involve the following steps:

[x] Select the subset of labels we actually want to use. In my opinion that should be the lifecycle/, triage/, kind/, and priority/ labels classes and the needs-triage label (subset of these).
[x] Come up with a process description (as part of the contributor guide) that heavily borrows from the K8s process description linked above.
[x] Define the selected labels (plus maybe others) as the default set of labels in the CS org.
[x] Adjust the labels in the existing repositories to include the selected labels. It has to be discussed whether the existing ones should be renamed or kept. Removal is no good idea and may be even not possible as existing issues and PRs make use of them. It might make sense to write a script to do this daunting job.
[ ] Configure the stale plugin to act in accordance with the process description (see #22).

Thoughts @sbckr, @jaredweinfurtner?

One can search for all issues in a specific org with any of the given labels (ORed) by using user:carbynestack is:issue label:"<label-1>", label:"<label-2>" in the Github search bar. See here for what is possible.
Guess this will become very handy in the triaging session to quickly find all relevant issues. Same works for PRs.

The needs-triage label has to be assigned to all newly opened and reopened issues and PRs. This can be achieved easily with GHA as described here.

I provided a first proposal for the triaging process as a guide here #44.

My proposal would be to use these labels with their respective meaning except the following:

do-not-merge/needs-kind
kind/api-change
kind/deprecation
kind/design
lifecycle/active
needs-kind
needs-priority
sig/cluster-lifecycle

Labels in existing repositories have been updated using a small tool written in golang (see carbynestack/.github#3).

Need your help now @jaredweinfurtner to implement the assignment of the needs-triage label (see https://github.com/carbynestack/carbynestack/issues/42#issuecomment-1259572577) and configuring the stale plugin (see https://github.com/carbynestack/carbynestack/issues/42#issue-1364844328).

@strieflin The re-usable workflows (for both auto-labeling of triage and stale-action cleanup) are in this PR: https://github.com/carbynestack/.github/pull/2.
Once that is merged, please review the PRs for each repository to utilize these reusable workflows:

cli - https://github.com/carbynestack/cli/pull/27
cli-ng - https://github.com/carbynestack/cli-ng/pull/97
carbynestack.github.io - https://github.com/carbynestack/carbynestack.github.io/pull/70
castor - https://github.com/carbynestack/castor/pull/40
java-http-client - https://github.com/carbynestack/java-http-client/pull/16
amphora - https://github.com/carbynestack/amphora/pull/38
carbynestack - https://github.com/carbynestack/carbynestack/pull/43
common - https://github.com/carbynestack/common/pull/41
ephemeral - https://github.com/carbynestack/ephemeral/pull/29
mp-spdz-integration - https://github.com/carbynestack/mp-spdz-integration/pull/17
klyshko - https://github.com/carbynestack/klyshko/pull/7
corporate-information - https://github.com/carbynestack/corporate-information/pull/3

base-images and cli-ng still not done.

Changes in cli-ng done (carbynestack/cli-ng#97).

Changes in base-images done (carbynestack/base-images#11).


33s->33ms

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


Add support for text submissions

Thanks a lot for your PR. Could you please add tests that test the types of the returned entities? (Call each method once, run a test using typeguard)

Sorry for the late update. Tests have been added.


Rock Paper Scissors Python Game

Rock Paper Scissors Python Game issue#224.
Made a rock paper scissors python game. The game calculates the score of both the player and the computer and randomly selects option for computer using random module.
GSSoC'22 Contributor.

@Mennatallah9 add .ipynb file(Jupyter notebooks or Google collab notebooks) and readme.md file as well ...

@Niketkumardheeryan Done!

@Niketkumardheeryan Done!

could you please add a demo in your reame.md file

@Niketkumardheeryan Done!

could you please add a demo in your reame.md file

Yes sure!

@Niketkumardheeryan  Sorry for the delay. I've updated the readme.md file could you check it out please?


add link

Coverage decreased (-0.01%) to 53.843% when pulling bb40d2a36d9b40f9752cf908ffcf9ec79e063be8 on mintao/doc into 5b4733ff8b51d769e7ea4d20f0a9c0e63b276a16 on zhiyuhe/v0.14.0_docs.


Relative Face position

Is there a way to get the relative (0-100) position of face detection / landmark on a image?

Solved:
facePosY = (resizedResult._box._y + resizedResult._box._height ) / displaySize.height


Openvpn Connect v.3

Hi,
I'm testing with Openvpn connect 3 as mac client, it not work.
it is supposed to work with Openvpn connect?

Didn't even know that OpenVPN Connect 3 exists for MacOS.
Reading https://openvpn.net/vpn-server-resources/connecting-to-access-server-with-macos/ it seems like the client is designed for the OpenVPN Access Server. Not sure, if the client works against OpenVPN 2 server.

Openvpn Connect is a client for windows/macos which works nice with all openvpn edition.
I using it for more then 2 years with an Openvpn 2.4.4 Server.
this is what i got on openvpn server logs:
PUSH: Received control message: 'PUSH_REQUEST'

and this what i have on client logs:
⏎[Sep 24, 2023, 15:08:03] Creds: Username/Password
⏎[Sep 24, 2023, 15:08:03] SSL Handshake: peer certificate: CN=server, 2048 bit RSA, cipher: TLS_AES_256_GCM_SHA384         TLSv1.3 Kx=any      Au=any   Enc=AESGCM(256)            Mac=AEAD

⏎[Sep 24, 2023, 15:08:03] Session is ACTIVE
⏎[Sep 24, 2023, 15:08:03] EVENT: GET_CONFIG ⏎[Sep 24, 2023, 15:08:03] Sending PUSH_REQUEST to server...
⏎[Sep 24, 2023, 15:08:04] Sending PUSH_REQUEST to server...
⏎[Sep 24, 2023, 15:08:06] Sending PUSH_REQUEST to server...

How I can logs all events the management interface?

Running with CONFIG_LOG_LEVEL=debug (--log.level=debug) shows you all command between plugin and management interface

Found the issue!!!
it Worked when I removed the password file from
management <IP_ADDRESS> 8081 password.txt
with just management <IP_ADDRESS> 8081
and Removed from the yaml configfile.

Could you please try the lastest version?
Yesterday, I figure out some issues if, the management interface has a password enabled. it should fixed in 1.4.0

Seams it not received the line from Management interface:
	line, err := c.readMessage()
	if err != nil {
		return err
	}
	fmt.Printf("Received Line %v \n",line)               ### This will not Print anything!
	if strings.HasPrefix(line, "ENTER PASSWORD") {
		if err := c.rawCommand(c.conf.OpenVpn.Password); err != nil {
			return err
		}

		line, err := c.readMessage()
		if err != nil {
			return err
		}

		if !strings.HasPrefix(line, "SUCCESS: password is correct") {
			return errors.New("wrong openvpn management interface password")
		}
	}

Ok, I can confirm with 1.4.0 Version it works!
Thank you Very much!

Thanks for the hint that OpenVPN 3 for Mac works fine, I add the client to the compatibility list.


Tool Calling - how can we request to the LLM that it re-calls for data after a period of time

In my use case the data changes and the LLM keeps returning and using cached data ....
any ideas or tips to avoid this ?
Thanks

I've also been thinking about those kinds of problems.
You need to understand, that an LLM is just a Text -> Text function. And all other logic ("architecture" of an LLM app) should be managed externally.
If you have a tool call, that LLM uses, then it's the responsibility of the programmer who made the system to handle the tool call.
Not LLM returns output, but a combination of LLM + tools + servers that handle requests.
 Turn if off, or make the expiry less

Thanks.  My tool side of things always returns the latest / live data.  The issue is that if the LLM has called it once it often caches the tool result in the LLM so the LLM does not call the tool for every request (which I would like).  Ive tried adding plenty of hints via @Tool which helps a bit but still it caches some data / fails to re-execute the actual tool call (if that makes sense).


Weird resizing bug

It's a weird thing, yet I notice that the player can sometimes desync from movement for the Scene Editor when resizing the window, most noticeable when shrinking

I added snappier movement to it, so it is at least not noticeable.


Campfire Adapter emit errors

We've had the ability to emit 'errors' for awhile, but the Campfire adapter wasn't updated to use this. This should mean that if you have an error handling script, you'll be able to catch the floods of rate-limiting errors when you connect with lots of rooms.
cc https://github.com/github/hubot/pull/699

It is probably okay to merge, but it has been so long I don't remember what the underlying problem we were trying to identify, and now that we're off Campfire, there's not a good way to validate it.

Ok. Should we just close this then?

Code seems to be safe enough, just covering usage of err. I would vote for a merge.

I'm just going to close this. I don't think it's a good habit of getting into of merging code that "looks good" without actually being able to validate it.


Controller composition

We should support grouping controllers with similar properties, mostly for organization but also for sharing metadata across them instead of requiring either global metadata configuration for all pages or everything being locally defined on the view controllers. The "AppController" is just a special universal case of this behavior where it also takes care of application level initialization.

This should be largely taken care of with programatic layout controllers.


Recent update did something to Webmin Sysstats

Hi!
After the latest Authentic theme update the webmin sysstats subsite doesn't load. It just shows a blank page. Switching to any of the Webmin inbuilt themes makes the sysstats load correctly. Any chance of looking into this :)
Sysstats module: http://webminstats.sourceforge.net

Hi,
Yes. I forgot to add an exclusion. It's very wrong that some modules not using ui_print_footer(); functions. It's actually very wrong.
Here is the patch for CSS extensions in theme's settings:
body.sysstats .container-fluid {
    pointer-events: auto !important;

    opacity: 1 !important;
}

Does it fix it? Yes? I will add it to the distro!

Thank you very much!

https://github.com/qooob/authentic-theme/issues/396
I'm creating exclusion list, stay tuned. It'll be in version 17.72.

Will be fixed in 17.72 and provide options for modules that need to be excluded.
https://github.com/qooob/authentic-theme/issues/396#issuecomment-185839541

Please upgrade to 17.72.


typo on README.

Found a typo on README.md

I signed it!
--
Tiago Justino
http://tiago.justino.com.br/
On Tue, Aug 4, 2015 at 3:46 PM, googlebot<EMAIL_ADDRESS>wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project, in which case you'll need to
sign a Contributor License Agreement (CLA).
[image: :memo:] Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll
verify. Thanks.

If you've already signed a CLA, it's possible we don't have your
GitHub username or you're using a different email address. Check your
existing CLA data https://cla.developers.google.com/clas and verify
that your email is set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
If you signed the CLA as a corporation, please let us know the
company's name.

—
Reply to this email directly or view it on GitHub
https://github.com/GoogleChrome/accessibility-developer-tools/pull/223#issuecomment-127783130
.

Woot! Thanks @TiagoJustino :star2:


$cachedResource is not $resource

At the moment your $cachedResource is not a drop-in replacement for $resource, as it requires one to rewrite all the code where $resource calls get made. I suggest you mixin/enrich your functionality on the original $resource provider, enabling drop-in and later removal of your module without breaking code.
So in an ideal scenario one would just load your plugin, optionally with a configuration that contains things such as TTL per resource, and it would just work without code rewriting.
I don't have much time to do this myself, but I can advise and review ;)

I'm wondering if it could be done today by decorating the $resourceProvider with $cachedResource.


Streamlit app viz issues

Need to change this. the  viz is not working
Screenshots

Smartphone (please complete the following information):

Browser [e.g. stock browser, safari]

Please assign me this issue. I am confident to resolve it.

sir, user should upload the csv file that contains review column because our app is to analyze the reviews and classify them as positive or negative.

@revanth1718 what csv file you have used, can u attach here. the csv file I upload didn't work as expected.

reviews.csv

Please assign me this issue.

Please assign this issue to me . I am a contributor in GSSOC'24.


Fix flaky test in CollectionUtilsTest.Java

The test below in CollectionUtilsTest.java was found flaky because of the ordering of result HashMap. The orders of elements in the HashMap are not the same as every time the test being called. In this case, LinkedHashMap was applied to ensure the orders do not cause the flakiness. This code change is trying to fix the flaky tests mentioned above, because they sometimes fail (as the picture showed) and sometimes pass. The failure could be reproduced by the commands above by using the tool of NonDex. The code change is to make sure the tests will always pass in this case.

org.apache.commons.collections4.CollectionUtilsTest.get

The test failures could be reproduced by

mvn install -pl . -am -DskipTests
run tests with NonDex
mvn -pl . edu.illinois:nondex-maven-plugin:1.1.2:nondex -Dtest=org.apache.commons.collections4.CollectionUtilsTest#get

Codecov Report

Merging #360 (b9759cf) into master (9bbfad5) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #360   +/-   ##
=========================================
  Coverage     81.17%   81.17%
  Complexity     4603     4603
=========================================
  Files           289      289
  Lines         13452    13452
  Branches       1979     1979
=========================================
  Hits          10919    10919
  Misses         1935     1935
  Partials        598      598

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

I believe this is fixing a non-issue artificially introduced by the nondex plugin. The HashMap has an unspecified iteration order, but it is a deterministic data structure. If it is not modified then the iterator will return the same order.
This is different from other changes identified by nondex (see #341, #353) where the test assumptions about ordered iteration were false.
However I think the suggested change is harmless and it will prevent others identifying the same issue in the future using the nondex plugin.


Ant o

created a simple layout in html/css to come up with a design on which we all will all agree on and go from there.

Hey approving. Just wanted to confirm in your css, under button font size is that supposed to be 1rem?

I didn't catch that, googled the difference I should be using rem to scale off of root font size in html.


rtm_client.start() fails

Description
from slack import RTMClient

slack_bot_token = os.environ.get('SLACK_BOT_TOKEN')
rtm_client = RTMClient(token=slack_bot_token)
rtm_client.start()

What type of issue is this? (place an x in one of the [ ])

[x] bug
[ ] enhancement (feature request)
[ ] question
[ ] documentation related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x ] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x ] I've read and agree to the Code of Conduct.
[ x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
slackclient version: 2.4.0
python version: 3.7
OS version(s): macOS 10.15.1
Steps to reproduce:

pip3 install slackclient
Run the code in the Description

Expected result:
Authentication successful
Actual result:
raise e.SlackApiError(message=msg, response=self)
slack.errors.SlackApiError: The request to the Slack API failed.
The server responded with: {'ok': False, 'error': 'not_authed'}

Attachments:
Side Note, the WebClient authenticates successfully.

:wave: Sorry for our very late response here. This looks like an issue related to the absence of a token. The error code not_authed generally indicates the absence. If your token is incorrect, you'd see invalid_auth error instead.
(venv) $ cat app.py
from slack import RTMClient
rtm_client = RTMClient(token='')
rtm_client.start()

(venv) $ cat requirements.txt
slackclient==2.5.0

(venv) $ python3 app.py
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/slack/rtm/client.py", line 329, in _connect_and_read
    url, data = await self._retreive_websocket_info()
  File "/usr/local/lib/python3.7/site-packages/slack/rtm/client.py", line 503, in _retreive_websocket_info
    resp = await self._web_client.rtm_connect()
  File "/usr/local/lib/python3.7/site-packages/slack/web/base_client.py", line 226, in _send
    return SlackResponse(**{**data, **res}).validate()
  File "/usr/local/lib/python3.7/site-packages/slack/web/slack_response.py", line 176, in validate
    raise e.SlackApiError(message=msg, response=self)
slack.errors.SlackApiError: The request to the Slack API failed.
The server responded with: {'ok': False, 'error': 'not_authed'}

Let me know if you have something further to ask/clarify here. Otherwise, please allow me to close this issue within a few days.

Im having a similar issue, but I think I just dont understand the correct token to use.
import os
from slack import RTMClient
from slack.errors import SlackApiError

rtm_client = RTMClient(token=os.environ["SLACK_API_TOKEN"])
rtm_client.start()

and then running the command:
SLACK_API_TOKEN='xoxb-<some_numbers>-<more_numbers>-<letters>' python hello_world.py

and get the error: The server responded with: {'ok': False, 'error': 'not_allowed_token_type'}
I think Im just using the wrong token type, but the slack website doesnt make it obvious what token to use. This is the "Bot User OAuth Access Token" from the slack "Install app" page. Ive also tried the "Client Secret", "Signing Secret", and "Verification code" from the Basic Information page for the bot, but none of them work. What does the correct token look like? How do I find it?

@sterlingbaldwin Did you create your Slack app recently? If so, the default way no longer supports RTM. You need to create a "classic" Slack app from https://api.slack.com/apps?new_classic_app=1 . (you can find the link at the bottom of https://api.slack.com/authentication/migration)
similar issue: https://github.com/slackapi/python-slackclient/issues/609#issuecomment-608352189

Thanks @seratch

👋 Sorry for our very late response here. This looks like an issue related to the absence of a token. The error code not_authed generally indicates the absence. If your token is incorrect, you'd see invalid_auth error instead.
(venv) $ cat app.py
from slack import RTMClient
rtm_client = RTMClient(token='')
rtm_client.start()

(venv) $ cat requirements.txt
slackclient==2.5.0

(venv) $ python3 app.py
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/slack/rtm/client.py", line 329, in _connect_and_read
    url, data = await self._retreive_websocket_info()
  File "/usr/local/lib/python3.7/site-packages/slack/rtm/client.py", line 503, in _retreive_websocket_info
    resp = await self._web_client.rtm_connect()
  File "/usr/local/lib/python3.7/site-packages/slack/web/base_client.py", line 226, in _send
    return SlackResponse(**{**data, **res}).validate()
  File "/usr/local/lib/python3.7/site-packages/slack/web/slack_response.py", line 176, in validate
    raise e.SlackApiError(message=msg, response=self)
slack.errors.SlackApiError: The request to the Slack API failed.
The server responded with: {'ok': False, 'error': 'not_authed'}

I does work now. Just to note, I had put in the right token. Yet, it wasn't working. I did a clean install of the client and now it works. Thanks!

@denzilc Great to know!


use timestamptz for Swift.Date conversion

See https://github.com/vapor/postgresql/pull/117 on a discussion of the problems associated with this, and what needs to be done to avoid them.

Everything uses TIMESTAMPTZ now.


az functionapp deployment fails when deploying to an app with identity based connection for storage

Describe the bug
Deploying to a function app that uses an identity based connection for AzureWebJobsStorage (e.g. AzureWebJobsStorage__accountName) fails validation when running
 az functionapp deployment source config-zip.
To Reproduce
Follow the steps outlined here.
Expected behavior
Deployment should complete.
Actual behavior
Deployment fails with the error Could not find a 'AzureWebJobsStorage' application setting
Environment summary
azure-cli                         2.11.0
core                              2.11.0
telemetry                          1.0.5
Extensions:
appservice-kube                    0.1.7
Python location 'C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\pbatum.azure\cliextensions'
Python (Windows) 3.6.8 (tags/v3.6.8:3c6b436a57, Dec 23 2018, 23:31:17) [MSC v.1916 32 bit (Intel)]
Additional context

Looks like this validation logic is the problem:
https://github.com/Azure/azure-cli/blob/d1676f65bc643396ea1f562ac29cf2c66cd55d05/src/azure-cli/azure/cli/command_modules/appservice/custom.py#L539-L545

route to service team

Thanks @paulbatum, it looks like this is going to require some additional changes because we assume it's going to be a connection string here.

When not using Azure Files but using Managed Identity for AzureWebJobsStorage
az functionapp deployment should default to remote build. As the app is not using Azure Files, if using Run from package =1, content will upload to data\sitePackages - Windows Consumption, Dedicated, Linux Dedicated.
When using Azure Files but using Managed Identity for AzureWebJobsStorage

Remote build does not work without key vault references or full connection string. This is currently blocked on Azure Files supporting mounting vis Managed Identity.

Any idea when it would be fixed ? :)

Any Estimate on the fix ? Seems the main thread is locked and being looked into?
https://github.com/Azure/azure-functions-core-tools/issues/2671

In case anyone stumbles over this issue, I found a workaround. Basically setting the config setting core tools is looking for, then running core tools, then restore the original settings. I made a PS wrapper script for the core tools call to make this work until core tools get fixed. So if anyone needs a quick&dirty solution, here it is: https://github.com/ArunasFalcon/MIAzureFunctionDeployWrapper

This issue belong to the azure-functions-core-tools


cairo7 domain

government issued email adress (office 365)
http://www.moe.gov.eg/

@LoaiDev This domain does not belong to a university, nor to a college. I have to close the request without merging. Please ensure that you are familiar with this repository rules located at the bottom of this page before submitting a new request.
If your school does not have a specific email domain that is unique for this school, please apply for free educational license with an official document which proves that you are a student. You can do it using "OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students.
Thank you for your understanding!


fix(layout): text layout issues

Please read and mark the following check list before creating a pull request:

[x] I read and followed the CONTRIBUTING.md guide.

Short description of what this resolves:

Refactors text to use category where it causes layout issues

Updated in #115


'push' fails if upload takes more than 60 seconds

https://github.com/elastic/synthetics/blob/f75c4705b30f30a2b33b2d20e82b18a65adfa0e6/src/push/request.ts#L51
We have quite small project with about 10 journeys and 10 lightweight scripts, but it's expected that project will grow to have more than hundred different scripts in it. Existing implementation of 'push' fails even with existing project, because it takes more than hardcoded 60 seconds to perform operation. As far as I can tell there's no option to change this timeout, updating synthetics.config.ts with something like this doesn't work:
import { setGlobalDispatcher, Agent } from "undici";

setGlobalDispatcher(
  new Agent({
    headersTimeout: 5 * 60 * 1000,
  }),
);

Error if push takes more than 60 seconds:
HeadersTimeoutError: Headers Timeout Errors)
    at Timeout.onParserTimeout [as callback] (/***/***/git/synthetics-journeys/node_modules/undici/lib/client.js:931:28)
    at Timeout.onTimeout [as _onTimeout] (/***/***/git/synthetics-journeys/node_modules/undici/lib/timers.js:20:13)
    at listOnTimeout (node:internal/timers:559:17)
    at processTimers (node:internal/timers:502:7) {
  code: 'UND_ERR_HEADERS_TIMEOUT'
}

push should have timeout options or even better - refactored, so that all monitors are not pushed in single bulk request.
And no, it is not possible to have multiple small projects, all journeys should exist in single project.

@kazagz can you please describe your setup? i mean are you using public locations, private locations. Generally we expect push  command to be very very fast. It seems like your setup is too slow in some aspect. I would like to understand more on why it might be taking so long to push command. Either kibana is too slow or may es. Does your kibana and ES are on the same network?

@shahzad31 we're using private locations and have self-managed / on-premise platform. Monitors are pushed to Kibana from CI/CD pipeline. Kibana and Elastic are on same network. Pipeline and Kibana / Elastic are not on same network in a sense that Kibana server and CI/CD agents are in different segments, but they are on same datacenters and there's no issues with network latency etc.
Our journeys use some external npm packages in them so bundles would be larger than those that only contain out-of-the-box @elastic/synthetics packages.
We might in fact need some optimizations for our Kibana and Elastic, because these timeouts do tend to happen at times when there's some other workload being done by Kibana / Elastic, but that won't solve the issue permanently. Example, now on 'good' run (with Kibana / Elastic idle) it would take about 10 seconds to push monitors. On 'bad' run it would take about 70 seconds. Even if we do run pipeline on only 'good' timeslots, our goal is to have hundreds of journeys in project (x10 than we have now), which means that even on 'good' run it would almost certainly exceed 60 seconds for command to complete. I would feel much better if there would be an option to customize timeout or global configuration for undici.

@kazagz i have merged a PR to increase timeout to 120sec which aligns it with default kibana API timeout.  We will discuss internally to make it configurable , in that case we will also need to change kibana API timeout.


[IDEA2] menu buttons

[again i dont know if it is possible 100%]It would be cool if you could add the old roblox topbar from 2016-2019ish

This would be a cool feature

ALSO - i know the playerlist is not possible, im just talking about the top bar

You cant

The top bar isn't possible either.

[again i dont know if it is possible 100%]It would be cool if you could add the old roblox topbar from 2016-2019ish

This would be a cool feature

i wanted this feature too i will never be able to bring back old roblox :(


Versions cannot be pinned as expected

🐛 Bug Report
Pinning the versions of @docusaurus/core and @docusaurus/preset-classic results in different versions of @docusaurus packages being installed. I believe this is because of the version ranges specified in each package. For example.
Have you read the Contributing Guidelines on issues?
Yes
To Reproduce

npx @docusaurus/init@next init my-website classic
In package.json change the versions of @docusaurus/core and @docusaurus/preset-classic to 2.0.0-alpha.59
yarn
Peer into your node_modules or yarn.lock

Expected behavior
Pinning the versions of @docusaurus/core and @docusaurus/preset-classic results in all @docusaurus packages being the same version.
Actual Behavior
Pinning the versions of @docusaurus/core and @docusaurus/preset-classic results in different versions of @docusaurus packages.
If I'm not missing something and this isn't expected, then I'd be happy to open a PR. I'm eager to make my first contribution.

Hi
I'm not sure what we can do about this.
Isn't it a package manager potential bug instead?
Can you upload your attempt to a repo? That's a more reliable repro case
Le jeu. 30 juil. 2020 à 08:09, Bucky Maler<EMAIL_ADDRESS>a
écrit :

🐛 Bug Report
Pinning the versions of @docusaurus/core and @docusaurus/preset-classic
results in different versions of @docusaurus packages being installed. I
believe this is because of the version ranges specified in each package.
For example
https://github.com/facebook/docusaurus/blob/master/packages/docusaurus/package.json#L48
.
Have you read the Contributing Guidelines on issues
https://github.com/facebook/docusaurus/blob/master/CONTRIBUTING.md#reporting-new-issues
?
Yes
To Reproduce

npx @docusaurus/init@next init my-website classic
In package.json change the versions of @docusaurus/core and
@docusaurus/preset-classic to 2.0.0-alpha.59
yarn
Peer into your node_modules or yarn.lock

Expected behavior
Pinning the versions of @docusaurus/core and @docusaurus/preset-classic
results in all @docusaurus packages being the same version.
Actual Behavior
Pinning the versions of @docusaurus/core and @docusaurus/preset-classic
results in different versions of @docusaurus packages.
If I'm not missing something and this isn't expected, then I'd be happy to
open a PR. I'm eager to make my first contribution.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/facebook/docusaurus/issues/3161, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFW6PRDYFR5B3W6BOPW2KDR6EE77ANCNFSM4PM565FQ
.

@slorber I just opened a PR because I think it's as easy as pinning the versions inside of each package's package.json. I don't think it's a package manager bug.


KITE-1053: Fix int overflow bug in FS writer.

Keeping the number of records written in an int caused a bug where
writing more than Integer.MAX_VALUE records (~2B) would overflow the
counter and the check to see whether any records had been written would
fail because count is less than 0. The fix is to use a long.

@mkwhitacre, could you review this? It fixes an issue where too many records written from a single reducer will cause data files to be discarded instead of committed.

Change looks fine.  For my own knowledge can you provide a link to the code that checks if any records were written?

Yeah, the check is here: https://github.com/kite-sdk/kite/blob/master/kite-data/kite-data-core/src/main/java/org/kitesdk/data/spi/filesystem/FileSystemWriter.java#L196
When debug logging is on, we see that the else case is taken with the log message: DEBUG [main] org.kitesdk.data.spi.filesystem.FileSystemWriter: Discarded hdfs://.../.33c9684a-f4e9-432b-a003-2efaccfaa0d4.avro.tmp (-1969937604 entities)

Since the value of count doesn't really matter would tracking if data was written as a boolean be safer to avoid any overflow errors?

@mkwhitacre, yes and no. Yes it would technically be safer. But I don't think Java can handle files that are larger than Long.MAX_VALUE bytes, which means that if you are overflowing the record count now, you'd also be unable to write anything to the file.
In addition, check out #386 that adds size and time-based file rolling to the internal writers. That requires having the count so I'd rather not remove it to add it back later.

Ok thanks.  #386 and the ability to specify number of writers per partition should hopefully help me eliminate some custom code to try and more evenly distribute data across shuffles and still end up with appropriately sized files.

@mkwhitacre, great! Feel free to review that one, too.
So this one is good to go?

+1

Thanks for reviewing this, @mkwhitacre!


Optimize the implementation of IniParser

The IniParser could definitely use some improvements: the _Lex() member function has two loops for removing comments and another loop for the rest all done per line.

This will no longer be worked on as the parser will be rewritten from scratch.


make finalization configurable by environment variable

This will be the same as the v0.1.0eth2 production bridge except that USE_FINALIZATION can be configured with environment variable. It is true by default and can only be disabled with an explicit USE_FINALIZATION=false var

the clippy and rust audit checks will fail as expected because we want to make this as close to possible as v0.1.0eth2


[ENH] Add LivePlot line style cycler

The number of colors increased with the matplotlib version change.  However, we still run out of colors in a single plot.  It would be great to add a cycler for different lifestyles (solid, dashed, dot, etc).

This can be done without any changes to LivePlot. See for example this page of the matplotlib documentation and let us know if you have any questions.
I'm going to close this issue as I don't think it's in scope for bluesky, but I'm happy to answer follow-up questions here. It may be useful to have this issue as a record in case this comes up again.

@danielballan I understand how to do this in a notebook.  Are you saying that I can make a custom plan do this?  Or are you telling me that if I want to cycle the line style that I need to plot the data in an python notebook and implement a line style cycler?  I already know how to do the later. I was just asking for an enhancement so that when someone comes in after an overnight script, then can quickly make a decision based on the bsui LivePlot figure.

I think this should work exactly the same in a notebook or interactively at the terminal. Is that the question?

My request was to make the LivePlot do this without me having to type anything in the window.  Are you saying that I can do this if I create a custom plan?  Or are you saying that I should manually re-plot the data and ignore the bsui plot that occurs with any scan?
From: Dan Allan <notifications<EMAIL_ADDRESS>Reply-To: NSLS-II/bluesky <reply<EMAIL_ADDRESS>Date: Tuesday, October 24, 2017 at 3:28 PM
To: NSLS-II/bluesky <bluesky<EMAIL_ADDRESS>Cc: Andi Barbour <abarbour<EMAIL_ADDRESS>Author <author<EMAIL_ADDRESS>Subject: Re: [NSLS-II/bluesky] [ENH] Add LivePlot line style cycler (#872)
I think this should work exactly the same in a notebook or interactively at the terminal. Is that the question?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/NSLS-II/bluesky/issues/872#issuecomment-339104161, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AM_7GfOYQzcrHNxUb9LGX1T3T-vy4Ikiks5svjpngaJpZM4QDWbC.

You can change the default matplotlib color cycle to be one with more colors in it. I think that would solve your problem. LivePlot can't automatically do this for you because it will never know in advance how many lines you plan to put on the same axes, but it could just always use a color cycle with a large number of colors.

OK that makes sense.  This would be in the matplotlib bashrc, or I could alternatively import matplotlib and set it up that way.  The second option was already done so we could have the grid displayed.  So I will try it that way.  Thanks for your patience
From: Dan Allan<EMAIL_ADDRESS>Sent: Tuesday, October 24, 2017 3:35 PM
To: NSLS-II/bluesky
Cc: Barbour, Andi; Author
Subject: Re: [NSLS-II/bluesky] [ENH] Add LivePlot line style cycler (#872)
You can change the default matplotlib color cycle to be one with more colors in it. I think that would solve your problem. LivePlot can't automatically do this for you because it will never know in advance how many lines you plan to put on the same axes, but it could just always use a color cycle with a large number of colors.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/NSLS-II/bluesky/issues/872#issuecomment-339106113, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AM_7GbZNB5vgLOKYG13JtFsqezD1bUFWks5svjv2gaJpZM4QDWbC.

Sure, no problem. Yes, the matplotlibrc is the place to change this.


Terminal: find widget gives flaky results

Terminal, open find widget, find something -> works fine
Try to find some other term -> sometimes fails
If there are multiple instances of a result, sometimes moving between them fails

I can repro this flaky behavior both on my OS X with zsh shell and Win10 with powershell.
If nobody reported this so far please let me know and I will try to find better repro steps.

This is the first report, more details steps please :smiley:

Ok here are steps which always repro on my os x zsh shell

vscode repo, terminal, do a ls
cmd + f, search for something, get results, search for something else no results

I can also repro on my win10 powershell but not so consistently

@isidorn
@Tyriar
I can also see this frequently on Windows 7/CMD.EXE
Usually the second search term fails, however this is not one hundred percent consistent.
Once the problem occurs, it appears to be "permanent" until you kill the terminal instance and start a new one.
I think I may have seen this while working on simpleFind but was possibly fooled by Dragon issues.
@isidorn  - what screen capture to use that is good for github ? and works on Windows.

@cleidigh the creen capture I use is liceCap and I use it on my mac. Not sure if there is one for Windows though

@isidorn I'm not sure I understand, are you saying that the search for "blogs" should clear the selection?
Also the terminal find does not search the line that the selection is on, this is a known limitation and captured in another issue.

@Tyriar
cc @isidorn
I just redid my tests taking into account the above.  I noted the current selection with subsequent finds
and what I see matches your description of the other issue/limitation @Tyriar .
If I do a search making sure to look for something on another line things appear to be okay.  my guess is this is the same issue not a different one.

@isidorn
LiceCap is available for Windows and seems to work well Thanks!

@Tyriar yes I am saying that the search for "blogs" should clear the selection and then select "blogs".
After trying a bit more I seem to be always hitting the issue you mentioned - I do not get the search results on the current line. This seems like a big limitation and makes the find widget very unrealiable in terminal imho

@isidorn there are many issues with the implementation, this was something @rebornix and I threw together over 1-2 days that wasn't planned for that iteration. Many of the improvements are listed here https://github.com/Microsoft/vscode/issues/28768

Reopening as I have provided enough details and that is not the issue ehre.
It might be a duplicate but leaving that up to @Tyriar to decide

Let's close this off in favor of https://github.com/Microsoft/vscode/issues/28768, I think it captures everything 😃


Istanbul

Client AppsIstanbul
GitHub Mobile, GitHub CLI, and GitHub Desktop
[Enter feedback here]

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

ID: 1ed50e50-a3c1-1f3b-1ea5-40beec8ab6cd
Version Independent ID: 1ed50e50-a3c1-1f3b-1ea5-40beec8ab6cd
Content: Get support - Microsoft 365 admin
Content Source: microsoft-365/admin/get-help-support.md
Service: o365-administration
GitHub Login: @cmcatee-MSFT
Microsoft Alias: cmcatee

@BassamAlHassan  Can you please tell us what is your feedback Thank you!

@BassamAlHassan We appreciate any feedback that improves the content in the Microsoft docs but we haven't had any response from you so we are going to close this issue.
Please feel free to re-open this issue if you see an improvement is required in the specific area of this documentation. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Allow to detach grammar from rule actions

It would be useful to define different grammar logic to the same language description. In such case grammar would not have initialization and action sections but parsing strategy object would be passed to parse function. Actions for particular rule would be named by convention as rule name.
It would allow to managing single grammar rule to build (for example) evaluating parser and AST building parser easy to maintain.

How would you solve cases like this?
DoubleStringCharacter
  = !('"' / "\\" / LineTerminator) char_:SourceCharacter { return char_;     }
  / "\\" sequence:EscapeSequence                         { return sequence;  }
  / LineContinuation

That is, rules with several choices where each choice is completely different (with different set of labels, etc.).
(The code above is taken from the example JavaScript grammar).

It can be named via convention with number suffix or somehow explicitely named. Please check http://www.romanredz.se/freesoft.htm where it is solved in one way.


chore(CD): tweak Buildkite publish

Regular publish is 3 min faster
Integration version only takes 7 min 💨

Out of the oven 🧑🍳 🍪
https://unpkg.com/browse/<EMAIL_ADDRESS>https://unpkg.com/browse/<EMAIL_ADDRESS>Looks good here.

ecosystem-test for last commit version (3.15.0-integration-tweak-ci.5)
https://github.com/prisma/ecosystem-tests/actions/runs/2302902936
https://github.com/prisma/ecosystem-tests/actions/runs/2302902936


superset db upgrade fails

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

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

table clusters already exists
Superset version
23.3
Expected results
Upgrade superset DB  with

superset db upgrade

after running

pip install superset --upgrade

Actual results

sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) table clusters already exists [SQL: '\nCREATE TABLE clusters (\n\tcreated_on DATETIME NOT NULL, \n\tchanged_on DATETIME NOT NULL, \n\tid INTEGER NOT NULL, \n\tcluster_name VARCHAR(250), \n\tcoordinator_host VARCHAR(255), \n\tcoordinator_port INTEGER, \n\tcoordinator_endpoint VARCHAR(255), \n\tbroker_host VARCHAR(255), \n\tbroker_port INTEGER, \n\tbroker_endpoint VARCHAR(255), \n\tmetadata_last_refreshed DATETIME, \n\tcreated_by_fk INTEGER, \n\tchanged_by_fk INTEGER, \n\tPRIMARY KEY (id), \n\tUNIQUE (cluster_name), \n\tFOREIGN KEY(created_by_fk) REFERENCES ab_user (id), \n\tFOREIGN KEY(changed_by_fk) REFERENCES ab_user (id)\n)\n\n'] (Background on this error at: http://sqlalche.me/e/e3q8)

Steps to reproduce

pip install superset --upgrade
superset db upgrade

Table clusters already exists is a weird issue since clusters is a table that was added really early on in the project. Have you been issuing alembic related commands? Altering the alembic_version table?

I have the same problem.
In my case, the answer is: "superset" is not recognized as a command

@victorgil88 then it's not the same problem, you probably have installed in a virtualenv that you forgot to activate

I am also facing the same issue on windows while running python superset db upgrade.
May i know what this command does and do we need to setup tables or some config files.
INFO  [alembic.runtime.migration] Will assume transactional DDL.
INFO  [alembic.runtime.migration] Running upgrade bddc498dd179 -> 4451805bbaa1, remove double percents
Traceback (most recent call last):
  File "superset", line 15, in <module>
    cli()
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\click\core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\flask\cli.py", line 380, in main
    return AppGroup.main(self, *args, **kwargs)
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\click\core.py", line 697, in main
    rv = self.invoke(ctx)
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\click\core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\click\core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\click\core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\click\core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\click\decorators.py", line 17, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\flask\cli.py", line 257, in decorator
    return __ctx.invoke(f, *args, **kwargs)
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\click\core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\flask_migrate\cli.py", line 134, in upgrade
    _upgrade(directory, revision, sql, tag, x_arg)
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\flask_migrate\__init__.py", line 95, in wrapped
    f(*args, **kwargs)
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\flask_migrate\__init__.py", line 280, in upgrade
    command.upgrade(config, revision, sql=sql, tag=tag)
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\alembic\command.py", line 276, in upgrade
    script.run_env()
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\alembic\script\base.py", line 475, in run_env
    util.load_python_file(self.dir, "env.py")
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\alembic\util\pyfiles.py", line 90, in load_python_file
    module = load_module_py(module_id, path)
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\alembic\util\compat.py", line 156, in load_module_py
    spec.loader.exec_module(module)
  File "<frozen importlib._bootstrap_external>", line 728, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\superset/migrations\env.py", line 100, in <module>
    run_migrations_online()
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\superset/migrations\env.py", line 93, in run_migrations_online
    context.run_migrations()
  File "<string>", line 8, in run_migrations
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\alembic\runtime\environment.py", line 839, in run_migrations
    self.get_context().run_migrations(**kw)
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\alembic\runtime\migration.py", line 361, in run_migrations
    step.migration_fn(**kw)
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\superset\migrations\versions\4451805bbaa1_remove_double_percents.py", line 82, in upgrade
    replace('%%', '%')
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\superset\migrations\versions\4451805bbaa1_remove_double_percents.py", line 53, in replace
    .join(Table)
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\sqlalchemy\orm\query.py", line 2234, in join
    from_joinpoint=from_joinpoint,
  File "<string>", line 2, in _join
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\sqlalchemy\orm\base.py", line 220, in generate
    fn(self, *args[1:], **kw)
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\sqlalchemy\orm\query.py", line 2413, in _join
    left, right, onclause, prop, create_aliases, outerjoin, full
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\sqlalchemy\orm\query.py", line 2436, in _join_left_to_right
    ) = self._join_determine_implicit_left_side(left, right, onclause)
  File "H:\POC\APACHE_SUPERSET\venv\lib\site-packages\sqlalchemy\orm\query.py", line 2567, in _join_determine_implicit_left_side
    "Can't determine which FROM clause to join "
sqlalchemy.exc.InvalidRequestError: Can't determine which FROM clause to join from, there are multiple FROMS which can join to this entity. Try adding an explicit ON clause to help resolve the ambiguity.

(venv) (base) H:\POC\APACHE_SUPERSET\venv\Scripts>```

@prabhatmishra33 I encountered the same issue, downgrading sqlalchemy version to 1.2 fixed this for me. i hope it helps.

Hey @pammi22 - fixed for me as well! Cheers for the heads up

@lilila very late answer to your original question but hope this will be helpful to those who comes later. Your alembic_version table is probably corrupted. In my case what I did was running fabmanager create-db --app superset initially instead of superset db upgrade, which create the tables but not the alembic_version table. To fix it I figured out the latest migration and ran this in my database:
CREATE TABLE alembic_version (version_num character varying(32) PRIMARY KEY);
INSERT INTO alembic_version (version_num) VALUES ('d6ffdf31bdd4');

You'll have to replace the version_num with your own appropriate value of course.

When i run "superset db upgrade" code in Ubuntu 20.4 vm i got this error.Please help me to solve.
Traceback (most recent call last):
File "/home/mach/Desktop/Works/Apache_Superset/venv/bin/superset", line 5, in
from superset.cli import superset
File "/home/mach/Desktop/Works/Apache_Superset/venv/lib/python3.8/site-packages/superset/init.py", line 21, in
from superset.app import create_app
File "/home/mach/Desktop/Works/Apache_Superset/venv/lib/python3.8/site-packages/superset/app.py", line 23, in
from superset.initialization import SupersetAppInitializer
File "/home/mach/Desktop/Works/Apache_Superset/venv/lib/python3.8/site-packages/superset/initialization/init.py", line 26, in
from flask_appbuilder import expose, IndexView
File "/home/mach/Desktop/Works/Apache_Superset/venv/lib/python3.8/site-packages/flask_appbuilder/init.py", line 6, in
from .base import AppBuilder  # noqa: F401
File "/home/mach/Desktop/Works/Apache_Superset/venv/lib/python3.8/site-packages/flask_appbuilder/base.py", line 8, in
from .api.manager import OpenApiManager
File "/home/mach/Desktop/Works/Apache_Superset/venv/lib/python3.8/site-packages/flask_appbuilder/api/manager.py", line 8, in
from flask_appbuilder.baseviews import BaseView
File "/home/mach/Desktop/Works/Apache_Superset/venv/lib/python3.8/site-packages/flask_appbuilder/baseviews.py", line 21, in
from .forms import GeneralModelConverter
File "/home/mach/Desktop/Works/Apache_Superset/venv/lib/python3.8/site-packages/flask_appbuilder/forms.py", line 25, in
from .models.mongoengine.fields import MongoFileField, MongoImageField
File "/home/mach/Desktop/Works/Apache_Superset/venv/lib/python3.8/site-packages/flask_appbuilder/models/mongoengine/fields.py", line 4, in
from ...upload import BS3FileUploadFieldWidget, BS3ImageUploadFieldWidget
File "/home/mach/Desktop/Works/Apache_Superset/venv/lib/python3.8/site-packages/flask_appbuilder/upload.py", line 106, in
class FileUploadField(fields.TextField):
AttributeError: module 'wtforms.fields' has no attribute 'TextField'

I am facing this issue , Kindly provide any suggestion
(supersetdata) piyush@piyushtiwari01:~$ superset db upgrade
Traceback (most recent call last):
File "/home/piyush/supersetdata/bin/superset", line 18, in
from superset.cli import superset
ImportError: cannot import name 'superset' from 'superset.cli' (/home/piyush/supersetdata/lib/python3.8/site-packages/superset/cli/init.py)

I am geting this error when running python superset db upgrade
(venv) c:\superset\venv\Scripts>python superset db upgrade
C:\Python311\python.exe: can't open file 'c:\superset\venv\Scripts\superset': [Errno 2] No such file or directory
Please

AttributeError: module 'sqlparse.keywords' has no attribute 'FLAGS'


Ability to remove the transparentbg_mini.png on the PortableColorPicker.

Please add the ability to remove the background on the Border in the PortableColorPicker:
<Border.Background>

</Border.Background>

Hi, which version do you use. WPF or AvaloniaUI?

Thanks for the reply! I am using WPF and am a bit new to it.

You can try creating custom Template for PortableColorPicker, which essentially would be a copy of built-in template, just without the background.


Fix resolver to be more restrictive for callables

This test covers issue #52
Also tested to pass successfully with #51

Q
A

Is bugfix?
❌

New feature?
❌

Breaks BC?
❌

Fixed issues
#52

I think there should be a point in readme about static factory functions (like 'InterfaceName' => 'myGlobalFunctionFactory') won't be called.

I think there should be a point in readme about static factory functions (like 'InterfaceName' => 'myGlobalFactoryFunction') won't be called. It is a very rare and weird case, but, IMHO, it should be documented.

In this case it is definition and string definition is interpreted as class name.
https://github.com/yiisoft/di/blame/master/README.md#L50
https://github.com/yiisoft/factory/blob/master/src/Definitions/Normalizer.php#L58


Adds lazyRender support

This PR adds support to defer the render of the yield block in the ember-attacher-inner component.
The motivation would be to defer the initialization work of the attached items until the user interacts with it. In cases where the yielded contents are complex, this is preferred over having many items initialize which might or might not ever be used.
Adds a new property called lazyRender to the parent ember-attacher component.
This lazyRender property defaults to false to maintain current expected behavior.
Adds tests for lazyRendering to ensure contents are not rendered until after interacting.
Adds working example to the dummy app.
@kybishop, I am looking for some feedback. Are there any additional tests or cases you want explored?
I believe that once merged you will also need to deploy the dummy app to github pages.
Also, I was not sure if this should be in the readme or not as many of the options are not currently enumerated there.
Closes #74
Closes #64 (in my opinion)

Thanks for the PR @Duder-onomy! I'll have some time to look at in depth tonight and tomorrow.

Thanks for the feedback @kybishop. I think I addressed everything you mentioned and added a second test to ensure the default current behavior when lazyRender is unset.
Looking forward to getting this in. Been enjoying using ember-attacher recently, having ember-popper available on the yielded hash is a clutch move BTW. Saved me once already.

Merged! Thanks a ton @Duder-onomy. I'll have this out with the next release, which will be before EOW

RAWK!


Question: How to share page instance among multiple steps

Problem
For example I have 2 step definitions, first one opens a new tab/page
and second step interacts with the new page, there are further steps which will interact with the new page
When( 'I click on X button under "Some" section', async ( { page1, context } ) => {
	const [ newPage ] = await Promise.all( [
		context.waitForEvent( 'page', { timeout: 120000 } ),
		page1.clickButton()
	] );
} );

When( 'I do some stuff in other page', async ( { page2, } ) => {
	page2.doSomething();
} );

And In my fixtures I have fixtures for both pages, but this creates page instances at the beginning of the test, and when I want to interact elements of Page2, the test gets stuck  with no output at all
type Fixtures = {
	page1: Page1;
	page2: Page2;
};
export const test = base.extend<Fixtures>( {

	page1: async ( { page, world }, use ) => {
		const page1 = new Page1( page, world );
		await use( page1 );
	},
	page2: async ( { page, world }, use ) => {
		const page2 = new Page2( page, world );
		await use( page2 );
	}
} );

There can be different approaches.
In case of sharing page instances between steps you can use context.pages() method to get all pages and filter required one.
If there are fixtures that are initialized with Playwright's default page, you can make these fixtures to be able to hot-switch the page like myFixture.page = newPage. For example, in POM:
class AdminPage {
  page: Page;
  greeting: Locator;

  constructor(page: Page) {
    this.page = page;
    this.greeting = page.locator('#greeting'); // <- you should not store such locators if you want to hot-switch the page.
  }
}

The in the step you can switch fixtures to the new page:
When( 'I click on X button under "Some" section', async ( { page1, context } ) => {
	const [ newPage ] = await Promise.all( [
		context.waitForEvent( 'page', { timeout: 120000 } ),
		page1.clickButton()
	] );
        adminPage.page = newPage;
} );

But here we loose the ability to interact with old page via that fixture.
I think the better way is to use writable fixture as cross step context and put there all shared data, like word in cucumber js:
export const test = base.extend<Fixtures>( {
  world: async ({}, use ) => {
    await use({ newPage: null });
  },

And then in steps:
When( 'I click on X button under "Some" section', async ( { page1, context, world } ) => {
	const [ newPage ] = await Promise.all( [
		context.waitForEvent( 'page', { timeout: 120000 } ),
		page1.clickButton()
	] );
        world.newPage = newPage; // <- store new page for subsequent steps
} );

Thanks,
I did implement a similar solution. I created getter and setter for the page property and use it to hot swap the page instance when needed. The setter also re-initializes the page locators
import { Page } from '@playwright/test';
import { Utils } from '../../fixtures/utils';
import { TemplateLocators } from './templateLocators';
import type { World } from '../../fixtures/world';

export class Template extends Utils {
	// add this page in fixtures.ts and use fixture in step file
	private _page: Page;
	locators: TemplateLocators;

	constructor ( page: Page, world: World ) {
		super( world ); // Pass the world instance to the Utils class
		this._page = page;
		this.locators = new TemplateLocators( page );
	}

	set page ( newPage: Page ) {
		this._page = newPage;
		this.locators = new TemplateLocators( newPage ); // Re-initialize locators with the new page
	}

	get page (): Page {
		return this._page;
	}

	// add methods here

	async exampleMethod () {

	}
}

Within the step I assign the newPage using the setter
When( 'I click on X button under "Some" section', async ( { page1, templatePage, context} ) => {
	const [ newPage ] = await Promise.all( [
		context.waitForEvent( 'page', { timeout: 120000 } ),
		page1.clickButton()
	] );
        templatePage.page= newPage; // <- store new page for subsequent steps
} );

In my next step, I simply use the fixture as it is
When( 'do something in new tab', async ( { templatePage } ) => {
	await templatePage.doSomething();
} );

My fixture remains like this :
templatePage: async ( { page, world }, use ) => {
		const templatePage = new Template( page, world );
		await use( templatePage );
	},

The setter also re-initializes the page locators

That's elegant solution 👍


Allow upstream application to provide its user agent

server PR: https://github.com/zwave-js/zwave-js-server/pull/749

should the lib always add itself to the user agent? While it may be redundant for HA for the most part, I don't see a downside to doing this, only an upside


Python sample for Conversation Transcription

Hello,
Would it be possible to share some examples of Python code to implement Conversation Transcription
https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/conversation-transcription
Thanks in advance,
Oleg

Hi Oleg,
Conversation Transcription is currently not supported in the Python version of the SDK. Support is planned for a future release, and we will include samples once that support is added.