Error ets Jan  8 2013,rst cause:2, boot mode:(3,6) at NodeMCUV2

Yesterday compiled program in platformIO for a NodeMCUV2 (ESP8266) and it worked. Now I cannot compile a working firmware.bin. Nothing chanegd as far as I can see. Don't know where to start....

The error on the title is not a compilation error but a boot message from the ESP.
Give more details / screenshot of your issue.
(You can simply copy paste images here)

I know, it's the serial debug port and as far as I cab see it's the WD.

Can someone share complete .pio folder, maybe it's a version of the header files which are not correct.

On ESP8266, some users reported issues with the use of PROGMEM.
Just remove it from the default.h definition file you're using and try again.

Hello @Goofman2, what your situation now?

i had same issue on NodeMCU v3. board did not start. with removing PROGMEM it finally started.

I guess it's solved.


Use gateways for mesh expansion

(This is used to request new product features, please visit https://discuss.istio.io for questions on using Istio)
Describe the feature request
Mesh expansion is pretty cool.  Unfortunately, it requires a VPC.  Sort out how to use a gateway instead.
Describe alternatives you've considered
None.  I want mesh expasion integration with gateways.
Affected product area (please put an X in all that apply)
[ ] Configuration Infrastructure
[X] Docs
[X] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Additional context

+1 on using gateway for mesh expansion, we have got too many users ask about mesh expansion not working or not easy to get it working for non flat L3 network among k8s pods and VMs.
The question I want to bring up is:  is this in addition to the existing mesh expansion doc as a different model or we are proposing to get rid of the current mesh expansion?
cc @costinm @duderino

No, it's inaccurate. We already use gateway for mesh expansion. https://istio.io/docs/setup/kubernetes/additional-setup/mesh-expansion/
We might want to document both supports. Not aware of any any technical obstacles other than doc and testing...

@incfly thanks, you are right, it was embedded in there.

@incfly https://istio.io/docs/setup/kubernetes/additional-setup/mesh-expansion/  has a prereq: Mesh expansion machines must have IP connectivity to the endpoints in the mesh. This typically requires a VPC or a VPN, as well as a container network that provides direct (without NAT or firewall deny) routing to the endpoints. The machine is not required to have access to the cluster IP addresses assigned by Kubernetes.
The gateway in this doc is only for connecting pilot and citadel.  So we need a new doc to cover using gateway to connect workloads as well and this is the one: https://github.com/istio/istio.io/pull/4713


Unclear documentation for headless setup

The documentation states:

Just add headless.apkovl.tar.gz overlay file at the root of Alpine Linux boot media (or onto any writeable side-media) and boot the system.

This leaves me wondering how to provide the wpa_supplicant configuration. I am attempting an install on a Pi Zero W, which has no native ethernet interface.
It seems more is needed in these steps, for configuring a headless WiFi-only setup.

Hi, thanks for your interest.

Optional files can be added next to headless.apkovl.tar.gz

So you can add your custom wpa_supplicant.conf at same level as the apkvol file.
Note on PiZero you can use the usb-gadget path too, and setup wifi later with setup-alpine.
Your call.

Hi there. Thank you for your response. Here is what the filesystem looks like. Am I on the right path? When I boot the Pi Zero W2, it doesn't connect to WiFi:
xps# pwd
/media/sda1
xps# ls -alh
total 6.0M
drwxr-xr-x 5 root root  16K Dec 31  1969 .
drwxr-xr-x 5 root root 4.0K Aug 12 15:44 ..
-rwxr-xr-x 1 root root   25 Jul  6 07:55 .alpine-release
drwxr-xr-x 3 root root  16K Jul  6 07:55 apks
-rwxr-xr-x 1 root root  30K Jul  6 07:55 bcm2710-rpi-2-b.dtb
-rwxr-xr-x 1 root root  32K Jul  6 07:55 bcm2710-rpi-3-b.dtb
-rwxr-xr-x 1 root root  32K Jul  6 07:55 bcm2710-rpi-3-b-plus.dtb
-rwxr-xr-x 1 root root  30K Jul  6 07:55 bcm2710-rpi-cm3.dtb
-rwxr-xr-x 1 root root  31K Jul  6 07:55 bcm2710-rpi-zero-2.dtb
-rwxr-xr-x 1 root root  31K Jul  6 07:55 bcm2710-rpi-zero-2-w.dtb
-rwxr-xr-x 1 root root  51K Jul  6 07:55 bcm2711-rpi-400.dtb
-rwxr-xr-x 1 root root  51K Jul  6 07:55 bcm2711-rpi-4-b.dtb
-rwxr-xr-x 1 root root  52K Jul  6 07:55 bcm2711-rpi-cm4.dtb
-rwxr-xr-x 1 root root  49K Jul  6 07:55 bcm2711-rpi-cm4s.dtb
-rwxr-xr-x 1 root root  21K Jul  6 07:55 bcm2837-rpi-3-a-plus.dtb
-rwxr-xr-x 1 root root  21K Jul  6 07:55 bcm2837-rpi-3-b.dtb
-rwxr-xr-x 1 root root  22K Jul  6 07:55 bcm2837-rpi-3-b-plus.dtb
-rwxr-xr-x 1 root root  21K Jul  6 07:55 bcm2837-rpi-cm3-io3.dtb
drwxr-xr-x 2 root root  16K Jul  6 07:55 boot
-rwxr-xr-x 1 root root  52K Jul  6 07:55 bootcode.bin
-rwxr-xr-x 1 root root   60 Jul  6 07:55 cmdline.txt
-rwxr-xr-x 1 root root  469 Jul  6 07:55 config.txt
-rwxr-xr-x 1 root root 5.3K Jul  6 07:55 fixup4.dat
-rwxr-xr-x 1 root root 7.1K Jul  6 07:55 fixup.dat
-rwxr-xr-x 1 root root 6.3K Aug 12 15:46 headless.apkovl.tar.gz  # <- headless tarball
-r-xr-xr-x 1 root root 119K Aug 12 11:41 ldlinux.c32
-r-xr-xr-x 1 root root  60K Aug 12 11:41 ldlinux.sys
drwxr-xr-x 2 root root  32K Jul  6 07:55 overlays
-rwxr-xr-x 1 root root 2.2M Jul  6 07:55 start4.elf
-rwxr-xr-x 1 root root 2.9M Jul  6 07:55 start.elf
-rwxr-xr-x 1 root root  221 Aug 12 15:47 wpa_supplicant.conf   # <- My wpa_supplicant
xps#

Yes as far as what we cover in this repo goes.
I have tested on PiZeroW (my primary target initially), but not with PiZeroW2 (yet).
There have been issue in earlier Alpine releases for supporting wireless chip on this device (missing firmware), but I think 3.16.2 should be fine now.

I faced the same issue with my Raspberry Pi 4. It worked perfectly via ethernet but not via wifi. I then retried and after waiting for some time it connected to my router. @jabberwock For how long did you wait?

Entropy generation can be an issue which may slow wpa-supplicant start.
On Pi it is a good idea to install rng-tools and set it as a boot runlevel service. On single-core Pi, it is advised to just rely on hwrng, and disable jitter source in /etc/conf.d/rngd.
Anyhow this is after initial boot-up when you install addon packages…

Yes as far as what we cover in this repo goes, layout seems correct. I have tested on PiZeroW (my primary target initially), but not with PiZeroW2 (yet). There have been issue in earlier Alpine releases for supporting wireless chip on this device (missing firmware), but I think 3.16.2 should be fine now.
unsure why you have these though:
-r-xr-xr-x 1 root root 119K Aug 12 11:41 ldlinux.c32
-r-xr-xr-x 1 root root  60K Aug 12 11:41 ldlinux.sys

Alpine release just needs to be extracted on blank FAT32 SD, with no other processing. Also make sure FAT partition label is not "boot"

These are here from following the directions for installing syslinux at https://wiki.alpinelinux.org/wiki/Create_a_Bootable_Device#Manually_copying_Alpine_files

I faced the same issue with my Raspberry Pi 4. It worked perfectly via ethernet but not via wifi. I then retried and after waiting for some time it connected to my router. @jabberwock For how long did you wait?

I waited about 10 minutes. I will give it another go ASAP. Thank you!

@jabberwock The 2 files are for x86/64 install, not Pi.
You may have some mix&match files.
Just follow the Pi guide in Wiki: all you really need is just to untar on a blank SD (not named « boot »), and add the 2 files (apkovl & wpa). The rest of the wiki description happens after first boit really…
Again the usb-ethernet-gadget route is also very efficient it you have a PC/Mac on the site to hook usb to.

On Pi it is a good idea to install rng-tools and set it as a boot runlevel service.

I remember having entropy related delays with wifi but it's been a couple years since I've done much with a pi. On the wiki I wrote for the original zero w, I said:

I had problems with it initially as WiFi wouldn't connect when going through the setup-alpine script and when I was able to get it connect (after numerous failed manual attempts) it wouldn't reconnect on reboot. The solution documented below adds and starts the rngd service prior to running setup-alpine which fixes the wifi connection problems and allows you to walk through the setup script successfully.

I haven't tested it, but one possible solution for the current headless boot, might be to install the rngd packages from unattended.sh?
Download the rng-tools and rng-tools-openrc .apk files from a repo mirror with the correct architecture, eg:
https://dl-cdn.alpinelinux.org/alpine/v3.16/main/aarch64/
Copy both files into the root of the sd card alongside the headless.apkovl.tar.gz etc. and create unattended.sh there also which might look something like:
#!/bin/sh

for apk in $ovlpath/rng*
do
  apk add --allow-untrusted $apk
done

rc-service rngd start

I doubt @jabberwock issue is with entropy: juste mentioned it about possible cause for @kevbenjam delays.
Back on original issue, please confirm which specific install archive file you use.

@jabberwock Upcoming 3.17 will fix the issue with updated update-kernel and linux-firmware: both Pi02w variants, CM4 and Pi400 firmware are now properly built into modloop, enabling wifi from stock releases.
Those who can't wait may copy & replace modloop files extracted from 3.17_rc3 image.


test: additional unit tests for main module

closes #570
Summary:
Additional unit test for main module.
Expected behavior:
No code change. Tests should pass.
Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Run the unit tests with gradle test to make sure you didn't break anything
[x] Format the title like "feat: -new feature short description-" (PR title must follow the conventional commit specification)
[x] Linked all relevant issues
~[ ] Include screenshot(s) showing how this pull request works and fixes the issue(s)~

@barbeau @aababilov
fieldValuesNotSetShouldBeNull for class GtfsStopTimeTest and GtfsRoute failed. I think that the default value should be NOT_AVAILABLE  instead of ALLOWED. If you agree with that, I open an issue to rectify this.

Indicates that the rider can alight from the transit vehicle at any point along the vehicle’s travel path as described by shapes.txt, on every trip of the route.


Killercoda webhook broken?

The update for v1.2.0 has been merged (#76) but I don't see killercoda.com being updated.
Please check whether there are any errors on the webhook which syncs to killercoda and / or the killercoda.com logs.

Closing this as "not an issue" because I can see killercoda.com is now serving 1.2.0 so I'm assuming it was a temporary problem.


pop-box width adjusted for mobile

Fixes #2025
Sample :- https://shubham3211.github.io/calendar-fix/index.html

The screenshot shows resolution as well, please check-

@agbilotia1998 I am not getting the error , can you tell me how to generate the error


Adding A Highlight Button to the Admin Page for Stories Still Being Edited

#Highlight Button on the Admin Page
We have button for Bold and Italics
Could you add a highlight button for stories being edited? (Yellow and/or other colors)
(NOT Urgent)

https://gsdf.georgia.gov/admin/#/collections/pages/entries/1bde?ref=workflow

@BeverlyRShepard
Until we look into adding a button or changing the editor entirely, keep in mind that you can add Mark tags around the text you want highlighted.  For Example if I want to highlight the word test I would add  in front and  at the end.
<mark>test </mark>


fixed grammar

"Organisation's" is the possessive form of the noun "organisation", which indicates ownership or possession by the organisation.

Brilliant, thanks!


Refactor on as enhancer

Codecov Report

Merging #55 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #55   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          19     19
  Lines         213    211    -2
  Branches       57     57
=====================================
- Hits          213    211    -2

Impacted Files
Coverage Δ

src/enhancers/as.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Autoscroll breaks on far right or bottom

When you are scrolled (with autoscroll or manual scroll) all the way to the right or all the way to the bottom, the autoscroll will not work.
Must be an implementation detail that is wrong somewhere, but not sure where.

Will open issue in React Beautiful DnD's repo.


docs: fix get-started.md error

Coverage remained the same at 76.297% when pulling 9773170eb5de7f1741ce67a74c5b9ed34afe694f on Gala-R:fix-docs-wrong into 90e855b57f35a0921ab401e93c42d82dd9b2694a on emqx:main.


Commit message missing from Cypress Cloud when cypress/included container is used in GitHub Actions

Description
When we let Cypress tests run on the container cypress/included, commit message is no longer logged in Cypress Cloud. The commit hash is still there but no link to click.
URL of Issue(s)
https://cloud.cypress.io/projects/fm8w1c/runs/71/overview
Steps to replicate

Add these last two lines to your workflow yaml file for a recorded run as described here:

jobs:
  cypress-run:
    runs-on: ubuntu-22.04
    container:
      image: cypress/included

Commit and push to GitHub
Rerun the workflow on GitHub Actions
Commit message is missing from Cypress Cloud

When you remove these again, the necessary information reappears.
Browser
n/a
Device

[ ] PC
[ ] Mac
[ ] iPhone
[ ] iPad
[ ] Android Phone
[ ] Android Tablet

Additional Information
GITHUB token is provided as an ENV variable, like so: https://github.com/ugent-library/deliver/blob/fa660f2f7eb801315311c00de37263d6cf53aacf/.github/workflows/cypress-tests.yml#L35

@verheyenkoen
Thanks for reporting the issue that the commit message is missing in Cypress Cloud if you are using a Cypress Docker container like this:
jobs:
  cypress-run:
    runs-on: ubuntu-22.04
    container:
      image: cypress/included

It seems that this is a permissions issue, as I am able to reproduce the situation:

no commit MESSAGE shown on Cypress Cloud
Numerical COMMIT is shown on Cypress Cloud, however it is not a hyperlink back to the GitHub repo

After adding the Docker user 1001 as below the commit MESSAGE was shown and the COMMIT was a hyperlink.
jobs:
  cypress-run:
    runs-on: ubuntu-latest
    container:
      image: cypress/included:latest
      options: --user 1001

Would you like to try this?
I also have some other comments on your workflow. Let's get the main point sorted out first if possible though.

https://github.com/cypress-io/github-action#docker-image

Yes, this worked, thanks!

Hey, having the same issue. Workflow:
jobs:
  cypress:
    runs-on: default-visable
    container:
      image: cypress/browsers:node18.12.0-chrome107
      options: --user 1001
    env:
      GITHUB_TOKEN: ${{ secrets.PACKAGES_READ_ONLY_TOKEN_GITHUB }}
      PUBLIC_API_URL: "https://api.staging.visable.io"
      IS_CYPRESS: "true"
      BASE_URL: "https://www.wlw-staging.de"
      REQUESTS_INTERNAL_API: "https://requests-service.internal.wlw-1.staging.visable.cloud/requests_service/internal_api"
      RECAPTCHA_SITE_KEY: "6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI"
      RECAPTCHA_SECRET_KEY: "6LeIxAcTAAAAAGG-vFI1TnRWxMZNFuojJ4WifJWe"
    steps:
      - uses: pnpm/action-setup@v3
        with:
          version: 8.15.3
      - name: Define proper Checkout REF
        shell: bash
        run: echo "ref=$(echo ${GITHUB_HEAD_REF:-${GITHUB_REF}})" >> $GITHUB_OUTPUT
        id: extract_ref
      - uses: actions/checkout@v4
        with:
          ref: "${{ steps.extract_ref.outputs.ref }}"
      - name: setup github packages authentication
        run: 'echo "//npm.pkg.github.com/:_authToken=${{ secrets.PACKAGES_READ_ONLY_TOKEN_GITHUB }}" > ~/.npmrc'
      - uses: cypress-io/github-action@v6
        id: cypress
        env:
          GITHUB_TOKEN: ${{ secrets.PACKAGES_READ_ONLY_TOKEN_GITHUB }}
          COMMIT_INFO_BRANCH: ${{ github.ref_name }}
          CYPRESS_RECORD_KEY: ${{ secrets.CYPRESS_RECORD_KEY }}
        with:
          record: true
          build: pnpm build
          start: pnpm start
          browser: chrome
      - name: cleanup repo files
        if: always()
        run: find . -mindepth 1 -delete

@gkatsanos
Please open a new issue. The previous one was about cypress/included which you are not using.
It may be a permissions issue again, since you are apparently using a self-hosted runner.

Yes, it seems it is a permissions issue indeed.


List of versions

Very often a work is derived into a set of versions. While isVersionOf can describe the relation that exactly two EditorialObjects have, we also need a list of derived versions from a source in everyday's work. This list is hard to extract from a set of  isVersionOf relations, that might even be hierarchichal. You need to "follow" a chain of versions in the worst case. It would be practical to identify a source version and then link all derived content to it, even if the versions have evolved over several generations of intermediate versions.
Therefore, I propose to introduce a class EditorialVersions that is referenced from the source with hasVersions´ and from the targets with isEditorialVersionOf.  Individual EditorialObjects can still be linked with isVersionOf to point to the direct ancestor.
Please comment!

EBUCorePlus Editorial Committee: a more generic approach to version control is recommended. Replace the isVersionOf relation by a generic VersionControl-Class that describes, eg. the source, the target, the version number, the editor, the editing date, the applied changes ... for any type of class, not only EditorialObjects.
But we need to obeye the idea of business impact. If the change is not the reason for different handling in the business process then it does not need to be documented and no new instance has to be created. Always ask ourselves, whether the source object needs to "survive" or not.
The desired list of versions from a source could then be generated with a SPARQL-Query, even spanning multiple version steps.
Have a look at the ontology of "variants". It is similar to branches in a source versioning system. Check out this link for further exploration:
https://support.isan.org/hc/en-us/articles/360002783131-Records-relations-and-hierarchies-in-the-ISAN-Registry


My recipe doesn't appear in the cookbook

Hi Chris,
My recipe (Vegan Breakfast Cookies) isn't appearing in the class cookbook at https://chrisdaaz.github.io/forking/.  It looks like it was merged into your forking repo 6 days ago, so I'm wondering if I did something wrong that is making it not appear in the final product.
Thanks,
Lori

thanks for letting me know! there was a problem with the YAML frontmatter for the recipe (not your fault), so i fixed it with this commit: https://github.com/chrisdaaz/forking/commit/488cbb36a2579ea5b6c7e2612c022805d516d27d
Enjoy! https://chrisdaaz.github.io/forking/recipes/vegan-breakfast-cookies.html


Release 3.1.0 for Windows

Replacing OFFICE NOISES • When working from home feels too quiet! with WORKPLACE BACKGROUND NOISE -- Office Sounds for Focusing While You Work Remotely.

https://github.com/kkamara/kelvinkamara/releases


Improve SAML Extension Processing in response building

Current implementation has been done due to the following restrictions.

All the extension processors are invoked after building the assertion and before encrypting as in [1], since there are few modifications to the assertion in eIDAS processor.
In default saml assertion builder in [2], returns the signed assertion. Since there will be modifications to the assertion in eidas extension processor, assertion will be signed again after those modifications.
Extension processor invocation can't move inside the default saml assertion builder (i.e. before signing), since the response object should be needed for eidas extension processor to build and send a error response

This can be improved as performing any modification to the assertion before it gets signed.
[1] https://github.com/wso2-extensions/identity-inbound-auth-saml/blob/342cb8d5fc1ea2f1fff5f309379902db6e2f23eb/components/org.wso2.carbon.identity.sso.saml/src/main/java/org/wso2/carbon/identity/sso/saml/builders/DefaultResponseBuilder.java#L94
[2] https://github.com/wso2-extensions/identity-inbound-auth-saml/blob/342cb8d5fc1ea2f1fff5f309379902db6e2f23eb/components/org.wso2.carbon.identity.sso.saml/src/main/java/org/wso2/carbon/identity/sso/saml/builders/assertion/DefaultSAMLAssertionBuilder.java#L103

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


[ci] Use ubuntu-latest as runner

Description
Brief description of what this PR is about

If this change is a backward incompatible change, why must this change be made?
Interesting edge cases to note here

Codecov Report
Base: 72.08% // Head: 71.30% // Decreases project coverage by -0.78% :warning:

Coverage data is based on head (db00edb) compared to base (bb5073f).
Patch coverage: 70.94% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #2199      +/-   ##
============================================
- Coverage     72.08%   71.30%   -0.79%
- Complexity     5126     6334    +1208
============================================
  Files           473      629     +156
  Lines         21970    28044    +6074
  Branches       2351     3019     +668
============================================
+ Hits          15838    19996    +4158
- Misses         4925     6576    +1651
- Partials       1207     1472     +265

Impacted Files
Coverage Δ

api/src/main/java/ai/djl/modality/cv/Image.java
69.23% <ø> (-4.11%)
:arrow_down:

...rc/main/java/ai/djl/modality/cv/MultiBoxPrior.java
76.00% <ø> (ø)

...rc/main/java/ai/djl/modality/cv/output/Joints.java
71.42% <ø> (ø)

.../main/java/ai/djl/modality/cv/output/Landmark.java
100.00% <ø> (ø)

...main/java/ai/djl/modality/cv/output/Rectangle.java
72.41% <0.00%> (ø)

...i/djl/modality/cv/translator/BigGANTranslator.java
21.42% <0.00%> (-5.24%)
:arrow_down:

.../modality/cv/translator/ImageFeatureExtractor.java
0.00% <0.00%> (ø)

.../ai/djl/modality/cv/translator/YoloTranslator.java
27.77% <0.00%> (+18.95%)
:arrow_up:

...modality/cv/translator/wrapper/FileTranslator.java
44.44% <ø> (ø)

...y/cv/translator/wrapper/InputStreamTranslator.java
44.44% <ø> (ø)

... and 566 more

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

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


Fill in correct values for stimulus drift and shift corrections

As mentioned in #290, these fields have been added to config files but aren't yet correct:

[ ] Dataset 3

[x] audio_delivery_latency
[x] visual_delivery_latency
[x] tactile_delivery_latency
[ ] audio_delivery_shift_correction
[ ] #292
[ ] tactile_delivery_shift_correction

[ ] Dataset 4

[x] audio_delivery_latency
[ ] visual_delivery_latency
[x] tactile_delivery_latency
[ ] audio_delivery_shift_correction
[ ] visual_delivery_shift_correction
[ ] tactile_delivery_shift_correction

[ ] Dataset 4.1

[x] audio_delivery_latency
[ ] visual_delivery_latency
[x] tactile_delivery_latency
[ ] audio_delivery_shift_correction
[ ] visual_delivery_shift_correction
[ ] tactile_delivery_shift_correction

Note to people doing this
stimulus drift can be done using (trigger == 2)

I added some of these to visual-input-stream.
For tactile, these are set to as none as they are not relevant for the current datasets

Note that audio_delivery_shift_correction is correctly 0.0 for dataset 3 - we have the MISC channel and have confirmed there was no drift (luckily, as I don't think I would have noticed this if there was.).

Interestingly, the config for dataset 3 was incorrect anyway, and had the audio and delivery delays from 4, so good job you put this issue here Cai.

Completed as part of #290, tested and confirmed to mimic previous results.


CMP-2310: Remove CronJob beta API compatibility code

The CronJob API has been stable for a while, and there are no longer any
supported versions of OpenShift that also support the CronJob beta API.
This commit removes the complicated code we needed to ensure the
operator handled clusters with both versions.

/hold for test

/unhold
verification pass with 4.15.0-0.nightly-2023-11-19-195637 and 4.11.0-0.nightly-2023-11-17-114901

/label qe-approved


CASMTRIAGE-2096: Clarify Kubernetes NCNs in topics and add glossary entry csm 1.1

CASMTRIAGE-2096: Clarify Kubernetes NCNs in topics and add glossary entry csm 1.1

Closing this guy as csm-1.1 is kaput


Feature/Zitadel Postgres Integration

This PR provides an option to deploy netbird by the getting started script with the a PostgreSQL database by setting the environment variable ZITADEL_DATABASE to postgres.
Which will automatically add Postgres to docker compose file and setup Zitadel with it.
The PR fix some typos aswell.
Issue ticket number and link

#1785

Checklist

[x] Is it a bug fix
[x] Is a feature enhancement

Awesome PR, @r0b2g1t; thanks. We actually had in our roadmap to make Postgres the default for the installer. Can you update the following check to reflect that?
  if [[ $ZITADEL_DATABASE == "" ]]; then
    CRDB=$(renderDockerComposeCockroachDB)
    ZITADEL_DB_ENV=$(renderZidatelCockroachDBEnv)
  elif [[ $DATABASE == "postgres" ]]; then
    CRDB=$(renderDockerComposePostgres)
    ZITADEL_DB_ENV=$(renderZidatelPostgresEnv)
  fi

@mlsmaycon thanks for the remark. I have set Postgres as default and added echos for the user about the usage of the environment variable.

Thanks @r0b2g1t .
Can you also update the https://github.com/netbirdio/netbird/blob/main/.github/workflows/test-infrastructure-files.yml#L172 file with cockroachdb tests?

I will take a look into it and will try to create tests. :-)

Thanks @r0b2g1t .
Can you also update the https://github.com/netbirdio/netbird/blob/main/.github/workflows/test-infrastructure-files.yml#L172 file with cockroachdb tests?

I will take a look into it and will try to create tests. 🙂

@mlsmaycon I have added tests for psotgres and cockroach.

@mlsmaycon the tests are stable. May you can take a look into it and give feedback.

@r0b2g1t thanks again for the amazing contribution


Rings tool: Center Point parameter does not handle coordinates entered in Long Lat order (ArcGIS Pro)

The Coordinate Conversion tool was modified to allow users to enter in coordinates in both Lat Long and Long Lat order. All other tools that allow user to type in coordinates should allow the same.
Tool accepts coordinates to be entered in Lat Long...

Tool does not accept coordinates to be entered in Long Lat...

@elinz @nfeuerstein @kgonzago To do this correctly we will have to define a new field for user to define the format for incoming points. This requires ui changes. Lots of coding. Is this something we want to document and add as enhancement to version after next (same goes for all the other dd tools)?

@pHill5136 @nfeuerstein @kgonzago Maybe I'm missing something, but from my testing the tool already is handling how to interpret the input format.

The Coordinate Conversion tool was modified to allow lat/long OR long/lat.  Is this the same modification, but in Distance and Direction?  Or something more complex?

@nfeuerstein @elinz  @kgonzago I think the best way to do this is have a combo box that allows the user to define the input format for cases where it is not obvious the format needed (i.e points like (10, 0, 20.0)). To do this will require quite a bit of coding including ui changes that we want to avoid as much as possible at this time.

@pHill5136 Agreed. I suggest tackling any UI changes in our next release.

I have a fix for this locally which just reverses coordinates order when trying to parse lat long coords. I will hang on to this in case we need it. Same fix should work for all issues involving lat/long coord order: #216, #217, #218, #219, #220, #221, #222.

@rjones0 @kgonzago @nfeuerstein I think we should hold onto this for now. We will have to discuss exactly how we want to approach this for all the dd tools. For instance do we want long lat coords to be user defined i.e user tells us s/he is adding coordinates as long lat. Will have to turn off functionality when not using decimal coordinates also might consider turning off map point tool when entering long lat.

@rjones0 @pHill5136 sorry for the late reply and am not ignoring the suggestion. We have a meeting to discuss the lat/long and long/lat issue. Decisions made from that meeting will dictate how this issue will be resolved.

Addressed in #495

This cannot be finished until the Distance and Direction documentation topics are versioned and released

Removing - QC Verify (Checklist) tag as this issue has already been marked with a E- Verified tag. FYI @topowright

Removing "Known Issue" label as this has now been addressed and is listed in the "Issues Addressed" section of our release notes.

removing the closing label, e-verified. This is not published and able to be tested on dev.


Fix CI test breakage

This renames an integration test and the associated scenario folder to come in under the path length limit that we were hitting on Appveyor.

Thx


Color picker is far too wide and does not remember when I resize it smaller

This was discussed a little in #178670, but I'm not sure I totally understand the logic behind it sometimes not saving my size. Additionally, it now seems even wider than it was back then.
https://github.com/microsoft/vscode/assets/1078012/e4ed2947-e391-4834-a899-c0f13559cc12

Hi @DanTup thank you for posting this issue. I see how the sizing that is rendered can be confusing. So far we have decided to use the strategy I described in https://github.com/microsoft/vscode/issues/178670, but we may decide to implement a way to remember size per token location.

@aiday-mar I'm still not sure I understand. Even if it can't persist, why can't it have a smaller default size?

const currentMaxWidth = Math.max(this._editor.getLayoutInfo().width * 0.66, 500, lastWidth);

This line looks like it will always take at least 66% of the width of the editor. Is that intended? This seems kinda silly if you only have a single file open and are on an ultrawide monitor (it would be even worse on a super-ultrawide).

Yes that is a good point, we'll look into it when there is time

Hi I am trying to reproduce the error, but when I make the color picker appear it appears normal sized. Could you please post the example in the GIF here? What type of language is this? Are you perhaps using some extensions related to this language that could be affecting the color picker?

Hi @DanTup I am trying to reproduce this issue. I believe this should be reproducable with the right extensions installed (since they provide the colors). With the main Flutter and Dart extensions, I am currently not able to reproduce this issue. Could you share please the extensions you are using?

I don't think it's caused by other extensions, but here's the list:
PS C:\Dev> code --list-extensions
amodio.tsl-problem-matcher
Dart-Code.dart-code
Dart-Code.flutter
dbaeumer.vscode-eslint
dcmdev.dcm-vscode-extension
esbenp.prettier-vscode
GitHub.copilot
GitHub.copilot-chat
googlecloudtools.cloudcode
ms-vscode-remote.remote-containers
ms-vscode-remote.remote-wsl
ms-vscode.powershell
ms-vsliveshare.vsliveshare

Can you provide a screenshot of what you see, and confirm which version of the Flutter SDK you're using? The SDK version is shown in the language status area:

(the colours won't show up without a Flutter extension because they're coming from the Dart LSP server).

Hi @DanTup thank you for the explanation. I was finally able to reproduce the error. I will look into it.

I have looked at the code and it appears this happens in the case when in the hover there is a color picker and there is markdown content. When there is markdown content, the hover will assume the natural width of the markdown content thereby stretching the color picker. A fix here would be to limit the width of the hover when a color picker is present. This however means that the markdown content below the color picker will be squeezed into a smaller space.

I reduced the repro to just this:

/// These colors are identified by their transparency. The low transparency
/// levels (e.g. [Colors.white12] and [Colors.white10]) are very hard to see and
/// should be avoided in general. They are intended for very subtle effects.
class Aaaaaaaaa {}

void f() {
  Aaaaaaaaa? a;
}

For some reason the hover does not want to wrap that paragraph, and makes the hover really wide.

So according to the equation in https://github.com/microsoft/vscode/issues/199944#issuecomment-1838645790, the width has a maximum can be up to the editor width times 0.66. Would you say that this roughly corresponds to what you are seeing? Is the hover width indeed 2/3 of the editor width?
We can consider making that fraction smaller in order to avoid cases like yours.

Actually, to be clear - the real issue here isn't so much the maximum size - it's that if I resize it to be 1/3 of the current size, then it does not persist that.
I could live with the defaults being bad if it at least saved when I tried to resize it smaller. The issue here is that I have no way to fix it, they'll always expand to this size.

Hi thanks for the clarification. Yes those are all good points. IMO we should make the hover persist on a per token basis like you mentioned, which would be more intuitive. There have been some discussions in the team, and overall the consensus was to keep the current persistance mechanism as is. I will work on a PR to make the defaults smaller than what you showed, this should at least improve the experience.

IMO we should make the hover persist on a per token basis like you mentioned, which would be more intuitive.

Depending on what you mean by "per token", that might not be what I was asking for. I don't want to see this same overly-wide hover/color picker as I move around the code. I'd prefer there was just a single size for a) all hovers and b) all colour pickers, and when I resized one, the next one was that size regardless of where it was.
However, if the defaults were more reasonable, I'd probably care less about that. It's just really annoying to have to move my mouse so far 😄
That said - I'm now wondering why the hover content affects the width of the colour picker anyway. Why can't the hover by wider (for the documentation) without causing the colour picker to stretch? I don't think anyone would really expect the aspect ratio of the colour picker to vary depending on the documentation comments of the class next to the colour picker? 🤔

Yes we have considered making the content hover the same size for all hovers but that would not look good because content hovers are of different sizes. Consider the two following hovers, we can not equate them:

I think we can make the color picker have a fixed size and always center it in the middle, but I think that some users explicitly want to increase the size of the color picker in order to better see the colors. I am not sure if we should make it fixed size.
Like you said however the color picker size currently varies with the documentation comments below it, so we can decide to force a smaller rendering width when a color picker is present in the hover. If there is a color picker, the content hover will be smaller size.
Additionally we can decrease the defaults

Yes we have considered making the content hover the same size for all hovers but that would not look good because content hovers are of different sizes. Consider the two following hovers, we can not equate them:

Can't you have a default/user-persisted hover size and then just shrink it if the content is small (but do not overwrite the user-persisted preference when you do this)? If I resize a hover, I would really not expect it to persist that size for that one very specific token in that file. Almost every time I invoke a hover it will be in a different location, so it seems like my "preference" would almost never be used?

I think we can make the color picker have a fixed size and always center it in the middle

Why center it? My concern here is how far I have to move my mouse so far from where I hovered to select a color and centering it won't solve that problem.

but I think that some users explicitly want to increase the size of the color picker in order to better see the colors

Hmm, that's fair. Maybe the real issue here then is that the colour picker and hover documentation are being lumped together... Is there a great benefit in showing the doc comments hidden below the colour picker? If they weren't there, the width of the colour picker and the width of documentation hovers would be less tied together.
Although again, my real issue here is with the incredibly wide default rendering.. I suspect all these other gripes would be less of a problem if the default was better :)

I see yes that is an idea. Currently when one changes the size, it persists the current size as the new upper bounded size. If the next hover is smaller it assumes a smaller size, if it is bigger, it is limited by the previous upper bounded size. I think you are suggesting to have maybe some sort of setting of type maximum natural width and height of hover which would take two entries for the width and height, and these could be used instead? I opened a feature request here to track this https://github.com/microsoft/vscode/issues/200356
I don't think we are currently planning on separating the color picker from the markdown content in the hover. If you feel this is a feature you would really like to see in VS Code, you may open an issue and we can discuss this there.
I opened a PR here https://github.com/microsoft/vscode/pull/200355 in order to change how the default maximum natural width and height are calculated. The calculation is as follows:
const height = Math.max(Math.min(this._editor.getLayoutInfo().height / 4, 400), ContentHoverWidget._lastDimensions.height);
const width = Math.max(Math.min(this._editor.getLayoutInfo().width * 0.66, 800), ContentHoverWidget._lastDimensions.width);

In particular this means that the width and height will never be bigger initially than 800 pixels and 400 pixels respectively, even if you have a very wide editor.
This calculation can be combined with the setting I mentioned earlier, so one could tweak the values 400 and 800 through the settings.

Hi @DanTup after some discussion with the team, we decided to limit the width of the color picker to a certain maximum width, even if the hover is larger. We will be going forward with this decision.

we decided to limit the width of the color picker to a certain maximum width

Do you mean an absolute value? And not "some % of the editor width"? If so (and it's not a huge value), that sounds good to me :-)

So I think we will set an absolute maximum value on the color picker

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Way to expose resources attributes in a data to allow grafana and prometheus providers to work nicely

Yes ✅: managed grafana and managed prometheus

Is your request related to a problem? Please describe.

When trying to provision grafana using grafana provider I cannot do it in the same terraform run, the common provider issue of resource not being known at the creation time for provider to refresh state, or being deleted on a destroy which results in some resources being orphaned in the terraform state making it invalid.
Describe the solution you'd like.

Right now both prometheus workspace data type, and grafana workspace data type are being found by id. ID is not in the outputs. It would also be preferable to be able to find those by { Tag = Name } rather then just by the id which allows other terraform runs to get those without creating a file just to pass id in between or read it directly from terraform stat (sic!)
Except for being able to find a resource using data query by name it would also be preferable if grafana api keys would be in the attributes as well. Meaning other terraform run can get those staticly in the provider definition.
Something like this:
data "aws_grafana_workspace" "example" {
  filter {
    name   = "name"
    values = ["$MYENV-GRAFANA"]
}

provider "grafana" {
  url  = "https://${data.aws_grafana_workspace.example.endpoint}"
  auth = data.aws_grafana_workspace.example.auth_keys.admin.json
}

Describe alternatives you've considered.

Additional context

you will want to open this question on the provider https://github.com/hashicorp/terraform-provider-aws
We can only support what the provider supports


Documentation on adding tile layers

Is there any documentation on how to add a tile layer to the map?
have tried
M.add_layer("layername","http://tiles{0-3}.basemap.com/url/{z}/{x}/{y}.png")

But it looks like the layer that gets added is requesting:
http://localhost:8888/notebooks/notebooks/null/9/8/4.png etc

@digitaltopo  Try running:
M.add_layer(None, name="layername",
            vis_url="http://tiles{0-3}.basemap.com/url/{z}/{x}/{y}.png")

This should add a layer to the map which has no data associated with it.

Thank you, this works for the most part although the tile subdomains are being parsed as %7B0-3%7D and an extra set of z/x/y.png is being added to the end of the base url.
Leaving off the {z}/{x}/{y}.png} in the base url makes this work, as geonotebook is adding it by itself:
http://tiles0.basemap.com/url/
How can we pass the subdomain range?

can you try
http://tiles{s}.basemap.com/url/

I tried {s} as well, and it's still encoding the {s}.

Can you try running
M.add_layer(None, name="layername",
            vis_url="http://tiles{0-3}.basemap.com/url/{z}/{x}/{y}.png",
            vis_params={layer_type: "osm"})

Without the layer_type parameter it auto-adds the /{z}/{x}/{y}.png and uses the rest as is rather than as a template.
To set the subdomains after that, you should be able to add
M.layers["layername"].subdomains("0123")

or
M.layers["layername"].subdomains(["0", "1", "2", "3"])

The M.layers["layername"] object is from the python API, which doesn't expose a way to set subdomains.  That would have to be added to the RPC spec to call the javascript method on the layer object to work.

I tried {s} as well, and it's still encoding the {s}.

I see so I guess something is not send rightfully to GeoJS.
@jbeezley would you like to look into it bit more?

As I mentioned, setting the subdomains in a way supported by geojs would require extending the RPC spec.  Even better, we could add support for the {a-c} syntax in url template strings; the openlayers renderer should work with this kind of template parameter without any changes.

It'd be quick to extend the url template syntax.  Until then, a url with an explicit subdomain can be used; it won't benefit from the distribution across subdomains, but it will work.

@jbeezley @manthey roger that. @jbeezley @manthey are you interested/has time to extend the RPC spec? Ping me over the email if you have questions on non-technical related matters.

I'm extending what we accept as subdomain template strings in geojs, and should have a PR there shortly.  Currently, if you use the vis_params={layer_type: "osm"} and a string with a fixed subdomain (e.g., vis_url="http://tiles0.basemap.com/url/{z}/{x}/{y}.png"), I believe it will work right now.  The templated ranges will be supported once the PR is merged in geojs and we update the geojs version in geonotebook.

Reference https://github.com/OpenGeoscience/geojs/pull/715.

@digitaltopo we have fixed the issue on the Javascript side of things (thanks to @manthey and @jbeezley ). Could you please try the latest version of the GeoNotebook (master as of few minutes ago)? and provide us any feedback.

Thanks @aashish24 et all!

I have updated GeoNotebook  (pulled master branch, ran install scripts) but still seem to be seeing the same behavior:

Here is my code:
# Basemap Base Url
basemapUrl = "https://tiles{0-3}.domain.com/pathtotiles/{z}/{x}/{y}.png"

# Query Parameters
basemapQueryParams = {"api_key": MY_API_KEY}

# Base Map Vis Parameters
basemapVisParams = {"layer_type": "osm"}

# Add the basemap layer
M.add_layer(None, name="basemap",
            vis_url=basemapUrl,
            vis_params=basemapVisParams,
            query_params=basemapQueryParams)

In my network tab, I'm still seeing the following issues:

Curly braces in the basemap url are being encoded, resulting in: ...%7Bz%7D/%7Bx%7D/%7By%7D...
The z/x/y.png suffix is appended to the url again: ...%7Bz%7D/%7Bx%7D/%7By%7D.png/3/8/4.png
The subdomain prefixes are also being encoded, and apparently not parsed: https://tiles%7B0-1%7D...
The query_params don't seem to be added to the requests

Additionally, when I tried passing a base url using a fixed subdomain, and left off the x/y/z.png:

https://tiles1.domain.com/pathtotiles
I get imagery responses, but the resulting tiles displayed on the map are all wrong, and it looks like it's requesting images with a variety of Z values while I am not zooming (I'm looking at network requests while panning the map).
This results in a pretty funny looking map :)

These may be two separate issues.
I'm going to dig around the source and see if I can figure out what's going on. Appreciate any help!

@digitaltopo sorry to hear this @manthey any ideas why would it not work as expected (see 1. above)

@digitaltopo This works for me:
M.add_layer(None, name="layername",
            vis_url="http://tile.stamen.com/toner-lite/{z}/{x}/{y}.png",
            layer_type="osm")

Note that instead of vis_params=, we specify layer_type=.

@kotfic I don't see how query_params gets processed in any way -- it looks like the created layer has a query_params property, but the NoDataLayer doesn't set it from the add_layer function, and setting it after layer creation doesn't update the javascript side of things.  Maybe I'm missing something.

@manthey Thanks!

Adding layer_type="osm" as an argument itself did the trick.

For any future reference, layer_type is it's own parameter instead of a property on vis_params. Thanks for clearing that up!

The subdomain still has issues, it seems that the only valid input that's being respected is {s}, anything else gets encoded, and therefore isn't making it to GeoJS's subdomain parser, so I'm unable to use a subdomain like {1-3}. It appears that using {s} results only in subdomains a,b,c.

@manthey @kotfic I don't see query_params in the NoDataLayer either:

class NoDataLayer(GeonotebookLayer):
    def __init__(self, name, remote, vis_url, **kwargs):
        super(NoDataLayer, self).__init__(name, remote, None, **kwargs)
        self.vis_url = vis_url

On a docker version build from current master, subdomains work for me:
M.add_layer(None, name="layername",
            vis_url="http://{b-c}.tile.openstreetmap.org/{z}/{x}/{y}.png",
            layer_type="osm")

only gets tiles from the b and c subdomains, and {1-3} asks for tiles from subdomains 1, 2, 3.
How did you update your deployment?  If you are running locally, what version does npm list show for geojs?

I'm running locally, I pulled git master branch .
"geojs": "^0.12.2" in /geonotebook/js/package.json

To update the client code, you will need to rerun client build.  The exact procedure depends on how you installed it.  If you did a normal install, it should be sufficient to rerun pip install ..  If you did a development install, then you'll want to go into the js subdirectory and run npm install && npm run build.

Thanks @jbeezley this is the process I followed. At this point the OSM style layer works for me as expected.
I'm only unable to specify custom subdomains like {1-3}. Using {s} in the url produces a-c subdomains but my tile server uses tiles1.domain tiles2.domain etc. When passing anything other than {s} I'm seeing requests that look like this: https://tiles%7B1-3%7D.domain...
The same is true when I use the example @manthey posted above:
"http://{b-c}.tile.openstreetmap.org/{z}/{x}/{y}.png" --->
http://%7Bb-c%7D.tile.openstreetmap.org/4/6/8.png
results in url encoded {s}
while
"http://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png" -->
http://b.tile.openstreetmap.org/14/13015/5547.png
works as expected.
Can you give any background on how the vis_url gets passed to geojs, as it seems that somewhere the contents of {s} are being url encoded if a custom subdomain scheme is used.

My guess is that for some reason you are not getting the newest version geojs in your build.  There are occasions where npm install won't actually update to the correct package versions.  You can check the version that is installed by running npm ls geojs in the js subdirectory.  If it still has a version < 0.12.2, then you might try deleting the node_modules directory and reinstalling.

To be clear what version should I expect? Geojs is listed as ^0.12.2. I'll reinstall and rebuild.

The latest is 0.12.2.

@jbeezley Thanks! Got it all working now. When reinstalling I used the --upgrade --force-reinstall flags for pip install. Maybe this was the oversight on my part. Thank you all for your support!

Great!  I forgot that pip will refuse to upgrade if there wasn't a version change.


Docs: Phantom wallet support

🔎 Have you searched existing issues to avoid duplicates?

[X] I have made sure that my issue is not a duplicate.

🧪 Have you tested your code using latest version of Synpress?

[X] I have made sure that my issue still exists on latest version of Synpress.

💡 Are you able to provide enough information to be able to reproduce your issue locally?

[X] I can provide enough details to reproduce my issue on local environment.

Synpress version
"^4.0.3"
Node.js version
v22.11.0
Operating system
15.0
Run mode
Playwright + Synpress (as plugin)
CI platform (if applicable)
No response
Are you running your tests inside docker? (if applicable)

[ ] This issue could be related to docker.

What happened?
Documentation does not have phantom(solana) related integration. Although the home page of synpress shows phantom as its available integrations.
So where are the docs??
What is your expected behavior?
No response
How to reproduce the bug.
Check documentation
Relevant log output
No response

Contact the Support page to resolve your error.
Note: You can also initiate a chat with the live agent on the chat button to get more information about your request via Live Chat
@kr-keshav-kk
Support.

Related:
https://github.com/synthetixio/synpress/pull/698


How to update a CSG Operation

Description:
I am tying to update an operation live while the scene is running, here's my mesh thats using the operation:
function createMesh() {
  const loader = new GLTFLoader();

  const dracoLoader = new DRACOLoader();
  dracoLoader.setDecoderPath("/examples/jsm/libs/draco/");
  loader.setDRACOLoader(dracoLoader);

  loader.load(
    "https://cdn.glitch.me/dc99a522-a347-4f3e-a04f-210e55dccd91/Tall%20Base%201.glb?v=1709712049776c",
    function (gltf) {
      result = gltf.scene.children[0];

      let resultMaterial = new THREE.MeshPhongMaterial({
        specular: 0x111111,
        shininess: 5,
        side: THREE.DoubleSide,
        alphaToCoverage: true,
        stencilWrite: true,
        stencilRef: 0,
        vertexColors: true,
      });

      result.material = resultMaterial.clone();

      meshBrush = new tbc.Operation(result.geometry, resultMaterial);
      {
        inside = new tbc.Operation(
          new THREE.BoxGeometry(10, 10, 10),
          resultMaterial
        );
        meshBrush.add(inside);
        inside.operation = tbc.ADDITION;
      }

      mesh = csgEvaluator.evaluateHierarchy(meshBrush);
      {
        const colorArray = new Uint8Array(
          mesh.geometry.attributes.position.count * 3
        );
        colorArray.fill(255);
        const colorAttr = new THREE.BufferAttribute(colorArray, 3, true);
        colorAttr.setUsage(THREE.DynamicDrawUsage);
        mesh.geometry.setAttribute("color", colorAttr);

        mesh.geometry.boundsTree = mesh.geometry.computeBoundsTree();

        //Center the model
        mesh.scale.set(1, 1, 1);
        let bounds = new THREE.Box3();
        bounds.setFromObject(mesh);
        mesh.position.sub(bounds.getCenter(new THREE.Vector3()));
        mesh.updateMatrixWorld(true);
        //Scale model to 100

        bounds = new THREE.Box3().setFromObject(mesh);
        let size = bounds.getSize(new THREE.Vector3());
        let { max } = Math;
        let maxsz = max(size.x, max(size.y, size.z));
        mesh.scale.multiplyScalar(1 / maxsz);
        mesh.needsAutoUpdate = true;
        bounds.setFromObject(mesh);
        mesh.position.sub(bounds.getCenter(new THREE.Vector3()));
      }
      mesh.material = result.material.clone();
      mesh.geometry.computeBoundingBox();
      scene.add(point);
      point.add(mesh);
    }
  );
}

What I need:
I am trying to change the operation of the inside mesh using inside.operation = tbc.SUBTRACTION with the help of a GUI button, is that possible? If so can anyone explain how it works in detail cause I am new to this CSG stuff.
Thanks

Video:
https://github.com/gkjohnson/three-bvh-csg/assets/58696726/f292620f-d584-4650-926a-a64ea4122e16
Description:
The cube shown in the video is a three-bvh-csg Operation mesh, I want its operation to be updated to SUBTRACTION when I switch the hollow type to 1 or to ADDITION when I switch it to ADDITION. After switching if I do console.log(inside.operation) I get  0 as the result for addition and 1 for subtraction.
Observation:
I have observed that doing inside.operation = tbc.ADDITION and doing inside.operation = 0 are performing the same action, it's the same with subtraction but the number is 1
Thanks for replying to my issue though

Please - a live example. This means something working and editable. Not a video.

Oh my bad here's the code editing platform: https://glitch.com/edit/#!/teeth-important

As in my previous comment:

Ie no loaded models, etc so it's clear what the code flow is.

Unfortunately I cannot spend time dissecting almost 500 lines of code to understand what's happening. Please provide a minimal example that shows only the issue you're running in to which does not require a model, drawing interactions, rotations, etc.

For that let me make a new code and share the link here

Thanks for the help man, that was a minor yet dumb mistake


Live Activity Counts displaying incorrectly

Description: The Live Activity count, as part of the Internal and Public Reports, is showing activity prior to the Engagement Page being published & live to the public.
Summary: There is a count of "2" for August 2023 and "2" for September 2023, but the page wasn't published until October 4.
Steps to Reproduce:

Engagements > look to Coyote Hydrogen - Early Engagement
Hit Actions dropdown > select View Report - Public or Internal
Scroll to see Live Activity > notice August/September

Expected Result: There should only be Live Activity since the Engagement Page went live
Actual Result: There are 4 counts of mystery data, appearing under August/September, which should not be possible
Environment: PROD
OS: Windows
Device/Model: Lenovo ThinkPad Laptop
Browser (if applicable): Edge
Attachments:

Obsolete data in the system, erroneously being included in this survey result, has been successfully purged and rectified.


[openssl] Revise jom/nmake support

What does your PR fix?
Uniformly use plain vcpkg_build_nmake for windows incl. nmake, leveraging the recently integrated PREFER_JOM with nmake fallback. This fallback should mitigate issues with running jom on some computers.
It also cherry picks a post-3.0.7 fixup from #27618.
PR history:
Based on various issues reported for building port openssl on windows, this PR started as an attempt to build openssl without jom using plain vcpkg_build_nmake but turned into a revision of this script to integrate parallel build capabilities using jom. These script changes were merged as https://github.com/microsoft/vcpkg/pull/27255.
Some past pushes also tested de-duplicating steps shared by the unix and windows branches.
But now this PR is trimmed.

Which triplets are supported/not supported? Have you updated the CI baseline?
unchanged, no

Does your PR follow the maintainer guide?
yes

If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?
yes

We probably won't remove jom due to build time with nmake, but there is still enough to take from this PR:

General port cleanup
Merge uwp rules into windows rules

There is still room for improvement, in particular where I don't know enough about the MSVC toolchain:

More clear resolve the PDF/-Zi/-Z7 handling?
Filter the -MP from concurrent builds (' jom')?

Hm, I think I pass the same options to jom and nmake, but CC (full path) arrives only in nmake log files, not jom makefiles.
OTOH, I wasn't able to create a minimal reproducer with jom and echo $(CC) :angry:

The current opencv4 regression is expected to be fixed by #27239.

Depends on #27255.

Thanks you!


Link pricing information from service plans

Note:
Service plans impact pricing. Pricing information is available via Discovery Center and SAP Cloud Logging Capacity Unit Estimator

The documentation was changed accordingly and is now available in the draft version Service Plans .

Same issue as https://github.com/SAP-docs/btp-cloud-logging/pull/19#issuecomment-2461698294


Using domain (Route53) : all query parameters are cleared!!

Note: If your question is regarding the AWS Amplify Console service, please log it in the
AWS Amplify Console repository

Which Category is your question related to?
Domain Route53
Amplify CLI Version
7.6.9
You can use amplify -v to check the amplify cli version on your system
What AWS Services are you utilizing?
Route53
Provide additional details e.g. code snippets. Be sure to remove any sensitive data.
I've registered a domain in route53, then add it into amplify app.
The problem is if I don't put www in the URL, then all query parameters are cleared.
for example
don't work :
https://abcdef.com/xxx?yyy=zzz

works
https://www.abcdef.com/xxx?yyy=zzz

Please help.

Hey @lehoai :wave: thanks for raising this! Transferring this over to Hosting to get some more eyes on it 🙂


Dark theme is unusable

Describe the bug
When I visit "Live Examples > 4.0 > React Official" the font/input element contrast is atrocious, rendering the whole example website completely unusable.
I poked around a bit but couldn't find anything in the code, did someone forget to include the lightening parts of the dark theme?
To Reproduce

Go to https://storybook.js.org/basics/live-examples/
Click on any of the 4.0 examples that use the dark theme (React, specifically)
Wait for page to load
Try looking at the "Components > Form > Select" as a specific example

Expected behavior
I should be able to read the text of the select element.
Screenshots
Firefox 64.0

Chrome 71.0.3578.98

System:

OS: Windows 10
Device: HP Pavilion
Browser: Chrome and Firefox (versions noted above)
Version: 4.0

Fixed in v5


Changed advertised listener of kafka

When we create a kafka adapter in streampipes, it fails with the following message in the schema generation step.
System error while guess the schema of the data ;  Connect Worker<EMAIL_ADDRESS>is currently not available. Sorry, something went wrong! Hit the feedback button (top right corner) to ask for help. If you think you’ve found a bug, fill an issue on our Github Page
Also, in the logs of docker image of connect-main, the following message was coming
10:26:26.415 SP [Thread-6] WARN  o.apache.kafka.clients.NetworkClient - [Consumer clientId=b1810568-12ba-43d5-a6ed-770828f823f2, groupId=ea8a814c-56b1-4fa0-8539-c313ab60453a] Connection to node 1001 (localhost/<IP_ADDRESS>:9094) could not be established. Broker may not be available
After this fix, all the errors were resolved.

Hi @ashishmalgawa thanks for the PR! This is a weird behaviour since we rely on this OUTSIDE kafka listener interface for development purposes, e.g. for pipeline element development when we run Kafka and StreamPipes backend inside Docker and develop in the IDE (e.g. IntelliJ).
May I ask how you created the kafka adapter in StreamPipes connect? What are your settings, e.g. kafka broker host and port

I used "kafka" as broker address, and port "9094"

I see. can you try the following:
broker hostname: kafka
port: 9092
Other than that, we currently deploy data sources simulating event stream such as the flowrate sensor 1 & 2 that are are part of the lite version. If you use the CLI you see the entry sources-watertank-simulator templates/lite that linkes to the corresponding docker-compose file in services/sources-watertank-simulator/docker-compose.yml.
This is a simulated data stream that is already available as a data stream (source) within the pipeline editor and ready to be used. So there is no need in connecting it again to via StreamPipes connect.

@ashishmalgawa I close this PR as I don't see an issue with the kafka listeners. If this should still be relevant, we can reopen it.


[build-script] Overzealous path expansion

Purpose
This PR fixes some overzealous path expansion for the --build-subdir argument which attempts to expand the build subdirectory path as much as possible due to changes introduced yesterday by #13231. When the path is expanded out to an absolute path it will then cause all build directories to generate relative to where build-script was invoked, rather than the standard build directory above the Swift workspace.
rdar://35913659

@swift-ci please test


Improvements for CMakeLists.txt

added support for build 32-bit and 64-bit in one pass

added options to disable building libarary and tests

update README with better instructions for 64bit

drop cmake requirement to 3.5 (still higher than needed...)

use find_path to locate wine include directory

enable -Wall -Wextra and suppress existing warnings

fix compilation error with array initialization on gcc5

remove executable bit from source files

Thanks a lot, very nice improvements !


IUS Support has some issues

When running an ius simulation, the directory with the makefile is "dirtied" with several files that should be up in the sim_build folder.
Also, I noticed that the "results.xml" is not located in the same location as in the questa and aldec simulations.  In IUS the "results.xml", ends up in the same directory as the makefile.  In questa and aldec, the "reulsts.xml" ends up in the "sim_build" folder because of the change directory command that happens before running the sim.
@chiggs and @stuarthodgson What folder should results.xml be located in at the end of the simulation?  Currently it looks like ALDEC and Questa may behave differently.  And from the way the makefiles are, it seems like you want it to be in same directory as the makefile so the simulation won't run again if nothing has changed.
Also, I have noticed that there is an issue with vhpi simulations.  When starting from a clean build, if I run an VHPI simulation first, the test will always fail.  I see the following error message "VHPI ERROR: Registered callback isn't enabled!  Got 1000" in VhpiCbHdl.cpp:214.  I run the same test again without cleaning using VPI and it passes successfully.  I then run it one more time without cleaning, but this time targeting VHPI and works.  Something odd is happening that doesn't allow VHPI to work unless VPI sim has been run first.

As for the last issue, it looks like there is just an issue with VHPI.  When I thought the VHPI test was passing, that was actually the VPI interface working again.

@leftink , Taking the endian_swapper as an example, yes there is indeed something "odd" with IUS. I also seem not to have documented it anywhere. The IUS implementation of VHPI is far from complete. We can not query the state of a callback for instance. This leads to the the error
VHPI ERROR: Registered callback isn't enabled! Got 1000

at the start of the simulation, VCS and Aldec work fine in this regard. The outcome of this is that on IUS the VHPI interface can only be used to modify values and read them back. Therefore a mixed language simulation will work fine as the VPI interface can be used to do the scheduling.
The current implementation will use the first registered interface layer as the scheduling one and IUS helpfully always loads VPI even under vhdl tests so that sort of works, but again only for mixed language. We also only use the first interface to obtain the root handle so in the endian_swapper test with TOPLEVEL_LANG=vhdl we do not work.
I do have some patches that no longer checked the state of the callback once we arm it, none of the the other interfaces implementations do this so seems safe enough. But then another problem with IUS hits, that the way it schedules events is different to VPI and seems wrong. A value change will result in a callback to before the function to modify the value has returned.
Since we are not IUS users and the only person we are aware of was using mixed language and so did not see these problems it has been on the back burner.

@stuarthodgson That is fine, we aren't big users of IUS anymore either, but it was the only simulator I had that would let me do VHPI.  I think we are will be able to do some testing with Aldec in the next month or two so I can just wait until then.
What about the issue with the makefile?  Where are you guys expecting the results.xml to be located?  I have a feeling that the Aldec and Questa makefiles need to be fixed.
@chiggs and @stuarthodgson I also dug into the issue with IUS always loading the VPI interface regardless if it is told to or not.  It looks like IUS has a "feature" that it will search the shared libraries in its path and if any have the symbol "vlog_startup_routines[]" defined they will be automatically loaded.  According to their documentation if you want to control loading through the command line then this symbol shouldn't be present.  What would you guys think of adding a compile flag that will name mangle the "vlog_startup_routines" symbol?  Then we can load things normally for IUS.  I did a quick test with the name mangling and everything worked as expected.

@leftink , we already have a -DIUS as there is another feature where they ignored the standard for VHPI and changed a structure members type, took a while to find that feature. So doing some name mangling based on that #define should be pretty easy. We where doing so well at not having any simulator specific features until IUS as well.


want to add a STICKY NAV BAR

@AnshSinghSonkhia could you pls assign me this issue

Hey , I came across this issue and would love to work on it.
Could you confirm if it's still open? If available, could you please assign it to me?


[Haxe][ASFileParser] Fixed parsing of regex after a 'switch', 'try'. fixes #1841

this is another more complicated problem, if I start solving them all at once, it will take a very long time and there will be a lot of change.
I know more than 10 of these options.

Done.
The parsing of single-line functions I will be make separately.

This seems a bit hacky and quite probably there are better ways of solving this problem, but it could be investigated later.


 IF YOU DO NOT FOLLOW THE FORMAT OR MAKE A GENERIC TOKEN REQUEST YOUR ISSUE WILL BE DELETED WITHOUT COMMENT
YOUR JUSTLIST MUST FOLLOW THE JSON SPECIFICATION
https://github.com/justswaporg/justlists/example.justlists.ts
Checklist

[x] I understand that this is not the place to request a token listing.
[x] I have tested that my JustList is compatible by pasting the URL into the add a list UI at justswap.org.
[x] I understand that filing an issue or adding liquidity does not guarantee addition to the justlists website.

Please provide the following information for your token.
JustList URL must be HTTPS.
JustList URL:
JustList Name:
Link to the official homepage of the JustList manager:

I can't find out few tokens with add addresses. Like Kodx,KIH etc..please fix the issue.

This is not the place to open this type of report, nor to list any token

please close this issue

Sorry for wrongly doing this activity.
On Fri, 9 Jul 2021, 19:16 Steven Cabrera Londoño, @.***>
wrote:

please close this issue
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/justswaporg/justlists/issues/1555#issuecomment-877201441,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQZXTF7KRAHBGEH5X3ZF3ITTW34SFANCNFSM5ACFHUVA
.


Donut view for node states

It would be great to be able to visualize node states with a donut view (like Foreman).
This can easily be achieved using c3js (already used in Puppet board): http://c3js.org/samples/chart_donut.html
I would assign this to myself, just as a reminder to code it someday (unless someone else wants to do it).

Where exactly is this visual desired? Im seeing a place for one in the overview page displaying the information for the failed, changed and unreported information. Anywhere else?

I'm thinking of the overview page indeed. Maybe a donut of resource types in the node view/report view too.

The Overview page is not a problem, the node/report views however need some work in order to be more efficient.
It can definitely be done after https://github.com/voxpupuli/puppetboard/issues/202

Because the 0.2.0 release will include massive software updates I feel it is best to delay this request until a future release. Hopefully still in the 0.2.x releases.
I'm sorry for the continuing delay.

Is this still desired?

Haven't worked on it, but it could certainly be nice.

I think a better option is a bar chart of daily runs: #308

I've updated the default_settings.py so that this can now be configured.  We may want to come back and add something to the GRAPH_FACTS array so that you can specify the type of graph you want per fact.


internal: split panic test

This PR moves all panic tests into a separate file and uses conditional compilation to ensure they are only available on non-native backends.

Pull Request Test Coverage Report for Build 3352
Details

0 of 0   changed or added relevant lines in 0 files are covered.
18 unchanged lines in 7 files lost coverage.
Overall coverage increased (+0.08%) to 83.337%

Files with Coverage Reduction
New Missed Lines
%

immut/priority_queue/priority_queue.mbt
1
84.0%

priority_queue/priority_queue.mbt
1
86.44%

builtin/byte.mbt
1
86.67%

immut/array/array.mbt
1
93.83%

queue/queue.mbt
2
92.42%

deque/deque.mbt
4
87.88%

immut/list/list.mbt
8
78.81%

Totals

Change from base Build 3351:
0.08%

Covered Lines:
4106

Relevant Lines:
4927

💛  - Coveralls


Minor housekeeping related to deprecated methods

Might be  cleaner to put these in the deprecated.jl file? If you think it's more logical to keep it as is feel free to close!

Current coverage is 80.20% (diff: 0.00%)

Merging #28 into master will not change coverage

@@             master        #28   diff @@
==========================================
  Files             5          6     +1
  Lines           293        293
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            235        235
  Misses           58         58
  Partials          0          0

Powered by Codecov. Last update a89539e...dc07295

LGTM! :+1:


Update compat for upcoming Ferrite release

xref: https://github.com/Ferrite-FEM/Ferrite.jl/pull/668

Fixed with 910f589cac313422313996377ac09d765e0ecb68


Write docs on how to do testing

Need to document 2 ways:

Exercise the device directly, i.e. call device.read() and inspect the output. Should use helpers made in #199
Run a plan in the RunEngine and examine the docs. Use a pattern like:

from collections import defaultdict

def assert_emitted(docs: Dict[str, list], **numbers: int):
    assert list(docs) == list(numbers)
    assert {name: len(d) for name, d in docs.items()} == numbers

def test_plan():
    docs = defaultdict(list)
    RE(plan(), lambda name, doc: docs[name].append(doc))
    assert_emitted(docs, start=1, descriptor=1, resource=1, datum=1, event=1, stop=1)

There is an existing docs page on testing that we can add to: https://blueskyproject.io/ophyd-async/main/user/how-to/write-tests-for-devices.html


Fix Go dependency with new module name

Since this repo was moved from another repo, I found some of the Go dependencies were still using previous package name. These names should be updated with new module name.

Please assign this to me. I'll fix it.

@mlycore Assigned.

Finished.


Encrypted password and 403 Forbidden error

If you have an encrypted password stored in the "PASS" variable within a Docker environment, you can't establishing a connection to the Transmission rpc.
To avoid a 403 Forbidden error, it's crucial to include the IP address "<IP_ADDRESS>" in the rpc-whitelist variable within the settings.json file.

There is nothing special happening in the mod regarding auth handling. By the encryption you mean docker secrets or something else? If something else, is it supported by the container without the mod?
Since this is a mod to main image, the address should be added via WHITELIST. It's also only needed if the variable is used in the first place. I guess here we just need more documentation in the repo.


set custom error handler for application run

To search for #1190 bug

:+1:   (but you already knew https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/1102#issuecomment-94282558 ;)  )


Added link to weavenet/aws-ec2-vpn

Added a link to a Cloud Formation template which stands up a VPN that can be used by MacOS users who wish to run their own VPN on AWS.

Have you seen https://github.com/jlund/streisand ? I've been using this setup, works extremely well :-)

Yes, but you would have to spin up a new instance every day to not be impacted by correlation attacks coming from the same source IP right?

@9Yg1rxeSeha90ZU1 correct.  For my use case that was acceptable, but in hindsight this may not bee appropriate to include.  Closing for now.


tidb: update golangci-lint version on master / release-5.x

golangci-lint version need upgrade from v1.21.0 to v1.29.0 on master&release-5.x

hold

hold on until tidb lint releated pr merged  25389

The golangci-lint has been upgraded to v1.41.1 on master by this PR: https://github.com/pingcap/tidb/pull/25912
And those lint has been fixed.

fix lint errors on release-5.1  #https://github.com/pingcap/tidb/pull/26295


Feature : List installed packages of a given env

Goal :

Port the following feature of Gator using Conda Store : List installed packages of a given env

Acceptance :

The feature works with mamba/conda and Conda Store

Other notes :
Show the packages with their version and channel

Blocked by https://github.com/Quansight/conda-store/issues/150, which should modify the existing endpoint for retrieving packages. I think in priniciple I will send a request to /api/v1/builds/<build_id>/ for a paginated list of packages, rather than the existing endpoint /api/v1/namespace/<namespace>/environments/<environment/.

Now that #150 is close, I remove the blocked label.

We need to fix the checkbox to invert its state.

Merged: https://github.com/mamba-org/gator/pull/155


Remove hardcoded permits for stream assembly

Right now we have hardcoded default permits for all stream
assemblies.This creates a situation for where it's easy to forget
default permits exist when defining any other permit in releases.yml example
when rhcos is broken - or at the time of branch cut. Including them explicitly
in releases.yml will ensure that we are aware of them and they are defined
in one place.
Context: https://coreos.slack.com/archives/C048BG69N8H/p1668031797575059
We will need follow up ocp-build-data PRs for all versions that we build
to include these explicitly (right now they are explicitly defined in 4.13-4.8)
4.7 - <>
4.6 - <>

/lgtm


Web socket events do not work.

Hello,
I have been trying to work with explorer events referring to the documentation https://cardanodocs.com/technical/explorer/
but not able to get it to work.
My main goal is to listen to new block events, so I can process those blocks.
var client = require('socket.io-client');
var socket = client('http://localhost:8100'); //also tried on port 8110
socket.on('SubBlockLastPage', function(msg){ console.log(msg); });

Now I'm expecting the callback to be triggered every time the last page changes (new slot added). But nothing happens.
I have the explorer running along with the node.
Is there something I'm missing?

There's a unicode problems in explorer, thanks to @ilap
https://forum.cardano.org/t/how-to-query-based-on-block-height-and-listen-to-new-block-transaction-events-also-sockets-api/12472/10?u=vantuz-subhuman

hi cardano team
I hope you fix this issue, and support socket in node js

Checked with cardanoexplorer.com using polling transport with a local HTTP server listening on localhost:3100. Cool thx.

Welcome!  Happy to help!

Please fix this issue for socket.io on nodejs. Thank

Please fix this issue for socket.io on nodejs. Thank

What's the problem? It's working in some conditions. See @johnalotoski's comments above

Yes, It work with chrome, but Nodejs won't work.
Nodejs Client
datnv@lt29-datnv:~/projects/ibl-master-socket$ npm start
><EMAIL_ADDRESS>start /home/datnv/projects/ibl-master-socket
> NODE_ENV=dev node index.js

2018-09-26 09:14:54.391 ERROR 14543 SOCKET ADA Socket connect error: http://<IP_ADDRESS>:8110 - websocket error
2018-09-26 09:14:55.924 ERROR 14543 SOCKET ADA Socket connect error: http://<IP_ADDRESS>:8110 - websocket error
2018-09-26 09:14:57.137 ERROR 14543 SOCKET ADA Socket connect error: http://<IP_ADDRESS>:8110 - websocket error

Cardano
3|connect-mainnet-explorer  | [cardano-sl.node.notifier.socket-io:Debug:ThreadId 190423] [2018-09-26 02:14:54.38 UTC] New session has started (#"BzMAJw45BTM8MDojFgQK")
3|connect-mainnet-explorer  | [cardano-sl.node.notifier.socket-io:Debug:ThreadId 190429] [2018-09-26 02:14:55.92 UTC] New session has started (#"DRINDSQmBDQVLAUuLzUE")

I too am experiencing the same issue on NodeJS (printing the received data) with the socket.io client branch release/1.3.0,
  �0{"pingInterval":25000,"pingTimeout":60000,"upgrades":["websocket"],"sid":"Jw4iCjIyOSs/OxQSLQsr"}
{ Error: server error
  at Socket.onPacket (/XXXXXXXXXXXXXXXXX/test/node_modules/engine.io-client/lib/socket.js:450:19)
  at XHR.<anonymous> (/XXXXXXXXXXXXXXXXX/test/node_modules/engine.io-client/lib/socket.js:273:10)
  at XHR.Emitter.emit (/XXXXXXXXXXXXXXXXX/test/node_modules/component-emitter/index.js:133:20)
  at XHR.Transport.onPacket (/XXXXXXXXXXXXXXXXX/test/node_modules/engine.io-client/lib/transport.js:145:8)
  at callback (/XXXXXXXXXXXXXXXXX/test/node_modules/engine.io-client/lib/transports/polling.js:144:10)
  at Object.exports.decodePayload (/XXXXXXXXXXXXXXXXX/test/node_modules/engine.io-parser/lib/index.js:295:14)
  at XHR.Polling.onData (/XXXXXXXXXXXXXXXXX/test/node_modules/engine.io-client/lib/transports/polling.js:148:10)
  at Request.<anonymous> (/XXXXXXXXXXXXXXXXX/test/node_modules/engine.io-client/lib/transports/polling-xhr.js:126:10)
  at Request.Emitter.emit (/XXXXXXXXXXXXXXXXX/test/node_modules/component-emitter/index.js:133:20)
  at Request.onData (/XXXXXXXXXXXXXXXXX/test/node_modules/engine.io-client/lib/transports/polling-xhr.js:299:8) code: 'parser error' }

It works with python-sockio
Here is the demo I tried.
import socketio

sio = socketio.Client()

@sio.on('connect')
def on_connect():
    print('connection established')
    sio.emit('CallMe')
    sio.emit('Subscribe SubBlockLastPage')

@sio.on('CallYou')
def on_message(*args):
    print args
    print('Call')

@sio.on('BlocksLastPageUpdated')
def on_block(*args):
    print args
    print('block')

@sio.on('disconnect')
def on_disconnect():
    print('disconnected from server')

url = "http://localhost:8110"
sio.connect(url)
sio.wait()


Allow clmbr_compute_representations to run on CPU

Is your feature request related to a problem? Please describe.
clmbr_compute_representations currently only runs on GPU.
Describe the solution you'd like
For GPU-constrained environments it would be great to compute patient representations using pretrained CLMBR on CPUs.

This is now fixed in the latest release!


Refactor: Rename subCollective(s) to relatedCollective(s)

This renames all subCollective(s) instances to relatedCollective(s).
Related https://github.com/opencollective/opencollective/issues/3040

Great, thanks! Let's wait for Pia's feedback on https://github.com/opencollective/opencollective/issues/3040 before moving on with this

Great, thanks! Let's wait for Pia's feedback on opencollective/opencollective#3040 before moving on with this

You are welcome. :smile:

As per https://github.com/opencollective/opencollective/issues/3040#issuecomment-620533323, let's rather say "Connected collectives".

As per opencollective/opencollective#3040 (comment), let's rather say "Connected collectives".

Done. :smile:


Call diskparts to discover partitions on startup (terminal and CPU)

Also update diskparts according to a change suggested by Erik Quanstrom in 9fans to correctly discover partitions on disks with no plan9 partition.
Add both CPU and terminal options to syslinux menu

Signed-off-by: Graham MacDonald<EMAIL_ADDRESS>

I still think Harvey doesn't need swap.

Commit 01022f1eaf4030409782caf3c84c3adb78b63b71 is not signed-off.
Please fix these issues:

ron minnich has not signed-off 01022f1.

If you'd like more information on how to sign your commits please visit signed-off-by.me

sorry, I clicked update :-(

Rebased - please re-approve and we can merge it in


Variation Documentation Updates for 104

Just 104, or also master ?

Yes, it's also required on master I'm afraid. Should I change this PR onto postreleasefix/104, or shall I create a second PR just for master?

Can you submit it against postreleasefix/104 (keeps the git tree cleaner) ?

Done, #453


Update the install script to dynamically determine the path to Elsewhere

We're now building a debian package which ensures everything is in known locations. Closing as invalid.


Increased frequency of webhook handling errrors for pull_request.opened events after dependency upgrades

Bug Report
Current Behavior
Ever since upgrading probot from v9.11.2 to 9.11.7 and a bunch of @octokit packages (notably, a major upgrade of @octokit/endpoint from 5.5.1 to 6.0.3), I've noticed a significant increase on webhook handling errors that seem to be originating from pull_request.opened events.
 18:18:25.344Z ERROR event: Not Found (id=bafb5800-cc47-11ea-8c8e-959b67c42d2e)
  HttpError: Not Found
      at /app/node_modules/@octokit/request/dist-node/index.js:66:23
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      at async Job.doExecute (/app/node_modules/bottleneck/light.js:405:18)
   --
   event: {
     "event": "pull_request.opened",
     "id": "bafb5800-cc47-11ea-8c8e-959b67c42d2e",
     "installation": [installation ID]
     "repository": [org/repo-name]
   }
 18:18:25.345Z ERROR probot: Not Found
   HttpError: Not Found
       at /app/node_modules/@octokit/request/dist-node/index.js:66:23
       at runMicrotasks (<anonymous>)
       at processTicksAndRejections (internal/process/task_queues.js:97:5)
       at async Job.doExecute (/app/node_modules/bottleneck/light.js:405:18)
18:18:25.346Z  INFO http: POST / 500 - 108.98 ms (id=03a667d0-0e1f-9513-afa8-d10c76b949fd)

However, these failures seem to be intermittent and I can't seem to reliably reproduce them. When I resend these webhooks, they typically do go through successfully.
Environment

Probot version(s): [v9.11.7]
Node/npm version: [Node v12.13.0/npm 6.12.0]
OS: [OSX 10.14.6]

Additional context/Screenshots
If it helps for investigation, here are some IDs of webhooks that failed to deliver:
bafb5800-cc47-11ea-8c8e-959b67c42d2e
09dbd880-ccae-11ea-84ed-9044171588e2
a2715900-ccac-11ea-9c8b-e5f2be242192

When you downgrade to v9.11.2, do you still see the errors?
Not Found errors can occur if you try to read (GET / HEAD) a resource shortly after it was created. Can you share what you do in your pull_request.opened handler?

hey @gr2m, thanks for looking into this!
Unfortunately, I can't downgrade it without causing disruptions since the app is actually running in production. I've only noticed these errors surfacing intermittently after the upgrades, whereas they were never an issue before.
Ah, that could explain a lot. This is a snippet of the first thing that happens in my pull_request.opened handler:
const { data: commits } = await octokit.pulls.listCommits({
  owner,
  repo,
  pull_number
});

where octokit is context.github, and owner, repo, and pull_number are destructured from context.payload.

Can you try to replace above code with
const { data: commits } = await octokit.pulls.listCommits({
  owner,
  repo,
  pull_number,
  request: { retries: 1 }
});

This will retry the request if it fails, for any status code. This comes from the retry Octokit plugin, which Probot uses

Ah cool didn't know you could do that!
Is the octokit instance that Probot uses not configured to retry automatically by default then?

Is the octokit instance that Probot uses not configured to retry automatically by default then? By adding the request: { retries: 1 } bit, am I opting in to the retry plugin? Or am I overriding its default number of retries?

yes, the octokit instance will retry automatically, but not in case of a 404 response. Setting request: { retries: 1 } on a request will make sure the request gets retried in any case

awesome. i'll try that! thank you so much 😁


certificate is expired at https://ny1.ptopenlab.com/AIVision/

because the cert is expired, you have to use browser advanced settings to allow it. A cert update was requested and hopefully will happen soon.
This issue is logged to help troubleshooting. Not to recommend bad security practices.
In case of cert issues, some steps in this pattern don't work unless you bypass that security.
One sneaky instance of this problem is when running the example app on a phone and it won't display the image (until you browse to the site and bypass security).

Fixed on SuperVessel. I entered a new issue #28 to take the "insecure" stuff out of our examples.


Implement TypedBuilder for VariantOper

In the context of #1655

cc @Kukovec

@Kukovec, if you have not started this work, please wait till #1928 and #1927 are closed.


Add installer

Perhaps a cpack or WiX based solution, or both.

I'm no fan of Go, but you can use this to release on commit: https://github.com/goreleaser/goreleaser
Rust tutorial: https://medium.com/@jondot/shipping-rust-binaries-with-goreleaser-d5aa42a46be0


add optional per-request/response timeout value

As recommended in  https://datatracker.ietf.org/doc/html/draft-ietf-lamps-lightweight-cmp-profile#name-cmp-message-transfer-mechan:

Independently of the means of transfer, it can happen that messages are lost or that a communication partner does not respond. To prevent waiting indefinitely, each PKI entity that sends CMP requests SHOULD use a configurable per-request timeout, and each PKI management entity that handles CMP requests SHOULD use a configurable per-response timeout in case a further request message is to be expected from the client side within the same transaction. In this way a hanging transaction can be closed cleanly with an error as described in Section 3.6 (failInfo bit: systemUnavail) and related resources (for instance, any cached extraCerts) can be freed.

So please add a configurable maximal time (in seconds) to wait for responses on the upstream interface (e.g. HTTP)
and to wait for subsequent requests (where applicable) on the downstream interface, with reasonable default values.
A value of 0 shall mean to wait indefinitely.
It could be considered an error if a non-zero downstream timeout value given is smaller than any configured retryAfter value.

HTTP(S) timeout implemented in 93a53715efb649f5b8761adf7c1782fc0725d180

transaction expiration implemented in 2ccf9e4


[clean] Space Auto Remover - CH10

Run regex algo to suto remove spaces (as publisher required), replace half-width with full-width (i.e. "(" to "（") in suitable situations.

[ ] Need to check html rendering: numref, cite, etc. rendering

Job d2l-zh/PR-968/1 is complete.
Check the results at http://preview.d2l.ai/d2l-zh/PR-968/


add titan network

This looks to be a good submission. The only issue I notice is that the 'chain' 'ttnt' images seem to be duplicates, which I believe can be reduced to a single set of images.

This looks to be a good submission. The only issue I notice is that the 'chain' 'ttnt' images seem to be duplicates, which I believe can be reduced to a single set of images.

Thanks, I changed this


x/image/tiff: decoding of metadata is not available

Current implementation of TIFF decoder is unable to decode following metadata from TIFF image:

TIFF tags
EXIF tags
GPS tags

What version of Go are you using (go version)?

$ go version
go version go1.20.2 windows/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
Microsoft Windows 10
Intel x86-64 (a.k.a. AMD64)
What did you expect to see?
Usable metadata for TIFF images.

It looks like it needs a new API to decode the metadata? Would you like to file a proposal (see https://golang.org/s/proposal-process)? Thanks.

If someone needs TIFF metadata decoded, this functionality is available in the "TIFFer" library – https://github.com/vault-thirteen/TIFFer


GitHub Cheat Sheet link update

https://services.github.com/on-demand/downloads/github-git-cheat-sheet.pdf  => https://github.github.com/training-kit/downloads/github-git-cheat-sheet.pdf

hey @990094523 , thanks for reporting the issue! would you like to contribute with a PR since you already found the correct link? You only need to update the file at https://github.com/git/git-scm.com/blob/master/app/views/doc/index.html.erb#L24 with the correct link :)

👌

closed by #1325


Unable to Install git on Linux

Please follow the general troubleshooting steps first:

[x] Ran brew update and retried your prior step?
[x] Ran brew doctor, fixed as many issues as possible and retried your prior step?
[x] Confirmed this is problem with Homebrew/brew and not specific formulae? If it's a formulae-specific problem please file this issue at https://github.com/Homebrew/homebrew-core/issues/new

Bug reports:
Error shown when attempting to install git
brew install git
==> Installing dependencies for git: openssl, pkg-config, curl, expat
==> Installing git dependency: openssl
==> Downloading https://www.openssl.org/source/openssl-1.0.2j.tar.gz
######################################################################## 100.0%
==> perl ./Configure --prefix=/scratch/linuxbrew/Cellar/openssl/1.0.2j --openssldir=/scratch/linuxbrew/etc/openssl no-ssl2 zlib-dynamic shar
==> make depend
Last 15 lines from /home/user/.cache/Homebrew/Logs/openssl/02.make:
	not in /usr/include/stddef.h
makedepend: warning:  o_fips.c (reading /usr/include/openssl/fips.h, line 52): cannot find include file "stdarg.h"
	not in ./stdarg.h
	not in ../stdarg.h
	not in ../include/stdarg.h
	not in /usr/include/stdarg.h
makedepend: warning:  o_fips.c (reading /usr/include/openssl/aes.h, line 61): cannot find include file "stddef.h"
	not in ./stddef.h
	not in ../stddef.h
	not in ../include/stddef.h
	not in /usr/include/stddef.h
/usr/local/bin/perl5: error while loading shared libraries: libdb.so.3: cannot open shared object file: No such file or directory
make[1]: *** [local_depend] Error 127
make[1]: Leaving directory `/tmp/openssl-20170104-17308-i3xymb/openssl-1.0.2j/crypto'

▽
make: *** [depend] Error 1

READ THIS: https://github.com/Linuxbrew/brew/blob/master/docs/Troubleshooting.md#troubleshooting

These open issues may also help:
<EMAIL_ADDRESS>Migration [Tracking] https://github.com/Homebrew/homebrew-core/issues/4543
The description for openssl installation is misleading https://github.com/Homebrew/homebrew-core/issues/5291

brew config output
HOMEBREW_VERSION: 1.1.5-3-gb421e7e
ORIGIN: https://github.com/Linuxbrew/brew.git
HEAD: b421e7e2146de291a1a2cd0ca7ca2e0972b74465
Last commit: 2 days ago
Core tap ORIGIN: https://github.com/Linuxbrew/homebrew-core
Core tap HEAD: 0ddf7cddd25191e9d943a77762b23cf796870513
Core tap last commit: 2 days ago
HOMEBREW_PREFIX: /scratch/linuxbrew
HOMEBREW_REPOSITORY: /scratch/linuxbrew
HOMEBREW_CELLAR: /scratch/linuxbrew/Cellar
HOMEBREW_BOTTLE_DOMAIN: https://linuxbrew.bintray.com
CPU: hexa-core 64-bit haswell
Homebrew Ruby: 2.0.0-p648 => /usr/bin/ruby
Clang: N/A
Git: 2.10.2 => /bin/git
Perl: /bin/perl => /usr/bin/perl
Python: /bin/python => /usr/bin/python2.7
Ruby: /bin/ruby => /usr/bin/ruby
Java: openjdk version "1.8.0_111"
Kernel: Linux 4.1.12-32.2.3.el7uek.x86_64 x86_64 GNU/Linux
OS: Oracle Linux Server release 7.3
Codename: n/a
OS glibc: 2.17
OS gcc: 4.8.5
Linuxbrew glibc: 2.19
Linuxbrew gcc: 5.3.0
Linuxbrew xorg: N/A

brew doctor output
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!

Warning: "config" scripts exist outside your system or Homebrew directories.
`./configure` scripts often look for *-config scripts to determine if
software packages are installed, and what additional flags to use when
compiling and linking.

Having additional scripts in your path can confuse software installed via
Homebrew if the config script overrides a system or Homebrew provided
script of the same name. We found the following "config" scripts:
  /bin/krb5-config
  /bin/kde4-config
  /bin/ncurses5-config
  /bin/ncursesw5-config
  /bin/icu-config
  /bin/curl-config
  /bin/pkg-config
  /bin/pcre-config

Please encode copy-paste-pastes in triple-backticks.
```
paste here
```

/usr/local/bin/perl5: error while loading shared libraries: libdb.so.3: cannot open shared object file: No such file or directory

Try removing /usr/local/bin from your PATH environment variables.
Try
PATH=$(brew --prefix)/bin:/usr/bin:/bin brew install git


Signpost security policy from core repo READMEs

What
There is an organisation-wide security policy associated with the repo.
It is linked to from the 'New Issue' page:

But otherwise is not very visible.
Add a link to the security policy from the README.
Why
In the Cabinet Office, including GDS, the CDIO Cyber Security team run a vulnerability disclosure programme with HackerOne and NCC Group to triage reports from security researchers.
The security policy is a way of telling researchers how to get in contact with us via that programme.
Who needs to know about this
Dependencies
At the minute the linked security policy is out of date as it does not reference the new vulnerability disclosure  programme, so we probably want to wait until that's been resolved.
Done when

[ ] The README in the govuk-frontend repo points to the security policy
[ ] The README in the govuk-design-system repo points to the security policy
[ ] The README in the govuk-prototype-kit repo points to the security policy

I've raised PRs to add the link to the READMEs for the Design System, Frontend and Prototype Kit repos.


Remove Dark Theme & change into system theme and update previous code

Hi

please rebase the code so there are no merge commits
why is .gradle committed again? This is persisitn issue in ever PR you have made so far

Please resolve the conflicts and accept the latest PR. Test it according to the latest code. The design must be same as that was sent to you by using brand color


xfce4-12: remove alias

Motivation for this change
xfce4-12 should not point to xfce version 4.14. People will be better off seeing an error than unknowingly being force-switched to 4.12.
I think we should backport this change to 20.03 ASAP so it has time to sink before the release.
cc @worldofpeace @disassembler
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

Merged and backported as a4bf572a9fa


Photo formatting and PDF printing

Hi!
Thanks for developing this innovative and incredibly useful resource for us all ... for free!! I really want to thank you for your work and creativity!
Issue #1: I've noticed the photo formatting is a little off. It seems like it's stretched sideways.
Issue #2: When printing the document to a PDF, the formatting is not as crisp as the web page, and it bleeds into a second page unexpectedly. So, maybe it would be nice to limit the template to fit a page size (US Letter, A4, etc).
Thanks again for your great work!

Hey there :)
Regarding the first issue, it is actually only visible in the preview mode of the app because we're using a CSS property called zoom that still has a few kinks in it with regards to browsers. But this issue will not be visible in the final print version or the PDF of the resume.
About the second issue, I haven't had any issues regarding the quality of the PDF. It prints everything into a vectorized format so it should be visible. Maybe it's an issue with the browser? I have tried it on Chrome and Safari and it works well.
I'm currently looking into some solutions where the PDF is built internally and not through the browser. Will do my best to keep you updated on that. Thank you so much for the feedback :)

Merged into #41