text:
Delete old transactions in transaction log state store

Background
Split from:

https://github.com/gchq/sleeper/issues/1713

Related to:

https://github.com/gchq/sleeper/issues/2453

Description
We'd like to delete old transactions that will no longer be read. This should keep the number of transactions DynamoDB needs to manage relatively low when serving requests to bring state stores up to date.
Analysis
We can identify any transactions that will never be needed by queries to bring a state store up to date, and delete them from the log. This can include any transaction that is a certain number of transactions behind the latest snapshot, and/or that was created a certain amount of time before the latest snapshot. We could make those thresholds configurable.
We could create a lambda to do this on a schedule.

Finished, closing.

repo: gchq/sleeper


text:
iCloud3 v3.0.5.5 (7/16/2024) Released

Change Log - v3.0.5.5 (7/16/2024)

ICLOUD3 FAILED TO LOAD (Fix) - iCloud3 injected special code into the HA history recorder to exclude various sensor entities from being added to the history recorder database. This caused problems with HA in the 2024.7 release.  The HA 2024.7.2 included special code that blocked iCloud3 from loading. A temporary patch was posted on the iCloud3 GitHub repository to disable the recorder injection.
This update fixes this problem. Only sensor attributes  related to the battery, distance and timer sensors are now being added to the HA recorder history. Sensors that are predominantly text based (info sensors, the Event Log sensor, badge, tracking update times, zone, etc.) are not being added. The state value of all sensors are added.
NOTE: The sensor state and attribute values are available on a real time base like they always have. This update only relates to the HA history recorder database.
SPECIAL NOTE: If you get an HA error that a sensor attribute is not available, create an issue on the iCloud3 GitHub repository. Let me know the sensor name and attribute name that is causing the error. I will remove it from the exclusion list in the next update.

Important Links:
Migrating from v2.4.7_ - See here for instructions on migrating from from an older version.
Installing for the first time_ - See here for instructions on installing as a New Installation
iCloud3 v3 Documentation - iCloud3 User Guide can be found here

Just updated, after restart icloud 3 again fails to start. Could it be that you missed to increase the version number in the manifest?
I had manually added that to 3.0.5.3, after your update it was set back to 3.0.5.2.

HACS was the problem. It was downloading the v3.0.5.2 release, not the v3.0.5.5 release even though the zip file for the release was correct and the files were correct. I will create a new release and see what happens.
Here is the v3.0.5.5 zip file.
icloud3.zip

It was my error. I did everything except update the custom_components/icloud3 code files on the GitHub repository so it was picking up v3.0.5.2 code instead.
All is good now. HACS updates the files  with the v3.0.5.5 version after refreshing via the Update Information option.

@gcobb321 one question. When the new version is installed will it still blocked in 2024.7.2 or not?

No. It will load and run without any issues.

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
vue-firestore featured on Alligator.io

I thought it would be nice to add a link to it in the readme.

@mornir thank you so much for this awesome contribution, we really appreciate it!!

source: gharchive/pull-request

authors: amranidev mornir

repo: gdg-tangier/vue-firestore

license: mit

license_source: bigquery


text:
Contact page improvement

Related Issue
[Feature] Improve contact-us card #64
Proposed Changes

Added contact page
Modified some home page default text.

Checklist

[ ✓] Documentation of the code
[✓ ] Added name to CONTRIBUTORS file
[✓ ] Tested in local machine
[✓ ] Following the same color scheme

Screenshots

Hey @jobs-code, this is SPA so no need to make new contact.html and why have you added the map? By improvement we meant that you design this

will update the same.

repo: gdsc-aec-india/gdsc-aec-web


text:
Ring boolean

(accidentally pushed to main, here is the real PR)
New component that can carve out some layers in the ring_coupler, for instance to define point couplers with heaters.
Originally:
    c = coupler_ring(         cross_section="strip_heater_metal",         length_x=0,         bend=gf.components.bend_circular,     )

New component:
   d = coupler_ring_point(c, open_layers=("HEATER",), open_sizes=((5, 7),))

So now we can make DRC-clean point coupler heater rings:
Current behaviour has a short :(
c = ring_double_heater(
        length_x=0,
        port_orientation=90,
        bend=gf.components.bend_circular,
        via_stack_offset=(2, 0),
        coupler_ring=coupler_ring
    )
    c.show(show_ports=True)

With new open layers:
    c = ring_double_heater(
        length_x=0,
        port_orientation=90,
        bend=gf.components.bend_circular,
        via_stack_offset=(2, 0),
        coupler_ring_top=coupler_ring,
        coupler_ring=gf.partial(
            coupler_ring_point,
            coupler_ring=coupler_ring,
            open_layers=("HEATER",),
            open_sizes=((5, 7),),
        ),
    )
    c.show(show_ports=True)

Thank you Simon!

authors: joamatab simbilod

repo: gdsfactory/gdsfactory


text:
挺好用的，但是有点小问题

程序是可以同步更新ip到指定的域名，但是调用godaddy 成功后 是没有任何信息的，然后你的程序就认为是同步失败，因为我没有设置接口调用成功的字符串
如果用户未填写任何调用成功的信息，应该认为如果没有任何信息，那么就是同步成功

貌似有不小的问题，测试过程中，当服务所在的机器IP发生变化时，30秒后并没有去指定的dns服务商同步 新的ip，只有当手动点击 修改，然后保存才会去做这个同步操作，

好的,收到,过几天会加上,这两天在重构ddns部分内容所以不会太快加上

n

OK，刚才那个PR，可以在前端加个说明：如果不写，就认为接口无信息返回即为成功
有的服务商接口调用成功就是没有信息，没信息就表示成功

加个开关,如果不禁用成功调用字符串检测的同时用户又不填写字符串的话会弹出提示.
禁用检测后就仅以StatusCode== http.StatusOK 作为接口成功调用的判断.
另外有时间的话麻烦把godaddy 的参数模版发一份给我,我添加进前端模版里面?

好的 我可以试试
---原始邮件---
发件人: @.>
发送时间: 2022年8月7日(周日) 中午11:16
收件人: @.>;
抄送: @.@.>;
主题: Re: [gdy666/lucky] 挺好用的，但是有点小问题 (Issue #3)
加个开关,如果不禁用成功调用字符串检测的同时用户又不填写字符串的话会弹出提示.
禁用检测后就仅以StatusCode== http.StatusOK 作为接口成功调用的判断.
另外有时间的话麻烦把godaddy 的参数模版发一份给我,我添加进前端模版里面?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

不急,我还没同步代码上github,这两天ddns部分重构优化的东西有点多,还没完成...

ok  第一次参与项目  😂，不规范的地方请严厉指出
---原始邮件---
发件人: @.>
发送时间: 2022年8月7日(周日) 中午11:31
收件人: @.>;
抄送: @.@.>;
主题: Re: [gdy666/lucky] 挺好用的，但是有点小问题 (Issue #3)
不急,我还没同步代码上github,这两天ddns部分重构优化的东西有点多,还没完成...
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


text:
Dashboard login jump failed

I checkout gearpump-0.7.6 and running sbt clean +assembly +packArchiveZip  to building a released package and  then I startup the Gearpump service in Local Mode . Using bin/local to start cluster and bin/services to start Web Service . But when I open http://127.0.0.1:8090 in browser try to login it (the username and password is default , admin:admin ) , it could't jump to cluster page and stay in login page . I think maybe something wrong but I can't found anything in log .

@darionyaphet
Have you tried using the chrome developer tool to record the network traffic?

Please post any errors of browser's console

@clockfly @stanleyxu2005 thank you for you help ~
I open chrome's developer tool and found a 401 Error
POST http://127.0.0.1:8090/logout 401 (Unauthorized)  jquery.js:9172
l.cors.b.crossDomain.send @ jquery.js:9172
n.extend.ajax @ jquery.js:8653
n.(anonymous function) @ jquery.js:8804
logout @ login.js:37
(anonymous function) @ login.js:42
i @ jquery.js:3182
j.fireWith @ jquery.js:3312
n.extend.ready @ jquery.js:3531
J @ jquery.js:3547

I'm not sure login is really needed . Maybe we can display a default page to show basic cluster status and make user login when want to submit a new job .

@darionyaphet You can deploy a cluster with login feature disabled. The switch is in config file.

Yes set authentication-enabled  to false will skip login module :+1:

@darionyaphet do you think we could close this?
It seems simplification of login is being addressed in https://github.com/gearpump/gearpump/issues/2021 ...

It seem have found the problem   I will close it :)

authors: clockfly darionyaphet karol-brejna-i stanleyxu2005

repo: gearpump/gearpump


text:
微信红包 4.0 Release Notes

更新推荐

新增 多语言支持，目前支持中文和英文两种语言
新增 适配部分Android 7.0机型（进行中，华为等部分机型仍不可用）

所有更新

新年快乐！
新增 多语言支持，目前支持中文和英文两种语言
新增 适配部分Android 7.0机型（进行中，华为等部分机型仍不可用）
优化 UI
优化 性能改进
修复 Uber与滴滴合并后优惠链接失效的问题
修复 Bugly高优先级的问题
移除 自动回复功能

立即下载
站内下载：https://github.com/geeeeeeeeek/WeChatLuckyMoney/releases/latest
国内分流：http://fir.im/luck （每天有下载限额）
项目推荐
git-recipes，高质量的Git中文教程，汇集了国外社区的优秀文章和个人实践。
electronic-wechat，Mac OS X和Linux下更好用的微信客户端。更多功能，更少bug。支持阻止撤回、群聊@，带来了更现代的界面和更丰富的功能。

今年是我第一次用这个插件，感觉非常好用，谢谢开发者。#划掉#连版本升级都要卖萌，我要报警了！#划掉#

7.0依旧无法打开拆字

authors: geeeeeeeeek lizhangqu wtlusvm

repo: geeeeeeeeek/WeChatLuckyMoney


text:
scripts/build-win32.bat needs electron version(1.1.0 -> 1.4.8) update

Description
scripts/build-win32.bat needs update
--version=1.1.0 may fail,  and --version=1.4.8 works.
Specifications

Version of Electron (run $ electron --version): v1.4.0
OS: Windows
Stack trace from the error message (if any)

set PLATFORM=%1%
set ARCH=%2%
set APP_NAME="Electronic WeChat"

set ignore_list="dist|scripts|\.idea|.*\.md|.*\.yml|node_modules/nodejieba"

electron-packager . "%APP_NAME%" --platform=%PLATFORM% --arch=%ARCH% --version=**1.4.8**  --app-version=1.3.0 --asar --icon=assets\icon.png --overwrite --out=.\dist --ignore=%ignore_list%

Updated in the master branch, not yet in the production branch

authors: Kulbear cooka

repo: geeeeeeeeek/electronic-wechat


text:
Run o1 with MetaGPT, cannot produce any output.

Bug description

When running o1, with examples/build_customized_multi_agents.py, no output is shown in the terminal. But o1 is indeed being used and charged.
logs does have the o1 output as 'DEBUG', it is just not shown in the terminal
If switch to gpt4, everything is working.

Environment information
o1 and o1 mini both have the issue. No output in the terminal.

System version: Linux
MetaGPT version or branch: Latest metaGPT github repo installation as of today.

Please update your configuration as follows:
llm:
  api_type: 'openai'
  api_key: 'sk-...'
  model: 'o1-mini'
  use_system_prompt: false
  stream: false

Make sure use_system_prompt and stream are set to false.

authors: hohoCode shenchucheng

repo: geekan/MetaGPT


text:
mac.homebrew: Install mas apps from Brewfile over SSH does not work

I'd like to reopen https://github.com/geerlingguy/ansible-role-homebrew/issues/146 here, as the issue still exists.
I have a Brewfile with multiple mas apps in it. When I run the playbook over SSH, it fails:
TASK [geerlingguy.mac.homebrew : Install from Brewfile.] *******************************************************************************************************************************************************************************************************************************************************************
fatal: [ws547]: FAILED! => changed=true
  cmd:
  - /usr/local/bin/brew
  - bundle
  delta: '0:00:09.632515'
  end: '2022-04-01 15:18:18.952991'
  msg: non-zero return code
  rc: 1
  start: '2022-04-01 15:18:09.320476'
  stderr: 'Error: Unable to install Affinity Designer app. mas installation failed.'
  stderr_lines: <omitted>
  stdout:
(Lot of Brewfile content)
  stdout_lines: <omitted>

However, it works using ansible_connection=local therefor I'm using this workaround now:
- name: Set controller_host fact
  set_fact:
    controller_host: "{{lookup('pipe','hostname')}}"

- name: Switch to local connection if this is the device
  set_fact:
    ansible_connection: local
  when: ansible_hostname == controller_host

For me the whole MAS installation doesnt work when using ansible remotely on my M1 mac. It just stops at the task. Im logged in via GUI and have Xcode installed and uninstalled to check if it was user error. It just doesnt appear to install or it takes forever that way?

authors: KriegersBlog tuxpeople

repo: geerlingguy/ansible-collection-mac


text:
Allow arbitrary gitlab_rails key/values in gitlab.rb

With these changes, the added example gitlab_rails dictionary will set add the following settings to /etc/gitlab/gitlab.rb:
gitlab_rails['gitlab_email_from'] = "git@example.com"
gitlab_rails['backup_keep_time'] = "604800"

Other arbitrary keys/values are possible, too.

Instead of continuing to add multiple extra layers of key/value configuration (other PRs are asking for other configurable changes), I think I may instead treat this role's config file like I do apache/nginx vhost config in other roles—the default configurable parts will be ignored if a playbook chooses to use its own config file (instead of managing it through this role). Maybe a new variable like gitlab_use_managed_config.

See #16 - instead of making this role manage all aspects of GitLab config, I'll leave playbooks to their own devices if they want to configure things out of the norm/base set of config.

authors: geerlingguy robbwagoner

repo: geerlingguy/ansible-role-gitlab


text:
git clone [REPO] in post-provision script not working

Issue Type

Bug Report / Support Request

Your Environment
Vagrant 2.2.2
VirtualBox 5.2.22r126460
ansible 2.7.4
  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/home/panda/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/dist-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.15rc1 (default, Nov 12 2018, 14:31:15) [GCC 7.3.0]

Your OS

Linux (Linux Mint 19 Cinnamon)

Full console output
$ vagrant up
https://gist.github.com/BWPanda/088fa0f58eddcd5d1f99bdd27f20d36a
Summary
My 'websites.sh' script tries to clone a git repository into the VM, but nothing is there when I ssh into it...
The script firstly adds the 'vagrant' user to the 'www-data' group, then it changes the group of the '/var/www' dir to 'www-data' and adds write permission for the group. It then adds the key for the git repository to the SSH known_hosts file (to avoid the interactive prompt to do so), and finally clones the repository into '/var/www': sudo -u vagrant git clone [REPO_URL] (well, tries to).
When I run vagrant ssh (which takes me straight to '/var/www'), only the 'dashboard' directory is there, no repository directory (my 'html_dir.sh' script removes the '/var/www/html' dir).
I've tried debugging this, but am not really sure how to (e.g. even running echo "test" in the script doesn't show anything when I ssh into the VM, but I know it runs as the SETUP_COMPLETE_FILE (copied from the example script) is present in '/etc'). How do I know what the issue is and how to fix it?

I should mention that running the same git clone ... command after SSHing into the VM works fine...

@BWPanda - If you run the script from within the VM, does that work? E.g. call /vagrant/scripts/websites.sh (if it's in your vagrant shared directory—otherwise copy it somewhere in the VM, make it executable (chmod +x) then run it).

@geerlingguy No, it doesn't. I then worked out that the following, run from within the VM, works:
git clone [REPO]
While this doesn't:
sudo -u vagrant git clone [REPO]
That second line is what the script uses, as the script is run as the 'root' user, whereas I need it to be run by the 'vagrant' user.
That gives the following error:

Permission denied (publickey,keyboard-interactive).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.

I've created a new SSH key on my host machine, added its public key to the remote git repository, then updated my scripts to copy that key onto the VM. So it should have access...
Because I can clone the repo. normally in the VM, then I'm guessing the issue has to do with trying to do it as the 'vagrant' user. Any ideas on how to do that?

Fixed it. Had to name the SSH keys 'id_rsa(.pub)' (they had different names on my host) and change the owner & group to 'vagrant'. After that, cloning the git repo. as 'vagrant' user works from the script.

authors: BWPanda geerlingguy

repo: geerlingguy/drupal-vm


text:
Path ammend

I think the path inside the container needs to be drupal (like with your live example)

It depends on how you structure your project. The web root needs to be /var/www/drupalvm/drupal/web to be picked up by the default config. So it depends on whether your project directory has drupal/web, or is the drupal project directory directly...
I think in my initial testing, I was always testing by downloading Drupal VM, then running things inside the Drupal VM directory (which would then have a drupal/web directory).
Can you give a little more detail about how this tripped you up / your use case?

authors: geerlingguy kevinhowbrook


text:
Plugin disabled

See https://github.com/Enriath/external-plugins/issues/126 for more info

Fixed it in https://github.com/geheur/weapon-animation-replacer/commit/bcb58d4b344a1b76f38ccc809e6e825115e26c7a but didn't close the issue
Smh text

repo: geheur/weapon-animation-replacer


text:
Enhance documentation for ValidateAndMigrate

I open this issue to ask if you can enhance the documentation of the library regarding the fact that you need to insert
ignorePendingMigrations = true to Fly4sConfig when running ValidateAndMigrate as you do in tests
Otherwise you will encouter this error
Failed validation:
  - version: 0
  - path: .../V0__create_tables.sql
  - description: create tables
  - errorCode: RESOLVED_VERSIONED_MIGRATION_NOT_APPLIED
  - errorMessage: Detected resolved migration not applied to database: 0. To fix this error, either run migrate, or set -ignorePendingMigrations=true.

Thanks

Hi @benkio, I think you should have the same problem even using plain Flyway.
Actually validateAndMigrate just call flyway validate and if it succeeds calls migrate.
I suggest you have a look at the flyway documentation for this kind of issue.
https://flywaydb.org/documentation/usage/errorcodes/

authors: benkio geirolz


text:
.NET Core 5

Have you looked at switching to .NET Core 5? I sort of got halfway there just to get VS to cooperate with me.
It looks like it was pretty painless, except the Unit Tests need a bit more attention. Did you have any ideas for this? I don't even know if Xunit is still a thing in .NET Core 5?
This isn't necessarily needed, but it might be nice just to make the onboarding ramp as smooth as possible?

I have considered it, but as far as I could tell, it does require people to install the runtime if they don't have it yet, which makes the installation experience a bit less smooth. Right now, any reasonably new version of Windows will have the .NET framework 4.6 or later installed, which means pass-winmenu will work directly out of the box.
That said, I'm not opposed to the idea of upgrading at all, especially since it makes the development experience nicer, which I think is also valuable (more external contributions is a good thing, as far as I'm concerned). I'd say that as soon as .NET 5 has a reasonable installation base, I'm happy to switch to it.

Implemented in v1.14.

authors: colemickens geluk

repo: geluk/pass-winmenu


text:
memtests failing with panic: system.cpu6: read of 10ff86 (blk 10ff80) @ cycle 2000 returns 3c, expected 0

Describe the bug
The gem5 Daily tests are currently failing.
The SuiteUID:tests/gem5/memory/test.py:memtest-NULL-x86_64-opt test suite is failing with src/cpu/testers/memtest/memtest.cc:161: panic: system.cpu6: read of 10ff86 (blk 10ff80) @ cycle 2000 returns 3c, expected 0.
This same bug appears to be affecting the other memtest long tests in "tests/gem5/memory".
Affects version
At the time of writing it affects the develop branch. This report was based on revision f7ad8fe4350be7d4299b22d9030385e3f261c7d8.
To Reproduce
To run the test:
cd tests
./main.py run --length=long -j`nproc` -uid SuiteUID:tests/gem5/memory/test.py:memtest-NULL-x86_64-opt

To run the script directly (i.e., what the script calls):
# Build gem5.
scons build/NULL/gem5.opt -j12

# Run the memory test
./build/NULL/gem5.opt tests/gem5/memory/memtest-run.py

Terminal Output
src/cpu/testers/memtest/memtest.cc:161: panic: system.cpu6: read of 10ff86 (blk 10ff80) @ cycle 2000 returns 3c, expected 0

Host Operating System
Ubuntu 22.04
Host ISA
X86
Compiler used
GCC

Pretty sure this was introduced by #177. 4fd9d66c537671f0950687cac327c4513c9c8eed was the first "bad" commit in the bisect.
@vsoriap  Was the new atomic support in the MemTest tested with the classic caches? Should we disable this or did this expose a bug?
Also pinging @tiagormk and @giactra  who approved that change.
If atomics are known not to work in the classic caches, then we have two options:

Disable atomics in the tests/gem5/memory/memtest-run.py file
Set the default percent atomic to 0 in src/cpu/testers/memtest/MemTest.py

I would prefer (2).
If atomics are supposed to work in the classic caches... well, we have a bigger bug to track down. We should consider to (1) or (2) above to get tests passing and work on the bug in parallel.

Hi @powerjg,
I didn't test the changes with the classic caches. I assumed that classic caches supported atomic ops, as Full System emulation works correctly with recent Linux versions that include atomics. Anyways, I'm not an expert in classic caches.
I would also opt for setting percent atomic to 0 (Option 2) as the preferred solution.

Fixed by #477

authors: BobbyRBruce powerjg vsoriap


text:
demo 中 springboot 从2.7.0 改成 3.1.2

就会报 如下：

APPLICATION FAILED TO START

Description:
A component required a bean of type 'com.gearwenxin.client.BloomZ7BClient' that could not be found.
Action:
Consider defining a bean of type 'com.gearwenxin.client.BloomZ7BClient' in your configuration.
Process finished with exit code 130

没事了，需要添加如下，就成功了：
@ComponentScan(basePackages = {"com.gearwenxin","****"})

repo: gemingjia/gear-wenxinworkshop-starter


text:
SearchContentのUIにビジネスロジックが表出してしまっているのを修正したい

検索イベントをdebounceで頻度を少なくしているけど、これってビジネスロジックじゃない？
TextFieldStateをState hoistingでScreenModelへ持っていけば、このあたりの問題も解決するんじゃなかろうか
ただしそうすると、SearchTextFieldがScreenModelに依存することになるので、interfaceでScreenModelに依存しないようにしたほうがいいだろう
とりあえずState hoistingするだけやってみよう

debounceでテキストの変更から一定時間経ったら検索をトリガーするのはビジネスロジックか？
UIロジックじゃないの？
TextFieldStateがいろいろ機能を持ちすぎてる気がするのが問題な気もするなあ・・・
State hoistingをやってみているが、今の状態のほうが適切な気もする・・・
ScreenModelで直接rememberTextFieldState()は呼べない（Composable関数内でしか呼べない）
（ただこれは、ViewModelでも同じことなのでVoyagerの問題というわけではないが）
それにState hoistingすることによって、次の2つを成立させるのが難しくなる

テキストが変更されて一定時間経ったらたらトリガーする
上記条件にかかわらずソフトキーボードで検索（Doneなど）が押されたら即座に検索する

現状でもこれはできていないが、ScreenModelで検索文字列を保持して、その文字が同じであればSkipするようにすれば解決できる

ViewModelに持っていくなら直接コンストラクタを呼び出すのでいいのか・・・
https://www.droidcon.com/2023/11/21/basictextfield2-a-textfield-of-dreams-1-2/

ViewModelに持っていく場合、複数の状態を公開するようになってしまう（というかそれが前提みたいな書き方な気がする）
VoyagerはStateが1つだけなので、ScreenModelのStateとしてはtextFieldStateを公開できない
ただ直接参照すればいいだけだが・・・

ビジネスロジックかUIロジックかなんてことを議論したいんじゃなくて（というかどっちになるか正解はないように思う）、UIにロジックがあるのが気持ち悪いから修正しようよが始まりだったように思う
ただでさえUIのためのスタイルでComposable関数は読みづらいのに、そこにロジックが交じると余計にカオスになっていくと思う
ifによる状態によって表示・非表示が変わる程度ならいいが、今回問題にしてる検索処理を走らせるトリガーなんかはScreenModel（ViewModel）でやったほうが合理的かなあと思う


text:
synthesis audio are different.

Hi, @geneing , thanks for your repo.
I found a weird phenomenon.
The model would generate audio during training,
Then I used the same checkpoint to synthesis audio.
I try to compare them (using same checkpoint and test mel file)
The audio which synthesis by loading checkpoint sounds bad than the audio which are saving at training time. The voice volume are smaller and background noise are increase in the audio which synthesis by loading checkpoint.

@fann1993814 That's odd.
Are you using synthesize.py for synthesis, or are you using the C++ library (e.g. using WaveRNNVocoder module)?
synthesize.py uses the same code as train.py. The one possible difference is that synthesize calls model.train(False), which may affect some layers. Could you comment out that line and try again?

Hi, @geneing
I also use both synthesize method. (c++ infer & torch infer)
And I already  comment out model.train(False),
But those audios, which synthesis by loading checkpoint, still sound worse.
(The dataset's sample rate is 22K)
My synthesize code is below:
vocoder=WaveRNNVocoder.Vocoder()

#model.bin is converted by checkpoint_step000800000.pth
vocoder.loadWeights('model_outputs/model.bin')

fname = 'test_0_mel.npy'

mel = np.load(fname)
mel = mel.astype('float32')

mel0 = mel.copy()
start = time.time()
wav = vocoder.melToWav(mel0)
print(time.time() - start)

librosa.output.write_wav('test_orig.wav', wav, 22050)

device = 'cuda'
latest_checkpoint = 'checkpoints/checkpoint_step000800000.pth'
model = build_model().to(device)
checkpoint = torch.load(latest_checkpoint, map_location=device)
model.load_state_dict(checkpoint["state_dict"])

mel1 = mel.copy()
start = time.time()
output = model.generate(mel1, batched=False)
print(time.time() - start)
librosa.output.write_wav('test_orig_torch.wav', wav, 22050)

In model_outputs directory, I added mel input file that matches the model.bin training parameters. The wav file is what I get back.
Since your dataset is 22050 Hz, have you adjusted the hparams file? In particular hop_size, win_size, sample_rate, upsample_factors, which are all related.

Yes, I already adjusted the hparams file.
num_mels=80,
fmin=125,
fmax=7600,
n_fft=1024,
hop_size=256,
win_size=1024,
sample_rate=22050,

upsample_factors=(4, 4, 16),

Hi, @geneing
I use preemphasize for training, and the problem is solved.
And I found the compile script "-ffast-math" would result in NaN error in C++.
The option may optimize some operation via reducing float precision. (I guess)
If canceling the option is not effect the inference speed. (It's my recommendation)

repo: geneing/WaveRNN-Pytorch


text:
NTR: vasodilation by nitric oxide

Dear Biocurators,
I am writing to request a new GO term, which arose whilst annotating paper PMID: 21768538 (Wu et al., 2011).
It is demonstrated in Figure 6 in this paper that miR-92a expression affects the regulation of vasodilation by nitric oxide.
Therefore, I wish to request the term:   ‘vasodilation by nitric oxide’
I am planning to subsequently request regulation terms via TermGenie in order to capture the effect of miR-92a on this process.
These terms would subsequently become siblings to terms such as (as well as others):
GO:0003121: regulation of vasodilation by epinephrine
GO:0003122: regulation of vasodilation by norepinephrine
GO:0003124: regulation of vasodilation by neuronal epinephrine
DbxREFs: GOC:BHF, GOC:BHF_miRNA, GOC:bc
I will look forward to hearing from you with regard to my request.
Thank you,
Barbara
cc: @RLovering
cc: @rachhuntley

Hi Barbara,
I’m afraid I have a couple of comments about this term too :-)
‘vasodilation’ is already a regulation term; it is a child of ‘regulation of blood vessel size’ and defined as “An increase in the internal diameter of blood vessels, especially arterioles or capillaries, usually resulting in a decrease in blood pressure.”. Therefore ‘vasodilation by nitric oxide’ would already capture the fact that the size of blood vessels is modified (increased = regulated) by nitric oxide. You wouldn’t need further regulation terms (and we wouldn’t want ‘regulation of regulation’ terms in the ontology). Unfortunately, I can see that the confusion may have arisen from the current existence of ‘regulation of vasodilation’ terms with several children. Some of them have a dbxref GOC:cardio so Ruth may remember something about them. I wasn’t around at the time, so I may have to check with other editors in case we need to edit the vasodilation branch - or in case I’m missing the point here…
Thanks,
Paola

@RLovering

Hi Paola,
Thank you for this overview.
Can I just confirm that this means that I only need to request 'vasodilation by nitric oxide', which would become is_a child term of 'vasodilation', which would be synonymous with ‘regulation of blood vessel size resulting in an increase in the internal diameter of blood vessels'?
But this also means that in order to make the annotation, which I intended, I also need to request the sibling term 'vasoconstriction by nitric oxide' (not to say 'negative regulation of vasodilation'!). However, I have just checked on Protein2GO and regulation terms for vasoconstriction are also abundant!
Thanks,
Barbara
@rachhuntley
@RLovering

Hi Barbara,
Given the confusion, I'd rather wait until I can clarify before adding terms or annotations. It seems we have a mix of terms under 'regulation of blood vessel size' - mostly old terms - my gut feeling is that we may have to edit the branch to better reflect the biology and current ontology procedures. I'll bring this up for discussion with my fellow editors and will keep you posted. Feel free to comment again if you don't hear from me within a few days.
Thanks,
Paola

Thanks, Paola!
Ok, I'll will look forward to hearing some news regarding this!
Barbara
@rachhuntley
@RLovering

Note for self -
'regulation of blood vessel size' sits directly under (is_a) 'biological regulation' -
it should be more specifically is_a 'regulation of biological quality'
and still NOT have regulation children

I just looked at this paper again and 'vasoconstriction by nitric oxide' would not actually be correct, because, based on Figure 6D, nitric oxide causes vasodilation.
But silencing of KLF2 by miR-92, which happens upstream, results in a decrease in the level of vasodilation:
miR-92a  ---|  KLF2  -->  eNOS  -->  nitric oxide synthesis  -->  vasodilation
@rachhuntley
@RLovering

Sounds like it may fit a LEGO model better than classical annotation...
(Barbara, not sure how familiar you are with LEGO, so my comment may be addressed to Ruth and Rachael instead.)

After discussing with Barbara, we think having synonyms of regulation of blood vessel size for vasodilation and vasoconstriction is confusing. What size is this referring to; length, width? It seems as if there should be an additional parent "regulation of blood vessel diameter".

Perhaps:
'regulation of blood vessel size' -> 'regulation of blood vessel diameter' as that seems to be the intention. Synonyms on vasodilation and vasoconstriction could be changed to fit.

At the editors call yesterday, we briefly went over the 'regulation of blood vessel size' branch. It was agreed that it needs a revamp. It won't be a quick fix I'm afraid. I will of course keep existing annotations into account. I'll start looking into this now and will post updates as I go. It might be more prudent for Barbara to hold onto annotating to these terms for the moment - they're confusing anyway!

Notes for self:

'reg. of blood vessel size' is indeed a descendant of 'reg. of biological quality', so that's ok
'reg. of blood vessel size' points to the OBA term 'blood vessel size', so I'll have to look into whether OBA has the more appropriate descendant of 'tube diameter' that I could use

Thank you for this update, Paola.
We have left all of the uncertain annotations from this paper (PMID:21768538) on hold.
@rachhuntley
@RLovering

Let’s start at the top - regulation of blood vessel size:
[Term]
id: GO:0050880
name: regulation of blood vessel size
namespace: biological_process
def: "Any process that modulates the size of blood vessels." [GOC:ai]
is_a: GO:0003018 ! vascular process in circulatory system
is_a: GO:0035150 ! regulation of tube size
intersection_of: GO:0065007 ! biological regulation
intersection_of: regulates OBA:0000032 ! blood vessel size
relationship: part_of GO:0008015 ! blood circulation
“size” is generic here - of course a generic tube may increase its size by becoming longer as well as wider, but blood vessels specifically become wider (vasodilation) or narrower (vasoconstriction), so we need to link to a diameter term here. It appears that OBA doesn’t have a specific term yet; the one we need is
OBA:NEW blood vessel diameter
is_a OBA:0000032 blood vessel size
is_a OBA:0000171 tube diameter
@cmungall , is there an OBA TG instance that I could use to request this? Otherwise could you please point me in the right direction.
We could then rename GO ’regulation of blood vessel size’ as ‘regulation of blood vessel diameter’, change the intersection to point to the new OBA term, and go from there. (We’d also need to redefine it and place it under GO:0035296 ’regulation of tube diameter’, whose def, btw, may do with some changes - currently “Ensuring that a tube is the correct width.”)
Thanks,
Paola

http://oba.termgenie.org/

Actually, I'd like to try a different route for OBA, using DOSDPs
This may be much more opaque at first, but we're improving it. Go to:
https://github.com/obophenotype/bio-attribute-ontology/blob/master/src/ontology/modules/entity_attribute.tsv
Edit the file, add a new line, use the next ID (+1 from previous line)

@cmungall , I confirm I have permission to access TG OBA (but I'll try to follow your other suggested route, as recommended). However, FYI, there are ~22 unsatisfiable classes, preventing TG OBA to function.

@cmungall done. Let's see how many attempts this will take :-)
Note the last line in the file was for OBA_0000110, but OBA IDs at the top of the file went as high as OBA_0000182, so I choose OBA_0000183 for my new term (this doesn't exist yet, as far as I can tell).

Hi @cmungall ,
Not sure if the OBA term made it. Anyway I requested it in imports_request.obo,
+relationship: needs OBA:0000183 ! blood vessel diameter
Thanks,
Paola

Hi @cmungall , any update on this please? :-)
@BarbaraCzub , FYI, I won't have a chance to work on this for a few days now, as I'll be on leave.
Thanks,
Paola

Hi Paola, thanks for the update on this.
Enjoy your leave and I'll wait to hear from you afterwards.
Thanks,
Barbara
@paolaroncaglia

Hi Paola,
I was not sure, as I was following the conversation, where your term requests were supposed to make it, but I just had a look on QuickGO and the vasodilation and vasoconstriction are now defined as 'an increase/decrease in the internal diameter...' whereas the previous definitions were ‘regulation of blood vessel size resulting in an increase/decrease in the internal diameter of blood vessels' (however, there is nothing in the change log about these definitions having being modified recently...). Anyhow, does this mean that regulation terms for both vasodilation and -constriction are now valid? And/or are you planning to make further changes to these terms/definitions?
Thank you,
Barbara
@RLovering
@rachhuntley
@dosumis

@paolaroncaglia

Hi Barbara (and @cmungall ),
As far as I can see, the term OBA:0000183 ! blood vessel diameter hasn’t been committed yet; the pull request at https://github.com/obophenotype/bio-attribute-ontology/pull/11 is still open. (Barbara, Chris was busy with grant submissions and traveling to meetings lately, hence - possibly - the delay.) Ideally, I would like to start editing this branch from the top down, so I’d like to wait for the OBA term to be available and then go from there to do the necessary GO edits.
As for definitions of vasodilation and vasoconstriction, I didn’t do any change in this branch, and I’m not aware that others did (as apparently confirmed by the change log). We editors are still of the opinion that current regulation terms for vasodilation and -constriction should not be valid. If you look at ‘regulation of blood vessel size’ and search for its children (http://www.ebi.ac.uk/QuickGO/GTerm?id=GO:0050880#term=children), you will see that both ‘vasodilation’ and ‘regulation of vasodilation’ are is_a children of the parent term - a good indicator that something is wrong. same for ‘vasoconstriction’ and its regulation. So yes, I am still planning to make changes in this ontology branch :-)
Thanks for your patience with this,
Paola

Hi Paola,
Thank you for the update and for clarifying the situation. I see what you mean about the continuing need to tidy up this branch! However, I would vote for including the regulation terms in the new restructured branch. If you look at the example, which I pasted in above (miR-92a ---| KLF2 --> eNOS --> nitric oxide synthesis --> vasodilation), when annotating the silencing of KLF2 by miR-92a, it would not be wrong to add the AE causally_upstream_of negative regulation of vasodilation, but it would be incorrect in this case to say causally_upstream_of vasoconstriction. But, as you suggested, perhaps to should be annotated using LEGO?
Thanks,
Barbara
@rachhuntley
@RLovering

Or perhaps...  AE part_of negative regulation of vasodilation?
Anyway, just a thought!
Barbara

Note for self - OBA term was committed a few hours ago. Next week I'll check if the term is available or if I have to add it again in imports_requests.obo.

Note for self: OBA:0000183 ! blood vessel diameter doesn't seem to be available yet, so I requested it again in imports_requests.obo - just now. Will need to check after 24 hours or so.

Dear Paola,
I hope you are well. Following a team discussion re: vasodilation and -constriction, we would like to emphasise that it is important to specify (within the definitions for these processes) that they involve the constriction and/or relaxation of smooth muscle cells. I.e. factors, which influence the vessel diameter, should be distinguished to make it clear that the changes in diameter do not occur e.g. due to proliferation of endothelial cells, which form the vessel. These aspects are not identified within the current vasodilation and -constriction definitions, which are 'A decrease in the diameter of blood vessels, especially arteries, usually causing an increase in blood pressure' and 'An increase in the internal diameter of blood vessels, especially arterioles or capillaries, usually resulting in a decrease in blood pressure.' respectively.
I hope you will find this helpful!
Kind Regards,
Barbara
@paolaroncaglia
@rachhuntley
@RLovering

Hi Barbara,
Thanks for the input - yes that will be very helpful in trying to disentangle this biological node.
I will keep it in mind.
Best,
Paola

Hi @cmungall
Sorry to bug you again, but I still can't see OBA:0000183 ! blood vessel diameter... could you advise please? :-)
Thanks,
Paola

Hello, I was wondering whether there has been any progress on this issue? Are there any conclusions to whether regulation terms for 'vasodilation' could be created, or is 'vasodilation' a regulation term in itself? Re: PMID:21768538, Figure 6.
Thanks,
Barbara

Hi @BarbaraCzub ,
This issue wasn't forgotten, I just haven't had a chance to address it yet. Thanks for the reminder. I'll look into it again soon and will keep you posted.

Thanks @paolaroncaglia

Started with adding GO:0097746 regulation of blood vessel diameter
(and with fixing the def of ‘regulation of tube diameter’). More work needed.

Thank you @paolaroncaglia
So it seems to me the annotation, which I will ultimately be making, will be 'regulation of blood vessel diameter by/in response to NO', rather than 'regulation of vasodilation by NO'. And, I admit, this will be much clearer.

More work: edited the ‘regulation of blood vessel size by renin-angiotensin’ node.

Edited and rehoused ’vasoconstriction’ and ‘vasodilation’ - just those two terms, not their regulation ones or their children; more work needed.

Hi @BarbaraCzub ,
I haven't examined the paper you wish to annotate, but if you'd like to use the new term GO:0097746 'regulation of blood vessel diameter', that's ready to use. You could add the information on NO as an extension.

Hi Paola
to be clear are you suggesting AE: part_of response to NO

Hi @RLovering ,
If the paper shows that the diameter of the blood vessels changes in response to NO, then yes, I'd suggest to annotate to 'regulation of blood vessel diameter' with an AE: part_of response to NO. Hope that helps.

Hm... I have just re-read this paper and I am not convinced that this is how I should capture this information.
Nitric oxide (NO) positively regulates blood vessel diamater (NAS), and there is experimental evidence in the paper in Figure 6, which shows that:

miR92a negatively regulates NO biosynthesis (which I had annotated)
miR92a negatively regulates blood vessel diamater
These effects are not direct, but depend on prior silencing of KLF2 by miR92a:

miR92a  --|  KLF2  -->  eNOS (NO synthase)  -->  vasodilation
So the annotations would be:
miR92a: negative regulation of blood vessel diameter
KLF2: positive regulation of blood vessel diameter
eNOS (NO synthase): positive regulation of blood vessel diameter
I will not include the AE: part_of response to NO, as the levels on NO depend on miR92a anyway.
Please let me know, if you disagree.
@paolaroncaglia I think I will wait until this branch has been tidied up as I need the positive and negative regulation terms, which atm exist as 'vasodilation' and 'vasoconstriction', for which regulation terms exist also...

Notes for self: I will approach the revamp of the vasodilation/vasoconstriction branch from the bottom up. To-do list:

[ ] for clarity, rename ‘vasodilation by acetylcholine involved in regulation of systemic arterial blood pressure’ as ‘acetylcholine-mediated vasodilation involved in regulation of systemic arterial blood pressure’ (as agreed on an editors’ call); keep old name as exact synonym;

[ ] similarly, rename ‘vasodilation by norepinephrine-epinephrine involved in regulation of systemic arterial blood pressure’ as ‘norepinephrine-epinephrine-mediated vasodilation involved in regulation of systemic arterial blood pressure’; keep old name as exact synonym;

[ ] rename ‘vasodilation of artery involved in baroreceptor response to increased systemic arterial blood pressure’ as ‘artery vasodilation involved in baroreceptor response to increased systemic arterial blood pressure’; keep old name as exact synonym;

Then, looking at ‘regulation of vasodilation’ and children/descendants:

[ ] rename ‘envenomation resulting in modulation of vasodilation in other organism’ as ‘envenomation resulting in vasodilation in other organism’ (1 annotation, correct under the new naming); keep old name as related synonym;

[ ] rename ‘modulation of vasodilation in other organism’ as ‘vasodilation in other organism’ (no annotations); keep old name as related synonym; move it under (is_a) ‘vasodilation’ and delete link with ‘regulation of vasodilation’;

[ ] merge ‘regulation of vasodilation by circulating epinephrine’ and ‘regulation of vasodilation by neuronal epinephrine’ (no annotations, no mappings, no inferences) into their parent ‘regulation of vasodilation by epinephrine’; make sure all resulting synonyms are related;

[ ] rename ‘regulation of vasodilation by epinephrine’ (no annotations) as ‘epinephrine-mediated vasodilation’; keep old name as related synonym; change synonym scope of ‘regulation of vasodilation by adrenaline’ from exact to related; place it under (is_a) ‘vasodilation’ and delete link to ‘regulation of vasodilation’;

[ ] merge ‘regulation of vasodilation by circulating norepinephrine’ and ‘regulation of vasodilation by neuronal norepinephrine’ (no annotations, no mappings, no inferences) into their parent ‘regulation of vasodilation by norepinephrine’; make sure all resulting synonyms are related;

[ ] rename ‘regulation of vasodilation by norepinephrine’ (no annotations) as ‘norepinephrine-mediated vasodilation’; keep old name as related synonym; change synonym scope of ‘regulation of vasodilation by noradrenaline’ from exact to related; place it under (is_a) ‘vasodilation’ and delete link to ‘regulation of vasodilation’;

[ ] the branch ‘regulation of relaxation of vascular smooth muscle’ is also problematic as ‘relaxation of vascular smooth muscle’ itself is_a ‘negative regulation of smooth muscle contraction’. Given that ‘regulation of relaxation of vascular smooth muscle’ and its pos. and neg. children have no annotations, I’d like to merge all 3 into ‘relaxation of vascular smooth muscle’ (making sure all resulting synonyms are related) and make the def. of ‘relaxation of vascular smooth muscle’ clearer by changing it to “A negative regulation of smooth muscle contraction resulting in relaxation of vascular smooth muscle. The relaxation is mediated…”;

[ ] create GO:NEW ‘positive regulation of blood vessel diameter’ (“Any process that increases the diameter of blood vessels.”) and place ‘vasodilation’ (“An increase in the internal diameter of blood vessels…”) under it (is_a) rather than under ‘regulation of blood vessel diameter’;

[ ] similarly, create GO:NEW ‘negative regulation of blood vessel diameter’ (“Any process that decreases the diameter of blood vessels.”) and place ‘vasoconstriction’ (“A decrease in the internal diameter of blood vessels…”) under it (is_a) rather than under ‘regulation of blood vessel diameter’;

(@BarbaraCzub, these are the new terms you need, so keep watching this space please, I will add the new GO IDs in a separate comment as soon as they’re ready.)
The list of to-do items below needs further examination:

[ ] look at exp. annotations of ‘negative regulation of vasodilation’ and suggest new homes for them, possibly ‘negative regulation of blood vessel diameter’; then eliminate term, possibly by merging it into ‘vasodilation’;

[ ] same for ‘positive regulation of vasodilation’;

[ ] then look at ‘regulation of vasodilation’; it should have no children left; look at its annotations (and InterPro mappings!) and suggest new homes for them; then eliminate term, possibly by merging it into ‘vasodilation’;

[ ] Then work on vasoconstriction.

Hi @paolaroncaglia , thank you for this update. I will look forward to these new GO terms becoming available.

Hi @BarbaraCzub , here are the new terms:
+id: GO:0097755
+name: positive regulation of blood vessel diameter
+id: GO:0097756
+name: negative regulation of blood vessel diameter

Thanks @paolaroncaglia

Following up on the strategy outlined above, I will:

[ ] Merge ‘negative regulation of vasodilation’ into ‘negative regulation of blood vessel diameter’.
FYI, my rationale for choosing to merge into ‘negative regulation of blood vessel diameter’ rather than ‘vasoconstriction’ is the following:
‘vasoconstriction’ specifically means constriction of smooth muscle cells that line the vessels;
I looked at a couple of annotations to ‘negative regulation of vasodilation’:

PMID:18671723 “naofen interferes with NO production” => upstream of dilation or constriction => negative regulation of blood vessel diameter;
PMID:24309216 “adenosine A1 antagonist DPCPX … failed to reduce vasodilatation induced by CGS21680” => not entirely clear, so safe to say upstream of dilation or constriction => negative regulation of blood vessel diameter.
‘negative regulation of vasodilation’ had 11 experimental annotations, they are in the attached table annotations_need_checking.xlsx. If curators wish to rehouse them under more specific terms, they’ll be given a chance to do so, see below.

[ ] Merge ‘positive regulation of vasodilation’ into ‘positive regulation of blood vessel diameter’.
Rationale for doing so is similar to the above and supported by looking at a couple of annotations (PMID:23826814 and PMID:23232926).
‘positive regulation of vasodilation’ had 55 experimental annotations, they are in the attached table annotations_need_checking.xlsx, see below;

[ ] Merge ‘regulation of vasodilation’ into ‘regulation of blood vessel diameter’.
Again this is backed up by looking at some annotations (PMID:17916776 and PMID:12730558).
‘regulation of vasodilation’ had 7 direct experimental annotations, they are in the attached table annotations_need_checking.xlsx, see below.

[ ] ‘regulation of vasodilation’ has 5 InterPro mappings. I’ll need to look at them and suggest changes.

[ ] Then work on vasoconstriction :-(

[ ] When the clean-up of this branch is complete, I’ll contact the relevant MODs to let them know of the changes and point them to the spreadsheet in case they wish to rehouse any of their annotations.

Thanks Paola this sounds right

annotations_need_checking.xlsx

@asangrador @almitchell @happy-lorna @ndrawlings @EBI-Hsinyu
Following changes of GO terms related to ‘vasodilation’, I merged GO:0042312 ‘regulation of vasodilation’ into ‘regulation of blood vessel diameter’. This affects InterPro because GO:0042312 ‘regulation of vasodilation’ has 5 InterPro mappings, which I suggest to move instead to GO:0042311 ‘vasodilation’. The mappings are:
IPR000147
IPR000332
IPR000356
IPR000670
IPR001483
Thanks in advance for looking into this.

Hi Paola
so for O35607 Bmpr2 which is annotated to GO:0045906 negative regulation of vasoconstriction this should be annotated with the GO term: negative regulation of blood vessel diameter.
but this doesn't imply whether the blood vessel diameter is smaller or larger as a result. How are we supposed to indicate this. The diameter size is an important aspect of human system, and neg reg of vasoconstriction does not mean vasodilation
Sorry for taking so long to appreciate this. I think this is why the terms were created despite the problem with negative negative.
Ruth

Hi @RLovering ,
I haven't fully revised the vasoconstriction branch yet, but I'll keep your comment above in mind. (Neg reg of vasoconstriction means that the diameter does not decrease, so it's certainly not the same as neg reg of diameter ;-) perhaps you meant 'reg. of diameter', but I will look into terms and annotations and formulate a plan, I do agree that these terms are problematic but hopefully annotation procedures will become clearer to us all if we focus on what the processes are and what it is that regulates them instead. Plus, LEGO is probably the best way forward here.)

@RLovering , @BarbaraCzub
Looking at the vasoconstriction branch highlights yet more work to do. At first sight, the areas in need of revision are not only the existing regulation terms, but also the link with ‘vascular smooth muscle contraction’ (currently is_a ‘vasoconstriction’). Quickly put: vasoconstriction refers to decrease in diameter of a whole blood vessel; the vessel is made of endothelial + muscle cells; ‘vascular smooth muscle contraction’ should be part_of ‘vasoconstriction’, not is_a. (And the reciprocal ‘vasoconstriction’ has_part ‘vascular smooth muscle contraction’ should be added, too.) (Note that ‘relaxation of vascular smooth muscle’ correctly is part_of ’vasodilation’ already.) Are there cases where vascular smooth muscle cells contract without causing vasoconstriction?
As for vasodilation, the vasoconstriction node contains many terms (though, luckily, only 57 manual experimental annotations) so revising everything is not a quick thing. I’ll have a word with David Hill. Thanks for your patience…

@RLovering , @BarbaraCzub, @rachhuntley
I discussed this ticket briefly with @ukemi. He has some thoughts about it, and agrees that it would be a really good case for LEGO. I'm handing it over to him so he can continue where I left, as I'm wrapping up my ontology tickets. Thanks.

Discussed with @RLovering
Decisions:

[x] Merge 'regulation of blood vessel size' and 'regulation of blood vessel diameter'
[x] Change label: GO:0097746 regulation of blood vessel diameter -> blood vessel diameter homeostasis
[x] Change label: GO:0002034 regulation of blood vessel diameter by renin-angiotensin ->     maintenance of blood vessel diameter homeostasis by renin-angiotensin

Obsolete:
GO:0097756 negative regulation of blood vessel diameter -> consider: vasoconstriction
GO:0097755 positive regulation of blood vessel diameter -> consider: vasodilation

Dear all,
The proposal has been made to obsolete
GO:0097756 negative regulation of blood vessel diameter -> consider: vasoconstriction: 16 EXP
GO:0097755 positive regulation of blood vessel diameter -> consider: vasodilation: 45 EXP
Contributor   (Assigned by)
AgBase | 7
MGI | 2
RGD | 43
UniProt | 9
There are no mappings; these terms are not in any subsets.
We are opening a comment period for this proposed obsoletion. Since there are many annotations to be reviewed, we’d like to proceed and obsolete this term on November 27th, 2020. Unless objections are received by November 27th, 2020, we will assume that you agree to this change. You can add comments to the ticket: https://github.com/geneontology/go-ontology/issues/12253
Thanks, Pascale

Fixed AgBase annotations.

Fixed UniProt annotations.

authors: BarbaraCzub RLovering cmungall dosumis paolaroncaglia pgaudet rachhuntley

repo: geneontology/go-ontology


text:
malate-aspartate shuttle parentage

Although it plays a crucial role in respiration malate-aspartate shuttle is not directly part of the electron transport chain (ETC)
parent should move up to
GO:0045333   cellular respiration

opinions, @sjm41 ?

More info. There are 3 children:

so it should apply to one or more of these.
GO:0022904  respiratory electron transport chain
Definition
A process in which a series of electron carriers operate together to transfer electrons from donors such as NADH and FADH2 to any of several different terminal electron acceptors to generate a transmembrane electrochemical gradient.
so I suppose it could fit, but most descriptions of the respiratory ETC  begin with mitochondrial NADH.
The problem I see is that in this case the citric acid cycle and other NADH providing systems could be included?

On a related note:
Could 'malate-aspartate shuttle' term become also a child of NADH oxidation?
The other pathway that does a similar reaction 'glycerolphosphate shuttle' (GO:0006127) is part of NADH oxidation.

That would definitely be correct, but I wonder if we plan to keep NADH oxidation (seems like a single-step process, so maybe should only be in molecular function @pgaudet ).
Anyway, I will add this parent for consistency.
Glycerophosphate shuttle should have some mitochondrial transport parent....

That would definitely be correct, but I wonder if we plan to keep NADH oxidation

Is NADH oxidation (or NAD reduction) ever annotated in isolation, or always as a part of a larger reaction (process) in which a second participant is reduced or oxidized?

These are the only direct EXP annotations to NADH oxidation:
UniProtKB:Q9JXV5	Fructose-1,6-bisphosphate aldolase		GO:0006116
UniProtKB:P0DOB5	ATP-dependent 6-phosphofructokinase		GO:0006116
UniProtKB:Q9ALA2	NAD(P) transhydrogenase subunit alpha		GO:0006116
UniProtKB:Q07637	Pyruvate kinase		GO:0006116
UniProtKB:P05062	Fructose-bisphosphate aldolase B		GO:0006116
UniProtKB:P08201	Nitrite reductase (NADH) large subunit		GO:0006116
MGI:MGI:95679	glycerol-3-phosphate dehydrogenase 1 (soluble)		GO:0006116
MGI:MGI:95679	glycerol-3-phosphate dehydrogenase 1 (soluble)		GO:0006127
RGD:621381	glycerol-3-phosphate dehydrogenase 1		GO:0006116
FB:FBgn0022160	Glycerophosphate oxidase 1		GO:0006127
FB:FBgn0001098	Glutamate dehydrogenase		GO:0006116
UniProtKB:P0DMQ6	Sorbitol dehydrogenase		GO:0006116
SGD:S000001417	Mitochondrial glycerol-3-phosphate dehydrogenase		GO:0006116
AGI_LocusCode:AT3G10370	SUGAR-DEPENDENT 6		GO:0006127
SGD:S000002243	Mitochondrial external NADH dehydrogenase		GO:0006116
SGD:S000002180	NAD-dependent glycerol-3-phosphate dehydrogenase		GO:0006116
RGD:1311112	phosphoenolpyruvate carboxykinase 2 (mitochondrial)		GO:0006116
RGD:1311112	phosphoenolpyruvate carboxykinase 2 (mitochondrial)		GO:0006116
RGD:2503	NAD(P)H quinone dehydrogenase 1		GO:0006116
SGD:S000000349	Alcohol dehydrogenase isoenzyme V		GO:0006116
SGD:S000004589	NADH:ubiquinone oxidoreductase		GO:0006116
SGD:S000004918	Glucose-repressible alcohol dehydrogenase II		GO:0006116
SGD:S000005446	Alcohol dehydrogenase		GO:0006116
SGD:S000005446	Alcohol dehydrogenase		GO:0006116
SGD:S000005446	Alcohol dehydrogenase		GO:0006116
SGD:S000005420	NAD-dependent glycerol 3-phosphate dehydrogenase		GO:0006116
SGD:S000004753	Mitochondrial external NADH dehydrogenase		GO:0006116
SGD:S000004688	Mitochondrial alcohol dehydrogenase isozyme III		GO:0006116

Hi @deustp01
In the wiki page you cite, 'NADH oxidation' is also described as 'NAD regeneration' (specifically, the authors write "Since the malate–aspartate shuttle regenerates NADH inside the mitochondrial matrix"). We also have a GO term for NADH regeneration; would that not be a more appropriate description of the biological purpose of the malate–aspartate shuttle?
Pascale

... would that not be a more appropriate description of the biological purpose of the malate–aspartate shuttle?

The way we used to explain the process to medical students is that, as a result of glycolysis NADH accumulates in the cytosol where it can't be used for much (mostly only NADPH can be be used for biosyntheses and there's no easy way to convert cytosolic NADH to NADPH) and meanwhile the pool of NAD+ needed for continued glycolysis is depleted. The shuttle transfers NADH to the mitochondrion where it can be fed into mitochondrial oxidative phosphorylation, yielding much useful energy, coupled to the restoration of cytosolic NAD+ via the molecular interconversions of the shuttle. So if it is regeneration of anything, it would be NAD+ regeneration, but if there is some sort of NAD(H) homoeostasis term, that would be a better fit to the idea that the whole process works to maintain appropriate levels of NAD and NADH in various cellular compartments. Sanity check, @sjm41

@sjm41 @rozaru did https://github.com/geneontology/go-ontology/issues/28982
make this ticket obsolete?
Do you agree that the matale aspartate shuttle supports the respiratory transport chain, but isn't part of it? of do you think the relationship should be part_of?

@sjm41 @rozaru did https://github.com/geneontology/go-ontology/issues/28982
make this ticket obsolete?

Yes, I believe so - I'll close this one.

Do you agree that the matale aspartate shuttle supports the respiratory transport chain, but isn't part of it?
Yes.


text:
terraform deployment

To add terraform deployment for AWS

Closing this issue as terraform deployment is redundant.

repo: genomicsengland/panelapp


text:
Include plugins in esbuildOptions

Add plugins option in esbuildOptions

Why do you need this? Ideally you would use a Vite plugin instead, since that would apply during dev and build.

Do they work during build? For example I have to move query engine files related to prisma to ./build/server/.

authors: geoffrich sukeshpabolu

repo: geoffrich/svelte-adapter-azure-swa


text:
Improvements

[ ] Replace broadcasting with MovementOps.EXPAND
[ ] Add Div to mlops
[ ] Add conv support for padding and dilation
[ ] Consider if we can add something to combine transpose and weight grad to reduce processing ops
[ ] MovementOps.FLIP?

FYI, if you don't mind getting a bit spicier in terms of memory safety, you can replace all of your movement ops with a strided view op:
E.g.;
view = lambda x, shape, strides, offset: \
  np.ndarray(buffer=x.data, shape=shape, strides=strides, offset=offset, dtype=x.dtype)
x = np.arange(3).reshape(-1,1)
y = np.random.rand(3, 4)

Expand/Broadcast: view(x, (3, 4), (8, 0), 0) == np.broadcast_to(x, (3, 4))
Flip: view(y, (3, 4), (-32, -8), 8 * 12 - 8) == np.flip(y)
Transpose: view(y, (4, 3), (8, 32), 0) == np.transpose(y)
Reshape: np.reshape(y, -1) == view(y, (12,), (8,), 0)
Slice: view(y, (4,), (8,), 8 * 4) == y[1], view(y, (3,), (32,), 8) == y[:, 1]
And many others

Notice that you don't actually need to launch a kernel to perform a view op like above; if your other kernels are stride aware you effectively "fuse" the data-movement into the preceding or following op.
Note that the stride tricks can run out when input arrays are no longer contiguous, and sometimes you will need to materialize the array with a copy.  However, with an efficient copy op (hint), this is still cheaper or equal to the runtime cost of doing the data-movement eagerly like you're doing now.
NumPy does these tricks internally, and torch does some of them (the ones that don't involve negative strides; they don't support that yet).

So I actually want to do it all without copies. Movement ops should all always be free, then there's a kernel to make contiguous (or stride aware kernels).
See my start here: https://github.com/geohot/tinygrad/pull/328
I understand that say, a permute followed by a reshape might traditionally require a copy, but I'll solve this by using "virtual dimensions". A real dimension can contain multiple virtual dimensions, and the virtual dimensions are what is actually used.

ShapeTracker works!

authors: geohot orausch

repo: geohot/tinygrad


text:
Drag end event

Hi,
Just started using this excellent library and everything is working as expected although I am having difficulty trapping the pm:markerdragend event. This is my code which otherwise works ok:
L.geoJSON(g, {
        onEachFeature: function (feature, layer) {

            layer.options.id = feature.properties.id

            layer.on("dblclick", function(e) {

                if (editingLayer == drawnLayer) {

                    if (this.pm.enabled()) {
                        this.pm.disable();
                        editing = false
                        console.log(this.options.id)
                    } else {
                        if (editing == false) {
                            this.pm.enable()
                            editing = true
                        }
                    }
                }

            })

            layer.on("pm:markerdragend", function(e) {
                this.pm.disable()
                console.log(this.options.id)
            })

        }

    })

Double-clicking on a marker enables and disables the editing but drag end doesn't. Could you suggest how I might improve this?

You need to use pm:dragend.
pm:markerdragend is for the vertex marker on a line

Excellent - thank you

authors: Falke-Design itcareerswitch

repo: geoman-io/leaflet-geoman


text:
Question: plans to drop dependencies 'flufl.enum' and 'pathlib' from requirements?

Description
I'm wondering if there are any plans to remove the flulf.enum and pathlib dependencies from the requirements for PyWPS. I've run into issues with installing PyWPS in conda environments using modern python version because of these libraries, which is odd since both of these libraries have been available in the standard library since version 3.4.
Is there a development branch for the PyWPS 4.3+ where Python2.7 and requirements not native to Python3 have been dropped from the requirements?
Environment

operating system: Linux
Python version: 3.7
PyWPS version: 4.2.3
source/distribution
[ ] git clone
[ ] Debian
[ ] PyPI
[ ] zip/tar.gz
[ ] other (please specify):
web server
[ ] Apache/mod_wsgi
[ ] CGI
[x] other (please specify): Anaconda (conda-forge)

Steps to Reproduce
Additional Information

Fixed by PR #520.

authors: Zeitsperre cehbrecht

repo: geopython/pywps


text:
Make the background colour configurable

For consistency, since everything else is now. Some people may not care for pastel blue.

When we do this, we should make sure to update layout-test - it's now hardcoded there as well.

repo: georgefst/monpad


text:
I got no rendered result running the run_viewer.py

I run python nerfstudio/scripts/viewer/run_viewer.py --load-config {outputs/.../config.yml} with the load-config correctly configured. On the webpage I get the training image and lidar points, but don't have the rendered vision, like this

What's wrong? I trained the model for 20000 iterations.

I got a bug on the viewer, fixed.

repo: georghess/neurad-studio


text:
Upload fails when using with python notebook

Steps to reproduce:

Checkout the tutorial branch or PR #161
Start EVA server and jupyter notebook on ada1.
Run the object_detection notebook (specifically the upload cell)
Cmd fails with the following error.
[Errno 13] Permission denied: '/tmp/test_video.mp4'

The permission denied error occurs when a user tries to overwrite a file created by another user in the /tmp directory. In this case, changing the file name should resolve the issue.

repo: georgia-tech-db/eva


text:
HELP: When running to 'cursor.fetch_all()', the eva_server output 'UnicodeDecodeError: 'utf-8' codec can't decode byte 0x80 in position 8: invalid start byte'

Can you list more detailed steps how to reproduce this issue? By just using this code snippet, I cannot reproduce your issue.

I used the main branch project. I installed version 0.0.10 of evadb in pip.
I started the "eva_server &" command from the command line, and then executed the code in the image.

The server will report this UnicodeDecodeError.
I use this code is aim to test the abi provided by server from a python project.
I run eva_cmd__client.py to start the client  will also report this error.
But I started eva_client in the command is smoothly. I'm confused.

next is the all packages in my environment:
absl-py==1.1.0
aiosignal==1.3.1
alembic==1.8.1
antlr4-python3-runtime==4.10
anyio==3.6.2
appdirs==1.4.4
astor==0.8.1
astunparse==1.6.3
async-timeout==3.0.1
attrs==22.1.0
autocfg==0.0.8
backcall==0.2.0
banal==1.0.6
black==22.6.0
blinker==1.4
brotlipy==0.7.0
cached-property
cachetools==4.2.4
certifi
cffi
chardet
charset-normalizer==2.0.12
click
colorama
cryptography
cycler==0.11.0
Cython==0.29.30
dataset==1.5.2
debugpy==1.6.4
decorator==5.1.1
dill==0.3.6
diskcache==5.4.0
distlib==0.3.6
django-commands==0.7
easyocr==1.5.0
entrypoints==0.4
evadb==0.0.10
facenet-pytorch==2.5.2
fastapi==0.87.0
fastjsonschema==2.16.2
filelock==3.8.0
flake8==3.9.1
flatbuffers==1.12
fonttools==4.33.3
frozenlist==1.3.3
fsspec==2022.10.0
funcsigs==1.0.2
future==0.18.2
gast==0.3.3
gluoncv==0.10.5.post0
google-auth==1.35.0
google-auth-oauthlib==0.4.6
google-pasta==0.2.0
graphviz==0.8.4
greenlet==1.1.3
grpcio==1.43.0
grpcio-tools==1.47.0
h11==0.14.0
h5py
idna==3.3
imageio==2.22.4
importlib-metadata
importlib-resources==5.10.0
iniconfig==1.1.1
ipykernel==6.16.2
ipython==7.34.0
ipywidgets==8.0.2
isort==5.10.1
jedi==0.18.1
joblib==1.1.0
jsonschema==4.17.1
jupyter_client==7.4.7
jupyter_core==4.12.0
jupyterlab-widgets==3.0.3
Keras-Applications==1.0.8
Keras-Preprocessing==1.1.2
kiwisolver==1.4.3
Mako==1.2.1
Markdown==3.3.7
MarkupSafe==2.1.1
matplotlib==3.5.1
matplotlib-inline==0.1.3
mccabe==0.6.1
mkl-fft==1.3.1
mkl-random==1.2.2
mkl-service==2.4.0
mock==4.0.3
msgpack==1.0.4
multidict
munkres==1.1.4
mxnet==1.9.1
mypy-extensions==0.4.3
nbclient==0.6.8
nbformat==5.7.0
nbmake==1.3.4
nest-asyncio==1.5.6
netron==5.9.1
networkx==2.6.3
nltk==3.7
numpy==1.21.6
nvidia-cublas-cu117==11.10.1.25
nvidia-cuda-runtime-cu117==11.7.60
nvidia-cudnn-cu116==8.4.0.27
nvidia-tensorrt==8.4.1.5
oauthlib==3.2.0
objgraph==3.5.0
onnx==1.12.0
opencv-python==4.5.5.64
opencv-python-headless==4.5.4.60
opt-einsum==3.3.0
packaging==21.3
pandas==1.3.5
parso==0.8.3
pathlib==1.0.1
pathspec==0.10.1
petastorm==0.11.5
pexpect==4.8.0
pickleshare==0.7.5
Pillow==9.0.1
pkgutil_resolve_name==1.3.10
platformdirs==2.5.2
pluggy==1.0.0
portalocker==2.5.1
prettytable==3.3.0
prompt-toolkit==3.0.30
protobuf==3.19.4
psutil==5.9.1
ptyprocess==0.7.0
py==1.11.0
py4j==0.10.9.5
pyarrow==10.0.0
pyasn1==0.4.8
pyasn1-modules==0.2.8
pycodestyle==2.7.0
pydantic==1.10.2
pyflakes==2.3.1
Pygments==2.12.0
PyMySQL==0.10.1
pyparsing==3.0.9
pyrsistent==0.19.2
pyspark==3.0.2
pytest==7.1.2
python-bidi==0.4.2
python-dateutil==2.8.2
python-multipart==0.0.5
pytools==2022.1.12
pytz==2022.1
PyWavelets==1.3.0
PyYAML==5.1
pyzmq==24.0.1
rarfile==4.0
ray==1.13.0
regex==2022.6.2
requests==2.27.1
requests-oauthlib==1.3.1
rsa==4.8
scikit-image==0.19.3
scipy==1.4.1
seaborn==0.11.2
Shapely==1.8.5.post1
six==1.16.0
sniffio==1.3.0
SQLAlchemy==1.3.20
SQLAlchemy-Utils==0.36.6
starlette==0.21.0
tensorboard==2.3.0
tensorboard-data-server==0.6.1
tensorboard-plugin-wit==1.7.0
tensorflow-estimator==2.3.0
tensorflow-gpu==2.3.1
termcolor==2.0.1
thop==0.1.1.post2207130030
tifffile==2021.11.2
tomli==2.0.1
torch==1.10.2
torchaudio==0.11.0+cu113
torchvision==0.11.3
tornado==6.2
tqdm==4.43.0
traitlets==5.3.0
typed-ast==1.5.4
typing_extensions==4.1.1
urllib3==1.26.9
uvicorn==0.20.0
virtualenv==20.17.0
wcwidth==0.2.5
Werkzeug==2.1.2
widgetsnbextension==4.0.3
wrapt==1.14.1
yacs==0.1.8
yarl
zipp==3.8.0

Thanks for sharing the details. Looks like a mismatch between the server and client versions.  Can you please try running the client script outside the eva directory so it uses the pip installed version?
Another alternative is to launch the server using python eva/eva_server.py.  This will use the server code from the master branch.

Yes, I also found the cause of this problem. Because my pip has installed eva, and there is a folder of eva on the master branch. Therefore, when importing packages, there is an error. Therefore, I suggest that the folder name on the main branch can not be called eva


text:
Implement std::fmt::Debug for gdal::Geometry

This will make it easier for users to inspect the contents of the geometry while developing.

Now implemented:
https://github.com/georust/gdal/blob/master/src/vector/geometry.rs#L341-L348
via
https://github.com/georust/gdal/commit/a1f880c895c3ec73019116568a7b0bfe4b82f73e

authors: frewsxcv metasim

repo: georust/gdal


text:
[WIP] Upgrade to serde 0.9

Howdy! This is a reactionary upgrade to serde 0.9. I say reactionary because all I've done is the least amount of work I can to make it build and pass tests.
There is one major wrinkle and I'm not sure how to progress it; serde_json::to_value() now returns a Result, and we're kind of assuming in the to_object methods that nothing will fail. You can see I'm calling expect(), which is basically how serde_json used to work, but doesn't now.
As the serde API drifts further away from rustc_serialize I think it's going to get harder to maintain the compatibility layer. How do you think we should move forward?
I'm thinking we could:

Keep the expect or similar and document when to_object() can panic
Or update to_object() to return a Result, that's always Ok with rustc_serialize

CC: @frewsxcv

I think it's clear Serde is the future of serialization in the Rust ecosystem. How do you feel about dropping support for rustc-serialize?

Personally I'm only using serde support so am totally on board with that. It would make the codebase simpler again. There could be some other users with different opinions though.

I appreciate your initial effort to support both, but I think we're good to remove rustc-serialize support.

Looks like you'll need to update the Travis config to stop testing 'with-serde'

Ah yes I'll update that :+1: I was going to do a bit of boyscouting too and clean up the serde uses and some docs.

authors: KodrAus frewsxcv

repo: georust/rust-geojson


text:
images in root directory

The image https://github.com/geoscixyz/em/blob/master/zteminv2d3d_section.png is currently sitting in the root directory. Could it please be moved to the relevant case history directory or removed if it is a duplicate?
cc @sgkang

@sgkang : would you mind taking a look at this when you get a chance? It should be a small update. Thanks!!

closed with #483

repo: geoscixyz/em


text:
Feature Request: Inherit Local Filename Extension from Training, Mask Images

The name '/tmp/mul.tif'  should probably be '/tmp/mul.{}'.format(extension) or something like that, so that it will be sure to work with VRTs.  The same for /tmp/mask.tif'.

VRTs seems to work without doing this.

repo: geotrellis/deeplab-nlcd


text:
🛑 k3s WeatherForecast is down

In 78daa64, k3s WeatherForecast (https://k3s.g11s.cc/WeatherForecast) was down:

HTTP code: 0
Response time: 0 ms

Resolved: k3s WeatherForecast is back up in 4a82d14.

repo: gerrited/upptime


text:
🛑 Hacker News is down

In e4ea2bb, Hacker News (https://news.ycombinator.com) was down:

HTTP code: 502
Response time: 295 ms

Resolved: Hacker News is back up in 30600fb after 12 minutes.


text:
Make open-channel tx fee configurable and don't hardcode other tx fee

We don't want to overspend when opening a channel but we need to be flexible when estimating tx fee for HTLCs, commit transactions etc.
The best way forward would be to have two different settings:

a configurable/low fee for channel opening
a dynamic fee for everything else

Related to #555

Adding additional settings is blocked by #642  (adding configurable settings PR).

I went for a fee threshold (a limit above which we will just refuse to create a channel on our node), that is configurable.
other tx fees are dynamic, as long as we can connect to esplora. if esplora has issues, we also have configurable fallbacks.

authors: bonomat klochowicz


text:
Jitsi in rocket does not work in 5.5

Bug description:

When opening a jitsi meet window from rocket.chat as a Ferdi service, the jitsi window fails to load with this messages:
Uncaught TypeError: Cannot read property '1' of null
    at Array.g (BrowserDetection.js:72)
    at S (BrowserDetection.js:144)
    at new y (BrowserDetection.js:187)
    at new a (BrowserCapabilities.js:20)
    at Object.<anonymous> (index.js:3)
    at n (bootstrap:19)
    at Object.<anonymous> (lib-jitsi-meet.min.js?v=4127:10)
    at Object.<anonymous> (lib-jitsi-meet.min.js?v=4127:10)
    at n (bootstrap:19)
    at Object.<anonymous> (statistics.js:1)
/opt/Ferdi/resources/app.asar/node_modules/electron-spellchecker/src/spell-check-handler.js:214 Uncaught Error: document.body is null, if you're calling this in a preload script you need to wrap it in a setTimeout
    at SpellCheckHandler.attachToInput (/opt/Ferdi/resources/app.asar/node_modules/electron-spellchecker/src/spell-check-handler.js:214)
    at /opt/Ferdi/resources/app.asar/webview/spellchecker.js:1
_.web.js:5 Uncaught ReferenceError: JitsiMeetJS is not defined
    at Module.<anonymous> (_.web.js:5)
    at n (bootstrap:19)
    at Object.<anonymous> (app.bundle.min.js?v=4127:1)
    at n (bootstrap:19)
    at Object.<anonymous> (app.bundle.min.js?v=4127:1)
    at n (bootstrap:19)
    at Object.<anonymous> (app.bundle.min.js?v=4127:1)
    at n (bootstrap:19)
    at Object.<anonymous> (app.bundle.min.js?v=4127:24)
    at n (bootstrap:19)

The code at the error point is the following:
/**
 * Detects Electron environment.
 *
 * @returns {Object|undefined} - The name (ELECTRON) and version.
 */
function _detectElectron() {
    const userAgent = navigator.userAgent;

    if (userAgent.match(/Electron/)) {
        const version = userAgent.match(/Electron\/([\d.]+)/)[1];

        return {
            name: ELECTRON,
            version
        };
    }
}

Steps to reproduce:

Go to a rocket.chat service
Click on the video call button, join the call
Check for the new window to load a jitsi call
No jitsi call, a gray window is seen (in dark mode)

Expected behavior

The window should load a jitsi call
Screenshots

Environment:

Operating System: Ubuntu 20.04
Ferdi Version: 5.5
Server: Ferdi with a franz account
Meet.jit.si verison: 4127

This worked fine in 5.4.3 before updating.

Updated rocket.chat to latest version 3.4.1 and it's still happening. This is what's shown in Ferdi's development console in the jitsi window.

Same issue Here.
Ferdi 5.5.0
Manjaro Linux

Sorry - we are not in a position to support Ferdi 5.5 - its REALLY old.  I would suggest that you try out the latest beta here or the even newer nightlies here.
We are very close to releasing the v5.6 - so these betas or nightlies are quite stable at this point.

authors: hugorn martinszy vraravam

repo: getferdi/ferdi


text:
Add "trigger" support to respond to non-command text

Fixes #117

A couple of nits but this LGTM!
This change is a really big deal. Feel free to merge at will sir!

A couple of nits but this LGTM!
This change is a really big deal. Feel free to merge at will sir!

authors: clockworksoul theothertomelliott

repo: getgort/gort


text:
feat: :sparkles: card row pattern

close #155

close #156

repo: getgoui/go-ui


text:
admin plugin breaks the site for this skeleton

The moment I install admin plugin site stops loading and admin I get the error

Not Found
The requested URL /grav/admin was not found on this server.

Without admin plugin the site loads just fine. With the plugin installed the url automatically appends admin and normal site URL is not even accessible.

This is not a bug, you simply don't have page rewrites working - http://learn.getgrav.org/troubleshooting/page-not-found

Thanks...yes you are right. I forgot to create the conf file specific to new folder and it was just using the default one.

authors: pubmania rhukster

repo: getgrav/grav-skeleton-onepage-site


text:
Site and Admin Error latest Grav Develop: Invalid argument supplied for foreach()

Just installed latest Grav Develop.
Site broken:

In admin, after I click on username:

Must have been one of the commits from 4/5 May (guess it's the Groups selection pre-filled in user form)

Thanks for reporting!

authors: axel-rank flaviocopes

repo: getgrav/grav


text:
After inserting contact-form modular page opens on form

Hi, I have created a site based on the Agency theme and I've added a contact-form by editing the home page.
But when I browse to the site (https://steyaert.be/marleen/) it opens on the contact form part instead of the top of the page.
I have fooled around with the params but I can't seem to find a solution to this.
This is the content of my homepage in the attached txt file.
home.txt

This is likely the issue: one of your form fields has autofocus: on, so the browser scrolls down.

Hero!
That was indeed the issue, thanks!

authors: DimitriSteyaert flaviocopes


text:
Support for stable Micropub extension 'Post Status'

Link to Micropub Extension 'Post Status'. Discussion on the extension can be found here. It is stable as of June 2020.
This would aid users in writing articles that are long form and are written over the course of several days, by letting them revisit the publish page and having them specify post-status=published whenever they're ready.

This has been implemented in the v0.1.x branch.
By default, for Jekyll and Hugo configs, Indiekit will use this value to output draft: true in the frontmatter if post-status=draft. This is the preferred value for Hugo. Jekyll recommends publishing to a special _drafts folder, which Indiekit does not support. While this behaviour might not be desirable for Jekyll, it may still be useful Jekyll-esque static site generators like Eleventy which can hide posts using this value.

authors: hirusi paulrobertlloyd

repo: getindiekit/indiekit


text:
[Question] TemplateTag plugin ordering

Insomnia Version: 6.3.2
Operating System: Windows 10 Pro x64 1809

Details
Hi,
Im writing a plugin for Insomnia to help with an API I'm testing.
Basically, we need to provide the same value multiple times in the request, and the value must be unique per request.
I'm using insomnia-plugin-faker to generate random numbers.
{
  "example": "{% faker 'random', '', '', '', '', '', '', '', '', '', '', '', '', 'number', '', '', 'en' %}",

Then elsewhere in the request, I use my plugin to get this value.
  "reference": "{% requestbodyjsonpath 'req_a71e53d53e1e4ebab20df69d4c95a779', '$.example' %}"
}

Unfortunately, this doesn't work as I need it to... It does seem to apply both plugins, but the values for example and reference are different. Which I assume means that my plugin is running first, replacing my tag with the faker tag. Then faker is running and replacing the faker tag with the random number.
e.g.
{
  "example": "123",
  "reference": "456"
}

Interestingly, if i change example to use an environment variable, then it just renders the environment variable tag.
e.g.
template:
{
  "example": "{{i}}",
  "reference": "{% requestbodyjsonpath 'req_a71e53d53e1e4ebab20df69d4c95a779', '$.example' %}"
}

rendered request:
{
  "example": "123",
  "reference": "{{i}}"
}

Is there an intended behaviour for this type of plugin?
Would it be possible to explicitly order plugins?
Would it be possible to run plugins after environment variable replacements? (Maybe this will break other plugins)
Should I look for '{{ }}' tags within my plugin and manually lookup environment variables?
Cheers,
Michael

I think you might be able to replace '$.example' with simply example and Nunjucks will include the variable for you. Can you see if that works?
I think there's also a render() method exposed to plugins so you could render the {% faker .... %} tag directly from inside your plugin, although that would be kind of a hack.

Thanks for the reply. I decided to just use environment variables for anything that needed to be shared.

authors: gschier tehmantra

repo: getinsomnia/insomnia


text:
Add versioning in CMake for shared library

Title: Add versioning in CMake for shared library
Description:
Hello,
I propose this change to enable building reflect-cpp with Yocto.
Issue:
Without this change, the following error occurs during the build process:
ERROR: reflect-cpp-0.16.0-r0 do_package_qa: QA Issue: -dev package reflect-cpp-dev contains non-symlink .so '/usr/lib/libreflectcpp.so' [dev-elf]
ERROR: reflect-cpp-0.16.0-r0 do_package_qa: Fatal QA errors were found, failing task.
ERROR: Logfile of failure stored in: /workdir/tmp/work/cortexa55-xware-linux/reflect-cpp/0.16.0/temp/log.do_package_qa.1139088
ERROR: Task (/workdir/layers/meta-xhello/recipes-core/reflect-cpp/reflect-cpp_0.16.0.bb:do_package_qa) failed with exit code '1'

Solution:
With this change, the package builds correctly with the proper SOVERSION. Yocto can locate the original .so file in the main package and create a symlink in the *-dev package.

@xbrtszstk , do you want to turn this into a Linux package?

@xbrtszstk , all right, merged.

repo: getml/reflect-cpp


text:
Instant tooltips

Moved from the v2022.3 release criteria:

On anything with title text, show our own popup with the text right away, rather than make people wait for the browser.

GitHub has done this forever, for example. It’s a big big usability win.

Focusing on a title-text element with keyboard navigation should ideally also pop the tip.
(Nice to have:) Today there are elements where if their text content overflows, we truncate the text with an ellipsis; we also add title text. The title text is added even if the text content does not actually end up overflowing: the title text is added if the text content might overflow. However, ideally we show an instant tooltip only if the text content actually overflows.

Tested wit Success!

Tested with Success!

I've filed an issue with design review feedback at #753. We didn't end up making those changes for .2, but we're planning to do so for .3.

authors: dbemke matthew-white srujner

repo: getodk/central-frontend


text:
Returning Record RC

Trying out build similar to #1383 (fix for #572).

[ ] Unit test all changes
[ ] Update README.md if applicable
[X] Add [WIP] to the pull request title if it's work in progress
[ ] Squash commits that aren't meaningful changes
[ ] Run sbt scalariformFormat test:scalariformFormat to make sure that the source files are formatted

@getquill/maintainers

Im sorry that I forgot to mention something important. The insert(entity).returning(_.id) API used to not only add id SQL RETURNING clause but also removed It from the Insert clause as well. After a few conversations with Flavio and others, we concluded that if we want to support returning tuples  etc.. in the returning clause eg .returning(r => (r.foo, r.bar)) it is very unclear that the behavior of returning is to exclude foo and bar from the initial insertion. Also, we wanted to have an API that does not exclude records at all. Therefore, we decided to make .returning do exactly that and .returningGenerated return generated columns I.e. columns that are auto-generated therefore should be excluded from the Insert.

The other thing that we realized was that whether a single column (MySQL, Sqlite etc...), multiple columns (Oracle) or multiple columns with an actual RETURNING clause that supports sql operations (Postgres) is supported has to be controlled by the idiom as opposed to the context. MirrorContext for instance has to generate RETURNING clauses for only Postgres but... allow multiple column tuples/case-classes for Oracle and allow only one return variable for other databases the same way in MirrorContext as well as JdbcContext. So the dialect has to control these things. Also,
we need to know all of this during compile time during. For the reason we introduced the RuturnCapability types. These live in the dialects but can be inspected from anything that has access to the context including the Parser, the Metas etc...

@deusaquilus Okay, now it's clear, great work! Except missing readme update, everything else lgtm.

authors: deusaquilus mosypov

repo: getquill/quill


text:
"SyntaxError: invalid syntax" when installing master via pip

When installing the latest master (89024b4) via pip (pip install -U git+https://github.com/getsentry/raven-python) on Python 2.7, I'm getting a "SyntaxError: invalid syntax" for the following line: https://github.com/getsentry/raven-python/blob/master/raven/transport/aiohttp.py#L30
Looks reasonable, the asterisk really doesn't look like Python (2.x) syntax, or am I missing something?

When compiling raven, I see the SyntaxError tagged above, but the exit code for "python -m compileall" is still 1.  Shouldn't the exit code be 0 if this were truly not an issue?  This only came up when I ran a deployment, and my tool pays attention to the exit codes.

This isn't an issue, and exists in any library that tries to be python 2 and python 3 compatible in the same codebase. Similarly, this happens to gunicorn as well. The only fix we could do is to remove the python 3 specific syntax from our codebase, but I don't really think that's reasonable.

Upgrading your pip version might solve the issue.
I just tested a Raven install with Python 2.7 and pip 7.0.3, didn't saw a warning.

@xordoquy The underlying problem is from python -m compileall, which people run across their projects outside of pip. pip happens to call this internally and just masks the output so it's not surfaced to the user. So anyone who runs python -m compileall explicitly would be seeing this, which is a bit awkward.

And to clarify, compileall is naive to all of this. It just generates pyc files for every python file in the source tree, it doesn't actually import modules or anything, so it doesn't understand that certain files aren't even accessed based on conditional imports, etc.

Right, I assumed the compilall was part of the installation process.

Yeah, it totally is. pip just masks those errors by literally using a regular expression to parse them out. :) It's kinda gross. But it's not an error by any means, just noise.

authors: hheimbuerger lkiss80 mattrobenolt xordoquy

repo: getsentry/raven-python


text:
[Question] Sourcemap Upload Help/Documentation

OS:

[ ]  Windows
[X]  MacOS
[ ]  Linux

Platform:

[X]  iOS
[ ]  Android

There doesn't seem to be any clear and concise steps to getting sourcemap output automatically uploaded to Sentry with the releases/builds.  I wasn't able to find this on sentry's site either.
Is there any walkthrough on how to do this anywhere?

Any help @getsentry? @HazAT @mitsuhiko

Is now the problem solved?

@CarisL I don't believe anything has been updated to provide clear steps to uploading a sourcemap to Sentry, so I don't think it's been solved yet.

I agree with EricPKerr. The document does not giveclear steps for sourcemap instruction

I am closing all old issues, please if this is still a problem feel free to revive it.
Also, consider moving to our new SDK @sentry/react-native if it still happens there please open a new issue.

authors: CarisL EricPKerr HazAT WatsonFungHK

repo: getsentry/react-native-sentry


text:
ref: Normalize user options

This PR adds normalization of user options that should make it easier to work with them down the line.

At some point, I'd like to see us having tests for the options normalization but it doesn't have to be right now. Let's talk about how we want to deal with tests for now and go with that strategy.

Screw tests.
Jokes aside: Probably yes. Here it doesn't matter too much imo because TS pretty much asserts that stuff is correct but at some point, we should probably do some high-level integration tests.


text:
reduce mangling of involved object names

The short_name logic seems to be targeted at pods, replicasets, and
statefulsets where parts of the name can be auto generated. In other
cases the short_name mangling is undesirable as it throws away relevant
parts of the name when the name contains dashes.  For example a Service
called "my-lb" would appear in the culprit only as "my".
This is an improvement but still imperfect because 1) it is quite
possible to create many of these objects directly without any generated
suffix and 2) even when a suffix is appended it is not always 2 segments
as currently assumed. A more complete fix likely requires querying
kubernetes for details about the involved object and determining the
closest object that is not automatically created by kubernetes to
attribute the culprit to.

Thanks for the PR.
My only fear here is that I don't currently know for sure whether "Pod", "ReplicaSet", "StatefulSet" is the correct set. Do you think it might be enough to make this an opt-in argument for now? So you could run yours with MANGLE_NAMES="pod,replicaset,statefulset"?

Thanks, I pushed up a new container.

repo: getsentry/sentry-kubernetes


text:
Use namespaced TestCase

This PR add PHPUnit forward compatibility layer. Now all tests extend from namespaced PHPUnit TestCase.

Hi there, thanks for the contribution!
This was already done on the 2.0 branch, but it's still useful!

I don't think we need it in stable version.

I don't think we need it in stable version.

We don't necessarily need it, but it's good to have it 👍

Oh, I haven't seen changes. It only change parent class name.

repo: getsentry/sentry-php