[Feature request] Detach package dependencies for app.xxx.js

Feature request
Description
I found that a vuepress2 project with a relatively large structure, for example, contains a number of custom components. After executing build, all related codes will be bundled in dist/assets/app.xxx.js, resulting in the large size of a single js file  and prolonged white screen of the site.

Whether vite or webpack, the code of all custom components is in the same javascript file.
For vite, it even packages vue-router and nprogress into app.xxx.js.

Is the packaging behavior able to be controlled by vuepress2? Is it possible to split them into different small files ?
功能需求
描述
我发现，一个结构较为庞大的 vuepress2 项目，例如含有较多数量的自定义组件，经过 build 之后，会把所有相关的代码都放在 dist/assets/app.xxx.js，导致单个 js 文件太大，从而导致打开站点的白屏时间较长。

不论是 vite 还是 webpack，所有自定义组件的代码都在同一个js文件中。
对于 vite，甚至还会把 vue-router、NProgress 也放在 app.xxx.js。

这部分打包的行为能否由 vuepress2 控制？能否能够将他们拆分为不同的小文件？

Components

You should try importing your components directly in markdown files if you want them to async loaded with that page.
Registerting them globally is expected to result them being bundled in entry files.

Entry packages

Any packages invoke or imported in appSetup stage is expected to appear in entry file, because they should be loaded when initilizing and seting up the VuePress App. so bundling vue-router NProgress and so on should be the expected behavior.
If you found packages with really big size imported, you may need to contact plugin developer to see if they can load it async (probably using dynamic import), to split those big packages as chunks, and load them async.
So currenly there are not much VuePress team can do. (Alos NProgress is not big in size, so I don't think there are actually benifit spiliting it in to a sperate chunk)

Maybe we should add some reminder in documation here.

And if you are taling about spilting "common official packages" such as  vue, vue-router, @vuepress/client, @vuepress/shared packages in to a sperate chunk, so that they won't be upgraded when reploying docs so that users don't need to refetch them, that should be another thing, you can open a PR or issue for that, and I agree with that.
@meteorlxy Does this sound ok to you? (Also, does vite support that? I am not pretty much sure)

Components

You should try importing your components directly in markdown files if you want them to async loaded with that page.
Registerting them globally is expected to result them being bundled in entry files.

Entry packages

Any packages invoke or imported in appSetup stage is expected to appear in entry file, because they should be loaded when initilizing and seting up the VuePress App. so bundling vue-router NProgress and so on should be the expected behavior.
If you found packages with really big size imported, you may need to contact plugin developer to see if they can load it async (probably using dynamic import), to split those big packages as chunks, and load them async.
So currently there are not much VuePress team can do. (Alos NProgress is not big in size, so I don't think there are actually benifit spiliting it in to a sperate chunk resulting an extra web request)

Thanks a lot, I had a look at documentation again, found that plugin @vuepress/register-components is a good choice rather than registering components manually in clientAppEnhance.ts . The custom components are indeed detached from app.xxx.js into different js files now.


Log kernel point evaluation for weighted ChebyshevU

Implementation of (real) point evaluation of the log kernel applied to weighted ChebyshevU polynomials. Currently only works for reals, I am not quite sure why the complex case does not work. It does not enter the * function (as if const LogKernelPoint was not implemented at all).

Code cov misses are due to macros, so fine


Some ideas for TagUI development

Placeholder issue on some ideas of what's next for TagUI -

General - helpers, ocr, visual, sql, remove technical blocks, apache 2, etc..
Reusability - integrations with begin/finish, compounding with sub-scripts
Extensibility - custom global / local functions, custom global / local repository
Business - roro / ahk integration, excel, access, control, dashboard, reporting
Developers - packages for other programming languages, eg python and r
Holy Grail - ai-enabled recorder that learns workflows by watching videos
Eco-infra - convergence of various rpa tools into a single deployment
Dependencies - update casperjs v1.1.4-1, sikuli v1.1.2, slimerjs v1.0

Support of begin and finish keyword for integrations is implemented with https://github.com/kelaberetiv/TagUI/issues/82. It makes calling Python, R, JS, Sikuli, CLIs easier, especially if there is a large code block to be run and developer prefers to put that code as part of TagUI script and not as a separate file for the respective platform.

Support for calling other TagUI scripts within a script is implemented with #80 (more details there). With that commit, users can create reusable TagUI scripts that can be called from other scripts. Scripts can be compounded to do something much more complicated, while keeping flow readable and reusable.

Great, thanks very much Ken for the great support and prompt updates.
I will give this a try and get back to you.
BR,
Terry

Trying out a new Chrome extension improvement. A window popups immediately once user clicks on the note down element menu. This can help make it easier to check elements and write automation flows.

to try this version on Chrome, go to the address chrome://extensions/
download and unzip chrome.zip, then drag chrome folder into webpage
disable old v3.1 extension, while recording right-click to note down element

A new ask step is added to allow interactive input from user. If run in default invisible or headless mode, the prompt will be shown in the shell window. If run in chrome mode, it will be a popup box.
The parameter for ask step is the question / prompt / instruction you have for the user. This feature is now usable from the cutting edge version. More details in the issue - https://github.com/kelaberetiv/TagUI/issues/127

Adding provision for double-click and right-click actions as part of #78
(works in visible and invisible Chrome, and visual recognition automation)

Added support for user-defined global custom functions that persist with each TagUI releases.
This feature is now usable from the cutting edge version. For more details, see issue https://github.com/kelaberetiv/TagUI/issues/137

Added support for a global repository file tagui_global.csv (place in tagui/src folder) that will make definitions available to all automation flows. This user-created file will persist with new versions of TagUI as this file is not included as part of the repository.
When there is the same definitions, flow-specific repository definitions take precedence over the global definitions. This global repo file works with a flow has datatable. More details at issue https://github.com/kelaberetiv/TagUI/issues/139

Added support for a local repository file tagui_local.csv that will make definitions available to automation flows in the same folder as the tagui_local.csv. This user-created file will persist with new versions of TagUI as this file is not included as part of the repository.
When there is the same definitions, flow-specific repository definitions take precedence over the local definitions and then over the global definitions. This local repo file works with a flow has datatable. More details at issue https://github.com/kelaberetiv/TagUI/issues/139
This feature is now usable from the cutting edge version.

Added support for local functions file tagui_local.js that make user-defined functions available to automation flows in the same folder as the tagui_local.js. This user-created file will persist with new versions of TagUI as this file is not included as part of the repository.
Flow-specific functions take precedence over the local functions and then over the global functions. More details at issue #137. This feature is now usable from the cutting edge version.

Implemented a big codebase change that fundamentally affects all TagUI steps. The change allows deterministic flow of execution for some niche scenarios so that the order of actions, including steps that does not involve interacting with elements (such as echo, js step), and complex use of nested for, if, else, else if, can be done in the exactly the same order synchronous versus asynchronously. That is important as RPA and process automation micro-steps almost always need to be in sequence.
This change is now usable from cutting edge version. Details of change - #150
Breaks in backward compatibility in exchange for deterministic automation execution

var now strictly not supported for variables definition to be in scope. previously for some steps  (eg echo, api), var variables will still be in scope
frame and popup after one another requires { and } steps. in general conditions (for, if else, else if, while) and popup / frame need { and } if used consecutively, in order for scope to be defined
random use of { and } blocks without purpose no longer works. for example, when { and } steps are not used with if, else, else if, for, while popup, frame

On a suggestion I heard recently - to run automation without restarting Chrome and closing user's browser tabs. This feature has been implemented and now usable from cutting edge release, which can be downloaded here to overwrite existing packaged installation. (do backup beforehand)
How it works is by creating a separate Chrome user profile for TagUI's use, so that profile is launched whenever TagUI automation is run. This way, existing Chrome browser tabs used by the user will not be closed and affect their work. More details at this issue.
Credentials (signed-in passwords and so on), will have to be re-entered as the browser will start off on a clean slate during the first run. Eg can use wait 30 seconds or live step to pause the automation to login.

A few new features implemented into cutting edge release since above post.
See below and respective issues for more details -

csv helper function csv_row() for easy handling of writing to csv files - https://github.com/kelaberetiv/TagUI/issues/184
extending present() and visible() to visual recognition using sikuli - https://github.com/kelaberetiv/TagUI/issues/202
running complex statements for python and vision integration - https://github.com/kelaberetiv/TagUI/issues/167
some more csv improvements in progress (see for more details) - https://github.com/kelaberetiv/TagUI/issues/175

Thanks @lohvht and @Aussiroth !

Scrapped encrypting and auditing features, simply out-of-scope and controlled from OS level - more details here - https://github.com/kelaberetiv/TagUI/issues/217

Also, I am scrapping efforts on developing enterprise features such as a dashboard for centralized deployment, and a reporting interface for gathering execution details to be viewed centrally.
Commercial RPA software does this very well and I believe the niche for TagUI is in personal desktop automation in a distributed way. Use cases where benefit individual users but not creating that much financial value that the company want to dedicate 1 commercial RPA user license to the laptop.
Efforts on creating these enterprise features should rather be reserved to features such as making it easier for users to create script (eg the Italian guy's sample of auto-filling up the steps), or more pressing stuff such as integration with Windows desktop applications.

Closing this issue for now,
As outstanding items on desktop apps is tracked by https://github.com/kelaberetiv/TagUI/issues/113 and ide helper is tracked via https://github.com/kelaberetiv/TagUI/issues/188.
Hardware robotics integrations and video computer vision automation  can be raised later.

I'm only looking at 3 items in pipeline for TagUI before hitting maintenance mode.

integrating with desktop apps -  https://github.com/kelaberetiv/TagUI/issues/113
assistant for writing scripts - https://github.com/kelaberetiv/TagUI/issues/188
for loop break and continue - https://github.com/kelaberetiv/TagUI/issues/216

May reach out to other open-source RPA software maintainers to look at collaboration. Was thinking yesterday if can make a great open-source RPA tool and pass on to Microsoft or another large tech company to maintain, can put pressure on commercial RPA tools to raise the quality and ease-of-use of their free versions. That should lead to the largest impact on the RPA ecosystem.

I'm only looking at 3 items in pipeline for TagUI before hitting maintenance mode.

integrating with desktop apps -  https://github.com/kelaberetiv/TagUI/issues/113
assistant for writing scripts - https://github.com/kelaberetiv/TagUI/issues/188
for loop break and continue - https://github.com/kelaberetiv/TagUI/issues/216

May reach out to other open-source RPA software maintainers to look at collaboration. Was thinking yesterday if can make a great open-source RPA tool and pass on to @microsoft or another large tech company to maintain, can put pressure on commercial RPA tools to raise the quality and ease-of-use of their free versions. That should lead to the largest impact on the RPA ecosystem.


[9.x] allow to chain jobs when condition is true

This PR adds a new when-like method, which allows to chain an array of jobs when a condition is true.
For example:
JobChainingTestFirstJob::dispatch()->chainWhen(false, [
            new JobChainingTestSecondJob // won't be chained because the condition is false
        ])
        ->chainWhen(true, [
            new JobChainingTestThirdJob // will be chained because the condition is true
        ]);

Of course, it is possible to chain a default array of jobs, if the condition is false and if the third parameter is not null.
JobChainingTestFirstJob::dispatch()->chainWhen(false, [
            new JobChainingTestSecondJob // Won't be chained because the condition is false
        ], [
            new JobChainingTestThirdJob // Will be chained because the condition is false
        ]);

If this PR is OK, I will add some other stuff like chainUnless (in another PR or in this one ? As you wish), and I will write the Laravel documentation.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


Textobject's behaviour if not in hunk

Description
I used map({'o', 'x'}, 'ih', ':<C-U>Gitsigns select_hunk<CR>') which from readme to create textobject. It's useful but when we not in a hunk and then press cih, we will enter insert mode, it's a different behaviour from built-in textobject, which don't enter insert mode.(try ci" in a line with "quotes)
Neovim version
Nightly
Operating system and version
Arch Linux
Expected behavior
Do nothing, like the built-in textobject
Actual behavior
Enter insert mode
Minimal config
vim.o.packpath = '/tmp/nvim/site'

local plugins = {
  gitsigns = 'https://github.com/lewis6991/gitsigns.nvim',
  -- ADD OTHER PLUGINS _NECESSARY_ TO REPRODUCE THE ISSUE
}

for name, url in pairs(plugins) do
  local install_path = '/tmp/nvim/site/pack/test/start/'..name
  if vim.fn.isdirectory(install_path) == 0 then
    vim.fn.system { 'git', 'clone', '--depth=1', url, install_path }
  end
end

require('gitsigns').setup{
  debug_mode = true, -- You must add this to enable debug messages
  -- ADD GITSIGNS CONFIG THAT IS _NECESSARY_ FOR REPRODUCING THE ISSUE
}

-- ADD INIT.LUA SETTINGS THAT IS _NECESSARY_ FOR REPRODUCING THE ISSUE
vim.keymap.set({'o', 'x'}, 'ih', ':<C-U>Gitsigns select_hunk<CR>')

Steps to reproduce

nvim --clean -u minimal.lua
press cih outside a hunk

Gitsigns debug messages
None

I'm not sure if this can be considered a bug.

ciw, cw puts you in insert mode on blank lines
cip puts you in insert mode on blank lines
cis puts you in insert mode on blank lines
ci' does just looks for the last and next ' even if the cursor is not in a quoted string.


"Validate lab environment": clarification where to begin

Learners were often confused with the note on top stating to skip steps 1-3 if they had a subscription. I hope this makes it clearer.
Checklist
Mark completed with "x" between brackets, "[x]", or checking the box once the PR is created:

[ ] Has related GitHub Issue 💥 Create Issue 📝
[X] Tested it
[X] Read the PR collaboration guide 👓 Collaboration Guide 📝

Changes proposed in this pull request:

Removed note on top
Added one section for "Don't have subscription yet" and one for "Have a subscription"

I liked it. What you think @fimdim @petender? We may approve it on Friday.


Improve error handling in base.py

The parsing logic using UserWarning in base.py could probably be improved (we should fail more explicitly).

This is completed, no ?

yes it is!


[Tooltip] Improve legibility

...and increase font weight on desktop to improve readability
The specs only tell us about the background color and opacity (instead of setting the opacity of the whole element).
Increasing the font weight a bit improves the readability of a 10px font on normal desktop displays (i.e. no high-dpi ones). It's an opinionated change.

Before:

After:

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

Argos showcases the improved legibility: https://www.argos-ci.com/mui-org/material-ui/builds/43021. Very nice :+1:

I like the improved readability, but would it be possible to base the background color on a theme variable so that it still is easily customized? I use slightly tinted grey colors in my theme.

I like the improved readability, but would it be possible to base the background color on a theme variable so that it still is easily customized? I use slightly tinted grey colors in my theme.

@lucaas  You can do that by overriding the used color when creating your own theme.
Please open a separate issue if this doesn't help. This change doesn't affect the customizability of the Tooltip.

I missed commit a7a08ad which addressed my concern, so you can disregard from my comment.


keydb-server SIGSEGV with tcmalloc

I cannot start keydb-server compiled with tcmalloc from google-perftools-2.6.2 installed in Gentoo linux. Following gdb stack trace continues infinitely. The same problem happens in both v5.1.1 and current unstable branch.
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7b61601 in InitModule () at src/malloc_extension.cc:212
212     src/malloc_extension.cc: No such file or directory.
(gdb) bt full
#0  0x00007ffff7b61601 in InitModule () at src/malloc_extension.cc:212
No locals.
#1  0x00007ffff7b61d89 in InitModule () at src/malloc_extension.cc:221
No locals.
#2  MallocExtension::instance () at src/malloc_extension.cc:221
No locals.
#3  0x00007ffff7b6d42a in tc_malloc_size (ptr=0x555555f588e8) at src/tcmalloc.cc:2181
No locals.
#4  0x0000555555598997 in zmalloc (size=size@entry=8, mclass=mclass@entry=MALLOC_LOCAL) at zmalloc.cpp:116
        _n = <optimized out>
        ptr = 0x555555f588e8
#5  0x000055555562c807 in operator new (size=size@entry=8) at new.cpp:16
No locals.
#6  0x00007ffff7b61606 in InitModule () at src/malloc_extension.cc:212
No locals.
#7  0x00007ffff7b61d89 in InitModule () at src/malloc_extension.cc:221
No locals.
#8  MallocExtension::instance () at src/malloc_extension.cc:221
No locals.
#9  0x00007ffff7b6d42a in tc_malloc_size (ptr=0x555555f588e0) at src/tcmalloc.cc:2181
No locals.
#10 0x0000555555598997 in zmalloc (size=size@entry=8, mclass=mclass@entry=MALLOC_LOCAL) at zmalloc.cpp:116
        _n = <optimized out>
        ptr = 0x555555f588e0
#11 0x000055555562c807 in operator new (size=size@entry=8) at new.cpp:16
No locals.
#12 0x00007ffff7b61606 in InitModule () at src/malloc_extension.cc:212
No locals.
#13 0x00007ffff7b61d89 in InitModule () at src/malloc_extension.cc:221
No locals.
#14 MallocExtension::instance () at src/malloc_extension.cc:221
No locals.
#15 0x00007ffff7b6d42a in tc_malloc_size (ptr=0x555555f588d8) at src/tcmalloc.cc:2181
No locals.
#16 0x0000555555598997 in zmalloc (size=size@entry=8, mclass=mclass@entry=MALLOC_LOCAL) at zmalloc.cpp:116
        _n = <optimized out>
        ptr = 0x555555f588d8

Log Files
It does not create any log file.
To Reproduce
On Gentoo:

install google-perftools-2.6.2
compile keydb with tcmalloc
run keydb-server

Issue with how we've overloaded new/delete for zmalloc().

Oh, I see. It actually means that tcmalloc is currently unsupported, right? What was the reason to override new and delete globally? Do you plan to migrate zmalloc calls to a new operator?

Hi @arkamar
This was an unintentional break, I do want to support tcmalloc.
As for why new/delete is overriden KeyDB is migrating to C++ and while you can pass in custom allocators to STL containers it’s not exactly pretty. If we don’t use the zmalloc framework then the allocations won’t be tracked for things like enforcing maxmemory.

Based on https://github.com/gperftools/gperftools/issues/130 This is actually supported, although it looks like not very well as Initialize is not reentrant.  I think a proper fix is in tcmalloc itself possibly, but I'll see if there's a workaround.

Quick update: tcmalloc agrees there’s an issue here. I need to get them a PR to resolve the issue.

I cannot start keydb-server compiled with tcmalloc from google-perftools-2.6.2 installed in Gentoo linux. Following gdb stack trace continues infinitely. The same problem happens in both v5.1.1 and current unstable branch.
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7b61601 in InitModule () at src/malloc_extension.cc:212
212     src/malloc_extension.cc: No such file or directory.
(gdb) bt full
#0  0x00007ffff7b61601 in InitModule () at src/malloc_extension.cc:212
No locals.
#1  0x00007ffff7b61d89 in InitModule () at src/malloc_extension.cc:221
No locals.
#2  MallocExtension::instance () at src/malloc_extension.cc:221
No locals.
#3  0x00007ffff7b6d42a in tc_malloc_size (ptr=0x555555f588e8) at src/tcmalloc.cc:2181
No locals.
#4  0x0000555555598997 in zmalloc (size=size@entry=8, mclass=mclass@entry=MALLOC_LOCAL) at zmalloc.cpp:116
        _n = <optimized out>
        ptr = 0x555555f588e8
#5  0x000055555562c807 in operator new (size=size@entry=8) at new.cpp:16
No locals.
#6  0x00007ffff7b61606 in InitModule () at src/malloc_extension.cc:212
No locals.
#7  0x00007ffff7b61d89 in InitModule () at src/malloc_extension.cc:221
No locals.
#8  MallocExtension::instance () at src/malloc_extension.cc:221
No locals.
#9  0x00007ffff7b6d42a in tc_malloc_size (ptr=0x555555f588e0) at src/tcmalloc.cc:2181
No locals.
#10 0x0000555555598997 in zmalloc (size=size@entry=8, mclass=mclass@entry=MALLOC_LOCAL) at zmalloc.cpp:116
        _n = <optimized out>
        ptr = 0x555555f588e0
#11 0x000055555562c807 in operator new (size=size@entry=8) at new.cpp:16
No locals.
#12 0x00007ffff7b61606 in InitModule () at src/malloc_extension.cc:212
No locals.
#13 0x00007ffff7b61d89 in InitModule () at src/malloc_extension.cc:221
No locals.
#14 MallocExtension::instance () at src/malloc_extension.cc:221
No locals.
#15 0x00007ffff7b6d42a in tc_malloc_size (ptr=0x555555f588d8) at src/tcmalloc.cc:2181
No locals.
#16 0x0000555555598997 in zmalloc (size=size@entry=8, mclass=mclass@entry=MALLOC_LOCAL) at zmalloc.cpp:116
        _n = <optimized out>
        ptr = 0x555555f588d8

Log Files
It does not create any log file.
To Reproduce
On Gentoo:

install google-perftools-2.6.2
compile keydb with tcmalloc
run keydb-server

do you have a ebuild you can share?

I cannot start keydb-server compiled with tcmalloc from google-perftools-2.6.2 installed in Gentoo linux. Following gdb stack trace continues infinitely. The same problem happens in both v5.1.1 and current unstable branch.
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7b61601 in InitModule () at src/malloc_extension.cc:212
212     src/malloc_extension.cc: No such file or directory.
(gdb) bt full
#0  0x00007ffff7b61601 in InitModule () at src/malloc_extension.cc:212
No locals.
#1  0x00007ffff7b61d89 in InitModule () at src/malloc_extension.cc:221
No locals.
#2  MallocExtension::instance () at src/malloc_extension.cc:221
No locals.
#3  0x00007ffff7b6d42a in tc_malloc_size (ptr=0x555555f588e8) at src/tcmalloc.cc:2181
No locals.
#4  0x0000555555598997 in zmalloc (size=size@entry=8, mclass=mclass@entry=MALLOC_LOCAL) at zmalloc.cpp:116
        _n = <optimized out>
        ptr = 0x555555f588e8
#5  0x000055555562c807 in operator new (size=size@entry=8) at new.cpp:16
No locals.
#6  0x00007ffff7b61606 in InitModule () at src/malloc_extension.cc:212
No locals.
#7  0x00007ffff7b61d89 in InitModule () at src/malloc_extension.cc:221
No locals.
#8  MallocExtension::instance () at src/malloc_extension.cc:221
No locals.
#9  0x00007ffff7b6d42a in tc_malloc_size (ptr=0x555555f588e0) at src/tcmalloc.cc:2181
No locals.
#10 0x0000555555598997 in zmalloc (size=size@entry=8, mclass=mclass@entry=MALLOC_LOCAL) at zmalloc.cpp:116
        _n = <optimized out>
        ptr = 0x555555f588e0
#11 0x000055555562c807 in operator new (size=size@entry=8) at new.cpp:16
No locals.
#12 0x00007ffff7b61606 in InitModule () at src/malloc_extension.cc:212
No locals.
#13 0x00007ffff7b61d89 in InitModule () at src/malloc_extension.cc:221
No locals.
#14 MallocExtension::instance () at src/malloc_extension.cc:221
No locals.
#15 0x00007ffff7b6d42a in tc_malloc_size (ptr=0x555555f588d8) at src/tcmalloc.cc:2181
No locals.
#16 0x0000555555598997 in zmalloc (size=size@entry=8, mclass=mclass@entry=MALLOC_LOCAL) at zmalloc.cpp:116
        _n = <optimized out>
        ptr = 0x555555f588d8

Log Files
It does not create any log file.
To Reproduce
On Gentoo:

install google-perftools-2.6.2
compile keydb with tcmalloc
run keydb-server

@arkamar do you have a gentoo ebuild for keydb by any chance ?

@bhakimi, sorry, I wanted to do it last time you wrote but it slipped out of my head. Anyway, I just cut the keydb ebuild from our internal overlay https://github.com/Excello-cz/keydb-overlay. I hope you find it useful.

Thanks !!
On Sun, Jul 5, 2020 at 12:53 PM Petr Vaněk<EMAIL_ADDRESS>wrote:

@bhakimi https://github.com/bhakimi, sorry, I wanted to do it last time
you wrote but it slipped out of my head. Anyway, I just cut the keydb
ebuild from our internal overlay
https://github.com/Excello-cz/keydb-overlay. I hope you find it useful.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JohnSully/KeyDB/issues/122#issuecomment-653931475,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2BO3KGLMWWODD4G6JCGL3R2DK2BANCNFSM4J3YM2EQ
.

Updating to google-perftools-2.7 (which looks to be stable on Gentoo) seems to fix the SIGSEGV so I'm closing this issue.


rna-transcription: Changes return type to Maybe

Error case is now defined, eliminating the desire to throw an error
for invalid input.
The test and example solution are more idiomatic to Haskell, using a
Maybe.

Closes #166

Great! Thanks! :+1:
I'm going to merge it!
Just one thing. It's always good to take a look at exercism/x-common to see if there is a .json file for the exercise. Usually those files have a good list of test cases we should implement, this way we don't have to duplicate work thinking about that.

Do you know why CI didn't run for this PR? Also, thanks for the link. I can amend the commit with the other test cases before you merge.

Trying to find out what's happening with Travis. I'll hold this PR until the problem is solved

I wrote a new PR #169 , just to test it. Same problem!

Looks like it's working again. I've also updated the test cases.

Perfect! :smile:


Font not being loaded when launching from i3

When I launch st from an i3 binding, it doesn't use the proper font. When I run an identical command (st -f "Liberation Mono") from zsh, the font is properly selected.
Other arguments that I pass to the -f flag in i3 work as expected. For instance, I am able to change the font launching from the i3 binding. So far the only thing that I noticed not to work is the font selection itself.
Here is the pertinent line in my i3 config file ~/.config/i3/config:
bindsym $mod+Return exec --no-startup-id st -f "Liberation Mono"

Why not change the font config in config.def.h and recompile?

Hi fikovnik, thanks for the reply.
I have tried changing config.h and the behavior is the same wether I pass the font via argument or compile it by changing the config.h.
That is, the font is properly loaded launching from shell but not launching via i3 keybind.
I have no clue what can be causing this.

I have now noticed that the problem also occurs when launching st from dmenu.

Yet another weird thing I found.
To try and go around the issue, I have installed sxhkd and configured a shortcut to launch st.
If I run sxhkd from a terminal, the shortcut works as intended (with the proper font).
It also works if I do so by launching it into the background (with sxhkd &).
Howerver, if I add sxhkd & to my .xprofile, the shortcut will launch st with the wrong font.

Ok, it is definately a lightdm issue. I have just disabled lightdm and launched X via startx, no problem whatsoever.
I guess the answer is, ditch lightdm....


Fix windows issue with multiple file patterns in the file dialog

Try to fix this issue. https://github.com/godotengine/godot/pull/81781

Bugsquad edit, fixes: https://github.com/godotengine/godot/pull/81781

For reviewers, see:

https://github.com/godotengine/godot/pull/81218
https://github.com/godotengine/godot/pull/81782

Please use git pull --rebase to update your branch in the future, if keeps your history clean, see here.

Please follow the above instructions, do not use this method but the linked method

@JerryLi-lab if you need help to update your branch in the instructed way please say so

Thank you. I will try it.

You have also included a different fix unrelated to this, you need to put it on a separate branch, this is why it is better to use a dedicated branch for a PR and not master

You have also included a different fix unrelated to this, you need to put it on a separate branch, this is why it is better to use a dedicated branch for a PR and not master

I got it. I want to fix another issue. Should I clone a new brunch?

Yes, using git branch

I have submitted something, please tell me how to delete it

Though it might be easier if you close this PR, restore your branch using git reset --hard upstream/master and recreate your changes manually, on a new branch

You've added yourself as the author of unrelated commits

Did you follow the specific instructions? Using git rebase -i?
I'd say it'd be easier to start fresh

I'd suggest using git reset --hard upstream/master and adding your fix manually, as it's so short

Did you follow the specific instructions? Using git rebase -i?
I'd say it'd be easier to start fresh

Yes. Could I delete this fork to remove them. and adding my fix manually

No not your fork, just follow the instruction with git reset --hard upstream/master

Do you have a remote registered? With git remote add upstream https://github.com/godotengine/godot.git

Thank you. It works. Please tell me what should I do next?

Add your changes back, make a single commit, and use git push --force

Add your changes back, make a single commit, and use git push --force

Thank you for your patient teaching. Should I use a new branch to modify another issue? Delete this branch after merging?

Yes, make sure your other branch doesn't include this one though, base it off upstream/master

Yes, make sure your other branch doesn't include this one though, base it off upstream/master
Once merged, or not, reset this branch the same way again

I now want to submit the code for another issue. Can I use a new branch? Will it affect here?

Create a new branch it won't affect this


fix: dev install

this was breaking the jupyter labextension develop step

lint commit closes: https://github.com/jupyterlab-contrib/jupyterlab-vim/issues/98


OLS-538: Check final token count before reaching LLM

Description
Check final token count before reaching LLM
That should avoid "Internal server error"
Type of change

[ ] Refactor
[ ] New feature
[x] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library

Related Tickets & Documents

Related Issue #OLS-538
Closes #

Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] PR has passed all pre-merge test jobs.
[ ] If it is a core feature, I have added thorough tests.

Testing

Please provide detailed steps to perform tests related to this code change.
How were the fix/results from this change verified? Please provide relevant screenshots or results.

/hold

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 71.59%. Comparing base (732f648) to head (8842ed0).
Report is 14 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##             main     #810       +/-   ##
===========================================
- Coverage   94.42%   71.59%   -22.84%
===========================================
  Files          55       54        -1
  Lines        2027     2017       -10
===========================================
- Hits         1914     1444      -470
- Misses        113      573      +460

Files
Coverage Δ

ols/src/query_helpers/docs_summarizer.py
95.08% <100.00%> (-4.92%)
:arrow_down:

... and 26 files with indirect coverage changes

But later we can include role or any additional character during truncation itself.. and we will achieve below..

@asamal4 do we have a story for implementing that change?

/approve
but you broke a unit test (and we should have an e2e test for this behavior)

/approve
but you broke a unit test (and we should have an e2e test for this behavior)

yup broke, it was on purpose. With @asamal4 's PR, it is fixed now

/lgtm
concerns about https://github.com/openshift/lightspeed-service/pull/810/files#r1581220802 can be addressed in a refactor followup

/retest


[PostgreSQL] return main array types in data types list.

PostgreSQL is a special database that has a huge list of data types.
Now we read standard data types (int4, varchar, time etc.), add aliases (like serial) and user data types.
Yo can enable reading of all data types in connection settings.
Now we need to return to the main list of types - basic array data types (_int4, _varchar, _time etc.).

Implemented. Also array types is now in the end of possible data types list for the column.

verified


New version: Bobby v1.0.1

Registering package: Bobby
Repository: https://github.com/alemelis/Bobby.jl
Created by: @alemelis
Version: v1.0.1
Commit: 66a535a9857323c4f697c75ed1e26eed0d7dfb2d
Reviewed by: @alemelis
Reference: https://github.com/alemelis/Bobby.jl/commit/66a535a9857323c4f697c75ed1e26eed0d7dfb2d#commitcomment-39479881

@@alemelis why did you increase the version to 1.0.1?  If you https://github.com/alemelis/Bobby.jl/blob/e7ea0438c9fa02ad78d0cd790d8be9649020ea5b/Project.toml#L4 to v1.0.0 and register again then #15474 will be updated.
Generally speaking, if you want to fix an automerge issue, just fix it and retrigger again registration with the same version, so that the already open PR will be automatically updated.  Note also that you need to either remove https://github.com/JuliaRegistries/General/pull/15474#issuecomment-634775791 or add in the [noblock] text so that it will be ignored and automerge can work

@@alemelis why did you increase the version to 1.0.1? If you https://github.com/alemelis/Bobby.jl/blob/e7ea0438c9fa02ad78d0cd790d8be9649020ea5b/Project.toml#L4 to v1.0.0 and register again then #15474 will be updated.
Generally speaking, if you want to fix an automerge issue, just fix it and retrigger again registration with the same version, so that the already open PR will be automatically updated. Note also that you need to either remove #15474 (comment) or add in the [noblock] text so that it will be ignored and automerge can work

@giordano thanks for replying
probably I'm not doing it right, but I get
Error while trying to register: "Tag with name v1.0.0 already exists and points to a different commit"

https://github.com/alemelis/Bobby.jl/commit/e25bc02d522928ca3abe18f9532b1a2f5e9459e2

Delete this tag: https://github.com/alemelis/Bobby.jl/releases/tag/v1.0.0.  If you want to create tags, I can recommend using TagBot, which will create the tag after the version has been successfully merged here in the registry, so that the tags will always be in sync with the registry

Oh, you already have it

right, thanks
I add the TagBot after pushing the release

Awesome!  #15474 will now be automatically merged, so I'm going to close this one :wink:


[Feature] Lidar fake perception

Status
DEVELOPMENT
Description
#1431
Todos

[ ] Tests
[x] Documentation

Steps to Test or Reproduce
Please see here.
https://github.com/CPFL/Autoware/blob/feature/lidar_fake_perception/ros/src/computing/perception/detection/lidar_detector/packages/lidar_fake_perception/README.md

@kfunaoka Thanks for your quick response. I fixed them.

Hah, travis network error occured while build test...
https://travis-ci.org/CPFL/Autoware/jobs/414346087

@aohsato Did 589e749 work fine on your PC?
[  4%] Building CXX object computing/perception/detection/lidar_detector/packages/lidar_fake_perception/CMakeFiles/lidar_fake_perception_node.dir/nodes/lidar_fake_perception.cpp.o
Generating moc_selectionwidget.cpp
In file included from /home/funaoka/Autoware/ros/src/computing/perception/detection/lidar_detector/packages/lidar_fake_perception/nodes/lidar_fake_perception.cpp:4:0:
/home/funaoka/Autoware/ros/src/computing/perception/detection/lidar_detector/packages/lidar_fake_perception/include/lidar_fake_perception.h:16:42: fatal error: autoware_msgs/DetectedObject.h: No such file or directory
compilation terminated.

@kfunaoka yes of course and local build test by industrial_ci was passed on indigo/kinetic. please double check my code...

@aohsato I've face the error on my PC. I'll check what is wrong (my env or some other stuff).

It might be a cmake bug. Travis appears to have the same problem.
$ cmake --version
cmake version 3.5.1

./catkin_make_release -j1 makes lidar_fake_perception_node be built after DetectedObject is generated.
[ 43%] Generating EusLisp code from autoware_msgs/DetectedObject.msg
Scanning dependencies of target lidar_fake_perception_node
[ 74%] Building CXX object computing/perception/detection/lidar_detector/packages/lidar_fake_perception/CMakeFiles/lidar_fake_perception_node.dir/nodes/lidar_fake_perception.cpp.o
[ 74%] Building CXX object computing/perception/detection/lidar_detector/packages/lidar_fake_perception/CMakeFiles/lidar_fake_perception_node.dir/nodes/lidar_fake_perception_node.cpp.o
[ 74%] Linking CXX executable /home/funaoka/Autoware/ros/devel/lib/lidar_fake_perception/lidar_fake_perception_node

./catkin_make_release makes lidar_fake_perception_node be built before DetectedObject is generated.
Scanning dependencies of target _catkin_empty_exported_target
[  3%] Built target _catkin_empty_exported_target
Scanning dependencies of target lidar_fake_perception_node
[  4%] Building CXX object computing/perception/detection/lidar_detector/packages/lidar_fake_perception/CMakeFiles/lidar_fake_perception_node.dir/nodes/lidar_fake_perception.cpp.o
In file included from /home/funaoka/Autoware/ros/src/computing/perception/detection/lidar_detector/packages/lidar_fake_perception/nodes/lidar_fake_perception.cpp:four:0:
/home/funaoka/Autoware/ros/src/computing/perception/detection/lidar_detector/packages/lidar_fake_perception/include/lidar_fake_perception.h:16:42: fatal error: autoware_msgs/DetectedObject.h: No such file or directory
compilation terminated.
computing/perception/detection/lidar_detector/packages/lidar_fake_perception/CMakeFiles/lidar_fake_perception_node.dir/build.make:62: recipe for target 'computing/perception/detection/lidar_detector/packages/lidar_fake_perception/CMakeFiles/lidar_fake_perception_node.dir/nodes/lidar_fake_perception.cpp.o' failed
make[2]: *** [computing/perception/detection/lidar_detector/packages/lidar_fake_perception/CMakeFiles/lidar_fake_perception_node.dir/nodes/lidar_fake_perception.cpp.o] Error 1
CMakeFiles/Makefile2:27891: recipe for target 'computing/perception/detection/lidar_detector/packages/lidar_fake_perception/CMakeFiles/lidar_fake_perception_node.dir/all' failed
make[1]: *** [computing/perception/detection/lidar_detector/packages/lidar_fake_perception/CMakeFiles/lidar_fake_perception_node.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[  4%] Built target points2vscan_automoc
Generating moc_selectionwidget.cpp

@aohsato I've created a pull request #1440 for the issue where autoware_msgs/DetectedObject.h can not be found. Thanks @yn-mrse!

@kfunaoka Thanks much! I forgot about adding add_dependencies...
@cirpue49 Could you please test and comment?

@cirpue49 Super thanks! I resolved conflict and am waiting travis...


added an example of the "virtual (copy) constructor idiom"

Apologies - I have been out of action for a while, so have only just gotten round to merging this in. Thanks very much for the contribution! I gave it a bit of a review and edit, including:

Simplified the code by showing only a single derived class (the reader can extrapolate for themselves)
Simplified the code by performing the copy in a function, rather than in another class
Removed some unnecessary notes in the description
Reworded parts of the description
Added a note to the end about not being able to use smart pointers due to return type covariance

Will be deploying an updated build of the site later today. Thanks again.


Issue with "Titles"

Hey @khushi-joshi-05 ,  I've noticed a few issues with the website that I'd like to work on:
Website Title Enhancement: As we click on Home , Menu , Service , Contact and Cart , we reach on another page , but the title above on the screen does not change as you can see in the screenshots. It's always showing "Food ordering website" , only on Cart page it shows "My Cart". I think on loading other pages too , It should have some amazing title like
"Food Ordering Website | Home" or "Foodie Website | Home"
"Food Ordering Website | Service"
"Food Ordering Website | Contact"
"Food Ordering Website | Cart"
So that user can easily see what page they are loading.

Could you please assign me this issue under GSSoC'24?

i want to work on this project

please assign me


93258: Status for R4 and Stu3 is changed to active where R5 will stay as "draft"

Description
Status in CapabilityStatement returns as "draft" for all R4/R5 and Stu3 versions.
Requirement is to change Status for R4 and Stu3 to "active" and leaving R5 status as "draft".
Related issues
93258#
Testing
Called {{fhirURL}}/metadata for all three versions Stu3, R4 and R5.
Stu3 and R4 has "status": "active" and R5 has "status": "draft", in CapabilityStatement
FHIR Team Checklist

[ ] Update the title of the PR to be succinct and less than 50 characters
[ ] Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
[ ] Tag the PR with the type of update: Bug, Dependencies, Enhancement, or New-Feature
[ ] Tag the PR with Azure API for FHIR if this will release to the Azure API for FHIR managed service (CosmosDB or common code related to service)
[ ] Tag the PR with Azure Healthcare APIs if this will release to the Azure Healthcare APIs managed service (Sql server or common code related to service)
[ ] CI is green before merge
Review squash-merge requirements

Semver Change (docs)
Patch|Skip|Feature|Breaking (reason)

this is already working. so, closing this PR.


Use --quiet by default for marlint CLI

Because we treat 'warning' as recommendation and not a failure, we need to use --quiet option by default in our CLI. Instead add new flag --all to fail on warning

Turns out this is not a good idea. We should still warn, it's up to us in CI what to do


sops_decrypt_file(): resolve path argument relative to terragrunt.hcl

Description
Update path resolution logic in sops_decrypt_file() to resolve relative path arguments relative to the file containing the call to sops_decrypt_file(), rather than relative to the working directory of the Terragrunt process.
This change should be invisible for the common case of running Terragrunt directly inside the directory containing terragrunt.hcl. However, it enables intuitive use of terragrunt run-all with sops_decrypt_file(), ensuring configurations behave the same, no matter if they're evaluated directly or under run-all.
An additional test case for sops_decrypt_file() was added that validates its behavior in combination with run-all.

TODOs
Read the Gruntwork contribution guidelines.

[x] Update the docs.
[x] Run the relevant tests successfully, including pre-commit checks.
[x] Include release notes. If this PR is backward incompatible, include a migration guide.

Release Notes (draft)

Updated sops_decrypt_file() path resolution to be relative to terragrunt.hcl instead of Terragrunt's working directory.
Migration Guide

If you were relying on the behavior of terragrunt run-all on a set of modules using sops_decrypt_file() using a file in the current working directory, such as a shared secret, you can wrap the argument to sops_decrypt_file() in a call to find_in_parent_folders(), as shown in the documentation for sops_decrypt_file().

My bad. I just copied the existing test case that was there at the time I made the change without thinking. Should be fine now, I hope.

Hey @sybereal
I've run the tests for this functionality, and they still aren't passing. Are you able to run the tests locally?
This PR has been open for a long time, and while this functionality seems very convenient, there are workarounds via functions like get_terragrunt_dir.
We can leave the PR open a little bit longer, but if you could ensure that tests are passing before re-requesting review from me, that would be great.

Could you tell me which tests are failing that aren't failing on master? I can't see the CircleCI logs even after creating an account, and locally I can't run the full suite because I do not have an AWS account set up. I specifically ran only the sops tests with go test ./... -run '.*Sops.*', and those were fine, but ofc that way I can't tell if my change broke anything else.

Running the tests after rebase worked!


unit test/tiny refactor

Codecov Report

Merging #20 (d2ba7f6) into main (d645619) will decrease coverage by 27.04%.
The diff coverage is 23.62%.

@@             Coverage Diff             @@
##             main      #20       +/-   ##
===========================================
- Coverage   64.28%   37.23%   -27.05%
===========================================
  Files           4        8        +4
  Lines         308      333       +25
===========================================
- Hits          198      124       -74
- Misses         91      207      +116
+ Partials       19        2       -17

Flag
Coverage Δ

Linux
37.23% <23.62%> (-27.05%)
:arrow_down:

Windows
?

macOS
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/cmd2/add.go
0.00% <0.00%> (ø)

pkg/cmd2/import.go
0.00% <0.00%> (ø)

pkg/cmd2/search.go
0.00% <0.00%> (ø)

cmd/listings.go
52.17% <38.29%> (-8.39%)
:arrow_down:

pkg/cmd2/listings.go
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Use provider names from mimesis master

The providers seem to have gone out of sync, eg
mimesis.providers.Personal in the meanwhile has become
mimesis.providers.Person.
Should be fixed w/ this mini commit : )

@casio Thanks!


Local storage not available in Safari private browsing

Vue.js version
1.0.23
Steps to reproduce
Take your Safari Browser and enter the private browsing mode. Or just disable local storage.
What is Expected?
VueJS should work as expected even if no local storage is available.
What is actually happening?
On of my clients respond with a message to me, that some functions on their website aren't working properly. I found out that when you browsing in Safari private mode that there is no local storage available. In Firefox and Chrome local storage works fine in private browsing.
For my bugs I just wrapped the necessary local storage accesses in a try catch block. That solved my problem.
Any ideas about if this should be solved?

This is unrelated to Vue.js. Vue.js is an interface library, and does not use local storage.


Implemented render steps for bloom effect on emissive materials

Adds tracking of elements with emissive material to the viewer, and adjusts the rendering steps to render out the emissive materials to a separate buffer to apply a bloom effect. Note that this effect sidesteps the emissive property of PBR, and instead produces a more neon-like glow.
To render the correct elements to the right buffers, additional bookkeeping is required in the ConstructRender class. This is something that should probably be streamlined in the future, as the scene preparation code is starting to look like spaghetti when squinting at it.
Limitations:

this PR does not add support for particle systems with emissive materials.
The off-screen buffers used for the bloom effect should be multisampled for pixel-perfect accuracy when blending them into the final frame, but three-d does not (yet) have support for multisampled textures.

Modified the actual colors slightly by taking the team color and adding 10 to each channel to make it all a bit brighter, adding more (like 64 to each channel) made the glow really white.
Looks great :tada:  I've rebased it and merging, thanks for the contribution :+1:


Footer issue

Closes issue: #1824
Describe the changes you've made
Removed that extra footer margin that was not looking so good.
Checklist:

[✔] My code follows the style guidelines of this project.
[✔] I have performed a self-review of my own code.
[✔] I have commented my code, particularly in hard-to-understand areas.
[✔] I have made corresponding changes to the documentation.
[✔] New and existing unit tests pass locally with my changes.

Screenshots

@RiyaGupta89 this PR is related to issue #1782


remove routed service, should be handled by the package

See https://github.com/pfsense/pfsense-packages/pull/1006

Resubmitted as #1829


Approximate wavelength-dependent spectrum

Since difference in size of planet is small, we can just compute
F(\lamba) = F(\lambda_0) + dF/dr (r(\lambda)-r(\lambda_0))

But, the limb-darkening will change with wavelength as well, so not sure this will work.


Source Image repeatedly "changed"

Hi there,
after creating a HA NAT Gateway setup using the give module, we experience the following behaviour lately:
Even though, we haven't changed our code at all, suddenly tfplan outputs the following change:
-/+ module.nat-zone-2.module.nat-gateway.google_compute_instance_template.default (new resource required)       id:                                                  "default-20180920175925090000000001" => <computed> (forces new resource)       can_ip_forward:                                      "true" => "true"       disk.#:                                              "1" => "1"       disk.0.auto_delete:                                  "true" => "true"       disk.0.boot:                                         "true" => "true"       disk.0.device_name:                                  "persistent-disk-0" => <computed>       disk.0.disk_size_gb:                                 "0" => "0"       disk.0.disk_type:                                    "pd-ssd" => "pd-ssd"       disk.0.interface:                                    "SCSI" => <computed>       disk.0.mode:                                         "READ_WRITE" => <computed>       disk.0.source_image:                                 "projects/debian-cloud/global/images/family/debian-9" => "debian-cloud/debian-9" (forces new resource)       disk.0.type:                                         "PERSISTENT" => "PERSISTENT"       machine_type:                                        "n1-standard-1" => "n1-standard-1"       metadata.%:                                          "2" => "2"
Even when we recreate the NAT-Gateways, upon executing the next "tfplan" this pending change is reported again. I'm assuming that the referenced "debian-cloud/debian-9" is internally mapped to a fully qualified name called "projects/debian-cloud/global/images/family/debian-9" upon creation.
Can you confirm and fix the issue please?
My suggestion is to change the image to the long name --> projects/debian-cloud/global/images/family/debian-9
Thanks!
Maik

Are you seeing that today (24 Sept) each new terraform apply requires a "new resource" even when nothing changed?
I did not see that problem a few days ago, with same or very similar code. I tried reverting to provider google 1.17, but that did not seem to solve the problem.
Do you think this is related to the debian-cloud naming (or change thereof ?). Thanks :-)

I was having this issue as well. If you set the compute_image = "projects/debian-cloud/global/images/family/debian-9" manually it will stop trying to rebuild the instance. I've also opened a PR changing the variable to avoid this workaround.
https://github.com/GoogleCloudPlatform/terraform-google-nat-gateway/pull/93

Thanks @jbanton-dm . This temporarily fixed it for us.
Nevertheless, the mentioned fix #93 should be merged.

I'm going to apply a similar change to the managed-instance-group module which has the same issue.


how can we remap the Preview key bindings?

I would like to remap the key bindings for scrolling up/down the preview window
can it accept/reuse the FZF options in the environment variables?

You can now override the default mappings with your own:
https://github.com/camspiers/snap/commit/3f068ca0361f47118fa00b455623a5bbd0b007d8
These are the default mappings:
{
    ["enter-split"] = {"<C-x>"},
    ["enter-tab"] = {"<C-t>"},
    ["enter-vsplit"] = {"<C-v>"},
    ["next-item"] = {"<C-n>"},
    ["next-page"] = {"<C-f>"},
    ["prev-item"] = {"<C-p>"},
    ["prev-page"] = {"<C-b>"},
    ["select-all"] = {"<C-a>"},
    ["view-page-down"] = {"<C-d>"},
    ["view-page-up"] = {"<C-u>"},
    enter = {"<CR>"},
    exit = {"<Esc>", "<C-c>"},
    next = {"<C-q>"},
    select = {"<Tab>"},
    unselect = {"<S-Tab>"}
}

snap.run {
  producer = snap.get'producer.ripgrep.vimgrep',
  select = snap.get'select.vimgrep'.select,
  multiselect = snap.get'select.vimgrep'.multiselect,
  views = {snap.get'preview.vimgrep'},
  mappings = {
    ["view-page-down"] = { put your mappings here },
    ["view-page-up"] = { put your mappings here },
  }
}


Sema: Fix crash on settable storage accesses on lvalue existentials

Fixes #62219

@swift-ci please smoke test macOS

@swift-ci please test source compatibility debug

@swift-ci please smoke test

@swift-ci please test

Slava gave me a go-ahead. Most of the modified code was originally authored by me, so we’re fine.


Improve micro performance

Remove unnecessary if state logic in the for loop

It looks you are embarking some commits from another branch. Can you please rebase the current branch?

I'll check

ok looks good :+1:


Build fails  from tarball,  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1)

src/math/src/poly.findroots.c:287:9: error: non-floating-point argument in call to function ‘__builtin_isnan’
if (isnan(du) || isnan(dv)) {
^
src/math/src/poly.findroots.c:287:9: error: non-floating-point argument in call to function ‘__builtin_isnan’
: recipe for target 'src/math/src/polyc.o' failed
Thanks for the help

I got this too. Casting du and dv to float made the compiler error go away and "make check" still succeeds (" PASSED ALL 42373 CHECKS")
liquid-dsp-1.2.0$ diff -u src/math/src/poly.findroots.c{.orig,}
--- src/math/src/poly.findroots.c.orig	2016-07-05 16:44:30.094003182 -0700
+++ src/math/src/poly.findroots.c	2016-07-05 16:44:36.018079503 -0700
@@ -284,7 +284,7 @@
#endif
     // adjust u, v

   if (isnan(du) || isnan(dv)) {

   if (isnan((float)du) || isnan((float)dv)) {
       u *= 0.5f;
       v *= 0.5f;
   } else {

HEAD on master already has a fix for this, for what it's worth
https://github.com/jgaeddert/liquid-dsp/commit/3055eb3da9d0a202c1a975f7db0c8370a09a30bc

Thanks for the notice. I should just spin a new release and tarball soon as the latest one is woefully out of date.

Yes please.


Add startup tests for machine word size

The server should fail to start on a 32-bit platform.

can we not just add
when (sizeOf @Int undefined /= 8) $ do
  throwIO (AssertionFailed "Not on a 64-bit platform.")

as the first line of the server?

That is exactly what we should add.

Okay, done

Will push when i get out of the bathroom

fixed by 870bba099815a281406176c3ad727d44876e9446


macOS make install fail

install ./doc/man3/i2d_CMS_bio_stream.pod -> /usr/local/share/doc/openssl/html/man3/i2d_CMS_bio_stream.html
Cannot find "ERR_get_error(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "CMS_sign(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "CMS_verify(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "CMS_encrypt(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "CMS_decrypt(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SMIME_write_CMS(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "PEM_write_bio_CMS_stream(3)" in podpath: cannot find suitable replacement path, cannot resolve link
install ./doc/man3/i2d_PKCS7_bio_stream.pod -> /usr/local/share/doc/openssl/html/man3/i2d_PKCS7_bio_stream.html
Cannot find "ERR_get_error(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "PKCS7_sign(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "PKCS7_verify(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "PKCS7_encrypt(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "PKCS7_decrypt(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SMIME_write_PKCS7(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "PEM_write_bio_PKCS7_stream(3)" in podpath: cannot find suitable replacement path, cannot resolve link
install ./doc/man3/i2d_re_X509_tbs.pod -> /usr/local/share/doc/openssl/html/man3/i2d_re_X509_tbs.html
Cannot find "d2i_X509(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "i2d_X509(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "i2d_X509(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "ERR_get_error(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "X509_CRL_get0_by_serial(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "X509_get0_signature(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "X509_get_ext_d2i(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "X509_get_extension_flags(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "X509_get_pubkey(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "X509_get_subject_name(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "X509_get_version(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "X509_NAME_add_entry_by_txt(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "X509_NAME_ENTRY_get_object(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "X509_NAME_get_index_by_NID(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "X509_NAME_print_ex(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "X509_new(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "X509_sign(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "X509V3_get_d2i(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "X509_verify_cert(3)" in podpath: cannot find suitable replacement path, cannot resolve link
link /usr/local/share/doc/openssl/html/man3/d2i_X509_AUX.html -> /usr/local/share/doc/openssl/html/man3/i2d_re_X509_tbs.html
d2i_X509_AUX.html => i2d_re_X509_tbs.html
link /usr/local/share/doc/openssl/html/man3/i2d_X509_AUX.html -> /usr/local/share/doc/openssl/html/man3/i2d_re_X509_tbs.html
i2d_X509_AUX.html => i2d_re_X509_tbs.html
link /usr/local/share/doc/openssl/html/man3/i2d_re_X509_CRL_tbs.html -> /usr/local/share/doc/openssl/html/man3/i2d_re_X509_tbs.html
i2d_re_X509_CRL_tbs.html => i2d_re_X509_tbs.html
link /usr/local/share/doc/openssl/html/man3/i2d_re_X509_REQ_tbs.html -> /usr/local/share/doc/openssl/html/man3/i2d_re_X509_tbs.html
i2d_re_X509_REQ_tbs.html => i2d_re_X509_tbs.html
install ./doc/man3/o2i_SCT_LIST.pod -> /usr/local/share/doc/openssl/html/man3/o2i_SCT_LIST.html
Cannot find "d2i_SCT_LIST" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "d2i_SCT_LIST" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "i2d_SCT_LIST" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "d2i_SCT_LIST(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "i2d_SCT_LIST(3)" in podpath: cannot find suitable replacement path, cannot resolve link
link /usr/local/share/doc/openssl/html/man3/i2o_SCT_LIST.html -> /usr/local/share/doc/openssl/html/man3/o2i_SCT_LIST.html
i2o_SCT_LIST.html => o2i_SCT_LIST.html
link /usr/local/share/doc/openssl/html/man3/o2i_SCT.html -> /usr/local/share/doc/openssl/html/man3/o2i_SCT_LIST.html
o2i_SCT.html => o2i_SCT_LIST.html
link /usr/local/share/doc/openssl/html/man3/i2o_SCT.html -> /usr/local/share/doc/openssl/html/man3/o2i_SCT_LIST.html
i2o_SCT.html => o2i_SCT_LIST.html
install ./doc/man5/config.pod -> /usr/local/share/doc/openssl/html/man5/config.html
install ./doc/man5/x509v3_config.pod -> /usr/local/share/doc/openssl/html/man5/x509v3_config.html
Cannot find "ASN1_generate_nconf(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "ASN1_generate_nconf(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "ASN1_generate_nconf(3)" in podpath: cannot find suitable replacement path, cannot resolve link
install ./doc/man7/bio.pod -> /usr/local/share/doc/openssl/html/man7/bio.html
Cannot find "BIO_ctrl(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "BIO_f_base64(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "BIO_f_buffer(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "BIO_f_cipher(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "BIO_f_md(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "BIO_f_null(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "BIO_f_ssl(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "BIO_find_type(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "BIO_new(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "BIO_new_bio_pair(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "BIO_push(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "BIO_read_ex(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "BIO_s_accept(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "BIO_s_bio(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "BIO_s_connect(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "BIO_s_fd(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "BIO_s_file(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "BIO_s_mem(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "BIO_s_mem(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "BIO_s_null(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "BIO_s_socket(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "BIO_set_callback(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "BIO_should_retry(3)" in podpath: cannot find suitable replacement path, cannot resolve link
install ./doc/man7/crypto.pod -> /usr/local/share/doc/openssl/html/man7/crypto.html
install ./doc/man7/ct.pod -> /usr/local/share/doc/openssl/html/man7/ct.html
Cannot find "d2i_SCT_LIST(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "CTLOG_STORE_new(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "CTLOG_STORE_get0_log_by_id(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SCT_new(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SCT_print(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SCT_verify(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SCT_validate(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "CT_POLICY_EVAL_CTX(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_set_ct_validation_callback(3)" in podpath: cannot find suitable replacement path, cannot resolve link
install ./doc/man7/des_modes.pod -> /usr/local/share/doc/openssl/html/man7/des_modes.html
Cannot find "BF_encrypt(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "DES_crypt(3)" in podpath: cannot find suitable replacement path, cannot resolve link
install ./doc/man7/evp.pod -> /usr/local/share/doc/openssl/html/man7/evp.html
Cannot find "EVP_SealInit(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_OpenInit(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_DigestSignInit(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_DigestVerifyInit(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_SignInit(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_VerifyInit(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_EncryptInit(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_DigestInit(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_PKEY_new(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_PKEY_set1_RSA(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_PKEY_keygen(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_PKEY_cmp(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_PKEY_print_private(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_PKEY_derive(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_PKEY_sign(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_PKEY_verify(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_PKEY_verify_recover(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_DigestSignInit(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_PKEY_encrypt(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_PKEY_decrypt(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_SealInit(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_OpenInit(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_BytesToKey(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_EncodeInit(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_EncodeInit(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_DigestInit(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_EncryptInit(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_OpenInit(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_SealInit(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_DigestSignInit(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_SignInit(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_VerifyInit(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_EncodeInit(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_PKEY_new(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_PKEY_set1_RSA(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_PKEY_keygen(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_PKEY_print_private(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_PKEY_decrypt(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_PKEY_encrypt(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_PKEY_sign(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_PKEY_verify(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_PKEY_verify_recover(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_PKEY_derive(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "EVP_BytesToKey(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "ENGINE_by_id(3)" in podpath: cannot find suitable replacement path, cannot resolve link
install ./doc/man7/ssl.pod -> /usr/local/share/doc/openssl/html/man7/ssl.html
Cannot find "SSL_CTX_new(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_new(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_set_fd(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_set_bio(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_accept(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_connect(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_read_ex(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_read(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_write_ex(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_write(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_shutdown(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_new(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "BIO_s_accept(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_clear(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "CRYPTO_get_ex_new_index(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_accept(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_clear(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_connect(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CIPHER_get_name(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_COMP_add_compression_method(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_add_extra_chain_cert(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_add_session(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_ctrl(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_flush_sessions(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_get_verify_mode(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_load_verify_locations(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_new(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_sess_number(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_sess_set_cache_size(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_sess_set_get_cb(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_sessions(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_set_cert_store(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_set_cert_verify_callback(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_set_cipher_list(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_set_client_CA_list(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_set_client_cert_cb(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_set_default_passwd_cb(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_set_generate_session_id(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_set_info_callback(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_set_max_cert_list(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_set_mode(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_set_msg_callback(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_set_options(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_set_quiet_shutdown(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_set_read_ahead(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_set_security_level(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_set_session_cache_mode(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_set_session_id_context(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_set_ssl_version(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_set_timeout(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_set_tmp_dh_callback(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_set_verify(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_use_certificate(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_alert_type_string(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_do_handshake(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_enable_ct(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_get_SSL_CTX(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_get_ciphers(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_get_client_CA_list(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_get_default_timeout(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_get_error(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_get_ex_data_X509_STORE_CTX_idx(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_get_fd(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_get_peer_cert_chain(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_get_rbio(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_get_session(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_get_verify_result(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_get_version(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_load_client_CA_file(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_new(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_pending(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_read_ex(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_read(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_rstate_string(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_session_reused(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_set_bio(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_set_connect_state(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_set_fd(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_set_session(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_set_shutdown(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_shutdown(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_state_string(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_want(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_write_ex(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_write(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_SESSION_free(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_SESSION_get_time(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "d2i_SSL_SESSION(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_set_psk_client_callback(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_CTX_use_psk_identity_hint(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "SSL_get_psk_identity(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "DTLSv1_listen(3)" in podpath: cannot find suitable replacement path, cannot resolve link
install ./doc/man7/x509.pod -> /usr/local/share/doc/openssl/html/man7/x509.html
Cannot find "X509_NAME_ENTRY_get_object(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "X509_NAME_add_entry_by_txt(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "X509_NAME_add_entry_by_NID(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "X509_NAME_print_ex(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "X509_NAME_new(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "d2i_X509(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "d2i_X509_ALGOR(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "d2i_X509_CRL(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "d2i_X509_NAME(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "d2i_X509_REQ(3)" in podpath: cannot find suitable replacement path, cannot resolve link
Cannot find "d2i_X509_SIG(3)" in podpath: cannot find suitable replacement path, cannot resolve link

Well...  that pod2html spewing a bit more than necessary.  Can you verify that links weren't properly produced in the resulting HTML files (just pick one it complained about)?

As long as make install doesn't return non-zero, it doesn't count as failure. I mean question is what does make install return. You can examine the value for example with echo $? immediately after make install completes. The value being zero might mean two things: a) above messages should be disregarded as harmless warnings; b) make install doesn't pay enough attention to failures. Question also is if it's actually MacOS-specific, as it might be perl-version specific. I mean question also if what does perl -v print...

No update from original poster in six months; closing issue.  Please re-open if still a problem.


Projects not opening in Visual Studio

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Clone
Open solution in Visual Studio 2019 with latest EF Core

Any log messages given by the failure

No log messages, but the tooltip text hovering over each project says "This project requires user input. Reload the project for more information." When I select "Reload Project" for any of the 5 projects, it says "The operation cannot be completed"

Expected/desired behavior

View files in each project in VS (without having to setup Azure resources)

OS and Version?

Windows 10

Versions

1903 build 18362.418

Mention any other details that might be useful

Thanks! We'll be in touch soon.

I changed the SDK version in global.json, and we're good to go.


Issue to obtain the test token

Describe the feature request
I have suggestion that use another test token, as so many contributor they dont obtain the token for testing, etc.
the best way is to have another type token.
Spam policy

[X] I verify that this issue is NOT SPAM and understand SPAM issues will be closed and reported to GitHub, resulting in ACCOUNT TERMINATION.

I agree

true

Thousands of users are doing it successfully. So no.


Handle concurrency failures

Currently, in the connectors, it is possible that a resource gets created on the underlying store (in the underlying key vault), but the key fails to get added to the DB.
In such a scenario, a retry will fail because the key exists in the Vault by ID. There are multiple solutions to this problem but the goal of this ticket is to discuss them and choose one:
Solutions:

Do not correlate the ID of the QKM with the ID of the vault and generate a new ID when creating a new key. In such a scenario, it is possible that keys get created on the underlying vault but retrying will work as the ID will be different.
Delete key in vault if it fails to get added to the DB
?

if we create in the underlying store but never reference them, they will just leak/pollute the store. I guess we should just delete the key in the backend before leaving the func.
Another idea would be to reuse it for a new key, and link them on a new create. But that require more complexity to keep an "unlinked" set of key somewhere. It's more optimised (if the creation of key is costly), but more complex. I don't think it's worth adding this complexity at this level of the project.


ROX-15146: Disable certgen API for managed Central

Description
Restrict certgen API for managed centrals. A small refactoring has been made in order to reuse the existing helper methods.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Testing performed manually on a local cluster with helm installation method.
Here I tell how I validated my change

Generate chart

docker run -it --rm -v "$(pwd):/usr/src/stackrox" quay.io/stackrox-io/roxctl:4.1.x-842-g944704de24 helm output central-services --image-defaults opensource --output-dir /usr/src/stackrox/stackrox-central-services-chart --remove

Install central

helm upgrade -i --namespace=stackrox stackrox-central-services ./stackrox-central-services-chart --values ./tmp/helm/values/values-central-dev.yaml --set env.managedServices=true --create-namespace

Open UI
Ensure that certificate download fails

/test ocp-4-13-operator-e2e-tests

For full coverage I guess it would also make sense to verify that download still works as expected in a non-managed setting. But perhaps this is already verified by e2e tests?

Tested with env.managedServices=false as well


yet another windows 10 build fail ( 2.0 rc.0 )

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10 x64
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
TensorFlow installed from (source or binary): source
TensorFlow version: 2.0-rc.0
Python version: 3.7.4
Installed using virtualenv? pip? conda?: N/A
Bazel version (if compiling from source): 0.26.0 x64
GCC/Compiler version (if compiling from source):  Visual Studio 2019
CUDA/cuDNN version: 10.1 / 7.6.2
GPU model and memory: RTX 2080Ti GDDR6 11GB

Describe the problem
build failed
Provide the exact sequence of commands / steps that you executed before running into the problem
bazel build --config=opt --config=v2 --define=no_tensorflow_py_deps=true //tensorflow/tools/pip_package:build_pip_package

Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
ERROR: D:/repo/tensorflow/tensorflow/core/grappler/optimizers/data/BUILD:712:1: C++ compilation of rule '//tensorflow/core/grappler/optimizers/data:rebatch' failed (Exit 2): python.exe failed: error executing command
  cd C:/users/alan-workstation/_bazel_alan-workstation/ibqopsat/execroot/org_tensorflow
  SET CUDA_TOOLKIT_PATH=C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v10.1
    SET INCLUDE=C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE;C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\ATLMFC\INCLUDE;C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\ucrt;C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\shared;C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\um;C:\Program Files (x86)\Windows Kits\10\include\10.0.18362.0\winrt;
    SET LIB=C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\LIB\amd64;C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\ATLMFC\LIB\amd64;C:\Program Files (x86)\Windows Kits\10\lib\10.0.18362.0\ucrt\x64;C:\Program Files (x86)\Windows Kits\10\lib\10.0.18362.0\um\x64;
    SET PATH=C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\amd64;C:\WINDOWS\Microsoft.NET\Framework64\v4.0.30319;C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE;C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools;C:\Program Files (x86)\Windows Kits\10\bin\x64;C:\Program Files (x86)\Windows Kits\10\bin\x86;;C:\WINDOWS\system32
    SET PWD=/proc/self/cwd
    SET PYTHON_BIN_PATH=C:/Anaconda3/python.exe
    SET PYTHON_LIB_PATH=C:/Anaconda3/lib/site-packages
    SET RUNFILES_MANIFEST_ONLY=1
    SET TEMP=C:\Users\ALAN-W~1\AppData\Local\Temp
    SET TF_CONFIGURE_IOS=0
    SET TF_CUDA_COMPUTE_CAPABILITIES=7.5
    SET TF_NEED_CUDA=1
    SET TMP=C:\Users\ALAN-W~1\AppData\Local\Temp
  C:/Anaconda3/python.exe -B external/local_config_cuda/crosstool/windows/msvc_wrapper_for_nvcc.py /nologo /DCOMPILER_MSVC /DNOMINMAX /D_WIN32_WINNT=0x0600 /D_CRT_SECURE_NO_DEPRECATE /D_CRT_SECURE_NO_WARNINGS /D_SILENCE_STDEXT_HASH_DEPRECATION_WARNINGS /bigobj /Zm500 /J /Gy /GF /EHsc /wd4351 /wd4291 /wd4250 /wd4996 /I. /Ibazel-out/x64_windows-py2-opt/bin /Iexternal/com_google_absl /Ibazel-out/x64_windows-py2-opt/bin/external/com_google_absl /Iexternal/eigen_archive /Ibazel-out/x64_windows-py2-opt/bin/external/eigen_archive /Iexternal/local_config_sycl /Ibazel-out/x64_windows-py2-opt/bin/external/local_config_sycl /Iexternal/nsync /Ibazel-out/x64_windows-py2-opt/bin/external/nsync /Iexternal/gif_archive /Ibazel-out/x64_windows-py2-opt/bin/external/gif_archive /Iexternal/jpeg /Ibazel-out/x64_windows-py2-opt/bin/external/jpeg /Iexternal/com_google_protobuf /Ibazel-out/x64_windows-py2-opt/bin/external/com_google_protobuf /Iexternal/com_googlesource_code_re2 /Ibazel-out/x64_windows-py2-opt/bin/external/com_googlesource_code_re2 /Iexternal/farmhash_archive /Ibazel-out/x64_windows-py2-opt/bin/external/farmhash_archive /Iexternal/fft2d /Ibazel-out/x64_windows-py2-opt/bin/external/fft2d /Iexternal/highwayhash /Ibazel-out/x64_windows-py2-opt/bin/external/highwayhash /Iexternal/zlib_archive /Ibazel-out/x64_windows-py2-opt/bin/external/zlib_archive /Iexternal/double_conversion /Ibazel-out/x64_windows-py2-opt/bin/external/double_conversion /Iexternal/snappy /Ibazel-out/x64_windows-py2-opt/bin/external/snappy /Iexternal/local_config_cuda /Ibazel-out/x64_windows-py2-opt/bin/external/local_config_cuda /Iexternal/local_config_tensorrt /Ibazel-out/x64_windows-py2-opt/bin/external/local_config_tensorrt /Ibazel-out/x64_windows-py2-opt/bin/external/local_config_cuda/cuda/_virtual_includes/cuda_headers_virtual /Ibazel-out/x64_windows-py2-opt/bin/external/local_config_tensorrt/_virtual_includes/tensorrt_headers /Ibazel-out/x64_windows-py2-opt/bin/external/local_config_cuda/cuda/_virtual_includes/cudnn_header /Ibazel-out/x64_windows-py2-opt/bin/external/local_config_cuda/cuda/_virtual_includes/cublas_headers_virtual /Iexternal/eigen_archive /Ibazel-out/x64_windows-py2-opt/bin/external/eigen_archive /Iexternal/nsync/public /Ibazel-out/x64_windows-py2-opt/bin/external/nsync/public /Iexternal/gif_archive/lib /Ibazel-out/x64_windows-py2-opt/bin/external/gif_archive/lib /Iexternal/gif_archive/windows /Ibazel-out/x64_windows-py2-opt/bin/external/gif_archive/windows /Iexternal/com_google_protobuf/src /Ibazel-out/x64_windows-py2-opt/bin/external/com_google_protobuf/src /Iexternal/farmhash_archive/src /Ibazel-out/x64_windows-py2-opt/bin/external/farmhash_archive/src /Iexternal/zlib_archive /Ibazel-out/x64_windows-py2-opt/bin/external/zlib_archive /Iexternal/double_conversion /Ibazel-out/x64_windows-py2-opt/bin/external/double_conversion /Iexternal/local_config_cuda/cuda /Ibazel-out/x64_windows-py2-opt/bin/external/local_config_cuda/cuda /Iexternal/local_config_cuda/cuda/cuda/include /Ibazel-out/x64_windows-py2-opt/bin/external/local_config_cuda/cuda/cuda/include /Iexternal/local_config_cuda/cuda/cublas/include /Ibazel-out/x64_windows-py2-opt/bin/external/local_config_cuda/cuda/cublas/include /D__CLANG_SUPPORT_DYN_ANNOTATION__ /DEIGEN_MPL2_ONLY /DEIGEN_MAX_ALIGN_BYTES=64 /DEIGEN_HAS_TYPE_TRAITS=0 /DTF_USE_SNAPPY /showIncludes /MD /O2 /DNDEBUG -w -DWIN32_LEAN_AND_MEAN -DNOGDI /arch:AVX /Fobazel-out/x64_windows-py2-opt/bin/tensorflow/core/grappler/optimizers/data/_objs/rebatch/rebatch.o /c tensorflow/core/grappler/optimizers/data/rebatch.cc
Execution platform: @bazel_tools//platforms:host_platform
tensorflow/core/grappler/optimizers/data/rebatch.cc(66): fatal error C1001: An internal error has occurred in the compiler.
(compiler file 'msc1.cpp', line 1468)
 To work around this problem, try simplifying or changing the program near the locations listed above.
Please choose the Technical Support command on the Visual C++
 Help menu, or open the Technical Support help file for more information
Internal Compiler Error in C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\amd64\cl.exe.  You will be prompted to send an error report to Microsoft later.
INTERNAL COMPILER ERROR in 'C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin\amd64\cl.exe'
    Please choose the Technical Support command on the Visual C++
    Help menu, or open the Technical Support help file for more information
Target //tensorflow/tools/pip_package:build_pip_package failed to build
INFO: Elapsed time: 1520.158s, Critical Path: 200.17s
INFO: 3706 processes: 3706 local.
FAILED: Build did NOT complete successfully
FAILED: Build did NOT complete successfully

Just to verify did you get chance to follow instructions from TensorFlow website .Please, let us know.
Please, go through the below link and see if it helps you.Thanks!
https://github.com/tensorflow/tensorflow/issues/31085

@ravikyram
I see, so vs2019 is not supported and seems to be never?

build success with VS2017, closing

Are you satisfied with the resolution of your issue? Yes No

Hello,
I tried to compile with VS2017, CUDA 10 and the bazel version listed in the tutorial -[https://www.tensorflow.org/install/source_windows], but rebatch.cc couldn't get compiled. So I changed the file like this and the build had success.
Previous:
constexpr std::array<const char, 6> kBatchDatasetOps = {
kBatchOp,       kBatchV2Op,      kMapAndBatchOp, kExperimentalMapAndBatchOp,
kPaddedBatchOp, kPaddedBatchV2Op};*
Changed:
constexpr std::array<const char, 6> kBatchDatasetOps = {
"BatchDataset", "BatchDatasetV2", "MapAndBatchDataset", "ExperimentalMapAndBatchDataset",
"PaddedBatchDataset", "PaddedBatchDatasetV2"
};*
Greetings!


Preserve Unity project hierarchy fully

It would be great to not have to place game objects under the ArenaClient object since it makes it hard for devs to locally test their scripts. Since now, it will remove those objects after the Player has ended.
It would be better to have a way to set ArenaObject components to mirror themselves, perhaps the whole set of GameObjects in the project, preserving the developers hierarchy and allowing a synchronization step check on Player start, with appropriate confirmations.

Added in #35.


libspatialindex: 1.9.3 -> 2.0.0

Description of changes
Update libspatialindex to the latest major version.
There are no significant major enhancements or refactorings that should change
any behaviors. It had been a long time (almost 5 years!) since a release and
2.0.0 was the next version number...
Release notes:
https://github.com/libspatialindex/libspatialindex/releases/tag/2.0.0

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.


Code for Activity 7

@ldconejo, Code for Activity 7.
student name: Juan Camilo Medina

Good progress with the Django project.
-Luis