I'd like to use the following mapping in my mappings.lua configuration:
map('n', '<C-D-[>', ':BufferPrevious<cr>', options)
map('n', '<C-D-]>', ':BufferNext<cr>', options)
map('n', '<C-D-w>', ':BufferClose<cr>', options)
I currently have this in my kitty.conf which is not working.
map ctrl+cmd+[ send_text all ?
The latest commit of the current Neovide repository does not support macOS without Python2 installed.
To fix this, you should revert to commit db53e94 after cloning the repository. To do this, execute the following command:
git reset --hard db53e94
And add the following environment variables in zshrc:
export SKIA_BINARIES_URL=https://github.91chi.fun//https://github.com/rust-skia/skia-binaries/releases/download/{tag}/skia-binaries-{key}.tar.gz
Restart the shell, re-use the cargo bundle --release command to build the App, and drag the built App to the /Applications folder.
Related
I am trying to build onnxruntime from source on Linux. According to this instruction I have successfully built python wheels and shared libs. But I have not seen headers for C API.
There is a build option --build_csharp which seems to enable C#/C packages. I tried to add this option but got following errors.
CMake Warning at CMakeLists.txt:137 (message):
Language Csharp is not found in the system
I installed dotnet-sdk-3.1 but still got this error. Can I ask how to properly generate onnxruntime C API on Linux? Thanks!
Please try the following steps:
- Steps to build ONNX from source code:
1. git clone --recursive https://github.com/Microsoft/onnxruntime
2. Get the commit ID of the version you want to build (In case you want older version)
3. git checkout "your commitID"
4. Install the required version of Cmake on your system
6. Run: <path>\build.sh --config Release --build_shared_lib --parallel
7. A build folder will be created in the onnxruntime.
5. Get the onnxruntime.dll from the dir: \onnxruntime\build\Windows\Release\Release
6. Get the required headers (onnxruntime_c_api.h, onnxruntime_cxx_api.h, onnxruntime_cxx_inline.h)
from the dir: \onnxruntime\include\onnxruntime\core\session and put it in the unit location.
When I run flutter change channel or flutter doctor, the CMD show me this:
C:\Users\MyUser>flutter doctor -v
Checking Dart SDK version...
Building flutter tool...
Running pub upgrade...
/C:/src/flutter/packages/flutter_tools/lib/src/aot.dart:144:5: Warning: Must explicitly return a value from a non-void function.
return;
^
When I run:
git clean -xfd
git pull
flutter doctor
The CDM show me this:
fatal: not a git repository (or any of the parent directories): .git
How can I solve it? Thank you
Had the same issue...Copied the flutter_tools from flutter download and replaced with the same folder in my installation then ran flutter doctor from command in administrator mode.
Funny the issue started 3 days ago for me too.
1.Go the Flutter install directory and please run (in cmd)
git clean -xfd
git stash save --keep-index
git stash drop
git pull
2.and restart your computer
then run
flutter doctor
3.then go to your project path run
flutter packages get
flutter run
I had the exact same problem yesterday, i tired to run
git clean -xfd
git pull
flutter doctor
in cmd and i kept getting:
fatal: not a git repository (or any of the parent directories): .git
eventually i gave up and i deleted the old flutter sdk directory from my PC as well as the path from Enviroment Variables and i downloded the new sdk and setup flutter again and now it's running fine
https://docs.flutter.dev/get-started/install
On windows, delete flutter folder C:\Users\User\AppData\Local\Pub
This is the flutter temp/cache folder and may contain outdated versions of the libraries
unfortunately none of the given solution so far works for me..
I had to the following steps, which was the only solution for me:
delete the whole flutter folder
extract (or copy) it from the zip-file to your installation directory (in my case I just downloaded the latest flutter version, because I didn't have access to the previous downloaded zip-file anymore)
open the IDE in the installation directory (or open the associated project)
run flutter pub get
I've created an F# (script) app via the dotnet cli using the following outlined steps. However, when I open the app/project in VS Code with Ionide, intellisense is inactive. How can I resolve this?
To create the app/project, I:
Created an app directory
Ran dotnet new tool-manifest and dotnet tool install paket and dotnet paket restore
Ran dotnet paket init
Modified paket.dependencies
Opened "project" in VS Code with Ionide
paket.dependencies (Note: I removed framework restrictions)
source https://api.nuget.org/v3/index.json
storage: packages
nuget FSharp.Data
Script:
#r "./packages/FSharp.Core/lib/netstandard2.0/FSharp.Core.dll"
#r "./packages/FSharp.Data/lib/netstandard2.0/FSharp.Data.dll"
open System
open FSharp.Data
type research = CsvProvider<"./path/to/file", HasHeaders=true, PreferOptionals=true>
let data = research.GetSample()
I am trying to get just one folder to build (see above). I have the following YML file in that folder:
version: '0.0.{build}'
image: Visual Studio 2017
configuration: Release
build: off
notifications:
- provider: Email
to:
- keith#sol3.net
subject: CI build 0.0.{build} failed!
on_build_success: false
on_build_failure: true
on_build_status_changed: false
init:
# Best practice (Windows line endings different to Unix/Linux)
- cmd: git config --global core.autocrlf true
install:
appveyor DownloadFile https://dist.nuget.org/win-x86-commandline/v4.0.0/nuget.exe
before_build:
# Display .NET Core version
- cmd: dotnet --version
# Change to specific project folder
- cmd: cd Sol3.Infrastructure
# Display minimal restore text
- cmd: dotnet restore Sol3.Infrastructure.csproj --verbosity m
build_script:
- cmd: dotnet build Sol3.Infrastructure.csproj
- cmd: dotnet pack -c Release /p:PackageVersion=0.0.{build}
after_build:
# For once the build has completed
on_finish :
# any cleanup in here
deploy: off
Constantly getting error of too many SLN/PRJ files. Also noticed that it is NOT using this file as the version is matching the default settings in Appveyor itself.
Appveyor's appveyor.yml file:
version: 1.0.{build}
build:
verbosity: minimal
Can appveyor do this? Is appveyor the best choice? Any guidance?
This is my sandbox (tiny right now) and I have several projects and would like each project to have it's own appveyor.yml file. I do have SLN files in there too and those are artifacts from VS2017 before I switched to VSCode. Thinking I should delete those now until I need to put a SLN together...
By default AppVeyor checks for appveyor.yml or .appveyor.yml in the root of your repo. If you need to specify custom file name or custom path (relative to the repo root), you need to do this in Custom configuration .yml file name filed in General project setting. Some more information is here. What probably happens now is that AppVeyor has not idea about your YML file in the Sol3.Infrastructure and goes with default configuration in which it searches for VS solution or project to build.
Side notes:
nuget is pre-installed
I would recommend using paths relative to the build folder, instead
of doing CD
no need to cleanup at on_finish, each build runs on transient VM,
which is being deleted right after build finished
Context
We are trying to use edeliver to deploy a "Hot Upgrade" of a Phoenix Web Application to a remote Virtual Machine instance.
Our aim is to build an "upgrade" version of the app each time so that the app can be "hot" upgraded in production without any down-time.
We have succeeded in doing this "hot upgrade" on a "Hello World" phoenix app:
https://github.com/nelsonic/hello_world_edeliver which is automatically deployed from Travis-CI when the build passes. see: https://travis-ci.org/nelsonic/hello_world_edeliver/builds/259965752#L1752
So, in theory this technique should work for our "real" app.
Attempting to Deploy a "Real" Phoenix App using Edeliver
Ran the following command (to build the upgrade):
mix edeliver build upgrade --auto-version=git-revision --from=$(git rev-parse HEAD~) --to=$(git rev-parse HEAD) --verbose
i.e. "build the upgrade from the previous git revision to the current one"
So far, so good. "Release successfully built!"
Error: vm.args: No such file or directory
When we attempt to deploy the upgrade:
mix edeliver deploy upgrade to production --version=1.0.3+86d55eb --verbose
cat: /home/hladmin/healthlocker/releases/1.0.3+86d55eb/vm.args: No such file or directory
Note: we have a little bash script that reads the latest upgrade version available in .deliver/releases and deploys that see: version.sh
Question:
Is there a way to ignore the absence of the vm.args file and continue the deployment?
Or if the file is required to complete the deployment, is there some documentation on how to create the file?
Note: we have read the distillery "Runtime Configuration" docs: https://github.com/bitwalker/distillery/blob/master/docs/Runtime%20Configuration.md and are sadly none-the-wiser ...
Additional Info
Environment
Localhost: Mac running Elixir 1.4.2
Build Host: Ubuntu 16.04.2 LTS running Elixir 1.4.5
mix.exs file: https://github.com/healthlocker/healthlocker/blob/continuous-delivery/mix.exs
edeliver version: 1.4.4
Build tool: distillery version: 1.4.0
Umbrella project: yes.
This question was also asked on: https://github.com/edeliver/edeliver/issues/234
As mentioned by others, the vm.args file is necessary for BEAM to run the release. A default file is created by distillery during the release build process and should be located in releases/<version>/vm.args. From your log output it looks like expected directory is being checked.
Can you show us the contents of /home/hladmin/healthlocker/releases/?
Can you confirm that the default vm.args file is being created when building the release and extracting it (outside of the upgrade process)?
You also asked:
Or if the file is required to complete the deployment, is there some documentation on how to create the file?
If diagnosing the problem with the default vm.args file doesn't get you anywhere, you can also write your own file and configure distillery to use that file instead of the default. The details for this are in the distillery configuration docs. In short,
add the vm_args setting to your distillery config, which should be at rel/config.exs(relative to your project root), for example:
environment :prod do
set vm_args: "<path>/vm.args"
[...]
end