make menuconfig not supported on Windows

Since the kconfiglib switch, make/ninja menuconfig can't work on Windows, but this page implies it's possible run menuconfig on Windows:
http://docs.zephyrproject.org/application/application.html#overriding-default-configuration
A fix for this issue likely involves writing a Python3 GUI on top of kconfiglib that allows users to graphically edit their configuration.

@ulfalizer awesome, thanks for the pointers! I wish I had more time to work on this :\

Here's a "wish list" for this particular feature:

Python3-based tool that includes all of menuconfig's functionality
Uses one of the ncurses replacement libraries above
Has full mouse support
Tested on *NIX and Windows 7/10

Options for the GUI library to use:
https://github.com/peterbrittain/asciimatics
https://github.com/erikrose/blessings
https://github.com/jonathanslenders/python-prompt-toolkit

I've done some initial review of these based on their documentation and installing them and playing around with their basic examples.
In all three cases, the libraries appear to be thoughtfully designed and carefully implemented.
Blessings provides basic terminal coloring and text styling, as well as positioning and fullscreen control. The feature set seems too restricted to implement the full wish-list, which includes features like text boxes and input fields, mouse support, etc., without a lot of trouble.
Asciimatics, by contrast, provides TUI support, including buttons, line drawings, and (terminal permitting) mouse input, out of the box.
Prompt toolkit has all of the above, as well as support for advanced features like text autocomplete, Emacs and Vi keybindings within the TUI, and more.
I would therefore rule out blessings and restrict the search to Asciimatics and Prompt toolkit.
Between the two, prompt toolkit seems to have a much better ecosystem, with many significant projects using it as a backend. I'm a longtime user of the IPython shell, for example, and I was interested to learn it uses prompt_toolkit. Some of the other features people have implemented on it (like the aws shell) were futuristic by CLI standards -- really impressive stuff.
Asciimatics is Apache 2.0, prompt toolkit is BSD 3 clause.
Given that, I think prompt toolkit is a clear winner, as something that can be used to start small but eventually produce really killer features.

Given that, I think prompt toolkit is a clear winner, as something that can be used to start small but eventually produce really killer features.

Ugh, though there's some pain coming down the pipe:
https://github.com/jonathanslenders/python-prompt-toolkit/issues/568

Ugh, though there's some pain coming down the pipe

Not sure this is a real problem, it looks like he'll push to pypi without changing the name, and even if he did change the name we could use the *2 version?

Nice coincidence. I just bumped Kconfiglib's major version to 3 (though I doubt anyone will be affected by the small API behavior change -- just sticking to principles since I said I use semantic versioning). :P
Yeah, seems best to go with the *2 version. Thanks for the investigation!

Not sure this is a real problem, it looks like he'll push to pypi without changing the name, and even if he did change the name we could use the *2 version?

Lots of tools depend on the 1 version, I'm not sure how distro package management would cope with both installed in one system -- I guess 'import prompt_toolkit' would work with the version 1 from apt in your IPython install, but the *2 version in your pip --user install in the Zephyr environment?
More seriously, testing things in the early documentation pages beyond hello-world from the 2.0 branch broke fairly often. It seems like the docs are in some kind of intermediate state between the two versions, which could be a pain to develop against.

Probably wouldn't be a huge pain to switch out prompt_toolkit out for something else at least, if it turns out to be a pain. Could do a basic usable version with just keyboard input and simple menu drawing first, and then see what to go with from there when adding more fancy features like mouse support. The basic version would probably be pretty easy to port over to other toolkits if needed.

Would be cool if there was a UI toolkit that could generate both a text-based user interface and a graphical UI as output, depending on settings. Doubt there's anything like that though.

Here's some notes from playing around a bit with some of the toolkits (I might update them as I go):
ASCIIMATICS
The API and widget set seem nice and flexible, and mouse support is good.
Unfortunately, there's really noticeable startup delay and (worse) input delay in the UI examples I tried (samples/contactlist.py, samples/forms.py, samples/treeview.py).
Holding down a key in the contactlist.py example, I saw CPU usage go up to 90% on my Core i7-2600k. I think ASCIIMATICS might have been more of an animation library initially, with the UI stuff added later.
Here's two related issues I found:

ENH: samples for common UI forms seems slow (no background animation in the examples I tried though, afaics)

Startup performance seems pretty bad

Python Prompt Toolkit
Seems to be focused on text input, with some widgets tacked on.
Mouse support might only be available for text widgets and simple buttons:

Clicking checkboxes and radio buttons in examples/full-screen/yes-no-dialog.py doesn't do anything. Clicking the <YES>/<NO> buttons at the bottom works though, and the mouse also works for the menu at the top.

The mouse doesn't work at all in example/full-screen/buttons.py

There's also the upcoming 2.0 version switch that @mbolivar mentioned, which seems a bit messy.
Urwid
Haven't looked into it much, but it seems it might lack Windows support.
The standard curses module
Pretty low-level and do-it-yourself.
Doesn't work out of the box on Windows, though getting it ro run might be possible.
Unicurses is related (though there seems to be other options). It might have an issue with 64-bit Windows though.
Blessings
A thin wrapper around the standard curses module, with the same limitations. Also seems to use some ioctl() stuff for terminal resizing that might not work on Windows.

Made a little progress on a version that uses the curses module. It's still in a WIP (hacky) state and missing essential features (no save/load, symbol information, search, mouse support, etc.)
The curses-specific parts are trivial, so it'd be easy to switch out curses for something else. I suspect that will be true when more features are added as well. Most of the complication is in menu navigation logic and the like.

Some things I like about curses:

Zero dependencies on *nix (the curses module is in the Python standard library).

Fast and snappy (pretty much instantaneous response). Unresponsive/flickering UIs is a personal pet peeve.

Super flexible.

It would be nice if PDCurses turns out to be a viable option on Windows. Then we could use curses everywhere.
I added somw Vi keybindings by the way, in addition to the "intuitive" keybindings:

J/K: Down/up

L: Toggle item or jump into menu

H: Jump to parent menu

Tell me if you have any other feature requests. :)

@mbolivar @SebastianBoe @nashif @ulfalizer
I have looked through the option of using PDCurses and the .whl file you point to, but here are the issues with it:

We don't have the source code for it for the latest Python version
It's unsupported, placed in some random person's homepage
If a problem arises on a user's computer (say a segfault) we are on our own and we would need to provide our own wheel
It doesn't support Unicode
It is awkward to install (download the wheel for the particular Python version and architecture)
It might disappear in the future or not be supported for upcoming Python versions, leaving us hanging

Therefore I would much rather use a pure Python alternative that gives us the certainty that we will be able to support it for many years into the future.

A few more comments on the options you list:

Urwid does not work on Windows, requires several modules not available on it, so not an option
Blessings doesn't seem to support color on Windows, comes with no examples either, it's a very small project

For me the best contender is still python-prompt-toolkit by far because of all the reasons listed so far.

@gbakke FYI

Summing up some notes from IRC:

FWIW, the guy providing the Python PDCurses wheel seems to be pretty serious. But yeah, there's of course the risk that he stops updating them.

I wonder what form the Unicode brokenness in the Python PDCurses wheel takes. Slightly messed-up display vs. very messed-up display vs. not being able to input Unicode stuff at all would make a difference I think.

python-prompt-toolkit is about to release version 2.0, which isn't on PyPI yet. @carlescufi noted that it can be installed directly from the GitHub repo with e.g. pip install -e<EMAIL_ADDRESS>

All I really need is a text output buffer + input events. I'm going for a simple fullscreen interface that would be intuitive to people used to make menuconfig, and I think a fancy UI toolkit is overkill for that (and would get messy if the widgets don't fit the model). The interface is just a list, some buttons, and a few modal dialogs.
I wonder if python-prompt-toolkit can be used like a portable curses.

All the work I'm doing now would apply for any toolkit (i'm basically only using getch() + addstr() on the curses side), so I could get a usable version done in curses first and then switch over to something else if needed.

@ulfalizer thanks for the updates. If all you need is getch() and addstr() then I am pretty sure we can get a version of those relatively easily either using PPT or taking the necessary code from it.

@carlescufi I suspect it might be messy to rip it out cleanly if they don't provide it in the interface. There's probably display optimization and stuff going on. I think that's needed to avoid flicker even in terminal emulators.
Pretty sure we'll work something out at least. :)

Got Windows installed and did some testing. Works fine until you resize the terminal.
Unfortunately, fixing that might be a bit painful. Some notes:
No KEY_RESIZE events are returned by getch() in the Python code, so the terminal resize isn't even detected. PDCurses itself supports KEY_RESIZE, but the wheel does not. Functions like curses.resizeterm() and curses.is_term_resized() end up not even existing.
It might be because setup.py from the wheel only has this:
define_macros = [("WINDOW_HAS_FLAGS", None)]`

Looking at _cursesmodules.c in the wheel source code (which is a just modified version of _cursesmodule.c from the CPython sources), it looks like HAVE_CURSES_IS_TERM_RESIZED and the like would need to be defined for those functions to become available. Maybe those macros are supposed to get defined by the extension building framework when building extensions though...
Perhaps rebuilding the wheel (python setup.py build) with some extra flags would fix it at least.

I added a simple configuration dialog for string/int/hex values (no input verification yet) and save/load functionality, so it's in a basic usable state now.
Still ugly as sin, but that's for later.

Some missing/planned stuff:

Symbol information
I'm thinking of a format similar to the one generated by genrest.py.

Search and "jump to"
I want a list of matching symbols to pop up as you type. Selecting a symbol will jump directly to it in the menu tree.

"Show all" mode
This would show symbols even if they aren't currently visible. That would make the search nicer, as "show all" mode could be turned on automatically if the symbol you jump to isn't visible.
It would probably be a nice feature to have in other cases too.

Please tell me if there's any other features you want to see.

@ulfalizer This is excellent progress. the "Search and jump to" functionality is something I've always wanted in menuconfig so this will be most welcome.
Regarding the beautification, I would settle with a simple color scheme reasonably similar to what's in menuconfig today, but maybe @mbolivar, @nashif or @SebastianBoe have opinions on the visual style that we should adopt here.
In any case, nice work.

maybe @mbolivar, @nashif or @SebastianBoe have opinions on the visual style that we should adopt here.

I wish I had opinions :).
I don't use menu-driven applications from the terminal much (I prefer xconfig to menuconfig).
My only general idea would be that discoverability, for users who are accustomed to full-featured GUIs would be preferable to magic key sequences to get help or otherwise start to figure out how to use the application.

Hello,
Status update is mostly that I wasted time on nitpicking alternative scrolling implementations and trickiness related to that. Scrolling is surprisingly tricky to get robust, with having to remember positions when jumping in and out of menus, nodes disappearing, windows being resized, scroll offsets, page up/down, the window being resized while a dialog is open, etc.
I'll try to get back to more essential stuff soon so I can get a first version out. Should really have left some of this till later, but you know how it is when you double down on stuff.
@mbolivar
Any particular features in xconfig that you've missed in menuconfig?

Hi Ulf, awesome update. I think it's time to post a DNM/RFC PR now so we can start discussing this. The PR should also include the following:

Integration with CMake (at this point I suggest just using menuconfig.py instead of mconf with the same framework as the current one)
Removal of C tools (we really want to get rid of those in one shot)

In a follow-up PR then we can target:

Switch from source to gsource
Simplification of kconfig.cmake

I think the for CMake side @SebastianBoe can probably contribute, so we are all in sync from the get go

Status update:

Refactored the color/style code to be easy to maintain. The first version was ad-hoc and spread out.

Fixed crashes and other issues when colors and other optional features aren't supported. I tested with TERM=vt100, since it's likely to work with most terminals if it works with that.

Added verification of ranges, so you get an error if you attempt to set an int/hex symbol to a value outside an active range.
It isn't strictly illegal to set an out-of-bounds value (though the value will be ignored while the range is still in effect), but I decided that it's a good idea anyway.

Made visible if properly hide menus.

Did a little bit of work on the help display dialog.

Getting closer.

Status update:

Made an information interface in the same style as the main display.

Added information texts for all the different types of items (symbols, choices, menus, comments). It should have most of the stuff from make menuconfig now, barring stuff I've missed.

Tweaked expression printing to show the values of all the operands, like make menuconfig does.
I also made it point out when a symbol is undefined, as make menuconfig displays that in a super-confusing way (S390[="S390"] means S390 is undefined there, while it now shows up as S390(=undefined/n) now).

Screenshots below:

As seen in the last screenshot, long expressions can get ugly, which is a problem make menuconfig has as well. The expression could probably be split it up in some way to fix it, but it might not be a priority at the moment.
Major TODOS off the top of my head:

Check that everything still works on Windows.

Clean up and let the dust settle a bit.

There's now a do-not-merge pull request at https://github.com/zephyrproject-rtos/zephyr/pull/7140. Feedback appreciated!

A proper pull request is now at https://github.com/zephyrproject-rtos/zephyr/pull/7174.

This has now landed in master

Nice work @ulfalizer!


Generate Only flag doesn't seem to work for creating certs

Im trying to use a multisig akash wallet to share access to infra in our DAO.
I was trying to:
akash tx cert generate client --from $my_multisig --generate-only
But the error I was getting was: Error: cannot sign with offline keys.  Which makes it seem like --generate-only is being ignored since it shouldn't be signing a transaction.
I also tried akash tx cert publish client --from $my_multisig  --generate-only with the same error.
When I tried --generate-only with a non multisig key, it just created the client cert.
Unless Im doing something wrong, it seems like we can't use --generate-only to generate unsigned cert and deployment transactions?

@troian Hey, quick question: it seems that the generate-only flag is not being checked and that the NewKeyPairManager is creating a signature and using it as a password for keyPairManager; however, if this account is multi-sig, the signature will fail due to not reaching the threshold.
Is it possible to check for the flag and, if it exists, do a passwordless keyPairMAnager or maybe also require a password?
https://github.com/akash-network/node/blob/52d5ee5caa2c6e5a5e59893d903d22fe450d6045/x/cert/utils/key_pair_manager.go#L47-L58

I think one of the things to consider is what would be the implications of generating a keyPairManager with an empty string as password.
	keyPairManager{
		addr:          fromAddress,
		passwordBytes: []bytes(""),
		homeDir:       cctx.HomeDir,
	}

because if this is possible, I can  create a PR to fix this and make use of the flag. I'm just not sure if there and security implications on generating a certificate.
I just see usage for it here:
	blk, err = x509.EncryptPEMBlock(rand.Reader, types.PemBlkTypeECPrivateKey, keyDer, kpm.passwordBytes, x509.PEMCipherAES256) // nolint: staticcheck

https://github.com/akash-network/node/blob/52d5ee5caa2c6e5a5e59893d903d22fe450d6045/x/cert/utils/key_pair_manager.go#L256
Or find another mechanism to generate a password that does not involve signing.

@JeancarloBarrios thanks for digging, yeah, it does not work with msig accounts at the moment.
track https://github.com/akash-network/support/issues/59 for updates to cert tool. i have PoC in my stash, however there is one dependency that creates version collision between cosmos-sdk and new pem library.
i hope we get it resolved when new cosmos-sdk ends up in the node repo

I was reading the related issues and it seems that go std library will not add support for PKCS8 so probably will need to use something like: https://pkg.go.dev/golang.org/x/crypto/pbkdf2 not sure if this is the related library that is colliding with cosmos SDK.
Is this change also affecting things on the provider repo too?

we will be switching to go.step.sm/crypto with PKCS8 support

i'll give a think for multisig issue as well.

fixed in v0.24.0 network upgrade


Authentication set via pulumi config not being picked up by the provider

     Type                         Name                       Plan       Info
 +   pulumi:pulumi:Stack          azure-potential-issue-dev  create
     └─ azure:core:ResourceGroup  resourceGroup                         1 error

Diagnostics:
  azure:core:ResourceGroup (resourceGroup):
    error: Error building AzureRM Client: Authenticating using the Azure CLI is only supported as a User (not a Service Principal).

    To authenticate to Azure using a Service Principal, you can use the separate 'Authenticate using a Service Principal'
    auth method - instructions for which can be found here: https://www.terraform.io/docs/providers/azurerm/guides/service_principal_client_secret.html

    Alternatively you can authenticate using the Azure CLI by using a User Account.

The config was set as follows:
▶ pulumi config
KEY                   VALUE
azure:clientId        [secret]
azure:clientSecret    [secret]
azure:environment     public
azure:location        WestUS
azure:subscriptionId  [secret]
azure:tenantId        [secret]

the same code works when setting these as environment variables

the work around for this while the amazing people at Pulumi are writing a fix is to set the environment variables your self with the following:
export ARM_CLIENT_SECRET=`pulumi config get azure:clientSecret`
export ARM_CLIENT_ID=`pulumi config get azure:clientId`
export ARM_SUBSCRIPTION_ID=`pulumi config get azure:subscriptionId`
export ARM_TENANT_ID=`pulumi config get azure:tenantId`

then run pulumi up as normal

Hi all
We have found and are investigating this regression and will get a new version shipped asap!
P.


refactor(askcode): Simplify call(get('get'),'n') in generated AskCode

@km4 any updates here? Please let me know if you have any questions

get some problem with understanding this calculated/converted code.
Example:
*ask
ask() {
    let n
    n = 3
   return n
}

return  *askcode
ask(let('n'),assign('n',3),return(call(get('get'),'n')))

and if I paste on our playground all its fine, but if I change askcode to
ask(let('n'),assign('n',3),return(call(get('n'))))

got error Error: Cannot call 3

get some problem with understanding this calculated/converted code.
Example:
*ask
ask() {
    let n
    n = 3
   return n
}

return *askcode
ask(let('n'),assign('n',3),return(call(get('get'),'n')))

and if I paste on our playground all its fine, but if I change askcode to
ask(let('n'),assign('n',3),return(call(get('n'))))

got error Error: Cannot call 3

ok now I see, call(get(get the change to only get(

@km4 , the main idea for fixing this ticket is to fix the code which generates the .askcode files: https://github.com/xFAANG/askql/blob/master/src/test.jest.testRunner.ts
So just a find-and-replace in the generated .askcode files wouldn't be enough.
After you fix the generator, you can just easily remove all the .askcode files in the project, run npm test and they will be regenerated using your fixed code.

Hey, @km4 . Would you like more pointers for this issue?

@czerwinskilukasz1
Yes, I debug this generates process and I find the only problem in askCodeToSource function.
source
ask {
        let a =1
return a
}

askFormatted
ask() {
  let a = 1
  return get('a')
}

askCode const askCode = parseAskScript(askFormatted);
AskCode {
  name: 'ask',
  params: [
    AskCode { name: 'let', params: [Array] },
    AskCode { name: 'return', params: [Array] }
  ]
}

askSourceCode const askCodeSource = askCodeToSource(askCode);
ask(let('a',1),return(call(get('get'),'a')))

Then the problem is on https://github.com/xFAANG/askql/blob/master/src/askcode/lib/AskCode.ts#L76 ?

@czerwinskilukasz1 or @mhagmajer can you check this ^ ?

@km4 yes, that looks about right. If you're still working on that, please reopen the PR or comment on the issue #200


Reduced HTTP dependency requirement

Status
*READY
Description
Reduced the minimum requirement for the HTTP package from 1.1.0 to 0.13.4 to improve compatibility with other packages
Type of Change

[ ] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠 Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[x] 🧹 Code refactor
[ ] ✅ Build configuration change
[ ] 📝 Documentation
[ ] 🗑 Chore

Hi @manuelperez96 Can you please review and make a new version for this change?

I have a lot of work now. I try upload the changes as soon as possible

I have a lot of work now. I try upload the changes as soon as possible

Okay. Thank you 🙏

HI, thanks for the update. I already upload the new version to pudev. I included in the readme as a contributor.


Prettier: failed to parse buffer (PrettierAsync) for every JS file

Do you want to request a feature or report a bug?
Bug
What is the current/expected behavior?
Using PrettierAsync always results in the error Prettier: failed to parse buffer. Prettier  command works fine (on every file).
What version of vim-prettier are you using - (output of :PrettierVersion) ?
0.2.7
What version of prettier are you using - (output of  :PrettierCliVersion) ?
1.16.1
What is your prettier executable path - (output of  :PrettierCliPath) ?
/Users/dsaenger/code/titan-web/node_modules/.bin/prettier
(local project path)
Did this work in previous versions of vim-prettier and/or prettier ?
Did not use  vim-prettier before
To be clear: This error always occurs with whatever JS file when using :PrettierAsync, even Hello World:
console.log('Hello World');

.. but :Prettier works fine.
I'm using https://github.com/skwp/dotfiles vim config .. maybe vim-prettier does not work with another plugin .. how can I debug this?

I will look into this ASAP

Could you try with the prettier 1.0 branch ?
to try with the 1.0 branch please update your .vimrc to
from:
Plug 'prettier/vim-prettier', { 'do': 'yarn install' }

to:
Plug 'prettier/vim-prettier', { 'do': 'yarn install', branch: 'release/1.x' }

Curious to see if it still broken in there too

Thanks for taking the time and looking into this!
I tried the 1.0 branch but the result is exactly the same :/

HI @ds82  do you mind trying one more thing ?
on your vimrc :
try adding this
let g:prettier#config#config_precedence = 'file-override'

I don't mind at all .. I'm happy that you try to fix my problem!
Unfortunately, setting the variable makes no differences either :/

Hi @mitermayer, I had the same problem but switching to the release/1.x branch with 1.0.0-alpha version from the PrettierVersion command fixed the issue for me.

I will try to merge release/1.x branch to master ASAP, in the meantime feel free folks to use that branch directly
Plug 'prettier/vim-prettier', {
  \ 'do': 'yarn install',
  \ 'branch': 'release/1.x',
  \ 'for': [
    \ 'javascript',
    \ 'typescript',
    \ 'css',
    \ 'less',
    \ 'scss',
    \ 'json',
    \ 'graphql',
    \ 'markdown',
    \ 'vue',
    \ 'lua',
    \ 'php',
    \ 'python',
    \ 'ruby',
    \ 'html',
    \ 'swift' ] }

If anyone else could please try the release/1.x branch to confirm that it does fix this issue that would be great!

Tried the branch again (hash cb598c1212dfe20f5a5a950bdee529d224d574d9), but still does not work :/

@ds82  thanks for trying, can you post your vim --version paste ? I am still trying to figure out how to repro

I've just got this issue, trying the vim-prettier with release/1.x branch, to get the php support.
Both in js and php files running :Prettier and :PrettierAsync resulted in Prettier: failed to parse buffer.
The cause appeared to be the ruby plugin, I've just removed it manually for now:
~/.vim/plugged/vim-prettier on release/1.x!
$ yarn remove @prettier/plugin-ruby

Sidenote: the error message is not informative enough, maybe consider adding some debug / verbose mode. To find the issue I added echo a:errors into this functiona:
function! prettier#job#runner#onError(errors) abort
  call prettier#logging#error#log('PARSING_ERROR')
  echo 'Errors'
  echo a:errors
  ...
endfunction

And got the error:
[
'/home/user/.vim/plugged/vim-prettier/node_modules/@prettier/plugin-ruby/src/nodes.js:5',
'  ...require("./nodes/alias"),',
'  ^^^',
'SyntaxError: Unexpected token ...',
'    at createScript (vm.js:56:10)',
'    at Object.runInThisContext (vm.js:97:10)',
'    at Module._compile (module.js:542:28)',
'    at Object.Module._extensions..js (module.js:579:10)
',
'    at Module.load (module.js:487:32)',
'    at tryModuleLoad (module.js:446:12)',
'    at Function.Module._load (module.js:438:3)',
'    at Module.require (module.js:497:17)
',
'    at require (internal/module.js:20:19)',
'    at Object.<anonymous> (/home/user/.vim/plugged/vim-prettier/node_modules/@prettier/plugin-ruby/src/print.js:3:15)',
'    at Module._compile (module.js:570:32)',
'    at Object.Module._extensions..js (module.js:579:10)',
'    at Module.load (module.js:487:32)',
'    at tryModuleLoad (module.js:446:12)',
'    at Function.Module._load (module.js:438:3)',
'    at Module.require (module.js:497:17)'
]

Hi @ serebrov
The above error seems to come from prettier/ruby  cc @kddeisz

On the sidenote i will add to release/1.x a task to have errors a bit more clear when they are non syntax related

What's the minimum node version required for this? I specified 8 in the ruby plugin, but maybe I need to support older versions. This is using the spread operator which I guess this doesn't understand.

Hi @kddeisz ,
We currently do not have any specified node version https://github.com/prettier/vim-prettier/blob/master/package.json
I belive quite a few people are using older node versions as they seem to be encountering this issue

Alright I just released v0.8.0 for @prettier/plugin-ruby which supports the obsolete node versions. Let me know if people still have problems.

Thanks @kddeisz !

Just updated release/1.x to have the latest ruby prettier plugin https://github.com/prettier/vim-prettier/commit/18a42315acc254755b122b4afaf3896466227b6c
@serebrov  do you mind trying it again ?

@mitermayer yes, works for me now even on node 6.10.

Is this closable? It's just still on my radar so just want to make sure it's all fixed up.

This issue is closed on release/1.x  but since master still behind i will leave it open until this weekend when i will do the release/1.x release!

Sounds great!

This issue has been solved on release/1.x branch will close this to help me track fixed issues for the release changelog

This issue is NOT solved in release/1.x

Will reopen this to investigate issue reported above

I just ran into this message - sounds slightly different then what others are experiencing, but maybe one of these steps will help somebody else who lands here.
In my case, running :PrettierCliPath in vimh told me where my executables were, and then running that executable directly against any JS file revealed that I had an invalid .prettierrc for the version of prettier which installed with vim-prettier (but not my system version).
/Users/me/.vim/plugged//vim-prettier/node_modules/.bin/prettier myfile.tsx
resulted in
[error] Unable to expand glob patterns: hooks/useMeasure.tsx !**/node_modules/** !./node_modules/** !**/.{git,svn,hg}/** !./.{git,svn,hg}/**
[error] Invalid trailingComma value. Expected "all", "none", "php5" or "php7.2", but received "es5".

From here, fixing was easy, just fix errors in my .prettierrc until it stopped complaining. Now it's working great!

I had the same issue after updating node to lts (v12.17.0 in my case). I upgraded to newest prettier version (2.0.5) and it works now.

I encountered the same issue. on Sep 15, 2020

I met same issue, Step 18, 2020

I had the same issue. All I did just npm i -g prettier, and it works now.

I had the same issue. All I did just npm i -g prettier, and it works now.

It worked for me

I had the same issue. All I did just npm i -g prettier, and it works now.

Thanks! It worked for me, too. I wonder why the local version of prettier doesn't work, though. Is that a bug?

Just in case this helps someone else:
For me, it turned out to be something wrong with the system-installed version of nodejs (which I've never touched because I use NVM). I installed the LTS nodejs from the official site and vim-prettier immediately started working.
A hint that lead me to this solution was the output of the :PrettierCli command, which started with:
PrettierCli
Command terminated
dyld: Library not loaded: /usr/local/opt/icu4c/lib/libicui18n.64.dylib

Searching that error, I found a gist thread where people were having success by reinstalling node in homebrew. Since I don't use homebrew for managing node installations, I decided to try installing the official package.
Stoked to have prettier working again! 🎉

npm i -g prettier

This also worked for me.

I've tried all of the above to no fail.
:disappointed:
" Set prettier to run automatically
autocmd BufWritePre *.js,*.jsx,*.mjs,*.ts,*.tsx,*.css,*.less,*.scss,*.sass,*.json,*.graphql,*.md,*.vue,*.yml, *.yaml, *.html PrettierAsync
let g:prettier#autoformat = 1
let g:prettier#exec_cmd_async = 1
let g:prettier#config#parser = 'babylon'
let g:prettier#config#single_quote = 'true'
let g:prettier#config#trailing_comma = 'all'

Even tried the  npm i -g prettier - still failed
Prettier Version: 1.0.0-beta
Prettier CLI Version: 2.2.1
Not sure what to do anymore

I've tried all of the above to no fail.
" Set prettier to run automatically
autocmd BufWritePre *.js,*.jsx,*.mjs,*.ts,*.tsx,*.css,*.less,*.scss,*.sass,*.json,*.graphql,*.md,*.vue,*.yml, *.yaml, *.html PrettierAsync
let g:prettier#autoformat = 1
let g:prettier#exec_cmd_async = 1
let g:prettier#config#parser = 'babylon'
let g:prettier#config#single_quote = 'true'
let g:prettier#config#trailing_comma = 'all'

Even tried the npm i -g prettier - still failed
Prettier Version: 1.0.0-beta
Prettier CLI Version: 2.2.1
Not sure what to do anymore

For me, switching to 'release/1.x' branch worked. You might also try out ale, though I haven't tested it.

I had this issue, :Prettier was working as expected but when I was using it on save it failed. I was using this configuration to auto format on save:
let g:prettier#autoformat = 1
let g:prettier#autoformat_require_pragma = 0

Then reading :h prettier I realized that this was outdated, and changed it to:
let g:prettier#autoformat = 0
autocmd BufWritePre *.js Prettier

Now it works. Something to note is that if I use PrettierAsync instead of Prettier on BufWritePre the issue persist. Another thing that may help is that I used yarn instead of npm when installing  release/1.x. Plug 'prettier/vim-prettier', { 'do': 'yarn install', 'branch': 'release/1.x' }

I had this issue, :Prettier was working as expected but when I was using it on save it failed. I was using this configuration to auto format on save:
let g:prettier#autoformat = 1
let g:prettier#autoformat_require_pragma = 0

Then reading :h prettier I realized that this was outdated, and changed it to:
let g:prettier#autoformat = 0
autocmd BufWritePre *.js Prettier

Now it works. Something to note is that if I use PrettierAsync instead of Prettier on BufWritePre the issue persists. Another thing that may help is that I used yarn instead of npm when installing release/1.x. Plug 'prettier/vim-prettier', { 'do': 'yarn install', 'branch': 'release/1.x' }

This worked for me even without going to 'release/1.x'
Seems the commands are outdated.
Thanks @andrescuco

I am still seeing this issue. It happens when i add a new rule to the prettier config "arrowParens", "avoid", If i remove this config the issue goes away immediately

In my case, this is due to the node version in the session that you run vim with is not compatible with prettier that installed locally for the project.
try
./node_modules/.bin/prettier -v

if this errors out, try to lower the node version to around v10.*
in my case,
nvm use v10

got my problem solved.

I'm hitting the issue with PrettierAsync, but not Prettier. It doesn't matter if I run PrettierAsync manually or on file save.
$ npm -v
9.5.1
$ ~/.vim/bundle/node_modules/.bin/prettier -v
2.8.8
$ cat ~/.vim/bundle/vim-prettier/package.json
{
  "name": "vim-prettier",
  "author": "M* R*<EMAIL_ADDRESS>  "version": "1.0.0-beta",
  "description": "Vim plugin for prettier",
  "license": "MIT",
  "repository": {
    "type": "git",
    "url": "git://github.com/prettier/vim-prettier.git"
  },
  "scripts": {
    "test": "vim --version && LOG_LEVEL=error jest",
    "lint": "vint --version && vint ."
  },
  "dependencies": {
    "@prettier/plugin-lua": "0.0.1",
    "@prettier/plugin-php": "^0.16.3",
    "@prettier/plugin-ruby": "^0.8.0",
    "@prettier/plugin-xml": "^0.7.2",
    "prettier-plugin-svelte": "^2.3.1",
    "prettier": "^2.3.1"
  },
  "devDependencies": {
    "colors": "^1.3.2",
    "jest": "^23.6.0",
    "vim-driver": "^1.0.0"
  }
}


Set up statistiques from matchs

Get and process data from matchs then output understandable and relevant data. Will be saved on Firebase database.

Beginning with descriptive statistics

[ ]  Chose 1

[ ]  Chose 2

Add top 3 podium with

User image
Name
Score

[ ] Podium with user image, name and score
[ ] Compute best combination of players given previous results : result sent to @Nguyinh for a "Shuffle Mode"
[ ] Time-dependant statistics
[ ] Statistics per day accessible through a clickable calendar
[ ] Statistics per player integrated on each player's profile
[ ] Number of consecutive games without loosing
[ ] Evolution of statistics in time
[ ] Team statistics
[ ] Shuffle

Add large javascript object in each player document with will contain time-dependant data created at each match played such as :

Date

Match ID

Current season

New ELO score

more if needed

GOAL : remove statistiques.html's refresh to get data, time dependant stats data would be updated at each match added
WARNING : Handle when a match is deleted


When I open the menu I can't walk with it open and the aimbot doesn't work by itself. [BUG?]

It's like the title says, if I open the menu I can't walk and the aimbot doesn't work with the autoshoot on
[it would be nice to make him able to walk while the menu is open and the aimbot works]
4K demo video: https://www.youtube.com/watch?v=pZ9oPD9NEnY

feature

thats not a bug


[Powerpoint question]: Living lab demonstration

Imagine, we have a seminar room in our institute (ScaDS.AI) called the "Living Lab". There we meet people and showcase contemporary use of artificial intelligence. We have demonstrators such as the magic mirror where you can try out clothes virtually.
Please draw two pictures of this living lab:

One presenter discussion with a small group of people about AI.
One shopping person using the magic mirror to try out dresses.

git-bob try to do this

Ok cool. Now I need a powerpoint presentation explaining to decision makers at my university why we need more money for the living lab. We would like to buy more equipment (3D googles, Workstations wirth GPUs) and hire more staff to have more events as shown in the pictures. Make a Powerpoint presentation with 5 slides.
git-bob try to do this


Compiling SQL source plugin with docker container

Please describe your problem in detail, if necessary, you can upload the log file through the attachment:
Hi Community, I was trying to install SQL source plugin, following this guide, I have followed below steps

Cloned this repo
Run below command
go build -trimpath --buildmode=plugin -tags sqlserver -o plugins/sources/Sql.so extensions/sources/sql/*.go
copy  plugins/sources/Sql.so to /plugins/source in docker container
Restart docker container
It gives me below error in docker container logs
 level=error msg="plugin sql open error: plugin.Open(\"/kuiper/plugins/sources/Sql.so\"): Error loading shared library libresolv.so.2: No such file or directory (needed by /kuiper/plugins/sources/Sql.so)" file="native/manager.go:746"

Please help, is it the right way to work, not sure if this going to work with docker or not ?
Thanks

We have pre-built plugin in url endpoint https://packages.emqx.net/kuiper-plugins/{version}/{os}/{type}/sql_{arch}.zip, for example, https://packages.emqx.net/kuiper-plugins/1.10.0/alpine/sinks/sql_amd64.zip. You can install directly.
If you want to build from source code, check this https://ekuiper.org/docs/en/latest/extension/native/develop/plugins_tutorial.html#plugin-deployment

Hi @ngjaying, thanks for quick response, I tried it gives me below error in API response, Do I have to pass script parameter as well, like they are mandatory ?
If any documentation link, please share
{
    "error": 1000,
    "message": "sources plugins create command error: fail to install plugin: invalid zip file: expectFiles: 2, got<EMAIL_ADDRESS>zipFiles: [sql_test.go sql.json sql.go<EMAIL_ADDRESS>yamlFileChecked:false, soFileChecked:true"
}

Thanks

Which zip file did you use? Is you eKuiper version the same as the plugin (1.10.0 from the error message).

Version -> 1.14.0
UI gives me below link  -> https://packages.emqx.net/kuiper-plugins/1.14.0/alpine/sources/sql_amd64.zip
error on this link is
{
  "error": 1000,
  "message": "sources plugins create command error: fail to download file https://packages.emqx.net/kuiper-plugins/1.14.0/alpine/sources/sql_amd64.zip: cannot download the file with status: 403 Forbidden"
}

Version number now srarts with v. So use v1.14.0


Gem v0.1.0 Does Not Load

Getting a weird error loading faster_path in an existing Rails application.  Here's the back trace:
(trunk*) rails console
/Users/patrick/.rvm/gems/ruby-2.2.3/gems/ffi-1.9.10/lib/ffi/library.rb:133:in `block in ffi_lib': Could not open library '/Users/patrick/.rvm/gems/ruby-2.2.3/gems/faster_path-0.1.0/target/release/libfaster_path.dylib': dlopen(/Users/patrick/.rvm/gems/ruby-2.2.3/gems/faster_path-0.1.0/target/release/libfaster_path.dylib, 5): image not found (LoadError)
    from /Users/patrick/.rvm/gems/ruby-2.2.3/gems/ffi-1.9.10/lib/ffi/library.rb:100:in `map'
    from /Users/patrick/.rvm/gems/ruby-2.2.3/gems/ffi-1.9.10/lib/ffi/library.rb:100:in `ffi_lib'
    from /Users/patrick/.rvm/gems/ruby-2.2.3/gems/faster_path-0.1.0/lib/faster_path.rb:36:in `<module:Rust>'
    from /Users/patrick/.rvm/gems/ruby-2.2.3/gems/faster_path-0.1.0/lib/faster_path.rb:34:in `<module:FasterPath>'
    from /Users/patrick/.rvm/gems/ruby-2.2.3/gems/faster_path-0.1.0/lib/faster_path.rb:5:in `<top (required)>'
    from /Users/patrick/.rvm/gems/ruby-2.2.3/gems/bundler-1.11.2/lib/bundler/runtime.rb:77:in `require'
    from /Users/patrick/.rvm/gems/ruby-2.2.3/gems/bundler-1.11.2/lib/bundler/runtime.rb:77:in `block (2 levels) in require'
    from /Users/patrick/.rvm/gems/ruby-2.2.3/gems/bundler-1.11.2/lib/bundler/runtime.rb:72:in `each'
    from /Users/patrick/.rvm/gems/ruby-2.2.3/gems/bundler-1.11.2/lib/bundler/runtime.rb:72:in `block in require'
    from /Users/patrick/.rvm/gems/ruby-2.2.3/gems/bundler-1.11.2/lib/bundler/runtime.rb:61:in `each'
    from /Users/patrick/.rvm/gems/ruby-2.2.3/gems/bundler-1.11.2/lib/bundler/runtime.rb:61:in `require'
    from /Users/patrick/.rvm/gems/ruby-2.2.3/gems/bundler-1.11.2/lib/bundler.rb:99:in `require'
    from /Users/patrick/rails/test_app/config/application.rb:10:in `<top (required)>'
    from /Users/patrick/.rvm/gems/ruby-2.2.3/gems/spring-1.1.2/lib/spring/application.rb:82:in `require'
    from /Users/patrick/.rvm/gems/ruby-2.2.3/gems/spring-1.1.2/lib/spring/application.rb:82:in `preload'
    from /Users/patrick/.rvm/gems/ruby-2.2.3/gems/spring-1.1.2/lib/spring/application.rb:140:in `serve'
    from /Users/patrick/.rvm/gems/ruby-2.2.3/gems/spring-1.1.2/lib/spring/application.rb:128:in `block in run'
    from /Users/patrick/.rvm/gems/ruby-2.2.3/gems/spring-1.1.2/lib/spring/application.rb:122:in `loop'
    from /Users/patrick/.rvm/gems/ruby-2.2.3/gems/spring-1.1.2/lib/spring/application.rb:122:in `run'
    from /Users/patrick/.rvm/gems/ruby-2.2.3/gems/spring-1.1.2/lib/spring/application/boot.rb:18:in `<top (required)>'
    from /Users/patrick/.rvm/rubies/ruby-2.2.3/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
    from /Users/patrick/.rvm/rubies/ruby-2.2.3/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
    from -e:1:in `<main>'

I suspect it's an issue with the ffi version but I'm assuming the gemspec should address that rather than me mucking around with that in the application's Gemfile.

Yes.  I thought this issue was addressed in https://github.com/danielpclark/faster_path/issues/18 but it seems there's still an issue on Mac OS.

Do you have Rust installed?

Sure do.
~:bin (master) brew install rust
Warning: rust-1.9.0 already installed
~:bin (master) brew link rust
Warning: Already linked: /usr/local/Cellar/rust/1.9.0
~:bin (master) which rustc
/usr/local/bin/rustc

Can you got to /Users/patrick/.rvm/gems/ruby-2.2.3/gems/faster_path-0.1.0/ and run cargo build --release and tell me what's in the target/release directory?  Also see if it works after you do this.

That got the app to boot.  Here's what it looks like after running cargo build --release
:faster_path-0.1.0 tree target/release
target/release
├── build
├── deps
│   └── liblibc-38919d24e617a235.rlib
├── examples
├── libfaster_path.dylib
└── native

Alright.  I'm guessing Mac needs the libc dylib file.  That's currently being deleted in the clean up script.

Change line # 20 in the Rakefile to !f[/\.(?:so|dll|dylib|deps)\z/] and run rake clean_src.  Tell me if it still loads for you after that.

I'm going to take a chance and merge that update.

Gem 0.1.1 has this update.

I just wiped out 0.1.0 and installed 0.1.1 and it has the same issue. I don't actually see a target directory at all. Also when I try just installing it without bundler, it goes into the building native extensions thing and then immediately says the gem is installed. I'm assuming it's just not running the cargo build process as part of the install for some reason.

I have an idea.  Perhaps the relative path for the rake commands is different in Mac.  I'll try changing Dir.chdir('../../') to one that find the path relative to __FILE__

Alright release 0.1.2 runs the rake commands relative to the __FILE__ location.

0.1.2. and running cargo build --release fixed it for me

@harmdewit Thanks!
My hope is to get it where you don't have to type cargo build --release.  I have a rake task for that.  I might just need to remove my rake task that supposedly "tidies" up the compiled directory.  On Linux and Windows it works when using bundler.

I just tried 0.1.3 and the issue persists. Still doesn't want to compile when the gem installs. What is the best way to run the extconf.rb file with some debugging?

I can't seem to find it now, but there is a bundle method for invoking bundle commands in a clean context (no other bundle stuff loaded).  I've looked for it but can't find it.  Another way is to add a dummy rails directory to the test directory.
In the mean time you can do  your modifications and test it manually by changing the version number and running gem bundle faster_path.gemspec and then doing a local install with gem install faster_path-#.#.#.gem

#33 may have fixed this.  Please download from master, build and install the local gem and let me know.

I've just checked out master:

bundle
rake build_lib
rake build
rake install:local

I'm then able to open an IRB session in a new window, require FasterPath and call it's methods. So it looks as if it's working! That said, I'm going to keep poking about.
I have Rust nightly installed, Ruby 2.1.5p273 on OS X 10.11.5

Okay!  I've published this as gem 0.1.5 .  I'd like a confirmation or two on this working with a Mac in a bundle install and I'll close this issue.  Thanks for your feedback!

Same error for me with 0.1.5. Still doesn't seem to be creating the target/release directory when doing a clean install on the Mac.

I'll have some help on this this weekend.  I'm currently at the Ruby for Good event and there are a lot of Macs here.

Awesome. I've tried to do some debugging myself but the limiting factor seems to just be time. If I find anything meaningful I'll let you know.

I've had a similar issue on Circle and Heroku. Rust appears to be installed just fine:
ubuntu@box618:~$ which rustc
/usr/local/bin/rustc

And there are no errors running bundle, but as soon as faster_path is required, this error occurs:
LoadError: Could not open library '/home/ubuntu/myapp/vendor/bundle/ruby/2.3.0/gems/faster_path-0.1.7/target/release/libfaster_path.so': /home/ubuntu/myapp/vendor/bundle/ruby/2.3.0/gems/faster_path-0.1.7/target/release/libfaster_path.so: cannot open shared object file: No such file or directory
/home/ubuntu/myapp/vendor/bundle/ruby/2.3.0/gems/ffi-1.9.10/lib/ffi/library.rb:133:in `block in ffi_lib'
/home/ubuntu/myapp/vendor/bundle/ruby/2.3.0/gems/ffi-1.9.10/lib/ffi/library.rb:100:in `map'
/home/ubuntu/myapp/vendor/bundle/ruby/2.3.0/gems/ffi-1.9.10/lib/ffi/library.rb:100:in `ffi_lib'
/home/ubuntu/myapp/vendor/bundle/ruby/2.3.0/gems/faster_path-0.1.7/lib/faster_path.rb:50:in `<module:Rust>'
/home/ubuntu/myapp/vendor/bundle/ruby/2.3.0/gems/faster_path-0.1.7/lib/faster_path.rb:48:in `<module:FasterPath>'
/home/ubuntu/myapp/vendor/bundle/ruby/2.3.0/gems/faster_path-0.1.7/lib/faster_path.rb:5:in `<top (required)>'
/home/ubuntu/.rvm/gems/ruby-2.3.1/gems/bundler-1.12.5/lib/bundler/runtime.rb:86:in `require'

Oddly, I had no issues installing/running on my Mac.

I think Bundler swallows up the error output that is designed in the Rakefile.  There are some alternative ways to go about using the extconf.rb extension builder which may be explored to fix this.  Apparently a Rakefile can be used instead of a Makefile.  I haven't found much on this as the documentation largely focusses on C code builds.  But using a Rakefile instead of calling Rake tasks from extconf.rb might be a solution.

Getting same error. But I suppose it is due the fact that there is no rust on my system. Are you planning to produce gems with prebuilt binaries?

Yes.  I'll be adding Thermite soon.  I need to figure out how to build for specific architectures and then sign it with something like gpg.

This commit may resolve this issue for many https://github.com/danielpclark/faster_path/commit/69ea7df970c7bc7dc1d2dae45004fb95051c8fdc
You could try to set your gem to pull directly from the master branch.

I've written an AssetResolution module that will build the library on require if it wasn't built during gem install.  If that fails it will error out with a very clear message as to why.
Also I've added OSX testing with TravisCI and it passes.  So I'm closing this issue.


Adding ps-hosts-not-found alarm

@petya-vasileva
{
"category": "Networking",
"subcategory": "Sites",
"event": "hosts not found",
"description": "This code checks whether the throughput/trace/latency data for expected hosts are found in the Elasticsearch. It is executed daily and takes a list of expected hosts as input. The function queries Elasticsearch for throughput/trace/latency data and compares unique hosts by each test group with the list of expected hosts. It reports sites and corresponding hosts that are mentioned in the configurations but can not be found in Elasticsearch. This process is crucial for ensuring that all the relevant information about hosts' testing is saved correctly in the database. The code can be found here: [..].",
"template": "Hosts expected but not found in the Elasticsearch\n%{site}\n%{hosts}"
}

We need to use Memcached to do the host->site mapping instead of PSConfig. For example:
from pymemcache.client import base client = base.Client(('memcached.collectors', 11211)) netsite = client.get('rcsite_psmsu02.aglt2.org') print(netsite)


heroku installation error

When trying to run mix admin.install on heroku this error shows up:
remote:        * creating css files
remote:        * creating js files
remote:        ** (File.Error) could not read file /tmp/build_de9a0426198c91c9e5245f5e2a4843d9/deps/ex_admin/web/static/vendor/active_admin/application.js.js: no such file or directory
remote:            (elixir) lib/file.ex:244: File.read!/1
remote:            lib/mix/tasks/admin.install.ex:229: anonymous fn/3 in Mix.Tasks.Admin.Install.read_active_admin_js/3
remote:            (elixir) lib/enum.ex:1473: Enum."-reduce/3-lists^foldl/2-0-"/3
remote:            lib/mix/tasks/admin.install.ex:220: Mix.Tasks.Admin.Install.do_active_admin_js/1
remote:            lib/mix/tasks/admin.install.ex:63: Mix.Tasks.Admin.Install.do_assets/1
remote:            lib/mix/tasks/admin.install.ex:43: Mix.Tasks.Admin.Install.do_install/1
remote:            (mix) lib/mix/cli.ex:58: Mix.CLI.run_task/2

It does not really mater how to run it:

Via heroku run ...
Via buildback's compile (as shown in error)
Via heroku run bash and manually trying to get it to work

What did I miss?

I'm sorry, but I don't have very much experience with heroku. But it looks like your trying to run mix admin.install on heroku?

Yes, I am running this command when deploying.  Here's my workflow:

priv/static is ignored
When deploying I run brunch build --production && phoenix digest via heroku-buildpack-phoenix-static
Next step I was trying to run mix admin.install --no-config --no-route --no-dashboard Since I don't want to concat admin files into my static assets.

I tried to run it as a buildpack step. Before and after brunch build. I also have tried to do it with .travis.yml: example. No luck either.
Maybe there's another workflow?

What about running mix admin.install locally, copying ex_admin's asset into your web/assets under vendor or ex_admin (and version them - that's what I do) and the let the build step simply copy them to priv/static (I'm also doing this with the buildpack-phoenix-static)

I committed a change into master last week. admin.install now installs the assets into web/static and updates your brunch-config.js file with instructions. on how to update it. This should resolve your issue.

@sobolevn I believe this should be resolved with the support for brunch assets. I have not heard back from you so I'm assuming this resolved your issue. Closing the issue. Please reopen if the brunch assets does not resolve your issue.

Sorry for the long response: just didn't have the time to work on this project lately.
@erikmueller this will work, no doubts. I think I will use it as a workaround.
@smpallen99 That's a good job! But actually I don't like the idea of modifying brunch.js since it may break things unintentionally. Furthermore, projects can use gulp, webpack or any other tool.
Maybe it would be a better idea to maintain these static files as a npm package? Project is totally growing into a separate github-organization ;)

That's how phoenix itself manages to solve the same problem:
package.json:
{
  "name": "your_app_name",
  "devDependencies": {
    "phoenix": "file:deps/phoenix",
    "phoenix_html": "file:deps/phoenix_html"
  }
}


Add X509Certificate2 to InitializeClient

SimpleTcpClient did accept X509Certificate, but when it was being initialized it wasn't being passed on to the InitializeClient method.
Now it checks if there is a certificate and if so, puts it into the collection, skipping the creation.

Many thanks @tautvilis - just published.
NuGet: https://www.nuget.org/packages/SuperSimpleTcp/<IP_ADDRESS>
Commit: https://github.com/jchristn/SuperSimpleTcp/commit/cb87c21de2cadbbc6e97642ad9dc2774443bc79a


[Feature] Dashboard for PhrasesTerm

Feature

Dashboard for PhrasesTerm

Why

Must have an interface to create the link between Phrase and Term

How

Dashboard as usual
A search function that allows search Term in Phrase

Definition of Done

[x] Dashboard
[ ] Suggestion function

Reference

" A search function that allows search Term in Phrase ? "
"[] Suggestion function "
--> I still don't understand this.
there's more :

How to create PhrasesTerms ?
What is input data?
because when created, two objects must exist.

@dutavi good question.
The model PhrasesTerm is called join-table in the relationship has and belongs to many (HABTM), so when you want to create a record of a join-table, you have to create 2 objects which it is belonged to beforehand. You can see more at https://guides.rubyonrails.org/association_basics.html#has-and-belongs-to-many-association-reference
Anyway, I will do this issue, so you can focus more on the writing test.


FIX: Tooltip bounce

If you set preferredPosition to right and some bigger text into content the component will shake little bit when you hover onto the tooltip itself.LiveURL: https://orbit-components-fix-tooltip-bounce.surge.sh

Closed in behalf of #1181


Modernize code

This PR adds several features to modernize and speed-up console-panel

use ES imports
bundle code with Rollup (reduces activation time by ~40%)
defer activation
lint code with ESLint
lint styles with StyleLint

If these changes are welcome, I'm willing to update the code further in subsequent PRs. The most important change I have in mind is migrating from atom-space-pen-views to etch, maybe also use TypeScript instead (let me know what you think).

@suda due to the general inactivity of this repository, let me bump this PR 😉

@suda By the way, I have noticed the same deactivation fix is necessary as in tool-bar. I will submit a second PR, maybe wait with a new release!


Fix lint in superset/db_engine_spec

CATEGORY
Choose one

[ ] Bug Fix
[ ] Enhancement (new features, refinement)
[X] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY
The db_engine_spec folder was largely un-linted by pylint, due to the presence of the # pylint: disable=C,R,W comment in most of the files. This method of skipping lint checks will hide all pylint failures introduced into the files. This PR removes those lines, fixes a number of pylint errors, and uses a more targeted disable approach for issues that would require larger refactors to resolve. Using this approach for disabling lint should highlight new problems introduced in future PRs and creates a specific list of items to clean up down the road.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN

Verify tests pass
Verify superset runs as expected locally (in progress)

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[X] Removes existing feature or API

Explanation: there was a function in presto.py that I believe was un-referenced: _consolidate_array_data_into_data.
REVIEWERS

❤

Yes, it appears so - I think I just need to update a couple tests.

OK, CI is green - sorry for the many commits. Let me know if you'd like me to squash before merge.

We force "Squash and merge" on this repo, so every PR gets auto-squashed and we have a 1-to-1 between commits in master and PRs.


Basic test case: no-fmf scenario with tests

This test case is triggered automatically by our validation script.
- job: copr_build
  trigger: pull_request
  targets:
  - fedora-all

- job: tests
  trigger: pull_request
  targets:
  - fedora-all

(No fmf files.)

/packit build


Add function to create Ephem from Orbit

Addresses #1009
Added a function to create an Ephem object from an Orbit object.

Propagates the specified orbit using the epochs argument.
Samples the orbit with interval points same as the size of epochs.
Uses the returned coordinates to create an Ephem object.
Checks for scalar epochs.
Not added corresponding tests.

This looks really good! Before I do a proper review, please rebase & force push on top of current master, I merged a couple of fixes for the Continuous Integration

This looks really good! Before I do a proper review, please rebase & force push on top of current master, I merged a couple of fixes for the Continuous Integration

This looks really good! Before I do a proper review, please rebase & force push on top of current master, I merged a couple of fixes for the Continuous Integration

Thanks for your suggestion on using twobody.propagate. I have done the rebasing and force pushing. Please let me know any improvements/suggestions on the tests that can be done and also we would need to fix the 2 failing checks.
Thanks!

This looks really good! Before I do a proper review, please rebase & force push on top of current master, I merged a couple of fixes for the Continuous Integration

Thanks for your suggestion on using twobody.propagate. I have done the rebasing and force pushing. Please let me know any improvements/suggestions on the tests that can be done and also we would need to fix the 2 failing checks.
Thanks!

Thanks for the reformatting command! As a result, the quality checks have passed!

Thanks for the reformatting command! As a result, the quality checks have passed!

Merged! Thanks @Yash-10 !

Merged! Thanks @Yash-10 !

Thank you for merging!! Learning a lot of things and am having a great experience.

Thank you for merging!! Learning a lot of things and am having a great experience.


Need to update roots.pem file

As suggested by @eugeneo here I'm creating this issue to discuss the update of roots.pem (sorry if this is not the place to discuss this, I didn't find anywhere else to do it). This file is already more than 3 years old, and because of this doesn't contains very important root certificates such as the DigiCert TLS RSA4096 Root G5 which leads servers with certificates signed by this certificate to fail the handshake connection with grpc clients (when using default grpc runtime truststore).
With that said it is very important to update this roots.pem file to avoid these kind of error to happen. I've already created the PR #37600 that do this by following https://github.com/grpc/grpc/blob/master/etc/README.md and https://github.com/grpc/grpc/pull/27539 but a new PR with a older contributor can be created without any problems.

Hello @matheussrsap, thank you for flagging this!
It definitely will require some time for us to check everything, in the meantime I want to highlight that "default grpc runtime truststore" is one of the options to use - you can also configure non-default truststores to load certs relevant to your env.

Hi @erm-g thanks for the quick answer! Unfortunately for our use case we can't set a custom truststore, this happens because the connection is not managed by us but instead by a third-party library that doesn't offer support to set a custom truststore and therefore uses the default one which leads to this error.
Because of this, the solution we've found was to update the default root certificates to a more updated version, this can solve not only our problem but also the problem of any user that uses the default grpc runtime truststore for any reason.


[BUG] Deployments in AIOps watchlist disappear

Becomes very inconvenient when an existing watchlist has already been trained

I think the reason the selection is disappearing is because you click on the row instead of the checkbox.
That's how the table works in all of rancher so I don't intend to fix it. You can use ctrl/shift+row click to select multiple.


Font color on blink

Is there a setting, or a way I can set the characters font color to be black when the cursor is shown. it make it difficult to read when the color of the font is close to that of the cursor

Unfortunately, no, there isn't any way to do this that I know of


[AKS] Support specify format when requesting clusterUser credential

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

This PR is the same as the one in Azure CLI: https://github.com/Azure/azure-cli/pull/21383

AKS

Close and reopen to rerun CI.


change validations.py

Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[x] Tests pass
[x] Appropriate changes to README are included in PR

merge


Set variables for keystone ports

Sometimes non-standard ports like 35357 and 5000 are blocked on the
firewall. This patch creates keystone_admin_port and keystone_user_port
variables with default values of 35357 and 5000 to permit the user to
deploy keystone on another port.

+1 lgtm


Feedback changes round 2

Add a default value to measurement: 'pieces (stuks)', which is cleared if one begins typing
Hide quantity measurement if measurement is not filled in
Add + in the drawer headers as a shortcut to add product (investigate if possible)
Pick a color for categories
Drawers should start uncollapsed
'Add Another' checkbox next to Add in Add Product form

Won't do the default value: if user wants to quickly add items without a quantity, it will always be added with measurement 'pieces' which will be incorrect


Carthage build fails on latest release (2.0.2)

When trying to update to the latest release, after running
carthage update Leanplum-iOS-SDK
The build fails with the following error message:
*** Skipped installing Leanplum-iOS-SDK.framework binary due to the error:                                                                                │@@ -7,3 +7,10 @@
        "Failed to read file or folder at /private/var/folders/v9/b69j6j112xjbggkzm4xpkm3h0000gn/T/carthage-archive.ghwvVH/__MACOSX/Leanplum.framework: Error D│ //
omain=com.antitypical.Result Code=0 "the DTSDKName key in its plist file is missing" UserInfo={com.antitypical.Result.file=/tmp/carthage-20170710-56241-9g56uj/│
Source/CarthageKit/Project.swift, com.antitypical.Result.function=readFailed, com.antitypical.Result.line=1100, NSLocalizedDescription=the DTSDKName key in its│ import Foundation
 plist file is missing}"                                                                                │+
*** Checking out Leanplum-iOS-SDK at "2.0.2"                                                                                │+class Leanplum {
*** xcodebuild output can be found in /var/folders/v9/b69j6j112xjbggkzm4xpkm3h0000gn/T/carthage-xcodebuild.x4OSkr.log                                          │+
*** Skipped building Leanplum-iOS-SDK due to the error:                                                                                │+  static func bootstrap() {
Dependency "Leanplum-iOS-SDK" has no shared framework schemes                                                                                │+  }

Version 2.0.1 and below works as expected.
Cheers,
Rog

Thats weird. I haven't tried it myself yet, but it seems to me that Carthage is looking for an xcschme .xcodeproj/xcshareddata/xcschemes...
What's odd is that it should just be using the framework file instead....
Similar issues:

https://github.com/Carthage/Carthage/issues/1056
https://github.com/Carthage/Carthage/issues/1109

We will need to dig deeper into this...

I am able to reproduce the issue, but I have no clue what's going on. I've opened this ticket on the Carthage repo, to see if there's anything we can do to investigate the issue more deeply and find the root cause: https://github.com/Carthage/Carthage/issues/2084

I'm not sure either but it looks like it might be an issue with the Result dependency you guys currently use.
Perhaps see if the latest Leanplum build updated that dependency and go from there?
Here's the repo for Result https://github.com/antitypical/Result

Could you please check this?
https://github.com/Carthage/Carthage/issues/1776#issuecomment-290451271

I checked it myself and it doesn't seem to be the case.

This is actually the case:
$ unzip -l Leanplum.framework.zip
Archive:  Leanplum.framework.zip
  Length      Date    Time    Name
---------  ---------- -----   ----
        0  07-21-2017 03:21   Leanplum.framework/
     6148  07-21-2017 03:21   Leanplum.framework/.DS_Store
        0  07-21-2017 03:21   __MACOSX/
        0  07-21-2017 03:21   __MACOSX/Leanplum.framework/
      120  07-21-2017 03:21   __MACOSX/Leanplum.framework/._.DS_Store
        0  07-19-2017 06:02   Leanplum.framework/Headers/
    35085  07-19-2017 06:02   Leanplum.framework/Headers/Leanplum.h
        0  07-21-2017 03:21   __MACOSX/Leanplum.framework/Headers/
      222  07-19-2017 06:02   __MACOSX/Leanplum.framework/Headers/._Leanplum.h
     4958  07-19-2017 06:02   Leanplum.framework/Headers/LPInbox.h
      222  07-19-2017 06:02   __MACOSX/Leanplum.framework/Headers/._LPInbox.h
      222  07-19-2017 06:02   __MACOSX/Leanplum.framework/._Headers
      737  07-19-2017 06:02   Leanplum.framework/Info.plist
      222  07-19-2017 06:02   __MACOSX/Leanplum.framework/._Info.plist
  9923080  07-19-2017 06:02   Leanplum.framework/Leanplum
      222  07-19-2017 06:02   __MACOSX/Leanplum.framework/._Leanplum
        0  07-21-2017 03:21   Leanplum.framework/Modules/
       97  07-21-2017 03:21   Leanplum.framework/Modules/module.modulemap
        0  07-21-2017 03:21   __MACOSX/Leanplum.framework/Modules/
      328  07-21-2017 03:21   __MACOSX/Leanplum.framework/Modules/._module.modulemap
      222  07-21-2017 03:21   __MACOSX/Leanplum.framework/._Modules
      222  07-21-2017 03:21   __MACOSX/._Leanplum.framework
---------                     -------
  9972107                     22 files

Thanks @ikesyo not sure why I didn’t notice it when I tried.

Thanks, I fixed it manually... Verified carthage update works again...
I modified our build scripts: zip -r9 "Leanplum-$IOS_VERSION_STRING.zip" ./* -x ./*.zip -x "*.DS_Store" -x "__MACOSX/" -x "__MACOSX/*"
This should prevent it from happening again...

Yup can confirm this is fixed for this 2.0.2. Thanks all!


feat: ensure notebook endpoints do their job

Describe your changes
This PR ensure that the notebook API part correctly answers and acts on the requests sent to make it on par with the renku- notebook implementation.
Issue ticket number and link
Part of #303

Squash and merge please when you merge this.


Microsoft Defender Antivirus OR Microsoft Defender for Endpoint

Microsoft Defender Antivirus and Microsoft Defender for Endpoint are 2 separate products as mentioned here:
https://docs.microsoft.com/en-us/microsoft-365/security/defender-endpoint/why-use-microsoft-defender-antivirus?view=o365-worldwide
This article says, Applies to: Microsoft Defender for Endpoint
BUT
Isn't it actually an article about: Microsoft Defender Antivirus
The "Applies to" section should be corrected
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f4449fe2-eb1b-0c55-cdb1-c8ff00681204
Version Independent ID: e0c1d23c-9dbd-85df-9c97-fa551c09f91e
Content: Manage Windows Defender in your business
Content Source: microsoft-365/security/defender-endpoint/configuration-management-reference-microsoft-defender-antivirus.md
Product: m365-security
Technology: mde
GitHub Login: @denisebmsft
Microsoft Alias: deniseb

@ssmiller60 Thank you for your feedback. We have added Microsoft defender antivirus to the applied to section via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/5557
Thanks
Sri

@msbemba Thank you very much for the contribution and updating the documentation with PR. @ssmiller60 Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


MQTT user authentication not supported

The MQTT client doesn't support user authentication. It's mentioned in the camera configuration that if your MQTT Broker requires user/pass authentication, you can set it up on the camera, which I did and verified the camera can connect. But the homebridge plugin doesn't currently support authentication.
I edited client.js to pass the info through to the client URL, but did so in a crude way that probably wouldn't stand up to the rigors of general consumption. It'd be awesome to get in properly supported!

MQTT MOSQUITTOOPTS need --cafile , --cafile, --cert

hey @bdonohoe how did you edited client.js? I found the file but I don't know what to edit.

Found it by my self

Hi @ScharV or @bdonohoe can you help me? Where is the client.js file stored and what do I have to edit? I am running Mosquitto on my linux server in at home as central server. I am using a raspberry PI as streaming homebridge client. On the Linux server I have running Home Assistant but that doesn's support streaming video to homekit.

Hey @conradhagemans sorry for my delayed reply....im actually driving with my car i will answer your question asap in the following hour

Take your time and drive carefully.
Thanks.

@conradhagemans
in my case with Homebridge i found the client.js file here:
/usr/local/lib/node_modules/homebridge-dafang/node_modules/mqtt/lib/client.js
————————————————————
Then you have to add it at the first Block like this:
...
}
var defaultConnectOptions = {
keepalive: 60,
reschedulePings: true,
protocolId: 'MQTT',
protocolVersion: 4,
reconnectPeriod: 1000,
connectTimeout: 30 * 1000,
username: "MyCam",
password: "MySecretPassword",
clean: true,
resubscribe: true
}
...
————————————————————
Username and password fields aren‘t there in original.
Hope that helps you otherwise feel free to contact me.

@ScharV thank you for the quick response. I will try it out and post an update later tonight.

Yes!! It works. Bridge added to my HomeKit app and camera added. Now error with FFMpeg. I think I have to recompile it on my raspberry. @ScharV once more thank you.


issues written in any non english languages

A lot of issues are written in Chinese, I dont think it should be "acceptable" as it is not the best choice to spread knowledge, discuss the subject, contribute or help each others

@zigomir Maybe we should encourage people to speak in English by including a message in the issue template telling them that they'd get faster feedback if they do so


Show error message when app is offline?

Coming out of a code review with @ericboucher, we were thinking about what should happen if the user loses internet access. We can show an error modal, or decide that it's an edge case we don't have to worry about.

I see- Most websites don't do anything and let the browsers tell the user that they can't find internet, right? I don't think we need to do anything special.
The thing we might want to consider is how to use cookies or local storage to prevent users' inputs/analyses settings from being lost.
I don't think this is that important for a demo/prototype, but something we'll likely consider down the road if/when we have real users. :)

SGTM


WIP: Gamification touch ups

Changes:

Add more tests for the programming app (models and views) and users app (views)
Add newline at EOF of icons8-points.svg
Remove outdated code from tests
Fix travis tests
Show toasts for 5 seconds instead of 3

To do:

[x] Make toasts showing the points/badges awarded sticky
Potentially show badge icon with the earned badge toast Not implementing
Try get test coverage back up to what it was Test coverage is broken, see notes.

Notes:

~Running ./dev test_coverage currently breaks - giving the error: KeyError: 'django_coverage_plugin.DjangoTemplatePlugin'. This is happening on all branches after ./dev test_suite is run.~

Don't mind me just tagging #207


paged results of plans does not work on /super_admin/users/:user_id/edit

Please complete the following fields as applicable:
What version of the DMPRoadmap code are you running? (e.g. v2.2.0)
versions v3.0.2 till v3.0.4
Expected behaviour:
Actual behaviour:
When you click either view all, a page number, or whatever you'll get a blank
list of plans.
Steps to reproduce:

go the admin > users page
click on a user with more than 10 plans (so that paging of plans applicable)
click on "next" below the list of plans

Reason: controller DOES return the correct results, but in the wrong format ("html")

@johnpinto1 this might be related to #675 in the DCC Roadmap fork?

@raycarrick-ed & @briri .I followed @briri comment https:/ github.com/DigitalCurationCentre/DMPonline-Service/issues/675#issuecomment-988931121  and got it to work - ALMOST. I moved issue to here as this is actually a Roadmap wide issue.
The View All for a User's Plans via Org Admin fails for users with plans on more than one page for the following reason: The links for ** View All** and Last both try to get pages that are outside the range of pages.
So in my test case.

If I now choose a user with more than one page of plans and press View All  the Plans return a blank fragment.
Similarly, if I press fLast for plans I get the same issue.

The reason for this is that the View All and Last are looking for 6 pages of plan data when there are only 2 pages.
I say this with confidence is when I press  Page 3 link I get a blank Plans fragment as when I press the ** View All** and Last links

Any ideas how we can insure the pages that appear as links for Plans in Org Admin user's pagination for Plans  can work like in other places.
Note If I do a search for Plans the pagination still shows more pages than exist. However, if I go to second page the number of pages is corrected. Bad news is View all search results fails here too.

As this a Roadmap issue as well as a DCC issue I have linked to a comment https://github.com/DigitalCurationCentre/DMPonline-Service/issues/675#issuecomment-990906539

Please unsubscribe me from your mailing list
On Mon, Nov 22, 2021, 11:56 AM Nicolas Franck @.***>
wrote:

Please complete the following fields as applicable:
What version of the DMPRoadmap code are you running? (e.g. v2.2.0)
versions v3.0.2 till v3.0.4
Expected behaviour:
Actual behaviour:
When you click either view all, a page number, or whatever you'll get a
blank
list of plans.
Steps to reproduce:

go the admin > users page
click on a user with more than 10 plans (so that paging of plans
applicable)
click on "next" below the list of plans

Reason: controller DOES return the correct results, but in the wrong
format ("html")
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/DMPRoadmap/roadmap/issues/3069, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSENX64H24F52Y532QKERDUNIASHANCNFSM5IQNPRUA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Thanks for helpful comment @ojsmaina . I think you need to unsubscribe from the email yourself.

@ojsmaina instructions for how to unsubscribe from this repository can be found here: https://docs.github.com/en/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions

This was in the last release. We should check to make sure it's addressed. @raycarrick-ed @briri


Integrate latest ledger dependencies

LGTM

I think the ProtocolParameter related improvements that are not directly related to ledger changes should be in a separate PR.

They are all related to the ledger changes, so they can't be extracted into a separate PR. PParams and PParamsUpdate have been completely redone in the latest version of ledger. Here is the relevant PR: https://github.com/input-output-hk/cardano-ledger/pull/3242

I'd prefer to not use lenses if we don't have to.

We have to. Every single field in almost every ledger type family is now to be manipulated by a dedicated lens.

We're not updating the fields of deeply nested structures and I think the lenses further obfuscate the code vs record accessors which immediately give me information/context about the data structure I am updating.

In the matter of fact we are. This is how you'd add inputs to  a transaction:
> let addInputs tx ins = tx & bodyTxL . inputsTxBodyL <>~ ins
> :t addInputs
addInputs
  :: EraTx era => Tx era -> Set (TxIn (EraCrypto era)) -> Tx era

It is important to note that this function here will work for all eras. This is the power of lenses from ledger, not only that they allow to modify nested structure.
Moreover. Both Tx and TxBody are nested structures themselves for every era. We historically provided pattern synonyms with record fields, that allowed us to pretend like they are not nested structures. But his is a maintenance burden and it doe snot help us with avoiding duplication. Lenses do. For example, I'd love to see an alternative approach that will let you compute a total output of any transaction in any era:
> let txTotalAda tx = fold $ fmap (\txOut -> txOut ^. coinTxOutL) (tx ^. bodyTxL . outputsTxBodyL)
> :t txTotalAda
txTotalAda :: EraTx era => Tx era -> Coin

Same applies to PParams, for example here is a lens that will let you set and get protocol version from PParams for any era:
> :t ppProtocolVersionL
ppProtocolVersionL :: EraPParams era => Lens' (PParams era) ProtVer

If a field was added at a later era then it will guarded by a specific type class that allows using the lens from specific era onwards, eg ppCostModelsL can be used in ALonzo, Babbage..., but not with PParams from eras prior to Alonzo:
> :t ppCostModelsL
ppCostModelsL
  :: AlonzoEraPParams era => Lens' (PParams era) CostModels

Before that we were using with PParams the hacky getField @"_protocolVersion" pp approach, but it was too ugly and limited in functionality. It only allowed for accessing, not modifying. And with respect to other types, like Tx, TxBody, TxOut we had no way to deal in an era agnostic fashion.
Long story short, lenses are the designated way to deal with ledger types that can change across eras.

There are many good refactors here +1 . We should definitely organize a call next week so you can take us through the changes.

Thank you. Sounds good with me.

FWIW, I think lenses are way easier than type families provided the lens API is discoverable.
In your example, how easy is it to find all the accessors for the expression:tx ^. bodyTxL?
For example you have outputsTxBodyL.  What other fields are there?

In your example, how easy is it to find all the accessors for the expression: tx ^. bodyTxL?
For example you have outputsTxBodyL. What other fields are there?

Those are great questions! We have a proper cardano-ledger-api in the works. For now we export all of the lenses, but there will be a lot more exported later with proper documentation and examples. For instance here are all the lenses  that are available for TxBody: https://github.com/input-output-hk/cardano-ledger/blob/302e46f4d83e5ad8dafec68130ea5b3c07942f52/libs/cardano-ledger-api/src/Cardano/Ledger/Api/Tx/Body.hs#L12-L56


email_field id doesn't propagate to label

If you use a custom id with email_field the label's "for" is still the default:
= bootstrap_form_for :purchase do |f|
  = f.email_field :email, id: "my_custom_id"

result:

  Email
  <input id="my_custom_id" class="form-control" type="email" name="purchase[email]">

expected:

  Email
  <input id="my_custom_id" class="form-control" type="email" name="purchase[email]">

I wrote fix for this bug #221


snippets marks remain active after completion is done

I think when a snippet has multiple marks to iterate through via tab, they remain active even after the completion is done. This causes the editor, when in insert mode, to go the mark when tab is pressed instead of inserting the character, at least until all of the previous completions have been exhausted.
The expected behavior of course would be to clear those marks so that post completion there's no need to tab through them.

Closing as this belongs in nvim-cmp I believe.


Crashes after Gitea is configured

Gitea version (or commit ref): latest and 1.0
Git version: What ever is in the Docker image
Operating system: Debian Buster with Docker (version 19.03.8, build afacb8b7f0)
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Description
Using the instructions found on the website I've make a Mysql server in Docker and setup using the database preparation instructions. I could guarantee that the Docker Mysql server works because I could connect and control the server using Mysql Workbench. I could also attest that the creditial and permissions for the
I've tried many times with different settings. Also dumped the entire Database and persistant files of Gitea between test runs. I would repeat the same problematic result everytime.
I suspect it might have to do with the fact I am using Portainer (not sure what's the difference). Not sure...
Before, I've tried using Docker Compose I ran into another problem that is why I didn't use that.
To replicate my problem:

Make a Mysql DB, pretty much default. connect to same network

Gitea using settings below, go to gitea's webpage, go to login

Enter DB info and save

Saves the info, reloads and crashes. Crashes everytime afterwards as well.

Screenshots
Gitea Docker
Docker Settings

Docker logs, shows Gitea terminating for no reason... repeatedly.

Mysql Docker

is there anything in /dat/gitea/log? Can Gitea even write to /data/gitea/log?

Sorry, clicked the wrong button haha.
Anyways, should have included the log.
So, yes that path could be read. The log file is too big to post entirely but the last few lines mentioned what went wrong...
2020/04/18 22:06:39 routers/init.go:99:GlobalInit() [I] ORM engine initialization successful!
2020/04/18 22:06:39 ...orm/dialect_mysql.go:431:GetTables() [I] [SQL] SELECT TABLE_NAME, ENGINE, TABLE_ROWS, AUTO_INCREMENT, TABLE_COMMENT from INFORMATION_SCHEMA.TABLES WHERE TABLE_SCHEMA=? AND (ENGINE='MyISAM' OR ENGINE = 'InnoDB' OR ENGINE = 'TokuDB') [giteadb]
2020/04/18 22:06:39 ...orm/dialect_mysql.go:320:GetColumns() [I] [SQL] SELECT COLUMN_NAME, IS_NULLABLE, COLUMN_DEFAULT, COLUMN_TYPE, COLUMN_KEY, EXTRA,COLUMN_COMMENT FROM INFORMATION_SCHEMA.COLUMNS WHERE TABLE_SCHEMA = ? AND TABLE_NAME = ? [giteadb oauth2_session]
2020/04/18 22:06:39 ...orm/dialect_mysql.go:460:GetIndexes() [I] [SQL] SELECT INDEX_NAME, NON_UNIQUE, COLUMN_NAME FROM INFORMATION_SCHEMA.STATISTICS WHERE TABLE_SCHEMA = ?  ORDER BY login_source_id ASC, external_id ASC LIMIT 100 []interface {}{"github"} - took: 1.264932ms
2020/04/18 22:06:39 .../xorm/session_raw.go:78:queryRows() [I] [SQL] SELECT repo.id FROM repository repo WHERE repo.num_closed_issues!=(SELECT COUNT() FROM issue WHERE repo_id=repo.id AND is_closed=? AND is_pull=?) []interface {}{true, false} - took: 683.466Âµs
2020/04/18 22:06:39 .../xorm/session_raw.go:78:queryRows() [I] [SQL] SELECT repo.id FROM repository repo WHERE repo.num_closed_pulls!=(SELECT COUNT() FROM issue WHERE repo_id=repo.id AND is_closed=? AND is_pull=?) []interface {}{true, true} - took: 508.8Âµs
2020/04/18 22:06:39 .../xorm/session_raw.go:78:queryRows() [I] [SQL] SELECT repo.id FROM repository repo WHERE repo.num_forks!=(SELECT COUNT() FROM repository WHERE fork_id=repo.id) - took: 290.683Âµs
2020/04/18 22:06:39 ...er/issues/indexer.go:142:func2() [I] PID 15: Initializing Issue Indexer: bleve
2020/04/18 22:06:39 .../xorm/session_raw.go:78:queryRows() [I] [SQL] SELECT pull_request.id FROM pull_request WHERE (status=?) []interface {}{1} - took: 521.433Âµs
2020/04/18 22:06:39 .../xorm/session_raw.go:78:queryRows() [I] [SQL] SELECT id, repo_id, hook_id, uuid, type, url, signature, payload_content, http_method, content_type, event_type, is_ssl, is_delivered, delivered, is_succeed, request_content, response_content FROM hook_task WHERE (is_delivered=?) []interface {}{false} - took: 499.954Âµs
2020/04/18 22:06:40 ...er/issues/indexer.go:150:func2() [F] Unable to initialize Bleve Issue Indexer: no such device

Well that's the hint. You need to set your indexer configuration correctly, in particular the ISSUE_INDEXER_PATH setting in [indexer]. See https://docs.gitea.io/en-us/config-cheat-sheet/#indexer-indexer

Hi @zeripath, I did some trial and error before resorting to here again.
I've tried a few other settings using the link you sent too. Still doesn't work... because of other problems (which I won't mentioned since it's prob the config)
So far, the Docker does NOT have any settings that were changed, so everything in [indexer] should be default.
As for the ISSUE_INDEXER_PATH setting, I couldn't find any other documentation or info on docs.gitea.io for what to set this to. The official documentation doesn't seem to talk about setting this particular setting.
So what exactly should I set for this anyways?

Could you paste your app.ini (suitably sanitized please.)
You would need to add a [indexer] section to your app.ini and within that [indexer] section set ISSUE_INDEXER_PATH to something appropriate.
However, it would be useful to work out what the default path is - as clearly this is not correct for the docker.

Also what version of Gitea are you using?

Hi @zeripath. I have used both version 1.0 and whatever is at "latest" before. Both have the same problem, errors and symptoms.
I've zipped app.ini as it is right now. Haven't changed anything included the pass which isn't salted... whatever.
I basically haven't changed anything different from whatever was in the Docker Documentation. Nothing really that would cause problems. Other than the fact that I am using regular Docker (in portainer) rather than Docker Compose. Shouldn't make a difference really.
As for the ISSUE_INDEXER_PATH setting, it is the default setting.
Mine:

Docs:

app.zip

Just checked the persistent data from the Docker.
/data which mounted to a host file
I found the issues.bleve which is a folder.
Just writing this just incase this is important
Btw, gitea runs as the user "tmod" fyi.
Permissions:

@Nathan13888 you've said:

I have used both version 1.0 and whatever is at "latest" before. Both have the same problem, errors and symptoms.

Gitea 1.0 is a very old version, "and whatever is at latest" is not very descriptive. Please let us know your current version of Gitea, which you can obtain by running:
/path/to/gitea --version

from inside your docker instance.

@guillep2k Thanks for tuning in.
What I mean is that I tried both version 1.0 and the version using the tag "latest". I only tried 1.0 because "latest" wasn't working for me (never did, always crashed after setup).
Anyways, this is what I found: Gitea version 1.12.0+dev-201-g50475fff0 built with GNU Make 4.2.1, go1.14.2 : bindata, sqlite, sqlite_unlock_notify

use at least 1.11.x version ... migration from v1.0 has ben droped in v1.12!
and for the error: just try to delete the indexer files

Hey all, I've deleted everything again to start from scratch. I've recreated a new Docker container using the same 1.12 version of Gitea.
The settings are the same as the ones in my first post.
Upon creation, I open the install page and enter the database password and submit the info.
Right afterwards, when I reload my browser, the website is gone (after a crash). When starting the container again, it crashes. in the log file, the same issue is here.
Using @6543 's suggestion, I deleted the files in the /data/gitea/indexers/ folder. I start the Docker again, crashes as usual but the deleted files weren't recreated afterwards either. The log says the same error.
Here's the line that keeps coming back:
2020/04/22 17:13:32 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT `external_id`, `user_id`, `login_source_id`, `raw_data`, `provider`, `email`, `name`, `first_name`, `last_name`, `nick_name`, `description`, `avatar_url`, `location`, `access_token`, `access_token_secret`, `refresh_token`, `expires_at` FROM `external_login_user` WHERE provider=? ORDER BY login_source_id ASC, external_id ASC LIMIT 100 [gitlab] - 584.032Âµs
2020/04/22 17:13:32 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT repo.id FROM `repository` repo WHERE repo.num_closed_issues!=(SELECT COUNT(*) FROM `issue` WHERE repo_id=repo.id AND is_closed=? AND is_pull=?) [true false] - 590.735Âµs
2020/04/22 17:13:32 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT repo.id FROM `repository` repo WHERE repo.num_closed_pulls!=(SELECT COUNT(*) FROM `issue` WHERE repo_id=repo.id AND is_closed=? AND is_pull=?) [true true] - 510.004Âµs
2020/04/22 17:13:32 ...m.io/xorm/core/db.go:154:QueryContext() [I] [SQL] SELECT repo.id FROM `repository` repo WHERE repo.num_forks!=(SELECT COUNT(*) FROM `repository` WHERE fork_id=repo.id) [] - 487.552Âµs
2020/04/22 17:13:32 ...er/issues/indexer.go:142:func2() [I] PID 15: Initializing Issue Indexer: bleve
2020/04/22 17:13:32 ...er/issues/indexer.go:158:func2() [F] Unable to initialize Bleve Issue Indexer: no such device
***

Ok it looks like for some reason bleve doesn't like that filesystem. I guess there's something odd about it - @lunny might know more. What's your host system?
In any case the workaround is to use the db issue indexer.
In app.ini:
[indexer]
ISSUE_INDEXER_TYPE = db

I see. Interesting observation. The server I'm running this on is my home server that also contains my NAS (which is really built out of consumer parts).
The volume the Gitea Docker runs off is this encrypted drive pool.
The pool consists of some WD Red drives pooled together using MergerFS. The base FS of the drives is XFS with Luks. I'll try changing this setting and report my results.

Okay, what a success! This one-liner fixed everything! It doesn't crash now. Awesome.
Btw, adding onto my last message, the server (running Docker) runs on Debian Buster.
Thanks @zeripath and all the others for all your help all along.

Changed the title so it is easier for others to find it.

This should really go in the Installation with Docker page as I had the exact same problem. It seems like the default setup of gitea doesn't work well with the fairly common use of MergerFS.
Linuxserver.io The Perfect Media Server - 2019 Edition
Serverbuilds.net Setting up media server using Ubuntu and SnapRaid
Symptoms
Using the exact  Installation with Docker steps, the docker instance crashes without details at the end of setup yeilding Received signal 15; terminating.
Steps to diagnose and resolve

Edit /gitea-data/gitea/conf/app.ini as follow

 [log]
 ROOT_PATH = /data/gitea/log
 MODE      = console
 LEVEL     = debug
 XORM     = console

Find that the real error is [F] Unable to initialize Bleve Issue Indexer at path: /data/gitea/indexers/issues.bleve Error: no such device
Search and find this issue
Edit /gitea-data/gitea/conf/app.ini as follow

 [indexer]
 ISSUE_INDEXER_PATH = /data/gitea/indexers/issues.bleve
 ISSUE_INDEXER_TYPE = db

Thank you very much @jshank ! I don't know why I thought because I had Docker running on Windows Server 2019 I couldn't use Gitea. But with your modification it's working!


updated project section

have made the project boxes four in a row.

@Tanujkanti4441 ur name is not in the list .what is ur participant id for swoc?

Just a begginer so haven't participated anywhere would you please tell me where to register

No problem I thought you were a participant in Swoc ..u can also try to
contribute to open source projects like swoc or ggsoc .it will help you
On Tue, 8 Feb 2022, 16:01 Tanuj Kanti, @.***> wrote:

Just a begginer so haven't participated anywhere would you please tell me
where to register
—
Reply to this email directly, view it on GitHub
https://github.com/Rayman-Sodhi/Clone-IT/pull/42#issuecomment-1032454302,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APVCDLHVYIB5SD4GRWMREYDU2DWHRANCNFSM5MPZN33Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you modified the open/close state.Message
ID: @.***>


Rename vim_widget.py to widgets/vim.py

Also rename vim.py to vimplugin.py
This is to have a consistent structure and naming with other plugins.

Probably better to do
Also rename vim.py to spyder-vim/plugin.py


(#2120) GeoRadius support store and storedist option with params

Resolves #2120
Different from #2140, it is implemented with params.
@sazzad16 PING

LGTM!

@gkorland @sazzad16 Hello, I want to continue to improve PR, please give me some specific suggestions.

@yangbodong22011 Please bear some patience. I'm sure @gkorland would jump in whenever he gets some free time. BTW, thanks for your enthusiasm!

@sazzad16 OK, I will be patient and thank you very much for your reply.


Any plans to add more detailed instructions for using the nodes? Specifically the Replace node?

Hi, I'm starting to test these nodes in a workflow, but I can't seem to grasp how the Replace node is supposed to work. I'm also unsure exactly where my initial prompt is supposed to go.
I see the Generator node's text field, and how it's being used to instruct the LLM on how to behave and receive the appropriate response. When I try to define a variable like [a] in that text field, it doesn't seem to work as intended. Perhaps I'm just not understanding the default workflow you've provided. Are you able to clarify things such as:

Where the user is supposed to put their initial prompt.
The purpose of the Replace node, with an example of it being used to affect image generation.

That would be immensely helpful. My ultimate goal is to include LLM prompt enrichment in my workflow in order to create better images. Thanks!
Trevor

Sorry, for some reason I didn't see your issue or get any notifications, not sure if going blind or a problem with GitHub.
In any case, the Replacer node is just there so you can combine text more easily, it takes in strings as input and converts any variable names it finds in the text field to their values, outputting a string as well. It's not strictly necessary for anything, and there are probably other nodes that use regex or something, might want to use those instead, depending on use case.
The prompt/instruction generally goes into the text field of the Generator node, it's just a string too so you can use it with other nodes.
For a simple example of how the Replacer node can be used, look at this:

The text in red is the raw model output, I inserted it between some tags with Replacer. Green is the combined output that is then passed to CLIPTextEncode. Hope this helps.