graphql voyager tab

#103 adding voyager tab to graphql faker

hm, something really strange, seems like it is somehow windows related will try once again from macbook little bit later

hm, something really strange, seems like it is somehow windows related will try once again from macbook little bit later

@mac2000 Do you mean broken CI?
It's broken for on master since I can't figure out why it errors only on CI.
So it 100% unrelated to your changes but it would be great if you can figure out why it's broken.

@IvanGoncharov indeed, I have created #113 with related issue, we should downgrade express typings in either case, and somehow deal with new issue with cp, after that will recreate pull request, at moment it does not makes sense because there will be too many not related changes in it


haskellPackages: update stackage and hackage

This Merge
This PR is the regular merge of the haskell-updates branch into master.
This branch is being continually built and tested by hydra at https://hydra.nixos.org/jobset/nixpkgs/haskell-updates. You may be able to find an up-to-date Hydra build report at cdepillabout/nix-haskell-updates-status.
We roughly aim to merge these haskell-updates PRs at least once every two weeks. See the @NixOS/haskell team calendar for who is currently in charge of this branch.
haskellPackages Workflow Summary
Our workflow is currently described in pkgs/development/haskell-modules/HACKING.md.
The short version is this:

We regularly update the Stackage and Hackage pins on haskell-updates (normally at the beginning of a merge window).
The community fixes builds of Haskell packages on that branch.
We aim at at least one merge of haskell-updates into master every two weeks.
We only do the merge if the mergeable job is succeeding on hydra.
If a maintained package is still broken at the time of merge, we will only merge if the maintainer has been pinged 7 days in advance. (If you care about a Haskell package, become a maintainer!)

This is the follow-up to #151578. Come to #haskell:nixos.org if you have any questions.

There are currently a whole bunch of failures on Darwin:
https://github.com/cdepillabout/nix-haskell-updates-status/tree/ed66299bcbcff2122c7abef32b37b50c37685c85
On Matrix, sterni was suggesting that these errors were introduced somewhere between 44f52594d1a0dda1848f227b34a0b088dcb1e11d and c066e2f31649da0324f3e9a2f60cf9834e2261db.
I'd appreciate help from anyone with interest in OSX in tracking this down and fixing it.
Some people that I've seen on past OSX-related issues that might be interested: @domenkozar, @roberth, @jkachmar, @NixOS/darwin-maintainers

Not strictly related, but there are also a few darwin-related Haskell PRs currently open that could use a review or a final push:

https://github.com/NixOS/nixpkgs/pull/149942
https://github.com/NixOS/nixpkgs/pull/152037
https://github.com/NixOS/nixpkgs/pull/152581 (this one is probably fine and just needs to be merged in, although it would of course be welcome if someone could test)
https://github.com/NixOS/nixpkgs/pull/147964

@veprbl posted another likely darwin-related issue at https://github.com/NixOS/nixpkgs/issues/152859.

@veprbl posted another likely darwin-related issue at #152859.

Not another, that is the exact issue.


Dependency and CI maintenance

This PR:

Adds testing of bleeding edge esda to 39-DEV CI
Adds pages to testing (39-DEV CI)
...

I still have no idea why some packages succeed in in CI without explicit reinstall (e.g. spaghetti, spopt), while others need explicit reinstall (e.g., segregation , geosnap )...


fix(tools): crowdin log response error

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

This PR fixes logging of an Crowdin API response error.
According to the Crowdin API, error object consists of code and message:

@naomi-lgbt So, should I just close this PR?

Yep - this can be closed.

Although this wasn't merged, you have highlighted an area that was unnecessary, thank you @alexandear.


peak_region_fragments & blacklist_region_fragments

Hello
I reproduce your research for my study of snATACseq & snRNAseq.
I downloaded all of your metadata in GEO and Synapse database, but I can't find the file included peak_region_fragments variable.
Do you provide cell-meta data including peak_region_fragments ?
Then, please give me the link for that file.
Thank you.

@heomanism Hi, how did you download the Synapse database? It seems to require permission.

Hello, can you provide the fragments file, it needs permissions, it is difficult to apply, thank you!


Setting up Milestones

Issue Description
Milestones are essential in any software project to improve the level of organization. In this context, we need to set some fundamental milestones to set a clearer roadmap.
These include:

Literature Research ( 2 weeks)
Development Phase (5 weeks)
Evaluation Phase(3 weeks)
Documentation Phase(3 weeks)

Step Details
Steps that will be performed:

[x] Create milestones on issues section
[x] Link issues to the milestone

Final Actions
Although the milestones will set general deadlines, changes may happen on the schedule.
Deadline of the Issue
23.59 - 04.03.2023

Please do see the Milestones section.

Looks good, thanks for the effort.

After Meeting 2, the headlines for milestones require change and the Midterm report needs to be added.

Please do check the updated version of the Milestones

LGTM


Controller set hostname

This exposes a configurable hostname type to Docker container through
fleet unit files.
Three hostname types are supported:

default     : standard Docker hostname
application : application hostname (e.g. my-app.v54.web.1)
server      : Core OS hostname

This fixes #2835 and is an alternative to #2428, which got rejected.
It is necessary when using a monitoring solution like New Relic.

Thanks for the contribution! Please ensure your commits follow our style guide. This code will be tested once a Deis maintainer reviews it.

Jenkins, add to whitelist.

I think this is a great compromise for hostnames! My only comment would be that we typically don't include notes like these in the Customizing Deis section, but I honestly can't think of a better location for the information in this PR.
I would also add an example for setting this with deisctl, but otherwise this looks great!

@Blystad Jenkins is failing with a style error in fleet.py. I confirmed that this isn't a problem on master:
➜  controller git:(pr-2837) venv/bin/flake8
./scheduler/fleet.py:101:1: C901 'FleetHTTPClient._create_container' is too complex (14)
➜  controller git:(pr-2837) git checkout master
Switched to branch 'master'
Your branch is up-to-date with 'origin/master'.
➜  controller git:(master) git pull
Already up-to-date.
➜  controller git:(master) venv/bin/flake8
➜  controller git:(master)

Added deisctl example and fixed the complexity by moving the hostname functionality into it's own function, which is better anyways. Now I'll just wait for Jenkins to pass.

It passed, and now I see a "Confirm Merge" button. Should I click that?

Code LGTM! We're shipping Deis v1.2.0 on Tuesday, so this will likely merge shortly thereafter.

this is really well designed. Nice job @Blystad!

@bacongobbler Thanks for the kind words. I've changed the documentation into a definition list now.

code LGTM. :shipit:


Touch trigger isn't fired when checking IO

Hi,
I'm just here for advice this is not really a bug in Nextion X2 library. What I experience is that when I add some additional logic to the loop-method it doesn't trigger my btnStepUp method any more. When I disable the sensor check it does work. I presume it's because the Nextion display already sent the data but the arduino is not listening because it's busy checking IO ports.  Do you have experience on how to handle this?
#include "NextionX2.h"
#include "SoftwareSerial.h"
#include <ezButton.h>

SoftwareSerial SerialNextion(PA10, PA9);
NextionComPort nextion;

#define topPin PB10

NextionComponent btUp(nextion, 0, 8);
ezButton topSensor(topPin);

void setup()
{
  nextion.begin(SerialNextion);

  pinMode(LED_BUILTIN, OUTPUT);

  btUp.touch(btnStepUp);
}

bool initDone = false;
void loop()
{
  nextion.update();

  /// If this is enabled nextion touch trigger doesn't work anymore
  // topSensor.loop();
  // if (dir == CCW && topSensor.getState() == LOW)
  // {
  //   topPosition = stepper.currentPosition();
  //   dir = CW;
  // }

  // I also tried to add another update() at the end of the loop but no difference
  // nextion.update();
}

void btnStepUp()
{
  digitalWrite(LED_BUILTIN, !digitalRead(LED_BUILTIN));
}

Maybe the ezButton blocks the loop(). Use the discussion forum please.


ORC-1450: Stop enforcing override keyword rule

What changes were proposed in this pull request?
This PR aims to recover Clang 10 dev environment by stopping enforcing override keyword.

This is a partial revert of #1420 because we still keep the changed other code.
GitHub Action missed this.

Clang on Ubuntu 20.04 job missed this because it uses Clang 11.0.0.
Clang on MacOS 11 job missed this because it uses AppleClang 13.0.0.

Why are the changes needed?
During Apache ORC 1.9.0 Preparation, I found that this broke ubuntu20_jdk=11_cc=clang docker test due to the unknown warning group errors.

#1532

How was this patch tested?
Pass the CI and do the manual testing with Docker environment.

cc @williamhyun and @wgtmac

Let me merge this in order to proceed Apache ORC 1.9.0.


An existing connection was forcibly closed by the remote host

This keeps happening even if I'm putting 30 second sleeps in between the calls being made.
Here's the code I have
`
from alpha_vantage.timeseries import TimeSeries
ts = TimeSeries(key='KEY', output_format='pandas')
def get_data(ticker):
    price_data, meta_data = ts.get_daily_adjusted(ticker, outputsize='full')
    price_data = price_data.rename(columns=column_translations)

    price_data = price_data.sort_values(['date'], ascending=True)

    return price_data`

ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host
During handling of the above exception, another exception occurred:
urllib3.exceptions.ProtocolError: ('Connection aborted.', ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None))
During handling of the above exception, another exception occurred:
raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: ('Connection aborted.', ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None))

Closing for now. Will reopen if there is further community response. Thanks!


Add interface support for Amazon

speech and OCR

Recognize Multiple Speakers
Amazon Transcribe is able to recognize when the speaker changes and attribute the transcribed text appropriately. This can significantly reduce the amount of work needed to transcribe audio with multiple speakers like telephone calls, meetings, and television shows.

Definitely worth adding the transcribe api


Add lifetime to force markers.

This PR fixes a visualization issue due to the force markers: when a pedestrian disappear at a sink waypoint, the forces arrows would not be deleted.
Before:

After:

Looks good, Thanks


ci-automation/garbage_collect: fix binpkg url

garbage_collect.sh was using 'docker_vernum' where it should have been using 'vernum' (as push_pkgs.sh does).
Also, make sure release directories are removed, not just packages.
This fix should be cherry-picked to 3066 and 3033.

Merged and cherry-picked to 3066 and 3033.


Github action to build and run the test suite

GitHub action to

pull  the changed code,
grab the rule IDs and test data from the git repo established in #797
update the rules cache of the container (container will need to have write permissions/git secrets for API key/ID)
parse the list of rules into a validation command
then run the rules against the datasets,
the output file can then be compared against an expected outcome file using a script, this should create a new readout file that the user will have to review

a second validation where the DATASET_SIZE_THRESHOLD is set to 0 should also be run to ensure dask implementations also run as expected

in thinking on this, we may want 2 containers--one running a pandas implementation and one running a dask implementation (via env DATASET_SIZE_THRESHOLD = 0 ) to ensure both implementations work

per Gerry in slack:  something like this could be useful for displaying report comparison results for testing in CORE: https://github.com/ctrf-io/github-actions-ctrf  when we compare the report generated by the action vs the report we have in the test repo


Route [voyager.posts.edit] not defined

Laravel: v5.8.37
Voyager: v1.3.1
PHP: 7.3
Database: Ver 14.14 Distrib 5.7.26, for osx10.10 (x86_64)

After 1 week work with voyager admin i got this errors. i dont know why this happened!
Route [voyager.posts.edit] not defined. (View: /Applications/MAMP/htdocs/avadis-laravel/vendor/tcg/voyager/resources/views/bread/partials/actions.blade.php) (View: /Applications/MAMP/htdocs/avadis-laravel/vendor/tcg/voyager/resources/views/bread/partials/actions.blade.php)

Since it looks like you already realized it's not a bug but probably something you changed I'm labeling this as questions and as issue template states question should be asked on Voyager Slack chat.


cache is not working in gitea/forgejo

because of URL in cache key
before patch:

after patch:

patch:
--- a/src/action.ts
+++ b/src/action.ts
@@ -73,7 +73,7 @@ export default async (options: Input): Promise<Output> => {
   let revision: string | undefined;
   let cacheHit = false;
   if (cacheEnabled) {
-    const cacheRestored = await restoreCache([bunPath], url);
+    const cacheRestored = await restoreCache([bunPath], 'bun-exe');
     if (cacheRestored) {
       revision = await getRevision(bunPath);
       if (revision) {

--- a/src/cache-save.ts
+++ b/src/cache-save.ts
@@ -6,7 +6,7 @@ import { CacheState } from "./action";
   const state: CacheState = JSON.parse(getState("cache"));
   if (state.cacheEnabled && !state.cacheHit) {
     try {
-      await saveCache([state.bunPath], state.url);
+      await saveCache([state.bunPath], 'bun-exe');
       process.exit(0);
     } catch (error) {
       warning("Failed to save Bun to cache.");

This is not a correct fix because we're using url as the primary key for cache restoring. If we have two actions with different bun versions, the actions would overwrite the same cache and we would get the wrong version in one of the actions.

maybe use hash?


Create a Collection or Partition (create.md) doc update

It does not look good to have two notes back on back.
Move the second note (note about parameters) to under the intro and above the heading.

Can you assign it to me? I am ready to work on this

/assign @harishfalco

@harishfalco I've assigned this issue to you. Feel free to let me know if the instructions are unclear. Thank you for contributing!

Sure @claireyuw . Should I make PR during hacktoberfest ?

Sure @claireyuw . Should I make PR during hacktoberfest ?

You can submit your PR whenever you're ready, but we will wait until October to merge to make sure it counts toward your Hacktoberfest participation.

Can you brief me about the issue? Its unclear

Hi @harishfalco
I've updated the instructions above.

@claireyuw Thanks for the update. Started working on it.

can i work on this issue

Can i work on this issue ?

Is there anyone working on this issue currently! If not, @claireyuw you can assign this issue to me, so I can make a PR regarding the issue!

@claireyuw , Sorry For not being active.I will complete it today

Hey @claireyuw  , I have understood the issue, could you please assign it to me if it hasn't been done yet?
I will work on it as soon as possible.

@tabhay563 @iamartyaa @AnuragYadav365 @ion05
Thank you all for showing initiative, but this issue has been assigned to @harishfalco. Feel free to check out other pending issues


Renumber and reoganize SIMD opcodes

This handles the recent changes to the upstream proposal, which
renumbered and reorganized most of the opcodes, but AFAIK no functional
change was intended.

ping, just wanted to make sure there wasn't anything else you'd like me to do!

Er oops, sorry about that! I'll send a follow-up

Would it be ok to publish this to crates.io?

Done @alexcrichton

Thanks!


Failing unit test & test:core run NOT including .tsx spec files in circleci job

working from 1.296.0
the test:core run fails at src/app/customer/Customer.spec.tsx -- Customer › when view type is "guest" › calls onUnhandledError if initialize was failed. (circleci job log attached)
This appears to be related to the recent addition to an if/guard statement that requires the providerWithCustomCheckout prop to be defined for the initializeCustomer() call. The prop is never passed to the mounted CustomerTest component in unit test so intializeCustomer() is never reached/called with the expected mocked rejection/error throw.
Seems this error was not caught due to circleci config only including .ts files instead of both .ts & .tsx files: circleci tests glob "packages/core/**/*.spec.ts" | circleci tests split --split-by=timings
Unsure if 100% passing unit tests are out of scope and/or if only .ts files being included in circleci job is intended, but figured I raise a flag on this. Please feel free to close if deemed too low of priority/out of scope -- easy to resolve regardless.
Thanks for all the continued hard work on the SDK & checkout-js by everyone!

Hey @mikematrs thanks for reporting this. Have just merged the PR to fix this issue. Sorry for the inconvenience.


Tooltips are displaced from where they should be

Prerequisites

[ ] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
I haven't used Atom for a while, but I started again 8 months ago, and since then atom-ide-ui and linter-ui-default tooltips have always been positioned erroneously.
I haven't tried safe mode, as then the packages are disabled and so I don't have the tooltips.
F.e., here's a screenshot showing a tooltip from the linter-ui-default package far away from the mouse cursor (I am hovering over the red-underlined function log():

The offset appears to be the same for tooltips generated by the atom-ide-ui package, so it lead me to believe they are using the same API, which I'm guessing is part of Atom's built-in overlay API.
Steps to Reproduce
Here's the version of everything I have installed, then it happens with the tooltips 100% of the time:

debug info with package info
{
  "atom": "1.32.0",
  "platform": "darwin",
  "release": "18.0.0",
  "vmpVersion": "1.35.0",
  "vmpConfig": {},
  "activeCommunityPackages": [
    "language-javascript-jsx: 0.3.7",
    "atom-material-syntax: 1.0.8",
    "aligner-javascript: 1.3.0",
    "atom-domterm: 0.6.0",
    "atom-vim-like-tab: 1.5.2",
    "autocomplete-modules: 2.2.2",
    "autocomplete-paths: 2.12.2",
    "better-git-blame: 0.4.7",
    "busy-signal: 1.4.3",
    "docblockr: 0.13.7",
    "emmet: 2.4.3",
    "ex-mode-sort: 1.0.0",
    "file-icons: 2.1.21",
    "file-watcher: 1.2.6",
    "git-plus: 8.1.0",
    "hey-pane: 1.1.0",
    "highlight-line: 0.12.0",
    "highlight-selected: 0.13.1",
    "hyperclick: 0.1.5",
    "imdone-atom: 2.4.29",
    "indent-guide-improved: 1.4.13",
    "intentions: 1.1.5",
    "keystroke: 0.4.0",
    "linter: 2.2.0",
    "linter-eslint: 8.4.1",
    "linter-ui-default: 1.7.1",
    "linter-ui-plus: 0.3.2",
    "minimap: 4.29.8",
    "minimap-bookmarks: 0.4.2",
    "minimap-git-diff: 4.3.1",
    "minimap-highlight-selected: 4.6.1",
    "minimap-linter: 2.2.1",
    "minimap-pigments: 0.2.2",
    "minimap-quick-highlight: 1.0.1",
    "pigments: 0.40.2",
    "prettier-atom: 0.55.2",
    "project-plus: 1.0.0",
    "quick-highlight: 0.13.0",
    "split-diff: 1.4.0",
    "teletype: 0.13.2",
    "todo-show: 2.3.0",
    "trailing-spaces: 0.4.0",
    "tree-view-git-status: 1.5.0",
    "vim-mode-plus: 1.35.0",
    "vim-mode-plus-keymaps-for-surround: 0.2.1",
    "editorconfig: 2.2.2",
    "language-jenkinsfile: 0.1.1",
    "language-pug: 0.0.22",
    "language-vue: 0.23.1",
    "atom-typescript: 12.6.3",
    "ex-mode: 0.18.0"
  ]
}

Expected behavior:
Tooltips should be next to the cursor, Or next to the part of the line (below) where the note is regarding.
Actual behavior:
The tooltips are displaced.
It gets worse depending on pane split configuration (the offset varies depending on orientation and size of pane splits.
Reproduces how often:
100% of the time.
Versions
See above
Additional Information
What else can I do to help find the problem?

For fun!

Thanks for the report!

Aha! It appears that my custom stylesheet is the culprit, and the styling is causing the overlay system to calculate incorrect positions.

Ahhh ok, thanks for tracking this down :+1:

From this, it seems that the overlay needs to calculate the position of the overlays taking into consideration CSS transforms. Granted, not many people have this type of stuff in their style sheet! 😄

😄 - since the issue is related to custom styles you had set we'll go ahead and close this but we'll share your note with the team as feedback to consider.

For fun!

That's pretty neat 😄


fix: kurtosis blob preconfirmation flow

sidecar: fixed transaction cost calculation
relay & mev-boost: fixed production of merkle leaves for inclusion proofs: now decoded without blob sidecars
builder: investigation into failing inclusion proof test with an array of 3+ constraints

Summary by CodeRabbit

New Features

Enhanced transaction cost calculation to accommodate EIP-4844 transactions.
Improved logging for fee validation and execution state updates, enhancing observability.

Bug Fixes

Improved error handling during transaction processing in inclusion proof verification.

Tests

Expanded test coverage for Merkle multi-proof generation, allowing for dynamic transaction combinations.

Documentation

Expanded documentation for the transaction cost calculation method for clearer developer guidance.

merging to move forward with testing blobs. adding an issue to fix the multiproofs separately.


S3 fails to work when running under AWS ECS Fargate

I am running the registry container under Amazon ECS Fargate. In a basic configuration (using file or memory storage) it works, but when I configure the storage to use S3 I get an error that no credentials were found in the chain. I am deploying it with a TaskRole that gives the needed access to the S3 Bucket.
I am running registry:latest docker image. I also tried using registry:2 and registry:2.7.1.
The Docker version is whatever version Amazon is using with Fargate.
After some digging I discovered the problem. The S3 storage driver code creates its own list of credential providers for AWS SDK which doesn't contain the checks needed for the ECS TaskRole to be used. These checks are in the AWS SDK default settings but the S3 storage driver doesn't include them.
What AWS SDK Does
The AWS SDK for Go (aws-sdk-go) default credential setup has special code to check for the environment variable (AWS_CONTAINER_CREDENTIALS_RELATIVE_URI) used by ECS to allow the TaskRole to be used.  This code is in aws/defaults/defaults.go. The RemoteCredProvider function checks for the special environment variables and returns the correct provider. It defaults to the regular EC2 Role Provider if the special environment variables are not set.
// RemoteCredProvider returns a credentials provider for the default remote
// endpoints such as EC2 or ECS Roles.
func RemoteCredProvider(cfg aws.Config, handlers request.Handlers) credentials.Provider {
    if u := os.Getenv(httpProviderEnvVar); len(u) > 0 {
        return localHTTPCredProvider(cfg, handlers, u)
    }

    if uri := os.Getenv(ecsCredsProviderEnvVar); len(uri) > 0 {
        u := fmt.Sprintf("http://<IP_ADDRESS>%s", uri)
        return httpCredProvider(cfg, handlers, u)
    }

    return ec2RoleProvider(cfg, handlers)
}

S3 Storage Driver Problem
The S3 storage driver creates its own credentials chain for AWS and misses the checks for the environment variables. I guess it does this to add a new entry to the specified access key/secret key in the configuration. The code in registry/storage/driver/s3-aws (in the New function) looks like this:
creds := credentials.NewChainCredentials([]credentials.Provider{
		&credentials.StaticProvider{
			Value: credentials.Value{
				AccessKeyID:     params.AccessKey,
				SecretAccessKey: params.SecretKey,
				SessionToken:    params.SessionToken,
			},
		},
		&credentials.EnvProvider{},
		&credentials.SharedCredentialsProvider{},
		&ec2rolecreds.EC2RoleProvider{Client: ec2metadata.New(sess)},
	})

awsConfig.WithCredentials(creds)

This falls back to the default EC2 role provider but does not have the extra checks for the ECS environment variables that allows the TaskRole to be used.
My Workaround
My workaround was to add an check around setting up the AWS credentials. In the New function of the S3 storage driver file s3.go - if the access key in the configuration is empty then skip the custom credential setup and let the AWS SDK use its default credential configuration.
       if params.AccessKey != "" {
                creds := credentials.NewChainCredentials([]credentials.Provider{
                        &credentials.StaticProvider{
                                Value: credentials.Value{
                                        AccessKeyID:     params.AccessKey,
                                        SecretAccessKey: params.SecretKey,
                                        SessionToken:    params.SessionToken,
                                },
                        },
                        &credentials.EnvProvider{},
                        &credentials.SharedCredentialsProvider{},
                        &ec2rolecreds.EC2RoleProvider{Client: ec2metadata.New(sess)},
                })
                awsConfig.WithCredentials(creds)
        }

When I built and deployed the Docker image the S3 driver worked as expected.
Resolution
The workaround does fix the problem when not using a specific access/secret.
As a quick fix it works but it may be better long term to get the default config (maybe by called aws.defaults.Get() instead of aws.NewConfig(). The aws.defaults.Get() has a config that includes the default cerdentials chain. The extra static provider could be inserted into the chain if the access/secret key is configured.
For now we are using our custom build of the registry.

@daddyman I was having the same issue and put together a fix for it, when I thought to check for any existing reports I found your ticket so have submitted a PR against this, I hope you don't mind?  The solution is a little different from yours but seems to work.
I've tested this in EC2 and ECS but haven't checked the other auth scenarios (static, env and shared config).

I've run into the same issue, works fine on local using my AWS credentials but panics when deployed to the AWS Fargate environment. I'm going to try doing a custom build with PR 2973.


UserWarning: nn.Upsample is deprecated.

Hi~
I found an error while using InfoGAN. The error is as follows. Hope to repair.
/usr/local/lib/python3.7/site-packages/torch/nn/modules/upsampling.py:129: UserWarning: nn.Upsample is deprecated. Use nn.functional.interpolate instead.
  warnings.warn("nn.{} is deprecated. Use nn.functional.interpolate instead.".format(self.name))
/usr/local/lib/python3.7/site-packages/torch/nn/modules/container.py:92: UserWarning: Implicit dimension choice for softmax has been deprecated. Change the call to include dim=X as an argument.
  input = module(input)

Thank you for writing the code, gave me a lot of inspiration!

This actually is not an error, it's just a warning. You don't need to worry about it.
If you want, you can just change the torch.nn.Upsample() layer  for  the function torch.nn.functional.interpolate() and choose the same interpolation method to have same behavior, e.g., change torch.nn.Upsample(mode='nearest', scale_factor=2)(x_in) to torch.nn.functional.interpolate(x_in, mode='nearest', scale_factor=2).
The problem is that nn.function.interpolate does not have bicubic interpolation implementation. In this case I transform the tensor back to numpy array and use any existing implemantion for it (like the PIL.Image.resize), then transform it back to Tensor (not sure if it is intelligent, but does the trick). There is a nice dicussion about this change here.

Just like @alsombra said it's just a warning, so you can run the implementations without problems despite the message you got. That said, I will probably write a wrapper for torch.nn.functional.interpolate soon which will replace the nn.Upsample layers.

Haven't had time to add this yet. Have to decide if I want to add this custom layer to each implementation or if I should add a common python file with custom layers. If you want to get rid of this message you can use this Upsample module.
class Upsample(nn.Module):
    """ nn.Upsample is deprecated """

    def __init__(self, scale_factor, mode="nearest"):
        super(Upsample, self).__init__()
        self.scale_factor = scale_factor
        self.mode = mode

    def forward(self, x):
        x = F.interpolate(x, scale_factor=self.scale_factor, mode=self.mode)
        return x

Thank you so much  l got it.


[ENH] Create a Send-BuildNotification cmdlet

This should be reasonably build system agnostic and work with our current CI/CD pipelines TeamCity, GitHub Actions and CircleCI + local builds.
It should call Send-SlackNotification with the default params we use for builds.
It would be helpful if #16 was resolved first.

If we do this we should tweak the build script snippet to insert one of these at the end by default.


can not decompress

For large models such as llama, the probabilities generated by inputting sequences one by one and inputting all sequences at once are inconsistent, which will lead to decoding problems. How to solve this problem? In your code, if I do not use use_slow_lossless_compression, the probabilities when encoding and decoding will be inconsistent.

Indeed, using use_slow_lossless_compression is the way to deal with this numerical issue.


Add .rustfmt.toml

Before starting work on https://github.com/ad4mx/spinoff/issues/15, I saw that there was inconsistent formatting applied to the source code, so I added a .rustfmt.toml file and ran cargo fmt. This PR only contains automatically fixed formatting changes.
This was to make sure that any future PRs will contain less formatting "noise" and that all contributors get the same output when we run "cargo fmt"

I'll remove .rustfmt! However, rustfmt's defaults are still maximum character width = 80, so the function declarations (where some still exceed 80 characters) will still be realigned vertically. We can set the maximum character width to 100 (from the default 80) if you prefer.
What do you think?

Yeah, I think that could work


Fix code scanning alert - Prohibits the use of iterator property due to compatibility issues

Tracking issue for:

[ ] https://github.com/sebastianjn/KellyWorld/security/code-scanning/173

Ignorar!


Fix issue

[ ] Do only one thing
[ ] Non breaking API changes
[ ] Tested

What did this pull request do?

User Case Description

Can you add some tests?


Animation Tree Transition is absolutely broken

Tested versions
Reproduced on 4.4 dev 5 and 4.3 Stable
System information
Godot v4.4.dev5 - Windows 10.0.22631 - Single-window, 1 monitor - Vulkan (Forward+) - dedicated AMD Radeon RX 6600 (Advanced Micro Devices, Inc.; 32.0.12019.1028) - Intel(R) Core(TM) i3-10105F CPU @ 3.70GHz (8 threads)
Issue description
Animation pace is inconsistent, and at times just goes to hell.
The first video showcases the animation pace inconsistency
https://github.com/user-attachments/assets/8c5b12cc-af2c-4c51-9e24-d221b0fe3df9
The second video I've also seen happen in the MRP at times, but only have a video of it happening in my game dummy scene, Observe Walk Calm in animation tree not completely bouncing going between 0 and 1, also at the start it may feel stuttery, but that's because it's a 30 fps video of a 60hz setup, and it's actually not visible but the animation was very aggressively switching back and forth from frame to frame
https://github.com/user-attachments/assets/78787d64-ea68-4e53-85c5-ed574fc494f4
Steps to reproduce
Inconsistent behavior, with no good steps to reproduce found yet beyond it seeming like it has something to do with the Transition node in Animation Tree. Animation Player animation runs smoothly consistently. the MRP at times may or may not produce the broken results.
Minimal reproduction project (MRP)
Bug.zip

Since there seems to be a mix-up in the issue, let's separate them:

If there is more than one AnimationTree, each one is misaligned

This is not a bug. It is the intended behavior because each AnimationTree is getting a different delta. If you want to process the same delta correctly, set CallbackModeProcess to Physics and this problem will not occur

The AnimationTree progression is broken “when opening the AnimationTreeEditor”

This is definitely a bug. However, it is a bug only in the editor. Perhaps, as with A, there is a confusion of pointers for what is passed to the editor

So the former is not a bug, only the latter needs to be fixed.

The problem does occur with callback on Physics on all animationtrees
https://github.com/user-attachments/assets/c3dade1e-9537-44e4-84db-6293c7d60875

The following MRPs confirm that the problem of the 2 occurs outside the editor.
at-bug.zip
In conclusion, simply the backward flag is not parameterized, which is why each AnimationTree had the same reference. Therefore, this problem should be specific to ping-pong.


Update README.md

Added Favorite Contacts to the list of apps using FLAnimatedImage. Thanks!

Not going to merge this for now since it's an outdated PR. Feel free to create a new PR if you still want to do it.


Give options to swipeHorizontally from right to left

This will be very helpful for us if you give an option to swipe pdf from right to left.
I believe that you can easily implement this feature if you show pdf images with reverse order
ex:
for ( int i = 610 ;  i >= 1 ;  i-- )
plz reply...

I need this options too.


[bug]: Interop: INVALID_ONION_HMAC

Background
There is an interop issue with Core lightning that causes INVALID_ONION_HMAC errors. It consistently reproduces with the following setup:
LND sender -> LND routing node -> CLN routing node -> CLN recipient
It does NOT reproduce with

4 LND nodes
4 CLN nodes
1 LND node and 1 CLN node
LND sender, LND routing node, CLN recipient
CLN sender, LND routing node, CLN routing node, CLN recipient

Your environment

version of lnd: 0.17.5
Seen in production on ubuntu, also locally on Mac M3
bitcoind 0.23
cln v24.02.2

Steps to reproduce
Create 4 lightning nodes with channels between them:

LND sender
LND routing node
CLN routing node
CLN recipient

Send a payment from the sender to the recipient over the two routing nodes.
Expected behaviour
The payment should succeed
Actual behaviour
The payment fails with INVALID_ONION_HMAC from index 1.
testing setup

Get binaries for lnd 0.17.5, cln 24.02.2, bitcoind and bitcoin-cli
Checkout the invalid_onion_hmac branch of https://github.com/breez/lspd
Review the test https://github.com/breez/lspd/blob/invalid_onion_hmac/itest/invalid_onion_hmac.go
Run the test with go test -timeout 5m -v ./itest -test.run TestInvalidOnionHmac --bitcoindexec /path/to/bitcoind --lightningdexec /path/to/lightningd --lndexec /path/to/lnd --bitcoincliexec /path/to/bitcoin-cli --testdir /path/to/temporary/testdir --preservelogs
Note that the test does not run any lspd related infrastructure, it's pure lightning nodes

logs
lnd-lnd-sender.log
lnd-lnd-router.log
lightningd-cln-router.log
lightningd-cln-recipient.log
CLN issue
https://github.com/ElementsProject/lightning/issues/7347

Are you able to hit this outside of your testing infrastructure? Ran a quick test this morning with LND -- LND -- CLN -(private)- CLN on the specified versions and I'm unable to reproduce this failure.

Hi all, we're the ones getting the bug in production in case I can be of any help. This issue is preventing affected nodes running on Greenlight infrastructure to receive payments from Alby or Blink (only ones tested so far).

I'm just wondering what the difference is between the test setup and the quick test I ran manually

I agree! The logs from a test are supplied at the bottom of the issue description with trace level from lnd. Maybe differences can be seen in there. If there's any other information that can be helpful, or running tests with specific settings, let me know.

have reproduced 👍

Need a build with more data?  I can have it spit out all the gory details to stderr....
We will give this error if they try to send a legacy onion, but nobody does that any more. Surely?

Indeed, LND log 2915:
   Payload: ([]uint8) (len=33 cap=64) {
    00000000  00 26 28 0f 74 eb c5 87  c8 00 00 00 00 00 00 27  |.&(.t..........'|
    00000010  10 00 00 00 88 00 00 00  00 00 00 00 00 00 00 00  |................|
    00000020  00                                                |.|
``

See that 00 at the front of the payload?  That's legacy, which we removed support for in 23.05 :grimacing:

Weird, we'll only try to send a legacy onion if either the hop hints sent over don't have the proper feature bits set, or we never got a node announcement from the destination node (so we don't know their feature bit set).

Ah, I think what's happening is that if CLN isn't setting the bit at all (we still set it, but have it marked as required), then we'd assume that the peer is super old and doesn't understand the new onion format.

@Roasbeef Can you elaborate which feature bits specifically?

Apparently (according to @ellemouton) the node hasn't seen the CLN node announcement, and is assuming the worst.  FWIW we stopped generating them in our 2022-04 release, six months before we stopped accepting them.
You should probably just rip out the code which generates the old-style legacy onions altogether.  For us it was a nice simplification...

@JssDWt the TLV onion feature bit.
What I think is happening here is CLN not setting the bit at all. Newer lnd clients (0.18 and forward) will start to set the bit to required. Eventually we'll also just stop setting it all together, but we can't do that yet, as older clients (pre 0.18) will use the feature bit to decide if they can do things like MPP or not.

CLN are setting the bit (it is set in the invoice) but the main issue is that the LND nodes in the setup are not seeing the CLN node announcement. They do get the channel announcement though & so know of the node but then assume a zero length feature bit vector. So that is the main issue.
The second issue (which I realised will only actually matter in the case where an invoice has chained hop hints) is that we (LND) assume that hop hints have zero length feature bit vectors (ie, we dont see them as having the TLV bit set and so we would use legacy encoding for these hops).


Choropleth Example

I'm trying to dynamically fill the polygons of a choropleth, but I'm having trouble figuring out how to pass the fill color through.
Is there an example available?

Weird. I swear I looked for a while.


Is the work being done to handle channel messages/mentions in Telegram?

Rasa Core version: 0.8.6
Python version: 3.6
Operating system (windows, osx, ...): WIndows
Issue:
Current version doesn't handle messages sent from Telegram channels or through mentions. Is it under work?
If not then I have made changes in telegram.py to handle this and I'll create a PR.
Content of domain file (if used & relevant):

What do you mean through telegram channels? There's a telegram connector? Or do you mean group chats?

There are channels and groups in telegram where you need to type @bot or /bot if you want to talk to the bot. The current rasa_core/channels/telegram.py does not handle this.

This is supported: https://github.com/RasaHQ/rasa_core/blob/master/rasa_core/channels/telegram.py#L128

Yeah that line is for user message, not for message from a user through a channel/group where the bot is mentioned as /bot <message>. In that case the request is different.

Have you tried using it in a channel/group? Because we've built a bot and use it in a group, which works completely fine.

An important thing to do is to set the group settings of the bot to listen on mention only, otherwise it will parse every single message in that group

If we send message to bot from a channel, the text is present inside channel_post.text key of the request json and not in message.

Ok that's interesting. Is it possible that this is a recent change? In any case, if you've already written the code, we'd be happy to accept a pull request.

I don't know about the change but this is only in case of a channel message. Also I didn't find any setting related to bot only listening to mentions for the channel. It is there for groups.

I'm still not understanding what the difference is between a group and channel... To me those are one and the same. In any case, the url you linked says that bots can have private mode enabled, which is what i'm talking about.

@swapkh91 can we close this?


Data Set Mauro Preview: accessible frame view

In V3 of the dictionary the data sets have frames, e.g. https://v3.datadictionary.nhs.uk/data_dictionary/messages/clinical_data_sets/data_sets/diagnostic_imaging_data_set_fr.asp?shownav=1
In V3+, there are no frames, e.g. https://www.datadictionary.nhs.uk/data_sets/clinical_data_sets/diagnostic_imaging_data_set.html#dataset_diagnostic_imaging_data_set
The frames were removed from V3+ to meet accessibility requirements.
During development of a new data set (using a preview in V3 style), we usually have a copy of an excel spreadsheet on one screen and the dictionary on another screen. This means we can check the order of items and item descriptions at the same time.
To do the same thing in V3+ we would have to:

access the item and then go back to go to the data set or
open the item up in a new frame / window and then return to the data set.

This will increase development time.
Is there a way to replicate frames (or something similar) in the Mauro preview that would meet the accessible criteria.
If this could be done in the preview initially, we may then want to think about doing something similar on the website but that can be considered later.

This needs further investigation to see if it is possible but is not essential for go live.


Remove unnecessary allocations in HRN lookup

Remove dozens of needless mallocs and also remove the unneeded static
global object, removing the auto-generated memory barrier.
Since all the data we have is static, use a POD. Also, with only 4
items, a linear search is superior.
Signed-off-by: Harald Fernengel<EMAIL_ADDRESS>

Abandoning. It's a micro-optimization that's not worth pursuing.


chore(dropdown): switch menu to directive

A <ng-content> template makes sense if you have something else on the template. If you remove the template entirely, the inner content will appear nonetheless.
Not sure about the chore thing, but I think that the first changelog won't be autogenerated (lot of experimentation that would result in a weird changelog.
Plunker

Not sure about the chore thing,

refactor is the way to go in cases like this

Definitely. Forgot about it.
El 7/11/2015 19:22, "Pawel Kozlowski"<EMAIL_ADDRESS>escribió:

Not sure about the chore thing,
refactor is the way to go in cases like this
—
Reply to this email directly or view it on GitHub
https://github.com/ng-bootstrap/core/pull/81#issuecomment-154733985.

LGTM


Kadane's Algorithm

Overview

Write code for Kadane's Algorithm in C++.
Add that code into a directory named "Arrays", if the directory doesn't exist, create one and add the code file.

Please take care of these things while creating the pull request.

The code file was added to the correct directory.
Code quality looks good.
The programming language used is the same as mentioned in the issue.

Hey I can work on this  issue

Hey,Is it still open . Can i Work on it?

is it open ?? I want to work on it please tell me

Hey @kataranandini & @muskaanrajput14,
This issue has already been assigned, PTAL on other issues.


Allow increasing recursion limit

I'm trying to deserialize very large CBOR files, and end up hitting the recursion limit of serde_cbor. Would it be possible to provide a way to increase or disable the recursion limit?
The related discussion in serde_json can be found here: https://github.com/serde-rs/json/issues/334.
The approach they took was to add a Deserializer::disable_recursion_limit function.

The API seems reasonable.

Parse arbitrarily deep JSON structures without any consideration for overflowing the stack.

Should this be an unsafe function as it may cause stack overflows and by extension denial of service or worse?

Marking it as unsafe may be a bit much as it doesn't violate any of Rust's safety guarantees. I like the approach serde_json took to gate this function, which was to require the library to be built with features = ["unbounded_depth"] to make sure the user knows what they're getting into :smiley:
I'm not morally opposed to marking it unsafe though, if others prefer that.

Another option could be to add a Deserializer::set_max_depth function as the Serde MessagePack library does.

I like the approach serde_json took to gate this function, which was to require the library to be built with features = ["unbounded_depth"] to make sure the user knows what they're getting into smiley

I think this crate already has to many features which cause problems because every new feature doubles the amount of build configurations. Sometimes the crate breaks if you have a specific combination of features and std/no-std enabled.

Another option could be to add a Deserializer::set_max_depth function as the Serde MessagePack library does.

Is this better than a simple opt-out from depth checking? Or asked another way: Are there people who know that their messages are at maximum nested 323 levels deep and want to set serde-cbor to this value?

I think this crate already has to many features which cause problems because every new feature doubles the amount of build configurations. Sometimes the crate breaks if you have a specific combination of features and std/no-std enabled.

Yeah, that's totally fair, I didn't think of this.

Is this better than a simple opt-out from depth checking? Or asked another way: Are there people who know that their messages are at maximum nested 323 levels deep and want to set serde-cbor to this value?

My particular use case is that I have a server deserializing cbor messages generated by untrusted clients. For my specific application, the cbor messages generates are quite large by their nature.
Setting the max recursion limit would be helpful because it would allow me to accept large cbor messages within reason, but still have a cap in the case of user abuse.
So I guess to directly answer the question, I'm not sure if there are people who know exactly what depth their messages are, but there may be people who simply want to change the default for their use case.

I'd merge a PR if you send one.


Details about metricx

Hi, would you like to share your code used to evaluate? I am confused about the implementation of F-measure and MAE, should I threshold probability map with 0.5 or vary the thresholds?

Lease refer to our evaluation tool: https://github.com/xuebinqin/Binary-Segmentation-Evaluation-Tool

On Mar 4, 2021, at 4:59 AM, 朱洁茹<EMAIL_ADDRESS>wrote:
Hi, would you like to share your code used to evaluate? I am confused about the implementation of F-measure and MAE, should I threshold probability map with 0.5 or vary the thresholds?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/xuebinqin/U-2-Net/issues/172, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADSGORNMC22CUNEL6ZOL7HLTB5YY7ANCNFSM4YTDTHMQ.

Thanks a lot


Create showcase section

Create a new navigatable section of the site where we showcase community plugins, applications and more built using Aurelia. It will work similarly to the blog section with contributions managed through pull requests to the repository. It would allow people to get exposure for their apps, GH repos and other creations, as well as highlight the community aspect of Aurelia.

Implemented at: https://aurelia.io/showcase/


Avoid serializing CleanConfig object inside stopWhen parameter

Without this change whole CleanConfig object gets serialized because of $this usage.
Here is an example of how CleanConfig object looked before this change. Notice serialization of itself inside stopWhen parameter.

Here is the object after change.

Now that I think about it, shouldn't it be just?
return $cleanConfig->rowsDeletedInThisPass < $cleanConfig->deleteChunkSize;

That could indeed work. Can you make the change? Also make sure that all tests pass.

@freekmurze I have updated the code.
Regarding tests, not sure why but in newer versions of laravel it tried to use default mysql connection when dispatching a batch. Managed to fix that by specifying env values in phpunit config.

Thanks!

My pleasure, thank you for this package!


Fix #10991: Add improved error messages for comparison with narrowed types

Fixes #10991
I think the error reporting I've implemented could be improved but it is probably worth discussing--just getting the ball rolling for now.
Ideas to consider.

Should the pre and post narrow types be presented (that is what it does now).
Should the error node be the operator or the narrowed reference (currently it is the same node as the parent error).

@RyanCavanaugh
Example:
const enum Keys {
    Tab = 10,
    Shift = 13
}

function enumType() {
    let key: Keys;

    if (key === Keys.Tab) {
        return;
    }

    if (key === Keys.Tab || key === Keys.Shift) {
    // Operator '===' cannot be applied to types 'Keys.Shift' and 'Keys.Tab'. [2365]
    // Earlier code in this block narrowed type 'Keys' to 'Keys.Shift' making this operation invalid. [2725]
        console.log('Bug');
    }
}

Failed CI is due to timeout on largeControlFlowGraph.ts. Can this happen coincidentally?


Adding iterable dataset for training

Addressing #11

[ ] Build tests for glitch_frac > 0
[ ] Build tests for waveform_frac > 0
[ ] Sample start_indices from first half of arrays to always include trigger
[ ] Build CI for running tests on PR

Moving from draft to full PR so that we can start review comments on individual lines. Injection code still needs to be completed and needs tests (though not sure what those will look like), but otherwise should be most of the way there

@wbenoit26 I think everything should be in here by now, with tests for everything as well. The waveform sampling tests could be a bit more complete, but it's worth having a discussion at some point about what functionality we want to trust that bbhnet.injection has tested for us, and which we want to verify in downstream libs. In either case, I've noted areas of improvement with TODO's and can open these up as good-first-issues.


Extend test framework to support running without coordinator

We need to extend the framework we use for ITs StargateTestResource / DseTestResource to provide an option to run tests without a coordinator node.
This is related to #600 but slightly different. Having this option could be useful for DSE 7 integration.
May also depend on #644 for an alternate authentication method without coordinator in the loop.

While doing this, it may make sense to collapse StargateTestResource / DseTestResource into a single class since StargateTestResource is never used on its own.


Unit tests

Use XUnit via NuGet. Also get code coverage at the same time with report generation.

Started this at V1.0.14, just some tests on EasyScript. Will add code coverage next, then see which key tests still need to be added.


Download with headless chrome

Im not able to download when using chrome headless mode . I saw some solutions using selenium for python with add_experimental_options, but i couldnt find this method in seleniumBasic. Any ideas? Thank you!

Hi jhgcc1,
You can use a couple methods for this. You can use phatomJS, which is headless by default or you can do this for chrome,
dim driver as new chromedriver
driver.AddArgument "--headless"
driver.get "https://google.com"
Hope that helps. I have a lecture about AddArguments on my site if you're interested in video guides.
Thanks
Dan Strong


position='current' file split open will change the current window buffer also

https://user-images.githubusercontent.com/18459807/179344877-ffbfacf1-728b-43ba-a04b-131ed1823a0b.mp4
Steps:

Open 'a.lua' file in neovim
Open neo-tree in current mode
Open 'b.lua' file in split window
Jump back to the first window
Run NeoTreeFocusToggle command to close the tree

Expected:
First window should show content of 'a.lua'
Actual:
First window shows content of 'b.lua'

Sorry to let this set for so long, but I am going to close it now because the scenarios you are describing are not the intended usage of the position=current feature, they are in fact the intended for the sidebar positions specifically. The beauty of the current position is that its usage is simple and obvious and does not need to be over complicated by the ability to open files in another window.
Please read this: http://vimcasts.org/blog/2013/01/oil-and-vinegar-split-windows-and-project-drawer/
Also, please do not use any of the deprecated NeoTree* commands, they will be removed soon. You should be using the singular Neotree command which takes arguments for all of it's variations.


Fixed ambigious IllegalArgumentException

This change is

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@9cc71e2). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master     #149   +/-   ##
=========================================
  Coverage          ?   84.22%
  Complexity        ?     1011
=========================================
  Files             ?       92
  Lines             ?     2884
  Branches          ?      125
=========================================
  Hits              ?     2429
  Misses            ?      373
  Partials          ?       82

Impacted Files
Coverage Δ
Complexity Δ

...rc/main/java/org/oscm/rest/event/EventBackend.java
100% <ø> (ø)
4 <0> (?)

...common/errorhandling/RestErrorResponseFactory.java
92.85% <100%> (ø)
3 <0> (?)


How to handle multiple origin proxy for one request in zuul2?

For example, /api/combine needs to aggregate date from origin A, B, C. Is there any appropriate way to send these origin proxy in current eventloop, instead of creating seperated thread pool.

Unfortunately no. Zuul is intended to be a proxy, not a request aggregator. You would have to do the requests async on a separate threadpool and then return them back to the single inbound request on the event loop.

@jiangsuxd How did you address this in your app?


version 1039

🚨 New Camouflage mechanism to avoid being blocked
⚡ CPU usage optimization
🐛 More reliable Secondary Proxy initial setup
🐛 Updated Clash links for Android and Windows
🐛 Fixed install fail on Ubuntu 20.04


openvscode-server 1.80.2

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Let's see whether memory usage is smaller with a newer nodejs: https://github.com/conda-forge/openvscode-server-feedstock/pull/34


Federated Jobs feature

Feature Description

One-line feature description (can be used as a release note):
Primary contact (assignee): @quinton-hoole
Responsible SIGs: @kubernetes/sig-apps-feature-requests @kubernetes/sig-federation-feature-requests
Design proposal link (community repo):  https://docs.google.com/document/d/1TZ4ZMZ8AEOlVyK6H_q-zNpAdlzTip8sxMQUVQeQ-O-w/edit#heading=h.v3yscf7s8679
Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @quinton-hoole @madhusudancs @irfanurrehman
Approver (likely from SIG/area to which feature belongs): @quinton-hoole
Feature target (which target equals to which milestone):

Alpha release target (1.7): Inital implementation of the design along with API.

Is there anything here that's specific to batch jobs? It seems like the goals you described would also make sense for long-running services.
BTW we have a proposal that introduces the concept of batch queues. Assuming that the proposal is adopted in some form, it might make sense to think of a federated/global queue that makes the placement decision when it decides to "admit" a job.

I think the better person to answer would be @quinton-hoole and @jianhuiz

@davidopp The intention of this feature is to support precisely the Kubernetes Jobs API to start with .  i.e. https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/
We should definitely extend it over time to support other types of workloads, as they become supported by Kubernetes.  I will take a look at your batch queues design proposal - it looks interesting.

Assigning this to myself as a proxy for @jianhuiz whom I cannot seem to assign to.

I just meant that since the primary functionality described here is picking a cluster or clusters, extending it to handle something like ReplicaSet (or even StatefulSet) might be pretty straightforward. The description didn't sound very Job-specific.

@quinton-hoole I've updated the feature description to fit the new template. Please, fill the empty fields in the new template (their actual state was unclear).

xref https://github.com/kubernetes/kubernetes/issues/34261

@quinton-hoole milestone has been updated to 1.8. Which stage will this feature target for 1.8?

@idvoretskyi alpha as per label.

@quinton-hoole @kubernetes/sig-federation-feature-requests any updates for 1.8? Is this feature still on track for the release?

It's in 1.8 as alpha feature with out re-balancing implemented
https://github.com/kubernetes/kubernetes/issues/45187

@quinton-hoole Any plans for this in 1.11?
If so, can you please ensure the feature is up-to-date with the appropriate:

Description
Milestone
Assignee(s)
Labels:

stage/{alpha,beta,stable}
sig/*
kind/feature

cc @idvoretskyi

@justaugustus, I would suggest closing this issue here, as federation features are no longer released with k8s releases.

Thanks for the update, @irfanurrehman!
/close


Explain client_secret (generation, handling)

Lots of OIDC examples around the net use the client_secret mechanism to authenticate the OIDC client.
On this page it is briefly mentioned:
"client_secret	required for web apps, not allowed for public clients	The application secret that you created in the Azure Portal for your app under Keys. It cannot be used in a native app (public client), because client_secrets cannot be reliably stored on devices. It is required for web apps and web APIs (all confidential clients), which have the ability to store the client_secret securely on the server side."
It is marked as required for webapps, so could we have a section explaining how to set it up?
Is the official way to create a key with description="client_secret" and let Azure generate the value? It is possible to enter a value, but it gets overwritten by Azure upon saving. Does the description matter? I have seen example screenshots that the description of the key is being set to "Client Secret"? I don't think it does, but it would be good to document this explicitly in this page

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

ID: 2870d4a9-e204-023a-56a8-c34e56347b43
Version Independent ID: 846fe3ae-21cb-e030-f68f-db73acef0c74
Content: Understand the OAuth 2.0 authorization code flow in Azure AD
Content Source: articles/active-directory/develop/active-directory-protocols-oauth-code.md
Service: active-directory
GitHub Login: @CelesteDG
Microsoft Alias: celested

Hello @valentijnscholten - To create a secret key:

See https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-integrating-applications#to-add-application-credentials-or-permissions-to-access-web-apis
Follow step 4 in the To add application credentials, or permissions to access web APIs section.
Copy the application key value. This is the value for the clientSecret.

Thanks. I did figure that out, but thought it would be good to document it here.
But it looks like there's another page already describing it, but it's located a in very different location so it's not obvious it's there or how to get there :)

Hello @valentijnscholten - Thank you for the feedback. We have various topics that talk about the client secret so we'll need it as a standalone topic that all the other topics can link to. This will prevent duplication of content and make it easier for us to maintain a single topic that we can update anytime. I've opened a documentation backlog work item to track this doc work. We may not get to it right away, but we'll definitely get this work item on our queue. Thank you.

Opened PBI 497277
@MohitGargMSFT @SaurabhSharma-MSFT @Mike-Ubezzi-MSFT - #please-close Provided the answer for now and customer is unblocked. I've got a PBI to create a dedicated topic for this. Thank you.


Server login delay/unable to login

After confirming the connection on Discord, the plugin sometimes refuses to log players in without any debug messages in console or something.
Way to recreate:
Make multiple people connect to the server at the same time and try to login.
4.0.3 slf4j version and no slf4j.

Solved the problem https://github.com/Alhxe/Discord-Integration/commit/697a82d8ce76f157bc90cd75b931efd838615433

Do you have the messages used in the language file?
In addition to this, I will add the possibility that this command is optional

I misunderstood the problem, a new analysis is pending.


[Bug]: Editing a comment clears out mention linking

What happened?
When editing a comment, the link to the mentioned user is removed.
Steps to reproduce the problem

Make a comment and mention someone
Edit comment
Save edit comment

What should have happened?
Link should remain after editing
What platforms do you use to access the site?
Linux
What browsers do you use to access the site?
Mozilla Firefox
Additional information, context and logs
Just noticed it and know it's a new feature but wanted to mention it.

@manuelurenah can you help with this one when you have a few minutes?


Simplification.And.retractLocalFunction: cases for sort inj and builtins

Fixes https://github.com/kframework/kore/issues/2095

Reviewer checklist

[ ] Test coverage: stack test --coverage
[ ] Public API documentation: stack haddock

With the changes from this PR: test-issue-vote-contract.out.golden
Without the changes: test-issue-vote-contract.out.fail
test-issue-vote-contract.sh.out.zip

@sskeirik Could you please verify the output on this one, too?

@ttuegel Deciphering the output of kore files is more work to me than just building the PR branch, copying the bins to where my script expects, and re-running my tests. After doing that:

I'm still seeing the unsatisfiable branch is not pruned, but with some differences (see below).
I'm seeing another unsatisfiable branch that I did not see before

Differences between previous and new version of unsatisfiable branch:
For reference, here is the definition of #lookup a function which wraps map access:
syntax OptionData ::= #lookup(Map, Data, TypeName) [function, smtlib(lookup)]
// --------------------------------------------------------------------------
rule #lookup(M, K, VT) => Some {M[K]}:>Data requires K in_keys(M) andBool         isValue(VT,{M[K]}:>Data)
rule #lookup(M, K, _ ) => None              requires notBool K in_keys(M)

Here is the previous output (with irrelevant constraints omitted):
{ false #Equals I2 +Int 1 ==Int I3 +Int 1 }
{ project:Data(     'QuesUnds'3 [ #SemanticCastToInt ( 'QuesUnds'1 ) ] ) #Equals #SemanticCastToInt ( I2 ) }
{ project:Data(     'QuesUnds'3 [ #SemanticCastToInt ( 'QuesUnds'1 ) ] ) #Equals #SemanticCastToInt ( I3 ) }

Here is the new output (with irrelevant constraints omitted):
(1) { false #Equals I2 +Int 1 ==Int I3 +Int 1 }
(2) { #SemanticCastToInt ( 'QuesUnds'1 ) in_keys('QuesUnds'3) #Equals true }
(3) { project:Data(     'QuesUnds'3 [ #SemanticCastToInt ( 'QuesUnds'1 ) ] ) #Equals #SemanticCastToInt ( I2 ) }
(4) { #lookup( 'QuesUnds'3 , #SemanticCastToInt ( 'QuesUnds'1 ) , int ) #Equals Some #SemanticCastToInt ( I3 ) }
(5) #Ceil( #lookup( 'QuesUnds'3 , #SemanticCastToInt ( 'QuesUnds'1 ) , int ) )
(6) #Ceil( project:Data(     'QuesUnds'3 [ #SemanticCastToInt ( 'QuesUnds'1 ) ] ) )

For some reason, the #lookup function in line (4) is not being simplified to Some project:Data(     'QuesUnds'3 [ #SemanticCastToInt ( 'QuesUnds'1 ) ] by the definition of #lookup and line (2), which would allow generating the equality:
(7) { project:Data(     'QuesUnds'3 [ #SemanticCastToInt ( 'QuesUnds'1 ) ] ) #Equals #SemanticCastToInt ( I3 ) }

New Unsatisfiable Branch
(1) { None #Equals #lookup( 'QuesUnds'3 , #SemanticCastToInt ( 'QuesUnds'1 ) , int ) }
(2) { #SemanticCastToInt ( 'QuesUnds'1 ) in_keys('QuesUnds'3) #Equals true }

By (2) and definition of #lookup, (1) should evaluate to None #Equals Some ... which should be unsatisfiable.

I'm investigating why #lookup doesn't get evaluated, I'll attach the log with debugging information on equation attempts for this symbol here:
debugLookupEquation.txt

Deciphering the output of kore files is more work to me than just building the PR branch, copying the bins to where my script expects, and re-running my tests.

@sskeirik The bug report you submitted with #2095 doesn't contain any symbol #lookup. Are you using a different version of the semantics? Are you using a different version of the frontend?
@ana-pantilie I'm going to review this as-is and if there are issues remaining, we will deal with those later.

@ttuegel I'm not sure 100% sure if everything is exactly the same. I suspect there are differences, though I think they are minor. I haven't had to do a proper debugging session to compare the previous and current versions. If you guys are happy with this, please merge it and I will follow-up when I have time to address this fully.


on hover popup for monitor?

Hello, set up a page with the monitor module from superadmin.
When I go to the url domain/$monitor it shows the statistics.
But it does not show me the popup as it appears on the superadmin landing
It does not show any errors from the console.
thank you very much for your help.
(https://www.totaljs.com/superadmin).

my app

Hi @adrianrey05,
try to refresh website and move your cursor to your website... still nothing?

Before lifting the issue I did many times, also cleared all navigation data.
Today just started working... :confused:
A thousand apologies and thanks.

:-D no problem! Great 👍


Feature docker

Finished dockerizing all the components. Now we work on the actual site.

Looks good.


AMD module support

Added AMD module support (require.js)

Please make a release as well if possible.

Should already be in 0.6.0, please check. And thank you for the request.


Issues with building from source

UPDATE: I have resolved the issue. Due to the naming conventions on the library files in Fedora, the build script will end up failing when trying to compile uinput.c
The solution I found was to just manually compile it myself using this line:
sudo gcc -pthread -shared -Wl,-z,relro -specs=/usr/lib/rpm/redhat/redhat-hardened-ld build/temp.linux-x86_64-2.7/src/uinput.o -L/usr/lib64/libpython2.7.so.1.0 -o build/lib.linux-x86_64-2.7/libuinput.so
This builds it for Python 2.7 on my system. For building it using Python 3, the line should be:
sudo gcc -pthread -shared -Wl,-z,relro -specs=/usr/lib/rpm/redhat/redhat-hardened-ld build/temp.linux-x86_64-2.7/src/uinput.o -L/usr/lib64/libpython3.so -o build/lib.linux-x86_64-2.7/libuinput.so
Is there a way to have this addressed to make compilation on Fedora work out of the box?

Old Post
Hey, I'm currently running Fedora 24-beta, however this issue is present in Fedora 23 as well.
It seems the build scripts aren't set up correctly,(See Edit2) so it won't build properly. Using "sudo python setup.py install" gives the output:
running install
running build
running build_py
running build_ext
building 'libuinput' extension
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/usr/include/python2.7 -c scc/uinput.c -o build/temp.linux-x86_64-2.7/scc/uinput.o
gcc -pthread -shared -Wl,-z,relro -specs=/usr/lib/rpm/redhat/redhat-hardened-ld build/temp.linux-x86_64-2.7/scc/uinput.o -L/usr/lib64 -lpython2.7 -o build/lib.linux-x86_64-2.7/libuinput.so
/bin/ld: cannot find -lpython2.7
collect2: error: ld returned 1 exit status
error: command 'gcc' failed with exit status 1

The issue is also seen [here.] (https://www.reddit.com/r/SteamController/comments/3w1bsk/standalone_steam_controller_driver/)
Would we be able to get this addressed soon?
Thank you for your time and all the work you've put into this project, btw. :)
EDIT:
I also tried cloning from the repo itself versus using the supplied tars in the documentation, and it has the same typo and issue, as is seen here:
running install
running bdist_egg
running egg_info
creating python_steamcontroller.egg-info
writing requirements to python_steamcontroller.egg-info/requires.txt
writing python_steamcontroller.egg-info/PKG-INFO
writing top-level names to python_steamcontroller.egg-info/top_level.txt
writing dependency_links to python_steamcontroller.egg-info/dependency_links.txt
writing manifest file 'python_steamcontroller.egg-info/SOURCES.txt'
reading manifest file 'python_steamcontroller.egg-info/SOURCES.txt'
writing manifest file 'python_steamcontroller.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
creating build
creating build/lib.linux-x86_64-2.7
creating build/lib.linux-x86_64-2.7/steamcontroller
copying src/events.py -> build/lib.linux-x86_64-2.7/steamcontroller
copying src/cheader.py -> build/lib.linux-x86_64-2.7/steamcontroller
copying src/uinput.py -> build/lib.linux-x86_64-2.7/steamcontroller
copying src/__init__.py -> build/lib.linux-x86_64-2.7/steamcontroller
copying src/tools.py -> build/lib.linux-x86_64-2.7/steamcontroller
copying src/daemon.py -> build/lib.linux-x86_64-2.7/steamcontroller
running build_ext
building 'libuinput' extension
creating build/temp.linux-x86_64-2.7
creating build/temp.linux-x86_64-2.7/src
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/usr/include/python2.7 -c src/uinput.c -o build/temp.linux-x86_64-2.7/src/uinput.o
src/uinput.c: In function ‘uinput_key’:
src/uinput.c:148:5: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
     write(fd, &ev, sizeof(ev));
     ^~~~~~~~~~~~~~~~~~~~~~~~~~
src/uinput.c: In function ‘uinput_abs’:
src/uinput.c:159:5: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
     write(fd, &ev, sizeof(ev));
     ^~~~~~~~~~~~~~~~~~~~~~~~~~
src/uinput.c: In function ‘uinput_rel’:
src/uinput.c:170:5: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
     write(fd, &ev, sizeof(ev));
     ^~~~~~~~~~~~~~~~~~~~~~~~~~
src/uinput.c: In function ‘uinput_scan’:
src/uinput.c:181:5: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
     write(fd, &ev, sizeof(ev));
     ^~~~~~~~~~~~~~~~~~~~~~~~~~
src/uinput.c: In function ‘uinput_set_delay_period’:
src/uinput.c:192:5: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
     write(fd, &ev, sizeof(ev));
     ^~~~~~~~~~~~~~~~~~~~~~~~~~
src/uinput.c:195:5: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
     write(fd, &ev, sizeof(ev));
     ^~~~~~~~~~~~~~~~~~~~~~~~~~
src/uinput.c: In function ‘uinput_syn’:
src/uinput.c:206:5: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
     write(fd, &ev, sizeof(ev));
     ^~~~~~~~~~~~~~~~~~~~~~~~~~
gcc -pthread -shared -Wl,-z,relro -specs=/usr/lib/rpm/redhat/redhat-hardened-ld build/temp.linux-x86_64-2.7/src/uinput.o -L/usr/lib64 -lpython2.7 -o build/lib.linux-x86_64-2.7/libuinput.so
/bin/ld: cannot find -lpython2.7
collect2: error: ld returned 1 exit status
error: command 'gcc' failed with exit status 1

The issue is this line: gcc -pthread -shared -Wl,-z,relro -specs=/usr/lib/rpm/redhat/redhat-hardened-ld build/temp.linux-x86_64-2.7/src/uinput.o -L/usr/lib64 -lpython2.7 -o build/lib.linux-x86_64-2.7/libuinput.so
There needs to be a space between the L in "-L/usr/lib64 -lpython2.7", and should be "-L /usr/lib64 -lpython2.7", I think.
Edit2: The build scripts seem fine, on second thought. The issue seems to be missing a python library for it to call and load. Unfortunately, I haven't been able to figure out what package I am missing, or if the library is located somewhere else under a different name, or anything of the sort. I will update if I find a solution to the missing library.

By the way, use
	```
	triple apostrophes
	```

when you are pasting terminal output, because that is unreadable :)

Post edited accordingly. Thanks, I'll remember that next time!
Haven't ever submitted an issue to github before, so I wasn't sure off hand how to fix that.


Intermittent connection issues

Version
botbuilder-integration-aiohttp>=4.9.1
Describe the bug
We have deployed a teams bot with python SDK. Intermittently when the users are trying to converse with the bot we get exceptions in the SDK
concurrent.futures._base.CancelledError
if "MemberNotFoundInConversation" in e.args[0]:
IndexError: tuple index out of range
although if the same user retries the same message again , right away everything works fine. Due to this we are unable to scale the bot further.
To Reproduce
Steps to reproduce the behavior:
Intermittent issue, Start the bot and monitor the conversation logs
Expected behavior

Give clear error message explaining where is the issue
Bot should respond to the user

Screenshots
Error type 1
[2020-09-11 04:23:37 +0000] [12] [DEBUG]
[on_turn_error] unhandled error:
DEBUG:aiohttp.web:
[on_turn_error] unhandled error:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/botbuilder/core/bot_adapter.py", line 128, in run_pipeline
context, callback
File "/usr/local/lib/python3.7/site-packages/botbuilder/core/middleware_set.py", line 69, in receive_activity_with_status
return await self.receive_activity_internal(context, callback)
File "/usr/local/lib/python3.7/site-packages/botbuilder/core/middleware_set.py", line 79, in receive_activity_internal
return await callback(context)
File "/usr/local/lib/python3.7/site-packages/botbuilder/core/activity_handler.py", line 68, in on_turn
await self.on_message_activity(turn_context)
File "/teams-connector/bot/teams_bot.py", line 112, in on_message_activity
await turn_context.send_activity(row['text'])
File "/usr/local/lib/python3.7/site-packages/botbuilder/core/turn_context.py", line 170, in send_activity
result = await self.send_activities([activity_or_text])
File "/usr/local/lib/python3.7/site-packages/botbuilder/core/turn_context.py", line 217, in send_activities
return await self._emit(self._on_send_activities, output, logic())
File "/usr/local/lib/python3.7/site-packages/botbuilder/core/turn_context.py", line 295, in _emit
return await logic
File "/usr/local/lib/python3.7/site-packages/botbuilder/core/turn_context.py", line 212, in logic
responses = await self.adapter.send_activities(self, output)
File "/usr/local/lib/python3.7/site-packages/botbuilder/core/bot_framework_adapter.py", line 728, in send_activities
raise error
File "/usr/local/lib/python3.7/site-packages/botbuilder/core/bot_framework_adapter.py", line 714, in send_activities
activity.conversation.id, activity.reply_to_id, activity
File "/usr/local/lib/python3.7/site-packages/botframework/connector/aio/operations_async/_conversations_operations_async.py", line 529, in reply_to_activity
request, stream=False, **operation_config
File "/usr/local/lib/python3.7/site-packages/msrest/async_client.py", line 115, in async_send
pipeline_response = await self.config.pipeline.run(request, **kwargs)
File "/usr/local/lib/python3.7/site-packages/msrest/pipeline/async_abc.py", line 159, in run
return await first_node.send(pipeline_request, **kwargs)  # type: ignore
File "/usr/local/lib/python3.7/site-packages/msrest/pipeline/async_abc.py", line 79, in send
response = await self.next.send(request, **kwargs)  # type: ignore
File "/usr/local/lib/python3.7/site-packages/msrest/pipeline/async_requests.py", line 106, in send
return await self.next.send(request, **kwargs)
File "/usr/local/lib/python3.7/site-packages/msrest/pipeline/async_abc.py", line 79, in send
response = await self.next.send(request, **kwargs)  # type: ignore
File "/usr/local/lib/python3.7/site-packages/msrest/pipeline/async_abc.py", line 79, in send
response = await self.next.send(request, **kwargs)  # type: ignore
File "/usr/local/lib/python3.7/site-packages/msrest/pipeline/async_requests.py", line 85, in send
await self.driver.send(request.http_request, **kwargs)
File "/usr/local/lib/python3.7/site-packages/msrest/universal_http/async_requests.py", line 91, in send
return await super(AsyncRequestsHTTPSender, self).send(request, **requests_kwargs)
File "/usr/local/lib/python3.7/site-packages/msrest/universal_http/async_requests.py", line 79, in send
await future
concurrent.futures._base.CancelledError
Error Type 2
[on_turn_error] unhandled error: tuple index out of range
DEBUG:aiohttp.web:
[on_turn_error] unhandled error: tuple index out of range
Traceback (most recent call last):
File "/teams-connector/bot/teams_bot.py", line 162, in get_member_details
turn_context, turn_context.activity.from_property.id
File "/usr/local/lib/python3.7/site-packages/botbuilder/core/teams/teams_info.py", line 175, in get_member
connector_client, conversation_id, member_id
File "/usr/local/lib/python3.7/site-packages/botbuilder/core/teams/teams_info.py", line 264, in _get_member
conversation_id, member_id
File "/usr/local/lib/python3.7/site-packages/botframework/connector/aio/operations_async/_conversations_operations_async.py", line 731, in get_conversation_member
request, stream=False, **operation_config
File "/usr/local/lib/python3.7/site-packages/msrest/async_client.py", line 115, in async_send
pipeline_response = await self.config.pipeline.run(request, **kwargs)
File "/usr/local/lib/python3.7/site-packages/msrest/pipeline/async_abc.py", line 159, in run
return await first_node.send(pipeline_request, **kwargs)  # type: ignore
File "/usr/local/lib/python3.7/site-packages/msrest/pipeline/async_abc.py", line 79, in send
response = await self.next.send(request, **kwargs)  # type: ignore
File "/usr/local/lib/python3.7/site-packages/msrest/pipeline/async_requests.py", line 106, in send
return await self.next.send(request, **kwargs)
File "/usr/local/lib/python3.7/site-packages/msrest/pipeline/async_abc.py", line 79, in send
response = await self.next.send(request, **kwargs)  # type: ignore
File "/usr/local/lib/python3.7/site-packages/msrest/pipeline/async_abc.py", line 79, in send
response = await self.next.send(request, **kwargs)  # type: ignore
File "/usr/local/lib/python3.7/site-packages/msrest/pipeline/async_requests.py", line 85, in send
await self.driver.send(request.http_request, **kwargs)
File "/usr/local/lib/python3.7/site-packages/msrest/universal_http/async_requests.py", line 91, in send
return await super(AsyncRequestsHTTPSender, self).send(request, **requests_kwargs)
File "/usr/local/lib/python3.7/site-packages/msrest/universal_http/async_requests.py", line 79, in send
await future
concurrent.futures._base.CancelledError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/botbuilder/core/bot_adapter.py", line 128, in run_pipeline
context, callback
File "/usr/local/lib/python3.7/site-packages/botbuilder/core/middleware_set.py", line 69, in receive_activity_with_status
return await self.receive_activity_internal(context, callback)
File "/usr/local/lib/python3.7/site-packages/botbuilder/core/middleware_set.py", line 79, in receive_activity_internal
return await callback(context)
File "/usr/local/lib/python3.7/site-packages/botbuilder/core/activity_handler.py", line 68, in on_turn
await self.on_message_activity(turn_context)
File "/teams-connector/bot/teams_bot.py", line 75, in on_message_activity
email_id, name, tenant_id = await self.get_member_details(turn_context)
File "/teams-connector/bot/teams_bot.py", line 165, in get_member_details
if "MemberNotFoundInConversation" in e.args[0]:
IndexError: tuple index out of range
`
Additional context
we used below starter code, and more or less have the same structure
https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/python/57.teams-conversation-bot

@jwiley84 Can you take a look at this?

@tdurnford @jwiley84  please do let me know incase you need any additional information or context on this issue.

Hi @saikiran2603 I see the issue you raised in the samples repo. in order to keep the work in one location, so you don't possibly get 2 different responses, we're going to go ahead and close this one. If Kyle is able to determine that the  issue is with the python SDK itself, we'll reopen this issue here.


Tracking issue of winit interface for Gtk

We are going to have a new unified interface to build window after #163. It should cover most usage in Tauri.
But there are still many missing features for gtk. Below is the list of features (but not limited to):

[ ] window methods (see comment below)
[ ] events (see comment below)
[ ] platform traits (need to discuss what traits and methods are needed)
[ ] monitor module

Missing window methods:

[ ] set_ime_position
[ ] set_cursor_position
[ ] current_monitor
[ ] available_monitor
[ ] primary_monitor

Missing events:

[ ] DeviceEvent
[ ] LoopDestroyed
[ ] MainEventsCleared
[ ] NewEvents
[ ] RedrawEventsCleared
[ ] RedrawRequested
[ ] Resumed
[ ] Suspended
[x] UserEvent
[ ] WindowEvent

The API is working great. One thing that we could try improve is not relying on the winit crate on Linux (currently only used for typing, e.g. the dpi module).


AWS MFA: handle unknown users

Merged via https://github.com/Blazebit/blaze-query/commit/a73df4204051659e462696d407fabcab2c112c87


Include position="floating" on ionic theme labels

Is your feature request related to a problem? Please describe.
I am working on an Ionic app and all my forms are "material" like design (without using Angular Material). This is achieved by using a position="floating" parameter in the ion-label HTML tag. This makes the label move up or down just like material, but it keeps up if the input has a placeholder.
Describe the solution you'd like
I would like to have the option to use that setup of ion-items, which I believe is when you put  position="floating" to the ion-label inside the ion-item
Describe alternatives you've considered
I've considered using Formly Material, but the design is not the same as the ones I'm using and it's very hard to radically change styles using this library. I was thinking of making my own wrapper, but I'm storing the FormlyFieldConfig in a database on my server, so I don't want to have too much overhead when creating a new form.
Additional context
Here you can see the style of the form when having a placeholder:

Here is a snippet of that code:
<form [formGroup]="userInfoForm" (ngSubmit)="onSubmit()">

      <ion-item>
        <ion-label class="form-label mat-primary" position="floating">Email</ion-label>
        <ion-input<EMAIL_ADDRESS>autocapitalize="on" type="text" formControlName="email"></ion-input>
      </ion-item>

    .... rest of the form ....
</form>
Here is a form without placeholder, with the label inside the input (as Material does):

And here is with the input filled, with the label in a smaller font:

The code is similar for this one as well:
<form class="login-form" [formGroup]="loginForm" (ngSubmit)="logIn()">

      <ion-item>
        <ion-label class="form-label" position="floating">Email</ion-label>
        <ion-input  type="email" formControlName="email"></ion-input>
      </ion-item>

    ... rest of the form ...
</form>

see https://github.com/ngx-formly/ngx-formly/issues/1263#issuecomment-434982843


Support Laravel 5

Can you bump the version up to support Laravel 5 too.

Any updates on this?

I would also be interested in this, actually during composer update I get:
% composer update
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for xethron/migrations-generator dev-master -> satisfiable by xethron/migrations-generator[dev-master].
    - Conclusion: remove laravel/framework v5.0.0
    - xethron/migrations-generator dev-master requires illuminate/support ~4.1 -> satisfiable by illuminate/support[v4.1.0, v4.1.1, v4.1.10, v4.1.11, v4.1.12, v4.1.13, v4.1.14, v4.1.15, v4.1.16, v4.1.17, v4.1.18, v4.1.19, v4.1.2, v4.1.20, v4.1.21, v4.1.22, v4.1.23, v4.1.24, v4.1.25, v4.1.26, v4.1.27, v4.1.28, v4.1.29, v4.1.3, v4.1.30, v4.1.4, v4.1.5, v4.1.6, v4.1.7, v4.1.8, v4.1.9, v4.2.1, v4.2.12, v4.2.16, v4.2.2, v4.2.3, v4.2.4, v4.2.5, v4.2.6, v4.2.7, v4.2.8, v4.2.9].
    - don't install illuminate/support v4.1.0|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.1|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.10|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.11|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.12|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.13|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.14|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.15|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.16|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.17|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.18|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.19|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.2|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.20|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.21|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.22|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.23|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.24|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.25|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.26|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.27|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.28|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.29|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.3|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.30|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.4|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.5|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.6|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.7|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.8|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.1.9|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.2.1|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.2.12|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.2.16|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.2.2|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.2.3|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.2.4|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.2.5|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.2.6|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.2.7|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.2.8|don't install laravel/framework v5.0.0
    - don't install illuminate/support v4.2.9|don't install laravel/framework v5.0.0
    - Installation request for laravel/framework 5.0.* -> satisfiable by laravel/framework[v5.0.0].

I decided to start the slow process of moving one of my CI apps over to L5 now that 5.0 is out.  First feature will be migrations.  I fuddled with it a bit last night and got it to run.  Some code changes, but mostly just different setup config (where you register artisan commands,  binding the migration repository interface, etc).  L5 pushed a lot of package=>framework binding points around.  Config is totally different.
Also, there's an issue with way\generators and binding its shipped config (just like with all L4 packages).  I'll need to check to see if he has a ~2 compatible update for L5 or if we'll have to deal with upgrading to ~3.
Hopefully I'll have a PR up of some sort in the next couple of days.

@jamisonvalenta goos stuff, looking forward to the PR

@jamisonvalenta I also started playing with it last weekend, and it appears we would have to rewrite the code I stole from @JeffreyWay as he won't be updating his Generators.
We have one of three options mostly. Submit a PR to the @laravel source for the features required to write the migrations, extend their class and build in our own functionality, or don't depend on other classes and let the plugin handle everything.
Personally, I'd push for the first option. It means there's less code to maintain, and if the styling ever changes, its the responsibility of Laravel to update it.
Doctrine and the plugin itself seems to work fine with some minor changes.
I have created a new branch called l5 that we can all work on. The composer package has also been updated to work with Laravel 5, so you can require it in composer as such:
"require-dev": {
    "xethron/migrations-generator": "dev-l5"
}

I'm also thinking that the actual structure of the classes might need to be revised... I never really liked it. Any ideas are welcome.
@jamisonvalenta would like to see what you're busy with so we don't do double work. I'm going to spend some time extending the L5 migrations generator class, and work in the features we require to write specific values. Once done, I'll see if I can get it into the Laravel source which would help other packages that might want to do something similar.

Ugh.  Sorry, composer is being a serious pain.
This package almost works out of the box.  There a couple of changes necessary inside of the migrations service provider, and there are also a few changes that need to be made to way/generators to be L5 ready.  My thought has always been to do a two-fold approach:
1 - spin up a temporary package that allows the package to be used with L5
2 - consider a rewrite
3 - do the rewrite
If I could just get composer to behave I would be happy to host the changes to way/generators that would get this package up and running again while @Xethron contemplates/implements a rewrite.
Ok.  Diving in again.

Composer debugged.  @Xethron, I have a PR up: https://github.com/Xethron/migrations-generator/pull/40.  Pull failed unit testing, but it looks like at least one of the tests will need to be rewritten (registers_the_package), since that doesn't matter in L5 anymore.

Everything seems to be working. Closing issue

Cheers ears! :+1:


Support multiple keys in bigdiffy

Addresses #137.
There were two options that I thought about:

Join all keys and to get a single String in *KeyFn functions.
Use the list of string representation of the keys as key to the join.

Decided to go with (1) since we will need to join the keys anyways to write the results.

Can you also add a test that runs with multiple keys?
Also would be good to update the docs with the new format.

Sorry, was travelling for a bit. Can you resolve conflicts? and then we can try to get this merged

@idreeskhan PTAL, rebased master and added multikey case class

LGTM, if you have a chance could you do some quick and dirty benchmarking to see the performance impact of boxing? If not we can probably just create an open issue for it and revisit if it crops up.


Admin Configuration Page

https://www.loom.com/share/0235a66b46f04f7691dab68873dce7c3?sid=da949c8e-3e90-4d94-8c18-b332985b0447
https://www.loom.com/share/be099a1ad1814aca999bae5520355f65?sid=3b0c4769-ff72-4d63-9291-b512ae246c08

Waiting for review

waiting for review

@Miley-Afful  There were 2 configurations when you expanded, so it should display '2' when not expanded. It should only show '0' when there are no configurations at all.

@muchinon, thanks for drawing my attention to that. please the changes have been made and committed