text:
llm api启动保持，依赖requirements都安装了，切换多个pyenv都一样的问题

root@autodl-:~/autodl-tmp/Langchain-Chatchat# python startup.py --llm-api
==============================Langchain-Chatchat Configuration==============================
操作系统：Linux-5.4.0-100-generic-x86_64-with-glibc2.17.
python版本：3.8.10 (default, Jun  4 2021, 15:09:15)
[GCC 7.5.0]
项目版本：v0.2.2
langchain版本：0.0.266. fastchat版本：0.2.24
当前LLM模型：chatglm2-6b @ cuda
{'api_base_url': 'http://localhost:8889/v1',
'api_key': 'EMPTY',
'local_model_path': 'THUDM/chatglm2-6b'}
当前Embbedings模型： m3e-base @ cuda
==============================Langchain-Chatchat Configuration==============================
2023-08-25 18:22:28,797 - startup.py[line:382] - INFO: 正在启动服务：
2023-08-25 18:22:28,797 - startup.py[line:383] - INFO: 如需查看 llm_api 日志，请前往 /root/autodl-tmp/Langchain-Chatchat/logs
2023-08-25 18:22:30 | ERROR | stderr | INFO:     Started server process [2472]
2023-08-25 18:22:30 | ERROR | stderr | INFO:     Waiting for application startup.
2023-08-25 18:22:30 | ERROR | stderr | INFO:     Application startup complete.
2023-08-25 18:22:30 | ERROR | stderr | INFO:     Uvicorn running on http://127.0.0.1:20001 (Press CTRL+C to quit)
INFO:     Started server process [2473]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://127.0.0.1:8889 (Press CTRL+C to quit)
Process model_worker(2439):
Traceback (most recent call last):
File "/root/miniconda3/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap
self.run()
File "/root/miniconda3/lib/python3.8/multiprocessing/process.py", line 108, in run
self._target(*self._args, **self._kwargs)
File "/root/autodl-tmp/Langchain-Chatchat/startup.py", line 213, in run_model_worker
app = create_model_worker_app(**kwargs)
File "/root/autodl-tmp/Langchain-Chatchat/startup.py", line 53, in create_model_worker_app
from fastchat.serve.model_worker import app, GptqConfig, AWQConfig, ModelWorker, worker_id
File "/root/miniconda3/lib/python3.8/site-packages/fastchat/serve/model_worker.py", line 39, in
from fastchat.model.model_adapter import (
File "/root/miniconda3/lib/python3.8/site-packages/fastchat/model/init.py", line 1, in
from fastchat.model.model_adapter import (
File "/root/miniconda3/lib/python3.8/site-packages/fastchat/model/model_adapter.py", line 14, in
import accelerate
ModuleNotFoundError: No module named 'accelerate'

补充：logs目录下只有一个controller.log文件，但是无日志记录。

请执行 pip install accelerate 并看下执行后是否还存在该问题

authors: imClumsyPanda joeiren

repo: chatchat-space/Langchain-Chatchat


text:
[BUG] 知识库问答，知识库有匹配结果，但用模型的回答或者返回无法回答该问题

问题描述 / Problem Description
知识库问答，知识库有匹配结果，但用模型的回答或者返回无法回答该问题
预期的结果 / Expected Result
应该是用知识库匹配结果来回答
实际结果 / Actual Result
但用了模型的回答或者返回无法回答该问题
环境信息 / Environment Information

langchain-Chatchat 版本/commit 号：v2.0.10
是否使用 Docker 部署（是/否）：否
使用的模型（ChatGLM2-6B / Qwen-7B 等）：ChatGLM2-6B
使用的 Embedding 模型 ：bge-large-zh
使用的向量库类型 (faiss / milvus / pg_vector 等)： faiss
操作系统及版本 : CentOS Linux release 7.5.1804 (Core)
Python 版本 / Python version: 3.10.12
其他相关环境信息 :

附加信息 / Additional Information
能不能如果有匹配结果，是使用匹配结果，而不是用模型的回复。

模型请求错误了，查询一下是不是填的token超过了4096

模型请求错误了，查询一下是不是填的token超过了4096

如何测试打印这个token数？

source: gharchive/issue

authors: liangpn zRzRzRzRzRzRzR

license_type: permissive

license_source: github-api


text:
0.3.1版本 text pdf html文件添加到向量数据库时when post /knowledge_base/update_docs: timed out

问题描述 / Problem Description
UnstructuredFileLoader used for /opt/chatchat_data/knowledge_base/samples/content/test_files/test.txt
对text pdf html文件添加到向量数据库时, 卡在
when post /knowledge_base/update_docs: timed out
环境信息 / Environment Information
python 3.10
langchain                   0.1.17 langchain-chatchat          0.3.1.1 langchain-community         0.0.36 langchain-core              0.1.52 langchain-experimental      0.0.58 langchain-openai            0.0.6 langchain-text-splitters    0.0.2 langchainhub                0.1.14
附加信息 / Additional Information

2024-07-31 12:48:23.354 | INFO | chatchat.server.knowledge_base.utils:file2docs:336 - UnstructuredFileLoader used for /opt/chatchat_data/knowledge_base/samples/content/test_files/test.txt

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

Wed, Jul 31 2024 12:53:23 pm

已解决.
原因是, 当时的nlkt_data不知道是下载的哪个版本的，莫名其妙的不行。
又重新下载放到/root目录下就正常了。
同时也测试了langchain-chatchat带的nlkt_data，放到/root目录也能正常使用。

nlkt_data 在那里了啊


text:
**

this is a pr test

that not be convinced  test pr of close

source: gharchive/pull-request

authors: glide-the xieguobin


text:
future of this repo

Dear @chaubold,
i noticed that our fork in the ilastik org diverged a bit from your repo. In a way I think it would be best to transfer this repository to the ilastik org, since we still use and maintain it. What do you think? Alternatively we could try to always add our changes upstream here...
Cheers
Dominik

Hey @k-dominik! Sure, sounds good.
So similar to https://github.com/chaubold/dpct that would mean I add a link to the ilastik-fork of the repo and archive this one here, right?
Greetings from Virginie's BioVision Center Kick-Off Sympozium in Zurich (fun coincidence that you're writing while I am seeing the community again after a long time 😄)

awww now even more sad that I'm not there - would've been so cool to catch up.
How we do it is up to you really. I personally would prefer you transfer the repo to the ilastik org, so it is absolutely obvious that releases coming from us are from the official source. We recently transferred https://github.com/ilastik/ilastiktools to the ilastik org as well. But of course this is up to you. Archiving with a note would also work :)

Sure, I can transfer the repo! I tried it just now but it obviously doesn't want me to do that because there's already a fork at https://github.com/ilastik with the same name. I'll make the contents of "my" repo mirror those of the "ilastik" version, tell you, then you can delete yours and I'll move ownership, ok?
Yeaaaah, would've been awesome to see you again! Next time! 😄

Hey I renamed our fork, so you could also just transfer :)

Ah, that also works :) Done! But now there's a commit on master that my version of the repo is no longer maintained so... you'll manage to get rid of that commit ;)
Cheers,
Carsten

thanks a lot @chaubold! I hope we find an opportunity to catch up, soon!

authors: chaubold k-dominik

repo: chaubold/multiHypothesesTracking

license: MIT


text:
Write program to find out IMDB rating

problem statement
Write program to find out IMDB movie  rating

Hi!!!
Can I work on this???

yes @alananayaa

authors: alananayaa chavarera

repo: chavarera/python-mini-projects


text:
Added script to check website load time

Description
A script to show the time taken by a  website to load
Fixes #168
Type of change
Choosing one or more options from the following as per the nature of your Pull request.

[x] New feature (non-breaking change which adds functionality)

Checklist:
Please tick all the boxes that are fulfilled by your Pull request

[x] I have named my files and folder according to this project's guidelines
[x] My code follows the style guidelines of this project
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md
[x] I have included a requirements.txt file(if external libraries are required)
[x] My changes dont produce any warnings.
[x] I have added a working sample/screenshot of the script

ALRIGHT will make the requested changes

ALRIGHT will make the requested changes

cool :+1:

Wow! Thanks, @chavarera for this!

Did not know a lot of this information!
Thanks for letting us know! ^_^

Made the requested changes @chavarera

@AdityaJ7
the extra lines in the code affect your code readability use blank lines when you want to show a separation between two code blocks.

done @chavarera

authors: AdityaJ7 chavarera tusharnankani


text:
powershell5 not installing...  image file did not contain a resource section

Recipe: powershell::powershell5
         * windows_package[Windows Management Framework Core 5.0] action install
         Recipe: <Dynamically Defined Resource>

             - create new file C:\Users\vagrant\AppData\Local\Temp\kitchen\cache\package\Win8.1AndW2K12R2-KB3066437-x64.msu
             - update content in file C:\Users\vagrant\AppData\Local\Temp\kitchen\cache\package\Win8.1AndW2K12R2-KB3066437-x64.msu from none to 9c5730
             (file sizes exceed 10000000 bytes, diff output suppressed)

           ================================================================================
           Error executing action `install` on resource 'windows_package[Windows Management Framework Core 5.0]'
           ================================================================================

           Chef::Exceptions::Win32APIError
           -------------------------------
           The specified image file did not contain a resource section.
           ---- Begin Win32 API output ----
           System Error Code: 1812
           System Error Message: The specified image file did not contain a resource section.
           ---- End Win32 API output ----

           Resource Declaration:
           ---------------------
           # In C:/Users/vagrant/AppData/Local/Temp/kitchen/cache/cookbooks/powershell/recipes/powershell5.rb```

What version of chef-client are you using? I think you might be running into this issue on 12.6.0:
https://github.com/chef/chef/issues/4354

yep... thanks! which version should i be using?

Until a new version is released with that fix, I'd recommend 12.5.1

Still seeing that even after changing to omnibus 12.5.1. I then checked the .kitchen.yml in the repo and saw 11.18.6 and tried its the same error.

Did you destroy the box? Kitchen wasn't reverting for me when I was trying to roll back with this issue.
Other details about the setup? Windows version, current version of Powershell etc.?

looks like i was forcing the latest regardless ... whoops
provisioner:
  name: chef_zero
  chef_metadata_url: 'https://www.chef.io/chef/metadata?p=windows&m=x86_64&pv=2012r2&v=latest'

:) We've all been there!

im getting this now... Expected process to exit with [0, 42, 127, 3010], but received '5' ... i tried destroy first this time and i did this fix:
windows_service 'wuauserv' do
  startup_type :automatic
  action [ :enable, :start ]
end```
no luck, any ideas?

Just a side point im experimenting the new dsc_resource in chef. Powershell 4 wouldn't work with dsc_script so i decided to give ps5 a shot. i can share my cookbook if you want to see what im doing.

Oh- it's an update. You're probably running into the winrm permissions issues using chef_zero...
Try using chef-zero-scheduled-task:
https://github.com/smurawski/chef-zero-scheduled-task

authors: sarimali trevorghess

repo: chef-cookbooks/powershell

license_source: bigquery


text:
unable to wildcard search on platform version number or profile version number

User Story
This is a known issue carried over from https://github.com/chef/automate/issues/325
Let's revisit this when we have some time to give it the special attention it needs.
Definition of Done
Can filter with wildcard on platform version number and profile version number.

let's investigate why this is.
if it's not possible to do the wildcard searching on those fields, then let's go ahead and note that here and close the issue

@vjeffrey The reason that wildcard search does not work with the platform and profile version numbers is that the version numbers are in a separate field. For the client runs page we fixed this problem for the platform field by concatenating the version on to the platform field.

changed the issue title to reflect what needs to be done to make this work; sounds like we just need alias fields for both of those where we concatenate the version number onto the text field, as @lancewf mentioned was done for client runs

So we do have a field with the platform name and version combined.
https://github.com/chef/automate/blob/2e9f37aafb847850da5b5d38a443b9d7c6facfc2/components/compliance-service/ingest/pipeline/processor/report.go#L57
We need to update suggestions to use that field
https://github.com/chef/automate/blob/72c60c610a100fd8578eb36c419b1e65507a1a10/components/compliance-service/reporting/relaxting/suggestions.go#L32.
We also need to update filtering to use that field.
https://github.com/chef/automate/blob/997be2f1f15bb25fea61d315d61a3ac72f83fadf/components/compliance-service/reporting/relaxting/reports.go#L547
I will look to see if profile version will be the same.

We will need to do a migration to switch platform.full field in Elasticsearch to allow wildcards.
https://github.com/chef/automate/blob/be1cb11c6b66d48896e314f0b46086f9d99bbc4c/components/compliance-service/ingest/ingestic/mappings/comp-rep-date.go#L193

authors: lancewf vjeffrey

repo: chef/automate


text:
Allow user to configure load balancer's client certificate checking

:nut_and_bolt: Description: What code changed, and why?
Expose ssl_verify_client and ssl_client_certificate in the load balancer's nginx config so that they can be set by a user via the Automate config.
Fixes #2968.

:chains: Related Resources
:+1: Definition of Done
:athletic_shoe: How to Build and Test the Change
:white_check_mark: Checklist

[x] I have read the CONTRIBUTING document.
[ ] Tests added/updated?
[ ] Docs added/updated?
[x] All commits have been signed-off for the Developer Certification of Origin.

:camera: Screenshots, if applicable

We've decided to turn off client certificate checking at the load balancer, as it was done as a research spike for the automate-deployed chef infra server. Closing.


text:
[infra-proxy-service] Limit adding/removing Infra Servers and organizations to Editors

:nut_and_bolt: Description: What code changed, and why?

At present this PR only added a migration to append the infra:infraServers:* to the editor role.
I am not aware of the consequence of implied the policy to particular role need guidance to follow the path?
:chains: Related Resources
https://github.com/chef/automate/issues/3519
:+1: Definition of Done

Limit adding/removing Infra Servers and organizations to Editors

:athletic_shoe: How to Build and Test the Change
Steps to build:

rebuild components/authz-service

Steps to test:

After rebuilding login with editor user.

Go to Dashboard >> Infrastructure >> Chef servers (shown) earlier it was hidden.

Perform any actions on servers or orgs will work accordingly.

:white_check_mark: Checklist

[ ] I have read the CONTRIBUTING document.
[ ] Tests added/updated?
[ ] Docs added/updated?
[ ] All commits have been signed-off for the Developer Certification of Origin.

:camera: Screenshots, if applicable
Signed-off-by: Vivek Singh vivek.singh@msystechnologies.com

Thanks for providing the detail @btm
Going to close this PR and will raise another one as discussed changes on https://github.com/chef/automate/issues/3519#issuecomment-621392424


text:
Fixes the spec file as it should display the recipe name and not default

Signed-off-by: Franklin Webber franklin@chef.io
Description
The chef recipe generator creates a recipe file and a matching spec file. This spec file should be named after the recipe it is spec'ing.

Nice. Thanks

repo: chef/chef-dk


text:
Excluding failing tests from nightlies

This is the Chef-DK component of https://github.com/chef/chef/pull/3039 - the tests I modified in that PR will continue to run for regular chef builds, but will be ignored when running chef verify.  This will exclude them from the nightly builds in CI which have been failing.
\cc @chef/client-core

:+1:

authors: jdmundrawala tyler-ball


text:
yum_package showing wrong version of package when EPOCH specified

Description
Chef client showing misleading information about package version with package have EPOCH in metadata. On instance with already installed docker-ce 19.03.9-3.el7 package:
         * yum_package[docker-ce] action install
           - install version 19.03.9-3.el7 of package docker-ce-cli

Message is misleading because:

Package already installed
yum_package installing package version 3:19.03.9-3.el7 (epoch in the beginning).

Chef Version
All chef versions
Replica case
On CentOS install any package with EPOCH != 0 in metadata, for example official Docker CE package - https://download.docker.com/linux/centos/7/x86_64/stable/Packages/docker-ce-19.03.9-3.el7.x86_64.rpm

This is ultimately a dup of #9763

authors: aleksey-hariton lamont-granquist

repo: chef/chef


text:
Allowable values for --ebs-volume-type should state "standard (magnetic) | io1 | gp2 | sc1 | st1"

Change ec2_server_create.rb
 option :ebs_volume_type,
        :long => "--ebs-volume-type TYPE",
        :description => "Standard or Provisioned (io1) IOPS or General Purpose (gp2)",
        :proc => Proc.new { |key| Chef::Config[:knife][:ebs_volume_type] = key },
        :default => "standard"

to:
 option :ebs_volume_type,
        :long => "--ebs-volume-type TYPE",
        :description => "standard (magnetic) | io1 | gp2 | sc1 | st1",
        :proc => Proc.new { |key| Chef::Config[:knife][:ebs_volume_type] = key },
        :default => "standard"

to align with AWS CLI run-instances.
This assumes the AWS EBS disk type abbreviations such as gp2 are generally understood.
Default value should also be changed from standard (magnetic) to gp2 (SSD) to align with current AWS practice. However, this is a disruptive change for current code. I'll propose this separately.
See also #451. I have to do the prerequisite admin to do a PR, but didn't want this to get lost.

@rjhintz Thanks for your comments. We will get it fixed soon.

Ok, thanks. I couldn't figure out how to do a PR because the method for becoming a contributor seems obsolete. See #452

Fixed in #464

authors: NimishaS dheerajd-msys rjhintz


text:
Add note about SlackArchive.

/cc @thom @iennae

I think I got the formatting right but I'm yolo-ing it up and editing via the web UI :D

repo: chef/slackin


text:
An update in docker-compose.yml should trigger the integration-test w…

…orkflow, and not the build workflow

Nice, works as expected.

repo: chehl/chameleon


text:
fix #32

#32  修正dialog.css和toast.css没有生效的问题

这两个css是不会独立生成文件的，在打包时已经合并了。
如果是需要单独生成文件，需要在添加entry。

不是单独生成文件。是样式虽然合并到js里了，但是页面并没有应用样式

修正之前

原master上start-dev,地址 http://localhost:3010/a.html?component=toast,截图如下，toast的样式没有应用

合并 #35 后，再次访问效果如下

这边仓库里产生了一个多余分支 ian4hu-fix-css-loader, 可能需要清理下

repo: chemdemo/webpack-seed

license: mit


text:
🛑 Homepage is down

In c36d616, Homepage (https://larrychen.tech) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Homepage is back up in c3d4110.

repo: chendachao/uptime


text:
🛑 tt is down

In e00bed5, tt (https://telebot-app-serverless-i7z8-chenhaonanniubi.vercel.app/checkhealth) was down:

HTTP code: 500
Response time: 2734 ms

Resolved: tt is back up in 3fde4e5.

repo: chenhaonanniubi/upptime


text:
🛑 tt is down

In 89adfd8, tt (https://telebot-app-serverless-i7z8-chenhaonanniubi.vercel.app/checkhealth) was down:

HTTP code: 504
Response time: 10231 ms

Resolved: tt is back up in 1fdbf31 after 13 minutes.


text:
🛑 tt is down

In c88b5a1, tt (https://telebot-app-serverless-i7z8-chenhaonanniubi.vercel.app/checkhealth) was down:

HTTP code: 500
Response time: 2969 ms

Resolved: tt is back up in a2d3a3d after 20 minutes.


text:
🛑 tt is down

In f8c7745, tt (https://telebot-app-serverless-i7z8-chenhaonanniubi.vercel.app/checkhealth) was down:

HTTP code: 500
Response time: 2408 ms

Resolved: tt is back up in 9a6b5cf after 20 minutes.


text:
🛑 Blog is down

In 7ed79ba, Blog (https://blog.chenishr.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Blog is back up in b02933f after 10 minutes.

repo: chenishr/upptime


text:
MAC: Package linux failed

NPM Version: 4.6.1
Node Version: v7.10.0
The build for OSX dmg and Windwos works fine, but when I try to build for Linux the package fails:
Build Response
Packaging for linux x64 using electron 1.7.0 to release/linux-unpacked
Building AppImage for arch x64
Building deb
Error: Exit code: 1. Command failed: /Users/mikepriest/Library/Caches/electron-builder/fpm/fpm-1.8.1-20150715-2.2.2/fpm -s dir -t deb --architecture a
md64 --name ExamBrowser --force --after-install /var/folders/bd/rz559x1s3md7kmxdzgmfqy0h0000gn/T/electron-builder-VUIcpu/0-2-after-install --after-rem
ove /var/folders/bd/rz559x1s3md7kmxdzgmfqy0h0000gn/T/electron-builder-VUIcpu/0-3-after-remove --description
 Trifork ExamBrowser is a locked down web-browser to be used in secure high-stakes examination environments. --maintainer C. T. Lin <chentsulin@gmail.
com> --vendor C. T. Lin <chentsulin@gmail.com> --version 1.0.0 --package /Users/mikepriest/source/Browser/exambrowser-electron/release/ExamBrowser_1.0
.0_amd64.deb --url https://github.com/chentsulin/electron-react-boilerplate --deb-compression xz --depends gconf2 --depends gconf-service --depends li
bnotify4 --depends libappindicator1 --depends libxtst6 --depends libnss3 --depends libxss1 --license MIT /Users/mikepriest/source/Browser/exambrowser-
electron/release/linux-unpacked/=/opt/exambrowser /Users/mikepriest/source/Browser/exambrowser-electron/resources/icons/1024x1024.png=/usr/share/icons
/hicolor/1024x1024/apps/exambrowser.png /Users/mikepriest/source/Browser/exambrowser-electron/resources/icons/128x128.png=/usr/share/icons/hicolor/128
x128/apps/exambrowser.png /Users/mikepriest/source/Browser/exambrowser-electron/resources/icons/16x16.png=/usr/share/icons/hicolor/16x16/apps/exambrow
ser.png /Users/mikepriest/source/Browser/exambrowser-electron/resources/icons/24x24.png=/usr/share/icons/hicolor/24x24/apps/exambrowser.png /Users/mik
epriest/source/Browser/exambrowser-electron/resources/icons/256x256.png=/usr/share/icons/hicolor/256x256/apps/exambrowser.png /Users/mikepriest/source
/Browser/exambrowser-electron/resources/icons/32x32.png=/usr/share/icons/hicolor/32x32/apps/exambrowser.png /Users/mikepriest/source/Browser/exambrows
er-electron/resources/icons/48x48.png=/usr/share/icons/hicolor/48x48/apps/exambrowser.png /Users/mikepriest/source/Browser/exambrowser-electron/resour
ces/icons/512x512.png=/usr/share/icons/hicolor/512x512/apps/exambrowser.png /Users/mikepriest/source/Browser/exambrowser-electron/resources/icons/64x6
4.png=/usr/share/icons/hicolor/64x64/apps/exambrowser.png /Users/mikepriest/source/Browser/exambrowser-electron/resources/icons/96x96.png=/usr/share/i
cons/hicolor/96x96/apps/exambrowser.png /var/folders/bd/rz559x1s3md7kmxdzgmfqy0h0000gn/T/electron-builder-VUIcpu/0-4-exambrowser.desktop=/usr/share/ap
plications/exambrowser.desktop

{:timestamp=>"2017-05-14T18:05:04.286885+0200", :message=>"Debian tools (dpkg/apt) don't do well with packages that use capital letters in the name. I
n some cases it will automatically downcase them, in others it will not. It is confusing. Best to not use any capital letters at all. I have downcased
 the package name for you just to be safe.", :oldname=>"ExamBrowser", :fixedname=>"exambrowser", :level=>:warn}
{:timestamp=>"2017-05-14T18:05:04.299923+0200", :message=>"Debian packaging tools generally labels all files in /etc as config files, as mandated by p
olicy, so fpm defaults to this behavior for deb packages. You can disable this default behavior with --deb-no-default-config-files flag", :level=>:war
n}
{:timestamp=>"2017-05-14T18:05:04.633739+0200", :message=>"Debian packaging tools generally labels all files in /etc as config files, as mandated by p
olicy, so fpm defaults to this behavior for deb packages. You can disable this default behavior with --deb-no-default-config-files flag", :level=>:war
n}
{:timestamp=>"2017-05-14T18:05:05.006964+0200", :message=>"Process failed: gtar failed (exit code 2). Full command was:[\"gtar\", \"-C\", \"/var/folde
rs/bd/rz559x1s3md7kmxdzgmfqy0h0000gn/T/package-dir-staging-46259710e12e86414e3108cfa6201953fb85c7cdd6e4693b7ea68ab5e864\", \"-J\", \"--numeric-owner\"
, \"--owner\", \"0\", \"--numeric-owner\", \"--group\", \"0\", \"-cf\", \"/var/folders/bd/rz559x1s3md7kmxdzgmfqy0h0000gn/T/package-deb-build-a3f5e7dcc
71a06c595e2b037d40965e6c6a586a08248e7871f92825678aa/data.tar.xz\", \".\"]", :level=>:error}

 at /Users/mikepriest/source/Browser/exambrowser-electron/node_modules/electron-builder-util/src/util.ts:75:16
    at ChildProcess.exithandler (child_process.js:212:5)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:194:7)
    at maybeClose (internal/child_process.js:899:16)
    at Socket.<anonymous> (internal/child_process.js:342:11)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:191:7)
    at Pipe._handle.close [as _onclose] (net.js:511:12)
From previous event:
    at exec (/Users/mikepriest/source/Browser/exambrowser-electron/node_modules/electron-builder-util/src/util.ts:53:3)
    at /Users/mikepriest/source/Browser/exambrowser-electron/node_modules/electron-builder/src/targets/fpm.ts:176:11
    at Generator.next (<anonymous>)
From previous event:
    at FpmTarget.build (/Users/mikepriest/source/Browser/exambrowser-electron/node_modules/electron-builder/out/targets/fpm.js:227:11)
    at default.each.it (/Users/mikepriest/source/Browser/exambrowser-electron/node_modules/electron-builder/src/platformPackager.ts:107:87)
    at runCallback (timers.js:672:20)
    at tryOnImmediate (timers.js:645:5)
    at processImmediate [as _immediateCallback] (timers.js:617:5)
From previous event:
    at postAsyncTasks.push.default.map.then (/Users/mikepriest/source/Browser/exambrowser-electron/node_modules/electron-builder/src/platformPackager.
ts:107:35)
From previous event:
    at LinuxPackager.packageInDistributableFormat (/Users/mikepriest/source/Browser/exambrowser-electron/node_modules/electron-builder/src/platformPac
kager.ts:107:8)
    at /Users/mikepriest/source/Browser/exambrowser-electron/node_modules/electron-builder/src/platformPackager.ts:102:10
    at Generator.next (<anonymous>)
    at runCallback (timers.js:672:20)
    at tryOnImmediate (timers.js:645:5)
    at processImmediate [as _immediateCallback] (timers.js:617:5)
From previous event:
    at LinuxPackager.pack (/Users/mikepriest/source/Browser/exambrowser-electron/node_modules/electron-builder/out/platformPackager.js:169:11)
    at /Users/mikepriest/source/Browser/exambrowser-electron/node_modules/electron-builder/src/packager.ts:257:24
    at Generator.next (<anonymous>)

at xfs.stat (/Users/mikepriest/source/Browser/exambrowser-electron/node_modules/fs-extra-p/node_modules/fs-extra/lib/mkdirs/mkdirs.js:56:16)
    at /Users/mikepriest/source/Browser/exambrowser-electron/node_modules/graceful-fs/polyfills.js:287:18
    at FSReqWrap.oncomplete (fs.js:114:15)
From previous event:
    at Packager.doBuild (/Users/mikepriest/source/Browser/exambrowser-electron/node_modules/electron-builder/out/packager.js:379:11)
    at /Users/mikepriest/source/Browser/exambrowser-electron/node_modules/electron-builder/src/packager.ts:170:52
    at Generator.next (<anonymous>)
    at runCallback (timers.js:672:20)
    at tryOnImmediate (timers.js:645:5)
    at processImmediate [as _immediateCallback] (timers.js:617:5)
From previous event:
    at Packager.build (/Users/mikepriest/source/Browser/exambrowser-electron/node_modules/electron-builder/out/packager.js:274:11)
    at /Users/mikepriest/source/Browser/exambrowser-electron/node_modules/electron-builder/src/builder.ts:198:33
    at Generator.next (<anonymous>)
From previous event:
    at build (/Users/mikepriest/source/Browser/exambrowser-electron/node_modules/electron-builder/out/builder.js:70:21)
    at Object.<anonymous> (/Users/mikepriest/source/Browser/exambrowser-electron/node_modules/electron-builder/out/cli/build-cli.js:71:41)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.runMain (module.js:605:10)
    at run (bootstrap_node.js:427:7)
    at startup (bootstrap_node.js:151:9)
    at bootstrap_node.js:542:3

NPM Log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node',
1 verbose cli   '/usr/local/bin/npm',
1 verbose cli   'run',
1 verbose cli   'package-linux' ]
2 info using npm@4.6.1
3 info using node@v7.10.0
4 verbose run-script [ 'prepackage-linux', 'package-linux', 'postpackage-linux' ]
5 info lifecycle electron-exam-browser@0.12.0~prepackage-linux: electron-exam-browser@0.12.0
6 silly lifecycle electron-exam-browser@0.12.0~prepackage-linux: no script for prepackage-linux, continuing
7 info lifecycle electron-exam-browser@0.12.0~package-linux: electron-exam-browser@0.12.0
8 verbose lifecycle electron-exam-browser@0.12.0~package-linux: unsafe-perm in lifecycle true
9 verbose lifecycle electron-exam-browser@0.12.0~package-linux: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/Users/mikepriest/source/Browser/exambrowser-electron/node_modules/.bin:/usr/local/apache-maven/apache-maven-3.3.9/bin:/Library/Java/JavaVirtualMachines/jdk1.8.0_45.jdk/Contents/Home/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/usr/local/apache-maven/apache-maven-3.3.9/bin:/Library/Java/JavaVirtualMachines/jdk1.8.0_45.jdk/Contents/Home/bin:
10 verbose lifecycle electron-exam-browser@0.12.0~package-linux: CWD: /Users/mikepriest/source/Browser/exambrowser-electron
11 silly lifecycle electron-exam-browser@0.12.0~package-linux: Args: [ '-c', 'npm run build && build --linux' ]
12 silly lifecycle electron-exam-browser@0.12.0~package-linux: Returned: code: 255  signal: null
13 info lifecycle electron-exam-browser@0.12.0~package-linux: Failed to exec package-linux script
14 verbose stack Error: electron-exam-browser@0.12.0 package-linux: `npm run build && build --linux`
14 verbose stack Exit status 255
14 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:279:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:194:7)
14 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:194:7)
14 verbose stack     at maybeClose (internal/child_process.js:899:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid electron-exam-browser@0.12.0
16 verbose cwd /Users/mikepriest/source/Browser/exambrowser-electron
17 verbose Darwin 16.5.0
18 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "package-linux"
19 verbose node v7.10.0
20 verbose npm  v4.6.1
21 error code ELIFECYCLE
22 error errno 255
23 error electron-exam-browser@0.12.0 package-linux: `npm run build && build --linux`
23 error Exit status 255
24 error Failed at the electron-exam-browser@0.12.0 package-linux script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 255, true ]

Seems to be an issue with electron-builder. Would recommend looking there for solutions

@10SPD after looking at the stack trace more, it seems like you dont have the requirements installed. See this section of the installation requirements

@amilajack  It does look like I was missing the Linux dependency. Somehow missed that in the docs.
Thanks, you're a life saver!

@10SPD May I know how did you solve this and what package were you missing? I installed rpm and the problem still persists. Thanks!

https://github.com/electron-userland/electron-builder/wiki/Multi-Platform-Build

@amilajack Thank you. was missing gnu-tar

repo: chentsulin/electron-react-boilerplate


text:
vue3版本

您好, 基于您当前的项目实现了一个vue3版本的 https://github.com/xiaofulzm/vue3-scroll-seamless

666 赞一个

感谢

authors: johnsnow20087349 weixiaoxiang xiaofulzm


text:
Ion-java-cli-process

Description
Ion-java-cli has 2 core parts for version one: process and compare.
This commit is for process which supports:

--output
--output-format
--error-report

note: I just noticed some check style errors such as I forget space after if-else statement, I'll fix them in the next commit.
What I finished

Support binary/text/pretty format
test: some example files which include string value, integer, list, structure and local symbol tables.
Support events format
test: some example files which include string value, integer, list, structure and local symbol tables.
Support -o options which outputs a file to ion-java/.
test: some example files which include string value, integer, list, structure and local symbol tables.
Support -e options which outputs error report to ion-java/.
test: some example files which include string value, integer, list, structure and local symbol tables.
Implement Event structure
Able to Write a Event structure to outputStream in Events type
test: converted a ionReader value to a Scalar event
Convert ionStream to Event structure
test: converted five types of events to outputStream(container_start, container_end, symbol_table, scalar and stream_end)
Check if Symbol table changes
test: It works for two local symbol tables with the same imports or the second local symbol table imports the previous local symbol table's name (which means the imports field of the current symbol table is previous symbol table's name)

What I'm going to do next/not implement yet

Error report structure
Embedded stream
--output-format none

Question/Specific areas what to check:

If Annotation is $0, both text and import location show 'null.string' while ion-c just simply shows 'null'. Not sure if it's because ion-java and ion-c performance different.
Reproduce/code: Code is in Event.java line 55-59

The output file is always start with a blank line.
Reproduce/code: To reproduce this, use -o  and -f events options and generate a new output file which its first line is blank.

When checking if 2 symbol tables are same, my logic checks the cases of systemTables, shareTables and substitue too which may be redundant.
reproduce/code: Code is in IonProcess.java: line 236

Local symbol table has 2 fields, imports and symbols. I only checked imports when checking if 2 symbol tables are same, Do we need to check symbols as well?)
reproduce/code: Code is in IonProcess.java: line 236

Addition question:

I checked styles such as extra space, camel format. if I miss anything please comment the line number, I"ll fix them in the next commit. :)
Not sure if I name the functions or variables appropriately. For example, IonProcess 228, I named two symbol tables x and y.

I created another pr2 whose destination is pr1: https://github.com/cheqianh/ion-java/pull/2
Thanks!

repo: cheqianh/ion-java


text:
🛑 Chequeado is down

In 3544942, Chequeado (https://chequeado.com) was down:

HTTP code: 502
Response time: 9060 ms

Resolved: Chequeado is back up in f47ca47.

repo: chequeado/status


text:
Add CakePHP framework integration

Thank you for the great library :)
Demo/Showcase is also now online:
https://sandbox.dereuromark.de/sandbox/qr-code-examples

Oh hey that's nice! A suggestion for your library: add the option connectPaths to the SVG options to avoid hairlines between the modules/layers.

Fixed it :) Thx!

I also proposed this for https://github.com/ziadoz/awesome-php/pull/1280 if that's all right.
There was no QR code topic yet.

Oh thank you!

authors: codemasher dereuromark

repo: chillerlan/php-qrcode


text:
cpu占用资源太高

cpu占用资源太高

CPU满占用是由于上一个版本的死循环查询方法造成的；
现在已更新，引入了apscheduler库，改进了定时任务方法，极大降低了CPU占用。


text:
Python 3 Support

Hi,
Thanks again for the excellent project. We are using documentedlist for http://docs.mitmproxy.org/en/stable/features/filters.html and it work just great.
We are currently migrating everything to Python 3 - are there any plans to add Python 3 support? :smiley:
/cc @dufferzafar

I see only one unicode() call which should fail with python 3. I've now fixed that and bumped the version to 0.4. Let me know if you find any other python 3 compatibility issues.

Wow - I just upgraded our stuff and everything just works. Thanks so much! :smiley: :blush:

authors: chintal mhils

repo: chintal/documentedlist


text:
Comment unused modules

Hi Team
Currently we are not using el2_dbg and el2_ifu modules of Caliptra, Do we have any macros to comment these modules.

Are you certain? Caliptra instantiates both these modules at caliptra_top_dut.rvtop.veer

Closing due to inactivity.

authors: Nitsirks Syed-mudabbir-ahsan

repo: chipsalliance/caliptra-rtl


text:
add BulkConnect, upstream from rocket-chip.

Contributor Checklist

[ ] Did you add Scaladoc to every public function/method?
[ ] Did you add at least one test demonstrating the PR?
[ ] Did you delete any extraneous printlns/debugging code?
[ ] Did you specify the type of improvement?
[ ] Did you add appropriate documentation in docs/src?
[ ] Did you state the API impact?
[ ] Did you specify the code generation impact?
[ ] Did you request a desired merge strategy?
[ ] Did you add text to be included in the Release Notes for this change?

Type of Improvement

API Impact

Backend Code Generation Impact

Desired Merge Strategy

Release Notes

Reviewer Checklist (only modified by reviewer)

[ ] Did you add the appropriate labels?
[ ] Did you mark the proper milestone (3.2.x, 3.3.x, 3.4.0, 3.5.0) ?
[ ] Did you review?
[ ] Did you check whether all relevant Contributor checkboxes have been checked?
[ ] Did you mark as Please Merge?

do you plan to add scala tests for these? Seems like it would be very helpful also as a demonstration

do you plan to add scala tests for these? Seems like it would be very helpful also as a demonstration

I'll add tests later this week, which is also the reason why this PR is still a draft.

I'll add tests later this week, which is also the reason why this PR is still a draft.


text:
i'd like to have an explanation about this problem

https://www.virustotal.com/gui/file/4ee1215868df906df34ab448dceba76e7260121c062db4d1d911b4220ec85920/detection

most probably this is because of native asus libraries make calls to rundll32

repo: chiputillo/AsusCurveFanControl


text:
filter by string similarity

I want to implement search feature which can find elements from database containing string field the most similar to given one. Most naive approach would be to fetch all the items, and then sort which ones have the higher number of matching words in string. What can be better solution utilizing optimization strength of chisel?

What do you need exactly for "most similar" match? Something like soundex, which we could probably expose as part of the ChiselStrike API?
https://www.postgresql.org/docs/current/fuzzystrmatch.html#id-1.11.7.26.6
https://www.sqlite.org/lang_corefunc.html#soundex

That would be great. If you curious about exact scenario, I am working on my chat assistant. Given question in telegram message, I want to find three most similar previously answered questions in my sqlite, and then combine those three Q/A as prompt to gpt3 responding back to questioner.

Perhaps this can be integrated for fuzzy search? https://github.com/LyraSearch/lyra/issues/190

repo: chiselstrike/chiselstrike


text:
support for YAML front matter

Like this: http://jekyllrb.com/docs/frontmatter/

It's been a year but github is currently parsing front matter into a table. Now that this is part of the official GFM parsing, I think we should put it into marked (into gfm) as well.
e.g.: https://github.com/dvcrn/dvcrn.github.io/blob/master/_posts/2015-10-13-my_dream_editor.markdown
Front matter:
---
layout: post
title: "My Dream Editor"
date: "2015-10-13 16:05:17 +0900"
---

Output:

@dvcrn if GitHub was, you wouldn't need to use an image as an example right? :stuck_out_tongue_winking_eye:

Nice catch! @dvcrn !
@adam-lynch click the other link. You can see it at the top of that page.

Elliott, thanks :). Weird how they render markdown differently here hmm
On Fri, 23 Oct 2015, 17:13 Elliott Regan notifications@github.com wrote:

Nice catch! @dvcrn https://github.com/dvcrn !
@adam-lynch https://github.com/adam-lynch click the other link. You can
see it at the top of that page.
—
Reply to this email directly or view it on GitHub
https://github.com/chjj/marked/issues/485#issuecomment-150622089.

They don't mention it in their docs, but they are definitely showing key-values, even complex ones with arrays, as a table. I still prefer JSON because it's easier to work with, but it makes sense for Github to display it Asa table.

They don't mention it in their docs

It's probably just left out because it's unrelated to their markdown parser. See https://github.com/blog/1647-viewing-yaml-metadata-in-your-documents

FYI if people are still looking, @adam-lynch's comment here is conceptually the way to go.
Also, metalsmith is really great for this type of think, and includes a metalsmith-markdown plugin that is built on top of marked. When used in combination with metalsmith-layouts, you can do some really cool things.
For example (in a gulp pipeline):
function _metalsmith() {
  var files = ['source/**', '!source/layouts/**', '!source/partials/**'];

  return gulp
      .src(files)
      .pipe(metalsmith({
        use: [
          markdown(),                   // from `metalsmith-markdown` (`marked` wrapper)
          layouts({                     // from `metalsmith-layouts`
            engine: 'handlebars',       // any engine from consolidate.js
            default: 'page.html',
            directory: 'source/layouts',
            partials: 'source/partials',
            pattern: '**/*.html'
          })
        ]
      }))
      .pipe(gulp.dest('build'));
}

metalsmith-layouts is automatically looking for the file.frontMatter property set internally by gulp-front-matter, and using it to render handlebars data for a fixed set of layouts.
Example markdown:
---
layout:    documentation.html
title:     Documentation - 4.2.1
permalink: /documentation/4.2.1/
---
- some
- list

some content

Example handlebars template:
<!DOCTYPE html>

{{title}}

    {{{contents}}}

Outputs:
<!DOCTYPE html>

Documentation - 4.2.1

some

list

some content

None of this would be possible without the work by @chjj and team, so thanks for that.
I originally came here looking for answers, so hopefully this helps the next guy/gal.
Cheers.

See #956
Closing as out of scope for the two targeted specifications of Marked.

:( but that makes sense.

Memo for browser 😆

I want to ignore frontmatter for my scenario.
Here is how I do it:
 md = md.replace(/^---$.*^---$/ms, '');

You can also use front-matter to get any edge cases.
md = frontMatter(md).body;

I came across a case where I do want the rendered output from my markdown to be handled differently based on the front matter. My use case is too niche to describe, but suppose we want to handle the case where we want to prefix some text to the beginning of headers, such that:
---
headingPrefix: Chapter:
---
# Some things I was thinking
These are some things I was thinking...

would become

Chapter: Some things I was thinking

These are some things I was thinking...

still contrived, but you get the point; the text in the optional front-matter would be used in rendering HTML from the markdown.
First the extension. To make this work, instead of just creating the extension we create a function that returns the extension; the function can take parameter(s) for the information it needs:
import { marked } from 'marked';

export const fixHeadings = (headingPrefix: string): Partial<Omit<marked.Renderer<false>, 'options'>> => {
  return {
    heading(text, level) {
      return `<h${level}>${headingPrefix} ${text}</h${level}>`;
    },
  };
};

Using the front-matter package we can handle attributes in the markdown front-matter similar to this:
import { marked } from 'marked';
import fm from 'front-matter';
import { fixHeadings } from './fixheadings'

interface MarkdownOptions {
  headingPrefix: string;
  // other options that can be set in the front-matter
}

const defaultOptions: MarkdownOptions = {
  headingPrefix: 'Chapter:', // good to have a default, because the front-matter might not exist
};

export const renderedOutputFromMarkdown = (md: string): string => {
  const options = { ...defaultOptions };
  // by default, the markdown we want to parse is the entire input
  let markdownString = md;

  try {
    const fmResult = fm(md);
    // if there is front-matter the markdown to parse is reduced to just the `body` from `front-matter`
    markdownString = fmResult.body;
    if ((fmResult.attributes as any).headingPrefix) {
      options.headingPrefix = (fmResult.attributes as any).headingPrefix;
    }
  } catch {
    // do nothing; can easily throw exceptions, especially when fm being edited
  }
  marked.use({ renderer: fixHeadings(options.headingPrefix) });
  // other marked.use() options go here as well

  return marked.parse(markdownString);
};

authors: UziTech adam-lynch dvcrn elliottregan joshbruce justinhelmer mcapodici scottgonzalez sernaferna up9cloud

repo: chjj/marked


text:
Failed to install tty.js with npm

I tried to install tty.js
$ npm install tty.js

But I got an error as below.
npm ERR! Linux 3.2.0-84-generic-pae
npm ERR! argv "/home/hayashida/.nvm/versions/node/v0.12.7/bin/node" "/home/hayashida/.nvm/versions/node/v0.12.7/bin/npm" "install" "tty.js"
npm ERR! node v0.12.7
npm ERR! npm  v2.11.3

npm ERR! version not found: pty.js@0.2.7
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /home/hayashida/Programs/ttyjstest/npm-debug.log

Is package dependency broken?
My environment is:

npm 2.11.3
Ubuntu Linux
Node.js v0.12.7

npm-debug.log is here.

I have accured same problem and created pull request, hope @chjj will approve merge it soon

Hi! We have exactly same bug. Can you fix it as soon as possible?

@G07cha
Thank you for your fix.  I wait @chjj will marge.
@kernelt
See #147.

Actually you can install from my fork:
npm install -g https://github.com/G07cha/tty.js.git

But if you want to recieve future updates keep eye on my pull request and this issue. If issue will be closed you can switch back to original repository.

It was still using an old version of pty.js (which for some reason was removed from npm? not sure). Should be fixed now.

Thanks, closing my pull request

:tada:

Oh, this new version of pty.js also solves the zombie process problem that initially started ocurring in node >0.8.0.

authors: G07cha chjj kernelt rhysd


text:
Cannot connect to MQTT over Websocket with Xamarin

Hi,
I tried to connect to the AWS iot core over Websockets in my Xamarin App and it fails.
This is how I connect:
            var optionsBuilder = new MqttClientOptionsBuilder();
            WebsocketUrlSigner signer = new WebsocketUrlSigner();
            var credentials = CognitoSession.Current.CurrentCredentials.GetCredentials();
            Credentials c = new Credentials()
            {
                AccessKeyId = credentials.AccessKey,
                SecretKey = credentials.SecretKey,
                SessionToken = credentials.Token
            };
            var url = signer.GetWebsocketUrl(c);

            optionsBuilder.WithWebSocketServer(url);
            optionsBuilder.WithClientId(clientId);
            optionsBuilder.WithProtocolVersion(MqttProtocolVersion.V311);

            MqttClientOptionsBuilderTlsParameters tlsParams = new MqttClientOptionsBuilderTlsParameters()
            {
                UseTls = true,
                SslProtocol = System.Security.Authentication.SslProtocols.Tls12
            };
            optionsBuilder.WithTls(tlsParams);

            options = optionsBuilder.Build();

The url is a signed url with SigV4 with the cognito AccessKey, SecretKey and Token.
When I call client.ConnectAsync(options) I get the following Exception:
{MQTTnet.Exceptions.MqttCommunicationException}:
Message: "Unable to connect to the remote server"
Source: mscorlib
StackTrace:
at MQTTnet.Adapter.MqttChannelAdapter.WrapException (System.Exception exception) [0x0005a] in <0cba824eb1f047f28db40a990343853f>:0
at MQTTnet.Adapter.MqttChannelAdapter+d__20.MoveNext () [0x000bf] in <0cba824eb1f047f28db40a990343853f>:0
--- End of stack trace from previous location where exception was thrown ---
at MQTTnet.Client.MqttClient+d__30.MoveNext () [0x00152] in <0cba824eb1f047f28db40a990343853f>:0
--- End of stack trace from previous location where exception was thrown ---
at MQTTnet.Client.MqttClient+d__30.MoveNext () [0x00356] in <0cba824eb1f047f28db40a990343853f>:0
--- End of stack trace from previous location where exception was thrown ---
In the inner exception there is a WebSocketErrorCode and it says "System.Net.WebSockets.WebSocketError.Success"
In a little Windows Forms test application with the same parameters it works.
Do I miss something in the parameters for Xamarin?
Any help appreciated.

Hi,
Cristian built a test adapter factory supporting WebSocket4Net. See
https://mail.google.com/mail/u/0/?tab=rm#search/aws/FMfcgxmZTvKnrmSKSpwjSDsqMtfSwmJL
I didn't test it a lot but it worked.
I'm realy interested in AWS IOT and it is a pity that there is still an issue with it.

I know I had been working with this library and webSockets using the server pieces of the library on the other end.  give me some time, and i'll look up how I wrote the connection.  I was using username/password authentication, which may make a difference.

I released a new extension nuget which allows using WebSocket4Net. All you need to do is download the new nuget and call UseWebSocket4Net() on the MqttFactory instance before creating the client. Please let me know if this works with AWS/Xamarin.

I updated MQTTnet to 3.0.2.
Which extention nuget should I install to call UseWebSocket4Net() ?

https://www.nuget.org/packages/MQTTnet.Extensions.WebSocket4Net/3.0.3-rc1


text:
RFM - Kid3

Current Maintainer

[ ] I am the maintainer of the package and wish to pass it to someone else;

I DON'T Want To Become The Maintainer

[x] I have followed the Package Triage Process and I do NOT want to become maintainer of the package;
[x] There is no existing open maintainer request for this package;

Checklist

[x] Issue title starts with 'RFM - '

Existing Package Details
Package URL: https://chocolatey.org/packages/kid3
Package source URL: The Chocolatey packages repo of the maintainer is gone. The source was previously located at: https://github.com/svnpenn/p/tree/master/kid3
You can download the raw nupkg file here: https://chocolatey.org/api/v2/package/kid3/3.3
Date the maintainer was contacted: 21-06-2019
How the maintainer was contacted: With the "Contact Maintainer" function.

Status: In progress

Waiting to be added as maintainer (request already sent to Chocolatey contact-site admins).
Updated package ready to be published: https://github.com/chtof/chocolatey-packages/tree/master/automatic/kid3

Status: Review
https://chocolatey.org/packages/kid3

Status: Published
https://chocolatey.org/packages/kid3
Can be closed.

authors: CypherNL chtof


text:
(putty.install) Tries to write MSI log file at an invalid location

Chocolatey Version
1.2.1
Chocolatey License
None
Package Version
0.78
Current Behaviour
putty.install fails to upgrade to 0.78 as the path for the MSI log does not exist.
putty.install v0.78 [Approved]
putty.install package files upgrade completed. Performing other installation steps.
Installing 64-bit putty.install...
WARNING: Something is wrong with the install log location specified. Please fix this in the package silent arguments (or in install arguments you specified). The directory specified as part of the log file path must exist for an MSI to be able to log to that directory. This is most likely an issue with the 'putty.install' package and not with Chocolatey itself. Please follow up with the package maintainer(s) directly.
ERROR: Running ["C:\Windows\System32\msiexec.exe" /i "C:\ProgramData\chocolatey\lib\putty.install\tools\putty-64bit-0.78-installer.msi" /qn /norestart /l*v "c:/programdata/chocolatey/choco-cache\chocolatey\putty.install\0.78\install.log" ] was not successful. Exit code was '1622'. Exit code indicates the following: Something is wrong with the install log location specified. Please fix this in the package silent arguments (or in install arguments you specified). The directory specified as part of the log file path must exist for an MSI to be able to log to that directory. This is most likely an issue with the 'putty.install' package and not with Chocolatey itself. Please follow up with the package maintainer(s) directly..
The upgrade of putty.install was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\putty.install\tools\chocolateyInstall.ps1'.
 See log for details.

Expected Behaviour
The package should determine if the path that it wants the MSI log file to be written to actually exists before passing it to the installer. Alternatively, it should not use a path under $env:TEMP but format the log filename instead (package name, version etc.). Many packages just use the root of $env:TEMP.
Steps To Reproduce
I cannot reproduce this behaviour on a test system. But I can reproduce it on my own system and I have provided the output above, and the log below.
I was upgrading from 0.77 to 0.78.
Environment
- Operating System: Microsoft Windows NT 10.0.19044.0
- PowerShell Version: 5.1.19041.1682
- Shell: PowerShell

Chocolatey Log
Gist is here.
Anything else?
My choco-cache setting:
> choco config
Chocolatey v1.2.1
Settings
cacheLocation = c:/programdata/chocolatey/choco-cache | Cache location if not TEMP folder. Replaces `$env:TEMP` value for choco.exe process. It is highly recommended this be set to make Chocolatey more deterministic in cleanup.

I uninstalled and reinstalled the package and the problem went away. I have absolutely no idea what is going on. The putty.install folder is still not in c:\programdata\chocolatey\choco-cache  but it still installs. Yet it didn't when upgrading.
No idea. Very confused. Closing this.