Why should we train NetL separately in train_L_step_w

In the function train_L_step_w, line 192, in train.py, we the gradients of loss are firstly propagated to NetL with Doc3D data set. Then in the gradients are propagated to NetL with DIW. People update the NetL twice in one step (optimizer_L.step()x2).
I have a question. We compute the spvLoss.lloss and warp_diff_loss with the corresponding data set and a supervision mask (using the torch.where function to remove unrelative gradients) , so that we can update the NetL in one step.
I read your paper, did not read the issues, and train the NetL with my idea. It does not converge.
According to the optimization theory, these two training tricks will lead to different NetLs. Therefore, I want to know the result of my training trick.  Or let us check the reason.

Sry my bad. I saw the email and I must reply in mind...
IIUC your idea is correct. It is only a different implementation.
I am not sure about it does not converge. When you train the Tnet in the weakly supervised manner, you should see the loss on the data from doc3d fluctuates (as the network has already converged when it was trained on doc3d only), while the loss on the data from diw drops. Since there is a 0.1 multiplier, if you just monitor the whole loss, you may not see significant changes.
Also I found the weakly sup training is tricky. The loss might not drop in the first several epochs.
Below might be (did not document the exp well so I am not 100% sure lol) part of my training log for your reference:
100,0.005063588265329599,0.02370934202136986
200,0.004935386124998331,0.022192930404885902
300,0.005119685549288988,0.021928391292158716
400,0.004981142934411764,0.02187072460517174
500,0.0050409529358148575,0.020735550189557334
600,0.0049947695806622505,0.0211542390116961
700,0.004915028810501099,0.020587545698645834
800,0.004990944638848305,0.020549847342187944
900,0.004903901368379593,0.02045272541466805
1000,0.005064345896244049,0.02088677820217645
1100,0.0049436925910413265,0.020250055080146698
1200,0.004958824720233679,0.020161601953728493
1300,0.004986349493265152,0.02039550368504056
1400,0.00499705970287323,0.019787318414702548
1500,0.005011213012039661,0.01999400551726301
1600,0.004894820973277092,0.019615766742502306
1700,0.005025567952543497,0.01998966940524982
1800,0.005114749539643526,0.01963189327273391
1900,0.005022508092224598,0.01974157745019287
2000,0.005051152780652046,0.019586424166879952
2100,0.0048703644424676895,0.01913408813931006
2200,0.004957091063261032,0.018964561364001764
2300,0.005040901713073254,0.019552078878607746
2400,0.00502112926915288,0.019812215049959395
2500,0.0051467400044202805,0.019536561044368718
2600,0.0051370542496442795,0.01931596776574929
2700,0.0049997540190815926,0.019503309363752386
2800,0.00503464974462986,0.01917101903851312
2900,0.004995362833142281,0.0189093729876982
3000,0.005060319788753986,0.019391178179471037
3100,0.0050315591506659985,0.018922625512100506
3200,0.0051877968944609165,0.019159920200847214
3300,0.00510516669601202,0.019096903228442975
3400,0.005153291393071413,0.01920557122347776
3500,0.005053812172263861,0.018502684357541974
3600,0.0050436812452971935,0.019163471748832067
3700,0.005045927129685879,0.018949978152939296
3800,0.005036205053329468,0.018755136477167353
3900,0.005005819257348776,0.018657028925450434
4000,0.005015464965254068,0.0186833193359192
4100,0.005152611993253231,0.0187683873301277
4200,0.005056890659034252,0.018977879092028797
4300,0.005157520994544029,0.01858032355662087
4400,0.005055396351963282,0.01836480664451265
4500,0.005114920437335968,0.018911168594058655
4600,0.005029668565839529,0.01864923090862618
4700,0.005187106318771839,0.01893219656656726
4800,0.005118091590702534,0.018685637584060184
4900,0.005208715330809355,0.01891479855790604
5000,0.005045102909207344,0.018463619530186146
5100,0.005198843311518431,0.018528455137144
5200,0.005084374453872442,0.01821221580195834
5300,0.005017156712710857,0.018156634556730264
5400,0.005164026748389006,0.018550131587547935
5500,0.005054773297160864,0.018286904431760346
5600,0.005188659764826298,0.01867897027372242
5700,0.005099665839225054,0.018122819249187076
5800,0.004954097326844931,0.01821176953402006
5900,0.004983177874237299,0.018063550908384268
6000,0.0050760190933942795,0.01838901475107358
6100,0.0050915866158902645,0.018429808222736543
6200,0.005066524725407362,0.018086263409570882
6300,0.005140822846442461,0.018022173762230892
6400,0.004976288881152868,0.017803625915408766
6500,0.005096477456390858,0.018190466708287462
6600,0.005129553377628326,0.018321200010965367
6700,0.005067517980933189,0.01847482156500423
6800,0.0051100836135447025,0.018117362248123194
6900,0.004947172477841377,0.017991205841614632
7000,0.00500882463529706,0.01808356638170746
7100,0.005111531354486942,0.018221665996114314
7200,0.005158735904842615,0.017969297821906868
7300,0.005106328055262566,0.018003088725714884
7400,0.005048552993685007,0.01797017322638618
7500,0.00505921570584178,0.01773643644663264
7600,0.005083793308585882,0.017740979126475025
7700,0.0050888885743916035,0.017991992946363743
7800,0.005112549755722284,0.017688068847847762
7900,0.0050511048175394535,0.018229370963517653
8000,0.0049722096882760525,0.017501540532057193
8100,0.005142809357494116,0.017890013834209795
8200,0.005066135432571173,0.01744315579839847
8300,0.00511603057384491,0.01748281598038487
8400,0.005207541864365339,0.0179856979743903
8500,0.005039854906499386,0.018147616880004595
8600,0.005058737006038427,0.01751584804817577
8700,0.0050256880931556225,0.017666095496568404
8800,0.0051104240119457245,0.01791217255691693
8900,0.005057178437709808,0.018108111947888146
9000,0.005073448643088341,0.01751806254175639
9100,0.005069409497082233,0.01763443953852933
9200,0.004967368673533201,0.01781840996920026
9300,0.005104700569063425,0.017298269710773778
9400,0.005121214780956507,0.018104995522937768
9500,0.005068340804427862,0.01769434156151156
9600,0.00506182387471199,0.0177548410635703
9700,0.005070047918707132,0.01768864319672391
9800,0.005082407034933567,0.017681782471694288
9900,0.005042869132012129,0.017680984781758932
10000,0.005144722759723663,0.017649849083728693
10100,0.005149520467966795,0.01782877853451249
10200,0.005029845517128706,0.017689869467588756
10300,0.005004498641937971,0.01770577735083724
10400,0.005142222158610821,0.017733169813551455
10500,0.005035723093897104,0.017489189457483074
10600,0.005146523471921682,0.017886761965415422
10700,0.005066465120762587,0.017881848862513334
10800,0.00519703421741724,0.017751254158660176
10900,0.0052534244023263454,0.01766847537581638
11000,0.005095356609672308,0.017325492920294554
11100,0.005109227262437344,0.017326535374238408
11200,0.005051949992775917,0.01724445531971433
11300,0.004993387497961521,0.01717610032537176
11400,0.005004818085581064,0.017540716627468658
11500,0.005011163651943207,0.01731159731750203
11600,0.0050667268224060535,0.0176553093727354
11700,0.005025411956012249,0.01742547087709361
11800,0.005094574298709631,0.017385293080985235
11900,0.004999820608645678,0.01711685024227235
12000,0.005150946322828531,0.017528203680422204
12100,0.004913340322673321,0.01708819018085543
12200,0.00516160111874342,0.01752402819259588
12300,0.005033752880990505,0.017194476921818344
12400,0.005021130666136742,0.01742381763959208
12500,0.004977911710739136,0.017267174064356915
12600,0.005074720364063978,0.017081996364153303
12700,0.005014317575842142,0.01724405743882404
12800,0.00513584865257144,0.017619379132109272
12900,0.005105980206280947,0.017341053219106187
13000,0.004963347222656012,0.017015018766546954
13100,0.005080872680991888,0.01708559109772523
13200,0.005049297120422125,0.017389978788253914
13300,0.0049912030808627605,0.017269668142476043
13400,0.005138266831636429,0.017159466563777034
13500,0.005093121435493231,0.017481376159964333
13600,0.005029590800404549,0.01702950325446383
13700,0.00511751975864172,0.017336320683297865
13800,0.004985549487173557,0.01731252500695391
13900,0.004978805314749479,0.016822183279029793
14000,0.0050791045650839806,0.017147356183233323
14100,0.005115289706736803,0.01718729724977572
14200,0.005044733174145222,0.016885606143606388
14300,0.005097928922623396,0.016765603508410516
14400,0.004988375585526228,0.017009330714409302
14500,0.005115858744829893,0.01718717492041414
14600,0.005077785812318325,0.017138921134050442
14700,0.005027669947594404,0.017026507674188014
14800,0.005161136854439974,0.017272212045865952
14900,0.005096090957522392,0.017131204053052896
15000,0.005074597895145416,0.017328664095173592
15100,0.0050181495025753975,0.016989927437741192
15200,0.005027234088629484,0.016949108675530625
15300,0.005086027085781097,0.016982037915826736
15400,0.0051588015630841255,0.016979691761674635
15500,0.005010928027331829,0.016853461790167275
15600,0.005075820256024599,0.01677895493904782
15700,0.005030659027397633,0.017015818410753693
15800,0.0051097567193210125,0.016914397613342062
15900,0.005015738774091005,0.017168930507203133
16000,0.00513323163613677,0.01704400165707704
16100,0.005079986061900854,0.017215396960201895
16200,0.005077979993075132,0.017389186217122224
16300,0.005066171288490295,0.01703552727312825
16400,0.005185272078961134,0.017332382197871605
16500,0.005027707666158676,0.017063749420024525
16600,0.005190769676119089,0.01736109989003955
16700,0.005173949524760246,0.017408522330081975
16800,0.005009079817682505,0.01707219486207405
16900,0.005081778857856989,0.017054250524635762
17000,0.005094040185213089,0.017123837941243718
17100,0.005071504041552544,0.017141971764489547
17200,0.005277260672301054,0.017408842515744122
17300,0.005172219593077898,0.016957586480792358
17400,0.005042460281401873,0.01743945400296821
17500,0.005064051598310471,0.016741323842592103
17600,0.005149027798324823,0.01723910541509017
17700,0.004989778622984886,0.017045945484915833
17800,0.005025830119848251,0.016978719986969776
17900,0.005147910676896572,0.017312073484943385
18000,0.005073569715023041,0.01695158000239283
18100,0.005074741318821907,0.017127971701446174
18200,0.00505696889013052,0.016980369910154607
18300,0.00505310483276844,0.017111300210977513
18400,0.005096033681184053,0.01731119412993352
18500,0.004993887152522802,0.017083545935357436
18600,0.0052564446814358234,0.017154309001907175
18700,0.005086237099021673,0.017093555657946506
18800,0.0050272406078875065,0.01698923420892316
18900,0.005038172472268343,0.01731060073459176
19000,0.004986036103218794,0.016878104985226294
19100,0.00506561016663909,0.017287441577607452
19200,0.0050743576139211655,0.01709481608641651
19300,0.005089832469820976,0.017113640417450386
19400,0.0050940606743097305,0.017131619414273318
19500,0.004956440534442663,0.016614284556741632

the first col might steps (sry cannot remember all the details) and the 2nd col is the sup loss and 3rd col is w sup loss. You can see the 2nd col just fluctuated while the 3rd col dropped from 0.024 to 0.016


[src/parser.rs] Loosen parse validation so that just the executable path suffices

EDIT: Curiously ./target/debug/makers --version and ./target/debug/makers --help now works but ./target/debug/cargo-make --version and ./target/debug/cargo-make --help work as if neither --help nor --version were provided

if cargo make used to work, now why this parser needs fixing?
also, any change here needs to come with a test

closing as not needed


2020/03/15 19:40:36 [WARN] Log levels other than TRACE are currently unreliable, and are supported only for backward compatibility.
  Use TF_LOG=TRACE to see Terraform's internal logs.
  ----
2020/03/15 19:40:36 [DEBUG] Service discovery for registry.terraform.io at https://registry.terraform.io/.well-known/terraform.json
Initializing provider plugins...
- Checking for available provider plugins...
2020/03/15 19:40:37 [DEBUG] fetching provider versions from "https://registry.terraform.io/v1/providers/-/aws/versions"
2020/03/15 19:40:37 [DEBUG] GET https://registry.terraform.io/v1/providers/-/aws/versions
2020/03/15 19:40:37 [DEBUG] fetching provider location from "https://registry.terraform.io/v1/providers/hashicorp/aws/2.53.0/download/darwin/amd64"
2020/03/15 19:40:37 [DEBUG] GET https://registry.terraform.io/v1/providers/hashicorp/aws/2.53.0/download/darwin/amd64
2020/03/15 19:40:38 [DEBUG] verified GPG signature with key from HashiCorp Security<EMAIL_ADDRESS>2020/03/15 19:40:38 [DEBUG] getting provider "aws" (hashicorp/aws) version "2.53.0"
2020/03/15 19:40:38 [DEBUG] plugin cache is disabled, so downloading aws 2.53.0 from https://releases.hashicorp.com/terraform-provider-aws/2.53.0/terraform-provider-aws_2.53.0_darwin_amd64.zip?checksum=sha256:1c971e22842fe2e74f40b01f0d1e30ed3621e0af07504f8245480a301af0ef06
- Downloading plugin for provider "aws" (hashicorp/aws) 2.53.0...
2020/03/15 19:45:59 [DEBUG] looking for the aws 2.53.0 plugin we just installed
2020/03/15 19:45:59 [DEBUG] checking for provider in ".terraform/plugins/darwin_amd64"
2020/03/15 19:45:59 [DEBUG] found provider "terraform-provider-aws_v2.53.0_x4"
2020/03/15 19:45:59 [DEBUG] all plugins found discovery.PluginMetaSet{discovery.PluginMeta{Name:"aws", Version:"2.53.0", Path:"/Users/example/code/.external/terragrunt_issue_1087/tg-files/dep/var-c-dep/.terragrunt-cache/ALAW-9qKrWFB6k-nU6L3O4aLABI/bQYZk3-HsFAyd3gqa0dF80ehSoE/tf-modules/ssm-test-dep/.terraform/plugins/darwin_amd64/terraform-provider-aws_v2.53.0_x4"}:struct {}{}}
2020/03/15 19:45:59 [DEBUG] filtered plugins discovery.PluginMetaSet{discovery.PluginMeta{Name:"aws", Version:"2.53.0", Path:"/Users/example/code/.external/terragrunt_issue_1087/tg-files/dep/var-c-dep/.terragrunt-cache/ALAW-9qKrWFB6k-nU6L3O4aLABI/bQYZk3-HsFAyd3gqa0dF80ehSoE/tf-modules/ssm-test-dep/.terraform/plugins/darwin_amd64/terraform-provider-aws_v2.53.0_x4"}:struct {}{}}
2020/03/15 19:45:59 [DEBUG] checking for provider in "."
2020/03/15 19:45:59 [DEBUG] checking for provider in "/usr/local/bin"
2020/03/15 19:45:59 [DEBUG] checking for provider in ".terraform/plugins/darwin_amd64"
2020/03/15 19:45:59 [DEBUG] found provider "terraform-provider-aws_v2.53.0_x4"
2020/03/15 19:45:59 [DEBUG] found valid plugin: "aws", "2.53.0", "/Users/example/code/.external/terragrunt_issue_1087/tg-files/dep/var-c-dep/.terragrunt-cache/ALAW-9qKrWFB6k-nU6L3O4aLABI/bQYZk3-HsFAyd3gqa0dF80ehSoE/tf-modules/ssm-test-dep/.terraform/plugins/darwin_amd64/terraform-provider-aws_v2.53.0_x4"
2020/03/15 19:45:59 [DEBUG] checking for provider in ".terraform/plugins/darwin_amd64"
2020/03/15 19:45:59 [DEBUG] found provider "terraform-provider-aws_v2.53.0_x4"

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
2020/03/15 19:45:59 [WARN] Log levels other than TRACE are currently unreliable, and are supported only for backward compatibility.
  Use TF_LOG=TRACE to see Terraform's internal logs.
  ----
2020/03/15 19:45:59 [INFO] Terraform version: 0.12.23
2020/03/15 19:45:59 [INFO] Go runtime version: go1.12.13
2020/03/15 19:45:59 [INFO] CLI args: []string{"/usr/local/bin/terraform", "plan", "-lock-timeout=20m"}
2020/03/15 19:45:59 [DEBUG] Attempting to open CLI config file: /Users/example/.terraformrc
2020/03/15 19:45:59 [DEBUG] File doesn't exist, but doesn't need to. Ignoring.
2020/03/15 19:45:59 [INFO] CLI command args: []string{"plan", "-lock-timeout=20m"}
2020/03/15 19:45:59 [WARN] Log levels other than TRACE are currently unreliable, and are supported only for backward compatibility.
  Use TF_LOG=TRACE to see Terraform's internal logs.
  ----
2020/03/15 19:45:59 [DEBUG] checking for provider in "."
2020/03/15 19:45:59 [DEBUG] checking for provider in "/usr/local/bin"
2020/03/15 19:45:59 [DEBUG] checking for provider in ".terraform/plugins/darwin_amd64"
2020/03/15 19:45:59 [DEBUG] found provider "terraform-provider-aws_v2.53.0_x4"
2020/03/15 19:45:59 [DEBUG] found valid plugin: "aws", "2.53.0", "/Users/example/code/.external/terragrunt_issue_1087/tg-files/dep/var-c-dep/.terragrunt-cache/ALAW-9qKrWFB6k-nU6L3O4aLABI/bQYZk3-HsFAyd3gqa0dF80ehSoE/tf-modules/ssm-test-dep/.terraform/plugins/darwin_amd64/terraform-provider-aws_v2.53.0_x4"
2020/03/15 19:45:59 [DEBUG] checking for provisioner in "."

Perhaps it solved me a problem of providers error - but it still looks like workaround...

Seems like https://github.com/gruntwork-io/terragrunt/issues/2542, https://github.com/gruntwork-io/terragrunt/issues/1212, and several other reports.

Resolved in v0.50.11 release.


Ethical Risks of Brain-Computer Interface Technology?

Ethics Committee refers to the committee composed of medical, pharmaceutical and other background personnel, whose responsibility is to independently review, agree, follow up review of the trial protocol and related documents, obtain and record the methods and materials used to obtain and record the informed consent of the subjects, so as to ensure that the rights and safety of the subjects are protected. The composition and all activities of the committee shall not be interfered or influenced by the clinical trial organization and the conducter. According to Chinese law, the ethics committee is subject to the management of the medical and health institutions where it is located and the supervision of the subjects. The National Health and Health Commission, the State Administration of Traditional Chinese Medicine and the local health and family planning administrative departments at or above the county level are responsible for the inspection, supervision or daily supervision of the ethics review work.(伦理委员会指由医学、药学及其他背景人员组成的委员会，其职责是通过独立地审查、同意、跟踪审查试验方案及相关文件、获得和记录受试者知情同意所用的方法和材料等，确保受试者的权益、安全受到保护。该委员会的组成和一切活动不应受临床试验组织和实施者的干扰或影响。根据中国法律规定，伦理委员会受所在医疗卫生机构的管理和受试者的监督，由国家卫生健康委员会、国家中医药管理局以及县级以上地方卫生计生行政部门负责对伦理审查工作的检查、督导或日常监督管理。)
BCI research on animals and humans, applications for scientific research projects and papers published must be strictly reviewed and approved by the Medical Ethics Committee.(无论是对动物和人类开展BCI 研究，还是申报科研项目和发表论文，都必须经医学伦理道德委员会严格审查和批准。)
The research and development personnel of brain-computer interface technology have the professional knowledge that ordinary people do not have, and directly participate in the research and development and promotion of brain-computer interface technology. Therefore, the research and development personnel of brain-computer interface technology have the unshirkable responsibility to avoid ethical risks. However, in practice, researchers of brain-computer interface technology often pay more attention to brain-computer interface technology itself and ignore the ethical risks of brain-computer interface technology.A survey of ethical norms and attitudes towards scientists working on human embryonic stem cell transplantation showed that most scientists were evasive and did not agree with the importance of ethical norms.The possible ethical risks in the application of brain-computer interface technology are as follows: security ethical risk, privacy ethical risk, fairness ethical risk, free will ethical risk, responsibility ethical risk, life ethical risk and ecological ethical risk.(脑机接口技术的研发人员具备常人所不具备的专业知识，并且直接参与脑机接口技术的研发和推广，因此，脑机接口技术的研发人员对于规避伦理风险负有不可推卸的责任。然而，在实际中，脑机接口技术的研发人员往往较为关注脑机接口技术本身而忽视了脑机接口技术的伦理风险。曾有一项关于针对从事人类胚胎干细胞移植研究的科学家的伦理规范和态度的调查，调查结果显示，大多数科学家对于伦理规范持回避态度，他们并不认同伦理规范的重要性。脑机接口技术在应用过程中可能出现的伦理风险如下：安全伦理风险、隐私伦理风险、公平伦理风险、自由意志伦理风险、责任伦理风险、生命伦理风险和生态伦理风险。)

相关文献名称：

《脑机接口隐私风险治理》


New Build APIs and changes in deploy API spec and additional features…

… in deploy API

@Nidhi251289 I've updated the .md files and left some comments on the .yaml files. Please let me know if you have any questions. After you make any required corrections in the spec files, let me know so I can merge the PR.

@ilholbea Great, thank you! I'll wait for the confirmation from @Nidhi251289.

Waiting for the go ahead to publish.


Graphlab algorithms

Tested implementations for all Graphalytics algorithms on the GraphLab Create Platform, except for the ForestFire Model.

Refer to this link for build results (access rights to CI server needed):
http://jenkins.tribler.org//job/Graphalytics_pull_request_tester/26/
Test PASSed.


How can we help?
I would like help so I can submit the manifest.
Please read and ensure the following

[X] The installer meets the above requirements

Please provide the following information
Download Page Url: https://www.arrl.org/tqsl-download
Publisher: TrustedQSL Developers & The American Radio Relay League (ARRL)
Package Name: TrustedQSL
Description: TrustedQSL is a tool which provides tools for digitally signing Amateur Radio QSO records.
Package Version: 2.6.5
Installer URL: https://www.arrl.org/files/file/LoTW Instructions/tqsl-2.6.5.msi
My only real question is what should I put for the license? It's a custom license (or at least one I've not seen before), which is available here.

D'oh! It's a modified BSD license. I should be able to handle this.

And PR submitted with #102359!


Edit Encode.decimal comment

Currently decimal is converted to string to preserve precision so the comment is not valid

Thank you :)


Add projectedfslib

This PR adds bindings to Projected File System.
I want to open a pull request to avoid duplicate works. I think most things should work. However there are a few structs are not passing the structs x64 test because of possible incorrect definition of anonymous unions.
I also want to spend some time replicating the official RegFS example with this API, so we can be confident that this binding works fine.

[x] Fix struct-x64 tests
[x] Replicate RegFS example

Alright, I've finished rewriting the RegFS example in Rust. It is available here: https://github.com/fanzeyi/prjfs-rs and it uses fairly amount of the API I added in this PR. It works!


Move flat constants from settings components and into zygoat-django

Related to #103 - see there for implementation recommendations.
Some things (like the security headers) are just going to be flat values that have no external dependencies on anything else in the settings file. My vote is that we make zygoat-django module called settings_constants (or something to that effect) and do an import * from there.

Handled by Kris


Implement config sharing to Twig layer

Needed for https://github.com/libero/pattern-library/pull/98.
https://github.com/libero/pattern-library/pull/98/files#diff-7bb6b4493ed851122cfb90d0e48aeb98R21 is the first occurrence of configuration, in this case the media statement breakpoint specified in
<source srcset="/images/download-full.svg" type="image/svg+xml" media="(min-width: 45.625em)">

that is shared between the sass and Twig layers.
Tasks

[ ] decide on a suitable data format to export to the Twig layer (documented to this ticket)
[ ] update ConfigDistributor.js to export new format to appropriate location for Twig to access
[ ] update config--libero-default.js to export to the templating layer
[ ] Update https://github.com/libero/pattern-library/pull/98/files#diff-7bb6b4493ed851122cfb90d0e48aeb98R21 to use the config-exported value

Thinking about it, the breakpoint is actually computed by Sass rather than being shared between Twig and Sass. I think this might be a suitable to consider moving the config to Sass, and output values that can be used by the other layers...


Move logic formulas from CpogPlugin to WorkcraftCore

CI is finally running.

The coverage drop is expected as big portion of code is moved to the core.


request to transfer java-loggertracer under opentracing-contrib umbrella

Hi,
I setup the project https://github.com/davidB/java-loggertracer, and would like to transfer it under opentracing-contrib umbrella.
Review and better name are welcome.

Hi @davidB,
I had a quick look at it, correct me if I am wrong. It does not depend on any specific logging framework e.g. slf4j reporter can be moved to a separate module (with dep on jackson).

@davidB thanks for donating this :)
I think java-loggertracer is a reasonable, self-descriptive name. Since repos can always be renamed, I decided to carpe diem and created https://github.com/opentracing-contrib/java-loggertracer/invitations for you.
Please @-mention myself and @pavolloffay on your initial PR.
To be clear, you are an admin on this new repo and can run your own show there in terms of when merges happen, etc. Though I would recommend getting real / meaningful reviews at first while the groundwork is being established.

@bhs ,
About initial PR (migration), it's easier (for me) to push from my local clone of https://github.com/davidB/java-loggertracer to the new remote repo, than to create a PR (in fact I don't know how to create a PR between 2 repos that have no fork relation. If you know a simple way to make it, tell me.
@pavolloffay ,
You're right since today, I introduce Reporter as abstraction to report to slf4j or other system (I'll probalbly provide a prometheus reporter). So each Reporter could be move to separated module, jar.
But as starting point, I prefer to include Reporter and define its dependency in scope provided (except for jackson). It's simpler for developpement and not more works for user.
Thanks

@bhs ,
I 'll fork the new repo, and push to my fork.

Ah, I trashed my local and remote repo/copy :-(


Another Fix for Checkpointing

It will be safer to only allow a single rank to remove the directory because there is a possibility of race condition

@fabianlim the PR description has an explanation of the change, but the commit message only says "bugfix". In the future, it would be great if you could include the same detail in the commit log, as well. Thanks!

@russellb got it! Sorry for any inconvenience caused!


Auto connect on Windows

It appears we can do this with netsh, but we may have to create a "profile". The documentation has a bunch of samples. Perhaps we should roll the connect functionality in with node-wifiscanner and create a node-wifi module?
netsh documentation

Bryce, I'm not sure I understand what's being requested here. Could you provide some more context please.

On macOS we can automatically connect to a Wi-Fi network, but we cannot on Windows right now. It is possible, but requires some research and testing. The links above are a starting point.

Thanks. related to #258.


Remove dead code from walproposer_utils.c

This code occupies space in walproposer_utils.c without providing any benefit for neon compute.

I don't have much context into this, but what changed that made this code obsolete?

Nothing has changed, that code was left after refactoring neon extension code out of postgres repo. This code was mostly copied from walsender.c and AFAIU the main idea was that in theory it will be used in the future. But right now I see that deleting it doesn't break anything, so it's better to remove unused parts.

I think the idea was to keep it similar to walsender.c, so that we can easily copy-paste future upstream changes to walsender.c to waproposer_utils.c, too. I agree that if we can rid of this much code, it's probably better to remove it even if it makes it look more different from walsender.c.


Question...

Just curious if you remember how you tested performance?

The testing was done client-side on a real device. There is a frame-time overlay mode available by using frameTime: true in the config object passed to the Particles constructor. You can see this in action here by clicking the "Toggle Frame-time Counter" in the top bar.
The stated benchmark of 1000 particles with real-time n-body gravity used this frame-time counter and was able to maintain 60fps (a combined physics + render latency of < 16.67ms) on a base-model 2015 13" MBP, though with more recent hardware, it should be fairly easy to exceed that particle count while maintaining 60fps.

The physics latency could stand to be substantially improved by implementing a tree-based approach like the Barnes-Hut algorithm, which should reduce the amortized complexity of the physics down from O(N^2) to O(NLogN). In some preliminary testing I've done, there is some overhead associated with using this data structure that reduced performance for small particle counts, but greatly improved performance in particle counts greater than about a hundred.

Beautiful, thanks! I might yonk that frame counter concept for some smart tv stuff I'm working on. You might find it interesting - I'll send the link once I'm done.


[-] Error: Could not find a backend to open C:\Users\user\AppData\Local\Temp\tmp5ueaib09.png`` with iomode ri`

Title shows the error message that is returned from the backend. It also gave a error that "Transperent" directory was not found in the back end?

Please be more descriptive, could you also provide some screenshots?

Please be more descriptive, could you also provide some screenshots?

Sorry did not reply instead commented. Still new to this. But ive provided screenshots of what i know in the comment.

pip install imageio[pyav] imageio[opencv]
Also, what is your Env file named, and what are the contents? (Censor the API Keys)

Hello, for me the error was raised at this point :
main.py :
final_video_path = generate_video(combined_video_path, tts_path, subtitles_path, n_threads or 2, subtitles_position, text_color or "#FFFF00")
This was calling generate_video in the video.py file.
In the generate_video function the error was in this line : subtitles = SubtitlesClip(subtitles_path, generator)
At this step it was calling ImageMagick and I think this interaction generated the error.
In my case in the .env file I had put the .exe file that I downloaded from the website it was someting like that :
`IMAGEMAGICK_BINARY="C:\Users\Toufik\Desktop\MoneyPrinter\ImageMagick-7.1.1-38-Q16-HDRI-x64-dll.exe"
I change it for the path of the .exe file that is generated after the installation of ImageMagick
Now in my .env I have something like that :
IMAGEMAGICK_BINARY="C:\Program Files\ImageMagick-7.1.1-Q16-HDRI\magick.exe"
This fixed the issue for me. If it can help anyone :)
`


Initial UI updates

UI updates, including removing unnecessary fields and adding new button images

Branch made obsolete by feat-scoreui

The few relevant image files have been pulled into feat-scoreui, deleting branch


docs-bug(mat-autocomplete): Incorrect tab title for optgroup example code

Documentation Feedback
Steps to Reproduce

Go to the Autocomplete optgroup Example.
Click the "View Code" button

Result
One of the tabs for viewing the code reads ./autocomplete-optgroup-example.html.

Affected documentation page
https://material.angular.io/components/autocomplete/examples#autocomplete-optgroup

@wagnermaciel
I think this problem is solved by this PR #24626.

Looks like the related PR was merged. Closing.


Link In/LinkOut Undo Not Working Correctly

Current Behavior
When performing an undo after changing link in/link out connections, the connections are not set correctly.
Expected Behavior
Undo should work correctly
Steps To Reproduce

Two or more Link Out nodes (labelled "Out1", "Out2", ...)

Only one Link In node (labelled "In")

Connect "Out1" to "In" and see that a dotted line connects them

Select each node in turn ensuring that all nodes show the correct connections

Open properties of "In"

Untick "Out1" and tick "Out2"

Select each node in turn ensuring that all nodes show the correct connections

Press CTRL+Z once to undo the above change

Select each node in turn show the wrong connections are shown

Open properties of "In"

Ticks are shown for both "Out1" and "Out2"

Selecting "Out1" also shows no connection

Example flow
[{"id":"3f13efa6cd3adaee","type":"link out","z":"ecce9a260798dab7","name":"1","mode":"link","links":[],"x":315,"y":320,"wires":[]},{"id":"a6e8b21a3e0d56d4","type":"link out","z":"ecce9a260798dab7","name":"2","mode":"link","links":[],"x":315,"y":360,"wires":[]},{"id":"2fd90e621d364265","type":"link in","z":"ecce9a260798dab7","name":"Output","links":[],"x":415,"y":340,"wires":[[]]}]

Environment

Node-RED version:  Docker - 3.1.9 (also affects 4.0.0-beta-3)
Node.js version: v18.20.2
npm version: 10.5.0
Platform/OS: Linux 6.1.0-18-amd64 x86_64
Browser: Firefox 123

Thanks for such a clear set of steps to reproduce this issue - that always makes our life easier.
Will investigate.


Ignore favourites when using "Reply All"

When using the "Reply All" feature, it includes users that favourited posts, even if they didn't actually participate in the conversation.

Simple check added for this. In v.31.02+


iOS The application is disabled

Issue Description
The LinkedIn login works fine on most devices (Android, iOS emulator), but on one iPhone X, the WebView displays the message The application is disabled. This is with the same config as the other apps.
Steps to Reproduce / Code Snippets
<LinkedInModal
                    ref={ref => {
                      this.modal = ref;
                    }}
                    renderButton={this.renderButtonLinked}
                    linkText={this.props.loginTitle}
                    clientID={this.props.clientId}
                    clientSecret={this.props.clientSecret}
                    redirectUri={this.props.clientUri}
                    onSuccess={this.onSuccess}
                    permissions={['r_basicprofile', 'r_emailaddress']}
                    onError={this.onError}
                    onOpen={() => this.setState({ visibleError: false })}
                  />

Expected Results
The app should receive the auth code.
Additional Information

Nodejs version: 8.12
React version: 16.6.1
React Native version: 0.57.5
Expo version: N/A
react-native-linkedin version: 1.3.1
Platform(s) (iOS, Android, or both?): iOS


[BUG] When using a user defined function that is both imported and using a variable in the imported file. PSRule fails with The variable named 'xxx was not defined in the template.

Existing rule
No response
Description of the issue
When using imported functions that manipulate variables that are not present in the file that imports the function. PSRule throws and error despite the compiled ARM template being valid
Error messages
The variable named '_1.array1' was not defined in the template.
Reproduction
main.bicep
import {getAllArrays} from 'module2.bicep'

output allArrays array = getAllArrays()

module2.bicep
@export()
var array1 = []

@export()
var array2 = [
  1
]

@export()
func getAllArrays() array => union(array1, array2)

Deploying the template succeeds to compile and run on Azure  outputting an array with a value of [1] but PSRule throws a validation error.
Version of PSRule
2.9.0
Version of PSRule for Azure
1.39.1
Additional context
No response

Thanks for reporting the issue @GABRIELNGBTUC


Microsoft.PowerShell.Commands.WriteErrorException,Import-NAVApplicationObject

Failing to import Test Toolkit from the Image itself.
Begun today, worked yesterday :)
Perhaps it's and image problem and not NAVContainerHelper issue...

Okay, this might be related to hyperV and security updates.
https://freddysblog.com/2020/02/26/the-world-after-february-18th/
https://freddysblog.com/2020/02/14/hyperv-isolation-to-the-rescue/

Love it when issues solve themselves:-)


calling makeAff callbacks more than once

I wrote some (arguably broken) code that goes like this here:
  waitForEvent client eventType =
    makeAff \_ success ->
      BareBones.addListener client eventType
        { fromArgumentsJS: const unit, action: success }

This is for an IRC client. I use this to make sure that the client doesn't attempt to send any messages until after it's connected to the server and joined a channel.
I call waitForEvent client "join", and this adds an event listener which fires every time anyone joins the room, so success gets called more than once. This means that the rest of the Aff action gets executed multiple times.
Is it my responsibility to ensure that the success callback only gets called once, or do you think Aff should protect against this?

I'd think it's probably working as intended if we're saying Aff is ErrorT (ContT Unit (Eff e) a - there's nothing that says a continuation can only be resumed once.

Yeah, I personally do not prefer this type of usage because it leads to a very imperative style of coding, but there's no particular reason to disallow it (and, anyway, it's possible in ContT, callCC, etc.).


Scanner no longer working

The solarman_scan worked before, but it has now stopped working.  Therefore it seems that there has been a software update to the solarman data loggers that makes the scanning function defect. It might be that it e.g no longer responds to "WIFIKIT-214028-READ".
The read and write to the ip of the data logger still works, but the scan can not find the IP. This shows that there is a data logger on the local network.
Anyone else having the same issue?

Hi @davidlekve,
Yes, the first firmware I know of that has this feature removed is MW3_SSL_5408_1.0B. The binary contains no trace of WIFIKIT-214028-READ or any similar string.

Just for information, is this the Module Version I have been having trouble with: LSW3_32U_5406_1.06
Thank you for reply @davidrapan. Do you know if there is a good way to solve this and get the ip for these data loggers?

Hmm that's weird, LSW3_32U_5406_1.06 is quite old and discovery works with this one (I have device with this version).

Does it respond to direct requests?
def test_logger_direct(local_ip: str, logger_ip: str):
    sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)

    sock.settimeout(1.0)
    request = "WIFIKIT-214028-READ"
    sock.bind((local_ip, 48899))
    address = (logger_ip, 48899)
    sock.sendto(request.encode(), address)

    try:
        data = sock.recv(1024)
        values = data.decode().split(",")
        print(values)
    except socket.timeout:
        pass

Hi @davidlekve,
Yes, the first firmware I know of that has this feature removed is MW3_SSL_5408_1.0B. The binary contains no trace of WIFIKIT-214028-READ or any similar string.
@davidrapan  do you have a copy or link to this firmware ?

Hey @davidlekve, I just remembered that it won't respond to the <IP_ADDRESS>. You have to send packet to the broadcast address of particular network e.g. <IP_ADDRESS> in <IP_ADDRESS>/24.
@githubDante I'm not at home rn I'll look when I get there.
😉

Does it respond to direct requests?
def test_logger_direct(local_ip: str, logger_ip: str):
    sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)

    sock.settimeout(1.0)
    request = "WIFIKIT-214028-READ"
    sock.bind((local_ip, 48899))
    address = (logger_ip, 48899)
    sock.sendto(request.encode(), address)

    try:
        data = sock.recv(1024)
        values = data.decode().split(",")
        print(values)
    except socket.timeout:
        pass

I work with @davidlekve. Thanks for the script. It does respond to direct request:
['WIFIKIT-214028-READ']

Hey @davidlekve, I just remembered that it won't respond to the <IP_ADDRESS>. You have to send packet to the broadcast address of particular network e.g. <IP_ADDRESS> in <IP_ADDRESS>/24.
@githubDante I'm not at home rn I'll look when I get there.
😉

We have done this and the broadcast address is set to the one of the network.

When running the scan script this block throws an exception:
data = sock.recv(1024)

is set to the one of the network.

You mean to the network to which the inverter belongs to, right?

is set to the one of the network.

You mean to the network to which the inverter belongs to, right?

Answering for @davidlekve here.
Yes. The inverter has the IP: <IP_ADDRESS>, so we use the broadcast address: <IP_ADDRESS>.

Yeah, just checking.
Then I'm out of ideas and you are proly stuck with probing whole range using unicast...

@davidlekve & @francinv, as #73 has been merged you can update with git pull and use the unciast scanner available in the utils/ directory.


stellar/horizon: Figure out difference from core in path payment ingestion

From the outage on 2023-07-27, Horizon is processing path payments differently from Core (somehow). We should figure out what the difference is and fix it so it doesn't happen again.
Possibilities from @sisuresh:

This was a pathPaymentStrictSend. Is it possible that horizon processes the trades dest->source instead of source->dest?<PHONE_NUMBER>400180200 +<PHONE_NUMBER>6599 (the xlm-silver math if you do the last trade first) overflows int64, but<PHONE_NUMBER>400180200 +<PHONE_NUMBER>6599 -<PHONE_NUMBER>9640  (the xlm-silver math if you do it in order) doesn't.
The effects also show the same reserve amounts for Silver on the first and last hop. Is that the reserve before the operation is applied?
Another guess related to the question above - maybe the intermediate reserve isn't accounted for after the xlm -> silver trade.

Related?


Elasticsearch source skeleton

@danlamanna
Can you QA this?  It should give you a good start.
Also nicks the corner of #134 .

:clap:

I wanted to do one more thing, I'm done now.

Ah memories :smile_cat: .

@mgrauer This looks great.
We agreed Elasticsearch as a source makes sense to have in core Minerva so others can use it. If it makes sense to you I'll implement a very rudimentary backend for minerva_elasticsearch_query and get this merged in.
This will require adding elasticsearch as a Minerva dependency, which is a pretty lightweight wrapper around urllib3.
Following that, I will create analyses specific to the Elasticsearch indices people using Terra will want.
Sound good?

This all sounds good to me.  I think it makes the most sense to add that additional endpoint to elasticsearch_source.py.
I think we said that endpoint will do something like

create a Job (async local or Romanesco)
create a Dataset, tie it into the Job (there was some discussion about adding it to the meta/minerva object in the Job, we'll have to figure out the exact specifics of this later)
return the Job from the endpoint
in the async Job, bring back the query result, save it as a JSON file in the Dataset
create GeoJson from the JSON, as a collection of lat/long points, save the GeoJson file to the Dataset
set the minerva metadata similar to this

And let me know if you have any better ideas or questions

My concern with putting that into master is that in general, Elasticsearch indices won't always contain geospatial information. I want to avoid putting anything into core that is specific to a particular domain, Memex HT data in this instance.
So if we create the general endpoint which just processes an ES query and puts the resulting JSON into a dataset, then the user can do whatever they want with it.
Then in Terra, I will create a specific analysis that takes that dataset and alters it using the code you've mentioned.

great, makes sense.

@mgrauer This is ready for review, let me know if the general approach makes sense and feel free to be as nitpicky as you'd like :)

I don't get the purpose of the elasticsearch dataset endpoint, it seems like it isn't used.  Can you remove it and the test?  Or else explain its use to me.
The way I see it, you have endpoints that do everything you need already, without this other endpoint

create an elasticsearch source
run a query job on an elasticsearch source

create a job
create a JSON dataset
the job runs the query on the source and uploads the result to the JSON dataset

I'll remove it, I originally added it to follow convention with the WMS endpoints.

Will you want to convert this to a romanesco job?  If so, please add an issue for that.

@mgrauer Updated. This look good to you?

LGTM.


Feature/wal 246 ION DID Provider

Implement ION DID Provider. Seeking initial feedback before rebasing to Veramo and opening a PR there.
Changes:

Remove old ION provider code
Do not depend on ion-tools
Do not depend on external POW SDK. An improved version is part of the code. We might extract that into a seperate lib at one point
Update and recovery keys, including key rotations
Full implementation of all Identifier methods

Known issues:

README is not update yet. Will do that before rebasing on Veramo develop
POW works on Node. Not tested yet on React-native. Out of scope for this implementation
Adding/Updating services/keys does not get propagated. Needs more investigation. MS gives back a 200 response for them, but it never ends up in the DID Document. Will look at that later.

Codecov Report

Merging #53 (ae7a75d) into develop (040014a) will increase coverage by 0.20%.
The diff coverage is 62.63%.

:exclamation: Current head ae7a75d differs from pull request most recent head 3d615ac. Consider uploading reports for the commit 3d615ac to get more accurate results

@@             Coverage Diff             @@
##           develop      #53      +/-   ##
===========================================
+ Coverage    62.73%   62.93%   +0.20%
===========================================
  Files           23       56      +33
  Lines          864     1878    +1014
  Branches       173      345     +172
===========================================
+ Hits           542     1182     +640
- Misses         322      696     +374

Impacted Files
Coverage Δ

...ages/bls-did-provider-key/src/BlsKeyDidProvider.ts
0.00% <0.00%> (ø)

...ages/bls-did-provider-key/src/BlsKeyDidResolver.ts
0.00% <0.00%> (ø)

.../connection-manager/src/agent/ConnectionManager.ts
0.00% <0.00%> (ø)

...ction-manager/src/store/AbstractConnectionStore.ts
0.00% <0.00%> (ø)

...on/src/migrations/internal-migrations-ormconfig.ts
0.00% <0.00%> (ø)

...kages/data-store/src/connection/ConnectionStore.ts
0.00% <0.00%> (ø)

...uth-siop-op-authenticator/src/session/OpSession.ts
5.30% <0.00%> (-1.01%)
:arrow_down:

...er/src/migrations/internal-migrations-ormconfig.ts
0.00% <0.00%> (ø)

packages/ms-request-api/src/agent/MsRequestApi.ts
0.00% <0.00%> (ø)

...ges/vc-handler-ld-local/src/ld-default-contexts.ts
100.00% <ø> (ø)

... and 32 more

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Index out of range on Web

Everything is working fine with me on iOS and Android but once I run my app on the web (Chrome) I got this error from the widget LocalizedApp
════════ Exception caught by widgets library ═══════════════════════════════════
The following IndexError was thrown building MyApp(dirty):
RangeError (index): Index out of range: no indices are valid: 0

The relevant error-causing widget was
MyApp
lib/main.dart:54
When the exception was thrown, this was the stack
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 236:49  throw_
dart-sdk/lib/_internal/js_dev_runtime/private/js_array.dart 581:7             _get]
packages/localize_and_translate/src/main.dart 192:51                          get locale
packages/UnitedPalestine/main.dart 85:28                                      build
packages/flutter/src/widgets/framework.dart 4569:28                           build
...

Any extra steps I need to do to make it works on the web?

No extra steps needed,
I can see the problem in MyApp class  not LocalizedApp
please share more details about implementation, issue and flutter doctor command
and test LocalizedApp with empty project to see if it has errors

Future<void> main() async {
  WidgetsFlutterBinding.ensureInitialized();
  //await Firebase.initializeApp();
  // ignore: unused_local_variable

    await translator.init(
      localeDefault: LocalizationDefaultType.device,
      languagesList: <String>['ar', 'en'],
      assetsDirectory: 'assets/language/',
      apiKeyGoogle: '<Key>',
    );
  }

  SystemChrome.setPreferredOrientations(
      [DeviceOrientation.portraitUp, DeviceOrientation.portraitDown]).then((_) {
    //runApp(MyApp());
    runApp(
      LocalizedApp(
        child: MyApp(),
      ),
    );
  });
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MultiProvider(
      providers: [
        Provider<AuthenticationService>(
          create: (_) => AuthenticationService(FirebaseAuth.instance),
        ),
        StreamProvider(
          create: (context) =>
              context.read<AuthenticationService>().authStateChanges,
        )
      ],
      child: MaterialApp(
        debugShowCheckedModeBanner: false,
        initialRoute: SplashScreen.routName,
        routes: {
          SplashScreen.routName: (ctx) => SplashScreen(),
          SigninScreen.routName: (ctx) => SigninScreen(),
          SignupScreen.routName: (ctx) => SignupScreen(),
          OTPScreen.routName: (ctx) => OTPScreen(),
        },
        localizationsDelegates: translator.delegates,
        locale: translator.locale,
        supportedLocales: translator.locals(),
      ),
    );
  }
}

did you try to start with empty widget screen like Container() to see if the error belongs to another code,
plus, is asset files exists !
We use this plugin in active projects right now, all cool.


Problems starting up

[code]
I'm sorry, but an uncaught exception occurred.
While running game code:
File "game/Submods/MAS Additions/FaceDetectionAndRecognition_Topics.rpy", line 1, in script
init 5 python:
File "game/Submods/MAS Additions/FaceDetectionAndRecognition_Topics.rpy", line 21, in
aff_range=(mas_aff.NORMAL, None)
File "game/definitions.rpy", line 745, in init
SyntaxError: invalid syntax (, line 1)
-- Full Traceback ------------------------------------------------------------
Full traceback:
File "game/Submods/MAS Additions/FaceDetectionAndRecognition_Topics.rpy", line 1, in script
init 5 python:
File "C:\Program Files (x86)\Doki Doki Literature Club\renpy\ast.py", line 814, in execute
renpy.python.py_exec_bytecode(self.code.bytecode, self.hide, store=self.store)
File "C:\Program Files (x86)\Doki Doki Literature Club\renpy\python.py", line 1719, in py_exec_bytecode
exec bytecode in globals, locals
File "game/Submods/MAS Additions/FaceDetectionAndRecognition_Topics.rpy", line 21, in
aff_range=(mas_aff.NORMAL, None)
File "game/definitions.rpy", line 745, in init
File "C:\Program Files (x86)\Doki Doki Literature Club\renpy\python.py", line 584, in py_compile
raise e
SyntaxError: invalid syntax (, line 1)
Windows-8-6.2.9200
Ren'Py <IP_ADDRESS>.2187
Monika After Story <IP_ADDRESS>-unstable.2<IP_ADDRESS>
[/code]

Seems to be same issue as #19
I'll need to check this on Monday, not certain what causes it.

Ah okay then, all the best to you man

Closing, related to another, now closed issue.


Migrate from node-sass to dart-sass

node-sass (which we use) is deprecated, and the recommended path is to migrate to dart-ass: https://sass-lang.com/dart-sass
This could also possibly address the vulnerabilities in node-sass 6.0.1: https://security.snyk.io/vuln/SNYK-JS-NODESASS-535500

node-sass (6.0.1) is quite the liability: https://app.snyk.io/test/npm/node-sass/6.0.1

Hi @0xJem I've made this migration in this pr -> https://github.com/OlympusDAO/olympus-frontend/pull/1248/


Generate internet shortcuts

That points to the pano world view, or pano itself, for example:
[InternetShortcut]
URL=https://maps.google.com/?q=-33.67614817925245,-69.01404288410123&ll=-33.67614817925245,-69.01404288410123&z=0

Put that in folder next to images, make it’s file name be <image_key>.url.
Ok, create one for earth view, one for street view and one for the user’s homepage (if not Google official).

Looks like this works if you have the panoid (assuming more precise than the lat/lon):
http://www.google.com/maps?layer=c&panoid=2xXom-TXErsz16MNt95ZPg

https://github.com/mhulse/internet-shortcut

They are now being generated with one bug unrelated to shortcut creation: #55


Set Licence expression on package

Summary
I wish for the nuget packages to have the licence expression property set correctly
Details
The licence expression property should be set to the correct licence type I.e. MIT as this will enable analysis of licences in use to occur in external tools & the license type will be shown in Nuget etc.

Thanks for raising this @thompson-tomo
Would you be willing to submit a PR for this? I assume what you mean is setting the PackageLicenseExpression in the csproj file. Yes?

@andrueastman sure I will go through submitting PR's in the coming days.

Here is some additional context on the nature of the change


Moved view title contains [Object object]

Have the flame chart visualizer installed and debug something JavaScript
Move the "Realtime Performance" view from the debug view into the Explorer view
Notice it's now the [Object object]: Realtime Performance view

I cannot reproduce (anymore?):

@connor4312 can you check?


On restoring, keep endpoints that are in not-ready state in cilium endpoint list

This happen when the bpf program gave an error while compiling and the endpoint stop showing up in the cilium endpoint list
I'm not sure since which version does this happen

@aanm has a repro locally, working on it.


Make curric filter sidebar fixed width

Description
Fixes the width of the curriculum sidebar
Issue(s)
Fixes CUR-1143
How to test

Go to https://deploy-preview-3060--oak-web-application.netlify.thenational.academy/teachers/curriculum/
Navigate to the curric sequences
Check width of the sidebar stays consistent

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


Sidecar watchdog in operator service

Description
This PR adds another job to the operator service, adding a "watchdog" that periodically checks all pods to make sure that the sidecar is present.
This should help fixing issues such as #4171 (the sidecar may not be present in pods if the entire cluster is restarted and apps' pods are restarted before the dapr-sidecar-injector service), as well as mitigate issues such as those we are experiencing in our E2E tests, where the injector service does not receive the admission webhook.
Issue reference
Fixes #4171
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

Looks like this is working and it is catching pods where the sidecar wasn't injected. From logs:
{"instance":"dapr-operator-5445c95fbd-bgdtw","level":"warning","msg":"Pod hellobluedapr-98869bdf7-lr5ff does not have the Dapr sidecar and will be deleted","scope":"dapr.operator","time":"2022-06-14T02:22:04.821961274Z","type":"log","ver":"edge"}
{"instance":"dapr-operator-5445c95fbd-bgdtw","level":"info","msg":"Deleted pod hellobluedapr-98869bdf7-lr5ff","scope":"dapr.operator","time":"2022-06-14T02:22:04.832526661Z","type":"log","ver":"edge"}

Just need to complete the PR now :)

/ok-to-test

Because  ok-to-test can't show the watchdog running in this PR, I've triggered it in a fork: https://github.com/ItalyPaleAle/dapr-ci-test/actions/runs/2505352950


Migration to null-safety

It would be awesome if this package was migrated to null-safety.

Do you accept Pull Requests for this?

If anyone is interested, here is a null-safe version of this package, using the Android v2 embedding: https://pub.dev/packages/app_group_directory


Does it make sense to have a cspack vso agent task

I use Octopus Deploy extensively and it's handling of Cloud Services deployments is a bit clunky (http://docs.octopusdeploy.com/display/OD/Azure+Cloud+Services), I basically need to package the Azure Cloud Services bits with cspack which are then rolled into a NuGet package and sent to the Octopus deploy server.
Since I now have a working custom NuGetPackage and NuGetPublish steps (this to the community here) and I'm thinking to create another custom step which runs right before these to create the package.
Does this sounds sensible, does anyone know if this has been done already and I've missed it ? Are the Azure deployment tools like cspack already on the VSO hosted agent or should I ship cspack with my code.

There is an octopus deploy task that you could use and I believe it takes care of running octopack to create the package.  Is that what you are looking for?

Chris, are you referring to https://github.com/OctopusDeploy/OctoTFS? If so, I can report that this definitely does not run Octopack for you - it's currently only for creating a release and optionally deploying it.

We don't plan on creating a cspack task.  You can however script it yourself


Fix the fragment instance on vue v1.0.26

Surround the template in a div to fix the 'fragment instance'

Fixed #10

Coverage remained the same at 100.0% when pulling 11b60ad7d5bfbfe44c42aa2866a9c930ed08008b on timfeid:master into 9e37230450d00ea0d47e2585b6a36a67d62f8efa on Haixing-Hu:master.

I created the dist files and also checked the final JavaScript file, the div tag was there, but the error didn't disappear. Not sure, maybe I did something wrong, but as long as the DIV tag is there I would assume it works assuming your PR works.

Interesting, for some reason I was able to get this working by just copying vue-html-editor.js to my local. Using require('vue-html-editor') fails, but using require('./vue-html-editor') works without the div there as well.

So, wrapping the template in a parent element doesn't work? Every piece of documentation points that it should.

@Haixing-Hu @timfeid
Is there any answer? I changed all the template:
"<textarea class='form-control' :name='name'></textarea>"
to
"
<textarea class='form-control'", :name='name'></textarea>
"
Or is it wrong?

Same here.
@Haixing-Hu It's very bad when you find something that should be cool and spend all day trying to make it work with no success...

As I mentioned earlier, I was only able to get this working by copying it to my local and requiring it that way.

Didn't work for me...
On 10 Oct 2016, at 23:23, Tim Feid <notifications<EMAIL_ADDRESS>wrote:
As I mentioned earlier, I was only able to get this working by copying it to my local and requiring it that way.

You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/Haixing-Hu/vue-html-editor/pull/12#issuecomment-252750020, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AINYzqnwLJb-PZOtVs7TjpPkToHwGKPoks5qyqzVgaJpZM4JsWND.


Can't authentificate mojang account

When i execute
picomc account authenticate<EMAIL_ADDRESS>it returns
AttributeError: 'OfflineAccount' object has no attribute 'authenticate'
after i input a password.
That's not a big issue but still needs a fix.
picomc, version 0.4.2
Python 3.8.6

This is a result of poor documentation, it's definitely on my list to improve that. You need to specify the email on account creation, not authentication. For example
picomc account create any_name<EMAIL_ADDRESS>
and the later just
picomc account authenticate any_name

The any_name acts just as an internal identifier, it need not match the email nor game username, that is retrieved from the API.
Please close this issue if solved. Thank you

I assume it works? Please comment if mis-closed.


fix(trace): check fn sigs for contract with fallbacks

Motivation
closes #9115

Solution

when decoding functions for contracts with fallback make sure the decoded function is in contract sigs, otherwise use fallback for trace

looks fine to me, thanks a lot for looking into this!


pull request for e2e test at 12/26/2016 15:45:15

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add OS type meta label to Azure SD

There is currently no way to differentiate Windows instances from Linux ones in Azure SD. This is needed when you have a mix of node_exporters / wmi_exporters for OS-level metrics and you want to have them in separate scrape jobs.
This change allows you to do just that. Example:
  - job_name: 'node'
    azure_sd_configs:
      - <azure_sd_config>
    relabel_configs:
      - source_labels: [__meta_azure_machine_os_type]
        regex: Linux
        action: keep

The way the vendor'd AzureSDK provides to get the OsType is a bit awkward - as far as I can tell, this information can only be gotten from the startup disk. Newer versions of the SDK appear to improve this a
bit (by having OS information in the InstanceView), but the current way still works in them.
As per MAINTAINERS.md, can either @brian-brazil or @fabxc review this please?

Thanks!


Added documentation to gp.py, input.py, and param.py

I added documentation to three files in this commit: gp.py, input.py, and param.py. Functionally, there are no changes to the code (the changes are only cosmetic. The code itself is identical).

If this PR does not overlap with PR #15 , We can simply rebase the last 3 commits against the current main branch and review this PR concurrently with PR #15 , rather than waiting for it to be merged. We have resolved all the delayed, conflicting PRs, so probably this is the last time we need rebasing.


Add type linting

i.e. pylint

Briefly looked into pylint yesterday - it seems like mypy is actually the appropriate solution instead https://mypy-lang.org/


Accessibility Review

Website URL
http://linkfree.eddiehub.io
GitHub Repo URL
http://github.com/EddieHubCommunity/LinkFree

Did you mean to post linkfree twice or would you like me to review something else?


Adding of custom view to alert

Hi!
First of all, thank you for that great library.
Please, tell me, how can I add custom view to alert such as UIProgressView and others?
When I adding my custom view as a subview to FCAlertView object it's added to alertBackground, but I want to add it to alert, below title and above buttons. How can I make this?
Thank you.

Hi @iamluckykim
Thank you so much for using FCAlertView.
At this point, adding extra UIView to the FCAlertView would not be supported and/or recommended.
This is to keep the alert simple and within the base guidelines. As an example, framing of different items could become an issue the more you could add to it. If anything changes in the future, however, I will let you know.
Thanks again!


Fix scheduled trigger to actually trigger in January and July

old:

Runs at 01:23, on day 1 of the month, every 6 months.

new:

Runs at 01:23, on day 1 of the month, only in January and July.

Explanation
https://chat.openai.com/c/50754ff2-7aa6-4477-8537-b46652ba3e11

unable to load conversation :(

User
what's wrong with this trigger?
on:
schedule:
# At 01:23 on 1st January and every 6 months afterward
- cron: '23 1 1 1/6 *'


Is there any way to setup column width in wiki?

https://learn.microsoft.com/en-gb/azure/devops/project/wiki/markdown-guidance?view=azure-devops#tables

This is the default width, we need to make the third one with longer width.

Document details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: fa622358-f5bb-1f5c-177a-081a37b6acef
Version Independent ID: 72f7fd16-a822-66c8-3a34-8905645ce5f2
Content: Markdown syntax for files, widgets, and wikis - Azure DevOps
Content Source: docs/project/wiki/markdown-guidance.md
Service: azure-devops
Sub-service: azure-devops-wiki
GitHub Login: @chcomley
Microsoft Alias: chcomley

And remove the scroll bar.

@fazhong-ms -- thank you for your question.  My research indicates that each browser decides the column width when rendering tables.
I am closing this issue now.  You are welcome to @ mention me for any followup.  We hope to hear from you again.


Started process of moving extranious information to Wiki

Should you link to wiki on things removed?

been in merge conflict, so I modified readme directly, and linked to your wiki posts.   Awesome job getting this started.


App closes after attempting to extract a file (1.4.4)

What version of the application did you download like "windows_x64" or "macos"? What file are you trying to extract?


tests: match request body

Request body must match recorded one in cassettes.

/azp run

/azp run


Get a new expression for each gear

Need to get a new rotation expression every time to ensure the rotation is referencing the proper gear. Alternatively if getting the expression is expensive, two expressions could be kept.
Fixes #214

@skendrot,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


Add issues badge

Codecov Report
Base: 100.00% // Head: 100.00% // No change to project coverage :thumbsup:

Coverage data is based on head (3279a9e) compared to base (3625a49).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #25   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            8         8
  Lines          129       129
  Branches        17        17
=========================================
  Hits           129       129

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


factory.close() keeps the java process hanging indefinitely

OrientDB Version: 3.0.22
Java Version: 11
OS: Ubuntu 20/Windows 10/MacOS
Expected behavior
factory.close() keeps the java process hanging indefinitely
Actual behavior
factory.close() to eventually end
Steps to reproduce

I just browse around my app therefore data will be written in db and when I close the app I have a shutdown hook that calls factory.close() this will trigger the above calls and the process hangs indefinitely.

Hi @florian-stoica-tlabs ,
I am sorry, but we perform tasks which you describe many times a day without any problems.
Could you send us the test to reproduce?

Hi @florian-stoica-tlabs,
We had in the past similar issues, but not related to the stack you are posting, can you try the latest hotfix of 3.0.x series (current 3.0.35)
Bye

No answer, closing the issue for now. In case, please comment on this very issue.


accessory out of compliance error

Hello,
The HomeKit app don't upgrade accessories and stuck also when remove and add all again.
with this JSON all works fine. When i try to add other PLC temperature sensor homekit application stuck and don't work.
{     "bridge": {         "name": "Homebridge 6990",         "username": "0E:A9:8F:4E:A6:1B",         "port": 51402,         "pin": "129-22-950",         "advertiser": "bonjour-hap"     },     "accessories": [],     "platforms": [         {             "name": "Config",             "port": 8581,             "platform": "config",             "lang": "it"         },         {             "ip": "<IP_ADDRESS>",             "rack": 0,             "slot": 1,             "communicationOP": false,             "enablePolling": true,             "distributePolling": true,             "accessories": [                 {                     "accessory": "PLC_Switch",                     "name": "Spegni tutto",                     "db": 15,                     "manufacturer": "Company",                     "enablePolling": true,                     "get_On": 0.2,                     "set_On": 0.2                 },                 {                     "accessory": "PLC_LightBulb",                     "name": "Corridoio",                     "db": 15,                     "manufacturer": "Company",                     "enablePolling": true,                     "get_On": 8.3,                     "set_On_Set": 5.7,                     "set_On_Reset": 6                 },                 {                     "accessory": "PLC_LightBulb",                     "name": "Binario living",                     "db": 15,                     "manufacturer": "Company",                     "enablePolling": true,                     "get_On": 6.4,                     "set_On_Set": 2.1,                     "set_On_Reset": 2.2                 },                 {                     "accessory": "PLC_LightBulb",                     "name": "Applique divano",                     "db": 15,                     "manufacturer": "Company",                     "enablePolling": true,                     "get_On": 6.5,                     "set_On_Set": 2.3,                     "set_On_Reset": 2.4                 },                 {                     "accessory": "PLC_LightBulb",                     "name": "Faretti ingresso",                     "db": 15,                     "manufacturer": "Company",                     "enablePolling": true,                     "get_On": 6.6,                     "set_On_Set": 2.5,                     "set_On_Reset": 2.6                 },                 {                     "accessory": "PLC_LightBulb",                     "name": "LED ingresso",                     "db": 15,                     "manufacturer": "Company",                     "enablePolling": true,                     "get_On": 6.7,                     "set_On_Set": 3,                     "set_On_Reset": 3.1                 },                 {                     "accessory": "PLC_LightBulb",                     "name": "Lampada tavolo",                     "db": 15,                     "manufacturer": "Company",                     "enablePolling": true,                     "get_On": 7.1,                     "set_On_Set": 3.3,                     "set_On_Reset": 3.4                 },                 {                     "accessory": "PLC_LightBulb",                     "name": "LED tavolo",                     "db": 15,                     "manufacturer": "Company",                     "enablePolling": true,                     "get_On": 7.6,                     "set_On_Set": 4.5,                     "set_On_Reset": 4.6                 },                 {                     "accessory": "PLC_LightBulb",                     "name": "Faretti living",                     "db": 15,                     "manufacturer": "Company",                     "enablePolling": true,                     "get_On": 7.7,                     "set_On_Set": 4.7,                     "set_On_Reset": 5                 },                 {                     "accessory": "PLC_LightBulb",                     "name": "Balcone cucina",                     "db": 15,                     "manufacturer": "Company",                     "enablePolling": true,                     "get_On": 8.1,                     "set_On_Set": 5.3,                     "set_On_Reset": 5.4                 },                 {                     "accessory": "PLC_LightBulb",                     "name": "LED sotto TV",                     "db": 15,                     "manufacturer": "Company",                     "enablePolling": true,                     "get_On": 8.2,                     "set_On_Set": 5.5,                     "set_On_Reset": 5.6                 },                 {                     "accessory": "PLC_LightBulb",                     "name": "Camera matrimoniale",                     "db": 15,                     "manufacturer": "Company",                     "enablePolling": true,                     "get_On": 7.4,                     "set_On_Set": 3.7,                     "set_On_Reset": 4                 },                 {                     "accessory": "PLC_LightBulb",                     "name": "TV camera matrimoniale",                     "db": 15,                     "manufacturer": "Company",                     "enablePolling": true,                     "get_On": 7.5,                     "set_On_Set": 4.1,                     "set_On_Reset": 4.2                 },                 {                     "accessory": "PLC_LightBulb",                     "name": "LED sotto cucina",                     "db": 15,                     "manufacturer": "Company",                     "enablePolling": true,                     "get_On": 70.2,                     "set_On_Set": 70,                     "set_On_Reset": 70.1                 },                 {                     "accessory": "PLC_TemperatureSensor",                     "name": "Esterna",                     "db": 15,                     "manufacturer": "Company",                     "enablePolling": true,                     "get_CurrentTemperature": 10                 }             ],             "platform": "PLC"         }     ] }
simply add other "PLC_TemperatureSensor" for stuck all.
There is a limitation on query on PLC? or limitation on homekit?
On "Accessory" on Homebridge i see temperature but on Homekit not. Whats i can do?
thanks

Hallo,
Can you describe a bit more what you mean with the home app stucks?
Does the state update when you close and reopen the home app?
Do you have an AppleTV as control center?
Are you sure that the temperature sensor is not showing up? As temperature sensors are only shown in home app when open the room.

Have you already enabled the "Debug mode" of homebridge in the error case and head a look at the log file?
If not please do so and send the log.

Hello,
if i add more than one temperature sensor HomekitApp stuck like in photo, but in homebridge i see all fine. (see photo)

From log i don't see problems.
log.txt

And i saw another problem. I used PLC garagedooropener feature, also in this case, i see in HomeBridge status without problem and on  Homekit is always in "updating"
for now i use only app on Iphone. I bought AppleTV yesterday, i'm waiting to receive it.
JSON is:
"accessory": "PLC_GarageDoorOpener",
"name": "Garage",
"db": 15,
"manufacturer": "Elmod",
"enablePolling": true,
"get_CurrentDoorState": 71,
"get_TargetDoorState": 8.4,
"set_TargetDoorState": 72
log garage.txt

I have first looked at the issue with the PLC_GarageDoorOpener:

I can reproduce the issue
It is related to your configuration
get_TargetDoorState has to be of type Byte therefore no Bit address like 8.4 is allowed.
please change e.g to "get_TargetDoorState": 73,

I will now look on the other issue.

For you issue with the temperature sensor I have could also not see an issue from the log file.
Having more temperature sensors is no is normal I have seven in my environment.
To be honest currently I have no glue what the issue could be therefore my questions and suggestions are just narrow down the issue.
The only thing I coud can see is that the two accessories are polled at the same time. Which is absolutely fine. For better traceability of the issue you could set the defaultPollInterval to a number > as the number of accessories you have defined.
[12/28/2024, 10:04:17 PM] [PLC] [LED ingresso] Execute polling...
[12/28/2024, 10:04:17 PM] [PLC] [Camera matrimoniale] Execute polling...
[12/28/2024, 10:04:17 PM] [PLC] [LED ingresso] get On: 0 (getBit DB15DBX6.7)
[12/28/2024, 10:04:17 PM] [PLC] [Camera matrimoniale] get CurrentTemperature: 19.899999618530273 (getReal DB15DBD26)

To exclude that long response times from your PLC are the issue I have done a new 2.0.7 release to log also the execution time of the PLC request. Could you please retest with this please?
When you remove the Temperature sensor form the json does it then work instantly again?
What is your setup?

In which environment is Homebrige executed
What PLC are you using

I have seen various issues with the Home app connecting to Homebridge when Homebridge MAC address was changed. In my case it was caused by getting a new MAC address when restarting the container.
Are you sure that you have always the same MAC address?

I have first looked at the issue with the PLC_GarageDoorOpener:

I can reproduce the issue
It is related to your configuration
get_TargetDoorState has to be of type Byte therefore no Bit address like 8.4 is allowed.
please change e.g to "get_TargetDoorState": 73,

I will now look on the other issue.

Ok, perfect. Now it work fine! Thank you!

For you issue with the temperature sensor I have could also not see an issue from the log file. Having more temperature sensors is no is normal I have seven in my environment.
To be honest currently I have no glue what the issue could be therefore my questions and suggestions are just narrow down the issue.
The only thing I coud can see is that the two accessories are polled at the same time. Which is absolutely fine. For better traceability of the issue you could set the defaultPollInterval to a number > as the number of accessories you have defined.
[12/28/2024, 10:04:17 PM] [PLC] [LED ingresso] Execute polling...
[12/28/2024, 10:04:17 PM] [PLC] [Camera matrimoniale] Execute polling...
[12/28/2024, 10:04:17 PM] [PLC] [LED ingresso] get On: 0 (getBit DB15DBX6.7)
[12/28/2024, 10:04:17 PM] [PLC] [Camera matrimoniale] get CurrentTemperature: 19.899999618530273 (getReal DB15DBD26)

To exclude that long response times from your PLC are the issue I have done a new 2.0.7 release to log also the execution time of the PLC request. Could you please retest with this please?
When you remove the Temperature sensor form the json does it then work instantly again?
What is your setup?

In which environment is Homebrige executed
What PLC are you using

I have seen various issues with the Home app connecting to Homebridge when Homebridge MAC address was changed. In my case it was caused by getting a new MAC address when restarting the container. Are you sure that you have always the same MAC address?

Hello,
I don't know why but now it works well. I just added one by one with plugin configuration and not directly in JSON configuration. By the way, i also add you log with new version of plugin.
Hardware is:

PLC S7-1200 CPU1214C
Raspberry PI 3 B+ (distro Diet-Pi)

Thank you too much for your help!
log v2.txt


Minor modifications to make compiling/using in Windows easier

First: Thanks for this plugin! Works flawlessly once I got it working.
However, as I'm not very familiar with Godot's plugin/GDNative/GDExtension/module-infrastructure it took me a while to get this working. Thought that maybe the results from my experiments could be useful to someone else so I made this PR. Feel free to reject.
Also made a "release", mostly to keep track of my experiments: https://github.com/GNSS-Stylist/Godot-FFB-SDL/releases/tag/Dev1
Original commit comment:
To successfully compile this in windows a lib-file needs first to be generated out of the dll. This adds bat-scripts to do this. Also modified README.md to mention this Windows-related complication.
Added also "ffbplugin.gdextension"-file.

Hey, thanks for the pull request! Glad you got it working.
However i have been using mingw to cross-compile the binaries for windows from linux and the changes to Sconstruct script will brake this. I wonder if we can check for what compiler is being used?
If so, I think it might be better to just grab the .lib file from the latest SDL2-devel-VC release from SDL2 Releases here on github than to have multiple batch scripts for extracting it.
If its not possible then id like to keep cross-compiling an option because i don't have windows installed.
I will dive deeper tomorrow and and review the changes then. I'll also take a look at how we can set/check the compiler in SConstruct script

Investigated this a bit and made a minor fix to SConstruct to allow compilation with MinGW under windows. Compilation goes through, but the resulting dll doesn't, however, seem to work. First Godot nags about missing dependencies when trying to use it:

Can't open dynamic library: C:/long_path/Godot-FFB-SDL-Extension/bin/libffbplugin.windows.template_debug.x86_64.dll. Missing dependencies: cygwin1.dll, cyggcc_s-seh-1.dll, cygstdc++-6.dll. Error: Error 126: The specified module could not be found..
core/extension/gdextension.cpp:455 - GDExtension dynamic library not found: C:/long_path/Godot-FFB-SDL-Extension/bin/libffbplugin.windows.template_debug.x86_64.dll

After adding C:\cygwin64\bin to path Godot nags about the dll itself missing, which sounds a bit misleading:

Can't open dynamic library: C:/long_path/Godot-FFB-SDL-Extension/bin/libffbplugin.windows.template_debug.x86_64.dll. Error: Error 126: The specified module could not be found..

Not sure what's going on here, but will happily continue using the working dll compiled with VC.
Grabbing the lib-file from SDL2-releases also work, thanks for the tip!

Made some commits and now the plugin compiles with VC without complications. Also updated the SDL2.dll to latest stable V2.30.2 (because why not if downloading the corresponding .lib-file anyway). Tested with Win 10 and Logitech Driving Force GT.


This module is now a hybrid ESM/CommonJS package that works under node or webpack

Followed by this one


kvrocks2redis test keep failing in ArchLinux CI

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
unstable
Minimal reproduce step
https://github.com/apache/kvrocks/actions/runs/11145141492/job/31005011435
What did you expect to see?

What did you see instead?

Anything Else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

AssertionError: Data mismatch for key 'set_key_0': source data: '['set_value_0_1', 'set_value_0_2', 'set_value_0_3']' destination data: '['set_value_0_3', 'set_value_0_2', 'set_value_0_1']'

I think it is possible that a behavior change in a new version of Redis caused this reordering.


Navigation Bar Height on Some Screens

Navigation bar height is not enough on register/login pages.
Device: iPhone XR.
OS: 12.4
Xcode: 11.3.1 (11C504)

Will be handled in #3067.


its_container block os detection

So if I attempt to use dockerspec using docker compose with serverspec os detection:
describe docker_compose(compose_yml) do
  its_container(:mysql) do
    if os[:family] == 'redhat'
       describe ...
    end
  end
end

This results in the following error gems/specinfra-2.64.0/lib/specinfra/helper/os.rb:30:in 'detect_os': Specinfra failed os detection. (NotImplementedError). Digging a bit deeper, this is because when specinfra attempts to obtain uname via Specinfra.backend.run_command('uname -m') the docker_compose backend is missing information on which container to execute the command.
Looking at the docker_compose backend, the container settings comes from get_config(:docker_compose_container).to_s, the only problem is I'm not sure how to restore this context in  rspec/resources/its_container.rb so the Specinfra.backend.run_command method runs successfully. Any hints or suggestions on how to fix this?
p.s.
If I set the :docker_compose_container, os[:family] works:
set :docker_compose_container, :mysql

os[:family]

but I'm hoping to get it working in the its_container block so this works with any container.

@nanliu sorry for my delayed answer and thank you for all your information. I'm going to try to search for a way to implement it correctly. But, as you have already seen, it is not an easy task.

@zuazo, thanks for looking into this. I will take another crack at this issue as well.
I recently presented a talk for Portland Docker user group regarding how to use dockerspec in a container.
This project received lots positive feedback, and people were really interested in trying it out. I found the source code of the project to be very well documented, but most people attending wasn't aware of Ruby API docs, so maybe worth including a link in the README to: http://www.rubydoc.info/github/zuazo/dockerspec/Dockerspec

@nanliu thank you, man :beer: I don't know what to say. I'm glad to know that this little hack can be useful to others :smiley: I can add a link to your presentation in the README if you want.
As for the documentation, the first badge in the README points to the documentation of the released gem:

Your link (http://www.rubydoc.info/github/zuazo/dockerspec/Dockerspec) is for the master branch documentation.
But if you think the link to the documentation might be clearer in another way, or should we write it down elsewhere, feel free to send a PR. I will accept it with open arms. Maybe we should link both the released and master documentation at the beginning of README?
FYI: Whatever progress I make on the OS detection subject, I will write it here.

Hi @nanliu:
Sorry for the delay in my answer. Following your comments and recommendations:

I fixed OS detection in 8046c8a787a5a8a6a0185be41c107478c41b4472 and d76e2503946bd4f828e8ad911c9679db066a0be7.
I have added both released and unreleased documentation to the README.
I also have added a link to your presentation.

Thanks for all your help!

Thanks for fixing this!

Released in 0.4.0.


Ignoring of files within folder exclusion

https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/file-matching-patterns?view=azure-devops
Hi, I have the below:
API/web.connections.config
API/web.config
API/thing.txt
Web/app.js
Web/bundle.js
I want to delete (match) everything except:
API/web.connections.config
Web/app.js
So in this case the below would be deleted:
API/web.config
API/thing.txt
Web/bundle.js
I have tried to below pattern matches:
**
!API/web.connections.config
!Web/app.js
--------------
API/**
!API/web.connections.config
Web/**
!Web/app.js
--------------
API/*
!API/web.connections.config
Web/*
!Web/app.js
--------------
API/*
!API/*.connections.config
Web/*
!Web/*app.js
--------------
API/*
API/!*.connections.config
Web/*
Web/!*app.js

Every single one of these examples matches on everything and deletes them all. Would you be able to document the correct way of doing something such as the above? It would help me greatly.
Thanks

Thanks for your question. It looks like you're working through an issue with your scenario or implementation, rather than an issue with the documentation. Here are a couple of options where you might consider asking your question:

Azure DevOps on Stack Overflow
Azure DevOps Support Bot


count summary

Can we add a total # of count for campaigns and users next to section header e.g. Campaigns (6)?
This way, it won't change the current layout and I can get the summary at the same time.

Done @ https://github.com/mobilizingcs/classes/commit/513d380166794123e6f6d43944fe61d35920ba2d

Wait did you mean in the campaign list overview, or the edit campaign page?


feat(frontend): Improve models input UI/UX in settings

What is the problem that this fixes or functionality that this introduces? Does it fix any open issues?
The models input dumps all the raw LiteLLM IDs that cause slight performance issues and overwhelm the user with options.

Give a summary of what the PR does, explaining any non-trivial design decisions
Default behaviour
This PR breaks down the input into a Provider input and Models input. Given the provider, a filtered models list will be available for the user to choose.

Changed default LLM_MODEL to openai/gpt-4o from gpt-4o

The user can see the "Verified" providers and models that we recommend and know work well with OpenHands.

utils/verified-models.ts
export const VERIFIED_PROVIDERS = ["openai", "azure", "anthropic"];
export const VERIFIED_MODELS = ["gpt-4o", "claude-3-5-sonnet-20240620-v1:0"];

If preferred, the user can set a custom LLM model.

New settings were added, CUSTOM_LLM_MODEL and USING_CUSTOM_LLM. That way, the socket class sends the appropriate LLM with the LLM_MODEL key if settings.USING_CUSTOM_LLM is true.

Tests

~85 - 90%+ test coverage

Notes

Need to confirm which are the verified providers and models we want to set and display to the user.
Need to confirm that the new way of setting custom LLM models is OK
Since LiteLLM does not maintain consistency between supported models (some are not returned at all and just say they support it by append some-provider/), most are dumped in an other provider. Need to confirm if it is OK, which ones do we want to "pull out", and if there are alternative ways to handle this (TBH considering going to the LiteLLM repo and making the changes for consistency myself)

TODO

[x] Add a switch to allow the user to switch between LiteLLM models and a custom model
[ ] Investigate providers that offer custom models
[x] Input validation
[x] Set verified models and providers
[x] Bug fixes

Accidentally removed #3514 after re-forking

@neubig Could confirm the verified providers and models we want to display?

export const VERIFIED_PROVIDERS = ["openai", "azure", "anthropic"];
export const VERIFIED_MODELS = ["gpt-4o", "claude-3-5-sonnet-20240620-v1:0"];

Is OpenRouter still selectable as provider?

@tobitege Yes, looks like we do:

The thing I can't be certain is if all the models OpenRouter offers through LiteLLM are under this provider. It could be the case that there are additional models LiteLLM does NOT list/return, or they do but without the provider (e.g., some-model instead of openrouter/some-model). In those cases, I will need to do a little hardcoding stuff as I did for OpenAI

@tobitege Yes, looks like we do:

Thanks! Yes, OpenRouter could add new models any day, but usually litellm is usually pretty fast in adding support for new ones.
I'd not restrict any selection a user may do with OpenRouter, it'll either work or not, to be blunt. 😬

I'd not restrict any selection a user may do with OpenRouter, it'll either work or not, to be blunt.
Yes I'm trying not to restrict anything here. Actually the thing that this PR does remove is the ability to input a custom model given a provider (e.g., openrouter/some-random-model-maybe-not-in-docs). Do you think this is OK? I can't see the reasons why the user would want to do such a thing in the first place

I'd not restrict any selection a user may do with OpenRouter, it'll either work or not, to be blunt.

Yes I'm trying not to restrict anything here. Actually the thing that this PR does remove is the ability to input a custom model given a provider (e.g., openrouter/some-random-model-maybe-not-in-docs). Do you think this is OK? I can't see the reasons why the user would want to do such a thing in the first place

I think it'd be ok. The typing in the box always felt wonky anyways.

I'd not restrict any selection a user may do with OpenRouter, it'll either work or not, to be blunt.

Yes I'm trying not to restrict anything here. Actually the thing that this PR does remove is the ability to input a custom model given a provider (e.g., openrouter/some-random-model-maybe-not-in-docs). Do you think this is OK? I can't see the reasons why the user would want to do such a thing in the first place

@amanape There is this tricky thing where liteLLM interprets the model names like "openai/something" as a hint to route the completion call to an openai-compatible endpoint, which they build according to base_url or provider-specific url, and ending with /v1, in other words they build some API URL which they know accepts messages in OpenAI format, because the user added "openai" prefix. (In that case it also makes sure that the parameters are in the right format, I think)
I don't know if that has relevance for openrouter. I know our users needed it in some cases, like CommandR and/or Cohere where the prefix worked, its missing did not.
My point is that typing in the box was necessary to add /openai to some prefixes. Maybe it's fine if it's still possible via custom model, though.
Sorry for typing in a closed issue, just a quick thought and I'll take it these days elsewhere for further thinking/testing.


core/exchange: Syncing slowly against core node

It has been observed on robusta-3 that syncing for a bridge nodes slows significantly and it seems the cause is the size of the data being requested since robusta-3 is filled to 256 square width on every block.

closing as stale


[TEST] Update travis testing

Codecov Report

Merging #31 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #31   +/-   ##
=======================================
  Coverage   98.42%   98.42%
=======================================
  Files          14       14
  Lines         634      634
=======================================
  Hits          624      624
  Misses         10       10

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 39cb746...73a7fdb. Read the comment docs.

Pull Request Test Coverage Report for Build 168

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.423%

Totals

Change from base Build 162:
0.0%

Covered Lines:
624

Relevant Lines:
634

💛  - Coveralls

Pull Request Test Coverage Report for Build 168

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.423%

Totals

Change from base Build 162:
0.0%

Covered Lines:
624

Relevant Lines:
634

💛  - Coveralls


Query Regarding Room Usage in Audio/Video Calling Application

Specifically, we are debating between two strategies for room usage:

Creating a new room every time a call is initiated.
Using a static room code that remains consistent for each user.

We would greatly appreciate your insights and recommendations on which approach would be best suited for our application. Your expertise in this area would be invaluable to us as we aim to provide the best user experience possible.

hey @kherajanid
I hope you can resolve the query now.


Enforce Support for UTF-8 Encoding Scheme in Digest Authentication as per RFC 7616

This commit enforces the use of the 'UTF-8' encoding scheme as the sole allowed value for character encoding in Digest Authentication, in alignment with the guidelines specified in RFC 7616.

@arturobernalg We have been providing an option to override US-ASCII as the standard HTTP message char-set for decades, which is by far a greater deviation from the standard protocol. I see no reason why we could not have that option for user name / password in the standard auth schemes. But so be it.


Add Documentation: Algorithm Optimization Techniquesscroll to up butt…

Have written document as in .md file in which i have defined techniques such as Dynamic Programming optimizations, Bit Manipulation Tricks, or Space Optimization Techniques that can help improve the efficiency of the algorithms.
Hey @ajay-dhangar please approve my PR

have made requested changes please review the changes

@MastanSayyad kindly look as documentation changes shall come under Level 1

@NEGRAH-S Yes

@ajay-dhangar , Change this to Level 1 And see if any other have same cahnges make them level 1 as well


add mi308 fp16|fp8 mixtral8x(7B,22B)TP=1,2,4,8

Add MI308X fp16|fp8 mixtral8x(7B,22B) config files

Thank you for this. This PR offers the following:

Update num_stages from 0 to 2 in the tuning script and in default value if configs are not found. (These changes got skipped in my previous PRs)
mi308 has 2 names. This PR adds the config files for the 2nd name. Hence, now the branch can be used on any of the mi308 machines ( AMD_Instinct_MI300X_OAM && AMD_Instinct_MI308X_OAM)


POC Implement Angular and JSPM on Styleguide 2.0

@davegomez news?

Not yet @caiovaccaro, gonna work on it this week but before I have some questions to ask ;-)


Passing a function that produces React.Element or React.ReactNode errors on 5.7.2

🔎 Search Terms
ts57, children, ReactNode, JSX.Element
🕗 Version & Regression Information

This changed between versions 5.6.3 and 5.7.2

⏯ Playground Link
https://www.typescriptlang.org/play/?ts=5.7.2#code/JYWwDg9gTgLgBAJQKYEMDG8BmUIjgIilQ3wChS0IA7AZ3gEEww4BeOACgEpWA+OAb1Jw4RGAFcoVDkOFwAPD35de8gCbAAbjwASwOQHp1WgL4GeMzqWPkgA
💻 Code
import React from "react"

const App = () => {
  return (
    <>{() =>
Hi
}</>
  )
}

🙁 Actual behavior
Type '{ children: () => Element; }' is not assignable to type '{ children?: ReactNode; }'.
  Types of property 'children' are incompatible.
    Type '() => React.JSX.Element' is not assignable to type 'ReactNode'.

🙂 Expected behavior
No errors
Additional information about the issue
I also checked @types/react, but didn't find relevant changes.

It turned out that 5.7.2 errors properly, while 5.6.2 was silent while React warns with the following:
Warning: Functions are not valid as a React child. This may happen if you return a Component instead of <Component /> from render. Or maybe you meant to call this function rather than return it.
    at Foo
    at App


sdk/state: don't allow a non-native closing agreement to cause an escrow account to exceed its asset limit

we should store the channel asset limit either on the "open" object (this ticket). Or possibly store on the channel balance. Once stored then validate new payments against it
blocked by merge of: https://github.com/stellar/experimental-payment-channels/pull/78

I think we should store it on the second option you mention, the channel balance, because it will be possible to change the asset limit over time.

I changed the title of this issue because its less about the channel having an asset limit, but the escrow account that is the destination of the payment and its limit.

currently there's an issue that a a user could validate a payment doesn't surpass the escrow account assetLimit, but then the other party sends an amount to the escrow account that maxes out the asset limit. Which would cause the payment to fail.
This would be fixed with the separated disbursement ticket though: https://github.com/stellar/experimental-payment-channels/issues/80
at least, the payment could fail but the channel wont be stuck open (and the malicious actor would only hurt themselves)

I think we can disregard this issue because of #147 and also because of #146.
Please reopen if you disagree.


sssd: fix race condition in test

Description of changes
Fixes a race condition that causes the test to fail sometimes, as seen in https://github.com/NixOS/nixpkgs/pull/195026

Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Per CONTRIBUTING.md the commit messages should start with nixos/sssd:.

My bad. Because this came from a PR related to the package, I wasn't sure what the prefix should be.