completion doesn't import the respective packages or modules

im using Golang(gopls server)

You should provide detailed information if you want to solve problem (e.g. animated gif, repro steps, your settings).

ok

my lsp settings
require'compe'.setup {
  enabled = true;
  autocomplete = true;
  debug = false;
  min_length = 1;
  preselect = 'enable';
  throttle_time = 80;
  source_timeout = 200;
  incomplete_delay = 400;
  allow_prefix_unmatch = false;

  source = {
    path = true;
    buffer = true;
    calc = true;
    vsnip = true;
    nvim_lsp = true;
    nvim_lua = true;
    spell = true;
    tags = true;
    snippets_nvim = true;
    treesitter = true;
  };
}
local lspconfig = require 'lspconfig'
local saga = require 'lspsaga'

saga.init_lsp_saga()

lspconfig.gopls.setup {
  cmd = {"gopls", "serve"},
  settings = {
    gopls = {
      analyses = {
        unusedparams = true,
      },
      staticcheck = true,
    },
  },
}

https://user-images.githubusercontent.com/60929919/107116587-5e395500-689a-11eb-8d1b-abcb385dd8b3.mov

It seems to not map compe#confirm

means?
how to check whether I mapped or not?

@hrsh7th Should we add FAQ example of CR mapping to readme?

@rustiever I checked it with your animated gif. In the gif, the newline had been inserted when you press <CR> (if compe#confirm mapping is available, it would not happen)

one more thing is whenever complete the functions or methods It doesn't complete it with parentheses
https://user-images.githubusercontent.com/60929919/107122316-137d0480-68bd-11eb-9f77-79d062e3bc9b.mov

Please your full config... it seems vim-go installed

configs

Your config has no compe#confirm mapping. Please read the docs.

I updated can you check pls now

Hm... current config seems correct. I will investigate it .

@rustiever By the way, this problem still exists latest nvim-compe?

yes @hrsh7th

@rustiever Sorry. I'm cloning your config but I can't understand your config (It has lua require'plugins' but plugins directory does not exists...)
So could you provide minimal reproducible config based on https://github.com/hrsh7th/nvim-compe/blob/master/misc/minimal.vim ?

I'm using the packer plugin manager, and for this lua require'plugins' line in lua folder configs are there

https://github.com/hrsh7th/nvim-compe/blob/master/misc/minimal.vim how to use this to reproduce without affecting my current configs?

nvim -u minimal.vim

https://github.com/hrsh7th/nvim-compe/blob/master/misc/minimal.vim how to use this to reproduce without affecting my current configs?

nvim -u minimal.vim

whether minimal.vim from current directory or I should save anywhere else?

whether minimal.vim from current directory or I should save anywhere else?

yes, you should save the file locally

`if has('vim_starting')
set encoding=utf-8
endif
scriptencoding utf-8
if &compatible
set nocompatible
endif
let s:plug_dir = expand('/tmp/plugged/vim-plug')
if !isdirectory(s:plug_dir)
execute printf('!curl -fLo %s/autoload/plug.vim --create-dirs https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim', s:plug_dir)
end
execute 'set runtimepath+=' . s:plug_dir
call plug#begin(s:plug_dir)
Plug 'hrsh7th/nvim-compe'
call plug#end()
PlugInstall | quit
" Options or settings here.
" lua require ('lsp-config')
lua << EOF
require'compe'.setup {
enabled = true;
autocomplete = true;
debug = false;
min_length = 1;
preselect = 'enable';
throttle_time = 80;
source_timeout = 200;
incomplete_delay = 400;
allow_prefix_unmatch = false;
source = {
path = true;
buffer = true;
calc = true;
vsnip = true;
nvim_lsp = true;
nvim_lua = true;
spell = true;
tags = true;
snippets_nvim = true;
treesitter = true;
};
}
local lspconfig = require 'lspconfig'
local saga = require 'lspsaga'
saga.init_lsp_saga()
lspconfig.gopls.setup {
cmd = {"gopls", "serve"},
settings = {
gopls = {
analyses = {
unusedparams = true,
},
staticcheck = true,
},
},
}
EOF
`
to reproduce

@rustiever I say again, your reproducible config has no compe#confirm mapping.

I have no time to support the user who does't read README.md and instructions.

terribly sorry for the trouble I'm causing you

`if has('vim_starting')
set encoding=utf-8
endif
scriptencoding utf-8
if &compatible
set nocompatible
endif
let s:plug_dir = expand('/tmp/plugged/vim-plug')
if !isdirectory(s:plug_dir)
execute printf('!curl -fLo %s/autoload/plug.vim --create-dirs https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim', s:plug_dir)
end
execute 'set runtimepath+=' . s:plug_dir
call plug#begin(s:plug_dir)
Plug 'hrsh7th/nvim-compe'
call plug#end()
PlugInstall | quit
" Options or settings here.
" lua require ('lsp-config')
lua << EOF
require'compe'.setup {
enabled = true;
autocomplete = true;
debug = false;
min_length = 1;
preselect = 'enable';
throttle_time = 80;
source_timeout = 200;
incomplete_delay = 400;
allow_prefix_unmatch = false;
source = {
path = true;
buffer = true;
calc = true;
vsnip = true;
nvim_lsp = true;
nvim_lua = true;
spell = true;
tags = true;
snippets_nvim = true;
treesitter = true;
};
}
local lspconfig = require 'lspconfig'
local saga = require 'lspsaga'
saga.init_lsp_saga()
lspconfig.gopls.setup {
cmd = {"gopls", "serve"},
settings = {
gopls = {
analyses = {
unusedparams = true,
},
staticcheck = true,
},
},
}
EOF
set completeopt=menuone,noselect
inoremap   compe#complete()
inoremap        compe#confirm('')
inoremap       compe#close('')
inoremap       compe#scroll({ 'delta': +4 })
inoremap       compe#scroll({ 'delta': -4 })
`

`if has('vim_starting')
set encoding=utf-8
endif
scriptencoding utf-8
if &compatible
set nocompatible
endif
let s:plug_dir = expand('/tmp/plugged/vim-plug')
if !isdirectory(s:plug_dir)
execute printf('!curl -fLo %s/autoload/plug.vim --create-dirs https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim', s:plug_dir)
end
execute 'set runtimepath+=' . s:plug_dir
call plug#begin(s:plug_dir)
Plug 'hrsh7th/nvim-compe'
call plug#end()
PlugInstall | quit
" Options or settings here.
" lua require ('lsp-config')
lua << EOF
require'compe'.setup {
enabled = true;
autocomplete = true;
debug = false;
min_length = 1;
preselect = 'enable';
throttle_time = 80;
source_timeout = 200;
incomplete_delay = 400;
allow_prefix_unmatch = false;
source = {
path = true;
buffer = true;
calc = true;
vsnip = true;
nvim_lsp = true;
nvim_lua = true;
spell = true;
tags = true;
snippets_nvim = true;
treesitter = true;
};
}
local lspconfig = require 'lspconfig'
local saga = require 'lspsaga'
saga.init_lsp_saga()
lspconfig.gopls.setup {
cmd = {"gopls", "serve"},
settings = {
gopls = {
analyses = {
unusedparams = true,
},
staticcheck = true,
},
},
}
EOF
set completeopt=menuone,noselect
inoremap compe#complete()
inoremap compe#confirm('')
inoremap compe#close('')
inoremap compe#scroll({ 'delta': +4 })
inoremap compe#scroll({ 'delta': -4 })
`

can you check on this pls

You must read README.md
inoremap <silent><expr> <C-Space> compe#complete()
inoremap <silent><expr> <CR>      compe#confirm('<CR>')
inoremap <silent><expr> <C-e>     compe#close('<C-e>')
inoremap <silent><expr> <C-f>     compe#scroll({ 'delta': +4 })
inoremap <silent><expr> <C-d>     compe#scroll({ 'delta': -4 })```

You must read README.md
inoremap <silent><expr> <C-Space> compe#complete()
inoremap <silent><expr> <CR>      compe#confirm('<CR>')
inoremap <silent><expr> <C-e>     compe#close('<C-e>')
inoremap <silent><expr> <C-f>     compe#scroll({ 'delta': +4 })
inoremap <silent><expr> <C-d>     compe#scroll({ 'delta': -4 })```

yes I read, and also added those in file but still there is problem

Your report is very annoying. Why didn't you check the markdown fenced code block before sending comment?
Your config seems to completely break to me.
let s:plug_dir = expand('/tmp/plugged/vim-plug')
if !isdirectory(s:plug_dir)
execute printf('!curl -fLo %s/autoload/plug.vim --create-dirs https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim', s:plug_dir)
end

execute 'set runtimepath+=' . s:plug_dir
call plug#begin(s:plug_dir)
Plug 'hrsh7th/nvim-compe'
call plug#end()
PlugInstall | quit

Your config has only nvim-compe but the config uses lspsaga and lspconfig, I can't understand.
If you can't get nvim-compe work, you can also try other completion-engine.

If you are using 'packer.nvim', You should clear packer.nvim's cache before testing.
I think you can't create minimal config.
Please put the :imap command result.

If you are using 'packer.nvim', You should clear packer.nvim's cache before testing.
I think you can't create minimal config.
Please put the :imap command result.

`if has('vim_starting')
set encoding=utf-8
endif
scriptencoding utf-8
if &compatible
set nocompatible
endif
let s:plug_dir = expand('/tmp/plugged/vim-plug')
if !isdirectory(s:plug_dir)
execute printf('!curl -fLo %s/autoload/plug.vim --create-dirs https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim', s:plug_dir)
end
execute 'set runtimepath+=' . s:plug_dir
call plug#begin(s:plug_dir)
Plug 'hrsh7th/nvim-compe'
call plug#end()
PlugInstall | quit
" Options or settings here.
" lua require ('lsp-config')
set completeopt=menuone,noselect
inoremap   compe#complete()
inoremap        compe#confirm('')
inoremap       compe#close('')
inoremap       compe#scroll({ 'delta': +4 })
inoremap       compe#scroll({ 'delta': -4 })
lua << EOF
require'lspconfig'.gopls.setup{}
EOF
let g:compe = {}
let g:compe.enabled = v:true
let g:compe.autocomplete = v:true
let g:compe.debug = v:false
let g:compe.min_length = 1
let g:compe.preselect = 'enable'
let g:compe.throttle_time = 80
let g:compe.source_timeout = 200
let g:compe.incomplete_delay = 400
let g:compe.max_abbr_width = 100
let g:compe.max_kind_width = 100
let g:compe.max_menu_width = 100
let g:compe.documentation = v:true
let g:compe.source = {}
let g:compe.source.path = v:true
let g:compe.source.buffer = v:true
let g:compe.source.calc = v:true
let g:compe.source.vsnip = v:true
let g:compe.source.nvim_lsp = v:true
let g:compe.source.nvim_lua = v:true
let g:compe.source.spell = v:true
let g:compe.source.tags = v:true
let g:compe.source.snippets_nvim = v:true
let g:compe.source.treesitter = v:true
let g:compe.source.omni = v:true
`
I'm sorry for troubling you,
can you kindly check on this config


Filter use

Can you guys explain that how to implement filter to the  classical function " find out the work done by a body moving with different velocities from point A to E (say)?

We need following steps for that:
Define the Problem:
Discretize the Path
Calculate Force at Each Point
Calculate Work at Each Step
Sum the Work
Numerical Integration
Implement a Filter
Final Result

@reshnashrestha but have not used force term in our problem.

you can skip that part and in that manner, you can add your process.


Showing different currency while creating gift.

If this is in sats, why is this showing dollars?

For gifting, the default currency in all screens should be fiat, with an option for them to choose sats if needed. Like the Send screen

https://xd.adobe.com/view/e8259038-6a8a-4b4f-b88f-780e311438a5-bd76/screen/e151d4ef-3852-42d9-bd9c-08cc2d5ca1ba/
lets use this switch.

Verified this issue on dev app v2.0.1(337)


Update issue templates

Codecov Report
Patch and project coverage have no change.

Comparison is base (edb41de) 85.04% compared to head (d9ad5f2) 85.04%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main       #1   +/-   ##
=======================================
  Coverage   85.04%   85.04%
=======================================
  Files          17       17
  Lines         448      448
  Branches      102      102
=======================================
  Hits          381      381
  Misses         67       67

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Implement mono / code generation for tuples

Note that I combined the code paths for record & tuple accessors using field: IndexOrField (tuple or record, respectively). I called the combined type StructAccessorData.
I experimented with also doing the same thing with TupleAccess/RecordAccess, but the there wasn't nearly as much code sharing possible in that case.
Thanks to Ayaz for helping investigate/resolve the test failures!

The windows failure looks unrelated:
  thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 32, kind: Uncategorized, message: "The process cannot access the file because it is being used by another process." }', crates\compiler\build\src\link.rs:795:50

Thanks for the review! Working on updates...

mono tests for the decision trees build when pattern matching tuples (even 1 is fine)

Can you expand a little on this? Not sure how to test the decision tree building.

Can you expand a little on this? Not sure how to test the decision tree building.

Generating IR for pattern matching of tuples would be enough. See for example the list pattern matching tests in mono tests

I added a couple exhaustiveness checks, the mono test for pattern matching (which caught a bug - thanks!), and a few fixups.


Iterate on "apply changes to multiple roads/lanes"

The colors of the edited road/lane and selected ones (dark blue now👇) are not very obvious in dark mode.

Suggestion: try using the theme color orange #EE702E which I think might work better on both modes.
Also, I would add a tooltip on the edited road/lane just to make it clearer.

It is easy to lose the context of the changes, losing check of which lane/road was edited especially in the night mode.
Suggestion: adding relocation functionality on both editor and multi-road editor

Figma Link

Thanks, both changes done! I'm redeploying the web app for a quick preview, but I'm on the slow laptop...

ab_orange_1 is maybe a bit too close to the current arterial road color in day mode, but it's still distinguishable. And I suspect those colors might be shifting soon anyway.

Changes live at http://abstreet.s3-website.us-east-2.amazonaws.com/dev/abstreet.html?--dev&system/us/phoenix/maps/tempe.bin&--cam=19.58/33.42743/-111.92628
I'll close this, since both issues you reported are now fixed, but we can reopen if we need to adjust more


RFC: refactoring the internal

tldr: I am planning to make some changes to refactor the redux-saga internal which includes removing runSaga#options.dispatch / runSaga#options.getState and seperating effect-runners into categories, how do you think about it?
I am excited about saga running environments introduced in #1479. env brings more opportunities to simplify proc() and make it easier to extend redux-saga. proc() is over complex now (the function definition span 500+ lines), I am planning to make use of env and move complexity from proc() to runSaga().
#1481 is an attempt to simplify the implementation of digestEffect. In that PR, I extract the logic of composing middlewares to env.finalizeRunEffect (or env.enhanceRunEffect) in runSaga. For proc(), getting a env.finalizeRunEffect instead of env.middleware means reducing the knowledge requirement about the outter world.
As the doc says, runSaga could be used to connect external input/output, but currently runSaga requires options.dispatch and options.getState, which means our runSaga/proc is still coupled with redux since dispatch and getState are APIs from redux. Ideally, runSaga should not require any redux-related options. Removing options.dispatch and options.getState makes it easier to run sagas in non-redux environments.
In 2fb401d68afc988563daff608d210e9a8d295cf7, I remove env.dispatch by passing runSaga a special channel in src/internal/middleware.js. The special channel could be thought as a redux-store-connected stdChannel: every put effect to this channel will trigger store.dispatch, and every call of store.dispatch will put the action to this channel.
Removing env.getState is difficult now, because select effects depend on env.getState. Removing env.getState requires a mechanism that allows defining new effect types when runSaga is called. env.runCustomEffect seems like a good option now, we can use it internally first to remove env.getState. That means running logic of select effects is defined in src/internal/middleware.js, and select effects are only available in sagas started by sagaMiddleware.run. Later on, I'll try to find better alternatives to extend effect types, and perhaps we could allow extending in the user land.
We have tried move effect-runner out of proc in #1263, but it has lots of conflicts and can hardly merge now. I've implemented the separation in my little-saga. Here is an image showing the structure of little-saga:

The code in folder src/core/ implements the core effect types, which inlcudes promise / iterator / fork / spawn / join / cancel / cancelled / def. Other effect types are extended by def-effect. src/commonEffects implements all / race / apply / call / cps / getContext / setContext, and src/channelEffects implementes channel-related effects including put / take / flush / actionChannel. In little-saga, select effect is defined when connecting to a redux store.
Once env.runCustomEffect can be use internally, I think we could seperate redux-saga's effect-runners into several categories like in little-saga. Redux-saga is much more complicated than little-saga, I'll write code carefully and try to avoid breaking changes (expect for runSaga#options.getState and runSaga#options.dispatch).
How do you think about these changes? If you agree my proposal, I am glad to bring these changes. I am open to any suggestion, so just tell me any idea/thought you have.

As the doc says, runSaga could be used to connect external input/output, but currently runSaga requires options.dispatch and options.getState, which means our runSaga/proc is still coupled with redux since dispatch and getState are APIs from redux. Ideally, runSaga should not require any redux-related options. Removing options.dispatch and options.getState makes it easier to run sagas in non-redux environments.

We can certainly discuss alternative API, but even though dispatch/getState names are obviously taken from redux you can pass any functions as those to connect external input/output. Don't quite think this is a blocker for anyone if they need this lower level API.
At the moment I don't particularly feel like removing internally used dispatch/getState is an important thing to do, I don't see it making things any easier. They are kinda a nicely defined way of integrating saga with anything - where getState is used for querying something and dispatch is acting like an "emit" function.
What is more interesting to me is to see how exactly have you separated various effect categories in your little-saga. I will have to take a look into that in the following week.
Don't be discouraged by my words though, I'm happy to discuss any idea.

Don't quite think this is a blocker for anyone if they need this lower level API.
Yes, you are right. I've made mistakes. I was thinking that dispatch / getState introduces much challenge for connecting external I/O ( emitter, Observable). But after a second thinking, it is fine that using dispatch / getState actually.

What is more interesting to me is to see how exactly have you separated various effect categories in your little-saga. I will have to take a look into that in the following week.
I can make a trial PR in the next few days.


KAFKA-12937; mm2 can start from the ending of a topic

this patch resolve the KAFKA-12937 issue: mm2 can not start from the ending of a topic.
When starting with previously uncommitted partitions, the MirrorSourceTask always set offset to 0.
solution:  filter the uncommitted partitions and call seekToEnd or seekToBeginning to reset offset according to auto.offset.reset config.
@halorgium @astubbs  @alexism  @glasser  @rhardouin  please check

Not sure why I was tagged?

Not sure why I was tagged — did you mean somebody else?

hello, the github recommend.  there's no Assignees, I don't know how to trigger the flow

This has been fixed in https://issues.apache.org/jira/browse/KAFKA-13988. Closing.


Add Wrapped Matic to Axelar asset list

Whether we'll use this logo is still tbd... but it is impressive in design. Can we at least fix the serif font on the svgs @ToggLeTek ?

Alrighty, I have updated the SVG. Sorry about that. Thought I had converted the Font --> Outlines. Silly me!

resolved by #643


UIImageView+AFNetworking does not work for Gif

I was building a gif app and found all the gif does not play using
[cell.imageView setImageWithURL:[NSURL URLWithString:gif.smallGifURL]];

In AFURLResponseSerialization.h
static UIImage * AFImageWithDataAtScale(NSData *data, CGFloat scale) {
    UIImage *image = [[UIImage alloc] initWithData:data];
    if (image.images) {
        return image;
    }

    return [[UIImage alloc] initWithCGImage:[image CGImage] scale:scale orientation:image.imageOrientation];
}

I think image.images is always nil because [[UIImage alloc] initWithData:data] does not work for animated gif.
Why didn't we bring in AnimatedGIFImageSerialization?
The issue will be fixed if I include the  AnimatedGIFImageSerialization in my project.

The issue will be fixed if I include the AnimatedGIFImageSerialization in my project.

Yes, that's what should be done. They are different dependencies.


Get Search Bearer token doesn't work with PowerShell

The document section Test as current user has:
az account get-access-token --scope https://search.azure.com/.default

Bearer token generated with this Azure CLI command in a cloud shell does work. However, there is no command for PowerShell and PowerShell is being used widely.
A similar command with PowerShell
 $token = (Get-AzAccessToken -ResourceUrl "https://search.azure.com/.default").Token

gave the following error:
Get-AzAccessToken: SharedTokenCacheCredential authentication failed: AADSTS500011: The resource principal named https://search.azure.com/.default was not found in the tenant named xxxx. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You might have sent your authentication request to the wrong tenant. Trace ID: xxxxxxx Correlation ID: xxxxxx Timestamp: 2024-01-04 15:35:23Z

When simply using $token = (Get-AzAccessToken).Token, no error was thrown but the generated bearer token isn't a valid bearer token with the search service.
I tried both PowerShell 5 and 7, which gave the same error. Please help to investigate and provide a solution. Thanks.

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

ID: 2293a04c-2b13-4087-0b20-eebf2278f522
Version Independent ID: 9fc429b6-1f91-74e0-3f35-3b0e54ecd213
Content: Connect using Azure roles - Azure AI Search
Content Source: articles/search/search-security-rbac.md
Service: cognitive-search
GitHub Login: @HeidiSteen
Microsoft Alias: heidist

@whsh-ca
Thanks for your feedback! We will investigate and update as appropriate.

Hi @whsh-ca, I received the same error message. I checked the Get-AzAccessToken command itself, and I believe the cmdlet doesn't support the Azure Search Uri endpoint. In looking at the supported ResourceTypeName, Azure Search isn't listed as one of them. I don't think it's an issue with the PowerShell but the Az.Account module itself. I suggest creating a new question or a bug, so the appropriate team can investigate the issue.
In the meantime, I have reached out to the product group to verify if that resource uri is supported or not. I'll updated this post with what I'm able to find out.
I'm proceeding to close this issue since it's related more to the module rather than the doc.
#please-close


Specifying snippet

Commit hash and line numbers - easiest to implement, most brittle, relies on PRs to update

Commit hash and search terms for start/end - need to update commit manually, and you can check if it is still relevant
Search terms and branch name - updates automatically, might break if search terms are not found
Search terms and branch name - we follow every commit and notify when relevant lines are modified

I prefer branch. Can you do line numbers and keep track of how those line numbers change based on git? So I specify lines 10-20 on master/file.js, and when there's a new commit that adds two lines at line 15, my YAML/JSON gets auto-changed to lines 10-22? If not, I'd prefer search terms, and notifying only when the search term breaks.

Yeah I think we'll only be able to do the simplest approach -- 1 -- for the hackathon, since we ended up focusing on the reader experience and didn't want to work on building out CI-type functionality. But I like the idea of specifying line numbers and trying to track how they change.


Header checking

Initial pass at resolving issue #68
Interface changes:

New interface HeaderCheckerInterface
Modified interface ParametersCheckerInterface so that it only checks parameters.
New interface CombinedCheckerInterface that checks both at once. (Not fussy about name.)

Implementation changes:

RestrictiveParameterChecker now only checks parameters.
RestrictiveHeaderChecker checks headers using same implementation as old RestrictiveParameterChecker.
RestrictiveChecker checks both and keeps same constructor as old RestrictiveParamterChecker. I.e. people who want to continue using the previous way of doing checking use this new object instead.

Tests updated.

And one more, please post to develop :wink:

Will make changes and resubmit this to the develop branch.


Redesign the Contact Page

Fixes: #580
I have redesigned the Contact Page and this is how it looks.

Resolve the conflicts in the mentioned files. Ensure you pull all the latest changes before pushing your feature/bug fixes to the main branch. After resolving the conflicts, please open a new PR for review.
Thank you!


mu-q and mu-mu energy

Hi Andy,
I'm running into energy dependence on the kappa parameter when dipoles are present. I've noticed that helPME does not have kappasweep tests for this case so I'm wondering if you've verified it. When testing, I did add the E_self(mu) but it didn't help much. I also tried with a wide range of k-space grids and with a very large real-space cutoff, and both with zero and non-zero total dipole moment to no avail. Below is a table of one of the test runs for a water dimer from your unit tests (including coordinates, charges and dipole moments) with different kappas (called alpha). All quantities are in atomic units (Hartree and Bohr).

grid dim
alpha [a.u.]
GridSp [a.u.]
range [a.u.]
E_self [a.u.]
E_real [a.u.]
E_rec [a.u.]
E_total [a.u.]
T(real) [s]
T(rec) [s]

20
0.02
2
283.936361
-0.023545708
-0.393121622
1E-10
-0.41666733
0.005952
0.003026

30
0.03
1.333333
189.290907
-0.035318903
-0.381349666
1.3161E-06
-0.416667253
0.002008
0.001949

48
0.045
0.888889
126.193938
-0.052979502
-0.363781306
8.88422E-05
-0.416671965
0.001029
0.004987

64
0.0675
0.592593
84.1292922
-0.079473126
-0.338054364
0.000779148
-0.416748342
0.001016
0.011076

96
0.10125
0.395062
56.0861948
-0.119222761
-0.300991047
0.003060132
-0.417153676
0
0.039894

144
0.151875
0.263374
37.3907965
-0.178878262
-0.248487195
0.008947323
-0.418418134
0
0.135686

216
0.2278125
0.175583
24.9271977
-0.268466299
-0.176956275
0.023667676
-0.421754898
0
0.420907

324
0.34171875
0.117055
16.6181318
-0.403202007
-0.093209204
0.065818528
-0.430592682
0
1.399255

486
0.512578125
0.078037
11.0787545
-0.606499142
-0.026404418
0.182708722
-0.450194838
0
4.846253

750
0.768867188
0.052025
7.38583635
-0.91547316
-0.001493128
0.440175597
-0.476790692
0
18.04084

I would appreciate if you'd let me know if I'm missing something and maybe add a kappasweep test with dipoles.
Kind regards,
Alexei
Edit: the GridSp is approximate. It's an input parameter used to compute the grid dimensions.
Edit2: the splineOrder was 7 in all tests but I've also run with higher orders with the same results.

A small update.
I tried to reproduce numbers for the "Two dipoles" case in table 2 from https://doi.org/10.1063/1.481216 (E(eps_sur=Inf)=-2.0087525) and could only do that for a very small kappa=0.05. So it's obviously not the surface term.
Alexei

A small update.
I tried to reproduce numbers for the "Two dipoles" case in table 2 from https://doi.org/10.1063/1.481216 (E(eps_sur=Inf)=-2.0087525) and could only do that for a very small kappa=0.05. So it's obviously not the surface term.
Alexei

Hi, Alexei,
Thanks for the very thorough debugging effort.  I don't directly have a kappa (alpha, also beta in the PME literature!) sweep test for the dipole case, because I don't support the real space term in the code; I wanted to avoid the slippery slope of becoming a full MD engine, rather than just a reciprocal space helper.  I can mimic a dipole with a set of equal and opposite charges and make a test case out of that (I already made something similar to test the electric field last week) so I'll let you know what I find from that.  The dipole code itself was tested via a kappa sweep test in the code that inspired me to add multipoles, but I will check it again here.  I'm out of town for a few days, so apologies in advance if you don't hear back from me immediately.  I am very eager to get this resolved though, so that I can be sure the code is doing what I expect and so that you can use it for what your needs.
Thanks again,
Andy.

Hi, Alexei,
Thanks for the very thorough debugging effort.  I don't directly have a kappa (alpha, also beta in the PME literature!) sweep test for the dipole case, because I don't support the real space term in the code; I wanted to avoid the slippery slope of becoming a full MD engine, rather than just a reciprocal space helper.  I can mimic a dipole with a set of equal and opposite charges and make a test case out of that (I already made something similar to test the electric field last week) so I'll let you know what I find from that.  The dipole code itself was tested via a kappa sweep test in the code that inspired me to add multipoles, but I will check it again here.  I'm out of town for a few days, so apologies in advance if you don't hear back from me immediately.  I am very eager to get this resolved though, so that I can be sure the code is doing what I expect and so that you can use it for what your needs.
Thanks again,
Andy.

Sorry for the long delay in addressing this - it completely fell off my radar for a while.  The dipoles should hopefully be fixed by #58 now, but please ping back if there are any further problems.  I'm still a bit confused by the test that compares fields to finite differences of potentials; the test is great for cubic boxes, but not otherwise, so I still need to do some reading.  Possible h=0 terms aside, the "kappa sweep" test and comparison to the literature values you cited above make me think that the current implementation is correct.

Hi Andy,
Thank you for the fix and for the heads up. I finally came around to
testing it and can confirm that it fixes the issues I reported. I've now
incorporated it into the AMS ForceField engine.
Thank you again and kind regards,
Alexei
On 25/06/2021 23:17, Andy Simmonett wrote:

Sorry for the long delay in addressing this - it completely fell off
my radar for a while. The dipoles should hopefully be fixed by #58
https://github.com/andysim/helpme/pull/58 now, but please ping back
if there are any further problems. I'm still a bit confused by the
test that compares fields to finite differences of potentials; the
test is great for cubic boxes, but not otherwise, so I still need to
do some reading. Possible h=0 terms aside, the "kappa sweep" test and
comparison to the literature values you cited above make me think that
the current implementation is correct.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/andysim/helpme/issues/57#issuecomment-868837890,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG3TYKHRVCXJXAMOMX2U2UTTUTW5DANCNFSM4WT6CAJQ.


Home page redesign

Visually redesign the home page to make it more simplistic and remove the list of things to do that currently don't always apply to everyone

This needs to be split into multiple issues. Right now it's unclear what exactly do you intend to do.

Current WIP design


Merge #1267 as experimental

Merge https://github.com/LunarG/gfxreconstruct/pull/1267.
Being behind a compile-time switch wouldn't allow CI to catch breaking code changes, so would be the same as being in another branch.  However, we can merge with a bunch of banners saying "unsupported", "issues may not be answered," etc.

Getting the d3d11 support merged and shipped via CI would be much appreciated!
We already used it for a situation where Apitrace crashed.
So having prebuilds that dont expire like the CI build of the PR would be really helpful.


Emoji modifiers not removed by emoji-strip

For example, the following string contains emoji modifiers (http://emojipedia.org/skin-tone-modifiers/):
Just casually bumped into @andyroddick in the commentary box @bbctennis @Wimbledon 👍🏻👍🏻
emoji-strip currently does not remove these from strings.

+1 - I'll see if I can figure out a patch for this, but I'm pretty emoji-ignorant. =)

Fixed this in version 1.0.0. Already published to npm.


live-restore prevents graceful stop of containers during upstart system halt/reboot

Description

I have noticed on upstart based system Ubuntu 14.04, Docker containers are not gracefully stopped, if the Docker engine is configured with live-restore option. This causes problems for containers that need to be properly shutdown.
Steps to reproduce the issue:

Enable live-restore
sudo reboot

Describe the results you received:
No entries in docker's upstart log (/var/log/update/docker.log) attempting to stop any containers. Upstart's /etc/init.d/sendsigs kills any remaining processes, with SIGKILL, as a last resort, which ends up killing all containers.
Describe the results you expected:
Even with live-restore enabled, a host halt/shutdown should still trigger the docker's init to stop containers.
I feel a solution to this, would be to update the docker's upstart config (/etc/init/docker.conf) to:

Change stop on runlevel [!2345] to stop on starting rc RUNLEVEL=[06]
Create a post-stop script directive

Checks if the runlevel is either 0 (halt) or 6 (reboot)
Gracefully kill all running cotainers with docker-runc kill <container
Set a timer, maybe 30 seconds, and wait for either the timer to expire or all containers to enter stop state (docker-runc list).

I have the above working and can submit a PR, but wanted to run it by others first.
Not sure if this also affects non-upstart based systems.

ping @crosbymichael

This is by design.  When docker gets killed, it does not know if it is a system reboot, shutdown, or you manually stopping the daemon.  So its not going to try to gracefully kill any containers.
I don't think there is really anything to do in the daemon itself for handling this and should be left up to the admin.  init script changes could be acceptable but may not cover all the corner cases.

Is there a method for stopping all containers gracefully when live-restore is used? Or do you just need to run docker stop on every container individually?

@jsravn https://github.com/moby/moby/pull/31664 has been open to fix this in the upstart init. I believe a docker kill -s TERM $(docker ps -q) would do the trick, but haven't tested. If you do a docker stop $(docker ps -q), that will work, but would cause containers with restart policy unless-stopped to not start on reboot.


python311Packages.oslo-db: cleanup dependencies

Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 283170 run on x86_64-linux 1

4 packages marked as broken and skipped:

python311Packages.subunit2sql
python311Packages.subunit2sql.dist
python312Packages.oslo-db
python312Packages.oslo-db.dist

2 packages built:

python311Packages.oslo-db
python311Packages.oslo-db.dist


Console ...When i mark to copy..it to be err.  Can not  Copy Application Err

Console ...When i mark to copy..it to be err.  Can not  Copy Application Err
wacs.exe

You can try going into settings.json and changing the character encoding to unicode instead of utf-8. That seems to help for some users.

@WouterTinus Ths  so much....  It  worked....


Math magicians: components

In this pull request, I have implemented :

Deleted all the boilerplate from CRA (text, images, styles)
Created a directory called components
Inside components, created a new Calculator.js file
In Calculator.js, created a React component that matches this design:

@MahmoudBakr23 and @Davidosky007  Thanks for your kind review and feedback.


MAINT: remove non-default settings (except shallow) in .gitmodules

Closes gh-15276
[ci skip]

I've added a backport label--otherwise, paranoia about silent submodule updates, or failure to update, is going to cost time on the maintenance/1.8.x branch, where some future PROPACK changes for Windows cannot be ruled out yet.

good idea


Should persist UUID and PhoneID

Not saving (generating new for each app run) UUID and PhoneID as it is now leads to IG account ban.

See: https://github.com/mgp25/Instagram-API/blob/master/src/Settings/StorageHandler.php#L17

Hi
So , Should I change the code and follow this notes:

Do not save UUID and PhoneID in export function.
Generate new UUID and PhoneID in import function.
Generate new UUID and PhoneID in New function.

Hi,
as i can understand the issue, it is that the UUID and PhoneID are not saved and must be saved to not get the account banned. So what to do is to export and import ?

Hi @skawm ,
Export function will save InstaType that contains UUID...

Hi @ahmdrz ,
so I don't understand exactly where the issue since the UUID and PhoneID are/can be saved through the export-imports functions

Hello,
I did not notice export feature, because I read the readme a long time ago when it wasn't there.
I think import/export covers this, except it should be mentioned in readme what it's needed for and that using Login many times instead of import/export leads to high account ban risk.
Also, I think https://github.com/mgp25/Instagram-API defaults to automatic file storage for that reason.
Thank you

@glebtv https://godoc.org/gopkg.in/ahmdrz/goinsta.v2 Import and Export are successfully implemented on v2 branch.


The HTC Vive controllers do not appear in any Unity Scene

Hi.
I am sorry for my ignorance but I am trying this Moondust project with the HTC Vive and its first Controllers( not Knuckles ones) in Unity and these controllers do not appear in any example, for it, Could anybody help me to fix it? Would it be possible?
Thanks for your time

Not to sound rude, but the readme on the main page specifically states the demo only works with knuckles controllers, and not original vive controllers, I think your out of luck.

Hi wirelessdreamer
Pleasse do not worry, You are right, I made a mistake. Now I got thae EV3 and I will try this Moondust project.
Regards


Visual refinement feedback megasesh

:tada: This PR is included in version 1.16.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


docs: move release notes to 0.1

The release notes currently don't render. This may be due to the lack of a prior tag, but it still unfortunate.
I have not been able to fix this rendering.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>2
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>6:
0.0%

Covered Lines:
443

Relevant Lines:
443

💛  - Coveralls


Is possible to get audio output ?

Hi ,
how to get audio out like speaker ?

This component does not play out any audio because if it did you would get a horrible looping echo effect because the sound from your speaker will go directly back into your microphone.

Hi,
I would like to get some clarification with get devices method i.e.
OT.getDevices(callback), This method is currently returning only the audio
input and video input. But we are in need of one more additional
information (ie audio output) which is not currently returning by that
method. Is there any other way to get that data through any of the other
methods rendered by opentok? If it is not readily available, please let us
know the possible way to get it.
On Thu, Aug 6, 2015 at 5:51 PM, Adam Ullman<EMAIL_ADDRESS>wrote:

Closed #18
https://github.com/opentok/opentok-hardware-setup.js/issues/18.
—
Reply to this email directly or view it on GitHub
https://github.com/opentok/opentok-hardware-setup.js/issues/18#event-375232839
.

--
Regards
Gobi Baskaran

Oh, sorry, I misunderstood. Audio output devices aren't available to us in the browsers yet and so we can't provide them. They are currently available in Chrome 45 (beta) behind a flag. When they do become available and not behind a flag we will be able to expose them. More information can be found at:
https://code.google.com/p/webrtc/issues/detail?id=2243
https://webrtc.github.io/samples/src/content/devices/multi/

Aren't audio output devices are now available, but still can't get it through OT.getDevices(). is this still in the pipeline?


[macOS] CVDisplayLink unavailable crash (on app start)

Describe the bug
We have a pretty significant amount of logs from the production environment with a stack trace suggesting the app failed to initialize CVDisplayLink
   at Avalonia.Native.Interop.Impl.__MicroComIAvnPlatformRenderTimerProxy.RegisterTick(IAvnActionCallback callback)
   at Avalonia.Native.AvaloniaNativeRenderTimer.add_Tick(Action`1 value)
   at Avalonia.Rendering.ThreadProxyRenderTimer.add_Tick(Action`1 value)
   at Avalonia.Rendering.RenderLoop.Add(IRenderLoopTask i)
   at Avalonia.Rendering.Composition.Server.ServerCompositor..ctor(IRenderLoop renderLoop, IPlatformGraphics platformGraphics, BatchStreamObjectPool`1 batchObjectPool, BatchStreamMemoryPool batchMemoryPool)
   at Avalonia.Rendering.Composition.Compositor..ctor(IRenderLoop loop, IPlatformGraphics gpu, Boolean useUiThreadForSynchronousCommits, ICompositorScheduler scheduler, Boolean reclaimBuffersImmediately, Dispatcher dispatcher)
   at Avalonia.Rendering.Composition.Compositor..ctor(IRenderLoop loop, IPlatformGraphics gpu, Boolean useUiThreadForSynchronousCommits)
   at Avalonia.Rendering.Composition.Compositor..ctor(IPlatformGraphics gpu, Boolean useUiThreadForSynchronousCommits)
   at Avalonia.Native.AvaloniaNativePlatform.DoInitialize(AvaloniaNativePlatformOptions options)
   at Avalonia.Native.AvaloniaNativePlatform.Initialize(IntPtr factory, AvaloniaNativePlatformOptions options)
   at Avalonia.Native.AvaloniaNativePlatform.Initialize(AvaloniaNativePlatformOptions options)
   at Avalonia.AvaloniaNativePlatformExtensions.<>c__DisplayClass0_0.<UseAvaloniaNative>b__0()
   at Avalonia.AppBuilder.SetupUnsafe()
   at Avalonia.AppBuilder.Setup()
   at Avalonia.AppBuilder.SetupWithLifetime(IApplicationLifetime lifetime)
   at Avalonia.ClassicDesktopStyleApplicationLifetimeExtensions.StartWithClassicDesktopLifetime(AppBuilder builder, String[] args, ShutdownMode shutdownMode)

I would assume something happened and the CVDisplayLink callback mechanism failed to initialize.
cc: @maxkatz6
To Reproduce
I can't repro it but I would guess disconnecting monitor before starting the app would do the trick.
Expected behavior
fallback to standard timer?
Avalonia version
11.0.7
OS
macOS
Additional context
https://github.com/AvaloniaUI/Avalonia/pull/12652

I checked the logs again and all crashes happened in the first second after the app started. It also does not relate to a single user (the user could start the app before and after and no user had this issue twice).

@ltetak are you sure it's reproducible on 11.0.7? I don't think it was ever backported.

@ltetak is there any special setup on these machines? Multiple displays, maybe? Something that might help testing.

@ltetak pushed this PR so it can rethrow original status code instead. Can you try once builds are ready?
https://github.com/AvaloniaUI/Avalonia/pull/14938

@ltetak I don't know if CGGetActiveDisplayList is a right approach, but it might worth a try, yea. Ideally should be double checked how Chromium/qtbase handle that.

This is interesting https://source.chromium.org/chromium/chromium/src/+/main:ui/display/mac/display_link_mac.cc;l=236?q=CVDisplayLinkCreateWithCGDisplay

@maxkatz6 I haven't checked this yet but we also have other logs that seem somewhat related
System.Runtime.InteropServices.COMException: BeginDrawing failed
   at IAvnMetalRenderingSession Avalonia.Native.Interop.Impl.__MicroComIAvnMetalRenderTargetProxy.BeginDrawing()
   at IMetalPlatformSurfaceRenderingSession Avalonia.Native.MetalRenderTarget.BeginRendering()
   at ISkiaGpuRenderSession Avalonia.Skia.Metal.SkiaMetalGpu+SkiaMetalRenderTarget.BeginRenderingSession()
   at IDrawingContextImpl Avalonia.Skia.SkiaGpuRenderTarget.CreateDrawingContext(bool useScaledDrawing)
   at void Avalonia.Rendering.Composition.Server.ServerCompositionTarget.Render()
   at void Avalonia.Rendering.Composition.Server.ServerCompositor.RenderCore(bool catchExceptions)
   at void Avalonia.Rendering.Composition.Server.ServerCompositor.RenderReentrancySafe(bool catchExceptions)
   at void Avalonia.Rendering.Composition.Server.ServerCompositor.Render(bool catchExceptions)
   at void Avalonia.Media.MediaContext.SyncCommit(Compositor compositor, bool waitFullRender, bool catchExceptions)
   at void Avalonia.Controls.TopLevel.HandleClosed()
   at void Avalonia.Controls.WindowBase.HandleClosed()
   at void Avalonia.Native.WindowBaseImpl+WindowBaseEvents.Avalonia.Native.Interop.IAvnWindowBaseEvents.Closed()
   at void Avalonia.Native.Interop.Impl.__MicroComIAvnWindowBaseEventsVTable.Closed(Void* this)
   at void Avalonia.Native.DispatcherImpl.RunLoop(CancellationToken token)
   at void Avalonia.Threading.DispatcherFrame.Run(IControlledDispatcherImpl impl)
   at void Avalonia.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
   at void Avalonia.Threading.Dispatcher.MainLoop(CancellationToken cancellationToken)
   at int Avalonia.Controls.ApplicationLifetimes.ClassicDesktopStyleApplicationLifetime.Start(string[] args)
   at int Avalonia.ClassicDesktopStyleApplicationLifetimeExtensions.StartWithClassicDesktopLifetime(AppBuilder builder, string[] args, ShutdownMode shutdownMode)


Update GitHub Actions

Use the newest versions to solve the deprecation warning
Remove the cache step as the newest go and node actions have built-in caching
Add the official<EMAIL_ADDRESS>email address

In case you didn't notice, the pipeline failed for this^

@binwiederhier Thanks, that should fix it 👀

Codecov Report
Patch and project coverage have no change.

Comparison is base (ffbf288) 65.76% compared to head (3f8784c) 65.76%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #745   +/-   ##
=======================================
  Coverage   65.76%   65.76%
=======================================
  Files          50       50
  Lines        7332     7332
=======================================
  Hits         4822     4822
  Misses       1725     1725
  Partials      785      785

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Support dictionary of nullable items

I have a model as follows:
public class PurchaseReadDto
{
    public Dictionary<string, decimal?> ParticipantsParts { get; set; }
}

Swagger for ParticipantsParts of which is generated as:
"ParticipantsParts": {
     "type": "object",
     "additionalProperties": {
           "type": "number",
            "format": "decimal"
       }
}

And in my C# client it surfaces back as System.Collections.Generic.IDictionary<string, decimal>.
As was suggested in https://github.com/RicoSuter/NSwag/issues/82, I can add null to type ("type": ["null", "number"]) and the generated code turns into Dictionary<string, decimal?> - exactly what I need.
But can I make it being generated this way right away?
Maybe the attribute ItemsCanBeNullAttribute from https://github.com/RicoSuter/NSwag/issues/1951 could be reused although in this case there is no ambiguity: decimal? must clearly allow null values.
I use this $(NSwagExe_Core20) webapi2swagger for swagger generation.
Thanks!

You are right, in this case it should just work...

That was quick! Thank you very much.
But I can not make it work. I installed the last version of NJsonSchema package, copied assemblies from there to nswag.msbuild\12.1.0\tools\NetCore21\ (I dont know any other way to update them for NSwagExe_Core21), got this record in generated swagger "x-generator": "NSwag v<IP_ADDRESS> (NJsonSchema v<IP_ADDRESS> (Newtonsoft.Json v<IP_ADDRESS>))", where v9.13.30 is the updated version, but the generated result is still the same. No sign of nullability, with or without ItemsCanBeNullAttribute.
What do I miss?

Can you post the spec of this "ParticipantsParts": { again? Is it still the same?

Absolutely
    "PurchaseReadDto2": {
      "type": "object",
      "additionalProperties": false,
      "properties": {
        "ParticipantsParts": {
          "type": "object",
          "additionalProperties": {
            "type": "number",
            "format": "decimal"
          }
        }
      }
    }

and
    [System.CodeDom.Compiler.GeneratedCode("NJsonSchema", "<IP_ADDRESS> (Newtonsoft.Json v<IP_ADDRESS>)")]
    public partial class PurchaseReadDto2
    {
        [Newtonsoft.Json.JsonProperty("ParticipantsParts", Required = Newtonsoft.Json.Required.Default, NullValueHandling = Newtonsoft.Json.NullValueHandling.Ignore)]
        public System.Collections.Generic.IDictionary<string, decimal> ParticipantsParts { get; set; }
        public string ToJson()
        {
            return Newtonsoft.Json.JsonConvert.SerializeObject(this);
        }
        public static PurchaseReadDto2 FromJson(string data)
        {
            return Newtonsoft.Json.JsonConvert.DeserializeObject<PurchaseReadDto2>(data);
        }
    }

I'll try AspNetCore Middleware (should have done that before) to elliminate possibility of update mess.

Same result. I installed NJsonSchema from nuget beside NSwag.AspNetCore

Is this Swagger 2 or OpenAPI 3? Because Swagger 2 does not know about null it might not work there...

Yes, it was Swagger 2 as it turns out now. I conjectured that if it could generate spec for simple nullable properties it will cope with Dictionary of nullables.
So if I add AddOpenApiDocument to middleware, the generated spec is
"PurchaseReadDto2": {
        "type": "object",
        "additionalProperties": false,
        "properties": {
          "participantsParts": {
            "type": "object",
            "nullable": true,
            "additionalProperties": {
              "type": "number",
              "format": "decimal",
              "nullable": true
            }
          }
        }
      }

which is probably the right thing.
Can I use this OpenApi in my tool chain the way I used swagger before from MSBuild: webapi2swagger to swagger2csclient? Could you give me any directions?
Thank you for your help!

In Swagger 2 we should generate a custom x-nullable property, so this should also work... need to check why this is not the case here.
OpenApi 3 should just work in the toolchain too, but there might be some edge cases which are not covered yet... but it is clearly the stuff which will get most attention in the future. It depends whether other non-nswag tools you’re using already support v3

Added another PR, but this might be a major breaking change.

Moved to OpenApi and aspnetcore2swagger from swagger and webapi2swagger.
Now I have the spec generated with "nullable" set to true as above, but the generated client code never changed:
[System.CodeDom.Compiler.GeneratedCode("NJsonSchema", "<IP_ADDRESS> (Newtonsoft.Json v<IP_ADDRESS>)")]
public partial class PurchaseReadDto2
{
    [Newtonsoft.Json.JsonProperty("ParticipantsParts", Required = Newtonsoft.Json.Required.Default, NullValueHandling = Newtonsoft.Json.NullValueHandling.Ignore)]
    public System.Collections.Generic.IDictionary<string, decimal> ParticipantsParts { get; set; }

Is there any setting for this?

Wow, you've found extremely nasty but which only applies to additional items and additional properties schemas... will be fixed in nswag v12.2 soon

Oh my! I got off easy! It could have attacked me)
All right, I have my workaround ("type": ["null", "number"]) for now.
I am looking forward to when you have fixed it. Many thanks!

Your hack is fine for some days, but type": ["null", "number"] is not valid in swagger nor in openapi

"will be fixed in nswag v12.2 soon" - and it was. Thank you!


[feature request] - Option to not save modes for buffers

I've been using persp-state-save and persp-state-load for a while now, and it works great. Except for one case, if there's some kind of issue or bug with a mode or elsip command it seems to be persisted into the persp-state-save and loaded up the following time. Generally one of the perspectives will also lose its named title and get a random string of numbers. So would it be possible to save the buffers and spaces but not included the running modes of said buffer?

persp-state-save avoids saving anything it cannot reliably restore. This includes all kinds of buffers, like shells, which do not have an associated file. It sounds like you ran into a mode that those heuristics don't catch. What mode have you run into with this problem? Can you help me reproduce it?


Haiyue chen terrain builder

A struct could be setup as a flower with the different colors/types as integer values that are manipulated by the get and set functions. Overall looks good!


[Settings] The "Car" app crashed after adding a photo when re-open the app.

Environment:  Samsung Galaxy S10e, Android 10
Reproducible: rarely, for "Delete avatar" also
Build found: 1.0.84
Preconditions
The "Car" app is opened
The "My Profile" page is opened
Steps to reproduce

Go to the 'Setting' page
Long press the avatar icon
Press on the "Add avatar"
Upload avatar photo
Close the "Car" app
Re-open the "Car" app
Observe the result

Actual result
The "Car" app crashed after adding a photo when re-open the app.
Expected result
The "Car" app crashed  must re-open
Labels to be added
"Bug" ("bug"), Priority ("pri: ")

https://user-images.githubusercontent.com/71496479/110704747-12156380-81fe-11eb-8b75-a9beb6c4f95c.mp4


move to Akka 2.4

but note that 2.4 build requires JDK 8, so the 2.11.x branch will need to stay on Akka 2.3
related, if not part and parcel: #146

this is high priority for Scala 2.12.0. details on the Akka team's own efforts at https://github.com/akka/akka/issues/20306

fixed by @szeiger in #262


[PRIORITY QUEUE]

#priority  QUEUES

[X] I have gone through the repository and made sure this data structure has not been implemented

IMPLEMENTATION OF PRIORITY QUEUE

priority QUEUE

C++

Is this your first contribution to this repository?
Yes

@developer22-university The issue statement is particularly not clear as to which DS you are going to implement. Is it a priority queue or a simple queue? Please update the issue.

hey I would like to implement prioirity queue using c++. So, do let me know!


🐛 BUG:

Which Cloudflare product(s) does this pertain to?
Other
What version(s) of the tool(s) are you using?
N/A
What version of Node are you using?
N/A
What operating system are you using?
Windows
Describe the Bug
Searching for test on https://miniflare.dev gives invalid results (takes you to a Not found page for every result clicked).

Please provide a link to a minimal reproduction
https://miniflare.dev/testing/jest/#writing-and-running-tests
Please provide any relevant error logs
No response

@demosjarco thanks for filing this issue. We need to update the search index. For now, Miniflare v3 does not support the unit testing environments that v2 did.


added shape property to SliverAppBar

re-open PR https://github.com/flutter/flutter/pull/31662 with @shihaohong
Description
added shape property in SilverAppBar widget, which was already implemented in AppBar widget
Related Issues
#31656

CLA updated

Closing this PR out, as it has been resolved with https://github.com/flutter/flutter/pull/33073. Thanks for your contribution @mtiziano


having same order in node resource unit in node finder and my nodes

Description
A clear description of the bug is:
Having node resource unit order consistency in both my nodes and node finder.

more info at https://github.com/threefoldtech/tfgrid-sdk-ts/issues/2258.
Must include any relevant identifiers, like:

Network: Dev

Version: 2.3.0-alpha12

Work In Progress :

working on issue

Verified, Devnet bd6c7c5.
The node resources are now consistent between the node finder and my nodes.

I found another bug and reported here.


[BEAM-11648] First step in creation of Vortex sink

I can help review on this PR

I can help review on this PR

friendly ping!

Sorry a bit delay on this PR.
I am pretty busy this week so I should be able to start review from next week.

Correct - this is refactoring + utility functions that have been split out of the main Vortex PR

Run Java PreCommit

Run Java PostCommit

Run Dataflow ValidatesRunner

LGTM. Thanks.


yo does not find angular-2-crud generator

Type of issue
yo does not find my generator

The generator is public and you have it in your repository with the name "angular-2-crud", but when I run
#yo angular-2-crud
You don't seem to have a generator with the name angular-2-crud installed.
But help is on the way:

You can see available generators via npm search yeoman-generator or via http://yeoman.io/generators/.
Install them with npm install generator-angular-2-crud.

If I run #yo doctor

Yeoman Doctor
Running sanity checks on your system

✔ Global configuration file is valid
✔ NODE_PATH matches the npm root
✔ Node.js version
✔ No .bowerrc file in home directory
✔ No .yo-rc.json file in home directory
✔ npm version

Everything looks all right!

If I run #yo and try to find the generator
? 'Allo gorums! What would you like to do? Install a generator
? Search npm for generators: angular-2-crud
? Here's what I found. Official generator → ෴
  Install one?
❯ angular-2-crud This app generate a CRUD for Angular2
  Search again
  Return home

but still the same error after the install above
My environment

OS version/details: Ubuntu 17.04
Node version: 8.0.0 (run node --version in your terminal)
npm version: 5.4.2 (run npm --version in your terminal)
Version of yo : 2.0.0 (run yo --version in your terminal)

Steps to reproduce the behavior
here the steps Github project
You don't seem to have a generator with the name “angular-2-crud” installed.
But help is on the way:

You can see available generators via npm search yeoman-generator or via http://yeoman.io/generators/.
Install them with npm install generator-angular-2-cru

Did you npm install -g  generator-angular-2-crud first?

Yes I did

Seems that that was was caused by updating to "yeoman-generator": "^2.0.0" without adapting the breaking changes.

Any link to know about "the breaking changes"?

@gorums https://github.com/yeoman/generator/releases/tag/v2.0.0
This generator can just downgrade the version if they don't plan to adjust for the new API. It'll continue to work as is.


Halcyon-based rename

Agreed, and I'll be probably going back through most of these and resetting to AnyCPU.


Add margin to code block to right side

I have added the margin to right side for code block that is bigger then screen:
Before:

After:

If I did it in wrong way, please feel free to add comments and I will change my PR.

Thanks. Yeap, it is a problem.
We use  for every code string in code block. Like:
function test

Why this PR will not create margin between s inside the line?
Maybe we can just add padding to .code-block itself?

Why this PR will not create margin between s inside the line?
I thought that one line is one span. But now I can see that this is not true.

Maybe we can just add padding to .code-block itself?

.code-block already has padding and it doesn't work.
.code-block {
    padding: 12px var(--text-side);
    margin-right: calc(var(--text-side)*-1);
    margin-bottom: 18px;
    margin-left: calc(var(--text-side)*-1);
    font-size: 14px;
}

So now I'm not sure how I we can fix it.

I think we can ignore the problem for now. Adding extra wrapper could slow down API pages with many examples.
Feel free to send another PR if you find a way.

Sure. It make sens. Thanks 👍


Add sql workflows for the Guest OS pipeline migration

The 28 SQL server build workflows is part of the pipeline migration to Concourse.
/cc @bkatyl

Previous PR was: https://github.com/GoogleCloudPlatform/compute-image-tools/pull/1785


Faster full screen.

I enjoy the very fast (no animation) full screen behavior in iTerm/MacVim etc. I think hyperterm should have an option to allow full-screening very quickly.

Agreed! I think the default iterm command is Cmd+Enter.


Font Smoothing flickers when auto-savings on OS X and Safari

OS: OS X 10.10
Browser: Safari
When editing or composing a new post, whenever an auto-save draft is triggered the font-smoothing goes away and all the text appears thinner (see screenshot). This causes the text to flicker every time that a draft is saved. It's a very distracting experience.
(the flicker happens at the end of the gift, maybe 15-20 seconds in).

I can't reproduce this bug on master

This is because the save button spinner is using a transform in the animation. Adding "-webkit-transform: translate3d(0,0,0)" to the rendered-markdown will stop the flickering, however it will also change the appearance of the rendered text to the lighter weight. Googling "safari translate3d text flicker" will return a lot of results around this.

I believe this has been fixed in Safari 9 as I'm unable to reproduce it.

Same!
On Wed, Oct 7, 2015 at 10:18 AM Kevin Ansfield<EMAIL_ADDRESS>wrote:

I believe this has been fixed in Safari 9 as I'm unable to reproduce it.
—
Reply to this email directly or view it on GitHub
https://github.com/TryGhost/Ghost/issues/5901#issuecomment-146249557.

In that case, I'm gonna close the issue. No need to add a workaround for a browser bug that's already fixed by the vendor :wink:


[KOGITO-5102] - Long KogitoRuntime Name + Namespace causes Route Error in KogitoRuntime

See: https://issues.redhat.com/browse/KOGITO-5102
Description
When deploying a KogitoRuntime on OpenShift where <name>-<namespace> combined is longer than 63 characters, Kogito fails to create a route because the host does not conform to DNS 1123 naming conventions.
For this fix I added a spec.host field to the KogitoRuntime CRD to allow users to manually set a custom host. In addition, the host input is validated before route creation and defaults to the original route creation steps if host is invalid.
Many thanks for submitting your Pull Request :heart:!
Please make sure your PR meets the following requirements:

[x] You have read the contributors' guide
[x] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[x] Pull Request contains a link to the JIRA issue
[x] Pull Request contains a description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket
[x] Your feature/bug fix has a unit test that verifies it
[x] You've ran make before-pr and everything is working accordingly
[x] You've tested the new feature/bug fix in an actual OpenShift cluster
[x] You've added a RELEASE_NOTES.md entry regarding this change

Can one of the admins verify this patch?

Unfortunately not working as expected on OCP. When I create:
apiVersion: app.kiegroup.org/v1beta1
kind: KogitoRuntime
metadata:
  name: example-quarkus
spec:
  image: quay.io/kiegroup/examples-process-quarkus-example-nightly:latest
  host: "test.hostname.com"

I get an error:
{"level":"error","ts":1629797259.442733,"logger":"controller","msg":"Reconciler error","reconcilerGroup":"app.kiegroup.org","reconcilerKind":"KogitoRuntime","controller":"kogitoruntime","name":"example-quarkus","namespace":"ksuta-test","error":"Route.route.openshift.io \"example-quarkus\" is invalid: spec.host: Forbidden: you do not have permission to set the host field of the route","stacktrace":....

The issue seems to come from missing permission, see https://github.com/openshift/origin/issues/22612
The question is whether it has sense to provide such permissions or rather address route configuration in different way based on discussions in https://issues.redhat.com/browse/KOGITO-4730

Works as expected now.
/jenkins test

While the PR works as expected, I think that we should clarify how to represent the hostname in CR related to https://issues.redhat.com/browse/KOGITO-4730. If we will change the structure later to include skipping Route creation or TSL specification then we introduce backward incompatibilities.

will be addressed as part of https://issues.redhat.com/browse/KOGITO-5903


Do I have to stop watching when entering Foreground?

Could you describe how the plugin works? I'm interested in only listening the location while being on background, does the Plugin already handles this? Does it only activate when App enters background mode, and stops when it enters foreground mode? Or do I have to detect this transitions myself and do addWatcher / removeWatcher accordingly?

For your use case, you will have to detect those transitions yourself. The plugin is capable of working in foreground-only by simply omitting the "backgroundMessage" option, but alas not background-only.


Support for automatically generating getter and setter

I couldn't find this issue already existing. I was starting to make variable public just to avoid the setter/getter manual writing, I knew it was time to look for something. Luckily someone beat me to it
https://marketplace.visualstudio.com/items?itemName=DSKWRK.vscode-generate-getter-setter
perhaps this code can be integrated in the mainline, or use as a basis for this new functionality.

@waderyan this should come from the TS team.

This issue was moved to Microsoft/TypeScript#12417


Question: should updating the query cache cause a hook to re-render?

I am using a hook for a query that returns items in a list. Elsewhere, i use writeQuery on the cache to update the cached value for the query. My expectation is that this would trigger the hook to re-render. Is something wrong with my usage, or is this not supported?

something wrong with my usage. disregard!


ATS is not closing the connection

https://quic-tracker.info.ucl.ac.be/traces/20180322/0 asserts the correct behavior of the host when encountering an unsupported TLS version (TLS 1.3 draft-00), i.e. closing the connection with error code TLS_HANDSHAKE_FAILED (0x201). ATS is not closing the connection.

quic-tracker reported this and I could reproduced this with latest quic-latest branch (a34cac14b4bd89e83efd9fbcee1401a85a865e11)

Fixed by https://github.com/apache/trafficserver/commit/71a69310413b5137f4d54d97cb0f5061447ba056


Update issue descriptions

Update descriptions slightly so they make more sense when displayed by the current versions of truffle+analyze and sabre.

Seems like this is not passing tests because of signatures.json mismatch. Is there a default signatures.json I can use to generate the expected outputs?

You can replace your own signatures.json with:
tests/mythril_dir/signatures.json.example, that will give the correct results


additional homepage blocks

Complete Homepage

[x] Profile
[x] Skills

Section add with skills and Profile


unsafe impl Send+Sync for Submitter, SubmissionQueue, CompletionQueue

The IoUring type already has Send + Sync impls.
In tokio-epoll-uring, we use split() and need the Submitter, SubmissionQueue and CompletionQueue to be Send (not sync, though).
This PR adds those unsafe impls, and adds hopefully not too repetitive commentary on why these impls are safe.

Co-authored-by: Conrad Ludgate<EMAIL_ADDRESS>Cherry picked from commit https://github.com/neondatabase/fork--tokio-rs--io-uring/commit/bbc5a0c5f6cde9051037ec2fcc648cbadb7a80b4

You seem to have to use unsafe to get &'static mut or use scope thread to make sense. I would recommend submission_shared and completion_shared.

Sorry, I'm not following. Who's talking about &'static mut ?

I would recommend submission_shared and completion_shared.

The unsafe impls proposed in this PR allow movement of Submitter, SubmissionQueue, and CompletionQueue, to different threads in consuming code, without any unsafe.
I consider that strictly better than the unsafe fn submission_shared() and unsafe fn completion_shared().

This would be useful in my project as well


LSNBLDR-816: Boolean property to control the display of media downloa…

…d links

Cool, I'd just update the PR title/message since there's no property anymore.


(Swift) Letter c is a built-in?

In the following snippet:
func max(_ a: Double, _ b: Double, _ c: Double) -> Double {
  if a > b {
    return a > c ? a : c
  } else {
    return b > c ? b : c
  }
}

The parameter c is incorrectly highlighted as a built-in.

This seems to result from https://github.com/highlightjs/highlight.js/blob/760dcd6080ba4ef7763ff1deff250530efa1dc94/src/languages/swift.js#L26
No idea what that c is doing there. There is no variable or function with that name in the Standard Library.

I asked @mportiz08 if they know anything about this and whether it could be merged into their PR.  If no one knows what it's for then does seem like something we could just yank.

I'd be ok with a PR to remove this it's definitely not a general purpose keyword.

@joshgoebel When I finish the project I'm working on, I'll see if I can fix some of the Swift issues I've reported myself.

@joshgoebel What do you think about removing the list of built-ins all together?
I looked into updating them, however, I now feel like we should just remove them. In Swift, functions can be overloaded not only on the number and types of their parameters, but also on the parameter names. Using only a function's base name to highlight it will lead to many false matches. Proper highlighting would require a type checker.

I now feel like we should just remove them. In Swift, functions can be overloaded not only on the number and types of their parameters, but also on the return type and on the parameter names. Using only a function's base name to highlight it will lead to many false matches.

Removing a large swath of keywords makes auto-detection worse for the whole library, so generally it's frowned upon.
Can you give a few specific examples of the type of issues you're imagining?  Or is this c issue truly representative?  Typically for something like this we'd add a rule to eliminate false positives.  If these are built-in functions could we match then as built_in(...) so there would be no false positives unless the built-in was immediately proceeded by a (, etc?

I'm only talking about the global functions in the Standard Library here, not keywords.
The problem is that Swift has now moved most functions into types as methods, and the few functions that remain global often have general names such as min, max, zip, print, stride, sequence etc. These aren't reserved names, so you can declare variables with that name, or even other global functions, as long as they are valid overloads.
For example, here's my best attempt at generating a current list of public global functions in the standard library. These show the number of parameters and their argument labels (_ means unlabeled), but not the parameter types or return type:
 abs(_:)
 all(_:)
 any(_:)
 assert(_:_:file:line:)
 assertionFailure(_:file:line:)
 debugPrint(_:separator:terminator:)
 debugPrint(_:separator:terminator:to:)
 dump(_:name:indent:maxDepth:maxItems:)
 dump(_:to:name:indent:maxDepth:maxItems:)
 fatalError(_:file:line:)
 getVaList(_:)
 isKnownUniquelyReferenced(_:)
 max(_:_:)
 max(_:_:_:_:)
 min(_:_:)
 min(_:_:_:_:)
 numericCast(_:)
 pointwiseMax(_:_:)
 pointwiseMin(_:_:)
 precondition(_:_:file:line:)
 preconditionFailure(_:file:line:)
 print(_:separator:terminator:)
 print(_:separator:terminator:to:)
 readLine(strippingNewline:)
 repeatElement(_:count:)
 sequence(first:next:)
 sequence(state:next:)
 stride(from:through:by:)
 stride(from:to:by:)
 swap(_:_:)
 swift_unboxFromSwiftValueWithType(_:_:)
 transcode(_:_:_:_:stopOnError:)
 transcode(_:from:to:stoppingOnError:into:)
 type(of:)
 unsafeBitCast(_:to:)
 unsafeDowncast(_:to:)
 withExtendedLifetime(_:_:)
 withUnsafeMutablePointer(to:_:)
 withUnsafePointer(to:_:)
 withVaList(_:_:)
 withoutActuallyEscaping(_:do:)
 zip(_:_:)

I don't think a regex grammar can match these correct, and false positives are extremely confusing for new learners, which is why I'd rather not see them highlighted at all.

I'm only talking about the global functions in the Standard Library here, not keywords.

Yes, I understood.

I don't think a regex grammar can match these correctly, and false positives are extremely confusing for new learners,

It might actually be fun to try with some type of fuzzy look-ahead actually, but I take your larger point.

which is why I'd rather not see them highlighted at all.

Now highlighting them or not is a different question entirely. :-)  Though my fear with that line of thinking is that without any visual indication it becomes harder to keep the grammar up-to-date over time (as the language evolves, etc).

@joshgoebel Is there a way to tell the parser to only match built-ins if they are followed by an opening brace? I only see one $pattern for all of the keywords.
If not, can I just make a separate mode for these (with class name built_in)?
Also, feel free to assign this to me, I'll fix it anyway now that I have a list of built-ins :)

Is there a way to tell the parser to only match built-ins if they are followed by an opening brace? I only see one $pattern for all of the keywords.

Nope, you'd need a rule for that kind of customization, as you've already realized.  beginKeywords already has this . inspection voodoo built-in though....
Also related: https://github.com/highlightjs/highlight.js/issues/2500
I'd rather see us go ahead and just add a matcher for x.dispatch() though then you won't need all this complexity... you just have one rule to match obj.dispatch() in general, then a second rule to match built-ins.... actually at that point the keyword support may "just work" without needing any other changes.

Would you accept the suggested rule above for now? It solves 99% of the issues I have with built-ins being incorrectly highlighted. The remaining 1% would be overloads with the same name as a built-in, which I don't think we can detect with regexes.

I suggested what I did because often that's how we prefer to solve this.  For example see JS:
      // hack: prevents detection of keywords in some circumstances
      // .keyword()
      // $keyword = x
      {
        variants: [
          { begin: '\\.' + IDENT_RE },
          { begin: '\\$' + IDENT_RE }
        ],
        relevance: 0
      },

This is much easier to understand (since you're version would even be simpler):
{ // consume .built_in
begin: regex.concat(/\./, either(...builtIns), /\(/)
relevance: 0,
}

A ruleset with more rules but simpler rules is far better than a rule set with fewer but very complex rules.  And again this is also very compatible with the future direction to turn this into a "dispatch" rule...

Fixed in https://github.com/highlightjs/highlight.js/pull/2908


wrong-number-of-arguments in shell-maker mode

Sending a question through shell-maker-model fails with the following backtrace:
Debugger entered--Lisp error: (wrong-number-of-arguments ((t) (command shell) "Callback for Copilot Chat shell-maker.\nArgument CO..." (progn (setq copilot-chat--shell-cb-fn (apply-partially #'copilot-chat--shell-cb-prompt-wrapper shell)) (setq copilot-chat--shell-maker-answer-point (point))) (let ((inhibit-read-only t)) (save-current-buffer (set-buffer copilot-chat--shell-maker-temp-buffer) (erase-buffer))) (copilot-chat--ask command copilot-chat--shell-cb-fn)) 4)
  copilot-chat--shell-cb(#("ping" 0 4 (fontified t)) (("ping")) (closure ((response-count . 0) (suffix-newline . "\n\n") (prefix-newline . "") (buffer . #<buffer *Copilot-chat*>) (no-announcement) (on-output) (input-string . #("ping" 0 4 (fontified t)))) (response partial) (setq response-count (1+ response-count)) (setq prefix-newline (if (> response-count 1) "" "\n")) (if response (if partial (progn (shell-maker--write-partial-reply (concat prefix-newline response)) (setq shell-maker--busy partial) (if on-output (progn (funcall on-output input-string response nil nil)))) (shell-maker--write-reply (concat prefix-newline response suffix-newline)) (if no-announcement nil (shell-maker--announce-response buffer)) (setq shell-maker--busy nil) (shell-maker--write-input-ring-history) (if (progn (or (progn ...) (signal ... ...)) (aref shell-maker--config 6)) (progn (if on-output (progn ...)) (funcall (progn ... ...) input-string (shell-maker-last-output)))) (goto-char (point-max))) (shell-maker--write-reply "Error: that's all is known" t) (setq shell-maker--busy nil) (if no-announcement nil (shell-maker--announce-response buffer)) (if on-output (progn (funcall on-output input-string (shell-maker-last-output) t t))))) (closure ((errored) (suffix-newline . "\n\n") (buffer . #<buffer *Copilot-chat*>) (no-announcement) (on-output) (input-string . #("ping" 0 4 (fontified t)))) (error) (if errored nil (shell-maker--write-reply (concat (string-trim error) suffix-newline) t) (setq errored t)) (setq shell-maker--busy nil) (if no-announcement nil (shell-maker--announce-response buffer)) (if on-output (progn (funcall on-output input-string error t t))) (if (progn (or (progn (and (memq ... cl-struct-shell-maker-config-tags) t)) (signal 'wrong-type-argument (list 'shell-maker-config shell-maker--config))) (aref shell-maker--config 6)) (progn (funcall (progn (or (progn ...) (signal ... ...)) (aref shell-maker--config 6)) input-string error) (goto-char (point-max))))))
  funcall(copilot-chat--shell-cb #("ping" 0 4 (fontified t)) (("ping")) (closure ((response-count . 0) (suffix-newline . "\n\n") (prefix-newline . "") (buffer . #<buffer *Copilot-chat*>) (no-announcement) (on-output) (input-string . #("ping" 0 4 (fontified t)))) (response partial) (setq response-count (1+ response-count)) (setq prefix-newline (if (> response-count 1) "" "\n")) (if response (if partial (progn (shell-maker--write-partial-reply (concat prefix-newline response)) (setq shell-maker--busy partial) (if on-output (progn (funcall on-output input-string response nil nil)))) (shell-maker--write-reply (concat prefix-newline response suffix-newline)) (if no-announcement nil (shell-maker--announce-response buffer)) (setq shell-maker--busy nil) (shell-maker--write-input-ring-history) (if (progn (or (progn ...) (signal ... ...)) (aref shell-maker--config 6)) (progn (if on-output (progn ...)) (funcall (progn ... ...) input-string (shell-maker-last-output)))) (goto-char (point-max))) (shell-maker--write-reply "Error: that's all is known" t) (setq shell-maker--busy nil) (if no-announcement nil (shell-maker--announce-response buffer)) (if on-output (progn (funcall on-output input-string (shell-maker-last-output) t t))))) (closure ((errored) (suffix-newline . "\n\n") (buffer . #<buffer *Copilot-chat*>) (no-announcement) (on-output) (input-string . #("ping" 0 4 (fontified t)))) (error) (if errored nil (shell-maker--write-reply (concat (string-trim error) suffix-newline) t) (setq errored t)) (setq shell-maker--busy nil) (if no-announcement nil (shell-maker--announce-response buffer)) (if on-output (progn (funcall on-output input-string error t t))) (if (progn (or (progn (and (memq ... cl-struct-shell-maker-config-tags) t)) (signal 'wrong-type-argument (list 'shell-maker-config shell-maker--config))) (aref shell-maker--config 6)) (progn (funcall (progn (or (progn ...) (signal ... ...)) (aref shell-maker--config 6)) input-string error) (goto-char (point-max))))))
  (cond ((string-equal "help" (string-trim input-string)) (shell-maker--print-help) (setq shell-maker--busy nil)) ((string-equal "clear" (string-trim input-string)) (call-interactively #'comint-clear-buffer) (shell-maker--output-filter (shell-maker--process) (shell-maker-prompt shell-maker--config)) (setq shell-maker--busy nil) (set-buffer-modified-p nil)) ((string-equal "config" (string-trim input-string)) (shell-maker--write-reply (shell-maker--dump-config shell-maker--config)) (setq shell-maker--busy nil)) ((not (shell-maker--curl-version-supported)) (shell-maker--write-reply "\nYou need curl version 7.76 or newer.\n\n") (setq shell-maker--busy nil)) ((and (progn (or (progn (and (memq ... cl-struct-shell-maker-config-tags) t)) (signal 'wrong-type-argument (list 'shell-maker-config shell-maker--config))) (aref shell-maker--config 4)) (funcall (progn (or (progn (and ... t)) (signal 'wrong-type-argument (list ... shell-maker--config))) (aref shell-maker--config 4)) input-string)) (shell-maker--write-reply (concat "\n" (funcall (progn (or (progn ...) (signal ... ...)) (aref shell-maker--config 4)) input-string) "\n\n")) (setq shell-maker--busy nil)) ((string-empty-p (string-trim input-string)) (shell-maker--output-filter (shell-maker--process) (concat "\n" (shell-maker-prompt shell-maker--config))) (setq shell-maker--busy nil)) (t (shell-maker--output-filter (shell-maker--process) (propertize "<shell-maker-end-of-prompt>" 'invisible (not shell-maker--show-invisible-markers))) (funcall (progn (or (progn (and (memq ... cl-struct-shell-maker-config-tags) t)) (signal 'wrong-type-argument (list 'shell-maker-config shell-maker--config))) (aref shell-maker--config 5)) input-string (shell-maker--extract-history (save-current-buffer (set-buffer buffer) (buffer-string)) (shell-maker-prompt-regexp shell-maker--config)) #'(lambda (response partial) (setq response-count (1+ response-count)) (setq prefix-newline (if (> response-count 1) "" "\n")) (if response (if partial (progn ... ... ...) (shell-maker--write-reply ...) (if no-announcement nil ...) (setq shell-maker--busy nil) (shell-maker--write-input-ring-history) (if ... ...) (goto-char ...)) (shell-maker--write-reply "Error: that's all is known" t) (setq shell-maker--busy nil) (if no-announcement nil (shell-maker--announce-response buffer)) (if on-output (progn ...)))) #'(lambda (error) (if errored nil (shell-maker--write-reply (concat ... suffix-newline) t) (setq errored t)) (setq shell-maker--busy nil) (if no-announcement nil (shell-maker--announce-response buffer)) (if on-output (progn (funcall on-output input-string error t t))) (if (progn (or ... ...) (aref shell-maker--config 6)) (progn (funcall ... input-string error) (goto-char ...)))))))
  (if shell-maker--busy nil (setq shell-maker--busy t) (cond ((string-equal "help" (string-trim input-string)) (shell-maker--print-help) (setq shell-maker--busy nil)) ((string-equal "clear" (string-trim input-string)) (call-interactively #'comint-clear-buffer) (shell-maker--output-filter (shell-maker--process) (shell-maker-prompt shell-maker--config)) (setq shell-maker--busy nil) (set-buffer-modified-p nil)) ((string-equal "config" (string-trim input-string)) (shell-maker--write-reply (shell-maker--dump-config shell-maker--config)) (setq shell-maker--busy nil)) ((not (shell-maker--curl-version-supported)) (shell-maker--write-reply "\nYou need curl version 7.76 or newer.\n\n") (setq shell-maker--busy nil)) ((and (progn (or (progn (and ... t)) (signal 'wrong-type-argument (list ... shell-maker--config))) (aref shell-maker--config 4)) (funcall (progn (or (progn ...) (signal ... ...)) (aref shell-maker--config 4)) input-string)) (shell-maker--write-reply (concat "\n" (funcall (progn (or ... ...) (aref shell-maker--config 4)) input-string) "\n\n")) (setq shell-maker--busy nil)) ((string-empty-p (string-trim input-string)) (shell-maker--output-filter (shell-maker--process) (concat "\n" (shell-maker-prompt shell-maker--config))) (setq shell-maker--busy nil)) (t (shell-maker--output-filter (shell-maker--process) (propertize "<shell-maker-end-of-prompt>" 'invisible (not shell-maker--show-invisible-markers))) (funcall (progn (or (progn (and ... t)) (signal 'wrong-type-argument (list ... shell-maker--config))) (aref shell-maker--config 5)) input-string (shell-maker--extract-history (save-current-buffer (set-buffer buffer) (buffer-string)) (shell-maker-prompt-regexp shell-maker--config)) #'(lambda (response partial) (setq response-count (1+ response-count)) (setq prefix-newline (if ... "" "\n")) (if response (if partial ... ... ... ... ... ... ...) (shell-maker--write-reply "Error: that's all is known" t) (setq shell-maker--busy nil) (if no-announcement nil ...) (if on-output ...))) #'(lambda (error) (if errored nil (shell-maker--write-reply ... t) (setq errored t)) (setq shell-maker--busy nil) (if no-announcement nil (shell-maker--announce-response buffer)) (if on-output (progn ...)) (if (progn ... ...) (progn ... ...)))))))
  (let ((buffer (shell-maker-buffer shell-maker--config)) (prefix-newline "") (suffix-newline "\n\n") (response-count 0) (errored)) (if shell-maker--busy nil (setq shell-maker--busy t) (cond ((string-equal "help" (string-trim input-string)) (shell-maker--print-help) (setq shell-maker--busy nil)) ((string-equal "clear" (string-trim input-string)) (call-interactively #'comint-clear-buffer) (shell-maker--output-filter (shell-maker--process) (shell-maker-prompt shell-maker--config)) (setq shell-maker--busy nil) (set-buffer-modified-p nil)) ((string-equal "config" (string-trim input-string)) (shell-maker--write-reply (shell-maker--dump-config shell-maker--config)) (setq shell-maker--busy nil)) ((not (shell-maker--curl-version-supported)) (shell-maker--write-reply "\nYou need curl version 7.76 or newer.\n\n") (setq shell-maker--busy nil)) ((and (progn (or (progn ...) (signal ... ...)) (aref shell-maker--config 4)) (funcall (progn (or ... ...) (aref shell-maker--config 4)) input-string)) (shell-maker--write-reply (concat "\n" (funcall (progn ... ...) input-string) "\n\n")) (setq shell-maker--busy nil)) ((string-empty-p (string-trim input-string)) (shell-maker--output-filter (shell-maker--process) (concat "\n" (shell-maker-prompt shell-maker--config))) (setq shell-maker--busy nil)) (t (shell-maker--output-filter (shell-maker--process) (propertize "<shell-maker-end-of-prompt>" 'invisible (not shell-maker--show-invisible-markers))) (funcall (progn (or (progn ...) (signal ... ...)) (aref shell-maker--config 5)) input-string (shell-maker--extract-history (save-current-buffer (set-buffer buffer) (buffer-string)) (shell-maker-prompt-regexp shell-maker--config)) #'(lambda (response partial) (setq response-count ...) (setq prefix-newline ...) (if response ... ... ... ... ...)) #'(lambda (error) (if errored nil ... ...) (setq shell-maker--busy nil) (if no-announcement nil ...) (if on-output ...) (if ... ...)))))))
  shell-maker--eval-input(#("ping" 0 4 (fontified t)) nil nil)
  (let (shell-maker--input) (comint-send-input) (shell-maker--eval-input shell-maker--input on-output no-announcement))
  shell-maker--send-input()
  shell-maker-submit()
  funcall-interactively(shell-maker-submit)
  command-execute(shell-maker-submit)

Steps to reproduce:

Set front end to 'shell-maker
Run M-x copilot-chat-display
Enter any prompt, e.g. "ping" and press enter

Version tested: commit:8f0dcb8 under emacs 29.4

What version of shell-maker are you using ? They changed the argument number of the callback and this could be the issue. Can you try to update shell-maker ?

shell-maker seems to have moved to a dedicated repository. It is no more a part of chatgpt-shell and I have some issues with dependencies with melpa but it works with some warnings.

Thanks! I manually updated shell-maker.el which solved the problem!