text:
Support EU-OSK103

Describe the bug （描述一下问题）
With midea-discover I can scan my AC but after that I see only errors, you can see it in the log.
With home assistant I have only empty entitys.
Screenshots / Logs / Pcap File（屏幕截图/日志/抓包文件）

fabio@fabio-ubuntu:~$ midea-discover -d
INFO:msmart.cli:Debug mode active
INFO:msmart.cli:msmart version: 0.1.35 Currently only supports ac devices.
INFO:msmart.cli:Sending Device Scan Broadcast...
DEBUG:asyncio:Using selector: EpollSelector
DEBUG:msmart.scanner:Broadcast message sent: 0
DEBUG:msmart.scanner:Midea Local Data 192.168.1.77 837000c8200f00005a5a0111b8007a800000000004a8270b150b151463d40200001d0000000000000000018000000000436ee59185981acb80953897076f587787ebb386550d89a3c21abce6b500afc6ff9ba3eb53ca23c00d8f8eab3d45f8da1df38bcb21798b124621b72cc562e17b9da346cfc3769eff509ce3f73eca554306c867e13b66bf3c47ad04339bcf76ae4bdfb3e16e33d88768cc4c3d0658937d0bb19369bf0317b24d3a4de9e6a13106b8448ff8a89cfacf3682a621c04122189e7f9eb4015f4df1b13d3f0c26aa2bf6
DEBUG:msmart.scanner:Decrypt Reply: 192.168.1.77 4d01a8c02c19000030303030303050303030303030305131413834303744394536383031303030300b6e65745f61635f363830310000870002000000000000000000ac00acac00000000a8407d9e6801150029082115000302000000000000000000000000000000000000000000000000000000000000000000
DEBUG:msmart.scanner:Midea Local Data 192.168.1.160 837000b8200f05425a5a0111a8007a8000000000000000000000000045e803000011000000000000000000000000000098c515ed3fea64df13e0c27b61e84fcb87ebb386550d89a3c21abce6b500afc6501b4983ef9cc3d51b7343512d1bc06850f3120e864eca588b828b69af80922be703a83ed4af68f9e390a73cf240c57c8bb9e6e39726e7af22ed2adc38c30dc6f31443d17c3aac03a7656614ae1dca44dd689654bd13f0d8066ea95ecf95bcc7db24e0db2789dc7fa79f21ab43182f2f
DEBUG:msmart.scanner:Decrypt Reply: 192.168.1.160 a001a8c02c19000030303030303050303030303030305131413834303744394544343334303030300b6e65745f61635f443433340000000001000000040000000000ac00000000000000a8407d9ed434069fcd0300080103030000000000000000000000000000000000000000
DEBUG:msmart.scanner:Midea Local Data 192.168.1.228 837000b8200f05f05a5a0111a8007a800000000000000000000000003ded0200001d000000000000000000000000000071c689dfb128a5aa89f849a63ce651bf658e482a575f9f149308534ec98af6b04b54e339bd26465187e16d44f468f37cd10bd84e5ef2bcad2067702602c92dce3bca28212f56810da1e08db0898079f58bb9e6e39726e7af22ed2adc38c30dc6f31443d17c3aac03a7656614ae1dca443b3143974cb5ae4f0d2c7e19115082934f213ca11b4728a4f55266e617c4a1b3
DEBUG:msmart.scanner:Decrypt Reply: 192.168.1.228 e401a8c02c19000030303030303050303030303030305131413834303744394337383632303030300b6e65745f61635f373836320000000001000000040000000000ac00000000000000a8407d9c7862069fcd0300080103030000000000000000000000000000000000000000
DEBUG:msmart.scanner:Midea Local Data 192.168.1.110 837000b8200f045d5a5a0111a8007a8000000000000000000000000098520300001d0000000000000000000000000000e8a2e2d38d7fd43fc24fdf7dd6020cd987ebb386550d89a3c21abce6b500afc63903ef171d34b30c8c8e56fb5c961dc58a6b8a236949fc24c775498c2712c9f4143466ca547091736cbb7faa6b439fa2a50bc4cd412f1ce53b276a62d7412834f31443d17c3aac03a7656614ae1dca44d52cb203821bc325826660244cca402980b7056e18ab1501297cc700fedf1abd
DEBUG:msmart.scanner:Decrypt Reply: 192.168.1.110 6e01a8c02c19000030303030303050303030303030305131413834303744394544343032303030300b6e65745f61635f443430320000000001000000040000000000ac00000000000000a8407d9ed402069fcd0300080103020000000000000000000000000000000000000000

DEBUG:msmart.scanner:Socket timeout
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login/id/get HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"ok","result":{"loginId":"a8341370-9bb4-4f64-8024-9f734d1b4392"},"errorCode":"0"}
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login/id/get HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"ok","result":{"loginId":"39108674-f532-4336-9126-1420ec733e1f"},"errorCode":"0"}
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login/id/get HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"ok","result":{"loginId":"a45a2baa-a190-4f48-831e-3b22d5c3832b"},"errorCode":"0"}
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login/id/get HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"ok","result":{"loginId":"c1b92efc-c4bb-40b5-ac97-0030f1236dea"},"errorCode":"0"}
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"password error，please enter again.","errorCode":"3101"}
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"login failed, loginId is empty, please login again.","errorCode":"3144"}
DEBUG:msmart.cloud:Restarting full: '3144' - 'login failed, loginId is empty, please login again.'
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"login failed, loginId is empty, please login again.","errorCode":"3144"}
DEBUG:msmart.cloud:Restarting full: '3144' - 'login failed, loginId is empty, please login again.'
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"login failed, loginId is empty, please login again.","errorCode":"3144"}
DEBUG:msmart.cloud:Restarting full: '3144' - 'login failed, loginId is empty, please login again.'
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login/id/get HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"ok","result":{"loginId":"5f743393-3a19-4215-b9a8-431ba38adccd"},"errorCode":"0"}
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login/id/get HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"ok","result":{"loginId":"88f11b81-9378-434b-97fe-7d5a8bc46c9d"},"errorCode":"0"}
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login/id/get HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"ok","result":{"loginId":"a2376205-7ea5-447a-86e3-28dfcdf109d4"},"errorCode":"0"}
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"password error，please enter again.","errorCode":"3101"}
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"login failed, loginId is empty, please login again.","errorCode":"3144"}
DEBUG:msmart.cloud:Restarting full: '3144' - 'login failed, loginId is empty, please login again.'
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"login failed, loginId is empty, please login again.","errorCode":"3144"}
DEBUG:msmart.cloud:Restarting full: '3144' - 'login failed, loginId is empty, please login again.'
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login/id/get HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"ok","result":{"loginId":"70672eee-6bf4-4e79-80f7-f0eb4df1e775"},"errorCode":"0"}
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login/id/get HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"ok","result":{"loginId":"cc2b7fcd-a88a-4c82-a347-49714ed7478b"},"errorCode":"0"}
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"password error，please enter again.","errorCode":"3101"}
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"login failed, loginId is empty, please login again.","errorCode":"3144"}
DEBUG:msmart.cloud:Restarting full: '3144' - 'login failed, loginId is empty, please login again.'
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login/id/get HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"ok","result":{"loginId":"bc8b4697-0b9b-4412-9a5e-fbc6ec886826"},"errorCode":"0"}
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"ok","result":{"originPrivateVersion":"","nickname":"midea_is_best@outlook.com","sessionId":"44c4ad60ee2d47518cb6339f937f424b20211121113948973","accessToken":"fe2658f1e2a821091586ad4af58efd8db920ebb829d567559397ded751813801","userId":"4826094","versionCode":"","leftCount":""},"errorCode":"0"}
DEBUG:msmart.cloud:Retrying API call: 'user/login'
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"login failed, loginId is empty, please login again.","errorCode":"3144"}
DEBUG:msmart.cloud:Restarting full: '3144' - 'login failed, loginId is empty, please login again.'
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login/id/get HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"ok","result":{"loginId":"bfa28fb9-ac3e-429e-b52a-d0618b6cdaa3"},"errorCode":"0"}
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"ok","result":{"originPrivateVersion":"","nickname":"midea_is_best@outlook.com","sessionId":"44e2f5cefceb4e5cbe715a0d124f4d3d20211121113949709","accessToken":"5f35d4224d9d9acfc04825f32e8a1d08b920ebb829d567559397ded751813801","userId":"4826094","versionCode":"","leftCount":""},"errorCode":"0"}
DEBUG:msmart.cloud:Retrying API call: 'user/login'
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"login failed, loginId is empty, please login again.","errorCode":"3144"}
DEBUG:msmart.cloud:Restarting full: '3144' - 'login failed, loginId is empty, please login again.'
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login/id/get HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"ok","result":{"loginId":"d390668c-4d8e-4250-ae7e-95be94b04f2a"},"errorCode":"0"}
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"ok","result":{"originPrivateVersion":"","nickname":"midea_is_best@outlook.com","sessionId":"21732a6a9f1840c1a540ea6b68343c0720211121113950384","accessToken":"1817202854b5460385dab2e4012ad92cb920ebb829d567559397ded751813801","userId":"4826094","versionCode":"","leftCount":""},"errorCode":"0"}
DEBUG:msmart.cloud:Retrying API call: 'user/login'
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"login failed, loginId is empty, please login again.","errorCode":"3144"}
DEBUG:msmart.cloud:Restarting full: '3144' - 'login failed, loginId is empty, please login again.'
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login/id/get HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"ok","result":{"loginId":"aeb165bf-34ab-4698-8e88-47a651afb474"},"errorCode":"0"}
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"ok","result":{"originPrivateVersion":"","nickname":"midea_is_best@outlook.com","sessionId":"4b436469fa73481a939af1c68ae8e00a20211121113951030","accessToken":"5e3540de8325f52fce8a572a5d9799e0b920ebb829d567559397ded751813801","userId":"4826094","versionCode":"","leftCount":""},"errorCode":"0"}
DEBUG:msmart.cloud:Retrying API call: 'user/login'
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"login failed, loginId is empty, please login again.","errorCode":"3144"}
DEBUG:msmart.cloud:Restarting full: '3144' - 'login failed, loginId is empty, please login again.'
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login/id/get HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"ok","result":{"loginId":"0d61862c-c9a5-4885-8056-3763a18fc6ec"},"errorCode":"0"}
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"ok","result":{"originPrivateVersion":"","nickname":"midea_is_best@outlook.com","sessionId":"fd87db61d9a1473cb7f451ef354a2da720211121113951670","accessToken":"99da0f069ab9fefbf74cb983e61e41cfb920ebb829d567559397ded751813801","userId":"4826094","versionCode":"","leftCount":""},"errorCode":"0"}
DEBUG:msmart.cloud:Retrying API call: 'user/login'
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
DEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"login failed, loginId is empty, please login again.","errorCode":"3144"}
DEBUG:msmart.cloud:Restarting full: '3144' - 'login failed, loginId is empty, please login again.'
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443
^CDEBUG:urllib3.connectionpool:https://mapp.appsmb.com:443 "POST /v1/user/login/id/get HTTP/1.1" 200 None
DEBUG:msmart.cloud:Response: {"msg":"ok","result":{"loginId":"74e2262b-2ff8-4134-a23f-5249be29a592"},"errorCode":"0"}
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): mapp.appsmb.com:443

Versions (版本信息)

Home Assistant version: core-2021-11-4 Home Assistant OS
Midea msmart version: 0.1.35
Dongle WiFi: EU-OSK103

I don't if this is a bug or a feature request.
Thanks for your work.
p.s. I also wrote on Telegram, but I have not received a reply

new version 0.1.36 fixed this issues，please try.

authors: BigMiura mac-zhou

repo: mac-zhou/midea-ac-py


text:
API reference

Addresses https://github.com/mackelab/sbi/issues/109 using mkdocstrings.

To test this locally, check out the branch and follow the instructions in docs/README.md.

The docstrings look good to go. I don't know why the docs building failed, though.

source: gharchive/pull-request

authors: jan-matthis meteore

repo: mackelab/sbi

license_type: permissive

license_source: github-api


text:
Integrate lightning transactions

Minting and trading tokens should use real lightning transactions

Purchasing NFTs is working, but payouts (to creator, seller, and market owner) still TBD

Added LN deposit address to profile

Payouts to seller now working https://github.com/macterra/artx-market/commit/24349ef863ce969defac44d8bc496e4b8797be4e
TBD royalties and transaction fee

Completed with https://github.com/macterra/artx-market/commit/c577e0d9f29867c08cabc1db84cc3efd82393ee1

source: gharchive/issue

repo: macterra/artx-market

license: MIT


text:
Ignores NaturalRegen setting in Minecraft

Minecraft: 1.18.1 Forge: 39.0.64 It ignores NaturalRegen: False. Furthermore it tries to heal even when healingPerSecond is set to 0 in the configs causing hunger to decrease despite no regen occurring.

Please provide a pastebin of your configuration file.
Thanks!
MacTso

Sorry it took so long to get this. I wasn't at my PC when I noticed the message. https://pastebin.com/RsZgLNGq

It's okay.  I had two other issues tonight.   I'll look at this tomorrow.
It might be minecraft is doing it if you are wounded.
Thanks for the config.  How many hit points was your man at (roughly)?
Cheers,
MacTso

Okay so it is currently adding 0.0 extra exhaustion once per second when you are hurt.
This is mostly cosmetic (since it's 0.0) but it is a small performance drain so I can  I can make a change so it doesn't do the operation unless the extra exhaustion is greater than 0.
It's also "healing 0.0 damage" once per second.   I can also add a check for 0 on that so it only runs if the hardernaturalhealing amount is over 0.0.

I put in a fix for this but realized later that it is intended to cause extra exhaustion when you are wounded.  So later I'll be putting in a fix that if that is non-zero, it will apply it once per second if you are wounded.  If it is zero it will skip over the code silently.

repo: mactso/HarderNaturalHealing


text:
unamed wilds do not register

i tried the solution u gave for infernal mobs .
with untamed wilds , biomesoplenty and clean minecraft.
somehow sbu doesnt pick up on them like they are not even in .
any solution to that?

I'll have to take a look at it.  The main reason I can think of would be they are generated during world generation and not spawned.
I wouldn't be able to fix that.  Tho you could add them to SBU spawn tables and they should spawn.
I'm unfamiliar with untamed wilds.  I'll take a look at their entity spawn code now.

repo: mactso/SpawnBalanceUtility


text:
Pool Public Key (48 bytes) needs to be specified via -p , see chia keys show.

can help me pls ?

I had the same problem. The temp folder and all other folders cannot be named "temp folder" must be "temp_folder". Now I don't get a warning anymore, but after starting it stops after a few seconds. :(
I only get this:
Final Directory: E:\Farm_3
Number of Plots: 1
Process ID: 7408
Number of Threads: 8
Number of Buckets: 2^7 (128)

You can also use quotes around the path if spaces are involved.

If it stops after Number of Buckets: 2^7 (128) that's a know issue, we are trying to fix it, see #126

You can also use quotes around the path if spaces are involved.

I tried with and without quotes, the same thing happens

Eu consegui tirando o nome "temp" dos destinos e reinstalando o pacote c++ visual


text:
Telemetry: Removing Excess Data

Telemetry is growing to be very large and is only going to get even larger when 5v5 roles around. That's an extra 4 players with extra objects, AI and much more. There is a big need of removing any Excess Data that can be assumed to be the case already.
Executed
For example, the Executed event shows when a non-player kills a player, such as Kraken or a minion killing a player. We know that no gold is gained from this, isHero is obviously false just from the event, targetIsHero is obviously true from the event. The Team of the AI can also be easily assumed as well in my opinion. Any turrets killing it will be opposite of KilledTeam. Any Jungle creeps killing, the team can be determined using Position. A lot of this data is excess and can be removed to help lower the size of Telemetry. As I spend more time working with Telemetry I will try to add more examples of data that can be removed.
	{
	    "time": "2017-06-13T06:43:40+0000",
	    "type": "Executed",
	    "payload": {
	        "Team": "Left",
	        "Actor": "*JungleMinion_TreeEnt*",
	        "Killed": "*Samuel*",
	        "KilledTeam": "Left",
	        "Gold": "0",
	        "IsHero": 0,
	        "TargetIsHero": 1,
	        "Position": [
	            -41.82,
	            0.01,
	            27.02
	        ]
	    }
	}

GoldFromTowerKill/GoldMine/KrakenKill
When a player earns gold from the destruction of a turret belonging to the enemy team. These events occur 3 times for each event. When a tower is destroyed every team member gains 300 gold. There is no need to make 3 separate events. Simply create 1 event as shown below. All that is necessary is which team gained the gold and how much. Although technically Amount can be assumed, I believe it is better to keep it in there in case different maps reward different amounts or amounts change in future updates.
	{
		"time": "2017-03-31T02:57:02+0000",
		"type": "GoldFromTowerKill",
		"payload": {
			"Team": "Left"
			"AmountEach": 300
		}
	}

NPCkillNPC
When one non-player actor kills another, such as the Kraken or a minion killing a turret. Once you know the KilledTeam it is easy to know the Team. IsHero and TargetIsHero are unnecessary as it is NPC killing NPC.  To be honest I think ALL cases of IsHero and TargetIsHero can be removed as they can inferred and rarely would they have a use case. Just by knowing who died and who killed and event these two can be inferred. If needed a json file can be created in resources folder to keep a list of all NPC.
	{
		"time": "2017-03-31T03:07:21+0000",
		"type": "NPCkillNPC",
		"payload": {
			"Team": "Left",
			"Actor": "*Kraken_Captured*",
			"Killed": "*Turret*",
			"KilledTeam": "Right",
			"Gold": "300",
			"IsHero": 0,
			"TargetIsHero": 0,
			"Position": [
				54,
				0,
				2.92
				]
		}
	}

EarnXP Event
XP Earned can only occur when a hero kills something. This is the same case as Gold Earned. All cases of XP Earned having its own separate event is unnecessary and may cause bloating of the Telemetry. Consider moving it inside the KillActor Event.
Example:
{
		"time": "2017-03-17T00:39:09+0000",
		"type": "KillActor",
		"payload": {
			"Team": "Left",
			"Actor": "*Koshka*",
			"Killed": "*JungleMinion_TreeEnt*",
			"KilledTeam": "Neutral",
			"XP Amount": 67,
			"XP Shared With": 1
			"Gold": "80",
			"IsHero": 1,
			"TargetIsHero": 0,
			"Position": [
				-21.95,
				0,
				24
			]
		}
	}

Hero Swaps/Skin Changes
I am not sure if any developer has any use case for these events. I have seen many times (I myself am guilty of this) of swapping heroes constantly with another person until there are about 2 seconds left. We swap about 20 times and that is 20 events. Imagine have 10 people doing this. The swapping is going to get insanely high and Skin Changes as well. Perhaps if every developer can agree that these events are useless and the only ones that matter are the final selected Skin and Hero.
Level Up/Learn Abilities/PlayerFirstSpawn Events
At the beginning of a match when can we convert all these events into 1 giant PlayerFirstSpawn Event? I personally don't think there is any use case for having separate events. Once again need developer input here if someone does have a use case for them. Note this is only for those first 25 seconds after the match starts where all these events are spammed. Other Level Up and Learn Ability Events that occure after the first 25 seconds should still be maintained separately.
Example:
{
        "timeStart": "2017-08-06T20:43:06+0000",
        "timeFinish": "2017-08-06T20:44:06+0000",
        "type": "PlayerFirstSpawn",
        "payload": {
            "Team": "Left",
            "Actor": "*Kestrel*",
            "LevelsGained": 4, **This will indicate how many level events occured. AKA This is a Battle Royale since 4 levels**
            "AbilityALevels": 3, **This will indicate the hero upgraded the A ability 3 times.
            "AbilityBLevels": 1, **This will indicate the hero upgraded the B ability 3 times.
            "AbilityCLevels": 0, **This will indicate the hero upgraded the C ability 3 times.
        }
    },

Nooooo have you gone out of mind? Are we at the state already where we remove features from the API?!
Executed uses the same format as every kill event. Do not change it.
Gold from objective kill uses a similar format to xp gain events. That the whole team always gets the same amount of gold is an assumption that is currently true. There are no team-tied events in Telemetry, do not introduce another format.
NPCkillNPC uses the same format as every kill event. IsHero and TargetIsHero are an absolute necessity as it is not guaranteed whether a player or hero could not have the name *Turret*. These booleans make mapping over the Telemetry JSON to get objective and hero kills easy. Do not change it.
An EarnXP event and EarnGold event is required for every participant that earned XP or gold. Currently, ambient gold earns are missing. This does not fit into the KillActor event.
Hero swaps are necessary because there is an association between hero pick event and player ID.
Level up, learn ability events should not be aggregated. They must use a common format both in early and in late game. Players do not spawn with upgraded abilities in Brawl matches. Players are not required to upgrade any ability at all.

This issue "Telemetry is growing to be very large" is completely off focus. Let's take a look at a ranked match https://cdn.gamelockerapp.com/semc-vainglory/eu/2017/07/11/09/13/25863716-6619-11e7-a1a7-0242ac110005-telemetry.json
    134   "BuyItem",
   2028   "DealDamage",
    680   "EarnXP",
     15   "GoldFromTowerKill",
      6   "HeroSelect",
      8   "HeroSkinSelect",
    383   "KillActor",
     66   "LearnAbility",
     66   "LevelUp",
      2   "NPCkillNPC",
      6   "PlayerFirstSpawn",
    892   "UseAbility",
    108   "UseItemAbility"

8 of the events you want to trim make up (0+15+2+6+8+66+66+6)/4394 = 3.84% of the space.
Telemetry is not too large since we have #192 gzip compressed JSON. 76KB is downloaded and parsed within milliseconds.
Instead of removing features, choose a different format:

MessagePack ("It's like JSON. but fast and small.") http://msgpack.org/
ProtoBuf (like XML, but simpler, faster and smaller) https://developers.google.com/protocol-buffers/docs/overview

the granuarity of events helps in parsing the data and using it for various reasons. If we start mering events, then we have to write much complicated parsers and have to make assumptions.
in addition, removing events like Gold from Objectives (which is same today), may change as a game mechanic in 3v3 or even in 5v5 like Damage taken by VainTurrets is much less - mauybe they give different Gold. Such changes wont allow telemetry to scale well and we all who consume will have to make changes with every small change.
The balance is - a bit large telemetry file vs. easy of consumptions/parsing and usage - i will take the later any day because the compute power we have now days is more than enough to handle the sizes.
Are there concerns with Telemetry being slow or any consumer having issues with the size of it? If not, why remove it. i think it's a little too early in lifecycle of API to start removing features already. If it's not a problem please dont fix it.

Please, please, please do not REMOVE data from the API ... more data is ALWAYS better than less, and more granular data is ALWAYS better than aggregated data.

Hey dudes - I guess I don't really see a reason to remove it either.  :)

authors: Skillz4Killz cklugewicz genexp kvahuja schneefux

repo: madglory/gamelocker-vainglory

license: mit

license_source: bigquery


text:
refactor of StreamHandler and EventStore client

This pull request is to fix an issue when a data stream contains multiple complete messages. The handle method will now return an array of SocketMessages instead of just 1. The EventStore client has also been changed to handle the multiple messages.
If the last part of the data stream contain a partial message, this will be kept in the instance variable as before.
A test has been added to test this new scenario and previous test have been updated to expect the array of socketMessages.

btw, I noticed this when I updated a persistent subscription through the GetEventStore UI. This automatically disconnects any clients running. When I restarted the client it would disconnect after a few seconds. Turns out 2 complete message are being pushed upon re-connect and the code wasn't handling it right. @JurJean : This might also explain the inflight messages not working as they might appear as multiple complete messages in the stream.

Hey, thanks for active contribution. I will check your MR today's evening or tommorow's morning.

Awesome!

Merged.
I also have added docker-compose for usage examples / testing purposes.
Docker-compose contains eventstore in 3.4.0 version and php+protobuf installed.
It is published as 0.9.5 version now.

authors: JurJean dgafka rhofland

repo: madkom/event-store-client


text:
Resilient Microservice WebAPIs with REST and API Gateway

Title / Título
Resilient Microservice WebAPIs with REST and API Gateway
Description / Descripción
Splitting your application into a bunch of microservices is a non trivial task with a lot of challenges, that might end up in with a complete different system that’s breaking the clients. Can we fix that somehow? Yes - with REST (the real one) and an API Gateway.
In this presentation I’d like to reharse the REST architectural style (that’s probably one of the most misunderstood concepts and why you should probably hold your horses with using GraphQL); then we will start with a sample monolithic application and slowly break it into multiple microservices.
Problems will start to rise, clients will break and multiple parts of code will be duplicated across the microservices. Here’s the point where I’d like to refactor the API and introduce an API Gateway, and solve these one by one.
At the end of the presentation, you’ll see how we can switch from the monolithic version to the microservice version without breaking the clients at all.
Speaker Bio / Bio del Ponente
Vincenzo Chianese is an Italian Software developer currently working for LunchBadger. He puts bugs in the code, making sure his coworkers have always something to fix
Level / Nivel
Intermediate
Duration / Duración
45 minutes

@alexfernandez Hay novedades sobra esto?

@XVincentX Está en cola, ¿tienes restricciones de fecha? En principio vamos tirando de la lista por orden de entrada, a no ser que haya alguna restricción.

No no tranquilo, no tengo restricciones. Queria solo saber el estado de la cosa. Espero una tua llamada entonces 👍

@XVincentX Parece que no nos responden del Impact Hub. ¿Has encontrado sala en el Campus Madrid?

Està libre es 26/2 y el 28/2 (7:30 PM) o el 25 (todo el dia).
25/2 a las 7:00?

Buenas,
El 25 es domingo, mala fecha. El lunes 26 o el miércoles 28 a las 19:30
podrían ser buenas opciones. Ve reservando si quieres, y si nos responden
del Hub siempre podemos reevaluar.
Alex.
On Mon, Feb 5, 2018 at 11:15 AM, Vincenzo Chianese <notifications@github.com

wrote:

Està libre es 26/2 y el 28/2 (7:30 PM) o el 25 (todo el dia).
25/2 a las 7:00?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/madridjs/talks/issues/36#issuecomment-363040119, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA1gGs0KCug0ou8rsXo6x-WRlO0ys4f-ks5tRtTEgaJpZM4PZ0Zb
.

Ha! Por esto estaba libre todo el dia! 😄
Hecho. Te escribo cuando me contestan.

¡Gracias!
On Mon, Feb 5, 2018 at 11:28 AM, Vincenzo Chianese <notifications@github.com

wrote:

Ha! Por esto estaba libre todo el dia! 😄
Hecho. Te escribo cuando me contestan.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/madridjs/talks/issues/36#issuecomment-363043501, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA1gGv6bmI9Xdd-ECBEEslu7HBPX2Lbwks5tRtfmgaJpZM4PZ0Zb
.

@XVincentX ¿La quieres hacer en español o en inglés?

Me gustaría mucho hacerla en Español, pero no creo que tengo bastante fluidez.
Entonces preferiría en Ingles.
Un saludo,
V.

On Feb 12, 2018, at 6:48 AM, Alex Fernández notifications@github.com wrote:
@XVincentX ¿La quieres hacer en español o en inglés?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Hecho! Cerramolos!

authors: XVincentX alexfernandez

repo: madridjs/talks


text:
hdsky签到失败

hdsky在签到环节加入了验证码，需要更新一下

已更新


text:
'$' as identifier

Hi, this is a cool work.
It seems that identifiers starting with '$' can not be used.
Is it intentional?

No, it seems a bug.
I'll fix it.

Fixed.

repo: maekawatoshiki/rapidus


text:
Add "font_creation" function

Write a function that creates and formats fonts, then replace the related code with that function call. Fonts are created 11 distinct times in the run_calibration_GUI.py code - let's eliminate that redundancy.

Done. Included in last pull request.

repo: maestrolab/SMAREACTcleaned


text:
race condition

just tested this package, and there seems to be a race condition where sometimes answers return empty when called quickly after loading this module.

do you have an example?

sure. you have a c9.io username?

Take a look here:
https://gitlab.com/pushrocks/dnsly/blob/master/ts/index.ts
It should work and does sometimes
But responses often return empty like here:
https://gitlab.com/pushrocks/dnsly/builds/6250193

switched to node's built in dns lookup for the meantime

pretty sure this was fixed by https://github.com/mafintosh/dns-socket/commit/ca5ef8875a1e59a2516db45524a7e5d862bf1a57

authors: mafintosh philkunz

repo: mafintosh/dns-socket


text:
Electron installation fails on Debian based distros.

I have been trying to install electron on my Ubuntu system both as a dependancy and globally but both commands fail.
Here is the output:
saq1610@saq1610-MacBookPro:~/Watson$ sudo npm install electron-prebuilt -g
/usr/local/bin/electron -> /usr/local/lib/node_modules/electron-prebuilt/cli.js

> electron-prebuilt@0.35.1 postinstall /usr/local/lib/node_modules/electron-prebuilt
> node install.js

sh: 1: node: not found
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR! electron-prebuilt@0.35.1 postinstall: `node install.js`
npm ERR! Exit status 127
npm ERR!
npm ERR! Failed at the electron-prebuilt@0.35.1 postinstall script.
npm ERR! This is most likely a problem with the electron-prebuilt package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node install.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls electron-prebuilt
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 4.2.0-19-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install" "electron-prebuilt" "-g"
npm ERR! cwd /home/saq1610/Watson
npm ERR! node -v v4.2.2
npm ERR! npm -v 1.4.21
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /home/saq1610/Watson/npm-debug.log
npm ERR! not ok code 0
saq1610@saq1610-MacBookPro:~/Watson$

According to the log in /usr/share/doc/nodejs/README.Debian this seems to be the issue:
nodejs command
--------------

The upstream name for the Node.js interpreter command is "node".
In Debian the interpreter command has been changed to "nodejs".

This was done to prevent a namespace collision: other commands use
the same name in their upstreams, such as ax25-node from the "node"
package.

Scripts calling Node.js as a shell command must be changed to instead
use the "nodejs" command.

It seems that electron still calls upon "node" rather than "nodejs" which is why the "install.js" script fails.

As it says node: not found, we can expect your system to not be affected by problems in case Node.js uses the command node, so, as a temporary solution, you could create an alias like this:
alias node='nodejs'

The alias will only be valid during that terminal session which means you're safe in case you'll ever have another program using node as its command. After setting the alias, install again, it should work after that without using an alias.

The alias doesn't work. It seems the npm process spawns another process where the alias is not recognized?
Another thing that caught my eye: the node_modules folder is empty after the error.
If the post install script doesn't run, does the whole package get removed again?
Shouldn't it be in there?

@tomwor Yeah, it's possible that npm spawns a process that is not affected by this way of aliasing. It could also be that npm deletes the dependency folder in node_modules/ if installation has failed, probably because you can't just resume the installation process if it has failed at some point, so it rather asks you to download it again (if not cached) and start the installation again from zero.
It's also possible that not every Debian user will even install the ax25-node package (or others using the node command), to be honest, node is a really bad name for a command since it's just as descriptive as webbrowser or something like that, maybe it'll even be changed in the future as Node.js is getting more popular everyday. On packages.debian.org, it is described like this:

The ax25-node program accepts TCP/IP and packet radio network connections and presents users with an interface that allows them to make gateway connections to remote hosts using a variety of amateur radio protocols.

Another way for making the alias available globally is to create the alias in your .bashrc file, but you can of course also use sudo ln -s.

I recommend trying out https://packages.debian.org/sid/nodejs-legacy, that seems to have worked for others having issues installing on different linux distros.
sudo apt-get install nodejs-legacy

See https://github.com/electron-userland/electron-prebuilt/issues/27#issuecomment-181583077 for an example that resolved a similar issue. Marking this as resolved as it sounds like nodejs-legacy was made to deal with this issue.

authors: maxrimue ngoldman saq1610 tomwor

repo: mafintosh/electron-prebuilt


text:
does pumpify not emit "end" when an error happens?

Given streams A, B, C are streams I have
const stream = pumpify.obj(A, B, C)
if A emits error followed by an emit of end, the pumpified stream emits error but does not emit end. Is that the correct behavior? Does a pumpify pipeline close on an error only emitting an error event without emitting an end.
Still trying to understand Node streams, but from what I got on normal Node streams an error does not stop the stream so there is also an end. I am writing some code that has to know when a pipeline finishes hence my confusion with error and end
Therefore to know if something finished successfully do I just listen to end and to know if something finished failing i listen to error.

never mind, it was a problem with a ParallelTransfrom library I was using. It and pumpify do not play together well when the ParallelTransfrom stream is the last one in the pipeline.

Are you sure you are draining the last stream in the pipeline?

authors: firemuzzy mafintosh

repo: mafintosh/pumpify


text:
Cannot start kachery daemon

(kachery-env) typhoon:~% kachery-daemon-start --label franklab --owner kyuhyun9056@gmail.com --auth-group kachery-users
node: 15.14.0
+ export KACHERY_DAEMON_PORT=14747
+ KACHERY_DAEMON_PORT=14747
+ export KACHERY_DAEMON_HOST=typhoon
+ KACHERY_DAEMON_HOST=typhoon
+ npm install -g -y /home/kacheryuser/miniconda3/envs/kachery-env/lib/python3.8/site-packages/kachery_daemon/kachery-daemon-node-1.0.22.tgz
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated node-pre-gyp@0.11.0: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future
npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.

changed 224 packages, and audited 225 packages in 12s

9 packages are looking for funding
  run `npm fund` for details

4 high severity vulnerabilities

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
+ exec kachery-daemon-node start --verbose 0 --auth-group kachery-users --kachery-hub-url https://kacheryhub.org --label franklab --owner kyuhyun9056@gmail.com
node:internal/modules/cjs/loader:927
  throw err;
  ^

Error: Cannot find module 'external/real/kacheryStorage/KacheryStorageManager'
Require stack:
- /home/kacheryuser/miniconda3/envs/kachery-env/lib/node_modules/kachery-daemon-node/dist/services/ClientAuthService.js
- /home/kacheryuser/miniconda3/envs/kachery-env/lib/node_modules/kachery-daemon-node/dist/startDaemon.js
- /home/kacheryuser/miniconda3/envs/kachery-env/lib/node_modules/kachery-daemon-node/dist/cli.js
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:924:15)
    at Function.Module._load (node:internal/modules/cjs/loader:769:27)
    at Module.require (node:internal/modules/cjs/loader:996:19)
    at require (node:internal/modules/cjs/helpers:92:18)
    at Object.<anonymous> (/home/kacheryuser/miniconda3/envs/kachery-env/lib/node_modules/kachery-daemon-node/dist/services/ClientAuthService.js:25:33)
    at Module._compile (node:internal/modules/cjs/loader:1092:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1121:10)
    at Module.load (node:internal/modules/cjs/loader:972:32)
    at Function.Module._load (node:internal/modules/cjs/loader:813:14)
    at Module.require (node:internal/modules/cjs/loader:996:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/home/kacheryuser/miniconda3/envs/kachery-env/lib/node_modules/kachery-daemon-node/dist/services/ClientAuthService.js',
    '/home/kacheryuser/miniconda3/envs/kachery-env/lib/node_modules/kachery-daemon-node/dist/startDaemon.js',
    '/home/kacheryuser/miniconda3/envs/kachery-env/lib/node_modules/kachery-daemon-node/dist/cli.js'
  ]
}

Please try 1.0.23 on pypi

Seems like it's resolved. Also sortingview backend started up. Closing

repo: magland/sortingview


text:
bin/magento setup:db:status gives a false negative.

Magento version 2.4.3-p2
php 7.4
When doing bin/magento setup:upgrade and after do a bin/magento setup:db:status.
Expected

All modules are up to date.

Actual
Declarative Schema is not up to date
Run 'setup:upgrade' to update your DB schema and data.
More Information
Because of the db_schema.xml

        <column name="transaction_fee"
                xsi:type="float"
                unsigned="true"
                nullable="false"
                comment="Transaction Fee"/>

        <column name="transaction_fee"
                xsi:type="float"
                unsigned="true"
                nullable="false"
                comment="Transaction Fee"/>

Both have unsigned true Magento expects the float to have a scale/precision. Like float(10,2), because in the db_schema this is not declared. During bin/magento setup:db:status It needs to have a match in \Magento\Framework\Setup\Declaration\Schema\Db\MySQL\Definition\Columns\Real::fromDefinition otherwise unsigned is not registrated.
I have added this patch to resolve it.:
diff --git a/etc/db_schema.xml b/etc/db_schema.xml
--- a/etc/db_schema.xml
+++ b/etc/db_schema.xml
@@ -332,6 +332,8 @@
                 xsi:type="float"
                 unsigned="true"
                 nullable="false"
+                scale="2"
+                precision="10"
                 comment="Transaction Fee"/>

@@ -340,6 +342,8 @@
                 xsi:type="float"
                 unsigned="true"
                 nullable="false"
+                scale="2"
+                precision="10"
                 comment="Transaction Fee"/>

Hi @leonhelmus,
We are happy to share that we've just released the new 1.10.1 version where we have fixed this issue. Thank you for opening this issue with detailed information on error entry point + suggestion on how to fix this!
We are closing this issue now but please feel free to reopen the issue if this still occurs.

authors: Marvin-Magmodules leonhelmus


text:
Dataset Refresh refreshing more than the single dataset defined.

using 5.* notice that when the refresh is executed it is kicking off more than one dataset even though the checkbox to update all is not checked.

Issue should be fixed. When not the case please add : System.debug with value true to your pipeline. and send the log

I scrapped your task and just using powershell myself as I did not know how long it would take to resolve.
On Dec 9, 2020, at 10:34 AM, Maik van der Gaag notifications@github.com wrote:

Issue should be fixed. When not the case please add : System.debug with value true to your pipeline. and send the log
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

authors: awilbourn maikvandergaag

repo: maikvandergaag/msft-extensions


text:
Connect-PowerBIServiceAccount : Failed to populate environments in settings

Describe the issue
During release the Power Bi Publish step is failing with the following error:
##[debug]Connect-PowerBIServiceAccount : Failed to populate environments in settings
**Extension **

Extension: Power BI Actions
Version: 5.4.44 (Latest)

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
Task should be finished successfully.
Situation (please complete the following information):

Agent type: Azure scale set Windows (Self-hosted)
Autentication: Service Connection
Extension Version: 5.4.44 (Latest)

Log info
2023-07-25T19:31:19.9627834Z ##[debug]Evaluating condition for step: 'Power BI Action: Publish'
2023-07-25T19:31:19.9628615Z ##[debug]Evaluating: succeeded()
2023-07-25T19:31:19.9628768Z ##[debug]Evaluating succeeded:
2023-07-25T19:31:19.9629092Z ##[debug]=> True
2023-07-25T19:31:19.9629296Z ##[debug]Result: True
2023-07-25T19:31:19.9629490Z ##[section]Starting: Power BI Action: Publish
2023-07-25T19:31:19.9719628Z ==============================================================================
2023-07-25T19:31:19.9719748Z Task         : Power BI Actions
2023-07-25T19:31:19.9719795Z Description  : Release Task Power BI Actions
2023-07-25T19:31:19.9719859Z Version      : 5.4.44
2023-07-25T19:31:19.9719902Z Author       : Maik van der Gaag
2023-07-25T19:31:19.9720715Z Help         :
2023-07-25T19:31:19.9720763Z ==============================================================================
2023-07-25T19:31:30.8785951Z ##[debug]VstsTaskSdk 0.10.0 commit 787a46ec0a2df5b4d12c2e801bd3f319975c054c
2023-07-25T19:31:30.9923546Z Starting Power BI Actions extension
2023-07-25T19:31:31.0022193Z ##[debug]Entering C:\a_tasks\PowerBIActions_d5b7fec6-2b25-4742-905b-0dad97687df5\5.4.44\run.ps1.
2023-07-25T19:31:31.0076615Z ### Required Module is needed. Importing now...
2023-07-25T19:31:31.0109231Z ##[debug]Loading module from path 'C:\a_tasks\PowerBIActions_d5b7fec6-2b25-4742-905b-0dad97687df5\5.4.44\ps_modules\MicrosoftPowerBIMgmt.Profile\1.2.1077\MicrosoftPowerBIMgmt.Profile.psd1'.
2023-07-25T19:31:31.0164351Z ##[debug]Loading 'TypesToProcess' from path 'C:\a_tasks\PowerBIActions_d5b7fec6-2b25-4742-905b-0dad97687df5\5.4.44\ps_modules\MicrosoftPowerBIMgmt.Profile\1.2.1077\Microsoft.PowerBI.Commands.Profile.types.ps1xml'.
2023-07-25T19:31:31.0187002Z ##[debug]Loading 'FormatsToProcess' from path 'C:\a_tasks\PowerBIActions_d5b7fec6-2b25-4742-905b-0dad97687df5\5.4.44\ps_modules\MicrosoftPowerBIMgmt.Profile\1.2.1077\Microsoft.PowerBI.Commands.Profile.format.ps1xml'.
2023-07-25T19:31:46.0624528Z ##[debug]Populating RepositorySourceLocation property for module MicrosoftPowerBIMgmt.Profile.
2023-07-25T19:31:46.0644707Z ##[debug]Loading module from path 'C:\a_tasks\PowerBIActions_d5b7fec6-2b25-4742-905b-0dad97687df5\5.4.44\ps_modules\MicrosoftPowerBIMgmt.Profile\1.2.1077.\lib\netstandard2.0\Microsoft.PowerBI.Commands.Profile.dll'.
2023-07-25T19:31:46.0878840Z ##[debug]Exporting cmdlet 'Connect-PowerBIServiceAccount'.
2023-07-25T19:31:46.0892149Z ##[debug]Exporting cmdlet 'Disconnect-PowerBIServiceAccount'.
2023-07-25T19:31:46.0904495Z ##[debug]Exporting cmdlet 'Get-PowerBIAccessToken'.
2023-07-25T19:31:46.0917029Z ##[debug]Exporting cmdlet 'Invoke-PowerBIRestMethod'.
2023-07-25T19:31:46.0929189Z ##[debug]Exporting cmdlet 'Resolve-PowerBIError'.
2023-07-25T19:31:46.0941748Z ##[debug]Importing cmdlet 'Connect-PowerBIServiceAccount'.
2023-07-25T19:31:46.0953884Z ##[debug]Importing cmdlet 'Disconnect-PowerBIServiceAccount'.
2023-07-25T19:31:46.0965827Z ##[debug]Importing cmdlet 'Get-PowerBIAccessToken'.
2023-07-25T19:31:46.0977534Z ##[debug]Importing cmdlet 'Invoke-PowerBIRestMethod'.
2023-07-25T19:31:46.0989044Z ##[debug]Importing cmdlet 'Resolve-PowerBIError'.
2023-07-25T19:31:46.1001454Z ##[debug]Importing alias 'Add-PowerBIServiceAccount'.
2023-07-25T19:31:46.1013300Z ##[debug]Importing alias 'Login-PowerBI'.
2023-07-25T19:31:46.1025086Z ##[debug]Importing alias 'Login-PowerBIServiceAccount'.
2023-07-25T19:31:46.1036404Z ##[debug]Importing alias 'Logout-PowerBI'.
2023-07-25T19:31:46.1048089Z ##[debug]Importing alias 'Logout-PowerBIServiceAccount'.
2023-07-25T19:31:46.1059745Z ##[debug]Importing alias 'Remove-PowerBIServiceAccount'.
2023-07-25T19:31:46.1071158Z ##[debug]Importing alias 'Set-PowerBIServiceAccount'.
2023-07-25T19:31:46.1096348Z ##[debug]Loading module from path 'C:\a_tasks\PowerBIActions_d5b7fec6-2b25-4742-905b-0dad97687df5\5.4.44\ps_modules\MicrosoftPowerBIMgmt.Workspaces\1.2.1077\MicrosoftPowerBIMgmt.Workspaces.psd1'.
2023-07-25T19:31:46.1148065Z ##[debug]Loading 'FormatsToProcess' from path 'C:\a_tasks\PowerBIActions_d5b7fec6-2b25-4742-905b-0dad97687df5\5.4.44\ps_modules\MicrosoftPowerBIMgmt.Workspaces\1.2.1077\Microsoft.PowerBI.Commands.Workspaces.format.ps1xml'.
2023-07-25T19:31:46.1319876Z ##[debug]Populating RepositorySourceLocation property for module MicrosoftPowerBIMgmt.Workspaces.
2023-07-25T19:31:46.1340396Z ##[debug]Loading module from path 'C:\a_tasks\PowerBIActions_d5b7fec6-2b25-4742-905b-0dad97687df5\5.4.44\ps_modules\MicrosoftPowerBIMgmt.Workspaces\1.2.1077.\lib\netstandard2.0\Microsoft.PowerBI.Commands.Workspaces.dll'.
2023-07-25T19:31:46.1409706Z ##[debug]Exporting cmdlet 'Add-PowerBIWorkspaceUser'.
2023-07-25T19:31:46.1422586Z ##[debug]Exporting cmdlet 'Get-PowerBIWorkspace'.
2023-07-25T19:31:46.1438535Z ##[debug]Exporting cmdlet 'Get-PowerBIWorkspaceMigrationStatus'.
2023-07-25T19:31:46.1450783Z ##[debug]Exporting cmdlet 'New-PowerBIWorkspace'.
2023-07-25T19:31:46.1981666Z ##[debug]Exporting cmdlet 'Remove-PowerBIWorkspaceUser'.
2023-07-25T19:31:46.2002410Z ##[debug]Exporting cmdlet 'Restore-PowerBIWorkspace'.
2023-07-25T19:31:46.2006201Z ##[debug]Exporting cmdlet 'Set-PowerBIWorkspace'.
2023-07-25T19:31:46.2023057Z ##[debug]Importing cmdlet 'Add-PowerBIWorkspaceUser'.
2023-07-25T19:31:46.2038167Z ##[debug]Importing cmdlet 'Get-PowerBIWorkspace'.
2023-07-25T19:31:46.2053931Z ##[debug]Importing cmdlet 'Get-PowerBIWorkspaceMigrationStatus'.
2023-07-25T19:31:46.2069270Z ##[debug]Importing cmdlet 'New-PowerBIWorkspace'.
2023-07-25T19:31:46.2086560Z ##[debug]Importing cmdlet 'Remove-PowerBIWorkspaceUser'.
2023-07-25T19:31:46.2097813Z ##[debug]Importing cmdlet 'Restore-PowerBIWorkspace'.
2023-07-25T19:31:46.2109171Z ##[debug]Importing cmdlet 'Set-PowerBIWorkspace'.
2023-07-25T19:31:46.2120439Z ##[debug]Importing alias 'Add-PowerBIGroupUser'.
2023-07-25T19:31:46.2131302Z ##[debug]Importing alias 'Get-PowerBIGroup'.
2023-07-25T19:31:46.2141938Z ##[debug]Importing alias 'Get-PowerBIGroupMigrationStatus'.
2023-07-25T19:31:46.2152625Z ##[debug]Importing alias 'New-PowerBIGroup'.
2023-07-25T19:31:46.2163086Z ##[debug]Importing alias 'Remove-PowerBIGroupUser'.
2023-07-25T19:31:46.2173634Z ##[debug]Importing alias 'Restore-PowerBIGroup'.
2023-07-25T19:31:46.2184143Z ##[debug]Importing alias 'Set-PowerBIGroup'.
2023-07-25T19:31:46.2212149Z ##[debug]Loading module from path 'C:\a_tasks\PowerBIActions_d5b7fec6-2b25-4742-905b-0dad97687df5\5.4.44\ps_modules\MicrosoftPowerBIMgmt.Reports\1.2.1077\MicrosoftPowerBIMgmt.Reports.psd1'.
2023-07-25T19:31:46.2277659Z ##[debug]Populating RepositorySourceLocation property for module MicrosoftPowerBIMgmt.Reports.
2023-07-25T19:31:46.2295575Z ##[debug]Loading module from path 'C:\a_tasks\PowerBIActions_d5b7fec6-2b25-4742-905b-0dad97687df5\5.4.44\ps_modules\MicrosoftPowerBIMgmt.Reports\1.2.1077.\lib\netstandard2.0\Microsoft.PowerBI.Commands.Reports.dll'.
2023-07-25T19:31:46.2350057Z ##[debug]Exporting cmdlet 'Copy-PowerBIReport'.
2023-07-25T19:31:46.2360863Z ##[debug]Exporting cmdlet 'Copy-PowerBITile'.
2023-07-25T19:31:46.2371634Z ##[debug]Exporting cmdlet 'Export-PowerBIReport'.
2023-07-25T19:31:46.2382010Z ##[debug]Exporting cmdlet 'Get-PowerBIDashboard'.
2023-07-25T19:31:46.2392574Z ##[debug]Exporting cmdlet 'Get-PowerBIImport'.
2023-07-25T19:31:46.2402841Z ##[debug]Exporting cmdlet 'Get-PowerBIReport'.
2023-07-25T19:31:46.2413772Z ##[debug]Exporting cmdlet 'Get-PowerBITile'.
2023-07-25T19:31:46.2424135Z ##[debug]Exporting cmdlet 'New-PowerBIDashboard'.
2023-07-25T19:31:46.2434563Z ##[debug]Exporting cmdlet 'New-PowerBIReport'.
2023-07-25T19:31:46.2444829Z ##[debug]Exporting cmdlet 'Remove-PowerBIReport'.
2023-07-25T19:31:46.2455937Z ##[debug]Importing cmdlet 'Copy-PowerBIReport'.
2023-07-25T19:31:46.2466122Z ##[debug]Importing cmdlet 'Copy-PowerBITile'.
2023-07-25T19:31:46.2476527Z ##[debug]Importing cmdlet 'Export-PowerBIReport'.
2023-07-25T19:31:46.2486691Z ##[debug]Importing cmdlet 'Get-PowerBIDashboard'.
2023-07-25T19:31:46.2497200Z ##[debug]Importing cmdlet 'Get-PowerBIImport'.
2023-07-25T19:31:46.2507314Z ##[debug]Importing cmdlet 'Get-PowerBIReport'.
2023-07-25T19:31:46.2517771Z ##[debug]Importing cmdlet 'Get-PowerBITile'.
2023-07-25T19:31:46.2528530Z ##[debug]Importing cmdlet 'New-PowerBIDashboard'.
2023-07-25T19:31:46.2539219Z ##[debug]Importing cmdlet 'New-PowerBIReport'.
2023-07-25T19:31:46.2549503Z ##[debug]Importing cmdlet 'Remove-PowerBIReport'.
2023-07-25T19:31:46.2559923Z ##[debug]Importing alias 'Get-PowerBIDashboardTile'.
2023-07-25T19:31:46.2583891Z ##[debug]Loading module from path 'C:\a_tasks\PowerBIActions_d5b7fec6-2b25-4742-905b-0dad97687df5\5.4.44\ps_modules\MicrosoftPowerBIMgmt.Data\1.2.1077\MicrosoftPowerBIMgmt.Data.psd1'.
2023-07-25T19:31:46.2632665Z ##[debug]Loading 'FormatsToProcess' from path 'C:\a_tasks\PowerBIActions_d5b7fec6-2b25-4742-905b-0dad97687df5\5.4.44\ps_modules\MicrosoftPowerBIMgmt.Data\1.2.1077\Microsoft.PowerBI.Commands.Data.format.ps1xml'.
2023-07-25T19:31:46.2868763Z ##[debug]Populating RepositorySourceLocation property for module MicrosoftPowerBIMgmt.Data.
2023-07-25T19:31:46.2889042Z ##[debug]Loading module from path 'C:\a_tasks\PowerBIActions_d5b7fec6-2b25-4742-905b-0dad97687df5\5.4.44\ps_modules\MicrosoftPowerBIMgmt.Data\1.2.1077.\lib\netstandard2.0\Microsoft.PowerBI.Commands.Data.dll'.
2023-07-25T19:31:46.2945363Z ##[debug]Exporting cmdlet 'Add-PowerBIDataset'.
2023-07-25T19:31:46.2957527Z ##[debug]Exporting cmdlet 'Add-PowerBIRow'.
2023-07-25T19:31:46.2968671Z ##[debug]Exporting cmdlet 'Export-PowerBIDataflow'.
2023-07-25T19:31:46.2979477Z ##[debug]Exporting cmdlet 'Get-PowerBIDataflow'.
2023-07-25T19:31:46.2990603Z ##[debug]Exporting cmdlet 'Get-PowerBIDataflowDatasource'.
2023-07-25T19:31:46.3000923Z ##[debug]Exporting cmdlet 'Get-PowerBIDataset'.
2023-07-25T19:31:46.3011498Z ##[debug]Exporting cmdlet 'Get-PowerBIDatasource'.
2023-07-25T19:31:46.3022215Z ##[debug]Exporting cmdlet 'Get-PowerBITable'.
2023-07-25T19:31:46.3032832Z ##[debug]Exporting cmdlet 'New-PowerBIColumn'.
2023-07-25T19:31:46.3043866Z ##[debug]Exporting cmdlet 'New-PowerBIDataset'.
2023-07-25T19:31:46.3054531Z ##[debug]Exporting cmdlet 'New-PowerBITable'.
2023-07-25T19:31:46.3065350Z ##[debug]Exporting cmdlet 'Remove-PowerBIRow'.
2023-07-25T19:31:46.3076039Z ##[debug]Exporting cmdlet 'Set-PowerBIDataset'.
2023-07-25T19:31:46.3086004Z ##[debug]Exporting cmdlet 'Set-PowerBITable'.
2023-07-25T19:31:46.3096931Z ##[debug]Importing cmdlet 'Add-PowerBIDataset'.
2023-07-25T19:31:46.3107219Z ##[debug]Importing cmdlet 'Add-PowerBIRow'.
2023-07-25T19:31:46.3117716Z ##[debug]Importing cmdlet 'Export-PowerBIDataflow'.
2023-07-25T19:31:46.3128591Z ##[debug]Importing cmdlet 'Get-PowerBIDataflow'.
2023-07-25T19:31:46.3139277Z ##[debug]Importing cmdlet 'Get-PowerBIDataflowDatasource'.
2023-07-25T19:31:46.3150148Z ##[debug]Importing cmdlet 'Get-PowerBIDataset'.
2023-07-25T19:31:46.3160822Z ##[debug]Importing cmdlet 'Get-PowerBIDatasource'.
2023-07-25T19:31:46.3171132Z ##[debug]Importing cmdlet 'Get-PowerBITable'.
2023-07-25T19:31:46.3181846Z ##[debug]Importing cmdlet 'New-PowerBIColumn'.
2023-07-25T19:31:46.3192015Z ##[debug]Importing cmdlet 'New-PowerBIDataset'.
2023-07-25T19:31:46.3202630Z ##[debug]Importing cmdlet 'New-PowerBITable'.
2023-07-25T19:31:46.3212863Z ##[debug]Importing cmdlet 'Remove-PowerBIRow'.
2023-07-25T19:31:46.3223699Z ##[debug]Importing cmdlet 'Set-PowerBIDataset'.
2023-07-25T19:31:46.3234444Z ##[debug]Importing cmdlet 'Set-PowerBITable'.
2023-07-25T19:31:46.3241135Z ### Trying to import the incorporated module for PowerBI
2023-07-25T19:31:46.3256735Z ##[debug]Loading module from path 'C:\a_tasks\PowerBIActions_d5b7fec6-2b25-4742-905b-0dad97687df5\5.4.44\ps_modules\PowerBI\PowerBI.psm1'.
2023-07-25T19:31:46.3382539Z ##[debug]Exporting function 'Set-PowerBIDatasetToGatewayInGroup'.
2023-07-25T19:31:46.3394007Z ##[debug]Exporting function 'Get-PowerBIDatasetGatewayDatasourceInGroup'.
2023-07-25T19:31:46.3404972Z ##[debug]Exporting function 'Update-PowerBIDatasetSource'.
2023-07-25T19:31:46.3415609Z ##[debug]Exporting function 'Update-PowerBIDatasetDatasourcesInGroup'.
2023-07-25T19:31:46.3425945Z ##[debug]Exporting function 'Get-PowerBIDataSourcesInGateway'.
2023-07-25T19:31:46.3436450Z ##[debug]Exporting function 'Get-PowerBIGateways'.
2023-07-25T19:31:46.3446791Z ##[debug]Exporting function 'Set-DatasetOwnership'.
2023-07-25T19:31:46.3457258Z ##[debug]Exporting function 'Set-PowerBIDataSetOwnership'.
2023-07-25T19:31:46.3467655Z ##[debug]Exporting function 'Update-PowerBIDatasetParameter'.
2023-07-25T19:31:46.3478198Z ##[debug]Exporting function 'Update-PowerBIDatasetParameters'.
2023-07-25T19:31:46.3488461Z ##[debug]Exporting function 'Invoke-API'.
2023-07-25T19:31:46.3498949Z ##[debug]Exporting function 'New-DataSetSingleRefresh'.
2023-07-25T19:31:46.3509668Z ##[debug]Exporting function 'New-DatasetRefresh'.
2023-07-25T19:31:46.3520152Z ##[debug]Exporting function 'Update-PowerBIDatasetDatasources'.
2023-07-25T19:31:46.3530363Z ##[debug]Exporting function 'Update-PowerBIDatasetDatasource'.
2023-07-25T19:31:46.3541052Z ##[debug]Exporting function 'Update-ConnectionStringDirectQuery'.
2023-07-25T19:31:46.3551447Z ##[debug]Exporting function 'Get-PowerBIReport'.
2023-07-25T19:31:46.3561670Z ##[debug]Exporting function 'Get-PowerBiDataSet'.
2023-07-25T19:31:46.3571585Z ##[debug]Exporting function 'Get-PowerBiDataSetDataSources'.
2023-07-25T19:31:46.3581804Z ##[debug]Exporting function 'Get-PowerBiDataSets'.
2023-07-25T19:31:46.3591718Z ##[debug]Exporting function 'Get-PowerBiParameters'.
2023-07-25T19:31:46.3601867Z ##[debug]Exporting function 'New-PowerBIWorkSpace'.
2023-07-25T19:31:46.3611935Z ##[debug]Exporting function 'Remove-PowerBIWorkSpace'.
2023-07-25T19:31:46.3622332Z ##[debug]Exporting function 'Import-PowerBIFile'.
2023-07-25T19:31:46.3632193Z ##[debug]Exporting function 'Get-PowerBIGroupPath'.
2023-07-25T19:31:46.3642484Z ##[debug]Exporting function 'Add-PowerBIWorkspaceUsers'.
2023-07-25T19:31:46.3652452Z ##[debug]Exporting function 'Add-PowerBIWorkspaceGroup'.
2023-07-25T19:31:46.3662951Z ##[debug]Exporting function 'Add-PowerBIWorkspaceSP'.
2023-07-25T19:31:46.3673162Z ##[debug]Exporting function 'Publish-PowerBIFile'.
2023-07-25T19:31:46.3683423Z ##[debug]Exporting function 'Publish-PowerBIFileApi'.
2023-07-25T19:31:46.3693897Z ##[debug]Exporting function 'Remove-PowerBIReport'.
2023-07-25T19:31:46.3704006Z ##[debug]Exporting function 'Get-PowerBICapacity'.
2023-07-25T19:31:46.3713900Z ##[debug]Exporting function 'Set-Capacity'.
2023-07-25T19:31:46.3724203Z ##[debug]Exporting function 'Redo-PowerBIReport'.
2023-07-25T19:31:46.3734540Z ##[debug]Exporting function 'Redo-PowerBIReportCrossWorkspace'.
2023-07-25T19:31:46.3744806Z ##[debug]Exporting function 'Update-BasicSQLDataSourceCredentials'.
2023-07-25T19:31:46.3754842Z ##[debug]Exporting function 'Set-RefreshSchedule'.
2023-07-25T19:31:46.3764947Z ##[debug]Exporting function 'Publish-TabularEditor'.
2023-07-25T19:31:46.3775004Z ##[debug]Exporting function 'Add-PowerBIDatasetPermissions'.
2023-07-25T19:31:46.3785697Z ##[debug]Exporting function 'Get-PowerBiDatasetUsers'.
2023-07-25T19:31:46.3798366Z ##[debug]Importing function 'Add-PowerBIDatasetPermissions'.
2023-07-25T19:31:46.3808838Z ##[debug]Importing function 'Add-PowerBIWorkspaceGroup'.
2023-07-25T19:31:46.3819946Z ##[debug]Importing function 'Add-PowerBIWorkspaceSP'.
2023-07-25T19:31:46.3830781Z ##[debug]Importing function 'Add-PowerBIWorkspaceUsers'.
2023-07-25T19:31:46.3840901Z ##[debug]Importing function 'Get-PowerBICapacity'.
2023-07-25T19:31:46.3851871Z ##[debug]Importing function 'Get-PowerBiDataSet'.
2023-07-25T19:31:46.3862322Z ##[debug]Importing function 'Get-PowerBiDataSetDataSources'.
2023-07-25T19:31:46.3872673Z ##[debug]Importing function 'Get-PowerBIDatasetGatewayDatasourceInGroup'.
2023-07-25T19:31:46.3882996Z ##[debug]Importing function 'Get-PowerBiDataSets'.
2023-07-25T19:31:46.3894301Z ##[debug]Importing function 'Get-PowerBiDatasetUsers'.
2023-07-25T19:31:46.3905624Z ##[debug]Importing function 'Get-PowerBIDataSourcesInGateway'.
2023-07-25T19:31:46.3916731Z ##[debug]Importing function 'Get-PowerBIGateways'.
2023-07-25T19:31:46.3928134Z ##[debug]Importing function 'Get-PowerBIGroupPath'.
2023-07-25T19:31:46.3939235Z ##[debug]Importing function 'Get-PowerBiParameters'.
2023-07-25T19:31:46.3950275Z ##[debug]Importing function 'Get-PowerBIReport'.
2023-07-25T19:31:46.3961413Z ##[debug]Importing function 'Import-PowerBIFile'.
2023-07-25T19:31:46.3972555Z ##[debug]Importing function 'Invoke-API'.
2023-07-25T19:31:46.3984846Z ##[debug]Importing function 'New-DatasetRefresh'.
2023-07-25T19:31:46.3995761Z ##[debug]Importing function 'New-DataSetSingleRefresh'.
2023-07-25T19:31:46.4007040Z ##[debug]Importing function 'New-PowerBIWorkSpace'.
2023-07-25T19:31:46.4018143Z ##[debug]Importing function 'Publish-PowerBIFile'.
2023-07-25T19:31:46.4029180Z ##[debug]Importing function 'Publish-PowerBIFileApi'.
2023-07-25T19:31:46.4040523Z ##[debug]Importing function 'Publish-TabularEditor'.
2023-07-25T19:31:46.4051872Z ##[debug]Importing function 'Redo-PowerBIReport'.
2023-07-25T19:31:46.4063165Z ##[debug]Importing function 'Redo-PowerBIReportCrossWorkspace'.
2023-07-25T19:31:46.4074242Z ##[debug]Importing function 'Remove-PowerBIReport'.
2023-07-25T19:31:46.4085261Z ##[debug]Importing function 'Remove-PowerBIWorkSpace'.
2023-07-25T19:31:46.4096849Z ##[debug]Importing function 'Set-Capacity'.
2023-07-25T19:31:46.4107690Z ##[debug]Importing function 'Set-DatasetOwnership'.
2023-07-25T19:31:46.4118790Z ##[debug]Importing function 'Set-PowerBIDataSetOwnership'.
2023-07-25T19:31:46.4129914Z ##[debug]Importing function 'Set-PowerBIDatasetToGatewayInGroup'.
2023-07-25T19:31:46.4141182Z ##[debug]Importing function 'Set-RefreshSchedule'.
2023-07-25T19:31:46.4152367Z ##[debug]Importing function 'Update-BasicSQLDataSourceCredentials'.
2023-07-25T19:31:46.4163915Z ##[debug]Importing function 'Update-ConnectionStringDirectQuery'.
2023-07-25T19:31:46.4174956Z ##[debug]Importing function 'Update-PowerBIDatasetDatasource'.
2023-07-25T19:31:46.4186104Z ##[debug]Importing function 'Update-PowerBIDatasetDatasources'.
2023-07-25T19:31:46.4197343Z ##[debug]Importing function 'Update-PowerBIDatasetDatasourcesInGroup'.
2023-07-25T19:31:46.4208835Z ##[debug]Importing function 'Update-PowerBIDatasetParameter'.
2023-07-25T19:31:46.4219985Z ##[debug]Importing function 'Update-PowerBIDatasetParameters'.
2023-07-25T19:31:46.4230951Z ##[debug]Importing function 'Update-PowerBIDatasetSource'.
2023-07-25T19:31:46.4486106Z ##[debug]INPUT_POWERBISERVICEENDPOINT: '6a480815-b295-4019-ba26-b60f50361c82'
2023-07-25T19:31:46.4581551Z ##[debug]ENDPOINT_URL_6a480815-b295-4019-ba26-b60f50361c82: 'https://api.powerbi.com/v1.0/myorg'
2023-07-25T19:31:46.4601023Z ##[debug]ENDPOINT_AUTH_6a480815-b295-4019-ba26-b60f50361c82: '*****'
2023-07-25T19:31:46.4622676Z ##[debug]ENDPOINT_DATA_6a480815-b295-4019-ba26-b60f50361c82: '{"OrganizationType":"Public"}'
2023-07-25T19:31:46.4681877Z ##[debug]{
2023-07-25T19:31:46.4691427Z ##[debug]    "Url":  "https://api.powerbi.com/v1.0/myorg",
2023-07-25T19:31:46.4699732Z ##[debug]    "Data":  {
2023-07-25T19:31:46.4707844Z ##[debug]                 "OrganizationType":  "Public"
2023-07-25T19:31:46.4715892Z ##[debug]             },
2023-07-25T19:31:46.4724120Z ##[debug]    "Auth":  {
2023-07-25T19:31:46.4731995Z ##[debug]                 "parameters":  {
2023-07-25T19:31:46.4739975Z ##[debug]                                    "TenantId":  "45597f60-6e37-4be7-acfb-4c9e23b261ea",
2023-07-25T19:31:46.4748456Z ##[debug]                                    "ClientId":  "",
2023-07-25T19:31:46.4756435Z ##[debug]                                    "ClientSecret":  ***,
2023-07-25T19:31:46.4764609Z ##[debug]                                    "ClientCertificate":  ""
2023-07-25T19:31:46.4772648Z ##[debug]                                },
2023-07-25T19:31:46.4780534Z ##[debug]                 "scheme":  "None"
2023-07-25T19:31:46.4788492Z ##[debug]             }
2023-07-25T19:31:46.4796399Z ##[debug]}
2023-07-25T19:31:47.0153234Z ##[debug]7:31:47 PM - Connect-PowerBIServiceAccount begin processing with ParameterSet ServicePrincipal.
2023-07-25T19:31:47.0172111Z ##[debug]7:31:47 PM - Cmdlet version: 1.2.1077.0
2023-07-25T19:31:47.0888829Z Done processing Power BI Actions
2023-07-25T19:31:47.1247766Z ##[debug]Caught exception from task script.
2023-07-25T19:31:47.1272988Z ##[debug]Error record:
2023-07-25T19:31:47.1736235Z ##[debug]Connect-PowerBIServiceAccount : Failed to populate environments in settings
2023-07-25T19:31:47.1745623Z ##[debug]At C:\a_tasks\PowerBIActions_d5b7fec6-2b25-4742-905b-0dad97687df5\5.4.44\run.ps1:54 char:5
2023-07-25T19:31:47.1755378Z ##[debug]+ ...             Connect-PowerBIServiceAccount -Environment $organizationT ...
2023-07-25T19:31:47.1764551Z ##[debug]+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2023-07-25T19:31:47.1773970Z ##[debug]    + CategoryInfo          : WriteError: (Microsoft.Power...IServiceAccount:ConnectPowerBIServiceAccount) [Connect-Po    werBIServiceAccount], Exception
2023-07-25T19:31:47.1782713Z ##[debug]    + FullyQualifiedErrorId : Failed to populate environments in settings,Microsoft.PowerBI.Commands.Profile.ConnectPo    werBIServiceAccount
2023-07-25T19:31:47.1791702Z ##[debug]
2023-07-25T19:31:47.1806916Z ##[debug]Script stack trace:
2023-07-25T19:31:47.1835076Z ##[debug]at , C:\a_tasks\PowerBIActions_d5b7fec6-2b25-4742-905b-0dad97687df5\5.4.44\run.ps1: line 54
2023-07-25T19:31:47.1846074Z ##[debug]at , : line 1
2023-07-25T19:31:47.1855336Z ##[debug]at , : line 22
2023-07-25T19:31:47.1864185Z ##[debug]at , : line 18
2023-07-25T19:31:47.1872940Z ##[debug]at , : line 1
2023-07-25T19:31:47.1887724Z ##[debug]Exception:
2023-07-25T19:31:47.1920938Z ##[debug]System.Exception: Failed to populate environments in settings
2023-07-25T19:31:47.1930808Z ##[debug]   at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)
2023-07-25T19:31:47.2127335Z ##[error]Failed to populate environments in settings
2023-07-25T19:31:47.2128042Z ##[debug]Processed: ##vso[task.logissue type=error]Failed to populate environments in settings
2023-07-25T19:31:47.2134575Z ##[debug]Processed: ##vso[task.complete result=Failed]
2023-07-25T19:31:47.2398837Z ##[section]Finishing: Power BI Action: Publish
Additional information
The current agent pool being used is located in Azure and the proxy as well. The task is working fine, when we are using our old agent pool, which is not located in Azure and using a different proxy.

Hi @maikvandergaag,
Is there any update on this issue?

Hi @maikvandergaag,
Is there any update on this issue?

At first sorry for the late response as I have been working on a XPlat version of the extension: How did you setup your service connection

Task is using the default "Power BI Service Connection", the org type is set to Commercial and it is using Service Principal for authentication.

Oke what kind of authentication are you using for the SP? And what API connections have been setup?

Closing issue due to no response

authors: KristofKuli maikvandergaag


text:
Usage Error of validator, field, config, and info in Pydantic V2 when running test_reflexion.sh

Hi, I'm trying to run the testing scripts of test_reflexion.sh and I got the following error:
llm-gym/lib/python3.8/site-packages/pydantic/_internal/_decorators_v1.py", line 77, in make_generic_v1_field_validator
    raise PydanticUserError(
pydantic.errors.PydanticUserError: The `field` and `config` parameters are not available in Pydantic V2, please use the `info` parameter instead.

And on the doc of pydantic, there is also some description about the usage errors in Version 2:

The field argument is no longer available.

This indicates that in Pydantic V2 there are no longer field parameter, which is used in the code like here
however, when I check the environment.yml again, I find the required version is pydantic==2.3.0, pydantic-core==2.6.3 and I've got the above PydanticUserError with the required versions.
Therefore, is there any mistakes I've made during the environment setup or should I change the version of pydantic to V1?

I've found an official code transformation tool here, which is helpful for migration from v1 to v2

Hello, sorry about that, the new environment.yaml has fixed the problem by downgrading the version of pydantic at PR#3

ok, thanks for your help! I'll close this issue

authors: hzxwonder ziyuwan

repo: mail-ecnu/Text-Gym-Agents


text:
[FR] Ability to send bulk emails

Hi.
In this library, I miss the ability to send a bulk email.
Could it be added?
Thanks

Hi,
as Laravel does not have 1st party support for Bulk Emails, you need to use our PHP SDK to access Bulk functionality.

authors: Ajtak fosron

repo: mailersend/mailersend-laravel-driver


text:
Sending File Attachments

Does this library support the sending of file attachments?

@zzxoto that messages is not a function

Hi @krausekai here is an example:
const res = await mg.messages.create(domain, {
      from: fromEmail,
      to: toEmail,
      subject: "Hello 2",
      text: 'Text',
      inline: [your attachment here],
      attachment: [or here]
    });

Attachment with inline disposition. Can be used to send inline images. You can send several inline attachments.

const mailgun = require('mailgun.js');
const mgApiKey = process.env.MAILGUN_API_KEY;
const mgDomain = process.env.MAILGUN_DOMAIN;
const mg = mailgun.client({ username: 'api', key: mgApiKey });
const filepath = path.join(__dirname, 'logo.png');

const data = {
      from: 'user@example.com',
      to: email@example.com,
      subject: 'test mail',
      html: `<p>Hello, world</p>.`,
      attachment: [filepath],
    };

mg.messages.create(mgDomain, data)
  .then(msg => console.log(msg)) //
  .catch(err => console.log(err)); //

Email is properly sent but without attachment. logo.png is in the same folder. What am I missing?

const mailgun = require('mailgun.js');
const mgApiKey = process.env.MAILGUN_API_KEY;
const mgDomain = process.env.MAILGUN_DOMAIN;
const mg = mailgun.client({ username: 'api', key: mgApiKey });
const filepath = path.join(__dirname, 'logo.png');

const data = {
      from: 'user@example.com',
      to: email@example.com,
      subject: 'test mail',
      html: `<p>Hello, world</p>.`,
      attachment: [filepath],
    };

mg.messages.create(mgDomain, data)
  .then(msg => console.log(msg)) //
  .catch(err => console.log(err)); //

Email is properly sent but without attachment. logo.png is in the same folder. What am I missing?

@guanacone
According to the example, I think you should like
      attachment: [fs.createReadStream(filepath)],

authors: Tochukwuibe acro5piano andrii-yelis guanacone krausekai

repo: mailgun/mailgun-js


text:
Statistiques d'erreurs

Bonjour,
cela fait quelques jours que j'essaie de récupérer les erreurs de délivrabilité des mails sans succès.
Je cherche à récupérer les erreurs et leurs messages respectifs mais je n'ai rien en retour.
Dans un premier temps, j'ai essayé de récupéré le paramètre BounceReason avec le bout de code ci-dessous (il s'agit d'une partie d'une fonction):
$params = array(
    "method"  => 'GET',
    "AllMessages" => true,
    "ShowExtraData" => true,
    "MessageStatus" => 'Bounce',
    "Limit" => $limit,
    "CampaignID" => $campaignID
);
$response = $mj->messagesentstatistics($params);
$bounces = $response->Data;

Malheureusement, je ne récupère pas cette information malgré le paramètre ShowExtraDataà truecomme indiqué dans la doc.
Par ailleurs, j'ai essayé d'utilisé la méthode bouncestatistics en lui appliquant un filtre sur CampaignID afin de récupérer les paramètres IsBlocked et IsStatePermanent mais cette méthode me retoune un tableau vide...
Une idée ?

Bonjour @Romano83,
Merci de nous avoir contacté.
Concernant messagesentstatistics, le filtre MessageStatus doit être positionné à la valeur numérique du status (5 dans votre cas pour bounce).
Pour bouncestatistics, pouvez-vous svp confirmer que l'ID de Campagne est correct via une requête GET sur /campaign avec ce même ID ?
Aussi, pouvez-vous svp nous montrer un extrait de code ?
Merci d'avance,
Arnaud.

Bonjour @arnaudbreton,
Je viens de tester votre solution pour messagesentstatistics avec le filtre MessageStatus sur 5 mais j'ai le même résultat que précédemment.
Voici ce que j'utilise pour récupérer les différentes infos de ma campagne :
    // Je récupére l'ID de la newsletter en bdd après l'envoi de celle-ci
		$id = $this->_getParam('id', 0);
		$customvalue = "mj.nl=".$id;
		$mj = new Mailjet();
		$params = array('method' => 'VIEW', 'unique' => $customvalue);
		$response = $mj->campaign($params);
		$campaigns = $response->Data[0];
		$count = $response->Count;
		$campaign_id = $campaigns->ID;
		$status = $campaigns->Status;
		$this->view->status = $status;
		$params = array('method' => 'GET', 'CampaignID' => $campaign_id);
		$response = $mj->messagestatistics($params);
		$statistics = $response->Data[0];
		$this->view->statistics = $statistics;
		$model = new Application_Model_Emailing();
	    $params = array("method" => "GET","CampaignID" => $campaign_id);
		$bounces = $model->EmailBounce($mj, $params);

// Et la fonction EmailBounce
public function EmailBounce($mj, $params = array()){
	    $limit = 100;
	    $defaultsParams = array(
			"AllMessages" => true,
			"ShowExtraData" => true,
			"MessageStatus" => 5,
	        "Limit" => $limit,
	    );
	    $params = array_merge($params, $defaultsParams);
	    $response = $mj->messagesentstatistics($params);
		$bounces = $response->Data;
		return $bounces;
	}

Voici ce que me retourne la méthode /campaign
stdClass Object
(
    [Count] => 1
    [Data] => Array
        (
            [0] => stdClass Object
                (
                    [CampaignType] => 2
                    [ClickTracked] => 3
                    [CreatedAt] => 2015-06-30T13:15:30Z
                    [CustomValue] => mj.nl=3392440
                    [FirstMessageID] => 2.1110623319149E+16
                    [FromEmail] => xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
                    [FromID] => 1
                    [FromName] =>
                    [HasHtmlCount] => 3
                    [HasTxtCount] => 3
                    [ID] => 4617768139
                    [IsDeleted] =>
                    [IsStarred] =>
                    [ListID] => 1436702
                    [NewsLetterID] => 3392440
                    [OpenTracked] => 3
                    [SendEndAt] => 2015-06-30T13:15:30Z
                    [SendStartAt] => 2015-06-30T13:15:30Z
                    [SpamassScore] => 0
                    [Status] => 0
                    [Subject] => test statistiques mailjet 5
                    [UnsubscribeTrackedCount] => 0
                )

        )

    [Total] => 1
)

Et la méthode messagesentstatistics :
stdClass Object
(
    [Count] => 1
    [Data] => Array
        (
            [0] => stdClass Object
                (
                    [ArrivalTs] => 2015-06-30T13:15:30Z
                    [Blocked] =>
                    [Bounce] => 1
                    [BounceDate] =>
                    [BounceReason] =>
                    [CampaignID] => 4617768139
                    [Click] =>
                    [CntRecipients] => 1
                    [ComplaintDate] =>
                    [ContactID] => 1475345445
                    [Details] =>
                    [FBLSource] =>
                    [MessageID] => 2.1110623319149E+16
                    [Open] =>
                    [Queued] =>
                    [Sent] => 1
                    [Spam] =>
                    [StatePermanent] =>
                    [Status] => bounce
                    [ToEmail] => xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
                    [Unsub] =>
                )

        )

    [Total] => 1
)

Bonjour @Romano83, merci pour vos retours.
D'après ceux-ci vous obtenez bien un message pour votre campagne. Vous attendez-vous à un résultat différent?

Bonjour @arnaudbreton,
effectivement, j'obtiens bien un résultat mais je pensais récupérer les propriétés BounceReason, BounceDate et StateID comme indiqué dans la doc... surtout avec le filtre ShowExtraData à 1.
Je trouve qu'il est plus difficile (et peut être moins bien expliqué) de récupérer les erreurs qu'avec la version 1 de l'API... Avec la méthode reportEmailBounce, on retrouvait toutes ces infos.
Par ailleurs, pouvez-vous m'éclairer sur les raisons d'un tableau vide lorsque j'utilise la méthode bouncestatistics?
Voici ce que je fais :
// C'est la suite du code précédemment montré
$params = array(
    'method' => 'GET',
    'CampaignID' => $campaign_id,
);
$bounces2 = $mj->bouncestatistics($params);

et voici ce que j'obtiens :
stdClass Object
(
    [Count] => 0
    [Data] => Array
        (
        )

    [Total] => 0
)

Pourtant (à part si je ne comprends pas comment fonctionne cette méthode), je devrais bien obtenir quelque chose vu que j'ai au moins un mail qui à le statut Bounce ?

@Romano83, votre utilisation de l'API semble correcte. Afin de pouvoir vous fournir une aide plus avancée, pourriez vous svp ouvrir un ticket via notre support en mentionnant cette issue Github ?
Merci de votre compréhension,
Arnaud.

Bonjour @arnaudbreton un ticket est déjà ouvert sur votre support. Il s'agit du numéro 327124.
Merci pour votre aide,
Romain

Merci de votre retour @Romano83, je vous invite à continuer la discussion sur ce ticket.


text:
MF-323 - Rename interface implementation files in writers

This pull request resolves #323.
Signed-off-by: Dušan Borovčanin dusan.borovcanin@mainflux.com

Codecov Report

Merging #329 into master will decrease coverage by 1.97%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #329      +/-   ##
==========================================
- Coverage   89.35%   87.37%   -1.98%
==========================================
  Files          36       36
  Lines        1372     1339      -33
==========================================
- Hits         1226     1170      -56
- Misses        103      123      +20
- Partials       43       46       +3

Impacted Files
Coverage Δ

writers/influxdb/messages.go
88.57% <ø> (ø)

writers/mongodb/messages.go
100% <ø> (ø)

ws/api/transport.go
69.41% <0%> (-17.65%)
:arrow_down:

http/api/transport.go
70% <0%> (-17.24%)
:arrow_down:

things/api/http/endpoint.go
92.66% <0%> (-0.51%)
:arrow_down:

things/api/grpc/server.go
97.56% <0%> (+2.32%)
:arrow_up:

Continue to review full report at Codecov.

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

@dusanb94 please update the branch

authors: codecov-io drasko dusanb94

repo: mainflux/mainflux


text:
Add support for GNOME 40

This is a simple change to support GNOME 40 (and probably 3.38 too)

@TheWeirdDev
Thanks!  That works for me.

It worked, thanks

someone do something for 47 :sob:

@NormTurtle, did something change in 47? Can you open a new issue and we can discuss it there?
I'm going to close this pull request because as it seems a bit outdated by now...

@maiself im sorry i can't give much about on technical changes related to this project.
im a just a user not a developer.
i want that extension to get worked.
to save my eyees in deep night when watching lectures with white boards.

but, you can still see how other have some workarounds.
https://github.com/cg505/gnome-shell-grayscale-window
https://github.com/JackKenney/gnome-true-color-invert ( too old i guess?)

I just looked thru the 47 release notes and didn't see anything that might affect this extension, so it may be as simple as adding version 47 to metadata.json.
I see that the grayscale extension already has 47 listed, so it should be easy to compare for any changes. I don't know when I'll be able to upgrade to 47 to test tho.
If you know how to find it and edit it, adding the version to the list in metadata.json and then restarting may get things work right away. Otherwise please be patient until I can get around to updating things. Thanks for bringing this to my attention. I know how important dark mode and brightness inversion can be, I get headaches from bright screens, it's why I created this extension in the first place 🙂

@NormTurtle, just send a new version off for review, so should update automatically in a day or two when it passes. All that was needed was adding version 47 to the metadata file.

Thank you so much

authors: JumperLuko NormTurtle TheWeirdDev flatcap maiself


text:
[BUG]: Process Builder Error 132 in AGC compress / Illegal instruction (core dumped)

Description
Building and Loading Phase AGC compress error
Hello, I am trying out the software in Rice Data. I experienced an error in AGC compress. For reference I am using IR 64 and Azucena genomes with IRGSP as my reference from NCBI.
Error from the terminal
[main] INFO net.maizegenetics.phgv2.cli.AgcCompress 2024-10-21 04:28:13,074: Starting AGC compression: validate the URI
[main] INFO net.maizegenetics.phgv2.utils.VariantLoadingUtils 2024-10-21 04:28:13,085: begin Command:conda run -n phgv2-conda tiledbvcf stat --uri vcf_dbs/hvcf_dataset
[main] INFO net.maizegenetics.phgv2.utils.VariantLoadingUtils 2024-10-21 04:28:14,468: Using  TileDB datasets created in folder vcf_dbs.
[main] INFO net.maizegenetics.phgv2.cli.AgcCompress 2024-10-21 04:28:14,474: Verifying FASTA files id lines are annotated
[main] INFO net.maizegenetics.phgv2.cli.AgcCompress 2024-10-21 04:28:14,478: VerifyFileAnnotation: time: 0.00253612 secs.
[main] INFO net.maizegenetics.phgv2.cli.AgcCompress 2024-10-21 04:28:14,479: calling loadAGCFiles
[main] INFO net.maizegenetics.phgv2.cli.AgcCompress 2024-10-21 04:28:14,479: begin Command to create/append:conda run -n phgv2-conda agc create -i data/assemblies_list.txt -o vcf_dbs/assemblies.agc output/updated_assemblies/IRGSPRef.fa
[main] ERROR net.maizegenetics.phgv2.cli.AgcCompress 2024-10-21 04:28:15,994: agc create run via ProcessBuilder returned error code 132
[main] ERROR net.maizegenetics.phgv2.cli.AgcCompress 2024-10-21 04:28:15,994: Error: could not create agc compressed file.
Exception in thread "main" java.lang.IllegalArgumentException: Error running ProcessBuilder for agc create or append: Error running ProcessBuilder to compress agc files: 132
at net.maizegenetics.phgv2.cli.AgcCompress.loadAGCFiles(AgcCompress.kt:214)
at net.maizegenetics.phgv2.cli.AgcCompress.processAGCFiles(AgcCompress.kt:123)
at net.maizegenetics.phgv2.cli.AgcCompress.run(AgcCompress.kt:76)
at com.github.ajalt.clikt.parsers.Parser.parse(Parser.kt:306)
at com.github.ajalt.clikt.parsers.Parser.parse(Parser.kt:319)
at com.github.ajalt.clikt.parsers.Parser.parse(Parser.kt:40)
at com.github.ajalt.clikt.core.CliktCommand.parse(CliktCommand.kt:458)
at com.github.ajalt.clikt.core.CliktCommand.parse$default(CliktCommand.kt:455)
at com.github.ajalt.clikt.core.CliktCommand.main(CliktCommand.kt:475)
at com.github.ajalt.clikt.core.CliktCommand.main(CliktCommand.kt:482)
at net.maizegenetics.phgv2.cli.PhgKt.main(Phg.kt:38)
Command exited with non-zero status 1
Here is the agc_create_error.log content
/tmp/tmpza56jx6g: line 3: 71174 Illegal instruction     (core dumped) agc create -i data/assemblies_list.txt -o vcf_dbs/assemblies.agc output/updated_assemblies/IRGSPRef.fa
Previous command: It had no error as I redid the prepare-assemblies
[main] INFO net.maizegenetics.phgv2.cli.PrepareAssemblies 2024-10-08 04:51:36,768: creating assembliesList, calling createParallelAnnotatedFastas
[main] INFO net.maizegenetics.phgv2.cli.PrepareAssemblies 2024-10-08 04:51:36,840: Adding entries to the inputChannel:
[main] INFO net.maizegenetics.phgv2.cli.PrepareAssemblies 2024-10-08 04:51:36,842: adding IRGSPRef to the inputChannel
[main] INFO net.maizegenetics.phgv2.cli.PrepareAssemblies 2024-10-08 04:51:36,843: adding SeqAzucena to the inputChannel
[main] INFO net.maizegenetics.phgv2.cli.PrepareAssemblies 2024-10-08 04:51:36,843: adding SeqIR64 to the inputChannel
[main] INFO net.maizegenetics.phgv2.cli.PrepareAssemblies 2024-10-08 04:51:36,843: Done adding data to the inputChannel
annotateFasta: entry = IRGSPRef
annotateFasta: entry = SeqIR64
annotateFasta: entry = SeqAzucena
Files used
Here are the txt files used to annotate.
annotation_keyfile.txt
assemblies_list.txt
Other Files can be downloaded through these links
Reference Genome: Nipponbare IRGSP SNP REF
Download Link: https://ftp.ncbi.nlm.nih.gov/genomes/all/GCF/001/433/935/GCF_001433935.1_IRGSP-1.0/GCF_001433935.1_IRGSP-1.0_genomic.fna.gz
Anchorwave GFF file: Nipponbare IRGSP SNP GFF
Download Link: https://ftp.ncbi.nlm.nih.gov/genomes/all/GCF/001/433/935/GCF_001433935.1_IRGSP-1.0/GCF_001433935.1_IRGSP-1.0_genomic.gff.gz
Short Sequence Variants(1): Azucena SNP
Download Link: https://ftp.ncbi.nlm.nih.gov/genomes/all/GCA/009/830/595/GCA_009830595.1_AzucenaRS1/GCA_009830595.1_AzucenaRS1_genomic.fna.gz
Short Sequence Variants(2):  IR 64 SNP
Download Link: https://ftp.ncbi.nlm.nih.gov/genomes/all/GCA/009/914/875/GCA_009914875.1_OsIR64RS1/GCA_009914875.1_OsIR64RS1_genomic.fna.gz
Thank you!
Expected behavior
Creation of the assemblies.agc in the vcf_dbs directory
PHG version
2.4.7.161

It looks like AGC didn't install properly from the conda environment. You can confirm this by trying to run an AGC command via the command line in the phgv2-conda environment, eg.
agc create ref.fa in1.fa in2.fa > col.agc
I expect you'll get the same "Illegal instruction (core dumped)" error message.
What platform and architecture are you working on?  There isn't a Bioconda build released for ARM (M-series) Macs yet, but you can build AGC from source if you need to work on an ARM machine.

Hello just checked, and right it did not install correctly.
I was using a x64 architecture in ubuntu. The error points to the AVX expressions in the cpu.
I found it in this issue page: https://github.com/refresh-bio/agc/issues/2.
Do note that I have not verified this to be the case
I am still finding a workaround as of the moment

Hello I found a way to circumvent agc problem for now by using another computer, but I experienced another error in a now in create ranges. Would this be better if i made it another issue? Does this have to do with the files I have used?
For now this is the issue:
java.lang.IllegalArgumentException: createFlankingList: chrom NC_001320.1 not found in reference fasta.
at net.maizegenetics.phgv2.utils.GeneralUtilitiesKt.createFlankingList(GeneralUtilities.kt:88)
at net.maizegenetics.phgv2.cli.CreateRanges.run(CreateRanges.kt:345)
at com.github.ajalt.clikt.parsers.Parser.parse(Parser.kt:279)
at com.github.ajalt.clikt.parsers.Parser.parse(Parser.kt:292)
at com.github.ajalt.clikt.parsers.Parser.parse(Parser.kt:41)
at com.github.ajalt.clikt.core.CliktCommand.parse(CliktCommand.kt:457)
at com.github.ajalt.clikt.core.CliktCommand.parse$default(CliktCommand.kt:454)
at com.github.ajalt.clikt.core.CliktCommand.main(CliktCommand.kt:474)
at com.github.ajalt.clikt.core.CliktCommand.main(CliktCommand.kt:481)
at net.maizegenetics.phgv2.cli.PhgKt.main(Phg.kt:58)
Exception in thread "main" java.lang.IllegalArgumentException: ERROR - createFlankingList faulted with message: createFlankingList: chrom NC_001320.1 not found in reference fasta.
at net.maizegenetics.phgv2.utils.GeneralUtilitiesKt.createFlankingList(GeneralUtilities.kt:108)
at net.maizegenetics.phgv2.cli.CreateRanges.run(CreateRanges.kt:345)
at com.github.ajalt.clikt.parsers.Parser.parse(Parser.kt:279)
at com.github.ajalt.clikt.parsers.Parser.parse(Parser.kt:292)
at com.github.ajalt.clikt.parsers.Parser.parse(Parser.kt:41)
at com.github.ajalt.clikt.core.CliktCommand.parse(CliktCommand.kt:457)
at com.github.ajalt.clikt.core.CliktCommand.parse$default(CliktCommand.kt:454)
at com.github.ajalt.clikt.core.CliktCommand.main(CliktCommand.kt:474)
at com.github.ajalt.clikt.core.CliktCommand.main(CliktCommand.kt:481)
at net.maizegenetics.phgv2.cli.PhgKt.main(Phg.kt:58)

Yes, problems with different parts of the code should be written as separate issues.
The error above shows an inconsistency in your files.  It appears you either have the wrong reference fasta, or wrong gff.  The naming convention in your reference fasta does not match what is in the gff.  Please check your files and open a new issue if you still see a problem - thanks.

@pmvijar regarding the original AGC instructions issue, if you're willing to compile the binary yourself you should be able to get it working on the first computer. AGC provides a "no-avx" makefile - or alternatively, using the standard makefile with PLATFORM=SSE2 may also work. These more specialized builds aren't available through conda, unfortunately, so it's up to you whether it's worth the effort to compile them for this machine.

The files errors were resolved.
For the agc, I'll be migrating the data to a compatible server.

authors: aberthel lynnjo pmvijar


text:
Simpler install instruction

No need to specify a version, Composer will automatically get a constraint for the latest stable if none is passed.
Also Archer isn't in accounting, Cyril is :d

Thanks!

authors: Anahkiasen maknz

repo: maknz/slack


text:
addimage appears not to work for new collections

bot_1      | Traceback (most recent call last):
bot_1      |   File "/usr/local/lib/python3.8/site-packages/discord/ext/commands/core.py", line 83, in wrapped
bot_1      |     ret = await coro(*args, **kwargs)
bot_1      |   File "/usr/src/app/src/picturecommands.py", line 442, in add_image
bot_1      |     image_collection = self.get_cmd_from_alias(image_collection)
bot_1      |   File "/usr/src/app/src/picturecommands.py", line 379, in get_cmd_from_alias
bot_1      |     cursor.execute(
bot_1      |   File "/usr/local/lib/python3.8/site-packages/psycopg2/extras.py", line 243, in execute
bot_1      |     return super(RealDictCursor, self).execute(query, vars)
bot_1      | TypeError: not all arguments converted during string formatting

Fixed, there were a bunch of issues.


text:
cachedJSON function Compile Error

This function below in the response protocol gives the following compile error: 'Call can throw, but it is not marked with 'try' and the error is not handled'
   private lazy var cachedJSON: JSON = {
        return JSON(data: self.data ?? Data())
    }()

I've created a pull request for this issue. Please check #5.

authors: Ruckt aleciogomes

repo: malcommac/HermesNetwork


text:
Phone generation function

Simple function for international phone number generation with test and updated readme file

Hi,
Thanks for the PR and implementation, here's a problem with your commit. You used {{%numericRandomizer 3 0 9%}} to generate 3 numbers in [0, 9] but the numericRandomizer does not work the way you intended. When you use this expression({{%numericRandomizer 3 0 9%}}) it would generate 3 numbers in [0, 9) just because of the nature of  rand.Int31n function. So, basically current version would not generate any 9s. Can you please fix it, so I can merge the PR?

Hello, thank you for review, I have fixed this issue. Sorry for that.

Merged. Thanks!

authors: dmitrijivanenko malisit

repo: malisit/kolpa


text:
Custom Tree Line Height

Summary
Just setting Compact SideBar: true/false is not enough, compact is too compact and disabling it is too sparse.
...
Expected behavior
setting a custom line height on the tree, instead just like we're allowed to on the sidebar identing

This is a change I already made for version 0.9 but because of hard to reproduce issues I couldn't release the version for the time being.

thank you @mallowigi do you know which previous versions does not include the new tree spacing? So I can just rollback for now

i think version 0.4.0

thanks

@mallowigi installed EAP instead, thanks man!

authors: hernandev mallowigi

repo: mallowigi/material-theme-jetbrains-eap


text:
Examples use ?, not try!, not unwrap (C-QUESTION-MARK)

C-QUESTION-MARK

Fixed in 47cfbce8404709f77d2b287595e12278993ff014 & ea423f64fe0db83988791ca5b69f523d0ef46505.

Last missed unwrap replaced in ac42a60bd165b349fd7e49dadca7c00a41ccf9bf.


text:
Make image useable for non-root user

What do you see as the best way to make micromamba available to a non-root user? Due to the defined environment variable BASH_ENV=/root/.bashrc, I see permission errors. A simple way could be to make /root/.bashrc readable for everyone but that seems wrong.
Also, I guess I would need to activate the conda base environment the same way as was done for the root user. Do any other pitfalls come to your mind?

Hi @Midnighter -- thank you for your interest in Micromamba. Here is one approach that you could take:
FROM mambaorg/micromamba:0.12.0

RUN groupadd conda && \
        useradd --home-dir /home/conda --create-home --shell /bin/bash --skel /dev/null -g conda conda

RUN chown -R conda.conda /opt/conda

USER conda

ENV BASH_ENV /home/conda/.bashrc

RUN /bin/micromamba shell init -s bash -p $MAMBA_ROOT_PREFIX && \
        echo "micromamba activate base" >> ~/home/conda/.bashrc

I am working on updating the image to make this more straight forward, but I'm not sure when I'll get that wrapped up.

Thank you for the suggestion! If it's easier to outline what you have in mind than to actually do it, feel free to post it here and I can work on the changes.

FWIW, I was able to use a non-root user just by clearing BASH_ENV and bootstrapping the non-root user's .bashrc:
ENV BASH_ENV=
RUN /bin/micromamba shell init -s bash -p $MAMBA_ROOT_PREFIX && \
  echo "micromamba activate base" >> $HOME/.bashrc

Another interesting point on this topic would be to make the pre-installed tools available to any user. The scenario I describe is that I would create a Docker image derived from the micromamba image and install a couple of conda packages as root. Then I run that image with a non-root id, for example, docker run -u 1001:10001.
In order for any user id to be able to use the conda packages, the BASH_ENV should have permissions to be read by all (so maybe it should be in a different place), and /opt/conda would need read permissions for all, as well as binaries need to be executable by all.
I would do all of this in my derived image definition but I wanted to ask for your feedback if you think that's a decent approach.

Implemented in dc4bf68302b2f19e80133c7ce0ff2417c09987be.

authors: Midnighter shane-axiom wholtz

repo: mamba-org/micromamba-docker


text:
Failure to solve pip dependencies from environment.yml when using docker (podman works)

Create the following env.yml

name: test
channels:
  - conda-forge
dependencies:
  - python=3.8
  - pip
  - pip:
    - requests

Run the following commands in that same directory

Docker (broken example from readme):
docker run -it --rm -v $(pwd):/tmp --privileged mambaorg/micromamba:latest \
     /bin/bash -c "micromamba create --yes --name new_env --file env.yml && \
		   micromamba env export --name new_env --explicit > env.lock"

Result:
Installing pip packages: requests
error    libmamba Subprocess call failed: Invalid argument
critical libmamba Subprocess call failed. Aborting.

Podman (works):
podman run -it --rm -v $(pwd):/tmp --userns=keep-id mambaorg/micromamba:latest \
   /bin/bash -c "micromamba create --yes --name new_env --file env.yml && \
		 micromamba env export --name new_env --explicit > env.lock"

Result: produces env.lock
Note: the only difference between the two commands is --userns=keep-id and --privileged  for docker, this is due to SELinux but should not impact the result.
Related: https://github.com/mamba-org/mamba/issues/2388

Please see issue #267 and let me know if the solution presented there works for you.

authors: mjlbach wholtz