[Event Request]Table 352 "Default Dimension" - OnUpdateBankGlobalDimCodeOnCaseElse

Request a new event in procedure UpdateBankGlobalDimCode in table 352 "Default Dimension":
local procedure UpdateBankGlobalDimCode(GlobalDimCodeNo: Integer; BankAccNo: Code[20]; NewDimValue: Code[20])
var
    BankAcc: Record "Bank Account";
begin
    if BankAcc.Get(BankAccNo) then begin
        case GlobalDimCodeNo of
            1:
                BankAcc."Global Dimension 1 Code" := NewDimValue;
            2:
                BankAcc."Global Dimension 2 Code" := NewDimValue;
            //<NEW>
            else
                OnUpdateBankGlobalDimCodeOnCaseElse(GlobalDimCodeNo, BankAccNo, NewDimValue);
            //</NEW>
        end;
        BankAcc.Modify(true);
    end;
end;

//<NEW>
[IntegrationEvent(false, false)]
local procedure OnUpdateBankGlobalDimCodeOnCaseElse(GlobalDimCodeNo: Integer; BankAccNo: Code[20]; NewDimValue: Code[20])
begin
end;

Realized later that this procedure is only called for Global Dimensions 1 and 2.  By using the DimMgt.DefaultDimOn... calls, this request is unnecessary.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


feat: expand hub support to helm plugins

The same motivation behind the creation of Helm Hub of enabling distributed search in an intentional way applies Helm plugins, which is a mechanism for adding functionality to Helm independently of Helm release cycles.  While there is minimal documentation on the Helm website how to begin searching for plugins, this has the same pains and benefits that led to making charts discoverable.

Closing this since we have an artifact hub issue where we can follow up on this.

Artifact Hub now supports Helm plugins :)
https://artifacthub.io/docs/topics/repositories/#helm-plugins-repositories

Artifact Hub now supports Helm plugins :)
https://artifacthub.io/docs/topics/repositories/#helm-plugins-repositories


pittpatt "inconsistent image dimensions" errors on some devices

On certain devices, face tracking fails with errors
E/pittpatt: online_face_detector.cc:236] inconsistent image dimensions E/pittpatt: detector.cc:220] inconsistent image dimensions
Has been observed on

Samsung Galaxy Note 4
Samsung Galaxy J2
with apparently fairly normal front camera preview sizes of e.g.
960x540, 720x480, 640x480

One workaround is to force to 800x480, which enables face tracking to work
with front camera on both these devices (even though 800x480 not even listed
in available preview sizes on J2)

The face tracker assumes that each image frame received is consistently the same dimensions.  As far as I can tell, it looks like it is receiving a new image frame that is has different dimensions that the previous image frame.
Can you give more details on how you initialized the face detector and how you are passing in images?

Thank you for responding so quickly.
Our detector is very simple, just via
new FaceDetector.Builder().build()
with 4 of the usual flags (setLandmarkType(FaceDetector.NO_LANDMARKS) etc)
Frame created via new Frame.Builder().build(), using setImageData() with a byteBuffer and our preview width and height (which will be constant until camera switched front/rear)

When the camera is switched or rotated, the face detector should be rebuilt so that it can reinitialize for images of a different dimension.

Yes -- the second I saw your original response I started looking at this, think the bug is in our code...mea culpa


Small refactoring

Not much done this time, mostly small refactors and bugfixes. One noticeable thing is the start of error system rewrite. You can see it in action by triggering same seed warning and inpaint-no-source-mask error at the same time


Service Health dashboard Add a RUM chart in the custom chart

Describe the solution you'd like
-Add a RUM chart in the custom chart part Service Health dashboard
Additional context
Will show the value of having both RUM and synthetics and what the difference is

Good idea, given the time restraints for the workshop, we will add text around making this a homework/in their own time exercise post workshop.


NO-ISSUE: Fix python version to 3.11

fix python version to "3.11" as the application requires

/cc @adriengentil @osherdp


NO-JIRA Add proxy forwarding doc

@brusdev I'm confused.. the PR title says NO_JIRA Adding doc, and the commit is fixing something... was that a mistake?

@clebertsuconic the commit summary was wrong, I have just fixed it.

@clebertsuconic the commit summary was wrong, I have just fixed it.


fix(connlib): clear timeout after it fired

We don't want the timer to fire multiple times at the same Instant unless it has been specifically set to that Instant again. Thus, clear the timer after it fired.
I don't think this fixed #6067 but it can't hurt.

@jamilbk Do we have a gateway on staging that tracks main?

I'll set up a vultr instance that tracks this version once merged.


Garbage Values

was working for me until two days ago now it does not accept more than one string without becoming garbage values.

Sorry for late reply! Fixed! v1.0.3 👍


Framer Animations

I will add Framer animations to your website ,
it will enhance the user experience ,
Animations @ Hero section , about us , courses page and project page

Thank you for raising the issue.
But for now it is not required.
So I am closing this issue.
Please understand.
And one more thing this project is already inactive including me also due to some of my works.
Please do contribute to other projects.
I hope you understand.

Thank you for raising the issue.
But for now it is not required.
So I am closing this issue.
Please understand.
And one more thing this project is already inactive including me also due to some of my works.
Please do contribute to other projects.
I hope you understand.

Ok
No worries


build: use dotnet7

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


Some Emacs packages got broken with 17.03

Issue description
Hi.
Some Emacs packages which were ok at 16.09 got broken with 17.03
Steps to reproduce

Adding zerodark-theme leads to output path ‘/nix/store/s2id04jc7lrhnilsc9vgi8i1p1003jxy-font-lock+.el’ has sha256 hash ‘0iajkgh0n3pbrwwxx9rmrrwz8dw2m7jsp4mggnhq7zsb20ighs30’ when ‘0ffs2c7gyhfa2mskdh7a1yp0na99kk282zm4zn56ljp55rrnnnh0’ was expected error
If I activate ergoemacs-mode, Emacs shows the error Opening output file: No such file or directory, /home/gnidorah/.emacs.d/ergoemacs-extras/ergoemacs-global-25-1-1-x86-64-unknown-linux-gnu.el.gz. It doesn't matter whether it was installed from melpaStablePackages or melpaPackages. One from elpaPackages loads but produces a warning Invalid slot name: #<ergoemacs-theme-component-map-list ergoemacs-theme-component-map-list>, standard

Technical details

System: (NixOS: nixos-version, Ubuntu/Fedora: lsb_release -a, ...)
Nix version: (run nix-env --version)
Nixpkgs version: (run nix-instantiate --eval '<nixpkgs>' -A lib.nixpkgsVersion)

With regard to the sha issue with font-lock+.el---I think this is just an inherent conflict between melpa being willing to get code off of emacswiki.org, and nix's desire for stable identifiers---if you look at the sha on master, it matches what is expected, but it only dates back to 2017-03-02.
@ttuegel should we update the sha in the font-lock+.el expression for the release?

With regard to ergoemacs-mode---whatever it's baroque initialization code is doing, it is apparently not smart enough to simply mkdir ~/.emacs.d/ergoemacs-extras/, instead electing to get itself into some infinite-seeming loop.  I would suggest reporting a bug upstream.
Doing that mkdir manually allowed it to start, at which point I discovered it was apparently written by someone who doesn't actually like emacs---I barely escaped. :)  Good luck!

I have the same problem with a fresh NixOS 17.03. Script to reproduce this problem:
#!/usr/bin/env bash

test_dir=$(mktemp -d)

pushd $test_dir

cat <<EOF > default.nix
{ pkgs ? import <nixpkgs> {} }:

let
  emacsWithPackages = (pkgs.emacsPackagesNgGen pkgs.emacs).emacsWithPackages;
in
  emacsWithPackages (epkgs: (with epkgs.melpaStablePackages; [
    zerodark-theme
  ]))
EOF

nix-build default.nix

popd

rm -rf $test_dir

Will produce the following output:
these derivations will be built:
  /nix/store/5dazdrnv260bg23sdfmjjv0ymzwxff3j-font-lock-plus.drv
  /nix/store/zbxigj6v897gf2vmjlx5lc3qdr50qp79-font-lock+.el.drv
  /nix/store/y77x6znrqmbla3mpbi1h8x5cvafsvl55-emacs-font-lock-plus-20170101.947.drv
  /nix/store/18f3aimx2pxx6d819r19mfxh74rcv21y-emacs-all-the-icons-2.2.0.drv
  /nix/store/hbl6hqrkvph25qcnimwhv13jnbm1bz10-pkg-info.drv
  /nix/store/zcr3vd4nwdm8vv1mlbs528hpwzznwjgg-pkg-info.el-f9bb471ee95d1c5fe9adc6b0e98db2ddff3ddc0e-src.drv
  /nix/store/v0ab1dr7glx1lg9sva5ncik7vq6232lb-emacs-pkg-info-0.6.drv
  /nix/store/pbj4qrcpk318zzl18f5x15sgqnf2a1dy-let-alist-1.0.5.el.drv
  /nix/store/wiwjwkrplqi1mbbzxqj8zn8bj8sv6h7p-emacs-let-alist-1.0.5.drv
  /nix/store/pl97nfwc1k04vxdzkcgppwxlh87r5h12-emacs-flycheck-30.drv
  /nix/store/b2l6glxi8nl03213yq1b670gdaqqw3ij-emacs-zerodark-theme-4.2.drv
  /nix/store/49rjkx6f4bjjm9l9y9wflkg4qf8z53cd-emacs-packages-deps.drv
  /nix/store/aqrgfjymwa8vysg1886b89rjvkf5cvc6-emacs-with-packages-25.1.drv
building path(s) ‘/nix/store/s2id04jc7lrhnilsc9vgi8i1p1003jxy-font-lock+.el’

trying https://www.emacswiki.org/emacs/download/font-lock+.el
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 19202    0 19202    0     0   100k      0 --:--:-- --:--:-- --:--:--  100k
output path ‘/nix/store/s2id04jc7lrhnilsc9vgi8i1p1003jxy-font-lock+.el’ has sha256 hash ‘0iajkgh0n3pbrwwxx9rmrrwz8dw2m7jsp4mggnhq7zsb20ighs30’ when ‘0ffs2c7gyhfa2mskdh7a1yp0na99kk282zm4zn56ljp55rrnnnh0’ was expected
cannot build derivation ‘/nix/store/y77x6znrqmbla3mpbi1h8x5cvafsvl55-emacs-font-lock-plus-20170101.947.drv’: 1 dependencies couldn't be built
building path(s) ‘/nix/store/3cygxp1xk8364yhvkw739y4y602ibvgy-let-alist-1.0.5.el’
cannot build derivation ‘/nix/store/18f3aimx2pxx6d819r19mfxh74rcv21y-emacs-all-the-icons-2.2.0.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/b2l6glxi8nl03213yq1b670gdaqqw3ij-emacs-zerodark-theme-4.2.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/aqrgfjymwa8vysg1886b89rjvkf5cvc6-emacs-with-packages-25.1.drv’: 1 dependencies couldn't be built
error: build of ‘/nix/store/aqrgfjymwa8vysg1886b89rjvkf5cvc6-emacs-with-packages-25.1.drv’ failed

@mdorman Thank you much for fixing!


CBMC: State + prove spec for polyvec_compress() and polyvec_decompress()

This is using a different compression than poly_compress and poly_decompress

Fixed in #367


Menu does not "respect" nested pages.

When enabling "fabricator: true" for pages. The menu (f-menu.html ) does not respect the page path, because it is rendered without any {{baseurl}}. Same for menu example on pages.html
So the f-menu.html should be something like this:
f-menu.txt

Thanks I'll take a look at this!


Update long-run builds to use Frierson diffusion option.

Follow up PR to #2349.
Uses the new stability dependent diffusion option introduced in PR2349 to the long-run pipeline. (Affects aquaplanet long-run cases)
(These cases are being run on the A100 cluster; will post when available.)

I only see changes in slab ocean now. Maybe something is wrong with the rebase?

Do you want to change the topography one as well?

We could do so, but I think I'd like to wait for the checks against the WIP implicit update branches and assign parameters accordingly.

Results from topography longruns (with WIP implicit solver update branch: https://buildkite.com/clima/climaatmos-longruns/builds/1354#018cf69d-e535-4a74-a729-e8e77a617526)

Could we merge this?

@Sbozzolo Added the diag print block you suggested in this PR type_getters.jl. If this is reasonable I can queue this to be merged soon.

@Sbozzolo Added the diag print block you suggested in this PR type_getters.jl. If this is reasonable I can queue this to be merged soon.

I made some minor improvements in 8282e9882
At the end, it looks like this:
    length(diagnostics) > 0 && @info "Computing diagnostics:"

    for diag in diagnostics
        writer = nameof(typeof(diag.output_writer))
        @info "- $(diag.output_short_name) ($writer)"
    end

It would be great if you could add this instead.

@Sbozzolo Added the diag print block you suggested in this PR type_getters.jl. If this is reasonable I can queue this to be merged soon.

I made some minor improvements in 8282e98
At the end, it looks like this:
    length(diagnostics) > 0 && @info "Computing diagnostics:"

    for diag in diagnostics
        writer = nameof(typeof(diag.output_writer))
        @info "- $(diag.output_short_name) ($writer)"
    end

It would be great if you could add this instead. If you can keep it as a separate commit in this PR, that would be awesome.
(This change will be merged in with #2489 anyway)

Ah awesome - if this is a feature in #2489 I'll remove it from here. Noted the suggestions for local test branches in any case.


Feedly: Leo Web Alerts are missing

Leo Web Alerts are displayed in the feed list, but no articles get synced.
Is this a Feedly API limitation or could you support this in the future?

It seems support for this cannot be done in NetNewsWire for now.
NetNewsWire is designed such that you must be subscribed to the feed/source to read an article. Leo seems to be finding articles from sources you're not subscribed to so you're not seeing them in NetNewsWire.
This issue with the design of NetNewsWire is tracked at #1299


Request to add sample results

Description
Hello! This project looks awesome but to decide whether I would like to invest the time into setting it up, it'd be great to be able to see some sample upscaled videos. I was wondering if the project would be open to including some on the README (ie. maybe one real world video and another anime video). I know there are different models but it'd still be helpful to have an example of generally how good/bad we should expect the results to be.
(In my case, I'm concerned with if the upscaled results will be spatially inconsistent for real world footage resulting in a really bad distracting `result)
Current Researched Artifacts [COMPULSORY]
I looked in the tests/ folder for the example footage and found only the inputs are there not the upscaled results.

Hi, @MatthewScholefield, sorry for the late reply was caught up for something at the moment.
The  tests/ folder is meant to generate an output video on a specific device (basically to test a given host machine can generate an output.
You can let it run overnight by executing ./tests/02_test_upscale_video_single.sh.ps1. It shall generate an output video (based on that machine) right next to the sample 1 video inside ./tests/video/ directory.

Hmm, thanks for the reply. I don't fully follow. I know the exact generated output might be slightly different due to some non-determinism with parallel floating point operations, but won't the results still generally all look the same for the same input and model?
The idea is just to give a prime example for potential users to get a sense of what sort of results to expect so I don't think it'd matter if it looks a little different.

I know the exact generated output might be slightly different due to some non-determinism with parallel floating point operations, but won't the results still generally all look the same for the same input and model?

Not this problem. It's a different one like on some hardware some folks produced some big mosaic distorted output that I can't reproduce the bug here at all for debugging purposes. Then there is the hardware configurations uncharted territory (e.g. I never got a chance to test on AMD hardware; so far Apple & 3 Nvidia).
When resources are scare, distribute a decentralized consistent test infrastructure is 2 birds 1 stone (for now).

The idea is just to give a prime example for potential users to get a sense of what sort of results to expect so I don't think it'd matter if it looks a little different.

Point taken on the marketing material. =)
For the interim, internally, it's basically using ffmpeg dissecting the video frame by frame by probing its highest quality state (frame-rate matching and etc) then replace it back making its visual larger. No variable bit rate support though; that's beast is too complicated.
My recommendation is to use the image mode and some test image to find your desired model, then only do the video (save time). What's confirmed is the size is definitely upscaled and some model has some visual effects (noise reductions and etc).
Site-note: be careful with your scaling factor (e.g. 720p upscale 4x), it nearly fry my laptop once when generating an output video beyond 4k.

FYI, what I did was using this video from Pexels: https://www.pexels.com/video/the-sun-illuminating-earth-s-surface-1851190/
Download the smallest (source), and the nearest output size. Then AI generated and compare. Pexels allowed you to download multiple sizes by selecting the options next to the download button.


js-interop:

I am calling this function in javascript with the window.receiveDeviceStatus and it doesn't seem to be working, the error i am getting is window.receiveDeviceStatus is not a function.
Does it happen in Dartium or when compiled to JavaScript?

Dart SDK version: use Dart 2.12.0 (build 2.12.0-133.7.beta)
pkg/js version: js: ^0.6.2`

Failing code:
@JS()
library callable_function;

import 'package:js/js.dart';

/// Allows assigning a function to be callable from `window.functionName()`
@JS('updatedevice')
external set pReceiveDeviceStatus(void Function() f);

/// Allows calling the assigned function from Dart as well.
@JS()
external void receiveDeviceStatus();

void _someDartFunction() {
  print('Hello from Dart!');
}

void main() {
  pReceiveDeviceStatus = allowInterop(_someDartFunction);
  // JavaScript code may now call `functionName()` or `window.functionName()`.
}

@srvstvnhl any luck? Getting the same error


GPU availability check before deployment

Is your feature request related to a problem? Please describe.
When I want to deploy the pod in the specific location I cannot get information about availability in that location. Current gpu_query allows only to specify gpu_id and gpu_count to get the list of GPUs.
Describe the solution you'd like
I would like to be able to send a get request to check if there is a GPU with given parameters (the same as I latter provide to create_pod()).
Describe alternatives you've considered
Maybe an external API to request data from (beside python lib)?
Additional context
None

I can add a general availability check; however, this would not help when the GPU becomes unavailable between checking and creating the pod. Is that what you are looking for?

I've just raised #307 to retrieve the machine information necessary from the runpod GraphQL API to enable this.


docker-compose with extra ssh options doesn't work.

Hello,
I have build the image from container/wetty/dockerfile
and alerted docker-compose to have command as:
command: yarn start --sshhost <IP_ADDRESS> --sshport 2222 --sshuser dockuser --title Test-Console --base /console/ --sshauth publickey --sshkey ~/.ssh/id_rsa_wetty
The image gets deployed. but connecting to localhost:3000/console shows  ssh-client login:
This is what the docker image process shows.
root | 525 | 15473 | 0 | 15:18 | pts/1 | 00:00:00 | login -h localhost
root | 15473 | 15446 | 0 | Jan01 | ? | 00:00:04 | node . yarn start --sshhost <IP_ADDRESS> --sshport 2222 --sshuser dockuser --sshauth publickey --sshkey /root/.ssh/id_rsa_wetty --title Test-Console --base /console/
I am concern over the process "login -h localhost" This was suppose to be the custom ssh commands.
Any idea.
Thanks,

Hello, correction, so i made a mistake.
the docker-compose command should be: yarn start --ssh-host <IP_ADDRESS> --ssh-port 2222 --ssh-user dockuser --title Test-Console --base /console/ --ssh-auth publickey --ssh-key ~/.ssh/id_rsa_wetty
But even after this, access console, ask for username and then the connection drops and reconnect button shown.
any idea.

Hello, correction, so i made a mistake.
the docker-compose command should be: yarn start --ssh-host <IP_ADDRESS> --ssh-port 2222 --ssh-user dockuser --title Test-Console --base /console/ --ssh-auth publickey --ssh-key ~/.ssh/id_rsa_wetty
But even after this, access console, ask for username and then the connection drops and reconnect button shown.
any idea.

This is a weird one, it appears that ssh is ignoring the -p flag passed to it from wetty and just using the default port 22.
inspecting the pid i can see that the correct args are being passed

This is a weird one, it appears that ssh is ignoring the -p flag passed to it from wetty and just using the default port 22.
inspecting the pid i can see that the correct args are being passed

$  ps -fp 1832320
UID          PID    PPID  C STIME TTY          TIME CMD
butlerx  1832320 1832225  0 10:35 pts/24   00:00:00 ssh butlerx@localhost -t   -p 2222 -o PreferredAuthentications=password -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no
$  ssh butlerx@localhost -t   -p 2222 -o PreferredAuthentications=password -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no
ssh: connect to host localhost port 2222: Connection refused```

$  ps -fp 1832320
UID          PID    PPID  C STIME TTY          TIME CMD
butlerx  1832320 1832225  0 10:35 pts/24   00:00:00 ssh butlerx@localhost -t   -p 2222 -o PreferredAuthentications=password -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no
$  ssh butlerx@localhost -t   -p 2222 -o PreferredAuthentications=password -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no
ssh: connect to host localhost port 2222: Connection refused```

This issue looks to be  the same as #308 going to close and continue in that issue

This issue looks to be  the same as #308 going to close and continue in that issue


Fix bug #334

Just check if the 'Desc' -key is present, if not, use the 'Value' field, which at least should be.
I added an assert to make diagnosing this a bit easier, if it ever happens that 'Value' might not be present.

Thanks to point that, should be related to remove_col_not_exist_parts('desc'). A correct replacement of this call should work.
I will check this.

Commit accept but after I replaced by a more compact solution.


Fixes missing recursive-readdir dependency needed for npm run flow:re…

Fixes issue described here: https://github.com/ctrlplusb/react-universally/issues/152

Thanks so much for this.  Would you be open to modifying the flow removals script to use the following technique?
https://github.com/ctrlplusb/react-universally/blob/master/tools/development/ensureVendorDLLExists.js#L50
I am happy to add you as a collaborator to this project.  I am trying to encourage more help, and it's great to see you taking the initiative here.

Sure ! I'll gladly make the change & will try to update the PR later today.


[stable/jenkins] Added backup service account annotations and pod securitycontext

Ive checked this on my local project and it works fine, adds annotation to the service account Jenkins-backup and sets proper securitycontext to the backup pod.
What this PR does / why we need it: Adds annotations to the jenkins-backup service account and securitycontext runAsUser and fsGroup to the pod generated by backup Cronjob
Which issue this PR fixes

fixes 22670

Special notes for your reviewer:
This is my first PR so dunno if ive done everything right, please guide me if there is something wrong.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

@torstenwalter New PR regarding the old one (https://github.com/helm/charts/pull/22730) that had some issues along the way with signoff. Hope this one will be ok ?

📢 stable/jenkins has moved to https://github.com/jenkinsci/helm-charts. If still applicable, please reopen the PR there. Thanks!


Difference with spring-cloud-sleuth-brave

Sorry but I would like to ask what is the difference between this project and spring-cloud-sleuth-brave.
I'm using sleuth default tracing implementation which is brave.
I want to know how far will this project go and if it will replace brave in the future.
Thanks.

Spring Cloud Sleuth is feature complete and you should migrate to Micrometer Tracing and Boot 3 in the future. You can read the migration guide here https://github.com/micrometer-metrics/tracing/wiki/Spring-Cloud-Sleuth-3.1-Migration-Guide


Document update process

Update documentation with directions for updating.

Optional: To keep existing database copy game_cache and game_cache-times into unzipped new copy
Delete old installation and replace with new

Also note replacing extracted configuration files with old custom copy (if there were no breaking changes)


Refactor duplicated function expressions for extracting hex and alpha colors

I changed to private method and added jsdoc as suggested. I don't understand why the build fails on only firefox on linux, even though the code does not seem to be browser dependent.

Looks good.  Can you please squash this down to a single commit so we can pull it?

I have squashed my commits into a single one.
I notice that many of my builds fail on particular browsers. I am aware that the compatibility of FF41 may be one of the causes, but sometimes they fail also on particular versions of IE. What will be possible causes for my failed builds?
As I can test my code on only a single platform and I do not have access to the build reports in SauceLabs, I am interested in how certain commits or upgrade of certain browsers lead to build failures.

@kencheung I took a look at the test failures in IE, and they're not related to your PR. Don't worry about it.

I still see "9 commits" up at the top.    Otherwise the push will fail and suggest you pull and merge, which defeats the whole purpose of squashing.  Try git log --graph --decorate --color --all to see more clearly what I mean.

I think it works this time. Thank you very much for your help.


kore: 4.0.1 -> 4.1.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/kore/versions.
meta.description for kore is: "An easy to use web application framework for C"
meta.homepage for kore is: "https://kore.io"
meta.changelog for kore is: ""
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 4.1.0 with grep in /nix/store/1gxfwsnbr221lq4qndcapqkljnmjiz5n-kore-4.1.0

directory tree listing: https://gist.github.com/7db03a487ec93af338aa613d0a00c9cd

du listing: https://gist.github.com/4cc85baab8ae2c83ef98fc7a2a8e694f

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
kore

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1gxfwsnbr221lq4qndcapqkljnmjiz5n-kore-4.1.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A kore https://github.com/r-ryantm/nixpkgs/archive/ba1cf80b7ca43f85b9b31875dff75f8153fd64e8.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1gxfwsnbr221lq4qndcapqkljnmjiz5n-kore-4.1.0
ls -la /nix/store/1gxfwsnbr221lq4qndcapqkljnmjiz5n-kore-4.1.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

kore

Maintainer pings
cc @johnmh for testing.

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

1 package built:

kore


Browser support?

Hello and thank you for sharing Liike with the rest of us.
Would you mind adding in the read me file information about what browsers Liike does support.
Thanks 👍

Good point! The only thing that requires newer browser is requestAnimationFrame which has been around since IE10. You can polyfill it pretty easily though.
I’ll add this information to the readme. Thanks! 😎👍

Added!


Improperly placed tag v5.3.1

You placed tag v5.3.1 to a commit 762396d997b4e155778ba62346376b37b4673154 but it should point to the f4319c12803f27a93150178f8b61f10aea09ce01 most probably.

You are right, sorry it took so long to fix.


STORM-3301: Fix case where KafkaSpout could emit tuples that were alr…

…eady committed
1.x version of https://github.com/apache/storm/pull/2922

solution need


Rename exp.html to experiment.html

I don't know of any reason for the slightly cryptic name.

Because it'll break old stuff, let's leave this be for now.

This issue was moved to Dallinger/Dallinger#147


Meta sync for F&Fs

We'll have a surface data(meta) sync for F&F's when the user lands on screens like F&F, ManageBackup, Send, and then when a contact is specifically selected(and the channel is active + have the new data flag set) that is when we fetch the encrypted data specifically for that contact, decrypt and store it.

Dev task


Validation doesn't work at some circumstances.

validation doesn't work in following case. A space is missing between "name" and "test". But there is no error red line to remind user.

@andxu would you be able to look at this? seems like another yaml parser issue.

@andxu Do you have time to look into these issues?

I will look into this issue, it seems a bug in vscode-yaml owned by redhat, it might need some time for the final fix to be available at market place.

Add a PR to solve the missing validation rule.
But for the timestamp issue, the schema definition is a string type. Although kubectl apply doesn't complain it, i prefer to keep the strict rule to give an error for null value.

Although kubectl apply doesn't complain it, i prefer to keep the strict rule to give an error for null value

null is a valid string. (Well, you can define a type system where it's not, but it doesn't seem relevant in this case.) The validation output tool is substantially less valuable if

null is an interesting question in json validator. Agree that the validation should be accurate.
A quick fix on the schema side is changing the type of timestamp to ['string', 'null'], that can pass the validation. The problem here is it looks like a generic problem, and should be fixed at the generic vscode-yaml extension side.

@testforstephen @andxu If we think this is a bug in vscode-yaml, can we raise it there with a small repro (smaller than our massive Swagger file anyway!), and link that back to this issue please?  Thanks!

Created an issue https://github.com/redhat-developer/yaml-language-server/issues/72

Verified, the results as below:
Build: 4626

Scenarios
Windows
Mac
Linux

A space is missing, but there is no error red line to remind user.
Not repro
Not repro
Not repro

Yaml validator will report an error for null value when the   schema type is string.
Repro
Repro
Repro

The latest version 0.0.13 of vscode-yaml extension has fixed the null value validation bug. So close the issue.

@testforstephen VS Code doesn't provide a way to declare a dependency on a particular version of another extension, does it?  So I should possibly add some documentation around this...

Correct, there's no way to specify the specific dependency version. And every time VS Code is reloaded or restarted, it'll auto check the latest version for all the installed extensions and auto upgrade to latest version by default.

@testforstephen there is a setting 'extensions.autoUpdate' in vscode defaults to true, if user chooses to disable it, vscode will not update the extensions automatically, so you'd better to specify the minimal vscode-yaml version, or check this version in our extension.


Can not save ELMoTransformer

When save ElmoTransformer ,it ocurs
RecursionError: maximum recursion depth exceeded

@QDPeng
The same issue.
Did you solve the problem?


ZZZ SUPPORT

can i add Z.Z.Z ?
TOday realase 24.07.04
plz support Z.Z.Z
thank you <3

Hi
I'm currently working on it, and new version will be released this week.

Always Thank you <3 im waiting

Closing issue.
Version 1.3.2, which contains zzz check-in feature, has been released.
Please check app updates.


feat: add Tilix colors

Description
Based off of Alacritty colors.

I just merged #21, you may need to solve the conflicts.

I added a new wiki page that lists some ports of this color scheme. This page can be edited by anyone, so users can share their ports freely.

I added a new wiki page that lists some ports of this color scheme. This page can be edited by anyone, so users can share their ports freely.

Good idea. I like it.


dynatrace_alerting_profile does not work correctly

I can create an alerting profile that contains mixed Predefined and Custom event filters. Trying to do the same via Terraform HCL fails. A snippet of the Terraform HCL config that is failing:
### dynatrace_alerting_profile ###
resource "dynatrace_alerting_profile" "alerting_profile" {

    display_name = "Microsites"
    mz_id = local.management_zone
    event_type_filters {
        predefined_event_filter {
            event_type = "APPLICATION_ERROR_RATE_INCREASED"
        }
        predefined_event_filter {
            event_type = "SERVICE_ERROR_RATE_INCREASED"
        }
        predefined_event_filter {
            event_type = "DATABASE_CONNECTION_FAILURE"
        }
        predefined_event_filter {
            event_type = "MONITORING_UNAVAILABLE"
        }
        custom_event_filter {
            custom_description_filter {
                operator = "EQUALS"
                value = "Name"
                case_insensitive = false
                enabled = true
            }
            custom_title_filter {
                operator = "EQUALS"
                value = "Name"
                case_insensitive = false
                enabled = true
            }
        }
    }

When trying to create alerting profile via Terraform it fails with the error below:

dynatrace_alerting_profile.alerting_profile: Modifying... [id=23e073ee-8616-33ba-870e-7002d08158cb]
╷
│ Error: {
│   "code": 400,
│   "message": "Constraints violated.",
│   "constraintViolations": [
│     {
│       "parameterLocation": "PAYLOAD_BODY",
│       "location": "",
│       "message": "The parameters of this object are mutually exclusive. Please only provide one of the 2 filters",
│       "path": "eventTypeFilters[0]"
│     }
│   ]
│ }
│
│   with dynatrace_alerting_profile.alerting_profile,
│   on monitoring.tf line 29, in resource "dynatrace_alerting_profile" "alerting_profile":
│   29: resource "dynatrace_alerting_profile" "alerting_profile" {

Hello @moseskt
It looks like you've run into a limitation of the Config REST API of Dynatrace here.
It doesn't accept certain combinations of filters while the WebUI allows for it.
The resource dynatrace_alerting takes care of that. It utilizes the Settings 2.0 REST API. Here the functionality is indeed streamlined with the WebUI.
The example you've provided looks like this when using dynatrace_alerting.
resource "dynatrace_alerting" "alerting_profile" {
  name            = "Microsites"
  management_zone = "d4a898f9-abb4-4f20-a913-201a86f81335"
  filters {
    filter {
      predefined {
        type = "APPLICATION_ERROR_RATE_INCREASED"
      }
    }
    filter {
      predefined {
        type = "SERVICE_ERROR_RATE_INCREASED"
      }
    }
    filter {
      predefined {
        type = "DATABASE_CONNECTION_FAILURE"
      }
    }
    filter {
      predefined {
        type = "MONITORING_UNAVAILABLE"
      }
    }
    filter {
      custom {
        description {
          operator       = "STRING_EQUALS"
          value          = "Name"
          case_sensitive = true
          enabled        = true
        }
      }
    }
    filter {
      custom {
        title {
          operator       = "STRING_EQUALS"
          value          = "Name"
          case_sensitive = true
          enabled        = true
        }
      }
    }
  }
}

Let me know if that solves your difficulties.

Closing the ticket for now, please re-open it if you have any issues with the solution that @Dynatrace-Reinhard-Pilz provided. Thanks!


Single Fetch throwing response does not work

Reproduction
https://stackblitz.com/edit/remix-run-remix-ndbnrb?file=app%2Froutes%2F_index.tsx,app%2Froot.tsx,tsconfig.json
System Info
System:
    OS: macOS 14.3
    CPU: (16) arm64 Apple M3 Max
    Memory: 229.22 MB / 64.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.11.1 - ~/.nvm/versions/node/v20.11.1/bin/node
    npm: 10.2.4 - ~/.nvm/versions/node/v20.11.1/bin/npm
    pnpm: 9.5.0 - ~/.nvm/versions/node/v20.11.1/bin/pnpm
  Browsers:
    Chrome: 127.0.6533.72
    Safari: 17.3

Used Package Manager
npm
Expected Behavior
Loader states should always stay consistent. E.g. useLoaderData<typeof loader> should always contain the latest valid loader data
Actual Behavior
Loader state isnt consistent when using throw response with single fetch. It becomes undefined unexpectedly leading to destructuring errors (see stackblitz)

@brophdawg11 Thanks for your explanation, however, I am throwing the response stub which per the docs is a way to the short circuit actions/loaders to immediately respond to the incoming request. So what is happening here is that an error is incorrectly thrown by Remix, while it should have just sent a normal response

So what is happening here is that an error is incorrectly thrown by Remix

How so?  Your code is throwing the response stub - and any time you throw anything from a loader/action you trigger an ErrorBoundary.
Can you point to the section of the docs that is causing the confusion?

Redirects are different than errors since you're telling the router to navigate to a new route, as opposed to informing it of an error on the current route.
You're not throwing a redirect in your reproduction though - you're throwing a response stub with a 400 status.  Without single fetch, that's equivalent to throw json({ error: "broken" }, { status: 400 }) which would trigger the ErrorBoundary in the same way.

Redirects are different than errors since you're telling the router to navigate to a new route, as opposed to informing it of an error on the current route.
You're not throwing a redirect in your reproduction though - you're throwing a response stub with a 400 status. Without single fetch, that's equivalent to throw json({ error: "broken" }, { status: 400 }) which would trigger the ErrorBoundary in the same way.

You're right, I've only ever thrown with redirect before so didn't realize it worked this way. I notice though that single fetch's types override useRouteLoaderData always return something, i.e., it removes the | undefined from the return type (see https://github.com/remix-run/remix/blob/ac747ff7cdd8dde2b50fdf392fce0a29bbf2257f/packages/remix-react/future/single-fetch.d.ts#L27-L29). This seems inconsistent with this behavior

it removes the | undefined from the return type

Ah thanks for pointing this out - this is a bug.  In your case useRouteLoaderData("root") will always be defined but if you put an invalid route id or a non-mounted id in there it would be undefined - got this fixed in #9796 👍

How exactly is the behavior different between the two, and for what reason? It’s not clear from the docs. I only seitched to it for the | ubdefined and was surprised it never became undefined during errors unlike useLoaderData


cargo-generate: 0.5.3 -> 0.11.0

Motivation for this change
Bump version package version (https://github.com/cargo-generate/cargo-generate/blob/master/CHANGELOG.md)
Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

P.S. one test fails because access to the github server was used (disabled via patch)
P.S.S. Closes the PR #129345

@SuperSandro2000 I think this is ready for merge. thanks

git::should_canonicalize failed on darwin, any reasons it is failing and shall we skip it on darwin?

git::should_canonicalize failed on darwin, any reasons it is failing and shall we skip it on darwin?

I'll check why this crash happened.

git::should_canonicalize failed on darwin, any reasons it is failing and shall we skip it on darwin?

I'll check why this crash happened.

Yeah, this test assumes that is runs from /Users/ directory


WIP: Implement jwt

What changed?

Why?

How did you test it?

Potential risks

Release notes

Documentation Changes

Thanks for making this contribution! this is an important feature that many people are wishing to have.

This part of the code is only validating the token, not creating it. Is this the only task expected at this point? (Based on the task list)
Yes, we will do that in other tasks when sending authorized requests.

Pull Request Test Coverage Report for Build 1c1b7202-cbd1-42a3-9822-fb7a974bb22e

109 of 129 (84.5%)  changed or added relevant lines in 10 files are covered.
5 unchanged lines in 3 files lost coverage.
Overall coverage increased (+0.09%) to 56.719%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

cmd/server/cadence/server.go
0
1
0.0%

common/config/config.go
2
4
50.0%

common/authorization/authorizer.go
4
10
40.0%

common/util.go
0
11
0.0%

Files with Coverage Reduction
New Missed Lines
%

service/history/execution/mutable_state_task_refresher.go
1
74.4%

common/task/fifoTaskScheduler.go
2
87.63%

common/task/weightedRoundRobinTaskScheduler.go
2
89.64%

Totals

Change from base Build d86cb3da-bb92-4fde-9e2f-caf8388d0cde:
0.09%

Covered Lines:
77579

Relevant Lines:
136777

💛  - Coveralls


Invalid cron expression

Hi,
thanks for this app, the first android crond that works for me.
However it reports a lot of "Invalid cron expression" if crontab contains:

commented lines, starting with #
empty lines
lines with fields separated by Tabs instead of spaces

Also, it would be nice to have crontab and log in (larger) separate windows and buttons and checkboxes in a settings page or menu.

Glad, you like it.
About "Invalid cron expression":
To be quite honest: This doesn't bother me too much. Also it's technically correct ;)
Recognizing all the different kinds of none cron expression and deciding what an invalid cron expression is and what is something completely different, can get complex and error prone really fast.
And what do you gain? A somewhat nicer error message?
You're welcome to take a shot at it yourself :)
About the UI design:
I actually quite like everything beeing on one screen. and not having to search through several pages. It's on the edge of beeing too much stuff on the screen at the same time, but I don't think it has crossed it. Especially with such large screen today.


test_trialwise_decoding fails

On current master (commit 462028a7b77d2a1751f8526de4fbd8122d56f92c) the acceptance test test_trialwise_decoding fails for me. The train loss for instance is different from the values hardcoded in the test.
In test:
[1.1114974617958069,
1.0976492166519165,
0.668171226978302,
0.5880511999130249,
0.7054798305034637,
0.5272344648838043]
On CPU, torch==1.4.0:
[1.1114973425865173, 0.6608118116855621, 0.8881862759590149, 0.5603521466255188, 0.6126846820116043, 0.3842557668685913]
I also tried on GPU for fun:
[0.949962854385376, 0.9517839550971985, 0.7434093356132507, 0.6833578497171402, 0.9080942273139954, 0.3789084255695343]
@robintibor @sliwy would you know why this fails?

I think that it may be connected with #134. It fails with skorch version 0.8. Can you check if it works with skorch==0.7?

Ah good catch @sliwy! It does work with skorch==0.7.
I took a quick look at the changes from 0.7 to 0.8 but couldn't identify the culprit https://github.com/skorch-dev/skorch/compare/v0.7.0...v0.8.0. It seems like they've changed the fit loop, maybe that had an impact?

can you make the test less strict so it works for both versions?

@agramfort I think it would be nice to understand what is behind this difference between versions... If it ends up being too complicated I can just modify the test though.
I've looked at the differences from 0.7 to 0.8 and I think it might be caused by the introduction of the new PassthroughScoring class as default for NeuralNet instead of BatchScoring. Could there be an interaction with EEGClassifer` @sliwy @robintibor ?

yeah I agree we should look inside. Did not look at the PassthroughScoring class yet, but definitely such interactions may be there and cause problems. may try to have a look on friday

@robintibor that was fixed in #155 right?

yep should be fixed, thanks for the notice


Jmeter Functional Tests (Service Description and Policy Data Model)

Performs service description and policy data model tests either locally or remotely via jmeter (just change the URL in the test plan). See README.markdown for more info

Austin,
I don't see anything here that effects core functionality, so merging isn't a problem. However, before we do that is there anything special one needs to execute this test?  I'd like to know it works before I merge into master, and knowing we don't have a mock LR to test the tests, a little more explanation is needed. Like do these changes only effect the Basic Publish.jmx file?
There's obviously a lot of code included with this, and it's not really clear to me the coverage that's going on.

I'd be happy to provide more information to you in terms of coverage and setup; unfortunately I broke my femur this weekend and the pain medication limits my ability to communicate effectively. I will try to do my best later on today. Thank you for taking a glance at it though!
Sent from my iPhone
On Dec 19, 2011, at 3:39 PM, Jim<EMAIL_ADDRESS>wrote:

Austin,
I don't see anything here that effects core functionality, so merging isn't a problem. However, before we do that is there anything special one needs to execute this test?  I'd like to know it works before I merge into master, and knowing we don't have a mock LR to test the tests, a little more explanation is needed. Like do these changes only effect the Basic Publish.jmx file?
There's obviously a lot of code included with this, and it's not really clear to me the coverage that's going on.

Reply to this email directly or view it on GitHub:
https://github.com/LearningRegistry/LearningRegistry/pull/150#issuecomment-3210920

I added additional sections to the existing README based on your questions about coverage and usage, which can be found here: https://github.com/armontoya/LearningRegistry/blob/jmeter_functional/jmeter_tests/README.markdown. Please let me know if this sufficiently answers your questions.


Add dir-start-index fuseStressBench

When generating data in fuse stressbench, user can choose the directory names to start from a certain index.
With this change, user is able to generate all test data in different batches. For example, for the first batch we set --num-dirs 10 and --dir-start-index 0, and for the second batch we set --num-dirs 10 and --dir-start-index 10, we are able to generate 20-dirs test files that is recognizable by reading stress bench.

@apc999 FYI

alluxio-bot, merge this please

@maobaolong This is more like a workaround in my opinion. But feel free to submit a PR to the main branch.

@ssz1997 Could us let jenkins bot to cherry-pick this to the main branch?


Retry on ClientError exceptions with backoff

getting a little more retry logic in
want to do more around configurability, but will come later

Coverage decreased (-0.1%) to 97.34% when pulling b8ce067026031be46d975a142eaf848ebd650509 on more-retry into 8106eb151c3d76bd844875645256ee1984fca794 on devel.

Coverage decreased (-0.1%) to 97.34% when pulling b8ce067026031be46d975a142eaf848ebd650509 on more-retry into 8106eb151c3d76bd844875645256ee1984fca794 on devel.

Coverage decreased (-0.1%) to 97.34% when pulling b8ce067026031be46d975a142eaf848ebd650509 on more-retry into 8106eb151c3d76bd844875645256ee1984fca794 on devel.

Coverage decreased (-0.1%) to 97.34% when pulling b8ce067026031be46d975a142eaf848ebd650509 on more-retry into 8106eb151c3d76bd844875645256ee1984fca794 on devel.

Coverage decreased (-0.1%) to 97.34% when pulling b8ce067026031be46d975a142eaf848ebd650509 on more-retry into 8106eb151c3d76bd844875645256ee1984fca794 on devel.

Coverage decreased (-0.2%) to 97.257% when pulling 909bccd57bdaddcedcf724237dfc4454a23bf65c on more-retry into 8106eb151c3d76bd844875645256ee1984fca794 on devel.

+1


Incorrectly parsing property as in operator

Acorn incorrectly parses a property as an in operator and then proceeds to parse a divide as a regex.
0123. in/alert(1)/i
If this parser was being used in a sandbox then this could bypass it.

Good catch -- that was definitely obscure, it took me a while to figure out why this was even supposed to parse that way. Fixed by attached patch.


Reference to non-existing directory

When I run npm run bootstrap, I get:
npm ERR! code ENOENT
npm ERR! syscall chmod
npm ERR! path /~/rmf-web/packages/dashboard/node_modules/ros2-bridge/src/index.js
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, chmod '/~/rmf-web/packages/dashboard/node_modules/ros2-bridge/src/index.js'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

however the folder node_modules doesn't seem to exist

You need to give more context on what you are doing,
which package does it fail on?
were there any other errors from npm?
were you able to build the typescript files?
are you running as root?

Here's the full log. Previous steps did not report errors. I'm running inside a docker container as root. Not sure what you mean by "you need to give more context". I'm simply following the instructions in the main README.
> root@ bootstrap /~/rmf-web
> node scripts/bootstrap.js

><EMAIL_ADDRESS>install /~/rmf-web/node_modules/husky
> node husky install

husky > Setting up git hooks
husky > Done

><EMAIL_ADDRESS>postinstall /~/rmf-web/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"

[...]
><EMAIL_ADDRESS>postinstall /~/rmf-web/node_modules/core-js-pure
> node -e "try{require('./postinstall')}catch(e){}"

[...]

><EMAIL_ADDRESS>postinstall /~/rmf-web/node_modules/husky
> opencollective-postinstall || exit 0

[...]

npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/watchpack-chokidar2/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

[...]

><EMAIL_ADDRESS>install /~/rmf-web/packages/ros2-bridge/node_modules/int64-napi
> node-gyp rebuild

make: Entering directory '/~/rmf-web/packages/ros2-bridge/node_modules/int64-napi/build'
  CC(target) Release/obj.target/int64/src/int64.o
  SOLINK_MODULE(target) Release/obj.target/int64.node
  COPY Release/int64.node
make: Leaving directory '/~/rmf-web/packages/ros2-bridge/node_modules/int64-napi/build'

><EMAIL_ADDRESS>install /~/rmf-web/packages/ros2-bridge/node_modules/ref-napi
> node-gyp-build

><EMAIL_ADDRESS>install /~/rmf-web/packages/ros2-bridge/node_modules/rclnodejs
> node-gyp rebuild

make: Entering directory '/~/rmf-web/packages/ros2-bridge/node_modules/rclnodejs/build'
  CXX(target) Release/obj.target/rclnodejs/src/addon.o
In file included from ../../nan/nan.h:56,
                 from ../src/addon.cpp:15:
/root/.cache/node-gyp/12.20.1/include/node/node.h:737:43: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
  737 |       (node::addon_register_func) (regfunc),                          \
      |                                           ^
/root/.cache/node-gyp/12.20.1/include/node/node.h:771:3: note: in expansion of macro ‘NODE_MODULE_X’
  771 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
      |   ^~~~~~~~~~~~~
../src/addon.cpp:94:1: note: in expansion of macro ‘NODE_MODULE’
   94 | NODE_MODULE(rclnodejs, InitModule);
      | ^~~~~~~~~~~
  CXX(target) Release/obj.target/rclnodejs/src/executor.o
  CXX(target) Release/obj.target/rclnodejs/src/handle_manager.o
  CXX(target) Release/obj.target/rclnodejs/src/rcl_action_bindings.o
  CXX(target) Release/obj.target/rclnodejs/src/rcl_bindings.o
  CXX(target) Release/obj.target/rclnodejs/src/rcl_handle.o
  CXX(target) Release/obj.target/rclnodejs/src/rcl_lifecycle_bindings.o
  CXX(target) Release/obj.target/rclnodejs/src/rcl_utilities.o
  CXX(target) Release/obj.target/rclnodejs/src/shadow_node.o
  SOLINK_MODULE(target) Release/obj.target/rclnodejs.node
  COPY Release/rclnodejs.node
make: Leaving directory '/~/rmf-web/packages/ros2-bridge/node_modules/rclnodejs/build'

><EMAIL_ADDRESS>postinstall /~/rmf-web/packages/ros2-bridge/node_modules/rclnodejs
> node scripts/generate_messages.js

Start JavaScript message generation...
Generation complete.
npm WARN lifecycle<EMAIL_ADDRESS>cannot run in wd<EMAIL_ADDRESS>npm run build (wd=/~/rmf-web/packages/ros2-bridge)
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

added 681 packages from 474 contributors and audited 682 packages in 18.437s

[...]

><EMAIL_ADDRESS>postinstall /~/rmf-web/packages/react-components/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"

[...]

><EMAIL_ADDRESS>postinstall /~/rmf-web/packages/react-components/node_modules/core-js-pure
> node -e "try{require('./postinstall')}catch(e){}"

[...]

><EMAIL_ADDRESS>postinstall /~/rmf-web/packages/react-components/node_modules/date-fns
> node ./docs/printV2Notice.js

[...]

npm WARN lifecycle<EMAIL_ADDRESS>cannot run in wd<EMAIL_ADDRESS>npm run build (wd=/~/rmf-web/packages/react-components)
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

added 986 packages from 586 contributors and audited 988 packages in 8.574s

[...]

npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/webpack-dev-server/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/watchpack-chokidar2/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

npm ERR! code ENOENT
npm ERR! syscall chmod
npm ERR! path /~/rmf-web/packages/dashboard/node_modules/ros2-bridge/src/index.js
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, chmod '/~/rmf-web/packages/dashboard/node_modules/ros2-bridge/src/index.js'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR!  Exit status 254
npm ERR!
npm ERR! Failed at the root@ bootstrap script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2021-02-05T21_30_54_171Z-debug.log

I replaced parts that seemed irrelevant with [...].
The 'complete log':
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/root/.nvm/versions/node/v12.20.1/bin/node',
1 verbose cli   '/root/.nvm/versions/node/v12.20.1/bin/npm',
1 verbose cli   'run',
1 verbose cli   'setup'
1 verbose cli ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose stack Error: missing script: setup
4 verbose stack     at run (/root/.nvm/versions/node/v12.20.1/lib/node_modules/npm/lib/run-script.js:155:19)
4 verbose stack     at /root/.nvm/versions/node/v12.20.1/lib/node_modules/npm/lib/run-script.js:63:5
4 verbose stack     at /root/.nvm/versions/node/v12.20.1/lib/node_modules/npm/node_modules/read-package-json/read-json.js:116:5
4 verbose stack     at /root/.nvm/versions/node/v12.20.1/lib/node_modules/npm/node_modules/read-package-json/read-json.js:436:5
4 verbose stack     at checkBinReferences_ (/root/.nvm/versions/node/v12.20.1/lib/node_modules/npm/node_modules/read-package-json/read-json.js:391:45)
4 verbose stack     at final (/root/.nvm/versions/node/v12.20.1/lib/node_modules/npm/node_modules/read-package-json/read-json.js:434:3)
4 verbose stack     at then (/root/.nvm/versions/node/v12.20.1/lib/node_modules/npm/node_modules/read-package-json/read-json.js:161:5)
4 verbose stack     at /root/.nvm/versions/node/v12.20.1/lib/node_modules/npm/node_modules/read-package-json/read-json.js:382:12
4 verbose stack     at /root/.nvm/versions/node/v12.20.1/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:123:16
4 verbose stack     at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
5 verbose cwd /~/rmf-web
6 verbose Linux 5.4.0-42-generic
7 verbose argv "/root/.nvm/versions/node/v12.20.1/bin/node" "/root/.nvm/versions/node/v12.20.1/bin/npm" "run" "setup"
8 verbose node v12.20.1
9 verbose npm  v6.14.10
10 error missing script: setup
11 verbose exit [ 1, true ]

Thanks for the extra info.
I don't see the typescript files being compiled, you might need to allow unsafe-perm https://docs.npmjs.com/cli/v6/using-npm/config#unsafe-perm.
Regarding the 2nd log
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/root/.nvm/versions/node/v12.20.1/bin/node',
1 verbose cli   '/root/.nvm/versions/node/v12.20.1/bin/npm',
1 verbose cli   'run',
1 verbose cli   'setup'
1 verbose cli ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose stack Error: missing script: setup
4 verbose stack     at run (/root/.nvm/versions/node/v12.20.1/lib/node_modules/npm/lib/run-script.js:155:19)
4 verbose stack     at /root/.nvm/versions/node/v12.20.1/lib/node_modules/npm/lib/run-script.js:63:5
4 verbose stack     at /root/.nvm/versions/node/v12.20.1/lib/node_modules/npm/node_modules/read-package-json/read-json.js:116:5
4 verbose stack     at /root/.nvm/versions/node/v12.20.1/lib/node_modules/npm/node_modules/read-package-json/read-json.js:436:5
4 verbose stack     at checkBinReferences_ (/root/.nvm/versions/node/v12.20.1/lib/node_modules/npm/node_modules/read-package-json/read-json.js:391:45)
4 verbose stack     at final (/root/.nvm/versions/node/v12.20.1/lib/node_modules/npm/node_modules/read-package-json/read-json.js:434:3)
4 verbose stack     at then (/root/.nvm/versions/node/v12.20.1/lib/node_modules/npm/node_modules/read-package-json/read-json.js:161:5)
4 verbose stack     at /root/.nvm/versions/node/v12.20.1/lib/node_modules/npm/node_modules/read-package-json/read-json.js:382:12
4 verbose stack     at /root/.nvm/versions/node/v12.20.1/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:123:16
4 verbose stack     at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
5 verbose cwd /~/rmf-web
6 verbose Linux 5.4.0-42-generic
7 verbose argv "/root/.nvm/versions/node/v12.20.1/bin/node" "/root/.nvm/versions/node/v12.20.1/bin/npm" "run" "setup"
8 verbose node v12.20.1
9 verbose npm  v6.14.10
10 error missing script: setup
11 verbose exit [ 1, true ]

It seems like it is running to run the setup script, which should not happen as part of the bootstrap. I'm assuming you are trying to run the setup script in packages/dashboard, if so, make sure that you are in the correct working directory.

I set it using npm config set unsafe-perm true and that seemed to do it!
After it had failed I had tried to run npm start so that's probably what those logs pertain to.
Side note: I had to run source ~/.nvm/nvm.sh before nvm install 12 to avoid nvm not found.
Thanks for your help. I think this can be closed - not sure if we want to add something to the instructions.


learn PSF

David's interested to have me work on this and has convinced me that it's important.

He convinced me too. Also to run on DECaLS I'd rather learn the psf than try integrate other people's stand-alone psf code. UQ may be more pressing for now though.


[Bug]: Topbar wrapper changed from img to svg

Describe the bug
In v6.5.0, I was able to change the logo of the swagger index document by having a custom css as below (as the wrapper contained img element:-
.topbar-wrapper > a img {
content: url("logo-secure.png");
height: 65px;
}
In updated version 6.7.1, its all changed to svg and now my logo doesnt work!
Please help.
Expected behavior
No response
Actual behavior
No response
Steps to reproduce
No response
Exception(s) (if any)
No response
Swashbuckle.AspNetCore version
No response
.NET Version
No response
Anything else?
No response

The version of swagger-ui between 6.5.0 and 6.7.1 was upgraded from 4.15.5 to 5.17.14.
The design of the user interface's HTML elements and how they interact with swagger-ui's JavaScript is not something we control.
You will need to update your code's CSS customisation for the topbar in swagger-ui v5 to achieve the desired effect.


Tuya entities "Unavailable" following end of Home Assistant Cloud trial ending/not fixed by renewal

Describe the bug
In my HA install (running in a VM on a Synology NAS), I have had a Tuya integration working for many months (maybe a year, even). Lately, I noticed that the entities for all of my Tuya devices show on the Dashboard in yellow and say they're unavailable.
I have verified the Tuya API information, removed the integration and re-added it, attempted adding the integration again (via Devices, but just adds another instance of the Integration).
Expected behavior
I would expect that, issue of why "Yellow" and "Unavailable" are good end-user diagnostics aside, that restoring all the outside-Home-Assistant issues (Tuya plan, and Home Assistant Cloud re-ups) would cause the devices to reappear and the entities become functional again-- in short orders.
Diagnostics for integrations and devices
config_entry-tuya-abf3fd107ae8d90c2ff1cc3710081ce8.json.txt
Screenshots

Home Assistant Version
Home Assistant 2023.1.7
Supervisor 2023.01.1
Operating System 9.5
Frontend 20230110.0 - latest
Additional context
Add any other context or logs about the problem here.

Same issue here, I guess the bug came with a new home assistant version

Update: All of the entities do appear in the Smart Life application, and are available in that app, and in Alexa and Google Home, but there is no such integration. I believe previously, the Tuya integration connected to these devices in Smart Life.

Yes.

I just saw that the Tuna IOT page has changed.
I remember having created an cloud app on iot.tuya.com. that disappeared.
So I think tuya changed something.

I kind of remember having to choose the Smart Life app as opposed to the Tuya Smart app when I set up that connection originally, but I don't remember seeing the option when I re-set it up.
My situation now seems to be that I have to go and re-add every device by hand onto the Tuya app, which I really don't want to do. It includes a set of eight recessed flood lamps that are about 11 ft high.
Fletcher
Brilliant Stupid, LLC.

Feb 7, 2023 20:28:34 darnoldser @.***>:

I just saw that the Tuna IOT page has changed.
I remember having created an cloud app on iot.tuya.com[https://iot.tuya.com]. that disappeared.
So I think tuya changed something.
—
Reply to this email directly, view it on GitHub[https://github.com/tuya/tuya-home-assistant/issues/907#issuecomment-1421982747], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAV7HNHCOSCY3ZGQARPVKU3WWMOGTANCNFSM6AAAAAAUNIY3HQ].
You are receiving this because you authored the thread.[Tracking image][https://github.com/notifications/beacon/AAV7HNFPWVZLFU4HSO5CRETWWMOGTA5CNFSM6AAAAAAUNIY3HSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSUYG6BW.gif]

I am sure that I had to setup a project online on the IOT developer webpage.
Following the description of the tuya integration:
https://www.home-assistant.io/integrations/tuya/
But that is not accessible anymore.
Regards

It took a week to get Tuya to extend my trial, which they finally did... But now:

all the devices are listed in Home Assistant
They all lost their names, so I don't know which lightbulb is which
They lost their configuration data, so they don't belong to any rooms anymore
When I add them to a room, they stay 'unavailable'.

I would happily buy bulbs that work reliably with Home Assistant... That's why I bought Tuya bulbs in the first place, and they worked reliably for the first 3 months. It doesn't seen like there's an actual reliable bulb with good open source software on the market. Is that really the case?

For what it's worth, I extended my trial, or even I think they give me a free account for a year, just pick the lowest level one for $0.00.
Other than this business with the integration knocking all of the devices offline, my Tuya bulbs have been fine for more than a year. The only issue I have with them sometimes is when the power flickers, or somebody flips the light switches on and off too quickly, and the bulbs go into setup mode. Usually, I can just turn off the light, and turn it back on and everything is fine.
Also, not a single thing I purchased was branded as Tuya, though. They were just fairly inexpensive bulbs with various Chinese non-names, but they all turned out to use the same app, which ultimately was Tuya.

Feb 9, 2023 14:11:24 Ian McFarland @.***>:

It took a week to get Tuya to extend my trial, which they finally did... But now:

all the devices are listed in Home Assistant

They all lost their names, so I don't know which lightbulb is which

They lost their configuration data, so they don't belong to any rooms anymore

When I add them to a room, they stay 'unavailable'.

I would happily buy bulbs that work reliably with Home Assistant... That's why I bought Tuya bulbs in the first place, and they worked reliably for the first 3 months. It doesn't seen like there's an actual reliable bulb with good open source software on the market. Is that really the case?
—
Reply to this email directly, view it on GitHub[https://github.com/tuya/tuya-home-assistant/issues/907#issuecomment-1424902399], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAV7HNDLV3F3FHFOHJQ3DELWWVTQHANCNFSM6AAAAAAUNIY3HQ].
You are receiving this because you authored the thread.[Tracking image][https://github.com/notifications/beacon/AAV7HNB23THR5NAJODMNDKDWWVTQHA5CNFSM6AAAAAAUNIY3HSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSU5ZEP6.gif]

Whilst re-adding the Tuya integration had no errors, when adding the Local Tuya integration, I was given a No permissions. Your subscription to cloud development plan has expired error.
This is odd because in my IOT page, ther are no API issues for that project...


Drop unused policies reduce scope.

There are several permissions we don't need any longer and other entire trust policies we don't need any longer

I'm going to update this to drop a couple policies I'm moving in-repo.

ok, we need https://github.com/chainguard-dev/enterprise-packages/pull/2782 to go in before we can merge this.


Crash report: SIGSEGV error

This is happening on Linux, version 1.9.0
Operating system: Linux
                  0.0.0 Linux 3.0.39-1.el6.elrepo.x86_64 #1 SMP Thu Aug 2 01:16:43 EDT 2012 x86_64
CPU: amd64
     family 6 model 44 stepping 2
     16 CPUs

Crash reason:  SIGSEGV
Crash address: 0x0

Thread 0 (crashed)
 0  phantomjs!QVariant::QVariant [qatomic_x86_64.h : 121 + 0x0]
    rbx = 0x00007fff3da16a70   r12 = 0x0000000002ffdde0
    r13 = 0x0000000002ff9f60   r14 = 0x00007fff3da16a70
    r15 = 0x000000000304b2d0   rip = 0x0000000001cf520c
    rsp = 0x00007fff3da16980   rbp = 0x0000000002ff9f60
    Found by: given as instruction pointer in context
 1  phantomjs!Callback::call [callback.cpp : 44 + 0xa]
    rbx = 0x00007fff3da16a10   r12 = 0x0000000002ffdde0
    r13 = 0x0000000002ff9f60   r14 = 0x00007fff3da16a70
    r15 = 0x000000000304b2d0   rip = 0x000000000040ed1a
    rsp = 0x00007fff3da169a0   rbp = 0x0000000002ffddd0
    Found by: call frame info
 2  phantomjs!WebpageCallbacks::qt_static_metacall [webpage.cpp : 296 + 0x7]
    rbx = 0x00007fff3da171d0   r12 = 0x00007fff3da171d0
    r13 = 0x0000000002fad510   r14 = 0x000000000304b2c0
    r15 = 0x000000000304b2d0   rip = 0x000000000040f26e
    rsp = 0x00007fff3da16a70   rbp = 0x0000000000000000
    Found by: call frame info
 3  phantomjs!WebpageCallbacks::qt_metacall [webpage.moc : 163 + 0xe]
    rbx = 0x0000000000000000   r12 = 0x00007fff3da171d0
    r13 = 0x0000000002fad510   r14 = 0x000000000304b2c0
    r15 = 0x000000000304b2d0   rip = 0x000000000040f330
    rsp = 0x00007fff3da16aa0   rbp = 0x0000000000000000
    Found by: call frame info
 4  phantomjs!JSC::Bindings::QtRuntimeMetaMethod::call [qt_runtime.cpp : 1455 + 0x17]
    rbx = 0x00007fff3da16fa0   r12 = 0x000000000304b2d0
    r13 = 0x000000000304bac0   r14 = 0x000000000304b2c0
    r15 = 0x000000000304b2d0   rip = 0x000000000054a3f7
    rsp = 0x00007fff3da16ad0   rbp = 0x000000000304bab0
    Found by: call frame info
 5  phantomjs!JSC::cti_op_call_NotJSFunction [JITStubs.cpp : 2191 + 0x3]
    rbx = 0x0000000000000000   r12 = 0x00007fa33c4a0690
    r13 = 0x00007fa2f70bd8f0   r14 = 0x00007fff3da178d8
    r15 = 0x00007fa33c4a0628   rip = 0x0000000000f539f5
    rsp = 0x00007fff3da17880   rbp = 0x00007fff3da178e0
    Found by: call frame info
 6  0x7fa2f84688e7
    rbx = 0x00007fa340b75530   r12 = 0x00000000000001e4
    r13 = 0x00007fa33c4a0628   r14 = 0xffff000000000000
    r15 = 0xffff000000000002   rip = 0x00007fa2f84688e8
    rsp = 0x00007fff3da178e0   rbp = 0x00007fff3da17980
    Found by: call frame info
 7  phantomjs!JSC::Interpreter::executeCall [JITCode.h : 77 + 0x16]
    rip = 0x0000000000f24cf6   rsp = 0x00007fff3da17990
    Found by: stack scanning
 8  phantomjs!JSC::call [CallData.cpp : 38 + 0x21]
    rbx = 0x0000000002af3b90   r12 = 0x00007fa2f7e68758
    r13 = 0x00007fa2f7e68750   r14 = 0x00007fa340b6c8d0
    r15 = 0x00007fff3da17ab0   rip = 0x0000000000f6929d
    rsp = 0x00007fff3da17a60   rbp = 0x0000000000000000
    Found by: call frame info
 9  phantomjs!WebCore::ScheduledAction::executeFunctionInContext [JSMainThreadExecState.h : 48 + 0xb]
    rbx = 0x0000000002af3b90   r12 = 0x00007fa2f7e68758
    r13 = 0x00007fa2f7e68750   r14 = 0x00007fa340b6c8d0
    r15 = 0x00007fff3da17ab0   rip = 0x0000000001009a79
    rsp = 0x00007fff3da17a70   rbp = 0x0000000000000000
    Found by: call frame info
10  phantomjs!WebCore::ScheduledAction::execute [ScheduledAction.cpp : 132 + 0x29]
    rbx = 0x00007fa2f792f200   r12 = 0x00007fa2f7e68750
    r13 = 0x00007fa2f7b8d800   r14 = 0x0000000000000001
    r15 = 0x00007fa2f7b8d8d0   rip = 0x000000000100a14d
    rsp = 0x00007fff3da17be0   rbp = 0x00007fa340b6c8d0
    Found by: call frame info
11  phantomjs!WebCore::DOMTimer::fired [DOMTimer.cpp : 148 + 0xa]
    rbx = 0x00007fa33c0c3d68   r12 = 0x00007fa2f7e68750
    r13 = 0x0000000002af0988   r14 = 0x0000000000000008
    r15 = 0x00007fff3da17c80   rip = 0x00000000008abbd9
    rsp = 0x00007fff3da17c40   rbp = 0x00007fa2f7b8d8d0
    Found by: call frame info
12  phantomjs!WebCore::ThreadTimers::sharedTimerFiredInternal [ThreadTimers.cpp : 112 + 0x8]
    rbx = 0x00007fa33c0c3d68   r12 = 0x0000000000000000
    r13 = 0x0000000002b90aa0   r14 = 0x00000000000126b6
    r15 = 0x00007fff3da18410   rip = 0x000000000098ae73
    rsp = 0x00007fff3da17cd0   rbp = 0x00007fa340bd37a8
    Found by: call frame info
13  phantomjs!QObject::event [qobject.cpp : 1156 + 0x8]
    rbx = 0x0000000002f772c0   r12 = 0x00007fff3da18410
    r13 = 0x0000000002b90aa0   r14 = 0x00000000000126b6
    r15 = 0x00007fff3da18410   rip = 0x0000000001ce67c4
    rsp = 0x00007fff3da17d10   rbp = 0x0000000002f772c0
    Found by: call frame info
14  phantomjs!QApplicationPrivate::notify_helper [qapplication.cpp : 4562 + 0xc]
    rbx = 0x00007fff3da18690   r12 = 0x00007fff3da18410
    r13 = 0x0000000002b90aa0   r14 = 0x00000000000126b6
    r15 = 0x00007fff3da18410   rip = 0x00000000015d568f
    rsp = 0x00007fff3da17eb0   rbp = 0x0000000002f772c0
    Found by: call frame info
15  phantomjs!QApplication::notify [qapplication.cpp : 4423 + 0x17]
    rbx = 0x00007fff3da18690   r12 = 0x00007fff3da18410
    r13 = 0x00007fff3da18690   r14 = 0x00000000000126b6
    r15 = 0x00007fff3da18410   rip = 0x00000000015de31b
    rsp = 0x00007fff3da17ee0   rbp = 0x0000000002f772c0
    Found by: call frame info
16  phantomjs!QCoreApplication::notifyInternal [qcoreapplication.cpp : 946 + 0x2]
    rbx = 0x0000000002b8e1c0   r12 = 0x00007fff3da18410
    r13 = 0x00007fff3da18690   r14 = 0x00000000000126b6
    r15 = 0x00007fff3da18410   rip = 0x0000000001cd4fd4
    rsp = 0x00007fff3da183b0   rbp = 0x0000000002f772c0
    Found by: call frame info
17  phantomjs!QTimerInfoList::activateTimers [qcoreapplication.h : 231 + 0x14]
    rbx = 0x0000000002b91938   r12 = 0x0000000000000000
    r13 = 0x0000000000000000   r14 = 0x00000000000126b6
    r15 = 0x00007fff3da18410   rip = 0x0000000001cfeacd
    rsp = 0x00007fff3da18400   rbp = 0x000000000153cb5e
    Found by: call frame info
18  phantomjs!QEventDispatcherUNIX::processEvents [qeventdispatcher_unix.cpp : 941 + 0x7]
    rbx = 0x0000000000000000   r12 = 0x00007fff3da184e0
    r13 = 0x0000000002b8e030   r14 = 0x0000000000000001
    r15 = 0x0000000002b8e2d8   rip = 0x0000000001cfece0
    rsp = 0x00007fff3da18490   rbp = 0x0000000002b910d0
    Found by: call frame info
19  phantomjs!QEventDispatcherQPA::processEvents [qeventdispatcher_qpa.cpp : 246 + 0x4]
    rbx = 0x0000000002fef7a0   r12 = 0x0000000000000000
    r13 = 0x0000000002b8e030   r14 = 0x00007fff3da18520
    r15 = 0x0000000002b8e2d8   rip = 0x00000000016311e4
    rsp = 0x00007fff3da184e0   rbp = 0x0000000002b910d0
    Found by: call frame info
20  phantomjs!QEventLoop::processEvents [qeventloop.cpp : 149 + 0x1]
    rbx = 0x0000000002fef7a0   r12 = 0x00007fff3da185b0
    r13 = 0x00007fff3da185c0   r14 = 0x0000000002b8e230
    r15 = 0x0000000002b8e2d8   rip = 0x0000000001cd40b5
    rsp = 0x00007fff3da18520   rbp = 0x00007fff3da18560
    Found by: call frame info
21  phantomjs!QEventLoop::exec [qeventloop.cpp : 200 + 0x4]
    rbx = 0x0000000002fef7a0   r12 = 0x00007fff3da185b0
    r13 = 0x00007fff3da185c0   r14 = 0x0000000002b8e230
    r15 = 0x0000000002b8e2d8   rip = 0x0000000001cd4518
    rsp = 0x00007fff3da18550   rbp = 0x00007fff3da18690
    Found by: call frame info
22  phantomjs!QCoreApplication::exec [qcoreapplication.cpp : 1218 + 0x4]
    rbx = 0x0000000002b8e1c0   r12 = 0x00007fff3da18690
    r13 = 0x00007fff3da18858   r14 = 0x00007fff3da18600
    r15 = 0x0000000000000000   rip = 0x0000000001cd63cb
    rsp = 0x00007fff3da185b0   rbp = 0x0000000002b8e1c0
    Found by: call frame info
23  phantomjs!main [main.cpp : 118 + 0x4]
    rbx = 0x0000000002f4b6c0   r12 = 0x00007fff3da18690
    r13 = 0x00007fff3da18858   r14 = 0x00007fff3da18600
    r15 = 0x0000000000000000   rip = 0x0000000000427c42
    rsp = 0x00007fff3da185f0   rbp = 0x00007fff3da18828
    Found by: call frame info
24  libc-2.12.so + 0x1ecdc
    rbx = 0x0000000000000000   r12 = 0x0000000000407cc0
    r13 = 0x00007fff3da18820   r14 = 0x0000000000000000
    r15 = 0x0000000000000000   rip = 0x00007fa33f48bcdd
    rsp = 0x00007fff3da18750   rbp = 0x0000000000000000
    Found by: call frame info
25  phantomjs + 0x279ef
    rip = 0x00000000004279f0   rsp = 0x00007fff3da18770
    Found by: stack scanning

Thread 1
 0  libc-2.12.so + 0xaadbd
    rbx = 0x00007fa33d8a0d50   r12 = 0x00000000ffffffff
    r13 = 0x00007fa33d8a19c0   r14 = 0x0000000000000000
    r15 = 0x0000000000000003   rip = 0x00007fa33f517dbd
    rsp = 0x00007fa33d8a0c20   rbp = 0x00007fa33d8a0cd0
    Found by: given as instruction pointer in context
 1  libc-2.12.so + 0xaac2f
    rip = 0x00007fa33f517c30   rsp = 0x00007fa33d8a0c30
    rbp = 0x00007fa33d8a0cd0
    Found by: stack scanning
 2  phantomjs + 0x18ac86f
    rip = 0x0000000001cac870   rsp = 0x00007fa33d8a0c38
    rbp = 0x00007fa33d8a0cd0
    Found by: stack scanning
 3  ld-2.12.so + 0x9b86
    rip = 0x00007fa340ab2b87   rsp = 0x00007fa33d8a0c60
    rbp = 0x00007fa33d8a0cd0
    Found by: stack scanning
 4  phantomjs!WebPage::renderPdf [qmap.h : 185 + 0xb]
    rip = 0x00000000004173d8   rsp = 0x00007fa33d8a0c70
    rbp = 0x00007fa33d8a0cd0
    Found by: stack scanning

Thread 2
 0  libc-2.12.so + 0xde513
    rbx = 0x0000000000000000   r12 = 0x00007fa33d09fd70
    r13 = 0x0000000000000010   r14 = 0x00007fa338000a98
    r15 = 0x00007fa338000d30   rip = 0x00007fa33f54b513
    rsp = 0x00007fa33d09fb40   rbp = 0x00007fa3380008e0
    Found by: given as instruction pointer in context
 1  phantomjs!qt_safe_select [qcore_unix.cpp : 83 + 0x15]
    rip = 0x0000000001cfcf27   rsp = 0x00007fa33d09fb50
    Found by: stack scanning
 2  phantomjs!QEventDispatcherUNIXPrivate::doSelect [qeventdispatcher_unix.cpp : 223 + 0xd]
    rbx = 0x00007fa3380012b0   r12 = 0x00007fa33d09fd70
    r13 = 0x00007fa3380008e0   r14 = 0x0000000000000000
    r15 = 0x00007fa338000d30   rip = 0x0000000001cfe1e7
    rsp = 0x00007fa33d09fbe0   rbp = 0x00007fa3380008e0
    Found by: call frame info
 3  phantomjs!QEventDispatcherUNIX::processEvents [qeventdispatcher_unix.cpp : 937 + 0x4]
    rbx = 0x00007fa3380012b0   r12 = 0x00007fa33d09fd70
    r13 = 0x00007fa3380008c0   r14 = 0x0000000000000001
    r15 = 0x0000000002cb04d8   rip = 0x0000000001cfec92
    rsp = 0x00007fa33d09fd20   rbp = 0x00007fa3380008e0
    Found by: call frame info
 4  phantomjs!QEventLoop::processEvents [qeventloop.cpp : 149 + 0x1]
    rbx = 0x00007fa3380012b0   r12 = 0x00007fa33d09fe00
    r13 = 0x00007fa33d09fe10   r14 = 0x0000000002b8e230
    r15 = 0x0000000002cb04d8   rip = 0x0000000001cd40b5
    rsp = 0x00007fa33d09fd70   rbp = 0x00007fa33d09fdb0
    Found by: call frame info
 5  phantomjs!QEventLoop::exec [qeventloop.cpp : 200 + 0x4]
    rbx = 0x00007fa3380012b0   r12 = 0x00007fa33d09fe00
    r13 = 0x00007fa33d09fe10   r14 = 0x0000000002b8e230
    r15 = 0x0000000002cb04d8   rip = 0x0000000001cd4518
    rsp = 0x00007fa33d09fda0   rbp = 0x00007fff3da18690
    Found by: call frame info
 6  phantomjs!QThread::exec [qthread.cpp : 542 + 0xc]
    rbx = 0x0000000002cb0450   r12 = 0x0000000002cb04d8
    r13 = 0x0000000000000001   r14 = 0x0000000000000000
    r15 = 0x0000000000000003   rip = 0x0000000001bd69f6
    rsp = 0x00007fa33d09fe00   rbp = 0x0000000002cb04d8
    Found by: call frame info
 7  phantomjs!QThreadPrivate::start [qthread_unix.cpp : 338 + 0x9]
    rbx = 0x0000000002cb04d8   r12 = 0x0000000002cb05c0
    r13 = 0x0000000000000001   r14 = 0x0000000000000000
    r15 = 0x0000000000000003   rip = 0x0000000001bd98c2
    rsp = 0x00007fa33d09fe50   rbp = 0x0000000002cd7600
    Found by: call frame info
 8  libpthread-2.12.so + 0x77f0
    rbx = 0x0000000000000000   r12 = 0x00007fff3da17b70
    r13 = 0x00007fa33d0a09c0   r14 = 0x0000000000000000
    r15 = 0x0000000000000003   rip = 0x00007fa33ffb57f1
    rsp = 0x00007fa33d09fea0   rbp = 0x0000000000000000
    Found by: call frame info

Loaded modules:
0x00400000 - 0x026e3fff  phantomjs  ???  (main)
0x7fa2f717d000 - 0x7fa2f7190fff  n019003l.pfb  ???
0x7fa33d8a2000 - 0x7fa33dabffff  libselinux.so.1  ???
0x7fa33dac1000 - 0x7fa33dcd8fff  libresolv-2.12.so  ???
0x7fa33dcdb000 - 0x7fa33deddfff  libkeyutils.so.1.3  ???
0x7fa33dede000 - 0x7fa33e0e8fff  libkrb5support.so.0.1  ???
0x7fa33e0e9000 - 0x7fa33e314fff  libk5crypto.so.3.1  ???
0x7fa33e315000 - 0x7fa33e518fff  libcom_err.so.2.1  ???
0x7fa33e519000 - 0x7fa33e7f7fff  libkrb5.so.3.3  ???
0x7fa33e7f8000 - 0x7fa33ea39fff  libgssapi_krb5.so.2.2  ???
0x7fa33ea3a000 - 0x7fa33ec94fff  libssl.so.1.0.0  ???
0x7fa33ec95000 - 0x7fa33eeaafff  libz.so.1.2.3  ???
0x7fa33eeab000 - 0x7fa33f240fff  libcrypto.so.1.0.0  ???
0x7fa33f245000 - 0x7fa33f46cfff  libexpat.so.1.5.2  ???
0x7fa33f46d000 - 0x7fa33f808fff  libc-2.12.so  ???
0x7fa33f80e000 - 0x7fa33fa23fff  libgcc_s-4.4.6-20110824.so.1  ???
0x7fa33fa24000 - 0x7fa33fca7fff  libm-2.12.so  ???
0x7fa33fca8000 - 0x7fa33ff98fff  libstdc++.so.6.0.13  ???
0x7fa33ffae000 - 0x7fa3401c5fff  libpthread-2.12.so  ???
0x7fa3401ca000 - 0x7fa3403d1fff  librt-2.12.so  ???
0x7fa3403d2000 - 0x7fa3405d5fff  libdl-2.12.so  ???
0x7fa3405d6000 - 0x7fa34080bfff  libfontconfig.so.1.4.4  ???
0x7fa34080c000 - 0x7fa340aa8fff  libfreetype.so.6.3.22  ???
0x7fa340aa9000 - 0x7fa340ac8fff  ld-2.12.so  ???
0x7fa340cba000 - 0x7fa340cbdfff  87f5e051180a7a75f16eb6fe7dbd3749-le64.cache-3  ???
0x7fa340cbe000 - 0x7fa340cc6fff  b79f3aaa7d385a141ab53ec885cc22a8-le64.cache-3  ???
0x7fff3da8b000 - 0x7fff3da8bfff  linux-gate.so  ???

Please upgrade to PhantomJS 2.0. 1.9.x is no longer supported, and known to have many crasher bugs that are fixed in 2.0.


[Proposal] Support of LIST partition

List partition
Doris currently only supports Range partitioning, where data is usually partitioned by time columns.
However, in some scenarios, users want to partition by some enumerated values of columns, such as by city, etc.
Design
To add support for List partitioning, the following functional points need to be considered.

Support for List partition syntax in creating table statements.
Support for adding and deleting List partition syntax.
Support for List partitioning in various load operations.
Support for List partition pruning during query.

List partitioned tables do not need to consider dynamic partitioning.
Detailed design
Syntax
The main changes involved here include.

Implementation of the subclass ListPartitionDesc of the parsing class PartitionDesc
Implementation of metadata class PartitionInfo subclass ListPartitionInfo
Support for parsing and checking ListPartitionDesc in CreateTableStmt
Support for the creation of List Partition tables in Catalog class.
Metadata persistence-related changes.

The syntax is referenced from MySQL and Oracle
Single partition column
CREATE TABLE tb1 (
    k1 int, k2 varchar(128), k3 int, v1 int, v2 int
)
PARTITION BY LIST(k1)
(
    PARTITION p1 VALUES IN ("1", "3", "5"),
    PARTITION p2 VALUES IN ("2", "4", "6"),
    ...
)
...
;

Multi-partition columns
CREATE TABLE tb2 (
    k1 int, k2 varchar(128), k3 int, v1 int, v2 int
)
PARTITION BY LIST(k1, k2)
(
    PARTITION p1 VALUES IN (("1", "beijing"), ("1", "shanghai")),
    PARTITION p2 VALUES IN (("2", "beijing"), ("2", "shanghai"), ("2", "tianjin")),
    PARTITION p3 VALUES IN (("3", "beijing")),
    ...
)
...
;

NOTE: Each partition needs to ensure that the partition values are unique.
Add partition
ALTER TABLE tb1 ADD PARTITION p4 VALUES IN ("7", "8", "9");

ALTER TABLE tb2 ADD PARTITION p4 VALUES IN (("4", "tianjin"));

Load
The current load methods of Doris include Stream Load, INSERT, Routine Load, Broker Load, Hadoop Load, Spark Load.
Among them, Stream Load, INSERT, Routine Load, and Broker Load all use TabletSink class for data distribution. Our first phase supports List partition support for these load operations.
The main changes involved include:

Changes related to the Descriptors.TOlapTablePartitionParam structure in the Thrift structure TOlapTableSink
Changes related to the OlapTablePartition object in the OlapTableSink class on the BE side.

Query
The query mainly needs to implement the List Partition pruning function.
The main changes involved include:

Implementing the subclass ListPartitionPruner of PartitionPruner

Partition related
Support operations related to partitioned tables, such as recover, truncate, temporary partition, restore, replace, etc.

Nice Job~~

Please send the proposal to the mailing list too

Please send the proposal to the mailing list too

Already sent to<EMAIL_ADDRESS>


Arguments in others read as one

When attempting to have multiple arguments (in my case, --disableYarnAudit --failOnCVSS 7), they are submitted as one argument though.

Configured action:
- name: dependency-check
        uses: dependency-check/Dependency-Check_Action@main
        id: dependency-check
        with:
          project: 'project'
          path: '.'
          format: 'HTML'
          others: '--disableYarnAudit  --failOnCVSS 7'

I might be able to simplify it using an entrypoint + docker : https://docs.github.com/en/actions/creating-actions/dockerfile-support-for-github-actions#entrypoint

@javixeneize I need access to push a branch

It’s better to do a PR instead. Fork the project and then do the pull request from there

What is the best way to test a github action?

There’s a project to test the action, https://github.com/dependency-check/DependencyCheck_Test
You just need to refer to your repo when using the action

I have added a new field called failoncvss. This should work for you

name: Depcheck
uses: dependency-check/Dependency-Check_Action@failoncvss
id: Depcheck
with:
project: 'test'
path: '.'
format: 'HTML'
failoncvss: 7
others: '--disableYarnAudit'

I need to find a way to send an array in others, but by now it would allow you to do what you want
Thanks

Okay. I will probably just use my fork for now. Thank you.

Closing due to inactivity


 Why don't you try and fix the issue. What do you want for free?

@mungruez Do you really think that your friendly words motivate the busy maintainer, who doesn't have enough time to fix something for a random unfriendly guy on the internet? If I were the maintainer, I would close this issue and wouldn't fix it, just to annoy the user.

lol, dude I tried to fix the issue with live server on my mac and like i
said its a complete waste of time. I had to learn Webpack 5 and now I no
longer need live server to link/read/write files to javascript projects. I
got a good understanding of bundling and using Webpack's "dest" folder .
Drilling myself and burning to learn was the only way because of how
unhelpful the javascript community was. You are absolutely right "No one
should want anything for free"! No wonder no one fixes anything and because
I said it does not work I must fix it lol. The youtube open source
community is much better products like this made me dislike Javascript
because other programming communities are much better.
On Sun, Jun 12, 2022 at 12:23 PM Mawoka @.***> wrote:

@mungruez https://github.com/mungruez Do you really think that your
friendly words motivate the busy maintainer, who doesn't have enough time
to fix something for a random unfriendly guy on the internet? If I were the
maintainer, I would close this issue and wouldn't fix it, just to annoy the
user.
—
Reply to this email directly, view it on GitHub
https://github.com/ritwickdey/live-server-web-extension/issues/86#issuecomment-1153225032,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEBBTLS6NW4WHGSOTZ26W63VOYFJNANCNFSM5S23MFDQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

+1


Change to fixture

The test-method was quite long and had code-duplication. This is moving it to a fixture style and hopefully speeds it up as well.

Thanks, I will review it soon.


docker: no matching manifest for unknown in the manifest list entries.

Hi,
I have this error when I try ton pull the image ghost:latest and the others.
latest: Pulling from library/ghost
docker: no matching manifest for unknown in the manifest list entries.
See 'docker run --help'.
Thanks.

What platform are you on?  That sounds like a miscompiled Docker daemon.

Linux DietPi 4.4.77-rockchip-ayufan-136 arch64 GNU/Linux.
I'im using a rock64 with dietpi

Odd, I'd recommend looking into why your Docker install doesn't appear to know what platform it's on (making it unable to determine which image from the manifest lists to pull).  See https://github.com/nginxinc/docker-nginx/issues/266 for a similar issue over on nginx.
I'd suggest trying the Docker Community Forums, the Docker Community Slack, or Stack Overflow for further help debugging your Docker installation.

I have same issue. Similar platform. @SirTerrific have you been able to fix the problem?

I used an ARMv8/Ghost images and it solved the issue


Tensorflow v2 update

Hi MorvanZhou,
Your code was not compatible with tensorflow v2. Also, I've changed ArmEnv to be like the openai gym interface (ie. using box2d for action and observation space).
        self.action_space = spaces.Box(
            low=-self.u_max,
            high=self.u_max, shape=(self.action_dim,),
            dtype=np.float32)
        # node1 (l, d_rad, x, y),
        # node2 (l, d_rad, x, y)
        low = np.array([0, 0, 0, 0, 0, 100, 100])
        high = np.array([1, self.arm1l, self.arm1l, self.arm1l + self.arm2l, self.arm1l + self.arm2l, 300, 300])
        self.observation_space = spaces.Box(
            low=low,
            high=high
        )

Should I do a pull request?
Best,
Tessa

Thanks, which code have you upgraded to tf2?

The ddpg policy for the robot arm.

Oh, for that code, I have done the upgrading in this repo, https://github.com/MorvanZhou/RLarm thanks.


Access wait time from failed attempt listener?

I'd like to log the wait time until next run will be started. As we use withBackoff() this time is not a constant value. Any way this can be achieved?
RetryPolicy<Server> retryPolicy = new RetryPolicy<Server>()
    .handle(Throwable.class)
    .withBackoff(INITIAL_RETRY_DELAY_IN_SECONDS, MAX_RETRY_DELAY_IN_SECONDS, ChronoUnit.SECONDS)
    .withMaxAttempts(REGISTER_MAX_ATTEMPTS)
    .onFailedAttempt(listener -> log.warn("Registering server '{}' attempt #{} failed: '{}'. Retrying in {} seconds...",
            serverUrl,
            listener.getAttemptCount(),
            listener.getLastFailure().getMessage(),
            listener.getXXX()));

We're currently using failsafe 2.4.4.

This has come up before (#232) but I was waiting to see if there was much interest. There are some caveats though, which are described here: https://github.com/failsafe-lib/failsafe/issues/232#issuecomment-604218020. Any thoughts on those?

This has come up before (#232) but I was waiting to see if there was much interest. There are some caveats though, which are described here: #232 (comment). Any thoughts on those?

Thanks, was searching for the wrong keywords I guess. Closing in favor of your issue and already left a comment there!


Add github action for  making a release

This file contains jobs to run when making a tag.
When a tag is made that matches "v.*", it will trigger this workflow to
do:

checkout the source
set the 'release' env. variable (stripping out 'refs/heads/v' character in tag name)
create a release using create-release action
create the tarball with source code for the release using
create-tarball.sh

Deferring this for later


Rebuild to pull in latest GSL

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Thanks for opening this PR @kdm9 - I'm not sure how to proceed from here? I'm happy to open a different PR if that's easier than debugging what's happening here?

@jeromekelleher good question. AFAICT, the only build failures are on OSX, and are actually "deprecation brownouts", i.e. they forced them to fail as those CI configs will soon be removed.
The original problem is that the C module is linked to libgsl.so.25 (gsl version 2.6) but the version requirement is for version 2.7 and therefore only libgsl.so.26 is installed. I'm hoping a rebuild triggered by bumping the version number will fix this, and has for other packages where I've found this issue. I've hit this same problem in quite a few different packages now, so maybe @conda-forge/gsl have ideas on how to prevent this more thoroughly than just rebuilding with every new gsl version.
If you were to just merge this, I think what will happen is that we'll get new packages for windows & linux, but mac will still have the old ones as the CI builds aren't working. I don't know if any folks from the conda-forge org can comment on the osx CI issue (e.g. @conda-forge/help-osx-arm64).

Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)

Are you sure this was done?

Everything is building now, so merging.


emacs(eglot): internal error when registering workspace/didChangeWatchedFiles capability

It's not clear to me if this is an emacs issue or a Next LS issue yet

related https://github.com/joaotavora/eglot/issues/1258


findlib search path

Adding a new directive "SEARCH" to .merlin that sets the findlib search path for the project, overriding any OCAMLPATH variable

Ok, I misunderstood your request.
This looks fine overall.
SEARCH is maybe too general. Would you mind renaming to FINDLIB_SEARCH or FINDLIB_PATH (or whatever seems appropriate for FINDLIB)?

Sometimes a single PR explains more than a thousand words...
The environment variable is OCAMLPATH. Either that or something close, like FINDLIB_PATH.

Squashed and renamed SEARCH to FINDLIB_PATH. Thanks for the PR.


record metrics per host

todos are blocking on metric tagging (possibly: https://github.com/palantir/tritium/pull/39)