Conditionally include a plugin

Hi, I like the idea of antidote having its own file for plugins, but I have a use case which I'm not sure how to achieve using the "static" file.
Let's say I want to check if a variable is set, and only if that's the case, include a plugin in the list.
My original use case is for powerlevel10k; I'm using different themes on my different computers, and the issue I get is that if I include powerlevel10k in the file, it's loaded automatically, overwriting things.
So, I want to load powerlevel10k based on a variable I set in my config

There's an annotation called conditional that lets you achieve something like this. I use it for loading macOS only plugins like so:
# .zshrc
# define a function
is-macos() {
  [[ $OSTYPE == Darwin* ]]
}

# now load antidote
source /path/to/antidote.zsh
antidote load

And then in your .zsh_plugins.txt
# .zsh_plugins.txt
sorin-ionescu/prezto path:modules/osx conditional:is-macos

So, let's apply this to your situation. Perhaps you are setting the ZSH_THEME variable to whatever prompt you want. You could do something like:
# .zshrc
# define a function
prompt-is-p10k() {
  [[ $ZSH_THEME == 'p10k' ]]
}
# now load antidote
source /path/to/antidote.zsh
antidote load

# .zsh_plugins.txt
romkatv/powerlevel10k conditional:prompt-is-p10k

However, might I suggest a better alternative. Why don't you use Zsh's built in prompt mechanism? Pull themes into your fpath with the kind:fpath annotation. Then, you don't need to set variables - just call prompt powerlevel10k in your .zshrc.
# .zshrc
# load antidote plugins
source /path/to/antidote.zsh
antidote load

# now set your prompt - you can wrap in an `if` statement too if you want
autoload -Uz prompting && promptinit
prompt powerlevel10k

# .zsh_plugins.txt
# kind:fpath will make any prompt you want available to Zsh's built-in prompt system
# as long as that prompt plugin defines a prompt_THEME_setup function
sindresorhus/pure kind:fpath
romkatv/powerlevel10k kind:fpath

Hope this helps. Ping me again if not.

Thank you @mattmc3 for the super quick and comprehensive reply.
Now that I have you here, maybe I can mention the root issue that caused me to start playing around with my config:
I really LOVE antidote, and I find it much faster than the other plugin managers I've tried (honestly, not sure why it doesn't have as much stars as some other popular ones).
Everything was working fine, but recently I noticed that my prompt is actually "tricking" me when using antidote.
I do a lot of stuff in the background when I open a new shell (some hooks running, some commands checking things etc.), but what I mean by "tricking me" is this:
antidote brings me to the prompt, but it's basically blocked when I start typing for, say, 200-300ms and then it reflects what I typed.
I tried experimenting with zplug, and, as I mentioned before, it is slower than antidote, but at least when I see my prompt (which of course takes longer to appear), I can immediately start typing and I see the characters I'm typing.
I think this started happening maybe in the last few weeks, or at least it was barely noticable before.
As I mentioned, I'm doing a bunch of things, so I'm OK with my prompt appearing with a delay, but the fact that it's "fake" is what is driving me crazy.
I'm hoping that you could tell me what I can try with this information to fix the issue (because having a reproducible config is honestly out of the question :slightly_frowning_face: because of the million things I'm doing in a million different files, a bunch of them being company-related things that can't be shared)

I really LOVE antidote, and I find it much faster than the other plugin managers I've tried (honestly, not sure why it doesn't have as much stars as some other popular ones).

Thanks! I suspect most people have long had their preferred plugin manager - antidote is much later to the game and built off the wonderful work Carlos put into antibody.

antidote brings me to the prompt, but it's basically blocked when I start typing for, say, 200-300ms and then it reflects what I typed.

I suspect you are using PowerLevel10k's instaprompt? That's the feature that shows you a quick version of your prompt, but then loads the rest of your config in the background. Do you get the same behavior if you switch to a different prompt (like sindresorhus/pure)? PowerLevel10k is a great prompt - but I suspect this is unrelated to antidote and more to do with the plugins you're loading.
If you are willing to post your config or point me to it, that might help. If not, that's okay - you can also debug Zsh yourself by adding this like to the top of your .zshrc: zmodload zsh/zprof and then running zprof when your prompt is fully loaded. You should see profile metrics that will tell you what's slowing things down.

Unfortunately, this is happening with starship, so it has nothing to do with p10k.
I tried to see if I can see something with zprof, but I'll try again.
Can you think of any reason why the same list of plugins in zplug would yield my prompt ready to type immediately but having the blocking behavior I mentioned in antidote?

No, I cannot. That's really weird. I use starship myself and have had great luck with it and have never seen that behavior.

Can you think of any change made recently (in the past month maybe) that might affect this?
Right now, I'm playing with my plugins.txt for antidote, and as I disable the plugins I have there, that delay seems to be decreasing, so I guess that means that it has something to do with those?
Literally dumping my file here, just in case it might be of help:
https://github.com/zsh-users/zsh-completions
https://github.com/belak/zsh-utils path:completion

https://github.com/ohmyzsh/ohmyzsh path:lib
# https://github.com/ohmyzsh/ohmyzsh path:plugins/azure          kind:defer
https://github.com/ohmyzsh/ohmyzsh path:plugins/docker         kind:defer
https://github.com/ohmyzsh/ohmyzsh path:plugins/docker-compose kind:defer
https://github.com/ohmyzsh/ohmyzsh path:plugins/fancy-ctrl-z   kind:defer
https://github.com/ohmyzsh/ohmyzsh path:plugins/git            kind:defer
# https://github.com/ohmyzsh/ohmyzsh path:plugins/terraform      kind:defer
https://github.com/ohmyzsh/ohmyzsh path:plugins/git-auto-fetch kind:defer

# For some reason, this just randomly puts the region in the prompt!!!
# https://github.com/ohmyzsh/ohmyzsh path:plugins/aws kind:defer

https://github.com/romkatv/powerlevel10k kind:fpath

https://github.com/ael-code/zsh-colored-man-pages
https://github.com/Aloxaf/fzf-tab
https://github.com/ChrisPenner/copy-pasta
https://github.com/djui/alias-tips
https://github.com/jeffreytse/zsh-vi-mode
https://github.com/marlonrichert/zsh-edit
https://github.com/mtxr/zsh-change-case
https://github.com/zsh-users/zsh-autosuggestions

https://github.com/hlissner/zsh-autopair                      kind:defer
https://github.com/zdharma-continuum/fast-syntax-highlighting kind:defer

# Disable; contributes to prompt delay!
# https://github.com/bilelmoussaoui/flatpak-zsh-completion      kind:defer

# vim: ft=zsh

As I continue playing, starship seems to be the culprit. As I said, I run a lot of things, so I expect things to be a bit slow, but it seems like antidote is not "waiting" for things and showing me the prompt, but starship needs more time, so the prompt is blocked (seems like zplug is actually waiting for that "more time")
Sorry, I know you're like "what a stupid thing to say", but I'm trying to be like a good patient mentioning all the symptoms, hoping that something is found

Oh, I see where the issue is. You are using kind:defer on nearly everything. Roman has been pretty clear that while zsh-defer may work well for some plugins, it can also cause some very hard to track down problems. See https://github.com/romkatv/zsh-defer#caveats. Roman has gone so far as to say he doesn't recommend using it at all and recommends PowerLevel10k with instaprompt. But I have found that, when used sparingly, zsh-defer can be useful.
I would recommend pulling the kind:defer annotations off and adding back only if you have a plugin that's slow and might benefit from it, and only one at a time so as to verify the rest of your config works.

OMG!, THANK YOU @mattmc3, I still have a tiny delay for the prompt, but it's barely noticable (at least for my use case, it's fine) :rocket:

However, I have a new problem :stuck_out_tongue_closed_eyes: ; I tried "un-deferring" everything, and I saw these errors:
zsh-syntax-highlighting: unhandled ZLE widget 'reverse-yank-pop'

cp: cannot create regular file ‘/home/farzadmf/.zplug/repos/robbyrussell/oh-my-zsh/cache//completions/_docker’: No such file or directory

First error
This seems to be the reason for the first unhandled ... one:
+_zsh_highlight_bind_widgets:54> [[ reverse-yank-pop == zle-* ]]
+_zsh_highlight_bind_widgets:59> print -r -- 'zsh-syntax-highlighting: unhandled ZLE widget '\''reverse-yank-pop'\'

zsh-syntax-highlighting: unhandled ZLE widget 'reverse-yank-pop'

If I https://github.com/zdharma-continuum/fast-syntax-highlighting kind:defer, the first error (unhandled ...) seems to be gone, but I think the error shouldn't happen with defer, right?

Second error
Tried zsh -x, and I see this line seems to be causing the cannot create ... error:
/local/home/farzadmf/.cache/antidote/https-COLON--SLASH--SLASH-github.com-SLASH-ohmyzsh-SLASH-ohmyzsh/plugins/docker/docker.plugin.zsh:58> cp /local/home/farzadmf/.cache/antidote/https-COLON--SLASH--SLASH-github.com-SLASH-ohmyzsh-SLASH-ohmyzsh/plugins/docker/completions/_docker /home/farzadmf/.zplug/repos/robbyrussell/oh-my-zsh/cache//completions/_docker

cp: cannot create regular file ‘/home/farzadmf/.zplug/repos/robbyrussell/oh-my-zsh/cache//completions/_docker’: No such file or directory

Seems like antidote is trying to copy something to ~/.zplug directory?? :thinking: It's most probably me messing things up, but I've no idea what!
And docker completion fails with (when I press TAB):
(eval):1: _docker: function definition file not found

For the first error, the path being referenced is .zplug, so there's something residual from when you used that plugin manager. I use zdharma-continuum/fast-syntax-highlighting kind:defer in my own config with great success, so if that's working for you go for it.
You might also want to start fresh - it looks like there's a lot of residual cruft. Check that your antidote home is storing the repos where you really want them. Removing your static plugins file and running rm -rf -- $(antidote home) to start fresh might also help you troubleshoot.

I do have the plugin (fast-syntax-highlighting) and it's kind:defer. In my effort to "un-defer" everything, I wanted to also remove defer from it, but I guess I can't
Regarding the docker completion issue, I looked around and saw that they're relying on ZSH_CACHE_DIR to be set (and also OMZ seems to set ZSH as well), so I ended up setting the value to a directory I'm using (and add the completions sub-directory to fpath), and it seems to be working fine


debian/ubuntu groupadd fails inside container when run rootless

/kind bug
Description
Executing "groupadd foo" within a debian or ubuntu container fails when run by rootless podman but works when run by root/sudo podman (podman run from RHEL8). I'm not sure if this is a bug or an indication https://github.com/containers/libpod/blob/master/rootless.md should get updated and maybe an enhancement should be made. Either way, I found this behavior surprising and confusing.
The impact of this is that many debian/ubuntu packages will fail to get-apt install when run inside a rootless container because many packages will have some dependency that will run groupadd within an install script (e.g. dbus package).
In addition to "debian:10.2" I also repro with more recent "debian:bullseye-20200130" and "ubuntu:19.10" and "ubuntu:focal-20200115".
Steps to reproduce the issue:

as non-root run podman run -it --rm library/debian:10.2

inside container run groupadd foo

Describe the results you received:
groupadd: /etc/group.7: lock file already used
groupadd: cannot lock /etc/group; try again later.

Describe the results you expected:
Expected it to succeed with no output which is what happens when running the same podman command but as root/sudo.
Output of podman version:
podman version 1.6.4

Output of podman info --debug:
debug:
  compiler: gc
  git commit: ""
  go version: go1.12.12
  podman version: 1.6.4
host:
  BuildahVersion: 1.12.0-dev
  CgroupVersion: v1
  Conmon:
    package: conmon-2.0.6-1.module+el8.1.1+5259+bcdd613a.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.6, commit: 6ffbb2ec70dbe5ba56e4bfde946fb04f19dd8bbf'
  Distribution:
    distribution: '"rhel"'
    version: "8.1"
  IDMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
  MemFree: 472834048
  MemTotal:<PHONE_NUMBER>
  OCIRuntime:
    name: runc
    package: runc-1.0.0-64.rc9.module+el8.1.1+5259+bcdd613a.x86_64
    path: /usr/bin/runc
    version: 'runc version spec: 1.0.1-dev'
  SwapFree:<PHONE_NUMBER>
  SwapTotal:<PHONE_NUMBER>
  arch: amd64
  cpus: 4
  eventlogger: journald
  hostname: ham.home
  kernel: 4.18.0-147.5.1.el8_1.x86_64
  os: linux
  rootless: true
  slirp4netns:
    Executable: /usr/bin/slirp4netns
    Package: slirp4netns-0.4.2-2.git21fdece.module+el8.1.1+5460+3ac089c3.x86_64
    Version: |-
      slirp4netns version 0.4.2+dev
      commit: 21fdece2737dc24ffa3f01a341b8a6854f8b13b4
  uptime: 15h 53m 12.89s (Approximately 0.62 days)
registries:
  blocked: null
  insecure: null
  search:
  - private.dkr.ecr.us-east-1.amazonaws.com
  - registry.redhat.io
  - registry.access.redhat.com
  - quay.io
  - docker.io
store:
  ConfigFile: /home/castedo/.config/containers/storage.conf
  ContainerStore:
    number: 4
  GraphDriverName: overlay
  GraphOptions:
    overlay.mount_program:
      Executable: /usr/bin/fuse-overlayfs
      Package: fuse-overlayfs-0.7.2-1.module+el8.1.1+5259+bcdd613a.x86_64
      Version: |-
        fuse-overlayfs: version 0.7.2
        FUSE library version 3.2.1
        using FUSE kernel interface version 7.26
  GraphRoot: /home/castedo/.local/share/containers/storage
  GraphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  ImageStore:
    number: 44
  RunRoot: /run/user/1000
  VolumePath: /home/castedo/.local/share/containers/storage/volumes

Package info (e.g. output of rpm -q podman or apt list podman):
podman-1.6.4-2.module+el8.1.1+5363+bf8ff1af.x86_64

@giuseppe Potentially fuse-overlayfs? Is this a bug we know about already?

it works for me both with fuse-overlayfs 0.7.2 and with the version from git master, it could be something different.
@castedo could you try the following:
$ podman run  --name foo -it --rm library/debian:10.2
from another terminal:
$ strace -o /tmp/strace.log -f -Z -p $(PID of the shell inside the container, you can get it from runc list)
then run again the groupadd inside of the container.  After it fails, kill the strace process and please attach here the /tmp/strace.log file

Thanks for looking at it!
I attach two because the first one (strace.log) was after a fresh reboot and showed a new error (below). The second one (strace2.log) was a repeat soon afterwards without the error.
strace.log
strace2.log
Error that results from first run after fresh reboot (immediately upon running podman run):
ERRO[0000] Error refreshing volume castedo.conf: error acquiring lock 0 for volume castedo.conf: file exists
Let me know if you want more details on where this castedo.conf comes from and why it's showing up. At the moment I don't know why that error is happening on the first run.


[NVIDIA] Fix Unit Tests

Description
Changes:

Previously in release mode some of Unit Tests expected to crash with ASSERT_DEATH, but after switching to OPENVINO_ASSERT which always throws exception it is not anymore a case
Updated MatMul test which not always converts to FP16

@nkogteva I suggest to enable Unit Tests for NVIDIA plugin by default, to avoid such thing in future


New language for OWNERS?

Should OWNERS file have their own language?
For instance, this file https://github.com/kubernetes/apimachinery/blob/master/Godeps/OWNERS returns an empty language selection.
According to this post it's a YAML file but we fail to identify it.

this is really nice, but enry relies on github/linguis for language detection - by design, it supports only the things that linguist does support by auto generating Go code using exactly same heuristics as linguist.
So I would say this request need to be filed upstream.

Closing in favor of umbrella #181


Update ErrorCodes to agree with #2412 from tock.

This updates libtock-c's values for ErrorCodes from the kernel to agree with https://github.com/tock/tock/pull/2412 .

bors r+


Error while running initial backup

Saw this error during an initial backup.  Rerunning started from where it left off.
Running under Ubuntu 20.04 as a Proxmox LXC.
D, [2020-10-22T07:54:56.843152 #312] DEBUG -- : [INBOX] uid: 61446 (12214/20208) - 43660 bytes
Traceback (most recent call last):
        25: from /usr/local/bin/imap-backup:23:in `<main>'
        24: from /usr/local/bin/imap-backup:23:in `load'
        23: from /var/lib/gems/2.7.0/gems/imap-backup-2.2.2/bin/imap-backup:73:in `<top (required)>'
        22: from /var/lib/gems/2.7.0/gems/imap-backup-2.2.2/lib/imap/backup/configuration/list.rb:18:in `each_connection'
        21: from /var/lib/gems/2.7.0/gems/imap-backup-2.2.2/lib/imap/backup/configuration/list.rb:18:in `each'
        20: from /var/lib/gems/2.7.0/gems/imap-backup-2.2.2/lib/imap/backup/configuration/list.rb:20:in `block in each_connection'
        19: from /var/lib/gems/2.7.0/gems/imap-backup-2.2.2/lib/imap/backup/account/connection.rb:49:in `run_backup'
        18: from /var/lib/gems/2.7.0/gems/imap-backup-2.2.2/lib/imap/backup/account/connection.rb:90:in `each_folder'
        17: from /var/lib/gems/2.7.0/gems/imap-backup-2.2.2/lib/imap/backup/account/connection.rb:90:in `each'
        16: from /var/lib/gems/2.7.0/gems/imap-backup-2.2.2/lib/imap/backup/account/connection.rb:93:in `block in each_folder'
        15: from /var/lib/gems/2.7.0/gems/imap-backup-2.2.2/lib/imap/backup/account/connection.rb:54:in `block in run_backup'
        14: from /var/lib/gems/2.7.0/gems/imap-backup-2.2.2/lib/imap/backup/downloader.rb:15:in `run'
        13: from /var/lib/gems/2.7.0/gems/imap-backup-2.2.2/lib/imap/backup/downloader.rb:15:in `with_index'
        12: from /var/lib/gems/2.7.0/gems/imap-backup-2.2.2/lib/imap/backup/downloader.rb:15:in `each'
        11: from /var/lib/gems/2.7.0/gems/imap-backup-2.2.2/lib/imap/backup/downloader.rb:16:in `block in run'
        10: from /var/lib/gems/2.7.0/gems/imap-backup-2.2.2/lib/imap/backup/account/folder.rb:68:in `fetch'
         9: from /var/lib/gems/2.7.0/gems/imap-backup-2.2.2/lib/imap/backup/account/folder.rb:91:in `examine'
         8: from /usr/lib/ruby/2.7.0/net/imap.rb:470:in `examine'
         7: from /usr/lib/ruby/2.7.0/monitor.rb:202:in `mon_synchronize'
         6: from /usr/lib/ruby/2.7.0/monitor.rb:202:in `synchronize'
         5: from /usr/lib/ruby/2.7.0/net/imap.rb:472:in `block in examine'
         4: from /usr/lib/ruby/2.7.0/net/imap.rb:1255:in `send_command'
         3: from /usr/lib/ruby/2.7.0/monitor.rb:202:in `mon_synchronize'
         2: from /usr/lib/ruby/2.7.0/monitor.rb:202:in `synchronize'
         1: from /usr/lib/ruby/2.7.0/net/imap.rb:1273:in `block in send_command'
/usr/lib/ruby/2.7.0/net/imap.rb:1213:in `get_tagged_response': end of file reached (EOFError)

Hi @borpin,
It looks like this is a network-induced error. I agree that the error message EOFError is not very helpful, but as it's happening in Net::IMAP, there's not much we can do.

@borpin This is fixed in version 3.2.0


[Epic] Warehouse box management

[ ] Make a box #18
[ ] Find a box #20
...

Just gonna close this because it isn't very useful right now and will just be out of date.


MINOR: remove kafka-preferred-replica-election.sh in doc

We've removed kafka-preferred-replica-election.sh in https://github.com/apache/kafka/pull/10443 , but we forgot to update the doc. Fix it.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@dajac , one line PR to fix the doc script. Please take a look. Thanks.

Thanks @dajac !

@showuon You’ve put yourself as reviewer of the PR :).

Oh... NO!! Sorry! Should we do anything to it?

No worries. It happened to me as well. You can’t do much for it.


Prepare for migration to the new backend

We've been hard at work re-writing the backend for Jupyter Book and we are getting close to having a version that is ready to test out here. The codebase is different enough that I think it is worth "starting fresh", partially because the current Jupyter Book repo is like 40mb because of all the notebooks and images and such.
However, I want to make sure folks here are OK with this first, particularly those with lots of commit histories in the current master branch. How do people feel about the following steps:

Add the new jupyter-book code as a remote to the jupyter-book repo
Add a migration guide for the new version
Pull that code into a beta branch and release it as a public beta for Jupyter Book
Once the beta is ready for a full release:

Move the current jupyter-book master code to a legacy branch
Replace master with the beta branch entirely (AKA, with a git reset --hard command

That way, we have history preserved in the legacy branch, and we retain all of the issues etc that are currently in there (for which many could now be closed).

In particular I want to make sure that @emdupre and @SamLau95 and @martinagvilas are OK with this!

This plan sounds good to me! Excited for the improvements.
A list of changes (esp. backwards-incompatible changes) would be helpful for future migrations.

@SamLau95 good point, I'll make that explicit in the todo list

Sounds good! And also agree with @SamLau95 about the list of changes. I'm in the process of migration with the Turing-Way, so any unnoticed change that I can spot I will report 😄

This all sounds good to me !
Only clarification: do you think there's a point in maintaining the legacy branch over just merging in the new build system to master ? I ask as I'm wondering if we'd accept eg bug fixes there.
If there's no plan to update it (just want to keep track of history), I'd vote we just merge them, personally ! We recently did a similar merge of two repositories with unrelated histories in Nistats/Nilearn.

I think the mean reason not to merge into master is because the history of the current master branch is pretty beefy (lots of images, notebook files with artifacts, etc) whereas the new jupyter-book repo is much more streamlined (very few images, all text files, etc). I think it's a difference between about 40mb for a clone vs. what'll be more like 10mb or so.
Another question for the group - I'm not sure if it's the right idea or not, but how do folks feel about potentially moving this repository to the ExecutableBookProject org? Most of the other Jupyter Book dependencies are in there as well, and I think the EBP is in some ways a more natural fit for Jupyter Book as the steward of the project (rather than Jupyter which has like 100 other repositories in this org). I can see pros and cons to both, but curious what y'all think.

I think the mean reason not to merge into master is because the history of the current master branch is pretty beefy (lots of images, notebook files with artifacts, etc) whereas the new jupyter-book repo is much more streamlined (very few images, all text files, etc).

I definitely get that, but I think it's possible to clean a git history of specific files. if that's not of interest, though, no worries !

how do folks feel about moving this repository to the ExecutableBookProject org?

I'm fine with that, personally !

@emdupre let me look into how much work it would be. The codebase is quite different, so another factor in this is "whether or not this will take a day of Chris' life to figure out" 😆

nobody has suggested that we shouldn't move this repository to ExecutableBookProject, so I will plan to do this later today or tomorrow unless somebody objects (and please feel free to!)

OK, step one is done - I've got a checklist at the top to follow. Fingers crossed that it goes smoothly :-)  @emdupre if I end up needing to spend 3 days figuring out how to merge new changes in then you owe me a 🍺 :-)

I think I owe you one anyway :smile_cat:
And happy to help, as it's useful !

this is now done! you can install the pre-release with:
pip install -U jupyter-book --pre

Test it out and give feedback y'all!
Check out the in-progress upgrade guide here: https://github.com/ExecutableBookProject/jupyter-book/issues/504
cc @kirtiejane @emdupre @SamLau95 @martinagvilas


[NEW ICON]: Desktop Environments & Tiling Window Managers

Skill Name
KDE, i3wm, Gnome...
Why?
It's pretty much saying everything about your setup and how you work on your computer, so having this information is very interresting to have
Reference Image

Code of Conduct Aknowledgment

[x] I have read and agree to the Code of Conduct.

It would be interresting to get other wm or de in the same pull request for a better comprehension from others, if you know what I mean


remove atlas folder

There's no Atlas folder to compile there.

For there to be an atlas folder, you need to make in externals

ok, thanks


Manually setting Blade syntax to the old way means you can't use blade comments

(in app service provider)
And I hate it.
Want to undo the custom Blade templates in app service provider, and then just find anywhere in the site we need to output un-escaped. Which is likely nowhere.

How to handle this:
Delete these two lines:
https://github.com/tightenco/symposium/blob/master/app/Providers/AppServiceProvider.php#L23-L24
Then look through all of our views to figure out if any of the {{ }} blocks are expecting to allow HTML -- if they are, adjust them to use the new {{!! syntax.


release 2.0.0

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.111%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
135

Relevant Lines:
140

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.111%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
135

Relevant Lines:
140

💛  - Coveralls


BloomFilter broken on Edge > 38

After some initial digging, it seems that the 'range' value of the LuminosityMaterial needs to be defined as a 2d Vector rather than null, if no range is specified.
I haven't had time to build out an example case but if this is something you want to address, I'll happily expand on this tomorrow when I have a dab more time!

Sounds interesting!
I don't use Edge, so I'll rely on your findings. Also, reverting 4428c91 might just do the trick.

Ahh! That's basically the exact change I made in my brief test.
Our project had to support Edge and pressed for time, we just ended up disabling Bloom. It would be neat to get to the bottom of though, it seems like all other postprocessing filters work great in Edge!

I reverted said commit since it's better to avoid null uniforms altogether, The fix is included in v2.1.1.
The BloomPass should now work in Edge, so I'm closing this for now. If it's still broken, let me know!


Allow paths after the status code

One of the apps I'm working with uses ElasticSearch, and I was adding better support for HTTP errors, so I decided to use httpstatus for my unit tests. The app automatically appends additional paths to the URL to retrieve data from ElasticSearch, so it was trying to access http://httpstat.us/405/_cat during testing, but the httpstatus service doesn't support random paths on the end of the URL.
I found a workaround in my code to strip the paths, but If this is something that may be handy in the httpstatus site, I can take a shot at a pull request. It's been a few years since I did any serious ASP.NET work, but it would come back pretty quick.

Waiting for this as well.

Closing as I think we added this a while ago (like, the link above works as expected)


[request] Allow overriding of request configuration on fluent request builders

Describe the feature
Hi all!
We have a feature request on vector to allow setting the x-amzn-logs-format HTTP header to json/emf when publishing events to CloudWatch Logs via PutLogEvents to send embedded metrics.
I found an example of doing it with the Java SDK:
PutLogEventsRequest putLogEventsRequest = PutLogEventsRequest.builder()
                        .overrideConfiguration(builder ->
                                // provide the log-format header of json/emf
                                builder.headers(Collections.singletonMap("x-amzn-logs-format",  Collections.singletonList("json/emf"))))
                        .logEvents(Collections.singletonList(inputLogEvent))
                        .logGroupName(logGroupName)
                        .logStreamName(logStreamName)
                        .sequenceToken(sequenceToken)
                        .build();

But I don't see a similar sort of method for overriding request headers for the Rust SDK. Am I missing something? Or would this be a feature request?
Use Case
Overriding request headers on a per API call-basis.
Proposed Solution
Add a method to all fluent builders that allows overriding request configuration including headers.
Here is what the Java SDK seems to support overriding:
https://sdk.amazonaws.com/java/api/latest/software/amazon/awssdk/core/RequestOverrideConfiguration.html
Other Information
No response
Acknowledgements

[ ] I may be able to implement this feature request
[ ] This feature might incur a breaking change

A note for the community

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue, please leave a comment

Thanks for submitting this, I have an idea of how to support this and I'll run it by the team to see what they think.

@jszwedko The way to accomplish this task today is to:

Have users construct the operation directly (i.e. not using the fluent builder)
Call Operation::into_parts to get access to the inner request
Add the header to that request
Reconstruct the operation by calling Operation::from_parts
Send the operation off using a smithy client

That's obviously not a very friendly experience. The much nicer solution would require adding a new API to allow converting a fluent builder into some type Sendable<O> (this type doesn't exist and doesn't necessarily need to be named Sendable) that has methods for modifying the inner operation and updating operations with an Operation::augment method that allowed users to pass a callback that would modify the inner parts of an op.
@rcoh imagines the UX looking like this:
let sendable = dynamodb.list_tables().limit(5).<workshop work here>();
sendable.map_operation(|op| op.augment(...).send().await;

We'd need an RFC proposal covering all this before moving forward with a PR. I'm currently absorbed in checksum work relating to S3 but I may be able to look at this afterwards. I can't give any time estimate or guarantee though.
If you're interested in writing and submitting an RFC for this, we can coach you on the process. Let me know if that's how you'd like to proceed.

Thanks for the response @Velfi ! I missed that the request could be split into parts and reconstructed. We can give that a shot. Otherwise that UI you mentioned looks decent to me to be able to compose the operations similar to what the Java SDK allows for.

I have a PR implementing John's RFC that should make things much nicer.

It is now possible with the latest SDK to add this header. Take a look at the notes for release-2022-09-21 for an example.


[M10-364] Implemented Ogury SDK - Banners - Interstitials - Rewards

M10-364
M10-400
M10-401
Description, Motivation and Context
What is the goal of ticket?  What are the acceptance criteria?
Integrate Ogury SDK - Interstitials
How Has This Been Tested?
Manually tested App Build
Does this change require updates outside of the code, like updating the documentation, adding a feature flag, or adding fields to a DB table? If so, was this done?
N/A
Any tickets that this is dependent upon?
N/A
Should reviewers manually test your changes?
No
Evidence

Confirmed we are going to use Asset Key OGY-374D2BA758F4 @kkawai @maddapper


Add Dockerfile

Could we have a Dockerfile for jupyterlab? Or it's preferred that put it in other repos such like https://github.com/jupyter/docker-stacks. I'm willing to help to add one.

Hi @waitingkuo, I think docker-stacks would be the best location.

Agreed. @waitingkuo - do you want to open an issue over in the docker-stacks repo? Thanks for the suggestion!

I'll open an issue there, thanks


Spp-117-nl

Description
spp-117-nl klaar voor review
Hier is gerenderde pdf spp_117_nl_abiotiek_waterlopen.pdf

Related Issue

Task list

Steps by contributor:

[x] Add description to this pull request (under "## Description")
[x] Open the dropdown (triangle) near 'create pull request' and choose 'Create draft pull request'
[x] Check for potential problems by running protocolhelper::check_frontmatter() and address them
[x] Check for potential problems by running protocolhelper::check_structure() and address them
[x] Add further commits if needed and push them to GitHub
[x] Update the protocol-specific NEWS.Rmd
[x] Mark the pull request as 'ready for review'

Review steps for the author(s):

[x] Add reviewers, at least one subject-matter specialist and one administrator
[x] Wait for review comments and address them
[ ] Iterate until reviewer approvals (merging the pull request will be done by an administrator)
[ ] Verify that the checks done by continuous integration succeeded. These will check if protocolhelper::check_frontmatter() and protocolhelper::check_structure() succeeded without errors.

To be done by an administrator after review: see guidelines for admins.

@karenwuyts hier is nog een protocol van het MNM project. De gerenderde versie:
spp_117_nl_abiotiek_waterlopen.zip
Het is klaar om gereviewed te worden.

Small suggested changes in 02, 04, 05 and 06. In addition, the title could be more in analogy with spp-116-nl: ‘Abiotische staalname in stromende oppervlaktewateren’; given that this is a project-specific protocol, should the project name be mentioned in the title?

@anleyssen Wat denk jij?


Make secret Lock page

Lock page has two buttons: Lock, Unlock
This page can be accessed anytime
If you press lock, the client exchanges a random token with the WS server. The WS server checks for this key on every incoming package.
If it's incorrect, it responds with an error message

Take route from .Env file so nobody can see it in the repo.


allowFontScaling prop add-on

allowFontScaling bool
Specifies whether fonts should scale to respect Text Size accessibility
setting on iOS. The default is true.

Maybe you also should add a new line in the prop-section in README.md with this new prop?


Logging to AWS Cloudwatch

Is your feature request related to a problem? Please describe.
There is no in-built way to stream the logs to AWS CloudWatch.
Describe the solution you'd like
Since Cloudwatch is the main logging system and the log analyzer used by all AWS Services, having it as a direct logging destination would be ideal
Describe alternatives you've considered
The other way I can think of implementing this would be to use the Cloudwatch Logs agent to point to read from the logging folder within the EC2. Or use the AWS CLI, CloudWatch Logs SDK, or the CloudWatch Logs API to push directly from within the code or simplify with an app such as Watchtower
Additional context
Deployment is managed through Terraform with AWS provider

Hi @dumim! Great feature request! How urgent is this for you and when would you need this by?

Hey @dumim , all the logs from the ECS containers should be sent to CloudWatch by default.
The log group is this: https://github.com/mage-ai/mage-ai-terraform-templates/blob/master/aws/main.tf#L31
Could you check whether you can find your logs there?

Hey @dumim , are you able to find the cloudwatch logs from the log group I mentioned above?

@dumim I'm going to close ticket. Feel free to reopen the ticket if you still have issues with the logs.

@wangxiaoyou1993 Thank you! I glossed over this part, that will work for us at the moment. We are still in the process of setting up Mage, will report back once deployed.


Compilation fails if using lld

In my ~/.cargo/config.toml, I have the following entry:
[target.x86_64-unknown-linux-gnu]
linker = "clang"
rustflags = ["-Clink-arg=-fuse-ld=lld"]

to improve link times and iteration speed. However, this seems to break linkme compilation, badly.
Here's a snippet from the error message during compilation:
  = note: ld.lld: error: undefined symbol: __start_linkme_BENCHMARKS
          >>> referenced by 29qlfu0bgl5pi1ii
          >>>               /home/meatball/coding/linkme/target/debug/deps/example-d6ac051010cd24ec.29qlfu0bgl5pi1ii.rcgu.o:(example::BENCHMARKS::h84fb1b0801cd0cb3)
          >>> the encapsulation symbol needs to be retained under --gc-sections properly; consider -z nostart-stop-gc (see https://lld.llvm.org/ELF/start-stop-gc)

          ld.lld: error: undefined symbol: __stop_linkme_BENCHMARKS
          >>> referenced by 29qlfu0bgl5pi1ii
          >>>               /home/meatball/coding/linkme/target/debug/deps/example-d6ac051010cd24ec.29qlfu0bgl5pi1ii.rcgu.o:(example::BENCHMARKS::h84fb1b0801cd0cb3)

          ld.lld: error: undefined symbol: __start_linkm2_BENCHMARKS
          >>> referenced by 29qlfu0bgl5pi1ii
          >>>               /home/meatball/coding/linkme/target/debug/deps/example-d6ac051010cd24ec.29qlfu0bgl5pi1ii.rcgu.o:(example::BENCHMARKS::h84fb1b0801cd0cb3)
          >>> the encapsulation symbol needs to be retained under --gc-sections properly; consider -z nostart-stop-gc (see https://lld.llvm.org/ELF/start-stop-gc)

          ld.lld: error: undefined symbol: __stop_linkm2_BENCHMARKS
          >>> referenced by 29qlfu0bgl5pi1ii
          >>>               /home/meatball/coding/linkme/target/debug/deps/example-d6ac051010cd24ec.29qlfu0bgl5pi1ii.rcgu.o:(example::BENCHMARKS::h84fb1b0801cd0cb3)
          clang-14: error: linker command failed with exit code 1 (use -v to see invocation)

Update: updating the linker entry to use the following seems to make all the tests compile and pass.
[target.x86_64-unknown-linux-gnu]
linker = "clang"
rustflags = ["-Clink-arg=-fuse-ld=lld", "-Clink-arg=-z", "-Clink-arg=nostart-stop-gc"]

Leaving the issue open as a request for this to be documented

I changed the title of #49 to remove the impression it's specific to FreeBSD.


request_id  attribute for generic response

Depends on https://github.com/Avarok-Cybersecurity/Citadel-Protocol/pull/218
This allows us to use .request_id on any incoming response, which makes it much easier (and quicker) to access response ids from incoming messages.
Let me know if there is any way I can restructure this.

This commit already has this attribute for responses and requests: https://github.com/Avarok-Cybersecurity/citadel-internal-service/pull/40/commits/f6cc31b1bad2d4e41e323d9053a03160ded6d20d
Ignore the diff for citadel-messaging/src


Use <> instead of != for not equal operator.

This makes not equal operations work correctly and includes a test.

sorry, i completely missed this! Thanks!


Another round of changes

I'm so sorry to make you go through this:

For the ones to accept, I have commented with OKAY.
For the ones to not accept, I have commented with DELETE/IGNORE.
There is one that I'm not sure what to do with, and I commented as such. I lean toward ignoring it.

I'll close this and cherry pick the commits that are still relevant


Improve SQL parsing of character literals (quoted strings)

Impact

[x] Bug fix (non-breaking change which fixes expected existing functionality)
[ ] Enhancement/New feature (adds functionality without impacting existing logic)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
This fixes an SQL parsing issue where a certain character sequence inside a quoted character literal (aka quoted string) is incorrectly tokenized (premature end-of-string detection), leading to errors executing the SQL command(s) on the database host.  The issue affects users of MySQL, Postgres, and possibly other DBs.
Also, a SQL character literal test pattern which fails without this update is added to the SimpleSqlGrammarTest.groovy to confirm the fix and prevent future reversion.
Things to be aware of
Per https://github.com/highlightjs/highlight.js/issues/1748

Some SQL implementations support only quote-char-twice as an escaped-quote, others only support backslash-quote, some support both, and sometimes it is configurable.
This means it is not possible to always conclusively identify quoted text boundaries without context about SQL platform and configuration.
A real fix is possibly to invoke a block of code defined in SimpleSqlGrammar.jj to dynamically check for false-positive matches on S_CHAR_LITERAL.

A related complication is that '\' is sometimes a valid string literal, and sometimes it is not.
A similar issue in a different SQL parser using JavaCC is mentioned here: https://github.com/JSQLParser/JSqlParser/issues/1172.

It was fixed, in theory, here: https://github.com/JSQLParser/JSqlParser/pull/1715/files#diff-d323df58a0300a038ac87b328bf05b8255ff06e6b5d0e9aeae641fa566e4068c
That fix may be overly specific to one SQL platform, but the core approach of adding a block of Java code (ala Lex) might be feasible.

Things to worry about
There are inconsistencies between different DB platforms in what is considered valid character literal syntax.  Strings that are valid on one type of server may not be valid on another, and vice versa.  This makes platform-agnostic end-of-string detection imprecise.  Please test this very thoroughly on multiple DB platforms.
On the other hand, the current parser logic exposes MySQL, Postgres, and possibly other DBs to errors and/or unintended SQL command execution.
It may be that the truly correct fix involves detection of DB platform and configuration options.
Additional Context
The character pattern that this fixes was distilled out of changeSets that work correctly with MySQL 5.7 and Liquibase 3.5.4.  I have not tested all the intervening releases to see exactly where it stopped working.

Hello @erasmussen-first ! Thanks for the PR.
We have one failed integration test . It's a mysql test, and it fails when running the following SQL:
CREATE PROCEDURE insert_shop ()
INSERT INTO shop
VALUES
(1,'\'',3.45),
(1,'B',3.99),
(4,'\"',19.23),
(4,'\'\"',10.00)
;

CREATE FUNCTION f_insert_shop ()
RETURNS VARCHAR(20)
DETERMINISTIC
BEGIN
INSERT INTO shop
VALUES
(5,'\'',3.45),
(5,'B',3.99),
(7,'\"',19.23),
(7,'\'\"',10.00);
RETURN ('STRING');
END
;

It is failing because it is not able to find the delimiter ";" to split the String into 2 SQLs, then it bundles it all together and we have a failure.
I managed to reproduce the issue adding the following line to the unit test file:
        "'a\'b;c\nd'"                                          | ["'a\'b;c\nd'"]

Notice that this is almost the same test that you added, but instead of using double \  I'm using just one.  I tried some options but wasn't able to "fix" it.. any ideas?

Thanks.  I suspect the \' and \" within the same string are not handled correctly.  I'll try to adjust the patterns later today.

Hi @erasmussen-first ! thanks for the change, but it still not passing this check. I added the verification to the unit tests files so we are able to validate it using github build.

That's very strange.  It seems to be is working here with the pattern that I though you added in your comment.  It may be that GitHub comments are turning a double backslash into a single backslash and I misinterpreted what you said.  I'll merge in the latest master to make sure I'm not missing something else and try again with the new pattern added to the test.

Thanks @erasmussen-first !


add should use the name of the project if no name is provided

Currently add has a mandatory name argument. This should be optional. The default should be parsed from the git url.

Thought is also to reverse the order (  instead of  ) to better match git clone semantics


[Bug] Synthetic Suites not working in Docker Examples

The provided heartbeat.docker.yml includes a synthetic_suites pointing to examples/todos, however this is failing to find the playwright-core:
2020-10-29T09:37:53.101Z	INFO	synthexec/synthexec.go:240	Running command: /usr/share/heartbeat/.node/node/bin/npx @elastic/synthetics /opt/examples/todos --dry-run --json --network --outfd 3 in directory: '/opt/examples/todos'
2020-10-29T09:37:54.310Z	INFO	synthexec/synthexec.go:288	Command has completed(0): /usr/share/heartbeat/.node/node/bin/npx @elastic/synthetics --inline --screenshots --json --network --outfd 3
2020-10-29T09:37:58.656Z	INFO	synthexec/synthexec.go:336	stderr: helpers.ts(4,22): error TS2307: Cannot find module 'playwright-core' or its corresponding type declarations.
2020-10-29T09:37:58.656Z	INFO	synthexec/synthexec.go:336	stderr:
2020-10-29T09:37:58.675Z	ERROR	synthexec/synthexec.go:284	Error waiting for command /usr/share/heartbeat/.node/node/bin/npx @elastic/synthetics /opt/examples/todos --dry-run --json --network --outfd 3: exit status 1
2020-10-29T09:37:58.675Z	INFO	synthexec/synthexec.go:288	Command has completed(1): /usr/share/heartbeat/.node/node/bin/npx @elastic/synthetics /opt/examples/todos --dry-run --json --network --outfd 3
2020-10-29T09:37:58.675Z	WARN	synthexec/synthexec.go:295	Error executing command '/usr/share/heartbeat/.node/node/bin/npx @elastic/synthetics /opt/examples/todos --dry-run --json --network --outfd 3': exit status 1

As a result, the Todos monitor is not running.
Trying to run it from an interactive bash session into the running container, you get the same issue
../../../opt/examples/todos/helpers.ts:4:22 - error TS2307: Cannot find module 'playwright-core' or its corresponding type declarations.
4 import { Page } from 'playwright-core';
                       ~~~~~~~~~~~~~~~~~

Done via #126


Microsoft Edge Support

[x] Go through release checklist (see issue)
[x] Add to package.json/build scripts etc
[x] Go through docs
[x] Publish

[x] Go through with CoilDev "draft" but don't publish
[x] Publish "Coil" extension

[x] Need 300x300 png logo
[x] Need 440x280 promotional tile

[x] Await Review

Published:
https://microsoftedge.microsoft.com/addons/detail/ljionajlbinlfkdnpkloejeoogfgkojm?hl=en-US


fix: updated wording on hint in step 42 of Learn String Manipulation by Building a Cipher

Checklist:

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

Closes #XXXXX

Does not close but is tied to issue #54430

Thank you for working on this PR.
There's a merge conflict there @samGreer, once fixed, we can leave our reviews.

Hey @samGreer
This PR seems to make similar changes as the existing PR #54463. As such, we are going to close this as a duplicate.
If you feel you have additional changes to expand upon this PR, please feel free to push your commits and request this PR be reopened.
Thanks again! 😊

If you have any questions, feel free to ask questions on the "Contributors" category on our forum or the contributors chat room.


Translation to RUSSIAN 2-js-basics > 1-data-types

Should I do anything else to make this PR to be approved and merged?

@leestott Hello! Please review and merge this PR :)


Crash when device name is a number greater thant an integer.

Hi,
I got an error after I added the device named "N010025001001".
When I try to see the devices from the city where that device is, I get a "Django.utils" error saying that the name exceed the integer limits.
The only way to correct this was to delete the device in postgres itself...
Could you check it out?
Thx

This was due to the way we implement natural ordering for device names. This ensures that, for example, a device named router30 shows up between router1 and router100. We do this by casting the trailing numeric portion as an integer and sorting on it separately.
In this case, NetBox was attempting to cast the number<PHONE_NUMBER>1 as an integer, which is too big to fit the type (the maximum value of a signed four-byte integer is<PHONE_NUMBER>). I've adjusted the regex to match only up to nine digits, which ensures that the captured value can be converted to an integer. This approach can likely be improved, but be should be sufficient in the short term.


Update Composer dependencies (2020-08-03-00-05)

Visual regression test passed!
View the visual regression test report


[EXPIRIMENTAL] Cancel fiber

This PR is WIP about an idea @clue and I discussed a while ago to see if t would be possible to make fibers cancelable. In practice, or specifically this implementation, this means you can either prevent it from being started by canceling before it gets executed. Or you cancel any awaited promises once it already started.
Please keep in mind that this is an idea we aren't sure about if it should make it into this package or not yet.

I think this following case would fail 🤔
        $promise = async(function (): int {
            echo 'a';
            await(async(function(): void {
              await(async(function(): void {
                await(sleep(2));
              })());
            })());
            echo 'b';

            return time();
        })();

@WyriHaximus looks good to me, only thing I just noticed is that the description for cancellation is missing inside the functions.php.

@WyriHaximus looks good to me, only thing I just noticed is that the description for cancellation is missing inside the functions.php.

@SimonFrings done :+1:


Default theme causes white text on white background on dark GTK+ theme

Describe the bug 🐛
Dark GTK+3 (used on Gnome specifically) theme set dark-grey background with white text.
This library sets background to white explicitly, but does not set font color, resulting in white on white.
To Reproduce 🔍
Steps to reproduce the behavior:

Install Gnome 3
Enable GTK+3 dark mode (if not enabled)
Create a searchbox input
Type text into the input

Expected behavior 💭
Either don't change background color or also appropriately change font color.
Screenshots 🖥
Default dark GTK+3 behavior:

With instantsearch.js:

Environment:

OS: Linux, Gnome with dark GTK+3 theme
Browser: Firefox
Version: 62

Good call, thanks! We should probably not change the background color I think

Since it's not instantsearch.js is not using the common them of InstantSearch just yet, we need to fix that internally first.

Thanks, I'm probably not the right guy for any frontend, maybe @senseexception would like to pick this up? :wink:

It actually would be as simple as removing
https://github.com/algolia/instantsearch.js/blob/62bac743ab3aa679a4e5f10c6e8534b43e80ffcf/src/css/theme/_search-box.scss#L12
or adding color: $black after it

Okay, looks like a no-brainer that won't take much time.

I guess we should choose to add color: $black instead of removing the background color. In case of websites, that only implemented their own text color but not a background color, removing background: $white might result in similar problems as described by @Majkl578.
If we keep background: $white, the compatibility is still given for those who didn't configured their own background color. Adding color: $black will keep the search-box text readable for every desktop theme.
For the integration on a website, the colors should be set anyway by the designer to prevent off-colored results.

That sounds reasonable @SenseException, adding color: $black seems to be the way to go 👍


API docs

API docs have now been published for the .NET 6 release of MAUI. The conceptual docs need updating so that types link into the API docs. This will be a fairly large task.

This is an on-going task that's been started and is being tracked through individual issues.


Custom dialog styling

Description

Is there a way to style the dialog (like in the original Zendesk SDK)

Device information

Android OS version: 8.0.0
Compile SDK version: <IP_ADDRESS>
Build tools version: 27.0.3
Any other relevant information:
I had a couple of styles defined in the app_theme style: RateMyAppButtonStyle, RateMyAppTitleStyle and RateMyAppDividerStyle. It looks like these have been removed in this sdk. Can they be added back, so the dialog can look the way I'd like it to?

Hi @ahabbaba9,
Styles are still there, only renamed. See https://github.com/zendesk/rate_my_app_android/blob/master/ratemyapp/src/main/res/values/styles.xml#L5.
RateMyAppButtonStyle -> rma_button
RateMyAppTitleStyle -> rma_title
RateMyAppDividerStyle -> rma_divider
Sorry for the inconvenience caused,
Elvis


Added getPrice function

In draft as enums are not complete yet. Basic features are in though.

https://github.com/icastillejogomez/degiro-api/issues/19

https://github.com/icastillejogomez/degiro-api/issues/19

Hi there,
I see a hard coded "userToken" in the code.
You might want to remove that from the project history.

Hi there,
I see a hard coded "userToken" in the code.
You might want to remove that from the project history.

Hi there,
I see a hard coded "userToken" in the code.
You might want to remove that from the project history.

Thanks, done. I assumed/thought it was the same across every account as it still worked after I logged out. Should be removed.

Hi there,
I see a hard coded "userToken" in the code.
You might want to remove that from the project history.

Thanks, done. I assumed/thought it was the same across every account as it still worked after I logged out. Should be removed.

I am getting a Cross-Origin error.
Grund: CORS-Kopfzeile 'Access-Control-Allow-Origin' fehlt
Any idea?

I am getting a Cross-Origin error.
Grund: CORS-Kopfzeile 'Access-Control-Allow-Origin' fehlt
Any idea?

Hi bdoubleu86, please open a new issue next time instead of hijacking a completely different and unrelated issue. As for your problem, see https://github.com/icastillejogomez/degiro-api/issues/23.

Hi there,
I'm looking forward to this feature, and I was wondering what is preventing from accepting this P.R ?
Does it have some remaining work to do ?
How can we help to speed up the merge ?
(sorry, I'm quite new to open source project)

@danielvandenberg95 did you review this code? How do you think about this PR?

Hi all
This PR has been opened for quite some time.
What needs to be done for it to be merged?


Separate execution of trusted getters and trusted calls.

Currently, trusted calls and trusted getters are executed sequentially in the same function. When aura is introduced, this will also consume block production time and getters can only be executed if it's the enclaves slot.
This is not favorable. TrustedGetter execution should be completely independently of trusted calls and also be available if it's not the enclave's slot. This will also increase sidechain-tx's per second.

if it is our slot, only execute calls. only if there is time left, execute getters too
if it isn't our slot, execute getters

Would it make sense, to do #404 first? Separating block production and execution of tops is probably a good basis for this issue?

I think you are correct @mullefel. It will probably simplify the overall workflow if you do #404 first.

After discussing with @clangenb, we decided that we will go with the fully de-coupled solution. That means:

Trusted Getters are run on a separate thread, have their own scheduled slots
Introduction of an RwLock for state access. Getters only need a read lock (of which there can be multiple at the same time)
Slot timings are defined as 100 ms execution, 200 ms idle time

We want a long enough idle time to guarantee that trusted calls can still be executed (#447 will further help with that)
These are just arbitrary values for the start, we might need to fine-tune them later on

I will do some preliminary refactoring PRs before implementing this change:

[ ] Decrypt state only once per shard for trusted getters (currently we load and decrypt the state file for each single getter)
[ ] Cleanup and abstract the access to the state (this will also be necessary for #459)


app: Localize the wording of java code

I localize the wording of the JAVA code.

localize "UNKNOWN" in the remote ID details to "-" to make it clear whether the information is available or not.
I localize help into Japanese.

UNKNOWN

HELP

Thanks. These are really good changes to help make it easier to localize into additional languages. That clearly was not considered when the app was initially developed so it is great to get this supported properly.
This also fixes Issue #60.


[Bug]: The user sees 503 error when he is downgraded from EE to CE by removing the license from license & billing page

Is there an existing issue for this?

[X] I have searched the existing issues

Description
The user sees 503 error when he is downgraded from EE to CE by removing the license from the license & billing page
Steps To Reproduce

go to https://ee-2453.dp.appsmith.com/
Make sure the instance have EE license
now go to admin setting license & billing tab
click on remove license and downgrade
The user sees error on the UI and then the instance goes with 503 error for some time

Public Sample App
No response
Environment
Deploy Preview
Issue video log
No response
Version
v1.9.39

@RakshaKShetty checking if the form login was disabled on this instance before the downgrade happened? This is expected as we haven't handled the downgrade migrations on client side as yet and @dipyamanbiswas07 is planning to pick this up as an upcoming task.

This is fixed


Custom Types

It would be very helpful a way to create custom types and views to avoid fork and miss the project updates.

I think that you can fork and create new types without miss project updates. New types (with new files) would not conflict with current code (or future updates).
Is not easy to create a Type generator, because every type need about 5 different files: Service, icon and 3 views (create, list and update).


Publish 0.4.0 release to NPM

The release 0.4.0 is not available at the NPM.
❯ npm install --save<EMAIL_ADDRESS>npm ERR! Darwin 15.6.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "--save"<EMAIL_ADDRESS>npm ERR! node v5.0.0
npm ERR! npm  v3.10.3

npm ERR! No compatible version found<EMAIL_ADDRESS>npm ERR! Valid install targets:
npm ERR! 0.3.0, 0.2.3, 0.2.2, 0.1.1, 0.1.0, 0.0.8, 0.0.7, 0.0.6, 0.0.5, 0.0.4, 0.0.3, 0.0.2, 0.0.1
npm ERR!
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

Just published it
On Nov 30, 2016 6:36 AM, "Sandro Machado"<EMAIL_ADDRESS>wrote:

The release 0.4.0 is not available at the NPM.
❯ npm install --save<EMAIL_ADDRESS>npm ERR! Darwin 15.6.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "--save"<EMAIL_ADDRESS>npm ERR! node v5.0.0
npm ERR! npm  v3.10.3
npm ERR! No compatible version found<EMAIL_ADDRESS>npm ERR! Valid install targets:
npm ERR! 0.3.0, 0.2.3, 0.2.2, 0.1.1, 0.1.0, 0.0.8, 0.0.7, 0.0.6, 0.0.5, 0.0.4, 0.0.3, 0.0.2, 0.0.1
npm ERR!
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     https://github.com/npm/npm/issues
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/niftylettuce/react-native-loading-spinner-overlay/issues/36,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAf7hQ7Io3_JnRzXRdtLj9U_XIHjiO53ks5rDV_YgaJpZM4LAGFg
.

@niftylettuce thanks! I also did a PR, please let me know WDYT.


Remove "name" argument from from_arrays(**arrays) example

Thanks for you first contribution! :+1:


chore(dependencies): relax dependencies

This allows a wider range of compatible versions. Also, python 3.7 is no longer supported (End Of Life).
More specifically, the importlib-metadata pin is causing trouble when coupled with opentelemetry.

Hi @jonapich, thanks for the PR!
We don't have validation for the poetry.lock file, yet.  To avoid https://blog.phylum.io/bad-beat-poetry/, I have opened #127.  This allows us to keep full control of the lock file.

Merged.  Tagged.  Released.  Thanks again for spotting the issue and helping out!


Util that can create and read files from a hidden folder in the user's project

This is more of an RFC I guess, but what do we think about a utility that lets the author create and read files inside a hidden folder just for that integration inside a user's project?
So it'd be something like this:
({ createHiddenFile, readHiddenFile }) => {
  createHiddenFile({
    name: 'foo.ts',
    content: `export default {}`
  })

  const myHiddenFile = await readHiddenFile('foo.ts')
}

These would then save at ${ root }/.[integration.name]/foo.ts So right next to the hidden .astro folder. And it can't read/write outside that folder.
For context, the usecase is:
For my themes, I'm planning on shipping encrypted versions of my component files so that then they can be decrypted on the user's machine if they have the correct permissions with their env variables. So they'll set an env key, it'll check the api for their "level" and then decrypt the components for that level.
But I don't want it to have to make an api call each time they run or build their project. So once it's done one call and gotten the decryption keys I want to store them on the user's machine. Then they can still develop and reinstall and everything without the api.
I realise I could do this relatively easily without a utility. But I'm going to implement this either way, so just wondered if other people thought there'd be any interest in making it an AIK util.

Isn't it a good usecase for node_modules caching? Like storing at .node_modules/.your-folder. This way it's even cached by hosts like vercel. That being said, I think it's a great idea. This way we can add the folder name to .gitignore as needed

Yeah actually that's a good idea, to cache it in the node modules. I'm not really sure what would be best. But yeah whether it's stored in node_modules or a level up, just a little util that can just handle it for you


Resolved Support Version 2.0.0 changes for regard-application

Fixes #206

Reviewer is @vanithavalluripalli9


[General] Standardize microservice name

Have updated all except for the naming for the user_service database. The change for the database name goes successful when launching user-service alone but failed when launches together with other components


Change in behavior of jax.distributed

Description
Originally posted in the discussion, but maybe better to report as a bug since I am seeing a significant change in behavior.
https://github.com/google/jax/discussions/13439
I am getting different behaviors for each of these scenarios:

2 GPUs on a node in the same process (both recent commit and release)
1 GPU per process, 2 processes (recent commit: 7495a9e3705d67c498723240cfed3f14c5916567)
1 GPU per process, 2 processes (0.3.25 release commit: a683186570404a05a2aea9f7e452400bb0299e57)

I launch the following simple program that adds two arrays and reduces the sum.
mpirun -n 2 python test.py

import jax
import os
import numpy as np
import jax.numpy as jnp
from mpi4py import MPI
from jax.experimental.pjit import pjit
from jax.experimental.pjit import PartitionSpec as P
from jax.experimental.maps import Mesh
from jax import make_jaxpr

rank = MPI.COMM_WORLD.Get_rank()
size = MPI.COMM_WORLD.Get_size()
rc = jax.distributed.initialize("localhost:1234", size, rank)

os.environ["CUDA_VISIBLE_DEVICES"] = str(rank)

def fxn(a,b):
    return (a + b).sum()

fp = pjit(fxn, in_axis_resources=(P('x',), P('x',)), out_axis_resources=None)

a = jnp.arange(8)
b = jnp.arange(8)
devices = np.array(jax.devices())
with Mesh(devices, ('x',)):
    if rank == 0:
        print(devices)
        print(make_jaxpr(fp)(a,b))
    c = fp(a,b)

if rank == 0:
    print(c)

For recent commit, I get the following output (jaxpr and result):
[StreamExecutorGpuDevice(id=0, process_index=0, slice_index=0)
 StreamExecutorGpuDevice(id=1, process_index=1, slice_index=0)]
{ lambda ; a:i32[8] b:i32[8]. let
    c:i32[] = pjit[
      donated_invars=(False, False)
      in_positional_semantics=(<_PositionalSemantics.GLOBAL: 1>, <_PositionalSemantics.GLOBAL: 1>)
      in_shardings=(OpShardingSharding({devices=[2]0,1}), OpShardingSharding({devices=[2]0,1}))
      jaxpr={ lambda ; d:i32[8] e:i32[8]. let
          f:i32[8] = add d e
          g:i32[] = reduce_sum[axes=(0,)] f
        in (g,) }
      name=fxn
      out_positional_semantics=_PositionalSemantics.GLOBAL
      out_shardings=(OpShardingSharding({replicated}),)
      resource_env=ResourceEnv(Mesh(array([0, 1]), ('x',)), ())
    ] a b
  in (c,) }
56

For 2 GPUs in the same process, the output is basically the same except the GPUs are both process_index=0
For 0.3.25 release, I get a different output and different jaxpr:
[StreamExecutorGpuDevice(id=0, process_index=0, slice_index=0)
 StreamExecutorGpuDevice(id=1, process_index=1, slice_index=0)]
{ lambda ; a:i32[8] b:i32[8]. let
    c:i32[] = pjit[
      donated_invars=(False, False)
      in_positional_semantics=(<_PositionalSemantics.LOCAL: 0>, <_PositionalSemantics.LOCAL: 0>)
      in_shardings=(OpShardingSharding({devices=[2]0,1}), OpShardingSharding({devices=[2]0,1}))
      jaxpr={ lambda ; d:i32[16] e:i32[16]. let
          f:i32[16] = add d e
          g:i32[] = reduce_sum[axes=(0,)] f
        in (g,) }
      name=fxn
      out_positional_semantics=_PositionalSemantics.LOCAL
      out_shardings=(OpShardingSharding({replicated}),)
      resource_env=ResourceEnv(Mesh(array([0, 1]), ('x',)), ())
    ] a b
  in (c,) }
112

So basically multi-GPU in one process and multi-process (recent commit) treat the input arrays a and b as global arrays of size 8 and create two shards of size 4 on each GPU.
Multi-process on the most recent release treats the input arrays a and b as global arrays of size 16 that have already been sharded. It was not obvious to me glancing through recent history why this behavior would have changed.
What is the expected or defined behavior? I would have thought the behavior would be the same regardless of whether multiple devices are in the same process or in different processes.  The "new" distributed behavior makes more sense to me since you would expect the answer to be independent of the number of GPUs or how the GPUs are distributed.
What jax/jaxlib version are you using?
7495a9e3705d67c498723240cfed3f14c5916567 and 0.3.25
Which accelerator(s) are you using?
GPU
Additional system info
Ubuntu 20.04, Python 3.10.6
NVIDIA GPU info
Probably not relevant, but:
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 520.61.05    Driver Version: 520.61.05    CUDA Version: 11.8     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA RTX A6000    On   | 00000000:01:00.0 Off |                  Off |
| 30%   38C    P8    25W / 300W |     40MiB / 49140MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   1  NVIDIA RTX A6000    On   | 00000000:61:00.0 Off |                  Off |
| 30%   46C    P8    23W / 300W |    122MiB / 49140MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

I replied on the discussion

I am going to close this issue as this is an intended change in pjit (see the discussion where we can continue this). Feel free to open if we identify an actual bug.


Selecting a new font in Appearance causes Spyder to crash

Problem Description
Font setting causes spyder to crash

Although the spyder closes and exits, the Python process is not killed.

Subsequent problems is #10229
Versions

Spyder version: 4.0.0b5
Python version: 3.7.3
Qt version: 5.9.6
PyQt version: 5.9.2
Operating System name/version: win7

This probably happens because you have fonts with Chinese characters on its name.

@steff456, please take a look at this one: install a font whose name contains Chinese characters on Windows and try to see if you can reproduce this.

@steff456, please take a look at this one: install a font whose name contains Chinese characters on Windows and try to see if you can reproduce this.

I download three fonts that contain Chinese and Korean characters on Windows but I cannot reproduce the issue, even changing spyder language to Chinese.

Thanks @steff456! Maybe this problem happens if your Windows versions is in Chinese too, but we don't have the means to test that, sorry.

@leavor, could you remove your fonts with Chinese characters and try again? Maybe that could help.

@leavor, could you remove your fonts with Chinese characters and try again? Maybe that could help.

There are too many fonts,

I don't know which one I need to delete, and when I delete it, I am prompted that this font is protected by the system and cannot be deleted.
I put my font library on the cloud disk, I am not sure if this will provide a little help.
the address is as follows:
https://pan.baidu.com/s/1Z9og-tFCe6-OVVwWe7ZIjQ
extract code: lkqg

I don't think the problem has to do with Chinese fonts specifically, but with a combination between those fonts and a Chinese version of Windows.
So thanks for the link, but we're going to pursue this further because we don't have a way to install a Chinese version of Windows.

I have the same problem with a german version of Windows 10.
When I start the App via the "start.py" Script, I get the following Error Message:
QWidget::repaint: Recursive repaint detected
DirectWrite: CreateFontFaceFromHDC() failed (Gibt einen Fehler in einer Eingabedatei an, zum Beispiel eine Schriftartdatei.) for QFontDef(Family="MS Serif", pointsize=12, pixelsize=20, styleHint=5, weight=50, stretch=100, hintingPreference=0) LOGFONT("MS Serif", lfWidth=0, lfHeight=-20) dpi=120
QBackingStore::endPaint() called with active painter on backingstore paint device

@lhalb, thanks for the error message. This looks like a bug in Qt itself.
Could you please update to PyQt 5.12 and try again? Maybe this bug is fixed in that version.

Was this solved? I just intalled spyder 4 and experiencing the same issue. It crashes at the font selection drop down.

@haidernab could you provide details? os qt version etc?

@ccordoba12 @goanpeca I think this is the same bug I've reported in https://github.com/spyder-ide/spyder/issues/10893.
So there is indeed a Qt bug with fonts on Windows (see https://bugreports.qt.io/browse/QTBUG-57180), which causes a harmless warning for some fonts that are not scalable.
The crash however is due to a bug with the internal console when it tries to paint this harmless message.

Duplicate of #10893


Progressive call results implementation is incomplete

There are no call options yet added for progressive call results as per the spec. I have a commit with the necessary changes. I should have a patch ready this week.

Nice! The other piece (besides options) missing is: have a function on the invocation details, so the callee can produce progressive call results. Eg:

https://github.com/crossbario/autobahn-python/blob/master/examples/twisted/wamp/rpc/progress/backend.py#L46
https://github.com/crossbario/autobahn-python/blob/master/examples/twisted/wamp/rpc/progress/backend.js#L22

We have an example for a JS caller invoking a C++ callee, where there latter produces progressive results:

https://github.com/crossbario/autobahn-cpp/blob/master/examples/web/index.html#L34
https://github.com/crossbario/autobahn-cpp/blob/master/examples/callee.cpp#L63

What is missing is the reverse: a C++ caller invoking a JS callee, where the latter produces progressive results. The JS side in there - the C++ bits are missing.
In Python, this looks like this:
        def on_progress(i):
            print("Progress: {}".format(i))

        res = yield self.call(u'com.myapp.longop', 3, options=CallOptions(on_progress=on_progress))

We can use that as a model for C++ too. That is, we need a (templated) member in https://github.com/crossbario/autobahn-cpp/blob/master/autobahn/wamp_call_options.hpp for the user to provide a progressive result callback.


The resulting data is truncated. how can i solve it?? Is it a fragment_size problem??

The resulting data is truncated. how can i solve it??
Is it a fragment_size problem

??

How did you get to this state?

@isoos The data was requested through the await client.search() function. There were no errors, but the results were stuttered.

I'm not sure how to reproduce or debug this. Is the server on the same network, or is there any proxy inbetween?

@isoos I got elasticsearch data by communicating with my elastic cloud and external network.


fix(library/vm/vm): fix segfault in call_stack_fn

@leodemoura This produces the ugly stack trace that we talked about yesterday, it seems that we do not inline tactic_bind (even though it is @[inline]) because it is not fully applied:
run_command (do
  x ← return 5,
  x ← return 5,
  x ← return 5,
  x ← return 5,
  x ← return 5,
  x ← return 5,
  x ← return 5,
  x ← return 5,
  x ← return 5,
  x ← return 5,
  trace_call_stack)


docs: easyops-cn/docusarus-search-local v3 support

Pre-flight checklist

[x] I have read the Contributing Guidelines on pull requests.
N/A If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
N/A If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

easyops-cn/docusarus-search-local has Docusaurus v3 support, so this updates the documentation to reflect that.
Source: https://github.com/easyops-cn/docusaurus-search-local#easyops-cndocusaurus-search-local
Test Plan

N/A
Test links

Deploy preview: https://deploy-preview-9583--docusaurus-2.netlify.app/community/resources#search
Related issues/PRs

N/A

Thanks
Actually I'd prefer to remove all refs to Docusaurus v2 in this page. This was useful during the v1/v2 transition but we should expect most plugins to be compatible with v2+ from now on. If they are not, it's likely only a matter of time


TimePicker - remove padding !

Reproduction link
https://fqlmnr.run.stackblitz.io
Steps to reproduce

What is expected?
Remove padding: 0 0 160px;
Comment
In the calendar, when choosing a date there are no padding, follow a uniform format

Environment
Info

ng-zorro-antd
8.0.3

Browser
Chrome 73

It does make sense to have the padding. Helps with top alignment.
When selecting the time I want to pick it from the top, to have an "aligned overview" of the time.

When there is no padding, it's pretty bad

Understood
thanks


Post-repo-split stuff

Everything before this PR in this repo is simply the result of a git subtree split, i.e. it has exactly the same history as the bindings/matrix-sdk-crypto-nodejs directory in matrix-rust-sdk.

So, with commented-out if's for pages deployment, docs seem to be working fine. I think this can be merged, and afterwards https://github.com/matrix-org/matrix-rust-sdk/pull/2264 can. The only thing I'm not sure how to test is the release stuff.

When I attempt to build this locally, it hits this failure:
~/git/matrix-rust-sdk-crypto-nodejs (main)$ npm install --ignore-scripts && npm run build -- --features tracing

added 295 packages, and audited 296 packages in 31s

35 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

><EMAIL_ADDRESS>build
> napi build --platform --features tracing

Type Error: Could not parse the Cargo.toml: Error: Command failed: cargo metadata --format-version 1 --manifest-path "/home/andrewf/git/matrix-rust-sdk-crypto-nodejs/Cargo.toml"
error: failed to parse manifest at `/home/andrewf/git/matrix-rust-sdk-crypto-nodejs/Cargo.toml`

Caused by:
  error inheriting `rust_version` from workspace root manifest's `workspace.package.rust_version`

Caused by:
  failed to find a workspace root

error: failed to parse manifest at `/home/andrewf/git/matrix-rust-sdk-crypto-nodejs/Cargo.toml`

Caused by:
  error inheriting `rust_version` from workspace root manifest's `workspace.package.rust_version`

Caused by:
  failed to find a workspace root

<snip: traceback>

Pardon the naive question, but do I have to clear some kind of workspace-related setting that was applied by previous (successful) builds of the bindings before the repo move?

Sounds like you are testing main, i.e. the state before this PR?

D'oh, yes, that was it.  It builds just fine now.
One last question: are all of the beta releases (like matrix-sdk-crypto-nodejs-v0.1.0-beta.X) omitted from this repo's git history?  In the original repo, they were given branches that never got merged back into main (other than beta.1), which may have prevented them from being seen by the git subtree split.
This isn't too urgent, but asking since I typically test with tagged releases & wanted to know if that practice would/should change (even if just for the short term until new releases are cut).

In the original repo, they were given branches that never got merged back into main

Huh, why is that? I'm sure there is a way to keep those, but I wonder if it makes sense. The tags and branches will continue to exist on the other repo anyways (unless we decide to delete them).

Not sure why the Node bindings releases were done that way, especially since the JS & FFI bindings releases appear in main.
This also caused problems with the Node bindings' release workflow, where every new release would think the previous release was beta.1 (since it was the only release in main).
I'd be fine with losing the history of previous releases, as long as there can be a new release cut from this repo sometime soon, to serve as an example of a clean release to use.


fix(network_info_plus): Return nullable values on windows again

Description
Since version 4.0.0, the windows implementation got a rewrite in Dart.
Previously, when a PC has no wifi, then null is returned. Since 4.0.0 we return an empty string '' instead which does not align with the API. Furthermore, this (unwanted?) breaking change seems to be unecessary.
Related Issues

Related #1780

Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I titled the PR using Conventional Commits.
[x] I did not modify the CHANGELOG.md nor the plugin version in pubspec.yaml files.
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze) does not report any problems on my PR.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate that with a ! in the title as explained in Conventional Commits).
[X] No, this is not a breaking change. This is more like a revert of a breaking change

@timsneath tagging you here since you did the refactoring. Do you have time for a quick review?

I'm really sorry -- since I moved on from Google, I'm no longer able to review Dart-related PRs. You might try @halildurmus, who has taken over governance of the Win32 packages.

I'm really sorry -- since I moved on from Google, I'm no longer able to review Dart-related PRs. You might try @halildurmus, who has taken over governance of the Win32 packages.

Thank you for pointing me in the right direction @timsneath 🙏🏽 And for all your valuable contributions to plus_plugins 😊
By the way, I was genuinely inspired by your Medium article. Wishing you continued success and brilliance in your next chapter.


preferences fails write when .tessel folder doesn't exist

I ran into this trying to get the t2 working on WIndows 10, node 4.3, following this gist https://gist.github.com/tcr/992978a5dbe5bff2e18f495c5c0973c3
Unfortunately, the preferences file handling fails if there is no ~/.tessel folder.
C:\Users\Joe\Documents\Software\Tessel>t2 list
INFO Searching for nearby Tessels...
ERR! Detected CLI crash { [Error: LIBUSB_TRANSFER_STALL] errno: 4 } Error: LIBUSB_TRANSFER_STALL
ERR!     at Error (native)
undefined
Submit Crash Report to help Tessel Developers improve the CLI ?
    If yes(y), subsequent crashes will be submitted automatically. Yes
ERR! Error writing preference crash.reporter.prompt false
ERR! Detected CLI crash { [Error: ENOENT: no such file or directory, open 'C:\Users\Joe\.tessel\preferences.json']
ERR!   errno: -4058,
ERR!   code: 'ENOENT',
ERR!   syscall: 'open',
ERR!   path: 'C:\\Users\\Joe\\.tessel\\preferences.json' } Error: ENOENT: no such file or directory, open 'C:\Users\Joe\.tessel\preferences.json'
ERR!     at Error (native)
undefined
Submit Crash Report to help Tessel Developers improve the CLI ?

Closed by https://github.com/tessel/t2-cli/issues/821


Fix #173 (bad help).

Good q!  I have tested it here with and without serial loaded to make sure that it does the right thing but I haven't run it on an actual device.
Probably testing it is the best way to go... what do you run to test?

I don't really have a standard test. But best is to test on an AllPixel, of course. Let me pull this and throw together a standard test script. I'd put it in the tests dir, but it's obviously not runnable by our travis job.

Cool. This checks out and everything works.
New test script here: https://gist.github.com/adammhaile/1b43fdde6ae6cbbd35560c68a9b90beb
Not sure where we should put it though...

I think we should check it in as a unit test that's disabled by default but can be enabled by setting an environment variable...

Or could do a command line argument that enables serial testing as we already have similar arguments

AFAIK there isn't a good way to pass things into a unit test other than an
environment variable...?
On Mon, Apr 24, 2017 at 1:37 PM, Adam Haile<EMAIL_ADDRESS>wrote:

Or could do a command line argument that enables serial testing as we
already have similar arguments
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/pull/174#issuecomment-296629418,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPdsk6FCDhnbA7bWijEPgcTq44GAJI9ks5rzImKgaJpZM4NFeYz
.

--
/t
https://tom.ritchford.com https://tom.ritchford.com
https://tom.swirly.com https://tom.swirly.com

Ahh... I was thinking of benchmark, coverage, test commands but yeah...
that would get weird.
I'm fine with an env var.
On Mon, Apr 24, 2017 at 7:39 AM, Tom Swirly<EMAIL_ADDRESS>wrote:

AFAIK there isn't a good way to pass things into a unit test other than an
environment variable...?
On Mon, Apr 24, 2017 at 1:37 PM, Adam Haile<EMAIL_ADDRESS>wrote:

Or could do a command line argument that enables serial testing as we
already have similar arguments
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<https://github.com/ManiacalLabs/BiblioPixel/pull/
174#issuecomment-296629418>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AAPdsk6FCDhnbA7bWijEPgcTq44GAJI9ks5rzImKgaJpZM4NFeYz>
.

--
/t
https://tom.ritchford.com https://tom.ritchford.com
https://tom.swirly.com https://tom.swirly.com
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/pull/174#issuecomment-296629902,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6a6mqvL_-qoRNWlKSKsE8kXgZgouACks5rzInxgaJpZM4NFeYz
.


Remove some unused/untested dead code

Motivation
Less code is always better!
Changes

Remove some unused/untested dead code

@swift-server-bot test this please


cel-go: 0.18.0 -> 0.18.1

Diff: https://github.com/google/cel-go/compare/v0.18.0...v0.18.1
Changelog: https://github.com/google/cel-go/releases/tag/v0.18.1
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

1 package built:

cel-go


offer markdown export

One other thing - since many of these will be presented through Github, I suggest offering a markdown export!

This is a suggestion from VIP :)

If the agreement is in HTML, this can be done in the browser with to-markdown.
Server-side, there's always pandoc.

Ok, good options.

Another option would be to have the source “code” of the templates in MarkDown – as the majority already is: https://git.fsfe.org/fsfe-legal/fla/ and then generate that to the HTML served on the website.

https://github.com/integrations/html-to-mrkdwn

That one converts to “Slack Markdown”, which differs quite a bit from any standard Markdown.

Does not seem to differ that much. https://github.com/integrations/html-to-mrkdwn/blob/master/lib/index.js
In any case, sth like this is the only viable option imo, as a lot would have to be redone (basically the whole chooser.js) for markdown, and most of all the technique it uses cannot be used as markdown obviously does not have html ids/classes and css attributes. I'll look into it more on the weekend.

@step21, that makes a lot of sense to me. Thanks for looking into this :smiley:
Regarding Slack MarkDown, if you compare it to CommonMark (the de facto standardised MarkDown), it is lacking many features, and also some things are done quite differently – most notably * for strong (** or __ in CommonMark) and _ for simple emphasis (* or _ in CommonMark). This website shows an overview of the major differences.

a basic markdown function is now in the markdown branch. Still has to be added to gui though  and I'm not sure yet where is best. I guess just another button next to html/pdf.

A button next to PDF sounds like a good idea to me. If it is getting too crowded, we might want to change the buttons to a pull-down menu.

If you want to try it, run python -m http.server in the directory. (it has a button now) I just wanted to leave it for a while/fix other stuff before merging this.

merged in #29
Please test @silverhook :)

Hey, thanks for tackling this!
I took it for a spin and generated the FLA:

Pandoc does not complain and outputs a usable PDF
MarkDown Lint does have a few things it complains about though:

the first line is not the top-level header
mixing of different styles of header notations – atx style is mixed with setex style throughout the file
obsolete whitespace between the bullet and its text in a list
(many complains about the line length, but we can safely ignore those)

(I also noticed that there are some inconsistencies between the FLA and the other CLA templates when it comes to dots after the section numbers, we should probably normalise those.)
If these can be fixed somehow, that’d be superb! Ideally I’d like us to have a CommonMark-compliant output, but what we have here is workable already.

Looking at this again

the first line is not top level, because it is not toplevel in html, but h2
the parser should default to one, normally setex according to docs. not sure why not. Maybe due to the numbered list, but I'll ask.

I think I would also ignore the two additional whitespaces, as it will render fine and should not be a big issue, no?
With the top level, easiest would be to change it in the template from h2 to h1, but I wonder if that might have unintended consequences in other versions.

update for the spaces after bullets https://github.com/domchristie/turndown/issues/291
made an issue for heading styles https://github.com/domchristie/turndown/issues/364


Large hives can take up large amounts of memory

Some registry hives can be as large as 2GB. Maybe not a big issue for most people, but also not difficult to fix. I went with the following solution using mmap for myself. It substantially reduces the time to read from a large hive and uses almost no memory.
import mmap
from Registry import RegistryParse
from Registry.Registry import Registry as _Registry

class Registry(_Registry):
    def __init__(self, f):
        self._buf = mmap.mmap(f.fileno(), 0, prot=mmap.ACCESS_READ)
        self._regf = RegistryParse.REGFBlock(self._buf, 0, False)

Used like this:
with open(path) as f:
    r = Registry(f)
    # stuff

hey @dhagrow
this is a good solution. if i were to re-write this library, i'd probably have the registry constructor accept a buffer object, and leave it up to the caller to (1) read from the file, (2) create a mmap, (3) do something i haven't even thought of.
there are a couple other warts that i'd want to address in a major version bump, so i'll include this in the list.
thanks for sharing this tip!

hey,
any news on this? It would be a great feature indeed


Bug/feedback welsh layout

What

Reformatted feedback template
Fixed missing localisation of 'Send feedback' button
Added structure to support layout fix in Welsh

English
Desktop

Tablet

Mobile

Welsh
Desktop

Tablet

Mobile

How to review
Verify structure and approach
Who can review
Frontend / Design System developers

Localisation fix in the feedback form:
English (as before)

Welsh ('Send feedback' localised)


Update miniconda action

Fix #13

Codecov Report

Merging #14 (a3e2290) into master (9ca9bfc) will not change coverage.
The diff coverage is n/a.


Improve Work Files tool aesthetics and functionality

Issue
The Avalon Work Files tool currently has the barebones functionality and I'd like to make it more trivial to use when working in a scene with many saved versions and files. And I believe it can offer some more things that one might want to use now and then.
Of course #412 is part of improving workflows too. But I think we can do much more.
Here are some ideas:

Remove the Duplicate button and add that under "right mouse" functionality on a file to avoid clutter.
Merge files of the same sequence. Say you have model_v001 to model_v114 then it would show model v114 and you could expose the other versions by right clicking or something. 95% of the time you're opening the latest anyway. Any reason to NOT do this?
Add "date modified" to the view (often requested by our artists). Funnily this is most useful when you don't do 2) or keep it simple to see the visual date differences between this and earlier files. Artists often told me they wanted to quickly see the date differences between different versions.
Allow to sort by date modified.
Add filter by name field.

The points 2) and 5) really are only useful if uses save with files with different names, which the workfiles currently disallows. It forces you to use a particular file path formatting. Bringing me to point 6). Should we allow work files to be saved as different steps or branches?
So like now you could have a character model that has a scene for character_model_v001.ma and character_model_v002_fix.ma where fix is a comment/description for that file. But what if someone wanted to save "another branch of work" like: "hires", "lowres", "proxy" or maybe just a part of the character "belt" or "head". I'm seeing other pipelines allowing to do so and I'm wondering whether we'd want to expose that too. It seems very logical, we often have artists saving manually outside of Work Files to allow just that.

Any better ideas? References or design mockups are also very welcome.

I dont really mind any of these improvements. The main purpose of the Workfiles app is to make it easier and quicker to access your work files than the DCCs "Open File"

Remove the Duplicate button and add that under "right mouse" functionality on a file to avoid clutter.

This needs to be explained/obvious to the end user somehow. Too often right-click functionality is lost to the user because its not explained or indicated.

Merge files of the same sequence. Say you have model_v001 to model_v114 then it would show model v114 and you could expose the other versions by right clicking or something. 95% of the time you're opening the latest anyway. Any reason to NOT do this?

Sounds good to me. We already have clique as a vendor to be able to do this.

But what if someone wanted to save "another branch of work"

We have worked with making another task if something needs branching. Maybe its a matter of making the Context Manager able to make tasks?

I like that

I did a quick survey in the studio and artists spoke quite loudly against this. They feel it's obscuring and confusing the simplicity it has right now. I actually agree with them on this one. Moreover, what happens when you have my_file_v01, my_file_v02, my_file_v02_testingSomething? The only way to know which is newer is by date, and that doesn't mean it's the one artist wants.

Yes, absolutely

Totally

YES.

But what if someone wanted to save "another branch of work"

Yeah we do this quite a lot for plethora of situations. I'd rather leave this a bit loose. Actually the "snapshot" system that is used in shotgun is perfect I think. People often want to save subversions of their current workfile. Currently we use comment for this, or simple maya "incemental save" but maybe some supported way would be good, on top of comment.
maybe having version, subversion,  comment? subversion and comment of coure being optional


Where can I see the results when I have finished predicting?

Where can I see the results when I have finished predicting?

Hi, we did not put the logger in the predict.py. You can just move the logger code during the training to the predict.py. Or, you can wait for a while, and I will add the logger to predict.py.

Thanks for the reply, I can wait for a while.
------------------ 原始邮件 ------------------
发件人: "Fengyu @.>;
发送时间: 2022年5月24日(星期二) 下午2:35
收件人: @.>;
抄送: "To be a peaceful @.>; @.>;
主题: Re: [TRUMANCFY/SLIM] Where can I see the results when I have finished predicting? (Issue #2)
Hi, we did not put the logger in the predict.py. You can just move the logger code during the training to the predict.py. Or, you can wait for a while, and I will add the logger to predict.py.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

What is the goal of data processing? I followed the code and got dizzy. Please give me some advice

How can I slove the problem that "PermissionError: [Errno 13] Permission denied: 'E:\SLIM\SLIM-main\logs\mixsnips_seed1234_TI0_attn0_cls0_mask4_ticoef1.0.log'"

How can I slove the problem that "PermissionError: [Errno 13] Permission denied: 'E:\SLIM\SLIM-main\logs\mixsnips_seed1234_TI0_attn0_cls0_mask4_ticoef1.0.log'"

mkdir logs

I just created a folder, which should be incorrect. The original error is that "FileNotFoundError: [Errno 2] No such file or directory: 'E:\SLIM\SLIM-main\logs\mixsnips_seed1234_TI0_attn0_cls0_mask4_ticoef1.0.log'"

hello，could you please help answer it that "  File "E:\SLIM\SLIM-main\data_loader.py", line 351, in convert_examples_to_features
intent_label_id = int(example.intent_label)
TypeError: int() argument must be a string, a bytes-like object or a number, not 'list'"
By the way ,would you mind to give me a contact information（Wechat）

I just slove the problem ,but I meet a new one.In predict.py, "TypeError: init_logger() missing 1 required positional argument: 'args'"

I also face the problem, how can I find the results after predicting, can anyone give me some guidings?


chore: switch build to esnext module type

What kind of change does this PR introduce?
build
What is the current behavior?
commonjs
What is the new behavior?
no need to support commonjs as pg-meta is purely server side
Additional context
Add any other context or screenshots.

FYI Studio imports @supabase/postgres-meta for types - not sure how this will affect that