Upgrade 3.0: Visual Studio - develop for Windows (the doctor check crashed)

After upgrade to 3.0 "flutter doctor" shows the following message:
_[☠] Visual Studio - develop for Windows (the doctor check crashed)
Steps to Reproduce

flutter upgrade

Logs

    X Exception: Bad UTF-8 encoding (U+FFFD; REPLACEMENT CHARACTER) found while decoding string: [
        {
          "instanceId": "74aee65d",
          "installDate": "2022-05-04T16:02:20Z",
          "installationName": "VisualStudio/17.2.0+32505.173",
          "installationPath": "C:\\Program Files\\Microsoft Visual Studio\\2022\\Community",
          "installationVersion": "17.2.32505.173",
          "productId": "Microsoft.VisualStudio.Product.Community",
          "productPath": "C:\\Program Files\\Microsoft Visual Studio\\2022\\Community\\Common7\\IDE\\devenv.exe",
          "state":<PHONE_NUMBER>,
          "isComplete": true,
          "isLaunchable": true,
          "isPrerelease": false,
          "isRebootRequired": false,
          "displayName": "Visual Studio Community 2022",
          "description": "��魠� ��⥣�஢����� �।� ࠧࠡ�⪨, ��ᯫ�⭠� ��� ��㤥�⮢, ���⭨��� �஥�⮢ � ������ ����� � �⤥���� ���짮��⥫��.",
          "channelId": "VisualStudio.17.Release",
          "channelUri": "https://aka.ms/vs/17/release/channel",
          "enginePath": "C:\\Program Files (x86)\\Microsoft Visual
          Studio\\Installer\\resources\\app\\ServiceHub\\Services\\Microsoft.VisualStudio.Setup.Service",
          "installedChannelUri": "https://aka.ms/vs/17/release/channel",
          "releaseNotes": "https://docs.microsoft.com/en-us/visualstudio/releases/2022/release-notes-v17.2#17.2.0",
          "thirdPartyNotices": "https://go.microsoft.com/fwlink/?LinkId=661288",
          "updateDate": "2022-05-11T20:31:48.4180195Z",
          "catalog": {
            "buildBranch": "d17.2",
            "buildVersion": "17.2.32505.173",
            "id": "VisualStudio/17.2.0+32505.173",
            "localBuild": "build-lab",
            "manifestName": "VisualStudio",
            "manifestType": "installer",
            "productDisplayVersion": "17.2.0",
            "productLine": "Dev17",
            "productLineVersion": "2022",
            "productMilestone": "RTW",
            "productMilestoneIsPreRelease": "False",
            "productName": "Visual Studio",
            "productPatchVersion": "0",
            "productPreReleaseMilestoneSuffix": "7.0",
            "productSemanticVersion": "17.2.0+32505.173",
            "requiredEngineVersion": "3.2.2146.50370"
          },
          "properties": {
            "campaignId": "318320405.1550076964",
            "channelManifestId": "VisualStudio.17.Release/17.2.0+32505.173",
            "nickname": "",
            "setupEngineFilePath": "C:\\Program Files (x86)\\Microsoft Visual Studio\\Installer\\setup.exe"
          }
        }
      ]
      .


terrascan: init at 1.2.0

Motivation for this change
Detect compliance and security violations across Infrastructure as Code to
mitigate risk before provisioning cloud native infrastructure. It contains
500+ polices and support for Terraform and Kubernetes.
https://github.com/accurics/terrascan
Related to #81418
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 107752 run on x86_64-linux 1

1 package built:

terrascan

Result of nixpkgs-review pr 107752 run on x86_64-linux 1

1 package built:

terrascan

Result of nixpkgs-review pr 107752 run on x86_64-darwin 1

You removed the entry from top level. You wan't to add that back.

You removed the entry from top level. You wan't to add that back.

The removal was accidentally.

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 107752 run on x86_64-linux 1

1 package built:

terrascan

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 107752 run on x86_64-linux 1

1 package built:

terrascan

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 107752 run on x86_64-darwin 1

1 package built:

terrascan

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 107752 run on x86_64-darwin 1

1 package built:

terrascan


[Evaluated] Issues in test_foreach

🐛 Describe the bug
# AssertionError: RuntimeError not raised
"test_0dim_tensor_overload_exception_xpu",
# RuntimeError: ceil is not supported for complex inputs
"test_autodiff__foreach_ceil_inplace_xpu_complex128",
"test_autodiff__foreach_ceil_outplace_xpu_complex128",
# RuntimeError: floor is not supported for complex inputs
"test_autodiff__foreach_floor_inplace_xpu_complex128",
"test_autodiff__foreach_floor_outplace_xpu_complex128",
# RuntimeError: trunc is not supported for complex inputs
"test_autodiff__foreach_trunc_inplace_xpu_complex128",
"test_autodiff__foreach_trunc_outplace_xpu_complex128",
# RuntimeError: "min_elementwise_xpu" not implemented for 'ComplexDouble'
"test_autodiff__foreach_clamp_max_inplace_xpu_complex128",
"test_autodiff__foreach_clamp_max_outplace_xpu_complex128",
"test_autodiff__foreach_minimum_inplace_xpu_complex128",
"test_autodiff__foreach_minimum_outplace_xpu_complex128",
# RuntimeError: "max_elementwise_xpu" not implemented for 'ComplexDouble'
"test_autodiff__foreach_clamp_min_inplace_xpu_complex128",
"test_autodiff__foreach_clamp_min_outplace_xpu_complex128",
"test_autodiff__foreach_maximum_inplace_xpu_complex128",
"test_autodiff__foreach_maximum_outplace_xpu_complex128",
# RuntimeError: "erf_xpu" not implemented for 'ComplexDouble'
"test_autodiff__foreach_erf_inplace_xpu_complex128",  # erf
"test_autodiff__foreach_erf_outplace_xpu_complex128",
# RuntimeError: "erfc_xpu" not implemented for 'ComplexDouble'
"test_autodiff__foreach_erfc_inplace_xpu_complex128",  # erfc
"test_autodiff__foreach_erfc_outplace_xpu_complex128",
# RuntimeError: "frac_cpu" not implemented for 'ComplexDouble'
"test_autodiff__foreach_frac_inplace_xpu_complex128",
"test_autodiff__foreach_frac_outplace_xpu_complex128",
# RuntimeError: "lgamma_vml_cpu" not implemented for 'ComplexDouble'
"test_autodiff__foreach_lgamma_inplace_xpu_complex128",
"test_autodiff__foreach_lgamma_outplace_xpu_complex128",
# RuntimeError: "round_vml_cpu" not implemented for 'ComplexDouble'
"test_autodiff__foreach_round_inplace_xpu_complex128",
"test_autodiff__foreach_round_outplace_xpu_complex128",
# RuntimeError: Unlike NumPy, torch.sign is not intended to support complex numbers. Please use torch.sgn instead.
"test_autodiff__foreach_sign_inplace_xpu_complex128",
"test_autodiff__foreach_sign_outplace_xpu_complex128",
# RuntimeError: Tried to instantiate dummy base class CUDAGraph
"test_big_num_tensors__foreach_max_use_cuda_graph_True_xpu_float32",
"test_big_num_tensors__foreach_max_use_cuda_graph_True_xpu_float64",
"test_big_num_tensors__foreach_norm_use_cuda_graph_True_xpu_float32",
"test_big_num_tensors__foreach_norm_use_cuda_graph_True_xpu_float64",
# RuntimeError: linalg.vector_norm: Expected a floating point or complex tensor as input. Got Bool/Short/Int/Long/Char/Byte
"test_foreach_reduce_large_input__foreach_norm_xpu_bool",
"test_foreach_reduce_large_input__foreach_norm_xpu_int16",
"test_foreach_reduce_large_input__foreach_norm_xpu_int32",
"test_foreach_reduce_large_input__foreach_norm_xpu_int64",
"test_foreach_reduce_large_input__foreach_norm_xpu_int8",
"test_foreach_reduce_large_input__foreach_norm_xpu_uint8",
# AssertionError: Tensor-likes are not close!
"test_pointwise_op_with_tensor_of_scalarlist_overload__foreach_addcdiv_is_fastpath_True_xpu_float16",
# RuntimeError: Negation, the `-` operator, on a bool tensor is not supported. If you are trying to invert a mask, use the `~` or `logical_not()` operator instead.
"test_unary_op_tensors_on_different_devices__foreach_neg_xpu_bool",

Versions
Collecting environment information...
PyTorch version: N/A
Is debug build: N/A
CUDA used to build PyTorch: N/A
ROCM used to build PyTorch: N/A
OS: Ubuntu 22.04.3 LTS (x86_64)
GCC version: (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang version: 14.0.0-1ubuntu1.1
CMake version: version 3.22.1
Libc version: glibc-2.35
Python version: 3.9.19 (main, Mar 21 2024, 17:11:28) [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-5.15.0-106-generic-x86_64-with-glibc2.35
Is CUDA available: N/A
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: Could not collect
Nvidia driver version: Could not collect
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: N/A
CPU:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 52 bits physical, 57 bits virtual
Byte Order: Little Endian
CPU(s): 224
On-line CPU(s) list: 0-223
Vendor ID: GenuineIntel
Model name: Intel(R) Xeon(R) Platinum 8480+
CPU family: 6
Model: 143
Thread(s) per core: 2
Core(s) per socket: 56
Socket(s): 2
Stepping: 8
CPU max MHz: 3800.0000
CPU min MHz: 800.0000
BogoMIPS: 4000.00
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cat_l2 cdp_l3 invpcid_single intel_ppin cdp_l2 ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb intel_pt avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local split_lock_detect avx_vnni avx512_bf16 wbnoinvd dtherm ida arat pln pts hwp hwp_act_window hwp_epp hwp_pkg_req avx512vbmi umip pku ospke waitpkg avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg tme avx512_vpopcntdq la57 rdpid bus_lock_detect cldemote movdiri movdir64b enqcmd fsrm md_clear serialize tsxldtrk pconfig arch_lbr amx_bf16 avx512_fp16 amx_tile amx_int8 flush_l1d arch_capabilities
Virtualization: VT-x
L1d cache: 5.3 MiB (112 instances)
L1i cache: 3.5 MiB (112 instances)
L2 cache: 224 MiB (112 instances)
L3 cache: 210 MiB (2 instances)
NUMA node(s): 2
NUMA node0 CPU(s): 0-55,112-167
NUMA node1 CPU(s): 56-111,168-223
Vulnerability Gather data sampling: Not affected
Vulnerability Itlb multihit: Not affected
Vulnerability L1tf: Not affected
Vulnerability Mds: Not affected
Vulnerability Meltdown: Not affected
Vulnerability Mmio stale data: Not affected
Vulnerability Retbleed: Not affected
Vulnerability Spec rstack overflow: Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2: Mitigation; Enhanced IBRS; IBPB conditional; RSB filling; PBRSB-eIBRS SW sequence; BHI BHI_DIS_S
Vulnerability Srbds: Not affected
Vulnerability Tsx async abort: Not affected
Versions of relevant libraries:
[pip3] intel-extension-for-pytorch==2.1.30+git9e27c62
[pip3] numpy==1.26.4
[pip3] torch==2.4.0a0+gitff98731
[conda] intel-extension-for-pytorch 2.1.30+git9e27c62 dev_0
[conda] numpy 1.26.4 pypi_0 pypi
[conda] torch 2.4.0a0+gitff98731 pypi_0 pypi

`
RuntimeError: ceil is not supported for complex inputs
"test_autodiff__foreach_ceil_inplace_xpu_complex128",
"test_autodiff__foreach_ceil_outplace_xpu_complex128",
RuntimeError: floor is not supported for complex inputs
"test_autodiff__foreach_floor_inplace_xpu_complex128",
"test_autodiff__foreach_floor_outplace_xpu_complex128",
RuntimeError: trunc is not supported for complex inputs
"test_autodiff__foreach_trunc_inplace_xpu_complex128",
"test_autodiff__foreach_trunc_outplace_xpu_complex128",
RuntimeError: "min_elementwise_xpu" not implemented for 'ComplexDouble'
"test_autodiff__foreach_clamp_max_inplace_xpu_complex128",
"test_autodiff__foreach_clamp_max_outplace_xpu_complex128",
"test_autodiff__foreach_minimum_inplace_xpu_complex128",
"test_autodiff__foreach_minimum_outplace_xpu_complex128",
RuntimeError: "max_elementwise_xpu" not implemented for 'ComplexDouble'
"test_autodiff__foreach_clamp_min_inplace_xpu_complex128",
"test_autodiff__foreach_clamp_min_outplace_xpu_complex128",
"test_autodiff__foreach_maximum_inplace_xpu_complex128",
"test_autodiff__foreach_maximum_outplace_xpu_complex128",
RuntimeError: "erf_xpu" not implemented for 'ComplexDouble'
"test_autodiff__foreach_erf_inplace_xpu_complex128",  # erf
"test_autodiff__foreach_erf_outplace_xpu_complex128",
RuntimeError: "erfc_xpu" not implemented for 'ComplexDouble'
"test_autodiff__foreach_erfc_inplace_xpu_complex128",  # erfc
"test_autodiff__foreach_erfc_outplace_xpu_complex128",
RuntimeError: "frac_cpu" not implemented for 'ComplexDouble'
"test_autodiff__foreach_frac_inplace_xpu_complex128",
"test_autodiff__foreach_frac_outplace_xpu_complex128",
RuntimeError: "lgamma_vml_cpu" not implemented for 'ComplexDouble'
"test_autodiff__foreach_lgamma_inplace_xpu_complex128",
"test_autodiff__foreach_lgamma_outplace_xpu_complex128",
RuntimeError: "round_vml_cpu" not implemented for 'ComplexDouble'
"test_autodiff__foreach_round_inplace_xpu_complex128",
"test_autodiff__foreach_round_outplace_xpu_complex128",
RuntimeError: Unlike NumPy, torch.sign is not intended to support complex numbers. Please use torch.sgn instead.
"test_autodiff__foreach_sign_inplace_xpu_complex128",
"test_autodiff__foreach_sign_outplace_xpu_complex128",
RuntimeError: Negation, the - operator, on a bool tensor is not supported. If you are trying to invert a mask, use the ~ or logical_not() operator instead.
"test_unary_op_tensors_on_different_devices__foreach_neg_xpu_bool",
`
passed now

closed and new issue is https://github.com/intel/torch-xpu-ops/issues/583


Refine and pick off the first meaningful chunk of  Show oracle details and proofs in markets & market list

Story
As a trader interested in new markets
I want evidence of the market oracle's reputation
So I can decide if it is trustworthy
Acceptance Criteria

[ ] I can find oracle details and proofs for each market
[ ] I can independently verify those proofs
[ ] It is very obvious to me when a market has been flagged as malicious
[ ] Some of this information / status is also available on the market list (not just in market details)

Tasks

[ ] Break this down into tickets for component parts
[ ] Identify dependencies outside the team and create tickets for them
[ ] Decide which to do this sprint and update tasks accordingly
[ ] Visual design

[ ] Short oracle profile
[ ] Long oracle profile
[ ] Console: Market list
[ ] Any other touchpoints defined above

[ ] Implement
[ ] QA

Sketch

Miro exploration

Additional details / background info

Dependent on https://github.com/vegaprotocol/ux-and-visual-design/issues/79, see that ticket for background and design specs
The oracle profile will also be shown in proposals on the token site, so ideally the same components should be used for consistency – see https://github.com/vegaprotocol/frontend-monorepo/issues/2087

Thoughts on how we could break this down:

The smallest thing:

Move the oracle section up to be the third item in the market info tab
Add a link to the oracle spec file (if it exists) on GitHub

Implement the profile stub in the market info tab, to pull in the most crucial bits of info
Implement warning banner on markets, to draw attention to dastardly behaviour
Implement the full profile (in the modal)
Implement oracle status in market lists

Note visual design is not included in this list, as that has to happen before point 2 regardless, and all of these bits should be designed at once so they are complementary.

Matt and I met and agreed there are some subtasks. In ticket 1 above we'll need to make the library to seek and parse the files from GitHub. In each subsequent stage we'll need to add functionality to that library.
Neil to make these into tickets (tag Matt particularly in item 1).

Please see attached the proposed designs for the Oracle in the INFO tab and the various statuses it can have.

Each status has a colour + icon
We've defined some rules around how links display ie. ideally the proofs fit on one line but if the links are too long then stack them. In Console we only show the top two proofs.

Figma link here ↳
It might be useful for context to see the proposed Oracle Detail Pages and compare what info is exposed in the Console Accordion vs what is exposed when you (in future) are able to click to view details.
These designs are in the Governance Figma: Figma link


Added timeout variable in base actor

Codecov Report

Merging #517 into release-2.0.0 will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             release-2.0.0     #517   +/-   ##
================================================
  Coverage            38.87%   38.87%
  Complexity             759      759
================================================
  Files                  111      111
  Lines                 7778     7778
  Branches               881      881
================================================
  Hits                  3024     3024
  Misses                4423     4423
  Partials               331      331

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 2504a72...b1b8762. Read the comment docs.


Mobject is_off_screen method doesn't work

Description of bug / unexpected behavior

I have objects which are clearly off screen but calling obj.is_off_screen() returns False. Looking at the source code, I think the problem is a conceptual bug:
    def is_off_screen(self):
        if self.get_left()[0] > FRAME_X_RADIUS:
            return True
        if self.get_right()[0] < -FRAME_X_RADIUS:
            return True
        if self.get_bottom()[1] > FRAME_Y_RADIUS:
            return True
        if self.get_top()[1] < -FRAME_Y_RADIUS:
            return True
        return False

The conditions in the left/bottom tests should be swapped with those for right/top, respectively, because get_left() and get_bottom() return negative numbers.
    def is_off_screen(self):
        if self.get_left()[0] < -FRAME_X_RADIUS:
            return True
        if self.get_right()[0] > FRAME_X_RADIUS:
            return True
        if self.get_bottom()[1] < -FRAME_Y_RADIUS:
            return True
        if self.get_top()[1] > FRAME_Y_RADIUS:
            return True
        return False

Or they should just be replaced with absolute value tests. I hope I'm not missing anything...

I'm not sure I see a problem with the current implementation. An mobject is declared to be off screen, if its left border is past the right end of the frame, or if its right border is past the left end of the frame; or if its upper border is past the lower end of the screen; or if its lower border is past the upper end of the frame.
Your suggestion, on the other hand, would return True as soon as any part of the mobjects bounding box is outside of the frame.
Can you give some more details about your situation and why you think the implementation is incorrect?

Seems like I misunderstood the intent of this method. I was assuming it should return True if any part of the object is off screen. This is a useful thing to know, since it can be used for things like adaptive scaling in case your object gets too big and doesn't fit inside the screen. The way it's currently implemented, it will only return True if no part of the object is visible.

I think it would make sense to have another method which checks whether a mobject is fully contained in the screen (maybe is_fully_on_screen?) which can be used for purposes like this.
(In addition, the current is_off_screen method should also be better documented.)
Something like that would be a good feature for a first contribution, in case you are interested. :-)

Yeah, your suggestion makes sense. I'm going to try to make some time for it soon (haven't done any PRs on Github yet and need to figure out the procedure). Thanks for your suggestion (and the clarification on the original issue)!

By the way, do you think it would be too dirty if we parameterize this method, instead of creating a new one?

Yeah, your suggestion makes sense. I'm going to try to make some time for it soon (haven't done any PRs on Github yet and need to figure out the procedure). Thanks for your suggestion (and the clarification on the original issue)!

Sounds good. In case you need any support, feel free to use this issue -- or simply ask in one of the text channels for development on our Discord.

By the way, do you think it would be too dirty if we parameterize this method, instead of creating a new one?

That could also be a valid approach, sure. I guess it is less a question of actual implementation, but more of proper documentation.


Pact Consumer 4.0.0-beta.3 generating numberValue as object instead of primitive

When building the consumer pact file with 4.0.0-beta.3, using the LambdaDSL, I noticed that it converts NumberValue to a Object with a value attribute containing the number expected instead of just expecting the number itself.
Expected Value:
{     "number": 1 }
Actual Value:
{    "number":  {        "value":  1    } }
The code block I am referring to is the following:
LambdaDsl.newJsonBody(o -> o.numberValue("number", 1)).build()
This belongs to the pact-jvm-consumer-java8 artifact. This was not the case in 4.0.0-beta.2, and was working as expected.
If this is an expected behaviour going forward, would it be possible to add another method in the LambdaDSL package to support such a case.

I am unable to replicate this. The following code passes when run against the current master.
        DslPart dslPart = LambdaDsl.newJsonBody(o -> o.numberValue("number", 1)).build();
        assertThat(dslPart.getBody().toString(), is("{\"number\":1}"));

With 4.0.0-beta, when the map returned from Interaction.toMap() is serialized the type is a Number. The default gson serialization of Number is { "value":  }. This can be addressed using registerTypeHierarchyAdapter(Number.class, ...) to provide custom serialization.

4.0.0-beta.5 has been released

Thank you 👍


Refactor Patient Visits to use react query

🚀 Feature Proposal
Refactor patient visit code to use react query instead of redux
Add 3 hooks

usePatientVisits
useAddVisit
useVisit

Refactor code that currently accesses visits through the patient stored in the redux store to now use this code
Motivation
Remove redux
Technical Notes

look diagnoses and imaging requests for code that links to visits
use allergies code as inspiration
remove unused redux code when finished

Hi @jackcmeyer. I would love to take a look at this. Could you please assign this to me?

@Tomastomaslol  Sure! Thanks for volunteering!


nohup: initial implementation

review comments:

use atty crate for isatty
do not use nix crate.  it is too "fat".   libc crate is OK.

Roger that. I'll take care of it on Monday.


introduce semantic version specific updates to run with update management command

COMBINE_VERSION is added in version v0.4 to combine.settings, which introduces the possiblity of comparing versions, and acting on those version changes when the management command update is invoked.
For example, proposed that in the changes fromv0.3.3 --> v0.4, the job_details['transformation'] structure changed for Transform Jobs changes to support multiple transformations for a single Job.  This is a great improvement, but comes at the cost of changing the loosely defined data model of job_details, namely that it was only ever concerned with a single, possible Transformation Scenario.  This has effects for front-end display, exporting/importing, and most importantly, re-running in Spark, if different versions are encountered.
But with versions, particularly if these version specific commands are run in a particular order, it can be deduced that a Combine instance without COMBINE_VERSION, or one that is less than v0.4, needs to have the job_details updated (the single Transform merely becomes the first of a list of length one).
The packaging library provides means to compare semantic version strings, which is perfect here, e.g.:
In [1]: from packaging import version

In [2]: version.parse(settings.COMBINE_VERSION)
Out[2]: <Version('0.3.3')>

In [3]: version.parse(settings.COMBINE_VERSION) > version.parse('v0.5')
Out[3]: False

In [4]: version.parse(settings.COMBINE_VERSION) < version.parse('v0.5')
Out[4]: True

This is undoubtedly an established pattern, and feels quite a bit like ordered db migrations, so work will be to see where these version comparison specific snippets are stored.  They are permanent, so perhaps in management folder?

Scaffolding will be present in v0.4, under new VersionUpdateHelper class in update.py management command.
Preliminary example is updating all < v0.4 Transform Jobs to multiple transformations job_details.
Closing.


APIDoc POC

The following is a reference example of how can we employ a swagger schema to serve it as a documentation. For now only local build supported.
New patch.go script was added to address several problems in current protoc-gen-swagger generation:

Wraps responses with appropriate "success" code
Breaks down the recursive definitions (many-to-many)
Adds documentation to a collection operators
Treats atlas.rpc.identifier differently

Requirements:
protoc-gen-swagger : https://github.com/askurydzin/grpc-gateway/tree/primitive-types-mimics/protoc-gen-swagger -- patched to break recursive protoc messages definitions via oneof.
atlas-app-toolkit with swagger changes
As result we will be able to browse API Documentation on a localhost:8080/apidoc

patch.go script was incorporated into https://github.com/infobloxopen/grpc-gateway. so now you can check manually how it will work running ./bin/server and open localhost:8080/apidoc


cosign attest requires --predicate to be passed explicitly

From Slack:
@anderssonw writes:

https://github.com/sigstore/cosign/blob/17cc13812d8a7bfbb068ffc10fdbbdb3a9416f11/cmd/cosign/cli/attest/attest.go#L135
Is this working as intended? It seems an empty predicate path returns the following error:
Error: signing ghcr.io/ORG/IMAGE@sha256:DIGEST: open : no such file or directory
main.go:74: error during command execution: signing ghcr.io/ORG/IMAGE@sha256:DIGEST: open : no such file or directory

This is running a keyless attest, btw:
cosign attest --identity-token $IDENTITY_TOKEN ghcr.io/ORG/IMAGE@sha256:DIGEST

piping like this: echo 'foo' | cosign attest --identity-token $IDENTITY_TOKEN ghcr.io/ORG/IMAGE@sha256:DIGEST
does not change the error
if a predicate file is required, why is it not a required flag?
if i explicitly set --predicate - using stdin worked fine

@mattmoor:

I was looking at this code the other day and iirc the absence of the flag causes it to use os.Stdin, so not sure why the behavior doesn’t change without a bit of digging
I wonder if there is a bad default value
The default should probably be - in that case
The flags are mostly defined in an options package, so I’d check for attest options there

The default should probably be - in that case

I believe this is the right fix.
A couple of caveats:

If the default value is -, then not providing standard input redirection causes the command to halt with this message:     Using payload from: standard input. We can probably detect when interactive mode is being used to provide a meaningful error message. Similar to https://github.com/sigstore/cosign/blob/83c08ce4f35116da7c74350a67d5740ca5e28ca5/cmd/cosign/cli/fulcio/fulcio.go#L148-L149
When using the syntax echo 'foo' | cosign attest ..., either --yes or --no-upload must also be provided. Otherwise, the error user declined the prompt is raised. This is probably ok.

Alternatively, we could mark the flag as required (must not be an empty string) and let the user decide which behavior better suits their needs. This actually seems like the least surprising option.


cannot give retention policy duration in nanoseconds

Since we support retention policies specified in all other InfluxDB units (u, ms, s, m, h, d, w) we might as well support nanos, too.
> create retention policy foo on mydb duration<PHONE_NUMBER>u replication 1
> create retention policy bar on mydb duration<PHONE_NUMBER>000n replication 1
ERR: error parsing query: found<PHONE_NUMBER>000, expected duration at line 1, char 46

> show retention policies mydb
name	duration	replicaN	default
default	0		1		true
foo	1h0m0s		1		false

Supporting a retention policy under microseconds makes no sense.  I'm not sure why we even support anything other than seconds for an retention policy.  I'm assuming that by happy accident the parser can parse this.  I think the real fix is to:

[ ] Support n as a duration and let it parse
[ ] Error out with some type of minimum duration if you try to create a retention policy with a duration less than a minute or something like that.

@corylanou It does error out if you provide a duration less than 1 hour, thus the<PHONE_NUMBER> microseconds I specified in the example.


Warn users when a non-setup DLL is loaded and matches a setup DLL

On Windows, we run a LibFuzzer -help=1 check with loader snaps enabled, to help debug missing DLLs.
Another failure mode is that the user has shipped a targeted DLL in the setup container, but a different DLL with the same name gets loaded from a higher-priority location, instead. Detect this, and log a user-facing warning to help future debugging.
Note that this could be built on top of #2736. If we retain the entire loader snap transcript, we can parse all dynamically-linked DLL resolutions, and consequently diff against an enumeration of DLLs in the setup container.
AB#42916675

test comment

The support that we've added for .local files mitigates this somewhat. We will now always prefer loading DLLs from the executable directory rather than elsewhere.


Fix client traceback formatting, pep8, dont use bare except

There was an issue with the formatting of tracebacks in the client. It was not showing the formatted remote traceback, only the local traceback and a brief description of the traceback.
I also found a few pep8 violations and the use of bare except.

I had made a bunch of changes to simplerpc so I just incorporated your changes in that commit.  I did change the name of the server_forever method to start to better match the symantics of our eventloop.  Thanks for these contributions!.  Would you mind testing things again before we merge?

Sure thing, I'll be happy to test it again since I'm planning to port some code I wrote for xmlrpclib to this.

Great, let us know if you find anything else.
On Sun, Feb 26, 2012 at 8:36 AM, Dan Colish
<EMAIL_ADDRESS>wrote:

Sure thing, I'll be happy to test it again since I'm planning to port some code I wrote for xmlrpclib to this.

Reply to this email directly or view it on GitHub:
https://github.com/zeromq/pyzmq/pull/183#issuecomment-4182397

--
Brian E. Granger
Cal Poly State University, San Luis Obispo
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>


UN-451 - Performance Metrics - Backend tracking requirements update - content group

Related ticket(s):
https://national-archives.atlassian.net/browse/UN-451
About these changes
Changed "insights" to "articles" in the basepage.py GTM_CONTENT_GROUPS variable.
How to check these changes
Go to /stories on your local host, open the console and enter dataLayer. This will then show the GTM variables being passed from the back-end. Ensure that contentGroup1 says "Articles". Check this on an article page as well, not just the index page.
Before assigning to reviewer, please make sure you have

[x] Checked things thoroughly before handing over to reviewer.
[x] Checked PR title starts with ticket number as per project conventions to help us keep track of changes.
[x] Ensured that PR includes only commits relevant to the ticket.
[x] Waited for all CI jobs to pass before requesting a review.
[x] Added/updated tests and documentation where relevant.

For Reviewer

Before merging PR
main branch :
  - check PR merge tile begins with `release/<major.minor.patch>:<default/custom description>`
  - check PR merge tile begins with ticket number Ex `DF-XXX: Ticket name / short description`
  - select `Create a merge commit`

develop branch:
  - check if merges into base branch are `not to be kept On Hold` and then proceed.
  - check PR merge tile begins with ticket number Ex `DF-XXX: Ticket name / short description`
  - select `Squash and merge`

For Reviewer/Developer

After merging PR:

check and arrange to deploy on platform-sh.
update status on JIRA ticket on deployment.
update slack on deployment progress of the JIRA ticket once deployed.

Hi @ababic, I've made this PR but Elise and Helen are going to have a chat about what the value in contentGroup1 should be - I personally think it should be "Articles" but Elise mentioned that Helen said it should be "Stories from the collection". I think just "Stories" will do. I'm away until 08/02, but I'm happy for it to be whatever Elise and Helen think.


Check issued-at timestamp is failing

The lua-resty-openidc plugin is failing for us on simple requests. The problem is likely caused by differences in time synch and/or latency between our Ping server and our app servers running on AWS & Verizon clouds.
We're seeing the following message in our logs:
2015/09/29 19:30:56 [error] 18972#0: *4 [lua] openidc.lua:90: openidc_validate_id_token(): token is not valid yet: id_token.iat=1443554983, os.time()=1443555056, client: <client_ip>, server: , request: "GET /redirect_uri?state=&code= HTTP/1.1", host: "<server_ip:port>"
Increasing the value in the script to 1000 fixes the problem for us. Is there a reason for the hard-coded 10ms value in the script?  Is it reasonable to increase that value or to parameterize it so that implementations can override in config files?

Yes, a configurable value makes sense. Do notice that the time is in seconds so you've now set the "slack" interval to 1000 seconds which may be a bit more that you should allow for security-wise as the offset between client and server in your case is 73 seconds.


New version: Unity.Unity.6000.UWP version 6000.0.4f1

Created by 🥟 Dumplings in workflow run #5502.
Logs
Updated: 6000.0.3f1 → 6000.0.4f1
Submitting WinGet manifests
Pull request created: https://github.com/microsoft/winget-pkgs/pull/155721
Handling Unity.Unity.6000.Android...
Submitting WinGet manifests
Pull request created: https://github.com/microsoft/winget-pkgs/pull/155722
Handling Unity.Unity.6000.iOS...
Submitting WinGet manifests
Pull request created: https://github.com/microsoft/winget-pkgs/pull/155723
Handling Unity.Unity.6000.tvOS...
Submitting WinGet manifests
Pull request created: https://github.com/microsoft/winget-pkgs/pull/155724
Handling Unity.Unity.6000.visionOS...
Submitting WinGet manifests
Pull request created: https://github.com/microsoft/winget-pkgs/pull/155725
Handling Unity.Unity.6000.LinuxIL2CPP...
Submitting WinGet manifests
Pull request created: https://github.com/microsoft/winget-pkgs/pull/155726
Handling Unity.Unity.6000.LinuxMono...
Submitting WinGet manifests
Pull request created: https://github.com/microsoft/winget-pkgs/pull/155727
Handling Unity.Unity.6000.LinuxServer...
Submitting WinGet manifests
Pull request created: https://github.com/microsoft/winget-pkgs/pull/155728
Handling Unity.Unity.6000.MacMono...
Submitting WinGet manifests
Pull request created: https://github.com/microsoft/winget-pkgs/pull/155729
Handling Unity.Unity.6000.MacServer...
Submitting WinGet manifests
Pull request created: https://github.com/microsoft/winget-pkgs/pull/155730
Handling Unity.Unity.6000.UWP...
Submitting WinGet manifests

Microsoft Reviewers: Open in CodeFlow

@wingetbot run


Serenity/JS 2.0 migration guide

It's here for your review @jan-molak 😄- the Serenity/JS 2.0 migration guide.
Issues:

Tables - they look wrong on the served version of the site - for instance
Table of Contents - I had to put relative references in that cause the links to not work when you read the site via the rendered readme file. Maybe that doesn't matter?

Hi Jan, I'm in the process of completing this now. Just as a note to-selves... I've removed this bit:
 Alert.accept() | Accept.alert()
 Alert.dismiss() | Dismiss.alert()

As we haven't bottomed out the alerting vocabulary yet....


Tasks ran after ActionFunc block forever

What versions are you running?

$ go list -m github.com/chromedp/chromedp
github.com/chromedp/chromedp v0.6.5
$ google-chrome --version
Google Chrome 88.0.4324.96
$ go version
go version go1.16 linux/amd64

What did you do? Include clear steps.
I am getting the raw html of a site using chromedp.ActionFunc. However, after running chromedp.ActionFunc any further tasks, like chromedp.WaitVisible or chromedp.SendKeys block forever. The example below will not terminate, only if the line chromedp.WaitVisible("h1"), is commented out, or moved above the chromedp.ActionFunc it finishes.
package main

import (
	"context"
	"fmt"
	"log"

	"github.com/chromedp/cdproto/dom"
	"github.com/chromedp/chromedp"
)

func main() {
	ctx, cancel := chromedp.NewContext(context.Background())
	defer cancel()

	var body string
	err := chromedp.Run(ctx,
		chromedp.Navigate("https://example.com"),
		chromedp.WaitReady("body"),
		chromedp.ActionFunc(func(ctx context.Context) error {
			node, err := dom.GetDocument().Do(ctx)
			if err != nil {
				return fmt.Errorf("could not get doc: %w", err)
			}

			body, err = dom.GetOuterHTML().WithNodeID(node.NodeID).Do(ctx)
			if err != nil {
				return fmt.Errorf("could not get html: %w", err)
			}
			return nil
		}),
		chromedp.WaitVisible("h1"), // <- this will block for ever
	)
	if err != nil {
		log.Fatalf("Failed to open site: %v", err)
	}

	log.Print(body)
}

What did you expect to see?
I expect to run further tasks in the browser after running an chromedp.ActionFunc task.
What did you see instead?
Task ran after chromedp.ActionFunc block forever.

What's wrong?
According to my test, dom.GetDocument().Do(ctx) will cause the NodeIds in the browser to change, which will make those NodeIds stored in  chromedp stale. Which in turn will make chremedp out of order.
Here is the log that shows the NodeIds have been changed (just the interested entries are left):
2021/03/02 18:33:35 -> {"id":15,"sessionId":"2CE25C3047911DBCA12F308CD41C1AE4","method":"DOM.getDocument","params":{}}
2021/03/02 18:33:35 <- {"id":15,"result":{"root":{"nodeId":1,"backendNodeId":3,"nodeType":9,"nodeName":"#document","localName":"","nodeValue":"","childNodeCount":2,"children":[{"nodeId":2,"parentId":1,"backendNodeId":4,"nodeType":10,"nodeName":"html","localName":"","nodeValue":"","publicId":"","systemId":""},{"nodeId":3,"parentId":1,"backendNodeId":5,"nodeType":1,"nodeName":"HTML","localName":"html","nodeValue":"","childNodeCount":2,"children":[{"nodeId":4,"parentId":3,"backendNodeId":6,"nodeType":1,"nodeName":"HEAD","localName":"head","nodeValue":"","childNodeCount":5,"attributes":[]},{"nodeId":5,"parentId":3,"backendNodeId":7,"nodeType":1,"nodeName":"BODY","localName":"body","nodeValue":"","childNodeCount":1,"attributes":[]}],"attributes":[],"frameId":"418B15B13ECB3C8B5D2A5F377DAD8C07"}],"documentURL":"https://example.com/","baseURL":"https://example.com/","xmlVersion":""}},"sessionId":"2CE25C3047911DBCA12F308CD41C1AE4"}
2021/03/02 18:33:35 -> {"id":16,"sessionId":"2CE25C3047911DBCA12F308CD41C1AE4","method":"DOM.getDocument","params":{}}
2021/03/02 18:33:35 <- {"id":16,"result":{"root":{"nodeId":6,"backendNodeId":3,"nodeType":9,"nodeName":"#document","localName":"","nodeValue":"","childNodeCount":2,"children":[{"nodeId":7,"parentId":6,"backendNodeId":4,"nodeType":10,"nodeName":"html","localName":"","nodeValue":"","publicId":"","systemId":""},{"nodeId":8,"parentId":6,"backendNodeId":5,"nodeType":1,"nodeName":"HTML","localName":"html","nodeValue":"","childNodeCount":2,"children":[{"nodeId":9,"parentId":8,"backendNodeId":6,"nodeType":1,"nodeName":"HEAD","localName":"head","nodeValue":"","childNodeCount":5,"attributes":[]},{"nodeId":10,"parentId":8,"backendNodeId":7,"nodeType":1,"nodeName":"BODY","localName":"body","nodeValue":"","childNodeCount":1,"attributes":[]}],"attributes":[],"frameId":"418B15B13ECB3C8B5D2A5F377DAD8C07"}],"documentURL":"https://example.com/","baseURL":"https://example.com/","xmlVersion":""}},"sessionId":"2CE25C3047911DBCA12F308CD41C1AE4"}

You see that the the NodeIds  for the same backendNodeId: 3 are different.
The behavior of  DOM.getDocument is weird, and it's  not documented explicitly. The most related information I can find on Chrome DevTools Protocol document are:

DOM.Node:  DOM interaction is implemented in terms of mirror objects that represent the actual DOM nodes. DOMNode is a base node mirror type.

NodeId: Node identifier that is passed into the rest of the DOM messages as the nodeId. Backend will only push node with given id once. It is aware of all requested nodes and will only fire DOM events for nodes known to the client.

Since chromedp depends on NodeId badly, I think it should have a note to say that dom.GetDocument() should not be used directly. And according to https://github.com/puppeteer/puppeteer/pull/71#issuecomment-314599749, maybe we should  reconsider how to use the DOM domain in chromedp.
A workaround
Back to the issue, in fact,  it's easy to get the raw html without running into this issue.  You just need to use chromedp.OuterHTML. Here are the changes  to your code:
 package main

 import (
    "context"
-   "fmt"
    "log"

-   "github.com/chromedp/cdproto/dom"
    "github.com/chromedp/chromedp"
 )

 func main() {
    ctx, cancel := chromedp.NewContext(context.Background())
    defer cancel()

    var body string
    err := chromedp.Run(ctx,
        chromedp.Navigate("https://example.com"),
        chromedp.WaitReady("body"),
-       chromedp.ActionFunc(func(ctx context.Context) error {
-           node, err := dom.GetDocument().Do(ctx)
-           if err != nil {
-               return fmt.Errorf("could not get doc: %w", err)
-           }
-
-           body, err = dom.GetOuterHTML().WithNodeID(node.NodeID).Do(ctx)
-           if err != nil {
-               return fmt.Errorf("could not get html: %w", err)
-           }
-           return nil
-       }),
-       chromedp.WaitVisible("h1"), // <- this will block for ever
+       chromedp.OuterHTML("html", &body, chromedp.ByQuery),
+       chromedp.WaitVisible("h1"),
    )
    if err != nil {
        log.Fatalf("Failed to open site: %v", err)
    }

    log.Print(body)
 }

BWT, maybe chromedp.WaitReady and chromedp.WaitVisible don't behave as you think. Please check the doc and the source code.

@ZekeLu Not just DOM.getDocument, read the doc of DOM.getDocument: "Fired when Document has been totally updated. Node ids are no longer valid."

maybe we should reconsider how to use the DOM domain in chromedp.

Maybe you can copy the design from Rod to Chromedp.

I think  you meant the DOM.documentUpdated event.  Yes, I have read that doc, and it has been handle by chromedp:
https://github.com/chromedp/chromedp/blob/e2970556e3d05f3259c464faeed1ec0e862f0560/target.go#L232-L254
And it handled it by calling DOM.getDocument, that's why the user should not call it again.
I think the problem is that is not documented that the call to DOM.getDocument will cause the node ids become invalid. And the name is a little misleading. The key is not to call dom.GetDocument in chromedp directly.

@ZekeLu Yes, the problem is the t.frameMu chromedp still can't 100% prevent the race condition. For example, if you query a node and get the node id, then the DOM.documentUpdated happens because the goroutine handles the event is blocked by some slow consumer, the node id will be invalid even the user has never called the dom.GetDocument directly.
That's why I say chromedp should follow a similar design about how to handle the remote node: using the object id, not the node id.

the DOM.documentUpdated happens because the goroutine handles the event is blocked by some slow consumer

It's documented that the handler should avoid blocking at all costs.
https://github.com/chromedp/chromedp/blob/e2970556e3d05f3259c464faeed1ec0e862f0560/chromedp.go#L675-L678
Anyway, I got your point. The node id will become invalid. But if not caused by calling to dom.GetDocument, then it should be caused by page reloading or page navigation. In this case, the remote object id should become invalid too (I'm not sure about this. Please correct me if I'm wrong).
That said, I have taken a look into Rod and found many things to learn from. Next time when I have an issue which can not be addressed gracefully with chromedp, I will try Rob's way.
Thank you very much!

@ZekeLu If you run actions after the page is loaded, then might be fine. There will be two DOM.documentUpdated for each navigation, it's still a mystery for me why it's not one, and you can run DOM.querySelector before the DOM.documentUpdated events. Also, there's no doc to say only page reloading or page navigation will trigger DOM.documentUpdated, maybe we should read the source code of chromium to understand the details.

It seems that there is nothing more to do now. Closing.

chromedp.OuterHTML("html", &body, chromedp.ByQuery),
What happens if the page is not containing  tag?

If the page contains arbitrary content and you don't know the element to select in advance, then maybe you could try Fetch.getResponseBody.


store matches in firestore

should write match state periodically to firestore so that api can look up in firestore. also better for historising games.
one thought is that i could look in the memory of the process that receives the api call (ie have all running matches in a map). If it's there return it immediately (saves a call to firestore and is quicker), if it's not, check firestore. this would still work if i ever want to run the api across multiple instances, and greatly reduce the total number of firestore calls if only a single instance is running.

obvious solution that came to me is that there is no api for game states. just use firebase objects.


frame_rate on server always 0

I have send video data by the function rmtpMuxer.writeVideo() but the frame_rate data on server always 0, Now video can be recorded on server on can't watch it live.
Does not sure what I should do, I want to make it able to watch it realtime.

Seem like frame_rate data is does not matters to watch it realtime, so I will close it.


composer

The Composer installer script did not run correctly [exit code 1].
Script Output:
PHP Warning:  Module "openssl" is already loaded in Unknown on line 0

You need to fix your php.ini file so that the openssl extension is only loaded once.

How can I do it, I have tried but no solution can you explain me well step by step please.
Enviado do Outlook para Androidhttps://aka.ms/AAb9ysg

From: John Stevenson @.>
Sent: Monday, September 16, 2024 1:55:14 PM
To: composer/windows-setup @.>
Cc: MARGARIDA76 @.>; Author @.>
Subject: Re: [composer/windows-setup] composer (Issue #161)
You need to fix your php.ini file so that the openssl extension is only loaded once.
—
Reply to this email directly, view it on GitHubhttps://github.com/composer/windows-setup/issues/161#issuecomment-2352707206, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AWVUBF3W6L3GE7L7IVCMFVLZW3BKFAVCNFSM6AAAAABOI3CHLGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJSG4YDOMRQGY.
You are receiving this because you authored the thread.Message ID: @.***>

Open the file, search for extension=openssl, remove the duplicate entry.

I have tried that but the problem is continuing
Enviado do Outlook para Androidhttps://aka.ms/AAb9ysg

From: John Stevenson @.>
Sent: Monday, September 16, 2024 2:40:35 PM
To: composer/windows-setup @.>
Cc: MARGARIDA76 @.>; Author @.>
Subject: Re: [composer/windows-setup] composer (Issue #161)
Open the file, search for extension=openssl, remove the duplicate entry.
—
Reply to this email directly, view it on GitHubhttps://github.com/composer/windows-setup/issues/161#issuecomment-2352807122, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AWVUBF4HXF7H2C2NULQRB63ZW3GUHAVCNFSM6AAAAABOI3CHLGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJSHAYDOMJSGI.
You are receiving this because you authored the thread.Message ID: @.***>

I cannot really help you without a log file (as requested when you opened this issue).

Thank you very much for spend your time to guide me for resolution
Enviado do Outlook para Androidhttps://aka.ms/AAb9ysg

From: John Stevenson @.>
Sent: Monday, September 16, 2024 3:37:10 PM
To: composer/windows-setup @.>
Cc: MARGARIDA76 @.>; Author @.>
Subject: Re: [composer/windows-setup] composer (Issue #161)
I cannot really help you without a log file (as requested when you opened this issue).
—
Reply to this email directly, view it on GitHubhttps://github.com/composer/windows-setup/issues/161#issuecomment-2352947426, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AWVUBF5CQX2GPUB4L4F3QPDZW3NINAVCNFSM6AAAAABOI3CHLGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJSHE2DONBSGY.
You are receiving this because you authored the thread.Message ID: @.***>


Implement Custom Service Provider

[!NOTE]
This custom service provider granted for open source community

Additional Note

[!NOTE]
This still wip, not done yet because I am still focusing touring golang


Hash check to skip doesn't work in specific case

In the following scenario:

I build with a build directory "dist"
grunt-webfont correctly generates file and caches the hash
I change the build directory to "dist2"
I run grunt-webfont again

Result: Running grunt-webfont will not produce the file I need in dist2 dir
I think the assumption that since the hash matches, it doesn't need to generate new files is perhaps too broad.
I don't see a way, as of now, to fix this except to wipe node_modules or manually remove the hash check.

Actually, a slightly more realistic scenario might be:

grunt build
grunt clean
grunt build

Highly reproducible

You can just remove any generated file.
And of course it’s not “too broad”. Perhaps there’s a bug in hash calculation, I’ll look at it.

As part of the steps I mentioned above, the generated file is already deleted.  In fact, the entire output directory is wiped.  The only file that remains is hash.
I realize there's code that checks the generated code AFTER checking the hash, attempting to remedy this:
https://github.com/sapegin/grunt-webfont/blob/master/tasks/webfont.js#L131-L137
However, what happens if you have: 1) a hash 2) no files.  Since the file does not exist (https://github.com/sapegin/grunt-webfont/blob/master/tasks/webfont.js#L133), it returns false, and so it believes no regeneration is necessary.

Nevermind - I think I found the issue on my side.  I'll update with details

Hm, actually its a bit of both?
This line gets the list of generated font files.  When I've wiped my dist/ output directory, this returns with an empty array.  The next 2 lines add the demo path and the css path.
https://github.com/sapegin/grunt-webfont/blob/master/tasks/webfont.js#L128
I happen to have my css outside of my output dir, so in that case, it exists and _.some returns false.
If wf.generatedFontFiles(o) returns an empty array, I think regenerationNeeded should be true.

I submitted a PR https://github.com/sapegin/grunt-webfont/pull/230


app is undefined for electron-updater

I'm trying to use electron-updater from electron-builder, but get the following errors:
Uncaught TypeError: Cannot read property 'getVersion' of undefined
    at AppUpdater
…

&
Uncaught (in promise) TypeError: Cannot read property 'isReady' of undefined
    at AppUpdater.untilAppReady.resolve
…

The problem is:
this.app = require("electron").app stays undefinded

I run everything in app/main.dev.js and still get the same error. @amilajack  Is app/main.dev.js what you mean by main process? Thanks

Forget it, I'm just stupid

I just never removed the error-creating code.
What could be improved is the documentation. I had to understand the boilerplate before making updates work. (That actually doesn't sound like a bad thing.)
It probably took me several hours to get updates to work properly.

I had to realize that electron-builder is used and how that works
That I could use S3 instead of an update server
Set S3 up
Figure out that I have to run this in the main process and where that is

Mhm. I think I should add support for auto-updates. But I haven't bought a developer certificate from Applet yet and I can't test auto updates without it

Please see #1387


Netflix bug that break the player

There is a bug that causes the Netflix to be annoying, and it's happening while watching a movie that has a 16:9 aspect ratio (most of the movies use that aspect ratio), a white bar appears on the right side of the web that will let you scroll down and break the player, it's so anyone that even brake your immersion, but it will not happening when the movie is 1:1 aspect ratio
I tried to explain the bug in this video so you can fix it as soon as possible
yes I disabled all the other extensions and try to reinstall your extension there was no hope

@nzarbayezid Thanks for the report. I've seen this before - will take a look again.

@nzarbayezid The only way I can consistently reproduce this is if the subtitle offset from the bottom of the player is too low. Can you try setting that setting to a higher number? Also what version of the extension are you using?

no bro that's not the problem, as I told you I tried many ways to fix it but it's the extension

@nzarbayezid Thanks for replying. I suggested a possible way to fix the issue as you did not specify exactly what you had already attempted in order to fix the problem.
If you have time it would be helpful if you pasted a screenshot of the DOM elements of the page where you're seeing the issue. Specifically it would be helpful to know which element is overflowing the bottom of the page. You can access the DOM elements by right clicking on the page and clicking 'Inspect element.'

@nzarbayezid awesome thanks, do you think you could click through the elements and try to highlight the elements at the bottom? If you can highlight the element that's going off the screen that would be great.

@nzarbayezid Also, would be nice to see if the problem is the drop zone. If you drag a file into the Netflix player, does the dark asbplayer overlay go past the edge of the window? I attached a video of what it looks like for me.
https://user-images.githubusercontent.com/2254858/163657370-988cbc54-b911-4714-b85e-2bcab99987c1.mp4

https://user-images.githubusercontent.com/101425664/163669267-91a85261-acd1-45a9-972a-50d5ac552d1a.mp4
if you want any more information you can ask, I will answer you happily my dude

If you drag a file into the Netflix player, does the dark asbplayer overlay go past the edge of the window?

@nzarbayezid Thanks for all the help. I've attached two different versions of the extension. One is the latest version and the other has a workaround for your problem (as I don't know the root cause). If you have time, let me know if the first, the second, both, or none of them fix the issue.
asbplayer-extension-0.18.0-snapshot.zip
asbplayer-extension-0.18.0-snapshot-overflow-fix.zip

thanks
https://user-images.githubusercontent.com/101425664/163699749-945e5ea1-bc9d-48ab-aadd-d6fbe43fec29.mp4

Going to go ahead and close this since it seems to be resolved.
I think for some reason the Netflix video element seems to be extending past the bottom of the screen in your case. At the moment there isn't a reason to believe that asbplayer is the thing that's causing that to happen.


Bump versions and improve web-bundler support

CI error is:
Error: [ERROR] 	[error]: Build step io.quarkiverse.web.bundler.deployment.WebDependenciesScannerProcessor#collectDependencies threw an exception: io.quarkus.runtime.configuration.ConfigurationException: The Web Bundler is configured to only include compileOnly web dependencies, but org.webjars.npm:bootstrap-icons:1.10.3 is set as runtime. Use a compile only scope (e.g. provided) or set quarkus.web-bundler.dependencies.compile-only=false to allow runtime web dependencies.


[AutoPR datalake-analytics/data-plane] Add hierarchyQueueNode into JobInformation(Basic)

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3942

This PR has been merged into https://github.com/Azure/azure-sdk-for-java/pull/2401


Support for CLIP visual encoder

Motivation and Context
This PR enables support for a CLIP-trained ResNet visual encoder backbone for training and eval.

How Has This Been Tested

Types of changes

[Experiment] A pull request that add new features to the habitat-baselines training codebase. Experiments Pull Requests can be any size, must have smoke/integration tests and be isolated from the rest of the code. Your code additions should not rely on other habitat-baselines code. This is to avoid dependencies between different parts of habitat-baselines. You must also include a README that will document how to use your new feature or trainer. You will be the maintainer of this code, if the code becomes stale or is not supported often enough, we will eventually remove it.

Checklist

[x] My code follows the code style of this project.
[ ] I have updated the documentation if required.
[x] I have read the CONTRIBUTING document.
[x] I have completed my CLA (see CONTRIBUTING)
[ ] I have added tests to cover my changes if required.

@Ram81 @naokiyokoyama Feel free to review.


Remote Write: Close connection after 3 retries

I propose a change in remote write. If we error out for > 3 times, then we close the connection.
This is to help with user that are using load balancers and DNS, where the active connection might point to a wrong DNS entry but the load balancer of the old entry is still active, replying 503.

it feels a little bit hacky, if the server is still replying, I don't see why we should close the connection. Maybe the some tweaking should be done on the DNS side to quickly exclude the server.

I think https://github.com/prometheus/prometheus/issues/15262 is also related.
I would feel better about this change if it was 3 5xx errors; as it stands I think 3 429s would cause a close, which seems worse than before.


Accept composer auth secret in reusable PHPUnit workflow.

What?
Allow calling actions to pass composer auth secret.
Needed for Polylang Pro ACF integration.

I wonder 2 things:

Why do this here instead of a repository basis? Maybe because it's easier to manage secrets in a single place for all repos?
Instead of COMPOSER_AUTH: ${{ secrets.GH_COMPOSER_AUTH }}, should we do COMPOSER_AUTH: '{"http-basic": {"connect.advancedcustomfields.com": ${{ secrets.ACF_AUTH }}}}'? (I'm not sure it's doable though.) This would allow to cherry-pick secrets at the repo level.

I think you have the right solution but I explore other possibilities.

I wonder 2 things:

Why do this here instead of a repository basis? Maybe because it's easier to manage secrets in a single place for all repos?

Instead of COMPOSER_AUTH: ${{ secrets.GH_COMPOSER_AUTH }}, should we do COMPOSER_AUTH: '{"http-basic": {"connect.advancedcustomfields.com": ${{ secrets.ACF_AUTH }}}}'? (I'm not sure it's doable though.) This would allow to cherry-pick secrets at the repo level.

I think you have the right solution but I explore other possibilities.

You cannot define env var in the repository and expect it to be accessible in reusable workflow Shell unfortunately.

I don't understand why we would want to cherry pick auth key here.  The composer auth variable is set with what it gets, nothing more nothing less. So anything beeded by calling action will access it in its bash script.


Fixes /users PUT response to include actual user data

What's this PR do?
The response to a PUT /users request used to only have a valid updated_at field. All other user data was null. This fixes that.
This also updates a phpunit test to verify that.
Any background context?
Came across this while doing work on the Android app. The app would update its cache of user information based on what'd get returned from the /users PUT response. And the previous response basically seemed like it would null everything out.
What are the relevant tickets?
Fixes #205

:+1:


Fixes and formatting

Description

added neutral-background-color-selected tokens
added missing color-slider color tokens:

color-slider-border-color
color-slider-border-opacity

fixed typo in token name:

renamed color-wheel-area-margin to color-wheel-color-area-margin

reorganized tokens to align with Excel document better for easier comparisons

Related Issue

DNA-1233
DNA-1238
DNA-1235

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

:tada: This PR is included in version 12.0.0-beta.63 :tada:
The release is available on:

GitHub release
npm package (@beta dist-tag)

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.0 :tada:
The release is available on:

GitHub release
npm package (@next-major dist-tag)

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 12.0.0 :tada:
The release is available on:

GitHub release
npm package (@next-major dist-tag)

Your semantic-release bot :package::rocket:

@GarthDB The MR was quite a long time ago, but I'll give it a try anyway. Maybe you can give me a good hint.
Briefly about the background of my question. I am currently educating myself in the area of design systems and I am using Spectrum as a well done example. I'm currently looking into building and using Spectrum's design tokens, and in the process I came across the following question:
Why does the eventual Slider Component directly uses the gray colors (gray-300 and gray-700) for the background of the (filled) track, instead of any existing color alias?  I mean, are there no intervening design decisions with these colors that are reflected in the alias tokens? This decision might even be applicable to the Switch.
Thanks for your answer!


Translations get erased when deleting a block inside a blocks field

Bug Report
I've noticed a sort of critical bug, that causes us great headaches currently. Somehow the translations of blocks seem to be entangled with the index of the block, rather than the ID. When deleting a block, all translations of the following blocks get deleted, leading basically to a completely erased translation, if you delete the first block.
Steps to Reproduce

Create a simple collection with a blocks area that allows a block with a localized text field and configure two locales

{
  slug: 'test-collection',
  fields: [
    {
      name: 'blocks',
      type: 'blocks',
      blocks: [
        {
          slug: 'text',
          fields: [
            {
              name: 'text',
              type: 'text',
              localized: true,
            },
          ],
        },
      ],
    },
  ],
},

(something like this, there may be missing attributes)

Create a document, adding 2 blocks and translate them
Delete block 1
The translation of block 2 is erased

Other Details
Tested this with the newes version of Payload (1.5.4)
Only the follwing blocks of the deleted one lose their translation. When having 3 blocks and you delete the second one, the first one still has the translation, which led me to the conclusion, that it's somehow dependent on the index of the block inside the array.
Edit:
Also happens when reordering the blocks instead of deleting one.

Well, talk about timing... :D
#1832


[JS] [Service Bus] Fix missing TypeScript definitions for https-proxy-agent

In Service Bus' TypeScript samples we are importing https-proxy-agent, however: There are no TypeScript definitions for this package. This issue even exists in the source repository for this module, see: https://github.com/TooTallNate/node-https-proxy-agent/issues/27
As @ramya-rao-a suggested offline:

Contributing the typings upstream is the right step forward.

Let's get in touch with @TooTallNate and then let's send him a PR with the missing definitions ✨
Note: I have assigned this to me, but feel free to assign it to someone else.

Update:
The one and only @TooTallNate merged a PR that I made addressing this https://github.com/TooTallNate/node-https-proxy-agent/pull/66
We still need to wait for the version bump, but I could make a PR with our side of the fixes right now if that's ok.

Closing this since we have the types now :)


Primary Thread for PowerPlatform actions not working for Github workflows. .

Folks, to keep things together with regard to the issues the folks have been having with the PowerPlatform Actions, and compensations we may need to we are going to update this thread going forward and link the other issues to it.
#174
#173
#172
At this time, we have tracked the issue back to a GitHub Runner update that updated the way actions were checked out.
This change seems to have impacted actions that rely on the large file system support for gitHub as part of managing assets for actions.
We are working directly with the Git hub Runner's team actively to resolve this issue.
We are concurrently working to develop a workaround to the root issue and will post here once we have determined the best way to unblock your workflows.

Folks we have deployed a new release 0.5.2  that will allow your builds to work properly until a full fix is created with GitHub.
Please update your workflows to use 0.5.2 actions to get around this issue.
This issue will remain open for comment and feedback and updates to you as we resolve it completely.

@MattB-msft I'm facing below error while using version 0.5.2

Hello, your YML files should now work as usual, the LFS update has been rolled back for runners.

@kkanakas @MattB-msft - It is working again. Thank you.

Also, as a general rule if you use  /who-am-i or /who-am-o@v0  it will use the v0 tag which we keep pointed at the leading edge.  ( 0.5.3. for the moment)
for more info on this .. see : https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsuses

Folks we are resolving this at this time as GitHub as communicated that the issue is now fixed on their side.
Sorry for the disruption here.
Our next 'normal' release will bring back the git large file system configuration for faster action downloads.


Added new commands and modified existing vm commands for vm onboarding, policy enforcement for nonk8s control plane

Signed-off-by: Eswar Rajan Subramanian<EMAIL_ADDRESS>

@daemon1024 , can you please review this PR? Thanks


Virtual Assistant - Telemetry isn't working

Project - Virtual Assistant
Language: C#
Description
Telemetry Custom Events aren't working in the virtual assistant beyond the basic BotMessageSend and BotMessageReceived events.  None of the enhanced reporting events described in the Analytics section are captured.
The test case a generic VirtualAssistant with no skills.
This is likely a configuration issue, but I can't seem to find information about this.  Previously, telemetry was capture through recognizers, but that appears to have changed.
To Reproduce
Create a VA bot with template and configure telemetry, and run it.
The TelemetryClient is configured properly because my own custom telemetry events are logged properly.
A symptom might be that the TelemetryClient property appears to be reset to NullBotTelemetryClient for the MainDialog sometime after the constructor is called.
Snippet from MainDialog Constructor.  Saving telemetryClient in my own local plus displaying to App Insights.
TelemetryClient = telemetryClient;
_telemetryClient = telemetryClient;
TelemetryClient.TrackEvent($"MainDialog Constructor - Telemetry Client {TelemetryClient.ToString()}");

Snippet from MainDialog RouteAsync.  Note from screen capture that TelemetryClient has been reset to NullTelemetry.
_telemetryClient.TrackEvent($"MainDialog RouteAsync _telemetryClient {_telemetryClient.ToString()}");
 _telemetryClient.TrackEvent($"MainDialog RouteAsync TelemetryClient {TelemetryClient.ToString()}");

Snippet from DialogBot Constructor to see if it's being extracted properly there (and it is):
_telemetryClient = serviceProvider.GetService<IBotTelemetryClient>() ?? throw new ArgumentNullException(nameof(IBotTelemetryClient));
_telemetryClient.TrackEvent($"DialogBot Constructor - _telemetryClient: {_telemetryClient.ToString()}");

Here is the App Insights produced:

Expected behavior
Bot Telemetry should be produced.

Thanks @mekinney, the TelemetryClient needs to be passed in the LUIS and QnA recognizers to properly log, you can take a look at #1354 for a sample.
@enzocanoo can you verify if the Typescript version needs this update as well?

@mekinney - good spot, this should have been wired up and we'll publish a new VSIX shortly. If you move the above changes across you should be good to go.

Hey @ryanlengel, we added the Telemetry implementation for TypeScript in #1322 and fixed the QnA implementation with #1357.

Thanks.  This fixed it.


⚠ GitLab Server has degraded performance

In ba52372, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 3515 ms

Resolved: GitLab Server performance has improved in c926d22.


Aizad/FEQ-1874/Dropdown-Component-Fixes

Issues:

[ ] dropdown arrow rotating animation
[ ] dropdown input field not full width
[x] empty div issue for helper message placeholder below dropdown
[ ] only the colour of the label dims instead of the whole dropdown when it is disabled

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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 60.437%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
222

Relevant Lines:
344

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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 60.437%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
222

Relevant Lines:
344

💛  - Coveralls


Add support for compressed textures

We should support:

DDS
PVRTC
ETC

PVRTC is not yet supported. Also, we need server generation (user format -> platform specific formats -> select which to load based on platform).

All formats are supported now, only server generation is required.


DOM is re-arranged when Politespace is activated

If you have an input that uses Politespace, and say you have a span or some other DOM above or below the input it seems that Politespace will flip the position of these elements so that whatever was below the input becomes on top (and vice versa).
This requires me to wrap the input with a span or div which is not ideal.

I believe this was fixed with https://github.com/filamentgroup/politespace/commit/2ce813cd4c19b183ad86108b6590d246fc910cef (v0.1.17). Please reopen if this is not the case!

@zachleat I don't see release notes in your releases. we are running 1.6b, and wondering if we should update (would there be any downsides to look out for)?


Support installing deps with yarn

There's a new package manager in town and it's really fast. Figure we could add this for some of us to use during development while we evaluate. @joaomoreno feel free to merge if you're good with it.
Notes:

It's really fast, this is the cached/second run speed:
> time ./scripts/npm.sh install --arch=x64
...
real    1m54.064s
user    1m40.364s
sys     0m10.160s

> time ./scripts/yarn.sh install --arch=x64
...
real    0m23.007s
user    0m26.692s
sys     0m3.624s

The main speed gain seems to be in that native modules are built concurrently with up to 5 building at a time:
[1/6] ⡀ gc-signals<EMAIL_ADDRESS>| linux | x64
[-/6] ⡀ waiting...
[3/6] ⡀ native-keymap<EMAIL_ADDRESS>| linux | x64
[4/6] ⡀ pty.js
[5/6] ⡀ oniguruma<EMAIL_ADDRESS>| linux | x64

It mentions in the output that npm-shrinkwrap.json is not respected:
error npm-shrinkwrap.json found. This will not be updated or respected. See [TODO] for more information.

Added yarn.lock to .gitignore, here's some info on the file: https://yarnpkg.com/en/docs/yarn-lock

Removed /1.6 from the xterm.js branch and filed a bug against yarn (https://github.com/yarnpkg/yarn/issues/744), this still seems to work fine on with ./scripts/npm.sh, perhaps because the exact commit is specified in npm-shrinkwrap.json

I did a quick sanity test of vscode built using yarn and it seems fine.

Tested only Ubuntu 16.04 with command ./scripts/yarn.sh install --arch=x64

isn't scripts/yarn.sh a copy of scripts/npm.sh ? From my little knowledge about yarn, shouldn't it replace npm ? https://code.facebook.com/posts/1840075619545360/yarn-a-new-package-manager-for-javascript/

@nojvek The only real difference in the script is that is called yarn instead of npm, the intent here is to test it though while continuing to use npm. The npm-shrinkwrap.json issue mentioned in the PR is an example of something that must be fixed/looked into before we adopt it.

I see.

This is pretty cool. Although there's the problem of, lacking shrinkwrap, not being yet able to be used as our dependencies solution across developer boxes and build environments. We will potentially get into issues in our dev environments which would never surface in the product. Even worse: issues which never surface in the dev environments but do so in the product. This would be issue hell.
My intuition tells me to wait for shrinkwrap support before merging this, lest collaborators start using it and depending on it to just work.

It looks like yarn.lock is their version of npm-shrinkwrap.json and it should be included, so your issue could be worked around by keeping yarn.lock up to date. I guess let's wait for it to mature a little and then switch 100% to prevent any confusion. The time savings would really add up for me as I reinstall deps fairly frequently.

Can this be revisited? Yarn has proven itself to be reliable to many folks over the last 6 months since this issue was posted, and it's growing quickly in popularity.
I would be happy to submit an updated PR, although this is the kind of minor but far-reaching change that it is often faster for people with commit access to do.


ion-select does not support ion-options with boolean values

Ionic version:  (check one with "x")
[ ] 1.x (For Ionic 1.x issues, please use https://github.com/driftyco/ionic-v1)
[ ] 2.x
[x] 3.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

<ion-item>
  <ion-label>Is this new?</ion-label>
  <ion-select [(ngModel)]="isNew">
    <ion-option value="true">Yes</ion-option>
    <ion-option value="false">No</ion-option>
  </ion-select>
</ion-item>

ion-option value will parse the boolean value to string even if the model is of type boolean
Expected behavior:

ion-option value="true" should have a boolean value instead of a string value, I was expecting ion-option value="'true'" to return a string value instead of the one before. Instead both exhibits the same behavior.
Steps to reproduce:

See above
Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
global packages:

    @ionic/cli-utils : 1.1.2
    Cordova CLI      : not installed
    Ionic CLI        : 3.1.2

local packages:

    @ionic/app-scripts              : 1.3.7
    @ionic/cli-plugin-cordova       : 1.1.2
    @ionic/cli-plugin-ionic-angular : 1.1.2
    Ionic Framework                 : ionic-angular 3.1.0

System:

    Node       : v7.10.0
    OS         : Linux 4.8
    Xcode      : not installed
    ios-deploy : not installed
    ios-sim    : not installed

this is not how angular input's work:
something="true"

is always passed as string, you need instead:
[something]="true"

Refer to this: http://stackoverflow.com/questions/36802522/angular-2-ngmodel-binding-for-radio-input-of-boolean-type

@manucorporat Thanks, it didn't occur to me that it was angular input. My mistake.


Cannot fetch stream api response

Description
When I implement this fetch curl api on node.js standalone project, I get stream response,
And I implement in react-native project I cannot get response
async function chat(prompt) {
const API_KEY = "XXXX";
const url = new URL(
https://generativelanguage.googleapis.com/v1beta/models/gemini-2.0-flash-exp:streamGenerateContent?key={API_KEY}
);
const response = await fetch(url, {
method: "POST",
headers: {
"Content-Type": "application/json",
},
body: JSON.stringify({
contents: [
{
parts: [{ text: prompt }],
},
],
}),
});
if (!response.ok) {
console.error("Request failed", response.statusText);
return;
}
const reader = response.body.getReader();
const decoder = new TextDecoder();
let done = false;
let content = "";
while (!done) {
const { value, done: readerDone } = await reader.read();
done = readerDone;
content += decoder.decode(value, { stream: true });
console.log(content);
}
// Final content received
console.log("Final Content:", content);
}
Steps to reproduce
Copy above code and use fetch in single node.js project
It gets logging out stream response
When I copy and past on react-native project
And I call it,
Not getting response.body in fetch
"dependencies": {
"@google/generative-ai": "^0.21.0",
"@react-native-firebase/analytics": "^19.3.0",
"@react-native-firebase/app": "^19.3.0",
"@react-native-firebase/auth": "^19.3.0",
"@react-native-firebase/firestore": "19.3.0",
"@react-native-firebase/functions": "^19.3.0",
"@react-native-firebase/messaging": "^19.3.0",
"@react-native-firebase/remote-config": "^19.3.0",
"@react-navigation/stack": "^6.3.29",
"axios": "^1.7.9",
"country-flag-icons": "^1.5.13",
"https-browserify": "^1.0.0",
"moment-timezone": "^0.5.45",
"react": "18.2.0",
"react-native": "^0.73.9",
"react-native-device-info": "^10.13.1",
"react-native-fs": "^2.20.0",
"react-native-gesture-handler": "^2.16.1",
"react-native-keychain": "^8.1.3",
"react-native-localize": "^3.2.1",
"react-native-paper": "^5.12.3",
"react-native-safe-area-context": "^4.9.0",
"react-native-screens": "^3.29.0",
"react-native-sound": "^0.11.2",
"react-native-sse": "^1.2.1",
"react-native-vector-icons": "^10.0.3"
},
"devDependencies": {
"@babel/core": "^7.20.0",
"@babel/preset-env": "^7.20.0",
"@babel/runtime": "^7.20.0",
"@react-native/babel-preset": "0.73.21",
"@react-native/eslint-config": "0.73.2",
"@react-native/metro-config": "0.73.5",
"@react-native/typescript-config": "0.73.1",
"@types/react": "^18.2.6",
"@types/react-native-vector-icons": "^6.4.18",
"@types/react-test-renderer": "^18.0.0",
"babel-jest": "^29.6.3",
"eslint": "^8.19.0",
"jest": "^29.6.3",
"prettier": "2.8.8",
"react-test-renderer": "18.2.0",
"typescript": "5.0.4"
},
React Native Version
"react-native": "^0.73.9"
Affected Platforms
Runtime - Android, Runtime - iOS
Output of npx react-native info
OS: macOS 15.2
  CPU: (12) arm64 Apple M2 Pro
  Memory: 202.84 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 23.3.0
    path: /opt/homebrew/bin/node
  Yarn: Not Found
  npm:
    version: 10.9.0
    path: /opt/homebrew/bin/npm
  Watchman:
    version: 2<IP_ADDRESS>
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.16.2
    path: /usr/local/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 24.1
      - iOS 18.1
      - macOS 15.1
      - tvOS 18.1
      - visionOS 2.1
      - watchOS 11.1
  Android SDK: Not Found
IDEs:
  Android Studio: 2023.3 AI-233.14808.21.2331.11709847
  Xcode:
    version: 16.1/16B40
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.11
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.73.9
    wanted: ^0.73.9
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false

Stacktrace or Logs
ERROR  Error fetching data: [TypeError: Cannot read property 'read' of undefined]

Reproducer
https://github.com/huseyinaltas/Shock
Screenshots and Videos
No response

upgraded react-native 0.75.4 and trying now

0.75.4 has same issue

Hi @huseyinaltas,
It would be really helpful if you could provide a sample reproducer. You can use this template to create one.
Also, I noticed that the link to your repository (Shock) is returning a 404 error, so I’m unable to access it.
Could you let me know if this issue is platform-specific (i.e., Android or iOS)? I see that you're using the old architecture—would it be possible to try with the new architecture as well?

Hi @sarthak-d11  - I pushed app to here
https://github.com/huseyinaltas/ChatAPP
Issue is occurring on IOS and Android
I get "Error generating content: [TypeError: Cannot read property 'pipeThrough' of undefined]"

import { fetch } from "expo/fetch"

docs

Thank you @yanglee2421, this is the way. closing.


New project moving along

Hey there ! What do you think about this new project! @PardesiCat

Namaste, yes, I saw indeed a nice concept. I have made some suggested changes, which I explain in the pull request.
please check my pull request https://github.com/felipealfonsog/Upd8All/pull/29

great! Version 0.0.17 is now up and running ... stable .... try to use the development branch please for PR ...

Good idea would be now to promote this utility - piece of software ...

Got the v.0.0.18 running better and handles better a few things .... you can get it on AUR ... yay -S upd8all
And in this version in the tarball you appear as a contributor ! ... Thanks!

v.0.0.20 improved... lots of bugs and new formula now in the code ...

Namaste... i just saw previous issue you closed.
i was busy  didnt came online
i notice there minor issue in service script
in both main and devlopment branch  which is

# Extract the source file
tar xf "v.$pkgver.tar.gz"

it should be

tar -xf

"-" is missing
else everything working fine...

2nd. after install succesfully
this executable file doesn't get deleted; it remains, along with install_service.sh.

This was created by the following code.

Create a shell script to execute upd8all.py and copy it to /usr/local/bin
echo '#!/bin/bash' > upd8all
echo 'python /usr/local/bin/upd8all.py "$@"' >> upd8all
chmod +x upd8all
install -Dm755 upd8all "/usr/local/bin/upd8all"

We should add suggested solutions inside the clean-up code.
# Clean up temporary files
rm -rf "v.$pkgver.tar.gz" "Upd8All-v.$pkgver"
rm -rf "upd8all"


[bootstrap] Start recognizing Windows in bootstrap

This are minimal changes required to start Windows bootstapping.

@swift-ci smoke test


Could Doughnut chart has labels?

labels show how much the part taken.

The one thing that makes donuts really cool is having a big fat label in the empty space inside the doughnut

Consolidating all doughnut labelling issues in #78


Accept other analytic tool

I wonder if it would be possible to allow other analytics tools, instead of Google Analytics, in the IPT Settings.
We decided to use https://matomo.org at Rio Botanical Garden, and there is no simple way to make it work with IPT. Thus, please, consider to be more inclusive at the analytic tools that could be associated with IPT, in the "Settings".

Essentially https://github.com/gbif/ipt/issues/1988  — for flexibility, the administrator including a few lines of Javascript at the end of the page should be sufficient (Matomo's instructions: https://developer.matomo.org/guides/tracking-javascript-guide#finding-the-piwik-tracking-code).

Thanks @MattBlissett ! I'm looking forward to it.

If you need a quick fix, and you're using Tomcat or similar, you can manually edit .../WEB-INF/pages/footer.ftl

If you need a quick fix, and you're using Tomcat or similar, you can manually edit .../WEB-INF/pages/footer.ftl

Thanks @MattBlissett . That will be a little bit complicated, considering the access negotiation with IT Department. There is any possible horizon to next versions of IPT to have this feature implemented?

We (GBIF Finland/FinBIF) recently switched from GA to plausible across our services. Having plausible as an option would be handy for us at least.


Native backup encryption

Background: https://airtable.com/tblD3oZPLJgGhCmch/viwchkdQkRUw6hZ3z/recdIQAVjegzI4DpL?blocks=hide
PM: @rolandcrosby
Eng:

Closing - can't find the corresponding AirTable entry


Example agent doesn't work with conda install

@beauxel Could you share the repro steps and the error you get?

landon@landon:~/Desktop/gitRepos/CyberBattleSim$ bash install-conda.sh

mkdir -p /home/landon/miniconda3
wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh -O /home/landon/miniconda3/miniconda.sh
--2023-09-02 09:13:56--  https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh
Resolving repo.anaconda.com (repo.anaconda.com)... <IP_ADDRESS>, <IP_ADDRESS>, 2606:4700::6810:8203, ...
Connecting to repo.anaconda.com (repo.anaconda.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 103219356 (98M) [application/x-sh]
Saving to: ‘/home/landon/miniconda3/miniconda.sh’

/home/landon/minico 100%[===================>]  98.44M  93.0MB/s    in 1.1s
2023-09-02 09:13:57 (93.0 MB/s) - ‘/home/landon/miniconda3/miniconda.sh’ saved [103219356/103219356]

bash /home/landon/miniconda3/miniconda.sh -b -u -p /home/landon/miniconda3
PREFIX=/home/landon/miniconda3
Unpacking payload ...

Installing base environment...
Downloading and Extracting Packages
Preparing transaction: done
Executing transaction: done
installation finished.

rm -rf /home/landon/miniconda3/miniconda.sh
/home/landon/miniconda3/bin/conda init bash
no change     /home/landon/miniconda3/condabin/conda
no change     /home/landon/miniconda3/bin/conda
no change     /home/landon/miniconda3/bin/conda-env
no change     /home/landon/miniconda3/bin/activate
no change     /home/landon/miniconda3/bin/deactivate
no change     /home/landon/miniconda3/etc/profile.d/conda.sh
no change     /home/landon/miniconda3/etc/fish/conf.d/conda.fish
no change     /home/landon/miniconda3/shell/condabin/Conda.psm1
no change     /home/landon/miniconda3/shell/condabin/conda-hook.ps1
no change     /home/landon/miniconda3/lib/python3.11/site-packages/xontrib/conda.xsh
no change     /home/landon/miniconda3/etc/profile.d/conda.csh
no change     /home/landon/.bashrc
No action taken.
/home/landon/miniconda3/bin/conda init zsh
no change     /home/landon/miniconda3/condabin/conda
no change     /home/landon/miniconda3/bin/conda
no change     /home/landon/miniconda3/bin/conda-env
no change     /home/landon/miniconda3/bin/activate
no change     /home/landon/miniconda3/bin/deactivate
no change     /home/landon/miniconda3/etc/profile.d/conda.sh
no change     /home/landon/miniconda3/etc/fish/conf.d/conda.fish
no change     /home/landon/miniconda3/shell/condabin/Conda.psm1
no change     /home/landon/miniconda3/shell/condabin/conda-hook.ps1
no change     /home/landon/miniconda3/lib/python3.11/site-packages/xontrib/conda.xsh
no change     /home/landon/miniconda3/etc/profile.d/conda.csh
no change     /home/landon/.zshrc
No action taken.
landon@landon:~/Desktop/gitRepos/CyberBattleSim$ ls
CODE_OF_CONDUCT.md  cyberbattle  docs     init.ps1  install-conda.sh  notebooks           README.md             requirements.txt  SECURITY.md setup.py
createstubs.sh      Dockerfile   env.yml  init.sh   LICENSE           pyrightconfig.json  requirements.dev.txt  scripts           setup.cfg    SUPPORT.md
landon@landon:~/Desktop/gitRepos/CyberBattleSim$ bash init.sh
++ dirname init.sh
pushd .
~/Desktop/gitRepos/CyberBattleSim ~/Desktop/gitRepos/CyberBattleSim
conda info --envs

conda environments:

base                     /home/landon/miniconda3
esp                      /home/landon/miniconda3/envs/esp
nvdl                     /home/landon/miniconda3/envs/nvdl
++ conda shell.bash hook

eval 'export CONDA_EXE='''/home/landon/miniconda3/bin/conda'''
export _CE_M=''''''
export _CE_CONDA=''''''
export CONDA_PYTHON_EXE='''/home/landon/miniconda3/bin/python'''

Copyright (C) 2012 Anaconda, Inc
SPDX-License-Identifier: BSD-3-Clause
__conda_exe() (
"$CONDA_EXE" $_CE_M $_CE_CONDA "$@"
)
__conda_hashr() {
if [ -n "${ZSH_VERSION:+x}" ]; then
\rehash
elif [ -n "${POSH_VERSION:+x}" ]; then
:  # pass
else
\hash -r
fi
}
__conda_activate() {
if [ -n "${CONDA_PS1_BACKUP:+x}" ]; then
# Handle transition from shell activated with conda <= 4.3 to a subsequent activation
# after conda updated to >= 4.4. See issue #6173.
PS1="$CONDA_PS1_BACKUP"
\unset CONDA_PS1_BACKUP
fi
\local ask_conda
ask_conda="$(PS1="${PS1:-}" __conda_exe shell.posix "$@")" || \return
\eval "$ask_conda"
__conda_hashr
}
__conda_reactivate() {
\local ask_conda
ask_conda="$(PS1="${PS1:-}" __conda_exe shell.posix reactivate)" || \return
\eval "$ask_conda"
__conda_hashr
}
conda() {
\local cmd="${1-missing}"
case "$cmd" in
activate|deactivate)
__conda_activate "$@"
;;
install|update|upgrade|remove|uninstall)
__conda_exe "$@" || \return
__conda_reactivate
;;
*)
__conda_exe "$@"
;;
esac
}
if [ -z "${CONDA_SHLVL+x}" ]; then
\export CONDA_SHLVL=0
# In dev-mode CONDA_EXE is python.exe and on Windows
# it is in a different relative location to condabin.
if [ -n "${_CE_CONDA:+x}" ] && [ -n "${WINDIR+x}" ]; then
PATH="$(\dirname "$CONDA_EXE")/condabin${PATH:+":${PATH}"}"
else
PATH="$(\dirname "$(\dirname "$CONDA_EXE")")/condabin${PATH:+":${PATH}"}"
fi
\export PATH
# We'\''re not allowing PS1 to be unbound. It must at least be set.
# However, we'\''re not exporting it, which can cause problems when starting a second shell
# via a first shell (i.e. starting zsh from bash).
if [ -z "${PS1+x}" ]; then
    PS1=
fi

fi'
++ export CONDA_EXE=/home/landon/miniconda3/bin/conda
++ CONDA_EXE=/home/landon/miniconda3/bin/conda
++ export _CE_M=
++ _CE_M=
++ export _CE_CONDA=
++ _CE_CONDA=
++ export CONDA_PYTHON_EXE=/home/landon/miniconda3/bin/python
++ CONDA_PYTHON_EXE=/home/landon/miniconda3/bin/python
++ '[' -z x ']'

conda info --envs
local cmd=info
case "$cmd" in
__conda_exe info --envs
grep -q cybersim
/home/landon/miniconda3/bin/conda info --envs
conda env create -f env.yml
local cmd=env
case "$cmd" in
__conda_exe env create -f env.yml
/home/landon/miniconda3/bin/conda env create -f env.yml
Traceback (most recent call last):
File "/home/landon/miniconda3/lib/python3.11/site-packages/requests/compat.py", line 11, in
import chardet
ModuleNotFoundError: No module named 'chardet'

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/landon/miniconda3/bin/conda-env", line 6, in
from conda_env.cli.main import main
File "/home/landon/miniconda3/lib/python3.11/site-packages/conda_env/cli/main.py", line 17, in
from . import main_config, main_create, main_export, main_list, main_remove, main_update
File "/home/landon/miniconda3/lib/python3.11/site-packages/conda_env/cli/main_create.py", line 21, in
from conda.notices import notices
File "/home/landon/miniconda3/lib/python3.11/site-packages/conda/notices/init.py", line 3, in
from .core import notices  # noqa: F401
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/landon/miniconda3/lib/python3.11/site-packages/conda/notices/core.py", line 13, in
from . import cache, fetch, views
File "/home/landon/miniconda3/lib/python3.11/site-packages/conda/notices/fetch.py", line 9, in
import requests
File "/home/landon/miniconda3/lib/python3.11/site-packages/requests/init.py", line 45, in
from .exceptions import RequestsDependencyWarning
File "/home/landon/miniconda3/lib/python3.11/site-packages/requests/exceptions.py", line 9, in
from .compat import JSONDecodeError as CompatJSONDecodeError
File "/home/landon/miniconda3/lib/python3.11/site-packages/requests/compat.py", line 13, in
import charset_normalizer as chardet
ModuleNotFoundError: No module named 'charset_normalizer'

When I run bash init.sh is the issue missing modules.
also the conda environment doesnt get made correctly

@blumu Unrelated to this issue I did get this to work with another method on 20.04 without conda. I was attempting to make a tree and star pattern topology. The readme says use cyberbattlechain as a starting point for different topologies, Do you guys just mean longer chains of Linux Windows Linux[Flag]. Or can I break from that pattern and make the tree and start pattern?

I did create the graph using simpleenv, but I wasnt sure how to run the agent on that or specify which is my flag.

No, I did not try that. Also I've destroyed that VM since Im not working with CyberBattleSim anymore, but I believe it was 22.04. That's usually what I use.

Thank you @beauxrel for your answer and past contributions to CyberBattleSim! I am closing this issue for now as I could not repro on WSL2 nor docker with the most recent main branch.


Visual Intensity 2-5 missing

Maybe they are trackloaders? Must investigate 😊

Visual Intensity #2 is NDOS.


Getting this backing off problem when I use COPRO

Hi no matter which API I use, groq or OpenAI I get this message repeatedly, backing off after x tries
For groq

From OpenAI using gpt 4o

What does this error precisely mean and anyway to mitigate this?

Hi @ArslanS1997 ,
Try reducing the number of threads so COPRO doesn’t make too many requests simultaneously. This should help avoid triggering the rate limit.