Synthesis failed for automl

Hello! Autosynth couldn't regenerate automl. :broken_heart:
Here's the output from running synth.py:
11 autosynth [DEBUG] > Running: git checkout f7702e0178fa2aef3cc3149cb1ea51453e7c4181
Note: checking out 'f7702e0178fa2aef3cc3149cb1ea51453e7c4181'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at f7702e01 chore: update with latest version of protobuf (#3710)
2021-02-03 03:08:24,537 autosynth [DEBUG] > Running: git checkout f694606e3e34d0e2a289d655864e225cab9ecb88
Note: checking out 'f694606e3e34d0e2a289d655864e225cab9ecb88'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at f694606e chore(profiler): Set proto namespace to google.cloud
2021-02-03 03:08:24,554 autosynth [DEBUG] > Running: git branch -f autosynth-automl-29
2021-02-03 03:08:24,558 autosynth [DEBUG] > Running: git checkout autosynth-automl-29
Switched to branch 'autosynth-automl-29'
2021-02-03 03:08:24,584 autosynth [INFO] > Running synthtool
2021-02-03 03:08:24,585 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2021-02-03 03:08:24,585 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/AutoMl/29/sponge_log.log
2021-02-03 03:08:24,587 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata synth.metadata synth.py --
2021-02-03 03:08:24,820 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/google-cloud-php/AutoMl/synth.py.
On branch autosynth-automl-29
nothing to commit, working tree clean
2021-02-03 03:08:24,988 synthtool [DEBUG] > Ensuring dependencies.
DEBUG:synthtool:Ensuring dependencies.
2021-02-03 03:08:24,998 synthtool [DEBUG] > Cloning googleapis.
DEBUG:synthtool:Cloning googleapis.
2021-02-03 03:08:24,999 synthtool [DEBUG] > Using precloned repo /home/kbuilder/.cache/synthtool/googleapis
DEBUG:synthtool:Using precloned repo /home/kbuilder/.cache/synthtool/googleapis
2021-02-03 03:08:25,003 synthtool [DEBUG] > Which version of bazel will I run?
DEBUG:synthtool:Which version of bazel will I run?
bazel 3.0.0
2021-02-03 03:08:25,006 synthtool [DEBUG] > Generating code for: //google/cloud/automl/v1beta1:google-cloud-automl-v1beta1-php.
DEBUG:synthtool:Generating code for: //google/cloud/automl/v1beta1:google-cloud-automl-v1beta1-php.
2021-02-03 03:08:25,208 synthtool [ERROR] > Failed executing bazel --max_idle_secs=240 build //google/cloud/automl/v1beta1:google-cloud-automl-v1beta1-php:

Loading:
Loading: 0 packages loaded
INFO: Call stack for the definition of repository 'com_google_api_codegen' which is a http_archive (rule definition at /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/bazel_tools/tools/build_defs/repo/http.bzl:296:16):
 - <builtin>
 - /home/kbuilder/.cache/synthtool/googleapis/WORKSPACE:77:1
WARNING: Download from https://github.com/googleapis/gapic-generator/archive/v2.10.4.zip failed: class com.google.devtools.build.lib.bazel.repository.downloader.UnrecoverableHttpException GET returned 404 Not Found
ERROR: An error occurred during the fetch of repository 'com_google_api_codegen':
   java.io.IOException: Error downloading [https://github.com/googleapis/gapic-generator/archive/v2.10.4.zip] to /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/com_google_api_codegen/v2.10.4.zip: GET returned 404 Not Found
ERROR: no such package '@com_google_api_codegen//': java.io.IOException: Error downloading [https://github.com/googleapis/gapic-generator/archive/v2.10.4.zip] to /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/com_google_api_codegen/v2.10.4.zip: GET returned 404 Not Found
INFO: Elapsed time: 0.191s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)
FAILED: Build did NOT complete successfully (0 packages loaded)

ERROR:synthtool:Failed executing bazel --max_idle_secs=240 build //google/cloud/automl/v1beta1:google-cloud-automl-v1beta1-php:

Loading:
Loading: 0 packages loaded
INFO: Call stack for the definition of repository 'com_google_api_codegen' which is a http_archive (rule definition at /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/bazel_tools/tools/build_defs/repo/http.bzl:296:16):
 - <builtin>
 - /home/kbuilder/.cache/synthtool/googleapis/WORKSPACE:77:1
WARNING: Download from https://github.com/googleapis/gapic-generator/archive/v2.10.4.zip failed: class com.google.devtools.build.lib.bazel.repository.downloader.UnrecoverableHttpException GET returned 404 Not Found
ERROR: An error occurred during the fetch of repository 'com_google_api_codegen':
   java.io.IOException: Error downloading [https://github.com/googleapis/gapic-generator/archive/v2.10.4.zip] to /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/com_google_api_codegen/v2.10.4.zip: GET returned 404 Not Found
ERROR: no such package '@com_google_api_codegen//': java.io.IOException: Error downloading [https://github.com/googleapis/gapic-generator/archive/v2.10.4.zip] to /home/kbuilder/.cache/bazel/_bazel_kbuilder/a732f932c2cbeb7e37e1543f189a2a73/external/com_google_api_codegen/v2.10.4.zip: GET returned 404 Not Found
INFO: Elapsed time: 0.191s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)
FAILED: Build did NOT complete successfully (0 packages loaded)

Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/home/kbuilder/.cache/synthtool/google-cloud-php/AutoMl/synth.py", line 33, in <module>
    bazel_target=f'//google/cloud/automl/{lower_version}:google-cloud-automl-{lower_version}-php',
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 64, in php_library
    return self._generate_code(service, version, "php", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 197, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', '--max_idle_secs=240', 'build', '//google/cloud/automl/v1beta1:google-cloud-automl-v1beta1-php']' returned non-zero exit status 1.
2021-02-03 03:08:25,258 autosynth [ERROR] > Synthesis failed
2021-02-03 03:08:25,259 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at f7702e01 chore: update with latest version of protobuf (#3710)
2021-02-03 03:08:25,302 autosynth [DEBUG] > Running: git checkout autosynth-automl
Switched to branch 'autosynth-automl'
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 334, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 65, in synthesize_loop
    has_changes = toolbox.synthesize_version_in_new_branch(synthesizer, youngest)
  File "/tmpfs/src/github/synthtool/autosynth/synth_toolbox.py", line 259, in synthesize_version_in_new_branch
    synthesizer.synthesize(synth_log_path, self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


sourcehut.coresrht: imcompatible with python3Packages.jinja2 3.1+

Describe the bug
Steps To Reproduce
Enable any SourceHut service, it will crash pointing to some failed import from jinja2.
Expected behavior
Services up and running.
Additional context
Upstream has fixed this: https://git.sr.ht/~sircmpwn/core.sr.ht/commit/46791bf5ebc722d348ff47b0d106932c6f5f9e1c
Therefore upgrading SourceHut packages should fix the crash.  I am trying to but newer versions seems to have different build input requirements, didn't get them to build so far.  Someone more experienced with nix might be able to do this better.
Notify maintainers
@ju1m
Metadata

system: "x86_64-linux"
host os: Linux <IP_ADDRESS>-livepatched, NixOS, 22.05 (Quokka), 22.05pre377574.fb222e00868
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.8.0
channels(root): "nixos"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Fixed by GH-173678.


[MINOR] Remove stdout and stderr

What is this PR for?
Change system.out and system.err into logger.info
What type of PR is it?
[Improvement]
Todos

[x] - Fixed to remove system.out and system.err

What is the Jira issue?
This is very trivial and minor issue
How should this be tested?
Check your logs/zeppelin*.out to see "------ Create new SparkContext ..."
Apply this patch
Check your logs/zeppelin*.log to see "------ Create new SparkContext ..."
Screenshots (if appropriate)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

The failure is irrelative.
[ERROR] npm ERR! shasum check failed for /tmp/npm-9826-4ecc065c/registry.npmjs.org/multiparty/-/multiparty-2.2.0.tgz
[ERROR] npm ERR! Expected: a567c2af000ad22dc8f2a653d91978ae1f5316f4
[ERROR] npm ERR! Actual:   774ba609dc52b6137bb5faa41ce9b72d851ffb38
[ERROR] npm ERR! From:     https://registry.npmjs.org/multiparty/-/multiparty-2.2.0.tgz

[ERROR] npm ERR! shasum check failed for /tmp/npm-9821-09fbabd5/registry.npmjs.org/socket.io-client/-/socket.io-client-0.9.16.tgz
[ERROR] npm ERR! Expected: 4da7515c5e773041d1b423970415bcc430f35fc6
[ERROR] npm ERR! Actual:   417d664394ed5a959deea7a56bc9993d94289ecb
[ERROR] npm ERR! From:     https://registry.npmjs.org/socket.io-client/-/socket.io-client-0.9.16.tgz

LGTM

Merging if there's no more discussion.


UEx workshop #3 on corporate managed cloud services model

Describe the issue
Book and conduct UEx workshop with next ministry (probably SDPR), compile findings
Which Sprint Priority is this issue related to?
Alpha Service Delivery Model Blueprint
Community Engagement
Additional context
Initial email invitations have been sent out - need to follow up with each recipient to schedule and conduct the workshops: SDPR, Justice, Health, Transport, Education
Definition of done
UEx workshop completed and results compiled into a report on findings so far.

Another very informative discussion (Thu, July 8) - particularly good input from Business Owner/Product Owner.


Provide a way how to link plans from plans

Seems a very basic scenario we should support is to be able to link another L2 plan for easy inclusion of plan from other component.

Duplicate of #975, filed earlier but the new issue has a more detailed description.


Don't snap back to 'nearby' list when resolving location, if user manual navigation is in progress

When a user first lands on the map, yourpeer will try to locate them. If they are sharing their location it will center on their location and order services by 'nearby' as the default.
If the user has started searching the map before their location has been applied, they are being interrupted and pulled back to their location and the newly sorted list.
We don't want to interrupt their exploration and should only apply the 'nearby' list order view when they return to the list view.
Current behavior
https://github.com/user-attachments/assets/f4780da9-a665-420f-ac09-135d7e69e308

This is confirmed.


[BUG] The rancher-monitoring Pod stuck at terminating status when upgrading from v1.1.2 to v1.2.0-rc6

Describe the bug

This is a tracking issue to the upstream one: kubernetes/kubernetes#116847
Basically, we found that it is possible to hit the issue when doing Harvester upgrades. The upgrade stuck in the apply-manifests phase.

Take a deeper look into the apply-manifests Pod's log, it is waiting for all the monitoring-related Pods to terminate:
$ kubectl -n harvester-system logs hvst-upgrade-md6wr-apply-manifests-wqslg --tail=10
Tue Sep  5 10:20:39 UTC 2023
there are still 1 pods in cattle-monitoring-system to be deleted
Tue Sep  5 10:20:45 UTC 2023
there are still 1 pods in cattle-monitoring-system to be deleted
Tue Sep  5 10:20:50 UTC 2023
there are still 1 pods in cattle-monitoring-system to be deleted
Tue Sep  5 10:20:55 UTC 2023
there are still 1 pods in cattle-monitoring-system to be deleted
Tue Sep  5 10:21:00 UTC 2023
there are still 1 pods in cattle-monitoring-system to be deleted

The part of the script is doing a conversion that converts the rancher-monitoring ManagedChart to an Addon. After deleting the ManagedChart, it waits for all the dependents disappear before executing the conversion.
But one of the Pod is stuck in a terminating state, which is prometheus-rancher-monitoring-prometheus-0:
$ kubectl -n cattle-monitoring-system get pods
NAME                                         READY   STATUS        RESTARTS   AGE
prometheus-rancher-monitoring-prometheus-0   0/3     Terminating   0          19d

$ kubectl -n cattle-monitoring-system get pod prometheus-rancher-monitoring-prometheus-0 -o jsonpath='{.metadata.uid}'
33f43165-6faa-4648-927d-69097901471c

Using the Pod's UID 33f43165-6faa-4648-927d-69097901471c to search the kubelet's log in /var/lib/rancher/rke2/agent/logs/kubelet.log:
E0905 10:26:18.769199   17399 reconciler.go:208] "operationExecutor.UnmountVolume failed (controllerAttachDetachEnabled true) for volume \"pvc-7781c988-c35b-4cf8-89e6-f2907ef33603\" (UniqueName: \"kubernetes.io/csi/driver.longhorn.io^pvc-7781c988-c35b-4cf8-89e6-f2907ef33603\") pod \"33f43165-6faa-4648-927d-69097901471c\" (UID: \"33f43165-6faa-4648-927d-69097901471c\") : UnmountVolume.NewUnmounter failed for volume \"pvc-7781c988-c35b-4cf8-89e6-f2907ef33603\" (UniqueName: \"kubernetes.io/csi/driver.longhorn.io^pvc-7781c988-c35b-4cf8-89e6-f2907ef33603\") pod \"33f43165-6faa-4648-927d-69097901471c\" (UID: \"33f43165-6faa-4648-927d-69097901471c\") : kubernetes.io/csi: unmounter failed to load volume data file [/var/lib/kubelet/pods/33f43165-6faa-4648-927d-69097901471c/volumes/kubernetes.io~csi/pvc-7781c988-c35b-4cf8-89e6-f2907ef33603/mount]: kubernetes.io/csi: failed to open volume data file [/var/lib/kubelet/pods/33f43165-6faa-4648-927d-69097901471c/volumes/kubernetes.io~csi/pvc-7781c988-c35b-4cf8-89e6-f2907ef33603/vol_data.json]: open /var/lib/kubelet/pods/33f43165-6faa-4648-927d-69097901471c/volumes/kubernetes.io~csi/pvc-7781c988-c35b-4cf8-89e6-f2907ef33603/vol_data.json: no such file or directory" err="UnmountVolume.NewUnmounter failed for volume \"pvc-7781c988-c35b-4cf8-89e6-f2907ef33603\" (UniqueName: \"kubernetes.io/csi/driver.longhorn.io^pvc-7781c988-c35b-4cf8-89e6-f2907ef33603\") pod \"33f43165-6faa-4648-927d-69097901471c\" (UID: \"33f43165-6faa-4648-927d-69097901471c\") : kubernetes.io/csi: unmounter failed to load volume data file [/var/lib/kubelet/pods/33f43165-6faa-4648-927d-69097901471c/volumes/kubernetes.io~csi/pvc-7781c988-c35b-4cf8-89e6-f2907ef33603/mount]: kubernetes.io/csi: failed to open volume data file [/var/lib/kubelet/pods/33f43165-6faa-4648-927d-69097901471c/volumes/kubernetes.io~csi/pvc-7781c988-c35b-4cf8-89e6-f2907ef33603/vol_data.json]: open /var/lib/kubelet/pods/33f43165-6faa-4648-927d-69097901471c/volumes/kubernetes.io~csi/pvc-7781c988-c35b-4cf8-89e6-f2907ef33603/vol_data.json: no such file or directory"

There are plenty lines of identical log indicating the same thing: the kubelet cannot unmount the volume used by the prometheus Pod because the vol_data.json file is missing.
To Reproduce
According to the upstream ticket, it cannot be reproduced reliably (in fact, almost not reproducible), probably caused by some peculiar race conditions.
Expected behavior

The volume should be unmounted correctly and the upgrade should be done successfully.
Support bundle

Environment

Harvester ISO version: upgrading from v1.1.2 to v1.2.0-rc6
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): VMs provisioned using ipxe-examples (air-gapped setup)

Additional context
Add any other context about the problem here.
Other related issues and previous fixes:

longhorn/longhorn#5765
kubernetes/kubernetes#116847
kubernetes/kubernetes#120086

The workaround is to find out the stucking Pod and forcibly delete it.
$ kubectl get pods -n cattle-monitoring-system
NAME                                         READY   STATUS        RESTARTS   AGE
prometheus-rancher-monitoring-prometheus-0   0/3     Terminating   0          19d

$ kubectl delete pod prometheus-rancher-monitoring-prometheus-0 -n cattle-monitoring-system  --force

Thanks to @bk201 for providing the information!

The workaround is to find out the stucking Pod and forcibly delete it.
$ kubectl get pods -n cattle-monitoring-system
NAME                                         READY   STATUS        RESTARTS   AGE
prometheus-rancher-monitoring-prometheus-0   0/3     Terminating   0          19d

$ kubectl delete pod prometheus-rancher-monitoring-prometheus-0 -n cattle-monitoring-system  --force

Thanks to @bk201 for providing the information!

Thanks for the workaround @bk201 @starbops :smile: :+1:   - this seems that this may need to be done multiple times before the upgrade can proceed - it does look to be working now after 2-3 times of forcefully deleting the prometheus pods and letting them be re-created.

When upgrading to v1.2.0/v1.2.1, the old rancher-monitoring and rancher-logging managedchart are deleted, and then two same naming objects of type addons.harvesterhci.io are created.  PR: https://github.com/harvester/harvester/pull/3380
But the deleting of managedchart seems not working fully as expected, a short summary of related phenomenon: https://github.com/harvester/harvester/issues/4488#issuecomment-1838904523
The workaround is booked: https://docs.harvesterhci.io/v1.2/upgrade/v1-1-2-to-v1-2-0#6-an-upgrade-is-stuck-in-the-upgrading-system-service-state

The path (replacing a management chart with an RKE2 HelmChart) doesn't exist in recent versions, users are not supposed to hit this.


Create an esy branch with an esy.json and no vendored directories

This might be a good way to reconcile Dream, Piaf, and the rest of the "ecosystem" for esy users.
The branch can probably be maintained by constantly cherry-picking a single commit that adds esy.json and subtracts src/vendor. This could even be done in CI in the long term, but probably we'd rather get rid of src/vendor by actually upstreaming or releasing the protocol projects, instead.
cc @anmonteiro @EduardoRFS for interest.

I wonder if removing the dune file at src/vendor would be enough to use the installed version by esy. It could also be an opam file with an additional rm src/vendor/dune

Actually, it's probably the opposite. We need that file (atm) because it renames all the libraries so that Dream sees them under different names under the dream package. So we actually wouldn't be able to trivially depend on these packages from esy, because the rest of Dream expects these packages to have dream. names. However, I don't think that's a big deal, since probably only dream.http refers to the vendored code, and we can just include a patch for it in the one commit that will be cherry-picked.

At first glance, it seems easiest to just delete the whole vendor directory, patch src/http/dune, and add an esy manifest. I don't think an opam manifest will work, at least not when it's interpreted by opam, because we'd need to depend on exact commits of these projects. AFAIK opam can do that only with pin-depends, and that only works for direct "development" installs of the using project (Dream). Does esy handle that differently with an opam manifest? If not, it seems we have to use an esy.json.

I created and pushed the esy branch to at least serve as a PR target.
About the good first issue label: if opening a PR to esy, set the base of the PR to the branch in the GitHub UI:

On my side, I mostly aware about the initial diff/reason of the httpaf fork and I really would like to have only one httpaf instead of many and only trust into opam-repository. I'm currently aware about the initial diff but it seems that the "first" httpaf is still maintained (and it had several bug fixes - not sure they are incorporate into anmonteiro/httpaf) and some solutions exist about missed features.
Note that it's not about the usage of esy or opam but about which repository of the eco-system we trust.
Then, such situation burns many energies when, for the MirageOS support, I need to fork my own project (paf) to apply a minor patch due to incompatible interfaces. I'm a bit sad with such situation when it requires a certain amount of maintenability and energy (which I have less and less).
PS: I don't want to bring any trouble and if you don't agree with such view, it's fine but I really think that we should be more convergent in the eyes of "all" communities.

@dinosaure This issue doesn't make Dream diverge any more on http/af, etc., than it already has — it's only about using separate repos for code that is already vendored into Dream, which is possible on esy.
I fully agree with the intent to eventually resolve the forks, and to get everything released into opam.
To my knowledge so far, as of a few months ago, the "main" http/af lacks:

HTTPS support.
A runtime that is capable of handling protocol upgrades (I am hazy now, but I don't think it can do WebSocket upgrades out of the box).
A shared runtime with that can do ALPN to select an HTTP/2 server instead of http/af.

Given that Dream wants to support all of those things, it seems that it has to use the forks. It already is doing that. This issue just improves some situations for esy users.
cc @anmonteiro @seliopou

@dinosaure This issue doesn't make Dream diverge any more on http/af, etc., than it already has — it's only about using separate repos for code that is already vendored into Dream, which is possible on esy.

I agree with the current layout of dream which includes projects with (small?) divergences. However, if you take the perspective of opam-repository, the dream.httpaf is, by essence (and it's why you must include it as a part of dream), different to the "real" httpaf.
If you want to provide something for httpaf and dream according to the current state of opam-repository (as I try to do for paf), you must do a choice about which httpaf you want to use because both diverges (and not only on the implementation). It's why I said:

I need to fork my own project (paf) to apply a minor patch due to incompatible interfaces.

Just to be able to plug it with dream and the httpaf available on opam-repository. Of course, such case is more low-level than an usual Dream user but it's a fork and it has a cost. Then, it seems easy with esy to over-write an existing project by an other but as far as I can tell, it's not the politic of opam-repository (at least, pin-depends exists but it's only for a development purpose). These questions are of course outside of the scope of dream and it's more about different visions from esy and opam but we should consider them where MirageOS mainly use opam.
Then, about HTTP/AF support, the only missing feature is the upgrade (but some PRs exist to implement it, they just need some fuel).
Currently, the HTTPS support (even for CoHTTP) is not strictly handled by the project (or the core) itself but by something outside. In the case of dream, HTTPS is handled by gluten instead of httpaf/h2. And, in the case of MirageOS, it's handled by paf. I would not like to say that httpaf does not handle HTTPS, it can and only a piece into the distribution is missing - but it exists outside with paf or gluten.
Then, about ALPN which is intrinsic with HTTPS, the problem is the same. paf supports ALPN and can switch to h2 if the client support that. And of course, gluten does that too.
So I really think that a solution can exist with some effort (of course) about the connection upgrade. And, on this subject, you can view: inhabitedtype/httpaf#159 and inhabitedtype/httpaf#203
My mainly point is to be sync with opam-repository instead of to use some forks - even if it's working on esy without pain, it requires some plumbing into opam and assert an incompatibility into an eco-system which requires to do a choice between httpaf from @anmonteiro or httpaf from @seliopou. And, from the opam-repository perspective, @seliopou is the owner of httpaf.

My mainly point is to be sync with opam-repository instead of to use some forks

We already agree on the main point. The question is, can we get all of

HTTPS support.
A runtime that is capable of handling protocol upgrades (I am hazy now, but I don't think it can do WebSocket upgrades out of the box).
A shared runtime with that can do ALPN to select an HTTP/2 server instead of http/af.

If not, then we can't use the opam-repository http/af for now. From your message, it seems that WebSocket upgrades are the last thing missing. Can you confirm?
This isn't the point of this issue, however. Please open a new issue to discuss that. We are already using forks and that's not going to change by creating an esy branch. It will just be a temporary convenience for esy users.

If not, then we can't use the opam-repository http/af for now. From your message, it seems that WebSocket upgrades are the last thing missing. Can you confirm?

Yes, I can confirm. On my side with paf, we handle TLS with ocaml-tls and ALPN.

This isn't the point of this issue, however. Please open a new issue to discuss that. We are already using forks and that's not going to change by creating an esy branch. It will just be a temporary convenience for esy users.

Thanks, I will make an issue when I finish my MirageOS support :+1:.

I've since first renamed the vendored libraries, and now replaced them with depending on httpun in #351. I think this issue is likely obsolete.


Can't get it working on Ubuntu 18.04

::::            Self check               ::::
:: [OK] IP forwarding is enabled
:: [OK] Iptables MASQUERADE rule set
:: [ERR] WireGuard is not running, try to start now? [Y/n]
Job for<EMAIL_ADDRESS>failed because the control process exited with error code.
See "systemctl status<EMAIL_ADDRESS>and "journalctl -xe" for details.
Done
:: [OK] WireGuard is enabled (it will automatically start on reboot)
:: [ERR] WireGuard is not listening, try to restart now? [Y/n] y
Job for<EMAIL_ADDRESS>failed because the control process exited with error code.
See "systemctl status<EMAIL_ADDRESS>and "journalctl -xe" for details.
Done
Not sure what is going on. I've tried multiple installations. Any ideas?

Installing Ubuntu updates seems to have worked. Going to close this and reopen it later if it happens again.


Delay in client-initiated abort for event stream request

This issue was part of #1103 (see Issue 1), but has been moved to a different issue report to improve trackability. I have tested this on tag 1.0.0, rel/1.0.1 and 3104110 (the commit after #1103 has been marked as completed)
Say I have a controller that sends a 'text/event-stream' response, which writes (Response.WriteAsync()) a string every second. When the client aborts the request (like clicking on the 'Stop' button in chrome), the request in the controller should be aborted immediately. This means that HttpContext.RequestAborted should be set to cancelled immediately. This however doesn't happen. There always seems to be a delay of a couple of WriteAsync() calls
In the sample below, 2 things get written to the console: Starting response {i} and Ended response {i}. Now, when I fire the request and immediately abort the request from the browser, the console has the following output:
info: Microsoft.AspNetCore.Hosting.Internal.WebHost[1]
Request starting HTTP/1.1 GET http://localhost:5000/
Started response 1 of 20
Ended response 1 of 20
Started response 2 of 20
Ended response 2 of 20
Started response 3 of 20
info: Microsoft.AspNetCore.Server.Kestrel[14]
Connection id "0HKV17V8EGG77" communication error
Microsoft.AspNetCore.Server.Kestrel.Internal.Networking.UvException: Error -4081 ECANCELED operation canceled
info: Microsoft.AspNetCore.Hosting.Internal.WebHost[2]
Request finished in 2133.1317ms 200 text/event-stream

The cancellation isn't noticed until the start of the 3rd loop. This always happens and has no connection to the Task.Delay() value, because a delay of 1000 ms and 10.000 ms produce the same result.
After some research it seems the delay comes all the way from libuv.
For every WriteAsync() call in the sample, libuv calls back to UvWriteCb() in UvWriteReq.cs, with a pointer to the request (UvWriteReq) and a status code describing how the write has been handled. Only after the 3rd WriteAsync() call libuv reports status code -4081 (ECANCELED), which immediately triggers the abort flow in Kestrel.
On a side-note: this also happens with other content-types, but I've used a text/event-stream type in this issue as a most likely use-case.
Sample code:
using System;
using System.Threading.Tasks;
using Microsoft.AspNetCore.Builder;
using Microsoft.AspNetCore.Hosting;
using Microsoft.AspNetCore.Http;
using Microsoft.Extensions.Logging;

namespace SampleApp
{
    public class Startup
    {
        public static void Main(string[] args)
        {
            new WebHostBuilder().UseKestrel().UseUrls("http://localhost:5000").UseStartup<Startup>().Build().Run();
        }

        public void Configure(IApplicationBuilder app, ILoggerFactory loggerFactory)
        {
            loggerFactory.AddConsole(LogLevel.Information);
            app.Run(async ctx =>
            {
                ctx.Response.Headers.Add("Content-Type", "text/event-stream");
                var ct = ctx.RequestAborted;
                for (int i = 0; i < 20; i++)
                {
                    Console.WriteLine($"Started response {i + 1} of 20");
                    try
                    {
                        await Task.Delay(1000, ct);
                        await ctx.Response.WriteAsync($"data: Hello ({DateTime.Now})\r\r");
                    }
                    catch (TaskCanceledException)
                    {
                        break;
                    }
                    Console.WriteLine($"Ended response {i + 1} of 20");
                }
            });
        }
    }
}

If you trace the TCP session do you see the browser close the connection first with a FIN or RST?
/cc @davidfowl

This is the same problem, it's probably a FIN

@davidfowl Yeah, you're right.
FIN, ACK, followed by RST, ACK.

@muratg Can this issue be added to the 1.1.0-preview1 milestone like its predecessor #1103 was? I ask because anyone trying to use the JavaScriptServices-based templates will not be able to use HTTPS in development mode until this is fixed.

@SteveSandersonMS preview1 will be closed soon, tentatively adding it to this milestone. If not, we'll look into it at 1.1.0.

@halter73 Is fixing this issue the only way that the ObjectDisposedException on HTTPS connections is going to be fixed, or could the ObjectDisposedException be fixed in some simpler way? Just asking because the delayed-abort-notification issue is much less important than the ObjectDisposedException from the point of view of integrating with Webpack dev middleware.

@SteveSandersonMS The ObjectDisposedException was fixed in https://github.com/aspnet/KestrelHttpServer/pull/1127.

It would be good to test a few different clients to ensure we're not regressing any clients.
We also need to check IIS static file handler behavior too (does it kill the response upon receiving a FIN?).
@cesarbs will be doing a bit more investigation before we decide if this is in 1.1 or 1.2.

As discussed, I tested IIS with a client that requests a large file and immediately sends a FIN. IIS still sends the entire file.
It's hard to come across HTTP/1.0 clients, but I did check curl and it waits for a FIN from the server before sending it's own.
I think the best approach to this would be to provide a separate token, as suggested by @halter73.

Or we change static files to behave like IIS? It doesn't actually need the RequestAborted token, it just needs an active token so that WriteAsync will throw for send failures, correct? If that's the case it can create its own CTS.

So we trip the token on FIN and change StaticFiles to not break? I don't know, the behavior seems weird to me. Why trip a "request aborted" token just because the client sent a FIN? Unless we rename the token.

Because there's precedence for it. That's how IIS and ASP.NET 4 behave, and we we know there are existing clients that implement aborts that way, including our own .NET 4.5 HttpClient. Even Kestrel favors sending FINs over RSTs.

Can you point me to the docs on that? If we're going to do that I'd like to at least change the token's name. It seems super confusing that a "request aborted" token gets tripped just because the client signaled its done sending the request. Something like "client disconnected" would better reflect this behavior.
The problem of course is that that would break the API. Could we add a proxy property to the token with the new name?

We can't change the name and I doubt this will break anyone 😄. We can fix static files as @Tratcher said. We could add another feature interface but that might be overkill here.

We realized yesterday that the static files change won't work, it still requires the token to be cancelled.
The missing piece of this discussion is that we have failed to prove even one client would be broken if we changed this behavior (e.g. are there any that preemptively send a FIN?).  What we do know is that there are many clients broken without it.
http://stackoverflow.com/questions/39574061/httprequest-not-aborted-cancelled-on-browser-abort-in-asp-net-core-mvc

There's an interesting discussion on this topic here: https://lists.w3.org/Archives/Public/ietf-http-wg-old/2001JanApr/0036.html
I'm still reading through it. Also reading Section 6 of RFC 7230 to see if it says anything at all about this (the discussion linked above predates the updated RFC).

Additional task: verify the behavior of the same FIN abort scenario when Kestrel is running behind IIS+ANCM.

@Tratcher IIS does not foward the client FIN to Kestrel.

nginx truncates the response if it received an eager FIN from the client.

@cesarbs But nginx does immediately forward it right?

@NinoFloris Yes. Here's a network trace:

nginx is listening on port 8080, Kestrel on 5000. The browser is using port 5310 to connect to nginx and nginx is using port 5311 to connect to Kestrel.


igrep: 0.2.0 -> 0.5.0

Description of changes
upstream update
Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

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

1 package built:

igrep

Tested the binary and looks like a cool tool, nice!

Thank you for the review!
I merged early as I thought no-one would be interested to do a review.
feel free to let me know if you start a review and I'll wait until you are done.
(this time I just relied on borg and my local test on darwin).

No worries, I understand that you did that. All good!

Thanks for the update,
Could you please not self-merge without a review in such a short window (for non-security impacting changes).
I'd like to have a chance to review and approve (maybe 24h).

happy to wait next time!
(it's hard for me to know who is active and who isn't)
I'll remember that you are.


FIX: Handle None return in getTask

Fix error on chronos startup.
This fixes a bug I encountered recently. I had deleted some tasks from the chronos UI and when I bounced chronos, it wouldn't come up. The error in the logs pointed to the culprit here:
java.util.NoSuchElementException: None.get

It looks like code exists to handle the case when jobOption is empty, but we still unconditionally dereference the jobOption.

:+1:


added messages to slashcommands

added messages as it was missing for the context menus
(idk if it'll work )

idea is sound and build passed, thanks gonna merge it


add 2nd github account

Dev Home version
<IP_ADDRESS>
Windows build number
10.0.22621.1702
Other software
OS Build Version: 10.0.22621.1702.amd64fre.ni_release.220506-1250
.NET Version: .NET 6.0.16
Steps to reproduce the bug
add 1st gtthub account.
try to add a 2nd github account
Expected result
be able to have N github accounts
Actual result
the 2nd login fails
Included System Information
CPU: Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz
Physical Memory: 15.77GB (2.94GB free)
Processor Architecture: x64
Included Extensions Information
Extensions:
Microsoft.Windows.DevHome_<IP_ADDRESS>_x64__8wekyb3d8bbwe
Microsoft.Windows.DevHomeGitHubExtension_<IP_ADDRESS>_x64__8wekyb3d8bbwe

Duplicate of #918


Update policy-csp-defender.md

as per the user report #8740 , so i added admx  missing information after clearly cross with on my laptop runs with windows 10  20h2 64bit build no 19042.662 .
From this editing , i struggled few minutes for  formatting the line in correct and where to add those missing lines.
This editing of this article is  too complicated , editing needs too much concentration with dedicated experienced skills,
I knew all the contributors and all Authors , how are spent time to edit this article to make perfect.

#sign-off


Failing test for saving and then loading tokens

This is something that is happening, not quite sure why yet:
Here is the failing property: https://github.com/anchor/oauth2-server/pull/88/files#diff-a4132e7e065562ab33fba5295a0cce89R147
Failures:

  1) Postgres store save then load token
       uncaught exception: ResultError (UnexpectedNull {errSQLType = "varchar", errSQLTableOid = Just (Oid 28910), errSQLField = "client_id", errHaskellType = "ByteString", errMessage = ""}) (after 1 test)
       TokenGrant {grantTokenType = Bearer, grantExpires = 1858-11-17 00:00:00 UTC, grantUsername = Just "nnduqmroqwdjyjzdaeuxvcvaagwxtzrm", grantClientID = Nothing, grantScope = Scope {unScope = fromList ["q"]}}

Are we meant to be able to attempt to create a TokenGrant without a grantClientId?

Do not believe we can actually, looked through the code we only ever error out or return Just

user id can be empty for certain kinds of grant though (because clients can ask fro grants too I think?)

Apart from that one point, rest looks good

Cool, will fix. thanks.

I would say client_id cannot be null. This means, that you have to register a client even if you are just hacking on a project. This is what most big oauth2 deployments go. Github is an exception here, but I like the idea that we know all the clients and can revoke them if necessary.
user_id is a bit trickier. If we want to have service applications common to the whole infrastructure, then this has to be nullable. For every other request however it should contain the user_id.


SLING-3248 - Proposed Improvements to the Tenant Administrative Web Cons...

...ole Plugin

Notify the user of the status of its actions (add/remove tenant)

With the upcoming migration to git this repository will be deleted. If the pull request contains data that should be re-submitted I suggest that you save the changes locally and resubmit them after the migration, which will likely happen on Monday the 9th of October.


[Feature]: Support resolve the modules with hard-links

What problem does this feature solve?
pnpm creates hard links from the global store to the project's node_modules folders.
For example, imagine you have the following directory structure: packages/a and packages/b have the same version of lodash as a dependency. But they are different symlink that points to different files.
.
├── node_modules
│   ├── a -> ../packages/a
├── package.json
├── packages
│   ├── a
│   │   ├── index.ts
│   │   ├── node_modules
│   │   │   ├── b -> ../../b
│   │   │   └── lodash -><EMAIL_ADDRESS>│   │   └── package.json
│   └── b
│       ├── index.ts
│       ├── node_modules
│       │   └── lodash -><EMAIL_ADDRESS>│       ├── package.json
│       ├── pnpm-lock.yaml
│       └── pnpm-workspace.yaml
├── pnpm-lock.yaml
└── pnpm-workspace.yaml

Since two lodash/lodash.js points to different files, both rspack(or oxc internally) and webpack(or enhanced-resolve internally) treat the two files as unrelated. So at build time, two copies of lodash code will be packaged in the output bundle, even if their content is the same.
However, it can be found that in the file system, the two lodash.js point exactly to the same inode node. Which means they are the same file in physical storage.
$ ls -i packages/a/node_modules/lodash/lodash.js
2249211 packages/a/node_modules/lodash/lodash.js

$ ls -i packages/b/node_modules/lodash/lodash.js
2249211 packages/b/node_modules/lodash/lodash.js

To solve the problem, we created a webpack plugin to cache the request:
import fs from 'node:fs'

import type { ResolveRequest, Resolver } from 'enhanced-resolve'

class InodeWebpackPlugin {
  static #source = 'resolved'

  apply(resolver: Resolver) {
    resolver
      .getHook(InodeWebpackPlugin.#source)
      .tapAsync('INodeCachePlugin', (request, _, callback) => {
        if (!request.path) {
          return callback()
        }

        try {
          const { ino } = fs.statSync(request.path)

          const cachedRequest = this.#cache.get(ino)
          if (cachedRequest) {
            // Note that the query may change for the same path
            // with a different query.
            Object.assign(request, { ...cachedRequest, query: request.query })
            return callback()
          }

          this.#cache.set(ino, request)
        } catch {
          // explicitly ignore error
        }

        return callback()
      })
  }

  #cache = new Map<number, ResolveRequest>()
}

And it works as expected in webpack, the duplicated modules have been eliminated.
But when we are trying to migrate to rspack, we found that resolve.plugins is not supported(https://github.com/web-infra-dev/rspack/issues/3890).
So it would be great if rspack or oxc supports dealing with hard links like this by default(I would like to file an issue to enhanced-resolve, too).
What does the proposed API of configuration look like?
It would be great if this is enabled by default(just like symlinks options of enhanced-resolve).
It is acceptable if this is an experimental configuration or a sub-configuration in resolve. E.g.:
export default {
  resolve: {
    hardlinks: true,
  },
  experimental: {
    resolve: { hardlinks: true }
  },
}

Relate pnpm hardlinks
Pnpm use symlinks from package node_modules to workspace node_modules, and use hardlinks from workspace node_modules files to global files.
Currently resolver can only deal with symlinks and get the node_modules of workspace. So this issue should occur when
there are multiple workspaces.
cc @Boshen

This isn't a bundler problem. Your codebase is no longer a monorepo, it's just different packages put inside the same codebase, and then you enabled compilation from source.
I don't have an exact solution, but you can try:

resolve alias that module
hoist the dependency to the root

there's no source or target role around paths sharing the same inode, thus i believe it's impossible to determine the resolved path without a rule.
in your plugin, the resolved path is determined by the first request. i think it is unstable.

This isn't a bundler problem. Your codebase is no longer a monorepo, it's just different packages put inside the same codebase, and then you enabled compilation from source.
I don't have an exact solution, but you can try:

resolve alias that module
hoist the dependency to the root

I agree that having such a huge monorepo with a bunch of pnpm workspaces inside is not a good way. But this helps us to collaborate between different teams efficiently. And our build tools based on webpack and esbuild works just fine with the plugin.
I don't think resolve.alias is a good solution since it will break the version constraint of the packages, it is likely to use a different version of a package with resolve.alias and cause bugs. It also requires all developers to be familiar with resolve and the dependencies(and the dependencies of dependencies) and write them down to the webpack.config.js, which is just impossible. This is not how you manage dependencies in such a huge project.
Not to mention hoist the dependency to the root. We would not use such a monorepo if we could merge the workspaces into one.

I'm not sure what do you mean by "there's no source or target role around paths sharing the same inode". Could you please explain that to me in detail? Thanks!

as you know, a symbolic link represents a link file linking to another file, when a resolver resolves a request that points to a symbolic link with option like preferRealPath it gives the linked file's path.
while a "hard link" just represents a path to an inode node. in your case, there's two "hard links" linked to a same inode node. the two paths are of equal status thus a resolver cannot say "who it prefer".
so i do think,  other than just "resolving paths with same inode number to one path",  we need an explicit option to tell "which path the resolver should choose when resolving paths with same inode number to one path"

"use the first coming result" might not be a good idea as it will change.
it might cause problem when there're different loaders/plugins logic against the two paths sharing the same inode number. though it's not very common in node_modules scene.

After some discussions internally, the consensus is that we can try and add a js resolve hook into Rspack, but we won't guarantee it's performance.

@colinaaa Can you provide a github test repository that replicates this project structure?

"use the first coming result" might not be a good idea as it will change.
it might cause problem when there're different loaders/plugins logic against the two paths sharing the same inode number. though it's rarely common in node_modules scene.

I agree that using the first coming result is not an ideal way. But we have to return results for each request, and there is no way to know if there are requests to come in the future. So the only way to make it work is to return the first coming result.

In my opinion, "use the first coming result" or inode check of hardlink are both business-specific logic that can be ensured by the business itself. They are not suitable to implement in OXC.
But in Rspack, the before_resolve hook cannot get the resolved path, and the after_resolve hook would generate full request, which leading to a substantial increase in transmission costs. Rspack does indeed need a low-cost way to modify the resolve result.

@Boshen Check this out! https://github.com/colinaaa/rspack-hardlink-repro

rspack-hardlink-repro  main ❯ ls -lh ./packages/a/node_modules/lodash
lrwxr-xr-x  1 bytedance  staff    62B Mar 12 16:09 ./packages/a/node_modules/lodash -><EMAIL_ADDRESS>
rspack-hardlink-repro  main ❯ ls -lh ./packages/b/node_modules/lodash
lrwxr-xr-x  1 bytedance  staff    62B Mar 12 16:09 ./packages/b/node_modules/lodash -><EMAIL_ADDRESS>
rspack-hardlink-repro  main ❯ ls -i ./packages/a/node_modules/lodash
162517384 ./packages/a/node_modules/lodash

rspack-hardlink-repro  main ❯  ls -i ./packages/b/node_modules/lodash
162517383 ./packages/b/node_modules/lodash

Is this replicated correctly?

rspack-hardlink-repro on  main is 📦 v1.0.0 via  v18.18.0
❯ /bin/ls -lh ./packages/a/node_modules/lodash
lrwxr-xr-x@ 1 bytedance  staff    62B Mar 12 14:43 ./packages/a/node_modules/lodash -><EMAIL_ADDRESS>
rspack-hardlink-repro on  main is 📦 v1.0.0 via  v18.18.0
❯ /bin/ls -lh ./packages/b/node_modules/lodash
lrwxr-xr-x  1 bytedance  staff    40B Mar 12 15:04 ./packages/b/node_modules/lodash -><EMAIL_ADDRESS>
rspack-hardlink-repro on  main is 📦 v1.0.0 via  v18.18.0
❯ /bin/ls -i ./packages/b/node_modules/lodash/lodash.js
797938 ./packages/b/node_modules/lodash/lodash.js

rspack-hardlink-repro on  main is 📦 v1.0.0 via  v18.18.0
❮ /bin/ls -i ./packages/a/node_modules/lodash/lodash.js
797938 ./packages/a/node_modules/lodash/lodash.js

Did you run the pnpm --prefix packages/b install?

I can't get the same inode 🤔


Check for directory existence and create if absent

For multi-lingual books (e.g. book/en, book/fr, etc.) if you try and
build styles written in LESS it will fail because the init hook
triggers before the language directories are written. This change
checks to see if the path exists first and, if it doesn't, creates it
synchronously.

@SamyPesse ping! Any chance you or someone else could take a look at this and approve and merge it? Thanks!

If anyone can take a look at this pull request and approve it or offer suggestions, I'd really appreciate it! Thanks!


I want to add few mini Javascript projects

I would love to contribute to this repository by adding some Javascript projects.
It will help me to step into open source contribution and.

/assign


Address query with address-role=receiver param results in hour+ queries

Subject of the issue
User made queries include new address-role=receiver query parameter. Queries were at a low velocity. Each query resulted in a thread in the db exceeding 1hr in execution time and a 504 timeout for the user.
DB query
"SELECT t.round, t.intra, t.txnbytes, t.extra, t.asset, h.realtime FROM txn t JOIN block_header h ON t.round = h.round JOIN txn_participation p ON t.round = p.round AND t.intra = p.intra WHERE p.addr = $1 AND (t.txn -> 'txn' ->> 'rcv' = $2 OR t.txn -> 'txn' ->> 'close' = $3 OR t.txn -> 'txn' ->> 'arcv' = $4 OR t.txn -> 'txn' ->> 'aclose' = $5) AND t.txid != '' ORDER BY p.addr, p.round DESC, p.intra DESC LIMIT 1000"
Your environment
MainNet
Indexer 2.6.5
8 core CPU / 64gb RAM in a cluster
Steps to reproduce

Execute /v2/transactions?address-role=receiver&address={address} in MainNet
Monitor response and DB

Expected behaviour
Indexer responds with expected transaction response
OR
If Indexer times out, kill the query
Actual behaviour
Indexer times out on response, query lives on consuming sessions and CPU, repeated attempts crash server

I'm curious about the EXPLAIN of that on a loaded db, and if we could rearrange the query to trick Postgres into doing the right thing. Maybe rearrange it to
WITH (SELECT p.addr, p.round, p.intra FROM txn_participation p WHERE p.addr = $1) AS ptxn
SELECT ... JOIN ptxn ON t.round = p.round AND p.intra = t.intra WHERE ...

I want Postgres to figure out that it can do a cheap filter on txns by txn_participation before doing the expensive filter digging into all the txn fields. (I suspect it isn't doing that, EXPLAIN may confirm/dispense that theory)

This should now cause a query timeout, let us know if that's not the case. (of course, we know it might also be desirable to make this more performant, but that's a different concern)


Auto completion takes forever to load

Issue Type: Performance Issue
Create a variable of a well defined object type.
Start to type the name of the variable then hit Ctrl+Space.
Same when you type '.' after the name of the variable to get object properties.
Same when you press F12 on the class of the object to ceck manually which properties it has.
VS Code version: Code 1.43.2 (0ba0ca52957102ca3527cf479571617f0de6ed50, 2020-03-24T07:38:38.248Z)
OS version: Windows_NT x64 10.0.18363

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz (4 x 2592)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.90GB (7.22GB free)

Process Argv

Screen Reader
no

VM
0%

Process Info
CPU %	Mem MB	   PID	Process
    0	    70	  1048	code main
    0	    66	  1472	   window (Issue Reporter)
    1	   218	 14604	   gpu-process
    0	    24	 14904	   utility
    0	   188	 15344	   window (●<PHONE_NUMBER>163-AddCodesAnalytiques.ts - tsmean (Workspace) - Visual Studio Code)
    0	    24	  2756	     searchService
    0	    52	 16992	     C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe
    0	     4	 13864	       C:\WINDOWS\system32\cmd.exe /c ""C:\Program Files\nodejs\npm.cmd" run typeorm:local migration:run"
    0	    28	 18108	         "C:\Program Files\nodejs\\node.exe"  "C:\Users\ykc\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" run typeorm:local migration:run
    0	     4	 17144	           C:\WINDOWS\system32\cmd.exe /d /s /c ts-node ./node_modules/typeorm/cli.js --config properties/development.ormconfig "migration:run"
   27	  1027	 10928	             electron_node bin.js cli.js
    0	     5	 17048	     console-window-host (Windows internal process)
    0	   100	 17108	     extensionHost
    0	    23	 15228	       "C:\Program Files\Microsoft VS Code\Code.exe" "c:\Program Files\Microsoft VS Code\resources\app\extensions\json-language-features\server\dist\jsonServerMain" --node-ipc --clientProcessId=17108
    0	    14	 15852	       C:\wamp64\bin\php\php7.3.5\php.exe c:\Users\ykc\.vscode\extensions\felixfbecker.php-intellisense-2.3.14\vendor\felixfbecker\language-server\bin\php-language-server.php --tcp=<IP_ADDRESS>:49941 --memory-limit=4095M
    0	     5	 15928	         console-window-host (Windows internal process)
    0	    49	 17520	       electron_node tsserver.js
   25	   856	 17544	       electron_node tsserver.js
    0	    22	 17988	         electron_node typingsInstaller.js typesMap.js
    0	    27	 18168	     watcherService
    0	    13	 16428	   electron-crash-reporter
    0	    62	 16724	   shared-process

Workspace Info
|  Window (●<PHONE_NUMBER>163-AddCodesAnalytiques.ts - tsmean (Workspace) - Visual Studio Code)
|    Folder (shared): 325 files
|      File types: ts(201) js(69) json(8) prettierrc(1) npmignore(1)
|      Conf files: package.json(1) tsconfig.json(1) tslint.json(1)
|    Folder (backend): 1436 files
|      File types: ts(690) php(155) js(127) docx(95) json(22) jpg(20) png(17)
|                  xlsx(16) txt(13) dotx(7)
|      Conf files: tsconfig.json(2) package.json(1) tslint.json(1)
|                  launch.json(1)
|      Launch Configs: node
|    Folder (frontend): 1652 files
|      File types: ts(754) scss(233) html(232) css(21) png(21) json(14) svg(9)
|                  js(5) eot(5) ttf(5)
|      Conf files: package.json(1) tsconfig.json(1) tslint.json(1)
|                  launch.json(1)
|      Launch Configs: node;

Extensions (11)

Extension
Author (truncated)
Version

vscode-intelephense-client
bme
1.3.11

vscode-generate-getter-setter
DSK
0.5.0

gitlens
eam
10.2.1

php-debug
fel
1.13.0

php-intellisense
fel
2.3.14

php-pack
fel
1.0.2

Angular2
joh
9.1.2

vscode-JS-CSS-HTML-formatter
lon
0.2.3

vscode-apache
mrm
1.2.0

mssql
ms-
1.9.0

vscode-typescript-tslint-plugin
ms-
1.2.3

Which language is this for?

It's for TypeScript, sorry.
After several hours of VS Code being open it finally worked again, but I didn't change anything since yesterday, and it worked as soon as I opened VS Code yesterday. I just remember updating the software but it  continued to work just after I did the update.

Does this reproduce in the latest VS Code insiders build with all extensions disabled?

No it works fine on the  latest VS Code insiders build with all extensions disabled. Thank you.

Thanks for testing. Please see if you can track down which extension is causing this and file an issue against them


Rename calender to calendar

This might as well be a breaking change. The major change in this pull request is that I've renamed calender to calendar.
Other changes include:

[x] Added a ISC License
[x] Added new line to end of files
[x] Use 4 spaces instead of 2 for some files
[x] Use npm scripts instead of global grunt installation
[x] Updated README
[x] Added the updated build files
[x] Added .editorconfig

@mesaugat Thanks for a pull request. It looks fine.


My first revup bar

Topic: bar

Reviews in this chain:
└https://github.com/Coobaha/revup/pull/2 My first revup bar

#
head
base
diff
date
summary

0
f2393ca9
311ff10d
diff
Nov 1 8:46 AM
1 file changed, 1 insertion(+)


Correction for raw affiliation Université Montesquieu, Bordeaux IV.

Correction needed for raw affiliation Université Montesquieu, Bordeaux IV.
raw_affiliation_name: Université Montesquieu, Bordeaux IV.
new_rors: 05h5wna09
previous_rors: 03pbgwk21
works_examples: W1574253718;W2090409644;W1581088990;W1530652453;W1522902097;W2623038362;W2170594753;W1988081443;W2023965088;W1987818554;W1975618218;W1982808556;W2968857518;W2050051322;W1499547992;W1964486535;W2921254033
contact: dc209076868e171fcf96c0872d83f11d:976aaeeb3c4b12495058fd @ free.fr

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


Expanded modding API

The core modding API systems are in place and all current ingame actions are piped to the mod scripts. However the function list needs great expanding.

This is now becoming a high priority as 0.1 has shipped.
Please comment suggestions and requests below as to what features are wished from the mod api.

A few things I'd like to see/work on:

Functions to place and remove platforms.
Functions to save and load custom data to and from the save file.
The ability to expose custom functions to the console (by passing in a high-order function and a name).

Yes I was meaning to mention that I need to add a JS type for structures. Save and load should be easy, however the custom functions to the console will be tricky. I have pondered it before and the main issue is that the console engine is never and should never be restarted as that would clear all user defined variables and functions.

One way this could be achieved is by storing a list of all functions that the current gamemode has exposed to the console and setting them all to undefined when the gamemode is unloaded. (One cannot delete functions in JS)

We need a system to execute JS code in the target engine when exposing a type to said engine. Some features the these types must be implemented directly in JS itself (like overriding .toString) so this would allow for that.

So the new plan is unsandboxed IronPython scripts with explicit manual installation instead of autodownload from server and execute.
Work has begun in the IronPython branch https://github.com/ForLoveOfCats/SkyOfSteel/tree/IronPython

Exposing custom functions to the console will be possible now with IronPython as when the gamemode is unloaded we can delete the functions it exposed to the console. (Python allows deleting functions whereas JS does not)

Closing this as the game's entire internal API is now exposed with the new C# gamemode scripting


Google Play update unavailable

Multiple reports of users stating that they cannot download the recent 0.8.0 update due to Google Play showing their device is not supported. The issue is not related to the code itself since providing a built APK directly to the user installs and runs as expected.
Steps/conditions to reproduce:
TBD

Issue related to Opsec team bumping the minimum Android version to one of the latest for the build released as a precautionary measure to ensure users are running the most secure Android OSes. The version was then re-released with support for slightly older versions due to a big portion of the userbase reporting being unable to download the app.


How to edit prometheus configs?

I want to add job in Prometheus but I can't find config map with Prometheus configs. Where is it?

The Prometheus addon is using the prometheus operator.  I haven't personally used it.  But here's the link to prometheus operator docs. https://github.com/coreos/kube-prometheus/blob/master/README.md

@heckad you need to create "service monitor" for the "thing" you want to be monitored by existing prometheus. Have a look for existing service monitors being deployed on your cluster to get the ides about the syntax.

@heckad Did you solve your problem ? I have exactly the same, no way to find the config of prometheus

@heckad Did you solve your problem ? I have exactly the same, no way to find the config of prometheus

@fabrichter, hi, I can't solve this problem.

@fabrichter, hi, I can't solve this problem.

I have the same problem and not information on how to change Prometheus configs to add a new job.

you have to add a servicemonitor for the scraper to go to your actuators https://medium.com/vividcode/monitor-spring-boot-apps-using-prometheus-on-kubernetes-a7c1b58c8511


make setup

Hi:
I build the images with "make setup" and get this error:

I don't konw which version of buildah  is right.

The current buildah version is 1.5.

closed.


Added baud_rate/dbaud_rate to json schema

Added baud_rate/dbaud_rate to json schema
For canfd baud_rate and dbaud_rate are mutually optional/required. For can you can only specify baud_rate

Looks good.
I didn't know "dependentSchemas" thing! Nice

Suggestion:
Instead of combining can and canfd describe each type in a separate oneOf. This will make is easier to understand and maintain the schema. The will also fix the problem that dbaud_rate is not allowed for canfd

Suggestion:
Instead of combining can and canfd describe each type in a separate oneOf. This will make is easier to understand and maintain the schema. The will also fix the problem that dbaud_rate is not allowed for canfd

dbaud_rate is only allowed for canfd and it "works", since not required means that it is not allowed.
I will update to two individual oneofs


Dsa

Description 📜
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
Fixes # <2454>

Type of change 📝

[x] Doc#umentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] DSA

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@AnkitaGupta454 remove the brackets and do not add space between # and digits then your issue will be attached.

Please review @harshsri28 @sneha-nitdgp


Rotate_Image.c

_ No description provided. _

@aradhymishra09 Please add problem statement and approach for the code file.


Issue found on page 'Securing Extensions' - Confusing recommendation

Dear team,
Under Disabling Autoinstalling and Autoloading Known Extensions it says:
To disable autoinstalling known extensions, run:
SET autoinstall_known_extensions = true;

To disable autoloading known extensions, run:
SET autoload_known_extensions = true;

I think that both of these suggestions are incorrect and they should instead be set to false, not true.
If my assumption there is incorrect I would suggest to make the configuration option more clear what it means.
Thank you for looking into this, Roy
Page URL: https://duckdb.org/docs/operations_manual/securing_duckdb/securing_extensions.html

Hi @rvsit, thanks for reporting. Indeed this seems to be off. I've submitted a fix.


Resolve References using Style Dictionary

Hello there, Thanks for this Great Library
Please any idea of how to resolve references ?
{
    "global": {
      "hello-pink": {
        "50": {
          "value": "#fge7ee",
          "type": "color"
        },
      },
      "white": {
        "value": "#ffffff",
        "type": "color"
      }
    },
    "Light": {
      "bg": {
        "default": {
          "value": "{white}",
          "type": "color",
          "description": "Default background color for the whole app."
        },
      },
      }
    }
  }

Here is the error i get
scss

Property Reference Errors:
Reference doesn't exist: Light.bg.default.value tries to reference white, which is not defined

Hey, this is an issue you are having with style dictionary, not really the plugin.
I think the issue is that you need to use {global.white}

Got it..
I opened another issue there... I don't mind if you can help too
https://github.com/amzn/style-dictionary/issues/830

Hey @allindeveloper did you try to use {global.white}?

global.white would work but it wont work in using figma token plugin.. i believe, the designer uses the plugin

so from here https://github.com/amzn/style-dictionary/issues/830
global.accent.default would work but the issue is, accent.default has to be within the same token file not in a different global file...
And I think it's best to follow what's coming from figma and the plugin...

So @allindeveloper did this solve your problem?

I had to do {dark.accent.default} and {light.accent.default} which solved my issue
Thank you


Generated tiles have coordinates ouside extent

Hi,
I generated tiles with osm2vectortiles project and then went back to decoding them with mapbox-vector-tile python package. I found something odd: there are negative coordinates and coordinates above the extent (4096). I am attaching an example tile and its corresponding decoded version
(5728.txt).
5728.gz
5728.txt
Coordinates such as [-849, -2042], or [-2034, -1165] can be found in tile.
The tile corresponds to zoom 14, x=8590 y=5728
I simply extracted the tile from the database, un-gzipped it and ran through the mapbox-vector-tile decode function.
I look forward to any clarification on this. Best regards,
Clara

Hi Clara,
this is a result of the buffer. A buffer on a layer allows you to include extra data around the outside of each tile. Depending on the data and desired styles this can be necessary to ensure seamless rendering across tile boundaries. A more detailed documentation can be found here.

Hi Manuel, thanks for the quick reply! By looking at the file osm2vectortiles/osm2vectortiles.tm2source/data.yml where the buffer settings seem to be, I don't see any buffer-size greater than 256 but in the tile I showed before there are coordinates in the -2000 range for example or above 5000, well above the 256 maximum.
Maybe I should consider that the 256 may come from a lower zoom level and duplicate in size as I "zoom in"?
Thanks,
Clara

This is a bit counter intuitive. The buffer is measured in px relative to a
256px tile.
With a resolution of 4096 a buffer of 128px can stretch up to 2048 for
example.
On May 10, 2016 5:00 PM, "fitsoft"<EMAIL_ADDRESS>wrote:

Hi Manuel, thanks for the quick reply! By looking at the file
osm2vectortiles/osm2vectortiles.tm2source/data.yml where the buffer
settings seem to be, I don't see any buffer-size greater than 256 but in
the tile I showed before there are coordinates in the -2000 range for
example or above 5000, well above the 256 maximum.
Maybe I should consider that the 256 may come from a lower zoom level and
duplicate in size as I "zoom in"?
Thanks,
Clara
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/osm2vectortiles/osm2vectortiles/issues/318#issuecomment-218185237

Hello Lukas,
Then in the esample you just gave I could have a coordinate take roughly values in the interval [-2048, 4096 + 2048] ?
Thanks,
Clara

All great questions @fitsoft.

Then in the esample you just gave I could have a coordinate take roughly values in the interval [-2048, 4096 + 2048] ?

Yes. Or with 256px even [-4096, 4096, 8192].
I don't know what the max number (if you can have more than 256px buffer) for the tile coordinate system is (4096 suggests 12 bits but you also need one bit for minus and one for 8192 so perhaps 14bit if 256px is the max buffer).


fix: add feature flag for domain sharding

SUMMARY
Superset allow users to enable CORS and domain sharding to improve dashboard performance. Currently domain sharding is enabled by offer a list of domains in SUPERSET_WEBSERVER_DOMAINS. But in current configuration, once domain sharding is enabled, it applies to every user in the system.
We found there are some cases that we need to exempt some service users from domain sharding. This PR is to add an additional feature flag, so that we can apply/disable this feature to certain users while keeping Superset have domain sharding available.
TEST PLAN
CI
@john-bodley @etr2460

Codecov Report

Merging #11797 (891a2ba) into master (a062cbb) will decrease coverage by 3.80%.
The diff coverage is 28.57%.

@@            Coverage Diff             @@
##           master   #11797      +/-   ##
==========================================
- Coverage   66.55%   62.74%   -3.81%
==========================================
  Files         903      905       +2
  Lines       43719    43849     +130
  Branches     4199     4203       +4
==========================================
- Hits        29095    27513    -1582
- Misses      14517    16156    +1639
- Partials      107      180      +73

Flag
Coverage Δ

cypress
?

javascript
62.83% <28.57%> (-0.02%)
:arrow_down:

python
62.69% <ø> (-0.80%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

superset-frontend/src/utils/hostNamesConfig.js
33.33% <0.00%> (-54.17%)
:arrow_down:

superset/config.py
90.07% <ø> (ø)

superset/views/base.py
72.68% <ø> (ø)

superset-frontend/src/featureFlags.ts
83.33% <40.00%> (-16.67%)
:arrow_down:

superset-frontend/src/explore/App.jsx
0.00% <0.00%> (-100.00%)
:arrow_down:

superset-frontend/src/dashboard/App.jsx
0.00% <0.00%> (-100.00%)
:arrow_down:

superset-frontend/src/explore/index.jsx
0.00% <0.00%> (-100.00%)
:arrow_down:

superset-frontend/src/dashboard/index.jsx
0.00% <0.00%> (-100.00%)
:arrow_down:

superset-frontend/src/setup/setupColors.js
0.00% <0.00%> (-100.00%)
:arrow_down:

superset-frontend/src/chart/ChartContainer.jsx
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 176 more

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 a062cbb...891a2ba. Read the comment docs.


Wrongly passed code using generics and string literal types

TypeScript Version:
1.8.7
compiled: tsc --noImplicitAny error.ts
(the behavior is exactly the same with or without --noImplictAny)
Code
// A self-contained demonstration of the problem follows...
type Greeting = "hello" | "goodbye"

const apply = <T extends string,R>(t: T, f: (t:T) => R): R => f(t)
const f1 = (a: Greeting) => console.log('greetings')
const f2 = (a: number) => console.log(3+a)

apply("hello", f1) /* 1. should be good. is good */
apply("helo", f1) /* 2a. should be error. is good */
apply<Greeting, void>("helo", f1) /* 2b. should be error. is error */

apply("hello", f2) /* 3. should be error. is error */
apply(3, f1) /* 4. should be error. is error */
apply(3, f2) /* 5. should be error. is error */

Expected behavior:
2-5 should have an error:
2 should have an error because "helo" is not a member of "hello"|"goodbye"
3 should have an error because "hello" is not a number
4 should have an error because 3 is not a member of "hello"|"goodbye" and because 3 is not a member of type which extends string
5 should have an error because 3 is not a member of a type which extends string, and because number does not extend string.
Actual behavior:
1, 2b, 3-5 are correct
2a passes typechecking even though it should be equivalent to 2b

Please see https://github.com/Microsoft/TypeScript/wiki/FAQ#why-are-function-parameters-bivariant for explanation.

@mhegazy Can you explain where function parameter bivariance comes into play here?

@tmcl explained it to me, the inferred generic parameters for 2a. are <string, void>, because string is the common type between "helo" and Greeting, and (s:Greeting) => void is compatible with (s:string) => void due to function parameter bivariance.


Setting limit on number of checkpoints per notebook

Is there a way to set a limit on the number of checkpoints created per notebook?
The checkpoints do not store the diff but rather the whole notebook as a blob, so a large file could eat up the storage.

There isn't a feature to do this at the moment. The closest thing is a feature to set the maximum allowed file size.

What all changes would be required to implement this enhancement?
Correct me if my understanding is wrong-  The 'limit' argument could be passed to the PostgresCheckpoints class through the configuration file, and changes can be made to the create_notebook_checkpoint() method, which would delete the oldest checkpoint if limit is getting crossed before creating the new checkpoint.


issue in outh.php

after passing on my credentials and signing in ,i'm getting error in outh.php
Notice: Use of undefined constant clientId - assumed 'clientId' in C:\xampp\htdocs\project\microsoft\phpconnect\php-connect-rest-sample\app\oauth.php on line 34
Notice: Use of undefined constant clientSecret - assumed 'clientSecret' in C:\xampp\htdocs\project\microsoft\phpconnect\php-connect-rest-sample\app\oauth.php on line 35
Notice: Use of undefined constant redirectUri - assumed 'redirectUri' in C:\xampp\htdocs\project\microsoft\phpconnect\php-connect-rest-sample\app\oauth.php on line 36
Notice: Use of undefined constant urlAuthorize - assumed 'urlAuthorize' in C:\xampp\htdocs\project\microsoft\phpconnect\php-connect-rest-sample\app\oauth.php on line 37
Notice: Use of undefined constant urlAccessToken - assumed 'urlAccessToken' in C:\xampp\htdocs\project\microsoft\phpconnect\php-connect-rest-sample\app\oauth.php on line 38
Notice: Use of undefined constant urlResourceOwnerDetails - assumed 'urlResourceOwnerDetails' in C:\xampp\htdocs\project\microsoft\phpconnect\php-connect-rest-sample\app\oauth.php on line 39
Notice: Use of undefined constant scopes - assumed 'scopes' in C:\xampp\htdocs\project\microsoft\phpconnect\php-connect-rest-sample\app\oauth.php on line 40
Notice: Use of undefined constant code - assumed 'code' in C:\xampp\htdocs\project\microsoft\phpconnect\php-connect-rest-sample\app\oauth.php on line 65
Fatal error: Uncaught exception 'GuzzleHttp\Exception\RequestException' with message 'cURL error 60: SSL certificate problem: unable to get local issuer certificate (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)' in C:\xampp\htdocs\project\microsoft\phpconnect\php-connect-rest-sample\vendor\guzzlehttp\guzzle\src\Handler\CurlFactory.php:187 Stack trace: #0 C:\xampp\htdocs\project\microsoft\phpconnect\php-connect-rest-sample\vendor\guzzlehttp\guzzle\src\Handler\CurlFactory.php(150): GuzzleHttp\Handler\CurlFactory::createRejection(Object(GuzzleHttp\Handler\EasyHandle), Array) #1 C:\xampp\htdocs\project\microsoft\phpconnect\php-connect-rest-sample\vendor\guzzlehttp\guzzle\src\Handler\CurlFactory.php(103): GuzzleHttp\Handler\CurlFactory::finishError(Object(GuzzleHttp\Handler\CurlHandler), Object(GuzzleHttp\Handler\EasyHandle), Object(GuzzleHttp\Handler\CurlFactory)) #2 C:\xampp\htdocs\project\microsoft\phpconnect\php-connect-rest-sample\vendor\guzzlehttp\guzzle\src\Handler\CurlHandler.php(43): GuzzleHttp\Handler\CurlF in C:\xampp\htdocs\project\microsoft\phpconnect\php-connect-rest-sample\vendor\guzzlehttp\guzzle\src\Handler\CurlFactory.php on line 187
could you please help

Hi @cliffon . Thanks for reporting this issue. Did you try this troubleshooting step from the readme? If not, can you please try it?
Error: Unable to get local issuer certificate
You receive the following error after providing your credentials to the sign in page.
SSL certificate problem: unable to get local issuer certificate
cURL can't verify the validity of the Microsoft certificate when trying to issue a request call to get tokens. You must configure cURL to use a certificate when issuing https requests by following these steps:

Download the cacert.pem file from cURL website.
Open your php.ini file and add the following linecurl.cainfo = "path_to_cacert/cacert.pem"

I offered a pull request to fix the "Use of undefined constant" notices and it was merged in yesterday, so that should be fixed.

Thanks again for reporting this issue, @cliffon ! Please reopen if you're still running into this.
Thanks again @schinkel  for fixing!


Command line parameters are not documented (including -ll-exception and -I)

Problem or new feature
The -I command line parameter, for including a directory into module searches, does not appear to be documented
Suggestions
It probably should be documented.

If I remember correctly, this was actually delegated to Rakudo because, you know, it's not a language but an implementation issue. I wonder if it still makes sense. We have an entry for environment variables here, but not for command line arguments. Anyway, that's where it should go.

I've found this issue #1668. Let me see if I find where we said "it was going to Rakudo"

And now everything is coming back to me, including this issue #949 that was the origin of the removal, to which I (more or less vehemently) opposed.

The wiki page it's been moved to hasn't changed since it was created. I'm not sure the command line has evolved since then, it probably has.

We should document any of the compiler args that are in Roast, which include at least -I, -n, -e, -p, --doc, and close out with a link to rakudo's wiki page for any non-standard ones.

There seems to be fairly comprehensive switch documentation here.


Add function enable/disable SW pins

Useful if not all SW pins are connected. It's good to disable disconnected ones. Otherwise it causes higher voltages spikes which can cause audible noise.

Tested. It works.
TODO: Read current value of the register not to overwrite anything else.


Support mount existing pv?

Some cloud vendor doesn't support "Dynamic Volume Provisioning". Does clickhouse-operator support mounting existing pv to each ChiHost? I don't see how to customize templates to do that.

If you define a volumeClaimTemplate with storageClass set to '' (empty string) the operator should use existing PVs.
This is described in the docs.  Have a look at https://github.com/Altinity/clickhouse-operator/blob/master/docs/storage.md.

Which existing PV does the template use if define a volumeClaimTemplate with storageClass set to '' (empty string)? I need each ck instance mount an unique existing PV.

It should pick up a PV that is large enough to meet your request and keep it even when pods restart or are upgraded. Try it out and post your results.  We've mostly been working with dynamic provisioning in our tests.

p.s.,  I'v managed to bound existing pv. Thanks!


feat: add locked type for mentions

Adds a locked icon type for voice channels you can't access. Saw this icon when you mention a voice channel w/o access to join.

Released in v2.5.0 because apparently v2.4.0's dist folder got messed up so I had to do a release


Adding --use-deps option.

This adds --use-deps as an option to the version command. The changes work in the following way:

Retrieve dependency projects
a. Capture the output from nx print-affected command
b. Parse the returned dependency graph
c. Traverse dependencies to get a list of the dependencies
Pass the list of dependencies to the tryBump function
Assess if there are affecting commits in the project or any of its dependencies to determine if there should be a change
Retrieve the recommended version bumps for the project and its dependencies
Use the greatest of the retrieved bumps.

Hi @CaffeinatedCodeMonkey, you made a very great work on this feature, thanks a lot for that! :fire:
I would like to see more e2e tests to be sure it behaves correctly. Firstly to be sure that no bump occurs if the option is not defined, secondly to check if it correctly bumps the project when the option is used, checking the CHANGELOGs content should be enough.
Regarding the options, I'm wondering how it is supposed to work with the sync mode? Does it have a meaning to use it with this mode? What do you think?
One minor detail would be to Prettify the files.
I will test it manually against different projects (libs, publishable libs, apps...) to see if it work as expected. I will come back after that.
Thanks again!

@edbzn Thanks! I'll add in the e2e tests and Prettify the files.
As far as sync mode, I guess it really depends on the underlying implementation of it. From what I'm gathering from the code, it appears that you run the version command against a single project in the workspace, it would update the versions for all versionable projects in the workspace according to the calculated version bump based on that single project. Is this correct? If so, then the behavior I would expect would be the following:
Single Project: If run on a single project, it would determine the version bump leveraging the specified project and its dependencies, then apply that new version across all versionable projects.
Affected Projects: If run across multiple projects, then it would repeat the Single Project behavior multiple times, potentially resulting in versions being skipped. Example: Project A bumps the workspace's versions from 0.0.1 to 0.0.2, followed by Project B bumping them from 0.0.2 to 0.0.3.
If my assumption on your all's implementation is correct, then this should already work. If, instead, it already calculates the version bump by taking into account all projects during a single execution, then it would require some extra work.

@edbzn I've added in the e2e tests. Also, I would like to point out one limitation I've just found with the --use-deps option: change logs. It appears that the change logs are not a simple matter to change in order to incorporate commit messages from dependencies into the target project. This has the result that you can see version bumps in the change log without including the messages.
Would the change logs including commit messages from dependencies be required in order to get it merged? And if so, do you have any guidance on how to achieve it?

It appears that the change logs are not a simple matter to change in order to incorporate commit messages from dependencies into the target project. This has the result that you can see version bumps in the change log without including the messages.

I don't think we need to include dependencies commit message in the changelog but instead what could be useful is a standard log for dependency bump, for example:
- update dependency @my-dependency to v0.0.2 (c16d0fa)

This would be achieved by creating an empty commit, but I have to think about a more robust & transparent solution. What do you think?

I think adding an empty commit could work. I think I may use the following strategy:
In tryBump, during
forkJoin([lastVersion$, commits$]).pipe(
    switchMap(([lastVersion, commits]) => {...})

I'll have access to the list of commits. From there, I should be able to filter down to the feats and fixes. For each resulting array that has more than 0 commits, I can add a commit with a message like:
{type}({target_project}): changes occurred in one or more dependent projects

Then, an eventual enhancement could be to parse the commits and embed their messages in the newly made commits.
How does this sound?

Ummh you are right it will not work and it can be hard with the underlying package we use (standard-version). I think we can skip this feature at this stage, open an enhancement issue and improve it further if users need it.

@edbzn I've written up a discussion (https://github.com/jscutlery/semver/discussions/293) for that feature. Are there any outstanding issues you feel need addressed in this PR?

I'm waiting for @yjaaidi review and feedback before merging. Thanks for your time!

@edbzn and @yjaaidi , I've made some changes, based on what I learned from NX-Conf. It no longer leverages the CLI for getting the project graph. Instead it uses a function in @nrwl/workspace. According to Nrwl, the function is still subject to change, but is available for use, it just requires a deep import. In order to avoid breakage during changes, I've specified a project graph version when the function is called.

Nice change, I approve.
I'm still thinking about the dependency log, we will need to breakout standard-version into smaller functions to control the full behavior. It requires a certain amount of work, I will fill the discussion with more details in the near future.

@edbzn Thanks! It looks like everything rebased correctly.


Force UTF-8 Encoding when reading the NuSpec

Hi! First of all, thanks to the AWESOME plugin. Good work!
I found one minor issue when my Nuget description has special characters, even if the encoding is defined on the XML tag like this:

So, if you force UTF-8 it via the Get-Content we would be on safe side.

I will have as look at this as soon as I can.

In version 1.7.3 of the extension


How to generate different random number with this module?

I tried to generate a gaussian noise with this module, however, I come across this problem:
`
function gaussian_noise(_mu,_sigma,rng)
local sd = dist.normal(_mu,_sigma)
local noise = sd:sample(rng)
return noise
end
for i=1,10 do
rng = prng.kiss99()
noise = gaussian_noise(0,1,rng)
print(noise)
end
`
I tried some methods but it just come out the same random number, and I did not know how to fix it through the document.
Any help will be appericated!

Sorry to interrupt, I made a mistake. Actually, the random will not be the same if:
rng = prng.kiss99()
sd = dist.normal(0,1)
for i=1,10 do

    u = sd:sample(rng)
    print(u)
end


Topology to svg

This is still wip but the idea is to create an sbt plugin to achieve something similar to https://zz85.github.io/kafka-streams-viz/
For now this is not a plugin (as it misses all the relevant code), it's incapable of scanning in search of topologies and it's not outputting the fancy "handwritten" graphs (for which I'll pull in rough.js).
What it does? topology as a string -> dot -> svg

this means going from
Topology
Sub-topologies:
Sub-topology: 0
	Source:  KSTREAM-SOURCE-0000000000 (topics: [conversation-meta])
	--> KSTREAM-TRANSFORM-0000000001
	Processor: KSTREAM-TRANSFORM-0000000001 (stores: [conversation-meta-state])
	--> KSTREAM-KEY-SELECT-0000000002
	<-- KSTREAM-SOURCE-0000000000
	Processor: KSTREAM-KEY-SELECT-0000000002 (stores: [])
	--> KSTREAM-FILTER-0000000005
	<-- KSTREAM-TRANSFORM-0000000001
	Processor: KSTREAM-FILTER-0000000005 (stores: [])
	--> KSTREAM-SINK-0000000004
	<-- KSTREAM-KEY-SELECT-0000000002
	Sink: KSTREAM-SINK-0000000004 (topic: count-resolved-repartition)
	<-- KSTREAM-FILTER-0000000005
Sub-topology: 1
	Source: KSTREAM-SOURCE-0000000006 (topics: [count-resolved-repartition])
	--> KSTREAM-AGGREGATE-0000000003
	Processor: KSTREAM-AGGREGATE-0000000003 (stores: [count-resolved])
	--> KTABLE-TOSTREAM-0000000007
	<-- KSTREAM-SOURCE-0000000006
	Processor: KTABLE-TOSTREAM-0000000007 (stores: [])
	--> KSTREAM-SINK-0000000008
	<-- KSTREAM-AGGREGATE-0000000003
	Sink: KSTREAM-SINK-0000000008 (topic: streams-count-resolved)
	<-- KTABLE-TOSTREAM-0000000007

to
digraph G {
	label = "Kafka Streams Topology"
	subgraph cluster_0 {
		label = " Sub-\ntopology: 0";
		style = filled;
		color = lightgrey;
		node [style = filled, color = white];
		"KSTREAM-\nSOURCE-\n0000000000" -> "KSTREAM-\nTRANSFORM-\n0000000001";
		"KSTREAM-\nTRANSFORM-\n0000000001" -> "KSTREAM-\nKEY-\nSELECT-\n0000000002";
		"KSTREAM-\nKEY-\nSELECT-\n0000000002" -> "KSTREAM-\nFILTER-\n0000000005";
		"KSTREAM-\nFILTER-\n0000000005" -> "KSTREAM-\nSINK-\n0000000004";
	}
	subgraph cluster_1 {
		label = " Sub-\ntopology: 1";
		style = filled;
		color = lightgrey;
		node [style = filled, color = white];
		"KSTREAM-\nSOURCE-\n0000000006" -> "KSTREAM-\nAGGREGATE-\n0000000003";
		"KSTREAM-\nAGGREGATE-\n0000000003" -> "KTABLE-\nTOSTREAM-\n0000000007";
		"KTABLE-\nTOSTREAM-\n0000000007" -> "KSTREAM-\nSINK-\n0000000008";
	}
	"conversation-\nmeta" -> "KSTREAM-\nSOURCE-\n0000000000";
	"KSTREAM-\nTRANSFORM-\n0000000001" -> "conversation-\nmeta-\nstate";
	"KSTREAM-\nSINK-\n0000000004" -> "count-\nresolved-\nrepartition";
	"count-\nresolved-\nrepartition" -> "KSTREAM-\nSOURCE-\n0000000006";
	"KSTREAM-\nAGGREGATE-\n0000000003" -> "count-\nresolved";
	"KSTREAM-\nSINK-\n0000000008" -> "streams-\ncount-\nresolved";
	"conversation-\nmeta" [shape = rect];
	"count-\nresolved-\nrepartition" [shape = rect];
	"streams-\ncount-\nresolved" [shape = rect];
	"conversation-\nmeta-\nstate" [shape = cylinder];
	"count-\nresolved" [shape = cylinder];
}

and ultimately to

@barambani I think I'll just merge this as is for now. I'm sure there's many things you won't like but let's address them after, wdyt?


Open Legend: Attribute Sub & Guard

1.7.7 on 2017 January 27th

Added Attribute Substitution for all Attributes

Fixed drop downs to have ALL attributes except for the current
attribute being looked at

Updated all function calls to account for 1.7.6

Including calculations to display prorperly if attribute subsitution
was being used

1.7.6 on 2017 January 24th

Added new universal function for determining attribute substitution
values

Reusable code so less lines of code

Updated drop down menus to reflect change of Evasion > Guard
Renames lines "Increase/Decrease Dice Size" to be "Attribute Dice
Bonus/Penalty"

I don't know what happened that caused all these 5eshaped things to show up on my commit. NOt sure if that is going to cause a problem??

There are merge conflicts. This means that the branch that you did all of your work on was out of date. You either need to make a local copy of your changes, then either pull from the main branch or delete and re-fork the main branch, then add all of your changes back that should fix it.


not working

steps of what I did:
step 1: i downloaded the zip file for this and extracted.
step 2: installed python 3.7
step 3: opened RATAttack.py file and added token I got from botfather and my chat id
step 4: saved the file and ran compile.py
END
now what happened in result.

a folder appeared in same directory with a name pycache that contained a file that apparently does nothing
got a new folder here "C:\Users{THIS_IS_MY_USERNAME}\AppData\Roaming" that contains an exe file and it also apparently does nothing.

if I send a msg to my bot. i will not respond.
any help is appreciated

Can you run python RATAttack.py and post the output?

Thanks for your reply.
this is what I get.
PS C:\Users{MY_USERNAME}\Downloads\Compressed\RAT-via-Telegram-master\RAT-via-Telegram-master> python RATAttack.py                                                                                Traceback (most recent call last):
File "RATAttack.py", line 11, in
from winshell import startup                                              # persistence
File "C:\Users{MY_USERNAME}\AppData\Local\Programs\Python\Python37\lib\site-packages\winshell.py", line 30, in
import win32con
ModuleNotFoundError: No module named 'win32con'
after that i tried to install win32con by using commands
python -m pip install win32con
and
pip install win32con
but both of these commands give error as win32con is not a module or it is not found. I have pypiwin32 already installed.
I dream if replacing win32con with pypiwin32 on file winshell.py on line 30 will fix the issue.
could you please tell me about this problem.

I honestly have no clue man. Have you tried this


Optimize method for reading the files generated by the OpenTofu

Fixed https://github.com/eclipse-xpanse/xpanse/issues/2068
Related to https://github.com/eclipse-xpanse/xpanse/pull/2094 and  https://github.com/eclipse-xpanse/terraform-boot/pull/162

LGTM

LGTM

LGTM

LGTM

LGTM


Enable to read and write boolean type data

This PR is to  enable to read and write boolean type data for segment v1

for #3323

What about segment v2?

What about segment v2?

The segment v2 works fine now, boolean type data write and read is suppoted by RlePageBuilder


AttributeError: 'FritzBoxTools' object has no attribute '_unique_id'

Hi @AaronDavidSchneider. Autodiscovery is working great. Thanks for adding it with the latest release.
Unfortunately I have this error in my log and entities are not available.
2020-10-06 20:05:27 ERROR (MainThread) [custom_components.fritzbox_tools.binary_sensor] Error getting the state from the FRITZ!Box
Traceback (most recent call last):
  File "/config/custom_components/fritzbox_tools/binary_sensor.py", line 69, in _async_fetch_update
    status = self.fritzbox_tools.fritzstatus
AttributeError: 'FritzBoxTools' object has no attribute 'fritzstatus'
2020-10-06 20:05:27 ERROR (MainThread) [homeassistant] Error doing job: Future exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/fritzbox_tools/switch.py", line 105, in _create_profile_switches
    if len(fritzbox_tools.profile_switch) > 0:
AttributeError: 'FritzBoxTools' object has no attribute 'profile_switch'
2020-10-06 20:05:27 ERROR (MainThread) [homeassistant.components.binary_sensor] Error while setting up fritzbox_tools platform for binary_sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 201, in _async_setup_platform
    await asyncio.gather(*pending)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 310, in async_add_entities
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 356, in _async_add_entity
    if entity.unique_id is not None:
  File "/config/custom_components/fritzbox_tools/binary_sensor.py", line 52, in unique_id
    return f"{self.fritzbox_tools.unique_id}-{self.entity_id}"
  File "/config/custom_components/fritzbox_tools/__init__.py", line 216, in unique_id
    return self._unique_id
AttributeError: 'FritzBoxTools' object has no attribute '_unique_id'

This happens in unconfigured state. Once configured with a profile and restarting HA again, everything is working.

Thanks for the report @ReneHezser! I had the same error with other components as well. Probably, because you did not properly remove fritzbox tools before a restart.
Happens sometimes. Feel free to reopen if it occurs more often to you.


Log the UTC offset to help debug OSF-6447

Purpose
Log moment().utcOffset() to aid in debugging OSF-6447.
Changes
Adds a log line during testing.
Side effects
n/a
Ticket
https://openscience.atlassian.net/browse/OSF-6447

Is this acceptable, @sloria, et al.?

Yep