[pcl] build failure

Operating system
Windows 11
Compiler
MSVC vC143, CUDA 12.4
Steps to reproduce the behavior
`./vcpkg install pcl[apps,core,cuda,opengl,openni2,qt,simulation,tools,visualization,vtk]:x64-windows`

Failure logs
Installing 1/9<EMAIL_ADDRESS>Building<EMAIL_ADDRESS>-- Using cached PointCloudLibrary-pcl-pcl-1.14.0.tar.gz.
-- Cleaning sources at C:/vcpkg/buildtrees/pcl/src/pcl-1.14.0-40680cf035.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/vcpkg/downloads/PointCloudLibrary-pcl-pcl-1.14.0.tar.gz
-- Applying patch add-gcc-version-check.patch
-- Applying patch fix-check-sse.patch
-- Applying patch fix-numeric-literals-flag.patch
-- Applying patch install-layout.patch
-- Applying patch install-examples.patch
-- Applying patch fix-clang-cl.patch
-- Applying patch gh-5926-exports.patch
-- Applying patch gh-5947-kinfu.patch
-- Applying patch gh-5985-inline.patch
-- Applying patch io_ply.patch
-- Using source at C:/vcpkg/buildtrees/pcl/src/pcl-1.14.0-40680cf035.clean
-- Found external ninja('1.11.0').
-- Configuring x64-windows
-- Building x64-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message):
Command failed: C:/Users/bazunzhi/scoop/apps/cmake/3.29.2/bin/cmake.exe --build . --config Debug --target install -- -v -j13
Working Directory: C:/vcpkg/buildtrees/pcl/x64-windows-dbg
See logs for more information:
C:\vcpkg\buildtrees\pcl\install-x64-windows-dbg-out.log
Call Stack (most recent call first):
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
ports/pcl/portfile.cmake:80 (vcpkg_cmake_install)
scripts/ports.cmake:175 (include)
Additional context
install-x64-windows-dbg-out.log
this build failure may be caused by the version of CUDA still not supported by pcl.

PCL 1.14.0 does not work with CUDA 12.4 because CUDA 12.4 was released two months after PCL 1.14.0.
On the PCL master branch, this is already fixed: https://github.com/PointCloudLibrary/pcl/commit/ccc4eee90a7242cf0d3c5e1ddb79716eabe4eb8c
You could try the vcpkg option --head to build the current PCL master branch instead, or replace CUDA 12.4 with CUDA 12.3

PCL 1.14.0 does not work with CUDA 12.4 because CUDA 12.4 was released two months after PCL 1.14.0. On the PCL master branch, this is already fixed: PointCloudLibrary/pcl@ccc4eee You could try the vcpkg option --head to build the current PCL master branch instead, or replace CUDA 12.4 with CUDA 12.3

OK,Thanks~


Update setup_pipeline.py

This is a change to lower the compute needed for the demo - NC12 is a large machine and an ask for large resource - therefore lowering to NC6


DOCSP-38371: Remove broken link (#1312)

Merges up https://github.com/mongodb/mongo-php-library/pull/1312

Closing this, as it will require a new PR regardless.


[FLINK-10326] Simplify ZooKeeperSubmittedJobGraphStore#constructor

What is the purpose of the change
Move initialization logic out of the ZooKeeperSubmittedJobGraphStore constructor.
This PR is based on #6681.
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

LGMT 👍


0.8.3 - issues

The bot constantly relaunches the app if you tick the 'farm shifter reward' option in Epic Quest -> First Family -> Twisted World.
This is because this stage doesn't actually have a shifter.
(This stage rewards are overall trash. But that's not your fault).
Thanks

If you've only started this Epic Quest then yes, Twisted World doesn't have a shifter. But upon further Epic Quest completion it will appear in both missions:

Just don't toggle 'farm shifter reward' for now

Thanks!


Not able to import an existing account as first step

Describe the bug
I installed XT on Brave. I tried to import an existing account as first step.
Brave shows an error after i added the passphrase and hit the button.
Expected behavior
Should be able to add an existing account as first step on Brave.
Screenshots

Browser (please complete the following information):

OS:Windows 10
Browser . Brave
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Same on Chrome

Not reproducable

Neither on Chrome, nor on Brave

Do you have any connections open

Ok. I have a theory what happened. I need to assume that you waited for a certain time (like 5 minutes) before you started to import.
Background:
The Manifest Version 3 runs so called service workers, which goes "offline" (being inactive) after a certain time period. When this happens, the service worker disconnects from the Messaging API. So the port being used does not exist anymore....and causing a communication faiilure. I was able to reproduce this on the signumart platform. I waited until the service worker became inactive and tried to sign a transaction, which caused an error then.
Google did an awesome job. Congrats!

I close this as duplicate of #24


Discord authentication is requiring re-authorization each time a user logs into the site

Describe the feature you'd like
We're using Discord as an identity provider and it works well... but for some reason it's prompting everybody (myself included) to re-authorize each time we log into the site fresh. Is there a way to have it only do this the first time or limit it to every 30, 60, etc days? It's not hindering people from getting into the site, it's just becoming increasingly annoying to have to re-authorize each time.
Describe the benefits this would bring to existing BookStack users
This would allow our users to authorize using their Discord account to authenticate only the first time or at the very least, a lesser frequency than "every single time"
Can the goal of this request already be achieved via other means?
Not that I'm aware of.
Have you searched for an existing open/closed issue?

[X] I have searched for existing issues and none cover my fundemental request

How long have you been using BookStack?
0 to 6 months
Additional context
No response

Looks like discord supports a prompt param. From the docs:

prompt controls how the authorization flow handles existing authorizations. If a user has previously authorized your application with the requested scopes and prompt is set to consent, it will request them to reapprove their authorization. If set to none, it will skip the authorization screen and redirect them back to your redirect URI without requesting their authorization.

Digging into this, and by doing a test on my local instance, I can see the library we use recently updated to set prompt=none by default, so this behavior should no longer be an issue on the latest release of BookStack.


Livestreamer and youtube

Hi can livestreamer play a youtube list one after another? For example play this video then when it done play a next one. https://www.youtube.com/watch?v=Dxzcc47LVWs&list=PL6fJmjt84zZiWk6e8mBtjFUU2PCVcO_I6

Youtube Playlists are currently not supported by livestreamer.

A very manual workaround would be to set the player to automatically quit after the vide ends (since it is not a live stream) and just putting the livestreamer commands one after the other...
Or download all of the videos and form a playlist from the local files.
If the usecase was some kind of uninterrupted "a kiosk mode".


Shapes votes as object not array

Fixes #22
Changes proposed in this pull request:

Proposal's votes: [ ] are now delivered as an object in the response data to match other implementations.

Note: we decided to use an array after all, but make entries and not just a root [0] to access all the votes.

Note: we decided to use an array after all, but make entries and not just a root [0] to access all the votes.


typo: compatibile -> compatible

@nschonni : Thanks for your contribution! The author, @CelesteDG, has been notified to review your proposed change.


Space after emoji

Issue
I have some problem with space after emoji. In iTerm2 emoji takes too much space. In RubyMine terminal everything OK. Any suggestions?
Screenshot
iTerm2

RubyMine terminal

Environment
Operating system: macOS
Terminal emulator: iTerm2
ZSH version: 5.3.1
Relevant .zshrc
# If you come from bash you might have to change your $PATH.
export PATH=$HOME/bin:/usr/local/bin:$PATH

# Path to your oh-my-zsh installation.
export ZSH=/Users/mac/.oh-my-zsh

# Set name of the theme to load. Optionally, if you set this to "random"
# it'll load a random theme each time that oh-my-zsh is loaded.
# See https://github.com/robbyrussell/oh-my-zsh/wiki/Themes
ZSH_THEME="spaceship"

# Uncomment the following line to use case-sensitive completion.
# CASE_SENSITIVE="true"

# Uncomment the following line to use hyphen-insensitive completion. Case
# sensitive completion must be off. _ and - will be interchangeable.
# HYPHEN_INSENSITIVE="true"

# Uncomment the following line to disable bi-weekly auto-update checks.
# DISABLE_AUTO_UPDATE="true"

# Uncomment the following line to change how often to auto-update (in days).
# export UPDATE_ZSH_DAYS=13

# Uncomment the following line to disable colors in ls.
# DISABLE_LS_COLORS="true"

# Uncomment the following line to disable auto-setting terminal title.
# DISABLE_AUTO_TITLE="true"

# Uncomment the following line to enable command auto-correction.
# ENABLE_CORRECTION="true"

# Uncomment the following line to display red dots whilst waiting for completion.
# COMPLETION_WAITING_DOTS="true"

# Uncomment the following line if you want to disable marking untracked files
# under VCS as dirty. This makes repository status check for large repositories
# much, much faster.
# DISABLE_UNTRACKED_FILES_DIRTY="true"

# Uncomment the following line if you want to change the command execution time
# stamp shown in the history command output.
# The optional three formats: "mm/dd/yyyy"|"dd.mm.yyyy"|"yyyy-mm-dd"
# HIST_STAMPS="mm/dd/yyyy"

# Would you like to use another custom folder than $ZSH/custom?
# ZSH_CUSTOM=/path/to/new-custom-folder

# Which plugins would you like to load? (plugins can be found in ~/.oh-my-zsh/plugins/*)
# Custom plugins may be added to ~/.oh-my-zsh/custom/plugins/
# Example format: plugins=(rails git textmate ruby lighthouse)
# Add wisely, as too many plugins slow down shell startup.
plugins=(git brew bundler docker gem npm osx rails ruby zsh-autosuggestions)

source $ZSH/oh-my-zsh.sh

# User configuration

# export MANPATH="/usr/local/man:$MANPATH"

# You may need to manually set your language environment
# export LANG=en_US.UTF-8

# Preferred editor for local and remote sessions
# if [[ -n $SSH_CONNECTION ]]; then
#   export EDITOR='vim'
# else
#   export EDITOR='mvim'
# fi

# Compilation flags
# export ARCHFLAGS="-arch x86_64"

# ssh
# export SSH_KEY_PATH="~/.ssh/rsa_id"

# Set personal aliases, overriding those provided by oh-my-zsh libs,
# plugins, and themes. Aliases can be placed here, though oh-my-zsh
# users are encouraged to define aliases within the ZSH_CUSTOM folder.
# For a full list of active aliases, run `alias`.
#
# Example aliases
# alias zshconfig="mate ~/.zshrc"
# alias ohmyzsh="mate ~/.oh-my-zsh"

eval "$(rbenv init -)"
export NVM_DIR="$HOME/.nvm"
  . "/usr/local/opt/nvm/nvm.sh"
export PATH="$(brew --prefix qt@5.5)/bin:$PATH"
export PATH=/opt/local/bin:/opt/local/sbin:$PATH

source "/Users/mac/.oh-my-zsh/custom/themes/spaceship.zsh-theme"

This is not related to theme. It's related to your terminal emulator unicode character width handling.  Try switching the unicode version  in your iTerm preferences.
Closing this now, Feel free to reopen if you've issues related with theme.

@salmanulfarzy thanks, man! Your link solve my problem. If anybody have the same trouble, this is how I solve it:

Go to Preferences in iTerm 2
Switch to Profiles
Switch to Text
Set checked Use Unicode version 9 width checkbox


refactor(ast_tools): all runners produce Vec<Output>

Standardize all the different Runners to produce Vec<Output>.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#6944
#6943
#6942  👈
#6941
#6940
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite

Merge activity

Oct 27, 10:32 AM EDT: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.


jVM generation is not supported for type other error with type guard

Description:
$title. Fails on slalpha4 with  incompatible types: 'anydata & readonly' will not be matched to 'int[]'.
Steps to reproduce:
Fails at the backend.
public function main() {
    int[] & readonly x = [1, 2, 3];
    anydata & readonly y = x;

    if y is int[] {
        int[] & readonly z = y;
    }
}

Affected Versions:
slalpha5-SNAPHOT

I will be looking into this because I am already working on the area.
https://github.com/ballerina-platform/ballerina-lang/issues/30681
https://github.com/ballerina-platform/ballerina-lang/issues/31011

Need to add test cases mentioned in https://github.com/ballerina-platform/ballerina-lang/issues/31011
after fixing this issue.

Fix this also.
type Foo int|Foo[]|object {};
type Bar int|Bar[]|string;

public function main() {
    Foo s = <int[]> [1, 2];
    float|Foo m = <Foo>s;
    if (m is Bar|string) {
        int f2 = m; // no compilation error, panics at runtime
        panic error("1");
    }
    panic error("2");
}


New categorization system for examples

The current system is:

Each example is under a separate category
Each category is its own tab

Note: The viewer is currently not consistent with the website. The examples there are not categorized in any way, and which examples are shown depends on if we build an rrd file for them in the viewer or not.
We want to move away from the current system, and make the viewer consistent with the website:

All examples should live on the same page
We should include all examples, even if they are not runnable
If an example is runnable, it should be indicated somewhere, and clicking on it will:
Start a new inline web viewer on the website
Stream the recording directly in the native viewer

For any examples which don't have an rrd file built (which may happen because it's an external example, or it's too expensive to build on every PR), clicking on the example will redirect the user to its source code/repository. It should be clearly indicated that the example is not runnable.
Because all examples now live on the same page, we'll need a way to filter them based on their tags.

The current plan I think is more something like:
In the gallery on rerun.io/examples:

Show each example as a card, whether runnable or not
If runnable, include a quick action button that opens up the viewer and loads it directly
Clicking on a card opens up a preview / modal of the example details page
The preview / modal can be expanded to be full page
The example detail page has a component that shows

a preview screenshot of the example
a link to the source code
a description of what it is
the Rerun types used
(optionally) a mini tutorial with the code snippets with rerun calls used to create it
instructions of how to run it

If the example is runnable (has an available rrd file) there is a button that replaces the preview image with an inline web-viewer
There is a categorization system that helps users filter and navigate all the examples

Current design is based on tags, which are themselves broken into 3 categories
We could also go with something simpler, like putting all examples on the same page divided into categories

In the in-app welcome page

Shows all runnable examples as cards
Clicking on a card streams the rrd into the viewer (web or native)
To begin with there is no filtering or higher level categorization of the examples

Replaced by:

https://github.com/rerun-io/rerun/issues/5665


Update org.yaml to add SUSE team members contributing to Kubeflow

We are starting to collaborate (intial effort around pipelines) at SUSE. This PR is to add the team members working there.

/assign @jlewi
Can you please review this one? I'm not familiar this type of request

@alfsuse Have you read the contributor guide? Could you please point at some PRs indicating your contributions?

@alfsuse Have you read the contributor guide? Could you please point at some PRs indicating your contributions?

Sure thing @jlewi here it is for me: https://github.com/kubeflow/website/pull/2056 and for @gsantomaggio https://github.com/kubeflow/pipelines/pull/4278 as said in my initial PR we are starting to collaborate here and so more PR's will come from us.

@alfsuse your diff doesn't look correct. I still don't see the folks added as members in the GitHub org. did you forget to add your changes?

@jlewi yep, I noticed that even if some PR's have been approved we still do not show up but I also see that the same PR's are not yet merged maybe that is why we are not yet there.  I would say let's wait until will be not completely merged, I'll re-check we show up in the contributor's list correctly and will comment on this PR.

@alfsuse Which PR added your folks as members?

@jlewi  for @gsantomaggio : https://github.com/kubeflow/pipelines/pull/4278#  has been merged yesterday
For me, I'm currently waiting to merge: kubeflow/website#2056 .
Both of us have other PR's ready but still open. As I said we may wait to have more PR's merged and re-issue this one if you think is better.

@alfsuse You have to update org.yaml to ensure that anyone who is listed in the team is also listed in the members section of the YAML. There is no connection to the other PRs.

Ah my bad and sorry okay should be fixed now... sorry about that.

np
/lgtm
/approve


Merge workspaces into the main src/

sqlx-tx is essentially a CLI application. To make release process to crates.io simpler, we should merge all code into the main src/

This is done in https://github.com/JasonShin/sqlx-ts/pull/15


Looked at the CSS and updated accordingly

https://storage.googleapis.com/code.getmdl.io/1.0.0/material.indigo-pink.min.css
Search for 'mdl-shadow--' and there only shadow classes that exist are for 2, 3, 4, 6, 8, and 16

Well spotted! The classes used to be called mdl-shadow--z[1-5] (or something) and we renamed them to be closer to the spec. Apparently, we forgot the documentation along the way. Thanks alot, @cliffordp. Change LGTM.

LGTM as well, nice catch.
Once the CLA is signed we can merge away.

CLA signed. Glad to help.
FYI: Working on an MDL Shortcodes plugin for WordPress. So far I've completed Badges, Buttons, Cards, and Grids. Tabs and so on are next.
Please let me know if there's some place to ask questions on my coding journey this week.
For example, I noticed some demo cards had .mdl-card--expand but I didn't notice any difference when that was added, and I didn't see it mentioned on that page's documentation.
tyvm for MDL!

I've put mdl-card--expand on the chopping block in the next major release. So don't worry about that one. ;) You can find details in issue #1036 on that one.
Support or general questions should be asked on StackOverflow and use the material-design-lite tag among any other appropriate tags. The issue tracker is for core problems with what MDL provides.
Thanks for the doc patch as well!


Line flicker at canvas edges

/* DO NOT DELETE THE TEMPLATE BELOW, you can safely delete this line */
Which version are you using?
1.31.1
Is the latest version affected?
You can checkout latest version here

[X] Yes
[ ] No

Which library are you using?

[ ] Vanilla JS (tsparticles)
[ ] React (react-tsparticles)
[ ] Vue.js 2.x (particles.vue)
[ ] Vue.js 3.x (particles.vue3)
[X] Angular (ng-particles)
[ ] Svelte (svelte-particles)
[ ] Preact (preact-particles)
[ ] Inferno (inferno-particles)
[ ] jQuery (jquery-particles)

tsParticles Configuration
{
  particles: {
    number: {
      value: 250,
      density: {
        enable: true,
        value_area: 6894.671861721748
      }
    },
    color: {
      value: '#c0c0c0'
    },
    shape: {
      type: 'circle',
      stroke: {
        width: 0,
        color: '#f1663c'
      },
      polygon: {
        nb_sides: 3
      },
    },
    opacity: {
      value: 1,
      random: false,
      anim: {
        enable: false,
        speed: 1,
        opacity_min: 0.1,
        sync: false
      }
    },
    size: {
      value: 4.008530152163807,
      random: true,
      anim: {
        enable: false,
        speed: 40,
        size_min: 0.1,
        sync: false
      }
    },
    line_linked: {
      enable: true,
      distance:<PHONE_NUMBER>865523,
      color: '#c0c0c0',
      opacity: 0.809723090737089,
      width: 1,
      shadow: {
        enable: false,
        blur: 0,
        color: '',
      },
    },
    move: {
      enable: true,
      speed: 3,
      direction: 'none',
      random: true,
      straight: false,
      out_mode: 'out',
      bounce: false,
      attract: {
        enable: false,
        rotateX: 600,
        rotateY: 1200
      }
    }
  },
  interactivity: {
    detect_on: 'window',
    events: {
      onhover: {
        enable: true,
        mode: 'repulse'
      },
      onclick: {
        enable: true,
        mode: 'push'
      },
      resize: true
    },
  },
}

/* DO NOT DELETE THE TEMPLATE ABOVE, you can safely delete this line */
Describe the bug
Connected lines are flickering insanely while trying to connect to something behind the screen
To Reproduce
Steps to reproduce the behavior:

Go to https://particles.js.org/
Look at the edge of the screen
See line flickering

Expected behavior
No flickering, all lines appearing smoothly
Screenshots
https://user-images.githubusercontent.com/3488005/126184400-1e4fca7f-359a-4e1c-9e7e-3ebbe0cc68c2.mp4
Desktop (please complete the following information):

OS: Windows 10
Browser: Chrome
Version: 91

Smartphone (please complete the following information):

Device: Samsung S9+
OS: Android 10
Browser: Chrome
Version: 91

Hi @VagrantAI-c,
Thanks for the reporting, I already discussed about this issue in one of the discussions here and a fix is already coming. I'm preparing 1.32 version for the release (PR #1803 if you want to see)

Thank you for the quick response! I will be looking for it

Thanks for reporting @VagrantAI-c. Am having this issue as well - am reverting to v1.29.2 where the problem does not appear for me
I am using the core tsparticles library (vanilla, not library specific), with Vue2.


⚠ Bofrost.be has degraded performance

In ee07ded, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1618 ms

Resolved: Bofrost.be performance has improved in 198f769 after 1 hour, 1 minute.


[stable/postgresql] custom metrics are not allowed

Documentation bug: The documentation (https://github.com/helm/charts/tree/master/stable/postgresql#metrics) states that custom metrics can be enabled. But there is no such parameter.
 Currently the use of customMetrics is not supported so either we update the documentation or we we re-add customMetrics support. Originally it was added in this PR https://github.com/helm/charts/pull/791


Usage example for Obelisk.ExecutableConfig

There is basic documentation here.
However, I can only find an outdated example in  qfpl / reflex-realworld-example and w/o some example, I am still puzzled about how to pass configuration to my obelisk backend. I want to specify a mysql host, database, user, and password this way.

Here's an up-to-date example

The json example is probably appropriate for your use case.

That is indeed what I was looking for!


[RUNTIME][WEB] Cleanup logging for web runtime.

The log(info) stops working for web runtime due to the usage of time
function.

Introduce TVM_LOG_CUSTOMIZE anf TVM_LOG_STACK_TRACE.
Reorganize the log customization code to wasm_runtime(so non-gpu usecase can apply).
Update the testcase to cover the logging.

cc @tkonolige @junrushao1994

Thanks @tqchen @tkonolige! I am going to merge it in :-)


UNIT_AudioDecoder_TEST test disabled

Original report (archived issue) by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).


Missing definitions of IndexedDB Database API

I have found the following definitions missing in the IndexedDB API

IDBObjectStoreParameters
IDBIndexParameters
multiEntry property of IDBIndex

I have yet to check out the complete API and what's missing. If someone can list them down I can write the definitions.

PRs are welcomed.


updated cmake

updated cmake to version 3.2.2

In the future, please submit separate pull requests for each cask, as more often than not this type of pull request brings problems with one or more of them, and it halts the inclusion of the other ones.
Specific versions of apps should be submitted to caskroom/versions.

weka37 still needs to be removed. Please squash your commits after.

I may have done something wrong because it doesnt look like I can squash my commits, but anyway, i removed weka, let me know if i should just revert and start over instead. Sorry about that.

No problem. I’ll squash them for you in the below referenced pull request. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes. Thank you for the contribution.


Implement index() Function

Provide Implementation for index() definition here in file src/Modules/Indexer.php
Once done, ensure all tests related to this function is passed before submitting changes.

Done


Drop Shoot ConfigMap controller

How to categorize this PR?

/area scalability usability
/kind bug
What this PR does / why we need it:
Drop Shoot ConfigMap controller as described and motivated in https://github.com/gardener/gardener/issues/5391.
Which issue(s) this PR fixes:
Fixes https://github.com/gardener/gardener/issues/5391
Special notes for your reviewer:
/invite @rfranzke
Release note:

Gardener does no longer automatically reconcile Shoot clusters if their referenced Audit Policy ConfigMap was changed. If users want to immediately rollout Audit Policy changes, they can manually trigger a Shoot reconciliation as described in [triggering an immediate reconciliation](https://github.com/gardener/gardener/blob/master/docs/usage/shoot_operations.md#immediate-reconciliation).

/milestone v1.40
cc @BeckerMax

Isn't this actually a breaking change for folks that already rely that when they update their audit policy the Shoot will be reconciled? What if someone complains about that?

What about
https://github.com/gardener/gardener/blob/04d2b3f459d198e8db0ab57180ca2fea18e84da9/pkg/admissioncontroller/webhooks/admission/auditpolicy/admission.go#L187-L190
?

I assumed, this can stay. It shouldn't hurt, right?
If we removed it now, Shoots would contain an outdated resourceVersion.
We could also change it to unset the resourceVersion field of course in the webhook, if you want...

I think it's confusing if it stayed since there is no use of this field anymore. I would vote for removing this from GAC and potentially unsetting it in the maintenance controller when it anyways triggers a reconciliation. WDYT?

Isn't this actually a breaking change for folks that already rely that when they update their audit policy the Shoot will be reconciled?

Yes, it is. That's why I marked the release note as breaking user.

What if someone complains about that?

I hope, there won't be any complaints, as this is in sync with what we do on changes to the cloud provider secret. Even if, users are free to trigger immediate reconciliations themselves.

/hold
because of https://github.com/gardener/gardener/issues/5391#issuecomment-1029759772

I updated this PR according to https://github.com/gardener/gardener/issues/5391#issuecomment-1029759772 and rebased it onto the merged fixes.
This is now
/ready
to be included in the next release.
/unhold


Utility: Scroll animation up & down enhancement functional specifications

User Story

As a [user role below]:
DDS developer

I need to:
have the Scroll animation up & down enhancement functional specs

so that I can:
so that I can properly code the Scroll animation up & down enhancement utility that meets the Design functions and intent

Additional information

Overview and scope of the engineering work should be included in the linked epic (#4766)
Design Issue 182
Development issue (#4280 )
Prototype link

Acceptance criteria

[x] Documented Scroll animation up & down enhancement functional specifications
[ ] Sent and/or presented the specs to Design and Engineering for their review and comments
[ ] Additional stories are created, if needed, for any work to be done in future sprints

Updates are here: https://ibm.box.com/s/jjz5j9gofyqam02lldrbx7el6ekfvttz

Updates are here: https://ibm.box.com/s/jjz5j9gofyqam02lldrbx7el6ekfvttz


Git branching model: release tag vs release branch

Can we please discuss the use of release branches versus release tags (i.e. rel3 branch vs tagging a version number onto the master branch)? One thing I like about release tags rather than release branches is that it is much more difficult to mess them up (i.e. you can accidentally append a commit onto the branch after it's been released).  Release tags point to a specific commit and make it easier to disseminate.
It makes perfect sense to begin developing toward a rev3 release but, stable and merged rev1/rev2/rev3/etc commits are often marked as tags in master; official releases are then released off of master to ease the task of external users downloading the package appropriately. Deprecating master to progress further on a rev3 branch would (I believe) be confusing as the goal of a branch is to break off until development has matured, to eventually be merged back into the master branch. Contributors could also be left committing to a stale branch, not knowing that another had been made active. From my understanding, moving the primary branch from master to rev3 would deviate from common git practices.

https://stackoverflow.com/questions/9810050/why-should-i-use-tags-vs-release-beta-branches-for-versioning
https://nvie.com/posts/a-successful-git-branching-model/

Hi, rel3 will be merged into master, when I am sure that changes made in
this branch working well.
~Best
On Tue, 5 Mar 2019, 20:36 JC Staudt<EMAIL_ADDRESS>wrote:

Assigned #37 https://github.com/OLIMEX/DIY-LAPTOP/issues/37 to
@hehopmajieh https://github.com/hehopmajieh.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/OLIMEX/DIY-LAPTOP/issues/37#event-2181849627, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABrmZUDUrVpq8EnnKXBd8n4Veuq86ybtks5vTrkrgaJpZM4bfPk-
.


Unable to decompile push ret as jmp

It looks like RetDec cannot decompile push+ret as a jump or call. Do I need some command line options to enable it? A sample code is attached.
BTW, I guess this is not really decompilation as compilers usually do not generate push ret sequence. But it is useful to analyze obfuscated code.
# gcc -g push-ret.S -m32 -o push-ret

	.section	.data
.STR0:
	.string	"print"

	.section	.text
	.globl	myprint
myprint:
	pushl	%ebp
	movl	%esp, %ebp
	pushl	$.STR0
	call	puts
	subl	$4, %esp
	leave
	ret

	.globl	main
main:
	pushl	%ebp
	movl	%esp, %ebp
	#call	myprint
	pushl   $retaddr
	pushl   $myprint
	ret
retaddr:
	xorl	%eax, %eax
	leave
	ret

Yes, this is currently true and it can not be enabled by command line options. I think that ret gets translated to return no matter what was pushed to stack. We need a better dataflow analysis. I will add this to the list of problems that should be solved by the new decoder in #116. I hope I will get to work on the new decoder shortly.


Add mask in History

Is your feature request related to a problem? Please describe.
Problem is when I do ctrl + z to bring back the mask, it doesn't bring it back. Only brings back the previous generation (or the original pic)
Describe the solution you'd like
When doing ctrl + z after a generation that I clicked "Y" to, I want the previous generation come back while the mask that I've put stays in its place and doesn't go away. So basically can you please add the option of putting the mask history in "History" tab?

It was even a possibility I gave when discussing the implementation of the color brush tool:

yknow i literally missed that entire sentence in that post until now?? i promise i can read :|
i definitely think a history max x entries setting is a good idea just in general as well for what it's worth

so if i recall correctly, there's some quibbles with adding mask actions to history - @seijihariki might need to correct me because there's a high likelihood i'm wrong lol - but as an alternative to that, if you git checkout clear_brush_mask_option there should now be an option to preserve brushed masks in the dream and img2img tool context menus, which applies after accepting an image if you'd care to see if that does something like you're desiring

oh ok will try that tonight thanks! Also, is there a way to increase the max steps count from 70 to 200? Sometimes for bigger outpainting jobs 70 isn't enough imo. So is there anyway I can edit one of the files to change the max 70 number..?

I feel some slider ranges should be configurable in the settings menu... For now, editing js/index.js should not be hard to increase the range. It has a bunch of 'createSlider' functions, and you just need to change the max value passed to it.

So you don't have to manually search for the correct slider, it is here:
https://github.com/zero01101/openOutpaint/blob/35d586885459e8023a0d125b71b9676114191957/js/index.js#L606
Just change 70 to whatever you need for now, but I will give a look to making these more easily configurable.

So you don't have to manually search for the correct slider, it is here:
https://github.com/zero01101/openOutpaint/blob/35d586885459e8023a0d125b71b9676114191957/js/index.js#L606
Just change 70 to whatever you need for now, but I will give a look to making these more easily configurable.

nice thanks!

I did "git pull" but the mask goes away even after I choose "Y" to a generation and then undo. Am I doing something wrong?

did you run git checkout clear_brush_mask_option  first?  there should be a new option checkbox in the context menu

I got this error:
"(base) Z:\openOutpaint\openOutpaint>git checkout clear_brush_mask_option
error: Your local changes to the following files would be overwritten by checkout:
js/index.js
Please commit your changes or stash them before you switch branches.
Aborting"
I did edit the index.js to increase 70 steps to 200. Is that what's causing the issue?

yep, that'd be it - you can run git stash to put index.js back to unmodified state, and you should be able to checkout the other branch

yep, that'd be it - you can run git stash to put index.js back to unmodified state, and you should be able to checkout the other branch

Hmm it says it worked but I still don't see the option in the context menu

you might need to refresh without cache - i believe the almost-universal shortcut for that on windows browsers is [CTRL]+[F5] but otherwise you could open your [F12] devtools window and there should be an option in there somewhere to disable cache
but yeah, you're looking for this toggle:

Ahh it worked thanks! However now I tried to edit the index.js file to change 70 steps to 200 steps but it didn't apply. Is there a way to have both this option (preserve brushed masks) and also have the ability for us to change the max number of steps?

The steps thing should not have changed... Try erasing all site data and opening it again. This should clear the cache and update the slider max.

The steps thing should not have changed... Try erasing all site data and opening it again. This should clear the cache and update the slider max.

ohh my bad, I forgot about the ctrl + f5 thing. Ok it's working now. Best out/inpainting UI out there, cheers fellas!!


How to parse with the API: docs outdated?

I already have managed to port one of my parsing tasks to nearley (see https://github.com/loveencounterflow/mojikura-idl/blob/nearley/src/idlx.nearley etc), but this time around i seem to be doing something wrong.
For easier reference, I've uploaded a simple demo project to https://github.com/loveencounterflow/nearley-examples. To wit:
The grammar I use here is the JSON grammar from the nearley/examples folder; that I compiled with nearleyc grammars/json.ne -o grammars/json.js. Then, I copy-pasted (and adapted) this code from the README:
// from-the-docs.js
var grammar = require("./grammars/json.js");
var nearley = require("nearley");
var p = new nearley.Parser(grammar.ParserRules, grammar.ParserStart);
p.feed("[1,2,3]");
console.log( require( 'util' ).inspect( p.results ) );

But this fails:
$ ./run-example-from-the-docs.sh
xxx/nearley-examples/node_modules/nearley/lib/nearley.js:323
            throw err;
            ^

Error: invalid syntax at line 1 col 2:

  [1,2,3]
   ^
Unexpected "1"

    at Parser.feed (xxx/nearley-examples/node_modules/nearley/lib/nearley.js:320:23)
    at Object.<anonymous> (xxx/nearley-examples/from-the-docs.js:8:3)
...

OTOH, I can run nearleyc grammars/json.ne -o grammars/json.js && nearley-test grammars/json.js -i "[1,2,3]":
$ ./run-example-with-nearley-test.sh
...
1: {json$subexpression$1 → array ● }, from: 0
2: {json → _ json$subexpression$1 ● _}, from: 0
3: {_ →  ● }, from: 7
4: {_ →  ● %space}, from: 7
5: {json → _ json$subexpression$1 _ ● }, from: 0

Parse results:
[ [ 1, 2, 3 ] ]

Did I miss something here?
BTW when studying the JSON example, I realized it uses the moo parser; I guess the docs would definitely profit from a link to that software, as it fits so nicely into the nearley setup.

Yeah, I've seen this problem before. Solution:
- var p = new nearley.Parser(grammar.ParserRules, grammar.ParserStart);
+ var p = new nearley.Parser(grammar.ParserRules, grammar.ParserStart, { lexer: grammar.Lexer });

Without this, nearley uses its default parser instead of moo because it doesn't know about your custom one. Look at the compiled json.js, it exports { Lexer, ParserRules, ParserStart }.
You might ask, "Then what's the point of @lexer and inlining lexer into .ne"? And the answer is that you're right, there's no point. You can have your lexer = moo.compile() in a separate file and pass it into new nearley.Parser() just like now.
This is an issue with docs. 😢  I'll see if I can fix that when I have some time.
@Hardmath123 Alternatively, it might be a good idea to allow passing the whole grammar object as a single argument to new Parser(). Just duck-type that the first argument has ParserRules and ParserStart.

It works!
Thanks for the suggestion, and I'm totally for just passing the grammar object into new Parser().

The correct solution is actually
var p = new nearley.Parser(nearley.Grammar.fromCompiled(grammar))

...which does this for you, and is future-proof against updates to the interface between nearleyc and nearley.

Alternatively, it might be a good idea to allow passing the whole grammar object as a single argument to new Parser()

We shouldn't do that. Instead, you should store the result of fromCompiled, to avoid allocating a new Grammar on every parse.
Yes, the docs should definitely be updated. But then we still haven't documented lexers either...! :)

Oops, sorry! I've read the sources and still wasn't doing it right. 😁

OK var p = new nearley.Parser(nearley.Grammar.fromCompiled(grammar)) looks better than what I'm doing now... should definitely get mention in the README, didn't know about it.


[catloop] Connection Establishment Does Not Cancel Inflight Pop Correctly

Description
In Catloop LibOS, when trying to establish a connection, if the client does not get any ack from the server it must cancel the pending inflight pop operation and re-issue the connect request.
When cancelling the inflight pop, we leak the task handle due to the drop semantics on the scheduler.
Code Snippets
https://github.com/demikernel/demikernel/blob/7863a6237df2e4cbecad9a233a731c8e93fa94b8/src/rust/catloop/futures/connect.rs#L221-L223

Closed in https://github.com/microsoft/demikernel/pull/771.


Ignore Vespa deps

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

what does this solve? we auto-upgrade vespa deps to latest as part of releasing, so any error here is an actual error we should look into, maybe? (I fixed one today in https://github.com/vespa-engine/sample-apps/pull/1334 )

We're already have a SD job that updates the target Vespa version for sample apps. Renovate should not interfere.


New annotate function for inserting links to citations

With apologies for another big PR, this one takes a whack at link insertion (which I'm also calling "annotation"), including the problem of inserting citation links into text containing HTML or other stuff that has been cleaned.
The upshot of this PR is we can now do this (example from the updated README):
    from eyecite import get_citations, annotate, clean_text

    text = '
bob lissner v. test   1 U.S. 12,   347-348 (4th Cir. 1982)
'
    cleaned_text = clean_text(text, ['html', 'whitespace'])
    citations = get_citations(cleaned_text)
    linked_text = annotate(cleaned_text, [[c.span(), "", ""] for c in citations], target_text=text)

    returns:
    '
bob lissner v. test   1 U.S. 12,   347-348 (4th Cir. 1982)'

Note that it handles wrapping an  tag that overlaps the citation.
This replaces the existing as_regex mechanism for inserting links, and has a few benefits:

Can insert into text containing HTML (or into text cleaned by other arbitrary cleaning functions)
Can insert different links for different Id. tags, where previously all "Id. at 3" cites would have the same as_regex.
Can insert links to non-standard citation formats like NMSC and tax court

The game plan for the PR is:

Track the character offsets (relative to the cleaned text) that each token came from
Track the token that each citation came from
Use the offsets to insert annotations into the cleaned text
Use difflib to shift those offsets to where they need to be in the original text

This got big mostly because the first step of tracking offsets for each citation took some refactoring.
Commits In this PR
Models refactor: new citation class hierarchy, dataclasses, token references

Refactor the Citation objects so that all citation objects inherit from BaseCitation, and all citation objects know the token and index they came from. This makes it easy to track the original text and offsets that each citation came from.
Use dataclasses for the class hierarchy, with eq=True and frozen=True (if immutable) or unsafe_hash=True (if mutable) to allow for hash comparisons. This just saves some boilerplate.
Rename FullCitation to FullCaseCitation and ShortformCitation to ShortCaseCitation, for future statute extraction

Add test factories
Changing the citation object meant changing every line of the test cases, which was a drag. I added case_citation, supra_citation, etc. factories to a tests/factories.py file so each test line would take less boilerplate and be easier to change in the future.
Track token offsets (start and end)
Each Token now knows its start and end offset. This required a little messing around with the HyperscanTokenizer to translate from byte to string offsets. I also moved a couple of tests from TokenizeTest to FindTest because they weren't specific to tokenizing and it was annoying to get the offsets set up.
Add annotate function
Now that each extracted citation knows its start and end offsets in the cleaned text, we can add the actual annotation function to annotate.py. This is pretty straightforward (build up a list with the cleaned text interspersed with the annotations at the given offsets), except for the part of shifting offsets from cleaned text to original text using the SpanUpdater. That part is kind of hairy -- we use a diff to generate a mapping of each range of characters in the cleaned text to a range of characters in the original text.
I played with adding a dependency to the diff-match-patch library, which produces minimal edit sequences and which I've had to use in other cases when messing with moving annotations, but it didn't seem to matter in this case so I didn't add the dependency. I kept a comment in showing how one would use that library though, in case we see weirdness when running this on more cases with the default difflib.
Default cleaners to none
If you're going to use annotate you can't let get_citations() do cleaning itself, so I changed the default from get_citations(clean=['whitespace']) to get_citations(clean=[]).
Expose public functions at base package for import
Since I was adding another public method I took this opportunity to update init.py so you can do from eyecite import get_citations, annotate, clean_text.
Remove as_regex methods
I deleted the as_regex methods -- I think these are no longer helpful as they don't work for non-standard case citations or non-unique Id. and Supra citations. Note that their behavior may be a little different as some of them tried to capture more parts of the citation, and CitationBase.span() only covers the actual matched token.
Allow extraction of Id. cites at end of text
In writing tests for the annotation function I realized that eyecite can't handle "Id." at the very end of the text (the after_tokens scanning code throws an index error), so this fixes that.
Update readme for model refactors and annotation
Update the readme for all the changes above.

I started reviewing the code itself, but before I got too far along, I got confused about the API and what it's accomplishing. The crux of my confusion was why we were doing "cleaning" work, which made me think that the results of the cleaning were permanent for some reason. It couldn't be that we were doing cleaning text as part of the citation stuff could it?
Eventually, I realized/remembered that the reason we "clean" the text is that finding citations in HTML with whitespace, and underscores and whatever else breaks regexes, so if we want to find citations, that junk has to get out of the way somehow. Got it.
I wonder if we need a different word here. Maybe call these strippers, and maybe tweak the parameter names for get_citations so that it takes plain_text instead of just "text"? I think the docs could use a tweak too, to explain why these are separate steps so that I can remember this stuff in the future.
Does this resonate with you guys?

Oh, also, I wonder if there's any point in continuing to provide a clean parameter to the get_citations function. Seems like a separation there might be better. get_citations always takes plaintext, full stop. If you have HTML, you better use the cleaning functions first and always.

Good ideas. I removed the clean option from get_citations, and added a section to the readme to explain what that function is expecting as far as clean input text.
Not sure about alternative terminology -- maybe "prepare_text"? Or maybe "clean_text" works when it's documented? Calling it strip_text isn't quite right because cleaning text might include replacements, like replacing curly quotes with straight quotes.
Speaking of which, that reminded me to add a test for replacing curly quotes with straight quotes, which exposed an additional case I had to handle in SpanUpdater. As you can see in the new test, annotating text with a replacement ends up looking like this:
1 Abbott’s Pr.Rep. 1
-- the curly quote gets wrapped. I think this behavior is correct, and the most correct thing to do as a consumer of the library is to call annotate with wrap_elisions=False and custom tags as start and end markers, then use the custom tags to insert links using an HTML-aware annotation library. But this is a good place to start.

(I fixed the lint test failure -- pylint was getting a lower score on CI than in local dev because it needed the hyperscan library installed in order to lint those lines properly.)
A related naming-improvement question to clean_text might be the term target_text -- I struggled to name that one. That is, how to have an intuitive API for these two calls:

Apply annotations directly to text, from which the citations were extracted: annotate(text, annotations)
Apply annotations to text, given citations that were extracted from cleaned_text: annotate(cleaned_text, annotations, target_text=text)

Maybe there's a clearer interface to put on that than "you always supply the clean text the citations actually came from, and if you want to annotate different text that you got the clean text from, you supply that as an optional parameter target_text"? It's not the worst but maybe there's something clearer.

Yeah, I played with the naming a bit. What about drawing a distinction between plain_text and source_text. So you wind up with:
plain_text = clean_text(source_text)
citations = get_citations(plain_text=plain_text))
annoted_text = annotate(plain_text=plain_text, annotations=annotations, source_text=source_text)

With the idea being that we make it clear where we expect plain text, and we use source_text to indicate which text we're talking about. I think target_text might be confusing because it refers to an implementation detail. That is, the value passed there is the target of the annotations, but  as somebody that doesn't know what's going on inside the function, I don't think of it that way. I think of it as my starting text that I was working with before I had to clean it up to do citation stuff.

I was experimenting with the change, so I just went ahead and pushed it. But it's one commit, so we can revert if we find something we like better or if you don't like it.

OK, I've reviewed everything, and it all looks good. @mattdahl said he'd take a look, probably this weekend, with an eye towards whether any of this would be tricky on the CL side of things. I don't think it would, but he knows that part better. Matt, if you just want to look at the API of this and think about whether it's sufficient, that might be all we need from your end.
Jack, if Matt says it's good, I think we just have the parameter naming question to wrestle with. The rest looks solid to me.

I don't feel strongly about the naming on this one -- your tweak is fine with me!

Awesome, yeah, I didn't feel strongly about them either. I think my tweaks are an improvement, but I still don't quite love the API. Maybe it's fine though and I just need to get used to it.
With that, we're just waiting for your review then, @mattdahl. I think it's ready to go, but I wouldn't hesitate to make changes if you noted some we needed for this tweak.
Thank you both!

Thanks for making those changes, @jcushman. This looks really amazing! I have no objection to it being merged @mlissner.

Seriously sorry about letting this one slip. I was deep into setting up our intrusion detection system last week. This looks great and I absolutely love it. The next steps, at this point, I presume are to actually integrate this, right? Or did we have more tweaks to the reporters DB that were needed?


Expanding stress options

Changes

Added two new stress options--- SingleThreadedTelemetry and MultipleThreadedTelemetry.

In single threaded mode, two kinds of telemetry are emitted: a per-file analysis, which shows the analysis time, CPU utilization, and memory consumption for each file. Here, the analysis is run on a single core. The mode also emits an aggregated analysis which emits the time-stamp, mean analysis rate (ms/KB), and mean CPU utilization. Here's a sample command line invocation:

stress SingleThreadedTelemetry D:\dataset\ -d "D:\repos\sarif-pattern-matcher\Bld\bin\AnyCPU_Release\Security\netstandard2.1\SEC101.SecurePlaintextSecrets.json" -o "D:\repos\test.sarif" --csv-aggregate "D:\repos\Single_Aggregate.csv" --csv-per-file "D:\repos\Single_PerFile.csv"

In multi-threaded mode, the analysis is executed on all available cores, and an aggregate telemetry is emitted:

stress MultiThreadedTelemetry D:\dataset\ -d "D:\repos\sarif-pattern-matcher\Bld\bin\AnyCPU_Release\Security\netstandard2.1\SEC101.SecurePlaintextSecrets.json" -o "D:\repos\test.sarif" --csv-aggregate "D:\repos\Multi_Aggregate.csv"

        "search-definitions",

In 'Analyze' command this option was changed to "plugin", may need to change here to keep consistent.

Refers to: Src/Sarif.PatternMatcher.Cli/StressOptions.cs:38 in d441728. [](commit_id = d441728ec9ef1678542b706133324f3029a63763, deletion_comment = False)


Formset support

Formset + testapp fixtures and documentation

Codecov Report

Merging #599 into master will not change coverage by %.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #599   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines            8         8
=========================================
  Hits             8         8

Continue to review full report at Codecov.

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

This repo has moved, please point your PR to https://github.com/codingjoe/django-select2 Thanks!


Remove experimental from KDD references

Fixes #786

This should also be applied to v2.2 before merging.


Extend Canvas.DrawVertices to Allow Specifying Vertex Count

Summary
IDrawDevice allows to add vertices with a re-used buffer array while specifying the number of vertices. Canvas.DrawVertices is designed as a simple pass-through method, but has no similar API. This should be extended.
Analysis

Note: Only invoke the canvas transformation for the used part of the vertex buffer.

Done by @SirePi.


Add setTextScale

Currently in progress, will have ranges 0.1 to 10, don't really see the use of having anything more than that. If the limit becomes a problem I probably will change it.

Ended up using 0.5-10. 0.4 and lower took too long to render, wanted to be friendly to hardware components of servers and clients alike. <3


Error executing lua ...cker/start/neo-tree.nvim/lua/neo-tree/command/parser.lua:167: attempt to index local 'stat' (a nil value)

desc:
Got the error as title after the update. It seems that some of my config is wrong, but I'm not sure where I should modify it.

config:
  vim.keymap.set('n', ';', function ()
    if vim.bo.filetype ~= 'neo-tree' then
      win_prev = vim.api.nvim_get_current_win()
      vim.cmd('Neotree focus reveal_force_cwd dir=' .. vim.fn.getcwd())
    else
      vim.api.nvim_set_current_win(win_prev)
    end
  end, NOREF_NOERR_TRUNC)

Remove the dir= .. vim.fn.getcwd() part seems to suppress the error. But I remember I put this with purpose. It seems that something about the command has been updated?

The error would seem to indicate to me that vim.fn.getcwd() is not providing a valid path. I would echo that out to see what it is. I should also a more graceful check on this parameter to let you know the path was invalid.
I'm not sure why it would be needed. The default behavior is to use the current working directory anyhow. It could be that it was not choosing the scope that you wanted, i.e. global vs tab vs window working directory.

It's also possible that your cwd requires escaping if the path has special characters or spaces.

I think we can safely close this one since I have no problem after removing it.


update: ready to next release

[x] update .gitignore file 🐞
[x] use linter 💅🏻
[x] use nyc for coverage 💯
[x] update mocha ☕
[x] improve test code / ++cov to 100 🧪
[x] update all deps. 🥡
[x] update ci pipeline 🎲
[x] improve the source code ✨
[x] update README.md 📋
[x] better pkg.json 🎗

Related: #1323 🚥
READY TO NEXT RELEASE 🚀

@jonathanong, @dead-horse, @niftylettuce, @gyson, please can you take look here, publish the new release then close all PRs and Issues and update koa-convert dep. inside the koa repo. and close the reltaed PRs ..
I guess that's all I'm capable of doing with my current access.

Just waiting on npm ownership from @gyson or npm staff.

v2.0.0 released https://github.com/koajs/convert/releases/tag/v2.0.0


Reinstate mongo26

[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 formula update/change?

[X] Does your submission pass brew audit --strict --online <formula> (after doing brew install <formula>)?
[X] Does your submission adhere to Versions "Acceptable Formulae" guidelines?

I'd like to still be able to use mongodb26. Is this feasible? I made the formula just by bringing back the old one from ffd1baca844f6af6771e20760d65a73ca2c4bdb7

Is this version still supported by upstream? I can't find anywhere on their site stating this is the case. Regardless, given it still builds I'm probably OK with including it but as this repo is deprecated it would be great if you could migrate it to homebrew/core like https://github.com/Homebrew/homebrew-versions/pull/1507 and https://github.com/Homebrew/homebrew-core/pull/8630. Thanks and shout if I can help.

Will homebrew take old versions as PRs? I only see ./Formula/mongodb.rb in there not even 3.0, so I'm a little gunshy of pushing 2.6 to them. Should I not be?

We're migrating old versions into homebrew/core and will accept older versions that are widely used and build on all platforms.

Is this version still supported by upstream? I can't find anywhere on their site stating this is the case. Regardless, given it still builds I'm probably OK with including it but as this repo is deprecated it would be great if you could migrate it to homebrew/core like #1507 and Homebrew/homebrew-core#8630. Thanks and shout if I can help.

If this is still supported by upstream we'll review it on homebrew/core, thanks!


Fonts folder in assets not necessary

Short description of the problem:
The Fonts folder in src/assets is not necessary and there are errors: "Error: EPERM: operation not permitted" when ionic serve is started.
What behavior are you expecting?
The folder can be deleted because the fonts are copied from folder in node_modules, you can see in copy.config.js
Steps to reproduce:

Clone Conference App
Run npm install
Run ionic serve

Oh, sorry, this should be in conference app!


chore: dont need engines

We dont need engines — as this isn't a cli or anything. Its runtime react library.

😅 I should update lib-builder template - https://github.com/TheUiTeam/lib-builder/blob/master/src/commands/init.ts#L28


fixed grammar typo

Checklist

[ x] documentation is added or updated
[ ] tests are added or updated

Merged, thanks!
fff1470cda fixed grammar typo (master)
d0afc7bffa fixed grammar typo (1.1.1)


trace.py: Fix events name type

Events name must be ascii strings. Unicode strings will break trappy, so
encode them to ascii first.

Restarted the travis job, looks like the failure was due to some network issue.
Out of curiosity, how did you find that error ? I suppose you get unicode strings when reading from a JSON or other file.
Also, maybe it could be worth having this in trappy instead of here ?

It was failing with an exception because the event names are used to create classes on the fly. In Python 2, class name apparently cannot be unicode strings (which is expected). I'm not completely sure of why we end up with unicode strings there.

Also, maybe it could be worth having this in trappy instead of here ?
I was hesitating. You can say that trappy API expects str and therefore, you should give str. You can also say that trappy API should be able to deal with anything reasonable and accept unicode strings as long as it can encode them in ascii byte strings.


Think about how verifiable timestamps can be implemented

https://w3c.github.io/did-imp-guide/#verifiable-timestamps

We probably need to take help from  DID team @ w3c.  Need more literature on this.


upload is blocked when there is a banner message

I kind of like this but happy to fix

During the Qiita meeting we decided that it's a nice feature during the release so will not fix but leaving open for a few days in case some other user disagrees.

I was opposed to this.  A simple notification banner of something happening some days in the future should not prevent users from doing a simple data upload.
From: Antonio Gonzalez<EMAIL_ADDRESS>Reply-To: biocore/qiita<EMAIL_ADDRESS>Date: Wednesday, October 24, 2018 at 9:43 AM
To: biocore/qiita<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [biocore/qiita] upload is blocked when there is a banner message (#2681)
During the Qiita meeting we decided that it's a nice feature during the release so will not fix but leaving open for a few days in case some other user disagrees.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/biocore/qiita/issues/2681#issuecomment-432735009, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANq27Sl86raBTSpTAqhq8Ol_c13UxmMfks5uoJibgaJpZM4W3NyJ.

Got it, thanks!


Rename SsaContext to SSAContext

Hi, I'm looking for some good-first-issues to contribute in this repo, and would be happy to take this one.
However, before getting to it, i would like to check if this change conforms to the Rust naming convention.
In Rust's API guideline, it states that "In UpperCamelCase, acronyms and contractions of compound words count as one word: use Uuid rather than UUID, ...", as can see with the naming of std::net::TcpStream.
So should we still go for this change? wdyt

Hey, thanks for choosing to contribute to the Noir.
You are correct, we have not followed this standard throughout the codebase though. If you want, you can change the structs to follow the guideline. Another one which we can phase out, is the usage of get_foo instead of foo

I think we should keep SsaContext and change any other types throughout the codebase that do not follow this pattern

Thanks for the inputs. Then I think I'll try to identify namings of the mentioned cases:

those not following UpperCamelCase (or any other) guideline,
usage of get_foo instead of foo.

And track them in a separate issue, then send out a PR for it.

Closing this issue as we won't be doing this.


Unrecognized cop or department RSpecRails/InferredSpecType for V3.0.1

Versions
rubocop (1.64.1)
rubocop-rspec (3.0.1)
Command
bundle exec rubocop --format progress --config .rubocop_with_todo.yml

Error output
Error: unrecognized cop or department RSpecRails/InferredSpecType found in .rubocop_with_todo.yml
Did you mean 'RSpec/RepeatedDescription'?

Trying to update from version 2.30.0 to 3.1.0 unrecognized cop error is raised during build process.
Rubocop Rspec documentation link here

Can you tell me the result of the following command?
bundle exec rubocop -V.

bundle exec rubocop -V

1.64.1 (using Parser <IP_ADDRESS>, rubocop-ast 1.31.3, running on ruby 3.1.4) [arm64-darwin20]
  - rubocop-performance 1.21.0
  - rubocop-rspec 3.0.1

Have you included rubocop-rspec_rails to your Gemfile and required it from your .rubocop.yml?

No, I didn't I've just installed:
  gem "rubocop"
  gem "rubocop-performance"
  gem "rubocop-rspec"

Do I need it @pirj ?

Yes, we have an upgrade doc.
Any improvements to the discoverability of this document are welcome.

Thank you so much @pirj @ydah for your support. It's working as expected now.
Just to confirm. In changelog the reference to this gem seems to be needed in case we use the gem but as we've just seen it is required.
Thank you one more time 👍🏻

I wasted some time on this for a dependabot PR that upgraded to v3.
What confused me was that the output from running rubocop was leading to a dead end:

Error: The RSpec/Rails/InferredSpecType cop has been moved to RSpecRails/InferredSpecType.
Error: unrecognized cop or department RSpecRails/InferredSpecType found in .rubocop.yml
?

I've created a PR which will I hope will lead those updating the gem in a better direction.


Encode multiple SKBitmap objects as a GIF

Hello.
 Alternatively, is it possible to make a GIF out of a directory full of PNG files on disk using this library? It is possible I am just missing something online and maybe you can point me in the right direction.
As an aside - I have been using this library for the last few days with .net core and I have to say that it is extremely awesome! I've worked with the Skia in C++ as well, but these C# bindings truly save me a lot of time and are so simple to use. Thanks! :)

Right now, I don't think you can. I had a look and they even stopped using giflib, and are using a custom gif decoder.
You could try any .NET-based gif libraries out there.
I asked a question on the forums which may be interesting: https://groups.google.com/forum/#!topic/skia-discuss/R99fiu-tYNU

Okay, well thank you so much for the help! :)


Testing new CircleCI features, please ignore

See title

Hey @jamiew I've re-jigged the circle ci config to use workflows - is this what you what you were looking to do: https://github.com/helpwithcovid/covid-volunteers/pull/174

Superceded by #174, thank you @shen-sat!


[styles] Support augmenting a default theme type

[x] I have followed (at least) the PR section of the contributing guide.

Added support for users to augment an interface once in @material-ui/styles instead of having to set the theme type every time they use makeStyles, useTheme, and styled.
I also added it to a few additional places that wouldn't cause a breaking change.
This makes it possible to reuse the definitions in @material-ui/core where the only difference from @material-ui/styles is the theme type.

Could you add a guide to the docs how to use this feature? We already have one for the core under https://material-ui.com/guides/typescript/#customization-of-theme

@merceyz Could you just add a small notice on how to use this? I can put this into written form if you don't have more time. I would appreciate a starting point though.

@eps1lon Sorry for the long wait. I've added a type spec test and a tiny bit of documentation, don't know where exactly you want it or what it should say so it's quite limited and probably in the wrong location


Updates to enable live testing in sovereign clouds for multiple services

This PR is a copy of the changes created in https://github.com/Azure/azure-sdk-for-net/pull/17277 by @Luyunmt, @tzhanl and others, but rebased against master so the diff/commits can be easily reviewable.
These changes contain fixes for the following services to be able to run live tests against AzureUsGovernment and AzureChina clouds. For some of the below services (core, keyvault, extensions, search, app config) the sovereign cloud live tests will be green with the changes. For the rest, they should pass with public, but represent incremental changes towards working sovereign cloud tests.

Text analytics
Core
Extensions
Event hubs
Identity
key vault
Search
Storage account
Form recognizer
Service bus
Event grid
Tables

@benbp According to the above conversations, I made changes in  https://github.com/Luyunmt/azure-sdk-for-net/commit/cdf7359b769b772e8ab2023744a759a8a900366a

@benbp According to the above conversations, I made changes in  https://github.com/Luyunmt/azure-sdk-for-net/commit/cdf7359b769b772e8ab2023744a759a8a900366a


Artifact should not block SnappedPower

Probably best to add a new power type (maybe SPECIAL) as an alternative to BUFF/DEBUFF, since we'll want SnappedPower to be immune to both debuff-affecting things like artifact but also buff-affecting things like Amnesia

Related, current Amnesia order cleanses SnappedPower. RemoveAllPowersAction removes all powers and is done after SnapAction. Either new "RemoveNonSpecialPowersAction" or patch RemoveAllPowersAction to ignore SPECIAL power types.

Yep, Amnesia will need an update. I think I'd probably lean towards making a new RemovePowersMatchingPredicateAction (similar to what we did for ExhaustCardsMatchingPredicateAction) and let Amnesia pass in its predicate for p -> p.type == PowerType.BUFF || p.type == PowerType.DEBUFF

Oh, Amnesia is also a curse now.

Fixed by #96


[New Core]: Double Dragon III

Core Author username
Coin-OpCollection
Core .yml snippet
display_name: Double Dragon III
repository: Distribution-OpenFPGA
filter: pram0d.doubledragoniii_

Closed per #810.


Supported file types for image overlay

Added notes about supported file types for image overlay, and link to  tags documentation

Sorry, but all of the things added here seem pretty explanatory to me. I don't see the value of adding this to the documentation.

Explanatory sounds good doesn't it? Especially in the Tutorials (maybe less so in the Docs)
There are similar details provided in the doco for Video Overlay. Are their guidelines about what to include in the doco?

Sorry, meant 'self-explanatory' looks like it got auto-corrected. Still don't think we need to add this or spend time on it, our backlog is big enough at the moment.


No entryPoint defined for this router when using default tls config for entryPoint

Do you want to request a feature or report a bug?

Bug

What did you do?
static configuration:
entryPoints:
  web:
    address: ":80"
  websecure:
    address: ":443"
    http:      # these two lines
      tls: {}  # cause the error

dynamic configuration:
http:
  routers:
    test:
      entryPoints:
        - websecure
      rule: "Host(`test.example.com`)"
      service: test

If I comment out the last two lines in this static configuration snippet the error doesn't happen.
Note that this only seems to happen on the file provider since I have also specified entrypoints for routers via the docker swarmMode provider and it works just fine there.

What did you expect to see?
The router was not using my configured entryPoint "websecure" like the one below in the screenshot but was assigned to "traefik" and "web".
The default tls configuration from #6417 seems to override my configured entrypoints.
What did you see?

Log entry:
time="2020-03-06T15:17:54Z" level=debug msg="No entryPoint defined for this router, using the default one(s) instead: [traefik web websecure]" routerName=test

Output of traefik version: (What version of Traefik are you using?)

2.2.0-rc1

Thank you very much for testing the RC :heart:
duplicate of #6441

Closed by #6444.


Create new out file plugins only for secondary

Consider points

Plugin's name
This plugins's name is out_secondary_file now.
It may be too verbose.

Supporting params
I think supporting compress and append params.

Not for this PR tasks

Create a utility command that read dumped data

Close #873

@ganmacs I reviewed at once. There are some points which must be fixed.
Could you update this change? I'll review again in detail after that.

@ganmacs I added review comments.
And please re-check test names. I found some wrong English, and names which doesn't explain what the test is checking good enough.
For example,  "test 'should be output unzip file'" doesn't explain "when?" "why?". In addition, "unzip file" is incorrect expression... "plain text / uncompressed file" is correct.

I added review comments.

@tagomoris
I updated.

I found that Fluent::FileUtil.writable_p returns false if the directory of specified path doesn't exist.
It means configuration like directory /path/to/${tag}/%Y%m%d always raises configuration errors.
Hmm.

@tagomoris
I wrote a test that directory has placeholders (  https://github.com/fluent/fluentd/pull/1154/files#diff-39910dc690f56dd659cdccdca103e55aR417 ) and this test passed.
If configuration is like directory /path/to/${tag}/%Y%m%d, Fluent::FileUtil.writable_p  check direcotry /path/to/ is writable or not (https://github.com/fluent/fluentd/blob/master/lib/fluent/compat/file_util.rb#L39).
I think it is good enough to check.

@ganmacs Ah, I misread the code... you're right.
LGTM.

Merged! It'll be released as v0.14.5. Thank you!


Require 2048 bit DH groups

https://github.com/linuxfoundation/cii-best-practices-badge/blame/master/criteria.md#L237-L244
Could you please add a sentence to the crypto bits paragraph requiring 2048 bit DH groups with a link to https://weakdh.org/

The existing criterion has this through "discrete logarithmic group 2048"
portion. I think the criterion will start getting really complicated and
unweildly if we include each different weakness in an alogrithm.
Maybe in the higher level badges we can call out specific weaknesses that
aren't allowed.
On Thu, 15 Oct 2015 at 14:31 Dan Kohn<EMAIL_ADDRESS>wrote:

https://github.com/linuxfoundation/cii-best-practices-badge/blame/master/criteria.md#L237-L244
Could you please add a sentence to the crypto bits paragraph requiring
2048 bit DH groups with a link to https://weakdh.org/
—
Reply to this email directly or view it on GitHub
https://github.com/linuxfoundation/cii-best-practices-badge/issues/83.

I think implementing issue #60 will make this less of a problem.  In most software crypto is not relevant (so it's easy to skip). In software where crypto is relevant, these kinds of things are important.

I believe this is already addressed by the text.


I can't get it to work(Am I dumb?)

I am running vanilla gnu emacs with the elpaca package manager. Since I don't know how elpaca works with this package I've tried to download it manually.
What I've done is this
  (use-package dash :ensure t)
  (use-package s :ensure t)
  (use-package editorconfig :ensure t)
  (add-to-list 'load-path "~/.config/emacs/packages/copilot.el")
  (add-to-list 'load-path "~/.config/emacs/packages/copilot-balancer.el")
  (load-file "~/.config/emacs/packages/copilot-balancer.el")
  (load-file "~/.config/emacs/packages/copilot.el")
  (require 'copilot)
  (setq copilot-node-executable "/usr/bin/node")

  (add-hook 'prog-mode-hook 'copilot-mode)

  (define-key copilot-completion-map (kbd "<tab>") 'copilot-accept-completion)
  (define-key copilot-completion-map (kbd "TAB") 'copilot-accept-completion)

the ~/.config/emacs/packages/... is the directory where i've git cloned the files and everything is present.
But my problem, when opening emacs after inserting this code.

Hi.  It looks like you don't have dash installed.  Its installation instructions are here https://github.com/magnars/dash.el#installation.  I can't help with specific instructions for how to install it via elpaca as I'm not familiar with it.


Peer-to-peer code review

Great job so far. Excellent design of both mobile and desktop views. Very few changes need to be applied, and your project would be perfect

I can see that hover is only applied to the last button in the contact section. Can you please add the hover to the rest of the buttons?
I can see that the title of the page is "My Portfolio", which is not the best option when it comes to accessibility. As a user tends to open multiple tabs at the same time, a catchy name is preferred so that the user can find it easily. A good example of a page title could be "Jesse - full-stack developer"

Your have documented your project in a professional way. You code base looks clean and on accessibility, you've followed best practices.

However, there are is an issue you need to fix. I would advice you work with percentages on widths on mobile in order for it to adjust to new width when scaled up


fixes #70

Adds postinstall script, moves build tools from devDependencies to dependencies to build on install, adds src to files because npm removes most stuff that isnt listed there.
This fixes #70

Could someone please review the appveyor tests?

@torvitas we use webpack-defaults base repo for all webpack-contrib repos, PR is invalid, why your need src directory?

As described in the linked issue, because you added ./dist to gitignore npm doesn't include it when installed via npm install. I solved that by adding a postinstall script that compiles dist on installation.
Where do you want me to PR?

@torvitas npm don't use .gitignore for ignoring files, npm use .npmignore

You do not have ./dist in the repository at all.

@torvitas why we need dist in repo? Code in dist generate automatically before publish in npm

You didn't publish yet. The way the package is right now it is not possible to install.
Try to npm install git+https://github.com/webpack-contrib/uglifyjs-webpack-plugin.git#master there will be an almost empty folder in node_modules/uglify-webpack-plugin

@torvitas don't need PR, just wait when some bug will be fixed and release will be publish

Well .. there is no sense in having an not installable beta. But I also got there is no willingness to accept my PR at all. You didn't even try to understand the problem I am trying to solve here.
Over and out.

@torvitas i understand your problems, there is not publish release because current master can contain bug (or unexpected behavior).

#issuecomment-313692335 completely solved it


0.13 upmerge

sigh github doesn't like an automatic merge that git's command line can do.

needs resolving.

Ah, I saw the other pull request.

Isn't this PR supposed to become empty after merging #6014?


Fix TokenRatesController write to legacy contractExchangeRates

Explanation
Currently in TokenRatesController it is possible for the wrong chainId's contractExchangeRates to populate state. contractExchangeRates if the network changed in the middle of a updateExchangeRates execution. This PR fixes this issue by adding a guard to check if the chainId is still matching rather than assuming it still does.
References

Fixes https://github.com/MetaMask/MetaMask-planning/issues/1122

Changelog
@metamask/assets-controllers

FIXED: No longer possible for TokenRatesController to update contractExchangeRates with stale data if the network changes in the middle of a call to updateExchangeRates

Checklist

[x] I've updated the test suite for new or updated code as appropriate
[x] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
[x] I've highlighted breaking changes using the "BREAKING" category above as appropriate

Good catch! While I wasn't aware of this bug, it looks like the fix is the same thing I've done in this PR already: #3624

@Gudahtt thank you for fixing this! One thing that is different between my fix and yours is that I read contractExchangeRatesByChainId for the chainId and spread the new contract exchange rates into that object which i then use to set the legacy contractExchangeRates where as yours replaces contractExchangeRates with the new contract exchange rates directly which would leave out any existing contractExchangeRates

Ah, I see,  I hadn't thought through the consequences of the new methods accepting token addresses as a parameter. I was still of the mindset of the tracked token list being the only entries. Hmm. That's not ideal.

closing in favor of https://github.com/MetaMask/core/pull/3639 and https://github.com/MetaMask/core/pull/3624


Update README.md : Redundant Cloning Instructions

In the installation guide in README.md, the instructions for cloning the repository to local machine using both methods - SSH and HTTPS are not clearly differentiated and might confuse new contributors.
Since it's my first issue and the change seems minimal, I'd like to take this on if you assign the issue to me. Thanks!

@sanjay-kv I have made a pull request #145. Kindly look into it.

@sanjay-kv Please add gssoc24 label since my contribution has not been added to the leaderboard

gssoc will do. we follw gssoc as important label

@sanjay-kv sir I can't see my contribution on the leaderboard, will this contribution not be considered?


Separate network upgrade and freeze from node update/add/delete command

Feature to Enhance
Separate network upgrade and freeze from node update/add/delete command

Requested Enhancement
Some user case may issue multiple addressbook change transaction back to back
then do a single upgrade

1. NodeCreate a few new nodes
2. NodeUpdate both existing nodes and new nodes
3. NodeDelete both existing nodes and new nodes
4. Do Freeze prepare_upgrade
5. Do Freeze upgrade
6. The nodes restart

### Business Need

```markdown
Reduce number of upgrade and freeze required

Additional Context
Please update and leverage this design doc to assist: Solo Reusability for DAB Test Cases (DRAFT)
relates to:

#522
#528
#529

:tada: This issue has been resolved in version 0.31.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Simplify tags in forget test

It's a little unexpected for there to be a tag with a comma within it, so I'm simplifying to two standard-looking tags.

The tags separated by comma was done on purpose. This results in an AND combination of the tags.
According to the restic documentation:

This command removes all but the last snapshot of all snapshots that have either the foo or bar tag set:
restic forget --tag foo --tag bar --keep-last 1

To only keep the last snapshot of all snapshots with both the tag foo and bar set use:
restic forget --tag foo,bar --keep-last 1


DocLinkChecker returns different exit codes than documented

When running the DocLinkChecker from our pipeline, we get different exit codes than we should.
The documentation states we should receive 1000 (warnings only) and 1001 (with errors), however, testing showed that we received 232 and 233 respectively instead. In the screenshot you can see the exit code echo'ed out via script.

Am I missing something here or is this indeed a bug?

@hashtag-squirrel I validated the return codes, but they are the values described in the README. I tested in a command shell where I did an echo %errorlevel% after the DocLinkChecker command and was always as reported.
How did you get the "233" value? Which environment and shell?

@hashtag-squirrel  I was able to see that same behavior. Investigating...

@hashtag-squirrel found it. To fix this I have to change return values. Discussing breaking change.


vendor: Revendor with latest vndr

This makes the results consistent with the latest version of vndr, and
fixes the vendor check.

LGTM!


feat: add round function

[!TIP]
The owner of this PR can publish a preview release by commenting /publish in this PR. Afterwards, anyone can try it out by running pnpm add radashi@pr<PR_NUMBER>.

Summary
The round function is designed to round a given number to a specified precision.
Related issue, if any:
https://github.com/sodiray/radash/issues/61
What kind of change does this PR introduce?
Feature
For any code change,

[x] Related documentation has been updated, if needed
[x] Related tests have been added or updated, if needed

Does this PR introduce a breaking change?

No

Thanks for the contribution! Hope to see more from you in the future.


[TIR] ThreadAllreduce warp-level primitive support with multi-warp

This PR enhances the implementation of the LowerThreadAllreduce pass.
Prior to this PR, for CUDA backend we will leverage warp-level primitives only when

the reducing threads are a sub-warp (i.e., size 16, 8, 4, 2), or
the number of reducing threads is less then 32, and equals the reduction extent.

Under the requirement above, for reductions that have large number of reducing threads (e.g., reducing over 128, 256 or larger number or threads), the generated code is inefficient.
This PR improves the LowerThreadAllreduce pass, so that we now generate more efficient CUDA code in such cases, when the number of reducing threads is a multiple of warp size, with the help of warp-level primitives.
Specifically, in such cases, we first reducing 32 elements within each warp, getting the results of each warp stored in shared memory. We then trigger a second round of warp-level primitive reduction within the first warp, and get the final reduction results.
In addition to using warp-level primitives, by doing this we also reduce the size of the shared memory. For example, even when reducing over 1024 threads, we now only require shared memory of size 32, compared with 1024 prior to this PR.
Tests are added to ensure correctness.

cc @masahi

@MasterJH5574 LGTM ! I also encountered the same problem when I searched for reduce_sum on Ansor. Is your work considered on Ansor?


Create an AWS S3 Copy Object Connector

Creating this connector as a skeleton for many other operations available through the AWS Java SDK client used in camel-aws.
I'm opening a PR for this.

Fixed with https://github.com/syndesisio/connectors/commit/b7b01975505e6e13f46187a821a94142961698f2


✨ Generic doc option for markdown front matter

Description
Add a generic option frontMatter to docOptions accepting a k/v map that will be printed in every Markdown page generated.
This supports requests like #1150.
frontMatter: {
  draft: true,
  hide_table_of_contents: true,
}

---
id: an-object-type-name
title: An Object Type Name
draft: true
hide_table_of_contents: null
---

This will deprecate the options docOptions.toc  and docOptions.pagination.
Checklist

[x] My changes follow the contributing guidelines of this project.
[ ] I have performed a self-review of my code.
[ ] I have made corresponding changes to the documentation.
[x] I have added tests that prove my fix is effective or that my changes work.
[x] New and existing unit tests pass locally with my changes.

coverage: 94.148% (+0.2%) from 93.997%
when pulling bdc734a2a51b8e06e62faf2b2ac89fc606b134d0 on feat/markdown-front-matter
into 9c5643474921e582c838ba395b4023fed0e13b3b on main.


DocsArchive-<IP_ADDRESS>Auto archive content

Auto archive content from https://github.com/OPS-E2E-PPE/docs-archive-test

Docs Build status updates of commit 41f0f94:
:warning: Validation status: warnings

File
Status
Preview URL
Details

archvieTargetFolder/content/someContent.md
:warning:Warning

Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

archvieTargetFolder/TOC.yml
:white_check_mark:Succeeded

archvieTargetFolder/docfx.json
:white_check_mark:Succeeded

archvieTargetFolder/content/someContent.md

Line 10: [Warning] Invalid file link:(~/content/CoVer.jpg).
[Suggestion] Missing attribute: author. Add the current author's GitHub ID. NOTE: This Suggestion will be elevated to a Warning on 9/1/2019.

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


Support disembodied hand

Just a small change, shouldn't change anything for those without disembodied hand

I was thinking about this a while back, so thanks for doing it. I think this throws off the pull logic for the spell test if someone has both hand familiars, but it shouldn't break anything


PATCH method and is_conflict

After working on some rest handlers for PATCH requests, I noticed that only PUT requests go through the is_conflict function and as such can return a 409.
I wasn't sure about this but, apparently, the rfc
do mention 409 and 412 as possible return codes in case of conflict.

Some conflicts will happen when you do the actual modification and it's up to you to return a 409 in that case, but I agree that some conflicts may be detected in is_conflict the same way as for PUT and we should probably allow it.

I would like to do this soon but I'm conflicted on whether this should be a 2.x change or a 3.0 change, since it'll change drastically how cowboy_rest executes when doing PATCH requests compared to the current code and documentation. But the RFC says the code and documentation is wrong, so maybe it should be treated as a bug. I dunno.


Error in pip's c7n_mailer

$ pip search c7n
c7n (<IP_ADDRESS>)         - Cloud Custodian - Policy Rules Engine
c7n_logexporter (0.1)  - Cloud Custodian - Cloud Watch Log S3 exporter
c7n_mailer (0.1)       - Cloud Custodian - Reference Mailer
c7n_org (0.0.2)        - Cloud Custodian - Multi Account
c7n_salactus (0.2.1)   - Cloud Custodian - Salactus S3
c7n_traildb (0.1)      - Cloud Custodian - Cloud Trail Tools

$ pip install c7n_mailer
Collecting c7n_mailer
Collecting boto3 (from c7n_mailer)
  Using cached boto3-1.4.7-py2.py3-none-any.whl
Collecting jsonschema (from c7n_mailer)
  Using cached jsonschema-2.6.0-py2.py3-none-any.whl
Collecting Jinja2 (from c7n_mailer)
  Using cached Jinja2-2.9.6-py2.py3-none-any.whl
Collecting s3transfer<0.2.0,>=0.1.10 (from boto3->c7n_mailer)
  Using cached s3transfer-0.1.11-py2.py3-none-any.whl
Collecting jmespath<1.0.0,>=0.7.1 (from boto3->c7n_mailer)
  Using cached jmespath-0.9.3-py2.py3-none-any.whl
Collecting botocore<1.8.0,>=1.7.0 (from boto3->c7n_mailer)
  Using cached botocore-1.7.38-py2.py3-none-any.whl
Collecting functools32; python_version == "2.7" (from jsonschema->c7n_mailer)
Collecting MarkupSafe>=0.23 (from Jinja2->c7n_mailer)
Collecting futures<4.0.0,>=2.2.0; python_version == "2.6" or python_version == "2.7" (from s3transfer<0.2.0,>=0.1.10->boto3->c7n_mailer)
  Using cached futures-3.1.1-py2-none-any.whl
Collecting docutils>=0.10 (from botocore<1.8.0,>=1.7.0->boto3->c7n_mailer)
  Using cached docutils-0.14-py2-none-any.whl
Collecting python-dateutil<3.0.0,>=2.1 (from botocore<1.8.0,>=1.7.0->boto3->c7n_mailer)
  Using cached python_dateutil-2.6.1-py2.py3-none-any.whl
Collecting six>=1.5 (from python-dateutil<3.0.0,>=2.1->botocore<1.8.0,>=1.7.0->boto3->c7n_mailer)
  Using cached six-1.11.0-py2.py3-none-any.whl
Installing collected packages: futures, docutils, jmespath, six, python-dateutil, botocore, s3transfer, boto3, functools32, jsonschema, MarkupSafe, Jinja2, c7n-mailer
Successfully installed Jinja2-2.9.6 MarkupSafe-1.0 boto3-1.4.7 botocore-1.7.38 c7n-mailer-0.1 docutils-0.14 functools32-3.2.3.post2 futures-3.1.1 jmespath-0.9.3 jsonschema-2.6.0 python-dateutil-2.6.1 s3transfer-0.1.11 six-1.11.0

$ c7n-mailer
Traceback (most recent call last):
  File "/Users/kqf870/code/tests/vee/bin/c7n-mailer", line 7, in <module>
    from c7n_mailer.cli import main
ImportError: No module named c7n_mailer.cli

And you installed it inside virtual environment?

yes this is in a virtualenv

I installed it this way and its working for me..
cd to cloud-custodian/tools/c7n_mailer
python setup.py develop

Right, I understand that it works that way. 👍
I wanted to shed light on the released version on pip being broken.

Lost track of this issue, this is fixed now.


Fix build warnings

If possible, we should try and fix the issues we've got in our bindings, since the warnings it throws up are a bit worrying for new users.
Most of it looks like just standard issues or dodgy comparisons/casts.
The files I think are just our bindings.c, so we should go through and update them.
Example

Thanks @mrillusi0n for fixing this!


THIRDEYE-859 : Create report module in distributed anomaly detection code

This pull request contains the new alert module

LGTM

Testing done: Started alert module locally to interact with the production setup.

Checked for emails sent in case of existing anomalies.
Checked for 0 anomalies email sent in case of no anomalies and sendZeroAnomaly=true
Checked that no email sent in case of no anomalies and sendZeroAnomaly=false


SDK: Refresh Token implementation

Supports changes in https://github.com/vector-im/element-ios/pull/5293 to resolve https://github.com/vector-im/element-ios/issues/5292
Included in this PR

Introduces a new SDK option MXSDKOptions.authEnableRefreshTokens to enable refresh tokens. Access token auth will remain in place for the user while logged. Refresh token auth will be used on next login/register.
Implemented the login/register, refresh endpoints as detailed in https://github.com/vector-im/element-ios/issues/5292.
The refresh token are now stored on MXCredential, it has a function for updating the tokens when they are refreshed. It is the source of truth for these values.
Previously the access token was long-lived, was passed around and multiple references to it were held without ill-effect. Now that access tokens are short-lived, the approach is to have MXCredential be the source of truth and other classes that require it such as MXHTTPClient to pull in the value on demand.
MXHTTPClient requestWithMethod functions in the past forked, with half of the function signatures supporting an auth mechanism for the Identity server and the others being for homeserver requests. Rather than maintaining two different auth mechanisms for the http client there I created one that servers both identity and homeserver auth. It comes at the risk of updating the identity server auth but with the benefit of approach/code actually being understandable(vs having two implementations).
MXHTTPClient is designated as authenticated or not in the init(the later meaning the auth closures are not invoked) and similar to the old identity server auth, individual requests can be downgraded to remove the auth headers. All auth requests are now wrapped in an access token check that verifies its validity/requests a new token if required. All authenticated responses are also checked for the UNKNOWN_TOKEN and retried after again verifying/requesting an access token.
MXRestClients used to interact with the homeserver are responsible for the refresh token exchange. A dispatch group and queue are used to ensure that the first request for an access token that requests an exchange with the server leads and all other requests for the token block until the leader completes. When they are unblocked the new token is in place.
Refreshes can also take place in other processes like extensions. To ensure there is only 1 leader across processes we do a read + write of the credentials from disk effectively within a single transaction using NSFileCoordinator. If the read tells use the credential is good we us it, if not we refresh the token with the server and write it back within the transaction so that the next read get is and we don't have race condition.

TODO

[x] Finish preemptive request of tokens at set interval before expiration.
[x] Make sure with the new code and in place and MXSDKOptions.authEnableRefreshTokens enabled that access token auth continues to work until the users logs out.
[x]  Make sure with the new code and in place and MXSDKOptions.authEnableRefreshTokens disabled that access token auth continues to work.

I wonder if it makes sense to have default valued parameters on MXRestClient Swift initializer. We had to make a lot of changes in the tests. Totally up to you.


"enableWheelZoom" turned on while not being set in module

Issue: "enableWheelZoom" option was observed to be turned on in a module which had no enableWheelZoom feature set (Issue occured in chrome, on OS X, with a user who had the role of atlas admin).
Note: This could not be replicated, but all modules were confirmed that this zoom option was not enabled.

Follow-up: To replicate this bug, the user must start an edit session by clicking the create document from schema widget button. After selecting the schema and seeing the form view, a user is able to mouse wheel zoom on the map.
Note: I'm wondering if a possible solution would be to set this option by default in the external Open Layers library as disabled (currently enabled) and then reverse the way we handle the enabling of the wheel zoom in the n2.mapAndControls.js (currently at line 1449)?


archive project

Please archive the repository in the settings.

Bump.

Bump

@DanielRuf why close?

@DanielRuf why close?

Not doing any opensource stuff anymore and closing all open and old issues which have no updates.


Added Content Writing about Hacktober Benefits

Added Content Writing about Hacktoberfest Benefits.
It will help others to know more about Hacktoberfest.
Thanks.

Added Content Writing about Hacktoberfest Benefits.
It will help others to know more about Hacktoberfest.
Thanks.

Sorry to inform but this repository has been excluded from hacktoberfest. So inorder to make your PR count towards hacktoberfest, request you to make your contribution in this repository -> https://github.com/SR-Sunny-Raj/Hacktoberfest2022-for-everyone


Title is truncated (5 items bar)

Hello. First of all, thank you for the library.
I have a small issue with badge title truncation when there's 5 items in bottom bar.
Please take a look at "Calendar" tab. It can be truncated even more if the screen is small.
Text size is default, icons are vector assets (24x24dp).

I believe there's enough space to fit the title properly, so I'm wondering if there's a quick workaround I can apply for now, till you fix it.
Thank you.

Hi, has you solved it?? I have the same issue.

@setoba1192 no, I didn't try though.
To be honest I would rather switch for different bottom bar lib, because this one looks as not maintained anymore, and I'm pretty sure it's gonna be faster than trying to workaround some internal bugs.

it's not a bug those are design limitations for bottom nav bar. you can reduce the text size if you want. copy dimens file from project and add the attrs which ever you want to your dimens file

Well, if you're talking about some design limitations, then you should know that title shouldn't be shown at all when there are > 3 items in bottom bar. At least Google says that.
But I was asked to implement it this way, and the fact that your lib supports it, was the only reason I used it.
So I would still ask you to remove that extra padding from title, or whatever is there and allow to fit 1-2 characters more, if there's this much space.

@Dimezis people asked me to allow it so i gave it as a feature. So people with small title can use it.
This is a open source library people can customise to there needs. it's just copy the dimens file and override the changes you need in your project. Just one line of work. You can customise the library as you need

@Ashok-Varma  hi, i'm looking to change text size, I dont know how can i override dimens file? pls help me. By the way thanks for great lib.

@canberkcakmak
check the value you need to change from this file https://github.com/Ashok-Varma/BottomNavigation/blob/master/bottom-navigation-bar/src/main/res/values/dimens.xml
in your dimens file write a new dimen => with the same name and with value you want