signal SIGSEGV: segmentation violation when running with --format pretty-printer flag

Bug description
When running kubescape as
kubescape scan --enable-host-scan \
          --kubeconfig /mnt/config-k8s-cls-test \
          --verbose \
          --disable-color \
          --format pretty-printer \
          --output output

I'm getting this segmentation error
...
...
...
| Low      | CIS-4.2.8 Ensure that the --hostname-override argument is not set                                                           |        0         |         0          |       6       |      0%      |
| Low      | CIS-4.2.9 Ensure that the --event-qps argument is set to 0 or a level which ensures appropriate event capture               |        0         |         0          |       6       |      0%      |
+----------+-----------------------------------------------------------------------------------------------------------------------------+------------------+--------------------+---------------+--------------+
|          |                                                      RESOURCE SUMMARY                                                       |        20        |         56         |      172      |    9.96%     |
+----------+-----------------------------------------------------------------------------------------------------------------------------+------------------+--------------------+---------------+--------------+
FRAMEWORKS: MITRE (risk: 2.44), AllControls (risk: 5.62), DevOpsBest (risk: 6.11), NSA (risk: 6.45), ArmoBest (risk: 6.18), cis-v1.23-t1.0.1 (risk: 14.25)

* failed to pull image scanning data: credentials are not configured for any registry adaptor. for more information: https://hub.armosec.io/docs/configuration-of-image-vulnerabilities

[success] Scan results saved. filename: output.txt
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x55dd2f34e847]

goroutine 1 [running]:
github.com/kubescape/kubescape/v2/core/pkg/resultshandling/printer/v2.(*PrettyPrinter).printResourceAttackGraph(0xc000cb8720, {0x0?, 0x0?})
	/work/core/pkg/resultshandling/printer/v2/attacktracks.go:74 +0x27
github.com/kubescape/kubescape/v2/core/pkg/resultshandling/printer/v2.(*PrettyPrinter).printAttackTracks(0xc000cb8720, 0xc0001b9980)
	/work/core/pkg/resultshandling/printer/v2/attacktracks.go:121 +0x748
github.com/kubescape/kubescape/v2/core/pkg/resultshandling/printer/v2.(*PrettyPrinter).ActionPrint(0xc000cb8720, 0xc0001b9980)
	/work/core/pkg/resultshandling/printer/v2/prettyprinter.go:65 +0x25b
github.com/kubescape/kubescape/v2/core/pkg/resultshandling.(*ResultsHandler).HandleResults(0xc00111c400)
	/work/core/pkg/resultshandling/results.go:80 +0xeb
github.com/kubescape/kubescape/v2/cmd/scan.getFrameworkCmd.func2(0x55dd3028c8e0?, {0xc0005ff9d0, 0x1, 0x1})
	/work/cmd/scan/framework.go:111 +0x565
github.com/kubescape/kubescape/v2/cmd/scan.GetScanCommand.func2(0xc0003e7b00?, {0xc00018e2d0?, 0x9?, 0x9?})
	/work/cmd/scan/scan.go:55 +0x89
github.com/spf13/cobra.(*Command).execute(0xc0003e7b00, {0xc00018e120, 0x9, 0x9})
	/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:916 +0x862
github.com/spf13/cobra.(*Command).ExecuteC(0xc0003e6c00)
	/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:1044 +0x3bd
github.com/spf13/cobra.(*Command).Execute(...)
	/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:968
github.com/kubescape/kubescape/v2/cmd.Execute()
	/work/cmd/root.go:87 +0x2d
main.main()
	/work/main.go:9 +0x1d

Testing other output types works as intended.
Also note that an output.txt file is created regardless the error.
The output content is
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Controls: 166 (Failed: 46, Excluded: 27, Skipped: 3)
Failed Resources by Severity: Critical — 0, High — 44, Medium — 74, Low — 22

+----------+---------------------------------------------------------------------------------------------------------------------------+------------------+--------------------+---------------+--------------+
| SEVERITY |                                                       CONTROL NAME                                                        | FAILED RESOURCES | EXCLUDED RESOURCES | ALL RESOURCES | % RISK-SCORE |
+----------+---------------------------------------------------------------------------------------------------------------------------+------------------+--------------------+---------------+--------------+
| High     | Resources memory limit and request                                                                                |        2         |         10         |      13       |     14%      |
| High     | Resource limits                                                                                |        2         |         11         |      13       |     14%      |
| High     | List Kubernetes secrets                                                                                |        0         |         3          |      18       |      0%      |
...
...
...
FRAMEWORKS: MITRE (risk: 2.44), AllControls (risk: 5.62), DevOpsBest (risk: 6.11), NSA (risk: 6.45), ArmoBest (risk: 6.18), cis-v1.23-t1.0.1 (risk: 14.25)
* failed to pull image scanning data: credentials are not configured for any registry adaptor. for more information: https://hub.armosec.io/docs/configuration-of-image-vulnerabilities

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Name: calico-node
Kind: DaemonSet
Namespace: kube-system

Score: 6330.50
Severity: High
Total vectors: 26

Environment
Official docker image quay.io/kubescape/kubescape
Steps To Reproduce
# On host machine run
$ docker run -it --rm --entrypoint sh -v ${PWD}:/mnt quay.io/kubescape/kubescape
# In container run
$ kubescape scan --enable-host-scan \
          --kubeconfig /mnt/config-k8s-cls-test \
          --verbose \
          --disable-color \
          --format pretty-printer \
          --output output

Expected behavior

No errors.
When --output file.txt flag is specified I would expect the file.txt to be created, not file.txt.txt
When --verbose flag is specified I would expect the output file to contain verbose output.

Actual Behavior

Getting a segmentation violation error.
Kubescape creates output.txt.txt file.
Kubescape outputs only scan summary table.

@MMquant can you check the version of kubescape running in your container?
You might want to docker pull again and check with the latest version which is v2.0.182.

Hi @matthyx,
I tested it on v2.0.182 and kubescape behaves exactly the same like v2.0.181

Thanks for checking, let me investigate.

@MMquant the problem appears when you combine --verbose with --format pretty-printer.
I have a "fix" but I am not sure if it cures the original problem or just its consequences... I will have to check with @amirmalka

When --output file.txt flag is specified I would expect the file.txt to be created, not file.txt.txt

@vladklokun Please take a look

@dwertent on it :eyes:
@MMquant Hi! Your expectation makes sense to me. However, we support emitting multiple outputs via the same flags, too. So I’m on edge how to keep the invocation consistent across single and multiple output modes.
So keeping that in mind, what would you expect when running the following commands?
kubescape scan --output file --format pretty-printer
kubescape scan --output file --format pretty-printer,json,sarif
kubescape scan --output file.txt --format pretty-printer,json,sarif

@vladklokun Hi,
I understand.
I didn't know that you can pass multiple format options to the --format flag. It's not clear from the docs.
Now it makes sense to me to leave it as it is. This mutliple output option is very handy.

@MMquant Thank you! I appreciate you finding multiple outputs handy.
You bring up a good point regarding documentation. I will try to improve our existing kubescape scan --help docs.
If we mentioned that --output controls the name of the output file without the extension, and that we also support outputting to multiple formats in this help message, would you find that helpful?

For example let's see the --help example here https://github.com/ffuf/ffuf. If a flag supports multiple values they are describing the flag as
Comma separated list of sizes and ranges
Comma separated list of extensions
Comma separated list of <whatever you want>

So something like
Comma separated list of output formats

and
Output file name without extension
Output filename without extension

could work.


Tpwdcee 1337

Coverage decreased (-1.1%) to 89.236% when pulling 007e887e6d4692483f92a9a19813f5e87c162bff on TPWDCEE-1337 into 05fa4881ee85e77dd441f6451e3bd317f824cfc7 on master.


feat: type support for event listener

This pull request continues the work of the following pull request from @Spice-Z: https://github.com/doublesymmetry/react-native-track-player/pull/1594

Adds type for useTrackPlayerEvents, allowing for nice type narrowing when checking for if (event.type == Event.Whatever)
Improves TrackPlayer.addEventListener type by having the listener type be inferred by the Event type
Extracts all the event structures into their own interfaces  as requested by @jspizziri

@puckey great work! This is looking really good. I'm going to do some basic testing in the next few days and hopefully, we can get this merged soon. It'll be an amazing addition.

Cool – I still need to revert some changes to the example app and will also merge in the latest commits from master. Will do so later today.

Okay, that should do it on my side. Let me know if you have any changes you would like to be done.

@dcvz this PR looks good to me and I did some basic testing with it, seems to work perfectly.


Make leaderGuide truly optional

Without this commit, not having leaderguide installed gives errors for undefined
variable g:lmap.

Thanks !


No browser found in android when trying to login

On my Samsung Galaxy S10 I get a "no browser found" error when trying to login (server is chat.sac-uto.ch).
Phone is up-to-date:
Android 12
patchlevel May 1, 2022
Packages installed:
from the releases page: v27.189 https://github.com/zulip/zulip-mobile/releases/download/v27.189/app-arm64-v8a-release.apk

Thanks @daald for the report! Glad it's now working for you.
Can you say a bit more about how you disabled Chrome? We've heard about an issue like this once before, and would love to better understand what's going on -- both to help the next person who sees it, and ideally so we can fix the problem entirely.

Sure.

Long-press to Chrome in the launcher
press the (i)
on the bottom, there is a "disable" button, near "force stop" and "open"

This is to disable apps which are included in the firmware image, like youtube or spotify. if an app was installed through apk or a store, there is an "uninstall" button instead.

To expand on observed behavior:

ReactApplicationContext is unable to find the web browser explicitly chosen in Android as the default
as soon as Google Chrome (com.android.chrome) is present in the system, the login portal's URL is opened properly within the system-wide default browser (which, in my particular case, is not Chrome)

Thanks @daald for those details, and @zer0def for the debugging!
Looking at the code of ours that's at those links, the logic definitely seems dubious — particularly in how it checks for com.android.chrome by name before launching a CustomTabsIntent, which isn't specific to Chrome. I'm not seeing how that bug would lead to a situation where disabling Chrome works around the problem, but I'm glad it did for @daald.
Because this app is now in maintenance mode as we're focused on building the new Zulip mobile app in Flutter, this is an issue I don't expect us to go back and fix for the legacy app. In the new app, fortunately, this functionality is provided by a package from Flutter upstream, and I think its logic is more solid than this. So I'd expect this sort of issue shouldn't arise in the new app — and if it does, I'll definitely be interested in getting to the bottom of it there.

No, it was the other way round. I had chrome disabled, that's why Zulip failed. After re-enabline, it worked. But there were 2 other browsers installed, so there was no reason to fail, just because Chrome was not there.
The above instructions where for reproducing, not for solving the issue...

Ah excellent, thanks for clarifying. All makes sense then. (Still a bug, but it now makes sense how the bug caused the pattern of behavior you saw.)
The reason I'd thought that disabling Chrome was the workaround was this part:

solved. I've disabled chrome browser

I've edited the title a bit to reflect the debugging above, and also the alternate symptom reported in #5795 that I believe is caused by this same issue.


Federation caching

This code is costly, try to use it the least possible.
The algorithm can be upgraded. In hexagrid, the 'path' already uses an A* heuristic, but we can just try the most straightforward path first.
Check if other parts of the federation algorithm can be improved.
Cache results until the buildings (including space stations) change, or the number of satellites available (qic for ivits change). If the number of sateliites available decreases, we can just remove federations from the list. If the number of satellites increase, we need to recalculate. BUT we can already exclude federations made of the same buildings as those in cache.
Finally, if the building value change (and the building does NOT belong to a federation, except for Ivits), we need to recalculate the whole thing.
Also, I noticed sometimes several of the federations suggested were identical. Need to look into it.

[x] Improve hexagrid
[x] Cache federations results
[x] Use cache when the number of satellites remain the same
[x] Use cache when the number of satellites remain the same (ivits)
[x] Use cache with filter when the number of satellites decreases
[x] Use cache with filter when the number of satellites decreases (ivits)
[ ] Use cache with filter when the number of satellites increases, but only test configurations of buildings that aren't in the cache
[ ] Use cache with filter when the number of satellites increases, but only test configurations of buildings that aren't in the cache (ivits)
[x] Clear cache when making a new building / upgrading a building outside a federatoin
[x] Clear cache when upgrading a building inside a federation (Ivits)
[ ] Look into identical federations being generated

Current benchmark for full-game test, without optimisation: 3.8s in one go, 7.5s move by move

Simple federation cache: 1.6s / 3.2s

With a bit more of cache use: 1.5s/3s.


clean up code and images

What changed

Cleaned up images, made terminal window background pale color (considered making these plain code blocks in markdown, but there is no way to highlight a snip-it that way, and I also don't think people like looking at all that code when it isn't necessary. For this case, I think images work better until we get more control over highlighting or styles within code blocks.

Cleaned up code blocks by specifying "none" for markdown fences. This got rid of a lot of whacky colors in the code samples.

Simplified stack file example and instructions.

Removed platform specific commands and suggestions (e.g., curl, vi, cat that won't work on Windows). I either need to find equivalents, or just not have these in there. For now, I've removed them.

FYI
@johndmulhausen @mstanleyjones
Signed-off-by: Victoria Bialas<EMAIL_ADDRESS>

LGTM


STY: Align tables to the left

Closes #10642

All better
https://14621-1460385-gh.circle-artifacts.com/0/html-scipyorg/special.html#bessel-functions

Thanks Eric.

Thanks Eric!
Now, if we could just get the first cell in the table to have top alignment to handle the rare cases where the second cell requires more than one line... 😄

This is probably doable in CSS, is there an example on that page? If not, can you link to one?

kolmogorov and multigammaln, for example.

Actually, all you have to do is make the width of your browser small enough to force many of the "one-line" descriptions to require more than one line in the table.

@WarrenWeckesser yes I had to do this even after your suggestion :)
https://github.com/scipy/scipy-sphinx-theme/pull/14 probably fixes it but I'd like to set up CircleCI over there so that artifacts can be viewed with the changes before we submodule update over here


bug: Error detected while processing BufWritePre Autocommands for "*": Formatter failed see :ConformInfo for more details

Neovim version (nvim -v)
0.9.5
Operating system/version
Windows 10 pro/10.0.19045 build 19045
Add the debug logs

[X] I have set log_level = vim.log.levels.DEBUG and pasted the log contents below.

Log file

Describe the bug
Prettier and stylua fails to format on save instead it gives the above error
What is the severity of this bug?
blocking (cannot use plugin)
Steps To Reproduce

install the conform plugin
open a file and try to save.

Expected Behavior
Prettier and stylua should be able to format on save with no errors
Minimal example file
No response
Minimal init.lua
-- 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",
    "--single-branch",
    "https://github.com/folke/lazy.nvim.git",
    lazypath,
  })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  {
    "stevearc/conform.nvim",
    config = function()
      require("conform").setup({
        log_level = vim.log.levels.DEBUG,
        -- add your config here
      })
    end,
  },
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

Additional context
No response

Also getting an error with prettier, except the message is blank:
Formatter 'prettierd' error:

I had a same error on lua and ts project.
I guess it is bcs of AST parsing is not possible by syntax errors.
I solved with quiet=true option.
  format_on_save = { timeout_ms = 500, lsp_fallback = true, async = true, **quiet = true** },

I had a same error on lua and ts project. I guess it is bcs of AST parsing is not possible by syntax errors. I solved with quiet=true option.
  format_on_save = { timeout_ms = 500, lsp_fallback = true, async = true, **quiet = true** },

Thanks for the help! With quiet=true conform started producing other errors in its log file, which helped me trace back to the root problem. My issue was that I upgraded to Pretter 3, which conflicted with some of my other packages.

@thecode-master-sy please ensure that you have set the log level to DEBUG as mentioned in the bug report template. There are a lot of debug logs missing in ConformInfo that would aid in debugging.

@stevearc  I have done that now, and have updated the log files

So the first step would be to try to run prettier on the command line to see if that works. If you just run prettier.cmd <file> does that format it?
The next step would be to run it with the same args as conform, using stdin. I don't know Windows command shell syntax, but in bash it would be something like prettier.cmd --stdin-filepath C:\Users\thecodemaster\Desktop\ecommerce-website\components\Button.tsx <C:\Users\thecodemaster\Desktop\ecommerce-website\components\Button.tsx.
Hmmm...looking at it again, I wonder if the issue could be caused by the CWD? C:/Users/thecodemaster/Desktop/ecommerce-website has the wrong slashes, but it should be coming from vim.fs.find. Also, if this didn't work I don't think most formatters would work on Windows. Still, to test that out you can remove the CWD and see if that changes the behavior.
require("conform").setup({
  formatters = {
    prettier = {
      cwd = function() end,
    },
  },
})

when I run prettier.cmd on the file path,  it doesn't actually format the file, it just logs out the content of the file.

Same with the  prettier.cmd --stdin-filepath C:\Users\thecodemaster\Desktop\ecommerce-website\components\Button.tsx  but this time it doesn't log anything at all

However if I run prettier --write on the file it formats it


cannot load such file -- json (LoadError)

Hi,
I'm installing dashing on my Fedora 17 Desktop, and the demo project (sweet_dashboard_project) dosn't start.
[ricardo@iridium sweet_dashboard_project]$ dashing start
The source :rubygems is deprecated because HTTP requests are insecure.
Please change your source to 'https://rubygems.org' if possible, or 'http://rubygems.org' if not.
/home/ricardo/.gem/ruby/1.9.1/gems/backports-3.1.1/lib/backports/tools.rb:328:in require': cannot load such file -- json (LoadError) 	from /home/ricardo/.gem/ruby/1.9.1/gems/backports-3.1.1/lib/backports/tools.rb:328:in require_with_backports'
from /home/ricardo/.gem/ruby/1.9.1/gems/dashing-1.0.4/lib/dashing.rb:7:in <top (required)>' 	from config.ru:1:in require'
from config.ru:1:in block in <main>' 	from /home/ricardo/.gem/ruby/1.9.1/gems/rack-1.5.2/lib/rack/builder.rb:55:in instance_eval'
from /home/ricardo/.gem/ruby/1.9.1/gems/rack-1.5.2/lib/rack/builder.rb:55:in initialize' 	from config.ru:1:in new'
from config.ru:1:in <main>' 	from /home/ricardo/.gem/ruby/1.9.1/gems/thin-1.5.1/lib/rack/adapter/loader.rb:33:in eval'
from /home/ricardo/.gem/ruby/1.9.1/gems/thin-1.5.1/lib/rack/adapter/loader.rb:33:in load' 	from /home/ricardo/.gem/ruby/1.9.1/gems/thin-1.5.1/lib/thin/controllers/controller.rb:181:in load_rackup_config'
from /home/ricardo/.gem/ruby/1.9.1/gems/thin-1.5.1/lib/thin/controllers/controller.rb:71:in start' 	from /home/ricardo/.gem/ruby/1.9.1/gems/thin-1.5.1/lib/thin/runner.rb:187:in run_command'
from /home/ricardo/.gem/ruby/1.9.1/gems/thin-1.5.1/lib/thin/runner.rb:152:in run!' 	from /home/ricardo/.gem/ruby/1.9.1/gems/thin-1.5.1/bin/thin:6:in <top (required)>'
from /home/ricardo/bin/thin:23:in load' 	from /home/ricardo/bin/thin:23:in '
[ricardo@iridium sweet_dashboard_project]$ dashing start
The source :rubygems is deprecated because HTTP requests are insecure.
Please change your source to 'https://rubygems.org' if possible, or 'http://rubygems.org' if not.
/home/ricardo/.gem/ruby/1.9.1/gems/backports-3.1.1/lib/backports/tools.rb:328:in require': cannot load such file -- json (LoadError) 	from /home/ricardo/.gem/ruby/1.9.1/gems/backports-3.1.1/lib/backports/tools.rb:328:in require_with_backports'
from /home/ricardo/.gem/ruby/1.9.1/gems/dashing-1.0.4/lib/dashing.rb:7:in <top (required)>' 	from config.ru:1:in require'
from config.ru:1:in block in <main>' 	from /home/ricardo/.gem/ruby/1.9.1/gems/rack-1.5.2/lib/rack/builder.rb:55:in instance_eval'
from /home/ricardo/.gem/ruby/1.9.1/gems/rack-1.5.2/lib/rack/builder.rb:55:in initialize' 	from config.ru:1:in new'
from config.ru:1:in <main>' 	from /home/ricardo/.gem/ruby/1.9.1/gems/thin-1.5.1/lib/rack/adapter/loader.rb:33:in eval'
from /home/ricardo/.gem/ruby/1.9.1/gems/thin-1.5.1/lib/rack/adapter/loader.rb:33:in load' 	from /home/ricardo/.gem/ruby/1.9.1/gems/thin-1.5.1/lib/thin/controllers/controller.rb:181:in load_rackup_config'
from /home/ricardo/.gem/ruby/1.9.1/gems/thin-1.5.1/lib/thin/controllers/controller.rb:71:in start' 	from /home/ricardo/.gem/ruby/1.9.1/gems/thin-1.5.1/lib/thin/runner.rb:187:in run_command'
from /home/ricardo/.gem/ruby/1.9.1/gems/thin-1.5.1/lib/thin/runner.rb:152:in run!' 	from /home/ricardo/.gem/ruby/1.9.1/gems/thin-1.5.1/bin/thin:6:in <top (required)>'
from /home/ricardo/bin/thin:23:in load' 	from /home/ricardo/bin/thin:23:in '
[ricardo@iridium sweet_dashboard_project]$ bundle install
The source :rubygems is deprecated because HTTP requests are insecure.
Please change your source to 'https://rubygems.org' if possible, or 'http://rubygems.org' if not.
Using backports (3.1.1)
Using coffee-script-source (1.6.2)
Using multi_json (1.7.2)
Using execjs (1.4.0)
Using coffee-script (2.2.0)
Using daemons (1.1.9)
Using rack (1.5.2)
Using tzinfo (0.3.37)
Using rufus-scheduler (2.0.18)
Using sass (3.2.7)
Using rack-protection (1.5.0)
Using tilt (1.3.6)
Using sinatra (1.3.6)
Using eventmachine (1.0.3)
Using rack-test (0.6.2)
Using sinatra-contrib (1.3.2)
Using hike (1.2.1)
Using sprockets (2.9.0)
Using thin (1.5.1)
Using thor (0.18.0)
Using dashing (1.0.4)
Using bundler (1.3.4)
Your bundle is complete!
Use bundle show [gemname] to see where a bundled gem is installed.
The weird thing is if I run:
[ricardo@iridium sweet_dashboard_project]$ thin start

Using rack adapter
Thin web server (v1.5.1 codename Straight Razor)
Maximum connections set to 1024
Listening on <IP_ADDRESS>:3000, CTRL+C to stop

Actually runs the http://<IP_ADDRESS>:3000/sample app.
Thanks.

i am also facing same issue
/home/shakeel/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/jbuilder-2.2.5/lib/jbuilder.rb:4:in require': cannot load such file -- multi_json (LoadError) 	from /home/shakeel/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/jbuilder-2.2.5/lib/jbuilder.rb:4:in <top (required)>'
from /home/shakeel/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/bundler-1.8.4/lib/bundler/runtime.rb:76:in require' 	from /home/shakeel/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/bundler-1.8.4/lib/bundler/runtime.rb:76:in block (2 levels) in require'
from /home/shakeel/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/bundler-1.8.4/lib/bundler/runtime.rb:72:in each' 	from /home/shakeel/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/bundler-1.8.4/lib/bundler/runtime.rb:72:in block in require'
from /home/shakeel/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/bundler-1.8.4/lib/bundler/runtime.rb:61:in each' 	from /home/shakeel/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/bundler-1.8.4/lib/bundler/runtime.rb:61:in require'
from /home/shakeel/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/bundler-1.8.4/lib/bundler.rb:134:in require' 	from /home/shakeel/rails_projects/test_app/config/application.rb:7:in <top (required)>'
from /home/shakeel/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/railties-4.1.1/lib/rails/commands/commands_tasks.rb:79:in require' 	from /home/shakeel/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/railties-4.1.1/lib/rails/commands/commands_tasks.rb:79:in block in server'
from /home/shakeel/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/railties-4.1.1/lib/rails/commands/commands_tasks.rb:76:in tap' 	from /home/shakeel/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/railties-4.1.1/lib/rails/commands/commands_tasks.rb:76:in server'
from /home/shakeel/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/railties-4.1.1/lib/rails/commands/commands_tasks.rb:40:in run_command!' 	from /home/shakeel/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/railties-4.1.1/lib/rails/commands.rb:17:in <top (required)>'
from bin/rails:8:in require' 	from bin/rails:8:in '

I'm using dashing on a french CentOS 7 install and have the same issue as described.  This date from 2013 and has been closed without a solution.
Must I understand this project has been abandoned since then and the book i'm reading is just too old to be pertinent anymore?

Hi, I have just fixed the issue on Fedora 22 with rails 5.0.2. After add "gem 'json'" into Gemfile, "rails server" got success. localhost:3000 can be displayed on browser. "cannot load such file -- json (LoadError)" was dissapeared when running "rails server". Thanks!


Add Support for Wall Follower Algorithm

It would be very nice to support the wall follower algorithm. We can go about this a couple of different ways.
Add another solve method.
We would rename def solve_maze to something like def solve_recursive_back and then add a new method, def solve_wall_follower.
Pros:
It keeps the code simple
Quick
Few auxiliary changes (for example, we may need to refactor def _validate_neighbors_solve
Cons
In the long run, the code may get incredibly unstructured if we support more.
Create a solver Class
Create a base class that represents a solution method.
For example,
class Solver
{
public:
virtual MAZE solve();
}

class WallFollower : Solver
{
 MAZE solve();
}

class RecursiveBacktracer : Solver
{
   MAZE solve();
}

etc
etc

We could always create an interface to it at a later time so that users don't need to mess around with class instantiation.
Pros:
Better long term support
Cons:
Adds complexity
Not as easy to use?
Options:

Don't support the algorithm
Add a new method for it
Create the class system

Thanks for all your suggestions and contributions! Yes, initially I didn't think of including more algorithms so I just had everything maze stuff in the Maze class, but yes, creating a solver class might definitely be a good way to go. Also the wall follower algorithm sounds like a good addition.

Also, I very recently added support for a breadth-first search solver as well as a (yet not fully functioning) bidirectional depth-first solver.


Request for a server files download

Hi vaga!
This would make our lives much easier (in particular Helk's) if there was some sort of server files download to use when updating a server running MageTech Gate. :)

working on it. trying to figure a way to set up server files one a PC that barely wants to run mc. Need to check with a guy who offered to do server files for me.

Taken care of.


Annoying scrollbar

When the notification is invoked, it leaves an annoying scrollbar on the right side of the notification box, which doesn't look nice at all. I believe it can be solved by simply deleting the "overflow" property from the css in the "id=x-notify-container" element.

I'm guessing you're on Firefox. Sorry about that, I've added scrollbar-width:none; as the overflow is there in case there are enough notifications to fill the screen and require you to scroll through them. I've also set the overflow-y to auto so it doesn't show on any other browsers until actual scrolling is required. Forgot to test the notifications on Firefox so I missed that. Thank you very much for bringing it to my attention.

Just tested it and it is solved. No problem, thanks also for doing this awesome project that saves me so much time. By the way, the same thing was happening in Chromium (Just for the record, because it's already solved).


betterlockscreen: 4.0.4 -> 4.1.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/pavanjadhaw/betterlockscreen/releases.
meta.description for betterlockscreen is: Fast and sweet looking lockscreen for linux systems with effects!
meta.homepage for betterlockscreen is: https://github.com/pavanjadhaw/betterlockscreen
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.1.0 with grep in /nix/store/nyb1vdmm7x5n3m249f7fkixafzrwh5m2-betterlockscreen-4.1.0
found 4.1.0 in filename of file in /nix/store/nyb1vdmm7x5n3m249f7fkixafzrwh5m2-betterlockscreen-4.1.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
betterlockscreen

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/nyb1vdmm7x5n3m249f7fkixafzrwh5m2-betterlockscreen-4.1.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A betterlockscreen https://github.com/r-ryantm/nixpkgs/archive/08af31c9e2d14b1712c792b5476c2d74327063ca.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/nyb1vdmm7x5n3m249f7fkixafzrwh5m2-betterlockscreen-4.1.0
ls -la /nix/store/nyb1vdmm7x5n3m249f7fkixafzrwh5m2-betterlockscreen-4.1.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

betterlockscreen

Maintainer pings
cc @eyJhb @SebTM for testing.

Duplicate of https://github.com/NixOS/nixpkgs/pull/251772


Add quick fix for avoid_returning_null_for_void

The fix should remove the null (and preceding space).

https://dart-review.googlesource.com/c/sdk/+/201102


Any plan for OpenLLaMA-65B？

Do you have a plan for releasing OpenLLaMA-65B？ Maybe met the GPUs  amount bottleneck? Thanks

Unfortunately we don't have the compute resources to do that.

Unfortunately we don't have the compute resources to do that.

So how many H100/H800 GPUs do you need to train a OpenLLaMA-65B model?  May I ask the minimum number?

I believe you will need at least 1000 of them to finish the training within a month.

If I don't mind the amount of month to train, for example, I have 5 months to train a 65B model, can I say that I need at least 1000/5=200 GPUs? If I have 10 months to train, can I say I need at least 1000/10=100 GPUs? Thanks

That sounds about right.


htp_connp_t leaks memory

htp_connp_t is allocating and failing to free request_line_raw field of connp->in_tx
==1888==    at 0x4C26FDE: malloc (vg_replace_malloc.c:236)
==1888==    by 0xE62595C: bstr_alloc (bstr.c:33)
==1888==    by 0xE625A50: bstr_dup_mem (bstr.c:222)
==1888==    by 0xE62D47D: htp_connp_REQ_LINE (htp_request.c:652)
==1888==    by 0xE62CE08: htp_connp_req_data (htp_request.c:948)
==1888==    by 0xF66C32A: modhtp_iface_data_in (htp.c:918)

Further data shows the entire in_tx is leaked:
==1888==    at 0x4C26FDE: malloc (vg_replace_malloc.c:236)
==1888==    by 0xEA56921: ib_mpool_create_ex (mpool.c:90)
==1888==    by 0xE840FF1: ib_tx_create (engine.c:553)
==1888==    by 0xF66D8A0: modhtp_htp_tx_start (htp.c:228)
==1888==    by 0xE625F32: hook_run_all (hooks.c:144)
==1888==    by 0xE62D253: htp_connp_REQ_IDLE (htp_request.c:846)
==1888==    by 0xE62CE08: htp_connp_req_data (htp_request.c:948)
==1888==    by 0xF66C32A: modhtp_iface_data_in (htp.c:918)

Please check with the current libhtp master.

Updating libhtp gets rid of the first leak reported, but the second leak is unchanged.
BTW, valgrind reports a number of other issues that may merit bug reports!

With major recent changes to mpool code all mem leaks will be investigated as a task


update postgres_jdbc to use map as return value in properties builder

A Helpful Guide For Navigating Our Branches

If this is a hotfix, make your PR against master.
If your change can ship immediately, make your PR against dev-tdvt.
If your change is for a future release, make your PR against the appropriate holding branch (eg dev-2020.1)

Also:

Please update the changelog of the project you modified, either under vNext or under a point release if you bumped the version.
If you are merging into master, update the root README.md if the PR includes a release of the SDK, Connector Packager, or TDVT.

Thank you and feel free to delete this from your PR description!

I changed the PR to merge into 2020.1-dev, but it went from 1 file changed to 8. Some of the changes are definitely harmless, but not sure about all of them. Also, there's a merge conflict. It might be easier to just close this and make a new PR.


some external references have disappeared

http://pombase2.bioinformatics.nz/gene/SPAC1952.17c

probably due to changes for #477 - the iPMTnet entry has only reached GO.xrf_abbs today
reopen if it doesn't fix itself in a day or two (or if Kim has a clever way of making a missing entry not break the rest of them)

probably due to changes for #477

Yep!
I've fixed the code so it doesn't bail out if the config is missing from GO.xrf_abbs so this shouldn't happen again.


Observations for README betterment

Folks may not immediately realize that running npm start & grunt serve spits out a PID which they can use to kill the server side of things. And that the rest of the logs are about the deployment and we start watching the client for changes.
For the first few minutes, users may find themselves scratching their heads after hitting ctrl+c and trying the same step again ... as to why the port is occupied.
Depending on the scroll buffer on one's terminal window, they may have already lost the PID or simply may not know to go looking for it.
Maybe some commonly agreed upon language for the README that is way way shorter than the essay I just wrote here ... can be coined?
Running grunt serve without installing nodemon first ... still kicks off the process regardless. Only this time there is no PID so it gets a bit arbitrary to go looking for a node process to kill. Now yes, the next thing one may do right away is npm install -g nodemon and then grunt serve again but the earlier command has taken up the port (which one assumes had just plain failed but such is not the case) and again users are briefly left wondering ... what???
Umm, so maybe some language that says: even if grunt serve fails due to lack of nodemon, a process occupying the port has started and must be killed before using grunt serve again.

I ran into the running process issue as well. You can just kill the node process - pid can be figured out via command line (e.g. ps -ax | grep node) and to confirm you can correlate it with what you see in the Activity Monitor / task manager - see attached.

It would be best to have the grunt serve command start the API, for instance with grunt-nodemon.

I have updated the project so it will automatically start the API when you start the project with grunt serve and updated the README accordingly.
Can you please confirm that this solves this issue @pulkitsinghal?

Confirmed, its easier and quicker to use.


validate start time on reservation request

@cbosborn There was a bit of confusion last week with somebody trying to reserve a time in the past and Celena mentioned it'd be nice to get a user friendly error message when that happens.
I can include a force flag to accommodate users when trying to reserve in the past.

Don't need in this in qcs-cli


Add patch to enable allowRecursiveCommitsWithSynchronousMountOnAndroid feature flag

Explanation of Change

Fixed Issues

$ https://github.com/Expensify/App/issues/52496
PROPOSAL: https://github.com/Expensify/App/issues/52496#issuecomment-2480452598
Tests

Tap FAB > Start chat.
Go back by swiping or using the back button.
Repeat the above steps 10 times or until the app crashes, whichever comes first. The test passes if the app doesn't crash, and fails if it does.

[x] Verify that no errors appear in the JS console

Offline tests

Tap FAB > Start chat.
Go back by swiping or using the back button.
Repeat the above steps 10 times or until the app crashes, whichever comes first. The test passes if the app doesn't crash, and fails if it does.

QA Steps

Tap FAB > Start chat.
Go back by swiping or using the back button.
Repeat the above steps 10 times or until the app crashes, whichever comes first. The test passes if the app doesn't crash, and fails if it does.

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
https://github.com/user-attachments/assets/14272c38-4ad8-4cc2-aa2e-8d996dad68bb

Android: mWeb Chrome
https://github.com/user-attachments/assets/583c5959-ad89-48a0-84e9-487ca50f6b15

iOS: Native
https://github.com/user-attachments/assets/ac2057e9-a408-4f23-9a8c-d851f0a1961c

iOS: mWeb Safari
https://github.com/user-attachments/assets/4808d3bb-7889-473e-bb19-3daaf2f7b99f

MacOS: Chrome / Safari
https://github.com/user-attachments/assets/22f62d62-5834-43a3-b88c-cd58bf75b587

MacOS: Desktop
https://github.com/user-attachments/assets/4c5ad45a-866f-416a-924e-5c7adbb409d5

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native
https://github.com/user-attachments/assets/84d64eda-2efc-4f50-999f-9a6bb81d9dd3

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.


Feature request: Add a way to replace every instance of a substring on the current line

(This is not a bug report, so I'm not following the standard template)
First of all, let me say that zsh-vi-mode is amazing, I'm certain it's the best Vi-mode plugin for any shell that exists.
However I have encountered one pretty common scenario that I would easily be able to resolve inside Vim, but is more challenging in zsh-vi-mode.
If I have a line like:
ln -sf ../syncthing/dotfiles/darkman .config/darkman

If I wanted to replace "darkman" with "direnv", in Vim I would just place my cursor on the word "darkman", press <C-n><C-n> to select both instances of "darkman", then press c to replace the word and enter insert mode, then type "direnv". Super quick and easy. (Though, to be clear, this is using the vim-visual-multi plugin, this is not built-in Vim functionality.)
Without multiple selections, this becomes a lot more tedious, especially when I have to repeat it a bunch of times for several different symlinks.

To summarize the feature request:
Problem: Replacing many instances of the same text on a line is tedious
Solution in Vim/Neovim: A multi-select plugin
Solution in zsh-vi-mode: ?
Possible solutions:

Add multiple cursors to zsh-vi-mode (drawback: extremely complicated)
Add limited support for multiple selections

Make a visual selection, then press a keybinding to also select the next instance of the selected text
Also needs a keybinding to skip the current selection and jump to the next one
Allow pressing d or x to delete the selection and leave multi-select mode, or press c to replace the selections and insert some new text, I to enter insert mode at the start of every selection or A to enter insert mode at the end of every selection
Simpler than full-blown multi-cursor mode, still massively powerful

Add a "replace all" keybinding

The user selects a span of text
Presses a keybinding called something "replace all"
This deletes the selected text and enters insert mode
When leaving insert mode, all the other instances of the selected text on the same line is also replaced
Much, much simpler than the above solutions, still solves the issue

Hi @Hubro,
Thank you very much for your good idea and scenarios, I'd love to explore this feature in the next days.
Thanks & Regards


List of dependencies that should be updated from time to time

Here is a list of different places in LightGBM's GitHub repo where we specify some dependencies or helpers. Quite often we should specify a particular version of such software. And these versions are tend to obsolete with time. If you see that there is a newer version comparing to what we have, please feel free to propose a PR with updates or simply leave a comment here.

SHAs of commits of third-party dependencies in the external_libs folder. If there are some checkpoints (markers of stable versions) of these libraries, e.g. Releases at GitHub, the most recent stable release should be used (not the unstable latest master commit). If there are no such indicators of stable commit, use the latest available one. How to update GitHub submodules.
SHAs of commits OpenCL libraries integration (same notes about versions as above):
1.https://github.com/microsoft/LightGBM/blob/f997a0692ca0f26740d2bdef2695c3e881d4e918/CMakeIntegratedOpenCL.cmake#L5-L6
2.https://github.com/microsoft/LightGBM/blob/f997a0692ca0f26740d2bdef2695c3e881d4e918/CMakeIntegratedOpenCL.cmake#L8-L9
3.https://github.com/microsoft/LightGBM/blob/f997a0692ca0f26740d2bdef2695c3e881d4e918/CMakeIntegratedOpenCL.cmake#L11-L12
Visual Studio version for OpenCL libraries integration https://github.com/microsoft/LightGBM/blob/f997a0692ca0f26740d2bdef2695c3e881d4e918/CMakeIntegratedOpenCL.cmake#L66-L68
MinGW w64 version at Appveyor https://github.com/microsoft/LightGBM/blob/f997a0692ca0f26740d2bdef2695c3e881d4e918/.appveyor.yml#L26
PublishBuildArtifacts Azure Pipelines task (multiple occurrences, do search the file for PublishBuildArtifacts keyword)
macOS image version at Azure Pipelines (Attention! Should be the oldest available, not the newest one) https://github.com/microsoft/LightGBM/blob/f997a0692ca0f26740d2bdef2695c3e881d4e918/.vsts-ci.yml#L144
Xcode version in Azure Pipelines macOS image (Attention! Should be the oldest available, not the newest one), also make updates in the Python installation guide about that this version is used for Python-package wheels generation https://github.com/microsoft/LightGBM/blob/f2695daba2506d047831e39aeb521e94adec5e8d/.ci/setup.sh#L7
DownloadBuildArtifacts Azure Pipelines task https://github.com/microsoft/LightGBM/blob/f997a0692ca0f26740d2bdef2695c3e881d4e918/.vsts-ci.yml#L220
NuGetCommand Azure Pipelines task https://github.com/microsoft/LightGBM/blob/f997a0692ca0f26740d2bdef2695c3e881d4e918/.vsts-ci.yml#L228
PublishBuildArtifacts Azure Pipelines task https://github.com/microsoft/LightGBM/blob/f997a0692ca0f26740d2bdef2695c3e881d4e918/.vsts-ci.yml#L233
GitHubRelease Azure Pipelines task https://github.com/microsoft/LightGBM/blob/f997a0692ca0f26740d2bdef2695c3e881d4e918/.vsts-ci.yml#L238
CMake minimum required version and minimum supported versions of different compilers (including CUDA) in CMakeLists.txt in case of adding new breaking changes in the CPP code of LightGBM (also, make updates in the installation guide and in the Python installation guide)
Regenerate files in Visual Studio solution folder in case of bumping minimum required version of MSVC++
Checkout repository GitHub Action (multiple occurrences, do search in the .github/workflows folder for actions/checkout keyword in all files)
NVIDIA CUDA Docker versions https://github.com/microsoft/LightGBM/blob/65349b41c20116007e602c17a68e375869a7e594/.github/workflows/cuda.yml#L25-L37
upload-artifact GitHub Action https://github.com/microsoft/LightGBM/blob/f2695daba2506d047831e39aeb521e94adec5e8d/.github/workflows/r_artifacts.yml#L48
setup-pandoc GitHub Action https://github.com/microsoft/LightGBM/blob/f2695daba2506d047831e39aeb521e94adec5e8d/.github/workflows/r_package.yml#L119
Versions of Visual Studio for R-package tests (two latest available versions) https://github.com/microsoft/LightGBM/blob/f2695daba2506d047831e39aeb521e94adec5e8d/.github/workflows/r_package.yml#L69-L70 https://github.com/microsoft/LightGBM/blob/f2695daba2506d047831e39aeb521e94adec5e8d/.github/workflows/r_package.yml#L76-L77
Version of the GitHub REST API (multiple occurrences, do search for application/vnd.github keyword in the repo)
List of linters for R-package linting script file
Entire Dockerfile(s) in the lightgbm-ci-docker repository that are used in our CI environments
OpenCL AMD App SDK for Windows (new file should be uploaded to Releases page of the repo) https://github.com/microsoft/LightGBM/blob/f2695daba2506d047831e39aeb521e94adec5e8d/.ci/install_opencl.ps1#L3
OpenCL AMD App SDK for Linux (new file should be uploaded to Releases page of the repo) https://github.com/microsoft/LightGBM/blob/f2695daba2506d047831e39aeb521e94adec5e8d/.ci/setup.sh#L72
SWIG for Windows (new file should be uploaded to Releases page of the repo) https://github.com/microsoft/LightGBM/blob/f2695daba2506d047831e39aeb521e94adec5e8d/.ci/test_windows.ps1#L44
libboost from Martin Hierholzer's ppa https://github.com/microsoft/LightGBM/blob/f2695daba2506d047831e39aeb521e94adec5e8d/.ci/setup.sh#L70
gcc version that comes from brew on macOS https://github.com/microsoft/LightGBM/blob/f2695daba2506d047831e39aeb521e94adec5e8d/.ci/test.sh#L4-L5
Three latest available macOS versions in the Python wheel filename https://github.com/microsoft/LightGBM/blob/f2695daba2506d047831e39aeb521e94adec5e8d/.ci/test.sh#L110
R 4.x version for Linux from R-project ppa https://github.com/microsoft/LightGBM/blob/f2695daba2506d047831e39aeb521e94adec5e8d/.ci/test_r_package.sh#L30-L32
R 4.x version for Windows from official CRAN site https://github.com/microsoft/LightGBM/blob/f2695daba2506d047831e39aeb521e94adec5e8d/.ci/test_r_package_windows.ps1#L49
Rtools 4.x version for Windows (new file should be uploaded to Releases page of the repo) https://github.com/microsoft/LightGBM/blob/f2695daba2506d047831e39aeb521e94adec5e8d/.ci/test_r_package_windows.ps1#L48
MiKTeX for Windows (new file should be uploaded to Releases page of the repo) https://github.com/microsoft/LightGBM/blob/f2695daba2506d047831e39aeb521e94adec5e8d/.ci/test_r_package_windows.ps1#L107
Minimum Autoconf version for R-package https://github.com/microsoft/LightGBM/blob/d107872a5342442420edaa1d1849901f865f2331/R-package/configure.ac#L6
Autoconf version for R-package
Ubuntu version in which Autoconf should be run to generate configure file for R-package: https://github.com/microsoft/LightGBM/tree/master/R-package#changing-the-cran-package and https://github.com/microsoft/LightGBM/blob/9388b2ecc1649d0a68d3c1ff053775ff00d4d288/.github/workflows/r_configure.yml#L12
Versions of R-package dependencies https://github.com/microsoft/LightGBM/blob/d107872a5342442420edaa1d1849901f865f2331/R-package/DESCRIPTION#L45-L57
Version of {roxygen2} used in R-package docs

https://github.com/microsoft/LightGBM/blob/fb37e5074ad0163afd9d88366b58075899775cfa/R-package/DESCRIPTION#L66
https://github.com/microsoft/LightGBM/blob/fb37e5074ad0163afd9d88366b58075899775cfa/docs/env.yml#L15

Supported versions of Visual Studio in R-package https://github.com/microsoft/LightGBM/blob/d107872a5342442420edaa1d1849901f865f2331/R-package/src/install.libs.R#L66-L70
Minimum required versions of system dynamic libraries LightGBM links to in case of adding new breaking changes in the CPP code of LightGBM (also, make updates in the installation guide and in the Python installation guide)
Azure Pipelines REST API version for artifacts downloading link https://github.com/microsoft/LightGBM/blob/d107872a5342442420edaa1d1849901f865f2331/docs/_static/js/script.js#L41
Minimum required version of libboost for GPU-version in CMakeLists.txt (also, make updates in the installation guide) https://github.com/microsoft/LightGBM/blob/d107872a5342442420edaa1d1849901f865f2331/CMakeLists.txt#L137
Minimum required version of OpenCL for GPU-version (multiple occurrences, do search for opencl keyword in the installation guide)
Visual Studio mapping for Boost binaries in the installation guide
Supported CUDA architectures in CMakeLists.txt for CUDA-version https://github.com/microsoft/LightGBM/blob/d107872a5342442420edaa1d1849901f865f2331/CMakeLists.txt#L159
Read the Docs config file (version of config file; build section; adding new and removing deprecated config values)
Minimum required version of Sphinx in case of adding new breaking changes in docs generating process https://github.com/microsoft/LightGBM/blob/d107872a5342442420edaa1d1849901f865f2331/docs/conf.py#L77
conda environment for building docs https://github.com/microsoft/LightGBM/blob/master/docs/env.yml
Minimum required version of sphinx_rtd_theme for documentation generation in docs' folder README file (search for sphinx_rtd_theme; version should be the same as in conda environment)
Suggested tag for RTD Docker image for generating documentation locally in docs' folder README file (search for readthedocs/build; tag should be the most recently released)
Entire Dockerfiles in the docker folder
Versions of Python-package dependencies https://github.com/microsoft/LightGBM/blob/9cc3777c8a892c7ca253864839a926fd35f2b775/python-package/setup.py#L338-L350
Supported versions of Visual Studio in Python-package https://github.com/microsoft/LightGBM/blob/9cc3777c8a892c7ca253864839a926fd35f2b775/python-package/setup.py#L183
Supported versions of Visual Studio Platform Toolsets in Python-package https://github.com/microsoft/LightGBM/blob/9cc3777c8a892c7ca253864839a926fd35f2b775/python-package/setup.py#L168
Supported Python versions (see #2713 for example how to start running tests with new Python version) https://github.com/microsoft/LightGBM/blob/9cc3777c8a892c7ca253864839a926fd35f2b775/python-package/setup.py#L373-L376
The oldest supported Python version (shouldn't be too strict just because that version reached EOL; it should reflect only known incompatibilities)
https://github.com/microsoft/LightGBM/blob/d31346f6c265e994c54ebddd19ed1fb6445ba0c9/python-package/setup.py#L343
Google Test release tag https://github.com/microsoft/LightGBM/blob/337103d39158001b695f70eb2b2fca6180c7868a/CMakeLists.txt#L475-L476

@jameslamb Please help to clarify. Should we monitor new releases for R 3.x stuff or they have been frozen forever?

@jameslamb Please help to clarify. Should we monitor new releases for R 3.x stuff or they have been frozen forever?

@jameslamb Please help to clarify. Should we monitor new releases for R 3.x stuff or they have been frozen forever?

No R 3.x resources will change.
Rtools for R 3.x is frozen forever. https://cran.r-project.org/bin/windows/Rtools/history.html

We also do not need to look for new versions of R itself. R doesn't have a concept of "long-term support" releases like other projects. So you won't see a bugfix that results in, say, R 4.1.1 and R 3.6.4 at the same time.
You can see the history of release dates at https://cran.r-project.org/bin/windows/base/old/.

@jameslamb Please help to clarify. Should we monitor new releases for R 3.x stuff or they have been frozen forever?

No R 3.x resources will change.
Rtools for R 3.x is frozen forever. https://cran.r-project.org/bin/windows/Rtools/history.html

We also do not need to look for new versions of R itself. R doesn't have a concept of "long-term support" releases like other projects. So you won't see a bugfix that results in, say, R 4.1.1 and R 3.6.4 at the same time.
You can see the history of release dates at https://cran.r-project.org/bin/windows/base/old/.

I'm so sorry for my English, but I can read this answer in two ways. Which is correct? 😄

No,     R 3.x resources will change.

No R 3.x resources will change.

Rtools for R 3.x is frozen forever.

Ah, I see, thanks! Removed from the list.

You can see the history of release dates at https://cran.r-project.org/bin/windows/base/old/.

I see there are
R 4.0.3 (October, 2020)
R 4.0.2 (June, 2020)
R 4.0.1 (June, 2020)
R 4.0.0 (April, 2020)

What about 4.0.4? Why we shouldn't wait for it?

I'm so sorry for my English, but I can read this answer in two ways. Which is correct? 😄

No,     R 3.x resources will change.

No R 3.x resources will change.

Rtools for R 3.x is frozen forever.

Ah, I see, thanks! Removed from the list.

You can see the history of release dates at https://cran.r-project.org/bin/windows/base/old/.

I see there are
R 4.0.3 (October, 2020)
R 4.0.2 (June, 2020)
R 4.0.1 (June, 2020)
R 4.0.0 (April, 2020)

What about 4.0.4? Why we shouldn't wait for it?

Oh sorry, let me rephrase.

there will never be a new R 3.x release
there will never be a new Rtools 3.x release

For 4.x series, there will continue to be new releases. They tend to do 4 or 5 per year. The next release of R will be R 4.1.0 (). That might or might not involve a new Rtools 4.x release. I use this mirror of the R source (R development is not actually done on GitHub) to keep track: https://github.com/wch/r-source/blob/trunk/VERSION

Oh sorry, let me rephrase.

there will never be a new R 3.x release
there will never be a new Rtools 3.x release

For 4.x series, there will continue to be new releases. They tend to do 4 or 5 per year. The next release of R will be R 4.1.0 (). That might or might not involve a new Rtools 4.x release. I use this mirror of the R source (R development is not actually done on GitHub) to keep track: https://github.com/wch/r-source/blob/trunk/VERSION

Thank you very much!
Then I'm removing R 3.x from the list as well.

The next release of R will be R 4.1.0. That might or might not involve a new Rtools 4.x release.

Got it, great! Then I think we can have them both in the list.

They tend to do 4 or 5 per year.

Quite frequent. For instance,

Visual Studio version for OpenCL libraries integration

VS releases have 2-year cycle, but I still find it useful to have VS mentioned here.

Thank you very much!
Then I'm removing R 3.x from the list as well.

The next release of R will be R 4.1.0. That might or might not involve a new Rtools 4.x release.

Got it, great! Then I think we can have them both in the list.

They tend to do 4 or 5 per year.

Quite frequent. For instance,

Visual Studio version for OpenCL libraries integration

VS releases have 2-year cycle, but I still find it useful to have VS mentioned here.

I want to note here that R 4.1.0 is planned for release on May 18, 2021.
https://twitter.com/pdalgd/status/1383008275545919488
You can see a full list of changes in that version at https://stat.ethz.ch/R-manual/R-devel/doc/html/NEWS.html. There is only one that looks immediately relevant to {lightgbm}, although it's hard to tell since some of the changes are deep in the internals of R and {lightgbm} may indirectly rely on them.

The default C++ standard has been changed to C++14 where available (which it is on all currently checked platforms): if not (as before) C++11 is used if available otherwise C++ is not supported.

Packages which specify C++11 will still be installed using C++11.

Either specify C++11 (see ‘Writing R Extensions’) or modernize the code and if needed specify C++14

I don't think {lightgbm} needs to worry about this, because it already declares its use of C++11 in the way that is recommended by "Writing R Extensions"

guidelines saying to set CXX_STD in Makevars: https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Using-C_002b_002b-code

Makevars.in: https://github.com/microsoft/LightGBM/blob/7ea2bc4dbca53c03eaae2aa2b22f9b30447caea4/R-package/src/Makevars.in#L1
Makevars.win.in: https://github.com/microsoft/LightGBM/blob/7ea2bc4dbca53c03eaae2aa2b22f9b30447caea4/R-package/src/Makevars.win.in#L1

I don't think that any action is required at this time to prepare for R 4.1.0. But that release will be a big one so I just wanted to note that it's coming so we're prepared.

This project's Windows R-package CI jobs will need to update to a new RTools toolchain, RTools43, once R 4.3 is released.
docs: https://cran.r-project.org/bin/windows/Rtools/rtools43/rtools.html
announcement on the R-pkg-devel mailing list: https://stat.ethz.ch/pipermail/r-package-devel/2023q1/008780.html

Looks like this issue haven't been updated from more than 1.5 year. I guess a lot of things have been changed.
Should we close this issue?
@jameslamb

Many of the things mentioned in this issue have been updated in the last year and a half, but I hadn't started from this issue and so did not remember to link it.
The list is a very useful list of all the places that could be updated and I'd hoped we would get outside contributors helping with this via the good first issue label, but:

you and I are the only people who've linked back to this issue or edited it in the 3.5 years since it was opened
it takes some effort to keep the links and list of items up to date

Despite that.... I vote that we keep it open. I will try to do a better job of linking back to this in version updates, and can spend some time updating the list and links in the issue description.
I also think there are some opportunities to use more automation for managing versions and to centralize version numbers in fewer places.
For example:

@borchero set up dependabot for GitHub Actions versions in #6449
I'm very interested in exploring Renovate, which can generically look at things like PyPI releases and git tags and suggest changes, and where you can centralize those versions in a file

https://docs.renovatebot.com/
example from RAPIDS:

renovate updating a file: https://github.com/rapidsai/ci-imgs/blob/1426d6b13d862c1427711c97d8aa46d702501253/versions.yaml#L10
that file's content being passed through as a docker build arg (just as an example): https://github.com/rapidsai/ci-imgs/blob/1426d6b13d862c1427711c97d8aa46d702501253/ci-conda.Dockerfile#L9

@jameslamb Thanks a lot for your position! Renovate looks interesting! I remember I saw it somewhere in the past but didn't give it a try, unfortunately...

@jameslamb without reading through the entirety of this issue:

SHAs of commits of third-party dependencies

we could also automate this using dependabot just like GH actions :smile:

we could also automate this using dependabot just like GH actions

Oh that would be excellent!
I'd support a PR that does that. At this point I'm very confident in this project's CI to catch issues with new versions of those dependencies, and it would be great to integrate bugfixes and performance improvements more often.

We had one extra spot in pinned issues, so I decided to pin this for now so it'll be more visible from https://github.com/microsoft/LightGBM/issues


Notion for api documentation

content/blog/notion-for-api-documentation/Screenshot (87).png is also not used in the article. Please delete it from the repo

Same with Screenshot (85).png and Screenshot (86).png


silx.gui.plot.tools.profile: Improved image profile tool to support PlotWidget item extension

This PR provides support for more Image item classes than ImageData and ImageRgba.

LGTM


Materialize expression_statement nodes

This change causes the parser to materialize expression_statement nodes for calls and receive expressions that appear as a statement, so that every child of a block is a statement (or comment).
REVIEWERS: why does test --update make a bunch of unnecessary whitespace changes to the corpus/*.txt files? I'm using ./node_modules/tree-sitter-cli/tree-sitter (v0.19.5) for this step. Should I be doing something different?
Checklist:

[ ] All tests pass in CI.
[ ] There are sufficient tests for the new fix/feature.
[ ] Grammar rules have not been renamed unless absolutely necessary.
[ ] The conflicts section hasn't grown too much.
[ ] The parser size hasn't grown too much (check the value of STATE_COUNT in src/parser.c).

every child of a block is a statement

This seems like a good change.

why does test --update make a bunch of unnecessary whitespace changes?

It is reformatting the S-expressions. I'm ok with committing these changes. For now, we'll just need to verify that no ERROR or MISSING nodes have been introduced.

Can you upgrade to the latest Tree-sitter and regenerate with that? Currently, the latest version is 0.20.6.

Could you rebase?

I know this is Alan's PR, but in case it is helpful, I rebased this commit and regenerated with tree-sitter 0.20.8. (Please do double-check my work if you want to use it.)
https://github.com/josharian/tree-sitter-go/commit/309e76588c33af4b9b48ea2b37751be01b21e253
Note that I found that regenerating at master with 0.20.8 made changes as well, so those would be mixed in here.

If you want you can PR that, but remove the comments added, especially the LL one - but otherwise I think it looks good

Sent https://github.com/tree-sitter/tree-sitter-go/pull/124.

Superseded by #124


[SUGGESTION] Path selection should default to currently selected path

If I click on the Path ellipsis to choose a new Path, currently the starting point is my default home user path. But if I already have a current Path selected, it would generally be better to start with that Path (as long as it hasn't been deleted).
For example, I may be downloading all files to an external hard drive, and I'd rather it start there, where I have been downloading to, rather than having to navigate over to that drive every time I select a new path.
This is analogous to using a text editor like Vim/GVim (also on github), where if I do a File / Open, the starting point is the path where I last opened a file.

Great idea added in latest commit. 😄


OC-224 Separate Mobile Properties

To allow multiple identifiers to be associated with a single MobileDeviceFacet or SIMCardFacet, this moves the identifiers to the MobileAccountFacet and creates a property with 0 - n MobileAccountFacets.

This proposal has been withdrawn.


Value formats

How to handle custom formats?

Closing - date/datetime/time formats will be handled and all other formats can be viewed/queried via the metadata subcommand.  Outside of date/datetime/time values the format is not important to the underlying data.


Keep header links on mobile

Done when nav links stack for mobile like so

I think we're on the same page that there just isn't room for including all those links on every page on mobile: Do we really want every one of our pages to look like that screenshot, with the actual page content not coming till an inch from the bottom? Closing.


Feature/add formats to ajv

@mheap PR related to -> https://github.com/mheap/frontmatter-json-schema-action/issues/6
Tested on my fork and works
 "authors": {
      "type": "array",
      "items": {
        "type": "string",
        "format": "email"
      }
    },

Fails
---
.....
id: "b06c309b-0ef1-474b-9f22-a4383028e338"
authors: ["m.hobert@fail"]
...
---

Passes
---
.....
id: "b06c309b-0ef1-474b-9f22-a4383028e338"
authors<EMAIL_ADDRESS>...
---

@Isengo1989 Could you add two tests please? One success and one failure
See https://github.com/mheap/frontmatter-json-schema-action/blob/main/index.test.js#L144-L183 for an example

@mheap the tests are currently failing with 2 errors :thinking:
  ✓ throws when no schema is provided (6 ms)
  ✕ throws when the provided schema is not JSON (8 ms)
  ✕ throws when the provided schema_path is not JSON (2 ms)
  ✓ throws when INPUT_PATHS is not provided (18 ms)
  ✓ throws when there are no matching files (1 ms)
  ✓ add annotations and fails when a document does not validate (6 ms)
  ✓ does not add annotations or fail when all documents are valid (2 ms)

I can add those, but it will fail. Is there an action for execution anyways?

Thx for merging @mheap - noticed that the response in node 18 and 20 differ. So you might want to change it up to two steps or only check on node 20 :thinking:
https://github.com/mheap/frontmatter-json-schema-action/actions/runs/12234657139


Better deployment logs on failure

Turns out we're not reporting all deployment failures or displaying all logs. Here is an example of the same project (with an error) before and after my changes.

Old logs
4:41:24 PM emjpy4: Creating zip package...
4:41:24 PM emjpy4: Starting deployment...
4:41:27 PM emjpy4: Updating submodules.
4:41:27 PM emjpy4: Preparing deployment for commit id '9fd232ff4e'.
4:41:27 PM emjpy4: Repository path is /tmp/zipdeploy/extracted
4:41:27 PM emjpy4: Running oryx build...
4:41:27 PM emjpy4: Command: oryx build /tmp/zipdeploy/extracted -o /home/site/wwwroot --platform python --platform-version 3.7 -p packagedir=.python_packages/lib/site-packages
4:41:30 PM emjpy4: Build orchestrated by Microsoft Oryx, https://github.com/Microsoft/Oryx
4:41:30 PM emjpy4: You can report issues at https://github.com/Microsoft/Oryx/issues
4:41:30 PM emjpy4: Oryx Version      : 0.2.20200114.13, Commit: 204922f30f8e8d41f5241b8c218425ef89106d1d, ReleaseTagName: 20200114.13
4:41:30 PM emjpy4: Build Operation ID: |cQ2TjqzGzBg=.5e3b5af1_
4:41:30 PM emjpy4: Repository Commit : 9fd232ff4eea439593a38a69d5d80798
4:41:31 PM emjpy4: Source directory     : /tmp/zipdeploy/extracted
4:41:31 PM emjpy4: Destination directory: /home/site/wwwroot
4:41:31 PM emjpy4: Python Version: /opt/python/3.7.5/bin/python3
4:41:31 PM emjpy4: Running pip install...
4:41:53 PM emjpy4: Syncing triggers...
4:41:54 PM emjpy4: Querying triggers...
4:42:23 PM emjpy4: HTTP Trigger Urls:
  HttpTrigger1: https://emjpy4.azurewebsites.net/api/HttpTrigger1

New logs
4:27:25 PM emjpy4: Creating zip package...
4:27:25 PM emjpy4: Starting deployment...
4:27:27 PM emjpy4: Updating submodules.
4:27:27 PM emjpy4: Preparing deployment for commit id '0691dd1e15'.
4:27:27 PM emjpy4: Repository path is /tmp/zipdeploy/extracted
4:27:27 PM emjpy4: Running oryx build...
4:27:27 PM emjpy4: Command: oryx build /tmp/zipdeploy/extracted -o /home/site/wwwroot --platform python --platform-version 3.7 -p packagedir=.python_packages/lib/site-packages
4:27:28 PM emjpy4: Build orchestrated by Microsoft Oryx, https://github.com/Microsoft/Oryx
4:27:28 PM emjpy4: You can report issues at https://github.com/Microsoft/Oryx/issues
4:27:28 PM emjpy4: Oryx Version      : 0.2.20200114.13, Commit: 204922f30f8e8d41f5241b8c218425ef89106d1d, ReleaseTagName: 20200114.13
4:27:28 PM emjpy4: Build Operation ID: |/dgAz8lGBUI=.aba2d471_
4:27:28 PM emjpy4: Repository Commit : 0691dd1e15b44f5eae766e2e92da224c
4:27:28 PM emjpy4: Source directory     : /tmp/zipdeploy/extracted
4:27:28 PM emjpy4: Destination directory: /home/site/wwwroot
4:27:28 PM emjpy4: Python Version: /opt/python/3.7.5/bin/python3
4:27:28 PM emjpy4: Running pip install...
4:27:29 PM emjpy4: [23:27:29+0000] Collecting azure-functions
4:27:30 PM emjpy4: [23:27:29+0000]   Using cached https://files.pythonhosted.org/packages/5b/6d/67a219c38be7e4eae7c001a9bf83ab059dcf497644ccc6c5f696ea4155fa/azure_functions-1.2.1-py3-none-any.whl
4:27:30 PM emjpy4: [23:27:29+0000] Cleaning up...
4:27:30 PM emjpy4: Done in 1 sec(s).
4:27:31 PM emjpy4: ERROR: Could not find a version that satisfies the requirement json (from -r requirements.txt (line 2)) (from versions: none)
4:27:31 PM emjpy4: ERROR: No matching distribution found for json (from -r requirements.txt (line 2))
4:27:31 PM emjpy4: WARNING: You are using pip version 19.3.1; however, version 20.1 is available.
4:27:31 PM emjpy4: You should consider upgrading via the 'pip install --upgrade pip' command.
4:27:31 PM emjpy4: ERROR: Could not find a version that satisfies the requirement json (from -r requirements.txt (line 2)) (from versions: none)\nERROR: No matching distribution found for json (from -r requirements.txt (line 2))\nWARNING: You are using pip version 19.3.1; however, version 20.1 is available.\nYou should consider upgrading via the 'pip install --upgrade pip' command.\n/opt/Kudu/Scripts/starter.sh oryx build /tmp/zipdeploy/extracted -o /home/site/wwwroot --platform python --platform-version 3.7 -p packagedir=.python_packages/lib/site-packages
4:27:39 PM emjpy4: Deployment failed.

There were two main problems I fixed:

We weren't checking deployment.status after it completed, meaning we didn't report failures. It's entirely possible the status didn't exist when we first implemented it, but still surprising to me it took this long for the bug to be found 🤷♂
If you call getLogEntryDetails for the same log id multiple times - it will sometimes return more logs. By using the last log time to keep track of what we've already displayed, I can make sure we pick up and display these new logs. This should hopefully result in a lot more logs for long-running commands, so I decided to get rid of our "Waiting for long running command" message. I don't think it was very helpful anyway

Fixes https://github.com/microsoft/vscode-azurefunctions/issues/2071
Fixes https://github.com/microsoft/vscode-azurefunctions/issues/1774
Fixes https://github.com/microsoft/vscode-azureappservice/issues/862

Considering we check the status in here we probably just dun goofed 🙈


Document steps needed to use decorators with vite

I think many use Vite with Solid, but I noticed there aren't any instructions on using classy-solid with Vite. Using the example car class from the readme will cause errors with Vite if it's not configured to use decorators (Support for the experimental syntax 'decorators' isn't currently enabled).
To do so, one can install @babel/plugin-proposal-class-properties, and @babel/plugin-proposal-decorators. Then update their vite.config.ts file to include:
// ...
solidPlugin({
     babel: {
          plugins: [
               ["@babel/plugin-proposal-decorators", { legacy: true }],
               "@babel/plugin-proposal-class-properties",
          ]
     },
}),
// ...

I think it would be beneficial to add this or similar instructions to the readme.

Nice, thanks, may as well copy this to the README

Nice, thanks, may as well copy this to the README


Merchant Id not found

image showing merchant ID not found
but I put exactly as what described on Package Plz help
my code is below
openCCAvenueCheckout({
required String amount,
required String orderId,
String currency = "INR",
// int timeout
}) async {
await CcAvenue.cCAvenueInit(
transUrl: "https://test.ccavenue.com/transaction/initTrans",
//'https://test.ccavenue.com/transaction/transaction.do?command=initiateTransaction',
rsaKeyUrl: 'https://secure.ccavenue.com/transaction/jsp/GetRSA.jsp',
// 'https://test.ccavenue.com/transaction/getRSAKey?access_code=${Config.ccAvenueAccessCode}&order_id=$orderId',
accessCode: Config.ccAvenueAccessCode,
merchantId: Config.ccAvenueMerchantId,
amount: amount.toString(),
orderId: orderId,
currencyType: currency,
redirectUrl: 'http://<IP_ADDRESS>/merchant/ccavResponseHandler.jsp',
cancelUrl: 'http://<IP_ADDRESS>/merchant/ccavResponseHandler.jsp',
);
}

@A7Aima
It's not the issue from Package, You need to check with the CCAvenue team, what went wrong

@A7Aima did you check with the test details mentioned in the readme doc? is it working for you?

No @avinash-gotluru

@A7Aima  can you please check with test details and let me know whether you are facing any issues with it?

@A7Aima  can you please check with test details and let me know whether it's working for you

i also facing same issue any one get solution??
please guide me if any solution you have.


Goalie should walk parallel to backline when the ball is near (before it becomes dangerous)

Currently a goalie stands in the goal and looks at the ball when it approaches said goal.
If the ball is not determined dangerous, the goalie does nothing.
In my opinion he should not move out of the goal but try to block the ball, therefore moving parallel to the backline

See #5. We need a localization for that stuff.

implemented in #104 .


Clear exit timeouts on unmount

It's to prevent the setState call on an unmounted Popover.
My use case was this: I have the popover opened and while it animate to exit, I change page in my app. The popover is unmounted and the setState is still called because of the setTimeout and that's trigger a warning.

@jasonkuhrt Can you review this one? Thanks!

@Kerumen Thanks! Going to take a look soon.

https://github.com/littlebits/react-popover/releases/tag/v0.5.4


Add Letters

T K J Z G I R Q

There's quite a lot going on in this PR. Could you resubmit as smaller ones? Makes it easier to review/assess impact. Then I'll try get them merged quickly. Thanks!


fix(sequencer): move begin_block ibc stuff to end_block

don't review yet!! this is a hack fix.
Summary
maybe fix running a full node - during proposal phase tx execution, we haven't called begin_block before executing the txs, so the state is different. this is not the proper fix, but might fix full nodes on dusk 4. the actual fix is to call the begin_block stuff inside prepare/process_proposal before tx execution.
Changes

move begin_block ibc stuff to end_block

Testing
dusk 4 full node ?

closing b/c this needs to be built off the 0.10.1 release


Merge from develop

merge changes and fix all stuff needed

Ready to merge
https://github.com/mrLuisFer/js-challenges-hub/pull/12


Expand Climate File Domain

Marching orders to expand the climate file domain to CONUS.  Our limiting envelope is the IEMRE domain, so will likely just use its metrics to govern processing.

We are off and running today with this, but since we jumped so far out in space, we really need to better align the "first guess" with IEMRE.  So I am writing a single file quick merge to run today.

This issue is generally "done" with daily reprocessing working to enhance the data quality with more local precipitation data applied.


Implement Hash#except

I do not know if there is an easier way of copying the hash. I cannot use the constructor like new HashValue { *this }, because it expects the new Hash to be of class Hash (and not of a sub class). Is there an easier way to do it?

I'm surprised that new HashValue { env, *this } didn't work, but I don't fully understand what you mean about the class.
Your code essentially does the same thing anyway, so I think this is fine...

I'm surprised that new HashValue { env, *this } didn't work, but I don't fully understand what you mean about the class.
Your code essentially does the same thing anyway, so I think this is fine...

I think when using new HashValue { env, *this } Value will be initialized using the current hash value with it's class type. I'm talking specifically about the spec spec/core/hash/except_spec.rb:23. Basically Hash#except must always return a class of type hash (not a subclass or anything like that).


Render to framebuffer Target, then blit to swapchain

Render to framebuffer Target, then blit to swapchain
Fixed depth for Texture, should be 1
Mailbox, Immediate present mode issues fixed
Fixed frame stuttering on excessive cycle flushing

Oh, I forgot this also includes some changes to the way buffers are initially sized. Exactly sized buffers are created upon first data upload and then next power of two is used. I can remove this logic if it's too much for this PR, though.

I think that all makes sense! Thanks! :)


Don't download this, its a virus

It got flagged as Win64:Evo-gen [Trj], Trojan.Agent.Script.1762566, and Trojan.Win32.Save.a by 4 out of 5 antiviruses, don't use this.

Bro never used GitHub
You can look at the whole code
You can even build it yourself with pyinstaller
I just made an exe because people struggled to run the python script
Also I don't know where you got this stats because you're one of the first to say that
It's amazing how someone on GitHub, an open source platform, don't know that you can check yourself
It's not even a big project, it's one python file with about a thousand lines so you can quickly check yourself
I realize to build the exe you would need the app.spec script which I can provide and you'll see you can get the exact same file
Really, people like you makes me mad

So idk what antivirus you have or where you checked it
Also another way to check is testing with tria.ge in case you haven't heard of it

Ok I was going to check on virustotao because I thought this could show that it's not a virus, but it's from where you got the results
Most was from random antivirus but still there was an Avast detection
Which is weird because it's not even that complex of an app so idk what got detected
And as I also usually use virus total, I understand
I'm sorry if I delt angry as your concern seem genuine
Though it doesn't excuse the things I said above to check

Inactive


Feature request - Windows version

Hi there,
I really appreciate the work you’ve done on Fetcharr! It’s exactly what I need, but I don’t use Docker, and I know many others who also don’t have Docker set up on their systems.
Would it be possible to create a version of Fetcharr that runs natively on Windows without needing Docker? It would be incredibly helpful and open up this tool to a wider audience who aren’t using Docker.
Thanks for considering this! I look forward to hearing your thoughts.

Hello.
While I don't particularly have the time right now to set up a workflow for building Windows versions, it should be straight forward to do manually:
./nuke Compile should take you most of the way there, creating a bin/x64/ folder with the built application. It would still require the .NET SDK, but I hope that's fine until I get around making an automated workflow for it.


Constant Autolinking

Is your feature request related to a problem? Please describe.
no problem, just greedy systems guy 🤩 this plugin is already amazing
Describe the solution you'd like
I would love to have an auto-link feature, which links keywords as I type along, same functionality, and different trigger, (without asking permission in popup)
Describe alternatives you've considered
🍪
Additional context
auto connecting automatically comes closest to an ACTUAL second brain. one that makes connections for you
I'm really excited about this idea

My idea on how to implement this
MVP

Adapt the function so it scans only current note for links https://github.com/AlexW00/obsidian-note-linker/issues/37
This would probably be very fast. So we could run it very often.

Trigger:

Manually (using a shortcut)
Schedule: Automatically trigger the function every X seconds / minutes on the current note.

Done 🎉

MVP Issues:
This approach will probably work fine and it looks easy to implement.
But if I have a word that I don't want to link, it will keep spanning it over and over.
To solve this:

Increase the schedule period. (does not solve, but minimizes the issue)
Maybe it should "remember" to not link that again. But that requires some persistent memory and would drastically change the architecture of the project.

Another idea
To solve the MVP issues, we must scan only the latest changes on the current file.

Adapt the function so it scans only a substring of the file.
For example, just one line.
Trigger:

At every new line break? (hitting enter)
At every new word?

Potential issues:

Complexity to adapt the scan functions (that would probably require more adjustments than the #37 MVP approach)
Will it work for copy-paste? / Imported files?

Conclusion:
I'd say we start with the MVP, implementing the #37 feature. Triggering with a shortcut.
And then it's very simple to setup a scheduler to make it automatic.


Ability to sort the results

Using the extension on generic domains like github.com show all the posts related to github.com sorted by popularity(i think). Is it possible to allow for an option to sort by time?
The algolia api provides this facility and can be used for this.

Yes, it's sorted by popularity. When there are many results (more than 4 actually) you also get a link ("See all N stories on Algolia"). With it you can go to the HN Algolia website and refine the search further.
I don't think I'll build any other features. It's a quick tool for discovering HN thread about specific pages (in spite of that search is not strict on the URL submitted), but it is not intended to be a full Algolia search replacement.
Thanks.


Install issues

Using umbraco 7.5.3 and articulate 2.0.5.  After installing the package i get error Could not load type 'Articulate.Controls.Installer'. ---> System.Web.HttpException
When i try to view doc type articulate i get error with articulate themepicker datatype clicking on that gives error. Looks like some of the default stuff it needs is missing

Have you tried, uninstalling or removing articulate files and re-installing? or installing on a new vanilla 7.5.3 (or better yet 7.5.6) ?

I turned on debug in web.config then installed and it worked.


New Scrollbar and minor bug fix

fixes issue:
#19
Hi @Abhirup-02, I have made the changes to the scrollbar as you suggested. I set the width to 11px and added a border-radius of 10px. Additionally, when I attempted to run the development server, it displayed an error message stating 'react-scripts' was not recognized. To resolve this, I installed 'react-scripts' using the command "npm install react-scripts --save".
demo video:
https://www.loom.com/share/a18bd7a8063a47b0a14eec4f5f114718

I like this new scrollbar. package-lock was updated  that's why it showed that error I think.

I like this new scrollbar. package-lock was updated that's why it showed that error I think.

I have made a new pull request that does not have any conflicts.


Change migration sql on needsReview default bug

Migration sql was not correctly converting the needsReview
flag from boolean to integer as expected

Why exactly do we need to convert from boolean to int?

So that we can have a way to "lock" the setting so a user cannot opt out of being a reviewer if the admin sets it.


Change unsafe prod script approval config

Looks like srv_typ from login moca results is not a full-proof way to tell if env is production

This has been implemented and will be part of v1.3.17


Update msbuild discovery for 2017

This also adds a find_vs_version function to share with
the cmake crate.
Fixes #162
Lightly tested.

👍


[3.x] Batch rename window size not updating correctly

Godot version
3.4 5ce734c073
System information
Linux
Issue description
When in batch rename window preview text doesn't fit in the window, the window background doesn't scale properly.
Moving the window updates it.
Same thing on 3.3.3, but on master it's fine (because it's a separate window there?).

Steps to reproduce
Open batch rename window.
Make so the preview text is so long that it doesn't fit.
Minimal reproduction project
No response

I was trying to fix this by making changes in editor/rename_dialog.cpp
But just turning on autowrap on the preview label was not enough as we also have to increase the height of the VBoxContainer, else, instead of overflowing from the right, it overflows from below.

Is there a way to do so? I was expecting to find some sort of update function to call inside the _update_preview function, but so far no luck.

the height is adjusted when the advanced options are toggled, but that too gives weird results.

We could also just clip off the overflow, but that would not show the complete preview to the user (which I guess is not ideal?)

We could also just clip off the overflow, but that would not show the complete preview to the user (which I guess is not ideal?)

In the master branch, there are various ellipsis overflow modes available in Label.