[WIP] fix(example): add a multisig example

Description
This PR adds an example on how to use multisigs.
More specifically it is implementing the following steps :

Creates the MultiSig account from Alice, Bob and Charlie addresses
Sends funds from Alice to the MultiSig account
Then tries to send funds from the MultiSig account to Eve

It makes a transferKeepAlive transaction and then :

constructs the signing payload
derives the tx hash of a signing payload
the tx is not submitted to the node

Calls approveAsMulti by giving as input the tx hash from step i

constructs the signing payload
signs the payload as Alice
serializes a signed TX
derives TX hash of a signed tx
submits the tx to the node

Call asMulti by giving as input the signingPayload from step i

constructs the signing payload
signs the payload as Bob
serializes a signed TX
derives TX hash of a signed tx
submits tx to node

Issue
The current example is not 100% correct since when it is run, it only submits the approveAsMulti transaction and then the asMulti is not submitted.
Possible errors

Maybe the timepoint inserted in the asMulti tx is not correct. I think that this timepoint needs to use the index and the height from the approveAsMulti result but I am not sure how to get that correctly.
Also I have some doubts on the maxWeight that I use in the transactions.

*** It is definitely a WIP so that is why an input from your side would be greatly appreciated.

Creates the MultiSig account from Alice, Bob and Charlie addresses
Sends funds from Alice to the MultiSig account

Could we abstract both of these steps outside of the main function to clear up some space and potentially make it easier to read. Since these are preliminary actions that needs to be done before any multisig transaction logic takes place.

Another point of confusion which I think could be optimized is the naming of the payloads, and the signatures. Denoting each with a number could be justifiable in a testing enviornment, but in this case because its a specific set of instructions to create a multisig tx, it would be more useful to have more specific naming.

Creates the MultiSig account from Alice, Bob and Charlie addresses
Sends funds from Alice to the MultiSig account

Could we abstract both of these steps outside of the main function to clear up some space and potentially make it easier to read. Since these are preliminary actions that needs to be done before any multisig transaction logic takes place.

Hey @TarikGul
:white_check_mark: For the first one, I created the createMultisigAccountfunction
:bangbang: For the second one, if I want to extract the code related to funds sent to multisig, I need to put the corresponding transferKeepAlive in a separate function. When I try to do this, I realize that I need to pass a lot of arguments in the function (variables like block, blockHash, genesisHash, etc which are used again in following functions in main) and it looks like it defeats its purpose. If you have any ideas on how to do this please let me know.

Creates the MultiSig account from Alice, Bob and Charlie addresses
Sends funds from Alice to the MultiSig account

Could we abstract both of these steps outside of the main function to clear up some space and potentially make it easier to read. Since these are preliminary actions that needs to be done before any multisig transaction logic takes place.

Hey @TarikGul ✅ For the first one, I created the createMultisigAccountfunction ‼ For the second one, if I want to extract the code related to funds sent to multisig, I need to put the corresponding transferKeepAlive in a separate function. When I try to do this, I realize that I need to pass a lot of arguments in the function (variables like block, blockHash, genesisHash, etc which are used again in following functions in main) and it looks like it defeats its purpose. If you have any ideas on how to do this please let me know.

Hmmm so i see what you are saying. If you think that it would be way cleaner to have the transferKeepAlive exist inside of the main function I am totally for it!

You have some errors related to the linter https://github.com/paritytech/txwrapper-core/runs/5823022101?check_suite_focus=true. I think running yarn lint should all be fixed

You have some errors related to the linter https://github.com/paritytech/txwrapper-core/runs/5823022101?check_suite_focus=true. I think running yarn lint should all be fixed

Thank you so much @0xslipk for the suggestion. yarn lint fixed all the spaces/formatting errors.
However I still have a lot of
error  Unsafe assignment of an anyvalue
even in lines that are the same as in the polkadot.ts example like these lines. Any ideas on why this appears as an error in the multisig.ts but not in the polkadot.ts ? Thank you so much in advance! :)

You have some errors related to the linter https://github.com/paritytech/txwrapper-core/runs/5823022101?check_suite_focus=true. I think running yarn lint should all be fixed

Thank you so much @0xslipk for the suggestion. yarn lintdid fix all the spaces/formatting errors. However I still have a lot of  error Unsafe assignment of an 'any' value even in lines that are exactly the same as in the polkadot.ts example like these lines.
Any ideas on why these appear as an errors in the multisig.ts but not in the polkadot.ts ?
Thank you so much in advance! :)

The current code in multisig.ts looks like it executes :

the ApproveAsMulti call (signed by Alice) and then
the AsMulti call (signed by Bob)

so we successfully get the 2 necessary approvals (threshold is 2) and we should then see the execution of the multisig transaction unsignedTXMulti (transfer of funds from the multisig account to Eve) but this does not happen. It is like the AsMulti call just adds another approval but does not trigger the execution of the multisig transaction.
I did a quick comparison of multisig tx executed from txwrapper and then of a similar one executed from the UI polkadot js apps.
In the first case (txwrapper) the transfer is not executed and if I check the events shown in the explorer I can see that the last event is a multisig.MultisigApproval event and when I click its block for details I can see the asMulti call.
However when I execute a similar transaction from polkadot-js apps UI the transfer is done and I get an event multisig.MultisigExecuted which I guess can be found here.

For the linting errror at the top of your multisig.ts file please paste:
/* eslint-disable @typescript-eslint/restrict-template-expressions */
/* eslint-disable @typescript-eslint/no-unsafe-member-access */
/* eslint-disable @typescript-eslint/no-unsafe-assignment */
/**
 * @ignore Don't show this file in documentation.
 */


Add auth, remove strategy config

Document most things!
Add Doorman.Auth.Bcrypt to be included in Ecto structs.
Remove strategy configuration option in favor of them being used
explicitly.
Add a quickstart guide in the README.

:shipit:

tyty!


Suggestion: Update Model Builder to support non-CUDA GPU's using OneAPI

The Model Builder extension currently supports GPU acceleration using CUDA Graphics card.
Please add support for GPU acceleration for non-CUDA graphics cards e.g. AMD Radeon and Intel Arc series.
It is possible to migrate existing CUDA code to OneAPI to support the Intel series of graphics cards
e.g.
https://codeplay.com/solutions/oneapi/for-cuda/
https://www.intel.com/content/www/us/en/develop/documentation/oneapi-programming-guide/top/software-development-process/migrating-code-to-dpcpp/migrating-from-cuda-to-dpcpp.html

@beccamc this is a framework suggestion. Let's transfer the issue there. No action items on MB / CLI side unless this becomes available in the framework.


Problem with latex

First off thank you for such an API. Using this I just published my very first medium story. While publishing my 2nd story which contains lots of latex code, this API is unable to parse it. I tried this notebook.

Thanks!
I didn't think about parsing LaTex, so this is something to consider for the future. Medium doesn't handle LaTeX so I'm guessing, an image will need to be created for it.

okay, thank-you


Show plugin name for actions in Command Palette

VSCode Version: Code - Insiders 1.5.0-insider (dde41be0231d6f8397d1da969ddab351f137b833, 2016-08-08T06:03:58.264Z)
OS Version: Darwin x64 15.6.0

Steps to Reproduce:
It would be great to be able to see plugin name (if possible) that registers action in Command Palette - like here I am inside TypeScript file and Command Palette offers me these actions:

But they are not applicable to TypeScript and it's not clear where they are coming from
When I try to use them I get:

I understand the problem, I just don't think that adding the name of the extension to the command palette would be the best solution. We need to spend time thinking about our overall commanding model throughout the whole product. We will consider how best to solve this problem when we look at commanding as a whole.
I will close this for the moment but we will focus on addressing this in the future when we look at commanding overall.


choice not allowed in verse

Strangely <choice> isn't allowed within <verse> but within <syl>. As <verse> may contain multiple syllables, this should be allowed.

good catch


[WF-14962] resolve composite indexes for parent deployment units for open api definitions

this fixes the missing open api definitions for classes located in the ear's lib directory or other ear modules
related issue in openapi-smallrye: smallrye/smallrye-open-api#785

Hello, grimmjo. I'm waiting for one of the admins to verify this patch with /ok-to-test in a comment.

@grimmjo Your fix looks perfect, although I would like to add a test case that covers this use case to detect future regressions.  Would you prefer to do that?  If not, I'll put one together and cherry-pick your fix.

@pferraro Thank you 😄.
I can give it a try and add a test case. Should I package it directly in the module or where should I put it?

It should reside with the other MP OpenAPI integration tests here: https://github.com/wildfly/wildfly/tree/master/testsuite/integration/microprofile/src/test/java/org/wildfly/test/integration/microprofile/openapi

@pferraro I've added an integration test combining the two scenarios from the issue

@pferraro can you review and approve the pull request?

@pferraro thanks for the review. I've fixed the small issues.
You're are very welcome. I'm glad that I could help you solving this issue 😃


FileExistsError when using on_disk_cache and multiple workers

🐛 Describe the bug
When multiple workers try to create a folder structure at the same time it fails and raises FileExistsError.
Expected behavior: create folder structure and continue
torchdata.datapipes.iter.IterableWrapper(urls)\
        .on_disk_cache(filepath_fn=filepath_fn)\
        .open_files_by_fsspec(mode='rb')\
        .end_caching(filepath_fn=filepath_fn)

dl = DataLoader(datapipe, batch_size=16, num_workers=96, persistent_workers=True)

Versions
torchdata==0.6.1

I've opened a pull request which fixes this issue


Backend Restructure

There's now one backend with an app for the game service and the user service.
The user service now has apps for:

creating users
banning users
unbanning users
updating 2 players mmr's (match-making ranking)

The game service now has:

a table to store game records (player1 Id, player 2 Id, match result, and timestamp)

It works in the dev server but I was getting migration issues when trying to deploy with nginx.
I'll make a branch in the future to integrate it with nginx.

lgtm :+1:


[6.5.x] RHBPMS-4196 - It is not possible to open copy of Business Process if …

…it's name contain whitespaces or multybyte chars

Hi @tsurdilo,
works good, but there are some inconsistency now. If you create new file with localized name it will have ID like on a top of attachment, if you make a copy with localized name it will be nicer (bottom part), but in my opinion it will be better if both ways will produce the same ID. WDYT is it possible to reuse existing code from AssetServiceServlet for working with files, or reuse this code in both places? For example some Util class with unified ID generation.

@hasys amended  - we have to push the process id on copy through the same code as on new process creation so in both cases it will generate an id similar to your first picture above (the non-readable one).

+1


Don't crash when the ingress rule has no path.

The path attribute is optional for k8s ingresses (it defaults to /), however the library here crashes if it's not specified.
The relative path check is only useful if path is specified, so add a check to see if it's there before attempting to read it.

See also #54

See also #54


Invalid template name in 'extends' tag: ''. Got this from the 'CMS_TEMPLATE' variable.

Getting the following error with latest version
Invalid template name in 'extends' tag: ''. Got this from the 'CMS_TEMPLATE' variable.

Need o add cms.context_processors.cms_settings in context_processors. My bad


Request: history preservation

Great work moving this to Typescript and adding extra features! Do you think it's easy enough to add memorising command history across sessions? Often a local REPL has the same repeated commands performed over and over. I wasn't able to figure out how to integrate https://www.npmjs.com/package/repl.history into this implementation.

Hi,
First of all, sorry for the late response and thank you for reaching out!
I'll investigate this and come back to you, but IIRC I already tried to support that in the first version but didn't make it work. Anyway I'll check it again


AM-870 SCIM pr operator

:id: Reference related issue.
https://gravitee.atlassian.net/browse/AM-870
:pencil2: A description of the changes proposed in the pull request
Fixed one bug related to passing a null value to LocalDateTime parser.
Tweaked mongo query builder for "pr" operator to make it filter out both null and non-existing values.
:memo: Test scenarios
:computer: Add screenshots for UI
:books: Any other comments that will help with documentation
:man: :woman:@mentions of the person or team responsible for reviewing proposed changes
@leleueri
This is a nice example: https://github.com/gravitee-io/gravitee-access-management/pull/1822

Tests are faling in CI, but locally are passing. We decided to merge it either way.


Uncaught ReferenceError: settings is not defined

function ChromecastComponent(player, settings1) {
  this.settings = settings1;
  ChromecastComponent.__super__.constructor.call(this, player, settings);
  if (!player.controls()) {
    this.disable();
  }
  this.hide();
  this.initializeApi();
}

Shouldn't settings be this.settings?

This seems to be a bug of the new coffeescript compiler. Havent tested that
before releasing the new version sorry. I will fix this today!
Steve Randy Tantra<EMAIL_ADDRESS>schrieb am Mi., 15. Apr. 2015
04:28:

function ChromecastComponent(player, settings1) {
this.settings = settings1;
ChromecastComponent.super.constructor.call(this, player, settings);
if (!player.controls()) {
this.disable();
}
this.hide();
this.initializeApi();
}
Shouldn't settings be this.settings?
—
Reply to this email directly or view it on GitHub
https://github.com/kim-company/videojs-chromecast/issues/12.

This one is fixed, i hope there is no other error. I currently have not time to test it. Before I release a new version, could you try it out?
I updated: https://github.com/kim-company/videojs-chromecast/tree/master/dist

It's fixed. Thanks!

Thanks for reporting it! I should test the builds next time.. :)


Added possibility to ignore duplicate assemblies

Hi,
I made another change to catch duplicate assembly / assembly load exception when calling Build(...) on metadatabuilder. The default behavior should be preserved.
I needed this for my module loader to prevent another workaround. Maybe you like it, then pull it, otherwise reject.
Thanks

Hi, sorry, did not have much time lately. I hope I can put in your changes next week


Remove Imports System, part 3

part 1: https://github.com/dotnet/samples/pull/1195
part 2: https://github.com/dotnet/samples/pull/1196
Applied Regex Replace in these directories:

snippets/visualbasic/VS_Snippets_Atlas
snippets/visualbasic/VS_Snippets_CFX

Directories to be addressed in the later parts (each directory will have separate PR):

snippets/visualbasic/VS_Snippets_CLR
snippets/visualbasic/VS_Snippets_CLR_Classic
snippets/visualbasic/VS_Snippets_CLR_System
snippets/visualbasic/VS_Snippets_CodeAnalysis
snippets/visualbasic/VS_Snippets_Data
snippets/visualbasic/VS_Snippets_Misc
snippets/visualbasic/VS_Snippets_Remoting
snippets/visualbasic/VS_Snippets_VBCSharp
snippets/visualbasic/VS_Snippets_WebNet
snippets/visualbasic/VS_Snippets_WindowsServer
snippets/visualbasic/VS_Snippets_Winforms
snippets/visualbasic/VS_Snippets_Wpf

This looks good, @Youssef1313. I'll merge your PR now.
Incidentally, I noticed that some of these files include Imports Microsoft.VisualBasic, which is also unnecessary. When you complete removing Imports System, would you like to do a PR to remove those as well. The total number should be far smaller.

Yes, I will remove them after finishing Imports System


Increase the timeout for the compliance operator tests

The timeout should not be limited by the travis timeout of 10 minutes. Increasing the timeout for scan completions.
Refs:

https://github.com/stolostron/backlog/issues/26164

Signed-off-by: Gus Parvin<EMAIL_ADDRESS>

This is resolved by the change Justin mentioned.


update.sh: update to latest Homebrew/brew tag.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your changes? Here's an example.
[x] Have you successfully run brew tests with your changes locally?

Rather than following every change on master let’s have non-developer users (i.e. those who have never run a dev-cmd or set HOMEBREW_DEVELOPER) update between tags.
This provides a fairly natural beta (the master branch) and stable (the tags) approach without restricting us to any particular way of managing our tags.
Also, ensure we always fetch tags and allow forcing tag update functionality by setting
HOMEBREW_UPDATE_TO_TAG.
This shouldn't be merged until after we tag 1.0.0 as 0.9.9 is too old to have users on for now.

I'm not sure I understand what this involves.  If this means that the "non-developer" who does brew update won't receive an update unless a new tag has been made since their last update, then I don't think this is a good idea.
Reason: Suppose a user files an issue and some fix is made in the brew repo.  But no new tag is created.  Then we can't just tell users "do brew update and try again"; we'd have to say "set HOMEBREW_DEVELOPER and then do brew update and try again" (or "run a dev-cmd and then brew update and then try again).  Besides being windy, that's just asking for user confusion.  If to avoid this new tags are created frequently, this also seems like not a good idea.  (Just wait until some tagged commit has to be reverted, etc.)
Apologies if I've misunderstood what this PR does.

If this means that the "non-developer" who does brew update won't receive an update unless a new tag has been made since their last update, then I don't think this is a good idea.

We've had a couple quite widespread breakages recently (including the linked kegs migration debacle today of which we're still dealing with the fallout) we definitely need to be more careful at upgrading all users to master.
Adding a homebrew_developer? check to every feature then remove it after a while doesn't scale.
We didn't say how often tags will be made by the way.

we'd have to say "set HOMEBREW_DEVELOPER and then do brew update and try again"

$ HOMEBREW_DEVELOPER=1 brew update

What's so difficult about that.

that's just asking for user confusion.

Slight user confusion when communicating to a single user or a few users is better than "no-commands-run" for thousands of users (which happened today, or yesterday depending on where you are).

 We don't force push here.

Current coverage is 75.41% (diff: 100%)

No coverage report found for master at 59b7f16.

Powered by Codecov. Last update 59b7f16...5bbeb4f

Then we can't just tell users "do brew update and try again"; we'd have to say "set HOMEBREW_DEVELOPER and then do brew update and try again" (or "run a dev-cmd and then brew update and then try again). Besides being windy, that's just asking for user confusion.

Really this is a question/debate about rolling release vs. tagged release software development approaches. I agree the tag approach would not make sense for taps (for now, at least) but except for when we've broken something with another change it's extremely rare that there are user fixes that we need to rapidly make changes to fix. In those cases, we can push them out more quickly to HOMEBREW_DEVELOPERs and, if things look good after a few days, make a tag.

I like the idea of "tagged release" for brew internals.  Very much so.  I just was doubtful about the implementation of putting it behind HOMEBREW_DEVELOPER.
Instead of having to tell users to do HOMEBREW_DEVELOPER=1 brew update, there should perhaps  be a new flag for update.  I don't know what the name would be, but something like brew update --rolling or something.

What's so difficult about that.

It's longer and it looks weird to the sort of newbies who are prone to getting confused.

Slight user confusion when communicating to a single user or a few users is better than "no-commands-run" for thousands of at least many users (which happened today, or yesterday depending on where you are).

There aren't just these two possibilities.

@chdiza It's behind HOMEBREW_DEVELOPER or if you've ever run a dev-cmd. We may iterate on the approach but this will be the one we start with.

@jawshooah @reitermarkus A heads up that this will be happening in the next few days as it'll affect you too.

As it currently stands this branch seems problematic due to lack of tags locally. Reproducer on clean VM:
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
brew install hub
cd /usr/local/Homebrew
hub checkout https://github.com/Homebrew/brew/pull/998
brew update

and that last brew update produces
Checking out v in /usr/local/Homebrew...
To checkout MikeMcQuaid-update-between-tags in /usr/local/Homebrew run:
  'cd /usr/local/Homebrew && git checkout MikeMcQuaid-update-between-tags
fatal: Cannot update paths and switch to branch 'v' at the same time.
Did you intend to checkout 'refs/tags/' which can not be resolved as commit?
fatal: Needed a single revision
invalid upstream refs/tags/
Already up-to-date.

It's trying to check out v because UPSTREAM_TAG is empty.

@zmwangx Well noticed. We'll need to do a forced-git fetch if there's no tags.

@chdiza Does brew update --force fix them for you?

This broke my setup. I had updated to d5b6ecf about 5-6 hours ago via brew update && brew upgrade. I installed the s3cmd package 30 minutes ago with the following output:
$ brew install s3cmd
Checking out v1.0.0 in /usr/local/Homebrew...
To checkout master in /usr/local/Homebrew run:
  'cd /usr/local/Homebrew && git checkout master
Auto packing the repository in background for optimum performance.
See "git help gc" for manual housekeeping.
Checking out v1.0.0 in /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core...
To checkout master in /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core run:
  'cd /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core && git checkout master
fatal: Cannot update paths and switch to branch 'v1.0.0' at the same time.
Did you intend to checkout 'refs/tags/1.0.0' which can not be resolved as commit?
fatal: Needed a single revision
invalid upstream refs/tags/1.0.0
==> Downloading https://homebrew.bintray.com/bottles/s3cmd-1.6.1.el_capitan.bottle.tar.gz
######################################################################## 100.0%
==> Pouring s3cmd-1.6.1.el_capitan.bottle.tar.gz
🍺  /usr/local/Cellar/s3cmd/1.6.1: 59 files, 784.4K

These messages worried me so I invoked brew update:
$  brew update
Auto packing the repository in background for optimum performance.
See "git help gc" for manual housekeeping.
error: The last gc run reported the following. Please correct the root cause
and remove .git/gc.log.
Automatic cleanup will not be performed until the file is removed.

warning: There are too many unreachable loose objects; run 'git prune' to remove them.

Checking out v1.0.0 in /usr/local/Homebrew/Library/Taps/caskroom/homebrew-cask...
To checkout master in /usr/local/Homebrew/Library/Taps/caskroom/homebrew-cask run:
  'cd /usr/local/Homebrew/Library/Taps/caskroom/homebrew-cask && git checkout master
fatal: Cannot update paths and switch to branch 'v1.0.0' at the same time.
Did you intend to checkout 'refs/tags/1.0.0' which can not be resolved as commit?
fatal: Needed a single revision
invalid upstream refs/tags/1.0.0
Checking out v1.0.0 in /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core...
To checkout master in /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core run:
  'cd /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core && git checkout master
fatal: Cannot update paths and switch to branch 'v1.0.0' at the same time.
Did you intend to checkout 'refs/tags/1.0.0' which can not be resolved as commit?
fatal: Needed a single revision
invalid upstream refs/tags/1.0.0
Already up-to-date.
+ brew upgrade --all
Auto packing the repository in background for optimum performance.
See "git help gc" for manual housekeeping.
error: The last gc run reported the following. Please correct the root cause
and remove .git/gc.log.
Automatic cleanup will not be performed until the file is removed.

warning: There are too many unreachable loose objects; run 'git prune' to remove them.

Checking out v1.0.0 in /usr/local/Homebrew/Library/Taps/caskroom/homebrew-cask...
To checkout master in /usr/local/Homebrew/Library/Taps/caskroom/homebrew-cask run:
  'cd /usr/local/Homebrew/Library/Taps/caskroom/homebrew-cask && git checkout master
fatal: Cannot update paths and switch to branch 'v1.0.0' at the same time.
Did you intend to checkout 'refs/tags/1.0.0' which can not be resolved as commit?
fatal: Needed a single revision
invalid upstream refs/tags/1.0.0
Checking out v1.0.0 in /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core...
To checkout master in /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core run:
  'cd /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core && git checkout master
fatal: Cannot update paths and switch to branch 'v1.0.0' at the same time.
Did you intend to checkout 'refs/tags/1.0.0' which can not be resolved as commit?
fatal: Needed a single revision
invalid upstream refs/tags/1.0.0

This happened every time so I went into /usr/local/Homebrew and invoked git prune & git gc & git fsck and repeated brew update:
$ Checking out v1.0.0 in /usr/local/Homebrew/Library/Taps/caskroom/homebrew-cask...
To checkout master in /usr/local/Homebrew/Library/Taps/caskroom/homebrew-cask run:
  'cd /usr/local/Homebrew/Library/Taps/caskroom/homebrew-cask && git checkout master
fatal: Cannot update paths and switch to branch 'v1.0.0' at the same time.
Did you intend to checkout 'refs/tags/1.0.0' which can not be resolved as commit?
fatal: Needed a single revision
invalid upstream refs/tags/1.0.0
Checking out v1.0.0 in /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core...
To checkout master in /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core run:
  'cd /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core && git checkout master
fatal: Cannot update paths and switch to branch 'v1.0.0' at the same time.
Did you intend to checkout 'refs/tags/1.0.0' which can not be resolved as commit?
fatal: Needed a single revision
invalid upstream refs/tags/1.0.0
Already up-to-date.
+ brew upgrade --all
Checking out v1.0.0 in /usr/local/Homebrew/Library/Taps/caskroom/homebrew-cask...
To checkout master in /usr/local/Homebrew/Library/Taps/caskroom/homebrew-cask run:
  'cd /usr/local/Homebrew/Library/Taps/caskroom/homebrew-cask && git checkout master
fatal: Cannot update paths and switch to branch 'v1.0.0' at the same time.
Did you intend to checkout 'refs/tags/1.0.0' which can not be resolved as commit?
fatal: Needed a single revision
invalid upstream refs/tags/1.0.0
Checking out v1.0.0 in /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core...
To checkout master in /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core run:
  'cd /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core && git checkout master
fatal: Cannot update paths and switch to branch 'v1.0.0' at the same time.
Did you intend to checkout 'refs/tags/1.0.0' which can not be resolved as commit?
fatal: Needed a single revision
invalid upstream refs/tags/1.0.0

@mgol Can I see the output of cd $(brew --repo) && git config homebrew.devcmdrun? Also, can you try to brew pull https://github.com/Homebrew/brew/pull/1060 && brew update --force and see how that behaves? Thanks!

@mgol and also, actually, echo HOMEBREW_DEVELOPER: $HOMEBREW_DEVELOPER. Thanks!

This:
cd $(brew --repo) && git config homebrew.devcmdrun

cds to /usr/local/Homebrew and prints nothing.
This:
brew pull https://github.com/Homebrew/brew/pull/1060 && brew update --force

resulted in:
rew pull https://github.com/Homebrew/brew/pull/1060 && brew update --force
Warning: Current branch is v1.0.0: do you need to pull inside master?
==> Fetching patch
Patch: https://github.com/Homebrew/brew/pull/1060.patch
==> Applying patch
Applying: update.sh: tweak tag handling.
==> Patch closes issue #1060
==> Patch changed:
 Library/Homebrew/cmd/update.sh | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)
Updated Homebrew from d5b6ecf to 09e0b09.
Updated 2 taps (caskroom/cask, homebrew/core).
==> Updated Formulae
antigen               fzf                   gupnp                 ipfs                  offlineimap           sonar-runner
aws-sdk-cpp           global                imagemagick           khard                 reposurgeon

And now brew update && brew upgrade behaves normally.

About the last bit:
$ echo HOMEBREW_DEVELOPER: $HOMEBREW_DEVELOPER
HOMEBREW_DEVELOPER:

So it's empty.

@mgol Thanks, will 🚢 https://github.com/Homebrew/brew/pull/1060 to fix this shortly.

Just my 2 cents on tag handling - Composer did a very nice thing when going stable. They have 3 update channels:

stable is the default and updates only to stable releases (following semver)
preview updates to any tag including alpha, beta and rc tags according to semver
snapshot updates to latest master.

The other nice thing is that once you update with a specific channel it keeps you on that channel and it explicitly stays what channel it uses the next time you update. This is really nicely working for Composer, not sure if it'd be good for Homebrew.
In short I really like the use of non-stable and stable tags which Composer does and hope Homebrew does something like that.

So how do I get Homebrew to update from 1.0.0 to 1.0.1? brew update just says I'm up to date.
I did get the fatal: Cannot update paths and switch to branch 'v1.0.1' at the same time. message, but I can't get 1.0.1 now. Short of nuking the whole thing (which I don't want to have to reinstall all my packages), what's the solutions?

In my case it seems as if Homebrew updated correctly to 1.0.1 but the brew command doesn't seem to be showing the correct version?
$ brew update
Checking out v1.0.1 in /usr/local/Homebrew...
To checkout v1.0.1 in /usr/local/Homebrew run:
  'cd /usr/local/Homebrew && git checkout v1.0.1
Already up-to-date.
$ cd /usr/local/Homebrew && git checkout v1.0.1
Already on 'v1.0.1'
$ brew --version
Homebrew 1.0.0 (git revision a381b; last commit 2016-09-21)
Homebrew/homebrew-core (git revision 48e0; last commit 2016-09-21)
$ cd /usr/local/Homebrew
$ git show-ref --tags | tail -2
d5b6ecfc5078041ddf5f61b259c57f81d5c50fcc refs/tags/1.0.0
a381b597d3ebf40887b50657df269d867a209eb7 refs/tags/1.0.1

but the brew command doesn't seem to be showing the correct version?


feat: add --sort_by global flag

Closing this as there isn't any context. If this flag is useful we can raise an internal ticket.


feat: storybook mandatory mode toggle

Enable toggling of mandatory mode between optional and required indicator.

relates to #433 ? :) found it as draft in the backlog.
maybe move it to the sprint so we remember it in the sprint-end meeting for presentation :)


kymo: downsample by position

Why this PR?
Downsampling over the spatial coordinate was a requested feature.
What to look out for
There's two small tricky aspects to this feature.

Downsampling can change the size of the Kymo (because pixels for which an insufficient number of input pixels are available are omitted). This means that either we abstract the number of pixels and use a factory method like we did for temporal downsampling; or we modify the internal _json. I picked the former to stay consistent to the existing style. Note however, that this means that the deprecated _json now contains information that doesn't take into account the downsampled nature of the Kymo.
Downsampling in position only should not invalidate timestamps. Downsampling in time should.

Note that I have considered making downsampling by time and position separate private functions on Kymo, which are then called by downsampled_by, but writing this it introduced so much duplication that I figured it wasn't worth it.

Just as a comment, I left the fixups as separate commits on purpose. I will merge these fixups into the respective commits where the code was introduced before merging.


Move DCP/1 to a different sub-domain to make way for the release of DCP/2

@NoopDog @hannes-ucsc Here's the plan for releasing DCP/2 to the public:

Continue development on DCP/2 using dev.singlecell.gi.ucsc.edu and prod.singlecell.
Add an alias for DCP/1 (data.) at v1.data.humancellatlas.org
On the DCP/2 home page add a "Click here for old version of the DCP" which links to v1.data.
On the day of DCP/2 release, redirect data.humancellatlas.org to the prod.singlecell. instance
Some months later retire DCP/1 by removing the link from the DCP/2 home page and retiring the "v1.data" sub-domain

Rationale:

It biases people to go over to the new data, too, which is what we want.
Old project URLs would still work but the user will get the DCP/2 version of the project. But that seems compatible with the DCP/1 mode of "you always see the latest version - we don't have snapshots or data releases yet".
We don't need to get a new sub-domain of humancellatlas.org assigned from the Sanger
We don't need to get teh Sanger to update the link to the DCP that's on humancellatlas.org

I'm sure we need ticket(s) to standup the Azul service in DCP/1 under "v1.data.".

No, the user's address bar should read "data.humancellatlas.org". So, "reassign" the URL?
When we do this, will we break other DCP/1 services and endpoints such as https://matrix.data.humancellatlas.org/?
We need to have a good plan..

One way this could be done is to:

For the portal, just update the content to the new content and not try to show any older versions of content and leave that on data.humancellatlas.org

For the browser leave this also on data.humancellatlas.org/explore but allow the user to select which back end they want to use. By default we would use the /v2 api but could allow the user to select to use the /v1 api.

Then the browser would call the correct back end service depending on if the user selected v1 vs v2. We could make it very clear when in V1 mode that this is the old version of the app.
Azul would could deploy on the same prod prod endpoint and use a /v1 or /v2 API version to determine which back end really gets the message. This could be setup with cloudfront or  likely API Gateway.
On the browser we could also update the NEW urls to indicate that they require the new backend. like
https://data.humancellatlas.org/explore/v2/projects/f86f1ab4-1fbb-4510-ae35-3ffd752d4dfc
For old links like
https://data.humancellatlas.org/explore/projects/f86f1ab4-1fbb-4510-ae35-3ffd752d4dfc
that exist on the internet we would want to catch those and redirect to the new version but indicate that the old version exists and provide a link to it.
Whatever we decide  needs a proper write up in a google doc but wanted to get out a sketch of a proposal in this ticket.

We want "data." to resolve to the DCP/2 instance without any added "2" etc. in the URL.
Users with bookmarked/cited URLs will resolve to e.g. the latest instance of a project in DCP/2.
DCP/1 Portal/Browser/Azul be moved to the sub-domain "v1.data." which will only exist temporarily during the overlap period with DCP/2.
"matrix.data." and "dss.data." can resolve to the DCP/1 service instances ("how?" is TBD).
The AWS Route 53 name servers for data.humancellatlas.org are in the CZI HCA account (hca-id).
We have admin access to the account but CZI would need to maintain/pay for the account to maintain the name resolution for "data." Should be very low $$. Alternatively we would have to go back to Sanger to have them tell the Registrar (Mesh Digital at domainbox.com) to point to name servers under one of our AWS accounts (could be UCSC, Broad or EBI). So either CZI needs to keep the hca-id account in perpetuity or we need to go back to Sanger to transfer "data.humancellatlas.org" to name servers that we control.

MattW (CZI) says "Our strong preference is to close all the old AWS accounts".

See also DataBiosphere/azul#2104

@NoopDog @hannes-ucsc Can we configure the DCP/1 domain to be v1,data.humancellatlas.org now and (for the short term) redirect data.humancellatlas.org to v1,data.humancellatlas.org? i.e. Users going to "data.<>" will see "v1.data.<>' in the address bar.
Then when DCP/2 goes live, we make "data.humancellatlas.org" the one-and-only URL for DCP/2 and "v1,data.humancellatlas.org" as the one-and-only URL for DCP/1.
Then at the end of the year, we tell CZI they can tear down the CZI HCA accounts (and v1,data.humancellatlas.org with it).

I think that should be possible with a 301 redirect in the origin S3 bucket that backs the DB's CloudFront distro.
https://docs.aws.amazon.com/AmazonS3/latest/dev/how-to-page-redirect.html
@NoopDog own that.

After talking with Kathleen today, we're no longer going to setup a "v1.data" sub-domain since the DCP/1 will be retired by CZI at the end of December. Instead we'll send an emails notifying the general HCA community and the portals community of the impending shutdown. When DCP/2 is ready in December we'll switch over the "data.humancellatlas.org" sub-domain to the Data Browser and Azul instances in the UCSC AWS account.

Closing as per standup.


Content of compendium "Capacités de classes" been replaced by content of compendium "Classes et spécialisations"

As stated in the title, the content of the "Capacités de classes" compendium has been replaced by the content of the "Classes et spécialisations" compendium. It is no longer possible to access the class abilities (broken links).

Fixed! (normally)


Relicense the reference implementation.

... to Apache2 with LLVM exceptions.

I was about to do this a week ago but unfortunately didn't managed it yet. I will sent a PR myself as I want to do it a little different and re-license even more. As I am technically on vacation this probably needs a few more days. Please excuse the delay and if this causes any inconveniences.

Sure, that sounds good. Please also cc Mircea Trofin<EMAIL_ADDRESS>on the new PR.

Superseded by #367.


optional non-verified mempool

Implement a non-verified optional mempool.
With double spends protection.
No RBF support.
No ECC\UTXO verification.

PR Withdrawn, this branch will NOT be merged as the mempool in spruned is meaningless.
A mempool with an entire utxo set under the hood may be useful for a lot of things but, in spruned, which target low end devices, means relevant iops, flops, and last but not least, traffic. For what?

Without an utxo set you can't see transaction fees.
Unconfirmed transactions are unreliable anyway, even here where nothing but the ECC signature can be verified.

Unfortunately I really understood the drawbacks only when I already did a lot of work, even if the "useless thing" smell was in the air, when I started calling the mempool "optional" and putting the default mempool_size value at 0,  lot of code lines ago.
Lesson learned!

Pull Request Test Coverage Report for Build 347

151 of 302 (50.0%)  changed or added relevant lines in 18 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-1.9%) to 72.959%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

spruned/app.py
0
1
0.0%

spruned/repositories/repository.py
5
6
83.33%

spruned/dependencies/pycoinnet/inv_fetcher.py
0
1
0.0%

spruned/daemon/bitcoin_p2p/init.py
1
2
50.0%

spruned/daemon/tasks/headers_reactor.py
7
9
77.78%

spruned/repositories/blockchain_repository.py
1
4
25.0%

spruned/application/logging_factory.py
1
4
25.0%

spruned/application/context.py
2
7
28.57%

spruned/application/spruned_vo_service.py
8
14
57.14%

spruned/daemon/bitcoin_p2p/utils.py
13
26
50.0%

Files with Coverage Reduction
New Missed Lines
%

spruned/daemon/bitcoin_p2p/p2p_connection.py
1
59.71%

Totals

Change from base Build 342:
-1.9%

Covered Lines:
2895

Relevant Lines:
3968

💛  - Coveralls


Enhancement: Add link to github repo to index.html

Similar to the footnote on this page add a link to the Github repo to the index.html page

Fork the repo
Download all files
Open Index.html
Add the following (or something similar) to the end of the  starting with "Powered by.."

Fork this on Github

Commit change
Open a pull request

Questions can be asked here

@Jared-Peacock
It looks like this edit got overwritten in a recent update. You're welcome to add it back in again.

Check #37


sanity.functional cmdLineTester_pltest_0 j9vmem_test_numa (docker?) test failure

Subtest j9vmem_test_numa within the test target cmdLineTester_pltest_0 fails with:
18:24:59   [ERR] Starting test j9vmem_test_numa
18:24:59   [ERR] j9vmemTest.c line 1810: j9vmem_test_numa Found zero nodes with memory even after NUMA was reported as supported (FAIL)
18:24:59   [ERR]
18:24:59   [ERR] 		LastErrorNumber: -252
18:24:59   [ERR] 		LastErrorMessage: Unknown error -1
18:24:59   [ERR]
18:24:59   [ERR] Ending test j9vmem_test_numa

jdk version under test:
17:45:47  openjdk version "1.8.0_282-internal"
17:45:47  OpenJDK Runtime Environment (build 1.8.0_282-internal-202101051708-b07)
17:45:47  Eclipse OpenJ9 VM (build master-1910cfa3a, JRE 1.8.0 Linux amd64-64-Bit 20210105_860 (JIT enabled, AOT enabled)
17:45:47  OpenJ9   - 1910cfa3a
17:45:47  OMR      - a9b64bdc8
17:45:47  JCL      - 722ab284 based on jdk8u282-b07)
17:45:47  =JAVA VERSION OUTPUT END=

Failing test machine: docker-packet-ubuntu2004-x64-1f1.
Test passed on test-ibmcloud-rhel6-x64-1 - maybe related to running on docker? (https://ci.adoptopenjdk.net/job/Test_openjdk8_j9_sanity.functional_x86-64_linux/63/)
Link to failing job: https://ci.adoptopenjdk.net/job/Test_openjdk8_j9_sanity.functional_x86-64_linux_xl/68/

The API code is https://github.ibm.com/runtimes/openj9-omr/blob/ibm_sdk/port/linux/omrvmem.c#L2081
It also determines the global memory policy https://github.ibm.com/runtimes/openj9-omr/blob/ibm_sdk/port/linux/omrvmem.c#L218
and node_bits https://github.ibm.com/runtimes/openj9-omr/blob/ibm_sdk/port/linux/omrvmem.c#L251-L279
The API code reads from /sys/devices/system/node, looking for node<num> (i.e. node0, node1, etc) sub-directories. Inside these directories there should be meminfo files which should contain a line such as Node 0 MemTotal:       16431076 kB.
The API sets the state of each node based on the global memory policy and if the node has memory.
The test code is https://github.com/eclipse/openj9/blob/master/runtime/tests/port/j9vmemTest.c#L1781-L1810
It looks for nodes which have the PREFERRED or ALLOWED policy. If there are none, the test fails.

The API code is https://github.ibm.com/runtimes/openj9-omr/blob/ibm_sdk/port/linux/omrvmem.c#L2081
It also determines the global memory policy https://github.ibm.com/runtimes/openj9-omr/blob/ibm_sdk/port/linux/omrvmem.c#L218
and node_bits https://github.ibm.com/runtimes/openj9-omr/blob/ibm_sdk/port/linux/omrvmem.c#L251-L279
The API code reads from /sys/devices/system/node, looking for node<num> (i.e. node0, node1, etc) sub-directories. Inside these directories there should be meminfo files which should contain a line such as Node 0 MemTotal:       16431076 kB.
The API sets the state of each node based on the global memory policy and if the node has memory.
The test code is https://github.com/eclipse/openj9/blob/master/runtime/tests/port/j9vmemTest.c#L1781-L1810
It looks for nodes which have the PREFERRED or ALLOWED policy. If there are none, the test fails.

Is this intermittent? I see in recent builds running on testc-packet-fedora33-amd-2 or non-dockers passed.
https://ci.adoptopenjdk.net/job/Test_openjdk8_j9_sanity.functional_x86-64_linux_xl/73/
https://ci.adoptopenjdk.net/job/Test_openjdk8_j9_sanity.functional_x86-64_linux_xl/

Is this intermittent? I see in recent builds running on testc-packet-fedora33-amd-2 or non-dockers passed.
https://ci.adoptopenjdk.net/job/Test_openjdk8_j9_sanity.functional_x86-64_linux_xl/73/
https://ci.adoptopenjdk.net/job/Test_openjdk8_j9_sanity.functional_x86-64_linux_xl/

Failing test machine: docker-packet-ubuntu2004-x64-1f1.

but I do not know if its intermittent on that static docker instance.

Failing test machine: docker-packet-ubuntu2004-x64-1f1.

but I do not know if its intermittent on that static docker instance.

I didn't see there is machine docker-packet-ubuntu2004-x64-1f1? I thought all testc* machine is docker instance?

I didn't see there is machine docker-packet-ubuntu2004-x64-1f1? I thought all testc* machine is docker instance?

@sxa - you are the most likely to know the answer to https://github.com/AdoptOpenJDK/openjdk-tests/issues/2143#issuecomment-760476648

@sxa - you are the most likely to know the answer to https://github.com/AdoptOpenJDK/openjdk-tests/issues/2143#issuecomment-760476648

I moved it to another host - replace x64 with amd in the name and you have effectively the same system

I moved it to another host - replace x64 with amd in the name and you have effectively the same system

I've created a pltest binary containing debug and sent it to Stewart to try on the docker instance.

I've created a pltest binary containing debug and sent it to Stewart to try on the docker instance.

On naming  - yes it's a docker container. I've been experimenting with formats so there are several that can indicate it's docker https://github.com/AdoptOpenJDK/openjdk-infrastructure/issues/1809#issuecomment-757143144 ... Open to suggestions/comments on the preferred format that I'll cover them all too later 😊

On naming  - yes it's a docker container. I've been experimenting with formats so there are several that can indicate it's docker https://github.com/AdoptOpenJDK/openjdk-infrastructure/issues/1809#issuecomment-757143144 ... Open to suggestions/comments on the preferred format that I'll cover them all too later 😊

The test is failing because there are 2 or more nodes detected (in /sys/devices/system/node, like node0, node1, etc.) , but the get_mempolicy() API call is failing with EPERM.

The test is failing because there are 2 or more nodes detected (in /sys/devices/system/node, like node0, node1, etc.) , but the get_mempolicy() API call is failing with EPERM.

OK The two AMD EPYC systems I have had slightly different CPUs. NUMA isn't available on the EPYC 7402P but is (and so the test fails) on the EPYC 7401P.
Here is the strace from Peter's standalone pltest from the affected machine:
EPYC7401Pstrace.log.gz
It includes:
get_mempolicy(0x146fdd0, 0x146fd50, 1024, NULL, 0) = -1 EPERM (Operation not permitted)

numactl -s also gives get_mempolicy: Operation not permitted errors.
It can be resolved by starting the container with --privileged and possibly by doing other things with the cgroup controls to restrict the container

OK The two AMD EPYC systems I have had slightly different CPUs. NUMA isn't available on the EPYC 7402P but is (and so the test fails) on the EPYC 7401P.
Here is the strace from Peter's standalone pltest from the affected machine:
EPYC7401Pstrace.log.gz
It includes:
get_mempolicy(0x146fdd0, 0x146fd50, 1024, NULL, 0) = -1 EPERM (Operation not permitted)

numactl -s also gives get_mempolicy: Operation not permitted errors.
It can be resolved by starting the container with --privileged and possibly by doing other things with the cgroup controls to restrict the container

This can also be resolved with --cap-add=sys_nice on the docker run command line, which allows the container access to some control over the CPUs and may be a suitable option for our test environment if this recurs

This can also be resolved with --cap-add=sys_nice on the docker run command line, which allows the container access to some control over the CPUs and may be a suitable option for our test environment if this recurs

I think I only have one NUMA-capable host system (It's a 2.2GHz Intel Xeon Gold 5120). It currently has six docker images on it. I've confirmed (By starting another instance of the Fedora33 docker image with --cap-add=sys_nice and re-running the test) that the test appears to pass on there, so to resolve this I'll need to quiesce them, then shut them all down and restart with that option.

Although there were more containers deployed on the machine, only three have been active in jenkins, therefore I have restarted and tested those: #87 #88 #89 so the outstanding discussion is over whether we want to leave the machines with the sys_nice option, or modify the VM code to trap and deal wiht the situation.


DS-560 | Add option to center campaign page hero content when the fullwidth image layout is selected

READY FOR REVIEW
Summary

Add an option to center the hero content box (currently only left or right aligned) to the Campaign page hero
https://stanford.atlassian.net/browse/DS-560

Review By (Date)

End of the week Mar 15

Criticality

3

Review Tasks
Setup tasks and/or behavior to test

Go to https://deploy-preview-406--adapt-giving.netlify.app/campaign-test/ and check that the box in the hero banner is centered

Check responsive
You can also go to Storyblok giving DEV, go to the campaign-test page, and play with the Hero Content Position option (under Hero content styling group)

Check that the original left and right options are still working as before.

Associated Issues and/or People

DS-560 https://stanford.atlassian.net/browse/DS-560

@sherakama This should be fairly safe - I tested the old options and it shouldn't mess any existing layout up. Is it ok if I merge 🤠 ? Both Kristin and Alexis have looked at it. I'll need to add one option to Storyblok after we push this code to production.

Thanks - I'll merge this into dev and cut a release tomorrow 🤠


Typo in documentation for resource_monitor_grant

Provider Version
0.23.2
Describe the bug
There is a typo in the name of the grant resource for resource monitoring. The documentation says "snowflake_monitor_grant", whereas this should be "snowflake_resource_monitor_grant".
https://registry.terraform.io/providers/chanzuckerberg/snowflake/latest/docs/resources/resource_monitor_grant

Can confirm. You get unsupported resource type error if you follow the example in the doc:
The provider provider.snowflake does not support resource type
"snowflake_monitor_grant".

As noted above, to fix it - replace the resource name as snowflake_resource_monitor_grant

yup, I also met the same error today: The provider chanzuckerberg/snowflake does not support resource type "snowflake_monitor_grant".
Through changing snowflake_monitor_grant to snowflake_resource_monitor_grant can fix the error.

We are closing this issue as part of a cleanup described in announcement. If you believe that the issue is still valid in v0.89.0, please open a new ticket.


Dockerfile

Hello!
I wanted to build the image based on a Dockerfile.
Found this stackowerflow post, but the guy did not open a ticket i think, so i do. https://stackoverflow.com/questions/52618369/fabric8-maven-build-with-external-dockerfile-fails
Running minishift locally, installed from this guide.
https://www.marksei.com/openshift-minishift-widnows/
The sample project.
https://github.com/benike/fabric8-maven-plugin-with-dockerfile
2 commit, first is without Dockerfile, "mvn clean fabric8:deploy" deploys the app and everything works fine, second commit, added dockerfile and the plugin config, build fails.

maven version 3.5.4
minishift version 1.25.0
Best wishes,
Benike

Looks like that the image name was lost when using a Dockerfile. This is definitely a bug which we need to investigate.


initial support for root package BUILD targets

This is the initial support for import of Java targets in the root package (//:*). This is the solution for #404.
This PR does not contain a few things:

tests
the ability to NOT import the root package targets; right now they will always be imported

This feature is time sensitive so I will work those items in a follow up PR.

On further testing this is not sufficient. If you have only non-Java targets in your root build file, the code as it is will try to setup a classpath and will throw up a warning message during import. I will continue to iterate.


Update security-compliance-toolkit-10.md

Updated links and version for Windows 10

Why

Closes #[Issue Number]

Changes

Learn Build status updates of commit a3381b1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows/security/threat-protection/windows-security-configuration-framework/security-compliance-toolkit-10.md
:white_check_mark:Succeeded

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

close/reopen to trigger check

Learn Build status updates of commit a3381b1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

windows/security/threat-protection/windows-security-configuration-framework/security-compliance-toolkit-10.md
:white_check_mark:Succeeded

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


Update the generic aarch64 logo with a smaller one

Change-type: minor
Signed-off-by: Stevche Radevski<EMAIL_ADDRESS>

@balena-ci I self-certify!

@balena-ci rebase


Unable to install Xcode. Xcode.xip is damaged and can't be expanded.

Describe the bug
The archive "Xcode-13.3.1+13E500a.xip" is damaged and can't be expanded.
Screenshots

Version

OS:  12.3.1

I reinstalled the operating system and xcodes, but I still get this error. How do I troubleshoot this problem?

Hi @fandiluo
If you browse to /users/%username%/Library/Application Support/com.robotsandpencils.XcodesApp you'll see the xip file there. So a couple of questions on that

Is it the regular size (something like 12 GB)?
if you double click it, does it give you an error?

If it's a small size, can you delete it, make sure you are logged into your Apple account on Xcodes and try again?
If it gives you an error while expanding, it might give you the better error.
Thanks. Let me know

Is it the regular size (something like 12 GB)?
Yes, I have confirmed it. (Xcode 13.3 ~= 10.09 GB)

if you double click it, does it give you an error?
After I clicked on it, I got the same error

I'm sure I'm logged in...
I have compared the file sizes downloaded from the official site are the same.
I also tried using safari browser to download from the official site. I got the same error when I manually extracted the files.
I don't think it's a problem with XcodesApp, but I can't find a way to fix it.
Thanks for your help!  I hope we can find a solution 👍

@fandiluo curious if you have enough space available on the Mac? It's strange that even downloading straight from the website through safari gives you the same error.

It's a hardware problem.
The fact is that the memory on the motherboard is broken, but the computer is still working.
After replacing the motherboard, it works fine.
Thank you for your help!


IE issue: Jumpy scrolling in IE

I confirmed this in the very latest IE too.
Sorry to IE users. This is a bug and there'll be some patches for this issue.
#56 and #118 are redirected to this issue.
Any contribution from anyone will be welcomed.
Thank you.

any news on this issue? this is an awesome plugin but i have to get it working on IE 11...

Hi, I stopped looking for a solution.
It is a known glitch in internet explorer ... the solution lies in
modifying the html structure which breaks with the philosophy of the
scrollbar.
I switched to http://manos.malihu.gr/jquery-custom-content-scroller
since my current project is nearing completion and Internet Explorer is
not to be ignored for the target audience.
On 2015-01-13 15:55, doronsever wrote:

any news on this issue? this is an awesome plugin but i have to get it working on IE 11...
--
Reply to this email directly or view it on GitHub [1].

Links:
[1]
https://github.com/noraesae/perfect-scrollbar/issues/160#issuecomment-69755772

Hi,
I have used perfect scrollbar in my kendo grid content on both axis. It is appearing fine but its flickering while scrolling. It seems like there is some delay between scrolling and updating the scrollbars positions, causing a jumpy effect.
Please reply.
Thanks

Hiya,
I'm really sorry for the inconvenience here. Because of my shortage of environment and time, the process hasn't be done quickly so far. I'll try to do it asap. Any help will be really appreciated.
Cheers,

In case it is of any help https://www.modern.ie/en-us/virtualization-tools#downloads

Thanks for @larvanitis's suggestion, I installed IE VM. Now this issue is the highest priority, and I'm working on it. It's kinda tricky and I'm not sure if I can fix it very quickly, but I'll do my best.
Cheers guys!

Okay guys, I narrowed down the reason. Please refer to the following fiddle.
http://jsfiddle.net/js5hwjjt/
As you can see in the script, we change scrollTop and top properties at the same time. It means, the red square shouldn't blink, because both properties are updated in the same event cycle. As expected, in many major browsers such as Chrome, Safari or FF, it doesn't blink.
But well, in IE, it blinks, which eventually means that IE doesn't update the window completely during a JS context. It is nothing but a wrong behaviour of the browser itself.
Anyway, to fix the issue, we should modify the whole update logic of the plugin, as IE is totally broken in such a simple example. I'm sorry to frustrate you guys, but it may take longer than I thought it would.
Sorry 😂

+1 This is a major blocker for it to be used in production, otherwise everything works very nice.

I've been playing around a bit. What seems to be the issue is that you are changing the scroll top, and then changing the styling. I have no idea how IE works, but I guess it performs the redrawing when scroll top changes, and freezes the rendering until that has finished, before applying other style changes.
A solution I found is simply changing the order. First change the top styling, afterwards change the scrollTop: http://jsfiddle.net/DanielApt/uc8defz0/
Secondly I briefly explored using CSS transform, as they use the GPU, which could address the repainting. I tried that here, but actually there's a slight shaking (not blinking) effect. http://jsfiddle.net/DanielApt/jpcqpvg9/
I think therefore the first option works better, and is less big of a change. I have only tested the jsfiddles with IE9, and I'm not sure if this works when applied to plugin itself.

Just tested this in the plugin itself. Basically I called updateGeometry() before changing the scrolltop.
It seems to slightly improve the behaviour in IE (especially in IE9). I'm not seeing as much flashing, but when scrolling it still makes large jumps when scrolling.

I have a suspicion that the jumping behaviour is a performance issue in IE, due to the many reads and writes.
Every time the user scrolls we read the scrollTop which causes a browser repaint. Afterwards we change the layout, which again calls a repaint.
This might be a useful resource to tackling the issue http://www.html5rocks.com/en/tutorials/speed/animations/. It mentions using requestAnimationFrame, which sadly would not address IE9, but it could address IE10 and IE11.
Also in general the above article has a few valuable lessons, and it's mostly based around scrolling performance.

I've had the chance to spend a bit more time on this. The problem is actually two-fold:

All scrolling causes flickering of bars, especially when a large amount is scrolled.
Mousewheel scrolling is in large jumps.

I haven't yet pinpointed the cause of issue no.1, but I do know why issue no. 2 is happening.
Each browser exposes its mousewheel scroll delta in a different way. IE's scroll delta will always be 120 or -120. What changes is how often it fires, not the value of the scroll delta itself. We'd need to normalise the scroll delta to get a more consistent scroll and smoother experience. Somebody has attempted to normalise the scroll delta in this jsbin, and a brief test showed it scrolling smoothly in IE11.
I think Issue 1 is more important to address, as this affects more than just mousewheel scrolling, and is more noticeable.

Ok, so here's a solution for Issue 1: don't position the scrollbar inside the element.
That would mean that—gasp—we'd use fixed positioning to address it. I've only been testing it with mousewheel, but it's looking promising so far.
@noraesae have you in the past explored using fixed positioning? What were your reasons for doing it / not doing it?

Actually I've once thought about it. But what if the container moves out of
the display? Because it's fixed position, the scrollbar will remain in the
same position. So I thought it wasn't a good solution and abandoned it.
The other thought is, as you said, remove the scrollbars from the container
and append them just next to it, but use the other positionings to place
them in the same position as they currently display.
Anyway, it looks quite obvious that to fix the IE issue, we need to rethink
how the scrollbar works :(
On Saturday, April 11, 2015, DanielApt<EMAIL_ADDRESS>wrote:

Ok, so here's a solution for Issue 1: don't position the scrollbar
inside the element.
That would mean that—gasp—we'd use fixed positioning to address it.
I've only been testing it with mousewheel, but it's looking promising so
far.
@noraesae https://github.com/noraesae have you in the past explored
using fixed positioning? What were your reasons for doing it / not doing it?
—
Reply to this email directly or view it on GitHub
https://github.com/noraesae/perfect-scrollbar/issues/160#issuecomment-91593570
.

At least there's some good news then… I've got it working with fixed positioning, and when the browser scrolls it repositions them. You can check it out on my fork https://github.com/DanielApt/perfect-scrollbar/tree/issue-1-fix

Wow, it looks promising. I'll definitely try it, but I may take a rest today as it's 1.30am here :crescent_moon:
Great work!

I've just tested and it looks like the best idea to resolve this issue. We may also be able to make the logic even simpler using the rect information.

It works fine, until transforms are used. The use of getBoundingClientRect() does not take transform in consideration. Many people use translate3d(0,0,0) to enable GPU rendering, but that breaks the scrollbars.
Also because the scrollbars are now in a sense “not attached” to their element anymore they sort of move-freely in the z-index space. This means that when you hover over a .ps-container you'll see many positioned elements flicker. This is because the usage of opacity forces it to be placed in a new z-index (discussion) (example).
In many basic projects it works fine, but the fixed positioning option does not play nicely in big scenarios. I would prefer to use jScrollPane's approach, where they wrap the content in a container.
What I suggest is the following

    Lorem ipsum dolor sit amet...

after Ps.initialize()

        Lorem ipsum dolor sit amet...

Just finished quite a bit of work, where the content is moved around in its own container. Still need to work on properly getting RtL and opposite side scrollbars to work. First test in IE9 show it works, and we're not seeing any flickering.
https://github.com/DanielApt/perfect-scrollbar/commits/solution-2
Will do some more testing and dev work tomorrow hopefully.

I've actually noticed the solution before, but I really didn't want to make one more layer, in this case ps-content. The reason was that it modifies the original DOM. However, I guess now it's time to move on.
I'll merge some of your patches into a dev branch so that you can rebase the branch and work from there.

BTW, I've merged .editorconfig. Thanks!

No worries, in that case we stick with the fixed position, we'll just have to warn about using transforms on the element or any of its parents.
Also I'll find a fix for the opacity flicker, probably by using rgba() instead of opacity.

PS: Just realised, there could also be a hybrid of the offered ideas:
We could move content in to .ps-content and adjust that elements scroll top. Then all positioning is still relative to the actual element, and we're still using scrollTop.

@noraesae I would consider the solution using the modified DOM. I know its not at technically beautiful buts its practical and does the job. I would not be worried about the styling issue. Thats sort of thins happens ALL THE TIME in JS project where templating engines require extra markup. Also, awesome work @DanielApt for taking the time to look into this :) #2cents

@andri, DOM modifying is not so practical – visualization would change after scrollbar activation (consider all the existing projects, clean projects and projects with scrollbar selection option) and behaviour would change as well (event selectors would change). I appreciate Jun's will to find out a better solution.

@zomp, yeah I guess its hard to go that route this late in the game.

Guys... there is any progress at this issue?

Not from my side… haven't had the chance to look further in to it. Not sure if @noraesae has had the chance to look in to it.
Imho they're two options:

Modify the dom and put the content in a container, and scroll that.
Find a solution to IE's scrolltop changing and the scrollbar's positioning happening in two paints instead of one.

The usage of fixed positioning doesn't work when we put it in product.
Option 1 works, but the performance goes downhill.
Option 2 would be nicer, and it respects the core of the library, but I've simply not found any solution to address this.

Modifying the dom is not a good idea IMO. It doesn't play well with a lot of things. In our project, perfectScroll is actually the only scroll we can use because it doesn't touch the DOM. All the others just break the layout in a fashion that can't be fixed.

Just a small note, that I don't see this problem in Microsoft Edge on Windows 10

Until there's an official fix, I'll be more than happy to use the forked version by @DanielApt.
Daniel, is there a compiled .js anywhere :-) ?

@martinstender I had two approaches, both with their own issues. Which one did you want to try?
Fork 1 uses fixed positioning. Buggy when elements use css transforms.
Fork 2 wraps content in .ps-container. Performance goes down hill.
The forks won't be able to have the compiled js files, as the /dist directory will be ignored. The easiest way to do it is to download the fork and run gulp

Great, thank you - I'll give #2 a shot and see how it performs :-)
(Got the gulp working ... was new to that :-)

Since I really like perfect-scrollbar and all others (tried about 5 of them) have many issues, I just detected IE and went with the perfect-scrollbar only on browsers that are not IE and only desktop (device.js) otherwise the overflow auto takes over.  IE just won't be as pretty, but it won't be jumpy.
/**
 * detect IE
 * returns version of IE or false, if browser is not Internet Explorer
 */
function detectIE() {
  var ua = window.navigator.userAgent;

  // test values
  // IE 10
  //ua = 'Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; Trident/6.0)';
  // IE 11
  //ua = 'Mozilla/5.0 (Windows NT 6.3; Trident/7.0; rv:11.0) like Gecko';
  // IE 12 / Spartan
  //ua = 'Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.71 Safari/537.36 Edge/12.0';

  var msie = ua.indexOf('MSIE ');
  if (msie > 0) {
    // IE 10 or older => return version number
    return parseInt(ua.substring(msie + 5, ua.indexOf('.', msie)), 10);
  }

  var trident = ua.indexOf('Trident/');
  if (trident > 0) {
    // IE 11 => return version number
    var rv = ua.indexOf('rv:');
    return parseInt(ua.substring(rv + 3, ua.indexOf('.', rv)), 10);
  }

  var edge = ua.indexOf('Edge/');
  if (edge > 0) {
    // IE 12 => return version number
    return parseInt(ua.substring(edge + 5, ua.indexOf('.', edge)), 10);
  }

	// other browser
  return false;
}

if ($('html').hasClass('desktop') && !$('html').hasClass('msie')) {
  /* perfect-scrollbar v0.6.5 */
  !function ... SCRIPT GOES HERE minified

  $(".selector").perfectScrollbar({ });
  $(".selector").perfectScrollbar('update');
   $('.selector').css('overflow', 'hidden');

} // end if desktop and not IE any version

CSS
.selector {
   overflow-y: scroll;
   -webkit-overflow-scrolling: touch;
  -ms-overflow-style: -ms-autohiding-scrollbar;
   -ms-overflow-style: scrollbar;
}

html.desktop .selector {
   overflow:auto;
  -ms-overflow-style: scrollbar;
}

Might be worth looking at gemini scrollbar as they use a similar approach, and change the scrollTop instead of a relative positioning or transform hack.
Testing in IE9 I don't see the jumpy behaviour.

I'd like to conclude this issue as it's resolved in Edge. I guess the answers suggested in this thread are helpful to address the issue, and users can even use other plugins for old IEs.
I'll label this issue wontfix. However, you can freely discuss further and suggest other solutions.

One thing that I noticed and I remember fixing some issues on IE11 was that the css has the IE10 friendly:
-ms-touch-action: none;

But not the unprefixed version supported in IE11:
touch-action: none;


Server parameters passed on command line overwrite saved settings

Create a saved connection and give it a descriptive name like "mynamedconnection", connected to server "myserver" with integrated auth.
Run "azuredatastudio -S myserver -E"
ADS will open a new query editor for the saved connection without creating a whole new connection, but the the descriptive name will get deleted. So the tree will show "myserver,  (Windows Authentication)" instead of the name.
We should preserve the existing profile and not overwrite it.

This problem is rather complex. There is a disconnect among connectIfNotConnected, this._connectionStatusManager, and this._connectionStore in ConnectionManagementService.
connectIfNotConnected only looks at active connections to potentially reuse it, ignoring any already-saved profiles:
if (this._connectionStatusManager.isConnected(ownerUri)) {
resolve(this._connectionStatusManager.getOriginalOwnerUri(ownerUri));
} else {
Also, command line service doesn't assign any group id, so the ownerUri would never match.
I think the fix would be to have command line service query the connection store to find a matching profile and use it.


black[jupyter] in pre-commit

Adds black[jupyter] to pre-commit.
pre-commit run --all-files passes both before and after this PR

Neat, thanks!


Too many gulp listeners

If you run gulp watch and go developing; after a while you'll notice a terminal warning:
node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
Does someone have an idea which gulp task causes this or how to fix it?

closed with #18


Invalid entry in Gradle template (/build/)

The Gradle template ignores '/build/', but that does not cover build directories in modules.  Could it be replaced with 'build/' ?

Thank you for this report.
All of the available template come from the 3rd party repository provided by GitHub and are bundled with the plugin. It is not possible to modify them here with this plugin, however you can create your own templates with rules that you want.

I'll take it upstream, then.  Thanks!


LISDF Output Spec

We should define a proper schema somewhere.
In general, using dataclasses a lot. Had to do some hacks in some places to get things to work nicely. I would like to move the validation code elsewhere as it is getting big but won't bother for now.
We now support:

Serializing to JSON/YAML
Deserializing from JSON/YAML
Lots of helper functions in the models (especially JointSpacePath)

It is the simulator's job to take these Python objects and actually execute the plan. We just provide as much simple functionality as we can

Thoroughly tested, near 100% coverage for the lisdf.planner_output module (yay! 🎉 )

In the future, we need to decide what to do with versioning. It doesn't really matter for now. Probably would do with a refactor of validation code as well and parsing.

Fantastic PR! I left some comments which we should address in some way but I think this is a good start! One other note I might suggest is giving this directory a README.md so that people know where to start to learn about the output spec/can easily find the examples. (That can come in a small PR after this one though - I think the sooner this gets merged in the better).

Thanks! For the output spec ideally we might want to autogenerate it and have some formal spec somewhere. I'll give it a think for next PR.


No Paste Or Selection Support

I could neither paste anything to the console, nor select anything to copy.

Which console are you using? And does it work for other applications (e.g. dir)?

@WouterTinus Windows Command Prompt of course.
In cmd, I can surly copy and paste, but if I entered win-acme, I can't anymore.


Crashes after image selected on Cyanogenmod with cropping

On Cyanogen 12.1.1, Android 5.1.1, after selecting a picture from gallery or taking picture with camera, the app crashes.
My config:
export const uiPicker = {
	title: 'Choose a Picture', // specify null or empty string to remove the title
	cancelButtonTitle: 'Cancel',
	takePhotoButtonTitle: 'Take Photo...', // specify null or empty string to remove this button
	chooseFromLibraryButtonTitle: 'Choose from Library...', // specify null or empty string to remove this button
	cameraType: 'back', // 'front' or 'back'
	mediaType: 'photo', // 'photo' or 'video'
	maxWidth: 800, // photos only
	maxHeight: 800, // photos only
	aspectX: 1, // aspectX:aspectY, the cropping image's ratio of width to height
	aspectY: 1, // aspectX:aspectY, the cropping image's ratio of width to height
	quality: 0.2, // photos only
	angle: 0, // photos only
	allowsEditing: false, // Built in functionality to resize/reposition the image
	noData: false, // photos only - disables the base64 `data` field from being generated (greatly improves performance on large photos)
	storageOptions: { // if this key is provided, the image will get saved in the documents/pictures directory (rather than a temporary directory)
		skipBackup: true, // image will NOT be backed up to icloud
		path: 'images' // will save image at /Documents/images rather than the root
	}
};

The log message in adb:
D/QCameraParameters(  241): int qcamera::QCameraParameters::setAutoRotate(const qcamera::QCameraParameters&) set auto rotate: 0
E/mm-camera(  255): mct_pipeline_process_set:command=800000e
D/QCameraParameters(  241): int32_t qcamera::QCameraParameters::setNumOfSnapshot(): nBurstNum = 1, nExpnum = 1
D/LBSSystemMonitorService(  768): handleMessage what - 4
D/Wiper_jni(  768): Send Network Location.
W/JsonSuggestProvider( 2509): ext: null, mimeType: null, handles: false
D/ApplicationSuggestionService( 2509): handles? false
I/ActivityManager(  768): START u0 {act=com.android.camera.action.CROP dat=file:///data/data/com.cyngn.cameranext/files/crop-temp (has extras)} from uid 10038 on display 0
D/AndroidRuntime(24134): Shutting down VM
E/AndroidRuntime(24134): FATAL EXCEPTION: main
E/AndroidRuntime(24134): Process: com.cyngn.cameranext, PID: 24134
E/AndroidRuntime(24134): android.content.ActivityNotFoundException: No Activity found to handle Intent { act=com.android.camera.action.CROP dat=file:///data/data/com.cyngn.cameranext/files/crop-temp (has extras) }
E/AndroidRuntime(24134):        at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1781)
E/AndroidRuntime(24134):        at android.app.Instrumentation.execStartActivity(Instrumentation.java:1501)
E/AndroidRuntime(24134):        at android.app.Activity.startActivityForResult(Activity.java:3745)
E/AndroidRuntime(24134):        at android.app.Activity.startActivityForResult(Activity.java:3706)
E/AndroidRuntime(24134):        at com.android.camera.bi.do(SourceFile:1934)
E/AndroidRuntime(24134):        at com.android.camera.cb.onClick(SourceFile:456)
E/AndroidRuntime(24134):        at android.view.View.performClick(View.java:4789)
E/AndroidRuntime(24134):        at com.android.camera.ShutterButton.performClick(SourceFile:149)
E/AndroidRuntime(24134):        at android.view.View$PerformClick.run(View.java:19881)
E/AndroidRuntime(24134):        at android.os.Handler.handleCallback(Handler.java:739)
E/AndroidRuntime(24134):        at android.os.Handler.dispatchMessage(Handler.java:95)
E/AndroidRuntime(24134):        at android.os.Looper.loop(Looper.java:135)
E/AndroidRuntime(24134):        at android.app.ActivityThread.main(ActivityThread.java:5294)
E/AndroidRuntime(24134):        at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(24134):        at java.lang.reflect.Method.invoke(Method.java:372)
E/AndroidRuntime(24134):        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:904)
E/AndroidRuntime(24134):        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:699)

However, if I disable aspectX and aspectY, it works perfectly.
So obviously the feature doesn't exist in cyanogen or it has another name.
Maybe there could be a check in the app, if it is available or not.
A crash is a little bit hard.
Thanks!

Hello @timsuchanek
Are you using the last version of the package ?
And since you set allowsEditing: false there should be no crop and aspectX - aspectY are not used in this case

Hi @yfuks yes, I'm using 0.18.3.

Yes, it always happens on Android. I'm using the 0.18.5. Everything seems OK when I change
"allowsEditing" to false or it shows the same error as tims.
My suggestion is to separate the activity of capturing photo and cropping in the code. I hope this helps...

Hi guys ! Sorry for the lack of response :yellow_heart:

My suggestion is to separate the activity of capturing photo and cropping in the code.

It's not a good solution :). An intent alone to handle crop com.android.camera.action.CROP is badly supported on Android.

Maybe there could be a check in the app, if it is available or not.
A crash is a little bit hard.

Agree. Currently we check if we can create the activity or we print the above stack error (and it crash..). Will try to return the error to react-native and in the best case continue without cropping. Working on it ! :)

I feel like you have an old implementation of the module since com.android.camera.action.CROP isn't used anymore.
Anyway i push some robustness code that will return the error to react-native if the activity don't exist. Tell me if that fix the crash for you.

No response, i close


Removed LDAP Models that are no longer used

Removed LDAP Models that are no longer used

LdapDomain
LdapGroup
LdapManagement
LdapRegion
LdapServer
LdapUser

Requires related Schema and UI-Classic PRs.

[x] Schema   https://github.com/ManageIQ/manageiq-schema/pull/162
[x] UI-Classic  https://github.com/ManageIQ/manageiq-ui-classic/pull/3353

I think we can merge this, but it may break manageiq-ui-classic.  I have no idea how this works and it looks like it's a hash indexed by the model, but ¯\_(ツ)_/¯

Also, this PR doesn't remove the factories that the UI is using.


PayPal isn't making any transaction

I created Xamarin forms app using your provided code, its working perfect but I couldn't make any transaction. I get response from server that transaction is successful but when I check on my paypal account no any transaction happens.

You need to provide more insighrs
Plugin version
Device/simulator Os & version
Enviroment
Crash or error logs
Demo code

Please double check that you have correctly setup the enviroment and also api key on that code seems that you’re using no network and a no valid api key

You are right Sir.
I need to setup paypal rest api.
Thanks for your help

Hi AlejandroRuiz
sorry to bother you again. Ive created paypal rest api and got my live account creditionals but still I couldnt make a transaction. It does connects to paypal. Ive spoken to paypal they said this issue is from my side.
what changes Ive made I will send you now.
var config = new PayPalConfiguration(PayPalEnvironment.Production, "client id")

Just go to your Rest Api Apps and select the enviroment that you want then copy your ClientId string and pass it as parameter in the PayPalConfiguration class that all

thanks alot sir I am doing exactly same. But it won't let my transaction going through.
I text you my error. "There was a problem setting up this payment. Please visit the paypal website to check your  account"
I am using live account creditionals of rest api.


Actors "placeholder"?

It is difficult to identify who the actors are. I understand we can use User;uuid, etc., but still, it does not tell which user.

I was wondering if it would be interesting to allow configuring an actor_display_placeholder so that we can show the name instead or any other combination that can be useful when listing actors.
flipper.actor_display_placeholder = proc { |flipper_id| User.find(flipper_id).name }

Agreed. This would be nice. Closing as duplicate of #389. But I'd be open to a PR.
Instead of a one by one, which would lead to an N+1 loading issue when showing actors, I'd do something that is bulk like how we load the descriptions for features.
Configuration:
https://github.com/jnunemaker/flipper/blob/7727ca686462864e123ac27c60c3bc86f48546f9/lib/flipper/ui/configuration.rb#L74
Example usage:
https://github.com/jnunemaker/flipper/blob/7727ca686462864e123ac27c60c3bc86f48546f9/examples/ui/basic.ru#L30-L41
How the UI action loads them in bulk:
https://github.com/jnunemaker/flipper/blob/7727ca686462864e123ac27c60c3bc86f48546f9/lib/flipper/ui/actions/features.rb#L14-L18
I'd maybe call it actor_names_source to match descriptions_source. I'd have the method take an array of flipper_id's and return a hash of flipper_id => String name. Then the UI can use the name instead of flipper_id or show both (e.g. John Nunemaker (User;1)).

www.flippercloud.io allows defining a name for each actor and I always use Cloud so that's probably why I haven't gotten to this yet.

@jnunemaker thank you for the quick reply!

Instead of a one by one, which would lead to an N+1

For my use case, I'm not too worried about N+1, given I usually have just a few actors - and I don't open the page listing actors that often. But I understand some users may have many.
What I like about the proc is that we can leave it up for users to implement in the way they want.
For example, with the descriptors, it is key->value (string->string), whereas, with a proc, I can have more flexibility:
flipper.actor_display_placeholder = proc do |flipper_id|
   user = User.find(flipper_id).name # or user = USER_DESCRIPTORS[user.id]

   "#{user.name}-this-and-that-#{user.org.name}"
end

I can't merge anything that is N+1. Might not affect you but will affect others. The bulk version of the proc that I'm proposing is the same thing, you just make it work for an array.
# bulk version that does the same thing and never ends up in n+1;
# if you have actors other than User, you could group on the constant (User, Org, etc.) and do lookups for others.
flipper.actor_names_source = proc do |flipper_ids|
  # get the active record ids from flipper ids
  ids = flipper_ids.map { |flipper_id| flipper_id.split(';', 2).last }

  # find the users
  users = User.where(id: ids)

  # return hash of flipper_id => custom name
  users.inject({}) do |hash, user|
    hash[user.flipper_id] = "#{user.name}-this-and-that-#{user.org.name}"
    hash
  end
end

That's not really N+1. Everyone can implement that differently. It is just a callback for formatting rows. But I hear you.
I misread your initial comment, I thought you were suggesting something key-value, and that wouldn't do it.
The bulk version would work for me. It's solid.

Merged https://github.com/flippercloud/flipper/pull/737 which handles this. Should be released soon.


[Bug]: Shouldn't frontmatter.title override extracted H1?

Version
System:
    OS: macOS 14.0
    CPU: (12) arm64 Apple M2 Max
    Memory: 176.88 MB / 64.00 GB
    Shell: 5.9 - /bin/zsh
  Browsers:
    Chrome: 122.0.6261.94
    Safari: 17.0

Details
According to https://rspress.dev/api/config/config-frontmatter.html#front-matter-config:
By default, the page's h1 heading will be used as the title of the HTML document. But if you want to use a different title, you can use Front Matter to specify the title of the page.

I assumed this meant the frontmatter.title, when given, should always be chosen over h1 heading, but the h1 heading would be chosen in the sidebar.
By inspecting the source code, it seems like this is the reason:
// plugin-auto-nav-sidebar

export async function extractH1Title(...) {
  ...
  const match = content.match(h1RegExp);

  if (!match) {
    // only fallback to frontmatter.title when h1 is not found
    const { frontmatter } = loadFrontMatter(content, filePath, rootDir);
    return frontmatter.title || fileNameWithoutExt;
  } else {
    return match[1] || fileNameWithoutExt;
  }
}

See: https://github.com/web-infra-dev/rspress/blob/4fd420d599adaaa76645e6ec3fbeb483ffae74a2/packages/plugin-auto-nav-sidebar/src/utils.ts#L41-L46
Shall we change this?
Reproduce link
https://applink.larksuite.com/client/message/link/open?token=AmRKLqSagAAFZedZ1TCAAAY%3D
Reproduce Steps
For instance, when given:
---
title: <canvas>
---

# `<canvas>`

I will have
`<canvas>`

rather than
<canvas>

rendered in the sidebar.

Thanks for the detailed feedback. Now the pr #711 has corrected the priority of frontmatter.title.
Example:
---
title: <canvas>
---

# `<canvas>`

Currently the code-formatted h1 rendered in sidenav has supported monospaced fonts😄

@sanyuan0704 BEAUTIFUL! thanks for the work ;)


Uncaught ModuleNotFoundError in  line 1004

Aider version: 0.54.12
Python version: 3.10.12
Platform: Linux-6.9.3-76060903-generic-x86_64-with-glibc2.35
Python implementation: CPython
Virtual environment: No
OS: Linux 6.9.3-76060903-generic (64bit)
Git version: git version 2.34.1
An uncaught exception occurred:
Traceback (most recent call last):
  File "aider", line 8, in <module>
    sys.exit(main())
  File "main.py", line 498, in main
    main_model = models.Model(args.model, weak_model=args.weak_model)
  File "models.py", line 486, in __init__
    res = self.validate_environment()
  File "models.py", line 660, in validate_environment
    res = litellm.validate_environment(model)
  File "llm.py", line 23, in __getattr__
    self._load_litellm()
  File "llm.py", line 30, in _load_litellm
    self._lazy_module = importlib.import_module("litellm")
  File "__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1004, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'litellm'

Thanks for trying aider and filing this issue.
How did you install aider? What environment are you using?
It looks like you don't have the correct set of dependencies installed.

Its sorted. I had broken dependencies.
Thanks.
On Fri, Sep 6 2024 at 06:16:15 -0700, paul-gauthier
@.***> wrote:

Thanks for trying aider and filing this issue.
How did you install aider? What environment are you using?
It looks like you don't have the correct set of dependencies
installed.
—
Reply to this email directly, view it on GitHub
https://github.com/paul-gauthier/aider/issues/1399#issuecomment-2334034584,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BCPY7E3VDOAYD54FFAW4CPLZVGTJ7AVCNFSM6AAAAABNYSE6LSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZUGAZTINJYGQ.
You are receiving this because you authored the thread.Message ID:
@.***>

I'm going to close this issue for now, but feel free to add a comment here and I will re-open or file a new issue any time.


feat: support summary output for route/cluster/listener in hgctl gateway-config command (#995)

Ⅰ. Describe what this PR did
Support summary output for route/cluster/listener in hgctl gateway-config command
Ⅱ. Does this pull request fix one issue?

fixes #995
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

cc @2456868764


Allow different inputs choice to pad to bucket boundary in tf.data.Dataset.bucket_by_sequence_length

Please make sure that this is a feature request. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:feature_template
System information

TensorFlow version (you are using): 2.8.0
Are you willing to contribute it (Yes/No): No

Describe the feature and the current behavior/state.
tf.data.Dataset().bucket_by_sequence_length() has boolean input variable pad_to_bucket_boundary. However, if one wants to pad multiple sequences (e.g. audio, length=1000) and labels (e.g. 10 categories) then there is no capability to pad one by bucket_boundary and the other by maximum length in batch.
In my instance, I'd like to pad the audio to the maximum length in the batch, but the label by buckets.
Will this change the current api? How?
Boolean pad_to_bucket_boundary can also receive a dictionary with string key and boolean value.
Who will benefit with this feature?
Users who want to avoid unnecessary sparsity conversions/padding
Any Other info.

If there's a way to achieve the above via multiple operations that would be great to know.

Hi,
Thank you for opening this issue. Since this issue has been open for a long time, the code/debug information for this issue may not be relevant with the current state of the code base.
The Tensorflow team is constantly improving the framework by fixing bugs and adding new features. We suggest you try the latest TensorFlow version with the latest compatible hardware configuration which could potentially resolve the issue. If you are still facing the issue, please create a new GitHub issue with your latest findings, with all the debugging information which could help us investigate.
Please follow the release notes to stay up to date with the latest developments which are happening in the Tensorflow space.


Hops not used because of unset in get method.

Calling getMessagesFromContainer() results in clearing the messages in the session, regarding the hops, defined when adding a message.

Please provide unit tests for this; right now I still don't understand what the expectations are. Unit tests will clarify that.
Additionally, please look at the travis-ci output, and run php-cs-fixer; you have CS issues currently.

When hops are used, the key gets expired on the first request, no matter what number is used for the hops.

@riznmage Please write tests for that behavior, then.
Tests help us:

understand the expectations properly.
document the expectations for others.
ensure that future changes do not break those expectations.

The Travis CI build failed because of other tests, not related to the issue. You can check https://travis-ci.org/zendframework/zend-mvc/jobs/66870601
A test cannot be written, since a second request is needed to be made to test this. Basically, the expected behavior is this:

In a controller action, a message is set:
$this->flashMessenger()->addMessage("Message text", FlashMessenger::NAMESPACE_ERROR, 2);
This message uses 2 hops, which means that it will be kept for 2 more requests in the session.

A redirect is made from the same action:
return $this->redirect()->toRoute("someRouteName");
On the redirected page, the message is available.

Then a new request is made either by the user, or via AJAX/ESI. Judging by the value of the hops (2), the message should be available on this page, too, but it isn't.

@riznmage Travis-CI it's failing because the PR does not follow the CS guidelines
https://travis-ci.org/zendframework/zend-mvc/jobs/66870601#L433
Execute ./vendor/bin/php-cs-fixer fix -v in the project root

A test cannot be written, since a second request is needed to be made to test this.

You can mock the session manager in order to emulate multiple requests.

@riznmage Your last commit is erroneus. You have to execute the command in your local machine and don't modify travis configuration which is out of the scope.

@weierophinney I haven't writter a unit test so far. I'm just reporting a bug. Read https://github.com/zendframework/zend-mvc/pull/9#issuecomment-112082949 thoroughly and you will get what I'm talking about.

@riznmage Please review my earlier comment. I'm asking you to write a test so that we can understand the behavior expected and ensure that once corrected it stays corrected later.
If you need assistance writing the unit test, you can jump into the #zftalk.dev channel on Freenode IRC and ask.

Execute ./vendor/bin/php-cs-fixer fix -v in the project root
How exactly? @Maks3w

Okay.. it seems to be a mistake that I made. I was using getMessages() instead of getCurrentMessages(). Can you explain me what is the difference between these two? Why is getMessages() clearing the messages from the session container?

getMessages() is the one to use when accessing messages set in the previous request (which is the general reason for using FlashMessenger). getCurrentMessages() is the method to use when you want access to messages set during the current request.
getMessages() will clear the container of any expired messages, so that the next invocation will only retrieve those that still have request hops available (which is what the hops setting is for); that's likely the behavior you are seeing.


chore: release main

:rocket: Automated Release
dev-dependencies-client: 7.0.1
7.0.1 (2024-12-11)
Bug Fixes

bump non-breaking dependencies to latest (#477) (ffd14e9)

Dependencies

The following workspace dependencies were updated

dependencies

@versini/dev-dependencies-common bumped to 5.0.1

dev-dependencies-common: 5.0.1
5.0.1 (2024-12-11)
Bug Fixes

bump non-breaking dependencies to latest (#477) (ffd14e9)
bump non-breaking dependencies to latest (#479) (0f8723c)

dev-dependencies-server: 6.0.1
6.0.1 (2024-12-11)
Bug Fixes

bump non-breaking dependencies to latest (#477) (ffd14e9)

Dependencies

The following workspace dependencies were updated

dependencies

@versini/dev-dependencies-common bumped to 5.0.1

dev-dependencies-types: 2.0.2
2.0.2 (2024-12-11)
Bug Fixes

bump non-breaking dependencies to latest (#477) (ffd14e9)
bump non-breaking dependencies to latest (#479) (0f8723c)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

dev-dependencies-common-v5.0.1
dev-dependencies-client-v7.0.1
dev-dependencies-server-v6.0.1
dev-dependencies-types-v2.0.2
:sunflower:


[IOTDB-1055] Support data compression type GZIP

Hi, thank you so much for your contribution!
Since this is a new feature for IoTDB, can you please add a design doc on https://cwiki.apache.org/confluence/display/IOTDB/Design+Document?
Or provide a performance test like this (https://cwiki.apache.org/confluence/display/IOTDB/IOTDB-938+Re-implement+Gorilla+encoding+algorithm) to show the advantage of this compression type?

Thank you for your suggestions.
In fact, this is just the implementation of GZIP compression. as IOTDB
support GZIP compression in sql syntax(see issue ), but will run into
problem when store data point to disk.
I will make performance test as soon as possible, thanks your kind review
Haonan<EMAIL_ADDRESS>于2020年12月14日周一 下午3:00写道：

Hi, thank you so much for your contribution!
Since this is a new feature for IoTDB, can you please add a design doc on
https://cwiki.apache.org/confluence/display/IOTDB/Design+Document?
Or provide a performance test like this (
https://cwiki.apache.org/confluence/display/IOTDB/IOTDB-938+Re-implement+Gorilla+encoding+algorithm)
to show the advantage of this compression type?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/iotdb/pull/2264#issuecomment-744219265, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADYQDBCJ5ID5RUUALZ7A2K3SUWZX3ANCNFSM4U2GWZ4A
.