1) Virus in binaries 2) can not be built from source on Windows 11

[MaksymKravchuk]

1. Virus in binaries
   Using VirusTotal – 2 malware detections.
2. Cannot be built from source on Windows 11
   Install a fresh Windows 11 on a virtual machine, install the latest "Microsoft Visual C++ Redistributable" (MSVC 170), and download the latest Bazel executables, run "bazel build --config windows --compilation_mode=opt --copt=/GL //cdc_rsync"

WARNING: Target pattern parsing failed.
ERROR: Skipping '//cdc_rsync': error loading package 'cdc_rsync': Unable to find package for @@[unknown repo 'rules_cc' requested from @@]//cc:defs.bzl: The repository '@@[unknown repo 'rules_cc' requested from @@]' could not be resolved: No repository visible as '@rules_cc' from main repository. Was the repository introduced in WORKSPACE? The WORKSPACE file is disabled by default in Bazel 8 (late 2024) and will be removed in Bazel 9 (late 2025), please migrate to Bzlmod. See https://bazel.build/external/migration.
ERROR: error loading package 'cdc_rsync': Unable to find package for @@[unknown repo 'rules_cc' requested from @@]//cc:defs.bzl: The repository '@@[unknown repo 'rules_cc' requested from @@]' could not be resolved: No repository visible as '@rules_cc' from main repository. Was the repository introduced in WORKSPACE? The WORKSPACE file is disabled by default in Bazel 8 (late 2024) and will be removed in Bazel 9 (late 2025), please migrate to Bzlmod. See https://bazel.build/external/migration.
INFO: Elapsed time: 14.047s
INFO: 0 processes.
ERROR: Build did NOT complete successfully

PS: tried 5 versions of bazel from 2022 to today, same problems

[ljusten]

Thanks for the report! 1. The binaries were built from source ~2 years ago with github actions, so unless some dependency was faulty, I can't imagine how something could have snug in. However, my theory is the deployment process of the server piece: It's copied to the server and ran through ssh. That's working as intended, but of course from the perspective of a virus scanner it's pretty fishy. What we should rather do is run the server in some daemon mode (which doesn't exist yet) and then the client can just connect to it. 2. Yeah according to the last development build, nightly builds broke sometime in June 2023. Unfortunately, I don't have a Windows machine with Visual Studio anymore, so I can't fix it, so what I'm going to do is archiving the repo. - Lutz

…

On Thu, Feb 13, 2025 at 11:10 AM Maksym Kravchuk ***@***.***> wrote: 1. Virus in binaries Using VirusTotal – 2 malware detections. 2. Cannot be built from source on Windows 11 Install a fresh Windows 11 on a virtual machine, install the latest "Microsoft Visual C++ Redistributable" (MSVC 170), and download the latest Bazel executables, run "bazel build --config windows --compilation_mode=opt --copt=/GL //cdc_rsync" WARNING: Target pattern parsing failed. ERROR: Skipping '//cdc_rsync': error loading package 'cdc_rsync': Unable to find package for @@[unknown repo 'rules_cc' requested from @@]//cc:defs.bzl: The repository '@@[unknown repo 'rules_cc' requested from @@]' could not be resolved: No repository visible as ***@***.***_cc' from main repository. Was the repository introduced in WORKSPACE? The WORKSPACE file is disabled by default in Bazel 8 (late 2024) and will be removed in Bazel 9 (late 2025), please migrate to Bzlmod. See https://bazel.build/external/migration. ERROR: error loading package 'cdc_rsync': Unable to find package for @@[unknown repo 'rules_cc' requested from @@]//cc:defs.bzl: The repository '@@[unknown repo 'rules_cc' requested from @@]' could not be resolved: No repository visible as ***@***.***_cc' from main repository. Was the repository introduced in WORKSPACE? The WORKSPACE file is disabled by default in Bazel 8 (late 2024) and will be removed in Bazel 9 (late 2025), please migrate to Bzlmod. See https://bazel.build/external/migration. INFO: Elapsed time: 14.047s INFO: 0 processes. ERROR: Build did NOT complete successfully image.png (view on web) <https://github.com/user-attachments/assets/4570f0da-60d3-49b3-839c-1d26d17031bb> PS: tried 5 versions of bazel from 2022 to today, same problems — Reply to this email directly, view it on GitHub <#108>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEBQFMAN2HEUFTQSIBLJ2ID2PRVRRAVCNFSM6AAAAABXBYTZVCVHI2DSMVQWIX3LMV43ASLTON2WKOZSHA2TANJXGU2DKNY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- Dr. Lutz Justen Software Engineer ***@***.*** Google Germany GmbH ABC-Str. 19 <https://maps.google.com/?q=ABC-Str.+19+20354+Hamburg&entry=gmail&source=g> 20354 Hamburg <https://maps.google.com/?q=ABC-Str.+19+20354+Hamburg&entry=gmail&source=g> Google Germany GmbH | ABC-Str. 19 | 20354 Hamburg Geschäftsführer: Paul Terence Manicle, Liana Sebastian | Registergericht und -nummer: Hamburg, HRB 86891 Diese E-Mail ist vertraulich. Wenn Sie nicht der richtige Adressat sind, leiten Sie diese bitte nicht weiter, informieren Sie den Absender und löschen Sie die E-Mail und alle Anhänge. Vielen Dank. This e-mail is confidential. If you are not the right addressee please do not forward it, please inform the sender, and please erase this e-mail including any attachments. Thanks. Der Inhalt dieser E-Mail spiegelt den derzeitigen Stand der Verhandlungen wider und dient als Basis für weitere Gespräche. Er soll keine rechtlich verbindliche Verpflichtung begründen. Eine solche Verpflichtung wird allein durch einen zwischen allen beteiligten Parteien abgeschlossenen, schriftlichen Vertrag geschaffen. The above terms reflect a potential business arrangement, are provided solely as a basis for further discussion, and are not intended to be and do not constitute a legally binding obligation. No legally binding obligations will be created, implied, or inferred until an agreement in final form is executed in writing by all parties involved.