text:
[ SQL上线 ]

进行SQL上线时出现如下报错：

所使用的数据库是其他主机的数据库。不是docker-compose的默认库

具体修改了哪些配置，请列举出来。

docker-compose的配置如下，仅注释了Mysql
version: '3'

services:
  redis:
    image: redis:5
    container_name: redis
    restart: always
    ports:
      - "6379:6379"

#  mysql:
#    image: mysql:5.7
#    container_name: mysql
#    restart: always
#    ports:
#      - "3306:3306"
#    volumes:
#      - "./mysql/my.cnf:/etc/mysql/my.cnf"
#      - "./mysql/datadir:/var/lib/mysql"
#    environment:
#      MYSQL_DATABASE: archery
#      MYSQL_ROOT_PASSWORD: 123456

  mongo:
    image: mongo:3.6
    container_name: mongo
    restart: always
    volumes:
      - "./mongo/datadir:/data/db"
    ports:
      - 27017:27017
    environment:
      MONGO_INITDB_ROOT_USERNAME: root
      MONGO_INITDB_ROOT_PASSWORD: 123456

  inception:
    image: hhyo/inception
    container_name: inception
    restart: always
    ports:
      - "6669:6669"
    volumes:
      - "./inception/inc.cnf:/etc/inc.cnf"

  goinception:
    image: hanchuanchuan/goinception
    container_name: goinception
    restart: always
    ports:
      - "4000:4000"
    volumes:
      - "./inception/config.toml:/etc/config.toml"

  archery:
    image: hhyo/archery
    container_name: archery
    restart: always
    ports:
      - "9123:9123"
    volumes:
      - "./archery/settings.py:/opt/archery/archery/settings.py"
      - "./archery/soar.yaml:/etc/soar.yaml"
      - "./archery/downloads:/opt/archery/downloads"
    command: ["bash","/opt/archery/src/docker/startup.sh"]
    environment:
      NGINX_PORT: 9123

然后进入archery容器，修改Mysql的配置。
vi /opt/archery/archery/settings.py
   119	DATABASES = {
   120	    'default': {
   121	        'ENGINE': 'django.db.backends.mysql',
   122	        'NAME': 'archery',
   123	        'USER': 'root',
   124	        'PASSWORD': '123456',
   125	        'HOST': '192.168.10.187',
   126	        'PORT': '3316',
   127	        'OPTIONS': {
   128	            'init_command': "SET sql_mode='STRICT_TRANS_TABLES'",
   129	            'charset': 'utf8mb4'
   130	        },
   131	        'TEST': {
   132	            'NAME': 'test_archery',
   133	            'CHARSET': 'utf8',
   134	        },

@LeoQuote

@hhyo

看审核信息是goinception连不上要上线的mysql实例或者是备份数据库，系统配置测试goinception可以正常连接么

最后是怎么解决的？麻烦留下一个最终的解决方案，方便后续用户查看

解决方案：
最终我使用docker-compose默认的mysql重新启动了一下。问题解决。

进行SQL上线时出现如下报错：

所使用的数据库是其他主机的数据库。不是docker-compose的默认库

为啥我的这里选不了数据库，我是用docker安装的

现在问题解决了嘛？
在 2019-06-14 11:37:36，"007mawenbin" notifications@github.com 写道：
进行SQL上线时出现如下报错：
所使用的数据库是其他主机的数据库。不是docker-compose的默认库
为啥我的这里选不了数据库，我是用docker安装的
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

解决了呢，谢谢。是资源组没有关联实例的原因。
------------------ 原始邮件 ------------------
发件人: "bugman"notifications@github.com;
发送时间: 2019年6月17日(星期一) 晚上6:05
收件人: "hhyo/Archery"Archery@noreply.github.com;
抄送: "青春"578410927@qq.com;"Comment"comment@noreply.github.com;
主题: Re: [hhyo/Archery] [ SQL上线 ] (#160)
现在问题解决了嘛？
在 2019-06-14 11:37:36，"007mawenbin" notifications@github.com 写道：
进行SQL上线时出现如下报错：
所使用的数据库是其他主机的数据库。不是docker-compose的默认库
为啥我的这里选不了数据库，我是用docker安装的
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

repo: hhyo/Archery


text:
[ bug ]postgresql查询结果有json字符串的前端显示错误

在提交 issue 前，请查阅以下资源，请先进行搜索来保证没有类似的 issue。
文档 | FAQ
重现步骤
postgresql某表某字段为json字段，查询pg后端返回了正确的json数据结果，但前端展示异常
期待结果和实际结果
期待结果：
显示正确后端返回的json串
实际结果:

json串结果集后端返回正常，但前端显示均为  [object Object]
部署方式：手工部署
应用版本/分支：Release v1.8.0

pgsql json字段显示为[object Object]， 版本v1.8.5

pgsql json字段显示为[object Object]， 版本v1.11.3

source: gharchive/issue

authors: dmanbu liujing1087 moutianmouke

license_type: permissive

license_source: github-api


text:
HHH-18520 Upgrade to hibernate-models 0.9.0 + HHH-18521 Leverage hibernate-models ModelsConfiguration

https://hibernate.atlassian.net/browse/HHH-18520 Upgrade to hibernate-models 0.9.0
https://hibernate.atlassian.net/browse/HHH-18521 Leverage hibernate-models ModelsConfiguration
need to finish replacing the constructors for Annotations used by Jandex

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.

thanks @sebersole even if it's a draft but all suggestions/comments are really appreciated.

source: gharchive/pull-request

repo: hibernate/hibernate-orm


text:
HHH-9800 Numerous hibernate-infinispan tests continue to fail transiently

The original cause was JGRP-1931, this provides partial fix. However, timing issues with async replication cannot be solved completely.

Hmm, maybe I'll rethink this yet a bit. I could be better to use some kind of assertEventually.

Okay, I've rewritten that to an approach requiring less insight into the internal operations, and probably more reliable one.

Applied these changes to master for 5.0.0.CR2.  Thanks Radim!

authors: rvansa sebersole


text:
HSEARCH-2262 In the Elasticsearch mapping, validate the type of the null_value/indexNullAs property

https://hibernate.atlassian.net/browse/HSEARCH-2262
This currenly only works when running on JVMs with UTC timezone, and will fail miserably on JVMs with GMT+1 default timezone for instance. Either we fix HSEARCH-2335 and this PR will work as is, or we decide not to, and this PR will need some work. Fixed, see comments.

This isn't waiting on any other open PR right?

@Sanne This currently doesn't work, as explained in the first comment. It's not waiting on a PR alright, but it's waiting on HSEARCH-2335, which hasn't been fixed yet and must be fixed before merging.

ok. Do you plan to take HSEARCH-2335 ?

Well, it's basically a behavior change that fixes some bugs, but will
introduce ascending compatibility issues... Which is why I didn't address
it right away. Maybe you can give your opinion on that one? I think it
should be addressed, but someone else may think it's invalid ("works as
expected")...
If it's deemed valid, of course I can take it as soon as I'm done with the
VALIDATE/schema export stuff on Elasticsearch.
Yoann Rodière yrodiere@redhat.com
Software Engineer
Red Hat / Hibernate NoORM Team
On 20 September 2016 at 18:14, Sanne Grinovero notifications@github.com
wrote:

ok. Do you plan to take HSEARCH-2335 ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/hibernate/hibernate-search/pull/1151#issuecomment-248351344,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAZMzitvLrNBLCd3Si34GK8iAGgsgDYaks5qsAZzgaJpZM4JuSLR
.

See the discussion in https://hibernate.atlassian.net/browse/HSEARCH-2335: I was wrong. I will fix the tests so that they don't rely on the local timezone anymore, and will tackle https://hibernate.atlassian.net/browse/HSEARCH-2355 later.

The tests have been fixed. Ready for review!

Nice one, merging. The only thing which got me a bit confused is the usage of test Suite to make the two tests :)

merged

authors: Sanne yrodiere

repo: hibernate/hibernate-search


text:
ticketのis usedプロパティをstatusに

した

#91

close #91

仕様は #91 のこちらを参照

repo: hibiya-itchief/quaint-api

license: MIT


text:
无法使用!pic 创建图像

我接入了bing ai，可以用!bing 命令，尽管仍然有一些问题。
!pic 不可用，后台日志显示：
UnboundLocalError: cannot access local variable 'image_path' where it is not associated with a value
cannot access local variable 'image_path' where it is not associated with a value
Traceback (most recent call last):
  File "/app/bot.py", line 541, in pic
    await send_room_image(self.client, room_id, image_path)

有了，原来要带一个bing_auth_cookie参数


text:
🛑 kiwifarms.st is down

In 9faec13, kiwifarms.st (https://kiwifarms.st) was down:

HTTP code: 503
Response time: 1074 ms

Resolved: kiwifarms.st is back up in c721ce8 after 51 minutes.

repo: hickoryhouse/kf


text:
短縮URL発行機能へのスタイル適用の準備

ふんわりと構想してみたいのでとりあえずmergeお願いしたいです🙇

@yume-yu js/common.jsにロールバック箇所が見受けられます。昨日深夜に更新されたリファクタ分を含む範囲が本プルリクには未反映のようです。
マージを保留しますので、一旦 hidao80:masterからマージを試みてはいただけないでしょうか？🙏

なるほど。
ブランチ操作的にはfeature-developにmasterをマージ、その後にdesign-developにfeature-developをマージって感じがいいんでしょうか。

authors: KEINOS hidao80 yume-yu


text:
🛑 GitServer (Gitea) is down

In 50e0800, GitServer (Gitea) (https://git.yukineko.me) was down:

HTTP code: 0
Response time: 0 ms

Resolved: GitServer (Gitea) is back up in bb48097.


text:
Bug

Hey. I followed step by step the youtube video. And it started normally. But after I wanted to try the example find sentence or now a custom sentence there comes this error up.

If you need any more things just let me know! :)
I hope you wirte back soon

Try This: Work For Me (:
Add This Code: process.env.NODE_TLS_REJECT_UNAUTHORIZED = '0';
into line no 2 in src/utils/fetchPageContent.ts file
(Sorry For Bad English)

hey I tried that and it worked for me. After 3 or 4 succesfull minutes. Capitain Stack doesn't find results anymore.

This is the only error for me atm

Did You Run npm install ?

yep

I even re installed the whole thing

and again the same issue

Sorry, Idk About This Error

Hey @Gianiboy2265.
It's Typescript errors. Different versions of Typescript might have different errors as well.
Can you ignore the errors and start debugging?

yes I can

I just wondered bc when I first started the co-pilot the error wasn't there

When you install the dependencies, it'll download the latest vscode-dts automatically. It includes the definition for vscode module. The VSCode editor will start to read the type definition and through those errors.
Since the type definition for vscode-dts changes quite frequently (because Captain Stack uses an experimental API), updating code to fix those type errors will be outdated in a matter of weeks.
I'll close this thread since seems like the issue is resolved.

Duplicated of #45 and #48

Duplicate of #45 and #48

Duplicate of #45


text:
Workaround on Visual Mode motion in Mac

Not the best solution, but it's an attempt to fix somehow the visual mode motion on Mac. I was having a lot of issues using command V, it was selecting multiple lines at same time and when you tried to revert the last undesired line selected it was returning to the beginning of the block selected. Also the h and l was not working with v.

Are you sure this is a problem with Mac specifically and not with mixed line endings? Weird things happen if the project setting for EOL is different from the source file.

I double check my solution settings and it match with the source code. If you look at source code of CaretMoveActions you will see that if you are selecting in the Top-Down direction with V command and if you call CaretMoveActions.Up it will revert the selection to MainSelection.MinLine - 1 that means the beginning of the block and it only happens on Mac.
For example, if you are on line 10 and hit the following keys, V, Down/J, Down/J, Down/J, Up/K you would expect to have the lines 10 to 12 selected, but you will end up having lines 9 to 10.
This is only an example, it actually don't happen because CaretMoveActions.Down is messed up the same way CaretMoveActions.Up is, so when you hit Down/J key it will select more than one line at same time.
I tested it with version 0.10, btw

Thanks, I can't test it but I believe you.

authors: hifi marrony

repo: hifi/monodevelop-justenoughvi

license: mit

license_source: bigquery


text:
(Swift) Incorrect highlighting floating-point literals

The regular expression for matching numbers doesn't seem to handle exponents properly. For example, 1e-10 is a valid floating-point literal, but only the 10 highlights as a number.
I'm not entirely familiar with your regex syntax, but my guess is that this part: [\\d_]+(\\.[\\deE_]+)? means "one or more digits, followed by an optional part containing a decimal point and one or more digits or the letter e".  If that's correct, that  would explain why 12.1e12 does highlight correctly.
There may be a few more issues with this regex:

Does it handle negative exponents?
It seems to allow multiple letters e/E mixed in with the decimals. There should be only one e/E between the base and the exponent.

For reference, here is the grammar on floating-point literals:
https://docs.swift.org/swift-book/ReferenceManual/LexicalStructure.html#ID416

I'm not entirely familiar with your regex syntax

It's not "our syntax" per se...  It's just JavaScript's RegExp support... but I think it's generally standard-ish as far as RegEx goes... at least all the common things.

Yeah, this looks doable. And thanks for the ping!

Thank you for fixing this!

authors: gibson042 joshgoebel svanimpe


text:
Replace use of lexemes with $pattern, update version of highlight.js used in testing

Per @joshgoebel's request, this PR replaces the uses of lexemes with keywords.$pattern (and updates the version of highlight.js used in testing so that this will actually work).
...except, it doesn't work.  One of the tests checks that the tx in id$tx is not recognized as a builtin, because dollar signs are legal in Solidity identifiers.  But on this PR, this test fails.  It worked fine with lexemes... am I doing something wrong here?
I'll leave this PR up for now even though it's failing, in the hopes that maybe I can get some advice about how to fix this.

Please show the results of the failing test?

I mean, you can click through and see the results of the failing test yourself, but they'll be less than enlightening unless you know just what they're testing.  The nub of the issue is what I described above.  If you attempt to highlight "id$tx", you should get back "id$tx"; this was the case previously.  But with this PR currently, you get "id$tx".  That is to say, "tx" as recognized as a built-in.  However, it shouldn't be recognized as a builtin because it's part of the lexeme "id$tx", the dollar sign being legal in identifiers in Solidity.

Oh sorry, not used to people having tests.

Either you've missed a spot somewhere (nothing jumps at me) or there is possibly a regression between 9 and 10.  I'd suggest you start stripping away rules and complexity until you get it working.  If you get down to the bare foundation (ruling out the fact that it's some other  issue with the grammar itself) and it's still broken then you can pass it back to me and I can go digging further.
Or if you find "hey with works if this but not this" then again I might be able to take another look.  If there is a very low-level bug it might be simpler to jut delete your whole grammar and write the simplest grammar possible that might reproduce the issue.

Good idea, I'll try that, thanks!

Hm, OK, I tried to reproduce this with a simpler example and the problem didn't occur there.  I guess I'll have to do a bit more work to track down what's going on here.

If we're closing this could you please add a mention to your README that your grammar is not compatible with version 11?

Oh, sure thing.  I closed this because I was going to redo it from scratch, but yeah, I should add that note in the meantime regardless.

authors: haltman-at joshgoebel

repo: highlightjs/highlightjs-solidity

license: WTFPL


text:
Loaded model from file does not consider its action space continuous: error when running in LunarLanderContinuous-v2 environment

I train a model with PPO2 on the LunarLanderContinuous-v2 environment, then save it to a file.
Then I load the file, just like in the example, and run it again with the same environment to render the process, again just like in the example.
But an error occurs which indicates that the loaded/inferred model has as an attribute self.continuous=False or similar.
The equivalent process works just fine without error if env_name='LunarLander-v2'.
MWE of bug:
import gym

from stable_baselines.common.policies import MlpPolicy
from stable_baselines.common.vec_env import DummyVecEnv
from stable_baselines import PPO2

env_name = 'LunarLanderContinuous-v2'
policy = MlpPolicy
rl_alg = PPO2
rl_name = 'ppo2'

env = gym.make(env_name)
env = DummyVecEnv([lambda:env])

model = rl_alg.load(rl_name+"_"+env_name)

obs = env.reset()
while True:
    action, _states = model.predict(obs)
    obs, rewards, dones, info = env.step(action)
    env.render()

Stack trace:
WARN: gym.spaces.Box autodetected dtype as <class 'numpy.float32'>. Please provide explicit dtype.
WARN: gym.spaces.Box autodetected dtype as <class 'numpy.float32'>. Please provide explicit dtype.
Loading a model without an environment, this model cannot be trained until it has a valid environment.

---------------------------------------------------------------------------
AssertionError                            Traceback (most recent call last)
<ipython-input-3-e900d1547adb> in <module>()
     12 while True:
     13     action, _states = model.predict(obs)
---> 14     obs, rewards, dones, info = env.step(action)
     15     env.render()

/usr/local/lib/python3.5/dist-packages/stable_baselines/common/vec_env/base_vec_env.py in step(self, actions)
     92         """
     93         self.step_async(actions)
---> 94         return self.step_wait()
     95
     96     def get_images(self):

/usr/local/lib/python3.5/dist-packages/stable_baselines/common/vec_env/dummy_vec_env.py in step_wait(self)
     45         for env_idx in range(self.num_envs):
     46             obs, self.buf_rews[env_idx], self.buf_dones[env_idx], self.buf_infos[env_idx] =\
---> 47                 self.envs[env_idx].step(self.actions[env_idx])
     48             if self.buf_dones[env_idx]:
     49                 obs = self.envs[env_idx].reset()

/usr/local/lib/python3.5/dist-packages/gym/wrappers/time_limit.py in step(self, action)
     29     def step(self, action):
     30         assert self._episode_started_at is not None, "Cannot call env.step() before calling reset()"
---> 31         observation, reward, done, info = self.env.step(action)
     32         self._elapsed_steps += 1
     33

/usr/local/lib/python3.5/dist-packages/gym/envs/box2d/lunar_lander.py in step(self, action)
    236
    237     def step(self, action):
--> 238         assert self.action_space.contains(action), "%r (%s) invalid " % (action,type(action))
    239
    240         # Engines

AssertionError: array([0.87050533, 1.862139  ], dtype=float32) (<class 'numpy.ndarray'>) invalid

System Info
Model was trained/saved on Python 3.6 and loaded on Python 3.5
Library was installed via pip install stable-baselines
Trained on GPU, loaded and run on CPU only
All packages are up-to-date except I must run Tensorflow 1.5.0
Additional context
The model was trained and saved on a Google Compute Engine instance and run locally on an old Thinkpad laptop.

Hello,
The problem is that you don't clip the action. Cf Documentation:
https://stable-baselines.readthedocs.io/en/master/modules/policies.html

For all algorithms (except DDPG), continuous actions are only clipped during training (to avoid out of bound error). However, you have to manually clip the action when using the predict() method.

An easy solution to your problem is to upgrade your gym version, as they added clipping in LunarLanderContinuous recently ;) (see commit https://github.com/openai/gym/commit/d1146303b070a463e9e81086a0aeff7a2c909311#diff-41ce3ee7821ddd711130ac102a355dec)
(I assume your gym version is <= 0.10.5)

Great, thanks for the detailed answer! For some reason, it seemed like installing stable-baselines from pip encouraged gym 0.10.5 as a dependency. Upgrading gym resolved the issue.

The thing is that gym broke backward compatility with their new version for Multidiscrete action space, making stable baselines tests fails. That s why version 0.10.5 is the one recommended (but in your case, that does not matter)

authors: araffin lukasmericle

repo: hill-a/stable-baselines


text:
🛑 Pastebin is down

In 338dd6d, Pastebin (https://paste.hinzwifi.xyz/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Pastebin is back up in 16fa3cf after 16 minutes.

repo: hinzwifi/uptime-hinz


text:
freshness command doesn't work

maybe ./cmd/root.go is wrong. Because it would read config file in func init().
❯ tblmonit freshness ./tblmonit.toml
Failed to read Config File  Config File ".tblmonit" Not Found in "[/Users/ryo.kitagawa]"

I'm sorry, I made a mistake. But, this is a bit misleading...
I'll make PR that explain the config file.

repo: hirosassa/tblmonit


text:
feat: allow config path to be configured via env var

Description
The default config path can now be specified via env var.
Fixes #58
Example
The CONFIG_PATH environment variable can optionally be passed when starting the devnet API:
CONFIG_PATH="./path/to/Config.toml" stacks-devnet-api

If the variable isn't passed, or if resolving the variable yields an error, a default path of "./Config.toml" is used.

Checklist

[x] All tests pass
[ ] Tests added in this PR (if applicable)

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

authors: MicaiahReid blockstack-devops

repo: hirosystems/stacks-devnet-api


text:
Ordinal inscription addresses should be taproot addresses

The UI for testnet and the images from recent work being done (like PR https://github.com/hirosystems/stacks-wallet-web/pull/3198) all show bc1q or tb1q addresses which are native segwit and not taproot addresses.

Yes this was fixed in a later version of PR3198, thanks for being sharp. Looks good in current production version.

repo: hirosystems/stacks-wallet-web


text:
feat: detect chainID by default for testnet networks in tx builder functions

This PR was published to npm with the version 6.16.1
e.g. npm install @stacks/common@6.16.1 --save-exact

Updates the transaction builder functions to make them lookup the network chain_id by default when constructing txs for a custom testnet network. Behavior for mainnet and for primary testnet is unchanged.
Non-breaking
If the /v2/info request fails, e.g. when constructing a tx either offline or without expecting the network RPC to be available, then by default it will fallback to using the chainID already specified in the network object (which is typically either the default primary testnet chainID, or a user-specified chainID).

Closing as not-needed for now. Can reopen if this comes up again.


text:
Bugfix: fix gussian copula segmentfault error

Description

Motivation and Context

How has this been tested?

Types of changes

[ ] Maintenance (no change in code, maintain the project's CI, docs, etc.)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

fix done

repo: hitsz-ids/synthetic-data-generator


text:
Issue while opening a box

Steps to Reproduce
It was working normally. As I was caching more data suddenly when I hot restart the app it failed to open the box. It has something to do with encryption I think here is the log
Code sample
E/flutter ( 5490): [ERROR:flutter/lib/ui/ui_dart_state.cc(186)] Unhandled Exception: HiveError: This should not happen. Please open an issue on GitHub.
E/flutter ( 5490): #0      BinaryReaderImpl.readFrame
package:hive/…/binary/binary_reader_impl.dart:250
E/flutter ( 5490): #1      _KeyReader.readKeys
package:hive/…/io/frame_io_helper.dart:73
E/flutter ( 5490): <asynchronous suspension>
E/flutter ( 5490): #2      FrameIoHelper.keysFromFile
package:hive/…/io/frame_io_helper.dart:32
E/flutter ( 5490): <asynchronous suspension>
E/flutter ( 5490): #3      StorageBackendVm.initialize
package:hive/…/vm/storage_backend_vm.dart:88
E/flutter ( 5490): <asynchronous suspension>
E/flutter ( 5490): #4      HiveImpl._openBox
package:hive/src/hive_impl.dart:116
E/flutter ( 5490): <asynchronous suspension>
E/flutter ( 5490): #5      HiveImpl.openLazyBox
package:hive/src/hive_impl.dart:162
E/flutter ( 5490): <asynchronous suspension>

Version

Platform: Android-emulator Pixel 2, Mac-M1,
Flutter version: [2.0.6]
Hive version: [2.0.4]
Hive Flutter version [1.1.0]

Maybe it is another problem, but I was not able open box created in version 1.x.x with Hive 2.x.x

I have the same issue and I am not using encryption, but when I hot restart the app this happens. If I uninstall the app and reinstall then the issue stops until I hot restart some point again

This issue only seems to happen in Emulators and debug mode and can easily be fixed by clearing data or reinstalling

authors: cimplesid malaschitz nayefradwi

repo: hivedb/hive


text:
如何将data/self_cognition.json中设置、为自定义的具体值?

Reminder

[X] I have read the README and searched the existing issues.

Reproduction
CUDA_VISIBLE_DEVICES=0 python src/train_bash.py
--stage sft
--do_train
--model_name_or_path xxxx
--dataset self_cognition
--template default
--finetuning_type lora
--lora_target q_proj,v_proj
--output_dir path_to_sft_checkpoint
--overwrite_cache
--per_device_train_batch_size 4
--gradient_accumulation_steps 4
--lr_scheduler_type cosine
--logging_steps 10
--save_steps 1000
--learning_rate 5e-5
--num_train_epochs 3.0
--plot_loss
--fp16
Expected behavior
No response
System Info
No response
Others
如何将data/self_cognition.json中设置、为自定义的具体值?例如：将文档中的所有、：
{
"instruction": "你好",
"input": "",
"output": "您好，我是 ，一个由  开发的 AI 助手，很高兴认识您。请问我能为您做些什么？"
},
统一变成NAME为xxx，AUTHOR为yyy.是否再某个文件中可以定义实现自定义配置？

直接全部替换即可

记事本

authors: Songjiadong hiyouga mizzlefeng

repo: hiyouga/LLaMA-Factory


text:
训练已经成功,但是导出时提示包依赖错误

Reminder

[X] I have read the README and searched the existing issues.

System Info

llamafactory version: 0.9.1.dev0
Platform: Windows-11-10.0.22631-SP0
Python version: 3.12.4
PyTorch version: 2.4.1+cu124 (GPU)
Transformers version: 4.42.4
Datasets version: 2.21.0
Accelerate version: 0.34.2
PEFT version: 0.12.0
TRL version: 0.9.6
GPU type: NVIDIA GeForce RTX 4070 Ti SUPER

Reproduction
无,webui直接点击
Expected behavior
训练已经完成,点击导出提示报错.
Others

训练已经完成,点击导出时提示错误

PS C:\Users\benla> pip install auto_gptq>=0.5.0
WARNING: Ignoring invalid distribution ~ip (C:\Python312\Lib\site-packages)
Collecting auto_gptq>=0.5.0
  Downloading auto_gptq-0.7.1.tar.gz (126 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... error
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [1 lines of output]
      Building cuda extension requires PyTorch (>=1.13.0) being installed, please install PyTorch first: No module named 'torch'
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

由于我的环境不能使用默认,所以我安装了

点击WebUI的导出时报错

然而我按照控制台提示安装auto-gptq时提示

你尝试用命令行手动导出看看

尝试执行命令
llamafactory-cli export     --model_name_or_path ./models/Qwen2.5-7B-Instruct     --adapter_name_or_path ./saves/Qwen2.5-7B/lora/train_2024-10-11-16-38-17      --template Qwen2.5     --finetuning_type lora     --export_dir megred-model-path     --export_size 2     --export_device cpu     --export_legacy_format False

报错如下:
[WARNING|logging.py:313] 2024-10-12 09:42:38,581 >> Special tokens have been added in the vocabulary, make sure the associated word embeddings are fine-tuned or trained.
10/12/2024 09:42:38 - WARNING - llamafactory.model.loader - Processor was not found: 'Qwen2Config' object has no attribute 'vision_config'.
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "C:\Python312\Scripts\llamafactory-cli.exe\__main__.py", line 7, in <module>
  File "E:\llama-factory\LLaMA-Factory\src\llamafactory\cli.py", line 87, in main
    export_model()
  File "E:\llama-factory\LLaMA-Factory\src\llamafactory\train\tuner.py", line 75, in export_model
    get_template_and_fix_tokenizer(tokenizer, data_args)
  File "E:\llama-factory\LLaMA-Factory\src\llamafactory\data\template.py", line 368, in get_template_and_fix_tokenizer
    raise ValueError("Template {} does not exist.".format(data_args.template))
ValueError: Template Qwen2.5 does not exist.

authors: BenLampson codemayq


text:
Adding more songs(James Bond, Star Wars Imperial March, Morse Code SOS)

I added a few more songs.

Thanks for your contribution, feel free to add more sounds

authors: doriel hjdesigner

repo: hjdesigner/vibration-api


text:
🛑 LM Bogen WSV is down

In d321969, LM Bogen WSV (https://www.lmbogenwsv.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: LM Bogen WSV is back up in 7a6fbfa after 17 minutes.

repo: hjstrauss/MonitorMySites


text:
🛑 Griffo is down

In 851cfcc, Griffo (https://www.griffo.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Griffo is back up in 13d71dc after 15 minutes.


text:
🛑 Reime ohne Sinn und Verstand is down

In ec62b09, Reime ohne Sinn und Verstand (https://www.reimeohnesinnundverstand.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Reime ohne Sinn und Verstand is back up in dc91187 after 8 minutes.


text:
🛑 LM Bogen WSV is down

In 7fcdfb1, LM Bogen WSV (https://www.lmbogenwsv.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: LM Bogen WSV is back up in d867984 after 20 minutes.


text:
🛑 Opa Hansi is down

In 682aa72, Opa Hansi (https://www.opahansi.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Opa Hansi is back up in 0b6371d after 7 minutes.


text:
🛑 HJStrauss is down

In 2c77e11, HJStrauss (https://www.hjstrauss.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: HJStrauss is back up in aa0fb53 after 9 minutes.


text:
DGCNN accuracy

Hi,
I have a question about running dgcnn. I ran the code in scanobjectnn/dgcnn/train.py with the default parameters, and the eval accuracy I got stabilized to 0.792. But I see that in the paper (https://hkust-vgd.github.io/scanobjectnn/) the overall accuracy is 0.781, while bga-dgcnn is 0.797. So I am wondering if train.py is running the naive dgcnn, or it is actually running bga-dgcnn?

log_train.txt

Hi,
There was no random seed set during training, so there would be some variance in the results. We just ran the model for a fixed number of epochs and took the last checkpoint. Probably, could have done a more thorough evaluation on this. Please also use the evaluation script to evaluate the performance.

repo: hkust-vgd/scanobjectnn


text:
Keybindings help pop-up does not show up anymore

What did you expect to happen?
After pushing SPC, a pop-up shows up with a list of available key combinations.
What actually happened?
Nothing shoes up. Pushing ? brings up keybinding general help.
Additional details:
I don't exactly know which commit brought this about. But this was working across all my machines one week ago.

It is worth mentioning that I also get the following on start:
Error in pre-command-hook (doom-first-input-hook-h): (user-error "Helm-mode enabled (Ido-everywhere is incompatible with Helm-mode, disabling it)")
Steps to reproduce:

Push SPC

System information:

emacs   version    26.3
        features   XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND GPM DBUS GSETTINGS GLIB NOTIFY ACL GNUTLS LIBXML2 FREETYPE M17N_FLT LIBOTF XFT ZLIB TOOLKIT_SCROLL_BARS GTK3 X11 XDBE XIM MODULES THREADS LIBSYSTEMD LCMS2
        build      Aug 29, 2019
        buildopts  (--prefix=/usr --sysconfdir=/etc --libexecdir=/usr/lib --localstatedir=/var --with-x-toolkit=gtk3 --with-xft --with-modules 'CFLAGS=-march=x86-64 -mtune=generic -O2 -pipe -fno-plt' CPPFLAGS=-D_FORTIFY_SOURCE=2 LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now)
        windowsys  x
        daemonp    server-running
doom    version    2.0.9
        build      grafted, HEAD -> develop, origin/develop, origin/HEAD 4c61f22 2020-05-20 04:46:37 -0400
        dir        ~/.doom.d/
system  type       gnu/linux
        config     x86_64-pc-linux-gnu
        shell      /usr/bin/zsh
        uname      Linux 5.6.11-1-MANJARO #1 SMP PREEMPT Wed May 6 10:20:32 UTC 2020 x86_64
        path       (~/.pyenv/shims ~/.local/bin /usr/local/bin /usr/bin /bin /usr/local/sbin /usr/lib/jvm/default/bin /usr/bin/site_perl /usr/bin/vendor_perl /usr/bin/core_perl /usr/lib/emacs/26.3/x86_64-pc-linux-gnu/)
config  envfile    envvar-file
        elc-files  0
        modules    (:completion (company +auto +childframe) helm ido ivy :ui doom doom-dashboard hl-todo modeline nav-flash ophints (popup +all +defaults) tabs treemacs vc-gutter vi-tilde-fringe window-select workspaces :editor (evil +everywhere) file-templates fold format multiple-cursors rotate-text snippets :emacs dired electric ibuffer undo vc :checkers syntax spell grammar :tools ansible (docker +lsp) (eval +overlay) lookup lsp magit make pdf rgb :lang data emacs-lisp (javascript +lsp) markdown org perl php (python +pyenv +lsp) (rust +lsp) sh (web +lsp) :config (default +bindings +smartparens))
        packages   ((flycheck) (py-autopep8) (blacken) (pip-requirements) (python-pytest) (python-pylint) (direnv) (yasnippet) (arduino-mode) (docker) (dockerfile-mode) (docker-compose-mode) (ob-http) (ng2-mode) (prettier-js) (outshine))
        unpin      (n/a)
        elpa       (n/a)

Sorry guys. I should have taken the error more seriously. It turned out that I had helm and ido enabled together and this was causing the issue. Removing ido from init solved the issue.

repo: hlissner/doom-emacs


text:
Too hard to see what's being selected when using ivy

This was the issue I was having on discord in the help-nondoom channel
@gagbo
What happened?
When using ivy, the current selection is too hard to see. The background blends in with the minibuffer so it's impossible to tell what you are currently selecting.
What did you expect to happen?
Either some underline/different background color to indicate what your current selection is.
Steps to reproduce

Install the ivy package.
Run something like counsel-M-x or any function that uses ivy completion.
Try navigating up and down the list of selections.

System Information

Emacs version: 28.0.50
Emacs distro: Doom Emacs
Operating system: Ubuntu 20.04
Installed commit of doom-themes: 9e2680b
Which theme are you using: doom-acario-light

The purple "company-mode" option is not the current selection. On my monitor, that screenshot doesn't appear to be selecting anything but that's not to say that others won't be able to see the selection. This might just be a me issue.
My work around was to just add an underline to the ivy-current-match face which works fine.
(after! ivy
  (set-face-attribute 'ivy-current-match nil :underline t))

Similar issue with doom-dracula in terminal using vertico. When switching to e.g. doom-one and back again the current selection face suddenly has a darker background and so becomes distinguishable. However, that seems more like a bug of not resetting faces properly.

I'm not sure it's the same as doom-dracula and doom-one as you suggest. The contrast between the light blue background of the selected candidate and the yellow-ish default background is just terrible. I should look into fixing that

In vertico with opera-light there is the opposite problem: the description has a similar color of the highlighted background, and so it's not readable:

authors: DPDmancul gagbo myme nobellium1997

repo: hlissner/emacs-doom-themes


text:
CTA Button with Ceros Modal IFrame

Implement CTA Button with Ceros Modal IFrame.
Related to #66.
Example:
View Interactive Demo button from https://www.moleculardevices.com/products/microplate-readers/multi-mode-readers/spectramax-id3-id5-readers

Fixed by https://github.com/hlxsites/moleculardevices/pull/578

repo: hlxsites/moleculardevices