primordic/IssueDupesLite huggingface dataset:
Repository: helm/helm

Issue #5826: Feature request: helm 3 custom rendering engine
Created: 2019-05-31T18:56:48Z
I'm a maintainer of the helm-operator that is built into the Operator SDK, and I've been experimenting with the Helm 3 alpha libraries.
Using Helm 2 libraries, we are able to provide a custom implementation of tiller's environment.Engine interface to our tiller instance so that we can inject owner references into the release manifest.

  
    
      helm/pkg/tiller/environment/environment.go
    
    
        Lines 95 to 101
      in
      500f46b
    
  
  
    

        
          
           type Engine interface { 
        

        
          
           	// Render renders a chart. 
        

        
          
           	// 
        

        
          
           	// It receives a chart, a config, and a map of overrides to the config. 
        

        
          
           	// Overrides are assumed to be passed from the system, not the user. 
        

        
          
           	Render(*chart.Chart, chartutil.Values) (map[string]string, error) 
        

        
          
           } 
        
    
  


In Helm 3, it appears this interface is removed and there is not currently a way to customize the engine that is used to render the manifest. For example, the install action calls the global Render function in the engine package, which uses the default go templating engine.

  
    
      helm/pkg/action/install.go
    
    
         Line 323
      in
      2a3b7b5
    
  
  
    

        
          
           files, err := engine.Render(ch, values) 
        
    
  



  
    
      helm/pkg/engine/engine.go
    
    
        Lines 66 to 68
      in
      2a3b7b5
    
  
  
    

        
          
           func Render(chrt *chart.Chart, values chartutil.Values) (map[string]string, error) { 
        

        
          
           	return new(Engine).Render(chrt, values) 
        

        
          
           } 
        
    
  


I know there are plans to support a Lua templating engine, so I'm wondering if there are also plans to add an Engine interface back into Helm 3 and update the actions to be able to use it?
If so, I'd be willing to work on a PR for this.

Duplicate issue #5779: helm 3: allow adding custom template functions to engine
Created: 2019-05-22T14:56:48Z
At our company, we're using a custom utility to build/deploy our helm charts:
https://github.com/blendle/kubecrt
I've been experimenting with upgrading this utility to the Helm 3 alpha.
Unfortunately, it seems like v3 no longer provides access to the map of functions that will be used when rendering the charts.
Specifically, we add (back) the env and expandenv functions, as they provide us with the flexibility needed for our (private) deployment pipeline.
Whereas in 2.x, we could access those functions using renderer.FuncMap, it seems like they are now made private, and we're unable to modify them.
Any thoughts on making this use-case possible again?

Closing comment (2019-08-13T23:25:52Z): dupe of #5826
Repository: heroku/legacy-cli

Issue #634: failed to push some refs to 'git@heroku.com:myproject.git'
Created: 2012-11-15T05:46:38Z
heroku push failed with the following error..
  Auto packing the repository for optimum performance.
  Connection to heroku.com closed by remote host.
  To git@heroku.com:myproject.git
      7c6460b..caaabf7 master -> master
  error:  failed to push some refs to 'git@heroku.com:myproject.git'

Duplicate issue #612: unable to push the code
Created: 2012-10-24T10:25:55Z
i got  this following error when i push my code to the heroku server,
  Auto packing the repository for optimum performance.
  Connection to heroku.com closed by remote host.
  To git@heroku.com:myproject.git
      7c6460b..caaabf7 master -> master
  error:  failed to push some refs to 'git@heroku.com:myproject.git'

Closing comment (2012-12-12T06:24:06Z): Duplicate of #634.
Repository: heroku/legacy-cli

Issue #943: Running a pg command without specifying an app gives "internal service error"
Created: 2013-11-07T22:20:03Z
Running a pg command fails if you don't specify an app:
$ heroku pg:info
 !    Internal server error.
 !    Run `heroku status` to check for known platform issues.

This seems to happen even if you're in an app directory.
But it can be fixed by manually specifying an app:
$ heroku pg:info --app jacobian
=== HEROKU_POSTGRESQL_VIOLET_URL (DATABASE_URL)
...

Duplicate issue #973: pg commands fail with "Internal Server Error" when no app specified
Created: 2013-12-16T22:32:39Z
maciek@gamera:~$ heroku pg:psql
 !    Internal server error.
 !    Run `heroku status` to check for known platform issues.
(if an incorrect app is specified, you do get a clearer error).
It looks like this is because the request goes to :path=>"/apps//attachments", which returns a 404:
excon.error  {:error=>#<Excon::Errors::NotFound: Expected(200) <=> Actual(404 Not Found)>}

I think we can fix this by ensuring we have a valid app_name as we call Resolver#resolve, but I'm not sure what the best way to do that is.

Closing comment (2013-12-16T22:38:23Z): Duplicate of #943 yeah?
I "patched" that with #964 but it's ugly and @pedro thinks I'm a fool now!
Repository: heroku/legacy-cli

Issue #748: Feature request: `heroku fork` should copy the git repo
Created: 2013-04-06T08:27:57Z
After a short discussion on a support ticket @friism suggested I open an issue here.
From the ticket:

I noticed that it doesn't copy the git repo to the new app so if I manually push to the forked app I need to re-push the entire repo. This is a problem with our ~100mb repo. Any chance you could make it copy the repo across?

Duplicate issue #754: Fork does not clone the repo, only the application
Created: 2013-04-10T12:08:31Z
$  hs fork -a my-app clone-my-app                                                                                                                                                                                 
Creating fork clone-my-app... done
Copying slug... done
Adding cloudant:argon... done
Adding newrelic:standard... done
Adding papertrail:choklad... done
Adding redistogo:mini... done
Adding sendgrid:starter... done
Copying config vars... done
Fork complete, view it at http://clone-my-app.herokuapp.com/

$  git clone git@heroku.com:clone-my-app.git                                                                                                                                                                          
Cloning into 'clone-my-app'...
warning: You appear to have cloned an empty repository.

Closing comment (2013-04-11T20:52:47Z): Dup of #748
Repository: heroku/legacy-cli

Issue #302: Encoding error during login
Created: 2012-05-02T22:59:46Z
(from the heroku google group)
Hi,

I have download and installed Heroku toolbelt and tried to login but I
got the following error once I entered my password. For your
information I already had Git (1.7.10.msysgit.1) and Play framework
(1.2.4) already installed on my PC.

See 'git help <command>' for more information on a specific command.

C:\Users\a*******\workspace_java\StudentApp>heroku login
Enter your Heroku credentials.
Email: *******@******
Password (typing will be hidden):
C:/Program Files (x86)/Heroku/lib/heroku/auth.rb:216:in `glob': code
converter not found (UTF-16LE to IBM737) (Encoding::ConverterNotFoundError)
from C:/Program Files (x86)/Heroku/lib/heroku/auth.rb:216:in `associate_or_generate_ssh_key'
from C:/Program Files (x86)/Heroku/lib/heroku/auth.rb:212:in `check_for_associated_ssh_key'
from C:/Program Files (x86)/Heroku/lib/heroku/auth.rb:206:in `ask_for_and_save_credentials'
from C:/Program Files (x86)/Heroku/lib/heroku/auth.rb:59:in `get_credentials'
from C:/Program Files (x86)/Heroku/lib/heroku/auth.rb:22:in `login'
from C:/Program Files (x86)/Heroku/lib/heroku/command/auth.rb:12:in `login'
from C:/Program Files (x86)/Heroku/lib/heroku/command.rb:148:in `run'
from C:/Program Files (x86)/Heroku/lib/heroku/cli.rb:9:in `start'
from C:/Program Files (x86)/Heroku/bin/heroku:28:in `<main>'

Duplicate issue #794:  code converter not found (UTF-16LE to Windows-1258)
Created: 2013-05-14T03:27:18Z
Error:       code converter not found (UTF-16LE to Windows-1258) (Encoding::ConverterNotFoundError)
Backtrace:   c:/Program Files/Heroku/lib/heroku/command.rb:13:in `[]'
             c:/Program Files/Heroku/lib/heroku/command.rb:13:in `load'
             c:/Program Files/Heroku/lib/heroku/cli.rb:27:in `start'
             c:/Program Files/Heroku/bin/heroku:29:in `<main>'

Command:     heroku update
Version:     heroku/toolbelt/2.39.0 (i386-mingw32) ruby/1.9.3

Closing comment (2016-12-02T20:15:36Z): Is this a duplicate of #731?
(They both seem similar to #302, but the issue creation dates make me think that the resolution to #302 evidently didn't completely resolve #731 and this one.)
//cc @katukun @geemus
Repository: heroku/legacy-cli

Issue #1063: heroku fork fails for v3.6 of heroku client
Created: 2014-03-21T01:42:13Z
Running heroku fork dies for me.  I'm running v3.6 of the client, which I presume is the latest version:
› heroku update
Updating from 3.6.0... done, nothing to update
Here's the exception/trace info:
Original exception below:
 !    Heroku client internal error.
 !    Search for help at: https://help.heroku.com
 !    Or report a bug at: https://github.com/heroku/heroku/issues/new

    Error:       undefined method `[]' for nil:NilClass (NoMethodError)
    Backtrace:   /Users/dgehrett/.heroku/client/lib/heroku/command/fork.rb:67:in `block in index'
                 /Users/dgehrett/.heroku/client/lib/heroku/command/fork.rb:55:in `each'
                 /Users/dgehrett/.heroku/client/lib/heroku/command/fork.rb:55:in `index'
                 /Users/dgehrett/.heroku/client/lib/heroku/command.rb:218:in `run'
                 /Users/dgehrett/.heroku/client/lib/heroku/cli.rb:28:in `start'
                 /usr/bin/heroku:24:in `<main>'

    Command:     heroku fork -a movingcompanyreviews-stage
    Version:     heroku-toolbelt/3.6.0 (x86_64-darwin10.8.0) ruby/1.9.3

Duplicate issue #1064: Fork failed due to nil object
Created: 2014-03-21T17:19:38Z
Error:       undefined method `[]' for nil:NilClass (NoMethodError) 
Backtrace:   /Users/ben/.heroku/client/lib/heroku/command/fork.rb:67:in `block in index'
             /Users/ben/.heroku/client/lib/heroku/command/fork.rb:55:in `each'
             /Users/ben/.heroku/client/lib/heroku/command/fork.rb:55:in `index'
             /Users/ben/.heroku/client/lib/heroku/command.rb:218:in `run'
             /Users/ben/.heroku/client/lib/heroku/cli.rb:28:in `start'
             /usr/local/heroku/bin/heroku:24:in `<main>'

Command:     heroku fork -a givegab-demo givegab-rails4
Plugins:     heroku-pg-extras
Version:     heroku-toolbelt/3.6.0 (x86_64-darwin10.8.0) ruby/1.9.3

Closing comment (2014-03-21T20:54:12Z): Duplicate of #1063 see there for more
Repository: heroku/legacy-cli

Issue #1065: undefined method `get_attachments' on pgbackups:capture
Created: 2014-03-24T04:59:25Z
$ heroku pgbackups:capture --app my-cool-app
 !    Heroku client internal error.
 !    Search for help at: https://help.heroku.com
 !    Or report a bug at: https://github.com/heroku/heroku/issues/new

    Error:       undefined method `get_attachments' for #<Heroku::API:0x007fe383b56670> (NoMethodError)
    Backtrace:   /Users/me/.heroku/client/lib/heroku/helpers/heroku_postgresql.rb:99:in `app_attachments'
                 /Users/me/.heroku/client/lib/heroku/helpers/heroku_postgresql.rb:104:in `hpg_databases'
                 /Users/me/.heroku/client/lib/heroku/helpers/heroku_postgresql.rb:155:in `hpg_resolve'
                 /Users/me/.heroku/client/lib/heroku/helpers/heroku_postgresql.rb:58:in `resolve'
                 /Users/me/.heroku/client/lib/heroku/command/pgbackups.rb:379:in `resolve'
                 /Users/me/.heroku/client/lib/heroku/command/pgbackups.rb:74:in `capture'
                 /Users/me/.heroku/client/lib/heroku/command.rb:218:in `run'
                 /Users/me/.heroku/client/lib/heroku/cli.rb:28:in `start'
                 /usr/bin/heroku:25:in `<main>'

    Command:     heroku pgbackups:capture --app my-cool-app
    Version:     heroku-toolbelt/3.6.0 (universal.x86_64-darwin13) ruby/2.0.0

Trying heroku pgbackups:capture DATABASE_URL --app my-cool-app results in the exact same error. pgbackups and pgbackups:url seem to work fine.

Duplicate issue #1070: pgbackups:capture throws an error
Created: 2014-04-03T18:23:38Z
I've been using pgbackups:capture in the same way regularly.  This error is different from the message you get when you need to delete a backup:
$ heroku pgbackups:capture --app my-app
 !    Heroku client internal error.
 !    Search for help at: https://help.heroku.com
 !    Or report a bug at: https://github.com/heroku/heroku/issues/new

    Error:       undefined method `get_attachments' for #<Heroku::API:0x00000100afdd08> (NoMethodError)
    Backtrace:   /Users/SoftwareDev/.heroku/client/lib/heroku/helpers/heroku_postgresql.rb:99:in `app_attachments'
                 /Users/SoftwareDev/.heroku/client/lib/heroku/helpers/heroku_postgresql.rb:104:in `hpg_databases'
                 /Users/SoftwareDev/.heroku/client/lib/heroku/helpers/heroku_postgresql.rb:155:in `hpg_resolve'
                 /Users/SoftwareDev/.heroku/client/lib/heroku/helpers/heroku_postgresql.rb:58:in `resolve'
                 /Users/SoftwareDev/.heroku/client/lib/heroku/command/pgbackups.rb:379:in `resolve'
                 /Users/SoftwareDev/.heroku/client/lib/heroku/command/pgbackups.rb:74:in `capture'
                 /Users/SoftwareDev/.heroku/client/lib/heroku/command.rb:218:in `run'
                 /Users/SoftwareDev/.heroku/client/lib/heroku/cli.rb:28:in `start'
                 /usr/local/heroku/bin/heroku:24:in `<main>'

    Command:     heroku pgbackups:capture --app lingraphica-editor-production
    Plugins:     heroku-pg-extras
    Version:     heroku-toolbelt/3.6.0 (x86_64-darwin10.8.0) ruby/1.9.3

Closing comment (2014-04-03T18:26:58Z): I believe this is a duplicate of #1065
Repository: heroku/legacy-cli

Issue #1107: I get an error in the login process on Heroku
Created: 2014-05-08T15:09:34Z
Please help me error incidents on!
http://i.imgur.com/4YXMHBx.png

Duplicate issue #1108: Help me
Created: 2014-05-08T17:14:49Z
I can not run on Heroku Toolbelt SCM Git! Technical help me on this issue!
http://i.imgur.com/wKnJAGg.png

Closing comment (2014-05-08T17:57:39Z): This is a duplicate of #1107
Repository: heroku/legacy-cli

Issue #1428: Command "heroku certs:info" crashes
Created: 2015-02-27T13:21:45Z
heroku certs:info
Fetching SSL Endpoint XXX.herokuapp.com info for XXX... done
Certificate details:
!    Heroku client internal error.
!    Search for help at: https://help.heroku.com
!    Or report a bug at: https://github.com/heroku/heroku/issues/new
Error:       undefined method `[]' for nil:NilClass (NoMethodError)
Command:     heroku certs:info
Version:     heroku-toolbelt/3.27.2 (x86_64-darwin10.8.0) ruby/1.9.3
Error ID:    5db7cdac13f44061af232505c2a64e37

Duplicate issue #1438: heroku certs:info -a myapp
Created: 2015-03-03T16:30:52Z
The following command is returning an error:
heroku certs:info -a myapp
Result:
Certificate details:
!    Heroku client internal error.
!    Search for help at: https://help.heroku.com
!    Or report a bug at: https://github.com/heroku/heroku/issues/new
Error:       undefined method `[]' for nil:NilClass (NoMethodError)
Command:     heroku certs:info -a roomer-production
Version:     heroku-toolbelt/3.28.2 (x86_64-darwin10.8.0) ruby/1.9.3
Error ID:    896fa8cf776b4df09ddbd6e33085d3ad

Closing comment (2016-12-06T20:22:37Z): This looks like it might be a duplicate of #1428.
/cc @dickeyxxx @ransombriggs
Repository: heroku/legacy-cli

Issue #943: Running a pg command without specifying an app gives "internal service error"
Created: 2013-11-07T22:20:03Z
Running a pg command fails if you don't specify an app:
$ heroku pg:info
 !    Internal server error.
 !    Run `heroku status` to check for known platform issues.

This seems to happen even if you're in an app directory.
But it can be fixed by manually specifying an app:
$ heroku pg:info --app jacobian
=== HEROKU_POSTGRESQL_VIOLET_URL (DATABASE_URL)
...

Duplicate issue #968: Inform when no app selected on `pg:pull`
Created: 2013-12-11T18:12:20Z
If you try running pg:pull without specifying -a appname and you're not in a Heroku directory you get an internal server error:
$ heroku pg:pull DATABASE_URL foo_database
 !    Internal server error.
 !    Run `heroku status` to check for known platform issues.

$ heroku status
=== Heroku Status
Development: No known issues at this time.
Production:  No known issues at this time.

$ heroku pg:pull DATABASE_URL foo_database -a appname
# works
This error is a bit misleading

Closing comment (2013-12-11T19:42:58Z): Thanks for reporting!
This is a duplicate of #943 and is patched in #964 . bump to @pedro 😸
Repository: heroku/legacy-cli

Issue #748: Feature request: `heroku fork` should copy the git repo
Created: 2013-04-06T08:27:57Z
After a short discussion on a support ticket @friism suggested I open an issue here.
From the ticket:

I noticed that it doesn't copy the git repo to the new app so if I manually push to the forked app I need to re-push the entire repo. This is a problem with our ~100mb repo. Any chance you could make it copy the repo across?

Duplicate issue #804: Copy entire git repo
Created: 2013-05-21T16:01:44Z
Copy the entire git repo for the app when you fork it, not just HEAD.  This would make forking a lot quicker for folk who push to a forked app when that app has 5 years of git history associated with it....

Closing comment (2013-05-21T16:37:02Z): Dup of #748
Repository: hexojs/hexo

Issue #1657: 0.0.0.0 is not addressable, use 127.0.0.0 by default
Created: 2015-12-15T15:44:37Z
The change is in hexojs/hexo-server, but this breaks the feature of allowing other machines to visit the site via hexo-server (which I think is good).
We have to change all the documents in hexojs/site to reflect this change.
Also add workaround (specifying the ip) to maintain current behavior.
See hexojs/hexo-server#14 and jekyll/jekyll#3048 for the discussion.

Duplicate issue #1654: server won't run or connect
Created: 2015-12-15T05:20:55Z
Seems when I run locally, I can't connect via several browsers.  Related to failed dep?

E:\client\Tim\> nodist
  (x64)
> nodev4.2.3  (global)

E:\client\Tim\> npm -v
2.14.10

E:\client\Tim> npm install hexo-cli -g
npm WARN optional dep failed, continuing fsevents@1.0.6
C:\p\n\nodist\bin\hexo -> C:\p\n\nodist\bin\node_modules\hexo-cli\bin\hexo
hexo-cli@0.1.9 C:\p\n\nodist\bin\node_modules\hexo-cli
├── abbrev@1.0.7
├── minimist@1.2.0
├── bluebird@3.0.6
├── tildify@1.1.2 (os-homedir@1.0.1)
├── chalk@1.1.1 (ansi-styles@2.1.0, supports-color@2.0.0, escape-string-regexp@1.0.3, has-ansi@2.0.0, strip-ansi@3.0.0)
└── hexo-fs@0.1.5 (escape-string-regexp@1.0.3, graceful-fs@4.1.2, chokidar@1.4.1)

E:\client\Tim> hexo init blog
INFO  Copying data to E:\client\Tim\blog
INFO  You are almost done! Don't forget to run 'npm install' before you start blogging with Hexo!

E:\client\Tim> cd blog

E:\client\Tim\blog> npm install
npm WARN optional dep failed, continuing fsevents@1.0.6
npm WARN optional dep failed, continuing fsevents@0.3.8
-
> dtrace-provider@0.6.0 install E:\client\Tim\blog\node_modules\hexo\node_modules\bunyan\node_modules\dtrace-provider
> node scripts/install.js
...

hexo server
INFO  Hexo is running at http://0.0.0.0:4000/. Press Ctrl+C to stop.

Closing comment (2015-12-15T18:10:42Z): Great, thank you.
On Tue, Dec 15, 2015 at 8:46 AM, leesei notifications@github.com wrote:

This is tracked by #1657 #1657,
which is a more thorough solution.
—
Reply to this email directly or view it on GitHub
#1654 (comment).
Repository: hexojs/hexo

Issue #2105: permalink for pages broken for when config.root
Created: 2016-08-20T14:09:04Z
in lib/models/page.js
Page.virtual('permalink').get(function() {
    return ctx.config.url + '/' + this.path;
  });
should reflect:
Page.virtual('permalink').get(function() {
    return ctx.config.url + ctx.config.root + this.path;
  });
Somewhat like
  Post.virtual('permalink').get(function() {
    var config = ctx.config;

    return config.url + config.root + this.path;
  });
in lib/models/page.js
Same counts for category.js and tag.js

Duplicate issue #3601: Permalink not including root
Created: 2019-06-29T01:52:45Z
Environment Info
This Issue is Continuation of #2610 .
This Issue is Closed, but the BUG is not fixed.
For BUG

I've placed <%= page.permalink %> in post.ejs and the result is http://127.0.0.1:4000/El-meu-primer-post-ada5698b/


This link is not working as root is /blog/. Also <%= config.url + config.root + (page.path||'').replace('index.html', '') %> produces http://127.0.0.1:4000/blog/El-meu-primer-post-ada5698b/ which is ok.

This is very simple BUG, but I think this is IMPORTANT BUG.
Permalink not including root.
Deploy system will use the parameter url, root, permalink.
Now, post.permalink not including root : url + permalink.
It should be url + root + permalink

Closing comment (2019-09-29T17:31:33Z): Duplicate of #2105
Repository: hexojs/hexo

Issue #458: Internal Links
Created: 2014-01-19T20:27:54Z
Hi. I can't seem to find it anywhere, so I'll ask. How can I make internal links in a post to my other posts easily?

Duplicate issue #570: Is there anything equivalent to {% post_url xxx %}?
Created: 2014-04-01T19:35:06Z
Hi, I'm migrating my blog from Jekyll Bootstrap, the problem is that looks like there is no post_url in hexo, so I got following error message:
[error] HexoError: Process failed: _posts/2014-02-19-hadoop1-single-node-install-guide.md
Error: Unexpected tag "post_url 2014-02-19-hadoop1-single-node-install-guide" on line 28 in file /home/tao/lab/node/hexo/myblog/source/_posts/2014-02-19-hadoop1-single-node-install-guide.md.
    at Object.exports.throwError (/usr/local/lib/node_modules/hexo/node_modules/swig/lib/utils.js:183:9)
    at parseTag (/usr/local/lib/node_modules/hexo/node_modules/swig/lib/parser.js:543:13)
    at /usr/local/lib/node_modules/hexo/node_modules/swig/lib/parser.js:638:15
    at Object.exports.each (/usr/local/lib/node_modules/hexo/node_modules/swig/lib/utils.js:45:11)
    at Object.exports.parse (/usr/local/lib/node_modules/hexo/node_modules/swig/lib/parser.js:622:9)
    at parse (/usr/local/lib/node_modules/hexo/node_modules/swig/lib/swig.js:349:19)
    at precompile (/usr/local/lib/node_modules/hexo/node_modules/swig/lib/swig.js:479:23)
    at compile (/usr/local/lib/node_modules/hexo/node_modules/swig/lib/swig.js:584:16)
    at Object.render (/usr/local/lib/node_modules/hexo/node_modules/swig/lib/swig.js:513:17)
    at /usr/local/lib/node_modules/hexo/lib/post/render.js:69:29

Is there anything i'm missing? How to link to my other post?
Thanks.

Closing comment (2014-07-28T06:51:50Z): Duplicate of #458
Repository: hexojs/hexo

Issue #5301:   Incomplete display of HTML document, truncated at '#' in markdown document
Created: 2023-09-26T07:39:22Z
使用默认安装，将md文档处理为网页时，启动hexo网站服务，本地查看文档内容不全。
When using the default installation to process MD documents as web pages, starting the hexo website service may result in incomplete local viewing of document content.
### 数组

- 数组定义：`array_name=(value1 ... valuen)`<br>
  括号里面允许换行，value以空格或换行分隔
- 也可以单独定义数组各个分量：`array_name[i]=valuei` (i可以是数字).<br>
  即数组可以不定义就使用，也可以定义时赋初值，数组元素就像普通变量一样使用即可。
- 引用数组所有元素：`${array_name[*]}`或`${array_name[@]}`.<br>
  只会取得数组已定义元素值的列表
- 可以使用unset删除数组元素：`unset array_name[i]`<br>
- 使用`${#array_name[*]}`或`${#array_name[@]}`取得数组已定义的元素数量(数组长度)
- 使用`${#array_name[n]}`取得n号元素的长度，这些就像求串长一样。
- 数组切片：`${array_name[*]:position:length}`或`${array_name[@]:position:length}`.<br>
  这其实是对数组已定义元素值的列表进行切片，就像串取子串一样。
上面文档将只会显示部分处理内容:
The above document will only display partial processing content:
### 数组

- 数组定义：`array_name=(value1 ... valuen)`<br>
  括号里面允许换行，value以空格或换行分隔
- 也可以单独定义数组各个分量：`array_name[i]=valuei` (i可以是数字).<br>
  即数组可以不定义就使用，也可以定义时赋初值，数组元素就像普通变量一样使用即可。
- 引用数组所有元素：`${array_name[*]}`或`${array_name[@]}`.<br>
  只会取得数组已定义元素值的列表
- 可以使用unset删除数组元素：`unset array_name[i]`<br>
- 使用`$
经过多次验证，只会在正文包含'#'字符时出现异常。
After multiple verifications, exceptions will only occur when the body contains the '#' character.
版本信息：
npx hexo -v
INFO  Validating config
hexo: 6.3.0
hexo-cli: 4.3.1
os: win32 10.0.19044
node: 18.17.1
acorn: 8.8.2
ada: 2.5.0
ares: 1.19.1
brotli: 1.0.9
cldr: 43.1
icu: 73.2
llhttp: 6.0.11
modules: 108
napi: 9
nghttp2: 1.52.0
openssl: 3.1.2
simdutf: 3.2.12
tz: 2023c
undici: 5.22.1
unicode: 15.0
uv: 1.46.0
uvwasi: 0.0.18
v8: 10.2.154.26-node.26
zlib: 1.3

Duplicate issue #5437: hexo g is truncated by {#
Created: 2024-03-17T13:55:47Z
Check List

 I have already read Docs page & Troubleshooting page.
 I have already searched existing issues and they are not help to me.
 I examined error or warning messages and it's difficult to solve.
 I am using the latest version of Hexo. (run hexo version to check)
 My Node.js is matched the required version.

Expected behavior
Displaying the rest of the content normally.
Actual behavior
When using hexo g to generate static web pages, if there is '{#' in the source file, a truncation issue may occur, and the subsequent content will not be displayed.


How to reproduce?
By writing {#} in the markdown file and triggering hexo g.
Is the problem still there under Safe mode?
I used --safe, but the problem still exists.
Your Node.js & npm version
> node -v
v18.16.0
> npm -v
9.5.1

Your Hexo and Plugin version
No response
Your package.json
No response
Your site's _config.yml (Optional)
No response
Others
No response

Closing comment (2024-03-30T13:14:01Z): Duplicate of #5301
Repository: hexojs/hexo

Issue #3470: 安装hexo-admin 点击编辑hexo报错退出
Created: 2019-02-27T10:37:10Z
TypeError: next is not a function
at /data/blog/node_modules/hexo-admin/api.js:318:25
at /data/blog/node_modules/hexo-admin/api.js:141:7
at call (/data/blog/node_modules/connect/index.js:239:7)
at next (/data/blog/node_modules/connect/index.js:183:5)
at next (/data/blog/node_modules/connect/index.js:161:14)
at next (/data/blog/node_modules/connect/index.js:161:14)
at next (/data/blog/node_modules/connect/index.js:161:14)
at next (/data/blog/node_modules/connect/index.js:161:14)
at next (/data/blog/node_modules/connect/index.js:161:14)
at next (/data/blog/node_modules/connect/index.js:161:14)
at next (/data/blog/node_modules/connect/index.js:161:14)
at next (/data/blog/node_modules/connect/index.js:161:14)
at jsonParser (/data/blog/node_modules/body-parser/lib/types/json.js:110:7)
at call (/data/blog/node_modules/connect/index.js:239:7)
at next (/data/blog/node_modules/connect/index.js:183:5)
at SendStream.error (/data/blog/node_modules/serve-static/index.js:121:7)
at emitOne (events.js:116:13)
at SendStream.emit (events.js:211:7)
at SendStream.error (/data/blog/node_modules/send/index.js:270:17)
at SendStream.onStatError (/data/blog/node_modules/send/index.js:421:12)
at next (/data/blog/node_modules/send/index.js:736:16)
at onstat (/data/blog/node_modules/send/index.js:725:14)

Duplicate issue #3469: hexo-admin 配置后，输入用户名，密码后 登录后 hexo报错退出
Created: 2019-02-27T08:58:24Z
/data/blog/node_modules/serve-static/index.js:121
next()
^
TypeError: next is not a function
at SendStream.error (/data/blog/node_modules/serve-static/index.js:121:7)
at emitOne (events.js:116:13)
at SendStream.emit (events.js:211:7)
at SendStream.error (/data/blog/node_modules/send/index.js:270:17)
at SendStream.onStatError (/data/blog/node_modules/send/index.js:421:12)
at onstat (/data/blog/node_modules/send/index.js:727:26)
at FSReqWrap.oncomplete (fs.js:152:21)

Closing comment (2019-03-06T13:20:25Z): Duplicate #3470
Repository: hexojs/hexo

Issue #458: Internal Links
Created: 2014-01-19T20:27:54Z
Hi. I can't seem to find it anywhere, so I'll ask. How can I make internal links in a post to my other posts easily?

Duplicate issue #943: root not present for internal link in markdown
Created: 2014-12-02T03:51:11Z
_config.yml
# URL
## If your site is put in a subdirectory, set url as 'http://yoursite.com/child' and root as '/child/'
url: http://yoursite.com/child
root: /child/
...
relative_link: true
In a post:
Link to [about](/about).
EDIT: relative_link is set to true
Link generated: http://yoursite.com/about
Link expected:  http://yoursite.com/child/about
Should we hack relative link (not starting with http(s)) to add root to them?
Or there is swig helpers I should use for this?

Closing comment (2014-12-09T17:29:46Z): This is more related to #458.
Repository: hexojs/hexo

Issue #2601: How many characters are allowed in a post?
Created: 2017-06-09T08:23:55Z
Seems Hexo doesn't support very long post, right?

Duplicate issue #5080: hexo can't render complete content of a long page, if my essay is too long, it will only display partly or even do not display.
Created: 2022-10-06T01:29:00Z
I'm sure google can't solve my problem.
I search existing issues and can't find any same or approximate problem and solution.

Environment:

The latest node.js
The latest hexo frame
There are not any other plugins of hexo and nodejs
Windows10 OS

Describe the bug:
After I wrote a essay with about 374 lines and want to post it to my blog based on hexo, I found that hexo can't show this essay entirely, it only display the essay partly.
In order to prove this is a bug, I build another markdown file which includes about 8627 lines and put it into hexo, this time, hexo even do not show this essay, and I can find this essay nowhere.
To Reproduce:
In order to reproduce this bug, you can perform the following steps:

use latest nodejs and latest hexo to initialize a hexo blog.
new a markdown file which has 374 lines or more lines and put it into ./your_blog/sources/_posts/ easily.
execute the commands in order: hexo clean, hexo g, hexo s, and then open your blog and check the content integrity.

your essay maybe incomplete;
if your markdown file has too many lines (>= 8627), you will even can't find this essay in your blog.

Closing comment (2023-06-17T02:34:27Z): This issue may be related to #2601
Repository: hexojs/hexo

Issue #674: Better Error Messaging if Hexo is Already Running
Created: 2014-06-11T20:29:00Z
I was getting a weird error from Hexo while trying to run the hexo server command:
/usr/local/lib/node_modules/hexo/node_modules/async/lib/async.js:30
            if (called) throw new Error("Callback was already called.");
                              ^
Error: Callback was already called.
    at /usr/local/lib/node_modules/hexo/node_modules/async/lib/async.js:30:31
    at Domain.<anonymous> (/usr/local/lib/node_modules/hexo/lib/box/index.js:115:12)
    at Domain.EventEmitter.emit (events.js:95:17)
    at Server.EventEmitter.emit (events.js:70:21)
    at net.js:1046:12
    at process._tickDomainCallback (node.js:463:13)

Turns out I had hexo running in another terminal window. It'd be nice if hexo could be a little smarter and detect if it isn't able to listen on the port and display a more productive error.

Duplicate issue #675: hexo server
Created: 2014-06-12T06:48:06Z
Hexo 2.6.3
Node v0.10.28
Mac OS X 10.9
$ hexo server

/usr/local/lib/node_modules/hexo/node_modules/async/lib/async.js:30
            if (called) throw new Error("Callback was already called.");
                              ^
Error: Callback was already called.
    at /usr/local/lib/node_modules/hexo/node_modules/async/lib/async.js:30:31
    at Domain.<anonymous> (/usr/local/lib/node_modules/hexo/lib/box/index.js:115:12)
    at Domain.EventEmitter.emit (events.js:95:17)
    at Server.EventEmitter.emit (events.js:70:21)
    at net.js:1046:12
    at process._tickDomainCallback (node.js:463:13)

Closing comment (2014-06-12T10:37:50Z): dup of #674?
Repository: highcharts/highcharts

Issue #4284: 4.1.6 regression: Columns disappear after point.update with objects
Created: 2015-06-15T11:28:03Z
Demo: http://jsfiddle.net/highcharts/gpbLdcdc/

Duplicate issue #4326: Updating point in candlestick causes it to disappear
Created: 2015-06-25T21:58:57Z
See this fiddle: http://jsfiddle.net/bjacksoneze/9L9u1eye/16/
Whenever I attempt to change an attribute on the candlestick, in this case: close, it appears for a small fraction of a second then disappears.

Closing comment (2015-06-26T06:49:45Z): Duplicate of #4284.
Demo with the fix applied: http://jsfiddle.net/highcharts/9L9u1eye/17/
Until our next maintenance release, you can use the previous version of Highstock (2.1.5).
Repository: highcharts/highcharts

Issue #2522: Using axis type 'category' requires to have same values for all series
Created: 2013-12-09T16:14:22Z
With the current 'category' axis type the behaviour is bit cumbersome for users. The documentation says that that categories are taken from the first series. Still names are also read from subsequent series, but points x value is still always the index of the point (or explicit value).
Code example to demonstrate issue
http://jsfiddle.net/2gFMw/
My suggestion is to preprocess data without x values in category mode and calculate actual x value based on "name" property. I prototyped the solution here:
mstahv@c4b7f59
You will probably want rewrite the patch in a manner that suits better into your architecture. Logic most likely belongs to Axis.
Allowing this might not be the best idea performance wise (error 15 gets throw with the fix), but for most cases I think it wouldn't matter.
Original Vaadin Charts issue that brought this up:
http://dev.vaadin.com/ticket/13050

Duplicate issue #2831: Column chart with category type doesn't group xAxis names properly
Created: 2014-03-20T07:40:10Z
Given you have this series for the column chart with category xAxis type:
            series: [{
                name: 'Green',
                data: [
                    {
                        name: 'Mon',
                        y: 100
                    }, 
                    {
                        name: 'Tue',
                        y: 400
                    }
                ],
                color: 'green'
            }, {
                name: 'Yellow',
                data: [
                    {
                        name: 'Tue',
                        y: 140
                    }
                ],
                color: 'yellow'
            }]

Then the Yellow column is showing up with the Mon name instead of Tue. Here's a jsfiddle

Closing comment (2014-03-20T07:45:48Z): Possibly related to #2522.
Repository: highcharts/highcharts

Issue #9104: Proximate formatting problem when combination of height and series 
Created: 2018-10-02T10:07:23Z
Expected behaviour
Proximate should position legend near series data
Actual behaviour
When number of series exceeds height of the graph the legend are stacked at top of graph
Live demo with steps to reproduce
http://jsfiddle.net/u2yp509c/1/
Product version
Highcharts JS v6.1.4 (2018-09-25)
Affected browser(s)
All Browsers

Duplicate issue #11123: Highstock Legend overflow entries stacks.
Created: 2019-06-21T15:29:59Z
Expected behaviour
When the graph height exceeds the legend height the bottom entries should be added to a overflow scroll down , 1 of 2 etc
Actual behaviour
Bottom legend entries are stacked at top of the graph.
using "layout":"proximate"
Live demo with steps to reproduce
https://jsfiddle.net/garybrain/d08svw6r/3/
Looking at the code the last two legend items are placed at transform="translate(8,0)"
Also the more series you add eventually there will be a 1/2 option appear but they still stack at the top of the page.
https://jsfiddle.net/garybrain/d08svw6r/6/
Product version
Highstock 7.1.2
Affected browser(s)
All

Closing comment (2019-06-24T08:24:39Z): Hi @garybrain
Thanks for reporting, but you already did that, see #9104
Closing as duplicate of #9104
Repository: highcharts/highcharts

Issue #6225: Series line clipping on axis limit
Created: 2017-01-10T11:09:48Z
The series lines are clipped when its values are on the axis limits, as it can be found here. Note that the line width is half of the expected in values 0 and 5.
Searching on stackoverflow i found the clip flag on series that causes the expected behavior
However, this flag does not seems to work with color zones
This flag is not part of the series public api, so let me know if there is a better way to reproduce the expected behavior with color zones without changing the axis limits.

Duplicate issue #6839: Line chart clips line thickness when the series aligns with the xAxis min value
Created: 2017-06-15T13:49:40Z
Expected behaviour
line thickness should be the same everywhere
Actual behaviour
line thickness is half
Live demo with steps to reproduce
http://jsfiddle.net/fkubgt5w/4/
See the 2 lines thicknesses fluctuating
Affected browser(s)
Chrome, Safari

Closing comment (2017-06-19T07:43:18Z): Thank you for the reporting.
Duplicate of: #6225 and #6604
Repository: highcharts/highcharts

Issue #5607: Regression: Repetetive point names causes points to stack
Created: 2016-08-22T12:53:33Z
Actual behaviour
If xAxis.type is category and there are more than one point with the same name, the points will be given the same X value. It is not a bug per se, but we need an option in order to keep backwards compatibility from the data module and the cloud.
Live demo with steps to reproduce
http://jsfiddle.net/highcharts/f3p0ojuv/1/. Compare with v4.2.5.
Suggested fix
Add a new option, xAxis.categoryByIndex or similar, that gives the points a position (x value) based on their index rather than their name. Then make the data module use this option by default.

Duplicate issue #5653: Charts distorted after upgrading to 4.2.6
Created: 2016-09-02T17:45:30Z
Expected behaviour:
Charts not distorted
Actual behaviour:
Charts actually distorted. You hopefully see it when you compare the chart using below fiddle and Highcharts ver 4.2.5 and 4.2.6
Live demo with steps to reproduce:
http://jsfiddle.net/jentyk/ojov2vng/
Affected browser:
Chrome Version 52.0.2743.116 (64-bit).

Closing comment (2016-09-05T10:13:52Z): Thanks for reporting! It's a duplicate of #5607. It is caused by some point names being repeated. We'll come up with a fix ASAP.
Repository: highcharts/highcharts

Issue #5322: Pie chart with negative values renders incorrectly
Created: 2016-05-18T12:04:25Z
Expected behavior
Not sure what's the expected behavior, maybe ignore negatives
Actual behavior

Live demo of the issue
http://jsfiddle.net/alvarezg/87v4w3fp/
Affected browser(s)
Latest chrome at least

Duplicate issue #5361: pie chart renders double doughnut when value is above 200% -- broken in 4.1.6+
Created: 2016-05-31T16:07:19Z
We're using the pie chart to render a ring graph with multiple values overlaid on each other. When one of the values is above 200%, one of the rings renders outside of the ring graph.
We've found experimentally that Highcharts 4.1.5 is the latest release that doesn't have this issue. 4.1.6 and above renders the pie chart incorrectly in that scenario. 4.1.10 unfortunately has another bug causing the ring graph to animate with an artifact and doesn't reflect the correct value at the end.
These versions are important because the highcharts versions released on npm include 4.1.0 and 4.2.0 but nothing in between. Thus we're unable to specify 4.1.5 from the npm registry. We had been using the package highcharts-release 4.1.5, but switched to highcharts for CommonJS support.
Would you kindly publish highcharts 4.1.5 on npm? It may need to be a custom tag since there have been newer versions published.

Closing comment (2016-06-07T06:36:55Z): @peacechen It seems to be a duplicate of #5322. It will be fixed in an upcoming maintenance release, and you can find a potential workaround there.
Repository: highcharts/highcharts

Issue #5857: Drilldown to more than 50 - skip categories name
Created: 2016-10-21T10:20:56Z
Actual behaviour
Categories names are missing
Live demo with steps to reproduce
Example:

http://jsfiddle.net/gugjup9t/

Click into Microsoft, as a result when we have more than 50 categories, names are missing.
NameToX and setting labels.step as 1 do not solve the issue.
Affected browser(s)
All  browsers

Duplicate issue #7903: When a series with a large scale is zoomed in and the zooming is reset the X-Axis doesn't display the labels properly.
Created: 2018-02-22T10:51:12Z
Expected behaviour
X-Axis labels and values should be displayed properly after zooming is reset.
Actual behaviour
When a series with a large scale is zoomed in and the zooming is reset the X-Axis doesn't display the labels properly.
Live demo with steps to reproduce


Product version
Highcharts JS v4.1.8 (2015-08-20)
Affected browser(s)
All browsers

Closing comment (2018-07-13T12:31:16Z): It's a duplicate of #5857 - workaround is to set series.cropThreshold. Closing as duplicate.
Repository: highcharts/highcharts

Issue #340: Y axis extremes not always reflecting the zoomed data
Created: 2011-08-02T06:56:38Z
When using the example of "single line series" with less then or equal to 300 data points the y-axis will not scale right when zoom is not set to full: http://jsfiddle.net/b6G6x/
However it works for more than 300 data points (you can just add one point or see here) http://jsfiddle.net/e5zyM/
I don't know what the reason is, but maybe you can look into it and fix it - would be really helpful.

Ok, I found the problem: cropThreshold.
When the number of points is less than in cropThreshold all points are drawn even those that are not displayed in the current segment. The problem: the y-axis scales according to the all points, even the invisible ones.
It's a neat idea to use cropThreshold for performance reasons but it sucks that the y-axis isn't calculated correctly.

Duplicate issue #373: Wrong proportion for simple spline.
Created: 2011-08-18T13:46:29Z
Example: http://jsfiddle.net/DQ5gF/5
It seems, that it takes proportion for whole range. I mean it looks ok if click "all" in range navigator. But badly if zoom in.

Closing comment (2011-08-18T17:51:09Z): Duplicate of #340
Repository: highcharts/highcharts

Issue #5841: Highcharts tooltip first click issue in mobile devices
Created: 2016-10-18T13:48:08Z
Expected behaviour
Tooltip should appear on the first touch on point.
Actual behaviour
When we click on the chart for first time, the path gets highlighted without showing tooltip and then on subsequent clicks the tooltip appears. We tried with the Highcharts demo options and still the issue persists. Similarly, for checking purpose, we placed click event in the tooltip and gave a alert. It was working fine in jsFiddle. But didn't work in my mobile webView. The seen behaviour is on first click, the path gets highlighted. And then from next subsequent clicks, tooltip appears and it works fine.This behaviour is not seen on desktop devices or if the the chart is rendered in iframe tag.
jsFiddle
http://jsfiddle.net/2swEQ/2/
Tested browser(s)
Tested in these devices
iOS WebView: > 8.0,
Device: iphone 5s, iPhone 6 and 6S
Android: > Android Kit-Kat,
Device: Nexus, Samsung Galaxy devices

Duplicate issue #5744: iOS / show tooltip on click event issue
Created: 2016-09-29T11:37:52Z
Expected behaviour
Tooltip is shown on the first point's click
Actual behaviour
On iOS mobile device when the chart is rendered, first touch highlights the series and the second touch shows the tooltip. This behaviour does not occur in desktop devices or if the the chart is rendered in iframe tag.
Live demo with steps to reproduce
Use only code from jsfiddle - since jsfiddle uses iframe, the issue will not occur
http://jsfiddle.net/2swEQ/2/
Affected browser(s)
iPad 2, iOS 9.3.5, Safari 601.1
iPhone 5s, iOS 9.3.5;

Closing comment (2019-03-22T10:43:06Z): Closing as duplicate of #5841.
Repository: highlight/highlight

Issue #6234: Create Issue from errors page has unintended caching
Created: 2023-08-04T15:58:12Z
To reproduce

Click an error and observe error body
Select Create Issue and observe error body is filled in for Issue Title
Close modal
Select a different error
Select Create Issue and observe it uses the previous error's body for the Issue Title

https://www.loom.com/share/719e79d41cf848419b23d63b0e6fae60

Duplicate issue #5699: Submit Button for ticket integration needs loading state
Created: 2023-06-21T18:51:43Z
Submit button should have a loading state

Closing comment (2023-08-04T15:59:29Z): Related to #6234. @mayberryzane can you take this next week as well?
Repository: highlight/highlight

Issue #4080: Loading state to changing the state of an error + instant state updates locally
Created: 2023-01-30T16:42:04Z
we should at least give the user some feedback when an error group's state is updates. right now, it takes a few seconds and i ahve no idea what's going on.
we should make the updates to the local state instant.

I think this will set us up to start doing the weekly error/session triaging sessions.

Duplicate issue #4233: [error ui] Speed up the interaction times for error state selection 
Created: 2023-02-13T16:34:54Z
Leverage Apollo cache to avoid blocking the UI
Upgrade the loading state of the button

Closing comment (2023-02-13T18:59:25Z): Closing this as a duplicate of #4080
Repository: highlight/highlight

Issue #3921: Keep the bar width in the session timeline within sensible limits
Created: 2023-01-30T15:20:15Z
Bars too wide

https://app.highlight.io/1/sessions/CnkOc7z8poBGtYhRR5BGXBTephT5?page=1
https://app.highlight.io/1/sessions/SUzyRIKSipkVifdFEgpnFAmiq2UN?query=and%7C%7Ccustom_processed%2Cis%2Ctrue%7C%7Ccustom_created_at%2Cbetween_date%2C30%20days

Bars too thin

https://app.highlight.io/1/sessions/by6b3280owdiukxvPWVDogM4J0p8?page=1
https://app.highlight.io/1/sessions/nBZVSxrYrchrDDXLHgNIt2vKmfcf?page=1&query=and||custom_processed%2Cis%2Ctrue||custom_created_at%2Cbetween_date%2C30 days

Duplicate issue #5141: SR: Make timeline indicator bar width the same all the time
Created: 2023-04-27T14:47:46Z

Closing comment (2023-05-08T16:23:29Z): @highlight/jay is this a duplicate of #3921?
Repository: highlight/highlight

Issue #7379: advanced ingest filtering customization
Created: 2023-12-20T22:19:23Z
support multiple individual exclusion queries
support per-query sampling / rate limiting configurations
support custom rate limits (such as deny ingest if more than N logs are ingested in an X long period)

Duplicate issue #7068: support trace sampling by query
Created: 2023-11-02T20:11:13Z
Improving the ingest filters for specific queries
ie 10% of service:public-graph, 100% of private graph

Closing comment (2024-01-29T17:11:18Z): duplicate of #7379
Repository: highlight/highlight

Issue #4550: Support a webhook endpoint for all alerts
Created: 2023-03-09T23:26:48Z
Issue to track "the ability to send a webhook request" to an endpoint for all of our slack alerts. For a v1:

we send all alerts in a json format (let's keep it simple)
in the single alert UI, we add an entry (in addition to discord and slack) for the user to enter any number of webhook endpoints. On save, like slack, we send a sample message across.

Duplicate issue #3693: Add webhook trigger
Created: 2023-01-30T06:38:28Z
when an alert sends, optionally make a call to a webhook

Closing comment (2023-03-20T18:17:25Z): duplicate of #4550
Repository: highlight/highlight

Issue #5024: Replace logsearch screenshot w/ a table
Created: 2023-04-19T20:55:16Z
@et, this is merged!
#4999
Could we replace the table image w/ a proper table now?

Duplicate issue #5091: Migrate log search image to proper markdown table
Created: 2023-04-22T20:44:20Z
Now that @Crawron has shipped our new table, we can use that instead? Also, @et , you mentioned a few updates you wanted to make.

Closing comment (2023-04-24T14:31:18Z): Dupe of #5024