fix: gas and gasUsed in trace root only for ParityTrace

Description
This pull request is Part 2/2 of fixing the bug where the gas and gasUsed fields in Parity Trace root are incorrect.
Part 1/2 paradigmxyz/revm-inspectors#171
Related Issues and Pull Requests

Follow: ethereum/go-ethereum#27029
Improve: paradigmxyz/reth#3678 and paradigmxyz/reth#3719
Fix: paradigmxyz/reth#9142 with paradigmxyz/revm-inspectors#170
Update: paradigmxyz/reth#3782

Problem
The gas and gasUsed fields in Geth Debug Trace root should be the gas limit and gas used for the entire transaction.
However, two fields in Parity Trace root should be the original ones.
Reproducible Example
With the latest version Reth v1.0.3, using trace_transaction() to trace
the transaction 0x03128677ee3a9623d20f3c677f423ccc592d126374bf32e331343dd1bdf38b61
curl http://localhost:8545 \
  -X POST \
  -H "Content-Type: application/json" \
  --data '{"method":"trace_transaction","params":["0x03128677ee3a9623d20f3c677f423ccc592d126374bf32e331343dd1bdf38b61"],"id":1,"jsonrpc":"2.0"}'

From Reth
gas: 0x55493 (349331)
gasUsed: 0x32d16 (208150)

From Etherscan and QuickNode
gas: 0x4f227 (324135)
gasUsed: 0x36622 (222754)

Solution for reth

Modify revm-inspectors part

Then

remove with_transaction_gas_used() for Parity Trace

add with_transaction_gas_limit() for Geth Debug Trace

Miscellaneous

Actually, I love the current design, but the results are inconsistent with those of others.

When I used make pr to test the Reth Part, the issue paradigmxyz/reth#9381 still exists for me.
I should only skip tests for lockfile and test them seperately.

However, two fields in Parity Trace root should be the original ones.

can you please clarify what you mean by original here?

merging once compiles, hehe


[R-package] Use Rprintf for logging in the R package (fixes #1440, fixes #1909)

This PR proposes a change to get the R package closer to CRAN's standards (#629). See #1440 and #1909 for background. The basic issue, as documented in Writing R Extensions, is this:

Compiled code is checked for symbols corresponding to functions which might terminate R or write to stdout/stderr instead of the console.

To get LightGBM into compliance with this check, I propose using Rprintf()  and  Rvprintf() from R's headers. This is the approach CRAN recommends

The most useful function for printing from a C routine compiled into R is Rprintf. This is used in exactly the same way as printf, but is guaranteed to write to R’s output (which might be a GUI console rather than a file, and can be re-directed by sink). It is wise to write complete lines (including the "\n") before returning to R. It is defined in R_ext/Print.h.

Notes for Reviewers

cmake/modules/FindLibR.cmake was included to find R and its headers on any system. It borrows heavily from xgboost's implementation.
I've tested this approach on my personal Travis and it seems to be working. One task (mpi) is failing but I think it is unrelated.
I ran R CMD check lightgbm_2.3.2.tar.gz --as-cran and  can confirm that this NOTE is gone!

File ‘/home/travis/build/microsoft/LightGBM/lightgbm.Rcheck/lightgbm/libs/lib_lightgbm.so’:
  Found ‘printf’, possibly from ‘printf’ (C)
  Found ‘putchar’, possibly from ‘putchar’ (C)
  Found ‘stderr’, possibly from ‘stderr’ (C)
  Found ‘stdout’, possibly from ‘stdout’ (C)

Compiled code should not call entry points which might terminate R nor
write to stdout/stderr instead of to the console, nor use Fortran I/O
nor system RNGs. The detected symbols are linked into the code but
might come from libraries and not actually be called.

Travis is struggling today, seeing a lot of these

I just tried building this branch on my Windows laptop (Windows 10, R3.6.1, Visual Studio 16 2019) with Rscript build_r.R and can confirm this worked!
The first time I ran I did hit https://github.com/jameslamb/LightGBM/blob/feat/r-header/R-package/src/cmake/modules/FindLibR.cmake#L41, but that was easy to fix by following the error message and adding the Rtools minGW bin/ directory to the path.

I just rebased to master since there have been a lot of changes on there since this PR was opened. Made sure to pull the suggestions committed in the browser before doing that, so they didn't get reverted by the force push.

See R-devel (R 4.0): https://cran.r-project.org/doc/manuals/r-devel/NEWS.html in C-level facilities:

Header ‘R_ext/Print.h’ defines R_USE_C99_IN_CXX and hence exposes Rvprintf and REvprintf if used with a C++11 (or later) compiler.

Do we need a workaround for it?

Still investigating, but for the sake of documenting the discussion...divest (as one example), uses this same pattern and recently passed CRAN nightly checks against r-devel (which is 4.0.0 now) https://cran.r-project.org/web/checks/check_results_divest.html

Thanks for the review @Laurae2 ! I won't merge until @StrikerRUS and I agree on some of the lingering comments on FindLibR.cmake

@StrikerRUS I saw you resolved the comment threads on FindLibR.cmake.  Am I ok to merge this?
Thanks for the review! btw I made PR into xgboost  with one of the improvements you suggested: https://github.com/dmlc/xgboost/pull/5427

@jameslamb Please give me some time to make a second round of review.

@jameslamb Please give me some time to make a second round of review.

sure no hurry at all! Glad that I asked

@jameslamb Finally got a minute to drop a second round of review. Sorry for the delay!

no problem! I'll look at these right now.

R + Mac CI on Travis died with this error:

Looks like a timeout for Homebrew. I have been seeing that slightly more the last few weeks. I imagine all the people now working remote is putting a lot of pressure on ISPs.

@jameslamb

Looks like a timeout for Homebrew. I have been seeing that slightly more the last few weeks. I imagine all the people now working remote is putting a lot of pressure on ISPs.

Yeah, it seems to be so...
I cannot remember how many times I re-run Travis macOS builds last days. Also, Travis had some problems with macOS recently: https://www.traviscistatus.com/


Boardcast after elementwise mul

Hi,
I was trying to implement a kernel for computing q square. However, trying to run the code with A100 gives wrong results. Boardcasting after elementwise mul always got twice the result. I am using triton(2.0.0.dev20230217).
If I try to boardcast before elementwise mul and it can give right result.
import torch

import triton
import triton.language as tl

@triton.jit
def mul_boardcast_kernel(Q, OUT,
                    stride_qb, stride_qm,
                    stride_outb, stride_outm,
                    batch_size, nheads, BLOCK_N: tl.constexpr,
                    BLOCK_HEADDIM: tl.constexpr):
    m = tl.program_id(0)
    n = tl.program_id(1)
    b = tl.program_id(2)

    offs_m = tl.arange(0, BLOCK_HEADDIM)

    rm = m * BLOCK_N + tl.arange(0, BLOCK_N)
    rn = n * BLOCK_N + tl.arange(0, BLOCK_N)

    q_ptrs = Q + b * stride_qb + rm[:, None] * stride_qm + offs_m[None, :]
    q = tl.load(q_ptrs)
    tmp = tl.zeros([BLOCK_N, BLOCK_N], dtype=tl.float32)
    tmp = tl.sum(q*q, axis=1)[:, None]
    out_ptrs = OUT + b * stride_outb + rm[:, None] * stride_outm + rn[None, :]
    tl.store(out_ptrs, tmp)

def mul_boardcast():
    BLOCK_N = 128
    out = torch.zeros([batch_size * nheads, seq_len, seq_len], dtype=dtype).cuda()

    num_warps = 4 if dim <= 64 else 8
    grid = lambda meta: (seq_len // BLOCK_N, seq_len // BLOCK_N, batch_size*nheads)
    mul_boardcast_kernel[grid](q, out,
                        q.stride(0), q.stride(1),
                        out.stride(0), out.stride(1),
                        batch_size, nheads, BLOCK_N,
                        dim,
                        num_warps=num_warps,
                        num_stages=1)

    q_2 = torch.sum(q*q, axis=2)[:, :, None]
    print((out - q_2).abs().max())
    print((out / 2 - q_2).abs().max())

if __name__ == '__main__':
    torch.random.manual_seed(0)
    batch_size = 1
    seq_len = 2 ** 8
    nheads = 1
    dim = 64
    dtype = torch.float16
    q = torch.randn([batch_size * nheads, seq_len, dim], dtype=dtype).cuda()
    mul_boardcast()

Can you elaborate on what is wrong here? Is  print((out - q_2).abs().max()) wrong? Have you tried triton/main?
print((out - q_2).abs().max())  seems fine for me.

Yeah, print((out - q_2).abs().max()) is wrong. I found out is twice as much as q_2
I reinstall triton with version 2.0.0.post1, and it give the same result.
tensor(97.0625, device='cuda:0', dtype=torch.float16)
tensor(0.0625, device='cuda:0', dtype=torch.float16)


Plugin.available is interpreted as a method reference instead of property access

Describe the bug
Just running yin-yang works.  I'm using xmonad as my window manager, so XDG_CURRENT_DESKTOP is not set and so plugins specific to desktop environments do not work.  I tried XDG_CURRENT_DESKTOP=gnome yin-yang but then get:
Plugin Colors has no support for your desktop environment yet!
Plugin Icons has no support for your desktop environment yet!
No such schema “org.gnome.shell.extensions.user-theme”
Error while loading translation. Using default language.
No such schema “org.gnome.shell.extensions.user-theme”
Traceback (most recent call last):
  File "/usr/lib/python3.10/runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/lib/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/opt/yin-yang/yin_yang/__main__.py", line 134, in <module>
    window = main_window_connector.MainWindow()
  File "/opt/yin-yang/yin_yang/ui/main_window_connector.py", line 55, in __init__
    self.load()
  File "/opt/yin-yang/yin_yang/ui/main_window_connector.py", line 91, in load
    self.load_plugins()
  File "/opt/yin-yang/yin_yang/ui/main_window_connector.py", line 126, in load_plugins
    widget = plugin.get_widget(self.ui.plugins_scroll_content)
  File "/opt/yin-yang/yin_yang/plugins/_plugin.py", line 71, in get_widget
    widget.setVisible(self.available)
TypeError: 'PySide6.QtWidgets.QWidget.setVisible' called with wrong argument types:
  PySide6.QtWidgets.QWidget.setVisible(method)
Supported signatures:
  PySide6.QtWidgets.QWidget.setVisible(bool)

So, it seems like the Plugin.available property is being interpreted as a method reference instead of a property access.  Totally mysterious to me why this would happen.
Affected versions
Yin-Yang head de1f3eb5c81f90657685503eb317e1fe91c57273

I forgot to add @property to the gnome implementation, whoops


Feature: Conditional rendering of logos

Current State
With the integration, the existing UI will leave an empty space if the logo cannot be rendered. Ideally, we remove that extra whitespace, and instead leave the rest of the content viewable.
Also, the logos aren't working yet, as we have to convert the url into a thumbnail preview

A link that might help: https://stackoverflow.com/questions/67344372/how-do-i-display-images-from-google-drive-on-a-react-front-end-website

Finished with #40


API Versioning

Is your feature request related to a problem? Please describe.
We've broken things in the past with API changes, this will be unacceptable post-Stable.
Describe the solution you'd like

[ ] what we have now becomes API 1.0
[ ] version should be explicit in all routes, e.g. https://polyswarmd/1.0/bounties
[ ] future changes to API result in version bump
[ ] backwards compatibility ensured to a to be determined extent

Who is this assigned to? @myhndl this is very close to actual release for such a change.

Agreed, planned to and forgot to do this yesterday.
Will move off critical, furture breaking updates (1.1+) will introduce a version number.


Encountered issues running flutter run on macOS (M1 chip)

flutter pub add rust_in_flutter

dart run rust_in_flutter template

flutter run

After these three commands, i got this error
Launching lib/main.dart on iPhone 14 Pro in debug mode...
Running Xcode build...
Xcode build done.                                            1.1s
Failed to build iOS app
Error output from Xcode build:
↳
    ** BUILD FAILED **

Xcode's output:
↳
    Writing result bundle at path:
        /var/folders/z1/7zts17kx6jggkvmjn2wzpnwdw4zzb4/T/flutter_tools.CT3yeo/flutter_ios_build_temp_dirgLf6YD/temporary_xcresult_bundle

    /Users/shuai_yang/Projects/tally/ios/Pods/../.symlinks/plugins/rust_in_flutter/ios/../connectors/cargokit/build_pod.sh: line 2: set: -:
    invalid option
    set: usage: set [--abefhkmnptuvxBCHP] [-o option] [arg ...]
    Command PhaseScriptExecution failed with a nonzero exit code
    note: Building targets in dependency order
    /Users/shuai_yang/Projects/tally/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set
    to 9.0, but the range of supported deployment target versions is 11.0 to 16.2.99. (in target 'FMDB' from project 'Pods')
    note: Run script build phase 'Run Script' will be run during every build because the option to run the script phase "Based on dependency
    analysis" is unchecked. (in target 'Runner' from project 'Runner')
    note: Run script build phase 'Thin Binary' will be run during every build because the option to run the script phase "Based on dependency
    analysis" is unchecked. (in target 'Runner' from project 'Runner')

    Result bundle written to path:
        /var/folders/z1/7zts17kx6jggkvmjn2wzpnwdw4zzb4/T/flutter_tools.CT3yeo/flutter_ios_build_temp_dirgLf6YD/temporary_xcresult_bundle

Could not build the application for the simulator.
Error launching application on iPhone 14 Pro.

flutter pub add rust_in_flutter

dart run rust_in_flutter template

flutter run

After these three commands, i got this error
Launching lib/main.dart on iPhone 14 Pro in debug mode...
Running Xcode build...
Xcode build done.                                            1.1s
Failed to build iOS app
Error output from Xcode build:
↳
    ** BUILD FAILED **

Xcode's output:
↳
    Writing result bundle at path:
        /var/folders/z1/7zts17kx6jggkvmjn2wzpnwdw4zzb4/T/flutter_tools.CT3yeo/flutter_ios_build_temp_dirgLf6YD/temporary_xcresult_bundle

    /Users/shuai_yang/Projects/tally/ios/Pods/../.symlinks/plugins/rust_in_flutter/ios/../connectors/cargokit/build_pod.sh: line 2: set: -:
    invalid option
    set: usage: set [--abefhkmnptuvxBCHP] [-o option] [arg ...]
    Command PhaseScriptExecution failed with a nonzero exit code
    note: Building targets in dependency order
    /Users/shuai_yang/Projects/tally/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set
    to 9.0, but the range of supported deployment target versions is 11.0 to 16.2.99. (in target 'FMDB' from project 'Pods')
    note: Run script build phase 'Run Script' will be run during every build because the option to run the script phase "Based on dependency
    analysis" is unchecked. (in target 'Runner' from project 'Runner')
    note: Run script build phase 'Thin Binary' will be run during every build because the option to run the script phase "Based on dependency
    analysis" is unchecked. (in target 'Runner' from project 'Runner')

    Result bundle written to path:
        /var/folders/z1/7zts17kx6jggkvmjn2wzpnwdw4zzb4/T/flutter_tools.CT3yeo/flutter_ios_build_temp_dirgLf6YD/temporary_xcresult_bundle

Could not build the application for the simulator.
Error launching application on iPhone 14 Pro.

Maybe you could change set -e to set +e in file connectors/cargokit/build_pods.shline 2, then attempt to build again and attention the logs.

flutter pub add rust_in_flutter

dart run rust_in_flutter template

flutter run

After these three commands, i got this error
Launching lib/main.dart on iPhone 14 Pro in debug mode...
Running Xcode build...
Xcode build done.                                            1.1s
Failed to build iOS app
Error output from Xcode build:
↳
    ** BUILD FAILED **

Xcode's output:
↳
    Writing result bundle at path:
        /var/folders/z1/7zts17kx6jggkvmjn2wzpnwdw4zzb4/T/flutter_tools.CT3yeo/flutter_ios_build_temp_dirgLf6YD/temporary_xcresult_bundle

    /Users/shuai_yang/Projects/tally/ios/Pods/../.symlinks/plugins/rust_in_flutter/ios/../connectors/cargokit/build_pod.sh: line 2: set: -:
    invalid option
    set: usage: set [--abefhkmnptuvxBCHP] [-o option] [arg ...]
    Command PhaseScriptExecution failed with a nonzero exit code
    note: Building targets in dependency order
    /Users/shuai_yang/Projects/tally/ios/Pods/Pods.xcodeproj: warning: The iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set
    to 9.0, but the range of supported deployment target versions is 11.0 to 16.2.99. (in target 'FMDB' from project 'Pods')
    note: Run script build phase 'Run Script' will be run during every build because the option to run the script phase "Based on dependency
    analysis" is unchecked. (in target 'Runner' from project 'Runner')
    note: Run script build phase 'Thin Binary' will be run during every build because the option to run the script phase "Based on dependency
    analysis" is unchecked. (in target 'Runner' from project 'Runner')

    Result bundle written to path:
        /var/folders/z1/7zts17kx6jggkvmjn2wzpnwdw4zzb4/T/flutter_tools.CT3yeo/flutter_ios_build_temp_dirgLf6YD/temporary_xcresult_bundle

Could not build the application for the simulator.
Error launching application on iPhone 14 Pro.

Maybe you could try commenting out the line with the code set -e in the file connectors/cargokit/build_pods.sh, then attempt to build again and pay attention to the logs.

I commented out set-e, log changed to this
Launching lib/main.dart on iPhone 14 Pro in debug mode...
Running Xcode build...
Xcode build done.                                            1.8s
Failed to build iOS app
Error (Xcode): File not found: /Users/shuai_yang/Projects/tally/build/ios/Debug-iphonesimulator/rust_in_flutter/libhub.a

Could not build the application for the simulator.
Error launching application on iPhone 14 Pro.

  Launching lib/main.dart on iPhone 14 Pro in debug mode...
  Running Xcode build...
  Xcode build done.                                            1.8s
  Failed to build iOS app
  Error (Xcode): File not found: /Users/shuai_yang/Projects/tally/build/ios/Debug-iphonesimulator/rust_in_flutter/libhub.a

  Could not build the application for the simulator.
  Error launching application on iPhone 14 Pro.

It seem like that rust code compilation not correct, or check the path of libhub.a if exist or not.

libhub.a

libhub.a not exist

libhub.a

libhub.a not exist

Could you post more logs about that compilation of rust?

Also, can you check if the example app inside /example of this repository works well on your machine?
On Intel mac, it runs well:

Also, can you check if the example app inside /example of this repository works well on your machine?
On Intel mac, it runs well:

这是 example 运行 flutter run 的输出:
Launching lib/main.dart on iPhone 14 Pro in debug mode...
Running Xcode build...
Xcode build done.                                            2.7s
Failed to build iOS app
Error (Xcode): cannot find macro `stringify` in this scope

Error (Xcode): cannot find attribute `derive` in this scope

Error (Xcode): could not compile `cfg-if` (lib) due to 2 previous errors

Error (Xcode): could not compile `scopeguard` (lib) due to 16 previous errors

Could not build the application for the simulator.
Error launching application on iPhone 14 Pro.

Not really relevant, but I do understand that why CI didn't catch this problem. It was basically because GitHub CI's macos-latest is based on Intel machine.
It seems we should figure out on real M1 macs(pity that I don't have one)..

The real mistake is
Error (Xcode): File not found: /Users/shuai_yang/Projects/tally/build/ios/Debug-iphonesimulator/rust_in_flutter/libhub.a

Is there anything I can help rule out? Or is there a clue?

Apple Silicon version , the example run well.

Not really relevant, but I do understand that why CI didn't catch this problem. It was basically because GitHub CI's macos-latest is based on Intel machine.
It seems we should figure out on real M1 macs(pity that I don't have one)..

The real mistake is
Error (Xcode): File not found: /Users/shuai_yang/Projects/tally/build/ios/Debug-iphonesimulator/rust_in_flutter/libhub.a

Is there anything I can help rule out? Or is there a clue?

Maybe try to run flutter clean before  flutter run is a possible way.

Oh, I see that it runs well on iOS with M1 macs. Hope that I can be a help, but since I don't have a machine it's hard for me to provide direct support. Maybe it is problems of toolchains, but I'll try to inspect deeper when I have time :)

Oh, I see that it runs well on iOS with M1 macs. Hope that I can be a help, but since I don't have a machine it's hard for me to provide direct support. Maybe it is problems of toolchains, but I'll try to inspect deeper when I have time :)

example works just fine，moreover i replace example/ios/.symlinks directory to my project also work fine,So what's the problem?

Oh, I see that it runs well on iOS with M1 macs. Hope that I can be a help, but since I don't have a machine it's hard for me to provide direct support. Maybe it is problems of toolchains, but I'll try to inspect deeper when I have time :)

example works just fine，moreover i replace example/ios/.symlinks directory to my project also work fine,So what's the problem?

Another discovery is that I can use cargo lipo, then copy libhub.a to build/Debug-iphonesimulator/rust_in_flutter is also ok

Maybe this is related to #83. This seems to be a behavior of cargokit under the hood, hmm

Try this for m1 Mac.
cd macos
pod install
same for iOS. Works for me.

Should we write this workaround in the docs?

I have the same error: it was working once, then failed !!!
I switched to version 4.8.0 or 4.8.2 in pubspec.yaml, but not 4.9.0 because I only get black screen.
It seems to be an EOL problem in build_poc.sh, but I haven't investigated...

Hi @Alphapage , thank you for the report :)
Would you mind sharing your console output with us here? Maybe there can be information about what is causing the error.

t

No problem, @temeddix .
I get the same error that @hoslo describes from his first post:
./cargokit/build_pod.sh: line 2: set: -e
: invalid option

set: usage: set [--abefhkmnptuvxBCHP] [-o option] [arg ...]
Command PhaseScriptExecution failed with a nonzero exit code

Just for info, I replaced build_pod.sh and run_build_tool.sh by 4.8.2 version and now, 4.10.0 is working.

@Alphapage
Version 4.11.1 should removed trailing blank lines .sh files just like you mentioned. Could you try it out and share the result?

Sorry: same error !

You mean you formatted to unix because it was generated from Windows ?
I thought this was the problem. Sorry

Oh, I think I misunderstood your solution. I remove the 'last line' from those file. I will convert CRLF to LF and publish 4.11.2 again.
I've published 4.10 and 4.11 on Windows, where the files were written in CRLF. I will publish 4.11.2 on macOS to avoid those issues.

Verion 4.11.2 is published with LF EOL, not CRLF EOL, unlike 4.11.1
Could you share the result?

Works perfectly now 👍
Congratulations and many thanks

Happy to hear that:) Good luck with your project, and feel free to come back if you have any other issues or ideas!


bug: v3 has problems with vim-sandwich

Did you check docs and existing issues?

[X] I have read all the which-key.nvim docs
[X] I have searched the existing issues of which-key.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
NVIM v0.10.0 Build type: Release LuaJIT 2.1.1713484068
Operating system/version
Windows 10
Describe the bug
Which-key displays and waits for another key press after executing vim-sandwhich surround motions such as ds(, ds{
It only shows for yS, S, ys and cs if you dont type the whole command before the which-key delay but it shows regardless of typing speed for ds
Steps To Reproduce

nvim -u repro.lua
type (word)
position cursor inside parentheses
in normal mode: ds(

Expected Behavior
Do not display which-key after completed vim-sandwich keymap
Health
==============================================================================
which-key: require("which-key.health").check()

- OK Most of these checks are for informational purposes only.
  WARNINGS should be treated as a warning, and don't necessarily indicate a problem with your config.
  Please |DON't| report these warnings as an issue.
- WARNING |mini.icons| is not installed
- WARNING |nvim-web-devicons| is not installed
- WARNING Keymap icon support will be limited.

Checking for issues with your mappings ~
- OK No issues reported

checking for overlapping keymaps ~
- WARNING In mode `n`, <gc> overlaps with <gcc>:
  - <gc>: Toggle comment
  - <gcc>: Toggle comment line
- WARNING In mode `n`, <cs> overlaps with <css>:

- WARNING In mode `n`, <ys> overlaps with <yss>:

- WARNING In mode `n`, <ds> overlaps with <dss>:

- OK Overlapping keymaps are only reported for informational purposes.
  This doesn't necessarily mean there is a problem with your config.

Checking for duplicate mappings ~
- OK No duplicate mappings found

Log
Debug Started for v3.2.0
on_key: i
ModeChanged(n:i)
on_key: w
on_key: o
on_key: r
on_key: d
on_key: <Esc>
ModeChanged(i:n)
on_key: yss
ModeChanged(n:c)
ModeChanged(c:n)
ModeChanged(n:no)
ModeChanged(no:c)
ModeChanged(c:no)
State(start): { "Mode(o)", "Node()", { update = true } }
  getchar
  on_key: (
  got: (
  reattach: { "", "o" }
  feedkeys: { "Mode(o)", "(" }
ModeChanged(no:n)
ModeChanged(n:v)
on_key: (
ModeChanged(v:n)
on_key: ds
ModeChanged(n:c)
ModeChanged(c:n)
ModeChanged(n:no)
on_key: (
ModeChanged(no:c)
ModeChanged(c:no)
State(start): { "Mode(o)", "Node()", { update = true } }
  getchar
  on_key: <Esc>
  got: <Esc>
ModeChanged(no:n)
ModeChanged(n:v)
on_key: :
ModeChanged(n:c)
on_key: q
on_key: !
on_key: <CR>
ModeChanged(c:n)

Repro
vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
  spec = {
    { "folke/which-key.nvim", opts = {} },
    {"machakann/vim-sandwich",
      init = function ()
        vim.g["operator_sandwich_no_default_key_mappings"] = 1
      end,
      config = function ()
        vim.cmd "runtime macros/sandwich/keymap/surround.vim"
      end
    }
  },
})

I'm having a similar issue with nvim-surround. The previous version would display options for surround's keys like ys and ds. Wk doesn't display anything for nvim-surround now. Also, in the previous version "native" operations like dw would execute instantly. Operator pending keys like dw, cw, and ciw don't execute instantly, it pauses and shows many options.

@roycrippen4 that is not related to this issue and I can't reproduce that. If you want me to look at it, submit an issue with a working repro.

Should be fixed now.
Note that typing d first and then waiting to press s later won't work.
That might have worked with which-key before, but no longer works as this was incorrect.
vim-sandwish doesn't seem to define an omap for s, and only has a normal mode ds mapping.
When you press d you enter operator pending mode so only omaps work at that point.

vim-sandwish doesn't seem to define an omap for s, and only has a normal mode ds mapping.
When you press d you enter operator pending mode so only omaps work at that point.

In which-key-less Neovim it enters Operator-pending only after it is sure that only d is pressed. So making a ds Normal mode mapping is enough. Moreover, I don't think creating s Operator-pending mode mapping is a correct way to make ds work as operator (at least because it will be present for every operator, which is not intended).
This might be related to echasnovski/mini.nvim#1058.

This is unrelated to which key though. D or ds doesn't trigger any which key keymaps, so timeoutlen works as normal for those mappongs

Yeah, I've just tried to reproduce the echasnovski/mini.nvim#1058 with 'which-key.nvim' and it seems to work as I'd expect. The core description of the issue is "before, s will show which-key and wait for next action (add, delete ...) but now it just uses nvims default s action( replacing current char going into insert mode).", however I could not reproduce this even before v3.

So as a user, I'm wondering if which-key is supposed to work with mini.surround default keybindings somehow with or without additional configuration? Specifically for the initial key bindings when you press only s -> sa, sd, sr etc...
I have also disabled s key:
vim.keymap.set({ "n", "x" }, "s", "<Nop>")

If you press only s, then Neovim's s keybinding will be executed.
mini.surround only maps sa and others, not the bare s mapping.
Old which-key messed up the normal NEovim behavior in this case.
v3 does it how it should.
If you want to show which-key on s, you can add a keymap for s to WhichKey n s

Awesome! Thanks a lot! I finally got it to work 👍

I'm having the same problem when trying to change or delete text with c/{pattern}<cr> or d/{pattern}<cr>. Should I open another issue for that?


Broken "loop" option on Slides-Per-Column layout

Vue.js version and component version
"vue": "^2.4.1",
"vue-awesome-swiper": "^2.5.4",
Options
loop: true,
slidesPerView: 6,
slidesPerColumn: 2,
What is Expected?
Looping
What is actually happening?
Loop is not working. If we have 12 items per view (6 * 2) so on the end swiper will add only 6 items but not 12 as expected. Try it out!
Thank you

I'm sorry. that all problems with the loop attribute are known issues that come from swiper itself, as a component, no solution, thank you for your feedback!


Moved around power/battery tab components

Moves UPS devices into battery tab
Adds battery/UPS percent as client tab badge
Fixes alignment with UPS
Moves and hides adapter block in power client tab

Closing PR, changes rolled into PR #926 to fix some problems with UI logic


Improve es5 errors

If there's a rule description on Statement, it masks a number of interesting errors. I saw this when extending the ES5 grammar for my Syndicate/js DSL. I add new cases to Statement expecting input such as on message foo() { ... }, and if I forget the message, I get an unhelpful error far away from the real problem. Removing the rule description from Statement gets me much more useful error reports.
(Separately, I've fixed a typo: indentifier => identifier.)

Thanks, Tony!
(Earlier today @tonyg and I talked about a couple of things that could be done about this, e.g., nesting failures. We'll think about this some more, and loop in @lilyx before we do anything.)


FR: counts matrices from all aligners

Is your feature request related to a problem? Please describe.
Only STAR and Salmon (with Ensembl genomes) can currently output count matrices
Describe the solution you'd like
Use featureCounts (and/or HTseq-count and/or bedtools multicov) to generate gene count matrices from BAM files.
This can be applied to all aligners at once. Furthermore, this output could be used in the multiQC.
(optional) Additional context
The process is described here for hisat2.

We are splitting the alignment to the genome and quantification to the transcriptome.
Creating counts matrices from bams may still be added in the future, but are not a priority at the moment. Feel free to reopen this FR if there is a need!


JavaScript part of turbolinks on npm

Can we please make the JavaScript part of turbolinks also available on npm?
I did the port for jquery-ujs and it's very popular.

https://github.com/shakacode/jquery-ujs
https://www.npmjs.com/package/jquery-ujs (21,000 downloads the past month!)

So why does this matter?
I've setup https://github.com/shakacode/react_on_rails/ to make it super easy to use webpack with npm for client side assets. It's very awkward to have some assets load from standard Rails and the rest from npm. This will also helper users of other package systems.
In the long term rubygems should be used mostly for just ruby and JS assets should go on npm.
Thanks for considering this. I can create a fork and PR if you approve of this.

@dhh would you be willing to consider a PR on this one?
We got over 23,000 downloads in the past month on npm of jquery-ujs: https://www.npmjs.com/package/jquery-ujs
Installing JavaScript, given those numbers, via NPM is definitely something the community is doing.
I just reserved turbolinks on npm and would like to help either by doing what we're doing with jquery-ujs (supporting the distribution via a fork) or handing over turbolinks on npm to the rails team (along with jquery-ujs, if that's feasible).
Incidentally, the performance of our React on Rails demo at http://www.reactrails.com/ is quite snappy thanks to Turbolinks!

By the way, this doesn't change the fact that a gem still needs to be installed. One downside of including TurboLinks via NPM is that the version of the ruby code and the JS could could be different.
For React on Rails, v2+, we also have the JavaScript side distributed via NPM, and the Ruby code checks that the version numbers match.
The current code behind the http://www.reactrails.com includes Turbolinks in a "application.js" type file, as shown HERE.
So it is feasible to have a couple exceptions to including all dependencies via npm.
The bottom line is that if we think providing the JS code of TurboLinks via the Gem is the really the only desired distribution mechanism, I probably won't spend much time evaluating the option of npm. But if we might provide this, then I'll prototype this using a fork.
Thanks for your consideration.

Here is a document describing how we include and debug Turbolinks in the context of React on Rails.

Yeah, I think having Turbolinks on NPM makes lots of sense. @sstephenson is
handling the release. Can you transfer the name to him? Thanks!
On Tue, Feb 2, 2016 at 7:50 PM, Justin Gordon<EMAIL_ADDRESS>wrote:

By the way, this doesn't change the fact that a gem still needs to be
installed. One downside of including TurboLinks via NPM is that the version
of the ruby code and the JS could could be different.
For React on Rails, v2+, we also have the JavaScript side distributed via
NPM, and the Ruby code checks that the version numbers match.
The current code behind the http://www.reactrails.com includes Turbolinks
in a "application.js" type file, as shown HERE
https://github.com/shakacode/react-webpack-rails-tutorial/blob/master/app%2Fassets%2Fjavascripts%2Fapplication_non_webpack.js#L5
.
So it is feasible to have a couple exceptions to including all
dependencies via npm.
The bottom line is that if we think providing the JS code of TurboLinks
via the Gem is the really the only desired distribution mechanism, I
probably won't spend much time evaluating the option of npm. But if we
might provide this, then I'll prototype this using a fork.
Thanks for your consideration.
—
Reply to this email directly or view it on GitHub
https://github.com/rails/turbolinks/issues/658#issuecomment-178754219.

Roger that @dhh! Let me know if we can also transfer jquery-ujs.
@callumacrae, my collaborator on jquery-ujs, pointed me to this:

I'd be curious as to how people are using this through NPM. Is this for
those who opt out of the asset pipeline and use grunt or whatever
themselves?
On Wed, Feb 3, 2016 at 7:09 PM, Justin Gordon<EMAIL_ADDRESS>wrote:

Roger that @dhh https://github.com/dhh! Let me know if we can also
transfer jquery-ujs.
@callumacrae https://github.com/callumacrae, my collaborator on
jquery-ujs, pointed me to this:
[image: 2016-02-03_10-03-53]
https://cloud.githubusercontent.com/assets/1118459/12791866/e58dbc8e-ca5d-11e5-89c8-6f4d164f2530.png
—
Reply to this email directly or view it on GitHub
https://github.com/rails/turbolinks/issues/658#issuecomment-179382993.

Basically, yeah. Front-end developers don't usually like interacting with the asset pipeline, and I've spoken to quite a few companies who have switched to using gulp or grunt for that reason (it's nice to be able to write tooling in your main language, you know?). react_on_rails, @justin808's project, uses webpack, which again gets its dependencies from npm.

Sounds good to me. Would be happy to see them mirrored, if we can find a
workflow that's predictable and not likely to splinter the versions and
dependencies.
On Thu, Feb 4, 2016 at 11:32 AM, Callum Macrae<EMAIL_ADDRESS>wrote:

Basically, yeah. Front-end developers don't usually like interacting with
the asset pipeline, and I've spoken to quite a few companies who have
switched to using gulp or grunt for that reason (it's nice to be able to
write tooling in your main language, you know?). react_on_rails,
@justin808 https://github.com/justin808's project, uses webpack, which
again gets its dependencies from npm.
—
Reply to this email directly or view it on GitHub
https://github.com/rails/turbolinks/issues/658#issuecomment-179760712.

To make a release, it's basically just a case of updating the version number in package.json (and if you use the npm version command, it handles the git tag for you too), and then running npm publish. It's super simple :)

Oh, I don't doubt the steps. Just that it needs to be part of the release
pipeline.
On Thu, Feb 4, 2016 at 11:44 AM, Callum Macrae<EMAIL_ADDRESS>wrote:

To make a release, it's basically just a case of updating the version
number in package.json (and if you use the npm version command, it
handles the git tag for you too), and then running npm publish. It's
super simple :)
—
Reply to this email directly or view it on GitHub
https://github.com/rails/turbolinks/issues/658#issuecomment-179764634.

alert('khong tin duoc');

xuong dong  khong

khong co gì

hui

https://www.npmjs.com/package/turbolinks LIVE! We did it today. you can see it in use at http://www.reactrails.com.
PR showing usingit from NPM: https://github.com/shakacode/react-webpack-rails-tutorial/pull/259


Change FluentButton background

Hello,
It seems FluentButton background color in light theme could be stronger to differentiate from the website's background color. Right now, we can barely see some of them are buttons:

What it is the recommend approach to change these buttons background? Is it by overriding/creating a theme?
Thanks.

This is not really an issue we need to change from our side. There are a couple of things you can do

you can use the buttons' BackgroundColor parameter
you can chance the background color of the site with standard CSS or by using one of the defined css variables (see https://fluentui-blazor.net/DesignTokens)


Issue #40

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] The commit message follows our guidelines: https://github.com/xun082/create-neat/blob/master/CONTRIBUTING.md
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?
#40

[ ] Bugfix
[✅] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?

Closes #
Related to #
-Related to #40

What is the new behavior?

Does this PR introduce a breaking change?
[ ] Yes
[ ] No

Other information

Closes #
Related to #
-Related to https://github.com/xun082/create-neat/issues/40
描述有问题
Closes 指向关联的 issue，完成后会自动关闭 issue
Related to 指向了这个 issue 关联的其他 issue

commit 规范存在问题 xxx: 提交内容: #issue
建议把 test 的 commit 合并掉（git rebase -i HEAD~2）

pr也有问题，你提到自己 fork 的仓库了
要来目标仓库提到重构的主分支去


471 tada convertresultunits is overwriting tadamethodspeciationname with na

Updates to fix overwrite of tada method speciation name with na. In order to get this to work correctly, I had to add TADA.MethodSpeciationName as a column in the output of TADA_CreateUnitRef.

@wokenny13 - if you have time to take a look at these changes and run TADA_ConvertResultUnits on a few example data sets that would be great. Thanks!

@wokenny13 - this is ready for review.

Ran through a few example datasets for different states and for both Nitrogen and Phosphorus. The updates have fixed the overwriting issues for these examples that I ran.

@wokenny13 - thanks for running some example data sets. The checks are re-running due to a new vignette I merged into the develop branch. Once all those checks have passed, I will merge in the unit conversion changes.


swid_generator swid --hierarchic produces root Directory without @name

Running
swid_generator swid --package bash --full --pretty --hierarchic | head

produces
<?xml version="1.0" encoding="utf-8"?>
<SoftwareIdentity name="bash" tagId="Fedora_30-x86_64-bash-4.4.23-4.fc30.x86_64" version="4.4.23-4.fc30.x86_64" versionScheme="alphanumeric" xml:lang="en-US" xmlns="http://standards.iso.org/iso/19770/-2/2015/schema.xsd" xmlns:SHA256="http://www.w3.org/2001/04/xmlenc#sha256" xmlns:n8060="http://csrc.nist.gov/ns/swid/2015-extensions/1.0">
  <Entity name="strongSwan Project" regid="strongswan.org" role="tagCreator"/>
  <Meta product="Fedora 30 x86_64"/>
  <Payload n8060:envVarPrefix="$" n8060:envVarSuffix="" n8060:pathSeparator="/">
    <Directory root="">
      <Directory name="etc">
        <Directory name="skel">
          <File SHA256:hash="2584c4ba8b0d2a52d94023f420b7e356a1b1a3f2291ad5eba06683d58c48570d" n8060:mutable="true" name=".bash_logout" size="18"/>
          <File SHA256:hash="28bc81aadfd6e6639675760dc11dddd4ed1fcbd08f423224a93c09802552b87e" n8060:mutable="true" name=".bash_profile" size="141"/>

The top level Directory element is <Directory root=""> without @name attribute.
However, http://standards.iso.org/iso/19770/-2/2015-current/schema.xsd defines the attribute as mandatory:
<xs:attribute name="name" type="xs:string" use="required"/>

The net effect is that swidval /dev/stdin reports
ERROR GEN-1-1: cvc-complex-type.4: Attribute 'name' must appear on element 'Directory'.

on the output and xmllint --schema http://standards.iso.org/iso/19770/-2/2015-current/schema.xsd - says
-:6: element Directory: Schemas validity error : Element '{http://standards.iso.org/iso/19770/-2/2015/schema.xsd}Directory': The attribute 'name' is required but missing.
- fails to validate

Thanks for the report. What would you suggest as fix? An empty name attribute? Removing the element and just start with its children (all with root="", I guess)?

Having empty @name would match the schema formally but likely not its spirit.
Leaving out the top-level Directory would probably be the best way. The @root is not required, so you don't have to include it at all if its value would be empty.
In general though, both the --hierarchic and non-hierarchic outputs use the Directory elements as containers when they often should not. If the goal is to match exactly what rpm -ql outputs, when the parent directory is not owned by the package, it likely should not be listed. That's output of https://github.com/adelton/rpm2swidtag on the same package will be
  <Payload n8060:pathSeparator="/" n8060:envVarPrefix="$" n8060:envVarSuffix="">
    <File size="18" name=".bash_logout" location="/etc/skel" sha256:hash="2584c4ba8b0d2a52d94023f420b7e356a1b1a3f2291ad5eba06683d58c48570d" n8060:mutable="true" key="true"/>
    <File size="141" name=".bash_profile" location="/etc/skel" sha256:hash="28bc81aadfd6e6639675760dc11dddd4ed1fcbd08f423224a93c09802552b87e" n8060:mutable="true" key="true"/>
    <File size="312" name=".bashrc" location="/etc/skel" sha256:hash="30a80bfce3d108d6878cf13dfb1f3a1ea15b141dbdc5bc5803f4ab40a2a39f9c" n8060:mutable="true" key="true"/>

and Directory will only be included in the SWID tag when the directory is owned by the package:
    <Directory name=".build-id" location="/usr/lib">
      <Directory name="48">
        <File size="24" name="04c654c67d1555a98bb75a576cc00a88504bce" key="true"/>
      </Directory>
    </Directory>
    <Directory name="bash" location="/usr/share/doc">
      <File size="99966" name="FAQ" sha256:hash="24a49bf217b350e9c27dc8bcc1317bbad2c2a0d147e0bca72e09dc295b007124"/>
      <File size="7072" name="INTRO" sha256:hash="88d4f438af6af108d5970aed3a88208a295b6dafc2d55b549169bb0a372ec1fb"/>
      <File size="1693" name="RBASH" sha256:hash="be24c8b82aef28c89b11d1276a0cae1792f29802b847cd5f8b16481b7785d7b2"/>
      <File size="1084" name="README" sha256:hash="255cce4868c3fd2887c050fc4e56edc3a246e3dfedd8a58c16e57eaeaf43bee5"/>
      <File size="342306" name="bash.html" sha256:hash="685b744dd3aca1280935972160c523a1dbb55a6b3872f7d554b5cc7e1cb13f22"/>
      <File size="774491" name="bashref.html" sha256:hash="c6e6a560dab921011c6dd746f7403605c9bd0e0b32dab4cc8177a7aa67dee86f"/>
    </Directory>

It just occurred to me, the fact that swid_generator wraps files into Directory elements might be the reason why it fails to list any Files for .src.rpms. In source rpms, the files are not within any directories and that might be the reason why swid_generator does not output them.

Having empty @name would match the schema formally but likely not its spirit.

Maybe name="/" then? Because if --hierarchic is omitted root="/" is used for e.g. the Directory tag of /etc. But maybe that would result in a double slash at the beginning of the path in strongTNC (/ + the path separator, which is also /). So I guess omitting the root Directory tag and the attribute makes more sense.

Leaving out the top-level Directory would probably be the best way. The @root is not required, so you don't have to include it at all if its value would be empty.

OK.

In general though, both the --hierarchic and non-hierarchic outputs use the Directory elements as containers when they often should not.

I guess the idea was to avoid redundant location attributes for the File tags (or maybe it was just how strongTNC processed the tags, I don't know).

If the goal is to match exactly what rpm -ql outputs, when the parent directory is not owned by the package, it likely should not be listed.

I don't think that was the goal. It just collects all the files installed by a package for use with strongTNC in a relatively compact way. But if the standard actually defines the Directory/File tags to mean responsibility/possession that should maybe be changed or made an option.

In source rpms, the files are not within any directories and that might be the reason why swid_generator does not output them.

What do you mean? Where are they stored then? And I think the tool was mainly intended to work with binary packages anyway (executables are the main concern).

I guess the idea was to avoid redundant location attributes for the File tags (or maybe it was just how strongTNC processed the tags, I don't know).

Understood.

I don't think that was the goal. It just collects all the files installed by a package for use with strongTNC in a relatively compact way. But if the standard actually defines the Directory/File tags to mean responsibility/possession that should maybe be changed or made an option.

The XML schema comment says "Provides the ability to apply a directory structure to the files defined in a Payload or Evidence element" about the base="FilesystemItem" and then "A Directory element allows one or more directories to be defined in the file structure" about the name="Directory" type="Directory". So I guess it can be read both ways.

In source rpms, the files are not within any directories and that might be the reason why swid_generator does not output them.

What do you mean? Where are they stored then?

The are just file names, without any directory / path in from of them.

What's strange is that the example in the ISO standard (page 29) shows a Directory tag with a root  attribute but no name attribute (as an explicit alternative to a version in which the top-level tag has both). Maybe that's just wrong (I only have the original version of the standard), or the schema is too restrictive (but I guess if it was optional that would allow File tags without name attribute, which doesn't make sense).
If we remove the outmost Directory tag the question is how we would handle files in the root directory (not that that's very common, and the current code doesn't handle that correctly either I think). I guess we could add a root attribute to that File tag (while that might seem a bit strange, I don't think it violates the standard or schema as both tags are derived from FileSystemItem), or we set the location attribute to "/" (although, the tool was explicitly refactored once to not use that attribute anymore).
Another question is whether the hierarchic option really makes that much sense. It seems pretty redundant to me and might not even save any space depending on the structure of the package (e.g. for the bash package on Ubuntu 16.04 the hierarchic version requires 51 characters more than the flat version, and even 321 characters more with --pretty).
Anyway, I've pushed a commit to the 50-hierarchic-root branch that removes the enclosing tag and adds a root="/" attribute to the first-level Directory tags if the path is absolute (same for files in the root dir). The order of the child tags is different with the patch, though. It's now strictly alphabetical, the previous code added files before subdirs (I don't think that really matters).
I also noticed that the handling of relative paths is a bit strange for the flat file generator (again, something that's probably not very common, but interestingly the unit tests use relative paths). It adds a root attribute with the relative path to the directory in which the file is located, that seems wrong to me as that's never the absolute root path of that directory (a location attribute would probably better fit that). But since that really doesn't seem very common I didn't change it.

In source rpms, the files are not within any directories and that might be the reason why swid_generator does not output them.

What do you mean? Where are they stored then?

The are just file names, without any directory / path in from of them.

I see what you mean. I guess that's because they are unpacked relative to the current directory (at least if they work the same way DEB source packages work). As mentioned above, relative paths are not handled well by the code. And when filtering files in packages there is actually an explicit check whether the path starts with a slash:
https://github.com/strongswan/swidGenerator/blob/0d0941d261925cc01638e88df748c0f2c4395131/swid_generator/environments/common.py#L58-L59
As I already mentioned, for the current use cases source packages are not really relevant. So the question is what you would expect the tool to do with a  source package?

Well, the question is whether swidGenerator plans to be a generic SWID tag generating tool, or more-or-less tied to the strongTNC use case. If the second, then maybe failing when the package is a source package might be a valid behaviour, for example.

Is there a use case for SWID tags for source packages? And what paths would you expect in the tag? Just the relative paths? (According to the standard that would mean relative to the SWID tag, but would that actually be the case?)


Just installed Pyfolio getting AttributeError: module 'empyrical' has no attribute 'information_ratio'

I'm getting this on a number of the example notebooks.. I did update the utils py file in order to get Google data instead of yahoo,, and I do have some portions of the notebooks working but can't get a "full" tear sheet due to this error! Any hints/workarounds appreciated..

Same error, but in my case this occurs in a call from zipline

Can you guys try to install pyfolio master: pip install -U git@https://github.com/quantopian/pyfolio

Somebody renamed information_ratio to excess_sharpe. Make changes by yourselves.

@iamraa I could be mistaken, but I believe that excess_sharpe was added and information_ratio removed - but that they are functions with different behavior, as opposed to one function that was renamed.

actually it was just renamed.

Oh ok! I stand corrected.

Under an Anaconda virtual env for python 3.6
FYI, guess I'll try a manual install..
pip install -U git@https://github.com/quantopian/pyfolio
Collecting git@ https://github.com/quantopian/pyfolio
Could not find a version that satisfies the requirement git@ https://github.com/quantopian/pyfolio (from versions: )
No matching distribution found for git@ https://github.com/quantopian/pyfolio
(py36n) tom@tomServal:~$

Welp a simple
(py36n) tom@tomServal:~$ cd Documents//pyfolio/
(py36n) tom@tomServal:~/Documents/pyfolio$ python setup.py install
/home/tom/anaconda3/envs/py36n/lib/python3.6/site-packages/setuptools/dist.py:336: UserWarning: Normalizing 'v0.7.0+18.ga34222e' to '0.7.0+18.ga34222e'
  normalized_version,```
did not work as hoped..

%matplotlib inline
import pyfolio as pf```
gave me:
RuntimeError: module compiled against API version 0xb but this version of numpy is 0xa```

Guess I'll try a new env...

@dartdog pyfolio does not fix it. You have to fix it manualy in zipline scripts.
%env%/lib/python#.#/site-packages/zipline/finance/risk/
period.py & cumulative.py
Replace information_ratio by excess_sharpe.

@iamraa it actually at least got pyfolio up and going,, as follows... zipline is yet another exercise...
Well I did create a new env in conda, is just did a conda py 3 env,, the rand the setup.py in pyfolio.. it could not find or install numpy itself so I conda installed it then re-rand the setup.py for pyfolio, it kicked off recompliling just about everything.. then I replaced the utils.py in the egg.. with the modified one for Google data. Also had to install the right kernel modules in the new env for jupyter,, and low and behold, I can now run the single stock notebook!!

@twiecki if pyfolio and empyrical are going to be so intertwined, I believe better testing and deployment needs to be made.  Maybe synchronize version numbers / releases when there are reverse compatibility.
These headaches are making pyfolio and all of these other libraries more trouble then they are worth.


Images blurred out on Google Pixel 3

The images across the site seem to be blurred out when viewing on a Google Pixel 3 with Android and Chrome. Seems fine on an iPhone.

Thanks for the update. The intersection observer is not working. I don't have access to this device type for the test yet. Could you visit this Codepen and let me know if you're still having the issue.
https://codepen.io/afrith/pen/BaopQgY

Thanks, I get a rectangle saying 'observed'. Screenshot attached.

I hope to get time to look into this later.  See https://github.com/thriveweb/yellowcake/blob/master/src/components/Image.js

Thanks, so I changed the lazyload value to false and now the images don't load in desktop either, am I changing the right settings?

Cool, you found a bug. I've updated the repo and here is the code, or you can pull it in :).
    if (background && lazy) {
      style = {
        backgroundImage: `url(${
          this.state.isIntersecting ? fullSrc : smallSrc
        })`,
        backgroundSize
      }
    } else {
      style = {
        backgroundImage: `url(${fullSrc})`,
        backgroundSize
      }
    }

https://github.com/thriveweb/yellowcake/blob/master/src/components/Image.js

Then add lazy={false} to the image you want.
Example use: https://github.com/thriveweb/yellowcake/blob/master/src/components/PageHeader.js.
if (large) className += ' PageHeader-large'
  return (
    <div className={`PageHeader relative ${className}`}>
      {backgroundImage && (
        <Image
          background
          resolutions="large"
          src={backgroundImage}
          alt={title}
          size="cover"
          lazy={false}
        />
      )}

Cool, glad it's been of some use! This might sound daft but I'd like to try and pull it in, bit of a novice with github, is it hard to do?

Hey, the images load in incognito using chrome but not in the normal browser page, have cleared the cache etc...
Also, on a different subject is there any documentation about adding another page using specific components?
Thanks,
Joe

Gatsby has an application cache. @joebram you can find this in chrome inspect element > Application tab at the top > Cache on the left-hand menu > cache storage.
Delete that and you should be sorted.

Hello @Firthir . I have the same problem on a OnePlus 6. Have you found a better solution than disable the lazy loading ?
Thank you !

Hello @Firthir . I have the same problem on a OnePlus 6. Have you found a better solution than disable the lazy loading ?
Thank you !


BUG: Setting some window keys breaks help (?)

Did you check docs and existing issues?

[X] I have read all the docs.
[X] I have searched the existing issues.
[X] I have searched the existing discussions.

Neovim Version (nvim -v)
NVIM v0.9.4
Operating System / Version
Arch Linux
Describe the Bug
When assigning some keys for the global window it seems to break the help command (pressing ?). Weird that it only happens on non-filesystem sources such as git or buffers. It doesnt not happen on filesystem source.
I was able to narrow down to these 2 keys consistently break help for me:
        opts = {
            window = {
                mappings = {
                    ["u"] = "navigate_up",
                    ["F"] = "fuzzy_finder",
                },
            },
        },

u -> navigate_up only breaks git status source whereas F->fuzzy_finder breaks both git status and buffers.
Screenshots, Traceback

Exception:
E5108: Error executing lua: /root/.repro/plugins/nui.nvim/lua/nui/line/init.lua:22: attempt to index local 'block' (a nil value)
stack traceback:
        /root/.repro/plugins/nui.nvim/lua/nui/line/init.lua:22: in function 'append'
        ...ugins/neo-tree.nvim/lua/neo-tree/sources/common/help.lua:62: in function 'show'
        ...s/neo-tree.nvim/lua/neo-tree/sources/common/commands.lua:865: in function 'func'
        ...repro/plugins/neo-tree.nvim/lua/neo-tree/ui/renderer.lua:843: in function <...repro/plugins/neo-tree.nvim/lua/neo-tree/ui/renderer.lua:841>

Steps to Reproduce

Open nvim with minimal config:
➜ nvim -u minimaltree.lua

Open tree with :Neotree

Open help with ? (it should work with filesystem source)

Go to another source with >

Open help with ? which 💥

Expected Behavior
Should see regular help popup
Your Configuration
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
    vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
    vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
    { "folke/tokyonight.nvim", lazy = false },
    {
        "nvim-neo-tree/neo-tree.nvim",
        branch = "v3.x",
        dependencies = {
            "nvim-lua/plenary.nvim",
            "nvim-tree/nvim-web-devicons", -- not strictly required, but recommended
            "MunifTanjim/nui.nvim",
        },
        cmd = { "Neotree" },
        opts = {
            window = {
                mappings = {
                    ["u"] = "navigate_up",
                    ["F"] = "fuzzy_finder",
                },
            },
        },
    },
}
require("lazy").setup(plugins, {
    root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")

also here is my lock file:
➜ cat .repro/config/nvim/lazy-lock.json
{
  "lazy.nvim": { "branch": "main", "commit": "33c447b96e1cb1a5a2be87982d5d32bb5054079d" },
  "neo-tree.nvim": { "branch": "v3.x", "commit": "6f8c49956c89e9fefae6acdfe1d57c6293b0a03d" },
  "nui.nvim": { "branch": "main", "commit": "c0c8e347ceac53030f5c1ece1c5a5b6a17a25b32" },
  "nvim-web-devicons": { "branch": "master", "commit": "a1e6268779411048a87f767a27380089362a0ce2" },
  "plenary.nvim": { "branch": "master", "commit": "50012918b2fc8357b87cff2a7f7f0446e47da174" },
  "tokyonight.nvim": { "branch": "main", "commit": "dce0ab49ae751f4f3617ab42d6f20c72369c7cb1" }
}

The problem there is that not all commands work for all sources, and the global window.mappings should only contain mappings that are available in all of the sources that you use.
All search related command sonly work in the filesystem source, and the git_status source does not support anything related to changing cwd.
You should set these mappings within the filesystem.window.mappings section instead.

👍 thanks for quick response. closing as it was my bad. thanks for the explanation!
oh and thank you for the plugin!!! 🎉  I just switched today and I find it a lot more intuitive. amazing job!


Login Loop

Hyprland Version
.
Bug or Regression?
Bug
Description
Finally got Hyprland to start, on an Arch VM, however when logging in, the screen turns black, it waits 2 seconds and puts me back on the login page even though the password is 100% correct.
How to reproduce
Installed Arch on VirtualBox, with archinstall
Crash reports, logs, images, videos

https://wiki.hyprland.org/Getting-Started/Master-Tutorial/#vm


feat: add blas/base/isamax

Description
This RFC proposes to add a routine to find the index of the first element having maximum absolute value as defined in BLAS Level 1 routines. Specifically adding @stdlib/blas/base/isamax is proposed.
Related Issues

Does this pull request have any related issues?

None.
Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.
Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the contributing guidelines.

@stdlib-js/reviewers

This will be simple to review, I'll review this and idamax today evening ( IST )

Can you please iterate over changes made in idamax and see if this PR has anything to change?

Sure, @kgryte will review all the files once before pushing. Thanks for reviewing and merging this PR.


[Run] Switch to WPF UI theme manager

Summary of the Pull Request
Switch to WPF UI theme manager.

PR Checklist

[x] Closes: #29992 #30429
[ ] Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
[ ] Tests: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Dev docs: Added/updated
[ ] New binaries: Added on the required places

[ ] JSON for signing for new binaries
[ ] WXS for installer for new binaries and localization folder
[ ] YML for CI pipeline for new test projects
[ ] YML for signed pipeline

[ ] Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description on the Pull Request / Additional comments

Reverted theme manager work-around in ImageResizer / Run / QuickAccent / TextExtractor. The issue has been fully fixed in 0.76.2 by upgrading WPF UI.
Removed dependencies of Modern WPF and ControlzEx (the theme manager in Common.UI namespace) in favor of WPF UI theme manager.
Simplified theme changing and theme override logic.
Fixed an issue where theme override is lost on Windows startup.

Validation Steps Performed

Tested theme settings override at Windows startup.
Tested theme settings override over HC mode.
Tested system theme change.
Tested multiple theme modes switching.
Verified that plugins icons are correctly applied with system/dark/light theme settings.
Verified that plugins icons are correctly applied with HC 1/2/black/white.

Ready to review!
I have tested many scenarios including change accent color with fixed theme, verified correct errors/plugins icons, HC mode.
I ended up centralizing all theme related stuffs in a ThemeManger class as a single source of truth and have only one event listener for ApplicationThemeManager.Changed.
With the terms "transparency" I mean the mica background that is applied on PT startup on W11 (Screenshot https://github.com/microsoft/PowerToys/issues/30297) but sometimes is lost (happening already in 0.76.2).
I suspect that inside the WPF UI library window backdrop is rollback to default value when certain theme event is received but I am not able to dig further since I am on W10.

Indeed, #30297 is still not fixed ... 🤷  But this does seem more stable.


Strip down onnx to only pb definitions in mobile build

Another note is that we don't need to build with ONNX at all. It's also an option. :)


GH Mobile Money stucked on loading screen

Hello,
When initiating Ghana mobile money payment it get stuck after selecting network type and mobile number.
Momo auth get received via sms and whatsapp. Except the loading does not go away for you to enter payment auth code.
Please can you look into this issue ASAP?
Thank you.

I looked into the source code and realized
mobileMobileCallbacks didn't have chargeWebAuth  functionality in
Also it would be great if after payment the modal closes.
Currently it stays still.

I looked into the source code and realized
mobileMobileCallbacks didn't have chargeWebAuth  functionality in
Also it would be great if after payment the modal closes.
Currently it stays still.

Hi @MohammedBashiru thank you for reaching out to us. Please what version of the SDK are you using?

Hi @MohammedBashiru thank you for reaching out to us. Please what version of the SDK are you using?

Hello @texyz, thank you for your response.
I am using version 2.2.0

Hello @texyz, thank you for your response.
I am using version 2.2.0

@texyz Please can we get fix ET today ?

@texyz Please can we get fix ET today ?

Hi @MohammedBashiru can you please send us a mail at<EMAIL_ADDRESS>to have a closer look at this issue.

Hi @MohammedBashiru can you please send us a mail at<EMAIL_ADDRESS>to have a closer look at this issue.

I also facing the same issue now,can anyone tell me the solution for this issue??

@154010  Please send us a mail at<EMAIL_ADDRESS>

I also facing the same issue now,can anyone tell me the solution for this issue?
Mobile money not working for Ghana currency...
Please update new iOS RaveSDK version....

@AshokRadadiya @154010 This has been resolved, please update your pod. Thank you

Thanks for updating iOS RaveSDK 2.2.2.
I make payment using mobile money with GHS currency code. The
tranasctionSuccessful called
but Status display failed..
We will find some small bugs like when you make payment using mobile money
when loading dialog not spinning.
Also we are not set Recurring payment plans method...
I am waiting for your reply!
Thanks!
On Tue, Feb 16, 2021 at 6:22 PM Rotimi Joshua<EMAIL_ADDRESS>wrote:

@AshokRadadiya https://github.com/AshokRadadiya @154010
https://github.com/154010 This has been resolved, please update your
pod. Thank you
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Flutterwave/RaveSDK/issues/14#issuecomment-779817296,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEODZP5SKZ5M75JCXGTXBNDS7JTCLANCNFSM4V5IBVRA
.

Hi flutterwave team,
I have attached video.
Please check that properly, when payment is successful on iOS then
call tranasctionSuccessful method
call but *status:failed return. *
If payment *status:failed then why not call *tranasctionFailed method.
We are waiting for your reply...
Thank you!
On Wed, Feb 17, 2021 at 12:12 PM Ashok Radadiya<EMAIL_ADDRESS>wrote:

Hi flutterwave team,
I have attached video.
Please check that properly, when payment is successful on iOS then call tranasctionSuccessful method
call but *status:failed return. *
If payment *status:failed then why not call *tranasctionFailed method.
We are waiting for your reply...
Thank you!
On Wed, Feb 17, 2021 at 11:46 AM Ashok Radadiya<EMAIL_ADDRESS>wrote:

Thanks for updating iOS RaveSDK 2.2.2.
I make payment using mobile money with GHS currency code. The tranasctionSuccessful called
but Status display failed..
We will find some small bugs like when you make payment using mobile
money when loading dialog not spinning.
Also we are not set Recurring payment plans method...
I am waiting for your reply!
Thanks!
On Tue, Feb 16, 2021 at 6:22 PM Rotimi Joshua<EMAIL_ADDRESS>wrote:

@AshokRadadiya https://github.com/AshokRadadiya @154010
https://github.com/154010 This has been resolved, please update your
pod. Thank you
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Flutterwave/RaveSDK/issues/14#issuecomment-779817296,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEODZP5SKZ5M75JCXGTXBNDS7JTCLANCNFSM4V5IBVRA
.

Hi @AshokRadadiya apologies for that experience, please can you share the video or the link to the video again, can't find it in the thread.

I am also facing the same issue while using mobile money,the paymet has goes to the cancelled status in dash board.
I dont know why it is happen??

I will proceed to close this issue and mark it as resolved.


openai

Hi,i see the multi_inference code, and i find the assistant_reply is maked by openai(ChatOpenAI), it right?

Yes, the 'assistant_reply ' is obtained from OpenAI, chatgpt or text-davinci


Unable to upload contract to LocalTerra

Hi!
I have a misunderstanding or concern. I am unable to upload my code to LocalTerra, this gives me this error:
Error: rpc error: code = InvalidArgument desc = failed to execute message; message index: 0: Error calling the VM: Error during static Wasm validation: Wasm contract has unknown interface_version_* marker export (see https://github.com/CosmWasm/cosmwasm/blob/main/packages/vm/README.md): store wasm contract failed: invalid request
I might have missed something?

Terra is still using<EMAIL_ADDRESS>so you need to use v0.16.x when you compile your contract

Terra is still using<EMAIL_ADDRESS>so you need to use v0.16.x when you compile your contract

Sorry for my noob question, but how can I compile it for a specific cosmwasm version?