text:
seems read-only mode :(

Describe the bug
Until a few days ago, everything was working perfectly with the Eufy integration. Now, when I try to modify any entity, it reverts back to its previous state after a few seconds without staying set. It seems as if all entities are in read-only mode.
To reproduce
Steps to reproduce the behavior:

Go to 'a camera, activate o toggle whatever button, wait few seconds  you see goes back to previous  + the PUSH doesn't works neither '

Additional information
Go to Settings -> System -> Repairs -> Click on 3 dots (...) -> System Information and get Version and Installation Type to below fields;
Versione	core-2023.11.2
Tipo di installazione	Home Assistant OS
Sviluppo	false
Supervisor	true
Docker	true
Utente	root
Ambiente virtuale	false
Versione Python	3.11.6
Eufy Security Add-on (1.3.0)
eufy-security-ws (1.7.1)
Hardware Information;

Camera Model: EufyCam 2c

Debug Logs from Home Assistant (https://github.com/fuatakgun/eufy_security/discussions/624) - Without this, I will automatically resolve this issue

2023-11-15 17:17:48.395 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] _on_message - {'type': 'event', 'event': {'source': 'station', 'event': 'connected', 'serialNumber': 'T81XXXXXXXXXXXXX1'}}
2023-11-15 17:17:48.711 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] _on_message - {'type': 'event', 'event': {'source': 'device', 'event': 'property changed', 'serialNumber': 'T81XXXXXXXXXXXXX1', 'name': 'enabled', 'value': False}}
2023-11-15 17:17:48.711 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] camera _handle_property_changed - enabled
2023-11-15 17:17:48.741 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] _on_message - {'type': 'event', 'event': {'source': 'device', 'event': 'command result', 'serialNumber': 'T81XXXXXXXXXXXXX1', 'command': 'set_property', 'returnCode': 0, 'returnCodeName': 'ERROR_PPCS_SUCCESSFUL', 'customData': {'property': {'name': 'enabled', 'value': False}}}}
2023-11-15 17:17:49.714 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] _on_message - {'type': 'event', 'event': {'source': 'device', 'event': 'property changed', 'serialNumber': 'T81XXXXXXXXXXXXX1', 'name': 'batteryTemperature', 'value': 10}}
2023-11-15 17:17:49.715 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] camera _handle_property_changed - batteryTemperature
2023-11-15 17:17:49.737 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] _on_message - {'type': 'event', 'event': {'source': 'device', 'event': 'property changed', 'serialNumber': 'T81XXXXXXXXXXXXX1', 'name': 'wifiRssi', 'value': -58}}
2023-11-15 17:17:49.738 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] camera _handle_property_changed - wifiRssi
[..]
Traceback (most recent call last):
[...]
2023-11-15 17:17:52.195 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] domain - device - EventSourceType.product - device.set_property - {'domain': 'device', 'serial_no': 'T81XXXXXXXXXXXXX1', 'name': 'enabled', 'value': True} - {'name': 'enabled', 'value': True, 'serialNumber': 'T81XXXXXXXXXXXXX1'}
2023-11-15 17:17:52.195 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] {'name': 'enabled', 'value': True, 'serialNumber': 'T81XXXXXXXXXXXXX1', 'command': 'device.set_property', 'messageId': 'device.set_property.97xxxxxxxxxxxxxxxxxxxxxxxxxxx6d4'}
2023-11-15 17:17:52.195 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] send_message - {'name': 'enabled', 'value': True, 'serialNumber': 'T81XXXXXXXXXXXXX1', 'command': 'device.set_property', 'messageId': 'device.set_property.97xxxxxxxxxxxxxxxxxxxxxxxxxxx6d4'}
2023-11-15 17:17:52.215 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] _on_message - {'type': 'result', 'success': True, 'messageId': 'device.set_property.97xxxxxxxxxxxxxxxxxxxxxxxxxxx6d4', 'result': {'async': True}}
2023-11-15 17:17:52.685 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] _on_message - {'type': 'event', 'event': {'source': 'device', 'event': 'property changed', 'serialNumber': 'T81XXXXXXXXXXXXX1', 'name': 'enabled', 'value': True}}
2023-11-15 17:17:52.686 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] camera _handle_property_changed - enabled
2023-11-15 17:17:52.709 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] _on_message - {'type': 'event', 'event': {'source': 'device', 'event': 'command result', 'serialNumber': 'T81XXXXXXXXXXXXX1', 'command': 'set_property', 'returnCode': 0, 'returnCodeName': 'ERROR_PPCS_SUCCESSFUL', 'customData': {'property': {'name': 'enabled', 'value': True}}}}
2023-11-15 17:17:52.904 ERROR (MainThread) [custom_components.tapo_control] [initOnvifEvents] Initiating onvif connection failed.
2023-11-15 17:17:52.904 ERROR (MainThread) [custom_components.tapo_control] Authority failure
2023-11-15 17:18:00.371 DEBUG (MainThread) [custom_components.eufy_security] image 1 - False - None
2023-11-15 17:18:00.372 DEBUG (MainThread) [custom_components.eufy_security] async_camera_image 5 - is_empty False
2023-11-15 17:18:00.372 DEBUG (MainThread) [custom_components.eufy_security] async_camera_image 6 - 21189
[...]
2023-11-15 17:18:03.125 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] _on_message - {'type': 'result', 'success': True, 'messageId': 'device.set_property.8d4xxxxxxxxxxxxxxxxxxxxxxxxxx575', 'result': {'async': True}}
2023-11-15 17:18:03.832 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] _on_message - {'type': 'event', 'event': {'source': 'device', 'event': 'property changed', 'serialNumber': 'T81XXXXXXXXXXXXX1', 'name': 'wifiRssi', 'value': -60}}
2023-11-15 17:18:03.833 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] camera _handle_property_changed - wifiRssi
2023-11-15 17:18:14.040 ERROR (MainThread) [custom_components.tapo_control] [initOnvifEvents] Initiating onvif connection failed.
2023-11-15 17:18:14.041 ERROR (MainThread) [custom_components.tapo_control] Authority failure
2023-11-15 17:18:18.885 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] _on_message - {'type': 'event', 'event': {'source': 'device', 'event': 'property changed', 'serialNumber': 'T81XXXXXXXXXXXXX1', 'name': 'wifiRssi', 'value': -57}}
2023-11-15 17:18:18.885 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] camera _handle_property_changed - wifiRssi

Logs from Eufy Security Add-on (either from Add-ons page of Home Assistant or Docker output):

Sometimes add-on losing connection to devices and restarting it might mitigate it.
If it solves for you, I do not have another solution in my hand

thanks for watching this .
I'll test

Same issue over here... Everything is readonly. Restart won't give a solution.

Same issue over here... Everything is readonly. Restart won't give a solution.

I switched off the two factor authentication in the eufy app / control center. Rebooted the eufy addon in HA en suddenly it works again.

thank for advices . it helps

authors: derksendd frank777777 fuatakgun


text:
[BUG] CROSS Join fails for SparkExecutionEgnine

Minimal Code To Reproduce

df1_s = spark.createDataFrame([[1,2]], schema=StructType([StructField("a", IntegerType()), StructField("b",IntegerType())]))
df1_s = spark.createDataFrame([[1,2]], schema=StructType([StructField("c", IntegerType()), StructField("d",IntegerType())]))

dag= FugueWorkflow()
df1 = dag.df(df1_s)
df2 = dag.df(df1_s)
df2 = df1.join(df2, how='cross')
dag.run(engine='spark')

Describe the bug
When trying to perform  a cross-join using spark dataframes, I am encountering the following error
_2 _State.RUNNING -> _State.FAILED  can't specify on for cross join

Expected behavior
When using the 'SparkExecutionEngine', I would expect that a cross join would function in the same way as with local dataframes
dag = FugueWorkflow()
df1 = dag.df([[1,2]],"a:int,b:int")
df2 = dag.df([[3,4]],"c:int,d:int")
df3 = df1.join(df2, how='cross')
dag.run()

Environment (please complete the following information):

Backend: spark
Backend version: 3.2.2
Python version: 3.9.5
OS: linux

The problem is your code has typos, you defined df1_s twice and df2 is also from df1_s
This works
df1_s = spark.createDataFrame([[1,2]], schema=StructType([StructField("a", IntegerType()), StructField("b",IntegerType())]))
df2_s = spark.createDataFrame([[1,2]], schema=StructType([StructField("c", IntegerType()), StructField("d",IntegerType())]))

dag= FugueWorkflow()
df1 = dag.df(df1_s)
df2 = dag.df(df2_s)
df2 = df1.join(df2, how='cross')
dag.run(engine='spark')

But the error message is indeed confusing. It means that it automatically detected the common columns because of your typos, but it's not clear to users. We need to fix this.

Also, with Fugue, you really don't need to create spark df with the tedious schema expressions, you can just use pandas dfs
dag = FugueWorkflow()
df1 = dag.df(pd.DataFrame(...))
df2 = dag.df(pd.DataFrame(...))
...

dag.run(spark)

source: gharchive/issue

authors: goodwanghan jstammers

repo: fugue-project/fugue

license_type: permissive

license_source: github-api


text:
PixelFade: ノイズガイドによる段階的な置き換えを用いたプライバシー保護人物再識別

タイトル: PixelFade: ノイズガイドによる段階的な置き換えを用いたプライバシー保護人物再識別
リンク: https://arxiv.org/abs/2408.05543
概要:
オンライン人物再識別サービスは、潜在的なデータ漏洩や復元攻撃によるプライバシー侵害に直面しており、クラウドに保存された画像が悪意のある攻撃者にさらされ、社会的な懸念を引き起こしています。歩行者画像のプライバシー保護は非常に重要です。従来のプライバシー保護型人物再識別手法は、復元攻撃に耐えることができず、精度も低下します。本稿では、歩行者画像をノイズのような画像に最適化し、復元攻撃に耐える反復手法（PixelFade）を提案します。まず、既存のプライバシー保護手法で保護された画像の詳細な分析を行い、保護された画像のランダム性が復元モデルの学習を妨害することを明らかにします。具体的には、特定の認証モデルの属性制約を用いたノイズガイド型目的関数を提案し、歩行者画像を正規分布ノイズ画像に最適化すると同時に、認証モデルに従って元の識別情報を保持します。上記の非凸最適化問題を解決するために、制約操作と部分置換操作を交互に実行するヒューリスティック最適化アルゴリズムを提案します。この戦略は、元のピクセルをノイズに置き換えてプライバシーを保護するだけでなく、画像をより良い最適化方向に導き、識別性を効果的に保持します。広範な実験により、我々のPixelFadeは、復元攻撃への耐性と人物再識別性能において、従来の手法を上回ることが実証されました。コードはhttps://github.com/iSEE-Laboratory/PixelFadeで公開されています。

@yukihiko-fuyuki が以下のラベルを提案し、適用しました：

person-re-identification
adversarial-learning
privacy-enhancement

以下の新しいラベルが作成され、適用されました：

person-re-identification
adversarial-learning
privacy-enhancement

論文要約
論文要約: PixelFade - ノイズ画像でプライバシーを保護する人物再識別技術

背景:  人物再識別技術は、防犯やマーケティングに活用されている一方、クラウド上に保存された画像データが悪用されるプライバシー侵害のリスクも孕んでいます。
課題: 従来のプライバシー保護技術は、攻撃者による画像復元に弱く、識別精度も低いという課題がありました。
提案手法 (PixelFade):  本論文では、人物画像をノイズ画像に変換することでプライバシーを保護する、復元攻撃に強いPixelFadeという手法を提案しています。

ノイズ画像への最適化: PixelFadeは、人物画像を正規分布ノイズ画像に変化させます。
識別情報の保持:  ノイズ化を行う際、特定の人物認証モデルで識別に必要な情報のみを保持するように、画像を変換します。
段階的な置き換え:  独自のアルゴリズムを用いて、元の画像のピクセルをノイズに段階的に置き換えることで、最適なノイズ画像を生成します。

利点:

高い復元攻撃耐性: ノイズ画像化により、元の画像を復元することが困難になります。
高い識別精度:  識別に必要な情報のみを保持するため、高い識別精度を維持します。

成果: 実験により、PixelFadeは従来の手法と比較して、復元攻撃への耐性と人物再識別性能の両面で優れた結果を示しました。

一言でまとめると: PixelFadeは、人物画像をノイズ画像に変換することでプライバシーを保護しつつ、高い識別精度を維持する、安全性の高い人物再識別技術です。

repo: fulfulggg/Information-gathering

license: MIT


text:
error in GameScene.swift

/FlappySwift-master/FlappyBird/GameScene.swift:206:19: Overriding method with selector 'touchesBegan:withEvent:' has incompatible type '(NSSet, UIEvent) -> ()'

issue fixed.
override func touchesBegan(touches: Set, withEvent event: UIEvent) {....}

FlappyBird/GameScene.swift:206:41: Reference to generic type 'Set' requires arguments in <...>
I get this error when I replace the code line

You have to tell Swift what the Set type is. In this case, I think it's just Set<AnyObject>.

It was indeed expecting Set thanks :)
But now i've got an error In AppDelegate.swift with the function didFinishLaunchingWithOption.. I believe it expects something more.
Edit: I Just deleted the function to resolve it ^^

@azpery  how did u solve this issue? i still have error as  "FlappyBird/GameScene.swift:206:41: Reference to generic type 'Set' requires arguments in <...>"

You have to tell what type the Set is :
Set<NSObject>

Fixed in 4e94e7bfe and friends

authors: MaddTheSane azpery jashmenn lhlpasser stoneyzhang

repo: fullstackio/FlappySwift

license: mit

license_source: bigquery


text:
スケジュール管理

みんなが空いている日にちを共有してください

7/21 21:00
林（ゆ）
あき
こうな
りこ

7/31までに
動画編集を一通り終わらせる
↓
先輩に確認
8/2に完成版を提出

7/26
サークル内紹介の素材を提出する！


text:
The new transforms need an example unit test

Spawned from https://github.com/fusor/cpma/pull/128#issuecomment-491611443
I provided an example for how to accomplish this here: https://github.com/eriknelson/cpma/commit/bdd651a0616350d178fd39274bd4b80b3abf0424
Specifically this is how I would convert Flush into overridable behavior so it becomes testable: https://github.com/eriknelson/cpma/commit/bdd651a0616350d178fd39274bd4b80b3abf0424
I'm not 100% satisfied with pkg level default functions; it doesn't feel like that's a sustainable model for dependency injection (DI). Something to consider, I was chatting with another kubernetes go developer about how people deal with DI in go and there have been some promising proposals in major projects that maybe we could leverage? https://github.com/kubernetes-sigs/controller-runtime/pull/285
Pragmatically I do not think we should adopt this, but it's an interesting option to explore, should we choose to do so.

https://github.com/fusor/cpma/pull/148

authors: eriknelson jmontleon

repo: fusor/cpma


text:
Add PVC to html/json report

This PR adds PVC to html/json report

Closes https://github.com/fusor/cpma/issues/356

cc @tsanders-rh the PV/PVC info for labs you requested

Great.  Is "Name" as shown in the report "Namespace"?  Assume so.

@tsanders-rh Updated screenshot

@alexander-demichev Perfect!  Thanks!

source: gharchive/pull-request


text:
Support using OCP4 'latest', 'nightly', or explicit versions

pipeline/common_stages.groovy:

Rewrite if/else conditional to switch for greater flexibility & logical ease
Allow use of explicit versions (4.1.11, 4.1.9, etc.) on mirror
Support use-case for latest and nightly variable values

roles/ocp4_cluster_deploy/defaults/main.yml:

Set openshift_installer_release to latest
Add variables to support using nightly and latest

roles/ocp4_cluster_deploy/tasks/get_ocp4_installer.yml:

Consumes get_ocp4_nightly.yml
Improve support for nightly
Add support for latest

roles/ocp4_cluster_deploy/tasks/get_ocp4_nightly.yml:

Removed; consumed by get_ocp4_installer.yml

roles/login_ocp/defaults/main.yml:

Update release_url
Reorganize & comment variables now set dynamically

roles/login_ocp/tasks/download_oc_binary.yml:

Add logic to determine & use latest version

repo: fusor/mig-ci


text:
[Rbac] Alcor Rbac Support

This PR support rbac policy.

@Gzure Can you draft a short design spec to explain the high-level design points on Alcor RBAC? Thanks.

@Gzure Can you draft a short design spec to explain the high-level design points on Alcor RBAC? Thanks.

@xieus I add a simple rbac design file https://github.com/Gzure/alcor/blob/subnet-delete-bug/docs/modules/ROOT/pages/high_level/rbac_design.adoc

authors: Gzure xieus

repo: futurewei-cloud/alcor


text:
thread 'main' panicked at 'failed to parse abi file: Error("expected value", line: 1, column: 1)'

I keep getting this error. Maybe it's because of rate limiting?
fetching abi from https://api.bscscan.com/api/?module=contract&action=getabi&address=0x0feadcc3824e7f3c12f40e324a60c23ca51627fc&format=json&apikey=<redacted>
thread 'main' panicked at 'failed to parse abi file: Error("expected value", line: 1, column: 1)', /home/rappie/ityfuzz.git/src/evm/contract_utils.rs:87:60
stack backtrace:
   0: rust_begin_unwind
             at /rustc/af06dce64bf87ea9206bdf6cff61c144b9ce8458/library/std/src/panicking.rs:577:5
   1: core::panicking::panic_fmt
             at /rustc/af06dce64bf87ea9206bdf6cff61c144b9ce8458/library/core/src/panicking.rs:67:14
   2: core::result::unwrap_failed
             at /rustc/af06dce64bf87ea9206bdf6cff61c144b9ce8458/library/core/src/result.rs:1687:5
   3: ityfuzz::evm::contract_utils::ContractLoader::parse_abi_str
   4: <ityfuzz::evm::onchain::onchain::OnChain<VS,I,S> as ityfuzz::evm::middleware::Middleware<VS,I,S>>::on_step
   5: <ityfuzz::evm::host::FuzzHost<VS,I,S> as revm::evm_impl::Host<S>>::step
   6: revm::interpreter::Interpreter::run
   7: <ityfuzz::evm::host::FuzzHost<VS,I,S> as revm::evm_impl::Host<S>>::call
   8: revm::instructions::host::call
   9: revm::interpreter::Interpreter::run
  10: ityfuzz::evm::vm::EVMExecutor<I,S,VS>::execute_from_pc
  11: <ityfuzz::evm::vm::EVMExecutor<I,S,VS> as ityfuzz::generic_vm::vm_executor::GenericVM<VS,revm::interpreter::bytecode::Bytecode,bytes::bytes::Bytes,primitive_types::H160,primitive_types::H160,primitive_types::U256,alloc::vec::Vec<u8>,I,S>>::execute
  12: <ityfuzz::executor::FuzzExecutor<VS,Addr,Code,By,Loc,SlotTy,Out,I,S,OT> as libafl::executors::Executor<EM,I,S,Z>>::run_target
  13: <(Head,Tail) as libafl::stages::StagesTuple<E,EM,S,Z>>::perform_all
  14: <ityfuzz::fuzzer::ItyFuzzer<VS,Loc,Addr,Out,CS,IS,F,IF,I,OF,S,OT> as libafl::fuzzer::Fuzzer<E,EM,I,S,ST>>::fuzz_loop
  15: ityfuzz::fuzzers::evm_fuzzer::evm_fuzzer
  16: cli::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Awesome. Looks like it's working.
Can I point multiple cli instances running on different targets/chains to the same proxy?

yes

Thanks :slightly_smiling_face:
No more errors, closing the issue.

authors: rappie shouc

repo: fuzzland/ityfuzz


text:
Do not open pcap files

Hello, Mikhail!
I deployed your application on Linux Debian x86_64. Pre-installed apache2, php5, perl and tshark. When I try to open a pcap file, nothing happens in the interface. In the log file /var/log/apache2/error.log an error message appears:
[Tue May 24 14:17:57 2016] [error] [client 192.168.14.50] PHP Warning:  filesize(): stat failed for /var/www/extshark/php/../data/tmp/dumps/20-05-2016_19-45.pcap/view_.csv in /var/www/extshark/php/classes/TShark.php on line 46, referer: http://172.16.117.12/extshark/
Please tell me how to fix it?
Best regards!
Alexander

Hi!
That interface do not completed at all, it could open file, could show each packet detailed info. But it quite buggy and was used by me to open really large pcap without downloading. So if you do not afraid of some debugging you will launch it :)
First of all, please check existing of file "/data/tmp/dumps/20-05-2016_19-45.pcap/view_.csv"
This file was created by calling perl script at https://github.com/fuzzz/extshark/blob/master/php/classes/TShark.php#L35
For debugging you can try to run that script with same arguments manually.(There are no error handling :) )

Mikhail!
Thank you very much for your answer! After viewing the do_psml.pl script I found the cause of the error. Do not automatically installed package libhtml-parser-perl. The pcap file is now displayed in the web interface. Sorry to disturb.
Good luck in your developments!
Alexander

feel free to bother me if something goes wrong again :) GL

OK :)
Thank you very much!

authors: alex-a-n fuzzz

repo: fuzzz/extshark


text:
incorrect  UCIS coverage report  format ?

I've started evaluating pyvsc as a replacement for cocotb-coverage in our IC design team and while I was able to generate a successful coverage report as text file, the corresponding UCIS xml file was not displayed correctly by  the fc4sc
tools/gui/index.html  web viewer
text report :
test_gen_pyvsc.simple_test.txt
xml UCIS report :
test_gen_pyvsc.simple_test.ucis.xml.gz
How the UCIS report looks like with the WEB reader

This is how a similar report generated using cocotb-coverage (+ UCIS generation patch) looks like:

the corresponding XML file from cocotb-coverage
test_gen.simple_test.ucis.xml.gz
The code used to create the coverage bins is the following:
@vsc.covergroup
class APBSlaveCoverGroup:
    def __init__(self):
        self.with_sample(dict(addr=vsc.uint16_t(), write=vsc.bit_t()))
        "Create a instance of APBSlaveCoverGroup"
        self.add_cp = vsc.coverpoint(
            self.addr,
            bins={k: vsc.bin(v) for (k, v) in params.reg_dict_ext.items()},
        )
        self.type_cp = vsc.coverpoint(
            self.write,
            bins={
                "read": vsc.bin(0),
                "write": vsc.bin(1),
            },
        )

with params.reg_dict_ext declared as followed
reg_dict_ext = {'dout': 0, 'din': 12, 'dir': 16, 'ie': 28, 'pe': 32, 'pdir': 36, 'sr': 40, 'ds0': 52, 'ds1': 56, 'schmitt': 60, 'function*0': 64, 'function*1': 68, 'function*2': 72, 'function*3': 76, 'function*4': 80, 'function*5': 84, 'function*6': 88, 'function*7': 92, 'function*8': 96, 'function*9': 100, 'function*10': 104, 'function*11': 108, 'function*12': 112, 'function*13': 116, 'function*14': 120, 'function*15': 124, 'function*16': 128, 'function*17': 132, 'function*18': 136, 'function*19': 140, 'function*20': 144, 'function*21': 148, 'function*22': 152, 'function*23': 156, 'function*24': 160, 'function*25': 164, 'function*26': 168, 'function*27': 172, 'function*28': 176, 'function*29': 180, 'function*30': 184, 'function*31': 188, 'doutset': 4, 'doutclear': 8, 'dirset': 20, 'dirclear': 24, 'srset': 44, 'srclear': 48}

the coverage group is about monitoring which register has been accessed on a APB slave. addr represent the address and a bus and write represent the read/write selection signal. The reg_dict_ext represents the register mapping on the bus (the key is the register name, the value is the address on the bus)
Code used for generating the report:
    txt_coverage = vsc.get_coverage_report(details=True)
    if log:
        dut._log.info("Coverage Report :\n" + txt_coverage)
    # export
    vsc.write_coverage_db(filename=f"{output_dir}/{calling_module}.{test_name}.ucis.xml")
    with open(f"{output_dir}/{calling_module}.{test_name}.rpt",'w')  as f:
        f.write(txt_coverage)

But apparently the UCIS file is opened correctly in pyucis-viewer (that I have just discover BTW)

Hi @rbarzic,
Unfortunately, I don't have a full set of answers on this one. When I first started work on pyUCIS, I looked at the XML generated by fc4sc and found that it didn't validate against the published UCIS XML schema. At the time, I didn't investigate further. My understanding is that some pyVSC/pyUCIS users are taking the generated XML into commercial EDA coverage-analysis flows, which gives some weight to the view that the pyUCIS XML might be correct (subjective, of course, since I'm unable to work with that specific commercial EDA flow myself...).
What can you tell me about your intended use model and tool flow? It sounds like you might be using the fc4sc viewer, since you're currently using cocotb-coverage. It might be possible to support, at minimum, writing the XML format accepted by the viewer. Depending on your simulator toolchain, there might be other options for getting pyVSC coverage data into the coverage reporting tools there.

authors: mballance rbarzic

repo: fvutils/pyvsc


text:
copy(): The first argument to copy() function cannot be a directory

I get that error doing
$faker->file()
The /tmp folder exists.
PHP 5.4.38 (cli) (built: Feb 20 2015 02:42:34)
Copyright (c) 1997-2014 The PHP Group
Zend Engine v2.4.0, Copyright (c) 1998-2014 Zend Technologies
CentOS 6.2

What are your parameters for $faker->file(); like $faker->file($sourceDir, $targetDir, false)

I didnt use any parameters, just file()

file() returns a random file from the source directory (here `/tmp). I suspect it fails because this directory is empty, am I right?

Sorry, I just understood the source of the problem (#547). Continuing discussion there.

Fixed by #547

authors: fzaninotto montogeek vuchl

repo: fzaninotto/Faker


text:
adjacent lanelet problem

I need to get adjacent lane relation of 2 lanelets with the opposite direction, but Optional RoutingGraph::adjacentLeft(const ConstLanelet& lanelet) in src/lanelet2/lanelet2_routing/src/RoutingGraph.cpp get nothing for this scenario, the scenario is like pic below, i want to get adjacentLeft lanelet of laneletB, which should be laneletA, but get nothing by function adjacentLeft.

I checked, and find function leftOf is used when build boost::graph
template <typename Lanelet1T, typename Lanelet2T>
IfLL<Lanelet1T, IfLL<Lanelet2T, bool>> leftOf(const Lanelet1T& left, const Lanelet2T& right);
it judge the left relation use:
left.rightBound() == right.leftBound()
which only work for lanelet whose direction is the same.
for opposite direction adjacent lanelet,should be checked by this condition:
left.leftBound().invert() == right.leftBound()
Is return nothing specification for this scenario, or there should be return?

So for overtake maneuver using opposite lane(yellow dashed line), there is no routing method? or this situation should be include in trafficRules ?

Traffic rules are meant to be a customization point for users where they can implement their own behavior for the routing graph. For overtaking, I would suggest to create special overtaking traffic rules and use the graph created from them to plan these maneuvers.

Ok, thank you very much for your suggestion.

I just came across this today too, it seems like a common use case (#100). Would it make sense to add an official opposing relation?
If adjacent left/right are available, but not traversable, then it shouldn't be much different to add opposing right?
I don't know all the details behind the routing graph though.

Yes, could definitively make sense. Also for applications like overtaking using the opposing lane. Basically we would need four new different opposing relations (left/right, lane change for overtaking possible/not possible). I think we even have the information about opposing lanelets at some point when we create the graph, but we discard them after finding out that they are neither adjacent nor left/right.
Even though it should be quite straightforward to add this, it would require resources that we currently don't have, tbh. Unless there is an internal use case that makes it necessary for us. If you need this, I would suggest you implement it yourself.

authors: dufengit icolwell-as poggenhans


text:
Environment definitions

Two issues I'm addressing here

requirements.txt needs to have == between package name and version to be able to install it using pip install -r requirements.txt; not following this would confuse anyone familiar with standard conventions on this
The mixup around Python versions has convinced me that providing a Conda environment.yml is definitely worthwhile. I've also included instructions in the README on how to use it.

Hi Ed, thanks!
I tested the conda setup (with miniconda), but I currently get an error message.
PackagesNotFoundError: The following packages are not available from current channels:

  - libosxunwind=0.0.6*
  - libintl=0.22.5*
  - libgfortran=5.0.0*

 Current channels:

  - https://repo.anaconda.com/pkgs/main/linux-64
  - https://repo.anaconda.com/pkgs/r/linux-64
  - https://conda.anaconda.org/conda-forge/linux-64

It seems that the first two packages are not available for x86-64 Linux. I don't understand what the issue with libgfortran could be.

Ah, well spotted. libgfortran is a weird one; for some reason on macOS you get a metapackage gfortran v5.0.0 as well as the relevant version of gfortran5 (13.2.0 in our case).
Usually what I do is remove those, as they are intermediary dependencies that are well-constrained by the other explicitly specified packages, in the interests of being cross-platform. I've pushed a change to remove them here.

authors: edbennett fzierler


text:
1.21.3 support

title

1.21.3 didn't appear to have compatibility issues. 1.21.4 does, however.

repo: fzzyhmstrs/pc


text:
Ensure the hello_world workflow is working

Ensure and document:

dockstore tool launch --entry quay.io/ga4gh-dream/dockstore-tool-synapse-get --json hello_world_get.cwl.json sucessfully runs

Perhaps move the hello_world_get.cwl.json to Dockstore from Synapse.

The output files are in datastore/launcher*/outputs/

Perhaps move these output files to the original directory

dockstore tool launch --entry quay.io/ga4gh-dream/dockstore-tool-helloworld --json hello_world.cwl.json successfully runs
The output files are in datastore/launcher*/outputs/

Perhaps move these output files to the original directory

dockstore tool launch --entry quay.io/ga4gh-dream/dockstore-tool-helloworld-checker --json hello_world_checker.cwl.json successfully runs
dockstore tool launch --entry quay.io/ga4gh-dream/dockstore-tool-synapse-submit --json

This looks complete

authors: denis-yuen garyluu


text:
Ship with a standalone WSGI server

If you've ever set up Apache, then you know it can be a pain. We ship the server to run with the call ga4gh_server which uses the flask debug server, but when you set it up to run behind Apache it manages multiple processes better.
It is possible to ship the server with a "standalone" WSGI server. This means the call to ga4gh_server would by default handle multiple connections well and makes it suitable for most modest installations. We could still provide a path using the debug server via a flag.
This should make deployment much easier. You can still put the WSGI server behind apache or nginx using a proxy, it is easier to configure and doesn't require mod_wsgi.
http://stackoverflow.com/questions/20843486/what-are-the-limitations-of-the-flask-built-in-web-server
http://flask.pocoo.org/docs/0.12/deploying/wsgi-standalone/

This comment from your first link is rather disconcerting.
Another issue is security: if you are concerned at ALL about security (and not just the security of the data in the application itself, but the security of the box that will be running it as well) then you should not use the development server. It is not ready to withstand any sort of attack.

The entire post strongly suggests that we should move away from using our current configuration.
The guincorn server looks interesting.

We can close this issue if the script server_dev, when not running in debug mode, starts the app behind gunicorn as opposed to werkzeug.

Took a quick look at this and made these two branches:
https://github.com/david4096/server-1/tree/gunicorn
https://github.com/david4096/server-1/tree/twisted
I used minimal configuration and a synthetic test to simulate simultaneous queries. Since it is on the same machine, the number of source requests simultaneously sent is limited.
The script uses runs a lot of curl commands in the background
for i in {1..10000}; do
    curl -X POST http://localhost:8000/datasets/search --silent -O /dev/null &
done

https://github.com/david4096/server-1/tree/gunicorn ~360 requests/second

zsh do.sh  38.41s user 9.54s system 175% cpu 27.353 total

master (debug server) ~280 requests/second

zsh do.sh  50.76s user 22.94s system 206% cpu 35.768 total

https://github.com/david4096/server-1/tree/twisted ~230 requests/second

zsh do.sh  48.22s user 25.62s system 174% cpu 42.351 total

I think that the twisted library needs to be taken advantage of differently to realize its benefit (asynchronous communication). It seems to use a single process with multiple threads. Since it is managing the extra thread overhead it loses to the debug server, but if it had process management similar to gunicorn I believe it would be competitive.
The next steps are to add a configuration option to run with multiple workers, and to optionally specify the number of workers. The configuration path needs to be refactored slightly as some values are passed to the .run() method, and they should be set at an earlier config step if possible. Logging will behave differently when running under gunicorn, and so we'll have to determine the amount of test coverage we want/need when running under this mode. Tests that rely on bringing the server up and down appear to timeout right now.


text:
Ontologies update

Depends on #1104.
Makes two changes:

Change the Ontology/OntologyMap object to  OntologyTermMap internally. This is supposed to model what it's doing a bit better. The current setup is rather brittle and will need to be improved, but this at least makes it a bit clearer what's going on (I hope).
Ported the CLI support for ontologies to the SQL repo.  The SQL schema and CLI used the term Ontology rather than OntologyTermMap because it seems that the current approach is quite
limited and will need to be changed. This seems more forward compatible, since we don't want to affect uses by making them change CLI syntax or make backwards incompatible changes to the schema.

I would imagine that we would want to update the CLI add-ontology command to download the map from some authoritative source, and store the terms in the DB. Asking the repo administrator to create a text file mapping the term names to IDs is pretty user-unfriendly. I don't think we should tackle this now, I'm just giving my reasoning for not fully pushing the OntologyTermMap nomenclature into the repo mangement UI.
Issue #1111.

The mapping of ontology names to full ontology terms is a
different issue than having a full support for ontologies.
The current ontologyTermMap functionality is only required in
the server because of variant annotations needed to translate
names in the VCF info column to full ontology terms at run time.
This could be done at load time, as is done with sequence
annotations, at the cost of pulling a lot of data out VCFs.
We will need to implement some kind of ontology-based queries,
which could be done with an external ontology lookup service
(with the refserver doing caching) or internally loading the
ontologies.
We need help on this from someone who has many more clues about
ontology software than I have.
Jerome Kelleher notifications@github.com writes:

Depends on #1104.
Makes two changes:

Change the Ontology/OntologyMap object to OntologyTermMap internally. This
is supposed to model what it's doing a bit better. The current setup is
rather brittle and will need to be improved, but this at least makes it a
bit clearer what's going on (I hope).
Ported the CLI support for ontologies to the SQL repo. The SQL schema and
CLI used the term Ontology rather than OntologyTermMap because it seems
that the current approach is quite limited and will need to be changed.
This seems more forward compatible, since we don't want to affect uses by
making them change CLI syntax or make backwards incompatible changes to the
schema.

I would imagine that we would want to update the CLI add-ontology command to
download the map from some authoritative source, and store the terms in the DB.
Asking the repo administrator to create a text file mapping the term names to
IDs is pretty user-unfriendly. I don't think we should tackle this now, I'm
just giving my reasoning for not fully pushing the OntologyTermMap nomenclature
into the repo mangement UI.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
You can view, comment on, or merge this pull request online at:
https://github.com/ga4gh/server/pull/1117
Commit Summary
• Added UNIQUE indexes to some tables.
• Added URL support for ReadGroupSets.
• Added primary keys, unique and foreign keys.
• Added CASCADE delete for datasets.
• added remove-readgroupset and tidied tests.
• Added FTP support for URLs and note.
• Changed Ontology to OntologyTermMap.
• Added ontology add/delete/list functionality.
File Changes
• M ga4gh/cli.py (259)
• M ga4gh/datamodel/datasets.py (14)
• M ga4gh/datamodel/ontologies.py (41)
• M ga4gh/datamodel/reads.py (5)
• M ga4gh/datamodel/sequenceAnnotations.py (12)
• M ga4gh/datamodel/variants.py (13)
• M ga4gh/datarepo.py (336)
• M ga4gh/exceptions.py (76)
• M tests/datadriven/test_sequenceAnnotations.py (5)
• M tests/datadriven/test_variant_annotations.py (5)
• M tests/paths.py (7)
• M tests/unit/test_cli.py (77)
• M tests/unit/test_repo_manager.py (487)
• M tests/unit/test_variant_annotations.py (4)
Patch Links:
• https://github.com/ga4gh/server/pull/1117.patch
• https://github.com/ga4gh/server/pull/1117.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub*

This is complicate @diekhans, I agree. Are you happy within this PR as it is though?

I haven't looked at the code, but it does the job we need
today, which is a great criteria for a +1.
My main point was really there is future complexity coming with
ontologies, so don't worry about this being incomplete.
Jerome Kelleher notifications@github.com writes:

This is complicate @diekhans, I agree. Are you happy within this PR as it is
though?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub*

Excellent, thanks @diekhans.

Can I get some review here please @dcolligan, @macieksmuga, @david4096? This should be easy to follow once #1104 is merged.

@jeromekelleher could you rebase this so we can see only the changes that aren't in #1104 ?

Done -- thanks for the heads up @dcolligan.

Review please... @macieksmuga, @david4096, @dcolligan.

+1

OK, last chance to review here... Merging this tomorrow if I don't hear otherwise.

+1 thanks for pushing this part of the code forward. The ontology term map stuff was done in a rush for variant annotation and this keeps it in parallel with the internal server changes without modifying it greatly.

Excellent, thanks for the review @david4096. I think what we have here is good enough to keep us going for now, but we definitely need to look at this ontology stuff again. I think it would be great if we could take the burden of creating term maps away from the admin. One idea would be to  build them by downloading directly from some authorative source and store the map directly in the DB, without the intermediate text file faffing.

OK, merging this. Thanks again for the review @david4096, I'll open up issue(s) now for the dangling points.

authors: david4096 dcolligan diekhans jeromekelleher


text:
Add top-level exception handler to repo manager

Issue #1172

Looks good, +1.

authors: dcolligan jeromekelleher


text:
🛑 Revista is down

In 3edb60c, Revista (https://pensamientopenal.com.ar/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Revista is back up in bc26483.


text:
Allow symbols to be actionTypes

So you can do,
// actionTypes.js
export const MY_ACTION = Symbol();

I'm not sure I'm going to support this because symbols are not serializable AFAIK.
See also #4.

I'm closing for now (see reasons in #4) but may revisit later.
Need to understand our tooling story (#7) first.
Thanks for the PR though!

authors: boopathi gaearon

repo: gaearon/redux


text:
🛑 Test SAPISEARCH is down

In 21a768a, Test SAPISEARCH ($SAPISEARCH_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Test SAPISEARCH is back up in e0559c2.

repo: gaeljw/poc-uptime


text:
"nan" should be a non-dev dependency

I'm getting following error when installing v0.3.0 from npm. Installing nan beforehand fixed it.
% npm install libtidy

> libtidy@0.3.0 install /Users/o_kan/aaa/node_modules/libtidy
> node-gyp rebuild

module.js:327
    throw err;
    ^

Error: Cannot find module 'nan'
    at Function.Module._resolveFilename (module.js:325:15)
    at Function.Module._load (module.js:276:25)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at [eval]:1:1
    at Object.exports.runInThisContext (vm.js:54:17)
    at Object.<anonymous> ([eval]-wrapper:6:22)
    at Module._compile (module.js:409:26)
    at node.js:579:27
    at nextTickCallbackWith0Args (node.js:420:9)
gyp: Call to 'node -e "require('nan')"' returned exit status 1 while in binding.gyp. while trying to load binding.gyp

If moving it from devDependencies to dependencies is fine, I can do something after work :o .

Fixed in v0.3.1. Thanks for the report!

authors: gagern jokester

repo: gagern/node-libtidy


text:
deploy_from_abi_and_bytecode failed

error:

reference:
https://github.com/gakonst/ethers-rs/blob/master/examples/contracts/examples/deploy_from_abi_and_bytecode.rs
version:
ethers = "1.0.2"

is Atoken by any chance just an interface?

no, simple ERC20 Contract

could you please provide the json content and the cargo expand output of the example.

AToken.json.txt

did this ever get resolved?

authors: Trini7 mattsse scglenn

repo: gakonst/ethers-rs


text:
zkSync gas oracle

Is your feature request related to a problem? Please describe.
zkSync doesn't support eth_feeHistory, so the ProviderOracle gas oracle doesn't work with it. Instead, they have a zks_estimateFee RPC method to retrieve gas_limit, max_fee_per_gas and max_priority_fee_per_gas for a tx.
Describe the solution you'd like
I'd like to have a gas oracle that calls zks_estimateFee to estimate fees for ZkSync.
Describe alternatives you've considered
It's possible to estimate EIP-1559 fees without eth_feeHistory, but it won't be accurate.
Additional context
Happy to provide a PR if you accept this feature for inclusion.

Actually, on a second thought this won't work well, because the GasOracle interface doesn't support passing the tx as argument, but zks_estimateFee needs the tx as its argument. Not sure what's the best solution here.

You can create your own thin wrapper for this rpc as such:
use std::sync::Arc;

use ethers::providers::{Http, JsonRpcClient, Middleware, Provider, ProviderExt};
use zksync_types::{fee::Fee, web3::types::CallRequest};

async fn estimate_fee<J: JsonRpcClient>(client: J, request: CallRequest) -> Fee {
    let fee = client
        .request::<[CallRequest; 1], Fee>("zks_estimateFee", [request])
        .await
        .unwrap();

    fee
}

#[tokio::main]
async fn main() {
    let provider = Provider::<Http>::connect("https://mainnet.era.zksync.io").await;
    let client = Arc::new(provider);

    let request = CallRequest {
        from: Some(
            "0x1111111111111111111111111111111111111111"
                .parse()
                .unwrap(),
        ),
        to: Some(
            "0x2222222222222222222222222222222222222222"
                .parse()
                .unwrap(),
        ),
        data: Some(vec![0xff, 0xff, 0xff].into()),
        ..Default::default()
    };

    let fee_estimate = estimate_fee(client.provider().as_ref(), request).await;

    println!("{fee_estimate:?}");
}

With zksync_types from git:
[dependencies]
ethers = "2.0.4"
tokio = { version = "1.28.0", features = ["full"] }
zksync_types = { git = "https://github.com/matter-labs/zksync-era.git" }

Running this code would give you
Fee { gas_limit: 2263547, max_fee_per_gas: 250000000, max_priority_fee_per_gas: 0, gas_per_pubdata_limit: 7744 }

Thanks @montekki , I ended up doing something similar, but using only ethers types.
The code implements a GasOracle that always submits a dummy transaction for gas estimation to zks_estimateFee. This is fine, because we don't use the gas_limit field from the result, only max_fee_par_gas and max_priority_fee_per_gas which are independent of the transaction parameters.
Maintainers, if you're ok with this GasOracle solution, please let me know and I'll to submit a PR with it. Otherwise feel free to close the issue.

authors: agostbiro montekki


text:
Added a fully configurable version of G8RecognitionOperation:initWithLanguage routine

Because of the call to the original version of initWithLanguage is covered with unit tests and the new one is just called from it for now, it seems to me that no changes in unit tests required.

Hm... I have no issues with this code neither in XCode 6 nor 7. What's Travis is talking about???

@vorlovsky thanks for your work. Unfortunately travis-ci is failing. Please fix it and try again.

Fixed. Removed "copyFilesFromResources" because not more used.


text:
⚠ Inventory API Endpoint has degraded performance

In 51b12cb, Inventory API Endpoint (https://inventory.roblox.com/v1/users/82738847/assets/collectibles?limit=10&sortOrder=Asc) experienced degraded performance:

HTTP code: 200
Response time: 2703 ms

Resolved: Inventory API Endpoint performance has improved in af5f617.


text:
🛑 Users API Endpoint is down

In 305f752, Users API Endpoint (https://users.roblox.com/) was down:

HTTP code: 503
Response time: 31 ms

Resolved: Users API Endpoint is back up in 7e85e7e.


text:
Add an action to lint shell scripts and Dockerfiles

Added an action to run linters for shell scripts and Dockerfiles.  It will run on any PR.  If there's a lint issue in one of the files being modified, it will add a review pointing out the specific line and error. If it finds errors in files not in the PR, those will get noted under the "Checks" tab.  None of this blocks merging the PR anyway, but it should make it much easier to spot potential problems.

Note that I have not yet gone through and fixed all the existing lint issues; my plan is to do that after merging #76, since there's changes to pretty much all the files that would be affected by this.

While we're at it...
https://github.com/dotenv-linter/action-dotenv-linter
https://github.com/marketplace/actions/yaml-lint

While we're at it...
https://github.com/dotenv-linter/action-dotenv-linter
https://github.com/marketplace/actions/yaml-lint

Good idea! I've added them.

Lgtm

repo: games-on-whales/gow


text:
Consider using gometalinter.

Right now running gometalinter produces ~170 potential warnings. Some of them can be ignored (like exported symbols) others, however, cannot (like ignoring errors). I don't have sufficient knowledge of this project to judge where errors could be safely ignored and where they couldn't, so I'm asking you for advice.
Thanks.

I'm now using it, and slowly weeding out the warnings.

authors: DmitriyMV gammons

repo: gammons/todolist


text:
Some questions related to CLUE

Dear Dr. Cao, sorry to disturb you. When I intend to run CLUE based on the open source all datasets provided by the organizers of neurips competition, I find an error:

Even if I run this method before training, I still receive this error for clue.fitting step:

In addition, I think I cannot find these two datasets in the open codes part of this page: https://github.com/openproblems-bio/neurips2021_multimodal_topmethods/tree/main/src/match_modality/methods/clue
including the file prep.pickle and "hyperparams.yaml. I think without these files I cannot utilize the best combination of parameters.

Could you please help me? Thanks a lot.

Hi, I solved this problem by using train.py in another folder and had generated embeddings. Thanks a lot.

repo: gao-lab/GLUE


text:
Add raw dump to accelerate the save process

VizTracer can save json file directly from the C tracer now. There won't be any file_info, but all the trace data is there. This is helpful for cmdline usage to avoid duplicated load/dump procedure

Codecov Report

Merging #186 (7b89f1b) into master (e3baad3) will decrease coverage by 1.13%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##            master     #186      +/-   ##
===========================================
- Coverage   100.00%   98.86%   -1.14%
===========================================
  Files           22       22
  Lines         2361     2370       +9
===========================================
- Hits          2361     2343      -18
- Misses           0       27      +27

Impacted Files
Coverage Δ

src/viztracer/main.py
99.07% <100.00%> (-0.93%)
:arrow_down:

src/viztracer/report_builder.py
95.62% <100.00%> (-4.38%)
:arrow_down:

src/viztracer/tracer.py
100.00% <100.00%> (ø)

src/viztracer/viztracer.py
95.67% <100.00%> (-4.33%)
:arrow_down:

src/viztracer/patch.py
95.69% <0.00%> (-4.31%)
:arrow_down:

src/viztracer/simulator.py
96.77% <0.00%> (-3.23%)
:arrow_down:

src/viztracer/prog_snapshot.py
99.44% <0.00%> (-0.56%)
:arrow_down:

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 e3baad3...7b89f1b. Read the comment docs.

authors: codecov-commenter gaogaotiantian

repo: gaogaotiantian/viztracer


text:
Docs: add framework selector

Add framework dropdown on side nav and mobile nav

Redirect /docs to /docs/react
Add framework to route. /docs/guide becomes /docs/react/guide
Add framework to links mentioned in mdx. /docs/schemas/covalues is replaced with /docs/[framework]/schemas/covalues
Add a component for displaying content only when a specific framework is selected
<ContentByFramework framework="react">
   content visible only if React is the selected framework
</ContentByFramework>

I wasn't convinced by the url stuff, but honestly it feels great with the picker (and I genuinely can't see the url most of the time). I'm still a little worried about canonical urls and links... but I can't see any immediate problems (thanks to the ContentByFramework block)

I'm still a little worried about canonical urls
Same here

authors: bensleveritt trishalim

repo: garden-co/jazz


text:
add certs with the correct SAN

How to categorize this PR?

/area networking
/kind bug
What this PR does / why we need it:
Use correct SAN in certificates.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

none

/lgtm
I'm just wondering, if it wouldn't make sense to add a make target to generate the certificate.


text:
Use dependabot to manage Gardener package dependencies

How to categorize this PR?

/area os
/kind technical-debt
/os suse-chost
What this PR does / why we need it:
Integrates the changes pushed to gardener-extension-os-gardenlinux by @Kostov6 and @ialidzhikov into the suse-chost extension to have dependabot take care of up-to-date Gardener dependencies.
Release note:

NONE

/ready


text:
restrict CIDR range for openvpn-server and bastion host

What would you like to be added:
I would like to limit the CIDR ranges which are allowed to connect to the openvpn-server in the shoot, and the bastion host.
Why is this needed:
Currently the openvpn-server in the shoot cluster is open to 0.0.0.0/0, as is the bastion host. While CIDR limits are often implemented as a security consideration, they have other benefits as well: blocking unwanted requests early thus keeping logging and monitoring databases clean, lower the load on backend service, etc

We are working/waiting on an upsteam KEP:
https://github.com/kubernetes/enhancements/issues/1217
https://github.com/kubernetes/enhancements/pull/1216
https://github.com/kubernetes/kubernetes/pull/79312
While these will help reduce the number of control plane LB IPs, depending on the provider these IPs cannot be considered stable. But reducing the CIDR will also limit effective DR (we can recover a control plane automatically on a different seed!). We recommend zero trust/beyond corp setups.
Gardenlet https://github.com/gardener/gardener/issues/1576 will offer new options to restrict the CIDR.

There is a GEP for inverting the VPN direction, https://github.com/gardener/gardener/pull/2170, though, it will only be implemented for new Kubernetes versions. Older versions will still use the VPN solution.

@DockToFuture @ScheererJ will this still be necessary with your new reversed VPN proposal #3812?

It depends on how you look at the problem. With #3771/#3812, the openvpn server moves from the shoot cluster to the shoot control plane in the seed cluster. Therefore, if this is "only" about having clean logs/restricted access vector to the shoot cluster then it is no longer relevant. However, even with #3771/#3812 we continue to have an openvpn server, even though it is now located in the shoot control plane in the seed cluster. We still do not restrict connections to the openvpn server to certain cidr ranges. Hence, it might still be relevant.

Thanks @ScheererJ, do you or @DockToFuture plan to take this in the near future?

We do not plan to implement this for the reversed VPN proposal. Meanwhile we have added an authorization server for the reversed vpn solution. It would be fairly straight forward to implement the filter there (https://github.com/gardener/ext-authz-server/blob/master/pkg/auth/v3/auth.go).
@janwillies Feel free to propose a corresponding change if you still need this.

authors: ScheererJ janwillies rfranzke vasu1124

repo: gardener/gardener


text:
[provider-local] pod registry_registry-docker-ipv6 in CrashLoopBackOff

How to categorize this issue?

/area testing robustness
/kind bug test
What happened:

In provider-local kind setup, always pod registry_registry-docker-ipv6 in `CrashLoopBackOff.
From logs I can see network is unreachable error.

2023-02-05T15:04:28.396056945Z stderr F panic: Get "https://registry.ipv6.docker.com/v2/": dial tcp [2600:1f18:2148:bc00:8334:ca86:c3d6:a507]:443: connect: network is unreachable

What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

Gardener version:
Kubernetes version (use kubectl version):
Cloud provider or hardware configuration:
Others:

cc @breuerfelix @timebertt - could you please have a look (see also #7434) 👀

/assign

I think https://github.com/gardener/gardener/pull/7434#issuecomment-1418667778 is unrelated to this issue.
It rather seems like the mirror configuration in the shoot (changed with https://github.com/gardener/gardener/pull/7316) doesn't work, otherwise the node wouldn't try to pull the image from localhost.
cc @danielfoehrKn

authors: breuerfelix rfranzke seshachalam-yv timebertt


text:
Annotate kube-apiserver deployment after labeling the resources for encryption

How to categorize this PR?

/area control-plane security
/kind bug
What this PR does / why we need it:
When the encryption configuration is modified, we label the resources in parallel so that they are rewritten in the ETCD, then snapshot ETCD and remove the label. But in case there are thousands of resources and the client is throttled during the removal of label step, in the next try these resources are again labeled and this results in a cycle.
This PR adds an annotation to the kube-apiserver deployment marking the completion of adding of labels so that we don't repeat this again in case the labels are partially removed from resources.
The task functions for a particular GVK is executed in parallel but sets of tasks for different GVKs are now run in sequence to prevent hitting the rate limit.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Introduced with https://github.com/gardener/gardener/pull/8842
/cc @rfranzke @timuthy as reviewers of the original PR
Release note:

The `kube-apiserver` deployment is annotated to mark the completion of labeling the resources for encrytion so that this step is not repeated in case the "label removal" step fails and resources are partially without the label.

/cherry-pick release-v1.88

/cherry-pick release-v1.87

/cherry-pick release-v1.86

On a second thought, we could also have used the same etcd-snapshotted annotation as well, but it wouldn't make much difference. If snapshotting fails and the flow is retried, we will try to list the resources without the label again (which would be zero), this can be avoided with the current approach.

On a second thought, we could also have used the same etcd-snapshotted annotation as well, it will decrease a patch call for the KAPI deployment. If snapshotting fails and the flow is retried, we will try to list the resources without the label again (which would be zero), this can be avoided with the current approach.

This doesn't sound like a major impact/improvement. It is explicit as it is implemented right now which I prefer.

I'm not sure whether I'm missing somehting, but wouldn't it make more sense/be even better/more robust to have an annotation per GVK? With the current approach, we will only not try to relabel again when the labelling process was successful for all GVKs, right? However, when there are really many resources, this might not even work in a single step/reconciliation run? WDYT?

With the current approach, we will only not try to relabel again when the labelling process was successful for all GVKs, right?

While listing the resources during retry we use the requirement that the label shouldn't exist,
https://github.com/gardener/gardener/blob/d35f0fece5da8ecd879788433f0e65a2498ae763/pkg/utils/gardener/secretsrotation/etcd.go#L82-L94

Okay, then let's proceed with this for now. If we see potential for further optimizations, we can also ship them later when we have more clarity or see the need of even doing so. Thank you!
/approve

/cherry-pick release-v1.86

authors: rfranzke shafeeqes timuthy


text:
Use latest available garden linux suite for release builds

What would you like to be added:
Creating a new patch release for Garden Linux(e.g. 955.1) requires to update the VERSION file in the rel-955 branch.
I argue that if we create a 955.1 suite in our repo.gardenlinux.io, that we also intend to use 955.1 for the rel-955 branch release builds.
Therefore the manual step of updating the VERSION file 955.0 -> 955.1 can be eliminated.
Why is this needed:
Reducing manual steps

I agree, having the repo tree xxx.Y and having xxx.Y in Garden Linux' VERSION file should be intertwined.

authors: MrBatschner Vincinator

repo: gardenlinux/gardenlinux


text:
Avoid burning releases

As release engineer I would like to not be in situation where I can produce something leading to Garden Linux patch release number being "burned" and can't be used further for end-user consumption.
I would like to have:

[ ] Ability to produce release candidate without burning release candidate
[ ] use of experimental repo for drafting release repos?

Questions I'd like to be answered by docs in gardenlinux/repo

what happens if a tag (like 1337.2) exists, I delete the tag and re-create and push it?
Will it simply re-create that apt repo?
Is this a good idea because our repos are supposed to immutable?
What if I accidentally delete, re-create and push the wrong tag? are there any safety nets?

authors: fwilhe pnpavlov


text:
Add new parameters for docker daemon

Implemented some options for docker daemon

bind the docker daemon to multiple ipaddress (changed string to array)
add ip_forward, iptables, ip_masq, fixed_cidr and bridge option

docker::tcp_bind:
  - 'tcp://127.0.0.1:2375'
  - "tcp://%{::ipaddress}:2375"
docker::ip_forward: false
docker::iptables: false
docker::ip_masq: false
docker::fixed_cidr: '10.10.1.0/24'
docker::bridge: 'br0'
docker::default_gateway: '10.10.0.1'

OPTIONS=" -H tcp://127.0.0.1:2375 -H tcp://10.10.0.3:2375 --ip-masq=false --iptables=false --ip-forward=false --fixed-cidr 10.10.1.0/24 --default-gateway 10.10.0.1 --bridge br0"

Thanks @rchicoli, this looks great, one quick suggestion and one request.
Rather than break backwards compatibility with the change from a string to an array, it's probably worth calling any2array on the passed value. You can see an example of this in use here:
https://github.com/garethr/garethr-docker/blob/543b66fd58676164f5a6f7aab99508b440777346/manifests/run.pp#L128
This maintains the ability to pass a string, but allows for passing an array, without having to change the template (which always gets an array).
Also, would it be possible to add some quick unit tests to verify the changes? You should find some other examples but if you have any questions I'm happy to help. The tests really help with ensuring future changes don't break things.
Thanks again.

It sounds good.
I've already implemented any2array function, but now I am looking up how to get beaker-rspec running on my computer.
At the moment I am facing the following problems when I try to run BEAKER_setfile=spec/acceptance/nodesets/debian-81-x64.yml rake beaker
/usr/local/rvm/gems/ruby-2.2.3@3823/gems/beaker-2.32.1/lib/beaker/hypervisor/vagrant.rb:196:in
 `block (2 levels) in vagrant_cmd': Failed to exec 'vagrant destroy --force'.
Error was /usr/share/gems/gems/bundler-1.7.8/lib/bundler/spec_set.rb:92:in `block in materialize':
 Could not find rake-10.5.0 in any of the sources (Bundler::GemNotFound) (RuntimeError)

So I might push the changes changes tomorrow, after solving this little problem

@rchicoli this looks like you be not have the bundle correctly setup or up-to-date. Here's a few things to try:
BEAKER_setfile=spec/acceptance/nodesets/debian-81-x64.yml bundle exec rake beaker

Here you're explicitly running rake with bundler. This avoids issues with rake being on the path and not picking up the relevant bundle.
If that doesn't work then first try:
bundle install
bundle update

That should install the relevant gems, or update them if they are out of date and that's causing the issue. Let me know if any of that fixes the issues.

Thanks @garethr, it is working now, but for some reasons I had to upgrade vagrant to 1.8.1 and use ruby 2.1.6.
I am running the tests now. When this is finished I'll push the changes.

Although it was cool playing around with beaker for a full test environment, I've decided check only the parameters passed to the docker daemon.
So the problem I was having was when I run docker_full_spec, it reads the first lines and enables ip_forward and set default docker iptables
19       let(:pp) {"
20         class { 'docker': }
21       "}

Then add some context to the same describe section like
context 'disable docker\'s addition of iptables rules' do
  before(:all) do
    @pp =<<-EOS
      class { 'docker':
        iptables => false,
      }
    EOS
    apply_manifest(@pp, :catch_failures => true)
    # A sleep to give docker time to execute properly
    sleep 4
  end

  it 'should run idempotently' do
    apply_manifest(@pp, :catch_changes => true) unless fact('selinux') == 'true'
  end

  it 'should not enable iptables' do
    shell('iptables -L DOCKER') do |r|
      expect(r.stdout).to match(/0/)
    end
  end
end

But once ip_forward and iptables have been enabled,  it won't delete iptables DOCKER chain by itself after the daemon reloads with the new options.
I don't know, if you have better idea how to test it, feel free to point it out.
The result should not contain "Chain DOCKER"
ubuntu-1404-x64 14:33:07$ iptables -L DOCKER
  Chain DOCKER (1 references)
  target     prot opt source               destination

Anyways I think that the spec checks should be enough. What do you think?

@rchicoli yeah, I've solved that in other cases with matrix builds and different entry points, but for this test case and this feature I'm happy with your suggestion of the spec tests. Thanks

hey @garethr, good to know. I will keep that in mind.
Anyways I'm glad to contribute. The code has been rebased and I hope it's not a big deal the commit messages, because I didn't feel like rewriting the history today. Tell me if it is fine. Thanks and keep up the good work.

Btw I think the notify attribute on service.pp file should be changed to notify => $_manage_service, instead of Service['docker']
https://travis-ci.org/garethr/garethr-docker/jobs/107876029
https://github.com/rchicoli/puppet-docker/blob/systemd-options/manifests/service.pp#L183
if $_service_config {
  file { $_service_config:
    ensure  => present,
    force   => true,
    content => template($service_config_template),
    notify  => Service['docker'],
  }
}

don't you think so?
this is not related to this PR, so should I create a new one or do you create the hotfix by youself?

Thanks, merged. And the issue with Service is also fixed in master. Thanks!

authors: garethr rchicoli

repo: garethr/garethr-docker


text:
Can't recognise simple images

I am trying both Tesseract and SwiftOCR paraller. I have implemented your just 6 lines of code.
Tesseract recognise all images except your image (YourImage)
And SwiftOCR recognise only this image not others.
images.zip
Please help.

I am experiencing the same issue.  I believe you have to retrain the neural net powering SwiftOCR to handle different fonts.

P.S. to do the retraining, view the instructions towards the bottom of the main readme file.

I was getting garbage when I did a small test. The documentation for this framework is somewhat lacking and a lot of the issues have no response from the developer. I did the training, but how do you make use of the OCR-Network file that is created? I was really hoping this framework was going to do well for a few reasons:

It seems simpler than Tesseract
It supports Carthage (that's what I generally use for dependency management)
Any guidance and suggestions would be great!

SwiftOCR can't recognise multi line text. Only if you want to recognise short, single line alphanumeric strings (e.g. AB54ND84) you should consider using SwiftOCR.
@kevinmlong I developed SwiftOCR for a free time project (now I use a highly customised version of SwiftOCR) I have and never intended changing the OCR-Network File during runtime. You can change it, but it is a ugly solution with global variables (maybe I should rewrite SwiftOCR using better coding style 😉).
import SwiftOCR

recognizableCharacters = "abc...ABC...123" // Characters you trained SwiftOCR on (in the same order!)

let ocrNetworkURL = Bundle.main.url(forResource: "OCR-Network", withExtension: nil)! // URL of the OCR-Network file
globalNetwork = FFNN.fromFile(ocrNetworkURL)!

After setting the globalNetwork and the recognizableCharacters, you can use your custom OCR Network file.

authors: MlabTechnologies garnele007 kevinmlong yatendray


text:
Add iyaki.ar

Website (if applicable): https://iyaki.ar
This PR is:

[x] Adding a new domain
[ ] Updating existing domain
[ ] Changing domain name
[ ] Removing existing domain from list
[ ] Website code changes (darktheme.club site)
[ ] Other not listed

[x] The domain is in the correct alphabetical order
[x] The following information is filled identical to the data file

I confirm that I have read the FAQ page, particularly the red section about inappropriate content, and I attest that this site is appropriate based on those criteria.

[x] Check to confirm

Thanks!

authors: garritfra iyaki


text:
Wouldn't Load when sending email thru Ajax

Hi, I'm still learning to code.
I have a code where an ajax request is made to a PHP function and if the function succeeds, then an email is sent from within the said function.
I tried to implement this library and it works properly on all other ajax calls except this one.
I tried 3 methods

By Manually invoking $.LoadingOverlay("show") and $.LoadingOverlay("hide")
Via ajaxStart() and ajaxStop().
Via ajaxSend() and ajaxComplete()

The problem is, sending mails takes time and the overlay wouldn't start on the button click, it would show at the very end when the email is sent even if I manually trigger the overlay before the $.ajax({}); starts.
I'm not sure if I'm making a mistake, or maybe my concept of ajax is wrong.
But isn't the overlay/ajax call supposed to start when the user clicks a button and end when the task is completed?
I apologise in advance if this is a stupid question

You asked the same question here...

repo: gasparesganga/jquery-loading-overlay


text:
Inactive users showing in households

Index
Show

Member list
Photos

User household member list

Originally created by Tom Smyth at 2017-06-27 21:21, migrated from redmine-#6734

Status changed from New to Closed

By Tom Smyth at 2017-06-29 18:05

Version set to 4.3

By Tom Smyth at 2017-07-06 16:30

repo: gather-community/gather


text:
Display unit number on People page

From Elph:
In the Mess People directory it does not show unit number.
It is handy to know the unit number so that we can knock on their door if needed for a shift (or in the future delivering a meal.)
Can that be added to the feature request list?
Originally created by Willie Northway at 2016-11-27 16:35, migrated from redmine-#5468

Status changed from New to Cancelled

This is part of the existing plan, so cancelling. No need for separate issue.
By Tom Smyth at 2016-12-05 08:57


text:
HTTP: Can't assume response chunks usage when using a transformer

There's a chance the user wants to manually decode the bytes into a String, and then apply text based checks. But the original bytes might not be valid UTF-8.
Go with rawest InputStreamResponseBody instead of deciding based on checks.

false alarm

repo: gatling/gatling


text:
HTTP: StringBodyPart NPE in 3.8.2

Tl;dr

Upgraded from 3.7.6 to 3.8.2
Httpuploading a JPG does not appear to generate the "Content-Length" header
As a result POST Multipartformdata does not appear to succeed
fully working when downgrading back to 3.7.6

Code:
    public static HttpRequestActionBuilder UploadContent(String metadata, String filePath){
        return http("UploadContent")
                .post(URL_TO_SERVER)
                .header("Authorization", BEARER_TOKEN)
                .header("Content-Type", "multipart/form-data")
                .header("Connection", "keep-alive")
                .header("Accept", "*/*")
                .bodyPart(StringBodyPart("metadata", metadata))
                .bodyPart(RawFileBodyPart("file", filePath))
                .asMultipartForm();
    }

Exception in 3.8.2 when log level set to DEBUG:
java.lang.NullPointerException: null
        at java.base/java.lang.String.getBytes(String.java:963)
        at io.gatling.http.client.body.multipart.impl.StringPartImpl.<init>(StringPartImpl.java:29)
        at io.gatling.http.client.body.multipart.StringPart.toImpl(StringPart.java:49)
        at io.gatling.http.client.body.multipart.MultipartFormDataRequestBody.toChunkedInput(MultipartFormDataRequestBody.java:53)
        at io.gatling.http.client.body.multipart.MultipartFormDataRequestBody.build(MultipartFormDataRequestBody.java:62)
        at io.gatling.http.client.impl.request.WritableRequestBuilder.buildRequestWithBody(WritableRequestBuilder.java:67)
        at io.gatling.http.client.impl.request.WritableRequestBuilder.buildRequest(WritableRequestBuilder.java:113)
        at io.gatling.http.client.impl.HttpAppHandler.write(HttpAppHandler.java:112)

Upon examining the request it appears that it does not generate
Header from 3.7.6:
headers:
        Connection: keep-alive
        Authorization: {TOKEN HERE}
        Accept: */*
        host: {HOST HERE}
        content-type: multipart/form-data; boundary=wWbN8J-afqPrmMPIu1ykRW_XsJ7fbYyUk5-
        content-length: 3193874
body:MultipartFormDataRequestBody{boundary=[119, 87, 98, 78, 56, 74, 45, 97, 102, 113, 80, 114, 109, 77, 80, 73, 117, 49, 121, 107, 82, 87, 95, 88, 115, 74, 55, 102, 98, 89, 121, 85, 107, 53, 45], contentType='multipart/form-data; boundary=wWbN8J-afqPrmMPIu1ykRW_XsJ7fbYyUk5-', content=Part{name='metadata', charset=UTF-8, transferEncoding='null', contentId='null', dispositionType='null', contentType='null', customHeaders=, content={
  "customheaders" : "working"
}}

Header from 3.8.2:
headers:
        Connection: keep-alive
        Authorization: {TOKEN HERE}
        Accept: */*
        host: {HOST HERE}
        content-type: multipart/form-data; boundary=DWpzoA3CKc-AOSRgeEHJNhT0IdygFHC-U3f
body:MultipartFormDataRequestBody{boundary=[68, 87, 112, 122, 111, 65, 51, 67, 75, 99, 45, 65, 79, 83, 82, 103, 101, 69, 72, 74, 78, 104, 84, 48, 73, 100, 121, 103, 70, 72, 67, 45, 85, 51, 102], patchedContentType='multipart/form-data; boundary=DWpzoA3CKc-AOSRgeEHJNhT0IdygFHC-U3f', content=Part{name='metadata', charset=null, transferEncoding='null', contentId='null', dispositionType='null', contentType='null', customHeaders=, content={
  "customheaders" : "working"
}}

Thanks for reporting.
As a workaround, you can specify an explicit charset on your StringBodyPart:
.bodyPart(StringBodyPart("metadata", metadata).charset("UTF-8"))

authors: sagar-kalburgi-ripcord slandelle


text:
Add official starter with long lived backend API

@jasonbahl has a WPGQL demo content site living somewhere we can use for data.
As for the starter, we should fork a pre-existing well made starter and adapt it for WP.
@LekoArts do you have any suggestions on starters or themes you've made that would be good to fork (or use without forking if there's a way to do that)? I always hear you make the very best of them!

Hehe, thank you!
I think https://github.com/LekoArts/gatsby-starter-minimal-blog would be a good fit. It's my most popular blog starter and can probably be filled with content with the default Wordpress models. It has Pages and Posts and those Posts also can have Tags.
It's built on https://github.com/LekoArts/gatsby-themes/tree/master/themes/gatsby-theme-minimal-blog-core and https://github.com/LekoArts/gatsby-themes/tree/master/themes/gatsby-theme-minimal-blog.
Without forking option:
You could do something similar to https://github.com/LekoArts/minimal-blog-yaml - so fill the generic GraphQL interfaces with content from WordPress. I started doing this as a test with a local WP instance but never found time to do it. It would be really cool to do it this way because then I could directly link it as an alternative source than MDX.
However, I also understand if we don't want an official starter example rely on my upstream changes in the theme 😆
So with that in mind, you also have the option of forking it:
You could copy the contents of https://github.com/LekoArts/gatsby-themes/tree/master/themes/gatsby-theme-minimal-blog into the existing starter and then essentially do the same https://github.com/LekoArts/gatsby-themes/tree/master/themes/gatsby-theme-minimal-blog-core only with WordPress. Then you don't have any dependenies on those two themes and a "normal" starter (that doesn't rely on a theme).

Thanks @LekoArts ! Unfortunately the timeline for shipping this project has tightened by a lot :p So that means we'll be going with the most basic barebones starter I can find. Probably the official blog starter. Thanks for writing that all out though, and in the future we'll definitely reconsider when we have more time to spend on polishing things.

https://github.com/gatsbyjs/gatsby-starter-wordpress-blog

authors: LekoArts TylerBarnes


text:
进程被杀死

样本大的时候 产生val.txt文件大 到2G以上啦 这样建词汇表 是不是建不出来？是不是内存不够的关系？大概要什么配置才能顺利跑完所有数据？
是不是需要分布式建立？还是能训练结果逐步更新追加？
谢谢！

请问解决了吗，我也遇到了，样本集过大直接就kill了

authors: rzechen yeyicheng

repo: gaussic/text-classification-cnn-rnn


text:
Add Context, Failure, Formatter types (#71)

added context, failure & formatter types

Coverage remained the same at 93.955% when pulling e54eb9df7a2aa8d059c1d0e9d8fcfc27b98834e0 on Vedurumudi-Priyanka:context into 3dd83fcd5f57a3fe3c8b2674b2ec2c3475301afa on gavv:master.

Hi, sorry, but we already have #71 and #78. Thanks.

authors: Vedurumudi-Priyanka coveralls gavv

repo: gavv/httpexpect


text:
Fix catkin dependencies for demos

Add missing dependency on rqt_topic for ros_ign_gazebo_demos to package.xml.
🦟 Bug fix
Fixes: #276
Summary
Added missing packages to package.xml for demos package.
Checklist

[x] Signed all commits for DCO
[x] Added tests
[x] Updated documentation (as needed)
[x] Updated migration guide (as needed)
[x] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

I don't think we need to add some of the dependencies. For example *_controllers is something that is used with gz_ros2_control but these examples are not using this library.
Can you point me where is this package using all these controllers ?

Oops, sorry! I think I mixed this up with: https://github.com/gazebosim/ros_gz/pull/277
I updated this current PR with the single missing dependency on rqt_topic.

I don't think we need to add some of the dependencies. For example *_controllers is something that is used with gz_ros2_control but these examples are not using this library.
Can you point me where is this package using all these controllers ?

Oops, sorry! I think I mixed this up with: #277
I updated this current PR with the single missing dependency on rqt_topic.

I see I put the wrong issue link. For future reference, this is the other one I was working on simultaneously: https://github.com/ros-controls/ign_ros_control/pull/2


text:
Remove Cone shape from particle emitters

🦟 Bug fix
Summary
Cone shape particle emitters are not supported in gz yet. We should add this only when there is support for it, see https://github.com/gazebosim/gz-rendering/pull/1003#pullrequestreview-2082665533
Checklist

[x] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

cc @bperseghetti

cc @bperseghetti

Guess I don't have reviewer permissions on this repo......

repo: gazebosim/sdformat


text:
xml_generator_configuration_t.xml_generator_path default value

Hello. A small request for improvement.
Starting with Python 3.3 (https://docs.python.org/3/library/shutil.html) shutil package contains "which" function. From the doc: "... Return the path to an executable which would be run if the given cmd was called ..."
Since version 2.0 deprecates gccxml, pygccxml will have only 1 xml generator. If  "xml_generator_path" was not passed in init, the package can try to resolve castxml executable location via shutil.which functionality.
Thank you
P.S. I am still learning git, so no pull request at this time, sorry.

Thanks, I didn't know about this new function. As I want to still keep python 2.7 around, I will not be able to use this directly. But I think I will wrap this with a python 2.7/3.3 check, as this is an way more elegant way to fetch castxml's path.

That's now implemented in the develop branch with e2e213257557e54ecf10e78b0310909df84de6d6. Thanks for the hint.

authors: RomanYakovenko iMichka

repo: gccxml/pygccxml


text:
Bug report:

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behaviour or a link to the recipe / input used to cause the bug:

generete a qr code from any simple link or etc...
try to add text on it
See error

Looks working in my environment.
Generate QR Code, Add Text To Image - CyberChef

Version: 9.55.0
Compile time: 09/12/2022 11:42:13 UTC
User-Agent:
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/109.0
Link to reproduce

What error do you get and what is your environment (browser, etc.)?

this is what i get:

this is what i get:

The 'Add Text to Image' component has now been updated and I can no longer reproduce this issue.  Hopefully fixed, feel free to request I reopen this if not!

repo: gchq/CyberChef


text:
Coreset algorithm benchmarks for different data types

What's the new feature?
Explore opportunities to identify benchmarks for application of different coreset algorithms to different types of data, providing objective recommendations.
What value does this add?
This would give us greater insight into the application of different coreset algorithms to different data types, as well as providing a helpful starting point for users new to the package. This will help people apply and use the package more readily.
Is there an alternative you've considered?
No response
Additional context
This was a recommendation made during Sprint 15 Review.

Per @pc532627 there may be possible to combine this with #510

This becomes higher priority when recombination algorithms #71 and further alternative approaches are implemented.

If we're talking about integers vs floats, take care as JAX has some interesting behaviour.

repo: gchq/coreax


text:
🛑 Académie de la Truffe is down

In 44ba21a, Académie de la Truffe ($ACADEMIE_TRUFFE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Académie de la Truffe is back up in 333df9e.

repo: gcommeuneidee/upptime


text:
PydanticUserError

I havent been able to fix this
Exception has occurred: PydanticUserError
A non-annotated attribute was detected: substrate = LayerLevel(layer=(99999, 0), thickness=10.0, thickness_tolerance=None, zmin=-13.0, material='si', sidewall_angle=0.0, sidewall_angle_tolerance=None, width_to_z=0.0, z_to_bias=None, mesh_order=99, layer_type='grow', mode=None, into=None, doping_concentration=None, resistivity=None, bias=None, derived_layer=None, info={}). All model fields require a type annotation; if substrate is not meant to be a field, you may be able to resolve this error by annotating it as a ClassVar or updating model_config['ignored_types'].
For further information visit https://errors.pydantic.dev/2.7/u/model-field-missing-annotation

Hi @chamithri-A,
I also ran into this a recently, and from what I understand, pydantic is essentially a type checker - do you encounter the same error if you add type hints to your attributes?
for example, do you get the same error if you try putting
substrate: LayerLevel = LayerLevel(layer=(99999, 0), ...

authors: chamithri-A fp-matt

repo: gdsfactory/gdsfactory


text:
Fixing existing code does not work again

Bug description
I generated metagpt project. But I am not satisfied with dummy logic implementation. I want to apply corrections to generated project
I tried:
--project-path ... --inc
and
--project-path ... only
The docs and resources changes. But the generated code doesn't. The .py code files in project does not change. The new file mentioned in log are not created.
Running metagpt on existing project doesn't call metagpt.actions.write_code:run. Only metagpt.actions.write_code_plan_and_change_an:run.
Does metagpt support applying new requirements to project?
Bug solved method
Have not tried to solve yet.
Environment information
Debian, python=3.11.2-1+b1, venv,
I have this bug as on pip metagpt version, as on newest metagpt github release.
Model gpt-3.5-turbo

According to the document, there are still some unresolved issues in incremental development.

I've consolidated all the incremental development-related issues into #1498 to make it easier to follow up. Any new issues will be discussed in this newly opened issue, and the old issue will be closed.

authors: AndPim4912 iorisa seehi

repo: geekan/MetaGPT


text:
Update to python3

Some  files have the following problems.
#437 #391
The problem is that both python3 and python2 are used in function.
So, I would like to take it up for the rest of the files, if no one else is working on it.

1

authors: fanjindong jinyoungHan

repo: geekcomputers/Python


text:
Encountered Error - New to Ansible - Not sure what to look for to correct ?!?

Here is a copy of the output I'm getting where the error occurs.
TASK [Copy templated internet-monitoring files into place.] ************************************************************************
ok: [x.x.x.x] => (item={'src': 'grafana-config.monitoring.j2', 'dest': 'grafana/config.monitoring'})
changed: [x.x.x.x] => (item={'src': 'prometheus.yml.j2', 'dest': 'prometheus/prometheus.yml'})
ok: [x.x.x.x] => (item={'src': 'prometheus-pinghosts.yaml.j2', 'dest': 'prometheus/pinghosts.yaml'})
TASK [Ensure internet-monitoring environment is running.] **************************************************************************
fatal: [x.x.x.x]: FAILED! => {"changed": false, "msg": "Error connecting: Error while fetching server API version: ('Connection aborted.', PermissionError(13, 'Permission denied'))"}
RUNNING HANDLER [Restart internet-monitoring] **************************************************************************************
PLAY RECAP *************************************************************************************************************************
x.x.x.x : ok=11 changed=2 unreachable=0 failed=1 skipped=8 rescued=0 ignored=0
I surprised myself in getting this far on what was basically my first attempt to run an actual play book using Ansible beyond reading about it. Any clues / hints on how I should proceed would be much appreciated :)

@BEMORLDEV, I was running into this problem too.  I found the same error in Issue #324, where it was suggested to reboot the Pi.  I did so and got past this error.  If you haven't already, I'd recommend that you try rebooting too.
If you still run into issues, try adding the following line to ~/internet-pi/ansible.cfg
log_path = ./ansible.log

That should create a new at ~/internet-pi/ansible.log - it's just a persistent log for console output.  Next, run ansible-playbook main.yml -vvv.  The -vvv will give more verbose output.  And since it's writing to a log, it should make reviewing any more failures a little easier.
Hope this helps!  Good luck!

Im receiving the same message and when running docker-compose up in the internet monitoring folder i get:
ERROR: Couldn't find env file: /home/eclipse/internet-pi/internet-monitoring/grafana/config.monitoring

Hi @EclipseOfficeTech,
have you checked the closed issues that have the same problem?
https://github.com/geerlingguy/internet-pi/issues?q=is%3Aissue+is%3Aclosed+Error+while+fetching+server+API+version
I think in most cases the user specified in inventory.ini was not part of the docker group.
That's why usually a reboot is recommended as the user was just added to the group and this still needs to be recognised by the system.

I'm still seeing this error whenever I try to run the ansible script. I've double checked and the pi user is part of the docker group. The only other thing that might be different for me is that I had to install docker-compose via Apt instead of Pip to get around the error described in https://github.com/geerlingguy/internet-pi/issues/445

This is a docker permission issue. I followed this script to fix: https://stackoverflow.com/questions/64662372/docker-compose-up-error-while-fetching-server-api-version-connection-aborte
sudo gpasswd -a $USER docker
newgrp docker

authors: BEMORLDEV EclipseOfficeTech aht kreekles martinbrose sdcinglis

repo: geerlingguy/internet-pi


text:
Fix m5term select issues

Running m5term on Ubuntu (Linux on Windows) fails with no STDIN input.
This is due to several unexpected sanity checks in readwrite() polling
loop.
Returning 0 from select() means timeout which should be expected as there
is a 1 second timeout set to the select().
And it is actually no need to perform "read(nfd) < 0" sanity checks.
This patch fixes the select() loop related issues.
Signed-off-by: Lv Zheng zhenglv@smart-core.cn

How can I get a trace from gem5 sim.

Do you mean InstTracer, like something enabled by --debug-flags=Exec?
If so, it doesn't appear on m5term, but goes along in the gem5.opt output.
I think all outputs visible in m5term can be found in m5out/system.terminal.
If we want to end the m5term, we can just ctrl+c gem5 side, then the m5term can automatically exit.

We cannot access googlesource.com here from China.
However github.com doesn't work.

authors: cghalibkhan zetalog


text:
arch-riscv: squash walks with tlb hits in startWalkWrapper

Because each vector load is fragmented into 64 byte cache-aligned chunks, and one page-table walk is issued per fragment on tlb miss, walks start to accumulate on a pending queue, which is processed in a blocking way (no pending walks can be issued while one is being processed). This adds noticeable latency on vector loads when VLEN is sufficiently large.
This commit fixes the issue by allowing walks to be squashed if a TLB lookup hits just before starting the walk on startWalkWrapper. This idea was taken from the ARM walker.

The current test failing in our CI is due to the pull-request not containing a change ID. The easiest way to solve this is with the following:
n f=.git/hooks/commit-msg ; mkdir -p  ;  curl -Lo  https://gerrit-review.googlesource.com/tools/hooks/commit-msg ; chmod +x \n
git commit --amend --no-edit
This will add a change ID to the commit at the HEAD of the pull request.
To avoid this going forward we strongly recommend using our pre-commit git hooks. To install execute util/pre-commit-install.sh in the gem5 repo. These git hooks automatically add Change-IDs to a commit and run our style checks on code you have added or altered.

Thanks. Should be good now. Tell me otherwise if something is missing or has to be changed.

Thanks. Should be good now. Tell me otherwise if something is missing or has to be changed.

THanks for the contribution. This appears to be working fine. I'll merge it.


text:
-t option used on an unknown chart

When the -t option is used to target a chart that indeed does not exist, no error is raised and the execution of Spray silently continues/ends.
It would be better to at least have a warning printed in the logs, or even fail in error

Closed by https://github.com/gemalto/helm-spray/pull/42

repo: gemalto/helm-spray


text:
fix window.global

Gemini не делает снимок области по селектору если в контексте страницы есть window.global.
substack/node-browserify#1189

@SwinX

@eroshinev сори, но тебе надо бы отребейзиться от мастера ещё раз =) Твой PR родил уникальный кейс, при котором у нас свалились браузерные тесты. Кажется, что вот этим падения полечатся и я наконец-то смогу принять изменения.

Сделал.

Спасибо!

authors: SwinX eroshinev

repo: gemini-testing/gemini


text:
muscle cell vs muscle fiber

GO distinguishes between muscle cell and muscle fiber. However, in CL these are exact syns.
id: CL:0000187
name: muscle cell
def: "A mature contractile cell, commonly known as a myocyte. This cell has as part of its cytoplasm myofibrils organized in various patterns." [MESH:A11.620]
synonym: "muscle fiber" EXACT []
synonym: "myocyte" EXACT []
I am sure we made the same decision in GO many years ago.
However, the distinction has bounced back
e.g.
GO:0048747 ! muscle fiber development [DEF: "The process whose specific outcome is the progression of the muscle fiber over time, from its formation to the mature structure. Muscle fibers are formed by the maturation of myotubes. They can be classed as slow, intermediate/fast or fast."]
GO:0055001 ! muscle cell development ***  [DEF: "The process whose specific outcome is the progression of a muscle cell over time, from its formation to the mature structure. Muscle cell development does not include the steps involved in committing an unspecified cell to the muscle cell fate."]
This is blocking some changes to the xp file Heiko and I need to make.
EQUIVALENT_CLASS_PAIR: EquivalentClasses(
GO:0048739 'cardiac muscle fiber development'
GO:0055013 'cardiac muscle cell development' )
EQUIVALENT_CLASS_PAIR: EquivalentClasses(
GO:0048747 'muscle fiber development'
GO:0055001 'muscle cell development' )
I suggest we merge fiber into cell.
See attached image.
But there are other less serious problems at the terminological level. E.g.
GO:0014856 ! skeletal muscle cell proliferation
GO:0035914 ! skeletal muscle cell differentiation
GO:0043503 ! skeletal muscle fiber adaptation
GO:0048741 ! skeletal muscle fiber development
note that CL doesn't even include 'skeletal muscle fiber' as a syn of 'skeletal muscle cell' (presumably it should)
I suggest we always use the CL term as the primary label
Reported by: cmungall
Original Ticket: geneontology/ontology-requests/10199

@cmungall  can you comment how we can close this? It seems to be about alignment with  CL and equivalence blah blah....

The term "muscle fiber development" should not logically mean muscle myofibril development because the IS_A relationship to "striated muscle cell development". "striated muscle cell development" IS_A "muscle cell development".
"muscle fiber development" has two is_a children "cardiac muscle fiber development" and "skeletal muscle fiber development".
Thus I suggest that we deprecate "muscle fiber development"; move its annotations to "muscle cell development" and rename "X muscle fiber development" to "X muscle cell development" and make them IS_A children of "striated muscle cell development".
I looked at the refs supporting several direct annotations of "muscle fiber development", from MGI, ZFIN, FB, and WB, and found that they can all be annotated with "muscle cell development". One WB paper described muscle filament defects of some pharyngeal muscle cells.

Sure - the only issue is there are 80 EXP annotations. If we believe that another term is equivalent, we would do a merge (for convenience for curators).

Yes, merge is a good idea.

I'm OK with a merge here

In Cell Ontology, there is CL:0008002 ! skeletal muscle fiber with the Definition: A transversely striated, synctial cell of skeletal muscle. It is formed when proliferating myoblasts exit the cell cycle, differentiate and fuse.
Thus I suggest we keep the "skeletal muscle fiber" part in GO terms, not changing them to "skeletal muscle cell".

Remove synonyms of "muscle fiber/fibre" from contractile fiber terms. In general, the common usage of "muscle fiber" refers to a muscle cell rather than some actin/myosin filiments.

authors: ValWood cmungall gocentral pgaudet raymond91125

repo: geneontology/go-ontology


text:
neuron projection branch point

I would like to see "neuron projection branch point” added to the GO ontology under the parent term "neuron projection” (GO:0043005).  It would also be a new parent of “dendritic branch point” (GO:1990033).  The definition could be "The location where a secondary projection arises from a neuron projection.” Example can be found in PMID:25586189.

[Term]
+id: GO:0061845
+name: neuron projection branch point
+namespace: cellular_component
+def: "The location where a secondary projection arises from a neuron projection." [PMID:25586189]
+is_a: GO:0044463 ! cell projection part
+relationship: part_of GO:0043005 ! neuron projection

authors: slaulederkind ukemi


text:
OTR: Comment on GO:0019060 intracellular transport of viral protein in host cell

The stanza for GO:0019060 intracellular transport of viral protein in host cell includes the following comment:

This term is for annotation of the movement of individual viral proteins, rather than the whole viral particle.

It seems like this comment is misleading in that it can be read to suggest that viral protein cargoes should be annotated to GO:0019060. But the existing experimental annotations are more consistent with our practice for use of protein localization terms. The annotations are to cellular proteins involved in the movement of viral cargoes, not viral proteins being moved.

Hi @jimhu-tamu
You are right, this term is not very clear. The synonyms are confusing and the usage is very inconsistent.
pmasson55 your suggestions are welcome !
Pascale

I agree this term is very misleading and should be improved. It seems that Interpro used it to annotate the adenovirus shutoff protein that acts as a chaperone to the hexon protein and directs it to the host nucleus. However this term has also been assigned to mammalian proteins. In addition, the synonym terms are also misleading: viral capsid transport in host cell nucleus, intracellular viral protein transport, intracellular viral capsid transport and viral capsid transport in host cell cytoplasm are complete different concepts and shouldn't be used as exact synonyms. So I suggest to remove this misleading GO term or change it to be more accurate.

Hi @pmasson55 ,
Thanks for the input.Do you have suggestions for re-housing the existing annotations?
Thanks, Pascale

I agree that the comment and synonyms are confusing. But it seems to me that being used for proteins encoded by both the host and the virus is not a problem if we agree that this is not about annotating cargoes. Perhaps it's reviewing the practice for the parent term GO:0006886 intracellular protein transport more thoroughly,  but a cursory look at that is consistent with my understanding of how protein localization terms have been annotated. Machinery, not cargoes.
But I suspect that this touches on the other issue @pgaudet and I have been discussing about what constitutes a cellular vs host cellular process.

We may propose to obsolete. Currently reviewing existing annotations:
F1SF88	-
P09914	IFIT1
P63172	DYNLT1
Q03518	TAP1
Q03519	TAP2
Q9BUN8	DERL1
InterPro:IPR003381
Thanks, Pascale

The GO editors usually provide the source of these annotations as it is not efficient having 13 groups all checking to see if they created these annotations
Thanks
Ruth

Hi Ruth,
Indeed ! Sorry I omitted the 'I' in the previous comment "Currently reviewing existing annotations with @pmasson55"; if there are questions/suggestions for changes we will contact the appropriate groups.
Pascale

Changed the comment to "This term is for annotation of proteins responsible for the movement of individual viral proteins, rather than the whole viral particle. "

[ ]  Fixed axioms referring to 'cell', 'nucleus' etc rather than 'host cell', host cell nucleus', etc
[ ]  Must fix (remove?) synonyms:
viral capsid transport in host cell nucleus,
intracellular viral protein transport,
intracellular viral capsid transport and
viral capsid transport in host cell cytoplasm

authors: RLovering jimhu-tamu pgaudet pmasson55


text:
term merge sodium ion export from cell?

is there a difference between this and  (only) child
GO:0098667    sodium ion export across plasma membrane
?

I had done that for import, I am not sure I checked export.
Thanks for pointing it out,
Pascale

If we only think it ever happens by movement across the membrane and never by another mechanism such as exocytosis. I did a quick search and couldn't find evidence to the contrary.

The parent of the current export term is transmembrane transport.

Then I think it makes sense to merge as long as the parent wasn't added incorrectly. Have you done a sanity check on the existing annotations? Are they all transporters/channels?

I think we  established this when Pascale did the import terms. Only known 'directed movement' is transmembrane.

Also merged 'potassium ion export from cell' (no annotations) into 'potassium ion export across plasma membrane'

authors: ValWood pgaudet ukemi