Marshmallow Schema construction should be handled by Parser

Hi @sloria. Loving the new marshmallow integration! Thanks so much.
I had a suggested tweak to the API I was hoping to run past you. Presently marshmallow schemas are used like:
# example A
@use_args(UserSchema())
def my_pryamid_view(request, args):
    pass

I suggest it makes sense to push the construction of the schema instance into the core.Parser becoming:
# example B
@use_args(UserSchema)
def my_pyramid_view(request, args):
    pass

This has a number of benefits:

The current approach requires API users to explicitly set strict=True either in the schema constructor or the schema Meta class. This could be ensured internally if  core.Parser handles construction.
Since webargs presently requires schema instances be constructed at module scope and usage of the marshmallow context will persist between requests. Re-constructing the schema each requests ensures no state can persist.
Presently core.Parser is already responsible for schema construction with dictionary based webargs usage. The proposed change would bring the two usages more into line.

Of course example A over simplifies the construction of the marshmallow schemas since there are a number of arguments that could be supplied with marshmallow construction. What we probably would require is either:
# example C
@use_args(UserSchema, only=('name', 'email'))
def my_pyramid_view(request, args):
    pass

or
# example D
@use_args(lambda: UserSchema(only=('name', 'email'))
def my_pyramid_view(request, args):
    pass

or
# example E
@use_args(UserSchema, schema_args={'only': ('name', 'email')})
def my_pyramid_view(request, args):
    pass

I dislike C because it utilizes kargs which I think have limitations should the use_args decorator, for example, require additional arguments be passed to core.Parser in later versions of the API.
I favour E over D as it allows us to address the issue of setting strict=True during schema construction.
This would also be compatible with webargs's dictionary based usage. So with dictionaries E becomes:
# example F
user_dict = {
    'name': field.String(),
    'email': field.Email(),
    'password': field.String(),
}

@use_args(user_dict, schema_args={'only': ('name', 'email')})
def my_pyramid_view(request, args):
    pass

I'm happy to put a PR together should there be interest in this change.

Thanks for the suggestion, @DamianHeard . I think this is worth considering. You make good points about the API here. One other alternative I can think of would be to pass a callable that takes the request. That would enable use cases such as:
def make_user_schema(request):
    only = request.query['fields']
     # Once marshmallow 2.2 is released...
    partial = request.method == 'PATCH'
    return UserSchema(only=only, partial=partial)

@use_args(make_user_schema)
def my_view(request, args):
    #...

Thoughts?

Thanks for you're prompt reply.
So yes I think some sort of setup callable would definitely be useful. In particular, this would solve one of my up coming feature requests in advice: the ability to provide the request in the marshmallow context.
The downside to this suggestion is that it's less declarative as the schema associated with the view is now slightly harder to find in the callable. This might sound like a small thing but this is one of the things me and my co-workers enjoy most about using webargs.
Can I suggest the following iteration on you're suggestion. The callable should accept the schema class along with the request:

def  make_schema(cls, request):
    only = request.queryu['fields']
    partial = request.method == 'PATCH'
    return cls(only=only, partial=partial)

@use_args(UserSchema, callable=make_schema)
def my_view(request, args):
    # ...

This is more declarative and allows callables to be composed with schemas rather than be hard wired which should promote re-use.
I could for example do:
def use_args_with(cls, schema_args, **kwargs):
    return use_args(cls, lambda request: kls(context['request']=request, **schema_args), **kwargs)

 @use_args_with(UserSchema, schema_args={'only': ('name', 'email')})
def my_view(request, args):
    # ...

In the event a callable isn't provided I would suggest the Parser would just fall back on the schemas constructor.

I'm not sure adding a callable param is the most intuitive solution. What happens if a schema instance is passed? Would the callable have to handle both instances or classes? A function that returns an instance of a Schema seems more predictable.
You could still easily implement use_args_with :
def use_args_with(schema_cls, schema_kwargs=None, **kwargs):
    schema_kwargs = schema_kwargs or {}
    def maker(request):
        return schema_cls(only, partial, **schema_kwargs)
    return use_args(maker, **kwargs)

@use_args_with(UserSchema, schema_kwargs={'only': ('name', 'email')})
def my_view(request, args):

How would you modify this approach to work when the schema is specified as a dict? Since the Parser is presently responsible for constructing the schema it wouldn't be available in the closure.

How would you modify this approach to work when the schema is specified as a dict?

def use_args_with(schema_cls, schema_kwargs=None, **kwargs):
    if not isinstance(schema_cls, Mapping):
        schema_cls = argmap2schema(schema_cls)
    schema_kwargs = schema_kwargs or {}
    def maker(request):
        return schema_cls(only, partial, **schema_kwargs)
    return use_args(maker, **kwargs)

Thanks for your speedy response.
While I don't love that it will certainly produce the required result. The main downside I see is that between the various parser implemention and the decorators there's already a lot of places converting dicts objects to ma.Schema and this would continue that proliferation rather than taking advantage of what's already been implemented.
I agree that in my suggestion supplying callable a schema has already been instantiated is far from clearly defined. If you recall my earlier points I was leaning towards ultimately removing support for passing in instantiated schemas for the following reasons:

The current approach requires API users to explicitly set strict=True either in the schema constructor or the schema Meta class. This could be ensured internally if core.Parser handles construction.
Since webargs presently requires schema instances be constructed at module scope and usage of the marshmallow context will persist between requests. Re-constructing the schema each requests ensures no state can persist.
Presently core.Parser is already responsible for schema construction with dictionary based webargs usage. The proposed change would bring the two usages more into line.

That said I can see this might be a major departure from your thoughts and maybe entirely unpalatable. In addition to this, I don't for example have a solution of how one would easily supply constructor arguments to the schema without also using a callable or making further modifications to the decorators.
I'm still happy to put a PR together if you're happy for me to push it over the line in my own time. If I come up with an alternative approach I'll be sure to slap it up here for discussion prior to then.

Good points in favor of passing a Schema class over an instance. However, I'm not sure we want to completely drop support for passing instances. Passing an instance can be useful (1) when the constructor args don't need to be dynamic and (2) for performance reasons (avoiding the overhead of instantiating a Schema).
The main advantage of allowing a callable is that it enforces the mutual exclusivity of passing a dict vs. Schema class vs. Schema instance.

Added in https://github.com/sloria/webargs/commit/f77b288d5544ce6743bc823f9ee9e537920184fb


Prompt got  eaten and move up a line on certain actions

General information
Please report the following information as possible as you can:

Terminal program: Xfce 4.16
Operating system: Manjaro Linux 5.4.105-1
ZSH framework: oh-my-zsh, zinit
ZSH version: 5.8
ZVM version: 0.8.4 (258eff7b16f9232bb99323aad019969cf94601c5)

Basic examination

[x] I have read through the README page
[x] I have the latest version of zsh-vi-mode
[x] I have tested with another terminal program

Problem description
The prompt jumps up, deleting whatever line came before it. In the below case, use a two-line prompt, and both lines in the prompt jump up to delete the line of output before them.
To illustrate, the terminal looks like this:
Last login: Wed Sep  8 14:38:23 on ttys004
╭─ ~                                                                      ✔
╰─ echo "output to be clobbered by the next prompt"
output to be clobbered by the next prompt
╭─ ~                                                                      ✔
╰─

Then, I hit S and my terminal looks like this:
Last login: Wed Sep  8 14:38:23 on ttys004
╭─ ~                                                                       ✔
╰─ echo "output to be clobbered by the next prompt"
╭─ ~                                                                       ✔
╰─

Notice that the line of output following the echo got eaten, and the prompt is now one line higher in the terminal than it started at.
Reproduction steps

Either open a new terminal or just hit to get a fresh prompt.
Type <ESC>S or <ESC>R<ESC>

Expected behavior
The prompt should keep at the same line rather than moving up a line.

This issue is introduced by<PHONE_NUMBER>a5da5ec570289dfa08687cece1c5f6 and c1480b4a96dfe9ff5ca28f482a7417db25bdd797.

I've updated to the latest version and it does fix the issue in almost every case. I still see it occasionally on a fresh terminal if S is the first thing I do bit I might have to give it some time to see exactly what actions lead to it still occurring.
For now, this seems like a big improvement and is enough to get me to switch from softmoth/zsh-vim-mode

@trmckay Thanks! Could you provide me some more details of your environment? Such as ZSH framework, theme and so on.

@jeffreytse Of course, here is my zshrc. In short, I am using zplug with a few plugins and the starship prompt.
#!/bin/zsh

source $HOME/.aliases

setopt correct

HISTFILE=$HOME/.zsh_history
HISTSIZE=2000
SAVEHIST=1000

# Directory navigation
setopt autocd autopushd pushdignoredups

# Starship prompt
eval "$(starship init zsh)"
export STARSHIP_CONFIG=~/.config/starship.toml

source /usr/share/zsh/scripts/zplug/init.zsh

zplug "jeffreytse/zsh-vi-mode"
zplug "mdumitru/fancy-ctrl-z"
zplug "zsh-users/zsh-syntax-highlighting"
zplug "mdumitru/git-aliases"
zplug "zpm-zsh/tmux"
zplug "zsh-users/zsh-completions"
zplug "unixorn/fzf-zsh-plugin"

TMUX_AUTOSTART=false
TMUX_MOTD=false

export KEYTIMEOUT=1

zplug load

function post_init() {
    # Start a tmux session.
    function start_tmux {
        session=$(tmux ls 2> /dev/null | fzf --print-query | cut -d':' -f1)
        exists=$(echo $session | wc -l)
        if [ $exists -ne 2 ]; then
            session=$(echo $session | head -1)
            if [ "$session" == "" ]; then
                return 1
            fi
            cd "$(fd -t d '.*' . | fzf)" || return 1
        else
            session=$(echo $session | tail -1)
        fi
        tmux new-session -A -s "$session" || return 1
    }
    bindkey -s '^n' 'start_tmux^M'

    # Open a file in nvim.
    bindkey -s '^o' 'nvim $(fzf)^M'

    [ -f ~/.fzf.zsh ] && source ~/.fzf.zsh
}

zvm_after_init_commands+=('post_init')

eval "$(zoxide init zsh)"

### oh-my-zsh completion

# Handle completions insecurities (i.e., completion-dependent directories with
# insecure ownership or permissions) by:
#
# * Human-readably notifying the user of these insecurities.
function handle_completion_insecurities() {
  # List of the absolute paths of all unique insecure directories, split on
  # newline from compaudit()'s output resembling:
  #
  #     There are insecure directories:
  #     /usr/share/zsh/site-functions
  #     /usr/share/zsh/5.0.6/functions
  #     /usr/share/zsh
  #     /usr/share/zsh/5.0.6
  #
  # Since the ignorable first line is printed to stderr and thus not captured,
  # stderr is squelched to prevent this output from leaking to the user.
  local -aU insecure_dirs
  insecure_dirs=( ${(f@):-"$(compaudit 2>/dev/null)"} )

  # If no such directories exist, get us out of here.
  [[ -z "${insecure_dirs}" ]] && return

  # List ownership and permissions of all insecure directories.
  ls -ld ${(@)insecure_dirs}
}

# fixme - the load process here seems a bit bizarre
zmodload -i zsh/complist

WORDCHARS=''

unsetopt menu_complete   # do not autoselect the first completion entry
unsetopt flowcontrol
setopt auto_menu         # show completion menu on successive tab press
setopt complete_in_word
setopt always_to_end

# should this be in keybindings?
bindkey -M menuselect '^o' accept-and-infer-next-history
zstyle ':completion:*:*:*:*:*' menu select

# case insensitive (all), partial-word and substring completion
if [[ "$CASE_SENSITIVE" = true ]]; then
  zstyle ':completion:*' matcher-list 'r:|=*' 'l:|=* r:|=*'
else
  if [[ "$HYPHEN_INSENSITIVE" = true ]]; then
    zstyle ':completion:*' matcher-list 'm:{a-zA-Z-_}={A-Za-z_-}' 'r:|=*' 'l:|=* r:|=*'
  else
    zstyle ':completion:*' matcher-list 'm:{a-zA-Z}={A-Za-z}' 'r:|=*' 'l:|=* r:|=*'
  fi
fi
unset CASE_SENSITIVE HYPHEN_INSENSITIVE

# Complete . and .. special directories
zstyle ':completion:*' special-dirs true

zstyle ':completion:*' list-colors ''
zstyle ':completion:*:*:kill:*:processes' list-colors '=(#b) #([0-9]#) ([0-9a-z-]#)*=01;34=0=01'

if [[ "$OSTYPE" = solaris* ]]; then
  zstyle ':completion:*:*:*:*:processes' command "ps -u $USERNAME -o pid,user,comm"
else
  zstyle ':completion:*:*:*:*:processes' command "ps -u $USERNAME -o pid,user,comm -w -w"
fi

# disable named-directories autocompletion
zstyle ':completion:*:cd:*' tag-order local-directories directory-stack path-directories

# Use caching so that commands like apt and dpkg complete are useable
zstyle ':completion:*' use-cache yes
zstyle ':completion:*' cache-path $ZSH_CACHE_DIR

# Don't complete uninteresting users
zstyle ':completion:*:*:*:users' ignored-patterns \
        adm amanda apache at avahi avahi-autoipd beaglidx bin cacti canna \
        clamav daemon dbus distcache dnsmasq dovecot fax ftp games gdm \
        gkrellmd gopher hacluster haldaemon halt hsqldb ident junkbust kdm \
        ldap lp mail mailman mailnull man messagebus  mldonkey mysql nagios \
        named netdump news nfsnobody nobody nscd ntp nut nx obsrun openvpn \
        operator pcap polkitd postfix postgres privoxy pulse pvm quagga radvd \
        rpc rpcuser rpm rtkit scard shutdown squid sshd statd svn sync tftp \
        usbmux uucp vcsa wwwrun xfs '_*'

# ... unless we really want to.
zstyle '*' single-ignored show

if [[ $COMPLETION_WAITING_DOTS = true ]]; then
  expand-or-complete-with-dots() {
    print -Pn "%F{red}…%f"
    zle expand-or-complete
    zle redisplay
  }
  zle -N expand-or-complete-with-dots
  # Set the function as the default tab completion widget
  bindkey -M emacs "^I" expand-or-complete-with-dots
  bindkey -M viins "^I" expand-or-complete-with-dots
  bindkey -M vicmd "^I" expand-or-complete-with-dots
fi

# automatically load bash completion functions
autoload -U +X bashcompinit && bashcompinit

zstyle ':completion:*:approximate:*' max-errors 2
zstyle ':completion:*:ssh:*' hosts off

source $HOME/.local.zsh

I've also since found that the issue only occurs with the starship prompt.

@trmckay You mean that this issue will disappear without the starship?

@jeffreytse Yeah. I looked through their issues and couldn't find anything relevant. I think maybe this is specific to multiline prompts, not starship itself. But, I can do more testing later.

@trmckay Thank you for your kindly testing, once you got any progress, you are welcome to touch me. : )

@jeffreytse some info for you. This issue is now specific to starship and affects multi- and single-line prompts. There are no issues being tracked in the starship repo. Let me know if I can help you solve this.

Hi @trmckay
Thanks for your following up, could you provide me a minimum .zshrc file which can reproduce the issue in your environment? I will try to settle with your minimum .zshrc file.
Thanks and Regards

@jeffreytse with starship, tmux, and zplug installed:
eval "$(starship init zsh)"
export STARSHIP_CONFIG=~/.config/starship.toml
source /usr/share/zsh/scripts/zplug/init.zsh
zplug "jeffreytse/zsh-vi-mode"
zplug load

I have also noticed this same behavior in the following environment:

Terminal program: kitty 0.23.1
Operating system: macOS 11.6
ZSH framework: N/A
ZSH version: 5.8
ZVM version: 1a7ade5

For me, the critical ingredients appear to be the following:

This only happens inside of a tmux session (using an empty .tmux.conf file works for reproducing)
A multiline prompt is required (I use powerlevel10k)

So, this .zshrc appears to be enough to trigger the issue:
source ~/powerlevel10k/powerlevel10k.zsh-theme
[[ ! -f ~/.p10k.zsh ]] || source ~/.p10k.zsh
source ~/.zsh-vi-mode/zsh-vi-mode.plugin.zsh

If you don't have a ~/.p10k.zsh config file, the config wizard will guide you through setting up a prompt, I use a dual-line prompt with a blank line in between each prompt.
Then, run tmux to start a new tmux session. Hit Enter to add in a few new lines, hit Esc to enter vi normal mode, and then each time you hit Esc, the prompt will move up and eat a line on the screen.

Hi @trmckay @tymcauley
Thanks for the helpful information, once I get progress, I will let you know. : )
Thanks and Regards

I'm having this issue too with oh-my-zsh with several plugins enabled, and zsh-vi-mode. Happens only in tmux, and only with multiline prompt. It also happens when using tab completion

I just spent 2 days trying to fix this problem. I didn't realize there was a bug report on it.
This is happening for me on macos. I've got. Zsh, starship, vi mode.   It happens  after I hit ESC to go into vi command mode.  The first key I type in command mode (no matter what it is) the prompt eats 2 lines above it.
https://www.reddit.com/r/terminal_porn/comments/s9rtfq/annoying_problem_with_starship_zsh_and_vimode/?utm_source=share&utm_medium=ios_app&utm_name=iossmf

Fixed my problem 3 different ways.
#1 deleting zle-keymap-select widget altogether solves this for me.
#2 sticking the following into my .zshrc , also solves the problem.
function zle-line-init zle-keymap-select {
    RPS1="${${KEYMAP/vicmd/-- NORMAL --}/(main|viins)/-- INSERT --}"
    RPS2=$RPS1
    zle reset-prompt
}
zle -N zle-line-init
zle -N zle-keymap-select

#3  And lastly, I discovered I was initializing starship twice in my .zshrc.  Removing one of the two init lines fixes it as well.

I am also experiencing this bug, but I'm running this as my theme:
zplug 'romkatv/powerlevel10k', as:theme, depth:1

I'm also running on tmux.  This tmux is running on a linux machine which I've connected to over ssh from a mac.
❯ zsh --version
zsh 5.8 (x86_64-debian-linux-gnu)
❯ tmux -V
Alias tip: tm -V
tmux 3.2a

Also getting this with Starship regardless of whether in tmux or not...

@jeffreytse some info for you. This issue is now specific to starship and affects multi- and single-line prompts. There are no issues being tracked in the starship repo. Let me know if I can help you solve this.

It's not specific to starship. I don't use starship, and I still have this issue.

I needed to use PR #180 AND do point 2 here https://github.com/jeffreytse/zsh-vi-mode/issues/124#issuecomment-1021410225 to fix it.
Note that I use pure prompt

Any update here?  Would love to see this fixed.

Would

Hi, the PR #180 has been merged, hope this helpful. : )

I'm seeing this after updating to 0.10.0. I don't remember encountering this issue before today which is weird because it's such a long-standing issue.

@diminutivesloop, could you provide minimum reproduce steps for your seeing, so that I can have a further check for you. Thank you! : )

@diminutivesloop Could you try again with the latest update? If you're using zsh-syntax-highlighting plugin, it should fix the issue. : )

@diminutivesloop I'm already on 0.10.0 and the issue is still present and I don't see any newer version that's been released. I also don't have zsh-syntax-highlighting installed so that wouldn't be causing the issue. I can look at producing a minimal reproduction.

@diminutivesloop Thanks for your update, could you try with the latest update 4d778df, which means you clone this repository directly.

So I was actually able to try the latest version by running brew install zsh-vi-mode --HEAD, and from my testing this issue appears to be fixed.

I just installed the latest version from GitHub together with Sindre's Pure prompt and it always deletes the latest line when I switch between insert mode and visual mode.
Video recording: https://s.stl8.co/TSLCLRZV

The exact commands I ran from history:

I experience the same isse using Sindre's pure prompt together with zsh-vi-mode. Without this plugin  (using bindkey -v), lines are not eaten away.


feat(client-python): support Github CI for client-python

What changes were proposed in this pull request?

add github ci to test python

Why are the changes needed?

Fix: #2518

Does this PR introduce any user-facing change?

no

How was this patch tested?

github pipeline

@shaofengshi Hi, I use Github ci to have a test. Does this meet our needs?

I think we'd better integrate with gradle, so one gradle command can run all the build/test things. The changes here only do the github CI, we still cannot run it locally.

Peidian, will this change make the github action longer? If the PR doesn't have change on Python, will the test python be triggred also? @coolderli

Peidian, will this change make the github action longer? If the PR doesn't have change on Python, will the test python be triggred also? @coolderli

@shaofengshi Yes, this will always be triggered for now. We can add some restrictions to it.

close this. because there is a new patch: https://github.com/datastrato/gravitino/pull/2684


debug single test actually run all tests

I noticed all tests running when I only debugging one,  traced rust-tools and found args.executableArgs (which specify testname) is not passed to dap.
This is what get it working locally, not sure if this is on-purpose for some other reason or simply missed:
lua/rust-tools/dap.lua:125

Yes this is something that was missed, ill fix it later or you can open a pull request


feat: add codemod

[FX-4620]
🔴 Please do not review
Description
Describe the changes and motivations for the pull request.
How to test

Temploy
FIXME: Add the steps describing how to verify your changes

Screenshots

Before.
After.

Insert screenshots or screen recordings
Insert screenshots or screen recordings

Development checks

[ ] Add changeset according to guidelines (if needed)
[x] Read CONTRIBUTING.md and Component API principles
[N/A] Make sure that additions and changes on the design follow Toptal's BASE design, and it's been already discussed with designers at #-base-core
[N/A] Annotate all props in component with documentation
[N/A] Create examples for component
[N/A] Ensure that deployed demo has expected results and good examples
[N/A] Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.
[x] Self reviewed
[x] Covered with tests (visual tests included)

All development checks should be done and set checked to pass the
GitHub Bot: TODOLess action

PR commands

List of available commands:

@toptal-bot run package:alpha-release - Release alpha version
@toptal-anvil ping reviewers - Ping FX team for review

PR Review Guidelines

When to approve? ✅
You are OK with merging this PR and

You have no extra requests.
You have optional requests.

Add nit: to your comment. (ex. nit: I'd rename this variable from makeCircle to getCircle)

When to request changes? ❌
You are not OK with merging this PR because

Something is broken after the changes.
Acceptance criteria is not reached.
Code is dirty.

When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:

There are leftovers like unnecessary logs, comments, etc.
You have an opinionated comment regarding the code that requires a discussion.
You have questions.

How to handle the comments?

An owner of a comment is the only one who can resolve it.
An owner of a comment must resolve it when it's addressed.
A PR owner must reply with ✅ when a comment is addressed.

@toptal-bot run package:alpha-release

@toptal-bot run package:alpha-release

@toptal-bot run package:alpha-release

@toptal-bot run package:alpha-release

I tried to run it inside a Picasso and this is an output:
No files selected, nothing to do.
All done.
Results:
0 errors
0 unmodified
0 skipped
0 ok
Time elapsed: 0.002seconds

I think, we also should cover spec, test and story files, because they are also part of the project.

@dmaklygin Great suggestion, please let me add it!

@toptal-bot run package:alpha-release

@dmaklygin Just checked it in picasso, I think the issue was that you need to use the following command (otherwise picasso-codemod looks for monorepo)
npx @toptal/picasso-codemod v38.1.0 packages/picasso/src/**/*.ts*

The output is the following
All done.
Results:
1 errors
2011 unmodified
0 skipped
0 ok
Time elapsed: 3.879seconds

And 1 error stands for custom case that needs to be addressed manually
Manual update required for Container.bottom in packages/picasso/src/Pagination/story/Ellipsis.example.tsx:79
 ERR packages/picasso/src/PageTopBarMenu/PageTopBarMenu.tsx Transformation error (Unable to find @toptal/picasso or Container declaration to insert new spacing import)
Error: Unable to find @toptal/picasso or Container declaration to insert new spacing import
    at insertSpacingImport (/Users/aleksandr/toptal/tmp/picasso/packages/picasso-codemod/src/v38.1.0/utils/insert-spacing-import.ts:28:11)
    at transform (/Users/aleksandr/toptal/tmp/picasso/packages/picasso-codemod/src/v38.1.0/spacing-values.ts:108:24)
Manual update required for Container.bottom in packages/picasso/src/Pagination/story/Variants.example.tsx:8

Then yarn start is run and Picasso Storybook launches

However, one bug was caught and addressed, thanks for checking on picasso!

@augustobmoura

Maybe we should move this AC to https://toptal-core.atlassian.net/browse/FX-4315?

It looks like it belongs to this ticket, I'll address it in a separate pull request, thanks!

@toptal-bot run package:alpha-release

Latest package Staff Portal run result ✅

@toptal-anvil ping reviewers


Adding output binding for commercetools

Description
Adding output binding for commercetools.
Issue reference
n/a
Please reference the issue this PR will close: #[issue number]
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[x] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

I assume this is a continuation of the work in PR -- https://github.com/dapr/components-contrib/pull/1224

LGTM
Please complete the docs PR for this -- I opened a docs issue for you. https://github.com/dapr/docs/issues/2351
I will merge this once the docs PR has been opened.

@berndverst I added this alrready back then into v1.5 of the docs, see https://github.com/harrykimpel/docs/tree/v1.5/daprdocs/content/en/reference/components-reference/supported-bindings


[COLIB-NGC] 59 gov steam eu

Hey @Lampros-Cresym, thanks for your review! I resolved some conversations and will push the changes now. Some others are not resolved yet, but I answered. Have a look what you think!

@Lampros-Cresym I think that @matoubongrain also needs to approve -- because she requested changes back then.
Alternatively, you could merge it into dev.

@Lampros-Cresym I cannot merge, I think because @matoubongrain and Erwan also need to approve -- because they requested changes back then. Alternatively, you could merge it into dev.

I think it is OK to merge. Their comments have been resolved. If needed, we will re-evaluate it later.
@GJCRESYM could we merge it to dev?


formatter design

I do not quite like how formatters work. Right now, they modify the observation dictionary in place. This makes it easy for the formatter, because you do not have to copy the observation, but has unpleasant consequences:

the side-effects in the observation are visible to downstream functions, but not to filter and ignore functions, which are processed before
the side-effects make it impossible to write one-line formatters using 'lambda' (but that is really a weakness in Python). Even without side-effects it would be hard to write one-liners.

What I would really like is to specify places in the observation where I want to make some changes. For example, I want to split the lines for key1[].foo, or I want to replace all strings that match a date in key2.dates[].

Also, I am proposing that only agents specify formatters. The spy function does not really need them because you can just as well format the value before passing it to spy. The spy_point` should not have it because we want to discourage writing bond-specific code in production code.

Agree that I don't really like the way they work right now. I'm sure we can find something better.
As for formatters in spy_point... I can imagine a situation where being able to specify a formatter right next to the function could be useful, e.g. when you know that there's one argument you'll never want to observe, or something along those lines. I agree that minimizing bond code in production is important but it's something to consider.

For now I have moved the formatter than I had in bond_reconcile._print to the testing code.

Here is a proposal for helping the writing of formatters, without writing a new JSON serializer. Essentially we specify a list of pairs (location_regexp, action) where the location_regexp says what keys in the observation should be acted on, with the keys being of the form "key1.key2[xxx]", and the actions being things like "split_lines", "search_replace(regexp, replacement)"
So we can write things like:
formatter=formatters.split_lines().at('.*\.what$'),
...
formatter=formatters.search_replace('random=\d+', 'random=...').at('.*\.what\[\d+\]$')

This allows one to write simple formatters without defining auxiliary functions. Another advantage is that most of the time we use the standard JSON formatter and we do not need to re-traverse the object.
This notation should allow one to write new actions.
Using regexp to match keys is fast, but the notation is awkward because the key language contains "." and "[ ]" which have special meaning as regular expressions.

Yeah, I like that direction. We could probably allow regex for full flexibility, but also provide easier ways, e.g. split_lines().atKey('what') would achieve the same thing as your first line and search_replace(...).atKeyWithValue('what', '\d+') would achieve the same as the second line (or something like this - generally I just I feel that most of the time full regex would be unnecessary and a simpler interface would be nice)

Another useful formatter would be a rounding function for floating point values.


Source only repo?

I started to clone this repository, but stopped less than half way through after realizing it is over 1GB.  I wonder if it's due to multiple versions of binaries stored within.
Is there a smaller source-only version of this repository?

Try cloning with depth=1 so you only get the latest version of the binaries. But yeah, that's the biggest reason for the overall repo size. Probably ought to clean that out some day.

Oh, and there are source tarballs available at http://proteowizard.sourceforge.net/download.html (Source, bjam build, with or without vendor reader support)

Using depth=1 worked fine.  Thanks for the suggestion!


Mockoon DOWN

🚨 Service Alert: Check the details below
Monitor Details

Monitor Name: Mockoon
Incident Status: TRIGGERED
Severity: critical
Monitor Status: DOWN
Monitor Health Checks: 1
Monitor Failure Threshold: 1

Actions

View Monitor

[start_datetime:1732954980]

The incident has been auto resolved
Total downtime: 0 minutes


Updated Polish translation

Please make sure these boxes are checked before submitting your pull request - thanks!

[ ] Run the unit tests with gradlew app:connectedGmsDebugAndroidTest to make sure you didn't break anything (with an emulator running or phone connected)

[x] If you have multiple commits please combine them into one commit by squashing them.

Note you may see the Cirrus CI system failing on your PR. It's pretty flaky right now so don't
be alarmed.

Thank you so much for jumping on this!


Local pull request success status testing

Docs Build status updates of commit b427837:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

E2E_DocsBranch_Dynamic/index.md
:white_check_mark:Succeeded
View

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


Support ProRes

Fixes #666

With this, we could now add the Video codec preference that we could not add in https://github.com/wulkano/kap/pull/254. @skllcrn ?
The benefit of recording in ProRes would be that it should in theory require a lot less processing power as it doesn't have to compress the video. It can also be useful for people that intend to edit the video after capturing it with Kap for maximum quality.

@sindresorhus would the resulting exported videos (trimmed/converted) be in ProRes as well? Or would we switch it to H264 like we have it now? Asking because that might change some of the conversions. Save Original would obviously be the ProRes video.
Also, since ProRes is not compressed at recording time, does that mean that the export would take longer? Or does it trim time off of that as well? (skipping the decoding step)

Only “Save Original” would be in ProRes. Export from ProRes to GIF should in theory be faster as ProRes can be decoded faster.

So, do we record in ProRes by default? Instead of H264, since it's less processing power, faster export (in theory). Is there any drawbacks to recording in ProRes?
This way we don't have to create a new setting for it

The downside is more disk space. We should probably do some manual benchmarks before making it the default. For example, one downside is that we to convert it before showing it in the editor, so long recordings will make the editor take longer to show.

Yeah, even with the fast preset, when I tested it on a big file it takes a couple of seconds. We could show the editor early, with a loader and a message saying "Generating preview" or something like that. I'll run some conversions locally in small/medium/large files, with fast preset or normal (good quality) conversions and send the results

Some benchmarking results: https://gist.github.com/karaggeorge/18fe906ea5f1f03c68d758a6e9bf95ff
TL;DR:
Conversions take a while, and the ProRes files are really really big, so imo we should have recording in ProRes under a setting, and definitely come up with a design for the editor while we are generating the preview (6 minute ProRes video took more than a minute to generate)

Conversions take a while, and the ProRes files are really really big, so imo we should have recording in ProRes under a setting

👍
@skllcrn Are you ok with this?

and definitely come up with a design for the editor while we are generating the preview

@skllcrn $ open -a Sketch

(6 minute ProRes video took more than a minute to generate)

That is surprising. I imagined it would take much less time. Are we sure we're using the fastest settings with ffmpeg? Quality doesn't matter for the preview.

Can you try the ultrafast preset? https://trac.ffmpeg.org/wiki/Encode/H.264#Preset

@sindresorhus
definitely not the fastest, but the ones we use currently. I'll try ultrafast. For crf I thought it was 0-51 where 51 was the worst. Should I try 51 instead of 0?
I'll also try the audio and scale options. Scaling it down will also include more complexity, since we use the actual video dimensions for the editor, but we'll have to override them with the not-scaled-down ones
Also, I was still using my computer. Not anything heavy, regular work, but it wasn't the only process running. So it could probably be faster in theory, but a user will probably be doing something else while converting anyway

For crf I thought it was 0-51 where 51 was the worst. Should I try 51 instead of 0?

I misunderstood that option. Yeah, just try. I don't think it will have much impact though.

So, I can't use -c:a copy because I get an error:
[mp4 @ 0x7f91d5801e00] Could not find tag for codec pcm_s16be in stream #1, codec not currently supported in container
Could not write header for output file #0 (incorrect codec parameters ?): Invalid argument
Error initializing output stream 0:0 --

But changing crf to 51 (worst possible quality) and using ultrafast brought a 1 minute video conversion from 10s to 6s, so I guess it improves a bit.
Using the scale down by half brought that down to 4.2s

But changing crf to 51 (worst possible quality) and using ultrafast brought a 1 minute video conversion from 10s to 6s, so I guess it improves a bit.
Using the scale down by half brought that down to 4.2s

So let's do both of those tricks then.

We could show the editor early, with a loader and a message saying "Generating preview"

We'll still need this though.

Closing as this is stale.


GCP provider; disable creating new VPC for benchmarks

Is there a way to disable the creation of a new VPC for some of the benchmarks?  Can we instead pass in a VPC that already exists for use with the benchmarks?  Some projects/users may not have permission to create VPCs.

For GCP, you can specify a network name, and it will use that network. It does create subnets for the VMs. I do not believe it creates any VPCs.
I believe AWS creates a VPC per VM. We do not have a feature/flag to pass in a VPC name instead of creating a new one when a VM is created. And I don't think there is any planned work for it. An implementation for this would be to add a flag in aws_network that passes in the name for VPCs and checks to see if it should use the VPC for the VM instead of creating a new one.

Sorry. I was initially confused by the question. We have a flag that you can pass to specify the VPC.
gce_network_name can be set to set it to a predefiend VPC in GCP.

Thanks adding --gce_network_name=vpc_name seems to have worked.    Is there a way to disable creating the SSH Firewall rule.  I do not need to do that for my use case.  I can already SSH into my project no need to create the firewall rule.

Have you tried ---gce_remote_access_firewall_rule?


chapter_recurrent-neural-networks/index

Job d2l-zh/PR-648/1 is complete.
Check the results at http://preview.d2l.ai/d2l-zh/PR-648/


Revert "Remove checks for loaded ftplugin and indent"

Use did_ftplugin for early return is a standard practice in vim. The commit that introduced this change was aiming to solve a treesitter bug which should be outside of orgmode's scope (see #447).
At the time #447 was issued, I was thinking about this is a telescope bug, but indeed this is a treesitter's bug, see https://github.com/nvim-treesitter/nvim-treesitter/issues/4754.
And indeed this commit only solves #447 partially. The first time you opened an org file via telescope, the fold works correctly, but the second time you opened a file via telescope, the fold does not work again.
Based on above description, I think we should revert the changes and follow the standard practice of vim's ftplugin. And let the bugs to be fixed in upstream.

Thanks for investigating this, it's a very interesting issue.
Do you have an idea what's actually causing the bug in nvim-treesitter?

Thanks for investigating this, it's a very interesting issue.
Do you have an idea what's actually causing the bug in nvim-treesitter?

The fold method of treesitter uses cache to store fold information (fold level at each line).
And I suppose the autocmds that triggers treesitter to recalculate the fold are not activated in insert mode file switching.
so when you are switching files at insert mode, the cache are not updated.

Thanks!


Fixes issue #98 added splashscreen

Pull Request Title
feat(clnapp): fixes issue #98
Description
1.Added a SplashScreen which runs fine on both Iphone and Android.
2.Updated the kotlin version to the latest one under Android/gradle
Checklist

[x] I have tested my changes
[x] I have updated the documentation
[x] I have added necessary comments

Screenshots (if applicable)

Android:
https://github.com/dart-lightning/lndart.clnapp/assets/119595975/5f7608bb-91ff-4523-8d89-de6f0c9c71cd

Iphone:
![Simulator Screenshot - iPhone 15 Pro Max - 2024-03-16 at 15 46 41](https://github.com/dart-lightning/lndart.clnapp/assets/119595975/327269d1-ecd1-4468-8666-3b7ecf5e338d)
![Simulator Screenshot - iPhone 15 Pro Max - 2024-03-16 at 15 46 39](https://github.com/dart-lightning/lndart.clnapp/assets/119595975/885f61d7-0f32-420a-8870-7f214c8663d5)

Commits

feat(clnapp): fixes issue #98

Added a splash screen in the app .
The splash screen now consists of the app logo, a cool tagline on a light blue background.

The splesh screen need to respect our theme color

The splesh screen need to respect our theme color

So,I need to change:
1.the background color from Light Blue to backgroundColor: Theme.of(context).colorScheme.background,
2.and the text color from white to default.
Between is the tag line good?

The splesh screen need to respect our theme color

https://github.com/dart-lightning/lndart.clnapp/assets/119595975/3d0ffdeb-e313-4172-8760-fb197a5afd77
This will be the result after making the changes in color from sky blue to primary background
Hope this one matches CLN app's theme

on the web is still blue https://deploy-preview-144--clnapp.netlify.app/

Yes because I have not yet pushed the changes . I just thought to ask is this one perfect so that I can create a fresh pull request for the same

idk I still do not like how it looks, it is a standard usage of the splash screen

.

idk I still do not like how it looks, it is a standard usage of the splash screen

May be we can use an animated spark coming down instead of a simple logo of the app.
I mean instead of simple logo, it comes as an animated spark of electricity and then comes the test after a delay  And then a circle  showing loading.

I do not want to add a splash screen at this moment because the application UI sucks anyway. So I am closing this PR because there are issue more important to fix.
Thanks for contributing


Login Page - Kato

Day 2

[x] Set up basic React app structure and Login page

Day 3-4

[ ] Frontend Developer 2: Work on JWT authentication via Login page

Day 5-7

[ ] Frontend Developer 2:  Fine-tune JWT authentication

Day 8-10

[ ] Frontend Developer 2: Debug Login page, finalize JWT implementation

Day 11

[ ] Integrate

I'm not sure whether I'm the one who is supposed to do the JWT auth or Vitusan, so for now I'll leave it to him so that I can work on the profile page, and if he needs help I will be available.


[HACK] cstdlib: Forward malloc et. al. to kmm_malloc, if KERNEL

This is the only way to get the external module "uavcanlib" to work inside the px4 kernel.
If an alternate solution, e.g. moving uavcanlib to user space is implemented this hack should be removed.
[NOT UPSTREAMABLE]

I wonder if this breaks the shmfs in protected build, which intentionally allocates from user heap? Just a question...

No, shmfs does not include cstdlib as it is a c++ header


Height 100% - Child Resize Inconsistent Behavior

In this app
<?xml version="1.0" encoding="utf-8"?>
<s:Application
	xmlns:fx="http://ns.adobe.com/mxml/2009"
	xmlns:s="library://ns.apache.org/royale/spark"
	creationComplete="init()"
	>
	<fx:Script>
		<![CDATA[
			private function init():void
			{
				myContent.height = 200;
				myContent.width = 200;
			}

		]]>
	</fx:Script>
	<s:Group id="upperContainer">
		<s:Group id="bottomContainer" width="100%">
			<s:BorderContainer backgroundColor="blue" id="myContent"/>
		</s:Group>
	</s:Group>
</s:Application>

bottomContainer height will remain 0. But if I initialize myContent with the values given in init() then it's height will be 200. It should not matter if height of myContent was given after creationComplete, or before.

This is the ChildResize branch.

Seems to work ok for me.

This seems to be fixed, at least with PR #1135 and other previous PRs (don't know which one fixed it;  I guess ChildResize branch did).  This shows a blue square 200x200, and DOM attributes show bottomContainer has height 200, when the width/height are set in creationComplete.

I can confirm it works in ChildResize as well. Will ChildResize or PR #1135 is merged.

Works in develop, already.


[C++][Parquet] StreamReader::SkipRows() skips to wrong spot in files containing multiple row groups

Describe the bug, including details regarding any error messages, version, and platform.
The issue arises due to a simple arithmetic error when calculating the offset from the current row group. As far as I can tell this affects all platforms and the bug has existed since the introduction of the StreamReader skip code in https://github.com/apache/arrow/commit/56adb6a7ecd5f189f03f4a73a6df1c9a2af1eeb0
I will submit a PR with a unit test case and proposed fix shortly.
Component(s)
C++

OK, maybe I didn't read the contributing guidelines correctly but I wasn't successful in getting my PR to automatically reference this issue. It is here: https://github.com/apache/arrow/pull/36191

OK, maybe I didn't read the contributing guidelines correctly but I wasn't successful in getting my PR to automatically reference this issue. It is here: #36191

The PR title has to be started with GH-XXX to link it to correct issue.

OK, maybe I didn't read the contributing guidelines correctly but I wasn't successful in getting my PR to automatically reference this issue. It is here: #36191

The PR title has to be started with GH-XXX to link it to correct issue.

Should I submit a patch for the contributing guide, which says the issue should be named ARROW-XXX or PARQUET-XXXX?
https://github.com/apache/arrow/blob/main/.github/CONTRIBUTING.md?plain=1#L61

OK, maybe I didn't read the contributing guidelines correctly but I wasn't successful in getting my PR to automatically reference this issue. It is here: #36191

The PR title has to be started with GH-XXX to link it to correct issue.

Should I submit a patch for the contributing guide, which says the issue should be named ARROW-XXX or PARQUET-XXXX? https://github.com/apache/arrow/blob/main/.github/CONTRIBUTING.md?plain=1#L61

Yes, that would be great!


Dev

Hi @jeffreybschmidt, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

Hi Jeffrey, you 've created a pull request against our master branch. Can you please re-create this PR using the DEV branch. I'm closing this one.

Thanks for closing the PR Bert. It never should've been created in the
first place - my mistake.

Jeff
On Mar 21, 2015 1:50 AM, "Bert Jansen"<EMAIL_ADDRESS>wrote:

Hi Jeffrey, you 've created a pull request against our master branch. Can
you please re-create this PR using the DEV branch. I'm closing this one.
—
Reply to this email directly or view it on GitHub
https://github.com/OfficeDev/PnP/pull/562#issuecomment-84276705.


useContext return undefined

Describe the bug
Here is the example code
type CtxType = {
  foo : string
}

const Ctx = createContext<CtxType>()

const useAppCtx = () => {
  const ctx = useContext(Ctx)
  if (!ctx) throw 'context is undefined'
  return ctx
}

const Provider: ParentComponent = (props) => {
  return <Ctx.Provider value={{foo: 'bar'}}>
    {props.children}
  </Ctx.Provider>
}

const App = () => {
  return <Provider>
    <Child />
  </Provider>
}

const Child = () => {
  const {foo} = useAppCtx()
  ....
}

Whenever I use useAppContext it will return undefined when I save the code, however it works fine when I refresh the browser

The issue is when i have to style the component I have to refresh the browser manually.
Is there any workaround for this issue? Thank you
Your Example Website or App
https://stackblitz.com/edit/solidjs-templates-wqdscb?file=src%2FApp.tsx
Steps to Reproduce the Bug or Issue

copy the code above
try to edit code
The code will be stuck in runtime error because of the undefined context and you have to manually refresh the browser to continue

Expected behavior
I don't have to refresh the browser manually to continue working on my code.
Screenshots or Videos
No response
Platform

OS: macOS
Browser: Chrome

Additional context
No response

I have found the workaround from https://github.com/solidjs/solid-refresh/issues/15
/* @refresh reload */

putting this comment on top of the file that have the Context code seems to be working for me. the undefined error did not appear and the code is updating correctly in browser

I found a better work around from https://github.com/vitejs/vite/issues/3301#issuecomment-1080030773. Seems like a Vite issue and
/* @refresh reload */
didn't work for me.

@xTye Yes, the superior workaround is to move createContext on a separate module alongside utilities to access that context instance.
Right now, those are the two known fixes, but the upcoming rewrite for Solid Refresh should fix the Context issue

I have the same problem where useContext(OrganizationContext) will return undefined on HMR.
solid-js: 1.7.12
solid-refresh: 0.5.2
However, it seems that this issue was marked as solved by PR #34

@xTye Yes, the superior workaround is to move createContext on a separate module alongside utilities to access that context instance.
Right now, those are the two known fixes, but the upcoming rewrite for Solid Refresh should fix the Context issue


Grib Py3 whats new

replacing #1774 for now, noting the lack of support for GRIB in Python3

I'm not sure I agree with the statement, even if it is factually correct at the moment. The problem is that a future version of the GRIB_API could come along which does support Python3 - I can't be certain, but it looks to me like if that did happen we wouldn't need a new Iris version.
We aren't taking away functionality from users at this point, so I'd be inclined to just make a mention of GRIB not being available on Py3 yet, rather than it being a fundamental limitation of Iris.

i've updated the wording, is this any better?

I know this is closed, but I'm puzzled..
The latest we have from @QuLogic appears to at least pass all the existing grib tests.
So, in the context of v1.9 release, @QuLogic @marqh : do we still need this warning, if the old code is still functional for now ?

I think we agreed that the change necessary to make GRIB work on Python 3 was not going to be included. The discussion is in the (closed) PR #1774 which is the py3k-grib branch you are referring to.

Thanks for explaining @ajdawson.
Sorry for a slip of the mouse :  I meant to say https://github.com/QuLogic/iris/tree/py3k
But in any case, I think it is the same, if I misunderstood the status of this (and now have it right!)
I presume these commits are the contribution from py3k-grib, which will will not be including ?
e6b25f7 py3k: Re-set GRIB file loader after every message.
4fcd55a py3k: Be explicit about GRIB array type.

Assuming I've now got it, I'll add some python-3 specific skips to the things that break.

I believe that is accurate. If unsure I'd suggest you additionaly check with @rhattersley.

It all looks good to me. :+1: Thanks for pushing this forwards! :smile:
(FYI, work commitments have dragged me away from much active involvement recently and for the next month or so, but I'm very happy to spout opinions where that helps! :wink:)


WS2812: fix timing and add nRF support

An ugly fix for pulse timing to get the WS2812 LED strip driver to work on nRF, and support for that family.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@31340d8). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master   #10412   +/-   ##
=========================================
  Coverage          ?   53.14%
=========================================
  Files             ?      210
  Lines             ?    25745
  Branches          ?     5673
=========================================
  Hits              ?    13681
  Misses            ?     9754
  Partials          ?     2310

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 31340d8...6d97a9b. Read the comment docs.

@carlescufi thanks!
@jhedberg since you have a driver for this chipset, would you mind taking a look and ACKing if it seems OK?

@jhedberg since you have a driver for this chipset, would you mind taking a look and ACKing if it seems OK?

@mbolivar I only have experience with the ws2812b_sw driver, which is bit-banging based (rather than SPI). That said, this PR does look fine to me.

@jhedberg I'll take that as an approval. This PR has now been up for a while and @mbolivar is the led_strip maintainer so I'll merge it.

@mbolivar I only have experience with the ws2812b_sw driver, which is bit-banging based (rather than SPI). That said, this PR does look fine to me.

Thanks!


controller: Fix ignoring job event uniqueness errors

This logic was broken in https://github.com/flynn/flynn/commit/bc37712.

LGTM.


avoid facades

part of https://github.com/concrete5/concrete5/issues/3287

@KorvinSzanto I didn't profile this, just wondering is this would be what you had in mind? Could you please have a quick look before I start going through more classes? Thanks!

created a new PR for the application class only. Impact is pretty small though.


require-dir is broken and cannot get "/api/users"

currently I am using windows 10 on nodejs version 8.2.1 and express 4.15.5
I dont know if I am doing this wrong, but i followed your simple example from the npm page https://www.npmjs.com/package/node-crud and am having two problems:

require-dir is broken at file .\index.js line 93:
if( !require.extensions.hasOwnPropterty(ext))

when using a suggested fix to change it to
(if !Object.prototype.hasOwnProperty.call(require.extensions,ext))
and using your simple example:
------------------file: index.js --------------
var crud = require('node-crud'),
express = require('express'),
app = express();
// set up some express middleware
app.use(require('body-parser').urlencoded({ extended: true }));
app.use(require('body-parser').json());
// Let's create our first Crud API route
crud.entity('/users').Read()
.use(function(req, res, next) {
// express middleware capability
next();
})
.pipe(function(data, query, cb) {
cb(null, [ { name: 'bobby tables' } ]);
});
crud.launch(app);
app.listen(3000);
express says cannot get "/api/users/"
there are no other errors or messages thrown by this so i dont know whats going on but wanted to let you know that this  seems broken on node 8

@jjmo18

For the require-dir issue, this a package we do not manage here. Perhaps it's broken. All our active stuff us using node v7.5.0, and I will not have any time soon to address this. Feel free to submit a pull request using something other than require-dir, or submit a pull request to them to fix their issue.
Try hitting /api/users instead of /api/users/

Correct. On Windows path.join creates backslashes not forward slashes. I'll make a PR to fix this.

https://github.com/uhray/crud/pull/4

#4

Note: I've tested<EMAIL_ADDRESS>(latest at time of comment) and it seems to operate fine. If there are any bugs present in the version of require-dir node-crud is using, updating is an option. (Currently node-crud uses require-dir@0.1.0).


CCryptoBoringSSL: add Windows generated assembly

This adds the generated assembly files for Windows.  Unfortunately, the
x64 generated assembly appears to be ELF-esque and SYSV ABI rather than
Win64.  Additionally, the ARM targets do not seem to generate valid
Windows ARM code either (quick perusal shows at least invalid SP
handling on ARMv7 NT and non-conforming prologues on AArch64).  Add x86
Windows assembly only for the time being.
[One line description of your change]

Checklist

[ ] I've run tests to see all new and existing tests pass
[ ] I've followed the code style of the rest of the project
[ ] I've read the Contribution Guidelines
[ ] I've updated the documentation if necessary

If you've made changes to gyb files

[ ] I've run .script/generate_boilerplate_files_with_gyb and included updated generated files in a commit of this pull request

Motivation:
[Explain here the context, and why you're making that change. What is the problem you're trying to solve.]
Modifications:
[Describe the modifications you've done.]
Result:
[After your change, what will change.]

Hmm, I'm surprised the x86_64 asm isn't right, as BoringSSL uses it on Windows for things like Chromium. Did you try asking for nasm instead of coff?

Using nasm would introduce a new dependency for building.  I think that after the next re-branch, might be good to try the masm variant.

I'm definitely mostly interested in what we can arrange for clang to actually build, so I'm fairly relaxed about what we end up doing here.


Creates a new flagset to avoid conflit with other libraries that use the same flag

…the same flag
https://github.com/DataDog/dd-trace-go/issues/1153
:question: What
Baker library conflicts with dd-trace-go library because of dependencies on glog.
glog also defines the flag v
panic: /var/folders/yg/7bk34drs0zjfsb9b_r_1sykr0000gn/T/go-build2940344100/b001/exe/main flag redefined: v
This PR make possible to use both libraries side by side.
It's not possible to send PR to glog because it's a Google internal library that does not accept contributions. But dd-trace-go and also ristretto have dependencies on it.
:hammer: How to reproduce the error
Try to import both libraries at the same time:
package main

import (
	"fmt"

	"github.com/AdRoll/baker"
	"gopkg.in/DataDog/dd-trace-go.v1/ddtrace/tracer"
)
func main() {
	tracer.Start(
		tracer.WithEnv("testing"),
		tracer.WithService("tags-automation"),
	)
	defer tracer.Stop()
	components := baker.Components{}
	if err := baker.MainCLI(components); err != nil {
		fmt.Println(err.Error())
	}
}

produces the error:
panic: /var/folders/yn/hdtb3wnd5xg31ygy3vt2g99w0000gn/T/go-build2429850215/b001/exe/testing flag redefined: v

goroutine 1 [running]:
flag.(*FlagSet).Var(0x140000bc120, {0x1059befb8, 0x140004814a8}, {0x1053ac54c, 0x1}, {0x10540798b, 0x1d})
        /usr/local/go/src/flag/flag.go:980 +0x2a4
flag.(*FlagSet).BoolVar(...)
        /usr/local/go/src/flag/flag.go:715
flag.(*FlagSet).Bool(0x0?, {0x1053ac54c, 0x1}, 0x0, {0x10540798b, 0x1d})
        /usr/local/go/src/flag/flag.go:728 +0x70
flag.Bool(...)
        /usr/local/go/src/flag/flag.go:735
github.com/AdRoll/baker.MainCLI({{0x0, 0x0, 0x0}, {0x0, 0x0, 0x0}, {0x0, 0x0, 0x0}, {0x0, ...}, ...})
        /Users/danimar.ribeiro/go/pkg/mod/github.com/!ad!roll/baker@v0.1.0-alpha/baker_cli.go:35 +0xec
main.main()
        /Users/danimar.ribeiro/Projetos/extra/baker-test/testing.go:17 +0xb4
exit status 2

:white_check_mark: Checklists

[X] Have the changes in this PR been functionally tested?
[X] Has make gofmt-write been run on the code?
[X] Has make govet been run on the code? Has the code been fixed accordingly to the output?
[X] Have the changes been added to the CHANGELOG.md file?

Codecov Report

Merging #213 (d5df4c5) into main (40a57bc) will increase coverage by 7.32%.
The diff coverage is 76.63%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #213      +/-   ##
==========================================
+ Coverage   53.95%   61.28%   +7.32%
==========================================
  Files          60       67       +7
  Lines        4003     4972     +969
==========================================
+ Hits         2160     3047     +887
- Misses       1646     1687      +41
- Partials      197      238      +41

Impacted Files
Coverage Δ

api.go
100.00% <ø> (ø)

baker.go
0.00% <0.00%> (ø)

baker_cli.go
0.00% <0.00%> (ø)

filter/clausefilter.go
73.50% <0.00%> (+1.18%)
:arrow_up:

filter/clear_fields.go
75.00% <0.00%> (+10.71%)
:arrow_up:

filter/dedup.go
90.32% <0.00%> (+1.86%)
:arrow_up:

filter/expand_json.go
96.61% <0.00%> (+0.45%)
:arrow_up:

filter/format_time.go
97.91% <0.00%> (+0.11%)
:arrow_up:

filter/hash.go
77.55% <0.00%> (+0.46%)
:arrow_up:

filter/metadata_lastmodified.go
89.47% <0.00%> (+0.58%)
:arrow_up:

... and 103 more

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 1d34ab0...d5df4c5. Read the comment docs.


Remove contract_ from contract_storage_reads and update requests and rename StorageUpdateRequest to StorageWrite

Update: We have a PublicDataWrite and a PublicDataUpdateRequest types. Doing this renaming would cause a collision so it's probably not worth doing.


Add Ajax csrf_token to base.html

Add this code to base.html
  <script>
    $.ajaxSetup({
      data: {csrfmiddlewaretoken: '{{ csrf_token }}'},
    });
  </script>

this allow easy use Ajax forms + csrf token

can help too: https://stackoverflow.com/questions/5100539/django-csrf-check-failing-with-an-ajax-post-request

Quoting from the documentation

All subsequent Ajax calls using any function will use the new settings, unless overridden by the individual calls, until the next invocation of $.ajaxSetup().

If I am reading this correctly, if you make any ajax call that will contain request data (i.e. overriding the data parameter), and this is highly likely, then you would need to specify the csrf token again. Therefore, there is little benefit to add it by default.

no, this add csrfmiddlewaretoken token to data dict, so if you already use JQuery and use data usual this not must be problem)

@demestav agreed with you.
However, there is a better solution for CSRF and jQuery ajax, which is also mentioned in django's docs.
If you think that having an X-CSRFToken header with a csrftoken value in every ajax call1 will give some benefits to this project, then the suggestion from Django's docs could be a solution for this issue.
1 except those((GET|HEAD|OPTIONS|TRACE)) which doesn't require CSRF protection


Explanatory no results on Workflow A.3

https://arax.ncats.io/?source=ARS&id=0623c772-5cab-4eeb-bc32-df92e30dc4d0
Both predicates

{
  "description": "Unsupported query structure.",
  "logs": [],
  "message": {
    "knowledge_graph": {
      "edges": {},
      "nodes": {}
    },
    "query_graph": {
      "edges": {
        "e01": {
          "object": "n0",
          "predicates": [
            "biolink:entity_negatively_regulates_entity",
            "biolink:negatively_regulates_entity_to_entity"
          ],
          "subject": "n1"
        }
      },
      "nodes": {
        "n0": {
          "categories": [
            "biolink:Gene"
          ],
          "ids": [
            "NCBIGene:23221"
          ]
        },
        "n1": {}
      }
    },
    "results": []
  },
  "status": "Unsupported",
  "validation_result": {
    "message": "",
    "n_edges": 0,
    "n_nodes": 0,
    "size": "1 kB",
    "status": "PASS",
    "version": "1.1.1"
  }
}

Explanatory Agent currently doesn't support the predicate "biolink:entity_negatively_regulates_entity" & "biolink:negatively_regulates_entity_to_entity". We are in the process of a major design update and would be able to answer these queries post-implementation (expected by September Relay).


Not building under linux 386

I'm compiling my program for my friend who has a 32-bit machine. When I run go get, go build etc, I get this:
$ GOARCH=386 go get

# github.com/hajimehoshi/oto
../../.local/go/pkg/mod/github.com/hajimehoshi/oto@v0.3.1/context.go:63:12: undefined: newDriver
../../.local/go/pkg/mod/github.com/hajimehoshi/oto@v0.3.1/context.go:120:18: undefined: driver

Specifying GOARCH explicitly disables CGO. What about specifying CGO_ENABLED=1?

Yes, that solves it, along with installing the 32-bit shared lib for
libasound (multilib/lib32-alsa-lib on Arch). Thanks, should I add
this to the README/docs?
On 20/06/12 11:33pm, Hajime Hoshi wrote:

Specifying GOARCH explicitly disables CGO. What about specifying CGO_ENABLED=1?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/hajimehoshi/oto/issues/113#issuecomment-643578859

I'm glad that you have solved the issue!

should I add this to the README/docs?

I didn't think so as this is a Go's issue. However, at the same time, this is FAQ and kind of a trap for Oto users. I'll accept a PR change if you'd like :-)
If you do, please add a link https://golang.org/cmd/cgo/#hdr-Using_cgo_with_the_go_command and quote this:

The cgo tool is enabled by default for native builds on systems where it is expected to work. It is disabled by default when cross-compiling. You can control this by setting the CGO_ENABLED environment variable when running the go tool: set it to 1 to enable the use of cgo, and to 0 to disable it.


Documentation: POST restorePoints Azure SQL DW REST API

I think the POST restorePoints REST API needs to be documented in the REST API documentation page (see link at the bottom in the Content Source). That's the REST API equivalent of New-AzureRmSqlDatabaseRestorePoint. It was mentioned here:
https://azure.microsoft.com/en-us/blog/quick-recovery-time-with-sql-data-warehouse-using-user-defined-restore-points/
I think it also needs to be documented at the following link. This link currently has the GET restorePoints REST API to list the restore points of an Azure SQL DB (or DW) but not the POST to create a new restore point.
https://docs.microsoft.com/en-us/rest/api/sql/restorepoints/listbydatabase
While we are on the topic, I think the REST API equivalent of Remove-AzureRmSqlDatabaseRestorePoint may also need to be documented.

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

ID: 95eb3903-d171-d3c9-180e-a49e14522f27
Version Independent ID: 44cece14-8e57-4d3b-6e5c-2a8ffe719be5
Content: Pause, resume, scale with REST in Azure SQL Data Warehouse
Content Source: articles/sql-data-warehouse/sql-data-warehouse-manage-compute-rest-api.md
Service: sql-data-warehouse
GitHub Login: @kevinvngo
Microsoft Alias: kevin

Adding @kevinvngo

By the way, here's an ADFv2 example of creating a user-defined restore point (a "backup") of your DW:
https://github.com/furmangg/automating-azure-sql-dw/blob/master/README.md#backupazuresqldw

Please share the link to REST API to create Sql DW restore point

https://docs.microsoft.com/en-us/azure/sql-data-warehouse/sql-data-warehouse-restore-database-rest-api

I think above link is to restore the datawarehouse. csn you please share the link to create user defined restore point

Hi Prashanth,
We’re looking into why the REST API doc was not automatically generated. If you are currently blocked, the REST call is exactly like the GET (https://docs.microsoft.com/en-us/rest/api/sql/restorepoints/listbydatabase) but in the PUT, in the request body, you provide the label name:
{"RestorePointLabel" : "myname"}

This is currently being tracked as a product defect as the REST API is automatically created.

#please-close


Cleanup and correct third-party drivers doc

Cleaned Up And Corrected Third-Party Drivers Document
Description

Moved StratusLab's PyPi package link to the correct row
Made source link for Snooze use consistent naming with other source links (include GitHub username)
Tightened table spacing
Rearranged links in footer to maintain grouping by provider
Removed version number from PyPi link

Status

done, ready for review

Checklist

[ ] Code linting (required, can be done after the PR checks) [No Code Changes]
[X] Documentation
[ ] Tests [No Code Changes]
[X] ICLA (required for bigger changes)

Thank you @danhunsaker! Merged in trunk. ✨


Evaluation using DSR

Is the evaluation of DSR done on CPU?
Whenever I do the evaluation my whole 32 GB gets filled up
Do I need to change anything in the code or config file to du the inference on GPU?
Because I see in the code that you append the .cpu().numpy() features in M = []
So my whole memory is getting filled up

I think there is a serious issue in the inference of PartiallReID
DSREvaluation is done on CPU which is disrupting the RAM. If you can optimize it , it would be of a great help
While evaluating the PartialReID training on big datasets like Market1501, it is impossible to do so

Due to the GPU space limitation，it cannot save the spatial features. So we first save these spatial features in CPUs. And then compute DSR on GPUs by converting numpy to tensor.

@xiaomingzhid
So we cant use the DSR features for big datasets?
I wanted to train and test the fast-reid PartialReID on Market1501 dataset

We have tried experiments on large databases, there is no problem, you can try

My whole RAM gets filled up 32 G on Market1501?
Is there any hack you can suggest?

Do your CPUs only have 32 G? Our CPUs have 216 G. If you want to test using DSR, you save the spatial features on hard disk or increase your cpu memory.

For calculcation I need to load the features in hard drive. So it will create the same issue right?
Is there any solution where I can use dsr in parts. i.e Get some chunks of spatial features and calculate it with query images

Three suggestions you could try:

feature channel could be reduced to 512 (ours is 2048). But it may reduce the accuracy.
add sever CPU memory
save the gallery spatial features in hard disk and store these gallery features separately. If you want to use these spatial features, you can load them separately.

Thanks a lot @xiaomingzhid
Do you have the results of PartialReID trained on Market1501 and tested on Market1501?
If you can just provide me the benchmark then it would be of a great help.

You could find some useful results in this paper: https://openaccess.thecvf.com/content_ICCV_2019/papers/He_Foreground-Aware_Pyramid_Reconstruction_for_Alignment-Free_Occluded_Person_Re-Identification_ICCV_2019_paper.pdf.

@xiaomingzhid  Thanks a lot.
I solved it with some small workaround as my use-case was pretty based on an only a small set of gallery images at the time of inference.
Thanks again for your help. I am closing the issue


Navigate and redirects

HTML's navigate algorithm invokes fetch and asks it to not follow redirects. Service workers however do not have this primitive so will follow redirects. This results in e.g. a request for /foo ending up with a response from some other origin potentially. I guess that's all okay?

I think it's OK, but we need to understand how a developer might want to handle it. I've seen reports of OAuth redirect flows running afoul of this.

Actually, in some other ticket we ended up restricting this. A request for /foo needs a same-origin or synthetic response. See #590.
Of course, redirects still happen even though HTML sets redirect mode to "manual". This can be problematic if the URL redirected to is to be handled by the navigate algorithm in some manner rather than Fetch (e.g. a skype URL or some such).

We fixed this with redirect "manual".


Landscape Slider, and System Info Widgets

#9 #14
(Sorry about all the spam PR's btw. I have no idea what I'm doing.

Issue: Sun not in alignment when adjusting slider.


Write Readme file

Currently, The readme file only contains the name of the repository. It should contain more informations.

Add description
Change header name

Ich versteh kein wort...


701 Update DS and CA versions

this is basically catching up with #668
I thought a bit about whether the component versions should be the same as for 3.7.2 or different, and in the end decided to use the same component versions as the API is the same (ABI is a different topic, but I'm not sure whether that should play into the VERSION here). If you disagree, please let me know what you would prefer.
The example change and the slightly different overall VERSION update from #668 I already merged when setting the overall VERSION to 3.6.1.

Codecov Report

Merging #750 (a17d4cc) into c++14-compliant (8476383) will decrease coverage by 0.64%.
The diff coverage is n/a.

Additional details and impacted files

@@                 Coverage Diff                 @@
##           c++14-compliant     #750      +/-   ##
===================================================
- Coverage            90.56%   89.91%   -0.65%
===================================================
  Files                  250       90     -160
  Lines                13554     6286    -7268
===================================================
- Hits                 12275     5652    -6623
+ Misses                1279      634     -645

Impacted Files
Coverage Δ

framework/src/bundle/BundleRegistry.cpp
79.60% <0.00%> (-11.97%)
:arrow_down:

framework/src/service/ServiceEvent.cpp
71.79% <0.00%> (-5.76%)
:arrow_down:

...mework/src/service/ServiceReferenceBasePrivate.cpp
86.45% <0.00%> (-5.64%)
:arrow_down:

framework/src/service/ServiceRegistrationBase.cpp
77.66% <0.00%> (-4.24%)
:arrow_down:

framework/src/util/FrameworkEvent.cpp
61.81% <0.00%> (-3.94%)
:arrow_down:

framework/src/bundle/BundleResourceBuffer.cpp
67.34% <0.00%> (-3.86%)
:arrow_down:

framework/src/service/ServiceListeners.cpp
96.26% <0.00%> (-3.74%)
:arrow_down:

framework/src/util/Utils.cpp
75.58% <0.00%> (-3.32%)
:arrow_down:

framework/src/bundle/BundleResourceContainer.cpp
92.08% <0.00%> (-3.29%)
:arrow_down:

framework/src/bundle/BundleEvent.cpp
85.00% <0.00%> (-3.00%)
:arrow_down:

... and 230 more


Add sandstone mining into the bot

🚀 Feature Proposal - Sandstone mining
Currently the only way to obtain buckets of sand is from killing kalphite queen in the bot. This is slow and doesn't really reflect the main way people obtain these ingame. Sandstone in game can be mined and then grinded into buckets of sand. This would allow buckets of sand to be obtained and used for making molten glass through a reasonable and realistic method.
ty for coming to my tedtalk

Hi, first of all thanks for your ted talk.
Even though it could be a good addition, u can +collect sand too now 👍🏼


chore(main): release 0.37.5

:robot: I have created a release beep boop
0.37.5 (2023-06-08)
Bug Fixes

deps: update dependency go_router to v8 (#347) (feedc60)
deps: update kotlin monorepo to v1.8.22 (#345) (df2697b)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/CCXXXI/ecg_monitor/releases/tag/v0.37.5 :sunflower:


Type matching error when executing a UDF of "timestamp" type via substrait

Describe the bug, including details regarding any error messages, version, and platform.
I used this test to invoke a UDF via substrait that inputs and outputs "timestamp":
https://github.com/icexelloss/arrow/blob/pyarrow-udf-timestamp-type/python/pyarrow/tests/test_substrait.py#L449
And hit with this error:
>   raise ArrowNotImplementedError(message)
E   pyarrow.lib.ArrowNotImplementedError: Function 'y=ceil(x)' has no kernel matching input types (timestamp[us, tz=UTC])
E   /home/icexelloss/workspace/arrow/cpp/src/arrow/compute/exec/expression.cc:548  call.function->DispatchBest(&types)
E   /home/icexelloss/workspace/arrow/cpp/src/arrow/engine/substrait/relation_internal.cc:550  des_expr.Bind(*input.output_schema)
E   /home/icexelloss/workspace/arrow/cpp/src/arrow/engine/substrait/serde.cc:212  FromProto(root_rel.has_root() ? root_rel.root().input() : root_rel.rel(), ext_set, conversion_options)
E   /home/icexelloss/workspace/arrow/cpp/src/arrow/engine/substrait/util.cc:48  DeserializePlan(substrait_buffer, registry, nullptr, conversion_options)

After some debugging, I found this ultimately hit this comparison (between the input data type declared by the kernel and the data type of the actual input) and failed:
https://github.com/icexelloss/arrow/blob/pyarrow-udf-timestamp-type/cpp/src/arrow/compare.cc#L1375
I printed the left_fp and right_fp values in the debugger, they are different, but I cannot make sense of what they mean:
print left_fp
(const std::basic_string<char, std::char_traits<char>, std::allocator<> >) $3 = {
  _M_dataplus = (_M_p = "@Sn3:UTC")
  _M_string_length = 8
   = (_M_local_buf = "@Sn3:UTC\0\xd1LwkU", _M_allocated_capacity =<PHONE_NUMBER>044199232)
}
print right_fp
(const std::basic_string<char, std::char_traits<char>, std::allocator<> >) $4 = {
  _M_dataplus = (_M_p = "@Su3:UTC")
  _M_string_length = 8
   =
 (_M_local_buf = "@Su3:UTC\0\"\xb3wkU", _M_allocated_capacity =<PHONE_NUMBER>044657984)
}

Component(s)
C++

Figured this out. The issue was that Acero translates substrait timestamp_tz to timestamp[us, UTC] and the function is defined as timestamp[ns, UTC], which result in a mismatching.

This is technically not a "bug" but the error message can certainly be improved

What error message would have been useful here?

"Expected type x, got type y" ?

Ideally, something like:
"Input/output type of function y=ceil(x) does not match between substrait plan and the function definition. Substrait plan: Timestamp[ms], function definition: Timestamp[ns]"


feat: speed and re-rendering optimisations

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Optimizing Rendering of parts, with focus on rounding errors, and durationSettling after a take
Speed optimization - "now" time is rounded for 25fps

What is the current behavior? (You can also link to an open issue here)
When take the new part stops for a second

What is the new behavior (if this is a feature change)?
Registering take and use "now" instantly as the new take.

Other information:

Status

[ ] Code documentation for the relevant parts in the code have been added/updated by the PR author
[x] The functionality has been tested by the PR author
[ ] The functionality has been tested by NRK

Codecov Report

Merging #530 (a0a0d6c) into release35 (e7b0e05) will increase coverage by 32.16%.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           release35      #530       +/-   ##
===============================================
+ Coverage      67.83%   100.00%   +32.16%
===============================================
  Files            252         2      -250
  Lines          15193        40    -15153
  Branches        3369        14     -3355
===============================================
- Hits           10306        40    -10266
+ Misses          4720         0     -4720
+ Partials         167         0      -167

Impacted Files
Coverage Δ

packages/blueprints-integration/src/context.ts
100.00% <ø> (ø)

packages/blueprints-integration/src/util.ts
100.00% <0.00%> (ø)

meteor/lib/collections/PeripheralDevices.ts

meteor/lib/api/playout.ts

...eteor/server/api/playout/lookahead/findForLayer.ts

meteor/server/migration/1_11_0.ts

meteor/lib/collections/CoreSystem.ts

meteor/server/api/ingest/expectedMediaItems.ts

meteor/lib/logging.ts

... and 203 more

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 6df9784...a0a0d6c. Read the comment docs.

Looking very interesting. Haven't had time to do a proper review, but I've made some quick code quality comments.

@jstarpl also look into the calmDownTiming used in onRefreshTimer, right now it´s set to 40ms (1 * 25fps) but i think the best performance contra GUI updates is around 70ms. To see what it does, try setting it at 1000ms

The conflict in SegmentTimelineContainer.tsx is because i´ve removed the playbacksimulation, as it gets the new "take" imidiately.

<<<<<<< r35/timing-rendering-optimize
=======
				const simulationPercentage = this.playbackSimulationPercentage
>>>>>>> release36


Purchases

Purchases are not importing for the steakhouse restaurants.

Looks like the problem might be with ubiquitious-train.  not all the purchases are loading.  Its looks like the steak purchases from Stockyards that are keyed in manually (which is all the steakhouses and JD) are not importing.

run.py needs to be updated to match yearly-table-update.  for some reason yearly-table-update is working correctly but not run.py


Bolt Chats Disappeared

I wrote code in Bolt and it is gone. I paid for subscription, was developing code in Bolt, and now it is all gone. Please help me get it back.

Appreciate the feedback! We are aware of this issue with chat persistence. Temporary workarounds and updates can be found here: #39. (Go to stackblitz.com, login (same credentials as Bolt), click Collections on the left-hand side, click Bolt Collection). Appreciate your patience as improvements continue to be made.


Add first browser test for ErrorBar

What

Add the first browser test for ErrorBar. Takes care of boilerplate.
To aid code sharing, refactor the browser tests so far into a reusable fixture.

Why
'cause I don't wanna test manually.
How Tested
rushx test:e2e:chat

@anjulgarg This PR conflicts in a big way with #594
Let's land that one first. I'm happy to rebase this on top and refactor the tests added in #594 as well.

@anjulgarg This PR conflicts in a big way with #594
Let's land that one first. I'm happy to rebase this on top and refactor the tests added in #594 as well.

Merged #594


[NTR] esophagus nonkeratinized squamous epithelial cell

Note - please check that the term does not already exist (check OLS: https://www.ebi.ac.uk/ols/ontologies/cl)
Preferred term label:
esophagus nonkeratinized squamous epithelial cell
Synonyms
esophageal nonkeratinized squamous epithelial cell
nonkeratinized squamous epithelial cell of esophagus
oesophageal nonkeratinized squamous epithelial cell
nonkeratinized squamous epithelial cell of oesophagus
Definition (free text, please give PubMed ID in format PMID:XXXXXX)
Any cell that is part of the esophageal nonkeratinizing stratified squamous epithelium. The esophagus, which requires flexibility to accommodate swallowing of a bolus, is covered with a nonkeratinizing epithelium. PMID:11694559
Parent cell type term (check the hierarchy here https://www.ebi.ac.uk/ols/ontologies/cl):
non keratinizing barrier epithelial cell
What is the anatomical structure that the cell is a part of? Please check Uberon: https://www.ebi.ac.uk/ols/ontologies/uberon
Your nano-attribution (ORCID)
Any additional notes or concerns
CL already has keratinized squamous cell of esophagus but I think this may be incorrect -- the reference that is listed in the definition only seems to say that esophagus squamous epithelium is nonkeratinizing so possibly this is a typo.

Hi @mkeays, it appears that the linked PR has been closed. Can we close this ticket?


fix: add mk_all to Lint style

See Zulip

The actual issue has been discovered and resolved by Ruben's #16699, so I am closing this PR.

I wonder if this could save contributors a tiny bit of time in the situtation where they have added new files but forgotten to add them to Mathlib.lean? Then with the current workflows those new files would not be linted until after they saw the complaint from lake exe mk_all at the very end of the build job and then pushed a new commit fixing that.
(If we want to go with something like this PR, then we may have to adjust the lint and suggest and bot fix style workflows to be consistent with the changes here as well).

Now that I look at it more closely, the "lint and suggest" workflow runs lake exe mk_all in a parallel job, which saves even more time at the cost of using more (Github hosted) runners.

I also had #14077, but was not really happy with it, even though it was delegated.  If you think that it is fine, I can merge master and then bors r+ it!


367 | Valid Perfect Square | Python

Valid  Perfect Square -
What will change -
Type of Issue -

Adding New Code

Programming Language

Python

Self Check

Ask for issue assignment and wait to get assigned to it before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Discord server ✉ - https://discord.gg/CXksGdn
Happy Coding,

Please assign it to me @SSKale1

Please assign it to me @SSKale1

Can i work on this please?

[x] Assigning to @JayeshSareen for issue creation.


Update reschedule on node fail

Describe the proposed changes

From Swarm code ,wo can see that the env about reschedule is splited by semicolon, the links https://github.com/docker/swarm/blob/master/cluster/config.go#L35
Unreleased project version

Related issue

Related issue or PR in another project

Please take a look

Update reschedule on node fail

Deploy preview ready!
Built with commit ebb924c3620cfce3b3f1d1a2e119cdbb322c6cba
https://deploy-preview-592--docker-docs.netlify.com

@sanscontext @mstanleyjones @londoncalling @joaofnfernandes WDYT ?


Add parser tests for gateway API L4 routes

Is there an existing issue for this?

[X] I have searched the existing issues

Problem Statement
Currently parser package does not provide any tests for UDPRoute,  TCPRoute and TLSRoute
Those are in alpha right now, so it's understandable it was not the top priority.
Proposed Solution
Implement parser tests for UDPRoute,  TCPRoute and TLSRoute
Additional information
No response
Acceptance Criteria

[ ] UDPRoute translation into kong config is tested in dataplane parser package
[ ] TCPRoute translation into kong config is tested in dataplane parser package
[ ] TLSRoute translation into kong config is tested in dataplane parser package

It can be now easily covered with introducing of test cases and expected results in internal/dataplane/parser/testdata/golden - golden tests approach


Date range for Teaching Page

Is it possible to provide a date range for the teaching page? For example, if I want to say that I taught a course from 2020-09-25 to 2024-05-01 how would I write this in the Date section of the teaching .md file?

The date field of the Markdown file determines the order chronologically, so a range really isn't possible in that field. Right now this is by design, but is there a reason why it would make more sense to have a range in the date field as opposed to elsewhere in the teaching page?

Thank you for explaining it to me. It probably doesn't make sense to have a range in the date field, I just wanted to check if there was a workaround. Thank you :)


Add MongoDB and Cassandra in travis/azure test automation

Overview of the feature request

Add travis/azure tests for 'cassandra', 'mongodb', 'couchbase'
Motivation for or Use Case

I am doing a PR at https://github.com/jhipster/jhipster-vuejs/pull/434 and hence would like to have validated against all DBs types.
Was there any issue for these DBs or simply not added yet?
If it is the latter case, I can do a PR.
Related issues or PR

[x] Checking this box is mandatory (this is just to show you read everything)

Plz, I'd prefer Azure, rather than Travis, as we'll remove the builds with Travis

Of course, Travis tests should be removed as they are so slow.


Add image or special font for the title

Is your feature request related to a problem? Please describe.
No, just a way to make the presentation better.
Describe the solution you'd like
The title on the intro.md page should stand out and be centered.  This could be done by adding an image or a different font.
Describe alternatives you've considered
The alternative is to leave the title as it is using the top level markdown and the same arial font.
Additional context
An example if in the intro page of Chronos.

As a resolution, I will center the header, but otherwise not change it.  For a more colorful book, I will use font awesome icons that come with Jupyter Book.


Bump package-publisher action version

Attempting to fix https://github.com/pulumi/pulumi-openstack/issues/340

@aq17 Did you merge an associated PR in ci-mgmt?

@iwahbe the changes are already in ci-mgmt; they have not been applied here because of dirty worktree failures in the action-upgrade PRs.


Docs/GitHub previous link gave 404

to: @chunyong-lin
cc: @airbnb/streamalert-maintainers
related to:
resolves:
Background
The previous link gave a 404, as the page did not exist. I believe the url i have set is the one it was describing?
Changes

Changed the link provided

Testing

make html - Opened produced documentation in my browser

Coverage remained the same at 96.143% when pulling d8989e2d1cc2fcba37fde3713fcd01b988b16d95 on jack1902:docs/github into 875aeb4b53786f68d82df2e6192535ee3caf2a27 on airbnb:release-3-0-0.


Missing Command Line Tool for HAPI FHIR 1.4

I am not seeing command line tool included in the HAPI FHIR 1.4 release. any help? thanks.

Attached I extracted from cli 1.3, and it works for cli 1.4
sh-bat.zip


vue3: Correct way to use in setup?

I'm trying to use vue-lang-router with vue 3 using programmatic routes but I get all kind of strange errors.
If I understand right, vue-lang-router is not compatible with useRouter() ? I cannot find a way to import vue-lang-router in the setup.
One of the error I get often is :
Uncaught (in promise) TypeError: this.$i18n is undefined
Wich sends me to this bit of code:
  mounted() {
            /* istanbul ignore if */
            if (((process.env.NODE_ENV !== 'production') || __INTLIFY_PROD_DEVTOOLS__) && !false) {
                this.$el.__INTLIFY__ = this.$i18n.__composer;
                const emitter = (this.__emitter = createEmitter());
                const _vueI18n = this.$i18n;
                _vueI18n.__enableEmitter && _vueI18n.__enableEmitter(emitter);
                emitter.on('*', addTimelineEvent);
            }
        },

This is what I'm doing :
import { useRouter } from 'vue-router'

…
setup() {
    const router = useRouter()
    return {
       router
    }
}
…

…
    // later in an event
    router.push({
      name: 'write/story',
    })
…

Hi @sheoak, right now vue-lang-router doesn't support usage inside Composition API.

I see… do you have a workaround @radek-altof ? I have many call to router in my composables and it would take quite a lot of refactoring to change this.

@radek-altof actually after some more tests I have this error even if I don't use composition API.
This simple link:
 <router-link to="/fr/bureau">test</router-link>
Trigger this error:
Uncaught (in promise) TypeError: this.$i18n is undefined
But it doesn't happen if just load the page and click on the link. I need to come back to the page and click on it, then I get the error.
I'm using keep-alive around my router component as well as components key in my route (with an s). My route components are loaded async like so:
const ProjectsIndex = () => import('@/views/ProjectsIndex')

Yeah, sandbox would definitely be helpful, thanks. As for some workaround for Composition API, I don't think there's anything, sorry. It's going to require some coding. I don't have the necessary free time now to dive into experiments with Composition API, so probably only in the future.

So in the end it's seems it's not related to vue-lang-router but to vue-i18n. It seems to be related to my layout system so I will consider it's not a vue-lang-router bug and close the issue. For those who would have similar errors it seems related to vue-i18n + async layouts in vue 3.


[ASK] Reshape (Custom Dataset)

I'm currently working on a masters project in which I run a number of different models for tweet recommendation. I'm trying to use xDeepFM to no avail and was wondering where I'm going wrong.
I've followed the entire notebook with no problem but I was wanting to use my own data for this. I have an FFM training file with (according to xLearn) Feature Count: 48756, Field Count: 6475. I define this in a yaml file similar to the one provided but run into the following error:
tensorflow.python.framework.errors_impl.InvalidArgumentError: Input to reshape is a tensor with 8287990 values, but the requested shape requires a multiple of 64750
	 [[{{node XDeepFM/Reshape}} = Reshape[T=DT_FLOAT, Tshape=DT_INT32, _device="/job:localhost/replica:0/task:0/device:GPU:0"](XDeepFM/embedding/embedding_lookup_sparse, XDeepFM/Reshape/shape)]]
	 [[{{node Mean/_37}} = _Recv[client_terminated=false, recv_device="/job:localhost/replica:0/task:0/device:CPU:0", send_device="/job:localhost/replica:0/task:0/device:GPU:0", send_device_incarnation=1, tensor_name="edge_293_Mean", tensor_type=DT_FLOAT, _device="/job:localhost/replica:0/task:0/device:CPU:0"]()]]

I was wondering if maybe my training file was malformed but xLearn seems to detect the field/feature counts no problem. Happy to provide any other info, pretty new to all this.
EDIT: Just to clarify, my yaml file is identical to the one in the notebook, aside from the field/feature counts.

Hey @ajhepburn can you provide more details about your data and how it is processed by xLearn?


improve search results

I don't know how else to put this other than that the search functionality kind of sucks right now. I was looking for my post about the voyager records and figured I'd try searching for it instead of scrolling down the page of posts, since it's a bit of an older one. Searching for "voyager", the actual post I was looking for was the last result out of a page of seven total posts. The title of the post in question has "voyager" in it; how is this even possible?
I assume the fix is just to tweak the weights of the keys that Fuse looks for, but I might have to end up looking for a new fuzzy search library. It also might be a good idea to switch the page over to using an edge function rather serverless since you can really feel that cold start when you click on the search icon.

Meant to close this with b9932e2 but typed the wrong issue number again. By default, Fuse.js only searches within the first 60 characters of each string. This means that when I searched for "voyager", Fuse.js didn't know that "voyager" existed in the title of the post, therefore leading to horrible search results. Adding the ignoreLocation option to the search instance fixes this.
I also tried using the edge runtime with Vercel (f3011e4), but it seems like Astro's image engine stuff uses Node.js APIs and using the Vercel image service option didn't work for me either. I hope nobody minds a 2 second cold start when they try to search!
I could always have the search be done on the client, but I don't love the idea of having to send down every single post to the client just to use search. To be fair, "every single post" is only really 88 KB, so it'd have the effect of sending a second copy of React to the client. I don't love that idea.
The search certainly isn't great, but I fixed the glaring problem with it which was the goal of this issue. I'll try to improve search quality and speed in the future.


added the subscription structs for future usage

for future usage of the subscription api i added the structs already.
I dont really know if this pull request will go through because it's code which doesnt do anything (since the resource is not included yet.) But i use them in a 3rd party plugin.
Feel free to discuss :)
The process is the following
https://developer.paypal.com/docs/api/subscriptions/v1/
create a product -> create a plan -> create a subscription -> get response from subscription -> get subscription details.

what do you think about adding the Resource Classes as well?

what do you think about adding the Resource Classes as well?

Well, yes, let me do it step by step :'D

what do you think about adding the Resource Classes as well?

Well, yes, let me do it step by step :'D

ok, we can do this in a separate PR :+1:

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/PT-11986
Please use this issue to track the state of your pull request.

thanks for your contribution @dominikmank  :+1: :tada: :blue_heart:
we made some additional annotations to the new structs to make clear, that they are not used in the plugin itself and are some kind of unofficial :wink:


Fix #27 - Use correct tempate_settings debug default

This fix is superseded by fixes in https://github.com/nedbat/django_coverage_plugin/pull/30


MSRC Portal Doesn't List SQL 2008 Anymore

Hi, the text above says:
ESUs are made available if needed, once a security vulnerability is discovered and is rated as Critical by the Microsoft Security Response Center (MSRC). Therefore, there is no regular release cadence for SQL Server ESUs.
if you look on the MSRC https://portal.msrc.microsoft.com/en-us/security-guidance under SQL the latest version it reports on is now Microsoft SQL Server 2012...there is no report for SQL 2008
Thanks

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

ID: bd3e29e8-6559-58d3-27a5-3c443bd76c94
Version Independent ID: 37b33566-6d93-ca52-7f54-4101ddb3a332
Content: What are Extended Security Updates? - SQL Server
Content Source: docs/sql-server/end-of-support/sql-server-extended-security-updates.md
Product: sql
Technology: install
GitHub Login: @MashaMSFT
Microsoft Alias: mathoma

@scruffty -- thank you for your feedback.
@MashaMSFT -- please look into this issue #4313.

Hi @scruffty , thanks for bringing this to our attention! Let me look into it :)
Thanks!
Masha from the SQL Docs team

Hi @MashaMSFT - they have now re-appeared so I'm guessing this is down to you? If so, thank you!!!