text:
DropZoneItem css blocking MudMenu overlay

Bug type
Component
Component name
MudDynamicDropItem
What happened?
If you put MudMenu into MudDynamicDropItem, the overlay for the closing behavior does not respect the viewport of the screen but instead the parent element size. This is due to the CSS prop transform: translate3d(0px, 0px, 0px); on the MudDynamicDropItem style.
Link to the article I've found when solving this problem.
This has an easy solution, although I sincerely wonder why is the Transform prop used there. Could someone at least explain why it is there? I hope this will not be a breaking change.
I also noticed that this bug was introduced in the latest update to the MudDataGrid, which now has the feature to drag and drop columns. The problem with closing the Headeer options menu is the same.
Expected behavior
When the Transform prop is removed, the fixed position behaves relative to the viewport again.
Reproduction link
https://try.mudblazor.com/snippet/ckGRaVvmSkivzxFe
Reproduction steps

...
Relevant log output
No response
Version (bug)
6.7.0
Version (working)
No response
What browsers are you seeing the problem on?
Firefox
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I have only now noticed this has been previously discussed in #7047. I still feel like there should not be a workaround for this issue but rather a fix in the repository itself.

I sincerely wonder why is the Transform prop used there. Could someone at least explain why it is there?

We don't know. The original author, @emorell96, who made the commit, has not responded, which is why the issue is on hold. It is unclear what risks may arise if we simply remove it. Therefore, if someone is interested in investigating this further, the task is available for anyone to take.

authors: ScarletKuro fondraco

repo: MudBlazor/MudBlazor


text:
Adding adornment to a text field shows scrollbar

Things to check

[X] I have searched the existing issues for this bug
[X] To rule out a caching problem I made sure the bug also happens in an incognito tab

Bug type
Component
Component name
MudTextField
What happened?
Adding adornment to a text field shows scrollbar (error):

Without adornment scrollbar is not visible:

I have no idea why adding adornment to a text field adds a scrollbar. Please someone fix that.
Expected behavior
Scrollbar should not be visible when text field have adornment.
Reproduction link
https://try.mudblazor.com/snippet/wuQyaWFErwWaSUfj
Reproduction steps
Add adornment to text field and the scrollbar shows.
Relevant log output
No response
Version (bug)
7.6.0
Version (working)
6.20.0
What browsers are you seeing the problem on?
Chrome
On which operating systems are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

A reproduction link to trymudblazor is missing. This is mandatory.

Reproduction: https://try.mudblazor.com/snippet/wuQyaWFErwWaSUfj

#3455

#3455

The thing is that they are talking about 6.0.2, but actually in 6.20.0 there was indeed no scroll with this trymudblazor code, so I guess it is a regression?

source: gharchive/issue

authors: FritzTheCat9 ScarletKuro danielchalmers

license: MIT

license_type: permissive

license_source: github-api


text:
I want to use this in my project. I have an ionCube license.

Hello, I want to use this in my project. I have an ionCube Windows Desktop license. However, since I thought I could do this with github workflows instead of doing it manually every time, I started researching and came across your repo. Can you help me with this? What do I need to use this action in my project? Also, how do we make configurations such as ionCube version selection, PHP version selection and files to be encrypted?

I just tested and: Unable to resolve action murilochianfa/ioncube-encode-action, repository not found

I just tested and: Unable to resolve action murilochianfa/ioncube-encode-action, repository not found

Sorry for the wrong typo, but now its correct, now uses:
MuriloChianfa/ioncube-encoder-action@v1.0.0

I'll test it after lunch.
By the way, how does it do this encryption? Are you using ionCube CI for this yourself?
I also saw how to specify parameters, namely ionCube and PHP versions.
There is another issue I'm curious about. Currently, when I create a release in my worklow, I also create a zip file and add it to the release. Is it possible to do this with your action package? So, first the PHP files I have chosen will be encrypted, then they will be made into a zip without touching the normal repo and added to the release. Likewise, this zip file will be sent to our own APIs.

Hello, I want to use this in my project. I have an ionCube Windows Desktop license. However, since I thought I could do this with github workflows instead of doing it manually every time, I started researching and came across your repo. Can you help me with this? What do I need to use this action in my project? Also, how do we make configurations such as ionCube version selection, PHP version selection and files to be encrypted?

You can read the Inputs section for all parameters to set in your pipeline, ou directly here https://github.com/MuriloChianfa/ioncube-encoder-action/blob/98cfa104d0cdb7d167c7a67967e8109a7bd7d01a/action.yml#L5
For now, you can only use the license running the pipeline on a self-hosted server or in the trial version, as I am still writing and testing the temporary activation of the license.

I'll test it after lunch.
By the way, how does it do this encryption? Are you using ionCube CI for this yourself?
I also saw how to specify parameters, namely ionCube and PHP versions.
There is another issue I'm curious about. Currently, when I create a release in my worklow, I also create a zip file and add it to the release. Is it possible to do this with your action package? So, first the PHP files I have chosen will be encrypted, then they will be made into a zip without touching the normal repo and added to the release. Likewise, this zip file will be sent to our own APIs.

Yes, im testing with IonCube CI version.
And you can integrate this workflow with another actions by example actions/upload-artifact@v3 or something like this for upload the encrypted project into one version.
would be like this:
name: Encode with IonCube

on: [push]

jobs:
  encode:
    runs-on: ubuntu-latest

    steps:
    - name: Checkout Repository
      uses: actions/checkout@v3

    - name: IonCube Encode
      uses: MuriloChianfa/ioncube-encoder-action@v1.0.0
      with:
        encoder-version: 'current'
        php-target-version: '8.2'
        arch: 64
        source: 'src'
        output: 'encrypted'

    - uses: actions/upload-artifact@v3
      with:
        name: encrypted
        path: encrypted

It looks like you just published your project. I would like to contribute to this as much as I can. If there is anything I can do, you can tag me.
I see it says "trial" there. Is this the trial feature in ionCube online decoder? So, are the files we encrypt with this action currently encrypted temporarily?
I have a license, maybe we can get support from ionCube because such a github action is absolutely necessary.
For example, when I create a release right now, I automatically zip it, get the version code, and update it on my own servers. I do not update each location separately.
The only thing I'm missing right now is ionCube encryption, because I'm currently encrypting it in the desktop application and uploading it to github.
Could your repo be a solution to my request?
I've tested it now and the workflow works fine, but I don't know exactly where the encrypted file went :D

Could your repo be a solution to my request?

Yes, but this repository only can encrypt your project with IonCube, you need to integrate your action with another action with function of upload actions files to github like actions/upload-artifact@v3 OR softprops/action-gh-release@v1

I understand that the process creates encrypted files in the output I specified, and then I can add this output as a release asset or send it to my server if I want. But if I don't do anything else, it will just remain in encrypted form, right?
So, how should I configure it to select only certain files, ignore others, and copy only others, just like in the desktop version of IonCube?
Is there also an encoding process for dual PHP versions as in the IonCube desktop version?
I think I'm asking a little too much, but I want to make sure since this is exactly what I need.

So, how should I configure it to select only certain files, ignore others, and copy only others, just like in the desktop version of IonCube?

Its possible, but im not implemented this options yet, im still working on it.

Is there also an encoding process for dual PHP versions as in the IonCube desktop version?

This is possible too, you can use 2 times of this action, first encrypting the files of one version and later another action for the other files of next version.

If you inform me about how it can be implemented, I will try to help. I will review the entire code at my convenience.
Actually, I'm not talking about encode separately. For example, if you encode only for PHP 8.1, it won't work on others. However, if you encode for PHP 8.1-8.2, your code will work in these two versions.

Actually, I'm not talking about encode separately. For example, if you encode only for PHP 8.1, it won't work on others. However, if you encode for PHP 8.1-8.2, your code will work in these two versions.

i dont know if it works, we have to test this for confirm.

Hi dude I went through your code and I pretty much understand how it works. I've seen a few TODO: attachments. What can I do?

Also i added trial: false and tried with some ioncube_encoder.sh still working trial so evaluation

authors: BeycanDeveloper MuriloChianfa

repo: MuriloChianfa/ioncube-encoder-action


text:
fix cdUp logic

Closes #731.
I did not change the assert(false) part although I do not really understand why it is here : Qt says that the logical operation of moving up is just not done if the parent directory does not exist, so even in the rare case of /.git, we could just keep running or display a warning.

According to the documentation: This is the path of the .git folder for normal repositories, or of the repository itself for bare repositories.
https://libgit2.org/libgit2/#HEAD/group/repository/git_repository_path
So I don't understand why it could that the folder is not the .git folder?

We may have a repository that is bare in the sense that its worktree is not at the same place as its configuration directory, in which case the configuration directory is not repo/.git but just repo. That's what I am addressing in my issue.
Cordialement,
Yann Salmon
Depuis mon téléphone ; excusez la brièveté.

Thanks for the clarification. I will merge it as soon as the ci build is working again

source: gharchive/pull-request

authors: Murmele ysalmon

repo: Murmele/Gittyup


text:
Adds slick slider to the project instead of hacky carousel.

NOTE: This adds depreciation warnings becuase the gem uses scss.css as the extension.  I put in a PR to fix this issue see: https://github.com/bodrovis/jquery-slick-rails/pull/10
I also removed the Semantic Vernacular tests.

Coverage increased (+0.77%) to 84.64% when pulling 55e96f30f1175bacf115f1207804e530d1737f2c on raysuelzer:ror4 into 30346014e79d0c25c8aaec73b488006dbba02c93 on MushroomObserver:ror4.

Coverage increased (+0.77%) to 84.64% when pulling 5d62f970968eeabfe5c5a542c362d3fed0fa1ad1 on raysuelzer:ror4 into 30346014e79d0c25c8aaec73b488006dbba02c93 on MushroomObserver:ror4.

Coverage increased (+0.77%) to 84.64% when pulling b9651b9869a8edabe526edc720227cec6f0c95f7 on raysuelzer:ror4 into 30346014e79d0c25c8aaec73b488006dbba02c93 on MushroomObserver:ror4.

Coverage increased (+0.77%) to 84.64% when pulling 4b026f37d994aef3a5ae2f1f0184b02fc28e08cf on raysuelzer:ror4 into 30346014e79d0c25c8aaec73b488006dbba02c93 on MushroomObserver:ror4.

Coverage increased (+0.77%) to 84.64% when pulling d9c8edb43659fa7fb31918b7ea2d671c12f18559 on raysuelzer:ror4 into 30346014e79d0c25c8aaec73b488006dbba02c93 on MushroomObserver:ror4.

Coverage increased (+0.75%) to 84.62% when pulling a0481534351259510904a2cb90e900e28a3bd198 on raysuelzer:ror4 into 30346014e79d0c25c8aaec73b488006dbba02c93 on MushroomObserver:ror4.

Coverage increased (+0.75%) to 84.62% when pulling a646f4de26e2f6f76a00f47d4aa1e8bcff37259a on raysuelzer:ror4 into 30346014e79d0c25c8aaec73b488006dbba02c93 on MushroomObserver:ror4.

Coverage increased (+0.75%) to 84.62% when pulling d07b050597a4c0a782c70695f8e7fad37f080660 on raysuelzer:ror4 into 30346014e79d0c25c8aaec73b488006dbba02c93 on MushroomObserver:ror4.

Thanks for dealing with so many issues!  Also nice to see coverage increase a bit.  Hopefully we will be able to release when Jason gets back.
For the Semantic Vernacular tests, I suggest leaving the test code there but disabling the tests from running.  This will (1) if we want -- make it easier to figure out why the timeout error is not being rescued, and (2) let us remove the associated SVD classes at the same time as we remove the tests
To skip a test method, just insert skip("msg") as the first line of a test.  For example

class SemanticVernacularControllerTest < FunctionalTestCase
  def test_index
    skip("Takes too long to time out.")

Sorry Joe.  I deleted them in this commit.  I'm not on my linux box anymore, but i can put them back in.

authors: JoeCohen coveralls raysuelzer

repo: MushroomObserver/mushroom-observer


text:
Music cannot be resumed

After a song is completed, the button doesn't change from 'pause' to 'play'.

Desired behavior = song should stop but play button should be active again. For now, this will satisfy the bug.
Notification of credit received is covered elsewhere.
Open question for later: Should we highlight a "next song" after one completes?

authors: ShuoZhang-dev mpmikesell

repo: MusicAsLanguage/mobileapp


text:
Concatination Duplicate Bug

When the cursor at position 0, on pressing the delete button the first portion of data gets duplicated and then gets concatinated with the last portion of the data.

Issue resoved with the new feature of manual deletion positon slection.
Follow this commit - 1a914b59edfaa3282076c32af37b2f4ba9731b96

repo: MustakAbsarKhan/Calculator-App


text:
今日收到了微信提醒，大意就是提醒我非法使用了插件之类，强制将我下线了，还好是第一次，后续可能再发现的话就要封号了。暂时告别这个插件了，真的很好用，感谢作者！xx腾讯 shit！

issue规范

MacOS版本 : 10.xx.x
微信版本 : 2.x.x
小助手版本 : 2.x.x
BUG描述 : 点击窗口闪退
操作场景 : 微信启动后, 鼠标左键点击会话列表中某个会话的头像
方便的话提供日志, 截图或者视频(可选)

哥们我刚才也收到了，你用的是小助手的哪个版本呀？我用的是wechat 3.1.2，小助手2.9-1.1

我刚才也收到了

我也。。。

老哥们用的是什么版本呀，分享下呀 ，看看还有没有可能可以继续用

我也。。。暂时告别吧，安全第一

今天收到警告，告别了
➜  ~ omw un
[22:01:11] 当前 Oh My WeChat 版本为 v2.1.4
[22:01:11] 当前微信小助手版本为 v2.9.2
[22:01:12] 你想卸载哪一个？

微信小助手
Oh My WeChat
两个都卸载
取消
你的选择：1
\n\t卸载成功, 重启微信生效!
[22:01:16] 微信小助手卸载完成

WeChat Version 3.1.5 (18846)

刚才也收到了，害

我也收到了 祝张小龙全家安康吧

祝张小龙户口本只有一页

收到+1

收到+1

我也收到了

今天收到警告，告别了 ➜ ~ omw un [22:01:11] 当前 Oh My WeChat 版本为 v2.1.4 [22:01:11] 当前微信小助手版本为 v2.9.2 [22:01:12] 你想卸载哪一个？

微信小助手
Oh My WeChat
两个都卸载
取消
你的选择：1
\n\t卸载成功, 重启微信生效!
[22:01:16] 微信小助手卸载完成

WeChat Version 3.1.5 (18846)

Device Type: MacBookPro16,1
System Version: Version 10.15.7 (Build 19H1519)
System Language: en
WeChat Version: [2021-07-09 21:18:35] v3.1.5.19 (18846) #c2c10a1669
WeChat Language: en
Historic Version: [2021-05-14 11:38:20] v3.0.3.17 (18061) #33550cfae1
Network Status: Reachable via WiFi or Ethernet
Display: *(1792x1120)/Retina

收到+1，日了狗了

收到+1

App Version: Version. 3.2.1 (19797)
Verbose: v3.2.1.16 (0x13020110)
System: OSX 10.15.7 build(19H1519)
Model: MacBookPro12,1
Hash: 9a86491f79
Build Date: Oct 17 2021
Build Time: 09:49:33
Lang: zh-Hans

我也是，张小龙可以早点买块坟地了

早上更新了下微信 弹出检测到有插件 立马安装了以前的3.0.0 beta的。。。

早上更新了下微信 弹出检测到有插件 立马安装了以前的3.0.0 beta的。。。

好吧。今天被封了。。不敢用了

authors: KenmuHuang LiuShaw VictorNanka WaterSunMount abchwabc hereBo hunkier izozo liusoon luofeng0603 mingjunChan simirence smallLabel syxchina testerliyd wenyang94 withzhaoyu

repo: MustangYM/WeChatExtension-ForMac


text:
安装报错：No such file or directory

issue规范

MacOS版本 : 13.4
微信版本 : 3.8.1
小助手版本 : 3.8.2.1
BUG描述 : 安装报错：No such file or directory
操作场景 : 拖动install.sh至terminal中执行后
日志

微信的Appstore版和官网版命名不一致，后面我会兼容一下。

我拉取最新代码也是报这个错，请问兼容了吗？

官网下载的3.8.2版本，一样的报这些错误，appStore版本3.8.1也是报这些错

same issue

3.8.1和3.8.2，现在更新了3.8.3还是不行。

我拉取最新代码也是报这个错，请问兼容了吗？
请问该要怎么兼容

无法兼容
获取 Outlook for iOShttps://aka.ms/o0ukef

发件人: XYuanZ @.>
发送时间: Wednesday, December 6, 2023 5:15:35 PM
收件人: MustangYM/WeChatExtension-ForMac @.>
抄送: maomaoxiansheng @.>; Comment @.>
主题: Re: [MustangYM/WeChatExtension-ForMac] 安装报错：No such file or directory (Issue #1810)
我拉取最新代码也是报这个错，请问兼容了吗？
请问该要怎么兼容
―
Reply to this email directly, view it on GitHubhttps://github.com/MustangYM/WeChatExtension-ForMac/issues/1810#issuecomment-1842484185, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB5GNH2WSDR4PW35IZFCZA3YIAZTPAVCNFSM6AAAAAA2U6XFZGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBSGQ4DIMJYGU.
You are receiving this because you commented.Message ID: @.***>

authors: MustangYM XYuanZ debbyzang iPermanent irvinglu23 maomaoxiansheng owspace


text:
还我的TOUCHBAR！！！

issue规范

MacOS版本 : 11.1
微信版本 : 2.6.1
小助手版本 : 2.8.3
BUG描述 : 点击窗口闪退
操作场景 : 下载了touchbar就没了
方便的话提供日志, 截图或者视频(可选)

还我的touchbar，touchbar不能用？

touchbar天天用，要是不能解决只能卸载了。。。

1.5分钟后：
这个issue我关了哈，重启了一下解决了


text:
Fix NIP-05 handling for zap feed

We support entering a nip-05 address in the sync nostr contacts form, however this would break the zap feed because it'd always return undefined when trying to get the hex pub. This fixes  it so we can actually resolve it into the hexpub as well as makes it so it'll return a better error when this happens.

not needed anymore

repo: MutinyWallet/mutiny-web


text:
Login simulator

Why it has been removed? I can't find any explanation except "do not use it" in #18 and #20. Then how to check that e.q. LDAP authentication succeeds before getting problems during login stage?

Because results are not reliable.
Plugin don't "know" that this is just a simulation.
Stuff that got triggered by the simulator is not removed.
.....
There is no need for a simulator, because you cant lock yourself out.
The fork does things in a different way, it wont touch your local users.
http://mutonufoai.github.io/pgina/documentation.html

repo: MutonUfoAI/pgina


text:
Feature/cache

Added some functionality. But still in progress.

Need to add some tests.
Issue #10


text:
BungeeCord plugin messages bug.  (The received string length is longer than maximum allowed)

What is the output link of /viaversion dump?
https://dump.viaversion.com/c1fc4812461a6b6a4302defe89026f739ca3d3f9ea14040bf73ac3435f299217
Are you using any additional software like BungeeCord? If so, what software and version? (Please list your plugins as well)
BungeeCord with changeskin
How does this error happen? login? Using an item?
Is there an error in the console? Use pastebin.com. Is there a kick message?
[19:19:37 INFO]: [ViaVersion] Leymooo INCOMING: PLAY 10 -> 9 [UNKNOWN[393]] Value: PacketWrapper{packetValues=[], readableObjects=[Pair{Type|String, bungeecord:legacy/changeskin}], id=9}
[19:19:37 INFO]: Leymooo lost connection: Internal Exception: io.netty.handler.codec.DecoderException: The received string length is longer than maximum allowed (28 > 20)

fixed in  https://github.com/SpigotMC/BungeeCord/commit/6fadb4250cb7f89feb2a98d9de973f6d627e33ae

repo: MylesIsCool/ViaVersion

license: mit

license_source: bigquery


text:
🛑 PharmacyRecommend is down

In d862892, PharmacyRecommend (http://www.lmshi.shop:8081) was down:

HTTP code: 0
Response time: 0 ms

Resolved: PharmacyRecommend is back up in a4e7174 after 8 days, 6 hours, 50 minutes.


text:
[P1] [Umbrella] Storage Enhancements - Pre-TestNet

Details
Dependent Tasks

#1318
#1136
#297

I'll add more items to this list,

authors: todd-mystenlabs velvia

repo: MystenLabs/sui


text:
Sui Code Bug or Feature Request

We found that the parse_file function in move-compiler::parser::syntax.rs does not return Result::Err(). However, when calling this function, the case where parse_file returns Result::Err() is handled, and Diagnostics are generated. Is this expected behavior?

@awelc can we close this issue now?

Fixed in https://github.com/MystenLabs/sui/pull/18301

authors: awelc hapeeeeee stefan-mysten


text:
thread 'main' panicked at 'Sui System State object deserialization cannot fail: Eof'

Steps to Reproduce Issue

download configs from:
https://github.com/MystenLabs/sui/raw/main/crates/sui-config/data/fullnode-template.yaml
https://github.com/MystenLabs/sui-genesis/raw/main/devnet/genesis.blob

use docker-compose.yaml from the https://github.com/MystenLabs/sui/blob/main/docker/fullnode/docker-compose.yaml

start container by docker compose up -d

Expected Result
container start successfully
Actual Result
Error:
....
fullnode  | 2022-10-20T18:13:38.463694Z  INFO sui_storage::event_store::sql: Recovered last sequence number from event store last_seq_num=0
fullnode  | thread 'main' panicked at 'Sui System State object deserialization cannot fail: Eof', /sui/crates/sui-core/src/authority/authority_store.rs:1382:14
fullnode  | stack backtrace:
fullnode  | 2022-10-20T18:13:38.480878Z ERROR telemetry_subscribers: panicked at 'Sui System State object deserialization cannot fail: Eof', /sui/crates/sui-core/src/authority/authority_store.rs:1382:14 panic.file="/sui/crates/sui-core/src/authority/authority_store.rs" panic.line=1382 panic.column=14
fullnode  |    0:     0x55e06e2779bd - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h2b42ca28d244e5c7
fullnode  |    1:     0x55e06e2a078c - core::fmt::write::h401e827d053130ed
fullnode  |    2:     0x55e06e270701 - std::io::Write::write_fmt::hffec93268f5cde32
fullnode  |    3:     0x55e06e279435 - std::panicking::default_hook::{{closure}}::h1f023310983bc730
fullnode  |    4:     0x55e06e279151 - std::panicking::default_hook::h188fec3334afd5be
fullnode  |    5:     0x55e06cb039b6 - telemetry_subscribers::set_panic_hook::{{closure}}::he5852eb7725a0cd1
fullnode  |    6:     0x55e06e279a7a - std::panicking::rust_panic_with_hook::hf26e9d4f97b40096
fullnode  |    7:     0x55e06e2798b7 - std::panicking::begin_panic_handler::{{closure}}::hfab912107608087a
fullnode  |    8:     0x55e06e277eb4 - std::sys_common::backtrace::__rust_end_short_backtrace::h434b685ce8d9965b
fullnode  |    9:     0x55e06e2795e9 - rust_begin_unwind
fullnode  |   10:     0x55e06b9876c3 - core::panicking::panic_fmt::ha6dc7f2ab2479463
fullnode  |   11:     0x55e06b987813 - core::result::unwrap_failed::h42ad8e915aa0a906
fullnode  |   12:     0x55e06bc33083 - sui_core::authority::authority_store::SuiDataStore<S>::get_sui_system_state_object::h9cf071193a11b213
fullnode  |   13:     0x55e06bed0e06 - sui_node::SuiNode::start::{{closure}}::h4950c5a67e0c1aed
fullnode  |   14:     0x55e06bf1e603 - <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::h6af338de7ad624e2
fullnode  |   15:     0x55e06bc37a9f - <tracing::instrument::Instrumented<T> as core::future::future::Future>::poll::h832f69ca2a3b36f9
fullnode  |   16:     0x55e06bace94d - std::thread::local::LocalKey<T>::with::h5158d9d7e27b382a
fullnode  |   17:     0x55e06bd127ff - tokio::park::thread::CachedParkThread::block_on::h4ea2eaa1af06774a
fullnode  |   18:     0x55e06bb216e4 - tokio::runtime::scheduler::multi_thread::MultiThread::block_on::hac6ed422dba14533
fullnode  |   19:     0x55e06bc2290b - tokio::runtime::Runtime::block_on::hb50a3bec1e09b166
fullnode  |   20:     0x55e06bd392a9 - sui_node::main::h06f0469f12f67b35
fullnode  |   21:     0x55e06ba393b3 - std::sys_common::backtrace::__rust_begin_short_backtrace::h1d428248447d565d
fullnode  |   22:     0x55e06bda7f89 - std::rt::lang_start::{{closure}}::hd5e38e51957905a5
fullnode  |   23:     0x55e06e268a4e - std::rt::lang_start_internal::h6612c8a7a6861b8b
fullnode  |   24:     0x55e06bd39398 - main
fullnode  |   25:     0x7fb6db5f6d0a - __libc_start_main
fullnode  |   26:     0x55e06b9a94aa - _start
fullnode  |   27:                0x0 - <unknown>
fullnode  | 2022-10-20T18:13:38.498993Z  INFO sui_storage::lock_service: LockService command loop stopped, the sender on other end hung up/dropped
fullnode  | 2022-10-20T18:13:38.499186Z  INFO sui_storage::lock_service: LockService queries loop stopped, the sender on other end hung up/dropped
fullnode exited with code 101

System Information

uname -a
Linux sui 5.15.0-25-generic #25-Ubuntu SMP Wed Mar 30 15:54:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.1 LTS
Release:	22.04
Codename:	jammy

docker version
Client: Docker Engine - Community
Version:           20.10.20
API version:       1.41
Go version:        go1.18.7
Git commit:        9fdeb9c
Built:             Tue Oct 18 18:20:18 2022
OS/Arch:           linux/amd64
Context:           default
Experimental:      true
Server: Docker Engine - Community
Engine:
Version:          20.10.20
API version:      1.41 (minimum version 1.12)
Go version:       go1.18.7
Git commit:       03df974
Built:            Tue Oct 18 18:18:08 2022
OS/Arch:          linux/amd64
Experimental:     false
containerd:
Version:          1.6.8
GitCommit:        9cd3357b7fd7218e4aec3eae239db1f68a5a6ec6
runc:
Version:          1.1.4
GitCommit:        v1.1.4-0-g5fd4c4d
docker-init:
Version:          0.19.0
GitCommit:        de40ad0

Temporary problem with  the bad genesis.blob
Solved.


text:
🛑 POST to DRM is down

In 9c2dcec, POST to DRM (https://mysteryexe.xyz/drm.php?) was down:

HTTP code: 403
Response time: 540 ms

Resolved: POST to DRM is back up in 113b476 after 44 minutes.

repo: Mysteryexe/uptime-checker


text:
Pouch dupe

Description:
This is an old old dupe that used to plague mods in 1.7.10, basically you drop a container and open it at the same time.
Reproduction:

Hold pouch(apothecary or component)  in main hand
press the hotkey for opening the pouch/right click and then immediately press q, more or less pressing both at the same time but opening the pouch before dropping it, might take a few tries
pouch gui appears on screen and items can be removed from it, pouch item drops on the ground
remove items, close gui, pick up dropped pouch, remove items a second time

Expected behavior:
many mods for 1.7.10 used to have this dupe and a few in 1.12 do as well, probably requires running additional checks for item location and/or storing the inventory to an external location not connected directly to the item, im not an expert on what needs to be done to resolve this, those are just some things other mod devs have done.
Mystic Mods Versions

Roots: 3.0.25
MysticalLib: 1.6.0

Other Versions:

Forge: 14.23.5.2847
Minecraft: 1.12.2

Screenshot (gif):

Bonus: while testing this dupe i discovered that you can move opened pouches around your inventory using the number keys, if you open a pouch on your hotbar, and then hover over a slot in the pouch and press the number corresponding to the hotbar location of the pouch, the pouch will get put inside itself, crash the player, and delete itself on relog
if you put a different pouch into the currently open pouch, theres no way to remove it.

Thanks for the information!
Especially the bonus point, that one is frustrating as hell and I keep forgetting that is a possibility. I think I can bypass that by making an isSlotValid function that checks to make sure that the item isn't another pouch, meaning you can't move items in regardless - in theory, if Minecraft actually checks that.
For the former, that is literally what I'm currently coding: the inventory will be stored safely in the "world save data" (server-side data cache in the data folder), and instead pouches will have a UUID associated with them which is then used when looking up the inventory.
Hopefully that'll address the former issue!
If you're interested, I've just started a wide, open alpha of Roots 3.1 on the Mystic Modding Discord -- it will have compatibility issues with a lot of things, including pre-existing pouches, but if you're interested in checking it out I'd love the same level of diligence and feedback that you've shown with this issue!

Thanks for the quick response and feedback! And good luck with getting that working, I'll definitely make sure to hop on the discord server and check out that alpha when I have time between reporting on githubs all of the other annoyances the kids on the server I staff keep finding. xD

Also, what's the mod letting you see a WAILA like screen for a dropped item?

I think I've finally come up with a bug-free solution to the pouches; it won't hold over upgrades at the minute (pouches would just be wiped) as I have yet to code some transitionary stuff, but all pouches are now stored externally on the server and hopefully with no additional overheads as saving the world data is only called once (on the container closing).
(And the world data should be saved regularly enough regardless)

authors: DoomRater ace10102 noobanidus

repo: MysticMods/Roots


text:
ANMS_FUN_BLD_001 (Time-Based Rule)

Setup for the test case was not successful.  The tables of known rules and report templates were not generated, and the number of rules was not displayed, by a time was.  Time based rules were created and submitted, but did not execute until optional receiving managers parameter was included.

This is a duplicate of issue #98

This is a duplicate of issue https://github.com/NASA-AMMOS/anms/issues/98

repo: NASA-AMMOS/anms


text:
Create NoahMP-36 plugin for CMEM3 radiative transfer model

Allows use of Noah-MP-3.6 with the CMEM3 radiative transfer model so
that the land surface model (LSM) can generate microwave brightness
temperatures (V-pol and H-pol) given meteorological inputs. This will
allow for future data assimilation of SMAP brightness temperatures
into the LSM directly, instead of depending on SMAP retrievals of soil
moisture, which introduce their own assumptions and biases.

I realized after creating this pull request that I need to create a testcase for it, too. I'm working on that.

Thanks for the instruction. I've made the requested changes.

Thanks for the revisions.
Would you please package the data needed to run your test?  Please see
LISF/docs/howto_create_lis_testcases/howto_create_lis_testcases.adoc
Do not commit the tar files, just tell me where they are.  I will upload them to our data server.

I created the tar files and have placed them in the directory here:
/discover/nobackup/pshellit/lisFromGitHub/noahmp-3.6-cmem3-plugin/SRC/lis/testcases/surfacemodels/land/noahmp.3.6_cmem3/
The names of the files are as follows:

noahmp36cmem3plugintest_input.tar.gz
noahmp36cmem3plugintest_ldt.tar.gz
noahmp36cmem3plugintest_output.tar.gz

Resolves: #33

authors: jvgeiger pshellit

repo: NASA-LIS/LISF


text:
Simple wrappers to call the pds-batch-loader and pds-service-loader docker compose services

At the moment the pds-batch-loader and pds-service-loader docker compose services are executed with the environment variables defined in the docker compose .env file.
Create some simple wrappers (shell scripts) to execute these pds-batch-loader and pds-service-loader services with relevant arguments (E.g.: The harvest-job-config file is passed as an argument).

Created pull request: https://github.com/NASA-PDS/registry/pull/25

repo: NASA-PDS/archive-analytics


text:
himanshukurapati-nau

The Readme file is currently lengthy and complex, making it challenging for newcomers to comprehend how to contribute effectively to the project.
To enhance accessibility and clarity, I propose relocating the Contributing section to the beginning of the Readme file and streamlining its content where feasible.
I kindly request assistance from anyone willing to dedicate time to address this issue and improve the project's accessibility for all contributors. Thank you!

Hi, myself Himanshu Kurapati studying master's in computer science in NAU. I am willing to contribute to open source projects which would help me in learning new things. I am interested to solve this issue. I am assigning it to myself.

Hi @caiton1 I would like to get your help as this is my first time doing it.

I have moved contribution section to top.

repo: NAU-OSS/jabref


text:
Feature 405 point to grid

Added Point2Grid wrapper
Added Point2Grid.conf which uses test data found on kiowa
Added a unit test file containing 1 unit test
Edited quicksearch keywords file
Edited met_util.py to add a few name lookups

I made some in-line edits/suggestions. You will also need to add:

Documentation file for use case in docs/use_cases/met_tool_wrapper/Point2Grid/Point2Grid.py
A section for the new wrapper and all of the possible config variables in docs/Users_Guide/wrappers.rst
An item for each new config variables in the Glossary: docs/Users_Guide/glossary.rst

Thanks George! I will work on the documentation. I could not actually find your inline comments. I am probably doing something incorrectly. I added one of my own just as a sanity check.

@fisherhucar I see the inline comments in the Conversation and also if you go to "Files changed." Let me know if you are still having issues finding them.

Yep, I tried both of those but I don't seem to see them. Maybe a quick
screen share after the 11:00 meeting?
On Tue, May 19, 2020 at 10:31 AM George McCabe notifications@github.com
wrote:

@fisherhucar https://github.com/fisherhucar I see the inline comments
in the Conversation and also if you go to "Files changed." Let me know if
you are still having issues finding them.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NCAR/METplus/pull/466#issuecomment-630934478, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AHAUIKGSRRK6NVMYBWEWRWTRSKX7VANCNFSM4NELL6UQ
.

--
Hank Fisher       Research Applications Laboratory
303-497-2817      National Center for Atmospheric Research
fisherh@ucar.edu  P.O. Box 3000, Boulder CO 80307-3000

Ah, I had to submit my review before you could see them. You should be able
to see them now.
On Tue, May 19, 2020 at 10:42 AM Hank Fisher notifications@github.com
wrote:

Yep, I tried both of those but I don't seem to see them. Maybe a quick
screen share after the 11:00 meeting?
On Tue, May 19, 2020 at 10:31 AM George McCabe notifications@github.com
wrote:

@fisherhucar https://github.com/fisherhucar I see the inline comments
in the Conversation and also if you go to "Files changed." Let me know if
you are still having issues finding them.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NCAR/METplus/pull/466#issuecomment-630934478, or
unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AHAUIKGSRRK6NVMYBWEWRWTRSKX7VANCNFSM4NELL6UQ
.

--
Hank Fisher Research Applications Laboratory
303-497-2817 National Center for Atmospheric Research
fisherh@ucar.edu P.O. Box 3000, Boulder CO 80307-3000
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/NCAR/METplus/pull/466#issuecomment-630941845, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AFSSZN54MJWEP52M6RZPTE3RSKZHTANCNFSM4NELL6UQ
.

--
George McCabe - Software Engineer III
National Center for Atmospheric Research
Research Applications Laboratory
303-497-2768
My working day may not be your working day. Please do not feel obliged to
reply to this email outside of your normal working hours.

There they are! Thanks.
Hank
On Tue, May 19, 2020 at 10:49 AM George McCabe notifications@github.com
wrote:

Ah, I had to submit my review before you could see them. You should be able
to see them now.
On Tue, May 19, 2020 at 10:42 AM Hank Fisher notifications@github.com
wrote:

Yep, I tried both of those but I don't seem to see them. Maybe a quick
screen share after the 11:00 meeting?
On Tue, May 19, 2020 at 10:31 AM George McCabe <notifications@github.com
wrote:

@fisherhucar https://github.com/fisherhucar I see the inline
comments
in the Conversation and also if you go to "Files changed." Let me know
if
you are still having issues finding them.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NCAR/METplus/pull/466#issuecomment-630934478, or
unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AHAUIKGSRRK6NVMYBWEWRWTRSKX7VANCNFSM4NELL6UQ

.

--
Hank Fisher Research Applications Laboratory
303-497-2817 National Center for Atmospheric Research
fisherh@ucar.edu P.O. Box 3000, Boulder CO 80307-3000
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/NCAR/METplus/pull/466#issuecomment-630941845, or
unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AFSSZN54MJWEP52M6RZPTE3RSKZHTANCNFSM4NELL6UQ
.

--
George McCabe - Software Engineer III
National Center for Atmospheric Research
Research Applications Laboratory
303-497-2768
My working day may not be your working day. Please do not feel obliged to
reply to this email outside of your normal working hours.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NCAR/METplus/pull/466#issuecomment-630945719, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AHAUIKASEZIQDN3INN5XJN3RSK2DPANCNFSM4NELL6UQ
.

--
Hank Fisher       Research Applications Laboratory
303-497-2817      National Center for Atmospheric Research
fisherh@ucar.edu  P.O. Box 3000, Boulder CO 80307-3000

authors: fisherhucar georgemccabe

repo: NCAR/METplus


text:
cu_tiedtke.f90 divide by zero

I'm tracking down whether this is a problem with the input data or the code itself. ICAR was built with MODE=debugslow on Intel compilers. About 30% of the way through the first time step an error forrtl: error(73): floating divide by zero occurs.  The domain is situated over Idaho.
Physics Options:
pbl = 2 ! Simple
lsm = 3 ! Noah
water = 2 ! simple
mp = 2 ! simple
rad = 2 ! simple
conv = 1 ! Tiedke Scheme
adv = 1 ! upwind
wind = 1 ! linear theory

The traceback provides the following (edited) information:
Routine             Line               Source
module_cu_tiedtke    2923    cu_tiedtke.f90
module_cu_tiedtke    1211    cu_tiedtke.f90
module_cu_tiedtke     648     cu_tiedtke.f90
module_cu_tiedtke     443     cu_tiedtke.f90
convection_mp_con    153     cu_driver.f90
time_step_mp_step     477     time_step.f90
MAIN__                         90     driver.f90

Hi Nick,
I believe that generally when I have seen errors in the core physics from WRF, it is often a problem with the inputs.  One thing that jumps to mind is the order of the vertical dimension.  Do you have 1000hPa (or 0m ASL or AGL) as the first level in the vertical dimension?  If it is the last level the code will break.
I would recommend that while you are still testing, you may want to turn off most of the physics parameterizations to make it as simple as possible.  You could even set wind=0 to turn off the linear theory perturbation.
pbl = 0 ! Simple
lsm = 0 ! Noah
water = 0 ! simple
mp = 2 ! simple
rad = 0 ! simple
conv = 0 ! Tiedke Scheme
adv = 1 ! upwind
wind = 1 ! linear theory

On Jul 17, 2017, at 12:15 PM, Nick Dawson notifications@github.com wrote:
I'm tracking down whether this is a problem with the input data or the code itself. ICAR was built with MODE=debugslow on Intel compilers. About 30% of the way through the first time step an error forrtl: error(73): floating divide by zero occurs. The domain is situated over Idaho.
Physics Options:
pbl = 2 ! Simple
lsm = 3 ! Noah
water = 2 ! simple
mp = 2 ! simple
rad = 2 ! simple
conv = 1 ! Tiedke Scheme
adv = 1 ! upwind
wind = 1 ! linear theory
The traceback provides the following (edited) information:
Routine             Line               Source
module_cu_tiedtke    2923    cu_tiedtke.f90
module_cu_tiedtke    1211    cu_tiedtke.f90
module_cu_tiedtke     648     cu_tiedtke.f90
module_cu_tiedtke     443     cu_tiedtke.f90
convection_mp_con    153     cu_driver.f90
time_step_mp_step     477     time_step.f90
MAIN__                         90     driver.f90
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/NCAR/icar/issues/34, or mute the thread https://github.com/notifications/unsubscribe-auth/ADOgXtDak_AGxGrqKwzE-0PlDJJTomONks5sO4Y3gaJpZM4OaJx5.

Using the simplified options (along with wind=0), the model ran. Wind values are provided for all time steps but after the first time step the ta2m output is blank (missing values). I'm pretty sure this happens because nearly everything is turned off.
The problem must be the input files. Input files are created from CFSv2 data in WPS. Two runs of ungrib are needed to provide the 3D data and the surface data. I've added variables to the ungrib/metgrid tables to provide the necessary inputs for icar. Looking at the "Z" field, the first metgrid level ranges between 600-1300 gpm. But the next level starts at ~100 gpm and increases monotonically up to ~45,000 gpm thereafter.
ICAR does provide a warning, "Forcing Z levels are below the terrain provided. For pressure level forcing data this is expected, but not well tested."

Hi Nick, have you made any more progress on this?  Does it work with other input files so we can close this?

I wasn't able to get things working and moved on to testing MPAS. I will give it another shot tomorrow and see if I can get ICAR running with CFSv2 inputs.

OK, if you have a minimal forcing dataset you can post that reproduces this error, let me know and I'll take a look at it.

What is the minimal forcing needed in order run ICAR with nearly all parameterizations turned off? Is it simply a wind field, lat(u,v)/lon(u,v), Z, and heights? The current CFSv2 inputs are too large (217MB) to share via github. I assume the &var_list can also be trimmed down with the following &physics options?
Here's what I mean when I say turn off parameterizations
&physics
pbl = 0
lsm = 0
water = 0
mp = 2
rad = 0
conv = 0
adv = 1
wind = 0
https://github.com/NCAR/icar/issues

You also need (potential) temperature, water vapor and pressure. 217MB isn’t very large though, I can set up an FTP site for you to upload to, I’ll email directly with an ftp site.
ethan

On Aug 1, 2017, at 10:10 AM, Nick Dawson notifications@github.com wrote:
What is the minimal forcing needed in order run ICAR with nearly all parameterizations turned off? Is it simply a wind field, lat(u,v)/lon(u,v), Z, and heights? The current CFSv2 inputs are too large (217MB) to share via github. I assume the &var_list can also be trimmed down with the following &physics options?
Here's what I mean when I say turn off parameterizations
&physics
pbl = 0
lsm = 0
water = 0
mp = 2
rad = 0
conv = 0
adv = 1
wind = 0
https://github.com/NCAR/icar/issues https://github.com/NCAR/icar/issues
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/NCAR/icar/issues/34#issuecomment-319418451, or mute the thread https://github.com/notifications/unsubscribe-auth/ADOgXkt33kqcmypsXCbrzvVoQiTxdXYoks5sT04KgaJpZM4OaJx5.

I decreased the grid spacing of the forcing files so they are much smaller now, but I will still need to send via FTP.
Nick Dawson, Ph.D.
ATMOSPHERIC SCIENTIST
Idaho Power | Power Supply
Work 208-388-5291
Mobile 208-860-0954
From: Ethan Gutmann [mailto:notifications@github.com]
Sent: Tuesday, August 01, 2017 10:34 AM
To: NCAR/icar icar@noreply.github.com
Cc: Dawson, Nick NDawson@idahopower.com; Author author@noreply.github.com
Subject: [EXTERNAL] Re: [NCAR/icar] cu_tiedtke.f90 divide by zero (#34)
You also need (potential) temperature, water vapor and pressure. 217MB isn’t very large though, I can set up an FTP site for you to upload to, I’ll email directly with an ftp site.
ethan

On Aug 1, 2017, at 10:10 AM, Nick Dawson <notifications@github.commailto:notifications@github.com> wrote:
What is the minimal forcing needed in order run ICAR with nearly all parameterizations turned off? Is it simply a wind field, lat(u,v)/lon(u,v), Z, and heights? The current CFSv2 inputs are too large (217MB) to share via github. I assume the &var_list can also be trimmed down with the following &physics options?
Here's what I mean when I say turn off parameterizations
&physics
pbl = 0
lsm = 0
water = 0
mp = 2
rad = 0
conv = 0
adv = 1
wind = 0
https://github.com/NCAR/icar/issues https://github.com/NCAR/icar/issues
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/NCAR/icar/issues/34#issuecomment-319418451, or mute the thread https://github.com/notifications/unsubscribe-auth/ADOgXkt33kqcmypsXCbrzvVoQiTxdXYoks5sT04KgaJpZM4OaJx5.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/NCAR/icar/issues/34#issuecomment-319425250, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AcBLKtV9Fr0bt5komeJELBZjUFwlYhZIks5sT1OAgaJpZM4OaJx5.

This transmission may contain information that is privileged, confidential and/or exempt from disclosure under
applicable law.  If you are not the intended recipient, you are hereby notified that any disclosure, copying,
distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If
you received this transmission in error, please immediately contact the sender and destroy the material in its
entirety, whether in electronic or hard copy format.  Thank you.

Given how many other things have changed since this was opened, I'm going to close this for now.  We can always come back to this with a test case in the future.

authors: gutmann kbnd

repo: NCAR/icar


text:
Fix Docker Volume Declarations

This pull request fixes an issue with the Docker volume declarations.
While most languages interpret the idom statement #comment correctly, Dockerfiles don't seem to allow this within volume declarations. This results in the unintended creation of the #, the, just etc. volumes for all running instances of this container (at least when built/run through podman).
To illustrate this issue, I've run podman inspect on the joai image, which yields:
"Volumes": {
  "#": {},
  "/joai/config": {},
  "/joai/data": {},
  "config": {},
  "harvested/provided": {},
  "just": {},
  "records": {},
  "the": {}
}

Thank You for providing and maintaining this project and best regards!

Resolves #12

repo: NCAR/joai-project


text:
Need to move Andy's documentation to an NCAS location

And move all the links in the various setup, readme, etc code.

Hi @bnlawrence, thanks for raising this. I agree! I was due to start compiling issues for cf-view (of which this would be one the first as most urgent) though I am still trying to work through some major work towards getting cf-plot in a state I'd feel comfortable developing on (e.g. code standards, modularisation and getting the docs hosted centrally via NCAS-CMS, likewise there). But I should show cf-view some love too at this stage!
Andy provided a tarball of cf-view docs, so I can start work on that next week (I'm at a workshop today until Thursday inclusive so not much time this week). Hope that timeline sounds OK.

authors: bnlawrence sadielbartholomew

repo: NCAS-CMS/cf-view


text:
Update dataone_format_mappings

Updates supported formats except for .mat and .raw files.
Partial update for #84.
Closes #29.

This looks good to me - why exclude .mat files though?

The .mat files can have different versions associated with them, like with netCDF files. They are not supported enough in R at the moment to easily determine the version.
The .raw format can be added as "image/x-raw", but there could be some cases where .raw does not represent an image file.

Makes sense. I'm going to merge this one. I also think issues #29 should be closed already. I think it already guesses the format for you (now it can guess better though!)

authors: drkrynstrng jeanetteclark

repo: NCEAS/arcticdatautils


text:
Allow user to remove geoposition in location

This PR resolves the following items ;
In the location editor, make the geo location an editable field
Make it possible to have a location with a null geo position
The current "drag-and-drop-only" way of placing a location is clumsy as it is very difficult to zoop out, find a new area, zoom in and place marker. When in edit mode, clicking on the map should do that.
UI changes :
New Lan and Lng text fields are added to page to make user able to enter coordinates manually.
New button added to page to delete current coordinate values.
Closes #2934
Related items are from #244 (3rd,4th and 5th item in the list)
With this update ;
-Now the users will be allowed to set geoposition null through a new clear button which is added to Location Editor (clear button is hidden by default , it is enabled when a valid coordinate is selected on map or entered manually) .
-Now users can enter coordinates manually in the Location Editor .
-Now a user can place a location with one click on map.

We have opened this new PR as Yusuf mentioned before .
Yusuf's briefing to Vassil was as follows :
due to poor commit messages and non isolated (large) commits, I would like to rewrite history on branch https://github.com/NCI-Agency/anet/tree/GH-2934-allow-to-remove-geoposition-in-location However, there is an already opened PR and i don't (and probably i shouldn't) want to do any rebase operation on existing branch. My idea is to delete the whole PR and branch and start over. it wouldn't take much time for me and i really want to get things done the way they are supposed to be.

repo: NCI-Agency/anet


text:
Add Mapping to Transcriptome

Add this command to STAR:
--quantMode TranscriptomeSAM

This will create an additional mapping to transcriptome coordinates.

Pull request created

completed with PR 9f594053d22d663eeca4dd87f439238478cc188d

authors: slsevilla wilfriedguiblet

repo: NCI-RBL/iCLIP


text:
🛑 liste.ndla.no is down

In a5ca16a, liste.ndla.no (https://liste.ndla.no) was down:

HTTP code: 0
Response time: 0 ms

Resolved: liste.ndla.no is back up in ab5d74c after 5 minutes.

repo: NDLANO/oppetid


text:
fix: send mail to submitter with details when project is published (WIP)

Fixes #513

The display of citation info in the mail is pending. write now the citation details is fetched making a ajax call in UI. need to discuss whether this detail could be saved to DB and also there are different formats of citations, how also this can be handled.
https://github.com/NFDI4Chem/nmrxiv/blob/email-submitter/resources/js/Shared/Citation.vue

Citation:
Get citations to your project in various formats  here


text:
[nz-menu] 文本内容溢出的时候没有变成省略号

在使用导航菜单[nz-menu]的时候内容溢出了，看着像是设置了flex的盒模型顶掉了block。

I'd like to close this issue because the v16.2.1 which contains this bugfix had been released.

authors: Laffery liulovegame

repo: NG-ZORRO/ng-zorro-antd


text:
Repeat + Random : enable choice of scope

Enable the choice of scope (flow scope, user scope, global scope).

Done

authors: Klervix TothiViseo

repo: NGRP/node-red-contrib-viseo


text:
3++ Infrastructure Requirements (NHS D - hosted instances)

NHSD Infrastructure is required to run NHSD hosted Mauro instances.
Expect 4 infrastructures required as follows:

UAT
Pre-Production
Production – Data Dictionary
Production – DD4C

Infrastructure to include secure access for authorised internal and external customers.

Expect to need (MVP)
dev
uat
data migration
DD/DD4C authoring
live (NHS D (incl DD))

other instances for external (funded) e.g NHS X

Requirements need elaborating further

NHS Digital hosted instances required for:

UAT: March 2021 onwards
Public (NHS D including DD and DD4C): March 2021 onwards
DD instance: solely for DD team (required once DMDS preparing for V3++ migration)
Dev: at the point where we are developing our own plug ins
HDRUK dedicated instance: for them to do their work on (needs confirmation of funding)

This is as requested by Maxine and Nicholas.

21/5/ - update from BC:  basically I want the requirement expressed as services rather than servers for this and that. Ultimately that is what we will have to provide and might not require a server at all for parts of it.

23/6 - update from BC:  Environments, approach and configuration established. Staff trained in their use. Awaiting Mauro.

22/12/21 - update from BC. Requirements demonstrated so issue closed.

authors: AngelaFaulding GSChandel maxChappell rajabr57

repo: NHSDigital/DataDictionaryPublication


text:
Add Bubble Sort in C

For short term contributors: we understand that getting your commits well
defined like we require is a hard task and takes some learning. If you
look to help without wanting to contribute long term there's no need
for you to learn this. Just drop us a message and we'll take care of brushing
up your stuff for merge!
Closes https://github.com/NITSkmOS/Algorithms/issues/19
By submitting this pull request I confirm I've read and complied with the
below declarations.

[x] I have read the Contribution guidelines and I am confident that my PR reflects them.
[x] I have followed the commit guidelines for this project.
[x] My code follows the standard code structure.
[x] This pull request has a descriptive title. For example, {Tag}: Add {Algorithm/DS name} [{Language}], not Update README.md or Added new code.
[x] This pull request will be closed if I fail to update it even once in a continuous time span of 7 days.
[x] This pull request shall only be reviewed and merged once all the checks passes. No maintainer or supporter shall be obliged to review it before this condition is met.
[x] I have mentioned the issue number correctly (with hyperlink) in this pull request description.

After you submit your pull request, DO NOT click the 'Update Branch' button.

Comment on 5d3041f1279fade890c985b055688764b0e927f6, file euclidean_gcd/C/euclidean_gcd.c, line 6.
Missing space before ( in while(  [whitespace/parens] [5]
Origin: CPPLintBear, Section: all.cpp.

ack 257c37e

repo: NITSkmOS/Algorithms


text:
Allow selecting shop-disabled countries in settings

Country::getCountries() doesn't return disabled countries in the shop, and makes them unselectable. This changes allows for that.

Ok, but pay attention to the fact that a country not only can be set as "inactive" but also "disabled" on a store, which IIRC removes it from the joining table.

I double checked, and if it is of any use to you, here's why I'll keep using my modified version:
We have two shops in a multishop environment, for two geographical markets. Multishop is a bit of a mess in PrestaShop, since some tables like product_shop have additional information per shop, while country_shop is a simple joining table where disassociating a country from a shop deletes it from that joining table. Setting a country as inactive changes the boolean flag on the country table, but that's something that lives for all shop.
Let's say I have shop A with Italy and shop B with France: they both have to be active, but they are each associated with either one of the two shops.
Country::getCountries() adds a join statement Shop::addSqlAssociation('country', 'c') that links tables country and country_shop. It does not return countries that are not associated with the current shop.

You are absolutely right! thanks for the commit 👍

authors: NKoonen mcdado

repo: NKoonen/vatchecker


text:
modifications of deployer support

I think we need several modifications of deployer (and download) support.

I don't think multiple deployers need to be chained as the output dictionary has already been processed well when it arrived at the deployer. I think that framework supports a single deployer is enough.
I'd like the single deployer gets an Option[Dictionary] as an input parameter and outputs a Seq[String] from process function.
Then framework transforms the Seq[String] to Array[Byte].
The series of procedures described above is started by framework when either Deploy or Download buttons is clicked.
If the user clicks Deploy button, framework transports the Array[Byte] to the registered server (Solr/ES). Otherwise (user clicks Download button), framework transports the Array[Byte] to web browser that the user is using.

I'll open some pull requests for each procedure.

Hi Yamamoto-san,
I've just pushed a branch framework_support_transfer_bytearry which includes a list of items described above except Download button stuff. Can you check it?

I'm going to merge this soon...


text:
Allow end date for logging rules

Hi
its easy to turn on trace level logging and forget to turn it off - resulting in massive log files or heavy disk usage
Suggestion would be add an end date or expiry date to the rule in nlog.config that would disable the rule past this date. Then we could specify for how long we wanted tracing to run for
e.g.
  <rules>
    <logger name="*" minlevel="Trace" writeTo="traceFile" endDate="12-Jan-2020 17:00:00" />
  </rules>

You can add a logging rule with a rulename. Then you can setup a timer to trigger after your own desired timeout that reverts loglevel to a proper level.
You can also make use of nlog-config-variables or nlog-gdc-item in the rule-filter-config (Those can also be reverted by a timer by your own desire):
https://github.com/nlog/NLog/wiki/Filtering-log-messages#semi-dynamic-routing-rules

I like the idea (had the exact same issue in the past)
But note sure if it fits in NLog. But if it does, then its a plus compared to other frameworks.

I like the idea (had the exact same issue in the past)
But note sure if it fits in NLog. But if it does, then its a plus compared to other frameworks.

Yep - back in the day I wrote something myself to do this - think it would be useful for nlog

Think it should be outside the core. In some extension logic.
Sent from my Sony Xperia
---- Blpowom wrote ----
I like the idea (had the exact same issue in the past)
But note sure if it fits in NLog. But if it does, then its a plus compared to other frameworks.
Yep - back in the day I wrote something myself to do this - think it would be useful for nlog
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/NLog/NLog/issues/3812?email_source=notifications&email_token=ACXZ7HBXSKRZF6ATLL7HD4LRD3AGZA5CNFSM4KYSYJTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMPOEMQ#issuecomment-589226546, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACXZ7HAAANZFFNSE6KJAFA3RD3AGZANCNFSM4KYSYJTA.

Closing due to inactivity

authors: 304NotModified Blpowom snakefoot

repo: NLog/NLog


text:
nwm_client_new: Minimum dask version 2021.11.1

Looks like sort_values is somewhat recent to dask, requiring a minimum version. This ticket is to update setup.cfg with a minimum dask[complete]>=2021.11.1.

Looks like this issue is outdated with recent versions and moving minimum support to python 3.8.

repo: NOAA-OWP/hydrotools


text:
Change minimum ngen.init_config python version >=3.7

ngen.cal and ngen.config both support 3.7. In introducing ngen.init_config I overlooked that minimum version and set it to >=3.8. This PR makes the necessary changes to bring that down to >=3.7 and changes the minimum supported version in the package metadata.
Changes

ngen.init_config's minimum supported python version >=3.7 from >=3.8

This should fix #49's failing tests once it is merged.

repo: NOAA-OWP/ngen-cal


text:
Scenario Editor: Expansions can be added multiple times

Description of Problem or Question
Expansion requirements can be added multiple times
Valkyrie Version
2.0.1

You will need to cater for RN / Cotw & FA if making exclusions.
Since adding these only add the variables #expansion = 1. Duplicates in this don't matter that much

repo: NPBruce/valkyrie


text:
ReOpt API “Get Size & Dispatch” Freezing SAM Software

I tried to size a Microgrid (both domestic and international) using SAM’s ReOpt API using the commercial solar+BESS module, and when I clicked on the Get size and dispatch button, SAM became unresponsive in both Mac and Windows environments. Anyone else notice this issue? I sized the critical load as a percentage of the actual load. Tried it for both a NM and international project. Got the same results = SAM froze up. It’s a great feature if it works, though.

This is the error message that came back after several minutes - just now seeing it. I’m using 5 min interval load data. Will the integration with ReOpt only work with 60 min (8760) time interval data?
“Could not evaluate callback function:call_reopt->on_change
[76]: error in call to 'reopt_size_battery()': Load profile must have 8760 entries.[61]: eval error in statement list”

Thanks for reporting the issue. The call to ReOpt indeed takes quite some time (~3-5 minutes).
From the reopt lite api, the load "must be hourly (8,760 samples), 30 minute (17,520 samples), or 15 minute (35,040 samples)." However, the SAM integration currently only allows hourly load profiles.
I will see if we can expand this to 30 and 15 minute data easily for the upcoming patch. Otherwise, we will fix this for the next release.

Very good. Thank you for the quick response. Yes, expanding the allowable time step interval data would be very helpful. Thank you.

I got the ReOpt API to work and recommend battery sizing, but it looks like it’s optimizing around fastest payback or NPV? Please confirm.
Also, Is there a way to optimize the battery sizing around the probability of surviving the outage by time? If not, is there a workaround to force SAM to solve for the latter?
Thanks, Brian

It optimizes for NPV.
The ReOpt Lite website allows you to optimize for resilience. I haven't seen any flag in the API that we're using that toggles between NPV vs resilience as the objective function. There is the option to provide resilience statistics (avg hrs survived, survival function etc). I will inquire with the ReOpt team.

That would be a great new feature, though: to let SAM pick the battery size (and solar PV size) based on probability of surviving an outage and then filter the results (in a parametric study) By NPV or savings or simple payback. Please document this feature request. Thanks!

authors: brianschmidly dguittet

repo: NREL/SAM


text:
Add support for inverters with more than 4 MPPT inputs

Some inverters on the market have more than four MPPT inputs, such as the SMA Sunny Tripower Core 1, which has six.
https://sam.nrel.gov/forum/forum-general/3388
Supporting more MPPT inputs requires supporting more than four subarrays, which would require redesigning the System Design input page to be more flexible and managing a larger number of input and output variables. Subarray inputs and outputs are currently implemented as single values, but it may make sense to implement them as arrays. For example, a single array to store the number of modules per string input or operating voltage output for each subarray instead of separate variables for each subarray.
See also:
https://github.com/NREL/SAM/issues/396
https://github.com/NREL/SAM/issues/215
https://sam.nrel.gov/forum/forum-general/2907

This would be a fantastic enhancement! The ultimate would be the option to add an arbitrary number of MPPTs but I realise this could be challenging.
We have found some scenarios where it is very helpful to calculate many MPPTs - even more than real hardware would allow. For example, when modelling optimizer/micro-inverter systems where there are multiple different panel orientations within individual strings/mppts, it is necessary to break the string into smaller groups and simulate each orientation as a separate MPPTs so the correct orientation can be specified (since each MPPT can only have a single orientation). This workaround allows all panels to use the correct orientation for generation calculations, whilst keeping them all under a single inverter so that inverter clipping is applied correctly.

@cpaulgilman @janinefreeman FYI, we have "published" an extension of the inverter model to multiple MPPT, which uses the CEC parameters to pvlib-python.  In my opinion this model has a stronger basis than what I think SAM does currently (average power and voltage over arrays to get single inputs to the Sandia inverter model). I intend to document the extended model once we've done some lab work to demonstrate it's validity.

Duplicate of https://github.com/NREL/SAM/issues/215

authors: cpaulgilman cwhanse python1981


text:
cannot find how to use template for request header

I tried to pass X-Api-Roles to the backend API (couchdb), but I could not figure out how to use a template to achieve this. In "Global Request" settings I entered:
X-Auth-CouchDB-Token: (mysecretttoken)
X-Auth-CouchDB-UserName: apiumbrella
X-Auth-CouchDB-Roles: {{X-Api-Roles}}
Content-Type: application/json; charset=utf-8
Accept: application/json

The value of X-Api-Roles is passed to the backend, but I would like to pass it as X-Auth-CouchDB-Roles. How can I achieve this?
tcpdump snippet showing request from API umbrella to API backend:
        0x0290:  330d 0a58 2d41 7069 2d55 7365 722d 4964  3..X-Api-User-Id
        0x02a0:  3a20 6531 6665 6632 3230 2d30 6166 642d  :.XXXXXXX-0afd-
        0x02b0:  3439 3062 2d61 3833 312d 3461 6639 6232  490b-a831-4af9b2
        0x02c0:  6630 3234 3963 0d0a 582d 4170 692d 526f  f0249c..X-Api-Ro
        0x02d0:  6c65 733a 2063 6f75 6368 2d62 652d 7465  les:.couch-xx-yy
        0x02e0:  616d 2d75 7365 7273 0d0a 582d 4175 7468  yy-users..X-Auth
        0x02f0:  2d43 6f75 6368 4442 2d54 6f6b 656e 3a20  -CouchDB-Token:.
        0x0300:  3533 3464 3132 3465 3366 6230 3063 6537  xxxxxxxxx
        0x0310:  3761 3139 6230 3236 3963 3166 6664 6131  7a19b0269c1ffda1
        0x0320:  3130 6661 6461 3136 0d0a 582d 4175 7468  10fada16..X-Auth
        0x0330:  2d43 6f75 6368 4442 2d55 7365 724e 616d  -CouchDB-UserNam
        0x0340:  653a 2061 7069 756d 6272 656c 6c61 0d0a  e:.apiumbrella..

Figured it out after looking at this pull request.
This did the trick: In "API Backends" under "Global Request Settings / Set Request Headers" I had to add
X-Auth-CouchDB-Roles: {{headers.x-api-roles}}
So, while my couchdb backend API is always accessed with one and the same proxy user (I named it apiumbrella, suprisingly), I can pass in roles specific to the API-key / API-user.
Is there a list of all headers supporting template-based rewriting, or can I just use any header translated to lower case?

repo: NREL/api-umbrella


text:
BLD: Added h5py and hdf5 for SWMR

Attn @ericdill
cc: @tacaswell @danielballan
This adds h5py and hdf5 libraries that work with SWMR. I have built and they work for me ok. Could you please have a look and if good merge, I need these packages on CSX. Thanks!

lgtm. thanks @stuwilkins

authors: ericdill stuwilkins

repo: NSLS-II/auto-build-tagged-recipes


text:
FIX: correct labels processing

Description

Motivation and Context

How Has This Been Tested?

That was hot-fixed at SMI.

Would like to experiment with the usability a little more before merging. Trying to get this working locally against a spoofed IOC....

Codecov Report

Merging #1037 into master will increase coverage by 0.01%.
The diff coverage is 87.5%.

@@            Coverage Diff             @@
##           master    #1037      +/-   ##
==========================================
+ Coverage   89.45%   89.46%   +0.01%
==========================================
  Files          50       50
  Lines        8371     8371
==========================================
+ Hits         7488     7489       +1
+ Misses        883      882       -1

Impacted Files
Coverage Δ

bluesky/magics.py
84.61% <87.5%> (+0.51%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 82fea20...23849da. Read the comment docs.

OK, I think this is a decent second pass. If this behavior seems sensible to you all, let's merge it and get a bug-fix release out. Future iterations may follow as we try to use it more in the wild.
Example configuration:
from ophyd import EpicsMotor, Device, Signal, Component
mtr = EpicsMotor('', name='mtr', labels={'motors'})
from bluesky.magics import BlueskyMagics
get_ipython().register_magics(BlueskyMagics)

class Thing(Device):
    a = Component(EpicsMotor, '')
    b = Component(EpicsMotor, '')

class ThingHaver(Device):
    tA = Component(Thing)
    tB = Component(Thing, labels={'favorites'})

th = ThingHaver(name='th', labels={'motors', 'things'})
s = Signal(name='s', labels={'motors', 'favorites', 'stuff'})

Output:
In [2]: %wa
motors
  Positioner                     Value       Low Limit   High Limit  Offset
  mtr                            0           0           0           0
  th_tA_a                        0           0           0           0
  th_tA_b                        0           0           0           0
  th_tB_a                        0           0           0           0
  th_tB_b                        0           0           0           0

  Local variable name                    Ophyd name (to be recorded as metadata)
  mtr                                    mtr
  th                                     th
  s                                      s

things
  Positioner                     Value       Low Limit   High Limit  Offset
  th_tA_a                        0           0           0           0
  th_tA_b                        0           0           0           0
  th_tB_a                        0           0           0           0
  th_tB_b                        0           0           0           0

  Local variable name                    Ophyd name (to be recorded as metadata)
  th                                     th

favorites
  Positioner                     Value       Low Limit   High Limit  Offset
  th_tB_a                        0           0           0           0
  th_tB_b                        0           0           0           0

  Local variable name                    Ophyd name (to be recorded as metadata)
  th.tB                                  th_tB
  s                                      s

stuff
  Local variable name                    Ophyd name (to be recorded as metadata)
  s                                      s

I like the updates.

Closes #828 only 9 months late. Sorry for the long wait on that, @afluerasu and @ambarb.

Self-merged with @tacaswell and @mrakitin's blessing via Slack. Moving on to tag a micro release....

authors: codecov-io danielballan mrakitin

repo: NSLS-II/bluesky


text:
Fix issue due to Conda-forge

also corrected sha256 number, and remove unused tests.

Now conda auto-build is back again after a quick fix.

Thanks for checking on this. Here is the error info
latest: Pulling from nsls2/debian-with-miniconda
Digest: sha256:362eb464ac1e3f283378dbce0384d1e37328cfdf64f7cc4da9307f55a7d1d1d7
Status: Image is up to date for nsls2/debian-with-miniconda:latest
Running the docker container
CONDARC_PATH=/root/.condarc
Exporting CONDARC=/root/.condarc
showing conda info
Current conda install:

             platform : linux-64
        conda version : 4.0.5
  conda-build version : not installed
       python version : 3.5.1.final.0
     requests version : 2.9.1
     root environment : /conda  (writable)
  default environment : /conda
     envs directories : /conda/envs
        package cache : /conda/pkgs
         channel URLs : https://conda.anaconda.org/lightsource2-tag/linux-64/
                        https://conda.anaconda.org/lightsource2-tag/noarch/
                        https://conda.anaconda.org/conda-forge/linux-64/
                        https://conda.anaconda.org/conda-forge/noarch/
                        https://repo.continuum.io/pkgs/free/linux-64/
                        https://repo.continuum.io/pkgs/free/noarch/
                        https://repo.continuum.io/pkgs/pro/linux-64/
                        https://repo.continuum.io/pkgs/pro/noarch/
          config file : /root/.condarc
    is foreign system : False

contents of condarc at /root/.condarc
binstar_upload: false
always_yes: true
show_channel_urls: true
channels:
- lightsource2-tag
- conda-forge
- defaults
Fetching package metadata: ........
Solving package specifications: .........

Package plan for installation in environment /conda:

The following packages will be downloaded:

    package                    |            build
    ---------------------------|-----------------
    ncurses-5.9                |                9         954 KB  conda-forge
    patchelf-0.9               |                1         349 KB  conda-forge
    sqlite-3.13.0              |                0         4.9 MB  conda-forge
    xz-5.2.2                   |                0         853 KB  conda-forge
    python-3.5.2               |                3        31.8 MB  conda-forge
    conda-env-2.5.1            |           py35_0          27 KB  defaults
    markupsafe-0.23            |           py35_2          32 KB  defaults
    psutil-4.3.1               |           py35_0         228 KB  defaults
    pytz-2016.6.1              |           py35_0         162 KB  conda-forge
    ruamel_yaml-0.11.14        |           py35_0         377 KB  defaults
    six-1.10.0                 |           py35_0          18 KB  conda-forge
    clyent-1.2.2               |           py35_0          15 KB  defaults
    conda-4.1.12               |           py35_0         204 KB  defaults
    jinja2-2.8                 |           py35_1         278 KB  conda-forge
    python-dateutil-2.5.3      |           py35_0         237 KB  conda-forge
    anaconda-client-1.4.0      |           py35_0         101 KB  defaults
    conda-build-1.21.3         |           py35_0         238 KB  defaults
    conda-execute-0.6.0        |           py35_0          14 KB  conda-forge
    ------------------------------------------------------------
                                           Total:        40.7 MB

The following NEW packages will be INSTALLED:

    anaconda-client: 1.4.0-py35_0    defaults
    clyent:          1.2.2-py35_0    defaults
    conda-build:     1.21.3-py35_0   defaults
    conda-execute:   0.6.0-py35_0    conda-forge
    jinja2:          2.8-py35_1      conda-forge
    markupsafe:      0.23-py35_2     defaults
    ncurses:         5.9-9           conda-forge
    patchelf:        0.9-1           conda-forge
    psutil:          4.3.1-py35_0    defaults
    python-dateutil: 2.5.3-py35_0    conda-forge
    pytz:            2016.6.1-py35_0 conda-forge
    ruamel_yaml:     0.11.14-py35_0  defaults
    six:             1.10.0-py35_0   conda-forge

The following packages will be UPDATED:

    conda:           4.0.5-py35_0 defaults    --> 4.1.12-py35_0   defaults
    conda-env:       2.4.5-py35_0 defaults    --> 2.5.1-py35_0    defaults
    python:          3.5.1-0      conda-forge --> 3.5.2-3         conda-forge
    sqlite:          3.9.2-0      conda-forge --> 3.13.0-0        conda-forge
    xz:              5.0.5-1      conda-forge --> 5.2.2-0         conda-forge

...

   Building: linux-64/metadataclient-0.1.1-py34_0.tar.bz2
Build cmd: conda build /repo/recipes-tag/metadataclient --python 3.4 --numpy 1.11
BUILD START: metadataclient-0.1.1-py34_0
    (actual version deferred until further download or env creation)
updating index in: /conda/tmp_envs/55fc582f7dd397d3a5f0/pkgs
updating index in: /conda/tmp_envs/55fc582f7dd397d3a5f0/conda-bld/linux-64
updating index in: /conda/tmp_envs/55fc582f7dd397d3a5f0/conda-bld/noarch

The following packages will be downloaded:

    package                    |            build
    ---------------------------|-----------------
    ca-certificates-2016.8.31  |                0         163 KB  conda-forge
    ncurses-5.9                |                9         954 KB  conda-forge
    sqlite-3.13.0              |                1         4.9 MB  conda-forge
    tk-8.5.19                  |                0         1.9 MB  conda-forge
    xz-5.2.2                   |                0         853 KB  conda-forge
    zlib-1.2.8                 |                3          87 KB  conda-forge
    openssl-1.0.2h             |                2         3.4 MB  conda-forge
    readline-6.2               |                0         713 KB  conda-forge
    python-3.4.5               |                2        26.9 MB  conda-forge
    certifi-2016.8.31          |           py34_0         220 KB  conda-forge
    setuptools-26.1.1          |           py34_0         354 KB  conda-forge
    wheel-0.29.0               |           py34_0          82 KB  conda-forge
    pip-8.1.2                  |           py34_0         1.6 MB  conda-forge
    ------------------------------------------------------------
                                           Total:        42.0 MB

The following NEW packages will be INSTALLED:

    ca-certificates: 2016.8.31-0      conda-forge
    certifi:         2016.8.31-py34_0 conda-forge
    ncurses:         5.9-9            conda-forge
    openssl:         1.0.2h-2         conda-forge
    pip:             8.1.2-py34_0     conda-forge
    python:          3.4.5-2          conda-forge
    readline:        6.2-0            conda-forge
                                                                                824,0-1       19%

os.uname(): posix.uname_result(sysname='Linux', nodename='763b6f905bd2', release='3.19.0-59-generic', version='#65-Ubuntu SMP Mon Apr 18 16:12:07 UTC 2016', machine='x86_64')

sys.version: 3.5.2 | packaged by conda-forge | (default, Sep  8 2016, 14:23:11)
[GCC 4.8.2 20140120 (Red Hat 4.8.2-15)]

log file: /root/auto-build-logs/09.12-02.51
Building: linux-64/metadataclient-0.1.1-py34_0.tar.bz2
Build cmd: conda build /repo/recipes-tag/metadataclient --python 3.4 --numpy 1.11
BUILD START: metadataclient-0.1.1-py34_0
    (actual version deferred until further download or env creation)
updating index in: /conda/tmp_envs/55fc582f7dd397d3a5f0/pkgs
updating index in: /conda/tmp_envs/55fc582f7dd397d3a5f0/conda-bld/linux-64
updating index in: /conda/tmp_envs/55fc582f7dd397d3a5f0/conda-bld/noarch

The following packages will be downloaded:

    package                    |            build
    ---------------------------|-----------------
    ca-certificates-2016.8.31  |                0         163 KB  conda-forge
    ncurses-5.9                |                9         954 KB  conda-forge
    sqlite-3.13.0              |                1         4.9 MB  conda-forge
    tk-8.5.19                  |                0         1.9 MB  conda-forge
    xz-5.2.2                   |                0         853 KB  conda-forge
    zlib-1.2.8                 |                3          87 KB  conda-forge
    openssl-1.0.2h             |                2         3.4 MB  conda-forge
    readline-6.2               |                0         713 KB  conda-forge
    python-3.4.5               |                2        26.9 MB  conda-forge
    certifi-2016.8.31          |           py34_0         220 KB  conda-forge
    setuptools-26.1.1          |           py34_0         354 KB  conda-forge
    wheel-0.29.0               |           py34_0          82 KB  conda-forge
    pip-8.1.2                  |           py34_0         1.6 MB  conda-forge
    ------------------------------------------------------------
                                           Total:        42.0 MB

The following NEW packages will be INSTALLED:

    ca-certificates: 2016.8.31-0      conda-forge
    certifi:         2016.8.31-py34_0 conda-forge
    ncurses:         5.9-9            conda-forge
    openssl:         1.0.2h-2         conda-forge
    pip:             8.1.2-py34_0     conda-forge
    python:          3.4.5-2          conda-forge
    readline:        6.2-0            conda-forge
    setuptools:      26.1.1-py34_0    conda-forge
    sqlite:          3.13.0-1         conda-forge
    tk:              8.5.19-0         conda-forge
    wheel:           0.29.0-py34_0    conda-forge
                                                                                824,0-1       19%
    certifi:         2016.8.31-py34_0 conda-forge
    ncurses:         5.9-9            conda-forge
    openssl:         1.0.2h-2         conda-forge
    pip:             8.1.2-py34_0     conda-forge
    python:          3.4.5-2          conda-forge
    readline:        6.2-0            conda-forge
    setuptools:      26.1.1-py34_0    conda-forge
    sqlite:          3.13.0-1         conda-forge
    tk:              8.5.19-0         conda-forge
    wheel:           0.29.0-py34_0    conda-forge
    xz:              5.2.2-0          conda-forge
    zlib:            1.2.8-3          conda-forge

========== STDOUT ==========

None

========== STDERR ==========

('Using Anaconda API: https://api.anaconda.org\n'
 'WARNING:/conda/tmp_envs/55fc582f7dd397d3a5f0/lib/python3.5/site-packages/conda_build/build.py:Build '
 'prefix failed with prefix length 255\n'
 'WARNING:/conda/tmp_envs/55fc582f7dd397d3a5f0/lib/python3.5/site-packages/conda_build/build.py:Error '
 'was: \n'
 'WARNING:/conda/tmp_envs/55fc582f7dd397d3a5f0/lib/python3.5/site-packages/conda_build/build.py:ERROR: '
 'placeholder '
 "'/opt/conda/envs/_build_placehold_placehold_placehold_placehold_placehold_placeho' "
 'too short in: conda-forge::ncurses-5.9-9\n'
 '\n'
 'WARNING:/conda/tmp_envs/55fc582f7dd397d3a5f0/lib/python3.5/site-packages/conda_build/build.py:One '
 'or more of your package dependencies needs to be rebuilt with a longer '
 'prefix length.\n'
 'WARNING:/conda/tmp_envs/55fc582f7dd397d3a5f0/lib/python3.5/site-packages/conda_build/build.py:Falling '
 'back to legacy prefix length of 80 characters.\n'
 'WARNING:/conda/tmp_envs/55fc582f7dd397d3a5f0/lib/python3.5/site-packages/conda_build/build.py:Your '
 'package will not install into prefixes > 80 characters.\n'
 'ERROR: placeholder '
 "'/opt/conda/envs/_build_placehold_placehold_placehold_placehold_placehold_placeho' "
 'too short in: conda-forge::ncurses-5.9-9\n'
 '\n')
Sending the following message to slack

It looks that the issue has been resolved by conda team. We can move conda-forge in front of defaults now.

I think that problem was coming from the conda 4.0.x binaries. Updating conda to 4.1.x or 4.2.x might fix it.

Also there is a tremendously long issue where it is being discussed how to handle the change in the prefix length: https://github.com/conda-forge/conda-forge.github.io/issues/171#issuecomment-248400560

I was using conda 4.1.2, but still got the error. I think the issue came from pytz and sqlite, which need to be installed from default, instead of conda-forge, according to conda-forge team.
However, those two packages have been fixed for now at conda-forge. Thanks for the follow up!

authors: ericdill licode


text:
Fix signatures of configure/deconfigure; add 'state' property.

The signature changes are noncontroversial. Someone read them to make sure I didn't miss something?
I called the new property 'state'. I am not attached to that name.@klauer expressed some minor reservations about 'report' because it could be a verb or a noun -- hard to guess if it's a method or a property.
Whatever we choose let's get this merged soon so the framework is in place and tested in time for beam. We can add actual content to state pretty safely as we go.

@dchabot If you are still OK with this, as discussed this morning, please merge. Thanks.

repo: NSLS-II/ophyd


text:
calibration url distortion type detection issue

currently, we are using rasberry pi IMX477 camera module equipped with 3.9mm F2.8 lens equipped. The exact product is https://vctec.co.kr/product/detail.html?product_no=17791&cate_no=145
because it didn't publish camerainfo by its own driver, we have made calibration yaml & ini files, to publish camerainfo. while proceeding, we met the error
yaml-cpp: bad conversion in line 4~
so we decided to use ini file, and we found out that the node arguscamera sees the url and gets the calibration data
but we got calibration data as 'plumb_bob' distortion model, but if we echo the camerainfo publishing, it shows that distortion type is 'rational_polynomial', resulting in 3 more garbage data in the distortion parameter in the message
so we tried to put
camera_info_->distortion_model = "plumb_bob"
in between line 86 & 87 in 'argus_camera_mono_node.cpp', but it doesn't change the output message's distortion_model
how can we make the node to recognize the distortion model as 'plumb_bob'?
we are using the same container you've uploaded in the tutorial, and using Jetson Xavier NX, and tried to update/lower the version of yaml-cpp, but it didn't resolve the problem related in yaml file..
we upload the zip file containing the yaml and ini file for your support.
camera_infos.zip

Thank you for reporting this issue. We are looking into it and will keep you updated.

Hi @chengu1000 - we've just merged #23 that we think will fix your bug. Could you try pulling the latest and see if this works for you?


text:
[Paddle] Debug wheel test

Description
We have experienced test failures in the PaddlePaddle test for building Python wheels because the base container has installed python3-wheel with APT. This causes problems when we try installing the correct wheel version with Pip. This PR works around this issue by installing wheel locally.
Type of change

[ ] Documentation change (change only to the documentation, either a fix or a new content)
[x] 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)
[ ] Infra/Build change
[ ] Code refractor
[x] Testing

Changes

Install wheel locally in PaddlePaddle test for building Python wheels

Checklist:

[x] I have read and followed the contributing guidelines
[x] The functionality is complete
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

/te-ci paddle

/te-ci paddle

repo: NVIDIA/TransformerEngine


text:
Better way of checking cuDNN version

The CUDNN_VERSION env variable is specific to the NGC containers. This PR adds the API for the pyTorch extension to check the cuDNN version that is available (based on the loaded libcudnn*.so library).

/te-ci pytorch


text:
docs: general improvements

Made some general improvements to the markdown documentation syntax as well as correct some small spelling errors.

Thanks for the PR, but there're some other updates needed as well. Fixed
Closing this

authors: angudadevops beholdenkey

repo: NVIDIA/cloud-native-stack


text:
Update README.md

had to modify to the chart arg to work .
This is error i was getting with the command in the documentation:
azureuser@azeltov-linux:~$ helm upgrade
--install
--username '$oauthtoken'
--password "${NGC_API_KEY}"
-n ${NAMESPACE}
nv-ingest
--set imagePullSecret.create=true
--set imagePullSecret.password="${NGC_API_KEY}"
--set ngcSecret.create=true
--set ngcSecret.password="${NGC_API_KEY}"
--set image.repository="nvcr.io/ohlfw0olaadg/ea-participants/nv-ingest"
--set image.tag="24.10"
https://helm.ngc.nvidia.com/ohlfw0olaadg/ea-participants/charts/nv-ingest-0.3.8.tgz
Error: "helm upgrade" requires 2 arguments
Usage:  helm upgrade [RELEASE] [CHART] [flags]
Description

Checklist

[ ] I am familiar with the Contributing Guidelines.
[ ] New or existing tests cover these changes.
[ ] The documentation is up to date with these changes.

@azeltov I'm going to close this and move it to the https://github.com/NVIDIA/nv-ingest/pull/256 PR so I can get it into the 24.12 release. Thanks for updating this!

repo: NVIDIA/nv-ingest


text:
Update to new cudf strings where character data is no longer a child column

Fixes the submodule sync error reported in #1706.  This updates to the changes in rapidsai/cudf#14202 where the strings column has the character data stored in a device buffer rather than a child column.

build

build

repo: NVIDIA/spark-rapids-jni


text:
[submodule-sync] bot-submodule-sync-branch-24.08 to branch-24.08 [skip ci] [bot]

submodule-sync to create a PR keeping thirdparty/cudf up-to-date.
HEAD commit SHA: 9a70685f72f50077c34bb46148888129da23e278, cudf commit SHA: https://github.com/rapidsai/cudf/commit/a583c97ca977041e3cc3399739e29962982d6aad
This PR will be auto-merged if test passed. If failed, it will remain open until test pass or manually fix.

HEAD commit SHA: 9a70685f72f50077c34bb46148888129da23e278, CUDF commit SHA: https://github.com/rapidsai/cudf/commit/a583c97ca977041e3cc3399739e29962982d6aad
Test passed: True

SUCCESS - auto-merge


text:
[FEA] Optimize the all-true and all-false cases in GPU If and CaseWhen

We have the cases where the prediction produces all true or all false in a batch when running GpuCaseWhen  and GpuIf with the row-based UDF, which is an expensive operation. We can indeed skip the execution of the row-based UDF for such case to improve the performance.

Should be addressed by  https://github.com/NVIDIA/spark-rapids/pull/4383/

repo: NVIDIA/spark-rapids


text:
[FEA] Update spark2 code for 22.08

Is your feature request related to a problem? Please describe.
we need to update the spark2 code to pull in all the changes in 22.08. We should do this in burndown once most things are merged.

Pr is up but we should make another final pass once all features are committed

Pr is merged and update to date as of now we can rerun if anything else goes in and decide if we want to update.

closing this as decided not to update the spark2 code anymore for 22.08, majority of changes went in with previous pull request


text:
Add query number to Spark app name when running benchmarks

Signed-off-by: Andy Grove andygrove@nvidia.com
When viewing Spark event logs in history server from a benchmark suite run, every app currently has the same name, such as "TPC-DS Like Bench" which isn't very helpful.
This PR simply adds the query name to the app name. For example: "TPC-DS Lilke Bench q5".

build

authors: andygrove jlowe


text:
Lstm nativ

re-merged my changes with last version of GA3C
current results (by setting Config.USE_RNN to False, True, & True + summing lstm_state & cnn_state as a residual connection)
we can see lstm is not so helpful in Pong Case, as the problem is for most part completely observable

...better later than ever

I don't think so that lstm isn't helpful for Pong (wrt my experiments with vanilla a3c), but if you follow with some straightforward way you can't see some improvements. For example: use the same stacked state with small internal update loop.
It's better to increase this loop at least for 20 steps and do not try to stack images or you can stack them and therefore you can a bit decrease this loop.
So... I don't inspect code too much >> it should be TIME_MAX = 5

@4SkyNet : ok will try with TIME_MAX=20.
Do you if standard nn regularization techniques (weight decay, dropout, batchnorm) can affect convergence and/ or performance?

following results on Pong :

@etienne87 I don't experiment with them in a3c context, but I know that ddpg uses batchnorm for improvements.
and also thx for experiments >> lstm_20 starting earlier but then behave not so steepest as old on 'ff'
...I don't really know, but it could be if you still stack the images
...you can also try elu instead of relu I think

i close this attempt as something is not right with my code.


text:
Static Maps linked to incorrect file

Land Use maps link to basempas
Basemap links to Land Use map
(keep Land Use on top and Basemap on bottom if possible)

@chriswhong just wanted to flag this from yesterday.

Resolved with PR #406

repo: NYCPlanning/labs-community-portal


text:
Discuss how we should react when availability API is down.

When SCSB's availability API is down or times out...we have a few options.
We can:

"null out" availability info in our response.
Trust the last availability information we got from ElasticSearch
Mark items we know to be dubious as possibly out of date and signal that in the UI.

This may be out of scope for this release but I wanted to record the conversation here.
CCing: @natalietsch, @nonword, @kfriedman, @jobinthomasnypl

This is in Jira here: https://jira.nypl.org/browse/SRCH-39

repo: NYPL-discovery/discovery-api


text:
DSD-1027: Header Refactoring 2 (Styles)

Fixes JIRA ticket DSD-1027
This PR does the following:

Furthers refactors the Header component and its styles. This PR mostly focuses on polishing the look.
This should also fix a few things from PR #1047
Out of scope for this ticket but will work on soon:

Working on pressing the "ESC" key to close dropdowns.
Context state management for the patron data.
Updated interfaces.

How has this been tested?
Locally in Storybook.
Mobile
The production Header is on the left side. The Reservoir Header component is on the right side.
Regular

Login Menu is open

Search Menu is open

Mobile Navigation is open

Patron is signed in

Patron is signed in and login menu is open

Desktop
The production header is on the top. The Reservoir Header component is on the bottom.
Regular

Login Menu is open

Search Menu is open

Patron is signed in and login menu is open

Accessibility concerns or updates

N/A

Checklist:

[ ] I have updated the Storybook documentation accordingly.
[ ] I have added relevant accessibility documentation for this pull request.
[ ] All new and existing tests passed.

Front End Review:

[ ] Review the Vercel preview deployment once it is ready.

There are some parts that are a few pixels off but it's too tedious to get to match 100% and I don't think we should bother; they're unnoticeable.

Your pull request is missing a changelog—was that intentional?

Yes, this is a refactor and nothing new is added.

repo: NYPL/nypl-design-system


text:
Adding Egypt to the IBAN registry

IBAN has been available in Egypt since Nov 2020. This adds Egypt to our IBAN registry along with the BBAN structure.
see PR: https://github.com/arturmkrtchyan/iban4j/pull/85

added


text:
Doesn't work in Microsoft Edge

It shows a gray question mark sign in the icon. Logging out of Facebook then logging back in doesn't seem to fix the issue. In Chrome and Vivaldi works well. Please fix it.

Hello, it should be fixed in the next release (Pending review).

Related to #35.

The Edge version of the extension is now available at https://microsoftedge.microsoft.com/addons/detail/fnotifier/jkpbopolkbhegaabkoljoofcfingihlp.

repo: Narno/F-Notifier


text:
docs: update read_key() filepath -> filename

Documentation provides old reak_key() filepath argument. New argument is  filename:
https://github.com/Nasdaq/data-link-python/blob/86c5665ba67b5e67e1e2fe6204b361f14c0a6cb8/nasdaqdatalink/api_config.py#L100-L104

Nice catch; Thanks.  Will place this in an integration branch and will get merged in a future release.

authors: couture-ql dimitryzub

repo: Nasdaq/data-link-python


text:
MUU-370: As requested the 008 field base value contains current year

The value of year is set to 008 field automatically so it wont be needed to update again once the year changes.

Tässä olisi hyvä eksplisiittisesti pakottaa kentän mitta neljään merkkiin, jotta ei vahingossakaan pääse tapahtumaan sellaista, että vuoden lisäys sotkee kentän formaatin.
createBaseRecord() funktion tarkoituksena on ollut antaa myöten sille, että base record voidaan parametrisoida - toisin sanoen, esimerkiksi juuri näihin kiinteämittaisiin kenttiin tulevat tiedot (vuosi, formaatti, kieli yms) voisi lähettää funktiolle parametrina.
Siksi itse muuttaisin toteutusta vähän, sillä tavalla, että ottaisin vuoden muuttujaan ja pakottaisin sen neljän merkin mittaiseksi. Sitten myöhemmin vuosi voidaan lähettää myös parametrina (ja jos on tyhjä, käytetään oletusta eli kuluvaa vuotta).

authors: natlibfi-kmskuusi natlibfi-koskimim

repo: NatLibFi/melinda-ui-rest-api


text:
Shoot

and this package looks interesting. Too bad I can't use it v_v

have you considered a name change?

Haha, I just might have to since it's not for Kevin

authors: bwiklund kevinkhill

repo: NateFerrero/nginxify


text:
Android x86 support

x86 Android can use the UEFI as long as it's running on a device that supports it, x86 Novusk could be used as a kernel for Android running on Android boxes.
Things that would be needed:

[x] Documentation
[x] Mouse support
[x] Keyboard support
[x] Start Android OS

3e1cb13 Added documentation for Android development.

ca1818c closed keyboard support issue.

21bdddc Added x86_64 ps2 mouse driver.

3e1cb13 added documentation explaining how to start Android with Novusk


text:
Error after installed web pack

I've installed web pack on my project and then i'm getting the following error.
ERROR in ./modules/pack.address/pack.address.component.ts
Module not found: Error: Can't resolve 'nativescript-directions' in 'C:\dev\fm-transportes\src\FM.Transportes\app\modules\pack.address'
@ ./modules/pack.address/pack.address.component.ts 13:17-51
@ ./app.module.ts
@ ./main.ts
database.service.ts
const Sqlite = require("nativescript-sqlite");

const dbName = "fm.db";
import { Package, Pack, Order, Address, Reason, PackageSummary, PackStatus, Checkout } from "../";

export class DatabaseService {
  constructor() {
    this.Setup();
  }

Is the nativescript-directions plugin compatible ?
I also opened an issue on the web pack page
#https://github.com/NativeScript/nativescript-dev-webpack/issues/81

NativeScript-directions is a totally different plugin.   This plugin does NOT need it nor reference it.    So I'm not sure why you are asking about it here.

sorry, i past wrong code. I'm with error with
sqlite still as you can see below:
ERROR in ./modules/shared/services/database.service.ts
Module not found: Error: Can't resolve 'nativescript-sqlite' in 'C:\dev\fm-transportes\src\FM.Transportes\app\modules\shared\services'
 @ ./modules/shared/services/database.service.ts 1:13-43
 @ ./modules/shared/index.ts
 @ ./app.module.ts
 @ ./main.ts

authors: NathanaelA dzfweb

repo: NathanaelA/nativescript-sqlite