gdcm: 3.0.22 -> 3.0.23

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/malaterre/GDCM/releases.
meta.description for gdcm is: The grassroots cross-platform DICOM implementation
meta.homepage for gdcm is: https://gdcm.sourceforge.net/
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.0.23 with grep in /nix/store/zv40cm0zn8q3jy9z6gpzv9lk35rpb47a-gdcm-3.0.23
found 3.0.23 in filename of file in /nix/store/zv40cm0zn8q3jy9z6gpzv9lk35rpb47a-gdcm-3.0.23

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

29 total rebuild path(s)

29 package rebuild(s)

First fifty rebuilds by attrpath
ants
c3d
elastix
ezminc
gdcm
intensity-normalization
itk
itk_5
itk_5_2
mirtk
mrtrix
octavePackages.dicom
python310Packages.dicom2nifti
python310Packages.gdcm
python310Packages.intensity-normalization
python310Packages.pydicom-seg
python310Packages.pymedio
python310Packages.pyradiomics
python310Packages.simpleitk
python310Packages.torchio
python311Packages.dicom2nifti
python311Packages.gdcm
python311Packages.intensity-normalization
python311Packages.pydicom-seg
python311Packages.pymedio
python311Packages.pyradiomics
python311Packages.simpleitk
python311Packages.torchio
simpleitk

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/zv40cm0zn8q3jy9z6gpzv9lk35rpb47a-gdcm-3.0.23 \
  --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 gdcm https://github.com/r-ryantm/nixpkgs/archive/eac6fcaf257195f8e493ae7336fd15ade81397c9.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/eac6fcaf257195f8e493ae7336fd15ade81397c9#gdcm

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zv40cm0zn8q3jy9z6gpzv9lk35rpb47a-gdcm-3.0.23
ls -la /nix/store/zv40cm0zn8q3jy9z6gpzv9lk35rpb47a-gdcm-3.0.23/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.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @tfmoraes for testing.

@ofborg build gdcm gdcm.passthru.tests

@ofborg eval


Customized Landing Page Doesn't Show Up In Docker Deployment

Gitea Version
1.15.0+dev-593-gafc2fffe2
Git Version
2.30.1 (Apple Git-130)
Operating System
MacOS
How are you running Gitea?
With one customization, we built Gitea ourselves based on the source code from Gitea. For the native deployment, we follow the README documentation.

TAGS="bindata" make build
./gitea web

See the description below for more details.
Database
PostgreSQL
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Description
We make changes to the landing page. All code changes are under the custom directory. Running it natively, the customized landing page shows up properly.
We make a docker image with the command "docker build -t abc/gitea ." The Dockerfile comes with the source code without any changes.
We run the command, "docker-compose -f postgresql.yml up", to bring up a Gitea docker container. The content of the postgresql.yml file is copied from https://docs.gitea.io/en-us/install-with-docker/#postgresql-database and we replace "image: gitea/gitea:1.15.5" with "image: abc/gitea:latest". The version # is the same as what we see in the native deployment starting with "a77c1a".
With the same version number, the customized landing page shows up in the native deployment, but not in the Docker deployment.
Update based on a comment from a Gitea team number:
The landing page customization is done based on a guide from the Gitea team. The directory structure is the following: custom->conf, custom->options->locale, custom->templates.
The Gitea version in this ticket is updated with extended information.
It was stated where our docker compose file comes from in the original ticket. Based on the URL of the Gitea online document, it is clear that we use the rootful one as what you call it.
Screenshots
No response

custom data is not part of Gitea release, it shouldn't be copied into the docker image for a common release.
Users can always use a volume to map their own custom data into docker containers.
As long as the issue has a solution and it is not a bug, we can close this issue.

In our case, there is not any data involved for customization, but application files. The current Dockerfile is a trap for people who need to do such customization given lacking proper documentation on the subject. It should either leave all customization stuff out or have them properly.


Deploying rules in AWS

Hi,
INFO Helm client version: 3.5.4
INFO Kubernetes client version: v1.18.19
INFO Kubernetes server version: v1.18.16-eks-7737de
We ran into this error with webhook while deploying monitoring on an EKS cluster.  The error occurred when apply this rule: rules-sas-launcher-job.yaml
INFO Adding Prometheus recording rules...
Error from server (InternalError): error when creating "monitoring/rules/viya/rules-sas-launcher-job.yaml": Internal error occurred: failed calling webhook "prometheusrulemutate.monitoring.coreos.com": Post https://v4m-operator.monitoring.svc:443/admission-prometheusrules/mutate?timeout=10s: context deadline exceeded
I modified the deploy_monitoring_cluster.sh and commented out the this section and the monitoring installed correctly with exception of applying the rules.
    # Rules
    log_info "Adding Prometheus recording rules..."
    for f in monitoring/rules/viya/rules-*.yaml; do
      kubectl apply -n $MON_NS -f $f
    done

I ran into a similar issue with webhooks in AWS but it didn't seem to like any modifications I made to (  --set webhook.hostNetwork=true,webhook.securePort=) during the helm install of prometheus.  Those 2 settings have had to set in another helm install with a webhook issue and it fixed this issue in the past.   Also, checked to see if there were any lingering CRDs or validatingwebhookconfigurations or MutatingWebhookConfiguration.
Thanks in advance

@devopsasadm Thank you for reporting this.  Given the age of this issue, I'm going to close it as "stale".  We (now) regularly deploy onto both EKS and AWS clusters and have not seen this problem.  Please open a new issue if you are still seeing this issue.


Bug: When comparing a weapon it shows the unlevelled variant

Colourful:

Dull:

Just noticed it also shows the unlevelled state on the main Overview page:

Can't seem to replicate...

Doesnt seem to be all weapons now that I look.
Amos, Aqua, Sac Bow for example. But other bows seem to be fine?

WeaponCardNano, WeaponCardPico, WeaponFullCard all use weaponSheet.img. Need to copy from WeaponCard and determine the image based on the ascension (img vs imgAwaken)

could prob have a general icon(asc:number) function


Add new doc section for production guides.

This will be progressively added to before is ready for merging.


Compile library example

I'll change the acceptance test to use another app than Tinker. We already have too many versions of Tinker floating around and I'd like to avoid scattering some more.


DM-39400: Separate Gafaelfawr models

The change to include the Gafaelfawr token in the UserInfo model meant that we were leaking the token to API callers asking for the lab status. Solve this problem properly by separating the Gafaelfawr model from the UserInfo model that's part of the lab API, and by creating two Gafaelfawr models, one with a token and one without.
Fix up the typing to expect the model needed at each point in the lab controller code. While doing this, remove the now-unnecessary separate token argument to many of the lab construction methods, allowing additional simplification.
Take this opportunity to clean up the lab status API a bit, since it was getting cluttered by collapsing multiple different types of data into one flat object. Move the user metadata into a user key, and return only the user data of interest to the status of the lab by omitting the user's full quota inforamtion. Instead, add the quota enforced on the user's namespace (as distinct from the resource restrictions on the lab) to the top-level UserInfo model.

Incidentally, "quantity" is what Kubernetes officially seems to call the thing we've been calling a "quantum," so I switched to the Kubernetes terminology.


Add optional restart flag to Application /update API

Summary
Fixes #277
Blocked by https://github.com/epinio/epinio/issues/2363

Our instance of epinio is running from epinio/epinio is 7984eb56, that's before the merge that brought in the param 88c3b9 / https://github.com/epinio/epinio/pull/2457.
Can you update our instance (via the make process) and give this a test?

Our instance of epinio is running epinio/epinio 7984eb56, that's before the merge that brought in the param 88c3b9 / epinio/epinio#2457.
Can you update our instance (via the make process) and give this a test?

Sure, Sorry I forgot to update our dev instance. Will do in a bit.
I tested it on my own epinio instance, https://epinio.<IP_ADDRESS>.nip.io/, which is aligned with main branch


[UBS courier] Input field is not disabled by default  in the 'Ні' radio button when using the 'tab' button instead mouse

Environment: Windows10 X64, Opera 78.0.4093.147.
Reproducible: always.
Build found: 08.09.2021
Preconditions

Log into GreenCity https://ita-social-projects.github.io/GreenCityClient/#/ as an existing user.
User goes to the next sections via 'tab' button instead mouse

Steps to reproduce

Go to 'UBS кур'єр' tab
Click on 'Замовити кур'єра' button
Scroll to 'Еко магазин' section
Pay attention to the two radio buttons “Так” and “Ні”
Choose 'Ні' radio button and enter any numbers into input field

Actual result
By default the system displayed “Ні” answer and the input field for the shop order number is enabled in the 'Еко магазин'section on the 'Деталі замовлення' tab.
Expected result
By default the system displayed “Ні” answer and the input field for the shop order number is disabled in the 'Еко магазин'section on the 'Деталі замовлення' tab.
User story and test case links
User stories : #2196 , #2379
Test case GC-2050

Done!


[feat] Build for the web

Describe the problem
I know that Yew already exists, but implementing a way to build for the web in tauri would be a really useful feature
Describe the solution you'd like
I don't need this feature urgently, but it would be nice if it could at least be added to the Tauri roadmap by an admin to be implemented at some point. I just want a simple way to build a single page app (or even multi page at some point). I think it'd be a great idea because then the web app can leverage the power of rust whilst still being easy to write and having nice gui.
Alternatives considered
Of course, there's yew, but that'd mean you'd have to create your app again from the ground up.
Additional context
No response

I am not sure what you mean tbh so would need more clarification. Tauri uses web technology to present the UI inside a webview on Desktop, you can still reuse your HTML/CSS/JS project and run it inside the browser (you still need to guard your usage of tauri APIs though so it doesn't error in the browser)

Thanks for the clear up, I understand the motivation and while It is a valid case I don't think we have enough resources to spend on this at the moment so I will keep this issue open in case we get some time for it or if someone else wants to pick it up.

I know just how incredibly hard of a feature it would be to implement, but I was just wondering if it could be added to the tauri roadmap as a very low priority feature that could be implemented at some point if someone feels like doing it.

@Jamzy01 I have a working project running both on Desktop and Web.
Here: https://github.com/Tnze/ffxiv-best-craft
So basically I have a lib crate for my rust code. And a tauri binding for desktop and wasm binding for web application.
Having two head-write binding is a bit annoying. But at least it works.

@Jamzy01 I have a working project running both on Desktop and Web. Here: https://github.com/Tnze/ffxiv-best-craft
So basically I have a lib crate for my rust code. And a tauri binding for desktop and wasm binding for web application.
Having two head-writing binding is a bit annoying. But at least it works.

Your game looks really great! It's a proof of concept that something like this will work just fine, but it'd just be so much nicer if it was built into Tauri.

It'd just be so much nicer if it was built into Tauri.

I think we can build a new wasm binding tools that easy to used just like Tauri's #[tauri::command]. Then we can write a crate that can switch between compiled to a WASM binary or a Tauri plugin.

Just my two cents: I have talked with many people that are looking to switch to a different app development platform, and who were curious about my thoughts, since I have used Tauri on numerous occasions. I told them that Tauri was great for building entirely self-contained web-apps in an app wrapper (e.g. effectively no rust backend), and great for dedicated desktop apps that rely on a rust backend. I have used it previously for both, and I can attest to that. However, when I tell them that it is not great for web+desktop with a mostly shared codebase - precisely because of the fact that it ends up being completely on the developer to architect those switches and builds - it turns out that it is a huge red flag for people that turns them away from the project.
As I have gotten more familiar with Rust, it feels odd that there aren't feature flags/configuration conditionals that allow users to define both web implementations and native ones for when the available libraries differ, and then support building the app in either web or desktop/mobile through a unified build. I understand that the tauri devs are concerned about the lack of support for some desktop functionality in wasm-based builds, but it seems like there is a lot of other configuration that ends up being needed to figure out a web version that ends up being put on the app developer, but which actually could be handled easily in the build process with sufficient build-time conditionals (e.g. wasm build, function linking, worker execution, etc).


(status: 401 Unauthorized): authentication failed

Fresh Install of unpoller
I checked it thru three times, verified passwords, and still get  the error,
Controller 1 of 1 Auth or Connection Error, retrying: unifi controller: (user: unifipoller): http://X.X.X.X/api/login (status: 401 Unauthorized): authentication failed
I verified the password several times / Copy and pasted.
Move to the old interface and do not have the full settings as before.
UniFi OS  3.2.12.
Network  8.0.28.
User is  View Only
OS Setting View Only
Please help me get this back and running again.

These should be https and verify the port is either 443 or 8443

Im running a UDM Pro it states not to use 443 or 8443. I changed to https and get
metric fetch for InfluxDB failed: re-authenticating to https://x.x.x.x443: unifi controller: (user: unifipoller): https://<IP_ADDRESS>:443/api/auth/login (status: 403 Forbidden): authentication failed: error initializing inputs
if I use 8443 I get:
[ERROR] metric fetch for InfluxDB failed: re-authenticating to https://<IP_ADDRESS>:8443: unifi controller: (user: unifipoller): https://<IP_ADDRESS>:8443/api/login (status: 404 ): authentication failed: error initializing inputs

https://<IP_ADDRESS>/proxy/networks/api/auth/login. allows me to log in with the unifipoller id and password to the web UI.

This is a local access user correct? It appears 443 is the correct port here for you which is what I expected.

Correct local access only

This should work, I'm running the same versions, this implies one of the follow:

Check the config - it's possible special characters are not being handled here correctly depending on your configuration file format choice
The credentials are not correct for this user

Ok so I have setup again for the fifth time I still get the same message. It will not log in
When it states auth token - this is the password for the unifipoller account on the UDM Pro correct?
| auth token for account created earlier. e.g. unifipoller
Looks like I really need help getting this going again
I did not mention I al running this on a Synology 918+

username password combo - you should probably also specify how you are trying to configure this when asking for help

Configuring with the Synology install process.

more to the point: share your config file (redact the passwords) share the exact commands you're using the start and the full log

I have to run a config file as well as the directions for the synology setup?

share your config file
and the exact commands

I used this process https://unpoller.com/docs/install/synology/  I have No Config file with this process

you have to have a config file to connect to the right device

Sorry for the confusion on my part, The Synology process does not mention a config file it appears to get that from the config of the container. Is the config your talking about the up config and where should I locate the file once created?
IE I should follow this first : Installation
Unpoller's Docker container can be configured in two ways:
Using environment variables.
Using a configuration file.
And then config my Synology?

it's a container so yeah you need to supply it some config

The config is coming from the container setup from what I can tell. Under the environment settings
it asks for UP_UNIFI_DEFAULT_URL and the UP_UNIFI_DEFAULT_AUTH_TOKEN which are provided.

Please share exactly what you’re doing - I’m afraid I’m going to need to close this otherwise

On the UDM User unpoller created password set - Limited admin
Prepared Synology & Docker
Run docker & configure network
Created new network:
Named Grafana_Net
Enable IPv4
Get network configuration automatically is selected
Click add
Prepare mapped volumes
/docker/altuha/grafana and /dockeraltuha/influxdb
Download needed images from the registry
unpoller for ghcr.io/unpoller/unpoller:latest https://github.com/unpoller/unpoller/pkgs/container/unpoller
grafana for grafana/grafana:latest https://hub.docker.com/r/grafana/grafana/
influxdb for influxdb:1.8 https://hub.docker.com/_/influxdb/
Create influxdb container
In Image, select influxdb: and click launch
container named influxdb1
Click Advanced Settings
On volume tab add the following:
The /docker/influxdb folder from above to mount path /var/lib/influxdb -  read/write
On the Network tab
Added network Grafana_Net
Removed the default bridge
Ensured that the use the same network as the docker host was unchecked
local port from Auto to 3456 - container port as 8086 and type as TCP
environment tab added the following vars
INFLUXDB_DATA_DIR | /var/lib/influxdb/data
INFLUXDB_DATA_WAL_DIR | /var/lib/influxdb/wal
INFLUXDB_DATA_META_DIR | /var/lib/influxdb/meta
Finalized container and:
Click APPLY
Click NEXT
Click APPLY
SSHed into  Synology
Ran the command sudo docker exec -it influxdb1 bash
followed InfluxDB Post Setup instructions ](https://unpoller.com/docs/dependencies/influxdb#post-setup).
Create unpoller container
In Image select ghcr.io/unpoller/unpoller:latest and click launch
Container name unpoller1
Click Advanced Settings
On the network tab:
Add network Grafana_Net
Removed the default bridge
Ensured that the use the same network as docker host was unchecked
On the Environment tab, add the following vars:
UP_INFLUXDB_URL | http://influxdb1:8086
UP_UNIFI_DEFAULT_URL | https://<IP_ADDRESS>
UP_UNIFI_DEFAULT_AUTH_TOKEN | unpoller UDM Password
UP_UNIFI_DEFAULT_ORG | unpoller
UP_UNIFI_DEFAULT_BUCKET | unpoller
Finalized the container by:
Click APPLY
Click NEXT
Click APPLY
checked for data and this is where I cant pull data

lol you just copy and pasted the docs from the website.

The error message at the top of this thread indicates the wrong auth info is provided. ie. bad username or password. Seems like you've tried lots of things related to that and I now suspect your controller is just in a bad state. Might want to consider factory resetting it and starting over.

Well, I bailed on the Synology direction, used ssh for the installation, and could configure it without issue. The config is then shown in the Synology docker. Seems the Synology direction is missing a few steps and ENV variables. In short all is good now


Adding the UI design of error 404 pages.

I can contribute by providing a UI design of error 404 pages in both Web and App mode.

Can i work on this issue ?

Sure @Pushkar03 work on this.

Adding Error 404 Pages UI design in both Dark & Light mode
Dark Mode

Light Mode

This looks really amazing. Add them @blyncnov

Hey I have made them

This is my contribution not the other's one

@Rajdip019 What do you mean add them ?

This is solved so closing this isssue.


test_qt_scrollbar fails with display settings over 150%

🐛 Bug Report
napari\_qt\widgets\_tests\test_qt_scrollbar.py fails when System>Display>Scale is set to 150% or higher (Windows).
💡 Steps to Reproduce

Set System>Display>Scale to 150%
run pytest napari\_qt\widgets\_tests\test_qt_scrollbar.py

💡 Expected Behavior
Test outcomes to be not dependent on the Display Settings on my machine.
🌎 Environment
napari: 0.1.dev3654+g5721704
Platform: Windows-10-10.0.22631-SP0
Python: 3.10.15 | packaged by conda-forge | (main, Oct 16 2024, 01:15:49) [MSC v.1941 64 bit (AMD64)]
Qt: 5.15.2
PyQt5: 5.15.11
NumPy: 2.0.2
SciPy: 1.14.1
Dask: 2024.11.2
VisPy: 0.14.3
magicgui: 0.9.1
superqt: 0.6.7
in-n-out: 0.2.1
app-model: 0.3.1
psygnal: 0.11.1
npe2: 0.7.7
pydantic: 2.10.2
OpenGL:

GL version:  4.6.0 - Build <IP_ADDRESS>22
MAX_TEXTURE_SIZE: 16384
GL_MAX_3D_TEXTURE_SIZE: 2048

Screens:

screen 1: resolution 1920x1080, scale 1.0

Optional:

numba: 0.60.0
triangle not installed
napari-plugin-manager: 0.1.3

Settings path:

C:\Users\prins\AppData\Local\napari\napari-env_704272392b11459f80cdac6a05820f790f73194c\settings.yaml
Plugins:
napari: 0.1.dev3654+g5721704 (81 contributions)
napari-console: 0.1.1 (0 contributions)
napari-svg: 0.2.0 (2 contributions)

💡 Additional Context
No response

Thanks for reporting!
I don't think we have many devs using Windows and GUI things like that are hard to test on CI.
Could you post the full test failure output? maybe it would help us debug.


react-native-root-siblings doesn't work

With react-native 0.49 react-native-root-siblings no longer works. Is there an easy way to remove the dependency?

Plz upgrade to 2.0.0


Update editions-and-components-of-sql-server-version-15.md

Making changes for Standard Edition for Extensible key management

@amitmsft : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


adding simple support for hipchat

Thanks for this, can you add a unittest?

I am not sure that I know what to test? I guess I could test the message if we want to make it more complicated than just the description.

I'd suggest testing that the expected http endpoint is hit.

I could write that test, but that test is kind of silly IMHO. If I copy and paste the URL from the code that I wrote and it is wrong it will be wrong in both the test and the code. Then the test will pass but it will still not work. Really we would need to test that the interaction between hipchat and alertmanager worked correctly with an integration test, but there is not really a way that I know to just spin up a fake hipchat server.

okay I think that I took most of your comments except for the unit tests into consideration. I feel like I could break out the message into a unit test if we really wanted to, but the only thing that I would know to test is the message. Which all of the golang maps should just default to "" anyhow so I am not sure if it would be worth it.

@a86c6f7964 I wouldn't demand it here, but the thing that'd make sense to test in this situation would be whether the correct JSON and headers are sent. That can be done by setting the hipchat URL to a custom one (which would point to an instance of http://golang.org/pkg/net/http/httptest/#Server). However, since we currently don't do that for the other mechanisms, I think I wouldn't require that for adding this for now.

Could you add the same README.md addition as in https://github.com/prometheus/alertmanager/pull/40/files?

:+1: otherwise, thanks!

do you want me to squash any of this? or would you rather just leave all of the commits.

Yep, squash it please (after last comment) :) In general, commit messages should in the end be self-sufficient. For example, "adding 5 second timeout" is ambiguous without the context of a PR, so "Add 5 second timeout for Hipchat notifications" is better. So something like "Add simple support for HipChat notifications" would be great for the squashed overall commit.

okay squashed

Thanks!


Support for fine grained personal access tokens

Hey! First off thanks for this incredible project!
Is your feature request related to a problem? Please describe.
For security purposes it would be very helpful to be able to use GitHub's new fine grained access tokens but this does not work as the GraphQL API does not support them yet.
Describe the solution you'd like
How deeply integrated is usage of the GraphQL API? Would it be possible / feasible to use the REST API instead?
I'd be happy to work on a PR for this myself if it's deemed viable.
Describe alternatives you've considered
Waiting for GitHub to add support in the GraphQL API itself.
Additional context
It does seem like fine grained token support is planned for Q1 2023 so hopefully this will be a non-issue soon but it would be great to have this work in the meantime.

We switched to graphql queries to reduce the sheer number of API calls necessary to grab all the data that we need.
For example, we need to grab commits to branch x with associated pull requests with the files touched by that pull request. We do that in a single paginated graphql request where the REST equivalent is a paginated listCommits call, n getPullRequest calls, n getPullRequestFiles calls. Quota-wise this is similar, but actual API calls turns out to be a lot.
We are considering an SCM abstraction to support other methods of acquiring this data (perhaps Gitlab, or even a version that uses a local git clone), but this is significant work that needs to be prioritized.
An alternative is to use GitHub app credentials (OAuth public/private key). We run our own app instance that uses probot and app credentials to manage releases. Note that this is not an official Google product, but it's something we run for ourselves.


feat(explorer): remove dev command from build

First attempt to compile out next dev path for @latticexyz/explorer build but so far didn't succeed, will continue experimenting with it.

Close in favor of https://github.com/latticexyz/mud/pull/3108


too many values to unpack (expected 2)

Updated from latest changes and now get:
$ python test_pasd.py
C:\PASD\pipelines\pipeline_pasd.py:41: FutureWarning: Importing `DiffusionPipeline` or `ImagePipelineOutput` from diffusers.pipeline_utils is deprecated. Please import from diffusers.pipelines.pipeline_utils instead.
  from diffusers.pipeline_utils import DiffusionPipeline
C:\Python310\lib\site-packages\torchvision\transforms\functional_tensor.py:5: UserWarning: The torchvision.transforms.functional_tensor module is deprecated in 0.15 and will be **removed in 0.17**. Please don't rely on it. You probably just need to use APIs in torchvision.transforms.functional or in torchvision.transforms.v2.functional.
  warnings.warn(
clean, high-resolution, 8k
  0%|          | 0/20 [00:00<?, ?it/s]
too many values to unpack (expected 2)

My bad. Fixed now.


⚠ Bofrost.at has degraded performance

In 159c7b0, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 890 ms

Resolved: Bofrost.at performance has improved in 68718e9.


Rename project from orchestra to orquesta

The project is renamed from orchestra to orquesta to coincide with our marketing campaign.

Codecov Report

Merging #77 into master will not change coverage.
The diff coverage is 98.91%.

@@           Coverage Diff           @@
##           master      #77   +/-   ##
=======================================
  Coverage   94.28%   94.28%
=======================================
  Files          36       36
  Lines        2084     2084
  Branches      392      392
=======================================
  Hits         1965     1965
  Misses         71       71
  Partials       48       48

Impacted Files
Coverage Δ

orquesta/exceptions.py
98.14% <ø> (ø)

orquesta/utils/context.py
100% <ø> (ø)

orquesta/specs/types.py
100% <ø> (ø)

orquesta/utils/dictionary.py
86.2% <ø> (ø)

orquesta/expressions/functions/base.py
100% <ø> (ø)

orquesta/utils/date.py
89.65% <ø> (ø)

orquesta/utils/expression.py
100% <ø> (ø)

orquesta/specs/loader.py
100% <ø> (ø)

orquesta/composers/mistral.py
93.81% <100%> (ø)

orquesta/specs/mock/__init__.py
100% <100%> (ø)

... and 26 more

Continue to review full report at Codecov.

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


[Improvement] Scheduling using cost function.

This post is about scheduling service on hosts based on the current available configuratoin only.
Thinks Rancher take into account:

Number of containers (this is a simple utilization metric)
Strict scheduling rules (must / must not)
Preferred scheduling rules (should / should not).

I'd like to talk about the way Rancher chooses what host a new service should be deployed to.
First consider the set of all host H. From this set all hosts that are explicitly forbidden can be removed using the strict scheduling rules. This leaves us with a smaller set H'.
Since all strict rules have been taken into account, we can conclude a solution exists if H' is not empty.
This is the easy part, now come the part where Rancher has to decide how to divide the containers across the available hosts. Currently it seems Rancher only does this when initially launching a service and it is unclear when these conditions are re-evaluated.
Consider the galera cluster from the gallery, it comes with 3 nodes which, for obvious reasons, prefer to be scheduled on different hosts. When launching the cluster on a Rancher setup with 3 nodes all is fine.
If 2 hosts go down Rancher has no choice but to move all containers to the 1 remaining host.
Now when the hosts come back up (for simplicity lets assume it has been rebooted so the galera containers are not running anymore).
Now we're stuck in a situation where Rancher will not allow us to re-balance the galera cluster to make use of all hosts.

Trying to delete a container (and its sidekicks) from the host with all container results in the container being recreated on the same host.
Increasing the scale uses the proper hosts, but decreasing it afterwards then seems to remove the most recently created container.

All of these issues could be simply resolved if Rancher uses a cost function to compare different solution.
A simple cost function would be counting the number of broken non-strict rules. When a container needs to be removed there's only very few choices and it would be easy to calculate the best choice, same for adding a new container.
The only issue is initial scheduling where dividing n containers over m nodes gives us a really large search set, still improving this only for the rescheduling case would already be great.
tldr; In case Rancher needs to remove 1 container, could it do it intelligently instead of just removing the most recently created?

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


@github/jtml availability on Github Package

It seems that @github/jtml is published on npm but @github/catalyst is published on github packages.
Would be eassier to have both on Github Packages so the npm configation for @github registry is straight forward.
Thanks

Or both on npm, works as well 😄

Thanks for pointing this out! I'll work to get jtml released as OSS, and look at how we can publish to both GPR and the npm registry.

Thanks!
On Tue, Nov 24, 2020, 15:29 Keith Cirkel<EMAIL_ADDRESS>wrote:

Thanks for pointing this out! I'll work to get jtml released as OSS, and
look at how we can publish to both GPR and the npm registry.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/github/catalyst/issues/83#issuecomment-733009880, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABIB4DGBBCI5PJJMA4ESBVLSRO7N3ANCNFSM4UA55P7Q
.

https://github.com/github/catalyst/pull/84 has pushed @github/catalyst to npm. Releasing jtml will take a little longer.

@github/jtml is now open source!
https://github.com/github/jtml

@github/jtml is now open source!
https://github.com/github/jtml


Training is slow enough

Thanks for code sharing. union_area = MultiPoint(union_poly).convex_hull.area ran extremely slowly when I had tried your code on icdar-2015 dataset, one iteration cost more than 20 mins, it's inconceivable. Can u explain why? Thank u again.

@qjadud1994

It didn’t take that long time when I trained.
I think you should check ‘shapely’ library.

@qjadud1994 My Version: 1.6.4.post2, may you tell me which version you use in? Thank you so much

@qjadud1994 In fact, the pytorch version can't work, I print some variables of non_max_suppression_poly,l such as
iter 0 (epoch 0) || loss: 1309.4976 || l loc_loss: 0.1840 || l cls_loss: 1309.3135 (Time : 2.5)
Get 687960 boxes
1 th boxes
2 th boxes
3 th boxes

the nms algorithm seems ran slowly extremely, each iteration for 687960 boxes cost several minutes, looking for your reply

Did you use the ImageNet pre-trained weights?
During training, NMS is just to visualize the results of valid images. Modify to visualize after number epoch.
Use a high threshold value.

@qjadud1994 In fact, the pytorch version can't work, I print some variables of non_max_suppression_poly,l such as
iter 0 (epoch 0) || loss: 1309.4976 || l loc_loss: 0.1840 || l cls_loss: 1309.3135 (Time : 2.5)
Get 687960 boxes
1 th boxes
2 th boxes
3 th boxes

the nms algorithm seems ran slowly extremely, each iteration for 687960 boxes cost several minutes, looking for your reply

Hi, have you solved the problem? I was stumped by the same question that my program jamed on the "non_max_suppression_poly(quad_boxes, score, self.nms_thresh) --> shapely.Ploygon(box1).convex_hull".
I have try to changed the version of Shapely while i do not know which version is @qjadud1994  used.  By the way, do you know where to get the 'retinanet_se50' pre-trained model ?
Thank you anyway,  I look forward to your reply.

@ qjadud1994实际上，pytorch版本无法正常工作，我打印了一些non_max_suppression_poly诸如，l之类的变量
iter 0 (epoch 0) || loss: 1309.4976 || l loc_loss: 0.1840 || l cls_loss: 1309.3135 (Time : 2.5)
Get 687960 boxes
1 th boxes
2 th boxes
3 th boxes

在nms algorithm似乎跑慢极了，每次迭代687960箱要花好几分钟，期待您的回复

嗨，您解决了这个问题吗？我的程序卡在“ non_max_suppression_poly（quad_boxes，score，self.nms_thresh）-> shapely.Ploygon（box1）.convex_hull”这个问题上，使我感到困惑。
我不知道@ qjadud1994 使用哪个版本，但是尝试更改Shapely的版本。顺便说一句，您知道从哪里获得“ retinanet_se50”预训练模型吗？
无论如何，谢谢您，我期待着您的回复。

Hello, I also have a very slow running problem. How do you solve your problem?

@qjadud1994 In fact, the pytorch version can't work, I print some variables of non_max_suppression_poly,l such as
iter 0 (epoch 0) || loss: 1309.4976 || l loc_loss: 0.1840 || l cls_loss: 1309.3135 (Time : 2.5)
Get 687960 boxes
1 th boxes
2 th boxes
3 th boxes

the nms algorithm seems ran slowly extremely, each iteration for 687960 boxes cost several minutes, looking for your reply

Hi, have you solved the problem? I was stumped by the same question that my program jamed on the "non_max_suppression_poly(quad_boxes, score, self.nms_thresh) --> shapely.Ploygon(box1).convex_hull".
I have try to changed the version of Shapely while i do not know which version is @qjadud1994 used. By the way, do you know where to get the 'retinanet_se50' pre-trained model ?
Thank you anyway, I look forward to your reply.

Hello, I also have a very slow running problem. How do you solve your problem?

Try to use pyclipper lib with cython, rewrite nms and overlaps module, it will be fast enough.


19 Dec 2024: NOAA-21-derived DEA Hotspots are now available

Tech alert

Berna verbally approved.


feature request: preview window

Did you check existing requests?

[X] I have searched the existing issues

Describe the feature
I'd like to have a preview window like nvim-bqf. And I'd like to easily show/hide it.
Provide background
I tried using quicker and nvim-bqf together (so I could have preview), but ran into issues when editing the quickfix window. So my preference now is to use quicker only.
I know we can see context, but it's not quite the same. I would prefer context sometimes, preview sometimes, and neither sometimes.
What is the significance of this feature?
nice to have
Additional details
No response

Can you explain more what the issues were when using quicker with bqf? If it's possible I'd prefer that the two just play nice together.


Not working

Challenge Bonfire: Check for Palindromes has an issue.
User Agent is: Mozilla/5.0 (Linux; Android 4.4.2; LG-D321 Build/KOT49I.D32110d) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.133 Mobile Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

var palindrome = function(str) { str = str.replace(/[\.,-\/#!$%\^&\*;:{}=\-_`~()@\+\?><\[\]\+]/g, '').toLowerCase(); return str === str.split("").reverse().join(""); }
palindrome("eye");

Everything checks out beside (race car) and 2 others. At first i thought it was an issue with spaces and used /\s/g in replace(), but after pulling my hair out I literally used the answer (the one not using recursion) from Github and its not working

Aswer i input from https://github.com/FreeCodeCamp/FreeCodeCamp/wiki/Bonfire-Check-for-Palindromes
function palindrome(str) {
var normalizedStr = str.replace(/[\W_]/g, '').toLowerCase();
var reverseStr = normalizedStr.split('').reverse().join('');
return normalizedStr === reverseStr;
}

Well answer from Github works. Copying error on my part. Don't understand the error in mine though. Guess I'll have to trudge through it more.

The problem is, indeed, that you are not removing spaces.  Simply adding a space to your character class causes it to pass all tests.


kn workflow quarkus deploy command does not print the app URL to console

kn workflow quarkus deploy command does not print the app URL to console log.
The only way how to get URL is to get it from deployed services details with the command kn service list ${SERVICE_NAME}.
If you used SonataFlow plugin, there is no url printed to console log. You have to get it from deployed services details. For example kn service list ${SERVICE_NAME}.

This would be a nice enhancement in the cli.


Errors in numpy-cupy comparison tests are ignored if accept_error=True by default

cupy.testing has decorators for comparing results from numpy and cupy functions such as numpy_cupy_array_equal. In these decorators, accept_error=True by default, so even if test code has typo or access to undefined names, they would pass. Such decorators are used everywhere without specifying accept_error=False: https://github.com/pfnet/chainer/search?utf8=✓&q=numpy_cupy_array_equal&type=Code
For example, https://github.com/pfnet/chainer/pull/1404 has typo in test code, calling xp.fill_diag instead of xp.fill_diagonal, but the tests pass. I suppose errors should not be ignored by default. It would be better to have users to specify which type of errors should be accepted.

It is a good suggestion. How about making default value False, or adding an argument specifying acceptable error type?


Missmatch with npmjs.com

The npm link on graphql.org leads to the graphql-server npm page which references github.com/apollostack/apollo-server as repository which den forwards to github.com/apollographql/graphql-server.
The npm page further uses a readme that seems to be deprecated, saying that one should run npm install apollo-server to install and use some code syntax if I'm not mistaken.
This problem only became apparent when npm complained because of a peer dependency missmatch, leading to #291 and #243 explaining that this was deprecated and npm install graphql-server-<variant> was the correct syntax as also noted in the readme of this repository.
All in all the conflicting and deprecated information is really confusing when starting using this lib so I think the information should be updated accordingly.

Thanks for bringing this to our attention, I'm fixing it right now.
@DxCx it also looks like the README.md files on npm for each package are extremely minimal and just link to the docs. I think we should change that.

@helfer
each package in packages can contain it's own README.md,
if you will remember when we spoke about splitting to variants you said that you will update the READMEs after we split..

Haha, I don't remember that, but it sounds like something I would say. Since I don't have a lot of time right now, I hope we can split up the work among a few people. Do you remember who the main authors are for the various packages?

nope, we can probably dig it from git log..
seems like:
koa - @HriBB
hapi - @nnance
express - @nnance
lambda has a readme as far as i remember..

ok, I think none of these people have made any commits recently. Let's just create an issue and tag it with "help wanted"!

#373.


Chests not updating texture from unopened to opened in single player

Lootr version: <IP_ADDRESS>
Minecraft version: 1.19.2
Modpack(s): All of Fabric 6
In single player, chests do not update from the gold unopened texture to the blue opened texture. Barrels update texture without issues, as do shulker chests.
In multiplayer, chest textures update as normal.
Apologies if a similar issue exists.

That's an interesting issue. Do you happen to have a copy of the client-side latest.log associated with this session?
Preferably if you could go into a single player game and use the /lootr chest command to create a chest and then see if opening that works or not, and then the latest.log for that session would be very helpful.

Thanks for the reply.
Actually, starting a new session resolved the issue. In the new session I loaded a singleplayer world first. In the other session, I had loaded the multiplayer server first, which is the only distinguishing factor I can think of.
Please find the logs attached. Both sessions contain an instance of /lootr chest.
-1 is the session in which the issue occurred, and the world was loaded at 07:55:32. The issue also occurred in the world loaded at
10:05:35.
-2 is the new session in which the issue did not occur.
2024-03-20-2.log.gz
2024-03-20-1.log.gz

Update: it appears the issue does indeed arise when going from singleplayer to multiplayer and vice versa. I have one more session in which this occurred.
2024-03-20-6.log.gz

That's very interesting and gives me a potential avenue to investigate. Thanks!


Output file should start with

Hello and thank you for providing this theme which is great !
What is wrong
HTML exported file starts with :
<!doctype html>

What it should be
The tag should probably be in CAPS :
<!DOCTYPE html>

The  HTML standard describes it as case insensitive but some implementations seems not to agree with it :
I actually discovered it by having a strange "bug" while uploading my HTML file to github pages. I was getting a 404 on https://{myname}.github.io/{my_repo}/ while https://{myname}.github.io/{my_repo}/index.html was perfectly fine.
I fixed it for myself by including a sed command to my CD process but that should probably be fixed in a more reliable way in the code.

Fixed in v1.0.4.


led strips not available

It is not possible to change the state of LED strips. They do not who in the home app

@dondiego9999, can you detail describe your case?

@dondiego9999, can you detail describe your case?

I  have the same issue: Fibaro RGBW Controller2 not shown in Accessories.

@ilcato, can I help you to localize error ?

Can you check the type attribute in the device api?  I do not have such a devices. I'm looking for com.fibaro.FGRGBW441M and com.fibaro.colorController.

New controller has type - com.fibaro.FGRGBW442

@KostuaD, just published version 1.0.4. Can you try it?

@KostuaD, just published version 1.0.4. Can you try it?

Hello!
Updated to version 1.0.4. The module is registered.
I can turn it on and off, but there is no way to adjust the brightness, and accordingly I can not change the color of the glow of the LED strip.
Thanks you!

@KostuaD, can you send me the whole json object associated to the new device types?

Please tell me which file is needed and where to find it

template-155-com.fibaro.FGRGBW442CC.zip
This is a template loaded with Fibaro HC3

@KostuaD, select the icon with the symbol {...} in the lower left of the Fibaro Home Center web site.
Select "Devices" ine the "Select a definition" combo box.
Select "GET /devices/{deviceID}" row in the list.
Click on "Try it out"
Insert deviceId and press execute.
Post here the resulted response.
Thanks

{
"id": 148,
"name": "Лента (09)",
"roomID": 220,
"view": [
{
"assetsPath": "/dynamic-plugins/com.fibaro.rgbwController/assets",
"jsPath": "/dynamic-plugins/com.fibaro.rgbwController",
"name": "com.fibaro.rgbwController",
"translatesPath": "/dynamic-plugins/com.fibaro.rgbwController/i18n",
"type": "ts"
}
],
"type": "com.fibaro.FGRGBW442CC",
"baseType": "com.fibaro.colorController",
"enabled": true,
"visible": true,
"isPlugin": false,
"parentId": 145,
"viewXml": false,
"configXml": false,
"interfaces": [
"levelChange",
"light",
"zwave",
"zwaveAlarm",
"zwaveMultiChannelAssociation",
"zwaveProtection"
],
"properties": {
"parameters": [],
"pollingTimeSec": 0,
"zwaveCompany": "Fibargroup",
"zwaveInfo": "3,6,4",
"zwaveVersion": "5.0",
"RFProtectionState": 0,
"RFProtectionSupport": 0,
"alarmLevel": 0,
"alarmType": 0,
"categories": [
"lights"
],
"color": "255,0,0,0",
"configured": true,
"currentProgram": 0,
"currentProgramID": 0,
"dead": false,
"deadReason": "",
"deviceControlType": 50,
"deviceIcon": 15,
"emailNotificationID": 0,
"emailNotificationType": 0,
"endPointId": 1,
"isLight": true,
"localProtectionState": 0,
"localProtectionSupport": 0,
"log": "",
"logTemp": "",
"manufacturer": "",
"markAsDead": true,
"model": "",
"nodeId": 29,
"parametersTemplate": "849",
"productInfo": "1,15,9,2,16,0,5,0",
"programsSortOrder": "1,2,3,4,5",
"protectionExclusiveControl": 0,
"protectionExclusiveControlSupport": false,
"protectionState": 0,
"protectionTimeout": 0,
"protectionTimeoutSupport": false,
"pushNotificationID": 0,
"pushNotificationType": 0,
"saveLogs": true,
"serialNumber": "h'0000000000001e70",
"smsNotificationID": 0,
"smsNotificationType": 0,
"state": false,
"useTemplate": true,
"userDescription": "",
"value": 0
},
"actions": {
"reconfigure": 0,
"setColor": 1,
"setValue": 1,
"startLevelDecrease": 0,
"startLevelIncrease": 0,
"startProgram": 1,
"stopLevelChange": 0,
"toggle": 0,
"turnOff": 0,
"turnOn": 0
},
"created":<PHONE_NUMBER>,
"modified":<PHONE_NUMBER>,
"sortOrder": 22
}

@vvsokolov, they changed the api for setting the color. Are you able to test the interface of the setColor action? Without a working device I'm not able to check it. Thanks.

@vvsokolov, they changed the api for setting the color. Are you able to test the interface of the setColor action? Without a working device I'm not able to check it. Thanks.

yes, I can

@ilcato is it version for testing ?

@ilcato , Fibaro release firmware 5.040.37

@vvsokolov can you check how the setColor action works by calling the API directly?

Hi! The same issue. RGBW can be only switched on or off, but brightness control does not work. I can help you to debug the issue if you tell me what you want.

@dior4ik I nee you to try to call the setColor action API in order to understand what I need to pass to it.

I don't have an RGB strip and use Fibaro RGBW only to switch it On, Off and control brightness. Now only On and Off features are working. Here is a sample request for controlling brightness:
curl -X POST "http://<IP_ADDRESS>/api/devices/141/action/setValue" -H  "accept: /" -H  "Content-Type: application/json" -H  "X-Fibaro-Version: 2" -H  "Accept-language: en" -H  "Authorization: Basic .........." -d "{"args":[100]}"

@dondiego9999 , @vvsokolov , @dior4ik , @KostuaD can you test latest version of the plugin for this issue ?

Hello ilcato!
In new version of plugin test passed.
Fibaro RGBW Controller2 work correctly. Brightness, color, switch on and off all worked.
Thank you!


Let third party libraries reuse logic

Describe the bug
Following the new logic integration, we now have a clear VoxeetAppCompatActivity extends VoxeetCommonAppCompatActivity. However most of cross platform libraries or even libraries requiring the developer to override the AppCompatActivity will need to copy/paste a lot of the UXKit's logic to be compatible with both framework/libraries
Expected Behaviour

Developer should have a friction less integration
Avoid copy/paste most of the logic
Reuse a maximum of said logic

Note : Only libraries support AndroidX will be supported (either directly or via jetifier)

Note: this include directly React Native and Cordova support

Closing as the whole architecture is ready 👍


Add ability to write using a pure PUT request

Without going through the fileWriter.

Fixed by #12


Fork Laravel

Go ahead and fork the Laravel repository and add the data-set you'd like to work with in this issue.

The civilian workers' index shows steady growth in overall employment. As of June 2023, the index has reached 159.0, indicating a 1.2% increase over the three-month period.
The health care and social assistance industry has consistently shown growth, with an index of 157.2 in December 2005 reaching 159.0 in June 2023
The data highlights differential growth rates between goods-producing industries and service-providing industries. While goods-producing industries experienced a 0.9% increase in the three months ending June 2023, service-providing industries only saw a 0.6% increase.
The professional and business services industry has shown varied growth rates. While the index reached 157.7 in June 2023, indicating a 1.4% increase during the three months ending June 2023
The financial activities industry experienced a decline during the three months ending June 2023. The index decreased from 156.8 in March 2023 to 155.2 in June 2023, resulting in a negative percent change of -1.9%. This indicates a contraction in the financial sector

Great. Let's start by closing this issues out and working on creating an endpoint to retrieve those data sets.


Commenting with ctrl+/ does not work.

Commenting with ctrl+/ does not work.

Yeah, it doesn't seem to recognise # as a comment at all. Odd, because it looks like the author has copied the code for comments from the Python files...

this is still the case...

Still :(

mmm it would seem that beefsack is no longer maintaining this... is someone willing to fork in order to correct this bug ?? which is way beyond my capabilities...

Hi, apologies for the tardiness on getting to this one.
Implementing commenting support is a standalone feature, all this plugin does at the moment is syntax highlighting and snippets.  Commenting support requires
I moved away from Sublime Text over a year ago so it'll be unlikely I'll be able to implement this, but PRs are welcome.  I'd suggest people look at other plugins which support the commenting shortcuts if they're looking for examples.

Actually I think the issue is more about comments not being highlighted than having a shortcut to comment lines.
Currently every line that starts with # is white, when it should be.. gray I guess.
Is it possible to add that to the syntax highlighting without much hassle?
Thanks for the heads up!

Bump? Anyone managed to fix this?


vibe.core.file.readFile throws OOM Exception reading pseudo system file.

Example test.
import vibe.core.file;

shared static this()
{
    auto f = readFile("/proc/self/statm");
}

Building vibe-d 0.7.26 configuration "libevent", build type debug.
Running dmd...
Building bug ~master configuration "application", build type debug.
Compiling using dmd...
Linking...
Running ./bug
core.exception.OutOfMemoryError@(0)
Error executing command run:
Program exited with code 1

Also happens with master.
Stepping through the code:
ubyte[] readFile(Path path, ubyte[] buffer = null, size_t max_size = size_t.max)
{
        auto fil = openFile(path);
        scope (exit) fil.close();
        enforce(fil.size <= max_size, "File is too big.");
        auto sz = cast(size_t)fil.size;      // <---  fil.size = -1
        auto ret = sz <= buffer.length ? buffer[0 .. sz] : new ubyte[sz];   // <--- OOM
        fil.read(ret);
        return ret;
}

i guess it comes from here:
https://github.com/rejectedsoftware/vibe.d/blob/master/source/vibe/core/drivers/threadedfile.d#L109
i don't understand the comment on stat_t being wrong on linux, it seems to work fine.
then i guess
https://github.com/rejectedsoftware/vibe.d/blob/master/source/vibe/core/drivers/threadedfile.d#L174
would also need a fix to cope with unknown filesize


space law book

About the PR

Added space law book, which works like other guidebook books
Also added it to different places
reopened #22921
Why / Balance

Useful to have space law in-game
Technical details

Media

[ ] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

add: Space Law book added to the game.

I think the the Security 101 book has space law inside

I think the the Security 101 book has space law inside

where is this book located?

I think the the Security 101 book has space law inside

It opens the Security page of the guidebook.

no sprite for the book?

no sprite for the book?

its already exist


[tests] change string concatenation format in python scripts

Solve issue #3924

What about the following two cases:
https://github.com/openthread/openthread/blob/6a96f647915f0ae8975186fc4197d1dd7ee152c8/tests/scripts/thread-cert/node.py#L366
https://github.com/openthread/openthread/blob/6a96f647915f0ae8975186fc4197d1dd7ee152c8/tests/scripts/thread-cert/node.py#L766

What about the following two cases:
https://github.com/openthread/openthread/blob/6a96f647915f0ae8975186fc4197d1dd7ee152c8/tests/scripts/thread-cert/node.py#L366
https://github.com/openthread/openthread/blob/6a96f647915f0ae8975186fc4197d1dd7ee152c8/tests/scripts/thread-cert/node.py#L766

@jwhui
Sorry for missing that. I've changed the two cases.


Fix for #9317, #9353

Removed two Yii 2 disservices which may lead to fatal errors in several components.

Rethink my mind. It may be interested to know that components not defined.

its quite confusing that some application's components do return an error and some dont. I would choose for consistency and let the enduser decide if an error is to be thrown

@dynasource This PR is closed 8 minutes before you write comment ;-) Correct fix is https://github.com/yiisoft/yii2/pull/9369

I know. I would like to know why you choose to skip this commit and prefer inconsistency.

@dynasource #9369 is much more consistent and agile.


Speed up smoke tests

Description of changes: This reduces run time for this test to 1:20 minutes, down from 3:30 minutes, on my machine.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Please tag this pr with at least one of these labels to make our release process faster: BREAKING, new feature, bug fix, other change, dev setup

Saved a couple tenths of seconds here and there as well

Does this only affect MQCNN?

No, fixed the title

Is there a reason to run for at least two epochs, to make sure that looping works?

I don't think so, there are other tests that do training on multiple batches and epochs


Refactor SearchTokens.py

The get method in the SearchTokens class in SearchTokens.py has a number of issues which merit addressing:

The function currently is quite long (100 lines) and mixes multiple concerns: managing database transactions, conditionally executing different queries, and handling the business logic based on URL parameters. This makes the function difficult to test and maintain.
Excess and redundant error handling: There are multiple nested try-except blocks, which makes the code complex and harder to maintain
Inserting tokens into the database with hardcoded SQL mixes data access logic with controller logic and violates separation of concerns
Exceptions are printed to standard output and internal error messages are potentially leaked to the user, which can lead to a leak of sensitive information.
The line if type(self.psycopg2_connection) == dict: is unclear and seems incorrect for validating database connection status
Some error handling branches return both a tuple with a dictionary and status code, while others return a dictionary, leading to inconsistent behavior
Use of print() for logging is not advisable -- this is less flexible and harder to manage than logging frameworks which support levels and better output management
Data is repeatedly fetched and then transformed in ways that could potentially be optimized and simplified.

Refactoring is merited in this situation to make the code more comprehensible, maintainable, and testable.

@josh-chamberlain I may need a better understanding of the Search Tokens:

Why do we need them in the first place?
How is it being used on the front-end? The Search Token code appears to call several database-interfacing functions which are also used by other endpoints -- for example: /data-sources, and /quick-search. Why do we have multiple endpoints performing the same functionality, only one uses search tokens?

@maxachis consider this a conversation in progress. search tokens were a quick way to get a prototype up, but definitely not the longest-term solution. I think the reason these concepts are tied together is that search is the first real action people can take in the app.
Here are some goals of auth:

the Vue app effectively is a user of our public API with base permissions
when users log in, they get a JSON web token (JWT) and a couple additional permission

@joshuagraber , anything to add about what would be helpful from your perspective?

@josh-chamberlain @maxachis Sorry, I must've been away when you tagged me here. Closing this without any more work seems appropriate, and we can just move forward with the new search paradigm we've been discussing.


OpenAPI emitter: @extension should also be applied to securitySchemes

Clear and concise description of the problem
@extension("x-amazon-apigateway-authtype", "custom")
model MyAuth is ApiKeyAuth<ApiKeyLocation.header, "Authorization">;

Should emit to:
components:
  securitySchemes:
    MyAuth:
      type: apiKey
      in: header
      name: Authorization
      x-amazon-apigateway-authtype: custom

Checklist

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

est: 5

Not sure if a separate issue, but I too would like to be able to use this for AWS API Gateway, and include the necessary things for using Cognito.
Similar to above but needs the authorizer as well:
  securitySchemes:
    myCognitoSecurity:
      type: "apiKey"
      name: "Authorization"
      in: "header"
      x-amazon-apigateway-authtype: "cognito_user_pools"
      x-amazon-apigateway-authorizer:
        providerARNs:
        - "arn:aws:cognito-idp:us-west-2:<redacted>:userpool/us-west-2_<redacted>"
        type: "cognito_user_pools"

I believe this will also require changes to ApiKeyAuth to support scopes, as that section should look like:
      security:
      - myCognitoSecurity:
        - myScope


Introduce Scheduling bounded context

Description
Core scheduler management is not properly encapsulated and can be accessed and modified everywhere. We need to encapsulate the scheduling functions to only be accessible by proper interfaces. As part of this we will introduce a domain for dealing with core scheduling bounded context.
Depends on : 575
Acceptance Criteria

[ ] core scheduling related logic should be encapsulated
[ ] Client should still rely on the same apis & there should be minimal change in the api contract.
[ ] All service and handlers related to job runs will be part of this domain
[ ] Remove the old api from Protos.
[ ] Dag compilation should happen properly.
[ ] Dag uploading/updating and deletion of Dags for removed jobs should happen properly.
[ ] Priority resolution logic should not be changed.
[ ] DAG deploying to Scheduler should be run independently of job spec creation, and dependency and priority resolution
[ ] Alerting should be proper for SLA misses and Job Failures(only complete DAG failures/not operator failures)
[ ] Relevant metrics and logging should be improved to address the debuggability concerns.
[ ] Re assess the metric collection callbacks/events from the scheduler.
[ ] Re assess the Data Base model for metrics collected for job_run and its breakup(sensors/tasks/hooks).

Scope

[x] Introduction of the new scheduler bounded context with all the handlers & services.
[x] JobRunInput
[x] UploadToScheduler
[x] RegisterJobEvent [takes care of job state updation( scheduling metrics )  and alerting ]
[x] JobRun
[x] Introduction of new repositories to work with the new models being introduced as part of this BC.
[ ] Improve the debuggability through logging, capturing the right metrics.

Out of Scope

Handling of replay functionality in Optimus
Handling of backup
GetJobTask API
GetWindow API
JobStatus API
RunJob API

JobRunInput Scenarios

should be able to get job resources such as job assets / evn variables / secrets
if a job_run exists then fetch execution time from the existing job run.

else use schedule time as execution time.

Out of scope:

RegisterJobEvent

should update job run state appropriately

job run

details captured

[refenrece information] -> job name , project name , namespace name
[run state] -> status
[time metrics] -> scheduled time , start time , end time , sla definition

events observed / Callback Mappings

TYPE_JOB_SUCCESS <- job_success_event
TYPE_JOB_FAIL <- job_failure_event

Scenarios

creation

Entry in job run table is done when a job_run of given schedule time is fetched for the first time. The end time here is saved as a long time in future in year 3000.
Only one job_run entry remains per job for a given schedule time.

updation

on TYPE_JOB_SUCCESS, TYPE_JOB_FAIL the job state and end_time is updated appropriately, based on information fetched from event.

operator run

Note: (sensor_run/task_run/hook_run) is refered as operator_run for brevity.
details captured

[refenrece information] -> job run id, operator name
[run state] -> status
[time metrics] -> start time , end time

events observed / Callback Mappings

TYPE_<operator-type>_START <-  operator_start_event
TYPE_<operator-type>_SUCCESS <-  operator_success_event
TYPE_<operator-type>_RETRY <-  operator_retry_event
TYPE_<operator-type>_FAIL <-  operator_failure_event

Scenarios

creation

Entry in (sensor_run/task_run/hook_run) table is done when a TYPE_<operator-type>_START event is received. The end time here is saved as a long time in future in year 3000.
multiple operator_run entry are persisted based on attemps of that operator

updation

on TYPE_<operator-type>_SUCCESS ,TYPE_<operator-type>_RETRY, TYPE_<operator-type>_FAIL the job run state and end_time is updated appropriately, based on information fetched from event. Also if operator_run entry does not already exist, then it is created before running the updation.

relay alert events to appropriate channels as configured

SLA_MISS

TODO:EVENT FIRING LOGIC STILL NEEDS TO BE ANALYSED
appropriate msgs are prepared for the configured chanels and a Notification is queued to be sent

TYPE_JOB_FAIL

appropriate msgs are prepared for the configured chanels and a Notification is queued to be sent

Out of scope:

Using the job run information for powering the sensor logic

JobRun Scenarios

should fetch job runs based on the request to power sensor logic.
Validate the incomming request

if request is invalid, respond with non 200 status code.

if job runs are not found for the given criteria

Then give emtpy response with a 200 status code.

Run Fetch logic

Calculate a set of expected runs based on the request window and the job's cron schedule

keeping the status of all as pending

Fetch runs information from the scheduler

this shall have the actual status of the runs

Merge the above 2 set of runs
Return the so obtained set of runs with the appropriate statuses

Out of scope:

powering this using the metrics captured in job_run table

UploadToScheduler Scenarios

should fetch all jobs in a given project

resolve priorities
group jobs by tenant
compile and upload dags

dags are to be uploaded to the scheduler
if the namespace folder is empty then delete

Out of scope:

dependency resolution, needs to be done by job bounded context


[BUG] REST APIs return incorrect HTTP Status Codes

What is the bug?

When a non-existent model ID or ML resource is sent in a REST Request, 400 Bad Request or 500 Internal Server Error or 200 OK are returned.  The return value should be 404 Not Found.

API
HTTP Status Code

Update Group
500

Delete Group
200

Deploy Model
500

Get Model
400

Predict Model
400

Unload Model
500

Delete Model
400

Get Task
500

How can one reproduce the bug?
Steps to reproduce the behavior:
Use the above APIs with a non-existent Model name or ML Resource.
For Unload model, attempt to unload a model in the deploying state.
What is the expected behavior?
Requests that specify a resource that could not be found should return 404 Not Found.
Status code 500 Internal Server Errors should not be returned during expected operation of the application and be reserved for unhandled and unexpected exceptions.
Do you have any additional context?
HTTP/1.1 400 Bad Request
content-type: application/json; charset=UTF-8
content-length: 273

{
    "error": {
        "root_cause": [
            {
                "type": "illegal_argument_exception",
                "reason": "Failed to find model to delete with the provided model id: NotAModel"
            }
        ],
        "type": "illegal_argument_exception",
        "reason": "Failed to find model to delete with the provided model id: NotAModel"
    },
    "status": 400
}

HTTP/1.1 500 Internal Server Error
content-type: application/json; charset=UTF-8
content-length: 185

{
    "error": {
        "root_cause": [
            {
                "type": "m_l_resource_not_found_exception",
                "reason": "Fail to find model"
            }
        ],
        "type": "m_l_resource_not_found_exception",
        "reason": "Fail to find model"
    },
    "status": 500
}

HTTP/1.1 500 Internal Server Error
content-type: application/json; charset=UTF-8
content-length: 287

{
    "error": {
        "root_cause": [
            {
                "type": "exception",
                "reason": "Model cannot be deleted in deploying or deployed state. Try undeploy model first then delete"
            }
        ],
        "type": "exception",
        "reason": "Model cannot be deleted in deploying or deployed state. Try undeploy model first then delete"
    },
    "status": 500
}

What is the correct exception name for the 404 in OpenSearch? Do you have an example? @dbwiddis

This looks like the source of the bug:
https://github.com/opensearch-project/ml-commons/blob/0e834a87fbef4888ffa03c2b990314e0561c7f50/plugin/src/main/java/org/opensearch/ml/action/handler/MLSearchHandler.java#L74
It returns on IllegalArgumentException || MLResourceNotFoundException

https://github.com/opensearch-project/ml-commons/pull/1074. This issue is partially resolved in the pen tests.

https://github.com/opensearch-project/ml-commons/pull/1079/files

This issue is fixed with the above 2 PRs.


@graphql-codegen/client-preset w/o needing to use useFragment

Is your feature request related to a problem? Please describe.
I love the new client preset '@graphql-codegen/client-preset', but I don't want to always have to use useFragment to get some data out from a query that used fragments for one reason or another.
Describe the solution you'd like
A configuration option that allows you to opt out from useFragment being a requirement. Essentially it would just change the TS types so that all of the fragment fields are accessible directly, without needing to use useFragment first.
Describe alternatives you've considered
I could just set up basic GQL codegen without the preset, but this preset is so easy to use and brings such nice DX that I'd rather avoid that.

@fabis94 Will that help you?
const config = {
   schema: 'https://swapi-graphql.netlify.app/.netlify/functions/index',
   documents: ['src/**\/*.tsx', '!src\/gql/**\/*'],
   generates: {
      './src/gql/': {
         preset: 'front-end',
         presetConfig: {
           fragmentMasking: false,
         }
       },
   },
};


Add security category in civo marketplace (with tools like kube-scan, polaris)

This issue is a:
[ ] Bug Report
[ ] Enhancement suggestion
[ * ] Feature request
If the issue concerns an existing Marketplace application, please tag the maintainer of the application (found in manifest.yaml) below:
Enhancement suggestions / feature requests
While exploring civo kubernetes service. What I really missed is deploying any security related tools on k8s through marketplace.
As a start, I would like to add tools like kube-scan and polaris to the marketplace.

maybe you can give starboard a try

Feel free to add PRs for any security tools you'd recommend. We're happy to make a new category for them.

I've added the category to the official supported list.


[FEAT] Loading Animation for Page Load

Description
This will help show some form of animation while the page is loading data from the backend or still loading the page.
Acceptance Criteria

Loading Animation:

A skeleton loader is displayed when the page is initially visited.
A skeleton loader is displayed when the page is loading heavy data.

Stop Loading Animation:

The loading animation stops when the page is fully loaded.
The transition from the loading animation to the fully loaded page is smooth and user-friendly.

Requirements

Show Animation While Page is Loading:

Implement a skeleton loader state when you just visit the page.
Implement a skeleton loader state when the page is loading heavy data.

Stop Loading Animation When Page is Fully Loaded:

Ensure the loading animation stops when the page is fully loaded.

Expected Outcome

[ ] A loading animation is displayed while the page is loading data from the backend or still loading.
[ ] The loading animation stops once the page is fully loaded.

Testing

Unit Tests:

Write unit tests to ensure the loading animation is displayed correctly.
Test various scenarios, including initial page load and loading heavy data, to verify the loading animation behavior.

Performance Testing:

Ensure the loading animation does not significantly impact page performance.
Test the transition from loading to fully loaded state to ensure it is smooth.

This is a backend repo, not a frontend repo


Keyboard shortcut for browser help about a keyword

I really miss a keyboard shortcut like F1 in SSMS, where you can lookup the online help article for a keyword e.g. I press F1 when my cursor is standing on SELECT and then the online article on https://docs.microsoft.com/ about select is opened in my browser. For PowerShell ctrl-F1 also does this for Visual Studio Code, so I suggest to add the same logic for Azure Data Studio.
Regards
Camilla

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5fe030aa-7a71-2d02-c26f-103cfe4687a8
Version Independent ID: 4781bc1f-47db-5eb3-066d-0177014fd7c7
Content: Create and customize keyboard shortcuts - Azure Data Studio
Content Source: docs/azure-data-studio/keyboard-shortcuts.md
Product: azure-data-studio
Technology: azure-data-studio
GitHub Login: @markingmyname
Microsoft Alias: maghan

@camillagaardsted -- thank you for your feedback.  For product suggestions, please use this link:

SQL Server Feedback

I am closing this issue now.  You are welcome to @ mention me for any followup.
We hope to hear from you again.


Fix firefox scroll speed

This PR fixes https://github.com/microsoft/monaco-editor/issues/1861
Firefox seems to be the only browser which supports DOM_DELTA_LINE.
In that case, deltaY is a number of lines. By default, its value is 3 or -3 which is then multiplied by 50 to get the scroll offset, so 150px, which is obviously too fast
In other browsers, the deltaY/deltaX is 1 or -1, so the scroll offset is just 50px
see:

https://stackoverflow.com/questions/20110224/what-is-the-height-of-a-line-in-a-wheel-event-deltamode-dom-delta-line/57788612#57788612
https://github.com/vaadin/vaadin-grid/pull/1648

In light of https://github.com/microsoft/monaco-editor/issues/1861#issuecomment-644108937 wouldn't it be easier to check if the scroll is positive / negative and apply the appropriate SCROLL_WHEEL_SENSITIVITY explicitly?

In light of microsoft/monaco-editor#1861 (comment) wouldn't it be easier to check if the scroll is positive / negative and apply the appropriate SCROLL_WHEEL_SENSITIVITY explicitly?

delta_multiplier_y would be ignored on that case, is that something we would want?
I wanted to keep the changes as simple as possible and change the behavior as less as possible in order to get it merged quickly, the main issue here is the scroll on Firefox being very unpractical.
If we want to ignore delta_multiplier_y, don't you think it's something that can be decided later? I didn't find any issues related to it.
Btw I'm not a Firefox user but I don't see any reason Monaco should ignore an user setting: If the user want their scroll to be fast, who am I to judge?

Without this pull request, the wheel sensitivity is different on Firefox and Chrome because Firefox uses DOM_DELTA_LINE. This pull request fix the computation of the delta in pixels by properly converting lines to pixels for firefox.
We deployed that fix on production for thousands of users and it works perfectly (and the same way with both firefox and chrome).
I think that ignoring delta_multiplier_y could be discussed in another issue. The issue I open is 100% fixed by this pull request.

is that something we would want?

Either that or we have to reduce the default scroll speed a lot. See my explanations in the attached issue.

I didn't find any issues related to it.

Since it is strongly related to https://github.com/microsoft/monaco-editor/issues/1861 I've reported it there, but could be tracked separately of course.

I don't see any reason Monaco should ignore an user setting: If the user want their scroll to be fast, who am I to judge?

I'm a Firefox user and currently it is not possible to use the mouse wheel in Monaco, because Monaco itself defaults to a fast scrolling speed already. There is also a difference between whole page scrolling and scrolling embedded content, which justifies not applying the setting -- the setting doesn't differentiate. I'm quite sure most people bumping up delta_multiplier_y do it for the slow whole page scrolling speed in FF (and the abuse of long scrolling in landing pages / low vertical information density of websites), and don't want their editor windows jump 100 lines of code with a mouse wheel tick.

I'm a Firefox user and currently it is not possible to use the mouse wheel in Monaco, because Monaco itself defaults to a fast scrolling speed already.

This PR makes the scrolling speed the same between Firefox and Chrome. If you still think that it's too fast, I believe this should be fixed in another PR.

This has been fixed via https://github.com/meganrogge/vscode/commit/c4309ff45e8a9e2ab27d88e10a085ad9d828616c


Integration with mkdocs example does not work out of the box!

I followed the example setup described in https://entangled.github.io/mkdocs-plugin/ and I was not getting what I was expecting.
For example, I added the very simple example defined in https://entangled.github.io/mkdocs-plugin/#annotate-code-blocks I was following, but the python source files were not generated.  I thought it was a matter of restarting the mkdocs serve command but still no python file generated.
I had to open a separate terminal and run there: entangled watch to get the behavior I was expecting, meaning the creation of a example/hello_world.py file (although, following along the mkdocs init example, I would expect the file to be named: src/example_package/hello_world.py so that it would end up in the source folder already created from mkdocs, but I divert)
Isn't it the idea to trigger the entangled functionality through the mkdocs hook?  Or maybe the instructions miss a step that explains that a separate process needs to run in parallel?
Not sure what is the intended usage here.
Nonetheless I'm thrilled if I can get this to work smoothly! :)

Yes you're right. For some time I had entangled sync triggered by the mkdocs serve loop. This didn't always work as expected though. Entangled would not always be triggered when needed, leading to conflicts when both markdown and source code were changed. I had to disable the integration with the downside that you have to run entangled watch next to mkdocs serve.

I am not clear then on the use of the entangled plugin in mkdocs. Or is that obsolete too?

It does transform the Markdown to render code blocks with a nice title. I do intend to extend support further (things like code navigation, figure captions) Just haven't found the time yet.

Ah yes, now I see it, thanks.
I'm not negatively critical here, I am just trying to figure out where things are given the state of the demos/documentation. I'm starting using it now, so maybe I'll have more feedback later on.
I'll leave the issue open, here, maybe as a reminder that the online instructions are out of date, maybe needing fixing?

Yes, excellent!


TODO: transition from PF4 to PF5

Description to be written.

Closing this PR, we will make this effort once we've passed the demo.


simply NettyExecutorManager.execute logic making it readable

What is the purpose of the pull request

NettyExecutorManager.execute logic is not graceful , using LinkedList to make it readable

Brief change log

NettyExecutorManager.execute()

hi, @qiaozhanwei  could you help to review this PR ?

Codecov Report

Merging #2744 into dev will decrease coverage by 0.18%.
The diff coverage is 85.71%.

@@             Coverage Diff              @@
##                dev    #2744      +/-   ##
============================================
- Coverage     37.19%   37.00%   -0.19%
+ Complexity     2554     2543      -11
============================================
  Files           434      434
  Lines         19977    19975       -2
  Branches       2423     2424       +1
============================================
- Hits           7430     7392      -38
- Misses        11880    11916      +36
  Partials        667      667

Impacted Files
Coverage Δ
Complexity Δ

...master/dispatch/executor/NettyExecutorManager.java
83.92% <85.71%> (+8.06%)
10.00 <3.00> (+1.00)

...duler/server/entity/DataxTaskExecutionContext.java
35.00% <0.00%> (-60.00%)
7.00% <0.00%> (-6.00%)

.../server/worker/processor/TaskExecuteProcessor.java
10.16% <0.00%> (-27.12%)
1.00% <0.00%> (-2.00%)

...he/dolphinscheduler/api/service/LoggerService.java
82.60% <0.00%> (-8.70%)
9.00% <0.00%> (-1.00%)

...nscheduler/server/entity/TaskExecutionContext.java
81.18% <0.00%> (-5.95%)
57.00% <0.00%> (-3.00%)

...ver/master/consumer/TaskPriorityQueueConsumer.java
54.41% <0.00%> (-4.42%)
16.00% <0.00%> (ø%)

...e/dolphinscheduler/remote/NettyRemotingClient.java
51.07% <0.00%> (-2.16%)
9.00% <0.00%> (-1.00%)

...he/dolphinscheduler/common/thread/ThreadUtils.java
77.77% <0.00%> (+6.34%)
15.00% <0.00%> (+1.00%)

Continue to review full report at Codecov.

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

+1


DDF-1226 Moved support-pmd project to ddf-support

Reviewers: @shaundmorris @lessarderic @andrew-fiedler

We're getting the following PMD warning when building:
[INFO] --- maven-pmd-plugin:3.4:pmd (pmd) @ catalog-solr-external-provider ---
[WARNING] Unable to locate Source XRef to link to - DISABLED

Can you add the following to the pmd section of the ddf-parent pom file and see if it solves the problem?
<reporting>
    <plugins>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-jxr-plugin</artifactId>
            <version>2.3</version>
        </plugin>
    </plugins>
</reporting>

Link to stackoverflow on this: http://stackoverflow.com/questions/12038238/unable-to-locate-source-xref-to-link-to

Did a clean build of ddf-support, ddf-parent and ddf-catalog and everything looks good.
:+1:

Tried to above fix to get rid of the warning and didn't work so let's just ignore that for now and move on.

:+1: we wanted to move support into platform, which looks like we can do from a build stand point, but there are issues with the maven release plugin when you attempt to release. This will at least allow for releasing ddf-parent to be smooth.

Verified build


Reduce retry-after header value

We currently use 3 seconds as retry-after value sent back to the client when a historical query is not cached in-memory yet. This seems excessive and should be lowered to 1 second.

Do you think this is worth making it runtime-configurable?


Does your library support swift 3.0?

Of course, just use the 7.x branch.

Mind posting this on the docs or README, would be good to know that :)
Thanks again for providing this repo and making it public!


update template to latest nuxtent version

Hi,
When I generate static with the command yarn generate, I am able to access to the main page but I can't access to https://mydomain.com/hello-world, it's only work in dev with yarn run dev http://myipvps:3000/hello-world
my nuxtent.config.js :
module.exports = {
  content: {
    permalink: ':slug',
    routes: [
      {
        path: '/_content',
        method: 'get'
      }
    ],
    isPost: false
  },

  api: {
    baseURL: process.env.NODE_ENV === 'production'
      ? 'https://mydomain.com'
      : 'http://myipvps:3000'
  }
}

my package.json :
{
  "name": "stnetwork",
  "version": "1.0.0",
  "description": "Nuxtjs Buefy",
  "author": "",
  "private": true,
  "dependencies": {
    "nuxtent": "latest",
    "nuxt": "1.0.0-alpha.3",
    "@nuxtjs/axios": "latest"
  },
  "scripts": {
    "dev": "HOST=myipvps nuxt",
    "build": "nuxt build",
    "start": "nuxt start",
    "generate": "nuxt generate",
    "lint": "eslint --ext .js,.vue --ignore-path .gitignore .",
    "deploy": "push-dir --dir=dist --branch=gh-pages --cleanup",
    "precommit": "npm run lint"
  },
  "devDependencies": {
    "babel-eslint": "^7.1.1",
    "eslint": "^3.15.0",
    "eslint-config-standard": "^6.2.1",
    "eslint-loader": "^1.6.1",
    "eslint-plugin-html": "^2.0.0",
    "eslint-plugin-promise": "^3.4.1",
    "eslint-plugin-standard": "^2.0.1"
  }
}

http://myipvps:3000/hello-world , that works
https://mydomain.com, that works
https://mydomain.com/hello-world, doesn't work (404 Page not found, nginx)
Thanks

Hi, thanks for opening this issue. The api changed and I will need to update the template. Will do that soon

@STnetwork Template is updated!


FAQ updates

New FAQ added and some fixes in CI FAQ

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65b3928a45ca57b3f778ec91--harness-developer.netlify.app


focal install fails

I get an install error using cs:ubuntu on focal: https://paste.ubuntu.com/p/3HMQsSCbhd/

This is https://github.com/juju/charm-helpers/pull/423

But yeah, the charm needs to be rebuilt bulling in the fix.

I tried rebuilding the charm as-is, pushing to the charmstore and deploying, and it failed in the same way for me (using cs:~mthaddon/ubuntu)

The charm-helpers PR has been released in v0.20.9 and I verified that rebuilding the Ubuntu charm now fixes the issue. I don't have permissions to update cs:ubuntu, though, and @tvansteenburgh is out this week.

I tried rebuilding the charm as-is, pushing to the charmstore and deploying, and it failed in the same way for me (using cs:~mthaddon/ubuntu)

I think the reason I was seeing this was local cache. If I build with --no-local-layers I also see the correct charmhelpers version. Thanks.

Confirming this has now been fixed.

FYI, this went out in cs:ubuntu-14


Support for smaller fees

Updated! Check BWU also

ACK, great work, we are getting there... :)

Thanks for the comments and for reviewing @dabura667 @matiu


overview for veracity replicate-logs

Truenorth targeted docs update for the 3rd party verification process and benefits

I've pushed a few updates for spelling and formatting, as well as updating the imagery.

LGTM - with some ppt removal coming...


[batches] make batch min/max edit dates date-strings instead of timesstamp

The date type is formatted as full timestamp on the json response. This is kinda useless, especially since the date here represents the CoreData.date field, which is only date and always presented as date string.
Just stringify the field

It's a soft prerequisite to use it, because otherwise it's a full timestamp, with time zone and a lot of mess that is not needed


[TASK] Bump embedded Rancher to v2.8.x and RKE2 to v1.27.x

Is your enhancement related to a problem? Please describe.

We should ship a supported Rancher and RKE2 in v1.3.0.
Describe the solution you'd like

Bump Rancher to v2.8.x.
Bump RKE2 to v1.27.x.

Describe alternatives you've considered

Additional context

RKE2 v1.27.10+rke2r1 has been released, do we plan to also bump? @bk201 @markhillgit @ibrokethecloud
https://github.com/rancher/rke2/releases/tag/v1.27.10%2Brke2r1
This v1.27.10 will solve this important issue: https://github.com/harvester/harvester/issues/4633

Verifying on v1.3-50a00ad1-head (24/02/20).
Result
$\color{green}{\textsf{PASS}}$ Clean install: bump Rancher 2.8.2 and RKE2 to 1.27.10  $~~$
harv1:~ # kubectl get settings.management.cattle.io server-version
NAME             VALUE
server-version   v2.8.2
harv1:~ # kubectl get nodes
NAME    STATUS   ROLES                       AGE   VERSION
harv1   Ready    control-plane,etcd,master   30m   v1.27.10+rke2r1

$\color{blue}{\textsf{Ongoing}}$ Upgrade path (v1.2 > v1.2-head > v1.3-head): bump Rancher 2.8.2 and RKE2 to 1.27.10  $~~$

Test Information

Test Environment: Single and three nodes Harvester on baremetal machines
Harvester version: v1.3-50a00ad1-head (24/01/20)

Verify Steps
Clean and upgrade path

Access to Harvester master node
Check the Rancher version

kubectl get settings.management.cattle.io server-version

Check the RKE2 version

kubectl get nodes


I wanted to raise your attention to some things i found out that might be helpful

    registrator:
        container_name: registrator
        image: gliderlabs/registrator
        command: -ip $DOCKER_HOST_IP -resync 60 consul://consul:8500
        volumes:
            - /var/run/docker.sock:/tmp/docker.sock
        depends_on:
            - consul
        links:
            - consul
        env_file:
            - ./shared/dev.env
    consul:
        container_name: consul
        command: -data-dir /data -ui-dir /ui -server -bootstrap
        image: progrium/consul
        ports:
            - 53
            - 8301
            - 8302
            - 8400
            - 53/udp
            - 8301/udp
            - 8302/udp
            - 8300:8300
            - 8500:8500
        env_file:
            - ./shared/dev.env
        volumes:
            - ./consul:/etc/consul.d
    consul-template:
        container_name: consul-template
        command: >
            -consul consul:8500
            -template "/etc/nginx/templates/upstream_servers.ctmpl:/etc/nginx/conf.d/upstream_servers.conf"
            -template "/etc/nginx/templates/upstream_stream_servers.ctmpl:/etc/nginx/conf.d/streams/upstream_servers.conf"
        image: masm/consul-template
        volumes:
            - /var/run/docker.sock:/tmp/docker.sock
        volumes_from:
            - server
        depends_on:
            - consul
        links:
            - consul
        env_file:
            - ./shared/dev.env

After a bit of testing and fiddling with a lot of the 3 images settings i have found this configuration out.
This works as part of a compose file. as you can see there was no need for changing the network mode or hacking to get the docker ip.
The key was using the links. This must be an issue in docker compose it self as the network should already allow em to link to those services by name but alas this is not possible it seems at the time from the command option. now the -ip $DOCKER_HOST_IP is the last thing that needs to be taking out for a fully ubiquitous solution and nothing i can think of seems possible so i ask for your help on this part and i can then write up a full solution for others to use

I'm new to all this... I am wondering why so many ports for consul?
The examples I've seen for running the consul node with docker run look like:
-p 8400:8400 -p 8500:8500 -p 8600:53/udp

I believe consul has multiple ports you can pass data into but all different protocols


Revert @rjsf/core and @rjsv/validator-ajv8 to v5.18.3

Proposed Changes
(Describe your changes here. Also describe the motivation for your changes: what problem do they solve, or how do they improve the application or codebase? If this pull request fixes an open issue, use a keyword to link this pull request to the issue.)
#7098 introduced a Javascript error. This PR reverts the dependency update (can revisit next month).

Screenshots of your changes (if applicable)

Associated [documentation repository](https://github.com/MarkUsProject/Wiki) pull request (if applicable)

Type of Change
(Write an X or a brief description next to the type or types that best describe your changes.)

Type
Applies?

🚨 Breaking change (fix or feature that would cause existing functionality to change)

✨ New feature (non-breaking change that adds functionality)

🐛 Bug fix (non-breaking change that fixes an issue)

🎨 User interface change (change to user interface; provide screenshots)

♻ Refactoring (internal change to codebase, without changing functionality)

🚦 Test update (change that only adds or modifies tests)

📦 Dependency update (change that updates a dependency)
X

🔧 Internal (change that only affects developers or continuous integration)

Checklist
(Complete each of the following items for your pull request. Indicate that you have completed an item by changing the [ ] into a [x] in the raw text, or by clicking on the checkbox in the rendered description on GitHub.)
Before opening your pull request:

[X] I have performed a self-review of my changes.

Check that all changed files included in this pull request are intentional changes.
Check that all changes are relevant to the purpose of this pull request, as described above.

[X] I have added tests for my changes, if applicable.

This is required for all bug fixes and new features.

[X] I have updated the project documentation, if applicable.

This is required for new features.

[X] If this is my first contribution, I have added myself to the list of contributors.

After opening your pull request:

[ ] I have updated the project Changelog (this is required for all changes).
[ ] I have verified that the pre-commit.ci checks have passed.
[ ] I have verified that the CI tests have passed.
[ ] I have reviewed the test coverage changes reported by Coveralls.
[ ] I have requested a review from a project maintainer.

Questions and Comments
(Include any questions or comments you have regarding your changes.)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 91.423%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
40000

Relevant Lines:
43079

💛  - Coveralls